个人在学习5G标准3GPP TS 23501-g51过程中，也发现google的机器翻译实在晦涩难懂，所以个人在借助百度翻译（中国人更懂中文）的同时，人工对每句话进行了校对。

在自己学习的同时，也将翻译内容分享给给广大网友。由于个人能力有限，翻译不到位的地方还请各位网友们指正。

4.2.3 Non-roaming reference architecture

Figure 4.2.3-1 depicts the non-roaming reference architecture. Service-based interfaces are used within the Control Plane.

图4.2.3-1描述了non-roaming参考体系结构。在Control Plane内使用service-based的接口。

Figure 4.2.3-1: 5G System architecture

NOTE: If an SCP is deployed it can be used for indirect communication between NFs and NF services as described in Annex E. SCP does not expose services itself.

注意：如果部署了SCP，它可以用于NFs和NF服务之间的间接通信。SCP不暴露服务本身。

Figure 4.2.3-2 depicts the 5G System architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other.

图4.2.3-2描述了non-roaming情况下的5G System架构，使用了显示各种网络功能如何相互作用的参考点表示法。

NOTE 1: N9, N14 are not shown in all other figures however they may also be applicable for other scenarios.

注1:N9、N14未在所有其他图中显示，但它们也可能适用于其他场景。

NOTE 2: For the sake of clarity of the point-to-point diagrams, the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary.

注2：为了点到点图的清晰性，未描述UDSF、NEF和NRF。然而，所有描述的Network Functions都可以根据需要与UDSF、UDR、NEF和NRF交互。

NOTE 3: The UDM uses subscription data and authentication data and the PCF uses policy data that may be stored in UDR (refer to clause 4.2.5).

注3：UDM使用订阅数据和身份验证数据，PCF使用可存储在UDR中的策略数据。

NOTE 4: For clarity, the UDR and its connections with other NFs, e.g. PCF, are not depicted in the point-to-point and service-based architecture diagrams. For more information on data storage architectures refer to clause 4.2.5.

注4：为清晰起见，UDR及其与其他NFs（如PCF）的连接未在点对点和service-based的体系结构图中描述。

NOTE 5: For clarity, the NWDAF and its connections with other NFs, e.g. PCF, are not depicted in the point-to-point and service-based architecture diagrams. For more information on network data analytics architecture refer to TS 23.288 [86].

注5：为清楚起见，NWDAF及其与其他NFs（如PCF）的连接未在点对点和service-based的体系结构图中描述。

Figure 4.2.3-2: Non-Roaming 5G System Architecture in reference point representation

Figure 4.2.3-3 depicts the non-roaming architecture for UEs concurrently accessing two (e.g. local and central) data networks using multiple PDU Sessions, using the reference point representation. This figure shows the architecture for multiple PDU Sessions where two SMFs are selected for the two different PDU Sessions. However, each SMF may also have the capability to control both a local and a central UPF within a PDU Session.

图4.2.3-3描述了UE使用参考点表示法，使用多个PDU Session并发访问两个（例如本地和中央）数据网络的non-roaming架构。此图显示了多个PDU会话的体系结构，其中为两个不同的PDU Session选择了两个SMF。然而，每个SMF还可以在PDU Session中控制本地和中央UPF。

Figure 4.2.3-3: Applying non-roaming 5G System architecture for multiple PDU Session in reference point representation

Figure 4.2.3-4 depicts the non-roaming architecture in the case of concurrent access to two (e.g. local and central) data networks is provided within a single PDU Session, using the reference point representation.

图4.2.3-4描述了使用参考点表示法在单个PDU Session中提供对两个（例如本地和中央）数据网络的并发访问情况下的non-roaming架构。

Figure 4.2.3-4: Applying non-roaming 5G System architecture for concurrent access to two (e.g. local and central) data networks (single PDU Session option) in reference point representation

Figure 4.2.3-5 depicts the non-roaming architecture for Network Exposure Function, using reference point representation.

图4.2.3-5描述了使用参考点表了的Network Exposure Function的non-roaming架构。

Figure 4.2.3-5: Non-roaming architecture for Network Exposure Function in reference point representation

图4.2.3-5：参考点表示中的网络暴露功能的非漫游架构

NOTE 1: In figure 4.2.3-5, Trust domain for NEF is same as Trust domain for SCEF as defined in TS 23.682 [36].

注1：在图4.2.3-5中，NEF的信任域与TS 23.682[36]中定义的SCEF的信任域相同。

NOTE 2: In figure 4.2.3-5, 3GPP Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity.

注2：在图4.2.3-5中，3GPP Interface表示NEF和5GC Network Function之间的南向接口，如NEF和SMF之间的N29接口、NEF和PCF之间的N30接口等。为简单起见，未显示来自NEF的所有南向接口。

3GPP TS 23501-g51 中英文对照 | 4.2.3 Non-roaming reference architecture相关推荐

3GPP TS 23.040 -- SMS -- part1(第三章节)
文章目录 Introduction Definitions 3. 服务和服务要素 3.1 Basic services 3.2 Short Message Service elements 3.2.0 ...
3GPP TS 29244-g30 中英文对照 | 5.4.9 Provisioning of Predefined PCC/ADC Rules
学习5G知识,势必要去阅读相关的技术标准,而纯英文的标准协议对于初学者来说是个门槛. 个人在学习5G标准3GPP TS 29244-g30过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借 ...
3GPP TS 29244-g30 中英文对照 | 5.11 User plane inactivity detection and reporting
学习5G知识,势必要去阅读相关的技术标准,而纯英文的标准协议对于初学者来说是个门槛. 个人在学习5G标准3GPP TS 29244-g30过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借 ...
3GPP TS 23501-g51 中英文对照 | 4.4.5 Application Triggering Services
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
3GPP TS 23501-g51 中英文对照 | 4.2.1 General
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
3GPP TS 23501-g51 中英文对照 | 5.2.1 General
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
3GPP TS 23501-g51 中英文对照 | 4.1 General concepts
学习5G知识,势必要去阅读相关的技术标准,而纯英文的标准协议对于初学者来说是个门槛. 个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借 ...
3GPP TS 23501-g51 中英文对照 | 5.3.3 Connection Management
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
3GPP TS 23501-g51 中英文对照 | 4.3.2 Roaming architecture
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...
3GPP TS 23501-g51 中英文对照 | 4.4.4 Location services
个人在学习5G标准3GPP TS 23501-g51过程中,也发现google的机器翻译实在晦涩难懂,所以个人在借助百度翻译(中国人更懂中文)的同时,人工对每句话进行了校对. 在自己学习的同时,也将翻 ...

3GPP TS 23501-g51 中英文对照 | 4.2.3 Non-roaming reference architecture

4.2.3 Non-roaming reference architecture

3GPP TS 23501-g51 中英文对照 | 4.2.3 Non-roaming reference architecture相关推荐

最新文章

热门文章