N.1 Origination procedures

23.2283GPPIP Multimedia Subsystem (IMS)Release 18Stage 2TS

N.1.1 (FO#1) Fixed xDSL origination, home

This origination procedure applies to users located in their home service area. As in clause 5.6.2, the UE is located in the home network, but is using an xDSL IP‑CAN to access the IM CN Subsystem.

NOTE: The below flows are example flows. The detailed stage 2 description of the RACS information flows can be found in ETSI ES 282 003 [78].

Figure N.1.1: Fixed xDSL originating – home (example flow)

Procedure F0#1 is as follows:

1. UE sends the SIP INVITE request, containing an initial SDP, to the P‑CSCF address determined with P‑CSCF discovery mechanism. The initial SDP may represent one or more media for a multi-media session.

2. A connection is reserved in the C‑BGF with optional NAT binding list retrieval.

3. P‑CSCF remembers (from the registration procedure) the next hop CSCF for this UE. In this case it forwards the INVITE to the S‑CSCF in the home network.

4. S‑CSCF validates the service profile, and invokes any origination service logic required for this user. This includes authorization of the requested SDP based on the user’s subscription for multi-media services.

5. S‑CSCF forwards the request, as specified by the S-S procedures. In addition, subject to operator policy, the S‑CSCF may insert in the request a reference location of the user, when network-provided location information is not already present. The reference location (e.g. line identification) is determined by the operator as part of the user profile and may be received from the HSS at registration.

6. The media stream capabilities of the destination are returned along the signalling path, per the S-S procedures.

7-9. S‑CSCF forwards the Offer Response message to the P‑CSCF which triggers RACS. RACS performs admission control based on the Offer and Answer parameters.
RACS configures the connections in the C‑BGF based on the SDP answer and optionally requests a NAT binding list.

10. UE decides the offered set of media streams for this session, confirms receipt of the Offer Response and sends the Response Confirmation to P‑CSCF. The Response Confirmation may also contain SDP. This may be the same SDP as in the Offer Response received in step 9 or a subset. If new media are defined by this SDP, a new connection configuration shall be performed following step 2. The originating UE is free to continue to offer new media in this request or in subsequent requests using the Update method. Each offer/answer exchange will cause the P‑CSCF to repeat the RACS interactions again.

11. P‑CSCF forwards this message to S‑CSCF

12. S‑CSCF forwards this message to the terminating endpoint, as per the S-S procedure.

13. The terminating end point responds to the originating end with an acknowledgement. If Optional SDP is contained in the Response Confirmation, the Confirmation Acknowledge will also contain an SDP response. If the SDP has changed, the admission control and configure connection flows are repeated.

14-15. S‑CSCF and P‑CSCF forward the answered media towards the UE.

16-18. The destination UE may optionally perform alerting. If so, it signals this to the originating party by a provisional response indicating Ringing. This message is sent to S‑CSCF per the S-S procedure. It is sent from there toward the originating end along the signalling path. UE indicates to the originating user that the destination is ringing.

19-20. When the destination party answers, the terminating endpoint sends a SIP 200-OK final response along the signalling path to the originating endpoint, as specified by the termination procedures and the S-S procedures.

21. P‑CSCF performs the approval of QoS Commit procedure which triggers the Open Gates procedures if required.

22. P‑CSCF passes the 200-OK response back to UE.

23. UE starts the media flow(s) for this session.

24-26. UE responds to the 200 OK with an ACK message which is sent to P‑CSCF and passed along the signalling path to the terminating endpoint.