id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
32.735
|
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.735/32735-910.zip
|
The present document provides the NRM-specific part related to the IMS NRM IRP [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.732 V9.1.X.
|
32.743
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.743/32743-900.zip
|
The present document maps the IRP information model in 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 V9.0.X.
|
32.745
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.745/32745-900.zip
|
The present document provides the NRM-specific part related to the STN Network Resources IRP NRM in 32.742 [1] of the XML file format definition for the Bulk Configuration Management IRP IS (TS 32.612 [2]).
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.742 V9.0.X.
|
32.753
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.753/32753-920.zip
|
The present document is part of an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning EPC resources. The EPC NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the EPC Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.752 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.752 v9.3.X.
|
32.755
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.755/32755-930.zip
|
The present document provides the XML file format definition for the EPC Network Resource Model IRP IS [2] V9.3.X.
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
|
32.763
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.763/32763-950.zip
|
The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the E-UTRAN Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.762 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.762 v9. 5.X.
|
32.765
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.6.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.765/32765-960.zip
|
The present document provides the XML definitions for the E-UTRAN Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
This specification is related to 3GPP TS 32.762 V9. 5.X.
|
32.773
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.773/32773-900.zip
|
The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HNS resources. The HNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the HNS Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.772 [5]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.775
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.775/32775-910.zip
| |
32.783
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.783/32783-900.zip
|
The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HeNS resources. The HeNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the HeNS Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.782 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.785
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.785/32785-910.zip
|
The present document provides the XML file format definition for the HeNS Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
|
32.821
|
Telecommunication management; Study of Self-Organizing Networks (SON) related Operations, Administration and Maintenance (OAM) for Home Node B (HNB)
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.821/32821-900.zip
|
The present document intends to study the following:
1) Define SON OAM solution architecture for both LTE and UMTS home NodeB.
2) Identify differences between SON OAM solution architecture for LTE Marco eNodeB and that for LTE and UMTS home NodeB; Propose aligned SON OAM solution architecture.
3) Identify what can be standardized for SON for LTE and UMTS NodeB in 3GPP SA5.
4) Prepare the work for a later implementation work item.
|
32.822
|
Telecommunication management; Study on System Maintenance over Itf-N
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.822/32822-900.zip
|
The present document studies key maintenance functions of element management system (EMS) in order to decide which one is necessary and could be managed over Itf-N, and makes a set of recommendations.
|
32.823
|
Telecommunication management; Self-Organizing Networks (SON); Study on self-healing
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.823/32823-900.zip
|
The present document is focused on studying on self-healing of SON. This study provides the general procedure of self-healing, and collects the use cases of self-healing and proposed related 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.824
|
Telecommunication management; Service Oriented Architecture (SOA) Integration Reference Point (IRP) study
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.824/32824-900.zip
|
Service Oriented Architecture (SOA) is gaining acceptance in the IS/IT industry. It promises to manage change [1], automate and simplify IT processes [1], optimize implementation [2], maximize (implementation) flexibility and scalability [3], facilitate integration beyond the enterprise (between companies, between partners and customers) [4], simplify development [5] and maintenance; etc.
IRP (Interface Reference Point) is the predominant standard for wireless network management since 2000. 3GPP developed it with 3GPP2 close collaboration. IRP architecture follows closely with that defined by ITU-T TMN work [6]. Besides publishing the IRP specifications, 3GPP also publishes its IRP methodology (e.g., the guidelines, templates on how to develop, maintain and publish IRP specifications). Today, the IRP specification methodology is being shared and jointly evolved and maintained by consortium of SDOs, such as ITU-T.
We note that the principles of SOA are currently being applied to the field of network management [11,12,16,17].
The purpose of this document is to analyse the IRP architecture and to provide a "gap analysis" on what enhancement is needed for the current set of IRP specifications such that it can claim to have the full set of characteristics of SOA.
|
33.812
|
Feasibility study on the security aspects of remote provisioning and change of subscription for Machine to Machine (M2M) equipment
|
TR
|
9.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.812/33812-920.zip
|
The scope of this Technical Report is to study the remote subscription management for M2M Equipment (M2ME) when the Machine Communications Identity Module (MCIM) application resides in the UICC and when the MCIM application resides in the M2M equipment. The remote subscription management includes tasks such as remote subscription provisioning and/or remote change of subscription.
The scope of this study includes the definition of a trust model for remote subscription management for M2ME.Security threats and security requirements are identified, and an evaluation of the candidate solutions is presented.
The security implications of the following requirements are within the scope of the study (based on section 5.2.2 of TR 22.868)
1. The possibility to change subscription for M2MEs out in the field (e.g. after contract expiry) without direct human intervention.
2. The possibility to allocate the M2ME at initial power up to a network operator without direct human intervention.
Furthermore, this study includes the following items:
- an investigation of candidate security solutions architectures that allow remote subscription management to take place in a secure manner;
- an identification of current USIM/ISIM functionality that may need to be incorporated in a MCIM application, with or without changes to allow remote subscription management for the M2ME;
- an identification of functionality in the network, in the UICC or in the M2ME, that may need to be added due to the remote subscription management method;
- the study may identify principle requirements for protected storage and the execution environment (e.g. by collaborating with relevant working groups such as the OMTP Hardware group)
This study is beyond the scope of the first requirement identified in SA1 TR 22.868 since section 5.2.2 of TR 22.868 contains a requirement to have "Tamper Save/Theft proof terminal including a UICC".
|
33.821
|
Rationale and track of security decisions in Long Term Evolution (LTE) RAN / 3GPP System Architecture Evolution (SAE)
|
TR
|
9.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.821/33821-900.zip
|
The scope of this 3GPP Technical Report is rationale and track of security decisions in Long Term Evolved (LTE) RAN and 3GPP System Architecture Evolution (SAE) for release 8.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.401. This TR is useful to better understand the basis on which decisions in TS 33.401 were taken, and the alternatives that were discussed towards the decision. Some of the text in this TR reflected 3GPP SA3’s decision. However 3GPP’s position on EPS Security Architecture is reflected in the normative text in TS 33.401.
|
34.171
|
Terminal conformance specification; Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD)
|
TS
|
9.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.171/34171-940.zip
|
The present document specifies the measurement procedures for the conformance test of the minimum performance requirements for FDD mode of UTRA user equipment (UE) where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A. The procedures for UEs that support other or additional A-GNSSs are specified in 3GPP TS 34.172 [18].
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.
|
36.800
|
Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Extended UMTS / LTE 800 Work Item Technical Report
|
TR
|
9.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.800/36800-900.zip
|
The present document is a technical report of the Extended UMTS/LTE 800 work item, which was established at TSG RAN#42. The objective of this work item is to provide UTRA and E-UTRA specification support for FDD in the Extended 800 MHz band in Japan. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.805
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Study on minimization of drive-tests in next generation networks
|
TR
|
9.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.805/36805-900.zip
|
The present document is intended to capture findings produced in the context of the Feasibility Study on Minimization of Drive-Tests (MDT) in next generation networks.
The study aims at assessing the feasibility, benefits and complexity of automating the collection of UE measurements to minimize the need of manual drive-tests. The work under this study should take the following steps.
1. Define use cases and requirements for minimizing drive tests in next generation LTE/HSPA networks
2. Based on the defined use cases and requirements, study the necessity of defining new UE measurements logging and reporting capabilities for minimizing drive tests and analyse the impact on the UE
Policy control mechanism and transport mechanism (including message syntax) for the new UE measurement logging and reporting capabilities are outside of the scope of the study. The study should focus on new logging and reporting capabilities for measurements already available at the UE.
|
36.806
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay architectures for E-UTRA (LTE-Advanced)
|
TR
|
9.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.806/36806-900.zip
|
The present document is related to the study item “Further advancements for E-UTRA” [2].
The document describes relay architectures being discussed for E-UTRA (LTE-Advanced).
|
36.810
|
Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); UMTS / LTE in 800 MHz for Europe
|
TR
|
9.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.810/36810-900.zip
|
The present document is a technical report of the "UMTS/LTE in 800 MHz for Europe" work item which was approved at TSG RAN #43 [2]. The purpose of this work item is to provide specification support for LTE and UMTS with paired channel arrangement in the band 790-862 MHz.
The report provides motivation for requirements and a list of recommended changes to the specifications.
|
36.814
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Further advancements for E-UTRA physical layer aspects
|
TR
|
9.2.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.814/36814-920.zip
|
This document is related to the technical report for physical layer aspect of the study item “Further advancements for E-UTRA” [1]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential physical layer evolution under consideration and compare the benefits of each evolution techniques, along with the complexity evaluation of each technique.
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.
|
36.815
|
Further Advancements for E-UTRA; LTE-Advanced feasibility studies in RAN WG4
|
TR
|
9.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.815/36815-910.zip
|
The present document is the technical report on "LTE-Advanced Feasibility Studies in 3GPP RAN WG4".
In particular it facilitates within TSG RAN the preparation of the ITU-R submission template with the parameters which are considered as RAN4 responsibility. The ITU-R submission template and its responsibility across the WGs is captured in [3] and discussed in RAN. The ITU-R submission template has been copied in Annex A.1.
This document is intended to gather the relevant background information in order to address critical UE and BS RF requirements and draw a conclusion on the feasibility of the identified RF scenarios and parameters.
|
36.821
|
Extended UMTS/LTE 1500 work item technical report
|
TR
|
9.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.821/36821-910.zip
|
The present document is a technical report of the Extended UMTS/LTE 1500 work item, which was established at TSG RAN#44. The objective of this work item is to provide UTRA and E-UTRA specification support for FDD in the Extended 1500 MHz band in Japan. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.902
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Self-configuring and self-optimizing network (SON) use cases and solutions
|
TR
|
9.3.1
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.902/36902-931.zip
|
The present document provides descriptions of agreed use cases and solutions with regards to self configuring and self optimizing networks.
The scope of the self configuring and self optimizing functionality is defined in TS 36.300 [2].
|
36.938
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Improved network controlled mobility between E-UTRAN and 3GPP2/mobile WiMAX radio technologies
|
TR
|
9.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.938/36938-900.zip
|
It is expected that IP based 3GPP services will be provided through various access technologies, including existing broadband radio access standards like IEEE 802.16e/ETSI BRAN, and 3GPP2 including HRPD and 1xRTT. In order to achieve this, inter-technology mobility between E-UTRAN and 3GPP2/Mobile WiMAX is considered in the study item "Improved Network Controlled Mobility between E-UTRAN and 3GPP2/Mobile WiMAX Radio Technologies".
The purpose of this TR is to help TSG RAN to capture a stage 2 level solution for each of the studied mobility scenarios, which can be used as a basis to initiate the stage 3 work when moving to the work item phase. This activity involves the Radio Access Network work area of the 3GPP studies for mobility and has impacts on both the Mobile Equipment and Access Network of the 3GPP systems. Architecture impact involving non-RAN nodes is under the responsibility of SA2.
|
22.112
|
USIM Application Toolkit (USAT) Interpreter; Stage 1
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.112/22112-800.zip
|
The present document specifies a system to make Mobile Operator services, based on USAT functionality and USIM based security functionality, available to an internet environment. This is achieved by specifying the necessary components and protocols for a secure narrow band channel between the internet application and an USAT Interpreter on the USIM. The actual application could be developed using the application language of choice. Two types of applications interfaces are used as examples, i.e., mark-up language based on WML and Remote Procedure Call (RPC).
The interpreter and the secure narrow band channel form a core platform to enable services like:
- Advanced security functionality, e.g., digital signatures in m-commerce applications
- Value added services based on position and roaming
- Controlled activation and management of other applications, e.g. multimedia and payment type of applications.
The secure narrow band channel is achieved by specifying the following:
- specific application and content related functionalities of the interface between the application system and the USAT Gateway;
- specific functionalities and protocols of the interface between the USAT Gateway and the USAT Interpreter associated with a USIM, achieved by defining a low level command set for interpretation by the USAT Interpreter;
- defined level of functionality available to the application server for the implementation of USIM based services such as PKI, location services, push and broadcast services, event based services, etc..
The present document does not specify any elements of the protocol stack between the application server and the USAT Gateway, the mark-up language definition, and the transport protocols between the USAT Gateway and the USAT Interpreter.
|
22.168
|
Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1
|
TS
|
8.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.168/22168-830.zip
|
This Technical Specification defines the stage one description of the Earthquake and Tsunami Warning System (ETWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of ETWS. ETWS deployment depends on operator decision or national regulations.
This TS contains the core requirements for the Earthquake and Tsunami Warning System, which are sufficient to provide a complete service.
This TS also contains regional requirements for Earthquake and Tsunami Warning System.
|
22.401
|
TISPAN; Videotelephony over NGN Service Description
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.401/22401-800.zip
|
The present document defines the requirements for a videotelephony service which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities.
The present document provides interoperability service requirements for interconnection between existing networks and a TISPAN NGN, and between TISPAN NGN.
The present document only provides requirements for IP multimedia based networks. Services provided by a TISPAN NGN to support legacy terminals and interfaces (PSTN/ISDN emulation) are defined in existing PSTN/ISDN documents. Requirements for PSTN/ISDN emulation are out of scope of the present document and are described in other documents.
The applicability of PSTN/ISDN simulation services to the videotelephony service requirements are defined in the present document.
The requirements in the present document are described from the user point of view. The requirements do not take into account capabilities of existing protocols defined for the IMS. The evolution or modifications to these protocols are beyond the scope of the present document.
NOTE: The present document uses the term "NGN" only in the context of TISPAN.
|
22.868
|
Study on facilitating machine to machine communication in 3GPP systems
|
TR
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.868/22868-800.zip
|
The present document identifies potential requirements to facilitate improvements in M2M communication and the more efficient use of radio and network resources.
Special consideration is given to the following areas for optimisation:
- Charging mechanisms
- Addressing
- Types of communication
- Fixed location, low mobility and low activity terminals
- Handling of large numbers of subscriptions and subscriber data within the network
- Handling issues of large number of M2M subscriptions for the user of M2M services
- Impact of optimisations for security resulting from improvement for M2M
|
22.892
|
Study on IMS Centralized Services (ICS) requirements
|
TR
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.892/22892-800.zip
|
The present document provides a study of the service experience and suggested service requirements for IP Multimedia System (IMS) Centralized Services (ICS). ICS enables the delivery of IMS based services to users regardless of the attached access network type; e.g. CS domain access or IP Based Access Networks. Service continuity between access networks is also considered. User and service provider perspectives are considered along with service scenarios as the basis for identifying service requirements. Based on the previous considerations, service requirements are identified and conclusions are drawn.
|
23.506
|
TISPAN; IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.228 Release 7, modified]
|
TS
|
8.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.506/23506-810.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 23.228 "IP Multimedia Subsystem; Stage 2, Release 7".
The present document provides the necessary adaptions to the 3GPP IP Multimedia Core Network Subsystem (IMS), in order to support the Access Networks and terminals in the scope of the present NGN Release. The present document also includes certain elements from 3GPP Release 8 (TS 23.228 v8.2.0)
|
23.507
|
TISPAN; Voice Call Continuity (VCC); Stage 2 [3GPP TS 23.206 Release 7, modified]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.507/23507-800.zip
|
The present document provides the ETSI TISPAN endorsement of 3GPP TS.23.206 [3] " Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2: Release 7”.
The current VCC solution explained in the TS.23.206 is essentially defined for a core IMS provider that is a mobile operator (that has also CS domain). In Informative Annex ZA theres is a possible scenario how the solution can be extended to a generic IMS operator (e.g. when fixed network operator and CS mobile network operator are separate organisations).
|
23.508
|
TISPAN; Presence Service; Architecture and functional description [Endorsement of 3GPP TS 23.141 and OMA-AD-Presence_SIMPLE-V1_0]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.508/23508-800.zip
|
(Void)
|
23.509
|
TISPAN; NGN Architecture to support emergency communication from citizen to authority [Endorsed document 3GPP TS 23.167, Release 7]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.509/23509-800.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 23.167 [1].
The present document defines the architectural description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services
The present document covers also the Access Network aspects that are crucial for the provisioning of IMS emergency services.
|
23.511
|
TISPAN; XML Document Management; Architecture and functional description [OMA-AD-XDM-V1_0-20051006-C modified]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.511/23511-800.zip
|
(Void)
|
23.517
|
TISPAN; IP Multimedia Subsystem (IMS); Functional architecture
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.517/23517-800.zip
|
The present document describes the IP Multimedia Subsystem (IMS) core component of the TISPAN NGN functional architecture and its relationships to other subsystems and components.
|
23.521
|
Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Support of Short Message Service (SMS) over NGN IMS subsystem; Stage 2; [Endorsement of 3GPP TS 23.204 Release 7]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.521/23521-800.zip
|
The present document provides the ETSI TISPAN endorsement of 3GPP TS.23.204 [1] "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 (Release 7)”.
|
23.611
|
TISPAN; XML Document Management; Architecture and functional description [OMA-AD-XDM-V1_0-20051006-C modified]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.611/23611-800.zip
|
(Void)
|
23.810
|
Study on architecture impacts of Service Brokering
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.810/23810-800.zip
|
The objective is to study if there is enhancement needed to the current service interaction management architecture (e.g. SCIM as part of AS and Service Broker as part of OSA SCS) in order to satisfy requirements in TS 22.228 [1].
This technical report contains the results of a study on service interaction management architecture with focus on the following aspects:
- considering through scenarios, if the current service interaction management architecture sufficiently manages interactions between application servers, within the Home Network or on third party servers, and
- determine, through a functional element architecture study, whether there is a need for enhancement of the architecture, as well as any required extensions to the current IMS protocols and procedures.
In addition, alternative mechanisms to improve preventing interacting services may be identified.
|
23.811
|
Service level interworking for messaging services; Stage 2
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.811/23811-800.zip
|
This document contains the results of the study into the architectural requirements and comes up with the solution of the service level interworking for the Short Message service as defined in the TS 23.040 [6] and Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_20070816-C [8]. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to identify an architectural solution that allows completely service level interworking between SMS and SIMPLE IM without degrading existing services, under the service requirements defined in the TS 22.340 [2] and TS 22.105 [3]. In addition, how to charge for the interworked services shall be considered in this study as well.
|
23.828
|
Earthquake and Tsunami Warning System (ETWS); Requirements and solutions; Solution placeholder
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.828/23828-800.zip
|
The present document is a temporary architectural solution placeholder for Earthquake and Tsunami Warning System (ETWS). This document is to present various architecture and function approaches for 3GPP networks (i.e. GERAN, UTRAN, and LTE) based on the ETWS requirements described in TS 22.168 [2].
NOTE: The contents of this Technical Report led into normative specification of ETWS in related specifications and the contents of this study should be considered out of date.
|
23.847
|
Enhancements to IMS service functionalities facilitating multicast bearer services
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.847/23847-800.zip
|
This study analyzes the feasibility and applicability of using multicast bearers (e.g. MBMS) in the context of IMS-based applications.
This study item captures the results of the technical considerations and solutions for transporting IMS services over multicast bearers with a focus on the possible enhancements to IMS functionalities and relevant charging, security and service provision procedures.
A brief summary of considerations include:
- Signalling procedures of multicast enabled IMS services should be analyzed based on the grouped communication scenarios and possible optimisations to the delivery mechanisms should be investigated.
- Charging and policy control procedures according to the PCC architecture.
- Service provision procedures both in network elements and UEs.
- Possible security requirements to multicast enabled IMS functionalities and bearer service entities.
- Real-time QoS requirements e.g. delay , interruption.
- UE capability requirements.
|
23.872
|
Study on architecture of IP Multimedia Subsystem (IMS) based Customized Alerting Tone (CAT)
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.872/23872-800.zip
|
This study intends to investigate the architectural impacts on and potential enhancements to IMS specifications to meet the normative requirements for CAT in IMS domain as specified in TS 22.182 [2]:
- Architecture and procedures to support basic call scenarios for CAT in IMS domain;
- Interaction with other service, e.g. IMS Multimedia telephony supplementary services;
- Service provision for roaming subscribers;
- Interworking between IMS CAT and CS CAT in TR 29.882 [3].
In the end, this study will provide conclusions with respects to what further specification work is required in order to fulfil the requirements for the CAT in IMS domain.
|
23.882
|
3GPP system architecture evolution (SAE): Report on technical options and conclusions
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.882/23882-800.zip
|
The objective of this feasibility study is to develop a framework for an evolution or migration of the 3GPP system to a higher-data-rate, lower-latency, packet-optimized system that supports, multiple RATs. The focus of this work will be on the PS domain with the assumption that voice services are supported in this domain.
NOTE: This feasibility study has led into work items specifying LTE/SAE and the contents of this study should be considered out of date.
The main objectives are to address the following aspects:
1) Overall architecture impacts stemming from requirements coming out from TSG-RAN's Study Item on Radio Evolution (see SP‑040915). The architectural developments should take into account the targets for the evolution of the radio-interface, e.g.:
i) whether there is a need for a modified network architecture and/or different functional split between network nodes (compared to the current 3GPP architecture);
ii) how to provide a very low latency (including C-plane) for the overall network (including core network, radio access network and radio access technology);
iii) how to provide the efficient support of the various types of services, especially from the PS domain (e.g. Voice over IP, Presence).
2) Overall architecture impacts stemming from the work in SA1 on an All-IP Network (AIPN) (see TS 22.258 [4]), e.g.:
i) support of a variety of different access systems (existing and future) and access selection based on combinations of operator policies, user preferences and access network conditions;
ii) how to realize improvements in basic system performance e.g. communication delay, communication quality, connection set-up time, etc.;
iii) how to maintain the negotiated QoS across the whole system; in particular to address inter-domain and inter-network interworking, and, QoS on the network link to the Base Station site.
NOTE: Although used in the SA WG1 TS 22.258 [4], the All-IP Network (AIPN) term is not used in the network architecture in this SAE TR as mapping between the term AIPN used in SA1 and the evolved architecture is not deemed necessary to progress the SAE work. Instead, the requirements on AIPN in TS 22.258 [4] are treated as overall system requirements. Even though the AIPN includes an evolved, IP based, core network and evolved IMS domain, the scope of this SAE TR does not include the IMS domain aspects.
3) Overall architecture aspects of supporting mobility between heterogeneous access networks, including service continuity. E.g.:
i) service continuity between I-WLAN and the 3GPP PS domain;
ii) how to support multiple radio access technologies and terminal mobility between different radio access technologies;
iii) how to maintain and support the same capabilities of access control (authentication, authorization), privacy and charging when moving between different radio access technologies.
Migration aspects should be taken into account for the above, i.e. how to migrate from the existing architecture.
In the course of conducting this feasibility study additional individual Work Items may be identified and prepared to address certain aspects and to take care of the respective specification work. The timelines of those Work Items may or may not concur with the timeline of this feasibility study.
|
23.892
|
IP Multimedia Subsystem (IMS) centralized services
|
TR
|
8.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.892/23892-801.zip
| |
23.893
|
Feasibility study on multimedia session continuity; Stage 2
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.893/23893-800.zip
|
This study intends to investigate the general problem of IMS-level multimedia session continuity, including potential enhancements to IMS specifications that can improve the multimedia session continuity experience. In particular, the following topics will be studied:
- Identification of session continuity scenarios;
- PS-PS session continuity;
- PS-PS session continuity in conjunction with PS-CS continuity;
- Session continuity between 3GPP and non-3GPP systems;
- Network-initiated Multimedia Session Transfer;
- Mobility of media components of a session between different terminals under the control of the same user;
- Coexistence and/or potential interactions with possible underlying mobility solutions defined by 3GPP. The solutions developed within this study should not have any impacts to underlying mobility solutions.
In the end this study will provide conclusions with respects to what further specification work is required in order to fulfil the IMS-level Multimedia Session Continuity requirements and improve the overall service continuity experience.
|
24.406
|
TISPAN; PSTN/ISDN simulation services; Message Waiting Indication (MWI): Protocol specification
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.406/24406-810.zip
|
The present document specifies the stage three Protocol Description of the Message Waiting Indication (MWI) service, based on stage one and two of the ISDN MWI supplementary services. Within the TISPAN NGN Release1 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.407
|
TISPAN; PSTN/ISDN simulation services; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification
|
TS
|
8.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.407/24407-830.zip
|
The present document specifies the stage three (protocol description) of the Originating Identification Presentation (OIP) simulation service and the Originating Identification Restriction (OIR) simulation services, based on stage one and two of the ISDN CLIP [4] and CLIR [5] supplementary service. Within the TISPAN NGN Release 1 the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
NOTE: It should be noted that the behaviour described in this the present document does not take into account other behaviours that may be specified in other applications and care needs to be taken when designing the filters etc. when two or more applications are involved in a session.
|
24.410
|
TISPAN; NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.410/24410-810.zip
|
The present document specifies the, stage three, Protocol Description of the Communication Hold (HOLD) services, based on stages one and two of the ISDN Hold (HOLD) supplementary services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.411
|
TISPAN; PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification
|
TS
|
8.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.411/24411-830.zip
|
The present document specifies the, stage three, Protocol Description of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) simulation service, based on stage one and two of the ISDN supplementary service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB). Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.423
|
TISPAN; PSTN/ISDN simulation services; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN PSTN/ISDN Simulation Services
|
TS
|
8.5.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.423/24423-850.zip
|
The present document defines a protocol used for manipulating data related to PSTN/ISDN Simulation services. The protocol is based on the eXtensible Markup Language (XML) Configuration Access Protocol (XCAP) [8]. A new XCAP application usage is defined for the purpose of manipulating PSTN/ISDN Simulation services data. The common XCAP related aspects that are applicable to PSTN/ISDN services are specified in the present document. The protocol allows authorized users to manipulate service‑related data either when they are connected to IMS or when they are connected to non‑IMS networks (e.g. the public Internet).
|
24.430
|
TISPAN; Presence Service Capability; Protocol Specification [3GPP TS 24.141 V7.0.0, modified and OMA-TS-Presence_SIMPLE-V1_0, modified]
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.430/24430-810.zip
|
The present document provides the 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 as defined in ES 283 003 [1].
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, either directly, or as modified by ES 283 003 [1].
The Presence XDMS and Resource List Server (RLS) specific data formats and XCAP application usages are within the scope of the present document. These are used within the context of the generic XDM capability described in
TS 183 038 [2].
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing presence functionality.
|
24.441
|
TISPAN; Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of 3GPP TS 24.247 Release 6]
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.441/24441-800.zip
|
The present document provides the ETSI TISPAN endorsement of 3GPP TS 24.247 (V6.4.0) [1]: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (Release 6)" in line with the requirements of TISPAN NGN.
|
24.447
|
TISPAN; NGN IMS Supplementary Services; Advice Of Charge (AOC)
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.447/24447-800.zip
|
The present document specifies the stage three Protocol Description of the Advice Of Charge (AOC) service, based on stage 1 and 2 of the ISDN Supplementary Service Advice Of Charge for all calls (permanent mode). Within the TISPAN NGN Release 2 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
Three AOC services exist:
a) Charging information at communication set-up time (AOC-S)
The AOC-S service enables a user to receive information about the charging rates at communication set-up time and also to receive further information during the communication if there is a change of charging rates.
b) Charging information during the communication (AOC-D)
The AOC-D service enables a user to receive information on the recorded charges for a communication during the active phase of the communication.
c) Charging information at the end of the communication (AOC-E)
The AOC-E service enables a user to receive information on the recorded charges for a communication when the communication is terminated.
|
24.451
|
TISPAN; Support of SMS and MMS over NGN IMS subsystem; Stage 3 [Endorsement of 3GPP TS 24.341 Release 7]
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.451/24451-810.zip
|
The present document provides the ETSI TISPAN endorsement of the 3GPP TS 24.341 [1] "Support of SMS over IP networks; Stage 3 (Release 7)".
|
24.454
|
TISPAN; PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG)
|
TS
|
8.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.454/24454-840.zip
|
The present document specifies the, stage three, Protocol Description of the Closed User Group (CUG) service, based on stage one and two of the ISDN Communication diversion supplementary services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Communication Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.503
|
TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified]
|
TS
|
8.22.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.503/24503-8m0.zip
|
The present document provides the ETSI TISPAN endorsement of 3GPP TS 24.229 [1]: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (Release 7)" in line with the requirements of TISPAN NGN.
The present document together with the endorsed document provides the necessary SIP/SDP specifications for supporting TISPAN Release 2 requirements.
|
24.504
|
TISPAN; PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification
|
TS
|
8.22.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.504/24504-8m0.zip
|
The present document specifies the, stage three, Protocol Description of the Communications Diversion (CDIV) services, based on stage one and two of the ISDN Communication diversion supplementary services. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Communication Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.505
|
TISPAN; PSTN/ISDN simulation services: Conference (CONF); Protocol specification
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.505/24505-810.zip
|
The present document specifies the, stage three, Protocol Description of the Conference (CONF) service based on stage one and two of the ISDN CONF supplementary service. Within the Next Generation Network (NGN) the stage 3 is specified using the IP-Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
The present document specifies centralized conferencing, using a conference focus, distributed conferencing is out of scope.
The present document does not cover the cases of :
a) cascading conference services; and
b) the support of the PSTN/ISDN conference service hosted in the PSTN.
|
24.508
|
TISPAN; PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification
|
TS
|
8.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.508/24508-820.zip
|
The present document specifies the stage three protocol description of the Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) services, based on stage one and two of the ISDN COLP [3] and COLR [4] supplementary services. Within the TISPAN NGN Release 1 Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.516
|
TISPAN; PSTN/ISDN simulation services; Malicious Communication Identification (MCID); Protocol specification
|
TS
|
8.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.516/24516-830.zip
|
The present document specifies the, stage three, Protocol Description of the Malicious Call Communication Identification (MCID) service based on the stage one and two of ISDN Malicious Call Identification supplementary service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP). The MCID service will store session related information independent of the service requested.
|
24.528
|
TISPAN; Common Basic Communication procedures; Protocol specification
|
TS
|
8.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.528/24528-830.zip
|
The present document describes the stage three protocol for basic communication procedures common to several services when at least one Application Server (AS) is included in the communication. The common procedures are based on stage three specifications for services.
The present document contains examples of signalling flows for the common basic communication procedures.
|
24.529
|
TISPAN; PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification
|
TS
|
8.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.529/24529-820.zip
|
The present document specifies the stage three (protocol description) of the Explicit Communication transfer (ECT) simulation service, based on stage one and two of the ISDN ECT supplementary service. Within the Next Generation Network (NGN) the stage 3 description is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).
|
24.801
|
3GPP System Architecture Evolution (SAE); CT WG1 aspects
|
TR
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.801/24801-810.zip
|
The present document discusses and describes the CT1 aspects of the 3GPP System Architecture Evolution (SAE) towards a higher-data-rate, lower-latency, packet-optimized system that supports multiple access technologies.
In particular, these CT1 aspects include the Non-Access-Stratum (NAS) functions to be performed by the User Equipment (UE) in idle mode, the NAS signalling procedures between the UE and the evolved packet core network (EPC) via the E-UTRAN, and the layer 3 signalling procedures between the UE and the EPC via non-3GPP access networks.
The present document also considers the requirements on the NAS between the UE and the core network which arise from specific services like MBMS and network functions like security, QoS, and mobility within the E‑UTRAN or between the E‑UTRAN and other 3GPP or non-3GPP access networks.
The present document is intended as a holding place for CT1 SAE material until it stabilises sufficiently to be moved to appropriate 3GPP technical specifications.
|
24.880
|
Media server control using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3
|
TR
|
8.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.880/24880-820.zip
|
The present document describes the implementation options and requirements for a media server control protocol to be used with the Mr and ISC interfaces.
This Technical Report includes the study of the following items:
- Define the requirements for a media server control protocol.
- Consider existing standards work that should be studied for the definition of a media server control protocol.
- Study and determine whether the media server control protocol should be carried in SIP or whether SIP should be used to setup a dedicated control interface.
- Study whether the AS directing the SIP session to the MRFC is always the same SIP-AS that should control the MRFC.
- Determine whether the media server control protocol should have a package naming and extension capability (similar to H.248 packages) to allow the support and registration of different media processing capabilities.
- Determine the SIP call flows and SDP capabilities associated with the media server control protocol and whether these SIP messages need to be passed through a S-CSCF proxy function or whether it is more efficient to have a direct AS-MRFC interface.
This Technical Report will be used to move into the specification phase for a media server control protocol.
|
25.816
|
UMTS 900 MHz Work Item technical teport
|
TR
|
8.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.816/25816-800.zip
|
This document is the technical report of the UMTS 900 MHz WI which was approved in TSG RAN meeting #26 [1].
The purpose of this TR is to summarize the study of radio frequency (RF) requirements for UTRA-FDD operating in the 900 MHz Band defined as follows :
• 880 – 915 MHz: Up-link (UE transmit, Node B receive)
• 925 – 960 MHz: Down-link (Node B transmit, UE receive)
|
25.820
|
3G Home Node B (HNB) study item Technical Report
|
TR
|
8.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.820/25820-820.zip
|
This document is a technical report of the study item on Home NodeB/eNodeB [1]. The goal of this study item is,
• To characterise the 3G Home NodeB environment. Whenever possible the scenarios defined as part of this study shall be of benefit to the LTE Home eNodeB investigation.
• To determine the feasibility of a solution and to outline any obstacles
• High level HNB requirements are understood not to be complete; hence the report includes a description of the motivation of requirements needed to progress the work
• Whenever possible to offer recommendations for specifications
|
25.821
|
UMTS1500 MHz work item technical report
|
TR
|
8.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.821/25821-800.zip
|
This document is a technical report of the UMTS1500 work items. The purpose of these work items is to provide UMTS specification support for UTRA FDD in the 1500 MHz in Japan. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
This document is a ‘living’ document, periodically updated and presented at all TSG-RAN meetings until all related CRs are agreed and approved.
|
25.823
|
Feasibility study on synchronized E-DCH for UTRA FDD
|
TR
|
8.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.823/25823-800.zip
|
The present document is the technical report for the Release 8 Study Item “Synchronised E-DCH” (see [1]).
This document is intended to gather all information in order to compare gains vs. complexity, and draw a conclusion on way forward. The document will describe likely impacts to the UTRA FDD specifications and system operation, estimate any changes to the UTRA FDD uplink data or control channel structure (including downlink control channels relating to the uplink and uplink control channels relating to the downlink) and evaluate potential performance gains
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.824
|
Scope of HighSpeed Packet Access (HSPA) Evolution for 1.28Mcps TDD
|
TR
|
8.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.824/25824-800.zip
|
The present document has been produced in the scope of the study item on "HSPA Evolution for 1.28Mcps TDD" [2]. The objective of the study item is to develop a framework for the evolution of the 1.28Mcps TDD mode of the 3GPP HSPA TD-SCDMA-based radio-access technology from Release 8 onwards.
This document lists the constraints for the 1.28Mcps TDD HSPA Evolution in Release 8 and an assessment of technical proposals and their respective, achievable performance and complexity.
|
29.412
|
TISPAN; Interworking; Trunking Gateway Control Procedures for interworking between NGN and external CS networks
|
TS
|
8.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.412/29412-810.zip
|
The present document defines the control procedures for trunk gateways when PSTN/ISDN emulation and PSTN/ISDN simulation services in an NGN Network require interworking with ETSI PSTN/ISDN services in a ISUP network. Interworking with BICC networks is not included in the scope of TISPAN R2.
Existing profiles will be evaluated, in order to determine if they can be re-used, with possible modifications, or if a completely new profile is to be defined.
|
29.421
|
TISPAN; NGN Release 1; Endorsement of 3GPP TS 29.162 Interworking between IM CN Sub-system and IP networks
|
TS
|
8.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.421/29421-810.zip
|
The present document describes the interworking between the TISPAN IMS and an external IP network including other IMS networks for IP multimedia service support.
The present document addresses the areas of control and user plane interworking through the network functions, which include the IBCF and I-BGF. For the specification of control plane interworking, the interworking between IMS SIP and an external SIP profile are detailed in terms of the procedures required for the support of both IMS originated and terminated SIP sessions.
In particular, the present document describes the protocol mappings for support of communications between networks using different IP versions or between networks with NATs operating at their border.
|
29.424
|
TISPAN; H.248 Profile for controlling Trunking Media Gateways; Protocol specification
|
TS
|
8.0.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.424/29424-801.zip
|
The present document defines the profile of the Gateway Control Protocol (ITU-T Recommendation H.248.1 [3]), for controlling Trunking Media Gateways (TMGW) for both the PSTN/ISDN Emulation and IMS Core Subsytems. Thus the scope of this Profile is a subset of the 3GPP profile for the Mn interface defined in TS 129 332 [2].
|
29.433
|
TISPAN; IP Multimedia; Diameter based protocol for the interfaces between the Call Session Control Function and the User Profile Server Function/Subscription Locator Function; Signalling flows and protocol details [3GPP TS 29.228 and 29.229 modified]
|
TS
|
8.1.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.433/29433-811.zip
|
The present document provides the ETSI TISPAN endorsement of the 3GPP TS 29.228 [1] " Cx and Dx interfaces; Signalling flows and messages contents" and the 3GPP TS 29.229 [2] "IP Multimedia (IM) Subsystem Cx and Dx interfaces based on the DIAMETER protocol; Protocol details".
The present document provides the necessary adaptations to the above specifications, in order to comply with the requirements of NGN Release 2.
|
29.458
|
TISPAN; SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification
|
TS
|
8.5.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.458/29458-850.zip
|
The present document specifies the Stage 3 of the real-time transfer of tariff information between a Charge Determination Point (CDP) and a Charge Generation Point (CGP) by means of the Session Initiation Protocol (SIP).
It identifies the protocol procedures and switching functions needed to support the transfer of tariff information related to IP multimedia services. The information needed to support the ISDN User part (ISUP) signalling aspects of charging (ES 201 296 [6]) for Advice of Charge information purposes is also specified, however, it can be used for other purposes as well where applicable.
The present document is applicable to an environment where different operators are working together. It is also applicable to a single network operator environment.
Whether the present document is applicable to a national environment and/or can be used for inter-network purposes depends on regulatory demands and/or bilateral agreements. It should be noted that there are network requirements and signalling limitations that are not covered because they are outside the scope of the present document. Examples of these are as follows:
- the on-line provided advice of charge information may not accurately reflect the correct charging rate due to discount rates, special charging arrangements, etc. It is out of scope to ensure alignment of this information;
- complaint handling between network operators in case of incorrect advice of charge information;
- explicit encryption or special security mechanisms;
- usage of the transferred tariff information for charging purposes;
- interaction between UE and CGP for possible confirmation of provided tariffs;
- any function behind the CGP towards the UE.
|
29.527
|
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
|
8.3.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.527/29527-830.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 29.163 [1].
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.
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.804
|
3GPP System Architecture Evolution (SAE): CT WG3 aspects
|
TR
|
8.0.1
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.804/29804-801.zip
|
The present document discusses and describes procedures and protocols from CT3 aspects of System Architecture Evolution (SAE) towards a higher-data-rate, lower-latency, packet-optimized system that supports multiple access technologies.
These CT3 aspects include the PCC enhancements (including impacts coming from the inter-access system handover, roaming and LBO), the QoS aspects for both 3GPP and non-3GPP networks, inter-working with external networks, MBMS and any other functions in the Evolved Packet Core (EPC) network that CT3 has impact on.
The present document is used as a placeholder for CT3 SAE materials to be moved to appropriate 3GPP technical specifications when it is sufficiently stable. As such, neither all the discussions within this document are finished nor the procedures need to be completed. This TR may also contain some empty clauses. This TR will no longer be updated on a systematic manner and therefore contained information may become outdated.
|
29.805
|
InterWorking Function (IWF) between MAP based and Diameter based interfaces
|
TR
|
8.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.805/29805-800.zip
|
The present document is to evaluate the feasibility of introduction of an InterWorking Function (IWF) between MAP-based and Diameter-based interfaces. This evaluation will be based on the study of various concrete interworking deployment scenarios for which an IWF can/could be used. For each scenario, it will be analysed how the IWF fulfils the specific interworking requirements and performs the mapping of procedures and the corresponding parameter handling.
The present document will study the related mechanism for the interworking scenarios, e.g. addressing. The other mechanism, such as security, will also be described in this document as a part of the whole solution.
|
29.863
|
Feasibility Study for the multimedia inter-working between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks
|
TR
|
8.2.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.863/29863-820.zip
|
The present document provides a feasibility study for the interworking of multimedia calls between the IP Multimedia CN Subsystem and CS networks (i.e. PSTN, ISDN and GSM/UMTS CS networks).
The present document study and outlines different solutions and functionality required within the MGW to deliver the user plane aspects between IM CN subsystems and CS networks for support of basic multimedia calls. It also outlines the solutions and functionality required within the MGCF and SGW to deliver the control plane aspects between IM CN subsystems and CS networks to support basic multimedia calls.
The document also studies the MONA interworking impacts, and which parts of MONA are feasible, or even possible, to interwork.
The user plane interworking necessary to cover the basic multimedia calls is also outlined and studied.
The different aspects studied for the different scenarios should encompass the transport protocol, transcoding and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
|
29.864
|
Study on IMS Application Server (AS) service data descriptions for AS interoperability
|
TR
|
8.0.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.864/29864-801.zip
|
The present document studies requirements for application server service data definition. It also studies the transfer of the defined service data between an application server and the HSS. Further, it exposes a service data definition for a telephony application server for services as defined in 3GPP TS 22.173 [3]. Finally it provides recommendations for how the framework can be reused and extended for future IMS service definitions.
|
29.882
|
Customized Alerting Tone (CAT) in 3G CS domain
|
TR
|
8.0.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.882/29882-801.zip
|
The present document provides a study into providing a Customized Alerting Tones in the 3GPP CS domain. The document covers the functional description, network architecture and protocol definition to support CAT in the 3GPP CS domain for speech and multimedia calls.
|
29.865
|
Inter-IMS network to network interface
|
TR
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.865/29865-800.zip
|
The objective of this document is to address the Inter-IMS Network to Network Interface (II-NNI) consisting of Ici and Izi reference points between IMS networks in order to support end-to-end service interoperability.
The present document will address the issues related to control plane signalling (3GPP usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues as transport protocol, media and codecs actually covered in a widespread set of 3GPP specifications.
Charging aspects will be addressed as far as SIP signalling is concerned.
The purpose of this document is to prepare some material that could be moved to the foreseen Technical Specification for the profiling of the Inter-IMS Network to Network Interface (II-NNI) and to propose if any needed modifications of the 3GPP core specifications are required.
|
31.112
|
Universal Subscriber Identity Module Application Toolkit (USAT) interpreter architecture description
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.112/31112-800.zip
|
The present document defines the stage 2 description for the USAT Interpreter system. As the second stage of a three-level structure, it is derived from the stage 1 service description.
The present document defines the overall architecture for the USAT Interpreter system:
Role models;
System architecture;
Function and information flow.
The stage 3 documents shall conform to the present document.
|
31.113
|
Universal Subscriber Identity Module Application Toolkit (USAT) interpreter byte codes
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.113/31113-800.zip
|
The present document specifies the byte codes that are recognised by an USAT Interpreter. The byte codes primary purpose is to provide efficient programmatic access to the SIM Application Toolkit commands.
The design objectives of the byte code set are:
- Compact representation for efficient transmission over the air interface.
- Minimisation of USAT Interpreter complexity to minimise SIM footprint and ease compliance testing.
- Easily configured and extended.
- Source language independent although XML-style mark-up languages are explicitly envisioned.
- Transport bearer independent (e.g. SMS, GPRS...)
- Transport protocol independent.
- Independent from design of external entities.
|
31.114
|
Universal Subscriber Identity Module Application Toolkit (USAT) interpreter protocol and administration
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.114/31114-800.zip
|
The present document specifies the transmission protocol to be used to communicate with the USAT Interpreter and the administrative structures and procedures to administer the USAT Interpreter.
The present document does not specify any USAT Interpreter byte code commands.
|
31.919
|
2G/3G Java Card™ Application Programming Interface (API) based applet interworking
|
TR
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.919/31919-800.zip
|
The present document describes:
- Description of TS 43.019 [1] APIs and TS 102 241 [2] / TS 31.130 [7] APIs interworking.
- The behaviour and limitations of the TS 43.019 [1] APIs used in 3G environment.
|
32.808
|
Telecommunication management; Study of Common Profile Storage (CPS) Framework of User Data for network services and management
|
TR
|
8.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.808/32808-800.zip
|
The present document investigates possibilities to introduce an end-user profile storage framework into 3GPP conformant communication networks. To this end the following topics are covered:
• Analysis of the consequences of creating one common data model structure for an end user:
- Existing data specifications concerning an end-user or a subscriber in 3GPP, TISPAN, OMA and other relevant standardization groups are listed and used as a basis for the proposal of a structure for a common end-user data model.
- Topics connected to the fact that one common data model exists, like minimizing data redundancy, access control, providing views for applications are highlighted.
- The relationship between an end user and a subscriber as defined by 3GPP is revisited in light of the fact that the relations between subscribers (contract holders) and end-users can be n:m.
• Current initiatives connected to subscription information carried out inside and outside 3GPP are covered.
• Analysis of differences and deficiencies concerning 3GPP's current status of specifications (e.g. GUP, SuM, etc.) in comparison to existing/emerging solutions with centralized or distributed storage models.
• Identification of items for standardization as a result of the analysis described in the bullet above.
|
32.816
|
Telecommunication management; Study on management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC)
|
TR
|
8.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.816/32816-800.zip
| |
32.818
|
Telecommunication management; Study on 3GPP SA5 / MTOSI XML harmonization
|
TR
|
8.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.818/32818-800.zip
|
The present document is the outcome of the SA5 MTOSI XML harmonization study.
MTOSI version 1.1 is considered in the present document.
The goal of the present document is multiple:
• At first, it mainly consists in studying the MTOSI XML recommendations and estimate whether or not they are applicable and useful to SA5.
• Then, a delta calculation, in terms of Methodology, Specifications and Models, will be studied and presented in order to define, in case MTOSI recommendations prove to be useful to SA5, what are the main differences between MTOSI and SA5 specifications. Once those will be identified, they will be ordered in priority and a decision will be made, whether or not the harmonization process for such or such items can be kicked off.
• Finally, a proposed roadmap for those activities will be presented. This roadmap is likely to evolve as we move along the harmonization effort between MTOSI and SA5.
The content of the present document is subject to 3GPP SA5 discussion and decisions will be made based on the output thereof.
|
32.819
|
Telecommunications management; Element management layer - Operation System Function (E-OSF) definition
|
TR
|
8.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.819/32819-800.zip
|
The present document identifies and defines the needs in the E-OSFs.
The intention is not to define new requirements for the eventual standardization of new Interface IRP or NRM IRP and/or System Context.
The present document proposes to define the E-OSFs including the following main aspects:
• Define functional scope of Element-OSF (E-OSF)
• Define functional requirement of Elements-OSF (E-OSF)
The present document identifies a set of functions require by operators to operate mobile networks.
By identifying these functional capabilities and then comparing them with the 3GPP IRP capabilities, widely used functions and omissions in the 3GPP set of IRPs are indicated.
Change Requests and new IRPs are expected to be created in order to narrow the functional gap.
|
32.820
|
Telecommunication management; Study on charging management; 3GPP Evolved Packet Core (EPC): Charging aspects
|
TR
|
8.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.820/32820-801.zip
|
The present document intends to study the impact of the evolved 3GPP system architecture with respect to charging.
The study covers the relevant non-roaming and roaming use cases for both 3GPP and non-3GPP accesses specified in TS 23.401 [3] and TS 23.402 [4].
The study aims at producing recommendations for the following aspects:
- 3GPP work item and specification structure;
- charging requirements and principles;
- charging architecture and charging scenarios; and
- charging data and protocols.
The aspect of charging requirements and principles includes the study of the reuse of 3GPP Release 7 charging specifications.
|
33.820
|
Security of Home Node B (HNB) / Home evolved Node B (HeNB)
|
TR
|
8.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.820/33820-830.zip
|
The present document identifies special security threats of H(e)NB and study the countermeasures to these threats.
The study should include, but not be limited to, threat analysis of H(e)NB, mutual authentication and security protection between H(e)NB and rest of network, maintenance of the security context between H(e)NB and rest of network, security requirements on the H(e)NB, provisioning of security credentials on the H(e)NB, security solution for verifying the location of the H(e)NB etc.
With regard to security protection between the H(e)NB and the rest of the network, bandwidth efficiency should be taken into consideration.
|
33.822
|
Security aspects for inter-access mobility between non 3GPP and 3GPP access network
|
TR
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.822/33822-800.zip
|
This document studies the security architecture, i.e. the security features and the security mechanisms for inter-access mobility between 3GPP access system and non-3GPP access systems. For the general architecture for inter-access mobility cf. TR 23.882. This report is meant to provide more detail on the security aspects of inter-access mobility.
The scope should be extended to the mobility between two non-3GPP access systems, which interwork with 3GPP core entities. An example would be the mobility between two WLAN access systems providing 3GPP IP access.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.402 [14]. This TR may therefore be useful to better understand the basis on which decisions in TS 33.402 [14] were taken, and which alternatives were under discussion. However, none of the text in this TR shall be quoted as reflecting 3GPP’s position in any way. Rather, 3GPP’s position on security for non-3GPP access to EPS is reflected in the normative text in TS 33.402 [14]. Information in the TR may be inaccurate and outdated. One example of outdated text can be found in clauses 4.1 and 4.2 on alternatives for authentication protocols. The choices of authentication protocols finally made by 3GPP can be found in TS 33.401 [13] and TS 33.402 [14] respectively.
|
22.273
|
TISPAN; Multimedia Telephony with PSTN/ISDN simulation services
|
TS
|
7.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.273/22273-710.zip
|
The present document defines the requirements for multimedia telephony services which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities.
An important aspect of the Multimedia Telephony with PSTN/ISDN Simulation service is to provide PSTN/ISDN like services. Nevertheless the requirements are independent of the media that is used during the communication.
The present document covers part of the transition from PSTN/ISDN to an NGN. Interconnection between the existing networks and a TISPAN NGN is also covered.
The present document only provides requirements for services using IMS. Services provided by a TISPAN NGN to support legacy terminals and interfaces (PSTN/ISDN emulation) are defined in existing PSTN/ISDN documents. Requirements for PSTN/ISDN Emulation are out the scope of the present document and are described in other documents.
New NGN services are out the scope of the present document and are described in other documents. The applicability of PSTN/ISDN simulation services to services other than Multimedia Telephony (e.g. instant messaging) is not defined. Some PSTN/ISDN simulation services (for example communication waiting) are clearly not applicable to some real-time communication services.
The requirements in the present document are described from the user point of view to assist in the transition of phone services to IP multimedia services with a similar behaviour. The requirements do not take into account capabilities of existing protocols. The evolution or modifications to these protocols are beyond the scope of the present document.
|
22.495
|
TISPAN;Services and Capabilities Requirements
|
TS
|
7.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.495/22495-700.zip
|
The present document specifies network requirements in terms of service-related capabilities for a TISPAN NGN incorporating an IMS. The present document places requirements for TISPAN NGN Release 1 subsystems.
The present document provides generic requirements for services and interoperability in a TISPAN NGN incorporating an IMS in terms of the capabilities for a network or networks.
Requirements on service-related subsystems provide sufficient detail for architecture, networking requirements and protocols to be specified.
Specific service requirements may be contained in other documents, as identified in the present document, and by other documents referencing the present document.
The present document does not define services, only capabilities and requirements. The present document does not place requirements on terminals or other customer-owned equipment. The present document specifies the
service-related requirements on an IMS that are used to determine the network architecture, requirements and control protocols for a network interface to a customer environment.
NOTE: The present document uses the term "NGN" only in the context of ETSI TISPAN.
|
22.811
|
Review of network selection principles
|
TR
|
7.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.811/22811-720.zip
|
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.
Potential changes shall be described to the selection mechanism to provide a better user and network operator experience.
The present document is applicable to both GERAN and UTRAN.
|
23.206
|
Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2
|
TS
|
7.5.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.206/23206-750.zip
|
The present document specifies the functional architecture and information flows of the Voice Call Continuity feature which provides the capability to transfer the path of an existing voice call between a 3GPP CS system (GSM/UMTS) and IMS, and vice versa. These capabilities were designed per requirements in TS 22.101 [20].
|
23.406
|
TISPAN; IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.228 v7.2.0, modified]
|
TS
|
7.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.406/23406-720.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 23.228 "IP Multimedia Subsystem; Stage 2, version 7.2.0".
The present document provides the necessary adaptions to the 3GPP IP Multimedia Core Network Subsystem (IMS), in order to support the Access Networks and terminals in the scope of the present NGN Release.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.