hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.4 Responses to an initial request for a dialog | When the P-CSCF receives any 1xx or 2xx response to the above request, the P-CSCF shall:
1) store the values received in the P-Charging-Function-Addresses header field;
2) store the list of Record-Route header fields from the received response;
3) store the dialog ID and associate it with the private user identity and ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.5 Target refresh request for a dialog | When the P-CSCF receives from the UE a target refresh request for a dialog, the P-CSCF shall:
1) verify if the request relates to a dialog in which the originator of the request is involved:
a) if the request does not relates to an existing dialog in which the originator is involved, then the P-CSCF shall answer the re... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.6 Responses to a target refresh request for a dialog | When the P-CSCF receives a 1xx or 2xx response to the above request, the P-CSCF shall:
1) if a security association or TLS session exists, rewrite the address and port number of its own Record Route entry to the same value as for the response to the initial request for the dialog; and
2) replace the saved Contact heade... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.7 Request for a standalone transaction | When the P-CSCF receives from the UE the request for a standalone transaction, and a service route value list exists for the served user of the request, the P-CSCF shall:
1) remove its own SIP URI from the top of the list of Route header fields;
2) if the UE is performing the functions of an external attached network u... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.8 Responses to a request for a standalone transaction | When the P-CSCF receives any response to the above request, the P-CSCF shall:
1) store the values received in the P-Charging-Function-Addresses header field;
before forwarding the response to the UE in accordance with the procedures of RFC 3261 [26].
NOTE: The P-CSCF can find the IMS communication service supported for... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.9 Subsequent request other than a target refresh request | When the P-CSCF receives from the UE a subsequent request other than a target refresh request (including requests relating to an existing dialog where the method is unknown), the P-CSCF shall:
1) verify if the request relates to a dialog in which the originator of the request is involved:
a) if the request does not rel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.10 Responses to a subsequent request other than a target refresh request | Void |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.11 Request for an unknown method that does not relate to an existing dialog | When the P-CSCF receives from the UE the request for an unknown method (that does not relate to an existing dialog), and a service route value list exists for the served user of the request, the P-CSCF shall:
1) if the UE performing the functions of an external attached network using static mode of operation:
i) select... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.12 Responses to a request for an unknown method that does not relate to an existing dialog | NOTE: The P-CSCF can find the IMS communication service supported for the transaction, as determined by the originating home network, in the topmost occurance of the "+g.3gpp.icsi-ref" header field parameter of the Feature-Caps header field(s) of 18x or 2xx response. The information can be used for charging purpose. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4 Requests terminated by the UE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.1 General for all requests | The P-CSCF shall log all SIP requests destined for the UE that contain a "logme" Session-ID header field parameter based on local policy.
If the serving network supports PCRF based P-CSCF restoration and the Restoration-Info header field is included in the incoming request, and the P-CSCF has no binding for the identit... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.2 General for all responses | When the P-CSCF receives, destined for the UE, a response sent on a dialog for which logging of signalling is in progress, the P-CSCF shall check whether a trigger for stopping logging of SIP signalling has occurred, as described in RFC 8497 [140] and configured in the trace management object defined in 3GPP TS 24.323 ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.3 Initial request for a dialog | When the P-CSCF receives, destined for the UE, an initial request for a dialog, prior to forwarding the request, the P-CSCF shall:
1) if an indication has been received from the PCRF that the signalling bearer to the UE is lost, and has not recovered, reject the request by sending 500 (Server Internal Error) response;
... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.4 Responses to an initial request for a dialog | When the P-CSCF receives any 1xx or 2xx response to the above request, the P-CSCF shall:
0A) if the response is originated from a UE which the P-CSCF considers as privileged sender, remove any P-Preferred-Identity header field, and skip step 1) below;
NOTE: The P-CSCF determines if the UE is considered privileged sende... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.5 Target refresh request for a dialog | When the P-CSCF receives, destined for the UE, a target refresh request for a dialog, prior to forwarding the request, the P-CSCF shall:
1) if a security association or TLS session exists, add its own address to the top of the received list of Via header fields and save the list. The P-CSCF Via header field entry is bu... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.6 Responses to a target refresh request for a dialog | When the P-CSCF receives a 1xx or 2xx response to the above request, the P-CSCF shall:
1) verify that the list of Via header fields matches the saved list of Via header fields received in the request corresponding to the same dialog, including the P-CSCF Via header field value. This verification is done on a per Via he... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.7 Request for a standalone transaction | When the P-CSCF receives, destined for the UE, a request for a standalone transaction, or a request for an unknown method (that does not relate to an existing dialog), prior to forwarding the request, the P-CSCF shall:
1) if an indication has been received from the PCRF that the signalling bearer to the UE is lost, and... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.8 Responses to a request for a standalone transaction | When the P-CSCF receives any response to the above request, the P-CSCF shall:
1) verify that the list of Via header fields matches the saved list of Via header fields received in the request corresponding to the same dialog, including the P-CSCF Via header field value. This verification is done on a per Via header fiel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.9 Subsequent request other than a target refresh request | When the P-CSCF receives, destined for the UE, a subsequent request for a dialog that is not a target refresh request (including requests relating to an existing dialog where the method is unknown), prior to forwarding the request, the P-CSCF shall:
1) if a security association or TLS session exists, add its own addres... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.10 Responses to a subsequent request other than a target refresh request | When the P-CSCF receives any response to the above request, the P-CSCF shall:
1) verify that the list of Via header fields matches the saved list of Via header fields received in the request corresponding to the same dialog, including the P-CSCF Via header field value. This verification is done on a per Via header fiel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.11 Request for an unknown method that does not relate to an existing dialog | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.4.12 Responses to a request for an unknown method that does not relate to an existing dialog | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.7 Initial INVITE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.7.1 Introduction | In addition to following the procedures for initial requests defined in subclause 5.2.6, initial INVITE requests also follow the procedures of this subclause. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.7.2 UE-originating case | When the P-CSCF receives from the UE an INVITE request for which resource authorization procedure is required, if it receives from the IP-CAN (e.g. via PCRF) an indication that the requested resources for the multimedia session being established cannot be granted and this indication does not provide an acceptable bandw... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.7.3 UE-terminating case | When the P-CSCF receives an INVITE request destined for the UE the P-CSCF may require the periodic refreshment of the session to avoid hung states in the P-CSCF. If the P-CSCF requires the session to be refreshed, then the P-CSCF shall apply the procedures described in RFC 4028 [58] clause 8.
NOTE 1: Requesting the ses... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.7.4 Access network charging information | The P-CSCF shall include the "access-network-charging-info" header field parameter within the P-Charging-Vector header field as described in subclause 7.2A.5. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8 Call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.1 P-CSCF-initiated call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.1.1 Cancellation of a session currently being established | Upon receipt of an indication that the signalling bearer is no longer available (e.g. an Rx interface message from PCRF), the P-CSCF shall cancel that dialog by applying the following steps:
1) if the P-CSCF serves the calling user of the session, send out a CANCEL request to cancel the INVITE request towards the termi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.1.2 Release of an existing session | Upon:
1) receipt of an indication that the radio/bearer resources are no longer available for a media negotiated in a session (e.g. an Rx interface message from PCRF) and if no SIP message removing the media for which resources are no longer available is received within an operator defined time after the reception of t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.1.3 Abnormal cases | Upon receipt of a request on a dialog for which the P-CSCF initiated session release, the P-CSCF shall terminate this received request and answer it with a 481 (Call/Transaction Does Not Exist) response. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.1.4 Release of the existing dialogs due to registration expiration and deletion of the security association, IP association or TLS session | If there are still active dialogs associated with the user after the security associations, IP association or TLS sessions were deleted, the P-CSCF shall discard all information pertaining to these dialogs without performing any further SIP transactions with the peer entities of the P-CSCF.
NOTE: If the interface betwe... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.2 Call release initiated by any other entity | When the P-CSCF receives a 2xx response for a BYE request matching an existing dialog, then the P-CSCF shall delete all the stored information related to the dialog. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.8.3 Session expiration | If the P-CSCF requested the session to be refreshed periodically, and the P-CSCF got the indication that the session will be refreshed, when the session timer expires, the P-CSCF shall delete all the stored information related to the dialog.
NOTE: If the interface between the P-CSCF and the IP-CAN is supported, the P-C... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.9 Subsequent requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.9.1 UE-originating case | The P-CSCF shall respond to all reINVITE requests with a 100 (Trying) provisional response.
For a reINVITE request or UPDATE request from the UE within the same dialog, the P-CSCF shall include the updated access-network-charging-info parameter from P-Charging-Vector header field when sending the SIP request to the S-C... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.9.2 UE-terminating case | The P-CSCF shall respond to all reINVITE requests with a 100 (Trying) provisional response.
For a reINVITE request or UPDATE request destined towards the UE within the same dialog, when the P-CSCF sends 200 (OK) response (to the INVITE request or UPDATE request) towards the S-CSCF, the P-CSCF shall include the updated ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.10 Emergency service | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.10.1 General | If the P-CSCF belongs to a network where the registration is not required to obtain emergency service, the P‑CSCF shall accept any unprotected request on the IP address and port advertised to the UE during the P-CSCF discovery procedure. The P-CSCF shall also accept any unprotected request on the same IP address and th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.10.2 General treatment for all dialogs and standalone transactions excluding the REGISTER method – requests from an unregistered user | If the P-CSCF receives an initial request for a dialog or standalone transaction, or an unknown method from an unregistered user on the IP address and the unprotected port advertised to the UE during the P-CSCF discovery or the SIP default port, the P-CSCF shall inspect the Request-URI independent of values of possible... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.10.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method after emergency registration | If the P-CSCF receives an initial request for a dialog, or a standalone transaction, or an unknown method, for a registered user over the security association, TLS session, or IP association that was created during the emergency registration, as identified by the presence of the "sos" SIP URI parameter in the Contact h... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.10.4 General treatment for all dialogs and standalone transactions excluding the REGISTER method - non-emergency registration | If the P-CSCF receives an initial request for a dialog, or a standalone transaction, or an unknown method, for a registered user, and the request is:
a) understood from saved or included information to relate to private network traffic (see subclause 5.2.6.3), and operator policy requires the P-CSCF to detect an emerge... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.10.5 Abnormal and rejection cases | If the IM CN subsystem to where the P-CSCF belongs to is not capable to handle emergency sessions or due to local policy does not handle emergency sessions or only handles certain type of emergency session request or does not support emergency sessions for either the geographical location of the UE is located or the IP... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.11 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.12 Resource sharing | The P-CSCF supporting resource sharing shall perform the actions defined in access technology specific annexes. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.13 Priority sharing | The P-CSCF supporting priority sharing shall perform the actions defined in access technology specific annexes. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.14 Access update | This subclause specifies procedures for the P-CSCF to inform the S-CSCF and any AS as applicable that the UE has changed access and possibly PLMN. This includes access update when the UE is not in a call and an in-call access update procedure when the access change happens when the UE is involved in an IMS session.
If ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3 Procedures at the I-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.0 General | When sending a failure response to any received request, depending on operator policy, the I-CSCF may insert a Response-Source header field with an "fe" header field parameter constructed with the URN namespace "urn:3gpp:fe", the fe-id part of the URN set to "i-cscf" and optionally an appropriate fe-param part of the U... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.1 Registration procedure | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.1.1 General | During the registration procedure the I-CSCF shall behave as a stateful proxy. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.1.2 Normal procedures | When the I-CSCF receives a REGISTER request, the I-CSCF shall verify whether or not it has arrived from a trusted domain. If the request has not arrived from a trusted domain, the I-CSCF shall complete the processing of the request by responding with 403 (Forbidden) response. Otherwise, the I-CSCF starts the user regis... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.1.3 Abnormal cases | In the case of SLF query, if the SLF does not send HSS address to the I-CSCF, the I-CSCF shall send back a 403 (Forbidden) response to the UE.
If the HSS sends a negative response to the user registration status query request, the I-CSCF shall send back a 403 (Forbidden) response.
If the user registration status query ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.2 Initial requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.2.1 Normal procedures | The I-CSCF may behave as a stateful proxy for initial requests.
Upon receipt of a request, the I-CSCF shall perform the originating procedures as described in subclause 5.3.2.1A if the topmost Route header field of the request contains the "orig" parameter. Otherwise, the I-CSCF shall continue with the rest of the proc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.2.2 Abnormal cases | In the case of SLF query, if the SLF does not send HSS address to the I-CSCF, the I-CSCF shall send back a 404 (Not Found) response to the UE.
Upon successful user location query, when the response contains the URI of the assigned S-CSCF, if the I‑CSCF is unable to contact the assigned S-CSCF, as determined by one of t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.3 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.3.1 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.3.2 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.3.3 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.4 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.3.5 Subsequent requests | When the I-CSCF receives a subsequent request, the I-CSCF shall verify whether it has arrived from an entity within the trust domain or not. If the request has not arrived from an entity within the trust domain, then the I-CSCF shall remove all P-Charging-Vector header fields, if present.
If no P-Charging-Vector header... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4 Procedures at the S-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.0 General | Where the S-CSCF provides emergency call support, the procedures of subclause 5.4.8 shall be applied first.
Upon
1) a third-party registration due to initial registration on behalf of a served public user identity; or
2) a trigger to an AS for an unregistered public user identity and there is no IP address of that AS a... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1 Registration and authentication | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.1 Introduction | The S-CSCF shall determine which authentication mechanism applies based on the contents of the REGISTER request and the authentication mechanism assigned in the HSS:
1) if the REGISTER request contains an Authorization header field with the "integrity-protected" header field parameter set to "no", the S-CSCF shall perf... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.2 Initial registration and user-initiated reregistration | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.2.1 Unprotected REGISTER | Any REGISTER request received unprotected by the S-CSCF without an Authorization header field, or with an Authorization header field having the "integrity-protected" header field parameter in the Authorization header field set to "no", or without an "integrity-protected" header field parameter is considered to be an in... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.2.2 Protected REGISTER with IMS AKA as a security mechanism | Upon receipt of a REGISTER request with the "integrity-protected" header field parameter in the Authorization header field set to "yes" or to "tls-connected", the S-CSCF shall identify the user by the public user identity as received in the To header field and the private user identity as received in the Authorization ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.2.3 Abnormal cases - general | In the case that the expiration timer from the UE is too short to be accepted by the S-CSCF, the S-CSCF shall:
- reject the REGISTER request with a 423 (Interval Too Brief) response, containing a Min-Expires header field with the minimum registration time the S-CSCF will accept.
On receiving a failure response to one o... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.3 Authentication and re-authentication | Authentication and re-authentication is performed by the registration procedures as described in subclause 5.4.1.2. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.4 User-initiated deregistration | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.4.1 Normal cases | When S-CSCF receives a REGISTER request with the registration expiration interval value containing the value zero, the S-CSCF shall:
1) verify that the REGISTER request is associated with an existing registered contact or an existing flow or, if the S-CSCF restoration procedures are supported by this S-CSCF, attempt to... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.4.2 Abnormal cases - IMS AKA as security mechanism | If case that the S-CSCF receives a REGISTER request with the "integrity-protected" header field parameter in the Authorization header set to "yes" or to "tls-connected", for which the public user identity received in the To header and the private user identity received in the Authorization header of the REGISTER reques... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.4.4 Abnormal cases – SIP digest with TLS as security mechanism | The procedures for subclause 5.4.1.4.2 apply. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.4.5 Abnormal cases – NASS-IMS bundled authentication as security mechanism | There are no abnormal cases for NASS-IMS bundled authentication. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.4.6 Abnormal cases – GPRS-IMS-Bundled authentication as security mechanism | There are no abnormal cases for GPRS-IMS-Bundled authentication. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.5 Network-initiated deregistration | NOTE 1: A network-initiated deregistration event that occurs at the S-CSCF can be received from the HSS or can be an internal event in the S-CSCF.
For any registered public user identity, the S-CSCF can deregister:
- all contact addresses bound to the indicated public user identity (i.e. deregister the respective publi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.6 Network-initiated re-authentication | The S-CSCF may request a subscriber to re-authenticate at any time, based on a number of possible operator settable triggers.
NOTE 1: Triggers for re-authentication include e.g. a current registration of the UE is set to expire at a predetermined time; one or more error conditions in the S-CSCF; the S-CSCF mistrusts th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.7 Notification of Application Servers about registration status | During registration, the S-CSCF shall include the P-Access-Network-Info header fields (as received in the REGISTER request from the UE and the P-CSCF) and a P-Visited-Network-ID header field (as received in the REGISTER request from the UE) in the third-party REGISTER request sent towards the ASs, if the AS is part of ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.1.8 Service profile updates | NOTE 1: The S-CSCF can receive an update of subscriber data notification on the Cx interface, from the HSS, which can affect the stored information about served public user identities. According to 3GPP TS 29.228 [14], the changes are guaranteed not to affect the default public user identity within the registration imp... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2 Subscription and notification | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2.1 Subscriptions to S-CSCF events | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2.1.1 Subscription to the event providing registration state | When an incoming SUBSCRIBE request addressed to S-CSCF arrives containing the Event header field with the reg event package, the S-CSCF shall:
0) if the Request-URI of the SUBSCRIBE request contains a URI for which currently no binding exists, then send a 480 (Temporarily Unavailable) response indicating that the subsc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2.1.2 Notification about registration state | The UE can bind any one of its public user identities either to its contact address or to a registration flow and the associated contact address (if the multiple registration mechanism is used) via a single registration procedure. When multiple registrations mechanism is used to register a public user identity and bind... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2.1.3 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2.1.4 Void | 5.4.2.1A Outgoing subscriptions to load-control event
Based on operator policy, the S-CSCF may subscribe to the load-control event package with one or more target SIP entities. The list of target SIP entities is provisioned.
Subscription to the load-control event package is triggered by internal events (e.g. the physic... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.2.2 Other subscriptions | Upon receipt of a NOTIFY request with the Subscription-State header field set to "terminated" and the S-CSCF has retained the SIP dialog state information for the associated subscription, once the NOTIFY transaction is terminated, the S-CSCF can remove all the stored information related to the associated subscription. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3 General treatment for all dialogs and standalone transactions excluding requests terminated by the S-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.1 Determination of UE-originated or UE-terminated case | Upon receipt of an initial request or a stand-alone transaction, the S-CSCF shall:
- perform the procedures for the UE-originating case as described in subclause 5.4.3.2 if the request makes use of the information for UE-originating calls, which was added to the Service-Route header field entry of the S-CSCF during reg... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.2 Requests initiated by the served user | For all SIP transactions identified:
- if priority is supported, as containing an authorised Resource-Priority header field or a temporarily authorised Resource-Priority header field, or, if such an option is supported, relating to a dialog which previously contained an authorised Resource-Priority header field;
the S-... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.3 Requests terminated at the served user | For all SIP transactions identified:
- if priority is supported, as containing an authorised Resource-Priority header field or a temporarily authorised Resource-Priority header field, or, if such an option is supported, relating to a dialog which previously contained an authorised Resource-Priority header field;
the S-... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.4 Original dialog identifier | The original dialog identifier is an implementation specific token that the S-CSCF encodes into the own S-CSCF URI in a Route header field, prior to forwarding the request to an AS. This is possible because the S-CSCF is the only entity that creates and consumes the value.
The token may identify the original dialog of ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.5 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.6 SIP digest authentication procedures for all SIP request methods initiated by the UE excluding REGISTER | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.6.1 General | When the S-CSCF receives from the UE a request (excluding REGISTER), and SIP digest without TLS or SIP digest with TLS is supported and in use for this UE, the S-CSCF may perform the following steps if authentication of SIP request methods initiated by the UE excluding REGISTER is desired:
1) The S-CSCF shall identify ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.3.6.2 Abnormal cases | In the case that SIP digest is used and the request from the UE contains an invalid "nonce" Authorization header field parameter with a valid challenge response for that nonce (indicating that the client knows the correct username/password), or when the "nonce-count" Authorization header field parameter value sent by t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.4 Call initiation | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.4.1 Initial INVITE | When the S-CSCF receives an INVITE request, either from the served user or destined to the served user, the S-CSCF may require the periodic refreshment of the session to avoid hung states in the S-CSCF. If the S-CSCF requires the session to be refreshed, the S-CSCF shall apply the procedures described in RFC 4028 [58] ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.