[go: up one dir, main page]

WO2013107004A1 - Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal - Google Patents

Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal Download PDF

Info

Publication number
WO2013107004A1
WO2013107004A1 PCT/CN2012/070521 CN2012070521W WO2013107004A1 WO 2013107004 A1 WO2013107004 A1 WO 2013107004A1 CN 2012070521 W CN2012070521 W CN 2012070521W WO 2013107004 A1 WO2013107004 A1 WO 2013107004A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
message
channel
dsbdr
sent
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2012/070521
Other languages
English (en)
Inventor
Haifeng Wang
Zhenhong Li
Ting Zhou
Jing Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Renesas Electronics Corp
Original Assignee
Renesas Mobile Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Renesas Mobile Corp filed Critical Renesas Mobile Corp
Priority to PCT/CN2012/070521 priority Critical patent/WO2013107004A1/fr
Publication of WO2013107004A1 publication Critical patent/WO2013107004A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance

Definitions

  • Embodiments of the present invention relate generally to wireless communication technology and, more particularly, relate to an apparatus, method and computer program product for facilitating concurrent occupation of a channel.
  • D2D communication technologies may use radio resources of a hosting cellular system, but allow two computing devices, such as mobile terminals (also referred to as user equipment (UE)), to communicate directly with each other without routing their communications through components of the cellular system.
  • UE user equipment
  • D2D communication may offer several advantages. For example, the direct communication link between mobile terminals engaged in D2D communication may result in reduced end-to-end delay time for data exchanged between the terminals as compared to indirect communication via cellular system components. Further, since communications may be offloaded from the cellular network to D2D communication links, network load may be reduced. Additional benefits of D2D communication may include improved local area coverage, improved serving network resource efficiency, and conservation of transmission power by both UEs and network access points. Additionally, D2D communication may support a variety of end user services, such as peer-to-peer applications, head-to-head gaming applications, collaborative applications, and/or the like that may be used by users of mobile terminals within close proximity of each other.
  • end user services such as peer-to-peer applications, head-to-head gaming applications, collaborative applications, and/or the like that may be used by users of mobile terminals within close proximity of each other.
  • Embodiments provided herein may provide several advantages to network providers, wireless service providers, computing devices, and computing device users.
  • some example embodiments improve the spatial reuse of a communication medium while avoiding inter-device interference.
  • some example embodiments facilitate concurrent occupation of a channel by multiple D2D communication groups such that two terminals within carrier-sensing range of each other may transmit simultaneously in the event that their transmissions do not mutually interfere.
  • some example embodiments provide for improved channel efficiency and capacity by allowing concurrent occupation of a channel in the event that there is a hidden terminal and/or an exposed terminal.
  • Some example embodiments are further operational in a manner compliant to conventional channel contention mechanisms, such as the WLAN Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA)
  • Some example embodiments additionally save cellular scheduling signaling overhead and latency delay by providing for concurrent channel use and channel reuse.
  • a method which may comprise determining, at a first terminal that is a member of a first D2D communication group, that the first terminal has not heard a clear to send message within a predefined period of time following the first terminal hearing a message requesting to send data on a channel sent by a second terminal that is a member of a second D2D communication group.
  • the method of this example embodiment may further comprise determining, responsive to determining that the first terminal has not heard a clear to send message within the predefined period of time following the first terminal hearing the message requesting to send data on the channel, to format and send a D2D shared band data request (DSBDR) message to a third terminal requesting the third terminal to send data to the first terminal over the channel during a period of time during which the channel is reserved by the second terminal.
  • the third terminal of this example embodiment may be a member of the first D2D communication group.
  • the method of the first example embodiment provides for improved channel efficiency and capacity by allowing concurrent occupation of a channel in the event that there is a hidden terminal and/or an exposed terminal.
  • an apparatus comprising at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus of this example embodiment to at least determine, at a first terminal that is a member of a first D2D communication group, that the first terminal has not heard a clear to send message within a predefined period of time following the first terminal hearing a message requesting to send data on a channel sent by a second terminal that is a member of a second D2D communication group.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, further cause the apparatus of this example embodiment to determine, responsive to determining that the first terminal has not heard a clear to send message within the predefined period of time following the first terminal hearing the message requesting to send data on the channel, to format and send a DSBDR message to a third terminal requesting the third terminal to send data to the first terminal over the channel during a period of time during which the channel is reserved by the second terminal.
  • the third terminal of this example embodiment may be a member of the first D2D communication group.
  • the apparatus of this example embodiment provides for improved channel efficiency and capacity by allowing concurrent occupation of a channel in the event that there is a hidden terminal and/or an exposed terminal.
  • a computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code stored therein.
  • the computer-readable program code may include instructions configured to cause an apparatus to determine, at a first terminal that is a member of a first D2D communication group, that the first terminal has not heard a clear to send message within a predefined period of time following the first terminal hearing a message requesting to send data on a channel sent by a second terminal that is a member of a second D2D communication group.
  • the computer-readable program code may further include instructions configured to cause the apparatus to determine, responsive to determining that the first terminal has not heard a clear to send message within the predefined period of time following the first terminal hearing the message requesting to send data on the channel, to format and send a DSBDR message to a third terminal requesting the third terminal to send data to the first terminal over the channel during a period of time during which the channel is reserved by the second terminal.
  • the third terminal of this example embodiment may be a member of the first D2D communication group.
  • the computer program product of this example embodiment provides for improved channel efficiency and capacity by allowing concurrent occupation of a channel in the event that there is a hidden terminal and/or an exposed terminal.
  • an apparatus may comprise means for determining, at a first terminal that is a member of a first D2D communication group, that the first terminal has not heard a clear to send message within a predefined period of time following the first terminal hearing a message requesting to send data on a channel sent by a second terminal that is a member of a second D2D
  • the apparatus of this example embodiment may further comprise means for determining, responsive to determining that the first terminal has not heard a clear to send message within the predefined period of time following the first terminal hearing the message requesting to send data on the channel, to format and send a DSBDR message to a third terminal requesting the third terminal to send data to the first terminal over the channel during a period of time during which the channel is reserved by the second terminal.
  • the third terminal of this example embodiment may be a member of the first D2D communication group.
  • the apparatus of this example embodiment provides for improved channel efficiency and capacity by allowing concurrent occupation of a channel in the event that there is a hidden terminal and/or an exposed terminal.
  • FIG. 1 illustrates an example of an exposed terminal problem that may be addressed by some example embodiments
  • FIG. 2 illustrates another example problem that may be addressed by some example embodiments
  • FIG. 3 illustrates an example system for facilitating concurrent occupation of a channel in accordance with some example embodiments
  • FIG. 4 illustrates a block diagram of an access point apparatus in accordance with some example embodiments
  • FIG. 5 illustrates a block diagram of a terminal apparatus in accordance with some example embodiments
  • FIG. 6 illustrates an example channel contending mechanism that may be used by some example embodiments
  • FIG. 7 illustrates an example of concurrent channel occupation in the case of an exposed terminal in accordance with some example embodiments
  • FIG. 8 illustrates an example of concurrent channel occupation in the case that a clear to send message is not sent in accordance with some example embodiments
  • FIG. 9 illustrates an example of channel contention and concurrent channel occupation in the case of multiple exposed terminals in accordance with some example embodiments
  • FIG. 10 illustrates a flowchart according to an example method for facilitating concurrent occupation of a channel according to some example embodiments.
  • FIG. 11 illustrates a flowchart according to another example method for facilitating concurrent occupation of a channel according to some example embodiments.
  • the terms "data,” “content,” “information” and similar terms may be used interchangeably to refer to data capable of being transmitted, received, displayed and/or stored in accordance with various example embodiments. Thus, use of any such terms should not be taken to limit the spirit and scope of the disclosure.
  • a computing device is described herein to receive data from another computing device, it will be appreciated that the data may be received directly from the another computing device or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, and/or the like.
  • circuitry refers to all of the following:
  • circuits and software such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.
  • FIG. 1 illustrates an example of an exposed terminal problem that may be addressed by some example embodiments.
  • the first D2D pair 102 is comprised of the UE1 104 and the UE2 106
  • the second D2D pair 108 is comprised of the UE3 1 10 and UE4 112.
  • the UE2 106 is an exposed terminal, as the UE2 106 and UE3 110 are within carrier-sensing range of each other. Accordingly, in the example of FIG.
  • the request to send (RTS) message 114 sent by the UE3 110 to the UE4 112 is heard by the UE2 106.
  • the UE2 106 is outside of carrier-sensing range of the UE4 112, and does not hear the clear to send (CTS) message 116 sent by the UE4 112 to the UE3 110 in response to the RTS message 114.
  • CTS clear to send
  • the UE3 110 and UE4 1 12 may occupy the channel and exchange data 118 with each other.
  • the UE2 106 and UE4 112 are outside of carrier-sensing range of each other, as illustrated by the caption 120, the UE2 106 may sense that the channel is busy due to reception of the RTS 114 and may update its Network Allocation Vector (NAV), which may define the duration for which the channel will be occupied, to be the duration of a period indicated in the RTS message 1 14 for which the UE3 1 10 reserved the channel.
  • NAV Network Allocation Vector
  • the UE2 106 may not try to access the channel until its NAV timer reaches 0.
  • the first D2D pair 102 may decline to occupy the channel concurrent with the second D2D pair 108 during the period reserved by the UE3 1 10 because the UE2 106 is exposed to the RTS message 114.
  • FIG. 2 illustrates another example problem that may be addressed by some example embodiments.
  • the first D2D pair 202 is comprised of the UE1 204 and the UE2 206
  • the second D2D pair 208 is comprised of the UE3 210 and UE4 212.
  • the UE3 210 may send an RTS message 214 to the UE4 212.
  • the UE4 212 may not respond to the RTS message 214 with a CTS message, such as because the channel is busy or the UE4 212 cannot hear the RTS message 214.
  • the channel may be occupied prior to the UE3 210 sending the RTS message 214 by communications between the UE4 212 and a wireless local area network (WLAN) station (STA) 216.
  • the WLAN STA 216 may, for example, obtain access to a WLAN from the WLAN access point (AP) 218. Since the UE4 212 does not send a CTS message in the example of FIG. 2, the UE3 210 may back off of contending the channel and may contend the channel again after doubling its contention window 222.
  • WLAN wireless local area network
  • the UE2 206 may keep silent for the duration of a NAV period that may correspond to a time indicated in the RTS message 214. Accordingly, the channel may go unused by either the first D2D pair 202 or the second D2D pair 208 during the period indicated as reserved by the RTS message 214. Some example embodiments further described herein may improve channel efficiency in this scenario by facilitating occupancy of the channel by the first D2D pair 202 in the event that the UE2 206 hears the RTS message 214, but no CTS message is sent.
  • FIG. 3 illustrates an example system 300 for facilitating concurrent occupation of a channel in accordance with some example embodiments.
  • system 300 as well as the illustrations in other figures are each provided as an example of an embodiment(s) and should not be construed to narrow the scope or spirit of the disclosure in any way.
  • the scope of the disclosure encompasses many potential embodiments in addition to those illustrated and described herein.
  • FIG. 3 illustrates one example of a configuration of a system for facilitating concurrent occupation of a channel
  • embodiments of the present invention may be implemented in systems having numerous other configurations.
  • an access point 302 may provide cellular network access to one or more terminal apparatuses, such as the UE1 304, UE2 306, UE3 308, UE4 310, UE5 312, and UE6 314.
  • the access point 302 may, for example, comprise an evolved Node B (eNB) that may provide an access point for a Long Term Evolution (LTE) cellular network (e.g., an LTE network, LTE Advanced network, and/or other current or future LTE network).
  • LTE Long Term Evolution
  • LTE Long Term Evolution
  • LTE networks may be implemented with any type of cellular network employing one or more mobile access mechanisms, such as LTE, LTE Advanced (LTE-A), Time Division Synchronous Code Division Multiple Access (TD- SCDMA), wideband code division multiple access (W-CDMA), CDMA2000, global system for mobile communications (GSM), general packet radio service (GPRS), and/or the like.
  • LTE-A LTE Advanced
  • TD- SCDMA Time Division Synchronous Code Division Multiple Access
  • W-CDMA wideband code division multiple access
  • CDMA2000 global system for mobile communications
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • the access point 302 may accordingly be embodied as any type of access point that may provide access to a cellular network, such as an eNB, a node B, base station, base transceiver station, and/or the like.
  • the terminal apparatuses in the system 300 may each comprise any computing device having a cellular network interface that may support interfacing with the access point 302 in order to support cellular network access.
  • the terminal apparatuses may each respectively be embodied as a mobile communication device, mobile telephone, personal digital assistant (PDA), smart phone, tablet computing device, pager, laptop computer, desktop computer with a cellular network adapter, portable game device, positioning device, some combination thereof, or the like. While the terminal apparatuses of the system 300 (e.g., the UEl 304, UE2 306, UE3 308, UE4 310, UE5 312, and UE6 314) are illustrated in FIG.
  • PDA personal digital assistant
  • UE user equipment
  • illustrations and discussion referencing a UE(s) are provided by way of example, and not by way of limitation, as where examples are described and/or illustrated to use UEs, any type of terminal apparatus may be substituted for a UE within the scope of the disclosure.
  • the terminal apparatuses of the system 300 may be grouped into a plurality of D2D communication groups, which may be served by the access point 302. Each D2D communication group may be comprised of two or more terminal apparatuses.
  • the illustration of FIG. 3 illustrates three such D2D communication groups, including a first D2D pairing including the UEl 304 and UE2 306, a second D2D pairing including the UE3 308 and UE4 310, and a third D2D pairing including the UE5 312 and UE6 314.
  • the system 300 is not limited to including three D2D pairings, as the system 300 may include additional or fewer D2D communication groups in some
  • a D2D communication group may include more than two terminal apparatuses.
  • the access point 302 may be configured to support setup of D2D communication between terminal apparatuses in a D2D communication group.
  • the access point 302 may be configured to allocate resources (e.g., in-band resources) for D2D communication, coordinate D2D link setup to accommodate D2D communication between two or more terminal apparatuses in a D2D communication group, control D2D data transmission by terminal apparatuses in a D2D communication group, and/or the like.
  • the access point 302 may be configured to provide such control signaling to support setup of D2D communication via cellular control signaling 316 (e.g., via LTE control signaling and/or via control signaling in accordance with some other cellular communication protocol) to the terminal apparatuses of the system 300.
  • cellular control signaling 316 e.g., via LTE control signaling and/or via control signaling in accordance with some other cellular communication protocol
  • the members of a D2D communication group may communicate via a D2D link 318, which may, for example, comprise wireless transmission of data on an unlicensed band, such as a band in the ISM range.
  • the terminal apparatuses in the system 300 e.g., the UEl 304, UE2 306, UE3 308, UE4 310, UE5 312, UE6 314, and/or the like
  • a first wireless access technology e.g., a cellular modem
  • a different wireless access technology e.g., a WLAN modem
  • FIG. 4 illustrates a block diagram of an access point apparatus 402 in accordance with some example embodiments.
  • the components, devices or elements illustrated in and described with respect to FIG. 4 below may not be mandatory and thus some may be omitted in certain embodiments. Additionally, some embodiments may include further or different components, devices or elements beyond those illustrated in and described with respect to FIG. 4.
  • FIG. 4 illustrates an apparatus that may comprise or be employed on a cellular network access point, such as the access point 302, and which may be configured to perform at least some of the functionality of an access point as described herein.
  • the access point apparatus 402 may comprise or be implemented on an eNB, node B, base station, base transceiver station, and/or other cellular network access point.
  • the access point apparatus 402 may further comprise one or more supporting cellular network nodes or other entities.
  • functionalities attributed to the access point apparatus 402 in accordance with various example embodiments may, in some example embodiments be performed by multiple apparatuses, which may act in concert to provide functionalities attributed to the access point apparatus 402.
  • the access point apparatus 402 may include or otherwise be in communication with processing circuitry 410 that is configurable to perform actions in accordance with one or more example embodiments disclosed herein.
  • the processing circuitry 410 may be configured to perform and/or control performance of one or more functionalities of the access point apparatus 402 in accordance with various example embodiments, and thus may provide means for performing functionalities of the access point apparatus 402 in accordance with various example embodiments.
  • the processing circuitry 410 may be configured to perform data processing, application execution and/or other processing and management services according to one or more example embodiments. In some
  • the access point apparatus 402 or a portion(s) or component(s) thereof, such as the processing circuitry 410 may be embodied as or comprise a chip or chip set.
  • the access point apparatus 402 or the processing circuitry 410 may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard).
  • the structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon.
  • the access point apparatus 402 or the processing circuitry 410 may therefore, in some cases, be configured to implement an embodiment of the invention on a single chip or as a single "system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processing circuitry 410 may include a processor 412 and, in some embodiments, such as that illustrated in FIG. 4, may further include memory 414.
  • the processing circuitry 410 may be in communication with or otherwise control a communication interface 418 and/or a D2D information broadcast controller 420.
  • the processing circuitry 410 may be embodied as a circuit chip (e.g., an integrated circuit chip) configured (e.g., with hardware, software or a combination of hardware and software) to perform operations described herein.
  • the processing circuitry 410 may be embodied as a portion of a server, computer, workstation or other computing device.
  • the processor 412 may be embodied in a number of different ways.
  • the processor 412 may be embodied as various processing means such as one or more of a microprocessor or other processing element, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or the like.
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the processor 412 may comprise a plurality of processors. The plurality of processors may be in operative
  • the plurality of processors may be embodied on a single computing device or distributed across a plurality of computing devices collectively configured to function as the access point apparatus 402.
  • the processor 412 may be configured to execute instructions stored in the memory 414 or otherwise accessible to the processor 412.
  • the processor 412 may represent an entity (e.g., physically embodied in circuitry - in the form of processing circuitry 410) capable of performing operations according to embodiments of the present invention while configured accordingly.
  • the processor 412 when the processor 412 is embodied as an ASIC, FPGA or the like, the processor 412 may be specifically configured hardware for conducting the operations described herein.
  • the processor 412 when the processor 412 is embodied as an executor of software instructions, the instructions may specifically configure the processor 412 to perform one or more operations described herein.
  • the memory 414 may include one or more non- transitory memory devices such as, for example, volatile and/or non-volatile memory that may be either fixed or removable.
  • the memory 414 may comprise a non- transitory computer-readable storage medium.
  • the memory 414 may comprise a plurality of memories.
  • the plurality of memories may be embodied on a single computing device or may be distributed across a plurality of computing devices collectively configured to function as the access point apparatus 402.
  • the memory 414 may be configured to store information, data, applications, instructions or the like for enabling the access point apparatus 402 to carry out various functions in accordance with one or more example embodiments.
  • the memory 414 may be configured to buffer input data for processing by the processor 412. Additionally or alternatively, the memory 414 may be configured to store instructions for execution by the processor 412. As yet another alternative, the memory 414 may include one or more databases that may store a variety of files, contents or data sets. Among the contents of the memory 414, applications may be stored for execution by the processor 412 in order to carry out the functionality associated with each respective application. In some cases, the memory 414 may be in communication with one or more of the processor 412,
  • D2D information broadcast controller 420 via a bus(es) for passing information among components of the access point apparatus 402.
  • the communication interface 418 may include one or more interface mechanisms for enabling communication with other devices and/or networks.
  • the communication interface 418 may include one or more interface mechanisms for enabling communication with other devices and/or networks.
  • the communication interface 418 may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module that may be in communication with the processing circuitry 410.
  • the communication interface 418 may be configured to facilitate over-the-air cellular communications between one or more terminal apparatuses (e.g., the UE1 304, UE2 306, UE3 308, UE4 310, UE5 312, UE6 314, terminal apparatus 502 illustrated in FIG. 5, and/or the like) and the access point apparatus 402.
  • the communication interface 418 may be further configured to facilitate communication with a cellular core network such that data may be communicated between a terminal apparatus and one or more other network- connected apparatuses.
  • the communication interface 418 may accordingly include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network and/or a communication modem or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB), Ethernet or other methods.
  • DSL digital subscriber line
  • USB universal serial bus
  • the processor 412 may be embodied as, include, or otherwise control a D2D information broadcast controller 420.
  • the D2D information broadcast controller 420 may be embodied as various means, such as circuitry, hardware, a computer program product comprising a computer readable medium (for example, the memory 414) storing computer readable program instructions executable by a processing device (for example, the processor 412), or some combination thereof.
  • the D2D information broadcast controller 420 may be capable of communication with one or more of the memory 414 or communication interface 418 to access, receive, and/or send data as may be needed to perform one or more of the
  • FIG. 5 illustrates a block diagram of a terminal apparatus 502 in accordance with some example embodiments.
  • the components, devices or elements illustrated in and described with respect to FIG. 5 below may not be mandatory and thus some may be omitted in certain embodiments. Additionally, some embodiments may include further or different components, devices or elements beyond those illustrated in and described with respect to FIG. 5.
  • the terminal apparatus 502 may comprise an apparatus that may be implemented on terminal apparatus configured for D2D communication.
  • the terminal apparatus 502 may be implemented on a mobile communication device, mobile telephone, personal digital assistant (PDA), smart phone, tablet computing device, pager, laptop computer, desktop computer with a cellular network adapter, portable game device, positioning device, some combination thereof, or the like.
  • the terminal apparatus 502 may, for example, be implemented on the UEl 304, UE2 306, UE3 308, UE4 310, UE5 312, UE6 314, and/or the like.
  • the terminal apparatus 502 may include or otherwise be in communication with processing circuitry 510 that is configurable to perform actions in accordance with one or more example embodiments disclosed herein.
  • the processing circuitry 510 may be configured to perform and/or control performance of one or more functionalities of the terminal apparatus 502 in accordance with various example embodiments, and thus may provide means for performing functionalities of the terminal apparatus 502 in accordance with various example embodiments.
  • the processing circuitry 510 may be configured to perform data processing, application execution and/or other processing and management services according to one or more example embodiments.
  • the terminal apparatus 502 or a portion(s) or component(s) thereof, such as the processing circuitry 510 may be embodied as or comprise a chip or chip set.
  • the terminal apparatus 502 or the processing circuitry 510 may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard).
  • the structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon.
  • the terminal apparatus 502 or the processing circuitry 510 may therefore, in some cases, be configured to implement an embodiment of the invention on a single chip or as a single "system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processing circuitry 510 may include a processor 512 and, in some embodiments, such as that illustrated in FIG. 5, may further include memory 514.
  • the processing circuitry 510 may be in communication with or otherwise control a user interface 516, a communication interface 518, and/or a channel contention controller 520.
  • the processing circuitry 510 may be embodied as a circuit chip (e.g., an integrated circuit chip) configured (e.g., with hardware, software or a combination of hardware and software) to perform operations described herein.
  • the processor 512 may be embodied in a number of different ways.
  • the processor 512 may be embodied as various processing means such as one or more of a microprocessor or other processing element, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or the like.
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the processor 512 may comprise a plurality of processors. The plurality of processors may be in operative
  • the plurality of processors may be embodied on a single computing device or distributed across a plurality of computing devices collectively configured to function as the terminal apparatus 502.
  • the processor 512 may be configured to execute instructions stored in the memory 514 or otherwise accessible to the processor 512.
  • the processor 512 may represent an entity (e.g., physically embodied in circuitry - in the form of processing circuitry 510) capable of performing operations according to embodiments of the present invention while configured accordingly.
  • processor 512 when the processor 512 is embodied as an ASIC, FPGA or the like, the processor 512 may be specifically configured hardware for conducting the operations described herein.
  • the processor 512 when the processor 512 is embodied as an executor of software instructions, the instructions may specifically configure the processor 512 to perform one or more operations described herein.
  • the memory 514 may include one or more non- transitory memory devices such as, for example, volatile and/or non- volatile memory that may be either fixed or removable.
  • the memory 514 may comprise a non- transitory computer-readable storage medium.
  • the memory 514 may comprise a plurality of memories.
  • the plurality of memories may be embodied on a single computing device or may be distributed across a plurality of computing devices collectively configured to function as the terminal apparatus 502.
  • the memory 514 may be configured to store information, data, applications, instructions or the like for enabling the terminal apparatus 502 to carry out various functions in accordance with one or more example embodiments.
  • the memory 514 may be configured to buffer input data for processing by the processor 512. Additionally or alternatively, the memory 514 may be configured to store instructions for execution by the processor 512. As yet another alternative, the memory 514 may include one or more databases that may store a variety of files, contents or data sets. Among the contents of the memory 514, applications may be stored for execution by the processor 512 in order to carry out the functionality associated with each respective application. In some cases, the memory 514 may be in communication with one or more of the processor 512, user interface 516, communication interface 518, or channel contention controller 520 via a bus(es) for passing information among components of the terminal apparatus 502.
  • the user interface 516 may be in communication with the processing circuitry 510 to receive an indication of a user input at the user interface 516 and/or to provide an audible, visual, mechanical or other output to the user.
  • the user interface 516 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen, a microphone, a speaker, and/or other input/output mechanisms.
  • the communication interface 518 may include one or more interface mechanisms for enabling communication with other devices and/or networks.
  • the communication interface 518 may be any means such as a device or circuitry embodied in either hardware, or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the processing circuitry 510.
  • the communication interface 518 may be configured to provide a cellular network interface (e.g., a cellular modem) to enable the terminal apparatus 502 to interface with a cellular network, such as via an access point 302, access point apparatus 402, and/or the like.
  • the communication interface 518 may be configured to provide a wireless network interface (e.g., a WLAN modem and/or the like) to enable the terminal apparatus 502 to engage in D2D
  • the communication interface 518 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN, and/or the like) and/or a wireless communication network (e.g., a cellular network, WSN,
  • communication modem or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB), Ethernet or other methods.
  • DSL digital subscriber line
  • USB universal serial bus
  • the processor 512 may be embodied as, include, or otherwise control a channel contention controller 520.
  • the channel contention controller 520 may be embodied as various means, such as circuitry, hardware, a computer program product comprising computer readable program instructions stored on a computer readable medium (for example, the memory 514) and executed by a processing device (for example, the processor 512), or some combination thereof.
  • the channel contention controller 520 may be capable of communication with one or more of the memory 514, user interface 516, or communication interface 518 to access, receive, and/or send data as may be needed to perform one or more of the functionalities of the channel contention controller 520 as described herein.
  • the D2D information broadcast controller 420 may be configured to cause the access point apparatus 402 to send D2D configuration and control information to one or more terminal apparatuses (e.g., terminal apparatuses 502) that may be served by the access point apparatus 402.
  • this D2D configuration and control information may be broadcast to terminal apparatuses that may be within a coverage area of the access point apparatus 402 and/or may be unicast to one or more individual terminal apparatuses that may be served by the access point apparatus 402.
  • the D2D information broadcast controller 420 may be configured to cause the access point apparatus 402 to broadcast D2D status information related to a status of one or more D2D communication groups within a coverage area of the access point apparatus 402.
  • the D2D status information may, for example, include an identification (ID) one or more terminal apparatuses in a D2D communication group, a media access control (MAC) address of one or more terminal apparatuses in a D2D communication group, transmission-reception (Tx-Rx) timeslot assignment information for a D2D communication group, and/or the like.
  • ID identification
  • MAC media access control
  • Tx-Rx transmission-reception
  • the D2D information broadcast controller 420 may, for example, be configured to cause the access point apparatus 402 to broadcast such status information periodically, responsive to formation of a new D2D communication group, responsive to updating a configuration (e.g., Tx-Rx timeslot assignment) for a D2D communication group, and/or the like.
  • a configuration e.g., Tx-Rx timeslot assignment
  • terminal apparatuses within the coverage area of the access point apparatus 402 may hear the status information.
  • a terminal apparatus 502 that may be within the coverage area of the access point apparatus 402 may be configured to obtain D2D status information that may be broadcast by the access point apparatus 402, such as via a cellular modem that may be implemented on the terminal apparatus 502 in some example
  • terminal apparatuses 502 that want to contend for a channel that may be used for D2D communication among members of a D2D
  • FIG. 6 illustrates an example channel contending mechanism that may be used by terminal apparatuses 502 in accordance with some example embodiments. More particularly, FIG. 6 illustrates an example implementation of a Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) mechanism that may be used by terminal apparatuses contending a channel for collision avoidance in accordance with some example embodiments. It will be appreciated, however, that in some example embodiments, a contention mechanism other than CSMA/CA may be used in addition to or in lieu of CSMA/CA.
  • UEl 602 and UE2 604 may comprise LTE user equipment devices, which may comprise a D2D pairing.
  • the UEl 602 and UE2 604 may each comprise embodiments of a terminal apparatus 502. There may additionally be one or more other terminals 606, which may include LTE UEs, WLAN STAs, and/or the like.
  • the UEl 602 may desire to contend a channel, and may send a message requesting to send data on the channel, such as the RTS (Request to Send) message 608, to the UE2 604.
  • the RTS message 608 may, for example, be sent using WLAN network technology via a WLAN modem.
  • a terminal other than the UE2 604 that hears the RTS message 608 may start a NAV period 620 beginning from a time 610 at which the RTS message 608 was received by the other terminal, and extending for a period indicated in the RTS message 608 during which the channel may be reserved by the UEl 602, which may terminate at the time 612, after which a new round of channel contention may begin.
  • the UE2 604 may receive the RTS message 608 and, following a Short Interframe Space (SIFS) period, may send a clear to send (CTS) message to the UEl 602 in response to the RTS message 608.
  • the CTS message 614 may, for example, be sent using WLAN network technology via a WLAN modem.
  • a terminal other than the UEl 602 that hears the CTS message 614 may set the NAV period 622, which may expire at time 612.
  • the UEl 602 may receive the CTS message 614, and, in response to the CTS message 614, the UEl 602 and UE2 604 may occupy the unlicensed channel for the period during which the channel is reserved by the UEl 602 (e.g., until time 612).
  • the UEl 602 and UE2 604 may engage in D2D communication over the unlicensed channel in accordance with a cellular networking protocol (e.g. LTE protocol) via cellular modems (e.g., LTE modems) that may be implemented on the UEl 602 and UE2 604.
  • a cellular networking protocol e.g. LTE protocol
  • cellular modems e.g., LTE modems
  • the UEl 602 and UE2 604 may engage in D2D communication in alternating Tx-Rx time slots 618.
  • the Tx-Rx time slots may be 1 millisecond (ms) in length.
  • the length of the Tx-Rx time slots may vary in embodiments implemented in non-LTE systems.
  • the Tx-Rx time slots may, for example, be assigned by an access point apparatus 402 that may serve the UEl 602 and UE2 604.
  • some example embodiments enable a terminal 606 that hears the RTS message 608, but not the CTS message 614 to engage in a secondary contention of the channel and occupy the channel concurrently with the UEl 602 and UE2 604.
  • the channel contention controller 520 associated with a terminal apparatus 502 that is a member of a first D2D communication group may be configured to detect (e.g., receive) a message requesting send data on a channel (e.g., an RTS message) sent by a second terminal that is a member of a second D2D communication group.
  • the RTS message may, for example, be heard by a WLAN modem of the terminal apparatus 502.
  • the first and second D2D communication groups may be served by the same access point apparatus 402.
  • the channel contention controller 520 may be configured to determine that the terminal apparatus 502 has not heard a CTS message within the predefined period of time following the terminal apparatus 502 hearing the RTS message.
  • the predefined period of time may, for example, comprise a SIFS period following receipt of the RTS message, during which the channel contention controller 520 may be configured to listen for a CTS message.
  • the channel contention controller 520 may be configured to recognize a situation in which the terminal apparatus 502 hears an RTS message, but does not hear a CTS message as a secondary contention requirement indicator.
  • the channel contention controller 520 may be configured in response to the secondary contention requirement indicator to format a message to another terminal that is paired with the terminal apparatus 502 in the first D2D communication group (e.g., a D2D partner of the terminal apparatus 502) requesting that the D2D partner send data to the terminal apparatus 502 over the channel during the period of time during which the channel is reserved by the terminal that sent the RTS message, which may be indicated in the RTS message.
  • This message may be referred to as a D2D shared band data request (DSBDR) message.
  • DSBDR D2D shared band data request
  • the DSBDR message may include an indication of an identifier of the apparatus 502, such as a UE ID, so as to identify the sender of the DSBDR message to any terminals that receive the DSBDR message.
  • the DSBDR message may include an indicator indicating that the signaling frame is a DSBDR signaling.
  • the channel contention controller 520 may be configured to cause the terminal apparatus 502 to send the DSBDR message to the D2D partner of the terminal apparatus 502,
  • the DSBDR message may be sent over the channel by a cellular modem of the terminal apparatus 502 in accordance with a cellular signaling protocol, such as LTE protocol.
  • the channel contention controller 520 may be configured to cause the terminal apparatus 502 to send the DSBDR message in a random interval of a subframe on the channel.
  • the D2D partner of the terminal apparatus 502 may accordingly listen to the channel during the subframe and detect any DSBDR messages that may be sent by terminals within range during the subframe. Sending the DSBDR message in a random interval of the subframe may, for example, reduce the possibility of collision in the event that multiple terminals hear the RTS message, but not a CTS message, and decide to send DSBDR messages prompting their D2D partners to send data on the channel.
  • the channel contention controller 520 may be configured to determine the random interval.
  • the channel contention controller 520 may be configured to determine the random interval by dividing a period of the subframe (e.g., 1 ms for embodiments implemented in LTE systems) by an amount of time that may be required for the terminal apparatus 502 to send the DSBDR message. The resulting quotient may be floored to derive an integer, N.
  • the channel contention controller 520 may be configured to generate a random integer, , that is uniformly distributed from 0 to N.
  • the channel contention controller 520 may determine the random interval of the subframe to be the i' h time interval of the subframe.
  • the first D2D communication group may occupy the channel during at least a portion of the period of time during which the channel is reserved by the second terminal (e.g., the period of time indicated in the RTS message sent by the second terminal). Accordingly, the first D2D communication group may occupy the channel concurrently with the primary channel occupier (e.g., the second D2D communication group), thus providing for improved channel efficiency and capacity.
  • the channel contention controller 520 may be configured to coordinate
  • the channel contention controller 520 may be configured to use the Tx-Rx timeslot assignment
  • the channel contention controller 520 may know the schedule for the assigned Tx and Rx timeslots of the second terminal based on Tx-Rx timeslot assignment information that may be broadcast by the access point apparatus 402. The channel contention controller 520 may use this knowledge to coordinate transmissions such that the terminal apparatus 502 transmits data to its D2D partner only during the second terminal's Tx timeslot and listens for data that may be sent by the D2D partner during the second terminal's Rx timeslot.
  • the terminal apparatus 502 may avoid transmitting data over the channel during the second terminal's Rx timeslot to avoid interfering with transmissions between members of the second D2D communication group, which is the primary channel occupier.
  • a channel contention controller 520 that may be associated with a terminal receiving a DSBDR message from its D2D partner may be configured whether to send data over the channel to its D2D partner in response to the DSBDR message. If the channel contention controller 520 only detects DSBDR signaling from its D2D partner during a subframe, the channel contention controller 520 may cause the terminal to send data to its partner over the channel during the next subframe.
  • the channel contention controller 520 may be configured to compare a priority that may be associated with each of the received DSBDR messages. If the channel contention controller 520 determines that the DSBDR message sent by the terminal's D2D partner is associated with the highest priority among the received DSBDR messages (e.g., the DSBDR messages received during the subframe), the channel contention controller 520 may cause the terminal to start transmitting data to its D2D partner during the next subframe. If, however, the DSBDR message sent by the terminal's D2D partner is not associated with the highest priority among the received DSBDR messages, the channel contention controller 520 may decline to respond to the DSBDR message sent by its D2D partner.
  • the channel contention controller 520 may decline to respond to the DSBDR message sent by its D2D partner.
  • the priority associated with a DSBDR message may correspond to a predefined priority that may be associated with a terminal that sent the DSBDR message.
  • the priority may, for example, be predefined by the access point apparatus 402.
  • the priority of a terminal may correspond to an identifier for the terminal.
  • the terminal having the smallest UE ID may have the highest priority.
  • the channel contention controller 520 may decline to respond to the DSBDR message sent by its D2D partner. If a DSBDR message is not even heard by the sending terminal's D2D partner, the D2D partner may not respond to the DSBDR message.
  • FIG. 7 illustrates an example of concurrent channel occupation in the case of an exposed terminal in accordance with some example embodiments.
  • FIG. 7 illustrates application of some example embodiments to the exposed terminal scenario illustrated in FIG. 1.
  • the first D2D pair 702 is comprised of the UEl 704 and the UE2 706, and the second D2D pair 708 is comprised of the UE3 710 and UE4 712.
  • the UEl 704, UE2 706, UE3 710, and UE4 712 may each comprise embodiments of a terminal apparatus 502.
  • the cellular network access point serving the first D2D pair 702 and second D2D pair 708 may broadcast status information for the D2D pairs periodically in its coverage area.
  • the status information may, for example, include UE ID information, MAC address information, D2D pair Tx-Rx timeslot assignment information, and/or the like. Accordingly, the D2D pair 702 may know the status information for the second D2D pair 708, and vice versa.
  • the UE3 710 may successfully access the channel according to a contention mechanism, such as a CSMA/CA mechanism, and may send an RTS frame 714 to the UE4 712.
  • the UE4 712 may respond with a CTS message 716, and the D2D pair 708 may occupy the channel and exchange data 718 for a period 720 indicated by the RTS message 714.
  • the UE2 706 is an exposed terminal, as the UE2 706 and UE3 710 are within carrier-sensing range of each other. Accordingly, the RTS message 714 sent by the UE3 710 to the UE4 712 may be heard by the UE2 706. However, the UE2 706 is outside of carrier-sensing range of the UE4 712, and does not hear the CTS message 716 sent by the UE4 712 to the UE3 710 in response to the RTS message 114.
  • the UE2 706 may also wish to contend the channel, but may have lost to the UE3 710 during the channel contention process.
  • the UE2 706 may sense that the channel is busy and determine that it has not heard a CTS message within a predefined period of time (e.g., a SIFS period) subsequent to hearing the RTS message 714. Responsive to this determination, UE2 706 may trigger a secondary channel contention, and may send a DSBDR message 722 to the UEl 704 over the channel.
  • the DSBDR message 722 may be sent during a random time interval in the subframe (e.g., a 1 ms LTE subframe).
  • the UEl 704 may only detect the DSBDR message 722 during the subframe, as indicated by the caption 724.
  • the UEl 704 may accordingly respond to the DSBDR message 722 by transmitting data 726 to the UE2 706 over the channel.
  • the D2D pair 702 may accordingly occupy the channel concurrent with the D2D pair 708 for at least a portion of the period 720 during which the channel is reserved by the UE3 710 in accordance with the time indicated in the RTS message 714.
  • the UE1 704 and UE2 706 may use D2D pair status information (e.g., Tx-RX timeslot assignment information) broadcast by the cellular network access point serving the D2D pair 702 and D2D pair 708 to align the Tx-Rx timeslot of the D2D pair 702 with the Tx- Rx timeslot of the D2D pair 708 so that transmissions on the channel by the D2D pairs do not interfere with each other even though the pairs concurrently occupy the channel.
  • D2D pair status information e.g., Tx-RX timeslot assignment information
  • CSMA/CA a new round of channel contention
  • FIG. 8 illustrates an example of concurrent channel occupation in the case that a clear to send message is not sent in accordance with some example embodiments.
  • FIG. 8 illustrates application of some example embodiments to the scenario illustrated in FIG. 2 in which a CTS message is not sent.
  • the first D2D pair 802 is comprised of the UE1 804 and the UE2 806, and the second D2D pair 808 is comprised of the UE3 810 and UE4 812.
  • the UE1 804, UE2 806, UE3 810, and UE4 812 may each comprise embodiments of a terminal apparatus 502.
  • the cellular network access point serving the first D2D pair 802 and second D2D pair 808 may broadcast status information for the D2D pairs periodically in its coverage area.
  • the status information may, for example, include UE ID information, MAC address information, D2D pair Tx-Rx timeslot assignment information, and/or the like. Accordingly, the D2D pair 802 may know the status information for the second D2D pair 808, and vice versa.
  • the UE3 810 may successfully access the channel according to a contention mechanism, such as a CSMA/CA mechanism, and may send an RTS frame 814 to the UE4 812.
  • a contention mechanism such as a CSMA/CA mechanism
  • the UE4 812 may not respond to the RTS message 814 with a CTS message, such as because the channel is busy or because the UE4 812 cannot hear the RTS message 814.
  • the channel may be occupied prior to the UE3 810 sending the RTS message 814 by communications between the UE4 812 and a WLAN STA 816.
  • the WLAN STA 816 may, for example, obtain access to a WLAN from the WLAN AP 818.
  • the UE2 806 and UE3 810 are within carrier-sensing range of each other. Accordingly, the RTS message 814 sent by the UE3 810 to the UE4 812 may be heard by the UE2 806. However, as the UE4 812 does not send a CTS message, the UE2 806 does not hear a CTS message in response to the RTS message, regardless of whether the UE2 806 is within carrier sensing range of the UE4 812.
  • the UE2 806 may also wish to contend the channel, but may have lost to the UE3 810 during the channel contention process.
  • the UE2 806 may sense that the channel is busy and determine that it has not heard a CTS message within a predefined period of time (e.g., a SIFS period) subsequent to hearing the RTS message 814. Responsive to this determination, UE2 806 may trigger a secondary channel contention, and may send a DSBDR message 822 to the UEl 804 over the channel.
  • the DSBDR message 822 may be sent during a random time interval in the subframe (e.g., a 1 ms LTE subfirame).
  • the UEl 804 may only detect the DSBDR message 822 during the subframe, as indicated by the caption 824. The UEl 804 may accordingly respond to the DSBDR message 822 by transmitting data 826 to the UE2 806 over the channel.
  • the D2D pair 802 may occupy the channel for at least a portion of the period 828 during which the channel is reserved by the UE3 810 in accordance with the time indicated in the RTS message 814.
  • the UE4 812 does not respond to the RTS message 814 with a CTS message
  • the D2D pair 808 does not transmit data on the channel and there is no interference caused by the D2D pair 802 occupying the channel.
  • the UE2 806 may not be able to determine whether it is an exposed terminal and did not hear the CTS (e.g., the example of FIG. 7) or if the CTS was never sent (e.g., the example illustrated in FIG. 8).
  • the UEl 804 and UE2 806 may accordingly use D2D pair status information (e.g., Tx-RX timeslot assignment information) broadcast by the cellular network access point serving the D2D pair 802 and D2D pair 808 to align the Tx-Rx timeslot of the D2D pair 802 with the Tx-Rx timeslot of the D2D pair 808 so that
  • D2D pair status information e.g., Tx-RX timeslot assignment information
  • a new round of channel contention (e.g., CSMA/CA) 830 may begin.
  • FIG. 9 illustrates an example of channel contention and concurrent channel occupation in the case of multiple exposed terminals in accordance with some example embodiments.
  • a first D2D pair is comprised of the UEl 902 and the UE2 904
  • a second D2D pair is comprised of the UE3 906 and UE4 908
  • a third D2D pair comprised of the UE5 910 and UE6 912. All three D2D pairs may be served by the same cellular network access point.
  • the UEl 902, UE2 904, UE3 906, UE4 908, UE5 910, and UE6 912 may each comprise embodiments of a terminal apparatus 502.
  • the cellular network access point serving the D2D pairs illustrated in FIG. 9 may broadcast status information for the D2D pairs periodically in its coverage area.
  • the status information may, for example, include UE ID information, MAC address information, D2D pair Tx-Rx timeslot assignment information, and/or the like. Accordingly, the D2D pairs may know the status information for other D2D pairs in the coverage area of the cellular network access point.
  • the UE3 902 may successfully access the channel according to a contention mechanism, such as a CSMA/CA mechanism, and may send an RTS frame 914 to the UE4 904.
  • the RTS message 914 may be sent using a WLAN modem that may be implemented on the UE3 902,
  • the UE4 904 may receive the RTS message 914 via a WLAN modem that may be implemented on the UE4 904.
  • the UE4 904 may respond with a CTS message 916, which may be sent via a WLAN modem that may be implemented on the UE4 904.
  • the D2D pair comprised of the UE3 902 and UE4 904 may occupy the channel and exchange data for a period 720 that may be indicated by the RTS message 914, which may terminate at time 918.
  • new round of channel contention e.g., CSMA/CA
  • CSMA/CA new round of channel contention
  • the UE1 906 and UE5 910 may comprise exposed terminals, as the UE1 906 and UE5 910 are within carrier-sensing range of the UE3 902. Accordingly, the RTS message 914 may be heard by the UE1 906 and UE5 910, such as by WLAN modems that may be implemented on the UE1 906 and/or UE5 910. However, the UE1 906 and UE5 910 may be outside of carrier-sensing range of the UE4 904, and do not hear the CTS message 916.
  • the UE1 906 and UE5 910 may also wish to contend the channel, but may have lost to the UE3 902 during the channel contention process.
  • the UE1 906 may sense that the channel is busy and determine that it has not heard a CTS message within a predefined period of time (e.g., a SIFS period) subsequent to hearing the RTS message 914. Responsive to this determination, UE1 906 may trigger a secondary channel contention, and may send a DSBDR message 922 to the UE2 908 over the channel (e.g., using a cellular modem, such as an LTE modem).
  • a cellular modem such as an LTE modem
  • the DSBDR message 922 may be sent during a random time interval in the subframe (e.g., a l ms LTE subframe). Further, as illustrated by 924, the UE5 910 may sense that the channel is busy and determine that it has not heard a CTS message within a predefined period of time (e.g., a SIFS period) subsequent to hearing the RTS message 914. Responsive to this determination, UE5 910 may trigger a secondary channel contention, and may send a DSBDR message 926 to the UE6 912 over the channel (e.g., using a cellular modem, such as an LTE modem). The DSBDR message 926 may be sent during a random time interval in the sub frame (e.g., a l ms LTE subframe).
  • a cellular modem such as an LTE modem
  • the UE2 908 may listen to the channel during the subframe to detect any DSBDR messages that may be sent. As illustrated by operation 928, in the example of FIG. 9, the UE2 908 may receive both the DSBDR message 922 and the DSBDR message 926 in the subframe. Since a further DSBDR message (the DSBDR message 926) was received during the subframe in addition to the DSBDR message 922 from the D2D partner of the UE2 908, the UE2 908 may determine which of the received DSBDR messages is associated with the highest priority. In the example illustrated in FIG. 1, the UE1 906 has a higher priority than the UE5 910.
  • the UE2 908 may determine to respond to the DSBDR message 922 by sending data 930 to the UE1 906 over the channel in the next subframe.
  • the D2D pair comprised of the UE1 906 and UE2 908 may occupy the channel concurrent with the D2D pair comprised of the UE3 902 and UE4 904 for at least a portion of the period during which the channel is reserved by the UE3 710 in accordance with the time indicated in the RTS message 914 (e.g. up till the time 920).
  • the UE1 906 and UE2 908 may use D2D pair status information (e.g., Tx-RX timeslot assignment information) broadcast by the serving cellular network access point to align their Tx-Rx timeslots with the Tx-Rx timeslot of the D2D pair comprised of the UE3 902 and UE4 904 so that transmissions on the channel by the D2D pairs do not interfere with each other even though the pairs concurrently occupy the channel.
  • D2D pair status information e.g., Tx-RX timeslot assignment information
  • the UE6 912 may also listen to the channel during the subframe to detect any DSBDR messages that may be sent. As illustrated by operation 932, in the example of FIG. 9, the UE6 912 may receive both the DSBDR message 922 and the DSBDR message 926 in the subframe. Since a further DSBDR message (the DSBDR message 922) was received during the subframe in addition to the DSBDR message 926 from the D2D partner of the UE6 912, the UE6 912 may determine which of the received DSBDR messages is associated with the highest priority. In the example illustrated in FIG. 1 , the UE1 906 has a higher priority than the UE5 910. Accordingly, the UE6 912 may determine to not respond to the DSBDR message 926.
  • a CTS message 916 is sent by the UE4 904, but not heard by the UE1 906 and UE5 910
  • secondary channel contention may be proceed in a manner substantially similar to that illustrated in FIG. 9 in an alternative scenario in which the UE4 904 does not send a CTS message 916 in response to the RTS message 914.
  • both the UE1 906 and the UE5 910 may opt to trigger a secondary channel contention responsive to not hearing a CTS message within a predefined period of time after hearing the RTS message 914.
  • FIG. 10 illustrates a flowchart according to an example method for facilitating concurrent occupation of a channel according to some example embodiments.
  • FIG. 10 illustrates operations that may be performed at a terminal apparatus 502.
  • the operations illustrated in and described with respect to FIG. 10 may, for example, be performed by, with the assistance of, and/or under the control of one or more of the processing circuitry 510, processor 512, memory 514, communication interface 518, or channel contention controller 520.
  • Operation 1000 may comprise determining, at a first terminal that is a member of a first device-to-device (D2D) communication group, that the first terminal has not heard a clear to send message within a predefined period of time following the first terminal hearing a message requesting to send data on a channel sent by a second terminal that is a member of a second D2D communication group.
  • the processing circuitry 510, processor 512, memory 514, communication interface 518, and/or channel contention controller 520 may, for example, provide means for performing operation 1000.
  • Operation 1010 may comprise determining, responsive to the determination of operation 1000, to format and send a DSBDR message to a third terminal requesting the third terminal to send data to the first terminal over the channel during a period of time during which the channel is reserved by the second terminal.
  • the third terminal may be a member of the first D2D communication group.
  • the processing circuitry 510, processor 512, memory 514, communication interface 518, and/or channel contention controller 520 may, for example, provide means for performing operation 1010.
  • the method may further comprise operation 1020, which may comprise receiving, at the first terminal, data sent by the third terminal over the channel in response to the DSBDR message.
  • the processing circuitry 510, processor 512, memory 514, communication interface 518, and/or channel contention controller 520 may, for example, provide means for performing operation 1020.
  • the method may further comprise operation 1030, which may comprise occupying the channel during at least a portion of the period of time during which the channel is reserved by the second terminal.
  • operation 1030 may further comprise using Tx- Rx timeslot assignment information for the second D2D communication group that may be broadcast by a serving cellular network access point to coordinate transmissions on the channel by the first D2D communication group to avoid interfering with any communications that may be sent over the channel by the second D2D communication group.
  • the processing circuitry 510, processor 512, memory 514, communication interface 518, and/or channel contention controller 520 may, for example, provide means for performing operation 1030.
  • FIG. 11 illustrates a flowchart according to another example method for facilitating concurrent occupation of a channel according to some example embodiments.
  • FIG. 1 1 illustrates operations that may be performed at a terminal apparatus 502.
  • the operations illustrated in and described with respect to FIG. 10 may, for example, be performed by, with the assistance of, and/or under the control of one or more of the processing circuitry 510, processor 512, memory 514, communication interface 518, or channel contention controller 520.
  • Operation 1100 may comprise receiving, at a first terminal, a DSBDR message sent by a second terminal that is a D2D partner of the first terminal in a D2D communication group.
  • the processing circuitry 510, processor 512, memory 514, communication interface 518, and/or channel contention controller 520 may, for example, provide means for performing operation 1100.
  • Operation 1110 may comprise determining, at the first terminal, whether to respond to the DSBDR message sent by the second terminal. In an instance in which the first terminal only detects DSBDR signaling from the second terminal during a subframe, operation 1110 may comprise the first terminal determining to respond to the DSBDR message by sending data to the second terminal over the channel during the next subframe.
  • operation 1110 may comprise the first terminal comparing a priority that may be associated with each of the received DSBDR messages and determining which of the received DSBDR messages is associated with the highest priority. If the first terminal determines that the DSBDR message sent by the second terminal is associated with the highest priority among the received DSBDR messages, the first terminal may determine to respond to the DSBDR message by sending data to the second terminal over the channel during the next subframe.
  • the first terminal may decline to respond to the DSBDR message sent by the second terminal.
  • the operation 1 1 10 may comprise the first terminal determining to decline to respond to the DSBDR message sent by the first terminal.
  • the processing circuitry 510, processor 512, memory 514, communication interface 518, and/or channel contention controller 520 may, for example, provide means for performing operation 1110.
  • FIGS. 10-1 1 are flowcharts of a system, method and program product according to example embodiments of the invention. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device of an apparatus employing an
  • any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus provides for implementation of the functions specified in the flowcharts block(s).
  • These computer program instructions may also be stored in a non-transitory computer-readable storage memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage memory produce an article of manufacture the execution of which implements the function specified in the flowcharts block(s).
  • the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowcharts block(s).
  • blocks of the flowcharts support combinations of means for perfom ing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware- based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions. [0097] Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé permettant de faciliter l'occupation simultanée d'un canal. Le procédé peut consister à déterminer, au niveau d'un premier terminal qui est un élément d'un premier groupe de communication de dispositif à dispositif (D2D), que le premier terminal n'a pas entendu un message « envoi autorisé » dans une période de temps prédéfinie suite à l'écoute d'un message par le premier terminal demandant d'envoyer des données sur un canal envoyé par un deuxième terminal qui est un élément d'un second groupe de communication D2D. Le procédé peut en outre consister à déterminer, en réponse à la détermination que le premier terminal n'a pas entendu un message « envoi autorisé » dans la période de temps prédéfinie suite à l'écoute du message par le premier terminal demandant d'envoyer des données sur le canal, de formater et d'envoyer un message de demande de données de bande partagée D2D (DSBDR) devant être envoyé à un troisième terminal. L'invention concerne également un appareil correspondant et un produit de programme informatique.
PCT/CN2012/070521 2012-01-18 2012-01-18 Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal Ceased WO2013107004A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/070521 WO2013107004A1 (fr) 2012-01-18 2012-01-18 Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/070521 WO2013107004A1 (fr) 2012-01-18 2012-01-18 Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal

Publications (1)

Publication Number Publication Date
WO2013107004A1 true WO2013107004A1 (fr) 2013-07-25

Family

ID=48798495

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/070521 Ceased WO2013107004A1 (fr) 2012-01-18 2012-01-18 Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal

Country Status (1)

Country Link
WO (1) WO2013107004A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3046365A4 (fr) * 2013-11-01 2016-10-12 Huawei Device Co Ltd Procédé d'accès à la communication et équipement utilisateur
WO2021047285A1 (fr) 2019-09-13 2021-03-18 Qualcomm Incorporated Commande de puissance d'interférence pour communications de liaison latérale
US20230027444A1 (en) * 2021-07-26 2023-01-26 Cisco Technology, Inc. Over-the-wire access point coordination

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010139847A1 (fr) * 2009-06-04 2010-12-09 Nokia Corporation Marquage efficace de sous-trames basé sur une transmission de dispositif à dispositif dans des spectres cellulaires de liaison descendante
WO2011069295A1 (fr) * 2009-12-11 2011-06-16 Nokia Corporation Procédé, appareil et produit programme d'ordinateur pour l'allocation de ressources dans un réseau de communication sans fil
WO2011088609A1 (fr) * 2010-01-19 2011-07-28 Nokia Corporation Réutilisation de ressource centralisée commandée par nœud b évolué pour utilisateurs de communication de dispositif à dispositif et cellulaires
WO2011110732A1 (fr) * 2010-03-09 2011-09-15 Nokia Corporation Protocole avec réutilisation spatiale améliorée

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010139847A1 (fr) * 2009-06-04 2010-12-09 Nokia Corporation Marquage efficace de sous-trames basé sur une transmission de dispositif à dispositif dans des spectres cellulaires de liaison descendante
WO2011069295A1 (fr) * 2009-12-11 2011-06-16 Nokia Corporation Procédé, appareil et produit programme d'ordinateur pour l'allocation de ressources dans un réseau de communication sans fil
WO2011088609A1 (fr) * 2010-01-19 2011-07-28 Nokia Corporation Réutilisation de ressource centralisée commandée par nœud b évolué pour utilisateurs de communication de dispositif à dispositif et cellulaires
WO2011110732A1 (fr) * 2010-03-09 2011-09-15 Nokia Corporation Protocole avec réutilisation spatiale améliorée

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3046365A4 (fr) * 2013-11-01 2016-10-12 Huawei Device Co Ltd Procédé d'accès à la communication et équipement utilisateur
US10039135B2 (en) 2013-11-01 2018-07-31 Huawei Device (Dongguan) Co., Ltd. Communication access method and user equipment
WO2021047285A1 (fr) 2019-09-13 2021-03-18 Qualcomm Incorporated Commande de puissance d'interférence pour communications de liaison latérale
US12289749B2 (en) 2019-09-13 2025-04-29 Qualcomm Incorporated Interference power control for sidelink communications
US20230027444A1 (en) * 2021-07-26 2023-01-26 Cisco Technology, Inc. Over-the-wire access point coordination
US11729762B2 (en) * 2021-07-26 2023-08-15 Cisco Technology, Inc. Over-the-wire access point coordination
US20230328717A1 (en) * 2021-07-26 2023-10-12 Cisco Technology, Inc. Over-the-wire access point coordination
US12160859B2 (en) * 2021-07-26 2024-12-03 Cisco Technology, Inc. Over-the-wire access point coordination

Similar Documents

Publication Publication Date Title
CN113068214B (zh) 无线通信中受限制的多链路设备操作的方法
US9461792B2 (en) Signaling and procedure design for cellular cluster contending on license-exempt bands
CN110856271B (zh) 设备到设备终端的资源分配方法和装置
US10064230B2 (en) Methods and devices enabling resource sharing for device-to-device communication in unlicensed band
US10917914B2 (en) Media access control for license-assisted access
JP7270541B2 (ja) 共有スペクトル上の周波数分割多重（ｆｄｍ）ベースの媒体アクセスのための技法および装置
US20150201401A1 (en) Radio resource reservation in framed communication system
EP3211924A1 (fr) Procédé et dispositif pour le partage de ressources entre stations dans un réseau local sans fil
WO2013160523A1 (fr) Découverte réseau dans un réseau sans fil
CN104717750A (zh) 一种信号传输方法及装置
CN105917720B (zh) 无线通信方法、接入点和站点
US20240251438A1 (en) Channel access method, and device and storage medium
US20230354377A1 (en) Sidelink communications in wireless network
CN107295567A (zh) 一种基于帧结构的无限资源冲突检测方法
WO2016171595A1 (fr) Commande d'accès à un support radio pour communication sans fil
US20240340952A1 (en) Channel access techniques in a multi-hop framework for ultra-high reliability
CN104918255A (zh) 用于一无线通讯系统的装置对装置使用者装置及其资源排程方法
WO2013107004A1 (fr) Procédé et appareil permettant de faciliter l'occupation simultanée d'un canal
CN105850217B (zh) 预留信道的方法及通信设备
CN109688628B (zh) 信号传输方法、相关装置及系统
JP2023505642A (ja) 情報伝送方法及び関連製品
JP7041344B2 (ja) ネットワーク制御装置、及びスロット割り当て方法
US20250119829A1 (en) Multi-hop support for coordinated medium access
KR101913261B1 (ko) 무선통신시스템에서 신호 송수신 방법
EP4351247A1 (fr) Procédé et appareil de sélection de ressources

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12865769

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12865769

Country of ref document: EP

Kind code of ref document: A1