Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/14—Reselecting a network or an air interface
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/04—Wireless resource allocation
  • H04W72/044—Wireless resource allocation based on the type of the allocated resource
  • H04W72/0446—Resources in time domain, e.g. slots or frames
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W74/00—Wireless channel access
  • H04W74/02—Hybrid access
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/24—Reselection being triggered by specific parameters
  • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
  • H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/24—Reselection being triggered by specific parameters
  • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
  • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/04—Wireless resource allocation
  • H04W72/044—Wireless resource allocation based on the type of the allocated resource
  • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/20—Control channels or signalling for resource management
  • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/12—Access point controller devices

Definitions

• the present invention is related to wireless communication systems.
• the present invention relates to integrating resource allocation between time division duplex (TDD) and frequency division duplex (FDD) in wireless communication systems.
• TDD time division duplex
• FDD frequency division duplex
• GSM Global System for Mobile Telecommunications
• 2G Second Generation mobile radio system standard
• 2.5G Second Generation mobile radio system standard
• ETSI SMG European Telecommunications Standard Institute - Special Mobile Group
• UMTS Universal Mobile Telecommunications Systems
• 3GPP Third Generation Partnership Project
• the UMTS network architecture includes a Core Network (CN) interconnected with a UMTS Terrestrial Radio Access Network (UTRAN) via an interface known as lu which is defined in detail in the current publicly available 3GPP specification documents.
• the UTRAN is configured to provide wireless communication services to users through wireless transmit receive units (WTRUs), known as User Equipments (UEs) in 3GPP, via a radio interface known as Uu.
• WTRUs wireless transmit receive units
• UEs User Equipments
• Uu radio interface
• the UTRAN has one or more Radio Network Controllers (RNCs) and base stations, known as Node Bs in 3GPP, which collectively provide for the geographic coverage for wireless communications with UEs.
• RNCs Radio Network Controllers
• Node Bs base stations
• the UTRAN may have several groups of Node Bs connected to different RNCs; two are shown in the example depicted in Figure 1. Where more than one RNC is provided in a UTRAN, inter-RNC communication is performed via
• Communications external to the network components are performed by the Node Bs on a user level via the Uu interface and the CN on a network level via various CN connections to external systems.
• the primary function of base stations is to provide a wireless connection between the base stations' network and the WTRUs.
• a base station emits common ch ⁇ uinel signals allowing non-connected WTRUs to become synchronized with the base station's timing.
• a Node B performs the physical radio connection with, the UEs.
• the Node B receives signals over the Iub interface from the RNC that control the signals transmitted by the Node B over the Uu interface.
• a CN is responsible for routing information to its correct destination. For example, the CN may route voice traffic from a UE that is received by the UMTS via one of the Node Bs to a public switched telephone network (PSTN) or packet data destined for the Internet.
• PSTN public switched telephone network
• the CN has six major components: 1) a serving General Packet Radio Service (GPRS) support node; 2) a gateway GPRS support node; 3) a border gateway; 4) a visitor location register; 5) a mobile services switching center; and 6) a gateway mobile services switching center.
• the serving GPRS support node provides access to packet switched domains, such as the Internet.
• the gateway GPRS support node is a gateway node for connections to other networks.
• the border gateway acts as a firewall to prevent attacks by intruders outside the network on subscribers within the network realm.
• the visitor location register is a current serving networks 'copy' of subscriber data needed to provide services. This information initially comes from a database whicb_ administers mobile subscribers.
• the mobile services switching center is in. charge of 'circuit switched' connections from UMTS terminals to the network.
• the gateway mobile services switching center implements routing functions required based on the current location of subscribers.
• the gateway mobile services switching center also receives and administers connection requests from. subscribers to external networks.
• the RNCs generally control internal functions of the UTRAN.
• RNCs also provide intermediary services for communications having a local component via a Uu interface connection with a Node B and an external service component via a connection between the CN and an external system, for example overseas calls made from a cell phone in a domestic UMTS.
• an RNC oversees multiple base stations, manages radio> resources within the geographic area of wireless radio service coverage servicecL by the Node Bs and controls the physical radio resources for the Uu interface.
• the lu interface of an RNC provides two connections to the CN: one to a. packet switched domain and the other to a circuit switched domain.
• Other- important functions of the RNCs include confidentiality and integrity protection.
• In communication systems such as Third Generation Partnership Project
• Time Division Duplex (TDD) and Frequency Division Duplex (FDD) systems multiple shared and dedicated channels of variable rate data are combined for transmission. Background specification data for such systems are publicly available and continue to be developed.
• TDD type systems the number of UL channels and DL channels may be dynamically adjusted in accordance with traffic conditions at a particular time and place. Therefore, TDD type systems are better suited to handle asymmetrical (or otherwise unbalanced) traffic having high data rates.
• FDD systems have an advantage over TDD type systems in that FDD systems are better suited for handling constant data rate services having low to moderate data rates such as voice traffic because of the predetermined allocation of UL and DL resources.
• Radio resource management between TDD type systems and FDD type systems is individually performed in each system type according to their own allocation methods. This arrangement precludes potential optimizations that may be achieved by integrating resource allocation between time division duplex (TDD) and frequency division duplex (FDD) in wireless communication systems. There is a need therefore to integrate radio resource management between TDD and FDD in wireless communication systems.
• TDD time division duplex
• FDD frequency division duplex
• the present invention integrates resource allocation between time division duplex (TDD) and frequency division duplex (FDD) in wireless communication systems.
• a radio network controller receives a radio access bearer (RAB) request from a core network or a wireless receive/transmit unit (WTRU).
• RNC utilizes a TDD-FDD selector to assign radio resources in response to the request.
• the TDD-FDD selector evaluates various parameters regarding the received RAB request and determines whether it is preferable to assign TDD resources or FDD resources and whether such resources are currently available. Once resources are assigned, system conditions are evaluated to determine whether optimizations may be made to a current resource allocation.
• Figure 1 is a diagram of a typical wireless communication system.
• FIG. 2 is a diagram illustrating an embodiment of the present invention wherein a TDD-FDD selector is provided for TDD and FDD type radio network controllers (RNCs).
• RNCs radio network controllers
• FIG. 3 is a diagram illustrating an embodiment of the present invention wherein a TDD-FDD selector is provided for an integrated TDD/FDD
• Figure 4 is a method wherein wireless resources are assigned in accordance with the present invention.
• FIG. 5 is a diagram illustrating an embodiment of the present invention wherein TDD and FDD type service may be provided with a single In connection between a core network and a FDD RNC.
• Figure 6 is a diagram illustrating the configuration of the RNCs shown in Figure 5.
• FIG. 7 is a block diagram of an RNC including a TDD-FDD selector having a policy server.
• Figure 8 is a flow chart of a process for handover between communication modes wherein a RNC is configured with a TDD-FDD selector having a policy server.
• WTRU includes but is not limited to a user equipment, mobile station, a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment.
• base station includes but is not limited to a Node-B, a site controller, an access point, or any other interfacing device in a wireless environment.
• the system 200 includes a TDD radio network controller (RNC) 204 and a FDD RNC 208 connected to a core network 202.
• RNC radio network controller
• Each RNC 204, 208 controls at least one base station.
• the TDD RNC 204 controls base station 212.
• Base station 212 in turn provides a coverage area 210 wherein WTRUs 228, 230 operating within coverage area 210 may be assigned resources from TDD RNC 204.
• the FDD RNC 208 controls base station 216 which in turn provides coverage area 214.
• WTRUs 220, 222 may be assigned resources from FDD RNC 208.
• a radio access bearer (RAB) request (i.e. a call-setup request) is transmitted from a core network or WTRU to an RNC, it is typically transmitted along with a plurality of parameters that provide information regarding how the requested connection will be utilized. Examples of such parameters include, but are not limited to, the degree of symmetry between the uplink and downlink (i.e.
• symmetry or symmetry status of the requested connection data transfer rate, frame size, application type, and whether the requested connection is point-to-point, point-to-multipoint, or broadcast.
• the aforementioned parameters are purely by way of example, as any type of parameter providing information regarding the requested connection may be utilized.
• RNCs 204, 208 of the present invention are configured with TDD-
• the TDD-FDD selectors 206, 210 may be one or more processors, as desired, for determining the optimal technology type for a received RAB request. That is, based on, for example, parameters provided regarding a RAB request, resource availability, and/or any other relevant considerations, the TDD-FDD selectors 206, 210 work in conjunction with an RNCs existing functionality including its radio resource manager (RRM) to assign resources so that connection requests are assigned resources based on the most efficient system technology type for handling the particular type of connection request. For example, assuming symmetry is the primary consideration, connection requests having symmetrical traffic (i.e.
• a similar amount of traffic in both the uplink and downlink are preferably handled by the FDD RNC 208 which, of course, implements FDD technology and is more efficient at handling such traffic.
• connection requests having asymmetrical traffic are preferably handled by the TDD RNC 204 which, of course, implements TDD technology and is more efficient at handling such traffic.
• a TDD-FDD selector 206, 210 may estimate data rates in the uplink and downlink for the received RAB request.
• the estimated uplink and downlink data rates may be estimated based on, for example, requested data rate, current traffic conditions, current interference levels, or any other relevant parameters.
• the TDD-FDD selector 206, 210 may then compare the difference between the estimated uplink and downlink data rates versus a predetermined threshold. If the difference between the estimated uplink and downlink data rates is equal to or above the threshold, the RAB request may be considered asymmetrical (i.e. has an asymmetrical symmetry status) and resources from a TDD RNC 204 may be assigned. If the difference between the estimated data rates is below the threshold, the RAB request may be considered symmetrical (i.e. has a symmetrical symmetry status) and resources from a FDD-RNC 208 may be assigned.
• connection may be evaluated, individually or in combination with symmetry, when determining the optimal technology type for assigning resources based on a received RAB request. For example, where a requested connection is for a voice application requiring real-time transmission, it is preferable for the connection to be provided using the FDD RNC 208. Similarly, for a data application not requiring real-time transmission, it is preferable for the connection to be provided using the TDD RNC 204. In general, if the traffic is very asymmetrical with a high data rate, TDD is preferable. If the traffic is very symmetrical with a fairly low data rate, FDD is preferable. Anything in between may be sent to either TDD or FDD depending on the situation. For example, if TDD cells are congested, it may be desirable to assign a RAB request to FDD regardless of other parameters.
• a RAB request may originate through either a TDD RNC 204 or a FDD RNC 208.
• the RNC that received the request makes the decision regarding resource assignment and, where necessary, forwards the RAB request to another RNC type as appropriate so that resources are allocated by an appropriate type of RNC.
• the TDD RNC 204 receives a RAB request and determines that it should be handled using FDD type technology
• the TDD RNC 204 will transfer the request to a FDD RNC 208 via an Iur interface.
• the FDD RNC 208 will then handle the request in a normal fashion.
• an integrated TDD-FDD RNC 304 is provided.
• the integrated TDD- FDD RNC 304 integrates the conventional functionality of a TDD RNC and a FDD RNC.
• a single TDD-FDD selector 306 is provided.
• the TDD-FDD selector 306 operates as explained above and determines whether received RAB requests should be handled in TDD mode or FDD mode.
• the TDD-FDD selector may evaluate symmetry, data rate, application type, resource availability, and any other relevant parameters when determining which mode is appropriate for a particular RAB request. For example, since WTRUs 320 and 322 are in a joint coverage area 324, WTRUs 320 and 322 may be assigned resources in either TDD mode or FDD mode, as appropriate.
• the method 400 begins in step 402 when a radio access bearer (RAB) request is received.
• the request may be received by either a TDD or FDD RNC or, in the case where an integrated TDD/FDD RNC is provided, the request may be received in either FDD mode or TDD mode.
• RAB radio access bearer
• parameters regarding the received request are evaluated.
• the parameters may be any parameters that provide information regarding the received RAB.
• the parameters that are preferably evaluated include symmetry, data rate, and application type.
• step 406 it is determined based on the parameters evaluated in step 404 whether it is preferable to handle the requested service in a TDD type cell or a FDD type cell (i.e. in TDD mode or FDD mode). As previously explained, it is preferable to handle high data rate asymmetrical connections in TDD (i.e. in a TDD cell) while symmetrical lower data rate connections are preferably handled in FDD (i.e. in a FDD cell).
• step 406 it is determined whether the WTRU that requires the RAB is within a TDD cell. That is, although it has been determined in step 406 that TDD is preferable, step 408 is a confirmation of whether TDD service is in fact currently available. For example, if the received RAB request was issued by a WTRU operating within a TDD cell and it is determined that the request should be handled within a TDD cell, TDD service is obviously available.
• the present invention confirms that TDD service is also available prior to handing the WTRU over from FDD to TDD. Therefore, if in step 408 it is determined that the WTRU is within a TDD cell, the requested service is provided in a TDD cell in step 410. However, if it is determined that the WTRU is not within a TDD cell (i.e. TDD service is not available), the requested service is provided to the WTRU in a FDD cell (step 414). Note in this situation that although the WTRU is not being serviced in a preferred cell (i.e.
• step 406 it is determined that the requested service is preferably handled in a FDD cell, the method 400 proceeds from step 406 to step 412.
• step 412 it is determined whether the WTRU that requires the RAB is within a FDD cell. That is, although it has been determined in step 408 that FDD is preferable, step 412 is a confirmation of whether FDD service is in fact currently available.
• the present invention confirms that FDD service is also available prior to handing the WTRU over from TDD to FDD. Therefore, if in step 412 it is determined that the WTRU is within a FDD cell, the requested service is provided in a FDD cell in step 414. However, if it is determined that the WTRU is not within a FDD cell (i.e.
• the requested service is provided to the WTRU in a TDD cell (step 410).
• a preferred cell i.e. a FDD cell
• the WTRU is provided with its requested service in TDD which is the system in which the WTRU was operating when the RAB was requested.
• WTRU location may be monitored to determine whether the WTRU moves into a FDD cell or FDD service otherwise becomes available.
• Existing connections may also be evaluated in step 416 with respect to symmetry (i.e. the connection's symmetry status), data rate, application type, and/or any other relevant parameters to determine whether the type of cell a WTRU is currently operating in, is still the WTRU's preferred cell. That is, while an initial evaluation may lead to a determination that a TDD cell is preferred, conditions or usage may change causing a FDD cell to become preferred.
• step 416 Based on the evaluation(s) performed in step 416, if it is possible to perform any type of optimization (i.e. move a WTRU from one type of cell to another, for example), the method 400 proceeds from step 418 to step 420 and reallocates the current cell allocation as appropriate. Once the reallocation is complete, the method 400 may return to step 416 to look for additional optimizations. If, based on the evaluations of step 416, no optimizations are currently possible, the method 400 may return to directly to step 416 and continue monitoring and evaluating existing connections for purposes of detecting any possible optimizations.
• any type of optimization i.e. move a WTRU from one type of cell to another, for example
• TDD and FDD RNCs may be provided, but only a single lu connection to a core network is needed.
• the lu connection is provided between the core network and an RNC belonging to the RNC type (i.e. either TDD or FDD) that is the dominant type of technology in the system. That is, the majority of coverage provided by the system may be TDD in which case TDD is the dominant system type and the lu connection is provided between the core network and a TDD RNC.
• the system 500 shown in Figure 5 is a FDD system having a wide area of coverage 550 wherein FDD is the dominant type of technology. Within the FDD coverage area 550 are a plurality of TDD hotspots 552, 554, 556, 558 wherein higher data rates are available.
• TDD-FDD selector 510 determines that a particular request should be handled in TDD and TDD service is available (eg. WTRU 524)
• the connection is transferred to TDD RNC 504 and is handled within the TDD portion (eg. RNC 504, base stations 570, 572) of system 500. That is, typical TDD radio resource management may be used while a WTRU 524 is operating within the TDD portion of system 500.
• typical FDD radio resource management may be used.
• the FDD RNC 508 as explained above, additional functionality is preferably provided in the FDD RNC 508.
• the FDD RNC 508 is configured as shown in Figure 6.
• the FDD RNC 508 includes a FDD RRM 604 and is configured to perform lu protocols 602, FDD Iub protocols 606, and FDD Iur protocols 610, as normal.
• the FDD RNC 508 includes a TDD serving radio network controller (S-RNC) radio resource manager (RRM) 608 and is configured to perform TDD Iur protocols 610.
• S-RNC TDD serving radio network controller
• RRM radio resource manager
• TDD SRNC RRM 608 and TDD Iur protocols 610) is similar to the functionality already performed in a typical FDD RNC and may be added, for example, as a software upgrade.
• the TDD RNC 504 is preferably configured to include a controlling RNC (C-RNC) TDD RRM 612 and is further configured to support TDD Iub protocols 614 and TDD Iur protocols 613, as normal.
• C-RNC controlling RNC
• Configuring an RNC as shown in FDD RNC 508 allows the configuration of a TDD RNC 504 to be less complex and therefore easier and cheaper to deploy. That is, having a single lu connection between the core network 502 and the FDD RNC 508 and thereby eliminating the need for the TDD RNC 504 to support lu protocols allows for quick deployment of TDD networks within a wider area FDD network.
• the TDD RNC 504 will never be in a S-RNC mode and therefore also does not need to support the standard functionality of a S-RNC. This is because, as mentioned above, WTRUs operating within the system 500 are always forced to access the FDD RNC 508 at call connection and disconnection.
• broadcast and access control channels are only set up in the FDD RNC 508 and therefore only when a RAB is assigned by TDD-FDD selector 510 to TDD can a WTRU such as WTRU 524 get into the TDD portion of system 500.
• the WTRU 524 Once assigned to the TDD portion of system 500, the WTRU 524 operates as normal within the TDD coverage areas and is handed over between TDD cells or back to the FDD RNC 508 as appropriate.
• the handover decisions between TDD cells in handled in accordance with standard TDD functionality while decisions on whether a WTRU should be handed back to a FDD RNC area is preferably determined by the TDD-FDD selector 510.
• FIG. 7 is a block diagram of an RNC 700 including a TDD-FDD selector 702 in accordance with alternate embodiment of the present invention.
• the RNC 700 is capable of switching between a TDD mode and a FDD mode.
• the RNC 700 preferably includes both an FDD RRM 708 and a TTD RRM 710 so that the RNC 700 may perform radio resource management for both TDD and FDD modes of communication.
• the TDD-FDD selector 702 may be included in another entity, such as Node-B or any other RNC functional entity.
• the RNC 700 may be a standalone RNC entity or a combination device that includes RNC functionality in its implementation, such as a General Packet Radio Service Serving Node (GSN)/RNC, or an RNC/Node B.
• GSN General Packet Radio Service Serving Node
• RNC/Node B an RNC/Node B.
• the FDD/TDD selector 702 includes a handover unit 704 and a policy server 706.
• the handover unit 704 performs a TDD-FDD handover and a FDD-TDD handover in accordance with an output of the policy server 706.
• the policy server 706 receives inputs related to one or more policies and makes a determination regarding a proper mode of communication.
• One or more policies are defined for initiating a FDD/TDD handover.
• Typical policy categories include: 1) Quality of Service (QoS); 2) Service; 3) Management; and 4) Behavior, but may include any additional categories as desired.
• the QoS policy defines the QoS condition such as a power or quality threshold.
• the service policy defines the service characteristic conditions, such as data rate asymmetry or real time (RT) service (e.g. a voice call) vs. non-real time (NRT) service (e.g. web browsing).
• the management policy defines the operation, administration and maintenance (OA&M) conditions. This includes RT policies applied for load balancing purposes, or NRT aspects relating to maintenance.
• the behavior policy defines one or more user behavior conditions, such as user location, or speed.
• Policies are defined as part of system configuration and may be independent or interdependent. For example, a management policy may take precedence over a QoS or service policy. Relevant inputs related to each policy are input to the policy server. The inputs to the policy server are provided by general RNC Control Logic, RRM functions or by an external entity, such as an OAM function. The policies may be defined or otherwise configured as desired thereby enabling service requests to be handled in either FDD mode or TDD mode, as desired.
• FDD selector 702 requests the policy server to make a decision regarding a proper mode of communication.
• the TDD-FDD selector 702 performs either a selection of a proper mode of communication or a transition between an FDD mode and a TDD mode in accordance with the decision made by the policy server 706.
• Figure 8 is a flow diagram of a process 800 for handover between a
• a WTRU establishes a communication in a particular communication mode (step 802).
• the WTRU requests a particular service, such as web browsing (step 804).
• the RNC 700 determines whether one or more of a plurality of predetermined policies is satisfied for the service request such that a transition of the mode of communication should occur (step 806). If one or more of the policies are met, (such as QoS, location, speed, etc.), the policy server 706 indicates that the communication mode in which the service should be granted, and the RNC 700 performs a transition of the communication mode in accordance with that indication (step 808). If not, the RNC 700 maintains the current mode of communication (810).
• TDD mode relevant inputs of each policy are input to the policy server. If one or more of the policy conditions for TDD to FDD handover is met, the policy server 706 indicates that a transition to FDD mode should occur and the RNC 700 performs the transition to FDD mode.
• TDD Time division duplex
• FDD frequency division duplex
• the present invention may be implemented in any type of wireless communication system employing any type of time division duplex (TDD) technology or any type of frequency division duplex (FDD) technology, as desired.
• TDD time division duplex
• FDD frequency division duplex
• the present invention may be implemented in UMTS-TDD, UMTS-FDD, TDMA, TDSCDMA, or any other similar type of wireless communication system.
• the present invention has been described in terms of various embodiments, other variations, which are within the scope of the invention as outlined in the claim below will be apparent to those skilled in the art.

Landscapes

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

Priority Applications (5)

Applications Claiming Priority (2)

Publications (1)

Family

ID=34393153

Family Applications (1)

Country Status (9)

Cited By (3)

Families Citing this family (8)

Citations (4)

Family Cites Families (4)

• 2004
  • 2004-09-15 KR KR1020077006102A patent/KR20070041633A/ko not_active Application Discontinuation
  • 2004-09-15 CN CNA2004800278581A patent/CN1871865A/zh active Pending
  • 2004-09-15 KR KR1020067007970A patent/KR100833639B1/ko not_active IP Right Cessation
  • 2004-09-15 MX MXPA06003302A patent/MXPA06003302A/es active IP Right Grant
  • 2004-09-25 JP JP2006528205A patent/JP2007507180A/ja active Pending
  • 2004-09-25 CA CA002539728A patent/CA2539728A1/en not_active Abandoned
  • 2004-09-25 WO PCT/US2004/031366 patent/WO2005032172A1/en active Application Filing
  • 2004-09-25 EP EP04784970A patent/EP1665839A4/en not_active Withdrawn
  • 2004-09-25 KR KR1020097020561A patent/KR20090122369A/ko not_active Application Discontinuation
  • 2004-09-27 TW TW093129317A patent/TWI267275B/zh not_active IP Right Cessation
  • 2004-09-27 TW TW094112770A patent/TW200616385A/zh unknown
• 2006
  • 2006-04-25 NO NO20061825A patent/NO20061825L/no unknown

Patent Citations (4)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events