Source: https://patents.google.com/patent/JP5226860B2/en
Timestamp: 2020-02-26 11:21:33
Document Index: 264290452

Matched Legal Cases: ['art 200', 'art 200', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 600', 'art 700', 'art 900', 'art 1000', 'art 200', 'art 200', 'art 400', 'art 400']

JP5226860B2 - Method and apparatus for communicating and / or using load information to support distributed traffic scheduling decisions - Google Patents
Method and apparatus for communicating and / or using load information to support distributed traffic scheduling decisions Download PDF
JP5226860B2
JP5226860B2 JP2011505151A JP2011505151A JP5226860B2 JP 5226860 B2 JP5226860 B2 JP 5226860B2 JP 2011505151 A JP2011505151 A JP 2011505151A JP 2011505151 A JP2011505151 A JP 2011505151A JP 5226860 B2 JP5226860 B2 JP 5226860B2
JP2011505151A
JP2011520331A (en
ハンデ、プラシャンス
2008-04-15 Priority to US4503008P priority Critical
2008-04-15 Priority to US61/045,030 priority
2008-11-10 Priority to US12/268,138 priority
2008-11-10 Priority to US12/268,138 priority patent/US8750116B2/en
2009-04-14 Application filed by クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ filed Critical クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ
2009-04-14 Priority to PCT/US2009/040576 priority patent/WO2009129268A2/en
2011-07-14 Publication of JP2011520331A publication Critical patent/JP2011520331A/en
2013-07-03 Publication of JP5226860B2 publication Critical patent/JP5226860B2/en
RELATED APPLICATION This patent application is entitled “NOTES ON LOAD-SPILLAGE BASED LINK SCHEDULING MECHANISM” filed on April 15, 2008, assigned to the assignee of the present application and expressly incorporated herein by reference. Claims priority of provisional application 61 / 045,030.
Various embodiments relate to wireless communications, and more particularly to methods and apparatus related to peer-to-peer communications.
In wireless communication networks without centralized control, efficient scheduling of traffic air link resources can be a difficult task. The approach of allocating the same weight or amount of airlink traffic resources to each connection is simple in design but tends to be uneconomical. For example, the type of data being communicated, the importance of the data being communicated, latency considerations, backlogs, queue status, current channel conditions, congestion, applications being run, etc. A particular communication device or pair of devices that may have different needs. Also, depending on the type, the device may have various device functions, for example, various traffic queue buffer sizes, various display functions, and the like. Also, the same device may have different needs over time based on the capabilities of other devices sharing the current connection. Thus, the importance of a particular device that can use a traffic segment is expected to vary over time.
When using distributed scheduling techniques for traffic scheduling, it is useful for individual devices making scheduling decisions to be aware of the current needs of other devices competing for the same resources. There may be. In view of the above, there is a need for a new method and apparatus that supports the exchange of load related information between nearby communication devices that are competing to use the same air link traffic resource. As the use of air link resources for control signaling tends to make those air link resources unavailable for traffic signaling, such methods and apparatus tend to minimize overhead It would be advantageous to efficiently configure control signaling.
Methods and apparatus related to scheduling of air link resources, eg, traffic segments, in a wireless communication system are described. The various methods and apparatus described are suitable for wireless peer-to-peer networks with distributed traffic scheduling, eg, ad hoc peer-to-peer networks. In some embodiments, individual wireless terminals corresponding to peer-to-peer connections wishing to communicate traffic signals may transmit transmitter yielding decisions and / or receiver yielding decisions per traffic slot. )I do. Load information is used to intentionally skew transmitter yield decisions in response to conditions and / or needs in the system.
A link load weight value is generated based on the intended transmitter load related information and / or the intended receiver load related information. One feature of various embodiments includes communication of traffic request parameters and / or link load weight values between wireless communication devices as part of scheduling signaling. In some embodiments, the traffic transmission request signal carries a link load weight value or one or more traffic request parameters used to derive a link load weight value. In some embodiments, the traffic transmission request response signal includes a link load weight value. The inclusion of the link load weight value in the traffic transmission request response signal allows the restoration of the link load weight value by a plurality of different devices that may have various channel conditions for the request response signal transmitter. These different devices may benefit from utilizing the recovered link load weight values and taking into account load information in transmitter concession decisions when making transmitter concession decisions for traffic signaling in the traffic segment. it can.
In some embodiments, as part of transmitter concession determination, the spillage value, weighted SINR, and interference cost estimate are based on one or more link load weight values and channel state measurement information. Calculate one or more of them.
According to some embodiments, an exemplary method of operating a first communication device receives a transmission request from a second communication device, generates a link load weight value, Transmitting a transmission request response including the link load weight value in response to a transmission request from a communication device. According to some embodiments, an exemplary first communication device receives a transmission request from a second communication device, generates a link load weight value, and At least one processor configured to transmit a transmission request response including the link load weight value in response to the transmission request; and a memory coupled to the at least one processor.
According to some embodiments, an exemplary method of operating a first communication device receives a request response from a second communication device that is responsive to a transmission request from the first communication device; Receiving a first link load weight value from a third communication device and making a transmitter yield determination based on the link load weight value received from the third communication device. According to some embodiments, an exemplary first communication device receives a request response from a second communication device that is responsive to a transmission request from the first communication device, and a third communication At least one configured to receive a first link load weight value from the device and to make a transmitter yield determination based on the first link load weight value received from the third communication device. With one processor.
While various embodiments have been discussed in the above summary, not all embodiments include the same features, and some of the features described above may be desirable but not necessary in some embodiments. I want to be understood. Numerous additional features, embodiments, and benefits of various embodiments are discussed in the detailed description that follows.
1 is a diagram of an example peer-to-peer network, eg, an ad hoc communication network, according to an example embodiment. 2 is a flowchart of an example method of operating a first communication device, eg, a peer to peer mobile wireless terminal, in accordance with an example embodiment. 1 is a diagram of an example wireless terminal, eg, a peer to peer mobile node, according to an example embodiment. FIG. It is a figure which shows the combined state of FIG. 4A and FIG. 4B. 1 is a flowchart of an example method of operating a first communication device, eg, a peer to peer mobile wireless terminal in a peer to peer communications system. 1 is a flowchart of an example method of operating a first communication device, eg, a peer to peer mobile wireless terminal in a peer to peer communications system. 1 is a diagram of an example wireless terminal, eg, a peer to peer mobile node, according to an example embodiment. FIG. 4 is a flowchart of an exemplary method of operation of a peer-to-peer communication device, according to an exemplary embodiment. 4 is a flowchart of an example method of operating a peer-to-peer communication device, according to an example embodiment. FIG. 3 shows two example peer-to-peer wireless terminals having peer-to-peer connections and example signaling exchanged in traffic data slots of example cyclic timing and frequency structures used in a peer-to-peer network. 4 is a flowchart of an exemplary method of operation of a peer-to-peer communication device, according to an exemplary embodiment. 4 is a flowchart of an example method of operating a peer-to-peer communication device, according to an example embodiment. FIG. 3 shows two example peer-to-peer wireless terminals having peer-to-peer connections and example signaling exchanged in traffic data slots of example cyclic timing and frequency structures used in a peer-to-peer network. FIG. 5 is used to illustrate aspects of various embodiments including an exemplary outflow calculation used in transmitter concession determination based on link load weight values. 1 is a diagram of an exemplary first communication device according to an exemplary embodiment. FIG. FIG. 14 illustrates an assembly of modules that can be used in the communication device of FIG. 13. 1 is a diagram of an exemplary first communication device according to an exemplary embodiment. FIG. FIG. 16 illustrates an assembly of modules that can be used in the communication device of FIG. 15.
FIG. 1 is a diagram of an exemplary peer to peer network 100, eg, an ad hoc communication network, according to an exemplary embodiment. An exemplary network supports peer-to-peer traffic signaling by communication devices, eg, mobile wireless terminals. Exemplary network 100 supports distributed scheduling of traffic air link resources, eg, segments, per slot. In some embodiments, scheduling is based on load information corresponding to different connections that are contending to use the same traffic air link resource. Exemplary peer to peer network 100 includes a plurality of wireless devices that support peer to peer traffic signaling (peer to peer communications device 1 102, peer to peer communications device 2 104, peer to peer communications device 3 106, peer to peer communications device 4 108, ..., peer to peer communications device. N 110). In some embodiments, the network 100 includes a reference signal transmitter 116, eg, a beacon transmitter. Wireless devices (102, 104, 106, 108,..., 110) in the communication network 100 establish a connection with each other, eg, a peer-to-peer connection, and carry traffic transmission request signals, eg, link load weight values. Generate and transmit a traffic request signal carrying one or more traffic request parameters used to derive a request signal or link load weight value, receive and process the traffic transmission request signal, and receiver concession determination Generate and transmit a traffic transmission request response signal, for example, a request response signal carrying a link load weight value, receive and process the traffic transmission request response signal, make a transmitter concession decision, and receive a peer-to-peer traffic signal Peer-to-peer traffic It is possible to send the issue. There are cyclic timing structures used in the network 100. In some embodiments, the wireless device uses a reference signal, eg, an OFDM beacon signal from reference signal transmitter 116, to synchronize to the timing structure. Alternatively, the signal used to synchronize with the timing structure can be obtained from another device, eg, a GPS transmitter, base station, or another peer-to-peer device. The timing structure used in the network includes a plurality of individual traffic slots.
FIG. 2 is a flowchart 200 of an example method of operating a first communication device, eg, a peer to peer mobile wireless terminal, in accordance with an example embodiment. Operation of the exemplary method begins at step 202, where the first communication device is powered on and initialized to establish a connection with one or more peer-to-peer connections, eg, a second communication device. Establish. Operation proceeds from step 202 to step 204. Operation can sometimes proceed from step 202 to one or more of step 206 and step 208.
In step 204, the first communication device receives a transmission request from a second communication device directed to the first communication device. Operation proceeds from step 204 to step 210. In step 210, the first communication device recovers at least one parameter from the received transmission request in step 204, said at least one parameter corresponding to i) transmission queue length, ii) traffic data to be transmitted. Quality of service requirements, or iii) at least one of pre-calculated indications about the probability of successful communication over a communication link between a second communication device and the first device. The transmission queue length is information indicating the amount of data in the transmission queue corresponding to the transmission request, for example. The quality of service requirement information is, for example, information indicating data rate, latency information, and / or traffic type. Operation proceeds from step 210 to step 214.
Returning to step 206, in step 206, the first communication device may receive one or more addressed to the first communication device during a transmission request interval during which a transmission request from the second communication device was received. Receive additional send requests. Then, in step 212, the first communication device determines the number of additional transmission requests received during the request interval that are directed to the first communication device. Operation proceeds from step 212 to step 214.
Returning to step 208, in step 208, the first communication device is directed to one or more devices directed to devices other than the first communication device during a request interval during which a transmission request from the second communication device is received. Receive multiple send requests. Operation proceeds from step 208 to step 214.
In step 214, the first communication device generates a link load weight value, which is a weight to be used when making a transmission concession decision. In some embodiments, step 214 includes one or more of sub-steps 216, 218, and 220. In sub-step 216, the first communication device uses the at least one parameter restored in step 210 in combination with at least some local information to generate the link load weight value. The local information includes, for example, unused and / or used receive buffer capacity, device display capacity, and / or determined priorities of links corresponding to other devices requesting to communicate with the device. In sub-step 218, the first communication device generates a link load weight value based on the determined number of additional transmission requests directed to the first communication device. For example, a higher link load weight value is determined for a larger number of additional transmission requests received. In sub-step 220, the first communication device generates a link load weight value based on the transmission queue length and / or quality of service requirements indicated in the received additional transmission request directed to the first communication device. . For example, higher generated link load values are generated for larger queue lengths due to additional transmission requests. As another example, higher generated link load values are generated from more stringent quality of service requirements due to additional transmission requests. By using a higher link load value under such circumstances, the probability of servicing the current transmission request is increased and additional directed towards the first communication device to be serviced during subsequent data transmission intervals You can pass a send request. Operation proceeds from step 214 to step 222.
In step 222, the first communication device makes a receiver (RX) concession decision with respect to the transmission request received from the second communication device. Operation proceeds from step 222 to step 224. If the determination in step 222 is to make a concession, operation proceeds from step 224 to connecting node A 232. However, if the determination in step 222 is not to make an RX concession, operation proceeds from step 224 to step 226.
In step 226, the first communication device generates a transmission request response signal that includes the generated link load weight value. Then, in step 228, in response to the transmission request from the second communication device in step 204, the first communication device transmits a generated transmission request response including the generated link load weight value. Operation proceeds from step 228 to step 230.
In step 230, the first communication device monitors traffic signals from the second communication device in a traffic segment corresponding to the received request and the transmitted request response. Operation proceeds from step 230 to connecting node A 232. Operation proceeds from connecting node A 232 to the input of step 204, step 206, and step 208, where an operation corresponding to another data transmission interval, eg, another traffic slot in the timing structure, is performed.
FIG. 3 is a diagram of an example wireless terminal 300, eg, a peer to peer mobile node, according to an example embodiment. Wireless terminal 300 is, for example, one of the peer-to-peer communication devices of FIG. The exemplary wireless terminal 300 includes a wireless receiver module 302, a wireless transmitter module 304, a processor 306, a user input / output device 308, and a memory 310 that are coupled to each other via a bus 312. Through the bus 312, various elements can exchange data and information. In some embodiments, the wireless terminal 300 also includes a network interface 307 that is also coupled to the bus 312. When included, the network interface 307 couples the wireless terminal 300 to a network node and / or the Internet, for example, via a backhaul network. Memory 310 includes routines 318 and data / information 320.
The user input / output device 308 includes, for example, a keyboard, a keypad, a mouse, a switch, a microphone, a camera, a display, a speaker, and the like. User input / output device 308 allows an operator of wireless terminal 300 to input data / information, access output data / information, and control at least some functions of wireless terminal 300. . A processor 306, eg, a CPU, executes routine 318 and uses data / information 320 in memory 310 to control the operation of wireless terminal 300 and implement a method, eg, the method of flowchart 200 of FIG.
A wireless receiver module 302, eg, an OFDM and / or CDMA receiver, is coupled to a receive antenna 314 for wireless terminal 300 to receive signals from other wireless communication devices. Received signals include, for example, connection establishment signals, connection maintenance signals, transmission request signals that carry parameters used to derive link load weight values, and traffic segment signals. The wireless receiver module 302 can and sometimes receives a transmission request signal from a second device with which the wireless terminal 300 shares the current connection. The wireless receiver module 302 can receive additional transmission requests corresponding to other connections of which the wireless terminal 300 is a member during the same request interval in which the request signal from the second device is received, and sometimes Receive. The wireless receiver module 302 can also receive and sometimes receive transmission requests corresponding to connections for which the wireless terminal 300 is not a member during the same request interval in which a request from the second device is received.
A wireless transmitter module 304, eg, an OFDM and / or CDMA transmitter, is coupled to a transmit antenna 316 for wireless terminal 300 to transmit signals to other wireless communication devices. The transmission signal includes, for example, a connection establishment signal, a connection maintenance signal, and a transmission request response signal that carries a link load weight value. In some embodiments, the same antenna is used for the receiver and transmitter.
The routine 318 includes a communication routine 322 and a control routine 324. Communication routine 322 implements various communication protocols used by wireless terminal 300. The control routine 324 includes a first transmission request detection module 326, a link load weight value generation module 328, a transmission request response control module 330, a transmission request information restoration module 332, a local information determination module 334, and an additional request. It includes a count module 336, a second transmission request detection module 338, a receiver concession module 340, a transmission request response generation module 342, and a traffic module 344.
Data / information 320 is one of timing / frequency structure information 346, current connection information 348, a detected received transmission request 350 corresponding to the current connection, and a detected request for the current connection. Or a plurality of restored parameters (parameter (s) 356, restored from request 1,... Parameter (s) 358 restored from request M) and other Detected received transmission request 360 corresponding to the connection, determined local information 362, determined number 368 of additional requests, receiver yield determination 366, generated link load weight value 370, generated transmission A request response signal 372 and a restored traffic signal 374 are included. The detected received transmission request 350 corresponding to the current connection is a detected received transmission request (request 1 352,... In the same slot corresponding to one or more connections of which the wireless terminal 300 is a member. Request M354). Timing / frequency structure information 346 includes information corresponding to a plurality of traffic transmission slots (traffic transmission slot 1 information 376,..., Traffic transmission slot N information 378). Each traffic transmission slot information includes, for example, information identifying scheduling air link resources, such as traffic transmission request air link resources and traffic transmission request response air link resources, information identifying traffic data rate related air link resources, and traffic segments and Contains information identifying traffic acknowledgment air link resources.
The first transmission request detection module 326 detects a received transmission request corresponding to the current connection of the wireless terminal 300. For example, the first transmission request detection module 326 detects a transmission request received from a second device with which the device 300 shares the current connection. The first transmission request detection module 326 can detect and sometimes detect transmission requests corresponding to other connections of the wireless terminal 300 during a request interval during which a transmission request from the second device is received. The detected received transmission request 350 corresponding to the current connection is the output of the first transmission request detection module 326.
The link load weight value generation module 328 generates a link load weight value to be used when, for example, a device that previously transmitted a transmission request signal makes a transmission concession decision. The generated link load weight value 370 is an output of the module 328 and is used as an input by the transmission request response generation module 342 and is carried by the generated transmission request response signal 372.
The transmission request response control module 330 is configured to transmit a transmission request response signal that includes a generated link load weight value in response to a transmission request received from a device that the device 300 shares the current connection, eg, a second device. The wireless transmitter module 304 is controlled. For example, in response to a transmission request received from the second device, eg, request 1 352, the receiver concession module 340 decides not to yield, and then the transmission request response control module 330 generates the generated transmission request response signal 372. For example, controlling the wireless transmitter module 304 to transmit an RX echo signal that signifies an acknowledgment to the received request 352, and the generated transmission request response signal 372 carries a generated link load weight value 370. In some embodiments, the transmission request response control module 330, in response to a received transmission request associated with the connection, when the receiver concession module 340 decision is to confer on the request, The wireless transmitter module 304 is controlled to refrain from transmitting request response signals over request response air link resources associated with the.
The transmission request information restoration module 332 restores at least one parameter from the received transmission request, where the at least one parameter is i) a transmission queue length, ii) a quality of service requirement corresponding to traffic data to be transmitted, and iii ) One of the pre-calculated indications about the probability of successful communication on the communication link between the device that sent the request and the device to which the request was directed. The transmission queue length is a parameter indicating the amount of data in the transmission queue corresponding to the transmission request, for example. The quality of service parameter is a parameter indicating at least one of a data rate, a waiting time, and a traffic type, for example. The parameter (s) 356 restored from request 1 indicate the parameter (s) restored from request 1 352 by the transmission request information restoration module 332 and restored from request M (1 Parameter (s) 358 indicates the parameter (s) restored from request M354 by module 332. The restored parameters 356 and / or 358 are used as input by the link load weight value generation module 328.
The local information determination module 334 determines local information. The local information includes, for example, unused and / or used receive buffer capacity, device display capability, and determined priorities of links corresponding to other devices requesting to communicate with the wireless terminal 300. The determined local information is an output of the local information determination module 334 and is used as an input to the link load weight value generation module 328. In some embodiments, the link load weight value generation module 328 combines the at least one recovered parameter with at least some local information, eg, the local determined to be the recovered parameter 356 from request 1. Information 362 is used to generate a link load weight value. In this way, the generated link load weight value is based on both the transmitting device input and the receiving device input.
Additional request count module 336 determines the number of additional transmission requests received during the same request interval destined for wireless terminal 300. For example, during a traffic slot request interval, the wireless terminal 300 receives a transmission request from a second device corresponding to the first connection of the wireless terminal 300, and one or more additional wireless terminal 300 A transmission request corresponding to the connection is received, wherein the first connection has the highest priority. The additional request counting module 336 counts the number of additional received requests that are directed to the wireless terminal 300 during the same request interval to obtain a determined number 368 of additional requests. The determined number 368 of additional requests is used as input by the link load weight generation module 328. In some embodiments, the link load weight value generation module 328 generates a link load weight value based on the determined number of additional transmission requests. In one embodiment, assuming other input conditions remain constant, link load weight value generation module 328 generates a higher link load weight value for a greater number of additional transmission requests received. To do.
In some embodiments, the link load weight value generation module 328 generates a link load weight value based on the transmission queue length and quality of service requirements indicated in the received additional transmission request. In some embodiments, higher link load weight values are generated for larger queue lengths due to additional transmission requests, assuming other input conditions are constant. In some embodiments, higher link load weight values are generated for more stringent quality of service requirements due to additional transmission requirements, assuming other input conditions are constant. In some embodiments, assuming that other input conditions are constant, higher link load weight values are generated for larger queue lengths and more stringent quality of service requirements due to additional transmission requests. In some embodiments, additional requests received during the same request interval destined for wireless terminal 300 are treated as a set, and the queue length information and quality of service requirements corresponding to each received additional request are linked. Used by the load weight value generation module 328. In some embodiments, assuming that other inputs remain constant, the link load weight value generation module 328 may have a larger queue length and more stringent service communicated by additional one or more transmission requests. Generate higher generated link load weight values for quality. By increasing the link load weight value in the request response, the probability of servicing the current corresponding transmission request can be increased, sometimes increasing. Thus, additional transmission requests can be passed during subsequent data transmission intervals.
The second transmission request detection module 338 detects a received transmission request corresponding to a connection for which the wireless terminal 300 is not a member. The detected received transmission request 360 corresponding to the other connection is the output of the module 338.
The receiver concession module 340 determines the current connection based on the received transmission request corresponding to the current connection and the received higher priority transmission request corresponding to other connections that the wireless terminal 300 is not a member of. A receiver concession decision is made. For example, the receiver yield module 340 makes a receiver yield decision based on priority information corresponding to the received request and received power level information corresponding to the received request. For example, if the receiver yield module 340 allows to continue the intended traffic transmission, the receiver yield module 340 determines whether to confer the traffic transmission segment based on the estimated SINR. Receiver concession determination 366 is an output of module 340 and is used as an input by transmission request response control module 330 and / or transmission request response generation module 342.
When the wireless terminal 300 decides not to make a concession regarding the received transmission request, the transmission request response generation module 342 generates a request response signal, eg, signal 372, corresponding to that request directed to the wireless terminal 300. The transmission request response generation module 342 includes the generated link load weight value in the generated transmission request response signal. In some embodiments, the link load weight value is communicated by phase on the OFDM modulation symbol. In some embodiments, the link load weight value is communicated by phase and amplitude on the OFDM modulation symbol.
The traffic module 344 processes the received traffic signal directed to the wireless terminal 300 on the traffic segment corresponding to the generated generated transmission request response signal. The recovered traffic signal 374 is the output of the traffic module 344. The recovered traffic signal is, for example, a peer to peer traffic signal that carries image data, audio data, and / or other file data.
4 comprising the combination of FIG. 4A and FIG. 4B is a flowchart 400 of an exemplary method of operating a first communication device, eg, a peer to peer mobile wireless terminal in a peer to peer communications system. Operation of the exemplary method begins at step 402, where the first communication device is powered on and establishes a peer-to-peer connection with the second communication device. Operation proceeds from start step 402 to step 404.
In step 404, the communication device determines whether it has data to send to the second communication device. If it is determined that the first communication device has data to send to the second communication device, operation proceeds from step 404 to step 406 or step 408, depending on the particular implemented embodiment. If it is determined that the first communication device does not have traffic data to send to the second communication device, the operation is performed from the output of step 404 via connection node B 468 for a subsequent data slot. Proceed to input in step 404 for
Consider a peer-to-peer communication system utilizing an alternative A implementation of steps 406 and 410. In step 406, the first communication device may: i) transmit queue length, ii) QoS requirement corresponding to traffic data to be transmitted, or iii) communication link between the first communication device and the second communication device. Generating a link load weight value corresponding to the connection between the first communication device and the second communication device based on at least one of the pre-computed indications of the success probability of the communication above To do. The transmission queue length is information indicating the amount of data in the transmission queue corresponding to the transmission request, for example. Examples of QoS requirements are data rate, latency, and traffic type, which can be alone or in combination. Then, in step 410, the first communication device generates a transmission request that includes the generated link load weight value from step 406. Operation proceeds from step 410 to step 412.
Next, consider alternatively that the peer-to-peer communication system is utilizing the alternative B implementation of step 408. In step 408, the first communication device may: i) transmit queue length, ii) quality of service (QoS) requirements corresponding to data to be transmitted, or iii) between the first communication device and the second communication device. A transmission request is generated that includes a parameter indicating at least one of pre-calculated instructions for the probability of successful communication on the communication link. The transmission queue length is information indicating the amount of data in the transmission queue corresponding to the transmission request, for example. Examples of QoS requirements are data rate, latency, and traffic type, which can be alone or in combination. Operation proceeds from step 408 to step 412.
In step 412, the first communication device transmits the generated transmission request to the second communication device. Then, in step 414, the first communication device monitors the transmission request response signal including the link load weight value from the device. Step 414 includes sub-step 416 and sub-step 418, and may include sub-step 420. In sub-step 416, the first communication device receives a request response from the second communication device that responds to the transmission request transmitted from the first communication device in step 412. Sub-step 416 includes sub-step 417 in which the first communication device receives a link load weight value from the second communication device. In step 418, the first communication device receives a request response from the third device. Sub-step 418 includes sub-step 419 in which the first communication device receives a link load weight value from the third communication device. In step 420, the first communication device receives a request response from the Nth communication device. Sub-step 420 includes sub-step 421 in which the first communication device receives a link load weight value from the Nth communication device. Operation proceeds from step 414 to step 422.
In step 422, the first communication device restores the link load weight value. Step 422 includes sub-step 426 and may include one or more of sub-step 424 and sub-step 428. In sub-step 426, the first communication device restores the link load weight value from the request response received from the third communication device. In some embodiments, the implementation is that the link load weight value communicated in the received request of step 416 is an echo of the generated link load weight value of step 406 communicated in the corresponding transmission request. This is an implementation form. In some such embodiments, the first communication device generates a link load weight value at step 406, stores the generated link load weight value, and the stored value is available, Sub-step 404 need not be performed. In some other embodiments in which the first communication device generates a link load value in step 406 and transmits the link load weight value generated in the transmission request, the receiver that is the target of the transmission request, for example, The link load weight value can be changed based on local information, and sometimes changes. In such an embodiment, substep 424 is performed. In embodiments in which step 408 is performed, sub-step 424 is performed because the link load weight value is generated by the intended receiver device.
When sub-step 420 of step 414 is executed, sub-step 428 of step 422 is executed. In sub-step 428, the first communication device restores the link load weight value from the request response received from the Nth communication device. Operation proceeds from step 422 to step 432 via connection node A 430.
In step 432, the first communication device makes a transmitter yield determination based on the link load weight value received from the third communication device. Two alternative transmitter yielding techniques are shown. Block 434 represents a first alternative transmitter concession technique that generates an interference cost estimate based on a sum of information corresponding to multiple connections and compares the single estimate to a threshold. Block 436 represents a second alternative transmitter concession technique that determines one or more individual interference cost estimates and compares the individual cost estimates to a threshold value.
Block 434 includes steps 438, 442, 444, 446 and 448. In step 438, the first communication device is based on the link load weight value from the third communication device and the link load weight value corresponding to the connection between the first communication device and the second communication device. To generate an interference cost estimate. In some embodiments, generating the interference cost estimate includes measuring a link load weight value received from the third communication device and a channel measurement between the third communication device and the first communication device. Calculating outflow values based on the channel measurements generated from In some embodiments, step 438 may include a step where the first communication device is other link than the link between the first communication device and the second communication device, eg, other higher priority links. Based on the sub-step 440 of generating an interference cost estimate. In some such embodiments, generating the interference cost estimate generates an outflow sum corresponding to a higher priority link than the link between the first communication device and the second communication device. Including doing. In some embodiments, generating the interference cost estimate includes generating an outflow sum corresponding to another set of links, including connections where the first device has not been joined, in which the request response has been detected. Including. For example, the other set of links is a set of links other than the link between the first communication device and the second communication device where a request response signal above a minimum level is detected. Operation proceeds from step 434 to step 442. In step 442, the first communication device compares the generated interference cost estimate of step 438 with a transmitter yield threshold. Various approaches to the threshold are possible, and different approaches are used in different alternative embodiments. In some embodiments, a fixed value is used for the threshold. In some embodiments, the threshold is set based on historical data of the average data rate experienced. In various embodiments, a threshold is set based on delay information, eg, a threshold is set based on an average scheduling delay. In some embodiments, the threshold varies between a plurality of alternative fixed values, for example, cyclically changes between two fixed values.
Then, in step 444, if the comparison in step 442 determines that the generated interference cost estimate in step 438 is below the threshold, operation proceeds from step 444 to step 446, where in step 446 the first The communication device decides not to make a transmitter concession. However, if the comparison in step 442 determines that the generated interference estimate does not fall below the threshold, operation proceeds from step 444 to step 448, where the first communication device transmits the transmitter concession. Decide what to do.
Returning to block 436, block 436 includes steps 450, 454, 456, 458 and 460. In step 450, the first communication device may receive the link load weight value received from the third communication device and the link load weight value corresponding to the connection between the first communication device and the second communication device. Based on this, an interference cost estimate is generated. Block 436 can include step 452, and sometimes includes. In step 452, the first communication device each receives a received link load weight value corresponding to a higher priority link than the link between the first communication device and the second communication device; One or more additional interference cost estimates are generated based on a link load weight value corresponding to a link between the communication device and the second communication device. In this alternative TX concession approach at block 436, an individual interference cost estimate corresponding to each higher priority link than the link between the first communication device and the second communication device is determined. In some such embodiments, generating the individual interference cost estimate transmits a link load weight value received from the communication device of the other higher priority link under consideration and a link load weight value. Calculating the individual outflow value using the channel measurement generated from the channel measurement between the other higher priority link device and the first communication device.
Operation proceeds from step 450 and step 452 to step 454. In step 454, the first communication device compares each generated interference cost estimate to a transmitter yield threshold. Various approaches to the threshold are possible, and different approaches are used in different alternative embodiments. In some embodiments, a fixed value is used for the threshold. In some embodiments, the threshold is set based on historical data of the average data rate experienced. In various embodiments, a threshold is set based on delay information, eg, a threshold is set based on an average scheduling delay. In some embodiments, the threshold varies between a plurality of alternative fixed values, for example, cyclically changes between two fixed values. In some embodiments, different thresholds are used for different links.
Then, in step 456, if any of the estimates exceed the concession threshold, operation proceeds from step 456 to step 458, where the first communication device determines to make a transmitter concession. However, if none of the interference cost estimates exceed the threshold, operation proceeds from step 456 to step 460, where the first communication device determines not to make a transmitter yield.
Operation proceeds from step 432 to step 462. In step 462, the first communication device proceeds based on the transmitter yield determination in step 432. If the decision is not to make a TX concession, operation proceeds from step 462 to step 464 where the first communication device transmits traffic during the traffic interval associated with the transmitted request of step 412 and the received request response of sub-step 416. Data is transmitted to the second communication device. However, if the determination in step 432 is to make a TX concession, operation proceeds from step 462 to step 466, where the first communication device transmits traffic during the traffic interval associated with the transmitted request in step 412. Refrain from sending data to the second communication device. Operation proceeds from step 464 or step 466 via connecting node B 468 to step 404, where it is determined whether the first communication device has data to transmit to the second communication device in another traffic slot. To do.
FIG. 5 is a diagram of an example wireless terminal 500, eg, a peer to peer mobile node, according to an example embodiment. The exemplary WT 500 is, for example, one of the peer-to-peer communication devices of FIG. The exemplary wireless terminal 500 includes a wireless receiver module 502, a wireless transmitter module 504, a processor 506, a user input / output device 508, and a memory 510 that are coupled together via a bus 512. Through the bus 512, various elements can exchange data and information. In some embodiments, the wireless terminal 500 also includes a network interface 507 that is also coupled to the bus 512, which can facilitate communication with network nodes and / or the Internet. Can be coupled to the backhaul. The user input / output device 508 includes, for example, a keyboard, a keypad, a mouse, a microphone, a camera, a switch, a display, a speaker, and the like. User input / output device 508 allows the console of wireless terminal 500 to input data / information, access output data / information, and control at least some functions of wireless terminal 500. .
Memory 510 includes routines 518 and data / information 520. A processor 506, eg, a CPU, executes the routine 518 and uses the data / information 520 in the memory 510 to control the operation of the wireless terminal 500 and implement a method, eg, the method of the flowchart 400 of FIG.
Wireless receiver module 502, eg, an OFDM and / or CDMA receiver, is coupled to receive antenna 514 for wireless terminal 500 to receive signals from other wireless devices. The reception signal includes, for example, a timing synchronization signal, a connection establishment signal, a connection maintenance signal, and a transmission request response signal. The transmission request response signal carries a link load weight value. In some other embodiments, the transmission request response is communicated in a signal different from the link load weight value, but the receiver module 502 receives both signals. Accordingly, the wireless receiver module 502 receives a signal carrying a request response and a link load weight value.
A wireless transmitter module 504, eg, an OFDM and / or CDMA transmitter, is coupled to a transmit antenna 516 for wireless terminal 500 to transmit signals to other wireless devices. The transmission signals include, for example, a connection establishment signal, a connection maintenance signal, a transmission request signal, and a peer to peer traffic signal. In some embodiments, the same antenna is used for the receiver and transmitter.
The routine 518 includes a communication routine 522 and a control routine 524. Communication routine 522 implements various communication protocols used by wireless terminal 500. The control routine 524 includes a request response detection module 528, a link load weight value restoration module 530, a transmitter concession module 532, a transmission request generation module 544, a priority module 546, a transmission request control module 548, and a traffic module. 550. In some embodiments, the control routine 524 also includes a link load weight value generation module 526. The transmitter yield module 532 includes an interference cost estimation module 534 and a threshold comparison submodule 542. The interference cost estimation module 534 includes a channel measurement submodule 536. In some embodiments, eg, an embodiment that implements the first alternative TX concession technique of block 434 of flowchart 400 in FIG. 4, interference cost estimation module 534 includes a total base outflow determination sub-module 538. In some embodiments, eg, an embodiment that implements the second alternative TX concession technique of block 436 of flowchart 400 of FIG. 4, interference cost estimation module 534 includes an individual base outflow determination sub-module 540.
Data / information 520 detected timing / frequency structure information 520, transmission queue length information 558, quality of service (QoS) information 560, communication probability information 562, connection information 564, and generation transmission request 568. Received transmission request response 570, restored link load weight value 572, channel measurement information 574, threshold information 582, comparison result information 584, transmitter (TX) concession decision 586, and generated traffic signal 588. In some embodiments, the wireless terminal 500 generates a link load weight value corresponding to a member link, for example, as part of transmission request signal generation. In such an embodiment, data / information 520 includes generated link load weight value 566. In some embodiments, eg, one embodiment that implements the first alternative TX concession technique of block 434 of flowchart 400 in FIG. 4, data / information 520 includes a determined total outflow value 576. In some embodiments, eg, one embodiment that implements the second alternative TX concession technique of block 436 of the flowchart 400 of FIG. 4, the data / information 520 is the individual link decision spill value (first other link). , Etc., one or more of the decision spill values 580) for the Nth other link.
Timing frequency structure information 552 includes information (traffic slot 1 information 554,..., Traffic slot N information 556) corresponding to a plurality of traffic transmission slots in a cyclic peer-to-peer timing structure. Traffic transmission slot 1 information 554 identifies air link resources used for peer-to-peer traffic scheduling, including, for example, air link resources for carrying transmission requests and air link resources for carrying request response signals. And information identifying the air link resources of the traffic segment. The connection information 564 includes information identifying the current connection of the wireless terminal 500 and air link resources in the timing / frequency structure associated with the connection identifier, eg, segments, eg, specific traffic transmission request air link resources, and wireless terminals Information identifying a particular transmission request response air link resource associated with the connection identifier currently held by the device 500. In some embodiments, the resources associated with a particular connection identifier vary for each traffic transmission slot in the timing / frequency structure, eg, according to a hopping sequence.
The request response detection module 528 detects the received request response signal including the request response received from the second device that responds to the transmission request from the wireless terminal 500.
The link load weight value restoration module 530 restores the link load weight value from the received signal including the link load weight value from the received signal from the third communication device. In some embodiments, the link load weight value is communicated in the request response signal. In some embodiments, the link load weight value from the third communication device is received, for example, in a transmission request response corresponding to a link for which device 500 is not a member. In some embodiments, eg, one embodiment that does not use the link load weight value generation module 526, the link load weight value restoration module 530 may also link from a second device corresponding to a connection of which the device 500 is a member. Restore the load weight value. In some embodiments in which the link load weight value generation module 526 is used, a device that generates a request response to a received transmission request may change the received link load weight value based on, for example, local information; An opportunity to communicate the changed link load weight value in the request response signal. In one such embodiment, the link load weight value restoration module 530 also restores the link load weight value from the second device corresponding to the connection of which the device 500 is a member. The restored link load weight value 572 is information obtained by the restoration module 530 that is used as input by the interference cost estimation module 534, the total base outflow determination submodule 538, and / or the individual link base outflow determination submodule 540. including.
The transmitter yield module 532 makes a transmitter yield decision based on the link load weight value received from the third communication device. Transmitter yield determination 586 is an output of transmitter yield module 532 and is used as an input to traffic module 550. A decision to perform a transmitter concession is a decision not to continue the intended traffic transmission in that traffic slot, and a decision not to perform a transmitter concession is a decision to continue the intended traffic transmission in that traffic slot.
The link load weight value generation module 526 includes i) a transmission queue length, ii) a quality of service requirement corresponding to the transmission request, and iii) a successful communication on the communication link between the second device and the wireless terminal 500. A link load weight value is generated from at least one of the pre-calculated instructions for the probability. In embodiments using the link load weight value generation module 526, transmission queue length information 558, eg, information indicating the amount of data in the transmission queue of the wireless terminal 500 corresponding to the transmission request, QoS information 560, eg, data rate, Latency information and / or information indicating traffic type, and communication probability information 562, for example, a pre-calculated probability of successful communication over the communication link between the wireless terminal 500 and the second communication device The information is an input to the link load weight value generation module 526. The generated link load weight value 566 is an output of the link load weight value generation module 526 and an input to the transmission request generation module 544 in the embodiment using the link load weight value generation module 526. In an alternative embodiment that does not use link load weight value generation module 526, transmission queue length 558, QoS information 560, and communication probability information 562 are inputs to transmission request generation module 544.
The transmission request generation module 544 generates a transmission request, for example, a generation transmission request 568. In some embodiments, eg, embodiments that use link load weight value generation module 526, transmission request generation module 544 generates a transmission request that includes a generated link load weight value, eg, value 566. In some embodiments, eg, embodiments that do not include the link load weight value generation module 526, the generate transmission request is another device, eg, the intended receiver of the transmission request, for generating the link load weight value. Contains parameters that are intended to be used by. In some such embodiments, the transmission request generation module 544 generates a transmission request that includes one or more parameters indicating one or more of transmission queue length information 558, QoS information 560, and communication probability information 562. Generate. The generation transmission request 568 is an output of the module 544 and an input to the transmission request control module 548.
The transmission request control module 548 can transmit the generated transmission request to the second device using, for example, an air link resource associated with the connection between the wireless terminal 500 and the second device. The module 504 is controlled.
The interference cost estimation module 534 determines the interference cost estimate based on the link load weight value received from the third communication device and the link load weight value corresponding to the connection between the wireless terminal 500 and the second communication device. Is generated. In some embodiments, the interference cost estimate is based on one or more outflow decisions. In some embodiments, the interference cost estimate is measured channel state information, eg, (i) measured between the second device corresponding to the current connection of the wireless terminal 500 and the wireless terminal 500. Between the third device and the wireless terminal 500, corresponding to the received detected transmission request response of the channel, and (ii) a higher priority link between the two devices that the wireless terminal 500 is not a member of Based on measured channel.
The threshold comparison submodule 542 compares the interference cost estimate 534 with the threshold limit in the threshold information 582. In some embodiments, eg, one embodiment that uses a sum-based outflow technique, the threshold comparison submodule 542 performs a single comparison that is used to determine a transmitter concession decision. In some other embodiments, eg, one embodiment that uses an individual link-based outflow determination technique, the threshold comparison sub-module 542 performs one or more comparisons for each link where interference effects are considered. For example, the comparison is performed once for each higher priority link in which a request response exceeding a predetermined level is detected. The comparison result 584 is the output of the threshold comparison submodule 542 and is used when making a concession decision by the transmitter concession module 532.
Various approaches to the threshold are possible, and different approaches are used in different alternative embodiments. In some embodiments, a fixed value is used for the threshold. In some embodiments, the threshold is set based on historical data of the average data rate experienced. In various embodiments, a threshold is set based on delay information, eg, a threshold is set based on an average scheduling delay. In some embodiments, the threshold varies between a plurality of alternative fixed values, for example, cyclically changes between two fixed values.
Priority module 546 determines relative priorities associated with different connections for traffic transmission slots. In some embodiments, the priority associated with a particular connection identifier varies for each traffic transmission slot based on hopping information. In some embodiments, a transmission request response corresponding to a higher priority link than the link of wireless terminal 500 is used in performing the transmitter concession decision, and lower priority links are not considered. .
When the transmitter concession module 532 decision is not to make a TX concession, the traffic module 550 generates a peer-to-peer traffic signal and generates it in the traffic segment of the traffic slot associated with the transmitted request sent and the corresponding request response received. The wireless transmitter module 504 is controlled to transmit the generated peer-to-peer traffic signal. Generated traffic signal 588, for example, a signal carrying user data such as image data, voice data and / or file data, is the output of traffic module 550.
Channel measurement sub-module 536 measures the channel between device 500 and other devices. The channel measurement submodule 536 measures the channel gain between the wireless terminal 500 and a second device with which the wireless terminal shares the current connection and to which the wireless terminal 500 has transmitted a transmission request. The channel measurement sub-module 536 also measures the channel gain between the wireless terminal 500 and a device that has transmitted a request response signal detected by the wireless terminal 500, eg, a request response signal intended for another wireless terminal. . Channel measurement information 574 is the output of channel measurement submodule 536 and is used as an input by total base outflow determination submodule 538 and individual link base outflow determination submodule 540.
The sum base outflow determination sub-module 538 generates outflows based on the link load weight values received from the third device and the channel measurements generated from the channel measurements between the third device and the wireless terminal 500. Determine the value. In some embodiments, the total base outflow determination submodule 538 detects a request response for other links where a request response was detected, including connections for which the first device has not joined, eg, the same traffic transmission slot. Generating an outflow sum corresponding to each of the other set of links that has been made. For example, the total outflow value is based on a plurality of link load weight values and a plurality of channel measurements. In some embodiments, the sum base outflow determination sub-module 538 generates an outflow sum corresponding to a higher priority link than, for example, a link between the wireless terminal 500 and the second communication device, eg, Lower priority links are not considered in the total outflow decision. In one embodiment, the interference cost estimate is the outflow sum value divided by the link load weight value corresponding to the link between the wireless terminal 500 and the second communication device. The determined total outflow value 576 is an output of the total base outflow determination submodule 538 and is an input to the threshold comparison submodule 542.
Individual link-based outflow determination submodule 540 determines an individual outflow determination corresponding to each of one or more received request response signals corresponding to links for which wireless terminal 500 is not a member. For example, the individual link-based outflow determination submodule 538 can convert the link load weight value received from the third device and the channel measurement generated from the measurement of the channel between the third device and the wireless terminal 500. A first outflow value is determined based on the link load weight value received from the fourth device and a measurement value of the channel between the fourth device and the wireless terminal 500; A second outflow value is determined based on the channel measurement value generated from. In one embodiment, the interference cost estimate is a value obtained by dividing the individual link base outflow value by the link load weight value corresponding to the link between the wireless terminal 500 and the second communication device. The decision outflow value 578 for the first other link is the output of the individual link base outflow decision submodule 540 and is the input to the threshold comparison submodule 542. Similarly, the decision outflow value 580 for the Nth other link is the output of the individual link base outflow decision submodule 540 and the input to the threshold comparison submodule 542.
FIG. 6 is a flowchart 600 of an exemplary method of operation of a peer to peer communications device, in accordance with an exemplary embodiment. Operation starts in step 602, where the communication device is powered on and initialized. In step 602, the peer to peer communications device establishes a connection with the other peer to peer communications device corresponding to a first link between the peer to peer communications device implementing the method and another peer to peer communications device.
Operation proceeds from step 602 to step 604. In step 604, the peer to peer communications device calculates a link load weight value for the first link, eg, a first link load value L 1 [t] 630. In various embodiments, the link load weight value is: i) a transmission queue length indicating the amount of data in the transmission queue corresponding to the transmission request, for example, ii) a quality of service requirement corresponding to the traffic data to be transmitted, eg data Rate, latency, traffic, traffic type, etc., and iii) of pre-computed indications about the probability of successful communication over the communication link between the peer-to-peer communication device and the device to which the traffic transmission request is directed It is generated from at least one. Then, in step 606, the peer to peer communications device generates a traffic transmission request that includes the calculated link load weight value. Operation proceeds from step 606 to step 607, in which the communications device transmits a generated traffic transmission request that carries the calculated link load weight value. In one embodiment, the calculated link load value is represented as a bit, which is carried by the traffic transmission request signal phase information.
In an alternative embodiment, different signals are generated and the generated signals are transmitted to carry the calculated link load weight value and traffic transmission request.
Operation proceeds from step 607 to step 608 and step 610. In step 608, the communication device monitors a traffic transmission request response signal corresponding to a previously transmitted traffic transmission request that requests transmission of a traffic signal in a current traffic slot corresponding to the first link. From time to time, sub-step 612 is performed where the communication device detects a signal indicating an acknowledgment to a transmitted traffic transmission request for the first link, for example, the communication device indicates an acknowledgment to the traffic transmission request; Detect and receive RX echo signals from the device to which the request was sent.
In step 610, the communication device monitors signals communicating link load values corresponding to different links. In some embodiments, the link load value is carried in the traffic transmission request response signal. From time to time, sub-step 614 is performed where the communications device detects one or more signals each communicating a link load weight value corresponding to a different link. Link load value L 2 [t] 632 and link load value L N [t] 634 are exemplary outputs from sub-step 614.
Operation proceeds from step 608 to step 616. In step 616, the communication device proceeds based on whether an affirmative request response signal in response to a previously transmitted transmission request signal in step 607 has been detected. If the communication device detects an acknowledgment signal, operation proceeds from step 616 to step 618; otherwise, operation proceeds from step 616 to connecting node A 628.
In step 618, the communication device calculates an outflow value for the first link based on signals detected from different links and link priority information. In certain embodiments, the communication device selectively uses information corresponding to a higher priority link than the first link in calculating an outflow value for the first link. For example, the channel gain between the communication device and the communication device with the higher priority link that transmitted the request response signal is higher than the higher priority to calculate the outflow value for the first link. Used in combination with the communicated link load weight value corresponding to the link. The outflow value S 1 [t] 636 is the output of step 618.
Operation proceeds from step 618 to step 620, in which the communication device determines the first link based on the link load weight value for the first link, the outflow value for the first link, and (630, 636). A weighted signal to interference noise ratio (SINR) is calculated. In one embodiment, SINR 1 = L 1 [t] / S 1 [t]. Operation proceeds from step 620 to step 622. In step 622, the communications device determines whether the calculated weighted SINR value of step 620 is less than a first link transmitter yield threshold. If the calculated weighted SINR is less than the concession threshold (β 1 ), operation proceeds from step 622 to step 624 where the communication device performs a transmitter concession and transmits a traffic signal in the traffic slot. Refrain. However, if the calculated SINR is greater than or equal to the first transmitter yield threshold, operation proceeds from step 622 to step 626, where the communication device transmits a traffic signal in the traffic slot. Operation proceeds from step 624 or step 626 to connecting node A 628 and from connecting node A 628 to the input of step 604, where the communications device calculates a link load value for the first link for another traffic slot. .
In some alternative embodiments, individual outflow values corresponding to individual pairs of links are calculated, where one pair is a first link and another link, eg, (first link, second link), (first 1 link, Nth link), where the second link and the Nth link correspond to links having a higher priority than the first link. In one such embodiment, an individual weighted signal to interference noise ratio is calculated for each pair and individually compared to a concession threshold. In some such embodiments, if any one comparison test indicates that a TX concession should be made, the TX concession is performed.
In some embodiments, an interference cost estimate is determined based on the outflow value, for example, the interference cost estimate is the inverse of the calculated weighted signal to interference noise ratio. In some such embodiments, transmitter concession determination is performed based on a comparison of the interference cost estimate with a threshold, eg, transmitter concession is performed when the interference cost estimate exceeds the threshold. Is done.
FIG. 7 is a flowchart 700 of an exemplary method of operating a peer to peer communications device, in accordance with an exemplary embodiment. Operation of the exemplary method begins at step 702, where the communication device is powered on and initialized. In step 702, the communication device establishes a peer-to-peer connection with another peer-to-peer communication device corresponding to the first link. Operation proceeds from step 702 to step 704.
In step 704, the communication device monitors the traffic transmission request signal. Sometimes steps 706 and / or 708 are performed as part of step 704. In sub-step 708, the communication device receives a traffic transmission request from another communication device that shares the connection that it wants to transmit traffic to the communication device via the first communication link. In sub-step 706, the communication device receives a traffic transmission request signal corresponding to the additional link.
Depending on the implementation, operation proceeds from sub-step 706 to sub-step 710 or sub-step 712. If the link load value is carried in the traffic transmission request signal, alternative A is used and operation proceeds from sub-step 706 to step 710. However, if the link load value is communicated in a signal unrelated to the traffic transmission request signal, alternative B is used and operation proceeds from sub-step 706 to step 712.
In step 710, the communication device restores the link load value for the first link communicated in the traffic transmission request signal received in sub-step 706. Operation proceeds from step 710 to step 716.
In step 712, the communication device receives a link load signal communicating the link load value for the first link from the other communication device. Then, in step 714, the communication device restores the link load value for the first link communicated in the received link load signal. Operation proceeds from step 714 to step 716.
In step 716, the communication device makes a receiver yield decision based on the received traffic transmission request signal power and link priority information. For example, the communication device may switch to a higher priority link based on the received power of the traffic transmission request signal corresponding to the higher priority link and the received power of the traffic transmission request signal corresponding to the first link. Consider whether to make a concession. Note that in this embodiment, when making a receiver yield decision, link load value information is not used in the receiver yield.
Operation proceeds from step 716 to step 718. In step 718, the communication device proceeds based on the receiver yield determination in step 716. If the determination in step 716 is to perform a receiver yield, operation proceeds from step 718 to connecting node A 728. However, if the determination in step 718 is not to perform a receiver yield, operation proceeds from step 718 to step 720 or step 722, depending on the implementation. If the transmission request response signal is an implementation that carries a link load value, alternative C is used and operation proceeds from step 718 to step 720. If the implementation is such that the link load value is communicated independently of the transmission request response signal, operation proceeds from step 718 to step 722.
Returning to step 720, in step 720, the communications device communicates an acknowledgment to the transmission request of sub-step 706 and generates a transmission request response signal that echoes the received first link load value. Operation proceeds from step 720 to step 726.
Returning to step 722, in step 722, the communications device generates a transmission request response signal that communicates an acknowledgment to the transmission request. Operation proceeds from step 722 to step 724. In step 724, the communication device generates a signal that echoes the received first link load signal. Operation proceeds from step 724 to step 726.
In step 726, the communication device transmits the generated signal or signal of step 720 or of steps 722 and 724. Operation proceeds from step 726 to connecting node A 728. Operation proceeds from connecting node A 728 to the input of step 704, where the communications device monitors a traffic transmission request signal corresponding to another traffic slot.
In an alternative embodiment, the communication device optionally modifies the received link load weight value corresponding to the first link based on local information, rather than simply echoing the received link load weight value. Local information includes, for example, receiver information such as receiver buffer capacity, current receiver buffer status such as amount of used and / or unused buffer capacity, device display function, other requesting communication with communication device, etc. And the number of other links on which a request to communicate with the communication device has been detected. Thus, in some embodiments, the received link load weight value for the first link may be different and sometimes different from the transmitted link load weight value.
FIG. 8 is an example exchanged with two example peer-to-peer wireless terminals (WT A 802, WT B 804) having peer-to-peer connections in an example cyclic timing and frequency structure traffic data slot used in a peer-to-peer network. (800) is a diagram illustrating the signaling. A WT (802, 804) is a wireless terminal that implements the method described in one or more of FIGS. 6 and 7, for example. FIG. 8 (800) also includes a time axis 801. WT A 802 generates a traffic transmission request signal (TX RQST) 806 requesting transmission of a traffic signal to WT B 804 in the traffic slot, and transmits the traffic transmission request signal (TX RQST) 806 to WT B 804. In some embodiments, the traffic transmission request signal 806 also carries a link load weight value 856 corresponding to the link between WT A 802 and WT B 804. In some embodiments, the link load weight value 856 is communicated by the phase information of the traffic transmission request signal 806.
The wireless terminal B 804 receives the traffic transmission request signal 806. Wireless terminal B 804 may correspond to other connections between various pairs of wireless terminals that may attempt to communicate traffic signals concurrently with, for example, intended WT A traffic signaling and / or other with WT B 804 A traffic transmission request signal corresponding to the connection can also be received. WT C outgoing traffic transmission request signal 858 and WT E outgoing traffic transmission request signal 860 represent such signals. The WT B 804 monitors and detects traffic transmission request signals corresponding to other links. WT B 804 has a receiver yield opportunity indicated by block 807. WT B 804 makes a receiver yield decision based on the power of the received traffic transmission signal 806 and the received traffic transmission signal corresponding to a higher priority connection than its own connection under consideration. If WT B 804 determines that interference from a higher priority connection is expected to unacceptably affect the restoration of the traffic signal from WT A 802 by WT B 804, then WT B 804 decides to make a concession; Do not send request response signals. However, if WT B 804 decides not to yield, it generates a traffic transmission request response signal (RX echo) 808 and transmits it to WT A 804. In some embodiments, WT B 804 includes the link load weight value 856 received from WT A 804 in the received traffic transmission request response signal 808 using, for example, phase information. In some other embodiments, WT B 804 may, for example, receiver unused and / or used buffer capacity, device indication capability, number of additional received requests corresponding to other links with WT B, etc. Based on the local information, the link load weight value in the received traffic transmission request 806 can be modified, sometimes modified, and the modified link load weight value, if transmitted, the traffic transmission request response signal 808 Conveyed in.
WT A 802 receives a traffic transmission request response signal 808 from WT B 804 and possibly receives a traffic transmission request response signal from another connection. Request response signal 862 supplied from WT D and request response signal 864 supplied from WT F are examples of request response signals corresponding to other connections. In this embodiment, each traffic transmission request response signal carries a link load weight value corresponding to the link. WT A 802 measures the power of the received signal and restores the link load weight value corresponding to the other link. WT A 802 also restores the link load value corresponding to the link of WT A 802 with WT B if WT B can modify the transmitted link load value. The WT A 802 measures the channel between itself and each of the detected traffic transmission request response signal sources. WT A 802 has a transmitter concession opportunity, indicated by block 809, the received power of the transmission request response signal corresponding to the link of WT A 802 itself, and the received power of the transmission request response signal corresponding to the higher priority link. The link load value corresponding to the link of WT A 802 itself, the link load value corresponding to the higher priority link, the channel between WT A 802 itself and WT B, and the higher priority of WT A 802 itself. Transmitter concession decisions are made based on the channels with each of the other sources of the detected request response signal corresponding to the link. The transmitter yield decision is made based on the amount of interference that WT A 802 is expected to bring to other higher priority connections.
If WT A 802 decides to make a concession, it refrains from transmitting a pilot signal in this traffic slot and does not transmit a traffic signal in this traffic slot. If WT A 802 decides not to make a concession, it sends a pilot signal 810 to WT B 804. WT B 804 then receives the pilot signal and estimates the channel condition, eg, indicating the maximum supported data rate or commanded data rate or the requested data rate to be used for the traffic signal in this traffic slot. A rate information signal 812 is generated and transmitted.
WT A 802 receives rate information signal 812, determines the data rate to use for the traffic signal, generates peer to peer traffic signal 814, and sends it to WT B 804. When the WT B 804 receives the traffic signal 814 and the traffic information restoration is successful, the WT B 804 generates a traffic acknowledgment signal 816 and transmits it to the WT A 802.
Note that in this embodiment, traffic scheduling is performed in a distributed manner for each traffic slot. In this embodiment, the link load weight value is also determined for each slot and communicated. In some embodiments, criteria used for transmitter concessions, such as SINR comparison limits, may change over time and will change from time to time.
FIG. 9 is a flowchart 900 of an exemplary method of operation of a peer to peer communications device, in accordance with an exemplary embodiment. Operation starts in step 902, where the communication device is powered on and initialized. In step 902, a peer to peer communications device establishes a connection with the other peer to peer communications device corresponding to a first link between the peer to peer communications device implementing the method and another peer to peer communications device.
Operation proceeds from step 902 to step 904. In step 904, the peer to peer communications device classifies the incoming traffic and sets one or more traffic request parameters based on the classification information, eg, transmission queue length information, quality of service information, communication success probability information. The transmission queue length is information indicating the amount of data in one or more transmission queues corresponding to a transmission request, for example. The quality of service requirement information corresponding to the traffic data to be transmitted is information indicating, for example, data rate, latency, and / or traffic type information. The communication success probability information is, for example, a pre-calculated instruction about the probability of successful communication on the communication link between the communication device and the communication device to which the traffic transmission request should be directed. In one embodiment, information indicating a certain traffic request parameter or a combination of a plurality of traffic request parameters is represented as bits, and the bits are carried by the phase information of the traffic transmission request signal. Parameter set information 930 including parameters P 1, P 2, P 3 is an exemplary output of step 904.
Operation proceeds from step 904 to step 906, where the communications device generates a traffic transmission request that includes one or more traffic request parameters. Then, in step 907, the communication device transmits the generated traffic transmission request that carries one or more traffic request parameters.
Operation proceeds from step 907 to step 908 and step 910. In step 908, the communications device monitors a traffic transmission request response signal corresponding to a previously transmitted traffic transmission request requesting transmission of a traffic signal in the current traffic slot. Sometimes sub-step 912 is performed and the communication device detects a signal indicating an acknowledgment to the transmitted traffic transmission request for the first link, eg, the communication device indicates an acknowledgment to the traffic transmission request. Detect and receive an RX echo signal from the device to which the request was sent, and the received signal also communicates a link load weight value corresponding to the first link. Therefore, the link load weight value L 1 [t] 931 is restored.
In step 910, the communication device monitors signals communicating link load weight values corresponding to different links. In some embodiments, the link load value is carried in the traffic transmission request response signal. From time to time, sub-step 914 is performed where the communication device detects one or more signals each communicating a link load weight value corresponding to a different link. Link load value L 2 [t] 932 and link load value L N [t] 934 are exemplary outputs from substep 914.
Operation proceeds from step 908 to step 916. In step 916, the communication device proceeds based on whether it detected an affirmative request response signal in response to the previously transmitted transmission request signal in step 907. If the communication device detects an acknowledgment signal, operation proceeds from step 916 to step 918; otherwise, operation proceeds from step 916 to connecting node A 928.
In step 918, the communication device calculates an outflow value for the first link based on the signals detected from the different links and the link priority information. In certain embodiments, the communication device selectively uses information corresponding to a higher priority link than the first link in calculating an outflow value for the first link. For example, the channel gain between the communication device and the communication device with the higher priority link that transmitted the request response signal is higher than the higher priority to calculate the outflow value for the first link. Used in combination with the communicated link load weight value corresponding to the link. The outflow value S 1 [t] 936 is the output of step 918.
Operation proceeds from step 918 to step 920 in which the communication device determines that the first link is based on the link load weight value for the first link and the outflow value for the first link (931, 936). A weighted signal to interference ratio (SINR) is calculated. In one embodiment, SINR 1 = L 1 [t] / S 1 [t]. Operation proceeds from step 920 to step 922. In step 922, the communications device determines whether the calculated weighted SINR value of step 920 is less than a first link transmitter yield threshold. If the calculated weighted SINR is less than the concession threshold (β 1 ), operation proceeds from step 922 to step 924 where the communication device performs a transmitter concession and transmits a traffic signal in the traffic slot. Refrain. However, if the calculated weighted SINR is greater than or equal to the first transmitter yield threshold, operation proceeds from step 922 to step 926 where the communication device transmits a traffic signal in the traffic slot. Operation proceeds from step 924 or step 926 to connecting node A 928 and from connecting node A 928 to the input of step 904, where the communication device calculates a link load value for the first link for another traffic slot. .
FIG. 10 is a flowchart 1000 of an example method of operating a peer to peer communications device, according to an example embodiment. Operation of the exemplary method begins at step 1002, where the communication device is powered on and initialized. In step 1002, the communication device establishes a peer-to-peer connection with another peer-to-peer communication device corresponding to the first link. Operation proceeds from step 1002 to step 1004.
In step 1004, the communication device monitors the traffic transmission request signal. Sometimes steps 1006 and / or 1008 are performed as part of step 1004. In sub-step 1006, the communication device receives a traffic transmission request that it wants to transmit traffic to the communication device via the first communication link from another communication device that shares the connection. In sub-step 1006, the communication device receives a traffic transmission request signal corresponding to the additional link.
Depending on the implementation, operation proceeds from sub-step 1006 to sub-step 1010 or sub-step 1012. If the traffic request parameter is carried in the traffic transmission request signal, alternative A is used and operation proceeds from sub-step 1006 to step 1010. However, if the traffic request parameter is communicated in a signal unrelated to the traffic transmission request signal, alternative B is used and operation proceeds from sub-step 1006 to step 1012.
In step 1010, the communication device recovers one or more traffic request parameters for the first link communicated in the traffic transmission request signal received in sub-step 1006. Exemplary traffic request parameters include a transmission queue length parameter that indicates the amount of data in the transmission queue that corresponds to the transmission request, and a quality of service requirement that indicates, for example, one or more of data rate, latency, and traffic type. And a communication success probability information parameter indicating a pre-calculated instruction for the probability of successful communication on the link. Operation proceeds from step 1010 to step 1016.
In step 1012, the communication device sends a signal communicating one or more traffic request parameters for the first link from the another communication device, eg, a queue length parameter, a QoS information parameter, a communication success parameter, and the like. Receive. Then, in step 1014, the communication device restores one or more traffic request parameters that are being communicated in the received link load signal of step 1012. Operation proceeds from step 1014 to step 1016.
In step 1016, the communication device makes a receiver yield decision based on the received traffic transmission request signal power and link priority information. For example, the communication device may switch to a higher priority link based on the received power of the traffic transmission request signal corresponding to the higher priority link and the received power of the traffic transmission request signal corresponding to the first link. Consider whether to make a concession. Note that in this embodiment, when making a receiver yield decision, no link load weight value is used in the receiver yield. In some other embodiments, link load weight values and / or recovered traffic request parameters are used in receiver yield determination.
Operation proceeds from step 1016 to step 1018. In step 1018, the communication device proceeds based on the receiver yield decision in step 1016. If the determination in step 1016 is to perform a receiver yield, operation proceeds from step 1018 to connecting node A 1028. However, if the determination in step 1018 is not to perform a receiver yield, operation proceeds from step 1018 to step 1019.
In step 1019, the communications device generates a link load weight value based on the restored one or more traffic request parameters and local information. Local information includes, for example, receiver information such as receiver buffer capacity, current receiver buffer status such as amount of used and / or unused buffer capacity, device display function, other requesting communication with communication device, etc. And the number of other links on which a request to communicate with the communication device has been detected.
Operation proceeds from sub-step 1019 to step 1020 or step 1022, depending on the implementation. If the transmission request response signal is an implementation that carries a link load value, alternative C is used and operation proceeds from step 1018 to step 1020. If the implementation is such that the link load value is communicated independently of the transmission request response signal, operation proceeds from step 1018 to step 1022.
Returning to step 1020, in step 1020, the communication device communicates an acknowledgment to the transmission request of sub-step 1006 and generates a transmission request response signal that communicates the generated link load weight value. Operation proceeds from step 1020 to step 1026.
Returning to step 1022, in step 1022, the communications device generates a transmission request response signal that communicates an acknowledgment to the transmission request. Operation proceeds from step 1022 to step 1024. In step 1024, the communication device generates a signal that communicates the generated link load weight value. Operation proceeds from step 1024 to step 1026.
In step 1026, the communication device transmits the generated signal of step 1020 or the signals of steps 1022 and 1024. Operation proceeds from step 1026 to connecting node A 1028. Operation proceeds from connecting node A 1028 to the input of step 1004, where the communications device monitors a traffic transmission request signal corresponding to another traffic slot.
FIG. 11 is an example exchanged with two example peer-to-peer wireless terminals (WT A 1102, WT B 1104) having peer-to-peer connections in an example cyclic timing and frequency structure traffic data slot used in a peer-to-peer network. 1100 is a diagram illustrating active signaling. WT 1102 and WT 1104 are exemplary WTs that implement one or more methods described in one or more of FIGS. 9 and 10, for example. 1100 also includes a time axis 1101. WT A 1102 generates a traffic transmission request signal (TX RQST) 1106 that requests transmission of a traffic signal to WT B 1104 in the traffic slot, and transmits the traffic transmission request signal (TX RQST) 1106 to WT B 1104. In some embodiments, the traffic transmission request signal 1106 also includes a traffic request parameter, eg, a transmission queue length parameter indicating the amount of data in one or more transmission queues corresponding to the transmission request, eg, data rate, wait Between WT A 1102 and WT B 1104 corresponding to a QoS parameter corresponding to the traffic data to be transmitted and / or a link between WT A 1102 and WT B 1104 indicating at least one of time and traffic type Carries a traffic communication success probability information parameter indicating a pre-calculated indication of the probability of successful communication over the communication link. In some embodiments, the traffic request parameter (s) 1156 is communicated by the phase information of the traffic transmission request signal 1106.
The wireless terminal B 1104 receives the traffic transmission request signal 1106. Wireless terminal B 1104 may correspond, for example, to other connections between various pairs of wireless terminals that may attempt to communicate traffic signals concurrently with intended WT A traffic signaling and / or other with WT B 1104 A traffic transmission request signal corresponding to the connection can also be received. WT C originated traffic transmission request signal 1159 and WT E originated traffic transmission request signal 1160 represent such signals. The WT B 1104 monitors and detects traffic transmission request signals corresponding to other links. WT B 1104 has a receiver yield opportunity indicated by block 1107. WT B 1104 makes a receiver concession decision based on the power of the received traffic transmission signal 1106 and the received traffic transmission signal corresponding to a higher priority connection than its own connection under consideration. If WT B 1104 determines that interference from a higher priority connection is expected to unacceptably affect the restoration of the traffic signal from WT A 1102 by WT B 1104, it decides to make a concession; Do not send request response signals. However, if WT B 1104 decides not to yield, it generates a traffic transmission request response signal (RX echo) 1108 and transmits it to WT A 1102. WT B 1104 may receive additional traffic request parameter (s) 1156 and corresponding to, for example, receiver unused and / or used buffer capacity, device indication capabilities, and other links with WT B. A link load weight value 1158 is generated based on the local information such as the number of received requests. The generated link load weight value 1158 is carried in the traffic transmission request response signal 1108.
WT A 1102 receives a traffic transmission request response signal 1108 from WT B 1104 and possibly receives a traffic transmission request response signal from another connection. Request response signal 1162 supplied from WT D and request response signal 1164 supplied from WT F are examples of request response signals corresponding to other connections. In this embodiment, each traffic transmission request response signal carries a link load weight value corresponding to the link. WT A 1102 measures the power of the received signal and restores the link load weight value corresponding to each of the links. The WT A 1102 measures the channel between itself and each of the detected traffic transmission request response signal sources. WT A 1102 has a transmitter concession opportunity as indicated by block 1109, the received power of the transmission request response signal corresponding to the link of WT A 1102 itself, and the received power of the transmission request response signal corresponding to the higher priority link. A link load value corresponding to the link of WT A 1102 itself, a link load value corresponding to a higher priority link, a channel between WT A 1102 itself and WT B, and a higher priority of WT A 1102 itself. Transmitter concession decisions are made based on the channels with each of the other sources of the detected request response signal corresponding to the link. A transmitter concession decision is made based on the amount of interference that WT A 1102 is expected to bring to other higher priority connections.
If WT A 1102 decides to make a concession, it refrains from transmitting a pilot signal in this traffic slot and does not transmit a traffic signal in this traffic slot. If WT A 1102 decides not to make a concession, it sends a pilot signal 1110 to WT B 1104. WT B 1104 then receives the pilot signal, estimates the channel condition, and indicates, for example, the maximum supported data rate or commanded data rate or the requested data rate to be used for the traffic signal in this traffic slot. A rate information signal 1112 is generated and transmitted.
WT A 1102 receives rate information signal 1112, determines the data rate to use for the traffic signal, generates peer to peer traffic signal 1114, and transmits it to WT B 1104. WT B 1104 receives traffic signal 1114 and, if the traffic information restoration is successful, generates traffic acknowledgment signal 1116 and sends it to WT A 1102.
FIG. 12 is a drawing 1200 used to illustrate aspects of various embodiments including an exemplary outflow calculation used in transmitter yield determination based on link load weight values. In FIG. 12, wireless terminal A (WT A 1202) and WT B 1204 have a first connection referred to as peer-to-peer connection 1, WT C 1206 and WT D 1208 have a second connection referred to as peer-to-peer connection 2, and WT E1210 and WT F1212 have a third connection called connection 3. The WT (1202, 1204, 1206, 1208, 1210, 1212) is illustrated, described, and / or implements one or more of one or more of the methods of FIGS. One of the WTs.
Assume that in this particular traffic transmission slot, connection 1 has a lower priority than both connection 2 and connection 3. Further, (WT A1202, WT C1206, WT E1210) each transmit traffic signals to (WT B1204, WT D1208, WT F1212) in the traffic slot, respectively, using the same air link traffic resource, eg, traffic segment. Suppose you want to.
In the transmission request, the blocks (WT A1202, WT C1206, WT E1210) respectively send traffic transmission request signals (TX request 1 1214, TX request 2 1222, TX request 3 1228), respectively (WT B1204, WT D1208, WT). F1212). Assume that the wireless terminal (WT B 1204, WT D 1208, WT F1212) has decided not to make an RX concession. Accordingly, the wireless terminal (WT B 1204, WT D 1208, WT F1212) requests traffic transmission request response signals including link load weight values (request response 1 1216 including link load weight value L1 1218, request including link load weight value L2 1226). Response 2 1224, request response 3 1230 including link load weight value L3 1232) is generated and transmitted to the wireless terminals (WT A 1202, WT C 1206, WT E 1210), respectively.
In this example, the TX concession determination of WT A1202 is considered. WT A 1202 monitors and detects request response 1 1216 including link load weight value L1 1218. WT A determines an estimate of the channel between WT B and WT A 1202 by measurement, for example, and this estimate is referred to as h1 1220. Assume that the channel from WT B to WT A and the channel from WT A to WT B are approximately the same. WT A 1202 also monitors request response signals (request response 2 1224 carrying link load weight value L2 1226, request response 3 1230 carrying link load weight value L3 1232) corresponding to other higher priority connections. And detect. WT A determines an estimate of the channel between WT D 1208 and WT A 1202 by measurement, for example, and this estimate is referred to as h2 1228. Assume that the channel from WT D to WT A and the channel from WT A to WT D are approximately the same. WT A determines an estimate of the channel between WT F1212 and WT A1202, for example by measurement, and this estimate is referred to as h3 1234. Assume that the channel from WT F to WT A and the channel from WT A to WT F are approximately the same.
WT A 1202 calculates an outflow value to be used in the TX concession decision. In some embodiments, WT A 1202 calculates a total spill value, for example, total spill = (h2) (L2) / h1 + (h3) (L3) / h1. WT A 1202 then calculates weighted SINR = L1 / total outflow. In some embodiments, the WT A 1202 compares the weighted SINR with a threshold and determines to make a TX concession if it is lower than the threshold, otherwise it does not make a TX concession. In some embodiments, WT A 1202 determines an interference cost estimate from the weighted SINR, eg, interference cost estimate = 1 / weighted SINR. The WT A then compares the interference cost estimate with a threshold and performs a TX concession if the interference cost estimate is above the threshold, otherwise it does not make a TX concession.
This exemplary total outflow calculation can be extended to N links with higher priority than the first link as follows.
In some embodiments, WT A 1202 calculates an individual spill value corresponding to each higher priority link, eg, as follows.
WT A 1202 then calculates weighted SINR 12 = L1 / individual outflow 12 and weighted SINR 13 = L1 / individual outflow 13 . In some embodiments, the WT A 1202 compares each weighted SINR to a threshold and decides to make a TX concession if any one is lower than the threshold, and otherwise, a TX concession. do not do. In some embodiments, WT A 1202 determines an individual interference cost estimate from the individual weighted SINR, eg, individual interference cost estimate = 1 / individually weighted SINR. WT A 1202 then compares each interference cost estimate with a threshold and decides to make a TX concession if any one of the individual cost estimates exceeds the threshold, otherwise TX TX No concessions.
FIG. 13 is a diagram of an example first communication device 1300 according to an example embodiment. The first communication device 1300 is, for example, a mobile wireless terminal that supports peer-to-peer communication and implements the method described in the flowchart 200 of FIG.
The first communication device 1300 includes a processor 1302 and a memory 1304 coupled to each other via a bus 1306, through which various elements (1302, 1304) can exchange data and information. . The processor 1302 receives a transmission request from the second communication device, generates a link load weight value, and a transmission request including a link load weight value in response to the transmission request from the second communication device. Sending a response. The link load weight value, in some embodiments, is the weight to be used when making a transmitter yield decision.
In some embodiments, the processor 1302 is configured to recover at least one parameter from the transmission request, wherein the at least one parameter is i) a transmission queue length, ii) a service corresponding to traffic data to be transmitted. Including at least one of a quality requirement, or iii) a pre-calculated indication of the probability of successful communication over the communication link between the second communication device and the first device. In some such embodiments, the processor 1302 is further configured to generate the link load weight value using the at least one parameter in combination with at least some local information.
In some embodiments, the processor 1302 receives one or more additional transmission requests during a request interval during which a transmission request from the second communication device is received and receives during the request interval. And determining the number of additional transmission requests and generating a link load weight value based on the determined number of additional transmission requests. In some such embodiments, the processor is further configured to generate the link load weight value based on a transmission queue length and quality of service requirements indicated in the received additional transmission request.
FIG. 14 is an assembly 1400 of modules that can be used in the first communication device 1300 shown in FIG. 13 and, in some embodiments, used in that device. Modules in assembly 1400 may be implemented in hardware within processor 1302 of FIG. Alternatively, the modules can be implemented in software and stored in the memory 1304 of the communication device 1300 shown in FIG. Although shown in the embodiment of FIG. 13 as a single processor, eg, a computer, it should be appreciated that the processor 1302 can be implemented as one or more processors, eg, a computer. When implemented in software, the modules contain code that, when executed by a processor, configures the processor 1302, eg, a computer, to implement functionality corresponding to that module. In an embodiment where an assembly of modules 1400 is stored in memory 1304, memory 1304 is a computer program product comprising a computer readable medium that corresponds to at least one computer, eg, processor 1302. Code for implementing the function, for example, individual code for each module is provided.
Fully hardware based or fully software based modules can be used. However, it should be appreciated that any combination of software modules and hardware modules (eg, implemented circuitry) can be used to implement the functionality. The module shown in FIG. 14 controls and / or configures elements in that device, such as first communication device 1300 or processor 1302, to perform the functions of the corresponding steps shown in the method of flowchart 200 of FIG. I want you to understand that.
As shown in FIG. 14, an assembly of modules 1400 includes a module 1402 for receiving a transmission request from a second communication device, a module 1404 for generating a link load weight value, and a second communication device. And a module 1406 for transmitting a transmission request response including the link load weight value in response to the transmission request. The module assembly 1400 further includes a module 1408 for recovering at least one parameter from the transmission request, wherein the at least one parameter is i) transmission queue length, ii) quality of service corresponding to traffic data to be transmitted. Including at least one of a requirement, or 3) a pre-calculated indication of the probability of successful communication over a communication link between a second communication device and the first device. A module 1404 for generating a link load weight value may, in some embodiments, use the at least one parameter in combination with at least some local information when generating the link load weight value. Composed. The module assembly 1400 received during the request interval with a module 1410 for receiving one or more additional transmission requests during the request interval during which the transmission request from a second communication device was received. A module 1412 for determining the number of additional transmission requests. In some, but not necessarily all, modules 1404 for generating link load weight values generate link load weight values based on the determined number of additional transmission requests. In at least some such embodiments, the module 1404 for generating the link load weight value is based on a transmission queue length and a quality of service requirement indicated in the received additional transmission request. Is generated.
FIG. 15 is a diagram of an example first communication device 1500 in accordance with an example embodiment. First communication device 1500 is, for example, a mobile wireless terminal that supports peer-to-peer communication and implements the method described in flowchart 400 of FIG. The first communication device 1500 includes a processor 1502 and a memory 1504 coupled to each other via a bus 1506, through which various elements (1502, 1504) can exchange data and information. . The processor 1502 receives a request response from a second communication device that responds to a transmission request from the first communication device, receives a first link load weight value from a third communication device, and And making a transmitter yield determination based on a first link load weight value received from a third communication device. The processor 1502 is further configured to receive the first link load weight value in a request response from a third communication device in some such embodiments.
In various embodiments, the processor 1502 may: i) transmit queue length, ii) quality of service requirements corresponding to traffic data to be transmitted, or iii prior to receiving the request response from a second communication device. ) A second link load weight value based on at least one of the pre-computed indications about the probability of successful communication on the communication link between the first device and the second communication device; And transmitting the transmission request including the generated second link load weight value to the second communication device prior to receiving the request response from the second communication device. And is further configured to do that.
The processor 1502 is configured in some embodiments to recover the second link load weight value from the request response received from the second communication device. In some embodiments, the processor 1502 may receive a first link load weight value received from a third communication device, the first communication device, and the first as part of making the transmitter yield decision. An interference cost estimate is configured to be generated based on the second link load weight value corresponding to the connection between the two communication devices.
FIG. 16 is an assembly 1600 of modules that can be used in the first communication device 1500 shown in FIG. 15 and, in some embodiments, used in that device. Modules in assembly 1600 may be implemented in hardware within processor 1502 of FIG. 15, for example, as separate circuits. Alternatively, the modules can be implemented in software and stored in the memory 1504 of the first communication device 1500 shown in FIG. Although shown in the embodiment of FIG. 15 as a single processor, eg, a computer, it should be appreciated that the processor 1502 can be implemented as one or more processors, eg, computers. When implemented in software, the modules contain code, and when the code is executed by the processor 1502, configures the processor 1502, eg, a computer, to implement functionality corresponding to the module. In an embodiment in which an assembly of modules 1600 is stored in memory 1504, memory 1504 is a computer program product comprising a computer readable medium that corresponds to at least one computer, eg, processor 1502. A code for implementing the function, for example, an individual code for each module is provided.
Fully hardware based or fully software based modules can be used. However, it should be appreciated that any combination of software modules and hardware modules (eg, implemented circuitry) can be used to implement the functionality. The modules shown in FIG. 16 understand and control and / or configure elements in that device, such as communication device 1500 or processor 1502, to perform the functions of the corresponding steps shown in the method of flowchart 400 of FIG. I want to be.
As shown in FIG. 16, a module assembly 1600 includes a module 1602 for receiving a request response from a second communication device that responds to a transmission request from the first communication device, and a third communication device from the third communication device. A module 1604 for receiving a link load weight value of 1 and a module 1606 for making a transmitter yield determination based on a first link load weight value received from a third communication device. In some embodiments, the first link load weight value is received in a request response from the third communication device.
The assembly of modules 1600, in some embodiments, prior to receiving the request response from a second communication device, i) transmission queue length, ii) quality of service requirements corresponding to traffic data to be transmitted. Or iii) a link load weight value based on at least one of the pre-computed indications about the probability of successful communication over the communication link between the first device and the second communication device And the transmission request including the generated link load weight value to the second communication device prior to receiving the request response from the second communication device. A module for further comprising.
The module assembly 1600 can and sometimes includes a module 1612 for recovering a link load weight value from a request response received from a second communication device.
In some, but not necessarily all, modules 1604 for making transmitter yield decisions based on a first link load weight value received from a third communication device are received from the third communication device. A module 1614 for generating an interference cost estimate based on the first link load weight value determined and the link load weight value corresponding to the connection between the first communication device and the second communication device. .
The techniques of the various embodiments may be implemented using software, hardware and / or a combination of software and hardware. Various embodiments are directed to apparatus, eg, a mobile node such as a mobile access terminal, a base station including one or more attachment points, and / or a communication system. Various embodiments are also directed to methods, eg, methods for controlling and / or operating mobile nodes, base stations, and / or communication systems, eg, hosts. Various embodiments also include machine, eg, computer, readable media, eg, ROM, RAM, CD, hard disk, including machine readable instructions for controlling the machine to perform one or more steps of the method. And so on.
It is to be understood that the specific order or hierarchy of steps in the processes disclosed is an example of an exemplary approach. It should be understood that based on design preferences, a particular order or hierarchy of steps in the process can be reconfigured while remaining within the scope of this disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not limited to the specific order or hierarchy presented.
In various embodiments, a node described herein may correspond to one or more methods, eg, receiving a transmission request signal, generating a link load weight value, and a link load weight value. One for performing a transmission request response including, receiving a request response signal, restoring a link load weight value, making a transmitter yield decision based on the received link load weight value, etc. Or it is implemented using multiple modules. Thus, in some embodiments, various functions are implemented using modules. Such modules can be implemented using software, hardware or a combination of software and hardware. Many of the above methods or method steps control a machine, for example a general purpose computer, with or without additional hardware, to implement all or part of the above method, eg, at one or more nodes. Can be implemented using machine-executable instructions, such as software, contained in a machine-readable medium such as a RAM device, floppy disk, etc., for example. Thus, in particular, various embodiments provide machine-executable instructions for causing a machine, eg, a processor and associated hardware, to perform one or more of the above-described method step (s). Is intended for machine-readable media including: Some embodiments are directed to a device, eg, a communication device, that includes a processor configured to perform one, more than one, or all of the one or more method steps of the present invention.
Some embodiments provide a computer-readable medium comprising code for causing a computer or computers to perform various functions, steps, acts, and / or operations, eg, one or more of the steps described above. A computer program product comprising Depending on the embodiment, a computer program product can, and sometimes does, include different code for each step to be performed. Thus, a computer program product can and sometimes includes code for each individual step of a method, eg, a method of controlling a communication device or node. The code can be in the form of a machine, eg, computer-executable instructions, stored on a computer-readable medium such as RAM (Random Access Memory), ROM (Read Only Memory), or other type of storage device. In addition to targeting a computer program product, some embodiments perform one or more of the various functions, steps, acts, and / or operations of one or more of the methods described above. It is intended for a processor configured as described above. Accordingly, some embodiments are directed to a processor, eg, a CPU, configured to perform some or all of the method steps described herein. The processor can be used, for example, in the communication device or other devices described in this application.
In some embodiments, one or more devices, eg, one or more processors, eg, CPUs, of a communication device, such as a wireless terminal, perform the method steps described as being executed by the communication device. Configured to do. Accordingly, some, but not all, embodiments are directed to devices having a processor, eg, a communication device, that includes a module corresponding to each of the various described method steps performed by the device in which the processor is included. To do. In some, but not all, devices, eg, communication devices, include modules corresponding to each of the various described method steps performed by the device in which the processor is included. Modules can be implemented using software and / or hardware.
Although described with respect to an OFDM system, at least some of the methods and apparatus of the various embodiments are applicable to a wide range of communication systems including many non-OFDM and / or non-cellular systems. At least some of these methods and apparatus are applicable to hybrid systems, eg, systems that include OFDM and CDMA signaling techniques.
In view of the above description, many additional variations on the methods and apparatus of the various embodiments described above will be apparent to those skilled in the art. Such variations should be considered within the scope. The method and apparatus can be used with CDMA, orthogonal frequency division multiplexing (OFDM), and / or various other types of communication techniques used to provide a wireless communication link between an access node and a mobile node. Used in various embodiments. In some embodiments, the access node is implemented as a base station that establishes a communication link with the mobile node using OFDM and / or CDMA. In various embodiments, the mobile node is as a notebook computer, personal information terminal (PDA), or other portable device that includes a receiver / transmitter circuit and logic and / or routines for performing the method. Implemented.
The claims described in the claims at the beginning of the application will be appended.
(1) A method of operating a first communication device,
Receiving a transmission request from a second communication device;
Generating a link load weight value;
In response to the transmission request from the second communication device, transmitting a transmission request response including the link load weight value;
(2) further comprising restoring at least one parameter from the transmission request, wherein the at least one parameter is i) a transmission queue length, ii) a quality of service requirement corresponding to traffic data to be transmitted, or iii) the Including at least one of pre-calculated indications about the probability of successful communication over a communication link between a second communication device and the first device
(1) The method as described.
(3) The method of (2), wherein generating the link load weight value comprises using the at least one parameter in combination with at least some local information.
(4) receiving one or more additional transmission requests during a request interval during which the transmission request from the second communication device was received;
Determining the number of additional transmission requests received during the request interval;
The method of (2), wherein the link load weight value is generated based on the determined number of additional transmission requests.
(5) The method according to (4), wherein the link load weight value is generated based on a transmission queue length and a quality of service requirement indicated in the received additional transmission request.
(6) A first communication device,
(7) The at least one processor is further configured to recover at least one parameter from the transmission request, the at least one parameter corresponding to i) a transmission queue length and ii) traffic data to be transmitted. Quality of service requirements, or iii) at least one of pre-calculated indications about the probability of successful communication on a communication link between the second communication device and the first device, 6) The 1st communication device of description.
(8) The first of (7), wherein the at least one processor is further configured to generate a link load weight value using the at least one parameter in combination with at least some local information Communication device.
(9) the at least one processor comprises:
Receiving one or more additional transmission requests during a request interval during which the transmission request from the second communication device was received;
Generating the link load weight value based on the determined number of additional transmission requests;
The first communication device according to (7), further configured to perform:
(10) The description (9), wherein the at least one processor is further configured to generate the link load weight value based on a transmission queue length and a quality of service requirement indicated in the received additional transmission request. First communication device.
(11) A first communication device,
Means for receiving a transmission request from a second communication device;
Means for generating a link load weight value;
Means for transmitting a transmission request response including the link load weight value in response to the transmission request from the second communication device;
(12) further comprising means for recovering at least one parameter from the transmission request, wherein the at least one parameter is i) a transmission queue length, ii) a quality of service requirement corresponding to traffic data to be transmitted, or iii ) Including at least one of pre-calculated instructions for the probability of successful communication on a communication link between the second communication device and the first device
(11) The first communication device according to (11).
(13) The means for generating a link load weight value is configured to use the at least one parameter in combination with at least some local information when generating the link load weight value. (12) The first communication device according to (12).
(14) means for receiving one or more additional transmission requests during a request interval in which the transmission request from the second communication device is received;
Means for determining the number of additional transmission requests received during said request interval;
The first communication device of (12), wherein the means for generating a link load weight value generates a link load weight value based on the determined number of additional transmission requests.
(15) The method according to (14), wherein the means for generating a link load weight value generates a link load weight value based on a transmission queue length and a quality of service requirement indicated in the received additional transmission request. First communication device.
(16) a code for causing at least one computer to receive a transmission request from a communication device;
Code for causing the at least one computer to generate a link load weight value;
A code for causing the at least one computer to transmit a transmission request response including the link load weight value in response to the transmission request from the communication device;
(17) The computer-readable medium is
Further comprising code for causing the at least one computer to restore at least one parameter from the transmission request, the at least one parameter corresponding to i) a transmission queue length and ii) traffic data to be transmitted (Iii) including at least one of a pre-computed indication about the probability of successful communication on a communication link between a second communication device and the first device; 16) The computer program product described.
(18) The computer-readable medium is
The computer program product of (17), further comprising code for causing the at least one computer to generate a link load weight value using the at least one parameter in combination with at least some local information. .
(19) A method of operating a first communication device,
Receiving a request response from a second communication device responding to a transmission request from the first communication device;
Receiving a first link load weight value from a third communication device;
Making a transmitter concession decision based on the first link load weight value received from the third communication device;
(20) The method according to (19), wherein the first link load weight value is received in a request response from the third communication device.
(21) Before receiving the request response from the second communication device,
i) transmission queue length, ii) quality of service requirements corresponding to the traffic data to be transmitted, or iii) probability of successful communication over the communication link between the first communication device and the second device Generating a second link load weight value based on at least one of the pre-calculated instructions of:
Transmitting the transmission request including the generated second link load weight value to the second communication device;
(22) The method further comprises restoring a second link load weight value from the request response received from the second communication device.
(20) The method described.
(23) performing the transmitter concession decision;
Based on the first link load weight value received from the third communication device and a second link load weight value corresponding to a connection between the first communication device and the second communication device. The method according to (20), comprising generating an interference cost estimate.
(24) comparing the generated interference cost estimate with a transmitter yield threshold;
Sending traffic data to the second communication device when the comparison indicates that the generated interference cost estimate is below the threshold;
The method according to (23), further comprising:
(25) making the transmitter concession decision;
Generating a plurality of interference cost estimates during a traffic interval, each for a different connection having a higher priority than a connection between the first communication device and the second communication device; Corresponding to generating,
Comparing the generated interference cost estimate with a transmitter yield threshold for each of the individual generated multiple interference cost estimates;
Sending traffic data to the second communication device during the traffic interval when the comparison indicates that each of the various generated interference cost estimates is below the threshold;
The method according to (20), comprising:
(26) During the traffic interval, when the comparison indicates that any one of the various generated interference cost estimates corresponding to higher priority connections exceeds the threshold. Further comprising controlling the first communication device to refrain from transmitting traffic data to the second communication device.
(25) The method described.
(27) generating the interference cost estimate between the first link load weight value received from the third communication device and the third communication device and the first communication device; The method of (23), comprising calculating an outflow value based on a channel measurement value generated from the channel measurement value.
(28) generating the interference cost estimate generating an outflow sum corresponding to a higher priority link than the link between the first communication device and the second communication device; The method according to (23), comprising:
(29) generating the interference cost estimate comprises generating an outflow sum corresponding to another set of links, including a connection in which the first device does not participate, where a request response is detected; (23) The method described.
(30) A first communication device,
(31) The first communication device according to (30), wherein the at least one processor is further configured to receive the first link load weight value in a request response from the third communication device. .
(32) wherein the at least one processor is
Prior to receiving the request response from the second communication device, i) transmission queue length, ii) quality of service requirement corresponding to traffic data to be transmitted, or iii) the first communication device and the Generating a second link load weight value based on at least one of the pre-computed indications about the probability of successful communication on the communication link with the second device;
Transmitting the transmission request including the generated second link load weight value to the second communication device prior to receiving the request response from the second communication device;
The first communication device according to (31), further configured to perform:
(33) wherein the at least one processor is
The first communication device according to (31), further configured to restore a second link load weight value from the request response received from the second communication device.
(34) wherein the at least one processor is
As part of making the transmitter yield determination, the first link load weight value received from the third communication device and the connection between the first communication device and the second communication device The first communication device according to (31), further configured to generate an interference cost estimate based on a second link load weight value corresponding to.
(35) a first communication device,
Means for receiving a request response from a second communication device in response to a transmission request from the first communication device;
Means for receiving a first link load weight value from a third communication device;
Means for making a transmitter yield determination based on the first link load weight value received from the third communication device;
(36) The first communication device according to (35), wherein the first link load weight value is received in a request response from the third communication device.
(37) prior to receiving the request response from the second communication device, i) a transmission queue length, ii) a quality of service requirement corresponding to traffic data to be transmitted, or iii) the first communication For generating a second link load weight value based on at least one of pre-calculated indications about the probability of successful communication on a communication link between the device and the second device Means,
Means for transmitting the transmission request including the generated second link load weight value to the second communication device prior to receiving the request response from the second communication device;
The first communication device according to (36), further comprising:
(38) A means for restoring a second link load weight value from the request response received from the second communication device is further provided.
(36) The first communication device according to (36).
(39) said means for making a transmitter yield decision;
Based on the first link load weight value received from the third communication device and a second link load weight value corresponding to a connection between the first communication device and the second communication device. The first communication device according to (36), further comprising means for generating an interference cost estimate.
(40) a code for causing at least one computer to receive a request response from a second communication device responding to a transmission request from the first communication device;
Code for causing the at least one computer to receive a first link load weight value from a third communication device;
A code for causing the at least one computer to make a transmitter yield determination based on the first link load weight value received from the third communication device;
A method for operating a first communication device comprising:
Generating a link load weight value for the first communication device for use in making a receiver concession decision with respect to the transmission request ;
Transmitting a transmission request response including the link load weight value in response to the transmission request from the second communication device.
Recovering at least one parameter from the transmission request, wherein the at least one parameter is i) a transmission queue length, ii) a quality of service requirement corresponding to traffic data to be transmitted, or iii) the second The method of claim 1, comprising at least one of pre-calculated indications about the probability of successful communication over a communication link between a communication device and the first device.
The method of claim 2, wherein the generating a link load weight value comprises using the at least one parameter in combination with at least some local information.
The method of claim 2, wherein the link load weight value is generated based on the determined number of additional transmission requests.
The method of claim 4, wherein the link load weight value is generated based on a transmission queue length and quality of service requirements indicated in the received additional transmission request.
Generating a link link load weight value for the first communication device for use in making a receiver concession decision with respect to the transmission request ;
At least one processor configured to transmit a transmission request response including the link load weight value in response to the transmission request from the second communication device;
The at least one processor is further configured to recover at least one parameter from the transmission request, wherein the at least one parameter corresponds to i) transmission queue length and ii) traffic data to be transmitted. Or iii) comprising at least one of pre-calculated indications about the probability of successful communication over a communication link between the second communication device and the first device. A first communication device as described.
The first communication device of claim 7, wherein the at least one processor is further configured to generate a link load weight value using the at least one parameter in combination with at least some local information. .
The first communication device of claim 7, further configured to generate the link load weight value based on the determined number of additional transmission requests.
10. The first of claim 9, wherein the at least one processor is further configured to generate the link load weight value based on a transmission queue length and quality of service requirements indicated in the received additional transmission request. 1 communication device.
Means for generating a link link load weight value for the first communication device for use in making a receiver concession decision with respect to the transmission request ;
Means for transmitting a transmission request response including the link load weight value in response to the transmission request from the second communication device.
Means for recovering at least one parameter from the transmission request, wherein the at least one parameter is i) a transmission queue length, ii) a quality of service requirement corresponding to traffic data to be transmitted, or iii) the first 12. The first communication device of claim 11, comprising at least one of pre-computed indications about the probability of successful communication on a communication link between two communication devices and the first device. .
13. The means for generating a link load weight value is configured to use the at least one parameter in combination with at least some local information when generating the link load weight value. 1st communication device.
Means for receiving one or more additional transmission requests during a request interval during which the transmission request from the second communication device was received;
Means for determining the number of additional transmission requests received during the request interval;
The first communication device of claim 12, wherein the means for generating a link load weight value generates a link load weight value based on the determined number of additional transmission requests.
15. The first of claim 14, wherein the means for generating a link load weight value generates a link load weight value based on a transmission queue length and a quality of service requirement indicated in the received additional transmission request. Communication devices.
A computer-readable medium storing code, wherein the code is
Code for causing at least one computer to receive a transmission request from a communication device;
Code for causing the at least one computer to generate a link link load weight value for the first communication device for use in making a receiver concession decision with respect to the transmission request ;
A computer readable medium comprising: code for causing the at least one computer to transmit a transmission request response including the link load weight value in response to the transmission request from the communication device.
The code of the computer readable medium is
Further comprising code for causing the at least one computer to restore at least one parameter from the transmission request, the at least one parameter corresponding to i) a transmission queue length and ii) traffic data to be transmitted Or iii) at least one pre-calculated indication of the probability of successful communication over a communication link between a second communication device and the first device. Item 17. The computer-readable medium according to Item 16.
18. The computer readable code of claim 17, further comprising code for causing the at least one computer to generate a link load weight value using the at least one parameter in combination with at least some local information. Medium .
Making a transmitter concession decision for the transmission request at the first communication device based on the first link load weight value received from the third communication device.
The method of claim 19, wherein the first link load weight value is received in a request response from the third communication device.
Before receiving the request response from the second communication device,
21. The method of claim 20, further comprising: transmitting the transmission request including the generated second link load weight value to the second communication device.
20. The method of claim 19 , further comprising restoring a second link load weight value from the request response received from the second communication device.
Making the transmitter concession determination,
Based on the first link load weight value received from the third communication device and a second link load weight value corresponding to a connection between the first communication device and the second communication device. 20. The method of claim 19 , comprising generating an interference cost estimate.
Comparing the generated interference cost estimate with a transmitter yield threshold;
24. The method further comprising: transmitting traffic data to the second communication device when the comparison indicates that the generated interference cost estimate is below the threshold. the method of.
Sending traffic data to the second communication device during the traffic interval when the comparison indicates that each of the various generated interference cost estimates is below the threshold; 21. The method of claim 20, comprising:
When the comparison indicates that any one of the various generated interference cost estimates corresponding to higher priority connections exceeds the threshold, the second during the traffic interval. 26. The method of claim 25, further comprising controlling the first communication device to refrain from sending traffic data to the other communication device.
The generating the interference cost estimate comprises measuring the first link load weight value received from the third communication device and a channel between the third communication device and the first communication device. 24. The method of claim 23, comprising calculating an outflow value based on a channel measurement generated from the value.
The generating the interference cost estimate comprises generating an outflow sum corresponding to a higher priority link than the link between the first communication device and the second communication device. Item 24. The method according to Item 23.
24. The generating the cost of interference estimate comprises generating an outflow sum corresponding to a set of other links that includes connections in which the first device does not participate in which a request response has been detected. The method described in 1.
Making a transmitter concession decision for the transmission request at the first communication device based on the first link load weight value received from the third communication device;
31. The first communication device of claim 30, wherein the at least one processor is further configured to receive the first link load weight value in a request response from the third communication device.
Prior to receiving the request response from the second communication device, transmitting the transmission request including the generated second link load weight value to the second communication device. 32. The first communication device of claim 31, further configured to:
31. The first communication device of claim 30 , further configured to restore a second link load weight value from the request response received from the second communication device.
As part of making the transmitter yield determination, the first link load weight value received from the third communication device and the connection between the first communication device and the second communication device 31. The first communication device of claim 30 , further configured to generate an interference cost estimate based on a second link load weight value corresponding to.
Means for making a transmitter concession decision for the transmission request for the first communication device based on the first link load weight value received from the third communication device. Communication device.
36. The first communication device of claim 35, wherein the first link load weight value is received in a request response from the third communication device.
Prior to receiving the request response from the second communication device, i) transmission queue length, ii) quality of service requirement corresponding to traffic data to be transmitted, or iii) the first communication device and the Means for generating a second link load weight value based on at least one of the pre-calculated indications about the probability of successful communication on the communication link with the second device;
Means for transmitting the transmission request including the generated second link load weight value to the second communication device prior to receiving the request response from the second communication device. The first communication device of claim 36, further comprising:
37. The first communication device of claim 36, further comprising means for recovering a second link load weight value from the request response received from the second communication device.
Said means for making a transmitter concession decision;
Based on the first link load weight value received from the third communication device and a second link load weight value corresponding to a connection between the first communication device and the second communication device. 37. The first communication device of claim 36, comprising means for generating an interference cost estimate.
Code for causing at least one computer to receive a request response from the communication devices that respond to a transmission request from at least a computer,
Code for causing the at least one computer to receive a link load weight value from a further communication device;
Computer readable medium comprising code for causing at least one computer to perform transmitter yielding decision regarding the transmission request based on the cut link load weight value before received from the further communication device.
JP2011505151A 2008-04-15 2009-04-14 Method and apparatus for communicating and / or using load information to support distributed traffic scheduling decisions Active JP5226860B2 (en)
US4503008P true 2008-04-15 2008-04-15
US61/045,030 2008-04-15
US12/268,138 2008-11-10
US12/268,138 US8750116B2 (en) 2008-04-15 2008-11-10 Methods and apparatus for communicating and/or using load information in support of decentralized traffic scheduling decisions
PCT/US2009/040576 WO2009129268A2 (en) 2008-04-15 2009-04-14 Methods and apparatus for communicating and/or using load information in support of decentralized traffic scheduling decisions
JP2011520331A JP2011520331A (en) 2011-07-14
JP5226860B2 true JP5226860B2 (en) 2013-07-03
ID=41163895
JP2011505151A Active JP5226860B2 (en) 2008-04-15 2009-04-14 Method and apparatus for communicating and / or using load information to support distributed traffic scheduling decisions
US (1) US8750116B2 (en)
EP (1) EP2266267A2 (en)
JP (1) JP5226860B2 (en)
KR (3) KR20130066710A (en)
CN (1) CN101978660B (en)
TW (1) TW200948156A (en)
WO (1) WO2009129268A2 (en)
CN104885484B (en) * 2012-12-14 2019-04-05 华为技术有限公司 It is provided using the service of abstract network resource requirement
KR101890499B1 (en) * 2013-11-05 2018-08-21 엘지전자 주식회사 D2d communication method and apparatus based on channel hopping
CN104955141B (en) * 2014-03-27 2018-11-02 大唐电信科技产业控股有限公司 A kind of Poewr control method and device
US20170251487A1 (en) * 2014-09-26 2017-08-31 Amit Kalhan Cooperative distributed scheduling for device-to-device (d2d) communication
US20180132190A1 (en) * 2015-06-30 2018-05-10 Jeongho Jeon Distributed link scheduling technique for device to device communication
JP4503934B2 (en) * 2002-09-26 2010-07-14 株式会社東芝 Server computer protection device, server computer protection method, server computer protection program, and server computer
RU2391798C2 (en) * 2005-10-26 2010-06-10 Квэлкомм Инкорпорейтед Use of resources application messages in mac with multiple carriers to achieve parity
ES2356858T3 (en) 2006-08-07 2011-04-13 Qualcomm Incorporated MESSAGE EXCHANGE SCHEME FOR ASynchronous WIRELESS COMMUNICATIONS.
CN101039277A (en) 2007-04-12 2007-09-19 华为技术有限公司 Load sharing method and its equipment
2008-11-10 US US12/268,138 patent/US8750116B2/en active Active
2009-04-14 JP JP2011505151A patent/JP5226860B2/en active Active
2009-04-14 KR KR1020137013557A patent/KR20130066710A/en active IP Right Grant
2009-04-14 EP EP09733271A patent/EP2266267A2/en not_active Withdrawn
2009-04-14 KR KR1020107025590A patent/KR101547183B1/en active IP Right Grant
2009-04-14 KR KR1020157008847A patent/KR101560628B1/en not_active IP Right Cessation
2009-04-14 WO PCT/US2009/040576 patent/WO2009129268A2/en active Application Filing
2009-04-14 CN CN200980110674.4A patent/CN101978660B/en not_active IP Right Cessation
2009-04-15 TW TW098112562A patent/TW200948156A/en unknown
WO2009129268A3 (en) 2010-01-14
CN101978660B (en) 2015-04-01
KR20110005864A (en) 2011-01-19
KR101560628B1 (en) 2015-10-15
TW200948156A (en) 2009-11-16
JP2011520331A (en) 2011-07-14
US8750116B2 (en) 2014-06-10
KR20150046354A (en) 2015-04-29
WO2009129268A2 (en) 2009-10-22
KR101547183B1 (en) 2015-08-25
CN101978660A (en) 2011-02-16
EP2266267A2 (en) 2010-12-29
US20090257351A1 (en) 2009-10-15
KR20130066710A (en) 2013-06-20
ES2427133T3 (en) 2013-10-28 Wireless communication procedures and devices that support peer communication
JP2009512356A (en) 2009-03-19 Method and apparatus for determining, communicating and using information including load factors for interference control
CN101843050B (en) 2013-11-27 Communications method and apparatus related to traffic scheduling and rate control in peer to peer communications system
US8874114B2 (en) 2014-10-28 Mobile communications system, mobile station and base station
ES2632129T3 (en) 2017-09-11 Procedures and apparatus for controlling interference in broadcasting signaling in a peer network
US7394789B2 (en) 2008-07-01 Handoff control method, base station controller, and base transceiver subsystem
JP5372969B2 (en) 2013-12-18 Method and apparatus for using multiple connection identifiers based on a traffic request
US8694662B2 (en) 2014-04-08 Method and apparatus for communicating transmission requests to members of a group and/or making group related transmission decisions
US8331946B2 (en) 2012-12-11 Methods and apparatus for supporting multiple users in a system with multiple polarized antennas
WO2011079729A1 (en) 2011-07-07 Power control method and apparatus
CN101978660B (en) 2015-04-01 Methods and apparatus for communicating and/or using load information in support of decentralized traffic scheduling decisions
EP2260671B1 (en) 2018-07-25 Methods and apparatus for using connection identifiers having different priorities at different times