hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.18 Dynamic Service Interaction | Dynamic Service Interaction allows that different ASs involved in the same IMS session (within an operator network or across networks) exchange information about executed services to avoid conflicting interactions between these services. Dynamic Service Interaction information is included in a SIP header field Service-... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.19 Restricted Local Operator Services | The UE and the network can support Restricted Local Operator Services (RLOS).
RLOS services are operator defined services that are offered to UEs when using an EPS IP-CAN as specified in annex L in the following scenarios:
- UE is successfully registered using IMS AKA or GPRS-IMS bundled authentication; or
- UE has att... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5 Application usage of SIP | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1 Procedures at the UE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.0 General | The UE procedures for UE detectable emergency calls are defined in subclause 5.1.6. Exceptions to UE procedures for SIP that do not relate to emergency, are documented in subclause 5.1.6 and shall apply. These exceptions include handling of a response to a request not detected by the UE as relating to an emergency.
Whe... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1 Registration and authentication | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.1 General | The UE shall register public user identities (see table A.4/1 and dependencies on that major capability).
NOTE 1: The UE can use multiple Contact header field values simultaneously containing the same IP address and port number in the contact address.
In case a UE registers several public user identities at different p... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2 Initial registration | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2.1 General | The initial registration procedure consists of the UE sending an unprotected REGISTER request and, if challenged depending on the security mechanism supported for this UE, sending the integrity-protected REGISTER request or other appropriate response to the challenge. The UE can register a public user identity with any... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2.2 Initial registration using IMS AKA | On sending a REGISTER request, as defined in subclause 5.1.1.2.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field, with:
- the "username" header field parameter, set to the value of the private user identity;
- the "realm" header field parameter, set to the domain name ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2.3 Initial registration using SIP digest without TLS | On sending a REGISTER request, as defined in subclause 5.1.1.2.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field as defined in RFC 7616 [286] and RFC 8760 [287] unless otherwise specified in the access specific annexes, with:
- the "username" header field parameter, se... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2.4 Initial registration using SIP digest with TLS | On sending a REGISTER request, as defined in subclause 5.1.1.2.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field set in accordance with subclause 5.1.1.2.3 unless otherwise specified in the access specific annexes; and
b) a Security-Client header field set to specify t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2.5 Initial registration using NASS-IMS bundled authentication | On sending a REGISTER request, as defined in subclause 5.1.1.2.1, the UE shall additionally populate the header fields as follows:
a) optionally, an Authorization header field, with the "username" header field parameter, set to the value of the private user identity;
NOTE 1: In case the Authorization header field is ab... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.2.6 Initial registration using GPRS-IMS-Bundled authentication | On sending a REGISTER request, as defined in subclause 5.1.1.2.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field as defined in RFC 7616 [286] and RFC 8760 [287] shall not be included, in order to indicate support for GPRS-IMS-Bundled authentication.
b) the Security-Cli... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.3 Subscription to the registration-state event package | Upon receipt of a 2xx response to the initial registration, the UE shall subscribe to the reg event package for the public user identity registered at the user's registrar (S-CSCF) as described in RFC 3680 [43] and RFC 6665 [28].
NOTE 1: If the UE supports RFC 6140 [191] and performs the functions of an external attach... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4 User-initiated reregistration and registration of an additional public user identity | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4.1 General | The UE can perform the reregistration of a previously registered public user identity bound to any one of its contact addresses and the associated set of security associations or TLS sessions at any time after the initial registration has been completed.
The UE can perform the reregistration of a previously registered ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4.2 IMS AKA as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.4.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field, with:
- the "username" header field parameter set to the value of the private user identity;
- the "realm" header field parameter directive, set to the val... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4.3 SIP digest without TLS as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.4.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field as defined in RFC 7616 [286] and RFC 8760 [287], including:
- the "username" header field parameter, set to the value of the private user identity;
- the "r... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4.4 SIP digest with TLS as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.4.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field set in accordance with subclause 5.1.1.4.3;
b) the Security-Client header field set to specify the signalling plane security mechanism the UE supports. The ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4.5 NASS-IMS bundled authentication as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.4.1, the UE shall additionally populate the header fields as follows:
a) optionally, an Authorization header field, with the "username" header field parameter, set to the value of the private user identity;
NOTE 1: In case the Authorization header field is ab... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.4.6 GPRS-IMS-Bundled authentication as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.4.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field as defined in RFC 7616 [286] and RFC 8760 [287] shall not be included, in order to indicate support GPRS-IMS-Bundled authentication.
b) security agreement h... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5 Authentication | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.1 IMS AKA - general | Authentication is performed during initial registration. A UE can be re-authenticated during subsequent reregistrations, deregistrations or registrations of additional public user identities. When the network requires authentication or re-authentication of the UE, the UE will receive a 401 (Unauthorized) response to th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.2 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.3 IMS AKA abnormal cases | If, in a 401 (Unauthorized) response, either the MAC or SQN is incorrect the UE shall respond with a further REGISTER indicating to the S-CSCF that the challenge has been deemed invalid as follows:
- in the case where the UE deems the MAC parameter to be invalid the subsequent REGISTER request shall contain no "auts" A... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.4 SIP digest without TLS – general | On receiving a 401 (Unauthorized) response to the REGISTER request containing one or more WWW-Authenticate header fields the UE shall select the topmost header field that it supports (i.e. where the "algorithm" WWW-Authenticate header field parameter is "SHA-256", "SHA-512-256" or "MD5"), and the UE shall:
NOTE 1: The ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.5 SIP digest without TLS – abnormal procedures | On receiving a 403 (Forbidden) response, the UE shall consider the registration to have failed. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.6 SIP digest with TLS – general | On receiving a 401 (Unauthorized) response to the REGISTER request, the procedures in subclause 5.1.1.5.4 apply with the following differences:
- The UE shall check the existence of the Security-Server header field as described in RFC 3329 [48]. If the Security-Server header field is not present or the list of supporte... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.7 SIP digest with TLS – abnormal procedures | On receiving a 403 (Forbidden) response, the UE shall consider the registration to have failed. If performing SIP digest with TLS, the UE should send an initial REGISTER according to the procedure specified in subclause 5.1.1.2 if the UE considers the TLS session to be no longer active at the P-CSCF. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.8 NASS-IMS bundled authentication – general | NASS-IMS bundled authentication is only applicable to UEs that contain neither USIM nor ISIM. Authentication is achieved via the registration and reregistration procedures as defined in subclause 5.1.1.2 and subclause 5.1.1.4. NASS-bundled authentication is granted by the network upon receipt by the UE of a 200 (OK) re... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.9 NASS-IMS bundled authentication – abnormal procedures | There is no separate authentication procedure, and therefore no abnormal procedures. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.10 GPRS-IMS-Bundled authentication – general | Authentication is achieved via the registration and reregistration procedures as defined in subclause 5.1.1.2 and subclause 5.1.1.4. GPRS-IMS-Bundled authentication is granted by the network upon receipt by the UE of a 200 (OK) response to the initial REGISTER request. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.11 GPRS-IMS-Bundled authentication – abnormal procedures | There is no separate authentication procedure and therefore no abnormal procedures. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.5.12 Abnormal procedures for all security mechanisms | A UE shall only respond to two consecutive invalid challenges. The UE may attempt to register with the network again after an implementation specific time.
5.1.1.5A Network-initiated re-authentication
At any time, the UE can receive a NOTIFY request carrying information related to the reg event package (as described in... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6 User-initiated deregistration | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6.1 General | For any public user identity that the UE has previously registered, the UE can deregister via a single registration procedure:
- all contact addresses bound to the indicated public user identity;
- some contact addresses bound to the indicated public user identity;
- a particular contact address bound to the indicated ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6.2 IMS AKA as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.6.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field, with:
- the "username" header field parameter, set to the value of the private user identity;
- the "realm" header field parameter, set to the value as rec... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6.3 SIP digest without TLS as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.6.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field as defined in RFC 7616 [286] and RFC 8760 [287], including:
- the "username" header field parameter, set to the value of the private user identity;
- the "r... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6.4 SIP digest with TLS as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.6.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field set in accordance with subclause 5.1.1.6.3; and
b) a Security-Client header field, set to specify the signalling plane security mechanism it supports. For f... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6.5 NASS-IMS bundled authentication as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.6.1, the UE shall additionally populate the header fields as follows:
a) optionally, an Authorization header field, with the "username" header field parameter, set to the value of the private user identity;
NOTE 1: In case the Authorization header field is ab... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.6.6 GPRS-IMS-Bundled authentication as a security mechanism | On sending a REGISTER request, as defined in subclause 5.1.1.6.1, the UE shall additionally populate the header fields as follows:
a) an Authorization header field as defined in RFC 7616 [286] and RFC 8760 [287] shall not be included, in order to indicate support GPRS-IMS-Bundled authentication.
b) the Security-Verify ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.1.7 Network-initiated deregistration | Upon receipt of a NOTIFY request, on any dialog which was generated during the subscription to the reg event package as described in subclause 5.1.1.3, including one or more <registration> element(s) which were registered by this UE, with:
1) the state attribute within the <registration> element set to "terminated", an... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.2 Subscription and notification | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.2.1 Notification about multiple registered public user identities | Upon receipt of a NOTIFY request for the dialog associated with the subscription to the reg event package the UE shall perform the following actions:
- store the information for the established dialog;
- store the expiration time as indicated in the "expires" header field parameter of the Subscription-State header fiel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.2.2 General SUBSCRIBE requirements | If the UE receives a 503 (Service Unavailable) response to an initial SUBSCRIBE request containing a Retry-After header field, then the UE shall not automatically reattempt the request until after the period indicated by the Retry-After header field contents.
5.1.2A Generic procedures applicable to all methods excludin... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.3 Call initiation - UE-originating case | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.3.1 Initial INVITE request | Where multiple domains exist for initiating a call/session, before sending an initial INVITE request, the UE shall perform access domain selection in accordance with the appropriate specification for the IP-CAN in use, taking into account the media to be requested. Access domain selection allows the policy of the netwo... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.4 Call initiation - UE-terminating case | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.4.1 Initial INVITE request | The preconditions mechanism should be supported by the terminating UE.
The handling of incoming initial INVITE requests at the terminating UE is mainly dependent on the following conditions:
- the specific service requirements for "integration of resource management and SIP" extension (hereafter in this subclause known... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.4.2 Reliable 18x Policy | The reliable 18x policy consists of one or more reliable 18x policy parts.
The reliable 18x policy part consists of a mandatory send 18x reliably configuration and an optional ICSI condition.
A 18x response (other than 183 response) to an INVITE request is to be sent reliably according to the reliable 18x policy if:
1)... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.5 Call release | If the UE sends a BYE request, the UE shall when applicable include in the BYE request a Reason header field with a protocol value set to "RELEASE_CAUSE" and a "cause" header field parameter as specified in subclause 7.2A.18.11.2. The UE may also include the "text" header field parameter with reason-text as specified i... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6 Emergency service | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.1 General | A CS and IM CN subsystem capable UE shall follow the conventions and rules specified in 3GPP TS 22.101 [1A] and 3GPP TS 23.167 [4B] to select the domain for the emergency call attempt. If the CS domain is selected, the UE shall attempt an emergency call setup using appropriate access technology specific procedures.
NOT... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.2 Initial emergency registration | When the user initiates an emergency call, if emergency registration is needed (including cases described in subclause 5.1.6.2A), the UE shall perform an emergency registration prior to sending the SIP request related to the emergency call.
The UE shall have only one valid emergency registration at any given time. If t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.3 Initial subscription to the registration-state event package | Upon receiving the 200 (OK) to the REGISTER request that completes the emergency registration, the UE shall not subscribe to the reg event package of the public user identity specified in the REGISTER request. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.4 User-initiated emergency reregistration | The UE shall perform user-initiated emergency reregistration as specified in subclause 5.1.1.4 and:
- the UE has emergency related ongoing dialog;
- standalone transactions exist; or
- the user initiates an emergency call.
The UE shall not perform user-initiated emergency reregistration in any other cases. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.5 Authentication | When a UE performs authentication a UE shall perform the procedures as specified in subclause 5.1.1.5. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.6 User-initiated emergency deregistration | Once the UE registers a public user identity and an associated contact address via emergency registration, the UE shall not perform user-initiated deregistration of the respective public user identity and the associated contact address.
NOTE: The UE will be deregistered when the emergency registration expires. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.7 Network-initiated emergency deregistration | An emergency registration will not be deregistered by the network (see subclause 5.4.8.4). |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.8 Emergency session setup | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.8.1 General | The UE shall translate any user indicated emergency number as specified in 3GPP TS 22.101 [1A] to an emergency service URN, i.e. a service URN with a top-level service type of "sos" as specified in RFC 5031 [69].
When an initial request for a dialog or a standalone transaction, or an unknown method transmitted as part ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.8.2 Emergency session set-up in case of no registration | When establishing an emergency session for an unregistered user, the UE is allowed to receive responses to emergency requests and requests inside an established emergency session on the unprotected ports. The UE shall reject or silently discard all other messages not arriving on a protected port. Additionally, the UE s... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.8.3 Emergency session set-up within an emergency registration | After a successful initial emergency registration, the UE shall apply the procedures as specified in subclause 5.1.2A and 5.1.3 with the following additions:
1) the UE shall insert in the INVITE request, a From header field that includes the public user identity registered via emergency registration or the tel URI asso... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.8.4 Emergency session setup within a non-emergency registration | The UE shall apply the procedures as specified in subclauses 5.1.2A and 5.1.3 with the following additions:
1) the UE shall include a service URN in the Request-URI of the INVITE request in accordance with subclause 5.1.6.8.1;
2) the UE shall insert in the INVITE request, a To header field with the same emergency servi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.9 Emergency session release | Normal call release procedure shall apply, as specified in the subclause 5.1.5. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.10 Successful or provisional response to a request not detected by the UE as relating to an emergency session | If the UE receives a 1xx or 200 (OK) response to an initial request for a dialog, the response containing a P-Asserted-Identity header field set to an emergency number as specified in 3GPP TS 22.101 [1A], and:
- if a public GRUU value (pub-gruu) has been saved associated with the public user identity, the public GRUU v... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.11 eCall type of emergency service | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.11.1 General | If the upper layers request establishment of an IMS emergency call of the manually initiated eCall type of emergency service, the service URN shall be "urn:service:sos.ecall.manual" as specified in RFC 8147 [244].
If the upper layers request establishment of an IMS emergency call of the automatically initiated eCall ty... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.11.2 Initial INVITE request | If the upper layers request establishment of an IMS emergency call of the automatically initiated eCall type of emergency service or of the manually initiated eCall type of emergency service and if allowed by IP-CAN specific annex, the UE shall send an INVITE request as specified in the procedures in subclause 5.1.6.8 ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.11.3 Transfer of an updated MSD | During an emergency session established for eCall type of emergency service as described in subclause 5.1.6.11.2, optionally during a session established for an incoming IMS call from a PSAP or for a test eCall as described in subclause 5.1.6A or subclause 5.1.6B, respectively, if the UE receives an INFO request with:
... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.12 Current location discovery during an emergency call | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.12.1 General | The UE can be requested to provide the current location information during an established emergency call. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.12.2 Current location information requested | If:
1) the UE indicated a Recv-Info header field with the g.3gpp.current-location-discovery info package name in the dialog of the emergency call;
2) the UE indicated an Accept header field indicating the "application/vnd.3gpp.current-location-discovery+xml" MIME type in the dialog of the emergency call; and
3) the dia... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.6.12.3 Providing current location information | If the UE has its location information available, the UE shall provide the location information.
If the UE does not have its location information available, the UE may attempt to obtain the location information. If the location information becomes available at a subsequent time, the UE shall provide the location inform... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.7 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.8 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.1.9 P-CSCF addresses management | The UE shall locally store the P-CSCF addresses discovered during the procedures described in subclause 9.2.1.
Based on conditions identified in subclause 5.1.1.2.1 and subclause 5.1.2A.1.6, the UE marks the locally stored P-CSCF addresses as unavailable.
The UE shall not use a locally stored P-CSCF address which is ma... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2 Procedures at the P-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.1 General | Where the P-CSCF provides emergency call support, the procedures of subclause 5.2.10 shall be applied first.
Subclause 5.2.2 through subclause 5.2.9 define P-CSCF procedures for SIP that do not relate to emergency. All SIP requests are first screened according to the procedures of subclause 5.2.10 to see if they do rel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2 Registration | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.1 General | The P-CSCF shall be prepared to receive the unprotected REGISTER requests on the SIP default port values as specified in RFC 3261 [26]. The P-CSCF shall also be prepared to receive the unprotected REGISTER requests on the port advertised to the UE during the P-CSCF discovery procedure.
NOTE 1: The P-CSCF will only acce... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.2 IMS AKA as a security mechanism | When the P-CSCF receives a REGISTER request from the UE, as defined in subclause 5.2.2.1, the P-CSCF shall additionally:
1) insert the "integrity-protected" header field parameter (described in subclause 7.2A.2) with a value "yes" into the Authorization header field in case the REGISTER request was either received prot... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.3 SIP digest without TLS as a security mechanism | When the P-CSCF receives a REGISTER request from the UE, as defined in subclause 5.2.2.1, the P-CSCF shall additionally:
1) if the REGISTER request includes an Authorization header field update the "integrity-protected" header field parameter as follows:
a) if the REGISTER request does not map to an existing IP associa... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.4 SIP digest with TLS as a security mechanism | TLS is optional to implement and is used only in combination with SIP digest authentication. If the P-CSCF supports TLS, then the P-CSCF shall support TLS as described in 3GPP TS 33.203 [19]. If the P-CSCF supports TLS, the P-CSCF shall support TLS ciphersuites as described in 3GPP TS 33.203 [19].
When the P-CSCF recei... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.5 NASS-IMS bundled authentication as a security mechanism | When the P-CSCF receives a REGISTER request from the UE, as defined in subclause 5.2.2.1, the P-CSCF shall additionally:
1) perform the NASS-IMS bundled authentication related query from the P-CSCF to the TISPAN NASS;
2) if the query in step 1) is successful, insert a P-Access-Network-Info header field as described in ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.6 GPRS-IMS-Bundled authentication as a security mechanism | When the P-CSCF receives a SIP request from a GPRS-IMS-Bundled UE, the P-CSCF checks the IP address in the "sent-by" parameter of the Via header field provided by the UE as specified in RFC 3261 [6]. If the "sent-by" parameter contains a domain name, or if it contains an IP address that differs from the packet source I... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.2.7 P-CSCF reconfigured to not accept registrations | If the P-CSCF has been reconfigured to not accept initial registrations and reregistrations and to redirect incoming registrations to another P-CSCF, on recepetion of a REGISTER request the P-CSCF shall return a 305 (Use Proxy) response.
NOTE 1: As an example, this situation can happen in case the P-CSCF has been admin... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.3 Subscription to the user's registration-state event package | Upon receipt of a 200 (OK) response to the first initial REGISTER request (i.e. this was the first initial REGISTER request that the P-CSCF received from the user identified with its private user identity), the P-CSCF shall:
1) generate a SUBSCRIBE request in accordance with RFC 3680 [43] and RFC 6665 [28], with the fo... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.4 Registration of multiple public user identities | Upon receipt of a NOTIFY request for the dialog associated with the subscription to the reg event package of the user, the P-CSCF shall:
- store the information for the established dialog;
- store the expiration time as indicated in the "expires" header field parameter of the Subscription-State header field, if present... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.5 Deregistration | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.5.1 User-initiated deregistration | When the P-CSCF receives a 200 (OK) response to a REGISTER request (sent according to subclause 5.2.2) sent by this UE, then the P-CSCF shall check each Contact header field included in the response. If there is a Contact header field that contains the contact address registered via this P-CSCF via the respective secur... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.5.2 Network-initiated deregistration | Upon receipt of a NOTIFY request on the dialog which was generated during subscription to the reg event package of the UE, as described in subclause 5.2.3, including one or more <registration> element(s) which were registered by the UE with either:
- the state attribute within the <registration> element set to "termina... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6 General treatment for all dialogs and standalone transactions excluding the REGISTER method | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.1 Introduction | The procedures of subclause 5.2.6 and its subclauses are general to all requests and responses, except those for the REGISTER method. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.2 Determination of UE-originated or UE-terminated case | Upon receipt of an initial request or a target refresh request or a stand-alone transaction, the P-CSCF shall:
- perform the procedures for the UE-terminating case as described in subclause 5.2.6.4 if the request makes use of the information for UE-terminating calls, which was added to the Path header field entry of th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3 Requests initiated by the UE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.1 General for all requests | When the P-CSCF receives an initial request for a dialog or a request for a standalone transaction from a UE that is not considered as privileged sender, and:
- the request does not include any P-Preferred-Identity header field or none of the P-Preferred-Identity header fields included in the request matches any of the... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.2 General for all responses | The P-CSCF shall log all SIP responses destined for the UE that contain a "logme" Session-ID header field parameter based on local policy.
5.2.6.3.2A Abnormal cases
When the P-CSCF is unable to forward the request to the next hop by the Route header fields, as determined by one of the following:
- there is no response ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.2.6.3.3 Initial request for a dialog | When the P-CSCF receives from the UE an initial request for a dialog, 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 using stat... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.