When user does initial
registration in the IMS network, P-CSCF will invoke ATCF/ATGW
functionality and decides to include itself for access transfer
of sessions according to operator policy. The inclusion of ATCF/ATGW
functionality will be decided based on the following factors.
- If UE is roaming, based
on the roaming agreement (home operator also supports SRVCC enhanced
with ATCF in SCC-AS and HSS). ATCF will have a list of configured
home networks which support SRVCC. ATCF functionality will only
be invoked for those home networks. Comparison will be done against
domain name in request URI.
- If ATCF is enabled
in P-CSCF service.
- If UE is SRVCC capable.
The SC UE shall include the g.3gpp.accesstype media feature tag as
described in subclause B.3 of 3GPP TS 24.292 [4] in
the Contact header field of the SIP REGISTER request. ATCF will
decide based on this tag.
- Based on Access-Type.
Access type is E-UTRAN, UTRAN and GERAN access networks for which
ATCF will be included.
Operator will have
the liberty to choose these criteria while configuring ATCF; either
one of them or a set or neither can qualify.
During registration,
ATCF will allocate a routable Session Transfer Number - Single Radio (STN-SR)
pointing to the ATCF. This number is configured in CSCF ATCF/ATGW Configuration
Mode. This STN-SR ensures that MSC Server selects the correct
ATCF during SRVCC procedure. This STN-SR allocated will be forwarded
to IMS Core (S-CSCF) though Feature-Caps header. The ATCF will also
include a management URI and path header information (same as P-CSCF
path) in the Feature-Caps header. The management URI will be used
by SCC-AS to provide SRVCC information to ATCF node.
The IMS-Core (S-CSCF)
will forward the UE registration information to SCC-AS through third
party register request. S-CSCF will include UE Register and 200OK
to register in multi-part body of the third party register request.
After third party registration
is successful, SCC-AS will send MESSAGE request to provide SRVCC
information to ATCF. The SRVCC information will be included in the
message body of MESSAGE request. It will contain the following information:
-
Correlation-MSISDN:
A Correlation MSISDN (C-MSISDN) is an MSISDN that is used for correlation
of sessions at access transfer and to route a call from the IM CN
subsystem to the same user in the CS domain. The C-MSISDN is bound
to the IMS Private User Identity and is uniquely assigned per IMSI
and IMS Private User Identity.
-
ATU-STI (Access Transfer
Update - Session Transfer Identifier): This point to the SCC-AS
and is allocated to the SCC-AS.
-
ATCF-Path: This
is exactly the path header added by ATCF during registration.
Once ATCF/ATGW
receives the above information from SCC-AS, Access-Transfer functionality
for that subscriber will be enabled.
Furthermore, ATCF needs
to validate the identity of SCC-AS. A list of SCC-AS will be configured
in ATCF, and incoming message request from SCC-AS will have SCC-AS
identity in URI in the P-Asserted-Identity header. This identity
will be compared against stored list, and if they don't match MESSAGE
request will be responded to with SIP 403 (Forbidden) response with warning
header “SCC-AS not authorised”.
Now, ATCF needs to
make the decision if it supports CS-PS access transfer. ATCF should look
for g.3gpp.cs2ps-srvcc media feature tag and g.3gpp.path in the
Contact header field of the SIP REGISTER request to decide if SC
UE supports CS-PS access transfer. ATCF should generate SIP 2xx
response for register towards UE, which contains a Feature-Caps
header field with the g.3gpp.atcf feature capability indicator and
with the g.3gpp.cs2ps-srvcc feature capability indicator and dynamic
STI-rSR. In this case, ATCF should send MESSAGE request to UE with
ATGW information. ATCF should send SIP MESSAGE request to UE after
receiving SIP message request from SCC-AS if
- The ATCF indicated
the support of the CS to PS SRVCC when handling the SIP REGISTER
request establishing the registration path;
- The SRVCC-related information
for the registration path contains the ATU-STI for CS to PS SRVCC;
and
- The ATCF does not have
the UE information for CS to PS SRVCC bound to the registration path.
During Registration,
if the ATCF is aware of all MSC servers which can be involved in
the SRVCC procedures and which are in the same network as the ATCF,
and it supports the MSC server assisted mid-call feature, ATCF should
insert the g.3gpp.mid-call feature capability indicator while forwarding
requests.