METHOD AND APPARATUS FOR TRANSFERRING WIRELESS TRANSMIT/RECEIVE UNIT CAPABILITY INFORMATION

Information

  • Patent Application
  • 20230216623
  • Publication Number
    20230216623
  • Date Filed
    March 09, 2023
    a year ago
  • Date Published
    July 06, 2023
    a year ago
Abstract
A wireless transmit/receive unit (WTRU) and a method for use by the WTRU are disclosed. The method includes transmitting, over an interface, to a controlling node a request for wireless transmit receive unit (WTRU) information, and receiving, over the interface, the WTRU information including WTRU capabilities information in response to the request, wherein the WTRU capabilities information indicates time intervals associated with numerations for shared channel allocation usage by the WTRU. A control node is also disclosed where the control note includes a processor and interface for receiving, over the interface, from a base station a request for WTRU information, and transmitting, over the interface, the WTRU information including WTRU capabilities information in response to the request, wherein the WTRU capabilities information indicates time intervals associated with numerations for shared channel allocation usage by the WTRU.
Description
FIELD OF INVENTION

The present invention is related to a wireless communication system. More particularly, the present invention is a method and system for transferring wireless transmit/receive unit (WTRU)-specific information.


BACKGROUND

In wireless communication systems implementing the Third Generation Partnership Project (3GPP) standards, the Radio Network Controller (RNC) maintains overall control of transmissions to WTRUs and knows the capabilities of each WTRU. However, the current scheme often incurs problems with throughput and transmission latency. In order to improve upon the current scheme, the Node-Bs may be relied upon to schedule and assign uplink (UL) radio resources to WTRUs. Node-Bs can make more efficient decisions and manage UL radio resources on a short-term basis better than an RNC, even if the RNC retains overall control over Node-Bs.


In order for a Node-B to assign UL radio resources to WTRUs in enhanced uplink (EU) operation, the Node-B must know several WTRU-specific parameters. Under the current 3GPP standard, only the RNC knows the WTRU-specific parameters. The RNC obtains this information via radio resource control (RRC) messages conveying WTRU-specific information. Therefore, it is necessary to forward the information to the Node-B for proper scheduling of radio resources in EU transmissions.


SUMMARY

The present invention is a method and system for transferring WTRU-specific information to the Node-Bs to support EU operation in a wireless communication system. An RNC obtains WTRU-specific information and transfers the WTRU-specific information to the Node-Bs. Each Node-B is configured to schedule UL transmissions from a WTRU and utilizes the WTRU-specific information in operation of EU transmissions.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a diagram of a wireless communication system.



FIG. 2 is a block diagram for transferring WTRU-specific information among network entities in accordance with the present invention.



FIG. 3 is a flow diagram of a process for transferring WTRU-specific information in accordance with the present invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention will be described with reference to the drawing figures wherein like numerals represent like elements throughout.


Hereafter, the terminology “WTRU” includes but is not limited to a user equipment, a mobile station, a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment. When referred to hereafter, the terminology “Node-B” includes but is not limited to a base station, a site controller, an access point or any other type of interfacing device in a wireless environment.



FIG. 1 is a block diagram of a wireless communication system 100 in which an RNC 106 controls a plurality of Node-Bs 104, (only one being shown), and each Node-B 104 covers one or more cells 108a, 108b, 108c. There is typically one “serving cell” that serves the WTRU 102, but the WTRU 102 may be in soft handover with several cells at one time. For example, in EU operation, UL transmissions are scheduled and radio resources are assigned by the Node-B 104 to the WTRU 102 through a “serving” cell, for example cell 108c, to which the WTRU 102 has established a connection. The WTRU 102 may also be connected to other cells in support of soft handover.



FIG. 2 is a block diagram of a system 200 for transferring WTRU-specific information to support EU operation in accordance with the present invention. The system 200 includes at least one WTRU 202, at least one Node-B 204, and at least one RNC 206. Communication links support signaling 208, 210, 212 between the WTRU 202, the Node-B 204 and the RNC 206. Initially, an RNC 206 obtains WTRU-specific information from a WTRU 202 using RRC messaging 208 during the initial connection. The information transferred from the WTRU 202 that is needed by the Node-B 204 is primarily physical transmission and reception capability information. The WTRU-specific information is then forwarded from the RNC 206 to a Node-B 204 to be used in scheduling UL transmissions for the WTRU 202.


A new signaling procedure may be utilized to transfer the information from the RNC 206 to the Node-B 204. Alternatively, the existing mechanisms, (for example the Radio Link Setup procedure over lur and lub interfaces), may be modified in order for the RNC 206 to forward relevant WTRU-specific information to the Node-B 204. Although the specific protocol or format used to transmit the information is not critical to the present invention, by way of the present example, the transfer of the information from the RNC 206 to the Node-B 204 is via lub interface 210 and lur interface. The RNC 206 transfers the WTRU-specific information to the Node-B 204 via the Radio Network Subsystem Application Protocol (RNSAP) control procedure (over the lur interface) and the Node B Application Part (NBAP) control protocol (over the lur interface). This information may be signaled along with the Radio Link Setup procedure in the UTRAN.


The forwarding of the WTRU-specific information may occur in response to a discrete event, such as when the WTRU 202 enters or establishes service in the service area covered by the RNC 206, or when the WTRU 202 leaves the service area. Alternatively, the forwarding of the WTRU specific information may occur periodically during the lifetime of a radio link whereby the WTRU 202 updates the WTRU-specific information.


The transfer of the WTRU-specific information may be initiated by either the RNC 206 or the Node-B 204. If it is initiated by the RNC 206, the WTRU-specific information is transferred at the initiation of the service or at the detection of change of WTRU-specific information from the RNC 206 to the Node-Bs 204. Alternatively, a Node-B 204 may request the information to be forwarded from the RNC 206 to the Node-B 204, and the RNC 206 subsequently transfers the information upon receipt of the request from the Node-B 204.


WTRU-specific information includes, but is not limited to: WTRU capabilities with respect to EU; information affecting data rates and throughput; and information regarding physical and transport channel characteristics allocated to a WTRU and relevant to a Node-B.


Information affecting data rates and throughput includes, but is not limited to: the number of multi-codes supported for UL physical channels; modulation schemes and coding rates supported for UL physical channels; automatic repeat request (ARQ) buffer or memory sizes in the WTRU; WTRU power class; number of hybrid ARQ (H-ARQ) processes supported in the WTRU; the form of available WTRU memory for EU; supported bit rates and bits receivable per transmit time interval (TTI) at layer 1 (L1) or layer 2 (L2) level; and capability for simultaneous reception of other than EU-specific channels by the WTRU.


Information on physical and transport channel characteristics includes, but is not limited to: maximum or minimum power settings of UL or DL physical channels; shared or dedicated physical channels allocated by that WTRU (spreading and scrambling codes, periodicity or enumerations of time intervals when the WTRU can be allocated shared channel usage); and information on HSDPA WTRU capability class for DL services.


The present invention is applicable to both frequency division duplex (FDD) and time division duplex (TDD) modes. Because of the commonality of higher layer (RRC or via lur/lub) signaling for FDD and TDD modes, all parameters listed above also apply to a TDD mode. For a TDD application, some TDD-only parameters should also be included, such as number of EU TDD service timeslots per WTRU, number of EU TDD spreading codes per WTRU and per time slot, and allowable and configurable power settings of physical channels of EU TDD WTRU per timeslot and per WTRU.


High Speed Data Packet Architecture (HSDPA) WTRU capabilities for DL data transmissions have several common attributes to EU WTRU capabilities for UL data transmissions. Since a Node-B provides scheduling of both DL HSDPA and UL EU services, the Node-B has the ability to dynamically distribute capabilities between UL and DL services, potentially on a TTI basis, and to better determine UL and DL transmissions for improved quality of service (QoS) and more efficient use of radio resources.



FIG. 3 is a flow diagram of a process 300 for transferring WTRU-specific information in accordance with the present invention. A WTRU 202 establishes a connection 212 to a Node-B 204 in a region covered by an RNC 206 (step 202). The RNC 206 obtains WTRU-specific information from the WTRU 202 using RRC messaging (step 204). The RNC 206 transfers the WTRU-specific information to the Node-B 204 (step 206). The transfer of WTRU-specific information may be initiated by the Node-B 204. The Node-B 204 is configured to schedule UL transmissions from the WTRU 202, and utilize the WTRU-specific information in operation of EU transmission.


Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone (without the other features and elements of the preferred embodiments) or in various combinations with or without other features and elements of the present invention.

Claims
  • 1. A base station comprising: a processor; andan interface,wherein the processor and the interface are configured to:transmit over the interface to a controlling node a request for wireless transmit receive unit (WTRU) information; andreceive, over the interface, the WTRU information including WTRU capabilities information in response to the request, wherein the WTRU capabilities information indicates time intervals associated with numerations for shared channel allocation usage by the WTRU.
  • 2. The base station of claim 1, wherein the WTRU information includes simultaneous reception capability information.
  • 3. The base station of claim 1, wherein the WTRU information includes physical layer capability information and buffer size information.
  • 4. The base station of claim 1, wherein the WTRU information includes power class information and modulation capability information.
  • 5. The base station of claim 1, wherein the WTRU information includes hybrid automatic repeat request (HARQ) capabilities information and quality of service (QoS) capabilities information.
  • 6. The base station of claim 1, wherein the WTRU information includes layer 2 capabilities information and number of supported channels capability information.
  • 7. The base station of claim 1, wherein the processor uses the WTRU information to schedule the WTRU.
  • 8. A method performed by a base station, the method comprising: transmitting, over an interface, to a controlling node a request for wireless transmit receive unit (WTRU) information; andreceiving, over the interface, the WTRU information including WTRU capabilities information in response to the request, wherein the WTRU capabilities information indicates time intervals associated with numerations for shared channel allocation usage by the WTRU.
  • 9. The method of claim 8, wherein the WTRU information includes simultaneous reception capability information.
  • 10. The method of claim 8, wherein the WTRU information includes physical layer capability information and buffer size information.
  • 11. The method of claim 8, wherein the WTRU information includes power class information and modulation capability information.
  • 12. The method of claim 8, wherein the WTRU information includes hybrid automatic repeat request (HARQ) capabilities information and quality of service (QoS) capabilities information.
  • 13. The method of claim 8, wherein the WTRU information includes layer 2 capabilities information and number of supported channels capability information.
  • 14. The method of claim 8, wherein the processor uses the WTRU information to schedule the WTRU.
  • 15. A control node comprising: a processor; andan interface,wherein the processor and the interface are configured to:receive, over the interface, from a base station a request for wireless transmit receive unit (WTRU) information; andtransmit, over the interface, the WTRU information including WTRU capabilities information in response to the request, wherein the WTRU capabilities information indicates time intervals associated with numerations for shared channel allocation usage by the WTRU.
  • 16. The control node of claim 15, wherein the WTRU information includes simultaneous reception capability information.
  • 17. The control node of claim 15, wherein the WTRU information includes physical layer capability information and buffer size information.
  • 18. The control node of claim 15, wherein the WTRU information includes power class information and modulation capability information.
  • 19. The control node of claim 15, wherein the WTRU information includes hybrid automatic repeat request (HARQ) capabilities information and quality of service (QoS) capabilities information.
  • 20. The control node of claim 15, wherein the WTRU information includes layer 2 capabilities information and number of supported channels capability information.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional application Ser. No. 17/701,119, filed Mar. 22, 2022, which is a continuation of U.S. Non-Provisional application Ser. 17/525,322, filed Nov. 12, 2021, now U.S. Pat. No. 11,424,875, which is a continuation of U.S. Non-Provisional application Ser. No. 17/099,379, filed Nov. 16, 2020, now U.S. Pat. No. 11,177,914, which is a continuation of U.S. Non-Provisional application Ser. No. 16/290,686, filed Mar. 1, 2019, now U.S. Pat. No. 11,101,946, which is a continuation of U.S. Non-Provisional application Ser. No. 15/722,759, filed Oct. 2, 2017, now U.S. Pat. No. 10,225,053, which is a continuation of U.S. Non-Provisional application Ser. No. 14/845,703, filed Sep. 4, 2015, now U.S. Pat. No. 9,780,927, which is a continuation of U.S. Non-Provisional application Ser. No. 14/186,375, filed Feb. 21, 2014, now U.S. Pat. No. 9,379,860, which is a continuation of U.S. Non-Provisional application Ser. No. 13/589,723, filed Aug. 20, 2012, now U.S. Pat. No. 8,665,798, which is a continuation of U.S. Non-Provisional application Ser. No. 12/901,931, filed Oct. 11, 2010, now U.S. Pat. No. 8,270,351, which is a continuation of U.S. Non-Provisional application Ser. No. 12/559,641, filed Sep. 15, 2009, now U.S. Pat. No. 7,813,328, which is a continuation of U.S. Patent application Ser. No. 10/980,723, filed Nov. 3, 2004, now U.S. Pat. No. 7,599,339, which claims the benefit of U.S. Provisional Application No. 60/519,436 filed Nov. 12, 2003, which are incorporated by reference as if fully set forth.

Provisional Applications (1)
Number Date Country
60519436 Nov 2003 US
Continuations (11)
Number Date Country
Parent 17701119 Mar 2022 US
Child 18181314 US
Parent 17525322 Nov 2021 US
Child 17701119 US
Parent 17099379 Nov 2020 US
Child 17525322 US
Parent 16290686 Mar 2019 US
Child 17099379 US
Parent 15722759 Oct 2017 US
Child 16290686 US
Parent 14845703 Sep 2015 US
Child 15722759 US
Parent 14186375 Feb 2014 US
Child 14845703 US
Parent 13589723 Aug 2012 US
Child 14186375 US
Parent 12901931 Oct 2010 US
Child 13589723 US
Parent 12559641 Sep 2009 US
Child 12901931 US
Parent 10980723 Nov 2004 US
Child 12559641 US