3GPP TS 23501-g51 中英文对照 | 4.3.5 Service Exposure in Interworking Scenarios

Posted 2021-09-07 COCOgsta

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

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

4.3.5 Service Exposure in Interworking Scenarios

4.3.5.1 Non-roaming architecture

Figure 4.3.5.1-1 shows the non-roaming architecture for Service Exposure for EPC-5GC Interworking. If the UE is capable of mobility between EPS and 5GS, the network is expected to associate the UE with an SCEF+NEF node for Service Capability Exposure.

图4.3.5.1-1显示了EPC-5GC Interworking Service Exposure的non-roaming架构。如果UE能够在EPS和5GS之间移动，则网络期望将UE与SCEF+NEF节点关联以进行Service Capability Exposure。

Figure 4.3.5.1 1: Non-roaming Service Exposure Architecture for EPC-5GC Interworking

NOTE 1: In Figure 4.3.5.1-1, Trust domain for SCEF+NEF is same as Trust domain for SCEF as defined in TS 23.682 [36].

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

NOTE 2: In Figure 4.3.5.1-1, EPC Interface represents southbound interfaces between SCEF and EPC nodes e.g. the S6t interface between SCEF and HSS, the T6a interface between SCEF and MME, etc. All southbound interfaces from SCEF are defined in TS 23.682 [36] and are not shown for the sake of simplicity.

注2：在图4.3.5.1-1中，EPC Interface表示SCEF和EPC节点之间的南向接口，例如SCEF和HSS之间的S6t接口、SCEF和MME之间的T6a接口等。SCEF的所有南向接口在TS 23.682[36]中定义，为简单起见，未显示。

NOTE 3: In Figure 4.3.5.1-1, 5GC 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.

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

NOTE 4: Interaction between the SCEF and NEF within the combined SCEF+NEF is required. For example, when the SCEF+NEF supports monitoring APIs, the SCEF and NEF need to share context and state information on a UE's configured monitoring events if the UE moves between from EPC and 5GC.

注4：SCEF和NEF之间需要在组合SCEF+NEF内进行交互。例如，当SCEF+NEF支持监视API时，如果UE在EPC和5GC之间移动，则SCEF和NEF需要共享UE配置的监视事件的上下文和状态信息。

NOTE 5: The north-bound APIs which can be supported by an EPC or 5GC network are discovered by the SCEF+NEF node via the CAPIF function and/or via local configuration of the SCEF+NEF node. Different sets of APIs can be supported by the two network types.

注5：SCEF+NEF节点通过CAPIF功能和/或通过SCEF+NEF节点的本地配置发现EPC或5GC网络支持的north-bound API。这两种网络类型可以支持不同的API集。

4.3.5.2 Roaming architectures

Figure 4.3.5.2-1 represents the roaming architecture for Service Exposure for EPC-5GC Interworking. This architecture is applicable to both the home routed roaming and local breakout roaming.

图4.3.5.2-1为EPC-5GC Interworking Service Exposure的漫游架构。该体系结构适用于本地路由漫游和本地分流漫游。

 

Figure 4.3.5.2-1: Roaming Service Exposure Architecture for EPC-5GC Interworking

NOTE: Figure 4.3.5.2-1 does not include all the interfaces, and network elements or network functions that may be connected to SCEF+NEF.

注：图4.3.5.2-1不包括所有可能连接到SCEF+NEF的接口、网元或网络功能。