Scribd Logo
Upload

Welcome to Scribd!

  • SH Interface

    Uploaded by

    prasoon
    55 views5 pages
    The Sh interface is defined by 3GPP as the interface between an Application Server (AS) and Home Subscriber Server (HSS). It supports two groups of operations - data handling procedures like downloading and updating subscriber data between the AS and HSS, and subscription/notification procedures that allow an AS to subscribe to notifications of subscriber data changes from the HSS. The Sh interface is important for exchanging sensitive subscriber data needed by applications, as well as for failover situations where a secondary AS needs to access subscriber data. While SIP messages can be used for registration, the Sh interface provides more fine-grained exchange of subscriber data required by applications and services.

    Original Description:

    good

    Original Title

    Sh Interface

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The Sh interface is defined by 3GPP as the interface between an Application Server (AS) and Home Subscriber Server (HSS). It supports two groups of operations - data handling procedures like downloading and updating subscriber data between the AS and HSS, and subscription/notification procedures that allow an AS to subscribe to notifications of subscriber data changes from the HSS. The Sh interface is important for exchanging sensitive subscriber data needed by applications, as well as for failover situations where a secondary AS needs to access subscriber data. While SIP messages can be used for registration, the Sh interface provides more fine-grained exchange of subscriber data required by applications and services.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    55 views5 pages

    SH Interface

    Uploaded by

    prasoon
    The Sh interface is defined by 3GPP as the interface between an Application Server (AS) and Home Subscriber Server (HSS). It supports two groups of operations - data handling procedures like downloading and updating subscriber data between the AS and HSS, and subscription/notification procedures that allow an AS to subscribe to notifications of subscriber data changes from the HSS. The Sh interface is important for exchanging sensitive subscriber data needed by applications, as well as for failover situations where a secondary AS needs to access subscriber data. While SIP messages can be used for registration, the Sh interface provides more fine-grained exchange of subscriber data required by applications and services.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 5

    Sh Interface What Is It Good for?

    Posted on December 12, 2014 by tttrainer

    There are main principles and there are small technical details. People mostly understand how
    a petrol engine works. But that doesnt mean they are able to fix one or even make it. No, it is
    a long way to understand how things really work. And it is a psychologically proven fact that
    we cant really understand things until we will try to change them. Well, dont try it at home
    with your petrol engine.

    This time we will take a closer look on one of often omitted interfaces. You dont need it in
    order to understand the general idea of IMS but when we go into a detail it can be very
    important.

    The Sh interface is defined by 3GPP in TS 29.329 as an interface between an AS and HSS.

    Sh Interface

    Remember the third party registration? I admit I didt tell you the whole truth. Shame on me.
    It can also look like this:
    Sh interface in the third party registration

    If you dont believe anymore check the 3GPP TS 29.328.


    So what operations are supported on Sh interface? There are two groups of them:

    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.
    In the first group we have:

    User-Data-Request/Answer (AS -> HSS)

    This operation is used to download data for particular subscriber from HSS.
    Profile-Update-Request/Answer (AS->HSS)

    In this operation AS stores/updates its data at HSS for a particular subscriber and/or
    application.

    In the second group we have:


    Subscribe-Notifications-Request/Answer(AS->HSS)

    AS takes a subscription that when ever there is change in particular data field for a given
    subscriber.

    Push-Notification-Request/Answer (HSS->AS)

    HSS updates the AS for change in some particular subscriber profile if the AS has an active
    subscription.

    Why we need this when there is a SIP REGISTER/SUBSCRIBE/NOTIFY? The thing is the
    SIP messages in the 3rd party registration are intended for the Event: Reg. Meaning that the
    AS will not receive all information subscriber or non subscriber data it needs for the
    application of service (e.g. There is no information in the SIP REGISTER or NOTIFY telling
    the RCS whether a particular user has some active news feeds or a permission to moderate
    video chats.) Sh operations are more sensitive and suitable for this purpose.
    It can also happen that some request (e.g. coming from Authentication Proxy) will not arrive
    on the right AS (AP can select a secondary AS for a particular subscriber). In that case the
    AS will download the subscriber data from the HSS via the Sh interface. Another reason can
    be geo-redundancy. We can have ASs which are handling only the users connected from
    some geographical area. But in case of a failure they can act as a backup ASs too. That means
    that the registration will be done by the primary server. After the failure the backup AS needs
    to access the subscribers data in order to apply services correctly.
    Sh for failover

    Most probably there will be also two I/S-CSCF. But the flow is complex already enough:
    Sh failover

    For the VoLTE the ETSI TS 29.364 defines the XML format for service data descriptions for
    AS interoperability.
    Clear? The final question is what is the LDAP for? Well, LDAP interface can be used
    instead of the Sh for the data handling procedures. Depends on the preferences and on what
    vendors support. LDAP is usually being used along with SOAP protocol because not all the
    needed operations are supported by the LDAP.

    You might also like