Question: In IMS Service Continuity, when a UE establishes an originating IMS session with CS media, how does the SCC AS handle the session legs?
Option 1: The SCC AS only terminates the Remote Leg from the remote end.
Option 2: The SCC AS establishes both Access and Remote Legs but does not coordinate signaling between them.
Option 3: The SCC AS coordinates media flow directly between the UE and the remote end without anchoring the session.
Option 4: The SCC AS terminates an Access Leg from the user and establishes a Remote Leg toward the remote end, coordinating session control signalling exchange between the two.
Explanation: This is correct because, according to the 3GPP specifications for IMS Service Continuity, when an originating IMS session is established with CS media, the SCC AS (Service Centralization and Continuity Application Server) employs a 3rd party call control (3pcc) function. This involves anchoring the IMS session by terminating the Access Leg from the user and establishing a Remote Leg towards the remote end, while also coordinating the session control signalling exchange between these two legs to ensure seamless communication.