hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.4.2 Subsequent requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.4.2.1 UE-originating case | When the S-CSCF receives the request containing the access-network-charging-info parameter in the P-Charging-Vector, the S-CSCF shall store the access-network-charging-info parameter from the P-Charging-Vector header field. The S-CSCF shall retain access-network-charging-info parameter in the P-Charging-Vector header f... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.4.2.2 UE-terminating case | When the S-CSCF receives 180 (Ringing) or 200 (OK) (to INVITE) responses containing the access-network-charging-info parameter in the P-Charging-Vector, the S-CSCF shall store the access-network-charging-info parameter from the P-Charging-Vector header field. The S-CSCF shall retain the access-network-charging-info par... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5 Call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5.1 S-CSCF-initiated session release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5.1.1 Cancellation of a session currently being established | Upon receipt of a network internal indication to release a session which is currently being established, the S-CSCF shall:
1) cancel the related dialogs by sending the CANCEL request according to the procedures described in RFC 3261 [26]; and
2) send an appropriate response to the sender of the original INVITE request. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5.1.2 Release of an existing session | Upon receipt of a network internal indication to release an existing multimedia session, the S-CSCF shall:
1) if the S-CSCF serves the calling user of the session, generate a BYE request destined for the called user based on the information saved for the related dialog, including:
- a Request-URI, set to the stored Con... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5.1.3 Abnormal cases | Upon receipt of a request on a dialog for which the S-CSCF initiated session release, the S-CSCF shall terminate the received request and answer it with a 481 (Call/Transaction Does Not Exist) response. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5.2 Session release initiated by any other entity | Upon receipt of a 2xx response for a BYE request matching an existing dialog, the S-CSCF shall delete all the stored information related to the dialog. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.5.3 Session expiration | If the S-CSCF requested the session to be refreshed periodically, and the S-CSCF got the indication that the session will be refreshed, when the session timer expires, the S-CSCF shall delete all the stored information related to the dialog. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.6 Call-related requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.6.1 ReINVITE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.6.1.1 Determination of served user | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.6.1.2 UE-originating case | For a reINVITE request or UPDATE request from the UE within the same dialog, the S-CSCF shall store the updated access-network-charging-info parameter from P-Charging-Vector header field in the received SIP request. The S-CSCF shall retain the access-network-charging-info parameter in the P-Charging-Vector header field... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.6.1.3 UE-terminating case | For a reINVITE request or UPDATE request destined towards the UE within the same dialog, when the S-CSCF receives the 200 (OK) response (to the INVITE request or UPDATE request), the S-CSCF shall store the updated access-network-charging-info parameter from the P-Charging-Vector header field. The S-CSCF shall retain th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.7 Void | 5.4.7A GRUU management
5.4.7A.1 Overview of GRUU operation
The S-CSCF provides a service of assigning and translating GRUUs for use by registered UEs, unless "Loose-Route Indication" indicating the HSS requires the loose-route mechanism as described in 3GPP TS 29.228 [14] has been provisioned in the service profile of ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8 Emergency service | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.1 General | The S-CSCF shall handle the emergency registration as per the needs of the normal registration.
NOTE 1: Emergency specific procedures for the Cx interface are specified in annex G in 3GPP TS 29.228 [14].
NOTE 2: When receiving an emergency service request then the S-CSCF handles the emergency service request as per the... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.2 Initial emergency registration or user-initiated emergency reregistration | When the S-CSCF receives a REGISTER request; and the Contact header field includes a "sos" SIP URI parameter that indicates that this is an emergency registration, the S-CSCF shall perform the actions as specified in subclause 5.4.1.1 with the following additions:
1) when handling unprotected REGISTER request or protec... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.3 User-initiated emergency deregistration | When S-CSCF receives a REGISTER request with the registration expiration interval value containing zero and the Contact header field contains a contact address that has been registered for emergency service (i.e. the "sos" SIP URI parameter that indicates that this is an emergency registration is included in the Contac... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.4 Network-initiated emergency deregistration | The S-CSCF shall not perform a network-initiated emergency deregistration. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.5 Network-initiated emergency re-authentication | If a given public user identity and the associated contact address have been registered via emergency registration, the S-CSCF shall not re-authenticate this public user identity. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.6 Subscription to the event providing registration state | If a S-CSCF receives a SUBSCRIBE request addressed to S-CSCF containing the Event header field with the reg event package with the Contact header field that contains a contact address that has been registered for emergency service, the S-CSCF shall reject the SUBSCRIBE request for the reg-event package by sending a 489... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.4.8.7 Notification of the registration state | When the user performs an emergency registration or when the emergency registration expires, the S-CSCF shall not send a NOTIFY request to the subscribers to the reg event package of the respective user.
The contact address that has been registered for emergency service shall not be included in the NOTIFY requests sent... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5 Procedures at the MGCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.1 General | The MGCF, although acting as a UA, does not initiate any registration of its associated addresses. These are assumed to be known by peer-to-peer arrangements within the IM CN subsystem. Therefore table A.4/1 and dependencies on that major capability shall not apply.
The use of the Path and Service-Route header fields s... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.2 Subscription and notification | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3 Call initiation | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3.1 Initial INVITE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3.1.1 Calls originated from circuit-switched networks | When the MGCF receives an indication of an incoming call from a circuit-switched network, the MGCF shall:
1) generate an INVITE request:
- set the Request-URI to the "tel" format using an E.164 address or to the "sip" format using an E164 address in the user portion and set user=phone in accordance with 3GPP TS 29.163 ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3.1.2 Calls terminating in circuit-switched networks | When the MGCF receives an initial INVITE request with Supported header field indicating "100rel", the MGCF shall:
1) based on local policy, store the "fe-identifier" header field parameter of the P-Charging-Vector header field, if present;
2) store the value of the "orig-ioi" header field parameter received in the P-Ch... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3.2 Subsequent requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3.2.1 Calls originating in circuit-switched networks | When the MGCF generate a subsequent request in accordance with 3GPP TS 29.163 [11B], the MGCF shall:
a) add a P-Charging-Vector header field with the "icid-value" header field parameter set to the value populated in the initial request for the dialog and a type 2 "orig-ioi" header field parameter. The MGCF shall set th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.3.2.2 Calls terminating in circuit-switched networks | When the MGCF receives a subsequent request, the MGCF shall:
1) store the value of the "orig-ioi" header field parameter received in the P-Charging-Vector header field, if present.
NOTE: Any received "orig-ioi" header field parameter will be a type 2 IOI. The type 2 IOI identifies the sending network of the request mes... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.4 Call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.4.1 Call release initiated by a circuit-switched network | When the MGCF receives an indication of call release from a circuit-switched network, the MGCF shall:
- send a BYE request to the UE. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.4.2 IM CN subsystem initiated call release | NOTE: The release of a call towards the circuit-switched network additionally requires signalling procedures other than SIP in the MGCF that are outside the scope of this document. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.4.3 MGW-initiated call release | When the MGCF receives an indication from the MGW that the bearer was lost, the MGCF shall:
- send a BYE request towards the UE; and
- may include Error-Info header field with a pointer to additional information indicating that bearer was lost. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.5 Call-related requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.5.1 Session modification | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.5.1.0 General | This subclause applies after the 2xx response to the initial INVITE request has been sent or received. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.5.1.1 Session modifications originating from circuit-switched networks | If the precondition mechanism was used during the session establishment, as described in subclause 5.5.3.1.1 or 5.5.3.1.2, the MGCF shall indicate support of the precondition mechanism during a session modification. If the precondition mechanism was not used during the session establishment, the MGCF shall not indicate... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.5.1.2 Session modifications terminating in circuit-switched networks | When the MGCF receives a reINVITE request for hold/resume operation, the MGCF shall:
- send a 100 (Trying) response;
- after performing interaction with MGW to hold/resume the media flow, send a 200 (OK) response.
Upon receiving a reINVITE request, an UPDATE request, or a PRACK request that indicates support for the pr... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.5.6 Further initial requests | When the MGCF responds to an OPTIONS request with a 200 (OK) response, the MGCF may include a message body with an indication of the DTMF capabilities and supported codecs of the MGCF/MGW.
NOTE: The detailed interface for requesting MGCF/MGW capabilities is not specified in this version of the document. Other solutions... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.6 Procedures at the BGCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.6.1 General | The use of the Path and Service-Route header fields shall not be supported by the BGCF.
For all SIP transactions identified:
- if priority is supported, as containing an authorised Resource-Priority header field, or, if such an option is supported, relating to a dialog which previously contained an authorised Resource-... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.6.2 Common BGCF procedures | When determining where to route the received request, the originating BGCF may use the information obtained from other protocols or any other available databases.
The BGCF may support retrieval of NP data as part of the procedures to determine where to route the request. Retrieval of NP data by the BGCF is subject to l... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.6.3 Specific procedures for INVITE requests and responses | When the BGCF receives an INVITE request that contains a Feature-Caps header field with the "+g.3gpp.home-visited" header field parameter, the BGCF shall decide based on local policy whether to perform loopback routeing for this request. The BGCF shall:
a) if loopback routeing is not to be performed for this request re... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.6.4 Specific procedures for subsequent requests and responses | When the BGCF receives a subsequent request whose initial request applied loopback routeing, the BGCF shall:
a) remove the "orig-ioi" header field parameter received in the P-Charging-Vector header field, if present. The BGCF shall insert a type 1 "orig-ioi" header field parameter into the P-Charging-Vector header fiel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7 Procedures at the Application Server (AS) | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1 Common Application Server (AS) procedures | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.0 General | When sending a failure response to any received request, depending on operator policy, the AS 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 "as" and optionally an appropriate fe-param part of the URN set i... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.1 Notification about registration status | The AS may support the REGISTER method in order to discover the registration status of the user. If a REGISTER request arrives and the AS supports the REGISTER method, the AS shall store the registration expiration interval value from the request and generate a 200 (OK) response or an appropriate failure response. For ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.2 Extracting charging correlation information | When an AS receives an initial request for a dialog or a request for a standalone transaction, the AS shall store the values received in the P-Charging-Vector header field, e.g. "orig-ioi" header field parameter, if present, and "icid-value" header field parameter, and retain the P-Charging-Vector header field in the m... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.3 Access-Network-Info and Visited-Network-ID | The AS may receive information about the served user core network in REGISTER requests from S-CSCF. This information can be obtained either from the P-Access-Network-Info header field and P-Visited-Network-ID header field in the REGISTER request or can be obtained from those header fields in the body of the REGISTER re... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.4 User identity verification at the AS | The procedures at the AS to accomplish user identity verification are described with the help of figure 5-1. Procedures for user identity verification using the Identity header field are specified in subclause 5.7.1.25.
NOTE: Different means can be used to represent or transport the credentials. Such mechanisms are sub... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.5 Request authorization | Once the AS have tried to verify the identity of the user, the AS either has a verified identity of the user or it considers the user as anonymous.
If the user is considered anonymous, the AS shall check whether the authorization policy defined for this request allows anonymous requests. If anonymous requests are allow... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.6 Event notification throttling | If the AS has a local configuration information limiting the rate at which notification generation is allowed, then the AS shall take that information into account. Such local configuration information could be e.g. the shortest time period between issuing consecutive NOTIFY requests. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.7 Local numbering | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.7.1 Interpretation of the numbers in a non-international format | If home operator's local policy defines a prefix string(s) to enable subscribers to differentiate dialling a geo-local number and/or a home-local number and if the phone number in a non-international format in the Request-URI includes such a prefix, the AS shall interpret the received number in a non-international form... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.7.2 Translation of the numbers in a non-international format | When an AS receives a request having a geo-local number in a non-international format in the Request-URI, the AS shall use the "phone-context" tel URI parameter to determine the visited access network, if the "phone-context" tel URI parameter in the Request-URI is available. If the "phone-context" tel URI parameter in ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.8 GRUU assignment and usage | It is possible for an AS to use a GRUU referring to itself when inserting a contact address in a dialog establishing or target refreshing SIP message.
This specification does not define how GRUUs are created by the AS; they can be provisioned by the operator or obtained by any other mechanism. The GRUU shall remain val... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.9 Use of ICSI and IARI values | Based on service logic, an AS can validate an ICSI value received in an Accept-Contact header field or received in a P-Asserted-Service header field and reject the request if necessary.
A trusted AS may insert a P-Asserted-Service header field in a request for a new dialog or standalone transaction. An untrusted AS may... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.10 Carrier selection | An AS may play a role in support of carrier selection as defined in RFC 4694 [112].
NOTE 1: In general, ASs do not need to support carrier selection, Rather a specific AS or a few ASs in a network will be used for carrier selection,
When an AS that supports carrier selection receives an initial request with a Request-U... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.11 Tracing | An AS can retrieve tracing configuration information from the HSS via the Sh reference point. The AS tracing configuration can use the parameters specified in 3GPP TS 24.323 [8K] but need not structure them as a management object. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.12 Delivery of original destination identity | If the service the AS provides needs to deliver the original destination identity to the UE, the AS shall insert a new hi-entry to the last hi-entry of History-Info header field including "mp" header field parameter as specified in RFC 7044 [66].
NOTE: If the "mp" header field parameter is present in the hi-entries wit... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.13 CPC and OLI | The AS may populate the "cpc" and "oli" URI parameters in each initial request for a dialog or a request for a standalone transaction in the tel URI or SIP URI representation of telephone numbers in the P-Asserted-Identity header field based on their origin source. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.14 Emergency transactions | Identification of emergency transactions for termination in the public network by an AS are outside the scope of this document, and are dependent on many application specific considerations.
Where an AS decides to generate an emergency request on behalf of its served user, the AS shall meet the following conditions:
1)... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.15 Protecting against attacks using 3xx responses | The AS upon receiving a 3xx response to a request from the served UE that contains a Contact header field may remove the Contact header field or modify the response code from 3xx to an appropriate non 2xx response code (e.g. 5xx response code) based on operator policy before sending the response towards the UE.
NOTE: A... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.16 Support of Roaming Architecture for Voice over IMS with Local Breakout | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.16.1 Preservation of parameters | An AS in a network supporting the roaming architecture for voice over IMS with local breakout shall not change the value of the "icid-value" header field parameter in the P-Charging-Vector header field received in the INVITE request when the AS sends any request or response related to an INVITE transaction.
NOTE: An AS... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.16.2 Preference for loopback routeing not to occur | When the AS is accessed by a network supporting roaming architecture for voice over IMS with local breakout, and the incoming INVITE request contains a Feature-Caps header field with the "+g.3gpp.home-visited" header field parameter, the AS can indicate to the S-CSCF its preference for loopback routeing not to occur by... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.17 Delivery of network provided location information | If the AS supports delivery of network provided location information, and the AS performs the retrieval of cell id and/or UE time zone via Sh interface, the AS shall insert the P-Access-Network-Info header field with the cell id, local-time-zone parameter and/or the "daylight-saving-time" parameter, including a "networ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.18 Delivery of MRB address information | A visited MRB address can be received during session establishment. If an AS receives the URI of an MRB in a "+g.3gpp.mrb" header field parameter included in a Feature-Caps header field of an INVITE request, it shall store this URI. If the AS requests allocation of MRF resources from an MRB in its own network, either i... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.19 Overload control | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.19.1 Outgoing subscriptions to load-control event | Based on operator policy, the AS may subscribe to the load-control event package with one ore 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 physical device hosting the SIP entity is power-cycled) or thro... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.19.2 Incoming subscriptions to load-control event | If subscriptions to load-control event package is supported, the AS shall handle incoming subscriptions to the load-control event package in accordance with RFC 6665 [28] and with RFC 7200 [201]. When the AS receives a SUBCRIBE request for the load-control event from an unauthorised or unexpected source, the AS shall g... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.20 Procedures in the AS for resource sharing | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.20.1 General | An AS supporting resource sharing shall use the "+g.3gpp.registration-token" header field parameter in the Contact header field of the incoming third-party REGISTER request and the "+g.3gpp.registration-token" header field parameter in the Feature-Caps header field in the initial INVITE request or provisional responses... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.20.2 UE-originating case | If the AS supporting resource sharing receives a response or request destined to the served user containing a Resource-Share header field, the AS shall remove that header field from the outgoing response or request.
Upon receiving an SDP answer in a provisional response or a 200 (OK) response to an initial INVITE reque... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.20.3 UE-terminating case | 5.7.1.20.3.1 Determine resource sharing using the initial SDP offer
Upon receiving an initial INVITE request containing an initial SDP offer destined for the served user, the AS supporting resource sharing shall if at least one registered UE is served by a P-CSCF supporting resource sharingdetermine if resource sharing... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.20.4 Updating the resource sharing options | If the AS during the duration of the call determines that the resource sharing options needs to be changed (e.g. if media streams are added by the UE), then the AS shall include a Resource-Share header field with the updated resource sharing options as specified in subclause 7.2.13, in the outgoing request or response ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.20.5 Abnormal cases | If the AS receives a request or response from a served user containing a Resource-Share field with the value "no-media-sharing", the AS shall no longer apply resource sharing with sessions involving the UE sending the request or response.
If the AS receives a request or response from a served user containg an SDP offer... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.21 Dynamic Service Interaction | If an AS supports dynamic service interaction, the AS should insert the Service-Interact-Info header field into the SIP messages before those messages are sent out. The Service-Interact-Info field is filled with the service identities of the services which have been executed. Additionally, the AS may insert into the Se... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.22 Service access number translation | When the AS is accessed by a service access number (e.g. toll free, premium service) and performes a translation of this number into a routeable number, the AS shall include in the outgoing request:
1) the Request-URI set to the targeted SIP URI containing the "cause" SIP URI parameter, defined in RFC 4458 [68], set to... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.23 Procedures in the AS for priority sharing | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.23.1 General | An AS supporting priority sharing and if according to local policy shall apply priority sharing as specified in the following subclauses.
NOTE: The MCPTT server is the only AS in the present document defined to use priority sharing (see 3GPP TS 24.379 [8ZE]).
An AS supporting priority sharing shall only include a Prior... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.23.2 Session originating procedures | If the Feature-Caps header field with the g.3gpp.priority-share feature-capability indicator was included in the "message/sip" MIME body in the third-party REGISTER request and when the AS determines that priority sharing can be applied, the AS supporting priority sharing shall:
1) include the Priority-Share header fie... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.23.3 Session terminating procedures | If the incoming REGISTER request contained in the "message/sip" MIME body of a third-party REGISTER request the g.3gpp.priority-share feature-capability indicator in a Feature-Caps header field and when the AS determines that priority sharing can be applied, the AS supporting priority sharing shall:
1). include the Pri... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.24 Handling re-INVITE request collisions | An AS shall handle re-INVITE request collisions as specified in RFC 3261 [26] with the clarification in this subclause.
When the AS receives a SIP 491 (Request Pending) response to a re-INVITE request initiated by the AS and sent towards the remote user, the AS shall:
1) if the AS is serving the user at the originating... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.25 Assertion verification using the Identity header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.25.1 General | RFC 8224 [252] describes a mechanism where an authentication service after verifying the calling number identity inserts a signature over selected header fields. A verification service can then use this signature to trust the correctness of the identity.
RFC 8946 [265] describes a mechanism where an authentication serv... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.25.2 Originating procedures | An originating AS supporting the calling number verification using signature verification and attestation information, as defined in subclause 3.1:
1) may based on local policy insert an Identity header field as specified in RFC 8224 [252] for all initial INVITE requests and MESSAGE requests and shall for this purpose ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.25.3 Terminating procedures | Upon receiving an initial INVITE request or a MESSAGE request containing one or more Identity header fields, an AS supporting the calling number verification using signature verification and attestation information, as defined in subclause 3.1, shall if the network indicated support for the calling number verification ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.25.4 Procedures over the Ms reference point | If the AS receives a verificationRequest as specified in annex V, the AS verifies the request and when verified generates a verificationResponse, as specified in annex V, including a "verstat" claim for the verified identity.
If the AS receives a signingRequest, specified in annex V, the AS sends the signed information... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.26 Procedures in the AS for 3GPP PS data off | An AS that supports 3GPP PS data off can receive in the message/SIP MIME body in a third party REGISTER request the REGISTER request sent by the UE. If this REGISTER request contains a "+g.3gpp.ps-data-off" Contact header field parameter the AS can determine that the UE supports 3GPP PS data off, and the value of the p... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.27 AS support for access update procedures | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.27.1 General | The AS can indicate that it supports in-call access update procedures by sending a feature-capability indicator including a public service identity indicating to where to send the updates.
When the AS receives a MESSAGE request with a P-Charging-Vector header field containing an "icid-value" header field parameter matc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.27.2 Originating procedures | If the AS supports in-call access update procedures and the AS is interested in receiving updates of changes of IP-CAN or PLMN the AS shall include in responses to an initial INVITE request a g.3gpp.in-call-access-update feature-capability indicator with a value set to a public service identity resolving to the AS.
Whe... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.27.3 Terminating procedures | If the AS supports access update procedures and the AS is interested in receiving updates of changes of IP-CAN or PLMN the AS shall include in the INVITE request a g.3gpp.in-call-access-update feature-capability indicator with a value set to a public service identity resolving to the AS.
When the AS receives a Handover... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.