3GPP TDocs (written contributions) at meeting
Meeting: R3-61 - 2008-08-18 to 2008-08-22, Jeju Island
meeting id: R3-61 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑081690 | Agenda RAN3#61, Jeju Island, South Korea 18-22 August 2008 | Chairman | - |
R3‑081691 | Revised draft report of RAN3#60, Kansas City, USA | MCC | - |
R3‑081692 | Workplan and Working Procedures v0.30.1 (Rel-8) | MCC | - |
R3‑081693 | LS on NodeB measurement to report common E-DCH Resource Usage (R2-082797 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑081694 | reply LS on E-AICH Power Offset and Error Targets for AICH/E-AICH (R2-082804 Source: TSG RAN WG2, To: TSG RAN WG1, Cc: TSG RAN WG3,TSG RAN WG4) | TSG RAN WG2 | - |
R3‑081695 | Reply LS on S1 Overload Control and on security for service request message (R2-082868 Source: TSG RAN WG2, To: TSG RAN WG3,TSG SA WG2,TSG SA WG3,TSG CT WG1, Cc: ) | TSG RAN WG2 | response to R3-080993 |
R3‑081696 | Reply LS on RAN3 requirements for GTPv2 (R2-082869 Source: TSG RAN WG2, To: TSG RAN WG3,CT4, Cc: TSG SA WG2) | TSG RAN WG2 | response to R3-080990 |
R3‑081697 | Reply LS on SRVCC from EUTRAN to 1xRTT (R2-082888 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑081698 | LS on reservation of an MMEC value (R2-082894 Source: TSG RAN WG2, To: CT4, Cc: CT1,TSG RAN WG3,TSG SA WG2,TSG SA WG5) | TSG RAN WG2 | - |
R3‑081699 | LS on per UE frequency restriction (R2-082897 Source: TSG RAN WG2, To: TSG SA WG2,TSG RAN WG3, Cc: CT1) | TSG RAN WG2 | response to R3-080979 |
R3‑081700 | Reply LS on Earthquake and Tsunami Warning System (R2-082883 Source: TSG RAN WG2, To: CT1,TSG SA WG1,TSG SA WG2,TSG SA WG3, Cc: TSG RAN WG1,TSG RAN WG3) | TSG RAN WG2 | - |
R3‑081701 | Reply-LS on Applicability of “subscriber type” indication for UTRAN & GERAN (R2-082884 Source: TSG RAN WG2, To: TSG RAN WG3,TSG SA WG2,TSG GERAN WG2, Cc: ) | TSG RAN WG2 | response to R3-080543 |
R3‑081702 | Response LS to “LS on the necessity of to convey ‘Receive Status of UL PDCP SDU’ in S1 Handover” (R2-082071/R3-080976) (R2-082886 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑081703 | Comments on the LS on CSG requirements for UTRA/E-UTRA (C1-081867 LS out on CSG requirements Source: CT1, To: TSG RAN WG2,TSG SA WG1,TSG SA, Cc: TSG SA WG2,TSG GERAN,TSG RAN WG3) | CT1 | - |
R3‑081704 | LS on LTE-cell- and eNB-identification (C1-081868-LS-out Source: CT1, To: TSG RAN WG2, Cc: TSG RAN WG3,TSG SA WG2) | CT1 | - |
R3‑081705 | Reply LS on Outstanding NAS messages from SA3 [C1-081634 (S3-080525)] (C1-081870 Source: CT1, To: TSG RAN WG2, Cc: TSG SA WG3,TSG RAN WG3) | CT1 | - |
R3‑081706 | Reply LS on NAS–AS interaction for dependent procedures (R2-082896 Source: TSG RAN WG2, To: CT1, Cc: TSG RAN WG3,TSG SA WG2) | TSG RAN WG2 | - |
R3‑081707 | LS on Message header for EPS session management (C1-082060-LS-out Source: CT1, To: TSG RAN WG2,TSG RAN WG3,TSG SA WG2, Cc: ) | CT1 | - |
R3‑081708 | Reply LS on Enhancements for SRNS Relocation (C4-081483 Source: CT WG4, To: TSG RAN WG3,CT WG1, Cc: TSG SA WG2) | CT WG4 | - |
R3‑081709 | Reply LS to S3-080503 – key change on-the-fly (R2-082890 Source: TSG RAN WG2, To: TSG SA WG3,TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑081710 | LS regarding GAN Iu mode security (GP-080883 Source: TSG GERAN WG2, To: TSG SA WG3,TSG RAN WG2,TSG RAN WG3, Cc: 3GPP TSG CT WG1) | TSG GERAN WG2 | - |
R3‑081711 | LS on specifying Inter-RAT PS Handover between GERAN and E-UTRAN (GP-080910 Source: TSG GERAN, To: TSG SA WG2, Cc: TSG RAN WG3) | TSG GERAN | - |
R3‑081712 | Response LS on Partial handover (S2-084324-LS-partial-handover.pa2 Source: TSG SA WG2, To: TSG RAN WG3, Cc: TSG RAN WG2) | TSG SA WG2 | - |
R3‑081713 | LS on AMBR Enforcement (S2-084413 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3, Cc: ) | TSG SA WG2 | - |
R3‑081714 | LS on SRVCC target cell selection (S2-084419 Source: TSG SA WG2, To: TSG RAN WG2,TSG GERAN, Cc: TSG RAN WG3) | TSG SA WG2 | - |
R3‑081715 | LS on UE Radio Capabilities (S2-084436_LS_on UE Radio Capabilities to MME Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3,TSG RAN,TSG GERAN WG2,CT,TSG SA, Cc: CT1,CT4,TSG GERAN) | TSG SA WG2 | - |
R3‑081716 | LS to RAN3 about RAN1 decision regarding Relative Narrowband TX Power Indicator for DL ICIC (R1-082253_ Source: TSG RAN WG1, To: TSG RAN WG3, Cc: ) | TSG RAN WG1 | - |
R3‑081717 | Reply LS on CSG related mobility (stage 2 text) (S1-080769 Source: TSG SA WG1, To: TSG GERAN,TSG RAN WG2, Cc: TSG SA WG2,TSG RAN WG3,TSG RAN WG4,TSG RAN WG1) | TSG SA WG1 | - |
R3‑081718 | Liaison Statement to 3GPP – Mobile Backhaul Implementation Agreement ( Source: Metro Ethernet Forum, To: RAN3, GERAN, Cc: ) | Metro Ethernet Forum | - |
R3‑081719 | LS on Recovery and Restoration (S2-084449_S2-084287_LS on Restoration Source: TSG SA WG2, To: CT4,TSG RAN WG3, Cc: ) | TSG SA WG2 | - |
R3‑081720 | Support for Network Based Location Technologies on User Plane (S2-084454_e-mail-r5-S2-084022-LS to CT4 Source: TSG SA WG2, To: TSG CT4,OMA LOC, Cc: TSG RAN,TSG RAN WG2,TSG RAN WG3) | TSG SA WG2 | - |
R3‑081721 | Reply LS on Enhancements for SRNS Relocation (S2-084455_e-mail-r1-S2-084023 Source: TSG SA WG2, To: TSG RAN WG3, Cc: CT1,CT4) | TSG SA WG2 | response to R3-080994 |
R3‑081722 | Response LS on the need for TAU in connected mode (S2-084456-email-r4-S2-084326 Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG RAN WG3,CT WG1) | TSG SA WG2 | - |
R3‑081723 | LS on Active mode paging in E-UTRAN (S2-084457-e-mail-r2-S2-084153 Source: TSG SA WG2, To: TSG RAN WG2,CT1, Cc: TSG RAN WG3) | TSG SA WG2 | - |
R3‑081724 | Reply LS on inclusion of MNC and MCC in RRC Connection Setup Complete message (S2-084458-e-mail-R4-S2-084299 Source: TSG SA WG2], To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG2] | - |
R3‑081725 | LS on Earthquake and Tsunami Warning System (S2-084460-e-mail-R1-S2-084418 Source: TSG SA WG2, To: TSG RAN WG1,WG2,WG3, Cc: ) | TSG SA WG2 | - |
R3‑081726 | Response LS on UE Radio Capabilities (RP-080473 Source: TSG RAN, To: TSG SA,TSG SA WG2, Cc: CT1,CT4,TSG GERAN,TSG RAN WG2,TSG RAN WG3,TSG GERAN WG2,CT) | TSG RAN | - |
R3‑081727 | LS on decision for NW interface option for ETWS support (R3-080475 Source: TSG RAN, To: TSG SA,TSG SA WG2,TSG RAN WG2,TSG RAN WG3, Cc: CT,CT1,CT4) | TSG RAN | - |
R3‑081728 | LS on HSPA VoIP Continuity Solution (RP-080489 Source: TSG RAN, To: TSG SA, Cc: TSG SA WG2,CT,CT1,TSG GERAN,TSG GERAN WG2,TSG RAN WG2,TSG RAN WG3) | TSG RAN | - |
R3‑081729 | ReplyLS on UE Radio Capabilities (CP-080411 Source: TSG CT, To: TSG SA, Cc: CT1,CT4,TSG GERAN,TSG SA WG2,TSG RAN WG2,TSG RAN WG3,TSG RAN,TSG GERAN WG2) | TSG CT | - |
R3‑081730 | LS on multiple solutions for VoIP call continuity (SP-080436 Source: TSG SA, To: TSG RAN,TSG RAN WG2,TSG SA WG2, Cc: TSG GERAN,CT,CT1,TSG GERAN WG2,TSG RAN WG3) | TSG SA | - |
R3‑081731 | Reply to LS from TSG-RAN on decision for NW interface option for ETWS support (SP-080440 Source: TSG SA, To: TSG SA WG2, Cc: TSG CT and TSG CT WG1,TSG RAN,TSG RAN WG2,TSG RAN WG3) | TSG SA | - |
R3‑081732 | LS on CS Fallback (R2-083035 Source: TSG RAN WG2, To: TSG SA WG2,TSG CT WG1, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑081733 | LS on Tracking Area Update in RRC Connected (R2-083036 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG RAN WG3,TSG CT WG1) | TSG RAN WG2 | - |
R3‑081734 | Response LS on “Direct Data Forwarding for Inter 3GPP RAT Handover” (S2-085134 Source: TSG SA WG2, To: CT WG4, Cc: TSG RAN WG3) | TSG SA WG2 | - |
R3‑081735 | LS reply on specifying Inter-RAT PS Handover between GERAN and E-UTRAN (S2-085136_LS_response_to_GERAN_IRAT_HOr3 Source: TSG SA WG2, To: TSG GERAN, Cc: TSG RAN WG3) | TSG SA WG2 | - |
R3‑081736 | Reply LS on “Changes to the format of TMGI” (C3-081062 Source: CT3, To: CT4, Cc: TSG RAN WG2,TSG RAN WG3,CT1) | CT3 | - |
R3‑081737 | LS on OAM support for RRC neighbour lists and RRC blacklists (S5-080996 Source: TSG SA WG5, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG5 | - |
R3‑081738 | LS on Enhancements for SRNS Relocation (C1-082547 Source: CT1, To: TSG RAN WG3, Cc: CT4) | CT1 | reply to R3-081585 |
R3‑081739 | LS on NAS triggering connection recovery after RLF (C1-082800 LS reply on connection recovery Source: CT WG1, To: TSG RAN WG2, Cc: TSG SA WG2,TSG RAN WG3) | CT WG1 | - |
R3‑081740 | LS on CS Fallback (C1-082806 Source: CT1, To: TSG RAN WG2,TSG SA WG1, Cc: TSG SA WG2,TSG RAN WG3) | CT1 | - |
R3‑081741 | LS on indicating needs for the key indicator information on Intersystem RAT handover security from E-UTRAN to UTRAN/GERAN (S3-080869 Source: TSG SA WG3, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG SA WG2,CT1) | TSG SA WG3 | - |
R3‑081742 | Reply LS to SA2 LS on Earthquake and Tsunami Warning System (S3-080912 Source: TSG SA WG3, To: TSG RAN WG2,TSG RAN WG3,CT1,TSG SA WG2, Cc: CT4,TSG RAN WG1,TSG GERAN WG1,TSG GERAN WG2) | TSG SA WG3 | - |
R3‑081743 | LS on Intersystem RAT handover security from E-UTRAN to UTRAN/GERAN (S3-080839 Source: TSG SA WG3, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG3 | - |
R3‑081744 | Reply LS on reservation of an MMEC value (S2-085261-LS-MMEC-value.pa5 Source: TSG SA WG2, To: TSG RAN WG2,CT4, Cc: CT1,TSG RAN WG3,TSG SA WG5) | TSG SA WG2 | - |
R3‑081745 | Reply LS on S1 Overload Control (S2-085264 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG SA WG3,TSG CT WG1) | TSG SA WG2 | reply to R3-081585 |
R3‑081746 | LS on Tracking Area Update in RRC Connected and handover for load balancing (S2-085265 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG CT WG1) | TSG SA WG2 | reply to R3-081580 |
R3‑081747 | Reply LS on CS Fallback (S2-085266_reply_to_RAN2_4644_on_CSFB Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG CT WG1,TSG RAN WG3) | TSG SA WG2 | - |
R3‑081748 | Reply LS on Earthquake and Tsunami Warning System (S2-085267_ETWS_LS Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG RAN WG1,TSG RAN WG3,CT1,TSG SA WG1,TSG SA WG3) | TSG SA WG2 | - |
R3‑081749 | Reply LS on reservation of an MMEC value (C4-081804_reply_ls_MMEC Source: TSG CT WG4, To: TSG RAN WG2, Cc: CT1,TSG RAN WG3,TSG SA WG2,TSG SA WG5) | TSG CT WG4 | - |
R3‑081750 | Reply LS on MME pool configuration (C4-081861_reply_ls_MME_pool_cfg Source: TSG CT WG4, To: TSG RAN WG3, Cc: TSG SA WG2,TSG SA WG5) | TSG CT WG4 | reply to R3-081578 |
R3‑081751 | Reply LS on Introduction of UE History Information in HSPA evolution (R2-083633 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | reply to R3-080984 |
R3‑081752 | Reply LS on SRVCC target cell selection (R2-083776 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG GERAN,TSG RAN WG3) | TSG RAN WG2 | - |
R3‑081753 | Reply LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN (R2-083778 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: TSG SA WG2,TSG CT WG1,TSG CT WG4) | TSG RAN WG2 | reply to R3-081576 |
R3‑081754 | LS on AMBR Enforcement (R2-083781 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG RAN WG3,CT1) | TSG RAN WG2 | - |
R3‑081755 | LS on ICIC Signalling (R2-083785 Source: TSG RAN WG2, To: TSG RAN WG1, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑081756 | Reply LS on OAM support for RRC neighbour lists and RRC blacklists (R2-083789 Source: TSG RAN WG2, To: TSG SA WG5, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑081757 | Further questions on Earthquake and Tsunami Warning System (R2-083786 Source: TSG RAN WG2, To: CT1,TSG SA WG1,TSG SA WG2, Cc: TSG RAN WG1,TSG RAN WG3,TSG SA WG3) | TSG RAN WG2 | - |
R3‑081758 | Reply LS on Inter RAT ANR (R2-083793 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | reply to R3-081606 |
R3‑081759 | Reply LS on the necessity of Location Reporting procedure in S1 (S2-085287 Source: TSG SA WG2, To: TSG RAN WG3, Cc: CT1) | TSG SA WG2 | reply to R3-081582 |
R3‑081760 | LS reply on the AP ID Uniqueness (S2-085288 Source: TSG SA WG2, To: TSG RAN WG3, Cc: None) | TSG SA WG2 | reply to R3-081567 |
R3‑081761 | LS reply on Handover restriction List signalling (S2-085289 Source: TSG SA WG2, To: TSG RAN WG3, Cc: TSG RAN WG2,CT1) | TSG SA WG2 | reply to R3-081573 |
R3‑081762 | Response LS on “ODB barring categories for EPS” (S2-085300-e-mail-rev1-S2-085280_LSout_ODB Source: TSG SA WG2, To: CT WG4,TSG SA WG1, Cc: TSG RAN WG3) | TSG SA WG2 | - |
R3‑081763 | LS on conditions for addition/removal of neighbour relations (S5-081220 Source: TSG SA WG5, To: TSG RAN WG3, Cc: None) | TSG SA WG5 | - |
R3‑081764 | LS on Cell Traffic Trace functionality (S5-081263 Source: TSG SA WG5, To: TSG RAN WG3, Cc: CT4) | TSG SA WG5 | - |
R3‑081765 | LS on removal of neighbour relations by OAM (S5-081239 Source: TSG SA WG5, To: TSG RAN WG3, Cc: None) | TSG SA WG5 | - |
R3‑081766 | Reply LS on CS Fallback (S1-082387 Source: TSG SA WG1, To: CT1,TSG RAN WG2,TSG SA WG2, Cc: TSG RAN WG3,CT6) | TSG SA WG1 | - |
R3‑081767 | Reply LS to RAN2 on ETWS (S1-082413 Source: TSG SA WG1, To: TSG RAN WG2, Cc: TSG SA WG2,TSG RAN WG3) | TSG SA WG1 | - |
R3‑081768 | Status Report: Enhancements for SRNS Relocation Procedure | Nokia Siemens Networks | - |
R3‑081769 | Status Report: Enhancements for FDD HSPA Evolution | Nokia Siemens Networks | - |
R3‑081770 | Status Report: UTRAN architecture for 3G HNB | Alcatel-Lucent | - |
R3‑081771 | Network related E-UTRAN Identities description | Motorola | - |
R3‑081772 | Update of E-UTRAN Ids | Motorola | - |
R3‑081773 | Update of E-UTRAN Ids | Motorola | - |
R3‑081774 | Functionality overview update (configuration update , trace, location reporting) | Motorola | - |
R3‑081775 | Functionality overview update (configuration update, status reporting, interference overload) | Motorola | similar change in 1882 |
R3‑081776 | Self- Optimization for Coverage optimization | ZTE | - |
R3‑081777 | Solution for Coverage and Capacity optimization | ZTE | - |
R3‑081778 | Considerations on automated configuration of Phy-CID for HNB | ZTE | - |
R3‑081779 | Access Control in 3G HNB Network | ZTE | - |
R3‑081780 | Method for Discovery and Registration at 3G HNB-GW | ZTE | - |
R3‑081781 | AMBR modification | ZTE | - |
R3‑081782 | SAE-Bearer-BitRate ASN1 modification | ZTE | contained in other CR |
R3‑081783 | Extension of the ranges of the HS-DSCH / E-DCH Provided Bit Rate Value IEs | ZTE | - |
R3‑081784 | Extension of the ranges of the HS-DSCH / E-DCH Provided Bit Rate Value IEs | ZTE | - |
R3‑081785 | Provision of X2 for HeNB | picoChip Designs Ltd | - |
R3‑081786 | Combining HNBAP and RUA | Alcatel-Lucent | - |
R3‑081787 | HNBAP Specification Proposal | Alcatel-Lucent,NSN, Kineto, Thomson, Airvana | - |
R3‑081788 | Clarification of HNB-GW & SeGW functions within the HNB Network Architecture | Alcatel-Lucent,Airvana, Thomson | - |
R3‑081789 | UE Registration and Signalling Connection Establishment | Alcatel-Lucent,Airvana, Thomson, Kineto | - |
R3‑081790 | HNB Registration & Discovery procedures | Alcatel-Lucent, Airvana, Thomson | - |
R3‑081791 | WI Status Report HNB-Arch | Alcatel-Lucent | - |
R3‑081792 | Further details on a solution for RAB management across the Iuh | Alcatel-Lucent | - |
R3‑081793 | S1 connectivity for HeNB | Panasonic | - |
R3‑081794 | HeNB functionality for S1-flex | Panasonic | - |
R3‑081795 | Iuh control plane protocol stack for CS and PS domain | Panasonic | - |
R3‑081796 | Mechanism for 3G HNB-GW Discovery, Registration and Configuration updates | Ip.access Ltd, AT&T, Cisco | - |
R3‑081797 | Mechanism for 3G HNB-GW Discovery, Registration and Configuration updates | Ip.access Ltd, AT&T, Cisco | - |
R3‑081798 | Network related Identities description | Motorola | - |
R3‑081799 | Update of E-UTRAN Ids | Motorola | - |
R3‑081800 | Update of E-UTRAN Ids | Motorola | - |
R3‑081801 | Functionality overview update | Motorola | - |
R3‑081802 | Functionality overview update | Motorola | - |
R3‑081803 | Clarification of eNB behaviour for location reporting over S1 | Motorola | agreed for big CR |
R3‑081804 | Clarification of eNB behaviour for location reporting over X2 | Motorola | depends on stage 2 outcome |
R3‑081805 | Paging load reduction in asynchronous cells | Motorola | - |
R3‑081806 | Over-the-air paging load reduction | Motorola | - |
R3‑081807 | Parallel transactions on S1 | Motorola | specs to be checked if problem exists |
R3‑081808 | Interaction between SAE Bearer Release and Handover | Motorola | - |
R3‑081809 | Consistency of eNB behaviour on reception of trace related messages | Motorola | replaced by 2320 |
R3‑081810 | X2 shutdown | Motorola | - |
R3‑081811 | Introduction of new cause values for UE context release | CATT | - |
R3‑081812 | Description for trace activation during S1 handover | CATT | - |
R3‑081813 | Relation between X2 Setup and Reset procedures | CATT | - |
R3‑081814 | Transmission of AMBR over S1 interface | CATT | - |
R3‑081815 | Transmission of AMBR over X2 interface | CATT | - |
R3‑081816 | The NAS PDU in S1 messages | CATT | - |
R3‑081817 | Value range correction in S1AP ASN.1 | CATT | - |
R3‑081818 | Value range correction in X2 AP ASN.1 | CATT | contained in other CRs |
R3‑081819 | Terminology alignment for Home Node B and Home eNode B (S1-082397 Source: TSG SA WG1, To: TSG GERAN,TSG SA,TSG RAN,TSG CT, Cc: ) | TSG SA WG1 | - |
R3‑081820 | Framework for distributed PCI selection | Qualcomm Europe | - |
R3‑081821 | Discovery of neighbor eNB IP address | Qualcomm Europe | - |
R3‑081822 | E-UTRAN architecture for the Home eNode B | Qualcomm Europe | - |
R3‑081823 | Transparent and optional concentrator for S1-MME | Qualcomm Europe | - |
R3‑081824 | HeNB initialization when attaching to the network | Qualcomm Europe | - |
R3‑081825 | Open issues on EPS Bearer context management | Qualcomm Europe | - |
R3‑081826 | Addition of NAS PDU in bearer release command message | Qualcomm Europe | wait for outcome of CT1/RAN2 |
R3‑081827 | Cause value for UE Context Release Request Message | Qualcomm Europe | - |
R3‑081828 | Removal of NAS PDU from bearer setup/modify response messages | Qualcomm Europe | - |
R3‑081829 | COMMON TRANSPORT CHANNEL SETUP REQUEST TDD message ASN correction | TD Tech | - |
R3‑081830 | COMMON TRANSPORT CHANNEL SETUP REQUEST TDD message ASN correction | TD Tech | - |
R3‑081831 | Correct ASN.1 compatibility problem in PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message for 1.28Mcps TDD | TD Tech, CATT | - |
R3‑081832 | Correct ASN.1 compatibility problem in PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message for 1.28Mcps TDD | TD Tech, CATT | - |
R3‑081833 | Extend the PCCPCH Power value for 1.28Mcps TDD | TD Tech | RAN4 first |
R3‑081834 | Extend the PCCPCH Power value for 1.28Mcps TDD | TD Tech | RAN4 first |
R3‑081835 | Use the NBCC in enhanced CELL_FACH state for 1.28Mcps TDD | TD Tech | - |
R3‑081836 | Work frequency indication in enhanced CELL_FACH state for 1.28Mcps TDD | TD Tech | - |
R3‑081837 | RACH Optimisation use case description | NTT DOCOMO | - |
R3‑081838 | S1AP procedures to support ETWS in E-UTRAN | NTT DOCOMO | - |
R3‑081839 | S1AP procedures to support ETWS in E-UTRAN: S1 Write Replace procedure | NTT DOCOMO | - |
R3‑081840 | S1AP procedures to support ETWS in E-UTRAN: S1 Kill procedure | NTT DOCOMO | - |
R3‑081841 | ETWS work alignment for UTRAN | NTT DOCOMO | - |
R3‑081842 | CR for 25.419 to support ETWS in UTRAN | NTT DOCOMO | - |
R3‑081843 | Concern on the status of U-plane handling in Inter RAT HO | NTT DOCOMO | - |
R3‑081844 | The necessity on AP Layer Activity Checking | NTT DOCOMO | - |
R3‑081845 | eNB triggered S1 Overload signaling | NTT DOCOMO | - |
R3‑081846 | eNB triggered S1 Overload signaling | NTT DOCOMO | - |
R3‑081847 | CS Fallback work alignment | NTT DOCOMO | - |
R3‑081848 | CS Fallback work alignment: CR on Initial Context Setup procedure | NTT DOCOMO | - |
R3‑081849 | Location Reporting procedure during X2 Handover | NTT DOCOMO | - |
R3‑081850 | Location Reporting procedure during X2 Handover | NTT DOCOMO | - |
R3‑081851 | Self-Configuration of transport layer address | Alcatel-Lucent | - |
R3‑081852 | Mobility towards Home eNBs | Alcatel-Lucent | - |
R3‑081853 | Mobility towards home eNBs | Alcatel-Lucent | - |
R3‑081854 | Completion of cell and eNB identifiers over S1 | Alcatel-Lucent | - |
R3‑081855 | Completion of cell and eNB identifiers over S1 | Alcatel-Lucent | - |
R3‑081856 | Alignment of causes | Alcatel-Lucent, | - |
R3‑081857 | Alignment of causes | Alcatel-Lucent, | agreed for big CR |
R3‑081858 | Correction of SAE bearer Bit Rate | Alcatel-Lucent | - |
R3‑081859 | Correction of SAE bearer Bit Rate | Alcatel-Lucent | could be continued with co-sourced docs |
R3‑081860 | Correction of SAE bearer level Qos parameters | Alcatel-Lucent, | - |
R3‑081861 | Correction of SAE bearer level Qos parameters | Alcatel-Lucent, | - |
R3‑081862 | Correction of SAE Bearer Id | Alcatel-Lucent, | - |
R3‑081863 | NAS PDU Handling in combined AS-NAS procedures | Alcatel-Lucent, | - |
R3‑081864 | NAS PDU Handling in combined AS-NAS procedures | Alcatel-Lucent | - |
R3‑081865 | Correction of NAS PDU in Bearer Release procedure | Alcatel-Lucent | - |
R3‑081866 | Data forwarding clean-up wrt direct/indirect path available | Alcatel-Lucent | - |
R3‑081867 | Data forwarding clean-up wrt direct/indirect path available | Alcatel-Lucent | - |
R3‑081868 | Correction of Security keys | Alcatel-Lucent | - |
R3‑081869 | Transfer of CDMA2000 MSI and pilot list for 1xRTT system | Alcatel-Lucent | - |
R3‑081870 | Transfer of CDMA2000 MSI and pilot list for 1xRTT system | Alcatel-Lucent | - |
R3‑081871 | Transfer of CDMA2000 MSI and pilot list for 1xRTT system in a packed element | Alcatel-Lucent, Ericsson, Motorola, Nokia Siemens Networks, Verizon, Nortel | agreed for big CR |
R3‑081872 | Correction of DRX parameter | Alcatel-Lucent, | - |
R3‑081873 | Self-configuration of transport layer address | Alcatel-Lucent | - |
R3‑081874 | Relocation related causes | Alcatel-Lucent, | - |
R3‑081875 | MME load balancing | Alcatel-Lucent | - |
R3‑081876 | Home eNB Registration | Huawei | - |
R3‑081877 | Discussion on C-Plane handling for Home eNB | Huawei | - |
R3‑081878 | Discussion on U-Plane handling for Home eNB | Huawei, Ericsson | - |
R3‑081879 | - | - | - |
R3‑081880 | UE capability update | Huawei, Ericsson | - |
R3‑081881 | Miscellaneous corrections | Huawei | - |
R3‑081882 | Alignment of the descriptions of the X2AP function | Huawei | agreed for big CR |
R3‑081883 | Addition of the Security Information IE to the HANDOVER REQUEST | Huawei | - |
R3‑081884 | Causes to distinguish different cases for NAS Non Delivery Indication | Huawei | - |
R3‑081885 | New cause to release S1 for load rebalancing | Huawei, Ericsson | - |
R3‑081886 | Removing the HRL information from Path Switch Ack message | Huawei | - |
R3‑081887 | Uniqueness of eNB UE X2AP ID | Huawei | - |
R3‑081888 | Failure and Unsuccessful Operation handling of the initial UE message | Huawei | - |
R3‑081889 | Failure and Unsuccessful Operation handling of the initial UE message | Huawei | - |
R3‑081890 | UE AMBR for EUTRAN | Huawei | - |
R3‑081891 | UE AMBR in S1 | Huawei | - |
R3‑081892 | UE AMBR in X2 | Huawei | - |
R3‑081893 | ECGI Transmission in S1AP messages | Huawei | - |
R3‑081894 | ECGI Transmission in S1AP messages | Huawei | - |
R3‑081895 | Adding Target Cell ID into Source eNB to Target eNB Transparent Container | Huawei | - |
R3‑081896 | Correcting presence of New eNB UE X2AP ID IE within HANDOVER CANCEL | Huawei | tbc |
R3‑081897 | NAS PDU of SAE BEARER RELEASE COMMAND | Huawei | - |
R3‑081898 | Align S1 AP ID in UE CONTEXT RELEASE COMPLETE message | Huawei | - |
R3‑081899 | Location Report in Initial Context Setup | Huawei | email#11 |
R3‑081900 | Discussion on handover restriction list | Huawei | - |
R3‑081901 | Handover Restriction List in SAE bearer setup procedure | Huawei | - |
R3‑081902 | Discussion on CSFB indication over S1 | Huawei | - |
R3‑081903 | CSFB indication over S1 | Huawei | - |
R3‑081904 | NAS message piggyback for SAE Bearer Setup/Modify Response | Huawei | - |
R3‑081905 | NAS message piggyback for SAE Bearer Setup/Modify Response | Huawei | - |
R3‑081906 | Discussion on Paging Cause | Huawei | - |
R3‑081907 | Alignment of Paging Causes | Huawei | - |
R3‑081908 | Discussion on DRX Parameters | Huawei | - |
R3‑081909 | Presence of DRX parameters in S1 paging | Huawei | - |
R3‑081910 | Addition of SAE bearer failure list in the PATH SWITCH REQUEST ACK | Huawei | - |
R3‑081911 | Discussion on NNSF functionality | Huawei | - |
R3‑081912 | NNSF functionality for S1 | Huawei | - |
R3‑081913 | Modification of S1 Paging procedure | Huawei | - |
R3‑081914 | Impact on S1 handover by Location Reporting procedure | Huawei | - |
R3‑081915 | Impact on S1 handover by Location Reporting procedure | Huawei | - |
R3‑081916 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081917 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081918 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081919 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081920 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081921 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081922 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑081923 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑081924 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑081925 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑081926 | The supplement of IPv4 encoding in NSAP structure | Huawei | - |
R3‑081927 | The supplement of IPv4 encoding in NSAP structure | Huawei | - |
R3‑081928 | The supplement of IPv4 encoding in NSAP structure | Huawei | - |
R3‑081929 | The supplement of IPv4 encoding in NSAP structure | Huawei | - |
R3‑081930 | The supplement of IPv4 encoding in NSAP structure | Huawei | - |
R3‑081931 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei | - |
R3‑081932 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei | - |
R3‑081933 | Further Clarification on Enhanced Cell_FACH/Cell_PCH | Huawei, Alcatel-Lucent | - |
R3‑081934 | Further Clarification on Enhanced Cell_FACH/Cell_PCH | Huawei, Alcatel-Lucent | - |
R3‑081935 | Further Clarification on Enhanced Cell_FACH/Cell_PCH | Huawei, Alcatel-Lucent | - |
R3‑081936 | E-FACH Measurement Report | Huawei | - |
R3‑081937 | E-FACH Measurement Report | Huawei | - |
R3‑081938 | Improve the data rate for Enhanced Cell_FACH state in FDD | Huawei | - |
R3‑081939 | Improve the data rate for Enhanced Cell_FACH state in FDD | Huawei | - |
R3‑081940 | Indication of Combination of 64QAM and MIMO over Iub | Huawei | - |
R3‑081941 | Indication of Combination of 64QAM and MIMO over Iub | Huawei | email#25 |
R3‑081942 | Discussion on E-RNTI allocation | Huawei | - |
R3‑081943 | CS capability of network for CS fallback | Huawei | - |
R3‑081944 | Preventing UTRAN->eUTRAN Inter-RAT HO for UE with SIM Access | Huawei | - |
R3‑081945 | Inter RAT handover restriction indication | Huawei | - |
R3‑081946 | Introduction of flexible E-DCH MAC-d PDU size indicator | Huawei | - |
R3‑081947 | HNBs Location Certification | Mitsubishi Electric | - |
R3‑081948 | HeNBs and X2 interface | Mitsubishi Electric | - |
R3‑081949 | Dynamic Setup of HNBs for Energy Savings and Interference Reduction | Mitsubishi Electric | - |
R3‑081950 | HNBAP Specification proposal - message contents TLV coding | Alcatel-Lucent, Airvana, Kineto^^^^ Airvana, Kineto^^^^ Airvana, Kineto^^^^ Airvana, Kineto | - |
R3‑081951 | HNBAP Specification proposal - message contents ASN.1 coding | Alcatel-Lucent | - |
R3‑081952 | Flexible Access Control Mechanism via UE Registration | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081953 | HNB Startup Overview | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081954 | Support for Plug-and-Play between HNB and HNB-GW | Kineto Wireless Inc, Motorola, TeliaSonera, NEC | - |
R3‑081955 | HNBAP messages for discovery and registration | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081956 | Abnormal condition for DTX-DRX | NEC | - |
R3‑081957 | Abnormal condition for DTX-DRX | NEC | - |
R3‑081958 | Abnormal condition for DTX-DRX | NEC | - |
R3‑081959 | Abnormal condition for DTX-DRX | NEC | - |
R3‑081960 | DRX-DTX and F-DPCH | NEC | - |
R3‑081961 | DRX-DTX and F-DPCH | NEC | - |
R3‑081962 | DRX-DTX and F-DPCH | NEC | - |
R3‑081963 | DRX-DTX and F-DPCH | NEC | - |
R3‑081964 | Alignment of improved L2 with RRC | NEC | tbc |
R3‑081965 | Alignment of improved L2 with RRC | NEC | tbc |
R3‑081966 | Alignment of improved L2 with RRC | NEC | tbc |
R3‑081967 | Alignment of improved L2 with RRC | NEC | tbc |
R3‑081968 | Adding capability of the UE without HS-SCCH transmit constraint | NEC | - |
R3‑081969 | Adding capability of the UE without HS-SCCH transmit constraint | NEC | - |
R3‑081970 | Incorrect description of HS-DSCH DATA FRAME TYPE usage | NEC | - |
R3‑081971 | Description of Priority Queue ID for Enhanced Cell_FACH | NEC | - |
R3‑081972 | Description of Priority Queue ID for Enhanced Cell_FACH | NEC | - |
R3‑081973 | Description of Priority Queue ID for Enhanced Cell_FACH | NEC | - |
R3‑081974 | Description of Priority Queue ID for Enhanced Cell_FACH | NEC | - |
R3‑081975 | Removing the ambiguity in HS-DSCH Common System Information description | NEC | - |
R3‑081976 | Removing the ambiguity in HS-DSCH Common System Information description | NEC | - |
R3‑081977 | Cell Transmission BW and frequency signalling over X2 | NEC | merged with 2344 |
R3‑081978 | SAE Bearer Management procedure-AS and NAS concatenation | NEC | - |
R3‑081979 | SAE Bearer Management procedure-AS and NAS concatenation | NEC | agreed for big CR |
R3‑081980 | Introduction of Cause IE in Downlink S1 CDMA2000 Tunnelling | NEC | - |
R3‑081981 | Introduction of Cause IE in Downlink S1 CDMA2000 Tunnelling | NEC | - |
R3‑081982 | IRAT ANR enhancement | NEC | agreed for big CR |
R3‑081983 | Load Balancing Framework Details | NEC | - |
R3‑081984 | Load Balancing Framework Details | NEC | - |
R3‑081985 | Inclusion of eNB capability information in the S1 Setup procedure | NEC | - |
R3‑081986 | Adding eNB Capability Information | NEC | - |
R3‑081987 | Correction of the Cell ID in messages | NEC | - |
R3‑081988 | Correct the wording of common and dedicated procedures | NEC | - |
R3‑081989 | Correct the wording of common and dedicated procedures | NEC | - |
R3‑081990 | Misalignment Between Tabular and ASN.1 for 36.413 | NEC | - |
R3‑081991 | ASN.1 and tabular misalignment | NEC | contained in other CRs |
R3‑081992 | Misalignment Between Tabular and ASN.1 for 36.423 | NEC | - |
R3‑081993 | ASN.1 and tabular misalignment | NEC | merged into 2315 |
R3‑081994 | Resource Optimization for UE-EPC Signalling transfer | NEC | - |
R3‑081995 | Resource Optimization for UE-EPC Signalling transfer | NEC | - |
R3‑081996 | Completion of Cell and eNB identifiers | Alcatel-Lucent | - |
R3‑081997 | Completion of Cell and eNB identifiers | Alcatel-Lucent | - |
R3‑081998 | Correction of the SAE Bearer Level QoS Parameters | Alcatel-Lucent | - |
R3‑081999 | Correction of SAE bearer bit rate | Alcatel-Lucent | tbc |
R3‑082000 | SAE Bearer Identity | Alcatel-Lucent | - |
R3‑082001 | Presence of Aggregate Maximum Bit Rate and SAE Bearer Info IEs in HANDOVER REQUEST message | Alcatel-Lucent | - |
R3‑082002 | Update of Trace Depth for EPS / E-UTRAN | Alcatel-Lucent | - |
R3‑082003 | Proposed LS to SA5 on Trace Depth coding in UTRAN and E-UTRAN | Alcatel-Lucent | - |
R3‑082004 | Minor changes | Alcatel-Lucent | - |
R3‑082005 | ASN.1 changes | Alcatel-Lucent | merged with CR 120 in R3-082315 |
R3‑082006 | X2 transport bearers | Alcatel-Lucent | - |
R3‑082007 | Update of the list of X2 functions | Alcatel-Lucent | - |
R3‑082008 | Trace in E-UTRAN | Alcatel-Lucent | - |
R3‑082009 | Non-GBR QoS Indication for Load Balancing | Nortel, Orange | - |
R3‑082010 | Hardware Load Definition | Nortel, Orange | - |
R3‑082011 | Hardware Load Introduction | Nortel, Orange | - |
R3‑082012 | TNL Load Definition | Nortel, Orange | - |
R3‑082013 | TNL Load Introduction | Nortel, Orange | tbc |
R3‑082014 | MBSFN support for centric solution | ZTE, Huawei | agreed for internal TR, open issues on MBSFN to be removed |
R3‑082015 | Comparison of UP synchronization robustness | ZTE, Huawei | - |
R3‑082016 | Some minor description corrections for E-DCH in LCR TDD | CATT | - |
R3‑082017 | Some minor description corrections for E-DCH in LCR TDD | CATT | - |
R3‑082018 | Uplink-downlink subframe configuration information for the served cell | CATT | - |
R3‑082019 | Uplink-downlink subframe configuration information for the served cell | CATT | - |
R3‑082020 | Improve the data rate for Enhanced Cell_FACH state in FDD | Huawei | - |
R3‑082021 | UTRAN Functionality Split | Huawei | - |
R3‑082022 | Some Considerations on RUA | Huawei | - |
R3‑082023 | Discussion on RUA Design Principles | Huawei | - |
R3‑082024 | RUA Message procedure | Huawei | - |
R3‑082025 | Proposal for RUA | Huawei | - |
R3‑082026 | 3G HNB GW Discovery procedure | Huawei | - |
R3‑082027 | 3G HNB Registration Procedure | Huawei | - |
R3‑082028 | UE Access control and UE Registration | Huawei | - |
R3‑082029 | Data Transfer on Iuh | Huawei | - |
R3‑082030 | RANAP Procedures on Iuh | Huawei | - |
R3‑082031 | Multiplexing Voice Frames over Iuh Interface | Huawei | - |
R3‑082032 | Multiplexing Negotiation | Huawei | - |
R3‑082033 | Downlink Detection Functionality for 3G HNB | Huawei | - |
R3‑082034 | Requirement Clarification and Way Forward for HNB Differentiated Charging Function | Huawei | - |
R3‑082035 | Some Identifiers Consideration for 3G HNB | Huawei | - |
R3‑082036 | Template for Evaluation Table for MBMS Improvement | Huawei, ZTE | - |
R3‑082037 | Comparisons of the solutions for MBMS over HSPA+ | Huawei, ZTE | - |
R3‑082038 | Discussion on RRM architecture that supports the PTP/PTM decision | Huawei | - |
R3‑082039 | LS on Key derivation during handover (S3-080923 Source: TSG SA WG3, To: TSG RAN WG2,TSG RAN WG3, Cc: ) | TSG SA WG3 | - |
R3‑082040 | Reply LS to RAN2 on ETWS (S1-082413 Source: TSG SA WG1, To: TSG RAN WG2, Cc: TSG SA WG2,TSG RAN WG3) | TSG SA WG1 | - |
R3‑082041 | LS on connected mode mobility support for 3G Home NodeBs | Qualcomm Europe | conclusions of meeting #60bis |
R3‑082042 | On Iub measurement for EUL in CELL_FACH | Qualcomm Europe | - |
R3‑082043 | HeNB GW Deployment Scenario | Samsung | - |
R3‑082044 | S1AP Correction according to NAS-AS interaction for dependent procedures | Samsung | - |
R3‑082045 | E-UTRAN identities | Samsung | - |
R3‑082046 | Correction of eNB Id definition | Samsung | - |
R3‑082047 | Correction of eNB ID and Cell Identity | Samsung | - |
R3‑082048 | Clarification on Initial UE Message transmission | Samsung | - |
R3‑082049 | Clarification on NAS Transport | Samsung | - |
R3‑082050 | MME load re-balancing support | Samsung | - |
R3‑082051 | UE history information deletion | Samsung | - |
R3‑082052 | S1 Setup | Samsung | - |
R3‑082053 | Introduce UE-AMBR to S1 Messages | Samsung | - |
R3‑082054 | Update Aggregate Maximum Bit Rate to UE-AMBR | Samsung | - |
R3‑082055 | LTE HeNB-GW discovery procedure | Samsung | - |
R3‑082056 | S1-h Setup Procedure | Samsung | - |
R3‑082057 | 3G HNB-GW Discovery Procedure | Samsung | - |
R3‑082058 | Introduction of new IE for X2 SETUP | Samsung | - |
R3‑082059 | Support of MBMS for 3G HNB Access | Samsung | - |
R3‑082060 | Signalling Connection in Iu and Iuh | Samsung | - |
R3‑082061 | RUA Frame Description | Samsung | - |
R3‑082062 | 3G HNB Security Problems | Samsung | - |
R3‑082063 | 3G HNB User Plane mechanism | Samsung | - |
R3‑082064 | RANAP on Iu-h | Samsung | - |
R3‑082065 | MOCN rerouting function | Samsung | - |
R3‑082066 | HeNB-GW: handling of User Plane | Samsung | - |
R3‑082067 | ANR Neighbors IP address lookup and establishment | Nortel | - |
R3‑082068 | LTE Local Breakout for Home eNB | Nortel | - |
R3‑082069 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | - |
R3‑082070 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | - |
R3‑082071 | Correction of SixtyfourQAM-DL-UsageIndicator | Ericsson | - |
R3‑082072 | Correction of SixtyfourQAM-DL-UsageIndicator | Ericsson | - |
R3‑082073 | Correction of SixtyfourQAM-DL-UsageIndicator | Ericsson | - |
R3‑082074 | Correction of SixtyfourQAM-DL-UsageIndicator | Ericsson | - |
R3‑082075 | Transparent HeNB Gateway considering the S1AP-ID-s | Ericsson, Huawei | - |
R3‑082076 | Transparent HeNB Gateway considering the S1 user plane transport | Ericsson, Huawei | - |
R3‑082077 | Adding dynamic configuration of the X2 interface | Ericsson | - |
R3‑082078 | Handling of unrecognised TEID/TLA during Path Switch procedure | Ericsson | - |
R3‑082079 | Handling of unrecognised TEID/TLA during Path Switch procedure | Ericsson | - |
R3‑082080 | Addition and correction of X2 procedures in stage 2 specification | Ericsson | - |
R3‑082081 | Correction of eNB ID and Cell ID coding | Ericsson | - |
R3‑082082 | Correction of eNB ID coding | Ericsson | - |
R3‑082083 | Correction EUTRAN Cell Global Identifier coding | Ericsson | - |
R3‑082084 | SCTP PPI and PORT numbers | Ericsson | - |
R3‑082085 | Longer forbidden TAC and LAC list length | Ericsson | - |
R3‑082086 | Longer forbidden TAC and LAC list length | Ericsson | - |
R3‑082087 | AS security support in S1 and X2 | Ericsson | - |
R3‑082088 | Security related updates to S1 | Ericsson | - |
R3‑082089 | Security related updates to X2 | Ericsson | - |
R3‑082090 | Information Elements definition cleanup | Ericsson | - |
R3‑082091 | Information Elements definition cleanup | Ericsson | - |
R3‑082092 | ASN.1 problems in SAE Bearer management messages | Ericsson | - |
R3‑082093 | Corrections of ASN.1 and tabular of SAE Bearer Management related messages | Ericsson | agreed for big CR |
R3‑082094 | Handling of UE associated logical connection at Initial Context Setup failure | Ericsson | - |
R3‑082095 | MME UE S1AP ID mandatory in UE CONTEXT RELEASE COMMAND | Ericsson | - |
R3‑082096 | MME UE S1AP ID mandatory in UE CONTEXT RELEASE COMMAND | Ericsson | agreed for big CR |
R3‑082097 | New S1AP class 2 procedure: Initial Ue Message Failure Indication | Ericsson | - |
R3‑082098 | Condition for release of GTP tunnels for indirect packet forwarding in EPC | Ericsson | SA2 first |
R3‑082099 | Multiple handover preparations | Ericsson | - |
R3‑082100 | Multiple handover preparations | Ericsson | - |
R3‑082101 | Path switch failure handling | Ericsson | - |
R3‑082102 | ASN.1 problems in Handover related messages | Ericsson | - |
R3‑082103 | Corrections of ASN.1 and tabular of Handover Management related messages | Ericsson | - |
R3‑082104 | Removal of Handover restriction list from Path Switch Ack | Ericsson | agreed for big CR |
R3‑082105 | Mandating RAC at inter-RAT handover | Ericsson | - |
R3‑082106 | Removal of unnecessary instances of NAS-PDU IE | Ericsson | - |
R3‑082107 | S1 ID handling of multiple GUMMEI | Ericsson | agreed for big CR |
R3‑082108 | Addition of User Inactivity cause value | Ericsson | - |
R3‑082109 | Introduction of UE history mechanism over S1 | Ericsson, Vodafone | - |
R3‑082110 | eNB provides Serving Cell Information to EPC outside the Location Reporting procedure | Ericsson, Vodafone | - |
R3‑082111 | Message definition cleanup | Ericsson | - |
R3‑082112 | ASN.1 problems in various messages | Ericsson | - |
R3‑082113 | Corrections of ASN.1 and tabular of various messages | Ericsson | agreed for big CR |
R3‑082114 | ASN.1 problems in IEs | Ericsson | - |
R3‑082115 | Some IE corrections | Ericsson | - |
R3‑082116 | Addition of missing statement on the order of bits in bitstrings | Ericsson | agreed for big CR |
R3‑082117 | Correction of misalignments between ASN.1 and tabular format | Ericsson | - |
R3‑082118 | Correction of AMBR presence | Ericsson | - |
R3‑082119 | HO Restriction procedure text corrections | Ericsson | agreed for big CR |
R3‑082120 | Correction of SN Status Transfer procedure | Ericsson | email#01 |
R3‑082121 | Correction of stage 2 stage 3 misalignment in SN Status Transfer procedure | Ericsson | agreed for big CR |
R3‑082122 | Served Cell Information alignment with RRC 36.331 | Ericsson | - |
R3‑082123 | Removal of FFS for RRC Context | Ericsson | agreed for big CR |
R3‑082124 | Clean-up of Resource Status procedures | Ericsson | - |
R3‑082125 | Home NodeB Initial connection | Ericsson | - |
R3‑082126 | Max Transport Block Size limits for EUL in CELL_FACH Ues | Ericsson | incorporated in 2339 |
R3‑082127 | Handling of E-RNTI and H-RNTI at E-DCH for CELL_FACH and Idle | Ericsson | - |
R3‑082128 | Introduction of frame formats supporting E-DCH for CELL_FACH and Idle over Iub | Ericsson | - |
R3‑082129 | Introduction of frame formats supporting E-DCH for CELL_FACH and Idle over Iur | Ericsson | - |
R3‑082130 | Required uplink resources in Node-B and E-DCH QoS | Ericsson | - |
R3‑082131 | Indication of required EUL uplink resources from Node B for GBR Radio Bearers | Ericsson | - |
R3‑082132 | Ping-Pong Cell Reselection Analysis and SON use case | CMCC | - |
R3‑082133 | Clarification on X2 Load Balancing | CMCC | - |
R3‑082134 | Clarification on X2 Load Balancing | CMCC | - |
R3‑082135 | ANR Functional Split in eNB and O&M | CMCC | - |
R3‑082136 | Solution on Load balancing with ping-pong HO avoidance | CMCC | - |
R3‑082137 | Proposal on CS Data Forwarding | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia, T-Mobile | - |
R3‑082138 | Clean-up for Stage3 Open Issues | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑082139 | Improvement for internal TR | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑082140 | On Relocation Complete Part | Nokia Siemens Networks, Nokia, Alcatel-Lucent, Huawei, Telecom Italia, T-Mobile | - |
R3‑082141 | RNSAP Message for DL NAS Forwarding | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑082142 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia | - |
R3‑082143 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia | - |
R3‑082144 | R3.022 v0.4.0 | Nokia Siemens Networks, Nokia | - |
R3‑082145 | User data flow recovery | Nokia Siemens Networks, Nokia | - |
R3‑082146 | NB+ MBMS recovery after the restart | Nokia Siemens Networks, Nokia | - |
R3‑082147 | PTM-PTP Switching | Nokia Siemens Networks, Nokia | - |
R3‑082148 | Criteria for Evaluation of MBMS improvements over evolved HSPA architecture | Nokia Siemens Networks, Nokia | - |
R3‑082149 | Evaluation on Two alternativesfor MBMS improvement over evolved HSPA architecture | Nokia Siemens Networks, Nokia | - |
R3‑082150 | Wayforward on MBMS solution for evolved HSPA architecture | Nokia Siemens Networks, Nokia | - |
R3‑082151 | Throughput related parameter in UE Historical Information | Nokia Siemens Networks, Nokia | - |
R3‑082152 | Reconsideration on Iub Resource Management | Nokia Siemens Networks, Nokia | - |
R3‑082153 | Analysis on NBAP Impact for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082154 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082155 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082156 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082157 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082158 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082159 | Introduction of Enhanced UE DRX | Nokia Siemens Networks, Nokia | - |
R3‑082160 | Introduction of Enhanced UE DRX | Nokia Siemens Networks, Nokia | - |
R3‑082161 | Introduction of Enhanced UE DRX | Nokia Siemens Networks, Nokia | - |
R3‑082162 | Introduction of Enhanced UE DRX | Nokia Siemens Networks, Nokia | - |
R3‑082163 | Introduction of Enhanced UE DRX | Nokia Siemens Networks, Nokia | - |
R3‑082164 | GU Group Id List in eNB Configuration Update | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑082165 | HeNB GW deployment analysis | Nokia Siemens Networks, Nokia | - |
R3‑082166 | Handling of C-Plane in HeNB | Nokia Siemens Networks, Nokia | - |
R3‑082167 | Handling of U-Plane in HeNB | Nokia Siemens Networks, Nokia | - |
R3‑082168 | Comparison of proposed methods for HeNBs architectures as described in TR R3.020 | Nokia Siemens Networks, Nokia | - |
R3‑082169 | NAS PDU handling in bearer management messages | Nokia Siemens Networks, Nokia | - |
R3‑082170 | AMBR updates | Nokia Siemens Networks, Nokia | - |
R3‑082171 | Subscriber Profile ID for RAT/Frequency priority | Nokia Siemens Networks, Nokia | - |
R3‑082172 | Security parameter in Initial Context | Nokia Siemens Networks, Nokia | - |
R3‑082173 | Security parameter during Handover | Nokia Siemens Networks, Nokia | - |
R3‑082174 | Overload handling S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑082175 | Overload handling S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑082176 | Overload handling S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑082177 | Removing of Paging Cause | Nokia Siemens Networks, Nokia | wait for cs fallback outcome |
R3‑082178 | Paging UE-Identity | Nokia Siemens Networks, Nokia | wait for cs fallback outcome |
R3‑082179 | UE context release update | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑082180 | Data forwarding for Inter 3GPP-RAT HO | Nokia Siemens Networks, Nokia | - |
R3‑082181 | Data forwarding for Inter 3GPP-RAT HO | Nokia Siemens Networks, Nokia | - |
R3‑082182 | AMBR mandatory in HO Request | Nokia Siemens Networks, Nokia | - |
R3‑082183 | Security parameter during Handover | Nokia Siemens Networks, Nokia | - |
R3‑082184 | Automatic Neighbour Relation function | Nokia Siemens Networks, Nokia | - |
R3‑082185 | Automated Configuration of Physical Cell Identity | Nokia Siemens Networks, Nokia | - |
R3‑082186 | Stage 2 specification for 3G HNB | Nokia Siemens Networks, Nokia, Airvana, Kineto | - |
R3‑082187 | Reply to CT4 LS on GTP-version for E-UTRAN | Nokia Siemens Networks | - |
R3‑082188 | Remaining open issues in load balancing | Motorola | - |
R3‑082189 | MME Load Balancing Enablers | Motorola | - |
R3‑082190 | Exchange of eUTRAN neighbour information | Motorola | - |
R3‑082191 | Exchange of eUTRAN neighbours in X2 setup | Motorola | - |
R3‑082192 | Some open issues in S1 Handover routeing and configuration | Motorola | - |
R3‑082193 | Introduction of MME Group ID in Handover Required message | Motorola | tbc |
R3‑082194 | Introduction of MME Group ID in X2 Configuration Update | Motorola | - |
R3‑082195 | Mandatory of "UE History Information IE" | Vodafone Group, Ericsson, T-Mobile | - |
R3‑082196 | Mandatory of "UE History Information IE" | Vodafone Group, Ericsson, T-Mobile | - |
R3‑082197 | Mandatory of "UE History Information IE" | Vodafone Group, Ericsson, T-Mobile | - |
R3‑082198 | Inclusion of the E-UTRAN GCI into INITIAL UE MESSAGE | Vodafone | - |
R3‑082199 | Interaction between Emergency services and SON switch off use cases | Huawei | - |
R3‑082200 | Discussion on Location Reporting Failure and Trace Failure after S1/X2 Handover | Huawei | - |
R3‑082201 | Location Reporting Failure and Trace Failure after S1 HO | Huawei | tbc |
R3‑082202 | Location Reporting Failure and Trace Failure after X2 HO | Huawei | tbc |
R3‑082203 | Resource Status Request Modification | Huawei | tbc |
R3‑082204 | Discussion on ANR IP lookup alternative | Huawei | - |
R3‑082205 | eNB Configuration Update procedures update for ANR | Huawei | - |
R3‑082206 | Parameter exchange during load balancing | Huawei | - |
R3‑082207 | Resource Status Request Parameter Exchange | Huawei | - |
R3‑082208 | Enhancement of UE history information with HO cause | Huawei | - |
R3‑082209 | X2 causes enhancement of UE history information | Huawei | - |
R3‑082210 | S1AP procedures to support ETWS in E-UTRAN: Stage 2 CR | NTT DOCOMO | - |
R3‑082211 | Discussion on X2 Handover Cancel | NTT DOCOMO | - |
R3‑082212 | KeNB handling at handover | NTT DOCOMO | - |
R3‑082213 | Correction of SAE Bearer identity | Alcatel-Lucent | - |
R3‑082214 | Correction of SAE Bearer identity | Alcatel-Lucent | - |
R3‑082215 | Principles for bootstrapping, provisioning and HNB operation | Airvana, ALU, Thomson | TR R3.020 |
R3‑082216 | Principles for bootstrapping, provisioning and HNB operation | Airvana, ALU, NSN,Thomson | - |
R3‑082217 | Flow Control & Prioritisation over S1/X2 Interface | Fujitsu | - |
R3‑082218 | Automatic Physical Layer Cell Identity Allocation | Ericsson | - |
R3‑082219 | S1 HO routing in case of HeNB Gw | Ericsson | TR R3.020 |
R3‑082220 | Removal of handover timers | Ericsson | tbc |
R3‑082221 | Early handover cancellation | Ericsson | - |
R3‑082222 | Value range update for eNB UE X2AP ID | CATT | contained in other CRs |
R3‑082223 | Iur aspects in evolved HSPA MBMS support | Nokia Siemens Networks, Nokia | R3.022 |
R3‑082224 | S1-U TNL congestion indication | T-Mobile, Orange | - |
R3‑082225 | Trace Support: Support of Configuration and Pulling of Trace Data | T-Mobile, Orange | - |
R3‑082226 | Latest version of TR 36.902 on "Self-configuring and self-optimizing network use cases and solutions" | T-Mobile | - |
R3‑082227 | SCTP restart function for X2 interface | NTT DOCOMO | - |
R3‑082228 | Framework for distributed PCI selection | Qualcomm Europe, T-Mobile, Orange, Telecom-Italia | - |
R3‑082229 | Discovery of neighbor eNB IP address | Qualcomm Europe, T-Mobile | - |
R3‑082230 | Enhancing the understandability of section 7 TS 36.412 | NTT DOCOMO | - |
R3‑082231 | Updating the Control Plane Protocol Stack | NEC | - |
R3‑082232 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei | - |
R3‑082233 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei | - |
R3‑082234 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082235 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082236 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei | - |
R3‑082237 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei | - |
R3‑082238 | Indication of Combination of 64QAM and MIMO over Iur | Huawei | email#25 |
R3‑082239 | Method for Discovery and Registration at 3G HNB-GW | ZTE | - |
R3‑082240 | Final report of RAN3#60, Kansas City, USA | MCC | - |
R3‑082241 | Workplan and Working Procedures v0.31.0 (Rel-8) | MCC | - |
R3‑082242 | LS response to S2-084449 (LS on Recovery and Restoration) | Ericsson | - |
R3‑082243 | LS on connected mode mobility support for 3G Home NodeBs | Qualcomm Europe | conclusions of meeting #60bis |
R3‑082244 | LS on connected mode mobility support for 3G Home NodeBs | RAN3 | conclusions of meeting #60bis |
R3‑082245 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082246 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082247 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082248 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082249 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei, NEC | - |
R3‑082250 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei, NEC | - |
R3‑082251 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei, NEC | - |
R3‑082252 | Adding abnormal conditions to Continuous Packet Connectivity | Huawei, NEC | - |
R3‑082253 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | - |
R3‑082254 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | - |
R3‑082255 | Correction on Enhanced Cell_FACH/Cell_PCH | Huawei, Alcatel-Lucent | - |
R3‑082256 | Correction on Enhanced Cell_FACH/Cell_PCH | Huawei, Alcatel-Lucent | - |
R3‑082257 | Removing the ambiguity in HS-DSCH Common System Information description | NEC | - |
R3‑082258 | Removing the ambiguity in HS-DSCH Common System Information description | NEC | - |
R3‑082259 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | - |
R3‑082260 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | - |
R3‑082261 | LS on Coding of Global Cell id and Global eNB ID | Alcatel-Lucent | - |
R3‑082262 | Completion of cell and eNB identifiers over S1 | Alcatel-Lucent | - |
R3‑082263 | Completion of Cell and eNB identifiers | Alcatel-Lucent | - |
R3‑082264 | Completion of Cell and eNB identifiers | Alcatel-Lucent | agreed for big CR |
R3‑082265 | Network related E-UTRAN Identities description | Motorola | agreed for big CR |
R3‑082266 | Correction of the description of subscriber and equipment trace | CATT | - |
R3‑082267 | Correct the wording of common and dedicated procedures | NEC | - |
R3‑082268 | Correct the wording of common and dedicated procedures | NEC | - |
R3‑082269 | SCTP restart function for X2 interface | NTT DOCOMO | - |
R3‑082270 | X2 transport bearers | Alcatel-Lucent | - |
R3‑082271 | Data forwarding for Inter 3GPP-RAT HO | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑082272 | Subscriber Profile ID for RAT/Frequency priority | Nokia Siemens Networks, Nokia | - |
R3‑082273 | Subscriber Profile ID for RAT/Frequency priority | Nokia Siemens Networks, Nokia | - |
R3‑082274 | LS on Management Based Trace activation | Alcatel-Lucent | - |
R3‑082275 | LS to SA5 on Trace Depth coding in UTRAN and E-UTRAN | Alcatel-Lucent | - |
R3‑082276 | E-UTRAN architecture for the Home eNode B | Qualcomm Europe | - |
R3‑082277 | Information Elements definition cleanup | Ericsson | agreed for big CR |
R3‑082278 | Information Elements definition cleanup | Ericsson | agreed for big CR |
R3‑082279 | Relative "Narrowband" Tx Power Indicator for DL ICIC | Alcatel-Lucent | agreed for big CR |
R3‑082280 | LS on E-UTRAN security related issues | Qualcomm Europe | - |
R3‑082281 | LS on Path Switch Request message | Alcatel-Lucent | - |
R3‑082282 | eNB provides Serving Cell Information to EPC outside the Location Reporting procedure | Ericsson, Vodafone | - |
R3‑082283 | Impact on S1 handover by Location Reporting procedure | Huawei | email#12 |
R3‑082284 | LS on SAE bearer/RAB definition for E-UTRAN specifications | Alcatel-Lucent | - |
R3‑082285 | AMBR updates | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑082286 | AMBR mandatory in HO Request | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑082287 | Handling of UE associated logical connection at Initial Context Setup failure | Ericsson | agreed for big CR |
R3‑082288 | LS on the use of UE History Information | Vodafone | - |
R3‑082289 | HNB ofline discussion note | Alcatel-Lucent, Airvana, Kineto, Huawei | - |
R3‑082290 | Presence of DRX parameters in S1 paging | Huawei | agreed for big CR |
R3‑082291 | Overload handling S1 interface | Nokia Siemens Networks, Nokia, Vodafone | agreed for big CR |
R3‑082292 | Overload handling S1 interface | Nokia Siemens Networks, Nokia, Vodafone | email#14 |
R3‑082293 | Reply LS on conditions for addition/removal of neighbour relations | Qualcomm | - |
R3‑082294 | Automatic Neighbour Relation function | Nokia Siemens Networks, Nokia | - |
R3‑082295 | IRAT ANR enhancement | NEC | not needed |
R3‑082296 | TR R3.020 v0.8.0 | Nokia Siemens Networks, Nokia | - |
R3‑082297 | Iuh signalling transport | Kineto Wireless, Alcatel-Lucent, NSN, Huawei, Samsung | - |
R3‑082298 | Agreement on framework for PCI selection | Qualcomm Europe, NSN, Orange, Vodafone, Telecom Italia, T-Mobile ^^^^Alcatel-Lucent, Huawei | - |
R3‑082299 | LS on configuring a range of PCI | Qualcomm | - |
R3‑082300 | S1AP procedures to support ETWS in E-UTRAN: Stage 2 CR | NTT DOCOMO | agreed for big CR |
R3‑082301 | RUA discussion | Samsung | - |
R3‑082302 | text proposal for TR R3.020 | Kineto,ALU, Airvana, Samsung, Huawei, Ericsson, NEC, Motorola | - |
R3‑082303 | Wayforward on MBMS solution for evolved HSPA architecture | Nokia Siemens Networks, Nokia, Ericsson | - |
R3‑082304 | Analysis on NBAP Impact for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082305 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082306 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082307 | UE Registration and Signalling Connection Establishment | Alcatel-Lucent,Airvana, Thomson, Kineto | email#16 |
R3‑082308 | Correction of SAE bearer level Qos parameters | Alcatel-Lucent, | agreed for big CR |
R3‑082309 | Correction of SAE Bearer Id | Alcatel-Lucent, | - |
R3‑082310 | Correction of the SAE Bearer Level QoS Parameters | Alcatel-Lucent | agreed for big CR |
R3‑082311 | SAE Bearer Identity | Alcatel-Lucent | - |
R3‑082312 | HNB discovery and registration | Kineto, Ericsson | - |
R3‑082313 | The supplement of IPv4 encoding in NSAP structure | Huawei | - |
R3‑082314 | MBMS for hspa architecture in Rel-8 | Huawei, ZTE,CATT, CMCC | - |
R3‑082315 | Correction of misalignments between ASN.1 and tabular format | Ericsson | agreed for big CR |
R3‑082316 | LS on the use of UE History Information | Vodafone | - |
R3‑082317 | LS on the use of UE History Information | RAN3 | - |
R3‑082318 | Minor changes | Alcatel-Lucent | email#15, agreed for big CR |
R3‑082319 | Summary of discussion on Concentrator function for HeNB | Qualcomm Europe, Ericsson, Huawei | agreed for internal TR without section 2.3 |
R3‑082320 | Correction of eNB behaviour on reception of trace related messages | Motorola | agreed for big CR |
R3‑082321 | correction of interaction between bearer release and UE context release | Motorola | agreed for big CR |
R3‑082322 | Mobility towards Home eNBs | Alcatel-Lucent | see 2341 |
R3‑082323 | Reply LS on Enhancements for SRNS Relocation | Nokia Siemens Networks | email#21 |
R3‑082324 | Clarification of SCTP Congestion Indication over S1 | Fujitsu | - |
R3‑082325 | Clarification of SCTP Congestion Indication over X2 | Fujitsu | - |
R3‑082326 | Longer forbidden TAC and LAC list length | Ericsson | agreed for big CR |
R3‑082327 | Longer forbidden TAC and LAC list length | Ericsson | agreed for big CR |
R3‑082328 | Proposal on CS Data Forwarding | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia, T-Mobile | - |
R3‑082329 | RNSAP Message for DL NAS Forwarding | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑082330 | Clean-up for Stage3 Open Issues | Nokia Siemens Networks, Nokia, Huawei | email#18 |
R3‑082331 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia | email#19 |
R3‑082332 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia | email#20 |
R3‑082333 | COMMON TRANSPORT CHANNEL SETUP REQUEST TDD message ASN correction | TD Tech | - |
R3‑082334 | COMMON TRANSPORT CHANNEL SETUP REQUEST TDD message ASN correction | TD Tech | - |
R3‑082335 | Correct ASN.1 compatibility problem in PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message for 1.28Mcps TDD | TD Tech, CATT | - |
R3‑082336 | Correct ASN.1 compatibility problem in PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message for 1.28Mcps TDD | TD Tech, CATT | - |
R3‑082337 | Introduction of frame formats supporting E-DCH for CELL_FACH and Idle over Iur | Ericsson | email#22 |
R3‑082338 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑082339 | Introduction of Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | email#23 |
R3‑082340 | Introduction of Enhanced UE DRX | Nokia Siemens Networks, Nokia | email#24 |
R3‑082341 | text proposal for mobility towards eHNB | Alcatel-Lucent | agreed for TR R3.020 |
R3‑082342 | Clean-up of Resource Status procedures | Ericsson | agreed for big CR |
R3‑082343 | Correction of SN Status Transfer procedure | Ericsson | email#01, agreed for big CR |
R3‑082344 | Served Cell Information alignment with RRC 36.331 | Ericsson | email#02, agreed for big CR |
R3‑082345 | Corrections of ASN.1 and tabular of Handover Management related messages | Ericsson | agreed for big CR |
R3‑082346 | Some IE corrections | Ericsson | email#03, agreed for big CR |
R3‑082347 | Message definition cleanup | Ericsson | agreed for big CR |
R3‑082348 | LS on automatic neighbour relation | Nokia Siemens Networks | - |
R3‑082349 | LS response to S2-084449 (LS on Recovery and Restoration) | RAN3 | - |
R3‑082350 | Addition of 16QAM AG table choice IE | Huawei, NEC | - |
R3‑082351 | Addition of 16QAM AG table choice IE | Huawei, NEC | - |
R3‑082352 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082353 | Addition of 16QAM AG table choice IE | Huawei | - |
R3‑082354 | Reply LS on conditions for addition/removal of neighbour relations | RAN3 | - |
R3‑082355 | Automatic Neighbour Relation function | Nokia Siemens Networks, Nokia | email#05 |
R3‑082356 | LS on automatic neighbour relation | Nokia Siemens Networks | email#05 |
R3‑082357 | Agreement on framework for PCI selection | Qualcomm Europe, NSN, Orange, Vodafone, Telecom Italia, T-Mobile ^^^^Alcatel-Lucent, Huawei | - |
R3‑082358 | LS on configuring a list of PCI | Qualcomm | - |
R3‑082359 | LS on configuring a list of PCI | RAN3 | email#06 |
R3‑082360 | Iuh signalling transport | Kineto Wireless, Alcatel-Lucent, NSN, Huawei, SamsungVodafone, Ip.access, Airvana | - |
R3‑082361 | SCTP restart function for X2 interface | NTT DOCOMO | - |
R3‑082362 | LS on Coding of Global Cell id and Global eNB ID | Alcatel-Lucent | - |
R3‑082363 | LS on Coding of Global Cell id and Global eNB ID | RAN3 | - |
R3‑082364 | Completion of cell and eNB identifiers over S1 | Alcatel-Lucent | email#07 |
R3‑082365 | LS on SAE bearer/RAB definition for E-UTRAN specifications | Alcatel-Lucent | - |
R3‑082366 | LS on SAE bearer/RAB definition for E-UTRAN specifications | RAN3 | - |
R3‑082367 | Subscriber Profile ID for RAT/Frequency priority | Nokia Siemens Networks, Nokia | email#08, agreed for big CR |
R3‑082368 | Subscriber Profile ID for RAT/Frequency priority | Nokia Siemens Networks, Nokia | email#08, agreed for big CR |
R3‑082369 | LS on Management Based Trace activation | RAN3 | - |
R3‑082370 | LS on Subscriber and Equipment Trace for EPC and E-UTRAN (R3-081057/S5-080878) | Alcatel-Lucent | email#09 |
R3‑082371 | Correction of SAE Bearer Id | Alcatel-Lucent, | agreed for big CR |
R3‑082372 | SAE Bearer Identity | Alcatel-Lucent | agreed for big CR |
R3‑082373 | LS on E-UTRAN security related issues | Qualcomm Europe | - |
R3‑082374 | eNB provides Serving Cell Information to EPC outside the Location Reporting procedure | Ericsson, Vodafone | email#10, agreed for big CR |
R3‑082375 | Path switch failure handling | Ericsson | email#13, agreed for big CR |
R3‑082376 | Proposal on CS Data Forwarding | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia, T-Mobile | email#17 |
R3‑082377 | changes to TS36.300 agreed in RAN3#61 | RAN3 | - |
R3‑082378 | changes to TS36.413 agreed in RAN3#61 | RAN3 | - |
R3‑082379 | changes to TS36.423 agreed in RAN3#61 | RAN3 | - |
R3‑082380 | TR R3.020 v0.9.0 | Nokia Siemens Networks, Nokia | email#29 |
R3‑082381 | TR R3.021v0.x.0 | Nokia Siemens Networks, Nokia | - |
R3‑082382 | Indication of Combination of 64QAM and MIMO over Iub | Huawei | email#25 |
R3‑082383 | Indication of Combination of 64QAM and MIMO over Iur | Huawei | email#25 |
R3‑082384 | Completion of cell and eNB identifiers over S1 | Alcatel-Lucent | email#07, agreed for big CR |
R3‑082385 | Overload handling S1 interface | Nokia Siemens Networks, Nokia, Vodafone | email#14, agreed for big CR |
R3‑082386 | UE Registration and Signalling Connection Establishment | Alcatel-Lucent,Airvana, Thomson, Kineto | email#16 |
R3‑082387 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei, Telecom Italia | email#19 |
R3‑082388 | Impact on S1 handover by Location Reporting procedure | Huawei | email#12, agreed for big CR |
R3‑082389 | Clean-up for Stage3 Open Issues | Nokia Siemens Networks, Nokia, Huawei | email#18 |
R3‑082390 | LS on Subscriber and Equipment Trace for EPC and E-UTRAN (R3-081057/S5-080878) | RAN3 | email#09 |
R3‑082391 | Reply LS on Enhancements for SRNS Relocation | RAN3 | email#21 |
R3‑082392 | LS on automatic neighbour relation | RAN3 | email#05 |
page generated from database: 2024-07-20 12:15:34