3GPP TSG-SA WG1 Meeting #66

Sapporo, Japan, 12th-16th May 2014

tdoc list SA1#66 draft END OF MEETING

For the hyperlinks to work:

1) unzip this tdoc list on your PC and place the .doc file in the folder you wish (let's call it ...\meeting_x)

2) place all the zipped tdocs in the subfolder ...\meeting_x\tdocs

3) you might have to refresh the fields. To do this, select all (CTL+A) and press F9.

Use the macros to widen/shrink a column, show all the content of a row or only its first line, show all the text or only first lines of the table.

Order	Ag.Item	Tdoc #	Source	Title	Spec	CR#	cat	Version in	Rel	WI	Summary	Discussion	Conclusion
999999	1.1	S1-141000	SA1 Chairman	Draft agenda for SA1#66	Replaced by S1-135001.
010101	1.1	S1-141001	SA1 Chairman	Draft Schedule and Agenda with document allocation for SA1#66	Revised to S1-141002.
010101,2	1.1	S1-141002	SA1 Chairman	Final Schedule and Agenda with document allocation for SA1#66	Mr. Miyamoto, Yoshihiro (Mr.) from NEC welcomed all the participants to Sapporo, Japan. Rich Hovey won the 3GPP Award of Excellence for 2013 for his hard work on ProSe.	Approved.
030101	3.1	S1-141003	SA1 Chairman	SA1-related topics at SA#63	Of the 7 SA1 documents presented to SA for approval: - 5 were approved without revision; - 2 had revisions and were approved. SA1 aspects were added to a CT approved WID where the SA1 work is expected to be for Rel-12, please refer to section 5.2 for details. There was no action to SA1.	Ericsson mentioned that SA also discussed about virtualisation, which might be further discussed at SA1 later on this year.	Noted.
010301	1.3	S1-141004	MCC	Draft minutes of SA1#65	Revised before the meeting to S1-141373
010301,4	1.3	S1-141005	MCC	Minutes of SA1#65	Approved.
090100	9.1	S1-141006	MCC	Extract of the 3GPP Work Plan for SA1#66	Noted.
080203	8.2	S1-141007	III, ITRI	Deployment on Remote Territory	A new use case is proposed to describe Deployment of IOPS on Remote Territory	Noted.
050208	5.2	S1-141008	III, ITRI	Discussion on Long Range Cell Operation for Public Safety	This is a presentation to introduce the proposed WID in S1-141013.	Noted.
050208,3	5.2	S1-141009	III, ITRI	Discussion on Support Long Range Cell Operation for ProSe	For off-line discussions.	Noted.
050208,3	5.2	S1-141010	III, ITRI	Support Long Range Cell Operation for ProSe	22.278	0199	For off-line discussions.	Noted.
050208,3	5.2	S1-141011	III, ITRI	Discussion on Support Long Range Cell Operation for GCSE	For off-line discussions.	Noted.
050208,3	5.2	S1-141012	III, ITRI	Support Long Range Cell Operation for GCSE	22.468	0002	For off-line discussions.	Noted.
050208,2	5.2	S1-141013	III, ITRI	WID proposal: Long Range Cell Operation for Public Safety (LCOPS)	WID	The WID is for introduction of E-UTRAN to support long-range cell operation (10-100km) for ProSe and GCSE. The scope of the Work Item is limited to Public Safety UEs and Public Safety use.	Telecom Italia wonder how the coverage can be extended if not using e.g. relay, which is already defined. For NSN, this WID has no impact on SA1. This for the radio groups to consider.	Revised to S1-141396
080774	8.7	S1-141014	NSN, China Mobile, Huawei	Definition for Enhanced Call Information	For drafting group.	Revised to S1-141357
080768	8.7	S1-141015	NSN, China Mobile, Huawei	Clarification of user vs. calling and called party	For drafting group.	Revised to S1-141358
080769	8.7	S1-141016	NSN, China Mobile, Huawei	Clarification on media types	For drafting group: agreed in drafting.	Agreed.
080776	8.7	S1-141017	NSN, China Mobile, Huawei	Timing of information transfer	For drafting group: agreed in drafting.	Agreed.
080770	8.7	S1-141018	NSN	Clarification on Pre-conditions	For drafting group.	Revised to S1-141360
080771	8.7	S1-141019	NSN	Clarification on Service flows	For drafting group.	Revised to S1-141361
080777	8.7	S1-141020	NSN	Update to Potential Requirements	For drafting group.	Revised to S1-141362
080602	8.6	S1-141021	NSN	The name of the TR	This is covered by S1-141198.	Noted.
999999	8.6	S1-141022	NSN	Correction to use case on network congestion	Withdrawn
080605	8.6	S1-141023	NSN	Correction to use case on network congestion	The text in the use case on network congestion in TR 22.808 was not changed from “RAN congestion” to “network congestion” consistently	Huawei will provide off-line revisions.	Revised to S1-141444
999999	4	S1-141024	Ericsson	Reply LS on Removal of option to subscribe for a notification of diversion occurrence	Revised to S1-141261
040007,1	4	S1-141025	Ericsson	Removal of CDIVN service	22.173	0094	F	8.9.0	Rel-8	TISMMTEL-R8	Agreed.
040007,2	4	S1-141026	Ericsson	Removal of CDIVN service	22.173	0095	A	9.6.0	Rel-9	TISMMTEL-R8	Agreed.
040007,3	4	S1-141027	Ericsson	Removal of CDIVN service	22.173	0096	A	10.5.0	Rel-10	TISMMTEL-R8	Agreed.
040007,4	4	S1-141028	Ericsson	Removal of CDIVN service	22.173	0097	A	11.5.0	Rel-11	TISMMTEL-R8	Agreed.
040007,4	4	S1-141029	Ericsson	Removal of CDIVN service	22.173	0098	A	12.5.0	Rel-12	TISMMTEL-R8	Agreed.
070278	7.2	S1-141030	Home Office	Proposed Security Requirements for MCPTT	For drafting session	Revised to S1-141312
999999	8.6	S1-141031	Juniper Networks, Vodafone, Telecom Italia, NSN	Traffic Steering based on operator's policies or user subscription	Revised to S1-141256
080608,2	8.6	S1-141032	Juniper Networks, Vodafone, Telecom Italia, NSN	ppt for discussion - Traffic Steering based on Operator's Policies or User Subscription	Background information for S1-141256.	Noted.
080610	8.6	S1-141033	Huawei, China Mobile, Orange, Alcatel-Lucent	Traffic steering in MVNO scenario	Traffic steering should enable different steering for MNO and MVNO end-users: - While a MNO has certain steering preferences for traffic of its end-users, - a MVNO may have different ones for its own end-users even under the same network conditions.	The Use Case might be already partly covered.	Revised to S1-141457
080611	8.6	S1-141034	Huawei, China Mobile, Orange	Traffic steering based on QoS information	This contribution describes a use case where the MNO implements traffic steering based on QoS information.	For drafting session.	Revised to S1-141500
080607	8.6	S1-141035	China Mobile, Huawei, Orange	Generic requirements on service steering	Some generic requirements on security, charging are proposed to be added.	Revised to S1-141455
999999	8.6	S1-141036	NSN	Proposed FMSS Definitions and Overview	Revised to S1-141426
080612	8.6	S1-141037	NSN	Proposed FMSS use case on changing the Service Chain during the connection	This use case shows how the Service Chain is changed during the connection, when conditions change.	Some off-line discussions to take place in particular with Huawei.	Revised to S1-141458
080613	8.6	S1-141038	NSN	Proposed FMSS use case on adding new Service Functions to the Service Chaining System	This use case shows how new Service Functions can be added to the Service Chaining System, concluding that “The operator shall be able to add Service Functions for new Network Services to an existing Service Chaining System.”	KDDI and Huawei do not disagree with the requirement but think it would be more appropriate to be placed at some other use case.	Noted.
080614	8.6	S1-141039	NSN	Proposed FMSS use case on adding capacity to the Network Service	This use case shows how capacity can be added to the Network Service. The derived Potential Requirement is that the operator shall be able to allocate additional Service Functions to its Service Chaining Systems to handle overload in the Network Service.	Off-line discussions requested.	Revised to S1-141459
080603	8.6	S1-141040	Huawei, China Mobile, Alcatel Lucent, Orange	Overview section for FMSS	This contribution clarifies the overview of FMSS by stating that: In order to realize efficient and flexible mobile service steering in the Gi-LAN network, the MNO uses some network information (e.g. user profile, RAT type, application characteristics, etc) to determine traffic steering policies that it provides to Gi-LAN. These policies are used in Gi-LAN to route the MNO’s subscriber’s traffic data to appropriate enablers.	NEC stressed out that the “Gi-LAN network” is not defined anywhere, so a definition for it should be introduced. For Cisco, this is too solution-oriented and the first sentence should be deleted. For Juniper, “MNO” is too specific.	Revised to S1-141442
080619	8.6	S1-141041	China Mobile, Huawei	FMSS Consolidated requirements	Revised to S1-141471
070102	7.1	S1-141042	Huawei, NEC, KPN	Clarification of background traffic use case	This contribution proposes some improvements applicable to the background traffic use case:	Revised to S1-141421
070103	7.1	S1-141043	Huawei, KPN, China Mobile	Generic requirements on service/capability exposure towards third parties	This contribution proposes potential requirements on service/capability exposure towards 3rd party service providers.	Revised to S1-141423
080766	8.7	S1-141044	Orange	ECIP use case on calling party side – information blocked	For drafting group.	Revised to S1-141445
080761,2	8.7	S1-141045	Orange	ECIP use case on calling party side – Text call per call	For drafting group.	Revised to S1-141555
080765	8.7	S1-141046	Orange	ECIP use case on calling party side – Important communication information	For drafting group. This was already seen as a previous meeting and not agreed.	Noted.
070501	7.5	S1-141047	Orange	Unexpected data exchange	22.368	0152	C	12.3.0	Rel-13	SRMMTC	The possibility to detect unexpected data exchange and connection is added to the section "MTC Monitoring".	This is a new functionality: this is not covered by this maintenance work item. A new WID is needed if the CR is acceptable.	Noted.
070103	7.1	S1-141048	Huawei, KPN	Complete FFS on Presence/LCS and on reason	Revised to S1-141422
081001	8.10	S1-141049	Rapporteur	Proposed skeleton for Study on User Control Over Spoofed Calls (UC_SPOOF) TR	TR	Agreed as a basis for future contributions atSA1#66.
999999	8.6	S1-141050	ZTE Corporation	Use Case for Service Chain Status update	Revised to S1-141378
999999	8.6	S1-141051	ZTE, China Mobile, China Telecom, China Unicom, CATT	Use Case for Flexible Mobile Service Steering -- Service Chain Bootstrapping and Auto Re-configuration	Revised to S1-141377
999999	7.4	S1-141052	General Dynamics UK Ltd	Definitions and abbreviations in support of normative requirements for Isolated E-UTRAN operation	Revised to S1-141399
999999	7.4	S1-141053	General Dynamics UK Ltd	Draft service description for Isolated E-UTRAN operation	Revised to S1-141400
070262	7.2	S1-141054	French Ministry of Interior	Inter system operations requirements	This paper proposes requirements related to the situation where Public Safety users from different PTT Systems have to communicate within one PTT group.	For drafting session: not handled.	Revised to S1-141321
999999	7.4	S1-141055	General Dynamics UK Ltd	Draft general, subscriber and service management normative requirements for Isolated E-UTRAN operation	Revised to S1-141401
070404	7.4	S1-141056	French Ministry of Interior	Minimum set of services for an isolated E-UTRAN	This contribution proposes a minimum set of services to be provided by an Isolated E-UTRAN. An Isolated E-UTRAN may be created by either network backhaul failure or with the addition of one or more eNB(s) to the network to enhance capacity. The proposed text is intended for inclusion in TS 22.278.	It has to be checked off-line if there is no overlap with the General Dynamics’ documents.	Revised to S1-141489
999999	7.4	S1-141057	General Dynamics UK Ltd	Draft normative requirements for initiation of Isolated E-UTRAN operation	Revised to S1-141402
070410	7.4	S1-141058	French Ministry of Interior	Operational requirements for isolated E UTRAN operation	This contribution proposes additional requirements in TS 22.278 to take into account that an Isolated E-UTRAN can be added in the network to provide extra capacity and shall be able, when possible, to synchronize with the rest of the network.	Revised to S1-141439
999999	7.4	S1-141059	General Dynamics UK Ltd	Draft normative requirements for ongoing Isolated E-UTRAN operation	Revised to S1-141403
999999	7.4	S1-141060	General Dynamics UK Ltd	Draft normative requirements for termination of Isolated E-UTRAN operation	Revised to S1-141404
999999	7.4	S1-141061	General Dynamics UK Ltd	Draft normative requirements for security aspects of Isolated E-UTRAN operation	Revised to S1-141405
080201	8.2	S1-141062	General Dynamics UK Ltd	Aligning the title of the FS_IOPS technical report with MCC drafting rules	The title is proposed to be changed to “Study on Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for Public Safety”.	Agreed.
081002	8.10	S1-141063	Sprint	Proposed TR Scope	This is a proposal for the scope of the UC_SPOOF TR.	Agreed.
999999	8.10	S1-141064	Sprint	Proposed UC_SPOOF Scope	Withdrawn
081003	8.10	S1-141065	Sprint	Proposed TR Introduction	This is an introduction for the same TR.	“detect” to be added .	Revised to S1-141492
070106	7.1	S1-141066	Huawei, NEC, KPN, China Mobile	Consolidation of SEES service/capabilities	This contribution proposes a consolidated list of network capabilities/services that can be exposed for SEES TR section 5.2 “Potential additional requirements”.	Ericsson noticed that the text proposed for consolidation is text which is not yet agreed, so this is rather confusing. The two operations (adding new requirements and consolidating them) should be clearly shown.	Revised to S1-141425
040008,2	4	S1-141067	Huawei	Draft Reply to OMA about SEES work item	A proposed SA’s view on the SEES-related API and time plan activities is proposed.	For Ericsson, 3GPP has not defined APIs so far. This might be done if needed, but it has to be clarified that this was not the case to date. For Telecom Italia, 3GPP can definitely be involved with APIs, in collaboration with GSMA and OMA, as it has been the case in the past. More discussions are needed in the drafting session.	Revised to S1-141383
070209	7.2	S1-141068	US Department of Commerce, General Dynamics UK Ltd, T-Mobile USA Inc., Blackberry	Service description for Section 4.1, Overview	This contribution provides general MCPTT service description for TS 22.179 section 4.1, Overview.	Motorola has still concerns for the distinction between MCPTT and PTT. The differences should be either highlighted or one single term should be used. For NSN, “PTT” is a trade mark and should not be used. This does not seem to be the case in the US, for the U.S. Department of Commerce. This is to be solved off-line.	Revised to S1-141407
070210	7.2	S1-141069	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Additional Floor control requirements, section 4.2	Additional requirements for section 4.2, Floor Control, are proposed.	This is to be further refined off-line.	Revised to S1-141408
070211	7.2	S1-141070	Alcatel-Lucent, US Department of Commerce	Modifications to a single Floor control requirement on hierarchy in section 4.2	Modifications to a single requirement on hierarchy for section 4.2, Floor Control are proposed.	Off-line discussions are needed. See also document S1-141071 on a related topic.	Revised to S1-141410
070212	7.2	S1-141071	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Additional General Group Call requirements, section 4.3	This document provides additional requirements for section 4.3, General Group Call.	Revised to S1-141411
070213	7.2	S1-141072	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Broadcast / Announcement Group Calls	A list of requirements for broadcast / announcement group calls is proposed.	This is also to be refined off-line.	Revised to S1-141412
070214	7.2	S1-141073	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Dynamic Group management	A list of requirements for dynamic group management is proposed.	Same comments as for S1-141072.	Revised to S1-141413
070216	7.2	S1-141074	Motorola Solutions Inc., Harris Corporation, US Department of Commerce	Additional requirements for Audio PTT Call Performance	A list of additional requirements for Audio PTT Call Performance is proposed.	All the requirements should be gathered together, involving all the interested companies.	Revised to S1-141415
070219	7.2	S1-141075	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for PTT Priority Requirements	For drafting session.	Revised to S1-141315
070221	7.2	S1-141076	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Emergency Group Calls	Revised to S1-141418
070222	7.2	S1-141077	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Imminent Peril Call	Revised to S1-141419
070267	7.2	S1-141078	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for personality management	For drafting session.	Revised to S1-141316
070268	7.2	S1-141079	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for location	For drafting session. This then came to SA1, where e.g. the usefulness of the statement “subject to regulatory requirements” was debated.	Revised to S1-141317
070269	7.2	S1-141080	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for security, section 4.10	For drafting session.	Merged with 1030 in S1-141312
070270	7.2	S1-141081	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for interworking with Project 25	A list of requirements for interworking with Project 25 as defined in the TIA-102 specifications.	For drafting session: not handled. A reference to the related documents should be added, but this can be done later.	Revised to S1-141319
070271	7.2	S1-141082	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for interworking with Legacy Land Mobile Radio	This is a list of requirements for interworking with Legacy Land Mobile Radio, including analogue systems.	For drafting session: not handled. SA1: same comments as for S1-141081. This is to be added in the P25 interworking document.	Revised to S1-141320
070272	7.2	S1-141083	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Off network	This introduces a list of requirements for Off network.	For drafting session: not handled. Some rewording was done online.	Revised to S1-141322
070273	7.2	S1-141084	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Emergency Alert	This contains a proposed list of requirements for emergency alert.	For drafting session. In PWS, there is a service called emergency alerting already. “distress alert” is proposed instead. But it was then mentioned that emergency alerting is already something well known in the public safety world.	Revised to S1-141584
050205	5.2	S1-141085	Qualcomm Incorporated	New WID for ProSe Maintenance (ProSeM)	WID	This is maintenance WID for Prose, as to ensure that Release 13 TS 22.278 and TS 22.115 contain all agreed ProSe Stage 1 requirements. These service requirements are to be copied from Release 12 TS 22.278 and TS 22.115 prior to removal of unfulfilled service requirements from Release 12 as per process for handling WIDs across releases. No new service requirements will be added under this WID.	Revised to S1-141394
999999	5.2	S1-141086	Qualcomm Incorporated	Review of ProSe stage-1 fulfilment (TS 22.278)	Revised to S1-141389
080801	8.8	S1-141087	Qualcomm Incorporated	Initiation of multimedia broadcast supplemental to PWS	This document proposes a use case and requirements for a process whereby a multimedia broadcast transmission is “bootstrapped” (i.e. initiated) subsequent to a PWS notification.	Off-line discussions requested by KDDI.	Revised to S1-141485
080901	8.9	S1-141088	Telefonica	Update to Section 1 (Scope)	22.852	0001	D	12.0.0	Rel-13	FS_GUSH	This CR expands TR22.852 to incorporate GERAN and UTRAN by changing E-UTRAN to RAN.	The category should be B.	Revised to S1-141460
080902	8.9	S1-141089	Telefonica	Update to Section 3 (Definitions, Symbols & Abbreviations)	22.852	0002	D	12.0.0	Rel-13	FS_GUSH	This CR expands TR22.852 to incorporate GERAN and UTRAN by adding UTRAN and GERAN to the definition of Hosting RAN.	The category should be B. The terminology might be improved.	Revised to S1-141461
080903	8.9	S1-141090	Telefonica	Update to Section 4.1.2 (What Constitutes a Shared RAN)	22.852	0003	D	12.0.0	Rel-13	FS_GUSH	Still to expand TR22.852 to incorporate GERAN and UTRAN, this CR changes E-UTRAN to RAN and to add two new situations: - Maximise Cost Savings - Maintain an obsolescent network	Also change of category is needed.	Revised to S1-141462
080903	8.9	S1-141091	Telefonica	Update to Section 4.2 (Scenario and use case 1)	22.852	0004	C	12.0.0	Rel-13	FS_GUSH	The CR changes E-UTRAN and LTE to RAN and to add an explanation that RAN can be E-UTRAN, UTRAN or GERAN	Also change of category is needed. The “Requirements” should actually be “Potential Requirements”.	Revised to S1-141463
080904	8.9	S1-141092	Telefonica	Update to Section 4.6 (Scenario and use case 5.a)	22.852	0005	C	12.0.0	Rel-13	FS_GUSH	The CR is to change EPC to Core Network and to add BTS references.	The category is to be changed, as for all the CRs in this series.	Revised to S1-141464
080905	8.9	S1-141093	Telefonica	Update to Section 4.9 (Scenario and use case 7)	22.852	0006	C	12.0.0	Rel-13	FS_GUSH	The CR changes eUTRAN to RAN.	The category is to be changed.	Revised to S1-141465
080906	8.9	S1-141094	Telefonica	Update to Section 4.14 (Scenario and use case 12)	22.852	0007	D	12.0.0	Rel-13	FS_GUSH	The CR adds to Note 2 that Use Case 15 may supersede this Use Case.	The UE seems to be impacted, when this WID was not assumed to impact the UE.	Revised to S1-141365
080907	8.9	S1-141095	Telefonica	Add new Section 4.16 (Scenario and use case 14)	22.852	0008	B	12.0.0	Rel-13	FS_GUSH	The CR adds a new use case to describe sharing of a common network e.g. 2G.	For NEC, this use case is very similar to what is already in the TR.	Revised to S1-141466
080909	8.9	S1-141096	Telefonica	Add new Section 4.17 (Scenario and use case 15)	22.852	0009	B	12.0.0	Rel-13	FS_GUSH	A new use case is added to describe how the various RATs interact.	Revised to S1-141467
080910	8.9	S1-141097	Telefonica	Update to Section 5 (Considerations)	22.852	0010	C	12.0.0	Rel-13	FS_GUSH	The CR adds BTS references and a new section 5.5 on Impact on RANs	Revised to S1-141468
080911	8.9	S1-141098	Telefonica	Update to Section 6 (Potential Requirements)	22.852	0011	C	12.0.0	Rel-13	FS_GUSH	It changes E-UTRAN to RAN and modifies the table in 6.2 to incorporate new requirements.	The changes on the other CRs have to be taken into account here.	Revised to S1-141469
080912	8.9	S1-141099	Telefonica	Update to Section 7 (Conclusion and recommendations)	22.852	0012	D	12.0.0	Rel-13	FS_GUSH	The CR adds UTRAN and GERAN in the conclusion.	Revised to S1-141470
080153	8.1	S1-141100	Teliasonera AB	Proposal for conclusion on ACDC and Network Sharing (Use Case 15)	Revised to S1-141336
070301	7.3	S1-141101	Alcatel-Lucent	Use case for end to end WebRTC bearer support over IMS	22.228	0197	B	12.6.0	Rel-13	eWebRTCi	The CR introduces a use case illustrating the use of WebRTC bearer protocols and security mechanisms between WebRTC IMS clients.	For Qualcomm, beside the fact that the description is quite long, they wonder what is really brings. The advantages should be more put forward.	Revised to S1-141430
070302	7.3	S1-141102	Alcatel-Lucent	Requirements to support end to end WebRTC bearer support over IMS	22.228	0198	B	12.6.0	Rel-13	eWebRTCi	As to minimize the Protocol Conversion, a requirement is added to tell that the IMS shall provide a mechanism to support communication between WebRTC IMS clients without requiring bearer level protocol conversions between WebRTC and IMS protocols.	No impacts on the codec are expected. NSN mentioned that the wording of the last sentence is wrong: this is the usage of this function which is “subject to operator policy and regional regulatory constraints”, not how it is performed like it is written in the document. For Huawei, even if the wording is not the best one, what is meant is quite obvious. The title of the proposed section can be improved, as well as the text itself.	Revised to S1-141431
040006,2	4	S1-141103	Alcatel-Lucent	I-WLAN clean up in 22.278	22.278	0200	C	12.4.0	Rel-12	TEI12	As part of the 3GPP process focused on discontinuing support for I-WLAN, the indication that 22.234 contains requirements applicable for EPS is removed from Rel-12 forward.	Blackberry proposes to postpone these CRs until it is known better what will be done in the other WGs.	Noted.
040006,4	4	S1-141104	Alcatel-Lucent	I-WLAN clean up in 22.011	22.011	0472	C	12.1.0	Rel-12	TEI12	Mirror CR.	Noted.
080154	8.1	S1-141105	Qualcomm Incorporated	ACDC System Overview	Revised to S1-141339
080155	8.1	S1-141106	Qualcomm Incorporated	ACDC Use Case: Applicability of ACDC in UE Connected State	Noted in the drafting.	Noted.
080155	8.1	S1-141107	Qualcomm Incorporated, NTT DOCOMO	Proposed Editorial Changes to TR 22.806 Study on Application specific Congestion control for Data Communication	Agreed in drafting.	Agreed.
080157	8.1	S1-141108	Qualcomm Incorporated	ACDC: Evaluation of Network Sharing Use Case	Noted
050203	5.2	S1-141109	Qualcomm Incorporated, NTT DOCOMO	Consolidation of Potential Requirements from TR 22.806 Study to Normative Text	Starting with the text of Use Cases and Potential Requirements in TR 22.806, a set of consolidated requirements is proposed for the normative phase	This is a background information for explaining what is in the CR in S1-141171. Telia Sonera propose to have it included in the TR. For drafting session.	Revised to S1-141342
050209	5.2	S1-141110	China Telecom	New study on Requirements for Virtualization of Mobile Networks (FS_RVMN)	WID	The objective is to study use cases and identify potential requirements for virtualization and programmability of networks considering Network Infrastructure Virtualization and Programmable and controlled API.	T-Mobile and Huawei reminded the SA’s decision that only SA5 should be impacted by NFV at this stage, so this should be reconsidered by SA1 at a later meeting. Telecom Italia agree. The dates are wrong in section 10.	Noted.
050209,2	5.2	S1-141111	China Telecom	Mobile SDN perspective	This provides background information for S1-141110.	Noted.
070217	7.2	S1-141112	Huawei, TD-Tech	End-to-end PTT setup time performance	It provides requirement of End-to-end PTT setup time performance.	It is judged as being already covered by some companies. There is no support.	Noted.
070263	7.2	S1-141113	Huawei, TD-Tech	Requirement for service continuity	For drafting session	Noted.
999999	7.2	S1-141114	Huawei, TD-Tech	Requirements for Interactions between PTT call and telephone call	withdrawn
070215	7.2	S1-141115	Ericsson	Q&A about the concept of PTT Session	This Q&A has been created in order to clarify the concept of a Session, KPI2 and KPI4. It is provided to the meeting for information, but the content can be included as for instance an informal annex in TS 22.179 if agreed by the meeting.	For Harris, several aspects mentioned here are implementation specific, e.g. about when is a session created, so they do not share Ericsson’s opinion.	Revised to S1-141414
070101	7.1	S1-141116	Ericsson	Update of the Connection Patterns use case	It is proposed to remove the relation to Radio Resource Control since that is not needed for the service exposure use case.	Revised to S1-141420
070105	7.1	S1-141117	China Unicom	Use Case on QoS Choice Exposure	This contribution describes a use case to allow 3rd party to choose the QoS (such as bandwidth, delay, etc.) for the designated users.	The author proposes to merge with S1-141066.	For drafting session.
070106	7.1	S1-141118	China Unicom	Use Case on Terminal Characteristics Exposure	To improve user experience, the 3rd party expects to use knowledge of terminal characteristics. These terminal characteristics could be obtained by the network at one time. Depend on the agreement of operator, subscriber and the 3rd party, terminal characteristics could be exposed to the 3rd party to adjust the content in order to fit the user’s terminal.	It is explained that this is the UE which is intended to send the info, not the user (as written). There are concerns on the battery power, and on the usefulness of the proposal.	Revised to S1-141424.
080407	8.4	S1-141119	Samsung Electronics	P-CR to TR 22.828 to Refine Potential Impacts for Use Cases 3&4	This contribution proposes refinements to Potential Impacts and Interactions sections for Use Cases 3 and 4.	Agreed.
070304	7.3	S1-141120	NSN	Proposed LS on WebRTC Security to SA3 and SA3 LI	LS draft	The Work Item is not yet approved by SA3.	Withdrawn.
070181	7.1	S1-141121	KPN, Huawei, NEC, China Mobile	Proposed SEES conclusion	Revised to S1-141552
999999	7.1	S1-141122	Huawei, NEC, KPN	Exposure of charging to 3rd party	22.115	0073	Revised to S1-141258
999999	7.1	S1-141123	Huawei, NEC, KPN	Exposure of network service and capabilities to 3rd party	22.101	0473	Revised to S1-141259
080302	8.3	S1-141124	Ericsson	Late provisioning of a selected MNO	A new use case is proposed for Late provisioning of selected MNO.	For several delegates (G&D, Vodafone, Telecom Italia), there already are existing solutions that require no change. Only the 4.x.5.1 Network based solution is to be kept, to be put in use case 3.	Revised to S1-141473
080303	8.3	S1-141125	Ericsson	Change of selected MNO	It is proposed to add a use-case on “Change of selected MNO” to the TR 22.802 to give a more accurate description of a use-case and potential solution that complements what is specified in “GSMA Remote Provisioning Architecture for Embedded UICC Technical Specification”.	It is preferable to split the document in two: the technical solution in one, and the rest (update of use case) in another one.	Revised to S1-141474 and S1-141475
080606	8.6	S1-141126	Cisco, Allot Communications	Traffic steering on network status to be on RAN status	This contribution proposes to use only RAN status when steering traffic.	For Deutsche Telekom AG and Ericsson, there is no reason why to restrict it to RAN only.	Noted.
080301	8.3	S1-141127	Ericsson	Single IP address	It is proposed to clarify that the multi-purpose APN soultion is using a single IP adress and IP stack. It is not expected that low cost MTC devices will support multiple IP addresses and IP stacks. Furthermore, the multi-purpose APN reduces the required IP address space for the MNOs.	The costs of terminals are not a matter for 3GPP: the phrasing should be changed, using e.g. “complexity”. For G&D, Telecom Italia and Vodafone, the complete sentence can be removed. For KPN, the last sentence can be removed. So only the first sentence is kept.	Revised to S1-141472
080408	8.4	S1-141128	Orange	P-CR to TR 22.828 on Section 4 Potential Requirements	Based on the consolidation process outlined in discussion paper (S1-141142), this contribution proposes clarification on potential requirements in section 4.1.6	There is a similar statement in section 4.2.	Revised to S1-141477
060202	6.2	S1-141129	Orange	Clarification on the use of codecs by the WebRTC IMS client	22.228	0203	F	12.6.0	Rel-12	IMS_WebRTC	It is clarified that the WebRTC IMS client shall offer (at least one of) the codecs made available by the 3GPP UE when establishing a session	NSN mentioned that there is already a set of mandatory codecs to be supported. For Alcatel-Lucent, the IMS can be accessed by multiple technologies, not only the 3GPP one.	Revised to S1-141490
070631,2	7.6	S1-141130	Orange	SMS-outbox update on Mobile	22.101	0474	B	13.2.0	Rel-13	SMS_OBUD	It is added to the specification that: when a Short message is sent from a Web portal, it shall be possible to update the mobile SMS outbox with Short message sent via the Web portal.	For Nokia, this is a solution more than a requirement. See corresponding Work Item in S1-141185. The WID (final version in S1-141525) could not be approved.	Noted.
070631	7.6	S1-141131	Orange	Discussion Paper SMS-outbox update on mobile	This is a proposal to solve the fact that today, when a mobile subscriber sends an SMS from a Web portal, this SMS is not updated in the SMS outbox on the subscriber’s mobile	Noted. See actual CR in S1-141130.
080404	8.4	S1-141132	Rapporteur	Addition of Requirement Numbers to TR22.828	The requirements are now numbered.	Agreed.
999999	8.4	S1-141133	Rapporteur	Addition of Requirement Numbers to TR22.828	Withdrawn
999999	8.4	S1-141134	Rapporteur	Addition of Requirement Numbers to TR22.828	Withdrawn
999999	8.4	S1-141135	Rapporteur	Addition of Requirement Numbers to TR22.828	Withdrawn
080409	8.4	S1-141136	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, China Mobile, China Telecom, KPN, Acer	Revsion of APN-AMBR Note & Add New Requirement	This contribution proposes revisions to the note regarding the impact of CSIPTO on APN-AMBR and to add a new requirement to the general requirements.	There are some typos in the requirements numbering. Some requirements need rephrasing.	Revised to S1-141478
080410	8.4	S1-141137	Intel; Interdigital; Samsung; Sony Mobile Communications; T-Mobile USA	Considerations on Security for CSIPTO	It is proposed to add that potential issues related to the maintenance of security may arise due to the coordinated movements of the IP flows between P-GWs.	Revised to S1-141479
080411	8.4	S1-141138	Intel, Interdigital, Samsung, Sony Mobile Communications; T-Mobile USA	Considerations on Charging for CSIPTO	It is proposed to add that there may be impact on charging aspects e.g. accounting and usage information due to CSIPTO triggered concurrent PDN connections.	Agreed.
080412	8.4	S1-141139	Intel, Samsung, Interdigital, Sony Mobile Communications; T-Mobile USA	Considerations on Evolution & Rollout for CSIPTO	It is clarified that Backward compatibility to pre-Rel 13 is not required.	Agreed.
080413	8.4	S1-141140	Intel	Proposed conclusion section for TR 22.828	It is proposed to create normative requirements based on the potential requirements documented in section 6 of the present document.	Some remaining issues have to be solved before the conclusion can be addressed.	Revised to S1-141561
080405	8.4	S1-141141	Intel, Sony Mobile Communications, Samsung, Interdigital, T-Mobile USA, Acer, KPN, China Mobile, China Telecom	Discussion Paper to Consolidate Potential Requirements in Section 6 of TR 22.828	This discussion paper reviews the requirements associated with the use cases agreed for this version and attempts to consolidate them. The approach used to do this is first outlined, and then the relevant text modified in several steps per that approach to result in the text that is proposed to be included in section 6 of TR 22.828.	This is background information.	Noted.
080406	8.4	S1-141142	Intel, Samsung, Sony Mobile Communications, Interdigital, T-Mobile USA, Acer, China Mobile, China Telecom, KPN	Proposed Text for CSIPTO Consolidated Requirements	This is also a clean-up of the TR.	Agreed.
050204	5.2	S1-141143	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, Acer, China Mobile, China Telecom, KPN	Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO)	WID	This is to clarify that the WID is an actual feature and not a study.	See related CR in S1-141145. Open	Revised to S1-141300
090301	9.3	S1-141144	WG Chairman	Requirement numbering: updated to include proposal for existing TS under change control	Noted.
050204,2	5.2	S1-141145	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, KPN, China Telecom, China Mobile, Acer	Discussion Paper - Draft CR to add CSIPTO to TS 22.101	Noted
070218	7.2	S1-141146	Motorola Solutions Inc., Harris Corporation, US Department of Commerce	Additional Requirements for Late Call Entry Performance	Additional requirements for Late Call Entry Performance are proposed.	Revised to S1-141416
070264	7.2	S1-141147	Motorola Solutions Inc., Harris Corporation, US Department of Commerce	Requirements for Audio / Voice Quality	For drafting session	Agreed.
060101	6.1	S1-141148	Alcatel-Lucent	Summary of actions made to create version 0.0.1 of 3GPP TS 22.519	This document summarises the actions to create version 0.0.1 of 3GPP TS 22.519.	This is left open for off-line review.	Noted
060102	6.1	S1-141149	Rapporteur	Draft 3GPP TS 22.519 on Business Communication Requirements v.	TS	This is the new proposed version of the TS.	There are problems with the template.	Revised to S1-141398
080619	8.6	S1-141150	China Mobile, Huawei	Traffic steering Conclusion	For drafting session.	Noted in drafting.
999999	5.2	S1-141151	China Mobile, Hua Wei	Proposed WID for Flexible Mobile Service Steering (FMSS)	Revised to S1-141375
070201	7.2	S1-141152	Motorola Solutions	Way forward for MCPTT requirements in TS 22.179	This contribution proposes a way forward to reflect the newly available OMA and ETSI TCCE requirements on MCPTT into TS 22.179.	A volunteer is needed to maintain the table. The UK Home Office has concerns with this approach: they do not see what 3GPP is going to use the info for. Blackberry has the same concern: this can be done off-line by companies, but there is no particular reason why to include this in the documentation. For NSN, this might distract the focus. For Motorola, this is an efficient way to monitor the level of completion of the TS. Two companies support having it as a separate document, while 2 companies have concerns to do this even as a separate document.	Noted.
070202	7.2	S1-141153	Motorola Solutions	Annex with primary requirements for TS 22.179	This contribution shows the content of a proposed new Annex to 22.179, to serve as repository of the primary requirements and facilitate mapping between final requirements and primary ones.	This will be good to keep as a private document.	Noted.
060203	6.2	S1-141154	Huawei, Alcatel-Lucent	Removable of requirements & use cases to align IMS WebRTC stage 1 with stage 2	22.228	0200	F	12.6.0	Rel-12	IMS_WebRTC	The 3rd party (e.g. enterprise) related stage 1 requirements & use cases from Rel-12 of 22.228 are removed to align the IMS WebRTC stage 1 with stage 2.	The title has to be more explicit.	Revised to S1-141428
060204	6.2	S1-141155	Huawei, Alcatel-Lucent	Alignment of IMS WebRTC stage 1 Authentication requirements with stage 2	22.228	0201	F	12.6.0	Rel-12	IMS_WebRTC	Same as S1-141154 for authentication requirements.	Revised to S1-141429
070303	7.3	S1-141156	Huawei	Addition of WebRTC Firewall Traversal requirement	22.228	0202	B	12.6.0	Rel-13	eWebRTCi	A requirement is added to tell that, when accessing IMS services via WebRTC IMS client, the IMS shall allow media to traverse across a restrictive firewall.	For Ericsson, what browser will actually support might be different, so there is no point for 3GPP to define material that might be useless. This is postponed until this is clarified.	Noted.
080763	8.7	S1-141157	Huawei, China Mobile	ECIP Introduction	For drafting group.	Revised to S1-141355
080764	8.7	S1-141158	Huawei, China Mobile	ECIP Scope	Agreed in drafting.	Agreed.
080762	8.7	S1-141159	Huawei, China Mobile	ECIP “update to References, Definitions and Abbreviations”	For drafting group.	Revised to S1-141356
080619	8.6	S1-141160	Huawei	Use case on traffic steering based on APN	For drafting session. Ericsson see APN as a specific solution. Was revised to S1-141346	Revised to S1-141567
080619	8.6	S1-141161	Huawei	Use case on traffic steering based on time and/or location	For drafting session.	Revised to S1-141503
080619	8.6	S1-141162	Huawei	Traffic steering in roaming cases	For drafting session. Was revised to S1-141347 but the original version can be agreed.	Agreed.
999999	8.1	S1-141163	LG Electronics, Inc.	Some clarification in the statement of honouring ACDC category	Revised to S1-141387
080158	8.1	S1-141164	Rapporteur	ACDC TR editorial: references	Agreed in drafting.	Agreed.
080159	8.1	S1-141165	Rapporteur	ACDC TR editorial: to solve Editor's NOTE on a term 'honour'	Revised to S1-141341
080160	8.1	S1-141166	NTT DOCOMO	ACDC TR clean-up: use case 2 and 3, removing overlap with SCM.	Agreed in drafting.	Agreed.
080161	8.1	S1-141167	NTT DOCOMO, Qualcomm Incorporated	ACDC TR clean-up: use case 9, removing overlap with SCM.	Revised to S1-141338
080162	8.1	S1-141168	NTT DOCOMO	ACDC TR clean-up: use case 16, update of description due to SCM.	Agreed in the drafting.	Agreed.
080163	8.1	S1-141169	NTT DOCOMO	ACDC TR clean-up: clause 7, update of the list of potential requirements due to SCM.	Agreed in the drafting.	Agreed.
050202	5.2	S1-141170	NTT DOCOMO, et.al	WID proposal for Application specific Congestion control for Data Communication (ACDC)	WID	This is the actual feature resulting from the study.	Revised to S1-141523
080172	5.2	S1-141171	NTT DOCOMO, Qualcomm Incorporated, Sony Mobile Communication, NTC, Hitachi, LG Electronics	Requirements for ACDC	22.011	0203	B	12.1.0	Rel-13	ACDC	Revised to S1-141340
050210,2	5.2	S1-141172	China Unicom	Study on Enhancements to User Location Reporting Support	WID	This study aims to provide details about the possible scenarios and use cases where there is a need of enhanced user location reporting.	For Cisco, one of the aims is to reduce signalling, but if the granularity is smaller, this is quite contradictory. Sprint would like to see more explanations on what is device-based location and what are the commercial aspects.	Revised to S1-141379
050210	5.2	S1-141173	China Unicom	Discussion on Enhancements to User Location Reporting Support	This is a presentation to present the new proposed WID in S1-141172. There are different problems with the present location reporting procedure : There is no network initiated location reporting in GERAN ; The location reporting granularity for GERAN and UTRAN can be at least as fine as LTE to the cell level. For the IDLE state UEs, they have to move to the CONNECTED state in order to report their location. This will cause additional signalling load to the network and consume network resources. It is expected that the IDLE state UEs could report the location with less signaling, e.g. without moving to the CONNECTED state, especially in the congestion or emergency situation. The location reporting function can’t be controlled flexibly by the network; Tailored location reporting needs to be further analyzed. The network may only want to know the users with certain common characteristics not all the users in the area.	Noted.
080619	8.6	S1-141174	NEC	Use case on sub-networking for M2M traffic	For drafting session.	Noted in drafting.
080773	8.7	S1-141175	China Mobile	Contents of Enhanced Calling Information	For drafting group.	Revised to S1-141359
080775	8.7	S1-141176	China Mobile	Relation with other services	For drafting group. Withdrawn by the author.	Noted.
080772	8.7	S1-141177	China Mobile	Conclusion of FS_ECIP	For drafting group. Withdrawn by the author.	Noted.
080802	8.8	S1-141178	Sprint	PWS multi-media broadcast areas	Just as there is a need to map PWS text messages from geographic areas to selected cell and sectors, there is a similar need to select specific cells and sectors to broadcast a multi-media message	Revised to S1-141484
080803	8.8	S1-141179	Sprint	PWS multi-media linked messages	This introduces a link between PWS text messages to corresponding PWS multi-media messages.	Qualcomm support this proposal. There is a typo in the first requirement.	Revised to S1-141487
999999	7.1	S1-141180	KDDI	Additional Use Case to Address Third Party OTT Server Issues	Withdrawn
999999	8.11	S1-141181	KDDI	Coping with Third Party Server Issues	Withdrawn
050211	5.2	S1-141182	KDDI	Feasibility Study on Control of Applications when Third party Servers encounter difficulties	WID	The objective of this study is to identify potential requirements that will enable the 3GPP network to detect or receive an indication from a third party server of its congestion status or failure status and selectively control individual applications on UEs when the 3GPP network becomes aware that a third party server has run into difficulties.	For KPN, MTC has already introduced APN-based congestion. TeliaSonera think this is useful e.g. to control overuse of MTC.	Revised to S1-141397
999999	8.6	S1-141183	KDDI	Change Request to Use Case to Address steering based on status of subscription	Revised to S1-141436
999999	8.3	S1-141184	Vodafone	Rationale for provisioning, storage, and management of APN(s) within the (U)SIM on the UICC	Revised to S1-141254
070631,4	5.2	S1-141185	Orange	Proposed new WID on SMS-outbox update on Mobile	WID	This is a WID to specify service requirements for update the outgoing SMS sent from web portal in mobile SMS outbox without the need to download a specific application on mobile for doing this update.	There is a need to find more supporting companies.	Revised to S1-141525
070207	7.2	S1-141186	General Dynamics UK Ltd	Clarification of statements about authorisation of actions	A proposal to clarify a number of ambiguous statements about the authorization of various MCPTT behaviours described in the draft TS.	For the U.S. Department of Commerce, some proposed definitions are ambiguous: e.g. “group member” is confusing between “MCPTT” or “GCSE” group member.	Noted, to be discussed off-line when drafting S1-141406.
999999	8.4	S1-141187	Ericsson	Consideration on CSIPTO complexity and suggested conclusion	Revised to S1-141381
080403	8.4	S1-141188	Rapporteur	MCC's Editorial and Formatting Changes to TR22.828	TR	Agreed as a basis for future contributions.
070265	7.2	S1-141189	UK Home Office	Discussion on Group Management in GCSE and the Relationship to MCPTT	For drafting session	Noted without presentation.
070206	7.2	S1-141190	UK Home Office	Group Management for MCPTT	A number of contributions (S1-141191, S1-141235, S1-141189, S1-141186 and S1-141228) attempt to resolve the terminology issues associated with GCSE and MCPTT, this document attempts to consolidate and solve the issues detailed in those contributions.	This needs off-line discussion to coordinate and align between the different companies. Was revised to S1-141406 but confusion with numbers.	Revised to S1-141541
070203	7.2	S1-141191	UK Home Office	Background Document for Group Management in GCSE and MCPTT	The UK Home Office is trying to understand the interactions between MCPTT and GCSE/ProSe. They have has asked some related questions to the SA2 delegates.	For Telecom Italia, this is rather a survey, not a 3GPP technical document. Two documents used this number.	Revised to S1-141540
080305	8.3	S1-141192	Alcatel-Lucent	Advantages of Device management based solution	As noted at SA1#65, the MAPN study should include a comparison of the various solutions proposed for the use cases. This contribution proposes text to be added to clause 5 stating the advantages of the device management based solution.	Gemalto has concerns about the clarity of the proposed text. For Ericsson, this is a good material for the study. For G&D, this is very similar to the proposal from Vodafone: it describes the advantages of a given solution. A fair treatment is to have all advantages for all solutions or none. For Nokia, the arguments for not including the previous contributions are different, so they do not agree that it should be either both agreed or both rejected. Telecom Italia and G&D propose to wait for OMA’s answer before this can be included in the TR. As a compromise, it can be introduced together with an editor’s note telling that this is subject to OMA’s answer. See other documents on same topic (S1-141192, S1-141193, S1-141195 and S1-141234).	Revised to S1-141538
080306	8.3	S1-141193	Alcatel-Lucent	Disadvantages of UICC based solution	As noted at SA1#65, the MAPN study should include a comparison of the various solutions proposed for the use cases. This contribution proposes text to be added to clause 5 stating the disadvantages of the UICC based solution.	For Morpho, there is no advantage with the OMA DM approach: an equally important number of updates will have to be done compared to the UICC OTA. Gemalto disagree with the conclusion presented here. See other documents on same topic (S1-141192, S1-141193, S1-141195 and S1-141234).	Revised to S1-141537
999999	8.3	S1-141194	Alcatel-Lucent	Disadvantages of UICC based solution	Withdrawn
080307	8.3	S1-141195	Alcatel-Lucent	FS_MAPN conclusion	The proposed solution is that the UICC based solution would consume additional resources (e.g., signalling, APIs) and create complexities in the mid to long term scenario, where as Device Management based solution provides a more scalable solution. If the basis for a solution is not limited to existing infrastructure or if consideration is given to a need for additional parameter configuration other than simple storage of multiple APNs, then the UICC based solution is at a disadvantage to the device management based solution even in the short term.	See other documents on same topic (S1-141192, S1-141193, S1-141195 and S1-141234).	Noted.
080804	8.8	S1-141196	Sprint	Multi-media PWS capable UEs in a PLMN only broadcasting text PWS	The two following requirements are proposed: 1. UEs supporting both text and multi-media PWS messages must be able to determine whether a PLMN will broadcast existing text PWS messages only. 2. UEs supporting both text and multi-media PWS messages operating in a PLMN broadcasting existing text PWS messages only will behave in the same fashion as a UE only supporting existing text PWS messages.	This has to be rephrased as requirements.	Revised to S1-141488
070220	7.2	S1-141197	Alcatel-Lucent	EPS priority management	In order to support different priorities of MCPTT calls, requirements on the 3GPP EPS are needed in addition to application level requirements. Currently EPS systems provide 16 priority levels. The network operator manages these levels according to the needs of the various customers and applications they support. Such requirements are proposed.	“the 16 available priority levels” to be changed to “the existing available priority levels”	Revised to S1-141417
080601	8.6	S1-141198	Huawei	FMSS TR Cleanup	This contribution proposes cleanup / editorial changes to TR 22.808 v0.3.1.	Agreed.
081004	8.10	S1-141199	LG Electronics, Inc.	Discussion on integrity-protected caller ID	This paper proposes for 3GPP systems to provide mechanisms to protect the users of 3GPP UE’s and provide them with a certain warning to a proper extent when necessary.	This will be further progressed between now and next meeting.	Noted.
040007	4	S1-141200	C1-140742	LS on “Removal of option to subscribe for a notification of diversion occurrence”	LS in	Due to problems completing the work in IETF, CT1 has removed the option to subscribe for a notification of a diversion occurrence. Action: remove this option from the current release of MMtel	Noted. See related CRs in S1-141025 to S1-141029 and proposed answer in S1-141261.
040099	4	S1-141201	C1-141512	Reply LS on MMTEL and SMS prioritization	LS in	Noted without presentation.
040013,2	4	S1-141202	C1-141513	Reply LS on GCSE QCIs and connected mode DRX	LS in	CT1 indicates that a new QCI will impact CT1 specs and asks why the new QCI has higher priority compared with IMS signalling. No action required.	Noted without presentation.
040009,3	4	S1-141203	C4-140714	Reply LS on MTC Device Identification for LI	LS in	CT4 informs SA3-LI that enhancing IMEI to cater for larger number of devices will be investigated in future. No action required.	For NEC, the requirement is already there. For the chair, there are two problems: 1. What is SA1/Stage 1 impact on the solution, whatever it is, to identify MTC UE? 2. Is expanding IMEI the correct solution ? For Telecom Italia, the MTC UE should be considered as “normal” UEs, i.e. there should be no particular identifier for these.	Noted.
040003	4	S1-141204	CP-140187	LS on Transfer of ETSI business trunking specifications	LS in	CT indicates that it will take care of ETSI business trunking specifications but that TS 181 019 (Requirements) needs to be transferred to SA1. Action required. See agenda item 6.1.	Noted.
040015	4	S1-141205	MSG(14)AdH012r3	Migration of eCall Transport	LS in	ETSI MSG asks for feedback on their draft TR Migration of eCall Transport. Action required	Contributions/reviews of MSG material are invited.	Postponed.
040008	4	S1-141206	OMA-LS_998	LS To 3GPP SA1 about SEES work item	LS in	OMA asks for the latest status of SEES and next steps. OMA also suggests co-operation on any future work on APIs and asks SA1 to send related requirements so they can develop the APIs. Response required.	Proposed answer in S1-141067.
040099	4	S1-141207	R2-141005	LS on MMTEL and SMS prioritization	LS in	Noted without presentation.
040013,4	4	S1-141208	R3-140950	Reply LS on GCSE QCIs and connected mode DRX	LS in	RAN3 feedback on SA2 proposal. No action required	Noted without presentation.
040099	4	S1-141209	S2-140419	LS on UE requirements for PSAP callback	LS in	Noted without presentation.
040016	4	S1-141210	S2-140449	LS reply on Next hop policy rule use case accepted into WT-300	LS in	SA2 answers questions from BBF related to policy control of the Next hop for a particular service in the IP Edge and how this is supported in Rel-12 PCC specs. SA2 also informs BBF about the SA1 study FS_FMSS. No action required	Noted.
040099	4	S1-141211	S2-140494	Reply LS on ProSe Lawful Interception	LS in	Noted without presentation.
040099	4	S1-141212	S2-140510	Reply to Wi-Fi Alliance on LS on Signaling Optimization	LS in	Noted without presentation.
040005	4	S1-141213	S2-140554	LS on Maintenance of I-WLAN Solution	LS in	SA2 proposes to stop maintaining I-WLAN aspects and provides several reasons. If SA agrees then other WGs need to assess impact to their specifications and that external bodies would need to be notified. (SA1 impacted spec is 22.234) No action required	Noted.
040017	4	S1-141214	S2-140565	Reply LS on interaction of oneM2M with Underlying Networks	LS in	SA2 provides oneM2M summary of Rel-12 MTCe work item. SA2 also explains that Tsp is the only available reference point to exchange information with external service providers/applications and invites oneM2M to work with SA1 if functionality other than provided by Tsp is needed. No action required	Noted.
040099	4	S1-141215	S2-140568	LS reply on discovery message size	LS in	Noted without presentation.
040013	4	S1-141216	S2-140846	LS on GCSE QCIs and connected mode DRX	LS in	SA2 indicates that new QCIs will be needed and ask other WGs for feedback. Action/response required.	Noted.
040002	4	S1-141217	S2-141481	LS on co-ordination of response LS to ITU JCA-SDN	LS in	SA2 asks SA to consider responding to ITU JCA-SDN to provide information on ongoing work on SDN and NFV in 3GPP . No action required	Noted without presentation.
040099	4	S1-141218	S3-131155	Reply LS on LS on interactions of oneM2M with Underlying Networks	LS in	Noted without presentation.
040099	4	S1-141219	S3-140226	Reply to LS on discovery message size	LS in	Noted without presentation.
040009	4	S1-141220	SA3LI14_009r1	MTC Device Identification for LI	LS in	SA3LI asks SA1 to update TS 22.368 to make it explicitly clear that MTC MEs are required to fully support normal ME numbering and identification requirements. Action required	Noted, answer in S1-141260 See also CT4’s answer in S1-141203.
040006	4	S1-141221	SP-140149	Reply LS on Maintenance of I-WLAN Solution	LS in	SA agrees to stop maintaining I-WLAN aspects from Rel-12 onwards. SA to provide guidance on handling documentation in June. No action required	Noted. See related CRs in S1-141103 and S1-141104.
040001	4	S1-141222	SP-140160	LS on 3GPP activities on Network Functions Virtualisation	LS in	SA5 is about to start some work on management aspects of virtualised 3GPP functions. The scope of a potential 3GPP study on architecture and system level impacts to be assessed in June SA. No action required	Noted.
040004	4	S1-141223	SP-140171	Response LS on Transfer of ETSI business trunking specifications	LS in	3GPP will transfer the business trunking specification from ETSI to 3GPP. No action required.	Noted.
040014	4	S1-141224	S1-140146/oneM2M-TP-2013-0382R02	LS to 3GPP on support of alternate device triggering scheme for non-SMS capable devices	LS in	Postponed from SA1#65 oneM2M asks SA1 to consider requirements for non-SMS MTC triggering. Action/response required.	Ericsson is a bit surprised that the main motivation is for UEs which do not support SMS, which is a very cheap and easy mechanism to support. NEC propose to reply that there is no work on this. For Qualcomm, SA1 requirement is that the MTC UE has to be able to be triggered, there is no specific mention that this should be done by SMS, so if SMS is a problem, other mechanism can be considered. KDDI clarified that other mechanisms are indeed been considered by SA2.	Proposed reply in S1-141386.
040010	4	S1-141225	TCCE (14)000043	reply to 3GPP Liaison Statement: Mission-critical Push to Talk over LTE	LS in	ETSI TCCE provides their User Requirements Specification for consideration for MCPTT. Action required	Input contributions are invited at SA1 on this topic.	Noted, no answer at this stage.
040012	4	S1-141226	TIA TR88-14-024	TD SP-130727 - LS on Mission Critical Push To Talk over LTE	LS in	TIA provides advanced notice of a new document on Priority and QoS Control that they plan to submit the August SA1 meeting for MCPTT. No action required	Noted.
040011	4	S1-141227	OMA-LS_1003	LS to 3GPP TSG SA, SA1 and SA2 on MCPTT requirements	LS in	OMA provides their Requirements Document for consideration for MCPTT. Action required.	Noted. The UK HOME OFFICE will draft a proposed answer in S1-141385.
070204	7.2	S1-141228	TCCE 04(14)000035	LS on Analysis on the scope of GCSE and the PTT Application.	LS in	3GPP is asked to consider incorporating the aspects of GCSE that are not yet standardised into the MCPTT requirements.	See S1-141235 on the same topic. For drafting session	Noted.
999999	S1-141229	Not allocated	Not allocated
999999	8.10	S1-141230	LG Electronics, Inc.	Discussion on integrity-protected caller ID	Withdrawn
999999	8.10	S1-141231	LG Electronics, Inc.	Discussion on integrity-protected caller ID	Withdrawn
070266	7.2	S1-141232	Intel	Clarification on MCPTT operation modes	This contribution proposes to clarify Network-mode vs Direct-mode operation for MCPTT.	For drafting session: not handled. Some aspects can be integrated into the NIST document.	Noted.
050206	5.2	S1-141233	Rapporteur (NSN)	Rel-13 Maintenance WI for Group Communication System Enablers for LTE	This document proposes a maintenance WI for Rel-13 of Group Communication System Enablers for LTE (GCSE_LTE), to support the introduction of features postponed by SA2 from Rel-12 to Rel-13. It does not introduce new functionality.	Some clean-up is needed, revision marks have to be accepted. For Motorola, SA2 might not work on this in Rel-13. The Chair explained that this is not a valid argument at this stage: if needed, it will be transferred to the next Release. She also clarified that there is no such thing as “Release-independent requirements”.	Revised to S1-141395
080308	8.3	S1-141234	Rapporteur (G&D)	FS_MAPN conclusion	Here, the proposed solutions are: - for the USIM potential requirements: The 3GPP system shall enable provisioning, storage, and maintenance of multiple APNs within the (U)SIM on the UICC. - for the Device Management based solution: the OMA-DM solutions can be used to fulfil the use cases. OMA-DM Lightweight M2M (LWMM) should be enhanced to completely support the set of use cases.	Qualcomm, agrees on the second bullet but think it is not appropriate to put the first one. For Vodafone, the OMA DM is not the appropriate solution. For Ericsson, this is too early to discuss the conclusion since the pros and cons of each solution have not been appropriately discussed. Telecom Italia agree that the TR should clearly list the pros and cons of the 3 proposals, and this is not yet achieved.	Withdrawn. All related documents (S1-141192, S1-141193, S1-141195 and S1-141234) were discussed off-line. See results in S1-141514.
070205	7.2	S1-141235	NSN	Comparing Group Member States in MCPTT and GCSE	This paper briefly compares Group Member states of GCSE_LTE and User states of MCPTT and proposes to harmonise them.	Noted, to be discussed off-line when drafting S1-141406.
080501	8.5	S1-141236	InterDigital, KPN	Proposed Acronyms for eICBD	A new acronym is added: GRIPA for Globally Routable IP Address	For Intel, this term is not used so much so it is not worth introducing an acronym for it. This is also the view of KDDI, which delegate is a member of the American Association for the Abolition of Abusive Acronyms (aka AAAAA).	Noted.
070208	7.2	S1-141237	NSN	Aligning the General Group Call section with GCSE Terminology and clarifying roles of “UE” and “User” in MCPTT Requirements	Noted, to be discussed off-line when drafting S1-141406.
080502	8.5	S1-141238	InterDigital, KPN	Proposed missing requirements for eICBD security use case	The following potential requirements are added: - The 3GPP system shall not disclose identity and service information of a UE to other UEs unless specifically permitted by its user - The 3GPP system shall not forward user data to and from other users without both sides specific permission - User’s permission may be revoked at any time	Some of these requirements are already present in the document and duplications should be avoided.	Revised to S1-141480
080503	8.5	S1-141239	InterDigital, KPN	Corrections to Service Discovery use case	This tdoc proposes corrections to 4.5 Service discovery use case. A new requirement clarifies the respective roles of 3GPP system and a framework for discovery that is not part of the 3GPP system.	Agreed.
080504	8.5	S1-141240	KPN, Interdigital	Corrections to IP connection establishment use cases	This Tdoc proposes several corrections for the IP connection establishment use cases (4.1, 4.2 and 4.3).	This needs further off-line discussions with NSN.	Revised to S1-141481
050207	5.2	S1-141241	Alcatel-Lucent	New WID for VoLTE Paging Distinction	WID	The objective of this work item is to specify service requirements to allow a more aggressive paging policy for VoLTE terminations than for non-VoLTE terminations.	More companies are supporting.	Revised to S1-141390
050207,2	5.2	S1-141242	Alcatel-Lucent, Verizon, Oracle	Requirements to support differentiated paging for VoLTE	22.228	0199	B	12.6.0	Rel-13	VoLTE_PPD	This adds the requirement to allow differentiated paging for VoLTE from non-VoLTE services.	Revised to S1-141391
050207,4	5.2	S1-141243	Alcatel-Lucent, Verizon, Oracle	EPS Requirement to support differentiated paging for VoLTE	22.278	0201	B	12.4.0	Rel-13	VoLTE_PPD	Equivalent CR to 22.278.	Revised to S1-141392
080507	8.5	S1-141244	KPN, Interdigital	eICBD charging use case	22.807	This Tdoc proposes charging requirements for eICBD	Also more off-line talks are needed before agreement.	Revised to S1-141482
060201	6.2	S1-141245	KPN (Rapporteur)	End of Release 12 alignment of M2M service requirements	22.368	0153	F	12.3.0	Rel-12	MTCe-SRM	SA2 has completed its work on Release 12, so this CR aligns 22.368 to what have been defined in Stage 2.	More time is left for off-line review. “Other spec affected” to be set to “no”.	Revised to S1-141427
080202	8.2	S1-141246	KPN	Operational aspects of subscription data for local services in an isolated E-UTRAN	This document proposes that: - A mechanism is supported where a list of served users and groups (user and group identifiers) can be compiled from information collected from the served public safety UEs after the eNB has become isolated. - Security of credentials normally stored in the core network shall not be compromised by solutions for isolated E-UTRANs.	For NSN, the first bullet is a solution rather than a requirement. See the actual changes in S1-141247.	Noted.
080202,2	8.2	S1-141247	KPN	Modification of service requirements for isolated E-UTRAN	This tdoc proposes modifications of the potential requirements in 22.897 on the basis of the related discussion paper in S1-141246 on operational aspects of local subscription data.	Revised to S1-141441
999999	8.5	S1-141248	KPN	Offloading IP connection between devices use case	22.807 PCR	FS_eICBD	Revised to S1-141376
080805	8.8	S1-141249	Sprint	Separated text and multi-media PWS messages	The following potential requirement is proposed: The UE which supports both existing text PWS and multi-media PWS shall notify the user about the availability of the multi-media PWS message and display it when requested. Any existing text only PWS messages relating to the same emergency situation will be ignored.	Discussed off-line.	Revised to S1-141491
081005	8.10	S1-141250	Sprint	User reporting spoofed call use case	These requirements are proposed to be added: 1. The user is able to notify the network that an incoming call is believed to have spoofed caller identification. 2. The network operator is able to take further action based on this notification of an undetected spoofed call.	This should be phrased as requirements. NSN pointed out that, in steps 4, 5 and 6, Peter is not sure about the validity and then the call becomes classified as a spoofed call.	Revised to S1-141493
081006	8.10	S1-141251	Sprint	User reporting a call incorrectly identified as spoofed use case	These requirements are proposed to be added: 1. The user is able to notify the network that calls that had been identified and possibly blocked by the network are either not spoofed calls or an exception is needed for the particular user. 2. The network operator is able to take further action based on this notification that a spoofed call or call attempt detected to be spoofed is not considered spoofed by the user or an exception for the particular user is required.	Same comment.	Revised to S1-141494
081007	8.10	S1-141252	Sprint	User retrieval of spoofed call history	These requirements are proposed to be added: 1. The user is able to review the selected history list of spoofed call and call attempts identified by the network as spoofed. 2. The network selects the history list of spoofed calls available for users to review. 3. Within the selected history list of spoofed calls and call attempts, the user is able to manage the list entries.	Same comments.	Revised to S1-141495
070411	7.4	S1-141253	LGE	Discussion on Change of Time Zone in IOPS	It is proposed to state that an eNB, under IOPS operations shall be able to provide the Public Safety UE’s with Network Identity and TimeZone (NITZ) or Local Time Zone (LTZ) information and with proper ways of notification that the time zone has changed in the specific location where the Public Safety officer is located	For Telecom Italia, this implies that the eNodeB knows the location of the user, which might be complex to implement. So this needs rewriting to tell the proposal deals with the eNB and not with the user.	Revised to S1-141440
080304	8.3	S1-141254	Vodafone	Rationale for provisioning, storage, and management of APN(s) within the (U)SIM on the UICC	Revision of S1-141184. This paper discusses how M2M and Automotive markets are placing new requirements on Network Service Providers, and concludes that storage of APNs within the (U)SIM on the UICC with management of them by existing means is the most efficient way for NSPs to respond. It leads to the potential requirement that the 3GPP system shall enable provisioning, storage, and maintenance of multiple APNs within the (U)SIM on the UICC.	Hiding the APNs is not seen as an appropriate solution for gaining in security, according to Nokia and Qualcomm. Telecom Italia support the Vodafone’s approach: the Over The Air approach is better than e.g. OMA DM and the storage on the UICC since it will avoid problems of synchronisation. For Vodafone, this is a classical approach that the ME reads data from the SIM. For Ericsson, this is not the subject. For Qualcomm, this proposal adds complexity and does not provide any added security. The requirement is not acceptable. As well as all the rest of this document.	Noted.
070409	7.4	S1-141255	LG Electronics, Inc.	Discussion Paper – Considerations on Proper Indication on IOPS status to UE’s	It is proposed to clarify that An eNB operating in IOPS mode shall be able to provide the IOPS status information for Public Safety UEs.and for commercial UEs.	The proposal 1 is already covered by S1-141402, so S1-141435 will have to incorporate material from S1-141255. The proposal 2 is not agreeable: it deals with commercial aspects, but IOPS is only for public safety.	Noted, partly merged with S1-141402 in S1-141435.
080608	8.6	S1-141256	Juniper Networks, Vodafone, Telecom Italia, NSN	Traffic Steering based on operator's policies or user subscription	Revision of S1-141031. This contribution describes an FMSS use case to select security services flexibly based on operator’s policies or user subscription. The policies could be based on user’s subscription, white or black lists, or other data. The security services vary and could consist of multiple security services, such as Parental Control, DDoS, Antimalware, and Anti-virus.	Revised to S1-141456
070199	7.1	S1-141257	KPN, MCC	Proposed editorial clean-up to TR 22853v100	For drafting session.
070182	7.1	S1-141258	Huawei, NEC, KPN	Exposure of charging to 3rd party	22.115	0073r1	B	13.0.0	Rel-13	SEES	Revision of S1-141122	The CRs have not been updated to follow the consolidated requirements.	Revised to S1-141304
070183	7.1	S1-141259	Huawei, NEC, KPN	Exposure of network service and capabilities to 3rd party	22.101	0473r1	Revision of S1-141123	Revised to S1-141303
040009,2	4	S1-141260	Qualcomm Inc.	Reply LS on MTC Device Identification for LI	LS draft	Proposed answer to S1-141220. It is proposed to answer that, since expanding IMEI is not a trivial issue for operators, and the numbering capacity of the 56-bit IMEI is considerable, SA1 encourage GSMA and CT4 to devise ways to manage the numbering space as efficiently as possible, so that the IMEI lifetime reaches multiple decades to come.	The length of the IMEI is out of scope of SA1, so all the related text (the two last paragraphs) should be deleted. Other comments (Telecom Italia’s one, etc) to be taken into account.	Revised to S1-141384
040007,9	4	S1-141261	Ericsson	Reply LS to CT1, SA5 (cc CT, CT3, ETSI E2NA) on Removal of option to subscribe for a notification of diversion occurrence	LS draft	Replaces S1-141024. This is to confirm to CT1 and SA5 that the requirement for CDIVN is removed from the current as well as earlier releases.	The CRs were agreed in SA1 and should then be attached to the LS.	Revised to S1-141382
090201	9.2	S1-141262	Rapporteur (Alcatel-Lucent)	IMS_Corp2 status update	SU	Work/Study Item Completion: 95% Draft TS 22.519 Completion: 95% No controversial issues. Target completion date in WID: 06/2014 SP#64 Is current completion date the same as above? n If not, current target completion date: 09/2014 SP#65 Will target completion date be met? n Expected date to send TS to SA plenary: For information: SA1#66 (05/2014) For approval: SA1#67 (08/2014)	Approved.
090202	9.2	S1-141263	Rapporteur (KPN)	SEES status update	SU	Work/Study Item Completion: 80% Draft TR 22.853 Completion: 100% Target completion date in WID: 06/2014 SP#64 Current target completion date: 09/2014 SP#65 Will target completion date be met? Yes Expected date to send TS to SA plenary: For information: SA1#65 (01/2014) CRs for approval: SA1#67 (08/2014)	Approved.
090203	9.2	S1-141264	Rapporteur (US Department of Commerce)	MCPTT status update	SU	Approved.
090204	9.2	S1-141265	Rapporteur (Alcatel-Lucent)	eWebRTCi status update	SU	This WI has been approved at SP#63 Approved WID is in tdoc SP-140166 Work/Study Item Completion: 90% No controversial issues. Target completion date in WID: 09/2014 SA# 65 Will target completion date be met? y	Approved.
090206	9.2	S1-141266	Rapporteur (General Dynamics Broadband)	IOPS status update	SU	This WI has been approved at SP#63 Approved WID is in tdoc SP-140167 Work Item Completion: 60% Draft TS 22.xxx Completion: 60% Target completion date in WID: <09/2014> SP#65 Is current completion date the same as above? Yes Will target completion date be met? Yes Expected date to send <TS> to SA plenary: For approval: SA1#67 (08/2014)	Approved.
090207	9.2	S1-141267	Rapporteur (KPN)	SRMMTC status update	SU	There was just one CR which was noted, so no need to have a status update.	Withdrawn.
090208	9.2	S1-141268	Rapporteur (NTT DOCOMO)	FS_ACDC status update	SU	This WI has been approved at SP#57 Approved WID is in tdoc SP-120546 Update of WID has been approved at SP#61 Approved WID is in tdoc SP-130415 Study Item Completion: 90% Draft TR 22.806 Completion: 90% Target completion date in WID: 03/2014 SP#63 Is current completion date the same as above? n If not, current target completion date: 06/2014 SP#64 Will target completion date be met? n If not, change target completion date to: 09/2014 SP#65 Expected date to send TR to SA plenary: For approval: SA1#66 (05/2014)	Approved.
090209	9.2	S1-141269	Rapporteur (General Dynamics Broadband)	FS_IOPS status update	SU	This WI has been approved at SP#60 Approved WID is in tdoc SP-130596 Study Item Completion: 100% Draft TR 22.897 Completion: 100% Target completion date in WID: <06/2014> SP#64 Current target completion date: <06/2014> SP#64 Will target completion date be met? Yes Expected date to send TR to SA plenary: For approval: SA1#66 (05/2014)	Approved.
090210	9.2	S1-141270	Rapporteur (G&D)	FS_MAPN status update	SU	This WI has been approved at SA#61 Approved WID is in tdoc SP-130416 Work/Study Item Completion: 58% Draft TR completion: 58% Target completion date in WID: 03/2014 SA#63 Current target completion date: 12/2014 SA#65 Will target completion date be met? NO If not, change target completion date to: 12/2014	Approved.
090211	9.2	S1-141271	Rapporteur (Intel)	FS_CSIPTO status update	SU	This WI has been approved at SP#61 Approved WID is in tdoc SP-130417 Work/Study Item Completion: 100% Draft TR 22.828 Completion: 100%	Approved.
090212	9.2	S1-141272	Rapporteur (KPN)	eICBD status update	SU	This WI has been approved at SP#61 Approved WID is in tdoc SP-130418 Work/Study Item Completion: 70% Draft TR 22.807 Completion: 70% Target completion date in WID: 08/2014 SP#65 Current target completion date: 08/2014 SP#65 Will target completion date be met? Yes Expected date to send TR to SA plenary: For approval: SA1#67 (08/2014)	Approved.
090213	9.2	S1-141273	Rapporteur (China Mobile)	FS_FMSS status update	SU	This WI has been approved at SP#62 Approved WID is in tdoc SP-130597 Work/Study Item Completion: 80% Draft TR 22.808 Completion: 80% Target completion date in WID: 09/2014 SP#65 Current target completion date: 09/2014 SP#65 Will target completion date be met? Yes Expected date to send TR to SA plenary: For information: SA1#66 (05/2014) For approval: SA1#67 (08/2014)	For Cisco, this cannot be 80% since this is just send for information. 70% is seen more reasonable by SA1.	Approved with 70%.
090214	9.2	S1-141274	Rapporteur (China Mobile)	FS_ECIP status update	SU	This WI has been approved at SP#62 Approved WID is in tdoc SP-130598 Study Item Completion: 70% Draft TR 22.810 Completion: 70% Target completion date in WID: 06/2014 SP#64 Current target completion date: 09/2014 SP#65 Will target completion date be met? N Expected date to send TR to SA plenary: For information: SA1#66 (05/2014) For approval: SA1#67 (08/2014)	Approved.
090215	9.2	S1-141275	Rapporteur (Qualcomm)	FS_MBSP status update	SU	This WI has been approved at SP#62 Approved WID is in tdoc SP-130599 Work/Study Item Completion: 59% Draft TR 22.815 Completion: 59% Target completion date in WID: 06/2014 SP#64	Approved.
999999	9.2	S1-141276	Rapporteur (Telefonica)	FS_GUSH status update	SU	Revised to S1-141588
090216	9.2	S1-141277	Rapporteur (Sprint)	FS_UC_SPOOF status update	SU	This WI has been approved at SP#63 Approved WID is in tdoc SP-140074 Work/Study Item Completion: 15% Draft TR 22.898 Completion: 15% Target completion date in WID: <12/2014> SP#66 Is current completion date the same as above? Y Will target completion date be met? y Expected date to send TR to SA plenary: For information: SA1#67 (8/2014) For approval: SA1#68 (11/2014)	Approved.
070152	7.1.1	S1-141278	Rapporteur/Session chair	SEES drafting agenda	Revised to S1-141280
070151	7.1.1	S1-141279	Rapporteur/Session chair	SEES drafting report	Approved.
070152r	7.1.1	S1-141280	Rapporteur/Session chair	SEES drafting agenda	Revision of S1-141278	Noted.
070153	7.1.1	S1-141281	Editor	TR 22.853 on Study on Service Exposure and Enablement Support (SEES) requirements v1.0.1	TR	Agreed as a basis for future contributions at SA1#66.
070101rr	7.1	S1-141282	Ericsson	Update of the Connection Patterns use case	Revision of S1-141420	Agreed
070103rr	7.1	S1-141283	Huawei, KPN	Complete FFS on Presence/LCS and on reason	Revision of S1-141422	Agreed.
070103rr	7.1	S1-141284	Huawei, KPN, China Mobile	Generic requirements on service/capability exposure towards third parties	Revision of S1-141423	Agreed at the drafting.	Revised to S1-141551
070106rr	7.1	S1-141285	China Unicom	Use Case on Terminal Characteristics Exposure	Revision of S1-141424	Withdrawn
999999	7.1.1	S1-141286	Huawei	Consolidated SEES capabilities	Revised to S1-141545
7.4.1	S1-141287	Rapporteur/Session chair	IOPS/FS_IOPS drafting agenda	Noted.
070451	7.4.1	S1-141288	Rapporteur/Session chair	IOPS/FS_IOPS drafting report	Approved.
070404rr	7.4	S1-141289	French Ministry of Interior	Minimum set of services for an isolated E-UTRAN	Revision of S1-141489	Agreed in drafting.	Agreed.
070410rr	7.4	S1-141290	French Ministry of Interior	Operational requirements for isolated E UTRAN operation	Revision of S1-141439	Agreed.
999999	7.4.1	S1-141291	Not allocated	Not allocated
999999	7.4.1	S1-141292	Not allocated	Not allocated
999999	7.4.1	S1-141293	Not allocated	Not allocated
999999	7.4.1	S1-141294	Not allocated	Not allocated
999999	7.4.1	S1-141295	Not allocated	Not allocated
999999	7.4.1	S1-141296	Not allocated	Not allocated
999999	S1-141297	Not allocated	Not allocated
999999	S1-141298	Not allocated	Not allocated
999999	S1-141299	Not allocated	Not allocated
050204r	5.2	S1-141300	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, Acer, China Mobile, China Telecom, KPN	Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO)	WID	Revision of S1-141143	Revised to S1-141301
050204rr	5.2	S1-141301	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, Acer, China Mobile, China Telecom, KPN	Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO)	WID	Revision of S1-141300	The revision marks have to be cleaned-up.	Revised to S1-141566
080699	8.6	S1-141302	Huawei	Consolidation of new requirements agreed in this meeting	This contribution proposes content for consolidated requirements section 6 for FMSS TR.	NSN support this approach.	Agreed.
070183r	7.1	S1-141303	Huawei, NEC, KPN	Exposure of network service and capabilities to 3rd party	22.101	0473r2	B	13.2.0	Rel-13	SEES	Revision of S1-141259	More time is given to reviews by the next meeting.	Noted.
070182r	7.1	S1-141304	Huawei, NEC, KPN	Exposure of charging to 3rd party	22.115	0073r2	B	13.0.0	Rel-13	SEES	Revision of S1-141258	Comments to be cleaned-up.	Noted.
080166	7.1	S1-141305	FS_ACDC Rapporteur	Proposed cover sheet for FS_ACDC TR	The outstanding issue is for the normative work, not for the TR.	Revised to S1-141601
080172rr	5.2	S1-141306	NTT DOCOMO, Qualcomm Incorporated, Sony Mobile Communication, NTC, Hitachi, LG Electronics, SHARP, NTT, TeliaSonera	Access control mechanism for operator-identified applications	22.011	0203r2	B	12.1.0	Rel-13	ACDC	Revision of S1-141340	Agreed.
080795	8.7	S1-141307	Rapporteur	Cover page for TR22.810 on ECIP WID	For NSN, the result will be an independent service, not the improvement of an existing one as written here. The second sentence of the abstract is not seen as accurate by Orange and is asked to be deleted. The outstanding issues need to be rephrased.	Revised to S1-141603
S1-141308	Chair’s reserve	Not allocated
S1-141309	Chair’s reserve	Not allocated
070252	7.2.1	S1-141310	Rapporteur/Session chair	MCPTT drafting agenda	Noted.
070251	7.2	S1-141311	Rapporteur/Session chair	MCPTT drafting report	It is proposed to have an extra ad-hoc meeting for MCPTT around July (12 companies supporting) or October (8 companies supporting) time frame.	Approved.
070278	7.2.1	S1-141312	Home Office	Proposed Merged Security Requirements for MCPTT	Proposals for security requirements to be included in the MCPTT Stage 1 TS	It was wondered if the requirement “14) The PTT service shall support lawful interception” is needed, since this is by law. Some have to be rewritten for clarity reasons.	Revised to S1-141318
070279	7.2.1	S1-141313	Motorola Solutions	Add definition of “participant type” to 3.1	This contribution adds additional definitions “participant” and “participant type” in TS 22.179.	Revised to S1-141585
070220rr	7.2	S1-141314	Alcatel-Lucent	EPS priority management	Revision of S1-141417	Edited on-line.	Revised to S1-141586
070219r	7.2	S1-141315	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for PTT Priority Requirements	Revision of S1-141075	Agreed in drafting.	Agreed.
070267r	7.2	S1-141316	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for personality management	Revision of S1-141078	Final review in SA1.	Agreed.
070268r	7.2	S1-141317	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for location	Revision of S1-141079	Agreed.
070278r	7.2.1	S1-141318	Home Office	Proposed Merged Security Requirements for MCPTT	Revision of S1-141312	Agreed.
070270r	7.2	S1-141319	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for interworking with Project 25	Revision of S1-141081	Revised to S1-141587
070271r	7.2	S1-141320	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for interworking with Legacy Land Mobile Radio	Revision of S1-141082	Agreed.
070262r	7.2	S1-141321	French Ministry of Interior	Inter system operations requirements	Revision of S1-141054	Agreed.
070272r	7.2	S1-141322	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Off network	Revision of S1-141083	Noted.
999999	7.2.1	S1-141323	Not allocated.	Not allocated.
999999	7.2.1	S1-141324	Not allocated.	Not allocated.
999999	7.2.1	S1-141325	Not allocated.	Not allocated.
999999	7.2.1	S1-141326	Not allocated.	Not allocated.
999999	7.2.1	S1-141327	Not allocated.	Not allocated.
999999	7.2.1	S1-141328	Not allocated.	Not allocated.
999999	7.2.1	S1-141329	Not allocated.	Not allocated.
999999	7.2.1	S1-141330	Not allocated.	Not allocated.
999999	7.2.1	S1-141331	Not allocated.	Not allocated.
999999	7.2.1	S1-141332	Not allocated.	Not allocated.
999999	7.2.1	S1-141333	Not allocated.	Not allocated.
080152	8.1.1	S1-141334	Rapporteur/Session chair	FS_ACDC drafting agenda	Noted.
080151	8.1.1	S1-141335	Rapporteur/Session chair	FS_ACDC drafting report	Approved.
080153r	8.1	S1-141336	Teliasonera AB	Proposal for conclusion on ACDC and Network Sharing (Use Case 15)	Revision of S1-141100	Revised to S1-141337
080153rr	8.1	S1-141337	Teliasonera AB	Proposal for conclusion on ACDC and Network Sharing (Use Case 15)	Revision of S1-141336	Agreed in the drafting.	Agreed.
080161r	8.1	S1-141338	NTT DOCOMO, Qualcomm Incorporated	ACDC TR clean-up: use case 9, removing overlap with SCM.	Revision of S1-141167	Was Revised to S1-141549 but another number used by mistake.	Revised to S1-141509
080154r	8.1	S1-141339	Qualcomm Incorporated	ACDC System Overview	Revision of S1-141105	Revised to S1-141550
080172r	5.2	S1-141340	NTT DOCOMO, Qualcomm Incorporated, Sony Mobile Communication, NTC, Hitachi, LG Electronics	Requirements for ACDC	22.011	0203r1	B	12.1.0	Rel-13	ACDC	Revision of S1-141171	Revised to S1-141306
080159r	8.1	S1-141341	Rapporteur	ACDC TR editorial: to solve Editor's NOTE on a term 'honour'	Revision of S1-141165	Agreed in drafting.	Agreed.
050203r	5.2	S1-141342	Qualcomm Incorporated, NTT DOCOMO	Consolidation of Potential Requirements from TR 22.806 Study to Normative Text	Revision of S1-141109	Agreed.
080609	8.6.1	S1-141343	Rapporteur/Session chair	FS_FMSS drafting agenda	Noted.
080651	8.6.1	S1-141344	Rapporteur/Session chair	FS_FMSS drafting report	Approved.
080619r	8.6	S1-141345	ZTE, China Mobile, China Telecom, China Unicom, CATT	Use Case for Flexible Mobile Service Steering -- Service Chain Bootstrapping and Auto Re-configuration	Revision of S1-141377	This is now very similar to S1-141554. The differences have to be checked off-line and clarified in a new version.	Revised to S1-141583
080619r	8.6	S1-141346	Huawei	Use case on traffic steering based on APN	Revision of S1-141160	Noted.
080619r	8.6	S1-141347	Huawei	Traffic steering in roaming cases	Revision of S1-141162	Withdrawn
080619rr	8.6	S1-141348	China Mobile, Huawei	FMSS Consolidated requirements	Revision of S1-141471	Agreed at drafting.	Agreed. The rapporteur will put the requirements back in the use case at implementation.
080699	8.6.1	S1-141349	Huawei	Cleanup to the TR	Withdrawn
080608rr	8.6	S1-141350	Juniper Networks, Vodafone, Telecom Italia, NSN	Traffic Steering based on operator's policies or user subscription	Revision of S1-141456	Agreed at drafting	Agreed.
080603rr	8.6	S1-141351	Huawei, China Mobile, Alcatel Lucent, Orange	Overview section for FMSS	Revision of S1-141442	Agreed at drafting	Agreed.
080607rr	8.6	S1-141352	China Mobile, Huawei, Orange	Generic requirements on service steering	Revision of S1-141455	Revised to S1-141542
080751	8.7.1	S1-141353	Rapporteur/Session chair	FS_ECIP drafting agenda	Noted.
080751	8.7.1	S1-141354	Rapporteur/Session chair	FS_ECIP drafting report	Approved.
080763r	8.7	S1-141355	Huawei, China Mobile	ECIP Introduction	Revision of S1-141157	Agreed in drafting.	Agreed.
080762r	8.7	S1-141356	Huawei, China Mobile	ECIP “update to References, Definitions and Abbreviations”	Revision of S1-141159	Agreed in drafting.	Agreed.
080774r	8.7	S1-141357	NSN, China Mobile, Huawei	Definition for Enhanced Call Information	Revision of S1-141014	Agreed.
080768r	8.7	S1-141358	NSN, China Mobile, Huawei	Clarification of user vs. calling and called party	Revision of S1-141015	Agreed in drafting.	Agreed.
080773r	8.7	S1-141359	China Mobile	Contents of Enhanced Calling Information	Revision of S1-141175	Agreed.
080770r	8.7	S1-141360	NSN	Clarification on Pre-conditions	Revision of S1-141018	Withdrawn.
080771r	8.7	S1-141361	NSN	Clarification on Service flows	Revision of S1-141019	Withdrawn.
080777r	8.7	S1-141362	NSN	Update to Potential Requirements	Revision of S1-141020	Withdrawn.
080952	8.9.1	S1-141363	Rapporteur/Session chair	FS_GUSH drafting agenda	Noted.
080951	8.9.1	S1-141364	Rapporteur/Session chair	FS_GUSH drafting report	Approved.
080906r	8.9	S1-141365	Telefonica	Update to Section 4.14 (Scenario and use case 12)	22.852	0007r1	D	12.0.0	Rel-13	FS_GUSH	Revision of S1-141094	For drafting session. Agreed in drafting.	Agreed.
080907rr	8.9	S1-141366	Telefonica	Add new Section 4.16 (Scenario and use case 14)	22.852	0008r2	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141466	Agreed in the drafting.	Agreed.
080909rr	8.9	S1-141367	Telefonica	Add new Section 4.17 (Scenario and use case 15)	22.852	0009r2	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141467	Agreed in the drafting.	Agreed.
080911rr	8.9	S1-141368	Telefonica	Update to Section 6 (Potential Requirements)	22.852	0011r2	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141469	Agreed in the drafting.	Agreed.
080912rr	8.9	S1-141369	Telefonica	Update to Section 7 (Conclusion and recommendations)	22.852	0012r2	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141470	Agreed.
999999	8.9.1	S1-141370	Not allocated	Not allocated
999999	8.9.1	S1-141371	Not allocated	Not allocated
999999	8.9.1	S1-141372	Not allocated	Not allocated
010301,3	1.3	S1-141373	MCC	2nd Draft minutes of SA1#65	Revised to S1-141005
080402	8.4	S1-141374	Intel, Samsung, KPN, Sony Mobile, Interdigital	Responses to S1-141381 (Consideration on CSIPTO complexity and suggested conclusion)	This document provides responses to the issues raised in S1-141381. It concludes that the complexity and restrictions depends on the solutions used. Solutions are outside the scope of SA1, and that it is premature to prevent CSIPTO from moving to stage 2 without further work.	Noted.
050201	5.2	S1-141375	China Mobile, Hua Wei	Proposed WID for Flexible Mobile Service Steering (FMSS)	WID	Replaces S1-141151. A new WID is proposed to define the requirements to enable the Core Network to control steering policy that will select required service functions of the service network (e.g. Gi-LAN network). The aim is to realize efficient and flexible mobile service steering in the Gi-LAN network. SA1 will develop requirements for actively managing steering policy generation.	It is clarified that the TR 22.808 has no conclusion yet. It is open for further off-line discussion. The intention is to refine the proposal at this meeting and have it approved at next meeting.	Revised to S1-141393
080508	8.5	S1-141376	KPN, Interdigital	Offloading IP connection between devices use case	Replaces S1-141248. This document proposes a use case that illustrates the possibility to offload a connection between two devices to ProSe direct mode	Revised to S1-141483
080619	8.6	S1-141377	ZTE, China Mobile, China Telecom, China Unicom, CATT	Use Case for Flexible Mobile Service Steering -- Service Chain Bootstrapping and Auto Re-configuration	Replaces S1-141051	For drafting session.	Revised to S1-141345
080615	8.6	S1-141378	ZTE Corporation	Use Case for Service Chain Status update	Replaces S1-141050. The contribution proposes a use case for service chain status update	For drafting session.	Revised to S1-141502
050210,2r	5.2	S1-141379	China Unicom	Study on Enhancements to User Location Reporting Support	WID	Revision of S1-141172	Revised to S1-141562
050210r	5.2	S1-141380	China Unicom	Discussion on Enhancements to User Location Reporting Support	Revision of S1-141173	Withdrawn.
080401	8.4	S1-141381	Ericsson, Vodafone, NSN	Consideration on CSIPTO complexity and suggested conclusion	Replaces S1-141187. This document proposes a conclusion for the TR 22.828 "Study on Co-ordinated PGW change for Selected IP Traffic Offload (CSIPTO)" which is that: The work performed in the CSIPTO study does not justify the complexity and restrictions it imposes on the 3GPP architecture and thus the work should conclude without adding any new requirements for this feature.	See S1-141374 on the same topic.	Noted.
040007,9r	4	S1-141382	Ericsson	Reply LS to CT1, SA5 (cc CT, CT3, ETSI E2NA) on Removal of option to subscribe for a notification of diversion occurrence	LS draft	Replaces S1-141261	Agreed.
040008,2r	4	S1-141383	Huawei	Draft Reply to OMA Architecture Working Group (Cc SA2) about SEES work item	LS draft	Replaces S1-141067, Proposed answer to S1-141383. It is explained that SA1 is currently in the process of defining service requirements for new complementary network capabilities to be exposed to 3rd parties. It is expected that 3GPP will not define any SEES APIs and Exposure Layer as suggested in the LS from OMA ARC WG.	“SA1” to be changed into “3GPP WG SA1”.	Revised to S1-141527
040009,2r	4	S1-141384	SA1/Qualcomm Inc.	Reply LS to SA3LI, GSMA TSG, CT4 (cc SA, SA2, SA3, CT1, GSMA FF) on MTC Device Identification for LI	LS draft	Replaces S1-141260	Approved.
040011,2	4	S1-141385	UK HOME OFFICE	LS to OMA COM of the Open Mobile Alliance (cc SA2) on MCPTT Requirements	LS draft	Proposed answer to S1-141227 It is proposed to answer that SA1 is interested in having feedback from OMA on the following: - is there a plan for OMA to do an assessment of the MCPTT SA1 requirements and the degree to which they are already met within what is already standardised within OMA PoC? - Has it been agreed within OMA the potential role for OMA with respect to Stage 2 MCPTT work?	For the US government, this is becoming a circular situation, since OMA is asking about SA1’s requirements, and SA1 is now asking about the OMA’s requirements. For T-Mobile USA and the French government, this response is appropriate. For Telecom Italia and T-Mobile USA, the first question is too vague. This is sent to off-line discussion.	Revised to S1-141530
040014,2	4	S1-141386	SA1/NEC	LS to oneM2M on support of alternate device triggering scheme for non-SMS capable devices	LS draft	Proposed answer to S1-141224. It is proposed to answer that SA1 has specified requirements on MTC Device triggering in section 7.1.2 of TS 22.368, however SA1 does not specify the specific mechanism that performs such triggering. Implementation of the requirement is not in the scope of SA1.	Approved.
080164	8.1	S1-141387	LG Electronics, Inc.	Some clarification in the statement of honouring ACDC category	Replaces S1-141163	Noted in the drafting.	Noted.
010301,3r	1.3	S1-141388	MCC	2nd Draft minutes of SA1#65	Replaces S1-141373	Withdrawn
050206	5.2	S1-141389	Qualcomm Incorporated	Review of ProSe stage-1 fulfilment (TS 22.278)	Replaces S1-141086. This contribution proposes an analysis of which SA1 requirements have been met in Release 12, which have not, and which are still in flux. This document will guide the creation of CRs to align Release 12 stage-1 with stage-2 & 3 and to bring these requirements forward into Release 13.	Telecom Italia noticed that Stage 2 and Stage 3 are not aligned anyway, so this alignment work will have to wait until stages 2 and 3 are aligned. KPN propose to align to Stage 2 for the time being. The content of the contribution is seen as correct at this stage but the complete “exercise” is proposed to be shifted to later on.	Revised to S1-141539
050207r	5.2	S1-141390	Alcatel-Lucent	New WID for VoLTE Paging Distinction	WID	Revision of S1-141241	Revised to S1-141524
050207,2r	5.2	S1-141391	Alcatel-Lucent, Verizon, Oracle	Requirements to support differentiated paging for VoLTE	22.228	0199r1	B	12.6.0	Rel-13	VoLTE_PPD	Revision of S1-141242	Revised to S1-141575
050207,4r	5.2	S1-141392	Alcatel-Lucent, Verizon, Oracle	EPS Requirement to support differentiated paging for VoLTE	22.278	0201r1	B	12.4.0	Rel-13	VoLTE_PPD	Revision of S1-141243	Revised to S1-141576
050201r	5.2	S1-141393	China Mobile, Hua Wei	Proposed WID for Flexible Mobile Service Steering (FMSS)	WID	Revision of S1-141375	Noted.
050205r	5.2	S1-141394	Qualcomm Incorporated	New WID for ProSe Maintenance (ProSeM)	WID	Revision of S1-141085. The objective is to clarified to be for both the support stage 2/3 development during Release 1 and for the support of end-of-release 12 maintenance. A list of topics is now provided.	See related discussion paper in S1-141389. One more supporting company.	Revised to S1-141569
050206r	5.2	S1-141395	Rapporteur (NSN)	Rel-13 Maintenance WI for Group Communication System Enablers for LTE	Revision of S1-141233	The list of supporting companies has to be cleaned-up.	Revised to S1-141571
050208,2r	5.2	S1-141396	III, ITRI	WID proposal: Long Range Cell Operation for Public Safety (LCOPS)	WID	Revision of S1-141013	For Telecom Italia, the objective is not new. Several companies are in the opinion that this is outside SA1 scope. So this is noted as well as all the related documents in S1-141008 to S1-141012.	Revised to S1-141536
050211r	5.2	S1-141397	KDDI	Feasibility Study on Control of Applications when Third party Servers encounter difficulties	WID	Revision of S1-141182. The justification part has been rewritten.	For Qualcomm, this approach is not efficient. This is explained to be wider in scope than ACDC. Another chance is given to off-line agreement.	Revised to S1-141526
060102r	6.1	S1-141398	Rapporteur	Draft 3GPP TS 22.519 on Business Communication Requirements v.	TS	Revision of S1-141149	CP in S1-141600	Agreed to be sent for information.
070401	7.4	S1-141399	General Dynamics UK Ltd	Definitions and abbreviation in support of normative requirements for Isolated E-UTRAN operation	22.278	0202	B	12.4.0	Rel-13	IOPS	Revision of S1-141052. The CR adds the definitions and an abbreviation in support of Isolated E-UTRAN operation	Some updates are needed on the cover page, including the title.	Revised to S1-141432
070402	7.4	S1-141400	General Dynamics UK Ltd	Service description for Isolated E-UTRAN operation	22.278	0203	B	12.4.0	Rel-13	IOPS	Revision of S1-141053. A service description of Isolated E-UTRAN Operation for Public Safety is added.	Same comments apply.	Revised to S1-141433
070403	7.4	S1-141401	General Dynamics UK Ltd	General, subscriber and service management normative requirements for Isolated E-UTRAN operation	22.278	0204	B	12.4.0	Rel-13	IOPS	Revision of S1-141055. General, subscriber and service management normative requirements for Isolated E-UTRAN operation are added.	Same comments.	Revised to S1-141434
070405	7.4	S1-141402	General Dynamics UK Ltd	Normative requirements for initiation of Isolated E-UTRAN operation	22.278	0205	B	12.4.0	Rel-13	IOPS	Revision of S1-141057. Some requirements for initiation of Isolated E-UTRAN operation are added.	The cover page needs to be cleaned-up. This is to be reviewed in the drafting session.	Revised to S1-141435
070406	7.4	S1-141403	General Dynamics UK Ltd	Normative requirements for ongoing Isolated E-UTRAN operation	22.278	0206	B	12.4.0	Rel-13	IOPS	Revision of S1-141059. Some requirements for ongoing Isolated E-UTRAN operation are added.	Revised to S1-141476
070407	7.4	S1-141404	General Dynamics UK Ltd	Normative requirements for termination of Isolated E-UTRAN operation	22.278	0207	B	12.4.0	Rel-13	IOPS	Revision of S1-141060. Some requirements for termination of Isolated E-UTRAN operation are added.	Revised to S1-141437
070408	7.4	S1-141405	General Dynamics UK Ltd	Normative requirements for security aspects of Isolated E-UTRAN operation	22.278	0208	B	12.4.0	Rel-13	IOPS	Revision of S1-141061. Some requirements for security aspects of Isolated E-UTRAN operation are added.	There are some overlaps with KPN’s documents.	Revised to S1-141438
070206r	7.2	S1-141406	UK Home Office	Group Management for MCPTT	Revision of S1-141190	For drafting session	Withdrawn.
070209r	7.2	S1-141407	US Department of Commerce, General Dynamics UK Ltd, T-Mobile USA Inc., Blackberry	Service description for Section 4.1, Overview	Revision of S1-141068	For drafting.	Agreed.
070210r	7.2	S1-141408	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Additional Floor control requirements, section 4.2	Revision of S1-141069	For drafting session: agreed in drafting.	Agreed.
070274	7.2	S1-141409	U.S. Department of Commerce	PTT vs MCPTT	For drafting.	Agreed.
070211r	7.2	S1-141410	Alcatel-Lucent, US Department of Commerce	Modifications to a single Floor control requirement on hierarchy in section 4.2	Revision of S1-141070	For drafting session: agreed in drafting.	Agreed.
070212r	7.2	S1-141411	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Additional General Group Call requirements, section 4.3	Revision of S1-141071	For drafting session: agreed in drafting.	Agreed.
070213r	7.2	S1-141412	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Broadcast / Announcement Group Calls	Revision of S1-141072	For drafting session: agreed in drafting.	Agreed.
070214r	7.2	S1-141413	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Dynamic Group management	Revision of S1-141073	For drafting session: agreed in drafting.	Agreed.
070215r	7.2	S1-141414	Ericsson	Q&A about the concept of PTT Session	Revision of S1-141115	For drafting session: noted.	Noted.
070216r	7.2	S1-141415	Motorola Solutions Inc., Harris Corporation, US Department of Commerce	Additional requirements for Audio PTT Call Performance	Revision of S1-141074	For drafting session: agreed in drafting.	Agreed.
070218r	7.2	S1-141416	Motorola Solutions Inc., Harris Corporation, US Department of Commerce	Additional Requirements for Late Call Entry Performance	Revision of S1-141146	For drafting session: agreed in drafting.	Agreed.
070220r	7.2	S1-141417	Alcatel-Lucent	EPS priority management	Revision of S1-141197	For drafting session	Revised to S1-141314
070221r	7.2	S1-141418	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Emergency Group Calls	Revision of S1-141076	For drafting session: agreed in drafting.	Agreed.
070222r	7.2	S1-141419	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Imminent Peril Call	Revision of S1-141077	For drafting session: agreed in drafting.	Agreed.
070101r	7.1	S1-141420	Ericsson	Update of the Connection Patterns use case	Revision of S1-141116	For drafting session.	Revised to S1-141282
070102r	7.1	S1-141421	Huawei, NEC, KPN	Clarification of background traffic use case	Revision of S1-141042	For drafting session. Agreed at drafting. The Note should be in Note format. That will be corrected at implementation.	Agreed.
070103r	7.1	S1-141422	Huawei, KPN	Complete FFS on Presence/LCS and on reason	Revision of S1-141048	For drafting session.	Revised to S1-141283
070103r	7.1	S1-141423	Huawei, KPN, China Mobile	Generic requirements on service/capability exposure towards third parties	Revision of S1-141043	For drafting session.	Revised to S1-141284
070106r	7.1	S1-141424	China Unicom	Use Case on Terminal Characteristics Exposure	Revision of S1-141118	For drafting session.	Revised to S1-141285
070106r	7.1	S1-141425	Huawei, NEC, KPN, China Mobile	Consolidation of SEES service/capabilities	Revision of S1-141066	For drafting session.	Revised to S1-141286
080604	8.6	S1-141426	NSN	Proposed FMSS Definitions and Overview	Revision of S1-141036. This document proposes Service Steering definitions and Overview.	Some delegates ask for more time to review the proposal, e.g. at the drafting session. A simplification of the document is requested.	Revised to S1-141443
060201r	6.2	S1-141427	KPN (Rapporteur)	End of Release 12 alignment of M2M service requirements	22.368	0153r1	F	12.3.0	Rel-12	MTCe-SRM	Revision of S1-141245	Only the cover page has been cleaned-up.	Agreed.
060203r	6.2	S1-141428	Huawei, Alcatel-Lucent	Removable of requirements & use cases to align IMS WebRTC stage 1 with stage 2	22.228	0200r1	F	12.6.0	Rel-12	IMS_WebRTC	Revision of S1-141154	Agreed.
060204r	6.2	S1-141429	Huawei, Alcatel-Lucent	Alignment of IMS WebRTC stage 1 Authentication with stage 2	22.228	0201r1	F	12.6.0	Rel-12	IMS_WebRTC	Revision of S1-141155	Agreed.
070301r	7.3	S1-141430	Alcatel-Lucent, Huawei, Intel	Use case for end to end WebRTC bearer support over IMS	22.228	0197r1	B	12.6.0	Rel-13	eWebRTCi	Revision of S1-141101	The text is cleaned-up. Some changes over changes to be removed.	Revised to S1-141531
070302r	7.3	S1-141431	Alcatel-Lucent, Huawei, Intel	Support for end to end WebRTC bearer support over IMS	22.228	0198r1	B	12.6.0	Rel-13	eWebRTCi	Revision of S1-141102	The reference to 3GPP Releases has been removed, the text has been clarified. Some changes over changes to be removed.	Revised to S1-141532
070401r	7.4	S1-141432	General Dynamics UK Ltd	Definitions and abbreviation for Isolated E-UTRAN operation	22.278	0202r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141399	Agreed.
070402r	7.4	S1-141433	General Dynamics UK Ltd	Service description for Isolated E-UTRAN operation	22.278	0203r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141400	Agreed.
070403r	7.4	S1-141434	General Dynamics UK Ltd	General, subscriber and service management normative requirements for Isolated E-UTRAN operation	22.278	0204r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141401	Agreed in drafting. Revisions over revisions.	Revised to S1-141556
070405r	7.4	S1-141435	General Dynamics UK Ltd	Normative requirements for initiation of Isolated E-UTRAN operation	22.278	0205r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141402	Agreed in drafting.	Agreed.
080609	8.6	S1-141436	KDDI	Change Request to Use Case to Address steering based on status of subscription	Revision of S1-141183. This is a CR to an existing use case to address traffic steering based on the user’s subscription status. The existing use case addresses a small number of subscription types such as priority. This P-CR adds wider approach to subscription types to address the status of subscriber services such as web filtering for children, employees and virus detection.	Some off-line checking with Juniper documents has to be performed.	Agreed.
070407r	7.4	S1-141437	General Dynamics UK Ltd	Normative requirements for termination of Isolated E-UTRAN operation	22.278	0207r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141404	For drafting session. General Dynamics wish to further progress the topic between now and next meeting.	Noted.
070408r	7.4	S1-141438	General Dynamics UK Ltd	Normative requirements for security aspects of Isolated E-UTRAN operation	22.278	0208r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141405	For drafting session. Same as for S1-141437.	Noted.
070410r	7.4	S1-141439	French Ministry of Interior	Operational requirements for isolated E UTRAN operation	Revision of S1-141058	For drafting session.	Revised to S1-141290
070411r	7.4	S1-141440	LGE	Discussion on Change of Time Zone in IOPS	Revision of S1-141253	For drafting session: not handled.	Noted.
080202,2r	8.2	S1-141441	KPN	Modification of service requirements for isolated E-UTRAN	Revision of S1-141247	Agreed in drafting. Some parts of the proposal overlap with S1-141290. They have to be removed.	Revised to S1-141559
080603r	8.6	S1-141442	Huawei, China Mobile, Alcatel Lucent, Orange	Overview section for FMSS	Revision of S1-141040	Revised to S1-141351
080604r	8.6	S1-141443	NSN	Proposed FMSS Definitions and Overview	Revision of S1-141426	For drafting session.	Noted at drafting.
080605r	8.6	S1-141444	NSN	Correction to use case on network congestion	Revision of S1-141023	Agreed.
080766r	8.7	S1-141445	Orange	ECIP use case on calling party side – information blocked	Revision of S1-141044	The second change was removed.	Agreed.
999999	8.7.1	S1-141446	Not allocated.	Not allocated.
999999	8.7.1	S1-141447	Not allocated.	Not allocated.
999999	8.7.1	S1-141448	Not allocated.	Not allocated.
999999	8.7.1	S1-141449	Not allocated.	Not allocated.
999999	8.7.1	S1-141450	Not allocated.	Not allocated.
999999	8.7.1	S1-141451	Not allocated.	Not allocated.
999999	8.7.1	S1-141452	Not allocated.	Not allocated.
999999	8.7.1	S1-141453	Not allocated.	Not allocated.
999999	8.7.1	S1-141454	Not allocated.	Not allocated.
080607r	8.6	S1-141455	China Mobile, Huawei, Orange	Generic requirements on service steering	Revision of S1-141035	For drafting session.	Revised to S1-141352
080608r	8.6	S1-141456	Juniper Networks, Vodafone, Telecom Italia, NSN	Traffic Steering based on operator's policies or user subscription	Revision of S1-141256	For drafting session.	Revised to S1-141350
080610r	8.6	S1-141457	Huawei, China Mobile, Orange, Alcatel-Lucent	Traffic steering in MVNO scenario	Revision of S1-141033	For drafting session. Agreed in drafting.	Agreed.
080612r	8.6	S1-141458	NSN	Proposed FMSS use case on changing the Service Chain during the connection	Revision of S1-141037	For drafting session.	Revised to S1-141501
080614r	8.6	S1-141459	NSN	Proposed FMSS use case on adding capacity to the Network Service	Revision of S1-141039	For drafting session.	Withdrawn
080901r	8.9	S1-141460	Telefonica	Update to Section 1 (Scope)	22.852	0001r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141088	Agreed.
080902r	8.9	S1-141461	Telefonica	Update to Section 3 (Definitions, Symbols & Abbreviations)	22.852	0002r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141089	For drafting session. Agreed in drafting.	Agreed.
080903r	8.9	S1-141462	Telefonica	Update to Section 4.1.2 (What Constitutes a Shared RAN)	22.852	0003r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141090	Agreed.
080903r	8.9	S1-141463	Telefonica	Update to Section 4.2 (Scenario and use case 1)	22.852	0004r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141091	For drafting session. Agreed in drafting.	Agreed.
080904r	8.9	S1-141464	Telefonica	Update to Section 4.6 (Scenario and use case 5.a)	22.852	0005r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141092	Agreed.
080905r	8.9	S1-141465	Telefonica	Update to Section 4.9 (Scenario and use case 7)	22.852	0006r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141093	Agreed.
080907r	8.9	S1-141466	Telefonica	Add new Section 4.16 (Scenario and use case 14)	22.852	0008r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141095	For drafting session.	Revised to S1-141366
080909r	8.9	S1-141467	Telefonica	Add new Section 4.17 (Scenario and use case 15)	22.852	0009r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141096	For drafting session.	Revised to S1-141367
080910r	8.9	S1-141468	Telefonica	Update to Section 5 (Considerations)	22.852	0010r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141097	Agreed.
080911r	8.9	S1-141469	Telefonica	Update to Section 6 (Potential Requirements)	22.852	0011r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141098	For drafting session.	Revised to S1-141368
080912r	8.9	S1-141470	Telefonica	Update to Section 7 (Conclusion and recommendations)	22.852	0012r1	B	12.0.0	Rel-13	FS_GUSH	Revision of S1-141099	Revised to S1-141369
080619r	8.6	S1-141471	China Mobile, Huawei	FMSS Consolidated requirements	Revision of S1-141041	For drafting session.	Revised to S1-141348
080301r	8.3	S1-141472	Ericsson	Single IP address	Revision of S1-141127	Agreed.
080302r	8.3	S1-141473	Ericsson	Late provisioning of a selected MNO	Revision of S1-141124	G&D propose to check with CT6 if this is a suitable solution, since this was not the original intention. Ericsson and Nokia do not want to want to have this sent to other WGs as they see it as an excuse not to agree on this document. On Friday: The text was edited on-line to try to find an agreement. The chair reminded that the agreement reached earlier during the week was to make a fair comparison between the three different possible solutions: the network-based one, the device-based one, and the UICC-based one. Delegates should not use arguments such as what is being done in other committee (e.g. OMA, GSMA, etc.) to try to discard solutions from the beginning, or this exercise will never be conduced. The text was tried to be modified to tell things like “this text does not assume normative agreement on remote subscription management”. Sent to off-line drafting.	Revised to S1-141591
080303r	8.3	S1-141474	Ericsson	Change of selected MNO (technical solution part)	Revision of one part of S1-141125	For off-line discussions. To be modified in the same way as S1-141473.	Revised to S1-141592
080303,2r	8.3	S1-141475	Ericsson	Change of selected MNO (update of use case part)	Revision of another part of S1-141125	Withdrawn.
070406r	7.4	S1-141476	General Dynamics UK Ltd	Normative requirements for ongoing Isolated E-UTRAN operation	22.278	0206r1	B	12.4.0	Rel-13	IOPS	Revision of S1-141403	Agreed in drafting.	Revised to S1-141557
080408r	8.4	S1-141477	Orange	P-CR to TR 22.828 on Section 4 Potential Requirements	Revision of S1-141128	Agreed.
080409r	8.4	S1-141478	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, China Mobile, China Telecom, KPN, Acer	Revision of APN-AMBR Note & Add New Requirement	Revision of S1-141136	Agreed.
080410r	8.4	S1-141479	Intel; Interdigital; Samsung; Sony Mobile Communications; T-Mobile USA	Considerations on Security for CSIPTO	Revision of S1-141137	Agreed.
080502r	8.5	S1-141480	InterDigital, KPN	Proposed missing requirements for eICBD security use case	Revision of S1-141238. The following note has been added: Some of the requirements in this clause may duplicate requirements in other clauses	The document number in the header is wrong, but this is just a PCR, so this is OK for this time.	Agreed.
080504r	8.5	S1-141481	KPN, Interdigital	Corrections to IP connection establishment use cases	Revision of S1-141240. “MNO” is replaced by “HPLMN” and some other clarifications/corrections have been performed.	Agreed.
080507r	8.5	S1-141482	KPN, Interdigital	eICBD charging use case	Revision of S1-141244	Agreed.
080508r	8.5	S1-141483	KPN, Interdigital	Offloading IP connection between devices use case	Revision of S1-141376	Agreed.
080802r	8.8	S1-141484	Sprint	PWS multi-media broadcast areas	Revision of S1-141178	Agreed.
080801r	8.8	S1-141485	Qualcomm Incorporated	Initiation of multimedia broadcast supplemental to PWS	Revision of S1-141087	What is offered in terms of service has been clarified.	Agreed.
070409	7.4	S1-141486	NSN	Updated WID on Isolated E-UTRAN Operation for Public Safety (IOPS)	WID	The material is now proposed to be collected in a new spec.	The proposal for the new TS is in S1-141528. So SA will be proposed to approve either a set of CRs to 22.278 or a new dedicated spec on IOPS with the same technical content as the CRs.	Revised to S1-141529
080803r	8.8	S1-141487	Sprint	PWS multi-media linked messages	Revision of S1-141179	Agreed.
080804r	8.8	S1-141488	Sprint	Multi-media PWS capable UEs in a PLMN only broadcasting text PWS	Revision of S1-141196	Agreed.
070404r	7.4	S1-141489	French Ministry of Interior	Minimum set of services for an isolated E-UTRAN	Revision of S1-141056	For drafting session	Revised to S1-141289
060202r	6.2	S1-141490	Orange	Clarification on the use of codecs by the WebRTC IMS client	22.228	0203r1	F	12.6.0	Rel-12	IMS_WebRTC	Revision of S1-141129	There are changes over changes.	Revised to S1-141599
080805r	8.8	S1-141491	Sprint	Separated text and multi-media PWS messages	Revision of S1-141249	Agreed.
081003r	8.10	S1-141492	Sprint	Proposed TR Introduction	Revision of S1-141065	Agreed.
081005r	8.10	S1-141493	Sprint	User reporting spoofed call use case	Revision of S1-141250	Agreed.
081006r	8.10	S1-141494	Sprint	User reporting a call incorrectly identified as spoofed use case	Revision of S1-141251	Agreed.
081007r	8.10	S1-141495	Sprint	User retrieval of spoofed call history	Revision of S1-141252	Agreed.
080473	8.4	S1-141496	Editor (Intel)	Revised version for consolidated requirements	New version of S1-141142.	Agreed.
999999	8.4	S1-141497	Editor (Intel)	Considerations on IMS for CSIPTO	Revised to S1-141543
999999	7.1	S1-141498	Not allocated	Not allocated
999999	7.1	S1-141499	Not allocated	Not allocated
080611r	8.6	S1-141500	Huawei, China Mobile, Orange	Traffic steering based on QoS information	Revision of S1-141034	For drafting session. Agreed in drafting.	Agreed.
080612rr	8.6	S1-141501	NSN	Proposed FMSS use case on changing the Service Chain during the connection	Revision of S1-141458	Revised to S1-141548
080615r	8.6	S1-141502	ZTE Corporation	Use Case for Service Chain Status update	Revision of S1-141378	Agreed in drafting. In SA1, it was judged as maybe not in scope, since from the communications from 3GPP towards S/Gi-LAN might be in the scope but not the other way round.	Noted.
080619r	8.6	S1-141503	Huawei	Use case on traffic steering based on time and/or location	Revision of S1-141161	Agreed at drafting.	Agreed.
999999	8.6	S1-141504	Not allocated	Not allocated
999999	8.6	S1-141505	Not allocated	Not allocated
999999	8.6	S1-141506	Not allocated	Not allocated
999999	8.6	S1-141507	Not allocated	Not allocated
999999	8.6	S1-141508	Not allocated	Not allocated
080161rr	8.1	S1-141509	NTT DOCOMO, Qualcomm Incorporated	ACDC TR clean-up: use case 9, removing overlap with SCM.	Revision of S1-141338	Agreed.
070153	7.1	S1-141510	Editor	TR 22.853 on SEES	TR	CP in S1-141553.	Agreed to be sent for approval.
070299	7.2	S1-141511	Editor	TS 22.179	TS	Agreed as a basis for future contributions.
080165	8.1	S1-141512	Editor	TR 22.806 on ACDC	TR	CP in S1-141601.	Agreed to be sent for approval.
080201	8.2	S1-141513	Editor	TR 22.897 on IOPS	TR	CP in S1-141560.	Agreed to be sent for approval.
080399	8.3	S1-141514	Editor	TR 22.802 on MAPN	TR	As a result of the off-line discussions, the following plan is agreed: More information is needed on the 3 possible solutions, including the OMA DM one, for which an LS in S1-141534. Then the pros and cons of each solution will be established, as to prepare the field for a fair comparison to take place at the next meeting. Contributions are invited on this topic. Some editor’s notes will be added in the TR to reflect these intentions in the TR in S1-141535. This version includes all the inputs agreed at SA1#66.	Agreed as a basis for future contributions.
080478	8.4	S1-141515	Editor	TR 22.828 on CSIPTO	TR	CP in S1-141521.	Agreed to be sent for approval.
080509	8.5	S1-141516	Editor	TR 22.807 on eICBD	TR	CP in S1-141563	Agreed to be sent for information.
080697	8.6	S1-141517	Editor	TR 22.808 on FMSS	TR	CP in S1-141602	Revised to S1-141604
080753	8.7	S1-141518	Editor	TR 22.810 on ECIP	TR	Some inputs were un-intentionally not included.	Revised to S1-141593
080899	8.8	S1-141519	Editor	TR 22.815 on MBSP	TR	Agreed as a basis for future contributions.
081099	8.10	S1-141520	Editor	TR 22.898 on UC_SPOOF	TR	Agreed as a basis for future contributions.
080479	8.4	S1-141521	Editor	Cover page for CSIPTO 22.828	TR	TR in S1-141515.	Agreed.
070299	7.2	S1-141522	UK Home Office	MCPTT Group Definition	Noted without presentation.
050202r	5.2	S1-141523	NTT DOCOMO, et.al	WID proposal for Application specific Congestion control for Data Communication (ACDC)	WID	Revision of S1-141170	Agreed.
050207rr	5.2	S1-141524	Alcatel-Lucent	New WID for VoLTE Paging Distinction	WID	Revision of S1-141390	Revision marks to be approved.	Revised to S1-141573
070631,4r	5.2	S1-141525	Orange	Proposed new WID on SMS-outbox update on Mobile	WID	Revision of S1-141185	NSN wonder if this means that every phone will have to be updated and, if this is the case, by the time it will be widely deployed, the service might be completely outdated. Telefonica share this view. In total, 3 companies have concerns with approving this WID.	Noted.
050211rr	5.2	S1-141526	KDDI	Feasibility Study on Control of Applications when Third party Servers encounter difficulties	WID	Revision of S1-141397	One more supporting company.	Revised to S1-141579
040008,2rr	4	S1-141527	Huawei	Draft Reply to OMA Architecture Working Group (Cc SA2) about SEES work item	LS draft	Revision of S1-141383	Agreed.
070409,2	7.4	S1-141528	General Dynamics	Proposed new TS on FS_IOPS	TS	This is to collect the technical content of the CRs on 22.278 and replace them by a stand-alone spec.	No need to present it to SA at this stage.	Agreed as a basis for future contributions.
070409r	7.4	S1-141529	NSN	Updated WID on Isolated E-UTRAN Operation for Public Safety (IOPS)	WID	Revision of S1-141486	Since this was already approved at SA, revision marks are needed compared to the SA-approved version. A clean version has to be provided in the same zip file too.	Revised to S1-141558
040011,2r	4	S1-141530	UK HOME OFFICE	LS to OMA COM of the Open Mobile Alliance (cc SA, SA2) on MCPTT Requirements	LS draft	Revision of S1-141385	Revised to S1-141590
070301rr	7.3	S1-141531	Alcatel-Lucent, Huawei, Intel	Use case for end to end WebRTC bearer support over IMS	22.228	0197r2	B	12.6.0	Rel-13	eWebRTCi	Revision of S1-141430	Agreed.
070302rr	7.3	S1-141532	Alcatel-Lucent, Huawei, Intel	Support for end to end WebRTC bearer support over IMS	22.228	0198r2	B	12.6.0	Rel-13	eWebRTCi	Revision of S1-141431	Agreed.
080472	8.4	S1-141533	Intel	Removal of Use Case 2 and IMS requirements from the TR	Agreed.
080399,2	8.3	S1-141534	Vodafone	Proposed LS to OMA on OMA DM	LS draft	Revised to S1-141589
080399,4	8.3	S1-141535	G&D	Editor´s notes on TR 22.802	Proposed to be noted by the author. This can be useful for information to be provided at the next meeting.	Noted.
050208,2rr	5.2	S1-141536	III, ITRI	WID proposal: Long Range Cell Operation for Public Safety (LCOPS)	WID	Revision of S1-141396	Proposed to be noted by the authors.	Noted.
080306r	8.3	S1-141537	Alcatel-Lucent	Disadvantages of UICC based solution	Revision of S1-141193	Mistake in upload.	Revised to S1-141596
080305r	8.3	S1-141538	Alcatel-Lucent	Advantages of Device management based solution	Revision of S1-141192	Agreed.
050206r	5.2	S1-141539	Qualcomm Incorporated	Review of ProSe stage-1 fulfilment (TS 22.278)	Revision of S1-141389	The points in lines 41 to 44 on pages 2 need further checks. Motorola Solutions believes that the ProSe requirements for Public Safety have not been met in Rel-12 to the extent that are marked in green in this document.	Agreed.
070203r	7.2	S1-141540	UK Home Office	Background Document for Group Management in GCSE and MCPTT	Revision of S1-141191	Noted.
070206r	7.2	S1-141541	UK Home Office	7.2 MCPTT: Mission Critical Push to Talk over LTE	Revision of S1-141190	Revised to S1-141544
080607rrr	8.6	S1-141542	China Mobile, Huawei, Orange	Generic requirements on service steering	Revision of S1-141352	NSN has off-line comments to provide to China Mobile on the wording.	Revised to S1-141547
080471	8.4	S1-141543	Editor (Intel)	Considerations on IMS for CSIPTO	Revision of S1-141497	Agreed.
070202r	7.2	S1-141544	UK Home Office	Group Management for MCPTT	Revision of S1-141541	Agreed.
070155	7.1.1	S1-141545	Huawei	Consolidated SEES capabilities	Revision of S1-141286	Agreed.
070202rr	7.2	S1-141546	UK Home Office	Update of the terminology	UK Home Office propose to add definitions for all the newly introduced terms.	Withdrawn.
080607rrrr	8.6	S1-141547	China Mobile, Huawei, Orange	Generic requirements on service steering	Revision of S1-141542	Agreed.
080612rrr	8.6	S1-141548	NSN	Proposed FMSS use case on changing the Service Chain during the connection	Revision of S1-141501	Revised to S1-141554
080161rr	8.1	S1-141549	NTT DOCOMO, Qualcomm Incorporated	ACDC TR clean-up: use case 9, removing overlap with SCM.	Revision of S1-141338	Withdrawn.
080154rr	8.1	S1-141550	Qualcomm Incorporated	ACDC Background Information	Revision of S1-141339	Seen at drafting.	Agreed.
070103rrr	7.1	S1-141551	Huawei, KPN, China Mobile	Generic requirements on service/capability exposure towards third parties	Revision of S1-141284	Agreed.
070181r	7.1	S1-141552	KPN, Huawei, NEC, China Mobile	Proposed SEES conclusion	Revision of S1-141121	Agreed.
070153,2	7.1	S1-141553	Editor	Cover page for TR on SEES	TS in S1-141510 to be sent for approval.	Agreed.
080612rrrr	8.6	S1-141554	NSN	Proposed FMSS use case on changing the Service Chain during the connection	Revision of S1-141548	Agreed.
080761,2	8.7	S1-141555	Orange	ECIP use case on calling party side – Text call per call	Revision of S1-141045	For drafting group.	Agreed.
070403rr	7.4	S1-141556	General Dynamics UK Ltd	General, subscriber and service management normative requirements for Isolated E-UTRAN operation	22.278	0204r2	B	12.4.0	Rel-13	IOPS	Revision of S1-141434	Agreed.
070406rr	7.4	S1-141557	General Dynamics UK Ltd	Normative requirements for ongoing Isolated E-UTRAN operation	22.278	0206r2	B	12.4.0	Rel-13	IOPS	Revision of S1-141476	Agreed.
070409rr	7.4	S1-141558	NSN	Updated WID on Isolated E-UTRAN Operation for Public Safety (IOPS)	WID	Revision of S1-141529	Agreed.
080202,2rr	8.2	S1-141559	KPN	Modification of service requirements for isolated E-UTRAN	Revision of S1-141441	Agreed.
080202	8.2	S1-141560	Editor	Cover page for the TR 22.897 on IOPS	TR	TR in S1-141513.	Agreed.
080413r	8.4	S1-141561	Intel	Proposed conclusion section for TR 22.828	Revision of S1-141140	Agreed.
050210,2rr	5.2	S1-141562	China Unicom	Study on Enhancements to User Location Reporting Support	WID	Revision of S1-141379	Rev marks to be accepted.	Revised to S1-141577
080509	8.5	S1-141563	Editor (KPN)	Cover page for EICBD TR	TR	TR in S1-141516.	Agreed.
080697,2	8.6	S1-141564	Editor	Cover page for the TR 22.808 on FMSS	TR in S1-141517. There should be outstanding issues since this is just presented for information: the consolidation of the requirements is e.g. missing, as well as potentially more use cases, etc.	Revised to S1-141602
050203s	5.2	S1-141565	NTT DOCOMO, Qualcomm Incorporated	Proposed Text for ACDC Consolidated Requirements	There are some inaccuracies on the PCR numbers.	Revised to S1-141582
050204rrr	5.2	S1-141566	Intel, Samsung, Interdigital, Sony Mobile Communications, T-Mobile USA, Acer, China Mobile, China Telecom, KPN	Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO)	WID	Revision of S1-141301	Agreed.
080619r	8.6	S1-141567	Huawei	Use case on traffic steering based on APN	Revision of S1-141160	Agreed.
090231	9.2	S1-141568	Rapporteur	Status update for CSIPTO	SU	This a new WI. Work/Study Item Completion: 0% CR to TS22.101 Completion: 0% Target completion date in WID: 09/2014 SP#65 Current target completion date: 09/2014 SP#65 Will target completion date be met? Yes If not, change target completion date to: Expected date to send CR to TS 22.101 to SA plenary: For agreement: SA#67 (08/2014) For approval: SP#65 (09/2014)	“approved” to be changed to “agreed”	Approved with this change.
050205rr	5.2	S1-141569	Qualcomm Incorporated	New WID for ProSe Maintenance (ProSeM)	WID	Revision of S1-141394	Agreed.
090232	9.2	S1-141570	Rapporteur (Qualcomm)	Status update for ProSe Maintenance	SU	This a new WI. Work/Study Item Completion: 30% Target completion date in WID: 09/2014 SP#65	Approved.
050206rr	5.2	S1-141571	Rapporteur (NSN)	Rel-13 Maintenance WI for Group Communication System Enablers for LTE	Revision of S1-141395	Agreed.
090233	9.2	S1-141572	Rapporteur (NSN)	Status update for maintenance for GCSE_LTE	SU	This a new WI. Work/Study Item Completion: 0% Target completion date in WID: 09/2014 SP#65	Approved.
050207rrr	5.2	S1-141573	Alcatel-Lucent	New WID for VoLTE Paging Distinction	WID	Revision of S1-141524	Agreed.
090234	9.2	S1-141574	Rapporteur (Alcatel-Lucent)	Status update for VoLTE Paging Distinction	SU	Is this a new WI? Y Work/Study Item Completion: 100% Target completion date in WID: 06/2014 SP#64	Approved.
050207,2rr	5.2	S1-141575	Alcatel-Lucent, Verizon, Oracle	Requirements to support differentiated paging for VoLTE	22.228	0199r2	B	12.6.0	Rel-13	VoLTE_PPD	Revision of S1-141391	Agreed.
050207,4rr	5.2	S1-141576	Alcatel-Lucent, Verizon, Oracle	EPS Requirement to support differentiated paging for VoLTE	22.278	0201r2	B	12.4.0	Rel-13	VoLTE_PPD	Revision of S1-141392	Agreed.
050210,2rrr	5.2	S1-141577	China Unicom	Study on Enhancements to User Location Reporting Support	WID	Revision of S1-141562	Agreed.
090235	9.2	S1-141578	Rapporteur (China Unicom)	Status update for Study on Enhancements to User Location Reporting Support	SU	Is this a new WI? Yes Study Item Completion: 0% Target completion date in WID: <06/2015> SP#68	Approved.
050211rrr	5.2	S1-141579	KDDI	Feasibility Study on Control of Applications when Third party Servers encounter difficulties	WID	Revision of S1-141526	Agreed.
090236	9.2	S1-141580	Rapporteur (KDDI)	Status update for Study on Control of Applications when Third party Servers encounter difficulties	SU	Is this a new WI? Yes Work/Study Item Completion: 0% Draft TR 22.8xy Completion: 0% Target completion date in WID: <12/2014> SP#66	Approved.
090221	9.2	S1-141581	Rapporteur (NTT DOCOMO)	Status update for WID proposal for Application specific Congestion control for Data Communication (ACDC)	SU	This a new WI. Work Item Completion: 90% Target completion date in WID: 09/2014 SP#65 Is current completion date the same as above? y Will target completion date be met? Y	Approved.
050203sr	5.2	S1-141582	NTT DOCOMO, Qualcomm Incorporated	Proposed Text for ACDC Consolidated Requirements	Revision of S1-141565	Agreed.
080619rr	8.6	S1-141583	ZTE, China Mobile, China Telecom, China Unicom, CATT	Use Case for Flexible Mobile Service Steering -- Service Chain Bootstrapping and Auto Re-configuration	Revision of S1-141345	This needs further refinements in NEC’s opinion, so ZTE is encouraged to contact NEC between now and next meeting.	Noted.
070273r	7.2	S1-141584	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for Emergency Alert	Revision of S1-141084	Agreed.
070279r	7.2.1	S1-141585	Motorola Solutions	Add definition of “participant type” to 3.1	Revision of S1-141313	Agreed.
070220rrr	7.2	S1-141586	Alcatel-Lucent	EPS priority management	Revision of S1-141314	Agreed.
070270rr	7.2	S1-141587	Harris Corporation, Motorola Solutions Inc., US Department of Commerce	Requirements for interworking with Project 25	Revision of S1-141319	Agreed.
090217	9.2	S1-141588	Rapporteur (Telefonica)	FS_GUSH status update	SU	Revision of S1-141276. This WI has been approved at SP#63 Approved WID is in tdoc SP-140339 Work/Study Item Completion: 80% Draft TR 22.852 Completion: 80% Target completion date in WID: 09/2014 SP#65 Is current completion date the same as above? y Will target completion date be met? y Expected date to send TR to SA plenary: For information: SA1#66 (05/2014) For approval: SA1#67 (08/2014)	Approved.
080399,2r	8.3	S1-141589	Vodafone	Proposed LS to OMA DM Group on options of usage of OMA DM for APN configuration	LS draft	Revision of S1-141534. This is to ask OMA DM group whether device management solutions as defined by OMA (e.g. OMA DM, OMA CP and OMA lightweight M2M) are suitable for use to automatically configure a device with all its device settings including conMO which containing the APN to be used per application.	For Ericsson, this is drafted in such a way that the answer will be “This is not suitable”. For Qualcomm, SA1 is just asking OMA to read their standards to SA1.	Revised to S1-141594
040011,2rr	4	S1-141590	UK HOME OFFICE	LS to OMA COM of the Open Mobile Alliance (cc SA, SA2) on MCPTT Requirements	LS draft	Revision of S1-141530	MCC to add the July ad-hoc in “future meetings”	Agreed.
080302rr	8.3	S1-141591	Ericsson	Network based solution for operator swap use-case	Revision of S1-141473	The text has been aligned to the differences between S1-141592 and S1-141595.	Revised to S1-141598
080303rr	8.3	S1-141592	Ericsson	Network based solution for the in-vehicle user equipment	Revision of S1-141474. The text on subscription management has been removed, a statement is added to tell that “Note, this text is not endorsing remote subscription management”.	The note can be removed since the text has been modified. Or the other way round: the note is kept and “the embedded UICC” is reintroduced.	Revised to S1-141595
080753r	8.7	S1-141593	Editor	TR 22.810 on ECIP	TR	Revision of S1-141518	CP in S1-141603.	Agreed to be presented for information.
080399,2rr	8.3	S1-141594	SA1	LS to OMA DM Group on options of usage of OMA DM for APN configuration	LS out	Revision of S1-141589	Approved.
080303rrr	8.3	S1-141595	Ericsson	Network based solution for the in-vehicle user equipment	Revision of S1-141592	Agreed.
080306rr	8.3	S1-141596	Alcatel-Lucent	Characteristics of UICC based solution	Revision of S1-141537	“APN” to be changed in “multiple APN” in the first added sentence.	Revised to S1-141597
080306rrr	8.3	S1-141597	Alcatel-Lucent	Characteristics of UICC based solution	Revision of S1-141596	Agreed.
080302rrr	8.3	S1-141598	Ericsson	Network based solution for operator swap use-case	Revision of S1-141591	Agreed.
060202rr	6.2	S1-141599	Orange	Clarification on the use of codecs by the WebRTC IMS client	22.228	0203r2	F	12.6.0	Rel-12	IMS_WebRTC	Revision of S1-141490	Agreed.
060197	6.1	S1-141600	Rapporteur (Alcatel-Lucent)	cover sheet for 22.519 to SA for information.	TR in S1-141319.	Agreed.
080166r	7.1	S1-141601	FS_ACDC Rapporteur	Proposed cover sheet for FS_ACDC TR	Revision of S1-141305	Agreed.
080697,2r	8.6	S1-141602	Editor	Cover page for TR 22.808 on FMSS	Revision of S1-141564	TR in S1-141517.	Revised to S1-141605
080795r	8.7	S1-141603	Rapporteur	Cover page for TR22.810 on ECIP WID	Revision of S1-141307	TR in S1-141593.	Agreed.
080697r	8.6	S1-141604	Editor	TR 22.808 on FMSS	TR	Revision of S1-141517	Agreed to be sent to SA.
080697,2rr	8.6	S1-141605	Editor	Cover page for TR 22.808 on FMSS	Revision of S1-141602	Agreed.

Proposed dates for ad-hoc for MCPTT and GCSE: 15, 16 and 17 July. “full power” for everything related to MCPTT and GCSE: agree CR, reply to LSs, etc.