A.8 Default messages for CS to PS SRVCC
34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification
A.8.1 MESSAGE UE receiving the ATGW information for CS to PS SRVCC
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
UE’s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP |
|||
|
sent-by |
SS P-CSCF address: protected server port of SS |
|||
|
via-branch |
value starting with ‘z9hG4bK’ (NOTE 1) |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
<sip:sti-sr@atcf.visited2.net> (SIP URI of the STI-SR) |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
default public user identity of the UE |
|||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
a random text string generated by the SS |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
Accept-Contact |
RFC 3841 [64] |
|||
|
ac-value |
+g.3gpp.smsip;require;explicit |
|||
|
Content-Disposition |
RFC 3261 [15] |
|||
|
disp-type |
render |
|||
|
P-Asserted-Identity |
RFC 3325 [89] |
|||
|
addr-spec |
<sip:sti-sr@atcf.visited2.net> (SIP URI of the STI-SR) |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/sdp |
|||
|
Content-Length |
RFC 3261 [15] |
|||
|
value |
length of message-body |
NOTE 1: Branch parameter values sent by SS are different within a test case execution.
A.8.2 MESSAGE UE providing information for CS to PS SRVCC
|
Header/param |
Cond |
Value/remark |
Rel |
Reference |
|---|---|---|---|---|
|
Request-Line |
RFC 3261 [15] |
|||
|
Method |
MESSAGE |
RFC 3428 [91] |
||
|
Request-URI |
<sip:sti-sr@atcf.visited2.net> (same value as received in A.8.1) |
|||
|
SIP-Version |
SIP/2.0 |
|||
|
Via |
RFC 3261 [15] |
|||
|
sent-protocol |
SIP/2.0/UDP (when using UDP) or |
|||
|
sent-by |
IP address or FQDN and protected server port of the UE |
|||
|
via-branch |
value starting with ‘z9hG4bK’ |
|||
|
From |
RFC 3261 [15] |
|||
|
addr-spec |
SIP URI of the UE |
|||
|
tag |
any value |
|||
|
To |
RFC 3261 [15] |
|||
|
addr-spec |
<sip:sti-sr@atcf.visited2.net> (SIP URI of the STI-SR) (same value as received in A.8.1) |
|||
|
tag |
not present |
|||
|
Call-ID |
RFC 3261 [15] |
|||
|
callid |
must be present, value not checked |
|||
|
CSeq |
RFC 3261 [15] |
|||
|
value |
any value |
|||
|
method |
MESSAGE |
|||
|
Max-Forwards |
RFC 3261 [15] |
|||
|
value |
non-zero value |
|||
|
P-Access-Network-Info |
A1 |
RFC 7315 [132] |
||
|
access-net-spec |
A3 |
access network information and, if applicable, the cell ID |
||
|
A4 |
access network information for NR, containing access-class parameter with value "3GPP-NR" or access-type parameter with value "3GPP-NR-FDD" or "3GPP-NR-TDD", and also containing the cell ID |
Rel-15 |
||
|
Route |
RFC 3261 [15] |
|||
|
route-param |
<sip: SS P-CSCF address: protected server port of SS;lr>, <sip: scscf.3gpp.org;lr> |
|||
|
Content-Type |
RFC 3261 [15] |
|||
|
media-type |
application/sdp |
|||
|
Content-Length |
header shall be present if UE uses TCP to send this request and if there is a message-body |
RFC 3261 [15] |
||
|
value |
length of message-body |
|
Condition |
Explanation |
|
A1 |
IMS security (A.6a/2 3GPP TS 34.229-2 [5]) |
|
A2 |
GIBA (A.6a/1 3GPP TS 34.229-2 [5]) |
|
A3 |
UE uses E-UTRAN access (A.18/1 3GPP TS 34.229-2 [5]) |
|
A4 |
UE uses NR access (A.18/5 3GPP TS 34.229-2 [5]) |
Annex B (normative):
Default DHCP messages
For all the message definitions below, the acceptable order and syntax of headers and fields within these headers must be according to IETF RFCs where those headers have been defined. Typically the order of headers is not significant, but there are well defined exceptions where the order is important.
For IPv6 DHCP messages refer to RFC 3315[23].
For IPv4 DHCP messages refer to RFC 2131[55].
The contents of the messages described in the present Annex is not complete – only the fields and headers required to be checked or generated by SS are listed here. The messages sent by the UE may contain additional parameters, fields and headers which are not checked and must thus be ignored by SS.