hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 4.2 Architectural Requirements | The solutions should build on 5GS architectural principles as defined in TS 23.501 [2]. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 5 Key Issues | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 5.1 Key Issue #1: Support of UE move between CAG cell of 5G Femto and CSG cell | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 5.1.1 General description | This key issue investigates any needed enhancements to support the UE moving between CAG cell of 5G Femto and CSG cell.
The KI should cover:
- The mobility scenarios to be studied for the UE move (e.g. CSG cell to CAG cell of 5G Femto, vice versa).
- Whether and how control signalling procedures are enhanced to support... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 5.2 Key Issue #2: Enabling provisioning of subscribers allowed to access CAG cell and managing access control by the CAG owner or an authorized administrator | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 5.2.1 Description | The 5G NR Femto aims to re-use the existing CAG mechanism defined for PNI-NPN for access control. In order to add flexibility to the 5G NR Femto, the owner of 5G NR Femto needs to be able to control which UE(s) can access to the 5G NR Femto.
NOTE 1: Ownership of the 5G NR Femto (or CAG or both) concept and a mechanism ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6 Solutions | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
<Key Issue #1>
<Key Issue #2>
#1
X
#2
X
#3
X
#4
X
#5
X
#6
X
#7
X
X
#8
X
#9
X
#10
X
#11
X |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1 Solution #1: Provisioning of CAG info to the network that 5G Femto serves | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1.1 Description | This solution mainly addresses two aspects that KI#2 states:
i) "The provisioning/updating of CAG info to the network that 5G Femto serves [..] will be considered".
ii) "consider the scenario of allowing the access to a CAG cell in the [..] visited network".
This solution introduces a new NF called 5G-CAS. 5G-CAS is a ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1.2 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1.2.1 Registration procedure | Figure 6.1.2.1-1: Retrieval of CAG configuration provisioned in the Serving PLMN
1-4. The same as steps 1, 14a and 14b in clause 4.2.2.2.2 of TS 23.502 [3].
5. The subscription data may contain a flag that suggests the Serving PLMN-specific subscription data needs to be retrieved from 5G CAS.
NOTE: According to inter-o... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1.2.2 Parameter provisioning | Figure 6.1.2.2-1: CAG configuration provisioning to the Serving PLMN
1-4. The same as steps 1,2,5 and 6 in clause 4.15.6.2 of TS 23.502 [3], except for that CAG information is provisioned. The CAG info is provisioned per UE basis.
NOTE 1: Control to allow only an authorized administrator to access NEF relies on the CAP... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1.2.3 Parameter update to UE | This procedure applies when UE has registered and AMF has subscribed to the notification of update of CAG info from 5G CAS during the registration procedure (See steps 10-11 in Figure 6.1.2.1-1).
Figure 6.1.2.3-1: CAG configuration update to UE
1. 5 G CAS sends to AMF a notification of the Serving PLMN-specific subscri... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.1.3 Impacts on services, entities and interfaces | The solution has the following impacts:
5G CAS:
- This stands for 5G CAg subscriber Server. 5G CAS is a new NF that is in the Serving PLMN and stores the Serving PLMN-specific subscription data for both non-roaming UEs and roaming UEs. 5G CAS supports a subset of service operations that UDM supports.
UDM:
- Access and ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.2 Solution #2: CAG provisioning and access control via V-UDR in the visited network | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.2.1 Description | In PNI-NPN, Closed Access Group (CAG) identifies a group of subscribers who are permitted/allowed to access one or more CAG cells of the PLMN identified by CAG ID(s), which is assumed to be reused for 5G Femto access control. A CAG cell is a cell broadcasting one or several CAG IDs. CAG membership of UE is configured i... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.2.2 Procedures | The following figure represents a high-level procedure of the solution.
Figure 6.2.2-1: Call flow for CAG ID(s) provisioning in the visiting network
1: AF creates a request on visited CAG information which may include visited allowed CAG list, GPSI and external location information via AF. Optionally, the request may a... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.2.3 Impacts on services, entities and interfaces | UE:
- receive visited CAG Information from AMF and update internal allowed CAG list,
- provide capability indication to AMF whether it supports visited CAG information.
AMF:
- based on visited CAG allowed list indication, fetch visited CAG Information from UDR (either directly or via UDM) per UE and perform CAG access ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3 Solution #3: Enable provisioning of CAG information from AF via NEF in roaming scenario | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.1 Description | This solution is aimed at KI#2 about how to enable the CAG owner or an authorized administrator to provision/update CAG information to the network for 5G Femto access control. The provisioning/updating of CAG info to the network that 5G Femto serves and the network that the UE has subscription will be considered.
The n... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.2 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.2.1 Procedure for provisioning CAG information to the CMF | Figure 6.3.2.1-1: CAG information provisioning
1. The owner of the 5G Femto establishes a connection with the AF responsible to manage the access to the 5G Femto in order to provide the CAG information which includes the list of UE identifier(s) (i.e. the GPSI) and allowed the list of CAG IDs of Femto cell which the UE... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.2.2 Procedure for visitor UE registration | Figure 6.3.2.2-1: Visitor UE registration procedure
1. The visitor UE of Femto cell intending to connected to a 5G Femto manually selects the CAG cell and attempts the registration.
NOTE: How the UE is aware of the CAG ID to be selected is considered outside the scope of this study.
2. The UE sends a Registration Reque... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.2.3 Procedure for CMF Registration | Figure 6.3.2.3-1: CMF Registration and Update
1. CMF sends Nnrf_NFManagement_NFRegister Request or Nnrf_NFManagement_NFUpdate Request to NRF to inform the NRF of its NF profile. The NF profile of CMF contains NF type, NF instance ID, FQDN or IP address of NF, Names of supported NF services and PLMN ID. The NF profile o... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.2.4 Procedure for CMF discovery | Figure 6.3.2.4-1: CMF discovery procedure
1. The NF service consumer (i.e. AMF or NEF) intends to discover services of CMF. The NF service consumer invokes Nnrf_NFDiscovery_Request from an appropriate configured NRF in the same PLMN. The request includes the CAG ID(s). If the NF consumer is AMF, the request includes th... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.3.3 Impacts on services, entities and interfaces | UE:
- For the UE of visitor, the ability to indicate that it is a visitor UE for CAG cell of 5G NR Femto in the Registration Request.
NOTE: The interactions between the UE and the AF takes place at application layer therefore is outside the scope of this study and this interaction has no impact on the UE.
AF:
- Capabil... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.4 Solution #4: provisioning of subscribers allowed to access CAG cell using CAG subscription update from AF | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.4.1 Description | CAG owner or administrator may provision to 5GC subscribers allowed to access a CAG cell.
In principle provisioning CAG information to UDM is based on the clause 4.2.4.2 of TS 23.502 [3] and provisioning the updated CAG information is based on the clause 4.15.6.2 of TS 23.502 [3]:
- AF (CAG owner or administrator) prov... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.4.2 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.4.2.1 General | The Figure 6.4.2.1-1 shows the procedure for how the AF provision CAG subscriptions allowed to access CAG cell:
Figure 6.4.2.1-1: Procedures for AF to provision CAG subscriptions allowed to access CAG cell
The steps of Figure 6.4.2.1-1 are described as follows:
1. The AF provides UE ID (e.g. SUPI, MSISDN or GPSI), allo... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.4.2.2 AF request redirection | Figure 6.4.2.2-1 shows the procedure for how NEF redirects AF request:
Figure 6.4.2.2-1: Procedure for AF request redirection
The steps of Figure 6.4.2.2-1 are described as follows:
1. AF provides information to NEF in the Serving PLMN as in step 1 of Figure 6.4.2.1-1.
2. When the UE ID is for a roaming UE, NEF sends b... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.4.3 Impacts on services, entities and interfaces | UDM:
- CAG information for UE(s) are provisioned from AF via NEF and notify the result of provisioning to NEF (step 11 of Figure 6.4.2.1-1).
NEF:
- To receive and authorize CAG owner or administrator's input (UE ID, allowed Cell information or CAG information) with assistance of CAPIF and, if required, change them into... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.5 Solution #5: Handover from/to CSG cell to/from CAG cell using mapped CAG/CSG ID | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.5.1 Description | In LTE Femto, Closed Subscriber Group (CSG) identifies a group of subscribers who are permitted/allowed to access one or more CSG cells of the PLMN identified by CSG ID(s). A CSG cell is a cell broadcasting one or several CSG IDs. The CSG membership of a UE is configured in the user subscription data and on the UE. If ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.5.2 Procedures | The following figure represents a high-level procedure of the solution.
Editor's note: How source RAN recognize the CSG/CAG Id of the target 5G(4G) cell based on measurement report containing E-UTRA(NR) measurement IE is FFS.
Figure 6.5.2-1: UE mobility from CAG cell of 5G Femto to 4G CSG cell
0a. 5GS is configured in ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.5.3 Impacts on services, entities and interfaces | UE:
- Receiving CSG-CAG ID partitioning constructing and reporting mapped CSG/CAG ID (depending on the considered mobility direction).
Editor's note: impacts to NGRAN/EUTRAN are FFS. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6 Solution #6: Management-based CAG cell and CSG cell mapping to support interworking | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6.1 Introduction | This solution provides methods to support interworking procedure between CAG cell and CSG cell based on management-based CAG cell and CSG cell mapping i.e. locally configured correlation between CAG information and CSG information. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6.2 Functional Description | The solution is based on the existing mechanism of CAG for PNI-NPN as specified in TS 23.501 [2] with following enhancements:
- The correlation between CAG information and CSG information (including corresponding Home eNB ID) can be configured locally in the AMF that the 5G NR Femto cell is connected to.
- Below tables... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6.3 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6.3.1 HO procedure from 5GS to EPS | The procedure is based on clause 4.11.1.2.1 of TS 23.502 [3] as illustrated in figure 6.6.3.1-1 below.
Figure 6.6.3.1-1: 5GS to EPS handover procedure
The following steps, referring to steps in clause 4.11.1.2.1 of TS 23.502 [3] as base, are enhanced for the CSG ID correlation handling in AMF.
3. Based on the target ID... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6.3.2 HO procedure from EPS to 5GS | The procedure is based on clause 4.11.1.2.2 and TS 23.502 [3] as illustrated in figure 6.6.3.2-1 below.
Figure 6.6.3.2-1: EPS to 5GS Handover procedure, preparation phase
Based on the following text in clause 5.30.3.4 of TS 23.501 [2]. The CAG access control can be enforced by AMF during Registration after the HO. No e... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.6.4 Impacts on services, entities, and interfaces | AMF:
- Support correlation information configuration related to Home eNB ID, CSG ID and CAG information.
- Support formulation of CSG related information towards MME during 5GS to EPS handover.
Editor's note: Whether there is UE impact is FFS. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.7 Solution #7: Reusing the existing mechanism for UE configuration and idle mobility | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.7.1 Description | There are following assumptions for this solution:
- It is assumed that the existing CAG concept defined for PNI-NPN is re-used for Femto access control without impacts to PNI-NPN.
- It is assumed that the UE is configured with Allowed CAG list and Allowed CSG list to access the 5G Femto and 4G Femto network.
In this s... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.7.2 Procedures | There is no new procedure defined |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.7.3 Impacts on services, entities and interfaces | There is no change to the existing mechanism on UE configuration, provisioning and idle mobility. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.8 Solution #8: The connected mode mobility between 4G CSG cell and 5G CAG cell | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.8.1 Description | This solution is to address the connected mode mobility part of KI#1 and propose enhancements to support the UE connected mode mobility between CAG cell of 5G and CSG cell of 4G.
The high level principle/assumption of this solution can be summarized as follows:
- The 4G and 5G interworking architecture with N26 interfa... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.8.2 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.8.3.1 HO from 5GS to EPS | Clause 4.2.2.2.2 of TS 23.502 [3] (General Registration) is re-used with following additional handling.
- In the step 14b, the UDM provides the UE allowed 4G CSG list and 5G CAG list to AMF.
- In step 21, the AMF providers the Mobility restriction list (including allowed CAG and CSG list) to NG-RAN.
Figure 6.8.3.1-1: 5... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.8.3.2 HO from EPS to 5GS | The procedure is same with clause 4.11.1.2.2 of TS 23.502 [3]. There is no enhancement for this procedure. In the existing mechanism:
- In step 10 in clause 4.11.1.2.2.2 (Preparation phase), the NG-RAN has provided supported CAG List of target cell in the Handover Request ACK to the AMF according to clause 9.2.3.5 of T... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.8.3 Impacts on services, entities and interfaces | Editor's note: Because the RAN impact solution is not considered in this SID, the inclusion of this solution in evaluation and conclusion phase is FFS.
UDM:
- There is UE allowed 4G CSG list and 5G CAG list subscription in the UDM/HSS.
- The UDM provides the allowed 4G CSG list and 5G CAG list as subscription data to A... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.9 Solution #9: Solution for mobility between CAG and CSG cells | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.9.1 Description | The solution aims to address the issues described in KI#1 to support mobility between a CAG cell of 5G Femto and a CSG cell of HeNB/EPC.
The solutions assumes the followings:
- The existing CAG concept defined for PNI-NPN is re-used for access control when a UE wants to access a 5G Femto cell without impacts to PNI-NPN... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.9.2 Procedures | Figure 6.9.2-1: Procedures for UE mobility from CSG cell to CAG cell
0. It is assumed that UE has been provisioned with the allowed CAG and CSG list for access to CAG cells of 4G HeNBs and CSG cells of 5G Femto gNBs. The UE is currently attached to a CSG cell and EPC and set up a PDN connection(s).
1. The UE discovers ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.9.3 Impacts on services, entities and interfaces | Editor's note: Because the RAN impact solution is not considered in this SID, the inclusion of this solution in evaluation and conclusion phase is FFS.
UE:
- No impact.
AMF:
- Check CAG list that recieves in the Forward Relocation Request message.
UDM:
- CSG subscription data includes both CSG ID(s) and CAG ID(s) that ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.10 Solution #10: Support of UE move during idle mode mobility | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.10.1 Description | This solution addresses the idle mode mobility from CSG/macro cell of 4G to CAG cell of 5G and CAG/macro cell of 5G to CSG cell of 4G.
For PNI-NPN, the allowed CAG list of the UE can be considered as mostly static as the PNI-NPN would be deployed based on SLAs between the operator and NPN owner. However, for 5G Femto, ... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.10.2 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.10.2.1 5GS to EPS Idle Mode Mobility | Figure 6.10.2.1-1
The proposed procedure is based on the existing steps in clause 4.11.1.2.1 of TS 23.502 [3] with the following differences:
0a. 5GS is configured in a way that the existing CAG ID values are partitioned to reserve CAG IDs with leftmost five bits set to zeros, for supporting mobility from/to a CSG cell... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.10.2.2 EPS to 5GS Idle Mode Mobility | A similar procedure defined for 5GS to EPS Idle Mode Mobility is followed for EPS to 5GS Idle Mode Mobility where CSG and CAG are interchanged in the procedure i.e. UE's allowed CSG list is updated via the existing mechanisms and UE constructed mapped CSG ID from the CAG ID based on the pre-configured CSG/CAG ID encodi... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.10.3 Impacts on services, entities and interfaces | UE:
- Converting between CSG and CSG ID based on CSG/CAG ID encoding information.
- The details of this conversion will be defined by Stage 3.
- Checks mapped CAG ID against the allowed CAG list if the CSG ID is not part of the allowed CSG list. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.11 Solution #11: Handover from/to CSG cell to/from CAG cell based on configuration available at RAN node | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.11.1 Description | This solution addresses the handover from CSG/macro cell of 4G to CAG cell of 5G and CAG/macro cell of 5G to CSG cell of 4G.
In this solution, the handover from/to CSG cell to/from CAG cell of 5G Femto is provided with an assumption that the CAG concept as defined for PNI-NPN is re-used for 5G Femto deployments. This s... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.11.2 Procedures | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.11.2.1 5GS to EPS Handover | The proposed procedure is based on the existing steps in clause 4.11.1.2.1 of TS 23.502 [3] with the following differences:
- In step 1, while NG-RAN node decides that the UE should be handed over to the E-UTRAN, the NG-RAN node uses the pre-configured information on PCI to CSG/CAG ID encoding. The pre-configured infor... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.11.2.2 EPS to 5GS Handover | The proposed solution is to apply same principles as the 5G to 4G solution.
When the CSG to CAG HO is supported, MME is configured to include in the HO Restriction list sent to the eNB the UE Allowed CSG IDs list containing the CSG IDs that are mapped from UE Allowed CAG IDs.
When source eNB receives the PCI from UE, i... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 6.11.3 Impacts on services, entities and interfaces | Editor's note: Because the agreed KI#1 expects that the solutions avoid impacts on RAN and EPC, the inclusion of this solution in evaluation and conclusion phase is FFS.
AMF:
- Includes CSG ID as part of the Forward Relocation Request message towards MME.
NG-RAN:
- Configuration of PCI to HeNB ID and to CSG/CAG ID enco... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 7 Overall Evaluation | Editor's note: This clause provides evaluations of different solutions. |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 7.1 Key Issue #2: Enabling provisioning of subscribers allowed to access CAG cell and managing access control by the CAG owner or an authorized administrator | Solution #1, #2, #3 and #4 are proposed to address Key Issue #2: Enabling provisioning of subscribers allowed to access CAG cell and managing access control by the CAG owner or an authorized administrator.
A comparison of solutions on above aspect is shown in Table 7.1-1.
Table 7.1-1: Comparison of solutions
1
2
3
4
Wh... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 8 Conclusions | |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 8.1 Key Issue #2: Enabling provisioning of subscribers allowed to access CAG cell and managing access control by the CAG owner or an authorized administrator | It is agreed to consider the following principles for the normative work:
- UE impacts shall be avoided.
- In the case of non-roaming:
- The CAG owner or an authorized administrator provides CAG info via NEF.
- The NEF API, i.e. Parameter Provisioning specified in the clause 4.15.6 of TS 23.502 [3] is enhanced to suppo... |
9ae0e8d0cc10f977a17ff6a1c18bb971 | 23.700-45 | 8.2 Key Issue #1: Support of UE move between CAG cell of 5G Femto and CSG cell | It is concluded that: - No normative work will be done in this release. Annex A: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2024-01 SA2#160-Ad Hoc-e S2-2401377 - - - Proposed skeleton agreed for FS_5G_Femto 0.0.0 2024-06 SP#104 SP-240615 - - - MCC editorial update for present... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 1 Scope | The present document describes key issues and solutions for the phase 3 of the system enhancements for Edge Computing in 5GS.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
- Whether and how to support more efficient Edge Hosting Environmen... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 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... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 3 Definitions of terms and abbreviations | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 3.1 Terms | For the purposes of the present document, the terms given in 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 TR 21.905 [1]. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 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 TR 21.905 [1]. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 4 Architectural Assumptions and Principles | Editor’s note: This clause will document any architectural assumptions and principles. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 4.1 Architecture Assumptions | The architecture in this study should be based on the following assumptions:
- The existing architecture and procedures for Edge computing as specified in TS 23.501 [2], TS 23.502 [3], TS 23.503 [4] and TS 23.548 [5] are used as baseline for further potential enhancement;
- Roaming is not considered in this study;
- Th... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 4.2 Architectural Requirements | The solutions should minimize the impact on the application layer if possible. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5 Key Issues | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5.1 Key Issue #1: Enhancements for EAS (re)discovery and UPF (re)selection with reducing impact on central 5GC NFs | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5.1.1 Description | This key issue is to investigate whether and how to reduce impact on central NFs when supporting EAS (re)discovery and UPF (re)selection.
Current Edge Computing design has impact on central 5GC Control Plane NFs. For example, the EAS Deployment Information and local UPF information (deployment information, or load) may... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5.2 Key Issue #2: Enhancement of EAS and local UPF (re)selection | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5.2.1 Description | Normally an edge application can be served by different EASs deployed in different sites. It is important to discover one suitable EAS to handle the edge application, especially considering that mostly the edge application have the stringent E2E delay and/or data rate requirement(s) which may depend not only on network... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5.3 Key Issue #3: EC Traffic Routing between local part of DN and central part of DN | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 5.3.1 Description | In some scenarios, the application traffic may need to be first steered to Edge and processed there. After initial processing, the application traffic may still need to be further forwarded to the Application Server in the central part of DN for further processing. The application traffic may not be able to be routed d... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6 Solutions | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Solutions
Key Issues
1
2
3
#1: Edge computing handling by I-SMF
X
#2: Edge computing handling by local SMF
X
#3: Reducing impact of DNS message handling on central SMF for EAS (re)discovery based on offload to L-SMF
X
#4: Enhanced EC Architecture with SMF selecting local ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.1 Solution #1: Edge computing handling by I-SMF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.1.1 Key Issue mapping | This solution is related to the KI#1. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.1.2 Functional Description | The architecture of this solution is described as Figure 6.1.2-1.
Figure 6.1.2-1: Architecture assumption
In this solution, I-SMF is used to handle the edge computing related traffic to be offloaded into local DN, EDI management, DNS message handling rules configuration or update, and UL CL/BP or L-PSA insertion. There... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.1.3 Procedures | 6.1.3.a I-SMF Insertion Procedure
Figure 6.1.3.a-1: Procedure of I-SMF Insertion
0. I-SMF invoke the SMF service to sends the I-SMF supported DNAI(s) to SMF in Node Level Alternatively, the I-SMF supported the DNAI(s) can be configured in the SMF.
1. Steps 1-10 of Addition of PDU Session Anchor and Branching Point or U... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.1.4 Impacts on existing services, entities and interfaces | I-SMF:
- Handling the edge computing related traffic to be offloaded into local DN, EDI management, DNS message handling rules configuration or update, and UL CL/BP or L-PSA insertion. and control the edge computing handling for ULCL/BP.
- Receiving the policy from PCF;- Receiving EDI for local network directly from NE... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.2 Solution #2: Edge computing handling by local SMF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.2.1 Key Issue mapping | This solution is related to the KI#1. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.2.2 Functional Description | The architecture of this solution is described as Figure 6.2.2-1.
Figure 6.2.2-1: Network Architecture for the L-SMF
In this solution, UL CL/BP controlled by local SMF (L-SMF) can offload edge computing related traffic to local DN. The L-SMF is responsible for EDI management, DNS message handling rules configuration or... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.