3GPP TSG-SA WG1 Meeting #71bis ad-hoc on FS_SMARTER	S1-15xxxx

Vancouver, Canada, 19-21 October 2015

Draft Minutes of

3GPP TSG SA WG1
Meeting #71bis ad-hoc on FS_SMARTER

Vancouver, Canada

19th - 21st October 2015

Chairman:	Toon Norp, KPN

Meeting Secretary:	Alain Sultan, ETSI/MCC

Contents

1	Opening of the meeting	3

1.1	Agenda and scheduling	3

1.2	IPR, antitrust and competition laws	3

1.3	Information for delegates	3

1.4	Information for rapporteurs	4

1.5	Working agreements	4

2	Reports and action items	4

3	FS Smarter: New Services and Markets Technology Enablers [SP-150142]	4

3.1	Grouping of use cases	4

3.2	New Building Block Study Item Descriptions	6

3.3	Outline / structure for the new Building Block TRs	9

3.4	Updates of existing use cases	11

3.4a	New use cases / Update of existing use cases related to credentials / identifiers	15

3.5	New use cases	18

3.6	Other contributions to TR 22.891 (e.g. editorials)	21

4	Work planning contributions	22

4.1	FS_SMARTER status update	22

5	Next meetings	22

5.1	Calendar	22

6	Any other business	22

7	Close	23

Annex 1: TDoc list	24

Annex 1.1: TDocs not appearing in the minutes	30

Annex 2: Void	32

Annex 3: Void	32

Annex 4: Agreed WIDs	32

Annex 5: New versions of Draft TSs/TRs and cover pages	32

Annex 6: Participants list	32

For the hyperlinks to work:

1) unzip this document and place the .doc file in a given folder (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.

1	Opening of the meeting

The SA1 meeting #71bis ad-hoc on FS_SMARTER took place from the 19th till the 21st of October 2015 at the Marriott Hotel in Vancouver, BC, Canada.

This meeting is an ad-hoc meeting, i.e. the attendance (or lack of it) is not accounted for voting rights. It was delegated decision power by SA1 on all FS_SMARTER issues.

The SA1 chair, Mr. Toon Norp (KPN), opened the meeting on Monday 19th of October at 9 AM local time.

He welcomed all the delegates and wished them a fruitful meeting.

He then gave the floor to Mr. Mark Younge, who in turn welcomed all the participants, in the name of the European Friends of 3GPP, the hosting consortium. Mr. Younge also gave some practical information about the meeting arrangements and the area.

1.1	Agenda and scheduling

S1-153000 from Chairman: Draft Agenda

Conclusion: Revised to S1-153001.

S1-153001 from Chairman: 2nd draft agenda

Conclusion: Revised to S1-153002.

S1-153002 from Chairman: 3rd Draft Agenda

Discussion: Agenda item "3.6 Other" added to Q.3 on Tuesday.

Conclusion: Noted.

1.2	IPR, antitrust and competition laws

Mr. Toon Norp reminded the delegates of their company's obligations under their SDO's IPR policies:

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

The delegates were asked to take note that they were thereby invited:

-	to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP.

-	to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Statement and the Licensing declaration forms (http://webapp.etsi.org/Ipr/).

Then delegates were also reminded of the antitrust and competition law policies:

"The attention of the delegates to the meeting was drawn to the fact that 3GPP activities were subject to antitrust and competition laws and that compliance with said laws was therefore required by any participant of the meeting, including the Chairman and Vice-Chairmen and were invited to seek any clarification needed with their legal counsel. The present meeting would be conducted with strict impartiality and in the interests of 3GPP. Delegates were reminded that timely submission of work items in advance of TSG/WG meetings was important to allow for full and fair consideration of such matters."

1.3	Information for delegates

A guide for SA1 new-coming delegates is available at http://www.3gpp.org/SA1-delegates-survival-guide

It was reminded that the delegates are encouraged to send draft TR/TS for information as soon as there is useful content to be reviewed. Draft TR/TS can be sent to SA plenary for information more than once.

This guide will however have to be slightly updated to take into account the new procedures in 3GPP, namely the progressive introduction of the "3GPP Ultimate" (3GU) platform and set of web tools.

1.4	Information for rapporteurs

"Beginner's guide" for writing a new TS/TR is available at http://www.3gpp.org/specifications-groups/delegates-corner/writing-a-new-spec (feedback on content is welcome!)

For detailed drafting guidelines, please see TR 21.801

The Rapporteur is expected to produce a work item/study item status report for the end of the meeting under agenda item 9.2. The template is available here.

For draft TR/TS, the Rapporteur is expected to update the draft TR/TS with all contributions agreed at the meeting before the meeting is closed.

1.5	Working agreements

There was no contribution for this agenda item.

2	Reports and action items

S1-153004 from chairman: Report for SA1 from SA plenary and RAN 5G WS

Discussion: SA1 results were approved. One WID was revised.

The following Rel-14 planning was agreed by SA:

- Target date Stage 1: March 2016

- Target date Stage 2: September 2016

- Target date Stage 3: March 2017.

There was also a RAN 5G Workshop concluding on possible timeline for Rel-15 and Rel-16.

Conclusion: Noted.

3	FS Smarter: New Services and Markets Technology Enablers [SP-150142]

3.1	Grouping of use cases

S1-153099 from HUAWEI TECHNOLOGIES Co. Ltd.: Discuss grouping of SMARTER requirements

Revision of S1-153040.

The use cases are grouped in 4 groups: eMobile Broadband (eMBB), Critical Communication (CC), V2X, and mMTC. The requirements for each one of these groups are proposed.

Also, a comparison of companies grouping proposals is done.

Discussion: For Nokia and Vodafone, this is very useful. However, for these 2 companies, V2X new specific topics should be integrated in the other categories, knowing that V2X is already part of Rel-14. Huawei has no concern about this.

The Rapporteur asked if this will lead to different TRs, one per type of use cases, or if all the use cases are going to be grouped in one single TR.

For Alcatel-Lucent, what is important to see is what types of requirements are added by the use cases (and this should be the object of classification) rather than the use cases themselves. Cisco support this view.

For Huawei, the work should now focus on the requirements rather than bringing new use cases.

Telefonica and the Chair reminded that what is important is to provide a work that would benefit to the "final

Customer"'s needs, in particular RAN WG groups and SA2.

All "grouping" documents to be concluded together.

Conclusion: Revised to S1-153109 as to put the overview table in 22.891.

S1-153109 from HUAWEI TECHNOLOGIES Co. Ltd.: Discuss grouping of SMARTER requirements

Revision of S1-153099

Discussion: This needs further work, e.g. group names alignment, "no latency" to be changed to something more accurate, etc.

Conclusion: Revised to S1-153169

S1-153169 from HUAWEI TECHNOLOGIES Co. Ltd.: Discuss grouping of SMARTER requirements

Revision of S1-153109

Conclusion: Revised to S1-153201

S1-153201 from HUAWEI TECHNOLOGIES Co. Ltd.: Discuss grouping of SMARTER requirements

Revision of S1-153169

Conclusion: Agreed.

S1-153041 from Nokia Networks Oy: Use case categorisation (rev of S1-152210)

This document proposes a categorisation of existing FS_SMARTER use cases in TR 22.891. This is an update of S1-152210, not presented at SA1#71 due to lack of time.

The following categories are proposed: Mobile broadband, Reliable communications, "Machine-to-machine and sensors", Network operation, Routing, Access and "Migration and interworking".

Discussion: "network coverage" could be into "access".

For the Rapporteur, this approach with a single list is easier to handle than a matrix approach.

Aspects such as security are agreed to be important. They are not listed here because they apply everywhere, though.

Conclusion: Revised to S1-153110 as to put the mapping of use cases to groups in 22.891.

S1-153110 from Nokia Networks Oy: Use case categorisation (rev of S1-152210)

Revision of S1-153041.

This document proposes a categorisation of existing FS_SMARTER use cases in TR 22.891 v1.0.0.

Discussion: See also S1-153112 on grouping.

Conclusion: Noted, to be considered when revising S1-153112.

S1-153014 from VODAFONE Group Plc: SMARTER Use Cases Grouping

This document proposes the criteria for use case grouping, and the identified Use Case Groups based on these criteria are also provided for further discussion.

These categories are "Enhanced mobile broadband", "Critical machine communications" and "Massive Machine Type Communications (Internet of things)", "Network operation" et "Migration and interworking".

Discussion: For Alcatel-Lucent, only 4 groups might be too reduced and might ",ask" some requirements.

Conclusion: Noted.

S1-153015 from VODAFONE Group Plc: SMARTER Building Block enhanced Mobile BroadBand

This presentation proposes to start a new building block study item for the identified use case group: enhanced Mobile BroadBand (eMBB).

A proposal is made to tell which use cases should go in this category.

Discussion: There is no disagreement with this idea.

Conclusion: Noted.

S1-153016 from VODAFONE Group Plc: SMARTER Building Block Critical Machine Communications

This presentation is to start the new building block on study item for the identified use case group: Critical Machine Communications (CMC).

Discussion: There is no disagreement with this idea.

Conclusion: Noted.

S1-153069 from TTA: Critical Communications in the 5G

This document describes the potential application of 5G services for critical communications in the 5G world.

Conclusion: All "grouping" documents to be concluded together.

S1-153017 from VODAFONE Group Plc: SMARTER Building Block massive IOT

This presentation is to start the new building block study item for the identified use case group: massive Internet of Things (mIoT).

Discussion: There is no disagreement with this idea.

Conclusion: Noted.

S1-153018 from VODAFONE Group Plc: SMARTER Building Block Network operation

This is the last presentation in this set of 4, and this one is to start a new building block study item for the identified use case group: Network Operation.

Discussion: There is no disagreement with this idea.

Conclusion: Noted.

S1-153035 from Alcatel-Lucent : FS_SMARTER considerations on grouping use cases

This document also proposes a potential grouping of use cases.

Discussion: This grouping is more detailed than several other proposals.

Nokia reminded that Phase 1 was supposed to focus on a very limited number of use cases but now, all the grouping proposals are based on all the existing use cases, leaving nothing for Phase 2. So the approach has to be clarified again.

With such a detailed proposal, the Chair asked if the author's intention is to produce 11 TRs, one per group. Alcatel-Lucent replied that this is where a limitation of the use cases for phase 1 might be useful to reduce the number of groups and TRs.

The Chair clarified that, if prioritization is to be made, then this leads to a full new area of work. This also needs to be done in consultation with SA2 and RAN.

For Alcatel-Lucent, this is also the role of SA1 to clarify what the operators want as a priority and then the other groups have to follow. Telefónica support this view.

For LG, after the grouping, the next task of SA1 would be to select some use cases, to make a first filter so that the other groups can progress efficiently.

Conclusion: Noted.

S1-153058 from LG Electronics France: Discussion on grouping SMARTER use cases

It is proposed to generate a separate BB on High Mobility and Vehicular Communications (HiV2X). Some of the existing use cases are identified to be part of this HiV2X BB.

Discussion: So this could be seen as the only topic so far in SMARTER Phase 2.So LTE-based V2X will be in Rel-14 and 5G-based V2X (HiV2X) can be for SMARTER Phase 2.

SA1 conclude that the working assumption is that the 5G-specific enhancements for V2X will be handled as part of Rel-15, hence it is out of FS_SMARTER.

Conclusion: Noted.

S1-153036 from Alcatel-Lucent : FS_SMARTER considerations on requirements grouping

This document proposes groups of requirements in alignment with the use case groupings proposed in S1-153035.

Discussion: Some analogies are found with Huawei's document S1-153099.

For T-Mobile, the purpose of these tables is unclear: it is explained by the Rapporteur that these tables are proposed to collect the results of 22.891 (not yet the conclusion).

For Cisco and T-Mobile, drafting these tables will be too time-consuming compared to the benefit they will bring.

A merging of Huawei's, Nokia's and this document can be done.

The concept of grouping the use cases into "families" is supported and will be the subject of a dedicated new contribution in S1-153112.

Conclusion: Revised to S1-153111 to change the tables into text.

S1-153111 from Alcatel-Lucent : FS_SMARTER considerations on requirements grouping

Revision of S1-153036.

The empty tables have been removed and only the clarifying text on "Considerations on grouping of potential requirements" is kept.

Discussion: Further minor corrections needed (add an "overview" section, remove "primary").

Conclusion: Revised to S1-153170

S1-153170 from Alcatel-Lucent : FS_SMARTER considerations on requirements grouping

Revision of S1-153111

Conclusion: Agreed.

S1-153077 from QUALCOMM Incorporated: SMARTER: Use Case Categorization

This paper provides a comparison between the draft TR22.891 use case categorization proposed by the Rapporteur (Vodafone) and one proposed by Qualcomm. This document is presented for consideration for incorporation into the agreed set of use case grouping.

Conclusion: To be handled with other document.

S1-153112 from Vodafone/Rapporteur: Grouping of use cases into families

Discussion: Other inputs to be considered too.

Conclusion: Revised to S1-153154

S1-153154 from Vodafone/Rapporteur: Grouping of use cases into families

Revision of S1-153112.

This takes into account Nokia's contribution, in particular for the name of the groups.

Discussion: Some inconsistencies in the use of acronyms (e.g. "CC" or "CriC").

Conclusion: Revised to S1-153171

S1-153171 from Vodafone/Rapporteur: Grouping of use cases into families

Revision of S1-153154

Conclusion: Agreed.

3.2	New Building Block Study Item Descriptions

S1-153019 from VODAFONE Group Plc: Study on New Services and Markets Technology Enablers - massive Internet Of Things

The objective of this study is to identify and document the key families of use cases and their consolidated potential requirements and to capture desired system requirements and capabilities to enable 3GPP network operators to support the needs of new services and markets related to massive Internet of Things.

Discussion: There are different aspects that need to be further discussed (security, charging, timeline, etc) but this can be done in a later phase.

For Morpheo, the security of the user equipments should not be impacted by this work item. For Telefónica, different types of mobiles will have different security requirements. Vodafone understands well the problem that a security weaker link should not be introduced in the overall system because of this study. This will be clarified in a new version of the study.

The concept of "family" of use case is to be introduced.

The name is to be reconsidered (e.g. "Internet of Everything").

Conclusion: Revised to S1-153114

S1-153043 from Nokia Networks Oy: Study on SMARTER Reliable Communications

Proposed WID on Reliable Communications.

The objective of this study is to develop use cases and identify potential service and operational requirements to enable 3GPP network operators to support Reliable Communications, e.g. for industry automation, tactile Internet and haptic control, etc.

Discussion: Telia Sonera support this Work Item.

"critical communication" would be a better name, for Vodafone and Telia Sonera.

This new timeline is proposed: presentation in March and approval in June. This timeline will be followed by all the new SA1 WID.

More companies are supporting.

Security and charging sections have to be updated.

The family concept has to introduced.

Conclusion: Revised to S1-153115

S1-153114 from VODAFONE Group Plc: Study on New Services and Markets Technology Enablers - massive Internet Of Things

Revision of S1-153019

Discussion: Orange is supporting too.

Morpho and Oberthur reminded that the security and charging aspects should be covered under the WID "Network Operation" and not under this WID.

Vodafone clarified that they just put a basic text in this WID, which is commonly used in many WIDs, so it doesn't preclude any further organisation of the work.

For Cisco and Intel, this present wording ("Charging/Security aspects will be considered in this study.") are acceptable too.

Another generic sentence will be proposed instead for the Security (the one for Charging is acceptable as such)

This sentence is: "Security aspects to mIOT will be considered in this study, however general aspects for 5G will be covered in the Network Operation WID". A similar sentence has to be put for all the other WIDs.

Conclusion: Revised to S1-153172

S1-153115 from Nokia Networks Oy: Study on SMARTER Reliable Communications

Revision of S1-153043.

The wording of the Objective is now:

The objective of this study is to develop use cases and identify potential service and operational requirements to enable 3GPP network operators to support Critical Communications. The following use case families have been identified in TR 22.891 in the area of Critical Communications:

- Higher reliability and lower latency

- Higher reliability, higher availability and lower latency

- Very low latency

- Higher accuracy positioning

Discussion: One typo.

Conclusion: Revised to S1-153173

S1-153172 from VODAFONE Group Plc: Study on New Services and Markets Technology Enablers - massive Internet Of Things

Revision of S1-153114

Discussion: China Unicom is also supporting.

Conclusion: Revised to S1-153184

S1-153173 from Nokia Networks Oy: Study on SMARTER Reliable Communications

Revision of S1-153115

Discussion: Other supporting companies added.

Conclusion: Revised to S1-153205

S1-153184 from VODAFONE Group Plc: Study on New Services and Markets Technology Enablers - massive Internet Of Things

Revision of S1-153172

Discussion: Other supporting companies added.

Conclusion: Revised to S1-153204

S1-153205 from Nokia Networks Oy: Study on SMARTER Reliable Communications

Revision of S1-153173

Conclusion: Agreed.

S1-153204 from VODAFONE Group Plc: Study on New Services and Markets Technology Enablers - massive Internet Of Things

Revision of S1-153184

Conclusion: Agreed.

S1-153059 from LG Electronics France: Study on New Services and Markets Technology Enablers - enhanced Mobile BroadBand

SID proposal for eMBB Building Block

Discussion: It was agreed off-line to merge it with another document.

Conclusion: Noted, to be merged with Huawei's document.

S1-153091 from HUAWEI TECHNOLOGIES Co. Ltd.: Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband

The objective of this study is to develop use cases and identify the related consolidated potential requirements to enable 3GPP network operators to support enhanced Mobile Broadband (eMBB) services.

Discussion: The time scale needs to be aligned to the one in S1-153043.

Same other comments on security and charging.

The concept of key family is to be introduced.

Merged with S1-153059.

Other companies are invited to co-sign.

Conclusion: Revised to S1-153116

S1-153116 from HUAWEI TECHNOLOGIES Co. Ltd., LG: Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband

Revision of S1-153091.

This is for the TR on enhanced Mobile Broadband (eMBB) scenarios.

Discussion: The sentence on Security has to be introduced.

Intel wondered why "Mobility on demand" is not listed anymore. It is explained to be covered elsewhere.

"22.xxx" is too vague: it should be replaced by "22.7xx" (or "22.8xx" which is the same, but they are different to "22.9xx", which would indicate that the TR is for publication).

Conclusion: Revised to S1-153174

S1-153174 from HUAWEI TECHNOLOGIES Co. Ltd., LG: Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband

Revision of S1-153116

Discussion: Supporting companies after agreement.

Conclusion: Revised to S1-153198

S1-153198 from HUAWEI TECHNOLOGIES Co. Ltd., LG: Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband

Revision of S1-153174

Conclusion: Agreed.

S1-153113 from LG Electronics France: Study on New Services and Markets Technology Enablers - High Mobility and Vehicular Services (HiV2X)

Revision of S1-153102

Conclusion: Withdrawn.

S1-153066 from China Mobile Com. Corporation: Study on New Services and Markets Technology Enablers - Network operation

The objective of this study is to identify and document the key families of use cases and their consolidated potential requirements and to capture desired system requirements and capabilities to enable 3GPP network operators to support the needs of new services and markets related to network operation.

Discussion: Supporting companies invited.

Timeline to be adjusted.

Conclusion: Revised to S1-153117

S1-153117 from China Mobile Com. Corporation: Study on New Services and Markets Technology Enablers - Network operation

Revision of S1-153066

Discussion: Changes to be accepted, same comment on TR number, the "?" on the supporting companies have to be cleaned up.

Conclusion: Revised to S1-153176

S1-153176 from China Mobile Com. Corporation: Study on New Services and Markets Technology Enablers - Network operation

Revision of S1-153117

Discussion: More supporting company.

Conclusion: Revised to S1-153183

S1-153183 from China Mobile Com. Corporation: Study on New Services and Markets Technology Enablers - Network operation

Revision of S1-153176

Discussion: Other supporting companies added.

Conclusion: Revised to S1-153203

S1-153203 from China Mobile Com. Corporation: Study on New Services and Markets Technology Enablers - Network operation

Revision of S1-153183

Conclusion: Agreed.

3.3	Outline / structure for the new Building Block TRs

S1-153042 from Nokia Networks Oy: Proposed structure for the dedicated TRs

Proposed structure for the dedicated TRs, and thoughts about the process.

SA1 is about to move from TR 22.891 to BB studies and TRs, each covering a subset of use cases in TR 22.891. As the final step in Phase 1 of FS_SMARTER is to consolidate the findings recorded in the BB TRs, it is important that the TRs share a common structure.

Discussion: The proposal in S1-153096 has to be merged with this one.

Conclusion: Revised to S1-153118

S1-153118 from Nokia Networks Oy: Proposed structure for the dedicated TRs

Revision of S1-153042

Discussion: Some off-line comments were forgotten.

Conclusion: Revised to S1-153178

S1-153178 from Nokia Networks Oy: Proposed structure for the dedicated TRs

Revision of S1-153118

Discussion: This does not propose actual text but a structure, which is agreed.

Conclusion: Agreed.

S1-153096 from KPN: Proposed structure for FS_SMARTER Building Block TRs

This paper proposes a general structure for the FS_SMARTER Building Block TRs. Main principle is to start with a description of the main use cases (e.g. eMBB, CC, mIoT). In subsequent sections, traffic scenarios are separated from detailed functional use cases.

Conclusion: Merged with S1-153042 in S1-153118.

S1-153020 from VODAFONE Group Plc: TR Skeleton mIOT

This is a skeleton for the new TR on Feasibility Study on New Services and Markets Technology Enablers for Massive Internet of Things.

Discussion: The template used in S1-153042 is to be used instead.

Conclusion: Revised to S1-153119

S1-153119 from VODAFONE Group Plc: TR Skeleton mIOT

Revision of S1-153020

Conclusion: Revised to S1-153177

S1-153177 from VODAFONE Group Plc: TR Skeleton mIOT

Revision of S1-153119

Conclusion: Agreed. Newer version in S1-153188.

S1-153021 from VODAFONE Group Plc: Introduction and Scope for mIOT TR

A scope and an overview are proposed for the new TR introduced in S1-153020.

The Scope clarifies that this TR aims to identify and document the key families of use cases and their consolidated potential requirements, and to capture desired system requirements and capabilities to enable 3GPP network operators to support the needs of new services and markets related to massive Internet of Things.

The focus of this work is on the use cases and requirements that cannot be met with EPS; consequently the extension of Rel-13 TSG RAN work and/or the existing SA work may be required.

Conclusion: Revised to S1-153120

S1-153120 from VODAFONE Group Plc: Introduction and Scope for mIOT TR

Revision of S1-153021

Discussion: There are some more "cost" to be replaced in this document.

Some other rewording needed.

Conclusion: Revised to S1-153187

S1-153187 from VODAFONE Group Plc: Introduction and Scope for mIOT TR

Revision of S1-153120

Conclusion: Agreed.

S1-153060 from LG Electronics France: TR Skeleton eMBB

TR skeleton for eMBB Building Block

Discussion: There is another proposal for the TR skeleton in S1-153092. The 2 proposals have to be merged and to follow the new template.

Conclusion: Revised to S1-153121

S1-153121 from LG Electronics France, Huwaei: TR Skeleton eMBB

Revision of S1-153060 and S1-153092

Conclusion: Revised to S1-153180

S1-153180 from LG Electronics France, Huwaei: TR Skeleton Enhanced Mobile Broadband (eMBB)

Revision of S1-153121

Conclusion: Noted. Final version in S1-153189.

S1-153092 from HUAWEI TECHNOLOGIES Co. Ltd.: Introduction and Scope for eMBB

This proposes a skeleton, introduction and scope for the new TR.

Discussion: It has to be merged with S1-153060.

Conclusion: Merged with S1-153060 in S1-153121

S1-153061 from LG Electronics France: Introduction and Scope for eMBB TR

Proposal for initial input for the eMBB Building Block TR based on the SMARTER phase-1 TR

Conclusion: Also merged in S1-153121 with S1-153060 and S1-153092.

S1-153064 from LG Electronics France: TR Skeleton HiV2X

Proposed TR skeleton for "High mobility and vehicular use cases" under SMARTER

Discussion: It has been decided earlier during this meeting not to start work on HiV2X at this stage.

This discussion will resume in March, when the timing will be more known.

Conclusion: Withdrawn.

S1-153067 from China Mobile Com. Corporation: TR Skeleton NO

This is a proposed skeleton for the TR on Feasibility Study on New Services and Markets Technology Enablers for Network Operation.

Discussion: It is in line with the Vodafone proposal. It also has to be updated to take into account the new proposals for skeletons in S1-153118.

Conclusion: Revised to S1-153124

S1-153124 from China Mobile Com. Corporation: TR Skeleton NO

Revision of S1-153067

Conclusion: Revised to S1-153181

S1-153181 from China Mobile Com. Corporation: TR Skeleton NO

Revision of S1-153124

Conclusion: Noted. Final version in S1-153190.

S1-153068 from China Mobile Com. Corporation: Introduction and Scope for NO TR

This text is also taken from the Study Item description.

Discussion: It also has to be updated accordingly.

The security should also be mentioned in the introduction.

Nokia noticed that the exact same text is used in the different proposed TRs, which does not have to be the case.

Conclusion: Revised to S1-153125

S1-153125 from China Mobile Com. Corporation: Introduction and Scope for NO TR

Revision of S1-153068

Conclusion: Revised to S1-153182

S1-153182 from China Mobile Com. Corporation: Introduction and Scope for NO TR

Revision of S1-153125

Conclusion: Agreed.

S1-153185 from Rapporteur (Nokia Networks): Skeleton for CriC TR

Conclusion: Noted. Final version in S1-153190.

S1-153186 from Rapporteur (Nokia Networks): Scope and Introduction for CriC

Conclusion: Agreed.

S1-153188 from Rapporteur (VODAFONE Group Plc): TR 22.7xx v.0.1.0 on (vertical) Massive Internet of Things (mIoT)

Output version of this meeting.

Conclusion: Agreed as a basis for future contributions.

S1-153189 from Rapporteur (Huawei): TR 22.7xx v.0.1.0 on (vertical) Enhanced Mobile Broadband (eMBB)

Output version of this meeting.

Conclusion: Agreed as a basis for future contributions.

S1-153190 from Rapporteur (Nokia Networks): TR 22.7xx v.0.1.0 on (vertical) Criticial Communications (CriC)

Output version of this meeting.

Conclusion: Agreed as a basis for future contributions.

S1-153191 from Rapporteur (China Mobile Com. Corporation): TR 22.7xx v.0.1.0 on (horizontal) NEO (Network Operation)

Output version of this meeting.

Conclusion: Agreed as a basis for future contributions.

3.4	Updates of existing use cases

S1-153028 from IAESI, THALES: Up-date of clause 5.1 “Ultra-reliable communications”

This contribution provides more examples and up-dates the text for service flows and requirements.

Discussion: Nokia wonder if some values are realistic. This has to be further checked off-line.

The " Central Coordinator" function has to be clarified and/or not to be mentioned if this is an architectural issue.

Conclusion: Revised to S1-153131

S1-153131 from IAESI, THALES: Up-date of clause 5.1 “Ultra-reliable communications”

Revision of S1-153028

Discussion: For Nokia, this is not agreeable material: the codec is not known, the video sounds archaic (black and white, very low resolution), the video is not refreshed at the same time as the audio, etc. so the values relating to these requirements are also not correct.

IAESI clarified that the video is in colour.

This will be rewritten to be more generic.

Conclusion: Revised to S1-153192

S1-153192 from IAESI, THALES: Up-date of clause 5.1 “Ultra-reliable communications”

Revision of S1-153131

Conclusion: Agreed.

S1-153049 from GIESECKE & DEVRIENT GmbH: addition of security requirements to use case 5.1

The following proposed requirements are added to the use case on Ultra-reliable communications:

The 3GPP system shall support 3GPP UEs to reliably authenticate themselves as mission critical.

The 3GPP system shall support end-to-end data protection, i.e. the 3GPP system shall provide mechanisms to prevent unauthorized access or manipulation of data sent over the 3GPP network.

Conclusion: Revised to S1-153132

S1-153132 from Giesecke & Devrient, Gemalto, Morpho, Oberthur Technologies, TeliaSonera, Alcatel-Lucent, Intel: Addition of security requirements to use case 5.1

Revision of S1-153049

Discussion: Minor modification needed.

Conclusion: Revised to S1-153193

S1-153193 from Giesecke & Devrient, Gemalto, Morpho, Oberthur Technologies, TeliaSonera, Alcatel-Lucent, Intel: Addition of security requirements to use case 5.1

Revision of S1-153132

Conclusion: Agreed.

S1-153038 from HUAWEI: E2E Resource Management for network slicing

This paper proposes requirement for E2E resource management for network slicing. It is resubmitted from SA1#71 (i.e. is a revision of S1-152227).

Conclusion: Agreed.

S1-153023 from ZTE Corporation: Clause 5.2 – Network Slicing Clarifications

This document proposes technical clarifications to TR 22.891 Clause 5.2 Network Slicing concepts and to add on new requirements

Discussion: This is seen as too many details here and should be simplified, in particular to mention only Stage 1 aspects.

Conclusion: Revised to S1-153133

S1-153133 from ZTE Corporation: Clause 5.2 – Network Slicing Clarifications

Revision of S1-153023

Discussion: There are still quite a few objections.

Conclusion: Noted.

S1-153029 from IAESI, THALES: Update of clause 5.2 “Network slicing”

This contribution adds examples for network slicing and updates the service and operational requirements.

Discussion: Same comment on the "coordinator".

Conclusion: Noted.

S1-153073 from HUAWEI TECHNOLOGIES Co. Ltd.: Slicing clarification

This paper proposes to clarify the potential requirements in slicing use case 5.2.

Discussion: There are some grammar problems at least in 5.2.2.

Some other rewording is needed.

Conclusion: Revised to S1-153134

S1-153134 from HUAWEI TECHNOLOGIES Co. Ltd.: Slicing clarification

Revision of S1-153073

Conclusion: Agreed.

S1-153089 from Cisco Systems: Clarifications for network slicing examples

The contribution provides clarifications for the example use cases currently listed for network slicing in TR 22.891.

Discussion: No problem with the concept but some re-wording and clarifications are needed.

Conclusion: Revised to S1-153135

S1-153135 from Cisco Systems: Clarifications for network slicing examples

Revision of S1-153089

Conclusion: Agreed.

S1-153095 from Ericsson LM: Network slicing isolation

The Network Slicing use case is enhanced and clarified and a new potential requirement is added.

Discussion: To be revised off-line.

Conclusion: Revised to S1-153136

S1-153136 from Ericsson LM: Network slicing isolation

Revision of S1-153095

Conclusion: Agreed.

S1-153100 from ZTE Corporation: update Coexistence with legacy systems to support legacy device

Revision of S1-153022.

It is proposed to update the coexistence with legacy systems to support legacy devices.

Discussion: There is a general support for the requirement but where it belongs has to be doubled check.

Conclusion: Revised to S1-153139

S1-153137 from ZTE Corporation: update Coexistence with legacy systems to support legacy device

Revision of S1-153100

Discussion: There are still quite a few objections.

Conclusion: Noted.

S1-153053 from LG Electronics: Text communication with IoT Devices

This paper proposed additional requirement considering scenario where simple message can be delivered from/to lightweight IoT devices.

Discussion: For Nokia, there is nothing to be done by 3GPP. Also for Alcatel-Lucent, this is an application issue.

KPN does not share this view and think there are implications on the network.

This is however too much focussing on the solution rather than on the requirements, and it has then to be rewritten.

Conclusion: Revised to S1-153138

S1-153138 from LG Electronics: Text communication with IoT Devices

Revision of S1-153053

Conclusion: Agreed.

S1-153104 from NEC, Intel: Resolving editor's note on use case 5.21 (IoT Device Initialization)

Revision of S1-153009.

This pCR tries to resolve the Editor’s note on the not agreed potential requirements of use case 5.21 (IoT Device Initialization).

Discussion: No disagreement but rewording needed.

Conclusion: Revised to S1-153139

S1-153139 from NEC, Intel: Resolving editor's note on use case 5.21 (IoT Device Initialization)

Revision of S1-153104

Discussion: The author indicated that more discussions are needed.

Conclusion: Noted.

S1-153094 from Intel Corporation (UK) Ltd: Update Bio-connectivity use case to support software and firmware updates

Adding need for efficient software and firmware updates for D2D-only devices use case

Discussion: This is not agreeable as such as the concept is not clear. It should be rewritten.

Conclusion: Revised to S1-153140

S1-153055 from INTERDIGITAL COMMUNICATIONS: Update of 5.23 "Access from less trusted networks"

The proposed changes to the use case make it less solution specific and more appropriate to SA-1 while preserving its original intent

Discussion: Nokia want to have the text clarified off line.

Conclusion: Revised to S1-153144

S1-153144 from INTERDIGITAL COMMUNICATIONS: Update of 5.23 "Access from less trusted networks"

Revision of S1-153055

Conclusion: Withdrawn.

S1-153140 from Intel Corporation (UK) Ltd: Update Bio-connectivity use case to support software and firmware updates

Revision of S1-153094

Conclusion: Agreed.

S1-153012 from Huawei, Hisilicon, China Telecom, Sony, Gemalto, Intel, ETRI, MTK, ZTE, China Unicom: Update the Wearable Device Communication use case in SMARTER

This document introduces the service types supported by the wearable devices and proposes associated potential requirements to update the wearable device communication use case in SA1 TR for SMARTER.

Discussion: Some comments from Alcatel-Lucent to be further checked off-line.

Conclusion: Revised to S1-153141

S1-153141 from Huawei, Hisilicon, China Telecom, Sony, Gemalto, Intel, ETRI, MediaTekMTK, ZTE, China Unicom, SK Telecom, ITRI, China Mobile, LGE: Update the Wearable Device Communication use case in SMARTER

Revision of S1-153012

Discussion: S1-153051 has also been considered in this version.

It was wondered if "non 3GPP access RAT" should be mentioned or not. A note will be added to specify that "Requirements are for 3GPP RATs, but non 3GPP RATs need also to be studied".

Conclusion: Revised to S1-153194

S1-153194 from Huawei, Hisilicon, China Telecom, Sony, Gemalto, Intel, ETRI, MediaTekMTK, ZTE, China Unicom, SK Telecom, ITRI, China Mobile, LGE: Update the Wearable Device Communication use case in SMARTER

Revision of S1-153141

Conclusion: Agreed.

S1-153051 from LG Electronics: Relay using heterogeneous access

This paper proposed to add additional requirement, considering the case where different radio access technologies is used at the relay.

Discussion: For Deutsche Telekom, this is acceptable in general but it has to be considered for variable use cases.

It has some analogies with the Intel document but Intel prefer to keep them as separate documents.

Conclusion: Revised to S1-153142

S1-153142 from LG Electronics: Relay using heterogeneous access

Revision of S1-153051

Conclusion: Withdrawn (included in S1-153141).

S1-153008 from NEC: SMARTER Service requirement on charging for multi RAT connections

This paper discusses about Potential Service Requirements on charging if UE obtains packet service using simultaneous multi RAT connections.

Two potential requirements are added:

The future network shall be able to differentiate charging a subscriber for the same 3GPP service if it is provided to a UE over different 3GPP and non-3GPP accesses.

And

The 3GPP system shall be able to issue CDRs reflecting the mixture of RAT types per bearer being used.

Discussion: Only the 1st requirement is to be kept.

Conclusion: Revised to S1-153143

S1-153143 from NEC: SMARTER Service requirement on charging for multi RAT connections

Revision of S1-153008

Conclusion: Agreed.

S1-153026 from HUAWEI: Addition of dynamically offloading traffic between RATs

It's proposed to add the potential requirement stating: The <5G system> shall be able to dynamically offload part of the traffic from one RAT to other RATs, taking into account e.g. load balance.

Discussion: This requirement might fit better to section 5.16

Conclusion: Revised to S1-153145

S1-153145 from HUAWEI: Addition of dynamically offloading traffic between RATs

Revision of S1-153026

Conclusion: Agreed.

S1-153030 from IAESI, THALES, GM Onstar: Update of clause 5.33 “Connected vehicles”

This contribution adds the use case of transmitting video images of hidden road segments and provides service and operational requirements.

Discussion: This is targeted to autonomous driving.

This seems to be an improvement of a Road safety service which is not defined by now. It should first be introduced with a proper Work Item.

Conclusion: Revised to S1-153146

S1-153146 from IAESI, THALES, GM Onstar: Update of clause 5.33 “Connected vehicles”

Revision of S1-153030

Discussion: Only the first requirement is agreeable.

Conclusion: Revised to S1-153195

S1-153195 from IAESI, THALES, GM Onstar: Update of clause 5.33 “Connected vehicles”

Revision of S1-153146

Conclusion: Agreed.

S1-153037 from GM - OnStar Europe, IAESI: update requirements for use case 5.33 connected vehicles

It proposes to enhance service requirements for 5.33 connect vehicles use case

Discussion: The wording is unclear, not only in this contribution but also in the present text: the meaning of "occasion" in this context is not understandable ("within 95%.of occasion.").

It is clarified that these numbers come from an ITRI study.

Conclusion: Revised to S1-153147

S1-153147 from GM - OnStar Europe, IAESI: update requirements for use case 5.33 connected vehicles

Revision of S1-153037

Conclusion: Withdrawn.

S1-153031 from IAESI, THALES: Update of clause 5.34 “Mobility on demand”

This contribution provides text for operational requirements.

Discussion: This contribution can be summarised by stating that the system has to support soft handover.

So this contribution can be simplified.

The paper also suggest to optimize the signalling when multiple UEs are performing handover at the same time, e.g. when in a train.

Conclusion: Revised to S1-153148

S1-153148 from IAESI, THALES: Update of clause 5.34 “Mobility on demand”

Revision of S1-153031

Discussion: Minor modifications needed (remove the operational requirements).

Conclusion: Revised to S1-153202

S1-153202 from IAESI, THALES: Update of clause 5.34 “Mobility on demand”

Revision of S1-153148

Conclusion: Agreed.

S1-153050 from LG Electronics: Context Aware Networking

This is resubmission of S1-152186 with update. Additional description and requirement is proposed in relation to various context information in the UE.

Conclusion: Agreed.

S1-153032 from IAESI, THALES: Update of clauses 5.45 and 5.46 (Industrial Automation)

This contribution proposes missing text for requirements and preconditions, such as "Coordinated time-frequency resources shall be allocated for regular cellular activity and for industrial critical communications in the area where S/As are deployed."

Discussion: For NTT DOCOMO and Telia Sonera, this is too specific for SA1 to discuss, and is rather a RAN contribution. Nokia also share the point that this should be rephrased in an SA1 terminology.

Conclusion: Revised to S1-153149

S1-153149 from IAESI, THALES: Update of clauses 5.45 and 5.46 (Industrial Automation)

Revision of S1-153032

Discussion: Still some concerns.

Conclusion: Noted.

S1-153070 from ITRI: Update to clause 5.49 Network capability exposure

This paper proposes some clarification text to description sub-clause and adds an additional requirements related to Network capability exposure use case of clause 5.49.

Discussion: Some rewording is needed.

A new use case would be more appropriate for this new requirement.

Conclusion: Revised to S1-153150

S1-153150 from ITRI: Update to clause 5.49 Network capability exposure

Revision of S1-153070.

The use case is clarified to be on Fronthaul/Backhaul Network Sharing.

Discussion: About the requirements "The 3GPP system shall be able to provide fronthaul/backhaul network sharing information and capabilities.", Nokia remarked that it is not clear to who the information is provided.

Conclusion: Revised to S1-153196

S1-153196 from ITRI: Update to clause 5.49 Network capability exposure

Revision of S1-153150

Conclusion: Agreed.

3.4a	New use cases / Update of existing use cases related to credentials / identifiers

S1-153045 from ORANGE: Subscriber’s identity and credentials storage and management

This contribution proposes a set of requirements on subscriber’s identity and credentials storage and management.

A new section is proposed, stating in short that 5G has to support at least the level of security of previous generations and, in addition, the operator shall be able to control and approve (before using it) the level of security of the secure entity.

Discussion: Telecom Italia sent an e-mail to Orange to state they support the contribution.

About the sentence "The credentials shall never leave the secure entity,", Vodafone wonder if this is compatible with GSMA mechanism to download UICC. Gemalto clarified that this is not incompatible.

For Intel, the sentence "The provisioning of credentials and subscriber’s identity in the UE allowing the authentication to 5G system is under operator responsibility and therefore out of scope of 3GPP." should be deleted since it is up to SA3 to decide. For Oberthur, it is not to be decided by SA3 but indeed by SA1 since this is a high level requirement.

For Nokia, if it is outside the scope, it should not be mentioned.

For Ericsson, NEC and LG, this paper is too conservative in its approach and too restrictive. For NEC, the intentions are good but not correctly written since they do not specify what the system should actually do. They should be rewritten as service requirements and not focussing on where/how to store the information.

For Intel, a generic statement stating that "5G should be at least as secure as 4G" is enough.

For Qualcomm, the problem is that this contribution seems to impose the previous generation mechanisms on 5G, when the intention is on the level of security, which should be at least as good, not on the mechanisms themselves.

NEC propose to revise the text deeply to start from the most obvious requirements to the most specific ones and check how much can be approved.

For Nokia, the problem is on the concept of "level of security" and how it applies to different types of terminals (voice, M2M, etc).

There are other documents on security, and it was suggested to use them as a basis for future work rather than this one.

Intel insisted that this should be discussed in SA3, to which G&D answered that this is clearly a service requirement to be handled in SA1.

Whatever can be "rescued" from this contribution is to put in another document.

For Cisco, who is neutral on the topic, this discussion has been going on for several meetings and wonder about how to solve this issue in the future.

Conclusion: Revised to S1-153126

S1-153126 from ORANGE: Subscriber’s identity and credentials storage and management

Discussion: Orange did not provide the revision, so the original document is withdrawn.

Conclusion: Withdrawn.

S1-153046 from GIESECKE & DEVRIENT GmbH: Use case device theft prevention

The TR mentions the usage of devices with significant value (drones, smart phones...). Those devices are potential targets of theft and therefore mechanisms are needed to prevent that. This includes the protection of relevant identifiers as well as the possibility to manage stolen devices remotely.

So a use case on device theft prevention is proposed.

Discussion: For Vodafone, "theft mitigation" is a better wording that "theft prevention", which is a fact that cannot really be prevented. For T-Mobile, the 2 aspects are valid (mitigation and/or prevention).

For Ericsson, this is an old problem with IMEIs which has been solved for quite some time. So the sentence "However, current technology does not provide sufficient protection of those identities (IMEIs)…" should be deleted.

The problem is that IMEI is mentioned, when this is supposed to be a wider problem than just IMEI. So all references to IMEI should be removed.

Conclusion: Revised to S1-153128

S1-153127 from GIESECKE & DEVRIENT GmbH: Use case device theft prevention

Revision of S1-153046

Discussion: Comments received off-line.

Conclusion: Revised to S1-153175

S1-153175 from Giesecke & Devrient, Morpho, Gemalto, Oberthur Technologies, Sprint: Use case device theft prevention

Revision of S1-153127.

The use case is now entitled "Device Theft Preventions / Stolen Device Recovery" and the text has been rewritten for clarity purposes.

Discussion: Some further modifications proposed during presentation.

Conclusion: Revised to S1-153197

S1-153197 from Giesecke & Devrient, Morpho, Gemalto, Oberthur Technologies, Sprint: Use case device theft prevention

Revision of S1-153175

Conclusion: Agreed.

S1-153047 from GIESECKE & DEVRIENT GmbH: Identifier and identity protection

Identifiers such as subscriber identity, device identity, device type identity and others are used. It is essential that those identities are stored on the device protected against manipulation in order to prevent DoS and other attacks. This document proposes the addition of a new use case.

Discussion: For Alcatel-Lucent, this could be combined with the previous contribution, but not to the author.

For Nokia, these are valid concerns but the contribution needs to be more specific, so some re-writing is needed.

This is seen by several companies as too generic: the exact identifiers need to be clarified.

Conclusion: Noted.

S1-153048 from GIESECKE & DEVRIENT GmbH: service related subscription management

Subscriptions may have different “owners” and therefore dedicated mechanisms are required to manage those subscriptions.

This document proposes the addition of a new use case.

Discussion: For several companies, this is also too generic and should be rewritten in a more specific way: e.g. what kind of subscriptions?, about "5G devices shall be able to switch between subscriptions based on the service it is requested to access.": what about if there are more than 2 subscriptions involved, etc.

Conclusion: Revised to S1-153129

S1-153128 from GIESECKE & DEVRIENT GmbH: service related subscription management

Revision of S1-153048

Conclusion: Revised to S1-153179

S1-153179 from Giesecke & Devrient, Morpho, Gemalto, Oberthur Technologies: service related subscription management

Revision of S1-153128

Discussion: The author mentioned that the discussion is not completed and more time will be needed after this meeting.

Conclusion: Noted.

S1-153083 from ORANGE: Subscriber’s identity and credentials storage and management to IOT Device

This contribution proposes a set of requirements on subscriber’s identity and credentials storage and management specific to IOT Device.

Discussion: Alcatel-Lucent and Intel have serious concerns about deleting/re-writing this section. From a procedural point-of-view, the chair has also concerns to consolidate the requirements just for this section when this has to be done for the entire TR.

Conclusion: Noted.

S1-153084 from ORANGE: Subscription security credentials Management

Discussion: Same comment as for the previous one.Noted.

Conclusion: Noted.

S1-153086 from Alcatel-Lucent : 5G Networks: A security perspective

This document provides background information related to the need for new security mechanisms to be provided for 5G devices. 3GPP security is a key advantage over other access technologies. To compete in new markets with different types of devices, it will be essential to provide the same or better level of security and to do so in a way that is compatible with the form factors and human interfaces of 5G devices.

Discussion: This is for information only.

The actual changes are in S1-153087.

Conclusion: Noted.

S1-153087 from Alcatel-Lucent: FS_SMARTER security considerations

This document proposes security considerations for FS_SMARTER.

Discussion: For Morpho, this can be done in the new documents rather than on the previous ones. For the chair, this is not a valid argument: it was never stated to stop working on the existing use cases.

The Editor's note removal is a problem.

The text is too much focussing on the devices and not on the services.

Change 1 overlaps another one from G&D and should not be included, change 3 is not agreeable, the other have to be rewritten.

Conclusion: Revised to S1-153130

S1-153129 from Alcatel-Lucent: FS_SMARTER security considerations

Revision of S1-153087

Discussion: Section 6.1 is not agreed to be deleted.

Orange has issues with the 2 requirements: they can be used as a basis for future work but are not agreeable as such.

Conclusion: Noted.

S1-153088 from Gemalto N.V., Telecom Italia, Giesecke & Devrient GmbH: Subscription update service flow alignment in section 5.22.3

During SA1#71 the use case in S1-152730 was discussed and the proposed requirements were agreed. However the service flow in 5.22.3 was not updated accordingly to the agreed proposed requirements. This document proposes to align the service flow to the agreed proposed requirements.

Conclusion: Agreed.

S1-153090 from Gemalto N.V., Giesecke & Devrient GmbH: IoT Device Initilization editor’s note removal

During last SA1#71 meeting document S1-152729 was agreed with an editor’s note indicating further study was needed with regards to “The 3GPP System shall support a secure mechanism (e.g. a factory installed certificate) that enables a device (e.g. IoT device) that has not been provided with a 3GPP subscription to establish access to a 3GPP network.” This document propose an improvement to the existing requirement.

Conclusion: Withdrawn.

S1-153097 from Ericsson LM: Industrial Factory Automation - Access Security

A new use case is proposed for Industrial Factory Automation.

Discussion: Some rewording is needed, but no disagreement with the use case itself.

Conclusion: Revised to S1-153137

S1-153130 from Ericsson LM: Industrial Factory Automation - Access Security

Revision of S1-153097

Conclusion: Agreed.

3.5	New use cases

S1-153039 from Huawei, NEC, DT, ALU: E2E Resource Allocation and QoS Guarantee

This paper proposes a use case for E2E resource allocation and QoS guarantee. It is resubmitted from SA1#71 (i.e. is a revision of S1-152444).

Discussion: Cisco and Ericsson prefer to have a specific use case for this.

Conclusion: Revised to S1-153151

S1-153151 from Huawei, NEC, DT, ALU: E2E Resource Allocation and QoS Guarantee

Revision of S1-153039

Conclusion: Withdrawn.

S1-153071 from LG Electronics: Diversified Connectivity

This is resubmission of S1-152187 (with update) that was not treated during SA1#71.

A new use case is proposed on Diversified Connectivity.

Discussion: To be revised off-line with the Rapporteur and Deutsche Telekom, in particular to address the problem of fraud.

Conclusion: Revised to S1-153152

S1-153152 from LG Electronics: Diversified Connectivity

Revision of S1-153071

Conclusion: Agreed.

S1-153074 from QUALCOMM Incorporated: SMARTER: Use case for Automotive: Automated Cooperative Driving

Resubmission from SA1#71 A new use case for Automotive Cooperative Driving Automation is added.

Discussion: Some acronyms are not explained.

3GPP uses metric and not imperial.

This refers to V2X when it was concluded earlier not to include V2X in 5G.

Conclusion: Noted, to be resubmitted by the author at the appropriate time.

S1-153080 from Huawei Tech.(UK) Co., Ltd: Resubmission of S1-152253 use case for cooperative short distance platooning

Conclusion: Withdrawn.

S1-153081 from Huawei Tech.(UK) Co., Ltd: Resubmission of S1-152254 use case see-through for assisted overtaking

Conclusion: Noted, to be resubmitted by the author at the appropriate time.

S1-153076 from QUALCOMM Incorporated: SMARTER: Use case for Sensor and State Map Sharing

Use case for Sensor and State Map Sharing

Discussion: V2X-related.

Conclusion: Noted, to be resubmitted by the author at the appropriate time.

S1-153075 from QUALCOMM Incorporated: SMARTER: Use case for multiple services with different subscriptions

Resubmission from SA1#71 This paper proposes to introduce a use case to support Multiple Simultaneously Active Subscriptions.

Conclusion: Revised to S1-153153

S1-153153 from QUALCOMM Incorporated: SMARTER: Use case for multiple services with different subscriptions

Revision of S1-153075

Discussion: For Nokia, the requirement on the 3GPP system is not clear.

Conclusion: Noted.

S1-153107 from Dish Network: New SMARTER use case on Multi-Connectivity and Service Sharing across operators

Revision of S1-153062

Conclusion: Revised to S1-153155

S1-153155 from Dish Network: New SMARTER use case on Multi-Connectivity and Service Sharing across operators

Revision of S1-153107

Conclusion: Agreed.

S1-153078 from Huawei Tech.(UK) Co., Ltd: Revision of S1-152245 use case for moving ambulance and bio-connectivity

This paper introduces a use case to support high bandwidth, low latency, high mobility, and ultra high reliability seamlessly in wide area, in order to provide mHealth and telemedicine services in a moving ambulance on the way to hospital.

Conclusion: Revised to S1-153156

S1-153156 from Huawei Tech.(UK) Co., Ltd: Revision of S1-152245 use case for moving ambulance and bio-connectivity

Revision of S1-153078

Conclusion: Agreed.

S1-153079 from Huawei Tech.(UK) Co., Ltd: Revision of S1-152246 use case for on-demand deployment of physical access network infrastructure

This paper proposes a use case to support on-demand physical network infrastructure deployment via nomadic access nodes.

Discussion: To be discussed off-line with interested companies.

Conclusion: Revised to S1-153157

S1-153157 from Huawei Tech.(UK) Co., Ltd: Revision of S1-152246 use case for on-demand deployment of physical access network infrastructure

Revision of S1-153079

Discussion: Alcatel-Lucent does not support this contribution. Ericsson also have concerns with this concept. They are not sure that the signalling will be actually reduced.

This might be a topic for study in RAN.

Conclusion: Noted.

S1-153123 from III: Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)

Revision of S1-153006

Conclusion: Revised to S1-153158

S1-153158 from III: Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)

Revision of S1-153123.

The use case has been revised so that it doesn't look as a solution anymore.

Discussion: Nokia have no confidence in the numbers presented here. The chair noticed that this might be a general problem.

All these numbers have to be removed and a simple sentence has to be put instead to state that direct air to ground communications have to be supported.

Conclusion: Revised to S1-153199

S1-153199 from III: Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)

Revision of S1-153158

Conclusion: Agreed.

S1-153010 from ETRI: eMVNO Service Providing Spectrum Sharing and Waveform Transparency

In this service scenario, the access network provided for eMVNO service is technology agnostic that the eMVNOs are free to develop their own device and access technology

Discussion: The spectrum sharing is an issue for several companies (Orange, NTT DOCOMO, etc). It needs at least further study, maybe in RAN.

Conclusion: Revised to S1-153159

S1-153159 from ETRI: eMVNO Service Providing Spectrum Sharing and Waveform Transparency

Revision of S1-153010

Conclusion: Witthdrawn.

S1-153034 from IAESI, THALES: Flexible spectrum access

This contribution introduces a new use case on flexible spectrum use schemes.

Discussion: This is also too detailed for SA1.It has to be rewritten to make it more in the SA1 style.

Conclusion: Revised to S1-153160

S1-153160 from IAESI, THALES: Flexible spectrum access

Revision of S1-153034

References to central coordinator and to implementation have been removed.

Discussion: Spectrum sharing is not an SA1 topic, according to Nokia.

Conclusion: Noted.

S1-153013 from Huawei, Hisilicon, China Telecom, Sony, Gemalto, ETRI, China Unicom, Deutsche Telekom: SMARTER Use Case for Wearable Device Charging

This document introduces the charging requirement for wearable devices and associated potential requirements are updated proposed for addition for wearable issue in SA1 TR for SMARTER

Discussion: To be revised off-line with Nokia,

Conclusion: Revised to S1-153161

S1-153161 from Huawei, Hisilicon, China Telecom, Sony, Gemalto, ETRI, China Unicom, Deutsche Telekom, SK Telecom, China Mobile, Intel: SMARTER Use Case for Wearable Device Charging

Revision of S1-153013

Discussion: Some further editing made while projecting.

Conclusion: Revised to S1-153200

S1-153200 from Huawei, Hisilicon, China Telecom, Sony, Gemalto, ETRI, China Unicom, Deutsche Telekom, SK Telecom, China Mobile, Intel: SMARTER Use Case for Wearable Device Charging

Revision of S1-153161

A "shall" is replaced by a "will" in the service flows.

Conclusion: Agreed.

S1-153101 from ZTE Corporation, ETRI, Ministry of Interior, France , China Telecom,China Unicom, Huawei: Use case for Emergency assistant transmission by normal UE

Revision of S1-153024.

This contribution proposes a use case that the user who is in emergency condition can transmit help signal through normal UE not only depend on the professional rescue equipment which will great help the user to be rescued from the emergency more quickly than before .

Discussion: This has to be simplified too, and as to focus on the emergency scenarios.

Conclusion: Revised to S1-153162

S1-153162 from ZTE Corporation, ETRI, Ministry of Interior, France , China Telecom,China Unicom, Huawei: Use case for Emergency assistant transmission by normal UE

Revision of S1-153101

Discussion: Several issues are still unclear and need to be solved before this is agreeable.

Conclusion: Noted.

S1-153052 from LG Electronics: Telemedicine Support

This paper describes a new SMARTER use case where preferential treatment is applied to the mission critical IoT devices such as devices for telemedicine.

Conclusion: Agreed.

S1-153103 from Deutsche Telekom: Network Slicing Roaming Use Case

Revision of S1-153027.

This is a new use case on Network Slicing.

Discussion: The full use case is not agreeable as such so it has to be revised after checking and keeping only what is agreeable.

Conclusion: Revised to S1-153164

S1-153164 from Deutsche Telekom: Network Slicing Roaming Use Case

Revision of S1-153103

Conclusion: Agreed.

S1-153033 from IAESI, THALES: SDN concepts applied to lower layers of 3GPP system

This contribution introduces a new use case including partial lower layers virtualization and a local coordinator.

The use case is called "Software Defined Networks (SDN) concepts applied to lower layers of 3GPP system"

Discussion: This is an architecture contribution, to be discussed in SA2.

Conclusion: Noted.

S1-153054 from LG Electronics: Use case on Traffic relay and slicing

This paper describes a new SMARTER use case where traffic of different characteristic is optimally supported to a UE over relay.

Discussion: Linked to V2X, so to be handled at a future time.

Conclusion: Noted.

S1-153105 from Dish Network: New SMARTER Use Case on support for broadcast service

Revision of S1-153056

Discussion: There is a general support but there should be no explicit mention of MBMS and some rephrasing is needed.

Conclusion: Revised to S1-153165

S1-153165 from Dish Network: New SMARTER Use Case on support for broadcast service

Revision of S1-153105

Conclusion: Agreed.

S1-153163 from Dish Network: New SMARTER Use Case on support for flexible broadcast content caching in 3GPP

Revision of S1-153106

Discussion: This is to be done as a revision of an existing use case.

Conclusion: Revised to S1-153166

S1-153166 from Dish Network: New SMARTER Use Case on support for flexible broadcast content caching in 3GPP

Revision of S1-153163

Conclusion: Agreed.

S1-153072 from Nokia Networks Oy: Proposed new use case on WLL

A new use case is proposed on Wireless Local Loop (WLL).

Discussion: The concept of "geofencing" is not known so it has to be explained or avoided.

Conclusion: Revised to S1-153167.

S1-153167 from Nokia Networks Oy: Proposed new use case on WLL

Revision of S1-153072

Conclusion: Agreed.

S1-153108 from Dish Network: New SMARTER Use Case for 5G Connectivity using satellites

Revision of S1-153093

Conclusion: Revised to S1-153168

S1-153168 from Dish Network: New SMARTER Use Case for 5G Connectivity using satellites

Revision of S1-153108

Conclusion: Agreed.

3.6	Other contributions to TR 22.891 (e.g. editorials)

S1-153003 from Rapporteur: TR 22.891 on FS_SMARTER v1.0.0 (SP-150562)

Conclusion: Noted.

S1-153098 from ETRI: Proposed Diagram for SMARTER Service

Revision of S1-153011.

This proposes a figure to show the newly agreed categories for the use cases:

1) Enhanced Mobile Broadband

2) Critical Communications

3) Massive Machine Type Communications

4) Network Operation

Conclusion: Agreed.

S1-153122 from Alcatel-Lucent : FS_SMARTER cost clean up

Revision of S1-153085.

The word "cost" is replaced by more appropriate words through all the document (e.g. "complexity", "concern", etc.)

Conclusion: Agreed.

S1-153007 from III: Quantum Entanglement: Cryptography and Communication (for information only)

1. Introduction 2. Quantum Entanglement 3. Quantum Cryptography - Quantum Key Distribution 4. Physical Limit for E2E Time Delay - Speed of Light 5. Shorten E2E Delay - Faster-Than-Light Communication 6. Conclusions To improve communication security, quantum cryptography could be considered. To shorten E2E delay, technology regarding Faster-Than-Light (FTL) communication is required.

Discussion: The chair stressed that this document is very valuable for information, even if there was not enough time to handle it, and encouraged delegates to review it off line.

Conclusion: Noted.

4	Work planning contributions

4.1	FS_SMARTER status update

S1-153005 from rapporteur: SMARTER status report

All the results of this present meeting are summarised:

4 new SIDs agreed for 3 vertical Building Block TRs and one horizontal Building Block TR, all arising from TR22.891.

Vertical TRs - Enhanced Mobile Broadband, Critical Communications and Massive Internet of Things. Horizontal TR - Network Operation.

Grouping of use cases from TR22.891 and construction of families of related use cases within each group completed.

Next steps:

Expected date to send TR 22.891 to SA plenary:

For information: SA#69 (09/2015) Done.

For approval: SA#70 (12/2015)

Expected date to send new BB TRs to SA plenary:

For information: SA#71 (03/2016)

For approval: SA#72 (06/2016)

Discussion: The FS_SMARTER SID might have to be updated to reflect the Building Blocks.

The names of the rapporteurs can be added (instead of just the companies).

The controversial issue ("Relationship between specific security work in the vertical TRs and overall system security in the horizontal Network Operation TR.") can now be considered as solved. It can be deleted.

It is reminded that this kind of report is for SA1 internal use only, in particular this time where there will be another SA1 meeting before the plenary.

Conclusion: Revised to S1-153206

S1-153206 from rapporteur: SMARTER status report

Revision of S1-153005

Conclusion: Noted.

5	Next meetings

5.1	Calendar

2015 meetings:

SA1#72	16 – 20 Nov 2015	Anaheim, CA, USA	Mega meeting

For SA1#72, the deadlines will be Monday 9th of November for tdoc/CR number requests and Tuesday 10th November for document upload. This is a trial to have a short time between the deadlines and the start of the meeting.

2016 meetings:

SA1#73	1-5 Feb 2016	Okinawa, Japan (TBC)

SA1#74	9-13 May 2016	Europe (TBD)

SA1#75	22-26 Aug 2016	North America (TBD)

SA1#76	7-11 Nov 2016	Tenerife, Spain (TBC)

6	Any other business

There was no contribution for this agenda item.

See the change on deadlines in the previous agenda item.

7	Close

The SA1 chair, Mr. Toon Norp (KPN), thanked the delegates for their hard work and willingness to compromise, as well as the MCC support, Mr. Alain Sultan (ETSI) for his work.

The SA1 delegates thanked the chair for his excellent work at chairing this meeting. They also thanked the host, the American Friends of 3GPP, for the facilities and services provided.

Annex 1: TDoc list

Tdoc #	Source	Title
S1-153000	Chairman	Draft Agenda
S1-153001	Chairman	2nd draft agenda
S1-153002	Chairman	3rd Draft Agenda
S1-153003	Rapporteur	TR 22.891 on FS_SMARTER v1.0.0 (SP-150562)
S1-153004	chairman	Report for SA1 from SA plenary and RAN 5G WS
S1-153005	rapporteur	SMARTER status report
S1-153006	III	Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)
S1-153007	III	Quantum Entanglement: Cryptography and Communication (for information only)
S1-153008	NEC	SMARTER Service requirement on charging for multi RAT connections
S1-153009	NEC	Resolving editor's note on use case 5.21 (IoT Device Initialization)
S1-153010	ETRI	eMVNO Service Providing Spectrum Sharing and Waveform Transparency
S1-153011	ETRI	Proposed Diagram for SMARTER Service
S1-153012	Huawei, Hisilicon, China Telecom, Sony, Gemalto, Intel, ETRI, MTK, ZTE, China Unicom	Update the Wearable Device Communication use case in SMARTER
S1-153013	Huawei, Hisilicon, China Telecom, Sony, Gemalto, ETRI, China Unicom, Deutsche Telekom	SMARTER Use Case for Wearable Device Charging
S1-153014	VODAFONE Group Plc	SMARTER Use Cases Grouping
S1-153015	VODAFONE Group Plc	SMARTER Building Block enhanced Mobile BroadBand
S1-153016	VODAFONE Group Plc	SMARTER Building Block Critical Machine Communications
S1-153017	VODAFONE Group Plc	SMARTER Building Block massive IOT
S1-153018	VODAFONE Group Plc	SMARTER Building Block Network operation
S1-153019	VODAFONE Group Plc	Study on New Services and Markets Technology Enablers - massive Internet Of Things
S1-153020	VODAFONE Group Plc	TR Skeleton mIOT
S1-153021	VODAFONE Group Plc	Introduction and Scope for mIOT TR
S1-153022	ZTE Corporation	update Coexistence with legacy systems to support legacy device
S1-153023	ZTE Corporation	Clause 5.2 – Network Slicing Clarifications
S1-153024	ZTE Corporation	Use case for Emergency assistant transmission by normal UE
S1-153025	HUAWEI	Low-delay video coding
S1-153026	HUAWEI	Addition of dynamically offloading traffic between RATs
S1-153027	Deutsche Telekom	Network Slicing Roaming Use Case
S1-153028	IAESI, THALES	Up-date of clause 5.1 “Ultra-reliable communications”
S1-153029	IAESI, THALES	Update of clause 5.2 “Network slicing”
S1-153030	IAESI, THALES, GM Onstar	Update of clause 5.33 “Connected vehicles”
S1-153031	IAESI, THALES	Update of clause 5.34 “Mobility on demand”
S1-153032	IAESI, THALES	Update of clauses 5.45 and 5.46 (Industrial Automation)
S1-153033	IAESI, THALES	SDN concepts applied to lower layers of 3GPP system
S1-153034	IAESI, THALES	Flexible spectrum access
S1-153035	Alcatel-Lucent	FS_SMARTER considerations on grouping use cases
S1-153036	Alcatel-Lucent	FS_SMARTER considerations on requirements grouping
S1-153037	GM - OnStar Europe, IAESI	update requirements for use case 5.33 connected vehicles
S1-153038	HUAWEI	E2E Resource Management for network slicing
S1-153039	Huawei, NEC, DT, ALU	E2E Resource Allocation and QoS Guarantee
S1-153040	HUAWEI TECHNOLOGIES Co. Ltd.	Discuss grouping of SMARTER requirements
S1-153041	Nokia Networks Oy	Use case categorisation (rev of S1-152210)
S1-153042	Nokia Networks Oy	Proposed structure for the dedicated TRs
S1-153043	Nokia Networks Oy	Study on SMARTER Reliable Communications
S1-153044	Nokia Networks Oy	General clean-up of TR 22.891
S1-153045	ORANGE	Subscriber’s identity and credentials storage and management
S1-153046	GIESECKE & DEVRIENT GmbH	Use case device theft prevention
S1-153047	GIESECKE & DEVRIENT GmbH	Identifier and identity protection
S1-153048	GIESECKE & DEVRIENT GmbH	service related subscription management
S1-153049	GIESECKE & DEVRIENT GmbH	addition of security requirements to use case 5.1
S1-153050	LG Electronics	Context Aware Networking
S1-153051	LG Electronics	Relay using heterogeneous access
S1-153052	LG Electronics	Telemedicine Support
S1-153053	LG Electronics	Text communication with IoT Devices
S1-153054	LG Electronics	Use case on Traffic relay and slicing
S1-153055	INTERDIGITAL COMMUNICATIONS	Update of 5.23 "Access from less trusted networks"
S1-153056	Dish Network	New SMARTER Use Case on support for broadcast service
S1-153057	Dish Network	New SMARTER Use Case on support for flexible broadcast content caching in 3GPP
S1-153058	LG Electronics France	Discussion on grouping SMARTER use cases
S1-153059	LG Electronics France	Study on New Services and Markets Technology Enablers - enhanced Mobile BroadBand
S1-153060	LG Electronics France	TR Skeleton eMBB
S1-153061	LG Electronics France	Introduction and Scope for eMBB TR
S1-153062	Dish Network	New SMARTER use case on Multi-Connectivity and Service Sharing across operators
S1-153063	LG Electronics France	Study on New Services and Markets Technology Enablers - High Mobility and Vehicular Services (HiV2X)
S1-153064	LG Electronics France	TR Skeleton HiV2X
S1-153065	LG Electronics France	Introduction and Scope for HiV2X
S1-153066	China Mobile Com. Corporation	Study on New Services and Markets Technology Enablers - Network operation
S1-153067	China Mobile Com. Corporation	TR Skeleton NO
S1-153068	China Mobile Com. Corporation	Introduction and Scope for NO TR
S1-153069	TTA	Critical Communications in the 5G
S1-153070	ITRI	Update to clause 5.49 Network capability exposure
S1-153071	LG Electronics	Diversified Connectivity
S1-153072	Nokia Networks Oy	Proposed new use case on WLL
S1-153073	HUAWEI TECHNOLOGIES Co. Ltd.	Slicing clarification
S1-153074	QUALCOMM Incorporated	SMARTER: Use case for Automotive: Automated Cooperative Driving
S1-153075	QUALCOMM Incorporated	SMARTER: Use case for multiple services with different subscriptions
S1-153076	QUALCOMM Incorporated	SMARTER: Use case for Sensor and State Map Sharing
S1-153077	QUALCOMM Incorporated	SMARTER: Use Case Categorization
S1-153078	Huawei Tech.(UK) Co., Ltd	Revision of S1-152245 use case for moving ambulance and bio-connectivity
S1-153079	Huawei Tech.(UK) Co., Ltd	Revision of S1-152246 use case for on-demand deployment of physical access network infrastructure
S1-153080	Huawei Tech.(UK) Co., Ltd	Resubmission of S1-152253 use case for cooperative short distance platooning
S1-153081	Huawei Tech.(UK) Co., Ltd	Resubmission of S1-152254 use case see-through for assisted overtaking
S1-153082	Huawei Tech.(UK) Co., Ltd	use case of idle mode mobility support for ultra-light mobile devices
S1-153083	ORANGE	Subscriber’s identity and credentials storage and management to IOT Device
S1-153084	ORANGE	Subscription security credentials Management
S1-153085	Alcatel-Lucent	FS_SMARTER cost clean up
S1-153086	Alcatel-Lucent	5G Networks: A security perspective
S1-153087	Alcatel-Lucent	FS_SMARTER security considerations
S1-153088	Gemalto N.V., Telecom Italia, Giesecke & Devrient GmbH	Subscription update service flow alignment in section 5.22.3
S1-153089	Cisco Systems	Clarifications for network slicing examples
S1-153090	Gemalto N.V., Giesecke & Devrient GmbH	IoT Device Initilization editor’s note removal
S1-153091	HUAWEI TECHNOLOGIES Co. Ltd.	Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband
S1-153092	HUAWEI TECHNOLOGIES Co. Ltd.	Introduction and Scope for eMBB
S1-153093	Dish Network	New SMARTER Use Case for 5G Connectivity using satellites
S1-153094	Intel Corporation (UK) Ltd	Update Bio-connectivity use case to support software and firmware updates
S1-153095	Ericsson LM	Network slicing isolation
S1-153096	KPN	Proposed structure for FS_SMARTER Building Block TRs
S1-153097	Ericsson LM	Industrial Factory Automation - Access Security
S1-153098	ETRI	Proposed Diagram for SMARTER Service
S1-153099	HUAWEI TECHNOLOGIES Co. Ltd.	Discuss grouping of SMARTER requirements
S1-153100	ZTE Corporation	update Coexistence with legacy systems to support legacy device
S1-153101	ZTE Corporation, ETRI, Ministry of Interior, France , China Telecom,China Unicom, Huawei	Use case for Emergency assistant transmission by normal UE
S1-153102	LG Electronics France	Study on New Services and Markets Technology Enablers - High Mobility and Vehicular Services (HiV2X)
S1-153103	Deutsche Telekom	Network Slicing Roaming Use Case
S1-153104	NEC, Intel	Resolving editor's note on use case 5.21 (IoT Device Initialization)
S1-153105	Dish Network	New SMARTER Use Case on support for broadcast service
S1-153106	Dish Network	New SMARTER Use Case on support for flexible broadcast content caching in 3GPP
S1-153107	Dish Network	New SMARTER use case on Multi-Connectivity and Service Sharing across operators
S1-153108	Dish Network	New SMARTER Use Case for 5G Connectivity using satellites
S1-153109	HUAWEI TECHNOLOGIES Co. Ltd.	Discuss grouping of SMARTER requirements
S1-153110	Nokia Networks Oy	Use case categorisation (rev of S1-152210)
S1-153111	Alcatel-Lucent	FS_SMARTER considerations on requirements grouping
S1-153112	Vodafone/Rapporteur	Grouping of use cases into families
S1-153113	LG Electronics France	Study on New Services and Markets Technology Enablers - High Mobility and Vehicular Services (HiV2X)
S1-153114	VODAFONE Group Plc	Study on New Services and Markets Technology Enablers - massive Internet Of Things
S1-153115	Nokia Networks Oy	Study on SMARTER Reliable Communications
S1-153116	HUAWEI TECHNOLOGIES Co. Ltd., LG	Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband
S1-153117	China Mobile Com. Corporation	Study on New Services and Markets Technology Enablers - Network operation
S1-153118	Nokia Networks Oy	Proposed structure for the dedicated TRs
S1-153119	VODAFONE Group Plc	TR Skeleton mIOT
S1-153120	VODAFONE Group Plc	Introduction and Scope for mIOT TR
S1-153121	LG Electronics France, Huwaei	TR Skeleton eMBB
S1-153122	Alcatel-Lucent	FS_SMARTER cost clean up
S1-153123	III	Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)
S1-153124	China Mobile Com. Corporation	TR Skeleton NO
S1-153125	China Mobile Com. Corporation	Introduction and Scope for NO TR
S1-153126	ORANGE	Subscriber’s identity and credentials storage and management
S1-153127	GIESECKE & DEVRIENT GmbH	Use case device theft prevention
S1-153128	GIESECKE & DEVRIENT GmbH	service related subscription management
S1-153129	Alcatel-Lucent	FS_SMARTER security considerations
S1-153130	Ericsson LM	Industrial Factory Automation - Access Security
S1-153131	IAESI, THALES	Up-date of clause 5.1 “Ultra-reliable communications”
S1-153132	Giesecke & Devrient, Gemalto, Morpho, Oberthur Technologies, TeliaSonera, Alcatel-Lucent, Intel	Addition of security requirements to use case 5.1
S1-153133	ZTE Corporation	Clause 5.2 – Network Slicing Clarifications
S1-153134	HUAWEI TECHNOLOGIES Co. Ltd.	Slicing clarification
S1-153135	Cisco Systems	Clarifications for network slicing examples
S1-153136	Ericsson LM	Network slicing isolation
S1-153137	ZTE Corporation	update Coexistence with legacy systems to support legacy device
S1-153138	LG Electronics	Text communication with IoT Devices
S1-153139	NEC, Intel	Resolving editor's note on use case 5.21 (IoT Device Initialization)
S1-153140	Intel Corporation (UK) Ltd	Update Bio-connectivity use case to support software and firmware updates
S1-153141	Huawei, Hisilicon, China Telecom, Sony, Gemalto, Intel, ETRI, MediaTekMTK, ZTE, China Unicom, SK Telecom, ITRI, China Mobile, LGE	Update the Wearable Device Communication use case in SMARTER
S1-153142	LG Electronics	Relay using heterogeneous access
S1-153143	NEC	SMARTER Service requirement on charging for multi RAT connections
S1-153144	INTERDIGITAL COMMUNICATIONS	Update of 5.23 "Access from less trusted networks"
S1-153145	HUAWEI	Addition of dynamically offloading traffic between RATs
S1-153146	IAESI, THALES, GM Onstar	Update of clause 5.33 “Connected vehicles”
S1-153147	GM - OnStar Europe, IAESI	update requirements for use case 5.33 connected vehicles
S1-153148	IAESI, THALES	Update of clause 5.34 “Mobility on demand”
S1-153149	IAESI, THALES	Update of clauses 5.45 and 5.46 (Industrial Automation)
S1-153150	ITRI	Update to clause 5.49 Network capability exposure
S1-153151	Huawei, NEC, DT, ALU	E2E Resource Allocation and QoS Guarantee
S1-153152	LG Electronics	Diversified Connectivity
S1-153153	QUALCOMM Incorporated	SMARTER: Use case for multiple services with different subscriptions
S1-153154	Vodafone/Rapporteur	Grouping of use cases into families
S1-153155	Dish Network	New SMARTER use case on Multi-Connectivity and Service Sharing across operators
S1-153156	Huawei Tech.(UK) Co., Ltd	Revision of S1-152245 use case for moving ambulance and bio-connectivity
S1-153157	Huawei Tech.(UK) Co., Ltd	Revision of S1-152246 use case for on-demand deployment of physical access network infrastructure
S1-153158	III	Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)
S1-153159	ETRI	eMVNO Service Providing Spectrum Sharing and Waveform Transparency
S1-153160	IAESI, THALES	Flexible spectrum access
S1-153161	Huawei, Hisilicon, China Telecom, Sony, Gemalto, ETRI, China Unicom, Deutsche Telekom, SK Telecom, China Mobile, Intel	SMARTER Use Case for Wearable Device Charging
S1-153162	ZTE Corporation, ETRI, Ministry of Interior, France , China Telecom,China Unicom, Huawei	Use case for Emergency assistant transmission by normal UE
S1-153163	Dish Network	New SMARTER Use Case on support for flexible broadcast content caching in 3GPP
S1-153164	Deutsche Telekom	Network Slicing Roaming Use Case
S1-153165	Dish Network	New SMARTER Use Case on support for broadcast service
S1-153166	Dish Network	New SMARTER Use Case on support for flexible broadcast content caching in 3GPP
S1-153167	Nokia Networks Oy	Proposed new use case on WLL
S1-153168	Dish Network	New SMARTER Use Case for 5G Connectivity using satellites
S1-153169	HUAWEI TECHNOLOGIES Co. Ltd.	Discuss grouping of SMARTER requirements
S1-153170	Alcatel-Lucent	FS_SMARTER considerations on requirements grouping
S1-153171	Vodafone/Rapporteur	Grouping of use cases into families
S1-153172	VODAFONE Group Plc	Study on New Services and Markets Technology Enablers - massive Internet Of Things
S1-153173	Nokia Networks Oy	Study on SMARTER Reliable Communications
S1-153174	HUAWEI TECHNOLOGIES Co. Ltd., LG	Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband
S1-153175	Giesecke & Devrient, Morpho, Gemalto, Oberthur Technologies, Sprint	Use case device theft prevention
S1-153176	China Mobile Com. Corporation	Study on New Services and Markets Technology Enablers - Network operation
S1-153177	VODAFONE Group Plc	TR Skeleton mIOT
S1-153178	Nokia Networks Oy	Proposed structure for the dedicated TRs
S1-153179	Giesecke & Devrient, Morpho, Gemalto, Oberthur Technologies	service related subscription management
S1-153180	LG Electronics France, Huwaei	TR Skeleton Enhanced Mobile Broadband (eMBB)
S1-153181	China Mobile Com. Corporation	TR Skeleton NO
S1-153182	China Mobile Com. Corporation	Introduction and Scope for NO TR
S1-153183	China Mobile Com. Corporation	Study on New Services and Markets Technology Enablers - Network operation
S1-153184	VODAFONE Group Plc	Study on New Services and Markets Technology Enablers - massive Internet Of Things
S1-153185	Rapporteur (Nokia Networks)	Skeleton for CriC TR
S1-153186	Rapporteur (Nokia Networks)	Scope and Introduction for CriC
S1-153187	VODAFONE Group Plc	Introduction and Scope for mIOT TR
S1-153188	Rapporteur (VODAFONE Group Plc)	TR 22.7xx v.0.1.0 on (vertical) Massive Internet of Things (mIoT)
S1-153189	Rapporteur (Huawei)	TR 22.7xx v.0.1.0 on (vertical) Enhanced Mobile Broadband (eMBB)
S1-153190	Rapporteur (Nokia Networks)	TR 22.7xx v.0.1.0 on (vertical) Criticial Communications (CriC)
S1-153191	Rapporteur (China Mobile Com. Corporation)	TR 22.7xx v.0.1.0 on (horizontal) NEO (Network Operation)
S1-153192	IAESI, THALES	Up-date of clause 5.1 “Ultra-reliable communications”
S1-153193	Giesecke & Devrient, Gemalto, Morpho, Oberthur Technologies, TeliaSonera, Alcatel-Lucent, Intel	Addition of security requirements to use case 5.1
S1-153194	Huawei, Hisilicon, China Telecom, Sony, Gemalto, Intel, ETRI, MediaTekMTK, ZTE, China Unicom, SK Telecom, ITRI, China Mobile, LGE	Update the Wearable Device Communication use case in SMARTER
S1-153195	IAESI, THALES, GM Onstar	Update of clause 5.33 “Connected vehicles”
S1-153196	ITRI	Update to clause 5.49 Network capability exposure
S1-153197	Giesecke & Devrient, Morpho, Gemalto, Oberthur Technologies, Sprint	Use case device theft prevention
S1-153198	HUAWEI TECHNOLOGIES Co. Ltd., LG	Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband
S1-153199	III	Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)
S1-153200	Huawei, Hisilicon, China Telecom, Sony, Gemalto, ETRI, China Unicom, Deutsche Telekom, SK Telecom, China Mobile, Intel	SMARTER Use Case for Wearable Device Charging
S1-153201	HUAWEI TECHNOLOGIES Co. Ltd.	Discuss grouping of SMARTER requirements
S1-153202	IAESI, THALES	Update of clause 5.34 “Mobility on demand”
S1-153203	China Mobile Com. Corporation	Study on New Services and Markets Technology Enablers - Network operation
S1-153204	VODAFONE Group Plc	Study on New Services and Markets Technology Enablers - massive Internet Of Things
S1-153205	Nokia Networks Oy	Study on SMARTER Reliable Communications
S1-153206	rapporteur	SMARTER status report

Annex 1.1: TDocs not appearing in the minutes

The following documents were revised before presentation:

Ag. Item	Tdoc number	Source	Title	Summary	Conclusion
3.5	S1-153006	III	Use Case and Requirements for Broadband Direct Air to Ground Communications (DA2GC)	According to ITU-R M.2282-0, a broadband Direct-Air-to-Ground Communications (DA2GC) system constitutes an application for various types of telecommunication services, such as Internet access and mobile multimedia services, during flights. The connection with the flight passengers’ user terminals on board aircraft is realized by already available mobile communication systems on board aircraft. The main application field would be Air Passenger Communications (APC). In addition, a broadband DA2GC system could also support Airline Administrative Communications services (AAC) and thus improve aircraft operation, resulting, in particular, in reduced Operational Expenditure (OPEX) for the airlines. Safety-relevant communications such as Air Traffic Control (ATC) and related services are not intended to be covered. In the past, Boring flights with a slow Internet connection or no connection at all are over. 5G technology should be able provide a reliable Internet connection on aircrafts,	Revised to S1-153123
3.4	S1-153009	NEC	Resolving editor's note on use case 5.21 (IoT Device Initialization)	This contribution tries to find agreement on the potential service requirements of use case 5.21 (IoT Device Initialization)	Revised to S1-153104
3.6	S1-153011	ETRI	Proposed Diagram for SMARTER Service	we propose to use following figure in section 4. Overview of TR22.891 to help understating the service concept and 3GPP direction of next generation mobile service.	Revised to S1-153098
3.4	S1-153022	ZTE Corporation	update Coexistence with legacy systems to support legacy device	It is proposed to update the coexistence with legacy systems to support legacy devices	Revised to S1-153100
3.5	S1-153024	ZTE Corporation	Use case for Emergency assistant transmission by normal UE	This contribution proposes a new use case that the user who is in emergency condition can transmit help signal through normal UE not only depend on the professional rescue equipment which will great help the user to be rescued from the emergency more quickly than before	Revised to S1-153101
3.5	S1-153027	Deutsche Telekom	Network Slicing Roaming Use Case	New use case describing the basic requirements for network slices in case of roaming.	Revised to S1-153103
3.1	S1-153040	HUAWEI TECHNOLOGIES Co. Ltd.	Discuss grouping of SMARTER requirements	Revised to S1-153099
3.5	S1-153056	Dish Network	New SMARTER Use Case on support for broadcast service	This submission proposes a new use case related to broadcast/multicast service delivery via a dedicated radio carrier	Revised to S1-153105
3.5	S1-153057	Dish Network	New SMARTER Use Case on support for flexible broadcast content caching in 3GPP	This submission proposes a new use case for support of caching of broadcast content in 3GPP system and efficient delivery of the cached broadcast content to the users	Revised to S1-153106
3.5	S1-153062	Dish Network	New SMARTER use case on Multi-Connectivity and Service Sharing across operators	This submission proposes a new use case related to end user multi-connectivity and sharing of services across multiple network operators.	Revised to S1-153107
3.2	S1-153063	LG Electronics France	Study on New Services and Markets Technology Enablers - High Mobility and Vehicular Services (HiV2X)	There is Rel-14 V2X study and work going on and some "High mobility and Vehicular service" use cases were also proposed in FS-SMARTER. There is some need to make an alignment between Rel-14 V2X Study/Work and FS_SMARTER-based high-mobility and vehicular use cases. This paper is intended to make a proposal on a way forward for what to do next about high mobility and vehicular use cases based on what was reflected in SMARTER TR.	Revised to S1-153102
3.4	S1-153085	Alcatel-Lucent	FS_SMARTER cost clean up	Revised to S1-153122
3.5	S1-153093	Dish Network	New SMARTER Use Case for 5G Connectivity using satellites	Revised to S1-153108
3.2	S1-153102	LG Electronics France	Study on New Services and Markets Technology Enablers - High Mobility and Vehicular Services (HiV2X)	Revision of S1-153063	Revised to S1-153113
3.5	S1-153106	Dish Network	New SMARTER Use Case on support for flexible broadcast content caching in 3GPP	Revision of S1-153057	Revised to S1-153163

The following tdoc were withdrawn:

tdoc number	Source	Title	Summary	Conclusion
S1-153025	HUAWEI	Low-delay video coding	This proposes potential requirement for 3GPP system to support video with transfer bandwidth and very low one-way service latency.	Withdrawn
S1-153044	Nokia Networks Oy	General clean-up of TR 22.891	General clean-up of TR 22.891	Withdrawn
S1-153065	LG Electronics France	Introduction and Scope for HiV2X	Initial input proposal for TR regarding the newly proposed BB of "High Mobility and Vehicular use cases"	Withdrawn.
S1-153082	Huawei Tech.(UK) Co., Ltd	use case of idle mode mobility support for ultra-light mobile devices	Withdrawn

Annex 2: Void

Annex 3: Void

Annex 4: Agreed WIDs

Tdoc #	Source	Title	Spec	Conclusion
S1-153198	HUAWEI TECHNOLOGIES Co. Ltd., LG	Study New Services and Markets Technology Enablers - on enhanced Mobile Broadband	WID	Agreed.
S1-153203	China Mobile Com. Corporation	Study on New Services and Markets Technology Enablers - Network operation	WID	Agreed.
S1-153204	VODAFONE Group Plc	Study on New Services and Markets Technology Enablers - massive Internet Of Things	WID	Agreed.
S1-153205	Nokia Networks Oy	Study on SMARTER Reliable Communications	WID	Agreed.

Annex 5: New versions of Draft TSs/TRs and cover pages

Tdoc #	Source	Title
S1-153188	Rapporteur (VODAFONE Group Plc)	TR 22.7xx v.0.1.0 on (vertical) Massive Internet of Things (mIoT)
S1-153189	Rapporteur (Huawei)	TR 22.7xx v.0.1.0 on (vertical) Enhanced Mobile Broadband (eMBB)
S1-153190	Rapporteur (Nokia Networks)	TR 22.7xx v.0.1.0 on (vertical) Criticial Communications (CriC)
S1-153191	Rapporteur (China Mobile Com. Corporation)	TR 22.7xx v.0.1.0 on (horizontal) NEO (Network Operation)
S1-153003	Rapporteur (Vodafone)	TR 22.891 on FS_SMARTER v1.0.0 (SP-150562)

Annex 6: Participants list

To be provided