id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 212
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
25.905
|
Feasibility study on improvement of the Multimedia Broadcast/Multicast Service (MBMS) in UTRAN
|
TR
|
7.2.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.905/25905-720.zip
|
The present document summarizes the work done under the study item "Improvement of the Multimedia Broadcast Multicast Service (MBMS) in UTRAN" defined in [1] by listing technical concepts addressing the objectives of the study item, analysing these technical concepts and recommending a way forward of the study item.
|
25.921
|
Guidelines and principles for protocol description and error handling
|
TR
|
7.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.921/25921-700.zip
|
The present document provides a guideline for protocol specification of UMTS stage 2 and 3 including the usage of formal languages and rules for error handling. The present document covers control-plane and user-plane protocols specified in TSG-RAN such as RRC, RLC, RANAP, RNSAP, NBAP, PCAP, and SABP.
|
25.922
|
Radio resource management strategies
|
TR
|
7.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.922/25922-710.zip
|
The present document shall describe RRM strategies supported by UTRAN specifications and typical algorithms.
This report is a release independent report. This means that the latest release applicable to 3GPP is the reference that this TR is defined upon, and contains information on all previous releases. Actual release where a given example applies is indicated in the relevant section.
|
25.999
|
High Speed Packet Access (HSPA) evolution; Frequency Division Duplex (FDD)
|
TR
|
7.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.999/25999-710.zip
|
The present document has been produced in the scope of the study item on "HSPA Evolution" [2]. The objective of the study item is to develop a framework for the evolution of the FDD mode of the 3GPP HSPA WCDMA-based radio-access technology beyond Release 7.
The present document lists the constraints for the FDD HSPA Evolution beyond release 7 and an assessment of technical proposals and their respective, achievable performance and complexity.
|
29.427
|
TISPAN; Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched CS) networks [3GPP TS 29.163 (Release 7), modified]
|
TS
|
7.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.427/29427-710.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 29.163 (V7.1.0) [1].
The clauses 7.2.3 and 7.4 of 3GPP TS 29.163 [1] specify the signalling interworking between ISDN User Part (ISUP) protocols and SIP in order to support services that can be commonly supported by ISUP and SIP-based network domains.
The clause 9.2.3.3.5 specifies how ringing tone is applied at the gateway when interworking ISUP and SIP.
The present document specifies the principles of interworking between the ETSI TISPAN IMS and ISUP based legacy CS networks, in order to support IM basic voice calls, therefore all the references to interworking between IMS and BICC are out of scope of the present document.
The present document is a protocol interworking specification; therefore all references to the user plane interworking are out of scope of the present document.
The present document specifies the interworking between ETSI SIP profile (as specified within ES 283 003 [3]) and ISUP, as specified in EN 300 356-1 [2] respectively.
|
29.800
|
Signalling System No. 7 (SS7) Security Gateway; Architecture, functional description and protocol details
|
TR
|
7.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.800/29800-700.zip
|
The present document is a temporary container for the functional description of the SS7 Security Gateway. The document covers also network architecture, routeing considerations, and protocol details. The contents of this report when stable will be moved into a Technical Specification 3GPP TS ab.cde. At the same time specific material related to MAPsec will be removed from 3GPP TS 29.002 [1].
|
29.801
|
Feasibility study of using M2PA in 3GPP networks
|
TR
|
7.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.801/29801-700.zip
|
The present document provides a study into the advantage and disadvantage of M2PA comparing with M3UA and provides a study into the possibility of introducing M2PA in 3GPP.
The present document also specifies the functionalities required on the protocol level to meet the requirements of BICC, MAP and CAP.
If necessary, the interactive between M2PA and M3UA should be studied.
|
29.802
|
(G)MSC-S - (G)MSC-S Nc Interface based on the SIP-I protocol
|
TR
|
7.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.802/29802-700.zip
|
The present document provides a study into providing a SIP-I based Nc interface (G)MSC-S - (G)MSC-S as an alternative to the existing BICC definition. The document covers the functional description, network architecture and protocol definition for the SIP-I based solution. The contents of this report when stable shall be moved into a Technical Specification 3GPP TS ab.cde along with modifications to existing specifications.
|
29.814
|
Bandwidth saving at Nb interface with IP transport
|
TR
|
7.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.814/29814-710.zip
|
The present document investigates solutions for a simple, optional transport format for the Nb interface and IP transport that allows transporting several RTP/NbFP/codec payload PDUs of different user plane connections within one packet. The solution shall minimise impacts to existing network characteristics, in particular jitter and packet delay. The transport format shall be suitable for any type of payload transported within NbFP. Though primarily intended and possibly optimised for NbFP transport within 3GPP circuit-switched core networks, the multiplexing design shall be generic and future proof by not precluding support of non-NbFP payload types, e.g. standard VoIP bearers or other interfaces such as Iu.
Furthermore, backward compatible signalling extensions required to negotiate the use of this transport option, to set up multiplexing connections, and to assign bearers to these connections are investigated.
The benefits and drawbacks of multiplexing at the Nb interface are investigated.
|
30.302
|
1.28 Mcps TDD enhanced uplink: RAN WG2 Stage 2 decisions
|
TR
|
7.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.302/30302-710.zip
|
This document is a Technical Report which captures the Stage 2 decisions on the support of 1.28 Mcps TDD Enhanced Uplink in UTRA.
|
30.817
|
Telecommunication management; Project scheduling and open issues for SA5, Release 7
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.817/30817-700.zip
|
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.
Status list of Work items can be found at the end of the present document.
List of SA5 Release 7 specifications can be found at the end of the present document.
The SA5 Release 7 work has been started in September 2005 and finished in June 2007.
|
32.806
|
Telecommunication management; Application guide for use of Integration Reference Points (IRPs) on peer-to-peer (p2p) interface
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.806/32806-700.zip
|
The present document shows how P2P horizontal interfaces can be added to the existing Telecommunication Management (TM) architecture and how existing Integration Reference Points (IRPs) can be applied to this architecture.
|
32.809
|
Telecommunication management; Feasibility study of XML-based (SOAP/HTTP) IRP solution sets
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.809/32809-700.zip
|
This present document is for the requested 3GPP Release 7 Work Item “XML-based (SOAP/HTTP) IRP Solution Set".
The purpose of the present document is to give TSG SA5 some arguments, through a survey work, about the need to specify a new Solution Set for all Interfaces, Network Resource Models and Data Definition IRPs based on XML-based (SOAP/HTTP) technology, as additional choice to CORBA and CMIP Solution Sets.
This document is intended to gather all information in order to provide a survey work on XML-based (SOAP/HTTP) Solution Set, based on the following sections:
(1) XML-based Solution Set technical introduction
(2) Business Status: Reasons
(3) Standardization Status
(4) Vendor Status
(4) Performance status:
(5) Economic Status
|
32.810
|
Telecommunication management; Information model Integration Reference Point (IRP) Study
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.810/32810-700.zip
|
The present document is focused on studying IRP Information Modelling to increase the interoperability of IRP based systems. The documents comprising conceptual overview, business case, Use Cases and Requirements. The findings and proposals of the study may be used to help generate new Technical Specifications (TS) and/or enhance existing Technical Specifications.
|
32.811
|
Telecommunication management; Itf-N performance criteria: Requirements
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.811/32811-700.zip
|
The present document provides the overall performance criteria for all Integration Reference Point (IRP) specifications produced by 3GPP.
Relevant IRP overview and high-level definitions are provided in 3GPP TS 32.101 [1], 32.102 [2] and 32.150 [3].
|
32.812
|
Telecommunication management; Itf-N Implementation Conformance Statement (ICS) template
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.812/32812-700.zip
|
The present document provides a template for Itf-N Implementation Conformance Statement (ICS) implementation conformance test. It defines the structure and table format for the ICS on the IS and CORBA SS level.
The intention is that:
a) For each IRP IS and CORBA SS specification version, for which an operator wishes to purchase an implementation of, a specific ICS document should be produced following the template herein (where each generic subclause number should be replaced by real numbers reflecting the structure in that IRP specification), and
b) For each Itf-N product offered or provided to support one or more IRP specifications, the vendor should fill in each applicable field of the tables in the ICS document(s) relevant for that/those IRP specifications and provide it to the customer.
|
32.814
|
Telecommunication management; UTRAN and GERAN Key Performance Indicators (KPI)
|
TR
|
7.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.814/32814-700.zip
|
The present document details a proposal to create Key Performance Indicators for UTRAN and GERAN networks, using performance measurements defined in the 32.4xx series specifications (any exceptions are noted in the KPI definitions).
The KPIs detailed in sections 4 & 5 are an output from the CO-OP initiative (A co-operative effort by eight network equipment providers) [8].
The KPIs detailed in section 6 are an example of an alternative high level KPI definition method that does not rely on standardised counter definitions. A draft KPI template is also described.
The KPI definitions in this Technical Report are intended as input to 3GPP for information and further study in the possible creation of a 3GPP Technical Specification.
|
33.803
|
Coexistence between TISPAN and 3GPP authentication schemes
|
TR
|
7.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.803/33803-700.zip
|
The present document studies from a security point of view the coexistence between TISPAN authentication methods (as specified in TISPAN release 1) and existing 3GPP authentication schemes, i.e. both the IMS AKA (as specified in TS 33.203 [5] and TS 24.229 [4]) and the early IMS security (as specified in TR 33.978 [6]). This document also aims to provide solutions to handle potential compatibility issues. These issues are listed in detail in section 5 of this document.
This document is meant to ensure that the same IMS core network entities can be used to support both 3GPP and TISPAN authentication schemes. In this context, rules are developed how an x‑CSCF can decide from a registration request which authentication scheme to apply. If these rules are not adhered to compatibility problems may arise.
|
33.918
|
Generic Authentication Architecture (GAA); Early implementation of Hypertext Transfer Protocol over Transport Layer Security (HTTPS) connection between a Universal Integrated Circuit Card (UICC) and a Network Application Function (NAF)
|
TR
|
7.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.918/33918-700.zip
|
The present document gives guidance on how to perform an early implementation of HTTPS connections between a UICC-based application and a Network Application Function in the Generic Authentication Architecture (GAA).
|
33.920
|
SIM card based Generic Bootstrapping Architecture (GBA); Early implementation feature
|
TR
|
7.5.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.920/33920-750.zip
|
The present document describes which change requests are to be implemented in addition to the Release 6 specifications TS 33.220 [1], TS 29.109 [2], and TS 24.109 [3] to enable the usage of 2G GBA.
|
33.978
|
Security aspects of early IP Multimedia Subsystem (IMS)
|
TR
|
7.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.978/33978-700.zip
|
The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain.
|
22.800
|
IP Multimedia Subsystem (IMS) subscription and access scenarios
|
TR
|
6.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.800/22800-600.zip
|
This document studies scenarios between subscribers and operators, mainly from IMS subscriptions point of view and verifies the compatibility of the possible scenarios within 3GPP Scope. Release 6 includes several work items like IMS enhancements, WLAN interworking that needs to be better understood so that clear requirement can be agreed and relevant technical specifications can be developed in time.
The document will identify the requirements arising from the following issues:
• Identification of requirements for 3GPP operators to implement only some of 3GPP system domains? (For example an IMS system separated from the PS domain and access network. What is the relationship between the AN/CN/IMS networks in this case? Are there conflicts in privacy issues due to several subscriptions?)
• Operator control of networks used to access / provide IMS services. For example operator may want to limit the subscriber to access the IMS via a specific 3GPP access network.
• Non-3GPP access network implications.
• Simultaneously access to IMS by one user with multiple devices. .
• UE functionality split (if any implications).
• Deployment of UICC with several USIM and ISIM applications from different parties.
• Analyse aspects of user interaction when activating USIM and ISIM applications on the UICC (e.g. manually, automatically, PIN, NON-PIN).
Below issues need to be described in scenarios :
• Generic issues
• Security
• Charging
• Privacy
• Roaming
• Regulatory (e.g lawful interception) etc.
• Quality of service
• User experience
Further TR needs to translate the scenarios, which fit in the scope of the 3GPP system to 3GPP service requirements.
Criteria for requirements to be included:
1. In scope with 3GPP access (UTRAN, GERAN) or access that 3GPP has specified interworking with (WLAN).
2. In scope with 3GPP core network(s).
3. In scope with 3GPP enabling technologies.
4. Scope of this work is limited to identify service requirements derived from scenarios capturing various business requirements. No architectural solutions will be considered in this TR.
Note: 3GPP should not place requirements, which would prohibit the possibility to use non-3GPP defined access for IMS.
Note: The SA2 within its own documentation shall look into technical feasibility and architecture implications of scenarios and requirements defined by SA1 and contact SA3 and SA5 for deeper technical understanding if necessary. Overall architecture implications shall consider also UICC implications (e.g. if it is appropriate to have several ISIMs on one UICC and possibility of having empty field for either ISIM or USIM in a UICC.?) and accordingly contact T3 for deeper technical understanding if necessary.
|
22.857
|
Run-time independent framework feasibility study
|
TR
|
6.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.857/22857-600.zip
|
The present document is a technical report consisting of a benefits analysis and a feasibility study on the creation of a framework enabling the application of MExE to arbitrary runtime environments.
|
23.125
|
Overall high level functionality and architecture impacts of flow based charging; Stage 2
|
TS
|
6.8.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.125/23125-680.zip
|
The present document specifies the overall high level functionality and architecture impacts of Flow Based Charging.
|
23.140
|
Multimedia Messaging Service (MMS); Functional description; Stage 2
|
TS
|
6.16.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-6g0.zip
|
The present document defines the stage 2 and stage 3 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1.
The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
The present document contains the core functions for a non realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service.
MMS uses a number of technologies to realise the requirements of the stage 1 description (3G TS 22.140) [1]. The present document describes how the service requirements are realised with the selected technologies. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realisation of the Multimedia Messaging Service.
The present document serves as a foundation for the development of MMS. It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world. In consequence readers may find that certain aspects are not clearly defined or open to misinterpretation. Where any such case is encountered it is essential that the issue is brought to the 3GPP TSG T2 standards body (see page 2 for contact information) for discussion and resolution in order to provide interoperable implementations.
|
23.841
|
Presence service architecture
|
TR
|
6.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.841/23841-600.zip
| |
23.846
|
Multimedia Broadcast/Multicast Service (MBMS); Stage 2
|
TR
|
6.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.846/23846-610.zip
|
The present document discusses architectural issues and describes functionalities required for the Multimedia Broadcast/Multicast Service. MBMS requirements are discussed in [2] and it is the intention of this document to present one or more alternatives to achieving the required functionality within 3GPP networks.
|
23.851
|
Network sharing; Architecture and functional description
|
TR
|
6.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.851/23851-610.zip
|
In the current mobile telephony marketplace, functionality that enables various forms of network sharing is becoming more and more important. These aspects have not really been addressed in either 2G or 3G systems, although there is functionality that supports a very basic type of network sharing in the current specifications within 3GPP. In [1], 3GPP has studied service requirements and functionality necessary for supporting a standardized network sharing.
The present document discusses issues and describes functionalities required for Network Sharing as outlined in [1]. The intention is to present one (or more) architectural alternatives for achieving the required functionality within a 3GPP network. An important part of the work is to adapt the network functionality so that supporting mobile telephones that do not have any of the possibly new functionality being introduced for network sharing support can be handled in a more efficient way than in pre-Rel-6 networks.
|
23.877
|
Architectural aspects of speech-enabled services
|
TR
|
6.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.877/23877-600.zip
|
The purpose of this technical report is to analyse the service requirements for speech enabled services as defined in 3GPP TS 22.243 Speech recognition framework for automated voice services; Service aspects (Stage 1).
The service requirements on Speech Enabled Services defined in TS 22.243 may place architectural requirements on the CS and PS domains and the IMS. Additionally various techniques for improving speech recognition performance may be identified which have architectural impact.
The objective of TR is to document these architectural impacts.
|
23.895
|
Provision of UE specific behaviour information to network entities
|
TR
|
6.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.895/23895-620.zip
|
This TR studies different possible mechanisms to provide the 3GPP network entities with UE Specific Behavior Information (UESBI). UESBI is used by correcting mechanisms to overcome some of the issues that will be recognized by 3GPP in TR 25.994 and other such documents. The description of these correcting mechanisms is out of the scope of this TR.
A comparison of the pros and cons of the different architectures is included, however, the TR is not expected to make a decisive conclusion. Instead, the TSG plenary meetings are expected to use this TR to recommend how to proceed with further work.
|
23.941
|
3GPP Generic User Profile (GUP); Stage 2; Data Description Method (DDM)
|
TR
|
6.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.941/23941-600.zip
|
The present document is the Stage Two description for the Data Description Method (DDM) and the Datatype Definition Method (DtDM) of the 3GPP Generic User Profile.
The present document specifies the method for describing the logical structure of the data description, Generic User Profile, Profile Components, methods for describing Datatypes and other constructs for use in 3GPP. The GUP data description method is designed to coexist with other data description technologies.
The document includes:
• DDM and DtDM features and definition;
• Process and procedures for administration of GUP/DDM and 3GPP TS 24.241 [12].
|
24.841
|
Presence service based on Session Initiation Protocol (SIP); Functional models, information flows and protocol details
|
TR
|
6.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.841/24841-600.zip
|
The present document is a temporary container for the functional models, flows and protocol details for the presence service within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP Events. Where this is not possible, extensions to SIP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
The present document includes information applicable to network operators, service providers and manufacturers.
Editor's note: Agreed material is held in this TR for an interim period of time. This has the advantage that:
It creates a location where the material may stabilise outside a document under CR control, thus fulfilling the function of the original annexes in the IN CN subsystem documents.
This TR will not be published.
|
25.309
|
FDD enhanced uplink; Overall description; Stage 2
|
TS
|
6.6.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.309/25309-660.zip
|
The present document is a technical specification of the overall support of FDD Enhanced Uplink in UTRA.
|
25.801
|
Feasibility study for improved access to User Equipment (UE) measurement data for Controlling Radio Network Controller (CRNC) to support Time Division Duplex (TDD) Radio Resource Management (RRM)
|
TR
|
6.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.801/25801-600.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to study aspects of improving CRNC access to UE measurements in preparation for a WI on this topic, as proposed in [1].
As requested by TSG-RAN, the document describes the consequences of the CRNC not having access to UE measurements in the case that the serving RNC does not match the controlling RNC, additionally it studies the complexity of the proposed solutions so that an evaluation of the incremental gain of a solution can be weighed against its additional complexity.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.803
|
S-CCPCH performance for Multimedia Broadcast/Multicast Service (MBMS)
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.803/25803-600.zip
|
The scope of this technical report is to capture simulation results for S-CCPCH operation in the context of MBMS as defined in [1].
It is important to note that the results presented in this report are raw simulation results and as such do not include any implementation margins which are typically considered when defining UE performance requirements and would have to be considered when dimensioning network resource required for MBMS deployment.
|
25.804
|
Feasibility study on uplink enhancements for UTRA TDD
|
TR
|
6.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.804/25804-610.zip
|
This present document details and compares proposed enhancements to the UTRA TDD uplink in terms of gains and complexity and draws conclusions on future work.
This document is the technical report for the Release 6 study item "Uplink Enhancements for UTRA TDD" [1]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential enhancements under consideration and compare the benefits of each enhancement with earlier releases for improving the performance of the UTRA TDD uplink, along with the complexity evaluation of each technique. The scope is to either enhance uplink performance in general or to enhance the uplink performance for background, interactive and streaming based traffic.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
|
25.807
|
Low output powers for general purpose Frequency Division Duplex (FDD) Base Station (BS)
|
TR
|
6.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.807/25807-600.zip
| |
25.808
|
FDD enhanced uplink; Physical layer aspects
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.808/25808-600.zip
|
The present document captures the agreements of the different techniques for FDD Enhanced Uplink, namely the support of Node B controlled scheduling, hybrid ARQ and shorter TTI, with regards to the overall support of UTRA FDD Enhanced Uplink.
The technical objective of this work item is the Enhanced Uplink functionality in UTRA FDD, to improve the performance of uplink dedicated transport channels.
|
25.862
|
RAB support for IMS
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.862/25862-600.zip
|
This document captures an analysis of the RABs that can be used in Release 5 in support of IMS, and different optimization proposals to improve the support of IMS in Release 6 or later.
The report may also serve as a basis to define test configurations to be incorporated in RAN5 for the test of IMS.
The report emphasises VoIP specifically, since it is where the optimization is most needed when comparing a non optimized IMS speech call and a R99 CS speech call.
|
25.887
|
Beamforming enhancements
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.887/25887-600.zip
|
The scope of this TR is to define potential measurements for UTRA FDD and their performance requirements for efficient support of RRM in case beamforming is used in UTRAN.
|
25.888
|
Improvement of inter frequency and inter system measurement for 1,28 Mcps TDD
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.888/25888-600.zip
|
In order to improve monitoring other RAT systems or performing inter-frequency measurements in 1.28 Mcps TDD , the channel re-assigning scheme with signaling support and other possible solutions are proposed and investigated, potentially allowing the UE to have a longer measurement window or to avoid possible measurement failures.The purpose of this document is to help the TSG RAN WG1, WG2, WG3 and WG4 to understand potential benefits with respect to the respective study areas, to investigate the proposed method and to identify the impacts to current specifications, which is needed for the introduction of the improvement of inter-frequency and inter-system measurement for1.28 Mcps TDD.
The different study areas will be described in subsequent chapters.
It is intended to gather all information in order to trace the history and the status of the SI in each WGs.
The TR should:
• describe the proposed methods for each study area.
• describe the impacts due to this SI.
• describe agreed requirements related to the SI.
• identify the affected specifications according to the introduction of inter frequency and inter system measurement for 1.28 Mcps TDD and
• also describes the schedule of the SI.
|
25.889
|
Feasibility study considering the viable deployment of UTRA in additional and diverse spectrum arrangements
|
TR
|
6.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.889/25889-600.zip
|
The present document summarises results from the Study Item “Feasibility Study considering the viable deployment of UTRA in additional and diverse spectrum arrangements”. Both UTRA FDD and UTRA TDD are considered. For UTRA FDD, the spectrum arrangements include the present FDD frequency bands as defined in Release 5 of the relevant 3GPP specifications as well as the additional bands identified for IMT-2000 by ITU-R WRC-2000, in particular the band 2500-2690 MHz. For UTRA TDD, the study focuses on the use of the additional band 2500-2690 MHz.
|
25.892
|
Feasibility study for Orthogonal Frequency Division Multiplexing (OFDM) for UTRAN enhancement
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.892/25892-600.zip
|
The scope of this Study Item is to consider the performance of OFDM in the mobile environment and to consider scenarios in which OFDM may be introduced in UTRAN 3GPP based systems. This activity involves the Radio Access work area of the 3GPP studies and has some effect on the Mobile Equipment and Access Network of the 3GPP systems.
The aims of this study are:
- to consider the advantages that may be gained by introducing a new modulation technique in 3GPP RAN systems,
- to estimate possible benefits and complexity and
- to recommend to 3GPP RAN if further standardisation development work should be undertaken by 3GPP.
As a starting point, OFDM will be considered in the downlink only. It should be possible to operate in a 5MHz spectrum allocation i.e. coupled with W-CDMA in the uplink for a 2*5MHz deployment scenario.
The following list provides examples of areas that are to be considered in the study:
- Throughput for data services . To be compared with throughput of current UTRAN releases;
- Complexity aspects of multimode UEs supporting both OFDM and release 99/release 5 UMTS;
- Deployment scenarios including frequency re-use aspects within diverse spectrum allocations;
The study should consider performance aspects, aspects linked to the evolution of UMTS (high level architecture, diverse spectrum arrangements and allocations), impacts on signalling in UTRAN , aspects of capacity/cost/complexity/coverage and aspects of co-existence with the existing UMTS modes.
The purpose of the study is to consider the feasibility of introducing OFDM in UTRAN and to compare OFDM performance with HSDPA. The analysis of OFDM performance and its comparison with reference HSDPA performance should be based on a basic OFDM design (often referred as textbook OFDM). More elaborate OFDM techniques should not be considered. However the use of text book OFDM in the feasibility study phase does not restrict the design when moving to the specification phase. It is a study of physical layer aspects only and does not include changes in UTRAN architecture. Changes are to be restricted to the physical layer and not extend beyond those needed to support an additional modulation. Principles as provided in TS 25.302 (Services provided by the physical layer) are to be respected where possible.
This study item was approved by the TSG RAN#16 (Marco Island Fl USA 4th – 7th June 2002).
|
25.895
|
Analysis of higher chip rates for UTRA TDD evolution
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.895/25895-600.zip
| |
25.896
|
Feasibility study for enhanced uplink for UTRA FDD
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.896/25896-600.zip
|
This present document is the technical report for the Release 6 study item “Uplink Enhancements for Dedicated Transport Channels”(see [1]).
The purpose of this TR is to help TSG RAN WG1 to define and describe the potential enhancements under consideration and compare the benefits of each enhancement with earlier releases for improving the performance of the dedicated transport channels in UTRA FDD uplink, along with the complexity evaluation of each technique. The scope is to either enhance uplink performance in general or to enhance the uplink performance for background, interactive and streaming based traffic.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information in order to compare the solutions and gains vs. complexity, and draw a conclusion on way forward.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
25.899
|
High Speed Downlink Packet Access (HSDPA) enhancements
|
TR
|
6.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.899/25899-610.zip
|
The present document is the technical report on HSDPA (High Speed Downlink Packet Access) Enhancements for Release 6 under the study item: “Radio link performance enhancement”. This TR describes enhancement technologies proposed as candidates of the improvement on HSDPA physical layer. It reports system performance gain and/or other beneficial points for each proposal. It also reports the complexity and some points changed from Release 5 to easily understand the benefits of new technologies. Furthermore, the impacts on the specification in other than physical layer are clarified.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
|
29.140
|
Multimedia Messaging Service (MMS); MM10 interface based on Diameter protocol; Stage 3
|
TS
|
6.4.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.140/29140-640.zip
|
The present document defines the procedures and the transport protocol for use in the Multimedia Messaging Service (MMS) based on Diameter.
The present document is applicable to:
- The MM10 interface between an MMS Relay/Server and the MSCF.
Whenever it is possible this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within this document.
|
29.207
|
Policy control over Go interface
|
TS
|
6.5.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.207/29207-650.zip
|
The present document provides the stage 3 specification of the Go interface. The functional requirements and the stage 2 specifications of the Go interface are contained in 3GPP TS 23.002 [2] and 3GPP TS 23.207 [3]. The Go interface is the interface between the GGSN and the Policy Decision Function (PDF).
The present document defines:
- the protocol to be used between PDF and GGSN over the Go interface;
- the signalling interactions to be performed between PDF and GGSN over the Go interface;
- the information to be exchanged between PDF and GGSN over the Go interface.
|
29.208
|
End-to-end Quality of Service (QoS) signalling flows
|
TS
|
6.7.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.208/29208-670.zip
|
The present specification gives examples of QoS signalling flows for resource reservation to provide end-to-end QoS. The flows are used as bases of developing QoS related protocol descriptions for new and existing specifications.
The present specification adds detailed flows of Service Based Local Policy (SBLP) procedures over the Go and Gq interfaces and their relationship with the bearer level signalling flows over the Gn interface.
The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in TS 29.207 [7] shall be taken into consideration.
The present specification also describes the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
|
29.209
|
Policy control over Gq interface
|
TS
|
6.8.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.209/29209-680.zip
|
The present document provides the stage 3 specification of the Gq interface. The functional requirements and the stage 2 specifications of the Gq interface are contained in 3GPP TS 23.002 [2] and 3GPP TS 23.207 [3]. The Gq interface is used for session based policy set-up information exchange between the Policy Decision Function (PDF) and the Application Function (AF).
Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
|
29.210
|
Charging rule provisioning over Gx interface
|
TS
|
6.7.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.210/29210-670.zip
|
The present document provides the stage 3 specification of the Gx reference point. The functional requirements and the stage 2 specifications of the Gx reference point are contained in 3GPP TS 23.125 [3]. The Gx reference point is for provisioning service data flow based charging rules between the Traffic Plane Function (TPF) and the Charging Rules Function (CRF), also known as Service Data Flow Based Charging Rules Function.
The present document defines:
- the protocol to be used between TPF and CRF over the Gx reference point;
- the information to be exchanged between TPF and CRF over the Gx reference point.
Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
3GPP TS 29.211 [15] provides callflows for Flow Based Charging, covering the signalling on the Gx reference point.
|
29.211
|
Rx Interface and Rx/Gx signalling flows
|
TS
|
6.4.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.211/29211-640.zip
|
The present document provides the stage 3 specification of the Rx reference point interface.
The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.125 [2]. The Rx reference point is used to exchange Flow Based Charging information between the Charging Rules Function (CRF) and the Application Function (AF).
Whenever it is possible the present document specifies the protocol by reference to specifications produced by the IETF within the scope of Diameter and to the Gq specification 3GPP TS 29.209 [4].
The present specification also provides detailed signalling flows for FBC procedures over the interfaces that correspond to Rx and Gx reference points.
|
29.846
|
Multimedia Broadcast/Multicast Service (MBMS); CN1 procedure description
|
TR
|
6.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.846/29846-600.zip
|
The present document discusses procedures required in the Core Network to support the Multimedia Broadcast/Multicast Service (MBMS) requirements that are outlined in 3GPP TS 22.146 [2] within the architectural solutions discussed in 3GPP TS 23.246 [3].
|
29.847
|
Conferencing based on SIP, SDP, and other protocols; Functional models, information flows and protocol details
|
TR
|
6.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.847/29847-600.zip
|
The present document is a temporary container for the functional models, flows and protocol details for the conferencing service within the IP Multimedia Core Network subsystem (IMS) based on the Session Initiation Protocol (SIP), SIP Events, the Session Description Protocol (SDP) , the Conference Policy Control Protocol (CPCP) and other protocols. The document covers also instant messaging conferences. The contents of this report when stable will be moved into the Technical Specification 3GPP TS 23.218 [3], 3GPP TS 24.228 [4] and 3GPP TS 24.229 [5].
Editor's note: This TR will also include information on conference floor control, which will be using different protocols than SIP and SDP (see clause 9), as e.g. described in draft-wu-sipping-floor-control-04.txt. This information might be moved either to TS 24.229 or to another 3GPP document.
Editor's note: The "other protocols" that are mentioned here need to be listed in detail, in order to replace the phrase "other protocols". This TR only covers protocols in the scope of CN1.
Editor's note: The work on instant messaging conferences is related to the work under the work item for IMS messaging, WID 11039, and the decision is to be made on contributed text as in which document it will appear.
Editor's note: The ongoing work on floor control and conferencing in CN5 needs to be taken into account.
This document does not cover the signalling between a MRFC and a MRFP.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SIP Events, SDP and other protocols. Where this is not possible, extensions to SIP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
The present document includes information applicable to network operators, service providers and manufacturers.
Editor's note: Agreed material is held in this TR for an interim period of time, and the material transferred into release 6 versions of 23.218, 24.228 and 24.229 at a later time. This has the advantage that:
It creates a location where the material may stabilise outside a document under CR control, thus fulfilling the function of the original annexes in the IN CN subsystem documents.
It avoids the need to create release 6 mirror CRs for all release 5 changes to the IM CN subsystem.
This TR will not be published.
|
29.903
|
Feasibility Study on SS7 signalling transport in the core network with SCCP-User Adaptation (SUA) layer
|
TR
|
6.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.903/29903-600.zip
|
The scope of this Technical Report (TR) is to capture the results of a feasibility study on SS7 signalling transport (e.g. MAP & CAP) in a 3GPP core network with SCCP-User Adaptation (SUA) for Release-5.
With this purpose in mind, this TR evaluates the advantages and disadvantages associated with the implementation of SUA in the core network, and compares it with the SCCP/M3UA option. Therefore, an overview of M3UA is provided in this document for reference. This TR covers all scenarios such as SUA peer to peer as well as interworking with legacy SS7 network, plus the interworking between SUA and SCCP/M3UA. This TR also identifies and studies the technical issues related to SUA implementation and proposes the possible technical solutions that will enable the effient implementation of SUA, with minimum impacts on the available services.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the core network signalling. At the end of the feasibility study, the open issues are reported and their importance is assessed. Also discussed are the benefits and drawbacks with respect to the introduction of SUA into 3GPP core network signalling.
|
29.962
|
Signalling interworking between the 3GPP profile of the Session Initiation Protocol (SIP) and non-3GPP SIP usage
|
TR
|
6.1.1
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.962/29962-611.zip
|
The present document investigates the SIP signalling interworking between entities of IM CN subsystems behaving as specified in the 3GPP profile of SIP and SDP in 3GPP TS 24.229 [1], with related call flow examples in 3GPP TS 24.228 [2], and SIP network entities external to the IM CN subsystems, which may not adhere to the 3GPP profile of SIP and SDP.
The present document assumes that GPRS access and service based local policy using the Go interface is applied.
Non-GPRS access to IMS may have implications on the TR, which are not yet discussed.
The considered SIP network entities external to the IM CN subsystems may feature different SIP capabilities, such as the support of arbitrary SIP options.
The document focuses on scenarios where the non-3GPP UA does not support one or more of the following SIP extensions:
Preconditions: "Integration of Resource Management and SIP" RFC 3312 [5];
Update: "The Session Initiation Protocol UPDATE Method" RFC 3311 [7];
100rel: "Reliability of Provisional Responses in SIP" RFC 3262 [6].
The present document focuses on the preconditions, the update and 100rel extensions because only these extensions imply interworking issues since they require the end-to-end cooperation of both UAs.
Security interworking may also have implications on the TR, which are not yet discussed.
The present document does not make any a priori assumptions where a possible interworking is performed within the IM CN subsystem. Any SIP network entity within the IM CN subsystem may take part in the interworking. The network entities that may become involved in a certain interworking topic are identified for each of these topics separately.
The present document features a discussion of topics, where an interworking is possibly required. Aspects of the 3GPP profile of SIP and SDP, which obviously do not require any interworking, are not discussed. An assessment of the impact and probability of occurrence of the discussed scenarios is also provided.
Problems due to network elements within the IM CN subsystem, which do not or only partly satisfy the 3GPP profile of SIP and SDP, in particular non 3GPP compliant SIP UAs, are out of scope of the present document.
The present document is dedicated exclusively to issues inherent in the SIP and SDP signalling. Related topics in a wider sense, such as IPv6 to IPv4 address translation or user plane transcoding are out of scope.
For brevity, in what follows the above SIP extensions are only mentioned if a SIP UA does not make use of them. Otherwise, it is understood that the UA makes use of them.
|
29.998-06
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User Location and User Status Service Mapping to MAP
|
TR
|
6.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06/29998-06-600.zip
|
The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
30.902
|
Guidelines for the modification of the Mobile Application Part (MAP) in Phase 2+
|
TR
|
6.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.902/30902-600.zip
|
After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects.
|
32.111-4
|
Telecommunication management; Fault Management; Part 4: Alarm Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-4/32111-4-650.zip
|
The present document defines the alarm integration reference point for the CMIP solution set. In detail:
- clause 4 contains an introduction to some basic concepts of the CMIP interfaces;
- clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces;
- clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.111-2 (V6.3.X).
|
32.304
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.304/32304-611.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Notification Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.302 [3]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Notification Management over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.302 V6.2.X.
|
32.314
|
Telecommunication management; Generic Integration Reference Point (IRP) management; Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.314/32314-600.zip
|
The present document specifies the CMIP Solution Set (SS) for Generic Integration Reference Point (IRP) management whose capabilities are specified in Generic Integration Reference (IRP) management: Information Service (TS 32.312 [1]).
Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notifications, parameters and attributes defined in the IS onto their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the GDMO/ ASN.1 specification.
This Solution Set specification is related to TS 32.312 V6.0.X.
|
32.324
|
Telecommunication management; Test management Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.324/32324-600.zip
|
The present document specifies the CMIP SS for the Test Management IRP IS defined in 3GPP TS 32.322 [8].
In detail:
• Clause 4 provides the basic architectural concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in 3GPP TS 32.322 [8] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Test Management IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.322 (V6.0.X).
|
32.334
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.334/32334-620.zip
|
The present document specifies the CMIP SS for the Notification Log IRP IS defined in 3GPP TS 32.332 [8].
In detail:
• Clause 4 provides the basic architectural concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in 3GPP TS 32.332 [8] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Notification Log IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.332 (V6.2.X).
|
32.354
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.354/32354-600.zip
|
The present document specifies the CMIP SS for the Communication Surveillance IRP IS defined in 3GPP TS 32.352 [8]. In detail:
• Clause 4 provides the basic architectural concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in 3GPP TS 32.352 [8] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Communication Surveillance IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.352 (V6.0.X).
|
32.403
|
Telecommunication management; Performance Management (PM); Performance measurements; UMTS and combined UMTS/GSM
|
TS
|
6.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.403/32403-690.zip
|
The present document describes the measurements for UMTS and combined UMTS/GSM.
TS 32.401 [12] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. RNC related measurements);
- Header 2: Measurement function (e.g. soft handover measurements);
- Header 3: Measurements.
|
32.414
|
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.414/32414-610.zip
|
The present document defines the performance management integration reference point for the CMIP solution set. It provides all the GDMO and ASN.1 definitions necessary to implement the PM IRP Information Service (TS 32.412 [7]) for the CMIP interface. In detail:
- clause 4 contains an introduction to some basic concepts of the CMIP interfaces;
- clause 5 contains the GDMO definitions for the Performance Management over the CMIP interfaces;
- clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is based on 3GPP TS32.412 (v6.4.0).
|
32.604
|
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.604/32604-610.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Basic CM Integration Reference Point (IRP): Information Service defined in TS 32.602 [6]. In detail:
• Clause 4 provides the basic concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in TS 32.602 (Basic Configuration Management IRP: Information Service) [6] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Basic Configuration Management IRP over the CMIP interfaces,
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.602 V6.1.X.
|
32.614
|
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.614/32614-610.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Bulk CM Integration Reference Point (IRP): Information Service defined in TS 32.612 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.612 V6.2.X.
|
32.624
|
Telecommunication management; Configuration Management (CM); Generic network resources: Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.624/32624-620.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Generic Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.622 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.622 V6.4.X [4].
|
32.634
|
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.634/32634-620.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the CN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.632 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.632 V6.2.X [4].
|
32.644
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.644/32644-630.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the UTRAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.642 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.642 V6.4.X.
|
32.654
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.654/32654-610.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the GERAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.652 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.652 V6.0.X.
|
32.664
|
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.664/32664-620.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Kernel Configuration Management IRP: Information Service defined in 3GPP TS 32.662 [7]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Kernel Configuration Management IRPover the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.662 V6.3.X.
|
32.674
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.674/32674-610.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the State Management IRP: Information Service defined in 3GPP TS 32.672 [6]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the State Management IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set is related to 3GPP TS 32.672 V6.0.X [6].
|
32.714
|
Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.714/32714-600.zip
|
The purpose of this Transport Network (TN) interface Network Resource Model IRP: CMIP Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.712 [4]) to the protocol specific details necessary for implementation of this IRP in a Q3 environment.
This Solution Set specification is related to 3GPP TS 32.712 V6.0.X
|
32.744
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.744/32744-610.zip
|
The purpose of this STN Network Resources IRP: CMIP Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.742 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.742 V6.0.X.
|
32.803
|
Telecommunication management; Process guide; Use cases in Unified Modelling Language (UML)
|
TR
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.803/32803-600.zip
|
The present document is a guide for developing subscription management requirements in the form of use cases.
The present document is used to allow use case process information to be removed from 3GPP TS 32.140 on "Telecommunication management; Subscription Management (SuM) Requirements". It is intended that this applies only to the Subscription Management (SuM) work item in Release 6.
|
32.804
|
Telecommunication management; Control of Remote Electrical Tilting (RET) antennas; Requirements
|
TR
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.804/32804-620.zip
|
The present document defines the requirements for the network wide control of RET antennas via the Itf-N.
Two example types of RET antennas are those that are tilted using a mechanical tilting mechanism and those that use a phased array.
The control of RET antennas has been studied in 3GPP RAN3 with an approved work item for “Remote Control of Electrical Tilting Antennas” provided in RP-030193 at RAN#19 in March 2003, producing TR 25.802 [1].
The RET control mechanism makes use of the Iuant interface, which is defined in the following set of specifications for General Aspects and Principles [8], Layer 1 [9], Signalling Transport [10], and Remote Electrical Tilting (RET) Antennas Application Part (RETAP) Signalling [11].
The ability to control Antenna tilt permits cell size to be adjusted, thereby permitting control of up and downlink throughput.
The ability to control Antenna tilts remotely from a network management system permits a network wide perspective to be obtained and for settings to be adjusted in response to predicted population movements, or in response to performance monitoring data to help make the best use of the available radio access network.
Figure 1 shows the main Network Elements (NEs) and depicts the two system contexts A and B where the IRPagent may be located either in the Element Manager (EM), or within the Network Element (NE).
Figure 1
|
32.805
|
Telecommunication management; Process guide; Backward compatibility recommendations
|
TR
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.805/32805-600.zip
|
The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
Clause 2 provides the list of references. Clause 3 provides the definitions and abbreviations used in the document. Clause 4 specifies the Recommendations. Clause 5 describes the system context where the Recommendations are applicable.
|
32.815
|
Telecommunication management; Charging management; Online Charging System (OCS) architecture study
|
TR
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.815/32815-610.zip
|
The present document analyses the architectures and functions of the OCS and thereby derives the functionality of the OCS reference points. It is expected that the content of the present document will serve as a basis for detailed 3GPP specifications of reference points between the logical OCS functionalities. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
|
33.200
|
3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security
|
TS
|
6.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.200/33200-610.zip
|
This technical specification covers the security mechanisms and procedures necessary to protect the MAP protocol. The complete set of enhancements and extensions to facilitate security protection for the MAP protocol is termed MAPsec and it covers transport security in the MAP protocol itself and the security management procedures.
The security mechanisms specified for MAP are on the application layer. This means that MAPsec is independent of the network and transport protocols to be used.
This technical specification contains the stage-2 specification for security protection of the MAP protocol. The actual implementation (stage-3) specification can be found in the MAP stage-3 specification, TS 29.002 [4].
NOTE: It is explicitly noted that automated key management and key distribution is not part of Rel‑5. All key management and key distribution in Rel‑5 shall therefore be carried out by other means (see Annex A).
|
33.810
|
3G Security; Network Domain Security / Authentication Framework (NDS/AF); Feasibility Study to support NDS/IP evolution
|
TR
|
6.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.810/33810-600.zip
|
The scope of this feasibility study is limited to authentication of network elements which are using NDS/IP, and located in the inter-operator domain.
It means that this study concentrates on authentication of Security Gateways (SEG), and the corresponding Za‑interfaces. Authentication of elements in the intra-operator domain is considered as an internal issue for the operators. This is quite much in line with [6] which states that only Za is mandatory, and that the security domain operator can decide if the Zb-interface is deployed or not, as the Zb-interface is optional for implementation.
However, NDS/AF can easily be adapted to intra-operator use. This is just a simplification of the inter-operator case as all NDS/IP NEs and the PKI infrastructure belong to the same operator. Validity of certificates may be restricted to the operator's domain.
This work might also later be extended to provide entity authentication services to non-control plane nodes, but this has not been studied.
Possible use of multi-purpose PKI solutions (e.g. providing end-user security) for NDS/AF has not been studied. On the contrary, it is recommended to use a dedicated and profiled PKI for NE authentication in NDS/IP. Different applications make different demands on a PKI and it may make sense to build a lightweight PKI for each purpose rather than to build one that solves all problems. Complexity is one of the main impediments to PKI deployment today [11].
The NDS architecture for IP-based protocols is illustrated in figure 1.
Figure 1: NDS architecture for IP-based protocols [6]
|
33.817
|
Feasibility study on (Universal) Subscriber Interface Module (U)SIM security reuse by peripheral devices on local interfaces
|
TR
|
6.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.817/33817-610.zip
|
This Feasibility Study report conducts a threat analysis and determines the feasibility of Reuse of a Single SIM, USIM, or ISIM by peripheral devices on local interfaces to access multiple networks. Most important for this Reuse is the authentication and key agreement (AKA) function provided by these applications. The peripheral devices include 3GPP and WLAN devices that function as integrated or attachable peripherals on Laptops or PDAs or other mobile data devices. The multiple access networks of interest correspondingly include 3GPP and WLAN type networks. The objective of this study is to realize the diverse usage models with multiple external (wired or wireless) interfaces from a security point of view, without incorporating significant changes to the 3GPP and WLAN infrastructure. It also studies the impact on current security specifications for 3GPP, especially given that some issues have already been identified surrounding key setting procedures, USIM sequence number synchronization, UICC presence detection/UICC application presence detection and termination of the UICC usage etc. It also studies additional user authentication requirements (e.g. PINs) when used over local interfaces like Bluetooth, IR or USB. Further more it studies the impact on having many entities using the same security mechanism and any 3GPP core network elements. Reuse of security functions provided by applications on the UICC does not have an impact on ownership and control of the UICC, which remains with the issuer of the UICC. This Feasibility Study may be used as a basis for future CRs to TS 33.234 as and when any of the proposals are developed by SA WG3.
|
34.121
|
Terminal conformance specification, Radio transmission and reception (FDD)
|
TS
|
6.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-640.zip
|
The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself.
|
45.811
|
Uplink - Time Difference Of Arrival (U-TDOA) in GSM and GPRS
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.811/45811-600.zip
|
The following document describes how the Uplink Time Difference Of Arrival (U-TDOA) location method works in GSM and GPRS environments.
|
49.001
|
General network interworking scenarios
|
TR
|
6.0.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/49_series/49.001/49001-601.zip
|
The present document serves as an introduction to the GSM 09.xx‑series.
In clause 4, the technical requirements for Public Land Mobile Network (PLMN) interworking are introduced, and in clause 5 there is a summary of the contents of the GSM 09.xx‑series.
|
51.010-3
|
Mobile Station (MS) conformance specification; Part 3: Layer3 (L3) Abstract Test Suite (ATS)
|
TS
|
6.3.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-3/51010-3-630.zip
|
The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM/3GPP mobile stations (MS) conforming to the TSs for Layer 3, cell selection, Enhanced Full Rate Speech, Multi-band, GSM-R band (R-GSM) and ASCI (the voice group call service (VGCS), voice broadcast service (VBS), enhanced Multi-Level Precedence and Pre-emption service (eMLPP), User-to-user Signalling (UUS) service and the Follow Me service) for the digital cellular telecommunications systems.
The present document is valid for MS implemented according GSM Phase2 or Phase2+ R96, or R97, or R98, or R99, or 3GPP Release 4, or Release 5.
The test suite in the current document is an example of TTCN implementation, and is not intended for direct use in formal conformance testing.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications.
|
22.048
|
Security mechanisms for the (U)SIM application toolkit; Stage 1
|
TS
|
5.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.048/22048-500.zip
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a 3G or GSM PLMN Entity and a UICC.
The security mechanisms which are specified are independent of applications.
The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (TS 23.048).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
Within the scope of this document, the UICC refers here to a ICC which support at least one application in order to access a cellular network.
The ICC is considered as a platform, which is either based on TS 31.101 [13], here called "3G platform", or TS 51.011 [23], here called "2G platform".
|
22.121
|
Service aspects; The Virtual Home Environment (VHE); Stage 1
|
TR
|
5.3.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.121/22121-531.zip
|
The present document specifies the content of the Stage 1 requirement for realisation of VHE.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located.
|
23.039
|
Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs)
|
TR
|
5.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.039/23039-500.zip
|
The present document describes a range of alternative interfaces which may be utilised by Short Message Service Centre (SMSC), and Short Message Entity (SME), developers for the connection of SMEs to SMSCs.
The purpose of the present document is to provide a single document within which the various proprietary SMSC to SME interface standards may be accommodated as optional implementations.
As stated in 3GPP TS 23.040 [1], the functionality of the SMSC is outside of the scope of the 3GPP Technical Specifications. As a result, no standardised interfaces have been specified for the connection of SMEs to the SMSC. In the absence of a prevailing standard, SC (Service Centre), developers have devised their own protocols which have not necessarily been based on any existing standards and are therefore largely incompatible with one another.
This document by referring to the various de-facto protocols will limit the further proliferation of proprietary standards and will benefit new SC/SME developers who may then adopt one or more of the existing protocols outlined in the present document.
This document does not provide recommendations, as to the preferred protocol implementation as all are regarded as being of equal merit. SC/SME implementors should therefore adopt the protocol most suited to their particular implementation, application or market.
|
23.048
|
Security mechanisms for the (U)SIM application toolkit; Stage 2
|
TS
|
5.9.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.048/23048-590.zip
|
The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB).
Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in 3GPP TS 51.011 [5] and allows remote management of files on the UICC in conjunction with SMS and the Data Download to UICC feature of 3GPP TS 31.111.
For UICCs based on 3GPP TS 43.019 [15], the set of commands used in the remote applet management is defined in the present document. This is based on the Open Platform card management specification [14]. For UICCs based on other technologies, other loading mechanisms may be used.
The present document is applicable to the exchange of secured packets between an entity in a 3G or GSM PLMN and an entity in the UICC.
Secured Packets contain application messages to which certain mechanisms according to 3GPP TS 22.048 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the UICC. The Sending/Receiving Entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
23.127
|
Virtual Home Environment (VHE) / Open Service Access (OSA)
|
TS
|
5.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.127/23127-520.zip
|
The present document specifies the stage 2 of the Virtual Home Environment.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located.
For Release 5, e.g. CAMEL, MExE, OSA and USAT are considered the mechanisms supporting the VHE concept.
Stage 2 specifications for CAMEL, MExE and USAT are addressed in other documents [1], [2], [3]. However, there is no separate stage 2 specification document for OSA. Therefore, the present document addresses stage 2 aspects for OSA.
|
23.195
|
Provision of User Equipment Specific Behaviour Information (UESBI) to network entities
|
TS
|
5.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.195/23195-540.zip
|
The present document defines the stage-2 description of the mechanism to provide the 3GPP network entities with UE Specific Behaviour Information (UESBI). UESBI may be used by correcting mechanisms to overcome some of the issues that have been recognized by 3GPP in TR 25.994 (Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults) [13], and other such documents. The description of these correcting mechanisms is out of the scope of this TS.
ITU-T Recommendation I.130 [1] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [2] defines stage 2 of the method.
|
23.227
|
Application and user interaction in the User Equipment (UE); Principles and specific requirements
|
TS
|
5.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.227/23227-510.zip
|
The present document defines the principles for scheduling UE resources and controlling UE interactions and resolving conflicts between independently running applications in different application execution environment (e.g. MExE, USAT etc.) and internal and external peripherals (e.g. infra-red, Bluetooth, USIM, radio interface, MMI, memory etc.).
The present document is divided in two parts: clause 4 defines a framework for event handling. Clause 5 addresses some specific issues.
Annex A contains an informative background to the problem area.
|
23.815
|
Charging implications of IMS architecture
|
TR
|
5.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.815/23815-500.zip
|
The present document identifies the charging implications of the IMS architecture, which is described in 23.002 [5] and 23.228 [4].
It is expected that the content of this TR will act as a basis for:
- change requests against the architecture specifications [4, 5] of SA2, clarifying the architecture implications on charging;
- change requests against the Charging Principles specification [3] of SA5, which contains the charging architecture and mechanisms;
- detailed specification of Charging Data Description [6] in SA5.
|
23.871
|
Enhanced support for user privacy in Location Services (LCS)
|
TR
|
5.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.871/23871-500.zip
| |
23.873
|
Feasibility study for transport and control separation in the PS CN domain
|
TR
|
2.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.873/23873-200.zip
|
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 domain that provide both significant control and transport functions may be decomposed into two separate functional entities: one entity taking care of the control functionality and an other entity handling the payload transport. An exact distribution of the functions currently supported by a single functional entity between new functional entities and other network entities will be defined as the result of this feasibility study, if necessary.
A standard control protocol should be used between the control and transport entities, if applicable, e.g. H.248. The required functionality, e.g. extensions to H.248 or any other protocol which may be chosen for this task, would have to be defined and standardised within 3GPP. This TR will identify and define these extensions, and extensions to other interfaces if applicable.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the PS CN domain. At the end of the feasibility study, the remaining open issues will be reported and their importance will be assessed. An analysis of the benefits and drawbacks of separating the control and transport functions in the PS CN domain will also be performed.
|
23.875
|
Support of Push service
|
TR
|
5.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.875/23875-510.zip
|
The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope.
|
23.910
|
Circuit switched data bearer services
|
TR
|
5.5.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.910/23910-550.zip
|
The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
24.228
|
Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
|
TS
|
5.15.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.228/24228-5f0.zip
|
The present document gives examples of signalling flows for the IP multimedia call control based on SIP and SDP.
These signalling flows demonstrate the interaction with the IP-connectivity network (GPRS), and with the protocol provided at the Cx interface.
These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228 [2].
NOTE: The detailed signalling flows in the present document can be referenced, but the specification will not be further maintained. The example flows can contain errors and can only be regarded as guidelines for persons wanting an overview of how SIP messages with detailed header information could in some example cases look like within 3GPP. Other not documented signalling flows can be as relevant and compliant as the ones that are outlined in this specification.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.