id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
29.816
|
Study on PCRF failure and restoration
|
TR
|
10.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.816/29816-a00.zip
|
The present document contains the results of the study on PCRF failure and restoration.
Target failure and recovery scenarios are detailed; the following scenarios are addressed (incl. roaming):
- Single PCRF deployment (covering also the equivalent scenario of multiple PCRFs with a fixed assignment of PCRFs);
- Multiple PCRFs and the DRA is used;
PCRF node failures of different type (e.g. complete outage, loss of dynamic data) and the aspect of reliability in signaling connections will be studied.
Functional requirements for solutions to handle such cases in a standardized way are defined, considering the network elements PCRF, PCEF, BBERF, AF and DRA and taking operators’ preferences into account (e.g. minimal impact on user experience versus maximal control/minimum risk for the operator).
The study describes the potential solutions, which include procedures and signalling between PCRF and other PCC related network nodes, and procedures and signalling between Diameter clients (i.e. PCEF/BBERF/AF) and the DRA.
Per solution the impacted 3GPP specifications and the necessary changes therein are listed.
The study report finally evaluates the solutions and draws conclusions with respect to the type of solutions and their feasibility in terms of implementation effort/complexity.
|
30.820
|
Telecommunication management; Project scheduling and open issues for SA5, Release 10
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.820/30820-a00.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
Status list of Work items can be found in Annex A of the present document.
|
31.828
|
UICC access to IMS
|
TR
|
10.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.828/31828-a00.zip
| |
32.825
|
Telecommunication management; Charging management; Rc reference point study
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.825/32825-a00.zip
|
The present document is a study report for Rc reference point supported by ABMF (Accounting Balance Management Function).
The study covers the drive and requirement analysis, existing architectures, key issues analysis, recommandations, etc.
The study aims at producing recommendations for the following aspects:
- 3GPP work item and specification;
- Charging requirements and principles;
- Charging architecture and Rc networking scenarios;
- Charging data and protocols;
- Technical recommandations
|
32.826
|
Telecommunication management; Study on Energy Savings Management (ESM)
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.826/32826-a00.zip
|
In the context of 3GPP Self-Organizing Networks (SON), this study investigates about Energy Savings Management in LTE / SAE networks, with the objective to contribute to the protection of our environment and the environment of future generations. One is forced to admit that, in addition, network energy consumption reduction will enable mobile network operators to save their OPEX.
The present document covers:
• Motivations of mobile network operators for the introduction of energy savings control mechanisms
• Analysis of possible mechanisms for Energy Savings Management via OAM
• Usage of existing IRPs to be used for the purpose of Energy Savings Management
• Identification of new IRP to be potentially defined
• Conclusions
• Recommendations on Energy Savings Management
• Identification of items for standardization as a result of this study
|
32.827
|
Telecommunication management; Integration of device management information with Itf-N
|
TR
|
10.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.827/32827-a10.zip
|
UE Management provides the network operator with the opportunity to manage and monitor the actual user experience of their subscribers via the remote management of the user equipement.
UE management over Itf-N provides the ability to minimize the complexibity and reduce the OPEX and CAPEX costs of managing the UE by the ingegrated management capabilities.
UE management over Itf-N provides the capabilites for service provisioning and personalized subscriber profile backup for the UE via DMS, to improve the subscriber satisfaction and thus contribute to subscriber retention.
The UE can provide measurments of the quality of radio network and the actual service being delivered to the user, collection of these measurements via Itf-N can be used by Centralized SON or manual optimization.
This document is to study UE management over Itf-N, including the following aspects:
- Subscriber profile configuration over Itf-N;
- Collection of UE measurements over Itf-N. Includes protocol definition over Itf-N and study of appropriate UE measurements defined in RAN WGs;
- Retrieval of UE measurement logs over Itf-N. Includes file format definition over Itf-N and study of appropriate solutions for measurement logging policy configuration and log retrieval over Itf-N.
To support the UE measurement log collection via Itf-N, this document will study how to support the UE measurement log transfer mechanisms measurement logging policy configuration and measurement log retrieval by DMS using existing UE management protocol procedures, and identify a suitable protocol from a network management perspective. This document will also study how to do the mapping between the selected protocol and Itf-N.
|
32.828
|
Telecommunication management; Study on alignment of 3GPP generic Network Resource Model (NRM) Integration Reference Point (IRP) and the TeleManagement Forum (TMF) Shared Information/Data (SID) model
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.828/32828-a00.zip
|
The present document studies how to allow the two organizations (3GPP and TMF) to evolve their respective NRMs and SID in a manner that they would become aligned to support consistent and integrated management of mobile and fixed networks. This study:
• identifies the non-aligned, contradicting or overlapping parts between NRMs and SID
• identifies the non-aligned, contradicting or overlapping parts regarding specification methodology
• proposes possibilities to align the parts identified above;
• ensures that the proposal allows usage of the 3GPP Generic NRM IRP independently of SID
• ensures that the proposal allows usage of mobile specific NRMs to be used as they are
• drives the alignment process with TMF
• identifies any required changes in the 3GPP specifications
• identifies required changes in the TMF specifications to be communicated to the TMF
• ensures that 3GPP remains full owner of the aligned part of the NRM specifications
• defines a procedure how aligned specifications can be maintained and updated in a consistent manner
Special emphasis has been given to the borderline between generic and harmonized part and the network technology specific parts of the models. In case new requirements had been identified during the alignment process, they have been taken into account as well.
It is not intended to add the mobile specific parts of the 3GPP Network Resource Models to the TMF SID.
These model aspects are published by 3GPP only. Interface aspects (e. g. the Alarm IRP) are outside of the scope of this Study.
|
32.829
|
Telecommunication management; Study on alignment of 3GPP alarm Integration Reference Point (IRP) and TeleManagement Forum (TMF) Interface Program (TIP) fault management
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.829/32829-a00.zip
|
The present document collects, compares and analyzes the specifications of Fault Management (FM) as defined by 3GPP and TMF. These two organizations have both a complete set of FM specifications consisting of requirement, technology-independent and solution set specification for
- Fault Management interface – operations and notifications and
- Alarm content
The present documentidentifies similarities and differences of the Fault Management capabilities in 3GPP and TMF and provides recommendations to align these capabilities.
|
32.831
|
Telecommunication management; Study on alignment of 3GPP Performance Management (PM) and TeleManagement Forum (TMF) Interface Program (TIP) Performance Management
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.831/32831-a00.zip
|
The present document provides consistent and aligned PM and PM interfaces in 3GPP and TMF. The present document:
• identifies similarities and differences of the PM capabilities in 3GPP and TMF TIP PM BA;
• proposes enhancements to 3GPP PM solutions for converged networks and to satisfy TMF TIP PM BA requirements;
• identifies any required changes in the 3GPP specifications;
• identifies any required changes in the TMF specifications (to be communicated to TMF).
Backwards compatibility of the PM IRP should be maintained as much as possible by re-using existing specifications to the maximum extent.
The counter collected by each of the Network Elements (NE) and the definition of those are NE specific and there is no intention to harmonize those.
However KPIs with a network view should be explored.
|
32.832
|
Telecommunication management; Study on alarm correlation and alarm root cause analysis
|
TR
|
10.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.832/32832-a00.zip
|
The present document:
• defines the management services offered by Alarm Correlation (AC) process and alarm root cause analysis (ARCA) process;
• Identifies the benefits of the AC process and ARCA process from views of network operators;
• Identifies the possible locations of the AC and ARCA processes within the IRP framework.
• Identifies possible IRP standard solutions, including enhancement of existing IRP standard solutions.
|
34.172
|
Terminal conformance specification; Assisted Global Navigation Satellite Systems (A-GNSS); Frequency Division Duplex (FDD)
|
TS
|
10.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.172/34172-a20.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) that supports Assisted Global Navigation Satellite Systems (A-GNSS). It includes the measurement procedures for the conformance test of both UE‑based and UE‑assisted A‑GNSS. It excludes performance requirements for UEs where the only A-GNSS supported is A-GPS L1C/A which are specified in TS 34.171 [26].
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.807
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.807/36807-a00.zip
|
The purpose of the present document is to summarize the study of radio requirements for the User Equipment (UE) radio transmission and reception as part of the Rel-10 work item on;
a) Carrier Aggregation for LTE (CA)
b) Enhanced DL Multiple Antenna Transmission for LTE (DLMA)
c) UL Multiple Antenna transmission for LTE (ULMA)
d) Fixed Wireless CPE RF Requirements (CPE)
|
36.808
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Carrier Aggregation; Base Station (BS) radio transmission and reception
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.808/36808-a10.zip
|
The purpose of this TR is to summarize the study of radio requirements for the Base Station (BS) radio transmission and reception as part of the Rel-10 work item on Carrier Aggregation for LTE (CA).
|
36.811
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Adding 2 GHz band LTE Frequency Division Duplex (FDD) (Band 23) for Ancillary Terrestrial Component (ATC) of Mobile Satellite Services (MSS) in North America
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.811/36811-a00.zip
|
The present document is a technical report for Adding 2 GHz LTE for ATC of MSS in North America work item, which was approved at 3GPP TSG RAN#47 [2]. The objective of this work item is to add the 2 GHz band LTE for ATC of MSS in North America to the appropriate 3GPP core specifications for LTE FDD networks. 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.812
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE TDD 2600MHz in US work item Technical Report
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.812/36812-a10.zip
|
The present document is a technical report of the LTE TDD in 2600MHz for US work item which was approved at TSG RAN #47 [2]. The objective of this work item is to provide specification support for LTE TDD in the 2496 to 2690MHz band in the US.
The report provides motivation for requirements and a list of recommended changes to the specifications.
|
36.813
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE L-Band Technical Report
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.813/36813-a10.zip
|
The present document is a technical report for “Adding L-Band LTE for ATC of MSS in North America” work item, which was approved at 3GPP TSG RAN#48 [2]. The objective of this work item is to add L-Band to the appropriate 3GPP core specifications for LTE FDD networks. 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.817
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Uplink multiple antenna transmission; Base Station (BS) radio transmission and reception
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.817/36817-a00.zip
|
The purpose of this TR is to summarize the study of radio requirements for the Base Station (BS) radio transmission and reception as part of the Rel-10 work item on Uplink Multiple Antenna Transmission for LTE (LTE UL MIMO).
|
37.801
|
UMTS-LTE 3500 MHz Work Item Technical Repor
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.801/37801-a00.zip
|
The present document is a technical report of the UMTS-LTE 3500 MHz work item, which was established at TSG RAN#38. The objective of the work item is to study current band plans in the frequency bands 3.4-3.6 GHz and 3.6-3.8 GHz, where they exist, with respect to feasibility for WCDMA as well as LTE. For these current band plans, suitable band arrangements, which are adopted by regulators, shall be identified for the purpose of developing specifications, without excluding other future arrangements.
|
37.802
|
Multi-standard radio Base Station (BS) Radio Frequency (RF) requirements for non-contiguous spectrum deployments
|
TR
|
10.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.802/37802-a10.zip
|
The present document is the technical report for the work item on Multi-standard radio Base Station RF requirements for non-contiguous spectrum deployments, which was approved at TSG RAN#48. The objective of the WI is to specify RF requirements for MSR specifications such that common RF components can be used for multi-RAT deployments where more than one spectrum block is in use, and where the blocks are non-contiguous in frequency within a band.
|
51.010-5
|
Mobile Station (MS) conformance specification; Part 5: Inter-Radio-Access-Technology (RAT) (GERAN / UTRAN) interaction Abstract Test Suite (ATS)
|
TS
|
10.21.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-5/51010-5-al0.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, for the digital cellular telecommunications systems.
The present document is valid for MS implemented according to R99, 3GPP Release 4, Release 5, Release 6, Release 7, Release 8, Release 9 or Release 10.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications.
|
22.127
|
Service requirement for the Open Services Access (OSA); Stage 1
|
TS
|
9.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.127/22127-900.zip
|
This document specifies the stage 1 requirements for realisation of an Open Service Access (OSA).
OSA enables applications to make use of network functionality through an open standardised interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applications implementing the services become independent from the underlying network technology.
Applications which make use of network functionality offered through the OSA interface are not standardised by 3GPP.
The network functionality offered through the OSA interface may or may not be standardised by 3GPP.
OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the Virtual Home Environment (VHE) concept to be realised.
|
23.198
|
Open Service Access (OSA); Stage 2
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.198/23198-900.zip
|
The present document specifies the stage 2 of the Open Service Access (OSA).
|
23.820
|
Study of IMS restoration procedures
|
TR
|
9.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.820/23820-900.zip
|
The present document identifies the changes required in the 3GPP IMS specifications so that a consistent state is restored in the IMS Core Network, after, or during a planned, or unplanned stop of a network element. The study will go through the following steps:
• Establish the requirements that should be covered with these procedures. That is which are the impacts to the end user service that are acceptable and which are not, after a network failure.
• List the service interruption scenarios that need to be studied.
• Provide solutions, so that in all the service interruption scenarios listed, the impacts to the end user service comply with the requirements. These solutions provide procedures for the automatic restoration to a consistent state in the network and indicate how to trigger these procedures.
• Analyze the impacts of the solutions in the current specifications.
• Conclusion and recommended way forward.
It is important to realise that these procedures are meant to be operational procedures for restoration and so care must be taken with what is existing and will exist with OA&M procedures to avoid overlap which could cause clashes.
|
23.826
|
Feasibility study on Voice Call Continuity (VCC) support for emergency calls
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.826/23826-900.zip
|
This document contains the results of the feasibility study into the architectural requirements and alternatives for the support of active voice call continuity between Circuit Switched (CS) domain and the IP Multimedia Subsystem (IMS) for emergency calls. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The Feasibility Study considers different solutions for offering voice call continuity for emergency calls when users move between the GSM/UMTS CS Domain and the IP Connectivity Access Network (e.g., WLAN interworking) with home IMS functionality. The objective is to identify an architectural solution that allows completely automatic connectivity to the correct PSAP (from the end-user point of view) as specified in TS 23.167 [4], and allow for the possibility of a domain transfer as specified in TS 23.206 [3]. The study will also identify configuration impacts upon existing networks in order to realize the desired functionality.
Existing solutions developed by the 3GPP (e.g. 3GPP system to Wireless Local Area Network Interworking (I-WLAN)) should be reused as much as possible.
|
23.830
|
Architecture aspects of Home Node B (HNB) / Home enhanced Node B (HeNB)
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.830/23830-900.zip
|
This Technical Report describes the architectural aspects of specific UTRAN and E-UTRAN base stations, known as Home NodeBs and Home eNodeBs, which provide services in e.g. residential or enterprise deployments.
NOTE: This feasibility study has led to normative modifications of various specifications; the contents of this technical report should therefore be considered out of date.
To achieve this, the objectives are to (a) document the architectural assumptions taken by other working groups as part of their previous and ongoing work on Home Node B/Home eNodeB and Closed Subscriber Groups (CSG), and to (b) identify any outstanding issues not properly addressed in Rel-8.
Starting from the resulting architectural baseline, the intention is to derive architectural requirements arising from the outstanding Rel-8 issues and the Rel-9 requirements on Home NodeB and Home eNodeB as laid down by SA WG1 in TS 22.220 [2]. Based on this, the objective is to discuss and conclude on solutions for the architectural issues arising from those requirements.
|
23.838
|
IP Multimedia Subsystem (IMS) service continuity enhancements; Service, policy and interaction; Stage 2
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.838/23838-900.zip
|
This technical report intends to develop enhancements for Rel-8 IMS Service Continuity and solutions for mobility of media flows and control of a session between different devices under the same subscription (i.e. Inter-UE Transfer) to a state where they can be transferred to normative specifications, focusing on the following aspects:
For Inter-UE transfer:
- Inter-UE Transfer scenarios for transferring/retrieval/addition/deletion of media flows in a Collaborative Session;
- Inter-UE Transfer scenarios for establishment or continuation of a Collaborative Session while transferring control;
- Transferring media flows to the target UE whilst keeping the Collaborative Session control in the source UE.
For IMS Service Continuity Enhancement:
- Management of operator policy and user preferences;
- Interaction and coexistence with underlying mobility mechanisms and corresponding policies;
- Further capabilities for the support of mid-call services during session transfer, in addition to those defined in TS 23.292 [6], TS 23.237 [5] and TS 23.216 [6];
- Session Continuity for speech and video over CS.
IMS Service Continuity will be restricted to service continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN level are not within the scope of this document This document does not overlap with the underlying EPC and SRVCC features, even though there could be cross-references between the corresponding Technical Specifications.
|
23.868
|
Feasibility study on extension of support for IP Multimedia Subsystem (IMS) emergency calls
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.868/23868-900.zip
|
The present document provides a study investigating possible limitations of the solution for IMS emergency calls defined for Rel-7 in TS 23.167 [2], as well as possible extensions of that solution to reduce or eliminate some or all of the identified limitations.
The study item is expected mainly to concern IMS although some aspects of IP-CAN support may also be included. The study item has the following objectives
- Evaluate the feasibility of supporting IMS emergency calls for combinations of IP access network A and IMS core network B not supported in Rel-7 including but not limited to the following cases:
- A is any IP access network and B is the home 3GPP compliant IMS network for any emergency calling UE with adequate security credentials
- A is any IP access network and B is a visited 3GPP compliant IMS network for any emergency calling roaming UE with adequate security credentials
Additional user cases may also be proposed and evaluated during the SI if deemed applicable.
- Evaluate other enhancements to the solution for IMS emergency calls in Release 7 that may improve performance and/or reduce complexity
- Evaluate the feasibility of better aligning the solution in TS 23.167 [2] with applicable IETF standards and draft standards (e.g. from the Ecrit and Geopriv working groups)
- Any enhancement to the support of IMS emergency calls shall remain backward compatible to the solution in Rel-7 from the perspective of the UE and any 3GPP network element. Furthermore, any enhancement should be based on the solution in Rel-7 and should avoid unnecessarily adding new network entities, protocols and interfaces and moving existing functions from one entity to another.
The study item is expected to enable SA WG2 to decide which of the above objectives if any may be worth supporting in Rel-8 and which extensions to the current solution would then be appropriate.
|
23.869
|
Support for Internet Protocol (IP) based IP Multimedia Subsystem (IMS) Emergency calls over General Packet Radio Service (GPRS) and Evolved Packet Service (EPS)
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.869/23869-900.zip
| |
23.870
|
Single Radio Voice Call Continuity (SR-VCC) support for IMS Emergency Calls
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.870/23870-900.zip
|
SRVCC as specified in TS 23.216 [3], provides handover of voice calls from E-UTRAN/HSPA to UTRAN/GERAN or from E-UTRAN to CDMA2000 1x. SRVCC of IMS emergency calls is not supported in TS 23.216 [3], and thus handover of such calls will have unpredictable effects, in the worst case causing the call to fail. This is a serious concern for operators and their subscribers, and may cause regulatory violations in some parts of the world.
Therefore, the objective of this document is to study both the EPS and IMS aspects of how to best support the handover of ongoing emergency calls for the following scenarios:
- E-UTRAN to UTRAN/GERAN CS.
- HSPA to UTRAN/GERAN CS.
- E-UTRAN to CDMA2000 1x CS.
|
23.879
|
Study on Circuit Switched (CS) domain services over evolved Packet Switched (PS) access
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.879/23879-900.zip
|
The present document contains the results of the study of the architectural requirements of CS Domain Services over evolved PS access and concludes with a way forward. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to describe an architecture that is capable of extending the 'traditional' MSC-Server based set of CS voice, supplementary and value-adding services and business principles (e.g. for roaming and interconnect) to the evolved PS access. The intention is also to give a CS handover-like user experience for voice calls when changing between evolved PS and legacy CS accesses. The architecture will however not be limited to the provision of speech services over evolved PS accesses; on the contrary, through the exploitation of the Combinational services, it will be possible to harness the capabilities of IMS to provide new, innovative services to the end user. Handover of the parallel PS session towards legacy 3GPP access will be considered as well, but may be limited by the capabilities of the legacy system and operator preferences.
Co-existence with IMS centric Single Radio VCC solutions shall be studied as well.
|
23.883
|
Study on enhancements to IMS Centralized Services (ICS)
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.883/23883-900.zip
|
The following aspects of IMS Centralized Services (ICS), though studied in Release 8 (and to some extent documented in TR 23.892 [2]), required further study and are herein documented:
- ICS supplementary service data management (e.g. Supplementary Services data synchronization).
- Management of Telephony Application Server (TAS) user configuration for an ICS UE when PS access cannot be used.
Consideration shall be given to attaining a consistent user experience, and managing and enforcing operator policies as well as user preferences. Heterogeneous access technologies over which the IMS service is provided shall also be taken into account.
|
23.891
|
Evaluation of LCS Control Plane Solutions for EPS
|
TR
|
9.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.891/23891-900.zip
|
This TR studies various alternatives for the stage 2 control plane LCS Reference Architecture for Evolved Packet Core.
This document does not document the radio signal measure and/or position methods for the E-UTRAN. Those are addressed in RAN specifications.
|
25.866
|
1.28 Mcps TDD Home Node B (HNB) study item technical report
|
TR
|
9.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.866/25866-900.zip
|
This document is a technical report of the 1.28Mcps TDD Home NodeB study item, which was approved in TSG RAN#41.
The goal of this study item is,
- To characterise the 1.28Mcps TDD Home NodeB environment.
- To determine the feasibility of a solution and to outline any obstacles for providing high data rate low cost services in home NodeB environment.
- 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.907
|
Evaluation of path-loss technologies for Location Services (LCS)
|
TR
|
9.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.907/25907-901.zip
|
<Editor's note: Text in this section is cited from the original text in 'Annex A.1 Overview'>
Path-loss technologies cover a broad scope of specific location technologies, including: RSSI Trilateration technologies, certain Enhanced Cell-ID technologies, and RF pattern matching technologies. For the purposes of this Study Item, individual technology groups to be evaluated will be treated independently as Annexes to the TR.
In this TR, Annex.A should:
- Describe pattern matching and outline it's benefits and challenges.
- Illustrate the required messaging to support RF pattern matching technologies, as well as the projected performance improvements associated with additional messaging/measurement support.
- Confirm the performance capability of RF pattern matching Technology on the UMTS air-interface, over all environments. Both in terms of accuracy and location result latency:
- Dense Urban
- In-Building
- Rural
- Illustrate the Standardized architecture for RF pattern matching technologies as related to the UMTS and future air interfaces.
- Provide an outline of anticipated standardization requirements for improved performance and interoperability of RF pattern matching technologies.
- Provide a conclusion based on the information contained herein and a recommendation to the 3GPP regarding standardization of RF pattern matching Technologies within the RAN.
|
25.913
|
Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)
|
TR
|
9.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.913/25913-900.zip
|
This document is related to the technical report for the study item "Evolved UTRA and UTRAN" [1]. The objective of the study item is to develop a framework for the evolution of the 3GPP radio-access technology towards a high-data-rate, low-latency and packet-optimized radio access technology.
This document provides guidance and collects requirements which an evolved UTRA and UTRAN system should meet.
|
29.198-01
|
Open Service Access (OSA) Application Programming Interface (API); Part 1: Overview
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-01/29198-01-900.zip
|
The present document is the first part of the 3GPP Specification defining the Application Programming Interface (API) for Open Service Access (OSA), and provides an overview of the content and structure of the various parts of this specification, and of the relation to other standards documents.
The OSA-specifications define an architecture that enables service application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-02
|
Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-02/29198-02-900.zip
|
The present document is Part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Common Data definitions of the OSA. The Common Data definitions contain data-types that are common across the rest of the OSA API. All aspects of the Common Data are defined here, these being:
- Data definitions;
- IDL Description of the data types;
- WSDL Description of the data types;
- Reference to the Java™ API description of the data types.
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-03
|
Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-900.zip
|
The present document is Part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Framework aspects of the interface. All aspects of the Framework are defined in the present document, these being:
• Sequence Diagrams;
• Class Diagrams;
• Interface specification plus detailed method descriptions;
• State Transition diagrams;
• Data definitions;
• IDL Description of the interfaces.
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-04-1
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 1: Call control common definitions
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-1/29198-04-1-900.zip
|
The present document is Part 4, Sub-part 1 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the common definitions used by the Call Control Service Capability Features (SCF).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-04-2
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 2: Generic call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-2/29198-04-2-900.zip
|
The present document is Part 4, Sub-part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Generic Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Generic Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-04-3
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 3: Multi-party call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-3/29198-04-3-900.zip
|
The present document is Part 4, Sub-Part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi-Party Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Party Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-04-4
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 4: Multimedia call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-4/29198-04-4-900.zip
|
The present document is Part 4, Sub-part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi-Media Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Media Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-04-5
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 5: Conference call control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-5/29198-04-5-900.zip
|
The present document is Part 4, Sub-Part 5 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Conference call control Service Capability Feature (SCF) aspects of the interface. All aspects of the Conference call control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-05
|
Open Service Access (OSA) Application Programming Interface (API); Part 5: User interaction Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-900.zip
|
This document is Part 5 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the User Interaction (UI) Service Capability Feature (SCF) aspects of the interface. All aspects of the User Interaction SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-06
|
Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-900.zip
|
The present document is Part 6 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Mobility Service Capability Feature (SCF) aspects of the interface. All aspects of the Mobility SCF are defined here, these being:
- Sequence Diagrams
- Class Diagrams
- Interface specification plus detailed method descriptions
- State Transition diagrams
- Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-07
|
Open Service Access (OSA) Application Programming Interface (API); Part 7: Terminal capabilities Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-900.zip
|
The present document is part of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-08
|
Open Service Access (OSA) Application Programming Interface (API); Part 8: Data session control Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-900.zip
|
The present document is Part 8 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Data Session Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Data Session Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-10
|
Open Service Access (OSA) Application Programming Interface (API); Part 10: Connectivity manager Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-10/29198-10-900.zip
|
The present document is Part 10 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Connectivity Manager Service Capability Feature (SCF) aspects of the interface. All aspects of the Connectivity Manager SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-11
|
Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-900.zip
|
The present document is Part 11 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Account Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Account Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-12
|
Open Service Access (OSA) Application Programming Interface (API); Part 12: Charging Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-900.zip
|
The present document is Part 12 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Charging Service Capability Feature (SCF) aspects of the interface. All aspects of the Charging SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-13
|
Open Service Access (OSA) Application Programming Interface (API); Part 13: Policy management Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-13/29198-13-900.zip
|
The present document is part 13 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Policy Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Policy Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-14
|
Open Service Access (OSA) Application Programming Interface (API); Part 14: Presence and Availability Management (PAM) Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-14/29198-14-900.zip
|
The present document is part 14 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence and Availability Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Presence and Availability Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
|
29.198-15
|
Open Service Access (OSA) Application Programming Interface (API); Part 15: Multi-media Messaging (MM) Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-15/29198-15-900.zip
|
The present document is Part 15 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi Media Messaging Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi Media Messaging SCF are defined here, these being:
• Sequence Diagrams.
• Class Diagrams.
• Interface specification plus detailed method descriptions.
• State Transition diagrams.
• Data definitions.
• IDL Description of the interfaces.
• WSDL Description of the interfaces.
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-16
|
Open Service Access (OSA) Application Programming Interface (API); Part 16: Service broker Service Capability Feature (SCF)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-16/29198-16-900.zip
|
The present document is Part 16 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Service Broker Capability Feature (SCF) aspects of the interface. All aspects of the Service Broker SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-01
|
Open Service Access (OSA); Parlay X web services; Part 1: Common
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-01/29199-01-900.zip
|
The present document is Part 1 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Common aspects of the Parlay X Web Services. The following are defined here:
Name spaces.
Data definitions.
Fault definitions.
WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-02
|
Open Service Access (OSA); Parlay X web services; Part 2: Third party call
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-02/29199-02-900.zip
|
The present document is Part 2 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.127 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Third Party Call Web Service aspects of the interface. All aspects of the Third Party Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-03
|
Open Service Access (OSA); Parlay X web services; Part 3: Call notification
|
TS
|
9.3.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-03/29199-03-930.zip
|
The present document is Part 3 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Notification Web Service aspects of the interface. All aspects of the Call Notification Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-04
|
Open Service Access (OSA); Parlay X web services; Part 4: Short messaging
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-04/29199-04-900.zip
|
The present document is Part 4 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Short Messaging Web Service aspects of the interface. All aspects of the Short Messaging Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-05
|
Open Service Access (OSA); Parlay X web services; Part 5: Multimedia messaging
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-05/29199-05-900.zip
|
The present document is Part 5 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia Messaging Web Service aspects of the interface. All aspects of the Multimedia Messaging Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-06
|
Open Service Access (OSA); Parlay X web services; Part 6: Payment
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-06/29199-06-900.zip
|
The present document is Part 6 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Payment Web Service aspects of the interface. All aspects of the Payment Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-07
|
Open Service Access (OSA); Parlay X web services; Part 7: Account management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-07/29199-07-900.zip
|
The present document is Part 7 of the Stage 3 Parlay X Web Service specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Account Management Web Service aspects of the interface. All aspects of the Account Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-08
|
Open Service Access (OSA); Parlay X web services; Part 8: Terminal status
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-08/29199-08-900.zip
|
The present document is Part 8 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Status Web Service aspects of the interface. All aspects of the Terminal Status Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-09
|
Open Service Access (OSA); Parlay X web services; Part 9: Terminal location
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-09/29199-09-900.zip
|
The present document is Part 9 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Location Web Service aspects of the interface. All aspects of the Terminal Location Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-10
|
Open Service Access (OSA); Parlay X web services; Part 10: Call handling
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-10/29199-10-900.zip
|
The present document is Part 10 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Handling Web Service aspects of the interface. All aspects of the Call Handling Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-11
|
Open Service Access (OSA); Parlay X web services; Part 11: Audio call
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-11/29199-11-900.zip
|
The present document is Part 11 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Audio Call Web Service aspects of the interface. All aspects of the Audio Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The web service had been extended to support media.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-12
|
Open Service Access (OSA); Parlay X web services; Part 12: Multimedia conference
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-12/29199-12-900.zip
|
The present document is Part 12 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia Conference Web Service aspects of the interface. All aspects of the Multimedia Conference Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-13
|
Open Service Access (OSA); Parlay X web services; Part 13: Address list management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-13/29199-13-900.zip
|
The present document is Part 13 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Address List Management Web Service aspects of the interface. All aspects of the Address List Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-14
|
Open Service Access (OSA); Parlay X web services; Part 14: Presence
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-14/29199-14-900.zip
|
The present document is Part 14 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence Web Service aspects of the interface. All aspects of the Presence Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
|
29.199-15
|
Open Service Access (OSA); Parlay X web services; Part 15: Message broadcast
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-15/29199-15-900.zip
|
The present document is Part 15 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Message Broadcast Web Service aspects of the interface. All aspects of the Message Broadcast Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-16
|
Open Service Access (OSA); Parlay X web services; Part 16: Geocoding
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-16/29199-16-900.zip
|
The present document is Part 16 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Geocoding Web Service aspects of the interface. All aspects of the Geocoding Web Service are defined here, these being:
• Name spaces
• Sequence diagrams
• Data definitions
• Interface specification plus detailed method descriptions
• Fault definitions
• Service policies
• WSDL Description of the interfaces
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-17
|
Open Service Access (OSA); Parlay X web services; Part 17: Application-driven Quality of Service (QoS)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-17/29199-17-900.zip
|
The present document is Part 17 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Application-driven Quality of Service (QoS) Web Service aspects of the interface. All aspects of the Application-driven QoS Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-18
|
Open Service Access (OSA); Parlay X web services; Part 18: Device capabilities and configuration
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-18/29199-18-900.zip
|
The present document is Part 18 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Device Capabilities and Configuration Web Service aspects of the interface. All aspects of the Device Capabilities and Configuration Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-19
|
Open Service Access (OSA); Parlay X web services; Part 19: Multimedia streaming control
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-19/29199-19-900.zip
|
The present document is Part 19 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia streaming control Web Service aspects of the interface. All aspects of the Multimedia streaming control Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-20
|
Open Service Access (OSA); Parlay X web services; Part 20: Multimedia multicast session management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-20/29199-20-900.zip
|
The present document is Part 20 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-21
|
Open Service Access (OSA); Parlay X web services; Part 21: Content management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-21/29199-21-900.zip
|
The present document is Part 21 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-22
|
Open Service Access (OSA); Parlay X web services; Part 22: Policy
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-22/29199-22-900.zip
|
The present document is Part 22 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Policy Web Service aspects of the interface. All aspects of the Policy Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
|
29.998-01
|
Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-900.zip
|
The present document is suggesting a mapping of the Application Programming Interface (API) for Open Service Access (OSA) onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations, and provides an overview of the content and structure of the various parts of the present document. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative and not normative.
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].
|
29.998-04-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-900.zip
|
The present document investigates how the OSA Call Control Interface Class methods defined in 3GPP TS 29.198-4 [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 APIs. 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].
|
29.998-04-4
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 4: Multiparty Call Control ISC
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-900.zip
|
The present document investigates how the OSA Call Control Interface Class methods defined in [5] can be mapped onto SIP methods.
The mapping of the OSA API to the SIP 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 APIs. 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].
|
29.998-05-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-900.zip
|
The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part 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 APIs. 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].
|
29.998-05-4
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-900.zip
|
The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations, within the context of SMS. 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].
|
29.998-06-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User location - user status service mapping; Subpart 1: Mapping to Mobile Application Part (MAP)
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-1/29998-06-1-900.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].
|
29.998-06-2
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User location - user status service mapping; Subpart 2: Mapping to Session Initiation Protocol (SIP)
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-2/29998-06-2-900.zip
|
The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto IMS ISC Interface (SIP) operations.
The mapping of the OSA API to the SIP 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].
|
29.998-08
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 8: Data Session Control Service Mapping to CAP
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-900.zip
|
The present document investigates how the OSA Data Session Control Interface Class methods defined in 3GPP TS 29.198-8 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part 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 APIs. 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.819
|
Telecommunication management; Project scheduling and open issues for SA5, Release 9
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.819/30819-900.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
|
32.111-3
|
Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-910.zip
|
The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [6]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.111-2 V7.1.X.
|
32.111-5
|
Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-5/32111-5-900.zip
|
The present document specifies the XML Definitions for the Alarm Integration Reference Point (Alarm IRP) as it applies to Itf-N, in accordance with Alarm IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
The present document defines the XML syntax of Alarm IRP notifications that is to be used for the Alarm IRP SOAP Solution Set and in conjunction with Notification Log IRP XML Definitions for Notification Log IRP XML Data File and the NL IRP XML Notification Format [4]. The document defines also the XML syntax for the IOC definitions of the Alarm IRP IS [3], which are used by the XML definitions for the Alarm IRP notifications and the Alarm IRP IS operations.
This specification is related to 3GPP TS 32.111-2 V9.0.X.
|
32.111-7
|
Telecommunication management; Fault Management; Part 7: Alarm IRP SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-7/32111-7-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Alarm IRP: Information Service (3GPP TS 32.111-2 [4]).
This Solution Set specification is related to 3GPP TS 32.111-2 V9.0.X.
|
32.123
|
Telecommunication management; Advanced Alarm Management (AAM) 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.123/32123-900.zip
|
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the AAM IRP CORBA Solution Set, whose semantics are specified in AAM IRP Information Service (3GPP TS 32.122 [3]).
This Solution Set specification is related to TS 32.122 v9.0.0.
|
32.125
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.125/32125-930.zip
|
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the AAM IRP XML file format definition, whose semantics are specified in AAM IRP Information Service (3GPP TS 32.122 [3]).
This file format definition specification is related to TS 32.122 v9.0.X.
|
32.127
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.127/32127-910.zip
|
The present specifies the SOAP Solution Set for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 [3]).
This Solution Set specification is related to TS 32.122 v9.0.X.
|
32.175
|
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.175/32175-930.zip
|
The purpose of this Subscription Management (SuM) Network Resource Model IRP XML definition is to define the mapping of the IRP information model (see TS 32.172 [5]) to the protocol specific details necessary for implementation of this IRP in an XML environment.
This specification is related to 3GPP TS 32.172 V9.3.X.
|
32.303
|
Telecommunication management; Configuration Management (CM); Notification 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.303/32303-900.zip
|
The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [5]).
This Solution Set specification is related to 3GPP TS 32.302.
|
32.305
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); eXtensible Markup Language (XML) definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.305/32305-900.zip
|
The present document specifies the XML Definitions for the Notification Integration Reference Point (Notification IRP) as it applies to Itf-N, in accordance with Notification IRP IS definitions [3].
This XML Definitions specification defines the Notification IRP XML Notification header format.
This specification is related to 3GPP TS 32.302 V9.0.X.
|
32.307
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.307/32307-920.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [4]).
This Solution Set specification is related to 3GPP TS 32.302 V9.0.X.
|
32.313
|
Telecommunication management; Generic Integration Reference Point (IRP) management; Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.313/32313-900.zip
|
The present document specifies the CORBA Solution Set for Generic Integration Reference Point (IRP) management whose capabilities are specified in 3GPP TS 32.312 [1], the Generic IRP management: Information Service.
This Solution Set specification is related to TS 32.312 V9.0.X.
|
32.317
|
Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.317/32317-910.zip
|
The present document specifies the SOAP Solution Set for Generic IRP management whose capabilities are specified in Generic IRP management: Information Service (3GPP TS 32.312 [1]).
This Solution Set specification is related to TS 32.312 V9.0.X.
|
32.323
|
Telecommunication management; Test management 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.323/32323-900.zip
|
The present document specifies the CORBA SS for the IRP whose semantics is specified in Test Management IRP IS (3GPP TS 32.322 [6]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to 3GPP TS 32.322 V9.0.X.
|
32.325
|
Telecommunication management; Test management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.325/32325-900.zip
|
The present document specifies the XML Definitions for the Test Management IRP (TMIRP) as it applies to Itf-N, in accordance with TM IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.322 V9.0.X.
|
32.327
|
Telecommunication management; Test management Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.327/32327-900.zip
|
The present document specifies the SOAP SS for the IRP whose semantics is specified in Test Management IRP IS (3GPP TS 32.322 [5]).
This Solution Set specification is related to 3GPP TS 32.322 V9.0.X.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.