3GPP TDocs (written contributions) at meeting
Meeting: R3-59b - 2008-03-31 to 2008-04-03, Shenzhen
meeting id: R3-59b (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑080575 | Agenda RAN3#59bis ,Shenzen, China 31 March - 03 April 2008 | Chairman | - |
R3‑080576 | Revised report of RAN3#59, Sorrento, Italy | MCC | - |
R3‑080577 | Synchronization in Radio Access Networks (ls218 Source: ITU-T SG15, To: TSG-RAN WG3, Cc: ) | ITU-T SG15 | - |
R3‑080578 | [DRAFT] LS on ETWS (GP-080410 Source: TSG GERAN, To: TSG SA WG1,TSG SA WG2, Cc: TSG RAN WG2,TSG RAN WG3,CT1,TSG SA WG3) | TSG GERAN | - |
R3‑080579 | Reply LS on CSG related mobility (stage 2 text) (GP-080417 Source: TSG GERAN, To: TSG SA WG1,TSG RAN WG2, Cc: TSG SA WG2,TSG RAN WG3,TSG RAN WG4,TSG RAN WG1) | TSG GERAN | reply to R2-075478=R3-080032 |
R3‑080580 | LS on High Interference Indicator (R1-081148 Source: TSG RAN WG1, To: TSG RAN WG3, Cc: TSG RAN WG2,TSG SA WG5) | TSG RAN WG1 | - |
R3‑080581 | LS on Synchronised E-DCH specification impacts (R1-081150 Source: TSG RAN WG1, To: TSG RAN WG2,TSG RAN WG3,TSG RAN WG4, Cc: ) | TSG RAN WG1 | - |
R3‑080582 | Reply LS on Paging Permission with Access Control (PPAC) (R2-081343 Source: TSG RAN WG2, To: CT1,TSG RAN WG3, Cc: TSG GERAN) | TSG RAN WG2 | reply to C1-080667 |
R3‑080583 | Reply-LS on “subscriber type” indication via S1 (R2-081355 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG RAN WG3,CT4) | TSG RAN WG2 | reply to R3-080043=S2-080965 |
R3‑080584 | Response LS to R2-081198/CT1-080399 on retransmission of UL and DL NAS message during inter-eNB handovers. (R2-081361 Source: TSG RAN WG2, To: TSG CT1, Cc: TSG RAN WG3) | TSG RAN WG2 | reply to R3-080410=CT1-080399 |
R3‑080585 | LS on PRB usage measurements in reply to R1-080617 (R2-081368 Source: TSG RAN WG2, To: TSG RAN WG1,TSG RAN WG3, Cc: None) | TSG RAN WG2 | R3-080038=R1-080617 |
R3‑080586 | Reply LS on inter-MME load balancing, Attach/TAU/Service Request procedures and corresponding RRC/S1 connection establishment procedures (R2-081380 Source: TSG RAN WG2, To: TSG SA WG2,CT1, Cc: TSG RAN WG3,TSG SA WG3) | TSG RAN WG2 | - |
R3‑080587 | Draft Response LS on LS Automatic Neighbour Relation (R4-080468 Source: TSG RAN WG4, To: TSG RAN WG3, Cc: TSG RAN WG2) | TSG RAN WG4 | reply to R3-080472 |
R3‑080588 | LS reply to status of security discussions in RAN2 (S3a071017-v3 Source: TSG SA WG3, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG3 | - |
R3‑080589 | LS on RACH Optimization Use Case (S5-080537r1 Source: TSG SA WG5, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG5 | reply to R3-080009=R2-075464 |
R3‑080590 | LS on Automatic Neighbour Relation (ANR) function (S5-080538 Source: TSG SA WG5, To: TSG RAN WG3, Cc: TSG RAN WG2,TSG RAN WG4) | TSG SA WG5 | reply to R3-072401 |
R3‑080591 | LS on SON OAM Architecture Definition Procedure (S5-080539 Source: TSG SA WG5, To: TSG RAN WG3, Cc: ) | TSG SA WG5 | - |
R3‑080592 | LS reply on RAN Performance monitoring (S5-080540 Source: TSG SA WG5, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG RAN WG1,TSG RAN WG4) | TSG SA WG5 | reply to R3-080530 |
R3‑080593 | LS on neighbour relations and ANR function (S5-080548 Source: TSG SA WG5, To: TSG RAN WG3, Cc: ) | TSG SA WG5 | - |
R3‑080594 | [Draft] LS on signalling Intra/Inter-frequency measurement bandwidth (R4-080541 Source: TSG RAN WG4, To: TSG RAN WG2,TSG RAN WG3,TSG GERAN, Cc: TSG RAN WG1) | TSG RAN WG4 | - |
R3‑080595 | LS on RAN performance monitoring (R2-081364 Source: TSG RAN WG2, To: TSG SA WG5, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑080596 | Liaison to establish working assumptions for the scope of responsibility for optimized handover specification (C1-080779 Source: CT1, To: TSG RAN WG2,TSG RAN WG3,CT4,TSG SA WG2, Cc: ) | CT1 | - |
R3‑080597 | EPS Session management procedure optimisations (C1-080780-LS-out Source: CT1, To: TSG RAN WG2,TSG RAN WG3,CT4, Cc: ) | CT1 | - |
R3‑080598 | LS on Decision of MBMS and LCS in SAE Rel8 Scope Discussions (SP-080223 Source: TSG SA, To: TSG SA WG2,TSG RAN WG1,WG2,WG3, Cc: TSG SA WG1,TSG GERAN WG2) | TSG SA | - |
R3‑080599 | Workplan and Working Procedures v0.29.1 (Rel-7) | MCC | - |
R3‑080600 | LS on Release 8 non-essential SAE features | TSG SA | - |
R3‑080601 | S1 load information distribution in paging procedures | Mitsubishi Electric | - |
R3‑080602 | S1 load information distribution in paging procedures | Mitsubishi Electric | - |
R3‑080603 | Load Balancing & Overload Control concepts for the S1 interface | Motorola | - |
R3‑080604 | UTRAN architecture for the Home Node B | Alcatel-Lucent | - |
R3‑080605 | UTRAN HNB - Comparison between GAN and Iu-based variants | Alcatel-Lucent, Huawei | - |
R3‑080606 | MBMS requirements for GTPv2 | Ericsson | - |
R3‑080607 | Transparent HeNB Gateway | Ericsson | - |
R3‑080608 | S1-flex for HeNB | Ericsson | - |
R3‑080609 | Clarification on the Download of UE Capability Information from the EPC | Ericsson | - |
R3‑080610 | Text Proposal: Clarification on the Download of UE Capability Information from the EPC | Ericsson | - |
R3‑080611 | Dynamic configuration of the X2 interface | Ericsson | - |
R3‑080612 | Definition and range of XXX AP IDs | Ericsson, Samsung | - |
R3‑080613 | Definition of XXX AP IDs | Ericsson, Samsung | - |
R3‑080614 | Extend range of XXX AP IDs, correction of Path Switch Request | Ericsson, Samsung | - |
R3‑080615 | SCTP flow control and overload protection | Ericsson | - |
R3‑080616 | SCTP flow control and overload protection | Ericsson | - |
R3‑080617 | Reset procedures in S1 and X2 | Ericsson | - |
R3‑080618 | Reset parts of S1, Abnormal conditions for Reset procedure | Ericsson | - |
R3‑080619 | Abnormal conditions and corrections for Reset procedure | Ericsson | - |
R3‑080620 | More access restriction information | Ericsson | - |
R3‑080621 | More access restriction information | Ericsson | - |
R3‑080622 | More access restriction information | Ericsson | - |
R3‑080623 | Partial handover | Ericsson | - |
R3‑080624 | Serving PLMN | Ericsson | - |
R3‑080625 | Serving PLMN | Ericsson | - |
R3‑080626 | Serving PLMN | Ericsson | - |
R3‑080627 | Target and Source IDs in S1 handover | Ericsson | - |
R3‑080628 | IDs in S1 HO | Ericsson | - |
R3‑080629 | S1 application data update | Ericsson | - |
R3‑080630 | S1 application data update | Ericsson | - |
R3‑080631 | Capacity factor for S1 load balancing | Ericsson | - |
R3‑080632 | Relative MME capacity factor for S1 flex load balancing | Ericsson | - |
R3‑080633 | S1-CP overload control | Ericsson | - |
R3‑080634 | Introduction of combined ASN.1 and tabular format | Ericsson | - |
R3‑080635 | Introduction of a combined tabular and ASN.1 format in RAN3 | Ericsson | - |
R3‑080636 | Correction of X2AP according to agreed drafting rules | Ericsson | - |
R3‑080637 | Introduction of ICIC support | Ericsson | - |
R3‑080638 | Introduction of ICIC indicators | Ericsson | - |
R3‑080639 | X2 application data update | Ericsson | - |
R3‑080640 | X2 Update procedure | Ericsson | - |
R3‑080641 | Alignment of X2 Release Resource name to S1 naming | Ericsson | - |
R3‑080642 | Alignment of X2 Release Resource name to S1 naming | Ericsson | - |
R3‑080643 | Addition of missing statement on the order of bits in bitstrings | Ericsson | - |
R3‑080644 | Inter RNS mobility: different implementation options and network scenarios | Ericsson | - |
R3‑080645 | Evaluation of enhanced SRNS relocation | Ericsson | - |
R3‑080646 | Frequency synchronization requirements in case of Synchronous Ethernet synchronization method | Orange | 36.401 |
R3‑080647 | Solution for interference reduction SON use case | Orange | 36.300 |
R3‑080648 | Security aspects for Home eNB | Orange | R3.020 |
R3‑080649 | Text proposal for RACH Optimisation Use Case | NTT DoCoMo | - |
R3‑080650 | Way forward on NW Architecture support for ETWS | NTT DoCoMo | - |
R3‑080651 | Clarification on problems in Multihoming and way forward on the number of SCTP association | NTT DoCoMo | - |
R3‑080652 | Consistency between S1 and X2 handover data forwarding handling | NTT DoCoMo | - |
R3‑080653 | Handover cancellation timing in S1 and X2 handover | NTT DoCoMo | - |
R3‑080654 | S1 ECHO procedure on S1 interface | ETRI | - |
R3‑080655 | X2 ECHO procedure on X2 interface | ETRI | - |
R3‑080656 | HNBs Location Certification | Mitsubishi Electric | - |
R3‑080657 | HeNBs and X2 interface | Mitsubishi Electric | - |
R3‑080658 | Dynamic Setup of HNBs for Energy Savings and Interference Reduction | Mitsubishi Electric | - |
R3‑080659 | FFS removal on paging repetition | CATT | - |
R3‑080660 | Addition of new causes for consistency | Nortel, Alcatel-Lucent | - |
R3‑080661 | ASN.1 Compacted List IE | Nortel | - |
R3‑080662 | The Message Structure IE is Strike Back | Nortel | - |
R3‑080663 | Return of the Message Structure IE | Nortel | - |
R3‑080664 | Abnormal condition for S1 Setup: Multiple association reject | Nortel | - |
R3‑080665 | Abnormal condition for X2 Setup: Multiple association reject | Nortel | - |
R3‑080666 | Initial Context Setup Response NAS PDU alignment | Nortel | - |
R3‑080667 | Rapporteur Update for 36.414 and 36.424 | Nortel | - |
R3‑080668 | Reset Resource dedicated procedure | Nortel | - |
R3‑080669 | Reset Resource for S1 | Nortel | - |
R3‑080670 | TRSON: reference to the stage 2 for the ANRF | Alcatel-Lucent | 36.902 |
R3‑080671 | E-UTRAN architecture for Home eNB | Alcatel-Lucent | 25.820 |
R3‑080672 | Alternative Solution for the SCTP Endpoint failure issue | Alcatel-Lucent | - |
R3‑080673 | Redundancy of the SCTP endpoint | Alcatel-Lucent | - |
R3‑080674 | PDCP Status Transfer in S1 handover | Alcatel-Lucent | - |
R3‑080675 | LS on Transfer of PDCP Status Information | Alcatel-Lucent | - |
R3‑080676 | Correction of Count Value and Receive Status | Alcatel-Lucent | - |
R3‑080677 | Specification of Handover causes in LTE | Alcatel-Lucent | - |
R3‑080678 | S1 Specification Principles to succeed the IOT | Alcatel-Lucent, NSN, Nortel, Nokia, NEC | - |
R3‑080679 | Specification Principles for S1AP | Alcatel-Lucent, NSN, Nortel, Nokia, NEC | - |
R3‑080680 | Interaction of Bearer Release and Handover procedures | Alcatel-Lucent | - |
R3‑080681 | Correction of Bearer Release Complete | Alcatel-Lucent | - |
R3‑080682 | UE Context Release over S1 and IOT Issues | Alcatel-Lucent | - |
R3‑080683 | S1 UE Context Release and IOT issues | Alcatel-Lucent | - |
R3‑080684 | Failure of the initial UE message | Alcatel-Lucent | - |
R3‑080685 | Handover target | Alcatel-Lucent | - |
R3‑080686 | Introduction of Handover cause values | Alcatel-Lucent | - |
R3‑080687 | Management of the S-TMSI | Alcatel-Lucent | - |
R3‑080688 | Management of the S-TMSI | Alcatel-Lucent | - |
R3‑080689 | Transfer of UE capabilities over S1 | Alcatel-Lucent | - |
R3‑080690 | Transfer of UE capabilities over S1 | Alcatel-Lucent | - |
R3‑080691 | Update of S1 Setup and relation with Reset procedure | Alcatel-Lucent | - |
R3‑080692 | Update of S1 Setup and relation with Reset procedure | Alcatel-Lucent | - |
R3‑080693 | Misalignment of cause "unspecified" | Alcatel-Lucent | - |
R3‑080694 | X2 Specification Principles to succeed the IOT | Alcatel-Lucent, NSN, Nortel, Nokia, NEC | - |
R3‑080695 | Specification Principles for X2AP | Alcatel-Lucent, NSN, Nortel, Nokia, NEC | - |
R3‑080696 | Correction of Handover cause values | Alcatel-Lucent | - |
R3‑080697 | Self-configuration of the type of handover | Alcatel-Lucent | - |
R3‑080698 | 3G HNB Access Network Architecture Considerations | Kineto Wireless Inc, NEC, Motorola | - |
R3‑080699 | 3G HNB Access Network Protocol Selection | Kineto Wireless Inc, NEC, Motorola | - |
R3‑080700 | HNB Abbreviations alignment adjustment | ZTE | - |
R3‑080701 | Iu-based 3G HNB Architecture | ZTE | - |
R3‑080702 | Self-Optimization for Coverage optimization | ZTE | - |
R3‑080703 | Solution for Coverage and Capacity optimization | ZTE | - |
R3‑080704 | Add Cause values | ZTE | - |
R3‑080705 | Add Cause in Reset Request | ZTE | - |
R3‑080706 | Add Cell Type in Served Cell Information | ZTE | - |
R3‑080707 | Impact of Higher Order Modulation on RAN3 LCR TDD specification | ZTE | - |
R3‑080708 | Introduction of LCR TDD 64QAM in NBAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | - |
R3‑080709 | Introduction of LCR TDD 64QAM in RNSAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | - |
R3‑080710 | Trace deactivation | ZTE | - |
R3‑080711 | Trace deactivation | ZTE | - |
R3‑080712 | Trace Required | ZTE | - |
R3‑080713 | Change Label to QCI | ZTE | - |
R3‑080714 | Modify the Presence of Security Information | ZTE | - |
R3‑080715 | TS 36.444 updates | ZTE | - |
R3‑080716 | Consideration on MBSFN Border cell type | ZTE | - |
R3‑080717 | Consideration on MBMS architecture over HSPA+ | ZTE | - |
R3‑080718 | Proposed Text for Architecture for MBMS provision in E-UTRAN in 36.440 | ZTE | - |
R3‑080719 | 36.401 clean up | NEC | - |
R3‑080720 | Inclusion of eNB capability information in the S1 Setup procedure | NEC | - |
R3‑080721 | Adding eNB Capability Information | NEC | - |
R3‑080722 | discussion and proposal of MME/eNB UE S1AP ID | NEC | - |
R3‑080723 | Correction the description for MME UE S1AP ID | NEC | - |
R3‑080724 | Proposal for the length of MME UE S1AP ID and eNB UE S1AP ID | NEC | - |
R3‑080725 | Adding MME Identity desctipion in 36.401 | NEC | - |
R3‑080726 | The procedure in S1AP for UE Radio Capability transferring | NEC | - |
R3‑080727 | Introducing UE Radio Capability in INITIAL CONTEXT SETUP RESPONSE message | NEC | - |
R3‑080728 | The interaction between S1/X2 Setup procedure S1/X2 reset procedure | NEC | - |
R3‑080729 | Interaction between S1 Setup procedure and Reset procedure | NEC | - |
R3‑080730 | Interaction between X2 Setup procedure and Reset procedure | NEC | - |
R3‑080731 | Clarifications on ANR Blacklists and Whitelists | Qualcomm Europe | - |
R3‑080732 | E-DCH Resource Release in CELL_FACH | Qualcomm Europe | - |
R3‑080733 | Common E-DCH resource usage report | Qualcomm Europe | - |
R3‑080734 | List of E-DCH Resource Parameters | Qualcomm Europe | - |
R3‑080735 | Mapping between H-RNTI and E-RNTI in Enhanced CELL_FACH for 1.28Mcps TDD | TD Tech | n/a |
R3‑080736 | Work frequncy select in Enhanced CELL_FACH | TD Tech | n/a |
R3‑080737 | Differentiated Charging for HNB | Huawei | 25.820 |
R3‑080738 | Requirements for 3G HNB Mobility | Huawei | 25.820 |
R3‑080739 | Possible Enhancements on Iu Interface for 3G HNB Architecture | Huawei | 25.820 |
R3‑080740 | Discussion on deployment of Home eNB | Huawei | R3.020 |
R3‑080741 | Transport efficiency improvement for MBMS service by ROHC | Huawei | R3.022 |
R3‑080742 | Template for Evaluation Table for MBMS improvement | Huawei | R3.022 |
R3‑080743 | Evaluation Table for MBMS improvement | Huawei | R3.022 |
R3‑080744 | Security information transfer in Handover procedure | Huawei | 36.413 |
R3‑080745 | MME introduction to the network | Huawei | 36.300 |
R3‑080746 | Introduction of S1 & X2 update procedures | Huawei | 36.413, 36.423 |
R3‑080747 | Introduction of S1 update procedure | Huawei | - |
R3‑080748 | Introduction of X2 update procedure | Huawei | - |
R3‑080749 | Exchange of S1 Interface Information between eNBs on X2 | Huawei | 36.423 |
R3‑080750 | Specific cause value for X2 handover preparation failure | Huawei | 36.423 |
R3‑080751 | Specific cause value for X2 handover preparation failure | Huawei | - |
R3‑080752 | The addition of IEs in S1 Setup Procedure | Huawei | 36.413 |
R3‑080753 | Correction on the reference section number of the IE Direct Forwarding Path Availability | Huawei | - |
R3‑080754 | Mobility Robustness Optimisation | Huawei | 36.902 |
R3‑080755 | Coverage Optimisation | Huawei | 36.902 |
R3‑080756 | Intra frequency load balancing | Huawei | 36.902 |
R3‑080757 | Idle mode Inter RAT load balancing | Huawei | 36.902 |
R3‑080758 | Neighbor Cell Removal for ANR | China MobileT-Mobile | - |
R3‑080759 | CR_Neighbor Cell Removal for ANR | China Mobile,T-Mobile | 36.902 |
R3‑080760 | Automatic Neighbor Relation function---Idle mode neighbour cell searching | China Mobile | - |
R3‑080761 | improvement on PRB-based load balancing | China Mobile, Huawei | - |
R3‑080762 | Basic ICIC procedures on X2 | China Mobile | - |
R3‑080763 | The NAS message in the SAE bearer release procedure | CATT, Samsung | - |
R3‑080764 | TA Update Procedure optimization | Samsung | - |
R3‑080765 | Enhance DL NAS TRANSPORT message to support S1 logical connection release | Samsung | - |
R3‑080766 | Correction on mis usage of TAI | Samsung | - |
R3‑080767 | Introducing S-TMSI to Initial UE Message | Samsung | - |
R3‑080768 | NAS Non Delivery Indication | Samsung | - |
R3‑080769 | NAS Non Delivery Indication | Samsung | - |
R3‑080770 | SAE bearer management optimization | Samsung | - |
R3‑080771 | SAE bearer management optimization | Samsung | - |
R3‑080772 | UE history information deletion | Samsung Electronics, Nokia Siemens Networks, Nokia | - |
R3‑080773 | Introduction of UE History Information in FDD HSPA evolution | Telecom Italia, Huawei, Nokia Siemens Networks, Nokia | R3.022 |
R3‑080774 | Common E-DCH usage in CELL_FACH state | Huawei | - |
R3‑080775 | 3G HomeNB Architecture Discussion | Vodafone | - |
R3‑080776 | Handling Duplicate TNL associations over X2 | Fujitsu | - |
R3‑080777 | Handling Duplicate TNL associations over X2 | Fujitsu | - |
R3‑080778 | Handling Simultaneous X2 Setup Requests (Solution 1) | Fujitsu | - |
R3‑080779 | Handling Simultaneous X2 Setup Requests (Solution 2) | Fujitsu | - |
R3‑080780 | Draft Reply LS on RAN3 requirements for GTPv2 | Fujitsu | - |
R3‑080781 | S1 connectivity for HeNB | Panasonic | - |
R3‑080782 | MBMS session start procedure | Panasonic, Nokia Siemens Networks | - |
R3‑080783 | 36. 445 Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 data transport (draft V0.0.0) | Panasonic | - |
R3‑080784 | TP on UDP/IP for M1 data transport | Panasonic | - |
R3‑080785 | TP on Diffserv code point marking for M1 data transport | Panasonic | - |
R3‑080786 | R3.021 v0.2.0 | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080787 | On FFS Removal for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080788 | Application of Enhanced Relocation to CS Core network | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080789 | Proposal on agreed scheme for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080790 | Specification Impact for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080791 | R3.022 v0.1.0 | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080792 | On Master Node B+/Legacy RNC Solution for MBMS over Node B+ | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080793 | Proposal on Evaluation for Three alternatives for MBMS over Node B+ | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080794 | Functional Split for Enhanced UL in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080795 | Stage-3 Proposal for Enhanced UL in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080796 | On E-RNTI Allocation for UE with Enhanced UL in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080797 | Solution for mapping between HS-DSCH RNTI and E-RNTI | Nokia Siemens Networks, Nokia | - |
R3‑080798 | Draft Reply LS to HS-DPCCH usage with Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080799 | Draft TS25.401 CR for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | 25.401 |
R3‑080800 | Draft TS25.423 CR for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | 25.423 |
R3‑080801 | Draft TS25.427 CR for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | 25.427 |
R3‑080802 | Draft TS25.433 CR for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | 25.433 |
R3‑080803 | Introduction of FACH DRX Scheme and Foreseen RAN3 Specification impacts | Nokia Siemens Networks, Nokia | - |
R3‑080804 | Small corrections for X2AP | Nokia Siemens Networks, Nokia | - |
R3‑080805 | X2 Setup Update | Nokia Siemens Networks, Nokia | - |
R3‑080806 | Introduction of X2 Information Update | Nokia Siemens Networks, Nokia | - |
R3‑080807 | Introduction of Serving MME Groups in X2 Setup | Nokia Siemens Networks, Nokia | - |
R3‑080808 | Framework for exchange of cell-level measurements on X2AP | Nokia Siemens Networks, Nokia | - |
R3‑080809 | Uplink and Downlink ICIC Indication | Nokia Siemens Networks, Nokia | - |
R3‑080810 | Uplink and Downlink ICIC Indication | Nokia Siemens Networks, Nokia | - |
R3‑080811 | S1AP Support for Handover to CDMA2000 HRPD and 1xRTT | Nokia Siemens Networks, Nokia | - |
R3‑080812 | Solution(s) to the 36.902s Automated Configuration of Physical Cell Identity Use Case | Nokia Siemens Networks, Nokia | - |
R3‑080813 | Issues and Enhanced Framework for the Energy Saving Use Case | Nokia Siemens Networks, Nokia | - |
R3‑080814 | Considerations on 36.902s Interference Reduction Use Case | Nokia Siemens Networks, Nokia | - |
R3‑080815 | Home eNodeB mobility call flows (redux R3-080373) | Nokia Siemens Networks, Nokia | - |
R3‑080816 | TR R3.020 v0.5.0 | Nokia Siemens Networks, Nokia | R3.020 |
R3‑080817 | HeNB GW -addressing aspects | Nokia Siemens Networks, Nokia | - |
R3‑080818 | Comparison of proposed methods for HeNB architectures as proposed in TR R3.020 6.2.1.2 | Nokia Siemens Networks, Nokia | - |
R3‑080819 | Further HeNB simplified S1 connectivity aspects | Nokia Siemens Networks, Nokia | - |
R3‑080820 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080821 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080822 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080823 | Aspects for MME pool configuration updates and eNB Introduction | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080824 | MME pool configuration | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080825 | Overload handling on the S1 interface | Nokia Siemens Networks, Nokia, Vodafone e | - |
R3‑080826 | Overload handling on the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080827 | Overload handling on the S1 interface | Nokia Siemens Networks, Nokia, Vodafone e | - |
R3‑080828 | S1 Setup Update procedure | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080829 | Hierarchy of setup and reset procedures | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080830 | NAS PDU IE in Initial Context Setup Response message | Nokia Siemens Networks, Nokia | - |
R3‑080831 | Default bearer handling | Nokia Siemens Networks, Nokia | - |
R3‑080832 | Early DL data | Nokia Siemens Networks, Nokia | - |
R3‑080833 | Early DL data | Nokia Siemens Networks, Nokia | - |
R3‑080834 | Control and handling of Data Forwarding | Nokia Siemens Networks, Nokia | - |
R3‑080835 | Control and handling of Data Forwarding | Nokia Siemens Networks, Nokia | - |
R3‑080836 | Abnormal condition for handover preparation | Nokia Siemens Networks, Nokia | - |
R3‑080837 | Inter 3GPP-RAT aspects | Nokia Siemens Networks, Nokia | - |
R3‑080838 | Security Aspects | Nokia Siemens Networks, Nokia | - |
R3‑080839 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | - |
R3‑080840 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | - |
R3‑080841 | Criticality diagnostics | Nokia Siemens Networks, Nokia | - |
R3‑080842 | ASN.1 & tabular style for S1/X2AP | Nokia Siemens Networks, Nokia, Alcatel-Lucent, Nortel | - |
R3‑080843 | ETWS aspects in EUTRAN | Nokia Siemens Networks, Nokia | - |
R3‑080844 | Reply LS to SA2 regarding ETWS Security (S3-080219 Source: TSG SA WG3, To: TSG SA WG2, Cc: TSG RAN WG2,TSG RAN WG3,TSG GERAN WG2,CT1,TSG SA WG1) | TSG SA WG3 | - |
R3‑080845 | Reply LS on outstanding NAS messages (S3-080229 Source: TSG SA WG3, To: TSG RAN WG2, Cc: TSG RAN WG3,CT1) | TSG SA WG3 | reply to R2-080601 |
R3‑080846 | Reply LS to RAN3 regarding the security of Home eNB (S3-080263 Source: TSG SA WG3, To: TSG RAN WG3, Cc: ) | TSG SA WG3 | - |
R3‑080847 | Coordination of MCEs by the EPC using Resource Refer-ences | Alcatel-Lucent | - |
R3‑080848 | Synchronization issue for E-MBMS signaling | Alcatel-Lucent, Alcatel Shanghai Bell | - |
R3‑080849 | Open Issues on resource allocation and multiplexing | Alcatel-Lucent, Alcatel Shanghai Bell | - |
R3‑080850 | Skeleton for 36.440 | Alcatel-Lucent | - |
R3‑080851 | Proactive ICIC Signalling Introduction | Alcatel-Lucent | - |
R3‑080852 | Multiple SCTP associations option | Nortel, Samsung | - |
R3‑080853 | Text proposal for S1 Multiple SCTP association | Nortel, Samsung | - |
R3‑080854 | Text proposal for X2 Multiple SCTP associations | Nortel | - |
R3‑080855 | EPS Identifiers discussion | Nortel | - |
R3‑080856 | ANR Neighbors IP address lookup and establishment | Nortel | - |
R3‑080857 | Discussion on Load Balancing | Nortel | - |
R3‑080858 | SAE Bearer NAS PDU handling none alignment with RRC | Nortel | - |
R3‑080859 | MME configuration at S1 Setup | Nortel | - |
R3‑080860 | Abnormal Condition for S1 Setup | Nortel | - |
R3‑080861 | S1-U TNL congestion indication | T-Mobile, Orange | 36.300 |
R3‑080862 | Trace Support: Support of Configuration and Pulling of Trace Data | T-Mobile, Orange | - |
R3‑080863 | HeNB GW architectural improvements | Nokia Siemens Networks, Nokia | - |
R3‑080864 | Capturing cell uplink overload indicator in X2-AP | Motorola | - |
R3‑080865 | Load balancing scheme and X2 message support | Motorola | - |
R3‑080866 | Automatic physical cell identity configuration | Ericsson | - |
R3‑080867 | Inter-RAT/Frequency ANR (Agreed text) | Ericsson | - |
R3‑080868 | Inter-RAT/Frequency ANR (Proposed update) | Ericsson | - |
R3‑080869 | Intra LTE ANR (Proposed update) | Ericsson, Nokia Siemens Networks, Nokia Corporation, T-Mobile, Qualcomm Europe | - |
R3‑080870 | Discussion on ETWS | Ericsson | - |
R3‑080871 | Served Cell Information alignment with RRC 36.331 | Ericsson | - |
R3‑080872 | Align Status Transfer to PDCP | Ericsson | - |
R3‑080873 | Align Status Transfer to PDCP | Ericsson | - |
R3‑080874 | Align Status Transfer to PDCP | Ericsson | - |
R3‑080875 | Align Status Transfer to PDCP | Ericsson | - |
R3‑080876 | Analysis of Packet Disordering at S-GW Change | Ericsson | - |
R3‑080877 | Switching the UL Tunnel Endpoint in the Path Switch Request procedure | Ericsson | - |
R3‑080878 | TAI Clean up | Ericsson | - |
R3‑080879 | TAI Clean up | Ericsson | - |
R3‑080880 | Partial handover | Ericsson | - |
R3‑080881 | Partial handover | Ericsson | - |
R3‑080882 | Partial X2 handover | Ericsson | - |
R3‑080883 | HO restriction info in Path Switch | Ericsson | - |
R3‑080884 | Max Transport Block Size limit for EUL in CELL_FACH UEs | Ericsson | - |
R3‑080885 | Inter-RAT ANR enhancement: Target Node Addressing in UTRAN | NEC | 36.300 |
R3‑080886 | Fast CS service redirection for LTE | NEC | 36.413 |
R3‑080887 | Addition of explicit TRACE START message | Ericsson | - |
R3‑080888 | Addition of explicit TRACE START message | Ericsson | - |
R3‑080889 | Addition of explicit TRACE START message | Ericsson | - |
R3‑080890 | Addition of explicit TRACE START message | Ericsson | - |
R3‑080891 | Correction of Trace Reference IE | Ericsson | - |
R3‑080892 | Correction of Trace Reference IE | Ericsson | - |
R3‑080893 | Correction of Trace Reference IE | Ericsson | - |
R3‑080894 | U-plane handling in Inter RAT Handover | NTT DoCoMo | - |
R3‑080895 | The discussion and proposal on the S1 Setup/Update | NEC | - |
R3‑080896 | The discussion and proposal on the X2 Setup/Update | NEC | - |
R3‑080897 | Details on Load Balancing and ICIC Signaling Mechanism | NEC | - |
R3‑080898 | Details on Load Balancing and ICIC Signaling Mechanism | NEC | - |
R3‑080899 | Rejection causes over X2 | Alcatel-Lucent | - |
R3‑080900 | Rejection causes over X2 | Alcatel-Lucent | - |
R3‑080901 | LS on CS Fallback (S2-081993_e-mail-rev1_appd_S2-081988 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3,CT WG1,CT WG4, Cc: ) | TSG SA WG2 | - |
R3‑080902 | Text proposal for RACH Optimisation Use Case | NTT DoCoMo, T-Mobile, Orange, Vodafone | - |
R3‑080903 | Iu-based 3G HNB Architecture | ZTE | - |
R3‑080904 | void | - | - |
R3‑080905 | Short notes on small nodes | Nokia Siemens Networks, Nokia | - |
R3‑080906 | Final report of RAN3#59, Sorrento, Italy | MCC | - |
R3‑080907 | Workplan and Working Procedures v0.30.0 (Rel-8) | MCC | - |
R3‑080908 | Adding MME Identity desctipion in 36.401 | NEC | - |
R3‑080909 | 36.401 clean up | NEC | - |
R3‑080910 | Frequency synchronization requirements in case of Synchronous Ethernet synchronization method | Orange | - |
R3‑080911 | SCTP flow control and overload protection | Ericsson | - |
R3‑080912 | SCTP flow control and overload protection | Ericsson | - |
R3‑080913 | LS on the necessity of to convey ‘Receive Status of UL PDCP SDU’ in S1 Handover | NTT DoCoMo | - |
R3‑080914 | LS on Transfer of PDCP Status Information | Alcatel-Lucent | - |
R3‑080915 | Correction of Count Value and Receive Status | Alcatel-Lucent | - |
R3‑080916 | Multicast mode in improved GGSN solution | NSN, Nokia | - |
R3‑080917 | LS on PDCP reset | Nokia Siemens Networks | - |
R3‑080918 | Trace deactivation | ZTE | - |
R3‑080919 | Addition of explicit TRACE START message | Ericsson | - |
R3‑080920 | Reset parts of S1, Abnormal conditions for Reset procedure | Ericsson | - |
R3‑080921 | LS on frequency restrictions | Ericsson | - |
R3‑080922 | Partial handover | Ericsson | - |
R3‑080923 | Partial handover | Ericsson | - |
R3‑080924 | Partial X2 handover | Ericsson | - |
R3‑080925 | merged TAI Clean up | Ericsson,Samsung | - |
R3‑080926 | merged TAI Clean up | Ericsson,Samsung | - |
R3‑080927 | Failure of the initial UE message | Alcatel-Lucent | - |
R3‑080928 | S1 Handover Cancellation procedure | NTT DoCoMo | - |
R3‑080929 | S1 Handover Cancellation procedure | NTT DoCoMo | - |
R3‑080930 | Impact of Higher Order Modulation on RAN3 LCR TDD specification | ZTE | - |
R3‑080931 | Introduction of LCR TDD 64QAM in NBAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | - |
R3‑080932 | Introduction of LCR TDD 64QAM in RNSAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | - |
R3‑080933 | Clarifications on ANR Blacklists and Whitelists | Qualcomm Europe, T-Mobile, Telecom Italia, Orange | - |
R3‑080934 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080935 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080936 | LS on S1 Overload Control | Nokia Siemens Networks | - |
R3‑080937 | S1AP Support for Handover to CDMA2000 HRPD and 1xRTT | Nokia Siemens Networks, Nokia, Alcatel Lucent, Ericsson, Motorola, Nortel, Verizon Wireless | - |
R3‑080938 | Clarify the Master NodeB+/Legacy RNC Solution for MBMS over Node B+ | Huawei | - |
R3‑080939 | Consideration on GGSN improvement for MBMS over Node B+ | Huawei | - |
R3‑080940 | Consideration on C-plane procedure over NodeB+ | Huawei | - |
R3‑080941 | Introduction of ICIC indicators | Ericsson | - |
R3‑080942 | LS on RAN2 status on enhanced uplink for CELL_FACH state in FDD (R2-081969 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: TSG RAN WG1) | TSG RAN WG2 | - |
R3‑080943 | Reply LS on neighbour relations and ANR function | Qualcomm | - |
R3‑080944 | Status transfer container | Alcatel-Lucent | - |
R3‑080945 | Correction of Handover cause values | Alcatel-Lucent | - |
R3‑080946 | Redundancy of the SCTP endpoint | Alcatel-Lucent | - |
R3‑080947 | Text proposal for RACH Optimisation Use Case | NTT DoCoMo, T-Mobile, Orange, Vodafone | - |
R3‑080948 | Transparent HeNB Gateway | Ericsson | - |
R3‑080949 | Draft Reply LS on RAN3 requirements for GTPv2 | Fujitsu | - |
R3‑080950 | Extend range of XXX AP IDs, correction of Path Switch Request | Ericsson, Samsung, NEC | - |
R3‑080951 | Extended range of MME S1AP ID for the source UE association | Ericsson | - |
R3‑080952 | Correction the description for MME UE S1AP ID | NEC, Ericsson, Samsung | - |
R3‑080953 | DRAFT LS on the Introduction of UE History Information in HSPA evolution | Telecom Italia | - |
R3‑080954 | Functional Split for Enhanced UL in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080955 | Impact of Higher Order Modulation on RAN3 LCR TDD specification | ZTE | - |
R3‑080956 | Introduction of LCR TDD 64QAM in NBAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | - |
R3‑080957 | Introduction of LCR TDD 64QAM in RNSAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | - |
R3‑080958 | Clarifications on ANR Blacklists and Whitelists | Qualcomm Europe, T-Mobile, Telecom Italia, Orange | - |
R3‑080959 | Interaction of Bearer Release and Handover procedures | Alcatel-Lucent | - |
R3‑080960 | SAE bearer management optimization | Samsung | - |
R3‑080961 | LS on RAN2 status on UE DRX (R2-081974 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑080962 | Draft Reply LS to HS-DPCCH usage with Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080963 | Reply LS to HS-DPCCH usage with Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080964 | DRAFT LS on the Introduction of UE History Information in HSPA evolution | Telecom Italia | - |
R3‑080965 | S1 ECHO procedure on S1 interface | ETRI | - |
R3‑080966 | X2 ECHO procedure on S1 interface | ETRI | - |
R3‑080967 | S1 ECHO procedure on S1 interface | ETRI | - |
R3‑080968 | X2 ECHO procedure on X2 interface | ETRI | - |
R3‑080969 | Redundancy of the SCTP endpoint | - | - |
R3‑080970 | MBMS over eHSPA Flat Architecture Adhoc Summary | adhoc-chair | - |
R3‑080971 | Frequency synchronization requirements in case of Synchronous Ethernet synchronization method | Orange | check ITU-T status, not for big CR |
R3‑080972 | Adding MME Identity desctipion in 36.401 | NEC | - |
R3‑080973 | SCTP flow control and overload protection | Ericsson | - |
R3‑080974 | SCTP flow control and overload protection | Ericsson | - |
R3‑080975 | LS on the necessity of to convey ‘Receive Status of UL PDCP SDU’ in S1 Handover | NTT DoCoMo | - |
R3‑080976 | LS on the necessity of to convey ‘Receive Status of UL PDCP SDU’ in S1 Handover | RAN3 | - |
R3‑080977 | LS on Transfer of PDCP Status Information | RAN3 | - |
R3‑080978 | Correction of Count Value and Receive Status | Alcatel-Lucent | - |
R3‑080979 | LS on frequency restrictions | RAN3 | - |
R3‑080980 | SAE bearer management optimization | Samsung | - |
R3‑080981 | Partial X2 handover | Ericsson | - |
R3‑080982 | Partial X2 handover | RAN3 | - |
R3‑080983 | DRAFT LS on the Introduction of UE History Information in HSPA evolution | Telecom Italia | - |
R3‑080984 | LS on the Introduction of UE History Information in HSPA evolution | RAN3 | - |
R3‑080985 | TR R3.021v0.3.0 | NSN | - |
R3‑080986 | LS on Enhancements for SRNS Relocation | Nokia Siemens Networks | - |
R3‑080987 | Reply LS on neighbour relations and ANR function | Qualcomm | - |
R3‑080988 | Clarifications on ANR Blacklists and Whitelists | Qualcomm Europe, T-Mobile, Telecom Italia, Orange | - |
R3‑080989 | Text proposal for RACH Optimisation Use Case | NTT DoCoMo, T-Mobile, Orange, Vodafone | - |
R3‑080990 | Draft Reply LS on RAN3 requirements for GTPv2 | RAN3 | - |
R3‑080991 | SCTP flow control and overload protection | Ericsson | - |
R3‑080992 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080993 | LS on S1 Overload Control | Nokia Siemens Networks | - |
R3‑080994 | LS on Enhancements for SRNS Relocation | RAN3 | TR in attachment under email check |
R3‑080995 | Functional Split for Enhanced UL in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑080996 | Redundancy of the SCTP endpoint | Alcatel-Lucent | - |
R3‑080997 | Status transfer container | Alcatel-Lucent | - |
R3‑080998 | Reset parts of S1, Abnormal conditions for Reset procedure | Ericsson | - |
R3‑080999 | UTRAN architecture for the Home Node B | Alcatel-Lucent | - |
R3‑081000 | Iu-based 3G HNB Architecture | ZTE | - |
R3‑081001 | RAN3#59bis changes for TS 36.300 | Ericsson | - |
R3‑081002 | RAN3#59bis changes for TS 36.401 | NEC | - |
R3‑081003 | RAN3#59bis changes for TS 36.413 | Nokia Siemens Networks | - |
R3‑081004 | RAN3#59bis changes for TS 36.423 | Ericsson | - |
R3‑081005 | Redundancy of the SCTP endpoint | Alcatel-Lucent | - |
R3‑081006 | 3G HNB Access Network Architecture Considerations | Kineto Wireless Inc, NEC, Motorola | - |
R3‑081007 | Short notes on small nodes | Nokia Siemens Networks, Nokia | - |
R3‑081008 | - | - | - |
page generated from database: 2024-09-26 11:02:35