hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7 Solution #7: 5G ProSe Multi-hop Layer-3 UE-to-Network Relay Communication with and without N3IWF support | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.1 Description | This solution addressed Key Issue #1 "Support of Multi-hop UE-to-Network Relays".
In this solution, the ProSe 5G UE-to-Network Relay operations are supported with the following principles:
- 5G ProSe multi-hop UE-to-Network Relay discovery with Model B:
- The Remote UE decides the maximum number of hops for discovery b... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2.1 5G ProSe multi-hop UE-to-Network Relay Discovery | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2.1.1 5G ProSe multi-hop UE-to-Network Relay Discovery with Model B | Figure 6.7.2.1.1-1: General procedures for 5G ProSe multi-hop UE-to-Network Relay Discovery with Model B
1. The 5G ProSe Remote UE decides the maximum number of hops for discovery based on e.g. according to QoS requirement or (pre-)configuration.
2a. The 5G ProSe Remote UE sends a 5G ProSe UE-to-Network Relay Discovery... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2.1.2 5G ProSe multi-hop UE-to-Network Relay Discovery with Model A | Figure 6.7.2.1.2-1: General procedures for 5G ProSe multi-hop UE-to-Network Relay Discovery with Model A
1. The UE-to-Network Relay decides the maximum number of hops for discovery based on (pre-)configuration, e.g. according to some mapping to the RSC.
2a. The 5G ProSe UE-to-Network Relay sends a UE-to-Network Relay D... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2.2 5G ProSe Communication via multi-hop 5G ProSe Layer-3 UE-to-Network Relay without N3IWF support | Figure 6.7.2.2-1: QoS control for Layer 3 UE-to-Network Relay operation
1. Service authorization and provisioning are performed for the 5G ProSe Layer-3 UE-to-Network Relay, Intermediate Relay(s) and 5G ProSe Layer-3 Remote UE.
2. The 5G ProSe Layer-3 UE-to-Network Relay may establish a PDU Session for relaying.
3. The... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2.3 QoS handling for 5G ProSe Multi-hop UE-to-Network Relay without N3IWF | Figure 6.7.2.3-1: QoS control for Layer 3 UE-to-Network Relay operation
If the 5G ProSe Layer-3 Remote UE initiates PC5 QoS Flows setup or modification during the Layer-2 link establishment or modification procedure:
1. The 5G ProSe Layer-3 Remote UE provides the QoS Info to the first Intermediate Relay.
2-3. The Inter... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.7.2.4 5G ProSe Communication via multi-hop 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support | Figure 6.7.2.4-1 and Figure 6.7.2.4-2 show the user plane protocol stack and the control plane protocol stack, respectively, for 5G ProSe Communication via multi-hop 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support.
Figure 6.7.2.4-1: User plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.8 Solution #8: Layer-3 multi-hop UE-to-Network Relay building on top of Solution #3 | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.8.1 Description | Solution #3 in TR 23.700-33 [3] describes how a MANET cloud of interconnected U2U Relays can be used for ad hoc interconnection of End UEs.
The salient features of Solution #3 that are relevant for the description of the U2N Relay solution of this clause are the following:
- There is a MANET cloud of interconnected U2U... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.8.2 Procedures | The only new procedure on top of those described in Solution #3 is the establishment of the iPsec tunnel. |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.8.3 Impacts on services, entities and interfaces | This clause lists the additional impacts on End UE on top of those listed in Solution #3.
5G ProSe End UE operating as Remote UE:
- Uses FQDN including the RSC of the desired U2N Relay service and formatted according to 3GPP-defined rules in order to obtain the IP address (on MANET side) of the End UE serving as U2N Re... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9 Solution#9 for Key Issue #2 | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9.1 Description | The solution applies for multi-hop UE-to-UE Relay discovery, communication and QoS handling.
The idea of this solution is shortest path discovery. Among the possible paths consisted of multiple Relay UEs between the discoverer End UE and discoveree End UE, the one firstly completing delivery of the Discovery message is... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9.2.1 Multi-hop UE-to-UE Relay discovery with Model B | Figure 6.9.2.1-1: Multi-hop UE-to-UE Relay Discovery with Model B
1. The discoverer 5G ProSe End UE (UE-1) sends a multi-hop UE-to-UE Relay Discovery Solicitation message. The multi-hop UE-to-UE Relay Discovery Solicitation message contains the Type of Discovery Message, User Info ID of itself, RSC, User Info ID of the... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9.2.2 Layer-2 link establishment communication via multi-hop UE-to-UE Relays | The general procedure is based on Layer-2 link establishment via 5G ProSe UE-to-UE Relay as described in clause 6.7.1 of TS 23.304 [4], with additional treatment for communication via multi-hop UE-to-UE Relays.
Figure 6.9.2.2 describes the general procedures of the solution.
Figure 6.9.2.2: General procedures for Layer... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9.2.3 QoS handling for multi-hop UE-to-UE Relays | Figure 6.9.2.3 describes the general procedure for QoS handling.
Figure 6.9.2.3: QoS handling for multi-hop UE-to-UE Relays
0. UE-to-UE Relay is provisioned with policy parameters from the network as described in clause 5.1.5 of TS 23.304 [4] and UE-to-UE Relay discovery has been completed as described in clause 6.9.2.... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.9.3 Impacts to Services, Entities and Interfaces | The following impacts are foreseen by this solution:
UE:
- Each UE can determine the multi-hop Relay route/path to the other End UE based on rule of shortest path discovery and send subsequent message based on stored routing information.
- Each Relay UE can calculate and transfer the accumulated QoS parameters (e.g. PD... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.10 Solution #10: Support for Multi-hop UE-to-UE Relay Discovery with max hop restriction | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.10.1 Description | This solution aims to propose Multi-hop UE-to-UE Relay Discovery with Model A to resolve the key Issue #2 Support of Layer-3 multi-hop UE-to-UE Relays. 5G ProSe UE-to-UE Relay Discovery with Model A and Model B are reused as baseline to support for multi-hop 5G ProSe UE-to-UE Relay Discovery Model A and Model B
For 5G ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.10.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.10.2.1 Multi-hop 5G ProSe UE-to-UE Relay Discovery with Model A | Figure 6.10.2.1-1: Multi-hop 5G ProSe UE-to-UE Relay Discovery with Model A
0. Source End UE, UE-to-UE Relay-1, UE-to-UE Relay-3 and UE-to-UE Relay-2 are provisioned with service authorization/parameters from PCF to support multiple hops UE-to-UE Relay.
1. The 5G ProSe UE-to-UE Relay-3 has a target list of other End UE... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.10.2.2 Multi-hop 5G ProSe UE-to-UE Relay Discovery with Model B | Figure 6.10.2.2.-1: 5G ProSe UE-to-UE Relay Discovery with Model B for supporting multiple-hops
0. UE1, UE2, U2U Relay-1 and U2U Relay-2 are provisioned with service authorization/parameters from PCF to support multiple hops.
1. The discoverer 5G ProSe End UE (UE-1) sends a 5G ProSe UE-to-UE Relay Discovery Solicitatio... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.10.3 Impacts on services, entities and interfaces | Editor's note: It is FFS to capture impacts on existing 3GPP nodes and functional elements. |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 7 Overall Evaluation | Editor's note: This clause will provide evaluation of different solutions. |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 8 Conclusions | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 8.1 Conclusions for KI#1 | The following principles are used for normative work:
- 5G ProSe Multi-hop Layer-3 UE-to-Network Relay Communication with N3IWF support:
- The 5G ProSe Layer Remote UE connects to the N3IWF over 5G ProSe Layer-3 Intermediate Relay and Layer-3 UE-to-Network Relay.
- The 5G ProSe Layer-3 Intermediate Relay neither select... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 8.2 Conclusions for KI#2 | The following principles are used for normative work: For PDU type IP: Support of Layer-3 multi-hop UE-to-UE Relay to normative phase is based on solution #3 and #4, with the following reasoning: - They are based on an existing MANET protocol (IETF RFC 7181 [9]) which is a proven mobile ad-hoc routing protocol. - The m... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 1 Scope | The scope of this Technical Report is to study and identify potential architecture and system level enhancements for the 5G system to support the operation of a mobile gNB mounted on vehicles, using NR for wireless access toward the UE and for wireless backhaul access toward the 5GC. The study addresses the service req... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 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... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 3 Definitions of terms and abbreviations | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1], TS 23.501 [2] 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].
mobile gNB with wireless access backhaul: A mobile base station acts as a gNB for oth... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 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] and TS 23.501 [2].
MWAB Mobile gNB with wireless access backhauling
MWAB-gNB... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 4 Architecture assumptions and requirements | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 4.1 Architecture assumptions | The study should be based on the following architecture assumptions:
- the MWAB consists of a gNB component (MWAB-gNB) and a UE component (MWAB-UE);
- the MWAB-gNB is based on the gNB functionality specified in TS 38.300 [4] and TS 38.401 [5];
NOTE 1: Architecture impact on MWAB-gNB may depend on the RAN study output a... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 4.2 Architecture requirements | Solutions of the study should provide architecture and system level enhancements to the 5G system to support the operation of MWAB to satisfy the normative requirements of a mobile base station relay specified in TS 22.261 [3]. Specifically:
- a MWAB shall be capable to serve legacy UE(s) to connect via MWAB;
- support... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5 Key Issues | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.1 Key Issue #1: Architectural enhancements for the support of a MWAB | This Key issue addresses architectural enhancements required to support the MWAB connects to the 5GC with the use of wireless backhauling (for the N2/N3 interfaces) via IP connectivity provided by a PDU session.
This will include:
- Whether and how the MWAB provides service for UEs from the HPLMN and UEs from other PLM... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.2 Key Issue #2: Authorization of a MWAB and configuration of MWAB | A MWAB that operates in a PLMN by using the wireless access backhaul and serving UEs in proximity, is subject to authorization, with the additional support of the HPLMN of the MWAB in case of roaming. In addition, configuration of the MWAB (both the MWAB-gNB and MWAB-UE) for the MWAB operation needs to be studied.
This... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.3 Key Issue #3: Control of UE's access to 5GS via a wireless access backhaul | This key issue is to investigate efficient control of UE access to MWAB. In particular, the following aspects should be addressed:
- Whether and how to enhance the existing CAG mechanism to control and manage the access of a UE via MWAB.
NOTE 1: Support of legacy UE(s) shall be considered.
NOTE 2: Aspects related to RA... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.4 Key Issue #4: Efficient mobility and service continuity when served by MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.4.1 General description | 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 group of UEs are already served by the MWAB, there are two mobility scenarios to b... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.5 Key Issue #5: Support of location services for UEs when MWAB(s) is involved | Based on the requirements of TS 22.261 [3], the 5G system shall be able to support location services for the UEs accessing 5GS via a mobile base station relay. When a UE is served by a MWAB, the MWAB's movement may affect not only positioning procedures but also regulatory services needing UE location. MWAB(s) not serv... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 5.6 Key Issue #6: Support of Emergency services for UEs via a MWAB | Based on the requirements of TS 22.261 [3], the 5G system shall be able to support emergency service for the UEs accessing 5GS via a mobile base station relay. Therefore, this key issue needs to address:
- Whether any enhancements are needed to support emergency service (including graceful release) for the UEs accessin... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6 Solutions | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.0 Mapping of solutions to key issues | Editor's note: This clause describes the mapping between solutions and key issues.
Table 6.0-1: Mapping of solutions to key issues
Key Issues
Solutions
1
2
3
4
5
6
1
X
X
X
X
X
2
X
3
X
4
X
5
X
6
X
7
X
X
8
X
9
X
10
X
11
X
12
X
13
X
14
X
15
X
16
X |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1 Solution #1: Architecture enhancements to support MWAB operations | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.1 General | Figure 6.1.1-1 presents an example architecture for the MWAB operation when no roaming was involved for the MWAB-UE. In this case, there may be two PLMNs involved, i.e. the PLMN 1 that serves the MWAB-UE, and the PLMN 2 that serves the UE connected to the MWAB.
In this case, the MWAB-gNB logically belongs to PLMN 2, an... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.2 Functional descriptions | The MWAB operates as follows to provide service to a UE:
1. To operate as a MWAB, the MWAB-UE needs to first register to a serving network that is allowed by its subscription, and that is PLMN 1 in the architecture shown in clause 6.1.1. The serving PLMN authorizes the MWAB based on its subscription and provides the au... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.3.1 MWAB-UE registration and authorization | The MWAB-UE performs PLMN selection based on existing procedures in TS 23.122 [9].
MWAB-UE also follows existing procedures in TS 23.501 [2], for network slice configuration. The serving PLMN accesses the HPLMN of the MWAB-UE for the subscription data.
The MWAB-UE may be triggered by the MWAB-gNB to establish the PDU s... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.3.2 Control of UE's access to MWAB | Legacy UE can access the MWAB-gNB as a normal gNB.
For CAG capable UEs, the enhancement as described in clause 5.35A.7 of TS 23.501 [2] can be reused for control the access to the MWAB, if the MWAB is configured by OAM of PLMN 2 to broadcast CAGs.
Editor's note: It is FFS whether enhancements is needed to prevent the M... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.3.3 Support of Location Service for UEs when MWAB(s) is involved | A separate solution compatible with the architecture introduced in this solution will be used to support the Location Service, based on the principles defined in clause 5.35A.5 of TS 23.501 [2].
Editor's note: It is FFS if further enhancements is needed to use the NRPPa procedures with MWAB in the roaming cases. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.3.4 UE mobility to and from a MWAB cell | Existing UE mobility procedure can be reused. No enhancement is required, based on the same considerations as described in clauses 5.35A.3.1 and 5.35A.3.2 of TS 23.501 [2]. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.1.4 Impacts on services, entities, and interfaces | None.
Editor's note: Related procedures can be eventually documented in an informative annex of TS 23.501 [2]. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2 Solution #2: MWAB architecture and procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.1 General | The solution provides methods for architectural enhancements for the support of a MWAB, which is based on the support of MWAB architecture as specified in clause 4.1 with the following high-level descriptions according to the different usages of PDU sessions(s) of the MWAB-UE:
- Connection with OAM server over IP conne... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.2 Functional descriptions | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.2.1 Connection with OAM server over PDU session | When a PDU session is used for the MWAB to access the OAM server, the MWAB-UE establishes a dedicated PDU session for the OAM traffic. Additionally, the OAM server address can be configured per PLMN ID, the MWAB selects the OAM server address of the respective PLMN ID for which it wants to act as NG-RAN.
The MWAB-UE is... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.2.2 N2 connection over BH PDU session | The N2 connection with AMF for the MWAB-gNB:
- The BH PDU session's PSA routes the N2 message between the MWAB-gNB and AMF based on the IP address.
- The N2 connection with AMF set over BH PDU session is described in the Figure 6.2.2.2-1.
- The MWAB-UE is configured with dedicated DNN/S-NSSAI for the PDU session for ba... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.2.3 N3 over BH PDU session | Editor's note: Detailed description is FFS. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.2.4 Xn over BH PDU session | The MWAB-gNB's Xn, if enabled based on configuration by OAM, may share the same PDU session of N2/N3 or different PDU session. When the respective PDU session providing IP connectivity is established, IP connectivity is also used to connect with another NG-RAN (using the Xn interface).
Editor's note: It is FFS whether ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.2.5 Handling of NG establishment with respect to the topic of multi-hop handling | Editor's note: Whether and how to avoid multi-hop handing needs to coordination with RAN WG3.
The MWAB need to avoid multi-hop (until RAN WGs agree otherwise). A solution is provided to ensure this is possible without requiring new impacts on MWAB-UE and the deployed NG-RAN (except in the event of Xn handover).
The MWA... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.1 Connection with OAM server over PDU session | The MWAB-UE may be configured dedicated DNN/S-NSSAI for the PDU session for backhaul link to the OAM server (e.g. Local Configuration or URSP rules) or network serving the MWAB-UE may determine a default DNN/S-NSSAI for it based on subscription. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.2 N2 connection over BH PDU session | The N2 message routing over BH PDU session is described in the Figure 6.2.3.2-1.
Figure 6.2.3.2-1: N2 message routing over BH PDU session
1 When MWAB-UE establishes the PDU session to access the OAM server, the address(es) of the AMF(s) for the MWAB-gNB to connect to can be configured by the OAM based on MWAB's locatio... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.3 N3 connection over BH PDU session | Editor's note: Detailed description is FFS. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.4 Xn connection over BH PDU session | Similar to the N3 connection over BH PDU session, the Xn connection is the user plane which routes the traffic from MWAB-gNB to another NG-RAN. The Xn message routing over BH PDU session is similar as the Figure 6.2.3.2-1. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.5 Alternative handling of N2 transmission by using dedicated IP address for MWAB-gNB | Editor's note: The additions proposed by this clause need further discussion.
There might be following additional treatment for MWAB-gNB IP address on top of the procedure in clause 6.2.3.2:
- Step 1: OAM may also configure MWAB with MWAB-gNB IP address, which is used to establish N2 interface with the AMF. MWAB-gNB ma... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.6 MWAB NG-establishment | Editor's note: The procedure is only for information, and details need to be further coordinated with RAN WGs.
Figure 6.2.3.6-1: MWAB NG connection establishment including additional information for MWAB
The MWAB NG establishment is augmented with additional information the AMF stores to later decide what to do for MWA... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.7 MWAB-UE registration over other MWAB-gNB | Figure 6.2.3.7-1: MWAB-UE registration and multi-hop handling
The MWAB-UE of MWAB 2 attempts to register over a MWAB-gNB of MWAB 1. The AMF rejects the Registration or accepts the registration without authorizing the MWAB-UE to operate as MWAB. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.8 MWAB-UE N2 handover and multi-hop handling | Editor's note: The detailed procedures of N2 handover is FFS.
Editor's note: The procedure is only for information, and details need to be further coordinated with RAN WGs.
Figure 6.2.3.8-1: MWAB-UE N2 handover successful
In figure 6.2.3.8-1 the AMF indicates that the UE being handed over is a MWAB UE. The target RAN n... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.3.9 MWAB-UE Xn handover and multi-hop handling | Editor's note: The detailed procedures of Xn handover is FFS.
Editor's note: The procedure is only for information, and details need to be further coordinated with RAN WGs.
Figure 6.2.3.9-1: MWAB-UE N2 handover successful
In figure 6.2.3.9-1 the source NG-RAN node indicates that the UE being handed over is a MWAB UE. T... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.2.4 Impacts on services, entities, and interfaces | MWAB:
- May be configured with dedicated DNN/S-NSSAI for the PDU session for backhaul link.
- OAM configures MWAB-gNB with the PDUs session information to be used for the N2/N3.
- MWAB-gNB triggers PDU sessions establishment for the BH link based on obtained configuration and uses related address(es) for N2/N3, OAM int... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.3 Solution #3: N3 backhaul PDU session management | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.3.1 General | This solution is to address KI#1 about how to provide the backhaul link using a PDU sessions for a MWAB to support the N3 interfaces.
MWAB provides wireless connection to the 5GC through an IP connectivity provided by a PDU session; hence, both N2 interface and N3 interface are carried over the PDU session(s) between M... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.3.2 Functional descriptions | This solution assumes that:
- BH PDU session for N2 backhaul is already established.
- One or multiple BH PDU session(s) for N3 backhaul is already established or has not been established. Each BH PDU session is associated with the default 5QI and ARP of the QoS Flow associated with the default QoS rule as defined in c... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.3.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.3.3.1 Handling of a UE PDU session establishment or modification | Figure 6.3.3.1-1: Handling of a UE PDU session establishment or modification
1. A PDU session is established or modified for a UE as defined in clause 4.3 of TS 23.502 [7], and this causes the MWAB-gNB to receive from SMF a new SM context for a PDU session including at least a QoS flow.
2. For each QoS flow the MWAB-gN... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.3.4 Impacts on services, entities, and interfaces | MWAB:
- The MWAB binds the UE QoS flow to a BH PDU session based on the UE requested PDU session and the QoS flow characteristics |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4 Solution #4: MWAB authorization handling | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4.1 Introduction | This solution addresses issues related to KI#2. It provides methods to support MWAB operation authorization in different roaming scenarios. It also provides means to handle authorization status change handling for both MWAB-gNB logic and MWAB-UE logic. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4.2 Functional Description | When MWAB node includes MWAB-gNB function and MWAB-UE function as described in clause 4, the authorization of the MWAB operation is based on subscription information linked to the MWAB-UE and the authorization status can depend on the location and/or time.
The MWAB-gNB and MWAB-UE may be connected to the same network/5... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4.3.1 MWAB node authorization and operation initiation | This procedure describes the MWAB node authorization steps and the operations with focus on the 5GC aspects.
Figure 6.4.3.1-1: MWAB node authorization and operation initiation
MWAB-UE registration and authorization phase:
1. The MWAB-UE triggers registration towards the selected PLMN in NR cell. The MWAB-UE provides th... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4.3.2 MWAB authorization status change for Registered MWAB | This procedure is used when MWAB authorization status changes for a registered MWAB-UE .
Figure 6.4.3.2-1: MWAB authorization status change handling
Registered MWAB-UE authorization status change:
1. BH-AMF triggers NAS UE configuration update procedure to inform the MWAB-UE with the MWAB authorization status change.
W... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.4.4 Impacts on services, entities, and interfaces | AMF:
- Support MWAB authorization handling based on subscription data and local policy.
- Support NGAP removal procedure.
MWAB-UE:
- Support Authorization status handling.
- Support the IP connectivity establishment for the backhaul usage request from MWAB-gNB.
MWAB-gNB:
- Support NGAP removal procedure.
- Support the ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5 Solution #5: Authorization and Change of Authorization of a MWAB and configuration of a MWAB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5.1 General | This is a Solution addressing Key Issue #2: Authorization of a MWAB and configuration of MWAB. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5.2 Functional descriptions | The solution is based on this outline:
- The MWAB-UE optionally includes a MWAB indication in the Registration request, in the UE MM Core Network Capability defined in clause 5.3.4 of TS 23.501 [2]. Alternatively, or in addition, the MWAB-UE may be configured by the HPLMN a specific (set of) S-NSSAI(s) associated with ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5.3 Procedures | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5.3.1 MWAB service authorization and MWAB gNB configuration | Figure 6.5.3.1-1: MWAB service authorization and initial MWAB-gNB configuration
1. The MWAB-UE registers and optionally includes in the UE MM Core network capability defined in clause 5.3.4 of TS 23.501 [2] an indication it is intending to act as MWAB, optionally also indicate the PLMN(s) for which it may want to act a... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5.3.2 MWAB change of service authorization | Figure 6.5.3.2-1: MWAB change of service authorization
1. The UDM may provide updated subscription data changing the MWAB authorization status to (not) authorized.
2. The AMF determines whether the MWAB authorization status has changed to Allowed or Not Allowed, and if so, the AMF updates the MWAB-UE with the new MWAB ... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.5.4 Impacts on services, entities, and interfaces | AMF:
- ability to authorize and update authorization state and support MWABs as per message flows above.
MWAB (new):
- support the interactions with the OAM and 5GS as outlined above for authorization and change of authorization state.
OAM:
- configuration of MWAB. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.6 Solution #6: Reusing CAG mechanism for managing UE's access to MWAB-gNB | |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.6.1 Key Issue mapping | This solution addresses Key Issue #3. |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.6.2 Functional Description | This solution proposes to reuse the existing CAG mechanism defined by NPN for managing UE's access to MWAB-gNB.
NOTE 1: In the case the UE does not support CAG functionality, or PNI-NPN is not deployed by the network, the NG-RAN and 5GC are allowed to use not only CAG mechanism but also other existing mechanisms e.g. f... |
c8a46327a444e7f9bf64e4f24735fddc | 23.700-06 | 6.6.3 Procedures | Figure 6.6.3-1: Reusing CAG mechanism for managing UE's access to MWAB-gNB
NOTE: The procedure is for demonstrative purpose, the steps are all supported by VMR.
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 a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.