hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6 Monitoring Event configuration and deletion via HSS for roaming scenarios using an IWK-SCEF
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.1 Configuration Procedure
| Figure 5.6.6.1-1 illustrates the procedure of configuring monitoring events at the HSS or the MME/SGSN. The procedure is common for various Monitoring Event types. The steps and parameters specific to different Monitoring Event types are detailed in clauses 5.6.6.3 to 5.6.6.9.
The procedure is also used for deleting a... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.2 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.3 Specific Parameters for Monitoring Event: Loss of connectivity
| The description in clause 5.6.1.3 applies with the following clarifications.
1-5. Steps 1-5 of clause 5.6.1.3 are executed.
6. The MME/SGSN executes step 6 of clause 5.6.1.3, but if the values proposed by HSS is not acceptable to the MME/SGSN the MME/SGSN rejects the request and includes acceptable values in the reje... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.4 Specific Parameters for Monitoring Event: UE reachability
| The description in clause 5.6.1.4 applies with the following clarifications.
1-5. Steps 1-5 of clause 5.6.1.4 are executed.
6. The MME/SGSN executes step 6 of clause 5.6.1.4, but if the values proposed by HSS is not acceptable to the MME/SGSN the MME/SGSN rejects the request and includes acceptable values in the reje... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.5 Specific Parameters for Monitoring Event: Location Reporting
| The description in clause 5.6.1.5 applies with the following clarifications.
1-2. Steps 1-2 of clause 5.6.1.5 are executed.
3. If Accuracy is included in step 1 then based on operator configuration the SCEF may map it to permissible granularity at different levels, which are described in clause 4.9.2. If Accuracy is ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.6 Specific Parameters for Monitoring Event: Change of IMSI-IMEI(SV) Association
| The description in clause 5.6.1.6 applies as there are no VPLMN changes.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.7 Specific Parameters for Monitoring Event: Roaming Status
| The description in clause 5.6.1.6 applies as there are no VPLMN changes.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.8 Specific Parameters for Monitoring Event: Communication failure
| The description in clause 5.6.1.8 applies with the following clarifications.
1. The SCS/AS sets Monitoring Type to "Communication Failure" prior to sending Monitoring Request to the SCEF as in step 1 of clause 5.6.1.8.
2. The SCEF executes step 2 of clause 5.6.1.8.
3. The SCEF executes step 3 of clause 5.6.1.8.
4. ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.6.9 Specific Parameters for Monitoring Event: Availability after DDN Failure
| The description in clause 5.6.1.5 applies with the following clarifications.
1-5. Steps 1-5 are executed according to clause 5.6.6.9.
6. Not applicable.
7. If the MME/SGSN is configured to use an IWK-SCEF for the PLMN of the SCEF, the MME/SGSN executes step 7 of 5.6.6.1.
8. The IWK-SCEF executes step 8 of clause 5.... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.7 Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios
| In this Release there is no support for Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8 Reporting of Monitoring Events from the HSS or the MME/SGSN for roaming scenarios
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.1 Reporting Procedure
| The following figure illustrates the common procedure flow of reporting Monitoring Events that are detected by the MME/SGSN or HSS for roaming scenarios. The steps specific to different Monitoring Event types are detailed in clauses 5.6.8.2 to 5.6.8.8.
Figure 5.6.8.1-1: Monitoring event reporting procedure for roami... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.2 Reporting Event: Loss of connectivity
| 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the mobile reachability timer expires, when an active UE is purged (see TS 29.272 [31]), when ISR is disabled and a UE, MME, SGSN, or HSS initiated detach occurs (see TS 23.401 [7], TS 23.060 [6]), or when ISR is enabled and a UE, MME,... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.3 Reporting Event: UE reachability
| 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the UE changes to connected mode or when the UE will become reachable for paging (for a UE using extended idle mode DRX).
If Maximum Response Time was included in step 5 of clause 5.6.6.4, then the MME/SGSN keeps the corresponding S1... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.4 Reporting Event: Location Reporting
| 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the MME/SGSN detects that the UE changes location with the granularity as requested by the monitoring event configuration.
2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. If step 2c is executed, the... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.5 Reporting Event: Change of IMSI-IMEI(SV) association
| This monitoring event is executes as in clause 5.6.3.5.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.6 Reporting Event: Roaming Status
| This monitoring event is executes as in clause 5.6.3.6.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.7 Reporting Event: Communication failure
| 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the MME/SGSN becomes aware of a RAN or NAS failure event.
2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed. If step 2c is executed, then the IWK-SCEF either forwards the received failure cause code(s)... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.8 Reporting Event: Availability after DDN failure
| 1a. This monitoring event is detected as of step 1a of clause 5.6.8.1, which is when the MME/SGSN becomes aware of UE availability after DDN failure.
2. Dependent on MME/SGSN configuration step 2a or 2c of clause 5.6.8.1 is executed.
3. Step 3 of clause 5.6.8.1 is executed.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.8.9 Reporting Event: PDN Connectivity Status
| This monitoring event executes as in clause 5.6.3.9.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.6.9 Network-initiated Explicit Monitoring Event Deletion Procedure
| The procedure is used by the SCEF towards the SCS/AS to delete a previously configured Monitoring Event.
Figure 6.5.9-1: Network-initiated Explicit Monitoring Event Deletion Procedure
0. A Monitoring Event configuration procedure according to clause 5.6.1 or clause 5.6.6 has already executed successfully.
1. The H... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.7 High latency communications procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.7.1 Availability Notification after DDN Failure
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.7.1.1 General
| In this feature, the AS subscribes once and then gets notification only when there has been some data delivery failure followed by the UE becoming reachable.
This feature involves an entry in the subscription for a UE for "network application triggering when the UE is available after a DDN failure". This is a differen... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.7.1.2 Event Configuration
| The figure 5.7.1.2-1 below provides the Event configuration procedure.
Figure 5.7.1.2-1: Event Configuration - Availability Notification after DDN Failure
1. The SCS/AS executes step 1 of clause 5.6.1.9.
2. The SCEF sends a Monitoring Request message to the HSS to request notification when the UE becomes available... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.7.1.3 Notification
| The figure 5.7.1.3-1 below provides the notification procedure. This figure is relative to EUTRAN, but the equivalent figure for UTRAN can be directly derived from this.
Figure 5.7.1.3-1: Notification - Availability Notification after DDN Failure
1. The application sends downlink data.
2. The PGW forwards the data... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.7.2 Notification using Monitoring Event "UE Reachability"
| If an SCS/AS wants to send downlink packet(s), the SCS/AS can request a One-time "UE Reachability" monitoring event by sending Monitoring Request message indicating Reachability Type as "Reachability for Data". The SCS/AS may send the packet data when it receives a notification that the UE has changed to connected mode... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.8 Procedure for Informing about Potential Network Issues
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.8.1 General
| This clause contains the detailed description and the procedures for the service capability exposure feature Informing about Potential Network Issues.
An SCS/AS may request for being notified about the network status. The following methods are supported:
- The SCS/AS requests to be informed, one-time, about the netwo... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.8.2 Request procedure for one-time or continuous reporting of network status
| This procedure is used by an SCS/AS to retrieve Network Status Information (NSI) from the network. This procedure can be used to request a one-time or continuous reporting of network status. Figure 5.8.2-1 illustrates the procedure.
Figure 5.8.2-1: Request procedure for one-time or continuous reporting of network st... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.8.3 Report procedure for continuous reporting of network status
| This procedure is used by the SCEF to report a change of Network Status Information (NSI) to the SCS/AS which requested a continuous reporting of network status. Figure 5.8.3-1 illustrates the procedure.
Figure 5.8.3-1: Report procedure for continuous reporting of network status
1. The RCAF detects a change in the ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.8.4 Removal procedure for continuous reporting of network status
| This procedure is used for termination of the continuous reporting of network status. It can be triggered by the SCS/AS at any time before the Duration is over or if no Duration was provided. The SCEF will trigger this procedure when the Duration is over. Figure 5.8.4-1 illustrates the procedure.
Figure 5.8.4-1: Rem... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.9 Procedure for resource management of background data transfer
| This clause describes the procedure for resource management of background data transfer to a set of UEs, i.e. an SCS/AS requesting a time window and related conditions from the SCEF via the Nt interface.
The UEs targeted for background data transfer may be served by a single PCRF or may be spread across multiple PCRFs... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.10 Communication Pattern parameters provisioning procedure
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.10.1 Communication Pattern parameters
| A set of Communication Pattern (CP) parameters is defined in the table below. All CP parameters are optional.
These CP parameters are specific for a UE or a group of UEs. Sets of these CP parameters are provided by the SCEF to the HSS which distributes them to the corresponding MME with relevant subscriber data. These... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.10.2 Communication Pattern parameters provisioning to the MME
|
Figure 5.10.2-1: Signalling sequence for provisioning of CP Parameters
1. The SCS/AS sends an Update Request (External Identifier or MSISDN or External Group Identifier, SCS/AS Identifier, CP parameter Set Id(s), CP parameter set(s), validity time(s), CP parameter Set Id(s) for Deletion, MTC Provider Information) me... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.11 Setting up an AS session with required QoS procedure
| This clause describes the signalling flow for setting up a 3rd party AS session with a specific QoS.
Figure 5.11-1: Setting up an AS session with required QoS
1. When setting up the connection between SCS/AS and the UE with required QoS for the service, the SCS/AS sends an On-demand QoS request message (UE IP addre... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.12 Change the chargeable party at session set-up or during the session procedure
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.12.1 Set the chargeable party at session set-up
| This clause describes the signalling flow for setting the chargeable party at AS session set-up. The SCS/AS may either request to sponsor the traffic from the beginning or may request to become the chargeable party at a later point in time.
Figure 5.12.1-1: Set the chargeable party at AS session set-up
1. When sett... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.12.2 Change the chargeable party during the session
| This clause describes the signalling flow for changing the chargeable party during an ongoing AS session, i.e. the SCS/AS starting or stopping to sponsor the application traffic.
Figure 5.12.2-1: Change chargeable party during an AS session
1. For the ongoing AS session, the SCS/AS may send a Change chargeable part... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13 Non-IP Data Delivery procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.1 T6a/T6b Connection Establishment
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.1.1 General
| When the UE performs the EPS attach procedure (see TS 23.401 [7]) with PDN type of "Non-IP", and the subscription information corresponding to either the default APN for PDN type of "Non-IP" or the UE requested APN includes the "Invoke SCEF Selection" indicator, then the MME initiates a T6a/T6b connection towards the S... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.1.2 T6a/T6b Connection Establishment Procedure
|
Figure 5.13.1.2-1: T6a/T6b Connection Establishment Procedure
1. UE performs steps 1-11 of the E-UTRAN Initial Attach procedure or step 1 of the UE requested PDN Connectivity procedure (see TS 23.401 [7]) or PDP Context Activation Procedure (see TS 23.060 [6]). The MME/SGSN receives subscription information for a no... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.2 NIDD Configuration
| Figure 5.13.2-1 illustrates the procedure of configuring necessary information at the SCEF and HSS. A NIDD Configuration is associated with a single UE or a group of UEs. The procedure can also be used for replacing and deleting configuration information.
NOTE 1: In order to avoid MO NIDD failure, the NIDD configurati... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.3 Mobile Terminated NIDD procedure
| Figure 5.13.3-1 illustrates the procedure using which the SCS/AS sends non-IP data to a given user as identified via External Identifier or MSISDN. This procedure assumes that procedures in clause 5.13.1 is completed.
Figure 5.13.3-1: Mobile Terminated NIDD procedure
1. If SCS/AS has already activated the NIDD serv... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.4 Mobile Originated NIDD procedure
|
Figure 5.13.4-1: Mobile Originated NIDD procedure
1. The UE sends a NAS message with EPS bearer ID and non-IP data, the Reliable Data Service header is included if the Reliable data service is enabled, to the MME as per the procedure described in clause 5.3.4B.2 of TS 23.401 [7] (steps 0 - 2) or the UE sends data to... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.5 T6a/T6b Connection Release
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.5.1 General
| The MME releases the T6a connection(s) towards the SCEF(s) corresponding to the "SCEF ID" indicator for that APN in the following cases:
- UE-initiated Detach procedure for E-UTRAN, or
- MME-initiated Detach procedure, or
- the HSS-initiated Detach procedure, or
- UE or MME requested PDN disconnection procedure.
T... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.5.2 MME/SGSN Initiated T6a/T6b Connection Release procedure
|
Figure 5.13.5.2-1: MME/SGSN Initiated T6a/T6b Connection Release procedure
1. The UE performs step 1 of the UE-initiated Detach procedure for E-UTRAN (see clause 5.3.8.2.1 TS 23.401 [7]), or the MME performs the MME-initiated Detach procedure (see clause 5.3.8.3 of TS 23.401 [7]), or the HSS performs step 1a of the ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.5.3 SCEF Initiated T6a/T6b Connection Release procedure
|
Figure 5.13.5.3-1: SCEF Initiated T6a/T6b Connection Release procedure
1. An NIDD Authorization Update request from the HSS indicates that the User is no longer authorized for NIDD, the SCS/AS indicates that the User's NIDD PDN connection is no longer needed, or the SCEF determines that it is needs to release a T6a/... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.6 Serving node relocation procedure over T6a/T6b
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.6.1 General
| Mobility may happen with respect to a non-IP PDN connection via the SCEF as a result of a TAU/RAU procedure. The following procedures apply:
- Successful TAU/RAU on a new MME/SGSN,
- Failed TAU/RAU.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.6.2 Successful TAU/RAU procedure with T6a/T6b
| The procedure in Figure 5.13.6.2-1 applies when a T6a/T6b PDN/PDP connection exists for a UE that executes a successful TAU procedure to a new MME or a successful RAU procedure to a new SGSN.
Figure 5.13.6.2-1: T6a/T6b and successful TAU/RAU procedure
1. UE performs a successful TAU/RAU procedure (see TS 23.401 [7]... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.7 Void
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.13.8 NIDD Authorisation Update
| Figure 5.13.8-1 illustrates the procedure of updating or revoking an existing NIDD Authorisation. The HSS may initiate the NIDD Authorisation Update procedure with the SCEF to send updated Authorisation information to the SCEF.
Figure 5.13.8-1: NIDD Authorisation Update procedure
1. The HSS may send an NIDD Authori... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.14 PFD management via SCEF
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.14.1 Procedure for PFD management via SCEF
| This procedure is used by the 3rd Party SCS/AS to manage PFDs into the operator network via SCEF. Figure 5.14.1-1 illustrates the procedure.
Figure 5.14.1-1: procedure for PFD management via SCEF
1. The 3rd party SCS/AS sends a PFD Management Request (SCS/AS Identifier, external Application Identifier(s) and one or... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.14.2 PFD definition
| PFD (Packet Flow Description) is a set of information enabling the detection of application traffic including:
- PFD id; and
- one or more of the following:
- 3-tuple(s) including protocol, server side IP address and port number;
- the significant parts of the URL to be matched, e.g. host name;
- a Domain name mat... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.15 Procedure for MSISDN-less MO-SMS via T4
|
Figure 5.15-1: MSISDN-less MO-SMS via T4
1. UE uses Short Message Mobile Originated procedure as specified in TS 23.040 [12] to delivery small data to SCS/AS. The service centre address points to the SMS-SC which contain the function described in this procedure, the destination SME address is set to short/long code ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.16 Procedure for Enhanced Coverage Restriction Control via SCEF
| Figure 5.16-1 shows the procedures for Enhanced Coverage Restriction Control via SCEF.
Figure 5.16-1: Procedure for Enhanced Coverage Restriction Control via SCEF
1. The SCS/AS sends an Enhanced Coverage Request (External Identifier or MSISDN, SCS/AS Identifier, Request Type, Enhanced Coverage Restriction Data, MTC... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.17 Procedures for accessing MTC-IWF Functionality via SCEF
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.17.1 Device triggering procedure via T8
| Figure 5.17.1-1 shows the procedure for Triggering via T8.
Figure 5.17.1-1: Device triggering procedure via T8
1. The SCS/AS determines the need to trigger the device. If the SCS/AS has no contact details for the SCEF, it may determine the IP address(es)/port(s) of the SCEF by performing a DNS query using the Exter... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.17.2 Device triggering recall/replace procedures via T8
| Figure 5.17.2-1 shows the procedures for recalling and replacing triggers over T8.
Figure 5.17.2-1: Procedure for triggering recall/replace via T8
1. The SCS/AS determines that it needs to recall/replace a trigger message that it has previously submitted. The SCS/AS sends Trigger Modify Request (SCS Identifier, TLT... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.17.3 Procedure for MSISDN-less MO-SMS via T8
| Figure 5.17.3-1 shows the procedures for MSISDN-less MO-SMS via T8.
Figure 5.17.3-1: Procedure for MSISDN-less MO-SMS via T8
1. The UE sends an SMS to the SCS/AS. The UE, MSC/MME/SGSN, and SMS-SC execute steps 1 and 2 of the MSISDN-less MO-SMS via T4 procedure of clause 5.15. SMS-SC uses the destination SME address... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.18 Procedure for Network Parameter Configuration via SCEF
|
Figure 5.18-1: Procedure for Network Parameter Configuration via SCEF
1. The SCS/AS sends a T8 Set Suggested Network Configuration Request (External Identifier or MSISDN or External Group Identifier, SCS/AS Identifier, Maximum Latency, Maximum Response Time and Suggested Number of Downlink Packets, Group Reporting G... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.19 RACS information provisioning procedures
| |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.19.1 General
| This clause specifies procedures for provisioning of UCMF with RACS related information from SCS/AS, either via SCEF or directly. Specification of these procedures does not preclude other methods of UCMF provisioning being used, e.g. O&M.
|
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.19.2 RACS information provisioning procedures via SCEF
| This procedure is used by SCS/AS to add, update or delete UE radio access capability entries in the UCMF using the protocol specified in TS 29.122 [44] for the SCEF northbound API and the protocol defined in TS 29.675 [49] for the UCMF northbound API. Figure 5.19.2-1 illustrates the procedure.
Figure 5.19.2-1: RACS ... |
88801ef891f5fda814c6a759927a12ca | 23.682 | 5.19.3 RACS information provisioning procedures via T9a
| This procedure is used by SCS/AS to add, update or delete UE radio access capability entries in the UCMF using the protocol defined in TS 29.675 [49]. Figure 5.19.3-1 illustrates the procedure.
Figure 5.19.3-1: RACS information provisioning procedure via T9a
1. The SCS/AS sends a Radio Capability Entry Request ((li... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 1 Scope | The present document is a technical report capturing the study on application enablement for Satellite access enabled 5G Services over 3GPP networks. The aspects of the study include identifying architecture requirements, supporting architecture for satellite access enabled 3GPP services and application enablers (eithe... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 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... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 3 Definitions of terms, symbols and abbreviations | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 3.1 Terms | For the purposes of the present document, the terms 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].
example: text used to clarify abstract rules by applying them literally. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 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].
5GC 5G Core Network
5QI 5G QoS Identifier
AC Application Client
A... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4 Key issues | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.1 Key issue #1: Usage of satellite access characteristics for the application enablement | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.1.1 Description | 3GPP SA1 has specified the service requirements for 5G for satellite access in 3GPP TS 22.261[2] which including supporting 5G system with satellite access, suitable QoS parameters for traffic over a satellite backhaul, etc. And 3GPP SA2 has also specified the architecture and solutions in Rel-17 and Rel-18 to support ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.1.2 Open issues | To support the satellite access in application enablers, the following aspects need to be studied:
- What are the satellite access characteristics that can be utilized by the application enablers?
- Whether and how to use the satellite access characteristics (e.g., QoS parameters for traffic over a satellite access) to... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.2 Key issue #2: Edge computing on satellite | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.2.1 Description | UPF and Edge in the backhaul part of a 5GS (i.e. on board a GEO satellite) facilitates reduction of latency and faster service provisioning to end users. 3GPP TS 23.558 [10] (SA6) defines Architectures for enabling Edge applications including the procedures for EAS discovery. Although 3GPP TS 23.558 [10] specification ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.2.2 Open issues | Deployment of Edge computing on board GEO satellites might impact the latency of application control and data information exchange. To assess the impacts of using Edge on board GEO satellites it would be benefitial to study the following aspects with the aim to reduce latency and data exchange over satellite feeder lin... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.3 Key issue #3: Satellite access with discontinuous coverage | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.3.1 Description | In a network with satellite access, a UE may experience a situation of discontinuous coverage, due to e.g., a sparse NGSO satellite constellation deployment. An illustration of a discontinuous coverage pattern for a given UE location and a single example LEO satellite at a nominal 600 km altitude is represented in Figu... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.3.2 Open issues | To support the discontinuous satellite coverage in application enabler, the following aspects need to be studied:
- Whether and how the information on discontinuous satellite coverage needs to be exposed to the application layer (e.g. semantics, service-based interfaces, etc.) on the AS/AF side.
- Whether and how the a... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.4 Key issue #4: Satellite access support for MC services | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.4.1 Description | To ensure reliable MC services with larger coverage area, MC systems can benefit from satellite access, especially when the connectivity provided by the terrestrial networks faces limitations, e.g., bad coverage at remote areas. Hence, MC service UEs can be able to connect to MC system via satellite access to ensure se... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.4.2 Open issues | There are several aspects that need to be considered and studied to support satellite access for MC services, including but not limited to:
1. Identify the different deployment scenarios for MC services using satellite access to result in a better MC service user experience. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.5 Key issue #5: Edge on board NGSO Satellite | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.5.1 Description | NGSO satellites are satellites moving with respect to the earth surface and they can be deployed in MEO (8,000 km – 20,000 km ) or LEO (400 km – 2000 km) orbits. This will reduce the one way latency. To utilize these reduced latencies UPFs as well as gNBs can be deployed on the NGSO. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.5.2 Open issues | This key issue studies how to deploy EAS(s) and EES(s) on NGSO satellite and whether and how the corresponding discovery, service provisioning and service continuity are impacted.
- How the EES(s) are placed on board the Satellite.
- How the EAS(s) are placed on board the Satellite.
- Whether and how the discovery and... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.6 Key issue #6: Support of UE-Satellite-UE communication for IMS services via Satellite access | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.6.1 Description | It has been described in the 3GPP TS 22.261 [6] that a 5G system with satellite access shall support UE-Satellite-UE communication regardless of whether the feeder link is available or not, and 5G system also be able to support different types of UE-Satellite-UE communication (e.g. voice, messaging, broadband, unicast,... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.6.2 Open issues | From the application enabler’s perspective, the key issue will focus on how to support the IMS service via satellite access in the application enabled layer, it is proposed to study the following items:
- Investigate different deployment options for the application enabler of IMS (i.e. eMMTEL App) to utilize satellite ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.7 Key issue #7: Usage of S&F events information for the application enablement | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.7.1 Description | 3GPP SA1 has specified the service requirements for 5G for satellite access in 3GPP TS 22.261 [22.261] as following which includes supporting Store and Forward (S&F) Satellite Operation. And 3GPP SA2 is studying the exposure of S&F events information to support these services requirements identified in SA1.
- Subject t... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.7.2 Open issues | To support utilization of S&F events information by application enablers, the following aspects need to be studied:
- What are the S&F events information that can be utilized by the application enablers?
- How to use the S&F events information to optimise the application enablement behaviour?
- Whether and how the S&F ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 4.8 Key issue #8: Impact of satellite access on KPIs for Mission Critical group communications |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.