hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4 Support of standalone IMS data channel session
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.0 General
| If the IMS AS received from the originating network:
- an initial INVITE request with the SDP offer containing only data channel media description;
- a re-INVITE request with the SDP offer in which the audio and video media is removed (i.e. the port number of the audio/video media set to 0);
the IMS AS shall determ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.1 Void
| 9.3.3.2.4.1A Subsequent standalone bootstrap data channel and application data channel establishment
Upon receipt of the initial INVITE request from the originating network towards a terminating UE with the SDP offer which only includes bootstrap data channels and the 183 (Session Progress) response to the INVITE requ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.2 Void
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.3 Combined standalone bootstrap data channel and application data channel establishment
| Upon receipt of the initial INVITE request from the originating network to a terminating UE with SDP offer which includes the media description for both bootstrap data channel and application data channel and the 183 (Session Progress) response to the initial INVITE request from the terminating UE, the IMS AS shall fol... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.5 Enforcement of 3GPP PS data off
| If "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services, upon receipt of a third-party REGISTER request containing a "+g.3gpp.ps-data-off" Contact header field parameter indicating the 3GPP PS data off status of the UE, in addition to the procedure in 3GPP TS 24.229 [9] clause 5.7.1.2... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6 Handling of data channel multiplexing
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6.1 General
| When the IMS AS receives from the originating network an initial INVITE with the SDP offer containing only the multiplexed data channel media description(s), if the data channel multiplexing is not supported by the terminating network, the IMS AS shall return 488 (Not Acceptable Here) response containing an SDP message... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6.2 Bootstrap data channel multiplexing
| When the IMS AS receives from the originating network an initial INVITE, a re-INVITE or an UPDATE request with an SDP offer that contains a multiplexed bootstrap media description from the originating network, if the data channel multiplexing is supported by the terminating network and the served UE, the IMS AS shall s... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6.3 Application data channel multiplexing
| When the IMS AS receives from the originating network an initial INVITE, re-INVITE or UPDATE request with an SDP offer that contains a multiplexed application data channel media description, if the data channel multiplexing is supported and it determines the terminating UE:
- supports the data channel multiplexing, t... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.7 Support of data channel interworking between a non-DC capable originating UE and a DC capable terminating UE
| Upon receipt of an initial INVITE request with an SDP offer containing the audio and video media description from the originating network, if the interworking required event subscribed and the IMS AS determines that the originating UE is a non-DC capable UE as the Contact header field does not include the media feature... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4 Abnormal cases
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.1 General
| Abnormal cases on IMS data channel include the following:
- The IMS AS has sent a data channel resource reservation/update request and does not receive a response to that request.
- The IMS AS has sent a data channel resource reservation/update request, and receives an error response to that request due to no suffic... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.2 No response on DC2 interface
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.2.1 Actions at the IMS AS
| If the IMS AS does not receive a response to a bootstrap data channel resource reservation/update request, the IMS AS shall:
- remove the data channel media description from the SDP offer for the INVITE/re-INVITE request; and
- set the port number of the "m=" lines for data channel as zero in the SDP answer of the re... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.3 Insufficient data channel resource
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.3.1 Actions at the IMS AS
| If the IMS AS receives an error response message to a bootstrap data channel resource reservation/update request, the IMS AS shall:
- remove the data channel media description from the SDP offer for the INVITE/re-INVITE request;
- continue the ongoing session procedure; and
- set the port number of the "m=" lines fo... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.4 No response or failure response on DC1 interface
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.4.1 Actions at the IMS AS
| If the IMS AS does not receive a response to a session event notification or receives a failure response to a session event notification, the IMS AS shall:
- in the case of notifying IMS data channel session establishment request or media change request on bootstrap data channel setup, remove the IMS data channel SDP ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.5 QoS parameters not received.
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.5.1 Actions at the IMS AS
| If new SDP offer generated by the UE includes the application data channel media description containing "a=3gpp-req-app" attribute with "endpoint" parameter set to "server" and:
- "a=3gpp-qos-hint" attribute but no QoS parameters received in the media instruction from the DCSF, the IMS AS of the served UE shall genera... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.6 Re-INVITE request collision
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.6.1 Actions at the IMS AS
| The IMS AS shall handle re-INVITE request collisions as specified in 3GPP TS 24.229 [9] with the clarification in this subclause.
When a re-INVITE request including an SDP offer containing IMS data channel media description is received while a re-INVITE is progressing as per 9.3.2.2.2 and 9.3.3.2.2, or while a re-INVI... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10 Interaction with supplementary services
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.1 Originating Identification Presentation (OIP)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.2 Terminating Identification Presentation (TIP)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.3 Originating Identification Restriction (OIR)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.4 Terminating Identification Restriction (TIR)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.5 Message Waiting Indication (MWI)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.6 Conferencing (CONF)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.6.1 Procedure at UE
| When a user is participating in two or more SIP sessions, established SIP session's data channel media streams are specific to each SIP session. The user is handling multiple SIP sessions, but only one SIP session shall be active at a time.
The user (conference creator) creates SIP session with the conference focus by... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.6.2 Procedure at IMS AS serving the user
| On reception of the SIP INVITE request in conjunction with IMS data channel setup as per clause 9.3.2.1.2 and request URI set to the conference factory URI in accordance with clause 5.3.1.3 3GPP TS 24.147 [15], the IMS AS serving the user shall follow procedure specified in clause 9.3.2.2.1.
NOTE 1: The served user ca... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7 Communication Diversion (CDIV)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.1 Communication Forwarding Unconditional (CFU)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.1.1 Actions at the AS of the diverting User
| On reception of incoming session setup INVITE request in the IMS AS of the diverting user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.2 Communication Forwarding on Busy user (CFB)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.2.1 Actions at the AS of the diverting User
| On reception of incoming session setup INVITE request in the IMS AS of the diverting user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.3 Communication Deflection (CD)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.3.1 Actions at the AS of the diverting User
| The CD service can only be triggered before the 200 OK SIP response reception from the diverting user as defined in 3GPP TS 24.604 [16].
On reception of 302(Moved Temporarily) SIP response at IMS AS, the IMS AS:
- shall notify the establishment failure event and trigger the release of the established data channel med... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.4 Communication Forwarding on No Reply (CFNR)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.4.1 Actions at the AS of the diverting User
| The CFNR service no-reply timer at IMS AS shall be started at the reception of 180 (Ringing) SIP response reception. On no-reply timer expiry, the IMS AS:
- shall notify the establishment failure event and send a CANCEL or BYE request to the diverting UE as per procedures defined in clause 4.5.2.6.3 of 3GPP TS 24.604 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.4.2 Actions at the AS of the originating User
| Upon receiving an SDP offer included in an UPDATE request containing data channel media description to update the BDC between the originating network and the diverted-to user, and the BDC between the originating user and the diverted-to network, the IMS AS shall:
1) notify the DCSF about media change event;
2) reques... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.5 Communication Forwarding on Not Reachable (CFNRc)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.5.1 Actions at the AS of the diverting User
| There’s no data channel media session setup between the originating and the diverting user’s network, hence the CFNRc behavior shall be same as CFU service in clause 10.7.1.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.6 Communication Forwarding on Not Logged-in (CFNL)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.6.1 Actions at the AS of the diverting User
| When the AS of the diverting user receives an incoming session setup INVITE request for an unregistered served user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media accordin... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.8 Communication Waiting (CW)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.8.1 Actions at AS of user B
| If a network-based CW ("approaching NDUB") or terminal based CW condition is determined, after a CW service execution, the serving IMS AS will interact with the serving DCSF and the MF of the user B, to reserve the DC media resources for waiting communication, based on the served user B subscription data. The serving I... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.8.2 Actions at UE of user B
| If the user B accepts the waiting communication and holds the active communication (as per procedures in 3GPP TS 24.615 [17]), the hold invoking UE of the user B shall perform the hold procedure.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.9 Advice Of Charge (AOC)
| The Advice Of Charge (AOC) service specified in 3GPP TS 24.647 [22] shall allow the served user to be informed of IP Multimedia session related charging information even if the session is accompanying with data channel media.
According to 3GPP TS 32.260 [20] and 3GPP TS 32.255 [21], duration-based charging and volume-... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.10 Flexible Alerting (FA)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.10.1 Actions at the AS serving the pilot identity
| The flexible alerting telecommunication service with IMS data channel, procedures for the IMS AS serving user B identified by the FA pilot identity, shall be in accordance with 3GPP TS 24.239 [23] with the additions defined in the present document.
Upon reception of an incoming SIP INVITE request with DC media destine... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11 Multi-Device (MuD)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11.1 Actions at the AS serving user B
| The multi-device service with IMS data channel, procedures for the IMS AS serving the user B having federated UEs, shall be in accordance with 3GPP TS 24.174 [24] with the additions defined in the present document.
On reception of a SIP initial INVITE request with an SDP offer containing IMS data channel media descrip... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11.2 Call pull, actions at the AS serving user A
| On reception of an INVITE request from the UE of the user A who has triggered the call pull request, to establish new partial dialog with the IMS AS of the user A in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.3:
1) the IMS AS shall update existing partial dialog towards the remote network in accordance with 3G... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11.3 Call push, actions at the AS serving user A
| On reception of a SIP REFER request for call push request from the UE of the user A involved in ongoing call:
1) the IMS AS shall establish new partial dialog with the target UE of the user A in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.4 and 3GPP TS 24.628 [28] clause 4.4.a;
2) the IMS AS shall update exist... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.12 Multi-iDentity (MiD)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13 Completion of Communications to Busy Subscriber (CCBS), Completion of Communications by No Reply (CCNR) and Completion of Communications on Not Logged-in (CCNL)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13.1 General
| The CCBS, CCNR and CCNL services enable a user, encountering a destination that is busy, does not answer or is not logged-in, to have the communication completed at a later point in time without the user having to manually initiate a new communication attempt, which is defined in 3GPP TS 24.642 [25].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13.2 Action at the UE
| When the UE initiates the initial IMS session before the CC services activation, the IMS data channel media description can be included in the INVITE along with other MMTel medias. The procedure defined in clause 9.3.2.1.2 applies.
On reception of the 486 (Busy Here) in case of CCBS or the 480 (Temporarily Unavailable... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13.3 Action at the IMS AS serving the originating UE
| Upon reception of the incoming sessions setup INVITE request in the IMS AS serving the originating UE with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.1... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.14 Enhanced Calling Name (eCNAM)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.15 Closed User Group (CUG)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.16 Communication Barring (CB)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17 Customized Ringing Signal (CRS)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17.1 General
| The CRS service is an operator specific service specified in 3GPP TS 24.183 [26], which describes three models of CRS service:
- Download and play model: it has no interaction with IMS data channel.
- Gateway model: it has no impact to IMS data channel.
- Early session model: it has no impact to IMS data channel.
... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17.2 Actions on the originating UE
| When the originating UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and the DC_Setup_Option leaf indicates that the IMS data channel is to be setup simultaneously while establishing an IMS session, the data channel media can be negotiated in the initial INVITE request and its correspon... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17.3 Actions on the CRS AS
| Upon receiving the SIP requests and responses containing data channel SDP media descriptions, the CRS AS shall ignore them and just transmit them transparently.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18 Customized Alerting Tones (CAT)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18.1 General
| The CAT service is an operator specific service specified in 3GPP TS 24.182 [27], which describes three models of CAT service as follows:
- forking model: it has no impact to IMS data channel.
- gateway model: it has no impact to IMS data channel.
- early session model: it has no impact to IMS data channel.
As spec... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18.2 Actions at the originating UE
| When the originating UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and the DC_Setup_Option leaf indicates that the IMS data channel is to be setup simultaneously while establishing an IMS session, the data channel media can be negotiated in the initial INVITE request and its correspon... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18.3 Actions at the CAT AS
| Upon receiving the SIP requests and responses containing data channel SDP media descriptions, the CAT AS shall ignore them and just transmit them transparently.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19 Explicit Communication Transfer (ECT)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.1 General
| The explicit communication transfer (ECT) service provides a party involved in a communication to transfer that communication to a third party as defined in 3GPP TS 24.629 [12].
There are three actors active in a transfer, they are acting in the following roles:
transferor: the party that initiates the transfer of th... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.2 Actions at the AS serving the transferor
| On reception of REFER message, if ECT has been triggered as defined in 3GPP TS 24.629 [12], the IMS AS serving the transferor:
- shall trigger the closing of all the established data channels on the transferor’s network (including the data channel between the transferor’s network and the transferor, the data channel b... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.3 Actions at the AS serving the transferee
| If the transferee's network has established data channel media with the transferor before the transfer happens, the transferee's network shall release the data channel between transferor and transferee’s network. After establishment of an IMS session towards the transfer target data channels may be established towards ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.4 Actions at the AS serving the transfer target
| In case of blind transfer, if the transfer target's network provides data channel service, on reception of incoming INVITE request from transferor’s network, the transfer target's network shall send the INVITE message to transfer target. On reception of the 18x response or 200 (OK) response on the INVITE message from t... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20 Communication Hold (HOLD)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.1 Actions at the invoking UE
| If the UE want to put some media stream on hold, then in addition to the application of procedures according to 3GPP TS 24.610 [32], the following procedures shall be applied at the invoking UE.
The invoking UE shall include in the generated SDP offer as specified in 3GPP TS 26.114 [4]:
1) for each data channel media... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.2 Actions at the AS serving the invoking UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.2.1 General
| In addition to the application of procedures according to 3GPP TS 24.610 [32], the following procedures shall be applied at the AS serving the invoking UE.
NOTE: The AS serving the invoking UE can be the AS in the originating IMS network and/or the terminating IMS network, depending on by which network the media to be... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.2.2 Event report
| On reception of the SIP re-INVITE request with the SDP offer that contains an "a=inactive" SDP direction attribute in data channel media description and data channel media was previously active, the AS shall notify the DCSF that data channel media is to be suspended as specified in 3GPP TS 29.175 [18].
On reception of... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.3 Actions at the held UE
| In addition to the application of procedures according to 3GPP TS 24.610 [32], the held UE shall generate an SDP answer for the held data channel media as specified as 3GPP TS 26.114 [4].
Annex A (informative):
Signalling flows
This annex provides the signalling flows related to clause10.
A.1 Interaction with suppl... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 1 Scope | The present document identifies the requirements for operation of Uncrewed Aerial Vehicles (UAVs) via the 3GPP system.
This includes requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 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... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3 Definitions, symbols and abbreviations | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Above ground level (AGL): In the context of a UAV it is the UAV altitude r... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
BVLOS Beyond Visual Line of Sight
C2 Command and Control
Remote I... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4 Overview on UAS | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4.1 General | An Uncrewed Aerial System (UAS) is the combination of an Uncrewed Aerial Vehicle (UAV), sometimes called a drone, and a UAV controller. A UAV is an aircraft without a human pilot onboard – instead, in some cases. the UAV can be controlled from an operator via a UAV controller and will have a range of autonomous flight ... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4.2 C2 Communication | When using 3GPP network as the transport network for supporting UAS services, the following C2 communication are considered to provision UAS services by guaranteeing QoS for the C2 communication:
Direct C2 communication: the UAV controller and UAV establish a direct C2 link to communicate with each other and both are r... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5 Requirements for Remote Identification of UAS | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.1 General | [R-5.1-001] The 3GPP system should enable UTM to associate the UAV and UAV controller, and the UTM to identify them as a UAS.
[R-5.1-002] The 3GPP system shall be able to provide UTM with the identity/identities of a UAS.
[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique ... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2 UAS traffic management | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2.1 General | NOTE: The following requirements are valid for both centralized and decentralized UTM.
[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with flight clearance, to a UAV.
[R-5.2.1-002] The 3GPP system shall be able to deliver route modification information received from a UTM... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2.2 Decentralized UAS traffic management | [R-5.2.2-001] The 3GPP system shall enable a UAV to broadcast the following data for identifying UAV(s) in a short-range area for collision avoidance: e.g. UAV identities if needed based on different regulation requirements, UAV type, current location and time, flight route information, current speed, operating status.... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.3 Void | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.4 Security | [R-5.4-001] The 3GPP system shall protect the transport of data between the UAS and UTM.
[R-5.4-002] The 3GPP system shall protect against spoofing attacks of the UAS identities.
[R-5.4-003] Void.
[R-5.4-004] Void.
[R-5.4-005] The 3GPP system shall support confidentiality protection of identities related to the UAS and... |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6 Requirements for UAV usages |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.