Method and device for radio communication
A common discovery channel scheme enables efficient power management in wireless communication systems by allowing terminal devices to detect multiple radio access technologies using a single low-power module, addressing the challenge of high power consumption and suboptimal network discovery.
Patent Information
- Application Number
- JP2024137499
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2016-12-30
- Filing Date
- 2024-08-19
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2037-12-20
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing power consumption and network discovery across multiple radio access technologies, leading to increased battery drain and suboptimal performance in terminal devices.
Implementing a common discovery channel scheme where network access nodes cooperate to broadcast discovery signals on a shared channel, allowing terminal devices to use a single low-power module for detection across various radio access technologies, reducing the need for continuous scanning by individual communication modules.
This approach significantly reduces power consumption in terminal devices by minimizing the active operation of multiple communication modules during discovery, while maintaining effective network detection and connection establishment across different wireless networks.
Smart Images

Figure 2024167254000001_ABST
Abstract
Description
[Background technology]
[0001] Cross-reference to related applications This application claims priority to U.S. Patent Application No. 62 / 440,501, filed December 30, 2016, the contents of which are incorporated by reference in their entirety.
[0002] Technical Field Various aspects relate generally to methods and devices for wireless communication.
[0003] Background technology An end-to-end communication network can include wireless communication networks and wired communication networks. A wireless communication network can include network access nodes (e.g., base stations, access points, etc.) and terminal devices (e.g., mobile phones, tablets, laptops, computers, Internet of Things (IoT) devices, wearables, implantable devices, machine-type communication devices, etc.), and vehicles (e.g., cars, trucks, buses, bicycles, robots, motorbikes, trains, ships, submarines, drones, aircraft, balloons, satellites, spacecraft, etc.), and can provide a wireless access network for such terminal devices to communicate with other terminal devices and access various networks via the network access nodes. For example, a cellular wireless communication network may provide a system of cellular base stations that serve terminal devices within an area to provide them with wireless access to communications with other terminal devices or to applications and services such as voice, text, multimedia, and the Internet, while a short-range wireless access network such as a wireless local area network (WLAN) may provide a system of WLAN access points (APs) that can provide access to other terminal devices within the WLAN network or to other networks such as cellular networks or wired communication networks. [Brief explanation of the drawings]
[0004] In the drawings, like reference numerals generally refer to the same parts throughout the various views. The drawings are not necessarily to scale. Rather, the drawings generally emphasize one or more features. In the following description, various aspects of the present disclosure are described with reference to the following drawings: [Figure 1] FIG. 1 illustrates an exemplary wireless communication system including terminal devices, terminal devices that also function as access nodes, wireless links and standards, network access nodes, servers, gateways / interchanges, and a backbone infrastructure in accordance with some aspects. [Figure 2] FIG. 2 illustrates a network scenario including terminal devices and network access nodes associated with an exemplary discovery information scheme, such as a common discovery channel scheme, in accordance with some aspects. [Figure 3] FIG. 3 illustrates an internal configuration of an exemplary terminal device according to some aspects. [Figure 4] FIG. 4 illustrates the internal structure of an exemplary common discovery module according to some aspects. [Figure 5] FIG. 5 illustrates a methodology for performing radio access communications using an exemplary common discovery channel scheme in accordance with some aspects. [Figure 6] FIG. 6 illustrates a first internal configuration of an exemplary network access node in accordance with some aspects. [Figure 7] FIG. 7 illustrates an example method for providing discovery signals in a common discovery channel scheme in accordance with some aspects. [Figure 8] FIG. 8 illustrates a first example network scenario utilizing an external database for storing discovery information in accordance with some aspects. [Figure 9] FIG. 9 illustrates a second example network scenario utilizing an external database for storing discovery information in accordance with some aspects. [Figure 10]FIG. 10 illustrates an example methodology for conducting wireless communication in connection with a common discovery channel scheme in accordance with some aspects. [Figure 11] FIG. 11 illustrates an example network scenario including terminal devices and network access nodes involved in a forwarding and common monitoring scheme in accordance with some aspects. [Figure 12] FIG. 12 illustrates a second exemplary internal configuration of a network access node in accordance with some aspects. [Figure 13] FIG. 13 illustrates a first exemplary method for conducting wireless communication in connection with a forwarding and common monitoring scheme in accordance with some aspects. [Figure 14] FIG. 14 illustrates a second exemplary method for conducting wireless communication in connection with a forwarding and common monitoring scheme in accordance with some aspects. [Figure 15] FIG. 15 illustrates an example wireless communication network according to some aspects. [Figure 16] FIG. 16 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 17] FIG. 17 illustrates a first example time-frequency resource grid for wireless communications in accordance with some aspects. [Figure 18] FIG. 18 illustrates an example transport-to-physical channel mapping in accordance with some aspects. [Figure 19] FIG. 19 illustrates a second example time-frequency resource grid for wireless communication in accordance with some aspects. [Figure 20] FIG. 20 illustrates an example network scenario of a wireless communication network in accordance with some aspects. [Figure 21] FIG. 21 illustrates a third example time-frequency resource grid for wireless communications in accordance with some aspects. [Figure 22] FIG. 22 illustrates a fourth example time-frequency resource grid for wireless communication in accordance with some aspects. [Figure 23] FIG. 23 illustrates an example methodology relating to selecting between available channel instances in accordance with some aspects. [Figure 24] FIG. 24 illustrates an exemplary internal configuration of a terminal device having a low-power wireless access system according to some aspects. [Figure 25] FIG. 25 illustrates an example methodology relating to providing multiple channel instances in accordance with some aspects. [Figure 26] FIG. 26 illustrates an exemplary internal configuration of a network access node in accordance with some aspects. [Figure 27] FIG. 27 illustrates an example methodology for providing channel configuration information to a requesting end device in accordance with some aspects. [Figure 28] FIG. 28 illustrates an exemplary message sequence chart associated with selecting and attaching a channel instance in accordance with some aspects. [Figure 29] FIG. 29 illustrates an exemplary method for operating a terminal device in accordance with some aspects. [Figure 30] FIG. 30 illustrates an example method for operating one or more network access nodes in accordance with some aspects. [Figure 31] FIG. 31 illustrates an example methodology for selecting random access transmit power in accordance with some aspects. [Figure 32] FIG. 32 illustrates an example internal configuration of a physical layer processing module utilizing modularization according to some aspects. [Figure 33] FIG. 33 illustrates an exemplary message sequence chart according to some aspects relating to a procedure for arranging scheduling of modularized physical layer processing modules. [Figure 34] FIG. 34 illustrates an exemplary method for operating a communications module arrangement in accordance with some aspects. [Figure 35] FIG. 35 illustrates a first exemplary internal configuration of a terminal device according to some aspects. [Figure 36] FIG. 36 illustrates a second exemplary internal configuration of a terminal device according to some aspects. [Figure 37] FIG. 37 illustrates a third exemplary internal configuration of a terminal device according to some aspects. [Figure 38] FIG. 38 illustrates a fourth exemplary internal configuration of a terminal device according to some aspects. [Figure 39] FIG. 39 illustrates an exemplary internal configuration of a receive module and a transmit module according to some aspects. [Figure 40] FIG. 40 illustrates an exemplary internal configuration of a receiver module according to some aspects. [Figure 41] FIG. 41 illustrates an example internal configuration of a receiver module for demodulator applications according to some aspects. [Figure 42] FIG. 42 illustrates an example of the operation of a control module according to some embodiments. [Figure 43] FIG. 43 illustrates a method of operating a communication system in accordance with some aspects. [Figure 44] FIG. 44 illustrates an exemplary wireless communication network illustrating data bearers in accordance with some aspects. [Figure 45] FIG. 45 illustrates an exemplary internal configuration of a terminal device in a receiving configuration according to some aspects. [Figure 46] FIG. 46 illustrates a first mapping of data from various data bearers to various receiver modules according to some aspects. [Figure 47] FIG. 47 illustrates a second mapping of data from various data bearers to various receiver modules in accordance with some aspects. [Figure 48] FIG. 48 illustrates a third mapping of data from various data bearers to various receiver modules in accordance with some aspects. [Figure 49] FIG. 49 illustrates a fourth mapping of data from various data bearers to various receiver modules in accordance with some aspects. [Figure 50] FIG. 50 illustrates a fifth mapping of data from various data bearers to various receiver modules in accordance with some aspects. [Figure 51]FIG. 51 illustrates an example distribution of data across various carriers in carrier aggregation according to some aspects. [Figure 52] FIG. 52 illustrates a sixth mapping of data from various data bearers to various receiver modules in accordance with some aspects. [Figure 53] FIG. 53 illustrates a sixth mapping of data from various data bearers to various receiver modules in accordance with some aspects. [Figure 54A] FIG. 54A illustrates various exemplary internal configurations of a terminal device in a transmission configuration according to some aspects. [Figure 54B] FIG. 54B illustrates various exemplary internal configurations of a terminal device in a transmission configuration according to some aspects. [Figure 55] FIG. 55 illustrates a first exemplary method for conducting wireless communication in accordance with some aspects. [Figure 56] FIG. 56 illustrates a second exemplary method of conducting wireless communication in accordance with some aspects. [Figure 57] FIG. 57 illustrates a first example depiction of a relationship between radio resource allocation and power consumption in accordance with some aspects. [Figure 58] FIG. 58 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 59] FIG. 59 illustrates a second example depiction of the relationship between radio resource allocation and power consumption in accordance with some aspects. [Figure 60] FIG. 60 illustrates an example depiction of a network node that performs processing in accordance with some aspects. [Figure 61] FIG. 61 illustrates an exemplary method of operating a network processor in accordance with some aspects. [Figure 62] FIG. 62 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 63] FIG. 63 illustrates various exemplary charts illustrating retransmission notification turnaround times according to some aspects. [Figure 64]FIG. 64 illustrates an exemplary method of operating a network processing module in accordance with some aspects. [Figure 65] FIG. 65 illustrates a first example network situation in accordance with some aspects. [Figure 66] FIG. 66 illustrates an exemplary internal depiction of a control module for a network access node according to some aspects. [Figure 67] FIG. 67 illustrates various exemplary transmission and reception schedules according to some aspects. [Figure 68] FIG. 68 illustrates a second example network situation in accordance with some aspects. [Figure 69A] FIG. 69A illustrates various transmission and reception schedules using discontinuous transmission and / or reception in accordance with some aspects. [Figure 69B] FIG. 69B illustrates various transmission and reception schedules using discontinuous transmission and / or reception in accordance with some aspects. [Figure 70] FIG. 70 illustrates a first exemplary method for conducting wireless communication in accordance with some aspects. [Figure 71] FIG. 71 illustrates a second exemplary method of conducting wireless communication in accordance with some aspects. [Figure 72] FIG. 72 illustrates an exemplary network scenario according to some aspects using a network access node. [Figure 73] FIG. 73 illustrates an exemplary message sequence chart illustrating a connection continuity service using a network access node in accordance with some aspects. [Figure 74] FIG. 74 illustrates an exemplary network situation according to some aspects using an edge computing server. [Figure 75] FIG. 75 illustrates an example message sequence chart illustrating a connection continuity service using an edge computing server according to some aspects. [Figure 76] FIG. 76 illustrates an example methodology for conducting wireless communication in a terminal device in accordance with some aspects. [Figure 77] FIG. 77 illustrates an example method for performing wireless communication in a network processing component in accordance with some aspects. [Figure 78] FIG. 78 illustrates an exemplary network situation according to some aspects. [Figure 79] FIG. 79 illustrates an exemplary message sequence chart illustrating connection continuity services for a group of terminal devices according to some aspects. [Figure 80] FIG. 80 illustrates an example method for performing wireless communication in accordance with some aspects. [Figure 81] FIG. 81 illustrates an example method for performing wireless communication in accordance with some aspects. [Figure 82] FIG. 82 illustrates an exemplary network situation in accordance with some aspects. [Figure 83] FIG. 83 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 84] FIG. 84 illustrates an exemplary internal configuration of an autonomous mobile device according to some embodiments. [Figure 85] FIG. 85 illustrates an exemplary message sequence chart according to some aspects relating to a procedure for selecting a sensitivity level for a navigation sensor in an autonomous mobile device. [Figure 86] FIG. 86 illustrates an exemplary network scenario using an external sensor network in accordance with some aspects. [Figure 87] FIG. 87 illustrates an example network scenario using multiple network access nodes, each with its own cell, in accordance with some aspects. [Figure 88] FIG. 88 illustrates an example network situation using a planned route for an autonomous mobile device according to some aspects. [Figure 89] FIG. 89 illustrates an example network situation using a master autonomous mobile device according to some aspects. [Figure 90] FIG. 90 illustrates an exemplary method of operating a mobile device according to some aspects. [Figure 91] FIG. 91 illustrates an example wireless communication network according to some aspects. [Figure 92] FIG. 92 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 93] FIG. 93 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 94] FIG. 94 illustrates an example depiction of the use of context information in different platforms of terminal devices according to some aspects. [Figure 95] FIG. 95 illustrates a road navigation scenario according to some embodiments. [Figure 96] FIG. 96 illustrates an example of a terminal device according to some aspects. [Figure 97] FIG. 97 illustrates an exemplary method in a terminal device according to some aspects. [Figure 98] FIG. 98 illustrates an example depiction of network scan timing results according to some aspects. [Figure 99] FIG. 99 illustrates an example application according to some aspects in a road navigation scenario using multiple network access nodes. [Figure 100] FIG. 100 illustrates an example method according to some aspects for controlling radio operations based on a historical sequence of radio conditions and other context information. [Figure 101] FIG. 101 illustrates an example method for conducting wireless communication in accordance with some aspects. [Figure 102] FIG. 102 illustrates an example of a terminal device and a network access node according to some aspects. [Figure 103] FIG. 103 illustrates an example configuration of a terminal device prediction and decision module according to some aspects. [Figure 104] FIG. 104 illustrates an example configuration of a network access node prediction and decision module according to some aspects. [Figure 105]FIG. 105 illustrates an exemplary message sequence chart according to some aspects detailing an interaction between a terminal device and a network access node prediction and decision module. [Figure 106] FIG. 106 illustrates an example method for making spectrum assignment decisions in accordance with some aspects. [Figure 107] FIG. 107 illustrates an example of a cloud-based infrastructure in accordance with some aspects. [Figure 108] FIG. 108 illustrates an example internal configuration of local and cloud prediction and decision modules according to some aspects. [Figure 109] FIG. 109 illustrates various exemplary message formats for crowdsourcing context information according to some aspects. [Figure 110] FIG. 110 illustrates a first exemplary method for conducting wireless communication in accordance with some aspects. [Figure 111] FIG. 111 illustrates a second exemplary method of conducting wireless communication in accordance with some aspects. [Figure 112] FIG. 112 illustrates an example network scenario for managing an IoT network in accordance with some aspects. [Figure 113] FIG. 113 illustrates an exemplary internal configuration of a gateway device according to some aspects. [Figure 114] FIG. 114 illustrates an example method according to some aspects in an IoT node for performing wireless measurements and detecting networks. [Figure 115] FIG. 115 illustrates an example internal configuration of a baseband modem for an IoT node according to some aspects. [Figure 116] FIG. 116 illustrates an example method according to some aspects in a gateway device for collecting wireless measurements and reconfiguring a wireless network. [Figure 117] FIG. 117 illustrates an example method for managing a wireless multi-hop network in accordance with some aspects. [Figure 118]FIG. 118 illustrates an example method for performing wireless communication in accordance with some aspects. [Figure 119] FIG. 119 illustrates an exemplary scenario of beam steering with a vehicle target according to some embodiments. [Figure 120] FIG. 120 illustrates an example internal configuration of a control module for a network access node according to some aspects. [Figure 121] FIG. 121 illustrates an exemplary method according to some embodiments for performing beam steering for a vehicle target. [Figure 122] FIG. 122 illustrates exemplary situations according to some ways a vehicle can obstruct another vehicle. [Figure 123] FIG. 123 illustrates an example scenario of radio access technology switching in accordance with some aspects. [Figure 124] FIG. 124 illustrates an exemplary scenario utilizing an aerial drone according to some embodiments. [Figure 125] FIG. 125 illustrates an example method for conducting wireless communication according to some aspects. [Figure 126] FIG. 126 illustrates an exemplary network architecture according to some aspects. [Figure 127] FIG. 127 illustrates an exemplary arrangement of network access nodes for distributing radio environment map (REM) data storage in accordance with some aspects. [Figure 128] FIG. 128 illustrates an exemplary internal configuration of a distributed REM server according to some embodiments. [Figure 129] FIG. 129 illustrates an exemplary message sequence chart illustrating a request-response mechanism for REM data according to some aspects. [Figure 130] FIG. 130 illustrates an example table relating to a two-dimensional framework for requesting REM data based on device capabilities and context information detail level in accordance with some aspects. [Figure 131] FIG. 131 illustrates a first exemplary method for managing REM data in a distributed manner according to some embodiments. [Figure 132] FIG. 132 illustrates a second exemplary method for managing REM data according to some embodiments. [Figure 133] FIG. 133 illustrates an exemplary plot of burst traffic duration in accordance with some aspects. [Figure 134] FIG. 134 illustrates an example methodology according to some aspects for triggering semi-persistent scheduling (SPS) based on predicted user traffic patterns. [Figure 135] FIG. 135 illustrates an example method according to some aspects for controlling scheduling decisions based on detection of non-compliant terminal device behavior. [Figure 136] FIG. 136 illustrates an exemplary wireless communication network according to some aspects. [Figure 137] FIG. 137 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 138] FIG. 138 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 139] FIG. 139 illustrates an exemplary end-to-end network architecture according to some aspects. [Figure 140] FIG. 140 illustrates an example end-to-end network architecture utilizing network slicing in accordance with some aspects. [Figure 141] FIG. 141 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 142] FIG. 142 illustrates an exemplary message sequence chart illustrating message exchanges between a terminal device and a core network for network slice selection according to some aspects. [Figure 143] FIG. 143 illustrates a first exemplary method for conducting wireless communication in accordance with some aspects. [Figure 144] FIG. 144 illustrates a second exemplary method of conducting wireless communication in accordance with some aspects. [Figure 145]FIG. 145 illustrates a third exemplary method of conducting wireless communication in accordance with some aspects. [Figure 146] FIG. 146 illustrates an exemplary end-to-end network architecture with an edge computing server and a charging server in accordance with some aspects. [Figure 147] FIG. 147 illustrates an exemplary internal configuration of an edge computing server according to some aspects. [Figure 148] FIG. 148 illustrates an exemplary message sequence chart illustrating message exchanges between a terminal device, an edge computing server, and a charging server according to some aspects. [Figure 149] FIG. 149 illustrates a first exemplary method for managing a data stream in accordance with some aspects. [Figure 150] FIG. 150 illustrates a second exemplary method for managing a data stream in accordance with some aspects. [Figure 151] FIG. 151 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 152] FIG. 152 illustrates a first exemplary message sequence chart illustrating message exchanges between a terminal device and a network access node according to some aspects. [Figure 153] FIG. 153 illustrates a second exemplary message sequence chart illustrating message exchanges between a terminal device and a network access node according to some aspects. [Fig. 154] FIG. 154 illustrates a third exemplary message sequence chart illustrating message exchanges between a terminal device and a network access node according to some aspects. [Figure 155] FIG. 155 illustrates an example priority curve showing service priority disabling according to some aspects. [Figure 156] FIG. 156 illustrates an exemplary message sequence chart illustrating gradual service disabling according to some aspects. [Figure 157] FIG. 157 illustrates a first exemplary method for conducting wireless communication in accordance with some aspects. [Figure 158] FIG. 158 illustrates a second exemplary method of conducting wireless communication in accordance with some aspects. [Figure 159] FIG. 159 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 160] FIG. 160 illustrates an example method for detecting and responding to a thermal constraint scenario through throttling in an end device in accordance with some aspects. [Figure 161] FIG. 161 illustrates an example method for detecting and responding to a power constrained scenario through throttling in a terminal device in accordance with some aspects. [Figure 162] FIG. 162 illustrates an example method for detecting and responding to thermal and / or power constraint scenarios through throttling in an end device in accordance with some aspects. [Figure 163] FIG. 163 illustrates an exemplary configuration of a terminal device according to some aspects. [Fig. 164] FIG. 164 illustrates an example method for conducting wireless communication in accordance with some aspects. [Figure 165] FIG. 165 illustrates an exemplary wireless communication network according to some aspects. [Figure 166] FIG. 166 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 167] FIG. 167 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 168] FIG. 168 illustrates an exemplary end-to-end network architecture according to some aspects. [Figure 169] FIG. 169 illustrates an exemplary network situation according to some aspects. [Figure 170] FIG. 170 illustrates an exemplary internal configuration of an assist device according to some embodiments. [Figure 171]FIG. 171 illustrates a diagram of interactions between a terminal device, a network access node, and an assisting device according to some aspects. [Figure 172] FIG. 172 illustrates a first exemplary message sequence chart illustrating interactions between a terminal device, an assisting device, and a network access node according to some aspects. [Fig. 173] FIG. 173 illustrates a second exemplary message sequence chart illustrating interactions between a terminal device, an assisting device, and a network access node according to some aspects. [Fig. 174] FIG. 174 illustrates a third exemplary message sequence chart illustrating interactions between a terminal device, an assisting device, and a network access node according to some aspects. [Figure 175] FIG. 175 illustrates a fourth exemplary message sequence chart illustrating interactions between a terminal device, an assisting device, and a network access node according to some aspects. [Figure 176] FIG. 176 illustrates a fifth exemplary message sequence chart illustrating interactions between a terminal device, an assisting device, and a network access node according to some aspects. [Figure 177] FIG. 177 illustrates an exemplary network scenario involving support of multiple terminal devices by an assistive device according to some aspects. [Figure 178] FIG. 178 illustrates an example application in an Internet of Things (IoT) environment according to some aspects. [Figure 179] FIG. 179 illustrates a first exemplary method for performing wireless communication in a terminal device in accordance with some aspects. [Figure 180] FIG. 180 illustrates a second exemplary method of performing wireless communication in a communication device in accordance with some aspects. [Figure 181] FIG. 181 illustrates a third exemplary method of performing wireless communication in a communication device in accordance with some aspects. [Figure 182]FIG. 182 illustrates a first example network situation according to some aspects of the present disclosure. [Figure 183] FIG. 183 illustrates an exemplary internal configuration of a vehicle network access node according to some aspects. [Figure 184] FIG. 184 illustrates a first exemplary message sequence chart illustrating prediction and preloading of target data for a terminal device according to some aspects. [Figure 185] FIG. 185 illustrates a second exemplary message sequence chart illustrating prediction and preloading of target data for a terminal device according to some aspects. [Figure 186] FIG. 186 illustrates a second example network situation according to some aspects. [Figure 187] FIG. 187 illustrates an exemplary network situation showing terminal device and network access node connections according to some aspects. [Figure 188] FIG. 188 illustrates a third exemplary message sequence chart illustrating prediction and preloading of target data for a terminal device in accordance with some aspects. [Figure 189] FIG. 189 illustrates a first exemplary method for performing wireless communication in a local network access node of a vehicle in accordance with some aspects. [Figure 190] FIG. 190 illustrates a second exemplary method for performing wireless communication in a local network access node of a vehicle in accordance with some aspects. [Figure 191] FIG. 191 illustrates an exemplary wireless communication network according to some aspects. [Figure 192] FIG. 192 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 193] FIG. 193 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 194]FIG. 194 illustrates an exemplary network scenario including a roadside network access node and a vehicle or vehicle terminal device according to some aspects. [Figure 195] FIG. 195 illustrates an exemplary illustration of a MapReduce framework in accordance with some aspects. [Figure 196] FIG. 196 shows an example illustration of a coded MapReduce framework in accordance with some aspects. [Figure 197] FIG. 197 illustrates an exemplary network scenario including a vehicle or a group of vehicle terminal devices according to some aspects. [Figure 198] FIG. 198 illustrates an exemplary internal configuration of a vehicle terminal device according to some aspects. [Figure 199] FIG. 199 illustrates a first example method for wireless distributed computing in accordance with some aspects. [Figure 200] Diagram 200 illustrates a second example method for wireless distributed computing in accordance with some aspects. [Figure 201] Diagram 201 illustrates a progressive network situation for an end device to connect to a network in accordance with some aspects. [Figure 202] FIG. 202 illustrates an example logical, transport, and physical channel mapping scheme according to some aspects. [Figure 203] FIG. 203 illustrates an exemplary method for connecting to a network using a direct link in accordance with some aspects. [Figure 204] FIG. 204 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 205] FIG. 205 illustrates an example method for telemetry assistance over a direct link according to some aspects. [Figure 206] FIG. 206 illustrates a first example network situation in accordance with some aspects. [Figure 207] FIG. 207 illustrates a second example network situation in accordance with some aspects. [Figure 208]FIG. 208 illustrates a first example time chart illustrating a procedure for direct link sharing in accordance with some aspects. [Figure 209] FIG. 209 illustrates a third example network situation according to some aspects. [Figure 210] FIG. 210 illustrates a second example time chart illustrating a procedure for direct link sharing in accordance with some aspects. [Figure 211] FIG. 211 illustrates an example network situation related to the use of the Device Knowledge History (DKH) class in accordance with some aspects. [Figure 212] FIG. 212 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 213] FIG. 213 illustrates a first exemplary method for performing wireless communication in a terminal device in accordance with some aspects. [Figure 214] FIG. 214 illustrates a second exemplary method for conducting wireless communication in a terminal device in accordance with some aspects. [Figure 215] FIG. 215 illustrates a third exemplary method for conducting wireless communication in a terminal device in accordance with some aspects. [Figure 216] FIG. 216 illustrates an exemplary wireless communication network according to some aspects. [Figure 217] FIG. 217 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 218] FIG. 218 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 219] FIG. 219 illustrates an exemplary end-to-end network architecture according to some aspects. [Figure 220] FIG. 220 illustrates a first exemplary network situation in accordance with some aspects. [Figure 221] FIG. 221 illustrates a second example network situation according to some aspects. [Figure 222] FIG. 222 illustrates an exemplary internal configuration of a vehicle terminal device according to some aspects. [Figure 223] FIG. 223 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 224] FIG. 224 illustrates an example message sequence chart detailing the use of a sidelink channel for a vehicular communication link in accordance with some aspects. [Figure 225] FIG. 225 illustrates an example method for performing wireless communication in a vehicle terminal device in accordance with some aspects. [Figure 226] FIG. 226 illustrates an exemplary method for organizing vehicle-to-infrastructure (V2I) or vehicle-to-network (V2N) communications for a network access node according to some aspects. [Figure 227] FIG. 227 illustrates an exemplary method for terminal device management of device-to-device communications according to some aspects. [Figure 228] FIG. 228 illustrates an exemplary method for network management of device-to-device communications according to some aspects. [Figure 229] FIG. 229 illustrates an exemplary network scenario involving serving floating cells with directional antenna beams in accordance with some aspects. [Figure 230] FIG. 230 illustrates an exemplary internal configuration of a network access node according to some aspects. [Figure 231] FIG. 231 illustrates an exemplary internal configuration of an anchored air device according to some embodiments. [Figure 232] FIG. 232 illustrates an exemplary internal configuration of a secondary aeronautical device according to some embodiments. [Figure 233] FIG. 233 illustrates an example time-frequency radio resource allocation according to some aspects. [Figure 234] FIG. 234 illustrates an exemplary method for controlling a floating cell in a floating cell anchoring aeronautical device according to some embodiments. [Figure 235]FIG. 235 illustrates an exemplary method for operating a secondary aeronautical device in a floating cell containing multiple vehicles or aeronautical terminal devices in accordance with some aspects. [Figure 236] FIG. 236 illustrates an exemplary method of operating a network access node in accordance with some aspects. [Figure 237] FIG. 237 illustrates an exemplary method for network management of floating cells according to some aspects. [Figure 238] FIG. 238 illustrates an example method for operating an anchor drone within a floating cell according to some embodiments. [Figure 239] FIG. 239 illustrates an exemplary method of operating a secondary drone within a floating cell according to some embodiments. [Figure 240] FIG. 240 illustrates an exemplary network scenario showing deployment of mobile infrastructure nodes in accordance with some aspects. [Figure 241] FIG. 241 illustrates an exemplary internal configuration of a mobile infrastructure node having an autonomous driving system according to some embodiments. [Figure 242] FIG. 242 illustrates an example method for activating a mobile infrastructure node as a dynamic mobile infrastructure node in accordance with some aspects. [Figure 243] FIG. 243 illustrates an exemplary method of operating a mobile infrastructure node in accordance with some aspects. [Figure 244] FIG. 244 illustrates an example method for operating a vehicle as a mobile infrastructure node in accordance with some aspects. [Figure 245] FIG. 245 illustrates an example network situation involving deploying a mobile infrastructure node in response to a critical network situation in accordance with some aspects. [Figure 246] FIG. 246 illustrates an example configuration of a processing module of a mobile infrastructure node according to some aspects. [Figure 247]FIG. 247 illustrates an exemplary message sequence chart illustrating activation and operation of a mobile infrastructure node according to some aspects. [Figure 248] FIG. 248 illustrates an exemplary network scenario including a deployment of multiple mobile infrastructure nodes in accordance with some aspects. [Figure 249] FIG. 249 illustrates an exemplary internal configuration of a mobile infrastructure node having an autonomous driving system according to some embodiments. [Figure 250] FIG. 250 illustrates an example method according to some aspects for providing network connectivity to areas affected by network overload or outage at a mobile infrastructure node. [Figure 251] FIG. 251 illustrates an exemplary method according to some aspects for coordinating one or more mobile infrastructure nodes to respond to a network connectivity disruption. [Figure 252] FIG. 252 illustrates an exemplary network situation including a cluster of end devices utilizing the same identity in accordance with some aspects. [Figure 253] FIG. 253 illustrates an exemplary internal configuration of a terminal device according to some aspects. [Figure 254] FIG. 254 illustrates an example network scenario showing downlink communications in accordance with some aspects. [Figure 255] FIG. 255 illustrates an example network scenario showing uplink communications in accordance with some aspects. [Figure 256] FIG. 256 illustrates an exemplary method of terminal device communication according to some aspects. [Figure 257] FIG. 257 illustrates an exemplary method for managing a leader terminal device according to some aspects. [Figure 258] FIG. 258 illustrates an exemplary method of terminal device communication according to some aspects. [Figure 259] FIG. 259 illustrates a first exemplary method for performing wireless communication in a terminal device in accordance with some aspects. [Figure 260] FIG. 260 illustrates a second exemplary method for conducting wireless communication in a terminal device in accordance with some aspects. [Figure 261] FIG. 261 illustrates an exemplary network situation according to some aspects. [Figure 262] FIG. 262 illustrates an example time-frequency radio resource allocation associated with a contention-based access mode in accordance with some aspects. [Figure 263] FIG. 263 illustrates an example time-frequency radio resource allocation associated with a scheduling-based access mode in accordance with some aspects. [Figure 264] FIG. 264 illustrates an example group resource block according to some aspects. [Figure 265] FIG. 265 illustrates an exemplary network situation involving group resource block configuration transfer in accordance with some aspects. [Figure 266] FIG. 266 illustrates an exemplary network situation according to some aspects including group leader operation in an out-of-coverage situation. [Figure 267] FIG. 267 illustrates an exemplary method for provisioning wireless network resources according to application requirements according to some aspects. [Figure 268] FIG. 268 illustrates an example method for provisioning wireless network resources according to application requirements according to some aspects. [Figure 269] FIG. 269 illustrates an exemplary network scenario including a mobile cloud network according to some aspects. [Figure 270] FIG. 270 illustrates an example message sequence chart for configuring a temporary hierarchical network with network access nodes in accordance with some aspects. [Fig. 271] FIG. 271 illustrates an exemplary method for communication in a hierarchical network in accordance with some aspects. [Fig. 272]FIG. 272 illustrates an exemplary method for communication in a hierarchical network in accordance with some aspects. [Fig. 273] FIG. 273 illustrates an exemplary network scenario including a mobile cloud network according to some aspects. [Fig. 274] FIG. 274 illustrates an exemplary message sequence chart for dynamically modifying a hierarchical network by a network access node in accordance with some aspects. [Figure 275] FIG. 275 illustrates an exemplary network situation illustrating the impact of hierarchy changes on a mobile cloud network in accordance with some aspects. [Figure 276] FIG. 276 illustrates an exemplary network situation showing the impact of hierarchy changes on a mobile cloud network in accordance with some aspects. [Figure 277] FIG. 277 illustrates an exemplary method for dynamic communication in a hierarchical network in accordance with some aspects. [Fig. 278] FIG. 278 illustrates an exemplary method for dynamic communication over a wireless access network according to some aspects. DETAILED DESCRIPTION OF THE INVENTION
[0005] The following detailed description refers to the accompanying drawings, which show, by way of illustration, specific details and manner in which aspects of the disclosure may be practiced.
[0006] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.
[0007] The terms "plurality" and "multiple" in the description and claims (if any) explicitly refer to a quantity greater than one. Terms such as "group," "set," "collection," "series," "sequence," "grouping," and the like refer to a quantity equal to or greater than one, i.e., one or more. Any term expressed in plural form that does not explicitly state "plurality" or "multiple" refers to a quantity greater than one. The terms "proper subset," "reduced subset," and "smaller subset" refer to a subset of a set that is not identical to the set of a set, e.g., a subset that contains fewer elements than the set of a set.
[0008] As used herein, the term "software" refers to any type of executable instructions or set of instructions, including data embodied in the software. Software can also encompass firmware. Software can create, delete, or modify software, for example, through machine learning processes.
[0009] As used herein, a "module" is understood to refer to any type of function-realizing entity, which may include hardware-defined modules such as special-purpose hardware, software-defined modules such as processors executing software or firmware, and mixed modules containing both hardware-defined and software-defined components. Thus, a module may be an analog circuit or component, a digital circuit, a mixed-signal circuit or component, a logic circuit, a processor, a microprocessor, a central processing unit (CPU), an application processor, a graphics processing unit (GPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an integrated circuit, a discrete circuit, an application-specific integrated circuit (ASIC), or the like, or any combination thereof. Any other type of implementation of the respective functions described in further detail below may also be understood as a "module." It is understood that any two (or more) modules detailed herein may be implemented as a single module having substantially equivalent functionality, and conversely, any single module detailed herein may be implemented as two (or more) separate modules having substantially equivalent functionality. Furthermore, references to a "module" may refer to two or more modules collectively forming a single module.
[0010] As used herein, the terms "circuit" and "circuitry" can include software-defined circuits, hardware-defined circuits, and mixed hardware-defined and software-defined circuits.
[0011] As used herein, "memory" may be understood as a non-temporal, computer-readable medium in which data or information may be stored for retrieval. Memory may be used by being contained in, integrated with, or associated with a module. References to "memory" herein may therefore be understood to refer to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, magnetoresistive random access memory (MRAM), phase random access memory (PRAM), spin transfer torque random access memory (STT MRAM), solid-state storage, 3D memory, 3D crosspoint memory, NAND memory, magnetic tape, hard disk drives, optical drives, etc., or any combination thereof. Furthermore, it is understood that registers, shift registers, processor registers, data buffers, etc., are also encompassed by the term "memory" herein. It is understood that a single component referred to as "memory" or "a memory" may be implemented as multiple different types of memory and, therefore, may refer to a collective component that includes more than one type of memory. It will be readily understood that any single memory component may be separated into multiple collectively equivalent memory components, and vice versa. Furthermore, while a memory may be depicted as separate from one or more other components (as shown), it will be understood that the memory may be integrated with another component, such as on a common integrated chip.
[0012] Various aspects described herein may utilize any wireless communication technology, including Global System for Mobile Communications (GSM) wireless communication technology, General Packet Radio Service (GPRS) wireless communication technology, Enhanced Data Rates for GSM Evolution (EDGE) wireless communication technology, and / or Third Generation Partnership Project (3GPP) wireless communication technology, such as Universal Mobile Telecommunications System (UMTS), Forma (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE-Advanced), and the like. Advanced), Code Division Multiple Access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High Speed Circuit Switched Data (HSCSD), Universal Mobile Telecommunications System (UMTS (3G)), Wideband Code Division Multiple Access (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4G) (3GPP Release 8 (Pre-4G)), 3GPP Release 9 (3rd Generation Partnership Project Release 9), 3GPP Release 10 (3rd Generation Partnership Project Release 10), 3GPP Release 11 (3rd Generation Partnership Project Release 11), 3GPP Release 12 (3rd Generation Partnership Project Release 12), 3GPP Release 13 (3rd Generation Partnership Project Release 13), 3GPP Release 14 (3rd Generation Partnership Project Release 14), 3GPP Release 15 (3rd Generation Partnership Project Release 15), 3GPP Release 16(3rd Generation Partnership Project Release 16), 3GPP Release 17 (3rd Generation Partnership Project Release 17), 3GPP Release 18 (3rd Generation Partnership Project Release 18), 3GPP 5G, 3GPP LTE Extra, LTE-Advanced Pro, LAA (LTE Licensed-Assisted Access), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), CDMA2000 (Code Division Multiple Access 2000) (3G), Evolution Data Optimized or Evolution Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communications System (2nd Generation) (D-AMPS (2G)), Push-to-Talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Offentlig Landmobil Telefoni (Norwegian), Public Mobile Telephone), MTD (Swedish abbreviation for Mobiltelefonisystem D, Mobile Telephone System D), Autotel / PALM (Public Automated Land Mobile), ARP (Finnish for Autoradiopuhelin, "Vehicle Radio Telephone"), NMT (Nordic Mobile Telephone), Hicap (high capacity version of NTT), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), WiDEN (Wideband Integrated Enhanced Network), iBurst, UMA (Unlicensed MobileAccess), (also referred to as the 3GPP Generic Access Network or GAN standard), Zigbee, Bluetooth®, WiGig (Wireless Gigabit Alliance) standards, common mmWave standards (wireless systems operating in the 10-300 GHz and above, such as WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating in the 300 GHz and above and THz bands, (3GPP / LTE-based or IEEE 802.11p and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP Cellular V2X, and Dedicated Short Range Communications (DSRC) communication systems (such as Intelligent Transport Systems and others). These aspects may be applied in connection with any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, and (licensed) shared spectrum (Licensed Shared Access (LSA) for 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies, Spectrum Access System (SAS) for 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include International Mobile Telecommunications (IMT) spectrum.(including 450-470MHz, 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2500-2690MHz, 698-790MHz, 610-790MHz, 3400-3600MHz, etc.), IMT Advanced Spectrum, IMT-2020 Spectrum (expected to include 3600-3800MHz, the 3.5GHz band, the 700MHz band, and bands in the 24.25-86GHz range, etc.), FCC's "Spectrum Frontier" This could include spectrum available under the "Tier" 5G initiative (including 27.5-28 GHz, 29.1 GHz-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-43.5 GHz, 57-64 GHz, 71-78 GHz, 81-86 GHz, and 92-94 GHz), Intelligent Transportation Systems (ITS) band spectrum (5.9 GHz, typically 5.85-5.925 GHz), and future bands from 94-300 GHz and beyond. Furthermore, this scheme could be used secondary to bands such as TV white space bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being promising candidates. In addition to cellular applications, specific applications for vertical markets may be addressed, such as program making and special events (PMSE), medical, health, surgery, vehicles, low latency, and drones. Furthermore, this scheme can be applied hierarchically, for example based on preferred access to the spectrum, by introducing a hierarchical prioritization of usage for different types of users (e.g., low / medium / high priority), e.g., first tier users followed by second tier users, followed by third tier users, etc. Various OFDM flavors (e.g., Cyclic Prefix OFDM (CP-OFDM), Single Carrier FDMA (SC-FDMA), Single Carrier OFDM (SC-OFDM), Filter Bank Based Multicarrier (FBMC), OFDMA (OFDMA), etc.) and especially 3GPP NR (NewVarious aspects may also be applied to OFDM (Radio) by allocating OFDM carrier data bit vectors to corresponding symbol resources. These aspects may be applied in any of the following contexts: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), infrastructure-to-vehicle (I2V), or vehicle-to-everything (V2X) contexts, such as a DSRC or LTE V2X context.
[0013] The term "base station" when used with respect to an access node of a mobile communication network may be understood as a macro base station (e.g., in the case of cellular communications), a micro / pico / femto base station, a Node B, an evolved Node B (eNB), a home eNodeB, a remote radio head (RRH), a relay point, or an access point (e.g., an AP for Wi-Fi, WLAN, WiGig, millimeter wave (mmWave), etc.). As used herein, a "cell" in the context of communications may be understood as an area (e.g., a public place) or space (e.g., a multi-story building or airspace) served by a base station or access point. A base station may be mobile, for example, installed in a vehicle, and the area or space covered may move accordingly. Thus, a cell may be covered by a set of co-located transmit and receive antennas, each antenna covering and serving a particular sector of the cell. A base station or access point may serve one or more cells, each characterized by a distinct communication channel or standard (e.g., base stations offering 2G, 3G, and LTE service). Macrocells, microcells, femtocells, and picocells may have different cell sizes and ranges, may be static or dynamic (e.g., cells installed on unmanned aerial vehicles or balloons), or may dynamically change their characteristics (e.g., from macrocell to picocell, from static to dynamic deployment, from omnidirectional to directional, or from broadcast to narrowcast). Communication channels may be narrowband or broadband. They may also use carrier aggregation across wireless communication technologies and standards or flexibly adapt bandwidth to communication needs. Furthermore, terminal devices may include or act as base stations, access points, relays, or other network access nodes.
[0014] For purposes of this disclosure, a wireless communication technology or standard may be categorized as either a short-range wireless communication technology or a cellular wide-area wireless communication technology. Furthermore, a wireless communication technology or standard may be categorized as human-to-human, human-to-machine, machine-to-human, machine-to-machine, device-to-device, point-to-point, point-to-multipoint, broadcast, peer-to-peer, full-duplex, half-duplex, omnidirectional, beamforming, beam-shaping, and / or directional. Furthermore, a wireless communication technology or standard may be categorized as using electromagnetic waves, light waves, or a combination thereof.
[0015] Short-range wireless communication technologies include, for example, Bluetooth, WLAN (e.g., according to any IEEE 802.11 standard), WiGig (e.g., according to any IEEE 802.11 standard), millimeter wave, and other similar wireless communication technologies.
[0016] Cellular wide area wireless communication technologies include, for example, Global System for Mobile Communications (GSM), Code Division Multiple Access 2000 (CDMA2000), Universal Mobile Telecommunication System (UMTS), Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A), General Packet Radio Service (GPRS), Evolution-Do (EV-DO), Enhanced Data Rates for GSM Evolution (EDGE), High Speed Packet Access (HSPA including High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), HSDPA+ (HSDPA Plus), and HSUPA+ (HSUPA Plus)), Worldwide Interoperability for Microwave Access (WiMax), next generation cellular standards such as 5G (e.g., millimeter wave (mmWave), 3GPP New Radio (NR)), 6G, and other similar wireless communication technologies. Cellular wide area wireless communication technologies also include "small cells," which are technologies such as microcells, femtocells, and picocells. Cellular wide area wireless communication technologies may be generally referred to herein as "cellular" communication technologies. Furthermore, as used herein, the term GSM refers to both circuit-switched and packet-switched GSM, including, for example, GPRS, EDGE, and any other related GSM technologies. Similarly, the term UMTS refers to both circuit-switched and packet-switched GSM, including, for example, HSPA, HSDPA / HSUPA, HSDPA+ / HSUPA+, and any other related UMTS technologies. Further communication technologies include line-of-sight (LiFi) communication technologies.It will be understood that the exemplary situations detailed herein are illustrative in nature and may therefore be similarly applied to various other mobile communication technologies, both existing and yet to be developed, particularly where such mobile communication technologies share similar features to those disclosed with respect to the following examples.
[0017] As used herein, the term "network" refers to both the access section of the network (e.g., the Radio Access Network (RAN) section) and the core section of the network (e.g., the core network section) in relation to a communication network, such as a mobile communication network, but also encompasses mobile access, backhaul, server, backbone, and gateway / switching elements to other networks of the same or different types in an end-to-end system (including peer-to-peer, device-to-device, and / or machine-to-machine communications). As used herein with respect to a mobile terminal, the term "radio idle mode" or "radio idle state" refers to a radio control state in which the mobile terminal is not assigned at least one dedicated communication channel of the mobile communication network. The term "radio connected mode" or "radio connected state" refers to a radio control state in which the mobile terminal is assigned at least one dedicated uplink communication channel of the mobile communication network. The uplink communication channel may be a physical channel or a virtual channel. The idle or connected mode is capable of connection switching or packet switching.
[0018] The term "terminal device" includes, for example, mobile phones, tablets, laptops, computers, Internet of Things (IoT) devices, wearables, embedded devices, machine-type communication devices, etc., and vehicles, for example, automobiles, trucks, buses, bicycles, robots, motorcycles, trains, ships, submarines, drones, airplanes, balloons, satellites, spacecraft, etc. Vehicles can be autonomously controlled, semi-autonomously controlled, or under human control, for example, according to one of the SAE J3016 levels of driving automation. The level of driving automation can be selected based on past, present, and estimated future states of the vehicle, other vehicles, traffic, people, or the environment.
[0019] Unless explicitly stated otherwise, the term "transmission" encompasses both direct (point-to-point) and indirect (through one or more relay points) transmission from an end device to a network access node or relay node, from an end device to another end device, and from a network access node or relay node to a backbone. Similarly, the term "reception" encompasses both direct and indirect reception between an end device, a network access node or relay node, and a backbone. The term "communication" encompasses either or both transmission and reception, e.g., unidirectional or bidirectional communication in either or both the inbound and outbound directions. Furthermore, the terms "transmission," "reception," "communication," and other similar terms encompass both physical transmission (e.g., transmission of radio signals) and logical transmission (e.g., transmission of logical data through software-level connections). For example, a processor can transmit or receive data in the form of radio signals with other processors, with physical transmission and reception being handled by radio layer components such as RF transceivers and antennas, and logical transmission and reception being performed by a processor. The term "operation" encompasses both direct operation via mathematical expressions / formulas / relationships and indirect operation via lookup or hash tables and other indexing or searching operations.
[0020] FIG. 1 illustrates an exemplary depiction of a communication network 100 according to some aspects. As illustrated in FIG. 1, the communication network 100 may be an end-to-end network spanning a wireless access network 102 to backbone networks 132 and 142. The backbone networks 132 and 142 may be implemented primarily as wired networks. The network access nodes 120-126 may be wireless access networks and may transmit and receive data wirelessly with the terminal devices 104-116 to provide wireless access connectivity to the terminal devices 104-116. The terminal devices 104-116 may utilize the wireless access connectivity provided by the wireless access network 102 to exchange data in end-to-end connections with servers in the backbone networks 132 and 142. The wireless access connections between the terminal devices 104-116 and the network access nodes 120-126 may be implemented according to one or more radio access technologies, and each terminal device may transmit and receive data with a corresponding network access node according to the protocols of the particular radio access technology governing the wireless access connection. In some aspects, one or more of the terminal devices 104-116 may utilize licensed or unlicensed spectrum for the wireless access connection. In some aspects, one or more of the terminal devices 104-116 may communicate directly with one another according to any of a wide variety of device-to-device (D2D) communication protocols.
[0021] 1, in some aspects, terminal devices such as terminal devices 106-110 may rely on forwarding links provided by terminal device 104, which may act as a gateway or relay between terminal devices 106-110 and network access node 120. In some aspects, terminal devices 106-110 may be configured according to a mesh or multi-hop network and may communicate with terminal device 104 via one or more other terminal devices. The configuration of the terminal device(s), e.g., a mesh or multi-hop configuration, may change dynamically depending on, for example, terminal or user requirements, the current wireless or network environment, application and service availability or performance, or communication or access costs.
[0022] In some aspects, a terminal device, such as terminal device 116, may transmit and / or receive data at network access node 126 using relay node 118, which may perform relayed transmission between terminal device 116 and network access node 126, e.g., via a simple relay scheme or a more complex process-and-forward scheme. The relay may be implemented as a series of relays or may use opportunistic relaying, in which the best or approximately best relay or series of relays at a given time or time interval is used.
[0023] In some aspects, network access nodes, such as network access nodes 124 and 126, may interface to core network 130, which may provide routing, control, and management functions governing both wireless access connectivity and core network and backhaul connectivity. As shown in FIG. 1 , core network 130 may interface to backbone network 142 and may perform network gateway functions to manage data transfer between network access nodes 124 and 126 and various servers on backbone network 142. In some aspects, network access nodes 124 and 126 may be directly connected to each other via a direct interface, which may be wired or wireless. In some aspects, a network access node, such as network access node 120, may interface directly to backbone network 132. In some aspects, a network access node, such as network access node 122, may interface to backbone network 132 via router 128.
[0024] The backbone networks 132 and 142 may include various internal and external servers 134-138 and 144-148. The terminal devices 104-116 may transmit and receive data with the servers 134-138 and 144-148 in logical software-level connections that rely on radio access networks and other intermediate interfaces for lower-layer transport. Thus, the terminal devices 104-116 may utilize the communications network 100 as an end-to-end network to transmit and receive data that may include internet and application data in addition to other types of user-plane data. In some aspects, the backbone networks 132 and 142 may interface through gateways 140 and 150, which may be connected at an interchange 152. 1 Common Channel
[0025] Receiving or transmitting discovery and control information can be an important part of the wireless network activity of a terminal device or network access node. A terminal device may reduce operating power and increase operating time and performance by intelligently discovering or scanning the wireless environment for network access nodes and standards or other terminal devices. A terminal device can scan discovery information to detect and identify available communication technologies and standards, parameters of these available communication technologies and standards, and nearby network access nodes or other terminal devices. In another aspect, there may be a known or occasionally published schedule that identifies one or more access technologies or standards, or one or more channels that can be scanned with priority to reduce scanning effort. In yet another aspect, discovery or control information may be communicated as payload or as part of a channel payload, for example, as a web or internet or cloud service, and using preferred or advertised channels to reduce scanning effort. After identifying the presence of a nearby network access node or other terminal device through receipt of such discovery information, the terminal device may establish a wireless connection with the selected network access node or other terminal device to exchange data and / or continue other wireless interactions with the network access node or other terminal device (e.g., radio measurements or reception of broadcast information). The selection of a network access node or other terminal may be based on terminal or user requirements, past, present, and expected future radio and environmental conditions, application and service availability or performance, or communication or access costs.
[0026] The terminal device may also receive control information that provides control information or parameters to ensure that both incoming and outgoing data are received and transmitted appropriately with a selected network access node or other terminal device, e.g., in accordance with a wireless standard, a proprietary standard, or a mixture thereof. The control parameters may include, for example, time and frequency scheduling information, coding / modulation schemes, power control information, paging information, retransmission information, connection / mobility information, and / or other such information that specifies when and how data should be transmitted and received. The terminal device may then use the control parameters to control data transmission and reception with the network access node or other terminal device, enabling the terminal device to successfully exchange user and other data traffic with the network access node or other terminal device over a wireless connection. The network access node may provide data to the terminal device, including voice, multimedia (e.g., audio / video / images), Internet and / or other web browsing data, or may interface with an underlying communications network (e.g., a core network) that may provide access to other applications and services, e.g., using cloud technology.
[0027] Therefore, to operate effectively on a wireless communication network, it may be important for a terminal device to properly receive, transmit, and interpret both discovery and control information. To this end, it may be desirable for the terminal device to receive discovery and control information on appropriate frequency resources at the correct time (e.g., in accordance with scheduling parameters), demodulate and decode the received discovery and control information (e.g., in accordance with format parameters) in accordance with a modulation and coding scheme, and maintain low effort to recover the original data or find the discovery and control information.
[0028] The procedures for receiving and interpreting such information according to corresponding scheduling and formatting parameters may be defined by a specific protocol associated with the radio access technology used by the wireless communication network. For example, a first wireless network may utilize a first radio access technology (e.g., a RAT such as 3GPP radio access technology, Wi-Fi, and Bluetooth), and the first radio access technology may have a specific radio access protocol that defines scheduling and formatting for the transmission and reception of discovery information, control information, and user traffic data. Network access nodes and terminal devices operating on the first wireless network may follow the radio protocol of the first radio access technology to properly transmit and receive wireless data over the first wireless network.
[0029] Each radio access technology may define different scheduling and format parameters for discovery and control information. For example, a second radio access technology may specify different scheduling and format parameters for discovery and control information (in addition to user data traffic) than a first radio access technology. Accordingly, a terminal device may receive discovery and control information for a first wireless network than for a second wireless network using different reception procedures; for example, this may include receiving different discovery signals / waveforms, receiving discovery and control information at different timings, receiving discovery and control information in different formats, receiving discovery and control information on different channels, and / or using different frequency resources.
[0030] The present disclosure relates to terminal devices configured to operate with multiple radio access technologies. A terminal device configured to operate with multiple radio access technologies (e.g., first and second RATs) may be configured according to the radio protocols of both the first and second RATs (and similarly for operation with additional RATs). For example, an LTE network access node (e.g., eNodeB) may transmit discovery and control information with different time and frequency scheduling (including periodicity, center frequency, bandwidth, duration, etc.) and in different formats (including information type / content, modulation and coding scheme, data rate, etc.) than a Wi-Fi network access node (e.g., WLAN AP). Thus, a terminal device designed for both LTE and Wi-Fi operation may operate according to a specific LTE protocol to properly receive LTE discovery and control information, and may also operate according to a specific Wi-Fi protocol to properly receive Wi-Fi discovery and control information. Terminal devices configured to operate with additional radio access networks, such as UMTS, GSM, or Bluetooth, may similarly be configured to transmit and receive radio signals according to the corresponding respective access protocols. In some aspects, a terminal device may have dedicated hardware and / or software components for each supported radio access technology.
[0031] In some aspects, a terminal device may be configured to omit periodic scanning of the wireless environment for available network access nodes, other terminal devices, and communication technologies and standards. This allows the terminal device to reduce operating power consumption and increase operating time and performance by omitting periodic scanning of the wireless environment for available network access nodes, other terminal devices, and communication technologies and standards. Instead of performing periodic comprehensive scans of the wireless environment, the terminal device may be configured to scan a dedicated discovery or control channel. In some aspects, the dedicated discovery or control channel may be provided by the network access node or other terminal device. In other aspects, the network access node or other terminal device may signal which discovery or control channel should be used by the terminal device.
[0032] Alternatively or additionally, in some aspects, a network access node or other terminal device may act as a proxy and relay discovery or control information over a dedicated channel. For example, other resource-rich terminal devices may relay discovery or control information to nearby terminal devices over low-power, short-range communications such as Bluetooth or 802.15.4 Low Energy (LE).
[0033] FIG. 2 illustrates an exemplary wireless network configuration according to some aspects. As shown in FIG. 2, terminal devices 200 and 202 can interact with one or more network access nodes, including network access nodes 210-230. In some aspects, network access nodes 210 and 212 may be network access nodes for a first radio access technology (RAT), and network access nodes 214-230 may be network access nodes for a second RAT. Furthermore, in some aspects, network access nodes 210 and 212 may be located at a cell site or radio tower (or similar network broadcast point) that includes cells of additional radio access technologies. For example, one or more cells of a third RAT, a fourth RAT, and / or a fifth RAT may be located at the cell site by network access nodes 210 and / or 212. In an exemplary situation, network access node 210 may be an LTE network access node, which may coexist with any one or more of UMTS, GSM, mmWave, 5G, Wi-Fi / WLAN, and / or Bluetooth. While the embodiments detailed below may refer to a wireless access network, the embodiments provided below may use any other combination of wireless access networks, and network access nodes 210-212 and 214-230 may similarly utilize any type of wireless access technology that conforms to a wireless access network. For example, the embodiments provided below may use LTE-Advanced and Wi-Fi / WLAN.
[0034] Terminal device 200 and terminal device 202 may be any type of terminal device, such as a cellular phone, user equipment, tablet, laptop, personal computer, wearable, multimedia playback and / or other handheld electronic device, consumer / home / office / commercial appliance, vehicle, or any type of electronic device capable of wireless communication.
[0035] In some aspects, terminal devices 200 and 202 may be configured to operate according to multiple radio access networks, such as both LTE and Wi-Fi access networks. Accordingly, terminal devices 200 and 202 may include hardware and / or software specifically configured to transmit and receive radio signals according to their respective access protocols. Without loss of generality, terminal device 200 (and / or 202) may be configured to support other radio access technologies, such as other cellular, short-range, and / or metropolitan area radio access technologies. For example, in an exemplary configuration, terminal device 200 may be configured to support LTE, UMTS (both circuit-switched and packet-switched), GSM (both circuit-switched and packet-switched), and Wi-Fi. In another exemplary configuration, terminal device 200 may additionally or alternatively be configured to support 5G and mmWave radio access technologies.
[0036] 3 illustrates an exemplary internal configuration of a terminal device 200 according to some aspects. As illustrated in FIG. 3, the terminal device 200 may include an antenna system 302, a communication system 304 including communication modules 306a-306e and a controller 308, a data source 310, a memory 312, and a data sink 314. Although not explicitly illustrated in FIG. 3, the terminal device 200 may include one or more additional hardware, software, and / or firmware components (e.g., a processor / microprocessor, a controller / microcontroller, other dedicated or general-purpose hardware / processors / circuitry), peripheral devices, memory, a power supply, external device interfaces, subscriber identity modules (SIMs), user input / output devices (e.g., a display, a keypad, a touchscreen, a speaker, external buttons, a camera, a microphone, etc.).
[0037] In a simplified operational overview, terminal device 200 may transmit and receive wireless signals over one or more wireless access networks. Controller 308 may direct such communication functions of terminal device 200 in accordance with a radio access protocol associated with each wireless access network and may exercise control over antenna system 302 to transmit and receive wireless signals in accordance with the format and scheduling parameters defined by each access protocol.
[0038] The terminal device 200 may transmit and receive wireless signals through an antenna system 302, which may be an antenna array including multiple antennas and may further include analog antenna combining and / or beamforming circuitry. The antennas of the antenna system 302 may be individually assigned or commonly shared among one or more communication modules 306a-306e. For example, one or more communication modules 306a-306e may have their own dedicated antennas, while other communication modules 306a-306e may share a common antenna.
[0039] The controller 308 may maintain RAT connections through the communication modules 306a-306d by providing and receiving upper layer uplink and downlink data, in addition to controlling the transmission and reception of such data as wireless signals via the communication modules 306a-306d. The communication modules 306a-306d may transmit and receive wireless signals via the antenna system 302 according to their respective radio access technologies and may be responsible for corresponding RF and PHY level processing. In some aspects, the first communication module 306a may be assigned to a first RAT, the second communication module 306b may be assigned to a second RAT, the third communication module 306c may be assigned to a second RAT, and the fourth communication module 306d may be assigned to a fourth RAT. As described in further detail below, the common discovery module 306e may be configured to monitor and process common discovery channels.
[0040] In the receive path, the communications modules 306-306d may receive analog radio frequency signals from the antenna system 302 and perform analog and digital RF front-end processing on the analog radio frequency signals to generate digital baseband samples (e.g., in-phase / quadrature (IQ) samples). Accordingly, the communications modules 306a-306d may include analog and / or digital receive components, including amplifiers (e.g., low-noise amplifiers (LNAs)), filters, RF demodulators (e.g., RF IQ demodulators), and analog-to-digital converters (ADCs) for converting the received radio frequency signals to digital baseband samples. Following RF demodulation, the communications modules 306a-306d may perform PHY layer receive processing on the digital baseband samples, including one or more of error detection, forward error correction decoding, channel decoding and deinterleaving, physical channel demodulation, physical channel demapping, radio measurements and searches, frequency and time synchronization, antenna diversity processing, rate matching, and retransmission processing. In some embodiments, the communications modules 306a-306d may include hardware accelerators that can be assigned to such processing-intensive tasks. The communications modules 306a-306d may also provide the resulting digital data stream to the controller 308 for further processing in accordance with the associated wireless access protocol.
[0041] While depicted as a single component in FIG. 3, the communications modules 306a-306d may each be implemented as separate RF and PHY modules including their own RF and PHY components and functionality. Furthermore, one or more such RF and PHY modules of multiple communications modules 306a-306d may be integrated into a common component, such as a common RF front-end module shared among multiple radio access technologies. Accordingly, such variations are recognized as providing similar functionality and are within the scope of this disclosure.
[0042] In the transmit path, the communications modules 306a-306d may receive digital data streams from the controller 308 and perform PHY layer transmit processing, including one or more of error detection, forward error correction coding, channel coding and interleaving, physical channel modulation, physical channel mapping, antenna diversity processing, rate matching, power control and weighting, and / or retransmission processing, to generate digital baseband samples. The communications modules 306a-306d then perform analog and digital RF front-end processing on the digital baseband samples to generate analog radio frequency signals that are provided to the antenna system 302 for wireless transmission. Accordingly, the communications modules 306a-306d may include analog and / or digital transmit components, including amplifiers (e.g., power amplifiers (PAs), filters, RF modulators (e.g., RF IQ modulators), and digital-to-analog converters (DACs)), to mix the digital baseband samples to generate analog radio frequency signals for wireless transmission by the antenna system 302.
[0043] In some embodiments, one or more of the communications modules 306a-306d may be structurally implemented as hardware-defined modules, such as one or more dedicated hardware circuits or FPGAs. In some embodiments, one or more of the communications modules 306a-306d may be structurally implemented as software-defined modules, such as one or more processors executing program code defining operation, control, and I / O instructions (e.g., software and / or firmware) stored on a non-temporary computer-readable storage medium. In some embodiments, one or more of the communications modules 306a-306d may be structurally implemented as a combination of hardware-defined and software-defined modules.
[0044] Although not explicitly shown in FIG. 3, the communications modules 306a-306d may include a controller, such as a processor, configured to control various hardware and / or software processing components of the communications modules 306a-306d in accordance with physical layer control logic defined by the communications protocol for the associated radio access technology.
[0045] The communications modules 306a-306d are responsible for RF and PHY processing according to their respective radio access protocols, while the controller 308 is responsible for upper layer control and may be embodied as a processor configured to execute protocol stack software code that directs the controller 308 to operate in accordance with the associated radio access protocol logic. The controller 308 may direct upper layer control via the communications modules 306a-306d, in addition to providing uplink data for transmission and receiving downlink data for further processing.
[0046] 3 as a single component, the controller 308 may be implemented as multiple separate controllers, each tasked with executing the protocol stack logic for one or more of the communication modules 306a-306d, e.g., a dedicated controller for each of the communication modules 306a-306d. The controller 308 is responsible for controlling the antenna system 302 and the communication modules 306a-306d in accordance with the communication protocols of the supported radio access technologies, and thus may represent the access and non-access stratums (NAS) (including Layer 2 and Layer 3) of the supported radio access technologies.
[0047] 3, the terminal device 200 may also include a data source 310, a memory 312, and a data sink 314, where the data source 310 may include a source of communication data above the controller 308 (e.g., above NAS / Layer 3), and the data sink 314 may include a destination of communication data above the controller 308 (e.g., above NAS / Layer 3), which may include, for example, an application processor of the terminal device 200, which may be configured to execute various applications and / or programs of the terminal device 200 at an application layer of the terminal device 200, such as an operating system (OS), a user interface (UI) for supporting user interaction with the terminal device 200, and / or various user applications. The application processor may interface with the controller 308 at the application layer (data source 310 / data sink 314) for transmitting and receiving user data, such as voice data, audio / video / image data, messaging data, application data, and basic Internet / web access data, over the wireless network connection provided by the communication system 304. The data source 310 and data sink 314 may further represent various user input / output devices of the terminal device 200, such as a display, keypad, touchscreen, speaker, external buttons, camera, and microphone, that may allow a user of the terminal device 200 to control various communication functions of the terminal device 200 related to user data. The memory 312 includes memory components of the terminal device 200, such as a hard drive or other such memory device. Although not explicitly shown in FIG. 3, various other components of the terminal device 200 shown in FIG. 3 may include integrated persistent and non-persistent memory components.These components may be used, for example, to store software program code and / or buffer data. 1.1 Common Channel #1
[0048] In an exemplary network scenario such as that shown in FIG. 2, a terminal device 200 may identify neighboring wireless networks (e.g., one or more network access nodes 210-230) by scanning discovery signals broadcast by the network access nodes. In many conventional communication scenarios, each network access node may broadcast its corresponding discovery signal in a particular discovery channel (e.g., in a radio frequency channel that may be a single or multi-carrier frequency channel depending on the corresponding radio access technology) according to RAT-specific scheduling and format parameters. For example, each radio access technology may define a particular discovery signal (e.g., having a particular coding and modulation format) to be broadcast in a particular time-frequency resource (e.g., a particular carrier or subcarrier in a particular time period). For example, network access nodes 210 and 212 may broadcast discovery signals for a first RAT in one or more discovery channels for the first RAT (which may or may not be the same physical frequency channel, e.g., different cells of the first RAT may utilize different discovery channels), while network access nodes 214-230 may broadcast discovery signals for a second RAT in one or more discovery channels for the second RAT (which may or may not be the same physical frequency channel).
[0049] Depending on the particular RAT protocol, the RAT-specific discovery channel may overlap with the RAT-specific operating channel. For example, in an exemplary Wi-Fi environment, a Wi-Fi network access node may broadcast Wi-Fi discovery signals, such as beacons, in a Wi-Fi operating channel. Thus, the Wi-Fi operating channel may also serve as a discovery channel that terminal devices may monitor to detect beacons (Wi-Fi discovery signals) for detecting Wi-Fi network access nodes. In an exemplary LTE environment, an LTE network access node may broadcast LTE discovery signals, such as primary synchronization sequences (PSSs) and secondary synchronization sequences (SSSs), on a set of center subcarriers of the LTE operating channel (and may broadcast other LTE discovery signals, such as master information blocks (MIBs) and system information blocks (SIBs), on generally any subcarrier of the LTE operating channel). In other RATs, discovery channels may be allocated separately from operating channels. This disclosure covers all such cases, and thus the RAT-specific discovery channel may be the same in frequency as the RAT-specific operating channel, may overlap in frequency with the RAT-specific operating channel, and / or may be allocated separately in frequency from the RAT-specific operating channel. Thus, a terminal device may perform discovery for a given RAT by monitoring radio signals on the RAT-specific discovery channel, which may or may not overlap with the RAT-specific operating channel. Furthermore, there may be a predetermined set of operating channels for a particular RAT (e.g., LTE center frequencies specified by 3GPP, Wi-Fi operating channels specified by IEEE, etc.).Thus, in some aspects where the discovery channel overlaps with the operating channel, the terminal device may scan the discovery channel by cycling through a predetermined set of different operating channels, e.g., by cycling through one or more LTE center frequencies to detect LTE discovery signals, or by cycling through one or more Wi-Fi operating channels to detect Wi-Fi discovery signals.
[0050] Thus, in many conventional wireless communication scenarios, terminal device 200 may monitor one or more discovery channels to discover network access nodes of various RATs. For example, to discover a network access node of a first RAT, terminal device 200 may monitor the discovery channel of the first RAT for discovery signals (where, as described above, the discovery channel may or may not overlap with the operating channel of the first RAT). In some aspects, discovery signals for a particular radio access technology may be defined by a particular standard or protocol, such as a particular signal format and / or a particular transmission schedule. Thus, terminal device 200 may discover a cell of the first RAT by scanning for discovery signals in the discovery channel of the first RAT. Thus, terminal device 200 may attempt to detect a network access node of the first RAT by monitoring wireless signals in accordance with the specifications of the first RAT (e.g., the signal format and scheduling of the discovery signal, the discovery channel frequency, etc., which may be standardized or defined in a protocol for the first RAT). In doing so, terminal device 200 may receive and identify discovery signals broadcast by network access nodes 210 and 212, and subsequently identify, or "discover," network access nodes 210 and 212. Similarly, terminal device 200 may attempt to discover network access nodes of the second RAT by monitoring wireless signals in accordance with the specifications of the second RAT (e.g., the signal format and scheduling of the discovery signals, discovery channel frequencies, etc., which may be standardized or defined in a protocol for the first RAT). Thus, terminal device 200 may similarly discover network access nodes 214-230. As mentioned above, in some aspects, network access nodes 210 and 212 may further provide carriers for a third RAT and / or a fourth RAT, which terminal device 200 may discover by monitoring wireless signals in accordance with the third and fourth RATs, respectively.
[0051] As described above, the communication modules 306a-306d are responsible for RF and PHY level signal processing for each wireless access technology. Thus, the controller 308 may maintain different wireless access connections through one or more of the communication modules 306a-306d by utilizing the communication modules 306a-306d to transmit and receive data. The controller 308 may maintain some wireless access connections independently of each other and may maintain other wireless access connections in coordination with other wireless access connections.
[0052] For example, in some aspects, the controller 308 may maintain the radio access connections for the first communication module 306a (first RAT connection), the second communication module 306b (second RAT connection), the third communication module 306c (third RAT connection), and the fourth communication module 306d (fourth RAT connection) in association with one another according to a master / slave / RAT system, etc. Conversely, in some aspects, the controller 308 may maintain the fourth RAT connection for the fourth communication module 306d substantially separate from the cellular RAT connections of the first communication module 306a, the second communication module 306b, and the third communication module 306c, e.g., not as part of the same master / slave RAT system.
[0053] The controller 308 may process the RAT connection of each of the communication modules 306a-306d according to a corresponding radio access protocol, which may include triggering a discovery procedure. The controller 308 may trigger the discovery procedure separately in each of the communication modules 306a-306d, the specific timing of which may depend on the specific radio access technology and the current state of the RAT connection. Thus, at any given time, some or all of the communication modules 306a-306d may or may not be performing discovery.
[0054] For example, during initial power-up operations of the terminal device 200, the controller 308 may trigger discovery for the communication modules 306a-306d as each RAT connection attempts to connect to an appropriate network access node. In some aspects, the controller 308 may manage the RAT connections according to a prioritized hierarchy, e.g., the controller 308 may prioritize the first RAT over the second and third RATs. For example, the controller 308 may operate the first, second, and third RATs in a master / slave RAT system, where one RAT is primarily active (e.g., the master RAT) and the other RAT (e.g., the slave RAT) is idle. Thus, the controller 308 may attempt to maintain the first RAT as the master RAT and may fall back to the second or third RAT if there are no live cells available for the first RAT. Thus, in some aspects, the controller 308 may trigger discovery for the communications module 306a after initial power-on and may proceed to trigger discovery for the second or third RAT if a cell of the first RAT is not found. In an exemplary situation, the first RAT may be, for example, LTE, and the second and third RATs may be "legacy" RATs such as UMTS or GSM.
[0055] After the RAT connection is established, the controller 308 may periodically trigger discovery in one or more communication modules 306a-306d based on the current radio access conditions of each RAT connection. For example, the controller 308 may establish the first RAT connection with a cell of the first RAT discovered during initial discovery by the first communication module 306a. However, if the first RAT connection becomes poor (e.g., due to weak signal strength or poor signal quality, or if the radio link fails and needs to be re-established), the controller 308 may trigger a new discovery procedure in the first communication module 306a to detect other neighboring cells of the first RAT and potentially measure and switch (by handover or reselection) to another cell of the first RAT. The controller 308 may also perform inter-RAT discovery by triggering a new discovery procedure in the second communication module 306b and / or the third communication module 306c. Depending on the individual state of the RAT connections of one or more communication modules 306a-306d, zero or more communication modules 306a-306d may be performing discovery procedures at any given time.
[0056] Because each of the communication modules 306a-306d may be tasked with discovering various types of radio access networks (each of which may have unique discovery signals with respect to both scheduling and format), the communication modules 306a-306d may perform RAT-specific processing on received radio signals to properly perform discovery. For example, because each radio access technology may broadcast a unique discovery signal on a unique discovery channel, the communication modules 306a-306d may scan different discovery channels and utilize different discovery signal detection techniques (e.g., depending on each target discovery signal, such as signal format and / or scheduling) to discover neighboring network access nodes for each respective radio access technology. For example, the first communication module 306a may acquire radio signals in various frequency bands and perform different signal processing for detection of a first RAT's discovery signal than the fourth communication module 306d for detection of a fourth RAT's discovery signal; similarly, this may hold for the second communication module 306b and the third communication module 306c.
[0057] Because the discovery procedure may involve detecting previously unknown network access nodes, time synchronization information for the network access nodes is likely unavailable for discovery. Thus, the terminal device 200 may not have specific knowledge of when discovery signals for each radio access technology are broadcast. For example, in an exemplary environment where the first radio access technology is LTE, when attempting to discover an LTE cell, the first communication module 306a may not have any timing reference point indicating when PSS and SSS sequences and MIBs / SIBs are broadcast by the LTE cell. The communication modules 306a-306d may face a similar situation for various different radio access technologies. Thus, depending on which communication module 306a-306d is currently tasked with performing discovery (and depending on the current state of ongoing communication connections for each communication module), the communication modules 306a-306d may continuously scan the corresponding detection channels to effectively detect discovery signals. Thus, each of the communication modules 306a-306d performing discovery at a given time may be actively powered and perform active receive processing on their respective assigned frequency bands to discover potential network access nodes.
[0058] The communications modules 306a-306d may perform constant receiving and processing, or may only perform periodic receiving and processing depending on the targeted radio access technology. Nevertheless, frequent operation of the communications modules 306a-306d (in addition to the respective antennas of the antenna system 302) may have a significant power penalty on the terminal device 200. Unfortunately, such a power penalty may be unavoidable because the communications modules 306a-306d generally need to operate continuously to discover nearby wireless networks. If the terminal device 200 is battery-powered, the power penalty may be particularly exacerbated due to the significant battery consumption associated with the regular operation of the communications modules 306a-306d.
[0059] Thus, to reduce the power penalty associated with monitoring for potential neighboring wireless networks, the terminal device 200 may utilize a common discovery module 306e to perform discovery instead of the communication modules 306a-306d. The common discovery module 306e may then monitor a common discovery channel to discover neighboring wireless networks and network access nodes regardless of the type of radio access technology used by the wireless networks. Instead of operating multiple communication modules 306a-306d to discover neighboring wireless networks for each radio access technology, the terminal device 200 may utilize the common discovery module 306e to monitor the common discovery channel to detect discovery signals of neighboring wireless networks. In some aspects, the common discovery channel may include discovery signals that include discovery information for network access nodes of multiple different radio access technologies.
[0060] In some aspects, network access nodes may cooperate to ensure that they are represented on a common discovery channel. As described in further detail below, such methods may include either a centralized discovery broadcast architecture or a distributed discovery broadcast architecture, both of which may result in the broadcasting of discovery signals on the common discovery channel indicating the presence of nearby wireless networks. Thus, because nearby wireless networks are all represented on the common discovery channel, terminal device 200 may utilize a common discovery module to monitor the common discovery channel without having to constantly operate communication modules 306a-306d. This may significantly reduce power consumption in terminal device 200 without sacrificing effective discovery of nearby networks.
[0061] Thus, the controller 308 may utilize the communication modules 306a-306d to maintain separate RAT connections according to their respective RATs. As previously described, the RAT connections in the communication modules 306a-306d may require discovery procedures according to the particular radio access protocol and the current state of each RAT connection. Thus, the controller 308 may monitor the state of the RAT connections to determine whether discovery should be triggered in any one or more of the communication modules 306a-306d.
[0062] In some aspects, the controller 308 may trigger discovery on any one or more of the communication modules 306a-306d during an initial power-on procedure, after a loss of coverage, and / or upon detection of poor radio measurements (low signal power or poor signal quality). The trigger criteria for such discovery may vary according to the particular radio access protocol of each RAT connection.
[0063] In some aspects, instead of triggering discovery in the communications modules 306a-306d as needed, the controller 308 may instead trigger discovery in the common discovery module 306e. The common discovery module 306e may then scan a common discovery channel to detect network access nodes for one or more radio access technologies of the communications modules 306a-306d. Thus, the communications modules 306a-306d may power down or enter a sleep state during the discovery procedure, allowing the terminal device 200 to significantly reduce power consumption.
[0064] In some aspects, the common discovery module 306e includes only RF and PHY receive components (such as those described above with respect to the communications modules 306a-306d) related to receiving and detecting discovery signals. FIG. 4 illustrates an exemplary internal configuration of the common discovery module 306e according to some aspects. As shown in FIG. 4, the common discovery module 306e may include a configurable RF module 402 and a digital processing module 404. In some aspects, the configurable RF module 402 may include analog and / or digital receive components including an amplifier (e.g., an LNA), a filter, an RF demodulator (e.g., an RF IQ demodulator), and an ADC for converting received radio frequency signals into digital baseband samples. The configurable RF module 402 may be configured to scan different RF channels (e.g., by frequency) and generate and provide baseband samples to the digital processing module 404. The digital processing module 404 can then perform PHY layer receive processing to process and evaluate the baseband samples. In some embodiments, the digital processing module 404 may be software configurable and may include a controller and one or more dedicated hardware circuits, each of which may be dedicated to performing specific processing tasks assigned by the controller (e.g., hardware accelerators). The digital processing module 404 may process baseband samples received from the configurable RF module 402, for example, as part of discovery. The digital processing module 404 may provide the results of discovery to the controller 308.
[0065] Because the common discovery module 306e may be used only for radio access technology discovery, the common discovery module 306e may not maintain a full bidirectional RAT connection. Therefore, the common discovery module 306e may also be designed as a low-power receiver. In some aspects, the common discovery module 306e may operate at significantly lower power and can be kept continuously active, conserving power compared to a normal discovery scan procedure (e.g., by the communications modules 306a-306d).
[0066] In some embodiments, the common discovery module 306e may be implemented as a hardware-defined module, e.g., one or more dedicated hardware circuits or FPGAs. In some embodiments, the common discovery module 306e may be implemented as a software-defined module, e.g., one or more processors executing program code defining operation, control, and I / O instructions (e.g., software and / or firmware) stored on a non-transitory computer-readable storage medium. In some embodiments, the common discovery module 306e may be implemented as a combination of hardware-defined and software-defined components.
[0067] FIG. 5 illustrates a methodology 500 outlining a common discovery procedure performed by terminal device 200 in accordance with some aspects.
[0068] As shown in FIG. 5, the controller 308 may perform wireless communications at 510 in accordance with the radio access protocols of one or more communication modules 306a-306d and thus may support the underlying RAT connections for one or more communication modules 306a-306d.
[0069] At 520, the controller 308 may determine whether to trigger discovery on any of the communications modules 306a-306d. In some aspects, discovery can be triggered, for example, during an initial power-up procedure, after a loss of coverage, and / or upon detection of poor radio measurements (low signal power or poor signal quality).
[0070] If the controller 308 determines that discovery should not be triggered for any of the communication modules 306a-306d, the controller 308 may return to 510 and continue standard wireless communication with the communication modules 306a-306d. In some embodiments, the controller 308 may keep the common discovery module 306e active and operate the common discovery module 306e continuously, independently of the communication modules 306a-306d. Thus, the controller 308 may continue to collect discovery results from the common discovery module 306e even during standard wireless communication operation of the communication modules 306a-306d.
[0071] If the controller 308 determines that discovery should be triggered for one or more of the communication modules 306a-306d, the controller 308 may trigger discovery in the common discovery module 306e at 530. In some aspects, the controller 308 may trigger discovery in the common discovery module 306e by activating the common discovery module 306e and instructing the common discovery module 306e to perform discovery.
[0072] The common discovery module 306e may then proceed to perform discovery by monitoring a common discovery channel (described below) for discovery signals containing discovery information for various network access nodes. The common discovery module 306e may decode any detectable discovery signals to obtain the discovery information contained therein and provide the discovery information to the controller 308 to complete 530. Certain challenges may exist associated with monitoring the common discovery channel at 530. For example, as described further below, network access nodes operating in a common discovery channel system may operate in a distributed manner, in which multiple network access nodes share a common discovery channel to broadcast their own discovery signals, or in a centralized manner, in which a single network access node broadcasts a common discovery signal on the common discovery channel containing discovery information for other network access nodes. In the distributed manner, the network access nodes may utilize a contention-based mechanism and, consequently, carrier sensing to detect channel occupancy of the common discovery channel. This can help avoid collisions because a network access node that detects that the common discovery channel is occupied can initiate a backoff procedure before attempting to transmit its discovery signal. In a centralized manner, the terminal device 200 can tune the common discovery module 306e to the common discovery channel and decode discovery information from any common discovery channel broadcast on the common discovery channel. In some aspects, the common discovery channel may utilize a simple modulation scheme in a channel with robust transmission characteristics (e.g., a common discovery channel allocated at a sub-GHz frequency), which can improve reception at the terminal device.
[0073] At 540, the controller 308 may then proceed with subsequent (e.g., "post-detection") communication operations for the RAT connections of one or more communication modules 306a-306d depending on the network access node represented by the obtained discovery information. For example, if the discovery information indicates that a valid network access node is within range and available for connection, e.g., if the discovery information indicates that the network access node 216 is available for a RAT connection of the fourth RAT, the controller 308 may modify the RAT connection of the fourth communication module 306d to connect to the network access node 216. Thus, the common discovery module 306e allows the controller 308 to obtain the discovery information at 530 without utilizing the communication modules 306a-306d.
[0074] In some aspects, various options for subsequent communication operations at 540 include one-sided wireless interactions with the network access nodes, e.g., operations performed unilaterally by the controller 308 without interaction from the network access nodes. For example, the controller 308 may perform wireless measurements on the discovered network access nodes and / or receive broadcast information of the discovered network access nodes. In some aspects, various options for subsequent communication operations at 540 include two-sided wireless interactions with the network access nodes, e.g., operations performed by the controller 308 with interaction from the network access nodes. For example, the controller 308 may potentially pursue and establish a two-way connection with the discovered network access nodes.
[0075] In some aspects, the common discovery module 306e may be configured to constantly monitor the common discovery channel (as opposed to being explicitly instructed by the controller 308 as in 530). Upon detecting a discovery signal on the common discovery channel, the common discovery module 306e may be configured to report the detected discovery information to the controller 308. Nevertheless, the common discovery module 306e may perform discovery on behalf of the communications modules 306a-306d, thereby allowing the terminal device 200 to avoid a battery power penalty. Such power savings may be particularly enhanced when multiple communications modules 306a-306d perform discovery simultaneously, because the terminal device 200 may instead utilize a single low-power receiver in the common discovery module 306e.
[0076] In some aspects, network access nodes of different radio access technologies may cooperate by broadcasting discovery signals on a common discovery channel that are subsequently detectable by the common discovery module 306e. Specifically, the network access nodes may broadcast discovery information (which would normally be broadcast on a RAT-specific discovery channel) on the common discovery channel, thereby allowing terminal devices to monitor the common discovery channel using the common discovery module.
[0077] In some aspects, network access nodes may participate in broadcasts of a common discovery channel according to either a centralized or distributed broadcast architecture, either option may enable a terminal device, such as terminal device 200, to obtain discovery information for network access nodes using common discovery module 306e according to method 500.
[0078] In some aspects, in a centralized broadcast architecture, a single centralized network access node, also referred to as a centralized discovery node, may broadcast a discovery signal to one or more other network access nodes, which may use the same or different radio access technology as the centralized discovery node. Thus, the centralized discovery node may be configured to collect discovery information of one or more other network access nodes and generate a common discovery signal that includes the discovery information of both the centralized and one or more other network access nodes. The centralized discovery node may then broadcast a common discovery signal on a common discovery channel, which in turn generates a common discovery signal that includes the discovery information of a group of network access nodes. Thus, the common discovery module 306e may discover an entire group of network access nodes by monitoring the common discovery channel and reading the common discovery signal broadcast by the centralized network access node.
[0079] Because the common discovery module 306e can monitor discovery information for network access nodes associated with various radio access technologies, the communications modules 306a-306d of the terminal device 200 can remain idle for discovery operations. Although the controller 308 may still operate the communications modules 306a-306d for non-discovery operations, such as standard wireless communication procedures related to receiving and transmitting other control and user data, the terminal device 200 may nevertheless save significant battery power by performing discovery only in the common discovery module 306e.
[0080] In some aspects, in a distributed broadcast architecture, each network access node (which may be a relay node or relay device) may continue to broadcast its own discovery signal in accordance with the individual network access node's radio access technology. However, rather than broadcasting the discovery signal on a unique RAT-specific discovery channel, the network access node may broadcast the discovery signal on a common discovery channel. To enable terminal devices to receive the discovery signal at a common discovery module, each network access node may broadcast its discovery signal in a common format, i.e., as a common discovery signal. Thus, the terminal device 200 can use the common discovery module 306e to monitor the common discovery channel for such common discovery signals broadcast by the individual network access nodes, thus eliminating the need for the individual communication modules 306a-306d to actively perform discovery.
[0081] Both centralized and distributed discovery architectures may allow terminal devices, such as terminal device 200, to perform discovery with a single common discovery module, thereby significantly reducing power consumption. Also, if discovery information for multiple network access nodes is grouped (either on the same common discovery signal or the same common discovery channel), such may simplify the discovery procedure and enable faster detection.
[0082] FIG. 2 is used to describe a centralized discovery architecture in which a single centralized discovery node may be assumed to be responsible for discovery broadcasts to one or more other network access nodes. For example, in some aspects, the network access node 210 may be assumed to be responsible for discovery broadcasts to one or more network access nodes 212-230. In other words, the network access node 210 may broadcast a common discovery signal on a common discovery channel that includes discovery information for one or more network access nodes 212-230. To generate the common discovery signal, the network access node 210 may first collect discovery information for one or more network access nodes 212-230. The network access node 210 may use any of a number of different techniques to collect the necessary discovery information, including any one or more of wireless scanning, terminal report collection, backhaul connections, and external services (described in more detail below).
[0083] 6 illustrates an internal configuration of a network access node 210 according to some aspects. The network access node 210 may include an antenna system 602, a radio system 604, a communication system 606 (including a control module 608 and a discovery module 610), and a backhaul interface 612. The network access node 210 may transmit and receive wireless signals via the antenna system 602, which may be an antenna array including multiple antennas. The radio system 604 is configured to transmit and / or receive RF signals and perform PHY processing to (1) convert digital data outgoing from the communication system 606 into analog RF signals for wireless transmission via the antenna system 602, and (2) convert incoming analog RF signals received from the antenna system 602 into digital data provided to the communication system 606.
[0084] The control module 608 may control the communication functions of the network access node 210 in accordance with a corresponding radio access protocol, including exercising control over the antenna system 602 and the radio system 604. Each of the radio system 504, the control module 508, and the detection module 510 may be structurally implemented as a hardware-defined module, e.g., one or more dedicated hardware circuits or FPGAs, a software-defined module, e.g., one or more processors executing program code defining operational, control, and I / O instructions (e.g., software and / or firmware) stored on a non-transitory computer-readable storage medium, or a hybrid of hardware and software-defined modules. The backhaul interface 612 may be a wired (e.g., Ethernet, fiber optics, etc.) or wireless (e.g., microwave radio or similar wireless transceiver system) connection point for a physical connection configured to transmit and receive data to and from other network nodes, such as a microwave radio transmitter or a connection point and associated components for a fiber backhaul link.
[0085] The network access node 210 may receive external data via the backhaul interface 612, which may include connectivity to other network access nodes, an Internet network, and / or an underlying core network (e.g., LTE Evolved Packet Core (EPC)) supporting the radio access network provided by the network access node 210. In some aspects, the backhaul interface 612 may interface with an Internet network (e.g., via an Internet router). In some aspects, the backhaul interface 612 may interface with a core network that may provide control functions in addition to routing to the Internet network. Thus, the backhaul interface 612 may provide the network access node 210 with connectivity to external networks (either directly or via a core network) that enable the network access node 210 to access external networks, such as the Internet. Thus, the network access node 210 can provide the standard functionality of a network access node in a wireless network by providing a wireless access network to enable served terminal devices to access user data.
[0086] As mentioned above, network access node 210 may be additionally configured to function as a centralized discovery node by broadcasting a common discovery signal containing discovery information for other network access nodes, such as one or more network access nodes 212-230. Figure 7 illustrates a method 700 detailing general procedures performed by a centralized discovery node, such as network access node 210, in accordance with some aspects.
[0087] At 710, the network access node 210 may collect discovery information for other network access nodes. At 720, the network access node 210 may generate a common discovery signal using the collected discovery information. At 730, the network access node 210 may broadcast the common discovery signal on a common discovery channel, thereby enabling terminal devices, such as terminal device 200, to perform discovery for multiple radio access technologies using the common discovery module 306e. The network access node 210 may generate the common discovery signal having a predetermined discovery waveform format, which may utilize, for example, on / off keying (OOK), binary phase shift keying (BPSK), or quadrature amplitude modulation (QAM, e.g., 16-QAM, 64-QAM, etc.). In some aspects, the common discovery signal may be a single-carrier waveform, while in other aspects, the common discovery signal may be a multi-carrier waveform, such as an OFDM waveform or another type of multi-carrier waveform.
[0088] Thus, network access node 210 may initially collect 710 discovery information for one or more network access nodes 212-230. Network access node 210 may utilize any one or more of a number of different discovery information collection techniques in 710, including wireless scanning, terminal report collection, backhaul connections to other network access nodes, and external services.
[0089] For example, in some aspects, network access node 210 may utilize wireless scanning at 710 to gather discovery information for other nearby network access nodes. Accordingly, network access node 210 may include a detection module 610 that may utilize antenna system 602 and radio system 604 to scan various discovery channels of other wireless access technologies to detect other network access nodes. Accordingly, detection module 610 may be configured to process signals received on various different discovery channels to detect the presence of network access nodes broadcasting discovery signals on the various different discovery channels.
[0090] 6 depicts detection module 610 as utilizing the same antenna system 602 and radio system 604 used by network access node 210 for standard base station radio access communications, in some aspects network access node 210 may alternatively include a separate antenna system and radio system that are specifically assigned to detection module 610 for purposes of discovery information gathering. Detection module 610 may be structurally implemented as a hardware-defined module, e.g., as one or more dedicated hardware circuits or FPGAs, as a software-defined module, e.g., as one or more processors executing program code defining operation, control, and I / O instructions (e.g., software and / or firmware) stored on a non-transitory computer-readable storage medium, or as a mixed hardware-defined and software-defined module.
[0091] In some aspects, the detection module 610 is configured to perform discovery signal detection similar to the communications modules 306a-306d, which allows the detection module 610 to detect RAT-specific discovery signals by processing received signals according to a proprietary radio access protocol, thereby identifying the corresponding broadcast network access node.
[0092] In some aspects, the discovery module 610 may utilize the antenna system 602 and the radio system 604 to scan discovery channels for multiple radio access technologies to detect network access nodes on the discovery channels. For example, the discovery module 610 may utilize the antenna system 602 and the radio system 604 to scan one or more LTE discovery channels (e.g., LTE frequency bands for PSS / SSS sequences and MIB / SIB) to detect nearby LTE cells. The discovery module 610 may similarly scan via one or more Wi-Fi discovery channels to detect nearby Wi-Fi APs, via one or more UMTS discovery channels to detect UMTS cells, via one or more GSM discovery channels to detect GSM cells, and scan one or more Bluetooth discovery channels to detect Bluetooth devices. The discovery module 610 may similarly scan discovery channels for any one or more radio access technologies. In some aspects, the detection module 610 can capture signal data for each scanned discovery channel, process the captured signal data according to the discovery signal format of the corresponding radio access technology, and identify any network access nodes broadcasting discovery signals therein.
[0093] 7, the discovery module 610 may identify one or more network access nodes 212-230 during a scan of discovery channels for one or more radio access technologies at 710. For example, in an example situation where the network access node 212 is an LTE base station and the network access nodes 214-230 are Wi-Fi APs, the network access node 210 may (1) detect the network access node 212 during a scan of the LTE discovery channel and (2) detect one or more of the network access nodes 214-230 during a scan of the Wi-Fi discovery channel. The discovery module 610 may collect predetermined discovery information from each detected discovery signal, and the network access node 210 may then use each detected discovery signal to generate a common discovery signal to broadcast on a common discovery channel including the discovery information of the detected network access nodes.
[0094] In some aspects, the detection module 610 may collect both “common” and “RAT-specific” information elements for one or more network access nodes identified during collection of discovery information, where the common information elements include general information related to the identified network access nodes (regardless of the particular radio access technology) and the RAT-specific information elements may include specific information specific to the parameters of the corresponding radio access technology.
[0095] For example, common information elements may include: a.RAT (e.g., LTE / Wi-Fi / UMTS / GSM, etc.) b. Frequency band and center frequency c. Channel Bandwidth d. Service Providers e. Geographical location (geographical location information such as GPS coordinates or relative navigation parameters detailing the location of a network access node relative to the terminal device) RAT specific information elements may include, for example: a. For LTE / Wi-Fi / UMTS / GSM: PLMN ID, Cell ID, Maximum Data Rate, Minimum Data Rate b. For Wi-Fi: Service Set ID (SSID), beacon interval, capability information, frequency hopping / direct sequence / non-conflict parameter set, traffic indication map, public / private network, authentication type, capability information, AP location information c. For Bluetooth: Bluetooth address, frequency hopping information d. RAT dependent: Radio measurements (signal strength, signal quality, etc.) and other performance metrics (cell load, energy per bit, packet / block / bit error rates, retransmission metrics, etc.) On the other hand, other RATs may request information similar to RAT-specific information elements.
[0096] In some aspects, the detection module 610 may obtain such discovery information at 710 by detecting and reading discovery signals from network access nodes on scanned discovery channels. Because each radio access technology may have a unique discovery signal (e.g., signal format and / or transmission scheduling), the detection module 610 may perform a specific process to obtain discovery information for each radio access technology.
[0097] For example, in an exemplary LTE environment, the detection module 610 may obtain a cell ID of an LTE cell (in the form of a physical cell identifier (PCI)) by identifying a PSS-SSS sequence pair broadcast by the LTE cell. The detection module 610 may obtain a channel bandwidth by reading a Master Information Block (MIB) message. The detection module 610 may obtain a PLMN ID of the LTE cell, for example, by reading an SIB1 message. Thus, the detection module 610 may collect such discovery information about one or more detected network access nodes and store the discovery information (e.g., in a memory; not explicitly shown in FIG. 6 ) for later broadcast in a common discovery signal.
[0098] Depending on the configuration of the detection module 610, the radio system 604, and the antenna system 602, in some aspects the detection module 610 may be configured to perform discovery channel scans for one or more radio access technologies, sequentially or in parallel, e.g., by sequentially or simultaneously scanning one or more discovery channels for one or more radio access technologies.
[0099] As mentioned above, network access node 210 may utilize additional and / or alternative techniques at 710 to collect discovery information for other network access nodes. Specifically, in some aspects, network access node 210 may utilize terminal report collection to obtain discovery information for neighboring network access nodes. For example, network access node 210 may request discovery reports (via control signaling) from served terminal devices. Accordingly, served terminal devices may perform discovery scans and report discovery information about detected network access nodes back to network access node 210 in the form of measurement reports.
[0100] For example, the discovery module 610 can trigger the transmission of control signals to request measurement reports from the terminal devices 200 and 202. The terminal devices 200 and 202 then perform discovery channel scans for various radio access technologies, obtain discovery information (e.g., common and RAT-specific information elements) about one or more detected network access nodes, and report the discovery information to the network access node 210 (e.g., using a communication module such as the communication modules 306a-306d). The discovery module 610 can receive the reports and collect the discovery information for the reported network access nodes. Thus, instead of (or in addition to) having the discovery module 610 actively perform radio scans to discover neighboring network access nodes, the served terminal device may perform a discovery scan and report the results to the network access node 210.
[0101] In some cases, terminal device 200 may discover network access node 216, while terminal device 202 may discover network access nodes 212, 220, and 224, as shown in FIG. 2. Thus, terminal devices 200 and 202 may obtain discovery information (common and RAT-specific information elements) of one or more discovered network access nodes and report the discovery information to network access node 210 in the form of a discovery report. The discovery report can be received by network access node 210 via antenna system 602 and processed by detection module 610. Thus, network access node 210 may obtain discovery information at 710 for other network access nodes.
[0102] Although terminal report collection may include terminal devices performing discovery scans (as opposed to radio scans at 710, in which network access node 210 performs the necessary radio operations and processing), this may still be advantageous and allow for reduced battery power consumption at the terminal devices. For example, network access node 210 may instruct a first group of terminal devices to perform discovery on a predetermined radio access technology (e.g., scan a predetermined discovery channel) and instruct a second group of terminal devices to perform discovery on other radio access technologies (e.g., scan other discovery channels). Network access node 210 may then aggregate discovery information of discovered radio access nodes provided by both groups of terminal devices at 720 and broadcast the aggregated discovery information on a common discovery channel at 730. Thus, terminal devices in both groups may obtain discovery information from both radio access technologies, while only having to individually perform discovery for one radio access technology, thereby conserving battery power.
[0103] In some aspects, terminal devices may be able to utilize discovery information obtained by other terminal devices when the terminal devices move to different geographic locations. For example, in an exemplary situation, terminal device 200 may report network access node 216 during terminal report collection, while terminal device 202 may report network access nodes 220 and 224 during terminal report collection. Because geographic location information may be included in the discovery information, when terminal device 200 moves to a new geographic location closer to the geographic locations of network access nodes 220 and 224, terminal device 200 may rely on discovery information previously received from network access node 210 on the common discovery channel to detect network access nodes 220 and 224 without performing a full discovery procedure. Thus, terminal device 200 may receive discovery information of network access nodes 220 and 224 via common discovery module 306e and utilize such discovery information when terminal device 200 moves within range of network access nodes 220 and 224. As mentioned above, the geographic location information in the discovery signal may include geographic location information such as GPS coordinates or another "absolute" location of the network access node (e.g., longitude and latitude coordinates), or other information indicating the relative location of the network access node with respect to the terminal device 200 (e.g., a timestamp signal that can be used to derive distance and / or other information providing directional information indicating the direction of the network access node from the terminal device).
[0104] Additionally or alternatively, in some aspects, the network access node 210 can use a backhaul connection to obtain 710 discovery information for broadcast on a common discovery channel at 730. In particular, the network access node 210 may be directly or indirectly connected to other network access nodes via a backhaul interface 612 (wireless or wired) and may utilize the backhaul interface 612 to receive discovery information from the other network access nodes at 710. For example, the network access node 210 may be connected to one or more network access nodes 212-230 via the backhaul interface 612, and the backhaul interface 612 may transmit respective discovery information to the network access node 210 at 710. Thus, the network access node 210 can aggregate the received discovery information to generate a common discovery signal at 720 and broadcast the common discovery signal at 730. Thus, the discovery module 610 can interface to the backhaul interface 612 to receive and aggregate discovery information.
[0105] There are many variations in the use of backhaul links to obtain discovery information. For example, in some aspects, network access node 210 may be directly connected to other network access nodes via backhaul interface 612, such as via an X2 interface with other network access nodes, such as network access node 212. In some aspects, network access node 210 may also be directly connected to network access nodes of other radio access technologies, such as via an inter-RAT interface via backhaul interface 612, such as directly connected to WLAN APs, such as network access nodes 214-230. Network access node 210 may receive discovery information of other network access nodes via backhaul interface 612 and broadcast a common discovery signal in response.
[0106] In some aspects, network access node 210 can interface with other centralized discovery nodes (or similarly functioning network access nodes) via backhaul interface 612. For example, a first centralized discovery node (e.g., network access node 210) may collect discovery information for a first plurality of network access nodes discoverable by the first centralized discovery node (e.g., network access nodes 214-222). A second centralized discovery node (e.g., network access node 212) may collect discovery information for a second plurality of network access nodes discoverable by a second centralized discovery node (e.g., network access nodes 224-230). In various aspects, the first and second centralized discovery nodes can utilize discovery collection techniques to collect discovery information for their respective first and second plurality of network access nodes, such as, for example, one or more of wireless scanning, terminal report collection, backhaul connectivity, or external services. The first centralized discovery node may then provide the collected discovery information for the first plurality of network access nodes to a second centralized discovery node, and the second centralized discovery node may provide the collected discovery information for the second plurality of network access nodes to the first centralized discovery node. The first centralized discovery node may then combine the resulting “combined” discovery information (for the first and second plurality of network access nodes) to generate a first common discovery signal. Similarly, the second centralized discovery node may combine the resulting “combined” discovery information (for the first and second plurality of network access nodes) to generate a second common discovery signal. The first and second centralized discovery nodes may then transmit respective first and second common discovery signals to generate common discovery signals that include discovery information for network access nodes discoverable at different centralized discovery nodes.
[0107] Additionally or alternatively, in some aspects, network access node 210 may use an external service to obtain 710 discovery information of other network access nodes. The external service may function as a database located at an internet-accessible network location, such as a cloud internet server, and may provide the discovery information to network access node 210 via backhaul interface 612. Thus, discovery module 610 may receive 710 the discovery information via backhaul interface 612 and aggregate 720 the discovery information to generate a common discovery signal.
[0108] For example, in the exemplary environment shown in FIG. 8 , network access node 210 may connect to external database 800 via backhaul interface 612. External database 800 may be located at an Internet-accessible network location and thus accessible by network access node 210 over the Internet via backhaul interface 612. Similarly, external database 800 may interface with other network access nodes and serve as a repository for discovery information. For example, one or more other network access nodes may provide their discovery information to external database 800. Network access node 210 may then query external database 800 via backhaul interface 612 for discovery information of other network access nodes at 710 in response to which external database 800 may send discovery information to network access node 210 via backhaul interface 612. Thus, such does not require a direct connection between the network access node 210 and other network access nodes to obtain the discovery information, but may maintain and update the discovery information in an external database 800 using a database manager.
[0109] In some aspects of wireless sensing and terminal report collection, network access node 210 may already implicitly know that the obtained discovery information pertains to nearby network access nodes. For example, network access node 210 may assume that network access nodes discovered during wireless sensing and reported by terminal devices served by network access node 210 are located relatively close to network access node 210 (e.g., due to detectability by wireless signals).
[0110] In some backhaul link setups, the backhaul connections may be designed such that only neighboring network access nodes include direct backhaul links. For example, each of network access nodes 214-222 may have a direct backhaul connection to network access node 210, while other network access nodes located further away from network access node 210 may not have a direct backhaul connection to network access node 210. Thus, the backhaul link setup may, in some cases, implicitly provide information about the proximity of other network access nodes.
[0111] In the case of external database 800, network access node 210 may not be able to implicitly determine which network access nodes represented in external database 800 are proximate to network access node 210. Because network access node 210 will ultimately broadcast the obtained discovery information as a common discovery signal that can be received by nearby terminal devices, network access node 210 may only want to obtain discovery information for nearby terminal devices.
[0112] Thus, when querying external database 800 for discovery information, in some aspects network access node 210 may indicate the geographic location of network access node 210. In response, external database 800 may retrieve discovery information for one or more network access nodes proximate to the indicated geographic location and provide this discovery information to network access node 210 for the reasons discussed above.
[0113] In some aspects, network access node 210 may specify a single location, e.g., the geographic location of network access node 210, or a geographic region, e.g., the coverage area of network access node 210. In response, external database 800 may obtain discovery information for the corresponding network access node and provide the discovery information to network access node 210. In some aspects, external database 800 may include a hash table (e.g., a distributed hash table) to enable rapid identification and retrieval of discovery information based on the input of the geographic location.
[0114] In some aspects, the network access node 210 may use any of a number of different techniques to collect 710 discovery information of other network access nodes with the discovery module 610. The discovery module 610 may consolidate the collected discovery information and provide the discovery information to the control module 608, which may generate 720 a common discovery signal with the collected discovery information. Such generation may include encoding the collected discovery information in digital data in a predetermined format known to both the network access node 210 and the common discovery module 306e. Many different such encoding schemes are available and may be used to generate the common discovery signal.
[0115] Regardless of the particular predefined format used for the common discovery signal, the control module 608 can encode relevant discovery information for one or more discovered network access nodes in the common discovery signal, such as common information elements (RAT, frequency band and center frequency, channel bandwidth, service provider, and geographic location) and RAT-specific information elements (depending on the particular RAT). For example, the network access node 210 can collect 710 discovery information for the network access node 210 and the network access nodes 214-230 and encode the discovery information into the common discovery signal at 720. The control module 608 can then broadcast the common discovery signal on a common discovery channel at 730 via the radio system 604 and the antenna system 602.
[0116] In some aspects, the common discovery channel may be predefined to allow the centralized network access node to know the frequency (or frequency band) to broadcast on the common discovery channel and to allow the common discovery module in each terminal device to know the frequency (or frequency band) to monitor for the common discovery signal. Any of a variety of different channel formats may be utilized for the common discovery channel, which may be a single or multi-carrier channel with a specific time-frequency scheduling (e.g., on specific carriers / subcarriers with a specific periodicity or other timing parameters). The common discovery channel may be standardized (e.g., by a standards body such as 3GPP, IEEE, or another similar entity) and / or specified by regulations in various geographic regions (e.g., for different countries). In some aspects, the communication protocol used for the common discovery channel may be a broadcast protocol, which may not require a handshake or contact from the terminal device to receive and decode the discovery signal on the common discovery channel. This format of the discovery signal on the common discovery channel allows the terminal device to utilize simple digital receiver circuitry to receive the discovery signal and obtain the information encoded therein. Each terminal device may then undergo its own decision-making process based on its unique needs and capabilities (eg, the network to which it is attempting to connect).
[0117] In some aspects, the common discovery channel may be a licensed frequency band (e.g., one allocated to a particular radio access technology and licensed by an operator, e.g., LTE / UMTS / GSM or other cellular bands) or an unlicensed frequency band (e.g., one not allocated to a particular radio access technology and publicly available for use; e.g., Wi-Fi and Bluetooth (ISM bands) in industrial, scientific, and medical applications). The common discovery channel may alternatively be a unique frequency band specifically designated (e.g., by a regulatory body) for entities authorized to broadcast discovery information.
[0118] Additionally, while certain examples herein may refer to a single common discovery channel, in some aspects multiple common discovery channels (e.g., each having a different frequency assignment) may be used. In such aspects, the common discovery module may be configured to monitor multiple different common discovery channels (e.g., in parallel or sequentially), or multiple common discovery modules may each be dedicated to scanning one or more common discovery channels. While this may slightly complicate the common discovery procedure in the common discovery module, this may alleviate congestion when multiple broadcast nodes (centralized or distributed discovery nodes) broadcast common discovery signals.
[0119] In some aspects, other network access nodes that do not function as centralized discovery nodes will not be configured to cooperate. For example, network access node 210 may be configured to perform the discovery information gathering techniques detailed above to unilaterally obtain discovery information for network access nodes 212-230 and broadcast such discovery information on a common discovery channel. Other network access nodes, such as network access nodes 212-230, may also broadcast discovery signals on their respective RAT-specific discovery channels. Thus, some aspects using a centralized discovery node may include some network access nodes specifically configured in accordance with these aspects and other network access nodes not specifically configured in accordance with these aspects.
[0120] According to these aspects, under operation of a centralized discovery node, such as network access node 210, controller 308 may utilize common discovery module 306e to scan for common discovery signals on the common discovery channel, as described above with respect to method 500 of FIG. 5. Thus, common discovery module 306e may detect the common discovery signal broadcast by network access node 210 and, as a result, decode the common discovery signal (according to the same predetermined format used by control module 608 to generate the common discovery signal) and recover the discovery information encoded in the common discovery signal. Thus, common discovery module 306e may obtain discovery information for network access nodes 210-230 and may report the discovery information to controller 308 (e.g., 530). The controller 308 can then proceed with post-discovery radio operations based on the received discovery information (e.g., 540 of method 500), which may include unilateral (e.g., performing radio measurements on the discovered network access nodes, receiving broadcast information of the discovered network access nodes, etc.) and / or bilateral (e.g., pursuing and establishing bilateral connections with the discovered network access nodes) radio interactions with various network access nodes for one or more of the radio access technologies supported by the terminal device 200. In some aspects, the specific use of the discovery information in the terminal device 200 can vary among various radio access technologies and in different circumstances and may be directed by the controller 308. For example, the controller 308 can perform unilateral and / or bilateral radio interactions with one or more network access nodes in accordance with the specific protocols of each radio access technology.For example, if the network access node 220 is configured according to, e.g., Wi-Fi, the controller 308 may perform radio measurements, receive broadcast information, establish a connection with the network access node 220 according to a Wi-Fi-specific protocol, and / or transmit and receive data with the network access node 220. In another example, if the network access node 212 is configured according to, e.g., LTE, the controller 308 may perform radio measurements, receive broadcast information, establish a connection with the network access node 212 according to an LTE-specific protocol. In another example, the controller 308 may manage, e.g., an LTE radio connection in, e.g., the communications module 306a. If the LTE radio connection is currently in a radio idle state and the controller 308 triggers a transition to a radio connected state, the controller 308 may utilize discovery information (e.g., obtained from receiving a common discovery signal) to identify the LTE network access node and initiate the establishment and execution of an LTE radio connection with the communications module 306a according to radio idle LTE procedures. The controller 308 may similarly perform unilateral and bilateral over-the-air interactions with discovered network access nodes, depending on the RAT-specific protocols and the current state of the RAT connection.
[0121] Thus, according to some aspects of the common discovery signal framework, the terminal device 200 may avoid performing discovery separately in the communication modules 306a-306d and instead perform the common discovery procedure in the common discovery module 306e, thus potentially saving significant battery power.
[0122] In some aspects, geographic location information may be important, especially in the case of a centralized discovery node. More specifically, by receiving discovery signals on a common discovery channel, terminal device 200 may avoid the need to physically discover one or more network access nodes (e.g., by receiving, processing, and analyzing wireless signals) during a local discovery procedure. Instead, the centralized discovery node may obtain discovery information and report the discovery information to terminal device 200 via the common discovery channel. Because terminal device 200 may not physically discover each network access node, terminal device 200 may not actually know whether each network access node is within wireless range. Thus, in some aspects, terminal device 200 may consider the geographic location information of a network access node to ensure that the network access node is actually within range before attempting post-discovery operations with the network access node (e.g., before attempting to establish a connection or before performing wireless measurements).
[0123] As mentioned above, in some aspects, a centralized discovery node, such as network access node 210, may include geographic information as a common information element of discovery information broadcast on a common discovery channel. For example, network access node 210 may obtain location information 710, for example, by estimating the geographic location of the network access node (e.g., by wireless sensing and location estimation procedures) or by explicitly receiving the geographic location of the network access node (e.g., over the air or through backhaul interface 612). In the example of FIG. 2, network access node 210 may identify the geographic locations of network access node 212 and network access nodes 214-230, which may be either explicit geographic locations (e.g., latitude and longitude) or general geographic regions or areas. Control module 608 may then encode such geographic location information as discovery information in the common discovery signal, which terminal device 200 may later recover by receiving the common discovery signal at controller 308.
[0124] Thus, in some aspects in which controller 308 determines which network access node to select for further post-discovery wireless operation, controller 308 may compare the current geographic location of terminal device 200 (e.g., obtained by a positioning module (not explicitly shown in FIG. 3 ) of terminal device 200 or reported by the network) with the geographic locations of the network access nodes reported in the common discovery signal. Controller 308 may then select a network access node from the network access nodes reported in the common discovery signal based on the geographic location information, such as by selecting one of the reported network access nodes that is closest or nearest to the current geographic location of terminal device 200.
[0125] In some aspects, a centralized discovery node, such as network access node 210, may alternatively apply power control to the transmission of the common discovery signal at 730 to reduce terminal processing overhead involved in comparing geographic locations. For example, network access node 210 may broadcast a low-power common discovery signal that includes discovery information only for network access nodes that are significantly closer to network access node 210, e.g., within a certain radius. Accordingly, because the common discovery signal is broadcast at low power, only terminal devices close to network access node 210 may be able to receive the common discovery signal. Thus, these terminal devices capable of receiving the common discovery signal are also located in proximity to the network access nodes reported in the low-power common discovery signal. In such a situation, the terminal device may assume that the network access nodes reported in the common discovery signal are geographically nearby and therefore, substantially all, are suitable for subsequent communication operations, such as establishing a wireless connection. Such power-controlled common discovery signals may operate according to radial distance. Additionally or alternatively, in some aspects, network access node 210 may utilize a sectorized or directional (e.g., beam-steering) antenna to broadcast a particular common discovery signal in a particular direction, where the directional common discovery channel contains discovery information for network access nodes located in a particular direction relative to network access node 210.
[0126] In some situations, these techniques can be problematic in that terminal devices located far from the centralized discovery node may not be able to receive the low-power common discovery signal. Thus, network access node 210 may instead assign different coverage sub-areas (within the overall coverage area) as different “zones,” e.g., Zone 1, Zone 2, Zone 3, etc., with each zone representing a certain distance from network access node 210. When network access node 210 broadcasts the common discovery signal at 730, network access node 210 may include zone information indicating the coverage zone from which it is transmitting. Thus, a terminal device, such as terminal device 200, can then examine only the reported network access nodes within terminal device 200's current zone, instead of having to use geographic location information to identify which network access nodes are nearby (e.g., within a predetermined radius of terminal device 200's current location). This may reduce the processing overhead involved in comparing geographic locations at the terminal device 200.
[0127] While the above description of the centralized discovery architecture may focus on a single centralized discovery node, e.g., network access node 210, in some aspects the centralized discovery architecture may include multiple centralized discovery nodes, e.g., various centralized discovery nodes geographically located to serve particular regions, such that a terminal device may receive a common discovery signal from multiple centralized discovery nodes.
[0128] For example, in an exemplary aspect, network access node 210 may be a centralized discovery node responsible for discovery broadcasts of network access nodes within the coverage area of network access node 210 and may therefore broadcast discovery information of network access nodes 214-222 in a common discovery signal. Similarly, network access node 212 may be a centralized discovery node responsible for broadcasting discovery information for network access nodes 224-230. Thus, network access nodes 210 and 212 may both broadcast a common discovery signal on a common discovery channel that can be received by terminal device 200 (which may be within the coverage area of network access nodes 210 and 212, as shown in the exemplary scenario of FIG. 2).
[0129] Thus, terminal device 200 may receive discovery information from two (or more) centralized discovery nodes and thus be able to serve multiple sets of network access nodes through a common discovery procedure. Location information (either a specific location or zone area) for network access nodes may be important in situations where terminal device 200 may not be located in close proximity to one or more network access nodes reported by network access nodes 210 and 212. Rather, terminal device 200 may only be within range of network access nodes 220 and 224, for example, as shown in FIG. 2.
[0130] Thus, with either specific location information or zone location information, the terminal device 200 can be configured to use its own geographic location to identify which network access nodes are within range and proceed to perform subsequent communication procedures accordingly. Furthermore, multiple centralized discovery nodes may be located in a single frequency network, in which case the centralized discovery nodes simultaneously transmit the same discovery signal in a synchronized manner (which may require appropriate coordination between the centralized discovery nodes).
[0131] Additionally, while the above examples focus on the use of cellular access nodes, e.g., network access nodes 210 and / or 212, any type of network access node may equally be used as a centralized discovery node, regardless of radio access technology. For example, one or more of network access nodes 214-230 may additionally or alternatively function as a centralized discovery node. Network access nodes with longer distance broadcast capabilities, such as cellular base stations, may be advantageous in some aspects due to the extended broadcast range of the common discovery signal.
[0132] In some aspects, the centralized discovery node may or may not correspond to a traditional network access node. For example, in some examples described above, network access nodes 210, 212, and 214-230 have been described as network access nodes (e.g., base stations or access points) capable of providing RAT connectivity to terminal devices to provide user data traffic to the terminal devices. However, in some aspects, the centralized discovery node may alternatively be specifically deployed for common discovery channel purposes. For example, a third party may deploy one or more centralized discovery nodes configured to provide common discovery channel services but not other traditional wireless access services. Traditional network operators (e.g., mobile network operators (MNOs), public Wi-Fi network providers, etc.) may be able to authorize the use of a common discovery channel provided by a third-party centralized discovery node.
[0133] In some aspects, the common discovery channel may additionally or alternatively be broadcast by a distributed discovery architecture. Unlike a centralized discovery architecture, which assumes that a centralized discovery node is responsible for discovery broadcasting to one or more other network access nodes, each network access node in a distributed discovery architecture may broadcast a unique discovery signal. However, as opposed to using individual RAT-specific discovery channels depending on the radio access technology, each network access node in a distributed discovery architecture may broadcast its respective discovery signal on the common discovery channel. Thus, a terminal device may perform discovery with a common discovery module that scans the common discovery channel, as described above with respect to method 500 of FIG. 5, thereby avoiding the need to launch multiple individual communication modules to perform discovery for multiple radio access technologies.
[0134] 2, network access nodes 210, 212, and 214-230 may function as distributed discovery nodes and accordingly broadcast unique discovery signals on the same common discovery channel containing each network access node's discovery information (common and RAT-specific information elements). Thus, a terminal device such as terminal device 200 can utilize a single common discovery module, such as common discovery module 306e, to monitor the common discovery channel and read the respective discovery signals broadcast by each distributed discovery node. Thus, terminal device 200 does not need to activate communication modules 306a-306d for discovery, thereby saving significant power.
[0135] More specifically, network access nodes 210, 212, and 214-230 may identify their own common and RAT-specific information elements (depending on the corresponding radio access technology) and encode this discovery information into discovery signals (e.g., in a control module such as control module 608). To simplify decoding at the terminal device, network access nodes 210, 212, and 214-230 encode their respective discovery signals in the same predetermined format in control module 608, resulting in multiple discovery signals that each contain unique information but are in the same format. Various digital coding and modulation schemes are well established in the art, and any may be used as the predetermined format.
[0136] Network access nodes 210, 212, and 214-230 may then each broadcast their respective discovery signals on the common discovery channel using the predefined discovery signal format, thereby enabling terminal devices, such as terminal device 200, to monitor the common discovery channel and detect discovery signals according to the predefined discovery signal format using common discovery module 306e, as described with respect to method 500. Because the predefined discovery signal format is known to common discovery module 306e, common discovery module 306e may be configured to perform signal processing to both detect discovery signals (e.g., using reference signals or similar techniques) and decode the detected discovery signals to recover the original discovery information encoded therein.
[0137] The common discovery module 306e can provide such discovery information to the controller 308, which can proceed to trigger subsequent communication actions by any of the communication modules 306a-306d based on the obtained discovery information and the current state of each RAT connection.
[0138] Because multiple network access nodes 210, 212, and 214-230 may be broadcasting discovery signals on a common discovery channel, there may be well-defined access rules to minimize the effects of transmission conflicts. For example, if both network access node 210 and network access node 216 broadcast their respective discovery signals on a common discovery channel at overlapping times, the two discovery signals may interfere with each other, making detection and decoding of the discovery signals difficult in common discovery module 306e.
[0139] Thus, in some aspects, broadcasts on a common discovery channel by a distributed discovery node (including when multiple centralized discovery nodes function as distributed discovery nodes to share the same common discovery channel) may be regulated by a set of access rules and broadcast transmission restrictions, such as a maximum transmit power, a maximum duty cycle, a maximum single transmission duration, etc. For example, in some aspects, one or more distributed discovery nodes may be constrained by a maximum transmit power and may not be permitted to transmit discovery signals on the common discovery channel above the maximum transmit power. In another example, one or more distributed discovery nodes may be constrained by a maximum duty cycle and may not be permitted to transmit discovery signals on the common discovery channel with a duty cycle that exceeds the maximum duty cycle. In another example, one or more distributed discovery nodes may be constrained by a maximum single transmission duration and may not be permitted to transmit discovery signals for a continuous time that exceeds the maximum single transmission duration.
[0140] Such access rules may be predetermined and pre-programmed into each distributed discovery node, thus enabling each distributed discovery node to follow the access rules when broadcasting a discovery signal on the common discovery channel.
[0141] Additionally or alternatively, in some aspects, distributed discovery nodes, e.g., network access nodes 210, 212, and 214-230, may utilize active sensing mechanisms similar to carrier sensing or contention detection and random backoff (e.g., Wi-Fi 802.11a / b / g / n protocols) to transmit their respective discovery signals without colliding with discovery signals transmitted by other network access nodes 210, 212, and 214-230 on a common discovery channel.
[0142] In such an active sensing scheme, a distributed discovery node (including multiple centralized discovery nodes acting as distributed discovery nodes sharing the same common discovery channel) may use listen-before-talk (LBT) and / or carrier sensing techniques (e.g., handled by the control module 608 and radio system 604) to perform radio sensing on the common discovery channel before actively broadcasting a discovery signal. For example, in an exemplary situation, the network access node 210 may prepare to transmit a discovery signal on the common discovery channel. To prevent collisions with transmissions from other distributed discovery nodes on the common discovery channel, the network access node 210 may first monitor the common discovery channel (e.g., over a sensing period) to determine whether any other distributed discovery nodes are transmitting on the common discovery channel. For example, in some aspects, the network access node 210 may measure radio energy on the common discovery channel and determine whether the radio energy exceeds a threshold (e.g., according to an energy detection scheme). If the radio energy on the common discovery channel is below a threshold, the network access node 210 may determine that the common discovery channel is free; conversely, if the radio energy on the common discovery channel is above a threshold, the network access node 210 may determine that the common discovery channel is busy, e.g., other transmissions are in progress. In some aspects, the network access node 210 may attempt to decode the common discovery channel (e.g., according to a common discovery signal format) to identify whether other network access nodes are transmitting common discovery signals on the common discovery channel.
[0143] If the network access node 210 determines that the common discovery channel is free, the network access node may proceed to transmit its common discovery signal on the common discovery channel. If the network access node 210 determines that the common discovery channel is busy, the network access node 210 may delay transmitting its common discovery signal, monitor the common discovery channel again, and re-evaluate whether the common discovery channel is free. The network access node 210 may then transmit its common discovery signal once the common discovery channel is free. In some aspects, a network access node using the common discovery channel may utilize a contention-based channel access scheme, such as carrier sensing multiple access (CSMA), CSMA collision avoidance (CSMA / CA), or CSMA collision detection (CSMA / CD), to control access to the common discovery channel. This can prevent collisions between common discovery signals transmitted by different network access nodes and prevent signal corruption on the common discovery channel. In some aspects, the network access node may handle collisions unilaterally, and the terminal device may not need to address collisions. For example, if there is a collision between two (or more) network access nodes when transmitting a discovery signal in a common discovery signal, the participating network access nodes may detect the collision and perform a backoff procedure before attempting to transmit the discovery signal again. If the network access nodes are too far from each other to detect a collision observed by the end device, there may be a hidden node problem (e.g., an end device is located between two network access nodes, and the network access nodes observe a collision that cannot be detected at their respective locations). In various aspects, participating network access nodes may utilize different techniques to address the hidden node problem. For example, the network access nodes may utilize iteration, i.e., by repeating the transmission of a discovery signal multiple times.In some aspects, a network access node may utilize a random backoff, which may prevent two (or more) network access nodes from detecting a transmission by a third network access node and then attempting to transmit simultaneously after both using the same backoff time. In some aspects, a network access node may utilize a centralized management scheme, such as having each network access node report to a coordination entity. The coordination entity may be a wireless device or a designated network access node specifically dedicated to managing access to the common discovery channel. The coordination entity may grant network access nodes access to the common discovery channel individually. In some aspects, each network access node may report to a single coordination entity, which may then broadcast and communicate with other nearby coordination entities (which also broadcast) and have a way to manage their broadcasts so that they do not overlap, for example, by scrambling the signals using orthogonal codes such as Zadoff-Chu sequences.
[0144] In some aspects, a distributed discovery node (including multiple centralized discovery nodes functioning as a distributed discovery node sharing the same common discovery channel) may utilize cognitive radio technology. In particular, a cognitive radio device may be configured to detect available, unused, or “free” channels. The cognitive radio device may then capture the detected available channel and use the channel for wireless transmission and reception. Thus, in some aspects, there may be a set of common discovery channels suitable for use as common discovery channels. A distributed discovery node, such as the network access node 210, may prepare to transmit a discovery signal and aim to find available time-frequency resources to use as common discovery channels for transmitting the discovery signal. Thus, in some aspects, the network access node 210 may be configured to utilize cognitive radio technology to adaptively identify available common discovery channels from the set of available common discovery channels. For example, the network access node 210 may evaluate wireless signals received on one or more of the set of common discovery channels and determine whether any of the set of common discovery channels are free, such as by performing energy detection (e.g., detecting wireless energy from any type of signal) or discovery signal detection (e.g., detecting a discovery signal by attempting to decode the wireless signal). Upon identifying available common discovery channels, the network access node 210 may utilize the available common discovery channels to transmit discovery signals. In some aspects, the set of common discovery channels may be predefined so that terminal devices can know which frequency channels are common discovery channels and, therefore, which frequency channels to scan for discovery signals. In some aspects, the distributed discovery node may be configured to broadcast the set of common discovery channels to inform terminals of frequency channels suitable for use as common discovery channels.
[0145] In some aspects, distributed discovery nodes (including multiple centralized discovery nodes functioning as distributed discovery nodes sharing the same common discovery channel) can operate a single frequency network to broadcast a common discovery signal on the single-frequency common discovery channel. For example, multiple distributed discovery nodes (e.g., multiple network access nodes 210-230) may exchange discovery information, aggregate the discovery information, and / or receive aggregated discovery information from a central control point (e.g., a server or core network node that aggregates the discovery information). The multiple distributed discovery nodes can then generate and transmit identical common discovery signals in a synchronized manner on the single-frequency common discovery channel, thus forming a single-frequency network carrying the common discovery signal. In some aspects, this may require infrastructure coordination to aggregate the information and / or maintain synchronized transmissions. The single-frequency common discovery channel broadcast in this manner can increase the coverage area and provide common discovery signals over a wide area.
[0146] In some aspects, distributed discovery nodes (including multiple centralized discovery nodes functioning as distributed discovery nodes sharing the same common discovery channel) may utilize a minimum periodicity (and optionally a maximum periodicity) for discovery signals broadcast on the common discovery channel. A maximum channel access time may also be used in conjunction with a required backoff time, in which case a distributed network access node may be required to wait a predetermined time following the broadcast of a discovery signal before broadcasting another discovery signal. Such techniques can ensure fairness by preventing distributed discovery nodes from over-utilizing the common discovery channel by broadcasting discovery signals too frequently.
[0147] It is desirable for the discovery signal format to be particularly robust for distributed discovery architectures due to the high probability of collisions (although such robustness can be beneficial in both centralized and distributed discovery architectures). Therefore, it is desirable for the discovery signal to be well suited for low-sensitivity detection and decoding, in addition to fast and accurate acquisition procedures. However, the requirements may be less stringent than for signal reception in traditional cellular cases (e.g., LTE, UMTS, and GSM) due to the modalities involved. In other words, only a deterministic amount of data may be included in the discovery signal, utilizing a predefined bandwidth and rate. This may enable the design of low-power receiver circuitry in the common discovery module 306e, providing further advantages.
[0148] As mentioned above, there may be multiple centralized discovery nodes within a centralized discovery architecture, each responsible for discovery broadcasts to other network access nodes. Therefore, such a situation may be treated as a hybrid of centralized and distributed discovery architectures, and potential collisions may occur between discovery signal broadcasts. Consequently, the centralized discovery nodes may employ similar access techniques, such as access rules and active sensing, to minimize the impact of such potential collisions.
[0149] In some aspects of centralized and distributed discovery architectures, terminal devices receiving discovery signals on the common discovery channel may perform error control to ensure that the information transmitted on the common discovery channel is correct. For example, if there is inaccurate information on the common discovery channel (e.g., if a distributed discovery node broadcasts inaccurate or misleading discovery information on the common discovery channel), the terminal device's receipt of such information may waste terminal resources by interpreting the erroneous information and acting on it by performing subsequent communication operations under incorrect assumptions. If the terminal device attempts to establish a connection with a false network access node, this may inevitably result in the waste of terminal resources. However, these situations may not result in a fatal error (e.g., may not result in a complete loss of connectivity or harm to the terminal device or the network).
[0150] Alternatively, if inaccurate discovery information is provided on the common discovery channel, there may be several repair options available to both the end device and the network access node. Specifically, an end device that identifies erroneous discovery information (either by being unable to detect a network access node based on the discovery information provided on the common discovery channel or by a failed connection) may notify the network access node to which it is connected (after an initial failure) of the presence of erroneous information being broadcast on the common discovery channel.
[0151] The notified network access node may then report the erroneous discovery information to the appropriate destination, e.g., via a backhaul link, to allow the erroneous discovery information to be repaired. For example, the notified network access node may utilize its connection via a backhaul link (if such a link exists, depending on the network architecture) to the offending network access node broadcasting the erroneous discovery information to notify the offending network access node of the erroneous discovery information, and in response, the offending network access node may correct the erroneous discovery information. Alternatively, if discovery information is handled in a database, e.g., as in the case of external database 800 in FIG. 8, the notified network access node may notify the external database (via a backhaul link) of the erroneous discovery information, thereby prompting the external database to correct the erroneous discovery information. Thus, to ensure that the discovery information is correct, the discovery information may be self-maintaining or "self-managed."
[0152] In some aspects, centralized and distributed discovery architectures may enable terminal devices to use a common discovery module to handle discovery responsibilities for multiple radio access technologies. As described above, such methods can significantly reduce the power penalty for the discovery procedure and can further simplify the discovery procedure due to the presence of a single (or limited number) common discovery channel. In some aspects, the common discovery channel method may use cooperation of network access nodes according to the centralized and / or distributed discovery architectures, which may cooperate with each other to consolidate discovery broadcast responsibilities at a single network access node (in the case of a centralized network architecture) and / or may cooperate with each other to minimize the impact of collisions (in the case of a distributed network architecture).
[0153] 8 for a centralized discovery architecture, in some aspects, terminal devices can further utilize external database 800 in a more active role. For example, a terminal device that currently has a RAT connection that provides access to external database 800 can query external database 800 for information related to nearby wireless access networks and network access nodes. For example, in an exemplary configuration in which external database 800 is provided as an external service at an Internet-accessible network location (e.g., as an Internet cloud server), a terminal device with an active Internet connection (e.g., provided via a RAT connection) can exchange data with external database 800 to obtain discovery information for associated network access nodes from external database 800.
[0154] 9 illustrates an example situation in which terminal device 200 has a RAT connection with network access node 210 according to some aspects. As shown in FIG. 9, network access node 210 may interface with external database 800 via backhaul interface 612. Terminal device 200 can utilize the RAT connection with network access node 210 to exchange network access node information with external database 800.
[0155] In particular, external database 800 may be located in an Internet-accessible network location and accordingly may have a network address, such as an Internet Protocol (IP) address, thereby enabling Internet-connected devices to exchange data with external database 800. Accordingly, a terminal device, such as terminal device 200, may utilize a RAT connection that provides Internet access (e.g., many cellular and short-range RAT connections) to exchange network access node information with external database 800. For example, terminal device 200 may utilize a RAT connection with network access node 210 (e.g., after discovery) to access external database 800 and request information from network access nodes of interest.
[0156] The terminal device 200 may utilize the external database 800 to obtain information (e.g., including discovery information) for other network access nodes of interest and may apply such information obtained from the external database 800 to affect radio access communications with such network access nodes.
[0157] 2, where network access nodes 212-230 are proximate to network access node 110, controller 308 of terminal device 200 may query external database 800 (via a first RAT connection with network access node 210 supported by first communications module 306a) for information regarding the proximate network access nodes. In response, external database 800 may provide controller 308 (via a first RAT connection with network access node 210 supported by first communications module 306a) with information regarding network access node 212 and network access nodes 214-230. Such information may include discovery information that controller 308 receives and utilizes to guide future radio access communications.
[0158] For example, based on the discovery information provided by the external database 800, the controller 308 may identify that a network access node 216 is within range of the terminal device 200 (e.g., by comparing the current geographic location of the terminal device 200 with the geographic location of the network access node 216 provided by the external database 800 as part of the discovery information). The controller 308 may then utilize the discovery information to connect to the network access node 216 and establish a RAT connection. Thus, the controller 308 may generally perform any unilateral over-the-air interaction with the network access node (e.g., performing radio measurements on the discovered network access node, receiving broadcast information of the discovered network access node) or bilateral over-the-air interaction (e.g., pursuing and potentially establishing a bidirectional connection with the discovered network access node) based on the network access node information provided by the external database 800.
[0159] In some aspects, external database 800 may obtain network access node information through any number of different sources, including through connections with network access nodes (which may additionally obtain discovery information, as described further herein) and / or through interfaces with radio access network databases. An end device may be able to request any type of network access node information from external database 800 during any time that the end device has a RAT connection that provides Internet access. Such information may be particularly useful to an end device either during a startup procedure or during periods of poor link quality.
[0160] For example, during startup and / or initial RAT connection establishment, terminal device 200 may attempt to quickly establish an initial RAT connection with an Internet-connected network access node (e.g., potentially without due consideration to establishing an optimal RAT connection in terms of radio link strength and quality) and may use the established RAT connection to query external database 800 for information about other network access nodes, such as discovery information. Terminal device 200 may then receive the requested network access node information from external database 800 via the RAT connection.
[0161] Upon obtaining the network access node information, the terminal device 200 can identify one or more other network access nodes and can utilize the network access node information to select a more suitable network access node to switch to (e.g., by utilizing detection information provided by the external database 800 to perform radio measurements and identify a more suitable network access node). Alternatively, in a situation where the current RAT connection degrades, the terminal device 200 can query the external database 800 for information about neighboring network access nodes, and the terminal device 200 can select a new network access node to connect to that may provide a better RAT connection.
[0162] Regardless of the particular situation, in some aspects a terminal device, such as terminal device 200, can utilize external database 800 to obtain information regarding network access nodes of interest, and can potentially utilize such information (e.g., including discovery information) to perform unilateral or bilateral wireless interactions with one or more network access nodes.
[0163] Thus, external database 800 may receive queries for network access node information from one or more terminal devices, in which case the terminal devices may transmit the queries to external database 800 over the wireless access network using a network addressing protocol (e.g., Internet Protocol (IP) addressing, Media Access Control (MAC) addressing, etc.). External database 800 may then respond to such queries by providing the requested information to the terminal devices over a similar reverse link. Thus, external database 800 may respond to each query individually using a network addressing protocol.
[0164] Alternatively, in some aspects, the external database 800 may collect multiple different requests from multiple terminal devices and distribute the requested information in a multicast or broadcast mode. Thus, the external database 800 may be configured to provide the requested information over either the same link or multicast or broadcast channel used by the counterpart terminal devices to query the information. For example, the external database 800 may provide the requested information in a multicast or broadcast format over a common discovery channel, as described above. Thus, the terminal devices may utilize a common discovery module, such as the common discovery module 306e, or a dedicated wireless access communication module (e.g., one of the communication modules 306a-306d, depending on which wireless access technology is employed, to query information from the external database 800).
[0165] In some aspects, the use of an external database 800 in conjunction with a centralized detection node architecture can be extended to provide information to network access nodes, e.g., to provide network access nodes with important information about other network access nodes. For example, Wi-Fi access points may be required to have wireless sensing capabilities to ensure that their transmissions do not interfere with other transmitters using the same unlicensed spectrum. For example, Wi-Fi access points may be able to detect the presence of nearby radar transmitters, which may find government or defense uses and therefore may be given high priority (e.g., by regulatory bodies such as the Federal Communications Commission (FCC)) in avoiding interference. It may be relatively complex for a Wi-Fi access point to perform comprehensive radar sensing because there may be multiple different types of radar signals present at a given geographic location, all of which may not be detectable.
[0166] To mitigate such problems, in some embodiments, a Wi-Fi access point may utilize an external database 800 as a database for maintaining information regarding radar signals. Accordingly, a Wi-Fi access point may report detected radar signals to the external database 800, which may, through the use of a centralized discovery node, broadcast such information so that other Wi-Fi access points can learn of nearby radar transmitters. Accordingly, a Wi-Fi access point may be configured with a receiving component to receive such information over a common discovery channel and may therefore rely on such information instead of having to perform a full radar sensing function.
[0167] Thus, discovery signals broadcast based on information provided by external database 800 may, in some aspects, not be limited to reception and use only by terminal devices. Accordingly, in some aspects, network access nodes may utilize such information, particularly for interference management purposes. For example, any number of different types of network access nodes may receive and apply such discovery signals to become aware of the presence of other network access nodes and then apply interference management techniques to reduce interference.
[0168] Although described and illustrated above as a single database, in some aspects multiple instances of external database 800 may be deployed, each instance may contain the same or different information, such as, for example, a different external database for serving a given geographic region.
[0169] In some aspects, the techniques described above with respect to the common discovery channel may also be extended to device-to-device (D2D) communications, in which case one or more terminal devices may utilize the common discovery channel to broadcast discovery information locally available at each mobile terminal. For example, controller 308 may have previously acquired discovery information of one or more network access nodes, e.g., via either conventional discovery in one of communications modules 306a-306d or receipt of discovery information over the common discovery channel by common discovery module 306e.
[0170] To simplify discovery procedures for other nearby terminal devices, the controller 308 may then transmit the obtained discovery information as a discovery signal (e.g., by generating the discovery signal according to a predetermined format) on the common discovery channel, for example, by using a transmission component included in the common discovery module 306e (in which case the common discovery module 306e may be more than a simple, uncomplicated receiver) or another communication module configured to transmit a discovery signal on the common discovery channel. Thus, other terminal devices may receive the discovery signal on the common discovery channel and utilize the discovery information contained therein to perform unilateral or bilateral wireless interaction with the network access node represented in the discovery information.
[0171] In some aspects, such inter-device operation of the common discovery channel can function similarly to the distributed discovery architecture described above, where each transmitting terminal device can operate as a distributed discovery node to broadcast a discovery signal on the common discovery channel.
[0172] 10 illustrates a method 1000 for performing wireless communication according to some aspects. Method 1000 includes decoding discovery information for a first radio access technology and a second radio access technology from a common discovery channel (1010), where the discovery information is encoded into one or more discovery signals according to a common discovery signal format, and controlling one or more RAT connections for the different radio access technologies according to the discovery information (1020). In one or more further exemplary aspects of the disclosure, one or more features described above with reference to FIGS. 1-9 may be further incorporated into method 1000. In particular, method 1000 may be configured to perform additional and / or alternative processes as described in detail with respect to terminal device 200. 1.2 Common Channel #2
[0173] In some aspects of the present disclosure, a terminal device may cooperate with a network access node to use a common control channel that provides control information for multiple radio access technologies. Thus, instead of monitoring separate control channels for multiple radio access technologies, the terminal device may combine the monitoring of the separate control channels into monitoring a common control channel that includes control information for the multiple radio access technologies.
[0174] In some aspects, the terminal device may also receive control information that instructs the terminal device on when and how to transmit and receive data over the radio access network. Such control information may include, for example, time and frequency scheduling information, coding / modulation schemes, power control information, paging information, retransmission information, and connection / mobility information. Upon receiving this information, the terminal device can transmit and receive wireless data in accordance with the specified control parameters to ensure proper reception at both the terminal device and the network side at the peer network access node.
[0175] The RAT connections may rely on such control information. For example, as described above in detail with respect to FIG. 3, the controller 308 may maintain separate RAT connections via two or more communication modules 306a-306d (although in many scenarios, the cellular connections of each of the communication modules 306a-306c may be jointly managed, e.g., in a master / slave RAT manner). Thus, the controller 308 may receive control information for a first RAT (e.g., LTE control information for maintaining an LTE connection in an exemplary LTE environment) via the first communication module 306a to maintain a first RAT connection, while receiving control information for a second RAT (e.g., Wi-Fi control information for maintaining a Wi-Fi connection in an exemplary Wi-Fi environment) via the second communication module 306c to maintain a second RAT connection. The controller 308 may then manage the first and second RAT connections according to the respective control information and corresponding radio access protocols.
[0176] Even if one of the RAT connections is idle, e.g., not actively exchanging user data traffic, the controller 308 may still monitor one of the RAT connections, particularly for control information such as paging messages.
[0177] For example, even if the first RAT connection in the first communication module 306a is idle (e.g., camped on an LTE cell but not assigned any dedicated resources in an exemplary LTE environment), if a network access node of the first RAT (e.g., the LTE cell) sends a paging message to the first communication module 306a indicating incoming data for the first communication module 306a, the controller 308 can still monitor the first RAT connection via the first communication module 306a. Thus, the controller 308 can continuously monitor the first radio access LTE connection for incoming first RAT data via the first communication module 306a.
[0178] Similarly, regardless of whether the second RAT connection in the second communication module 306b is idle, the controller 308 may also continuously monitor the second RAT connection for incoming second RAT data by the second communication module 306b (as well as any other RAT connections in communication modules 306c-306d, for example). This may cause excessive power consumption in the communication modules 306a-306d due to the constant monitoring of control information.
[0179] Therefore, it may be advantageous to consolidate the monitoring of multiple RAT connections into a single RAT connection, such as by being able to monitor a single RAT connection for control information of multiple RATs. For example, the terminal device 200 may monitor Wi-Fi beacons and data (e.g., beacon frames for notifying pending data of a Wi-Fi device currently using a power saving mode, which may prompt waking up to receive data) and other Wi-Fi control information of a Wi-Fi connection in an LTE connection. This may include forwarding incoming data for one RAT connection to another RAT connection at the network level (e.g., forwarding Wi-Fi data over the LTE connection), which may allow the terminal device 200 to monitor one RAT connection instead of multiple RAT connections. For example, the terminal device 200 may receive incoming Wi-Fi data via the first communication module 306a, which may allow the terminal device 200 to avoid continuously monitoring a Wi-Fi connection with the second communication module 306b.
[0180] These aspects thus enable the controller 308 to utilize a forwarding and common monitoring scheme, whereby monitoring of incoming data for multiple communication modules 306 a-306 d is consolidated into a single RAT connection. Thus, in the example above, the controller 308 may monitor only the first RAT connection of the first communication module 306 a. The controller 308 can receive incoming second RAT data at the first communication module 306 a, as such incoming second RAT data is forwarded to the first RAT connection, e.g., to a network access node counterpart for the terminal device 200 for the first RAT connection.
[0181] The controller 308 may proceed to identify incoming data for the second RAT, such as a paging message for the second RAT connection in the second communication module 306b, and proceed to control the second RAT connection according to the incoming second RAT data. For example, after receiving data on the first RAT connection, the first communication module 306a may provide the received data (which may include the incoming second RAT data embedded in the first RAT data) to the controller 308, and the controller 308 may identify the incoming second RAT data. If the incoming second RAT data is, for example, a second RAT paging message, the controller 308 may proceed to activate the second communication module 306b and receive the incoming second RAT data indicated in the second RAT paging message. Similar integration of monitoring for multiple RAT connections may also be achieved with any other combination of two or more RAT connections. For example, in an exemplary LTE and Wi-Fi environment where the first RAT is LTE and the second RAT is Wi-Fi, the controller 308 may receive Wi-Fi control data via the first communication module 306a (where the Wi-Fi data is forwarded to the LTE connection at the network level), and the controller 308 may then control the Wi-Fi connection via the second communication module 306b based on the Wi-Fi control data.
[0182] The forwarding and common monitoring system may rely on coordination from at least one of the counterpart network access nodes. For example, in the above example, the second RAT network access node identifies incoming data addressed to terminal device 200 and forwards the identified data to the first RAT network access node for subsequent transmission to terminal device 200 over the first RAT connection. Thus, the forwarding and common monitoring system may rely on a forwarding scheme in which second RAT data at the second RAT network access node intended for terminal device 200 is forwarded to the first RAT network access node, thereby enabling the first RAT network access node to subsequently transmit the second RAT data to first communication module 306a over the first RAT connection.
[0183] In certain circumstances, both the first RAT network access node and the second RAT access node may be configured according to a forwarding and common monitoring scheme, and the forwarding and common monitoring scheme may be realized with only a single cooperative network access node forwarding data to the terminal device via an uncooperative network access node.
[0184] 11 illustrates an exemplary forwarding and common monitoring system according to some aspects. In FIG. 11, second RAT data intended for terminal device 200 is re-routed or forwarded from the second RAT connection to the first RAT connection, thereby allowing terminal device 200 to refrain from monitoring the second RAT connection and instead monitor only the first RAT connection. Some examples in the following description may focus on LTE and Wi-Fi, but terminal device 200 may similarly apply similar forwarding and common monitoring techniques to any two or more radio access technologies.
[0185] 11, terminal device 200 may have a first RAT connection and a second RAT connection via first communication module 306a and second communication module 306d, respectively. As shown in 1100, terminal device 200 may have a second RAT connection provided by network access node 1106, which provides terminal device 200 with connectivity to Internet network 1102. Terminal device 200 may also have a first RAT connection provided by network access node 1108, which routes to Internet network 1102 via core network 1104.
[0186] In some aspects, because the first RAT connection and the second RAT connection are separate, terminal device 200 may be assigned a network address for each connection. For example, terminal device 200 may have a network address, e.g., abcd, for the second RAT connection (which identifies terminal device 200 as the termination destination of the second RAT connection) and a network address, e.g., efgh, for the first RAT connection (which identifies terminal device 200 as the termination destination of the first RAT connection). Data packets (e.g., IP data) can be routed along the first and second RAT connections from Internet network 1102 to terminal device 200 according to the first and second RAT network addresses. In some aspects, the network address may be an IP address. In some aspects, the network address may be a MAC address. Other network addressing protocols may also be used without departing from the scope of this disclosure. In some aspects, terminal device 200 may be associated with one or more network addresses, and the network may use the one or more addresses to route data to terminal device 200. The one or more network addresses may be any type of address that is compatible with the underlying network.
[0187] Thus, the controller 308 may maintain both a first and a second RAT connection with the first communication module 306a and the second communication module 306b to transmit user data traffic to and from the Internet network 1102. When a RAT connection is in an active state, the controller 308 may constantly operate the corresponding communication module to transmit uplink and downlink data to and from the appropriate network access node. Alternatively, when a RAT connection is in an idle state, the controller 308 may only periodically operate the corresponding communication module to receive infrequent control data, such as paging messages, that may indicate that the idle connection may be transitioned to an active state to receive incoming data.
[0188] When a paging message is received for a given idle RAT connection, the controller 308 may transition the corresponding RAT connection to an active state and subsequently activate the corresponding communication module to receive the incoming data announced in the paging message. Thus, monitoring for such paging messages may require the controller 308 to monitor both the first communication module 306a and the second communication module 306b even when the underlying RAT connection is in an idle state. This may require high battery power consumption in the terminal device 200.
[0189] In some aspects, to avoid having to separately monitor two or more RAT connections, the controller 308 can implement the forwarding and common monitoring mechanism shown in Figure 11, which temporarily disconnects one of the RAT connections and arranges for incoming data related to the disconnected RAT connection to be forwarded to another RAT connection. The controller 308 can then monitor the data of the disconnected RAT connection on the remaining RAT connections.
[0190] For example, in a situation where the second RAT connection with the network access node 1106 is in an idle state and the first RAT connection with the network access node 1108 is in an active or idle state, the controller 308 can temporarily disconnect the second RAT connection and transfer monitoring of the second RAT connection from the second communication module 306b to the first communication module 306a. Thus, the controller 308 can place the second communication module 306b in an inactive state to conserve battery power.
[0191] In some aspects, to disconnect a RAT connection (e.g., a second RAT connection), the controller 308 can configure a forwarding path to ensure that data (e.g., paging messages and other control data) intended for the terminal device 200 in the disconnected RAT connection is rerouted to another RAT connection (e.g., via the network access node 1108).
[0192] Thus, as shown in situation 1100, the controller 308 sends a forwarding setup command to the network access node 1106 (via the second communication module 306b over the second RAT connection), which instructs the network access node 1106 to temporarily disconnect the second RAT connection and reroute second RAT data intended for the terminal device 200 to an alternate destination. For example, the controller 308 may instruct the network access node 1106 to forward all second RAT data intended for the second RAT network address abcd of the terminal device 200 to the first RAT network address efgh of the terminal device 200. Upon receiving the forwarding setup command, the network access node 1106 may register the alternate destination of the terminal device 200, e.g., the first RAT network address efgh, in a forwarding table (as shown in FIG. 11 ), thereby activating forwarding to the alternate destination.
[0193] 12 illustrates an internal configuration of a network access node 1106 according to some aspects. The network access node 1106 may include an antenna system 1202, a radio system 1204, a communication system 1206 (including a control module 1208 and a forwarding table 1112), and / or a backhaul interface 1212. The network access node 1106 may transmit and receive wireless signals via the antenna system 1202, which may be an antenna array including multiple antennas. The radio system 1204 may perform transmit and receive RF and PHY processing to convert output digital data from the communication module 1206 into analog RF signals and provide them to the antenna system 1202 for wireless transmission, and to convert incoming analog RF signals received from the antenna system 1202 into digital data and provide them to the communication module 1206. The control module 1208 may control the communication functions of the network access node 1106 according to a corresponding wireless access protocol, e.g., Wi-Fi / WLAN, including through the antenna system 1202 and the radio system 1204.
[0194] The radio system 1204, control module 1208 may be structurally implemented as hardware-defined modules, e.g., as one or more dedicated hardware circuits or FPGAs, as software-defined modules, e.g., as one or more processors executing program code, or as a mixture of hardware-defined and software-defined modules, where the processors executing program code specify operational, control, and I / O instructions (e.g., software and / or firmware) stored on a non-transitory computer-readable storage medium.
[0195] In some aspects, the forwarding table 1112 may be embodied as a memory accessible (read / write) by the control module 1208. The backhaul interface 1212 may be a wired (e.g., Ethernet, fiber optic, etc.) or wireless (e.g., microwave radio or similar wireless transceiver system) connection point for a physical connection configured to send and receive data to and from other network nodes, such as a microwave radio transmitter, or a connection point and associated circuitry for a fiber backhaul link.
[0196] In some aspects, the control module 1208 may receive a forwarding configuration command (following processing by the antenna system 1202 and the radio system 1204) as shown at 1100 and proceed to activate forwarding for the terminal device 200 by updating the forwarding table 1112 according to an alternative destination, such as the first RAT network address efgh, provided by the controller 308 in the forwarding configuration command.
[0197] After forwarding activation, the network access node 1106 can reroute all second RAT data (e.g., addressed to the second RAT network address abcd) received from the Internet network 1102 intended for the terminal device 200 to an alternative destination, such as the first RAT network address efgh. Because the alternative destination is simply the first RAT network address of the first RAT connection of the terminal device 200, such results in the second RAT data being rerouted to the terminal device 200 via the first RAT network address. Thus, the terminal device 200 can receive the second RAT data via the first RAT connection at the first communication module 306a, along with other data addressed to the first RAT network address efgh.
[0198] In some aspects, the control module 1208 can populate the forwarding table 1112 using forwarding setup instructions received from the served terminal device. The forwarding table 1112 may include forwarding entries including at least an original network address and a forwarding network address. In some aspects, the control module 1208 can register the original network address of the terminal device (e.g., abcd for the terminal device 200) in the forwarding table 1112 along with the forwarding network address (e.g., efgh for the terminal device 200) specified in the forwarding setup instruction. Thus, upon receiving a forwarding setup instruction from the terminal device 200 (the terminal device 200 has the second RAT network address abcd and specifies the forwarding network address efgh in the forwarding setup instruction), the control module 1208 can register the original second RAT network address abcd and the forwarding network address efgh in the forwarding table 1112. In some cases, the control module 1208 may also set an “active flag” for a forwarding entry of the terminal device 200 to “on,” where the active flag for the forwarding entry may specify whether the forwarding path is currently active.
[0199] In some aspects, after receiving a forwarding configuration command from terminal device 200 at 1100, control module 1208 may proceed to forward all received data intended for terminal device 200 at second RAT network address abcd to first RAT network address efgh. FIG. 11 illustrates a high-level forwarding path through Internet network 1102, core network 1104, and network access node 1108, while FIG. 12 illustrates an internal path within network access node 1106 according to some aspects. As shown at 1110, Internet network 1102 can provide data packets to network access node 1106, which can be addressed to various terminal devices served by network access node 1106. Network access node 1106 can receive such data packets at backhaul interface 1212, which can route the received data packets to control module 1208. The control module 1208 may examine the destination network address of each data packet with the original network address in the forwarding table 1112, as shown in FIG. 12, to determine whether any data packets should be rerouted to a forwarding network address.
[0200] Thus, as shown at 1110, the network access node 1106 may receive a data packet (or a stream of data packets, although the following description may similarly apply to multiple data packets) addressed to destination network address abcd from the Internet network 1102. The network access node 1106 may receive such data packets from the Internet network 1102 via the backhaul interface 1212, where the data packets may then be received and processed by the control module 1208.
[0201] Subsequently, for each data packet addressed to the served terminal device, the control module 1208 may check whether the destination network address matches an original network address registered with an active forwarding flag in the forwarding table 1112. If the data packet is addressed to an original network address that has an active flag in the forwarding table 1112, the control module 1208 may forward the data packet to the forwarding network address registered with the original network address in the forwarding table 1112.
[0202] 12, upon receiving a data packet addressed to terminal device 200 (e.g., with network address abcd), control module 1208 may compare the destination network address abcd with the forwarding entries in forwarding table 1112 and determine that destination network address abcd matches the original network address abcd of terminal device 200 and has an active forwarding flag. As a result, instead of sending the data packet to terminal device 200 over the second RAT (provided from radio system 1204 and antenna system 1202 to second communication module 306b), control module 1208 may reroute the data packet to the forwarding network address of terminal device 200 registered for the original network address abcd in forwarding table 1112, e.g., to forwarding network address efgh, which may be the first RAT network address registered by terminal device 200 in the initial forwarding setup message.
[0203] Upon identifying the appropriate transport network address for the data packet, the control module 1208 may readdress the data packet (e.g., according to a corresponding header encapsulation and transmission protocol, e.g., according to an IP addressing scheme) and transmit the readdressed data packet to the Internet network 1102 via the backhaul interface 1212. Because the data packet is readdressed to transport network address abcd, the Internet network 1102 can route the readdressed data packet to the core network 1104.
[0204] In some aspects, the core network 1104 may similarly use the transport network address abcd to route the readdressed data packet to the appropriate network access node associated with the transport network address efgh, such as to the network access node 1108 that provides the first RAT connection to the terminal device 200 having the first RAT network address efgh as a user side destination address.
[0205] The network access node 1108 may then transmit the readdressed data packet to the terminal device 200 using the first RAT connection, and the terminal device 200 may receive the readdressed data packet at the first communication module 306a and subsequently process the readdressed data packet at the controller 308. Thus, the controller 308 need not actively operate the second communication module 306b to receive the data packet. Instead, the controller 308 may integrate monitoring of both the first RAT connection and the second RAT connection with only the first communication module 306a. The controller 308 can identify the readdressed data packet as a second RAT data packet and process the readdressed data packet according to the associated second RAT protocol as if the data packet had actually been received at the second communication module 306b.
[0206] As mentioned above, the data packet may be control data, such as a paging message indicating incoming second RAT data addressed to the terminal device 200. Upon recognizing that the data packet is a second RAT paging message, the controller 308 may proceed to activate and control the second communication module 306b to receive the incoming second RAT data via the second RAT connection.
[0207] To receive the second RAT data arriving via the second RAT connection, the controller 308 may deactivate forwarding in the network access node 1106. Accordingly, the controller 308 may resume the second RAT connection in the second communication module 306b with the network access node 1106 and send a stop forwarding command to the network access node 1106. In some aspects, the network access node 1106 and the controller 308 may keep the second RAT connection “virtual” during forwarding, such as by retaining a network address and ignoring a keep-alive timer (which could otherwise expire and trigger a complete disconnection of the connection). Thus, when the controller 308f decides to deactivate forwarding and utilize the second RAT connection again, the second communication module 306b and the network access node 1106 can resume use of the second RAT connection without performing a full connection re-establishment procedure. For example, the controller 308 may send a request (over the forwarding link) to the network access node 1106 to resume using the second RAT connection. The network access node 1106 can then respond (over the forwarding link) with an acknowledgment (ACK) and prompt the control module 1208 to resume using the second RAT connection with the second communication module 306d. In some aspects, the controller 308 may expect the network access node 1106 to be configured to continue monitoring the second RAT connection and may resume transmissions on the second RAT connection via the second communication module 306b. Alternatively, in some aspects, the network access node 1106 and the controller 308 may terminate (e.g., completely disconnect) the second RAT connection during forwarding and re-establish the second RAT connection, for example, by performing discovery and initial connection establishment.
[0208] In some aspects, the control module 1208 may receive a forwarding deactivation command (via the antenna system 1202 and the radio system 1204) and proceed to deactivate the forwarding link. In some cases, the control module 1208 may deactivate the forwarding link by changing the active flag in the forwarding table 1112 of the terminal device 200 to “off” (the control module 1208 may alternatively delete the forwarding entry from the forwarding table 1112). Thus, if the control module 1208 receives a further data packet addressed to the terminal device at abcd, it may determine from the forwarding table 1112 that the forwarding link is currently inactive for the destination network address abcd and proceed to wirelessly transmit the data packet to the terminal device 200 via the second RAT connection. Thus, the terminal device 200 can receive the incoming second RAT data indicated in the originally forwarded paging message via the second RAT connection in the second communication module 306b.
[0209] As mentioned above, in some aspects, the network access node 1106 may achieve the forwarding link by readdressing a data packet initially addressed to a second RAT network address of terminal device 200 that is addressed to a first RAT network address. In some aspects, the network access node 1106 may achieve the forwarding link for a given data packet by wrapping the data packet with another wrapper (or header) that includes the first RAT network address (e.g., a forwarding network address) of terminal device 200. The network access node 1106 may then send the rewrapped data packet to the Internet network 1102, which may then route the rewrapped data packet to the core network 1104 and the network access node 1108 according to the wrapper that specifies the first RAT network address of terminal device 200. The network access node 1108 may then complete the forwarding link by transmitting the rewrapped data packet to terminal device 200 over the first RAT connection.
[0210] FIG. 13 outlines the forwarding and common monitoring scheme as a method 1300 performed in terminal device 200 in accordance with some aspects. As shown in FIG. 13, controller 308 may first select a second RAT connection, e.g., via network access node 1106, to temporarily deactivate the connection and establish a forwarding link for all incoming data on the deactivated RAT connection (1302). In particular, controller 308 may send a forwarding setup command to the network access node that initially supports the selected RAT connection, e.g., the “original network access node,” which specifies the forwarding network address of the original network access node for forwarding all future incoming data addressed to terminal device 200. Controller 308 may then deactivate the selected RAT connection, which may include deactivating associated communication components, e.g., second communication module 306b, which controller 308 may place in an idle, sleep, or powered-off state to conserve power.
[0211] In some aspects, at 1304, the controller 308 may then proceed to send and / or receive data over the remaining RAT connections, including the RAT connections associated with the forwarding link, e.g., the first RAT connection with the network access node 1108. Thus, as opposed to performing communications over the deactivated RAT connection, the controller 308 may maintain the communications components associated with the deactivated RAT connection in an inactive state and instead monitor the associated incoming data on the forwarding link. The original network access node may proceed to forward all incoming data addressed to terminal device 200 at its original network address to a forwarding network address specified by the controller 308 in the forwarding setup command, which may be the network address of the terminal device's 200 remaining RAT connection served by another network access node, e.g., the “selected network access node.”
[0212] Thus, the controller 308 may examine 1306 data received from the selected network access node on the forwarding link to determine whether the incoming data is intended for the RAT connection associated with the forwarding link or whether it was originally addressed to the terminal device 200 via the deactivated RAT connection and is subsequently forwarded. If all incoming data on the forwarding link was originally associated with the RAT connection associated with the forwarding link, the controller 308 may continue to send and receive data on the remaining RAT connection(s) at 1304.
[0213] Alternatively, if the controller 308 determines that forwarded data for a deactivated RAT connection has been received on the forwarding link 1306, the controller 308 may read the forwarded data to identify the contents of the forwarded data and determine what further action is appropriate. More specifically, the controller 308 may determine 1308 whether the controller 308 needs to re-establish the deactivated RAT connection in order to receive further incoming data related to the now deactivated RAT connection.
[0214] In some aspects, if the forwarded data identified at 1306 is only incoming data for the deactivated RAT connection, or if the forwarded data identified at 1306 indicates that only a limited amount of further incoming data is pending for the deactivated RAT connection (e.g., a paging message indicating only a limited amount of further incoming data), then at 1308 the controller 308 may determine that there is no need to re-establish the deactivated RAT connection and may proceed at 1310 to receive any remaining forwarded data for the deactivated RAT connection from the selected network access node via the forwarding link.
[0215] Alternatively, if the controller 308 determines in 1308 that the deactivated RAT connection should be re-established (e.g., if the forwarding data identified in 1306 indicates a significant amount of incoming data for the deactivated RAT connection), or if the forwarding data indicates that uplink data traffic is required, the controller 308 may proceed to 1312 and re-establish the deactivated RAT connection and deactivate the forwarding link.
[0216] More specifically, the controller 308 may deactivate the forwarding link by reestablishing the deactivated RAT connection by reconnecting to the original network access node that originally provided the now-deactivated RAT connection (if the network access node is still available, as described in more detail below), and subsequently sending a forwarding deactivation command to the original network access node on the now-reestablished RAT connection. Such may include reactivating communication components associated with the re-established RAT connection, such as the second communication module 306b. The original network access node may deactivate the forwarding link by updating a forwarding table.
[0217] Because the forwarding link is now deactivated, the original network access node may not forward the incoming data addressed to terminal device 200, and may instead proceed to transmit the incoming data to terminal device 200 over the re-established RAT connection. Thus, controller 308 may receive 1314 the remaining data over the re-established RAT connection by the associated communications components.
[0218] Optionally, following completion of reception of the remaining data at 1314, the controller 308 may, in some aspects, decide to establish a new forwarding link by sending a forwarding setup command to the original network access node (potentially routed through the selected network access node), thus deactivating the same RAT connection again and allowing deactivation of the associated communication components. Thus, the controller 308 can conserve power by deactivating the associated communication components and resuming the forwarding link via another RAT connection, e.g., by combining reception for multiple RAT connections.
[0219] Activation of a forwarding link similar to 1302 may be completed by forwarding of a forwarding configuration instruction and subsequent registration by the network access node, however, similar to 1312, re-establishment of a previously deactivated RAT connection (and associated deactivation of a forwarding link) may be difficult due to dynamic radio conditions and network mobility.
[0220] For example, terminal device 200 may be within range of network access node 1106 at 1100 and 1110 (and thus be able to send a transfer instruction to network access node 1106), but terminal device 200 may move to a different geographic location after the transfer is initiated by network access node 1106. Additionally or alternatively, even if terminal device 200 remains in the same geographic location, changes in network and radio conditions may prevent network access node 1106 from completing a transmission to terminal device 200 (or vice versa).
[0221] Thus, in some cases, the controller 308 may not be able to re-establish the original RAT connection with the network access node 1106. As a result, the controller 308 may not be able to deactivate the forwarding link and resume communication over the original RAT. Thus, the network access node 1106 may continue to forward data addressed to the terminal device 200 according to the forwarding link originally established by the controller 308.
[0222] Thus, if a RAT connection of the same radio access technology as the original RAT connection is desired, the controller 308 discovers a new network access node of the same radio access technology; for example, in the environment of FIG. 11, the controller 308 may perform discovery for the second RAT to detect nearby network access nodes of the second RAT with which to establish a new RAT connection (e.g., to the same destination address on the Internet network 1102 using the new network access node).
[0223] Accordingly, the controller 308 may trigger discovery in an appropriate communication module, e.g., the second communication module 306b, to detect nearby network access nodes of the desired radio access technology (alternatively, using common discovery channels and procedures such as those described in detail above with respect to the common discovery module 306e of FIG. 3; such common discovery may equally be employed to discover network access nodes). If the appropriate communication module, e.g., the second communication module 306b, discovers a suitable network access node, the controller 308 may establish a RAT connection with the selected network access node and may hand over a deactivated RAT connection from the original network access node, e.g., network access node 1106, to the selected network access node, e.g., another network access node (not explicitly shown in FIG. 11), via the selected network access node. Since the original network access node is still operating the forwarding link in accordance with the forwarding configuration instructions originally provided by the controller 308, the controller 308 can therefore utilize the selected network access node to route a forwarding deactivation instruction to the original network access node, instructing the original network access node to deactivate the forwarding link.
[0224] In the environment of FIG. 11, the controller 308 can send a forwarding deactivation command to the network access node 1106, such that the selected network access node can receive the forwarding deactivation command from the controller 308 and route the forwarding deactivation command to the original network access node, for example, via the Internet network 1102.
[0225] Because the controller 308 also requires that all future data be routed to the terminal device 200 through the selected network access node, the controller 308 may also arrange for a connection handover to permanently transfer the RAT connection that is deactivated at the original network access node to the selected network access node, thereby allowing the controller 308 to continue the newly established RAT connection at the selected network access node.
[0226] The controller 308 may eventually decide to re-establish a forwarding link while connected to the selected network access node, in which case the controller 308 may send a forwarding setup command to the selected network access node having a forwarding address in a manner similar to that described above, and then cause data associated with the RAT connection with the selected network access node to be forwarded to the terminal device 200 via another network access node.
[0227] Although the controller 308 may successfully perform discovery in certain circumstances to find a neighboring network access node of the same radio access technology as the deactivated RAT connection, there may be other cases where the controller 308 is unable to find any suitable network access node and therefore leaves the forwarding link active in the original network access node without any way to re-establish the RAT connection with the same radio access technology as the deactivated RAT connection. Thus, the controller 308 may fall back on other radio access technologies.
[0228] For example, the controller 308 can deactivate the existing forwarding link at the original network access node, e.g., network access node 1106, and utilize the remaining RAT connection for which the forwarding link is active, e.g., the first RAT connection via network access node 1108 in the environment of FIG. 11, to transfer the deactivated RAT connection to the remaining RAT connection.
[0229] More specifically, in some aspects, the controller 308 may utilize a remaining RAT connection to route the forwarding deactivation command to the original network access node; for example, in the environment of FIG. 11 , the controller 308 may utilize the first RAT connection with the network access node 1108 to route the forwarding deactivation command via the core network 1104 and the Internet network 1102 to the network access node 1106. The network access node 1106 therefore receives the forwarding deactivation command and proceeds to deactivate the forwarding link (e.g., by updating the relay table 1112), thus terminating the forwarding of data addressed to the terminal device 200 to the forwarding network address originally specified by the controller 308 in the initial forwarding configuration command.
[0230] The controller 308 may also arrange for the deactivated RAT connection at the network access node 1106 to be transferred to the network access node 1108, thereby ensuring that the terminal device 200 continues to receive associated data via the remaining RAT connection. Because the second RAT connection is now disconnected, the terminal device 200 loses its second RAT network address and can instead rely on the first RAT connection and associated first RAT network address for data transfer.
[0231] The forwarding and common monitoring scheme described above is not limited to receiving paging messages, but may be particularly suitable for forwarding and common monitoring of any sporadic and / or periodic information. Thus, the control information may relate to idle mode control information, particularly relatively infrequent paging messages. However, the forwarding and common monitoring scheme may equally apply to any data and / or data stream. For example, the readdressed data packet described above may include a second RAT paging message indicating that only a small amount of incoming second data is pending transmission to the terminal device 200. Thus, instead of reactivating the second RAT connection with the second communication module 306b and deactivating the forwarding link with a forwarding deactivation command, the controller 308 rather leaves the forwarding link untouched (e.g., refrains from sending a forwarding deactivation command) and allows the network access node 1106 to continue forwarding data packets to the terminal device 200 by readdressing the data packets with the forwarding network address efgh and routing the readdressed data packets via the Internet network 1102, the core network 1104, and the network access node 1108 (e.g., the forwarding link) to the terminal device 200. Although excessive external data traffic on the first RAT connection between the network access node 1108 and the terminal device 200 may cause congestion, the forwarding link may be acceptable for forwarding a reasonable amount of data to the terminal device 200. Thus, the terminal device 200, in some aspects, can avoid activating the second communication module 306b to receive incoming data and instead receive the second RAT data from the network access node 1108 via the forwarding link.
[0232] After receiving the second RAT data arriving over the forwarding link, the terminal device 200 can continue to integrate monitoring in the first communication module 306a by leaving the forwarding link untouched at the network access node 1106, e.g., by refraining from sending a relay deactivation command. While it may be advantageous to avoid transmitting large amounts of data (such as multimedia data streams or large files) over the forwarding link, the terminal device 200 can achieve forwarding for any type or size of data in the same manner as described above, and all such variations are therefore within the scope of this disclosure.
[0233] Large amounts of data, such as multimedia data streams or large files, may be manageable depending on the capacity and current traffic load of the network access node selected to support the transfer link; thus, a high-capacity and / or low-traffic network access node may be better suited to handle large amounts of transferred data than other low-capacity and / or high-traffic network access nodes.
[0234] Although the forwarding link detailed herein may be utilized primarily for downlink data; depending on the configuration of the network access node, the terminal device 200 may, in some aspects, forward uplink data via the forwarding link. For example, if the forwarding link is active and the controller 308 has uplink data to transmit on an idle RAT connection, the controller 308 may determine whether to utilize the forwarding link to transmit the uplink data or to reactivate (or reestablish) the idle RAT connection. For example, if the uplink data is a limited amount of data (e.g., below a threshold), the controller 308 may transmit the uplink data via the forwarding link. If the uplink data is a greater amount of data (e.g., above a threshold), the controller 308 may reactivate (or reestablish) the idle RAT connection to transmit the uplink data. In some aspects, the controller 308 may first initiate the reestablishment of the idle RAT connection by sending an access request message to the network access node of the idle RAT connection via the forwarding link.
[0235] In addition to forwarding setup and forwarding deactivation instructions, in some aspects, terminal device 200 may additionally use forwarding modification instructions. Terminal device 200 may use such forwarding modification instructions to modify existing forwarding links (either active or inactive). For example, terminal device 200 may be assigned a new first RAT network address, e.g., qrst, and may update forwarding entries in network access node 1106 to ensure that future data packets are routed to the new first RAT network address. Accordingly, controller 308 may generate a forwarding modification instruction that identifies the new first RAT network address qrst as the forwarding network address and transmit the forwarding modification instruction to network access node 1106 (via the second RAT connection with second communication module 306b).
[0236] The control module 1208 may receive the forwarding modification command via the backhaul interface 1212 and subsequently update the entry for the terminal device 200 in the forwarding table 1112 to replace the old forwarding network address (efgh) with the new forwarding network address (qrst). Such a forwarding modification command may further be combined with a forwarding setup or forwarding deactivation command by including an activation or deactivation command in the forwarding modification command that prompts the control module 1208 to set an active forwarding flag in the forwarding table 1112.
[0237] The above-described exemplary scenarios 1100 and 1110 may be used for any type of radio access technology. For example, in some aspects, the first RAT may be, for example, LTE, and the second RAT may be, for example, Wi-Fi, where the network access node 1108 may be an LTE eNodeB, and the network access node 1106 may be a Wi-Fi AP. In some aspects, the first RAT may be Wi-Fi, and the second RAT may be LTE, where the network access node 1108 may be a Wi-Fi AP, and the network access node 1106 may be an LTE eNodeB. In some aspects, the first or second RAT may be Wi-Fi, and the other of the first or second RAT may be Bluetooth. Any radio access technology may be utilized without departing from the scope of this disclosure.
[0238] Thus, in various aspects, terminal device 200 may rely on coordination across various network access nodes to implement a forwarding and common monitoring scheme. In some aspects, a forwarding network access node (network access node 1106 or network access node 1108) may implement the forwarding procedure without manipulating the underlying radio access protocol. This may rely on the fact that incoming data may be forwarded to the same destination device via a different network address assigned to the destination device. In other words, standardized protocols such as Wi-Fi, LTE, etc. may not need to be modified to support the forwarding scheme in certain instances, since only the local configuration of the network access node may be modified to include the forwarding structure.
[0239] Because coordination by network access nodes can be important, the ability of terminal device 200 to implement the forwarding and common monitoring scheme may depend on whether the associated network access nodes support the forwarding system. Thus, if only one of network access node 1106 or network access node 1108 supports forwarding, in some aspects terminal device 200 may only be able to forward data traffic associated with a forwarding-capable network access node to a non-forwarding-capable network access node (and not vice versa). Nevertheless, only one of the network access nodes may be compatible in order for terminal device 200 to utilize the forwarding and common monitoring scheme.
[0240] However, if multiple network access nodes support forwarding, e.g., if both network access node 1106 and network access node 1108 support forwarding, terminal device 200 may be able to select which of the RAT connections to temporarily disconnect and which to support a forwarding link. As described in detail above, the forwarding and common monitoring scheme may provide power consumption advantages because terminal device 200 may be able to temporarily shut down one or more communication modules and have all associated data packets forwarded to other active communication modules, thereby consolidating the monitoring of incoming data packets into the active communication modules. Thus, applications in which terminal device 200 has active RAT connections to two or more network access nodes, each capable of forwarding, may be particularly advantageous when one RAT connection is more power intensive than the others, because terminal device 200 may be able to temporarily disconnect the power-intensive RAT connection and forward all associated data to the other RAT connection.
[0241] For example, if the second RAT connection via the second communication module 306b requires less power consumption than the first RAT connection via the first communication module 306a, the controller 308 may select to initiate a transfer from the first RAT to the second RAT and to send a transfer configuration command to the network access node 1108 specifying the second RAT network address of the terminal device 200 as the destination network address.
[0242] In some aspects, the controller 308 may consider factors alternative to or in addition to power consumption when determining which RAT connections to disconnect and which ones to support forwarding links (this is only feasible in situations where multiple RAT connections are provided by a forwarding-enabled network access node). For example, the controller 308 may consider which RAT connections are most “active,” e.g., which RAT connections are receiving the heaviest data traffic, and / or which RAT connections are most likely to receive data, such as paging messages. As previously mentioned, common monitoring may be particularly advantageous for idle mode monitoring for messages such as paging messages and other control information (although all data is considered applicable). Because each RAT connection of the terminal device 200 may operate separately and use different scheduling and formatting parameters, various RAT connections may have different traffic loads at any given time.
[0243] For example, each RAT connection may be in an active state or an idle state (radio access technologies may also have other activity states), an active RAT connection may be assigned dedicated radio resources, and an idle RAT connection may not be assigned any dedicated radio resources. Thus, an active RAT connection may have a large amount of data traffic (e.g., downlink and uplink control and user data), while an idle RAT connection may have minimal data traffic (e.g., limited to paging messages).
[0244] Due to the relatively heavy data traffic of an active RAT connection compared to an idle RAT connection, the controller 308 may choose to consolidate the data traffic for the idle RAT connection into the active RAT connection by establishing a forwarding link with a network access node for the idle RAT connection that forwards the data to the active RAT connection. Since doing so may require the active RAT connection to transmit both the forwarded data and the existing data of the active RAT connection, the forwarded data traffic may be light enough to not overload the active RAT connection.
[0245] For example, an idle RAT connection may be paging over a forwarding link to an active RAT. Therefore, the transmission link is unlikely to become overloaded. Conversely, if the controller 308 chooses to aggregate, for example, a video stream from an active RAT connection into another active RAT connection, the latter RAT connection may become overloaded (although this may depend on the capacity of the network access node tasked with the transmission and the current traffic situation).
[0246] Thus, the controller 308 may be configured to select which RAT connections to temporarily disconnect and which RAT connections to activate as forwarding links based on data traffic load. The controller 308 may further consider which RAT connections are most likely to receive incoming data; for example, a given RAT connection may generally receive incoming data, such as paging messages, more frequently than other RAT connections, which may be due to the underlying access protocol and / or the current state of the RAT connections. Thus, the controller 308 may identify which RAT connections are more likely to receive incoming data and which RAT connections are less likely to receive incoming data, and subsequently assign the "more likely" RAT connections as forwarding links for the "less likely" RAT connections.
[0247] Additionally or alternatively, the controller 308 may be configured to consider the coverage range of the network access node associated with each RAT connection when selecting which RAT connection to terminate and which to use for the forwarding link. For example, cellular network access nodes (e.g., base stations) generally have significantly larger coverage areas than short-range network access nodes (e.g., WLAN APs, Bluetooth master devices, etc.), where similar comparisons may generally be made for various radio access technologies.
[0248] Because a RAT connection associated with a larger coverage area supports a wider range of movement for terminal device 200, controller 308 may choose to temporarily disconnect the narrower-range RAT connection (e.g., by sending a forwarding configuration command to a network access node providing the narrower-range RAT connection) and thus utilize the wider-range RAT connection as a forwarding link. Thus, in the example environment of FIG. 11, controller 308 may choose to temporarily disconnect the second RAT connection provided by network access node 1106 and utilize the first RAT connection via network access node 1108 as a forwarding link.
[0249] Not only do cellular network access nodes provide wider coverage areas than short-range network access nodes, but many cellular radio access networks may collectively provide more consistent coverage over a wide geographic area. For example, Wi-Fi network access nodes available to terminal device 200 (e.g., to which terminal device 200 has permission or entitlement to connect) may only be available sporadically on a geographic basis, such as in a home, office, or particular public or private location, and may not generally form a contiguous geographic area. Thus, if terminal device 200 moves outside the coverage area of network access node 1106, for example, terminal device 200 may not have any available Wi-Fi network access nodes to connect to. Thus, if terminal device 200 selects to use a Wi-Fi connection as a forwarding link and subsequently moves out of coverage of the associated Wi-Fi network access node, terminal device 200 may not be able to continue using the Wi-Fi connection as a forwarding link.
[0250] However, it may be assumed that cellular radio access networks generally have large, contiguous coverage areas formed by the cells collectively, and therefore, even if terminal device 200 moves out of the coverage area of network access node 1108, terminal device 200 will have another cellular network access node available. Thus, controller 308 may additionally or alternatively consider which underlying radio access network provides more contiguous coverage, with cellular radio access networks and other long-range radio access networks generally considered to provide more contiguous coverage than short-range radio access networks such as Wi-Fi and Bluetooth.
[0251] Additionally or alternatively, in some aspects, the controller 308 may take into account the delay and / or latency requirements of one or more RAT connections. For example, certain data streams, such as voice and other multimedia streaming, may have strict delay and latency requirements and may not be able to tolerate large delays / latencies. Thus, if one RAT connection has strict delay / latency requirements, the controller 308 may choose to temporarily disconnect another RAT connection and continue to use the RAT connection with the strict delay / latency requirement as the transport link, such that the ability of the strict RAT connection to continue receiving the underlying data seamlessly can be maintained.
[0252] Additionally or alternatively, in some aspects, the controller 308 may consider security requirements of one or more RAT connections. For example, a particular data stream may have high priority security requirements and therefore may only be transported over a secure link. Thus, for example, if one of the RAT connections has very strict security requirements, the controller 308 may choose to temporarily disconnect another RAT connection and continue to use the RAT connection with the strict security requirements as the transport link.
[0253] Thus, the controller 308 may be configured to utilize any or a combination of these factors when selecting which RAT connections to use as forwarding links and which RAT connections to temporarily disconnect (e.g., those to consolidate on the forwarding link).
[0254] The controller 308 may additionally or alternatively be configured to adapt or switch the forwarding link based on a change in the status of the RAT connection. For example, in the example scenario of FIG. 11 where the controller 308 integrates Wi-Fi traffic with an LTE connection over a forwarding link, the Wi-Fi connection may initially be idle, while the LTE connection may initially be active. However, upon receiving a forwarded Wi-Fi data packet or a network management message over the LTE connection, the controller 308 may activate the second communication module 306b to receive the incoming Wi-Fi data. Thus, when the Wi-Fi connection transitions from an idle state to an active state while the LTE connection remains active, the controller 308 may not perform any forwarding; however, when the LTE connection eventually transitions to an idle state, the controller 308 may merge the LTE connection with the Wi-Fi connection by sending a forwarding setup command to the network access node 1108, which instructs the network access node 1108 to forward incoming LTE data packets to the Wi-Fi network address of the terminal device 200.
[0255] Similarly, if both the LTE connection and the Wi-Fi connection are initially idle, the controller 308 may choose to consolidate data traffic from one RAT connection to the other via a forwarding link and proceed to monitor only data traffic on the remaining active RAT connection, which may be done, for example, by setting up a forwarding link at the network access node 1108 that reroutes LTE data packets addressed to the terminal device 200 to the Wi-Fi connection.
[0256] If the controller 308 then receives a forwarded LTE data packet containing an LTE paging message from the network access node 1106 over the Wi-Fi connection, the controller 308 subsequently activates the first communications module 306a supporting the currently active LTE connection, "switches" the forwarding links by deactivating (via a forwarding deactivation command) the existing forwarding link at the network access node 1108, and establishing (via a forwarding deactivation command) a new forwarding link at the network access node 1106 that forwards Wi-Fi data traffic for the still-idle Wi-Fi connection to the currently active LTE connection. Accordingly, all such variations are within the scope of this disclosure.
[0257] While the forwarding links described above have been described as being explicitly activated and deactivated by forwarding configuration and activation commands, respectively, in some aspects, the controller 308 may establish a forwarding link with an expiration time after which the forwarding network access node terminates the forwarding link. For example, the controller 308 may decide to establish a forwarding link for a predetermined period of time defined, for example, on the order of milliseconds, seconds, minutes, hours, etc., and thus may explicitly identify the expiration time in a forwarding configuration command provided to a network access node, such as network access node 1106. Upon receiving and identifying a forwarding configuration command, the control module 1208 may register the forwarding link as a forwarding entry in the forwarding table 1112 and may further trigger an associated timer with an expiration time equal to the expiration time specified in the forwarding configuration command. The control module 1208 may then forward all data packets addressed to the terminal device 200 according to the registered forwarding link until the timer expires, after which the control module 1208 may unilaterally deactivate the forwarding link (e.g., by setting the active flag to "off" or deleting the forwarding entry from the forwarding table 1112) and refrain from rerouting any further data packets addressed to the terminal device 200 (e.g., until another forwarding setup message is received).
[0258] The RAT connections involved in the forwarding and common monitoring scheme described above may be part of a multi-SIM scheme, where, for example, some RAT connections are associated with a first SIM and other RAT connections are associated with a second SIM.
[0259] 14 illustrates a method 1400 for performing wireless communications in connection with the forwarding and common monitoring scheme described above. As shown in FIG. 14, method 1400 includes transmitting and receiving data over a first wireless access connection with a first network access node (1410), transmitting and receiving data over a second wireless access connection with a second network access node (1420) (the first wireless access connection and the second wireless access connection utilizing different radio access technologies), establishing a forwarding link (1430) that instructs the first network access node to reroute data intended for the first wireless access connection to the second wireless access connection, and receiving data related to the first wireless access connection and the second wireless access connection over the second wireless access connection (1440).
[0260] 11-13 may be further incorporated into method 1400. In particular, method 1400 may be configured to perform additional and / or alternative processes as described in detail with respect to terminal device 200. power efficiency
[0261] Power management can be an important consideration for both network access nodes and terminal devices in wireless communication networks. For example, terminal devices need to use power-efficient designs to reduce battery drain and increase operating time, while network access nodes can pursue power efficiency to reduce operating costs. Therefore, power-efficient designs and features can be very useful.
[0262] 15 illustrates a wireless communication network 1500 according to some aspects that may include terminal devices 1502 and 1504 in addition to network access nodes 1510 and 1512. While certain aspects of the present disclosure may describe particular wireless communication network configurations (e.g., LTE, UMTS, GSM, other Third Generation Partnership Project (3GPP) networks, WLAN / Wi-Fi, Bluetooth, 5G, mmWave, etc.), the subject matter detailed herein is considered illustrative in nature and thus may be applied to any other wireless communication network as well. The number of terminal devices and network access nodes in wireless communication network 1500 is exemplary and may be expanded to any number.
[0263] Thus, in an exemplary cellular configuration network, the access nodes 1510 and 1512 may be base stations (e.g., eNodeBs, NodeBs, base transceiver stations (BTSs), etc.), and the terminals 1502 and 1504 may be cellular terminals (e.g., mobile stations (MSs), user equipment (UEs), etc.). Thus, the network access nodes 1510 and 1512 may interface (e.g., via a backhaul interface) with a cellular core network, such as an Evolved Packet Core (EPC for LTE), a Core / Network (CN for UMTS), or other cellular core network, which may also be considered part of the wireless communication network 1500. The cellular core network may interface with one or more external data networks. In an exemplary short-range setting, network access nodes 1510 and 1512 may be access points (APs, e.g., WLAN or Wi-Fi APs) and terminal devices 1502 and 1504 may be short-range terminal devices (e.g., stations (STAs)). Network access nodes 1510 and 1512 may interface with one or more external data networks (e.g., internally or via external routers).
[0264] Thus, network access nodes 1510 and 1512 (and other network access nodes of wireless communication network 1500 not explicitly shown in FIG. 15 ) can provide a wireless access network to terminal devices 1502 and 1504 (and other terminal devices of wireless communication network 1500 not explicitly shown in FIG. 15 ). In an exemplary cellular setting, the wireless access network provided by network access nodes 1510 and 1512 can enable terminal devices 1502 and 1504 to wirelessly access a core network via wireless communications. The core network can provide switching, routing, and transmission of traffic data associated with terminal devices 1502 and 1504 and provide access to various internal data networks (e.g., control nodes, other terminal devices on wireless communication network 1500, etc.) and external data networks (e.g., data networks providing voice, text, multimedia (audio, video, images), and other Internet and application data). In an exemplary short-range setting, the wireless access network provided by network access nodes 1510 and 1512 may provide access to an internal data network (e.g., other terminal devices connected to wireless communication network 1500) and an external data network (e.g., a data network providing voice, text, multimedia (audio, video, images), and other Internet and application data). Network access nodes 1510 and 1512 may also be network access nodes for any other type of wireless access technology, thus providing wireless access networks to nearby terminal devices as well.
[0265] The radio access network and core network (if applicable) of wireless communication network 1500 may be controlled by network protocols, which may vary depending on the specifications of wireless communication network 1500. Such network protocols may define the scheduling, formatting, and routing of both user and control data traffic through wireless communication network 1500, including the transmission and reception of such data through both the radio access and core network domains of wireless communication network 1500. Thus, terminal devices 1502 and 1504 and network access nodes 1510 and 1512 may follow defined network protocols to transmit and receive data through the radio access network domain of wireless communication network 1500, while the core network may follow defined network protocols to route data in and out of the core network. Exemplary network protocols include LTE, UMTS, GSM, WiMAX, Bluetooth, Wi-Fi, mmWave, etc., any of which may be applicable to wireless communication network 1500.
[0266] Both the radio access network and the core network of wireless communication network 1500 can be controlled by network protocols, which may vary depending on the specifications of wireless communication network 1500. Such network protocols can define the scheduling, formatting, and routing of both user and control data traffic through wireless communication network 1500, including the transmission and reception of such data through both the radio access and core network domains of wireless communication network 1500. Thus, terminal devices 1502 and 1504 and network access nodes 1510 and 1512 can follow defined network protocols to transmit and receive data through the radio access network domain of wireless communication network 1500, while the core network can follow defined network protocols to route data in and out of the core network. Exemplary network protocols include LTE, UMTS, GSM, WiMax, Bluetooth, Wi-Fi, etc., or other next generation technologies such as 2G, 3G, 4G, 5G, and 6G, any of which may be applicable to wireless communication network 1500.
[0267] 16 illustrates the internal configuration of terminal device 1502, which may include antenna system 1602, radio frequency (RF) transceiver 1604, baseband modem 1606 (including physical layer processing module 1608 and controller 1610), data source 1612, memory 1614, data sink 1616, and power supply 1618. Although not explicitly shown in FIG. 16, terminal device 1502 may include one or more additional hardware, software, and / or firmware components (e.g., a processor / microprocessor, a controller / microcontroller, other specific or general hardware / processors / circuitry, etc.), peripheral(s), memory, power supply, external device interface(s), subscriber identity module(s) (SIM(s)), user input / output devices (e.g., display(s), keypad(s), touchscreen(s), speaker(s), external button(s), camera(s), microphone(s), etc.).
[0268] Terminal 1502 can transmit and receive wireless signals over one or more wireless access networks. Baseband modem 1606 can direct such communication functions of terminal 1502 in accordance with communication protocols associated with each wireless access network and can exercise control over antenna system 1602 and RF transceiver 1604 to transmit and receive wireless signals in accordance with formatting and scheduling parameters defined by each communication protocol. While various practical designs may include separate communication subsystems (e.g., separate antennas, RF transceivers, physical layer processing modules, and controllers) for each supported wireless access technology, for purposes of simplicity, the configuration of terminal 1502 shown in FIG. 16 depicts only a single instance of each such component.
[0269] The terminal device 1502 can transmit and receive radio signals with an antenna system 1602, which can be a single antenna or an antenna array including multiple antennas and can further include analog antenna combining and / or beamforming circuitry. In the receive path (RX), an RF transceiver 1604 can receive analog radio frequency signals from the antenna system 1602 and perform analog and digital RF front-end processing on the analog radio frequency signals to generate digital baseband samples (e.g., in-phase / quadrature samples) that are provided to the baseband modem 206. Thus, the RF transceiver 1604 can include analog and digital receive components, including amplifiers (e.g., low-noise amplifiers (LNAs)), filters, RF demodulators (e.g., RF IQ demodulators), and analog-to-digital converters (ADCs), to convert the received radio frequency signals to digital baseband samples. In the transmit path (TX), the RF transceiver 1604 receives digital baseband samples from the baseband modem 1606 and performs analog and digital RF front-end processing on the digital baseband samples to generate analog radio frequency signals to provide to the antenna system 1602 for wireless transmission. Thus, the RF transceiver 1604 may include analog and digital transmission components, including amplifiers (e.g., power amplifiers (PAs)), filters, RF modulators (e.g., RF IQ modulators), etc.), and digital-to-analog converters, to mix the digital baseband samples received from the baseband modem 1606 to generate analog radio frequency signals for wireless transmission by the antenna system 1602. The baseband modem 1606 may control the reception and transmission of the RF transceiver 1604, including the identification of transmissions, and receive radio frequencies for operation of the RF transceiver 1604.
[0270] As shown in FIG. 16 , the baseband modem 1606 can include a physical layer processing module 1608, which can perform physical layer (Layer 1) transmit and receive processing to prepare outgoing transmit data generated by the controller 1604 for transmission via the RF transceiver 1604. Accordingly, the physical layer processing module 1608 can perform one or more of the following: error detection, forward error correction encoding / decoding, channel coding and interleaving, physical channel modulation / demodulation, physical channel mapping, radio wave measurement and search, frequency and time synchronization, antenna diversity processing, power control and weighting, rate matching, retransmission processing, etc. The physical layer processing module 1608 can be structurally implemented as a hardware-defined module, e.g., one or more dedicated hardware circuits or FPGAs; a software-defined module, e.g., a processor configured to retrieve and execute program code defining operation, control, and I / O instructions (e.g., software and / or firmware) stored on a non-transitory computer-readable storage medium; or a mixed hardware- and software-defined module. 16, the physical layer processing module 1608 may include a physical layer controller configured to retrieve and execute software-defined instructions that control various hardware and software processing components of the physical layer processing module 1608 in accordance with physical layer control logic defined by the communications protocol for the associated radio access technology. Additionally, although the physical layer processing module 1608 is depicted as a single component in FIG. 16, in some aspects the physical layer processing module 1608 may be collectively implemented as separate sections of a physical layer processing component, with each section dedicated to physical layer processing for a particular radio access technology.
[0271] Terminal 1502 may be configured to operate according to one or more radio access technologies directed by controller 1610. Thus, controller 1610 may be responsible for controlling the wireless communication components of terminal 1502 (antenna system 1602, RF transceiver 1604, and physical layer processing module 1608) according to the communication protocol of each supported radio access technology, and thus may represent the access and non-access stratum (NAS) (including Layer 2 and Layer 3) of each supported radio access technology. In some aspects, controller 1610 may be structurally embodied as a protocol processor configured to execute protocol software (e.g., from memory 1614 or a local controller or modem memory) and then control the wireless communication components of terminal 1502 to send and receive communication signals according to corresponding protocol control logic defined in the protocol software.
[0272] As such, controller 1610 may be configured to manage the wireless communication functions of terminal device 1502 to communicate with various radio and core network components of wireless communication network 1500 and, therefore, may be configured according to communication protocols for multiple radio access technologies. Controller 1610 can be a unified controller collectively responsible for all supported radio access technologies (e.g., LTE and GSM / UMTS) or may be implemented as multiple separate controllers, each dedicated to a particular radio access technology, such as a dedicated LTE controller and a dedicated legacy controller (or a dedicated LTE controller, a dedicated GSM controller, and a dedicated UMTS controller). Regardless, controller 1610 may be responsible for directing the wireless communication activities of terminal device 1502 according to the communication protocols of the LTE and legacy networks. As described above with respect to physical layer processing module 1608, one or both of antenna system 1602 and RF transceiver 1604 may similarly be divided into multiple dedicated components, each corresponding to one or more supported radio access technologies. Depending on the details of each such component and the number of radio access technologies supported, the controller 1610 can be configured to control the wireless communication operations of the terminal device 1502 hierarchically according to a master / slave radio access technology (RAT) or according to a multi-subscriber identity module (SIM) scheme.
[0273] The terminal device 1502 may also include a data source 1612, a memory 1614, a data sink 1616, and a power source 1618, where the data source 1612 may include a source of communication data above the controller 1610 (e.g., above the NAS / Layer 3), and the data sink 1616 may include a destination of communication data above the controller 1610 (e.g., above the NAS / Layer 3). For example, they may include an application processor of the terminal device 1502 that may be configured to execute various applications and / or programs of the terminal device 1502 at an application layer of the terminal device 1502, such as an operating system (OS), a user interface (UI) to facilitate user interaction with the terminal device 1502, and / or various user applications. The application processor can interface with the baseband modem 1606 (as data source 1612 / data sink 1616) as an application layer to send and receive user data, such as voice data, audio / video / image data, messaging data, application data, basic Internet / web access data, etc., over the wireless network(s) provided by the baseband modem 1606. In the uplink direction, the application layer (data sink 1616) can provide data (e.g., voice over IP (VoIP) packets, UDP packets, etc.) to the baseband modem 1606, which can then encode, modulate, and transmit the data as a wireless signal via the radio transceiver 1604 and antenna system 1602. In the downlink direction, the baseband modem 1606 can demodulate and decode IQ samples provided by the RF transceiver 1604 to generate downlink traffic. The baseband modem 1606 can then provide downlink traffic to the application layer as a data source 1612 .The data source 1612 and data sink 1616 may further represent various user input / output devices of the terminal device 1502, such as display(s), keypad(s), touchscreen(s), speaker(s), external button(s), camera(s), microphone(s), etc., which allow a user of the terminal device 1502 to control various communication functions of the terminal device 1502 related to user data.
[0274] The memory 1614 may embody a memory component of the terminal 1502, such as a hard drive or other such permanent memory device. Although not explicitly shown in FIG. 16, in some aspects, various other components of the terminal 1502 shown in FIG. 16 may further include permanent and non-permanent integrated memory components, such as for storing software program code, buffering data, etc., respectively.
[0275] The power source 1618 may be a power source that provides power to the various electrical components of the terminal device 1502. Depending on the design of the terminal device 1502, the power source 1618 may be a "definite" power source, such as a battery (rechargeable or disposable), or an "indefinite" power source, such as a wired electrical connection. Thus, operation of the various components of the terminal device 1502 may draw power from the power source 1618.
[0276] Terminal devices, such as terminal devices 1502 and 1504 of FIG. 15 , can perform mobility procedures to connect to, disconnect from, and switch between available network access nodes of the radio access network of wireless communication network 1500. Because each network access node of wireless communication network 1500 may have a particular coverage area, terminal devices 1502 and 1504 may be configured to select and reselect among available network access nodes to maintain a strong radio access connection with the radio access network of wireless communication network 1500. For example, terminal device 1502 can establish a radio access connection with network access node 1510, and terminal device 1504 can establish a radio access connection with network access node 1512. If the current radio access connection degrades, terminal device 1502 or 1504 may seek a new radio access connection with another network access node of wireless communication network 1500; for example, terminal device 1504 may move from the coverage area of network access node 1512 to the coverage area of network access node 1510. As a result, the radio access connection with network access node 1512 may degrade, which terminal device 1504 may detect via radio measurements, such as signal strength or signal quality measurements, of network access node 1512. Depending on the mobility procedures defined in an appropriate network protocol of wireless communication network 1500, terminal device 1504 may search for a new radio access connection (which may be triggered at terminal device 1504 or by the wireless access network), such as by performing radio measurements to determine whether any neighboring network access nodes can provide a suitable radio access connection.As the terminal device 1504 may move within the coverage area of a network access node 1510, the terminal device 1504 may identify the network access node 1510 (which may be selected by the terminal device 1504 or by the radio access network) and transfer to a new radio access connection with the network access node 1510. Such mobility procedures, including radio measurements, cell selection / reselection, and handover, are established in various network protocols and may be employed by the terminal device and the radio access network to maintain a strong radio access connection between each terminal device and the radio access network across any number of different radio access network scenarios.
[0277] The various network activities of the terminal devices 1502, 1504 and the network access nodes 1510, 1512 inevitably consume power, such as transmitting, receiving, and processing wireless signals. Furthermore, power consumption is not limited solely to network activity, as many terminal devices can serve purposes other than wireless communication, such as smartphones, laptops, and other user-interactive devices. While terminal devices can generally be low-power devices, many terminal devices may also be mobile or portable and thus must rely on "finite" battery power. Conversely, network access nodes, such as cellular base stations and wireless LAN APs, may typically have "unlimited" (if not limiting) wired power sources; however, high transmit power and infrastructure support demands can consume significant power and, therefore, result in high operating costs. Therefore, power-efficient designs can play a crucial role in extending battery life in terminal devices and reducing operating costs in network access nodes.
[0278] Embodiments disclosed herein may improve power efficiency in wireless access networks through efficient operational and architectural designs in terminal devices and network access nodes to reduce power consumption, thereby extending battery life and reducing operating costs. 2.1 Power Efficiency #1
[0279] According to one aspect of the present disclosure, a radio access network may provide multiple different radio access channel options for terminal devices: For example, as opposed to providing only a single paging, control, traffic data, or random access channel, the radio access network may provide multiple paging / control / random access channels, or multiple “channel instances,” each tailored to different needs, e.g., different power consumption levels (e.g., power efficiency). Thus, terminal devices can selectively select which channel instance to utilize based on desired power efficiency; for example, some terminal devices may choose a low-power consumption channel (which may offer higher power efficiency at the expense of performance), while other terminal devices may choose a “normal” power consumption channel. In addition to power efficiency, terminal devices may also consider latency and reliability requirements when selecting a channel instance. Some aspects may be applied with control, paging, and / or random access channels, each tailored to different power efficiency, reliability, and latency characteristics. These aspects may also be used with common channel aspects, e.g., common channels tailored to specific power efficiency needs.
[0280] Network access nodes and terminal devices can transmit and receive data over specific time-frequency physical channels, with each channel consisting of specific frequency resources (e.g., bands or subcarriers) and defined for a specific time period. The time-frequency resources and data content of such physical channels may be defined by the associated network access protocol; for example, an LTE framework may specify specific time-frequency resources for LTE-specific physical channels, a UMTS framework may specify specific time-frequency resources for UMTS-specific physical channels, etc. Physical channels are conventionally assigned as either uplink or downlink channels, where terminal devices can transmit uplink data using uplink channels and network access nodes can transmit downlink data using downlink channels. Physical channels can further be associated with carrying specific types of data, such as certain channels designated exclusively to carry user data traffic and other channels designated to carry specific types of control data.
[0281] In various aspects, a physical channel may be a specific set of time and / or frequency resources. For example, in some aspects, a physical channel may always be assigned to a dedicated set of frequency resources, such as a subcarrier (or set of subcarriers) that carries only control data in an exemplary configuration of a control channel. Additionally or alternatively, in some aspects, a physical channel may be assigned to time-frequency resources that change over time, e.g., a physical channel is assigned to a set of time-frequency resources (e.g., subcarriers and time periods) that change over time. For example, a paging channel may occupy different time periods and / or subcarriers over time. Thus, a physical channel is not limited to a fixed set of time-frequency resources.
[0282] The allocation of time-frequency resources to physical channels can depend on the corresponding radio access technology. While LTE is used to describe the allocation of time-frequency resources to physical channels, this description is illustrative and applicable without limitation to other radio access technologies. The allocation of time-frequency resources to LTE radio access channels is defined by 3GPP Technical Specification (TS) 36.211 V13.1.0, "Physical Channels and Modulation" ("3GPP TS 36.211"). As detailed in 3GPP TS 36.211, the LTE downlink uses a multi-subcarrier frequency scheme to discretize the system bandwidth across time and frequency. In this scheme, the system bandwidth is divided into a set of subcarriers, each capable of carrying a symbol during a single symbol period. In time, the LTE downlink (frequency division duplex (FDD)) utilizes 10 ms radio frames, with each radio frame divided into 10 subframes of 1 ms duration. Each subframe is further divided into two slots, each containing 6 or 7 symbol periods, depending on the length of the cyclic prefix (CP). In frequency, the LTE downlink utilizes a set of equally spaced subcarriers, each separated by 15 kHz, where each block of 12 subcarriers spanning one slot is designated as a resource block (RB). Thus, the basic time-frequency resource may be a single subcarrier spanning a single symbol period, defined by 3GPP as a resource element (RE), with each RB containing 180 REs.
[0283] FIG. 17 illustrates an exemplary downlink resource grid 1700 according to some aspects, which may be an LTE resource grid showing subcarriers for two subframes and one resource block. Each unit block in the downlink resource grid 1700 may represent one RE, e.g., one symbol period for one subcarrier, for a typical CP length. As specified by 3GPP, a downlink subframe may generally be divided into a control region and a data region, with the first few symbols allocated for control data in the control region and the remaining symbols allocated for user data traffic in the data region. Depending on the system bandwidth and control format, each subframe may include one to three control symbols at the beginning of each subframe (as indicated by a control format indicator (CFI) provided on a physical CFI channel (PCFICH) appearing in a specific RE within the first symbol of each subframe).
[0284] Figure 17 shows the control region containing physical downlink control channel (PDCCH) data. While the data region may generally contain physical downlink shared channel (PDCCH) data, REs in both regions may be allocated to other physical channels, such as the physical broadcast channel (PBCH), physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), physical multicast channel (PMCH), and the aforementioned PCFICH detailed in 3GPP TS 36.211. Thus, each LTE physical downlink channel may consist of specific time-frequency resources (REs) carrying data specific to that channel.
[0285] Thus, physical time-frequency resources (REs) of the resource grid can be allocated to specific physical channels. Each physical channel can carry specific data provided by one or more transmission channels, which in turn can provide specific data for specific physical channels provided by one or more specific logical channels, respectively. Figure 18 shows an example channel mapping illustrating transmission channel mapping for PDSCH and PDCCH physical channels. As shown in Figure 18, the PDCCH channel can carry downlink control information (DCI) data, which is a control message addressed to a specific UE that can be transmitted on the PDCCH. Meanwhile, the PDSCH channel can carry data provided by the paging channel (PCH) and downlink shared channel (DL-SCH) logical channels. The PCH can carry paging messages addressed to a specific UE, and the DL-SCH can carry primarily user data traffic in addition to some control information. Thus, the REs of the downlink resource grid 1700 may be assigned directly to physical channels, but each physical channel may contain data provided over an associated transport channel, as well as logical channels containing traffic data, control data, and paging data.
[0286] Thus, a terminal device 1502 or 1504 receiving a downlink signal from a network access node, such as network access node 1510 or 1512, can process each data element contained in the downlink signal to recover the data from each channel. In an exemplary LTE setting, terminal device 1502 can process a PDCCH RE to recover important control data (specified in a DCI message addressed to terminal device 1502) that can identify the presence of other received data in the PDSCH RE addressed to terminal device 1502. The type of data indicated in the DCI message can depend on the current radio access state of terminal device 1502. For example, if terminal device 1502 is currently in a connected radio state, terminal device 1502 can be assigned dedicated downlink resources to receive traffic data on the PDSCH. Thus, the terminal device 1502 can monitor the PDCCH during each subframe to identify DCI messages addressed to the terminal device 1502 (e.g., via a radio network temporary identifier (RNTI)), which can specify the location of the PDSCH RE containing downlink data directed to the terminal device 1502, in addition to other parameters related to the downlink data.
[0287] Alternatively, if the terminal device 1502 is currently in a wireless state, the terminal device 1502 may not be in a position to receive traffic data on the PDSCH and may instead only be in a position to receive paging messages signaling upcoming traffic data intended for the terminal device 1502. Thus, the terminal device 1502 may monitor the PDCCH in specific subframes (e.g., according to periodic paging occasions) to identify a paging control message (a DCI message addressed with the Paging RNTI (P-RNTI)) indicating that the PDSCH contains a paging message. The terminal device 1502 (along with other idle mode UEs) receives the paging message on the PDSCH and identifies whether the paging message is intended for the terminal device 1502 (e.g., by the System Architecture Evolution (SAE) Temporary Mobile Subscriber Identity (S-TMSI) or International Mobile Subscriber Identity (IMSI) included in the paging message).
[0288] In other words, the terminal device 1502 can monitor a control channel and a paging channel for control messages and paging messages to the terminal device 1502, where both the paging channel and the control channel can be comprised of specific time-frequency resources. Furthermore, any reference to LTE is for illustrative purposes only and is utilized solely to provide context information for radio resource allocation for the physical channels. Various other radio access technologies can also specify control and paging channels that are comprised of specific time-frequency resources that the terminal device may require to monitor for the presence of control and paging messages destined for the terminal device. Thus, physical channels in other radio access technologies can similarly utilize dynamic allocation of time-frequency resources.
[0289] Terminal device 1502 can transmit uplink data to a network access node, such as network access nodes 1510 and 1512. The uplink resource grid can use a similar time-frequency discretization scheme as the downlink resource grid, but the resource allocation scheme per terminal device can differ slightly between the downlink and uplink. This can depend on the details of the radio access technology; some radio access technologies can use different uplink and downlink allocation schemes and physical layer waveforms in the uplink and downlink, while other radio access technologies can use the same uplink and downlink allocation schemes and / or physical layer waveforms in the uplink and downlink. For example, the LTE downlink primarily utilizes orthogonal frequency division multiple access (OFDMA) for multiple access. Here, RBs can be allocated to different users in a distributed and non-contiguous manner; thus, along the frequency axis, RBs addressed to a particular user can be interleaved with RBs addressed to other users and may not be adjacent in the downlink resource grid. In contrast, the uplink primarily utilizes single-carrier frequency division multiple access (SC-FDMA), where at any given time, only a set of adjacent RBs along the frequency axis can be allocated to a single user.
[0290] FIG. 19 illustrates an exemplary uplink resource grid 1900, which may be an LTE resource grid spanning 25 resource blocks and two radio frames, constituting an exemplary 5 MHz system bandwidth for FDD. As noted above, uplink resource allocation may generally be restricted to using only adjacent blocks along the frequency axis. The radio resources in the uplink resource grid 1900 are shown on a different scale than the downlink resource grid 1700, and each unit block in the uplink resource grid 1900 represents the subcarriers of a single resource block over one subframe (two resource blocks in total).
[0291] As indicated by the hatching in Figure 19, the time-frequency resources of the uplink resource grid 1900 may be allocated to specific uplink physical channels, including the physical uplink control channel, the physical uplink shared channel, and the physical random access channel. PUCCH allocations may generally be at the upper and lower ends of the system bandwidth, while the remainder of the system bandwidth may generally be allocated for PUSCH transmission. Thus, a UE, such as terminal device 1502, may be allocated radio resources (via an uplink grant provided by the radio access network on the PDCCH) to transmit uplink traffic data on the PUSCH and uplink control data on the PUCCH.
[0292] As specified by wireless communication standards such as 3GPP TS 36.211, specific resource blocks, typically located in the central region of the system bandwidth, may be allocated for PRACH transmission. A UE, such as terminal device 1502, may utilize the PRACH to establish an active radio connection with an eNodeB, such as network access node 1510, during a transition from an idle state to a connected state, during handover to network access node 1510, or when timing synchronization with network access node 1510 is lost. In contrast to PUCCH and PUSCH radio resources, which are uniquely assigned to individual UEs, an eNodeB may broadcast system information (e.g., a system information block (SIB)) identifying PRACH radio resources to all UEs in a cell. Thus, PRACH radio resources may be usable by any one or more UEs. Thus, the terminal device 1502 may receive such system information from the network access node 1510 to identify a PRACH configuration, which may specify both the specific radio resources (in time and frequency) allocated for PRACH transmission and other important PRACH configuration parameters. The terminal device 1502 may then generate and transmit a PRACH transmission including a unique PRACH preamble that identifies the terminal device 1502 during the PRACH opportunity. The network access node 1510 may then receive wireless data during the PRACH opportunity and decode the received wireless data to recover all PRACH transmissions transmitted by nearby UEs based on the unique PRACH preambles generated by each UE. The network access node 1510 may then initiate establishment of an active wireless connection for the terminal device 1502.
[0293] Thus, a terminal device can transmit and receive data on specific uplink and downlink channels defined as time-frequency radio resources. These channels may include paging, random access, control channels, traffic data channels, and various other channels depending on the details of the associated radio access standard. As described above in the exemplary case of LTE, these may include the PDCCH (control), PDSCH (traffic data), PUCCH (control), PUSCH (traffic data), and PRACH (random access), where the PDCCH and PDSCH may also be considered "physical" paging channels due to the transfer of paging DCI messages (addressed by DCI 1C, P-RNTI) on the PDCCH and RRC paging messages on the PDSCH. Regardless of the details, the physical channels for each radio access technology are defined as time-frequency resources available for the transmission and reception of specific data by terminal devices and network access nodes. Thus, although each radio access standard may have a unique physical channel scheme, the common underlying characteristics and uses of all radio access channels make the aspects disclosed herein applicable to the radio channels of any radio access technology.
[0294] Instead of providing only a single "instance" of such a channel, various aspects may provide multiple instances of a physical channel with different characteristics. Furthermore, one or more channel instances may have characteristics tailored to a particular power efficiency, latency, and / or reliability, allowing terminal devices to select which channel instance to utilize based on their current power efficiency and / or data connection characteristics (including reliability and latency). Different channel instances may each utilize different settings, such as period, time, expected traffic, etc., to enable each channel instance to effectively provide a desired power efficiency, latency, and reliability level. Furthermore, various channel instances may be provided via different radio access technologies, where a channel instance provided by a lower-power radio access technology may provide a more power-efficient option than another channel instance provided by a higher-power radio access technology. Similarly, certain radio access technologies may provide higher reliability and / or lower latency, thus providing channel instances of varying reliability and latency across different radio access technologies.
[0295] FIG. 20 illustrates an exemplary network scenario of a wireless communication network 2000 according to one aspect of the present disclosure. As shown in FIG. 20, the wireless communication network 2000 may include a terminal device 1502, a network access node 2002, a network access node 2004, a network access node 2006, and a core network 2008. In some aspects, the network access nodes 2002-2006 may be configured according to the same radio access technology, while in other aspects, the network access nodes 2002-2006 may be configured according to different radio access technologies. For example, in the exemplary scenario, the network access node 2002 may be a cellular base station, while the network access nodes 2004 and 2006 may be short-range access points such as an eNodeB 2002, a WLAN AP 2004, and a Bluetooth Low Energy (BT LE) node 2006. Other exemplary scenarios having different radio access technologies are also within the scope of the present disclosure.
[0296] Network access nodes 2002-2006 may be part of a radio access network of wireless communication network 2000 to provide wireless access connectivity to terminal devices, such as terminal device 1502, and thus provide connectivity to core network 2008 and other external data networks (e.g., external packet data networks, Internet Protocol (IP) Multimedia Subsystem servers, and other Internet-accessible data networks). The description of wireless communication network 2000 below is illustrative, and other radio access technologies may be incorporated into wireless communication network 2000, including, for example, other 2G, 3G, 4G, 5G, etc.
[0297] The terminal device 1502 may transmit and receive radio signals on various physical channels using various network access nodes 2002-2006 of the wireless communication network 2000. The network access nodes 2002-2006 may provide respective physical channels according to the details of their respective RATs, which may be the same or different, as described above.
[0298] One or more of the network access nodes 2002-2006 may provide a single "instance" of each channel type, e.g., see additionally FIG. 17. The network access node 2002 may provide a single control channel instance in which the control channel for each subframe has a constant, uniform configuration. Similarly, the network access node 2002 may provide a single random access channel instance according to a random access channel configuration, a single data traffic channel instance, a single uplink control channel instance, and a single uplink data traffic channel instance. In other words, the terminal device 1502 may not be able to freely select between multiple instances of each particular channel.
[0299] Thus, according to aspects of the present disclosure, a network access node, such as network access node 2002, may provide multiple channel instances, e.g., multiple physical channel configurations for a given channel type, thereby enabling a terminal device to select a channel instance according to the terminal device's operational profile. As shown in FIG. 20, in an exemplary application, network access node 2002 may provide a broadcast channel BCH, first and second paging channels PCH1 and PCH2, first and second random access channels RACH1 and RACH2, and / or first and second control channels CCH1 and CCH2. Thus, a terminal device served by network access node 2002 may have the option of selecting different channel instances (PCH1 vs. PCH2, RACH1 vs. RACH2, CCH1 vs. CCH2) when transmitting and receiving associated data. Although particular channel types are shown herein, some aspects, such as the network access node 2002, may provide other types of channel instances, such as multiple traffic data channel instances, e.g., first and second downlink data traffic channels, first and second uplink data traffic channels, etc. Additionally or alternatively, the number of channel instances for each channel type may be scaled to any amount.
[0300] One or more channel instances may be differently configured to have specific characteristics, for example, to provide different levels of power efficiency, latency, and / or reliability. For example, PCH1 may be configured to enable lower power consumption than PCH2 for terminal devices utilizing the channel; similarly, CCH1 may provide lower power consumption than CCH2, while RA...
Claims
1. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors (15912) of a communication device (13602), cause the one or more processors (15912) to: determining that the communication device (13602) is in a scenario when the battery power of the communication device (13602) falls below a battery power threshold; A step of classifying data from one or more applications (15908, 15910) of the communication device (13602) into a plurality of priorities, classifying data into the plurality of priorities includes classifying data from highest priority to lowest priority based on usage of the one or more applications (15908, 15910) over time; throttling said data from said one or more applications (15908, 15910) based on respective priorities while said communication device (13602) is in said scenario, throttling the data includes transmitting lower priority data with a longer transmission delay than the highest priority data; A step of terminating the narrowing when the communication device (13602) exits the scenario, The communication device (13602) is determined to have exited the scenario by: the battery power exceeding the battery power threshold; the battery power exceeds a second battery power threshold; and / or The communication device (13602) is connected to a charging power source. When at least one of the following occurs: Non-transitory computer-readable medium.
2. The non-transitory computer-readable medium of claim 1 , wherein the scenario is a power constrained scenario.
3. A communication device (13602) comprising: a detection circuit (15906) configured to determine that the communication device (13602) is in a certain scenario when the battery power of the communication device (13602) falls below a battery power threshold; A classification circuit (15904) configured to classify data from one or more applications (15908, 15910) of the communication device (13602) into a plurality of priorities, the classification circuit (15904) is configured to classify data from highest priority to lowest priority based on usage of the one or more applications (15908, 15910) over time; a traffic control circuit (15902) configured to throttle the data from the one or more applications (15908, 15910) based on their respective priorities while the communication device (13602) is in the scenario; the traffic control circuit (15902) is configured to transmit the lowest priority data with a longer transmission delay than the highest priority data; The traffic control circuit (15902) is further configured to terminate the throttling when the communication device (13602) exits the scenario; The communication device (13602) is determined to have exited the scenario when: the battery power exceeding the battery power threshold; the battery power exceeds a second battery power threshold; and / or The communication device (13602) is connected to a charging power source. When at least one of the following occurs: Communications equipment.
4. 1. A method for reducing power consumption comprising: determining that the communication device (13602) is in a scenario when the battery power of the communication device (13602) falls below a battery power threshold; A step of classifying data from one or more applications (15908, 15910) of the communication device (13602) into a plurality of priorities, classifying data into the plurality of priorities includes classifying data from highest priority to lowest priority based on usage of the one or more applications (15908, 15910) over time; throttling said data from said one or more applications (15908, 15910) based on respective priorities while said communication device (13602) is in said scenario, throttling the data includes transmitting the lowest priority data with a longer transmission delay than the highest priority data; A step of terminating the narrowing when the communication device (13602) exits the scenario, The communication device (13602) is determined to have exited the scenario by: the battery power exceeding the battery power threshold; the battery power exceeds a second battery power threshold; and / or The communication device (13602) is connected to a charging power source. When at least one of the following occurs: method.
Citation Information
Patent Citations
Radio communication device and route search method
JP2005303998A
Control device, communication device, communication apparatus, electronic device and information processing device
JP2006048630A
Uplink communication method and wireless terminal in wireless communication system
JP2008072194A
Method and apparatus for transmitting and receiving small data in a mobile communication system
JP2015519854A
System and method for applications management in a networked vehicular environment
US8989954B1
Cited By
Bridging mesh device controller for implementing a scene
US20240097932A1
