Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
TS 29.199-01
Open Service Access (OSA); Parlay X web services;
Part 1: Common
3GPP‑Page
ETSI‑search
ToC
↓
V9.0.0 (PDF)
2009/12 41 p.
V8.1.0
2009/10 41 p.
V7.2.0
2007/06 37 p.
V6.6.0
2007/06 35 p.
Rapporteur:
Mr. Unmehopa, Musa
full Table of Contents for
TS 29.199-01
Word version: 9.0.0
0
Introduction
p. 6
1
Scope
p. 8
2
References
p. 8
3
Definitions and abbreviations
p. 9
3.1
Definitions
p. 9
3.2
Abbreviations
p. 9
4
Use of Web Services technologies
p. 10
4.1
Web Service message content
p. 10
4.1.1
SOAP
p. 10
4.1.2
XML
p. 10
4.1.3
HTTP
p. 10
4.2
Web Service interface definitions
p. 10
4.2.1
WSDL
p. 10
4.3
Security for Parlay X Web Services
p. 10
4.4
XML data types
p. 10
5
Detailed service description
p. 11
5.1
Address data items
p. 11
5.2
Charging
p. 11
5.2.1
Charging data type
p. 11
5.3
Exception definition
p. 12
5.4
Service exception
p. 12
5.5
Policy exception
p. 13
6
Namespaces
p. 14
7
Sequence diagrams
p. 14
8
XML Schema data type definition
p. 14
8.1
TimeMetrics enumeration
p. 14
8.2
TimeMetric structure
p. 14
8.3
ChargingInformation structure
p. 14
8.4
ServiceError structure
p. 15
8.5
SimpleReference structure
p. 15
8.6
CallParticipantStatus enumeration
p. 15
8.7
CallParticipantTerminationCause enumeration
p. 15
8.8
CallParticipantInformation Structure
p. 15
8.9
CallSession Structure
p. 16
8.10
MediaInfo structure
p. 16
8.11
Media enumeration
p. 16
8.12
MediaDirection enumeration
p. 17
8.13
RetrievalStatus enumeration
p. 17
8.14
NameValuePair structure
p. 17
9
Web Service interface definition
p. 17
10
Fault definitions
p. 17
10.1
ServiceException
p. 17
10.1.1
SVC0001: Service error
p. 17
10.1.2
SVC0002: Invalid input value
p. 18
10.1.3
SVC0003: Invalid input value with list of valid values
p. 18
10.1.4
SVC0004: No valid address(es)
p. 18
10.1.5
SVC0005: Duplicate correlator
p. 18
10.1.6
SVC0006: Invalid group
p. 18
10.1.7
SVC0007: Invalid charging information
p. 18
10.1.8
SVC0008: Overlapping Criteria
p. 18
10.2
PolicyException
p. 19
10.2.1
POL0001: Policy error
p. 19
10.2.2
POL0002: Privacy error
p. 19
10.2.3
POL0003: Too many addresses
p. 19
10.2.4
POL0004: Unlimited notifications not supported
p. 19
10.2.5
POL0005: Too many notifications requested
p. 19
10.2.6
POL0006: Groups not allowed
p. 20
10.2.7
POL0007: Nested groups not allowed
p. 20
10.2.8
POL0008: Charging not supported
p. 20
10.2.9
POL0009: Invalid frequency requested
p. 20
10.2.10
POL0010: Retention time interval expired
p. 20
10.2.11
POL0011: Media Type not supported
p. 20
10.2.12
POL0012: Too many description entries specified
p. 20
10.2.13
POL0013: Addresses duplication
p. 21
10.3
Fault number ranges by service
p. 21
11
Service policies
p. 21
12
WSDL usage and style
p. 21
12.1
Service definition and documents
p. 22
12.1.1
Interface sets
p. 22
12.1.2
Preparing for document definition
p. 22
12.1.3
Documents
p. 23
12.1.3.1
Types definition document
p. 23
12.1.3.2
Shared faults document
p. 23
12.1.3.3
Service interface document
p. 23
12.1.3.4
Service bindings document
p. 23
12.1.4
Document separation rationale
p. 24
12.1.5
Document version identifier
p. 24
12.1.6
Document naming example
p. 24
12.1.7
Service definitions for notification patterns
p. 24
12.2
Namespaces
p. 25
12.2.1
Namespaces for Parlay X Web Services
p. 25
12.2.2
Use of namespaces
p. 25
12.2.3
Namespace elements
p. 25
12.2.4
Namespace Usage
p. 26
12.2.4.1
Why namespace versions are used
p. 26
12.2.4.2
When namespace versions are changed
p. 26
12.2.4.3
Benefit of managing namespace versions
p. 26
12.2.5
Common namespaces
p. 27
12.2.6
Target namespace
p. 27
12.2.7
WSDL and Schema namespaces
p. 27
12.2.8
Local namespace use
p. 28
12.2.9
Examples
p. 28
12.3
Authoring style - Document content and names
p. 28
12.3.1
General WSDL document information
p. 28
12.3.2
Names
p. 28
12.3.3
Case usage for names
p. 29
12.3.4
Naming conventions for special names
p. 29
12.3.5
Document layout
p. 29
12.4
Data type definitions
p. 30
12.4.1
Types section declaration
p. 30
12.4.1.1
Optional elements
p. 30
12.4.1.2
Nillable elements
p. 30
12.4.1.3
User defined simple data types
p. 30
12.4.1.4
Data structures
p. 30
12.4.1.5
Enumerations
p. 31
12.4.1.6
Unions
p. 31
12.4.1.7
Web Service references
p. 31
12.5
Messages and interfaces (PortTypes)
p. 32
12.5.1
Message Parts
p. 32
12.5.1.1
Document style Web Services
p. 32
12.5.2
Interfaces (PortTypes)
p. 32
12.5.3
Faults (Exceptions)
p. 32
12.6
Bindings and service definitions
p. 33
12.6.1
Binding
p. 33
12.6.2
Service definition
p. 33
13
Backward Compatibility Guidelines
p. 34
13.1
Implementation Guidelines for Server Programmers
p. 34
13.2
Implementation Guidelines for Client Programmers
p. 34
13.3
Removal of items from the specifications
p. 34
A
(Normative) WSDL for common data definitions
p. 36
B
Description of Parlay X Web Services Part 1: Common Definitions for 3GPP2 cdma2000 networks
p. 37
B.1
General Exceptions
p. 37
B.2
Specific Exceptions
p. 37
B.2.1
Clause 1: Scope
p. 37
B.2.2
Clause 2: References
p. 37
B.2.3
Clause 3: Definitions and abbreviations
p. 37
B.2.4
Clause 4: Use of Web Services technologies
p. 37
B.2.5
Clause 5: Detailed service description
p. 37
B.2.6
Clause 6: Namespaces
p. 38
B.2.7
Clause 7: Sequence diagrams
p. 38
B.2.8
Clause 8: XML Schema data type definition
p. 38
B.2.9
Clause 9: Web Service interface definition
p. 38
B.2.10
Clause 10: Fault definitions
p. 38
B.2.11
Clause 11: Service policies
p. 38
B.2.12
Clause 12: WSDL usage and style
p. 38
B.2.13
Annex A (normative): WSDL for common data definitions
p. 38
$
Change history
p. 39