hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.29.2 Procedures | Editor's note: How this solution can apply to roaming UEs is FFS.
Editor's note: How does the UE-satellite-UE communication link work if the serving satellite changes or at least one UE moves out of the serving satellite's coverage is FFS.
Figure 6.29.2-1:Procedures of activation of UE-satellite-UE communication during... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.29.3 Impacts to Services, Entities and Interfaces | SMF:
- Derives UE-1 and UE-2's IDs based on source/destination IP address and further derives the satellite ID of UE-1 and UE-2.
- Detects/verifies UE-1 and UE-2 are under same satellite coverage based on UE-1 and UE-2's satellite ID.
- Inserts the UPF deployed on satellite (collocated with RAN onboard) as UL CL and PS... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.30 Solution #30: Solution to determine UE-SATs-UE eligibility and enable communication setup | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.30.1 Description | The proposed solution complies with all architectural assumptions and principles of the present document as well as network scenarios for UE-Sat-UE generic architecture (regenerative payload capabilities on LEO satellite), as described in Annex C.
It evaluates eligibility necessary condition for realizing UE-satellite-... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.30.2 Procedures | The main steps for the procedure are the following:
Figure 6.30.2.1: determine UE-SATs-UE eligibility and enable communication setup.
1. When establishing a communication, the Caller UE inserts the field "P_Access_Network_Info" in a SIP message, e.g.: INVITE, indicating gNodeB identifier corresponding to its serving sa... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.30.3 Impacts on existing nodes and functionalities | UE:
- Provide P-Access-Network-Info header with fresh NR Cell Identity value.
xCSCF:
- Collect NR Cell Identity and IP address for the caller and the called UEs.
- Interrogate a satellite connectivity service, which monitors in real time satellite constellation motion and satellites interconnectivity, providing serving... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.31 Solution #31: UE-satellite-UE communication for IMS voice and video (UPF onboard) | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.31.1 Description | This solution resolves Key Issue #3: Support of UE-satellite-UE communication and focus on IMS voice and video service.
This solution based on the following assumptions:
- the PSA UPF anchored by IMS PDU session is on the ground and the UPF acting as UL CL/BP/local PSA to be deployed onboard satellite.
- All the IMS co... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.31.2 Procedures | Figure 6.31.2-1: Procedure of UE-satellite-UE communication for IMS voice and video (UPF onboard local switching)
1. During a call session setup process, the IMS component P-CSCF determines that local switching in the UPF onboard is possible. To determine this, the P-CSCF takes into account whether the UE is accessing ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.31.3 Impacts on services, entities and interfaces | IMS:
- The P-CSCF determines whether UPF local switching is possible when the UEs involved in the communication service with each other are accessing network via the satellite.
- The P-CSCF informs 5GC which two UEs are call parties for UE-satellite-UE communication with UPF local switching.
- The P-CSCF receive the re... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32 Solution #32 for Key Issue #3: Support of UE-satellite-UE communication for IMS services with UPF/AGW inserted on satellites | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.1 Description | This solution resolves the Key Issue #3 to support UE-satellite-UE communication for IMS services, and some content can resolve Key Issue #1.
This solution proposes enhancement to both 5GC and IMS, including:
- Enhance 5GC procedures and functions to transfer and handle the access network information with specific trea... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.1.1 Reference Architecture | The examples of network architecture are listed in the Annex C. For this solution, gNBs, UPFs and IMS AGWs are deployed on the satellites. The PSA UPFs for IMS session are on the ground.
IMS AGW can be deployed on each satellite with gNB and UPF, as shown in the Figure 6.32.1-1.
Figure 6.32.1.1-1: Network architecture ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.2.1 Provision of access network information in 5GC | This procedure is based on PDU session Establishment or Modification procedures described in clauses 4.3.2 or 4.3.3 of TS 23.502 [3], with specific treatment for Regenerative-based satellite access.
NOTE. The mechanism of this procedure can also apply for Key Issue #1 accordingly.
Figure 6.32.2.1-1 describes the genera... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.2.2 Provision of access network information to IMS | In this procedure, the 5G core network can provide the access network information of the UE via regenerative-based satellite access (e.g. RAT type information and/or Serving satellite ID) to IMS. This information is required in IMS to comply with regulatory requirements (e.g. data retention, lawful interception) and de... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.2.3 IMS procedures to determine to perform the UE-satellite-UE communication | This procedure describes how the access network information, with specific treatment for Regenerative-based satellite access provided by 5GC (e.g. RAT type information, and/or Serving satellite ID, and/or NPLI), can be distributed within IMS. This information is necessary in IMS to determine whether the conditions are ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.2.4 IMS influence on traffic routing | This procedure is proposed to ensure traffic routing remains in the satellites. It is based on Application Function influence on traffic routing procedures described in clause 4.3.6 of TS 23.502 [3].
- P-CSCF sends request to influence SMF routing decisions for traffic, by initiating Application Function influence on t... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.32.3 Impacts to Services, Entities and Interfaces | The following impacts are foreseen by this solution:
AMF:
- Determination of the RAT Type information and serving satellite ID for Regenerative-based satellite access of the UE.
- Provision to other NFs the RAT Type information and serving satellite ID for Regenerative-based satellite access.
SMF:
- Provision to other ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.33 Solution #33: Solution for UE-satellite-UE communication with IMS media entity onboard | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.33.1 Description | This solution resolves Key Issue #3 about the Support of UE-satellite-UE communication. Focus on the Architectural enhancement to support UE-satellite-UE communication, including minimum necessary set of 5GC network functions and IMS components (if any) onboard the satellite(s), and minimize service interruption if the... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.33.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.33.2.1 UE-Satellite-UE Communication Signalling | Figure 6.33.2.1-1: UE-Satellite-UE Communication Solution Procedure
1. For UPF(SAT) service Registration procedure, NRF store the UPF(SAT) profile(configured by OAM system, should include the IP address and Satellite ID of UPF(SAT)).
2. AMF can obtain Global RAN ID from RAN through NG Setup process.
3. After the satell... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.33.2.2 Minimize service interruption if the Serving Satellite changes | Due to the high mobility of LEO/MEO satellites, there are two scenarios after the UE connects with a satellite: multiple satellites provide continuous coverage to the same Earth Stationary Cell (as shown in Figure 6.33.2.2-1), and multiple satellites do not provide continuous coverage to the same Earth Stationary Cell ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.33.3 Impacts on services, entities and interfaces | This solution impacts the following entities.
O&M:
- Capability to configured the UPF(SAT) profile(Include the Satellite ID of UPF(SAT))
- Capability to provision all the Satellite ID of all satellite to AMF.
SMF:
- Capability to utilize the NRF to discover UPF(SAT) based on the RAT Type and Satellite ID.
AMF:
- Capabi... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.34 Solution #34: Enhancement on AMF discovery for Regenerative-based satellite | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.34.1 Description | This is a solution addressing Key Issue#1.
For LEO/MEO deployment, the gNB deployed on a satellite moves around the earth, it is not preferable to locally configure the IP addresses of all AMFs on the earth that can be connected by the satellite gNB. This solution provides mechanism for Satellite/gNB to dynamically dis... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.34.2 Procedures | The following procedures shows how to enhance the AMF discovery Regenerative-based satellite.
Figure 6.34.2.1-1: AMF selection enhancement for Regenerative-based satellite
0. The Satellite/gNB is configured with the address information of AMF Agent based on the ephemeris information of the Satellite/gNB.
1. When the Sa... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.34.3 Impacts on services, entities and interfaces | NGAP interface:
- The NG Setup response message is enhanced to include the address information of all AMFs within AMF agent's service area that is allowed to be connected by the Satellite/gNB
AMF Agent:
- AMF with enhancement on the NGAP interface as described in clause 6.34.2.
Satellite/gNB:
- gNB with enhancement on ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.35 Solution #35: N2/S1 procedures to handle feeder link switch | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.35.1 Description | This solution addresses KI#1.
There are different potential deployment scenarios for how feeder link switch takes place. In Figure 6.35.1-1 below, examples of where the gNB can reach the same AMF or not reach the same AMF after the feeder link switch are shown.
Figure 6.35.1-1. Feederlink switch scenarios
Both of these... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.35.2 Procedures | There are no impacts to the 3GPP procedures.
Editor's note: Call flows illustrating the scenario 2 options are FFS. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.35.3 Impacts to Services, Entities and Interfaces | gNB/eNB and AMF/MME implementations would need to support above mentioned existing features (e.g. multiple TNL associations, UE retention)
There are no impacts to 3GPP protocols or the SA WG2 standards. Potential impacts to describe the above methods in the context of NTN is assumed to be out of SA WG2 scope. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.36 Solution #36: User plane path failure management due to satellites leaving an area served by a CN | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.36.1 Description | This solution resolves Key Issue #1: Support of Regenerative-based satellite access.
This solution assumes that the gNB is deployed on LEO satellite and 5GC is on the ground.
To prevent user plane path failure errors, this solution is illustrated. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.36.2 Procedures | Figure 6.36.2-2 Method 1 of user plane path failure handling procedure
1. The gNB informs the AMF that movement information of itself.
2. The AMF informs the SMF when gNB on-board satellite has left the serving aera.
3&4. When the UPF does not receives regular Echo Response in the last path detection, the UPF informs t... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.36.3 Impacts to Services, Entities and Interfaces | Editor's note: Impacts to Services, Entities and Interfaces is FFS. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37 Solution #37: AMF Split Architecture to support Control plane procedure for S&F | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.1 Key Issue mapping | This solution aims to resolve the Key Issue #2, "Support of Store and Forward Satellite operation". |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.2 Description | As agreed in KI#2, The Store and Forward Satellite (S&F) operation in a 5G system with satellite access is intended to provide some level of communication service for UEs under satellite coverage with intermittent/temporary satellite connectivity (e.g. when the satellite is not connected via a feeder link or via ISL to... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3.1 5GS Architecture enhancement to support S&F | As agreed in KI#2, the delay tolerant/non-real time services can be served via S&F Satellite operation.
Figure 6.37.3.1-1: AMF split architecture for Store and Forward operation for 5GS
The key difference between the 3GPP Rel-18 and the proposed method is the buffering of MO and MT data on the NF in the orbit and buffe... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3.2 Registration Procedure in 5GS in S&F scenario | Figure 6.37.3.2-1: Registration procedure in S&F
1. UE to (R)AN: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI)
The Registration type indicates if the UE wants to perform an Initial Registration, a Mobility Registration Update, a Periodic Registration Update, an Emergency Re... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3.3 UE Reachability Estimation (Satellite Location/Coverage Information) | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3.3.1 UE reachability estimation | The URE is a new network function located on ground responsible for estimating which non-terrestrial network element can reach the UE, according to defined criteria, such as in shortest amount of time possible. The following figure shows a possible architecture, including the URE.
Figure 6.37.3.3-1: Architecture 5GS in... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3.3.2 URE-TNFs interaction and use-cases | A TNF that would like to know when a given UE is reachable queries the URE for this UE. The URE responds with the earliest possible "UE Reachability Time" and "UE Reachability Duration" and candidate Satellites. There can be several use cases where a TNF may interrogate the URE, for example:
1. to set a timer for a NAS... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.3.3.3 Reachability Modes | The information provided in the URE response to the TNF varies, depending on a selected "Reachability Mode" (RM). The RM determines how the UE is reachable; for example, "Same SAT Mode" (SSM), "Any SAT Mode" (ASM) or "Fastest Reach Mode" (FRM) (via inter-SAT link).
"Same SAT Mode" (SSM) assumes that the same satellite ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.37.4 Impacts on services, entities and interfaces | UE:
- NAS impact to handle larger delay due to S&F mode of operation.
- NAS impact due to new MM capability handling (S&F).
- NAS impact due to new interim GUTI allocation.
AMF-T:
- Buffer/Store N2 messages for transmission towards the UE.
- Determine when buffered N2 message should be transmitted to the relevant AMF-N... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.38 Solution #38: Exposure of Registration in S&F Mode | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.38.1 Description | This solution addresses following aspect of KI #2:
- What enhancements on the related UE and network procedures are needed to support S&F Satellite Operation?
When a UE registers to the network in S&F mode and is available to send/receive data on specific occasions only (e.g. when satellites fly-over and later connect ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.38.2 Procedures | It is proposed to add following events to be exposed by AMF/MME, UDM/HSS via NEF/SCEF to AF:
6.38.2-1
Event
Detection criteria
Which NF detects the event
Registration in S&F Mode
Detected when the UE registers in S&F Mode. The event report may include an indication of S&F Mode.
Ground-AMF/Ground-MME/UDM/HSS
Feeder Link... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.38.3 Impacts on services, entities and interfaces | AF/UDM/AMF/HSS/MME/SCEF/NEF: Support of new monitoring events. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.39 Solution #39: Session creation and parameters provisioning for S&F | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.39.1 Key Issue mapping | This solution is related to Key Issue #2 (Support of Store and Forward Satellite operation). |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.39.2 Description | Considering the limited storage capability of the MME/SGW on satellite, which performs S&F operation, the MME/SGW may configure storage quota for each UE, and may provision the parameter to UE for assisting UE to manage UL data sending to avoid exceeding the quota.
The Initial Attach / Initial Registration procedure is... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.39.3 MME, SGW and PGW onboard | Figure 6.39.3-1 depicts the Session create procedure for S&F operation with MME, SGW and PGW onboard, which can be during attach procedure or UE requested PDN connectivity procedure. Other attach procedures (e.g. the Authentication, security setup) can be resolved in other solutions (e.g. Sol#16).
In this procedure, th... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.39.4 Impacts on services, entities and interfaces | MME:
- Indicates the SGW to store the data.
- May allocate a S&F parameters (e.g. allowed Storage space, retention period) to UE.
SGW:
- May allocate a S&F parameters (e.g. allowed Storage space, retention period) to UE. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40 Solution #40: User plane offload from P-CSCF/IMS-AGW located on the ground | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.1 Description | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.1.1 General | This solution addresses Key Issue #3 Support of UE-satellite-UE communication.
KI#3 refers to the communication between UEs under the coverage of one or more serving satellites without the user plane traffic going through the ground network. In this case the UPFs need to be on the satellites to switch the media flows l... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.1.2 Architecture assumption | The demonstrating architecture for this solution is shown in Figure 6.40.1.2-1.
Figure 6.40.1.2-1: Demonstrating architecture
The UE1 and UE2 are connected to the different satellites which belong to the same satellite system with ISL connection. It is assumed the ISL is always available during the session. Each satell... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.2.1 Session establishment procedure | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.2.1.1 Procedure of option 1 | The figure 6.40.2.1.1-1 depicts the procedures in which the UE includes satellite access information in REGISTER request and INVITE request.
Figure 6.40.2.1.1-1: Procedure of option 1
The procedure of option 1 is as follows:
1. UE1 and UE2 has established PDU sessions for IMS. The SMF is on the ground and SMF has selec... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.2.1.2 Procedure of option 2 | The figure 6.40.2.1.2-1 depicts the procedures in which the UE includes satellite access information only in INVITE request and response.
Figure 6.40.2.1.2-1: Procedure of option 2
The procedure of option 2 is as follows:
1. UE1 and UE2 has established PDU sessions for IMS. The SMF is on the ground and SMF has selected... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.2.2 Satellite handover procedure | The figure 6.40.2.2-1 depicts the procedure when the on-board gNB and UPF change due to satellite moving.
Figure 6.40.2.2-1: Procedure of satellite handover
1. UE1 and UE2 has established PDU sessions for IMS. The media traffic of IMS session is transferred via gNB and ULCL/BP/local PSA UPF on the source satellite.
2. ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.40.3 Impacts on existing services, entities and interfaces | UE impacts:
- UE includes satellite access information in REGISTER, INVITE request and response message.
P-CSCF impacts:
- P-CSCF stores the satellite access information and includes the information in REGISTER, INVITE request and response message.
- P-CSCF determines whether the user traffic is able to be offloaded ba... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.41 Solution #41: Support of UE-satellite-UE communication for IMS services with UPF/AGW on board | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.41.1 Description | This solution resolves the Key Issue #3 to support UE-satellite-UE communication for IMS services.
This solution assumes that the UPF/AGW on board of the satellite, and the ground PSA UPF was selected when the PDU Session is established, the UPF on board satellite is inserted into the data path to act as UL CL and Loca... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.41.1.1 Reference Architecture | For this solution, gNB, UPF and AGW are deployed on the satellite, as shown in the Figure 6.41.1-1.
Figure 6.41.1.1-1: Network architecture with IMS AGW deployed on each satellite
A satellite may have multiple ISLs with multiple satellites, when an AGW receives a media packet from UE, it is not clear which ISL should b... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.41.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.41.2.1 Procedure when serving satellite changes | Figure 6.41.2.2-1 depicts the example scenario of the handover procedure: UE#1 handover from SAT-1 to SAT-2, and UE-2 states in SAT-2 unchanged.
Figure 6.41.2.2-1: Example scenario of the handover procedure
Based on the procedure of clause 4.3.5.7 "Simultaneous change of Branching Point or UL CL and additional PSA for ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.41.3 Impacts to Services, Entities and Interfaces | The following impacts are foreseen by this solution:
SMF:
- Provision to PCF the serving satellite ID for Regenerative-based satellite access.
PCF:
- Provision to P-CSCF serving satellite ID for Regenerative-based satellite access.
P-CSCF:
- Selection of AGW onboard satellite.
- Determines whether the USU communication... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42 Solution #42: UE-satellite-UE communication in the context of LEO satellite constellations with ISL | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.1 Description | This solution resolves Key Issue #3: Support of UE-satellite-UE communication and also Key Issue #1. The focus is on architectural enhancements to support UE-satellite-UE communication particularly for IMS voice and video service via a satellite constellation of LEO satellites. Multiple LEO satellites form a satellite ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.1 Association of Relay entity representative of satellite constellations | The registration procedure for the Relay entity with AMF, SMF, and P-CSCF respectively is as illustrated in Figure 6.42.2.1-1. The identifier for the constellations "satellite constellation ID" is used.
The ground-based representative Relay entity of satellite constellations establish a connection with each of the coun... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.2 Registration Procedure | Figure 6.42.2.2-1: Registration for UE-satellite-UE communication.
1. When a UE initiates a call, an RRC connection is set up between the UE and its serving gNB (onboard). The gNB then refers to the list of [start time, end time, to-be-connected Relay] created based on the satellite ephemeris and selects the appropriat... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.3 IMS PDU Session Establishment Procedure | Figure 6.42.2.3-1: IMS PDU session establishment procedure.
1-3. AMF receives PDU session establishment request for IMS DNN via the Relay. Based on the locally stored information created by the procedure in Clause 6.42.2.1, the AMF recognizes that the request comes from a UE served by a particular satellite constellati... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.4 IMS registration and voice call setup procedure | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.4.1 IMS registration | Figure 6.42.2.4.1-1: IMS registration
1. The UE sends Register to the P-CSCF IP address available to it from the ePCO (see Clause 6.42.2.3).
2. P-CSCF sends Register to S-CSCF.
3. Registration of S-CSCF in HSS.
4. Nhss_ImsSDM_Get request/response between S-CSCF and HSS.
5-6. 200 OK messages from S-CSCF to P-CSCF and fr... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.4.2 Voice call setup procedure - MO | Figure 6.42.2.4.2-1: Voice call setup procedure - MO
1. A voice establishment request message (SIP INVITE) is received at the P-CSCF.
The P-CSCF selects the Relay belonging to the satellite constellation ID based on UE's IP address and the corresponding satellite constellation ID.
2-4. Message for controlling the acces... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.2.4.3 Voice call setup procedure - MT | Figure 6.42.2.4.3-1: Voice call setup procedure - MT
1. SIP INVITE is received at I-CSCF.
2-3. I-CSCF looks for S-CSCF to forward SIP INVITE.
4-5. SIP INVITE is forwarded to S-CSCF then to P-CSCF.
6. P-CSCF selects the Ip intermediary belonging to the satellite constellation ID based on the terminating UE's IP address ... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.42.3 Impacts on services, entities, and interfaces | gNB on board:
- Capability to use satellite ephemeris and to discover an appropriate ground-based Relay.
Relay:
- A new network node that behaves as a gNB to AMF on the ground and as an AMF to gNB on board.
- Capability to use satellite ephemeris and to discover an appropriate gNB on board.
- Behaves as a UPF to SMF on... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43 Solution #43: UE-Sat-UE communication using resource allocation on-board satellite | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.1 Key Issue mapping | This solution aims to resolve Key Issue #3, " Support of UE-satellite-UE communication". |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.2 Description | This solution aims to ensure that the routing of user plane traffic for IMS (MMTEL) remains in the satellite(s) when both parties are served by a satellite of the same constellation. It considers that both parties could be served by the same or different satellites involving same or different SMF, UPF, PCF, P-CSCF.
Thi... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3.1 Overview | The call flows of clause 6.43.3.2 describe the case of an SDP Offer-answer scenario where resources are first reserved when the SDP Answer is processed by the local P-CSCF and then resources are reserved at the side of the SDP offer. |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3.2 PCC and SMF Procedures for IMS Session Establishment at terminating P-CSCF and PCF | This clause details the changes to be made to clause B.2.2. of TS 29.513 [25] it uses the same step numbers.
Figure 6.43.3.2-1: PCC Procedures for IMS Session Establishment at terminating P-CSCF and PCF
0. at IMS initial registration onto the P-CSCF the P-CSCF subscribes (Npcf_PolicyAuthorization_Subscribe targeting th... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3.3 PCC and SMF Procedures for IMS Session Establishment at Originating P-CSCF and PCF | This clause details the changes to be made to clause B.2.1 of TS 29.513 [25]. It uses the same steps numbers.
Figure 6.43.3.3-1: PCC Procedures for IMS Session Establishment at originating P-CSCF and PCF
1. The P-CSCF receives the SDP parameters defined by the originator within an SDP offer in SIP signalling.
2. The P-... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3.4 Change of Satellite in UE-Sat-UE scenario (mobility) | Figure 6.43.3.4-1: Change of Satellite in UE-Sat-UE
Figure 6.43.3.4-2: Change of Satellite using simultaneous change of UL CL
The above call flow is based on clause 4.3.6.7 from TS 23.502 [3].
UE has an established PDU Session with a UPF, including the PDU Session Anchor (Ground UPF). The PDU Session user plane involve... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3.4 Roaming case in UE-Sat-UE scenario | Figure 6.43.3.4-1: Voice roaming architecture using LBO
- For IMS roaming to work, the P-CSCF and S-CSCF exchange and record each other's Uniform Resource Identifiers (URIs) during IMS registration as specified in TS 24.229 [11]. The recorded S-CSCF URI is added as an SIP route header during the session setup by P-CSCF... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.3.5 Support for jurisdictions where LI can apply | When the satellite serves an area where LI may apply, the architecture supports an IMS-AGW on board of the satellite, as depicted in Figure 6.43.3.5-1.
This figure depicts a change of satellite at the side of the left UE where S-RAN / S-I-UPF and S-AGW-NT represent the RAN, the intermediate UPF (supporting both a UL CL... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.43.4 Impacts on services, entities and interfaces | UE:
- The UE needs to invoke reinvite based its own implementation of detecting change of serving satellite. The UE will use the existing P-ANI header information.
IMS
- IBCF: Allows PANI information be sent to the other party of the call but with only (outer IP) addressing information.
- P-CSCF.
- Upon UE registration... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44 Solution #44: eNB buffered signalling and CP data transfer with eNB monitoring list | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.1 Description | This solution resolves Key Issue #2.
Taking into account the intermittent availability of the service link and ground link the solution enhances Store and Forward operation while improving the UE power saving.
The enhanced attach procedure is used as example to illustrate the solution concept.
- The attach procedure is... |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.2 Architecture | Figure 6.44.2-1: eNodeB on board architecture with S&F operation |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.2 Procedures | |
bb41941961990826fe11f1fd44c6e58e | 23.700-29 | 6.44.2.1 Attach Procedure | The enhanced attach procedure is shown in Figure 6.44.2.1-1. The eNodeB calculates a next accessing time value that indicates when the service link will become available again. The UE uses this time to resume the attach procedure.
Figure 6.44.2.1-1: High-level procedure for S&F attach
1. When service link is available,... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.