hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 8 Deployment scenarios | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 8.1 General | The architecture shall support deployment of application enablers and services over satellite connectivity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 8.2 Deployment model | See clauses 6.1, 6.2 and 6.3. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 9 Business Relationships | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 9.1 EDGEAPP deployment with satellite connectivity | The business relationship for EDGEAPP deployment with satellite connectivity described below is in addition to the description in clause B.1 of 3GPP TS 23.558 [10].
Figure 9.1-1: Relationships involved in edge computing service with satellite connectivity
The PLMN operator can have satellite service agreement with the ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 9.2 SEAL deployment with satellite connectivity | The business relationship for SEAL deployment with satellite connectivity.
Figure 9.2-1: Relationships involved in VAL services with satellite connectivity
The PLMN operator can have satellite service agreement with the satellite service provider to offer his services e.g. to serve the unconnected areas.
The SEAL provi... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10 Overall evaluation | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.1 Architecture evaluations for Mission Critical | Option#1 in clause 6.1 discusses MC architecture to enable MC services over NTN. There are no impacts identified to the existing architecture in 3GPP TS 23.289 [19] for providing MC services over satellite access. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.2 Key issue evaluations for Mission Critical | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.2.1 Key issue #4: | There is no solution specified in this study. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.2.2 Key issue #8: | The solution #MC1 described provides a promising approach to inform the participants of a group communication of possible MC service users being connected via NTN. The solution can be further enhanced, and potential procedures can be investigated during the normative work. Other potential solutions may be considered as... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.3 Architecture evaluations for Application Enablers | Option#2 in clause 6.2 addresses architecture for EDGEAPP over satellite connectivity. The EDGEAPP architecture as defined in 3GPP TS 23.558 [10] is reused to enhance EDGEAPP procedures such as service provisioning, EAS discovery during satellite connectivity as per Solution #AE1, Solution #AE2, Solution #AE5 and Solut... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4 Key issue evaluations for Application Enablers | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4.1 Key issue #1: | Solution #AE9 addresses the open issues for the key issue #1. It defines a new analytics for the UE RAT connectivity and proposes the procedures for the ADAE server. The solution proposed in this study will be added as part of 3GPP TS 23.436 [20]. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4.2 Key issue #2: | Solution #AE1, Solution #AE5 and Solution #AE7 addresses key issue #2.
Solution #AE1, Solution #AE5 and Solution #AE7 resolves open issue to investigate different deployment options for EDGEAPP. Solution #AE1 and Solution #AE7 proposes ECS is deployed on ground while EAS and EES are deployed on satellite.
Solution #AE5... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4.3 Key issue #3: | Solution #AE3 addresses key issue #3.
Solution #AE3 resolves open issue about application enabler (SEAL Configuration management server) obtaining the satellite coverage availability information and to retrieve unavailability period for UE (either from UE or from the 5GS), for supporting satellite discontinuous coverag... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4.4 Key issue #5: | Solution #AE1 and Solution #AE2 addresses key issue #5.
Solution #AE1 resolves open issue to investigate deployment option ECS is deployed on ground while EAS and EES are deployed on satellite for EDGEAPP and optimise EDGEAPP behaviour by enhancing both EDGEAPP service provisioning and EAS discovery procedures.
Solutio... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4.5 Key issue #6: | Editor's Note: This clause will provide evaluation of different solutions for KI#6. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 10.4.6 Key issue #7: | Solution #AE4, Solution #AE6 and Solution #AE8 addresses key issue #7.
Solution #AE4, Solution #AE6 and Solution #AE8 resolves open issue to obtain the S&F events information and to utilize S&F events information to optimise application enablement behaviour.
Solution #AE4 proposes how SEAL (NRM, Configuration Server, S... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11 Conclusions | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.1 General conclusions | This clause provides conclusions for the study of supporting deployment of application enablers and services over satellite connectivity. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.2 Conclusions for Mission Critical | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.2.1 General conclusions for MC services over NTN | Annex A has provided several information and recommendations related to the satellite access support for MC services. As satellite characteristics, e.g., altitude, play a significant role in introducing propagation delays and have direct impact on MC KPIs, NGSO satellites (e.g., LEO, MEO) may be the most suitable ones ... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.2.2 Conclusions of key issue #4 | There is no solution specified in this study. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.2.3 Conclusions of key issue #8 | The solution #MC1 described provides a promising approach to inform the participants of a group communication of possible MC service users being connected via NTN. The solution can be further enhanced, and potential procedures can be investigated during the normative work. Other potential solutions may be considered as... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3 Conclusions for Application Enablers | |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3.1 Architecture conclusions | The study concludes with following architectural considerations for the normative work:
- There are no architectural changes required to the EDGEAPP architecture defined in 3GPP TS 23.558 [10] for supporting satellite connectivity. The EDGEAPP architecture defined in 3GPP TS 23.558 [10] can be reused for supporting sat... |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3.2 Conclusions of key issue #1 and #2 | The study concludes with following solution considerations for the normative work:
- Solution #AE1
- Solution #AE7 and
- Solution #AE9.
The study concludes that Solution#AE5 requires more detailed study of this scenario before adding this solution to normative. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3.3 Conclusions of key issue #3 | The study concludes with following solution considerations for the normative work:
- Solution #AE3. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3.4 Conclusions of key issue #5 | The study concludes with following solution considerations for the normative work:
- Solution #AE1 and
- Solution #AE2. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3.5 Conclusions of key issue #6 | There is no solution specified in this study. |
290e4ab292f1f681b376d1960297f638 | 23.700-01 | 11.3.6 Conclusions of key issue #7 | The study concludes with following solution considerations for the normative work: - Solution #AE4 and - Solution #AE8. Annex A (informative): Information related to Satellite access support for MC Service A.1 Propagation delay over satellite As per current 3GPP specifications 3GPP TS 22.261 [2] and 3GPP TS 23.501 [5],... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 1 Scope | The present document will study and identify potential enhancements to the 5G Proximity-based Services (5G ProSe) system defined in TS 23.304 [4] (beyond what has been specified in Rel-17 and Rel-18) considering the services requirements defined in TS 22.278 [5], TS 22.261 [6] and TS 22.115 [7].
The study will investig... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 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... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 3 Definitions of terms and abbreviations | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1], TS 23.304 [4] 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] and TS 23.304 [4].
5G ProSe Intermediate Relay: A 5G ProSe-enabled UE that provides fu... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.304 [4] 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.304 [4]. |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 4 Architecture Requirements and Assumptions | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 4.1 Architecture Requirements | Solutions shall comply with and build on the 5G ProSe architecture principles as defined in TS 23.304 [4] and 5G System architectural principles as defined in TS 23.501 [8]. To satisfy the normative stage-1 requirements in TS 22.261 [6], the system shall:
- Support multi-hop over NR PC5 reference point for Layer-2 and ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 4.2 Architecture Assumptions | - Architecture reference models defined in TS 23.304 [4] are used as baseline architecture for supporting 5G ProSe Ph3.
- NG-RAN for NR is used; non-3GPP access is not considered in this Release.
- NR based PC5 and NR Uu are considered.
- For multi-hop UE-to-Network Relay, all the relay entities on the path should be o... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 5 Key Issues | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 5.1 Key Issue #1: Support of multi-hop UE-to-Network Relays | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 5.1.1 General description | This key issue focuses on architecture enhancements to support 5G ProSe multi-hop Layer-3 and Layer-2 UE-to-Network Relay over NR PC5 reference point. This key issue addresses scenarios where multi-hop UE-to-Network Relay(s) are in coverage and out of coverage.
Figure 5.1.1-1: Example scenario of multi-hop UE-to-Networ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 5.2 Key Issue #2: Support of Layer-3 multi-hop UE-to-UE Relays | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 5.2.1 General description | This key issue focuses on architecture enhancements to support ProSe multi-hop Layer-3 UE-to-UE Relay over NR PC5 reference point. This key issue intends to support multi-hop Layer-3 UE-to-UE Relays for in coverage and out of coverage operation.
Figure 5.2.1-1: Example scenario of support of Layer-3 multi-hop UE-to-UE ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6 Solutions | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.0 Mapping of Solutions to Key Issues | Table 6.0-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
1
2
1
X
2
X
3
X
4
X
X
5
X
6
X
7
X
8
X
9
X
10
X |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1 Solution #1: Architecture enhancement to support 5G ProSe multi-hop UE-to-Network Relays | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.1 Description | The solution is illustrated with the architecture example as shown in Figure 6.1.1-1.
Figure 6.1.1-1: Example architecture of multi-hop UE-to-Network Relay
Following operation principles are applied to support the 5G ProSe multi-hop UE-to-Network Relay operations to provide services to a 5G ProSe Remote UE:
- Only 5G P... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.1 Relay Discovery | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.1.1 Support of Model A discovery | Figure 6.1.2.1.1-1 provides an example of how the Model A discovery is supported in the multi-hop relay environment.
Figure 6.1.2.1.1-1: Example Model A Discovery operation supporting multi-hop UE-to-Network Relay
For Model A discovery, the 5G ProSe UE-to-Network Relay reuses the 5G ProSe UE-to-Network Relay Discovery ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.1.2 Support of Model B discovery | Figure 6.1.2.1.2-1: Example Model B Discovery operation supporting multi-hop UE-to-Network Relay
For Model B discovery, the 5G ProSe Remote UE uses the 5G ProSe UE-to-Network Relay Discovery Solicitation message (Model B), with the following modified/additional IE:
- Discoverer Info: User Info ID of the 5G ProSe Remote... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.2 Authentication and authorization for multi-hop relay operation | Existing service authorization configuration defined in clause 5.1.4 of TS 23.304 [4] for 5G ProSe UE-to-Network Relay can be reused for the support of multi-hop relay operation, with the following enhancements:
- within the Authorization policy, for each PLMN, an indication of whether multi-hop relay operation is auth... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.3 Relay Selection/re-selection | For initial Relay selection, the 5G ProSe Remote UE select a Relay announcing the least Hop-Count value, either a 5G ProSe UE-to-Network Relay or an Intermediate UE-to-Network Relay, assuming that each of the hop will meet the AS layer quality criteria.
When a 5G ProSe Remote UE discovers another Intermediate UE-to-Net... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.4 PC5 Link establishment and management | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.4.1 Layer-2 Link establishment and management | Each of the Intermediate UE-to-Network Relay needs to establish a Layer-2 Link with its parent Intermediate UE-to-Network Relay or the 5G ProSe UE-to-Network Relay, before it can serve the 5G ProSe Remote UE.
Existing Layer-2 link management procedure as defined in TS 23.304 [4] for UE-to-Network Relay operation can be... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.4.2 IP address/prefix management for Layer-3 UE-to-Network Relay | When IP based PDU session types are used by the 5G ProSe UE-to-Network Relay, the Intermediate UE-to-Network Relay needs to act as an IP Router.
The actual IP address allocation is performed by the 5G ProSe UE-to-Network Relay, in the same way as that defined in TS 23.304 [4].
To support DHCP based IP address configura... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.5 Relay reselection and mobility support | There are two types of mobility scenarios, i.e. the mobility of a single 5G ProSe Remote UE and the mobility of an Intermediate UE-to-Network Relay with multiple child relays and remote UEs.
For a single 5G ProSe Remote UE, when it lost the connection with its old relay (either an Intermediate UE-to-Network Relay or a ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.6 Support of End-to-end QoS management | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.6.1 General | For Layer-3 Relay operation, similar End-to-end QoS management as defined in TS 23.304 [4] can be reused, with the following enhancements:
- the end-to-end QoS flow is to be identified by both the Remote UE ID and the PC5 QoS flow IDs;
- detailed procedures for QoS management for Layer-3 UE-to-Network Relays are provid... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.6.2 Support End-to-end QoS management for multi-hop Layer-3 UE-to-Network Relays | 6.1.2.6.2.1 Description
End-to-end QoS management for multi-hop UE-to-Network Relays can be done similarly as End-to-end QoS management for single hop Layer-3 UE-to-Network Relay as defined in TS 23.304 [4] clause 5.6.2.1, with enhancement to handle QoS split over multiple legs of PC5 interface.
The solution covers the... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.7 Support of Layer-2 multi-hop UE-to-Network Relay operation | Additional considerations for the support of Layer-2 multi-hop UE-to-Network Relay operation depends on RAN WG progress. |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.2.8 Additional parameters announcement procedure | Additional parameters announcement procedure outlined in Figure 6.1.2.8-1 is used by a 5G ProSe Remote UE to request a 5G ProSe UE-to-Network Relay to announce additional parameters (using Model A). Based on the Additional parameters announcement procedure specified in clause 6.5.1.3 of TS 23.304 [4], differences are m... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.1.3 Impacts on services, entities and interfaces | AMF:
- No impact.
PCF:
- Potential enhancement to provide multi-hop related policies.
5G ProSe UE-to-Network Relay:
- Additional discovery message handling, new link management procedures.
- Support enhanced End-to-end QoS handling.
5G Intermediate UE-to-Network Relay:
- Handling new discovery messages, including manag... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2 Solution #2: Multi-hop 5G ProSe UE-to-Network Relay Discovery and Layer-3 Communication | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.1 Description | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.1.1 General | This solution provides a mechanism for enabling multi-hop 5G ProSe UE-to-Network Relay, where the Remote UE is connected to the UE-to-Network Relay via one or more 5G ProSe Intermediate Relay(s). It is assumed that the 5G ProSe UE-to-Network Relay, the Remote UE and the 5G ProSe Intermediate Relay(s) receive appropriat... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.1.2 Enhancements to QoS handling | The following principles apply for QoS handling for Layer-3 Multi-hop 5G ProSe UE-to-Network Relay:
- The Intermediate Relay at each hop can determine the per-hop QoS or cumulative QoS (e.g. cumulative delay and/or hop-count) and QoS information may be attached in the multi-hop Communication Request / Link Modification... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2.1 5G ProSe multi-hop UE-to-Network Relay Discovery | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2.1.1 5G ProSe multi-hop UE-to-Network Relay Discovery with Model A | Figure 6.2.2.1.1-1 illustrates the procedure for 5G ProSe muti-hop UE-to-Network Discovery with Model A.
Figure 6.2.2.1.1-1: 5G ProSe multi-hop UE-to-Network Relay Discovery with Model A
1. The 5G ProSe UE-to-Network Relay sends a UE-to-Network Relay Discovery Announcement message. Additional to the parameters describe... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2.1.2 5G ProSe multi-hop UE-to-Network Relay Discovery with Model B | Figure 6.2.2.1.2-1 illustrates the procedure for 5G ProSe muti-hop UE-to-Network Discovery with Model B.
Figure 6.2.2.1.2-1: 5G ProSe multi-hop UE-to-Network Relay Discovery with Model B
1. The 5G ProSe Remote UE sends a 5G ProSe UE-to-Network Relay Discovery Solicitation message which includes, additional to the param... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2.2 5G ProSe Communication via multi-hop Layer-3 UE-to-Network Relay | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2.2.1 5G ProSe Communication via multi-hop Layer-3 UE-to-Network Relay without N3IWF support | Figure 6.2.2.2.1-1 depicts the procedure for 5G ProSe Communication via multi-hop Layer-3 UE-to-Network Relay without N3IWF support.
Figure 6.2.2.2.1-1: 5G ProSe Communication via multi-hop 5G ProSe Layer-3 UE-to-Network Relay without N3IWF
1. Service authorization and parameter provisioning are performed for the 5G Pr... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.2.2.2 5G ProSe Communication via multi-hop Layer-3 UE-to-Network Relay with N3IWF support | Intermediate Relay UE can connect to N3IWF according to clause 6.5.1.2 of TS 23.304 [4] and provides the relay function to Remote UE.
Figure 6.2.2.2.2-1: Reference architecture for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF through Intermediate Relay(s)
Figure 6.2.2.2.2-2: Control plane protocol stacks between 5G ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.2.3 Impacts on services, entities and interfaces | The solution has impacts on the following entities:
- UE:
- Needs to support 5G ProSe Intermediate Relay functionality, as well as the discovery and communication establishment procedures for multi-hop 5G ProSe UE-to-Network Relay for the 5G ProSe Remote UE, 5G ProSe Layer-3 UE-to-Network Relay and 5G ProSe Intermediat... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.3 Solution #3: Architecture enhancement to support Layer-3 multi-hop UE-to-UE Relays | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.3.1 Description | The solution is illustrated with the architecture example as shown in Figure 6.3.1-1.
Figure 6.3.1-1: Example architecture of Layer-3 multi-hop UE-to-UE Relay
Following operation principles are applied to support the 5G ProSe Layer-3 multi-hop UE-to-UE Relay operations to provide services to a 5G ProSe end UEs:
- 5G Pr... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.3.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.3.2.1 Relay Discovery | Both Model A and Model B discovery can be used to discover a Layer-3 multi-hop UE-to-UE Relay. This discovery does not include information about the end UEs connected via the UE-to-UE Relay. Therefore, the information included in the discovery message only contains the UE-to-UE Relay Discovery set as defined in TS 23.3... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.3.2.2 Layer-2 Link establishment and management | 5G ProSe End UE establishes one or more Layer-2 link with the 5G ProSe Layer-3 multi-hop UE-to-UE Relay discovered, that meets the AS layer criteria. The link establishment procedure as defined in clause 6.4.3.1 of TS 23.304 [4] can be used.
The Layer-2 link can be of the type of IP (v4 or v6).
The 5G ProSe End UE prov... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.4 Solution #4: Layer-3 Multi-hop Relay based on MANET | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.4.1 Key Issue mapping | This solution primarily addresses Key Issue #2 (Support of Layer-3 multi-hop UE-to-UE Relays).
Some considerations are also provided for addressing Key Issue #1 (Support of multi-hop UE-to-Network Relays). |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.4.2 Description | The solution assumes that the Multi-hop ProSe UE-to-UE Relays have a collocated MANET router functionality (IETF RFC 7181 [9]) that connect with neighbouring MANET routers and establish a mobile ad-hoc network as defined in MANET (IETF RFC 7181 [9]). The Multi-hop ProSe UE-to-UE Relay relies on a new MANET messages (fo... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.4.3 Procedures | This solution relies on a new MANET message, referred to as [MANET] Discovery Info, that carries:
- Identity of the Relay that is originator of the [MANET] Discovery Info message.
- List of locally discovered User Info IDs (per RSC).
- Signalling Endpoint Address (IP address and port number) that can be used for establ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.4.4 Impacts on services, entities and interfaces | ProSe UE-to-UE Relay impact:
- Has a collocated MANET router functionality and is able to initiate or join a mobile ad hoc network as defined in MANET (IETF RFC 7181 [9]).
- Supports a new MANET message called [MANET] Discovery Info that is used to diffuse information about discovered end UEs to other U2U Relays over t... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.5 Solution #5: Support of Multi-hop UE-to-UE Relay Discovery | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.5.1 Description | This solution addressed Key Issue #2 "Support of Layer-3 Multi-hop UE-to-UE Relays".
In this solution, the ProSe 5G UE-to-UE Relay operations is supported with the following principles:
- 5G ProSe multi-hop UE-to-UE Relay discovery with Model B:
- The Source End UE decides the maximum number of hops for discovery based... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.5.2 Procedures | Figure 6.5.2-1: 5G ProSe multi-hop UE-to-UE Relay Discovery with Model B
The procedure of 5G ProSe multi-hop UE-to-UE Relay Discovery with Model B is extended based on the Rel-18 UE-to-UE Relay Discovery with Model B.
1. The Source End UE decides the maximum number of hops for discovery based on e.g. according to QoS r... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.5.3 Impacts on services, entities and interfaces | There is no impact to NG-RAN, as the solution is using the existing features supported in Rel-18 NR ProSe design.
There are impacts to 5G ProSe End UE, UE-to-UE Relay, maybe to ProSe Policy. |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6 Solution #6: Multi-hop extension of 5G ProSe UE-to-UE Relay | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.1 Description | In this solution, 5G ProSe multi-hop Layer-3 UE-to-UE Relay over NR PC5 is supported with the following principles:
- Authorization and configuration
- For supporting multi-hop extension, a UE-to-UE Relay shall be authorized and configured as a UE-to-UE Relay with multi-hop extension.
- Multi-hop UE-to-UE Relay Discove... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.2 Procedures | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.2.1 5G ProSe multi-hop UE-to-UE Relay Discovery | |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.2.1.1 Multi-hop U2U Relay discovery using model A | Figure 6.6.2.1.1-1: Multi-hop U2U Relay Discovery with model A
Precondition: end UEs and U2U Relays are authorized and provisioned with multi-hop specific configurations such as multi-hop indication to indicate multi-hop is enabled, multi-hop authorization based on the capabilities/subscription, RSC supporting multi-ho... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.2.1.2 Multi-hop U2U Relay discovery using model B | Figure 6.6.2.1.2-1: Multi-hop U2U Relay Discovery with model B
Precondition: end UEs and U2U Relays are authorized and provisioned with multi-hop specific configurations such as multi-hop indication to indicate multi-hop is enabled, multi-hop authorization based on the capabilities/subscription, RSC supporting multi-ho... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.2.2 5G ProSe Communication via 5G ProSe multi-hop Layer-3 UE-to-UE Relay | Figure 6.6.2.2-1: IP address assignment procedure based on configured IP address pool for multi-hop relay
0. UE1 and UE2 are authorized for multi-hop UE-to-UE Relay service as End UE and are provisioned with parameters for discovery and connection setup with other UEs via multi-hop UE-to-UE Relay services.
U2U Relay_1 ... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.2.3 5G ProSe multi-hop Layer-3 UE-to-UE Relay Reselection with negotiated U2U relay reselection procedure | This solution is about negotiated layer-3 UE-to-UE relay reselection procedure with multihop relay discovery support and with list of candidates U2U relays which are directly reachable by Initiating End UE(UE1).
Based on the list of U2U relays, Responding End UE(UE2) tries to find new end to end route to UE1. UE2 may c... |
3311cb9776ac4185d7bb30a10abe5d55 | 23.700-03 | 6.6.3 Impacts on services, entities and interfaces | 5GC:
- Authorization and provisioning parameters for multi-hop Layer-3 UE-to-UE Relay.
End UE, U2U Relay:
- Support Multi-hop Layer-3 UE-to-UE Relay functionality. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.