hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.4.3 Services, Entities and Interfaces
| Editor's note: FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.4.4 Issues
| 1. Depending on the progress of other KIs (e.g., KI#3, KI#11) it is required to decide whether there is still UE Policy in 6G.
2. The 6G PCF can also store the Policy Set Entries in the 6G Data Framework (dependent on KI#21).
3. User preferences during UE policy evaluation shall be discussed based on use cases.
6.... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.5 Bullet 5: Solution variant #6.5: Support UE input for PCC decision
| This solution variant addresses KI#6, bullet 5 and is extracted from Solutions #18, #20, #6, #19 of Annex C, clause C.6, Table C.6-1.
Following are the high-level solution principles that are proposed:
1. UE input may be:
a. Application information (e.g. applications used by the UE, etc.).
b. QoS related PCC input ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.5.1 Description
| Editor's note: FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.5.2 Procedures
| Editor's note: FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.5.3 Services, Entities and Interfaces
| Editor's note: FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.6.5.4 Issues
| 1. Communication path (for the proposed options) to the core network for transporting UE inputs for PCC decision is FFS.
2. Each of the proposed transport options of UE inputs aspects (for e.g., authorization at the NEF, mention of CMF relaying to the PCF) needs to be discussed and is FFS and may require co-ordination... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.7 Solutions to KI#7
| Editor's note: The content of this clause is FFS
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8 Solutions to KI#8
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.0 High Level Summary of Solution variants for KI#8
| This clause shows the summary of solution variants for KI#8: 6G Network sharing.
Table 6.8.0-1: Summary of solution variants for KI#8
Classification of solutions for KI#8:
Other considerations
1
6G Multi-Operator Core Network
Solution#1
2
6G Indirect Network Sharing
Solution#1
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.1 Solution variant #8.1: 6G Multi-Operator Core Network
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.1.0 Topics addressed and High-level Solution Principles
| This solution is extracted from Solution#1 of Annex C.8 to propose 6G Multi-Operator Core Network (6G MOCN) mechanism for KI#8 (How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G). It gives the architecture design, the broadcasting info... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.1.1 Description
| Network sharing is a way for operators to share the heavy deployment costs for mobile networks, especially in the roll-out phase. For the network sharing in 6G, 6G Multi-Operator Core Network (6G MOCN) network sharing architecture, in which the 6G radio access network is shared in 6G System, should be designed. The arc... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.1.2 Procedures
| Editor's note: It is FFS how to perform the basic procedures to access the network through 6G MOCN after the PLMN selection.
Editor's note: It is FFS how to perform the mobility procedures between the non-shared network and shared network or between the different shared networks.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.1.3 Services, Entities and Interfaces
| Editor's note: If any enhancement in the clause 6.X.1.2 can be identified, the impacts on services, entities and interfaces can be added.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.1.4 Issues
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.2 Solution variant #8.2: 6G Indirect Network Sharing
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.2.0 Topics addressed and High-level Solution Principles
| This solution is extracted from Solution#1 of Annex C.8 to propose 6G Indirect Network Sharing (6G INS) mechanism for KI#8 (How to support the following network sharing architectures in 6G: Multi-Operator Core Network in 6G and Indirect Network Sharing in 6G). It gives the architecture design, the broadcasting informat... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.2.1 Description
| The 6G System should support 6G Indirect Network Sharing (6G INS) between hosting operator and participating operator (see Figure 6.8.2.1-1), in which the 6G RAN is shared. The communication between the shared 6G RAN and the 6G CN of the participating operator is routed through the 6G CN of the hosting operator that co... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.2.2 Procedures
| Editor's note: It is FFS how to perform the basic procedures to access the network through 6G INS after the PLMN selection.
Editor's note: It is FFS how to perform the mobility procedures between the non-shared network and shared network or between the different shared networks.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.2.3 Services, Entities and Interfaces
| Editor's note: If any enhancement in clause 6.X.2.2 can be identified, the impacts on services, entities and interfaces can be added.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.8.2.4 Issues
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.9 Solutions to KI#9
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.10 Solutions to KI#10
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.11 Solutions to KI#11
| Editor's note: The content of this clause is FFS.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12 Solutions to KI#12
| NOTE: In the description in sub-clauses of clause 6.12, a "{x}" denotes a reference to submitted solution "x" in Table C.12-1 of Annex C.12.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1 Solution variant #12.1: IMS based voice service using IP-CAN in the 6GS
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.0 Topics addressed and High-level Solution Principles
| The solution addresses KI#12, bullet#1, #2 and #3:
1. How the 6GS natively supports IMS based voice over the 6G access network, including how a UE supporting 6G RAN selects and connects to 6G network for voice service.
2. Whether and how to update the IMS specification to support an IP-CAN in the 6GS.
3. How to supp... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.1 UE's usage setting
| If the UE is configured to support IMS voice, the UE shall include the information element "UE's usage setting" in Registration Request message (or its equivalent message in 6GS). The UE's usage setting indicates whether the UE behaves in a "voice centric" or "data centric" way (Similar to TS 23.501 [2] clause 5.16.3.7... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.3 UE capability indicates to 6G RAN
| The UE indicates it supports IMS voice service to 6G RAN (e.g. 6G voice capability, 5G voice capability) in 6G RRC establishment procedure. {1} {5}
Editor's note: Whether needed and the details of IMS voice capability in 6G RRC are FFS and may require coordination with RAN WG.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.4 UE Capability Match Request procedure
| The 6GC can re-use the UE Capability Match Request procedure (e.g. as specified in the clause 4.2.8a of 23.502 [3]) to check the Voice Support Match Indicator for the UE. {5}
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.5 DNN
| The 6GC uses the well-known DNN for IMS. {1}
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.6 Transport of IMS signalling and IMS media traffic
| The UE supports IMS voice registers (or its equivalent procedure in 6GS) to the 6GS and requests PDU Session (or its equivalent in 6GS) for IMS service. {6}
As the same principle of existing IMS voice service, the IMS signaling and media are both transported over UP (user plane) of 6GS. The UP for IMS signaling and me... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.7 Voice continuity
| When the UE moves between 6G RAT and 5G RAT, SSC Mode 1 is used and the IMS voice service continuity is achieved by maintaining the IP address for the PDU Session (or its equivalent in 6GS) used for IMS connectivity. Maintaining the IP address ensures that the UE does not need to perform a fresh initial registration to... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.8 P-CSCF discovery and selection
| The 6GC network supports P-CSCF discovery and selection for the UE. {1} {6}
The P-CSCF information is pre/locally-configured in 6G core network or is dynamically generated by NRF based service discovery according to IMS DNN, S-NSSAI, and UE location; utilizing similar mechanisms as in 5G following the principles as de... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.9 P-CSCF restoration
| 6GC Core Network can support P-CSCF restoration procedure by using procedures defined by CT4 e.g., similar to what is currently defined in the clause 5.8 of TS 23.380 [12]. {2} {6}
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.10 HSS discovery and selection
| IMS subscriptions are stored and managed through the HSS. {6}
The I-CSCF/S-CSCF/IMS-AS uses the HSS discovery and selection functionality to select the appropriate HSS. The HSS discovery and selection principles as specified in Annex AA.3.3 of TS 23.228 [5] are re-used in 6GC. {6}
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.11 PCF aspects
| IMS can interact with 6G CN through a 6G PCF (or its equivalent NF in 6GS) for: {2}
- receiving 6G CN / 6G RAN information (e.g., User location information and/or UE Time Zone);
- subscribing to 6G CN events (e.g., PLMN Change, IP CAN/RAT change) and
- provisioning of service information (e.g., request the establi... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.12 Identity aspects
| IMS network can support usage of IMS identities, i.e. IMPI and IMPU, which are derived from 6G USIM using 6G identity. {1}
Editor's note: Whether 6G USIM is required needs coordination with CT6 WG.
Editor's note: Details of 6G identity depends on Key Issue #1: Study the support for control signalling for 6G System.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.13 Roaming aspects
| 6GS can support IMS Services for roaming users with: {2}
- Architecture without IMS-level roaming interfaces (Home routed the UE's IP point of presence is located in the home PLMN as well as whole IMS).
- Architecture with IMS-level roaming interfaces where the UE's IP point of presence is in VPLMN as well as P-CSCF... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.14 Paging aspects
| 6GS can support Paging policy differentiation. {2} {6}
The RAN node can support Paging Policy Differentiation (PPD) and Paging Priority to handle specific services like IMS voice during the paging, by reusing TS 23.228 [5] Annex E.9. {5}
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.15 Avoid late availability of Vo6G
| Reasons for the late availability of VoLTE/VoNR seem to include: {9, 12}
a) incomplete radio coverage on the new generation RAN. While this could be solved by handover from the new RAN to a legacy RAN this was hampered by:
i) lack of UE and RAN functionality and/or interoperability testing opportunities for mobile fe... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.1.16 Misc aspects
| 6GS can support: {2}
- Retrieval of User Status and IMEI.
- Network initiated session release - P-CSCF initiated.
- Provide NRF services to IMS NFs.
- Support of RAN Assisted Codec Adaptation.
The charging aspects will be addressed at a later stage. {2}
The UE sets the RRC establishment cause (e.g., mo-VoiceCall ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.1.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2 Solution variant #12.2: IMS Voice Call Fallback Mechanism
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.0 Topics addressed and High-level Solution Principles
| Editor's note: Whether to adopt the voice fallback solution and which voice fallback option as way forward are FFS.
Editor's note: Whether and how to do IMS Voice Call Fallback to EPS is to be FFS depending on Key Issue #17: Migration and Interworking.
Editor's note: The IMS Voice Call Fallback to NR, if needed, may ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.0.1 UE-based fallback mechanism
| If
- the network or the UE are not able to support IMS voice over PS session over 6GR connected to 6GC; and
- the network and the UE are able to support IMS voice over PS session over NR connected to 5GC;
then the AMF (or its equivalent NF in 6GS) sends the "Support of IMS voice over PS session" indication to the ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.0.2 Network-based fallback mechanism
| The Network-based fallback mechanism is a mapping of "EPS fallback procedure of 5GS" into "5GS fallback procedure of 6GS". {8}
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.1 Description
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.1.1 UE-based fallback mechanism
| For UE-based fallback mechanism, for different voice call scenarios, for different [Option 1] and [Option 2] specified in clause 6.12.2.0.1, the following principle applies:
Case 1) MO call, IDLE UE:
[Option 1] the UE initiates a Service Request with a "voice fallback" indication. then the UE sends a SIP INVITE over ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.1.2 Network-based fallback mechanism
| For 6G RRC establishment, the UE reports its IMS voice capability (e.g. 6G voice capability, 5G voice capability) and voiceFallbackIndication to 6G RAN. (It can refer the TS 38.331 [15] as example.) {5}
Editor's note: Whether needed, and the details of IMS voice capability in 6G RRC are FFS and may require coordinatio... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.2.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.3 Solution variant #12.3: Compatibility with existing deployed IMS
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.3.0 Topics addressed and High-level Solution Principles
| The solution addresses KI#12, bullet#6:
6. How to support the compatibility between 6G CN and the existing deployed IMS with minimum impacts on the existing deployed DIAMETER interfaces (e.g. Rx, Cx, Sh).
Editor's note: Two sub-variants proposed but which one to adopt requires further study.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.3.1 Description
| The current definition of the IMS architecture includes reference points based on SBI and Diameter for certain NFs (e.g. P-CSCF, S-CSCF, IMS AS, HSS, DCSF):
[Option 1]
- Only define the IMS architecture only based on SBI where there is an equivalent reference point based on Diameter:{3}
- Existing reference points ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.3.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.12.3.3 Services, Entities and Interfaces
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13 Solutions to KI#13
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.1 Solution variant #13.1: Support for emergency services via 6GS
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.1.0 Topics addressed and High-level Solution Principles
| This solution addresses the following aspects of KI#13:
- The functionality required in the UE and the 6G system to enable emergency voice service for 6GS.
- The functionality required in the UE and the 6G system to establish emergency session via 6GS for the emergency voice service.
- How to identify emergency ser... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.1.1 Description
| The 6G RAN node broadcasts support for emergency services using the ims-EmergencySupport flag to indicate that the cell may be considered acceptable by the UE.
When the UE is camped on a cell, and not in limited service state, during Registration procedure, the 6G Core includes an indication for Emergency Services Su... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.1.2 Procedures
| Detailed procedures for Emergency Services establishment via 6GS are FFS.
New procedures for Emergency Services Fallback described in clause 6.13.2 are triggered when the UE receives indication from 6G CN that Emergency Services over PS session is not supported natively over 6GR but through handover or redirection to ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.1.3 Services, Entities and Interfaces
| Existing UE and 6G CN procedures described in clauses 5.16.4 of TS 23.501 [2] and TS 23.167 [6] apply. In addition:
6G CN
• If Emergency Services over PS session are not supported "natively" over 6GR, the 6G CN provides indication to UE in Registration Accept whether Emergency Services Fallback over NR connected ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.1.4 Issues
| - The LS from ETSI TC EMTEL in SP-251285 presents additional requirements on emergency communications which can be invoked for persons with disabilities, including relay services, multiparty session control and translating services. The study of emergency service in 6G should take the afore mentioned requirements into ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.2 Solution variant #13.2: Support for Emergency Services Fallback to NR and E-UTRAN
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.2.0 Topics addressed and High-level Solution Principles
| This solution addresses the following aspects of KI#13:
- Whether and how to support emergency voice services if they are not provided in the serving 6G Network (Assuming this covers both domain selection and RAT/System selection at the time of the call).
The principles of clause 7.1.Y apply. In addition:
- 5GC p... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.2.1 Description
| This solution builds upon the principles described in solution variant #13.1 (Support for emergency services via 6GS) and assumes the UE has received indication in Registration Accept from the 6G CN that emergency services over PS session is not "natively" support over 6GR in the system but Emergency Services Fallback ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.2.2 Procedures
| Figure 6.13.2.2-1 describes the procedure for Emergency Services fallback.
Figure 6.13.2.2-1: Emergency Service Fallback
1. UE camps on 6GR in the 6G system.
2. UE has a pending emergency service session request from the upper layers.
3. If the 6G CN has indicated support for emergency services fallback via the ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.2.3 Services, Entities and Interfaces
| UE and 6G CN follow the procedures described.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.13.2.4 Issues
| - Whether handover to EPS is supported or not depends on KI#17 and KI#12
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14 Solutions to KI#14
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1 Solution variant #14.1: Enhance 5GS LCS architecture for 6GS
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.0 Topics addressed and High-level Solution Principles
| Solution addresses all bullet points from KI:
1. The architecture to support location services in 6GS.
2. How to support regulatory location services for emergency voice service in 6GS.
3. How to support location service exposure.
The high-level principles based on the first solution in #14.5 and solution #14.3 for... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.1 Description
|
Figure 6.14.1.1-1: Non-roaming reference architecture for Location Service for 6G (first solution in #14.5)
NOTE: AF and User Plane is only used for commercial services therefore those are out of scope in this release for this variant.
Figure 6.14.1.1-2: Non-roaming reference architecture for Regulatory Loca... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2 Procedures
| All signalling procedure as defined in TS 23.273 [13] can be enhanced for 6G version of the procedures:
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2.1 6GC-MT-LR procedure for the regulatory location service
|
Figure 6.14.1.2.1-1: 6G-MT-LR procedure for the regulatory location service
Procedure itself is identical with 5G procedure as written in clause 6.1.1 of TS 23.273 [13], but Entities are enhanced with 6G capabilities and support 6G-RAN. Enhancements are listed in 6.14.1.3.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2.2 6GC-MT-LR multiple location procedure for the regulatory location service
|
Figure 6.14.1.2.2-1: 6GC-MT-LR multiple location procedure for the regulatory location service
Procedure itself is identical with 5G procedure as written in clause 6.1.3 of TS 23.273 [13], but Entities are enhanced with 6G capabilities and support 6G-RAN. Enhancements are listed in 6.14.1.3.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2.3 6GC-NI-LR Procedure
|
Figure 6.14.1.2.3-1: 6GC-NI-LR
Procedure itself is identical with 5G procedure as written in clause 6.10.1 of TS 23.273 [13], but Entities are enhanced with 6G capabilities and support 6G-RAN. Enhancements are listed in 6.14.1.3.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2.4 6GC-MT-LR Procedure without UDM Query
|
Figure 6.14.1.2.4-1: 6GC-MT-LR Procedure without UDM Query
Procedure itself is identical with 5G procedure as written in clause 6.10.2 of TS 23.273 [13], but Entities are enhanced with 6G capabilities and support 6G-RAN. Enhancements are listed in 6.14.1.3.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2.5 Network Assisted Positioning Procedure with direct periodic measurement report based on solution #14.3
|
Figure 6.14.1.2.5-1: Network Assisted Positioning Procedure with direct periodic measurement report based on solution #14.3
Extended Network Assisted Positioning Procedure proposed by solution #14.3 to be introduced compared to 5G as enhancement. This procedure allows 6G-RAN and 6G-LMF to establish a direct connec... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.2.6 Terminate direct connection between 6G-RAN and 6G-LMF based on solution #14.3
| If the direct connection between 6G-RAN and 6G-LMF is not used as proposed in solution #14.3, then 6G-LMF can decide to terminate it based on Figure 6.
Figure 6.14.1.2.6-1. Terminate direct connection between 6G-RAN and 6G-LMF based on solution #14.3
1. 6G-LMF decides to terminate direct connection between 6G-RAN a... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.3 Services, Entities and Interfaces
| 6.14.1.3.1 Following Entities are reused and enhanced from 5G:
- 6G-LMF: 5G LMF enhanced with 6G-RAN capabilities. Based on solution 14.3 this includes a new interface (eNLp) to send periodical measurements data from 6G-RAN to 6G-LMF. 6G-LMF supports 6G Positioning methods.
- 6G-UDM: Enhanced to store UE informatio... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.3.1 Entities reused and enhanced from 5G
| The following Entities are reused and enhanced from 5G:
- 6G-LMF: 5G LMF enhanced with 6G-RAN capabilities. Based on solution 14.3 this includes a new interface (eNLp) to send periodical measurements data from 6G-RAN to 6G-LMF. 6G-LMF supports 6G Positioning methods.
- 6G-UDM: Enhanced to store UE information resides... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.3.2 Interfaces
| - eNLp: based on solution 14.3 this is a new interface in 6G introduced between 6G-RAN and 6G-LMF in order to receive location related measurement reports periodically.
- Le: interface towards LCS client is proposed to be kept. Interface is widely used in earlier generations for regulatory purposes mostly using Mobile... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.1.4 Open issues
| First solution in #14.5 expects backward compatibility for signalling but solution #14.3 does not state this since different interfaces may be enhanced due to another KIs.
Solution variant depends on the conclusion of KI#1.
|
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2 Solution variant #14.2: Redesign 5G LCS architecture related to AMF (mobility management) involvement
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.0 Topics addressed and High-level Solution Principles
| Solution addresses all bullet points from KI:
1. The architecture to support location services in 6GS.
2. How to support regulatory location services for emergency voice service in 6GS.
3. How to support location service exposure.
The high-level common principles based on the second solution in #14.5 and solution i... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.1 Description
|
Figure 6.14.2.1‑1: Architecture 6G location service in reference point representation (Sol#14.4)
Figure 6.14.2.1‑2: Architecture for 6G location service in SBI representation (Sol#14.4)
Figure 6.14.2.1-3 Non-roaming reference architecture for user-plane based Location Service for 6G (second solution in #1... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2 Procedures
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.1 Procedures based on solution #14.4
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.1.0 Positioning Message Transfer
| The positioning messages include LPP+ message and NRPPa+ message. The 6G location service architecture supports NLd interface between 6G RAN and 6G LMF to transfer the messages.
Editor's note: The details of the NLd interface (e.g. NLd interface is P2P interface or service based interface) is FFS and coordination wit... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.1.1 6GC-MT-LR procedure for the regulatory location service
| Figure 6.14.2.2.1.1-1 illustrates the general network positioning for the LCS clients external to the PLMN for the regulatory location service for non-roaming scenario.
This procedure is applicable to a request from an LCS client for a current location of the target UE, and it is assumed that the LCS client is authori... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.1.2 UE Positioning Procedure
| |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.1.2.1 UE Assisted and UE Based Positioning Procedure
| Figure 6.14.2.2.1.2.1-1 shows a positioning procedure used by a 6G LMF to support UE based positioning, UE assisted positioning and delivery of assistance data. The procedure is based on use of the LPP+ protocol between the LMF and UE.
Figure 6.14.2.2.1.2.1-1: UE Assisted and UE Based Positioning Procedure
1. The 6... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.1.2.2 Network Assisted Positioning Procedure
| Figure 6.14.2.2.1.2.2-1 shows a procedure that may be used by a 6G LMF to support network assisted and network based positioning. The procedure may be based on NRPPa+ signalling between the LMF and NG-RAN.
Figure 6.14.2.2.1.2.2-1: Network Assisted Positioning Procedure
1. The 6G LMF sends Transfer (NRPPa+ message) ... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.2.2 Procedures based on solution #14.5
| A 6G UE establishes the PDU session for the operator services support, based on the URSP or UE configurations, when it registers to the network. For a UE that supports LCS, it can discover a 6G LMF to connect to, based on configurations, or a self-formulated FQDN. The connection between the UE and the LMF can be based... |
fcf00dbf2301bc1e78448d06d0e070aa | 23.801-01 | 6.14.2.3 Services, Entities and Interfaces
| 6.14.2.3.1 Following Entities and functionalities are defined based on Solution #14.4
The 6G GMLC supports the following functions:
- Support Le interface to LCS Client.
- Support privacy check.
- Obtain serving CRF information of target UE from UDM+.
- Get cell ID and TAI of Target UE from the 6G mobility manage... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.