Tdoc List

2018-05-11 14:46

Agenda Topic TDoc Title Source Type For Avail Treated Decision Wdrn Replaced-by Replaces
1 Opening of the meeting S1‑181637 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181649 Not used Not used other discussion No
No
withdrawn Yes    
1.1 Agenda and scheduling S1‑181000 Draft Agenda for SA1#82 Chair agenda Information No
Yes
revised No S1‑181001  
    S1‑181001 2nd draft Agenda for SA1#82 Chair agenda Information Yes
Yes
revised No   S1‑181000
    S1‑181002 Final Schedule and Agenda with document allocation for SA1#82 Chair agenda Approval Yes
Yes
agreed No    
1.2 IPR, antitrust and competition laws                      
1.3 Previous SA1 meeting report S1‑181004 Draft minutes of SA1#81 MCC report Information Yes
Yes
revised No S1‑181005  
    S1‑181005 Final minutes of SA1#81 MCC report Information Yes
Yes
approved No   S1‑181004
1.4 Information for delegates                      
1.5 Information for rapporteurs                      
1.6 Working agreements                      
2 Reports and action items S1‑181003 Report of SA1 topics at SA#80 Chair report Information Yes
Yes
The items of interest for SA1 are:
ATIS ELOC
5G Voice call continuity
Discussion on legacy USIM
GSMA RILTE LS
RAN report (SP-180243)
CT report (SP-180198)
Also the proposed new WID on FS_EPCO (Study on Extended Provision of Connectivity Opportunities) was noted and not approved.
The new WID on FS_V2XIMP was revised.
noted No    
3 Liaison Statements (including related contributions) S1‑181140 LS on Removal of LTE specific terminology from Group Communication System Enabler TS 22.468 Nokia LS out Agreement Yes
Yes
This is to notify all the groups in destination about the changes in 1381.
CRs in 1671 and 1381 to be added.
revised No S1‑181249  
    S1‑181249 LS on Removal of LTE specific terminology from Group Communication System Enabler TS 22.468 Nokia LS out Agreement Yes
Yes
agreed No   S1‑181140
    S1‑181324 Removal of “UE configued for Delay Tolerant Service” condition for Unified Access Control Qualcomm Incorporated CR discussion Yes
Yes
Another approach is not to change anything in the SA1 specs.
noted No    
    S1‑181353 LS to 3GPP on QoS Prediction 5GAA_A-180156_NESQO LS in discussion Yes
Yes
Proposed answer in S1-181644 to let them know about SA1 progress related to this topic.
noted No    
    S1‑181644 LS answer to 3GPP on QoS Prediction LG Electronics LS out discussion Yes
Yes
Proposed answer to S1-181353
CRs to be added
revised No S1‑181742  
    S1‑181742 LS answer to 3GPP on QoS Prediction LG Electronics LS out discussion Yes
Yes
agreed No   S1‑181644
    S1‑181354 5G for Industrial Communication 5G-ACIA LS in discussion Yes
Yes
S1-181645 was initially allocated for an answer.
SA1 expect that SA will answer to this LS.
All the related CRs and WIDs will be approved by that time.
 
noted No    
    S1‑181645 5G for Industrial Communication 5G-ACIA LS out discussion No
Yes
Proposed answer to S1-181354
This is proposed to be answered directly by SA, when CyberCAV will be approved.
withdrawn Yes    
    S1‑181355 LS on RAN2 agreements on UAC for AS triggered events R2-1806231 LS in discussion Yes
Yes
noted No    
    S1‑181356 LS to 3GPP WG SA, TC ITS, TC RT, TC BRAN on TC RRS WI " Feasibility Study of a Radio Interface Engine" ETSI RRS(17)040038r2 LS in discussion Yes
Yes
Same as 1260.
withdrawn Yes    
    S1‑181357 LS on typical media bandwidths S4-AHI793 LS in discussion Yes
Yes
Qualcomm will keep this list for SA1's future references.
noted No    
    S1‑181571 LS on multi-device requirements GSMA RILTE_65 Doc 108 LS in discussion Yes
Yes
See related CR in 1382
noted No    
3.1 LSs on Mission Critical S1‑181270 LS on MC services over IOPS S6-180718 LS in   Yes
Yes
The items to be studied mentioned in the LS are an initial attempt at SA6 to prioritise their work.
Proposed answer in 1009.
noted No    
    S1‑181009 Suggested reply LS on MC services over IOPS Ericsson LS out Approval Yes
Yes
To be revised to add text on "it should be clear to the user that he is using a network in IOPS mode".
Tdoc numbers to be updated.
revised No S1‑181346  
    S1‑181346 Suggested reply LS on MC services over IOPS SA1 LS out Approval Yes
Yes
agreed No   S1‑181009
3.2 LSs on Secure storage S1‑181054 Clarification on secure storage and processing of subscription credentials KPN CR Agreement Yes
Yes
revised No S1‑181347  
    S1‑181347 Clarification on secure storage and processing of subscription credentials KPN CR Agreement Yes
Yes
The latest requirement ("Subscription identifier(s) and long term key(s) shall be stored and processed within a UE using a tamper resistant secure hardware component.") is not yet in Rel-16.
This can now be added.
Problem on the cover page
revised No S1‑181652 S1‑181054
    S1‑181651 Clarification on secure storage and processing of subscription credentials KPN CR Agreement Yes
Yes
Partly mirror of S1-181347
noted No    
    S1‑181652 Clarification on secure storage and processing of subscription credentials KPN CR Agreement Yes
Yes
KPN explains that "Subscription Identifiers" is the new wording that has been chosen to align to the SA3 terminology.
7 companies do not want to see "3GPP".
9 companies want to have "3GPP".
No possible agreement at this time.
noted No   S1‑181347
    S1‑181055 Reply-LS on secure storage and processing of subscription credentials KPN LS out Agreement Yes
Yes
revised No S1‑181348  
    S1‑181348 Reply-LS on secure storage and processing of subscription credentials KPN LS out Agreement Yes
Yes
revised No S1‑181653 S1‑181055
    S1‑181653 Reply-LS on secure storage and processing of subscription credentials KPN LS out Agreement Yes
Yes
noted No   S1‑181348
    S1‑181265 Reply-LS on secure storage and processing of subscription credentials S3-180851 LS in   Yes
Yes
NEC suggested that this definition could rather be put in 23.905, as to avoid to have a risk to have definitions in different places, in particular in SA1 and SA3.
The definition in SA1 documentation will be removed/aligned.
Proposed answer in 1055.
See CR in 1054 on this.
The requirement is not yet in Rel-16 so there is no alignment needed.
 
 No agreement on the corresponding CRs in 1651 to 53.
postponed No    
3.3 LSs on URLLC S1‑181172 Discussion on URLLC KPIs Vodafone Group Plc discussion Approval Yes
Yes
revised No S1‑181332  
    S1‑181332 Discussion on URLLC KPIs Vodafone Group Plc discussion Approval Yes
Yes
noted No   S1‑181172
    S1‑181219 [DRAFT] Reply LS on URLLC Nokia LS out   Yes
Yes
revised No S1‑181341  
    S1‑181341 [DRAFT] Reply LS on URLLC Nokia LS out - Yes
Yes
Poroposed answer to 1262.
See related CR in 1333
revised No S1‑181360 S1‑181219
    S1‑181221 Clarifications on communication service availability and reliability Nokia, Nokia Shanghai Bell CR   Yes
Yes
"node" to be changed into "system entity". Typo on the cover page.
revised No S1‑181361  
    S1‑181360 [DRAFT] Reply LS on URLLC Nokia LS out - Yes
Yes
CRs to be attached, "draft" to be removed
revised No S1‑181657 S1‑181341
    S1‑181361 Clarifications on communication service availability and reliability Nokia, Nokia Shanghai Bell CR - Yes
Yes
agreed No   S1‑181221
    S1‑181657 Reply LS on URLLC SA1 LS out - Yes
Yes
agreed No   S1‑181360
    S1‑181222 Clarifications on communication service availability and reliability Nokia, Nokia Shanghai Bell CR   Yes
Yes
Same change as 1221
revised No S1‑181362  
    S1‑181362 Clarifications on communication service availability and reliability Nokia, Nokia Shanghai Bell CR - Yes
Yes
It is not exactly a mirror of the other one, so it cannot be category A.
revised No S1‑181656 S1‑181222
    S1‑181656 Clarifications on communication service availability and reliability Nokia, Nokia Shanghai Bell CR - Yes
Yes
Incorrect WID on the coverpage.
revised No S1‑181740 S1‑181362
    S1‑181740 Clarifications on communication service availability and reliability Nokia, Nokia Shanghai Bell CR - Yes
Yes
agreed No   S1‑181656
    S1‑181262 Reply LS on URLLC S2-183015 LS in   Yes
Yes
noted No    
3.4 LSs on PS Data Off S1‑181252 Reply LS on Change default exempt status for BIP with respect to 3GPP PS Data Off feature C1-182783 LS in   Yes
Yes
T-Mobile clarified that any given operator cannot answer to a question which is asked to all operators: one operator can answer for himself.
Proposed answer in S1-181363
noted No    
    S1‑181363 Reply LS on Change default exempt status for BIP with respect to 3GPP PS Data Off feature Qualcomm/SA1 LS out - Yes
Yes
Proposed answer to S1-181252
agreed No    
    S1‑181259 LS on PS Data Off for 5G GSMA RILTE #64 LS in   Yes
Yes
This was taken already into account by SA2.
noted No    
3.5 LSs on other topics S1‑181256 LS on Archiving PRDs GSMA NG#6 LS in   Yes
Yes
noted No    
    S1‑181260 LS on TC RRS WI " Feasibility Study of a Radio Interface Engine" ETSI RRS(17)040038r2 LS in   Yes
Yes
noted No    
    S1‑181263 LS on UE WLAN MAC address inclusion in E911 location information S2-183032 LS in   Yes
Yes
Supseded by 1273.
noted No    
    S1‑181264 LS on Delay Tolerant Access and Low Access Priority in 5GS S2-184558 LS in   Yes
Yes
Proposed answer in 1364
noted No    
    S1‑181364 LS on Delay Tolerant Access and Low Access Priority in 5GS Qualcomm LS out - Yes
Yes
Proposed answer to 1264
agreed No    
    S1‑181273 LS on Guidance on UE WiFi MAC Address inclusion in LTE Positioning Protocol SP-180234 LS in   Yes
Yes
noted No    
3.6 LSs in cc S1‑181250 Reply LS on SoR mechanism C1-182490 LS in   Yes
Yes
noted No    
    S1‑181251 LS on modification of solution for PLMN and RAT selection policies for roaming based on SA2 comments C1-182779 LS in   Yes
Yes
noted No    
    S1‑181253 Reply LS on SoR mechanism C1-182829 LS in   Yes
Yes
noted No    
    S1‑181254 Reply LS on SoR mechanism C1-182830 LS in   Yes
Yes
noted No    
    S1‑181255 LS on NGMN Paper on 5G End-to-End Architecture Framework NGMN LS in   Yes
Yes
noted No    
    S1‑181257 Reply LS on CT1's chosen solution for unified access control R2-1803939 LS in   Yes
Yes
noted No    
    S1‑181258 Reply LS on NR interworking with GSM and UMTS R4-1802691 LS in   Yes
Yes
noted No    
    S1‑181261 Reply LS on PLMN and RAT selection policies for roaming S2-182723 LS in   Yes
Yes
noted No    
    S1‑181266 LS on SoR mechanism S3-180998 LS in   Yes
Yes
noted No    
    S1‑181267 Reply LS on SoR mechanism S3-181501 LS in   Yes
Yes
noted No    
    S1‑181268 LS on SoR mechanism S3i180141 LS in   Yes
Yes
noted No    
    S1‑181269 LS on the transmission of video over PC5 interface S4-180633 LS in   Yes
Yes
noted No    
    S1‑181271 LS/o on the results of the 1st meeting of the ITU-T Focus Group on Machine Learning for Future Networks including 5G (FG ML5G) ITU-T FG ML5G-0-004 LS in   Yes
Yes
noted No    
    S1‑181272 Reply LS on Establishment of SAE Cellular V2X Technical Committee and Associated Task Forces SP-180215 LS in   Yes
Yes
noted No    
4 New Study and Work Items (including related contributions) S1‑181340 Support information for 1023 EBU discussion discussion Yes
Yes
noted No    
    S1‑181023 Feasibility Study on Audio-Visual Service Production (FS_AVPROD) EBU SID new Agreement Yes
Yes
More supporting companies.
Title of the TR to be aligned with the title of the WID.
revised No S1‑181365  
    S1‑181365 Feasibility Study on Audio-Visual Service Production (FS_AVPROD) EBU SID new Agreement Yes
Yes
agreed No   S1‑181023
    S1‑181014 New WID on the Integration of Satellite Access in 5G THALES WID new Agreement Yes
Yes
revised No S1‑181493  
    S1‑181025 Extreme Long Range Communications – Discussion paper Orange discussion   Yes
Yes
revised No S1‑181327  
    S1‑181493 New WID on the Integration of Satellite Access in 5G THALES WID new Agreement Yes
Yes
revised No S1‑181600 S1‑181014
    S1‑181600 New WID on the Integration of Satellite Access in 5G THALES WID new Agreement Yes
Yes
Status Report in S1-181718
agreed No   S1‑181493
    S1‑181327 Extreme Long Range Communications – Discussion paper Orange discussion - Yes
Yes
This could be for Rel-17.
Interested companies are invited to contact Orange.
noted No   S1‑181025
    S1‑181028 Discussion on inter-RAT mobility requirements for realtime service OPPO, China Mobile, China Telecom, Alibaba Inc., CATT, CATR, ZTE, Huawei? WID new Discussion Yes
Yes
noted No    
    S1‑181026 WID on inter-RAT Mobility requirements for real time service OPPO, China Mobile, China Telecom, Alibaba Inc., CATT, CATR, ZTE, Huawei? WID new Approval Yes
Yes
Qualcomm clarified that RAN2 is going to propose a set of Rel-16 enhancements related to mobility, and this would be one of them.
revised No S1‑181369  
    S1‑181369 WID on inter-RAT Mobility requirements for real time service China Mobile, China Telecom, OPPO, Alibaba Inc., CATT, CATR, ZTE, Spreadtrum Communications WID new Approval Yes
Yes
Changes performed as requested.
Revision marks still appearing.
Wrong meeting date.
Acronym is too long.
Related CR in 1370.
revised No S1‑181658 S1‑181026
    S1‑181658 WID on inter-RAT Mobility requirements for real time service China Mobile, China Telecom, OPPO, Alibaba Inc., CATT, CATR, ZTE, Spreadtrum Communications WID new Approval Yes
Yes
Acronym changed to "MOBRT"
agreed No   S1‑181369
    S1‑181027 CR-Inter-RAT Mobility requirement for realtime service OPPO, China Mobile, China Telecom, Alibaba Inc., CATT, CATR, ZTE, Huawei? WID new Agreement Yes
Yes
This is linked to the WID in 1026.
revised No S1‑181370  
    S1‑181370 Inter-RAT Mobility requirement for realtime service OPPO, China Mobile, China Telecom, Alibaba Inc., CATT, CATR, ZTE CR Agreement Yes
Yes
Wrong date, CR number missing
WID should be Mob_Realtime .
Summary of change is too long.
revised No S1‑181659 S1‑181027
    S1‑181659 Inter-RAT Mobility requirement for realtime service OPPO, China Mobile, China Telecom, Alibaba Inc., CATT, CATR, ZTE CR Agreement Yes
Yes
agreed No   S1‑181370
    S1‑181029 Discussion on Network Controlled Interactive Service in 5GS OPPO discussion Discussion Yes
Yes
See actual SID in 1030.
noted No    
    S1‑181030 Study on Network Controlled Interactive Service in 5GS OPPO SID new   Yes
Yes
The aim of this work is to study the use cases and to derive potential service requirements to provide users with interactive services
revised No S1‑181371  
    S1‑181371 Study on Network Controlled Interactive Service in 5GS OPPO SID new - Yes
Yes
Status report in S1-181661
agreed No   S1‑181030
    S1‑181044 WID on MARCOM SyncTechno Inc. WID new Approval Yes
Yes
revised No S1‑181598  
    S1‑181598 New WID on Maritime Communication Services over 3GPP System (MARCOM) SyncTechno Inc., Korean Register of shipping WID new Approval Yes
Yes
Several updates needed, in particular with respect to the impacted specs.
revised No S1‑181691 S1‑181044
    S1‑181691 New WID on Maritime Communication Services over 3GPP System (MARCOM) SyncTechno Inc., Korean Register of shipping WID new Approval Yes
Yes
Status Report in S1-181692
agreed No   S1‑181598
    S1‑181060 new WID on LAN support in 5G KPN WID new Agreement Yes
Yes
Some more editorial corrections to be done, more supporting companies.
See related CR in 1075.
revised No S1‑181372  
    S1‑181372 new WID on LAN support in 5G (5GLAN) KPN WID new Agreement Yes
Yes
More companies added, several improvements made offline.
Status report in S1-181662
CR in 1373
agreed No   S1‑181060
    S1‑181075 5GLAN Requirements KPN CR Agreement Yes
Yes
All the text should be shown as added text with revision marks.
revised No S1‑181373  
    S1‑181373 5GLAN Requirements KPN CR Agreement Yes
Yes
Withdrawn for this meeting by the author since it needs further work on FS_5GLAN.
noted No   S1‑181075
    S1‑181070 Support of streaming services ZTE Wistron Telecom AB CR   No
Yes
withdrawn Yes    
    S1‑181087 Enhancement of LTE for Efficient delivery of Streaming Service (eLESTR) China Telecomunication Corp. WID new   Yes
Yes
The supporting companies have to confirm their suypport, since the present list is the one for the FS.
The TR should not be mentioned as output.
revised No S1‑181375  
    S1‑181375 Enhancement of LTE for Efficient delivery of Streaming Service China Telecomunication Corp. WID new - Yes
Yes
revised No S1‑181665 S1‑181087
    S1‑181665 Enhancement of LTE for Efficient delivery of Streaming Service China Telecomunication Corp. WID new - Yes
Yes
Status Report in 1306.
Agreed then one company added as supporting company.
revised No S1‑181753 S1‑181375
    S1‑181753 Enhancement of LTE for Efficient delivery of Streaming Service China Telecomunication Corp. WID new - No
Yes
agreed No   S1‑181665
    S1‑181071 Support of streaming services ZTE Wistron Telecom AB CR   Yes
Yes
WID should be "eLESTR".
Formatting needed.
A 800 series TR cannot be added as reference.
revised No S1‑181376  
    S1‑181376 Support of streaming services ZTE Corporation, China Telecom, CATT CR - Yes
Yes
The CR shows a deleteion of section 2, which is not the intention.
Some more clarifications are needed and typos to be corrected.
revised No S1‑181667 S1‑181071
    S1‑181072 Charging for streaming services ZTE Wistron Telecom AB CR   Yes
Yes
Same on the WID.
A 800 series TR cannot be added as reference.
revised No S1‑181377  
    S1‑181667 Support of streaming services ZTE Corporation, China Telecom, CATT CR - Yes
Yes
"e.g. the MVNOs with network sharing" to be changed in "e.g. MVNOs or network sharing".
Changes on changes.
revised No S1‑181750 S1‑181376
    S1‑181377 Charging for streaming services (PDBDT) ZTE Corporation, China Telecom, CATT CR - Yes
Yes
Same problem on Section 2.
Rev marks on the cover page to be removed.
"needs to be" to be changed in "shall be".
revised No S1‑181668 S1‑181072
    S1‑181750 Support of streaming services ZTE Corporation, China Telecom, CATT CR - No
Yes
agreed No   S1‑181667
    S1‑181668 Charging for streaming services (PDBDT) ZTE Corporation, China Telecom, CATT CR - Yes
Yes
A reference has to be added.
Wrong styles.
revised No S1‑181751 S1‑181377
    S1‑181751 Charging for streaming services (PDBDT) ZTE Corporation, China Telecom, CATT CR - No
Yes
agreed No   S1‑181668
    S1‑181112 New WID on Policy delivery to UE for background data transfer KDDI Corporation WID new Agreement Yes
Yes
revised No S1‑181366  
    S1‑181366 New WID on Policy delivery to UE for background data transfer KDDI Corporation WID new Agreement Yes
Yes
revised No S1‑181379 S1‑181112
    S1‑181379 New WID on Policy delivery to UE for background data transfer (PDBDT) KDDI, NEC WID new Agreement Yes
Yes
revised No S1‑181669 S1‑181366
    S1‑181669 New WID on Policy delivery to UE for background data transfer (PDBDT) KDDI, NEC WID new Agreement Yes
Yes
New Status Report in S1-181670
agreed No   S1‑181379
    S1‑181113 User Identities and Authentication Deutsche Telekom AG WID new Agreement Yes
Yes
revised No S1‑181519  
    S1‑181519 User Identities and Authentication Deutsche Telekom AG WID new Agreement Yes
Yes
revised No S1‑181687 S1‑181113
    S1‑181687 User Identities and Authentication Deutsche Telekom AG WID new Agreement Yes
Yes
Status Report in S1-181688
agreed No   S1‑181519
    S1‑181114 Policy delivery to UE for background data transfer KDDI Corporation CR Agreement Yes
Yes
revised No S1‑181367  
    S1‑181367 Policy delivery to UE for background data transfer KDDI, TOYOTA ITC, NTT DOCOMO, cisco, Vodafone CR Agreement Yes
Yes
Still revision on revision, and rev marksshown on the cover page.
revised No S1‑181380 S1‑181114
    S1‑181380 Policy delivery to UE for background data transfer KDDI, TOYOTA ITC, NTT DOCOMO, Cisco, Vodafone, NEC CR Agreement Yes
Yes
"core" to be removed in "5G core network" to be consistent with the rest of the CR.
It is wonderd if this is specific to IoT. If not, it can be moved to a more general section.
revised No S1‑181671 S1‑181367
    S1‑181671 Policy delivery to UE for background data transfer KDDI, TOYOTA ITC, NTT DOCOMO, Cisco, Vodafone, Ericsson, SK Telecom, Intel, NEC, Huawei CR Agreement Yes
Yes
agreed No   S1‑181380
    S1‑181138 Update MCOver WID to allow 22.468 update Nokia WID revised Agreement Yes
Yes
agreed No    
    S1‑181179 New WID on multi-device and multi-identity (MuD) Ericsson, Orange WID new Agreement Yes
Yes
This is linked to an incoming LS from GSMA RILTE not yet received.
The objective of this work item is to add service requirements for the multi-device and multi-identity use cases as described above.
Revised in advance to take into account of the comments to be made by delegates.
The relationship with LUCIA is explained to be the following:
Here, it is a user having multiple devices.
Whereas with Lucia, it was the opposite: a device can be used by different users.
The WID title is "multi-device" but the WID mentions also mutli-users. This has to be clarified.
It was also wondered why the changes impact 22.173 and not 22.228.
Vodafone supports the concept but has concerns with the wording.
revised No S1‑181382  
    S1‑181190 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
revised No S1‑181339  
    S1‑181382 New WID on multi-device and multi-identity (MuD) Ericsson, Orange WID new Agreement Yes
Yes
WID related to the incoming LS in S1-181571.
The check is missing on UICC and AN.
revised No S1‑181639 S1‑181179
    S1‑181639 New WID on multi-device and multi-identity (MuD) Ericsson, Orange WID new Agreement Yes
Yes
Status report in S1-181666.
Agreed then one more supporting company.
revised No S1‑181699 S1‑181382
    S1‑181699 New WID on multi-device and multi-identity (MuD) Ericsson, Orange WID new Agreement Yes
Yes
agreed No   S1‑181639
    S1‑181339 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
revised No S1‑181472 S1‑181190
    S1‑181472 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) (cyberCAV) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
Rev marks to be approved, more companies to be added
SA6 impact could be added for APIs
Title of the new TS to begin with "Service requirements for…"
"exclusive and private networks" to be replaced by "type-a and type-b"
revised No S1‑181550 S1‑181339
    S1‑181550 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) (cyberCAV) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
revised No S1‑181701 S1‑181472
    S1‑181701 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) (cyberCAV) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
revised No S1‑181713 S1‑181550
    S1‑181713 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) (cyberCAV) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
Some further editorial clean-up needed
Huawe, Vodafone, Telecom Italiai and Deutsche Telekom to be added as supporting companies
revised No S1‑181744 S1‑181701
    S1‑181744 New WID on Service Requirements for Cyber-Physical Control Applications in Vertical Domains (Release 16) (cyberCAV) Siemens AG, China Southern Power Grid Co., Robert Bosch GmbH WID new Agreement Yes
Yes
Status Report n S1-181745
revised No   S1‑181713
    S1‑181208 Inclusion of ethernet transport services in TS 22.261 Qualcomm Incorporated, Siemens CR Agreement Yes
Yes
revised No S1‑181374  
    S1‑181223 Making the Case (again) for a Work Item on service requirements for enabling cyber-physical control applications Siemens AG discussion Discussion Yes
Yes
revised No S1‑181338  
    S1‑181374 Inclusion of ethernet transport services in TS 22.261 Qualcomm Incorporated, Siemens CR Agreement Yes
Yes
2nd part in S1-181638.
Should have been rev1.
Two more requirements to be included, the two last ones from 1638.
revised No S1‑181663 S1‑181208
    S1‑181663 Inclusion of ethernet transport services in TS 22.261 Qualcomm Incorporated, Siemens CR Agreement Yes
Yes
Huawei to be added as co-author
revised No S1‑181547 S1‑181374
    S1‑181547 Inclusion of ethernet transport services in TS 22.261 Qualcomm Incorporated, Siemens, Huawei CR Agreement Yes
Yes
agreed No   S1‑181663
    S1‑181338 Making the Case (again) for a Work Item on service requirements for enabling cyber-physical control applications Siemens AG discussion Discussion Yes
Yes
noted No   S1‑181223
    S1‑181226 New WID on 5G positioning services ESA WID new Approval Yes
Yes
revised No S1‑181495  
    S1‑181495 New WID on 5G positioning services ESA WID new Approval Yes
Yes
revised No S1‑181607 S1‑181226
    S1‑181607 New WID on 5G positioning services (HYPOS) ESA WID new Approval Yes
Yes
Status Report in S1-181726
revised No   S1‑181495
    S1‑181236 cyberCAV TS skeleton Siemens AG draft TS Agreement Yes
Yes
revised No S1‑181473  
    S1‑181473 cyberCAV TS skeleton Siemens AG draft TS Agreement Yes
Yes
"Annex" should be spelt as per 3GPP drafting rules.
Title to be aligned as per 1550.
revised No S1‑181551 S1‑181236
    S1‑181551 cyberCAV TS skeleton Siemens AG draft TS Agreement Yes
Yes
To be used as a basis for the new TS in 1552
revised No   S1‑181473
    S1‑181237 Multi-device requirements Ericsson, Orange CR Agreement Yes
Yes
CR relating to the WID in 1382.
revised No S1‑181383  
    S1‑181383 Multi-device requirements Ericsson, Orange CR Agreement Yes
Yes
CR related to the incoming LS in S1-181571.
More companies are willing to co-sign.
Some rewording needed to enhance the clarity.
revised No S1‑181640 S1‑181237
    S1‑181640 Multi-device requirements Ericsson, Orange CR Agreement Yes
Yes
revised No S1‑181739 S1‑181383
    S1‑181739 Multi-device requirements Ericsson, Orange, Deutsche Telekom, Telecom Italia, China Unicom, LG Electronics, Vodafone, Huawei, Verizon UK Ltd CR Agreement Yes
Yes
agreed No   S1‑181640
    S1‑181393 Updated SMARTER_Ph2 WID Vodafone WID revised discussion Yes
Yes
Some rewording needed, in particular to delete or modify the sentence "In 3GPP SA1, this WID is not intended to add new Stage 1 service requirements."
revised No S1‑181675  
    S1‑181675 Updated SMARTER_Ph2 WID Vodafone WID revised discussion Yes
Yes
agreed No   S1‑181393
    S1‑181641 LS on Multi-Device and Multi-Identity Ericsson LS out Decision Yes
Yes
"draft" to be removed
revised No S1‑181642  
    S1‑181642 LS on Multi-Device and Multi-Identity SA1 LS out Decision Yes
Yes
agreed No   S1‑181641
    S1‑181643 LS on Multi-Device and Multi-Identity Ericsson LS out Decision Yes
Yes
CR to be attached
revised No S1‑181741  
    S1‑181741 LS on Multi-Device and Multi-Identity SA1 LS out Decision Yes
Yes
agreed No   S1‑181643
5 Rel-15 and earlier contributions                      
5.1 Release 15 Alignment CRs (aligning Stage 1 specifications with what has been implemented in Stage 2 and 3) S1‑181019 User profile presentation priority FirstNet, AT&T, Harris CR Agreement Yes
Yes
Some copy-paste error to be corrected in the next version.
revised No S1‑181384  
    S1‑181384 User profile presentation priority FirstNet CR Agreement Yes
Yes
agreed No   S1‑181019
    S1‑181068 Positioning Part align with Rel-15 5G NR Specification ZTE Wistron Telecom AB CR   Yes
Yes
"posoining" on the cover page instead of "positionning".
Rev marks on the cover page.
revised No S1‑181388  
    S1‑181388 Positioning Part align with Rel-15 5G NR Specification ZTE Wistron Telecom AB CR - Yes
Yes
agreed No   S1‑181068
    S1‑181139 Removal of LTE specific terminology from 22.468 Nokia CR Agreement Yes
Yes
"GCSE_LTE" will remain in Rel-12, 13 and 14.
Then it will become "GCSE" from Rel-15 onwards, when 5G will start to co-exist with 4G.
Some re-wording needed.
revised No S1‑181381  
    S1‑181381 Removal of LTE specific terminology from 22.468 Nokia, UIC CR Agreement Yes
Yes
agreed No   S1‑181139
    S1‑181161 Release 15 alignment on the inclusion of the 5G requirements Vodafone Group Plc CR   Yes
Yes
revised No S1‑181391  
    S1‑181391 Release 15 alignment on the inclusion of the 5G requirements Vodafone Group Plc CR - No
Yes
Replaced by 1646
withdrawn Yes   S1‑181161
    S1‑181164 Release 15 further alignment on URLLC KPIs Vodafone Group Plc CR Decision Yes
Yes
revised No S1‑181333  
    S1‑181333 Release 15 further alignment on URLLC KPIs Vodafone Group Plc CR Decision Yes
Yes
revised No S1‑181359 S1‑181164
    S1‑181359 Release 15 further alignment on URLLC KPIs Vodafone Group Plc CR Decision Yes
Yes
agreed No   S1‑181333
    S1‑181166 Release 15 alignment on the 5G requirements Vodafone Group Plc CR Approval Yes
Yes
This is an alignment CR to remove requirements for which no Stages 2 nor 3 were defined.
revised No S1‑181394  
    S1‑181394 Release 15 alignment on the 5G requirements Vodafone Group Plc CR Approval Yes
Yes
agreed No   S1‑181166
    S1‑181169 Release 15 further alignment on the URLLC KPIs Vodafone Group Plc CR Approval Yes
Yes
revised No S1‑181335  
    S1‑181335 Release 15 further alignment on the URLLC KPIs Vodafone Group Plc CR Approval Yes
Yes
revised No S1‑181358 S1‑181169
    S1‑181358 Release 15 further alignment on the URLLC KPIs Vodafone Group Plc CR Approval Yes
Yes
Wrong styles for the new proposed list.
revised No S1‑181654 S1‑181335
    S1‑181654 Release 15 further alignment on the URLLC KPIs Vodafone Group Plc CR Approval Yes
Yes
agreed No   S1‑181358
    S1‑181177 Alignment of RLOS availability into Automatic PLMN Selection Nokia Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
agreed No    
    S1‑181178 Alignment of requirements for access to restricted local operator services Nokia, Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
agreed No    
    S1‑181180 Alignment of Charging for Restricted Local Operator Services Nokia, Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
MCC should create a Rel-16 version of 22.115 before applying this CR to Rel-15, but after applying all other Rel 15 CRs.
agreed No    
    S1‑181181 Alignment of requirements for access to restricted local operator services Nokia, Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
agreed No    
    S1‑181182 Alignment of RLOS availability into Automatic PLMN Selection Nokia, Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
revised No S1‑181395  
    S1‑181395 Alignment of RLOS availability into Automatic PLMN Selection Nokia, Nokia Shanghai Bell, Sprint, Verizon CR - Yes
Yes
agreed No   S1‑181182
    S1‑181183 Alignment of requirements for access to restricted local operator services Nokia, Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
Here again, MCC should apply all agreed Rel 15 CRs to create v15.5.0 before creating a Rel 16 version, which should include this CR.
Some clean-up is needed (yellow highlight, change over change)
revised No S1‑181396  
    S1‑181396 Alignment of requirements for access to restricted local operator services Nokia, Nokia Shanghai Bell, Sprint, Verizon CR - Yes
Yes
agreed No   S1‑181183
    S1‑181185 Alignment of requirements for access to restricted local operator services Nokia, Nokia Shanghai Bell, Sprint, Verizon CR   Yes
Yes
agreed No    
    S1‑181646 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
Mirrors in S1-181647, 48.
"This is particularly relevant for Release 15 onwards (…)" is odd in a Rel-13 CR.
"transmission" to be correctly spelt.
"to optimise the use of battery resources" can be changed into "to minimise"
This is indeed category F and not B since the Stages 2 and 3 already exist, so this is a correction and not an addition.
revised No S1‑181672  
    S1‑181647 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
Mirror of S1-181646
revised No S1‑181673  
    S1‑181672 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
agreed No   S1‑181646
    S1‑181648 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
Mirror of S1-181646
revised No S1‑181674  
    S1‑181673 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
revised No S1‑181737 S1‑181647
    S1‑181674 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
revised No S1‑181738 S1‑181648
    S1‑181737 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
agreed No   S1‑181673
    S1‑181738 Inclusion of the CIoT requirements Vodafone CR Decision Yes
Yes
agreed No   S1‑181674
5.2 Rel-15 correction and clarification CRs (other than alignment) S1‑181073 Clarification to access restriction LG Electronics Inc. CR   Yes
Yes
noted No    
    S1‑181074 Clarification to access restriction LG Electronics Inc. CR   Yes
Yes
noted No    
    S1‑181076 Clarification to forbidden TA LG Electronics Inc. CR   Yes
Yes
revised No S1‑181560  
    S1‑181560 Clarification to forbidden TA LG Electronics Inc. CR - Yes
Yes
agreed No   S1‑181076
    S1‑181077 Clarification to forbidden TA LG Electronics Inc. CR   Yes
Yes
revised No S1‑181561  
    S1‑181561 Clarification to forbidden TA LG Electronics Inc. CR - Yes
Yes
Wrong CR number on the cover page.
revised No S1‑181566 S1‑181077
    S1‑181566 Clarification to forbidden TA LG Electronics Inc. CR - Yes
Yes
agreed No   S1‑181561
    S1‑181128 Discussion paper regarding changing the RSU definition’s note Ericsson, Nokia, Huawei discussion Information Yes
Yes
revised No S1‑181349  
    S1‑181349 Discussion paper regarding changing the RSU definition’s note Ericsson, Nokia, Huawei, LG Electronics discussion Information Yes
Yes
noted No   S1‑181128
    S1‑181129 Update the note in the RSU definition Ericsson, Nokia, Huawei CR Agreement Yes
Yes
revised No S1‑181350  
    S1‑181350 Update the note in the RSU definition Ericsson, Nokia, Huawei, LG Electronics CR Agreement Yes
Yes
This is the CR for 22.886.
agreed No   S1‑181129
    S1‑181130 Update the note in the RSU definition Ericsson, Nokia, Huawei CR Agreement Yes
Yes
revised No S1‑181351  
    S1‑181351 Update the note in the RSU definition Ericsson, Nokia, Huawei, LG Electronics CR Agreement Yes
Yes
This is the CR for 22.186.
Changes on changes.
revised No S1‑181562 S1‑181130
    S1‑181562 Update the note in the RSU definition Ericsson, Nokia, Huawei, LG Electronics CR Agreement Yes
Yes
agreed No   S1‑181351
    S1‑181174 Alignment of 3GPP PWS specifications to recent FCC WEA regulation changes Sprint Corporation CR Agreement Yes
Yes
"wireless" is mis-spelt.
revised No S1‑181563  
    S1‑181563 Alignment of 3GPP PWS specifications to recent FCC WEA regulation changes Sprint Corporation CR Agreement Yes
Yes
agreed No   S1‑181174
    S1‑181176 Alignment of 3GPP PWS specifications to recent FCC WEA regulation changes Sprint Corporation CR Agreement Yes
Yes
Same typo.
revised No S1‑181564  
    S1‑181564 Alignment of 3GPP PWS specifications to recent FCC WEA regulation changes Sprint Corporation CR Agreement Yes
Yes
agreed No   S1‑181176
    S1‑181204 PARLOS Rel15 CR removal of shall_not_affect_UICC requirement Qualcomm Incorporated CR Agreement Yes
Yes
revised No S1‑181345  
    S1‑181345 PARLOS Rel15 CR removal of shall_not_affect_UICC requirement Qualcomm Incorporated CR Agreement Yes
Yes
Agreed, material to be incorporated in 1396.
noted No   S1‑181204
5.3 Release 14 Alignment CRs (aligning Stage 1 specifications with what has been implemented in Stage 2 and 3)                      
5.4 Other Rel-14 and earlier CRs S1‑181131 Update the note in the RSU definition Ericsson, Nokia, Huawei CR Agreement Yes
Yes
revised No S1‑181352  
    S1‑181352 Update the note in the RSU definition Ericsson, Nokia, Huawei, LG Electronics CR Agreement Yes
Yes
And this is the corresponding CR for 22.185.
agreed No   S1‑181131
    S1‑181203 Rel13 CR Per RAT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
revised No S1‑181565  
    S1‑181565 Rel13 CR Per RAT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
Rel-14 mirror in S1-181613
Rel-15 mirror in S1-181614
Rel-16 mirror in S1-181615
The Rel-13 and 14 are withdrawn.
UICC box to be ticked.
noted No   S1‑181203
    S1‑181613 Per RAT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
noted No    
    S1‑181614 Per RAT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
revised No S1‑181677  
    S1‑181615 Per RAT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
revised No S1‑181678  
    S1‑181677 IoT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
agreed No   S1‑181614
    S1‑181678 IoT periodic network selection attempt timers Qualcomm Incorporated CR Agreement Yes
Yes
agreed No   S1‑181615
6 Rel-16 Work Item contributions                      
6.1 MONASTERY2: Mobile Communication System for Railways 2 [SP-170451] S1‑181063 Addition of location functionality for autonomous train control and operation KRRI CR Agreement Yes
Yes
revised No S1‑181417  
    S1‑181417 Addition of location functionality for autonomous train control and operation KRRI CR Agreement Yes
Yes
revised No S1‑181580 S1‑181063
    S1‑181580 Addition of location functionality for autonomous train control and operation KRRI CR Agreement Yes
Yes
revised No S1‑181622 S1‑181417
    S1‑181622 Addition of location functionality for autonomous train control and operation KRRI CR Agreement Yes
Yes
wrong rev number
revised No S1‑181705 S1‑181580
    S1‑181705 Addition of location functionality for autonomous train control and operation KRRI CR Agreement Yes
Yes
agreed No   S1‑181622
    S1‑181064 Off-network UE functionality for virtual coupling KRRI CR Agreement Yes
Yes
revised No S1‑181418  
    S1‑181418 Off-network UE functionality for virtual coupling KRRI CR Agreement Yes
Yes
revised No S1‑181587 S1‑181064
    S1‑181587 Off-network UE functionality for virtual coupling KRRI CR Agreement Yes
Yes
revised No S1‑181623 S1‑181418
    S1‑181623 Off-network UE functionality for virtual coupling KRRI CR Agreement Yes
Yes
Wrong rev number, cat to be changed to F
revised No S1‑181706 S1‑181587
    S1‑181706 Off-network UE functionality for virtual coupling KRRI CR Agreement Yes
Yes
agreed No   S1‑181623
    S1‑181084 CR_22.282_ setup time requirement for monitoring and control of critical infrastrucuture communication CHENGDU TD TECH LTD. CR   Yes
Yes
revised No S1‑181421  
    S1‑181421 CR_22.282_ setup time requirement for monitoring and control of critical infrastrucuture communication CHENGDU TD TECH LTD. CR - Yes
Yes
revised No S1‑181585 S1‑181084
    S1‑181585 CR_22.282_ setup time requirement for monitoring and control of critical infrastrucuture communication CHENGDU TD TECH LTD. CR - Yes
Yes
Wrong name, not to be used for future CRs.
agreed No   S1‑181421
    S1‑181137 New definitions and abbreviations for TS22.289 Teleste Corporation, Nokia discussion Approval Yes
Yes
agreed No    
    S1‑181141 Adding functionality to 22.179 to support assured voice communication Nokia,UIC CR Agreement Yes
Yes
revised No S1‑181420  
    S1‑181420 Adding functionality to 22.179 to support assured voice communication Nokia,UIC CR Agreement Yes
Yes
Wrong tdoc number on the cover page
revised No S1‑181708 S1‑181141
    S1‑181708 Adding functionality to 22.179 to support assured voice communication Nokia,UIC CR Agreement Yes
Yes
agreed No   S1‑181420
    S1‑181142 Introduction of 22.889 FRMCS-user communication handling section into 22.280 Nokia, UIC CR Agreement Yes
Yes
noted No    
    S1‑181143 Removal of misleading term "temporary" from Automatic Regrouping of 22.280 Nokia, UIC CR Agreement Yes
Yes
noted No    
    S1‑181163 Adding authorization for group comunication based on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
revised No S1‑181409  
    S1‑181409 Adding authorization for group comunication based on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement No
Yes
withdrawn Yes   S1‑181163
    S1‑181167 Adding authorization for private comunication based on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
revised No S1‑181412  
    S1‑181412 Adding authorization for private comunication based on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
revised No S1‑181590 S1‑181167
    S1‑181590 Adding authorization for private comunication based on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
These new proposed sections have to be put last in the TR (after the ones proposed in other CRs impacting the same section).
agreed No   S1‑181412
    S1‑181168 Addition of location based comunication depending on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
revised No S1‑181411  
    S1‑181411 Addition of location based comunication depending on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
revised No S1‑181589 S1‑181168
    S1‑181589 Addition of location based comunication depending on functional alias Kapsch CarrierCom France S.A.S, UIC, Nokia Germany, Ericsson LM, Hansung University CR Agreement Yes
Yes
agreed No   S1‑181411
    S1‑181189 chapter_5_10 MCX User log in to multiple devices Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181406  
    S1‑181406 chapter_5_10 MCX User log in to multiple devices Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181582 S1‑181189
    S1‑181582 chapter_5_10 MCX User log in to multiple devices Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181406
    S1‑181191 Generalisation of EPS into 3GPP system Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181413  
    S1‑181413 Generalisation of EPS into 3GPP system Union Inter. Chemins de Fer CR Agreement Yes
Yes
Mirror in 1414
revised No S1‑181583 S1‑181191
    S1‑181414 Generalisation of EPS into 3GPP system Union Inter. Chemins de Fer CR Agreement Yes
Yes
Wrong CR number on the cover page
revised No S1‑181584  
    S1‑181583 Generalisation of EPS into 3GPP system Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181413
    S1‑181584 Generalisation of EPS into 3GPP system Union Inter. Chemins de Fer CR Agreement Yes
Yes
Mirror CR.
Wrong CR number on the cover page
revised No S1‑181704 S1‑181414
    S1‑181704 Generalisation of EPS into 3GPP system Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181584
    S1‑181192 Extension of functional alias chapter 5.9a Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181405  
    S1‑181405 Extension of functional alias chapter 5.9a Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181581 S1‑181192
    S1‑181581 Extension of functional alias chapter 5.9a Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181676 S1‑181405
    S1‑181676 Extension of functional alias chapter 5.9a Union Inter. Chemins de Fer CR Agreement Yes
Yes
changes on changes
revised No S1‑181700 S1‑181581
    S1‑181700 Extension of functional alias chapter 5.9a Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181676
    S1‑181210 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181419  
    S1‑181419 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181591 S1‑181210
    S1‑181591 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
Used by mistake by another document
revised No S1‑181655 S1‑181419
    S1‑181655 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
Requirements numbers are wrong.
revised No S1‑181707 S1‑181591
    S1‑181707 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181655
    S1‑181211 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181415  
    S1‑181415 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181588 S1‑181211
    S1‑181588 Interworking between MCX Service system and GSM-R Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181415
    S1‑181212 Chapter 5.3 use of functional alias in late communication entry Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181403  
    S1‑181403 Chapter 5.3 use of functional alias in late communication entry Union Inter. Chemins de Fer CR Agreement No
Yes
Merged with 1404 in 1676
withdrawn Yes   S1‑181212
    S1‑181213 Chapter 5.7 use of functional alias as part of MCX ServiceUser ID Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181404  
    S1‑181404 Chapter 5.7 use of functional alias as part of MCX ServiceUser ID Union Inter. Chemins de Fer CR Agreement No
Yes
Merged with 1403 in 1676
withdrawn Yes   S1‑181213
    S1‑181214 Chapter 5.17 use of functional alias as part of the MCX User identity Union Inter. Chemins de Fer CR Agreement Yes
Yes
noted No    
    S1‑181216 Chapter 6.4.3, 6.4.5, 6.9 use of functional alias as part of MCX Service User identification Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181410  
    S1‑181410 Chapter 6.4.3, 6.4.5, 6.9 use of functional alias as part of MCX Service User identification Union Inter. Chemins de Fer CR Agreement No
Yes
withdrawn Yes   S1‑181216
    S1‑181217 Chapter 7.1 and 7.2 use of functional alias in Off-network communication mode Union Inter. Chemins de Fer CR Agreement Yes
Yes
noted No    
    S1‑181218 Chapter 5.11 and chapter 6.12 obtaining positioning information from external systems and forwarding position information to external systems Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181407  
    S1‑181407 Chapter 5.11 and chapter 6.12 obtaining positioning information from external systems and forwarding position information to external systems Union Inter. Chemins de Fer CR Agreement No
Yes
withdrawn Yes   S1‑181218
    S1‑181220 New chapter 6.17.x functional alias resolution for non-MCX Service Users Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181416  
    S1‑181416 New chapter 6.17.x functional alias resolution for non-MCX Service Users Union Inter. Chemins de Fer CR Agreement No
Yes
withdrawn Yes   S1‑181220
    S1‑181244 Add a requirement on 5.11 Location ETRI, Hansung University CR   Yes
Yes
revised No S1‑181408  
    S1‑181408 Add a requirement on 5.11 Location ETRI, Hansung University CR - Yes
Yes
revised No S1‑181617 S1‑181244
    S1‑181617 Add a requirement on 5.11 Location ETRI, Hansung University CR - Yes
Yes
agreed No   S1‑181408
    S1‑181274 TR22.289v0.2.0 to include agreements at this meeting Rapporteur (Nokia) draft TR discussion Yes
Yes
Only one pCR was agreed at this meeting.
agreed No    
    S1‑181275 Railways drafting agenda Rapporteur / Session Chair agenda discussion Yes
Yes
agreed No    
    S1‑181276 Railways drafting report Rapporteur / Session Chair report discussion Yes
Yes
38 documents, 49 revisions were handled
revised No S1‑181631  
    S1‑181631 Railways drafting report Rapporteur / Session Chair report discussion Yes
Yes
agreed No   S1‑181276
    S1‑181632 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181633 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181634 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181635 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181636 Not used Not used other discussion No
No
withdrawn Yes    
6.2 enIMS: enhancements to IMS for new real time communication services [SP-180137] S1‑181090 IMS Network Slicing Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181431  
    S1‑181431 IMS Network Slicing Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181630 S1‑181090
    S1‑181630 IMS Network Slicing Huawei Telecommunication India CR Approval No
Yes
Replaced by 1694 since a CR against 22.261 is preferred.
withdrawn Yes   S1‑181431
    S1‑181091 IMS support for Group Communication fast call set up time Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181432  
    S1‑181432 IMS support for Group Communication fast call set up time China Mobile, Huawei CR Approval Yes
Yes
There are different opinions about having the reference or not.
"For LTE" to be removed.
First requirement to be removed.
Changes on changes to be updated
revised No S1‑181720 S1‑181091
    S1‑181720 IMS support for Group Communication fast call set up time China Mobile, Huawei CR Approval Yes
Yes
agreed No   S1‑181432
    S1‑181092 IMS support for Augmented Reality Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181433  
    S1‑181433 IMS support for Augmented Reality Huawei Telecommunication India CR Approval No
Yes
withdrawn Yes   S1‑181092
    S1‑181093 IMS support for VR Telepresence Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181434  
    S1‑181434 IMS support for VR Telepresence Huawei Telecommunication India CR Approval No
Yes
withdrawn Yes   S1‑181093
    S1‑181094 Interworking with non-sip devices (camera) Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181435  
    S1‑181435 Interworking with non-sip devices (camera) Huawei Telecommunication India CR Approval Yes
Yes
More off-line discussions are needed
revised No S1‑181721 S1‑181094
    S1‑181721 Interworking with non-sip devices (camera) Huawei Telecommunication India CR Approval No
Yes
withdrawn Yes   S1‑181435
    S1‑181095 Support for one to many communication Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181436  
    S1‑181436 Support for one to many communication Huawei Telecommunication India CR Approval No
Yes
withdrawn Yes   S1‑181095
    S1‑181096 IMS support for services using AI (voiceprint) Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181437  
    S1‑181437 IMS support for services using AI (voiceprint) Huawei, China Mobile CR Approval Yes
Yes
For Qualcomm and Sony, this is application/media handling, and this is not to be covered by 3GPP.
noted No   S1‑181096
    S1‑181097 IMS support for service visibility and usage Huawei Telecommunication India CR Approval Yes
Yes
noted No    
    S1‑181277 TR22.819v0.6.0 to include agreements at this meeting Rapporteur (SyncTechno) draft TR discussion No
Yes
withdrawn Yes    
    S1‑181278 Cover page for presentation of TR22.819v0.6.0 Rapporteur (SyncTechno) TS or TR cover discussion No
Yes
withdrawn Yes    
    S1‑181279 enIMS+QoS_MON+5GMSG+MPS drafting agenda Rapporteur / Session Chair agenda discussion Yes
Yes
agreed No    
    S1‑181280 MARCOM+HYPOS+5GSAT drafting report Rapporteur / Session Chair report discussion Yes
Yes
This session handled:
19 Documents treated
22 Revisions
2  Agreed
1  Noted
16 Carried over to Plenary
agreed No    
    S1‑181694 IMS Network Slicing China Mobile, Huawei, Deutsche Telekom CR Decision Yes
Yes
Replaces 1630.
"It is possible" is ambiguous in the Note.
"IMS networks slices" to be replaced by "IMS networks".
Nokia prefers to delete the entire note since they see it as a deployment issue. This is the preferred aproach.
The title is misleading.
revised No S1‑181719  
    S1‑181719 IMS and Network Slicing China Mobile, Huawei, Deutsche Telekom CR Decision No
Yes
agreed No   S1‑181694
6.3 SMARTER_Ph2: New Services and Markets Technology Enablers – Phase 2 [SP-180138] S1‑181069 Positioning Part align with Rel-15 structure ZTE Corporation, Vodafone CR   Yes
Yes
revised No S1‑181389  
    S1‑181389 Positioning Part align with Rel-15 structure ZTE Corporation, Vodafone CR - Yes
Yes
agreed No   S1‑181069
    S1‑181125 Proposal to keep requirements in clause 6.10.2 of TS 22.261 for Rel-16 NTT DOCOMO INC. discussion Agreement Yes
Yes
NTT DOCOMO just have to reject any CR that would request to modify the requirements in Rel-16.
noted No    
    S1‑181170 Release 16 alignment on the inclusion of the 5G requirements Vodafone Group Plc CR Approval Yes
Yes
revised No S1‑181392  
    S1‑181392 Release 16 alignment on the inclusion of the 5G requirements Vodafone, Telecom Italia CR Approval Yes
Yes
Typos to be corrected.
Sections not impacted to be removed.
This needs further thoughts between now and the next meeting.
It can be split in different CRs.
noted No   S1‑181170
    S1‑181171 Release 16 alignment on URLLC KPIs Vodafone Group Plc CR Approval Yes
Yes
revised No S1‑181334  
    S1‑181334 Release 16 alignment on URLLC KPIs Vodafone Group Plc CR Approval Yes
Yes
Mirror CR of 1333.
Not needed since there is no Rel-16 version of 22.278 yet
noted No   S1‑181171
6.4 QoS_MON: QoS Monitoring [SP-180141] S1‑181099 QoS Monitoring Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181438  
    S1‑181438 QoS Monitoring Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181559 S1‑181099
    S1‑181559 QoS Monitoring Huawei Telecommunication India CR Approval Yes
Yes
wrong rev number, changes on changes
revised No S1‑181714 S1‑181438
    S1‑181714 QoS Monitoring Huawei Telecommunication India CR Approval Yes
Yes
agreed No   S1‑181559
6.5 Other Rel-16 CRs under TEI16 S1‑181020 User profile presentation priority FirstNet, AT&T, Harris CR Agreement Yes
Yes
This is a "conceptual mirror" even if the text to be modified is not exactly the same. This can be clarified in the "other comments" field.
revised No S1‑181385  
    S1‑181385 User profile presentation priority FirstNet, AT&T, Harris CR Agreement Yes
Yes
agreed No   S1‑181020
    S1‑181061 Update of the content to reflect new sections for ePWS SyncTechno Inc. CR Approval Yes
Yes
The ToC was forgotten to be updated.
This will be done next time.
noted No    
7 Study Item contributions S1‑181089 Services using AI (instant translation) in real time communication Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181430  
    S1‑181430 Services using AI (instant translation) in real time communication Huawei Telecommunication India CR Approval Yes
Yes
revised No S1‑181626 S1‑181089
    S1‑181626 Services using AI (instant translation) in real time communication Huawei Telecommunication India CR Approval Yes
Yes
Same comment applies about media handling, being out of scope of 3GPP for Qualcomm.
The case of emergency call can be more clearly separated from the general case.
Changes on changes, Note to be added.
revised No S1‑181722 S1‑181430
    S1‑181722 Services using AI (instant translation) in real time communication Huawei Telecommunication India CR Approval Yes
Yes
agreed No   S1‑181626
7.1 FS_FRMCS2: Study on Future Railway Mobile Communication System 2 [SP-170588] S1‑181085 gap analysis for monitioring and control of critical infrastructure in 6.13 CHENGDU TD TECH LTD. CR   Yes
Yes
revised No S1‑181422  
    S1‑181422 gap analysis for monitioring and control of critical infrastructure in 6.13 CHENGDU TD TECH LTD. CR Decision Yes
Yes
agreed No   S1‑181085
    S1‑181086 gap analysis for real time data communication in 6.14 CHENGDU TD TECH LTD. CR   Yes
Yes
revised No S1‑181423  
    S1‑181423 gap analysis for real time data communication in 6.14 CHENGDU TD TECH LTD. CR - Yes
Yes
revised No S1‑181586 S1‑181086
    S1‑181586 gap analysis for real time data communication in 6.14 CHENGDU TD TECH LTD. CR - Yes
Yes
agreed No   S1‑181423
    S1‑181134 Gap analysis of chapter 12.19 Ericsson, Nokia, UIC, ETRI, Hansung University, Huawei, Kapsch Carriercom CR Agreement Yes
Yes
revised No S1‑181428  
    S1‑181428 Gap analysis of chapter 12.19 Ericsson, Nokia, UIC, ETRI, Hansung University, Huawei, Kapsch Carriercom CR Agreement Yes
Yes
agreed No   S1‑181134
    S1‑181135 Gap analysis of chapter 12.19 Ericsson, Nokia, UIC, ETRI, Hansung University, Huawei, Kapsch Carriercom CR Agreement Yes
Yes
withdrawn Yes    
    S1‑181149 chapter_6_x_Train Integrity monitoring data communication Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181577  
    S1‑181577 chapter_6_x_Train Integrity monitoring data communication Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181149
    S1‑181152 chapter_6_x_Broadcast of public emergency warning information Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181578  
    S1‑181578 chapter_6_x_Broadcast of public emergency warning information Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181152
    S1‑181154 chapter_6_x_safety critical advisory messaging Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181579  
    S1‑181579 chapter_6_x_safety critical advisory messaging Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181154
    S1‑181155 chapter_12_8_interworking GSM-R processing MLPP priorities Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181574  
    S1‑181574 chapter_12_8_interworking GSM-R processing MLPP priorities Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181155
    S1‑181156 chapter_12_10_QoS_notify changes in the perceived_ QoS level to the FRMCS User Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181575  
    S1‑181575 chapter_12_10_QoS_notify changes in the perceived_ QoS level to the FRMCS User Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No   S1‑181156
    S1‑181157 chapter_12_Bearer_Flex_considering QoS_attributes_for_bearer_service_selection Union Inter. Chemins de Fer CR Agreement Yes
Yes
agreed No    
    S1‑181158 chapter_12 correction of wrong headline in chapter 12_19 Union Inter. Chemins de Fer CR Agreement Yes
Yes
revised No S1‑181576  
    S1‑181576 chapter_12 correction of wrong headline in chapter 12_19 Union Inter. Chemins de Fer CR Agreement Yes
Yes
Visio was used for the figures.
agreed No   S1‑181158
    S1‑181245 Gap analysis of chapter 9.11 FRMCS Naming Authority ETRI, Hansung University CR   Yes
Yes
revised No S1‑181424  
    S1‑181424 Gap analysis of chapter 9.11 FRMCS Naming Authority ETRI, Hansung University CR - Yes
Yes
revised No S1‑181618 S1‑181245
    S1‑181618 Gap analysis of chapter 9.11 FRMCS Naming Authority ETRI, Hansung University CR - Yes
Yes
Change over change, Rev marks on the cover page
revised No S1‑181709 S1‑181424
    S1‑181709 Gap analysis of chapter 9.11 FRMCS Naming Authority ETRI, Hansung University CR - Yes
Yes
agreed No   S1‑181618
    S1‑181246 Gap analysis of chapter 9.12 Wayside-Centric Automatic Train Control ETRI, Hansung University CR   Yes
Yes
revised No S1‑181425  
    S1‑181425 Gap analysis of chapter 9.12 Wayside-Centric Automatic Train Control ETRI, Hansung University CR - Yes
Yes
revised No S1‑181619 S1‑181246
    S1‑181619 Gap analysis of chapter 9.12 Wayside-Centric Automatic Train Control ETRI, Hansung University CR - Yes
Yes
change marks on the cover page
revised No S1‑181710 S1‑181425
    S1‑181710 Gap analysis of chapter 9.12 Wayside-Centric Automatic Train Control ETRI, Hansung University CR - Yes
Yes
agreed No   S1‑181619
    S1‑181247 Gap analysis of chapter 9.13 Autonomous Train Control and Operation ETRI, Hansung University CR   Yes
Yes
revised No S1‑181426  
    S1‑181426 Gap analysis of chapter 9.13 Autonomous Train Control and Operation ETRI, Hansung University CR - Yes
Yes
revised No S1‑181620 S1‑181247
    S1‑181620 Gap analysis of chapter 9.13 Autonomous Train Control and Operation ETRI, Hansung University CR - Yes
Yes
Also rev marks on the cover page
revised No S1‑181711 S1‑181426
    S1‑181711 Gap analysis of chapter 9.13 Autonomous Train Control and Operation ETRI, Hansung University CR - Yes
Yes
agreed No   S1‑181620
    S1‑181248 Gap analysis of chapter 12.6 Autonomous Train Control and Operation ETRI, Hansung University CR   Yes
Yes
revised No S1‑181427  
    S1‑181427 Gap analysis of chapter 12.6 Autonomous Train Control and Operation ETRI, Hansung University CR - Yes
Yes
revised No S1‑181621 S1‑181248
    S1‑181621 Gap analysis of chapter 12.6 Autonomous Train Control and Operation ETRI, Hansung University CR - Yes
Yes
Also change marks on the cover
revised No S1‑181712 S1‑181427
    S1‑181712 Gap analysis of chapter 12.6 Autonomous Train Control and Operation ETRI, Hansung University CR - Yes
Yes
agreed No   S1‑181621
    S1‑181302 TR22.abcv0.1.0 to include agreements at this meeting Rapporteur (Qualcomm) other discussion Yes
Yes
agreed No    
    S1‑181322 Gap analysis of chapter 6.7 Pushed Real Time Video streaming Ericsson, Nokia, UIC, ETRI, Hansung University, Huawei, Kapsch Carriercom CR discussion Yes
Yes
revised No S1‑181429  
    S1‑181429 Gap analysis of chapter 6.7 Pushed Real Time Video streaming Ericsson, Nokia, UIC, ETRI, Hansung University, Huawei, Kapsch Carriercom CR discussion Yes
Yes
agreed No   S1‑181322
    S1‑181323 Data communication to exchange key information for train safety application use case UIC CR Decision Yes
Yes
This adds a part that was missing of a previously agreed CR.
agreed No    
7.2 FS_MARCOM: Study on Maritime Communication Services over 3GPP system [SP-170453] S1‑181031 Network reselection in case of the transition from IOPS mode to on-network mode SyncTechno Inc. pCR   Yes
Yes
revised No S1‑181501  
    S1‑181501 Network reselection in case of the transition from IOPS mode to on-network mode SyncTechno Inc. pCR - Yes
Yes
agreed No   S1‑181031
    S1‑181032 Next positioning technologies SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181593  
    S1‑181593 Next positioning technologies SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181032
    S1‑181033 Satellite access SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181595  
    S1‑181595 Satellite access SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181033
    S1‑181034 5G LAN-type services over 5G system in a vessel SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181594  
    S1‑181594 5G LAN-type services over 5G system in a vessel SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181034
    S1‑181035 Introduction and Overview SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181489  
    S1‑181489 Introduction and Overview SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181035
    S1‑181036 Update of requirements in the clause 7.6(related to ePWS) SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181500  
    S1‑181500 Update of requirements in the clause 7.6(related to ePWS) SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181036
    S1‑181037 Editor's NOTE in the clause 5.1 SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181490  
    S1‑181490 Editor's NOTE in the clause 5.1 SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181037
    S1‑181038 Editor's NOTE in the clause 6.2 SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181491  
    S1‑181491 Editor's NOTE in the clause 6.2 SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181038
    S1‑181039 Editor's NOTE in the clause 6.3 SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181492  
    S1‑181492 Editor's NOTE in the clause 6.3 SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181039
    S1‑181040 Editor's NOTE in the clause 7.2 SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181498  
    S1‑181498 Editor's NOTE in the clause 7.2 SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181040
    S1‑181041 Editor's NOTE in the clause 7.5 SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181499  
    S1‑181499 Editor's NOTE in the clause 7.5 SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181689 S1‑181041
    S1‑181689 Editor's NOTE in the clause 7.5 SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181499
    S1‑181042 Consolidated potential requirements SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181596  
    S1‑181596 Consolidated potential requirements SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181690 S1‑181042
    S1‑181690 Consolidated potential requirements SyncTechno Inc., Korean Register of shipping pCR Approval Yes
Yes
agreed No   S1‑181596
    S1‑181043 Conclusion and Recommendations SyncTechno Inc. pCR Approval Yes
Yes
revised No S1‑181597  
    S1‑181597 Conclusion and Recommendations SyncTechno Inc. pCR Approval Yes
Yes
agreed No   S1‑181043
    S1‑181045 FS_MARCOM cover page for approval to SA SyncTechno Inc. TS or TR cover Approval Yes
Yes
For presentation of the TR in S1-181281 for information to SA.
agreed No    
    S1‑181115 Interworking with VHF Data Exchange System SyncTechno Inc. pCR Approval Yes
Yes
agreed No    
    S1‑181281 TR22.819v0.6.0 to include agreements at this meeting Rapporteur (SyncTechno) draft TR discussion Yes
Yes
agreed No    
    S1‑181282 MARCOM+HYPOS+5GSAT drafting agenda Rapporteur / Session Chair agenda discussion Yes
Yes
agreed No    
    S1‑181283 MARCOM+HYPOS+5GSAT drafting report Rapporteur / Session Chair report discussion Yes
Yes
agreed No    
    S1‑181608 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181609 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181610 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181611 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181612 Not used Not used other discussion No
No
withdrawn Yes    
7.3 FS_CAV: Study on Communication for Automation in Vertical Domains [SP-170169] S1‑181010 Aligning network terminology Siemens AG, Nokia, Qualcomm, Deutsche Telekom, Sennheiser, Robert Bosch GmbH discussion Decision Yes
Yes
The following definitions are proposed:
exclusive network: a 3GPP network that is not for public use and may interact with a PLMN.
private network: an isolated network that does not interact with a PLMN.
 
The debate went onto the word "interact" and what is meant by it. Qualcomm wondered if e.g. tunnelling is a case of "interaction".
 
The conclusions are superseded by 1342, which propose the opposite definitions, where an "exclusive network" have no interaction with the PLMN.
noted No    
    S1‑181046 FS_CAV section 8 potential Energy Consideration requirements Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
agreed No    
    S1‑181047 FS_CAV section 8.2.2.5 potential legacy and backward compatibility Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181447  
    S1‑181447 FS_CAV section 8.2.2.5 potential legacy and backward compatibility Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181682 S1‑181047
    S1‑181682 FS_CAV section 8.2.2.5 potential legacy and backward compatibility Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
agreed No   S1‑181447
    S1‑181048 FS_CAV section 8 potential Clock synchronization requirements Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181448  
    S1‑181448 FS_CAV section 8 potential Clock synchronization requirements Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval No
Yes
Merged into S1-181443
merged No   S1‑181048
    S1‑181049 FS_CAV section 8.2.7 potential other general requirements Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181453  
    S1‑181453 FS_CAV section 8.2.7 potential other general requirements Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
agreed No   S1‑181049
    S1‑181050 FS_CAV section 8 skeleton and annex for mapping table Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181440  
    S1‑181440 FS_CAV section 8 skeleton and annex for mapping table Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
agreed No   S1‑181050
    S1‑181051 CAV – potential communication service performance requirements on clock synchronization Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181343  
    S1‑181343 CAV – potential communication service performance requirements on clock synchronization Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
revised No S1‑181443 S1‑181051
    S1‑181443 CAV – potential communication service performance requirements on clock synchronization Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
agreed No   S1‑181343
    S1‑181056 Discussion Paper on Definition for Public/Private/Exclusive Networks KPN discussion Discussion Yes
Yes
So, with these definitions, an "exclusive network" is a specific type of "private network".
 
A set of CRs is proposed to introduce/modify these definitions in1057, 1058 and 1059.
 
For T-Mobile and Ericsson, it is dangerous to completely change the Rel-15 definition of "private network".
 
About the proposed change in the definition of PLMN:
- With the new addition to the definion of PLMN, it was wondered if a machine is part of the public.
- T-Mobile's opinion is that the proposed addition doesn't help much and should not be introduced
- Nokia clarified that the definition of PLMN was introduced by the time networks where operated by government-like companies, and this is what was meant by "public". So the definition has to be indeed revisited.
 
KPN clarified that "public networks" are networks open to the public, and by thus have to comply to certain government requirement, like legal interception, emergency calls, etc. These requirements do not necessarily apply to private network (or to networks type a and b, according to 1342).
 
Telecom Italia support KPN's proposal, emphasizing the fact that the previous Rel-15 definition of "private network" can still be deleted since it has not much been used so far in other groups.
noted No    
    S1‑181057 [DRAFT] Update of the definition of Public Land Mobile Network KPN draftCR Endorsement Yes
Yes
No support.
withdrawn Yes    
    S1‑181058 Removal of private network and related requirements in Release 15 KPN CR Agreement Yes
Yes
It was acknowledge that "private network" has already been used in other groups, as stated e.g. by Ericsson.
Now the problem was to check is "private network" was used for type a or type b network, i.e. With or without interaction with the PLMN.
Qualcomm clarified that SA3 has been using "private network" as type b network.
SA2 has been using "private network" too.
For Telecom Italia, SA2 is waiting for SA1's decision and SA3 is using it in a generic way.
 
KPN acknowledge that, with the previous definition of "private network" already in the specs (mentioning that "private network" do not interact with PLMN), it is not feasible to swap the terms as per their proposal in 1342 and 1056. So they wonder if other terminology would do.
 
"Exclusive network" has not been used yet in other groups.
withdrawn Yes    
    S1‑181059 New definitions for Private Network and Exclusive Network KPN CR Agreement Yes
Yes
withdrawn Yes    
    S1‑181062 Positioning Requirements for Use Cases under Factories of the Future Sony Europe Limited pCR Agreement Yes
Yes
revised No S1‑181344  
    S1‑181344 Positioning Requirements for Use Cases under Factories of the Future Sony Europe Limited pCR Agreement Yes
Yes
revised No S1‑181459 S1‑181062
    S1‑181459 Positioning Requirements for Use Cases under Factories of the Future Fraunhofer IIS, Sony, Siemens AG, Deutsche Telekom AG pCR Agreement Yes
Yes
agreed No   S1‑181344
    S1‑181088 Smart Grid : Millisecond-Level Precise Load Control China Telecomunication Corp. pCR   Yes
Yes
revised No S1‑181442  
    S1‑181442 Smart Grid : Millisecond-Level Precise Load Control China Telecomunication Corp. pCR - Yes
Yes
One typo to be corrected
revised No S1‑181539 S1‑181088
    S1‑181539 Smart Grid : Millisecond-Level Precise Load Control China Telecomunication Corp. pCR - Yes
Yes
agreed No   S1‑181442
    S1‑181098 FS_CAV Service QoS monitoring and reporting requirements consolidation Huawei Telecommunication India pCR Approval Yes
Yes
revised No S1‑181450  
    S1‑181450 FS_CAV Service QoS monitoring and reporting requirements consolidation Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
Further edited while projecting
revised No S1‑181537 S1‑181098
    S1‑181537 FS_CAV Service QoS monitoring and reporting requirements consolidation Siemens, Huawei, Nokia, Qualcomm, Ericsson pCR Approval Yes
Yes
agreed No   S1‑181450
    S1‑181109 CAV – update of definitions subclause Sennheiser Electronic GmbH pCR Decision Yes
Yes
See supporting slides in S1-181368
revised No S1‑181463  
    S1‑181368 CAV – support slides for the update of definitions subclause Sennheiser Electronic GmbH discussion Decision Yes
Yes
Supporting slides for S1-181109
noted No    
    S1‑181463 CAV – update of definitions subclause Sennheiser Electronic GmbH pCR Decision Yes
Yes
agreed No   S1‑181109
    S1‑181144 CAV - editorial cleanup to clause 1 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
revised No S1‑181337  
    S1‑181337 CAV - editorial cleanup to clause 1 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
agreed No   S1‑181144
    S1‑181145 CAV - cleanup of clause 2 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
revised No S1‑181336  
    S1‑181336 CAV - cleanup of clause 2 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
revised No S1‑181465 S1‑181145
    S1‑181465 CAV - cleanup of clause 2 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
agreed No   S1‑181336
    S1‑181146 Editorial cleanup to clause 3.3 in TR 22.804 Siemens, Nokia, Huawei pCR   Yes
Yes
revised No S1‑181470  
    S1‑181470 Editorial cleanup to clause 3.3 in TR 22.804 Siemens, Nokia, Huawei pCR - Yes
Yes
agreed No   S1‑181146
    S1‑181147 Editorial cleanup to clause 7 in TR 22.804 Siemens, Nokia, Huawei pCR   Yes
Yes
agreed No    
    S1‑181148 Editorial cleanup to Annexes E in TR 22.804 Siemens, Nokia, Huawei pCR   Yes
Yes
agreed No    
    S1‑181150 Editorial cleanup to apply exclusive network Nokia UK pCR   Yes
Yes
revised No S1‑181466  
    S1‑181466 Editorial cleanup to apply exclusive network Nokia UK pCR - Yes
Yes
revised No S1‑181698 S1‑181150
    S1‑181698 Editorial cleanup to apply exclusive network Nokia UK pCR - Yes
Yes
agreed No   S1‑181466
    S1‑181151 CAV – update of definitions subclause Siemens AG pCR Agreement Yes
Yes
revised No S1‑181462  
    S1‑181462 CAV – update of definitions subclause Siemens AG pCR Agreement Yes
Yes
agreed No   S1‑181151
    S1‑181153 CAV – update of network definition Siemens AG pCR Agreement Yes
Yes
revised No S1‑181464  
    S1‑181464 CAV – update of network definition Siemens AG pCR Agreement No
Yes
Withdrawn by the author
withdrawn Yes   S1‑181153
    S1‑181159 CAV – update of subclause 4.3.4.4 Siemens AG pCR Agreement Yes
Yes
revised No S1‑181461  
    S1‑181461 CAV – update of subclause 4.3.4.4 Siemens AG pCR Agreement Yes
Yes
typo on "quantitities"
revised No S1‑181549 S1‑181159
    S1‑181549 CAV – update of subclause 4.3.4.4 Siemens AG pCR Agreement Yes
Yes
agreed No   S1‑181461
    S1‑181160 Discussion on the remaining issues in CAV study Vodafone Group Plc pCR Decision Yes
Yes
Merged into S1-181466
merged No    
    S1‑181162 CAV – editorial cleanup of clause 4 Siemens AG, Nokia pCR Agreement Yes
Yes
agreed No    
    S1‑181165 CAV – update of subclause 4.1 and 4.2 Siemens AG pCR Agreement Yes
Yes
revised No S1‑181460  
    S1‑181460 CAV – update of subclause 4.1 and 4.2 Siemens AG pCR Agreement Yes
Yes
agreed No   S1‑181165
    S1‑181173 Editorial cleanup to clause 5 in TR 22.804 Siemens AG, Nokia, Huawei, ETRI pCR Agreement Yes
Yes
revised No S1‑181469  
    S1‑181469 Editorial cleanup to clause 5 in TR 22.804 Siemens AG, Nokia, Huawei, ETRI pCR Agreement Yes
Yes
revised No S1‑181471 S1‑181173
    S1‑181471 Editorial cleanup to clause 5 in TR 22.804 Siemens AG, Nokia, Huawei, ETRI pCR Agreement Yes
Yes
revised No S1‑181474 S1‑181469
    S1‑181474 Editorial cleanup to clause 5 in TR 22.804 Siemens AG, Nokia, Huawei, ETRI pCR Agreement Yes
Yes
agreed No   S1‑181471
    S1‑181175 Cleanup to clause 6 in TR 22.804 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
revised No S1‑181456  
    S1‑181456 Cleanup to clause 6 in TR 22.804 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
Further edited while projecting
revised No S1‑181546 S1‑181175
    S1‑181546 Cleanup to clause 6 in TR 22.804 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
agreed No   S1‑181456
    S1‑181184 CAV – 8.1 – merged potential communication service performance re-quirements Siemens AG, Huawei, Nokia, Qualcomm, Ericsson pCR Agreement Yes
Yes
revised No S1‑181441  
    S1‑181441 CAV – 8.1 – merged potential communication service performance re-quirements Siemens AG, Huawei, Nokia, Qualcomm, Ericsson pCR Agreement Yes
Yes
agreed No   S1‑181184
    S1‑181186 CAV – conclusions Siemens AG pCR Agreement Yes
Yes
revised No S1‑181454  
    S1‑181454 CAV – conclusions Siemens AG pCR Agreement Yes
Yes
agreed No   S1‑181186
    S1‑181187 CAV -cleanup of annexes A to C Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
revised No S1‑181455  
    S1‑181455 CAV -cleanup of annexes A to C Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
Agreed except for "Annexe", to be written as "annex"
agreed No   S1‑181187
    S1‑181188 CAV - cleanup of Annexe D, TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
agreed No    
    S1‑181206 FS_CAV Ethernet support deployment requirements Qualcomm Incorporated, Huawei, Siemens, Nokia discussion Agreement Yes
Yes
agreed No    
    S1‑181207 FS_5GLAN: Proposed terminology changes for 5GLAN TR22.821 Qualcomm Incorporated CR Agreement Yes
Yes
revised No S1‑181467  
    S1‑181467 FS_5GLAN: Proposed terminology changes for 5GLAN TR22.821 Qualcomm Incorporated CR Agreement No
Yes
To be considered at a later stage.
withdrawn Yes   S1‑181207
    S1‑181209 Section 4.1 of 5GLAN TR22.821 Qualcomm Incorporated CR Agreement Yes
Yes
The proposed added text should be shown with revision marks.
It should be category F.
"4.1(new)" to be changed in "4.1" on the cover page.
Other corrections needed on the cover page.
revised No S1‑181567  
    S1‑181567 Section 4.1 of 5GLAN TR22.821 Qualcomm Incorporated CR Agreement Yes
Yes
agreed No   S1‑181209
    S1‑181215 Editorial correction on Smart Farming Use case Fujitsu Limited pCR   Yes
Yes
revised No S1‑181321  
    S1‑181321 Editorial correction on Smart Farming Use case Fujitsu Limited pCR - Yes
Yes
revised No S1‑181378 S1‑181215
    S1‑181378 Editorial correction on Smart Farming Use case Fujitsu Limited pCR - Yes
Yes
revised No S1‑181457 S1‑181321
    S1‑181457 Editorial correction on Smart Farming Use case Fujitsu Limited pCR - Yes
Yes
Typo to be corrected ("stem")
revised No S1‑181548 S1‑181378
    S1‑181548 Editorial correction on Smart Farming Use case Fujitsu Limited pCR - No
Yes
agreed No   S1‑181457
    S1‑181638 cyberCAV TS Inclusion of Ethernet requirements Qualcomm Incorporated, Siemens discussion Agreement Yes
Yes
Relates to S1-181374, for the new TS for cyberCAV.
2 requirements to be moved to 22.261.
revised No S1‑181664  
    S1‑181664 cyberCAV TS Inclusion of Ethernet requirements Qualcomm Incorporated, Siemens discussion Agreement Yes
Yes
agreed No   S1‑181638
    S1‑181227 Cleanup of subclause 5.6.1 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
revised No S1‑181458  
    S1‑181458 Cleanup of subclause 5.6.1 in TR 22.804, V1.1.0 Siemens AG, Nokia, Huawei pCR Agreement Yes
Yes
agreed No   S1‑181227
    S1‑181228 FS_CAV exclusive/private network deployment requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR   Yes
Yes
revised No S1‑181445  
    S1‑181445 FS_CAV exclusive/private network deployment requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
revised No S1‑181680 S1‑181228
    S1‑181680 FS_CAV exclusive/private network deployment requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
revised No S1‑181743 S1‑181445
    S1‑181743 FS_CAV exclusive/private network deployment requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
agreed No   S1‑181680
    S1‑181229 FS_CAV Network service differentiation and isolation requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR   Yes
Yes
revised No S1‑181446  
    S1‑181446 FS_CAV Network service differentiation and isolation requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
Typo to be corrected
revised No S1‑181681 S1‑181229
    S1‑181681 FS_CAV Network service differentiation and isolation requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
agreed No   S1‑181446
    S1‑181230 FS_CAV network interaction potential requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR   Yes
Yes
revised No S1‑181449  
    S1‑181449 FS_CAV network interaction potential requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
revised No S1‑181475 S1‑181230
    S1‑181231 FS_CAV Network service exposure requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR   Yes
Yes
revised No S1‑181451  
    S1‑181451 FS_CAV Network service exposure requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
revised No S1‑181476 S1‑181231
    S1‑181476 FS_CAV Network service exposure requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
revised No S1‑181536 S1‑181451
    S1‑181536 FS_CAV Network service exposure requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
agreed No   S1‑181476
    S1‑181232 FS_CAV section 8.2.6 security and privacy potential requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR   Yes
Yes
revised No S1‑181452  
    S1‑181452 FS_CAV section 8.2.6 security and privacy potential requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
revised No S1‑181478 S1‑181232
    S1‑181478 FS_CAV section 8.2.6 security and privacy potential requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR - Yes
Yes
The statement "The 5G system shall allow over-the-top end-to-end security protocols in addition to 3GPP access security.(note 1)" is not really a requirement, it can be added as a note.
Other corrections made while projecting.
To be merged with 1444 in 1679.
merged No   S1‑181452
    S1‑181233 FS_CAV - section 8.2.1 - network service access requirements Siemens AG pCR Agreement Yes
Yes
revised No S1‑181444  
    S1‑181444 FS_CAV - section 8.2.1 - network service access requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR Agreement Yes
Yes
revised No S1‑181679 S1‑181233
    S1‑181679 FS_CAV - section 8.2.1 - network service access requirements Siemens, Nokia, Huawei, Qualcomm, Ericsson pCR Agreement Yes
Yes
Merge of 1444 and 1478
agreed No   S1‑181444
    S1‑181234 Presentation of Report to TSG SA#80: TR22.804, Version 2.0.0 Siemens AG TS or TR cover Approval Yes
Yes
revised No S1‑181702  
    S1‑181702 Presentation of Report to TSG SA#80: TR22.804, Version 2.0.0 Siemens AG TS or TR cover Approval Yes
Yes
Cover page for the TR in 1284.
"acceptance" to be changed in "approval".
Wrong template.
"network type-a / type-b" not mentioned, but this is fine since it is not contentious anymore. It can be mentioned in the changes.
revised No S1‑181746 S1‑181234
    S1‑181746 Presentation of Report to TSG SA#80: TR22.804, Version 2.0.0 Siemens AG TS or TR cover Approval Yes
Yes
agreed No   S1‑181702
    S1‑181552 cyberCAV TS Rapporteur (Siemens) draft TS Agreement Yes
Yes
To include material agreed at this meeting.
Only one pCR agreed at this meeting.
agreed No    
    S1‑181284 TR22.804v1.2.0 to include agreements at this meeting Rapporteur (Siemens) draft TR discussion No
Yes
To be submitted by May 15th, final version by Friday
agreed No    
    S1‑181285 CAV drafting agenda Rapporteur / Session Chair agenda discussion Yes
Yes
agreed No    
    S1‑181286 CAV drafting report Rapporteur / Session Chair report discussion Yes
Yes
agreed No    
    S1‑181479 Not used Not used other discussion No
No
withdrawn Yes    
    S1‑181525 Not used Not used other discussion No
No
withdrawn Yes    
7.4 FS_5G_HYPOS: Study on positioning use cases [SP-170589] S1‑181011 Container size in factories use case (FS_5G_HYPOS) Orange other   Yes
Yes
revised No S1‑181390  
    S1‑181390 Container size in factories use case (FS_5G_HYPOS) Orange other - Yes
Yes
revised No S1‑181484 S1‑181011
    S1‑181484 Container size in factories use case (FS_5G_HYPOS) Orange other - Yes
Yes
revised No S1‑181695 S1‑181390
    S1‑181695 Container size in factories use case (FS_5G_HYPOS) Orange other - No
Yes
withdrawn Yes   S1‑181484
    S1‑181021 First Responder location use case FirstNet, NextNav and BMWi pCR Approval Yes
Yes
revised No S1‑181497  
    S1‑181497 First Responder location use case FirstNet, NextNav, BMWi, KRRI, The Police of the Netherlands pCR Approval Yes
Yes
agreed No   S1‑181021
    S1‑181066 Supplement vertical positioning requirements ZTE Wistron Telecom AB pCR   Yes
Yes
revised No S1‑181480  
    S1‑181480 Supplement vertical positioning requirements ZTE Wistron Telecom AB pCR - Yes
Yes
agreed No   S1‑181066
    S1‑181067 Support of 3rd party to trigger location method negotiation ZTE Wistron Telecom AB pCR   Yes
Yes
revised No S1‑181482  
    S1‑181482 Support of 3rd party to trigger location method negotiation ZTE Wistron Telecom AB pCR - Yes
Yes
agreed No   S1‑181067
    S1‑181104 5G_HYPOS - TR 22.872 Clause 5 - Multiple editors notes ESA pCR Approval Yes
Yes
revised No S1‑181483  
    S1‑181483 5G_HYPOS - TR 22.872 Clause 5 - Multiple editors notes ESA pCR Approval Yes
Yes
agreed No   S1‑181104
    S1‑181105 5G_HYPOS - TR 22.872 Clause 6 - Considerations on privacy and adaptability ESA pCR Approval Yes
Yes
revised No S1‑181386  
    S1‑181386 5G_HYPOS - TR 22.872 Clause 6 - Considerations on privacy and adaptability ESA pCR Approval Yes
Yes
revised No S1‑181602 S1‑181105
    S1‑181602 5G_HYPOS - TR 22.872 Clause 6 - Considerations on privacy and adaptability ESA pCR Approval Yes
Yes
agreed No   S1‑181386
    S1‑181106 5G_HYPOS - TR 22.872 Clause 8 - Potential consolidated requirements ESA pCR Approval Yes
Yes
revised No S1‑181494  
    S1‑181494 5G_HYPOS - TR 22.872 Clause 8 - Potential consolidated requirements ESA pCR Approval Yes
Yes
revised No S1‑181604 S1‑181106
    S1‑181604 5G_HYPOS - TR 22.872 Clause 8 - Potential consolidated requirements ESA pCR Approval Yes
Yes
"Potential consolidated positioning requirements" to be changed into "Consolidated potential positioning requirements"
revised No S1‑181696 S1‑181494
    S1‑181696 5G_HYPOS - TR 22.872 Clause 8 - Potential consolidated requirements ESA pCR Approval Yes
Yes
The Horizontal Accuracy for wide area of 50 m is seen too wide, and several companies think that 10 m would be more reasonable.
For Qualcomm, it is not reasonable to change a value last minute without appropriate studies.
10 m is seen challenging for indoor, but this would be their challenge.
It is changed to 10m.
revised No S1‑181747 S1‑181604
    S1‑181747 5G_HYPOS - TR 22.872 Clause 8 - Potential consolidated requirements ESA pCR Approval No
Yes
agreed No   S1‑181696
    S1‑181107 5G_HYPOS - TR 22.872 Clause 9 - Conclusions and recommendations ESA pCR Approval Yes
Yes
revised No S1‑181387  
    S1‑181387 5G_HYPOS - TR 22.872 Clause 9 - Conclusions and recommendations ESA pCR Approval Yes
Yes
agreed No   S1‑181107
    S1‑181108 5G_HYPOS - TR 22.872 Annex A - Mapping matrices for potential consolidated requirements ESA pCR Approval Yes
Yes
revised No S1‑181605  
    S1‑181605 5G_HYPOS - TR 22.872 Annex A - Mapping matrices for potential consolidated requirements ESA pCR Approval Yes
Yes
agreed No   S1‑181108
    S1‑181132 TR 22.872 use case clarifications Philips International B.V. pCR Agreement Yes
Yes
revised No S1‑181481  
    S1‑181481 TR 22.872 use case clarifications Philips International B.V. pCR Agreement Yes
Yes
The Police of the Netherlands ask "drugs transport to be replaced by "Medecine transport" to avoid any confusion.
revised No S1‑181693 S1‑181132
    S1‑181693 TR 22.872 use case clarifications Philips International B.V. pCR Agreement Yes
Yes
agreed No   S1‑181481
    S1‑181133 TR 22.872 additional use cases Philips International B.V. pCR Agreement Yes
Yes
revised No S1‑181601  
    S1‑181601 TR 22.872 additional use cases Philips International B.V. pCR Agreement Yes
Yes
agreed No   S1‑181133
    S1‑181224 5G_HYPOS – TR 22.872 Clause 7 - Considerations on the suitability of positioning technologies for use cases ESA pCR Approval Yes
Yes
revised No S1‑181496  
    S1‑181496 5G_HYPOS – TR 22.872 Clause 7 - Considerations on the suitability of positioning technologies for use cases ESA pCR Approval Yes
Yes
revised No S1‑181603 S1‑181224
    S1‑181603 5G_HYPOS – TR 22.872 Clause 7 - Considerations on the suitability of positioning technologies for use cases ESA pCR Approval Yes
Yes
revised No S1‑181735 S1‑181496
    S1‑181735 5G_HYPOS – TR 22.872 Clause 7 - Considerations on the suitability of positioning technologies for use cases ESA pCR Approval Yes
Yes
agreed No   S1‑181603
    S1‑181225 5G_HYPOS - TR 22.872 Clause 5.5.1 – Editor’s note ESA pCR Approval Yes
Yes
agreed No    
    S1‑181235 5G_HYPOS - TR22.872 - Editorial cleanup and references ESA pCR Approval Yes
Yes
revised No S1‑181606  
    S1‑181606 5G_HYPOS - TR22.872 - Editorial cleanup and references ESA pCR Approval Yes
Yes
This is a pCR covering the entire TR, including the cover page.
One reference to be added.
revised No S1‑181697 S1‑181235
    S1‑181697 5G_HYPOS - TR22.872 - Editorial cleanup and references ESA pCR Approval Yes
Yes
Next version in 1287
agreed No   S1‑181606
    S1‑181287 TR22.872v1.1.0 to include agreements at this meeting Rapporteur (ESA) draft TR discussion No
Yes
To be sent by Tuesday May 15th, comments by Thursday, final version by Friday.
agreed No    
    S1‑181288 Cover page for presentation of TR22.872v1.1.0 Rapporteur (ESA) TS or TR cover discussion Yes
Yes
It is still not clear whether this is for information or approval. T should have been for information already last time.
It is preferred to have it for approval.
revised No S1‑181754  
    S1‑181754 Cover page for presentation of TR22.872v1.1.0 Rapporteur (ESA) TS or TR cover discussion No
Yes
Agreed to send it for approval.
agreed No   S1‑181288
    S1‑181342 Way Forward on terminology nnKPN, Vodafone, Nokia, Siemens other discussion Yes
Yes
See other documents that relate to the same topic.
noted No    
    S1‑181570 Way Forward on terminology nnKPN, Vodafone, Nokia, Siemens other discussion Yes
Yes
Word document, same topic as the presentation in S1-181342, but conclusions will be different since there was no agreement on 1342.
revised No S1‑181468  
    S1‑181468 Way Forward on terminology Siemens, Qualcomm other discussion Yes
Yes
"private" versus "exclusive" networks are now replaced by "Type-a" versus "Type-b" networks as follows:
type-a network: a 3GPP network that is not for public use and for which service continuity and roaming with a PLMN is possible.
type-b network: an isolated 3GPP network that does not interact with a PLMN.
 
Several steps are proposed on how to introduce these clarifications.
 
This late clarification has significant consequences. A new document (or a revised version of this document) will be provided to clarify by using editor's notes where further clarifications are needed in the SA1 documents, in particular in CAV but also 5GLAN.
 
Some further clarifications will be proposed off-line.
revised No S1‑181650 S1‑181570
    S1‑181650 Way Forward on terminology Siemens, Qualcomm, Vodafone other discussion Yes
Yes
The rapporteur is requested to add the editor's notes also to the newly agreed pCRs.
A clean-up of the entire TR 22.804 has to done by the rapporteur, changing "exclusive" and "private" into respectively "type a" and "type b" networks.
agreed No   S1‑181468
7.5 FS_5GSAT: Study on using Satellite Access in 5G [SP-170788] S1‑181013 FS_5GSAT- TR 22.822 - Section 2 – References - Clean up THALES pCR Agreement Yes
Yes
agreed No    
    S1‑181015 FS_5GSAT- TR 22.822 - Section 3.2 – Abbreviations THALES pCR Agreement Yes
Yes
agreed No    
    S1‑181016 FS_5GSAT- TR 22.822 - Section 7 – Considerations THALES pCR Agreement Yes
Yes
revised No S1‑181487  
    S1‑181487 FS_5GSAT- TR 22.822 - Section 7 – Considerations THALES pCR Agreement Yes
Yes
agreed No   S1‑181016
    S1‑181017 FS_5GSAT- TR 22.822 - Section 8 – Potential Requirements THALES pCR Agreement Yes
Yes
revised No S1‑181488  
    S1‑181488 FS_5GSAT- TR 22.822 - Section 8 – Potential Requirements THALES pCR Agreement Yes
Yes
revised No S1‑181616 S1‑181017
    S1‑181616 FS_5GSAT- TR 22.822 - Section 8 – Potential Requirements THALES pCR Agreement Yes
Yes
revised No S1‑181538 S1‑181488
    S1‑181538 FS_5GSAT- TR 22.822 - Section 8 – Potential Requirements THALES pCR Agreement Yes
Yes
agreed No   S1‑181616
    S1‑181018 FS_5GSAT- TR 22.822 - Section 9 – Conclusion and Recommendations THALES pCR Agreement Yes
Yes
revised No