3GPP SA2 #131 國際標準會議報告 · 會議報告 會議類別：其他...
30
會議報告（會議類別：其他） 出席第三代合作夥伴計畫服務及系統面- 3GPP SA2 #131 國際標準會議報告 出國單位：財團法人工業技術研究院 出席人員：陳斯傑 派赴地區：西班牙/聖克魯斯-德特內里費 會議期間：108 年 2 月 25 日至 108 年 3 月 1 日 報告日期：108 年 03 月 29 日
Transcript of 3GPP SA2 #131 國際標準會議報告 · 會議報告 會議類別：其他...
會議報告（會議類別：其他）
出席第三代合作夥伴計畫服務及系統面-
3GPP SA2 #131 國際標準會議報告
出國單位：財團法人工業技術研究院
出席人員：陳斯傑
派赴地區：西班牙/聖克魯斯-德特內里費
會議期間：108 年 2 月 25 日至 108 年 3 月 1 日
報告日期：108 年 03 月 29 日
1
摘 要
本次會議於 2019 年 2 月 25 日～3 月 1 日在西班牙/聖克魯斯-德特內里費
舉辦，參加人數為 152 人。本團隊鎖定第五代行動通訊(5th Generation mobile
communication, 5G)第二階段(Phase II)之工作項目(Work Item, WI)，著重在 3 個
WIs；分別存取數據資料之選取/交換/分岐(Access Traffic Steer, Switching and
Splitting, ATSSS)，於 5G 網路中無線和有線的收斂 (Wireless and Wireline
Convergence in 5G, 5WWC)和增強網路切片(enhance of Network Slicing, eNS)。
ATSSS 是針對使用者數據資料如何在不同的存取網路技術傳輸中切換使用傳
輸技術以及如何與 5G 核心網路(5G Core Network, 5GC)通信交換訊息，而
5WWC為討論在5G網路中加入有線的整合，可以藉由所定義的介面接入5GC，
與 5GC 的功能，進行非存取層(Non Access Stratum, NAS)或存取層(Access
Stratum, AS)的信令或使用者數據資料的傳輸和交換。針對 eNS 則是針對在 5G
第一階段中網路切片(Network Slice, NS)還未解決的問題，進行解決方案討論。
目前， 因 WIs 才剛開始的緣故，主要進程都以研究項目(Study Item, SI)的技術
報告書(Technical Report, TR)內容寫入 5G 的技術規格書(Technical Specification,
TS)為主。
本次會議中，本團隊與其他廠商共同發表技術貢獻文件共 1 篇，投稿於
ATSSS WI 標準文件以及共簽 1 篇第 17 版(Release 17, Rel-17)的 SI。
此次會議本計畫團隊共提 1 篇技術貢獻，並獲大會點名討論，進入 ATSSS
標準文件中。
2
縮寫與中英文對照表
英文全稱 英文縮寫 中文全稱
3rd Generation Partnership Project 3GPP 第三代合作夥伴計畫
5th Generation mobile
communication 5G 第五代行動通訊
Access Stratum AS 存取層
Access Traffic Steering, Switching
and Splitting ATSSS
存取數據資料傳輸流量轉向、
切換和分裂
Broadband Forum BBF 寬頻論壇標準組
Application Function AF 應用功能
Connection Management CM 連線管理
Control Plane CP 控制平面
Change Request CR 更改需求
Data Network DN 數據網路
Data Network Name DNN 數據網路名
enhance of Network Slicing eNS 網路切片改良
Evolve Packet System EPS 演進封包系統
Fully Qualified Domain Name FQDN 完整網域名稱
Fixed Network Residential
Gateway FN-RG 固定網路家用網閘
Internet Protocol IP 網際網路通訊協定
Key Issue KI 關鍵議題
Local Access Data Network LADN 本地存取數據網路
mobility 行動性
Multi-Access PDU MA PDU 多存取數據封包單元
Multipath Transmission Control
Protocol proxy MPTCP proxy 多路徑傳輸控制協定代理
Non Access Stratum NAS 非存取層
Network Exposure Function NEF 網路揭露功能
Network Slice NS 網路切片
Network Slice Instance NSI 網路切片實體
Network Slice Selection
Assistance Information NSSAI 網路切片選取協助資訊
Network Function Repository
Function NRF 網路功能儲存功能
3
英文全稱 英文縮寫 中文全稱
Next Generation Radio Access
Network NG-RAN 下一代無線存取網路
Operation and Maintenance OAM 管理維護系統
Policy and Charge Function PCF 策略與計費功能
Packet Data Unit PDU 數據封包單元
Phase II 第二階段
Public Local Mobile Network PLMN 公用陸地移動網路
Performance Measurement
Function PMF 效能測量功能
Pseudo Change Request P-CR 準修正請求
Quality of Service QoS 服務品質
Release 15 R15, Rel-15 第 15版
Release 16 R16, Rel-16 第 16版
Release 17 R17, Rel-17 第 17版
Residential Gateway RG 住家網關
Registration Area RA 註冊區域
Registration Management RM 註冊管理
Radio Resource Control RRC 無線電資源控制
Service Differentiator SD 服務輔助資訊
Service Management Function SMF 會議管理功能
Subscriber Permanent Identifier SUPI 使用者永久辨識碼
Service Request SR 服務請求
Study Item SI 研究項目
Session Management Function SMF 會議連線管理功能
System and service Aspect
working group #2 SA2 服務及系統面第 2 工作組
Technical Report TR 技術報告書
Technical Specification TS 技術規格書
Transport Converter 運輸轉換器
Trusted Non-3GPP access 可信的非 3GPP 存取
Trusted Non-3GPP Gateway
Function TNGF 可信的非 3GPP 網閘功能
User Data Management UDM 使用者資料庫
User Plane UP 使用者平面
User Plane Function UPF 使用者平面功能
4
英文全稱 英文縮寫 中文全稱
User Equipment UE 使用者設備
User Routing Selection Policy URSP 使用者路由選取策略
Untrusted Non-3GPP access 非可信的非 3GPP 存取
Work Item WI 工作項目
Wireless and Wireline
Convergence in 5G 5WWC
5G 網路中的無線和有線的整
合
5G Core Network 5GC 5G 核心網路
5G Residential Gateway 5G-RG 5G 家用網閘
5
會議解說
本次會議主要針對 5G Phase II 的 SIs 內容提出 CR，並且更新 Rel-15 內容，
讓其升級一版為 Rel-16。目前主要處理 5G Phase II WIs 的 CR 部分，而 P-CR
都延至 4 月份後的會期才開始。 而廠商們都同意先處理 CR，故只有少數 P-CR
因參與廠商覺得 CR 中的內容不符，請求轉至 P-CR 技術貢獻，將之提到為 Rel-
16 WIs 新設立的 TS 中。
6
目 錄
摘 要 ............................................................................................................. 1
縮寫與中英文對照表 ................................................................................... 2
會議解說 ....................................................................................................... 5
一、會議名稱 ............................................................................................... 7
二、參加會議目的及效益 ........................................................................... 7
三、會議時間 ............................................................................................... 7
四、會議地點 ............................................................................................... 7
六、會議紀要 ............................................................................................... 8
七、心得與建議 ......................................................................................... 27
八、附件 ..................................................................................................... 28
7
一、會議名稱
3GPP SA2 #131 會議
二、參加會議目的及效益
參加 5G Phase II WI 標準規範文件制定(Rel-16 WI)。
與其他國際大廠接觸，討論未來下一代網路架構可能的架構，並尋
求未來合作的可能性。
為 Rel-16 標準規範文件布局。
追蹤 3GPP 會議相關 WI 的規格制定方向及進度。
提出貢獻，參與技術討論及協商，確認未來技術運用之機會。
尋求國際大廠合作的可能性。
三、會議時間
February 25 – March 1, 2019
四、會議地點
西班牙/聖克魯斯-德特內里費(Hotel Iberostar Grand Mencey )
8
五、會議議程
會議進行之會議室與時間安排如下：
六、會議紀要
以下講解本次參加會議關注技術貢獻文件：(皆為 Accepted 的文件)
1. Access Traffic Steering, Switching, and Splitting support in the 5G system
architecture (ATSSS)
S2-1902241, 23.501 CR0770R4 (Rel-16, 'B'): QoS for Multi-Access PDU Session,
LG Electronics, Huawei, Hisilicon
此技術貢獻主要提案是針對 ATSSS 中的 MA PDU session 加入 QoS
的支援，釐清除了原有的單一 PDU 以外，MA PDU 也有自行規範的 QoS
能力。
Monday Tuesday Wednesday Thursday revisions only unless
stated differently
Friday (revisions only)
08:00 Q1
10:00
**********************************
08:30 ♠ Opening (1), Agenda (2), Reports (3), Common issues (4.1),
WIDs (7.1), Future Meetings (7.3)
♠ 5G (6.5.1) slicing and non-slicing
5G (6.5.4) Security
♠ eNS (6.21)
Revs of 6.5.1 and 6.5.7
♠ 5G (6.5.1) slicing and non-slicing
5G (6.5.4) Security (6.5.5) QoS
Vertical_LAN (6.15.1) 5G-LAN 6.5.1 and 6.5.7
9:00 Vertical_LAN (6.15.2) TSN 5G_URLLC (6.20)
6.5.7 and 6.5.2
5G_CIoT (6.9) 5G (6.5.9) IW & Migrate 5G_CIoT (6.9) 5G (6.5.9) IW & Migrate
9:00 3GPP maintenance (5.1, 6.1)
5G_CIoT (6.9)
5G_eLCS (6.13) 5WWC (6.7) 5G_eLCS (6.13)
ETSUN (6.12)
5G_eLCS (6.13)
5G (6.5.6) PCC 10:30 Q2
12:30
♠ Vertical_LAN (6.15.3) type a/b ♠ Vertical_LAN (6.15.1) 5G-LAN
♠ Vertical_LAN (6.15.2) TSN ♠ (6.5.2) AC/MM/CM (6.5.7) 3GPP specific
Vertical_LAN (6.15.3) type a/b
5G_eSBA (6.19) 11:30 (6.31) TEI16, 6.5.2
FS_5GSAT_ARCH (6.24) 5G_SRVCC (6.23)
eNA (6.11) FS_RACS (6.28) 3GPP maintenance (5.1, 6.1)
Revs of 5G_CIoT (6.9)
eNA (6.11) eV2XARC (6. 6) 11:30 eNA (6.11)
5G (6.5.10) non-3GPP specific
5G (6.5.3) SM/SC)
5G_eLCS (6.13) 5G (6.5.3) SM/SC) ETSUN (6.12)
5G (6.5.10) non-3GPP specific 5G (6.5.3) SM/SC)
ETSUN (6.12)
5G (6.5.10) non-3GPP specific 5G (6.5.3) SM/SC)
5WWC (6.7) no PCC related ATSSS (6.8) no PCC related
Lunch
14:00 Q3
15:30
♠ 5G_eSBA (6.19) ♠ 5G (6.5.11) Framework 5G_eSBA (6.19)
♠ ATSSS (6.8) no PCC related ♠ 5G_eSBA (6.19) 13:00 FS_UDICoM (6.29)
(6.5.6) PCC, eNA (6.11)
14:00 or later eNS (6.21), everything List of agreed tdocs for block approval
eV2XARC (6. 6) eV2XARC (6. 6) eNA (6.11) eV2XARC (6. 6)
5WWC (6.7)
FS_5GSAT_ARCH (6.24)
3GPP maintenance (5.1, 6.1)
(6.31) TEI16
See AI description above 5WWC (6.7)
16:00
Q4 17:30
♠ (6.5.2) AC/MM/CM
♠ 5G (6.5.5) QoS (6.5.7) 3GPP specific
5G (6.5.4) Security
♠ 5G_eSBA (6.19) 5G_URLLC (6.20) 15:00 block approval of agreed tdocs
Agreed tdocs not available by the time of the block approval may be turned to
status OPEN on request. ♠ Revisions AOB (8)
17:00 Close of meeting (9)
5G_CIoT (6.9) eNA (6.11) eV2XARC (6. 6) 5G (6.5.8) Services Support FS_RACS (6.28)
FS_UDICoM (6.29)
ETSUN (6.12)
ATSSS (6.8)
5WWC (6.7) 18:00
Q5 19:30
5G (6.5.6) PCC 5G_URLLC (6.20) QoS/PCC maintenance (5.2) 5G_URLLC (6.20)
♠ review of the work plan (7.2)
WIDs, TEI proposals (7.1)
Approved tdocs not available after the
meeting may be unapproved and go for email approval instead. 5G_CIoT (6.9) 5G (6.5.8) Services Support 5G_SRVCC (6.23)
IMS & related maint (5.4,6.4) Parlos_SA2 (6.16)
ATSSS (6.8)
5WWC (6.7)
9
S2-1902327, 23.503 CR0187R3 (Rel-16, 'B'): Support of ATSSS rules and URSP
rules for MA-PDU Sessions, Motorola Mobility, Lenovo, Ericsson
此技術貢獻主要是更新 URSP 的規範，將 MA PDU 加入到存取種類，
使得 Rel-16 的使用者裝置可以使用。
更新的 URSP 表格如下：
10
Information
name
Description Category PCF permitted to
modify in URSP
Scope
Route Selection
Descriptor
Precedence
Determines the order in which
the Route Selection Descriptors
are to be applied.
Mandatory
(NOTE 1)
Yes UE context
Route
selection
components
This part defines the route
selection components
Mandatory
(NOTE 2)
SSC Mode
Selection
One single value of SSC mode.
(NOTE 5)
Optional Yes UE context
Network Slice
Selection
Either a single value or a list of
values of S-NSSAI(s).
Optional
(NOTE 3)
Yes UE context
DNN Selection Either a single value or a list of
values of DNN(s).
Optional Yes UE context
PDU Session
Type Selection
One single value of PDU
Session Type
Optional Yes UE context
Non-Seamless
Offload
indication
Indicates if the traffic of the
matching application is to be
offloaded to non-3GPP access
outside of a PDU Session.
Optional
(NOTE 4)
Yes UE context
Access Type
preference
Indicates the preferred Access
Type (3GPP or non-3GPP or
Multi-Access) when the UE
establishes a PDU Session for
the matching application.
Optional Yes UE context
NOTE 1: Every Route Selection Descriptor in the list shall have a different precedence value.
NOTE 2: At least one of the route selection components shall be present.
NOTE 3: When the Subscription Information contains only one S-NSSAI in UDR, the PCF needs not provision the
UE with S-NSSAI in the Network Slice Selection information. The "match all" URSP rule has one S-
NSSAI at most.
NOTE 4: If this indication is present in a Route Selection Descriptor, no other components shall be included in the
Route Selection Descriptor.
NOTE 5: The SSC Mode 3 shall only be used when the PDU Session Type is IP.
S2-1902328, 23.501 CR0785R5 (Rel-16, 'B'): Updating 5.8.2.11 for N4 Rules to
support ATSSS, ETRI
11
此技術貢獻主要更新 MA PDU 在 UP 上的判斷規則，新增判斷條件在
UPF 上封包偵測條件上，讓 UPF 可以判斷每一條的會話是不是屬於 MA
PDU，如果是 MA PDU 的話，將會把相關的會話合併。
S2-1902246, 23.502 CR0993R1 (Rel-16, 'B'): Updates to Nnrf services to include
MA PDU session capability, Ericsson
此技術貢獻講述在 ATSSS 的情境下，UE 嘗試使用 MA PDU 的時候需
要相對應的 PCF，故 PCF 必須向 NRF 註冊，並且告知該 NRF 此 PCF 支
援 MA PDU。當 UE 使用 MA PDU 是，5GC 透過 NRF 將此會話導向有支
援 MA PDU 的 PCF 服務。
S2-1902331, 23.501 CR0740R8 (Rel-16, 'B'): Support of Steering Functions for
ATSSS, Motorola Mobility, Lenovo, Apple, DT, Nokia, Nokia Shanghai Bell, Orange,
Cisco, Korea Telecom, Ericsson, Broadcom, Charter Communications, ZTE
此技術貢獻主要提及 2 項重點：
1. 擬定 MPTCP proxy 為 Transport Converter，根據 Apple 的代表透露，
目前 Transport Converter 已經有相對應的開源軟體，但 ZTE 代表則
說有商業條款，不便明說，可以私下取得相關資料。
2. 因為英文語意的關係，將原本在 TR 中提到的 MA-PDU，在 TS 中
統一修改為 MA PDU。
S2-1902359, 23.501 CR0735R11 (Rel-16, 'B'): ATSSS Support, Motorola
Mobility, Lenovo, Broadcom, Convida Wireless, Huawei, ITRI, Nokia, Nokia
Shanghai Bell, OPPO
此技術貢獻在 TS23.501 提出 ATSSS 的支援，並且附上 ATSSS 的參考
圖，此技術貢獻主要是將 ATSSS 的功能加入，並且明文規定在標準文件
內，此為 Rel-16 的附加功能。
12
Figure 4.2.x-1: Non-roaming and Roaming with Local Breakout architecture for ATSSS
support
Figure 4.2.x-2: Roaming with Home-routed architecture for ATSSS support (UE
registered to the same VPLMN)
AMF
UE
N3
N6
N4
SMFN11
PMFN3
UPF
MPTCP
Proxy
functionality
Non-3GPP Access
3GPP Access
Data Network
N1
N2 N2
PCFN7
MPTCP
functionality
ATSSS-LL
functionality
N1
N3
N4
V-SMFN11
N3
V-UPF
Non-3GPP Access
3GPP Access
N1
N1N2
N2
N6
N4
H-SMF
Data Network
N16
N9
N9
HPLMNVPLMN
H-PCFAMF N7
UE
MPTCP
functionality
ATSSS-LL
functionality PMF
H-UPF
MPTCP
Proxy
functionality
13
Figure 4.2.x-3: Roaming with Home-routed architecture for ATSSS support (UE
registered to different PLMNs)
此外，此技術貢獻也規範了 ATSSS 的架構規則，此架構規則的優先順
序是由上至下區分，附上架構規則表如下：
N3
N4
V-SMFN11
N3
V-UPF
Non-3GPP Access
3GPP Access
N1
N2
N2
N6
N4
H-SMF
Data Network
N16
N9
HPLMNVPLMN
H-PCFAMF N7
UE
MPTCP
functionality
ATSSS-LL
functionality PMF
H-UPF
MPTCP
Proxy
functionality
AMF
N11
N1
14
Information
name
Description Category SMF permitted to
modify in a PDU
context
Scope
Rule
Precedence
Determines the order in which
the ATSSS rule is evaluated in
the UE.
Mandatory
(NOTE 1)
Yes PDU context
Traffic
Descriptor
This part defines the Traffic
descriptor components for the
ATSSS rule.
Mandatory
(NOTE 2)
Application
descriptors
One or more application
identities that identify the
application(s) generating the
traffic (NOTE 3).
Optional Yes PDU context
IP
descriptors
(NOTE 4)
One or more 5-tuples that
identify the destination of IP
traffic.
Optional Yes PDU context
Non-IP
descriptors
(NOTE 4)
One or more descriptors that
identify the destination of non-IP
traffic, i.e. of Ethernet traffic.
Optional Yes PDU context
Access
Selection
Descriptor
This part defines the Access
Selection Descriptor
components for the ATSSS rule.
Mandatory
Steering Mode Identifies the steering mode that
should be applied for the
matching traffic.
Mandatory Yes PDU context
Steering
Functionality
Identifies whether the MPTCP
functionality or the ATSSS-LL
functionality should be applied
for the matching traffic.
Optional
(NOTE 5)
Yes PDU context
NOTE 1: Each ATSSS rule shall have a different precedence value from the other ATSSS rules.
NOTE 2: At least one of the Traffic Descriptor components shall be present.
NOTE 3: An application identity consists of an OSId and an OSAppId.
NOTE 4: An ATSSS rule cannot contain both IP descriptors and Non-IP descriptors.
NOTE 5: If the UE supports only one Steering Functionality, this component may be omitted.
Table 5.x.8-1: Structure of ATSSS Rule
15
S2-1902360, 23.502 CR0866R9 (Rel-16, 'B'): Introduction of ATSSS Procedures
including Multi-Access PDU Session Establishment, Motorola Mobility, Lenovo,
Broadcom, Interdigital, OPPO
此技術貢獻主要說明 UE 啟用 MA PDU 來建立會話的方法與步驟。文
中提及會話建立的方式可沿用單一 PDU 建立的流程，唯獨 Rel-16 的 5GC
接收到 UE 需要 MA PDU 請求時，5GC 需要將相關的會話合併，從單一的
PDU 轉變成 MA PDU 的會話。
S2-1902361, 23.501 CR0921R3 (Rel-16, 'B'): Access Network Performance
Measurements, Nokia, Nokia Shanghai Bell, OPPO
此技術貢獻提出如何有效的使用 MA PDU 所建立的通道。要判斷最佳
通道的方法，最有效的作法是量測通道的效能/延遲，效能越好/延遲越低
者，則能提供 UE 更好的服務。文中提及可以在 UE 和 UPF 上新增效能量
測功能，從 UE 的效能量測功能，定時去測試通道的效能，評估是否需要
切換通道。
下圖附上 PMF 與協定上的角色：
Figure 5.x.x.4-1: UE/UPF measurements related protocol stack for 3GPP access
PMF
protocol
IP
UDP
5G-AN
protocol
layersUDP/IP
GTP-u
L1
L2
PMF
protocol
IP
UDP
5G-AN
protocol
layers
RAN N3 N9UPF UPF
(PSA)UE
UDP/IP
GTP-u
L1
L2
UDP/IP
GTP-u
L1
L2
UDP/IP
GTP-u
L1
L2
16
Figure 5.x.x.4-2: UE/UPF measurements related protocol stack for non-3GPP access
2. Enhancement of Network Slicing (eNS)
S2-1902752, 23.502 CR1074R1 (Rel-16, 'B'): ENS Update handover from 4G to
5G via N26, ZTE Wistron
為 ZTE 所提，將 Rel-16 中 eNS KI#2 所提之 NS 的 EPC 與 5GC 的交
互機制寫入 TS23.501，主要用意是將此功能寫入 Rel-16 的標準文件中。文
件內容沒有新增，可以參照 TR 23.740 KI#2 的總結。
3. Wireline and Wireless in 5G (5WWC)
S2-1901524, 23.502 CR0894R2 (Rel-16, 'B'): Procedures for Trusted Non-3GPP
Access, Motorola Mobility, Lenovo, Broadcom
此技術貢獻是將 Trusted Non-3GPP access 的註冊方法寫入標準文件。
文中解釋，在 Trusted Non-3GPP access 的情境下，接入 5GC 的網閘必須包
含在內，而接入網閘的方法是透過第二層的網路通道連接，UE 只要能接
入此網閘，就能夠與 5GC 接通。詳細的流程如附圖：
PMF
protocol
IPsec
GRE
IP
UDP
Non-
3GPP
IP IP
Non-
3GPP
Lower
Layers
IPsec
GRE
Lower
Layers
IP
PMF
protocol
IP
UDP
N3
stack
N9
stack
N3
stackN9 stack
N3IWFNwu N3 N9
UPF UPF
(PSA)
Untrusted N3GPP
Access Network
UE
17
Figure 4.12a.2.2-1: Registration via trusted non-3GPP access
S2-1902317, 23.502 CR1009R2 (Rel-16, 'B'): PDU Session establishment for
TNGF AMF AUSFUE
7a. N2 msg
(Identity Req./Res.)
4. L2 (EAP-Req/5G-Start)
5. L2 (EAP-Res/5G-NAS/
AN-Params [GUAMI, Selected PLMN ID,
Requested NSSAI, Establishment cause],
NAS-PDU [Registration Request])
6b. N2 msg
(Registration Request)
7b. L2 (EAP-Req/Res/5G-NAS/
NAS-PDU [Identity Req./Res.])
9a. N2 msg
(SMC Request [EAP-Success])9b. L2 (EAP-Req/5G-NAS/
NAS-PDU [SMC Request (EAP-Success)],
TNGF Address)
10c. L2 (EAP-Success)
9c. L2 (EAP-Res/5G-NAS/
NAS-PDU [SMC Complete])
TNAP
Trusted Non-3GPP
Access Network (TNAN)
L2: Ethernet, 802.3, 802.11,
PPP, etc.
8a. AAA Key
Request
(SUPI or SUCI)
8c. AAA Key
Response
(SEAF key,
EAP-Success)
11. Security establishment
using the TNAP key
2. L2 (EAP-Req/Identity)
3. L2 (EAP-Res/Identity)
NAI=username@realm AAA
6a. AMF Selection
8b. Authentication and Key Agreement
TNGF /
TNAP keys
created
(e.g. 4-way handshake for WLAN)
12. Local IP configuration
1. L2 connection
9d. N2 msg
(SMC Complete)
10a. N2 Initial Ctx Setup
Request
(TNGF key)
14. N2 Initial Ctx Setup
Response
10b. AAA
(TNAP key,
EAP-Success)
15b. [NAS over the NWt connection]
NAS Registration Accept
All subsequent NAS messages between UE & TNGF are carried over the NWt connection
15a. N2 msg
(NAS Registration Accept)
NWt connection
establishment
13a. IKE_INIT
13b. IKE_AUTH (IDi, SA, TSi, TSr, AUTH)
13c. IKE_AUTH (IDr, SA, TSi, TSr, AUTH)
0. Trusted Non-3GPP
Access Network Selection
13d. TCP Connection
18
Trusted Non-3GPP Access, Motorola Mobility, Lenovo, Broadcom
此技術貢獻新增相關 Trusted Non-3GPP access 建立會話的流程的說明，
因為 Trusted Non-3GPP access 建立會話的流程大致上不影響現有 untrusted
Non-3GPP access 的流程，故沒有新增任何流程圖。至於 Trusted Non-3GPP
access 的 untrusted Non-3GPP access 的差異則在文中有提及，而詳細內容
需參考 TR 23.716 和未來的 TS 23.316。
S2-1902374, 23.316: UE behind 5G-RG and FN-RG, Ericsson, Motorola
Mobility, Lenovo, ITRI
此技術貢獻是為了 UE 透過 5G-RG 或 FN-RG 連到 5GC 的解決方案。
此技術貢獻一共討論三種狀況，第一是透過 UE 透過 5G-RG 連到 Trusted
Non-3GPP access 再接入 5GC；第二是 UE 透過 5G-RG 連到 untrusted Non-
3GPP access 再接入 5GC；第三是 UE 透過 FN-RG 連到 untrusted Non-3GPP
access 再接入 5GC。
第二和第三種情境類似，UE 都必須藉由 N3IWF 連入 5GC。唯獨第一
是先透過 TNGF 認證後才得以介入 5GC。
附圖說明此三種狀況的架構圖：
Figure 4.8.1: Non-roaming architecture for 5GC capable UE behind 5G-RG using trusted
N3GPP access
N1
UPFN3
5G-RGN3
AMF
UPF
SMF
N2 AMF SMF
N2
W-5GAN5GC-UE TNGFN6 DNN for
5GC-UE
N6
NWt
N11
N4N11
N4
3GPP Access
N2
N1
N1
Ta
19
Figure X.1: Non-roaming architecture for 5GC capable UE behind 5G-RG using
untrusted N3GPP access
Figure X.2: Non-roaming architecture for 5GC capable UE behind FN-RG using
untrusted N3GPP access
S2-1902252, 23.501 CR0746R2 (Rel-16, 'B'): IP addressing enhancements,
Ericsson
此技術貢獻主要點出 RG 支援 IPv6 會在標準文件 TS 23.316 上詳細說
明。
S2-1902323, 23.501 CR0934R2 (Rel-16, 'B'): Support of full Frame Routing
feature, Nokia, Nokia Shanghai Bell
此技術貢獻主要是將 BBF 所需求的框架路由功能寫入 TS 23.501 文件
中，說明 5WWC 的情境下能使用該路由功能。
N1
UPFN3
5G-RGN3
AMF
UPF
SMF
N2 AMF SMF
N2
W-5GAN5GC-UE N3IWFN6 DNN for
5GC-UE
N6
NWu
N11
N4N11
N4
3GPP Access
N2
N1
N1
N1
UPFN3
FN-RGN3
AMF
UPF
SMF
N2 AMF SMF
N2
W-5GAN5GC-UE N3IWFN6 DNN for
5GC-UE
N6
NWu
N11
N4N11
N4
N1
20
S2-1902324, 23.502 CR1039R2 (Rel-16, 'B'): Support of full Frame Routing
feature, Nokia, Nokia Shanghai Bell
此技術貢獻主要新增一個框架路由的參數到會話管理表內，更新的表
格如附圖黃底文字醒目：
21
Subscription data
type
Field Description
Access and Mobility
Subscription data
(data needed for UE
GPSI List List of the GPSI (Generic Public Subscription
Identifier) used both inside and outside of the
3GPP system to address a 3GPP subscription.
Registration and
Mobility
Management)
Internal Group ID-list List of the subscribed internal group(s) that the
UE belongs to.
Subscribed-UE-AMBR The Maximum Aggregated uplink and downlink
MBRs to be shared across all Non-GBR QoS
Flows according to the subscription of the user.
Subscribed S-NSSAIs The Network Slices that the UE subscribes to. In
the roaming case, it indicates the subscribed
Network Slices applicable to the Serving PLMN.
Default S-NSSAIs The Subscribed S-NSSAIs marked as default S-
NSSAI. In the roaming case, only those applicable
to the Serving PLMN.
UE Usage Type As defined in TS 23.501 [2], clause 5.15.7.2.
RAT restriction 3GPP Radio Access Technology(ies) not allowed
the UE to access.
Forbidden area Defines areas in which the UE is not permitted to
initiate any communication with the network.
Service Area Restriction Indicates Allowed areas in which the UE is
permitted to initiate communication with the
network, and Non-allowed areas in which the UE
and the network are not allowed to initiate Service
Request or SM signalling to obtain user services.
Core Network type restriction Defines whether UE is allowed to connect to 5GC
and/or EPC for this PLMN.
RFSP Index An index to specific RRM configuration in the NG-
RAN.
Subscribed Periodic
Registration Timer
Indicates a subscribed Periodic Registration
Timer value.
MPS priority Indicates the user is subscribed to MPS as
indicated in TS 23.501 [2], clause 5.16.5.
MCX priority Indicates the user is subscribed to MCX as
indicated in TS 23.501 [2], clause 5.16.6.
22
UE behavioural information /
Communication patterns
Information on expected UE movement and
communication characteristics. See
clause 4.15.6.2
Steering of Roaming List of preferred PLMN/access technology
combinations or HPLMN indication that no change
of the "Operator Controlled PLMN Selector with
Access Technology" list stored in the UE is
needed (see NOTE 3).
Optionally includes an indication that the UDM
requests an acknowledgement of the reception of
this information from the UE.
Network Slicing Subscription
Change Indicator
When present, indicates to the serving AMF that
the subscription data for network slicing changed
and the UE configuration must be updated.
Tracing Requirements Trace requirements about a UE (e.g. trace
reference, address of the Trace Collection Entity,
etc.) is defined in TS 32.421 [39].
This information is only sent to AMF in the
HPLMN or one of its equivalent PLMN(s).
Inclusion of NSSAI in RRC
Connection Establishment
Allowed
When present, it is used to indicate that the UE is
allowed to include NSSAI in the RRC connection
Establishment in clear text for 3GPP access.
Subscribed DNN list List of the subscribed DNNs for the UE (NOTE 1).
Used to determine the list of LADN available to
the UE as defined in clause 5.6.5 of
TS 23.501 [2].
Slice Selection
Subscription data
(data needed for Slice
Selection as
described in
clause 4.2.2.2.3 and
in clause 4.11.0a.5)
Subscribed S-NSSAIs The Network Slices that the UE subscribes to. In
roaming case, it indicates the subscribed network
slices applicable to the serving PLMN.
UE context in AMF
data
AMF Allocated AMF for the registered UE. Include AMF
address and AMF NF Id.
Access Type 3GPP or non-3GPP access through this AMF
23
Homogenous Support of IMS
Voice over PS Sessions for
AMF
Indicates per UE and AMF if "IMS Voice over PS
Sessions" is homogeneously supported in all TAs
in the serving AMF or homogeneously not
supported, or, support is non-
homogeneous/unknown, see clause 5.16.3.3 of
TS 23.501 [2].
SMF Selection
Subscription data
(data needed for SMF
Selection as
described
in clause 6.3.2 of
TS 23.501 [2])
SUPI Key
SMF Selection Subscription data contains one or more S-NSSAI level
subscription data:
S-NSSAI Indicates the value of the S-NSSAI.
Subscribed DNN list List of the subscribed DNNs for the UE (NOTE 1).
Default DNN The default DNN if the UE does not provide a
DNN (NOTE 2).
LBO Roaming Information Indicates whether LBO roaming is allowed per
DNN, or per (S-NSSAI, subscribed DNN)
Interworking with EPS indication
list
Indicates for which DNN from the Subscribed
DNN list interworking is supported.
UE context in SMF SUPI Key
data PDU Session Id(s) List of PDU Session Id(s) for the UE
For each PDU Session Id:
DNN DNN for the PDU Session.
SMF Allocated SMF for the PDU Session. Includes
SMF IP Address and SMF NF Id.
PGW-C+SMF FQDN The S5/S8 PGW-C+SMF FQDN used for
interworking with EPS.
SMS Management
Subscription data
(data needed by
SMS parameters Indicates SMS parameters subscribed for SMS
service such as SMS teleservice, SMS barring list
SMSF for SMSF
Registration)
Trace Requirements Trace requirements about a UE (e.g. trace
reference, address of the Trace Collection Entity,
etc.) is defined in TS 32.421 [39].
This information is only sent to a SMSF in
HPLMN.
SMS Subscription
data
SMS Subscription Indicates subscription to any SMS delivery service
over NAS irrespective of access type.
(data needed in AMF)
UE Context in SMSF
data
SMSF Information Indicates SMSF allocated for the UE, including
SMSF address and SMSF NF ID.
24
Access Type 3GPP or non-3GPP access through this SMSF
Session Management
Subscription data
(data needed for PDU
GPSI List List of the GPSI (Generic Public Subscription
Identifier) used both inside and outside of the
3GPP system to address a 3GPP subscription.
Session
Establishment)
Internal Group ID-list List of the subscribed internal group(s) that the
UE belongs to.
Trace Requirements Trace requirements about a UE (e.g. trace
reference, address of the Trace Collection Entity,
etc…) is defined in TS 32.421 [39].
This information is only sent to a SMF in the
HPLMN or one of its equivalent PLMN(s).
Session Management Subscription data contains one or more S-NSSAI level
subscription data:
S-NSSAI Indicates the value of the S-NSSAI.
Subscribed DNN list List of the subscribed DNNs for the S-NSSAI
(NOTE 1).
For each DNN in S-NSSAI level subscription data:
DNN DNN for the PDU Session.
UE Address Indicates the subscribed static IP address(es) for
the IPv4 or IPv6 or IPv4v6 type PDU Sessions
accessing the DNN, S-NSSAI.
Frame Routes Set of Frame Route information. A
Frame Route refers to a range of IPv4
addresses / IPv6 Prefixes to associate
with a PDU Session established on this
(DNN, S-NSSAI). See NOTE 4.
Allowed PDU Session Types Indicates the allowed PDU Session Types (IPv4,
IPv6, IPv4v6, Ethernet, and Unstructured) for the
DNN, S-NSSAI.
Default PDU Session Type Indicates the default PDU Session Type for the
DNN, S-NSSAI.
Allowed SSC modes Indicates the allowed SSC modes for the DNN, S-
NSSAI.
Default SSC mode Indicate the default SSC mode for the DNN, S-
NSSAI.
Interworking with EPS indication Indicates whether interworking with EPS is
supported for this DNN and S-NSSAI.
25
5GS Subscribed QoS profile The QoS Flow level QoS parameter values (5QI
and ARP) for the DNN, S-NSSAI (see
clause 5.7.2.7 of TS 23.501 [2]).
Charging Characteristics This information is defined in TS 32.240 [34]; it
may e.g. contain information on how to contact
the Charging Function. This information, when
provided shall override any corresponding
predefined information at the SMF
Subscribed-Session-AMBR The maximum aggregated uplink and downlink
MBRs to be shared across all Non-GBR QoS
Flows in each PDU Session, which are
established for the DNN, S-NSSAI.
Static IP address/prefix Indicate the static IP address/prefix for the DNN,
S-NSSAI.
User Plane Security Policy Indicates the security policy for integrity protection
and encryption for the user plane.
Identifier translation SUPI Corresponding SUPI for input GPSI
(Optional) MSISDN Corresponding GPSI (MSISDN) for input GPSI
(External Identifier). This is optionally provided for
legacy SMS infrastructure not supporting
MSISDN-less SMS. The presence of an MSISDN
should be interpreted as an indication to the NEF
that MSISDN shall be used to identify the UE
when sending the SMS to the SMS-SC via T4.
Intersystem continuity
Context
(DNN, PGW FQDN) list For each DNN, indicates the PGW-C+SMF which
support interworking with EPC.
NOTE 1: The Subscribed DNN list can include a wildcard DNN.
NOTE 2: The default DNN shall not be a wildcard DNN.
NOTE 3: The Steering of Roaming information is protected using the mechanisms defined in TS 33.501 [15].
NOTE 4: Frame Route(s) are defined in TS 23.501 [2]. Frame Route information may refer
to a range of IPv4 addresses (an IPv4 address and an IPv4 address mask) and/or a range
of IPv6 Prefixes (an IPv6 Prefix and an IPv6 Prefix length)
S2-1902369, 23.501 CR0866R8 (Rel-16, 'B'): Clarification of RM and CM for
5G-RG, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell
此技術貢獻主要釐清 5WWC 情況下的 RM 和 CM。技術談及 5G-RG
26
透過有線網閘連入 5GC 的時候，其連線介面額外的介面 Y4 和 Y5。此技
術貢獻是為了將有線網閘納入考慮才將其資訊寫入到 TS 23.501 中。
S2-1902322, 23.316: Location info, N2 releases due to dead peer, and CM for
FN-CRG for cable access., Ericsson, Nokia, Nokia Shanghai Bell
此技術貢獻主要提及 IPv6 的分配方式和規範 IPv6 的使用。說明在
SMF 收到 IPv6 的請求時，會將相應的 IPv6 分配給 5G-RG 或 FN-RG 上使
用。而會話建立的時候，則會由 SMF 分配一組 IPv6 的遮罩網路地址給對
應的 UE。
S2-1902336, 23.316: Session Management of 5G-RG/FN-RG connection to 5GC
in the Wireline AN, Huawei
此技術貢獻主要為釐清 5WWC 情境中的會話管理要如何處理。當中
說明 5WWC 情境下的角色對應，UE 可以透過 5G-RG 和 FN-RG 建立會話
連線。
S2-1902371, 23.501 CR0862R7 (Rel-16, 'B'): UPF Selection influenced by the
indication of the identity/identities of 5G AN N3 User Plane capability, Nokia, Nokia
Shanghai Bell
此技術貢獻提出 UPF 的選擇可以使用 FQDN 當成識別參數，當 UE 透
過 5WWC 環境連上 5GC 的時候可以參照 FQDN，並且選擇對應的 UPF，
然後與其建立 N3 介面，串連 UP。
S2-1902283, 23.316: Wireline access specific QoS parameters, Telstra
此技術貢獻的主要用意是提出 5WWC 環境需要有特殊的 QoS 支援。
針對有線網閘，以目前的 5GC 還沒有規範 QoS 支援其網路速率。此篇技
術貢獻就特別說明，有線網閘需要有層級區分和限制最大和最小網路傳輸
速率。並將這兩個參數加入 UDM 一併管理。
27
七、心得與建議
1. 心得：
本團隊在本會期的主要貢獻為 ATSSS WI，並且也關注 5WWC、eNS
的 2 項 WIs 的發展。本會期針對 5G Phase II 的 WI 提出 CR 至 Rel-
15 的 TS 中，將 TS 從 Rel-15 提升至支援 Rel-16，相關細節將由專
門為 Rel-16 新設立的 TS 來交代。因本會期仍舊以 CR 為主，而新
設立的 TS 尚未提出文件框架，故本會期處理的 P-CR 並不多，P-CR
將在 4 月份會期可以投稿。
目前專注更新 Rel-16 SI 的功能與資訊至 TS23.50x 系列的標準文件
中，為確保相關內容有被納入考量與討論，需要緊密跟進 CR 的發
展，確認專注議題有被寫入標準文件，並且會在接下來的 WI 相關討
論繼續制訂其規範。由於本會期各 WI 的負責人已將接下來的標準
文件框架提出，在下一次會期，即 4 月份會期便能夠開始討論 Rel-
16 的 WIs。
2. 建議：
根據與會中，針對 ATSSS WI 尚有一些相關議題需要深入討論，如
整合有線網路的規範還未制定， 在接下來的會期也可以嘗試的跟進。
而 eNS WI 則確定沿用 Rel-15 的 NS 機制進而延伸，但是明確的方
法還需要在 WI 上討論，所以這也是本團隊應該要關注的議題。
本會期也提出 Rel-17 的 SIs，根據 SIs 提案書的內容，與本團隊早前
規劃的是一致，故本團隊也能提前為 Rel-17 佈局。
28
八、附件
1. 提案清單列表：
3GPP SA2#131 Meeting (25 February 2019 to 1 March 2019) (2,2,2)
1. S2-1902359, “23.501 CR0735R11 (Rel-16, 'B'): ATSSS Support,” Motorola
Mobility, Lenovo, Broadcom, Convida Wireless, Huawei, ITRI, Nokia, Nokia
Shanghai Bell, OPPO, <Accepted>
2. S2-1902374, “23.316: UE behind 5G-RG and FN-RG,” Ericsson, Motorola
Mobility, Lenovo, ITRI, <Accepted>
2. 會議照片集錦：
圖 1:會議場地配置表
29
圖 2: Vertical LAN 會議現場
圖 3: 3GPP SA2 代表成員大合照
