logo资料库

3GPP TS 23.501 V16.1.0 5.6 Session Management -中英文对照版V1.pdf

第1页 / 共47页
第2页 / 共47页
第3页 / 共47页
第4页 / 共47页
第5页 / 共47页
第6页 / 共47页
第7页 / 共47页
第8页 / 共47页
资料共47页,剩余部分请下载后查看
5.6 Session Management 会话管理
5.6 Session Management 会话管理
5.6.1 Overview 概述
5.6.1 Overview 概述
5.6.2 Interaction between AMF and SMF AMF和SMF间交互
5.6.2 Interaction between AMF and SMF AMF和SMF间交互
5.6.3 Roaming 漫游
5.6.3 Roaming 漫游
5.6.3 Roaming 漫游
5.6.4 Single PDU Session with multiple PDU Session Anchors 多PDU会话锚点的单PDU会话
5.6.4 Single PDU Session with multiple PDU Session Anchors 多PDU会话锚点的单PDU会话
5.6.4.1 General 一般性内容
5.6.4.1 General 一般性内容
5.6.4.2 Usage of an UL Classifier for a PDU Session PDU会话的上行分类器使用
5.6.4.2 Usage of an UL Classifier for a PDU Session PDU会话的上行分类器使用
5.6.4.3 Usage of IPv6 multi-homing for a PDU Session PDU会话的IPv6多宿主的使用
5.6.4.3 Usage of IPv6 multi-homing for a PDU Session PDU会话的IPv6多宿主的使用
5.6.5 Support for Local Area Data Network 本地数据网络的支持
5.6.5 Support for Local Area Data Network 本地数据网络的支持
5.6.6 Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session PDU会话建立阶段的二次鉴权授权
5.6.6 Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session PDU会话建立阶段的二次鉴权授权
5.6.7 Application Function influence on traffic routing AF对流量路由的影响
5.6.7 Application Function influence on traffic routing AF对流量路由的影响
5.6.7.1 General 一般性内容
5.6.7.1 General 一般性内容
5.6.7.2 Enhancement of UP path management based on the coordination with AFs
5.6.7.2 Enhancement of UP path management based on the coordination with AFs
5.6.7.2 Enhancement of UP path management based on the coordination with AFs
5.6.8 Selective activation and deactivation of UP connection of existing PDU Session 选择性激活和去活存在的PDU会话用户面连接
5.6.8 Selective activation and deactivation of UP connection of existing PDU Session 选择性激活和去活存在的PDU会话用户面连接
5.6.8 Selective activation and deactivation of UP connection of existing PDU Session 选择性激活和去活存在的PDU会话用户面连接
5.6.9 Session and Service Continuity 会话和服务连续性
5.6.9.1 General 一般性内容
5.6.9 Session and Service Continuity 会话和服务连续性
5.6.9 Session and Service Continuity 会话和服务连续性
5.6.9.1 General 一般性内容
5.6.9.2 SSC mode 会话和服务连续性模式
5.6.9.2 SSC mode 会话和服务连续性模式
5.6.9.2.1 SSC Mode 1 会话和服务连续性模式 1
5.6.9.2.1 SSC Mode 1 会话和服务连续性模式 1
5.6.9.2.2 SSC Mode 2 会话和服务连续性模式2
5.6.9.2.2 SSC Mode 2 会话和服务连续性模式2
5.6.9.2.3 SSC Mode 3 会话和服务连续性模式 3
5.6.9.2.3 SSC Mode 3 会话和服务连续性模式 3
5.6.9.3 SSC mode selection 会话和服务连续性模式选择
5.6.9.3 SSC mode selection 会话和服务连续性模式选择
5.6.10 Specific aspects of different PDU Session types 不同PDU会话类型的特定方面
5.6.10 Specific aspects of different PDU Session types 不同PDU会话类型的特定方面
5.6.10.1 Support of IP PDU Session type 对IP PDU会话类型的支持
5.6.10.1 Support of IP PDU Session type 对IP PDU会话类型的支持
5.6.10.2 Support of Ethernet PDU Session type 对以太网 PDU会话类型的支持
5.6.10.2 Support of Ethernet PDU Session type 对以太网 PDU会话类型的支持
5.6.10.3 Support of Unstructured PDU Session type 对非结构化 PDU会话类型的支持
5.6.10.3 Support of Unstructured PDU Session type 对非结构化 PDU会话类型的支持
5.6.11 UE presence in Area of Interest reporting usage by SMF SMF的终端在兴趣区的存在报告
5.6.11 UE presence in Area of Interest reporting usage by SMF SMF的终端在兴趣区的存在报告
5.6.12 Use of Network Instance 网络实例的使用
5.6.12 Use of Network Instance 网络实例的使用
5.6.13 Always-on PDU session 一直在线PDU会话
5.6.13 Always-on PDU session 一直在线PDU会话
5.6.14 Support of Framed Routing 成帧路由的支持
5.6.14 Support of Framed Routing 成帧路由的支持
1 5.6 Session Management 会话管理 5.6.1 Overview 概述 The 5GC supports a PDU Connectivity Service i.e. a service that provides exchange of PDUs between a UE and a data network identified by a DNN. The PDU Connectivity Service is supported via PDU Sessions that are established upon request from the UE. 5G 核心网支持 PDU 连接服务,在终端和通过 DNN 标识的数据网之间提供 PDU 交换的服务。通过支持由 UE 发起请求建立的 PDU 会话来支持 PDU 连接服务。 The Subscription Information for each S-NSSAI may contain a Subscribed DNN list and one default DNN. When the UE does not provide a DNN in a NAS Message containing PDU Session Establishment Request for a given S-NSSAI, the serving AMF determines the DNN for the requested PDU Session by selecting the default DNN for this S-NSSAI if a default DNN is present in the UE's Subscription Information; otherwise the serving AMF selects a locally configured DNN for this S-NSSAI. 每个 S-NSSAI 签约信息包含签约的 DNN 列表和一个缺省的 DNN。当终端在包含 PDU 会话建立请求的 NAS 消 息中没有为给定的 S-NSSAI 提供 DNN 时,如果终端签约信息中没有缺省 DNN,那么服务的 AMF 通过为此 S- NSSAI 选择缺省 DNN 来为请求的 PDU 会话决定 DNN,否则服务 AMF 为此 S-NSSAI 选择一个本地配置的 DNN。 The expectation is that the URSP in the UE is always up to date using the procedure defined in TS 23.502 [3] clause 4.16.12.2 and therefore the UE requested DNN will be up to date. 预期终端中终端路由选择策略(UE Route Selection Policy)使用 TS 23.502 的 4.16.12.2 小节定义的流程,始终 是最新的,因而终端请求 DNN 也将是最新的。 In order to cover cases that UE operates using local configuration, but also other cases where operator policies can be used in order to replace an "up to date" UE requested DNN with another DNN used only internally in the network, during UE Registration procedure the PCF may indicate, to the AMF, the operator policies to be used at PDU Session Establishment for rejection and/or DNN and possibly S-NSSAI replacement of a UE requested DNN. PCF may indicate rejection or replacement of UE requested DNNs not supported by the network, and indicate UE requested DNNs subject for replacement. 为了应对终端按照本地配置进行操作的场景,但是也会有其他情景,应用运营商策略仅在网络内部用另一个 DNN 替换“最新的”终端请求的 DNN,PCF 可在终端注册流程指示给 AMF,运营商策略应用在拒绝 PDU 会话 建立,和用 DNN 和可能的 S-NSSAI 替换终端请求的 DNN。PCF 可以指示拒绝或者替换哪些网络不支持的终 端请求 DNN,并在终端请求 DNN 被替换时进行指示。 If the DNN provided by the UE is not supported by the network and AMF can not select an SMF by querying NRF, the AMF shall either reject the NAS Message containing PDU Session Establishment Request from the UE with a cause indicating that the DNN is not supported or request PCF to perform a DNN replacement. If the DNN requested by the UE is indicated for replacement, the AMF shall indicate to the PCF to perform a DNN replacement. During PDU Session Establishment procedure and as a result of DNN replacement, the PCF provides the selected DNN and possibly a corresponding S-NSSAI to the AMF. The AMF uses the selected DNN and S-NSSAI in the query towards the NRF for the SMF selection and provides both requested and selected DNN and S-NSSAI to the selected SMF. 如果网络不支持终端提供的 DNN 并且 AMF 不能通过向 NRF 查询来选择 SMF,AMF 或者用原因为 DNN 不被 支持,拒绝终端的包含 PDU 会话建立请求的 NAS 消息,或者请求 PCF 执行 DNN 替换。如果终端请求的 DNN 被指示要替换,AMF 要指示 PCF 执行 DNN 替换。在 PDU 会话建立流程,作为 DNN 替换的结果,PCF 提供 给 AMF 被选择的 DNN 和可能的相应的 S-NSSAI。AMF 使用选择的 DNN 和 S-NSSAI,去查询 NRF 来选择 SMF,并提供请求和选择的 DNN 和 S-NSSAI 给被选择的 SMF。 NOTE 1: The selected DNN and S-NSSAI are determined based on operator preferences and can differ from subscribed DNNs. 注意 1:选择的 DNN 和 S-NSSAI 基于运营商偏好决定,可以和签约的 DNN 不同。 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
2 Each PDU Session supports a single PDU Session type i.e. supports the exchange of a single type of PDU requested by the UE at the establishment of the PDU Session. The following PDU Session types are defined: IPv4, IPv6, IPv4v6, Ethernet, Unstructured. 每个 PDU 会话支持单个 PDU 会话类型,支持终端在 PDU 会话建立阶段更换终端请求的 PDU 类型。后续的 PDU 会话类型定义为:IPv4, IPv6, IPv4v6, Ethernet(以太网), Unstructured(非结构化). PDU Sessions are established (upon UE request), modified (upon UE and 5GC request) and released (upon UE and 5GC request) using NAS SM signalling exchanged over N1 between the UE and the SMF. Upon request from an Application Server, the 5GC is able to trigger a specific application in the UE. When receiving that trigger message, the UE shall pass it to the identified application in the UE. The identified application in the UE may establish a PDU Session to a specific DNN, see clause 4.4.5. PDU 会话在终端和 SMF 之间使用 N1 接口上的 NAS SM 信令,可以建立(依终端请求),修改(依终端和 5G 核心网请求)和释放(依终端和 5G 核心网请求)。收到应用服务器发起的请求,5G 核心网将触发终端内的特 定应用。当终端收到触发消息,将其传送给终端中识别到的应用。终端中的识别到的应用可以建立到特定 DNN 的 PDU 会话,见 4.4.5 小节详述。 SMF may support PDU Sessions for LADN where the access to a DN is only available in a specific LADN service area. This is further defined in clause 5.6.5. SMF 可支持 LADN 的 PDU 会话,到 DN 的接入仅在特定的 LADN 服务区域可用。在 5.6.5 节进一步做定义。 SMF may support PDU Sessions for a 5G VN group which offers a virtual data network capable of supporting 5G LAN-type service over the 5G system. This is further defined in clause 5.8.2.13. SMF 可支持提供了虚拟数据网 5G VN 组的 PDU 会话,可以在 5G 系统之上支持 5G LAN 类型服务。在 5.8.2.13 节进一步做定义。 The SMF is responsible of checking whether the UE requests are compliant with the user subscription. For this purpose, it retrieves and requests to receive update notifications on SMF level subscription data from the UDM. Such data may indicate per DNN and per S-NSSAI: SMF 负责核对终端的请求是否符合用户签约信息。出于这个目的,SMF 向 UDM 检索和请求以获得 SMF 级别 签约数据的更新通知。这些数据可以每 DNN 和每 S-NSSAI 的进行指示。 - The allowed PDU Session Types and the default PDU Session Type. - 允许的 PDU 会话类型和缺省的 PDU 会话类型。 - The allowed SSC modes and the default SSC mode. - 允许的 SSC 模式和缺省的 SSC 模式。 - QoS Information (refer to clause 5.7): the subscribed Session-AMBR, Default 5QI and Default ARP. - QoS 信息(参见 5.7 节):签约的会话级 AMBR,缺省的 5QI 和 ARP。 - The static IP address/prefix. - 静态 IP 地址/前缀 - The subscribed User Plane Security Policy. - 签约的用户面安全策略 - the Charging Characteristics to be associated with the PDU Session. Whether this information is provided by the UDM to a SMF in another PLMN (for PDU Sessions in LBO mode) is defined by operator policies in the UDM/UDR. - 和 PDU 会话相关的计费特性。在 UDM/UDR 的运营商策略定义了是否由 UDM 提供给另一个 PLMN 的 SMF(LBO 模式下的 PDU 会话)此信息。 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
3 NOTE 2: The content of the Charging Characteristics as well as the usage of the Charging Characteristics by the SMF are defined in TS 32.240 [41]. 注意 2:TS 32.240 中定义了计费特性的内容和计费特性在 SMF 的使用。 A PDU Session may support: PDU 会话可支持: (a) a single-access PDU Connectivity Service, in which case the PDU Session is associated with a single access type at a given time, i.e. either 3GPP access or non-3GPP access; or 单接入 PDU 连接服务,此场景下 PDU 会话和给定时间内的单接入类型相关,如 3GPP 接入或者非 3GPP 接入;或 (b) a multi-access PDU Connectivity Service, in which case the PDU Session is simultaneously associated with both 3GPP access and non-3GPP access. 多接入 PDU 连接服务,此场景下 PDU 会话同时和 3GPP 接入和非 3GPP 接入相关。 A PDU Session supporting a single-access PDU Connectivity Service is also referred to as single-access PDU Session, while a PDU Session supporting a multi-access PDU Connectivity Service is referred to as Multi-Access PDU (MA PDU) Session and it is used to support the ATSSS feature (see clause 5.32 for details). 支持单接入 PDU 连接服务的 PDU 会话也被叫做单接入 PDU 会话,支持多接入 PDU 连接服务的 PDU 会话也 被叫做多接入 PDU 会话(MAPDU),被用来支持 ATSSS(Access Traffic Steering, Switching, Splitting,接入 流量引导,交换,分割)特性(详述见 5.32 节) A UE that is registered over multiple accesses chooses over which access to establish a PDU Session. As defined in TS 23.503 [45], the HPLMN may send policies to the UE to guide the UE selection of the access over which to establish a PDU Session. 终端在多个接入网注册,选择在某个接入类型去建立 PDU 会话。依照 TS 23.503 定义,HPLMN 可以发送策略 给终端去引导终端选择去建立 PDU 会话的接入类型。 NOTE 3: In this Release of the specification, at any given time, a PDU Session is routed over only a single access network. 注意 3: 在本版本的协议中,在任何给定时间,一个 PDU 会话只能在一个接入网中路由。 A UE may request to move a single-access PDU Session between 3GPP and Non 3GPP accesses. The decision to move single-access PDU Sessions between 3GPP access and Non 3GPP access is made on a per PDU Session basis, i.e. the UE may, at a given time, have some PDU Sessions using 3GPP access while other PDU Sessions are using Non 3GPP access. 终端可请求将单接入 PDU 会话在 3GPP 和非 3GPP 接入之间迁移。基于单个 PDU 会话进行单接入 PDU 会话在 3GPP 和非 3GPP 接入之间迁移,这样终端可以在给定时间,有一些 PDU 会话使用 3GPP 接入,同时其他 PDU 会话使用非 3GPP 接入。 In a PDU Session Establishment Request message sent to the network, the UE shall provide a PDU Session ID. The PDU Session ID is unique per UE and is the identifier used to uniquely identify one of a UE's PDU Sessions. The PDU Session ID shall be stored in the UDM to support handover between 3GPP and non-3GPP access when different PLMNs are used for the two accesses. The UE also provides as described in TS 24.501 [47]: 在发送给网络的 PDU 会话建立请求消息中,终端要提供 PDU 会话 ID。这个 PDU 会话 ID 在每个终端内是唯一 的,是用来唯一的识别一个终端的 PDU 会话的识别码。PDU 会话 ID 将存储在 UDM 中,支持在不同 PLMN 之 间使用两种接入网时在 3GPP 和非 3GPP 之间的切换。终端也按照 TS 24.501 定义提供如下: - A PDU Session Type. - PDU 会话类型 - S-NSSAI. 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
- S-NSSAI - The DNN (Data Network Name). - DNN(数据网络名) 4 - The SSC mode (Service and Session Continuity mode defined in clause 5.6.9.2). - SSC 模式(5.6.9.2 节定义的服务和会话连续性模式) Additionally, if the UE supports ATSSS and wants to activate a MA PDU Session, the UE shall provide a MA PDU Request indication and shall indicate the supported ATSSS capabilities (see clause 5.32 for details). 此外,如果终端支持 ATSSS 模式,想要激活 MA PDU(多接入 PDU)会话,终端将提供一个 MA PDU 请求指 示,将指示支持 ATSSS 能力(细节见 5.32 节) Table 5.6.1-1: Attributes of a PDU Session PDU 会话的属性 PDU Session attribute May be modified later during the lifetime of the PDU Session S-NSSAI No DNN (Data Network Name) No No PDU Session Type SSC mode No PDU Session Id User Plane Security Enforcement information Multi-access PDU Connectivity Service No No No Notes (Note 1) (Note 2) (Note 1) (Note 2) (Note 1) (Note 2) The semantics of Service and Session Continuity mode is defined in clause 5.6.9.2 (Note 3) Indicates if the PDU Session provides multi-access PDU Connectivity Service or not. NOTE 1: If it is not provided by the UE, the network determines the parameter based on default information received in user subscription. Subscription to different DNN(s) and S- NSSAI(s) may correspond to different default SSC modes and different default PDU Session Types 注意 1: 如果终端不提供此参数,网络基于收到用户签约缺省信息做决定。签约到不同 DNN 和 S- NSSAI 会对应到不同的缺省 SSC 模式和不同的缺省 PDU 会话类型。 NOTE 2: S-NSSAI and DNN are used by AMF to select a SMF to handle a new session. Refer to clause 6.3.2. 注意 2: S-NSSAI 和 DNN 被 AMF 用来选择 SMF 去处理新的会话。参见 6.32 节。 NOTE 3: User Plane Security Enforcement information is defined in clause 5.10.3. 注意 3: 用户平面安全管理信息在 5.10.3 节中定义。 Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the subscription allows, for this S-NSSAI, the UE to establish a PDU Session using any DNN value. 签约信息可能包含每个签约 S-NSSAI 的通配 DNN:当通配 DNN 和签约 S-NSSAI 关联时,签约(信息)允许 终端为此 S-NSSAI 建立使用任何 DNN 值的 PDU 会话。 NOTE 4: The SMF is made aware whether the DNN of a PDU Session being established corresponds to an explicitly subscribed DNN or corresponds to a wildcard DNN. Thus, the SMF can reject a PDU Session establishment if the DNN of the PDU Session is not part of explicitly subscribed DNN(s) and local policies in the SMF require UE to have a subscription to this DNN. 注意 4: SMF 要明确 PDU 会话建立的 DNN 是显式签约的 DNN 还是相应的通过通配 DNN 的。因此,如果 PDU 会话中的 DNN 不是显式签约的但是 SMF 中本地策略要求终端签约此 DNN,那么 SMF 可以 拒绝 PDU 会话建立。 A UE may establish multiple PDU Sessions, to the same data network or to different data networks, via 3GPP and via and Non-3GPP access networks at the same time. 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
5 终端可以建立多个 PDU 会话,这些会话在同一时间,去相同的数据网络或者不同的数据网络,通过 3GPP 接 入或者非 3GPP 接入网络。 A UE may establish multiple PDU Sessions to the same Data Network and served by different UPF terminating N6. 终端可建立至相同数据网络的多 PDU 会话,通过不同的终结 N6 接口的 UPF 提供服务。 A UE with multiple established PDU Sessions may be served by different SMF. 终端建立的多 PDU 会话可由不同 SMF 提供服务。 The SMF shall be registered and deregistered on a per PDU Session granularity in the UDM. SMF 在按照每 PDU 会话的粒度在 UDM 注册和注销 PDU 会话。 The user plane paths of different PDU Sessions (to the same or to different DNN) belonging to the same UE may be completely disjoint between the AN and the UPF interfacing with the DN. 属于同一个终端的不同 PDU 会话的用户面路径可在接入网到至 DN 的 UPF 间完全分离。 When the SMF cannot control the UPF terminating the N3 interface used by a PDU Session and SSC mode 2/3 procedures are not applied to the PDU Session, an I-SMF is inserted between the SMF and the AMF and handling of PDU Session(s) is described in the clause 5.34. 当 SMF 不能控制 PDU 会话所使用的终结 N3 接口的 UPF,SSC2/3 模式也不适用于 PDU 会话,5.34 节描述了 如何在 SMF 和 AMF 之间插入 I-SMF 处理 PDU 会话。 NOTE 5: User Plane resources for PDU Sessions of a UE, except for regulatory prioritized service like Emergency Services and MPS, can be deactivated by the SMF if the UE is only reachable for regulatory prioritized services. 注意 5:终端 PDU 会话的用户平面,除了像紧急服务和 MPS 这样的监管优先服务之外,如果终端仅为监管 优先服务可达时,可以被 SMF 去激活。 Interaction between AMF and SMF AMF 和 SMF 间交互 5.6.2 The AMF and SMF are separate Network Functions. AMF 和 SMF 是分离的网络功能。 N1 related interaction with SMF is as follows: N1 和 SMF 相关的交互如下: - The single N1 termination point is located in AMF. The AMF forwards SM related NAS information to the SMF based on the PDU Session ID in the NAS message. Further SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS signalling received by the AMF over an access (e.g. 3GPP access or non-3GPP access) are transported over the same access. - 单 N1 终结点位于 AMF。AMF 基于在 NAS 消息中 PDU 会话 ID 转发 SM 相关的 NAS 信息给 SMF。后 续为 N1 NAS 信令从 AMF 接收到的会话管理 NSA 交换(如 SM NAS 消息响应),从一种接入(如 3GPP 或者非 3GPP 接入)收到的就从同样的接入传输。 - The serving PLMN ensures that subsequent SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS signalling received by the AMF over an access (e.g. 3GPP access or non-3GPP access) are transported over the same access. - 服务的 PLMN 确保之后的一个接入(如 3GPP 接入或者非 3GPP 接入)被 AMF 接收的 N1 NAS 信令的 SM NAS 消息交换(如 SM NAS 消息响应)在相同的接入中传输。 - SMF handles the Session management part of NAS signalling exchanged with the UE. 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
6 - SMF 处理和终端交换的 NSA 信令的会话管理部分。 - The UE shall only initiate PDU Session Establishment in RM-REGISTERED state. - 终端将仅在 RM 注册态初始化 PDU 会话建立流程。 - When a SMF has been selected to serve a specific PDU Session, AMF has to ensure that all NAS signalling related with this PDU Session is handled by the same SMF instance. - 当 SMF 被选中为特定的 PDU 会话提供服务,AMF 要确保所有和此 PDU 会话相关的 NAS 信令由同一个 SMF 实例所处理。 - Upon successful PDU Session Establishment, the AMF and SMF stores the Access Type that the PDU Session is associated. - 一旦 PDU 会话建立成功,AMF 和 SMF 将存储 PDU 会话关联的接入类型。 N11 related interaction with SMF is as follows: N11 和 SMF 相关的交互如下: - The AMF reports the reachability of the UE based on a subscription from the SMF, including: - AMF 基于 SMF 的订阅,报告终端的可达性,包含: - The UE location information with respect to the area of interest indicated by the SMF. - 和 SMF 指示的感兴趣区域相关的终端位置信息。 - The SMF indicates to AMF when a PDU Session has been released. - 当 PDU 会话被释放,SMF 向 AMF 发送指示。 - Upon successful PDU Session Establishment, AMF stores the identification of serving SMF of UE and SMF stores the identification of serving AMF of UE including the AMF set. When trying to reach the AMF serving the UE, the SMF may need to apply the behaviour described for "the other CP NFs" in clause 5.21. - 当 PDU 会话成功建立,AMF 存储为终端服务 SMF 的标识,SMF 存储包括 AMF 集的为终端服务的 AMF 标识。当尝试联系为终端服务的 AMF 时,SMF 可能需要应用 5.21 节中描述的“其他核心网 NF”行为。 N2 related interaction with SMF is as follows: N2 和 SMF 相关交互如下: - Some N2 signalling (such as handover related signalling) may require the action of both AMF and SMF. In such case, the AMF is responsible to ensure the coordination between AMF and SMF. The AMF may forward the SM N2 signalling towards the corresponding SMF based on the PDU Session ID in N2 signalling. - 一些 N2 信令(如切换相关信令)可能要求 AMF 和 SMF 的共同操作。在这种情境下,AMF 负责确保 AMF 和 SMF 间的协调。AMF 可基于 N2 信令中 PDU 会话 ID 转发 SM 的 N2 信令给相应的 SMF。 - SMF shall provide PDU Session Type together with PDU Session ID to NG-RAN, in order to facilitate NG- RAN to apply suitable header compression mechanism to packet of different PDU type. Details refer to TS 38.413 [34]. - SMF 要把 PDU 会话 ID 和 PDU 会话类型一起提供给 NG-RAN,目的是促进 NG-RAN 为不同的 PDU 类 型的数据包应用合适的包头压缩机制。细节参见 TS 38.413。 N3 related interaction with SMF is as follows: N3 和 SMF 相关交互如下: - Selective activation and deactivation of UP connection of existing PDU Session is defined in clause 5.6.8. 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
7 - 5.6.8 节定义了如何选择性的对存在的 PDU 会话激活和去活用户面连接。 N4 related interaction with SMF is as follows: N4 和 SMF 相关交互如下: - When it is made aware by the UPF that some DL data has arrived for a UE without downlink N3 tunnel information, the SMF interacts with the AMF to initiate Network Triggered Service Request procedure. In this case, if the SMF is aware that the UE is unreachable or if the UE is reachable only for regulatory prioritized service and the PDU Session is not for regulatory prioritized service, then the SMF shall not inform DL data notification to the AMF - 当 UPF 通知(SMF)有目的地为终端的下行数据包到达而此时没有下行 N3 隧道信息,SMF 与 AMF 交 互来初始化网络触发的业务请求流程。在这种情境下,如果 SMF 知道终端不可达或者终端仅能为监管 优先服务可达然而 PDU 会话不是为监管优先服务的,那么 SMF 将不知会 AMF 下行数据通知。 The AMF is responsible of selecting the SMF per procedures described in clause 6.3.2. For this purpose, it gets subscription data from the UDM that are defined in that clause. Furthermore, it retrieves the subscribed UE-AMBR from the UDM, and optionally dynamic serving network UE-AMBR from PCF based on operator local policy, and sends to the (R)AN as defined in clause 5.7.2 AMF 负责按照 6.3.2 节描述每个流程选择 SMF。出于这个目的,按照那节内容定义,AMF 从 UDM 获得签约 信息。此外,AMF 从 UDM 检索签约 UE-AMBR 信息,可选的,基于运营商本地策略从 PCF 获得动态服务网 络 UE-AMBR,并按 5.7.2 节定义发送给(R)AN。 AMF-SMF interactions to support LADN are defined in clause 5.6.5. 支持 LADN 的 AMF-SMF 交互在 5.6.5 节定义。 In order to support charging data collection and to fulfill regulatory requirement (in order to provide NPLI - Network Provided Location Information- as defined in TS 23.228 [15]) related with with the set-up, modification and release of IMS Voice calls or with SMS transfer the following applies 为了支持和建立,修改和释放 IMS 语音呼叫或者 SMS 传输的计费数据收集和满足监管要求(为提供 NPLI-网 络提供位置信息,在 TS 23.228 中定义),应用如下: - At the time of the PDU Session Establishment, the AMF provides the SMF with the PEI of the UE if the PEI is available at the AMF. - 在 PDU 会话建立时,如果 AMF 中 PEI 可用则 AMF 提供给 SMF 终端的 PEI。 - When it forwards UL NAS or N2 signalling to a peer NF (e.g. to SMF or to SMSF) or during the UP connection activation of a PDU Session, the AMF provides any User Location Information it has received from the 5G-AN as well as the Access Type (3GPP - Non 3GPP) of the AN over which it has received the UL NAS or N2 signalling. The AMF also provides the corresponding UE Time Zone. In addition, in order to fulfill regulatory requirement (i.e. providing Network Provided Location Information (NPLI), as defined in TS 23.228 [15]) when the access is non-3GPP, the AMF may also provide the last known 3GPP access User Location Information with its age, if the UE is still attached to the same AMF for 3GPP access (i.e. valid User Location Information). - 当转发上行 NAS 或者 N2 信令给对等 NF(如至 SMF 或者 SMSF)或在 PDU 会话的用户面连接激活时, AMF 通过接收到上行 NAS 或者 N2 信令的接入网提供从 5G-AN 收到的用户位置信息和接入网的接入类 型(3GPP – 非 3GPP)。AMF 也提供相应的终端时区。额外的,为了满足当接入方式为非 3GPP 接入的 监管要求(例如提供终端提供的位置信息(NPLI),在 TS 23.228 做了定义),AMF 也可提供最后一次 3GPP 接入用户位置信息和其寿命,终端将仍然为 3GPP 接入连接到同样的 AMF。 The User Location Information, the access type and the UE Time Zone may be further provided by SMF to PCF. The PCF may get this information from the SMF in order to provide NPLI to applications (such as IMS) that have requested it. 用户位置信息,接入类型和终端时区会进一步由 SMF 提供给 PCF。PCF 可从 SMF 获取这些信息,提供 NPLI 信息给申请这些的应用(如 IMS)。 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
8 The User Location Information may correspond to 用户的位置信息对应于: - In the case of 3GPP access: Cell-Id. The AMF includes only the Primary Cell-Id even if it had received also the Cell-Id of the Primary cell in the Secondary RAN node from NG-RAN. - 在 3GPP 接入条件:小区 ID(Cell-ID)。AMF 即使从 NG-RAN 收到辅助 RAN 节点的主小区的小区 ID,也仅包含主小区 ID。 - In the case of Untrusted non-3GPP access: a UE local IP address (used to reach the N3IWF) and optionally UDP or TCP source port number (if NAT is detected). - 在非信任非 3GPP 接入场景:终端的本地 IP 地址(用以达到 N3IWF)和可选的 UDP 或 TCP 源端口号 (如果检测到 NAT(地址转换)) - In the case of Trusted non-3GPP access: TNAP Identifier, a UE local IP address (used to reach the TNGF) and optionally UDP or TCP source port number (if NAT is detected). - 在信任的非 3GPP 接入场景:TNAP (Trusted Non-3GPP Access Point)信任非 3GPP 接入点标识,终端 本地 IP 地址和可选的 UDP 或 TCP 源端口号(如果检测到 NAT(地址转换)) The TNAP Identifier shall include the SSID of the access point to which the UE is attached and shall include at least one of the following elements, unless otherwise determined by the TWAN operator's policies: 信任非 3GPP 接入点标识包含终端连接的接入点的 SSID,除非另有由 TWAN(Trusted WLAN Access Networks)运营商策略决定,包含至少一个以下元素, - the BSSID (see IEEE Std 802.11-2012 [106]); - Basic Service Set ID 基本服务集 ID(见 IEEE 标准 802.11-2012) - civic address information of the TNAP to which the UE is attached. - 终端附着的 TNAP 的内部地址信息。 NOTE 1: The SSID can be the same for several TNAPs and SSID only may not provide a location, but it might be sufficient for charging purposes. 注意 1:几个 TNAP 的 SSID 可以是相同的,SSID 可能不提供位置信息,但是这可能对于计费目的是足够 的。 NOTE 2: the BSSID associated with a TNAP is assumed to be static. 注意 2: 和 TNAP 相关联的 BSSID 被假定是静态的。 - In the case of W-5GAN access: The User Location Information for W-5GAN is defined in TS 23.316 [84]. - 在 W-5GAN 接入场景下:用户的 W-5GAN 位置信息在 TS 23.316 中定义。 When the SMF receives a request to provide Access Network Information reporting while there is no action to carry out towards the 5G-AN or the UE (e.g. no QoS flow to create / Update / modify), the SMF may request User Location Information from the AMF. 当 SMF 收到提供接入网信息报告的请求,同时没有朝向 5G-AN 或终端的操作(如没有 QoS 流的创建/更新/修 改),SMF 可能会向 AMF 请求用户位置信息。 The interaction between AMF and SMF(s) for the case of a I-SMF insertion, relocation or removal for a PDU session is described in the clause 5.34. 为 PDU 会话的 I-SMF 插入,重定位或者移除的场景下,AMF 和 SMF 的交互在 5.34 节进行定义。 个人翻译,语言不够通顺,错误不少,还请见谅 3GPP 没有版权,欢迎传播 18602912439
分享到:
收藏