3GPP TSG-SA WG1 Meeting #73
Okinawa, Japan, 1-5 January 2016
tdoc list SA1#73 draft Thursday 4th Feb 12.30 PM
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.
Sort by "order" (specifying a sort by "text" and not "number") to list the tdocs by agenda items.
Order
Ag.Item Tdoc #
010101
010102
1.1
1.1
S1-160000 Chair
S1-160001 Chair
010103
1.1
S1-160002 Chair
030001
3
S1-160003 Chair
SA1-related topics at SA#70
report
010301
1.3
1.3
9.1
S1-160004 ETSI
S1-160005 ETSI
S1-160006 ETSI
7.4
8.4
S1-160007 III
Draft minutes of SA1#72
Minutes of SA1#72
Extract of the 3GPP Work Plan
for SA1#73
Updating Potential
Requirements of Higher User
Mobility Use Case
report
report
Work
Plan
pCR
0.2.0
7.4
8.1
S1-160008 III
Updated Bandwidth
Requirements for BDA2GC
22.891
1.2.0
7.4
8.1
S1-160009 III
Updated Mobility Requirements 22.891
for BDA2GC
1.2.0
-1
8.2
S1-160010 III
Text proposal of traffic scenario pCR
3
0.2.0
Source
Title
Draft agenda for SA1#73
Draft Schedule and Agenda
with document allocation for
SA1#73
Final Schedule and Agenda
with document allocation for
SA1#73
1
Type/S CR#
pec
agenda
agenda
cat Versio Rel
n in
WI
Summary
Discussion
Conclusion
Revised to S1-160001.
Revised to S1-160002.
agenda
Nokia Networks pointed out that some Agreed.
delegates might end up working long
hours and the meeting chair has to take
this into account, in particular to allow
all the delegates to have proper break
time, in particular when considering
that the meeting location is quite
remote.
The chair reminded that the number of
documents is the key factor to
determine the meeting time.
Nokia Networks answered that the
delegates' health is also a key
parameter, and it is not because some
groups are working on very bad hours
that SA1 has to do the same.
The CR on "Data off" was not pursued. Agreed.
All other SA1 material was approved.
Open until Thursday
This paper proposes text for
updating potential
requirements of existing
higher user mobility use case
for TR 22.863 V0.2.0.
This paper proposes updating
Bandwidth Requirements of
existing use case for
Broadband Direct Air to
Ground Communications
(BDA2GC).
This paper proposes updating
Pre-conditions and Mobility
Requirements of existing use
case for Broadband Direct
Air to Ground
Communications (BDA2GC).
In TR22.861 V0.2.0, it
descripts 5 type traffic
scenario of IoT, the traffic
Merged into S1160044.
Merged into S1160044.
Merged into S1160044.
Revised to S1-160290
Text Proposal of Connectivity
aspects
pCR
0.2.0
scenario 3 of an IoT device
which is connected with
network via a relay UE in the
roaming case. It didn’t
consider that UE and IoT
device are roaming, so this
contribution has addition a
new part of traffic scenario 3.
In TR22.861 V0.2.0 [1], it
descripts connectivity aspects
of IoT, The various
combinations of these
connectivity scenarios should
consider to switch relayed
connection of 3GPP RAT or
non 3GPP RAT to the
network, based on the
consider that this contribution
has some addition of the
section.
This CR contribution
removes Stage 1 requirements
from MCPTT TS 22.179 V
13.3.0 (2015-12) that are held
in common with MCVideo
and/or MCData for placement
into a separate MCCoRe Rel14 specification.
This contribution proposes a
TS 22.280 for MCCoRe
Release 14. This TS is
provided as the basis for
3GPP SA1 to consolidate
requirements that are found to
be common between
MCPTT, MCVideo, and
MCData into a single
specification.
This document proposes
some clarificaitons on the
editor’s note in section 5.4 of
TR Critical Communications
and suggests text change
accordingly.
-1
8.2
S1-160011 III
070601
7.6
S1-160012 U.S. Department of Mission Critical Push to Talk
Commerce
over LTE Realignment
(MCPTT-R)
22.179 0036
070501
7.5
S1-160013 U.S. Department of TS 22.280 Mission Critical
Commerce
Services Common
Requirements (MCCoRe)
other
8.3
S1-160014 ETRI
Proposed Text clean-up for
Critical Communications
pCR
070404
7.4
Proposal for V2XLTE
Requirements grouping
discuss
ion
070421
7.4
071007
4
S1-160015 FUJITSU
Laboratories of
Europe
S1-160016 FUJITSU
Laboratories of
Europe
S1-160017 ORANGE
Reply LS on Data Off
Requirements
LS out
070510
7.5
S1-160018 MoI, France
pCR
Revised to S1-160435
070506
7.5
S1-160019 MoI, France
pCR
Revised to S1-160431
070808
7.8
S1-160020 MoI, France
pCR
Revised to S1-160459
070810
7.8
S1-160021 MoI, France
pCR
Revised to S1-160341
070804
7.8
S1-160022 MoI, France
MCCoRe Air ground air
communications
MCCoRe Mobility and priority
requirements
MCData Location sharing and
data forwarding
MCData Data base enquiries
and internet access
MCData air ground air
pCR
Noted.
C 13.3.0 Rel-14 MCImpMCPTTR
MCImpMCCoRe
Revised to S1-160313
Revised to S11600254.
Noted.
Proposal for inclusion in section discuss
5.2.4 of V2XLTE TS
ion
2
Revised to S1-160291
Revised and merged
into 407
Proposed SA1 reply LS to
GSMA NG RiLTE on the
progress on Data Off WID in
3GPP SA1
Revised to S1-160316
communications
MCData conversation
management
MCData enhanced presence
MCData external interfaces
MCData in IOPS mode
MCData robots requirements
MCVideo performances and
quality requirements
MCVideo Air ground air
MCVideo enhanced presence
MCVideo external interfaces
MCVideo in IOPS mode
MCVideo parameters remote
control
MCVideo profile management
070805
7.8
S1-160023 MoI, France
070809
070812
070811
070807
070727
7.8
7.8
7.8
7.8
7.7
S1-160024
S1-160025
S1-160026
S1-160027
S1-160028
MoI, France
MoI, France
MoI, France
MoI, France
MoI, France
070718
070719
070728
070726
070704
7.7
7.7
7.7
7.7
7.7
S1-160029
S1-160030
S1-160031
S1-160032
S1-160033
MoI, France
MoI, France
MoI, France
MoI, France
MoI, France
070716
7.7
S1-160034 MoI, France
070720
070721
7.7
7.7
S1-160035 MoI, France
S1-160036 MoI, France
070722
070711
7.7
7.7
S1-160037
S1-160038
070723
070712
7.7
7.7
S1-160039
S1-160040
070715
080103
7.7
8.1
S1-160041
S1-160042
8.2
S1-160043 VODAFONE Group Update to Section 4 of MIoT
Plc
TR
pCR
8.4
S1-160044 VODAFONE Group Update to “Higher User
Plc
Mobility” of eMBB TR
pCR
8.2
S1-160045 ZTE Corporation
FS_SMARTER-mIoT clean up pCR
section 5.2.1
8.2
S1-160046 ZTE Corporation
FS_SMARTER-mIoT clean up pCR
section 5.2.2
8.2
S1-160047 ZTE Corporation
FS_SMARTER-mIoT clean up pCR
section 5.2.3
8.5
S1-160048 ZTE Corporation
FS_SMARTER-NEO network
slice clean up
pCR
8.5
S1-160049 ZTE Corporation
FS_SMARTER-NEO network
capability exposure clean up
pCR
6
S1-160050 ORANGE
MMTEL R13 correction
22.173 0105
-1
060001
MCVideo push and pull
MCVideo video availability
notifications
MoI, France
MCVideo video consultation
MoI, France
MCVIdeo video remote control
including camera discovery
MoI, France
MCVideo video storage control
MoI, France
MCVideo video processing
capabilities
MoI, FRance
MCVideo robots
VODAFONE Group MIoT related updates to Section
Plc
6.2 of SMARTER TR
3
pCR
Revised to S1-160453
pCR
pCR
pCR
pCR
pCR
Revised to S1-160340
Revised to S1-160342
Agreed.
Revised to S1-160454
Revised to S1-160443
pCR
pCR
pCR
pCR
pCR
Noted.
Revised to S1-160349
Revised to S1-160462
Agreed.
Revised to S1-160440
pCR
pCR
pCR
Revised and merged
into 345
Revised to S1-160447
Agreed.
pCR
pCR
Revised to S1-160460
Revised to S1-160444
pCR
pCR
Revised to S1-160461
Revised to S1-160445
pCR
pCR
Revised to S1-160348
This document discusses the
Agreed.
necessary updates to Section
6.2 of TR 22.891, and group
the use cases into the
corresponding key families in
MIoT as analysed.
This document provides the
updates to Section 4 of MIoT
TR 22.861.
This document provides the
Revised to S1-160280
updates to Section 5.4 of
eMBB TR 22.863.
This document proposes text
to clean up the section 5.2.1
in mIoT TR.
This document proposes text
to clean up the section 5.2.2
in mIoT TR.
This document proposes text
to align the potential
requirements with the
description and traffic
scenarios in section5.2
This document proposes to
clean up the network slices
description and potential
requirements in NEO TR
This document proposes to
clean up the network
capability exposure
description and potential
requirements in NEO TR
A reference is corrected (the This mistake is also in previous
Revised to S1-160304
reference 8.2.7.2.5 is replaced Releases.
by the reference 8.2.7.3.5.)
The "Clause affected" is to be provided.
F 13.1.0 Rel-14 TEI13
060002
7.11
S1-160051 ORANGE
MMTEL correction
-1
8.5
S1-160052 ORANGE
Contribution concerning access pCR
to the network in low-ARPU
areas in TR NEO TR v0.2.0
071109
7.9
S1-160053 Huawei
Technologies
3GPP enhancement for TV
application support
22.101 0507
B 14.1.0 Rel-14 EnTV
071113
7.9
7.7
CR22115 Charging requirement 22.115 0079
for TV application support
MCVideo - Proposed
pCR
descriptive text
B 13.3.0 Rel-14 EnTV
070703
S1-160054 Huawei Tech.(UK)
Co., Ltd
S1-160055 HOME OFFICE
070701
7.7
S1-160056 HOME OFFICE
MCVideo - Proposed
requirements restructure
pCR
070706
7.7
S1-160057 HOME OFFICE
MCVideo - Clarification of
requirements
pCR
070707
7.7
S1-160058 HOME OFFICE
pCR
070708
7.7
S1-160059 HOME OFFICE
070709
7.7
S1-160060 HOME OFFICE
070710
7.7
S1-160061 HOME OFFICE
070504
7.5
S1-160062 HOME OFFICE
070508
7.5
S1-160063 HOME OFFICE
070419
7.4
S1-160064 Huawei
MCVideo - Proposed new
requirements for video coding
MCVideo - Proposed new
requirements for video modes
MCVideo - Proposed new
requirements for video
performance
MCVideo - Proposed new
requirements for remote PTZ
control
MCCoRe - Proposed new
section for interworking
MCCoRe - Proposed
explanation of intent of wording
Text Proposal for Overall
Service Requirements for V2X
TS
070420
7.4
S1-160065 Huawei
Text Proposal for Specific
pCR
Service Requirements for V2X
TS
070408
7.4
S1-160066 Huawei
Text Proposal for Definitions
for V2X TS
4
22.173 0106
pCR
pCR
pCR
pCR
pCR
pCR
pCR
F 14.0.0 Rel-14
TEI14
The title should be more precise.
This is a mirror CR. It should Same comments as the previous one.
be category A, WI is TEI13.
The contribution proposes a
set of requirements concernig
the access to the network in
low-ARPU areas where there
is a need for providing access
to essential services with a
basic Internet access.
Introduce new requirements
for 3GPP enhancement for
TV application support in
TS22.101
Charging requirement for TV
application support addition
Text proposal to be added in
section 4 of MCVideo to
describe the service.
Proposal for restructuring of
requirements section for
MCVideo to "build out" the
service after MCCoRe
Proposes changes to
requirements for various
reasons - to make them
unambiguous, - to separate
requirements, - some editorial
changes
New proposed video coding
requirements for MCVideo
Proposed new requirements
for video modes in MCVideo
Proposed new requirements
for video performance in
MCVIdeo
Proposed new requirements
for remote PTZ control in
MCVideo
Proposed new section for
interworking in MCCoRe
Proposed explanation of
intent of wording in MCCoRe
This contribution proposes
V2X overall requirements
describing common service
requirements that apply for
all V2V/V2I/V2P/V2N use
cases, including requirements
for message transfer, interPLMN, and control aspects.
This contribution proposes
V2X specific service
requirements including
latency, message size,
transmission frequency,
range, speed, and some other
requirements are added to
support V2V/V2I/V2P/V2N
use cases.
This contribution proposes
the definitions of RSU and
V2N/V2X Services inline
Revised to S1-160305
Revised to S1-160278
Merged into S1160330
Revised to S1-160339
Revised to S1-160439
Revised to S1-160437
Divided into several;
Merged with 033, 440,
445, respectively
Revised to S1-160441
Revised to S1-160442
Merged with 028 into
443
Merged with 038 into
444;
Revised to S1-160430
Revised to S1-160433
Revised and merged
into 407
Revised and merged
into 407
Revised into S1160401
070414
7.4
S1-160067 Huawei
Text Proposal for Overview for pCR
V2X TS
070423
7.4
S1-160068 Huawei
Text proposal for Security
Requirements for V2X TS
8.2
S1-160069 Huawei Device Co., Update sevice continutiy for
Ltd
IoT devices in MIoT TR
22.891
1.2.0
FS_SMA
RTERmIoT
8.2
S1-160070 Huawei Device Co., Update the subscription
Ltd
requirement for IoT devices in
MIoT TR
22.891
1.2.0
FS_SMA
RTERmIoT
8.2
S1-160071 Huawei Device Co., Update pairing requirement in
Ltd
MIoT TR
22.891
1.2.0
FS_SMA
RTERmIoT
8.2
S1-160072 Huawei Device Co., Update the KPI for services in
Ltd
traffic scenarios in MIoT TR
22.891
1.2.0
FS_SMA
RTERmIoT
070713
7.7
S1-160073 HOME OFFICE
pCR
070714
7.7
S1-160074 HOME OFFICE
070724
7.7
S1-160075 HOME OFFICE
070507
7.5
S1-160076 Harris Corporation
5
MCVideo - Proposed new
requirements for leaving a
video stream
MCVideo - Proposed new
requirements for forwarding a
video stream
MCVideo - Proposed new
requirements for configuring
external video capabilities
MCCoRe - Proposed new
common requirements for
Emergency and Imminent Peril
pCR
pCR
pCR
pCR
with the current TR, except to
clarify RSU can support V2X
applications and 3GPP
dealing with only transport
rather than application layer.
This contribution proposes
decription text for the
Overview section inline with
the current TR, except adding
one figure to illustrate
broadcast-type V2V
communications.
This contribution proposes to
capture security-related
service requirements for V2X
as a separate subsection under
Section 5, covering
authorization, anominity,
integrity protection, as well as
privacy.
This contribution is to update
the part of service continuity
for IoT devices of
Connectivity Aspects family
in Massive Internet of Things
TR, including traffic
scenarios and potential
requirements.
This contribution is to update
the requirement of identities
and subscriptions for IoT
devices and delete the relative
editor’s note of Connectivity
Aspects family in Massive
Internet of Things TR.
This contribution is to update
the requirement of pairing for
IoT devices and delete the
relative editor’s note of
Connectivity Aspects family
in Massive Internet of Things
TR.
This contribution is to update
the KPI for services in traffic
scenarios for IoT devices in
Massive Internet of Things
TR.
Proposed new requirements
for leaving a video stream in
MCVideo
Proposed new requirements
for forwarding a video stream
in MCVideo
Proposed new requirements
for configuring external video
capabilities in MCVideo
Emergency and Imminent
Peril are common mission
critical services. General
requirements are proposed
that describe what application
services are invoked when
emergency or imminent peril
Revised to S1-160404
Revised and merged
into 407
Revised to S1-160343
Agreed.
Revised to S1-160347
Revised to S1-160432
070802
7.8
S1-160077 HOME OFFICE
070801
7.8
070702
7.7
S1-160078 MINISTERE DE
L'INTERIEUR
S1-160079 MINISTERE DE
L'INTERIEUR
S1-160080 Applied
Communication
Sciences
8.3
communications are initiated.
Inclusion of Generic
capabilities into MCData as
per agreement at SA1-#72
MCData pCR on inclusion of pCR
Generic capabilities into
MCData
MCData definitions and
pCR
overview
MCVideo Scope and definitions pCR
Addition of MPS in
FS_SMARTER-CRIC Ultrareliable communications use
case
pCR
Revised to S1-160450
Revised to S1-160438
0.2.0
080109
8.1
S1-160081 Applied
Communication
Sciences
Inclusion of MPS in Table 5.1.3 pCR
of TR 22.891 (FS_SMARTER)
071102
7.1
Text alignment for terminating 22.153 0029
UE option
F 14.2.0 Rel-14
071103
7.1
Update to Priority Data Bearer 22.153 0030
Service
F 14.2.0 Rel-14
071104
7.1
S1-160082 Applied
Communication
Sciences
S1-160083 Applied
Communication
Sciences
S1-160084 Applied
Communication
Sciences
MPS Anonymity Requirement
22.153 0031
B 14.2.0 Rel-14
071001
7.10
S1-160085 Applied
Communication
Sciences, OEC, TMobile US, AT&T
MPS exemption when PS Data 22.011 0227
Off is enabled in the UE
C 14.1.0 Rel-14
080110
8.1
S1-160086 HUAWEI
TECHNOLOGIES
Co. Ltd.
FS_SMARTER 5.74 Updates pCR
to QoS and Policy Control Use
Case
070405
7.4
S1-160087 LG Electronics
070406
7.4
070412
7.4
070415
7.4
070403
7.4
070416
7.4
S1-160088 Rapporteur (LG
Electronics)
S1-160089 Rapporteur (LG
Electronics)
S1-160090 Rapporteur (LG
Electronics)
S1-160091 Rapporteur (LG
Electronics)
S1-160092 LG Electronics
Proposed text for Introduction
section for V2X TS
Proposed text for Scope section
for V2X TS
Proposed text for Reference
section for V2X TS
Proposed text for overview
section for V2X TS
Proposed change to section 5
structure
Discussion on CPR review
070417
070418
7.4
7.4
070409
7.4
S1-160093 LG Electronics
S1-160094 Rapporteur (LG
Electronics)
S1-160095 LG Electronics
070411
7.4
S1-160096 LGE
discuss
ion
CR to TR22.885 on CPR update 22.885 0001
Proposed text for requirement pCR
section for V2X TS
Discussion on V2X definition discuss
ion
Corrections to V2X Definition 22.885 0002
070410
7.4
S1-160097 Rapporteur (LG
Electronics)
Proposed text for Definition and pCR
Abbreviation section for V2X
6
Revised to S1-160451
This document proposes
inclusion of MPS in the list of
mission critical services in
clause 5.1.2.3 (Ultra-reliable
communications) of
FS_SMARTER-CRIC
consistent with clause 5.1 of
TR 22.891.
This document proposes
inclusion of MPS text in
Table 5.1.3 of TR 22.891 for
completeness.
Text alignment for
terminating UE option in TS
22.153 clause 5.4
This CR updates Priority
Data Bearer service to align
with Stage 2 in TS 23.401.
This CR proposes a
requirement for anonymity
protection of MPS
communication when
required.
PS_DAT Proposed text addition in
A_OFF clause 10 of TS 22.011
indicating that Emergency
and MPS shall be exempt
from PS Data Off.
This document proposes
updates to QoS and Policy
Control use case in clause
5.74 of TR 22.891 for access
agnostic QoS & policy
framework and E2E QoS.
Agreed.
Revised to S1-160332
Revised to S1-160333
Revised to S1-160334
Revised to S1-160318
pCR
Noted.
pCR
Revised to S1-160400
pCR
Revised to S1-160403
pCR
Revised to S1-160404
pCR
Noted
Noted.
F 14.0.0 Rel-14
F 14.0.0 Rel-14 FS_V2X
LTE
Revised to S1-160406
Revised to S1-160407
Revised into S1160401
Revised to S1-160402
Revised to S1-160401
8.2
TS
Clarification on mIOT family
-1
8.2
S1-160098 LG Electronics,
Huawei, Intel
S1-160099 LG Electronics,
Sony, Intel
S1-160100 LG Electronics
-1
8.2
S1-160101 LG Electronics
8.3
S1-160102 LG Electronics
070407
7.4
S1-160103 CATT
070413
7.4
S1-160104 CATT
080113
8.1
S1-160105 China
FS_SMARTER: RF sharing
Telecommunications
S1-160106 Dish Network
Proposal to add text on 5G
satellite access to TR 22.863
8.2
8.4
050001
pCR
Terminology for mIOT
connection mode
mIoT Traffic Scenario for
operational aspect family
mIoT Traffic Scenario for
connectivity aspect family
Traffic Scenario for Critical
Communication
Proposed text for Scope section
for V2X TS
pCR
Proposed text for Overview
section for V2X TS
pCR
pCR
Revised to S1-160235
pCR
Revised to S1-160236
pCR
pCR
pCR
pCR
8.3
S1-160107 Dish Network
Proposal to add text on satellite pCR
access to FS_SMARTER-CriC
BB TR
8.5
S1-160108 Dish Network
Proposal to add text on user
multi-connectivity across
operators to FS_SMARTERNEO BB TR 22.864
8.5
S1-160109 Dish Network
Proposal to add text on
pCR
broadcast/multicast services
using a dedicated radio carrier
to FS_SMARTER-NEO BB TR
22.864
8.5
S1-160110 Dish Network
pCR
5
Proposal to add text on 5G
satellite access to
FS_SMARTER-NEO BB TR
22.864
S1-160111 LG Electronics Inc. Preparations for eV2X Rel-15
7
This contribution proposes
the text for Introduction and
Scope sections of TS 22.cde
v0.1.0 on Normative Work
for V2X (V2XLTE).
This contribution proposes
the text for Overview section
of TS 22.cde v0.1.0 on
Normative Work for V2X
(V2XLTE).
pCR
discuss
ion
Revised to S1-160400
Revised to S1-160289
Not available.
This document proposes to
add text related to satellite
access use case 5.72 to
FS_SMARTER-eMBB BB
TR 22.863.
This document proposes to
add text related to satellite
use case 5.72 to
FS_SMARTER-Cric BB TR
22.862.
This document proposes to
add text on user multiconnectivity across operators
to FS_SMARTETR-NEO BB
to TR 22.864.
This document proposes to
add text on
broadcast/multicast services
using a dedicated radio
carrier to FS_SMARTERNEO BB TR 22.864.
This document proposes to
add text on satellite use case
5.72 to FS_SMARTER-NEO
BB TR 22.864.
SP-150573 (WID for
V2XLTE) has its target
completion date of 03/2016
and SA1#72 has completed
the Study (FS_V2XLTE)
with a compact set of 33
CPRs (consolidated potential
requirements). This set of
CPRs, which were carefully
chosen by many companies
involved through multiple
iterations of discussions, will
be ready to go for its
Normative form of
requirements in the new TS
Noted.
080102
8.1
S1-160112 LG Electronics Inc. Proposed Changes for
pCR
Overview Section and Diagram
8.3
S1-160113 HUAWEI
TECHNOLOGIES
Co. Ltd.
040004
4
S1-160114 LG Electronics Inc. [DRAFT] Reply LS on ACDC LS out
requirement for IMS services
040002
4
S1-160115 LG Electronics
Correction of ACDC
requirement for IMS services
22.011 228
F 13.4.0 Rel-13 ACDCST1
040003
4
S1-160116 LG Electronics
Correction of ACDC
requirement for IMS services
22.011 0229
A 14.1.0 Rel-14 ACDCST1
050002
5
S1-160117 NTT DOCOMO,
Vodafone
Discussion on the business
motivation behind USOS
discuss
ion
8
FS_SMARTER-CRIC: Low- pCR
delay speech and video coding
22.V2X (Tdoc # not assigned
yet). If the Work (V2XLTE)
is complete at SA1#73, we
will continue to investigate
the issues that have been
discussed in SMARTER and
other issues that have put on
hold due to the Vancouver
working assumption. This
paper intends to provide the
overview on what's done and
what's pending and to kick
off the discussion for
preparation for the next step
in May.
There is a misalignment
between what’s included in
TR 22.891 and the overview
section (Section 4). Based on
what SA1 has agreed since
SA1#71bis, this contribution
proposes to make a suitable
change on the overview
section of the TR.
This document proposes text
to be added for Low-delay
speech and video coding to
the Higher Reliability and
Lower Latency clause of the
SMARTER Critical
Communications TR 22.862.
The text is based on the use
case 5.50 in the SMARTER
TR 22.891.
DRAFT response to C1160793 on ACDC
requirement for IMS services
(Rel-13, 14)
Requirement is corrected that
ACDC shall not apply to
MMTEL voice, MMTEL
video and SMS over IMS
(SMS over IP) only.
Agreed.
Proposed answer to S1-1600220.
Revised to S1-160284
TO be updated to take into account that
the corresponding CRs were revised.
This is to answer to the CT1's request in Revised to S1-160282
S1-160220.
Ericsson mentioned that there are other
possible solutions, e.g. accept this
limitation but only for Rel-13.
Intel, Huwaei and Qualcom support
LG's CR as it is, i.e. not specifically for
Rel-13.
It was wondered if what to do with the
other IMS services should be mentioned
explicitely.
The cover page needs to be updated.
Requirement is corrected that Mirror CR.
Revised to S1-160283
ACDC shall not apply to
MMTEL voice, MMTEL
video and SMS over IMS
(SMS over IP) only.
This document discusses the
Noted.
business motivation behind
USOS. The authors believe
that we need to account for
usage over unlicensed access
in order to set an environment
where LAA could be widely
used in a commercially viable
New Use Case: Public Safety
Lifeline
New Use Case: Public Safety
Situational Awareness
ProSe for the Evolved Packet
System (EPS)
pCR
Ensuring correctness of
requirements for Rel-14
common functionality
pCR
way. We recommend
approval of the proposed
USOS WID and related
CR(s).
0.0.0
Proposed new use case for
public safety
0.0.0
New use case for public
safety
B 13.2.0 Rel-14 TEl14- Introduction service
WI-SA1 requirements for commercial
ProSe UE-to-Network Relay
for the Evolved Packet
System (EPS).
0.0.0
Analyzes current MCPTT
requirements from a
candidate section for core
functionality (location) as an
example on how to
correct/clarify those
requirements as they move to
Rel-14
8.3
S1-160118 Motorola Solutions
8.3
S1-160119 Motorola Solutions
-1
7.11
S1-160120 Huawei, Hisilicon
070509
7.5
S1-160121 Motorola Solutions
070806
7.8
S1-160122 Huawei, TD-Tech
pCR
070511
7.5
S1-160123
pCR
Merged with S1160023.
Revised to S1-160436
070512
7.5
S1-160124
pCR
Merged into 430
070725
7.7
S1-160125
pCR
Revised to S1-160346
070705
7.7
S1-160126
pCR
070717
7.7
S1-160127
Merged with S1160033
Revised to S1-160345
071105
7.3
S1-160128
080108
8.1
S1-160129
-1
5
S1-160130 China Unicom
-1
5
S1-160131 China Unicom
8.5
S1-160132 Gemalto N.V.
8.5
S1-160133 KDDI Corporation
080104
8.1
S1-160134 KDDI Corporation
071005
7
S1-160135 Vodafone,
3GPP PS Data Off
BlackBerry UK Ltd,
Definition of conversation in
MCData
Huawei, TD-Tech
MCService emergency alert
triggered by location
Huawei, TD-Tech
Management of Different
Combination of Voice and Data
Huawei, TD-Tech
Video control by a dispatcher in
MCVideo.
Huawei, TD-Tech
Remote control of MCVideo
UE
Huawei, TD-Tech
MCVideo profile management
and administration
China Unicom, ZTE, Requirements for enhancements
CATR, Huawei
on User Location Reporting
Support
Gemalto N.V.
Multi-RATs <5G>/E-UTRA
RAT capable UE security
considerations
Paging Policy Enhancements
and Procedure Optimizations in
LTE
Paging optimization
requirements in LTE
Security aspects
9
pCR
22.278 0223
pCR
22.101 0508
22.891
B 14.1.0 Rel-14 eULRS
1.2.0
pCR
Update SMARTER-NEO for
pCR
network accessibility in disaster
and security
Update grouping of use cases
pCR
with network accessibility in
disaster
Revised to S1-160434
Revised to S1-160335
<5G system> and E-UTRAN This is covered by S1-160317.
system will coexist for a
certain period of time. In such
situation multiple RATs
capable 5G devices will need
to authenticate over LTE and
such authentication should
not impact the existing LTE
system.
WID
new
22.101 0509
Revised to S1-160292
Noted.
Revised to S1-160287
B 14.1.0
Revised to S1-160288
Security aspects related to
Multi-RATs 5G/E-UTRAN
RAT capable UE.
Based on the agreement of
To be handled after S1-160133.
S1-160133, this contribution
proposes moving UC 5.3
from System flexibility to
Access in TR 22.891.
22.011 0224r5 B 14.1.0 Rel-14 PS_DAT Specific new requirements
CR 0230 was allocated but the author
A_OFF are added for behaviour of the used 0224r5.
Orange.
071006
7
S1-160136 Vodafone,
Addition of Mobile Data and
22.030 0019
BlackBerry UK Ltd, Data Roaming on/off functions
Orange.
to the MMI of Mobile
Equipment.
S1-160137 China Mobile Com. Proposed WID for eFMSS
WID
Corporation
new
050008
5
050009
5
S1-160138 China Mobile
999999
8.5
071107
7.9
S1-160139 China Mobile Com. NEO TR clean up
Corporation
S1-160140 Ericsson LM
Clarifies that TV service can
use both unicast and broadcast
071108
7.9
S1-160141 Ericsson LM
071110
7.9
S1-160142 Ericsson LM
080101
8.1
080105
8.1
S1-160143 Nokia Networks,
Alcatel-Lucent,
Vodafone,
MediaTek, Deutsche
Telekom, NEC,
Telecom Italia, Sony
S1-160144 Nokia Networks,
New title (and implied scope)
Alcatel-Lucent
for one CriC use case family
080106
8.1
S1-160145 Nokia Networks,
Alcatel-Lucent
Proposed family allocation for
recent eMBB use cases
8.3
S1-160146 Nokia Networks,
Alcatel-Lucent
Updates to title page for TR on pCR
CriC
Requirements for supporting
third party owned (S)Gi-LAN
service
10
22.105 0058
3GPP system when 3GPP Better titles should be used.
PS Data Off is configured by
the HPLMN
B 13.0.0 Rel-14 PS_DAT Specific new requirements for
A_OFF the Mobile Data and Mobile
Data when Roaming
functions are added.
The objective is to enhance
flexible mobile service
steering requirements
developed in Rel-13 for
supporting third party owned
(S)Gi-LAN service.
Requirements that will be
considered include:
• The 3GPP core network
shall be able to apply traffic
steering policies for the third
party’s owned (S)Gi-LAN
service functions.
• The 3GPP core network
shall be able to collect
accounting information to
support accounting between
operator and the third party
service provider.
B 13.0.0 Rel-14 eFMSS This CR goes with the WID It was requested as CR#0058 against
in S1-1600137.
22.105. It is now meant to be on
22.101.
Withdrawn, replaced by S1-160302.
pCR
F 14.0.0 Rel-14 FS_EnT
V
New use case: Hybrid TV
22.816 0002
delivery
Requirements for enhanced TV 22.101 0510
service
Completion of TR 22.891
22.891
B 14.0.0 Rel-14 FS_EnT
V
B 14.1.0
EnTV
22.891
Revised to S1-160301
Withdrawn.
Withdrawn
22.816 0001
22.891
Revised to S1-160315
This CR clarifies that the TV
service can be delivered with
both unicast as well as
broadcast.
FS_SMA This document proposes to
RTER
complete TR 22.891 at this
SA1 meeting.
Revised to S1-160336
Revised to S1-160337
Merged into S1160330
There is an agreement in general. Some Revised to S1-160317
rewording is needed.
FS_SMA This document proposes to
Agreed.
RTER
modify the title (and implied
scope) one use case family
related to CriC.
"Higher reliability, higher
availability" to be renamed
into "Higher availability".
FS_SMA This document proposes a
It is agreed that if a use case is allocated Agreed
RTER
family allocation for recent to a particular family, it does not mean
eMBB use cases.
that all the requirements of the family
apply to this particular use case.
It just mean that the use case is
considered to belong to this particular
family for some of its aspects.
FS_SMA This document proposes to
RTER- update the title page for TR
CRIC
on CriC.
8.3
S1-160147 Nokia Networks,
Alcatel-Lucent
Updates to scope and
definitions to TR on CriC
pCR
8.3
S1-160148 Nokia Networks,
Alcatel-Lucent
Miscellaneous corrections to
TR on CriC
pCR
8.3
S1-160149 Nokia Networks,
Alcatel-Lucent
Adding description for use case pCR
family on Higher availability
and lower latency to TR on
CriC
8.3
S1-160150 Nokia Networks,
Alcatel-Lucent
Adding description for use case pCR
family on Higher reliability,
higher availability and lower
latency to TR on CriC
FS_SMA
RTERCRIC
8.3
S1-160151 Nokia Networks,
Alcatel-Lucent
Adding description for use case pCR
family on Very low latency to
TR on CriC
FS_SMA
RTERCRIC
8.3
S1-160152 Nokia Networks,
Alcatel-Lucent
Adding description for use case pCR
family on Higher accuracy
positioning to TR on CriC
FS_SMA
RTERCRIC
8.3
S1-160153 Nokia Networks,
Alcatel-Lucent
Adding new use case family to pCR
TR on CriC
FS_SMA
RTERCRIC
8.4
S1-160154 Nokia Networks,
Alcatel-Lucent
Proposal to add text on WLL to pCR
TR 22.863
8.5
S1-160155 Nokia Networks,
Alcatel-Lucent
Proposal to add text on WLL to pCR
TR 22.864
FS_SMA
RTEReMBB
FS_SMA
RTERNEO
8.5
S1-160156 ORANGE
Legal and regulatory
obligations
pCR
080111
8.1
8.1
On-demand dynamic
deployment of physical access
network infrastructure
Change eMBB 5.32 family
allocation to High Density
pCR
080107
S1-160157 HUAWEI
TECHNOLOGIES
Co. Ltd.
S1-160158 HUAWEI
TECHNOLOGIES
Co. Ltd.
S1-160159 HUAWEI
TECHNOLOGIES
Co. Ltd.
eMBB: Move use case 5.32 to
Higher Density family and
clarify speed TBD values
pCR
8.4
11
pCR
FS_SMA
RTERCRIC
FS_SMA
RTERCRIC
FS_SMA
RTERCRIC
This document proposes to
update the scope and
definitions of TR on CriC.
This document proposes
miscellaneous corrections to
TR on CriC.
This document proposes to
add description for use case
family on "Higher availability
and lower latency" to TR on
CriC.
This document proposes to
add description for use case
family on "Higher reliability,
higher availability and lower
latency" to TR on CriC.
This document proposes to
add description for use case
family on "Very low latency"
to TR on CriC.
This document proposes to
add a general description for
use case family on "Higher
accuracy positioning" to TR
on CriC
This document proposes to
add a new use case family to
TR on CriC, as agreed at
SA1#72.
This document proposes to
add text on WLL to TR
22.863.
This document proposes to
add text on WLL to TR
22.864.
This contribution proposes a
set of requirements on Lawful
Interception for 5G Networks
Proposes new consideration The impact on 3GPP's work is not clear Noted.
for Nomadic networks for
for Alcatel-Lucent.
SMARTER
There is no consensus at this time.
This document moves 5.32
from eMBB Higher Mobility
family to eMBB Higher
Density family.
This document moves the use
case 5.32 “Improvement of
network capabilities for
vehicular case” from eMBB
“higher Mobility” to eMBB
“Higher Density” as this use
case is in-line with the basic
criteria for this family (high
volume of data traffic per
area, high number of devices
density, no high mobility
needs), and less with the
“Higher User Mobility”
family.
We also benefit from this
document to clarify expected
speed KPIs/values across
eMBB families1, 2 and 3.
8.4
S1-160160 HUAWEI
TECHNOLOGIES
Co. Ltd.
S1-160161 HUAWEI
TECHNOLOGIES
Co. Ltd.
S1-160162 HUAWEI
TECHNOLOGIES
Co. Ltd.
FS_eMBB: Simplify text of
Overview section
pCR
Proposal to update broadcast
requirements eMBB TR
pCR
eMBB: Streamline eMBB text
to differentiate better eMBB
families
pCR
8.4
S1-160163 HUAWEI
TECHNOLOGIES
Co. Ltd.
eMBB: Discussion on
consolidation for eMBB non
high speed families 1,2,3
pCR
8.4
S1-160164 HUAWEI
TECHNOLOGIES
Co. Ltd.
eMBB: Replace application
layer "service" by
"scenario"/”applications”
pCR
8.5
S1-160165 HUAWEI
TECHNOLOGIES
Co. Ltd.
S1-160166 Ericsson LM
S1-160167 HUAWEI
TECHNOLOGIES
Co. Ltd.
Proposal to update broadcast
requirements to NEO TR
pCR
8.5
S1-160168 HUAWEI
TECHNOLOGIES
Co. Ltd.
FS_NEO 5.1.2.1 Continue to pCR
replace application layer
"service" by "scenario"
8.3
S1-160169 HUAWEI
TECHNOLOGIES
Co. Ltd.
CriC: Moving Ambulance and pCR
Bio-connectivity
8.5
S1-160170 ORANGE
Subscriber’s identity and
credentials storage and
management
pCR
4
S1-160171 Qualcomm
Incorporated
Reply LS on Preferred Access
for Emergency Services
LS out
8.4
8.4
070425
040012
7.4
8.5
12
V2X requirement
pCR
FS_NEO: On-demand dynamic pCR
deployment of physical access
network infrastructure
Remove some text of
Overview section of eMBB,
mainly editorial
This document proposes to
add text on broadcast support
to eMBB
This document proposes
changes in eMBB families 1,
2 and 3 mainly to avoid
overlapping text between
families.
This document proposes
consolidation of requirements
for eMBB families 1, 2 and 3
targetting the nbon high
speed users (High Mobility
being in family 4)
replace application layer
"service" by "scenario" to
avoid confusion with 3GPP
Services
This document proposes to
update text on broadcast
support to NEO TR
V2XLTE
Withdrawn
This paper proposes a use
case to support on-demand
dynamic physical network
infrastructure deployment via
nomadic access nodes
This document continues to
replace application layer
"service" by "scenario" when
needed to avoid confusion
between:
• “service” abused in place of
application layer scenario
• “service” used correctly for
3GPP related services (3GPP
transport, mobility...)
This document proposes text
for the description and
requirements to be added to
the family of Higher
Reliability, Higher
Availability and Lower
Latency in the CriC TR
22.862. The text is based on
the use case 5.65 from the
SMARTER TR 22.891
This contribution proposes a
set of requirements on
subscriber’s identity and
credentials storage and
management.
It is proposed to answer that
SA1 considers that 3GPP
access - when available should have higher priority
than WLAN access for
emergency sessions. SA1
does not observe the
requirement for a UE to
Proposed answer to S1-160228.
For the UK Home Office, the wording
is confused ("does not observe"): it is
clearer just to say that there is no such
requirement if this is what is meant.
This can be sent as such at this time
then it can be clarified later on what to
do with "Emergency calls over
Revised to S1-160285
attempt an emergency session
over WLAN if 3GPP access
is available. If there is no
available 3GPP access, and if
WLAN supports emergency
sessions, then WLAN
emergency services should be
attempted.
071103
7.11
S1-160172 Qualcomm
Incorporated
071104
7.11
S1-160173 Qualcomm
Incorporated
050003
5
S1-160174 Qualcomm
Incorporated
050004
5
S1-160175 Qualcomm
Incorporated
071106
7.9
S1-160176 Qualcomm
Incorporated
071002
7.10
S1-160177 Qualcomm
Incorporated
070422
7.4
S1-160178 Qualcomm
Incorporated
S1-160179 Qualcomm
Incorporated
S1-160180 Qualcomm
Incorporated
S1-160181 Qualcomm
Incorporated
S1-160182 Qualcomm
Incorporated
S1-160183 Qualcomm
Incorporated
S1-160184 Qualcomm
Incorporated
8.5
8.5
8.5
8.5
8.5
8.3
Clarification of relationship
between GTT and Real Time
Text
Clarification of relationship
between GTT and Real Time
Text
New WID: Unlicensed
Spectrum Offloading System
enhancements (USOS)
22.173 0107
F 14.0.0 Rel-14 TEI14
22.101 0511
F 14.1.0 Rel-14 TEI14
CR22.101v14.1.0: Accounting
for usage when using
unlicensed spectrum
Importance of requirements
supporting Free-to-air, receiveonly eMBMS, and stand-alone
eMBMS networks
Definition of PS DATA OFF &
usage of APNs
22.101 0512
WID
new
This is to align to Rel-13.
Agreed.
Agreed.
The Objective is to:
- Define service requirements
to enable an MNO to
determine the type of
spectrum (specifically if
unlicensed spectrum has been
used) to enable accounting
for usage over unlicensed
access networks.
- Define service requirements
such that the information
gathered is sufficient to
enable its use for charging
and network planning
purposes.
The description text should be more
Revised to S1-160296
generic and should not imply that the
examples are the only cases that would
be addressed.
B 14.1.0
Revised to S1-160297
discuss
ion
discuss
ion
Privacy considerations for V2X discuss
communication
ion
NEO Cost Signaling
pCR
NEO Efficient Policy
Enforcement
NEO Multiple Slices per UE
pCR
NEO Service Based Network
Selection
NEO Service Credentials
pCR
pCR
pCR
CriC Local UAV Collaboration pCR
and Connectivity
13
WLAN".
For Ericsson, this point is already
answered: there is already a
requirement to support emergency calls
over WLAN. The question is when both
types of emergency calls (over WLAN
and over 3GPP RATs), which one to
use? This is for Rel-14 and can be
answered later.
So the LS can be sent as such, just to
state that nothing is documented at this
point in time.
Revised still to change the wording.
Noted.
this document proposes that All PS Data Off documents to be
PS DATA OFF can be
discussed together.
categorised by the closing of
the Internet APN and that
concisencsious mappin gof
services to APNs can ensure
consistent behavious of
applications
Noted.
Revised to S1-160408
071003
8.2
S1-160185 Sony Europe
Limited
MIoT secrity requirement
pCR
8.4
S1-160186 Sony Europe
Limited
Peformance requirement for
virtual meeting
pCR
7.10
S1-160187 Sony Europe
Limited
Presentation of issues around
3GPP ps-data off feature
discuss
ion
8.5
S1-160188 ORANGE
Identification of subscribers
independently of devices
pCR
8.2
8.2
S1-160189 Alcatel-Lucent
S1-160190 Alcatel-Lucent
pCR
pCR
8.2
S1-160191 Alcatel-Lucent,
Nokia Networks
S1-160192 Alcatel-Lucent,
Nokia Networks
S1-160193 Alcatel-Lucent,
Nokia Networks
S1-160194 Alcatel-Lucent,
Nokia Networks
S1-160195 Alcatel-Lucent,
Nokia Networks
S1-160196 INTERDIGITAL
COMMUNICATIO
NS
FS_MIOT variable data size
FS_MIOT lightweight device
configuration
FS_MIOT PR numbering
FS_NEO Service Continuity
pCR
FS_NEO Cleanup
pCR
FS_NEO Abbreviations
pCR
US GAO views on V2I
discuss
ion
pCR
8.5
8.5
8.5
070424
7.4
8.5
060008
SMARTER_NEO: Alignment
of user plane efficiency with
22.891
S1-160197 Nokia Networks
Barring of applications in
unmatched ACDC categories
22.011 0231
8.2
S1-160198 Nokia Networks
eMBB requirements clean-up
pCR
8.3
S1-160199 Nokia Networks
CriC requirements clean-up
pCR
-1
8.4
S1-160200 Nokia Networks
mIoT requirements clean-up
pCR
-1
8.5
S1-160201 Nokia Networks
NeO requirements clean-up
pCR
8.3
S1-160202 Nokia Networks
Adding Low-delay speech
coding to CriC TR
pCR
8.3
S1-160203 Nokia Networks
Adding Industrial control to
CriC TR
pCR
8.3
S1-160204 Nokia Networks
Adding Tactile internet to CriC pCR
TR
8.3
S1-160205 Nokia Networks
Addind High Accuracy
Enhanced Positioning
14
Noted.
pCR
6
-1
Formalize security
requirement under 5.1.3 for
the Internet of Things
security aspects
Add performance figures for
Virtual meeting user case in
eMBB
Background information and All PS Data Off documents to be
potential issues with 3GPP- discussed together.
ps-data-off feature
This contribution proposes
the identification of
subscribers in 5G Networks
pCR
Noted
F 13.4.0 Rel-13 ACDC
FS_SMA
RTEReMBB
FS_SMA
RTERCRIC
FS_SMA
RTERmIoT
FS_SMA
RTERNEO
FS_SMA
RTERCRIC
FS_SMA
RTERCRIC
FS_SMA
RTERCRIC
FS_SMA
RTER-
The Tdoc adds relevant
material from 22.891 to NEO
as an enabler of user plane
efficiency
This document clarifies the A mirror is needed, in S1-160311.
barring of applications in
The fonts used in this section has to be
unmatched ACDC categories double checked by MCC.
Morpho noted that the CR is claimed to
be category F but the only modification
is on a note, so it should be informative.
Nokia explained that the text presently
as a note is actually an essential
clarification,.Qualcomm support this
view.
This document cleans up nonvalidated requirements in TR
22.861 (eMBB)
This document cleans up nonvalidated requirements in TR
22.862 (CriC)
This document cleans up nonvalidated requirements in TR
22.863 (mIoT)
This document cleans up nonvalidated requirements in TR
22.864 (NeO)
This document adds use case
on Low-delay speech coding
to TR 22.862
This document adds use case
on Industrial control to TR
22.862
This document adds use case
on Tactile internet to TR
22.862
This document adds use case
on High Accuracy Enhanced
Agreed.
Withdrawn.
Withdrawn.
Withdrawn.
(ePositioning) to CriC TR
CRIC
8.4
S1-160206 INTERDIGITAL
SMARTER_eMBB: Import of pCR
COMMUNICATIO use case variable data rate from
NS
22.891
8.3
S1-160207 INTERDIGITAL
SMARTER_ CriC: Reduction
COMMUNICATIO of user plane latency
NS
pCR
8.5
S1-160208 Ericsson LM
pCR
071004
7.10
S1-160209 Ericsson
070803
7.8
S1-160210 KPN
400044
7
S1-160211 ORANGE
400045
7.1
S1-160212 ORANGE
Local supervisory tones
22.173 0108
060003
6
S1-160213 Nokia Networks
Removing EVS service
requirements from releases
where it is not supported
22.173 0109
060004
6
S1-160214 Nokia Networks
22.173 0110
060005
6
S1-160215 Nokia Networks
Removing EVS service
requirements from releases
where it is not supported
Removing EVS service
requirements from releases
where it is not supported
22.173 0111
A 12.8.0 Rel-12 EVS_cod
ec-SA1
060006
6
S1-160216 Nokia Networks
22.173 0112
A 13.1.0 Rel-13 EVS_cod
ec-SA1
060007
6
S1-160217 Nokia Networks
22.173 0113
A 14.0.0 Rel-14 EVS_cod
ec-SA1
040032
6
S1-160218 Verizon
Removing EVS service
requirements from releases
where it is not supported
Removing EVS service
requirements from releases
where it is not supported
Restricting
Unattended/Background Data
Traffic
FS_NEO: Forward
compatibility of release 15
3GPP PS Data Off
22.011 0224
IP connectivity requirements for pCR
MCData
Reply LS on call progression
LS out
indication
15
Positioning (ePositioning) to
TR 22.862
The Tdoc adds relevant
material from 22.891 to
eMBB: improved efficiency
for devices with highly
variable data rate
requirements
The Tdoc adds relevant
material from 22.891 to CriC
as an enabler to reduce user
plane latency
B 14.1.0 Rel-14 PS_DAT
A_OFF
To be taken as a basis for the PS Data
Off discussions.
Revised to S1-160314
Revised to S1-160452
To allow operators to provide
an identical experience to
their end user in terms of call
progression for all call
scenarios (Home and
Roaming cases)
Proposed answer to S1-160233.
Revised to S1-160323
The answer should be clearer on
whether "Home network" or "visited
network" are meant in "Ring back
tone".
" and stop the local busy Tone when
receiving media from the network"
(under "busy tone") seem to be a copypaste error and should be deleted.
See related CR in S1-160212.
B 14.0.0 Rel-14 TEI14
This CR clarifies that "When
Revised to S1-160295
no progress indication
(announcement or tone) is
provided to the subscriber by
the home network, there shall
be the equivalent indication
provided by the user terminal
using the supervisory tones as
indicated in Annex A.2. "
F 10.6.0 Rel-10 EVS_cod Work on EVS targeted Rel- The Reason for change is to be updated. Revised to S1-160309
ec-SA1 10 but the codec was
completed later, in Rel-12.
SA1 had, however, included
the service requirements
already in its Rel-10
specifications. This has to be
removed.
A 11.6.0 Rel-11 EVS_cod Mirror CR to the previous
Revised to S1-160310
ec-SA1 one.
Qualcomm has no problem with the
Revised to S1-160306
technical content but do not see them as
mirror from the first one.
This is to be revised.
Same comment.
Revised to S1-160307
It is proposed that SA1
provides the following
response:
"The system in the cited
requirements comprises any
Same comment.
Revised to S1-160308
For Huawei and LG, this is too
solution-centric and then out of scope
of SA1.
The actual answer will be in S1160293.
Noted.
one or more of the following:
User Equipment, Radio
Access Network, Core
Network.
SA1 is not capable of
determining if Solution 1 is
the best or only solution, but
SA1 agree that this
mechanism would – when
coupled with a predictable
UE or HLOS response –
satisfy the requirement.
SA1 can also note that neither
EAB nor ACDC solutions
fulfil the cited requirement."
040001
4
S1-160219
S1-160220 C1-160793
Not used
LS on ACDC requirement for
IMS services
040052
4
S1-160221 C1-160764
040026
4
S1-160222 ETSI
ITS(16)000010r2
LS on NG eCall support for the LS in
EU
LTE support for V2X services LS in
(FS_V2XLTE)
040053
4
040025
4
S1-160223 NGMN Alliance
Project
S1-160224 SP-150839
NGMN Description of Network LS in
Slicing Concept
LS on LTE support for V2X
LS in
services
040054
4
S1-160225 SP-150848
Noted without
presentation.
040047
4
S1-160226 ITU-T SG20 – LS
008
LS to WGs on Application
LS in
Architecture related SI/WI
proposals not related to Critical
Communications
LS on recently established new LS in
Study Group 20 (SG20)
040051
4
S1-160227 S2-154463
040011
4
S1-160228 S2-154427
Reply LS on eCall support for
the EU from IETF Ecrit WG
LS on Preferred Access for
Emergency Services
Noted without
presentation.
Noted.
16
LS in
CT1 consider that meeting
the stage 1 requirement that
“ACDC shall not apply to any
IMS services” would have an
impact to the solution agreed
by CT1 for Rel-13. Currently
the NAS layer is only aware
of IMS voice, video and SMS
applications (i.e. MMTEL
voice/video and SMS over
IP) and not aware of other
IMS services being started.
Hence, to meet this
requirement for all IMS
services, CT1 would need to
enhance or revisit the agreed
solution, which would be
difficult to complete within
Rel-13 timeframe.
Based on the above
considerations, each ETSI
ITS member has been
encouraged to review the
TR22.885 and the related
requirements and provide its
comments directly to 3GPP
TSG SA1.
See S1-160115 to
cover this issue.
Noted without
presentation.
ETSI ITS was a bit overwhelmed by all Noted.
the use cases presented by SA1. Some
clarifications, simplifications, etc,
should be done.
3GPP TSG SA kindly
This is sent as requested by SA1.
requests the recipient groups
to take the above information
and the ongoing work on
V2X into account.
Noted.
LS in
LS in
Noted without
presentation.
Noted.
In the context of the
feasibility study on the
Proposed answer in S1-160171.
040021
4
S1-160229 R1-157821
LS on clarification of Road Site LS in
Unit (RSU) types
040031
4
S1-160230 R2-157131
LS on Control of
LS in
Unattended/Background Traffic
17
support of emergency
services over WLAN
(FS_SEW), SA2 has agreed
that the UE shall be able to
determine which access
networks (WLAN and/or
3GPP) can be used for
establishing IMS emergency
sessions and in which order.
This agreement was based on
the assumption that e.g. in
some cases only 3GPP access
may be allowed for
emergency services while in
other cases both WLAN and
3GPP accesses may be
allowed and the WLAN may
have the highest priority.
Should SA2 consider
scenarios where the WLAN
access has higher priority or
equal priority with 3GPP
access for emergency
sessions? Or, in all cases the
3GPP access (when available)
should always have the
highest priority?
RAN1 asks SA1 to confirm
there are two RSU types
including UE-type and eNB
type and provide the details
of definition and the services
of the RSU and their
associated service
requirements.
In SA1's requirement in
22.101: "The system shall be
able to apply different
handling (e.g. be able to
prohibit or delay) all or a
particular selection of IP
bearer service requests
depending on whether a
service request is for
Unattended Data Traffic or
Attended Data Traffic.",
RAN2 ask SA1 what is the
“system” , and whether the
requirement would be met by
Solution 1 depending on
traffic handling in the
operating system of the UE.
Further, RAN2 ask SA1
comment whether the
proposed EAB- and/or
ACDC-based solutions can
meet the SA1 requirement.
RAN2's solution 1 is "when
RAN RRC signalling is
congested, RAN broadcast a
single congestion
bit/Background Data
Restriction (BDR) bit to the
Kept open until the corresponding
discussions take place.
Proposed answer in S1-160286.
Noted.
Proposed answer in S1-160218.
Noted.
UE. The bit is passed to OS
to initiate the background
data restriction."
040041
4
S1-160231 S5-156399
LS on definition of Network
Service
040005
4
S1-160232 R2-157019
Reply LS on ACDC mechanism LS in
400043
4
S1-160233 GSMA RILTE#48
Doc 115 Rev 3
IMS Network Requirements
LS in
regarding the provision of Call
Progress Indications
040046
4
S1-160234 C1-154001
LS on precedence of
information in USIM
8.2
S1-160235 LG Electronics
pCR
Revision of S1-160100
8.2
S1-160236
pCR
Revision of S1-160101
S1-160237
S1-160238
S1-160239
S1-160240
S1-160241
S1-160242
S1-160243
S1-160244
S1-160245
S1-160246
S1-160247
S1-160248
mIoT Traffic Scenario for
operational aspect family
LG Electronics
mIoT Traffic Scenario for
connectivity aspect family
Rapporteur (Applied MPS_Mods Status Report
Sciences)
Rapporteur (Sprint) ELIOT Status Report
Rapporteur (China eULRS Status Report
Unicom)
Rapporteur (LGE) V2XLTE Status Report
Rapporteur (US
MCCore Status Report
DoC)
Rapporteur (US
MCPTT-R Status Report
DoC)
Rapporteur (French MCVideo Status Report
MoI)
Rapporteur (French MCData Status Report
MoI)
Rapporteur (Huawei) EnTV Status Report
Rapporteur (Orange) PS_Data_Off Status Report
Rapporteur
FS_SMARTER Status Report
(Vodafone)
Rapporteur
FS_SMARTER-MIoT Status
(Vodafone)
Report
18
LS in
LS in
REP
REP
REP
REP
REP
REP
REP
REP
REP
REP
REP
REP
SA5 requests SA1 to inform
SA5 whether there is an
official definition of Network
Service in 3GPP
specifications.
3GPP SA1 is requested to
consider the issue and
determine whether any
modifications are needed to
any of their specifications to
provide further clarification
on the provision of call
progress indications to the
UE and whether the IMS
Network is required to mimic
CS behaviour or not.
CT1 request SA2 to provide
background on the
requirement above and
provide their views to the
above questions.
22.101 makes an extensive use of this Noted.
term.
There might indeed be a need to further
clarify the terms, which might be
referring to different concept.
It was proposed to use it as defined by
NFV, but Alcatel-Lucent and Cisco
checked and realised that this is tooNFV specific.
A simple answer is to say "no: these
terms haven't been defined". The risk is
that SA5 will define the terms on their
side and that this would not be
compliant with 5G.
Proposed answer in S1-160294.
Proposed answer in S1-160211.
Noted without
presentation.
Noted.
It is proposed that SA1 give directly the Noted.
requirements rather than having SA2 to
answer about SA1's requirements.
The requirements are not clear right
now so they have to be refined before
anything can be sent out.
070402
7.4
070403 7.4
070518rr 7.5
070519 7.5
071101
7.11
071101
7.11
070401
7.4
070402
7.4
070502
7.5
070501
7.5
8.5
040023
4
S1-160249 Rapporteur (Nokia FS_SMARTER-MIoT Status
REP
Networks)
Report
S1-160250 Rapporteur (Huawei) FS_SMARTER-MIoT Status
REP
Report
S1-160251 Rapporteur (China FS_SMARTER-NEO Status
REP
Mobile)
Report
S1-160252 Rapporteur
TS22.185v0.2.0 to include
TS
agreements at this meeting
S1-160253 Rapporteur
Cover page for TS22.185v0.2.0 TS
S1-160254 Rapporteur
TS 22.280
TS
S1-160255 Rapporteur
Cover page for TS22.280v0.1.0 TS
S1-160256 Rapporteur
TS22.281v0.1.0 to include
TS
agreements at this meeting
S1-160257 Rapporteur
Cover page for TS22.281v0.1.0 TS
S1-160258 Rapporteur
TS22.282v0.1.0 to include
TS
agreements at this meeting
S1-160259 Rapporteur
Cover page for TS22.282v0.1.0 TS
S1-160260 Rapporteur
TR22.891v1.3.0 to include
TR
agreements at this meeting
S1-160261 Rapporteur
Cover page for TR22.891v1.3.0 TR
S1-160262 Rapporteur
TR22.861v0.3.0 to include
TR
agreements at this meeting
S1-160263 Rapporteur
Cover page for TR22.861v0.3.0 TR
S1-160264 Rapporteur
TR22.862v0.3.0 to include
TR
agreements at this meeting
S1-160265 Rapporteur
Cover page for TR22.862v0.3.0 TR
S1-160266 Rapporteur
TR22.863v0.3.0 to include
TR
agreements at this meeting
S1-160267 Rapporteur
Cover page for TR22.863v0.3.0 TR
S1-160268 Rapporteur
TR22.864v0.3.0 to include
TR
agreements at this meeting
S1-160269 Rapporteur
Cover page for TR22.864v0.3.0 TR
S1-160270 Rapporteur / Session Other drafting agenda
AGE
chair
S1-160271 Rapporteur / Session Other drafting report
REP
chair
S1-160272 Rapporteur / Session V2X drafting agenda
AGE
chair
S1-160273 Rapporteur / Session V2X drafting report
REP
chair
S1-160274 Rapporteur / Session Mission Critical drafting agenda AGE
chair
S1-160275 Rapporteur / Session Mission Critical drafting report REP
chair
S1-160276 Rapporteur / Session SMARTER drafting agenda
AGE
chair
S1-160277 Rapporteur / Session SMARTER drafting report
REP
chair
S1-160278 ORANGE
Contribution concerning access pCR
to the network in low-ARPU
areas in TR NEO TR v0.2.0
S1-160279 WWRF
LS on LTE support for V2X
LS in
services
19
Revision of S1-160455
Noted.
One session was allocated to
this drafting.
Noted
Approved
Noted.
Approved.
Revision of S1-160052
As requested by 3GPP,
WWRF will be reviewing the
use cases and requirements
for LTE V2X and may come
back with comments, if any.
This is tasked to the Vertical
Industry Platform (VIP) WG
on Connected Cars (CC).
They also provide some
explanations on WWRF VIP
WG of Connected Cars.
Noted.
S1-160280 VODAFONE Group Update to “Higher User
Plc
Mobility” of eMBB TR
S1-160281 Nokia Networks
Considerations on V2X
pCR
040002r 4
S1-160282 LG Electronics
040003r 4
S1-160283
040004r 4
S1-160284
22.011 0228r1 F 13.4.0 Rel-13 ACDCST1
22.011 0229r1 A 14.1.0 Rel-14 ACDCST1
LS out
040012r 4
S1-160285
040022
4
S1-160286
050006
5
S1-160287
050007
5
S1-160288 China Unicom,China Paging optimization
Telecom, KT Corp., requirements in LTE
CATR, ZTE,
Applied
Communication
Sciences, Intel
22.101 0509
S1-160289 CATT
pCR
8.4
070423
7.4
070413r 7.4
071101
Correction of ACDC
requirement for IMS services
LG Electronics
Correction of ACDC
requirement for IMS services
LG Electronics Inc. [DRAFT] Reply LS to CT1 on
ACDC requirement for IMS
services
SA1/Qualcomm
Reply LS to SA2 on Preferred
Incorporated
Access for Emergency Services
LG
Reply LS to RAN1 (cc RAN2,
SA2) on clarification of RSU
types
China Unicom
Paging Policy Enhancements
and Procedure Optimizations in
LTE
8.2
S1-160290 III
8.2
S1-160291 III
7.11
S1-160292 Huawei, Hisilicon,
KPN, China
Telecom, ZTE
040033
S1-160293 Verizon, LG
040041r 4
S1-160294 Huawei
400045r 7.1
S1-160295 Orange
Proposed text for Overview
section for V2X TS
Text proposal of traffic scenario
3
Text Proposal of Connectivity
aspects
ProSe for the Evolved Packet
System (EPS)
Revision of S1-160044
Revised and merged
into 407
Revision of S1-160116.
Mirror CR.
Revision of S1-160114
Agreed.
LS out
Revision of S1-160171
LS out
Proposed answer to S1160229
WID
new
Revision of S1-160130.
The objective is to define
service requirements to
enable the 3GPP core
network to optimize the
paging procedures in LTE
based on the application
characteristics known and
trusted at the serving
network, the UE’s mobility or
likely location. A study has
been done in TR 22.838 with
the conclusion to take it as a
basis for the development of
normative phase.
B 14.1.0 Rel-14 PPEPO_ Revision of S1-160131.
LTE
The CR adds the
requirements to allow 3GPP
core network to enhance the
paging function based on the
core network and UE
information in LTE.
Revision of S1-160104
pCR
0.2.0
Revision of S1-160010
pCR
0.2.0
Revision of S1-160011
22.278 0223
B 13.2.0 Rel-14 TEl14
[DRAFT] LS to RAN2 (Cc
LS out
CT1) on Control of
Unattended/Background Traffic
LS answer to SA5 on definition LS out
of Network Service (S5156399)
Local supervisory tones
22.173 0108r1 B 14.0.0 Rel-14 TEI14
20
This includes the material of This is a late document.
S1-160007, S1-160008 and
S1-160009.
Revision of S1-160115
Revision of S1-160120.
The CR introduces the
service requirements for
commercial ProSe UE-toNetwork Relay for the
Evolved Packet System (EPS)
Proposed answer to S1160218 and S1-160230.
The attachments are missing.
Agreed/
Revised to S1-160325
Approved.
To be sent after the TR is available. A
link has to be put in the LS.
Revised to S1-160521
See companion CR in S1-160288.
NEC to be added as supporting
company.
Revised to S1-160299
The first sentence and the 2nd
requirement need to be specified more
precisely.
Revised to S1-160300
Revised to S1-160404
This is not TEI since it impacts the
Revised to S1-160312
other groups. And it is too late to
propose a new WID at this meeting
since WIDs have to be submitted by the
deadline.
So the chair proposes to endorse this
CR in SA1 but submit the
corresponding WID directly at SA.
"draft" to be removed in the title.
Revised to S1-160326
Proposed answer to S1160231
"draft" to be deleted as well as the
Revised to S1-160327
examples. This is not defined in 22.101.
Revision of S1-160212
"choice" to be changed into
"configuration".
Changes on changes to be removed.
Revision on the cover to be removed.
Revised to S1-160503
050003r 5
S1-160296 Qualcomm
Incorporated
WID
new
Revision of S1-160174
050004r 5
S1-160297
22.101 0512r1 B 14.1.0
Revision of S1-160175
050005
5
S1-160298
050006r 5
S1-160299
050007r 5
S1-160300
050008r 5
S1-160301
050010
5
S1-160302
050011
5
060001r 6
060002r 7.11
060005r 6
060006r 6
060007r 6
060003r 6
060004r 6
060008r 6
071101r 7.11
070601r 7.6
071004r 7.10
071006r 7
071007r 4
080101r 8.1
New WID: Unlicensed
Spectrum Offloading System
enhancements (USOS)
Qualcomm
CR22.101v14.1.0: Accounting
Incorporated
for usage when using
unlicensed spectrum
Qualcomm
Accounting for usage when
Incorporated
using unlicensed spectrum
China Unicom
Paging Policy Enhancements
and Procedure Optimizations in
LTE
China Unicom,China Paging optimization
Telecom, KT Corp., requirements in LTE
CATR, ZTE,
Applied
Communication
Sciences, Intel
China Mobile Com. Proposed WID for eFMSS
Corporation
China Mobile Com. eFMSS CR for supporting third
Corporation
party owned (S)Gi-LAN service
Supporting companies also added.
22.115 0080
WID
new
Revision of S1-160287
22.101 0509r1 B 14.1.0 Rel-14 PPEPO_ Revision of S1-160288
LTE
WID
new
22.101 0513
Revision of S1-160137
CR to include the impacts of The reason for change is to be clarified
S1-1600301.
and a new requirement is to be stated
clearly.
S1-160303 China Mobile Com. eFMSS CR for supporting third 22.115 0081
CR to include the impacts of This is the impact on 22.115.
Corporation
party owned (S)Gi-LAN service
S1-1600301.
S1-160304 ORANGE
MMTEL R13 correction
22.173 0105r1 F 13.1.0 Rel-14
Revision of S1-160050
S1-160305 ORANGE
MMTEL correction
22.173 0106r1 A 14.0.0 Rel-14 TEI13
Revision of S1-160051
S1-160306 Nokia Networks
Removing EVS service
22.173 0111r1 A 12.8.0 Rel-12 EVS_cod Revision of S1-160215
requirements from releases
ec-SA1
where it is not supported
S1-160307 Nokia Networks
Removing EVS service
22.173 0112r1 A 13.1.0 Rel-13 EVS_cod Revision of S1-160216
requirements from releases
ec-SA1
where it is not supported
S1-160308 Nokia Networks
Removing EVS service
22.173 0113r1 A 14.0.0 Rel-14 EVS_cod Revision of S1-160217
requirements from releases
ec-SA1
where it is not supported
S1-160309 Nokia Networks
Removing EVS service
22.173 0109r1 F 10.6.0 Rel-10 EVS_cod Revision of S1-160213
requirements from releases
ec-SA1
where it is not supported
S1-160310 Nokia Networks
Removing EVS service
22.173 0110r1 A 11.6.0 Rel-11 EVS_cod Revision of S1-160214
requirements from releases
ec-SA1
where it is not supported
S1-160311 Nokia Networks
Barring of applications in
22.011 0233 F
Rel-14 ACDC
Revision of S1-160197
unmatched ACDC categories
S1-160312 Huawei, Hisilicon, ProSe for the Evolved Packet
22.278 0223r1 B 13.2.0 Rel-14 TEl14
Revision of S1-160292
KPN, China
System (EPS)
Telecom, ZTE
S1-160313 U.S. Department of Mission Critical Push to Talk 22.179 0036r1 C 13.3.0 Rel-14 MCImp- Revision of S1-160012
Commerce
over LTE Realignment
MCPTTR
(MCPTT-R)
S1-160314 Ericsson
3GPP PS Data Off
22.011 0224r6 B 14.1.0 Rel-14 PS_DAT Revision of S1-160209
The previous version in S1-160209
A_OFF
should not have been rev0 since
CR#0224rev0 was S1-154159.
S1-160315 Vodafone,
Addition of Mobile Data and
22.030 0019r1 B 13.0.0 Rel-14 PS_DAT Revision of S1-160136
BlackBerry UK Ltd, Data Roaming on/off functions
A_OFF
Orange.
to the MMI of Mobile
Equipment.
S1-160316 ORANGE
Reply LS on Data Off
LS out
Revision of S1-160017
Requirements
S1-160317 Nokia Networks,
Completion of TR 22.891
22.891
FS_SMA Revision of S1-160143
Alcatel-Lucent,
RTER
Vodafone,
MediaTek, Deutsche
Telekom, NEC,
21
080110r 8.1
-1
Telecom Italia, Sony
S1-160318 HUAWEI
TECHNOLOGIES
Co. Ltd.
S1-160319 Vodafone, MCC
040032
4
S1-160320 S2-160572
040031
4
S1-160321 S2-160896
Reply LS (Cc SA1) on
LS in
precedence of information in
USIM
Removal of non-approved
22.011 0234r1
CR#0224rev3 on 3GPP PS Data
Off
Reply LS to GSMA NG RILTE LS out
(cc CT1) on call progression
indication
S1-160322 Vodafone, MCC
400044r 7
S1-160323 ORANGE
040035
S1-160324 RPa160083
4
040004rr 4
040033r
040041rr 4
8.1
8.3
FS_SMARTER 5.74 Updates pCR
to QoS and Policy Control Use
Case
Removal of erroneous text
22.011 0234
related to 3GPP PS Data Off
Reply LS (to SA1) on Set of
LS in
Rel-13 features for the Support
of Emergency sessions over
WLAN
LS on Scenarios and
Requirements for Next
Generation Access
Technologies
LS in
S1-160325 SA1/LG Electronics LS to CT1 on ACDC
LS out
Inc.
requirement for IMS services
S1-160326 SA1/Verizon, LG
LS to RAN2 (Cc CT1) on
LS out
Control of
Unattended/Background Traffic
S1-160327 Huawei
LS answer to SA5 on definition LS out
of Network Service (S5156399)
S1-160328 Nokia Networks
Proposed new use case family
for CriC use cases in TR 22.891
S1-160329 Nokia Networks
Proposal to add new use case
family on Priority services to to
TR 22.862 on CriC
22
Revision of S1-160086
Revised to S1-160322
22.101 states that “UEs shall See related CR in S1-160471 and
only be able to establish an
proposed answer in S1-160470.
Emergency session over
WLAN when:
- the UE has been provisioned
with the WLAN access
parameters, and
- the access parameters
include an indication of
where WLAN emergency
access is authorized.”
This text may be understood
to mean that the UE is
provisioned with information
on where (which AP) WLAN
emergency access is
authorized.
SA2 indicates that such
requirement is not considered
for Rel13.
Noted.
Noted.
Revision of S1-160319
Revision of S1-160211
See related CR in S1-160295.
Revised to S1-160504
NTT DOCOMO prefer to have the LS
simple to avoid the risk of mismatch
with the CR.
It has to be checked if "GSMA GFRG"
is an existing group.
RAN inform that their work Vodafone outlined that at least the
Noted.
on Scenarios and
terminology has to be aligned.
Requirements for Next
Oberthur pointed out that not only the
Generation Access
terminology has to be aligned but also
Technologies has started in e.g. the numbers.
3GPP TSG RAN (SID in RP- Most of the RAN work will be done
152257). The initial version before March, so alignment is important
of the TR is provided as
from the beginning.
attachment.
Proposed answer in S1-160506.
Revision of S1-160284
Agreed.
Revision of S1-160293
Revision of S1-160294
This document proposes a
new use case family for
FS_SMARTER-CriC use
cases in TR 22.891.
This document proposes to
add new use case family on
Priority services to TR 22.862
on CriC.
Agreed.
Tdoc number to be updated, revision to Revised to S1-160523
be accepted.
071111
7.11
S1-160330 Ericsson, Qualcomm Requirements for enhanced TV
service
S1-160331 Ericsson,
Requirements for enhanced TV
Qualcomm, Huawei, service
Nokia, EBU
S1-160332 Applied
Text alignment for terminating
Communication
UE option
Sciences
S1-160333 Applied
Update to Priority Data Bearer
Communication
Service
Sciences
S1-160334 Applied
MPS Anonymity Requirement
Communication
Sciences
S1-160335 China Unicom, ZTE, Requirements for enhancements
CATR, Huawei
on User Location Reporting
Support
S1-160336 Ericsson LM
Clarifies that TV service can
use both unicast and broadcast
S1-160337 Ericsson LM
New use case: Hybrid TV
delivery
S1-160338 Ericsson,
Requirements for enhanced TV
Qualcomm, Huawei, service
Nokia, EBU
S1-160339 Huawei
Accounting requirement for TV
Technologies
transport service support
S1-160340 MoI, France
MCData enhanced presence
S1-160341 MoI, France
MCData Data base enquiries
and internet access
S1-160342 MoI, France
MCData external interfaces
S1-160343 HOME OFFICE
MCVideo - Proposed new
requirements for leaving a
video stream
S1-160344 USDOC
Call Termination for MCCoRe
22.101 0510r1 B 14.1.0 Rel-14 EnTV
Revised to S1-160331
071112
7.11
22.101 0510r2 B 14.1.0 Rel-14 EnTV
Revised to S1-160338
070717r 7.7
S1-160345 Huawei, TD-Tech
070725r 7.7
S1-160346 Huawei, TD-Tech
070724r 7.7
S1-160347 HOME OFFICE
070715r 7.7
070719r 7.7
S1-160348 MoI, FRance
S1-160349 MoI, France
MCVideo profile management
and administration
Video control by a dispatcher in
MCVideo.
MCVideo - Proposed new
requirements for configuring
external video capabilities
MCVideo robots
MCVideo enhanced presence
S1-160350
S1-160351
S1-160352
S1-160353
S1-160354
S1-160355
S1-160356
S1-160357
S1-160358
S1-160359
S1-160360
S1-160361
S1-160362
S1-160363
S1-160364
S1-160365
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
071102r 7.1
071103r 7.1
071104r 7.1
071105r 7.3
071107r 7.9
071108r 7.9
071112r 7.11
071113r 7.9
070809r 7.8
070810r 7.8
070812r 7.8
070713r 7.7
070516
-1
7.5
23
22.153 0029r1 F 14.2.0 Rel-14
Revision of S1-160082
Agreed.
22.153 0030r1 F 14.2.0 Rel-14
Revision of S1-160083
Agreed.
22.153 0031r1 B 14.2.0 Rel-14
Revision of S1-160084
Agreed.
22.101 0508r1 B 14.1.0 Rel-14 eULRS
Revision of S1-160128
22.816 0001r1 F 14.0.0 Rel-14 FS_EnT
V
22.816 0002r1 B 14.0.0 Rel-14 FS_EnT
V
22.101 0510r3 B 14.1.0 Rel-14 EnTV
Revision of S1-160140
Agreed.
Revision of S1-160141
Agreed.
Revision of S1-160331
Revised to S1-160474
22.115 0079r1 B 13.3.0 Rel-14 EnTV
Revision of S1-160054
Agreed.
pCR
pCR
Revision of S1-160024
Revision of S1-160021
Agreed.
Agreed.
pCR
pCR
Revision of S1-160025
Revision of S1-160073
Agreed.
Agreed.
Revised to S1-160510
pCR
Outcome of offline discussion
(Day 3)
Revision of S1-160127
pCR
Revision of S1-160125
Agreed.
pCR
Revision of S1-160075
Agreed.
pCR
pCR
Revision of S1-160041
Revision of S1-160030
Revision on revision, revision on the
cover page.
Revised to S1-160473
Agreed.
Agreed.
Title to be kept as "capability reporting" Revised to S1-160516
instead of "capability sharing
reporting".
Revised to S1-160472
070406r 7.4
070410r 7.4
S1-160366
S1-160367
S1-160368
S1-160369
S1-160370
S1-160371
S1-160372
S1-160373
S1-160374
S1-160375
S1-160376
S1-160377
S1-160378
S1-160379
S1-160380
S1-160381
S1-160382
S1-160383
S1-160384
S1-160385
S1-160386
S1-160387
S1-160388
S1-160389
S1-160390
S1-160391
S1-160392
S1-160393
S1-160394
S1-160395
S1-160396
S1-160397
S1-160398
S1-160399
S1-160400 Rapporteur (LG
Electronics)
S1-160401 Rapporteur (LG
Electronics)
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Reserved SMARTER
Proposed text for Scope section
for V2X TS
Proposed text for Definition and
Abbreviation section for V2X
TS
Proposed text for Definition and
Abbreviation section for V2X
TS
Proposed text for Reference
section for V2X TS
Text Proposal for Overview for
V2X TS
Text Proposal for Overview for
V2X TS
070410rr 7.4
S1-160402 Rapporteur (LG
Electronics)
070412r 7.4
070414r 7.4
S1-160403 Rapporteur (LG
Electronics)
S1-160404 Huawei
070414rr 7.4
S1-160405 Huawei
070417r 7.4
S1-160406 LGE, CATT, Fujitsu Corrections to V2X
consolidated Requirements
24
pCR
Revision of S1-160088
Agreed.
pCR
Revision of S1-160097
Revised to S1-160402
pCR
Revision of S1-160401
Agreed.
pCR
Revision of S1-160089
Agreed.
pCR
Revision of S1-160067
Revised to S1-160405
pCR
Revision of S1-160404
Nokia pointed out that the document
Revised to S1-160500
was uploaded just before presentation,
which is not acceptable.
For Alcatel-Lucent, Nokia and Intel,
Noted.
this is aligning the study with the
normative work, which is not needed:
the study was to prepared the work for
the actual feature and does not have to
be aligned to the subsequent normative
work. They see it as a lost of time. For
Ericsson and Qualcomm, not aligning
the TR to the TS might be confusing.
LG does not want to make it a general
rule but think that this is useful in this
particular case.
Still no consensus.
22.885 001
F 14.0.0 Rel-14 FS_V2X Revision of S1-160093
LTE
070418r 7.4
S1-160407 Rapporteur (LG
Electronics)
Proposed text for requirement
section for V2X TS
070422r 7.4
S1-160408 Qualcomm
Incorporated
Privacy considerations for V2X discuss
communication
ion
070504r 7.5
S1-160409
S1-160410
S1-160411
S1-160412
S1-160413
S1-160414
S1-160415
S1-160416
S1-160417
S1-160418
S1-160419
S1-160420
S1-160421
S1-160422
S1-160423
S1-160424
S1-160425
S1-160426
S1-160427
S1-160428
S1-160429
S1-160430 HOME OFFICE
070506r 7.5
S1-160431 MoI, France
070507r 7.5
S1-160432 Harris Corporation
070508r 7.5
S1-160433 HOME OFFICE
070509r 7.5
S1-160434 Motorola Solutions
070510r 7.5
S1-160435 MoI, France
070511r 7.5
S1-160436 Huawei, TD-Tech
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
Reserved V2X
MCCoRe - Proposed new
section for interworking
MCCoRe Mobility and priority
requirements
MCCoRe - Proposed new
common requirements for
Emergency and Imminent Peril
MCCoRe - Proposed
explanation of intent of wording
Ensuring correctness of
requirements for Rel-14
common functionality
MCCoRe Air ground air
communications
MCService emergency alert
25
pCR
Revision of S1-160094.
This contribution proposes
V2X service requirements to
support V2V/V2I/V2P/V2N
use cases. The zip file also
contains a mapping table
between CPRs and Rs.
Requirement [R-5.2.4-001] deserves
Revised to S1-160502
further explanations, in particular the
part "even when an RSU is involved".
[R-5.1-007] is not grammatically
correct.
The privacy aspects have to be removed
from this contribution and be covered
by S1-160408.
Revision of S1-160178.
KPN pointed out that regulatory
Revised to S1-160501
One of the 2 following
requirements might either mandate to
requirements is proposed, to have user privacy or, on the contrary,
be decided by SA1:
mandate to collect all the data.
Both the HPLMN and
The second requirement is the preferred
VPLMN operators shall have one.
the option to either store or
"any single network entity" is not clear.
delete all of the messages
The pedestrian case seems to be
transferred by UEs using
missing. For Qualcomm, adding
network resources.
"pedestrian" just mean that everybody
Or:
would be impacted, not particularly
The 3GPP system shall
related to V2X.
support driver and vehicle
AT&T clarified that the US mandate
privacy, by ensuring that a
relates only to V2X applications.
UE cannot be tracked or
The sentence was edited online to try to
identified by any single
remove this ambiguity.
network entity (operator or
This
third party).
pCR
Revision of S1-160062
Revised to S1-160465
pCR
Revision of S1-160019
Revised to S1-160467
pCR
Revision of S1-160076
Agreed.
pCR
Revision of S1-160063
Agreed.
Revision of S1-160121
Agreed.
pCR
Revision of S1-160018
Revised to S1-160468
pCR
Revision of S1-160123
Agreed.
pCR
0.0.0
070701r 7.7
S1-160437 HOME OFFICE
070702r 7.7
070703r 7.7
S1-160438 MINISTERE DE
L'INTERIEUR
S1-160439 HOME OFFICE
070704r 7.7
S1-160440 MoI, France
070707r 7.7
S1-160441 HOME OFFICE
070708r 7.7
S1-160442 HOME OFFICE
070727r 7.7
S1-160443 MoI, France
070711r 7.7
S1-160444 MoI, France
070712r 7.7
S1-160445 MoI, France
070513
070720r
070513r
070518
070801r
S1-160446
S1-160447
S1-160448
S1-160449
S1-160450
triggered by location
MCVideo - Proposed
pCR
requirements restructure
MCVideo Scope and definitions pCR
pCR
Revision of S1-160055
Agreed.
pCR
Revision of S1-160033
Agreed.
pCR
Revision of S1-160058
pCR
Revision of S1-160059
pCR
Revision of S1-160028
pCR
Revision of S1-160038
Agreed.
pCR
Revision of S1-160040
Agreed.
pCR
Revision of S1-160035
Revision of S1-160446
Revised to S1-160448
Revised to S1-160517
Revised to S1-160458
Revised to S1-160455
070802r 7.8
Rapporteur
MoI, France
Rapporteur
Rapporteur
MINISTERE DE
L'INTERIEUR
S1-160451 HOME OFFICE
070803r 7.8
S1-160452 KPN
070805r 7.8
S1-160453 MoI, France
070807r 7.8
070518r 7.5
070514 7.5
S1-160454 MoI, France
S1-160455 Rapporteur
S1-160456 USDOC
070515
S1-160457 USDOC
Override for MCCoRe
070513rr 7.5
070808r 7.8
S1-160458 Rapporteur
S1-160459 MoI, France
070722r
070723r
070728r
070517
S1-160460
S1-160461
S1-160462
S1-160463
Combined MCCoRe Analysis
MCData Location sharing and
data forwarding
MCVideo video consultation
MCVideo video storage control
MCVideo external interfaces
Definitions for MCCoRe
7.5
7.7
7.7
7.7
7.5
MoI, France
MoI, France
MoI, France
Motorola
070517r 7.5
070504rr 7.5
S1-160464 Motorola
S1-160465 HOME OFFICE
070505
070506rr 7.5
S1-160466 UK Home Office;
US DoC
S1-160467 MoI, France
070510rr 7.5
S1-160468 MoI, France
040034
S1-160469
S1-160470 Alcatel-Lucent
7.5
4
26
Revision of S1-160079
MCVideo - Proposed
descriptive text
MCVideo parameters remote
control
MCVideo - Proposed new
requirements for video coding
MCVideo - Proposed new
requirements for video modes
MCVideo performances and
quality requirements
MCVIdeo video remote control
including camera discovery
MCVideo video processing
capabilities
Combined MCCoRe Analysis
MCVideo push and pull
Combined MCCoRe Analysis
TS 22.280
MCData definitions and
overview
MCData pCR on inclusion of
Generic capabilities into
MCData
IP connectivity requirements for
MCData
MCData conversation
management
MCData robots requirements
TS 22.280
Floor control for MCCoRe
7.5
7.7
7.5
7.5
7.8
Revision of S1-160056
Definitions for MCCoRe
MCCoRe - Proposed new
section for interworking
pCR - MCCoRe –New section
on Inter Service Interworking
MCCoRe Mobility and priority
requirements
MCCoRe Air ground air
communications
Reserved MC
Reply LS to SA2 (cc GSMA
NG, WBA) on Set of Rel-13
features for the Support of
Emergency sessions over
WLAN
"3GPP" in front of "codec" was deleted. Revised to S1-160514
It should be reintroduced.
Font to be corrected and requirements Revised to S1-160515
to be numbered.
Video mode to be added.
Agreed.
TS
pCR
Revision of S1-160078
pCR
Revision of S1-160077
Agreed.
pCR
Revision of S1-160210
Agreed.
pCR
Revision of S1-160023
Agreed.
pCR
TS
Revision of S1-160027
Revision of S1-160449
Outcome of offline discussion
(Day 3)
Outcome of offline discussion
(Day 3)
Revision of S1-160448
Revision of S1-160020
Agreed.
Revised to S1-160254
Noted.
pCR
pCR
pCR
pCR
pCR
Revised to S1-160509
Revised to S1-160508
Agreed.
Revision of S1-160037
Agreed.
Revision of S1-160039
"securities" to be changed to "security". Revised to S1-160518
Revision of S1-160031
Outcome of offline discussion
Revised to S1-160464
(Day 3)
Revision of S1-160463
Revision of S1-160430
Revised to S1-160507
pCR
Revision of S1-160431
Agreed.
pCR
Revision of S1-160435
Agreed.
LS out
Proposed answer to S1160320.
SA1 discussed the SA2
information and agreed to
modify the text to avoid any
An answer might not be needed, since Revised to S1-160505
the original one does not explicitly call
for one.
This is seen as informative, also to
GSMA in copy.
040033
4
071105rr 7.3
071112rr 7.11
070414rrr 7.4
070422rr 7.4
070418rr 7.4
400045rr 7.1
400044rr 7
040034r 4
040036 4
070505r 7.5
070513rrr 7.5
070515r 7.5
070516r 7.5
070519 7.5
070519r 7.5
S1-160471 Alcatel-Lucent,
Nokia Networks
Clarification on Support of
Emergency sessions over
WLAN
S1-160472
Reserved SMARTER
S1-160473 China Unicom, ZTE, Requirements for enhancements
CATR, Huawei
on User Location Reporting
Support
S1-160474 Ericsson,
Requirements for enhanced TV
Qualcomm, Huawei, service
Nokia Networks,
EBU
S1-160475
Reserved Mark
S1-160476
Reserved Mark
S1-160477
Reserved Mark
S1-160478
Reserved Mark
S1-160479
Reserved Mark
S1-160480
Reserved Mark
S1-160481
Reserved Mark
S1-160482
Reserved Mark
S1-160483
Reserved Mark
S1-160484
Reserved Mark
S1-160485
Reserved Mark
S1-160486
Reserved Mark
S1-160487
Reserved Mark
S1-160488
Reserved Mark
S1-160489
Reserved Mark
S1-160490
Reserved Mark
S1-160491
Reserved Mark
S1-160492
Reserved Mark
S1-160493
Reserved Mark
S1-160494
Reserved Mark
S1-160495
Reserved Mark
S1-160496
Reserved Mark
S1-160497
Reserved Mark
S1-160498
Reserved Mark
S1-160499
Reserved Mark
S1-160500 Huawei
Text Proposal for Overview for
V2X TS
S1-160501 Qualcomm
Privacy considerations for V2X
Incorporated
communication
S1-160502 Rapporteur (LG
Proposed text for requirement
Electronics)
section for V2X TS
S1-160503 Orange
Local supervisory tones
S1-160504 ORANGE
Reply LS to GSMA NG RILTE
(cc CT1) on call progression
indication
S1-160505 Alcatel-Lucent
Reply LS to SA2 (cc GSMA
NG, WBA) on Set of Rel-13
features for the Support of
Emergency sessions over
WLAN
S1-160506 Vodafone
Proposed answer to S1-160324
S1-160507 UK Home Office;
pCR - MCCoRe –New section
US DoC
on Inter Service Interworking
S1-160508 Rapporteur
Combined MCCoRe Analysis
S1-160509 USDOC
Override for MCCoRe
S1-160510 USDOC
Call Termination for MCCoRe
S1-160511
S1-160512 Rapporteur
Exception sheet for 22.280
S1-160513 Rapporteur
Exception sheet for 22.179
27
22.101 0508r2 B 14.1.0 Rel-14 eULRS
misunderstanding in SA2.
The CR is missing.
One limitation for support of
Emergency session over
WLAN is removed from Rel
13.
Revision of S1-160362
Revision of S1-160335
22.101 0510r4 B 14.1.0 Rel-14 EnTV
Revision of S1-160338
pCR
Revision of S1-160405
discuss
ion
pCR
Revision of S1-160408
22.173 0108r2 B 14.0.0 Rel-14 TEI14
LS out
Revision of S1-160295
Revision of S1-160323
LS out
Revision of S1-160470
22.101 0514
F 13.7.0 Rel-13 TEI-13
Agreed.
Revision of S1-160407
Revision of S1-160466
Revision of S1-160458
Revision of S1-160457
Revision of S1-160344
ES
With this, EnTV is completed.
Agreed.
For drafting session.
070707rr 7.7
S1-160514 HOME OFFICE
070708rr 7.7
S1-160515 HOME OFFICE
070719rr
070720rr
070723rr
070729
070819
040022r
S1-160516
S1-160517
S1-160518
S1-160519
S1-160520
S1-160521
7.7
7.7
7.7
7.7
7.8
4
MCPTTR
MCVideo - Proposed new
requirements for video coding
MCVideo - Proposed new
requirements for video modes
MCVideo enhanced presence
MCVideo push and pull
MCVideo video storage control
Exception Sheet for MC Video
Exception Sheet for MC Video
Reply LS to RAN1 (cc RAN2,
SA2) on clarification of RSU
types
Wearable device using LTE
LS answer to SA5 on definition
of Network Service (S5156399)
MoI, France
MoI, France
MoI, France
Rapporteur
Rapporteur
SA1
040041rrr 4
S1-160522 Huawei
S1-160523 Huawei
010000
010100
1
1.1
S1-160524
S1-160525
S1-160526
S1-160527
S1-160528
S1-160529
Z-AgItem Z-AgItem
Z-AgItem Z-AgItem
010200
1.2
Z-AgItem Z-AgItem
010300
1.3
Z-AgItem Z-AgItem
010400
1.4
Z-AgItem Z-AgItem
010500
1.5
Z-AgItem Z-AgItem
010600
020000
1.6
2
Z-AgItem Z-AgItem
Z-AgItem Z-AgItem
030000
040000
3
4
Z-AgItem Z-AgItem
Z-AgItem Z-AgItem
050000
5
Z-AgItem Z-AgItem
060000
6
Z-AgItem Z-AgItem
070000
7
Z-AgItem Z-AgItem
070100
7.1
Z-AgItem Z-AgItem
070200
7.2
Z-AgItem Z-AgItem
070300
7.3
Z-AgItem Z-AgItem
070400
7.4
Z-AgItem Z-AgItem
070500
7.5
Z-AgItem Z-AgItem
1
Opening of the meeting
1.1
Agenda and
scheduling
1.2
IPR, antitrust and
competition laws
1.3
Previous SA1 meeting
report
1.4
Information for
delegates
1.5
Information for
rapporteurs
1.6
Working agreements
2
Issues for early
consideration
3
Reports and action items
4
Liaison Statements
(including related contributions)
5
New Study and Work
Items (including related
contributions)
6
Rel-13 and earlier
contributions
7
Rel-14 Work Item
contributions
7.1
MPS_Mods:
Multimedia Priority Service
(MPS) Modifications [SP150043]
7.2
ELIOT: Enhancing
Location Capabilities for Indoor
and Outdoor Emergency
Communications [SP-150044]
7.3
eULRS:
Enhancements to User Location
Reporting Support [SP-150540]
7.4
V2XLTE: LTE
support for V2X services [SP150541]
7.5
MCCore: Mission
28
pCR
Revision of S1-160441
Agreed.
pCR
Revision of S1-160442
Agreed.
pCR
pCR
pCR
ES
ES
LS out
Revision of S1-160349
Revision of S1-160447
Revision of S1-160461
Agreed.
WID
LS out
Revision of S1-160286
Revision of S1-160327
To be sent after the TR is available.
Agreed.
Agreed.
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
070600
7.6
Z-AgItem Z-AgItem
070700
7.7
Z-AgItem Z-AgItem
070800
7.8
Z-AgItem Z-AgItem
070900
7.9
Z-AgItem Z-AgItem
071000
7.10
Z-AgItem Z-AgItem
071100
7.11
Z-AgItem Z-AgItem
080000
080100
8
8.1
Z-AgItem Z-AgItem
Z-AgItem Z-AgItem
080200
8.2
Z-AgItem Z-AgItem
080300
8.3
Z-AgItem Z-AgItem
080400
8.4
Z-AgItem Z-AgItem
080500
8.5
Z-AgItem Z-AgItem
080600
8.6
Z-AgItem Z-AgItem
090000
9
Z-AgItem Z-AgItem
090100
090200
9.1
9.2
Z-AgItem Z-AgItem
Z-AgItem Z-AgItem
090300
9.3
Z-AgItem Z-AgItem
090400
100000
100100
110000
120000
9.4
10
10.1
11
12
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Critical Services Common
Requirements [SP-150822]
7.6
MCPTT-R: Mission
Critical Push to Talk over LTE
Realignment [SP-150821]
7.7
MCVideo: Mission
Critical Video over LTE [SP150849]
7.8
MCData: Mission
Critical Data over LTE [SP150850]
7.9
EnTV: 3GPP
Enhancement for TV service
[SP-150756]
7.10
PS_Data_Off: 3GPP
PS Data Off [SP-150823]
7.11
Other Rel-14 Work
Item contributions and CRs
8
Study Item contributions
8.1
FS_Smarter: New
Services and Markets
Technology Enablers [SP150142]
8.2
FS_SMARTER-mIoT:
Study on New Services and
Markets Technology Enablers massive Internet of Things [SP150817]
8.3
FS_SMARTERCRIC: Study on SMARTER
Critical Communications [SP150818]
8.4
FS_SMARTEReMBB: Study New Services
and Markets Technology
Enablers - enhanced Mobile
Broadband [SP-150819]
8.5
FS_SMARTER-NEO:
Study on New Services and
Markets Technology Enablers –
Network Operation [SP150820]
8.6
Other Study Item
contributions
9
Work planning
contributions
9.1
Work Plan
9.2
Work Item/Study Item
status update
9.3
SA1 process
improvements/updates
9.4
Others
10
Next meetings
10.1
Calendar
11
Any other business
12
Close
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
2016 meetings:
SA1#74
9-13 May 2016
SA1#75
22-26 Aug 2016
SA1#76
7-11 Nov 2016
Venice, Italy (TBC)
San Francisco, US (TBC)
Tenerife, Spain (TBC)
2017 meetings: to be confirmed
29
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
Z-AgItem
SA1#77
13-17 Feb 2017
SA1#78
8-12 May 2017
SA1#79
21-25 Aug 2017
SA1#80 27 Nov – 1 Dec 2017
Last allocated CR number:
Spec
CR
22.001
8
22.004
13
22.011
234
22.016
13
22.030
19
22.038
44
22.041
21
22.057
10
22.060
30
22.071
82
22.078
193
22.101
514
22.105
58
22.115
81
22.129
30
22.140
47
22.141
22
22.146
62
22.153
31
22.168
6
22.173
22.174
22.179
22.182
22.220
22.228
22.233
22.234
22.246
22.259
22.268
22.278
22.279
22.340
22.368
22.468
22.519
22.803
22.805
22.806
22.808
22.809
22.816
22.828
22.852
22.853
22.871
113
10
36
23
159
212
35
32
29
16
47
223
3
7
156
13
Asia (TBD)
Europe (TBD)
Asia (TBD)
US (TBD)
Mega-meeting
Principles of circuit telecommunication services supported by a PLMN
General on supplementary services
Service accessibility
International Mobile station Equipment Identities (IMEI)
(U)SIM Application Toolkit (USAT); Service description; Stage 1
Operator Determined Barring (ODB)
Mobile Execution Environment (MExE); Service description; Stage 1
General Packet Radio Service (GPRS); Service description; Stage 1
Location Services (LCS); Service description; Stage 1
Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description; Stage 1
Service aspects; Service principles
Services and service capabilities
Service aspects; Charging and billing (76 pb)
Service aspects; Handover requirements between UTRAN and GERAN or other radio systems
Multimedia Messaging Service (MMS); Stage 1
Presence service; Stage 1
Multimedia Broadcast/Multicast Service (MBMS); Stage 1
Multimedia priority service
ETWS, replaced by PWS for later releases
IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services;
Stage 1
Push Service; Service aspects; Stage 1
MCPTT
Customized Alerting Tones (CAT) requirements; Stage 1
Service requirements for Home Node B (HNB) and Home eNode B (HeNB)
Service requirements for the IMS; Stage 1
Transparent end-to-end packet-switched streaming service; Stage 1
Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking
Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1
Service requirements for Personal Network Management (PNM); Stage 1
Public Warning System (PWS) requirements
Service requirements for the Evolved Packet System (EPS)
Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1
IP Multimedia Subsystem (IMS) messaging; Stage 1
Service requirements for Machine-Type Communications (MTC); Stage 1
Business Communication Requirements (v1.0.0)
64
3
2
2
6
2
0
15
0
5
30
22.885
22.897
22.908
22.934
22.935
22.949
22.937
22.942
22.948
22.968
22.988
42.068
42.069
Nextfree
2
0
1
5
1
1
1
1
0
1
5
41
10
140350
"1","Opening of the meeting"
"1.1","Agenda and scheduling"
"1.2","IPR, antitrust and competition laws"
"1.3","Previous SA1 meeting report"
"1.4","Information for delegates"
"1.5","Information for rapporteurs"
"1.6","Working agreements"
"2","Issues for early consideration"
"3","Reports and action items"
"4","Liaison Statements (including related contributions)"
"5","New Study and Work Items (including related contributions)"
"6","Rel-13 and earlier contributions"
"7","Rel-14 Work Item contributions"
"7.1","MPS_Mods: Multimedia Priority Service (MPS) Modifications [SP-150043]"
"7.2","ELIOT: Enhancing Location Capabilities for Indoor and Outdoor Emergency Communications [SP-150044]"
"7.3","eULRS: Enhancements to User Location Reporting Support [SP-150540]"
"7.4","V2XLTE: LTE support for V2X services [SP-150541]"
"7.5","MCCore: Mission Critical Services Common Requirements [SP-150822]"
"7.6","MCPTT-R: Mission Critical Push to Talk over LTE Realignment [SP-150821]"
"7.7","MCVideo: Mission Critical Video over LTE [SP-150849]"
"7.8","MCData: Mission Critical Data over LTE [SP-150850]"
"7.9","EnTV: 3GPP Enhancement for TV service [SP-150756]"
"7.10","PS_Data_Off: 3GPP PS Data Off [SP-150823]"
"7.11","Other Rel-14 Work Item contributions and CRs"
"8","Study Item contributions"
"8.1","FS_Smarter: New Services and Markets Technology Enablers [SP-150142]"
"8.2","FS_SMARTER-mIoT: Study on New Services and Markets Technology Enablers - massive Internet of Things [SP-150817]"
"8.3","FS_SMARTER-CRIC: Study on SMARTER Critical Communications [SP-150818]"
"8.4","FS_SMARTER-eMBB: Study New Services and Markets Technology Enablers - enhanced Mobile Broadband [SP-150819]"
"8.5","FS_SMARTER-NEO: Study on New Services and Markets Technology Enablers – Network Operation [SP-150820]"
"8.6","Other Study Item contributions"
"9","Work planning contributions"
"9.1","Work Plan"
"9.2","Work Item/Study Item status update"
"9.3","SA1 process improvements/updates"
"9.4","Others"
"10","Next meetings"
"10.1","Calendar"
"11","Any other business"
"12","Close"
Types of Tdocs
agenda
Work Plan
LS in
Possible statuses of
Tdocs
reserved
available
revised
31
LS out
pCR
draftCR
agreed
conditionally agreed
approved
CR
conditionally
approved
CR pack
ToR
WID new
WID revised
SID new
SID revised
WI status report
WI exception request
TS or TR cover
draft TS
draft TR
report
discussion
response
other
1
1.1
1.2
1.3
1.4
1.5
1.6
2
3
4
5
6
7
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.11
8
8.1
8.2
8.3
8.4
partially approved
treated
endorsed
replied to
merged
not pursued
postponed
noted
not concluded
withdrawn
reissued
1
Opening of the meeting
1.1
Agenda and scheduling
1.2
IPR, antitrust and competition laws
1.3
Previous SA1 meeting report
1.4
Information for delegates
1.5
Information for rapporteurs
1.6
Working agreements
2
Issues for early consideration
3
Reports and action items
4
Liaison Statements (including related contributions)
5
New Study and Work Items (including related contributions)
6
Rel-13 and earlier contributions
7
Rel-14 Work Item contributions
7.1
MPS_Mods: Multimedia Priority Service (MPS) Modifications [SP-150043]
7.2
ELIOT: Enhancing Location Capabilities for Indoor and Outdoor Emergency
Communications [SP-150044]
7.3
eULRS: Enhancements to User Location Reporting Support [SP-150540]
7.4
V2XLTE: LTE support for V2X services [SP-150541]
7.5
MCCore: Mission Critical Services Common Requirements [SP-150822]
7.6
MCPTT-R: Mission Critical Push to Talk over LTE Realignment [SP-150821]
7.7
MCVideo: Mission Critical Video over LTE [SP-150849]
7.8
MCData: Mission Critical Data over LTE [SP-150850]
7.9
EnTV: 3GPP Enhancement for TV service [SP-150756]
7.10
PS_Data_Off: 3GPP PS Data Off [SP-150823]
7.11
Other Rel-14 Work Item contributions and CRs
8
Study Item contributions
8.1
FS_Smarter: New Services and Markets Technology Enablers [SP-150142]
8.2
FS_SMARTER-mIoT: Study on New Services and Markets Technology Enablers massive Internet of Things [SP-150817]
8.3
FS_SMARTER-CRIC: Study on SMARTER Critical Communications [SP-150818]
8.4
FS_SMARTER-eMBB: Study New Services and Markets Technology Enablers enhanced Mobile Broadband [SP-150819]
32
8.5
8.6
9
9.1
9.2
9.3
9.4
10
10.1
11
12
8.5
FS_SMARTER-NEO: Study on New Services and Markets Technology Enablers –
Network Operation [SP-150820]
8.6
Other Study Item contributions
9
Work planning contributions
9.1
Work Plan
9.2
Work Item/Study Item status update
9.3
SA1 process improvements/updates
9.4
Others
10
Next meetings
10.1
Calendar
11
Any other business
12
Close
33