Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.335  Word version:  17.0.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 7

The present document specifies the stage 3 of the Ud interface between the Front-Ends (FEs) and the User Data Repository (UDR) in the User Data Convergence (UDC architecture).
This 3GPP Technical Specification (TS) specifies the protocol and interactions between the FE and the UDR for Ud reference point, in particular:
  • The details of the LDAP protocol that are to be considered
  • The details of the SOAP envelope that provide support for subscriptions to notifications and notifications about data changes service (S/N operations).
The User Data Convergence Stage 2 description (architecture and information flows) is specified in TS 23.335.
The UDR data model used with LDAP (i.e. attributes, object classes and directory information tree) is implementation specific and is left outside the scope of 3GPP specifications. For multivendor interoperability between FEs and UDR specific integration projects are needed. Some examples of Ud data models are described in TR 29.935.
Up

2  Referencesp. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TR 41.001: "GSM Release specifications".
→ to date, withdrawn by 3GPP
[3]
TR 21.912: (V3.1.0) "Example 2, using fixed text".
→ to date, withdrawn by 3GPP
[4]
RFC 4510:  "Lightweight Directory Access Protocol (v3)".
[5]
RFC 5805:  "Lightweight Directory Access Protocol (LDAP) Transactions".
[6]
W3C Recommendation "Simple Object Access Protocol (SOAP) 1.2": (27 April 2007). http://www.w3.org/TR/.
[7]  Void.
[8]
RFC 4511:  "Lightweight Directory Access Protocol (LDAP): The Protocol".
[9]
RFC 4528:  "Lightweight Directory Access Protocol (LDAP) Assertion Control".
[10]
TS 23.335: "User Data Convergence (UDC); Technical realization and information flows".
[11]
RFC 4512:  "Lightweight Directory Access Protocol (LDAP): Directory Information Models".
[12]
TS 32.182: "Telecommunication management; User Data Convergence (UDC); Common Baseline Information Model".
[13]  Void
[14]  Void
[15]
TS 33.210: "3G Security; Network Domain Security; IP network layer security".
[16]
RFC 4513:  "Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms".
[17]
National Institute of Standards and Technology, FIPS Pub 197: Advanced Encryption Standard (AES), 26 November 2001. .
[18]
OASIS "Directory Services Markup Language v2.0": (30 April 2002) http://www.oasis-open.org/.
[19]
TR 29.935: "Study on UDC Data Model".
[20]
OASIS " Web Services Security: SOAP Message Security 1.1 OASIS Standard Specification, 1 February 2006", https://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf.
[21]
OASIS "Web Services Security: "UsernameToken Profile 1.1 OASIS Standard Specification, 1 February 2006", https://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-UsernameTokenProfile.pdf.
Up

3  Definitions, symbols and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
LDAP Session:
starts with LDAP Bind Operation and ends with LDAP Unbind Operation or Notice of Disconnection.
Front End:
a core network functional entity or service layer entity or provisioning entity that can access user data stored in a unique repository.
Front End Identifier:
A name that uniquely identifies an FE within the set of all FEs accessing an UDR.
Front End Cluster:
FEs handling the same application may be grouped in clusters to differentiate between them e.g. with regard to geographical location, feature support, vendor, or other characteristics. All FEs within a cluster are treated equally for required purposes (e.g. authorization, notifications, etc.).
Application type:
The application handled by a FE (e.g. HLR) determines the application type of the FE. The application type is derived from the name indicated by a FE.
Front End Cluster Identifier:
A name that identifies a cluster grouped with FEs supporting the same application.
User Data Repository:
facility where user data can be accessed stored and managed in a common way.
Up

3.2  Symbolsp. 8

For the purposes of the present document, the following symbols apply:
Ud
reference point between a FE and the UDR

3.3  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
FE
Front End
UDR
User Data Repository
NDS
Network Domain Security

Up   Top   ToC