3GPP TSG SA WG2 #93 æœƒè­°å ±å‘Š - 網路通訊國際標準分析及參與 ...

3GPP TSG SA WG2 #93
Kundan Tiwari
/
101 10 06
101 10 14
101 10 26

3GPP TSG SA WG2#93 (SA2 meeting #93) 2012 08
12 (Bulgaria / Sofia)
European Friends of 3GPP 142 90
SA2
• SIMTC MTCe
• LIMONET
• Release 12 new SI/WI (Study Item/Work Item)
SIMTC
• Device Triggering
• SMS support in MME/PS-only
• Support of Dual Priority
MTCe (BBBuilding Blocks)
• SDDTE (Small Data and Device Triggering Enhancement)
• UEPCOP (UE Power Consumption Optimizations)
• MONTE (Monitoring Enhancements)
• GROUP (Group based MTC)
SI/WI
• FS_PCS (Providing control of inbound/outbound Connections when a
firewall or NAT is deployed in the PLMN)
• UPCON (User Plan Congestion Management Requirements)
1

Release 12 MTC PCR
Kundan
Tiwari
Rel-12 MTCeRel-11 SIMTCLIMONET
Rel-12 MTCeRel-11 SIMTC LIMONET
LIMONET MTCe
MTCe WLAN interworking
2

3

◦
◦
3GPP TSG SA WG2 #93 Meeting
142
◦
◦
◦
◦
Rel-12
3GPP
October 08, 2012 ~ October 12, 2012
Kempinski Hotel Zografski Sofia
100 James Bourchier Boulevard
1407 Sofia, Bulgaria
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 General issues and Incoming LSs
4

5 Release 7 and earlier
6 Release 8, 9 and 10 Essential Corrections
Member companies are asked to focus their input on Rel-8 and
Rel-9 solely to essential technical corrections of specifications
where doing nothing would lead to frequent and serious
misoperation (FASMO).
(Please do not submit documents directly to this agenda item.)
6.1 SAE: 23.401, 23.060; CSFB & SMSoSGs - 23.272; TEI10:
Essential corrections to 23.401 and 23.060 in release 9 and 10,
HENB, LIPA_SIPTO, NIMTC
NOTE: QoS-related documents belong under 6.2 not 6.1.
(Please do not submit documents directly to this agenda item.
Instead, please submit to 6.1.1 or 6.1.2 as appropriate.)
6.1.1 As 6.1, Without Terminal Impacts
6.1.2 As 6.1, With Terminal Impacts
6.2 SAE: QoS and PCC aspects; PEST, eVocoder, policy related
aspects of other WIs, etc.
6.3 SAE: 23.402 (including eANDSF, MUPSAP, MAPCON,
FlowMob, SMOG)
6.4 Other + IMS Related (e.g Emergency, eMBMS, eMPS, SRVCC
etc.)
6.5 AS/NAS SRVCC capability bits and voice domain selection
(work at SA2 93 on this topic will be driven by incoming LSs and
these will be allocated to agenda 6)
6.6 Inter-RAT HO in Roaming Scenarios for E-UTRAN capable
UEs without a roaming agreement for E-UTRAN service
(work at SA2 93 on this topic will be driven by incoming LSs and
these will be allocated to agenda 6)
7 Release 11 Maintenance
Category F CRs only are expected, except for alignment CRs to
TSs that are affected by agreed added functionality in Release 11,
yet changes have not yet been captured.
(Please do not submit documents directly to this agenda item.)
7.1 3GPP Packet Access + SIMTC +
FULL_MOCN-GERAN/GWCN-GERAN Maintenance
(Please do not submit documents directly to this agenda item.)
7.1.1 3GPP Packet Access: VPLMN Autonomous CSG Roaming (VCSG)
7.1.2 System Improvements for Machine-Type Communications Puneet Jain
5

(SIMTC), including M2M dual priority
(Intel)
7.1.3 SA2 Part of GERAN Network Sharing (FULL_MOCN-GERAN);
SA2 Part of GERAN Gateway Core Network Sharing for GERAN
(GWCN_GERAN)
Nicolas Drevon
(Alcatel-Lucent),
Chris Pudney
(Vodafone)
7.2 PCC/QoS Aspects and SIRIG
Rel-11 PCC/QoS: Service Awareness and Privacy Policies (SAPP),
QoS Control Based on Subscriber Spending Limits (QoS_SSL),
Rel-11 SIRIG Roaming Issue Correction (Cat-F CRs only) (SIRIG)
7.3 Non-3GPP Packet Access Maintenance (Please do not submit
documents directly to this agenda item.)
7.3.1 Non-3GPP Packet Access Maintenance
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)
7.3.2 BBF Interworking Building Block (BBAI) I, II Stefan Rommer
(Ericsson)
7.3.3 BBAI BB1: H(e)NB Local IP Address - Attempt to respond to
outstanding LSs, per SA 57 'action' assigned to SA2.
Stefan Rommer
(Ericsson)
7.4 IMS-Related Maintenace
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)
8 Release 12 (Please do not submit documents directly to this
agenda item.)
8.1 Release 12 Maintenance (for WIDs that complete before the
conclusion of Release 12)
8.2 Machine Type Communications Enhancements for Rel-12 23.887 Puneet Jain (Intel)
(MTCe)
8.2.1 (BB1): Small Data and Device Triggering Enhancements (MTCe-SDDTE) 23.887 Puneet Jain (Intel)
8.2.2 (BB2): Monitoring Enhancements (MTCe-MONTE) 23.887 Puneet Jain (Intel)
8.2.3 (BB3): UE Power Consumption Optimizations (MTCe-UEPCOP) 23.887 Peter Hedman
6

(Ericsson)
8.2.4 (BB4): Group Based MTC (MTCe-GROUP) 23.887 Annemieke Kips
(KPN)
8.3 WID for Policy and Charging Control for supporting fixed
broadband Access networks (P4C)
8.3.1 (BB1): WID for BB for Policy and Charging Control for supporting traffic
from fixed terminals and NSWO traffic from 3GPP UEs traffic (P4C-F)
8.3.2 (BB2): Policy and Charging Control for 3GPP UE terminals connected to
Broadband Forum access network as Trusted network in Interworking
scenario (P4C-TI)
8.3.3 (BB3): Policy and Charging Control for 3GPP UE connected to fixed
broadband access networks via S2b and S2c reference points (P4C-S2bc)
8.3.4 (BB4): Policy and Charging Control for EPC routed traffic over fixed
broadband access networks of 3GPP UEs connected via H(e)NB in
convergent scenarios (P4C-HeNB)
8.3.5 (BB5): Policy and Charging Control for supporting traffic from fixed
terminals in evolved fixed broadband access networks (P4C-FL2)
8.3.6 (BB6): Policy and Charging Control for 3GPP UE connected to fixed
broadband access networks via S2a reference point for EPC routed traffic in
Marco Spini
(Huawei)
23.896 Marco Spini
(Huawei)
23.839 Konstantin
Livanos
(Alcatel-Lucent)
23.896 Tricci So (ZTE)
23.896 Stefan Schmid
(NEC)
23.896 Marco Spini
(Huawei)
23.896 Tricci So (ZTE)
convergence scenario (P4C-TC)
8.4 Interworking between Mobile Operators using the Evolved 23.862 Changhong Shan
Packet System and Data Application Providers (MOSAP)
(Intel)
8.5 LIPA Mobility and SIPTO at the Local Network (LIMONET) 23.859 Fenqin Zhu
(Huawei)
8.6 Operator Policies for IP Interface Selection (OPIIS) 23.853 TaeHyeon Kim
(LG Electronics)
8.7 WLAN Network Selection for 3GPP Terminals (WLAN_NS) 23.865 Vivek Gupta
(Intel)
8.8 Study on Core Network Overload solutions (FS_CNO) 23.843 John
Kaippallimalil
(Huawei)
8.9 Study on S2a Mobility based On GTP and WLAN access to EPC 23.852 Chunhui Zhu
(FS_SaMOG)
(ZTE)
8.10 Study on Usage Monitoring Control enhancement –SA2 Part 23.858 Yifeng Bi (ZTE)
(FS_UMONC)
8.11 Study on Application Based Charging (FS_ABC) 23.800 Alla Goldner
(Allot
Communications)
7

8.12 Study on Optimizing Offloading to WLAN in 3GPP RAT
mobilitty (FS_WORM)
8.13 Study on IP Flow Mobility for S2a & S2b Interfaces
(FS_NBIFOM)
8.14 Technical Enhancements and Improvements (TEI12) –Category
B and C only, no corrections, alignments, clarifications, etc.
8.15 Minor Corrections and Clean Up (TEI12) –Category F only, no
stage 3 impact.
9 IMS Parallel Stream –see separate Table below in Section 2.
23.abc Stefano Faccin
(Research In
Motion)
23.861 Tricci So (ZTE)
10 Project Planning and Management
10.1 New and Revised Work Items
10.2 Review of the Work Plan
10.3 Planning future meetings
11 AOB
12 Close of the Meeting
16:00 on Friday
2. IMS Parallel Stream Agenda
9 IMS Parallel Stream Topics Specs Rapporteur
9.1 Incoming LSs
9.2 CRs on Release 10 and earlier
9.3 CRs on Release 11 Work Items
9.4 Release 12 Work Items
9.4.1 Short Message Service (SMS) submit and delivery without
MSISDN in IMS (SMSMI)
23.863 Curt Wong
(Nokia Siemens
Networks)
9.4.2 Business Trunking for IP-PBX in static mode of operation (BusTI) 23.897 Michele Zarri
(Deutsche
Telekom)
9.4.3 IMS Overload Control (IOC) - Antoine
Mouquet
(Orange), Yu
Qing (China
Mobile)
9.5 Study Items
8

9.6 Any Other Business
9.6.1 Reports
Monday Tuesday Wednesday Thursday Friday
08.00
08:50
♠ 3GPP Pkt Access
Incoming LSs (6, 7);
work on 7.4
♠ MTCe-SDDTE
(8.2.1) FS_NBIFOM (8.13)
BBAI H(e)NB Local
IP Addr (7.3.3)
IMS-Related
overflow (9.X), IMS
Revisions
09.00
09:00 ♠ Opening,
♠ FS_CNO (8.8)
♠ Pre-Rel-11
♠ 3GPP Pkt Access
♠ Parallel Session
Reports,
IMS-Related, Other
Maintenance
with
Reports, Revisions
10.30
Common
(6.4, 7.4)
Terminal Impact
IMS/non-IMS,
(6.1.2)
(1-4) , Rel-7 (5), LSs
Rel-7, 8, 9, 10, 11 (5,
P4C-F (8.3.1)
6, 7)
P4C-TI (8.3.2)
See [NOTE1]
P4C-TC (8.3.6)
Rel-12 WIDs (10.1)
11.00
♠ LSs (Rel-7 to
♠ SIMTC (7.1.2)
♠ MTCe-GROUP
♠ MTCe-MONTE
♠ Revisions
Rel-11) (4), WIDs
(8.2.4)
(8.2.2)
12.30
(10.1)
MOSAP (8.4)
Pre-Rel-11 non3GPP
(6.3)
Non-3GPP
Maintenance (7.3.1)
9

14.00
14:10 ♠
♠ MTCe-UEPCOP
♠ WLAN_NS (8.7)
♠ Revisions
♠ Revisions,
Pre-Rel-11
(8.2.3)
(6.1.1, 6.4, 7.1.2,
Close of meeting (11,
15.30
IMS-Related, Other
7.1.3, 7.4, 8.2.3)
12)
(6.4), Rel-11
IMS-Related (7.4)
Revisions
FS_ABC (8.11)
(6.2, 6.3, 7.2, 8.3.1,
Pre-re-11 PCC/QoS
8.3.2, 8.3.6, 8.4, 8.6)
(6.2), Rel-11
PCC-QoS (7.2)
16.00
♠
♠ 3GPP Pkt Access
♠ LIMONET (8.5)
♠ Revisions
FULL_MOCN-GER
Maintenance without
17:30
AN /
Terminal Impact
GWCN-GERAN
(6.1.1)
(7.1.3)
OPIIS (8.6)
FS_WORM (8.12)
P4C-F (8.3.1)
BUSTI (9.4.2)
IMS Opening (9.1,
9.2, 9.3)
6:10 GERAN
18-18:45 IMS PDN
SHARING ISSUES
Disconnection (6.4)
DRAFTING
() :
Abbreviation
BBAI
BusTI
DIDA
EPC
EPS
FULL-MOCN-GERAN
IWLAN
LIMONET
Topic
Support for BroadBand Forum Accesses Interworking
Business Trunking for IP-PBX in static mode of
operation
Data identification in ANDSF
Evolved Packet Core
Evolved Packet System
SA2 Part of GERAN Network Sharing
Interworking Wireless LAN
LIPA Mobility and SIPTO at the Local Network
10

MOSAP
NETLOC
OPIIS
QoS_SSL
SaMOG
SAPP
SEEE
SIRIG
SIMTC
SMSMI
SRVCC
TEI11
UMONC
VCSG
WORM
Interworking between Mobile Operators using the
Evolved Packet System and Data Application Providers
Network Provided Location Information for IMS
Operator Policies for IP Interface Selection
QoS Control Based on Subscriber Spending Limits
Study on S2a Mobility based On GTP and WLAN
access to EPC
Service Awareness and Privacy Policies
System Enhancements for Energy Efficiency
CN aspects of Service Indication for RRC Improvements
in GERAN
System Improvements to Machine-Type
Communications
Short Message Service (SMS) submit and delivery
without MSISDN in IMS
Single Radio Video Call Continuity for 3G-CS
Technical Enhancements and Improvements for release
11
Usage Monitoring Control enhancement –SA2 Part
VPLMN Autonomous CSG Roaming
Optimizing Offloading to WLAN in 3GPP RAT mobility
3GPP TSC SA WG2 ( SA2)
SA2 2 Rel-12 MTCe
•LS (Liaison Statements)
1. ETSI TC M2M LS IN (S2- 124058)
TS 23.682 device subscription ID ( Rel.11 IMSI)
3GPP access network External Identifier MTC
devices ( MTC applications UE MTC devices) SA2
MTC device External Identifier : domain identifier
11

MTC device MON, local identifier MON
MTC device MTC device MON subscription
identifier (IMSI) ETSI TC M2M M2M Service
Provider access network operator third
party access network operator
M2M services ETSI TC M2M ,
M2M Service Provider MTC device External Identifier
: IMS UE IMS PDN-GW,
Internet service PDN-GW. IMS PDN-GW operator
, PDN-GW UE deactivate IMS PDN connection, UE
ECM_IDLE mode. UE PDN connection
PDN-GW, MME UE bearer deactivation request.
UE IMS PDN connection deactivated,
mobile terminating VoLTE signal, state
ECM-CONNECTED, IMS PDN connection . ,
MT VoLTE signalling, IMS PDN connection
UE unreachable
2. SA2 Tsp device trigger SMS SCS
application port device trigger SMS SMS
Device Trigger messageSA2 S1-124190 CT1
•Release 11 SIMTC :
Release 11 SIMTC triggering
1. S2-123438 ETSI TC M2M LS IN
TS 23.682 device subscription ID ( Rel.11 IMSI)
3GPP access network External Identifier MTC
devices ( MTC applications UE MTC devices) SA2
12

MTC device External Identifier : domain identifier
MTC device MON, local identifier MON
MTC device MTC device MON subscription
identifier (IMSI) ETSI TC M2M M2M Service
Provider access network operator third
party access network operator
M2M services ETSI TC M2M ,
M2M Service Provider MTC device External Identifier
SA2 MTC operators common identifier, dynamic
identifier ,
, release
•Release 12 MTCe :
MTCe (BB, Building Blocks): SDDTE, MONTE, UEPCOP,
GROUP
‣SDDTE (Small Data and Device Triggering Enhancement)
21 6
1. (S2-123642) frequent small data
transmissions SDDTE :
(1) 3GPP system level only: UE applications UE behaviors
application signals 3GPP system signals
(2) application level, outside 3GPP system only:
3GPP scope 3GPP system overall
requirement.
application signals 3GPP system signals SA2
3GPP system
13

(3) : application level 3GPP
system level , , signal
reduction, SDDTE/UEPCOP .
(S2-124036)
2. Smart devices applications keep alive messages
(heartbeats/beacons) 3GPP system frequent small data
transmissions
CMCC S2-123534 always online
(Figure. 2 Figure. 2) application heartbeats PUSH
model
APP1
APP2
APP3
heartbeat
heartbeat
heartbeat
phone
Uni f i ed hear t beat
(backgroud)
APNS
Message
push
Appl i cati on server 1
Appl i cati on server 2
Appl i cati on server 3
APP4
Appl i cat i on hear t beat
( on t he st age)
Appl i cati on server 4
Figure. 1 (Source: S2-123534, Figure in introduction)
3. Provision
always-on policy
1. Login (Addr, Port) and start heartbeats
5. Answer
5. Answer
4. Keep PDP life and NAT conversation
2. Change status(addr,
port, 5-tuple)
AF (Application Server)
6. Inform of stopping heartbeats
Figure. 2 (Source: S2-123534, Figure 5.1.1-x, Network-based Always-online)
14

Figure. 2UE applications application server
application status application server PCRF
P-GW/GGSN keep alive connectionUE applications
keep alive connection small signals
traffic radio connection IP
connection P-GW/GGSN PDP context
UE public IP address
:
3GPP PDP context timer
application level solution application server UE PCP
(Port Control Protocol) OMA
application level 3GPP application level
offline discussion
3. S2-123644 SCS Push Proxy
applications keep alive data applications
(status on-line offline) small data transmission
procedure application server
SCS storing and forwarding PUSH
Proxy external ID public IP address
NAT/firewall SDDTE ( small data
procedure data/message UE) applications
applications keep alive data application
sever UE UE uplink small data transmission
application server online/offline
noted
4.ZTE S2-123543 UE IDLE CONNECTED
15

modes UE power consumption:
UE models
UE CONNECTED mode
noted
5. Samsung S2-123621 UE
traffic pattern (Figure. 3) data connection
connection Noted
Figure. 3 (Source: S2-123621, [Figure 1] number of packets generated from
five popular applications)
‣UEPCOP (UE Power Consumption Optimizations)
MTC devices UE
UE (extended DRX cycle) UE
(extended paging cycle )
12 6
1. Qualcomm RAN UEPCOP WI (working item)
SA2 RAN S2-123814
UE (connected, idle, idle-DRX,
sleep, etc.) power consumption
UEPCOP possible solution types
(CN, Core Network)(RAN, Radio
Access Network) SA2 RAN
16

SA2 :
(1) CN impact only
(2) CN based solution with some RAN impact
(3) CN RAN impact SA2
2. NSN (Nokia Siemens Networks) Ericsson S2-123728
UE paging channel power
consumption
(1) Alternative 1: DRX cycle UE
paging monitoring
||||
(2) Alternative 2: / DRX cycle paging
retransmission time UE paging
message
|||||
indication UE
extended DRX cycle DRX PDN-GW
S2-124729 7.1.3.yy.2 Editor's Note: "It is FFS
whether the SGW is impacted e.g. to keep larger buffers for DL
data” approved
3. Intel RAN2 eDDA (TS 36.331)
S2-123821 UE power saving preference E-UTRAN
UE assistance information (Figure. 4, UE power preference
indication, PPI, E-UTRAN) power saving configuration
17

PPI paging DRX connected mode DRX
S2-124031 approved
UE
EUTRAN
RRC connection reconfiguration
UE Assistance Information
Power preference Ind = low power
Figure. 4 (Source: S2-124031, Figure 7.1.3.X.1-1: UE Assistance Information)
Active Timer
RRC connection
4. S2-123647 UE ECM state:
ECM-DORMANT
(
expires
released
ECM-DORMANT ECM-IDLE ECM-CONNECTED
Periodic TAU timer expires, or
need for mobile originated communications
RRC connection
established
5. Figure. 5) CN UE MM SM registration
UE
Active Timer
expires
RRC connection
released
ECM-DORMANT ECM-IDLE ECM-CONNECTED
Periodic TAU timer expires, or
need for mobile originated communications
RRC connection
established
Figure. 5 (Source: S2-124184, Figure x.y: ECM state model in UE)
: stationary UE ()
update location low power
page UE
paged ECM state
18

UE ECM stateUE paging
UE
RRC state: “RRC-DORMANT”UE ECM-DORMANT
AS (access stratum) NAS (non-access stratum)
timer UE coverage
UE ECM-IDLE coverage
coverage S2-124184 approved
‣MONTE (Monitoring Enhancements)
monitoring configuration monitor (
ports)SA UE-based monitoring
10 7
1. ZTE S2-124004 ( Figure. 6) MTC monitoring
configuration NE (network elements) event
NE report NE
Figure. 6 (Source: S2-124173, Figure 1. MTC Monitoring functionalities)
19

MTC monitoring configuration UE subscription information
SGSN/MME HSS ( Attach Procedure ) UE
MTC monitoring configuration
SCS ( application server configuration
platform) MTC monitoring configuration Tsp MTC
monitoring configuration MTC-IWFMTC-IWF T5
MTC monitoring configuration MME/SGSN(Figure.
7)
UE
SGSN/
MME
HSS
MTC-IWF
SCS
2. Authorization
& load control
1. Monitoring Action Request
(Event Monitoring Data)
4. Subscriber Information Request
3. Monitoring Action Answer
(Monitoring Request-Failure )
5. HSS authorizes
event configuration
details.
6. Subscriber Information Answer
MME is configured to
monitor event
specified by SCS
7. Submit Request
(Monitoring Event Data)
Figure. 7 (Source: S2-124173, Figure 6.1.3.X.2-1: Monitoring call flow using
Tsp and T5)
UE
SGSN
/MME
GGSN
/PGW
HSS
MTC-
IWF
SCS
/AS
1.Detects and Collects MTC events
2. Report collected MTC Events
3.Query SCS/AS
4.Return SCS/AS info
5.MTC event report
20

Figure. 8 (Source: S2-124173, Figure 6.1.3.x.4-1 Reporting Monitoring events
from the SGSN/MME to SCS/AS)
SCSMTC-IWFT5 Tsp (Figure. 8)
S2-124173 approved
2. CMCC S2-123535 communication failure detection
of monitoring event failure cause information
failure cause report of monitoring event
: communication failure cause stage 2
stage 2 report failure failure
cause S2-124129 approved
3. S2-123646 MTC monitoring architecture
requirements(1) One time configuration and reporting
unified interface 3GPP monitoring
report (2) Offering monitoring services to 3GPP external entities
MTC monitoring architecture reference model(Figure.
9)
21

S6m
IWF
Tsp
SCS
Application
Server (AS)
HSS
S6
Sp
SPR
Rx
Online Charging
System
(OCS)
SGSN/MME
PCRF
Sy
Gn/S11
Gxx
Sd
Gx
Gy
BBERF
TDF
PCEF
PCEF
Gateway
Gz
Offline
Charging
System
(OFCS)
Figure. 9 (Source: S2-124174, Figure 6.1.3.x.1-1: Monitoring architecture
model –non-roaming)
architecture requirements 3GPP
Figure. 9 reference architecture MTC monitoring
MTC-IWFPCRFHSS SGSN/MME NE
S2-124131 architecture
requirementsapproved
4. Ericsson S2-123734 monitor USIM first attach
SCS notify USIM first attach event IMSI IMEI
S2-124175
‣GROUP (Group based MTC)
group-based messaginggroup-based policinggroup identifier (
)group-based charging
32 13 7
1. Group-based messaging : CBS group-based
22

messaging MBMS paging
2. S2-123999 CBS group-based messaging reference
architecture model Figure. 10
Um
UE Node B
Uu
UE Node B
LTE-Uu
UE eNode B
Gb
Iub
BSC
CBC-
BSC
RNC
Iu-Bc
S1-MME
Tcb
CBC
SBc
MME
MTC-
IWF
Tsp
SCS
App Server
Figure. 10 (Source: S2-124047, Figure 8.1.3.x.1-1: CBS/PWS based group
messaging architecture)
roaming RAT CBS
SCS operator domain operator access control
CBC NE ( CBC
MTC-IWF ) NE group-based messaging
S2-124047approved
3. S2-124000 MBMS group-based messaging
S2-124152 approved MTC-IWF SCS
BM-SC (Figure. 10 Figure. 11) procedure
Figure. 12
23

VPLMN
HPLMN
UE
E- UTRAN Uu
E- UTRAN
M3
M1
MME
Sm
MBMS
GW
PDN
Gateway
SCS
SGi
Tsp
Tmb
SGmb
Mz
V-BMSC - H-BMSC IWF
SGi-mb
SGi-mb
S6m
App Server
UE
Uu
UTRAN
Iu
SGSN
Sn
HSS
Figure. 10 (Source: S2-124152, Figure 8.1.3.1.1.1-1: MBMS based group
messaging architecture option 1)
VPLMN
HPLMN
UE
E- UTRAN Uu
E- UTRAN
M3
M1
MME
Sm
MBMS
GW
PDN
Gateway
SGi
SGmb
Mz
V-BMSC
H-BMSC
SGi-mb SGi-mb
IWF
Tsp
SCS/AS
UE
Uu
UTRAN
Iu
SGSN
Sn
Figure. 11 (Source: S2-124152, Figure 8.1.3.1.1.2-1: MBMS based group
messaging architecture option 2)
24

UE
UTRAN/EUTRAN
MME/SGSN
BM-SC/MBMS-GW
HSS
MTC-IWF
2. Authorization
3. Subscriber Information Request
4. Subscriber Information Response
5. MBMS Delivery
6. Session Start Request
Selection
6. Session Start Request/Response
7. Group messaging delivery
6. Session Start Response
8. Group messaging confirm
9. Action in response to group messaging
Figure. 12 (Source: S2-124152)
4. S2-124001 paging group-based messaging
MTC-IWF T5 push modelETWS/CMAS-like model
poll model group-based messaging group-based
paging procedure Figure. 13
25

UE
RAN
SGSN
/MME
HLR
/HSS
MTC-
IWF
SCS
/AS
2a.location mapping
1.group message
request
2b.mapping response
4. paging 4.paging via Iu/S1
3.Submit request over T 5
5. group message
retrieval procedure
6. group message delivery response
7.delivery report
8.delivery report
Figure. 13 (Source: S2-124051, Figure 8.1.3.x.3-1 the procedure of group
message delivery)
S2-124051 paging procedure
UE listening to paging ETWS/
CMAS-like
5. Group based policy control S2-124003 SA1
MTC group-based policy control clarifications: (1)
roaming case(2) policy gateway traffic routing
(3) UE policy groups(4) group
members 100 1000 UE (location)
architecture requirements
S2-124180approved
architecture assumptions (1)group based policy control
roaming policy group members(2) group members
(select) PCEF(3) group members HPLMN
GGSN/P-GW(4) group members network capacity
26

operator (5) UE (be associated with)
policy groups(6) dynamic policy control over Rx
interface
architecture requirements (1) group based policy control
policy group DL APN AMBR(2)
device DL/UP APN AMBR
6. Group based charging S2-124046
S2-124154approved
(1) group charging offline charging(2)
charging group bulk CDR device
CDR device level CDR (3) charging
characteristics S-GW/P-GW/GGSN bearer charging
policy Charging characteristics HSS/HLR
SGSN/MME SGSN/MME S-GW/P-GW/GGSN(4)
charging entities charging policy(5) bulk CDR
group ID charging group
•LIMONET :
LIMONET 20 8 7
‣Local PDN connection QoS management
HuaweiHisilicon CATT S2-124065 “Local PDN
connection QoS management” Rel-10 LIPA
PDN connection bearer
TS 23.401 “For this release of the specification no
interface between the L-GW and the PCRF is specified and there is no
support for Dedicated bearers on the PDN connection used for Local IP
Access. The Local GW (L-GW) shall reject any UE requested bearer
resource modification.” LIMONET PCRF
27

Sxx
local network local network
local network QoS
LIMONET TR 23.859 Rel-10
TR 23.859 Rel-10
S2-124065
‣Local PDN connection trigger
Local PDN connection trigger S2-124149(
S2-123724 S2-124066) S2-124150( S2-123808 S2-124067)
S2-124149 SAMSUNG InterDigital “How to trigger LIPA
service activation” MME/SGSN trigger LIPA
service activation Rel-10 LIPA CSG UE
Rel-12 Rel-12
Rel-10 LIPA CSGL-GW
RAN-based DNS-based
MME/SGSN UE LIPA
MME/SGSN UE LIPA LIPA
LIPA
offline discussion LIPA SIPTO@LN
L-GW IP LHN ID offline
discussion indicator L-GW
LIPA SIPTO@LN indicator
S2-124149
S2-124150 LG Electronics InterDigital “Criteria for
network to initiate per APN SIPTO@LN” SIPTO@LN
SIPTO@LN UE
28

APN S2-124150
‣Mobility handlings
Mobility handling LIMONET
‣Local network capability management
Local network capability management CATT
S2-123561 “H(e)NB providing LIPA and SIPTO@LN feature information
to MME/SGSN” P-CR
HeNB SIPTO HeNB
LIPA HeNB SIPTO LIPA
SIPTO LIPA MME/SGSN
HeNB SIPTO LIPA
LIPA per CSG per APN HSS CSG
LIPA SIPTO per APN (subscription)
CSG LIPA SIPTO UE
HeNB
MME/SGSN
HeNB SIPTO LIPA MME/SGSN
RAN based DNS based RAN based
HeNB L-GW IP MME DNS based HeNB
LHN ID MME/SGSN DNS LGW IP
UE LIPA SIPTO@LN HeNB LHN
id MME/SGSN LHN ID query DNA LGW IP
29

‣SIPTO@LN mobility
SIPTO@LN mobility S2-124063(
S2-123804) S2-124064 ( S2-123805)
S2-124063 InterDigital “per APN SIPTO@LN mobility
support” SIPTO@LN
• 1L-GW SIPTO@LN (per APN)
Figure. 14 (Source: S2-124063, Local network supports only SIPTO@LN)
()
SIPTO@LN H(e)NBs CSG
mobility
• 2UE SIPTO@LN LIPA Local
H(e)NB
30

Figure. 15 (Source: S2-124063, Local network supports both LIPA and
SIPTO@LN)
SIPTO@LN mobility UE
SIPTO@LN
S2-124063
‣LGW selection
LGW selection Intel, Verizon, Cisco, Alcatel-Lucent, Huawei,
Samsung S2-124062 ( S2-123797)
“Architecture for SIPTO@LN” P-CR
SIPTO@LN LIPA Mobility Architecture 1 TR 23.859
31

5.4.3 Architecture for SIPTO@LN
Solution X: Reusing LIPA Mobility Architecture 1
SIPTO@LN can be provided using the same architecture as LIPA Mobility
Architecture 1 described in clause 5.2.1.1. For the reader’s convenience, the
architecture figures for LIPA mobility from clause 5.2.1.1 are reproduced here
below as architecture figures for SIPTO@LN.
SGi
L-GW
Sxx
S5
SeGW
X2
HeNB
S1-U
S1-MME
HeNB
GW
S1-U
SGW
Uu
S1-MME
S11
UE
MME
Figure 5.4.3.x-1: SIPTO@LN architecture (EPS diagram for HeNB subsystem)
SGi
L-GW
Sxx
S5
SeGW
Iurh
HNB
Iuh
HNB
GW
Iu-UP
SGW
Uu
Iu-CP
S4
UE
S4-
SGSN
Figure 5.4.3.x-2: SIPTO@LN architecture (EPS diagram for HNB subsystem)
32

Gi
L-GW
Gn
Sxx
Se
GW
Gn
Iurh
HNB
Iuh
HNB
GW
Iu
SGSN
Uu
UE
Figure 5.4.3.x-3: SIPTO@LN architecture (UMTS diagram)
The following open points need to be resolved:
- whether Sxx contains a Control plane component;
- how to establish the secure tunnel transporting the S5 interface between the L-GW and the SGW;
- L-GW selection and addressing;
- discovery of the SIPTO@LN mobility area;
- deactivation of the PDN connection established in SIPTO@LN mode.
S2-124062
‣Architecture Clarification
Architecture clarification Ericsson ST Ericsson
S2-124153 ( S2-123569 S2-124061) “Architecture for
SIPTO@LN” P-CR SIPTO@LN
SIPTO above RAN S2-124153
TR 23.859
33

5.4.3 Architecture for SIPTO@LN
Solution X: Reusing LIPA Mobility Architecture 1
SIPTO@LN can be provided using the same architecture as LIPA Mobility
Architecture 1 described in clause 5.2.1.1. For the reader’s convenience, the
architecture figures for LIPA mobility from clause 5.2.1.1 are reproduced here
below as architecture figures for SIPTO@LN.
SGi
L-GW
Sxx
S5
SeGW
X2
HeNB
S1-U
S1-MME
HeNB
GW
S1-U
SGW
Uu
S1-MME
S11
UE
MME
Figure 5.4.3.x-1: SIPTO@LN architecture (EPS diagram for HeNB subsystem)
SGi
L-GW
Sxx
S5
SeGW
Iurh
HNB
Iuh
HNB
GW
Iu-UP
SGW
Uu
Iu-CP
S4
UE
S4-
SGSN
Figure 5.4.3.x-2: SIPTO@LN architecture (EPS diagram for HNB subsystem)
34

Gi
L-GW
Gn
Sxx
Se
GW
Gn
Iurh
HNB
Iuh
HNB
GW
Iu
SGSN
Uu
UE
Figure 5.4.3.x-3: SIPTO@LN architecture (UMTS diagram)
The following open points need to be resolved:
- whether Sxx contains a Control plane component;
- how to establish the secure tunnel transporting the S5 interface between the L-GW and the SGW;
- L-GW selection and addressing;
- discovery of the SIPTO@LN mobility area;
- deactivation of the PDN connection established in SIPTO@LN mode.
‣Others
Others S2-123829 S2-123830 TR
23.859 Figure A.3.3 Figure A.3.4
commenter ZTE ZTE
•New working items
1. UPCON (User plan congestion management requirements)
Stage 1 FS_UPCON user data RAN user plan
35

congestion active users
stage 2 UPCON TR (Technical Report)
architecture requirements user plan congestion
stage TR SA2 SA Plenary
meeting SA1 TS 22.101
WI S2-124145
•New study item
1. FS_PCP (Providing control of inbound/outbound Connections when a
firewall or NAT is deployed in the PLMN)
3GPP firewall NAT
IETF PCP (Port Control Protocol) UE
inbound/outbound connection port binding PUSH
notification TR
SI S2-124191
•:
S2-123786 ITRI Modifications to solution 6.17 of TR Posted
23.888
S2-123787 ITRI Group-based policy control for roaming
MTC group members
Posted
1. S2-123786: Modifications to solution 6.17 of TR 23.888
UE UE DRX cycle
DL (downlink) traffic UL (uplink) traffic
36

UE DL/UL traffic
2. S2-123787: Group-based policy control for roaming MTC group members
TS 23.887 TR 23.888 group based charging
roaming case architecture requirements UE roaming
operator policy group based policy rules
roaming members
1. Release 12 MTCe small
data transmission and device triggering UE power
consumption optimizationmonitoringgroup-based feature
MTCe key issues
2. 3GPP WLAN interworking
WID for WLAN Network Selection for 3GPP
Terminals FS_NBIFOM
3. SA2 Release 12
1. SA2
2.
3. 3GPP WLAN interworking
Release 12
37

1. .
(1) S2-123786, Modifications to solution 6.17 of TR 23.888, ITRI
(2) S2-123787, Group-based policy control for roaming MTC group
members, ITRI,
38

2.
20121008
3GPP [SA2#93]
2012/10/04 11 00 11 30
2012/10/08 09 00 09 30
ITRI ICL/V00
III
HTC: , Kundan Tiwari
ITRI :
1. 1: III LIMONET
• Downlink user plan data GTP-U tunnel :
1.1 [ITRI]
III LIMONET S2-1238301 "downlink user plan
data" GTP-U tunnel L-GW Source HeNB GTP-U
tunnel "downlink user plan data",
S2-123830 , "downlink user plan data" GTP-U tunnel ,
1 2 "downlink user plan data"
1.2 [III]
1 "downlink user plan data" GTP-U tunnel
L-GW Source HeNB
2 "downlink user plan data" UE Handover
Target HeNB Tunnel 1
UE Source HeNB
39

UE
Source
HeNB
Target
HeNB
Downlink User Plane data
L-GW
1
MME
Serving GW
1. Decision to trigger a
relocation via S1
GTP-U
2. Handover Required (L-GW@LN and TEIDs for Sxx)
3. Handover Request (L-GW@LN and TEIDs for Sxx)
4. Handover Request Ack
6. Handover Command
5. Handover Command
Detach from old cell and
synchronize to new cell
7. Handover Confirm
8. Handover Notify
Uplink User Plane data
9. Modify Bearer Request
11. Modify LIPA Bearer Request
(Target HeNB @ and TEIDs for
Sxx,)
10. Modify Bearer Response
12. Modify LIPA Bearer Response
GTP-U
Uplink User Plane data
Downlink User Plane data
13. UE Context Release Command
2
14. UE Context Release Complete
Figure. 16 (Source S2-123830)
2. 2: HTC MTCe-Group
• [ITRI]: GERAN/UTRAN CBS EUTRAN PWS (ETWS/CMAS)
group paging group message
• [HTC]: group paging EUTRAN ETWS/CMAS
40

GERAN/UTRAN T5 SGSN
GERAN/UTRAN Iu interface .
41