Method and apparatus for managing radio resources in a multi-wireless access technology wireless system
The method for multi-RAT operation in wireless communication systems addresses the challenge of underutilized radio resources by enabling simultaneous operation across different RATs, optimizing spectrum use and enhancing data rates and service continuity.
Patent Information
- Application Number
- JP2024006027
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2011-07-29
- Filing Date
- 2024-01-18
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2032-07-25
AI Technical Summary
Existing wireless communication systems face challenges in efficiently managing radio resources across multiple radio access technologies (RATs), leading to underutilization of spectrum and capacity, especially when carriers need to support both HSPA and LTE services, due to limited frequency bands and legacy deployments.
A method and apparatus for a wireless transceiver unit (WTRU) configured for multi-RAT operation, allowing simultaneous or near-simultaneous operation on multiple frequencies using different RATs, with a single RRC instance managing radio resources across all configured RATs.
Enables efficient utilization of radio resources and spectrum, enhancing data rates and service continuity by allowing WTRUs to operate simultaneously on multiple frequencies using different RATs, thereby optimizing network performance and reducing costs.
Smart Images

Figure 0007948977000001 
Figure 0007948977000002 
Figure 0007948977000003
Abstract
Description
Technical Field
[0001] The present invention relates to wireless communication technology.
[0002] Cross-reference of related applications This application claims the benefit of U.S. Provisional Application No. 61 / 513,180, filed July 29, 2011, the contents of which are incorporated herein by reference in their entirety.
Background Art
[0003] The demand for improved network coverage, improved capacity, and increased bandwidth for voice and data services in wireless systems has led to the continuous development of numerous radio access technologies (RATs). Examples of such RATs include, for example, Global System for Mobile Communications (GSM®), Wideband Code Division Multiple Access (WCDMA®), High-Speed Packet Access (which may include High-Speed Downlink Packet Access (HSDPA) and High-Speed Uplink Packet Access (HSUPA), and their respective multi-carrier versions), Long Term Evolution (LTE) of the 3rd Generation Partnership Project (3GPP) (which may include support for carrier aggregation in LTE Release 10 and later), IEEE 802.11b / a / g / n, IEEE 802.16a / e, IEEE 802.20, Code Division Multiple Access 2000 1x (CDMA2000 1x), and cdma2000 Evolution Data Optimized (cdma2000 EV-DO) of the 3rd Generation Partnership Project 2 (3GPP2).
Summary of the Invention
Problems to be Solved by the Invention
[0004] A novel method and apparatus for radio resource management in a multi-radio access technology wireless system are provided.
Means for Solving the Problems
[0005] A method and apparatus for performing wireless communication in a wireless transceiver unit (WTRU) configured for multi-RAT operation is disclosed. The method includes the steps of the WTRU wirelessly transmitting information on a first operating frequency according to a first RAT, and wirelessly transmitting information on a second operating frequency according to a second RAT. [Effects of the Invention]
[0006] This invention provides a method and apparatus for managing wireless resources in a novel multi-wireless access technology wireless system. [Brief explanation of the drawing]
[0007] A more detailed understanding can be obtained from the following explanation, which is given by example and accompanied by the attached drawings. [Figure 1A] This is a diagram of an exemplary communication system that can implement the disclosed embodiments. [Figure 1B] Figure 1A is a system diagram of an exemplary wireless transceiver unit (WTRU) that can be used in the communication system shown. [Figure 1C] Figure 1A is a system diagram of an exemplary radio access network and an exemplary core network that can be used within the communication system shown. [Figure 2] This is a block diagram of an exemplary system for multi-RAT communication. [Figure 3] This is an exemplary control plane block diagram for multi-RAT operation, using one RRC instance and one RRC connection per WTRU. [Figure 4] This is a flowchart illustrating an exemplary method for performing wireless communication in a WTRU configured for multi-RAT operation corresponding to the embodiment shown in Figure 3. [Figure 5] This is an illustrative control plane block diagram for multi-RAT operation, using one RRC connection per WTRU, for each configured RAT's RRC instance. [Figure 6] This is a flowchart illustrating an exemplary method for performing wireless communication in a WTRU configured for multi-RAT operation corresponding to the embodiment shown in Figure 5. [Figure 7] This is an exemplary control plane block diagram for multi-RAT operation, using RRC instances and RRC connections for each configured RAT. [Figure 8] This is a flowchart illustrating an exemplary method for performing wireless communication in a WTRU configured for multi-RAT operation corresponding to the embodiment shown in Figure 7. [Figure 9] This block shows the E-UTRA RRC status and the mobility support between E-UTRAN, UTRAN, and GERAN. [Modes for carrying out the invention]
[0008] Figure 1A is a diagram of an exemplary communication system 100 that can implement one or more disclosed embodiments. The communication system 100 can be a multiple access system that provides content such as voice, data, video, messaging, and broadcast to multiple wireless users. The communication system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 can utilize one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), quadrature FDMA (OFDMA), and single-carrier FDMA (SC-FDMA).
[0009] As shown in Figure 1A, the communication system 100 may include wireless transceiver 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 other networks 112, but it will be understood that the disclosed embodiments intend any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d may be configured to transmit and / or receive wireless signals and may include user equipment (UEs), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, and consumer electronics.
[0010] The communication system 100 may also include base stations 114a and 114b. Each of the base stations 114a and 114b can be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks such as the core network 106, the internet 110, and / or network 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, enode B, home node B, home enode B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are shown as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.
[0011] Base station 114a may be part of RAN 104, which may also include other base stations and / or network elements (not shown) such as base station controllers (BSCs), radio network controllers (RNCs), and relay nodes. Base stations 114a and / or base stations 114b may be configured to transmit and / or receive wireless signals within a specific geographic area, which may be called 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, base station 114a may include three transceivers, i.e., one for each sector of the cell. In another embodiment, base station 114a may utilize multiple-input multiple-output (MIMO) technology, and thus multiple transceivers may be available for each sector of the cell.
[0012] Base stations 114a and 114b can communicate with one or more WTRUs 102a, 102b, 102c, and 102d via an air interface 116, the air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 can be established using any suitable radio access technology (RAT).
[0013] More specifically, as mentioned above, the communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 can implement radio technologies such as Universal Mobile Communications System (UMTS) Terrestrial Radio Access (UTRA), which can establish an air 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).
[0014] In another embodiment, base stations 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as Advanced UMTS Terrestrial Radio Access (E-UTRA), which can establish an air interface 116 using Long-Term Evolution (LTE) and / or LTE Advanced (LTE-A).
[0015] In other embodiments, base stations 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.16 (i.e., Global Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM®), High Speed Data Rate for GSM Evolution (EDGE), and GSM EDGE (GERAN).
[0016] The base station 114b in Figure 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any appropriate RAT to facilitate wireless connectivity in localized areas such as workplaces, homes, vehicles, and campuses. 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 utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As shown in Figure 1A, the base station 114b may have a direct connection to the Internet 110. Accordingly, the base station 114b may not need to access the Internet 110 via the core network 106.
[0017] RAN 104 can communicate with core network 106, which can be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. For example, core network 106 can provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in Figure 1A, it will be understood that RAN 104 and / or core network 106 can communicate directly or indirectly with other RANs that utilize the same RAT as RAN 104 or a different RAT. For example, in addition to connecting to RAN 104 which can utilize E-UTRA radio technology, core network 106 can also communicate with another RAN (not shown) that utilizes GSM radio technology.
[0018] The core network 106 can also serve as a gateway for WTRU 102a, 102b, 102c, and 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing basic telephone services (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) within the TCP / IP Internet Protocol Suite. Network 112 may include wired or wireless networks owned and / or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs that have the same or different RATs as RAN 104.
[0019] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode functionality, that is, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links. For example, the WTRU 102c shown in Figure 1A may be configured to communicate with the base station 114a that may utilize cellular-based radio technology, and to communicate with the base station 114b that may utilize IEEE 802 radio technology.
[0020] Figure 1B is a system diagram of an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripherals 138. The WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0021] The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors working with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 can perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to the transceiver 120, and the transceiver 120 can be coupled to the transmit / receive element 122. Although Figure 1B shows the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.
[0022] The transmit / receive element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 may be a radiator / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and optical signals. It will be understood that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.
[0023] In addition, although the transmit / receive element 122 is shown as a single element in Figure 1B, the WTRU 102 can include any number of transmit / receive elements 122. More specifically, the WTRU 102 can utilize MIMO technology. Therefore, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interface 116.
[0024] The transceiver 120 can be configured to modulate the signal transmitted by the transmit / receive element 122 and to demodulate the signal received by the transmit / receive element 122. As mentioned above, the WTRU 102 can have multimode capabilities. Therefore, the transceiver 120 can include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.
[0025] The processor 118 of the WTRU102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit) and can receive user input data from them. The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 can retrieve information from any type of suitable memory, such as a non-removable memory 130 and / or removable memory 132, and can store data in them. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identification module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 can obtain information from memory located on a server or home computer (not shown), rather than from memory physically located on the WTRU 102, and can store data in such memory.
[0026] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components within the WTRU 102. The power supply 134 can be any suitable device for supplying power to the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), a solar cell, a fuel cell, etc.
[0027] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or instead of, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its own position based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may acquire location information using any suitable positioning method while maintaining consistency with one embodiment.
[0028] The processor 118 can be further coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripherals 138 may include an accelerometer, e-compass, satellite transceiver, digital camera (for photos or videos), Universal Serial Bus (USB) port, vibration device, TV transceiver, hands-free headset, Bluetooth® module, frequency modulation (FM) radio unit, digital music player, media player, video game player module, internet browser, and the like.
[0029] Figure 1C is a system diagram of RAN 104 and core network 106 according to one embodiment. As mentioned above, RAN 104 can utilize E-UTRA radio technology to communicate with WTRU 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with core network 106.
[0030] RAN104 may include e-nodes B140a, 140b, and 140c, but it will be understood that RAN104 may include any number of e-nodes B while maintaining consistency with one embodiment. Each of the e-nodes B140a, 140b, and 140c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, e-nodes B140a, 140b, and 140c can implement MIMO technology. Thus, e-node B140a can, for example, use multiple antennas to transmit wireless signals to and receive wireless signals from WTRU102a.
[0031] Each of the e-nodes B140a, 140b, and 140c can be associated with a specific cell (not shown) and can be configured to handle wireless resource management decisions, handover decisions, user scheduling on uplink and / or downlink, etc. As shown in Figure 1C, the e-nodes B140a, 140b, and 140c can communicate with each other via the X2 interface.
[0032] The core network 106 shown in Figure 1C may include a mobility management gateway (MME) 142, a serving gateway 144, and a packet data network (PDN) gateway 146. Although each of the above elements is shown as part of the core network 106, it will be understood that any one of these elements may be owned and / or operated by an entity other than the core network operator.
[0033] The MME142 can connect to each of the e-nodes B142a, 142b, and 142c within RAN104 via the S1 interface and can act as a control node. For example, the MME142 can be responsible for user authentication of WTRU102a, 102b, and 102c, bearer activation / deactivation, and selection of a specific serving gateway during the initial connection of WTRU102a, 102b, and 102c. The MME142 can also provide control plane functionality for exchanges between RAN104 and other RANs (not shown) utilizing other radio technologies such as GSM or WCDMA.
[0034] The serving gateway 144 can connect to each of the e-nodes B140a, 140b, and 140c in the RAN104 via the S1 interface. The serving gateway 144 can generally route and forward user data packets to and from WTRU102a, 102b, and 102c. The serving gateway 144 can also perform other functions, such as anchoring the user plane during e-node B handover, triggering a broadcast call when downlink data is available to WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.
[0035] The serving gateway 144 can also be connected to the PDN gateway 146, which can provide WTRU 102a, 102b, and 102c with access to a packet-switched network such as the Internet 110, thereby facilitating communication between WTRU 102a, 102b, and 102c and IP-enabled devices.
[0036] The core network 106 can facilitate communication with other networks. For example, the core network 106 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks such as PSTN 108, thereby facilitating communication between WTRU 102a, 102b, and 102c and conventional land-line communication devices. For example, the core network 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 106 and PSTN 108, or may communicate with an IP gateway. In addition, the core network 106 can provide WTRU 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0037] When RATs such as WCDMA and LTE were developed, they were designed to allow the use of two or more component carriers (CCs) for transmission and reception between the WTRU and the base station. A CC can be, for example, the frequency on which the WTRU operates. For example, a WTRU can receive transmissions on a downlink (DL) CC, and the DL CC can include multiple DL physical channels. As another example, a WTRU can perform transmissions on an uplink (UL) CC, and the UL CC can include multiple UL physical channels.
[0038] A cell may be associated with a UL CC based on an SI received by a WTRU using a dedicated configuration broadcast on the DL CC or transmitted from the network, and includes at least one DL CC. For example, if the SI is broadcast on the DL CC, the WTRU may receive the UL frequency and bandwidth of the associated UL CC as part of the SI IE (for example, if it is RRC_IDLE for LTE, or idle / CELL_FACH for WCDMA (i.e., if the WTRU does not yet have RRC connectivity to the network)).
[0039] More specifically, 3GPP WCDMA Release 8 provided support for the simultaneous use of two HSDPA component carriers (2C-HSDPA), Release 9 provided support for MIMO in multi-carrier DL WCDMA and also introduced support for two HSUPA UL CCs, and Release 10 introduced support for up to four DL CCs (4C-HSDPA). In Release 11, the number of DL CCs can be increased up to eight (8C-HSDPA). 3GPP LTE Release 10 introduced support for simultaneous transmission and / or reception, using the radio resources of multiple CCs between the base station and mobile station within the same transmit interval. The transmit time interval (TTI) for HSPA is a 2ms subframe, and the TTI for 3GPP LTE Releases 8, 9, and 10 is a 1ms subframe (each radio frame (10ms) contains 10 subframes of equal size of 1ms).
[0040] Network architectures for different RATs can support different functions in different entities within the architecture. Some RATs may perform similar functions (e.g., MAC functions) through different entities within the same architecture, and architectures for different RATs may include different entities. For example, in UTRAN, the Radio Resource Control (RRC), Packet Data Control Protocol (PDCP), Radio Link Control (RLC), Media Access Control Individual (MAC-d), and MAC-is sublayers are located within the Radio Network Controller (RNC), while Media Access Control High Speed (MAC-hs), MAC-i, and Layer 1 (L1) are located within Node B. Furthermore, in the Universal Terrestrial Radio Access Network (UTRAN), security (e.g., encryption), segmentation, and reassembly services for MAC, as well as sequential delivery services for PDCP, are provided by the RLC, while MAC ensures order between Hybrid Automatic Retransmission Request (HARQ) processes for the RLC layer. As another example, in the case of evolved UTRAN (eUTRAN), there is no RNC, and the RRC, PDCP, RLC, and MAC layers are all located within the eNode B (eNB). Security (e.g., encryption, integrity, and authentication) and sequential delivery services (e.g., during handover) are provided by the PDCP, while the RLC provides segmentation, resegmentation, and reassembly services to the MAC.
[0041] One of the design objectives of LTE Release 8 was to allow operators to deploy LTE using the same sites as for legacy WCDMA deployments, in order to reduce deployment and radio planning costs. Thus, network operators can deploy both WCDMA / HSPA and LTE within the same coverage area, and LTE deployments can have similar coverage to existing WCDMA / HSPA deployments, and multimode WTRUs supporting both WCDMA / HSPA and LTE access can be widely deployed.
[0042] However, spectrum is a costly resource, and not all frequency bands are necessarily available to all carriers. Therefore, while carriers are expected to be able to provide support for both HSPA and LTE services, carrier aggregation scenarios may be limited to at most two to three component carriers per RAT for a given carrier. In addition, legacy deployments may be maintained in the near future while LTE is being deployed, which could result in carriers experiencing periods where radio resources / spectrum and capacity are underutilized on one side of the RAT.
[0043] HSPA Release 10 with MIMO offers a downlink peak data rate of 42 Mbps, and Release 10 multi-carrier HSPA can further increase the peak rate by introducing support for up to four DL CCs. LTE Releases 8 and 9 offer up to 100 Mbps in a single CC DL, and LTE Release 10 with intra-RAT carrier aggregation can further increase the peak rate by combining the transmit resources of up to five CCs. Several motivations for utilizing the combined data rate / capacity of multi-RAT deployments include, for example, reducing the cost of providing higher data rates (data enhancement scenarios), migrating from WCDMA / HSPA to LTE with limited available spectrum (migration scenarios), maximizing the use of deployed RATs (e.g., through load balancing), and maximizing the use of radio components in WTRUs (e.g., dual-band receivers).
[0044] In addition to taking advantage of increased peak rates, carriers may want to reserve frequency bands for other reasons (e.g., for home eNB deployments). Furthermore, combining HSPA resources with LTE resources can provide further means of ensuring service continuity (e.g., for circuit-switched (CS) voice and / or services requiring LTE data rates). Therefore, it may be desirable to have a method that allows WTRUs to operate simultaneously on multiple frequencies, such that the WTRUs operate on at least one of the frequencies according to different RATs.
[0045] The embodiments described herein may relate to a multimode WTRU that supports the simultaneous (or near-simultaneous) operation of multiple different RATs on a CC. The embodiments described herein may also relate to how a multimode WTRU can perform radio resource management and associated RRC procedures when using different RATs. In one embodiment, the WTRU can perform radio resource management and associated RRC procedures using different RATs on different frequencies.
[0046] Some embodiments described herein are described with respect to a first RAT which is LTE and a second RAT which is WCDMA, HSUPA, and / or HSDPA, and vice versa. However, embodiments described herein can be applied to any wireless technology. Furthermore, although not expressly described herein, embodiments described herein can be applied to WTRUs which transmit using different RATs on different frequencies only at different time intervals (i.e., some form of time-division operation based on TTI), and / or such transmissions are performed within the same frequency band.
[0047] Figure 2 is a block diagram of an exemplary system 200 for multi-RAT communication. The shown system 200 includes a WTRU 204 and two base stations (e.g., eNBs) 202 and 206. In Figure 2, one WTRU 204 communicates with the two base stations 202 and 206 using channels 208, 210, 212, and 214. Channels 208, 210, 212, and 214 can be any combination of UL and DL channels of any number of different RATs.
[0048] Multi-RAT operation can include any multimode WTRU configured simultaneously for operation using at least one CC (e.g., DL CC, UL CC, or one or more serving cells) of a first RAT and at least one CC (e.g., DL CC, UL CC, or one or more serving cells) of a second RAT. Operation on different CCs can occur simultaneously or quasi-simultaneously. For example, operation according to different RATs can be used sequentially on the same CC. A multimode WTRU can include any mobile terminal that supports multiple RATs, such as any combination of GSM, WCDMA, HSPA, HSDPA, HSUPA, LTE, IEEE 802.11b / a / g / n, IEEE 802.16a / e, IEEE 802.20, cdma2000 1x, and cdma2000 EV-DO.
[0049] A serving cell can include, for example, a primary cell (PCell) or a secondary cell (SCell). More specifically, in the case of a WTRU that is not configured to use any SCells or does not support operation on multiple CCs (carrier aggregation), there may be only one serving cell (PCell). In the case of a WTRU configured to use at least one SCell, a serving cell can include one or more cells in a set containing all configured PCells and all configured SCells.
[0050] In one embodiment, the WTRU 204 can wirelessly transmit (communicate) information on a first operating frequency according to a first RAT, and can wirelessly transmit (communicate) information on a second operating frequency according to a second RAT. Communication on the first and second operating frequencies can be performed via any combination of channels 208, 210, 212, and 214. For example, the WTRU 204 can wirelessly transmit information on a first operating frequency according to a first RAT (e.g., LTE) on DL channel 208 (e.g., LTE DL), and can wirelessly transmit information on a second operating frequency according to a second RAT (e.g., WCDMA) on DL channel 212 (e.g., WCDMA HSDPA). As another example, WTRU204 can wirelessly transmit information on a first operating frequency according to a first RAT (e.g., WCDMA) on UL channel 212 (e.g., WCDMA HSDPA), and can wirelessly transmit information on a second operating frequency according to a second RAT (e.g., LTE) on UL channel 214 (e.g., LTE UL).
[0051] WTRUs such as the WTRU204 shown in Figure 2 can be configured for multi-RAT operation. WTRUs that support access to multiple RATs can access those resources using one of several different control plane configurations and several different methods, such as the control planes and methods illustrated and described with respect to Figures 3 to 8.
[0052] Figure 3 is a block diagram of an exemplary control plane 300 for multi-RAT operation, using one RRC instance 302, one state machine 304, one RRC connection 306 per WTRU, and one or more SRBs 308. Where referred to hereafter, the term RRC instance conceptually represents the use of an RRC protocol that may include a single state machine operating with multiple RRC states (e.g., CONNECTED or IDLE in the case of the LTE RRC protocol) with corresponding state transitions, an RRC procedure (including associated timers) including RRC control and measurement procedures, an RRC PDU and information elements (IE), an RRC configuration (including parameters for the configuration of RRC, PDCP, RLC, MAC), and a physical (PHY) layer, without limiting it to possible additional embodiments or subsets of the embodiments below. In the example shown in Figure 3, one RRC instance 302 can handle the management of radio resources for all configured RATs.
[0053] In the case of HSPA, there are at least four RRC states: CELL_DCH, CELL_FACH, CELL_PCH / URA_PCH, and UTRA_IDLE. In the case of LTE, there are two RRC states: RRC_CONNECTED and RRC_IDLE. If an RRC connection is established, the WTRU is in RRC_CONNECTED. Otherwise, the WTRU is in RRC_IDLE.
[0054] In the RRC_IDLE state, the WTRU monitors at least the broadcast channel to detect incoming calls, SI changes, and, in one embodiment, early terrestrial warning system (ETWS) / commercial mobile alert system (CMAS) notifications, and performs neighbor cell measurement, cell selection, cell reselection, and SI acquisition. In the RRC_CONNECTED state, the WTRU can transmit / receive on the unicast channel and monitor at least the broadcast channel and / or SI block type 1 to detect incoming calls, SI changes, and, in one embodiment, ETWS / CMAS notifications. The WTRU can also be configured to use one or more secondary cells in addition to the primary cell.
[0055] For each of the RRC protocols described in the paragraph above, a set of states, transitions, messages (e.g., protocol data units (PDUs)), and procedures are defined. Figure 9 is a block diagram 900 showing the E-UTRA (e.g., LTE) RRC states, including, for example, the CELL_DCH state 902, CELL_FACH state 904, CELL_PCH and URA_PCH states 906, the UTRA_IDLE state 908, the E-UTRA RRC CONNECTED state 910, the E-UTRA RRC IDLE state 912, the GSM_Connected state 914, the GPRS packet forwarding mode 916, and the GSM Idle / GPRS Packet Idle state 918. Figure 9 also shows mobility support between E-UTRAN, UTRAN, and GERAN.
[0056] In one embodiment, a single RRC instance 302 can manage a single RRC connection 306, which can be used to handle radio resource management for all serving cells configured in any RAT. According to this embodiment, at any given time, there can be at most one RRC instance and one RRC connection per WTRU.
[0057] Figure 4 is a flowchart 400 of an exemplary method for performing wireless communication in a WTRU configured for multi-RAT operation, corresponding to the embodiment shown in Figure 3. In the example shown in Figure 4, the WTRU can first access the network and establish an RRC connection 306 on a first RAT (e.g., a primary RAT (PRAT)) using an RRC instance 302 (402). The WTRU can then receive a configuration to add at least one serving cell of a second RAT (e.g., a secondary RAT (SRAT)) on the RRC connection 306 (404). The WTRU can then configure wireless resources using a single RRC instance 302 (406).
[0058] A primary cell (PCell) can include cell operations on a primary frequency, such as when a WTRU performs initial access to the system (e.g., the cell where the WTRU performs the initial connection establishment procedure, the cell where the WTRU initiates the connection re-establishment procedure, or the cell designated as the primary cell in a handover procedure). A PCell can also correspond to frequencies designated as part of the RRC configuration procedure. Some functions can only be supported on a PCell. For example, a PCell UL CC can correspond to a CC where the physical UL control channel resource is configured to carry all HARQ acknowledgment / negation (ACK / NACK) feedback for a given WTRU. For example, in LTE, a WTRU can use a PCell to derive parameters about security features and parameters about higher-layer SIs such as non-access layer (NAS) mobility information. Other functions that can only be supported on a PCell DL include SI acquisition and change monitoring procedures on a broadcast channel (BCCH), as well as group calling. For example, a WCDMA PCell can be similar to an LTE PCell. A secondary cell (SCell) may include a cell operating on a secondary frequency that can be configured, for example, after an RRC connection has been established and can be used to provide additional radio resources. SIs related to the operation of the relevant SCell can be provided using dedicated signaling when the SCell is added to the WTRU configuration. Parameters may have different values than those broadcast on the relevant SCell's DL using SI signaling, but this information is sometimes referred to as the relevant SCell's SI, regardless of the method used by the WTRU to obtain this information.
[0059] The primary RAT (PRAT) (or anchored RAT) may include radio access network technology. At least one serving cell can be configured as a PCell for the PRAT. The PCell can support at least one of the following: establishing a first RRC connection; deriving security parameters (e.g., if a single security context is used); using UL resources to transmit UL control information (UCI) (e.g., if UCI is transmitted only on the serving cell of the first RAT); and / or configuring at least one serving cell with UL resources (e.g., if UL resources are configured only in the first RAT). As a result, in some embodiments, the PRAT or anchored RAT may be referred to as the first RAT. The secondary RAT (SRAT) (or non-anchored RAT) may include any serving cell configured for it that is not for the PRAT in the WTRU configuration.
[0060] In one embodiment, the WTRU can access an LTE cell and establish an RRC connection 306 using LTE as the PRAT by using the corresponding RRC connection establishment procedure. The WTRU can be configured to use additional serving cells, which may include one or more HSPA serving cells, as the SRAT by using the RRC connection reconfiguration procedure of the PRAT. In one embodiment, the RRC connection reconfiguration procedure can be performed only after security has been activated in the PRAT. Furthermore, in one embodiment, during the RRC reconfiguration procedure, the WTRU can receive an RRC message containing one or more IEs related to the HSPA configuration (e.g., SI configuration IE, radio bearer IE, transport channel IE, and physical channel IE).
[0061] In another embodiment, the WTRU can access an HSPA cell and establish an RRC connection 306 using HSPA as the PRAT by using the corresponding RRC connection establishment procedure. The WTRU can be configured to use an additional serving cell (e.g., one or more LTE serving cells) as the SRAT by using the RRC connection reconfiguration procedure for the PRAT. In one embodiment, the WTRU can be configured to use the RRC radio bearer setup procedure for the PRAT to configure PRAT-specific information and simultaneously configure the WTRU to use an SRAT serving cell. Alternatively, the WTRU can be configured to use the SRAT in the RRC connection setup by using the signaling radio bearer (SRB) of the PRAT. In one embodiment, the RRC connection reconfiguration procedure can only be performed after security has been activated in the PRAT. Furthermore, in one embodiment, the WTRU may receive an RRC message during the RRC reconfiguration procedure that includes one or more IEs relating to the LTE configuration (for example, at least one of MAC-MainConfig IE, CQI-ReportConfig IE, PDSCH-Config IE, PhysicalConfigDedicated IE, RadioResourceConfigDedicated IE, and / or RadioConfigCommon IE for the DL configuration of a serving cell, and / or at least one of PUSCH-Config IE and / or SoundingRS-UL-Config IE for the UL configuration of a serving cell, including SI configuration IEs and / or RRC IEs).
[0062] The SRB is a wireless bearer used solely for transmitting RRC and NAS messages. SRB0 is used for RRC messages using the Common Control Channel (CCH) logical channel. SRB1 is for RRC messages (e.g., with piggybacked NAS messages) and for NAS messages before the establishment of SRB2, which uses the Individual Control Channel (DCCH) logical channel. SRB2 is for NAS messages and is always configured after security is activated. After security is activated, all RRC messages on SRB1 and SRB2 can be subjected to integrity protection and encryption.
[0063] When CCs (or serving cells) from different RATs are aggregated and configured for a given WTRU, it may be necessary to have a method for handling the management of radio resource connections. In particular, when multiple RRC connections and / or state machines (SMs) can be used for multi-RAT access (e.g., one per RAT on which the WTRU operates), it may be desirable to define a method to enable proper handling of each RRC connection and the interactions that may occur between them. Alternatively, when only a single RRC connection and / or state machine can be used for multi-RAT access, it may be desirable to define a method by which that single RRC state machine can control multiple radio resources.
[0064] Figure 5 is a block diagram of an exemplary control plane 500 for multi-RAT operation, using an RRC instance for each configured RAT, a state machine for each RRC instance, and one RRC connection per WTRU. More specifically, the example shown includes an RRC instance 502 for PRAT, a state machine 504 for PRAT, an RRC instance 508 for SRAT, a state machine 506 for SRAT, a single RRC connection 510, and one or more SRBs 512. In the example shown in Figure 5, radio resources for multiple RATs (e.g., PRAT and SRAT) can be managed using multiple RRC instances (e.g., one control plane instance per configured RAT).
[0065] In one embodiment, an RRC instance 508 for an SRAT includes a subset of the RRC protocol for the associated RAT. For example, an RRC instance 508 for an SRAT can handle at least some radio resource management functions for the corresponding RAT (e.g., in-frequency and inter-frequency measurement configuration and reporting, radio link monitoring (RLM), SI maintenance, and error handling). In one embodiment, each RRC instance 508 for an SRAT can interact with an RRC instance 502 for a PRAT. In the shown embodiment, an RRC instance 502 manages a single RRC connection 510, which can be used to handle radio resource management for at least one RAT. Additional RRC instances (e.g., an RRC instance 508 for an SRAT) also exist for each additional configured RAT, which may include a subset of the RRC protocol for the associated RAT (SRAT).
[0066] In the case of an LTE serving cell, the WTRU can determine a UL radio link failure (RLF) if it has performed an RLM and reached the maximum number of preamble transmissions for a random access procedure, and / or the maximum number of repeatable failures when performing a random access procedure on the associated serving cell. Furthermore, in the case of an LTE serving cell, the WTRU can determine a DL RLF if the RRC instance receives a number of consecutive out-of-sync indications equivalent to N310 from the physical (PHY) layer, and then timer T310 expires before the WTRU recovers from the error condition that started the timer.
[0067] Figure 6 is a flowchart 600 of an exemplary method of performing wireless communication in a WTRU configured for multi-RAT operation corresponding to the embodiment shown in Figure 5. In the example shown in Figure 6, the WTRU can first access the network and establish an RRC connection 510 in a first RAT (e.g., PRAT) using a first RRC instance (RRC instance 502 for PRAT) (602). The WTRU can then receive a configuration on the RRC connection 510 to add at least one serving cell of a second RAT (e.g., SRAT) (604). The WTRU can then use a second RRC instance (RRC instance 508 for SRAT) to configure the radio resources of SRAT using RRC PDUs (e.g., received on different SRBs) and / or configuration information received on the RRC connection 510 (606). In one embodiment, the second RRC instance 508 can initially operate according to an RRC connection mode (e.g., LTE CONNECTED or HSPA CELL_DCH). The state of the RRC instance for SRAT may be inactive, or the RRC connection mode may be initiated by PRAT.
[0068] For example, a WTRU can access an LTE cell and establish an RRC connection using LTE as the PRAT by using the corresponding RRC connection establishment procedure. The WTRU can be configured to use additional serving cells as the SRAT, for example, including one or more HSPA serving cells. In one embodiment, the configuration procedure can be performed only after security has been activated in the PRAT.
[0069] In one embodiment, the configuration can be received via the PRAT's RRC connection reconfiguration procedure. In one embodiment, during the RRC reconfiguration procedure, the WTRU can receive an RRC message containing one or more IEs relating to the HSPA configuration, which may include, for example, at least one of the following: SI configuration IE, radio bearer IE, transport channel IE, physical channel IE, and secondary serving HS-DSCH IE. In one embodiment, the PRAT's RRC instance can forward the received SRAT configuration information to the corresponding SRAT's RRC instance, which can configure the corresponding radio resources of the SRAT.
[0070] In another embodiment, the configuration can be received on an SRB configured to associate with an RRC instance 508 of SRAT. In one embodiment, the WTRU can receive an RRC PDU of the SRAT RRC protocol on the SRB. In one embodiment, the RRC message can include one or more IEs relating to the HSPA configuration, which may include at least one of the following: an SI configuration IE, a radio bearer IE, a transport channel IE, and a physical channel IE. In one embodiment, the RRC instance of SRAT can perform corresponding configuration procedures, such as a radio bearer control procedure and a physical channel configuration procedure.
[0071] For example, a WTRU can access an HSPA cell and establish an RRC connection 306 using HSPA as the PRAT by using the corresponding RRC connection establishment procedure. The WTRU can be configured to use additional serving cells as the SRAT, which may include, for example, one or more LTE serving cells. In one embodiment, this configuration procedure can be performed only after security has been activated in the PRAT.
[0072] In one embodiment, the configuration can be received via the PRAT's RRC connection reconfiguration procedure. In one embodiment, the WTRU can receive an RRC message containing one or more IEs relating to the LTE configuration, which may include, for example, an SI configuration IE (which may include at least one of MAC-MainConfig IE, CQI-ReportConfig IE, PDSCH-Config IE, PhysicalConfigDedicated IE, RadioResourceConfigDedicated IE, and RadioConfigCommon IE for the DL configuration of the serving cell, and may also include at least one of PUSCH-Config IE and SoundingRS-UL-Config IE for the UL configuration of the serving cell) and an RRC IE. In one embodiment, the PRAT's RRC instance 502 can forward the configuration information received by the SRAT to a corresponding SRAT's RRC instance that can configure the corresponding radio resources of the SRAT.
[0073] In another embodiment, the configuration may be received on an SRB configured to associate with an RRC instance 508 of SRAT. In one embodiment, a WTRU may receive an RRC PDU of the SRAT RRC protocol on the SRB. In one embodiment, an RRC message may include one or more IEs relating to an LTE configuration, which may include, for example, an SI configuration IE, (including at least one of MAC-MainConfig IE, CQI-ReportConfig IE, PDSCH-Config IE, PhysicalConfigDedicated IE, RadioResourceConfigDedicated IE, and RadioConfigCommon IE for the DL configuration of a serving cell, and at least one of PUSCH-Config IE and SoundingRS-UL-Config IE for the UL configuration of a serving cell) or a radio resource control IE. In one embodiment, an RRC instance of SRAT may perform a corresponding RRC reconfiguration procedure, such as a radio resource configuration procedure.
[0074] Figure 7 is a block diagram of an exemplary control plane 700 for multi-RAT operation, using an RRC instance for each configured RAT, a state machine for each RRC instance, and an RRC connection for each configured RAT. More specifically, the example shown includes an RRC instance 702 for PRAT, a state machine 704 for PRAT, an RRC instance 708 for SRAT, a state machine 706 for SRAT, an RRC connection 710 for PRAT, an RRC connection 712 for SRAT, and one or more SRBs 714. In the example shown in Figure 7, radio resources for multiple RATs (e.g., PRAT and SRAT) can be managed using multiple RRC instances (e.g., one control plane instance per configured RAT).
[0075] Figure 8 is a flowchart 800 of an exemplary method for performing wireless communication in a WTRU configured for multi-RAT operation corresponding to the embodiment shown in Figure 7. In the example shown in Figure 8, the WTRU can establish a first RRC connection 710 in a first RAT (e.g., PRAT) using a first RRC instance 702 (802). The WTRU can also establish a second RRC connection 712 in a second RAT (e.g., SRAT) using a second RRC instance 708 (804).
[0076] In the embodiment shown in Figure 7, each RRC instance 702, 708 manages one RRC connection 710, 712 for each serving cell configured in the associated RAT.
[0077] In one embodiment, RRC connections 710, 712 can be established according to any number of different methods. In one embodiment, the WTRU can receive RRC signaling from the network over an existing RRC connection. The RRC signaling may include, for example, a request to establish an additional RRC connection to the SRAT, and parameters for uniquely identifying the relevant cell (e.g., frequency (DL and UL), cell identification information, and SI). In another embodiment, the WTRU can receive an RRC reconfiguration message from the network over an existing RRC connection indicating the addition of at least one serving cell for the SRAT. The RRC reconfiguration message may include, for example, parameters for uniquely identifying the relevant cell (e.g., frequency (DL and UL), cell identification information, and SI). In another embodiment, when a Packet Data Protocol (PDP) context is established for a new application, the WTRU can receive a request to establish an additional RRC connection to the SRAT. In another embodiment, the WTRU can autonomously initiate access to the cells of a second RAT when it is already connected to a first RAT. This embodiment can be used, for example, when WTRU supports multi-RAT access using two independent RRC instances.
[0078] A WTRU can autonomously initiate access to a cell on a second RAT, for example, in response to receiving a mass call message on a RAT, while the WTRU is camped on to a cell using an RRC instance in idle mode. Alternatively, a WTRU can autonomously initiate access to a cell on a secondary RAT if it determines that an application is requesting a service. For example, if a WTRU wants to initiate a CS call and it determines that it is a multi-RAT compatible WTRU, it can initiate access to a cell on a secondary RAT, and in one embodiment, the reason can be indicated in the RRC connection establishment. In another embodiment, a WTRU can send a request on a PRAT to the network indicating that it can initiate SRAT setup (for example, following a WTRU-specific trigger). A WTRU can send a request to the network, for example, in response to receiving a service request, and in one embodiment, the reason can be indicated in the RRC message sent on a PRAT. In this embodiment, the WTRU can wait for an explicit setup message from the network to instantiate an SRAT RRC connection.
[0079] In one embodiment, there may be no interaction between RRC instance 702 and RRC instance 708. For example, this may be the case when a multimode WTRU operates as a multihomed IP device that can be configured using NAS procedures (for example, when, from a network connectivity standpoint, each RAT may correspond to a different IP interface). More specifically, the WTRU appears to the network as a single device implementing two different IP network interfaces, each having its own PDP context (i.e., IP address), control / user data path, and security context. RRM, mobility management, scheduling, and admission control for each RRC connection can be independent of each other.
[0080] In another embodiment, additional interaction may exist between RRC instance 702 and RRC instance 708. For example, an RRC message on a first RRC connection (e.g., 710) can initiate a procedure by which the WTRU can perform at least one of the following: enter an idle mode state, camp on (or alternatively, camp on to a cell of the frequency indicated in the RRC message), acquire an SI, monitor the broadcast channel, and perform a cell selection procedure to determine a suitable cell for performing access to SRAT. Alternatively, it can immediately perform initial access to a cell selected by the WTRU using the cell selection procedure, or alternatively, initial access to a cell of the frequency indicated in the RRC message.
[0081] In one embodiment, parameters can be interchangeable or common across multiple RRC instances and include at least one of security parameters, NAS configuration (including PDP context), and user plane parameters (if a single data path is used). For example, from a network connectivity standpoint, the WTRU still appears as a single device implementing a single IP network interface using a single PDP context (i.e., IP address), a single data path, and a single security context. The required parameters can be common across all RRC instances and can be obtained, for example, from the PRAT connection and / or initial NAS configuration. In one embodiment, RRM and mobility management for each RRC connection can be configured independently of each other. Alternatively, mobility can be based on the PRAT connection (e.g., 710).
[0082] In one embodiment, WTRU can be configured to use zero or more SCells for PRAT.
[0083] In the embodiment described with respect to Figures 5 to 8, where the control plane includes a separate RRC instance for each configured RAT for wireless resource management, the different RRC instances can interact with each other using one of several different methods, for example, security configuration, security activation, security failures, failure handling, RRC connection reconfiguration, RLM, error recovery, state transitions, return of transactions to idle mode, and actions on PUCCH / SRS release requests.
[0084] With regard to security configuration, activation, and failure, the WTRU can use a second RRC instance if it adds a first serving cell for SRAT. In one embodiment, if security is activated for another RRC instance, the WTRU considers that security is already activated for the second RRC instance and can apply the same configuration to integrity protection and encryption for the access layer, where applicable.
[0085] Regarding fault handling, the WTRU may receive control plane information (e.g., RRC PDU or IE) about an SRAT RRC instance that it may have failed to process. If the WTRU receives control plane information about an SRAT RRC instance that it may have failed to process, it may notify the network that the configuration has failed, suspend any ongoing transmissions on the relevant SRAT serving cell, disable the configuration for all SRAT serving cells, remove the configuration for all SRAT serving cells, notify the network that the configuration has failed, and / or terminate any secondary RAT RRC instances or secondary RAT RRC connections. If the WTRU receives a configuration message indicating that at least part of the configuration for at least one SRAT serving cell has been added, modified, or removed, the WTRU may fail to apply the relevant configuration. In this case, the WTRU may disable the configuration of the associated serving cell, remove the configuration of the associated serving cell, disable the configuration for all serving cells of SRAT, remove the configuration for all serving cells of SRAT, notify the network that the configuration has failed, and / or terminate the SRAT RRC instance or secondary RAT connection. None of these failures can affect the operation and / or configuration of the RRC connection for PRAT.
[0086] Regarding the reconfiguration of the RRC connection, the WTRU may receive a radio resource reconfiguration message indicating that it will add a configuration for a first LTE serving cell using the configured UL resources. The WTRU can then initiate a procedure to obtain UL timing synchronization (e.g., a random access procedure on the cell's UL PRACH resources). In one embodiment, the WTRU may receive a handover command which may include a configuration using at least one LTE serving cell using the configured UL resources. In this embodiment, in addition to initiating access to the HSPA target cell, the WTRU can also initiate a procedure to obtain UL timing synchronization (e.g., a random access procedure on the LTE target cell's UL PRACH resources).
[0087] With respect to RLM, the WTRU can perform RLM for the configured serving cells of the SRAT. In one embodiment, the WTRU can determine, for example, that a serving cell of a corresponding RAT is suffering from RLF according to criteria for RLF of that serving cell. If the WTRU determines that a serving cell of a first RAT is RLF (DL or UL), it can remove the configuration for all serving cells of the first RAT, turn off the radio frontend for the first RAT, and / or inform the network of the RLF status of the associated serving cells. In one embodiment, the RRC instance of the first RAT can inform the RRC instance of the second RAT of the UL RLF status.
[0088] With respect to state transitions and associated procedures, a change in the RRC state in a first RRC instance can trigger a state change and / or procedure in a second RRC instance. For example, a state transition in the first RRC instance can trigger a state transition in the second RRC instance, the release of the RRC connection in the second RRC instance, and / or the WTRU can turn off the radio frontend for the second RAT corresponding to the second RRC instance. In one embodiment, an RRC state transition from CELL_DCH to any other state for an HSPA RRC instance can trigger an LTE RRC instance to perform a state transition to RRC_IDLE, release the RRC LTE connection, and / or turn off the LTE frontend. For example, if HSPA is PRAT, LTE may be SRAT, and for the LTE RAT, UL resources may not be configured. In another embodiment, an RRC state transition to idle mode in the first RAT can trigger a state transition to idle mode for each configured SRAT's RRC instance, or alternatively, it can trigger, for example, releasing the RRC connection and / or turning off the front end of each configured SRAT. If HSPA is a PRAT, LTE can be an SRAT, and only HSPA RRC instances can perform the cell reselection procedure.
[0089] As another example, a state transition in a second RRC instance may not be permitted depending on the state of the first RRC instance. In one embodiment, an RRC state may not be permitted in an RRC instance for SRAT based on the current state of another RRC instance. In particular, if an LTE RRC instance is in the RRC_CONNECTED state, the WTRU cannot transition to the CELL-FACH or CELL_PCH state for an HSPA RRC instance.
[0090] As another example, the operating state of a second RRC instance may follow the state of the first RRC instance. In one embodiment, if the state of the LTE PRAT's RRC instance is RRC_CONNECTED, the initial state of the HSPA SRAT's RRC instance can be CELL_DCH.
[0091] Regarding the transition back to idle mode, a transition to RRC idle for an RRC connection that is a PRAT of a WTRU can trigger the release of other RRC connections and / or a transition to RRC IDLE for another RRC instance (e.g., all RATs, or only RATs where the WTRU should be in IDLE mode when not connected to the network). The RRC instance for a PRAT can notify another RRC instance for an SRAT of the change of state to IDLE. The RRC instance for the SRAT can then transition to IDLE mode, remove the dedicated configuration for the SRAT, revert to the default configuration, and / or perform the steps to activate and / or deactivate the SRAT's transceiver module and / or any functions.
[0092] Regarding actions taken when a PUCCH / SRS release request is made, the PRAT LTE RRC instance can receive an indication from a lower layer (e.g., the LTE MAC) to release the PUCCH / SRS-dedicated resources. This can occur, for example, when the maximum number of SR transmissions on the configured PUCCH resource for scheduling requests (SRs) is reached, or when the timing alignment timer (TAT) expires. When the TAT expires, the WTRU no longer has a valid timing advance and is no longer synchronized for UL transmissions. In this case, the PRAT RRC instance can inform the SRAT RRC instance of the loss of UL synchronization in PRAT.
[0093] In embodiments that use a single RRC connection for all configured RATs (e.g., the embodiments described above with respect to Figures 3, 4, 5, and 6), the WTRU can receive RRC messages and configuration parameters related to the SRAT, for example, via SRAT IEs piggybacked into the RRC PDU of the PRAT. In this embodiment, the WTRU can multiplex and / or demultiplex RAT-specific IEs within the RRC PDU of the single RRC connection and identify the IEs using explicit identifiers within the RRC PDU (e.g., RRC state machine or SRAT identification information).
[0094] In one embodiment, the PRAT's RRC message may include an SRAT container IE. The SRAT container IE may include information about the SRAT that can be processed according to the SRAT's RRC. For example, if the PRAT is LTE, an HSPA SRAT can be established by including an utra-Secondarycell-Container IE. In one embodiment, the presence of this IE may trigger the initiation of a secondary RAT.
[0095] If two or more SRATs can be established, an SRAT type IE and an SRAT message container IE can be used. The SRAT message container IE can carry messages specified in another standard indicated by the SRAT type IE. This container can carry the information and radio parameters necessary for the configured SRATs.
[0096] For example, a WTRU can be configured such that each group of cells configured for a given RAT is associated with the identification information of that RAT. When a WTRU receives an RRC PDU, it can determine which RAT the IE is associated with and process the RRC PDU according to the applicable RAT, for example. Similarly, a WTRU can send an RRC PDU that contains one or more information elements within it. If at most two RATs are supported, this can be implicitly determined by the presence of the IE itself within the PDU.
[0097] In embodiments that use separate RRC instances for each configured RAT (for example, the embodiments described above with respect to Figures 5, 6, 7, and 8), the WTRU can receive configuration parameters for the SRAT by multiplexing the RRC PDUs for the PRAT and SRAT, for example, using different SRB identifiers (SRB_ID). In one embodiment, the WTRU can multiplex and / or demultiplex the RRC PDUs on the data path and identify the RRC connections and / or state machines to which the RRC messages are applicable based on the radio bearer identification information used for transmitting the RRC PDUs.
[0098] For example, a WTRU can be configured so that one or more SRBs are associated with the control signaling of a particular RAT, for example, based on SRB_ID. When a WTRU receives an RRC PDU, it can determine which radio bearer the PDU is associated with, and, for example, if the WTRU is configured to use a RAT-specific security context, it can apply the appropriate security context for authentication (if necessary) and decryption, and / or process the RRC PDU using an RRC state machine applicable to the associated RAT. Similarly, a WTRU can transmit an RRC PDU using an association with an applicable RRC state machine.
[0099] In one embodiment, after security activation and association with a given priority, an SRB applicable to SRAT can be configured. For example, a WTRU can be configured such that an SRB applicable to a subset or type of HSPA RRC PDU has the same (or alternatively lower) priority as SRB1 for transporting HSPA RRC PDUs over the LTE MAC. For example, a WTRU can be configured such that a logical channel applicable to a subset or type of LTE RRC PDU maps to a specific priority in the MAC-ehs multiplexing function.
[0100] In embodiments that use a single RRC instance for all configured RATs (e.g., the embodiments described above with respect to Figures 3 and 4), if the WTRU receives a configuration that adds at least one serving cell for SRAT, then radio resource management can be performed using one or more of the examples described below. In such embodiments, the WTRU may have an established RRC connection using PRAT (e.g., 306 in Figure 3).
[0101] In one embodiment, if security (for example, for PRAT) is activated, the WTRU can add a serving cell for SRAT, in which case it can apply the same configuration to integrity protection and encryption for the access layer, where applicable (for example, when multiple data paths are used).
[0102] In one embodiment, the WTRU may receive an RRC message indicating that it is adding, changing, or deleting at least part of the configuration for at least one serving cell of an SRAT. The WTRU may fail to apply the relevant configuration, in which case it may disable the configuration for the relevant serving cell, delete the configuration for the relevant serving cell, disable the configuration for all serving cells of the SRAT, delete the configuration for all serving cells of the SRAT, turn off the radio frontend for the SRAT, notify the network that the configuration failed, and / or terminate the SRAT RRC instance of the SRAT RRC connection. In particular, failure to apply the configuration to an SRAT may not affect the operation and / or configuration of the RRC connection for the SRAT. If the RRC procedure applicable to an SRAT fails to complete successfully, the WTRU may abort the procedure and revert the procedure for the relevant SRAT to the state it was in before the WTRU initiated it.
[0103] If LTE is a PRAT, the RRC instance can perform radio resource management for the SRAT according to one of the following embodiments. In one embodiment, the WTRU operation for the PRAT can follow a typical procedure for the relevant RAT. In one embodiment, the WTRU can perform RLM for the configured serving cells of the LTE PRAT, for example, for the PCell. The WTRU can determine that it is suffering from a UL RLF on the PCell of the LTE PRAT according to criteria for the RLF of the serving cell of the corresponding RAT. If the WTRU determines that it is suffering from an RLF (DL or UL) for the PCell of the LTE PRAT, it can perform an RRC state transition from RRC_CONNECTED to RRC_IDLE, in which case it can remove the configuration for all serving cells of the HSPA SRAT and / or turn off the radio frontend for the HSPA SRAT.
[0104] The WTRU can also perform RLM for configured serving cells of an HSPA SRAT. The WTRU can determine if a serving cell of a corresponding RAT is suffering from a UL RLF on its primary serving cell, according to the criteria for RLF of that RAT. If the WTRU determines that a serving cell of an HSPA SRAT is under a UL RLF, it can disable the configuration of the serving cell in question, delete the configuration of the serving cell in question, disable the random access configuration of the serving cell in question, delete the random access configuration of the serving cell in question, disable the configuration for all serving cells of the HSPA SRAT, delete the configuration for all serving cells of the HSPA SRAT, turn off the radio frontend for the HSPA SRAT, inform the network of the UL RLF condition for the serving cell in question, deactivate secondary RAT serving cells, and / or terminate SRAT RRC instances of SRAT RRC connections.
[0105] In one embodiment, the WTRU can determine that a serving cell of a corresponding RAT is suffering from DL RLF according to criteria for RLF of the serving cell. If the WTRU determines that a serving cell of an HSPA SRAT is DL RLF, the WTRU can disable the configuration of the serving cell in question, remove the configuration of the serving cell in question, disable the configuration for all serving cells of the HSPA SRAT, remove the configuration for all serving cells of the HSPA SRAT, turn off the wireless frontend for the HSPA SRAT, and / or inform the network of the DL RLF condition for the serving cell in question.
[0106] The WTRU can perform an RRC state transition from LTE RRC_CONNECTED to LTE RRC_IDLE, in which case the WTRU can disable the configuration for all SRAT serving cells, remove the configuration for all SRAT serving cells, turn off the radio frontend for SRAT, and / or terminate any secondary RAT RRC instances or SRAT RRC connections.
[0107] A PRAT LTE RRC instance may receive an indication from a lower layer (e.g., the LTE MAC) to release PUCCH / SRS-dedicated resources. This can occur, for example, when the maximum number of SR transmissions on the configured PUCCH resources for SR is reached, or when the TAT expires. When the TAT expires, the WTRU no longer has a valid timing advance and is no longer synchronized for UL transmissions. In this case, the WTRU may disable the configuration for all SRAT serving cells, remove the configuration for all SRAT serving cells, turn off the radio frontend for SRAT, and / or terminate the SRAT RRC instance or SRAT RRC connection.
[0108] If the HSPA is a PRAT, the RRC instance can perform radio resource management for the SRAT according to one of the following embodiments. In addition, the WTRU operation for the PRAT can follow a typical procedure for the relevant RAT.
[0109] In one embodiment, the WTRU may receive a radio resource reconfiguration message indicating that it will add a configuration for a first LTE serving cell using the configured UL resources, and then initiate a procedure to acquire UL timing synchronization (e.g., a random access procedure on the cell's UL PRACH resources). In one embodiment, the WTRU may receive a handover command which may include a configuration for at least one LTE serving cell using the configured UL resources. In addition to initial access to the HSPA target cell, the WTRU may also initiate a procedure to acquire UL timing synchronization (e.g., a random access procedure on the LTE target cell's UL PRACH resources).
[0110] In one embodiment, the WTRU can perform RLM for one or more of the configured serving cells of the PRAT, in particular for the primary serving cell of the HSPA PRAT. The WTRU can determine, for example, that it is suffering from an RLF on the primary serving cell according to criteria for the RLF of the corresponding RAT serving cell. If it is determined that it is a UL RLF for the primary serving cell of the HSPA PRAT, the RRC instance for the HSPA PRAT can receive a first out-of-sync indication from the physical layer and refrain from performing the UL transmission. If at least one serving cell of the LTE SRAT is configured to use UL resources and can transmit UL feedback information on the serving cell, the WTRU can proceed with any transmission on the LTE SRAT.
[0111] If the WTRU determines that it is RLF (DL and / or UL) for the primary serving cell of the HSPA PRAT, it may perform an RRC state transition from CELL_DCH (and / or CELL_FACH), in which case it may remove the configuration for all serving cells of the LTE SRAT, turn off the radio frontend for the LTE SRAT, and / or deactivate the LTE SRAT by instruction.
[0112] In one embodiment, the WTRU can perform RLM for a configured serving cell of LTE SRAT. The WTRU can determine that it is suffering from UL RLF on an LTE SRAT serving cell, in particular on a PCell, according to criteria for RLF of the corresponding RAT serving cell. If it determines that it is UL RLF for an LTE SRAT serving cell, the WTRU can disable the configuration of the associated serving cell, remove the configuration of the associated serving cell, disable the random access configuration of the associated serving cell, remove the random access configuration of the associated serving cell, disable the configuration for all serving cells of LTE SRAT, remove the configuration for all serving cells of LTE SRAT, turn off the radio frontend for LTE SRAT, notify the network of the UL RLF condition for the associated serving cell, and / or terminate the SRAT RRC instance or SRAT RRC connection.
[0113] In one embodiment, the WTRU can determine that a serving cell of a corresponding RAT is suffering from a DL RLF according to criteria for the RLF of that serving cell. If it determines that a serving cell of an LTE SRAT is under DL RLF, the WTRU can disable the configuration of the serving cell in question, remove the configuration of the serving cell in question, disable the configuration for all serving cells of the LTE SRAT, remove the configuration for all serving cells of the LTE SRAT, turn off the radio frontend for the LTE SRAT, inform the network of the DL RLF condition for the serving cell in question, and / or terminate the SRAT RRC instance or SRAT RRC connection.
[0114] In one embodiment, the WTRU can perform an RRC state transition from a connected state (e.g., CELL_DCH, CELL_PCH, or URA_PCH) to an idle mode, in which case the WTRU can disable the configuration for all serving cells of LTE SRAT, remove the configuration for all serving cells of LTE SRAT, and / or turn off the radio frontend for LTE SRAT.
[0115] Embodiment
[0116] 1. A method for performing wireless communication in a wireless transceiver unit (WTRU) configured for multi-radio access technology (RAT) operation, the method comprising the step of the WTRU wirelessly transmitting information on a first operating frequency according to a first RAT.
[0117] 2. The method according to Embodiment 1, further comprising the step of the WTRU wirelessly transmitting information on a second operating frequency according to a second RAT.
[0118] 3. The method according to Embodiment 1 or 2, wherein the first RAT is either Long-Term Evolution (LTE) or High-Speed Packet Access (HSPA), and the second RAT is one of HSPA, LTE, and WiFi.
[0119] 4. The method according to any one of Embodiments 1 to 3, further comprising the step of the WTRU establishing a Radio Resource Control (RRC) connection in the first RAT using an RRC instance.
[0120] 5. The method according to Embodiment 4, further comprising the step of the WTRU receiving a configuration for at least one serving cell of a second RAT over an RRC connection.
[0121] 6. The method according to Embodiment 5, further comprising the step of configuring a WTRU to use an RRC instance to configure radio resources for a second RAT.
[0122] 7. The method according to any one of embodiments 1 to 6, wherein if the WTRU performs an RRC state transition from LTE RRC_CONNECTED to LTE RRC_IDLE on the first RAT, it performs at least one of the following: disabling the configuration for all serving cells of the second RAT, removing the configuration for all serving cells of the second RAT, and turning off the radio frontend for the second RAT.
[0123] 8. The method according to any one of embodiments 1 to 7, further comprising the step of a WTRU transmitting and receiving an RRC protocol data unit (PDU) of a type corresponding to a first RAT, wherein the RRC PDU of a type corresponding to a first RAT includes at least one information element (IE) corresponding to a second RAT.
[0124] 9. The method according to any one of embodiments 1 to 8, further comprising the step of the WTRU establishing a radio resource control (RRC) connection in the first RAT using a first RRC instance.
[0125] 10. The method according to embodiment 9, further comprising the step of the WTRU receiving a configuration for at least one serving cell of a second RAT over an RRC connection.
[0126] 11. The method according to embodiment 9 or 10, further comprising the step of configuring a WTRU to have a second RRC instance to provide radio resources for a second RAT.
[0127] 12. The method according to any one of embodiments 9 to 11, further comprising the step of a WTRU transmitting and receiving PDUs over an RRC connection, wherein each PDU has a signaling radio bearer identifier (SRB_ID) corresponding to one of a first RRC instance and a second RRC instance.
[0128] 13. The method according to any one of embodiments 9 to 12, wherein if the WTRU performs an RRC state transition from LTE RRC_CONNECTED to LTE RRC_IDLE on the first RAT, it performs at least one of the following: disabling the configuration for all serving cells of the second RAT, removing the configuration for all serving cells of the second RAT, turning off the radio frontend for the second RAT, and terminating the second RRC instance.
[0129] 14. The method according to any one of embodiments 1 to 13, further comprising the step of the WTRU establishing a first radio resource control (RRC) connection in a first RAT using a first RRC instance.
[0130] 15. The method according to Embodiment 14, further comprising the step of the WTRU establishing a second RRC connection in the second RAT using a second RRC instance.
[0131] 16. The method according to Embodiment 14 or 15, further comprising the step of adding a serving cell for a second RRC connection in the second RAT in response to security activated for the first RAT.
[0132] 17. The method according to Embodiment 14 or 15, further comprising the step of a WTRU performing radio link monitoring (RLM) for a serving cell configured with a first RAT, wherein the first RAT is an LTE.
[0133] 18. The method according to Embodiment 17, further comprising the step of determining whether the WTRU is experiencing a radio link failure (RLF) in which the first RAT is configured serving cell.
[0134] 19. The method according to Embodiment 17 or 18, further comprising the step of removing the configuration for all serving cells of the second RAT and turning off the radio front end for the second RAT if the WTRU determines that the configured serving cells of the first RAT are suffering from an RLF, wherein the second RAT is an HSPA.
[0135] 20. The method according to Embodiment 14 or 15, further comprising the step of configuring mobility management for a second RRC connection based on a first RRC connection.
[0136] 21. A wireless transceiver unit (WTRU) configured for multi-radio access technology (RAT) operation, comprising a transceiver configured to wirelessly transmit information on a first operating frequency according to a first RAT.
[0137] 22. The WTRU according to Embodiment 21, wherein the transceiver is further configured to wirelessly transmit information on a second operating frequency according to a second RAT.
[0138] 23. The WTRU according to Embodiment 21 or 22, wherein the first RAT is either Long-Term Evolution (LTE) or High-Speed Packet Access (HSPA), and the second RAT is one of HSPA, LTE, and WiFi.
[0139] 24. The WTRU according to embodiment 21 or 22, further comprising a processor configured to establish a radio resource control (RRC) connection in the first RAT using an RRC instance.
[0140] 25. The WTRU according to Embodiment 24, further configured to receive a configuration for at least one serving cell of a second RAT over an RRC connection.
[0141] 26. The WTRU according to embodiment 24 or 25, wherein the processor is further configured to use an RRC instance to configure radio resources for a second RAT.
[0142] 27. The WTRU according to any one of embodiments 24 to 26, wherein the transceiver is further configured to transmit and receive RRC protocol data units (PDUs) of a type corresponding to a first RAT, and the RRC PDU of a type corresponding to a first RAT includes at least one information element (IE) corresponding to a second RAT.
[0143] 28. The WTRU according to any one of embodiments 21 to 27, further comprising a processor configured to establish a radio resource control (RRC) connection in the first RAT using a first RRC instance.
[0144] 29. The WTRU according to Embodiment 28, further configured to receive a configuration for at least one serving cell of a second RAT over an RRC connection.
[0145] 30. The WTRU according to embodiment 28 or 29, wherein the processor is further configured to configure radio resources for a second RAT using a second RRC instance.
[0146] 31. The WTRU according to any one of embodiments 28 to 30, wherein the transceiver is further configured to transmit and receive PDUs over an RRC connection, and each PDU has a signaling radio bearer identifier (SRB_ID) corresponding to one of the first RRC instance and the second RRC instance.
[0147] 32. The WTRU according to any one of embodiments 28 to 30, wherein the processor is further configured to perform at least one of the following: disabling the configuration for all serving cells of the second RAT, removing the configuration for all serving cells of the second RAT, turning off the radio frontend for the second RAT, and terminating the second RRC instance, if it performs an RRC state transition from LTE RRC_CONNECTED to LTE RRC_IDLE on the first RAT.
[0148] 33. The WTRU according to any one of embodiments 21 to 32, further comprising a processor configured to establish a first radio resource control (RRC) connection in a first RAT using a first RRC instance.
[0149] 34. The WTRU according to embodiment 33, wherein the processor is further configured to establish a second RRC connection in the second RAT using a second RRC instance.
[0150] 35. The WTRU according to embodiment 33 or 34, wherein the processor is further configured to add a serving cell for a second RRC connection in the second RAT in response to security activated for the first RAT.
[0151] 36. The WTRU according to any one of embodiments 33 to 35, wherein the processor is further configured to perform radio link monitoring (RLM) for the serving cells configured for the first RAT.
[0152] 37. The first RAT is LTE, as described in Embodiment 36.
[0153] 38. The WTRU according to any one of embodiments 33 to 37, wherein the processor is further configured to determine whether the serving cell configured for the first RAT is suffering an uplink (UL) radio link failure (RLF).
[0154] 39. The processor is further configured to perform at least one of the following: if it determines that the configured serving cells of the first RAT are subject to UL RLF, it removes the configuration for all serving cells of the second RAT and turns off the radio front end for the second RAT, the second RAT being an HSPA, as described in any one of embodiments 33 to 37.
[0155] 40. The WTRU according to any one of embodiments 33 to 39, wherein the processor is further configured to configure mobility management for a second RRC connection based on a first RRC connection.
[0156] While features and elements have been described above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. In addition, the methods described herein can be implemented in computer programs, software, or firmware contained within a computer-readable medium, executed by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital multi-purpose disks (DVDs). A processor working with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
1. An e-node B (eNB) of a first wireless access technology (first RAT), Transceiver and, Equipped with a processor, The processor and the transceiver are, Using a first signaling radio bearer (first SRB), communicate with a wireless transceiver unit (WTRU) and RRC messages having the first radio resource control (RRC) format of the first RAT, Using the first SRB, an RRC reconstruction message including configuration information for the second RAT is sent to the WTRU, wherein the configuration information for the second RAT includes information that constitutes the second SRB for the second RAT. A configured eNB.
2. The processor and the transceiver are, A first RRC message is sent to the WTRU, containing information that constitutes a first media access control (MAC) entity for the first RAT. A second RRC message is sent to the WTRU containing information that constitutes a second MAC entity for the second RAT, and the first MAC entity and the second MAC entity are different. The eNB according to claim 1, further configured as follows.
3. The eNB according to claim 1, wherein the processor and the transceiver are further configured to transmit a first RRC message to the WTRU containing information comprising the WTRU for establishing a connection with the first primary cell of the first RAT.
4. The eNB according to claim 1, wherein the first RAT is a long-term evolution.
5. The eNB according to claim 1, wherein the first RAT and the second RAT are different RATs.
6. A method performed by an e-node B (eNB) of a first radio access technology (first RAT), The steps include using a first signaling radio bearer (first SRB) to communicate with a wireless transceiver unit (WTRU) and an RRC message having a first radio resource control (RRC) format of the first RAT, A step of using the first SRB to send an RRC reconfiguration message to the WTRU, the configuration information for the second RAT including information that constitutes the second SRB for the second RAT. A method for providing this.
7. The steps include sending a first RRC message to the WTRU, which includes information constituting a first media access control (MAC) entity for the first RAT, A step of sending a second RRC message to the WTRU, which includes information constituting a second MAC entity for the second RAT, wherein the first MAC entity and the second MAC entity are different. The method according to claim 6, further comprising:
8. The step of sending a first RRC message to the WTRU, which includes information constituting the WTRU for establishing a connection with the first primary cell of the first RAT. The method according to claim 6, further comprising:
9. The method according to claim 6, wherein the first RAT is a long-term evolution.
10. The method according to claim 6, wherein the first RAT and the second RAT are different RATs.
11. A wireless transceiver unit (WTRU), Transceiver and, Equipped with a processor, The processor and the transceiver are, Using a first signaling radio bearer (first SRB), communicate an e-node B (eNB) of a first radio access technology (first RAT) with an RRC message having the first radio resource control (RRC) format of the first RAT. Using the first SRB, an RRC reconstruction message containing configuration information for the second RAT is received from the eNB, wherein the configuration information for the second RAT includes information constituting the second SRB for the second RAT. A well-configured WTRU.
12. The processor and the transceiver are, The eNB receives a first RRC message containing information constituting a first media access control (MAC) entity for the first RAT, The eNB receives a second RRC message containing information that constitutes a second MAC entity for the second RAT, and the first MAC entity and the second MAC entity are different. A further configured WTRU according to claim 11.
13. The WTRU according to claim 11, wherein the processor and the transceiver are further configured to receive a first RRC message from the eNB containing information constituting the WTRU for establishing a connection with the first primary cell of the first RAT.
14. The WTRU according to claim 11, wherein the first RAT is a long-term evolution.
15. The WTRU according to claim 11, wherein the first RAT and the second RAT are different RATs.
16. A method performed by a Wireless Transceiver Unit (WTRU), The steps of using a first signaling radio bearer (first SRB) to communicate an e-node B (eNB) of a first radio access technology (first RAT) with an RRC message having a first radio resource control (RRC) format of the first RAT, A step of receiving an RRC reconstruction message from the eNB using the first SRB, the RRC reconstruction message including configuration information for a second RAT, wherein the configuration information for the second RAT includes information that constitutes a second SRB for the second RAT. A method for providing this.
17. The steps include receiving a first RRC message from the eNB containing information constituting a first media access control (MAC) entity for the first RAT, A step of receiving a second RRC message from the eNB, which includes information constituting a second MAC entity for the second RAT, wherein the first MAC entity and the second MAC entity are different. The method according to claim 16, further comprising:
18. The step of receiving a first RRC message from the eNB, which includes information constituting the WTRU for establishing a connection with the first primary cell of the first RAT. The method according to claim 16, further comprising:
19. The method according to claim 16, wherein the first RAT is a long-term evolution.
20. The method according to claim 16, wherein the first RAT and the second RAT are different RATs.
Citation Information
Patent Citations
Method and communication apparatus for improving RRC connection procedure
JP2009232457A
Architecture Providing Multi-System Carrier Aggregation
US20110134831A1
