3gpp sa2 #106 meeting 會議報告
TRANSCRIPT
會議報告(會議類別:其他)
3GPP SA2 #106 Meeting 會議報告
出席人員:廖青毓
派赴國家:美國/舊金山
會議期間:103 年 11 月 17 日至 103 年 11 月 21 日
報告日期:103 年 12 月 30 日
1
摘 要
本次 3GPP SA2 會議由 European Friends of 3GPP 主辦,於美國加州
舊金山舉行,共約有 264 人參加。
本團隊依規劃一位成員出席參與 SA2 相關議題之討論。會議摘要與
此行主要任務說明如下:
1. 此次會議中,本團隊針對 Rel-12 的 ProSe 工作項目重點提出修正澄清。
2. 此外,在 SA2 完成 stage 2 的規格書制定後,相關的工作群組例如 SA3,
CT4, CT1 也開始 stage 3 的工作,因此此會議重點中還包括根據 stage 3
的最新決議,更正 stage2 相關規格書。
3. 此次會議與 SA, CT, RAN 各個工作群組一起在舊金山舉行,特地安排
了共同議程討論需要跨工作群協議事項,包括:CT1/SA1 共同議程,
CT1/SA2 共同議程, SA2/CT4 共同議程等。
技術貢獻
這次會議共提出 4 篇提案;其中 MTC Groupe 與 Rel-12 ProSe 相關議題提
案各 2 篇。有 3 篇提案被接受,1 篇被討論。
與會成員與工作分配
成 員 任 務
廖青毓 負責 Rel12-ProSe、GCSE_LTE 以及 Rel-13 MTC 相關
討論
2
目 錄
摘 要 ........................................................................................................... 1
技術貢獻 ..................................................................................................... 1
與會成員與工作分配 ................................................................................ 1
一、會議名稱 ............................................................................................ 3
二、參加會議目的及效益 ........................................................................ 3
三、會議時間 ............................................................................................ 3
四、會議地點 ............................................................................................ 3
五、會議摘要:會議議程及會議紀要 .................................................... 4
六、心得與建議 ...................................................................................... 15
七、附件 ................................................................................................... 16
3
一、會議名稱
3GPP SA2 #106 Meeting
參與代表 264 人
二、參加會議目的及效益
參與 Rel-12 包括 ProSe 及 GCSE_LTE 工作項目的討論
參與 Rel-13 eProSe_Ext, MTC(包括 Group, Monitoring, AESE),
NBIFOM 相關工作項目討論
報告所發表之提案
與其他大廠接觸以討論合作項目
追蹤 3GPP 會議相關工作項目的規格制定方向及進度
三、會議時間
November 17, 2014 ~ November 21, 2014
四、會議地點
美國舊金山(San Francisco, CA, USA)
4
五、會議摘要:會議議程及會議紀要
(一)會議議程:
Monday Tuesday Wednesday Thursday Friday
7:30
Q0
8:55
eCSFB drafting
♠ 08:30-08:55 JM2 with
CT1 on eCSFB evaluation
NBIFOM drafting
♠ eProSe-Ext (7.13)
TEI13 Cat/B C
IMS-Related (7.19.4),
IMS-Related 3GPP
Maint (5.4, 6.1.4, 7.1.4)
♠ <reserved>
NBIFOM
DRAFTING
<reserved>
09.00
Q1
10.30
♠ 09:00 Opening (1),
Agenda (2),Reports (3)
Incoming LSs (4),
WIDs (8.1)
♠ FS_HLCom (7.17)
MCPTT General, System
Aspects, Application and
IMS considerati
ons (7.4.1, 7.4.2, 7.4.3)
♠ MONTE (7.9)
SETA (7.16)
♠ 3GPP Packet
Access Maintenance -
ProSe Corrections
(6.1.1), eProSe-Ext
(7.13),
eWebRTCi (7.12),
SeDoC (7.22)
♠ 07:00
Revisions
11.00
Q2
12.30
♠ CSPS_Coord
(7.3),voE_UTRAN_PP
D (7.15), TEI13 Cat
B/C 3GPP Packet
Access (7.19.1)
Non-3GPP Maintenance
(5,3, 6.1.3)
- - - - - - - - - - - - - - - -
ad hoc drafting ETSI
TC TCCE WG4 + OMA
PCPS in Golden Gate 1
♠ 3GPP Packet Access
maintenance (6.1.1) -
GCSE_LTE
Non-3GPP Maintenance
(5,3, 6.1.3)
♠ GROUPE (7.10)
NBIFOM (7.7)
♠ DECOR (7.6),
GCSE_LTE revisions
UPCON, eWebRTCi,
SETA, PCC/QoS
(LAST in parallel with
GCSE_LTE revisions)
♠ Revisions
14:00
Q3
15:30
♠ AESE (7.8) PCC
aspects handled last
TEI13 Cat B/C
PCC/QoS (7.19.2),
Non-3GPP Access
♠ 3GPP Packet Access
Maintenance (6.1.1) -
ProSe
eWebRTCi (7.12)
♠ 3GPP Packet Access
Maintenance - ProSe
Corrections (6.1.1),
eProSe-Ext (7.13)
PCC/QoS Maint (5.2,
6.1.2)
♠ Revisions
GCSE_LTE,
ProSe/eProSe-Ext
Revisions
NBIFOM,
♠ Revisions,
Planning
future
meetings (8.3),
AOB (9)
16:00 Close of
meeting (10)
5
(7.19.3)
- - - - - - - - - - - - - - - -
ad hoc drafting ETSI
TC TCCE WG4 + OMA
PCPS in Golden Gate 1
IMS-Related
Maintenance
16:00
Q4
17:30
♠ DECOR (7.6)
UPCON (7.2)
- - - - - - - - - - - - - - - -
ad hoc drafting ETSI
TC TCCE WG4 + OMA
PCPS in Golden Gate 1
♠ eProSe-Ext drafting
FMSS (7.21)
MONTE drafting -
location UNION SQUARE
4
♠ eCSFB (7.11)
NBIFOM (7.7)
♠ Revisions
FS_HLCom, 5.1,
eCSFB
6.1.1(besides
GCSE_LTE and
ProSe maint)
Revisions
MCPTT
PCC/QoS Maint
SETA
17:45
Q5
late
♠ 17:45-18:15
JM1 with CT4 and CT1
on ProSe, after JM1:
3GPP Packet Access
Maintenance (6.1.1) -
ProSe
<reserved>
18:00 JM SA1/CT1 with
interested parties from
SA2 on Shared Networks
17:45 DECOR drafting -
19:15
<reserved>
3GPP Packet Maint (5.1,
6.1.1 LS replies, Dual
Connectivity) until 19:30
MCPTT Application and
IMS considerations (7.4.3)
♠ 17:45-19:15
Revisions
GROUPE, MONTE,
AESE
17:45-19:15
Revisions
TEI13 Cat B/C 7.19.2,
7.19.3
N3GPP Maint 6.1.3
FMSS
19:15 Work Planning
(8.2), Planning Future
Meetings (8.3), 9
6
(二)會議紀要
2.1 團隊提案
本團隊參與 SA2 會議,任務除了觀察 SA2 目前的進度與議題討論,於此
次會議 HTC 提出 2 件 MTC GROUPE 提案,2 件 ProSe 提案,會議結論
詳述如下。
提案編號 來源 提案主題 提案成果
S2-144403 HTC,
Alcatel-Lucent,
NEC, KPN
[GROUPE]: 23.769: Update
Solution of Group based messaging
using cell broadcast to support
AESE framework
Accepted
S2-144598 HTC,
Alcatel-Lucent,
KPN
[GROUPE]: 23.769: Resolve FFSs
in Editor's Notes for Solution
5.1.3.1
Accepted
S2-144576 Qualcomm,
HTC
[ProSe]: 23.303 CR0140:
Correction of steps in Match Report
Accepted
S2-144176 HTC [ProSe]: 23.303 CR0144:
Clarification on the EPLMN issue
in ProSe Direct Discovery
Posted
GROUPE, S2-144403: Update Solution of Group based messaging
using cell broadcast to support AESE framework
此提案根據 AESE TR23.708 中 Service Exposure Framework 所決
議的系統架構提出更新支援 group based messaging via cell
broadcasting 的系統架構,如附件圖一所示。
在更新的系統架構中,在 PLMN 中的 SCEF (service capability
exposure framework)可藉由 3GPP 網路的 Tcb 和 Sh 介面提供傳
遞 group based messaging。此外,MTC-IWF 成為 SCEF 的部分功
7
能,可允許 SCEF 直接存取 Tcb 及 Sh 介面,並避免必須增加
MTC-IWF 的新功能。
此提案經過討論後通過。
GROUPE, S2-144598: Resolve FFSs in Editor's Notes for Solution
5.1.3.1
在此提案中,針對 group based messaging via cell broadcasting 方案
中的 FFS (for further study)的註解提出以下澄清:
Editor’s Note: The UE modes (idle/active CS/PS) that can detect the
group trigger/message is FFS:
- 澄清:此方案中並無預期任何 UE 的功能變更,因此接收群組
訊息時可應用的 UE 模式可以包括 idle/active, CS/PS
Editor’s Note: It is FFS what is the granularity of the group ID and
how the network allocates/reallocates one or more group IDs in
which each is associated to one 3GPP internal group identifier for a
specific group messaging service.
- 澄清:在主要議題 group identifier and addressing 中將有針對所
有 group based messaging delivery 方案提出共通的機制。因此
在此方案中不需提出專有方案
Editor’s Note: It is FFS on how to deliver group based messaging for
MTC devices in power saving mode.
8
- 澄清:根據 stage 1 的 TS 22.368 規格書,clause 7.2.14.3 章節:
group based addressing 所述:Verification of receipt of a broadcast
message is not necessary。因此,此提案提出在 group based
messaging delivery 的方案中,並無必要保證廣播的訊息被成功
接收。此外,要系統區分以下可能造成失敗無法接收群組訊息
的成因也是困難的,例如:UE在 limited state,啟動 power saving
mode 模式,或遭受不好的接收訊號條件等。因此,此提案提
出由網路策略來安排群組訊息的重傳機制。
- 在會議中與會代表要求增加以下註明:當 UE 在 power saving
mode 時可能在重傳的規劃中依然無法接收群組訊息。
Editor’s Note: FFS whether the message ID space that can be used for
group messaging based on cell broadcast can be divided between the
network-sharing partners without restricting the usability of the
approach in shared networks.
- 澄清:提出在 Rel-13 方案中不支援共享網路中傳遞群組訊息。
Editor’s Note: roaming considerations for both inbound and outbound
roaming are FFS.
- 澄清:漫遊 UE 接收細胞廣播訊息的方式與漫遊 UE 接收針對
群組發送的細胞廣播訊息,兩者並無差別。
Editor’s Note: How to control that only UEs belonging to a certain
group read respective group messages is FFS.
9
- 澄清:針對安全性議題,將需要 SA3 工作群組提出評估與建
議,因此,提議可發送聯絡函通知 SA3 開始評估此方案的相關
安全議題。
Editor’s Note: The type of controlled access is FFS. Examples
include: network provided dispersion parameters to be used by each
member of the MTC group, or a hashing algorithm based on e.g.,
IMEI that the UE uses to offset access time.
- 澄清:此機制用來控制分散回覆系統訊息的時間,這是避免接
收到群組廣播訊息的 UEs 同時回覆訊息造成系統壅塞。此機制
的設計將可使用 UE 的 IMEI 當做產生隨機回覆時間的依據。
此部分屬於對 UE 的影響,因此改納入方案評估章節。
此提案經過討論後通過。
ProSe, S2-144576: 23.303 CR0140: Correction of steps in Match
Report
此提案由 Qualcomm, HTC 共同提出
更正理由:在 match report 程序當中,Monitoring UE 的 Home
ProSe Function 會根據在 monitoring request 中得到的 Announcing
UE 所註冊的 VPLMN ID 資訊傳送包含 Charging 資料的訊息給
VPLMN 中的 ProSe Function,然而,在兩個程序中間,UE 可能
會因移動而改變了其註冊的 VPLMN,因此 ProSe Function 將無法
傳送訊息給 Announcing UE 真正所在 VPLMN 的 ProSe Function。
10
更正提案:因為 Monitoring UE 將在 match report 程序中提供
Monitored PLMN ID,在 monitoring UE 偵測到 ProSe Application
Code 時,此 Monitored PLMN ID 資訊將可提供 Announcing UE 真
正所在 VPLMN 的資訊,因此訊息將不會傳送至錯誤的 VPLMN
ProSe Function。
此提案經過討論後通過。
ProSe, S2-144176: 23.303 CR0144: Clarification on the EPLMN issue in
ProSe Direct Discovery
此篇提案由 HTC 提出
更正理由:因為 UE 在移動進入所設定的一個 Tracking Area 時,
當此 Tracking Area連結的 PLMN屬於 Equivalent PLMN也不同於
該UE所註冊的 PLMN時,此UE並不會發送Tracking Area Update
Request 訊息給網路重新註冊以更新 HSS 中的註冊 PLMN 資訊。
因此,在服務授權改變時,HSS 無法根據正確的註冊 PLMN 資訊
發送更新訊息給 UE 註冊的 MME 做出改變。
更正提案:要求 UE 在具有 Direct Discovery 的 announcing 授權
時,當發生改變 PLMN 時,將必須發送 Tracking Area Update
Request。
提案討論:在 Stage1 中 Equivalent PLMN 的設定僅根據行動管理
的考量,與服務無關,因此,並無限定 Equivalent PLMN 必須提
11
供相同的服務。因此要求 UE 根據服務改變行動管理策略是不恰
當的,此外,與會公司要求以網路端方案來解決。因此,S2-144575
提出網路端方案的提案成為候選的解決方案。
此提案經過討論後被否決。
2.2 其他會議重點提案
NBIFOM 部分:
NBIFOM, S2-144465: Clarifications and resolution of open issues in
section 7.8 on control mode
此提案由以下公司共同提案簽署:Qualcomm Incorporated,
Samsung, Huawei, Hisilicon, ZTE
UE 可能會依據 ISRP 觸發 UE-initiated IFOM service;PGW 可能
依據從 PCRF 獲得的 PCC rules 觸發 NW-initiated IFOM service。
因為觸發 UE 以及 Network 的依據獨立,因此當兩者共存之時,
就有可能發生衝突。
此提案提出修正 Solution A、 Solution B 的部分文字敘述,以及
提出新的 Solution 以完成 Solution C 中留下 open issues 部分。
新的 Solution 依照 operator 是否想要透過 PCC 控制 routing ,將
Routing Rule 分成兩種:不可被更改以及可被更改。當 UE 收到
的 Routing Rule 中 “Negotiation Indication” 被設為 “forbidden”
12
時,UE 不能更改這個 Routing Rule;反之亦然。
此提案經討論後通過
NBIFOM , S2-144669: Solution for Loss of WLAN Coverage
此提案由以下公司共同提案簽署:Huawei, HiSilicon, InterDigital
Communications, Samsung, ZTE, Qualcomm Incorporated, Intel
此提案提出一個解決方案,在同時擁有 WLAN 以及 3GPP 的連線
下,當UE 離開WLAN/3GPP 覆蓋範圍或是失去WLAN/3GPP 連
線時,如何維持原有的資料傳輸。當 UE 偵測到失去WLAN/3GPP
連線時,UE 透過 MME/TWAN 通知 P-GW 失去連線的 IP flows
訊息,P-GW 轉傳訊息給 PCRF 以產生新的 Routing Rule,並將
原有的在 WLAN/3GPP 上的 IP flows 全部移往 3GPP/WLAN 上。
此提案經討論後通過
NBIFOM, S2-144455: UE impacts on NBIFOM solutions
此提案由 LG Electronics 提出,討論 NBIFOM service 中
control-plane 以及 user-plane 的解決方案對原有 UE 所造成的影
響。
在 control-plane 的部分新增:UE 同時支援 UE-initiated 以及
NW-initiated 的 IFOM 步驟;UE 接受或是拒絕 NW-initiated
IFOM。
在 user-plane 的部分新增:在 UE-initiated 的情況下,UE 傳送一
13
個 “redirection” 的封包;在 NW-initiated 的情況下,UE 接受一
個 “redirection” 的封包。
此提案經討論後通過
NBIFOM, S2-144466: Co-existence with ANDSF for control-plane
signaling solution
提案由以下公司共同提案簽署:LG Electronics, Qualcomm
Incorporated, Huawei, ZTE
在既有的 “與 ANDSF 共存下的 user-plane signaling 解決方案”
中,延伸提出一個新的 control-plane signaling 解決方案:UE 可
以同時使用NBIFOM solution或是 ANDSF traffic steering rules來
當作 IFOM 的規則,UE 不能違反 ANDSF 或是 network policy,
透過禁止的連線轉傳送資料。
此提案經討論後通過
NBIFOM, S2-144016: Handling open issue #2 in NBIFOM control plane
solution
此提案由 Samsung 提出,討論“Open Issue #2: Do we need
additional indication (i.e. null routing rule) as described in some of
the alternatives below to indicate to PGW not to release the
connection even when all the IP flows are moved to another access?”
在 control-plane signaling 的解決方案。
此提案指出 UE 或是 NW 可以透過修改 Routing Rule,維持
14
multiple access PDN connection 其中一個 access 連線,且沒有實
際的資料在此 access 上傳輸。而實際上如何運作,雖然不在 3GPP
的規範之內,但是一些 implementation 的分針還是可以寫在 spec
裡面﹕在 Routing filter 使用 discard port (i.e., port 9);Routing
priority 改為 low。
此提案經討論後通過
2.3 SA2#106 標準會議決議重點提要
1. 根據 SA#65 的決議,3GPP 將成立 SA6 訂定應用層相關標準,並在
Rel-13 先針對 MCPTT(mission critical push to talk)工作項目為主,SA6
已於此次舊金山會議中舉行一連三天的會前會,根據目前 SA2 初步決
議的 MCPTT 系統架構,討論如何整合目前各標準工作組織 OMA,
PCPS 所現有的 PTT 架構。SA6 將於一月正式成立,與 SA2#107 同地
舉行,SA6#1 並將選出第一屆主席。
2. 此次 SA2 會議,針對 Rel-13 的工作項目有許多提案討論,並完成許多
進展,包括:MCPTT, MTC 相關工作項目(例如:Group、Monitoring、
AESE)、NB-IFOM(Network-based IP flow mobility and seamless
offload)、eWebRTC (extended WebRTC)、eCSFB(enhancement of CS
fallback)等,會議結束預期各工作項目進度成果請見 S2-144499。
15
3. 目前在 SA2 通過的工作項目過多超過負載,在 SA#66 根據營運商的需
求將會討論並可能決議 Rel-13 的優先工作項目。
4. 在此會期中已經新增新的議程,可以針對 Rel-13 的規格書提出新的功
能,提案類別屬於 B 或 C,包括:23.060, 23.221, 23.251, 23.272, 23.303,
23.401, 23.468, 23.682。
5. SA2 因過多的工作項目,在有限的會議時間內許多提案未能被討論,
因此在此次會議中研議於 2016 年年初舉辦一次所謂的 electronic
meeting,經由電子郵件群組討論提案,討論結果將具有通過提案決議
的效力。
六、心得與建議
1. 目前在 SA2 有兩個可能具有 UE 影響的 Rel-13 工作項目通過,且尚未
排入議程,包括: Feasibility Study on Co-ordinated P-GW Change for
SIPTO (FS_CSIPTO)以及 New Study Item for Isolated E-UTRAN
Operation for Public Safety (IOPS),建議與會公司可以開始進行提案布
局,在工作群組開始規劃初期即能參與討論並與提案公司建立合作討
論管道。
2. 預計 2015年 3月的 SA plenary將選出新任主席,以及 2015年 4月 SA2
WG 也將選出新任主席及副主席兩席,此次選舉針對副主席人選較往
16
年有更多公司宣布推出候選人參選,並以展開拉票競選活動,競爭非
常激烈。選舉時各候選人將會積極諮詢各個公司的意見並討論在雙方
有興趣發展的工作群組提出可能合作的方向與機會,因此建議各個公
司應該把握此機會好好與各個派出候選人代表的公司接觸與交流。此
外,針對投票權的維護,必須在選舉的該次會議前出席註冊連續至少
兩次會議,也是各公司必須要注意的,以避免喪失投票權。
七、附件
1. Overall SA2 agenda:
Topic Specs Rapporteur
1 Opening of the meeting 09:00 on Monday
2 Approval of the agenda
2.1 Handling of Postponed Work
2.2 IPR Call Reminder
3 Meeting reports
4 Common issues and Incoming LSs
5 Essential Corrections (except Rel-12 features, these are AI 6)
5.1 SAE; CSFB & SMSoSGs; HENB, LIPA_SIPTO, NIMTC,
VPLMN Autonomous CSG Roaming (VCSG), System
Improvements for Machine-Type Communications including
Dual Priority (SIMTC), SA2 Part of GERAN Network
Sharing (FULL_MOCN-GERAN); SA2 Part of GERAN
Gateway Core Network Sharing for GERAN
(GWCN_GERAN), Maintenance of enhancement TEIx CRs,
Alignment to past features (e.g. SAES), Alignment to diverse
features specified by other working groups, etc.
23.060, 23.272,
23.401 Diverse /
None
5.2 SAE: QoS and PCC aspects; PEST, eVocoder, policy related
aspects of other WIs, etc. Rel-11 PCC/QoS: Service
Awareness and Privacy Policies (SAPP), QoS Control Based
on Subscriber Spending Limits (QoS_SSL), Service
Identification for RRC Improvements in GERAN (Stage 2/3)
23.060, 23.401,
23.402 Diverse /
None
17
(SIRIG) , Maintenance of enhancement TEIx CRs, Alignment
to past features (e.g. SAES), Alignment to diverse features
specified by other working groups, etc.
5.3 SAE: 23.402 (including eANDSF, MUPSAP, MAPCON,
FlowMob, SMOG), Data identification in ANDSF (DIDA),
LOcation-Based Selection of gaTEways foR WLAN
(LOBSTER), S2a Mobility based On GTP and WLAN access
to EPC (SaMOG_WLAN) BBF Interworking Building Block
(BBAI) I, II, Maintenance of enhancement TEIx CRs,
Alignment to past features (e.g. SAES), Alignment to diverse
features specified by other working groups, etc.
23.402 Diverse /
None
5.4 Other + IMS Related: (including Emergency, eMBMS, eMPS,
SRVCC etc.), Single Radio Voice Call Continuity from
UTRAN/GERAN to E-UTRAN/HSPA (rSRVCC), Support of
IMS Emergency Sessions with Other Media on UTRAN and
e-UTRAN (NOVES-IMSESOM), Network Provided
Location Information for IMS (NetLoc), Roaming
Architecture for Voice over IMS with Local Breakout
(RAVEL), Single Radio Video Call Continuity for 3G-CS
(vSRVCC), Single Radio Voice Call Continuity (SRVCC)
aspect of enhancements for Multimedia Priority Service
(eMPS_SRVCC) , Maintenance of enhancement TEIx CRs,
Alignment to past features, Alignment to diverse features
specified by other working groups, etc.
23.167, 23.216,
23.228, 23.237 Diverse /
None
6 Release 12 Maintenance, Alignment and Exceptions
6.1 Release 12 Feature Maintenance
6.1.1 3GPP Packet Access: LIPA Mobility and SIPTO at the Local
Network (LIMONET), Machine Type Communication
Enhancements, Small Data and Device Triggering
Enhancements (MTCe-SDDTE) and UE Power
Consumption Optimizations (MTCe-UEPCOP), Core
Network Overload: GTP-C overload (CNO), Small Cell
Enhancement (TEI12, LTE_SC_enh_dualC), Rel-12 3GPP
Packet Access Maintenance: Proximity Services (ProSe)
Group Communication Service Enablers for LTE
(GCSE_LTE)
Includes alignment CRs and LSs for Rel-12 work ongoing in other
WGs.
23.060, 23.401,
23.682 Diverse
18
6.1.2 PCC/QoS Aspects: Usage Monitoring Control enhancement – SA2
Part (UMONC), Application Based Charging (ABC), User
Location Information reporting improvements (CNO-ULI),
Policy and Charging Control for supporting fixed broadband
Access networks from fixted Terminals and NSWO traffic
from 3GPP UEs traffic (P4C-F)
Diverse
6.1.3 Non-3GPP Packet Access Maintenance: Operator Policies for IP
Interface Selection (OPIIS), WLAN Network Selection for
3GPP Terminals (WLAN_NS) , Study on Optimizing
Offloading to WLAN in 3GPP RAT mobility (WORM), S2a
Mobility based On GTP and WLAN access to EPC
(eSaMOG), Network provided Location information for IMS
Trusted WLAN Access Network (TWAN) case
(NETLOC_TWAN), 3GPP/WiFi Interworking
(UTRA_LTE_WLAN_interw-SA2)
Diverse
6.1.4 IMS-Related Maintenance: Short Message Service (SMS) submit
and delivery without MSISDN in IMS (SMSMI), IMS
Business Trunking for IP-PBX in Static Mode of Operation
(BusTI), Real Time Communication (WebRTC) Access to
IMS (IMS_WebRTC)
Diverse
7 Release 13 (Please do not submit documents directly to this agenda
item.)
7.1 Release 13 Maintenance
7.1.4 Rel-13 IMS-Related: Resource Reuse for Multiple Media Sessions
(DRuMS), voice over E-UTRAN Paging Policy Differentiation
(voE_UTRAN_PPD), TEI13 (23.221CR0163R2, 23.292CR0213R2)
23.221,
23.228,
23.292
Diverse
7.2 User Plane Congestion Management (UPCON) 23.705, 23.203,
23.401, 23.060 Alla
Goldner
(Allot
Communicatio
ns)
7.3 Improvements to CS/PS coordination in UTRAN/GERAN
Shared Networks (CSPS_Coord)
23.704, 23.251,
23.401 Roland
Gustafsson
(Ericsson)
7.4 Mission Critical Push-to-Talk (MCPTT)
Analysis of 22.179 and 22.468 requirements is expected.
23.779, 23.179 Randy
Bloomfield
(U. S. Dept.
of Commerce)
7.4.1 MCPTT General Discussion Ibid ibid
7.4.2 MCPTT System Level Considerations ibid ibid
7.4.3 MCPTT Application and IMS Considerations ibid ibid
7.5 Resource Reuse for Multiple Media Sessions (DRuMS) - George
19
Foti (Ericsson)
7.6 Dedicated Core Networks (DECOR) 23.707 Daisuke
Fujishima
(NTT
DoCoMo)
7.7 IP Flow Mobility support for S2a and S2b interfaces
(NBIFOM)
23.861 Tricci So
(ZTE)
7.8 Architecture Enhancements for Service Exposure (AESE) 23.708 Puneet Jain
(Intel)
7.9 Monitoring Enhancements (MONTE) 23.789 Puneet Jain
(Intel)
7.10 Group based Enhancements (GROUPE) 23.769 Wanqiang
Zhang
(Huawei)
7.11 Enhanced CSFB (eCSFB) 23.772 Yang Xu
(China
Unicom)
7.12 Enhancements to WEBRTC ineroperability (eWebRTCi) 23.706 Yu Qing
(China Mobile)
7.13 Extended Proximity-based Services (eProSe-Ext) 23.713 Haris
Zisimopoulos
(Qualcomm
Incorporated)
7.15 - voice over E-UTRAN Paging Policy Differentiation
(voE_UTRAN_PPD)
- Laurent
Thiébaut (Alcatel-Lucen
t)
7.16 - SRVCC Enhancements for Transcoding Avoidance (SETA) 23.7xx George
Foti (Ericsson)
7.17 - Optimizations to Support High Latency Communications
(FS_HLCom)
23.7xx Hans
Rönnecke (Ericsson)
7.19 TEI13 Category B/C - Enhancements and Improvements only.
(Do not submit corrections to this agenda item.)
all
7.19.1 TEI13 Category B/C for 3GPP Packet Access. Do not submit
corrections to this agenda item.
23.060, 23.221,
23.251, 23.272,
23.303, 23.401,
23.468, 23.682
7.19.2 TEI13 Category B/C for PCC/QoS. Do not submit corrections to
this agenda item.
23.060, 23.203,
23.401
7.19.3 TEI13 Category B/C for Non-3GPP Access. Do not submit
corrections to this agenda item.
23.261, 23.402
7.19.4 TEI13 Category B/C for IMS, IMS-Related, Emergency, Other.
Do not submit corrections to this agenda item.
23.167,
23.204,
23.216, 23.228,
23.237, 23.246,
23.271, 23.292
7.21 Flexible Mobile Service Steering (FMSS) 23.7xx Sun Tao
(China
Mobile)
7.22 Service Domain Centralization (SeDoC) 23.7xx Chris Joul
(T-Mobile
20
US)
JM Joint Meetings
JM1 Joint Meeting with CT4, with some participants possibly from CT1
concerning questions on ProSe, including discussion of
C4-142121/S2-143831
JM2 JM with CT1 on TR 23.772 eCSFB evaluation (evaluation P-CRs with
aspects relevant to CT1 are welcome as input to the JM)
23.772
8 Project Planning and Management
8.1 New and Revised Work Items, Cover sheets for completed work items
8.2 Review of the Work Plan
8.3 Planning future meetings
9 AOB
10 Close of the Meeting
16:00 on Friday
2. 補充章節:
Node B BSCUE
Um Gb
Node B RNCUE
Uu Iub
eNode B MMEUE
LTE-Uu S1-MME
CBC
SCS/
Application Servers
CBC-
BSC
Iu-Bc
Tcb
MTC-
IWF
SBcSCEF
HSS
S6m/Sh
SMSC
T4
API(s)
圖一:S2-144403, 8.1.3.1.1-1: CBS/PWS based group messaging AESE based
architecture
21
3. 技術貢獻提案清單
3GPP LTE SA2 #106 Nov. 17-21 2014, San Francisco, CA, USA(4,3,3)
1. S2-144403, “Update Solution of Group based messaging using cell broadcast to
support AESE framework”, HTC, Alcatel-Lucent, NEC, KPN <Accepted>
2. S2-144598, “Resolve FFSs in Editor's Notes for Solution 5.1.3.1”, HTC,
Alcatel-Lucent, KPN < Accepted >
3. S2-144576, “Clarification on the Monitor Request Procedure”, Qualcomm, HTC
< Accepted >
4. S2-144176, “Clarification on the EPLMN issue in ProSe Direct Discovery”,
Qualcomm, HTC <Treated>