Patent Application
20170164266
Wireless communication systems provide for radio communication links to be arranged within the system between a plurality of user terminals. Such user terminals may be mobile and may be known as ‘mobile stations’ or ‘subscriber units.’ At least one other terminal, e.g. used in conjunction with mobile stations, may be a fixed terminal, e.g. a control terminal, base station, repeater, and/or access point. Such a system typically includes a system infrastructure which generally includes a network of various fixed terminals, which are in direct radio communication with the mobile stations. Each of the base stations operating in the system may have one or more transceivers which may, for example, serve mobile stations in a given local region or area, known as a ‘cell’ or ‘site’, by radio frequency (RF) communication. The mobile stations that are in direct communication with a particular fixed terminal are said to be served by the fixed terminal. In one example, all radio communications to and from each mobile station within the system are made via respective serving fixed terminals. Sites of neighboring fixed terminals in a wireless communication system may be offset from one another or may be non-overlapping or partially or fully overlapping. In another example, mobile stations may operate in a direct mode (e.g., without having to pass through, and without the aid of, other infrastructure devices such as a repeater or base station).
Wireless communication systems may operate according to an industry standard protocol such as, for example, the Project 25 (P25) standard defined by the Association of Public Safety Communications Officials International (APCO), or other radio protocols, such as the TETRA standard defined by the European Telecommunication Standards Institute (ETSI), the Digital Private Mobile Radio (dPMR) standard also defined by the ETSI, the Digital Mobile Radio (DMR) standard also defined by the ETSI, an open media alliance (OMA) push to talk (PTT) over cellular (OMA-PoC) standard, a voice over IP (VoIP) standard, or a PTT over IP (PoIP) standard. Protocols such as PoC, VoIP, and PoIP are implemented over broadband radio access networks (RANs) including third generation and fourth generation networks such as third generation partnership project (3GPP) Long Term Evolution (LTE) networks or IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g, 802.11ac and 802.11p) networks.
Communications in accordance with any one or more of these standards, or other standards, may take place over physical channels in accordance with one or more of a TDMA (time division multiple access), FDMA (frequency divisional multiple access), or CDMA (code division multiple access) protocol. Mobile stations in wireless communication systems such as those set forth above send communications (e.g., including user speech, audio, image data, control signaling, video, etc.), in accordance with the designated protocol. Such communications may be sent directly from one mobile station to one or more other mobile stations directly (e.g., via a direct mode protocol) and/or indirectly via an infrastructure (e.g., via an infrastructure mode protocol).
Many so-called “public safety” wireless communication systems provide for group-based radio communications amongst a plurality of mobile stations such that one member of a designated group can transmit once and have that transmission received by all other members of the group substantially simultaneously. Groups are conventionally assigned based on function. For example, all members of a particular local police force may be assigned to a same group so that all members of the particular local police force can stay in contact with one another, while avoiding the random transmissions of radio users outside of the local police force.
Mobile stations such as push-to-talk (PTT) handsets in particular have been used for some time by emergency personnel but also have recently begun to grow in general popularity. Such mobile stations contain a PTT input that enables the user to communicate with a group of users on the same channel (e.g., a particular physical or logical channel statically or dynamically assigned to a particular talkgroup, or set of otherwise associated mobile stations). The communications between the mobile stations occur at one of a set of isolated frequencies that may be selected, at least in part, by a knob on the mobile stations. To communicate with users on other physical or logical channels, the user may manually switch the channel at the mobile station thereby causing the transmission and reception channel to change (perhaps in conjunction with a frequency assignment by a trunked repeater).
In some situations, mobile stations previously operating within an infrastructure network may temporarily or permanently find themselves outside of infrastructure coverage (e.g., outside of wireless communication range of a fixed terminal). Accordingly, some mobile stations may experience periods lacking end-to-end network connectivity resulting in an inability to reach other mobile stations in situations where a need for aid or a need to provide reconnaissance may, in fact, become more likely to occur. Disruption-tolerant networks (DTNs) are thus characterized by their lack of instantaneous end-to-end paths from a source mobile station to a target device (mobile station or infrastructure device).
Conventional disruption-tolerant networking (DTN) source nodes adapt to the lack of end-to-end paths by widely broadcasting communications or requests therefore to each and every DTN node it encounters in a direct mode in hopes that the communications or request will eventually make it through the ad-hoc network of mobile stations to reach the intended destination mobile station. Such DTN broadcasting, however, results in substantially increased loading on intermediary mobile stations and on DTN network wireless medium resources, and results in inefficient use of such mobile station and wireless medium resources.
Accordingly, an improved device, system, and method is needed for routing communications and requests therefore in a DTN network in a more intelligent and efficient manner, so as to conserve mobile station and wireless medium resources in DTN networks.
Embodiments will now be described by way of example with reference to the accompanying drawings, in which:
In light of the foregoing, it would be advantageous to provide for an improved device, system, and method for routing communications or requests therefore in a disruption tolerant network (DTN) network in a more intelligent and efficient manner, assisted by back-end processing, so as to conserve mobile station and wireless medium resources in the DTN network.
In one embodiment, a method of transmitting communications in a DTN including a plurality of mobile stations, comprises: reporting, by a first mobile station, to an infrastructure network, contact pattern information comprising identities of other mobile stations and infrastructure devices determined to be within direct communication range and indications of times at which the other mobile stations and infrastructure devices were determined to be within direct communication range of the first mobile station; receiving, by the first mobile station, from the infrastructure network a set of DTN routing rules for routing communications to any one of the plurality of mobile stations and infrastructure devices via the DTN network; detecting, by the first mobile station, a first communication for transmission to a target device out of the plurality of mobile stations and infrastructure devices via the DTN network; identifying, by the first mobile station, as a function of the set of the DTN routing rules, one or more but less than all mobile stations (i) currently within wireless communication range of the first mobile station or (ii) not currently within but expected to be within wireless communication range of the first mobile station, to act as intermediary mobile stations for storing and forwarding the first communication towards the target device; and transmitting, by the first mobile station, the first communication to the identified one or more intermediary mobile stations when they are determined to be within direct wireless communication range.
In another embodiment, a mobile station comprises: a direct mode wireless interface for communicating via a DTN; an infrastructure mode wireless interface for communicating with an infrastructure network; a memory; and a processor configured to perform a set of functions, the set of functions comprising: reporting, via one of the infrastructure mode wireless interface and the direct mode wireless interface, to the infrastructure network, contact pattern information comprising identities of other mobile stations and infrastructure devices determined to be within direct communication range and indications of times at which the other mobile stations and infrastructure devices were determined to be within direct communication range of the first mobile station; receiving, via one of the infrastructure mode wireless interface and the direct mode wireless interface, and from the infrastructure network, a set of DTN routing rules for routing communications to any one of the plurality of mobile stations and infrastructure devices via the DTN network; detecting a first communication for transmission to a target device out of the plurality of mobile stations and infrastructure devices via the DTN network; identifying, as a function of the set of the DTN routing rules, one or more but less than all mobile stations (i) currently within wireless communication range of the first mobile station or (ii) not currently within but expected to be within wireless communication range of the first mobile station to act as intermediary mobile stations for storing and forwarding the first communication towards the target device; and transmitting, via the direct mode wireless interface, the first communication to the identified one or more mobile stations when they are determined to be within direct wireless communication range.
In a still further embodiment a method of routing communications in a DTN via infrastructure-network generated DTN routing rules, comprises: receiving, at a radio controller in an infrastructure network, contact pattern information from a plurality of mobile stations, the contact pattern information comprising, for each particular mobile station out of the plurality of mobile stations, identities of other mobile stations and infrastructure devices determined to be within communication range of the particular mobile station and indications of times at which the other mobile stations and infrastructure devices were determined to be within communication range of the particular mobile station; creating, at the radio controller, DTN routing rules as a function of the contact pattern information that, for each of an originating mobile station and target device pair, identifies one or more store, carry, and forward routes but less than all store, carry, and forward routes through the DTN network via one or more identified intermediary mobile stations to reach the target device; and causing, by the radio controller, some or all of the DTN routing rules to be provided, from the infrastructure network, to each of the plurality of mobile stations.
Each of the above-mentioned embodiments will be discussed in more detail below, starting with example infrastructure and DTN network architectures of the systems in which the embodiments may be practiced, followed by a discussion of device architectures of devices operating in the described infrastructure and DTN networks, and ending with a discussion of processes for implementing back-end assisted DTN routing in the infrastructure and in the DTN networks. Further advantages and features consistent with this disclosure will be set forth in the following detailed description, with reference to the figures.
The system 100 shown in
Three MSs 105, 107, 109 are illustrated in
BS 151 similarly has radio links with a plurality of MSs, particularly MSs in a service cell or site at least partially defined by a geographic location of the BS 151. In addition to MSs, BS 151 may maintain a direct wireless or wired link 160 (or indirect via system infrastructure 103) with the controller device 121 or other operator.
Two MSs 155, 159 are illustrated in
The system infrastructure 103 includes known sub-systems (not shown) required for operation of the infrastructure network portion of the system 100. Such sub-systems may include, for example, sub-systems providing authentication, routing, MS device registration and location, system management, and other operational functions within the system 100. The system infrastructure 103 may additionally provide routes to other BSs (not shown) providing cells serving other MSs, and/or may provide access to other types of networks such as a plain old telephone system (POTS) network or a data-switched network such as the Internet. The system infrastructure 103 may also maintain a separate link 133 to the controller 121.
Each of the BSs 101, 151 may operate as a conventional radio site, a trunked radio site, and/or a broadband radio site. In a conventional radio system, a plurality of MSs are formed into groups. Each group uses an associated channel (shared or separate) for communication. Thus, each group is associated with a corresponding channel, and each channel can only be used by one group at any particular moment in time. Channels may be divided by frequency, time, and/or code. In some systems, multiple groups may operate on the same channel, and may use a unique group ID embedded in the group communications to differentiate them. Thus, for example, wireless links 111, 113, and 115 may correspond to a statically assigned single channel (carrying traffic and signaling) made up of a pair of frequencies, including an uplink frequency to handle traffic originating from a MS, and a downlink frequency to handle traffic being repeated to other MSs in the talkgroup (and thus tuned to the downlink frequency of the pair of frequencies).
In a trunked radio system, MSs use a pool of channels for supporting virtually an unlimited number of talkgroups. Thus, all talkgroups are served by all channels. For example, in a trunking system, all MSs operating at a radio site idle on a designated control channel or rest channel and when a new call is requested over the control or rest channel, is assigned a new traffic channel (separated from the control channel by frequency or time slot) for the new group call while remaining MSs not participating in the new group call stay on the designated control channel or rest channel. In other embodiments, when a new call is requested over the control or rest channel, the control or rest channel is converted to a traffic channel for the new call, and a new control or rest channel (separated from the prior control channel by frequency or time slot) is assigned for remaining MSs not participating in the new group call to move to and continue to idle on.
Thus, for example, wireless links 111, 113, and 115 may correspond to a dynamically assigned traffic channel made up of a pair of frequencies, including an uplink frequency to handle traffic originating from a MS, and a downlink frequency to handle traffic being repeated for other MSs in the talkgroup (and thus tuned to the downlink frequency of the pair of frequencies). An additional pair of frequencies may be assigned to BS 101 to act as a control or rest channel, to which MSs 105, 107, 109 would return once a call has ended and traffic has ceased on the assigned traffic channel.
In a broadband radio system, MSs are each assigned their own separate (IP-based) broadband link, and talkgroups and channels are assigned logically and tracked and managed by the system infrastructure 103. Thus, for example, wireless links 111, 113, and 115 may correspond to separate individually assigned traffic channels, each made up of a pair of frequencies, including an uplink frequency to handle traffic originating from a MS, and a downlink frequency to handle traffic being separately repeated for each other MS in the talkgroup. Routing between MSs is handled logically and on an IP-basis by the infrastructure 103, such that communications transmitted by an initiating MS 105 and labeled with the target talkgroup is duplicated within the system infrastructure 103 and separately sent to target MSs 107 and 109 via separate broadband downlinks in wireless links 113 and 115. In the context of the broadband radio system, the frequencies of each separate broadband link 111, 113, 115 are independent of logical channels created over each separate broadband link, and broadband traffic across each link is tagged with a logical identifier that identifies particular broadband traffic as associated with a particular talkgroup. Thus, in this context, a talkgroup identifier and a logical channel identifier may be one in the same and may perform same or similar purposes. In other embodiments, broadband Multicast-Broadcast Single Frequency Network (MBSFN) channels may be used to replace one or both of the downlinks 113, 115. Other possibilities exist as well.
In a DMC radio network, BSs 101, 151, system infrastructure 103, and controller device 121 (and corresponding links) would not exist or may exist but are not used or are not accessible to the MSs. DMC is a communication technique where any MS can communicate with one or more other MSs without the need for any additional infrastructure equipment (including base stations or repeaters). Direct mode operation can therefore provide a more efficient, less costly communication system than repeater mode operation. Thus, for example, a DMC radio network may be comprised solely of DMC MSs 105, 107, 109 and intervening wireless direct links 112, 114, and 116. A separate DMC network of DMC MSs 155, 159 may be created via intervening wireless direct link 156. DMC networks are disclosed in more detail with respect to
As a result of the disconnected state of the DMC networks 202, 204 in
Applying the conventional “store-and-forward’ technique to
The processing unit 303 may include an encoder/decoder 311 with an associated code Read Only Memory (ROM) 312 for storing data for encoding and decoding voice, data, control, or other signals that may be transmitted or received between the radio controller and BSs or MSs in the system. The processing unit 303 may further include a microprocessor 313 coupled, by the common data and address bus 317, to the encoder/decoder 311, a character ROM 314, a Random Access Memory (RAM) 304, and a static memory 316.
The communications unit 302 may include one or more wired or wireless input/output (I/O) interfaces 309 that are configurable to communicate with MSs, with BSs, and/or with other components in the system infrastructure 103. The communications unit 302 may include one or more wireless transceivers 308, such as a DMR transceiver, a P25 transceiver, a Bluetooth transceiver, a Wi-Fi transceiver perhaps operating in accordance with an IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g, 802.11ac and 802.11p), a WiMAX transceiver perhaps operating in accordance with an IEEE 802.16 standard, Long Term Evolution (LTE) standard, and/or other similar type of wireless transceiver configurable to communicate via a wireless radio network. The communications unit 302 may additionally or alternatively include one or more wireline transceivers 308, such as an Ethernet transceiver, a Universal Serial Bus (USB) transceiver, or similar transceiver configurable to communicate via a twisted pair wire, a coaxial cable, a fiber-optic link or a similar physical connection to a wireline network. The transceiver 308 is also coupled to a combined modulator/demodulator 310 that is coupled to the encoder/decoder 311.
The microprocessor 313 has ports for coupling to the input unit 306 and to the display screen 305. The character ROM 314 stores code for decoding or encoding data such as contact pattern information, DTN routing rules, signaling messages, and/or data or voice messages. Static memory 316 may store operating code for the microprocessor 313 that, when executed, performs one or more of the steps set forth in
Static memory 316 may also store, permanently or temporarily, decoded contact pattern information for one or more, or all, MSs in the system, and may also store, permanently or temporarily, generated DTN routing rules for determining store, carry, and forward routes to transmit communications from any one MS in the system to any another MS in the system using one or more intermediary MSs. Other types of information could be tracked and/or stored in static memory 316 as well.
Static memory 316 may comprise, for example, a hard-disk drive (HDD), an optical disk drive such as a compact disk (CD) drive or digital versatile disk (DVD) drive, a solid state drive (SSD), a tape drive, a flash memory drive, or a tape drive, to name a few.
The processing unit 403 may include an encoder/decoder 411 with an associated code ROM 412 for storing data for encoding and decoding voice, data, control, and/or other signals that may be transmitted or received by MS 400. The processing unit 403 may further include a microprocessor 413 coupled, by the common data and address bus 417, to the encoder/decoder 411, a character ROM 414, a RAM 404, and a static memory 416.
The communications unit 402 may include an RF interface 409 configurable to communicate with other MSs such as MSs 107, 109, 155, 159, with BSs such as BSs 101, 151, and with controller device 121 via BSs 101, 151 and/or one or more intermediary MSs. The communications unit 402 may include one or more wireless radio transceivers 408, such as a DMR transceiver, a P25 transceiver, a TETRA transceiver, a Bluetooth transceiver, an LTE transceiver, a Wi-Fi transceiver perhaps operating in accordance with an IEEE 802.11 standard, a WiMAX transceiver perhaps operating in accordance with an IEEE 802.16 standard, and/or other similar type of wireless transceiver configurable to communicate via a wireless network. The transceiver(s) are capable of operating in accordance with an infrastructure mode to communicate directly with BSs and in a direct mode to communicate directly with other MSs. The transceiver(s) are also coupled to a combined modulator/demodulator 410 that is coupled to the encoder/decoder 411.
The microprocessor 413 has ports for coupling to the input unit 406 and to the display screen 405. The character ROM 414 stores code for decoding or encoding data such as contact pattern information, DTN routing rules, signaling messages, and/or data or voice messages. Static memory 416 may store operating code for the microprocessor 413 that, when executed, performs one or more of the steps set forth in
Static memory 416 may comprise, for example, a HDD, an optical disk drive such as a CD drive or DVD drive, a SSD, a tape drive, a flash memory drive, or a tape drive, to name a few.
At step 502, the MS reports contact pattern information to the radio controller in the infrastructure network, via an infrastructure wireless link such as wireless link 111 in
The aforementioned contact pattern information could be reported to the infrastructure in a number of ways, including being determined by and provided by the MS, obtained by the MS via an information exchange with the another MS and provided by the MS, pre-programmed or pre-associated with the another MS at the MS and provided by the MS, pre-programmed or pre-associated with the MS or another MS in the infrastructure at the radio controller or otherwise made accessible to the radio controller, and/or separately provided to the infrastructure by the another MS and stored at the radio controller or made accessible to the radio controller, among other possibilities.
At step 504, the MS receives, from the radio controller in the infrastructure network via an infrastructure wireless link such as wireless link 111 with BS 101 in
As a result, when an originating MS detects a request to transmit a first communication or a request therefore to a target MS at step 506, and in the absence of an available infrastructure network link, the originating MS can identify at step 508, and as a function of the DTN routing rules, one or more, but less than all, MSs within its current wireless communication range or MSs expected to be within its wireless communication range as first-hop intermediary MSs in a chain of MSs for storing and forwarding the first communication or request therefore towards the target MS via the DTN network.
Table I illustrates an example DTN routing rules table that may be received at the MS from the infrastructure. The first row of the rules in Table I shows that if the MS wishes to reach the target MS with an ID of 0xABCD, it should look to a MS with an ID of 0xEEEE that has a predicted time of arrival (TOA) within a DMC wireless communication range of the MS between 8:02 and 8:32 (assuming military time). In this case, the MS with the ID of 0xEEEE may be the only intermediary MS in a chain to the target MS with the ID of 0xABCD, or may be just the first of several intermediary MSs in a chain to the target MS with the ID of 0xABCD. Stated more generally, in some embodiments the DTN routing rules may specify an entire chain of all intermediary MSs on a path to each reachable target MS, an identical copy of which may be provided by the infrastructure to every MS and which and may be included in each transmission of the communication to each subsequent intermediary MS on the way to the target MS in order to ensure that each intermediary MS has obtained a copy. In other embodiments, unique DTN routing rules may be separately provided to and stored at the intermediary MSs that may only identify a next-hop MS (first-hop MS relative to each intermediary MS in the path to the target MS) and expected TOA of that next-hop MS in the path to the target MS. In the latter case, a copy of the DTN routing rules would not be sent via DMC as each unique set of rules would not be helpful to any other MS on the path to the target MS.
The second row of the rules in Table I shows that if the MS wishes to reach the target MS with an ID of 0x0123, it should look to one or both MSs having IDs of 0x4567 and 0x89AB. In this example, the DTN routing rules identify more than one route (but still less than all possible routes) to improve reliability of the transmission from the originating source MS to the target MS. The expected TOA is set to NULL to indicate that MSs having IDs of 0x4567 and 0x89AB were always detected to be within DMC wireless communication range of the MS. In this case, the originating MS may determine, if both intermediary MSs are indeed found within a wireless communication range of the MS, to randomly select one of the two or to transmit the same first communication to both. The identification of two MSs increases redundancy in the event that the predictions made in the infrastructure are incorrect or delayed, but still saves bandwidth and storage space over broadcasting the first communication to every single MS within communication range of the originating and/or intermediary MSs.
The third row of the rules in Table I shows that, in some instances, there may currently be no route available between a particular originator MS and a target MS (here, indicated via NULL), or that in some instances a time to reach the target MS (calculated by the infrastructure) exceeds a threshold maximum time set in the infrastructure. In this case, the originator MS would need to indicate, via its user interface, an error in contacting the indicated target MS. In some embodiments, the MS may indicate that no current route exists, but may provide an option via its user interface to store the communication for future transmission when an infrastructure connection becomes available or when updated DTN routing rules are received. If a new DMC or infrastructure-route becomes available, the stored communication could then be transmitted via the newly available route.
At step 510, the MS determines whether the intermediary MS(s) identified at step 508 are located during the expected TOA, and if so, proceeds to step 512 where the MS transmits the first communication directly to the identified one or more first-hop intermediary MSs. In some embodiments, the MS may wait for an acknowledgment that the target MS received the communication, and after a threshold period of time without receiving the acknowledgment, may return to step 508 and identify one or more backup or alternative first hop intermediary MSs, if available, that may be specified in the DTN routing rules.
Returning to step 510 if, on the other hand, the intermediary MS(s) identified at step 508 are not located within the expected TOA, processing proceeds to step 514, where the MS may wait for some threshold period of time after expiration of the TOA, to allow for some flexibility in timing and refrain from too hastily identifying a secondary but perhaps less optimal route. If the threshold period of time has not expired, processing may proceed back to step 510 to determine if the identified MSs can now be located. If, however, it is determined at step 514 that the threshold period of time has expired, processing proceeds to step 516. In one embodiment, at step 516 the MS identifies one or more secondary MSs to act as intermediary MSs, different from the MSs identified at step 508, and processing proceeds back to step 510 using the secondary MSs. In another embodiment, the first or a subsequent time step 516 is executed, the MS may fall back to a conventional pre-programmed DTN routing mechanism that, for example, may identify all available MSs within DCM range as intermediary mobile stations. Other fall-back pre-programmed DTN routing mechanisms could be used as well.
While steps 502, 504 and steps 506-516 are illustrated in a serial manner for ease of illustration, in some embodiments, steps 502 and 504 may be occurring continuously, even in parallel with steps 506-516, and corresponding continually updated contact pattern information periodically provided back to the infrastructure (when available) and updated DTN routing rules provided to the MS (when available), so that the DTN routing rules are continually being updated at MSs in the DTN network.
As one example of the process 500, and with respect to
MS 105, for example, may then detect a request to transmit an image to target MS 159 (step 506). MS 105 may identify, while now outside of the infrastructure network of
At step 602, the radio controller receives contact pattern information from a plurality of MSs. The contact pattern information received at step 602 may be the same or similar to the contact pattern information described with respect to step 502 of
At step 604, the radio controller creates a new set (or modifies an existing set) of DTN routing rules for the MSs reporting contact pattern information in the radio system in which it operates. The DTN routing rules are formed as a function of the reported contact pattern information, and indicate, for each of an originating and target MS and/or target infrastructure device pair, one or more store, carry, and forward routes through the DTN network via one or more identified intermediary MSs to reach the target MS or infrastructure device without requiring the communication desired to be transmitted to the target device to be broadcast to every MS in the DTN network and without requiring every MS in the DTN network to store the communication. The DTN routing rules also may indicate an expected TOA for the one or more next-hop intermediary MSs to arrive within a DCM wireless range of the transmitting MS. As set forth earlier, in some embodiments, the DTN routing rules may specify an entire chain of intermediary (next-hop) MSs and corresponding TOAs between the originating MS and target MS.
The radio controller in the infrastructure may use wireless system modeling tools such as NS-2, OMNET++, J-Sim, GloMoSim, or others to simulate DCM wireless coverage given the contact pattern and location information provided in the contact pattern information from the MSs, and known or determined characteristics of wireless interfaces available at the MSs. The radio controller may use the movement information provided by the MSs to predict future movement of the MSs along same/similar paths and based on similar characteristics (e.g., time of day, location, response status, detected velocity, etc.), and/or may use scheduling information based on some association of the MS (self-reported or pre-configured at the radio controller) with a regular movement, such as based on a known train or bus schedule with which a particular MS is reported to or pre-configured to be associated with.
Where more than one route is determined to exist between source and target MSs via the modeling, the radio controller may prioritize those intermediary MSs having preferred characteristics, as determined via the contact pattern secondary information, such as lower transmission loads, higher storage availability, higher battery capacity, faster wireless interface availability, larger battery or higher remaining charge, earlier expected arrival time at the target MS, lower velocity, or other information made available to the radio controller. In some embodiments, the radio controller may access locally stored information that is pre-populated or separately reported by MSs with MS characteristic and/or capability information as well in determining DTN routing rules. The resultant unique and/or common DTN routing rules may be the same or similar to those set forth above with respect to step 504 of
At step 606, the radio controller causes the unique or common DTN routing rules created or modified at step 604 to be provided to each MS in the DTN network via the infrastructure connection (e.g., for those MSs having a current connection to the infrastructure) and/or via the DTN network. In some instances, a MS that was within infrastructure coverage and reported contact pattern information may move out of infrastructure coverage by the time the DTN routing rules are created or updated. In other instances, the radio controller may update the DTN routing rules in a manner that affects one or more missing MSs that do not currently have an infrastructure link to the infrastructure and thus to the radio controller. In such cases, the radio controller may wait until the next time the missing MS(s) connects to the infrastructure and then transmit a notice to the MS that new or updated DTN routing rules are available (or may simply transmit them without prior notice). In some embodiments, the radio controller may explicitly request or implicitly rely on MSs that do have current connections to the infrastructure to provide the new or updated copy of the DTN routing rules to the missing MS(s) when they come into DMC wireless range of them. In the latter case, the radio controller may provide a list of MS identifiers that it has not yet been able to provide a new or updated copy of the (unique or common) DTN routing rules to, so that DMC MSs operating in the DTN network can determine whether a MS that it detects or connects to needs the new or updated DTN routing rules. In such a case, the MS could provide the new or updated DTN routing rules to the missing MS via a DMC link in the DTN network.
At step 608, the radio controller determines if updated contact pattern information has been received from one or more DMC MSs in the DTN network. If so, processing proceeds back to step 604 where DTN routing rules are modified to incorporate the updated information. If, on the other hand, no updated contact pattern information has been received, processing loops back to step 608.
As one example of the process 600, and with respect to
For example,
In accordance with the foregoing, an improved device, system, and method for routing communications or requests therefore in a DTN network in a more intelligent and efficient manner using back-end infrastructure assistance is disclosed. As a result, MS storage resource utilization and DMC wireless medium resource utilization can be reduced.
In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.
Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “has”, “having,” “includes”, “including,” “contains”, “containing” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by “comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms “a” and “an” are defined as one or more unless explicitly stated otherwise herein. The terms “substantially”, “essentially”, “approximately”, “about” or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%. The term “coupled” as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is “configured” in a certain way is configured in at least that way, but may also be configured in ways that are not listed.
It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or “processing devices”) such as microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used.
Moreover, an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.
The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/RU2014/000597 | 8/8/2014 | WO | 00 |
