Electronic devices, methods, and computer programs

Abstract

The electronic device comprises a circuit section designed to manage communication schedules within either a mesh network or a cellular network, each mesh modem and each cellular modem network using at least one shared network resource. The mesh network operates according to a specific mesh protocol, and the cellular network operates under a cellular protocol. The management of the communication schedule is coordinated in response to requests for access to the shared network resource. Furthermore, the circuit section of the device is provided to determine how to allocate the shared network resource based on these received requests.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus and an information processing method, and more particularly, to an information processing apparatus and an information processing method that enable an IoT device to transmit and receive messages to and from a server.

Background Art

[0002] Internet of Things (IoT) devices adopt various communication methods to transmit and receive messages to and from a server. One of them is cellular-based communication. 3GPP (Third Generation Partnership Project) has standardized specific protocols such as CAT-M and NB-IoT as part of LTE (Long-Term Evolution) for Low Power Wide Area Network (LPWAN) communication. These standards feature low throughput, low power consumption, and low cost communication, and are suitable for many IoT use cases.

[0003] Another communication method is device-to-device communication, which is often constructed as part of a device's mesh network. These networks typically utilize unlicensed bands (sub-GHz band or 2.4 GHz band). The protocols for such networks are standardized by the IEEE (Institute of Electrical and Electronics Engineers). For example, the 802.15.4 protocol and the like. Additional protocols such as Wi-SUN and Zigbee are defined on top of the basic protocol.

[0004] In certain cases, IoT devices that integrate both cellular communication and device-to-device communication are constructed by device manufacturers and solution providers. Primarily, the network of IoT devices requires communication with the external world (such as an application server), and cellular-based communication provides a suitable solution due to its widespread coverage and connection capabilities.

[0005] Mesh-based networks that utilize unlicensed bandwidth typically have short communication ranges. However, they consume less power, have lower costs, and do not require payment for connection to cellular networks.

[0006] In a typical mesh network configuration, all leaf devices and router devices have only inter-device modems, while the boundary router that communicates with the outside world has two modems: an inter-device modem and a cellular modem. [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] When a device has two modems that share resources, it needs to address the issue of coexistence. [Means for solving the problem]

[0008] According to one aspect of this disclosure, a novel processing method including a mesh-based communication protocol for IoT devices is described.

[0009] According to a first aspect, the disclosure provides an electronic device as described in independent claim 1. According to a second aspect, the disclosure provides a method as described in independent claim 20. According to a third aspect, the disclosure provides a computer program as described in independent claim 21.

[0010] Other embodiments are described in the dependent claims, drawings, and the following description.

[0011] Each embodiment will be described as an example with reference to the attached drawings. [Brief explanation of the drawing]

[0012] [Figure 1] This is a schematic block diagram of an electronic device having a mesh network and a cellular network. [Figure 2]This involves scheduling unicast and broadcast messages within a mesh network. [Figure 3] This is a diagram illustrating unicast messaging within a mesh network. [Figure 4] This is a diagram illustrating broadcast message scheduling within a mesh network. [Figure 5] This is a diagram illustrating an IoT device integrated into both a mesh network and an LTE network. [Figure 6] This is a block diagram of the electronic device disclosed herein. [Figure 7] This is a flowchart illustrating how scheduling information regarding cellular network communication schedules is received from a cellular modem and how the mesh network is scheduled. [Figure 8] This is a flowchart illustrating a method for calculating a scheduling profile for a mesh network based on the communication schedule of a cellular network in the first embodiment. [Figure 9] This is a flowchart illustrating a method for calculating a scheduling profile for a mesh network based on the communication schedule of a cellular network in a second embodiment. [Figure 10] This is a flowchart illustrating a method for calculating a scheduling profile for a mesh network based on the communication schedule of a cellular network in a third embodiment. [Figure 11] This is a flowchart illustrating a method for calculating a scheduling profile for a mesh network based on the communication schedule of a cellular network in a fourth embodiment. [Figure 12] The coexistence module according to the fifth embodiment of this disclosure enables scheduling of unicast and broadcast messages within a mesh network. [Figure 13]Scheduling of unicast and broadcast messages in a mesh network by the coexistence module according to the present disclosure in the sixth embodiment. [Figure 14] Scheduling of unicast and broadcast messages in a mesh network by the coexistence module according to the present disclosure in the seventh embodiment. [Figure 15] Scheduling of unicast and broadcast messages in a mesh network by the coexistence module according to the present disclosure in the eighth embodiment. [Figure 16] Scheduling of unicast and broadcast messages in a mesh network by the coexistence module according to the present disclosure in the ninth embodiment. [Figure 17] It is a flowchart of a method for calculating a scheduling profile for an LTE network based on the communication schedule of a mesh network in the tenth embodiment. [Figure 18] It is a schematic block diagram of an electronic device capable of implementing the present technology.

Embodiments for Carrying Out the Invention

[0013] Prior to the detailed description of the embodiments with reference to FIG. 1, a general description will be given.

[0014] In this specification, an element or step described in the singular and accompanied by the words "a" or "an" should be understood not to exclude a plurality of elements or steps unless explicitly stated to the contrary. Also, references to "one embodiment" of the present disclosure are not intended to be construed as excluding the existence of additional embodiments that incorporate the described features as well.

[0015] The methods and systems described herein can be implemented using computer programming or engineering techniques that include computer software, firmware, hardware, or any combination or subset thereof. Here, the technical effects may include, at least, enabling essential track references such as asynchronous media and ensuring that conventional players that do not understand the signaling do not attempt to play them.

[0016] A circuit configured to manage a communication schedule within a mesh network or a cellular network in which a mesh modem and each cellular modem of each electronic device according to the present disclosure share at least one network resource. The mesh network operates based on a mesh protocol, the cellular network operates based on a cellular protocol, the management of the communication schedule responds to requests for accessing the shared network resources, and the circuit is further configured to determine how to allocate the shared network resources based on the received requests.

[0017] The above-mentioned electronic device comprises an integrated circuit section and may consist of various components such as a microprocessor, microcontroller, and programmable logic device. These components are specifically programmed to perform the function of managing communication schedules within two different network types: mesh networks and cellular networks. The above-mentioned electronic device connects to the network via a modem configured to connect to each network. Specifically, the circuit section may communicate with a mesh modem connected to the mesh network, or may comprise such a mesh modem. Furthermore, the circuit section may communicate with a cellular modem connected to the cellular network, or may comprise such a cellular modem. The mesh modem and cellular modem utilize at least one shared network resource. This shared network resource may include elements such as a shared antenna, wiring, network interface, bandwidth, frequency spectrum, or designated time slots for data transmission.

[0018] Please understand that, below, shared resources always refer to the shared resources of the mesh modem and cellular modem. However, shared resources may sometimes be referred to as shared resources of the mesh network and cellular network.

[0019] Requests for access to shared network resources can originate from various sources, including applications, mesh networks, cellular networks (LTE), and / or devices within a mesh network or cellular network. Requests can also originate from mesh modems or cellular modems. For the purposes of this disclosure, such electronic devices can be considered part of both cellular and mesh networks. Therefore, requests originating from such electronic devices, or requests relayed or forwarded to such electronic devices from sources not belonging to either a cellular or mesh network, are still considered requests originating from either a cellular or mesh network. These requests can be defined as any communication or signal transmitted to such electronic devices that indicates a need for access to shared resources. Such requests may specify the type of access required, such as immediate access, scheduled access, or periodic access based on operational needs. These requests may also include details such as the resource usage period and specific network functions involved, ensuring that the electronic devices can efficiently allocate shared resources while minimizing conflicts.

[0020] In the spirit of this disclosure, a mesh network is characterized by a topology in which each device receives and / or transmits and / or relays data to the network. All devices in the network cooperate to efficiently distribute data across the network. The network operates under a set of rules known as a mesh protocol.

[0021] In the context of this disclosure, a cellular network operates by using cellular signals to simultaneously transmit information to a large number of external devices within a specific area.

[0022] A cellular network can be, for example, a cellular broadcast network.

[0023] The role of the circuitry within the electronic device described above is to manage the communication schedule. This schedule management is both dynamic and responsive. The circuitry can adjust the schedule based, for example, on real-time requests from any network seeking access to a shared resource. These requests are processed strictly according to the protocols specific to each network type.

[0024] Furthermore, the aforementioned circuitry is responsible for determining how to allocate shared network resources between the requesting networks. This decision-making process takes into account various factors, such as the priority level of the request, the current network load, and other relevant operational parameters. This ensures that resource allocation is carried out in a way that maximizes efficiency and minimizes potential conflicts between the two networks. Through this management and allocation system, the electronic device utilizes shared network resources to improve the performance of data transfer between devices in the mesh network on the server side (e.g., throughput and / or link quality).

[0025] Mesh modems are sometimes referred to as device-to-device modems, and cellular modems are sometimes abbreviated as LTE or 5G modems. The same applies to each network.

[0026] The shared network resources may, in particular, be the radio frequency (RF) antenna used by both modems, or the two modems may share an RF chain and / or a baseband (BB) chain.

[0027] The electronic devices described herein may be referred to as coexistence modules or coex modules. Coexistence refers to a solution that enables both devices to share resources while minimizing the impact on the performance of the devices and the overall network. For example, a device that requires but cannot use shared resources may be unable to receive important messages from its peer device or base station. This could result in a link being broken and the device being disconnected from the network. The impact of this could be more than just message loss.

[0028] However, because network protocols are usually designed to be robust, resource sharing may not negatively impact the network even without applying special coexistence processing to device operation.

[0029] Furthermore, coexistence issues can arise even if the two modems do not share any components, such as RF antennas. For example, even if each modem has its own antenna, if the two antennas are close together, the signal transmission from one modem may interfere with the signal reception of the other modem, even if they are not transmitting on the same frequency.

[0030] The LTE protocol defines several states for a device. First, a device can enter a sleep state. In this state, it is inactive and may be inaccessible from the cellular network. Second, a device can enter Radio Resource Control (RRC) idle mode. In this mode, the device is in an idle (Discontinuous Reception (DRX)) state, mostly in sleep mode, but wakes up periodically to listen for incoming messages from the network. The device wakes up at short intervals in idle DRX and at longer intervals in extended DRX (eDRX). Third, a device can enter RRC connected mode. In this mode, it is connected to a modem and exchanges traffic with a base station. In this mode, the specification defines a continuous DRX (cDRX) mode, which allows the modem to conserve power by entering short sleep periods.

[0031] While many mesh network protocols are based on the IEEE 802.15 4 protocol, they offer alternative communication modes. The following description relates to one form of mesh network implementation based on IEEE 802.15 4, but this disclosure is extendable to other protocols and implementations.

[0032] The envisioned basic mesh protocol could have several characteristics. It operates in non-beacon mode and supports various frame exchanges, including a unicast channel for peer-to-peer information exchange, a broadcast channel for transferring information to all neighboring devices, and an asynchronous channel for transmitting frames related to network configuration and parameters.

[0033] This mesh protocol employs channel frequency hopping, and the hopping sequence and parameters are distributed to all devices. The protocol is receiver-oriented, meaning that devices operate in receive (RX) mode unless transmission is required, and hop according to the channel frequency hopping pattern.

[0034] Because the network is beacon-less, devices need to expose their timing to neighboring devices. This can be achieved by adding a timing offset to some or all messages sent from that device. The hopping pattern can be modified using asynchronous or periodic / other messages. The hopping pattern for broadcast channels overlaps with that of unicast channels, but broadcast channels have higher priority than unicast channels. In a typical implementation, broadcast slots are used less frequently than unicast slots to allow devices to send and receive unicast messages.

[0035] Internet of Things (IoT) devices typically operate in one of two modes. The first mode is user-activated. In this mode, the device is primarily in a sleep state and only wakes up when a host application needs to send a message.

[0036] The second mode is network-activated. In this mode, the device waits for incoming messages. To facilitate waiting for incoming messages, the device intermittently listens to the cellular network (or the parent device in the case of a mesh network) to check for incoming messages. In a cellular network, waiting for incoming messages is achieved by the device waiting in iDRX (idle Discontinuous Reception) mode or eDRX (extended Discontinuous Reception) mode, waking up, and listening for paging opportunities (PO).

[0037] In many cases, scheduling and coordination in mesh networks is simpler than in LTE (Long-Term Evolution). This is because LTE scheduling is defined by base stations in specific activity profiles, whereas in mesh networks, it is defined only by peer devices, specifically the Personal Access Network (PAN) coordinator. Typically, the PAN coordinator is a perimeter router that includes LTE and mesh modems that require coexistence. This disclosure focuses on this approach. However, other solutions are possible and intended within the scope of this disclosure.

[0038] Prioritization is necessary because both modems may attempt to use shared resources simultaneously. For clarity, this disclosure focuses on cases where LTE takes precedence over the mesh network. However, different priority settings are possible. If the mesh network is already actively using shared resources, for example, mid-packet resource processing, LTE will only take over after the mesh network has completed its processing.

[0039] In this disclosure, each modem (mesh and LTE) registers its requests with the aforementioned electronic devices (which may be referred to as coex modules). These requests may include both periodic activities such as iDRX / eDRX wake-ups, and non-periodic activities such as future wake-ups for sending and receiving messages. There may also be unplanned, immediate requests for using shared resources.

[0040] The above electronic device, upon receiving a request, determines how to allocate resources. This determination may include one of the following scenarios:

[0041] Immediate use request for a shared resource: In this case, if the shared resource is available, it will be allocated to the requesting modem. However, if the shared resource is occupied or will soon be occupied, the electronic device will request that one of the modems delay transmission (buffer the message) until the shared resource becomes available again. For example, if a mesh modem is actively using a shared resource, the electronic device will update the LTE modem to wait until the resource becomes available again. This update may be in the form of an interrupt or simply a response indicating a failed use of the shared resource, and the LTE modem will need to poll again when ready. The reverse scenario can also occur: if the LTE modem is using the shared resource, the shared resource use request from the mesh modem will be rejected. This scenario is only relevant to unplanned activity that was not initially foreseen and avoided.

[0042] Scheduled Asynchronous Wake-up: An LTE modem registers to wake up at a specific time to send and receive messages. Additionally, the LTE modem may notify wake-up delay requirements, i.e., the acceptable timing tolerance for requests. Upon receiving such a request, the electronic device adjusts the LTE modem's wake-up time to meet the delay requirements and sends the result back to the LTE modem accordingly. The electronic device may also instruct the LTE modem to modify its scheduling profile (update its peers) before waking up to minimize the impact on LTE and mesh protocols. Once the LTE modem has woken up, used the shared resources, and gone back to sleep, the electronic device instructs the mesh modem to update its scheduling profile again.

[0043] Scheduled Synchronized Wake-up: The LTE modem shares its periodic activity (eDRX / iDRX, etc.) with the aforementioned electronic devices. The aforementioned electronic devices instruct the mesh modem to modify its scheduling profile (and update its peers) to minimize interference with the LTE modem's periodic wake-up.

[0044] The following presents various alternatives to minimize RF sharing problems by adjusting the scheduling profiles of mesh network devices. Note that these alternatives merely present various possible embodiments, and the scope of the patent is not limited to these alternatives.

[0045] The first option is to indicate channels that are unavailable during normal operation. Boundary routers distribute a roster of frequency channels used for communication along with a channel hopping sequence. Certain protocols allow changes to the channel list to accommodate dynamic operation in scenarios limited by interference. For example, it may be possible to temporarily mask specific frequency channels identified as being affected by interference, while allowing the use of the remaining frequency channels. Similar mechanisms may be applied to coexistence solutions.

[0046] As a second option, the boundary router may have the ability to signal its unavailability via asynchronous messages. These messages are used to enable, disable, or replace frequency channel lists. When a frequency is marked as unavailable, peer devices receive information that the boundary router will be unavailable during that time period. However, frequency channel slots must not be skipped.

[0047] This signaling can be implemented as a dedicated message or by modifying the existing message format (e.g., by using reserved bits). Depending on the implementation, this signaling may disable both broadcast and unicast.

[0048] A simpler way to indicate unreachability is to change the channel frequency to one that is invalid for the peer device. "Invalid" means a frequency that the peer device cannot use, implying that communication with the boundary router will be impossible.

[0049] A third option is to indicate unreachability. In this case, the boundary router sends a specific signaling to the peer device regarding the period of unreachability. Upon receiving this signaling, the peer device understands that it will not attempt to send or communicate with the boundary router during the defined period. The peer device can continue communicating with other peer devices without any changes. This can be achieved in several ways:

[0050] The first method involves sending a bit=1 via an asynchronous message to indicate that the boundary router is unreachable. When it becomes active again, the bit changes to 0 and is exposed via an asynchronous message.

[0051] The second method involves the boundary router sending an indication of the expected duration of unreachability.

[0052] A third method involves sending an indication of a periodic time interval during which the device will be unreachable.

[0053] For example, embedding a message in the mesh protocol to indicate a 100-millisecond disconnection period every 81.92 seconds improves efficiency compared to a scenario where the coordinator switches between b=1 and b=0 for each eDRX cycle.

[0054] Additionally or alternatively, the frequency hopping channel profile can also be modified. In this case, the frequency hopping channel profile is updated to minimize the possibility of the border router losing unicast messages when the LTE modem is using shared resources.

[0055] In the context of this disclosure, frequency hopping is achieved by a device dynamically changing the receiving channel over different time periods. This dynamic change is not random, but follows a specific sequence known as a hopping sequence. Alternatively, a preliminary messaging protocol may be incorporated to inform peer devices of the frequency hopping pattern (FHP).

[0056] The device can generate a pseudo-random channel sequence based on its extended address, making it a device-specific sequence. This means that each device in the network hops or switches between channels based on its own unicast channel hopping sequence.

[0057] In addition to unicast hopping, broadcast transmission is also supported by frequency hopping characteristics. To enable broadcast transmission, the network coordinator initiates a broadcast schedule. Subsequently, all other devices in the network follow the broadcast hopping sequence received from the coordinator.

[0058] A fourth method of indicating unavailability is to modify the broadcast profile. Unlike other methods, this method specifically blocks unicast messages while allowing broadcast messages to be sent without being received by boundary routers. This method selectively restricts unicast communication, ensuring that broadcast transmission continues across the network, even though reception at boundary routers does not occur.

[0059] Changes to the broadband scheduling profile may affect other devices in the network, depending on the protocol and implementation, potentially requiring these devices to update their broadcast scheduling. To prevent this, a boundary router can notify peer devices that the profile change applies only to itself. This indicates that the boundary router is currently unable to support mesh communication. This notification can be made in the form of an additional message or by utilizing spare or new bits in messages used by the current mesh protocol.

[0060] Additionally, the disclosure method may result in the loss of broadcast messages, which are typically used to notify of changes within the network. To mitigate the loss of broadcast messages, the coexistence module of a boundary router may request that peer devices send a solicit request after the shared resource has been released, asking them to expose the latest routing state.

[0061] Numerous cases can be distinguished by specific examples. Below, we present variations of the broadcast channel profile to align with various LTE activation profiles. These variations are designed to harmonize with different LTE operational profiles. Additionally, these adaptations to activity profiles can also be carried out using the methods 1 to 4 described above.

[0062] Case 1: eDRX / iDRX Wake-up. Here, the goal is to adjust the broadcast channel to overlap with the LTE wake-up period. For the record, the broadcast channel has higher priority than the unicast channel. During the broadcast channel time slot, all devices must listen on the broadcast channel and not the unicast channel. By overlapping the broadcast time slot with the LTE wake-up period, the perimeter router is expected to listen only on the broadcast channel and not the unicast channel. The motivation for this is that it is safer for the perimeter router to lose broadcast messages than unicast messages. Also note that the perimeter router will only lose broadcast messages sent in the time slot that overlaps with the wake-up period. Other time slots will still be received by the perimeter router's mesh modem.

[0063] Case 2: LTE in connection mode. Here, the LTE modem holds the shared resource for an extended period. Similar to Case 1, the goal is to prevent the boundary router from losing the unicast channel. In this mode, the broadcast channel slot period and duration are configured to be the same. This effectively creates a scenario where only broadcast messages can be received during that time period.

[0064] Case 3: LTE in cDRX state. This case is a more complex scenario where the LTE modem transitions from a connected state to a cDRX period. The same concepts as above (i.e., Cases 1 and 2) apply.

[0065] Furthermore, iDRX, eDRX, and cDRX allow for the configuration of periodic routines to cause devices to become unreachable within the mesh network. On the other hand, in connected mode, a single extended period of unreachability may be required. Methods for achieving this unreachability (including broadcast channel manipulation, specific messaging, and other techniques) have already been described.

[0066] However, it should be noted that cases 1-3 above should be considered as specific examples for realizing this disclosure, and are not limiting. Multiple methods can also be combined.

[0067] In some embodiments, the above request is received from at least one of the application or the transport layer protocol module.

[0068] The application may be a software program or a group of programs that runs on a processing unit that may be included in the above-mentioned electronic device. The processing unit may also be part of a device that includes the above-mentioned electronic device.

[0069] The transport layer protocol module can be a software component within a processing unit and handles communication protocols at the transport layer of the Open Systems Interconnection (OSI) model. The transport layer protocol module can manage protocols such as the User Datagram Protocol (UDP) and the Transmission Control Protocol (TCP).

[0070] This processing unit may be a processing unit for the electronic device described above, or a processing unit for an apparatus including the electronic device described above. The processing unit may run an application that may be an application that transmits requests in the spirit of this disclosure, and may include a transport layer protocol module.

[0071] In some embodiments, the above request is received from at least one of the following: the mesh modem, the peer device in the mesh network, or the cellular modem or remote device in the cellular network, according to their respective network protocols.

[0072] The source of the request may be any of the sources described above. In other words, in all embodiments described herein, the request may be received from an application, a transport layer protocol module, a mesh modem, a peer device in a mesh network, a cellular modem, or a remote device in a cellular network.

[0073] In some embodiments, the communication schedule is controlled so that the mesh network does not access the shared network connectivity resources, while the cellular network does. This ensures that the two networks operate without interfering with each other by alternating access to the shared resources.

[0074] The circuitry of the device monitors the current usage status of shared resources using a programmed algorithm and dynamically adjusts access rights for each network based on that status. This dynamic scheduling function allows each network to operate with optimal efficiency without interfering with each other. Optimization can be performed not only individually for each network but also collectively. The need for end-to-end packet transmission (e.g., from a leaf device to a server via a boundary router) is considered, and shared resource management at the boundary router may be required to ensure that packets pass through as smoothly as possible.

[0075] By effectively managing resources, the electronic devices ensure that both mesh networks and cellular networks can effectively perform their functions and reliably provide communication services within their respective protocols.

[0076] In some embodiments, the control includes sending a scheduling request to all peer devices connected to the mesh network, and in response to the scheduling request, the peer devices refrain from sending and / or receiving information to and from the mesh modem on a predetermined channel for a duration specified in the scheduling request.

[0077] This control may include scheduling requests sent to all peer devices that are part of the mesh network. The purpose of these scheduling requests is to instruct peer devices to temporarily stop transmitting information to the mesh modem on a given channel. The period during which the peer devices should refrain from transmitting is explicitly specified in the scheduling request.

[0078] Communication scheduling control may be defined to include not only cases where specific restrictions are imposed or periods of unavailability are set, but also the opposite. Specifically, control may include scheduling of permitted or available periods for communication. In this way, the electronic device can clearly define the areas and times in which communication is permitted or possible.

[0079] In some embodiments, the predetermined channel is at least one of a unicast channel or a broadcast channel.

[0080] This control may include sending scheduling requests to all peer devices in the mesh network and instructing the peer devices to temporarily stop transmitting information to the mesh modem on a given channel.

[0081] A unicast channel is used for direct communication between two specific devices, allowing data to be sent directly from one device to the other. A broadcast channel is used to send data simultaneously from one device to all other devices in the network.

[0082] The ability to designate either a unicast channel or a broadcast channel as a given channel provides flexibility in network management. This allows the network to adapt to changing communication needs while maintaining efficiency and stability.

[0083] In some embodiments, the predetermined channel includes both a unicast channel and a broadcast channel, and all of the broadcast channel and peer devices are configured to receive and / or transmit on both the broadcast channel and the unicast channel for a duration specified in the scheduling request.

[0084] This control may include sending scheduling requests to all peer devices in the mesh network, instructing them to temporarily suspend the transmission of information to the mesh modem on a given channel, which may include both unicast and broadcast channels.

[0085] The above electronic devices manage the configuration so that the mesh network can maintain a high level of operational consistency and responsiveness even when coordination of transmission activities is required.

[0086] In some embodiments, the predetermined channel is the unicast channel only, and all of the peer devices are configured to receive and / or transmit only on the broadcast channel for the duration specified in the scheduling request.

[0087] This control may include sending scheduling requests to all peer devices in the mesh network, instructing them to temporarily suspend the transmission of information to the mesh modem on a given channel (which may be a unicast channel in some embodiments).

[0088] In some embodiments, the predetermined channel is a broadcast channel, and all of the peer devices are configured to receive and / or transmit only on the broadcast channel for the duration specified in the scheduling request.

[0089] The above-described electronic device comprises an integrated circuit that manages communication within a mesh network by controlling the transmission activity of peer devices. This control may include sending scheduling requests to all peer devices in the mesh network and instructing them to temporarily suspend the transmission of information to the mesh modem on a predetermined channel (which may be only a broadcast channel).

[0090] In some embodiments, the predetermined channel is a channel that is neither a unicast channel nor a broadcast channel, and all of the peer devices are configured to receive and / or transmit on the channel that is neither a unicast channel nor a broadcast channel for a duration specified in the scheduling request.

[0091] A channel that is neither a unicast channel nor a broadcast channel can be any communication channel specifically provided to facilitate communication between a mesh modem and a peer device when neither a broadcast channel nor a unicast channel is available.

[0092] In some embodiments, the cellular protocol is the LTE protocol, and the duration corresponds to the period during which the LTE modem is active.

[0093] The management of communication schedules within the network is aligned with the LTE wake-up period. The LTE wake-up period is a specific time when the LTE network is activated to perform necessary communications and data transfers.

[0094] In the context of this disclosure, the LTE wake-up period is a predefined duration during which LTE network components are active for sending and receiving data.

[0095] In some embodiments, the cellular protocol is the LTE protocol, and the duration corresponds to the cDRX connection period and / or the eDRX period and / or the iDRX period.

[0096] According to this disclosure, the management of communication schedules within the network is configured to align with the cDRX (Continuous Discontinuous Reception), eDRX (extended Discontinuous Reception), or iDRX (idle Discontinuous Reception) periods defined in the LTE protocol.

[0097] The cDRX connection period is the interval during which LTE network components actively participate in sending and receiving data.

[0098] In the context of this disclosure, the duration specified in a scheduling request for managing access to a shared network resource may correspond to the cDRX connection duration.

[0099] The above circuitry may be configured to dynamically adjust the communication schedule based on the requirements of the LTE protocol and the specific timing of the cDRX connection period. This may include temporarily restricting or allowing access to shared network resources in order to synchronize with the activity period of the LTE network.

[0100] In some embodiments, the scheduling request is broadcast to the peer device via a broadcast message.

[0101] Asynchronous broadcasts are broadcasts that are transmitted independently of the normal communication schedule. Inclusion may also be considered when scheduling requests are sent via synchronous broadcast or unicast channels.

[0102] Scheduling requests typically involve instructing peer devices to temporarily suspend information transmission on a designated channel, which may be a unicast or broadcast channel depending on the network configuration and requirements. Managing communication schedules may include not only suspending transmission on specific designated channels, but also adjusting timing profiles (such as shifting time or extending duration).

[0103] The above circuitry is configured to process asynchronous broadcasts and manage responses from peer devices. This includes monitoring compliance with scheduling requests and adjusting the communication schedule accordingly to maintain network stability and efficiency.

[0104] In some embodiments, the scheduling request is sent to the peer device via a direct unicast.

[0105] This control may include sending scheduling requests to all peer devices in the mesh network.

[0106] Direct unicast can include sending scheduling requests individually to each peer device, rather than broadcasting the scheduling request to all devices simultaneously.

[0107] By utilizing direct unicast for sending scheduling requests, electronic devices ensure that critical network management commands are effectively transmitted to each device in the mesh network.

[0108] In some embodiments, the shared network resource is at least one of the following: data transmission means, antennas or network lines, network connection interfaces, radio frequency (RF) chains, digital front-ends, analog front-ends, baseband processors, or modulation / demodulation units.

[0109] In the spirit of this disclosure, an antenna can be any component for wireless communication that facilitates the transmission and reception of wireless signals between devices in a network. In the spirit of this disclosure, a network line can be any physical means of transmission typically used in wired connections that provides a physical medium for data transmission. A network connection interface can be a hardware or software component, such as a network card or a software-defined network interface, that manages the interaction between any device and network. This network connection interface can be any such component suitable for handling data packet processing and transmission control.

[0110] In some embodiments, the electronic device is further configured to send update requests to mesh modems connected to a mesh network to update mesh scheduling parameters and to receive scheduling information regarding cellular network communication schedules from cellular modems connected to a cellular network.

[0111] Specifically, the device is configured to interact directly with the network modem, facilitating the updating and synchronization of network schedules.

[0112] The device sends an update request to a mesh modem, which is part of the mesh network. This update request is intended to change or adjust mesh scheduling parameters, and may include adjustments to transmission times or other scheduling aspects to optimize the performance of the mesh network on shared network resources.

[0113] The device is configured to receive scheduling information from a cellular modem, which is part of a cellular network. This scheduling information includes details about the cellular network's communication schedule, such as time slots allocated for broadcasts, communication priority levels, and other relevant scheduling details to properly coordinate the use of shared resources and the operation of the cellular network.

[0114] Additionally, scheduling information may also be received from the application or the host. For example, an application that wakes up every 24 hours to send messages via LTE (Long-Term Evolution) can update the coex module for this expected wake-up. From an implementation standpoint, scheduling information may be transmitted directly from the host to the coex module, or from the LTE modem to the coex module. In certain cases or implementations, the LTE modem may not be aware of when the application is scheduled to wake up, so a direct update from the host or application to the coex module may occur.

[0115] By performing the dual functions of sending update requests to mesh modems and receiving scheduling information from cellular modems, the aforementioned electronic device can function as a central hub for coordinating both networks.

[0116] In some embodiments, the control includes calculating a scheduling profile for the mesh network based on the communication schedule of the cellular network and sending the update request based on the scheduling profile.

[0117] The calculation of a scheduling profile can include an analysis of the cellular network's communication schedule, including the timing, frequency, and priority of broadcasts within the cellular network. Using this information, the device calculates a scheduling profile for the mesh network.

[0118] Once the mesh network scheduling profile is established, devices can send update requests to the mesh modems. These update requests include new scheduling parameters that need to be implemented within the mesh network to align the mesh network's operation with the cellular network's schedule.

[0119] In some embodiments, in response to the update request, the mesh modem sends scheduling profile update information to at least one peer device connected to the mesh network.

[0120] The update request prompts the mesh modem to send scheduling profile update information to at least one peer device in the mesh network.

[0121] Upon receiving an update request, the mesh modem processes the information and compiles scheduling profile update information containing the modified scheduling parameters that peer devices in the mesh network must adopt. The mesh modem then distributes the scheduling profile update information to at least one peer device in the network.

[0122] The distribution of scheduling profile update information ensures that all peer devices in the network synchronize their operations and follow a unified communication schedule. This reduces conflicts and optimizes the use of shared network resources.

[0123] In some embodiments, the communication schedule is controlled so that the cellular network does not access the shared network connectivity resource, while the mesh network does access the shared network connectivity resource.

[0124] This control can include scheduling specific time slots or periods during which only mesh modems can utilize shared resources, preventing overlap in resource usage with the cellular network. This approach minimizes contention or interference between mesh modems and cellular modems in the use of shared resources.

[0125] The communication scheduling method manages communication schedules within a mesh network or cellular network that both share at least one network resource, wherein the mesh network operates based on a mesh protocol and the cellular network operates based on a cellular protocol, and the management of the communication schedules responds to requests for access to the shared network resource received from either the mesh network or the cellular network according to their respective protocols, and determines how to allocate the shared network resource based on the received request.

[0126] The above communication method may include managing the communication schedules of mesh networks and cellular networks. Both networks utilize at least one shared network resource.

[0127] The above method includes responsive management of communication schedules. This management is coordinated based on requests for access to shared network resources from either network. These requests are processed according to the specific protocols of each network, ensuring compliance with each network's operational guidelines. The above method includes a decision-making process regarding the allocation of shared network resources. This process determines how best to distribute or allocate resources between the two networks, taking into account received requests, optimizing resource utilization, and preventing conflicts.

[0128] In some embodiments, the methods described herein are also implemented as computer programs that cause a computer and / or processor to perform the methods when executed on a computer and / or processor. In some embodiments, a non-transient computer-readable recording medium is also provided. This non-transient computer-readable recording medium stores a computer program product that, when executed by a processor such as the aforementioned processor, causes the methods described herein to be performed.

[0129] Figure 1 shows a schematic diagram of IoT device 1000B to which the technology described herein can be applied.

[0130] The IoT device 1000B comprises an application layer module 1100, a UDP / TCP module 1200, and a communication module 1300. The communication module 1300 comprises an LTE modem 1310 and a mesh protocol modem 1320.

[0131] The LTE modem 1310 comprises a data buffer 1311, an IP (Internet Protocol) module 1312, a PDCP (Packet Data Convergence Protocol) module 1313, an RLC (Radio Link Control) module 1314, a MAC (Medium Access Control) module, and a PHY (Physical Access Control) module 1315. The LTE modem shown in Figure 1 can generally be a known LTE modem.

[0132] Buffer 1311 is the data storage unit. IP module 1312 handles the modem's IP functions. IP module 1312 manages IP packet encapsulation and decapsulation, IP addressing, and routing. PDCP module 1313 manages header compression and decompression, encryption and decryption, and the integrity of user data and control plane data. RLC module 1314 handles data packet splitting and reconfiguration, error correction by retransmission, and sequential delivery of packets. MAC module 1315 is responsible for multiplexing and demultiplexing of logical channels into transport blocks, scheduling decisions, and dynamic resource allocation. PHY module 1316 handles physical layer procedures, including modulation and demodulation, encoding and decoding, and MIMO (Multiple Input Multiple Output) processing.

[0133] The LTE modem 1310 may be implemented as a hardware component within the electronic device described above, or as a software module executed by the processor within the device. It interacts with other components of device 1000B, such as the application module 1100 or the UDP / TCP module 1200.

[0134] In an alternative embodiment, UDP / TCP 1200 can be integrated into either an LTE modem 1310 or a mesh modem 1320 to facilitate direct processing of data packet transmission and reception.

[0135] The LTE modem 1310 enables data transmission and reception based on the LTE standard.

[0136] The mesh modem 1320 shown in Figure 1 manages the operation of wireless or wired communications based on a mesh network standard (e.g., IEEE 802.11s).

[0137] The mesh modem 1320 facilitates data communication between IoT device 1000B and other devices in the mesh network by, for example, converting digital data from device 1000B into a format suitable for wireless transmission according to a predefined or pre-selected standard, and vice versa. The mesh modem 1320 establishes and maintains connectivity with the mesh network, manages data transmission and reception, and handles error detection and correction. This ensures that data packets are correctly destined on the network and routed to their intended destinations.

[0138] The mesh modem 1320 includes a buffer 1321, an IP module 1321, a Logical Link Control (LLC) module 1323, a MAC module 1324, and a PHY module 1325.

[0139] Buffer 1321 is a data storage unit. IP module 1322 handles the IP functions of the mesh modem 1320. This IP module 1322 manages IP packet encapsulation and decapsulation, IP addressing, and routing. LLC module 1323 can be responsible for error control, flow control, frame synchronization, and routing. MAC module 1324 manages the multiplexing and demultiplexing of logical channels to transport blocks, scheduling decisions, and dynamic resource allocation. PHY module 1325 handles physical layer procedures, including modulation and demodulation, coding, and decoding.

[0140] The mesh modem 1320 manages the device's access to network resources. The mesh modem 1320 can be implemented as a hardware component within the IoT device 1000B or as a software module executed by the processor within the device 1000B. This mesh modem 1320 interacts with other components of the device 1000B, such as the application module 1100 or the UDP / TCP module 1200.

[0141] In the IoT device 1000B shown in Figure 1, the LTE modem 1310 is connected to the first antenna ANT1, and the mesh modem 1320 is connected to the second antenna ANT2.

[0142] Figures 2 and 3 show schematic diagrams of the broadcast and unicast reception schedules for a mesh network. This scheduling includes both sending and receiving broadcast and unicast messaging, but Figure 2 only shows the reception window.

[0143] In the context of the mesh network connection schedule shown in Figure 2, two main data transmission modes are employed: broadcast and unicast.

[0144] Broadcast refers to the transmission of data from one device to all other devices on a network. In this mode, if a device has data to send, it will simultaneously send that data to all other devices on the network.

[0145] Unicast refers to the transmission of data from one device to a specific other device within a network. In this mode, data is sent from the source device to the destination device by following a specific path within the network. The path is determined using various routing algorithms that take into account factors such as the number of hops, link quality, and network congestion. Unicast is typically used for point-to-point communication to send data intended for a specific recipient.

[0146] In the context of this disclosure, the mesh modem 1320 within the device is configured to support both broadcast mode and unicast mode transmission.

[0147] The broadcast and unicast messages shown in Figure 2 are scheduled along a time axis. The first column of the unicast block (e.g., UA-1 to UA-3) indicates the time when a first device A, which is part of the mesh network, listens for messages transmitted by second and third devices B and C, which are also part of the mesh network. The second column of the unicast block (e.g., UB-1 to UB-3) indicates the time when a second device B listens for messages transmitted by second device A and third device B. The third column of the unicast block can be transmitted by second device B, and the third column of the unicast block (e.g., UC-1 to UC-3) can be received by third device C.

[0148] Additionally, transmit-oriented protocols utilizing beacons may be implemented, but these are not shown in the current diagram. These protocols facilitate structured data transmission by notifying that a network for transmitting data exists and is ready.

[0149] Unicast blocks (e.g., UA-1 to UA-3) indicate the frequency channels that a device (e.g., device A) monitors. Each device receives only on specific frequencies. For example, if device A wants to communicate with device B, device A must send a message (Tx in Figure 3) on that channel during the time when device B is listening on that channel. For example, as shown in Figure 3, while device B is monitoring device A's frequency (unicast block UB-2), device A receives a message Tx from device B. That is, the transmission (TX) is performed on the channel that device B is tuned to.

[0150] In the context of this disclosure, the broadcast offset (as shown in Figure 2) refers to the time delay before the start of broadcast transmissions B-2, B-0, and B-1. The broadcast duration (as shown in Figure 2) is the time interval during which broadcast transmissions B-2, B-0, and B-1 are continuous. The broadcast period (as shown in Figure 2) is the time interval between consecutive broadcast transmissions B-2, B-0, and B-1. The unicast slot duration refers to the time interval during which a device listens for any unicast messages received from any peer device (e.g., UA-1 to UA-3) on a particular frequency channel.

[0151] Figure 4 shows an additional schematic diagram of the broadcast schedule for a mesh network. As shown in the figure, messages can be broadcast on all frequency channels to ensure that all devices in the network receive them. Alternatively, messages can be sent on specific channels during specific broadcast intervals. Devices in the network can also send notification messages at a minimum rate (arrows labeled 0, 1, 2, and 3 in Figure 4) to allow new devices to join the network.

[0152] Because the device sends messages asynchronously, and each peer device may be tuned to a different frequency channel, the device needs to broadcast on all frequency channels. This is indicated by multiple arrows, each indicating that device A is sending messages on a different frequency channel. This method ensures that broadcast messages are received by all devices, including those operating with unicast scheduling. Asynchronously sendable announcement messages also serve to update network parameters or settings, including frequency channel settings.

[0153] Figure 5 is a conceptual diagram of the interaction between the mesh network 300 and the cellular network 400. In the context of this disclosure, any network topology type (including, but not limited to, a tree topology where direct connections exist between devices A and B) is considered a mesh network. In this particular example, only the boundary router 1000A has access to the “outside world,” for example, via the LTE antenna 410. However, it should be noted that in a real-world scenario, additional devices (e.g., devices A, B, and C) may also have similar access and become part of the LTE network 400. For simplicity, in this example, we assume that access to the outside world is facilitated via the boundary router 1000A, which also acts as the coordinator of the mesh network 300. In terms of resource sharing, only devices that can communicate directly with the boundary router 1000A (i.e., devices A, B, and C) are considered relevant. This is because, once the LTE modem 1310 takes over control of the resources, the boundary router 1000A loses its ability to communicate with its peer devices (devices A, B, and C). Please note that the description of the mesh network, including peer devices A, B, and C, is for illustrative purposes only and should be understood as non-exclusive. The number of peer devices is arbitrary.

[0154] Figure 6 shows a schematic diagram of the electronic device 1000 according to this disclosure. The device 1000 comprises an application module 1100, a UDP / TCP module, an LTE modem 1310, and a mesh protocol modem 1320, as well as a coexistence module 1330.

[0155] The coexistence module can be provided as part of the communication module 1300.

[0156] The coexistence module 1330 includes a processing module 1331 that performs processing of LTE / mesh and application parameters based on information 1352 and information 1353 received from the LTE modem 1310. Additionally, as indicated by the arrows, information from the application layer module 1100 may be incorporated into the scheduling process.

[0157] The coexistence module 1330 includes a scheduling module 1332 that schedules and updates LTE / mesh parameters and transmits update information 1350 and 1351 to the LTE modem 1310 and the mesh protocol modem 1320, respectively. Note that both modems are connected to the same antenna (ANT3). This indicates the need for resource sharing.

[0158] Figure 7 shows a schematic diagram of the scheduling and update process performed by the boundary router 1000A according to this disclosure. The following steps are performed in the time order shown. However, it should be noted that the time axis only shows the qualitative relationship between the individual process steps. This process may include a provision step S11 in which a channel scheduling profile is sent by the boundary router 1000A to the coexistence module 1330; a first update step S12 in which the LTE modem 1310 provides the coexistence module with update information regarding scheduled wake-ups; a first calculation step S13 in which the coexistence module 1330 calculates a new scheduling profile based on the scheduling profile provided by the boundary router 1000A and the wake-up schedule provided by the LTE modem 1310; a first request step S14 in which the coexistence module 1330 sends a request for scheduling parameter updates to the boundary router 1000A; and a first peer update step S15 in which the boundary router 1000A updates the mesh peers 2000 in the mesh network 300 with the new scheduling parameters. Furthermore, the boundary router 1000A can be replaced with a mesh modem 1320.

[0159] Furthermore, any of the aforementioned steps may be performed based on a schedule, or in response to the completion of a previous step or a request to perform that step.

[0160] This sequence is repeated in steps S16 through S19 and can then be continued as needed.

[0161] Figure 8 shows a schematic diagram of the scheduling and update process performed by the boundary router 1000A and the coexistence module 1330 according to one embodiment. The coexistence module 1330 shown in Figure 8 may be part of the boundary router 1000A, or it may be provided as a separate module.

[0162] The scheduling and update process may include the coexistence module 1330 instructing the boundary router 1000A to become unavailable for a predetermined period in the instruction step S21. In response, the boundary router 1000A notifies the peer devices 2000 of the mesh network 300 of its unavailability in the notification step S22. The boundary router then enters an inactivity period P1. After the inactivity period P1, the boundary router 1000A updates the peer devices 2000 with a new scheduling profile in the update step S23. In an optional notification step S24, the boundary router 1000A confirms its active status with the coexistence module 1330. After step S24, the boundary router 1000A can resume normal communication between the mesh peer devices 2000 and the boundary router 1000A.

[0163] As a specific, non-limiting example, a new scheduling profile can be implemented by providing a new list of frequency channels. Additionally, scheduling profiles can be modified by changing broadcast and unicast channel settings, adjusting message transmission timing, or changing the frequency hopping pattern as described above.

[0164] Furthermore, instruction step S21 may include receiving an instruction to make the boundary router 1000A unavailable for a specific period [t0…t1]. This is because the shared resources will be unavailable during that time.

[0165] Notification step S22 may include the boundary router 1000A sending an announcement message to all peer devices 2000, updating the scheduling profile used by the boundary router 1000A to "empty". This implies that the boundary router 1000A is unreachable.

[0166] During the inactivity period P1, the boundary router 1000A is unable to send or receive messages. The mesh peer device 2000 can optionally indicate that it cannot communicate with the boundary router 1000A during this period.

[0167] The update step S23 may include sending an announcement message to all peer devices 2000 along with the updated scheduling profile used by the boundary router 1000A. The list is not empty, indicating that the boundary router 1000A is now reachable.

[0168] The optional confirmation step S24 may include the boundary router 1000A sending a message back to the coexistence module 1330 confirming that it is active again.

[0169] Figure 9 shows a schematic diagram of the scheduling and update processes performed by the boundary router 1000A and the coexistence module 1330 in another embodiment.

[0170] This process may include an instruction step S81, a notification step S82, an unavailability period P1, and an optional confirmation step S83.

[0171] In instruction step S81, the boundary router 1000A receives an instruction from the coexistence module 1330 to become unavailable for a specific period [t0…t1] due to the unavailability of the shared resources.

[0172] In notification step S82, a notification message is sent to all mesh peer devices 2000 indicating that the scheduling profile used by the boundary router 1000A is "empty". This implicitly notifies that the boundary router 1000A is unreachable.

[0173] During the unavailability period P1, the boundary router 1000A will be unable to send or receive messages. The mesh device 2000 will be able to recognize that communication with the boundary router is impossible.

[0174] The optional confirmation step S83 may include the boundary router 1000A sending a message back to the coexistence module 1330 confirming that it is active again.

[0175] In the embodiment shown in Figure 8, the boundary router notifies the mesh peer 2000 of the end of the unavailability period P1 by sending an intentional availability notification (S23 in Figure 8), whereas in the embodiment shown in Figure 9, the device is notified that the unavailability period will continue for a predetermined time (i.e., from t'0 to t'1).

[0176] Figure 10 shows a schematic diagram of the scheduling and update processes performed by the boundary router 1000A and coexistence module 1330 in another embodiment.

[0177] The scheduling and update process may include a first notification step S31, a first announcement step S32, an optional update step S33, multiple unavailability periods P2, an interval end step S34, a second notification step S35, and an optional confirmation step S36. Thereafter, normal peer-router communication resumes.

[0178] In the first notification step S31, the coexistence module 1330 notifies the boundary router 1000A of a scheduled unavailability period P2, including periodicity and interval length (e.g., during the eDRX period).

[0179] In the first notification step S32, a notification message is sent to all peer devices 2000, which updates the frequency hopping channel scheme to match the unavailability period P2 requested by the coexistence module 1330.

[0180] In the optional update step S33, the coexisting module 1330 is optionally updated during the unavailable period P2.

[0181] During the unavailability period P2, attempts by peer device 2000 to send a message to boundary router 1000A will fail if its time slot is occupied by LTE modem 1310. On the other hand, attempts to send unicast messages will succeed. The unavailability period can be aligned with the periodic active time slots of LTE. More specifically, broadcast channels can be aligned with eDRX periods, and shared resources can be occupied during these periods. Period P2A shown in Figure 10 is aligned with the unavailability period P2.

[0182] If an unavailable state is communicated with explicit information (e.g., a bit=1 setting), all peer devices will recognize that the border router is inactive. Similarly, if the border router marks a group of channels (and their corresponding time slots) as inactive, peer devices will understand that they cannot communicate with the border router during those time slots.

[0183] If no unavailability notification is received, the boundary router leverages the protocol's broadcast slot priority over unicast slots. During a broadcast slot, all devices listen on the broadcast frequency channel and do not listen on unicast. Therefore, during this period, unicast messages cannot be sent or received with any device, but broadcast messages can be sent to all other devices.

[0184] For example, if a boundary router changes its scheduling profile to continuously allocate broadcasts, this effectively informs all devices that unicast messaging is inaccessible. In this scenario, all devices will refrain from sending unicasts to the boundary router, but may attempt to reach broadcasts if they exist.

[0185] In the interval completion step S34, the shared resources become fully available to the boundary router 1000A, as notified by the coexistence module 1330.

[0186] In the second notification step S35, the boundary router 1000A sends a notification message to all peer devices 2000 using the updated frequency hopping channel scheme.

[0187] In optional confirmation step S36, the boundary router 1000A sends a message to the coexistence module 1330 to confirm that it is "fully" active again.

[0188] Figure 11 shows a schematic diagram of the scheduling and update processes performed by the boundary router 1000A and coexistence module 1330 in another embodiment.

[0189] The scheduling and update process may include an instruction step S41, a first request step S42, an optional update step S43, an unavailability period P3, a second request step S44, and an optional confirmation step S45. Thereafter, normal peer-router communication resumes.

[0190] In instruction step S41, the boundary router 1000A is instructed to become unavailable for a specific period [t0…t1] due to the unavailability of the shared resources.

[0191] In the first request step S42, an announcement message is sent to all peer devices 2000, and the broadcast frequency channel scheme is updated. The frequency channel scheme is configured so that the boundary router 1000A listens only on the broadcast channel. This indicates to the mesh peers 2000 that communication via the unicast channel is not possible. Attempts to send information via the broadcast channel will fail if the boundary router 1000A's shared resources are occupied by LTE. Furthermore, it should be noted that peer devices may attempt to send broadcast messages but not unicast messages, and this will fail.

[0192] In the optional update step S43, the boundary router updates the unavailability period P3 for the coexistence module 1330.

[0193] In the second request step S44, the boundary router 1000A sends an announcement message to all peer devices 2000 to update the broadcast frequency channel scheme to the previous configuration or another configuration.

[0194] In optional confirmation step S45, the boundary router 1000A optionally sends a message back to the coexistence module 1330 to confirm that it is "fully" active again.

[0195] Note that the options shown in Figures 7 to 11 are only some examples of how boundary routers can communicate unreachable states to peer devices. Numerous other options exist for implementing this technology, and these may include combinations of different options.

[0196] In any of the embodiments shown in Figures 7, 8, 9, 10, and 11, any of the methods described above can be applied to the scheduling management of the mesh network. Mesh scheduling management is not limited to the specific methods applied in each embodiment. For periodic activities such as eDRX / iDRX wake-up, the system may implement methods such as setting bit=1 to indicate unavailability, or prohibiting specific frequencies during active LTE periods. For non-periodic activities, adjustments may include modifying the broadcast schedule or changing the frequency hopping sequence. The mesh protocol may provide solutions such as setting bit=0 to indicate the resumption of availability, employing frequency bars to restrict mesh device access during LTE activity, or adjusting broadcast messages to maintain mesh network communication without interfering with LTE operations.

[0197] Figure 12 shows a schematic scheduling of the mesh network 300 according to one embodiment. This scheduling can be used in combination with the embodiment shown in Figure 7 or 8 above.

[0198] As shown in Figure 12, the mesh modem 1320 can be configured to support a scheduled broadcast period B-0. The scheduling of the unicast period U-0 can be calculated based on the present disclosure in Figure 7 or Figure 8, where the mesh modem 1320 is configured to support a scheduled unicast period U-0.

[0199] In the context of the process described above, the boundary router 1000A transmits update information, specifically indicating a message unreceivable state. This update information is transmitted during one or more time slots BU-1, which may correspond to the LTE connection period CM, instructing the boundary router 1000A to become unavailable for a specific duration S-0 (which may correspond to period P1 in Figure 8). During this period, the boundary router 1000A does not monitor or listen on the specified frequency channel. This state continues until a subsequent update is transmitted in time slot BU-2. Broadcasts transmitted to the boundary router SU (shown with only two reference numerals for clarity) during the unavailability period S-0 are not received.

[0200] Figure 13 shows a schematic scheduling of a mesh network 300 according to one embodiment. This scheduling can be used in combination with the embodiment shown in Figure 9 described above.

[0201] As shown in Figure 13, broadcast messages sent by mesh peer devices B and C (which may be mesh peer 2000) from a specific time slot UP-1 to UP-4 are not received by the boundary router 1000A. These time slots correspond to the original broadcast slots established in the network. The boundary router 1000A communicates the change in the broadcast slot schedule via asynchronous messaging in time slot BU-1, leading to a new broadcast schedule. In the new schedule, the broadcast slots perfectly coincide with the LTE wake-up period, indicating a complete overlap. This overlap means that during the LTE wake-up period, the boundary router 1000A focuses on LTE communications and does not receive broadcast messages from the mesh network 300. Following this period, the boundary router 1000A communicates further changes to the broadcast slot schedule via asynchronous messaging in time slot BU-2, indicating a return to the original schedule or a transition to a different schedule.

[0202] Figure 14 shows a schematic scheduling of the mesh network 300 according to one embodiment. This scheduling can be used in combination with the embodiments shown in Figures 9 to 11 and Figure 9 described above.

[0203] As shown in Figure 14, the boundary router 1000A communicates a change in the broadcast slot schedule via asynchronous messaging in time slot BU-1. This communication establishes a new broadcast schedule. In the new schedule, the broadcast slots perfectly coincide with the LTE wake-up period, indicating a complete overlap. This overlap means that during the LTE wake-up period, the boundary router 1000A will concentrate on LTE communication and will not receive broadcast messages from the mesh network 300. Following this overlap period, the boundary router 1000A communicates a further change in the broadcast slot schedule via asynchronous messaging in time slot BU-2. This communication may indicate a return to the original schedule or a transition to a different schedule, depending on network requirements and the state of shared resources.

[0204] Figure 15 shows a schematic scheduling of the mesh network 300 according to one embodiment. This scheduling can be used in combination with the embodiments shown in Figures 8 to 11 described above.

[0205] As shown in Figure 15, the boundary router 1000A communicates changes to the broadcast slot schedule via asynchronous messaging in time slot BU-1. This communication establishes a new broadcast schedule. In the new schedule, the broadcast periodicity and duration remain the same as before. During the period from BB-0 to BB-2, the boundary router 1000A is dedicated to broadcast transmission and therefore cannot receive unicast transmissions. From the perspective of peer device 2000, it can attempt to communicate with the boundary router 1000A via the broadcast channel. However, these attempts fail because the boundary router 1000A's shared resources are allocated to the LTE modem 1310. Following the broadcast-centric period, the boundary router 1000A communicates further changes to the broadcast slot scheduling via asynchronous messaging in time slot BU-2. Subsequent communication may include the return to a schedule that supports both broadcast and unicast, or a transition to a different schedule, depending on network requirements and the state of shared resources.

[0206] Figure 16 shows a schematic scheduling of the mesh network 300 according to one embodiment. This scheduling can be used in combination with the embodiments shown in Figures 7 to 11 described above.

[0207] As shown in Figure 16, the boundary router 1000A communicates the change in broadcast slot scheduling via asynchronous messaging in time slot BU-1. This establishes a new broadcast schedule. In the new scheduling, broadcast slots BB-0 to BB-2 perfectly coincide with the LTE connection period CM, showing a complete overlap (see Figures 14 and 15). This overlap means that during the LTE connection period CM, the boundary router is focused on LTE communications and does not receive broadcast messages from the mesh network. Furthermore, time slots UP-0 to UP-2 for the broadcast channel overlap with the duration of C-DRX (Connected Mode Discontinuous Reception). This overlap indicates that the boundary router 1000A is not actively receiving broadcast messages during the C-DRX period. Following the overlapping period, further changes to the broadcast slot scheduling can be communicated by the boundary router via asynchronous messaging in time slots BU-2 and BU-3, depending on network requirements and the state of shared resources.

[0208] Figures 13-16 show several examples of variations of broadcast scheduling. Similarly, unavailability during these periods can be achieved by explicit notification of unavailability by the boundary router 1000A (e.g., b='1', unavailable channel). The advantage of this method is that peer device 2000 completely refrains from attempting to communicate with boundary router 1000A.

[0209] Figure 17 shows a schematic diagram of an alternative scheduling and update process performed by the boundary router 1000A according to this disclosure. The following steps are performed in the time order shown. However, it should be noted that the time axis only shows the qualitative relationship between the individual process steps. This process may include a providing step S51 in which a channel scheduling profile is sent from the mesh modem 1320 to the coexistence module 1330; a request step S52 in which the LTE modem 1310 provides update information regarding scheduled wake-ups to the coexistence module; a calculation step S53 in which the coexistence module 1330 calculates a new wake-up timing for the LTE modem 1310 based on the scheduling profile provided from the mesh modem 1320 and the wake-up schedule provided from the LTE modem 1310; an instruction step S54 in which the coexistence module 1330 sends an instruction to the LTE modem 1310 to reschedule the wake-up timing based on the calculation in step S53; and a wake-up step S55 in which the LTE modem 1310 wakes up at the scheduled time provided by the coexistence module 1330.

[0210] The wake-up scheduling provided by the LTE modem 1310 in request step S52 may include a scheduled wake-up timing at time t. The coexistence module can calculate a modified wake-up timing at time t'. Then, in step S54, the coexistence module instructs the LTE modem 1310 to wake up at time t' instead of time t.

[0211] This sequence can then be repeated at each step and may be continued as needed.

[0212] Figure 18 in Appendix 1 shows a block diagram of a computer capable of carrying out the various embodiments described herein.

[0213] This disclosure may be embodied as a system, method, and / or computer program product. The computer program product may include a computer-readable storage medium on which computer-readable program instructions are recorded, which can cause one or more processors to execute each aspect of this embodiment.

[0214] A computer-readable storage medium can be a tangible device capable of storing instructions used by an instruction-executing device (processor). A computer-readable storage medium can be, but is not limited to, an electronic device, a magnetic device, an optical device, an electromagnetic device, a semiconductor device, or a suitable combination thereof. A non-exclusive list of more specific examples of computer-readable storage mediums includes flexible disks, hard disks, solid-state drives (SSDs), random-access memory (RAM), read-only memory (ROM), EPROM (Erasable Programmable Read-Only Memory) or flash memory, SRAM (Static Random Access Memory), compact disks (CDs or CD-ROMs), DVDs (Digital Versatile Disks), and memory cards or memory sticks (and suitable combinations thereof). The computer-readable storage mediums used in this disclosure should not be interpreted as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses passing through optical fiber cables), or electrical signals transmitted through conductors.

[0215] The computer-readable program instructions described in this disclosure can be downloaded from a computer-readable storage medium to an appropriate arithmetic or processing device, or to an external computer or external storage device via a global network (i.e., the Internet), a LAN (Local Area Network), a WAN (Wide Area Network), and / or a wireless network. The network may include copper transmission lines, optical fiber, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within each arithmetic or processing device can receive computer-readable program instructions from the network, transfer such instructions, and store them in a computer-readable storage medium within the arithmetic or processing device.

[0216] The computer-readable program instructions for performing the operations of the Disclosure may include machine language instructions and / or microcode. These may be compiled or interpreted from source code written in any combination of one or more programming languages, including assembly language, Basic, Fortran, Java, Python, R, C, C++, C#, or similar programming languages. The computer-readable program instructions may be executed entirely on a user's PC, notebook computer, tablet, or smartphone, entirely on a remote computer or computer server, or on any combination of these computing devices. The remote computer or computer server may be connected to the user's device or a combination of devices via a computer network, including a LAN (Local Area Network), a WAN (Wide Area Network), or a global network (i.e., the Internet). In some embodiments, an electronic circuit, including, for example, a programmable logic circuit, an FPGA (Field-Programmable Gate Array), or a programmable logic array (PLA), may execute the computer-readable program instructions and perform each aspect of the Disclosure by configuring or customizing the electronic circuit using information from the computer-readable program instructions.

[0217] Herein, each aspect of the present disclosure will be described with reference to the flowcharts and block diagrams of the methods, apparatus (systems), and computer program products according to the embodiments of the present disclosure. Those skilled in the art will understand that each block in the flowcharts and block diagrams, and combinations of blocks within the flowcharts and block diagrams, can be implemented by computer-readable program instructions.

[0218] Computer-readable program instructions capable of implementing the systems and methods described herein are provided to one or more processors (and / or one or more cores within a processor) of a general-purpose computer, a special-purpose computer, or other programmable device, thereby enabling instructions executed via the processor of the computer or other programmable device to construct a system that performs the functions specified in the flowcharts and block diagrams of this disclosure. Computer-readable program instructions may also be stored in a computer-readable storage medium that can instruct the computer, programmable device, and / or other device to function in a particular manner. Thus, the computer-readable storage medium storing the instructions becomes a product containing instructions that perform each aspect of the functions specified in the flowcharts and block diagrams of this disclosure.

[0219] Computer-readable program instructions can also be loaded into a computer, other programmable device, or other device and used to execute a series of operational steps on the computer, other programmable device, or other device to generate a computer-executed process. Thus, instructions executed on the computer, other programmable device, or other device perform the functions specified in the flowcharts and block diagrams of this disclosure.

[0220] Figure 18 is a functional block diagram showing a network connectivity system 800 of one or more network-connected computers and servers. In one embodiment, the hardware and software environment shown in Figure 18 can provide an exemplary platform for implementing the software and / or methods according to this disclosure.

[0221] Referring to Figure 18, the network connectivity system 800 may include, but is not limited to, a computer 805, a network 810, a remote computer 815, a web server 820, a cloud storage server 825, and a computer server 830. In some embodiments, one or more instances of the functional blocks shown in Figure 18 may be employed.

[0222] Additional details of computer 805 are shown in Figure 18. The functional blocks shown within computer 805 are provided only to establish exemplary functionality and are not intended to be exhaustive. Details of the remote computer 815, web server 820, cloud storage server 825, and computer server 830 are not shown, but other computers and devices may include similar functionality to that shown in computer 805.

[0223] Computer 805 can be a PC (Personal Computer), desktop computer, laptop computer, tablet computer, netbook computer, PDA (Personal Digital Assistant), smartphone, or any other programmable electronic device capable of communicating with other devices on network 810.

[0224] The computer 805 may include a processor 835, a bus 837, memory 840, a non-volatile storage unit 845, a network interface 850, a peripheral device interface 855, and a display interface 865. In some embodiments, each function may be implemented as a separate electronic subsystem (an integrated circuit chip or a chip and associated devices). Alternatively, in other embodiments, a combination of functions may be implemented on a single chip (sometimes referred to as a system-on-a-chip or SoC).

[0225] The Processor 835 may be one or more single or multi-chip microprocessors designed and / or manufactured by Intel Corporation, Advanced Micro Devices (AMD), Arm Holdings (Arm), Apple Computer, Inc., etc. Examples of microprocessors include Intel Corporation's Celeron, Pentium, Core i3, Core i5, and Core i7; AMD's Opteron, Phenom, Athlon, Turion, and Ryzen; and Arm's Cortex-A, Cortex-R, and Cortex-M.

[0226] Bus 837 can be a proprietary or industry-standard high-speed parallel or serial peripheral interconnect bus, such as ISA, PCI, PCI Express (PCI-e), and AGP.

[0227] The memory 840 and the non-volatile storage unit 845 can be computer-readable storage media. The memory 840 may include any suitable volatile device such as DRAM (Dynamic Random Access Memory) and SRAM (Static Random Access Memory). The non-volatile storage unit 845 may include one or more of the following: a flexible disk, a hard disk, a solid-state drive (SSD), ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory) or flash memory, a CD (Compact Disc) or CD-ROM, a DVD (Digital Versatile Disk), and a memory card or memory stick.

[0228] The program 848 may be a set of machine-readable instructions and / or data stored in the non-volatile storage 845, which is used to create, manage, and control specific software functions described in detail at any point in this disclosure and shown in the drawings. In some embodiments, the memory 840 may be considerably faster than the non-volatile storage 845. In such embodiments, the program 848 may be transferred from the non-volatile storage 845 to the memory 840 before execution by the processor 835.

[0229] Computer 805 can communicate and interact with other computers via network 810 through network interface 850. Network 810 can be, for example, a LAN (Local Area Network), a WAN (Wide Area Network) such as the Internet, or a combination of both, and can include wired, wireless, or fiber optic connections. Generally, network 810 can be any combination of connections and protocols that support communication between two or more computers and associated devices.

[0230] The peripheral interface 855 can enable data input / output with other devices that can be locally connected to the computer 805. For example, the peripheral interface 855 can provide a connection to an external device 860. The external device 860 may include devices such as a keyboard, mouse, keypad, touchscreen, and / or other suitable input devices. The external device 860 may also include portable computer-readable storage media such as a thumb drive, portable optical or magnetic disk, or memory card. Software and data used to carry out embodiments of the present disclosure, for example, program 848, can be stored on such portable computer-readable storage media. In such embodiments, the software may be loaded into non-volatile storage 845, or alternatively, directly into memory 840 via the peripheral interface 855. The peripheral interface 855 may use industry standard connections such as RS-232 or USB (Universal Serial Bus) to connect to the external device 860.

[0231] The display interface 865 can connect the computer 805 to the display 870. In some embodiments, the display 870 can be used to present a command line or a graphical user interface to the user of the computer 805. The display interface 865 can connect to the display 870 using one or more proprietary or industry standard connections, such as VGA, DVI, DisplayPort, HDMI®, etc.

[0232] As described above, the network interface 850 provides communication with other computing and storage systems or devices located outside the computer 805. The software programs and data described herein can be downloaded to the non-volatile storage unit 845 via the network interface 850 and network 810 from, for example, a remote computer 815, a web server 820, a cloud storage server 825, and a computer server 830. Furthermore, the systems and methods described herein can be executed by one or more computers connected to the computer 805 via the network interface 850 and network 810. For example, in some embodiments, the systems and methods described herein can be executed by a combination of a remote computer 815, a computer server 830, or interconnected computers on network 810.

[0233] The data, datasets and / or databases employed in embodiments of the systems and methods described herein can be stored on and / or downloaded from the remote computer 815, the web server 820, the cloud storage server 825 and the computer server 830.

[0234] The circuit units used in this application can be defined as one or more of the following: electronic components (such as semiconductor devices), multiple electronic components directly connected to each other or interconnected via electronic communication, a computer, a network of computer devices, a remote computer, a web server, a cloud storage server, or a computer server. For example, one or more of the following may be encompassed by a circuit unit, or may include a circuit unit as one or more of its components. In some embodiments, multiple instances of one or more of these components may be employed, and each of these multiple instances may also be encompassed by a circuit unit or include a circuit unit. In some embodiments, a circuit unit represented by a network connection system may include a serverless computing system corresponding to a set of virtualized hardware resources. A circuit unit represented by a computer may be a PC (Personal Computer), a desktop computer, a laptop computer, a tablet computer, a netbook computer, a PDA (Personal Digital Assistant), a smartphone, or any other programmable electronic device capable of communicating with other devices on a network. The circuit unit may be a general-purpose computer, special-purpose computer, or other programmable device as described in this disclosure, including one or more processors. Each processor may be one or more single or multi-chip microprocessors. A processor is considered a processing circuit unit or circuit unit because it includes transistors and other circuit units. The circuit unit performs the systems and methods described in this disclosure and generates a machine based on computer-readable program instructions provided to one or more processors (and / or one or more cores within a processor) of one or more of the general-purpose computers, special-purpose computers, or other programmable devices described herein.This enables the execution of instructions, either by a circuit unit or via one or more processors of a programmable device containing a circuit unit, to construct a system that performs the functions specified in the flow diagrams and block diagrams of this disclosure. Alternatively, a circuit unit may be a pre-programmed structure such as a programmable logic device or an application-specific integrated circuit, and is considered a circuit unit whether used alone or in combination with other programmable or pre-programmed circuit units.

[0235] Clearly, in light of the above teachings, numerous modifications and alterations are possible with respect to this disclosure. Therefore, it should be understood that, within the scope of the appended claims, this disclosure may be implemented in ways other than those specifically described herein.

[0236] All units and entities described in this specification and claimed in the attached claims are implementable, for example, as integrated circuit logic on a chip, unless otherwise specified, and the functions provided by such units and entities are implementable by software, unless otherwise specified.

[0237] To the extent that the embodiments disclosed above are implemented using a software-controlled data processing device, it will be understood that the computer program providing such software control and the transmission, storage, or other medium providing such computer program are envisioned in each aspect of the disclosure.

[0238] Furthermore, this technology can also be configured as described below. (1) Each mesh modem and each cellular modem comprises a circuit unit configured to manage communication schedules within a mesh network or cellular network in which at least one network resource is shared, wherein the mesh network operates on a mesh protocol and the cellular network operates on a cellular protocol, and the management of communication schedules responds to requests for access to the shared network resource received from either the mesh network or the cellular network in accordance with their respective protocols, and the circuit unit is further configured to determine how to allocate the shared network resource based on the received requests. Electronic devices. (2) The electronic device described in (1), The aforementioned request is received from either the application or the transport layer protocol module. Electronic devices. (3) An electronic device as described in (1), The request is received from at least one of the following, in accordance with the respective network protocol: the mesh modem, the peer device in the mesh network, or the cellular modem or remote device in the cellular network. Electronic devices. (4) The electronic device described in (1), The communication schedule is controlled so that the mesh network does not access the shared network connectivity resources, and the cellular network does access the shared network connectivity resources. Electronic devices. (5) An electronic device described in any of (1) to (4), The control includes sending a scheduling request to all peer devices connected to the mesh network, and in response to the scheduling request, the peer devices refrain from receiving and / or transmitting to the mesh modem on a predetermined channel for a duration specified in the scheduling request. Electronic devices. (6) An electronic device as described in (5), The predetermined channel is at least one of a unicast channel or a broadcast channel. Electronic devices. (7) An electronic device as described in (6), The predetermined channel is the unicast channel, and all of the broadcast channel and peer devices are configured to receive and / or transmit on both the broadcast channel and the unicast channel for the duration specified in the scheduling request. Electronic devices. (8) An electronic device described in any of (6) to (7), The predetermined channel is the unicast channel only, and all of the peer devices are configured to receive and / or transmit only on the broadcast channel for the duration specified in the scheduling request. Electronic devices. (9) An electronic device described in any of (6) to (8), The predetermined channel is a broadcast channel, and all of the peer devices are configured to receive and / or transmit only on the broadcast channel for the duration specified in the scheduling request. Electronic devices. (10) An electronic device described in any of (6) to (9), The predetermined channel is neither the unicast channel nor the broadcast channel, and all of the peer devices are configured to receive and / or transmit on the channel that is neither the unicast channel nor the broadcast channel for the duration specified in the scheduling request. Electronic devices. (11) An electronic device described in any of (1) to (10), The cellular protocol is the LTE protocol, and the duration corresponds to the period during which the LTE modem is active. Electronic devices. (12) An electronic device described in any of (1) to (11), The cellular protocol is the LTE protocol, and the duration corresponds to the cDRX connection period and / or the eDRX period and / or the iDRX period. Electronic devices. (13) An electronic device described in any of (5) to (12), The scheduling request is broadcast to the peer device via a broadcast message. Electronic devices. (14) An electronic device described in any of (5) to (13), The scheduling request is sent to the peer device via direct unicast. Electronic devices. (15) An electronic device described in any of (1) to (14), The shared network resource is at least one of the following: a data transmission means, an antenna, a network line, a network connection interface, a radio frequency chain, or a front-end chain. Electronic devices. (16) An electronic device described in any of (1) to (15), Send an update request to the mesh modem connected to the mesh network to update the mesh scheduling parameters. The cellular modem connected to the cellular network receives scheduling information regarding the communication schedule of the cellular network. It is further configured to Electronic devices. (17) An electronic device described in any of (5) to (16), The aforementioned control is Based on the communication schedule of the cellular network, a scheduling profile for the mesh network is calculated. Send the update request based on the scheduling profile. including Electronic devices. (18) An electronic device described in any of (6) to (17), In response to the update request, the mesh modem sends scheduling profile update information to at least one peer device connected to the mesh network. Electronic devices. (19) An electronic device described in any of (6) to (18), The communication schedule is controlled so that the cellular network does not access the shared network connectivity resource, and the mesh network does access the shared network connectivity resource. Electronic devices. (20) A communication scheduling method, Both manage communication schedules within a mesh network or cellular network sharing at least one network resource, wherein the mesh network operates based on a mesh protocol and the cellular network operates based on a cellular protocol, and the management of the communication schedules responds to requests for access to the shared network resource received from either the mesh network or the cellular network in accordance with their respective protocols. The method of allocating the shared network resources is determined based on the received request. Communication scheduling method. (21) A computer program that causes a computer to perform the method described in (20). (22) A non-transient computer-readable recording medium that stores a computer program product that, when executed by a processor, causes to perform the method described in (20). [Explanation of Symbols]

[0239] 1000, 1000A, 1000B Electronic Devices 1100 Application Layer Module 1200 UDP / TCP module 1300 Communication Module 1310 LTE modem 1311 Data Buffer 1312 IP Module 1313 PDCP Module 1314 RLC module 1315 MAC Module 1316 PHY module 1320 Mesh Protocol Modem 1321 buffer 1322 IP Module 1323 LLC Module 1324 MAC module 1325 PHY module 1330 Coexistence Module 1331 Processing Module 1332 Scheduling Module Information 1350, 1351, 1352, 1353 2000 Mesh Pier 300 Mesh Network 400 cellular networks 410 LTE antenna 800 Network Connectivity Systems 805 Computer 810 Network 815 Remote Computer 820 Web Servers 825 Cloud Storage Server 830 Computer Servers 835 Processor 837 Bus 840 memory 845 Non-volatile memory unit 848 Programs 850 Network Interfaces 855 Peripheral Interface 860 External devices 865 Display Interface 870 displays ANT1, ANT2 antennas BB-0, BB-1, BB-2 Broadcast Slots B-0, B-1, B-2 Broadcast Period BU-1, BU-2, BU-3 Broadcast Slots CM LTE connection period P1, P2, P2A, P3 period S-0 Duration UA-1, UA-2, UA-3 Unicast Blocks UB-1, UB-2, UB-3 Unicast Blocks UC-1, UC-2, UC-3 Unicast Blocks UP-0, UP-1, UP-2, UP-3, UP-4 Unicast Period U-0 Unicast Period Tx transmission

Claims

1. Each mesh modem and each cellular modem comprises a circuit unit configured to manage communication schedules within a mesh network or cellular network sharing at least one network resource, wherein the mesh network operates based on a mesh protocol, and the cellular network operates based on a cellular protocol, and the management of communication schedules responds to requests for access to the shared network resource, and the circuit unit is further configured to determine how to allocate the shared network resource based on the received requests. Electronic devices.

2. The electronic device according to claim 1, The request is received from at least one of the application or the transport layer protocol module. Electronic devices.

3. The electronic device according to claim 1, The request is received from at least one of the following, in accordance with the respective network protocol: the mesh modem, the peer device in the mesh network, or the cellular modem or remote device in the cellular network. Electronic devices.

4. The electronic device according to claim 1, The communication schedule is controlled so that the mesh network does not access the shared network connectivity resources, and the cellular network does access the shared network connectivity resources. Electronic devices.

5. The electronic device according to claim 1, The control includes sending a scheduling request to all peer devices connected to the mesh network, and in response to the scheduling request, the peer devices refrain from receiving and / or transmitting to the mesh modem on a predetermined channel for a duration specified in the scheduling request. Electronic devices.

6. The electronic device according to claim 3, The predetermined channel is at least one of a unicast channel or a broadcast channel. Electronic devices.

7. The electronic device according to claim 6, The predetermined channel is the unicast channel, and all of the broadcast channel and peer devices are configured to receive and / or transmit on both the broadcast channel and the unicast channel for the duration specified in the scheduling request. Electronic devices.

8. The electronic device according to claim 6, The predetermined channel is the unicast channel only, and all of the peer devices are configured to receive and / or transmit only on the broadcast channel for the duration specified in the scheduling request. Electronic devices.

9. The electronic device according to claim 6, The predetermined channel is a broadcast channel, and all of the peer devices are configured to receive and / or transmit only on the broadcast channel for the duration specified in the scheduling request. Electronic devices.

10. The electronic device according to claim 5, The predetermined channel is neither the unicast channel nor the broadcast channel, and all of the peer devices are configured to receive and / or transmit on the channel that is neither the unicast channel nor the broadcast channel for the duration specified in the scheduling request. Electronic devices.

11. The electronic device according to claim 1, The cellular protocol is the LTE protocol, and the duration corresponds to the period during which the LTE modem is active. Electronic devices.

12. The electronic device according to claim 1, The cellular protocol is the LTE protocol, and the duration corresponds to the cDRX connection period and / or the eDRX period and / or the iDRX period. Electronic devices.

13. The electronic device according to claim 5, The scheduling request is broadcast to the peer device via a broadcast message. Electronic devices.

14. The electronic device according to claim 5, The scheduling request is sent to the peer device via direct unicast. Electronic devices.

15. The electronic device according to claim 1, The shared network resource is at least one of the following: data transmission means, antenna, network line, network connection interface, radio frequency chain, or front-end chain. Electronic devices.

16. The electronic device according to claim 1, Send an update request to the mesh modem connected to the mesh network to update the mesh scheduling parameters. The cellular modem connected to the cellular network receives scheduling information regarding the communication schedule of the cellular network. It is further configured to Electronic devices.

17. The electronic device according to claim 5, The aforementioned control is Based on the communication schedule of the cellular network, a scheduling profile for the mesh network is calculated. Send the update request based on the scheduling profile. including Electronic devices.

18. The electronic device according to claim 6, In response to the update request, the mesh modem sends scheduling profile update information to at least one peer device connected to the mesh network. Electronic devices.

19. The electronic device according to claim 1, The communication schedule is controlled so that the cellular network does not access the shared network connectivity resource, and the mesh network does access the shared network connectivity resource. Electronic devices.

20. A communication scheduling method, Both manage communication schedules within a mesh network or cellular network that share at least one network resource, wherein the mesh network operates based on a mesh protocol, and the cellular network operates based on a cellular protocol, and the management of the communication schedules responds to requests for access to the shared network resource. The method of allocating the shared network resources is determined based on the received request. Communication scheduling method.

21. A computer program that causes a computer to perform the method described in claim 20.

Images