hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.1 Task description | The purpose of this work item is to:
1) Study of Adding L-Band LTE for ATC of MSS in North America
2) Generate CRs to necessary 3GPP specifications
3) Generate a new technical report based on the study results
The specific spectrum band to be studied is Band 24:
- 1626.5 – 1660.5 MHz: Up-link
- 1525 - 1559 MHz: Down-li... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2 Regulatory and Emissions Background | In 2003, the FCC and Industry Canada approved rules permitting Mobile Satellite Services (MSS) and Ancillary Terrestrial Component (ATC) operations in assigned L-Band frequency bands [3]. In the US and Canada, these rules allow ATC network operations to coexist with neighboring bands and services. Subsequently in 2010,... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.1 Intra-L-Band Geographic Coordination Requirements | Within the L-band, coordination with other satellite operators is a bilateral matter between LightSquared and the other operator(s) (both under ITU and FCC rules). Furthermore, it is subject to confidentiality agreements with those operators and also subject to change over time. Hence it is not considered appropriate t... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.1.1 Search & Rescue (SAR) Protection | FCC Requirement: Every LightSquared eNodeB within 80 km or radio horizon of a SARSAT receiver operating in the 1544 – 1545 MHz, whichever is shorter, would be required to be coordinated with that SARSAT receiver. Similarly, every outdoor microcell within 45 km or radio horizon of a SARSAT receiver, whichever is shorter... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.1.2 Radio Astronomy System (RAS) Protection | FCC Requirement: ATC mobile terminals shall be operated in a fashion that takes all practicable steps to avoid causing interference to U.S. radio astronomy service (RAS) observations in the 1660–1660.5 MHz band.
Compliance Plan: Protection to RAS will be offered through geographical coordination.
Fig 4.2.1.2-1: Spectra... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.2.1 Defense/Aeronautical (MAT) Protection | FCC Requirement: The obligations of an ATC network to Mobile Aeronautical Telemetry systems operating in 1435 – 1525 MHz band are outlined as follows:
- Take all practicable steps to avoid locating ATC base stations within radio line of sight of Mobile Aeronautical Telemetry (MAT) receive sites in order to protect U.S.... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.2.2 RNSS (GPS) Band Protection | FCC Requirement: The obligations of an L-band eNodeB to the GPS band operating in 1559 – 1610 MHz are outlined as follows:
● Narrowband Emissions - (EIRP of discrete emissions of less than 700 Hz bandwidth, averaged over any 2 millisecond active transmission interval):
▪ [-80 dBm from 1559 to 1610 MHz]
● Wideband Emiss... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.3 UE Emissions Requirements | The following information outlines the UE emissions masks for L-Band, in EIRP metrics, consistent with FCC’s ATC rules.
● Maximum Power: +23 (+/- 2) dBm
● Out-of-Band Emissions for Mobile Terminals:
▪ OOCE/OOBE Emission:
- Limit of -58 dBW/4kHz (-28 dBm/4kHz) per terminal at a 1 MHz offset from the edge of the spectru... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 4.2.4 Overload Characteristics of GPS Receivers in Proximity to LTE Band 24 eNBs | In response to 3GPP RAN4 request for LightSquared to perform a study on the overload impact of LTE Band 24 on GPS receivers involved in cellular applications [21, 22], LightSquared has performed Field and Lab Tests for six (6) CellPhones/SmartPhones, as well as fixed GPS timing unites, used in network infrastructure, t... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5 Study of E-UTRA requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1 Operating band and channel arrangement | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.1 Operating bands | The L-Band LTE for ATC of MSS in North America is designed to operate in the operating band defined in Table 5.1.1-1:
Table 5.1.1-1: E-UTRA frequency bands
E‑UTRA Operating Band
Uplink (UL) operating band
BS receive
UE transmit
Downlink (DL) operating band
BS transmit
UE receive
Duplex Mode
FUL_low – FUL_high
FDL_low –... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.2 Channel bandwidths per operating band | The transmission bandwidth configuration in Table 5.1.2-1 shall be supported for each of the specified channel bandwidths.
Table 5.1.2-1: E-UTRA channel bandwidth
E-UTRA band / channel bandwidth
E-UTRA Band
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
24
Yes
Yes |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.3 Carrier frequency and EARFCN | The relation between EARFCN and the carrier frequency in MHz for the downlink is given by the following equation, where FDL_low and NOffs-DL are given in Table 5.1.3-1 and NDL is the downlink EARFCN.
FDL = FDL_low + 0.1(NDL – NOffs-DL)
The relation between EARFCN and the carrier frequency in MHz for the uplink is given... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.4 TX–RX frequency separation | The default E-UTRA TX channel (carrier centre frequency) to RX channel (carrier centre frequency) separation is specified in Table 5.1.4-1 for the TX and RX channel bandwidths defined in Table 5.1.2-1.
Table 5.1.4-1: Default UE TX-RX frequency separation
E-UTRA Operating Band
TX - RX
carrier centre frequency
separation... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.1.5 Band Release Independence | Band 24 is specified in Release 10, but is defined as a release-independent frequency band. This approach aligns the Band 24 band with other frequency bands when considering features that have to be supported in different releases.
UEs that conform to Release 8 and support Band 24 shall support the following requiremen... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2 Specific UE RF requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.1 Maximum Output Power | Band 24 will operate at the same maximum output power level as bands listed in Table 5.2.1-1 (Table 6.2.2-1 from 3GPP TS 36.101 [7]). The following UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth.
Table 5.2.1-1: UE Power Class
EUTRA band
Class 1 (dBm)
Toleran... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.2 Maximum Output Power with additional Requirements | Band 24 will use the default value for Additional Maximum Power Reduction (A-MPR) of 0 dB. |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.3 Spurious Emissions | Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, inter-modulation products and frequency conversion products, but exclude out of band emissions.
In section 4.2.3 of the TR [2], LightSquared previously noted that the FCC requirements for L... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.2.4 Reference Sensitivity Power Level | The reference sensitivity power level REFSENS is the minimum mean power applied to both the UE antenna ports at which the throughput shall meet or exceed the requirements for the specified reference measurement channel.
For the PREFSENS parameters provided in Table 5.2.4-1 below (from 3GPP TS 36.101 [7], Table 7.3.1-1)... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3 Specific BS RF requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.1 Operating band unwanted emissions | The operating band unwanted emission limits, specified in EIRP metrics, are defined from 10 MHz below the lowest frequency of the downlink operating band up to 10 MHz above the highest frequency of the downlink operating band. The requirements shall apply to whatever the type of transmitter considered (single carrier o... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.2 Additional spurious emissions requirements | These requirements may be applied for the protection of systems operating in frequency ranges other than the E-UTRA BS downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the E-UTRA BS, or they may be set by local or regional regulat... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.3 Co-location with other base stations | These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an E-UTRA BS. The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with base stations of the sa... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.4 General blocking requirement | The blocking characteristics are a measure of the receiver’s ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer, which is a 1.4MHz, 3MHz or 5MHz E-UTRA signal for in-band blocking or a CW signal for out-of-band blocking.
The general blocking requirements currently speci... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.5 Blocking requirement for co-location with other base stations | This additional blocking requirement may be applied for the protection of E-UTRA BS receivers when GSM, UTRA or E-UTRA BS operating in a different frequency band are co-located with an E-UTRA BS. The requirements assume a 30 dB coupling loss between interfering transmitter and E-UTRA BS receiver and are based on co-loc... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.6 UTRAN requirements | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.6.1 Required changes to 3GPP TS 25.461 | In 3GPP TS 25.461 [14], section 4.3.7 “Operating bands” and the corresponding Table 4.3.7.1 (Table 5.3.6.1-1 below) “Frequency bands” of 3GPP TS 25.461 [14] require alteration to accommodate the new L_Band_LTE_ATC_MSS frequency band parameters, as follows. (Section 6.8 of the TR for the work item summarizes these chang... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 5.3.6.2 Required changes to 3GPP TS 25.466 | In 3GPP TS 25.466 [15], Annex B “Assigned fields for additional data” and the corresponding Table B.2-1 (Table 5.3.6.2-1 in 3GPP TS 25.466 [15]) “Coding for operating bands in field 0x08” of 3GPP TS 25.466 [15] require alteration to accommodate the new L_Band_LTE_ATC_MSS frequency band parameters, as follows. (Section ... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6 Summary of required changes to E-UTRA specifications | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.1 Required changes to 3GPP TS 36.101 | Required changes in 3GPP TS 36.101 [7] are shown in Table 6.1-1.
Table 6.1-1: Required Changes for 3GPP TS 36.101 [7]
Clause
Description
Description of change
Proposed changes
5.5
Operating bands
Add a new row for the band into Table 5.5-1.
R4-102509
5.6.1
Channel bandwidths per operating band
Add channel bandwidths 5 ... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.2 Required changes to 3GPP TS 36.104 | Required changes in 3GPP TS 36.104 [8] are shown in Table 6.2-1.
Table 6.2-1: Required Changes for 3GPP TS 36.104 [8]
Clause
Description
Description of change
Proposed changes
5.5
Operating bands
Add a new row for the band into Table 5.5-1.
R4-102509
5.7.3
Carrier frequency and EARFCN
Add new channel numbers for the ba... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.3 Required changes to 3GPP TS 36.113 | Required changes in 3GPP TS 36.113 [9] are shown in Table 6.3-1.
Table 6.3-1: Required changes for 3GPP TS 36.113 [9]
Clause
Description
Description of change
Proposed changes
4.5.2
Receiver exclusion band
Add a new row for the band.
R4-102509 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.4 Required changes to 3GPP TS 36.124 | Required changes in 3GPP TS 36.124 [10] are shown in Table 6.4-1.
Table 6.4-1: Required changes for 3GPP TS 36.124 [10]
Clause
Description
Description of change
Proposed changes
4.4
Receiver exclusion band
Add a new row for the band.
R4-102509 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.5 Required changes to 3GPP TS 36.133 | Required changes in 3GPP TS 36.133 [11]are shown in Table 6.5-1.
Table 6.5-1: Required changes for 3GPP TS 36.133 [11]
Clause
Description
Description of change
Proposed changes
4.2.2.3
Measurements of intra-frequency E-UTRAN cells
Add the band to the band list for RSRP and SCH_RP.
R4-103619
4.2.2.4
Measurements of inte... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.6 Required changes to 3GPP TS 36.141 | Required changes in 3GPP TS 36.141 [12] are shown in Table 6.6-1.
Table 6.6-1: Required Changes for 3GPP TS 36.141 [12]
Clause
Description
Description of change
Proposed changes
5.5
Operating bands
Add a new row for the band into Table 5.5-1.
R4-102509
5.7.3
Carrier frequency and EARFCN
Add new channel numbers for the ... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.7 Required changes to 3GPP TS 36.307 | Required changes in 3GPP TS 36.307 [13] are shown in Table 6.7-1.
Table 6.7-1: Required Changes for 3GPP TS 36.307 [13]
Clause
Description
Description of change
Proposed Changes
New clause
Band 24 Independent of Release
Add a new clause to specify the extra requirements for UE conforming to earlier releases to support ... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.8 Required changes to 3GPP TS 25.461 | Required changes in 3GPP TS 25.461 [14] are shown in Table 6.8-1.
Table 6.8-1: Required changes for 3GPP TS 25.461 [14]
Clause
Description
Description of change
Proposed Changes
4.3.7
Operating bands
Add a new row for the band in Table 4.3.7.1.
R4-103240 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.9 Required changes to 3GPP TS 25.466 | Required changes in 3GPP TS 25.466 [15] are shown in Table 6.9-1.
Table 6.9-1: Required changes for 3GPP TS 25.466 [15]
Clause
Description
Description of change
Proposed Changes
Annex B
Assigned fields for additional data
Add an entry for the band in Table B.2-1.
R4-103240 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.10 Required changes to 3GPP TS 25.101 | Required changes in 3GPP TS 25.101 [16] are shown in Table 6.10-1.
Table 6.10-1: Required Changes for 3GPP TS 25.101 [16]
Clause
Description
Description of change
Proposed Changes
6.6.3
Spurious emissions
Add the band DL frequency range into Tables 6.13 and 6.13A for UTRA Band II, IV, V, X, XII, XIII and XIV.
R4-104674 |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.11 Required changes to 3GPP TS 25.104 | Required changes in 3GPP TS 25.104 [17] are shown in Table 6.11-1.
Table 6.11-1: Required Changes for 3GPP TS 25.104 [17]
Clause
Description
Description of change
Proposed Changes
6.6.3.3
Co-existence with other systems in the same geographical area
Add a new row for the band into Table 6.11.
R4-104052
6.6.3.4
Co-exist... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.12 Required changes to 3GPP TS 25.141 | Required changes in 3GPP TS 25.141 [18] are shown in Table 6.12-1.
Table 6.12-1: Required Changes for 3GPP TS 25.141 [18]
Clause
Description
Description of change
Proposed Changes
6.5.3.7.4
Co-existence with other systems in the same geographical area
Add a new row for the band into Table 6.38.
R4-104053
6.5.3.7.5
Co-e... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.13 Required changes to 3GPP TS 37.104 | Required changes in 3GPP TS 37.104 [19] are shown in Table 6.13-1.
Table 6.13-1: Required Changes for 3GPP TS 37.104 [19]
Clause
Description
Description of change
Proposed Changes
6.6.1.3
Additional spurious emissions requirements
Add a new row for the band into Table 6.6.1.3.1-1.
R4-104054
6.6.1.4
Co-existence with co... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 6.14 Required changes to 3GPP TS 37.141 | Required changes in 3GPP TS 37.141 [20] are shown in Table 6.14-1.
Table 6.14-1: Required Changes for 3GPP TS 37.141 [20]
Clause
Description
Description of change
Proposed Changes
6.6.1.5.5
Additional spurious emission requirements
Add a new row for the band into Table 6.6.1.5.5-1.
R4-104055
6.6.1.5.6
Co-location with ... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 7 Project plan | |
41f4dd01af106b6509f05176f478e52b | 36.813 | 7.1 Schedule and Work Task Status | The schedule and work task status for this work item are summarized in Table 7.1-1 below.
Table 7.1-1 Schedule and Work Task Status
RAN4 Meeting and Date
Work Tasks
Status
RAN4#55 (April 2010)
TR Skeleton
Approved
Summary of required changes to E-UTRA specifications
Approved
Band and channel arrangement
Approved
RAN4 A... |
41f4dd01af106b6509f05176f478e52b | 36.813 | 8 Open issues | None as of December, 2010.
Annex A (informative):
Configuration Example
This section provides one example of how a practical L-Band eNodeB may be configured. The example uses the following parameters: Two 10 MHz LTE carriers in a given sector.
● Centre frequency of Carrier-1: 1526-1536MHz
◦ ○ Channel Power : 20Wa... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 1 Scope | The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 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.
• Fo... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3 Feature: Enhanced Home NodeB / eNodeB UID_400035 | |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3.1 BB: 3G Home NodeB Gateway OAM&P (HNB-OAM_GW) UID_420035 | Technical Specification Group Services and System Aspects TSGS#42(08)0794
Meeting #42, 8 - 11 December 2008,
Athens, Greece
Technical Specification Group Services and System Aspects TSGS#47(10)0087
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100889
Meeting SA5#70, 1-5 Mar 2010, X... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 1 3GPP Work Area * | X
Radio Access
X
Core Network
Services |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2 Classification of WI and linked work items | |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.0 Primary classification * | This work item is a … *
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
X
Work Task (go to 2.4) |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.1 Study Item | Related Work Item(s) (if any]
Unique ID
Title
Nature of relationship
Go to §3. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.2 Feature | Related Study Item or Feature (if any)
Unique ID
Title
Nature of relationship
Go to §3. |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.3 Building Block | Parent Feature (or Study Item)
Unique ID
Title
TS
This work item is …
X
Stage 1 (go to 2.3.1)
X
Stage 2 (go to 2.3.2)
X
Stage 3 (go to 2.3.3)
Test spec (go to 2.3.4)
Other (go to 2.3.5)
2.3.1 Stage 1
Source of external requirements (if any)
Organization
Document
Remarks
none
Go to §3.
2.3.2 Stage 2
Corresponding stag... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3 Justification * | The target of SON is to maintain network quality and performance with a minimum of manual intervention from the operator.
Self-optimization functionality will monitor and analyse performance management data, and will automatically trigger optimization action on the affected network node(s) when necessary. This will sig... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 4 Objective * | Collect and document Self-Optimization OAM requirements for SON.
Define in cooperation with RAN WGs inputs to and outputs from the Self-Optimization Entity, its location in the management architecture, and the degree of standardisation of the associated algorithms.
Identify and document required Self-Optimization relat... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 5 Service Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 6 MMI-Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 7 Charging Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 8 Security Aspects | None |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Impacts * | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
Don't know
X |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale * | New specifications *
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.521
Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
SA5
SA#44 Jun 2009
SA#4... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.507
Self Configuration of Network Elements Integration Reference Point (IRP): SOAP Solution Set (SS) (Release 9)
SA#47 Mar 2010
SA#47 Mar 2010
... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 4 Multi-Media Telephony Service enhancements UID_400032 | Technical Specification Group Services and System Aspects TSGS#43(09)0051
Meeting #43, 9 - 12 March 2009, Biarritz, France
3GPP TSG-SA5 (Telecom Management) S5-091540
Meeting SA5#63, 16-20 February 2009, Prague, CZ revision of S5-091174
Source: SA5 (Telecom Management)
Title: New WID on Multimedia Telephony Service an... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 5 User Data Convergence | TSG SA Meeting #44 SP-090309
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092483
Meeting SA5#65, 11-15 May 2009, Tallinn, Estonia revision of S5-092426
Source: China Mobile, T-Mobile, Ericsson
Title: New Umbrella BB-level WID for the SA5 work on User Data Convergence - Modelling and Mana... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 6 MBMS support in EPS UID_400039 | Technical Specification Group Services and System Aspects TSGS#43(09)0052
Meeting #43, 9 - 12 March 2009, Biarritz, France
3GPP TSG-SA5 (Telecom Management) S5-091541
Meeting SA5#63, 16-20 February 2009, Prague, CZ revision of S5-091309
Source: SA5 (Telecom Management)
Title: New WID on MBMS support in EPS:
MBMS Charg... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 7 Feature: OAM&P 9 UID_420029 | BB: Network Infrastructure Management UID_420030
Technical Specification Group Services and System Aspects TSGS#42(08)0756
Meeting #42, 8 - 11 December 2008, Athens, Greece
3GPP TSG-SA5 (Telecom Management) S5-081836
Meeting SA5#61, 13~17 October 2008, Dalian, China (revision of S5-081... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 1 3GPP Work Area | X
Radio Access
Core Network
Services |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 2.0 Primary classification | This work item is a Feature
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
X
Work Task (go to 2.4) |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 3 Justification | Self-Configuration, 3GPP TS 32.501 has a chapter 6.5.2.6 titled “Radio Configuration Data”, but its only content is “FFS”. Consequently 32.502 and 32.503 contain nothing to fulfil some of the requirements listed in clause 5.1.5.1 of TR 32.816.
When radio Network Elements (e.g. cells and/or eNBs) are inserted into an op... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 4 Objective | It is proposed to work on technical solutions for Automatic Radio Network Configuration Data Preparation, i.e.:
Analyse which configuration parameter cannot be determined before-hand by the IRPAgent or by the self-configuration process and what input might be needed to generate them.
Define new functionality to trigger... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
Don't know
X |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 11 Work item rapporteur(s) * | Frode Nergard (frode.nergard@ericsson.com) |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 12 Work item leadership * | SA5 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 13 Supporting Individual Members * | Supporting IM name
Ericsson
Verizon Wireless
Alcatel-Lucent
T-Mobile
Nokia Siemens Networks
BB: Self-Organizing Networks (SON) UID_430043
Technical Specification Group Services and System Aspects TSGS#39(08)0067
Meeting #39, 10 - 13 March 2008, Puerto Vallarta, Mexico
Source: SA5 (Telecom Management)
Title: New WT-leve... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 8 Charging Management and Small Enhancements (CH9) UID_440068 | Technical Specification Group Services and System Aspects TSGS#47(10)0090
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101075
Meeting SA5#70, 1-5 Mar 2010, Xiamen, P.R. China revision of S5-100975
TSG SA Meeting #44 SP-090312
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Tele... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Feasibility Studies | Technical Specification Group Services and System Aspects TSGS#36(07)0306
Meeting #36, 4 – 7 June 2007, Busan, KOREA
Source: SA5 (Telecom Management)
Title: WID Study of System Maintenance by Itf-N
Document for: Approval
Agenda Item: 11.28 (OAM-Study) - OAM&P Studies
3GPP TSG-SA5 (Telecom Management) S5-071006
Meeting ... |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale (to be updated at each plenary) | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
TR 32.824
Study on SOA compliant need and additional capabilities for existing/currently planned Interface IRPs
SA5
SA#43 Sep 2009
SA#44 June 2009
... |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.531 Telecommunication management; Software management; Concepts and Integration Reference Point (IRP) Requirements | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.532 Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS) | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.533 Telecommunication management; Software management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.535 Telecommunication management; Software management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | Software Management, in general, provides the operator with the ability to manage effectively the software entities residing in the 3G network. Software Management function is useful especially when there is a need to manage a large number of software residing in the managed elements widely distributed geographically. ... |
8a916e998185fce27065b78e6b079636 | 32.535 | 1 Scope | The present document provides the XML file format definition for the Software Management Integration Reference Point (IRP) IS [3] V9.2.X.
The present document specifies the XML Definitions for the Software Management Integration Reference Point (IRP) as it applies to Itf-N, in accordance with Software Management IRP IS... |
8a916e998185fce27065b78e6b079636 | 32.535 | 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.
• Fo... |
8a916e998185fce27065b78e6b079636 | 32.535 | 3 Definitions and abbreviations | |
8a916e998185fce27065b78e6b079636 | 32.535 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], and 3GPP TS 32.331 [5] apply. |
8a916e998185fce27065b78e6b079636 | 32.535 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
IRP Integration Reference Point
IS Information Service
NL Notification Log
NRM Network Resource Model
SwM Software Management
UML Unified Modelling Language
XML eXtensible Markup Language |
8a916e998185fce27065b78e6b079636 | 32.535 | 4 Software Management IRP XML Definitions | |
8a916e998185fce27065b78e6b079636 | 32.535 | 4.1 Software Management IRP XML Definitions | This section provides XML definitions of Software Management IRP IOCs and notifications as defined in [3].
4.2 XML Schema for Software Management IRP Notifications (file name “swManagementIRPNotif.xsd”)
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xe="http://www.3gpp.org... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 1 Scope | This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
The present document shall analyse the current network selection mechanism and will highlight its limitations based on known operational problems. It will also consider issues brought about by the advent of new access systems.
P... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 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.
• Fo... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3 Definitions, symbols and abbreviations | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply.
R-UIM Removable User Identity Module (note this is a 3GPP2 term) |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
AP Access Point
CN Core Network
CS Circuit Switched
CSD Circuit Switched Data
FBS Full Band Scan
FPLMN Forbidden Public Land Mobile Network
HPLMN Home Public Land Mobile Network
I-WLAN Interworking WLAN
ME Mobile Equipment
OOS Out Of Se... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 4 Network Selection overview | The Stage 1 Requirements for Network Selection are found in TS 22.011 [1]. This describes the behaviour that is expected from a UE in order to select a PLMN from which to gain service.
Two modes of operation are supported: Automatic and Manual. At power on, and the UE is required to revert to the last mode used at powe... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.