hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5 High level principles | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.1 General | This clause describes the principles that are applicable in network selection up to Rel-6 and that are not expected to be challenged by the enhancements introduced to the network selection procedures. Furthermore the expectations of the three main stakeholders in the network selection procedures (customer, home operato... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.2 Key principles | The following is a set of principles that should be preserved when devising a new procedure to perform the registration to the serving mobile network. The assumption made in this paragraph is that the term “network” has to be interpreted as the core network of the mobile operator with whom the subscriber has direct rel... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.3 Backward compatibility | Enhancements to the network selection principles will not negatively affect the functionality of existing devices.
Enhancements to the Network Selection procedure in the core network shall be done such that backwards compatibility with existing UEs is maintained.
The network selection principles should allow for at lea... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.4 Customer expectations | Following switch-on where there is no last registered PLMN, the user should be registered on non-forbidden PLMN as fast as possible (typically within 20 seconds). This period includes the execution of any 3GPP defined functionality (e.g. after any PIN verification) that is performed by the mobile device but excludes an... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.5 Home operator expectations | The home operator's users' devices should select the home operator's preferred network and access type while roaming.
The home operator should be able to set which preferred networks are in the customer’s device. The home operator should be able to set the mix of networks and access types that can be used by each roami... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.6 Visited operator expectations | It should be possible for the visited operator to direct traffic from roamers onto the appropriate access technology to manage network capacity and loading (e.g. to use 2G for voice and 3G for high speed data services). The ability to change the access in real-time for roamers according to their usage should be possibl... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.7 UICC and USIM considerations | In terms of Network Selection Procedures, the USIM contains several sets of data that are used either for automatic or manual selection:
- User controlled PLMN selector with Access Technology
- Operator controlled PLMN selector with Access Technology
- Higher Priority PLMN search period
- Forbidden PLMNs
- HPLMN select... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6 Identified issues with current specifications | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.1 HPLMN initiated network reselection | No dynamic mechanism exists for the HPLMN to request that a UE selects a different VPLMN whilst roaming. Currently this happens through the use of the background scan when the UE is on a non-preferred network. This mechanism is not considered dynamic since updating the preference lists in the UE and taking the new list... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.2 Single priority or no priorities on VPLMNs | Currently the only standardised automatic network selection mechanism by which the HPLMN can control which VPLMN is selected is through the Operator preferred list. The intended behaviour is that one network in the visited country takes precedence over all the others, and in the case where a UE has selected an alternat... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.3 Manual network selection | Manual selection is a useful tool in cases where the selected PLMN is not providing adequate quality. However, in other circumstances it prevents the mobile operator from providing the user with the best possible service.
One key limitation of manual network selection is that the user is presented only with the network... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.4 Time to select a network | When multiple bands and multiple technologies are available the time to select a PLMN may be too long. The new procedure should address this area |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.5 RAT preference for PLMNs not prioritised by the USIM | This refers specifically to the case of the initial PLMN selection. Subsequent to that, the serving PLMN may change the RAT used by the UE .The visited operator should be able to allocate access technology and data rates on the basis of the identity (e.g. MCC-MNC) of the home operator of the inbound roamer.
TS 23.122 ... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.6 A new PLMN can only be selected after an exhaustive scan | This section highlights that the time from loss of coverage to registration on a new PLMN is already quite long and with future developments will possibly be even longer.
TS 23.122 [2] and TS 25.304 mandate that the UE shall search for its last RPLMN in every supported RAT and bands at power on or recovery from lack of... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.10 Ping ponging between Registration Areas | Currently the mechanisms standardised do not seem to adequately cater for the national roaming scenario nor formulti RAT (3G, WLAN, 2G etc.) environments. This, when associated with fluctuating signal condition, can lead to UE ping-ponging between 2G and 3G , causing significant signalling load on the network as well a... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.11 The last RPLMN is always the highest priority | TS 23.122 [2] mandates that the UE shall always select in priority its last RPLMN or an ePLMN when recovering from out of coverage or at power-on.
The main reason for this RPLMN requirement was due to the fact that in all roaming cases at that time the mobile will not find its HPLMN and this introduced an unnecessary (... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.12 Network selection in border areas | A problem exists for mobile users when commuting across national borders. Whilst manual network selection may be used to ensure that the user can select the HPLMN / EHPLMN, many users use Automatic Selection mode; and the ME is only permitted to select PLMNs of a higher priority within the same country in automatic mod... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.13 Multiple EHPLMNs | Currently the TS 23.122 [2] allows an operator to define a list of EHPLMNs which may have different priority. Thus under automatic network selection it is possible to for one of the constituent networks to be given priority over another. Manual network selection only allows the highest EHPLMN to be displayed to the su... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 7 Impact of technology changes | This section looks at how technology changes can impact the current Network Selection mechanism. When a new technology has been introduced typically one of two options are taken:
- Replication of the network selection principles.
Replicating the user experience provides the same over all "look and feel" to the user, ho... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 7.1 Multi-provider environments | The network selection procedures in TS 22.011 [1] focuses on PLMN selection defined in Section 3.2.2.1 as “an UE based procedure, whereby candidate PLMNs are chosen, one at a time, for attempted registration”.
Upcoming usage scenarios may require taking into consideration for network selection where there are different... |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 8 Conclusions | This Technical Report has reviewed current practice with regard to Network Selection Principles and considered the impact of some future developments within 3GPP on the existing mechanisms. It is concluded that it would be beneficial to consider enhancements to the current specifications in a number of areas.
1) A numb... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 1 Scope | The purpose of this document is to contain the updated Work Item Descriptions (WIDs) and capture status of all SA5 work items of the current 3GPP Release in order for the group to get an overview of current ongoing work.
This TR is used as a mean to provide input to the complete 3GPP work plan that is handled by MCC.
S... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 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... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 3 Operations, Administration, Maintenance & Provisioning - OAM&P | Feature: Operations, Administration, Maintenance & Provisioning (OAM7) Unique_ID: 35041
BB: Network Infrastructure Management (OAM7-NIM) Unique_ID: 35042
Technical Specification Group Services and System Aspects TSGS#28(05)0302
Meeting #28, Quebec, CANADA, 06-08 June 2005
Source: SA5 (Telecom Management)
Title: WID W... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
No
X
X
X
Don't know
X |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 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
NA
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
32.240
TBD
Add new principl... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 14c The WI is a Work Task: parent Building Block | • SA5's Charging Management small Enhancements (UID 320007, CH7) |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.307 Notification IRP SOAP SS | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.317 Generic IRP Management SOAP SS | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.607 Basic CM IRP SOAP SS | 32.665 Kernel CM IRP XML definitions |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.667 Kernel CM IRP SOAP SS | 5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 3.2 Principle of radio channel power monitoring | The transport channels and physical channels have mapping relations. The following is mapping of transport channels onto physical channels.
25.211
From the figure above, the mapping from transport channel to physical channel is mostly one to one. So, in most cases, we just need to monitor the physical channels.
It is p... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 14b The WI is a Building Block: parent Feature | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 4 Charging Management | WT Charging aspects of FBI for PacketCable Unique_ID: 7032
Acronym: FBI-PCBL-CH
Technical Specification Group Services and System Aspects TSGS#31(06)0145
Meeting #31, 13 - 16 March 2006, Sanya, China
Source: SA WG2
Title: Revised WID: "System enhancements for fixed broadband access to IMS".
Document for: Approval
Agen... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 14a The WI is a Feature: List of building blocks under this feature | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 5 Status list of Work items | This list reflects work items ongoing, completed, stopped or moved to Rel-8.
Feature: Operations, Administration, Maintenance & Provisioning (OAM7) Unique_ID: 35041 5
BB: Network Infrastructure Management (OAM7-NIM) Unique_ID: 35042 5
WT Enhance NRM to accommodate NGN (IMS as basis of the Next Generation Network) Un... |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 6 List of SA5 Release 7 specifications | Type
Number
Title
Rapporteur
TR
30.817
Telecommunication management; Project scheduling and open issues for SA5, Release 7
ZOICAS, Adrian
TS
32.101
Telecommunication management; Principles and high level requirements
TOCHE, Christian
TS
32.102
Telecommunication management; Architecture
BERGGREN, Tommy
TS
32.111-1
Telec... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 1 Scope | The scope of this Technical Report (TR) is to capture the results of a feasibility study on how to introduce a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference logical architecture for R’00.
With this separation in view, functional elements of the PS CN doma... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 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... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 3 Symbols and Abbreviations | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 3.1 Symbols | For the purposes of the present document, the following symbols apply:
Mp Interface between an SGSN server and a PS-MGW. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
cSGSN Control Serving GPRS Support Node
PS-MGW Packet Switching Media Gateway
SGSN server Serving GPRS Support Node server
xGGSN Extended Gateway GPRS Support Node |
997ad2510cb826711e63f644e1d2617f | 23.873 | 4 Introduction | This technical report (TR) was created in order to study a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference architecture for R’00. As different approaches can be considered for achieving this goal, the following sections describe and analyse a few alternativ... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 5 Reference Logical Architecture | This chapter describes a reference architecture which we use as a basis for the evolved architecture.
The full view of Release 2000 architecture (as specified in 3G TR 23.821) is the reference logical architecture for this TR and is provided in figure 1.
Figure 1: Reference logical architecture |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6 Alternative 1: SGSN Server – PS Media Gateway Approach | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.1 Introduction | In the PS CN domain the node that comprises the more user and control plane functions is undoubtedly the SGSN. It is therefore judicious to consider the SGSN as the primary target for a split of its user and control plane functions.
This approach consists in decomposing the SGSN into an SGSN server and a PS media gatew... |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2 Logical Architecture | The logical architecture for this approach, as an evolution of the reference logical architecture, is depicted in figure 2.
Figure 2: Evolved logical architecture with SGSN server and PS-MGW
NOTE: Putting SGSN server and 2G-SGSN in the same node is an implementation option. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1 Functional Nodes | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1.1 SGSN Server | The SGSN server is the main control node for GPRS. It handles all the signalling interfaces of an SGSN, including the GTP-C protocol on the Gn and Gp interfaces and the RANAP protocol on the Iu interface. The SGSN server controls the PS Media Gateway (PS-MGW) through the Mp interface. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1.2 2G-SGSN | This evolved architecture has no impact on the 2G-SGSN. A 2G-SGSN is necessary to support the Gb interface. The Gn interface of a 2G-SGSN supports both user and control data. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.