hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.2.2 Preparation phase
|
Figure 5.5.2.2.2-1: UTRAN Iu mode to E-UTRAN Inter RAT HO, preparation phase
1. The source RNC decides to initiate an Inter-RAT handover to the E-UTRAN. At this point both uplink and downlink user data is transmitted via the following: Bearers between UE and source RNC, GTP tunnel(s) between source RNC, source SGSN ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.2.3 Execution phase
|
Figure 5.5.2.2.3-1: UTRAN Iu mode to E-UTRAN Inter RAT HO, execution phase
NOTE: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 9 and 9a concern GTP based S5/S8.
The source RNC continues to receive downlink an... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.2.4 UTRAN Iu mode to E-UTRAN Inter RAT handover reject
| The Target eNodeB may reject the use of the Handover procedure if none of the requested EPS bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. The UE remains in the Source RNC/SGSN.
Figure 5.5.2.2.4-1: UTRAN... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.3 E-UTRAN to GERAN A/Gb mode Inter RAT handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.3.1 General
| The procedure is based on Packet-switched handover for GERAN A/Gb mode defined in TS 43.129 [8].
Pre-conditions:
- The UE is in ECM-CONNECTED state (E-UTRAN mode);
- The BSS must support PFM, Packet Flow Management, procedures.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.3.2 Preparation phase
|
Figure 5.5.2.3.2-1: E-UTRAN to GERAN A/Gb Inter RAT HO, preparation phase
1. The source eNodeB decides to initiate an Inter RAT Handover to the target GERAN A/Gb mode (2G) system. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and Source eNodeB, GTP tunnel(s) ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.3.3 Execution phase
|
Figure 5.5.2.3.3-1: E-UTRAN to GERAN A/Gb mode Inter RAT HO, execution phase
NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 10 and 10a concern GTP based S5/S8
The source eNodeB continues to receive dow... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.3.4 E-UTRAN to GERAN A/Gb mode Inter RAT handover reject
| The Target BSS may reject the use of the Handover procedure if none of the requested PFCs in the PS Handover Request message could be established. In this case no UE context is established in the target SGSN/BSS and no resources are allocated. The UE remains in the Source eNodeB/MME.
Figure 5.5.2.3.4-1: E-UTRAN to G... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.4.1 General
| The procedure is based on Packet-switched handover for GERAN A/Gb mode, defined in TS 43.129 [8].
Pre-conditions:
- The UE is in READY state (GERAN A/Gb mode);
- The UE has at least one PDP/EPS Bearer Context established;
- The BSS must support PFM, Packet Flow Management, procedures.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.4.2 Preparation phase
|
Figure 5.5.2.4.2-1: GERAN A/Gb mode to E-UTRAN inter RAT HO, preparation phase
1. The source access system, Source BSS, decides to initiate an Inter-RAT Handover to the E-UTRAN. At this point both uplink and downlink user data is transmitted via the following: Bearers between UE and Source BSS, BSSGP PFC tunnel(s) b... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.4.3 Execution phase
|
Figure 5.5.2.4.3-1: GERAN A/Gb mode to E-UTRAN Inter RAT HO, execution phase
NOTE: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 9 and 9a concern GTP based S5/S8.
The source SGSN continues to receive downlink and uplink user plane PDUs.
When source SGSN receives the Forward Reloca... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.4.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover reject
| The Target eNodeB may reject the use of the Handover procedure if none of the requested EPS bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. The UE remains in the Source BSS/SGSN.
Figure 5.5.2.4.4-1: GERAN... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.5 Inter RAT handover Cancel
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.5.1 General
| Instead of completing the handover procedure, the source RAN node (eNodeB, RNC or BSS) may at any time during the handover procedure, up to the time when a handover command message is sent to the UE cancel the handover. The reason for cancelling may be e.g. due to a timer expiration or due to other events within the so... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.5.2 Source RAN to Target RAN Inter RAT handover Cancel
|
Figure 5.5.2.5.2-1: Inter RAT handover Cancel
1. The source RAN decides to cancel the previously requested relocation of Handover resources. This may be due to not enough accepted bearers, UE returned to source cell or any other reason.
2. The source RAN sends a Cancel message with a Cause to the source EPC node (S... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.6 Network Assisted Cell Change
| Network Assisted Cell Change (NACC) is a means that enables better performance for packet data services upon inter-cell change for those networks that do not support PS Handover. It reduces the service interruption time for UEs in active mode upon cell change by providing in the source cell, prior to the cell change, s... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.6.1 Architecture Principles for E-UTRAN to GERAN NACC
| Introducing NACC from E‑UTRAN to GERAN follows the principles of the Network Assisted Cell Change between UTRAN and GERAN as described in TS 25.413 [22] and TS 23.060 [7]. It specifies the RAN Information Management (RIM) procedures as specified in clause 5.15 and depicted in figure 5.6‑1.
Figure 5.6-1: E-UTRAN to G... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.6.2 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7 Information storage
| This clause describes information storage structures required for the EPS when 3GPP access only is deployed. Information storage for the case where non 3GPP accesses are deployed is in TS 23.402 [2].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.1 HSS
| IMSI is the prime key to the data stored in the HSS. The data held in the HSS is defined in Table 5.7.1-1 here below.
The table below is applicable to E‑UTRAN in stand-alone operation only.
Table 5.7.1-1: HSS data
Field
Description
IMSI
IMSI is the main reference key.
MSISDN
The basic MSISDN of the UE (Presence... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.2 MME
| The MME maintains MM context and EPS bearer context information for UEs in the ECM-IDLE, ECM‑CONNECTED and EMM-DEREGISTERED states. Table 5.7.2-1 shows the context fields for one UE.
Table 5.7.2-1: MME MM and EPS bearer Contexts
Field
Description
IMSI
IMSI (International Mobile Subscriber Identity) is the subscrib... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.3 Serving GW
| The Serving GW maintains the following EPS bearer context information for UEs. Table 5.7.3-1 shows the context fields for one UE.
For emergency attached or RLOS attached UEs which are not authenticated, IMEI is stored in context.
Table 5.7.3-1: S‑GW EPS bearer context
Field
Description
E-UTRAN
UTRAN/
GERAN
IMSI... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.4 PDN GW
| The PDN GW maintains the following EPS bearer context information for UEs. Table 5.7.4-1 shows the context fields for one UE.
For emergency attached or RLOS attached UEs which are not authenticated, IMEI is stored in context.
Table 5.7.4-1: P‑GW context
Field
Description
E-UTRAN
UTRAN/
GERAN
IMSI
IMSI (Interna... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.5 UE
| The UE maintains the following context information. Table 5.7.5-1 shows the context fields. A GERAN or UTRAN capable UE maintains in addition the context information as described in a similar UE context table in TS 23.060 [7].
Table 5.7.5-1: UE context
Field
Description
IMSI
IMSI (International Mobile Subscriber I... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.6 Handling of Wild Card APN
| When the wild card APN is present in the subscription context, the UE is authorized to connect to APNs which are not present in the subscription context.
When a request is received for registering a PDN GW ID and there is no PDN subscription context with this APN, the nodes (HSS/MME/ S4 SGSN) shall store the PDN GW ID... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.7.7 CSS
| Please refer to TS 23.008 [28] for the content of the information storage for the CSS.
5.7A Charging
5.7A.1 General
Accounting functionality is provided by the Serving GW and the PDN GW. When a Secondary RAT may be used, the Serving GW and PDN GW can be assisted by the E-UTRAN (see clause 5.7A.4).
The Serving GW sh... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.8 MBMS
| MBMS is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients. Transmitting the same data to multiple recipients allows network resources to be shared.
Support of MBMS for EPS is defined in TS 23.246 [13].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.9 Interactions with other services
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.9.1 Location Reporting Procedure
| This procedure is used by an MME to request the eNodeB to report where the UE is currently located when the target UE is in ECM-CONNECTED state. The need for the eNodeB to continue reporting ceases when the UE transitions to ECM-IDLE. This procedure may be used for services that require accurate cell identification (e.... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.9.2 Location Change Reporting Procedure
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.9.2.1 General
| The PDN GW may request for each PDN connection independently whether the MME shall report changes of ECGI/eNodeB ID/TAI (by using the "MS Info Change Reporting Action" parameter) and/or the UE entering/leaving a Presence Reporting Area (by using the "Presence Reporting Area Action" parameter) and/or whether the MME sha... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.9.2.2 Reporting at Presence Reporting Area entering and leaving
| In some use cases policy control/charging decisions, such as QoS modification or charging rate change depend on whether the UE is located inside or outside a specific area of interest (Presence Reporting Area), and especially on whether the UE enters or leaves that specific area of interest.
A Presence Reporting Area ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.9.3 IMSI and APN information retrieval procedure
| This procedure is used by the RCAF to determine the UEs that are served by a congested eNodeB or E-UTRAN cell and the APNs of the active PDN connections of these UEs. This information is used to determine the PCRFs serving these UEs and subsequently report RAN user-plane congestion information (RUCI) to the PCRFs. The ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.10 Multiple-PDN support and PDN activation for UEs supporting "Attach without PDN connectivity"
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.10.1 General
| The EPS shall support simultaneous exchange of traffic to multiple PDNs through the use of separate PDN GWs or a single PDN GW. The usage of multiple PDNs is controlled by network policies and defined in the user subscription EPS Optimisation.
The EPS shall support UE-initiated connectivity establishment in order to a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.10.2 UE requested PDN connectivity
| The UE requested PDN connectivity procedure for an E-UTRAN is depicted in figure 5.10.2-1. The procedure allows the UE to request for connectivity to an additional PDN over E-UTRAN including allocation of a default bearer, if the UE already has active PDN connections over E-UTRAN. This procedure may also be used when a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.10.3 UE or MME requested PDN disconnection
| The UE or MME requested PDN disconnection procedure for an E-UTRAN is depicted in figure 5.10.3-1. The procedure allows the UE to request for disconnection from one PDN. Bearers including the default bearer of this PDN shall be deleted during this procedure. The procedure also allows the MME to initiate the release of ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.10.4 MME triggered Serving GW relocation
| The MME triggered Serving GW relocation procedure for E-UTRAN is depicted in figure 5.10.4-1. The procedure allows the MME to trigger Serving GW relocation due to events other than those described in the mobility scenarios (see clause 5.3.3.1 and clause 5.5.1). Such scenario exists during the establishment of a SIPTO a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.11 UE Capability Handling
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.11.1 General
| The UE Capability information is made up of the UE Radio Capability information and the UE Core Network Capability information.
The UE Radio Capability for Paging Information is separate from both the UE Radio Capability information and the UE Core Network Capability information. While some of the UE Radio Capability ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.11.2 UE Radio Capability Handling
| The UE Radio Capability information contains information on RATs that the UE supports (e.g. power class, frequency bands, etc). Consequently, this information can be sufficiently large (e.g. >50 octets for a UE supporting a small number of frequency bands; or multiple kilo bytes for a UE supporting many frequency bands... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.11.3 UE Core Network Capability
| The UE Core Network Capability is split into the UE Network Capability IE (mostly for E-UTRAN access related core network parameters) and the MS Network Capability IE (mostly for UTRAN/GERAN access related core network parameters) and contains capabilities, e.g. for CIoT, NAS/AS security algorithms (that also indicate ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.11.4 UE Radio Capability for Paging Information
| Depending upon the features implemented in the E-UTRAN, this procedure may assist the E-UTRAN in optimising the radio paging procedures, or this procedure can be essential for mobile terminating services to succeed.
Using procedures specified in TS 36.413 [36], the eNodeB shall upload the UE Radio Capability for Pagin... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.11.5 UE Radio Capability for Category M Differentiation
| This functionality is used by the Core Network to be able to identify traffic to/from Category M UEs for charging differentiation.
The eNodeB determines whether a UE is of Category M from the UE's radio capability if UE signals one or more of the specific Category M. The eNodeB then indicates to the MME whether the UE... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.12 Warning message delivery
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.12.1 General
| Warning message delivery is similar to Cell Broadcast Service defined in TS 23.041 [48], it permits a number of unacknowledged Warning messages to be broadcast to UEs within a particular area.
The maximum size of the Warning message for E-UTRAN is different from that of UTRAN/GERAN.
When S1-flex is used, the eNodeB m... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.12.2 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.12.3 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.13 Discontinuous Reception and UE Specific DRX Parameter handling
| During the Attach and Tracking/Routing Area Update procedures in E-UTRAN, UTRAN and/or GERAN, the UE can signal its UE Specific DRX Parameters to the Core Network (MME in the E-UTRAN case and SGSN in UTRAN/GERAN case).
In E-UTRAN and UTRAN, the UE may signal that it wishes to use the DRX cycle length broadcast in the ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14 Configuration Transfer procedure
| The purpose of the Configuration Transfer is to enable the transfer of information between two eNodeBs at any time via S1 interface and the Core Network. An example of application is to exchange the eNodeBs IP addresses in order to be able to use X2 interface between the eNodeBs for Self-Optimised Networks (SON), as sp... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14.1 Architecture Principles for Configuration Transfer
| Configuration Transfer between two eNodeBs follows the principles used by RAN Information Management (RIM) procedures (see clause 5.15) between UTRAN, E-UTRAN and GERAN i.e. providing a generic mechanism for the exchange of arbitrary information between applications belonging to the RAN nodes. However Configuration Tra... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14.2 Addressing, routing and relaying
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14.2.1 Addressing
| All the Configuration Transfer messages contain the addresses of the source and destination RAN nodes. An eNodeB is addressed by the Target eNodeB Identifier. For Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340 [85], the destination RAN node includes the candidate ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14.2.2 Routing
| The following description applies to all the Configuration Transfer messages used for the exchange of the E-UTRAN transparent container.
The source RAN node sends a message to its MME including the source and destination addresses. The MME uses the destination address to route the message encapsulated in a GTPv2 messa... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14.2.3 Relaying
| The MME performs relaying between GTPv2 messages as described in TS 29.274 [43]. The MME performs relaying between S1 and S10 messages as described in TS 36.413 [36], TS 23.501 [83] and TS 29.274 [43]. The Target eNodeB performs relaying between S1 and X2 message as described in TS 36.413 [36] and TS 36.423 [76].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.14.2.4 Applications using the Configuration Transfer procedures
| The RAN node applications, which use the Configuration Transfer procedures, are fully transparent for the MME. These applications are described in RAN specifications. An example of application is the transfer of information required for Self-Optimised Networks (SON).
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15 RAN Information Management (RIM) procedures
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15.1 General
| The RAN Information Management (RIM) procedures provide a generic mechanism for the exchange of arbitrary information between applications belonging to the RAN nodes. The RAN information is transferred via the MME and SGSN core network node(s). In order to make the RAN information transparent for the Core Network, the ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15.2 Addressing, routing and relaying
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15.2.1 Addressing
| All the messages used for the exchange of RAN information contain the addresses of the source and destination RAN nodes. A BSS is addressed by Routing Area Identity (RAI) + Cell Identity (CI) of one of its cells. An eNodeB is addressed by the Target eNodeB Identifier. An RNC is addressed by Global RNC-Id as defined in ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15.2.2 Routing
| The following description applies to all the messages used for the exchange of RAN information.
The source RAN node sends a message to its MME or SGSN including the source and destination addresses. The SGSN/MME uses the destination address to route the message encapsulated in a GTP message to the correct MME/SGSN via... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15.2.3 Relaying
| The SGSN performs relaying between BSSGP messages, RANAP messages and GTP messages as described in TS 48.018 [42], TS 25.413 [22], TS 29.060 [14] and TS 29.274 [43]. The MME performs relaying between S1 and S3/Gn messages as described in TS 36.413 [36] and TS 29.274 [43] / TS 29.060 [14].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.15.3 Applications using the RIM Procedures
| The RAN node applications, which use the RIM procedures, are fully transparent for the MME and SGSN. These applications are described in RAN specifications. An example between E-UTRAN and GERAN is the Network Assisted Cell Change described in TS 48.018 [42], TS 25.413 [22] and TS 36.413 [36]. An example between E-UTRAN... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.16 MME-initiated procedure on UE's CSG membership change
| If the UE is in ECM-CONNECTED state and connected via a CSG cell and the MME detects that the UE's CSG membership to that cell has expired, the MME shall send an S1AP UE CONTEXT MODIFICATION REQUEST message to the eNodeB which includes an indication that the CSG membership of the UE has expired. The eNodeB receiving th... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.17 Home eNodeB Multicast Packet Forwarding Function
| A Home eNodeB L-GW should receive and process multicast group membership report messages (e.g. according to RFC 3376 [62] / RFC 3810 [63]) sent either by the network accessed by LIPA or by the UE. Based upon these messages, the L-GW should forward multicast IP datagrams sent by the UE to the network accessed by LIPA, o... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.18 HPLMN Notification with specific indication due to MME initiated Bearer removal
| When initiating a Delete Session Request procedure, the MME shall add an appropriate cause code facilitating the operator of the P-GW to take appropriate action (e.g. Alarm, O&M action by operator's management network) if needed.
NOTE: This is for the HPLMN operator to be able to differentiate Delete Session Request p... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.19 Procedures to support Dedicated Core Networks
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.19.1 NAS Message Redirection Procedure
| When DCNs are used, these steps are used to reroute a NAS message (and thereby a UE) from one CN node to another CN node during Attach, TAU or RAU procedure. These steps are also used by the MME/SGSN or HSS initiated Dedicated Core Network Reselection procedure in clause 5.19.3.
Figure 5.19.1-1: NAS Message Redirect... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.19.2 Attach, TAU and RAU procedure for Dedicated Core Network
| When DCNs are used, the Attach, TAU and RAU procedures in this clause apply.
Figure 5.19.2-1: Attach,TAU and RAU procedure for Dedicated Core Network
1. Attach, TAU, or RAU procedure is initiated as specified in the relevant clauses of this specification and TS 23.060 [7]. The relevant steps of the procedure as spe... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.19.3 MME/SGSN or HSS initiated Dedicated Core Network Reselection
| If DCNs are deployed, this procedure is used by the HSS to update (i.e. add, modify or delete) the UE Usage Type subscription parameter in the serving node. This procedure may result in change of serving node of the UE. This procedure may also be used for MME/SGSN initiated serving node change for UEs, e.g. when config... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 1 Scope
| The present document specifies the application enabling layer platform architecture, capabilities and services to efficiently support storage and delivery for the application content/data for vertical applications as part of SEAL services specified in 3GPP TS 23.434 [4].
This work takes into consideration the existing... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 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.
-... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 3 Definitions of terms, symbols and abbreviations
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 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].
Application connection: Association between the VAL client and the VAL service to provide... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 3.2 Symbols
| None
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 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].
AF Application Function
CAPIF Common API Framework for northbou... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4 Overview
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.1 General
| This clause gives a functionality overview for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.2 Application signalling and data transmission
| This SEALDD functionality provides a mechanism for application signalling data transmission and application media data transmission between VAL client(s) and VAL server(s). The SEALDD enabled regular connection management procedures (e.g. connection establishment, connection deletion) are specified in clause 9.2. For s... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.3 Transmission quality measurement and transmission optimization
| The transmission quality measurement procedure specified in clause 9.7, supports the E2E transmission quality measurement between SEALDD client and SEALDD server, and exposes the transmission reports to VAL servers and other consumers (e.g. SEALDD server, NSCE server, etc). Based on the SEALDD enabled E2E transmission ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.4 Data transmission rate control
| The SEALDD layer provides the differentiated data delivery service with different bandwidth/transmission rate experience for VAL users, considering the network conditions (e.g. QoS monitoring, ECN marking for L4S report), which is described in clause 9.8.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.5 Service continuity support
| This functionality is provided to support service continuity due to UE mobility or load balance. The SEALDD layer maintains the transport layer connection by interacting SEALDD context, and requesting 5GC to perform seamless data transmission (e.g. IP replacement procedure, simultaneous connectivity). The service conti... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.6 Data storage
| The SEALDD server supports the data storage and storage management for VAL server, SEALDD client and other SEALDD servers, etc, the corresponding procedure is specified in clause 9.5.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.7 Background Data Transfer
| This SEALDD functionality enables to keep data transmission costs lower by favouring time windows for data transfer to/from specific UEs in a geographical area, e.g. during non-busy hours, that are less costly and able to handle larger bitrates. The background data transfer procedures are specified in clause 9.11.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 4.8 SEALDD enabled transmission for multi-modal service
| This SEALDD functionality enables data transmission for multi-modal service, e.g., XR application service, etc. The supported services include SEALDD enabled multi-modal data transmission service for multi-modal application, SEALDD enabled multi-modal flow synchronization, SEALDD enabled UE-to-UE communication based on... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 5 Business relationships
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 5.1 General
| The clause specifies the business relationships between the various stakeholders like VAL user, VAL service provider, SEALDD provider and PLMN operator.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 5.2 Business relationship option-A
| Figure 5.2-1 shows the business relationship option-A that exist and that are needed to support a single VAL user.
Figure 5.2-1: Business relationship option-A for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 5.3 Business relationship option-B
| Figure 5.3-1 shows the business relationship option-B that exist and that are needed to support a single VAL user.
Figure 5.3-1: Business relationship option-B for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6 Architectural requirements
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.1 General
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.1.1 Description
| The general architecture requirements specified in clause 4.1 of 3GPP TS 23.434 [4] are applicable for SEALDD service. This clause specifies the general requirements for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.1.2 Requirements
| [AR-6.1.2-a] The SEALDD service shall provide a discovery mechanism to support data delivery between VAL client(s) and VAL servers(s) considering different deployments of VAL server(s) (e.g. cloud or edge).
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.2 Data transmission requirements
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.2.1 Description
| This clause specifies the data transmission requirements for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.2.2 Requirements
| [AR-6.2.2-a] The SEALDD service shall provide a mechanism for application signalling data transmission and application media data transmission between VAL client(s) and VAL server(s).
[AR-6.2.2-b] The SEALDD service shall provide a mechanism to support the data transmission quality requirement configurations and measu... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.3 Data storage requirements
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.3.1 Description
| This clause specifies the data storage requirements for SEALDD service.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 6.3.2 Requirements
| [AR-6.3.2-a] The SEALDD service shall provide a mechanism for data storage supporting the CRUD operations.
[AR-6.3.2-b] The SEALDD service shall provide a mechanism to support the data storage status management.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.