ISO IEC 17876 pdf download – Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Private User Mobility (PUM) — Registration supplementary service

ISO IEC 17876 pdf download – Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Private User Mobility (PUM) — Registration supplementary service
6Signalling protocol for the support of sS-PUMR6.1sS-PUMR description
SS-PUMR is a supplementary service which enables a PUM user to register at, or de-register from, any wired or wirelessterminal within the PISN. The ability to register for incoming calls (IlnCall registration) is mandatory, whereas the ability toregister for outgoing calls (OuCall registration) or for both incoming and outgoing calls (AllCall registration) is optional. Theability to register at different locations in the PISN at different times enables the PUM user to maintain the provided services(including the ability to make and receive calls) at different access points. De-registration is used to inform the PISN that thePUM user is temporarily unable to make use of the provided services (including the receipt of calls).SS-PUMR may providethe PUM user with the ability to obtain information on the current registration sessions (interrogation).
6.2ss-PUMR operational requirements
6.2.1 Requirements on the Visitor PINX
Generic procedures for the call independent control (connection oriented) of supplementary services，as specified inISO/IEC i1582 for an Originating and Terminating PINX, shall apply.
6.2.2Requirements on the Home PINX
Generic procedures for the call independent control (connection oriented) of supplementary services，as specified inISO/IEC 11582 for a Terminating and an Originating PINX, shall apply.
6.2.3Requirements on the Previous Visitor PINX
Generic procedures for the call independent control (connection oriented) of supplementary services， as specified inISO/IEC 11582 for a Terminating PINX, shall apply.
6.2.4 Requirements on a Transit PINX
Generic procedures for the call independent control (connection oriented) of supplementary services， as specified inISO/EC 11582 for a Transit PINX, shall apply.
6.2.5 Requirements on the Directory PINX
Generic procedures for the call independent control (connection oriented) of supplementary services，as specified inISO/IEC 11582 for a Terminating PINX, shall apply.
6.2.6 Requirements on the Remote PINX
Generic procedures for the call independent control (connection oriented) of supplementary services，as specified inISO/IEC 11582 for an Originating PINX, shall apply.
6.3 SS-PUMR coding requirements
6.3.1 Operations
The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply. The notation is in accordance with ITU-T Rec. X.680 and X.690. The ITU-T Rec. X.208 and X.209 superseded version is in annex E.
6.3.2 Information elements
6.3.2.1 Facility information element
The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ISO/IEC 11582.
When conveying the invoke APDU of operations defined in 6.3.1, the destinationEntity data element of the NFE shall contain value endPINX.
When conveying the invoke APDU of operations defined in 6.3.1, the Interpretation APDU shall either be omitted or be included with value rejectAnyUnrecognisedInvokePdu.
6.3.2.2 Other information elements
Any other information elements (e.g. Calling party number, Called party number) shall be coded in accordance with the rules of ISO/IEC 11582.
6.3.3 Messages
The Facility information element shall be conveyed in the messages as specified in clause 10 of ISO/IEC 11582.
6.4 SS-PUMR state definitions
6.4.1 States at the Visitor PINX
The procedures for the Visitor PINX are written in terms of the following conceptual states existing within the SS-PUMR Supplementary Service Control entity in that PINX in association with a particular registration request.
6.4.1.1 State VisitIdle
SS-PUMR is not operating.
6.4.1.2 State VisitReg
A pumRegistr invoke APDU has been sent.
6.4.1.3 State VisitEnquiry
A pisnEnquiry invoke APDU has been sent.
6.4.1.4 State VisitInterrogation
A pumInterrog invoke APDU has been sent.
6.4.1.5 State VisitDe-reg
A pumDe-reg invoke APDU has been sent.
On receipt of a valid registration request from a PUM user and if the Visitor PINX possesses sufficient addressing information to make a registration request to the Home PINX, the Visitor PINX shall send a pumRegistr invoke APDU to the Home PINX using the call reference of a call independent signalling connection. The call independent signalling connection shall be established (or used, if an appropriate connection is already available) in accordance with the procedures specified in 7.3 of ISO/IEC 11582. Within the argument of the invoke APDU, the PISN number or an alternative identifier of the PUM user shall be included in element pumUserId, the basic service for which the PUM user is to be registered shall be included in element basicService, and the PISN number of the hosting user shall be included in element hostingAddr. This PISN number shall be suitable for use in the Called party number information element of a call or call independent signalling connection that is to be routed to the hosting user. If provided by the registration request from the PUM user, the Visitor PINX shall additionally include in element serviceOption the type of registration (InCall, OutCall or AllCall).