Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.328  Word version:  18.1.0

Top   Top   None   None   Next
1…   6…

 

1  Scopep. 7

This 3GPP Technical Specification (TS) specifies:
  1. The interactions between the HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point.
  2. The interactions between the SIP AS and the SLF (Subscription Locator Function) and between the OSA SCS and the SLF. This interface is referred to as the Dh reference point.
The IP Multimedia (IM) Core Network Subsystem stage 2 is specified in TS 23.228 and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in TS 24.228.
The IP Multimedia (IM) Session Handling with the IP Multimedia (IM) call model is specified in TS 23.218.
This document addresses the signalling flows and message contents for the protocol at the Sh and Dh interface.
This document also addresses how the functionality of Ph interface is accomplished.
The Presence Service Stage 2 description (architecture and functional solution) is specified in TS 23.141.
Up

2  Referencesp. 7

[1]
TS 23.228: "IP Multimedia (IM) Subsystem - Stage 2".
[2]
TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP (Release 5)".
[3]
TS 23.002: "Network architecture".
[4]
TS 23.218: "IP Multimedia (IM) Session Handling; IP Multimedia (IM) call model".
[5]
TS 29.329: "Sh Interface based on Diameter - Protocol details".
[6]
TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements".
[7]
TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol ; Protocol details".
[8]  Void.
[9]
ITU-T recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[10]
TS 23.018: "Basic Call Handling; Technical realization".
[11]
TS 23.003: "Numbering, Addressing and Identification".
[12]
TS 23.032: "Universal Geographical Area Description (GAD)".
[13]
TS 29.002: "Mobile Application Part (MAP) specification".
[14]
TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2".
[15]
RFC 2045:  "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[16]
RFC 3261:  "SIP: Session Initiation Protocol".
[17]
RFC 3966:  "The tel URI for Telephone Numbers".
[18]
TS 23.141: "Presence Service; Architecture and Functional Description".
[19]
TS 23.012: "Location Management Procedures".
[20]
ANSI X3.4: "Coded Character Set - 7-bit American Standard Code for Information Interchange"
[21]  Void
[22]
TS 33.203: "Access Security for IP-based services".
[23]
RFC 791:  "Internet Protocol".
[24]
RFC 4291:  "IP Version 6 Addressing Architecture".
[25]
RFC 4412:  "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[26]
TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol ".
[27]
TS 23.008: "Organization of subscriber data".
[28]
TS 29.212: "Policy and Charging Control (PCC); Reference points".
[29]
TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2".
[30]
TS 29.118: "SGs interface specification".
[31]
TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol".
[32]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[33]
TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2".
[34]
TS 29.273: "3GPP EPS AAA interfaces".
[35]
RFC 4776:  "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information".
[36]
RFC 7683:  "Diameter Overload Indication Conveyance".
[37]
ETSI ES 283 034: "e4 interface based on the DIAMETER protocol".
[38]
TS 22.153: "Multimedia Priority Service".
[39]
TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP" - stage 3.
[40]
TS 29.364: "IP Multimedia Subsystem (IMS) Application Server (AS) service data description for AS interoperability".
[41]
RFC 5952:  "A Recommendation for IPv6 Address Text Representation".
[42]
RFC 7944:  "Diameter Routing Message Priority".
[43]
RFC 8583:  "Diameter Load Information Conveyance".
[44]
RFC 6733:  "Diameter Base Protocol".
[45]
TS 24.323: "3GPP IP Multimedia Subsystem (IMS) service level tracing management object (MO)".
[46]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[47]
TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[48]
TS 23.632: "User data interworking, coexistence and migration; Stage 2".
Up

3  Definitions, symbols and abbreviationsp. 9

3.1  Definitionsp. 9

For the purposes of the present document, the following terms and definitions apply.
IP Multimedia session:
IP Multimedia session and IP Multimedia call are treated as equivalent in this specification.
Transparent data:
Data that is understood syntactically but not semantically by the HSS. It is data that an AS may store in the HSS to support its service logic. One example is data that an AS stores in the HSS, using it as a repository.
Non-transparent data:
Data that is understood both syntactically and semantically by the HSS.
AS (Application Server):
a term used to denote either of a SIP Application Server or an OSA Service Capability Server.
Up

3.2  Abbreviationsp. 9

For the purposes of the present document, the following abbreviations apply:
AS
Application Server
C
Conditional
CSCF
Call Session Control Function
CSG
Closed Subscriber Group
DRMP
Diameter Routing Message Priority
DSCP
Differentiated Services Code Point
GIBA
GPRS-IMS-Bundled-Authentication
HSS
Home Subscriber Server
IE
Information Element
IP
Internet Protocol
IM
IP Multimedia
IMS
IP Multimedia Subsystem
M
Mandatory
O
Optional
SIP
Session Initiation Protocol
SLF
Subscription Locator Function
S-CSCF
Serving CSCF

4  Main Conceptp. 9

This document presents the Sh interface related functional requirements of the communicating entities.
It gives a functional classification of the procedures and describes the procedures and message parameters.
Error handling flows, protocol version identification, etc. procedures are also included.

5  General Architecturep. 10

This clause further specifies the architectural assumptions associated with the Sh reference point, building on TS 23.228, TS 23.218 and also the Ph reference point building upon TS 23.141.

5.1  Functional requirements of network entitiesp. 10

5.1.1  Functional Requirements of the Application Serverp. 10

The Application Server may communicate with the HSS over the Sh interface.
For functionality of the Application Server refer to TS 23.002, TS 23.228 and TS 23.218.

5.1.2  Functional requirements of HSSp. 10

The HSS may communicate with the Application Server over the Sh interface and with the Presence Network Agent over the Ph interface. The functionality of the Ph interface shall be the same as the functionality of the Sh interface.
For functionality of the HSS refer to TS 23.002, TS 23.228 and TS 23.218.

5.1.3  Functional Requirements of the Presence Network Agent |R6|p. 10

The Presence Network Agent may communicate with the HSS over the Ph interface. In this case, all references to an Application Server in this specification apply also to a Presence Network Agent.

5.2  Functional classification of Sh interface proceduresp. 10

Operations on the Sh interface are classified in functional groups:
  1. Data handling procedures
    • The download of data from the HSS to an AS.
    • The update of data in the HSS.
  2. Subscription/notification procedures
    • An AS can subscribe to receive notifications from the HSS of changes in data.
    • The HSS can notify an AS of changes in data for which the AS previously had subscribed.

Up   Top   ToC