hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.1 General | Beyond UAV related requirements, the 3GPP can be used to support for a wide range of applications and scenarios by using low altitude UAVs in various commercial and government sectors. New service level requirements and KPIs for supporting various UAV applications by the 3GPP system have been identified and specified e... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.2 Network exposure for UAV services | [R-6.2-001] The 3GPP system shall provide means to allow a 3rd party to request and obtain real-time monitoring the status information (e.g., location of UAV, communication link status) of a UAV.
[R-6.2-002] Based on operator 's policy, the 3GPP system shall provide means to provide a 3rd party with the information reg... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.3 Service restriction for UEs onboard of UAV | [R-6.3-001] The 3GPP network shall be able to support network-based 3D space positioning (e.g., with altitude 30~300m) of a UE onboard UAV.
[R-6.3-002] The 3GPP system shall be able to notify the authorized third party of potential stopping of connectivity service before the UE onboard of UAV enters an area (e.g., due ... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.4 Requirements for UxNB | [R-6.4-001] The 5G system shall be able to support UxNBs to provide enhanced and more flexible radio coverage.
[R-6.4-002] The 3GPP system shall be able to provide suitable means to control the operation of the UxNBs (e.g. to start operation, stop operation, replace UxNB etc.).
[R-6.4-003] The 3GPP system shall be able... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.5 C2 communication | [R-6.5-001] The 3GPP system shall support C2 communication with required QoS for pre-defined C2 communication models (e.g. using direct ProSe Communication between UAV and the UAV controller, UTM-navigated C2 communication based on flight plan between UTM and the UAV).
[R-6.5-002] The 3GPP system shall support C2 commu... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.6 UAV safety | [R-6.6-001] The 5G system shall support means to determine whether UTM supports regulatory requirements e.g., maximum VLOS distance between the UAV and the UAV controller.
NOTE: The requirement applies to the case of both UAV and UAV controller connected to the 3GPP network.
[R-6.6-002] Based on operator’s policy, the ... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.7 Flight path and zones management | [R-6.7-001] Based on a 3rd party request and operator’s policy, the 5G system shall be able to reconfigure network resources to provide the required QoS along a UAV planned flight path, e.g. at particular geographical area(s) and time(s).
[R-6.7-002] The 5G system shall be able to support mechanisms for the UTM to conf... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6.8 UTM assistance requirements | [R-6.8-001] Based on operator’s policy, the 5G system shall be able to provide UTM with the information about geographic areas where UAV service requirements could or could not be met based on predicted network conditions and QoS (e.g. bitrate, latency, reliability).
[R-6.8-002] Based on a 3rd party request, the 5G sys... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7 Performance requirements | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.1 KPIs for services provided to the UAV applications | The 5G system shall be able to provide uncrewed aerial vehicle with the service performance requirements reported in Table 7.1-1.
UAV originated QoS in the table refers to the QoS of Uplink data (e.g. from UAV to the network side). UAV terminated QoS is the QoS of downlink data (e.g. from the network side to UAV).
The ... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.2 KPIs for UAV command and control | UAVs may use a variety of flight command and control modes. Command and control (C2) communications refers to the two-way communication, which may include video, required to control the operation of the UAV itself. C2 messages may be communicated with the UAV controller, the UTM or both and may or may not be periodic. ... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.3 Positioning performance requirements | Table 7.3-1 below lists typical scenarios and the corresponding positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
NOTE: The column on "Corresponding Positioning Service Level in TS 22.261" maps the scenarios listed in Table 7.3-1 to the service levels defined i... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 7.4 Other requirements | [R-7.4-001] The 5G system shall support a mechanism to switch between C2 communication modes for UAS operation, e.g. from indirect C2 communication to direct C2 communication, and ensure the disconnect time is below the latency requirements. [R-7.4-002] The 3GPP system shall enable concurrent communications between the... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 1 Scope | The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
The present document is applicable to:
- the interface between the User Equipment (UE) and the Call Se... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3 Definitions of terms, symbols and abbreviations | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3.1 Terms | For the purposes of the present document, the following terms apply.
3GPP PS data off status: indicates state of usage of the 3GPP PS data off. 3GPP PS data off status at the UE can be either "active" or "inactive".
Country: For the purposes of emergency service URNs in the present document, i.e. a service URN with a t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3.2 Symbols | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
1xx A status-code in the range 101 through 199, and excluding 100
18x A status-code in the range 180 through 189
2xx A status-code in the range 200 through 299
3xx A status-code in the range 300 through 399
4xx A status-code in the range 400 t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4 General | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.1 Conformance of IM CN subsystem entities to SIP, SDP and other protocols | SIP defines a number of roles which entities can implement in order to support capabilities. These roles are defined in annex A.
Each IM CN subsystem functional entity using an interface at the Gm reference point, the Ma reference point, the Mg reference point, the Mi reference point, the Mj reference point, the Mk ref... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.2 URI and address assignments | In order for SIP and SDP to operate, the following prerequisite conditions apply:
1) I-CSCFs used in registration are allocated SIP URIs. Other IM CN subsystem entities may be allocated SIP URIs. For example sip:pcscf.home1.net and sip:<impl-specific-info>@pcscf.home1.net are valid SIP URIs. If the user part exists, it... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.3 Routeing principles of IM CN subsystem entities | Each IM CN subsystem functional entity shall apply loose routeing policy as described in RFC 3261 [26], when processing a SIP request. In cases where the I-CSCF, IBCF, S-CSCF and the E-CSCF may interact with strict routers in non IM CN subsystem networks, the I-CSCF, IBCF, S-CSCF and E-CSCF shall use the routeing proce... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4 Trust domain | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.1 General | A trust domain can apply for specific header fields, tel URI parameters and SIP URI parameters within the IM CN subsystem.
For the IM CN subsystem, this trust domain consists of the functional entities that belong to the same operator's network (P-CSCF, the eP-CSCF, the E-CSCF, the I-CSCF, the IBCF, the S-CSCF, the BGC... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.2 P-Asserted-Identity | RFC 3325 [34] provides for the existence and trust of an asserted identity within a trust domain. A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Asserted-Identity header field according to RFC 3325 [34] when SIP signalling crosses the boundary of the trust domain.... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.3 P-Access-Network-Info | A functional entity at the boundary of the trust domain shall remove any P-Access-Network-Info header field according to RFC 7315 [52]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.4 History-Info | A functional entity at the boundary of the trust domain will need to determine whether to remove the History-Info header field according to RFC 7044 [66] subclause 10.1.2 when SIP signalling crosses the boundary of the trust domain. Subclause 5.4 identifies additional cases for the removal of the History-Info header fi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.5 P-Asserted-Service | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Asserted-Service header field according to RFC 6050 [121] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.6 Resource-Priority | If Priority verification using assertion of priority information features described in subclause 3.1 is supported then a functional entity at the boundary of the trust domain will need to determine, based on the operator policy, whether to remove a Resource-Priority header field.
Otherwise, if Priority verification usi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.7 Reason (in a response) | A functional entity shall only include a Reason header field in a response forwarded to another entity within the trust domain (as specified in RFC 6432 [130]). If a response is forwarded to an entity outside the trust domain, the functional entity shall remove the Reason header field from the forwarded response.
NOTE:... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.8 P-Profile-Key | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Profile-Key header field as defined in RFC 5002 [97] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.9 P-Served-User | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Served-User header field according to RFC 5502 [133] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.10 P-Private-Network-Indication | A functional entity shall only include a P-Private-Network-Indication header field in a request forwarded to another entity within the trust domain. If a request is forwarded to an entity outside the trust domain, the functional entity shall remove the P-Private-Network-Indication header field from the forwarded reques... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.11 P-Early-Media | A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Early-Media header field as defined in RFC 5009 [109] when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.12 CPC and OLI | Entities in the IM CN subsystem shall restrict "cpc" and "oli" URI parameters to specific domains that are trusted and support the "cpc" and "oli" URI parameters. Therefore for the purpose of the "cpc" and "oli" URI parameters within this specification, a trust domain also applies.
SIP functional entities within the tr... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.13 Feature-Caps | A functional entity at the boundary of the trust domain shall remove all Feature-Caps header fields received from UEs and external networks outside the trust domain.
NOTE: A UE that is a privileged sender is considered as part of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.14 Priority | Based on local policy, a functional entity at the boundary of the trust domain shall remove all Priority header fields with a "psap-callback" header field value. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.15 iotl | Entities in the IM CN subsystem shall restrict "iotl" URI parameter to specific domains that are trusted and support the "iotl" URI parameter. Support implies that the parameter is removed before the containing request is sent over an interface of a different type. Therefore for the purpose of the "iotl" URI parameter ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.16 Restoration-Info | A functional entity at the boundary of the trust domain will need to determine whether to remove the Restoration-Info header field when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.17 Relayed-Charge | Entities in the IM CN subsystem shall restrict the Relayed-Charge header field to specific domains that are trusted and support the Relayed-Charge header field. Trust implies that the sending domain intends the receiving domain to have the contents of this header field. Therefore for the purpose of the Relayed-Charge h... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.18 Service-Interact-Info | A functional entity at the boundary of the trust domain shall remove all Service-Interact-Info header fields defined in subclause 7.2.when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.19 Cellular-Network-Info | A functional entity shall only include a Cellular-Network-Info header field in a request forwarded to another entity within the trust domain. If a request is forwarded to an entity outside the trust domain, the functional entity shall remove the Cellular-Network-Info header field from the forwarded request. If a reques... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.20 Response-Source | A functional entity at the boundary of the trust domain will need to determine whether to remove the Response-Source header field according to subclause 7.2.17. when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.21 Attestation-Info header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Attestation-Info header field according to subclause 7.2.18. when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.22 Origination-Id header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Origination-Id header field according to subclause 7.2.19 when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.23 Additional-Identity header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Additional-Identity header field according to subclause 7.2.20 when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.4.24 Priority-Verstat header field | A functional entity at the boundary of the trust domain will need to determine whether to remove the Priority-Verstat header field according to subclause 7.2.21 when SIP signalling crosses the boundary of the trust domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5 Charging correlation principles for IM CN subsystems | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.1 Overview | This subclause describes charging correlation principles to aid with the readability of charging related procedures in clause 5. See 3GPP TS 32.240 [16] and 3GPP TS 32.260 [17] for further information on charging.
The IM CN subsystem generates and retrieves the following charging correlation information for later use w... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.2 IM CN subsystem charging identifier (ICID) | The ICID is the session level data shared among the IM CN subsystem entities including ASs in both the calling and called IM CN subsystems. The ICID is used also for session unrelated messages (e.g. SUBSCRIBE request, NOTIFY request, MESSAGE request) for the correlation with CDRs generated among the IM CN subsystem ent... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.3 Access network charging information | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.3.1 General | The access network charging information are the media flow level data shared among the IM CN subsystem entities for one side of the session (either the calling or called side). GPRS charging information (GGSN identifier and PDP context information) is an example of access network charging information. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.3.2 Access network charging information | The IP-CAN provides the access network charging information to the IM CN subsystem. This information is used to correlate IP-CAN CDRs with IM CN subsystem CDRs, i.e. the access network charging information is used to correlate the bearer level with the session level.
The access network charging information is generated... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.4 Inter operator identifier (IOI) | The Inter Operator Identifier (IOI) is a globally unique identifier to share between sending and receiving networks, service providers or content providers.
The sending network populates the "orig-ioi" header field parameter of the P-Charging-Vector header field in a request and thereby identifies the operator network ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.5 Charging function addresses | Charging function addresses are distributed to each of the IM CN subsystem entities in the home network for one side of the session (either the calling or called side) and provide a common location for each entity to send charging information. Charging Data Function (CDF) addresses are used for offline billing. Online ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.6 Relayed charge parameters | Where there is a desire to pass charging information to an entity over an interface to which the charging information is not directly related, then the Relayed-Charge header field is used. This is used only in accordance with the capabilities specified in this document, which currently specify only the relay of a trans... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.7 Loopback-indication parameter | When there is a desire to send the information that loopback has been applied to an entity, then the loopback-indication parameter is used. This parameter can e.g. be evaluated when processing the P-CSCF CDR and possibly the ATCF CDR to know whether or not to attempt to locate a correlated TRF CDR even for the non-loop... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.8 IM CN subsystem Functional Entity Identifier | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.8.1 General | Different rules for generating and processing of charging information apply. In order to inform the billing domain which IM CN subsystem functional entities have created charging information, the IM CN subsystem functional entities and ASs include an "fe-identifier" header field parameter as additional information in t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.8.2 Tracking of IM CN subsystem functional entities generating charging information | Each IM CN subsystem functional entity that generates charging events, includes its own address or specific IM CN subsystem functional entity identifier within the "fe-addr" element of the "fe-identifier" header field parameter of the P-Charging-Vector header field into the initial SIP request to be sent from own domai... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.5.8.3 Tracking of applications generating charging information | Each application for which the hosting AS is generating charging events, includes the address or specific identifier of the AS within the "as-addr" element and the application identifier within the "ap-id" element of the "fe-identifier" header field parameter of the P-Charging-Vector header field into the initial SIP r... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.6 Support of local service numbers | For the IM CN subsystem, the support of local service numbers is provided by an AS in the subscriber's home network as described in subclause 5.7.1.7. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7 Emergency service | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7.1 Introduction | The need for support of emergency calls in the IM CN subsystem is determined by national regulatory requirements. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7.2 Emergency calls generated by a UE | If the UE cannot detect the emergency call attempt, the UE initiates the request as per normal procedures as described in subclause 5.1.2A. Depending on network policies, for a non-roaming UE or for a roaming UE where the P-CSCF is in the same network where the UE is roaming an emergency call attempt can succeed even i... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7.3 Emergency calls generated by an AS | In certain circumstances an AS can identify that a request is an emergency call. This may relate to a request received from a UE (or subscription-based business trunking), or may be a call generated by an AS on behalf of a UE as far as the IM CN subsystem operation is concerned. These applications are outside the scope... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7.4 Emergency calls received from an enterprise network | An IBCF can also route emergency calls received from an enterprise network (peering-based business trunking) to an E-CSCF. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7.5 Location in emergency calls | A number of mechanisms also exist for providing location in support of emergency calls, both for routeing to a PSAP, and for use by the PSAP itself, in the IM CN subsystem:
a) by the inclusion by the UE of the Geolocation header field containing a location by reference or by value (see RFC 6442 [89]);
b) by the inclusi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.7.6 eCall type of emergency service | A PSAP supporting eCall over IMS supports:
- receipt of the minimum set of emergency related data (MSD) in an INVITE or INFO request;
- the EmergencyCallData.eCall.MSD Info-Package and the ability to request an updated MSD by including an "application/EmergencyCallData.Control+xml" MIME body part containing a "request"... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.8 Tracing of signalling | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.8.1 General | IM CN subsystem entities can log SIP signalling, for debugging or tracing purposes, as described in 3GPP TS 32.422 [17A]. Debugging of SIP signalling is configured using the 3GPP IMS service level tracing management object (MO), specified in 3GPP TS 24.323 [8K]. This management object can provide configuration data to ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.8.2 Trace depth | The depth parameter in trace control and configuration indicates which SIP requests and responses are logged. If the trace depth is "maximum" then all requests and responses within a dialog or standalone transaction are logged. If the trace depth is "minimum" then all requests and responses except for non-reliable 1xx ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9 Overlap signalling | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.1 General | This subclause explains the overlap signalling impacts on the core entities of the IM CN subsystem.
The support of overlap signalling, and each of the overlap signalling method, within the IM CN subsystem, are optional and is dependent on the network policy.
Only one overlap signalling method shall be used within one I... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.2 Overlap signalling methods | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.2.1 In-dialog method | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.2.1.1 General | The in-dialog method uses INFO requests or INVITE requests in order to transport additional digits. Before an early dialog has been established, upon reception of a 404 (Not Found) or 484 (Address Incomplete) response to an earlier INVITE request, new INVITE requests will be sent to transfer additional digits (as speci... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.2.2 Multiple-INVITE method | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.2.2.1 General | The multiple-INVITE method uses INVITE requests with the same Call ID and From header in order to transport digits (as specified in 3GPP TS 29.163 [11B]). |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.3 Routeing impacts | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.3.1 General | If overlap dialing is supported, the IM CN subsystem needs to be configured in such a manner that erroneous routeing of INVITE requests with incomplete numbers towards others entities than the corresponding INVITE requests with full numbers is avoided, for instance towards a default destination for unknown numbers such... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.3.2 Deterministic routeing | If the multiple-INVITE method is used for overlap signalling, if an entity receives a INVITE request outside an existing dialog with the same Call ID and From header field as a previous INVITE request during a certain period of time, the entity shall route the new INVITE request to the same next hop as the previous INV... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.9.3.3 Digit collection | Entities performing routeing decicisions may require additional digits for a decision where to route an INVITE request. These entities may interact with a routeing database to reach this decision.
If no suitable entry in a database is found for the digits received in a INVITE request, an entity can reject the INVITE re... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.10 Dialog correlation for IM CN subsystems | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.10.1 General | The Call-ID header field in combination with the tags in the From header field and in the To header field is the standard mechanism to identify SIP messages which belong to the same dialog. However the Call-ID header field is often changed by B2BUAs and other SIP intermediaries in the end-to-end message path.
To solve ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.10.2 CONF usage | In case of the activation of a 3PTY conference, in the INVITE request to the CONF AS the Session-ID header field is added to the URIs in the URI list, in order to indicate the dialogs which are to be included to the 3PTY conference at the CONF AS, as described in 3GPP TS 24.147 [8B]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.11 Priority mechanisms | In support of priority, the IM CN subsystem uses the mechanisms of RFC 4412 [116]. The request for prioritisation of a transaction / dialog may, for some deployments, be marked with the Resource-Priority header field by the UE. For other deployments, the request is not marked for priority by the UE, but the request is ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.12 Overload control | Usage of overload control is independent of the nature of any SIP using entity, i.e. there are no specific requirements for any particular IMS functional entity implementing SIP. The capability however is not extended to the UE except when performing the function of an externally attached network.
Two mechanisms are de... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.13 II-NNI traversal scenario | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.13.1 General | Within the IM CN subsystem, the signalling path between a calling user and a called user can be divided into one or more traffic legs, referred to as II-NNI traversal scenarios. Each II-NNI traversal scenario can span networks belonging to different operators and will have its own characteristics that can be different ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.13.2 Identifying the II-NNI traversal scenario | The "iotl" SIP URI parameter specified in RFC 7549 [225] containing traffic leg information can be used to identify the II-NNI traversal scenario type. The II-NNI traversal scenario type can be used by intermediary entities (e.g. IBCF and transit networks) to make policy decisions related to e.g. media anchoring, scree... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.13.3 Security aspects | When receiving a dialog creating SIP request or a standalone SIP request from outside the trust domain the IBCF acting as an entry point removes any "iotl" SIP URI parameter according to subclause 4.4.15 and assume the default II-NNI traversal scenario type or can use trusted elements of the SIP request to determine th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.14 Restoration procedures | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.14.1 General | The present document includes optional restoration procedures for failure of P-CSCF and S-CSCF. The general mechanism is to inform the UE that one of the entities along its registration path is not working, and hence the UE needs to perform an initial registration. For systems providing access to IM CN subsystem using ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.14.2 P-CSCF restoration procedures | P-CSCF restoration procedures are implemented in the S-CSCF, the IBCF and the UE.
When the UE originates a session it can detect that a P-CSCF is not reachable based on no response from the P-CSCF in which case the UE selects another P-CSCF if possible and performs a new initial registration.
UDM/HSS or HSS based P-CSC... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.14.3 S-CSCF restoration procedures | The P-CSCF can inform the UE about S-CSCF failures in a 504 (Server Time-out) response using the 3GPP IM CN subsystem XML body defined in subclause 7.6, in accordance with subclause 5.2.6.3.2A, when the P-CSCF is unable to forward a request to an S-CSCF.
When the S-CSCF receives a request initiated by the served user f... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.15 Resource sharing | Resource sharing allows two or more sessions to use the same resources for one or more media streams in uplink, downlink or both uplink and downlink direction.
A P-CSCF that supports resource sharing can determine that there is a potential for resource sharing based on local configuration or defer the determination of ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.16 Priority sharing | Priority sharing allows two or more sessions with different priority to share the same bearer.
The determination of the use of priority sharing is deferred to an AS in the home network:
1) if P-CSCF supports priority sharing and if according to local policy, the P-CSCF indicate that priority sharing is supported by inc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 4.17 3GPP PS data off | The UE and the network can support the 3GPP PS data off.
When 3GPP PS data off is supported and active, IP packets that are associated with services that are not a 3GPP PS data off exempt service are prevented from transport over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN as specified in 3GPP TS 23.228 [7]. The UE may be c... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.