The document discusses frequency band arrangements for 3.4-3.8 GHz in various regions and countries. It summarizes band plans in Europe, Japan, Latin America, and North America based on studies and decisions from regulatory bodies. Baseline frequency arrangements are identified for further specification work on UMTS and LTE in the 3400-3600 MHz band based on the regional summaries. The document also covers deployment aspects and required changes to 3GPP specifications to support operation in the 3.4-3.8 GHz band.
- This document describes a system for interworking between 3GPP systems and wireless local area networks (WLANs). It defines the architecture and procedures to provide authentication, authorization, and access control for WLAN users to access 3GPP services and IP connectivity. It also covers charging, quality of service, and other aspects of the interworking system.
This document provides a summary of key specifications for multiplexing and channel coding in LTE, including:
- It defines channel coding, multiplexing and interleaving procedures for both uplink and downlink transmissions.
- For uplink transmissions, it specifies channel coding for the random access channel and uplink shared channel, including transport block CRC attachment, code block segmentation, channel coding, rate matching and code block concatenation.
- It also defines channel coding for various control information formats reported on the uplink, such as channel quality information formats for different types of channel quality reports.
This document is a technical specification from ETSI that defines protocols for digital cellular telecommunications and Universal Mobile Telecommunications Systems (UMTS). It focuses on the core network protocols in the mobile radio interface and covers topics such as mobility management, call control, and session management. The document is over 100 pages and provides in-depth information on protocols and procedures for cellular networks.
This document is a technical specification from ETSI that defines the radio resource control protocol for LTE cellular networks. It specifies aspects of the protocol such as system information acquisition, services provided to upper layers, UE states and transitions, and general requirements for procedures. The document is 3GPP TS 36.331 version 10.2.0 Release 10.
This document provides 3GPP technical specifications for LTE user equipment radio access capabilities. It defines parameters including UE category, transport channel capabilities, physical channel capabilities, RF parameters, measurement capabilities, inter-RAT parameters, general parameters, and optional features. The document aims to standardize radio access capabilities to enable interoperability between UE and network equipment.
This document defines the E-UTRA UE radio access capability parameters as specified in 3GPP TS 36.306 version 10.7.0 Release 10. It includes parameters such as UE category, transport channel parameters, physical channel parameters, RF parameters, measurement parameters, inter-RAT parameters, general parameters, and optional features without UE radio access capability parameters. The document provides information needed for the network to utilize the full capabilities of the UE in E-UTRA networks.
This document provides a technical summary of the 410-430 MHz frequency band for LTE public protection and disaster relief (PPDR) and professional mobile radio (PMR) applications in Europe. It describes the relevant frequency allocations and compatibility studies. Key decisions by the Electronic Communications Committee allow the introduction of broadband LTE systems in the 410-415 MHz, 411-416 MHz, and 412-417 MHz bands for both PPDR and land mobile applications, with channel bandwidths of 1.4, 3, and 5 MHz. Emission limits for user equipment and base stations are specified to protect existing services operating in adjacent bands such as PMR, radio astronomy, and radiolocation.
This document provides specifications for Hybrid Broadcast Broadband TV (HbbTV). It defines an application model and JavaScript API to allow interactive applications to be delivered via broadcast or broadband and run seamlessly on a connected TV. The document covers key aspects of the HbbTV system including application signaling, lifecycle and synchronization of broadcast content. It also defines terminal capabilities and security requirements to ensure a consistent user experience across devices.
- This document describes a system for interworking between 3GPP systems and wireless local area networks (WLANs). It defines the architecture and procedures to provide authentication, authorization, and access control for WLAN users to access 3GPP services and IP connectivity. It also covers charging, quality of service, and other aspects of the interworking system.
This document provides a summary of key specifications for multiplexing and channel coding in LTE, including:
- It defines channel coding, multiplexing and interleaving procedures for both uplink and downlink transmissions.
- For uplink transmissions, it specifies channel coding for the random access channel and uplink shared channel, including transport block CRC attachment, code block segmentation, channel coding, rate matching and code block concatenation.
- It also defines channel coding for various control information formats reported on the uplink, such as channel quality information formats for different types of channel quality reports.
This document is a technical specification from ETSI that defines protocols for digital cellular telecommunications and Universal Mobile Telecommunications Systems (UMTS). It focuses on the core network protocols in the mobile radio interface and covers topics such as mobility management, call control, and session management. The document is over 100 pages and provides in-depth information on protocols and procedures for cellular networks.
This document is a technical specification from ETSI that defines the radio resource control protocol for LTE cellular networks. It specifies aspects of the protocol such as system information acquisition, services provided to upper layers, UE states and transitions, and general requirements for procedures. The document is 3GPP TS 36.331 version 10.2.0 Release 10.
This document provides 3GPP technical specifications for LTE user equipment radio access capabilities. It defines parameters including UE category, transport channel capabilities, physical channel capabilities, RF parameters, measurement capabilities, inter-RAT parameters, general parameters, and optional features. The document aims to standardize radio access capabilities to enable interoperability between UE and network equipment.
This document defines the E-UTRA UE radio access capability parameters as specified in 3GPP TS 36.306 version 10.7.0 Release 10. It includes parameters such as UE category, transport channel parameters, physical channel parameters, RF parameters, measurement parameters, inter-RAT parameters, general parameters, and optional features without UE radio access capability parameters. The document provides information needed for the network to utilize the full capabilities of the UE in E-UTRA networks.
This document provides a technical summary of the 410-430 MHz frequency band for LTE public protection and disaster relief (PPDR) and professional mobile radio (PMR) applications in Europe. It describes the relevant frequency allocations and compatibility studies. Key decisions by the Electronic Communications Committee allow the introduction of broadband LTE systems in the 410-415 MHz, 411-416 MHz, and 412-417 MHz bands for both PPDR and land mobile applications, with channel bandwidths of 1.4, 3, and 5 MHz. Emission limits for user equipment and base stations are specified to protect existing services operating in adjacent bands such as PMR, radio astronomy, and radiolocation.
This document provides specifications for Hybrid Broadcast Broadband TV (HbbTV). It defines an application model and JavaScript API to allow interactive applications to be delivered via broadcast or broadband and run seamlessly on a connected TV. The document covers key aspects of the HbbTV system including application signaling, lifecycle and synchronization of broadcast content. It also defines terminal capabilities and security requirements to ensure a consistent user experience across devices.
This document provides a technical specification for 5G New Radio (NR) user equipment (UE) radio transmission and reception in the frequency range of 450 MHz to 6 GHz. It specifies the operating bands and channelization for NR, the UE transmitter characteristics including output power, output power dynamics and time masks. It also addresses carrier aggregation and dual connectivity configurations and their impact on the transmitter requirements. The document contains requirements to ensure compatibility between NR equipment from different manufacturers.
This document provides specifications for using video and audio coding in digital broadcasting applications based on the MPEG-2 Transport Stream. It covers systems layer aspects like transport streams, transport stream packets, adaptation fields, and packetized elementary stream packets. The document defines requirements for baseline IRDs (integrated receiver decoders) and specifies fields in the transport packet and PES packet headers.
This document describes the overall architecture of the UTRAN (Universal Terrestrial Radio Access Network), including its internal interfaces and assumptions about the radio and Iu interfaces. It defines UTRAN identifiers, transport addresses, and function distribution principles. It also describes UTRAN functions related to radio resource management, mobility, broadcast/multicast services, and MBMS (Multimedia Broadcast Multicast Service).
This document defines the stage 2 specifications for out-of-band transcoder control (OoBTC) for speech services in 3GPP networks. It describes the principles and procedures to support transcoder free operation (TrFO), tandem free operation (TFO), and the interworking between TrFO and TFO. The document also covers codec negotiation using SIP for OoBTC on the Nc interface.
The document is a technical specification from ETSI that defines the physical layer procedures for LTE E-UTRA radio access. It specifies procedures for synchronization, power control, random access, physical downlink shared channel, channel state information reporting, HARQ-ACK reporting, physical uplink shared channel, physical downlink control channel assignment, physical uplink control channel assignment, and physical multicast channel. The document also defines reference signal procedures and assumptions for uplink/downlink configuration determination.
This document is a technical specification from the European Telecommunications Standards Institute (ETSI) that defines the General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access, also known as LTE. It covers the general aspects of architecture and functions for packet data networks and connected devices. The specification addresses topics like network access control, packet routing and transfer, security, mobility management, radio resource management, selection functions, and the network elements involved like E-UTRAN, MME, gateways, and PCRF.
This document specifies the KASUMI block cipher algorithm, which forms the core of the 3GPP confidentiality and integrity algorithms f8 and f9. It defines the algorithm structure, components, and operation over multiple rounds using subfunctions and subkeys. KASUMI encrypts a 64-bit input under the control of a 128-bit key to produce a 64-bit output. The specification is normative, with additional informative annexes providing illustrations and sample code.
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
Network architecture
(3GPP TS 23.002 version 5.12.0 Release 5)
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
R
This document provides a technical specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC) protocol. It specifies the protocol architecture, services, functions, and procedures, including system information acquisition, connection control, radio bearer control, mobility procedures, and security functions. The RRC protocol is defined as part of the Layer 3 radio interface protocol architecture for E-UTRA and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
This document describes 3GPP TS 36.214 which specifies measurements in LTE networks. It defines UE and E-UTRAN measurement capabilities for various metrics like Reference Signal Received Power, Reference Signal Received Quality, timing measurements, and location measurements. It also covers control of measurements and measurement abilities of the UE and E-UTRAN nodes.
The document is the installation guide for the TI-Navigator system. It contains information about installing and setting up the TI-Navigator hardware components like the network hub and access point. The document also provides regulatory information for different regions to ensure compliance with wireless communication standards.
Thuraya Introduced the new best-value satellite phone, Thuraya XT-LITE, which provides you the basic functionality as call and SMS.
Buy Thuraya XT-LITE today from Cygnus Telecom in Dubai. Please contact us today at info@cygnustelecom.com or visit our website www.cygnustelecom.com for more details.
We can ship Thuraya XT-LITE worldwide.
This document compares different options for a pre-paid telecommunications business:
1) Traditional retail options involve high upfront costs like deposits, expensive phones and contracts that make it difficult to earn a profit.
2) A franchise model offers residuals but involves risks of chargebacks and high fees that may result in operating at a loss.
3) Ynot Mobile offers a wholesale model with direct access to distributors and flexibility to set competitive prices with no restrictions. This allows earning profits upfront with lower risks.
The document promotes Ynot Mobile as providing a better opportunity than traditional retail or franchise models for a pre-paid telecommunications business.
Waqas Khan Jadoon is seeking a position that allows him to be effective for himself, his organization, and society. He has a PhD in Botany from Hazara University in Pakistan, as well as other academic qualifications. His research focuses on the plants of areas in Pakistan such as Thandiani Forests. He has work experience as a lecturer and is skilled in Microsoft Office, research, and languages including English, Urdu, and others.
Shapes is a fitness company founded in 1995 by Mr. Nadeem Ahmad with headquarters in Gulberg and branches in several Pakistani cities. It has over 400 employees across departments like marketing, HR, finance, and operations. Shapes offers high-class facilities like executive and regular gyms for men and women, aerobics halls, swimming pools, sports courts, and a spa. For communication, it uses forms, emails, meetings, letters, memos, advertisements, and visiting cards both internally and externally. The document discusses Shapes' communication channels, barriers, and the importance of the 7 C's in business communication.
Juliet Larsen had a severe allergic reaction to peanut butter at 15 months old that caused her heart to stop. Her mother Louise became an advocate for requiring schools to stock epinephrine auto-injectors (EpiPens) to treat anaphylaxis. A new law will take effect in January requiring public schools in California to have EpiPens. Louise started a Facebook group that now has over 7,000 members to raise awareness on life-threatening food allergies and advocate for policies like this new law.
Formula One delivered value to various customer groups by satisfying their wants and needs:
1) Carmakers used Formula One for innovation and testing to develop new technologies for production cars, as well as for branding and promotion.
2) TV broadcasters and media outlets gained access to a global audience, improving their businesses and diversifying their programming.
3) Sponsors received a huge global platform to promote their brands to spectators worldwide.
4) Local governments and businesses benefited from the prestige and wealth generated by hosting races.
If you are thinking about setting up a blog for business this free guide can lead you on the way to achieve the income you have always dreamed of. Or, if you already have a blog for you business, but are not quite getting the results you want, then this guide can reveal priceless information that you may be missing.
The document provides an overview of operating systems. It begins with definitions of an operating system and its roles in providing resources to users and applications and coordinating access to resources. It then discusses operating system concepts like process management, memory management, file management, I/O management, and protection systems. It outlines the evolution of operating systems from early batch systems to modern networked and distributed systems. It also discusses different operating system structures like kernel-based approaches, layered approaches, and virtual machine approaches.
Prashant Plastic Industries LLP is an Indian company that manufactures and retails industrial process equipment. Since 1980, it has produced products like blowers, chimneys, and tanks from quality materials. It offers customized equipment and after-sales support to various industries. Located in Mumbai, the company has 51-100 employees and exports to markets in Asia and the Middle East.
This document provides a technical specification for 5G New Radio (NR) user equipment (UE) radio transmission and reception in the frequency range of 450 MHz to 6 GHz. It specifies the operating bands and channelization for NR, the UE transmitter characteristics including output power, output power dynamics and time masks. It also addresses carrier aggregation and dual connectivity configurations and their impact on the transmitter requirements. The document contains requirements to ensure compatibility between NR equipment from different manufacturers.
This document provides specifications for using video and audio coding in digital broadcasting applications based on the MPEG-2 Transport Stream. It covers systems layer aspects like transport streams, transport stream packets, adaptation fields, and packetized elementary stream packets. The document defines requirements for baseline IRDs (integrated receiver decoders) and specifies fields in the transport packet and PES packet headers.
This document describes the overall architecture of the UTRAN (Universal Terrestrial Radio Access Network), including its internal interfaces and assumptions about the radio and Iu interfaces. It defines UTRAN identifiers, transport addresses, and function distribution principles. It also describes UTRAN functions related to radio resource management, mobility, broadcast/multicast services, and MBMS (Multimedia Broadcast Multicast Service).
This document defines the stage 2 specifications for out-of-band transcoder control (OoBTC) for speech services in 3GPP networks. It describes the principles and procedures to support transcoder free operation (TrFO), tandem free operation (TFO), and the interworking between TrFO and TFO. The document also covers codec negotiation using SIP for OoBTC on the Nc interface.
The document is a technical specification from ETSI that defines the physical layer procedures for LTE E-UTRA radio access. It specifies procedures for synchronization, power control, random access, physical downlink shared channel, channel state information reporting, HARQ-ACK reporting, physical uplink shared channel, physical downlink control channel assignment, physical uplink control channel assignment, and physical multicast channel. The document also defines reference signal procedures and assumptions for uplink/downlink configuration determination.
This document is a technical specification from the European Telecommunications Standards Institute (ETSI) that defines the General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access, also known as LTE. It covers the general aspects of architecture and functions for packet data networks and connected devices. The specification addresses topics like network access control, packet routing and transfer, security, mobility management, radio resource management, selection functions, and the network elements involved like E-UTRAN, MME, gateways, and PCRF.
This document specifies the KASUMI block cipher algorithm, which forms the core of the 3GPP confidentiality and integrity algorithms f8 and f9. It defines the algorithm structure, components, and operation over multiple rounds using subfunctions and subkeys. KASUMI encrypts a 64-bit input under the control of a 128-bit key to produce a 64-bit output. The specification is normative, with additional informative annexes providing illustrations and sample code.
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
Network architecture
(3GPP TS 23.002 version 5.12.0 Release 5)
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
R
This document provides a technical specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC) protocol. It specifies the protocol architecture, services, functions, and procedures, including system information acquisition, connection control, radio bearer control, mobility procedures, and security functions. The RRC protocol is defined as part of the Layer 3 radio interface protocol architecture for E-UTRA and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
This document describes 3GPP TS 36.214 which specifies measurements in LTE networks. It defines UE and E-UTRAN measurement capabilities for various metrics like Reference Signal Received Power, Reference Signal Received Quality, timing measurements, and location measurements. It also covers control of measurements and measurement abilities of the UE and E-UTRAN nodes.
The document is the installation guide for the TI-Navigator system. It contains information about installing and setting up the TI-Navigator hardware components like the network hub and access point. The document also provides regulatory information for different regions to ensure compliance with wireless communication standards.
Thuraya Introduced the new best-value satellite phone, Thuraya XT-LITE, which provides you the basic functionality as call and SMS.
Buy Thuraya XT-LITE today from Cygnus Telecom in Dubai. Please contact us today at info@cygnustelecom.com or visit our website www.cygnustelecom.com for more details.
We can ship Thuraya XT-LITE worldwide.
This document compares different options for a pre-paid telecommunications business:
1) Traditional retail options involve high upfront costs like deposits, expensive phones and contracts that make it difficult to earn a profit.
2) A franchise model offers residuals but involves risks of chargebacks and high fees that may result in operating at a loss.
3) Ynot Mobile offers a wholesale model with direct access to distributors and flexibility to set competitive prices with no restrictions. This allows earning profits upfront with lower risks.
The document promotes Ynot Mobile as providing a better opportunity than traditional retail or franchise models for a pre-paid telecommunications business.
Waqas Khan Jadoon is seeking a position that allows him to be effective for himself, his organization, and society. He has a PhD in Botany from Hazara University in Pakistan, as well as other academic qualifications. His research focuses on the plants of areas in Pakistan such as Thandiani Forests. He has work experience as a lecturer and is skilled in Microsoft Office, research, and languages including English, Urdu, and others.
Shapes is a fitness company founded in 1995 by Mr. Nadeem Ahmad with headquarters in Gulberg and branches in several Pakistani cities. It has over 400 employees across departments like marketing, HR, finance, and operations. Shapes offers high-class facilities like executive and regular gyms for men and women, aerobics halls, swimming pools, sports courts, and a spa. For communication, it uses forms, emails, meetings, letters, memos, advertisements, and visiting cards both internally and externally. The document discusses Shapes' communication channels, barriers, and the importance of the 7 C's in business communication.
Juliet Larsen had a severe allergic reaction to peanut butter at 15 months old that caused her heart to stop. Her mother Louise became an advocate for requiring schools to stock epinephrine auto-injectors (EpiPens) to treat anaphylaxis. A new law will take effect in January requiring public schools in California to have EpiPens. Louise started a Facebook group that now has over 7,000 members to raise awareness on life-threatening food allergies and advocate for policies like this new law.
Formula One delivered value to various customer groups by satisfying their wants and needs:
1) Carmakers used Formula One for innovation and testing to develop new technologies for production cars, as well as for branding and promotion.
2) TV broadcasters and media outlets gained access to a global audience, improving their businesses and diversifying their programming.
3) Sponsors received a huge global platform to promote their brands to spectators worldwide.
4) Local governments and businesses benefited from the prestige and wealth generated by hosting races.
If you are thinking about setting up a blog for business this free guide can lead you on the way to achieve the income you have always dreamed of. Or, if you already have a blog for you business, but are not quite getting the results you want, then this guide can reveal priceless information that you may be missing.
The document provides an overview of operating systems. It begins with definitions of an operating system and its roles in providing resources to users and applications and coordinating access to resources. It then discusses operating system concepts like process management, memory management, file management, I/O management, and protection systems. It outlines the evolution of operating systems from early batch systems to modern networked and distributed systems. It also discusses different operating system structures like kernel-based approaches, layered approaches, and virtual machine approaches.
Prashant Plastic Industries LLP is an Indian company that manufactures and retails industrial process equipment. Since 1980, it has produced products like blowers, chimneys, and tanks from quality materials. It offers customized equipment and after-sales support to various industries. Located in Mumbai, the company has 51-100 employees and exports to markets in Asia and the Middle East.
The document discusses several influential theorists in behaviorism: Ivan Pavlov is known for his experiments conditioning dogs to salivate to a bell using classical conditioning. B.F. Skinner conducted experiments using operant conditioning to reward behaviors in pigeons. Albert Bandura focused on social learning theory and the concept of self-efficacy. Edward Thorndike's work led to the development of operant conditioning. The document advocates using positive and negative reinforcement in teaching, as these methods motivate students.
Edge hspa and_lte_broadband_innovation_powerpoint_sept08Muhammad Ali Basra
This document summarizes the key innovations and developments in broadband wireless technologies, including EDGE, HSPA, HSPA+, and LTE. It finds that persistent innovation has significantly advanced capabilities from GPRS to current technologies that can deliver over 10 Mbps speeds. GSM/UMTS has an overwhelming global subscriber base and deployment. HSPA networks regularly achieve over 1 Mbps speeds and HSPA+ will increase this further. LTE is the most powerful wide-area wireless technology and is being adopted as the next-generation platform.
EV-DO Rev B is an evolutionary upgrade to CDMA2000 EV-DO that improves performance by allowing user traffic to flow over multiple 1.25 MHz carriers simultaneously. It provides significantly higher data rates and lower latency than EV-DO Rev A by using multi-carrier techniques. Operators can upgrade their existing EV-DO Rev A networks to Rev B with mostly software upgrades, protecting their previous investments and achieving higher performance at a fraction of the cost of alternative technologies. Rev B also maintains full backward compatibility with existing EV-DO Rev A and Release 0 devices.
The document summarizes research on using nanoparticles to improve gas sensor performance. It discusses how reducing metal oxide particles sizes to the nanoscale can dramatically increase their surface area and gas detection sensitivity, selectivity, and response time. The researcher has developed gas sensor prototypes using various metal oxide nanomaterials deposited as thick films or multilayer structures. Nanofabrication methods are also being explored to create high surface area sensor platforms using anodic aluminum oxide templates. Overall, the research aims to leverage nanotechnology to develop lower cost, higher performance gas sensors for industrial and environmental monitoring applications.
The document discusses the transition from 3G to LTE networks. It notes that data usage is growing significantly, placing pressure on networks. LTE aims to address this through a flat IP-based architecture, improved spectral efficiency from technologies like OFDMA and MIMO, and scalable bandwidth deployment. This will allow higher throughput and lower latency comparable to DSL, helping support new multimedia services and enriched user experiences with seamless connectivity at high speeds. Network operators can benefit from reduced costs per megabyte of traffic and a simpler architecture allowing flat-rate pricing plans.
The document is a 3GPP technical specification that defines the Radio Resource Control protocol for UMTS. It describes RRC functions and services, the RRC protocol architecture, state transitions and procedures. These include system information broadcasting, paging, RRC connection establishment and release, UE capability transfer, and security mode control.
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2 (Release 8)
3 gpp key performance indicators (kpi) for umts and gsm release 9Telecom Consultant
The document defines key performance indicators (KPIs) for 3G mobile networks. It provides overviews of KPIs, their purpose in evaluating network performance, and their relationship to service level agreements (SLAs) and quality indicators. Specific KPIs are then defined for various categories including accessibility, retainability, mobility, utilization and availability. Templates are also provided to standardize the information included in each KPI definition.
This document provides a technical specification for physical channels and modulation in E-UTRA, also known as LTE. It describes the frame structure, uplink transmission including physical channels like PUSCH and PUCCH, reference signals, and random access. The document also covers downlink transmission with physical channels and signals. It is a specification developed by 3GPP for the LTE wireless communication standard.
3GPP TR 22.885 study on LTE support for V2X servicesYi-Hsueh Tsai
The vehicular communication in this study, referred to as Vehicle-to-Everything (V2X), contains the following three different types:
- Vehicle to Vehicle (V2V) Communications
- Vehicle to Infrastructure (V2I) Communications
- Vehicle to Pedestrian (V2P) Communications
This document describes the Medium Access Control (MAC) protocol specifications for E-UTRA networks. It covers MAC architecture and functions, channel structures, procedures for random access, scheduling requests, data transfers, reconfiguration and reset. Protocol data units, formats and parameters are also defined. The document was developed by 3GPP for future development work within the organization to specify the MAC layer for 3G mobile networks.
This document describes the X2 application protocol (X2AP) which is used for communication between two eNodeBs in an Evolved Universal Terrestrial Radio Access Network. It defines procedures for basic mobility management, including handover preparation and UE context release, as well as global procedures like load indication and error reporting. The document also outlines the services, functions and specifications of X2AP.
This document defines Key Performance Indicators (KPIs) for measuring the performance of the Evolved Packet Core (EPC) network as specified in 3GPP TS 32.455. It includes KPI definitions for accessibility, mobility, and utilization of the EPC network. The KPIs measure things like attach success rates, handover success rates between different radio access technologies, and bearer creation success rates.
This document describes technical aspects of roaming end-to-end scenarios for Voice over LTE (VoLTE) IP Multimedia Subsystem (IMS) networks and other networks. It covers considerations for SIP header fields, identifiers, and elements. Example signaling flows are provided for registration when roaming, originating roaming calls without loopback, and originating roaming calls with loopback. The document is intended for future 3GPP specification development work.
This technical report from 3GPP provides an overview and analysis of end-to-end roaming scenarios for VoLTE calls using IMS. It describes key IMS specifications, architecture elements, procedures and signaling flows related to registration, routing, services and access transfers in roaming networks. The document aims to consolidate relevant information from 3GPP standards to aid understanding and development of roaming implementations.
This document provides 3GPP specifications for performance measurements related to the Universal Terrestrial Radio Access Network (UTRAN). It defines measurements for radio access bearer management, signaling connections, radio resource control connections, radio link control connections, soft handovers, hard handovers, and relocations. The measurements are intended to monitor performance of various procedures in the UTRAN network.
This document defines specifications for self-organizing network (SON) policy and optimization functions. It describes several SON functions including load balancing optimization, handover parameter optimization, interference control, capacity and coverage optimization, and random access channel optimization. For each function, it defines objectives, parameters to optimize, optimization methods, architecture, and performance monitoring considerations. It also covers coordination between different SON functions and between SON functions and non-SON network management operations.
This document provides an overview of 3GPP TR 25.931 which describes UTRAN functions and signaling procedures. It defines protocols and messages for communication between the UTRAN and UE, including RANAP, RNSAP, NBAP, RRC, BMC and frame protocols. The document also summarizes various procedures for paging, connection establishment and release, bearer establishment and modification, and physical channel reconfiguration. It serves as a reference for future 3GPP specification work but has not been approved and is not intended for implementation.
This document specifies standards for transport protocols and signaling protocols used to establish transport bearers over the UTRAN Iu interface. It defines the protocol stacks for both the circuit switched and packet switched domains, including the use of ATM, AAL2, IP, UDP, GTP and various signaling protocols. The document also covers areas like addressing, quality of service, and congestion control.
R3 030340(tr25.891 v030 improvement of rrm across rns and rns bss)-revadelekejare
This document provides a summary of 3GPP TR 25.891 V0.23.0 (2003-12) which proposes a Common Radio Resource Management (CRRM) functional model. The model includes Radio Resource Management (RRM) and CRRM functional entities that communicate over reference points. The CRRM entity supports RRM decisions by providing reporting information about other RRM entities and radio access networks. The document also discusses different applications of the CRRM model and potential enhancements.
This document describes the X2 application protocol (X2AP) which is used for communication between two evolved Node Bs (eNBs) in an Evolved Universal Terrestrial Radio Access Network (EUTRAN). It defines procedures for basic mobility functions like handover preparation and resource release, as well as global procedures like load indication and error reporting. The document provides specifications for the procedures to ensure forwards and backwards compatibility and proper functioning of the X2AP.
R3 031545 tr25852-v012 iu enhancements for ims support in utranadelekejare
This technical report from 3GPP discusses enhancements for supporting IP Multimedia Subsystem (IMS) in UTRAN networks. It outlines requirements such as priority for SIP signaling over user plane traffic. It also examines potential mechanisms like admission control and dynamic scheduling to meet requirements for priority and delay using an existing "signaling indication." The report serves as a living document to gather information and agree on enhancement proposals to integrate into technical specifications.
This document provides guidelines for GPRS roaming between mobile networks. It describes the standard GPRS architecture and interfaces involved in roaming, including the Gn/Gp interface between SGSNs and GGSNs. There are two roaming scenarios - one where the user's PDP context is terminated at a GGSN in their home network, and another where it is terminated at a GGSN in the visited network. The document specifies requirements for IP addressing and routing, APN configuration, and other GPRS functionality to ensure interoperability between networks for roaming users.
25952 520 base station classification (tdd)adelekejare
This technical report from 3GPP discusses the classification of base stations in 3G mobile networks. It defines scenarios like indoor and mixed indoor-outdoor environments. Propagation models are provided for path loss calculations in these scenarios. Minimum coupling loss is defined for local area base stations. Finally, the report proposes new requirements for different base station classes to account for varied use cases and radio environments compared to existing macrocell specifications.
This document is a 3GPP technical specification that outlines requirements for supporting radio resource management in UMTS FDD networks. It discusses requirements for various idle mode and connected mode mobility tasks, including cell selection, cell reselection, soft handover, hard handover, inter-RAT handover between UMTS FDD and TDD or GSM networks, and cell reselection in CELL_FACH state. It provides requirements for parameters like active set dimensions, handover delays, interruption times, and cell reselection delays. The document also lists definitions, abbreviations, references, and copyright information.
This document compares key performance metrics between LTE, WiMAX 16m, and IMT-Advanced technologies. It finds that LTE and WiMAX 16m have similar peak data rates and average data rates for downlink transmissions, but LTE has lower latency. For mobility performance, LTE and IMT-Advanced can support higher speeds compared to WiMAX 16m while maintaining spectral efficiency. Handover interruption times are also improved in LTE and IMT-Advanced.
This document discusses Motorola's approach to migrating GSM networks to LTE networks. It highlights that GSM has an immense installed base but LTE will provide higher data speeds. Motorola's solution allows operators to initially deploy GSM and later upgrade equipment to LTE, leveraging existing sites. Motorola has conducted trials of their LTE technology and ecosystem and will begin commercial releases in late 2009. Their solution aims to help operators transition networks from GSM to LTE.
The telecommunications industry faced mixed results in 2010, with traditional services becoming commoditized in developed markets while emerging markets saw continued growth. In 2011, operators will face increased competition from outside the industry, such as technology companies entering with smartphones and apps. Operators must shift to providing innovative, value-added services to retain customers. Consolidation through mergers and acquisitions will continue as operators seek growth opportunities and efficiencies to fund transforming their business models and cultures to compete successfully.
This document compares LTE and WiMax technologies and performance. It finds that LTE provides higher peak data rates beyond 150 Mbps, more spectrum efficiency, and full mobility support. However, both technologies can achieve similar performance under comparable conditions. The success of LTE or WiMax depends on each operator's strategic considerations regarding available spectrum, regulatory issues, legacy networks, and future evolution paths.
The document is a marketing report from the Broadband Forum that discusses:
1) The growing demand for mobile data and the need for service providers to adopt new technologies like LTE and Ethernet backhaul to handle this traffic growth in a more cost efficient way.
2) How MPLS can be used in mobile backhaul networks to provide Ethernet services with quality of service while allowing a gradual migration from older technologies to a pure IP packet-based network.
3) The Broadband Forum's MPLS in Mobile Backhaul Initiative which aims to define reference architectures and specifications for MPLS in mobile backhaul to help with interoperability between vendor products and reduce risks for service providers.
The document provides an overview of LTE architecture, interfaces, network elements, radio network and protocols. It describes the main LTE interfaces like Uu, S1, X2 and S5. The network elements discussed are eNB, MME, SGW and PGW. The radio network section covers physical layer technologies used in LTE like OFDMA, MIMO and QAM. It also explains transport channels, logical channels and layer 2 architecture in LTE.
This document summarizes some key features of the LTE radio interface that enable unprecedented performance in mobile broadband. It discusses features like spectrum flexibility that allow LTE to operate in different frequency bands and bandwidths with both FDD and TDD duplexing. It also describes multi-antenna transmission techniques in LTE including transmit diversity to improve coverage and capacity, and multi-stream transmission to significantly increase peak data rates through multiple parallel data streams. Scheduling, link adaptation, and hybrid ARQ are explained as ways to efficiently utilize radio resources based on varying channel conditions.
The document discusses frequency band arrangements for 3.4-3.8 GHz in various regions and countries. It summarizes band plans in Europe, Japan, Latin America, and North America based on studies and decisions from regulatory bodies. Baseline frequency arrangements are identified for further specification work on UMTS and LTE in the 3400-3600 MHz band based on the regional summaries. The document also covers deployment aspects and required changes to 3GPP specifications to support operation in the 3.4-3.8 GHz band.
IEEE began standardizing 802.16m in 2006 to develop a successor to 802.16e that could meet increasing demands for high-speed data transmission and mobility. 802.16m enhances data rates up to 1Gbps and supports mobility up to 350km/h, meeting 4G requirements. It offers backwards compatibility with 802.16e and is expected to be completed in 2010, with commercial networks beginning in 2012. 802.16m provides higher bandwidth, richer services, and lower costs to satisfy the evolving needs of mobile broadband users.
The document discusses the need for 5G networks and proposes a concept called the "NanoCore" as a potential 5G network architecture. It begins by reviewing the evolution of wireless technologies from 1G to 4G and how Moore's Law is no longer applicable. It then discusses how technologies like nanotechnology, cloud computing, and all-IP networks could be converged into a single "NanoCore" network to address future bandwidth demands beyond what 4G LTE networks can provide and overcome the limitations of Moore's Law. The proposed 5G NanoCore network would incorporate nanotechnology devices and leverage cloud computing and an all-IP infrastructure.
The document provides an overview of 4G technologies including WiMAX and LTE. It introduces Leonhard Korowajczuk who has over 40 years of experience in telecommunications and discusses CelPlan's expertise in wireless network design. The document outlines CelPlan's training courses on WiMAX, LTE, and wireless network design and discusses key aspects of deploying 4G networks, WiMAX, LTE, and their evolution over various standards releases.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Introduction of Cybersecurity with OSS at Code Europe 2024
LTE Approved Bands
1. 3GPP TR 37.801 V0.10.0 (2011-01)
Technical Report
3rd Generation Partnership Project;
Technical Specification Group Radio Access Networks;
UMTS-LTE 3500 MHz Work Item Technical Report
(Release 10)
The present document has been developed within the 3rd
Generation Partnership Project (3GPP TM
) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM
system should be obtained via the 3GPP Organizational Partners' Publications Offices.
3. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)3Release 10
Contents
Foreword.............................................................................................................................................................5
1 Scope........................................................................................................................................................6
2 References................................................................................................................................................6
3 Definitions, symbols and abbreviations ...................................................................................................7
3.1 Definitions ......................................................................................................................................................... 7
3.2 Symbols ............................................................................................................................................................. 7
3.3 Abbreviations..................................................................................................................................................... 7
4 Background ..............................................................................................................................................8
4.1 Task description................................................................................................................................................. 8
5 Frequency band arrangements..................................................................................................................9
5.1 Band status in Europe ........................................................................................................................................ 9
5.1.1 CEPT/ECC studies and decisions................................................................................................................. 9
5.1.2 European harmonised conditions for 3.4-3.8 GHz....................................................................................... 9
5.1.3 Frequency arrangements ............................................................................................................................ 10
5.1.4 Band plan in UK......................................................................................................................................... 11
5.1.5 Band plan in Germany................................................................................................................................ 11
5.1.6 Band plan in France.................................................................................................................................... 12
5.1.7 Band plan in Austria................................................................................................................................... 12
5.1.8 Summary of band arrangement in Europe.................................................................................................. 13
5.1.9 Additional frequency arrangements in the 3.4-3.6/3.6-3.8 GHz band........................................................ 15
5.2 Band status in Japan......................................................................................................................................... 16
5.2.1 Information on the future usage of 3.4-4.2GHz in Japan ........................................................................... 17
5.3 Band status in Latin America........................................................................................................................... 17
5.3.1 Mexico and Peru ........................................................................................................................................ 17
5.3.2 Argentina.................................................................................................................................................... 18
5.4 Band status in North America.......................................................................................................................... 18
5.4.1 US status .................................................................................................................................................... 18
5.4.2 Canada........................................................................................................................................................ 18
5.5 Conclusion on frequency band arrangements .................................................................................................. 19
5.5.1 Summary of regional band plans................................................................................................................ 19
5.5.2 Band plan working assumption .................................................................................................................. 20
5.5.3 Baseline frequency arrangements in 3400-3600 MHz ............................................................................... 20
6 Deployment aspects................................................................................................................................21
6.1 Deployment based on European scenarios....................................................................................................... 21
6.1.1 Possible interference scenarios from ERC/REC(04)05.............................................................................. 21
6.1.2 Assumptions for deriving requirements ..................................................................................................... 21
7 Study of UTRA requirements ................................................................................................................22
7.1 General aspects ................................................................................................................................................ 22
7.1.1 UTRA Channel raster and numbering........................................................................................................ 22
7.1.2. Spurious emissions frequency bandwidth .................................................................................................. 22
7.2 Specific UE RF requirements for UTRA......................................................................................................... 22
7.3 Specific BS RF requirements for UTRA ......................................................................................................... 22
7.4 Specific signalling requirements for UTRA .................................................................................................... 22
8 Study of E-UTRA requirements.............................................................................................................23
8.1 General aspects ................................................................................................................................................ 23
8.1.1 E-UTRA Channel raster and numbering .................................................................................................... 23
8.1.2 MSR BS operating band and categories..................................................................................................... 23
8.1.3 Spurious emissions frequency bandwidth .................................................................................................. 24
8.2 Specific UE RF requirements for E-UTRA ..................................................................................................... 24
8.3 Specific BS RF requirements for E-UTRA...................................................................................................... 24
8.3.1 Unwanted emissions................................................................................................................................... 24
8.3.2 Blocking requirements ............................................................................................................................... 25
4. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)4Release 10
8.4 Specific signalling requirements for E-UTRA................................................................................................. 27
8.4.1 Iuant interface............................................................................................................................................. 27
9 Required changes to UTRA FDD specifications ...................................................................................27
9.1 Required changes to TS 25.101 ....................................................................................................................... 27
9.2 Required changes to TS 25.104 ....................................................................................................................... 28
9.3 Required changes to TS 25.113 ....................................................................................................................... 28
9.4 Required changes to TS 25.133 ....................................................................................................................... 28
9.5 Required changes to TS 25.141 ....................................................................................................................... 28
9.6 Required changes to TS 34.124 ....................................................................................................................... 28
9.7 Required changes to TS 25.307 ....................................................................................................................... 28
9.8 Required changes to TS 25.331 ....................................................................................................................... 28
9.9 Required changes to TS 25.461 ....................................................................................................................... 28
9.10 Required changes to TS 25.466 ....................................................................................................................... 28
10 Required changes to E-UTRA specifications.........................................................................................29
10.1 Required changes to TS 36.101 ....................................................................................................................... 29
10.2 Required changes to TS 36.104 ....................................................................................................................... 30
10.3 Required changes to TS 36.141 ....................................................................................................................... 30
10.4 Required changes to TS 36.307 ....................................................................................................................... 32
10.5 Required changes to TS 36.113 ....................................................................................................................... 32
10.6 Required changes to TS 36.124 ....................................................................................................................... 32
11 Required changes to MSR specifications...............................................................................................32
11.1 Required changes to TS 37.104 ....................................................................................................................... 32
11.2 Required changes to TS 37.113 ....................................................................................................................... 33
11.3 Required changes to TS 37.141 ....................................................................................................................... 33
12 Required changes to UTRA TDD specifications ...................................................................................34
12.1 Required changes to TS 25.101 ....................................................................................................................... 34
12.2 Required changes to TS 25.102 ....................................................................................................................... 34
5.2 Frequency bands .............................................................................................................................................. 34
12.3 Required changes to TS 25.105 ....................................................................................................................... 35
5.2 Frequency bands .............................................................................................................................................. 35
12.4 Required changes to TS 25.142 ....................................................................................................................... 35
4.2 Frequency bands .............................................................................................................................................. 35
Annex A: Change history ......................................................................................................................37
5. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)5Release 10
Foreword
This Technical Report has been produced by the 3rd
Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
6. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)6Release 10
1 Scope
The present document is a technical report of the UMTS-LTE 3500 MHz work item, which was established at
TSG RAN#38. The objective of the work item is to study current band plans in the frequency bands 3.4-3.6 GHz and
3.6-3.8 GHz, where they exist, with respect to feasibility for WCDMA as well as LTE. For these current band plans,
suitable band arrangements, which are adopted by regulators, shall be identified for the purpose of developing
specifications, without excluding other future arrangements.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] RP-071012, “New Work Item Proposal: UMTS/LTE 3500”, TSG-RAN #38, Cancun, Mexico, 27-
30 November, 2007.
[3] RP-080133, “Regional 3500 MHz band arrangements and use”, Rapporteur UMTS/LTE 3500
(Ericsson), TSG-RAN meeting #39.
[4] R4-080136, "3500 MHz band status in Europe" (Ericsson).
[5] R4-080214, "Information on the future usage of the band, 3.4-4.2GHz in Japan" (ARIB).
[6] Off-line input during RAN4#46 from NII Holdings (3GPP Guest Member).
[7] “ECC Decision of 30 March 2007 on availability of frequency bands between 3400-3800 MHz for
the harmonised implementation of Broadband Wireless Access systems (BWA)”,
ECC/DEC/(07)02.
[8] “Guidelines for Accommodation and Assignment of Multipoint Fixed Wireless Systems in
Frequency Bands 3.4-3.6 GHz and 3.6-3.8 GHz”, ECC Recommendation (04)05.
[9] “Draft Report from CEPT to the European Commission in response to the Mandate to develop
least restrictive technical conditions for frequency bands addressed in the context of WAPECS”,
CEPT Report 019 (under consultation).
[10] “Report from CEPT to the European Commission in response to the Mandate to identify the
conditions relating to the provision of harmonised radio frequency bands in the European Union
for Broadband Wireless Access applications”, CEPT Report 015, 12 June 2007.
[11] R4-071342, "LTE at 3.5 GHz", Source: TeliaSonera.
[12] “Auction Terms And Conditions to Grant Concessions for the Use, Exploitation and Profit from
Frequency Bands in the Radio Electric Spectrum for The Provision of Fixed or Mobile Wireless
Access Service “, Federal Telecommunications Commission of Mexico, Sept. 3, 1997,
http://www.cft.gob.mx/cofetel/cft2/public_html/html/ina_bases_ing.html
[13] R4-081114, "Examples of regional bands for 3.5GHz" (Motorola).
[14] Office of Communications (www.ofcom.org.uk).
7. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)7Release 10
[15] BWA - Broadband Wireless Access - Präsidentenkammerentscheidung, Bundesnetzagentur für
Elektrizität, Gas, Telekommunikation, Post und Eisenbahnen (http://bwa-
versteigerung.bundesnetzagentur.de/images/Praesidentenkammerentscheidung.pdf) (in German).
[16] “Utilisation des bandes BLR “, Autorité de Régulation des Communications électroniques et des
Postes (http://www.arcep.fr/fileadmin/reprise/dossiers/blr/wimax/frqc-blr-wimax.pdf) (in French).
[17] “Übersicht spectrum 3500 MHz”, Rundfunk und Telekom Regulierungs-GmbH (RTR-GmbH)
(http://www.rtr.at/en/tk/Spektrum3500MHz) (in German).
[18] Title 47 of the Code of Federal Regulations (CFR), Part 90, Federal Communications Commission
(FCC),(http://www.access.gpo.gov/nara/cfr/waisidx_07/47cfr90_07.html).
[19] ECC PT1(08)102R2 (Annex 11), “Draft minutes (26 September 2008)”, 30th ECC PT1 meeting,
Paris, 16 -18 September 2008.
[20] CEPT/ERC/Recommendation 14-03e, “Harmonised Radio Frequency Channel Arrangements and
Block Allocations for Low and Medium Capacity Systems in The Band 3400 MHz to 3600 MHz”,
Podebrady 1997.
[21] Decision 2008/411/EC, “Commission decision of 21 May 2008 on the harmonisation of the 3 400-
3 800 MHz frequency band for terrestrial systems capable of providing electronic communications
services in the Community”.
[22] ITU-R Recommendation SM.329-10: "Unwanted emissions in the spurious domain".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [x] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [x].
Definition format
<defined term>: <definition>.
example: text used to clarify abstract rules by applying them literally.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
Symbol format
<symbol> <Explanation>
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [x] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [x].
BWA Broadband Wireless Access
CEPT European Conference of Postal and Telecommunications Administrations
ECC European Communications Committee (of CEPT)
ENG Electronic News Gathering
8. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)8Release 10
FPU Field Pickup Unit
FWA Fixed Wireless Access
FCC Federal Communications Commission
GB Guard Band
EU European Union
MWA Mobile Wireless Access
NWA Nomadic Wireless Access
OB Outside Broadcast
PMSE Programme Making and Special Events
RAT Radio Access Technology
RB Restricted Block
STL Studio to Transmitter Link
TTL Transmitter to Transmitter Link
TSL Transmitter to Studio Link
WRC World Radiocommunication Conference
4 Background
There are two new bands: 3.4-3.6 GHz and 3.6-3.8 GHz decided for Broadband Wireless Access, which are already
widely available for licensing in Europe. These bands have earlier been allocated to the Fixed Service on a primary
basis in Region 1. Furthermore, the 3.4-3.6 GHz band was allocated to the mobile service on a primary basis and
identified for IMT at WRC 07.
These bands constitute a substantial amount of spectrum that will be available in many countries in the short term. In
Europe (Region 1) both bands can be used so block sizes could be large for any duplex arrangement.
The ECC Decision (07)02 [7] not only designates the band 3.4-3.8 GHz for BWA deployment, it provides condition for
„flexible usage modes within authorised BWA deployments‟. This regulatory provision will allow licence holders to
deploy various types of terminal stations, from fixed to mobile.
4.1 Task description
The purpose of this work item is to:
- Study of UMTS/LTE 3500 for a potential deployment in Europe as well as in other regions. The current band
plans, where they exist, shall be studied with respect to feasibility for WCDMA as well as LTE and band
arrangement shall be proposed for all applicable regions.
Generate a new technical report based on study results.
- The specific bands to be studied are:
- 3.4-3.6 GHz
- 3.6-3.8 GHz
- Generate CR‟s to update the appropriate documents. All CRs will be delivered as one complete package for
UMTS and LTE.
- TSG RAN WG2 - study signalling issues related to UMTS/LTE 3500.
- The WI should introduce the UMTS/LTE 3500 in the specifications for UTRA/E-UTRA.
- Any additional related issues.
9. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)9Release 10
5 Frequency band arrangements
The description of band arrangements in this clause is based on the input in [4], [5] and [6], which is also summarized
in [3].
In Europe, a majority of countries already license the band 3.4-3.6 GHz for Fixed Wireless Access, in some countries
also for mobile use. Licensing of 3.6-3.8 GHz for Wireless Access is more limited. CEPT/ECC has generated
documentation including a spectrum decision for 3.4-3.8 GHz with “Flexible usage modes” for deployment of fixed,
nomadic and mobile networks. A European commission decision for harmonised conditions was made in May 2008
[21], making the band 3.4-3.6 GHz available from 2008 and the band 3.6-3.8 GHz from 2012. Frequency arrangements
considered in the ECC decision include FDD use with 100 MHz block offset between paired blocks and/or TDD use as
shown in Annex A. It shall be noted that ECC PT1 is working on channeling arrangements in the band 3400- 3800 MHz
for IMT and plan to finalize a draft deliverable in January 2011.
In Japan, not only 3.4-3.6GHz but also 3.6-4.2GHz will be available to terrestrial mobile service such as IMT to use
after 2010. No discussion has started yet on the detailed frequency arrangements.
In Latin America, the band 3.4-3.6 GHz was licensed in Mexico and Peru to operators that have acquired paired
frequency blocks with 100 MHz separation. Both FDD and TDD operation is allowed. The situation is similar in
Argentina, but blocks have been paired with both 50 and 100 MHz separation, see also Annex C.
5.1 Band status in Europe
The source of this information is the contributions in [4] and [13].
5.1.1 CEPT/ECC studies and decisions
The band 3.4-3.8 GHz was studied extensively by CEPT Electronic Communications Committee (ECC) in the last few
years, resulting in several reports, recommendations and decision [7,8,9,10]. The studies clearly identify the band 3400-
3600 MHz as the widest available choice for current and future BWA deployment in Europe. The band 3600-3800 MHz
is identified as a possible additional or alternative frequency band. An ERO survey indicated that a clear majority of
European countries already use the 3400-3600 MHz band for Fixed Wireless Access (FWA), while the use of the 3600-
3800 MHz band for wireless access systems was limited to a few European countries at the time of the survey (2006).
In some countries the bands are licensed also for mobile use.
The ECC Decision (07)02 [7] designates the bands 3.4-3.6 and 3.6-3.8 GHz for BWA deployment. The designation
gives considerations for “Flexible usage modes”, allowing a license holder to deploy various types of terminal stations
for Fixed, Nomadic or Mobile Wireless Access (FWA, NWA or MWA). Technical conditions for implementation of
flexible usage mode are given in ECC Recommendation (04)05 [8]. For Mobile Wireless Access, additional
requirements limit the radiated power, the TPC range and the block edge emissions.
WRC-07 identified the 3400 - 3600 MHz band for IMT in 41 European countries and 40 others in Region 1. Therefore,
the ECC has tasked ECC Project Team 1 (PT1) to develop appropriate ECC Deliverables which define band plans for
the usage of this band in the CEPT countries. The deliverables should also address the band 3600 - 3800 MHz.
According to the guidance given by the ECC, an optimised solution has to be found for the band 3400 - 3800 MHz,
which would facilitate the convergence between cellular and broadband wireless access systems already planned for the
band 3400 - 3800 MHz in some European countries.
5.1.2 European harmonised conditions for 3.4-3.8 GHz
CEPT/ECC has produced a report [10] to the European commission on BWA, concluding that the deployment of fixed,
nomadic and mobile networks is technically feasible within the frequency band 3.4-3.8 GHz. Another CEPT/ECC
report to the commission on the technical conditions for different frequency bands in the context of WAPECS1 also
addresses 3.4-3.8 GHz [9].
1 WAPECS = Wireless Access Policy for Electronic Communications Services
10. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)10Release 10
It is expected that early in 2008, there will be a European commission decision to harmonise the conditions for the
3.4-3.8 GHz band, where member states shall allow the use of the band for fixed, nomadic and mobile electronic
communication services. The decision will include technical conditions to ensure co-existence, but also allowing for
less stringent conditions to be applied if agreed between operators.
The band 3.4-3.6 GHz will be made available from 2008 and the band 3.6-3.8 GHz from 2012.
5.1.3 Frequency arrangements
The ECC decision [7] considers that within the two frequency bands, pairing of sub-bands 3400-3500/3500-3600 MHz
and 3600-3700/3700-3800 provide suitable frame conditions for FDD and TDD systems or their combination.
Two examples of frequency arrangements in line with those considerations are given in the ECC Recommendation [8].
The example arrangements contain paired blocks or combinations of paired and unpaired blocks, with a 100 MHz offset
between the paired low and high blocks. No specific consideration has been made for the necessary duplex gap. The
ECC example arrangements are shown in Figure 5.1.3-1 and 5.1.3-2 below and are also discussed in [11].
Figure 5.1.3-1 Example scheme with paired equal blocks in the 3.4-3.6 and 3.6-3.8 GHz bands (from
[8])
11. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)11Release 10
Figure 5.1.3-2 Example scheme with paired and unpaired blocks in the 3.4-3.6 and 3.6-3.8 GHz bands
(from [8])
In the subclauses below, several regional band plans for the band 3400 to 3600 MHz in Europe are presented, which
were collected from the various available documents published by European administrations.
5.1.4 Band plan in UK
In the UK the 3400 to 3600 MHz band plan pretty much follows ECC REC (04)05 [8]. Spectrum is typically assigned
in blocks of 20 MHz. Most of the spectrum is assigned for PMSE ENG/OB applications. In this band also two blocks
with a duplex distance of 100 MHz are assigned to broadband wireless applications.
Figure 5.1.4-1: UK band plan for 3400 to 3600 MHz (source: [14])
5.1.5 Band plan in Germany
In Germany the 3400 to 3600 MHz band was auctioned in December 2006 for broadband wireless access (BWA)
systems. Figure 5.1.5-1 shows the band plan, which was used for the auction. The band plan is based on a 7 MHz raster
with altogether 8 blocks. Two blocks with a duplex distance of 100 MHz are grouped to one package:
- Package A: 3410-3431 & 3510-3531 MHz
- Package B: 3431-3452 & 3531-3552 MHz
- Package C: 3452-3473 & 3552-3573 MHz
12. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)12Release 10
- Package D: 3473-3494 & 3573-3594 MHz
3400 MHz 3500 MHz 3600 MHz
3410 3494 3510 3594
A B A B C DC D
Figure 5.1.5-1: Band plan Germany (source: [15])
From the band plan it can be seen that no external guard band between the blocks is provided. The assignment of blocks
is assumed under the provision of ECC REC(04)05 [8], which defines an internal guard of half the system channel
bandwidth at the block edge. At the 3400 MHz boarder the first block starts at 3410 MHz with a guard band of 10 MHz
to protect services below 3400 MHz.
5.1.6 Band plan in France
Also France is following in principle a similar approach like Germany. For BWA three packets with two blocks each of
15 MHz in the 3.5 GHz band are defined. Figure 5.1.6-1 shows the arrangement for BWA blocks.
3400 MHz 3500 MHz
3432.5 3495
A B C A B C
3600 MHz
3532.5 35953465 3565
35803480
0
3447.5
0
3547.5
0
Figure 5.1.6-1: Band plan France (source: [16])
The 3 packages (2x 15 MHz) have a duplex distance of 100 MHz with the following arrangement:
- Package A: 3432.5-3447.7 & 3532.5-3547.7 MHz
- Package B: 3465-3480 & 3565-3580 MHz
- Package C: 3480-3495 & 3580-3595 MHz
5.1.7 Band plan in Austria
As a further example of a European band plan, the band plan from Austria is shown in Figure 5.1.7-1. In Austria two
possible band plan arrangements are available depending on the region. Like other countries (e.g. Germany or France)
the 3.5 GHz licenses are divided in different geographical regions, however typically using the same band plan
arrangement. Austria is divided in six regions with the option that in each region either arrangement A, B and C or the
13. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)13Release 10
blocks D and E can be used. At the moment the arrangement D and E is only used in one small rural region. In all the
other regions the block arrangement A, B and C is used.
Between the blocks an external guard band of 7 MHz is established and the first block starts at 3410 MHz with a 10
MHz guard band to protect applications below 3400 MHz. All blocks are based on a 7 MHz raster and two blocks are
grouped to a package with a duplex distance of 100 MHz:
Block arrangement 1:
- Package A (2x 21 MHz): 3410-3431 & 3510-3531 MHz
- Package B (2x 28 MHz): 3438-3466 & 3538-3566 MHz
- Package C (2x 21 MHz): 3473-3494 & 3573-3594 MHz
Block arrangement 2:
- Package D (2x 35 MHz): 3410-3445 & 3510-3545 MHz
- Package E (2x 42 MHz): 3452-3494 & 3552-3594 MHz
Figure 5.1.7-1: Band plan Austria (source: [17])
5.1.8 Summary of band arrangement in Europe
At the recent ECC PT1 meeting, a report was put together based on an “ERO questionnaire on the use of 3400-
3600 MHz and 3600 - 3800 MHz bands” [19]. It is based on the replies from 32 European countries, including the four
countries presently documented in the present document. The detail of information reported differs from country to
country, but for at least sixteen countries there is detailed information of existing band arrangements, channelization
and duplex in the band 3400-3600 MHz. That information is summarized below in Table 5.1.8-1 and also illustrated in
Figure 5.1.8-1.
14. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)14Release 10
Table 5.1.8-1 Summary of the survey in [19] for 16 European countries.
Country Uplink
frequency range
[MHz]
Downlink
Frequency range
[MHz]
Duplex
arrangement
Duplex
separation
for FDD
Block sizes
[MHz]
Austria 3410 3494 3510 3594 FDD, TDD 100 MHz 21, 28, 35, 42
Belgium 3450 3500 3550 3600 FDD, TDD 100 MHz 25
Bosnia & Herzegovina 3410 3494 3510 3594 FDD 100 MHz 21
Czech Republic 3410 3480 3510 3580 FDD, TDD 100 MHz 3.5 (raster)
France 3432.5 3495 3532.5 3595 FDD, TDD 100 MHz 15
Germany 3410 3494 3510 3594 FDD, TDD 100 MHz 21
Hungary 3410 3494 3510 3594 FDD, TDD 100 MHz 14
Ireland 3410 3500 3510 3600 FDD, TDD 100 MHz 11, 25, 35
Italy 3425 3500 3525 3600 FDD, TDD 100 MHz 21
Macedonia (FYROM) 3410 3494 3510 3594 FDD, TDD 100 MHz 31.5, 14
Norway 3413.5 3500 3513.5 3600 FDD, TDD 100 MHz 3.5 (raster)
Portugal 3410 3438 3510 3538 FDD, TDD 100 MHz 28
Russian Federation 3400 3450 3500 3550 FDD, TDD 100 MHz
Sweden 3410 3494 3510 3594 FDD, TDD 100 MHz 28
Switzerland 3410 3497.5 3510 3597.5 FDD, TDD 100 MHz 17.5, 21, 28
United Kingdom 3480 3500 3580 3600 FDD, TDD 100 MHz 20
Several observations can be made when analyzing the survey results summarized above:
- Blocks with FDD arrangements are possible in all listed countries and TDD arrangements in all but two.
- For FDD arrangements, the duplex separation is consistently 100 MHz.
- Block sizes are large, in general ≥14 MHz.
- While there are some variations in the frequency ranges, only one country has frequency blocks below 3410
MHz. For many countries, the frequency range 3400-3410 MHz is designated as a “guard band”.
- Most countries have frequency ranges ending at 3494 (and 3594) MHz, while a few have the whole range up to
3600 MHz designated.
Several countries reference give reference to ERC Recommendation 14-03E Annex B [20], where harmonised 100
MHz arrangements for these bands are given. The arrangements in [20] are for channel spacing of 1.75, 3.5, 7 and 14
MHz, but can easily be extended to multiples of those numbers, such as 21, 28, 35 and 42 MHz. The recommendation
[20] also gives channel raster for the arrangements. For any channel spacing ≥7 MHz, the edge of the uppermost
channel will be at 3494 MHz. This is also reflected in the frequency ranges for the arrangements in these countries in
Table 5.8.1-1.
The conclusion from the ERO survey is that an FDD arrangement where 3410-3500 MHz is paired with 3510-
3600 MHz covers a substantial part of the existing band arrangements in Europe.
15. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)15Release 10
28
50
70
84
84
84
84
84
84
62.5
87.5
86.5
75
50
90
20
28
50
70
84
84
84
84
84
84
62.5
87.5
86.5
75
50
90
20
3400 3500 3600
Portugal
Russian Federation
Czech Republic
Austria
Bosnia & Herzegovina
Macedonia
Germany
Hungary
Sweden
France
Switzerland
Norway
Italy
Belguim
Ireland
UK
Uplink Downlink
Figure 5.1.8-1 Illustration of the band arrangements in 16 European countries (from [19]).
5.1.9 Additional frequency arrangements in the 3.4-3.6/3.6-3.8 GHz band
The recently approved EC Decision 2008/411/EC for the identification of the band 3.4-3.8 GHz for BWA applications
[7] supports the introduction of Mobility in the band 3.4-3.6 GHz and 3.6-3.8 GHz. This introduction should be made
according to some technical constraints reported in Annex to the Decision; these constraints were identified by CEPT
after careful study of the consequences of the extension to Mobility of the usages in this band.
It should be noted that technical conditions in the Annex of the EC Decision have been defined on the basis of full
neutrality with no hypothesis of TDD of FDD usage of any block; as a consequence the technical conditions at edge
blocks are very stringent. In case neighbour operators both use FDD or synchronized TDD networks, these technical
conditions could be considerably relaxed.
Because of this technology neutrality, a plurality of allocation scenarios can be met. These scenarios include:
● Operation of TDD and FDD in adjacent frequency allocations
● Operation of different or same RAT in adjacent spectrum blocks allocations
There are numerous cases where a part of the spectrum will be occupied by another RAT, before LTE is deployed. It is
important to offer dual operation, or smooth migration to LTE perspectives.
The 3 following generic scenarios are described and commented in this contribution. Note that these
scenarios are compatible with the ECC recommendation (04)05
[8]
FDD-UL FDD-UL TDD UL-DL FDD DL FDD DL TDD UL-DL
Operator A Operator B Operator C Operator A Operator B Operator CGB
3400-3600 or 3600-3800 MHz
GBGB/
RB
16. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)16Release 10
Figure 5.1.9-1: Scenario A1 FDD and TDD in adjacent blocks
FDD-UL TDD UL-DL FDD DL TDD UL-DL
Operator A Operator B Operator A Operator CGB
3400-3600 or 3600-3800 MHz
GB/
RB
GB
Figure 5.1.9-2: Scenario A2 FDD and TDD in adjacent blocks, variant of A1
Operator A Operator B Operator CGB/
RB
TDD UL-DLTDD UL-DL TDD UL-DL
3400-3600 or 3600-3800 MHz
Figure 5.1.9-3: Scenario A3 TDD only scenario
GB refers to guard bands which may be necessary between TDD and FDD blocks, and possibly between TDD blocks
when they are not synchronized, and frames properly configured.
RB refers to Restricted Blocks. RB can be allowed provided that the risk of adjacent channel interference is not
increased.
Comments on scenarios:
Scenario A1: FDD and TDD operation in adjacent blocks
As a consequence of their support to neutrality, CEPT and EC allow the implementation of TDD solutions in
paired blocks.
Scenario A2: FDD and TDD operation in adjacent blocks (variant)
As a further improvement for the implementation of TDD, two TDD Operators assigned with adjacent paired
blocks are allowed to swap their spectrum to create larger unpaired blocks.
Scenario A3: TDD only operation in adjacent blocks
Note that guard bands may or may not be required depending on frame and switching points alignments. Figure
5.1.9.3 assumes that Operator A operator B are synchronized, while operators B and C are not synchronized.
5.2 Band status in Japan
The source of this information is the contribution in [5] and [13].
17. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)17Release 10
5.2.1 Information on the future usage of 3.4-4.2GHz in Japan
In Japan, not only 3.4-3.6GHz but also 3.6-4.2GHz will be available to terrestrial mobile service such as IMT to use
after 2010. No discussion has started yet on the frequency arrangement (i.e. the band or part(s) of the band should be
TDD, FDD uplink or FDD downlink) in the band.
In addition, 4.4-4.9 GHz will also be available to terrestrial mobile service such as IMT to use after 2010.
Figure 5.2.1-1 shows the spectrum allocation plan from the Ministry Internal affairs and Communication in Japan.
Voice FPU
Will move to
other band
Voice STL/TTL/TSL
Will move to other bands.
The schedule will be fixed by
March, 2008.
Coexisting study for 4G and Satellite
Communication systems by 2010.
Video STL/TTL/TSL
Will move to other bands.
Current schedule is to complete
the relocation by November, 2012.
4GHz band fixed wireless system
Complete the relocation by November, 2012.
Aero radio
navigation
Figure 5.2.1-1: Japan Spectrum allocation action plan for 3.4 to 4.4 GHz.
5.3 Band status in Latin America
The source of this information is the contribution in [6].
Several countries in Latin America (Region 2) have auctioned spectrum in the 3.4-3.6 GHz band. Many of these bands
are currently being used for broadband wireless services. This paper gives some background information on the
allocation of spectrum in the 3.4-3.6 GHz band in three countries in Latin America: Mexico, Peru and Argentina.
5.3.1 Mexico and Peru
In Mexico and Peru, the spectrum from 3.4-3.6 GHz was divided into 8 blocks of 25 MHz each. The blocks were
auctioned off individually, but acquired in pairs by operators. The result was 4 paired bands with 100 MHz offset
between the low and high band. Operation in both FDD and TDD mode is permitted in each of these bands.
Figure 5.3-1 Band arrangement in Mexico and Peru
18. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)18Release 10
5.3.2 Argentina
Argentina also auctioned spectrum between 3.4 and 3.6 GHz. The blocks in Argentina were also auctioned off
individually, and acquired in paired by the operators. Some of the blocks, as paired by the licensees, have 100 MHz of
separation and some have 50 MHz of separation. Operation in both FDD and TDD mode are permitted in these bands.
5.4 Band status in North America
The source of this information is the contribution in [13].
5.4.1 US status
In the US in the 3.5 GHz band only 50 MHz of spectrum from 3650 to 3700 MHz are available for terrestrial mobile
applications. The band 3500 to 3650 MHz is used by the federal government for high power radars and above 3.7 GHz
the band is used for broadcasting.
Frequency (MHz)
3500 3650 3700 4200
Federal
Government
High power radar (Navy)
Countermeasures
Cable TV feed
Satellite Control
Figure 5.4.1-1: US band plan for 3.5 to 4.2 GHz
For the available 50 MHz the following FCC rules apply [18]:
- Nationwide non-exclusive licensees for entire 50 MHz
- Registration required for individual fixed stations operating under nationwide license
- 10 year license
- Equipment employing unrestricted contention-based protocol (i.e. one capable of avoiding co-frequency
interference with devices using all other types of contention-based protocols) may operate throughout the entire
50 MHz.
- Equipment incorporating a restricted contention-based protocol (i.e. one that does not qualify as unrestricted)
may only operate in the lower 25 MHz.
- Governed under Part 90 of the FCC‟s rules [18].
5.4.2 Canada
Figure 5.4.2-1 shows the Canadian band plan for the band 3400 MHz to 3650 MHz. Spectrum is assigned in blocks of
25 MHz continuously. The band is limited to fixed wireless access systems and in 3400 to 3450 MHz grandfathered
operations are deployed. Canada considers extending the band plan to include FCC 3650 to 3700 MHz to harmonize
with the US.
19. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)19Release 10
Frequency (MHz)
3400 3425 3450 3475 3500 3525 3550 3575 3600 3625 3650 3675 3700
A B C D E F G H J K
Core Bands
Figure 5.4.2-1: Band plan for Canada for 3400 MHz to 3700 MHz
5.5 Conclusion on frequency band arrangements
5.5.1 Summary of regional band plans
The frequency band arrangements were studied and reported above for the following regions:
● Europe: The harmonised conditions determined by ECC and in the EU decision for BWA use in the bands are
summarized in subclause 5.1. In addition, the local band plans applied in UK, Germany, France and Austria for
the band 3.4-3.6 GHz is documented.
● Japan: The present use of the band 3.4-4.2 GHz is reported in subclause 5.2. The band will be made available
for terrestrial mobile services such as IMT, but there is currently no band plan.
● Latin America: The situation in Mexico, Peru and Argentina is documented in subclause 5.3. Many of the
bands are used for BWA services.
● North America: The situation in US and Canada is documented in subclause 5.4. While Canada has band plans
for FWA in 150 MHz of spectrum, only 50 MHz is available for terrestrial mobile services in the US.
Some observations can be made of the studies above. Looking first at Europe, it can be noted that all countries studied
except UK have paired band plans in use today that are aligned with the ECC decision [7] and the band plans given in
the ECC recommendation [8]. The ECC plan is based on pairing of the bands 3.4-3.6 GHz and 3.6-3.8 GHz as shown in
Figure 5.5-1, with use of the spectrum for either FDD or TDD. For FDD, the uplink-downlink duplex frequency
separation is 100 MHz. There is no given duplex band gap for the FDD arrangement in this proposal. There is a need to
find solution for this further during the work by e.g. half-duplex operation or flexible arrangements on national basis.
3400 3500
38003600 3700
3400 38003600
FDD FDD
TDD TDD
Figure 5.5.1-1FDD and TDD band plan in 3.4-3.6 GHz and 3.6-3.8 GHz.
For Latin America, it can be noted that the plans for Mexico and Peru are very similar to the European allocations. They
have a 100 MHz uplink-downlink separation and fit within the plan in Figure 5.5-1. Some blocks in Argentina also have
100 MHz uplink-downlink spacing, while others have 50 MHz.
The North American plans differ from the European and Latin American, especially for the US. Still, there is a
possibility in Canada for 2x50 MHz of paired spectrum or up to 150 MHz of unpaired spectrum, all aligned with the
plan in Figure 5.5-1.
20. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)20Release 10
5.5.2 Band plan working assumption
The studies performed above shows that the band plan in Figure 5.5.1-1 has good support throughout Europe and also in
some other parts of the world where a band plan compatible with the arrangement in Figure 5.1.3-1 and/or Figure 5.1.3-
2 is assumed. The plan calls for the bands to be paired with 100 MHz uplink-downlink duplex frequency separation of
100 MHz. Alternatively, any of the bands can be used as unpaired.
A framework frequency arrangement based on the studies would then be as follows (see also Figure 5.5-1):
3.4-3-6 GHz band:
● FDD Uplink 3400-3500 MHz
● FDD Downlink 3500-3600 MHz
● or TDD Unpaired 3400-3600 MHz
3.6-3-8 GHz band:
● FDD Uplink 3600-3700 MHz
● FDD Downlink 3700-3800 MHz
● or TDD Unpaired 3600-3800 MHz
Continued studies of deployment aspects and specific RF and signaling requirements would use this framework
frequency arrangement above as a working assumption.
The framework frequency arrangement as described above is to be applied for the UMTS/LTE 3500 work.
5.5.3 Baseline frequency arrangements in 3400-3600 MHz
The conclusion from the ERO survey documented in subclause 5.1.8 is that an FDD arrangement where 3410-
3500 MHz is paired with 3510-3600 MHz covers a substantial part of the existing band arrangements in Europe. This is
taken as the baseline FDD pairing to use for further work on the band 3400-3600 MHz, as shown in Figure 5.5.3-1.
From an implementation point of view, it will be difficult to implement a complete 2x90 MHz arrangement with a
single duplexer in a UE. A more reasonable single duplexer band arrangement may be on the order of 2x70 MHz, but
such an arrangement would cover a much smaller portion of the existing band arrangements (see Figure 5.1.8-1).
NOTE: The performance impact and implementation considerations and of a 2x90 MHz duplex arrangement will
need further study.
A TDD arrangement should be studied for the whole frequency range 3400-3600 MHz.
f [MHz]
3410 3500 3510 3600
Duplex band gap (10 MHz)
Uplink (90 MHz) Downlink (90 MHz)
Figure 5.5.3-1 Baseline FDD pairing arrangement for 3400-3600 MHz.
21. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)21Release 10
6 Deployment aspects
6.1 Deployment based on European scenarios
6.1.1 Possible interference scenarios from ERC/REC(04)05
The band arrangement presented in clause 5.5 is mainly based on European conditions, as expressed in a recent EU
decision [21] and ECC/REC(04)05[3]. The ECC recommendation considers both paired arrangements for FDD and
unpaired for TDD. Potentially, an implementation of the recommendation in [3] may be mix of FDD/TDD and/or
unsynchronized TDD.
Band plans that mix FDD and TDD within one or both bands shall be avoided to prevent difficult interference scenarios
and inefficient spectrum use, for the following reasons:
- Mix of FDD and TDD in the same geographical area gives adjacent up and downlink transmissions, which may
result in unreasonable terminal requirements to avoid mobile-to-mobile interference.
- The mix of FDD and TDD in the same geographical area results in spectrum inefficiency due to the need for
large guard bands. Especially, when considering large bandwidths of 20 MHz and above for LTE-Advanced, it is
important to avoid spectrum fragmentation and not waste spectrum for large guard bands
- LTE needs large channel bandwidths and use of multiple antennas to achieve the high data throughput
requirements for IMT systems. Mixing TDD/FDD is a major technical challenge for mobile terminal equipment
requiring multiple duplexers for each antenna.
- For LTE Advanced carrier aggregation, 3GPP is currently not studying a mixture of FDD and TDD operation.
The aim must be to avoid multiple interference scenarios in band plans, in order not to create difficulties in deriving a
common equipment standard. If such an interference scenario were to occur in a country where UMTS/LTE 3500 MHz
is to be deployed, the primary solution should be deployment and site solutions tailored to that specific situation.
6.1.2 Assumptions for deriving requirements
Based on the conclusions in subclause 6.1.2, the following taken as a working assumption for deriving RF requirements
for deployment based on European scenarios:
- Any deployment is based on ECC/REC(04)05 [8], but local variations and additional restrictions may exist that
vary between countries and regions.
- It is assumed that FDD and TDD are not deployed in the same frequency range, i.e. 3400-3600 MHz and 3600-
3800 MHz respectively are either deployed with TDD only or FDD only.
- For TDD deployment in a band, it is assumed that systems are synchronized.
- Other services in the band, mix of FDD/TDD and/or unsynchronized TDD will not be reflected through specific
RF requirements.
Based on these assumptions, there will be no new interference scenarios specific to the bands 3400-3600 MHz and
3600-3800 MHz, making it possible to re-use RF requirements from other bands.
22. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)22Release 10
7 Study of UTRA requirements
7.1 General aspects
7.1.1 UTRA Channel raster and numbering
It was shown in Table 5.1.8-1 that the frequency allocations in 3.4-3.6 GHz throughout Europe are made in blocks of
from 2x11 up to 2x42 MHz. Block sizes are generally large, so there does not seem to be a need to have any UARFCN
in addition to the default 200 kHz raster.
For the band 3400-3600 MHz, a 2x90 MHz FDD duplex arrangement was concluded in Subclause 5.5.3 and illustrated
in Figure 5.5.3-1:
- FDD Uplink 3410-3500 MHz
- FDD Downlink 3510-3600 MHz
This band allocation is for UTRA referred to as Band [XXII].
UARFCN can be defined as in Table 7.1.1-1, by reserving a part of the unused numbers that follow the Band XX
allocation.
Table 7.1.1-1: UARFCN allocated for UTRA FDD Band [XXII]
Uplink UARFCN Downlink UARFCN
UTRA
FDD
Band
Band
range
[MHz]
Range
res.
[MHz]
Formula
offset
FUL_Offset
[MHz]
Assigned/
Reserved
NU
FUL
[MHz]
Formula
offset
FDL_Offset
[MHz]
Assigned/
Reserved
ND
FDL
[MHz]
[XXII] [90] [90] [2525] Start res. [4425] 3410.0 [2580] Start res. [4650] [3510.0]
Min. [4437] [3412.
4]
Min. [4662] [3512.4]
Max. [4863] [3497.
6]
Max. [5088] [3597.6]
Stop res. [4874] [3499.
8]
Stop res. [5099] [3599.8]
7.1.2. Spurious emissions frequency bandwidth
In order to cover spurious emissions up to the 5th
harmonic, as recommended in ITU-R SM.329 [1], s2.5 table 1 [22],
the upper frequency limit for “Transmitter spurious emissions” and “Receiver spurious emissions” in TS 25.101, TS
25,104 and TS 25.141 needs to be extended from 12.75 GHz to 19 GHz for Band [42] and Band [43]
7.2 Specific UE RF requirements for UTRA
<Text to be added>
7.3 Specific BS RF requirements for UTRA
<Text to be added>
7.4 Specific signalling requirements for UTRA
<Text to be added>
23. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)23Release 10
8 Study of E-UTRA requirements
8.1 General aspects
8.1.1 E-UTRA Channel raster and numbering
It was shown in Table 5.1.8-1 that the frequency allocations in 3.4-3.6 GHz throughout Europe are made in blocks of
from 2x11 up to 2x42 MHz. E-UTRA is based on channel bandwidths from 1.4 to 20 MHz and a 100 kHz raster that
supports carrier deployment anywhere within those block sizes.
For the band 3400-3600 MHz, a 2x90 MHz FDD duplex arrangement was concluded in Subclause 5.5.3 and illustrated
in Figure 5.5.3-1:
- FDD Uplink 3410-3500 MHz
- FDD Downlink 3510-3600 MHz
This band allocation is for E-UTRA referred to as Band [22].
E-UARFCN can be defined as in Table 8.1.1-1, by reserving a part of the unused numbers that follow the band [21]
allocation.
Table 8.1.1-1 EARFCN allocated for E-UTRA Band [22]
E-UTRA
Operating
Band
Downlink Uplink
FDL_low [MHz] NOffs-DL Range of NDL FUL_low [MHz] NOffs-UL Range of NUL
[22] 3510 6600 6600 – 7499 3410 24600 24600 – 25499
It was concluded in Subclause 5.5.3 that TDD can be deployed in 3400-3600 MHz. Using the complete frequency range
available in 3400-3600 MHz would cover all possible arrangements. As indicated in subclause 5.5.2, the band 3600-
3800 MHz can also be used for unpaired arrangement, in line with ECC recommendation (04)05 [8].
Two unpaired arrangements for TDD are therefore defined for E-UTRA TDD:
- 3400-3600 MHz
- 3600-3800 MHz
The band allocations are for E-UTRA referred to as Band [42] and [43] respectively.
E-UARFCN can be defined as in Table 8.1.1-2, by reserving a part of the unused numbers that follow the band 41
allocation.
Table 8.1.1-2 EARFCN allocated for E-UTRA Band [42] and [43]
E-UTRA
Operating
Band
Downlink Uplink
FDL_low [MHz] NOffs-DL Range of NDL FUL_low [MHz] NOffs-UL Range of NUL
[42] 41590 41590 –
43589
41590 3400 41590 41590 – 43589
[43] 43590 43590 –
45589
43590 3600 43590 43590 – 45589
8.1.2 MSR BS operating band and categories
The tables identifying the band designations of unpaired bands in TS 37.104 and TS 37.141 will require alteration to
accommodate the new LTE3500 frequency band parameters, as follows.
24. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)24Release 10
Table 8.1.2-1: Unpaired bands in E-UTRA and UTRA.
MSR and
E-UTRA
Band
number
UTRA
Band
number
Uplink (UL) BS receive
UE transmit Downlink (DL) BS transmit
UE receive
Band
category
[42] [h)] 3400 MHz – 3600 MHz 3400 MHz – 3600 MHz 3
[43] [i)] 3600 MHz – 3800 MHz 3600 MHz – 3800 MHz 3
8.1.3 Spurious emissions frequency bandwidth
“Transmitter spurious emissions” and “Receiver spurious emissions” in TS 36.101, TS 36,104, TS 36.141, TS 37.104
and TS 37.141 need to extend the frequency range from 12.75 GHz to 19 GHz for Band [42] and Band [43] to cover
spurious emissions from those bands up to the 5th
harmonic, as recommended in ITU-R SM.329 [1], s2.5 table 1 [22].
8.2 Specific UE RF requirements for E-UTRA
<Text to be added>
8.3 Specific BS RF requirements for E-UTRA
8.3.1 Unwanted emissions
For the “Operating band unwanted emissions” in TS 36.104 and TS 36.141, the existing tables of requirements are
applicable to warrant addition of Bands [42] (3400-3600 MHz) and [43] (3600-3800 MHz).
The “Transmitter spurious emissions” in TS 36.104 and TS 36.141 require alteration to accommodate the LTE3500
frequency bands for TDD, as follows. Also, the tables on minimum co-location emissions requirements similarly
require alteration. Limits are the same as in other bands.
Table 8.3.1-1: BS Spurious emissions limits for E-UTRA BS for co-existence with systems operating
in other frequency bands
System type
for E-UTRA to
co-exist with
Frequency range
for co-existence
requirement
Maximu
m Level
Measurement
Bandwidth
Note
E-UTRA Band
[42]
3400 - 3600MHz -52 dBm 1 MHz This is not applicable to E-UTRA BS operating in Band
[42]
E-UTRA Band
[43]
3600 - 3800MHz -52 dBm 1 MHz This is not applicable to E-UTRA BS operating in Band
[43]
Table 8.3.1-2: Home BS Spurious emissions limits for co-existence with Home BS operating in other
frequency bands
Type of coexistence BS Frequency range
for co-location
requirement
Maximum
Level
Measurement
Bandwidth
Note
E-UTRA Band [42] 3400 - 3600MHz -71 dBm 100 kHz This is not applicable to Home BS
operating in Band [42]
E-UTRA Band [43] 3600 - 3800MHz -71 dBm 100 kHz This is not applicable to Home BS
operating in Band [43]
25. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)25Release 10
8.3.1-3: BS Spurious emissions limits for Wide Area BS co-located with another BS
Type of co-located BS Frequency range for co-
location requirement
Maximum
Level
Measurement
Bandwidth
Note
WA E-UTRA Band [42] 3400 - 3600MHz -96 dBm 100 kHz This is not
applicable to E-
UTRA BS operating
in Band [42]
WA E-UTRA Band [43] 3600 - 3800MHz -96 dBm 100 kHz This is not
applicable to E-
UTRA BS operating
in Band [43]
Table 8.3.1-4: BS Spurious emissions limits for Local Area BS co-located with another BS
Type of co-located BS Frequency range for co-
location requirement
Maximum
Level
Measurement
Bandwidth
Note
LA E-UTRA Band [42] 3400 - 3600MHz -88 dBm 100 kHz This is not
applicable to E-
UTRA BS operating
in Band [42]
LA E-UTRA Band [43] 3600 - 3800MHz -88 dBm 100 kHz This is not
applicable to E-
UTRA BS operating
in Band [43]
8.3.2 Blocking requirements
The blocking performance requirements in TS 36.104 and 36.141 require alteration to accommodate the LTE3500
frequency bands for TDD, as follows.
Table 8.3.2-1: Blocking performance requirement for Wide Area BS
Operating
Band
Centre Frequency of Interfering
Signal [MHz]
Interfering
Signal
mean power
[dBm]
Wanted Signal
mean power
[dBm]
Interfering signal
centre frequency
minimum
frequency offset
from the
channel edge of
the wanted
signal [MHz]
Type of
Interfering
Signal
[42], [43] (FUL_low -20) to (FUL_high +20) -43 PREFSENS +6dB* See table 7.6.1.1-
2
See table
7.6.1.1-2
1
(FUL_high +20)
to
to
(FUL_low -20)
12750
-15 PREFSENS +6dB* CW carrier
Note*: PREFSENS depends on the channel bandwidth as specified in TS 36.104 Table 7.2.1-1.
26. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)26Release 10
Table 8.3.2-2: Blocking performance requirement for Local Area BS
Operating
Band
Centre Frequency of Interfering
Signal [MHz]
Interfering
Signal
mean power
[dBm]
Wanted Signal
mean power
[dBm]
Interfering signal
centre frequency
minimum
frequency offset
from the
channel edge of
the wanted
signal [MHz]
Type of
Interfering
Signal
[42], [43] (FUL_low -20) to (FUL_high +20) -35 PREFSENS +6dB* See table 7.6.1.1-
2
See table
7.6.1.1-2
1
(FUL_high +20)
to
to
(FUL_low -20)
12750
-15 PREFSENS +6dB* CW carrier
Note*: PREFSENS depends on the channel bandwidth as specified in TS 36.104 Table 7.2.1-2.
Table 8.3.2-3: Blocking performance requirement for Home BS
Operating
Band
Centre Frequency of Interfering
Signal [MHz]
Interfering
Signal
mean power
[dBm]
Wanted Signal
mean power
[dBm]
Interfering signal
centre frequency
minimum
frequency offset
from the
channel edge of
the wanted
signal [MHz]
Type of
Interfering
Signal
[42], [43] (FUL_low -20) to (FUL_high +20) -27 PREFSENS +14dB* See table 7.6.1.1-
2
See table
7.6.1.1-2
1
(FUL_high +20)
to
to
(FUL_low -20)
12750
-15 PREFSENS +14dB* CW carrier
Note*: PREFSENS depends on the channel bandwidth as specified in TS 36.104 Table 7.2.1-3.
The co-location blocking performance requirements in TS 36.104 and TS 36.141require alteration to accommodate the
LTE3500 frequency bands for TDD, as follows.
Table 8.3.2-4: Blocking performance requirement for E-UTRA Wide Area BS when co-located with BS
in other frequency bands.
Co-located BS type Centre
Frequency of
Interfering
Signal (MHz)
Interfering
Signal mean
power
(dBm)
Wanted Signal
mean power (dBm)
Type of
Interfering
Signal
WA E-UTRA in Band [42] 3400 – 3600 +16 PREFSENS + 6dB* CW carrier
WA E-UTRA in Band [43] 3600 – 3800 +16 PREFSENS + 6dB* CW carrier
Note*: PREFSENS depends on the channel bandwidth as specified in TS 36.104 Table 7.2.1-1.
NOTE 1: Except for a BS operating in Band 13, these requirements do not apply when the
interfering signal falls within the uplink operating band or in the 10 MHz immediately
outside the uplink operating band.
For a BS operating in band 13 the requirements do not apply when the interfering signal
falls within the frequency range 768-797 MHz.
NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements
above. The current state-of-the-art technology does not allow a single generic solution for
co-location of UTRA TDD or E-UTRA TDD with E-UTRA FDD on adjacent frequencies for
30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions
that can be used. These techniques are addressed in TR 25.942.
27. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)27Release 10
Table 8.3.2-5: Blocking performance requirement for Local Area BS when co-located with BS in other
frequency bands.
Co-located BS type Centre
Frequency of
Interfering
Signal (MHz)
Interfering
Signal mean
power
(dBm)
Wanted Signal
mean power (dBm)
Type of
Interfering
Signal
LA E-UTRA in Band [42] 3400 – 3600 -6 PREFSENS + 6dB* CW carrier
LA E-UTRA in Band [43] 3600 – 3800 -6 PREFSENS + 6dB* CW carrier
Note*: PREFSENS depends on the channel bandwidth as specified in TS 36.104 Table 7.2.1-2.
NOTE 1: Except for a BS operating in Band 13, these requirements do not apply when the
interfering signal falls within the uplink operating band or in the 10 MHz immediately
outside the uplink operating band.
For a BS operating in band 13 the requirements do not apply when the interfering signal
falls within the frequency range 768-797 MHz.
NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements
above. The current state-of-the-art technology does not allow a single generic solution for
co-location of UTRA TDD or E-UTRA TDD with E-UTRA FDD on adjacent frequencies for
30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions
that can be used. These techniques are addressed in TR 25.942.
8.4 Specific signalling requirements for E-UTRA
8.4.1 Iuant interface
The list of frequency bands in TS 35.461 is updated according to Table 8.4.1-1. The coding for the bands is updated in
TS 25.466 according to Table 8.4.1-2. The following is noted:
- UTRA Band [h] and E-UTRA Band [42] have identical frequency ranges.
- UTRA Band [i] and E-UTRA Band [43] have identical frequency ranges.
Table 8.4.1-1: Frequency bands in TS 25.461
UTRA
Operating
Band
E-UTRA
Operating
Band
UL operating band
UE transmit, BS receive
DL operating band
UE receive, BS transmit
[h]] [42] 3400 – 3600 MHz 3400 – 3600 MHz
[i]] [43] 3600 – 3800 MHz 3600 – 3800 MHz
Table B.2-2: Coding for operating bands in field 0x09 in TS 25.466
Bit no 15 14…11 10 9 8 7 6 5 4 3 2 1 0
Operating band Res. Spare [i43] [h42] 41 e40 f39 d38 c37 b36 b35 a34 a33
9 Required changes to UTRA FDD specifications
9.1 Required changes to TS 25.101
<Text to be added>
28. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)28Release 10
9.2 Required changes to TS 25.104
<Text to be added>
9.3 Required changes to TS 25.113
<Text to be added>
9.4 Required changes to TS 25.133
<Text to be added>
9.5 Required changes to TS 25.141
<Text to be added>
9.6 Required changes to TS 34.124
<Text to be added>
9.7 Required changes to TS 25.307
<Text to be added>
9.8 Required changes to TS 25.331
<Text to be added>
9.9 Required changes to TS 25.461
Required changes in specification TS 25.461 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 9.9-1: Required Changes in TS 25.461 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 25.461
4.3.7 Operating bands Table 4.3.7.1 “Frequency bands” of TS 25.461 require alteration to accommodate
the Band [42] and [43] frequency band parameters, see clause 8.4.1.
9.10 Required changes to TS 25.466
Table 9.9-1: Required Changes in TS 25.466for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 25.466
Annex B Assigned fields for
additional data
Table B.2-2 “Coding for operating bands in field 0x09” is updated with Band [42]
and [43], see clause 8.4.1.
29. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)29Release 10
10 Required changes to E-UTRA specifications
10.1 Required changes to TS 36.101
Required changes in specification TS 36.101 are described in the tables below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 10.1-1: Required Changes in TS 36.101 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 36.101
5.5 Frequency bands Three new operating bands need to be added as:
• Band [42], 200 MHz for TDD mode, 3400 – 3600 MHz
• Band [43], 200 MHz for TDD mode, 3600 – 3800 MHz
5.6 Channel Bandwidth Add these new bands in E-UTRA channel bandwidth, supported bandwidths are [5,
10, 15, and 20 MHz].
5.7.3 Carrier frequency and
EARFCN
Add the EARFCN numbers and parameters as in Table 8.1-2 of the present
document.
6.2.2 UE maximum output
power
Add 23 dBm UE power class for band [42] and [43].
6.6.2.1 Spectrum emission
mask
The current spectrum emission masks will remain.
6.6.3.1 TX spurious emissions The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
6.6.3.2 TX spurious emissions
band UE co-existence
[Add Tx spurious emissions for band [42] and [43]. The spurious emission
requirement is FFS.]
7.3.1 Reference sensitivity
level
[Add reference sensitivity level requirement for band [42] and [43]. The requirement
is FFS. ]
7.6.2 Minimum requirement
(Out of-band blocking)
[Add out-of-band blocking requirements for band [42] and [43]. The limits are FFS]
7.9.1 RX spurious emissions The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
Table 10.1-2: Required Changes in TS 36.101 for Band [22]
Section Requirement Discussion / Required Changes in TS 36.101
5.5 Frequency bands Three new operating bands need to be added as:
• Band [22], 2x90 MHz for FDD mode
3410 – 3500 MHz: Up-link (UE transmit, Base station receive)
3510 – 3600 MHz: Down-link (Base station transmit, UE receive)
5.6 Channel Bandwidth Add these new bands in E-UTRA channel bandwidth, supported bandwidths are [5,
10, 15, and 20 MHz].
5.7.3 Carrier frequency and
EARFCN
Add the EARFCN numbers and parameters as in Table 8.1-1 of the present
document.
5.7.4 TX-RX frequency
separation
Add this requirement for Band [22]. 100 MHz
6.2.2 UE maximum output
power
Add 23 dBm UE power class for band [22].
6.6.2.1 Spectrum emission
mask
The current spectrum emission masks will remain.
6.6.3.2 TX spurious emissions [Add Tx spurious emissions for band [22]. The spurious emission requirement is
FFS.]
7.3.1 Reference sensitivity
level
[Add reference sensitivity level requirement for band [22]. The requirement is FFS. ]
7.6.2 Minimum requirement
(Out of-band blocking)
[Add out-of-band blocking requirements for band [22]. The limits are FFS and need
to take into account the implementation of duplexer.]
30. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)30Release 10
10.2 Required changes to TS 36.104
Required changes in specification TS 36.104 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 10.2-1: Required Changes in TS 36.104 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 36.104
5.5 Frequency bands Three new operating bands need to be added as:
• Band [42], 200 MHz for TDD mode, 3400 – 3600 MHz
• Band [43], 200 MHz for TDD mode, 3600 – 3800 MHz
5.7.3 Carrier frequency and
EARFCN
Add the EARFCN numbers and parameters as in Table 8.1-2 of the
present document.
6.6.3.1 Operating band unwanted
emissions (Category A)
Add this requirement for Band [42] and [43], see subclause 10.2.1.
6.6.3.2 Operating band unwanted
emissions (Category B)
Add this requirement for Band [42] and [43], using option 2, see
subclause 10.2.1.
6.6.4.1 Mandatory Transmitter
spurious emissions
The upper frequency limit needs to be extended from 12.75 GHz to 19
GHz for Band [42] and Band [43]
6.6.4.2 Protection of BS receiver of
own or different BS
The current requirements will remain for the new band [42] and [43] ,
see subclause 10.2.1.
6.6.4.3 –
6.6.4.4
Spurious emissions / Co-
existence requirements
Add requirements for Band [42] and [43] , see subclause 10.2.1:
• Requirements for co-existence in the same geographical area and for
BS co-location with other bands
•
7.6.1 General blocking
requirement
Add requirements for Band [42] and [43] , see subclause 10.2.2.
7.6.2 Co-location with other base
stations
Add requirements for Band [42] and [43] , see subclause 10.2.2.
7.7.1 Receiver spurious
emissions
The upper frequency limit needs to be extended from 12.75 GHz to 19
GHz for Band [42] and Band [43]
Table 10.2-2: Required Changes in TS 36.104 for Band [22]
Section Requirement Discussion / Required Changes in TS 36.104
5.5 Frequency bands Three new operating bands need to be added as:
• Band [22], 2x90 MHz for FDD mode
3410 – 3500 MHz: Up-link (UE transmit, Base station receive)
3510 – 3600 MHz: Down-link (Base station transmit, UE receive)
5.7.3 Carrier frequency and
EARFCN
Add the EARFCN numbers and parameters as in Table 8.1-1 of the
present document.
6.6.3.1 Operating band unwanted
emissions (Category A)
Add this requirement for Band [22] see subclause 10.2.1.
6.6.3.2 Operating band unwanted
emissions (Category B)
Add this requirement for Band [22], using option 2, see subclause 10.2.1.
6.6.4.1 Transmitter spurious
emissions
The mandatory requirement is not changed, see subclause 10.2.1.
6.6.4.2 Protection of BS receiver of
own or different BS
The current requirements will remain for the new band [22] , see
subclause 10.2.1.
6.6.4.3 –
6.6.4.4
Spurious emissions / Co-
existence requirements
Add requirements for Band [22] , see subclause 10.2.1:
• Requirements for co-existence is the same geographical area and for
BS co-location with other bands (Band [22])
•
7.6.1 General blocking
requirement
Add requirements for Band [22] see subclause 10.2.2.
7.6.2 Co-location with other base
stations
Add requirements for Band [22] see subclause 10.2.2.
10.3 Required changes to TS 36.141
Required changes in specification TS 36.141 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
31. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)31Release 10
Table 10.3-1: Required Changes in TS 36.141 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 36.141
4.1.2 Acceptable uncertainty
of Test System
Measurement uncertainty may need to be updated for the 3.5 GHz band.
5.5 Operating bands Three new operating bands need to be added as:
Band [42], 200 MHz for TDD mode, 3400 – 3600 MHz
Band [43], 200 MHz for TDD mode, 3600 – 3800 MHz
5.7.3 Carrier frequency and
EARFCN
Add the EARFCN numbers and parameters as in Table 8.1-2 of the present
document.
6.6.2 Adjacent Channel
Leakage power Ratio
(ACLR)
The mandatory requirement is not changed.
6.6.3 Operating band
unwanted emissions
The mandatory requirement is not changed.
6.6.4.5.1 Mandatory TX spurious
emissions (Category A)
The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
6.6.4.5.1 Mandatory TX spurious
emissions (Category B)
The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
6.6.4.5.4 Coexistence with other
systems in the same
geographical area
Add requirements for Band [42] and [43],
• According note 2, overlapping frequency arrangements [22] and [42], the special
co-ex requirement apply for European market.
6.6.4.5.5 Colocation with other
base stations
Add requirements for Band [4421] and [43].
7.6.5.1 General requirement Add requirements for Band [42] and [43].
7.6.5.2 Co-location with other
base stations
Add requirements for Band [42] and [43].
7.7.5 RX spurious emissions The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
Annex G Test Tolerances and
Derivation of Test
Requirements
Measurement uncertainty may need to be updated for the 3.5 GHz band.
Table 10.3-2: Required Changes in TS 36.141 for Bands [22]
Section Requirement Discussion / Required Changes in TS 36.141
4.1.2 Acceptable uncertainty
of Test System
Measurement uncertainty may need to be updated for the 3.5 GHz band.
5.5 Operating bands Three new operating bands need to be added as:
Band [22], 2x90 MHz for FDD mode
3410 – 3500 MHz: Up-link (UE transmit, Base station receive)
3510 – 3600 MHz: Down-link (Base station transmit, UE receive)
5.7.3 Carrier frequency and
EARFCN
Add the EARFCN numbers and parameters as in Table 8.1-1 of the present
document.
6.6.2 Adjacent Channel
Leakage power Ratio
(ACLR)
The mandatory requirement is not changed.
6.6.3 Operating band
unwanted emissions
The mandatory requirement is not changed.
6.6.4.5.4 Coexistence with other
systems in the same
geographical area
Add requirements for Band [22].
• Requirements for co-existence is the same geographical area and for BS co-
location with other bands (Band [22])
• According note 2, overlapping frequency arrangements [22] and [42], the special
co-ex requirement apply for European market.
6.6.4.5.5 Colocation with other
base stations
Add requirements for Band [22]. The requirement is FFS.
7.6.5.1 General requirement Add requirements for Band [22]. The requirement is FFS.
7.6.5.2 Co-location with other
base stations
Add requirements for Band [22]. The requirement is FFS.
Annex G Test Tolerances and
Derivation of Test
Requirements
Measurement uncertainty may need to be updated for the 3.5 GHz band.
32. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)32Release 10
10.4 Required changes to TS 36.307
Required changes in specification TS 36.307 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 10.4-1: Required Changes in TS 36.307 (Rel-8 and Rel-9) for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 36.307
New Band [42] Independent of
Release
New clause listing all Rel-10 RF and RRM requirements that a Band [42]
shall comply with.
New Band [43] Independent of
Release
New clause listing all Rel-10 RF and RRM requirements that a Band [43]
shall comply with.
10.5 Required changes to TS 36.113
Required changes in specification TS 36.113 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 10.5-1: Required Changes in TS 36.113 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 36.113
4.5.2 Receiver exclusion band Add new entries for Bands [42] and [43] are required in clause 4.5.2. The
exclusion applies to 20 MHz below the lower frequency band edge, to
20 MHz above the upper frequency band edge.
Band [42] 3380 MHz – 3620 MHz
Band [43] 3580 MHz – 3820 MHz
10.6 Required changes to TS 36.124
Required changes in specification TS 36.113 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 10.6-1: Required Changes in TS 36.124 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 36.124
4.4 Receiver exclusion band Add new entries for Bands [42] and [43] in clause 4.4. The exclusion
applies to 85 MHz below the lower frequency band edge, to 85 MHz
above the upper frequency band edge.
Band [42] 3315 MHz – 3685 MHz
Band [43] 3515 MHz – 3885 MHz
11 Required changes to MSR specifications
11.1 Required changes to TS 37.104
Required changes in specification TS 37.104 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
33. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)33Release 10
Table 11.1-1: Required Changes in TS 37.104 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 37.104
4.5 Operating bands and
Band Categories
Table 4.5-2 “Unpaired bands in E UTRA and UTRA” requires alteration to
accommodate the new LTE3500 frequency band parameters, see subclause 8.1.1.
6.6.1.1. Mandatory TX spurious
emissions
The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
6.6.1.3.1 BS spurious emissions
limits for co-existence
with systems operating
in other frequency bands
Add requirements for co-existence with Bands [42] and [43], with same limits as for
other bands. According to Note 1, the 10 MHz frequency range immediately outside
the downlink operating band is excluded.
6.6.1.4.1 BS spurious emissions
limits for BS co-located
with another BS
Add requirements for co-existence with Bands [42] and [43], with same limits as for
other bands. According to Note 1, the 10 MHz frequency range immediately outside
the downlink operating band is excluded.
7.4.1 General blocking
minimum requirement
Bands [42] and [43] are added to the same entry as the other TDD bands, giving the
same limits as for bands 33 to 40.
7.4.5 Additional BC3 blocking
minimum requirement
Bands [42] and [43] are added to the same entry as the other TDD bands, giving the
same limits as for other bands 33 to 40.
7.5.1 General minimum
requirement for out-of-
band blocking
Bands [42] and [43] are added to the same entry as the other TDD bands, giving the
same limits as for bands 33 to 40.
7.5.2 Co-location minimum
requirement for out-of-
band blocking
Add requirements for co-existence with Bands [42] and [43], with same limits as for
other bands. According to Note 2, the 10 MHz frequency range immediately outside
the downlink operating band is excluded.
7.6 RX spurious emissions The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
11.2 Required changes to TS 37.113
Required changes in specification TS 37.113 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
Table 11.2-1: Required Changes in TS 37.113 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 37.113
4.4.2 Receiver exclusion band Table 4.4-3 “Receiver exclusion band for base stations (unpaired bands)” requires
alteration to accommodate the new LTE3500 frequency band parameters. The
exclusion applies to 20 MHz below the lower frequency band edge, to 20 MHz
above the upper frequency band edge.
Band [42]/[h)] 3380 MHz – 3620 MHz
Band [43]/[i)] 3580 MHz – 3820 MHz
11.3 Required changes to TS 37.141
Required changes in specification TS 37.141 are described in the table below. Requirements which are not shown are
applicable without any modifications from the existing specifications.
34. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)34Release 10
Table 11.3-1: Required Changes in TS 37.141 for Bands [42] and [43]
Section Requirement Discussion / Required Changes in TS 37.141
4.4 Operating bands and
Band Categories
Table 4.4-2 “Unpaired bands in E UTRA and UTRA” requires alteration to
accommodate the new LTE3500 frequency band parameters, see subclause 8.1.1.
6.6.1.5.1. Mandatory TX spurious
emissions (Category A)
The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
6.6.1.5.2. Mandatory TX spurious
emissions (Category B)
The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
6.6.1.5.5 Additional spurious
emissions requirement
for co-existence with
systems operating in
other frequency bands
Add requirements for co-existence with Bands [42] and [43], with same limits as for
other bands. According to Note 1, the 10 MHz frequency range immediately outside
the downlink operating band is excluded.
6.6.1.5.6 Spurious emissions
limits for BS co-located
with another BS
Add requirements for co-existence with Bands [42] and [43], with same limits as for
other bands. According to Note 1, the 10 MHz frequency range immediately outside
the downlink operating band is excluded.
7.4.5.1 General blocking test
requirement
Bands [42] and [43] are added to the same entry as the other TDD bands, giving the
same limits as for bands 33 to 40.
7.4.5.5 Additional BC3 blocking
test requirement
Bands [42] and [43] are added to the same entry as the other TDD bands, giving the
same limits as for other bands 33 to 40.
7.5.5.1 General minimum
requirement for out-of-
band blocking
Bands [42] and [43] are added to the same entry as the other TDD bands, giving the
same limits as for bands 33 to 40.
7.5.5.2 Co-location test
requirement
Add requirements for co-existence with Bands [42] and [43], with same limits as for
other bands. According to Note 2, the 10 MHz frequency range immediately outside
the downlink operating band is excluded.
7.6.5.1 RX spurious emissions The upper frequency limit needs to be extended from 12.75 GHz to 19 GHz for
Band [42] and Band [43]
12 Required changes to UTRA TDD specifications
12.1 Required changes to TS 25.101
12.2 Required changes to TS 25.102
Section 5.2 “Frequency bands” of TS 25.102 require alteration to accommodate the new LTE3500 frequency band
parameters, as follows.
5.2 Frequency bands
UTRA/TDD is designed to operate in the following bands;
a) 1900 - 1920 MHz: Uplink and downlink transmission
2010 - 2025 MHz: Uplink and downlink transmission
b) 1850 - 1910 MHz: Uplink and downlink transmission
1930 - 1990 MHz: Uplink and downlink transmission
c) 1910 - 1930 MHz: Uplink and downlink transmission
d) 2570 - 2620 MHz: Uplink and downlink transmission
e) 2300—2400 MHz: Uplink and downlink transmission
f) 1880 - 1920 MHz: Uplink and downlink transmission
35. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)35Release 10
[h)] 3400 - 3600 MHz: Uplink and downlink transmission
[i)] 3600 - 3800 MHz: Uplink and downlink transmission
Note: Deployment in existing or other frequency bands is not precluded.
12.3 Required changes to TS 25.105
Section 5.2 “Frequency bands” of TS 25.105 require alteration to accommodate the new LTE3500 frequency band
parameters, as follows.
5.2 Frequency bands
UTRA/TDD is designed to operate in the following bands;
a) 1900 - 1920 MHz: Uplink and downlink transmission
2010 - 2025 MHz Uplink and downlink transmission
b) 1850 - 1910 MHz Uplink and downlink transmission
1930 - 1990 MHz Uplink and downlink transmission
c) 1910 - 1930 MHz Uplink and downlink transmission
d) 2570 - 2620 MHz Uplink and downlink transmission
e) 2300 - 2400 MHz Uplink and downlink transmission
f) 1880 - 1920 MHz: Uplink and downlink transmission
[h)] 3400 - 3600 MHz: Uplink and downlink transmission
[i)] 3600 - 3800 MHz: Uplink and downlink transmission
Note: Deployment in existing and other frequency bands is not precluded.
The co-existence of TDD and FDD in the same bands is still under study in WG4.
12.4 Required changes to TS 25.142
Section 4.2 “Frequency bands” of TS 25.142 require alteration to accommodate the new LTE3500 frequency band
parameters, as follows.
4.2 Frequency bands
UTRA/TDD is designed to operate in the following bands:
a) 1900 - 1920 MHz: Uplink and downlink transmission
2010 - 2025 MHz Uplink and downlink transmission
b) 1850 - 1910 MHz: Uplink and downlink transmission
1930 - 1990 MHz: Uplink and downlink transmission
c) 1910 - 1930 MHz: Uplink and downlink transmission
d) 2570 - 2620 MHz Uplink and downlink transmission
e) 2300 - 2400 MHz Uplink and downlink transmission
36. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)36Release 10
f) 1880 - 1920 MHz: Uplink and downlink transmission
[h)] 3400 - 3600 MHz: Uplink and downlink transmission
[i)] 3600 - 3800 MHz: Uplink and downlink transmission
Note: Deployment in existing and other frequency bands is not precluded.
38. 3GPP
3GPP TR 37.801 V0.10.0 (2011-01)38Release 10
Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New
2008-04 RAN4#47 R4-080935 TR skeleton 0.0.1
2008-05 RAN4#47 R4-081212 Agreed TP in RAN4#47:
R4-081210, "TP for Regional 3500 MHz band
arrangements and use"
0.0.1 0.1.0
2008-11 RAN4#49 R4-083231 Agreed TP in RAN4#49:
R4-082953, "TP for LTE/UMTS3500 TR: Frequency
band arrangements"
0.1.0 0.2.0
2009-02 RAN4#50 R4-091019 TR updated to be in line with TR template v1.7.0.
Agreed Text Proposals in RAN4#50:
R4-090615, "TP for band pairing 3400-3600 MHz"
0.2.0 0.3.0
2009-05 RAN4#51 R4-092007 Agreed Text Proposal in RAN4#50bis:
R4-091216, "Additional arrangements in the 3.4-3.8MHz
band"
0.3.0 0.4.0
2009-10 RAN4#52bis R4-093981 Agreed Text Proposal in RAN4#52 and RAN4#52bis:
R4-092959, "Text proposal on UMTS/LTE 3500 TDD
channel raster and numbering"
R4-093037, "UMTS/LTE 3500: Channel raster and
numbering for paired bands (TR ch 7.1 and 8.1)"
R4-093038, "UMTS/LTE 3500: Channel raster and
numbering for unpaired bands (TR ch 8.1)"
R4-093743, "Text proposal on corrections of additional
arrangements in the 3.4-3.8MHz band"
R4-093948, "TP on UE Requirements for New Bands of
3.5 GHz"
R4-093949, "TP on BS Requirements for New Bands of
3.5 GHz"
0.4.0 0.5.0
2009-11 RAN4#53 R4-094780 Agreed Text Proposal in RAN4#53:
R4-094840, "Required Changes of Base Station
Conformance Testing for 3.5 GHz (36.141)"
0.5.0 0.6.0
2010-06 RAN4 AH#3 R4-102544 Agreed Text Proposal in RAN4 #55:
R4-102335, "TP for LTE3500 TR, clause 10.2, 10.3
(Blocking requirements)"
R4-102336, "TP for LTE3500 TR, clause 10.2, 10.3
(Unwanted emissions)"
0.6.0 0.7.0
2010-08 RAN4#56 R4-103160 Agreed Text Proposal in RAN4 AH#3:
R4-102441, "TP for LTE3500 TR, Band and channel
arrangement (MSR specifications)"
R4-102442, "TP for LTE3500 TR, Band and channel
arrangement (TDD UTRA specifications)"
R4-102443, "TP for LTE3500 TR, Band and channel
arrangement (TDD UTRA Iuant interface specifications)"
0.7.0 0.8.0
2010-10 RAN4# AH#4 R4-103916 Agreed Text Proposal in RAN4 AH#3:
R4-103715, "TP on Way forward for UMTS-LTE 3500
deployment aspects"
R4-103716, "TP for Updates to general parts (TR
37.801 clause 3-5)"
R4-103717, "TP for Corrections of E-UTRA updates (TR
37.801 clause 8-10)"
R4-103718, "TP for Required changes to TS 36.307 (TR
37.801 clause 10.4)"
R4-103719, "TP for Required changes to TS 36.113 (TR
37.801 clause 10.X)"
R4-103720, "TP for Required changes to TS 36.124 (TR
37.801 clause 10.X)"
R4-103822, "TP for Required changes to TS 37.104 (TR
37.801 clause 11.1)"
R4-103823, "TP for Required changes to TS 37.141 (TR
37.801 clause 11.3)"
0.8.0 0.9.0
2010-11 RAN4#57 R4-104399 Editorial updates and corrections 0.9.0 0.9.1
2010-11 RAN4#57 R4-104786 Agreed Text Proposal in RAN4 AH#3:
R4-104474, "TP for UMTS-LTE 3500 MHz spurious
emissions range (TR 37.801)"
R4-104613, "TP for Radio Frequency Channel Number
(RFCN)"
R4-104785, "TP for Band 42 and 43 EARFCN (TR
0.9.0 0.10.0