3GPP TSG-SA WG1 Meeting #63                                                                                                                                                                                           S1-134002

Zagreb, Croatia, 19th – 23rd August 2013                                                                                                                                                                                                                                                         (revision of S1-134001)

                                                                                                                                                                                           (revision of S1-134000)

 

Title:                         Draft agenda and schedule with document allocation for SA1#63

Ag. Item:                  1.1

Source:                    SA1 Chairman/SA1 Vice Chairmen/MCC

Contact:                   Mona Mustapha [mona.mustapha@vodafone.com]

 

SA1 DRAFT SCHEDULE

The meeting will start at 09:00 local time on Monday and will close by 16:30 local time on Friday, at the latest.

MEETING ROOMS:

Plenary/Drafting                   = Grand Ballroom B

Breakout (not used) = Grand Ballroom C (Mon – Wed)

 

 

 

Monday

Tuesday

Wednesday

Thursday

Friday

Q0

None

 

 

Drafting:

8.1 RSE

 

 

Q1

09:00

 

10:30

Plenary:

1. Opening

3. Report/Action Items

4. LS

Drafting:

8.1 RSE

Drafting:

9.2 FS_REOPS

Plenary:

Revisions:

5.2 New WIDs

9.2 FS_REOPS

8.1 RSE

4. LS

9.1 FS_ACDC

Plenary:

Revisions

Q2

11:00

 

12:30

Plenary:

4. LS

5.2 New WIDs

Drafting:

8.1 RSE

Drafting:

9.2 FS_REOPS

8.1 RSE

Plenary:

Revisions

9.1 FS_ACDC

9.2 FS_REOPS

7.2 ProSe

5.2 New WIDs

4. LS

10.3 SA1 process improvements

10.2 WI status update

10.1 Work plan

Plenary:

Revisions

 

 

Lunch

 

 

 

 

 

Q3

14:00

 

15:30

Plenary:

5.2 New WIDs

Drafting:

9.1 FS_ACDC

Plenary:

8.2 TEI13

Multiple APN

Revisions:

5.2 New WIDs

Plenary:

Revisions

Plenary:

Revisions

Q4

16:00

 

17:30

Plenary:

5.2 New WIDs

7.1 GCSE_LTE

7.2 ProSe

Drafting overview: RSE, ACDC & REOPS

Drafting:

9.1 FS_ACDC

Plenary:

Revisions

5.2 New WIDs

4. LS

7.2 ProSe

9.1 FS_ACDC

11.1 Taipei meeting info

Plenary:

Revisions

Plenary:

10.2 WI status update

10.1 Work plan

(close by 16:30)

Q5

None

 

Social event

Starts 19:00

 

 

 

NOTE:

!! no Q0 or Q5 slots assigned !!

Slots scheduled based on contributions submitted

Slot allocation is a rough guideline and is subject to change during the meeting week

 


Contribution Guidelines

 

 

 

 

 

 


SA1 AGENDA

 

1  Opening of the meeting

1.1       Agenda and scheduling

AGE

S1-134000

SA1 Chairman

Draft agenda for SA1#63

Revised to S1-134001

 

AGE

S1-134001

SA1 Chairman

Draft agenda and schedule with document allocation for SA1#63

Revised to S1-134002

Revision of S1-134000.

AGE

S1-134002

SA1 Chairman

Final agenda and schedule with document allocation for SA1#63

Approved

Revision of S1-134000.

Revision of S1-134001.

 

 

No presentation

1.2       IPR

 

 

The attention of the delegates to this meeting is drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of.

 Members are hereby invited:

-               to investigate whether their companies owns IPRs which are, or are likely to become essential in respect of the work of 3GPP.

-               to notify the Director-General or the Chairman of their Organizational Partners, of all potential IPRs that their companies may own, by means of the appropriate IPR Statement and the Licensing declaration forms (e.g. see the ETSI IPR forms http://webapp.etsi.org/Ipr/).

 

 

1.3       Previous SA1 meeting report

REP

S1-134004

ETSI Secretariat

Draft Minutes of SA1#62

Revised to S1-134005

 

REP

S1-134005

ETSI Secretariat

Draft Minutes of SA1#62

Approved

Revision of S1-134004.

 

 

No presentation

1.4       Information for delegates

Cont

S1-134007

MCC

SA1 Delegate Guidelines

Withdrawn

 

 

SA1 Delegate Guidelines also available at http://www.3gpp.org/SA1-delegates-survival-guide

 

1.5       Working agreements

 

None

 

2  Issues for early consideration

 

For contributions to this Agenda Item, please contact the Chairman in advance of the meeting.

 

3  Reports and action items

3.1       Report from SA

REP

S1-134003

SA1 Chairman

SA1-related topics at SA#60

Noted

Short presentation of section 5.3

4  Liaison Statements (including related contributions)

TO

S1-134070

S1-133124 / ITU COM 15 – LS 012

(Alcatel-Lucent)

Impact of traffic localization on the transport network

 

Postponed

Postponed from SA1#62

ITU asks if SA1 work on "traffic localisation" where traffic does not traverse the core network will have any impact on the transport network – if yes then they will address this.

 

Response required

LS OUT

S1-134128

Telecom Italia

Impact of traffic localization on the transport network

 

Withdrawn

Postponed from SA1#62

ITU asks if SA1 work on "traffic localisation" where traffic does not traverse the core network will have any impact on the transport network – if yes then they will address this.

 

Response required

Answer to S1-134070.

LS OUT

S1-134026

Alcatel-Lucent

Reply LS re Impact of traffic localization on the transport network

Noted

Response to: LS COM 15 – LS 012 – E Impact of traffic localization on the transport network

LS OUT

S1-134033

China Unicom

Reply LS on Impact of traffic localization on the transport network

Noted

Response to: LS S1-133124 (ITU COM 15 – LS 012 – E) on Impact of traffic localization on the transport network

TO

S1-134080

RT-130039

(Telecom Italia / Alcatel-Lucent)

3GPP Internal LS on the technologies for public protection and disaster relief communications associated with work on wrc-15 agenda item 1.3

Noted, answer in S1-134159

SA1 requested to review ITU work on PPDR and to provide information on related SA1 work in this area.

 

Response required

LS OUT

S1-134055

Alcatel-Lucent

Reply LS re ITU-R WP5A request for input

Revised to S1-134129

Response to: 3GPP Internal LS on the technologies for public protection and disaster relief communications associated with work on wrc-15 agenda item 1.3

LS OUT

S1-134129

Alcatel-Lucent

Reply LS re ITU-R WP5A request for input

Revised to S1-134159

Response to: 3GPP Internal LS on the technologies for public protection and disaster relief communications associated with work on wrc-15 agenda item 1.3

Revision of S1-134055.

LS OUT

S1-134159

Alcatel-Lucent

Reply LS re ITU-R WP5A request for input

Revised to S1-134183

Response to: 3GPP Internal LS on the technologies for public protection and disaster relief communications associated with work on wrc-15 agenda item 1.3

Revision of S1-134055.

Revision of S1-134129.

LS OUT

S1-134183

Alcatel-Lucent

Reply LS re ITU-R WP5A request for input

Approved

Response to: 3GPP Internal LS on the technologies for public protection and disaster relief communications associated with work on wrc-15 agenda item 1.3

Revision of S1-134055.

Revision of S1-134129.

Revision of S1-134159.

 

No presentation

TO

S1-134074

C4-131008

(Vodafone)

Reply LS on Network Resilience for Public Safety communications

Noted

CT4 response to SA1, providing scope and status of their work on network resilience for Rel-11 and Rel-12.

 

Action required if further work in this area is needed

TO

S1-134075

R3-131137

(Vodafone)

Reply LS on Network Resilience for Public Safety Communications

Noted

RAN3 response to SA1, providing scope of their work on network resilience.

 

Action required if further work in this area is needed

TO

S1-134076

CP-130384

(Huawei)

Shifting of missing parts of IODB stage 3 out of Rel-11

Noted

Stage 3 functionality for handling premium rate outgoing communications for IODB moved out of Rel-11.

 

Action required: clean-up Stage 1 specifications

CR

S1-134008

Huawei

22.041 v11.2.0: Removal of IMS Operator Determined Barring Outgoing Premium Rate requirements from Rel-11

Revised to S1-134130

WI code TEI11 Rel-11 CR0018R- Cat F

CR

S1-134130

Huawei

22.041 v11.2.0: Removal of IMS Operator Determined Barring Outgoing Premium Rate requirements from Rel-11

Agreed

WI code TEI11 Rel-11 CR0018R- Cat F

Revision of S1-134008.

WI code TEI8 Rel-11 CR0018R1 Cat A

 

CR

S1-134131

Huawei

Removal of IMS Operator Determined Barring Outgoing Premium Rate requirements from Rel-10

Agreed

WI code TEI8 Rel-10 CR0019R- Cat A

 

CR

S1-134132

Huawei

Removal of IMS Operator Determined Barring Outgoing Premium Rate requirements from Rel-9

Agreed

WI code TEI8 Rel-9 CR0020R- Cat A

 

CR

S1-134133

Huawei

Removal of IMS Operator Determined Barring Outgoing Premium Rate requirements from Rel-8

Agreed

WI code TEI8 Rel-8 CR0021R- Cat F

 

TO

S1-134078

GSMA RCPG 08_0xx

(KPN?)

Response liaison statement to 3GPP SA1 on bulk charging

Postponed

GSMA explains  that there may be benefits to bulk charging.

 

Action required if further work in this area is needed

Cont

S1-134091

KPN

Discussion of liaison statement to 3GPP SA1 on bulk charging

Noted

 

TO

S1-134079

GSMA RCPG 09_010

(Huawei?)

Response LS to 3GP SA1 on CSFB charging

Postponed

GSMA explains that the LTE roaming scenario provided by SA1, where UE roams to an LTE network for PS service and a different PLMN's 3G/2G network for CS services, is not expected to be widely adopted. A few possible issues that need to be resolved was also included.

 

Action required if further work in this area is needed

TO

S1-134083

S3-130879

(Oracle?)

Reply LS on “LS on Notifications on Firewall Traversal from LS Reply SA1 S1-133279

Noted

SA3 explains the possible solutions for IMS firewall traversal where different types of non-3GPP accesses are used.

 

No action required

TO

S1-134086

GSMA Wi-Fi Roaming Task Force

(Orange?)

Wi-Fi Roaming Task Force – Signalling Optimisation

 

Postponed

GSMA asks 3GPP to specify operator policy to dynamically control WLAN authentication/association attempts that require the use of SIM based authentication.

 

Review and update/add SA1 requirements as needed.

LS OUT

S1-134092

Orange

Wi-Fi Roaming Task Force – Signalling Optimisation to SA3, copy to SA2

Withdrawn

 

TO

S1-134089

GSMA

SMS Barring

Postponed

 

LS OUT

S1-134143

Orange

LS on SMSC Usage Restriction

Revised to S1-134162

 

LS OUT

S1-134162

Orange

LS on SMSC Usage Restriction

Revised to S1-134179

Revision of S1-134143.

LS OUT

S1-134179

Orange

LS on SMSC Usage Restriction

Approved

Revision of S1-134143.

Revision of S1-134162.

 

No presentation

CR

S1-134141

Orange

22.088 v11.0.0: SMSC Usage Restriction in Roaming

Revised to S1-134161

WI code xx Rel-13 CR0006R- Cat C

CR

S1-134161

Orange

22.088 v11.0.0: SMSC Usage Restriction in Roaming

Revised to S1-134178

WI code xx  Rel-13 CR0006R- Cat C

Revision of S1-134141.

CR

S1-134178

Orange

22.088 v11.0.0: SMSC Usage Restriction in Roaming

Agreed

WI code xx  Rel-13 CR0006R- Cat C

Revision of S1-134141.

Revision of S1-134161.

 

No presentation

WID

S1-134142

Orange

WID on SMS Fraud in Roaming

Revised to S1-134160

 

WID

S1-134160

Orange

WID on SMS Fraud in Roaming

Withdrawn

Revision of S1-134142.

CC

S1-134085

GSMA Wi-Fi Roaming Task Force

(Alcatel-Lucent?)

Wi-Fi Roaming Task Force – Delivery of voice and real time services over Trusted Wi-Fi

Noted

GSMA identified SA2 work items where further work may be needed to support voice and RT services over WLAN.

 

No action required.

 

Proposed to be noted without presentation

CC

S1-134077

MSG(13)034016r1

(Qualcomm?)

eCall for IMS

Noted

ETSI MSG provides a status update of their eCall for IMS study in TR 103 140 (50% complete, scheduled for publication in early 2014).

 

No action required.

TO

'S1-134088

oneM2M-TP-2013-0307R01

LS on interactions of oneM2M with Underlying Networks

Moved to section 5.2

 

CC

S1-134081

S2-132326

(NEC)

Reply LS on interaction of oneM2M with Underlying Networks

Noted

SA2 summarises their MTC-related work for Rel-10, Rel-11 and Rel-12 and also work related to interaction with an M2M service layer (Tsp).

 

No action required.

 

Proposed to be noted without presentation

CC

S1-134082

S3-130842

(China Mobile)

Reply LS on interaction of oneM2M with Underlying Networks

Noted

SA3 summarises their MTC-related work that could be related to interaction with an M2M service layer.

 

No action required.

 

Proposed to be noted without presentation

CC

S1-134087

ATIS WTSC-2013-039

(T-Mobile)

LS on “CMAS International Roaming” (Issue P0041)

Noted

ATIS informs other groups that they are working on functionality that allows users to receive PWS warning messages when  roaming internationally.

 

No action required.

 

Proposed to be noted without presentation

CC

S1-134072

C1-132674

(Ericsson)

LS on UE Requirements for PSAP callback

Noted

CT1 asks SA2 for more information on how an emergency PSAP callback indicator would be used.

 

No action required.

 

Proposed to be noted without presentation

CC

S1-134073

C1-133592

(Telecom Italia)

Reply LS on IMS interconnection Routing

Noted

CT1 and CT3 explain mechanisms available in IMS to control routing.

 

No action required.

 

Proposed to be noted without presentation

TO

'S1-134084

S5-131036

(NEC?)

LS on OAM for Network Sharing

Moved to section 8.1

 

TO

'S1-134071

S1-133134 / GSMA CLP Doc LS_001

GSMA Connected Living Programme Request for APN Storage in the SIM

Moved to section 5.2

Postponed from SA1#62

5  Study and Work Items: New and Revisions

5.1       Revisions of existing WIDs (including related contributions)

 

No contributions to this agenda item

 

5.2       New Study and Work Items (including related contributions)

APN storage in UICC

TO

S1-134071

S1-133134 / GSMA CLP Doc LS_001

GSMA Connected Living Programme Request for APN Storage in the SIM

Noted

Postponed from SA1#62

Moved from section 4

 

GSMA identified an issue where, for M2M devices, the correct APN to connect to is needed, but current solutions used today incurs significant management overhead, and requests SA1 to consider the issue and possible improvements to the 3GPP specs.

 

Response/action required.

Cont

S1-134014

Gemalto N.V., G&D

Discussion paper on APN storage in UICC

Noted

 

WID

S1-134015

Gemalto, G&D, Morpho, Vodafone

APN storage in UICC

Revised to S1-134148

 

WID

S1-134148

Giesecke & Devrient

Study of need for multiple APNs

Revised to S1-134157

Revision of S1-134015.

WID

S1-134157

Giesecke & Devrient

Study of need for multiple APNs

Revised to S1-134171

Revision of S1-134015.

Revision of S1-134148.

WID

S1-134171

Giesecke & Devrient

Study of need for multiple APNs

Agreed

Revision of S1-134015.

Revision of S1-134148.

Revision of S1-134157.

 

No presentation

CR

S1-134016

Gemalto, et al

22.101 v12.4.0: APN Storage in UICC

Noted

WI code ASinU Rel-13 CR0461R- Cat B

LS OUT

S1-134017

Orange

LS on APN storage in USIM

Revised to S1-134149

Response to: LS (S1-133134) on "GSMA Connected Living Programme Request for APN Storage in the SIM" from GSMA Connected Living Programme.

LS OUT

S1-134149

Orange

LS on APN storage in USIM

Revised to S1-134173

Response to: LS (S1-133134) on "GSMA Connected Living Programme Request for APN Storage in the SIM" from GSMA Connected Living Programme.

Revision of S1-134017.

LS OUT

S1-134173

Orange

LS on APN storage in USIM

Approved

Response to: LS (S1-133134) on "GSMA Connected Living Programme Request for APN Storage in the SIM" from GSMA Connected Living Programme.

Revision of S1-134017.

Revision of S1-134149.

 

No presentation

Calling user importance status identification

Cont

S1-134021

Acer, Inc.

Discussion paper on "Calling User Importance Status Identification"

Noted

 

WID

S1-134022

Acer, Inc.

Draft WID on "Calling User Importance Status Identification”

Noted

 

UE-assisted SIPTO

Cont

S1-134031

Intel

Powerpoint Presentation on UE Assisted Selective IP Traffic Offload WID

Noted

 

WID

S1-134030

Intel

New WID on UE-Assisted Selective IP Traffic Offload (UESIPTO)

Revised to S1-134135

 

WID

S1-134135

Intel

New WID on Co-ordinated Selective IP Traffic Offload (CSIPTO)

Revised to S1-134151

Revision of S1-134030.

WID

S1-134151

Intel

New study on Co-ordinated P-GW change (FS_CSIPTO)

Revised to S1-134158

Revision of S1-134030.

Revision of S1-134135.

WID

S1-134158

Intel

New study on Co-ordinated P-GW change for SIPTO (FS_CSIPTO)

Revised to S1-134176

Revision of S1-134030.

Revision of S1-134135.

Revision of S1-134151.

WID

S1-134176

Intel

New study on Co-ordinated P-GW change for SIPTO (FS_CSIPTO)          

Agreed

Revision of S1-134030.

Revision of S1-134135.

Revision of S1-134151.

Revision of S1-134158.

 

 

No presentation

Service-aware network selection

WID

S1-134032

China Unicom

Study on service-aware network selection in UMTS/HSPA and LTE coexistence

Withdrawn

 

Exposure of network capability

Cont

S1-134044

China Mobile, Huawei

Discussion on Exposure of Network service

Noted

 

WID

S1-134041

China Mobile,  Huawei

Draft Feasibility Study on Exposure of Network Information and Capability

Revised to S1-134134

 

WID

S1-134134

China Mobile,  Huawei

Draft Feasibility Study on Exposure of Network Information and Capability

Revised to S1-134136

Revision of S1-134041.

WID

S1-134136

China Mobile,  Huawei

Draft Feasibility Study on Exposure of Network Information and Capability

Revised to S1-134066

Revision of S1-134041.

Revision of S1-134134.

Device-to-device communication

Cont

S1-134043

KPN

Discussion presentation on device-to-device communication

Noted

 

WID

S1-134042

KPN

Draft WID on Infrastructure based Device-to-device communication

Revised to S1-134090

 

WID

S1-134090

KPN

Draft WID on Infrastructure based Device-to-device communication

Revised to S1-134140

Revision of S1-134042.

WID

S1-134140

KPN

Draft WID on Infrastructure based Device-to-device communication

Revised to S1-134150

Revision of S1-134042.

Revision of S1-134090.

WID

S1-134150

KPN

Draft WID on Infrastructure based Device-to-device communication

Revised to S1-134155

Revision of S1-134042.

Revision of S1-134090.

Revision of S1-134140.

WID

S1-134155

KPN

New WID on Study on enhancements for infrastructure based data communication between devices

Agreed

Revision of S1-134042.

Revision of S1-134090.

Revision of S1-134140.

Revision of S1-134150.

 

No presentation

MBMS for emergency services

WID

S1-134059

Qualcomm Incorporated et al.

Proposed WID on MBMS for Emergency Services (MES)

Revised to S1-134065

 

WID

S1-134065

Qualcomm Incorporated et al.

New WID on Study on MBMS for Emergency Services (FS_MES)

Revised to S1-134069

Revision of S1-134059.

WID

S1-134069

Qualcomm Incorporated et al.

New WID on Study on MBMS for Emergency Services (FS_MES)

Noted

Revision of S1-134059.

Revision of S1-134065.

UPCON management priority

Cont

S1-134024

Qualcomm Inc

Use case for UPCON –  Priority on Demand

Noted

Moved from section 9.3

WID

S1-134060

Qualcomm Incorporated

Proposed WID on User Plane Congestion Management Priority (UPCONP)

Revised to S1-134139

 

WID

S1-134139

Qualcomm Incorporated

Proposed WID on User Plane Congestion Management Priority (UPCONP)

Revised to S1-134152

Revision of S1-134060.

WID

S1-134152

Qualcomm Incorporated

Proposed WID on User Plane Congestion Management Priority (UPCONP)

Withdrawn

Revision of S1-134060.

Revision of S1-134139.

CR

S1-134025

Qualcomm Incorporated

22.101 v12.4.0: Requirements for UPCON - Priority on Demand

Revised to S1-134138

Moved from section 8.2

WI code UPCONP Rel-13 CR0462R- Cat B

CR

S1-134138

Qualcomm Incorporated

22.101 v12.4.0: Requirements for UPCON - Priority on Demand

Withdrawn

Moved from section 8.2

WI code UPCONP Rel-13 CR0462R- Cat B

Revision of S1-134025.

M2M service enablement

TO

S1-134088

oneM2M-TP-2013-0307R01

LS on interactions of oneM2M with Underlying Networks

Noted, answer in S1-134067

Moved from section 4

oneM2M asks SA1 to provide feedback on and to consider a list of 9 items for interworking with M2M service layer for Rel-13.

 

Response/action required.

LS OUT

S1-134067

NEC

LS on interactions of oneM2M with Underlying Networks

Revised to S1-134175

Moved from section 4

oneM2M asks SA1 to provide feedback on and to consider a list of 9 items for interworking with M2M service layer for Rel-13.

 

Response/action required.

Answer to S1-134088.

LS OUT

S1-134175

NEC

LS on interactions of oneM2M with Underlying Networks

Approved

Moved from section 4

oneM2M asks SA1 to provide feedback on and to consider a list of 9 items for interworking with M2M service layer for Rel-13.

 

Response/action required.

Answer to S1-134088.

Revision of S1-134067.

 

 

No presentation

WID

S1-134063

NEC

WID for Support for Interworking with M2M Service Enablement (SIMSE)

Revised to S1-134066

Related LS in S1-134081 and S1-134082

WID

S1-134066

NEC

WID for M2M Service Interworking Support (MSIS)

Revised to S1-134153

Related LS in S1-134081 and S1-134082

Revision of S1-134063 and S1-134136.

WID

S1-134153

NEC

WID for M2M Service Interworking Support (MSIS)

Revised to S1-134156

Related LS in S1-134081 and S1-134082

Revision of S1-134063 and S1-134136.

Revision of S1-134066.

WID

S1-134156

NEC, KPN, China Mobile, Huawei

WID for Service Exposure and Enablement Support (SEES)

Revised to S1-134095

Related LS in S1-134081 and S1-134082

Revision of S1-134063 and S1-134136.

Revision of S1-134066.

Revision of S1-134153.

 

 

No presentation

WID

S1-134095

NEC, KPN, China Mobile, Huawei

WID for Service Exposure and Enablement Support (SEES)

Revised to S1-134174

Related LS in S1-134081 and S1-134082

Revision of S1-134063 and S1-134136.

Revision of S1-134066.

Revision of S1-134153.

 

 

No presentation

Revision of S1-134156.

WID

S1-134174

NEC, KPN, China Mobile, Huawei

WID for Service Exposure and Enablement Support (SEES)

Agreed

Related LS in S1-134081 and S1-134082

Revision of S1-134063 and S1-134136.

Revision of S1-134066.

Revision of S1-134153.

 

No presentation

Revision of S1-134156.

Revision of S1-134095.

 

No presentation

5.3       Proposals for new work (precursor to future Study and Work Items)

 

No contributions to this agenda item

 

6  Rel-11 and earlier contributions

 

No contributions to this agenda item

 

7  Rel-12 Contributions

7.1       GCSE_LTE: Group communication system enablers for LTE [SP-130326]

CR

S1-134057

Broadcom Corporation

22.468 v12.0.0: Support for non-GCSE communication media

Noted

Moved from section 8.2

WI code TEI13 Rel-13 CR0001R- Cat B

Comment: New WID is needed to introduce new functionality for Rel-13 (current release), TEI13 cannot be used.

7.2       ProSe: Proximity-based services [SP-130030]

CR

S1-134012

Alcatel-Lucent, Department of Commerce, Qualcomm

22.115 v12.1.0: Removing ProSe definitions that were added to 21.905

Agreed

WI code ProSe Rel-12 CR0071R- Cat D

CR

S1-134013

Alcatel-Lucent, Department of Commerce, Qualcomm

22.278 v12.3.0: Removing ProSe definitions that were added to 21.905

Agreed

WI code ProSe Rel-12 CR0186R- Cat D

CR

S1-134018

LG Electronics, Inc.

22.278 v12.3.0: Editorial clarification on the ProSe Communication part in ProSe Feature description

Revised to S1-134144

WI code ProSe Rel-12 CR0187R0 Cat F

Comment: remove revision marks from cover page. First version of CR is rev '-' not '0'.

CR

S1-134144

LG Electronics, Inc.

22.278 v12.3.0: Editorial clarification on the ProSe Communication part in ProSe Feature description

Agreed

WI code ProSe Rel-12 CR0187R0 Cat F

Comment: remove revision marks from cover page. First version of CR is rev '-' not '0'.

Revision of S1-134018.

CR

S1-134019

LG Electronics, Inc.

22.278 v12.3.0: Some clarification on the agreed wording on “concurrent” or “concurrently” in ProSe

Revised to S1-134145

WI code ProSe Rel-12 CR0188R0 Cat F

Comment: remove revision marks from cover page. First version of CR is rev '-' not '0'.

CR

S1-134145

LG Electronics, Inc.

22.278 v12.3.0: Some clarification on the agreed wording on “concurrent” or “concurrently” in ProSe

Agreed

WI code ProSe Rel-12 CR0188R0 Cat F

Comment: remove revision marks from cover page. First version of CR is rev '-' not '0'.

Revision of S1-134019.

 

No presentation

Cont

S1-134047

UK Home Office

Discussion on End-to-End security for Public-Safety ProSe

Noted

 

CR

S1-134046

UK Home Office

22.278 v12.3.0: Clarify requirements for ProSe Security in Public Safety applications.

Revised to S1-134146

WI code ProSe Rel-12 CRxxxR- Cat F

Comment: CR number required, changes should be shown as revision marks

CR

S1-134146

UK Home Office

22.278 v12.3.0: Clarify requirements for ProSe Security in Public Safety applications.

Revised to S1-134170

WI code ProSe Rel-12 CR0189R- Cat F

Comment: CR number required, changes should be shown as revision marks

Revision of S1-134046.

CR

S1-134170

UK Home Office

22.278 v12.3.0: Clarify requirements for ProSe Security in Public Safety applications.

Agreed

WI code ProSe Rel-12 CR0189R- Cat F

Comment: CR number required, changes should be shown as revision marks

Revision of S1-134046.

Revision of S1-134146.

 

 

No presentation

7.3       IMS_WebRTC: Web Real Time Communication access to IMS [SP-130325]

 

No contributions to this agenda item

 

7.4       Other Rel-12 contributions

 

No contributions to this agenda item

 

8  Rel-13 Contributions

8.1       RSE: RAN Sharing Enhancements [SP-130330], includes FS_RSE [SP-110820]

Cont

S1-134009

NEC

22.101 v12.0.0: Requirements for RAN Sharing Enhancements

Revised to S1-134103

WI code RSE Rel-13 CR????R- Cat B

Comment: CR number required

Cont

S1-134103

NEC

22.101 v12.0.0: Requirements for RAN Sharing Enhancements

Revised to S1-134180

WI code RSE Rel-13 CR????R- Cat B

Comment: CR number required

Revision of S1-134009, S1-134061, S1-134062 and S1-134048.

Cont

S1-134180

NEC

22.101 v12.0.0: Requirements for RAN Sharing Enhancements

Agreed

WI code RSE Rel-13 CR????R- Cat B

Comment: CR number required

Revision of S1-134009, S1-134061, S1-134062 and S1-134048.

Revision of S1-134103.

 

No presentation

Cont

S1-134048

Huawei, Alcatel-Lucent

22.101 v12.0.0: Requirements proposed for RAN Sharing Enhancements

Revised to S1-134103

WI code RSE Rel-13 CRDRAFTR- Cat B

Cont

S1-134062

Telecom Italia

Comments to “Proposed Requirements for RAN Sharing Enhancements”

Revised to S1-134103

 

Cont

S1-134061

NEC

Discussion on including a feature description into the RSE CR

Revised to S1-134103

 

TO

S1-134084

S5-131036

(NEC?)

LS on OAM for Network Sharing

Noted, answer in S1-134102

Moved from section 4

 

SA5 shares their draft TR on OAM for Network Sharing and indicates their intention to start related normative work. SA5 requests feedback on their TR and also to consider the terminology used in their TR (as it is different from SA1 terminology).

 

Response/action required: review TR and SA5 terminology, consider alignment of terminology with RSE.

 

To be reviewed further in RSE drafting session

LS OUT

S1-134102

NEC

LS on OAM for Network Sharing

Revised to S1-134181

Answer to S1-134084.

LS OUT

S1-134181

NEC

LS on OAM for Network Sharing

Approved

Answer to S1-134084.

Revision of S1-134102.

 

 

No presentation

8.1.1   RSE Drafting session information

AGE

S1-134100

Rapporteur

RSE Drafting Agenda

Noted

 

REP

S1-134101

Rapporteur

RSE Drafting Report

Approved

 

Summary of drafting session:

The target of the drafting session was to:

-       Create requirements for RSE in a CR to 22.101 (Rel-13). This has been partially achieved, the resulting CR is in S1-134103.
Agreement could be reached on

o    Allocation of Shared E-UTRAN resources

o    OAM Access to the Hosting E-UTRAN

o    Generation and retrieval of usage and accounting information

o    MDT Collection

o    PWS support of Shared E-UTRAN

-       Further work in a second batch of CRs is expected at the next meeting. This should particularly address the remaining  - unclear or potentially unnecessary -  requirements which were left over from S1-134009

A draft of the answer LS in S1-134102 to SA5 was presented but not agreed and requires more offline work. A proposal will be presented to SA1 plenary

 

S1-134104

 

Tdoc number for allocation in drafting session

Drafting

 

8.2       TEI13 contributions

 

TEI13 CRs will only be accepted if there is no impact to Stage 2/3 or for alignment purposes with Stage 2/3

 

CR

S1-134037

China Mobile

22.368 v12.2.0: MTC Device and Group Based MTC Feature Conflict Avoidance Policy Requirement

Revised to S1-134093

WI code Tel13 Rel-13 CR0149R- Cat F

Comment: TEI13 should not be used to maintain requirements of the current Stage 1 release. A new WID for maintenance is required. Clean-up is required for all MTCe-SRM requirements not implemented in Rel-12 and whether they should be brought forward to Rel-13, see process defined here.

CR

S1-134093

China Mobile

22.368 v12.2.0: MTC Device and Group Based MTC Feature Conflict Avoidance Policy Requirement

Noted

WI code Tel13 Rel-13 CR0149R- Cat F

Comment: TEI13 should not be used to maintain requirements of the current Stage 1 release. A new WID for maintenance is required. Clean-up is required for all MTCe-SRM requirements not implemented in Rel-12 and whether they should be brought forward to Rel-13, see process defined here.

Revision of S1-134037.

CR

S1-134038

China Mobile

22.368 v12.2.0: To Clarify MTC Device Location Monitoring

Revised to S1-134094

WI code Tel13 Rel-13 CR0150R- Cat F

Comment: see comment for previous document

CR

S1-134094

China Mobile

22.368 v12.2.0: To Clarify MTC Device Location Monitoring

Noted

WI code Tel13 Rel-13 CR0150R- Cat F

Comment: see comment for previous document

Revision of S1-134038.

CR

'S1-134057

Broadcom Corporation

22.468 v12.0.0: Support for non-GCSE communication media

Moved to section 7.1

WI code TEI13 Rel-13 CR0001R- Cat B

 

CR

'S1-134025

Qualcomm Incorporated

22.101 v12.4.0: Requirements for UPCON - Priority on Demand

Moved to section 5.2

WI code UPCONP Rel-13 CR0462R- Cat B

9  Study Item contributions

9.1       FS_ACDC: Application specific congestion control for data communication [SP-120546]

WID

S1-134034

NTT DOCOMO

Proposed update of WID for Study on Application specific Congestion control for Data Communication (FS_ACDC)

Revised to S1-134169

ACDC drafting session:

Administrative changes only: time scale, rapporteur’s name, and a few typos.SA#63, March 2014, is set as TR approval timing.

 

In the session, there were comments as follows:

- Timing of sending TR to SA should be different for Information and for Approval.

- Co-signers’ names: to add TeliaSonera, Intel, MediaTek, and LGE. to change to NSN, Blackberry.

 

On the SA1 reflector, there was a proposal to remove the last two sentences of the first paragraph of section3, Justification.

WID

S1-134169

NTT DOCOMO

Proposed update of WID for Study on Application specific Congestion control for Data Communication (FS_ACDC)

Agreed

ACDC drafting session:

Administrative changes only: time scale, rapporteur’s name, and a few typos.SA#63, March 2014, is set as TR approval timing.

 

In the session, there were comments as follows:

- Timing of sending TR to SA should be different for Information and for Approval.

- Co-signers’ names: to add TeliaSonera, Intel, MediaTek, and LGE. to change to NSN, Blackberry.

 

On the SA1 reflector, there was a proposal to remove the last two sentences of the first paragraph of section3, Justification.

Revision of S1-134034.

 

 

No presentation

Cont

S1-134023

Qualcomm Incorporated

Scope of ASAC Feasibility Study

Revised to S1-134107

ACDC drafting session:

Proposal for sorting out FS_ACDC discussion. It is proposed to place after the Use Cases clause a new clause for Key Issues and High Level Requirements. Four Key Issues have been analyzed: applicability, control and triggering, effects on existing communication, control range and proportionality.

 

The session discussed how to incorporate this proposal and agreed to extract a few sentences that would fit to the Scope clause. The session agreed that use cases are needed for (potential) requirements.

Cont

S1-134107

Qualcomm Incorporated

Scope of ASAC Feasibility Study

Revised to S1-134113

ACDC drafting session:

Proposal for sorting out FS_ACDC discussion. It is proposed to place after the Use Cases clause a new clause for Key Issues and High Level Requirements. Four Key Issues have been analyzed: applicability, control and triggering, effects on existing communication, control range and proportionality.

 

The session discussed how to incorporate this proposal and agreed to extract a few sentences that would fit to the Scope clause. The session agreed that use cases are needed for (potential) requirements.

 

Revision of S1-134023.

The session agreed to put the texts after the Scope as “Key issues for consideration.” The texts were further simplified and agreed. The session also agreed to incorporate texts on interworking of ACDC with other access barring mechanisms.

Cont

S1-134113

Qualcomm Incorporated

Scope of ACDC Feasibility Study

Agreed

Revision of S1-134023.

ACDC drafting session:

Proposal for sorting out FS_ACDC discussion. It is proposed to place after the Use Cases clause a new clause for Key Issues and High Level Requirements. Four Key Issues have been analyzed: applicability, control and triggering, effects on existing communication, control range and proportionality.

 

The session discussed how to incorporate this proposal and agreed to extract a few sentences that would fit to the Scope clause. The session agreed that use cases are needed for (potential) requirements.

 

Revision of S1-134023.

The session agreed to put the texts after the Scope as “Key issues for consideration.” The texts were further simplified and agreed. The session also agreed to incorporate texts on interworking of ACDC with other access barring mechanisms.

 

Revision of S1-134107.

Agreed to be added to the TR with a change of title to "Key issues for consideration" and placed in a new Annex

Cont

S1-134011

China Telecom

Controlling ongoing service when ACDC activated

Noted

ACDC drafting session:

It is proposed that ongoing service is to be restricted if not-allowed.

 

The session found there is a case like a voice call that should not be restricted if in progress.

Cont

S1-134028

Intel Corporation; Sony Mobile Communication; NTT Docomo

Regional and Local Differences in Allowed Applications for ACDC – Roaming Scenario

Revised to S1-134068

 

Cont

S1-134010

China Telecom, Huawei Technologies. Co., Ltd.

ACDC activation for Roaming UE Use Case

Revised to S1-134068

 

Cont

S1-134068

China Telecom, Intel Corporation; Sony Mobile Communication; NTT Docomo, Huawei

Regional and Local Differences in Allowed Applications for ACDC – Roaming Scenario

Revised to S1-134108

Revision of S1-134028 and S1-134010.

ACDC drafting session:

It is proposed that VPLMN’s policy is to be used and that, in case no ACDC-related provision exists in the roaming agreement, the roaming-in UE behaves like a UE w/o ACDC.

 

The session found that ACDC should work in the roaming scenario as well, but that the proposed scheme is too complex for an operator to maintain and too restrictive for future work; it is not desirable to use a word “list” and the potential requirements should be kept in high level.

Cont

S1-134108

China Telecom, Intel Corporation; Sony Mobile Communication; NTT Docomo, Huawei

Regional and Local Differences in Allowed Applications for ACDC – Roaming Scenario

Revised to S1-134154

Revision of S1-134028 and S1-134010.

ACDC drafting session:

It is proposed that VPLMN’s policy is to be used and that, in case no ACDC-related provision exists in the roaming agreement, the roaming-in UE behaves like a UE w/o ACDC.

 

The session found that ACDC should work in the roaming scenario as well, but that the proposed scheme is too complex for an operator to maintain and too restrictive for future work; it is not desirable to use a word “list” and the potential requirements should be kept in high level.

 

Revision of S1-134068.

Cont

S1-134154

China Telecom, Intel Corporation; Sony Mobile Communication; NTT Docomo, Huawei

Regional and Local Differences in Allowed Applications for ACDC – Roaming Scenario

Agreed

Revision of S1-134028 and S1-134010.

ACDC drafting session:

It is proposed that VPLMN’s policy is to be used and that, in case no ACDC-related provision exists in the roaming agreement, the roaming-in UE behaves like a UE w/o ACDC.

 

The session found that ACDC should work in the roaming scenario as well, but that the proposed scheme is too complex for an operator to maintain and too restrictive for future work; it is not desirable to use a word “list” and the potential requirements should be kept in high level.

 

Revision of S1-134068.

Revision of S1-134108.

Agreed to be added to the TR with minor editorial updates

Cont

S1-134035

NTT DOCOMO

ACDC use case: simplified use cases (pseudo PS barring and preferred handling of DMB)

Revised to S1-134109

ACDC drafting session:

Simplified in terms of flexibility of application, focusing on distinction between MMTEL and the others only or on a few disaster related applications. It is proposed that UEs are not to be affected by mechanisms intended to apply to old UEs.

 

The session understood that agreeing this P-CR does not prevent further enrichment of ACDC features. The session found (1) NOTE6 is not appropriate and should be removed, and (2) “Old UE” in NOTE5 should be rewritten as “UEs without ACDC capability”. The session agreed the revision with those changes (1) and (2), without another look at it.

Cont

S1-134109

NTT DOCOMO

ACDC use case: simplified use cases (pseudo PS barring and preferred handling of DMB)

Agreed

Revision of S1-134035.

Agreed in ACDC drafting session

Agreed to be added to TR

Cont

S1-134027

Intel Corporation; NTT Docomo; Sony Mobile Communications

Priority levels in ACDC

Revised to S1-134110

ACDC drafting session:

The session found emergency call should not be subject to ACDC. The session also found there should be another scheme to meet the use case by e.g. having several white lists; the potential requirements should be kept in high level.

Cont

S1-134110

Intel Corporation; NTT Docomo; Sony Mobile Communications

Priority levels in ACDC

Revised to S1-134163

ACDC drafting session:

The session found emergency call should not be subject to ACDC. The session also found there should be another scheme to meet the use case by e.g. having several white lists; the potential requirements should be kept in high level.

 

Revision of S1-134027.

Cont

S1-134163

Intel Corporation; NTT Docomo; Sony Mobile Communications

Priority levels in ACDC

Revised to S1-134168

ACDC drafting session:

The session found emergency call should not be subject to ACDC. The session also found there should be another scheme to meet the use case by e.g. having several white lists; the potential requirements should be kept in high level.

 

Revision of S1-134027.

Revision of S1-134110.

Cont

S1-134168

Intel Corporation; NTT Docomo; Sony Mobile Communications

Priority levels in ACDC

Agreed

ACDC drafting session:

The session found emergency call should not be subject to ACDC. The session also found there should be another scheme to meet the use case by e.g. having several white lists; the potential requirements should be kept in high level.

 

Revision of S1-134027.

Revision of S1-134110.

Revision of S1-134163.

Agreed to be added to the TR

Cont

S1-134029

Intel Corporation; Sony Mobile Communication

Regional and Local Differences in Allowed Applications in ACDC – Non Roaming Scenario

Revised to S1-134111

ACDC drafting session:

The session found the last potential requirement is not appropriate and should be removed. The session agreed the revision with that change, without another look at it.

Cont

S1-134111

Intel Corporation; Sony Mobile Communication

Regional and Local Differences in Allowed Applications in ACDC – Non Roaming Scenario

Agreed

ACDC drafting session:

The session found the last potential requirement is not appropriate and should be removed. The session agreed the revision with that change, without another look at it.

 

Revision of S1-134029.

Agreed in ACDC drafting session

Agreed to be added to the TR

Cont

S1-134147

Intel Corporation; Sony Mobile Communication

Regional and Local Differences in Allowed Applications in ACDC – Non Roaming Scenario

Noted

ACDC drafting session:

The session found the last potential requirement is not appropriate and should be removed. The session agreed the revision with that change, without another look at it.

 

Revision of S1-134029.

Agreed in ACDC drafting session

Revision of S1-134111.

Cont

S1-134036

NTT DOCOMO

ACDC use case: relationship to Access Class 11-15

Revised to S1-134112

ACDC drafting session:

The session found having barring status (barred/unbarred) is too complicated; it is better to write ACDC does not apply to AC11-15. The session also found it’s not relevant to mention AC0-9 and “Service Flows” needs to be revised.

Cont

S1-134112

NTT DOCOMO

ACDC use case: relationship to Access Class 11-15

Agreed

ACDC drafting session:

The session found having barring status (barred/unbarred) is too complicated; it is better to write ACDC does not apply to AC11-15. The session also found it’s not relevant to mention AC0-9 and “Service Flows” needs to be revised.

 

Revision of S1-134036.

Agreed to be added to the TR

9.1.1   FS_ACDC Drafting session information

AGE

S1-134105

Rapporteur

FS_ACDC Drafting Agenda

Noted

 

REP

S1-134106

Rapporteur

FS_ACDC Drafting Report

Approved

 

TR

S1-134167

Rapporteur

TR 22.806 v0.3.0

Agreed

Agreed as the basis for future contributions

No presentation

Summary of drafting session:

-       Texts for scoping purposes were in principle agreed: ACDC is about control of initiation of data communication at times of heavy traffic load in the network, and about from open access to blocking of access with various degrees. (Final check in plenary is needed.)

 

-       Two use case P-CRs were agreed: “ACDC use case: simplified use cases (pseudo PS barring and preferred handling of DMB)” and “Regional and Local Differences in Allowed Applications in ACDC – Non Roaming Scenario.”

-       Three use case P-CRs were revised for discussion in plenary: roaming, priority levels, and AC11-15.

 

-       Update of WID is open for discussion in plenary.

 

 

S1-134114

 

Tdoc number for allocation in drafting session

Drafting

 

9.2       FS_REOPS: Resilient E-UTRAN operation for Public Safety [SP-130240]

Cont

S1-134050

General Dynamics Broadband UK

Resilient E-UTRAN Operation: deriving the problem statement (supporting presentation)

Noted

 

Cont

S1-134049

General Dynamics Broadband UK

Resilient E-UTRAN Operation: deriving the problem statement

Revised to S1-134117

 

Cont

S1-134117

General Dynamics Broadband UK

Resilient E-UTRAN Operation: deriving the problem statement

Revised to S1-134166

Revision of S1-134049.

Cont

S1-134166

General Dynamics Broadband UK

Resilient E-UTRAN Operation: deriving the problem statement

Agreed

Revision of S1-134049.

Revision of S1-134117.

Cont

S1-134051

General Dynamics Broadband UK

A review of 3GPP activities in the area of Resilient E-UTRAN Operation

Noted

 

TR

S1-134052

Rapporteur

Outline TR 22.897: Study on Resilient E-UTRAN Operation for Public Safety

Revised to S1-134118

 

TR

S1-134118

Rapporteur

Outline TR 22.897: Study on Resilient E-UTRAN Operation for Public Safety

Agreed

Revision of S1-134052.

 

Agreed as the basis for future contributions

No presentation

Cont

S1-134054

ITRI

Discussion on REOPS consideration for severe situation

Noted

Comment: use correct use case template

Cont

S1-134056

InterDigital

Use cases for FS_REOPS

Revised to S1-134137

 

Cont

S1-134137

InterDigital

Use cases for FS_REOPS

Noted

Revision of S1-134056.

9.2.1   FS_REOPS Drafting session information

AGE

S1-134115

Rapporteur

FS_REOPS Drafting Agenda

Noted

 

REP

S1-134116

Rapporteur

FS_REOPS Drafting Report

Approved

 

Summary of drafting session:

On the scope and problem statement for the study item:

-       "Resilient E-UTRAN" was changed to "Isolated E-UTRAN"

-       Added functionality that the "Isolated E-UTRAN" will need to support (e.g. group communications) will be documented rather than the possible architectural solution (e.g. use of local EPC)

-       SA3 will need to be involved once the study is more mature as there are some security concerns

-       Limited bandwidth connectivity to EPC – whether in scope is FFS. One possible consideration is where signalling is carried to EPC but traffic is routed locally

 

 

S1-134119

 

Tdoc number for allocation in drafting session

Drafting

 

 

S1-134120

 

Tdoc number for allocation in drafting session

Drafting

 

 

S1-134121

 

Tdoc number for allocation in drafting session

Drafting

 

 

S1-134122

 

Tdoc number for allocation in drafting session

Drafting

 

 

S1-134123

 

Tdoc number for allocation in drafting session

Drafting

 

 

S1-134124

 

Tdoc number for allocation in drafting session

Drafting

 

9.3       Other Study Item contributions

Cont

'S1-134024

Qualcomm Inc

Use case for UPCON –  Priority on Demand

Moved to section 5.2

 

10  Work planning contributions

10.1     Work Plan

REP

S1-134006

MCC

3GPP Work Plan: extract for SA1#63

Noted

 

10.2     Work Item/Study Item status update

REP

S1-134125

Rapporteur (NEC)

RSE Status Update

Agreed

 

REP

S1-134126

Rapporteur (NTT DOCOMO)

FS_ACDC Status Update

Revised to S1-134182

 

REP

S1-134182

Rapporteur (NTT DOCOMO)

FS_ACDC Status Update

Approved

Revision of S1-134126.

 

 

No presentation

REP

S1-134127

Rapporteur (General Dynamics Broadband)

FS_REOPS Status Update

Agreed

 

REP

S1-134164

Rapporteur (KPN)

FS_ICBD Status update

Agreed

 

REP

S1-134165

Rapporteur

SEES status update

Agreed

 

REP

S1-134172

Rapporteur (G&D)

Need for Multiple APN Status update

Agreed

 

REP

S1-134177

Rapporteur (Intel)

CSIPTO Status update

Agreed

 

10.3     SA1 process improvements/updates

Cont

S1-134058

SA1 Chairman

SA1 output improvement proposals

Noted

 

Cont

S1-134064

SA1 Chairman

SA1 terminology review

Noted

Late document

10.4     Others

11  Next meetings

11.1     Calendar

Cont

S1-134053

ITRI

SA1#65 Taipei Meeting information

Noted

 

 

2013 meetings:

SA1#64           11 – 15 Nov 2013                        San Francisco, USA                           Mega meeting

 

2014 meetings:

SA1#65           20 – 24 Jan 2014                         Taipei, Taiwan                                    Possible joint meeting with SA2/SA3

SA1#66           12 – 16 May 2014                        Sapporo, Japan                                  Co-located with SA3 and SA5

SA1#67           18 – 22 Aug 2014                        Sophia Antipolis, France

SA1#67bis     13 – 17 Oct 2014                         TBD                                                       Will be cancelled if not needed

SA1#68           17 – 21 Nov 2014                        North America                                     Mega meeting

 

12  Any other business

13  Close

 

Close by 16:30 on Friday

 

14  Withdrawn documents (admin purposes only)

 

S1-134020

 

 

Withdrawn

 

 

S1-134045

 

 

Withdrawn

 

 

S1-134039

 

 

Withdrawn

 

 

S1-134040

 

 

Withdrawn

 

15  Document numbers to be allocated (admin purposes only)

 

S1-134096

 

 

Mona to allocate

 

 

S1-134097

 

 

Mona to allocate

 

 

S1-134098

 

 

Mona to allocate

 

 

S1-134099

 

 

Mona to allocate

 

 

Contents

1       Opening of the meeting.. 4

1.1       Agenda and scheduling.. 4

1.2       IPR. 4

1.3       Previous SA1 meeting report. 4

1.4       Information for delegates. 4

1.5       Working agreements. 4

2       Issues for early consideration. 5

3       Reports and action items. 5

3.1       Report from SA. 5

4       Liaison Statements (including related contributions) 5

5       Study and Work Items: New and Revisions. 8

5.1       Revisions of existing WIDs (including related contributions) 9

5.2       New Study and Work Items (including related contributions) 9

5.3       Proposals for new work (precursor to future Study and Work Items) 11

6       Rel-11 and earlier contributions. 11

7       Rel-12 Contributions. 11

7.1       GCSE_LTE: Group communication system enablers for LTE [SP-130326] 11

7.2       ProSe: Proximity-based services [SP-130030] 11

7.3       IMS_WebRTC: Web Real Time Communication access to IMS [SP-130325] 12

7.4       Other Rel-12 contributions. 12

8       Rel-13 Contributions. 12

8.1       RSE: RAN Sharing Enhancements [SP-130330], includes FS_RSE [SP-110820] 12

8.1.1        RSE Drafting session information. 13

8.2       TEI13 contributions. 13

9       Study Item contributions. 14

9.1       FS_ACDC: Application specific congestion control for data communication [SP-120546] 14

9.1.1        FS_ACDC Drafting session information. 14

9.2       FS_REOPS: Resilient E-UTRAN operation for Public Safety [SP-130240] 15

9.2.1        FS_REOPS Drafting session information. 15

9.3       Other Study Item contributions. 15

10         Work planning contributions. 15

10.1          Work Plan. 15

10.2          Work Item/Study Item status update. 15

10.3          SA1 process improvements/updates. 16

10.4          Others. 16

11         Next meetings. 16

11.1          Calendar. 16

12         Any other business. 16

13         Close. 16

14         Withdrawn documents (admin purposes only) 16

15         Document numbers to be allocated (admin purposes only) 16