RU2682370C2 - Half duplex fdd wtru with single oscillator - Google Patents

Abstract

FIELD: wireless communication equipment.SUBSTANCE: invention relates to the field of wireless communication. For this purpose, the method involves: determining, on the basis of the priority rule, a subframe to process from an uplink subframe and a subframe of a scheduled downlink transmission, moreover, the uplink subframe and the scheduled downlink transmission subframe conflict with each other; and processing a half duplex with single oscillator wireless transmission/reception unit (HD-SO-WTRU) of a specific subframe; moreover, the priority rules indicate that the downlink has a higher priority than the uplink.EFFECT: technical result – reduction of switching time between the uplink and downlink lines of communication in the case of using only one oscillator, which is beneficial for reducing costs in the production of MTC devices, but which requires an increase in the above time compared with the use of more than one oscillator.16 cl, 16 dwg

Description

FIELD OF TECHNOLOGY

[0001] The present application relates to the field of wireless communications.

BACKGROUND

[0002] Machine-type communications (MTC) may continue to evolve in the foreseeable future as wireless technology continues to progress. Today, many MTC devices are designed for low-level applications (low cost, low data rate) that are processed using GSM / GPRS networks. Migration of MTC devices in an LTE (Long Term Evolution) network is an attractive alternative to reduce the need for operators to continue to support networks with various radio access technologies, as well as increase spectrum utilization. In order to make migration more attractive, MTS devices must have been inexpensive.

[0003] Low-cost MTC devices have been proposed that utilize half-duplex frequency division duplex (HD-FDD). In accordance with the desire to reduce the cost, one oscillator can be used, which will be less expensive to produce, but may take time to switch between an uplink and a downlink.

SUMMARY OF THE INVENTION

A method is described that is performed in a half-duplex single oscillator wireless transmit / receive unit (HD-SO-WTBU) for processing subframes. The HD-SO-WTRU determines whether to process the first subframe or second subframe based on a priority rule, wherein the first and second subframes are adjacent, and at least one of the subframes is defined as an uplink subframe. The HD-SO-WTRU uses at least a portion of a subframe that it does not process to switch the frequency of its oscillator from the uplink direction frequency to the downlink direction frequency, or vice versa.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] A more detailed understanding can be obtained from the following description, given as an example in conjunction with the attached drawings, in which:

[0005] FIG. 1A is a block diagram of an exemplary communication system in which one or more of the disclosed embodiments may be implemented;

[0006] FIG. 1B is a block diagram of an example wireless transmit / receive unit (WTRU) that can be used in the communication system shown in FIG. 1A.

[0007] FIG. 1C is a block diagram of an example radio access network and an example core network that can be used in the communication system shown in FIG. 1A.

[0008] FIG. 2 is a flowchart illustrating an exemplary process of indicating a base station for half-duplex single-oscillator WTRU frequency division duplex communication (SO-HD-FDD WTRU);

[0009] FIG. 3 is a timing diagram that illustrates transmissions based on two exemplary HARQ processes for SO-HD-FDD WTRU;

[0010] FIG. 4 is a timing chart that illustrates a shift of an exemplary HARQ process of an SO-HD-FDD WTRU;

[0011] FIG. 5 is a timing chart that illustrates an exemplary HARQ process according to the number of oscillators for an HD-FDD WTRU; and

[0012] FIG. 8 is a timing chart that illustrates an example PDCCH only subframe for SO-HD-FDD WTRU,

[0013] FIG. 7 is a flowchart illustrating an exemplary conflict processing process for an SO-HD-FDD WTRU.

[0014] FIG. 8 is a flowchart illustrating an alternative example of a conflict processing process for an SO-HD-FDD WTRU involving a second previous subframe.

[0015] FIG. 9 is a flowchart that illustrates another alternative example of a conflict processing process for an SO-HD-FDD WTRU using the first previous adjacent subframe.

[0016] FIG. 10 is a timing chart that illustrates an example partial ignore scheme for an SO-HD-FDD WTRU,

[0017] FIG. 11 is a timing chart that illustrates the timing (timing) of a transmission without using packet transmissions.

[0018] FIG. 12 is a timing chart that illustrates timing of transmission with packet transmissions, as can be applied to 2 downlink transmissions,

[0019] FIG. 13 is a timing chart that illustrates timing of transmission with packet transmissions, as can be applied to 6 downlink transmissions.

[0020] FIG. 14 is a timing chart that illustrates timing of transmission with packet transmissions, as can be applied to 10 downlink transmissions.

DETAILED DESCRIPTION

[0021] FIG. 1A is a schematic representation of an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., for a variety of wireless users. Communication system 100 may allow multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, communication systems 100 may use one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), etc.

[0022] As shown in FIG. 1A, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and others network 112, although it should be understood that the disclosed embodiments allow any number of WTRUs, base stations, networks and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. As an example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and / or receive wireless signals, and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cell phone, personal digital assistant (PDA), smartphone, machine-type communication device (MTS), laptop, netbook, personal computer, wireless sensor, consumer electronics, etc.

[0023] Communication systems 100 may also include a base station 114a and a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to communicate wirelessly with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as core network 106, the Internet 110 and / or other networks 112. As an example, base stations 114a, 114b may be a base transceiver station (BTS), Node B (Node B), eNode B, home Node B, home eNode B, station controller, access point ( AP), wireless router, etc. While the base stations 114a, 114b are depicted, each as one element should be taken into account that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0024] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), radio network controller (RNC), relay nodes, and so on. .d. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals within a specific geographic region, which may be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, for example, one for each sector of the cell. In another embodiment, base station 114a may utilize multiple input multiple output (MIMO) technology and, therefore, may use multiple transceivers for each sector of the cell.

[0025] Base stations 114a, 114b may communicate with one or more of the WTRUs, 102a, 102b, 102c, 102d via a radio interface 116, which may be any suitable wireless link (eg, radio frequency (RF), microwave, infrared (IR) ), ultraviolet (UF), visible light, etc.). The radio interface 116 may be established using any suitable radio access technology (RAT).

[0026] More specifically, as noted above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, base station 114a in RAN 104 and WTRUs 102a, 102b, 102c may implement a radio technology such as Terrestrial Radio Access (UTRA) of the Universal Mobile Telecommunication System (UMTS), which can establish a radio interface 116 using Broadband CDMA (WCDMA). WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Advanced HSPA (HSPA +). HSPA may include high speed downlink packet access (HSDPA) and / or high speed uplink packet access (HSUPA).

[0027] In another embodiment, the base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as UMTS Evolved Terrestrial Radio Access (E-UTRA), which may establish a radio interface 116 using Long Term Evolution (LTE) and / or Developed LTE (LTE-A).

[0028] In other embodiments, the base station 114a and the WTRU 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (eg, worldwide compatibility for microwave access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Increased Data Transfer Rates for GSM Development (EDGE), GSM EDGE (GERAN ) etc.

[0029] The base station 114b in FIG. 1A can be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and can use any suitable RAT to facilitate wireless communications in a localized area, such as a business, home, vehicle, campus, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 1A, base station 114b may have a direct connection to the Internet 110. Thus, base station 114b may not be required to access the Internet 110 through the core network 106.

[0030] RAN 104 may communicate with a core network 106, which may be any type of network configured to transmit voice, data, applications and / or voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, 102d. For example, core network 106 may provide call control, billing services, location-based mobile services, paid calls, Internet connections, video distribution, etc. and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it should be borne in mind that RAN 104 and / or core network 106 may be in direct or indirect communication with other RANs that use the same RAT as RAN 104, or a different RAT. For example, in addition to connecting to RAN 104, which can be implemented using E-UTRA radio technology, core network 106 can also communicate with another RAN (not shown) using GSM radio technology.

[0031] The core network 106 may also serve as a gateway to the WTRU, 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110 and / or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide a simple old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the Internet Protocol TCP / IP stack. Networks 112 may include wired or wireless networks owned and / or operated by other service providers. For example, networks 112 may include another core network connected to one or more RANs that may use the same RAT as RAN 104, or a different RAT.

[0032] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode functionality, for example, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communication with various wireless networks over various wireless lines. For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may use cellular radio technology, and with a base station 114b, which may use IEEE 802 radio technology.

[0033] FIG. 1B is a block diagram of an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transceiver element 122, a speaker / microphone 124, a keyboard 126, a display / touch panel 128, a non-removable memory 130, a removable memory 132, a power supply 134, a chipset 136 of a global positioning system ( GPS) and other peripheral devices 138. It should be borne in mind that the WTRU 102 may include any sub-combination of the above elements, while maintaining compliance with the embodiment.

[0034] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, application specific integrated circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), state machine, etc. The processor 118 may perform signal encoding, data processing, power control, I / O processing and / or any other functionality that allows the WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transceiver element 122. Although FIG. 1B shows the processor 118 and the transceiver 120 as separate components, it should be borne in mind that the processor 118 and the transceiver 120 can be combined with each other in an electronic circuit package or chip.

[0035] The transceiver element 122 may be configured to transmit signals to, or receive signals from, a base station (eg, base station 114a) via a radio interface 116. For example, in one embodiment, the transceiver element 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transceiver element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transceiver element 122 may be configured to transmit and receive both RF and light signals. It should be borne in mind that the transceiver element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0036] Furthermore, although the transceiver element 122 is depicted in FIG. 1B, as a single element, the WTRU 102 may include any number of transceiver elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transceiver elements 122 (eg, multiple antennas) for transmitting and receiving wireless signals through a radio interface 116.

[0037] The transceiver 120 may be configured to modulate the signals to be transmitted by the transceiver element 122 and to demodulate the signals that are received by the transceiver element 122. As noted above, the WTRU 102 may have multi-mode functionality. Thus, the transceiver 120 may include multiple transceivers to allow the WTRU 102 to communicate via several RATs, such as, for example, UTRA and IEEE 802.11.

[0038] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keyboard 126 and / or a display / touch panel 128 (for example, a display unit on a liquid crystal display (LCD) or a display unit on organic light emitting diodes (OLED)) and may accept user input from them. The processor 118 may also output user data to a speaker / microphone 124, a keyboard 126, and / or a display / touch panel 128. In addition, the processor 118 can access information from, and store data in, any type of memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. Removable memory 132 may include a Subscriber Identity Module (SIM), memory card, Secure Digital (SD) memory card, and the like. In other embodiments, the processor 118 can access information from, and store the data in, a memory that is not physically located on the WTRU 102, but, for example, on a server or home computer (not shown).

[0039] The processor 118 may receive power from a power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry batteries (such as nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar panels, fuel cells, etc.

[0040] The processor 118 may also be coupled to the GPS 136 chipset, which may be configured to provide location information (eg, latitude and longitude) relative to the current location of the WTRU 102. In addition to, or instead of, information from the GPS 136 chipset, The WTRU 102 may receive location information via a radio interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on synchronization signals received from two or more neighboring base stations. It should be borne in mind that the WTRU 102 may obtain location information by any suitable location method, while maintaining compliance with the embodiment.

[0041] The processor 118 may further be connected to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless communications. For example, peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a speakerphone, a Bluetooth® module, a frequency -modulated (FM) radio, digital music player, multimedia player, video game player module, Internet browser, etc.

[0042] FIG. 1C is a block diagram of a RAN 104 and a core network 106 in accordance with an embodiment. As noted above, the RAN 104 may use the E-UTRA radio technology to communicate with the WTRU 102a, 102b, 102c via the radio interface 116. The RAN 104 may also communicate with the core network 106.

[0043] RAN 104 may include eNode-B 140a, 140b, 140c, although it should be understood that RAN 104 may include any number of eNode-B, while maintaining compliance with the embodiment. The eNode-B 140a, 140b, 140c may include, each, one or more transceivers for communicating with the WTRU 102a, 102b, 102c via the radio interface 116. In one embodiment, the eNode-B 140a, 140b, 140c may implement MIMO technology. Thus, the eNode-B 140a, for example, can use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0044] Each of the eNode-B 140a, 140b, 140c may be associated with a specific cell (not shown) and may be configured to process radio resource management decisions, handover decisions, uplink user scheduling, and / or downlink, etc. As shown in FIG. 1C, eNode-B 140a, 140b, 140c may communicate with each other via the X2 interface.

[0045] The core network 106 shown in FIG. 1C, may include a mobility management entity (MME) gateway 132, a serving gateway 144, and a packet data network (PDN) gateway 146. Although each of the above elements is depicted as part of a core network 106, it should be appreciated that one of these elements may be owned and / or operated by an entity other than the core network operator.

[0046] MME 142 can be connected to each of the eNode-B 140a, 140b, 140c in the RAN 104 via the S1 interface and can serve as a control node. For example, MME 142 may be responsible for authenticating users of the WTRU 102a, 102b, 102c, activating / deactivating the bearer channel, selecting a particular serving gateway during the initial connection of the WTRU 102a, 102b, 102c, and the like. MME 142 may also provide a control plane function for switching between RAN 104 and other RANs (not shown) that use other radio technologies such as GSM or WCDMA.

[0047] A serving gateway 144 may be connected to each of the eNode B 140a, 140b, 140c in the RAN 104 via the S1 interface. Serving gateway 144 may generally route and forward user data packets to / from WTRU 102a, 102b, 102c. Serving gateway 144 may also perform other functions, such as linking the user plane during handover (handover) between the eNode B, launching a paging call with downlink data for the WTRU 102a, 102b, 102c, managing and storing the contexts of the WTRU 102a, 102b , 102s, etc.

[0048] The serving gateway 144 can also be connected to a PDN gateway 146 that can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communication between WTRUs, 102a, 102b, 102c and IP devices.

[0049] The core network 106 may facilitate communication with other networks. For example, core network 106 may provide WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communication between WTRUs 102a, 102b, 102c and legacy landline communication devices. For example, core network 106 may include or can communicate with an IP gateway (eg, an IP multimedia subsystem (IMS) server) that serves as an interface between core network 106 and PSTN 108. In addition, core network 106 can provide WTRUs 102a, 102b, 102c with access to networks 112, which may include other wired and wireless networks that are owned and / or operated by other service providers.

[0050] As the development of LTE technology and the evolution of its network deployment, network operators may wish to reduce the cost of overall network support. One way to achieve this goal can be to minimize the number of different radio access technologies used in deploying and maintaining the network, for example, gradually replacing the old radio access technology network (e.g. GSM GPRS) with a radio access technology network with higher spectrum efficiency (e.g. LTE) .

[0051] One example of the application of wireless technology may be machine-type communication (MTC). MTS is a market that can continue to expand in the foreseeable future as wireless technology advances. Today, many MTC devices target low-level applications (low cost, low data rate) that are processed using the GSM / GPRS network. Due to the low cost of operations with the MTS device, there may be a containment of motivation for the migration of MTS to the new LTE network. Such reluctance to switch to LTE can cost network operators not only in terms of maintaining multiple RATs, but also in terms of preventing operators from maximizing their spectrum (for example, given the non-optimal spectral efficiency of GSM / GPRS). Given the likelihood of a high number of MTS devices, the total spectral resources necessary for such devices to provide services in GSM / GPRS can be significant and ineffectively assigned.

[0052] Thus, it may be preferable to find a cost-effective LTE solution that can provide clear commercial benefits for MTC device providers and operators to enable the migration of low-level MTC devices from GSM / GPRS networks to LTE networks. The terms LTE and LTE Evolved (LTE-A) can be used interchangeably.

[0053] A cheap MTS device may include, but is not limited to reducing the overall ability and functionality of a WTRU, including lower data rate, lower power consumption, and simpler implementation. Among other things, approaches to reduce implementation complexity may include reducing the number of RF components for these devices. This can be achieved by supporting a reduced number of radio access technologies (RATs) or RF circuits. Other approaches may include reducing the maximum applicable UL transmit power for such a device, reducing the maximum supported Rx or Tx channel bandwidth, or supporting (or operating) the half-duplex FDD mode (for example, only).

[0054] With the introduction of low-cost MTS devices in the network, it may be necessary to maintain a service area, and it may be preferable that their introduction does not lead to a problem in terms of achievable spectral efficiency during operation. It may also be beneficial for low-cost MTS devices introduced into the network to be interoperable with legacy LTE WTRUs, so that both legacy and modern devices may be able to communicate on a carrier in the same network. In addition, it may be preferable for low-cost MTC devices to support mobility and roaming.

[0055] The half-duplex operation may allow the LC-MTC device, which can be classified as category 0 WTRU, to use switching rather than duplex communication, so that implementation costs can be significantly reduced. In order to further reduce costs relative to the half-duplex mode of the LC-MTC device, one oscillator can be used for the frequencies or frequency ranges of the uplink and downlink.

[0056] Half-duplex operation was supported for conventional LTE devices, which can be classified as category 1 ~ 6 WTRUs for which separate oscillators for uplink and downlink frequency bands were used or assumed. For these devices, a relatively short maximum switching time (for example, 20 μs), which may include oscillator tuning time, can be used or anticipated in system design. When a single oscillator is used for the frequency ranges of both the uplink and the downlink, for example, in an LC-MTC device using half-duplex mode, it may be necessary to take into account the additional setup time of the oscillator, which can lead to a longer maximum switching time , for example, up to 1 ms. For an HD-FDD operation with a maximum timing advance of, for example, 0.67 ms, the total switching time may be the oscillator switching time plus timing advance, for example, 1.67 ms.

[0057] Provided that a significantly longer switching time (eg, 1.67 ms) may need to be considered for switching from downlink to uplink (Rx-to-Tx) and / or from uplink to downlink communications (Tx-to-RX), the eNB scheduler may need to know whether an LC-MTC device with half-duplex functionality with one oscillator or two oscillators is implemented. If traffic (e.g., unicast traffic) is planned in any direction during the switching time, the HD-FDD WTRU with one oscillator may not receive or transmit in the same or adjacent subframes. If the uplink and downlink signals are located or scheduled in the same subframe or adjacent subframes, the single-oscillator HD-FDD WTRU may not transmit the uplink signal or may not receive the downlink signal, and adjacent subframes may include self subframes during switching time. If the uplink and downlink signals are in the same subframe or adjacent subframes, the behavior of the WTRU may become undefined. There may be ambiguity from the point of view of the eNB scheduler, and the spectral efficiency can be significantly degraded due to too long switching times.

[0058] The scheduled traffic or scheduled transmission may be a transmission or resources for which scheduling has been provided (for example, in DCI format) or for which resources have been assigned (for example, for or due to HARQ retransmission or semi-persistent scheduling (SPS)). The terms “planned” and “intended” can be used interchangeably. PUSCH and PDSCH can be scheduled or scheduled transmissions. One or more of the PUCCH, SRS, and PRACH transmissions may be considered as scheduled or scheduled uplink transmissions. EPDCCH may be considered as scheduled or scheduled downlink transmissions. Scheduled downlink transmissions may include broadcast, paging, and / or other system signals or channels.

[0059] Uplink subframe processing or uplink subframe processing may include transmitting, such as transmitting one or more signals and / or channels in a subframe. Processing the downlink subframe or processing the subframe for the downlink may include one or more of receiving and / or decoding one or more signals and / or channels in the subframe. A subframe may be processed for at least one of the uplink and the downlink, or may not be processed. For example, the subframe used for switching may not be processed for the uplink and downlink. In another example, the lack of processing of a subframe may include a lack of reception and transmission in the subframe.

[0060] Hereinafter, the terms HD-FDD LC-MTS WTRU with one oscillator, Category 0 WTRU with one oscillator and HD-FDD WTRU with one oscillator, SO-HD-FDD WTRU can be used interchangeably. Also, dual oscillator HD-FDD WTRUs and DO-HD-FDD WTRUs may be used interchangeably and may include Category 0 WTRUs with HD-FDD functionality and other WTRU categories with HD-FDD functionality. As mentioned above, the WTRU may include user equipment (UE).

[0061] An adjacent subframe may be used for switching time. For example, if subframe n is used for the downlink, and subframe n + 4 is used or should be used for uplink transmission, subframes n + 2 and n + 3 can be considered as adjacent subframes that can be used for switching time. An SO-HD-FDD WTRU may not receive or transmit in an adjacent subframe, for example, because adjacent subframes may be used by the WTRU to perform a handoff. For example, if two subframes are needed or used, for example, by a WTRU to perform switching, subframes n-2, n-1, n + 1 and n + 2 can be used for switching if subframe n is used or specified for the opposite direction. In another example, if one subframe (or at least part of one subframe) is needed or used by the WTRU to perform a switch, then at least one of the subframes n-1 and n + 1 can be used for switching. Subframe n-1 and / or n + 1 can be used for switching if subframe n is used or defined for the opposite direction (for example, from subframe n-1 and / or n + 1). In another example, subframes n-2 and n-1 may be used for switching if subframe n is used or specified for the opposite direction.

[0062] In another example, if a subframe n is scheduled for an uplink, and a subframe n-1 (or n + 1) is not scheduled for an uplink, if the uplink has a higher priority than the downlink, then the WTRU may perform the scheduled transmission in subframe n and may not receive or try to receive signals or downlink channels in subframe n-1 (or n + 1), for example, regardless of whether subframe n-1 (or n + 1) can be scheduled for downlink transmission via eNB. If the WTEU is not yet tuned to the uplink frequency in (e.g., at the beginning) the n-1 subframe, then the WTRU may use at least a portion of the n-1 subframe for the switching time to tune the oscillator to the uplink frequency.

[0063] The WTRU may consider a subframe as an uplink subframe if it has scheduled or assigned uplink resources (or scheduled or scheduled uplink transmission) in the subframe or for the subframe. The WTRU may use (for example, for reception) and / or consider a subframe as a downlink subframe if the WTRU does not have scheduled or assigned resources (or scheduled or intended transmission) in or for the uplink in this subframe.

[0064) Hereinafter, the terms “adjacent subframe”, “switching subframe” and “unoccupied subframe” may be used interchangeably.

[0065] In one approach, an eNB may be informed by the WTRU of SO-HD-FDD functionality. In one example, a specific physical random access channel (PRACH) resource may be used to indicate SO-IFD-FDD functionality. In another example, the Category field can be used to indicate the functionality of SO-HD-FDD. If the category 0 WTRU indicates HD-FDD functionality, then the WTRU may be considered as having SO-HD-FDD functionality. In this case, a subset of PRACH resources or shared PRACH resources may be reserved for the SO-HD-FDD WTRU, and a subset of PRACH resources or shared PRACH resources may be used to indicate the SO-HD-FDD WTRU. A PRACH resource subset for SO-HD-FDD may be broadcast in a system information unit (SIB) (e.g., SIB-2). An SO-HD-FDD WTRU may transmit a PRACH preamble within a subset of PRACH resources.

[0066] An RF parameter, for example, supportedBandListEUTRA (list of supported EUTRA ranges), can be used to indicate which E-UTRA radio bands are supported by the WTRU. For each band, support may be indicated for half-duplex, full-duplex, or half-duplex with one oscillator.

[0067] The supportedBandListEUTRA parameter may be defined to indicate which radio frequency bands of the E-UTRA are supported by the WTRU. For each range, support may be indicated for either half-duplex mode or full-duplex mode. If a category 0 WTRU indicates half-duplex support (for example, only), then the eNB may consider this WTRU as a SO-HD-FDD WTRU.

[0068] FIG. 2 is a flowchart illustrating an exemplary process of indicating a base station for a half-duplex, single-oscillator WTRU, frequency division duplex (SO-HD-FDD WTRU). In this approach, the eNB can detect blindly SO-HD-FDD functionality without explicit indication from the WTRU. In this process, one or more of the following may apply:

[0069] the eNB may schedule a physical uplink shared channel (PUSCH) in step 200 for a Category 0 WTRU with HD-FDD functionality in an uplink subframe that is aligned with a downlink subframe (eg, time aligned), containing a broadcast channel (e.g., SIB-1), and if no PUSCH transmission is detected in the provided uplink resource from the WTRU in step 210, then the eNB may consider the WTRU as an SO-HD-FDD WTRU.

[0070] The detection of a scheduled PUSCH transmission may be based on signal strength. For example, if the signal level of the planned PUSCH is below a predetermined threshold in step 220, then the eNB may assume or determine that the PUSCH is not transmitted from the WTRU and may consider the WTRU as an SO-HD-FDD device in step 230. The eNB may not consider the WTRU as SO -HD-FDD device in step 240, if the eNB receives a response that exceeds the signal level threshold set in step 240. the eNB can schedule the PUSCH in the uplink subframe, which is aligned with the downlink subframe containing the broadcast channel, for advance dividing the number and KeNB WTRU may consider as SO-HD-FDD WTRU, if all cases satisfy the condition.

[0071] the eNB may schedule a physical downlink shared channel (PDSCH) in the DL subframe n for category 0 WTRU with HD-FDD functionality, where the DL subframe n + 4 contains a broadcast channel (eg, SIB-1) and if no corresponding PUCCH is received in the n + 4 UL subframe, then the eNB may consider the WTRU as having SO-HD-FDD functionality. The detection of the corresponding transmission of the physical uplink control channel (PUCCH) may be based on the signal strength.

[0072] More generally, an eNB may schedule either an uplink signal or a downlink signal in a subframe, which may contain a signal having a higher priority in the opposite direction, and check whether the lower priority signal is ignored on the WTRU side. A priority rule can be used (for example, used only) for the SO-HD-FDD WTRU.

[0073] FIG. 3 is a timing chart that illustrates that a subset of HARQ processes is used for an SO-HD-FDD WTRU, where a HARQ process can be defined as (re) transmitting uplink and downlink with timing n + 4. For example, if subframe n is used for the downlink, then subframe n + 4 is used for the corresponding HARQ-ACK transmission. In the example shown in FIG. 3, a WTRU that can use two consecutive HARQ processes, starting from subframes 0 and 1, for downlink receptions, can transmit the corresponding HARQ-ACKs in subframe 4 and 5, respectively. With this approach, a subset of the HARQ process can be used to support a single-oscillator SO-HD-FDD WTRU. In one example, two HARQ processes can be used for unicast traffic, as shown. In this case, two consecutive HARQ processes of eight HARQ processes can be used in order to minimize switching time. For example, HARQ processes 0 and 1 can be used. In another example, three HARQ processes can be used with three consecutive HARQ processes from eight HARQ processes, such as, but not limited to, HARQ processes 0, 1, and 2.

[0074] Alternatively, all HARQ processes for transmitting the PDSCH used for FDD (eg, eight) can be used, while a subset of HARQ processes can be used for transmitting PUSCH. Because the asynchronous HARQ procedure can be used for the downlink, and the synchronous HARQ procedure can be used for the uplink, all HARQ processes can be used for the downlink, while the subset of HARQ processes is used for the uplink. For example, eight HARQ processes can be used to transmit PDSCH, and two HARQ processes can be used to transmit PUSCH. The number of HARQ processes used for the SO-HD-FDD WTRU can be determined as a function of timing advance value.

[0075] In one example, if the timing advance value is less than a predetermined threshold, then N HARQ processes may be used, and if the timing advance value is greater than a predetermined threshold, M HARQ processes may be used, where N> M.

[0076] The number of HARQ processes for PDSCH and / or PUSCH can be predefined as a function of timing advance value, so that the SO-HD-FDD WTRU can implicitly be informed of the number of HARQ processes in accordance with timing advance value.

[0077] FIG. 4 is a timing chart that illustrates an exemplary HARQ process bias for SO-HD-FDD WTRU groups. A HARQ process offset may be used for one or more SO-HD-FDD WTRUs to maximize resource utilization. For example, HARQ processes {0, 1} 400, 410 can be used for one SO-HD-FDD WTRU group, and HARQ processes {2, 3} 420, 430 can be used for another SO-HD-FDD WTRU group , as shown. In this case, the eNB can divide the SO-HD-FDD WTRU into two groups and use different HARQ process offsets.

[0078] FIG. 5 is a timing chart that illustrates an exemplary HARQ process corresponding to the number of oscillators for an HD-FDD WTRU. With this approach, a different number of HARQ processes can be used according to the number of oscillators. For example, two HARQ processes can be used for SO-HD-FDD WTRU, while three HARQ processes can be used for DO-HD-FDD WTRU. In this case, sequential HARQ processes can be used from eight HARQ processes to minimize switching time. Alternatively, more HARQ processes can be used for DO-HD-FDD WTRU.

[0079] FIG. 6 is a timing chart that illustrates an exemplary PDCCH subframe for SO-HD-FDD WTBU only. In this approach, the eNB scheduler can, or always can, consider a subset of the downlink subframe, even if one or more subframes may need to be used for uplink direction in accordance with the HARQ procedure. Subframe 0 and 5 may or may always be considered as downlink subframes, so the eNB may not schedule uplink transmission in subframe 0 and 5. In another example, subframes containing broadcast channels may be considered as only subframes downlink. In this case, subframe n may or may always be used as the downlink subframe. The eNB may not transmit a PDCCH corresponding to the provision of the PUSCH in the n-4 subframe and / or adjacent subframes. n may correspond to subframe 0, indicated by 600, and subframe 5, indicated by 650. n may be 0 and / or 5 in an evenly numbered radio frame, and n may be 0 in an oddly numbered radio frame, since SIB-1 is transmitted only in the subframe 5 evenly numbered radio frames.

[0080] Subframe n may or may always be used for the downlink subframe, such that the eNB may not schedule PDSCH in subframe n-4 of 610 and / or adjacent subframes to avoid transmitting PUCCH in subframe n. n can be 0 and 5 in all radio frames. n may be 0 and / or 5 in an evenly numbered radio frame and 0 in an oddly numbered radio frame.

[0081] In another approach, an eNB scheduler may determine or use a priority rule between uplink and downlink signals, and PUSCH or PDSCH scheduling may be based on priority rules. For example, if an eNB needs or intends to schedule a PDSCH for a SO-HD-FDD WTBU in subframe n, and a subframe n contains scheduling request resources (SR) for the WTRU, the eNB may not schedule a PDSCH in subframe n, for example, if SB has a higher priority than PDSCH. Periodic uplink transmission may have a higher priority than PDSCH. For example, one or more of the SRs, periodic channel status information report (CSI) and periodic sounding reference signaling (SRS) may have a higher priority than PDSCH. Among periodic CSI reports, rank indication (RI) may have higher priority than PDSCH, while other types of reports, such as precoding matrix indicator (FMI) and channel quality indicator (CQI), may have lower priority. than PDSCH.

[0082] In another example, the SR may have a higher priority than the PDSCH, and other uplink transmissions may have a lower priority than the PDSCH. With the exception of SB, an eNB can schedule PDSCHs in a subframe where the WTRU can transmit periodic uplink signals. The terms NeNBʺ and е eNB лани scheduler can be used interchangeably.

[0083] In another approach, an adjacent subframe (eg, an uplink subframe) may not overlap (or precede or follow) with subframes containing one or more of a broadcast channel, a paging channel, and a synchronization channel. The eNB scheduler may assume or expect that, for example, all SO-HD-FDD WTRUs may receive broadcast or paging channels in RRC_CONNECTED (RRC connected) mode. In this case, the eNB scheduler can assume or expect that, for example, all RRC_CONNECTED SO-HD-FDD WTRUs can monitor SIB-1, for example, in order to check whether the valueTag (label value) is updated or not. The eNB scheduler can schedule and / or use a subframe containing SIB-1 (e.g., subframe 5 in an evenly numbered radio frame) as a downlink (e.g., always), and can avoid overlapping with an adjacent subframe (e.g., uplink subframe) ), or may avoid uplink resource scheduling or uplink transmission in an adjacent subframe. The eNB scheduler can avoid overlapping a subframe containing SIB-1 with a switching subframe.

[0084] The eNB scheduler may expect or assume that, for example, all RRC_CONNECTED SO-HD-FDD WTRUs may monitor PDCCHs with a temporary paging radio network identifier (P-RNTI) in one or more of a set or a subset of subframes (eg, one or more of subframes 0, 4, 5 and 9 in some radio frames). The eNB scheduler may consider subframes potentially used for paging as downlink subframes and may avoid overlapping with an adjacent subframe (e.g., uplink subframe) or may avoid scheduling uplink resources or transmitting uplink in an adjacent subframe. The eNB may avoid overlapping subframes potentially used for paging with the switching subframe.

[0085] In one approach, an eNB receiver may assume or expect that a scheduled uplink transmission in a particular subframe may not be transmitted from an SO-HD-FDD WTRU if the scheduled uplink transmission has one or more of the following properties: (i ) it is located (for example, should be transmitted) in the switching subframe; (ii) it is located (for example, should be transmitted) in a subframe adjacent to the signal in the opposite direction with a higher priority; and / or (ii) it conflicts with the signal in the opposite direction with a higher priority. The eNB may skip decoding the scheduled uplink signal from the WTRU to reduce decoding complexity and save computing power. As an example, if a periodic SRS transmission is scheduled in subframe n and subframe n is (or is part of) a switching subframe, or subframe n is (or adjacent to) a downlink subframe for an SO-HD-FDD WTRU, then eNB may assume or expect that the periodic SRS is not transmitted from the SO-HD-FDD WTRU if the periodic SRS may be of lower priority than the downlink signal that can be transmitted in the downlink subframe. eNB may not decode periodic SRS from SO-HD-FDD WTRU. In this example, subframe n may be an adjacent subframe of a downlink subframe, which may comprise a broadcast channel (e.g., PBCH and / or SIB). Subframe n may be an adjacent subframe of the downlink subframe, which may comprise a P-RNTI PDCCH, which may be for an SO-HD-FDD WTRU. Alternatively, subframe n may be an adjacent subframe of a downlink subframe, which may comprise a physical multicast channel (PMCH) and / or a positioning reference signal (PRS).

[0086] In another example, if a periodic PUCCH transmission (for example, a PUCCH that can carry a periodic CSI report) is scheduled in subframe n, and subframe n is a subframe (or part of a subframe) adjacent to the downlink subframe, then eNB may assume or expect that periodic PUCCH is not transmitted from the SO-HD-FDD WTRU. In this example, subframe n may be an adjacent subframe of a downlink subframe, which may comprise a broadcast channel (eg, a physical broadcast channel (PBCH) and / or SIB). Subframe n may be an adjacent subframe of the downlink subframe, which may comprise a P-RNTI PDCCH, which may be for an SO-HD-FDD WTRU. Subframe n may alternatively be an adjacent subframe of a downlink subframe, which may comprise PMCH and / or PRS.

[0087] In another approach, an eNB may assume or expect that a HARQ-ACK repetition may be skipped in a specific uplink subframe if the SO-HD-FDD WTRU is configured with HARQ-ACK repetitions. For example, if the SO-HD-FDD WTRU is configured with HARQ-ACK repetition, and if there is a downlink subframe containing certain information in the HARQ-ACK repetition, then the eNB may assume or expect that the HARQ-ACK in the subframe may be skipped. In this case, the eNB receiver may not receive the HARQ-ACK repetition in subframe n if subframe n can be used to transmit SIB-1 in the downlink. The eNB may skip receiving HARQ-ACK repetition in subframe n if subframe n can be used for at least one of the paging, PMCH, PRS and / or synchronization channel. Alternatively, the eNB scheduler may not configure HARQ-ACK repetition for the SO-HD-FDD WTRU.

[0088] In one approach, an eNB may use different link adaptation rules for SO-HD-FDD WTRU and DO-HD-FDD WTRU for a (enhanced) physical downlink control channel ((E) PDCCH) and / or PUSCH, For example, if an eNB receives discontinuous transmission (DTX) corresponding to a PDCCH from a DO-HD-FDD WTRU, an eNB may retransmit PDCCHs with higher transmit power and / or higher CCE aggregation. If the eNB receives a DTX corresponding to the PDCCH from the SO-HD-FDD WTEU in a specific uplink subframe, then the eNB can retransmit the PDCCH with the same transmit power and / or aggregation level (E) of the CCE. If, for example, in this case, the eNB receives the DTX corresponding to the (E) PDCCH in the subframe for the DO-HD-FDD WTRU or the full duplex WTRU, then the eNB may assume or expect that the (E) PDCCH may be skipped in the WTRU receiver, for example, due to a lower link adaptation level, where a lower link adaptation level may mean that the transmit power level or channel coding rate may not be sufficient to achieve a certain level of error rate. An eNB can increase the link adaptation level by adding a certain amount of transmit power or reducing the channel coding rate by increasing the aggregation levels (E) of the CCE. The link adaptation level can be configured as a signal-to-noise ratio (SNR) or signal-to-noise + interference (SINR) offset.

[0089] In another approach, the eNB may use various link adaptation rules for the SO-HD-FDD WTRU when the eNB receives the DTX corresponding to the PDCCH according to the location of the uplink subframe. In this case, if the eNB receives the DTX corresponding to the PDCCH in subframe n for the SO-HD-FDD WTRU, and the subframe n is an adjacent subframe, then the eNB may not assume that the PDCCH is lost due to a link adaptation error. The same link adaptation level may be used in retransmission. Otherwise, the eNB may consider that the PDCCH is lost due to a link adaptation error and increase the link adaptation level. As an example, subframes n + 1 or n-1 of a downlink n subframe containing a broadcast channel or a downlink n subframe containing SIB-1 can be considered as adjacent subframes, while n + 1 or subframes n − 1 downlink subframe n containing other SIBs may not be considered as adjacent subframes. In another example, subframes n + 1 or n − 1 of a downlink subframe n containing PMCH and / or PRS may be considered adjacent subframes. Alternatively, the subframes n + 1 or n − 1 of the downlink subframe n containing the paging may be considered as adjacent subframes.

[0090] FIG. 7 is a flowchart illustrating an example of a conflict processing process for an SO-HD-FDD WTRU. In this example, the WTRU can ignore either uplink transmission or downlink reception if the WTRU is scheduled to transmit uplink in subframe n 700, as well as receive downlink in adjacent subframe (e.g. n-1 and / or n + 1) 710. In this case, the ignore rule can be predefined or configured in accordance with the priority between the transmission of the uplink signal and the reception of the downlink signal. Priority checking of the current transmission / reception may be performed at step 720. In one example, the downlink signal can always have a higher priority than the uplink signal. In this case, if the WTRU is scheduled to receive the downlink signal, such as unicast, broadcast channel, synchronization signal, paging, PMCH and / or PRS, the WTRU may receive the downlink signal at step 730, even if the WTRU is scheduled for transmitting an uplink signal. The WTRU may skip the UL transmission in step 750. A switching time may be required or used by the WTRU before receiving the DL in step 730.

[0091] Alternatively, in one example, the uplink signal may always have a higher priority than the downlink signal. For example, if the WTRU is scheduled to transmit (e.g., any) uplink signal, e.g., PUSCH, PUCCH (e.g., for ACK / NACK or periodic CSI feedback report), SRS, SR, and / or the PRACH preamble, the WTRU may transmit the uplink signal at step 740, even if there may be a downlink signal for the WTRU to receive in an adjacent subframe. In this case, if the WTRU is scheduled to transmit the uplink signal in subframe n, the WTRU may skip receiving downlink signals in subframe n, as well as adjacent subframes (e.g., subframe n-1 and / or n + 1) in step 760 where the downlink signal may include at least one of (E) PDCCH, PHICH, PCFICH and PDSCH. If the WTRU is not scheduled for DL in an adjacent subframe at 710, the WTRU may transmit the UL signal in step 740 without considering priorities between the uplink and downlink signals. Switching time may be required or used by the WTRU before transmitting the UL in step 740.

[0092] PDSCH, which can be transmitted with a temporary cellular radio network identifier (C-RNTI), may have lower priority than uplink signals, while other downlink transmissions may have higher priority than uplink signals communication, and the uplink signal may include at least one of PUSCH, PUCCH, SRS and SR.

[0098] FIG. 8 is a flowchart illustrating an alternative example of a conflict processing process for an SO-HD-FDD WTRU involving a second preliminary subframe. In this example, the WTRU may ignore either uplink transmission or downlink reception if the WTBU is scheduled for uplink transmission in subframe n, 800, and is also scheduled for receiving downlink in adjacent subframe (e.g., n-1 ), 810. In this case, the ignore rule can be predefined or configured in accordance with the priority between the transmission of the uplink signal and the reception of the downlink signal. Priority checking of the current transmission / reception can be performed at block 820. The downlink signal can always have a higher priority than the uplink signal, or vice versa. An optional alternative 830 may be implemented that includes accounting for the n-2 subframe. If subframe n-2 is the uplink priority subframe, then the WTRU may skip receiving both subframe n-1 and subframe n to switch the oscillator to the transmission frequency, 840. At step 860, the WTRU may transmit the uplink signal in subframe n . If subframe n-2 is not a priority uplink subframe, 830, and receiving a downlink signal has higher priority than transmitting an uplink signal, 820, then the WTRU may proceed to receiving a downlink signal in subframe n-1 850.

[0094] FIG. 9 is a flowchart illustrating another alternative example of a conflict processing process for an SO-HD-FDD WTRU using an adjacent previous subframe. The flowchart begins with the WTRU scheduled for uplink transmission in subframe n, 900. If the WTRU is scheduled for downlink reception or not scheduled for uplink transmission in adjacent subframe n + 1, 910, the WTRU proceeds to checking transmit / receive priority, 920. An optional alternative, 930, may be implemented that includes accounting for subframe n-1. If the priority check indicates transmission, then the WTRU can determine if the n-1 subframe is a downlink priority subframe, 930. If n-1 is a downlink priority subframe, then the WTRU skips the transmission and switches the oscillator to the receive frequency, 940. Then The WTRU may receive the downlink subframe in subframe n + 1, 960. If the WTRU is not scheduled for DL, 910, the WTRU continues to transmit the uplink signal in subframe n, 950. At step 970, the WTRU skips reception in subframe n + 1. If subframe n-1 is not a downlink priority subframe, the WTRU continues to transmit the uplink signal in subframe n, 950, and may skip receiving in subframe n + 1, 970. If the transmit / receive priority check, 920, indicates a receive priority The WTRU skips the transmission of subframe n and switches the oscillator to the receive frequency, 940. Then, the WTRU is able to receive the downlink signal in subframe n + 1, 960.

[0095] The measurement of the channel state information reference signal (CSI-RS) may have a lower priority than the scheduled uplink signal. For example, if a WTRU needs (or has configured resources) to measure the CSI-RS in a subframe, and the subframe is either an adjacent subframe of a scheduled uplink subframe, or is a scheduled uplink subframe, the WTRU may skip the CSI-RS measurement in the subframe. The WTRU may transmit scheduled uplink transmission.

[0096] Broadcast channels may have a higher priority than the uplink signal. In one example, if a WTRU is scheduled to transmit an uplink signal in subframe n, and subframe n is either an adjacent subframe of a downlink subframe, which may comprise a broadcast channel, or a downlink subframe, then the WTRU may ignore uplink transmission . If the WTRU is in RRC_CONNECTED mode, then the subframe containing SIB-1 can always be considered as a downlink subframe, so that the WTRU can ignore uplink transmission for a subframe containing SIB-1 and / or associated adjacent subframes. A subframe containing one or more other SIB-1s may be considered as a downlink subframe during the modification period if the broadcast information is updated. Subframe n may be an adjacent subframe, an uplink subframe, or a downlink subframe. FIG. 10 shows a timing chart that illustrates an example partial ignore scheme for an SO-HD-FDD WTRU. In such an approach, the WTRU may ignore the portion of the downlink or uplink subframe that it overlaps. For example, if downlink reception overlaps with an adjacent uplink transmission subframe, a portion of the downlink subframe may be received. A WTRU may receive a PDCCH in a subframe, while a WTRU may skip receiving a portion of the PDSCH of a subframe. In this case, two types of subframes can be defined in which the SO-HD-FDD WTRU receives only PDCCHs, such as a multicast / broadcast single-frequency network (MBSFN) subframe and an adjacent subframe immediately after the last downlink subframe. Non-MBSFN subframes, where the SO-HD-FDD WTRU only accepts PDCCHs, can be defined as only PDCCH subframes. These subframes are shown as 1002, 1010, 1018. In a subframe of only PDCCH, DO-HD-PDD, the WTRU can receive both PDCCH and PDSCH.

[0097] Two types of downlink non-MBSFN subframes can be defined, such as the PDCCH 1002, 1010 and 1018 subframe only and the PDCCH + PDSCH subframe 1000, 1001, 1004, 1005, 1008, 1009, 1012, 1013, 1016 and 1017. In the PDCCH only subframe, the WTRU can only control the PDCCH, while in the PDCCH + PDSCH subframe, the WTRU can control the PDCCH and can receive signals in the PDSCH.

[0098] Only the PDCCH subframe may be implicitly configured in accordance with the uplink grant. For example, if a PUSCH is scheduled in subframe n, the WTRU can only receive PDCCH in subframe n-2, even though subframe n-2 is a non-MBSFN subframe. In this case, if the PDSCH is scheduled in the PDCCH only subframe, the WTRU may skip receiving the corresponding PDSCH and transmit the NACK to the eNB. If the PDSCH is scheduled in the PDCCH only subframe, then the WTRU may skip receiving the corresponding PDSCH and transmit the DTX to the eNB. Only the PDCCH subframe may be implicitly configured as a function of the timing advance value used. For example, if the WTRU timing advance value is greater than a predetermined threshold, then the WTRU may skip PDCCH control in the PDCCH subframe only. If the WTRU timing advance value is less than a predetermined threshold, then the WTRU can monitor the PDCCH in the PDCCH only subframe. The total PDCCH search space can only be monitored in the PDCCH only subframe.

[0099] In one approach, if the WTRU is configured to measure CSI-RS in subframe n, and subframe n is in an adjacent subframe for uplink transmission, or is a subframe (eg, an uplink subframe) in which the WTRU is scheduled for transmission uplink, then the WTRU may skip the CSI-RS reception in subframe n for CSI measurement. If the WTRU is to (or requested or expected) to report a CSI corresponding to the CSI-RI transmitted in subframe n, the WTRU may transmit the latest CSI measured before subframe n. If the WTRU does not have the most recent CSI measured before subframe n, then the WTRU may report a default value, where the default value may be a predetermined value that can be used when the measured CSI is not available. The most recently measured CSI may include CQI, ΡΜI and / or RI.

[0100] If the WTRU is configured or requested to report a CSI corresponding to the CSI-RS transmitted in subframe n, the WTRU may transmit the most recently measured CSI if the CSI is updated from the latest reporting.

[0101] If the WTRU is requested to report CSI, then the WTRU may first check whether the CSI is updated or not, from the latest CSI reporting. If the CSI is not updated from the latest reporting, then the WTRU may not report CSI, and a null signal may be transmitted.

[0102] In another approach, if the WTRU is configured or requested to report CSI in subframe n, and the WTRU must receive a downlink signal in subframe n, then the WTRU can either report CSI or receive a downlink signal in accordance with the CSI update condition. For example, if the CSI is not updated from the latest reporting, the WTRU may ignore the CSI reporting and may receive a downlink signal in a subframe. Otherwise, the WTRU may report the CSI and skip downlink reception according to priority.

[0103] If the downlink signal has a higher priority than CSI reporting, then the WTRU can receive the downlink signal regardless of the status of the CSI update. Alternatively, if the downlink signal has a lower priority than CSI reporting, then the WTRU can either ignore CSI reporting or transmit CSI reporting in accordance with the CSI update condition.

[0104] In FIG. 11 is a timing chart that illustrates transmission timing without using packet transmissions. In this case, the FDD LC-MTS WTRU with one oscillator may have a switching time of RX-to-TX (i.e., DL-to-UL) and TX-to-RX (i.e., UL-to-DL ) 1 ms, excluding forward and reverse transit time (RTT)). As a result, the scheduled DL transmission in subframe n with A / N feedback expected in the UL subframe n + 4 can cause n + 3 DL-to-UL switching, n + 4 UL transmission A / N, and then n +5 switching to DL frequency. Then n + 6 subframe will be ready to receive DL. For example, a downlink occurs in subframe 0 1100, a switching operation in subframes 1-3 1110, upload in subframe 4 1120, switching in subframe 5 1130, and receiving a downlink in subframe 6 1140. For WTRUs on the cell edge, 2 ms loss scheduling capabilities can be provided since RTT can be added to a switching time of 1 ms. In order to improve spectrum efficiency for these WTRUs, packet transmissions can be used in both DL and UL directions, as well as grouped A / N feedback for the entire packet, similar to the time division duplex (TDD) technique.

[0105] In another approach, the LC-MTC may support n + 4 * k (where k may be an integer or a natural number) feedback rule when grouping A / N for scheduled DL data. This means that the window size for DL packet transmissions may have, but is not limited to the following examples detailed in FIG. 12-14.

[0106] FIG. 12 illustrates, by way of example, 2 downlink subframe 1200-1210, 3 switching subframes 1220, 1230, and uplink A / N subframe 1240. The WTRU can group 2 A / N bits into a single transmission in 1CC format PUCCH, 1240, at n + 4, while n + 3 1230 can be used for switching time.

[0107] FIG. 13 illustrates, by way of example, 6 downlink subframes with n + 7 1370 as the switching point and n + 8 1380 as the feedback point. The WTRU may group 6 A / N into a single PUCCH transmission in subframe n + 8 1380.

[0108] FIG. 14 illustrates as an example 10 downlink subframes 1400-1445 with n + 11 1455 as a switching point and n + 12 as UL PUCCH with 10 grouped A / N 1460. In this configuration, PUCCH format 3 can be used.

[0109] In this case, the rule for DL packet transmissions for window size can be obtained as

Window_size = 4 * n + 2, where n is a positive integer

(equation 1)

[0110] The maximum value of owWindow_sizeʺ can be taken as the maximum number of A / N bits that the PUCCH format 3 can carry without performing an ʺINʺ operation between A / N received transport blocks, so that a 1-to-1 A / N mapping is sent to eNB, avoiding the repetition of the entire packet in case of failure of reception of a subframe. The mapping of A / N bits for PUCCH format 3 may be a concatenated sequence starting with the A / N of the received first subframe, A / N of the second received subframe, etc. The remaining unused A / N bits may be full.

[0111] In another approach, where the window size may be smaller (2 ~ 4 subframes), it may be acceptable to select a simple ʺ AND ателя pointer for a small packet (for example, 2 subframes), so a 1 or 2b PUCCH format may be used. When 2 A / N bits are available in the PUCCH, then each bit can be, for example, ʺandʺ for two pairs of transport blocks.

[0112] In another approach, the WTRU may follow one or more rules for grouped feedback. After the end of the DL packet, the last n + k subframe, where k is the DL packet size in the subframes, the WTRU may group A / N in the UL transmission of the n + k + 4 subframe. With this approach, the packet size limit will follow the capacity of the A / N PUCCH.

[0113] The second possible rule, which can make room for switching time, is to have grouped UL feedback in subframe m defined as follows:

m = n + Window_size + MOD4 (n) +1 (equation 2)

[0114] This can ensure that the WTRU uses the first multiple of 4 based on subframe n after packet n + k for its grouped UL feedback.

[0115] A UL packet may be generated similarly to TDD, and the WTRU will receive its A / N set on the physical channel of the Hybrid ARQ Indicator (PHICH), which can multiplex A / N over the set of PHICH as by multiplexing the set of WTRUs following the last UL subframe from WTRU data packet. Thus, the eNB can multiplex the multiple A / N PHICH for this UL packet.

[0116] In another approach, the WTRU may be configured with an assigned feedback subframe offset for DL and / or UL for a packet window size, or with multiple offsets specific to each window size from a configured set.

[0117] In order to facilitate a clear SO-HD-FDD packet transmission operation, the eNB may signal the DL and / or UL packet window size. In one approach, the window size for DL and UL can be broadcast through one of the SIBs using a bitmap or a combination of bits that will be mapped to various default packet configurations as an optional or mandatory IE. If IE is not broadcast, then the WTRU may use normal operation.

[0118] In another embodiment, the window size for DL and UL can be semi-statically configured by RRC signaling using a configuration or reconfiguration message. Alternatively, the WTRU may receive a set of window sizes that the WTRU may use.

[01191 The semi-static configuration may comprise the expected A / N group feedback feedback subframe that the WTRU should follow for the size of the packet window (s) configured for DL and / or UL. This offset can be counted from the beginning or from the end of the sub-frame of the packet window size. This offset may be unique or may have a specific value for each window size.

[0120] In another approach, a dynamic downlink configuration may be used. Based on the amount of data from the eNB, a larger or smaller packet window size may be signaled. This can be achieved by explicit signaling in the DCI (e.g., a combination of bits in the DCI) carried over the (E) PDCCH, which the WTRU can receive for proper reception of the packet transmission. This window size can be based on a set of default window sizes that the WTRU can assume or know

[0121] Alternatively, the WTRU may follow decoding (E) PDCCH decoding, and the “tail of the window packet” can be used by the ENB in the last DCI related to the packet window to signal the end of the packet data.

[0122] In another approach, a dynamic uplink configuration may be used. In addition to the semi-static configuration, a more dynamic circuit can be provided either separately or as a combination of both:

[01231 After the scheduling request (SR) sent by the WTRU, the eNB may signal, as part of the UL grant, the window size to use. The signal may be an explicit bit combination that the WTRU may interpret as one of the semi-statically configured UL window sizes.

[0124] After receiving a buffer status report (BSR), the eNB can increase or decrease the size of the window based on the amount of data from the WTRU using any method described in this document regarding the dynamic configuration of the uplink,

[0125] After receiving the power headroom report (PHR) from the WTRU, the eNB can adapt the modulation and coding scheme (MCS) and UL (link adaptation) and window size to adapt the WTRU transmissions in correlation with the last received BSR report.

[0126] Additionally, the WTRU may use a medium access control (MAC) control element (CE) to signal the UL packet window size or modify the UL packet window size. WTEU may use part of the PUCCH payload to signal UL packet window size. Alternatively, the WTRU may include a UCI UL packet in the last subframe indicating the end of the packet data.

[0127] Although features and elements are described above in specific combinations, one skilled in the art will understand that each feature or element can be used individually or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware included in a computer readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless communications) and computer-readable media for storing data. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard drives and removable drives, magneto-optical media, and optical media such as CD-ROMs and digital versatile disks (DVDs). The processor, together with the software, can be used to implement a radio frequency transceiver for use in a WTRU, WTRU, terminal, base station, RNC, or any host computer.

OPTIONS FOR CARRYING OUT

1. A method for half duplex mode using a single oscillator.

2. The method of embodiment 1, wherein the Extended Node B (eNB) scheduler is informed whether the WTRU with half-duplex functionality with one oscillator or two oscillators is implemented.

3. The method according to any of the previous embodiments, in which the single-oscillator WTRU may not receive or transmit in a subframe if there is unicast traffic scheduling in any direction within the switching time.

4. The method according to any of the previous embodiments, in which the behavior of the WTRU with one oscillator is determined provided that the signals of the uplink and downlink are located in the same subframe or adjacent subframes.

5. The method according to any of the previous embodiments, in which the WTRU with one oscillator may not transmit an uplink signal or may not receive a downlink signal, provided that the uplink and downlink signals are located in the same subframe or adjacent subframes.

6. The method according to any of the previous embodiments, in which the spectral efficiency is not significantly impaired due to switching time.

7. The method according to any of the previous embodiments, in which the eNB can be informed by the WTRU regarding the functionality of SO-HD-FDD.

8. The method according to any of the previous embodiments, in which the eNB blindly detects the functionality of SO-HD-FDD without an explicit indication from the WTRU.

9. The method of any of the previous embodiments, wherein the HARQ process subset is used to support a single oscillator SO-HD-FDD WTRU.

10. The method according to any of the previous embodiments, which uses two HARQ processes for unicast traffic.

11. The method according to any of the previous embodiments, in which a different number of HARQ processes are used in accordance with the number of oscillators.

12. The method according to any of the previous embodiments, in which two HARQ processes are used for SO-HD-FDD WTRU.

13. The method according to any of the previous embodiments, in which three HARQ processes are used for DO-HD-FDD WTRU.

14. The method according to any of the previous embodiments, in which the eNB scheduler always considers the subset of the subframes as the downlink, even if one or more subframes are to be used for uplink direction in accordance with the HARQ procedure.

15. The method according to any one of the preceding embodiments, wherein the eNB scheduler determines a priority rule between the uplink and the downlink, and the PUSCH or PDSCH scheduling is based on the priority rules

16. A method according to any one of the preceding embodiments, wherein the adjacent subframe does not overlap with subframes containing one or more of a broadcast channel, a paging channel, and a synchronization channel.

17. The method according to any of the previous embodiments, in which the eNB scheduler assumes that all SO-HD-FDD WTRUs can receive broadcast and paging channels in RRC_CONNECTED mode.

18. The method according to any of the previous embodiments, in which the eNB receiver assumes that the scheduled uplink transmission in a specific subframe may not be transmitted from the SO-HD-FDD WTRU.

19. The method according to any of the previous embodiments, in which the eNB skips decoding the scheduled uplink signal to reduce the complexity of decoding and save computing power.

20. The method according to any of the previous embodiments, wherein the eNB receiver assumes that the HARQ-ACK repeat is skipped in a specific uplink subframe if the SO-HD-FDD WTRU is configured with HARQ-ACK repeats.

21. The method according to any of the previous embodiments, in which the eNB uses various link adaptation rules for the SO-HD-FDD WTRU and DO-HD-FBD WTRU for the (enhanced) physical downlink control channel ((E) PDCCH) and physical uplink shared channel (PUSCH).

22. The method according to any of the previous embodiments, in which provided that the eNB receives the discontinuous transmission (DTX) corresponding to the PDCCH from the DO-HB-FDB WTRU, the eNB retransmits the PDCCH with a higher transmit power and / or higher level CCE aggregations.

23. The method according to any of the previous embodiments, in which provided that the eNB receives the DTX corresponding to the PDCCH from the SO-HD-FDD WTRU in a specific uplink subframe, the eNB retransmits the PDCCH with the same transmit power and / or level aggregations CEE.

24. The method according to any of the preceding embodiments, wherein the eNB uses various link adaptation rules for the SO-HD-FDD WTRU, provided that the eNB receives the DTX corresponding to the PDCCH in accordance with the location of the uplink subframe.

25. The method according to any of the previous embodiments, in which the WTRU ignores either uplink transmission or downlink reception in subframe n if the WTRU is scheduled for uplink transmission as well as downlink reception.

26. The method according to any of the previous embodiments, in which the WTRD ignores drops the portion of the downlink subframe or uplink that overlaps.

27, The method according to any of the previous embodiments, in which, provided that the WTRU is configured to measure CSI-RS in subframe n, and subframe n is in an adjacent subframe for transmitting an uplink or an uplink subframe in which a WTRU is scheduled for transmitting the uplink signal, the WTRU skips receiving CSI-RS in subframe n for measuring CSI.

28. The method according to any of the previous embodiments, in which provided that the WTRU is required to report in subframe n and the WTRU is also required to receive a downlink signal in subframe n, the WTRU either reports CSI or receives a downlink signal in accordance with condition for updating CSI.

29. The method according to any of the previous embodiments, in which packet transmissions are used in both directions DL and UL, as well as grouped A / N feedback for the entire packet of subframes to increase spectrum efficiency.

30. The method according to any of the previous embodiments, in which the LC-MTC supports the n + 4 * k feedback rule when grouping A / N for scheduled DL data.

31. The method according to any of the previous embodiments, in which the WTRU complies with the following rules for grouped feedback: after the end of the DL packet, the last subframe n + k, where k is the DL packet size in subframes, the WTRU can group A / N in subframe n + k + 4 UL gears. In this solution, the packet size limit will follow the capacity of the A / N PUCCH; and the grouped UL feedback in subframe m is defined as: m = n + Window_size + MOD4 (n) +1.

32. The method according to any of the previous embodiments, in which the WTRU is configured with an assigned feedback subframe offset for DL and / or UL for a packet window size or with a variety of offsets specific to each window size from a configured set.

33. The method according to any of the previous embodiments, in which the eNB can signal the window size of the DL and / or UL packet using one or a combination of the following methods: semi-static configuration; the dynamic configuration of the downlink and the dynamic configuration of the uplink.

34. The method according to any one of the preceding embodiments, further comprising transmitting a single oscillator (SO-HD-FDD) WTRU HD-FDD indication.

35. The method according to any of the previous embodiments, further comprising splitting the PRACH for the SO-HD-FDD UE.

36. The method according to any of the previous embodiments, further comprising the step of blindly detecting at the eNB receiver by scheduling uplink and downlink in adjacent subframes.

37. The method according to any of the previous embodiments, in which the HARQ procedure for the SO-FID-FDD WTRU comprises at least one selected from the group including a subset of consecutive HARQ processes and a HARQ process offset for two SO-HD-FDD WTRU groups .

38. The method according to any of the preceding embodiments, further comprising conflict prevention for uplink and downlink signals in adjacent subframes based on priority rules between uplink and downlink signals.

39. The method according to any of the previous embodiments, further comprising ignoring the WTRU rules when uplink and downlink signals are scheduled in adjacent subframes.

40. The method according to any of the previous embodiments, further comprising a packet-based transmission with aggregate A / N transmission to reduce spectral efficiency loss due to long switching times.

41. A WTRU configured to perform a method according to any of the previous embodiments, comprising:

receiver;

transmitter and

processor with the ability to communicate with the transmitter and receiver,

42. eNB configured to perform the method according to any one of embodiments 1-40.

43. A base station configured to perform the method according to any one of embodiments 1-40.

44. An integrated circuit configured to perform the method according to any one of embodiments 1-40.

Claims (22)

1. A method performed by a half-duplex single-oscillator wireless transmit / receive unit (HD-SO-WTRU) for processing subframes, the method comprising: determining, based on the priority rule, a subframe for processing from the uplink subframe and the scheduled downlink transmission subframe, wherein the uplink subframe and the scheduled downlink transmission subframe conflict with each other; and processing half-duplex with one oscillator unit of a wireless transmission / reception (HD-SO-WTRU) of a specific subframe; wherein the priority rules indicate that the downlink has a higher priority than the uplink. 2. The method of claim 1, wherein the sub-frame of the scheduled downlink transmission is a broadcast sub-frame. 3. The method of claim 1, wherein the uplink subframe includes an uplink scheduling request. 4. The method of claim 1, wherein the sub-frame of the scheduled downlink transmission is scheduled through machine-type communication (MTC) of a physical downlink control channel (PDCCH). 5. The method of claim 1, wherein the priority rule indicates that periodic channel status information (CSI) reporting uplink transmission has a lower priority than downlink reception. 6. The method of claim 1, wherein the priority rule indicates that periodic sensing reference signaling (SRS) reporting uplink transmission has a lower priority than downlink reception. 7. The method of claim 1, wherein the priority rule indicates that a precoding matrix indicator (PMI) or channel quality indicator (CQI) reporting uplink transmission has a lower priority than downlink reception. 8. The method of claim 1, wherein the priority rule indicates that receiving a downlink for measuring a channel status information reference signal (CSI-RS) has a higher priority than uplink transmission. 9. The method of claim 4, wherein the scheduled downlink transmission subframe is scheduled using a temporary cellular radio network identifier (C-RNTI). 10. Half-duplex with one oscillator unit of the wireless transmit / receive (HD-SO-WTRU) for processing subframes containing a processor configured to determine, based on a priority rule, a subframe for processing from an uplink subframe and a scheduled downlink transmission subframe, an uplink subframe and a scheduled downlink transmission subframe conflict with each other; and a transceiver configured to process a specific subframe; wherein the priority rules indicate that the downlink has a higher priority than the uplink. 11. The HD-SO-WTRU of claim 10, wherein the scheduled downlink transmission subframe is a broadcast subframe. 12. The HD-SO-WTRU of claim 10, wherein the uplink subframe is an uplink scheduling request subframe. 13. The HD-SO-WTRU of claim 10, wherein the sub-frame of the scheduled downlink transmission is scheduled through machine-type communication (MTC) of a physical downlink control channel (PDCCH). 14. The HD-SO-WTRU of claim 10, wherein the priority rule indicates that periodic channel state information (CSI) reporting uplink transmission has a lower priority than downlink reception. 15. The HD-SO-WTRU of claim 10, wherein the priority rule indicates that periodic sensing reference signaling (SRS) reporting uplink transmission has a lower priority than downlink reception. 16. The HD-SO-WTRU of claim 10, wherein the priority rule indicates that a precoding matrix indicator (PMI) or channel quality indicator (CQI) reporting uplink transmission has a lower priority than downlink reception. communication lines.

Images