hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.6.4 Impacts on existing services, entities and interfaces | No impact to the NFs. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.7 Solution #7: Architecture enhancement to support MWAB-gNB for SNPN | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.7.1 General | This solution addresses the KI#1 and KI#3 if the MWAB connects to an NG-RAN of an SNPN.
Figure 6.7.1-1 presents an example architecture for the MWAB operation when the serving SNPN of the MWAB-UE is the same as subscribed SNPN of MWAB-UE. In this case, there may be two SNPNs involved, i.e. the SNPN 1 that serves the MW... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.7.2 Functional descriptions | Except control of UE's access to MWAB, procedures and enhancement applied to MWAB-UE connecting to an NG-RAN of a PLMN can be also applied to MWAB-UE connecting to an NG-RAN of a SNPN. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.7.3 Control of UE's access to MWAB | In figure 6.7.1-1 and figure 6.7.1-2, if the SNPN 2 only has MWAB-gNB, then a dedicated SNPN ID can be used to control the UE to access the MWAB-gNB.
In figure 6.7.1-1 and figure 6.7.1-2, if the SNPN 2 has both normal gNB and MWAB-gNB with specific time or location, then the MWAB-gNB can be considered as part of SNPN p... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.7.4 Procedures | For the scenario that the SNPN 2 as shown in figure 6.7.1-1 and figure 6.7.1-2 has both normal gNB and MWAB-gNB:
1. If the UE supports accessing an SNPN providing access for Localized Services and the end user enables to access Localized Services, the UE performs the SNPN selection if validity information is met as spe... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.7.5 Impacts on services, entities, and interfaces | None. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8 Solution #8: Provisioning of efficient mobility and service continuity when served by MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.1 Key Issue mapping | This solution addresses Key Issue #4. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.2 Functional Description | This solution proposes to make use of the OAM method to provide efficient mobility and service continuity when served by MWAB.
Regarding the mobility of MWAB, the following aspects are specified:
- The address of the serving PLMN OAM is pre-configured at the MWAB.
- MWAB obtains the MWAB configuration parameters from P... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.3.1 Mechanism upon MWAB mobility | Figure 6.8.3.1-1: OAM method to provide efficient mobility and service continuity when served by MWAB
1. MWAB-UE registers to the network, and if it is authorized to operate as an MWAB-gNB, the flow continues.
2. MWAB communicates with the OAM of the MWAB-gNB, and obtains the MWAB configuration parameters. The MWAB con... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.3.2 Mechanisms upon UE mobility | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.3.2.1 UE mobility between a fixed cell and the MWAB cell | UE mobility between a fixed cell and the MWAB cell can take the current handover procedure using the Xn/N2 reference points as defined in TS 23.502 [7] as the basis.
Editor's note: It is FFS whether the Xn reference points will be used for this scenario and needs RAN coordination.
For UEs in RRC_IDLE and RRC_INACTIVE s... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.3.2.2 UE mobility between MWAB cells | Existing procedures (e.g. defined in TS 38.401 [5], TS 23.502 [7]) can be used to handle the mobility between MWAB cells.
Editor's note: It is FFS whether the Xn reference points will be used for this scenario and needs RAN coordination. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.3.2.3 UE mobility when moving together with the MWAB cell | The TAC broadcasted by the MWAB cell(s) can be configured by the OAM. The TAC to be broadcasted by the MWAB-gNB may change upon its mobility.
For a UE served by a MWAB cell, it may observe change of TAC and/or cell IDs, even if it is still connected to the same MWAB-gNB. This can trigger mobility registrations, as defi... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.8.4 Impacts on existing services, entities and interfaces | MWAB:
- Obtains the MWAB configuration parameters from the OAM via the PDU Session of the MWAB-UE.
- Uses the Cell ID and TAC in the SIB message based on its physical location and received MWAB configuration parameters.
- Manages (e.g. establishes, updates, releases) the NGAP connection with the AMF(s) as per the MWAB ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9 Solution #9: UE mobility handling due to MWAB mobility | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.1 Introduction | This solution addresses issues related to KI#4. It provides methods to support UE mobility handling in combination with the MWAB node mobility. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.2 Functional Description | When the MWAB node moves nationally and internationally, the MWAB-gNB and MWAB-UE may be connected to different networks e.g. MWAB-UE may select PLMN A to register and establish PDU sessions for backhaul communication, while the MWAB-gNB may broadcast/serve a different PLMN B and be connected to the 5GC of the broadcas... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.2.1 MWAB mobility | When MWAB node moves nationally, the MWAB-UE selects either its HPLMN to register or another PLMN to register when there is no HPLMN coverage. The MWAB-gNB connects to the core network based on configuration (e.g. the HPLMN of the MWAB-UE).
When MWAB node moves internationally, it is assumed that based on current regul... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.2.2 UE mobility | When MWAB node moves, the mobility for the UEs that are registered to network via the MWAB is handled in two different and separate ways:
- The UEs do not move together with the MWAB cell (i.e. UE moves away from MWAB) and will be served by other cells.
- The UEs moves together with the MWAB cell and continue to be ser... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.2.2.1 UEs moves away from MWAB node | For the UEs that do not move together with MWAB node and are in IDLE mode or in RRC_INACTIVE state, the UEs perform cell (re-)selection as normal based on TS 23.122 [9] and camp on other cells. For the UEs in CONNECTED mode, the MWAB-gNB applies the existing mobility methods of normal gNB to transfer the UEs to other c... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.2.2.2 UEs moves together with MWAB node | For the UEs that move together with the MWAB node and therefore continue to connect to cells configured on MWAB-gNB, there are 3 different types of scenarios:
- The MWAB-gNB remains connected/served by the same AMF as it moves (scenarios A, B and C above in clause 6.9.2.1).
- The MWAB-gNB needs to be connected/served b... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.2.3 Impact on BH connections | There are two possible scenarios that can be considered: the BH connection is retained as the MWAB-UE moves, meaning that the same UPF is kept. In this case the IP address of the MWAB-gNB remains unchanged, hence there is no impact on the BH connection as such.
If however the BH-UPF changes, SSC mode 3 could be benefic... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.3.1 Impact on UEs served by a MWAB upon mobility of MWAB or mobility of UE with respect to the MWAB | Existing IDLE mode, RRC_INACTIVE state and CONNECTED mode mobility procedures and existing cell reselection procedures specified in TS 23.122 [9]. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.3.2 Impact on the network when UEs moves together with MWAB node in the same PLMN | For the scenarios A, B, C (i.e. no UE AMF change) described in clause 6.9.2.1. it is assumed there is no need to change the MWAB-gNB's gNB ID as there is no change of AMF upon mobility, which can be supported by keeping the same gNB, so the UE is assumed to keep the same AMF and gNB. If there is no new TAC/Cell ID adve... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.3.3 UEs move together with MWAB node to different PLMN | For scenario F (i.e. the AMF, that MWAB-gNB connects to, changes in different PLMNs) when MWAB moves, the MWAB-UE needs to establish a BH connection and the MWAB-gNB connects to AMFs in the new PLMN. The issue now is that we need simultaneous registrations in two PLMNs with one credentials (the MWAB-UE credential) to p... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.9.4 Impacts on services, entities, and interfaces | MWAB:
- Support multiple instances of MWAB-gNB as outlined above.
- Handle UE mobility as outlined above.
- Interact with OAM server as outlined above.
- Rearrange NG connection as needed upon change of UPF.
- Support the UE mobility procedures for UE in CONNECTED mode in case of different or same TAC/Cell ID.
OAM:
- R... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10 Solution #10: New solution to address mobility aspects of an MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.1 General | This solution addresses the below highlighted aspects for Key Issue#4 defined as:
When the moving vehicles are equipped with MWAB, the MWAB-gNB can provide 5G coverage and communication to UEs (inside the vehicle and/or in its vicinity) and connected wirelessly to the 5G network via a macro NG-RAN node. When one or a g... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.2 Functional descriptions | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.2.1 Solution for mobility aspects related to Scenario A (mobility within the same 5GC node) | Figure 6.10.2.1 covers mobility of MWAB nodes between different gNBs but the 5GC nodes serving the UEs doesn't change in this scenario. MWAB-UE's backhaul PDU session is established via gNB1 terminating at MWAB-UPF which is the PDU Session Anchor for MWAB-UE. As the MWAB moves, signal strength received at MWAB-UE from ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.2.2 Solution for mobility aspects related to Scenario B (mobility between different 5GC nodes) | Figure 6.10.2.2 covers mobility aspects between different 5GC nodes, for the UEs being served by an MWAB. For the MWABs moving over a long distance, there are 2 stages of handover, first being the handover between different NG-RAN nodes serving the MWAB and second, the handover of UEs between different 5GC nodes. As di... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.3 Mobility between different 5GC nodes, when UEs are served by MWAB | Figure 6.10.3.1 covers the mobility procedure between different 5GC nodes when UEs are served by MWAB traveling over a long distance.
Figure 6.10.3.1: Mobility between different 5GC nodes, for UEs served by MWAB
1. MWAB can provide regular updates about MWAB-UE location (it indicates MWAB's location) to the source AMF ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.4 Handover of MWAB-UE | Editor's note: Mobility of MWAB-UE including the scenario of AMF change for MWAB-UE due to its mobility is FFS. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.10.5 Impacts on services, entities, and interfaces | Impacts on existing entities:
AMF:
- Support relevant message exchange and functionality for handling the handover procedure.
Functions required at new entities:
MWAB:
- Support relevant message exchange for handling the handover procedure. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11 Solution #11: Location services involving MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.1 General | This solution addresses KI#5 and proposes to reuse the location functionality specified for MBSR in Rel-18. According to clause 4.1, the MWAB-UE may be served by different PLMN than the UE connected to the MWAB-gNB. The N2 reference point between the MWAB-gNB and the AMF serving the UE is provided by IP connectivity ad... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.2 Functional descriptions | A MWAB may have location service capability as specified in TS 38.305 [11] and participate in the location service of a UE. As the MWAB may be moving, the location service procedures need to be enhanced as following for an accurate estimation of the UE positioning:
- The UE reports the cell-IDs of all the cells the UE ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.3.1 5GC-MT-LR procedure involving MWAB (same PLMN) | The 5GC-MT-LR procedure involving MWAB when the UE and MWAB-UE is served by the same PLMN is shown in Figure 6.11.3.1-1.
Figure 6.11.3.1-1: 5GC-MT-LR procedure involving MWAB (same PLMN)
The differences with the 5GC-MT-LR procedure involving Mobile Base Station Relay procedure in clause 6.1.4 in TS 23.273 [6] are that ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.3.2 5GC-MT-LR procedure involving MWAB (roaming to same PLMN) | If the MWAB-UE is roaming to a VPLMN and the MWAB-gNB operates as a gNB in the VPLMN (i.e. MWAB-UE and MWAB-gNB are, respectively, registered and connected to the same PLMN), then the procedure in clause 6.11.3.1 can be used with the following difference.
- After the (H)GMLC received the LCS Service Request from the LC... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.3.3 5GC-MT-LR procedure involving MWAB (different PLMN) | If the MWAB-UE is served by PLMN 1 as shown in figure 6.1.1-1 and the MWAB-gNB operates as a gNB in PLMN 2 as shown in figure 6.1.1-1 i.e. MWAB-UE and MWAB-gNB are, respectively, registered and connected to the different PLMNs, then the procedure in 6.11.3.1 can be used with the following difference.
- Step 3 When the ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.3.4 5GC-MO-LR Procedure involving MWAB (non-roaming and roaming to same PLMN) | This procedure is based on clause 6.2 of TS 23.273 [6] as illustrated in figure 6.11.3.4-1 below. The procedure support both the non-roaming case and when the MWAB-UE is roaming to a VPLMN and the MWAB-gNB operates as a gNB in the VPLMN(i.e. MWAB-UE and MWAB-gNB are, respectively, registered and connected to the same P... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.3.5 5GC-MO-LR Procedure involving MWAB (different PLMN) | If the MWAB-UE is served by PLMN 1 as shown in figure 6.1.1-1 and the MWAB-gNB operates as a gNB in PLMN 2 as shown in figure 6.1.1-1 i.e. MWAB-UE and MWAB-gNB are, respectively, registered and connected to the different PLMNs, then the procedure in clause 6.11.3.4 can be used with the following difference.
- Step 5 Wh... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.11.4 Impacts on services, entities, and interfaces | UE:
- No impact.
AMF:
- No impact.
LMF:
- Manage a list of which cell-ID(s) corresponds to a TRP(s) of MWAB-gNB(s).
- When performing location estimate apply same method when a MWAB is involved as when a MBSR is involved.
GMLC:
- No impact.
NRPPa:
- No impact, same TRP information Type is set to 'mobile trp location ty... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.12 Solution #12: support of Emergency services for UEs via a MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.12.1 Key Issue mapping | This solution addresses Key Issue #6. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.12.2 Functional Description | This solution proposes to support the following features regarding emergency services when the UE connecting to MWAB:
- Report the Cell ID/TAC that the UE is currently located when the target UE is connected to MWAB and is in CM-CONNECTED state. It is essentially meaningless to reporting the Cell ID/TAC of the MWAB-UE ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.12.3 Procedures | With extrapolation of the features defined in TS 23.501 [2] to emergency service and Rel-18 MBSR, the following is defined:
- Report the Cell ID/TAC that the UE is currently located when the target UE is connected to MWAB and is in CM-CONNECTED state.
NOTE 1: Timely update the Cell ID/TAC broadcasted by the MWAB-gNB as... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.12.4 Impacts on existing services, entities and interfaces | Impacts of the Network Entities as per the solution of KI#2, KI#4 and KI#5. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.13 Solution #13: Support of emergency calls in MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.13.1 General | This solution addresses Key Issue #6: Support of Emergency services for UEs via a MWAB. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.13.2 Functional descriptions | The solution proposes that the MWAB establishes a dedicated BH PDU session for emergency when an emergency session is ongoing, using the S-NSSAI and a DNN reserved for emergency sessions backhaul support. These are configured in the MWAB-gNB and AMF of the PLMN the MWAB-gNB broadcasts the PLMN ID of.
The BH PDU session... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.13.3 Procedures | This clause provides high level view of the type of impact expected by this solution.
UE places emergency call from CM-IDLE
Figure 6.13.3-1: Emergency BH PDU session establishment for a UE which was CM-IDLE
0. AMF serving MWABs is configured by OAM with S-NSSAI and DNN value for BH PDU session for emergency support.
1.... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.13.4 Impacts on services, entities, and interfaces | MWAB:
- Support the establishment and maintenance of the BH PDU session for emergency as outlined above.
OAM:
- configuration of S-NSSAI, DNN for BH PDU session for emergency at MWAB-gNB and AMF supporting MWAB UEs handling.
AMF:
- support of BH PDU session for emergency configuration data. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.14 Solution #14: Graceful release of emergency services. | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.14.1 Description | 1) When AMF decides to deregister the UE for e.g. because of notification from UDM, and if it finds the emergency PDU session is active for the UE, then AMF sends UE configuration command message and indicates registered for emergency services (see TS 24.501 [14]and TS 23.502 [7]). The AMF meanwhile initiates for relea... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.14.2 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.12.2.1 Procedure for graceful release of serving UEs when MWAB-UE is having active emergency PDU session | Figure 6.14.2.1-1: Graceful release of serving UEs when MWAB-UE is having active emergency PDU session
1. MWAB-UE is authorized for MWAB operations.
2. MWAB-UE is having an emergency PDU session.
3. UDM triggers Deregistration notification for MWAB-UE.
4. The AMF will first inform MWAB-UE that it should be registered f... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.14.2.2 Procedure for graceful release of serving UEs when they have active emergency PDU session | Figure 6.14.2.2-1: Graceful release of serving UEs when they have active emergency PDU session
1. MWAB-UE is authorized for MWAB operations.
2. MWAB-UE is having an emergency PDU session.
3. UDM triggers deregistration notification for MWAB-UE.
4. The AMF will first inform MWAB-UE that it is unauthorized for MWAB opera... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.14.3 Impacts on services, entities and interfaces | This solution impacts the following system entities.
AMF:
- Before sending UCU with registered for emergency services, the AMF should indicate to MWAB-UE that it is unauthorized for MWAB operations. So that it can gracefully stop MWAB operations and later the non-emergency PDU sessions are released.
- If MWAB-UE indica... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15 Solution #15: Protocol Stacks of backhaul link to support the N2/N3 interface for MWAB node | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15.1 General | This solution is for Key Issue #1, which addresses the protocol stacks of the backhaul link using a PDU session to support the N2/N3 interfaces for a MWAB node. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15.2 Description | Based on the Non-Roaming MWAB architecture for 5GS in Figure 4.1-1, BH PDU sessions are established between MWAB-UE and UPF for MWAB-UE (i.e. MWAB-UE-UPF) within BH-5GC to transfer N2/N3 signalling/data, where N2 interface is between MWAB-gNB and AMF within 5GC serving UE and N3 interface is between MWAB-gNB and UPF fo... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15.3.1 Protocol Stacks of backhaul link to support the N2 interface for MWAB node | Figure 6.15.3.1-1 illustrates Protocol Stacks of backhaul link to support the N2 interface for MWAB node. MWAB-UE connects to BH gNB. A PDU session between MWAB-UE and MWAB-UE-UPF is established as a backhaul link to support the overlayed N2 interface. The N2 interface terminates at MWAB-gNB and AMF respectively, which... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15.3.2 Protocol Stacks backhaul link to support the N3 interface for MWAB node | Figure 6.15.3.2-1 illustrates Protocol Stacks backhaul link to support the N3 interface for MWAB node. A PDU session between MWAB-UE and MWAB-UE-UPF is established as a backhaul link to support the overlayed N3 interface. The N3 interface terminates at MWAB-gNB and UE-UPF respectively, which includes GTP-U and UDP/IP l... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.15.4 Impacts on services, entities and interfaces | The impacts will be captured in the related procedures of establishing the backhaul links to support N2/N3 interface. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.16 Solution #16: Support for multiple backhaul PDU sessions | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.16.1 Introduction | This solution addresses how backhaul PDU sessions can be established by the MWAB-UE and how MWAB-gNB can utilise different BH PDU sessions for different traffic types of the MWAB-gNB and the UEs connected via the MWAB-gNB. It provides methods to support traffic categorization for MWAB. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.16.2 Functional Description | A MWAB node includes an MWAB-gNB function and an MWAB-UE function as described in clause 4. The MWAB-gNB part further provides access connectivity to the UEs.
There are different types of traffic will be transmitted from MWAB-gNB. The traffic can be categorized in different ways. One example is shown below:
- RAN-CN N2... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.16.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.16.3.1 Triggering of PDU session establishment or modification | This procedure describes the MWAB node authorization steps and the operations with focus on the 5GC aspects.
Figure 6.16.3.1-1: MWAB node authorization and operation initiation
1. The MWAB-UE triggers registration and becomes authorized to operate as MWAB.
2. Based on different traffic types that are transmitted by the... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.16.4 Impacts on services, entities, and interfaces | None. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 7 Evaluation | Editor's note: This clause provides the evaluations of the solutions of clause 6. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8 Conclusions | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8.1 KI#1: Architectural enhancements for the support of a MWAB Conclusion | The system architectures as shown in Figure 6.1.1-1 to 6.1.1-3 are agreed to be used as the basis for normative work for the cases where PLMNs are involved. Following additional aspects to be addressed in normative phase:
- Naming of the entities, e.g. MWAB-UE UDM vs. HPLMN UDM;
- Clarifications that the MWAB's HPLMN a... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8.2 KI#2: Authorization of a MWAB and configuration of MWAB Conclusion | It is proposed to proceed normatively based on these principles:
- MWAB-UE authorization and MWAB-gNB service authorization are two different authorizations and managed by different entities in the networks. The BH PLMN 5GC controls the first based on MWAB-UE subscription; and the OAM the MWAB-gNB connects to controls ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8.3 KI#3: Control of UE's access to 5GS via a wireless access backhaul Conclusion | The following principles are agreed to be used as the basis for normative work:
- The existing CAG mechanism (as defined in Rel-18 for MBSR) can be used as an optional method for managing UE's access to MWAB-gNB, for PNI-NPN deployment cases.
- Existing SNPN control mechanism can be used to manage the UE's access to MW... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8.4 KI#4: Efficient mobility and service continuity when served by MWAB Conclusion | The following principles are agreed to be used as the basis for normative work:
- There is no requirement to change the UE mobility behaviour for UEs served by a MWAB-gNB.
- MWAB-gNB's configurations (e.g. Cell ID/TAC, AMF address, etc.) are managed by OAM of the PLMN it serves, based on the location information of the... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8.5 KI#5: Support of location services for UEs when MWAB(s) is involved Conclusion | The following aspects are taken as way forward during normative work:
- Existing principles (e.g. the two options for LMF to retrieve the MWAB location either via NRPPa procedure or via GMLC) are re-used for UE location service when MWAB is involved as described in sol#11.
- The MWAB-gNB provides to the AMF an Addition... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 8.6 KI#6: Support of Emergency services for UEs via a MWAB Conclusion | The following principles are agreed for emergency service support in normative work: - Emergency services can be supported by MWAB based on the configuration of OAM. - Some dedicated BH PDU sessions (with specific S-NSSAI and DNN) may be established by MWAB-UE when the MWAB-gNB serves an emergency session. The S-NSSAI ... |
8da6a57d299293554265ff03968895f2 | 28.536 | 1 Scope
| The present document describes the management services for communication service assurance and specifies stage 2 and stage 3 for closed control loop communication service assurance solution that adjusts and optimizes the services provided by NG-RAN and 5GC.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 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.
-... |
8da6a57d299293554265ff03968895f2 | 28.536 | 3 Definitions of terms, symbols and abbreviations
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 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].
|
8da6a57d299293554265ff03968895f2 | 28.536 | 3.2 Symbols
| Void.
|
8da6a57d299293554265ff03968895f2 | 28.536 | 3.3 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].
COSLA Closed control loop SLS Assurance
CSC Communication Service Custome... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4 Communication service assurance service
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1 Stage 2
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.1 Void
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2 Model
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.1 Imported and associated information entities
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.1.1 Imported information entities and local labels
|
Label reference
Local label
TS 28.622 [5], IOC, Top
Top
|
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.1.2 Associated information entities and local labels
|
Label reference
Local label
TS 28.622 [5], IOC, SubNetwork
SubNetwork
TS 28.541 [6], IOC, NetWorkSlice
NetworkSlice
TS 28.541 [6], IOC, NetWorkSliceSubnet
NetworkSliceSubnet
TS 28.622 [5], IOC, ManagedElement
ManagedElement
TS 28.541 [6], attribute, serviceProfileId
serviceProfileId
TS 28.541 [6], attrib... |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.2 Class diagram
| |
8da6a57d299293554265ff03968895f2 | 28.536 | 4.1.2.2.1 Relationships
| This clause depicts the set of classes that encapsulates the information relevant for this MnS. This clause provides an overview of the relationships between relevant classes in UML. This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specifica... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.