Tdoc List
2017-06-07 20:01
| Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Opening of the meeting | |||||||||||
| 2 | Reminders for usage of IT resources, IPR declaration and antitrust compliance | |||||||||||
| 3 | Approval of the agenda | RP‑170856 | Agenda for RAN #76 held in West Palm Beach, USA, 05.06.-08.06.2017 | RAN chairman (Nokia) | agenda | Approval | Yes |
YesRAN chairman: There are some items for early consideration in the meeting and we will jump to them on Monday for a first pass:
- AI 9: NR standardization: RP-17 1172, RP-171249
- AI 9.2.1: low latency RP-170897, RP-171250
- AI 9.2.1: NR UE category RP-170 901, RP-170993, RP-171174
- AI 9.2.1: termination points RP-170968, RP-171216
- AI 9.2.1: separation CP/UP RP-171215
- AI 10.1.2: UL data compression RP-171108, RP-171387, RP-171184
- AI 10.11.13: Rel-15 NB_IOT/eMTC RP-171188, RP-171045, RP-171184
- AI 10.11.13.2: accelerating NB-IOT in 2017 RP-171005, RP-171006
| revised | No | RP‑171314 | |
| RP‑171314 | Revised agenda for RAN #76 held in West Palm Beach, USA, 05.06.-08.06.2017 | RAN chairman (Nokia) | agenda | Approval | Yes |
YesTelecom Italia: offline session on Tue morning on ITU-R IMT-2020 suggested
RAN chairman: 8:00-9:00 IMT-2020 offline session, rapporteur: Telecom Italia
Deutsche Telekom: would like to avoid parallel sessions
RAN chairman: updated time plans will be made available so that everyone is available of offline sessions, no parallel sessions to the main session will happen
SA chairman: joint session on Wed 18:00 - 19:00 in RAN room planned
RAN chairman: on Wed in the lunch break, the IETF chair will give a presentation in the RAN room
| approved | No | RP‑170856 | |||
| 4 | Approval of the meeting report of TSG-RAN #75 | RP‑170857 | Draft report of RAN #75 held in Dubrovnik, Croatia, 05.03.-08.03.2017 | ETSI MCC | report | Approval | Yes |
Yes
| revised | No | RP‑171409 | |
| RP‑171409 | Report of RAN #75 held in Dubrovnik, Croatia, 05.03.-08.03.2017 | ETSI MCC | report | Approval | No |
Yes
| approved | No | RP‑170857 | |||
| 5 | RAN WG reports | |||||||||||
| 5.1 | TSG RAN WG1 | RP‑170858 | Status Report RAN WG1 | RAN1 chairman (NTT DOCOMO) | report | Yes |
YesTelecom Italia:single UL support in RAN1 was supposed to be discussed in the connection with RAN1 report, any news?
RAN1 chairman: will discuss with RAN4 chair and delegates this week
Nokia: will have a Tdoc related to slide 25 in RP-171433 that we can discuss on Tue; we need a solution that works not just in RAN1 specs so we need to consult other WGs
Qualcomm: it was not intended that this works with all implementations, no band combinations were identified
Huawei: worried that we repeat here RAN1 discussions, RAN1 decision was made, RAN should not overtake the RAN1 decision
Nokia: RAN1 decision has significant impact on other WGs so they need to look at this as well
MCC: TR 38.900 will not be withdrawn
no further CRs to TR 38.900 are expected
| noted | No | |||
| RP‑170859 | List of CRs from RAN WG1 | ETSI MCC | discussion | Information | Yes |
Yes
| noted | No | ||||
| RP‑171433 | NR supporting 1Tx UE in LTE-NR UL Dual Connectivity | Nokia | discussion | discussion | Yes |
YesProposal 1: Down-scope the number of NSA architecture options and especially reconsider the architecture option 3A due to its limitation to support 1Tx UEs in LTE-NR UL DC.
Proposal 2: RAN#76 should decide if 1Tx UEs are only supported for certain problematic band combination or it is generic UE capability
Panasonic: is would be useful to collect RAN1/RAN2 feedback, no need to decide anything here; also dynamic switching could be possible
Nokia: 1Tx UE is considered in RAN1 and asking other WGs, static/semi-statis/dynamic is not yet decided, we want to avoid that decision is taken in one WG with big impacts on other WGs;
Panasonic: was not a problem in the past, one WG takes an assumption and asks for feedback from others to see whether assumption can remain;
Qualcomm: yes, it has an impact on architecture but no impact ...
LG: removal SCG bearers was not agreed in RAN2
Ericsson: we should not mix this paper with the bearer discussion; if there are intermodulation problems then we need to address this in this release and not 3 releases later;
Apple: we talk about "no simultaneous UL at a time" and not about "1Tx"; option 3A and this solution has nothing to do with each other; there was a good Samsung contribution explaining things in the last RAN4 meeting R4-17....
Sprint: not ready for down-scoping
NTT DOCOMO: agrees that we should not mix this paper with architecture discussions
Vodafone: mapping things to the same carrier does not necessarily impacts RAN2;
RAN chair: proposal 1 seems not agreeable; proposal 2: RAN2 and RAN4 will have to analyze this until Sep.17 and we cannot do this on the fly
Nokia: we should then task the WGs to analyze the impacts of the RAN1 decision on their work
RAN chair: is this acceptable?
Qualcomm: whether we task the WGs or not they need to analyze this but we could maybe decide about proposal 2
Intel: UE capability discussion can happen in RAN4; we do not need to send an LS now, can still do this later
RAN chair: there was no intention to send an LS but we can task the WGs
ZTE: it is clear that the RAN1 decision can impact on RAN2
Nokia: reminds that we need to have specs ready in Dec.
RAN chair: so the assumption is that RAN1/RAN2/RAN4 look into this problem until Sep.17
| noted | No | ||||
| 5.2 | TSG RAN WG2 | RP‑170860 | Status Report RAN WG2 | RAN2 chairman (Intel) | report | Yes |
YesNo time to add new LTE SI/WIs
LTE and UMTS Rel-14 ASN.1 reviewed and ready to be frozen from RAN2 point of view
RAN2 NR ad hocs for Jan and July 2018
| noted | No | |||
| RP‑170861 | List of CRs from RAN WG2 | ETSI MCC | discussion | Information | Yes |
Yes
| revised | No | RP‑171406 | |||
| RP‑171406 | List of CRs from RAN WG2 | ETSI MCC | discussion | Information | Yes |
Yes
| noted | No | RP‑170861 | |||
| 5.3 | TSG RAN WG3 | RP‑170862 | Status Report RAN WG3 | RAN3 chairman (Huawei) | report | Yes |
YesNew RAN3 Leaders elected:
Gino Masini (Ericsson) was elected as RAN3 chairman
Sasha Sirotkin (Intel) was elected as RAN3 vice-chairman
Rel-14 ASN.1 is ready for freezing from RAN3 point of view
Samsung: slide 11: prioritization will be discussed later, unclear what Dec.17 means here
RAN3 chair (Huawei): we did not reach consensus so far on Mon of RAN #76
Samsung: NSA option 3 should be completed by Dec.17
CMCC: no TU left in RAN3 so no new SIs/WIs?
RAN3 chair (Huawei): we added already something on Mon but companies need to be reasonable
RAN chair: so we need to make sure that everything that we approve related to RAN3 really fits into the RAN3 time budget
RAN chair and RAN thanked RAN3 chairman Philippe Reininger (Huawei) for his good and hard work in the last 4 years
| noted | No | |||
| RP‑170863 | List of CRs from RAN WG3 | ETSI MCC | discussion | Information | Yes |
Yes
| noted | No | ||||
| 5.4 | TSG RAN WG4 | RP‑170864 | Status Report RAN WG4 | RAN4 chairman (Samsung) | report | Yes |
Yespresented by RAN4 vice-chairman Hiromasa Umeda (NTT DOCOMO) presented the report on behalf of the RAN4 chairman
RAN chair: slide 17 covers only ongoing and not yet new SIs/WIs, correct?
RAN4 vice-chairman (NTT DOCOMO): correct
"The need of Nov Ad-hoc shall be confirmed in June plenary"
| noted | No | |||
| RP‑170865 | List of CRs from RAN WG4 | ETSI MCC | discussion | Information | Yes |
Yes
| revised | No | RP‑171394 | |||
| RP‑171394 | List of CRs from RAN WG4 | ETSI MCC | discussion | Information | Yes |
Yes
| noted | No | RP‑170865 | |||
| RP‑171150 | RAN4 NR progress and session management | Qualcomm Incorporated | discussion | Discussion | Yes |
NoProposal 1: Some NR related topics should be handled in the LTE RF session to increase the time available for discussion and speed up the process.
Proposal 2: Confirm the NR ad-hoc between RAN4#84Bis (mid Oct.) and RAN4#85 (end of Nov)
Sprint: proposal 1 would be ok, depends on how it is handled
Dish Networks: views from RAN4 chair and vice-chairmen would be useful, there is LTE/NR commonality so treated them together would be useful
RAN chair: proposal 1 is completely up to RAN4 leadership, regarding proposal 2 we could take a decision in Sep.
Sprint: has offered to host the Nov ad hoc but we would need to decide about the ad hoc this week
Ericsson, Nokia: there are just 6 weeks between the 2 WG meetings, adding another ad hoc in between would be critical for simulations
NEC: agrees with Ericsson and Nokia, rather extending RAN4 meetings over the week-end
RAN4 chair: proposal 1: we should see how the meeting goes, proposal 2: we have an offline discussion on Tue evening of RAN #76 to discuss RAN4 time budget so let's see this first
RAN chair: we will come back on this topic once we see the outcome of the
| available | No | ||||
| 5.5 | TSG RAN WG5 | RP‑170866 | Status Report RAN WG5 | RAN5 chairman (Motorola Mobility) | report | Yes |
YesRAN5 5G-NR Adhoc#1 16 – 20 April 2018 planned
| noted | No | |||
| RP‑170867 | List of CRs from RAN WG5 | ETSI MCC | discussion | Information | Yes |
Yes
| noted | No | ||||
| RP‑170868 | Status Report MCC TF160 (for approval) | ETSI MCC TF160 Leader | report | Approval | Yes |
Yes
| approved | No | ||||
| 5.6 | TSG RAN WG6 | RP‑170869 | Status Report RAN WG6 | RAN6 chairman (Nokia) | report | Yes |
Yespresented by RAN1 vice-chairman Matthew Baker (Nokia) on behalf of the RAN6 chairman
RAN chair: slide 25: on LSs: SA people are reminded to not forget to keep GERAN/RAN6 in the loop
SA chair: interested companies should drive their WIs but we can make sure that RAN6 is kept informed as well
RAN chair: slide 27: we need to have an action for this
SA chair: how do we handle this in SA, do we need an LS or is there a centralized approach?
RAN chair: no, each TSG will handle this separately, it seems CT did this already
Spec manager: recommends that WG chairs put this on their WG agenda, their is an application on the 3GPP web page under Specifications to detect the corresponding specs
conclusion: Regarding slide 27:
Action for RAN1/2/3/4/5/6: The WGs are tasked to check that their TRs/TSs (Rel-12 and onwards) are not referencing TS 44.118 and TS 44.160. If there is a reference, they have to provide corresponding CRs to RAN #77 to remove these references as it is intended to withdraw TS 44.118 and TS 44.160 at RAN #77.
| noted | No | |||
| RP‑170870 | List of CRs from RAN WG6 | ETSI MCC | discussion | Information | Yes |
Yes
| noted | No | ||||
| 6 | Other Reports | |||||||||||
| 6.1 | Report on TSG SA activities | RP‑170871 | TSG SA Report to TSG RAN - Questions for Advice and Requests | SA chairman (Samsung) | report | Yes |
Yes
| revised | No | RP‑171438 | ||
| RP‑171438 | TSG SA Report to TSG RAN - Questions for Advice and Requests | SA chairman (Samsung) | report | - | Yes |
YesCMCC: how could we handle Mobile Edge Computing?
SA chair: so far no coupling of SA work with RAN work is detected, if there is an input on this we would handle this in the usual way for inter-TSG related work
CMCC: yesterday it was said MEC is not addressed in RAN because it is more SA work and that if there is RAN impact SA would inform RAN by LS;
CMCC: if you see a need in SA2 to send an LS then you should present a proposal there, there is no need so far for SA to intervene
Telecom Italia: NB-IOT connected to 5G-CN will be considered in joint RAN-SA session?
SA chair: we will first discuss this topic in SA and see then what we need to discuss in the joint session
| noted | No | RP‑170871 | |||
| 6.2 | Report from PCG | |||||||||||
| 6.3 | Report from MCC | RP‑170872 | 3GPP Support Team Report | ETSI MCC | report | Yes |
YesRAN1 chair: election in RAN1 in Aug. with a high number voting companies: request to have multiple lines for voting to reduce the time needed for voting;
Qualcomm: slide 22: one company checking in for another company is strange; it could be critical if elections are decided just by a few votes;
Mediatek: if we detect these problems we need to react immediately and send an official email to these companies;
Ericsson: it may be even easier to simply to remove the voting rights;
specs manager: we could remove the voting rights from all affected companies;
RAN chair: this is what you should do
specs manager: it would be a lot of effort to check this on a permanent basis;
Qualcomm: asking for more radical solutions to solve these problems in only to have a reliable way to register and to check in;
Nokia: supports that corresponding registrations have to be removed;
Telecom Italia: for the host, do we have some information how big is the difference between people in the room and people checked in?
specs manager: just an example: CT yesterday: 50 people in the room, more than 100 checked in;
| noted | No | |||
| 6.4 | Reports from other groups/activities | RP‑171393 | IETF/3PP Cooperation on 5G | 3GPP CT Chairman (Huawei) | discussion | discussion | Yes |
YesRAN chair: reminder that IETF chair is coming on Wed in the lunch break to the RAN room for a presentation;
RAN chair: CT chair is the liaison person for IETF
| noted | No | ||
| 7 | Liaison activity of TSG RAN | RP‑170875 | LS requesting support for defining Next Generation Protocols (NGP(17)000038; to: RAN, CT, SA, IETF; cc: -; contact: Vodafone) | ETSI ISG NGP | LS in | Yes |
Yessuperseded by updated LS RP-170891
| noted | No | |||
| RP‑170891 | LS requesting support for defining Next Generation Protocols (NGP(17)000038r2; to: RAN, CT, SA, IETF; cc: -; contact: Vodafone) | ETSI ISG NGP | LS in | Yes |
YesRAN chair: any views from CT on this?
CT chair: plan is: collecting inputs from CT/RAN and SA will provide a response, CT views:
- in study phase for REL-15/16 on protocol requirements, inputs welcome
- do not want to be the man in the middle between NGP and IETF
- big attached documents, are not ready to be implemented in REL-15/16 so this is rather a longterm cooperation
RAN chair: anything we need to add from RAN? no comments were raised
conclusion: no LS answer from RAN, SA will send a reply LS
| noted | No | |||||
| RP‑170879 | LS on ETSI ISG MEC (Multi access Edge Computing) Phase 2 (MEC(17)000231; to: RAN, SA; cc: -; contact: Vodafone) | ETSI ISG MEC | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170880 | LS on the new structure of ITU-T SG20 (ITU_T_SG20_LS33; to: RAN, SA, ISO/TC 122, ISO/TC 204, ISO/IEC JTC 1/SC 6, ISO/IEC JTC 1/SC 31, ISO/IEC JTC 1/WG 7, ISO/IEC JTC 1/WG 10, ISO/IEC JTC 1/WG 11, GS1 EPCglobal, EC/IERC, ETSI, CEN, OMA, YRP, Ecma Internat | ITU-T SG20 | LS in | Yes |
YesRAN chair: is only for information for RAN
conclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170890 | LS on Standardisation of a new E-UTRA band (ATU_LS_170516; to: RAN, RAN4; cc: -; contact: ATU Secretary General) | ATU | LS in | Yes |
YesRAN chair: has RAN4 seen this?
RAN4 chair: yes, it was handled and there is a new WI proposal for this at RAN #76
conclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170903 | Reply LS to R1-1709716 on monitoring of partial NPDCCH search spaces (R2-1706195; to: RAN1; cc: RAN; contact: Huawei) | RAN2 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170904 | LS on Test Results of Technology Building Blocks phase of the Trial and Testing Initiative (NGMN_LS_170602; to: RAN, SA; cc: -; contact: KT) | NGMN | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170906 | reserved | ETSI MCC | LS in | No |
No
| reserved | No | |||||
| RP‑170907 | reserved | ETSI MCC | LS in | No |
No
| reserved | No | |||||
| RP‑170908 | reserved | ETSI MCC | LS in | No |
No
| reserved | No | |||||
| RP‑170909 | reserved | ETSI MCC | LS in | No |
No
| reserved | No | |||||
| 8 | ITU-R ad hoc | |||||||||||
| 8.1 | Status report | RP‑170873 | Status Report ITU-R Ad hoc | ITU-R Ad hoc Contact (Telecom Italia) | report | Yes |
Yes
| noted | No | |||
| 8.2 | Documents related to IMT-2020 | |||||||||||
| 8.3 | Other documents from/to ITU-R WP5D | |||||||||||
| 8.4 | Other documents from/to ITU-R WP5A | RP‑170905 | LS on the revision of Recommendation ITU-R M.2084-0 (ITU-R WP5A/TEMP/141(Rev.1); to: 3GPP, 5G Automotive Association, 79 GHz Project, ARIB, AWG, C2C-CC, CCSA, ETSI ERM-TG37, ETSI ERM-TGSRR, ETSI TC ERM, ETSI TC ERM TG 37, ETSI TC ITS, GSA, IEEE, IETF ITS, ISO TC 204, TIA, TTA, Wi-Fi Alliance; cc: -; contact: ITU-R SG5 Counselor) | ITU-R WP5A | LS in | Yes |
YesITU-R convener: we should task ITU-R ad hoc to contribute and prepare an input for RAN #77 in Sep.17
conclusion: ITU-R ad hoc is tasked to provide an input to RAN #77, so LS answer is postponed
| noted | No | |||
| 8.5 | Documents from/to other ITU-R groups | RP‑170900 | LS on ADJACENT BAND COMPATIBILITY STUDIES OF IMT-ADVANCED SYSTEMS IN THE MOBILE SERVICE IN THE BAND BELOW 1 518 MHz WITH RESPECT TO SYSTEMS IN THE MOBILE-SATELLITE SERVICE IN THE FREQUENCY BAND 1 518-1 525 MHz (ITU-R WP4C/TEMP/73; to: RAN; cc: ITU-R WP5D; | ITU-R WP4C | LS in | Yes |
YesITU-R convener: suggests to provide this LS also to RAN4; no action needed at the moment
conclusion: MCC will forward the LS to RAN4; no LS answer from RAN
| noted | No | |||
| 9 | New Radio | |||||||||||
| 9.1 | New WI/SI proposals for New Radio | RP‑171035 | Motivation for SI on NR positioning support | Intel Corporation | discussion | Discussion | Yes |
Yes
| not treated | No | ||
| RP‑171115 | Motivation for new Study Item on NR UE Positioning | CATT | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171034 | New SID: Study on NR positioning support | Intel Corporation, CATT, Qualcomm Inc. | WID new | Approval | Yes |
Yes
| not treated | No | RP‑170743 | |||
| RP‑170994 | Motivation for new SI on NR SON | CMCC | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑170995 | New Study Item proposal: Self-Organising Networks in New Radio | CMCC | SID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑170992 | Motivation for new SI : Study on vehicle UE for NR | LG Electronics Inc. | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑170991 | New SID on Study on vehicle UE for NR | LG Electronics Inc. | SID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑171110 | Motivation for Study on NR Sidelink Framework | CATT | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171111 | New SID on NR Sidelink Framework | CATT | SID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑171112 | Motivation for Study on UE Wakeup Mechanism in NR | CATT | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171113 | New SID on UE Wakeup Mechanism in NR | CATT | SID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑171046 | Motivation for new WI on MBMS support for non-standalone NR | LG Electronics Inc. | discussion | Yes |
Yes
| not treated | No | |||||
| RP‑171094 | Motivation for new SI : study on flexible and full duplex for NR | LG Electronics | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171114 | Consideration on further enhancement for high layer CU/DU split | CATT | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171033 | Motivation for SI on Enhancements to MIMO operation for NR | Intel Corporation | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171032 | New SID: Enhancements to MIMO operation for NR | Intel Corporation | SID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑171171 | Motivation for new Study Item on Multi Antenna Enhancements for NR | Nokia, Alcatel-Lucent Shanghai Bell | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171170 | New Study Item on Multi Antenna Enhancements for NR | Nokia, Alcatel-Lucent Shanghai Bell | SID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑171405 | Motivation for new WI: Enhancements on MIMO for NR | Samsung, ZTE, CATT | discussion | discussion | Yes |
Yes
| not treated | No | ||||
| RP‑171404 | New WID Proposal: Enhancements on MIMO for NR | Samsung | WID new | Approval | Yes |
Yes
| not treated | No | ||||
| RP‑171421 | New SI: CU-CP/CU-UP separation for NR | Ericsson | SID new | discussion | No |
No
| reserved | No | ||||
| 9.2 | Open REL-15 New Radio WIs | |||||||||||
| 9.2.1 | New Radio Access Technology [New WI: NR_newRAT] | RP‑171137 | Status Report of WI on New Radio Access Technology; rapporteur: NTT DOCOMO | RAN1 | WI status report | Yes |
YesNokia: single UL dual transmission decision of RAN1 has impact on other WGs and we need to discuss this further during this week
RAN chair: can come back on this in connection with RAN1 chairman's report
Huawei: unclear what we need to discuss
Nokia: it may even have an impact on RAN architecture
Qualcomm: our understanding is that there is no impact on higher layers
Ericsson: has some sympathy for Nokia proposal
RAN chair: we will discuss it further in connection with RAN1 report but please discuss it offline
Telecom Italia: sees also that there may be impact on RAN4
Huawei: the RAN1 agreement does not preclude 2 uplinks
conclusion: approved: Core: 22%, June 18 ; Perf.: 0%, Dec.18
| noted | No | |||
| RP‑170889 | LS on Closed Subscriber Group in 5GS (S1-172425; to: SA2, SA3, RAN; cc: -; contact: Qualcomm) | SA1 | LS in | Yes |
YesRAN3 chairman (Huawei): we do not have a home Node B concept in 5G so far, CSG at macro cell concept was never agreed so this exists only for home Node Bs
Deutsche Telekom: we should come up with a concept applicable to all scenarios
Mediatek: is not an SA1 issue and supports RAN3 chairman
Deutsche Telekom: bit indication in UMTS was a mistake, in LTE we did it correctly
Ericsson (new RAN3 chairman: supports RAN3 chairman that we would need more technical discussion, it would have been useful that this LS was also sent to RAN3
RAN chair: let's see the related discussion paper from Qualcomm in RP-171165
| replied to | No | |||||
| RP‑171165 | Discussion of Closed Subscriber Group (CSG) in NR | Qualcomm Incorporated | discussion | Decision | Yes |
Yesproposal: Basic functionality is required in release 15 NR to satisfy the request from SA1 to avoid legacy issues. RAN2 should be further tasked to perform technical analysis on forward compatibility, and define the required functionality.
RAN should note that the future introduction of CSG will be problematic otherwise.
Ericsson: we can take this use case into account in REL-15 addressing forward compatibility but it does not mean we need to implement it
Deutsche Telekom: we agreed already 1 bit for LTE and should do the same for NR so RAN should task RAN2
Vodafone: is CSG an agreed concept in CT in REL-15, then we should align otherwise we could discuss in RAN2/3
RAN chair: CSG concept is not yet agreed for REL-15 but it may impact compatibility, so let's have an LS response drafted in RP-171410
Huawei: agrees the forward compatibility issue but unclear what else we would answer
Qualcomm: will draft a reply
| noted | No | ||||
| RP‑171410 | Reply LS to RP-1710889 = S1-172425 on Closed Subscriber Group in 5GS (to: SA1; cc: SA2, SA3, RAN3; cc: -; contact: Qualcomm) | Qualcomm | LS out | approval | No |
No
| reserved | No | ||||
| RP‑170897 | LS on EPC QoS aspects for TSG RAN’s lower latency features (S2-173686; to: RAN, SA; cc: SA1, CT; contact: Vodafone) | SA2 | LS in | Yes |
YesRAN chair: item for early consideration; and this is one topic for the joint session with SA on Wed evening; draft reply to this LS in RP-171217
| replied to | No | |||||
| RP‑171217 | Draft reply LS to S2-173686 = RP-170897 on EPC QoS aspects for TSG RAN’s lower latency features (to: SA2; cc: SA, SA1, CT; contact: Nokia) | Nokia, Alcatel-Lucent Shanghai Bell | LS out | Approval | Yes |
YesEricsson: NR work is planned to complete in Dec., LTE work in Sep. so timing is quite clear
Mediatek: EPC part can not be answered by RAN, control plane latency is not enhanced
Vodafone: is not just a forward compatibility issue
Nokia: not all work will be completed in Dec.
KDDI: same view as Nokia: is for compatibility
| revised | No | RP‑171413 | |||
| RP‑171250 | Coordination of SA and RAN work on Low latency and URLLC | VODAFONE Group Plc | discussion | Approval | Yes |
YesProposal 1: Completion LTE work item on “Shortened TTI and processing time for LTE” by December 2017, and consider an early Release 15 ASN.1 freeze in March 2018.
Proposal 2: Respond to SA2 that we expect:
- Stage 3 completion of LTE low latency features in December 2017.
- Stage 3 completion of NR low latency for “Option 3 family” in December 2017.
Proposal 3: Agree to standardise one or a few QCIs for usage via EPC connected NR and LTE for low latency operation in Release 15.
Proposal 4: SA2 to strive to complete the standardisation of the first one or few QCIs for low latency services by December 2017.
Proposal 5: SA2 (and CT Working Groups) to strive to complete the standardisation of the “make before break” PDN connection continuity December 2017.
RAN chair: item for early consideration
Mediatek: we agreed at RAN #75 that the NR acceleration is the only acceleration
Nokia: finishing in Dec. seems reasonable but full ASN.1 freeze may not be beneficial as it would cause a lot of extra work
LG: would not be happy about a separate ASN.1 freeze
Huawei: LTE review for NSA will have to take place in March 18
RAN2 chair: correct, but sees a danger of setting a bad precedence case if we freeze one feature separately this time, we will see others next time
AT&T: supports RAN2 chairman
RAN chair: elements on short TTI completion should be captured in Nokia LS and we stick to the current ASN.1 freeze dates
Vodafone: stability of the feature is important, not so much the ASN.1 freeze; so we should emphasize that we do not touch it in a backward incompatible way after completion
Ericsson: from Ericsson point of view this should be fine, completion of the feature is a stage 3 completion and it is clear that we do not put the feature upside down afterwards
Nokia: can capture this in the LS
Vodafone: QCIs will be discussed in joint session?
RAN chair: yes
Vodafone: we have also an SA paper on this
Ericsson: what about target date?
RAN chair: realistically completion will probably Dec.
Huawei: this is in line with the current status report
RAN chair: so Dec.17 is assumed for the moment and can come back on this in connection with the status report
| noted | No | ||||
| RP‑171413 | Draft reply LS to S2-173686 = RP-170897 on EPC QoS aspects for TSG RAN’s lower latency features (to: SA2; cc: SA, SA1, CT; contact: Nokia) | Nokia, Alcatel-Lucent Shanghai Bell | LS out | Approval | Yes |
YesVodafone: not happy with the current text, SA2 asked us some specific questions and we answer "contact RAN2"
Nokia: we could delete the last sentence about QCI as this has nothing to do with the SA2 question
RAN2 chair: was wondering why SA2 could not decide on their own for a new QCI value, concluded that RAN could not conclude on this as this would require information from the core network;
RAN chair: do we see a need a new QCI value from RAN side?
Mediatek: we need technical discussion in the WGs about this, we are not changing control plane latency, agrees with Nokia that we could remove the last sentence if needed
Ericsson: supports Nokia
RAN chair: we could put text in [ ] and discuss it on Wed in the joint session
conclusion: remove comment, put [ ] around last paragraph and it will be still be a draft LS to be considered in joint session on Wed evening
| revised | No | RP‑171446 | RP‑171217 | ||
| RP‑171446 | Draft reply LS to S2-173686 = RP-170897 on EPC QoS aspects for TSG RAN’s lower latency features (to: SA2; cc: SA, SA1, CT; contact: Nokia) | Nokia, Alcatel-Lucent Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | RP‑171471 | RP‑171413 | ||
| RP‑171471 | Draft reply LS to S2-173686 = RP-170897 on EPC QoS aspects for TSG RAN’s lower latency features (to: SA2; cc: SA, SA1, CT; contact: Nokia) | Nokia, Alcatel-Lucent Shanghai Bell | LS out | Approval | No |
No
| reserved | No | RP‑171446 | |||
| RP‑170901 | LS on UE categories for NR and LTE-NR Dual Connectivity (R2-1706141; to: RAN, RAN1; cc: RAN4; contact: NTT DOCOMO) | RAN2 | LS in | Yes |
YesRAN chair: item for early consideration
| replied to | No | |||||
| RP‑170993 | UE categories for NR and LTE-NR Dual Connectivity | NTT DOCOMO, INC. | discussion | Decision | Yes |
YesProposal 1: Confirm the necessity of UE categories for all LTE-NR DC options (Option 3/4/7 series) as well as the NR standalone (Option 2).
Proposal 1a: Let RAN WGs decide technical details on how the UE category is defined for LTE-NR DC.
Proposal 2: Operators are asked to coordinate (offline or official email discussion) and input their opinion on DL/UL peak data rate targeted for Option 3 deployments to TSG-RAN #77.
RAN chair: item for early consideration
Telecom Italia: also other use cases than eMBB considered?
NTT DOCOMO: main use case for LTE-NR dual connectivity is eMBB
Vodafone: why is it needed to distinguish cat. between options 3, 4 and 7?
NTT DOCOMO: we have to complete option 3 by Dec.17
Deutsche Telekom: access capability are independent of architecture options, but we should discuss in Sep. which options a UE should support and also consider downscoping the options
Miedatek: agrees with Vodafone that SA and NSA categories should be discussed together
Ericsson: would not like to agree on proposal 1 immediately
Qualcomm: to proposal 1: can it be a throughput class rather than a cat.?
RAN chair: this may be a possibility to get rid of the UE cat. concept
Huawei: agrees with Qualcomm that NR and LTE do not need to use the same cat. concept
| noted | No | ||||
| RP‑171174 | Combined LTE-NR UE Category | MediaTek Inc. | discussion | Yes |
YesProposal#1 It is necessary to define UE categories in the LTE-NR DC (Opt. 3/4/7) as well as the NR standalone (Opt. 2) together
Proposal#2 The target peak data rate in DL and UL to be supported for Option 3 and Option 2 until December 2017.
Proposal#3 RAN to initiate email discussion toward RAN#77 on the peak data rate objectives for initial Rel-15 NR deployment by 2020
RAN chair: item for early consideration
CMCC: would like to have separate discussions of NSA and SA UE categories
Panasonic: concluding NSA case first is more important
RAN chair: not making UE cat. dependent on architecture options seems to be preferred, let's allocate a Tdoc for a draft LS answer for NTT DOCOMO in RP-171414
Mediatek: suggested to have email discussion until Sep.17 about alternative to UE categories
| noted | No | |||||
| RP‑171414 | Reply to R2-1706141 = RP-170901 on UE categories for NR and LTE-NR Dual Connectivity (to: RAN2; cc: RAN, RAN1; contact: NTT DOCOMO) | NTT DOCOMO | LS out | approval | No |
No
| reserved | No | ||||
| RP‑170898 | LS on Emergency Support in NR (S2-173700; to: RAN; cc: SA, RAN1, RAN2, RAN3; contact: Nokia) | SA2 | LS in | Yes |
Yes
| replied to | No | |||||
| RP‑170922 | Requirement for IMT Voice that Includes Regulatory Requirements | T-Mobile USA Inc. | discussion | Agreement | Yes |
Yesclarification that regulatory requirements for E911 with IMS Voice are part of the 5G-NR WID item and continues to be natively supported on NR for non-standalone (NSA) and standalone (SA)
RAN chair: seems to be clear to everyone
| noted | No | RP‑171390 | |||
| RP‑171166 | Support of location services over NR required for emergency calls | Qualcomm Incorporated | discussion | Decision | Yes |
Yesproposal: It is proposed TSG RAN #76 to adopt "TSG RAN#76 agrees that there is support for location services over NR in release 15 using RAT independent and E-UTRAN RAT dependent positioning methods" for rel.15. This can be extended to include LPP/LPPa support for NR in future releases.
Mediatek: asks for clarification how the exact regulatory requirement is
T-Mobile: 50m so far, does not specify a technology, passing NR 911 call to LTE to get location information will not fulfill regulatory requirement
LG: no location service in REL-15 preferred
RAN chair: did not think this is an option, we need to respond to the LS and we need to check whether we need to update our WID (T-Mobile seems to say the WID includes this implicitly so we need to check whether we need to be more clear);
CATT: option 1 and 2 will not work with voice over IMS, option 3 requires LTE
Ericsson: Cell-ID based on NR would be included anyway
Intel: option 3 does not work in standalone case, option 1 with proper scope could be considered in REL-15, does not think that Cell-ID based is possible
Nokia: we have Cell-ID concept in NR, we are looking for meeting regulatory requirements
RAN chair: LS to SA2 and RAN groups about the requirements for 911 to be considered; there will be one WID revision at the end of the week and we can consider to add something for this topic
Deutsche Telekom: there may be other requirements in other regions, e.g. in Germany Cell-ID is required
| noted | No | ||||
| RP‑171390 | Requirement for IMT Voice that Includes Regulatory Requirements | T-Mobile USA Inc. | discussion | Agreement | Yes |
Yes
| revised | No | RP‑171397 | RP‑170922 | ||
| RP‑171397 | Requirement for IMT Voice that Includes Regulatory Requirements | T-Mobile USA Inc. | discussion | Agreement | Yes |
Yes
| noted | No | RP‑171390 | |||
| RP‑171417 | Reply to S2-173700 = RP-170898 on Emergency Support in NR (to: SA2; cc: SA, RAN1, RAN2, RAN3; contact: T-Mobile) | T-Mobile | LS out | approval | Yes |
YesMCC: multiple versions of RP-171417 were distributed
| revised | No | RP‑171434 | |||
| RP‑171434 | Reply to S2-173700 = RP-170898 on Emergency Support in NR (to: SA2; cc: SA, RAN1, RAN2, RAN3; contact: T-Mobile) | T-Mobile | LS out | approval | Yes |
No
| available | No | RP‑171417 | |||
| RP‑171138 | Revision of WI: New Radio Access Technology | NTT DOCOMO, INC. | WID revised | Approval | Yes |
Yes
| revised | No | RP‑171418 | |||
| RP‑171418 | Revision of WI: New Radio Access Technology | NTT DOCOMO, INC. | WID revised | Approval | No |
No
| reserved | No | RP‑171138 | |||
| RP‑171315 | RAN WG chairmen's guidance related to specification approval for WI NR_newRAT | RAN1/RAN2/RAN3/RAN4 chairmen | discussion | Yes |
YesEricsson: proposal is not reflecting the latest RAN1 status
RAN2 chair: is based on current WID and further merging with other WID revisions is still needed
RAN3 chair: changes after Dec.17 to NSA should be F or B?
MCC: acc. to the agreements we are only looking for cat.F corrections but if we really need a cat.B CR then be honest and bring this to RAN for decision (do not falsify this to cat.F)
conclusion: will be merged into RP-171418
| merged | No | |||||
| RP‑170980 | Revised WID: New Radio Access Technology | Ericsson | WID revised | Approval | Yes |
YesNTT DOCOMO: not fine with the change but single RAT text would be ok, after single RAT we could talk about Multi-Standard
RAN4 chair: target dates for single RAT could be different
Ericsson: final approval could be in June 18
Nokia: before we are rushing too much we need to check the RAN4 impact
conclusion: parts of this Tdoc can be merged into RP-171418, details to be discussed offline
| merged | No | ||||
| RP‑170996 | Motivation for support of edge computing in NR WI | CMCC | discussion | Discussion | Yes |
YesProposal: It is proposed to include “RAN supporting of edge computing defined in SA2, if applicable” in current NR WID.
RAN3 chair: nothing against the feature but having generic features listed is probably not really helpful
Nokia: also understands that it is part of the WI but details are missing
Mediatek: "UE should be aware" is not in line with SA discussions and is rather a deployment issue
Ericsson: is ongoing SA2 work but does not see the RAN impact here
RAN chair: noone said that it is not part of the 5G scope but it may not be needed to spell this in out in the RAN WID
Ericsson: is SA2 work and if they identify any RAN impacts they will certainly let us know
Vodafone: there may be some UE impacts
CMCC: can we discuss MEC in RAN WGs?
RAN3 chairman (Huawei): should be discussed in connection with Tdoc about RAN3 prioritization
conclusion: If SA will identify any RAN impact, they will inform RAN and we will address this in due course.
| noted | No | ||||
| RP‑170997 | Update of WI: New Radio Access Technology | CMCC | WID revised | Approval | Yes |
Yesconclusion: No WID revision is approved but if SA will identify any RAN impact, they will inform RAN and we will address this in due course.
| rejected | No | ||||
| RP‑171167 | Proposed updated to WID on New Radio Access Technology | Qualcomm Incorporated | WID revised | Approval | Yes |
YesQualcomm: related to location services
RAN chair: can come back later
conclusion: merged into RP-171418
| merged | No | ||||
| RP‑171173 | Revised WID on New Radio Access Technology | Nokia Corporation | WID revised | Approval | No |
Yes
| withdrawn | Yes | RP‑170855 | |||
| RP‑171399 | LTE 4CC + NR 1CC combination to be added as CA band combination to NR WI | Telstra Corporation, Nokia, Ericsson, Samsung, Cohere Technologies | discussion | discussion | Yes |
YesRAN4 chair: in the future please make sure that you follow the RAN4 approach to bring the proposal to RAN4 first and make sure that it is included there
CMCC: some RAN1 impact?
conclusion: combination LTE (4CC) CA_3A-7C-28A + NR (1CC) 3.3 – 4.2 GHz will be included in RP-171418
Finally, it was decided to not include the combination at RAN #76 and to discuss the addition in RAN4.
| noted | No | ||||
| RP‑171186 | Considerations on the Progress of NR in RAN3 | RAN3 Chairman (Ericsson), RAN3 former Chairman (Huawei) | discussion | Discussion | Yes |
YesProposal 1: RAN to consider making NR option family 7 as part of the June 2018 drop and confirm that a specified F1 is part of the December 2017 drop; in alternative, RAN to consider making a fully specified F1 part of the June 2018 drop and keeping the current work plan for option families 3 and 7 as it is.
Proposal 2: Considering the current load of RAN3, and the need to progress in order to provide by December a first ASN.1 (including option 3, potentially F1/CP-UP separation), it is requested to RAN to treat the following topics as low priority, e.g. discuss if time allows until December, NG ‘agnostic’, SA2 related topics.
Nokia: concern about proposal 2, topics with architecture impacts need to be considered early enough otherwise they cannot happen
Deutsche Telekom: supports Nokia
RAN3 chairman (Huawei): this is not an attempt to stop the work but a reminder that we have priorities to be taken into account
Telecom Italia: ASN.1 freeze is in March 18, if RAN3 has an overload issue here, then we need to revise the priorities
Broadcom: changes regarding non-3GPP access are minor
RAN chair: would like to check all architecture topics before having a summary we could provide to RAN3 for further discussion
| noted | No | ||||
| RP‑170968 | Termination points for NG, S1-U, Xn and X2 interfaces | Deutsche Telekom, T-Mobile USA, Orange, TELUS, Telekom R&D Sdn. Bhd., Telecom Italia, BT, SK Telecom, KT, Samsung, Telstra, Telefonica et al | pCR | Endorsement | Yes |
YesRAN chair: item for early consideration
CMCC, China Unicom: support the proposal
| rejected | No | ||||
| RP‑171216 | Termination points for NG and Xn interfaces | Ericsson | discussion | Decision | Yes |
Yesproposal: ask 3GPP TSG RAN to follow the argumentation line provided in this document and to
- acknowledge the working assumption from RAN3#95bis that the Internal structure of the gNB is not visible to the CN and to other RAN nodes.
- abstain from following proposals brought forward in RP-170968
RAN chair: item for early consideration
Deutsche Telekom: only one company supporting this view
RAN chair: so where are we: a fully interoperable interface on S1 seems to be wanted by operators and we need to check the corresponding impacts; so it is needed that people sit together to address the issues
Ericsson: S1 will be a fully operable multi-vendor interface, noone is disputing this
BT: we need to decide the termination before we specify F1
conclusion: Ericsson will summarize result of offline discussion in RP-171419 (no piggy-backing of NG messages ...)
| noted | No | ||||
| RP‑171419 | Way forward on termination points NG and Xn interfaces | Ericsson | discussion | discussion | Yes |
No
| available | No | ||||
| RP‑171049 | F1 interface: Work Plan on F1 | NTT DOCOMO, INC. | discussion | Approval | Yes |
YesProposal: RAN to confirm that F1 specification for NSA aspects should be completed by Dec. 2017.
RAN chair: so target for F1 for stage 2 and stage 3 is Dec.17
RAN3 chair (Huawei): we need to take prioritization into account
RAN chair: can we endorse RP-171049?
Vodafone: we need to look at the full picture
Ericsson: approving F1 in Dec.17 will be challenging
Deutsche Telekom: we may have to downprioritize other topics
conclusion: RP-171049 is endorsed with the understanding that we need to make sure that we do not overpromise considering the work load
| endorsed | No | ||||
| RP‑171215 | Separation of CP and UP | Ericsson | discussion | Decision | Yes |
YesProposal 1: RAN is kindly asked to approve the standardization of a new control interface between CU-CP and CU-UP in RAN3. We suggest to name this interface E1.
Proposal 2: The E1 interface should be added to the NR Access Technology WID RP-170855.
RAN chair: item for early consideration
RAN3 chair (Huawei): it was asked whether this is part of the WI?
Nokia: does not think it is part of the existing WI at the moment, it it an interesting area but there are a number of open issues we would need to study first so starting a WI would be too early
NTT DOCOMO: there was no conclusion of CU-CP and CU-UP separation so far
Vodafone: supports the proposals
Deutsche Telekom: we were always promoting the CU-CP and CU-UP separation and proposed this already some time ago
ZTE: it is clear that currently it is not covered but we can discuss whether to add it, but since RAN3 is overloaded we can could consider it later but not calling it E1 may be better;
LG: topic should be also discussed with RAN2 as it is not a RAN3 only issue
NEC: supports to further study this first
RAN chair: we could have a 6 months SI and then could still have a WI afterwards in REL-15
RAN3 chair (Huawei): currently no time/TU available in RAN3 for a SI
conclusion: Ericsson will draft a SI proposal in RP-171421, leading WG: RAN3, RAN2 secondary responsible, target date: Dec.17
| noted | No | ||||
| RP‑171252 | Discussion on gNobe B logical description | VODAFONE Group Plc | discussion | Discussion | No |
Yes
| withdrawn | Yes | ||||
| RP‑171172 | A concern on NR standardization | SoftBank Corp. | discussion | Yes |
Yesproposal:
• RAN and WGs to consider further scope redunction (or something similar, e.g. delaying the start of SIs) to assign more time to review/stabilize the NR specifications, especially at the last half of Rel-15.
• RAN should this discuss this issue in RAN#77 taking into account the progress of NR work.
RAN chair: item for early consideration
Mediatek: this morning we have already increased the NR WI scope and we seriously need to consider the Softbank proposal
Deutsche Telekom: we would be happy do further shift the SIs
KT: downscoping of NR WI would be better
Telecom Italia: delaying SIs until Sep.17 would be ok for us
Deutsche Telekom: would this means SIs would complete a quarter later?
Thales: delaying NR SIs would impact scoping of satellite aspects in RAN?
RAN1 chair: only RAN1 led SIs should be shifted
Ericsson: if we take SIs one by one we will probably not achieve anything so a general guidance RAN1 led SIs should be kept on hold until Sep.17
Ericsson: RAN3 led SIs will be handled in RAN1?
RAN chair: RAN1 work for such a SI should also be on hold
Sprint: what about RAN2?
RAN chair: in RAN2 no TUs for NR SIs allocated
conclusion: Softbank will summarize the way forward on postponing RAN1 work of NR SIs until Sep.17
| noted | No | |||||
| RP‑171422 | Way forward on postponing RAN1 work for NR SIs | Softbank | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171249 | NR Standardization | NEC EUROPE LTD | discussion | Discussion | No |
YesRAN chair: item for early consideration
| withdrawn | Yes | ||||
| RP‑170882 | Reply LS to ECC_PT1_LS_160915 = RP-161968 and ECC_PT1_LS_170120b = RP-170037 on Suitability of technical conditions of ECC DEC (11) 06 for 5G (R4-1704402; to: ECC PT1; cc: RAN, ETSI TC ERM; contact: Ericsson) | RAN4 | LS in | Yes |
YesRAN chair: is only for information for RAN
conclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170884 | Reply LS to S2-171611 = RP-170035 on N2 and N3 reference points for 5G system (R3-171401; to: SA2; cc: SA, RAN, CT, CT4, CT1, SA3, RAN2; contact: Qualcomm) | RAN3 | LS in | Yes |
YesRAN chair: is only for information for RAN
conclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170892 | LS on NGMN Paper on 5G End-to-end Architecture Framework (NGMN_LS_170511; to: SA2; cc: SA, RAN; contact: Vodafone) | NGMN | LS in | Yes |
YesRAN chair: is only for information for RAN
conclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170886 | LS on Requesting status and technical information on WLAN integration in 3GPP NextGen System (IEEE 802.11-16/1574r3; to: SA, SA1, SA2, SA3; cc: IEEE 802 EC, IEEE 802.1 WG, RAN; contact: InterDigital) | IEEE 802.11 WG | LS in | Yes |
Yesconclusion: no LS answer from RAN (is primarily for SA)
| noted | No | |||||
| RP‑171437 | RAN3 way forward on workplan | RAN3 chairman (Ericsson) | discussion | discussion | No |
No
| reserved | No | ||||
| 9.3 | Open REL-15 New Radio SIs | |||||||||||
| 9.3.1 | Study on NR to support non-terrestrial networks [New SI: FS_NR_nonterr_nw] | RP‑170981 | Status Report for SI Study on NR to support Non Terrrestrial Networks; rapporteur: Thales | RAN1 | WI status report | Yes |
Yesconclusion: approved: 0%, Dec.17
| noted | No | |||
| RP‑170983 | Draft TR 38.811 v0.0.0 for NR to support Non Terrestrial Networks | Thales | draft TR | Discussion | Yes |
YesMCC: FS_NR_nonterr_nw is a RAN1 SI and TR should be submitted to RAN1
note: leadership of this TR will be changed from RAN1 to RAN
| revised | No | RP‑171453 | |||
| RP‑171453 | TR 38.811 v0.1.0 on Study on NR to support non-terrestrial networks | Thales | draft TR | Agreement | No |
No
| reserved | No | RP‑170983 | |||
| RP‑170921 | Revised SID: Study on NR to support Non-Terrestrial Networks | THALES | SID revised | Approval | Yes |
Yesconclusion: among othe changes, the leadership of the SI and the SI TR 38.811 will be moved from RAN1 to RAN
| revised | No | RP‑171450 | |||
| RP‑170973 | On NR support of non-terrestrial networks | Ericsson LM | discussion | Agreement | Yes |
YesProposal 1 : Prioritize the work on satellites
Proposal 2 : Remove the overlap with the ongoing SI on enhanced LTE support for aerial vehicles
Ericsson: SID is too wide at the moment
Dish: there is a SID revision in which we could include the changes there
Nokia: overlap in channel modelling part is not clarified enough so the 2nd SID change should be improved
Ericsson: if "first priority" is changed to scope then this would be ok
conclusion: first change can be included adding HUBs and replacing "first priority" by "scope", then 2nd change not needed, will be covered in the revision of SID RP-170921 in RP-171450
| noted | No | ||||
| RP‑171450 | Revised SID: Study on NR to support Non-Terrestrial Networks | THALES | SID revised | Approval | No |
No
| reserved | No | RP‑170921 | |||
| RP‑170917 | Proposed template for the NR-NTN technical report | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170918 | Proposed scope for the sFS_NR_nonterr_nw technical report | THALES | pCR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170929 | Non-Terrestrial Network overview | THALES | pCR | Approval | Yes |
Yesspecs manager: why is RAN drafting a RAN1 TR? We need a proper TR template
Qualcomm: KPIs are mentioned, would prefer to remove it
Nokia: capabilities always dimensioned for worst case?
Ericsson: taking use cases first will help, drones, helicopters etc. excluded?
Thales: correct
| revised | No | RP‑171447 | |||
| RP‑171447 | Non-Terrestrial Network overview | THALES | pCR | Approval | No |
No
| reserved | No | RP‑170929 | |||
| RP‑170930 | Non-Terrestrial Network Deployment scenarios | THALES | pCR | Approval | Yes |
YesEricsson: commercial airplanes? you are rather considering rather high altitude platforms
Qualcomm: KPIs also need to be removed here
| revised | No | RP‑171448 | |||
| RP‑171448 | Non-Terrestrial Network Deployment scenarios | THALES | pCR | Approval | No |
No
| reserved | No | RP‑170930 | |||
| RP‑170982 | Propagation delay and Doppler in Non-Terrestrial Networks | THALES | pCR | Approval | Yes |
YesZTE: channel modelling should be discussed in RAN1
Qualcomm: code Doppler: may be ok for DL but not for UL so that that needs further study
RAN chair: could be put ffs
Ericsson: RAN1 should look at this document
Qualcomm: thought deployment part is under RAN control
| revised | No | RP‑171449 | |||
| RP‑171449 | Propagation delay and Doppler in Non-Terrestrial Networks | THALES | pCR | Approval | No |
No
| reserved | No | RP‑170982 | |||
| 9.3.2 | Study on CU-DU lower layer split for New Radio [New SI: FS_NR_CU_DU_LLS] | RP‑171176 | Status report of Study on CU-DU lower layer split for New Radio; rapporteur: NTT DOCOMO, INC. | RAN3 | WI status report | Yes |
YesMCC: late submission
conclusion: approved: 0%, Dec.17
| noted | No | |||
| 9.3.3 | Study on NR-based access to unlicensed spectrum [New SI: FS_NR_unlic] | RP‑171322 | Status report for SI Study on NR-based access to unlicensed spectrum; rapporteur: Qualcomm | RAN1 | WI status report | Yes |
YesMCC: late request
conclusion: approved: 0%, June 18
| noted | No | |||
| RP‑171128 | Specification handling of 3GPP-based access to unlicensed spectrum | Huawei, HiSilicon | discussion | Discussion | Yes |
YesRAN chair: Tdoc for early consideration
proposal:
- From Rel-15 onwards, standard impact specific to 3GPP-based access to unlicensed spectrum will be specified in a different set of specifications.
- No use of unlicensed spectrum will be assumed in the IMT-2020 self-evaluations from 3GPP, and the corresponding specifications will not be submitted to ITU-R as part of the IMT-2020 submission.
Broadcom: unclear how non-3GPP access would be addressed
RAN chair: this is not affected
MCC: we discussed this topic offline at last meeting with the specs manager and his clear answer was that we will not be able to allocate another spec series for this (shortage of series numbers); will this split only affect RAN1 and RAN4 specs?
Huawei: correct
RAN1 chair: some further discussion about RAN1 specs needed
Dish Networks: will we remove band 46 from the specs?
RAN4 chair: suggests that RAN4 checks the impacts and comes back next quarter
RAN chair: would prefer to not load WGs with this
Telecom Italia: LTE CRs for next time?
RAN chair: yes, no hurry for this
conclusion: proposal is endorsed with the focus on RAN1 and RAN4 specs, detailed to be discussed with MCC/specs manager
| noted | No | ||||
| RP‑171416 | Revised SI: Study on NR-based Access to Unlicensed Spectrum | Qualcomm | SID revised | Approval | Yes |
Yes
| approved | No | ||||
| 9.3.4 | Study on Non-Orthogonal Multiple Access (NOMA) for NR [New SI: FS_NR_NOMA] | RP‑171185 | Status report of SI Study on 5G Non-Orthogonal Multiple Access ; rapporteur:ZTE | RAN1 | WI status report | Yes |
Yesconclusion: approved: 0%, June 18
| noted | No | |||
| RP‑171042 | Summary of the workshop on NOMA | ZTE Corporation | discussion | Information | Yes |
YesMediatek: workshop is outside of 3GPP?
ZTE: correct
| noted | No | ||||
| RP‑171043 | Revision of Study on 5G Non-Orthogonal Multiple Access | ZTE Corporation | SID revised | Approval | Yes |
Yes
| approved | No | RP‑170829 | |||
| 9.3.5 | Study on integrated access and backhaul for NR [New SI: FS_NR_IAB] | RP‑171318 | Status report for SI Study on integrated access and backhaul for NR; rapporteur: Qualcomm | RAN2 | WI status report | Yes |
YesMCC: late request
| revised | No | RP‑171333 | ||
| RP‑171333 | Status report for SI Study on integrated access and backhaul for NR; rapporteur: Qualcomm | RAN2 | WI status report | Yes |
YesMCC: late request
conclusion: approved: 0%, June 18
| noted | No | RP‑171318 | ||||
| 9.3.6 | Study of test methods for New Radio [New SI: FS_NR_test_methods] | RP‑171020 | Status report of SI: Study on test methods for New Radio; rapporteur: Intel | RAN4 | WI status report | Yes |
Yesconclusion: approved: 10%, March 18
| noted | No | |||
| RP‑171021 | Revision of SI: Study on test methods for New Radio | Intel Corporation | SID revised | Approval | Yes |
Yes
| approved | No | ||||
| 9.3.7 | Study on evaluation methodology of new V2X use cases for LTE and NR [New SI: FS_LTE_NR_V2X_eval] | RP‑171092 | Status report of SI: Study on evaluation methodology of new V2X use cases for LTE and NR; rapporteur: LG Electronics | RAN1 | WI status report | Yes |
Yesconclusion: approved: 0%, Dec.17
| noted | No | |||
| RP‑171093 | Revision of SI: Study on evaluation methodology of new V2X use cases for LTE and NR | LG Electronics | SID revised | Approval | Yes |
Yes
| approved | No | ||||
| 9.3.8 | Study on self-evaluation towards IMT-2020 submission [New SI: FS_5G_eval] | RP‑171090 | Status report for SI: Study on Self-Evaluation towards IMT-2020 submission; rapporteur: Huawei | ITU-R ad hoc | WI status report | Yes |
Yesconclusion: approved: 0%, June 18
| noted | No | |||
| RP‑170913 | Motivation for change request on Self Evaluation towards IMT-2020 Submission Study Item | TELEFONICA S.A. | discussion | Decision | No |
Yes
| withdrawn | Yes | ||||
| RP‑171044 | Discussion on SID and work plan of self-evaluation towards IMT-2020 submission | ZTE Corporation | discussion | Yes |
YesProposal 1: Phased approach including calibration phase, performance evaluation phase and submission template preparation phase should be clearly described in the SID.
Proposal 2: NR MIMO calibration should be reused and continue in this self-evaluation SI at least for eMBB. A new set of calibration should be setup in this SI for scenarios which are not covered by NR MIMO calibration e.g. URLLC and mMTC.
Proposal 3: Update the SID to allow updated proposal submission with additional self-evaluation before June 2019.\
Proposal 4: Update the meeting time of ITU-R WP 5D meeting #32 in Justification part of the SID.
Proposal 5: RAN4 should be involved in evaluation of other requirements described in Objective (d) of the SID.
Proposal 6: Update the SID to describe technical performance requirements for each of the three eMBB test environments in objective (a).
Huawei: some of the proposals are already reflected (4. and 5.) in the revised SID, some proposals (3.) were discussed in the offline discussion on Tue morning, calibration and proposal 1./2./6. are a bit too early i.e. we should wait for WP5D and can then probably refer to their documents;
Mediatek: system description also needs to be included in submission template or just the self-evaluation;
ZTE: probably also system description needs to be included in template as well
| noted | No | |||||
| RP‑171129 | Updated workplan for the study on self-evaluation towards IMT-2020 submission | Huawei, Ericsson, Telecom Italia | discussion | Information | Yes |
YesProposal: plan a session at RAN#77 where companies are encouraged to provide views on the following aspects to facilitate the work on self evaluation towards IMT-2020 submission.
- Review the draft skeleton of TR 37.910
- Provide views on 3GPP’s IMT-2020 submission format (RIT/SRIT definition)
- Provide views on evaluation configurations as defined in Report ITU-R M.[IMT-2020.EVAL], and the technical features to be evaluated to meet eMBB, mMTC and URLLC technical performance.
- Details can be further discussed in related RAN WGs.
RAN1 chair: worried about TUs needed
| noted | No | ||||
| RP‑171091 | Revision of SI: Study on self-evaluation towards IMT-2020 submission | Huawei, Ericsson, Telecom Italia | SID revised | Approval | Yes |
Yes
| revised | No | RP‑171439 | |||
| RP‑171439 | Revision of SI: Study on self-evaluation towards IMT-2020 submission | Huawei, Ericsson, Telecom Italia | SID revised | Approval | Yes |
YesMCC: suggests to have RAN as primary resp. as it will be RAN and not ITU-R ad hoc which is creating new TR versions
Huawei: time budget has TUs in [ ] and it is still unclear
RAN chair: can be done in Sep.17
conclusion: revised to correct prim. resp. to RAN, ITU-R ad hoc will be sec. resp.
| revised | No | RP‑171451 | RP‑171091 | ||
| RP‑171451 | Revision of SI: Study on self-evaluation towards IMT-2020 submission | Huawei, Ericsson, Telecom Italia | SID revised | Approval | No |
Yes
| approved | No | RP‑171439 | |||
| 9.4 | Closed REL-14 New Radio SIs | RP‑170967 | Update to TR 38.913 to take into account ITU-R KPIs | TELECOM ITALIA S.p.A. | CR | Approval | Yes |
Yes
| approved | No | ||
| RP‑170955 | CR to TR 38.912 on architecture and LDPC terminology | NTT DOCOMO, INC. | CR | Approval | Yes |
Yes
| revised | No | RP‑171386 | |||
| RP‑171386 | CR to TR 38.912 on architecture and LDPC terminology | NTT DOCOMO, INC. | CR | Approval | Yes |
YesNTT DOCOMO: related to RAN1 and RAN3 CRs to the SI TRs
| approved | No | RP‑170955 | |||
| RP‑171104 | Architecture terminology update | Huawei | draftCR | Endorsement | No |
Yes
| withdrawn | Yes | ||||
| RP‑171207 | Maintenance to TR38.900/38.901 related to channel model for frequencies from 0.5 to 100 GHz | RAN1 | CR pack | Approval | Yes |
YesMCC: WI code for TR 38.901 has to be FS_NR_newRAT
| approved | No | ||||
| RP‑171208 | Maintenance to TR38.802/TR38.901 related to New Radio (NR) Access Technology | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171254 | RAN4 38.803 CRs to Closed REL-14 New Radio SIs | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171253 | RAN4 TR 38.803 CRs to New Radio Access Technology | RAN4 | CR pack | Approval | Yes |
YesMCC: CRs are modifying former SI TR 38.803 with cat.B CRs and wrong WI code NR_newRAT; WID RP-170855 is crystal clear: TR 38.803 is not affected
Nokia: reminder to leave enough time for RAN4 to finish their work
RAN chair: avoid cat.B CRs to completed SIs in the future
conclusion: WI codes will be corrected to FS_NR_newRAT in RP-171452
| revised | No | RP‑171452 | |||
| RP‑171452 | RAN4 TR 38.803 CRs to New Radio Access Technology | RAN4 | CR pack | Approval | No |
Yes
| approved | No | RP‑171253 | |||
| 9.5 | Other inputs | RP‑171430 | Views on NR UL coverage | Qualcomm | discussion | discussion | Yes |
Yes
| revised | No | RP‑171445 | |
| RP‑171445 | Views on NR UL coverage | Qualcomm | discussion | discussion | Yes |
YesTelecom Italia: suppl. UL in line with RAN1?
Qualcomm: some simultaneous UL assumed
Huawei: we do not agree with everything but contents almost in line with WGs, the Tdoc was late and we do not need to treat WG discussion here
Nokia: Tdoc shows that multiple aspects have to be considered in RAN1 (e.g. coverage aspect) so we need to avoid that one WG decides alone about systemwide aspects
Orange: would like to have a continuation of this discussion in RAN1
ZTE: discussion on WG level appreciated but as Nokia said some system aspects need to be discussed in RAN
Vodafone: Tdoc highlights all of the issues but does not have the solutions, we need to address the issues and not just say it's complex
Qualcomm: providing good UL coverage is crucial, reason why we use UL sharing needs to be clear in order to find good solutions
RAN chair: companies are encouraged to discuss this more and to take this up in the WGs
| noted | No | RP‑171430 | |||
| 10 | LTE | |||||||||||
| 10.1 | New WI/SI proposals for LTE | |||||||||||
| 10.1.1 | led by RAN1 | |||||||||||
| 10.1.2 | led by RAN2 | RP‑171117 | Motivation for new WI on Further Enhancements LTE Device to Device, UE to Network Relays for IoT and Wearables | Huawei, Huawei Device | discussion | Discussion | Yes |
YesNokia: existing SI is still ongoing in RAN1 and this should be completed before we start a WI; detailed contents of the WI needs to be discussed offline as it seems to be a basket for several topics
Ericsson: same views
ZTE: similar views, if we would start it we would need to improve the scope a lot
Qualcomm: same views
LG: RAN2 TUs need to be reconsidered for the SI if we have no WI
Samsung: supports Nokia view
RAN1 chair: RAN1 time budget already overloaded for the next 6 months
Huawei: we timed the SI to start RAN2 study part now; compromise offer to allow to treat SA1/SA2 LSs;
US Dep.of Commerce: we are supporting this work
RAN2 chair: this shows that starting a SI where the leading WG has no time allocated is not ideal;
conclusion: SI will continue, LSs will be handled in RAN2 as business as usual (within SI scope) and we discuss a WI proposal again in Sep.17
| noted | No | ||
| RP‑171054 | Motivation for new WI on Further Enhancements to LTE Device to Device, UE to Network Relays for IoT and Wearables | LG Electronics Inc. | discussion | Yes |
Yes
| not treated | No | |||||
| RP‑171116 | New WI proposal: Further Enhancements LTE Device to Device, UE to Network Relays for IoT and Wearables | Huawei, Huawei Device, Intel, LG Electronics, Sony | WID new | Approval | Yes |
Yes
| revised | No | RP‑171415 | |||
| RP‑171415 | New WI proposal: Further Enhancements LTE Device to Device, UE to Network Relays for IoT and Wearables | Huawei, Huawei Device, Intel, LG Electronics, Sony | WID new | Approval | No |
Yesconclusion: withdrawn as not available
| withdrawn | Yes | RP‑171116 | |||
| RP‑171168 | FeD2D assessment based on architecture impacts | Qualcomm Incorporated | discussion | Decision | Yes |
Yes
| not treated | No | ||||
| RP‑171108 | How to progress on UDC WI | CATT | discussion | Discussion | Yes |
YesRAN chair: item for early consideration
Nokia: supports downselection but it should be done in RAN and not in RAN2
Samsung: supports Nokia
Ericsson: for one of the algorithms there was a lack of information so that's where the downselection in WG makes sense
Mediatek: prefers decision this week in RAN
RAN chair: suggests info is provided to RAN2 until 26.6.; RAN2 can analyse in their Aug. meeting and in Sep.17 at RAN #77 we will decide (down selection between DEFLATE-based solution and APDC solution)
Mediatek: companies should be able to verify the performance
Broadcom: there are algorithms in IETF for 10 years and we should check first that they do not provide what we need before we introduce something else
Samsung: this means we extend the SI by one quarter based on a company that did not provide their input earlier
Mediatek: RAN2 analysis should be only on APDC solution
conclusion: additional information on APDC solution is provided to RAN2 by 26.06.2017, RAN2 will do corresponding analysis on APDC solution and RAN #77 in Sep.17 will decide between DEFLATE-based solution and APDC solution
| noted | No | ||||
| RP‑171109 | New WID on UL data compression in LTE | CATT, Qualcomm Incorporated | WID new | Approval | Yes |
Yes
| revised | No | RP‑171387 | |||
| RP‑171387 | New WID on UL data compression in LTE | CATT, Qualcomm Incorporated | WID new | Approval | Yes |
YesRAN chair: item for early consideration
| not treated | No | RP‑171109 | |||
| RP‑171184 | Algorithm for UDC | MediaTek Inc. | discussion | Yes |
YesRAN chair: item for early consideration
| not treated | No | |||||
| RP‑171398 | Comments regarding UL data compression (UDC) | KDDI | discussion | discussion | Yes |
Yes
| not treated | No | ||||
| 10.1.3 | led by RAN3 | RP‑171119 | Motivation for new WI on Network Assistance for Network Synchronization in LTE | Huawei, HiSilicon | discussion | Discussion | Yes |
Yes
| not treated | No | ||
| RP‑171118 | New WI proposal: Network Assistance for Network Synchronization in LTE | Huawei, HiSilicon | WID new | Approval | Yes |
YesHuawei: was proposed already in March 17
Ericsson: same comment: why is solution 1/option 1 included as SI did not conclude on it
RAN chair: would you be fine with the other solutions?
Ericsson: yes
Deutsche Telekom: would like to see solution 1 in
Samsung: agrees with Ericsson that solution 1 should not be in
RAN3 chair (Huawei): no TU available in RAN3,, so better come back in Dec.17
Nokia: supports RAN3 chair
RAN chair: is the new RAN3 chair also ok to postpone the WI proposal to Dec.17?
new RAN3 chair (Ericsson): ok
| postponed | No | ||||
| 10.1.4 | led by RAN4 (not spectrum related) | RP‑170940 | Motivation for new WI on Performance requirements of interference cancellation receiver for LTE BS | China Telecom, Huawei | discussion | Discussion | Yes |
No
| available | No | ||
| RP‑170939 | New WID on performance requirements of interference cancellation receiver for LTE BS | China Telecom, Huawei | WID new | Approval | Yes |
Yes
| revised | No | RP‑171411 | |||
| RP‑171411 | New WID on performance requirements of interference cancellation receiver for LTE BS | China Telecom, Huawei | WID new | Approval | Yes |
No
| available | No | RP‑170939 | |||
| RP‑170976 | Motivation for new Work Item on network based CRS mitigation for LTE | Ericsson | discussion | Information | Yes |
No
| available | No | ||||
| RP‑170977 | New Work Item on UE requirements for network-based CRS mitigation for LTE | Ericsson | WID new | Approval | Yes |
Yes
| revised | No | RP‑171408 | |||
| RP‑171408 | New Work Item on UE requirements for network-based CRS mitigation for LTE | Ericsson | WID new | Approval | No |
No
| reserved | No | RP‑170977 | |||
| RP‑171015 | Motivation for WI: LTE CRS-IM Performance Requirements for Single RX Chain UEs | Intel Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171014 | New WI Proposal: LTE CRS-IM Performance Requirements for Single RX Chain UEs | Intel Corporation | WID new | Approval | Yes |
Yes
| revised | No | RP‑171465 | |||
| RP‑171465 | New WI Proposal: LTE CRS-IM Performance Requirements for Single RX Chain UEs | Intel Corporation | WID new | Approval | No |
No
| reserved | No | RP‑171014 | |||
| RP‑171017 | Motivation for SI: Study on Advanced Receivers LTE V2X | Intel Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171016 | New SI proposal: Study on Advanced Receivers for LTE V2X | Intel Corporation | SID new | Approval | Yes |
No
| available | No | ||||
| RP‑171023 | Motivation for SI: Enhanced Carrier Aggregation Mobility | Intel Corporation | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171022 | New SI Proposal: Enhanced LTE Carrier Aggregation Mobility | Intel Corporation | SID new | Approval | Yes |
No
| available | No | ||||
| RP‑171125 | Motivation for new work item on LTE DL 8Rx antenna ports | Huawei, HiSilicon | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171124 | New WI proposal: LTE DL 8Rx antenna ports | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171147 | Motivation for New Work Item on Lower Complexity Higher Order MIMO for LTE | Qualcomm Incorporated | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171145 | New Work Item: Lower Complexity Higher Order MIMO for LTE | Qualcomm Incorporated | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171181 | Legacy UE protection for Lean Carrier | MediaTek Inc. | discussion | Yes |
NoProposal 1: Solutions for network-based CRS mitigation support in legacy devices need to be first identified in a RAN1-led Study Item.
Proposal 2: Solutions identified for Network-based CRS mitigation with no impact on legacy devices can be specified in a RAN1-led working item.
| available | No | |||||
| RP‑171454 | Way forward on new proposals in RAN4 | RAN4 vice-chairman (Huawei) | discussion | discussion | No |
NoRAN4 vice-chairman: SKT was part of the offline discussion so we need to check with them
| reserved | No | ||||
| 10.1.5 | led by RAN4 (spectrum related) | RP‑170962 | New WID: LTE Advanced intra-band Carrier Aggregation Rel-15 for xDL/yUL including contiguous and non-contiguous spectrum | Ericsson | WID new | Approval | Yes |
No
| available | No | ||
| RP‑171002 | Motivation for necessity dual uplink intra-band non-contiguous CA_7A-7A with operator specific holding spectrum restriction | SK Telecom, LG Electronics | discussion | Decision | Yes |
No
| available | No | ||||
| RP‑171026 | New WID: LTE Advanced inter-band Carrier Aggregation Rel-15 for 2DL/1UL | Qualcomm Incorporated | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171126 | New WID proposal: LTE Advanced inter-band CA Rel-15 for 3DL/1UL | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑170963 | New WID: LTE Advanced inter-band Carrier Aggregation Rel-15 for 4DL/1UL | Ericsson | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑170935 | New WI: LTE Advanced inter-band CA Rel-15 for 5DL/1UL | Nokia | WID new | Approval | Yes |
Yes
| revised | No | RP‑171466 | |||
| RP‑171466 | New WI: LTE Advanced inter-band CA Rel-15 for 5DL/1UL | Nokia | WID new | Approval | No |
No
| reserved | No | RP‑170935 | |||
| RP‑171127 | New WID proposal: LTE Advanced inter-band CA Rel-15 for 2DL/2UL | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑170946 | New WID: LTE Advanced inter-band CA for xDL/2UL with x=3,4,5 in Rel-15 | LG Electronics Inc. | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171121 | Motivation for new work item on high power UE for LTE band 42 (power class 2) | Huawei, HiSilicon | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171120 | New work item proposal: high power UE for LTE band 42 (power class 2) | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171219 | Motivation High Power UE in Band 38 | VODAFONE Group Plc | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171220 | New WI proposal: High Power UE for LTE Band 38 | VODAFONE Group Plc | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171047 | New work item proposal: High Power UE for LTE Band 40 (power class 2) | Reliance Jio | WID new | discussion | Yes |
No
| available | No | ||||
| RP‑171123 | Motivation for new work item on new LTE band for 3.3-3.4 GHz for Africa | Huawei, HiSilicon | discussion | Discussion | Yes |
No
| available | No | ||||
| RP‑171122 | New WI proposal: new LTE band for 3.3-3.4 GHz for Africa | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171131 | New work item proposal: Introduction of new band support for 4Rx antenna ports for LTE for Rel-15 | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171132 | New WID Proposal: Addition of band 28 and 40 to LTE MTC Cat.0 | Huawei, HiSilicon | WID new | Approval | Yes |
No
| available | No | ||||
| 10.2 | Open REL-13 LTE SIs | |||||||||||
| 10.2.1 | Study on multi-node testing for LAA [FS_LTE_LAA_multinode_test] | RP‑170877 | LS to related to PD & ED issues (IEEE_802_LMSC_LS170322; to: RAN, RAN1, RAN4; cc: -; contact: Chairman IEEE 802 LMSC) | IEEE 802 LMSC | LS in | Yes |
YesRAN1 answered this LSin in RP-170894
conclusion: Qualcomm drafted an additional LS answer from RAN in RP-171029
| noted | No | |||
| RP‑170894 | Response to IEEE_802_LMSC_LS170322 = RP-170877 related to PD and ED issues (R1-1709855; to: IEEE 802 LMSC, RAN; cc: -; contact: Qualcomm) | RAN1 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑171029 | Draft Response LS to IEEE_802_LMSC_LS170322 = RP-170877 related to PD and ED issues (to: IEEE 802 LMSC; cc: RAN1, RAN4; contact: Qualcomm) | Qualcomm Incorporated | LS out | Approval | Yes |
YesMCC: is this an addition to RP-170894 ?
Qualcomm: there was one question that RAN1 left to RAN to answer it and this is a proposal how to answer it;
Broadcom: we should discuss status of the SI first before we decide to send this LS
RAN chair: is the rest agreeable? seems so
conclusion: we will see outcome of SI discussion on RAN4 testing before we approve RP-171455
| revised | No | RP‑171455 | |||
| RP‑171455 | Draft Response LS to IEEE_802_LMSC_LS170322 = RP-170877 related to PD and ED issues (to: IEEE 802 LMSC; cc: RAN1, RAN4; contact: Qualcomm) | Qualcomm Incorporated | LS out | Approval | No |
No
| reserved | No | RP‑171029 | |||
| RP‑170878 | LS on IEEE 802 response to 3GPP RAN1 LS dated November 2016 (R1-1613770) (IEEE_802_LMSC_LS170322b; to: RAN, RAN1; cc: IEEE 802.11 WG, IEEE 802.19 Coexistence WG; contact: Chairman IEEE 802 LMSC) | IEEE 802 LMSC | LS in | Yes |
YesRAN1 answered this LSin in RP-170893
| noted | No | |||||
| RP‑170893 | Response LS to IEEE_802_LMSC_LS170322b = RP-170878 regarding LAA (R1-1709854; to: IEEE 802 LMSC, RAN; cc: -; contact: Qualcomm) | RAN1 | LS in | Yes |
Yesis actually a joint response from RAN1 and RAN4
conclusion: no LS answer from RAN
| noted | No | |||||
| RP‑171077 | Status report for SI: Study on Multi-node testing for LAA; rapporteur: Huawei | RAN4 | WI status report | Yes |
YesMCC: status report with values in [ ] is unacceptable, revision required
Huawei: after offline discussion we concluded that the SI is 100% complete
NEC: all open issues solved?
Huawei: yes
| revised | No | RP‑171456 | ||||
| RP‑171456 | Status report for SI: Study on Multi-node testing for LAA; rapporteur: Huawei | RAN4 | WI status report | - | No |
Yesconclusion: approved: 100%, June 17; SI completed
Broadcom: what is the plan regarding moving this topic to a normative state?
CableLabs: would support to have normative WI on this
RAN chair: was this discussed in RAN4?
Ericsson: there is no such an agreement in RAN4
RAN chair: so we close the SI and is no normative WI available so far
Qualcomm: this is contribution driven and not up to RAN4 to
CableLabs: we should also capture this in the IEEE LS that no normative WI is planned
Qualcomm: we should say that there is no normative WI now
RAN chair: can be done in the LSout RP-171455
| noted | No | RP‑171077 | |||
| RP‑171143 | Summary of email discussions on remaining issues for multi-node tests | Ericsson, Qualcomm, Huawei, HiSilicon, Nokia, Alcatel-Lucent, Shanghai Bell, Verizon, AT&T, US Cellular, Vodafone, Skyworks, T-Mobile USA, MediaTek, Broadcom, Blackberry, CableLabs, Brocade, Blackberry, Orange, Hewlett Packard Enterprise | discussion | Information | Yes |
YesMCC: is this documentation of what happened already in RAN4 or are there remaining open issues?
Ericsson: is a documentation of what happened after the RAN4 meeting
| noted | No | ||||
| RP‑171146 | TR 36.789 v1.0.0 on Study on multi-node testing for license-assisted access (LAA); for approval | Ericsson, Qualcomm, Huawei, HiSilicon, Nokia, Alcatel-Lucent, Shanghai Bell, Verizon, AT&T, US Cellular, Vodafone, Skyworks, T-Mobile USA, MediaTek, Broadcom, Blackberry, CableLabs, Brocade, Blackberry, Orange, Hewlett Packard Enterprise | draft TR | Approval | Yes |
YesMCC: Is the SI completed or not?
Ericsson: all work is done
Blackberry: is there something missing?
RAN chair: check offlline
Ericsson: nothing was missing, this was checked with Blackberry
| approved | No | ||||
| 10.3 | Open REL-14 LTE WIs (not spectrum related) | |||||||||||
| 10.3.1 | Perf. part: Enhanced LAA for LTE [LTE_eLAA-Perf] | RP‑171040 | Status Report for enhanced LAA performance; rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yes
| revised | No | RP‑171401 | ||
| RP‑171401 | Status Report for enhanced LAA performance; rapporteur: Ericsson | RAN4 | WI status report | - | Yes |
YesMCC: late submission, target date change
conclusion: approved: 50%, Sep.17
| noted | No | RP‑171040 | |||
| RP‑171255 | RAN4 CRs to Perf. part: Enhanced LAA for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.2 | Perf. part: Support for V2V services based on LTE sidelink [LTE_SL_V2V-Perf] | RP‑170984 | Status report of WI Perf. part: Support for V2V services based on LTE sidelink; rapporteur: LG Electronics | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 100%, June 17; Perf. part completed
| noted | No | |||
| RP‑171256 | RAN4 CRs to Perf. part: Support for V2V services based on LTE sidelink | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.3 | Perf. Part: Performance enhancements for high speed scenario in LTE [LTE_high_speed-Perf] | RP‑171038 | Status report for WI: Perf. part: Performance enhancements for high speed scenario in LTE; rapporteur: NTT DOCOMO | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 100%, June 17; Perf. part completed
| noted | No | |||
| RP‑171257 | RAN4 CRs to Perf. Part: Performance enhancements for high speed scenario in LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171039 | Revised WID for Performance enhancements for high speed scenario in LTE | NTT DOCOMO, INC., Huawei, HiSilicon | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.4 | Core part: Radiated perf. req. for the verification of multi-antenna reception of UEs in LTE [LTE_MIMO_OTA-Core] | RP‑170895 | LS on MIMO OTA progress (R4-1705922; to: GCF CAG, GCF PAG, CTIA MOSG, CCSA; cc: RAN5, RAN; contact: Intel) | RAN4 | LS in | Yes |
Yesconclusion: no LS answer
| noted | No | |||
| RP‑171018 | Status report of WI Core part: Radiated performance requirements for the verification of multi-antenna reception of UEs in LTE; rapporteur: Intel | RAN4 | WI status report | Yes |
YesMCC: This Core part had already one exception and achieved so far just 50% in 15 months, are we confident that the other 50% can be achieved in 3 months?
RAN chair: continuation is planned into RAN4 time budget for the future?
conclusion: approved: Core: 50%, Sep.17
| noted | No | |||||
| RP‑171258 | RAN4 CRs to Radiated performance requirements for the verification of multi-antenna reception of UEs in LTE | RAN4 | CR pack | Approval | Yes |
YesMCC: CR set should only be approved if WI can really be completed by Sep.17 as if we move it to the next REL i Sep.17 all these CRs would have to be deimplemented
RAN chair: so you better complete the WI by Sep.17
| approved | No | ||||
| RP‑171019 | Exception for WI Core part: Radiated performance requirements for the verification of multi-antenna reception of UEs in LTE | Intel Corporation | WI exception request | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.5 | Perf. part: Enhancements on FD-MIMO for LTE [LTE_eFDMIMO-Perf] | RP‑170989 | Status report for WI: Perf. part: Enhancement on Full-Dimension (FD) MIMO for LTE; rapporteur:Samsung | RAN4 | WI status report | Yes |
Yes
| revised | No | RP‑171431 | ||
| RP‑171431 | Status report for WI: Perf. part: Enhancement on Full-Dimension (FD) MIMO for LTE; rapporteur:Samsung | RAN4 | WI status report | - | Yes |
YesMCC: late submission
conclusion: approved: Perf.: 50%, Sep.17
| noted | No | RP‑170989 | |||
| 10.3.6 | Perf. part: Further mobility enhancements in LTE [LTE_eMob-Perf] | RP‑171041 | Status report of WI Perf. part: Further mobility enhancements in LTE; rapporteur: ZTE | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 100%, June 17; Perf. part is completed
| noted | No | |||
| RP‑171259 | RAN4 CRs to Perf. part: Further mobility enhancements in LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.7 | Perf. part: Uplink Capacity Enhancements for LTE [LTE_UL_CAP_enh-Perf] | RP‑170966 | Status report for WI Perf. part: Uplink Capacity Enhancements for LTE; rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yes
| revised | No | RP‑171457 | ||
| RP‑171457 | Status report for WI Perf. part: Uplink Capacity Enhancements for LTE; rapporteur: Ericsson | RAN4 | WI status report | - | Yes |
NoMCC: late submission
conclusion: approved: Perf.: 75%, Sep.17 ?
| available | No | RP‑170966 | |||
| RP‑171260 | RAN4 CRs to Perf. part: Uplink Capacity Enhancements for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.8 | eMBMS enhancements for LTE [MBMS_LTE_enh2] | RP‑170978 | Status report for WI eMBMS enhancements for LTE; rapporteur: Ericsson | RAN1 | WI status report | Yes |
NoMCC: only use integer values for the % complete please; this WI had already one exception promising completion by RAN #76; target date change;
conclusion: approved: Core: 97%, Sep.17; Perf.: 70%, Sep.17 ?
| available | No | |||
| RP‑171195 | Maintenance of Rel-14 eMBMS enhancements for LTE | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171221 | RAN2 CRs to eMBMS enhancements for LTE | RAN2 | CR pack | Approval | Yes |
YesMCC: CR set should only be approved if a 2nd exception is granted and the WI can be completed by Sep.17
| approved | No | ||||
| RP‑171261 | RAN4 CRs to eMBMS enhancements for LTE | RAN4 | CR pack | Approval | Yes |
YesMCC: CR set should only be approved if a 2nd exception is granted and the WI can be completed by Sep.17
| approved | No | ||||
| RP‑171169 | FeMBMS/unicast-mixed carrier flag in measurement object | Qualcomm Incorporated | CR | Approval | Yes |
YesMCC: this CR was not seen in RAN2, it is related to a decision made in RAN4 (related to way forward R4-1706012) which requires an ASN.1 change; this CR is also relevant for exception request RP-170979
Nokia: was this discussed in RAN WGs?
Qualcomm: was a company CR
| approved | No | ||||
| RP‑171191 | Inter-site synchronization requirements for eMBMS | Huawei, HiSilicon | discussion | Discussion | Yes |
YesProposal: RAN should task RAN4 to specify the inter-cell synchronization requirement for 200us CP length for eMBMS enhancement under either the WID of eMBMS enhancement or under TEI.
Ericsson: we had a discussion in the past to do this under TEI, MBMS does not need this requirement;
RAN chair: TEI is usually not a clean approach, we should use it for things that affect 1 WG in 1 quarter;
Huawei: we are fine either way
Qualcomm: preference for TEI, feature works without it
conclusion: work will be done under TEI14 with the understanding that this happens in the next quarter
| noted | No | ||||
| RP‑170979 | WI exception request for Core part: eMBMS enhancement for LTE | Ericsson | WI exception request | Approval | Yes |
YesHuawei: we have a related Tdoc in RP-171191
| approved | No | ||||
| 10.3.9 | Perf. part: SRS switching between LTE component carriers [LTE_SRS_switch-Perf] | RP‑171074 | Status report for WI Perf. Part: SRS (sounding reference signal) switching between LTE component carriers, rapporteur: Huawei | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 100%, June 17; Perf. part WI is completed
| noted | No | |||
| RP‑171262 | RAN4 CRs to Perf. part: SRS switching between LTE component carriers | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.10 | Perf. part: Downlink Multiuser Superposition Transmission for LTE [LTE_MUST-Perf] | RP‑171178 | Status Report for WI: Perf. part: Downlink Multiuser Superposition Transmission for LTE; rapporteur: MediaTek | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 100%, June 17; Perf. part WI is completed
| noted | No | |||
| RP‑171263 | RAN4 CRs to Perf. part: Downlink Multiuser Superposition Transmission for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.11 | LTE Measurement Gap Enhancement [LTE_meas_gap_enh] | RP‑171024 | Status report of WI: Measurement gap enhancement for LTE; rapporteur: Intel | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171222 | RAN2 CRs to LTE Measurement Gap Enhancement | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171264 | RAN4 CRs to LTE Measurement Gap Enhancement | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171330 | WI summary for WI Core part: LTE Measurement Gap Enhancement | Intel | WI summary | Yes |
Yes
| noted | No | |||||
| 10.3.12 | Perf. part: LTE-based V2X Services [LTE_V2X-Perf] | RP‑170985 | Status report of WI Perf. part: LTE-based V2X Services; rapporteur: LG Electronics | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 75%, Sep.17
| noted | No | |||
| RP‑171265 | RAN4 CRs to Perf. part: LTE-based V2X Services | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.13 | Further enhanced MTC for LTE [LTE_feMTC] | RP‑171175 | Status report of WI Further enhanced MTC for LTE; rapporteur: Ericsson | RAN1 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 35%, Dec.17; Core part WI completed
| noted | No | |||
| RP‑171204 | Maintenance of Rel-14 FeMTC | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171223 | RAN2 CRs to Further enhanced MTC for LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171266 | RAN4 CRs to Further enhanced MTC for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171177 | Summary for WI Further enhanced MTC for LTE | Ericsson LM | WI summary | Yes |
Yes
| revised | No | RP‑171441 | ||||
| RP‑171441 | Summary for WI Further enhanced MTC for LTE | Ericsson LM | WI summary | - | Yes |
Yes
| noted | No | RP‑171177 | |||
| 10.3.14 | Enhancements of NB-IoT [NB_IOTenh-Core] | RP‑171059 | Status report for WI: Enhancements of NB-IoT; rapporteur: Huawei | RAN1 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 50%, Dec.17; Core part WI is completed
| noted | No | |||
| RP‑171205 | Maintenance of Rel-14 NB-IoT enhancements for LTE | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171224 | RAN2 CRs to Enhancements of NB-IoT | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171323 | Enhancements of NB-IoT | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171267 | RAN4 CRs to Enhancements of NB-IoT | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171218 | On the UL power control of NPRACH in NB-IoT | Ericsson India Private Limited | discussion | Decision | Yes |
YesProposal: RAN1 is tasked to present a solution to the identified issues at RAN#77 in the scope of NB-IoT Release 14.
Ericsson: related to ongoing RAN1 email discussion, we should look at it for REL-14 and not REL-13
Huawei: (Wed of RAN #76) RAN1 chair allowed for another day of email discussion
Samsung: supports Ericsson
MCC: would this be a cat.F or cat.B CR?
Ericsson: cat.F
RAN chair: if there is a CR we can see it in Sep.17
| noted | No | ||||
| RP‑171060 | Revision of WI: Enhancements of NB-IoT | Huawei, HiSilicon | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171061 | Work Item completion summary for enhancements of NB-IoT | Huawei, HiSilicon | WI summary | Yes |
Yes
| noted | No | |||||
| 10.3.15 | Perf. part: 4 RX antenna ports with CA for LTE DL [LTE_4Rx_AP_DL_CA-Perf] | RP‑170957 | Status Report of WI: Perf. part 4 receiver (RX) antenna ports with Carrier Aggregation (CA) for LTE downlink (DL); rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 90%, Sep.17
| noted | No | |||
| RP‑171268 | RAN4 CRs to Perf. part: 4 receiver (RX) antenna ports with Carrier Aggregation (CA) for LTE downlink (DL) | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.3.16 | Requirements for a new UE cat. with single receiver based on Cat.1 for LTE [LTE_UE_cat_1RX] | RP‑171148 | Status report for WI Requirements for a new UE category with single receiver based on Category 1 for LTE; rapporteur: Qualcomm | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core & Perf. part WI are completed
| noted | No | |||
| RP‑171269 | RAN4 CRs to Requirements for a new UE category with single receiver based on Category 1 for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171149 | Revision of WID: Requirements for a new UE category with single receiver based on Category 1 for LTE | Qualcomm Incorporated | WID revised | Approval | Yes |
Yesrelated to RP-171048
| approved | No | ||||
| RP‑171048 | Addition of Band 28 UE category 1bis into TS 36.101 | Telstra Corporation Limited | CR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171317 | WI summary for WI Core part: Requirements for a new UE category with single receiver based on Category 1 for LTE | Qualcomm | WI summary | Yes |
Yes
| noted | No | |||||
| 10.3.17 | Perf. part: Enh. CRS and SU-MIMO Interf. Mitigation Perf. Requirements for LTE [LTE_eCRSIM_eSUMIMO-Perf] | RP‑171013 | Status report of WI: Perf. part: Enhanced CRS and SU-MIMO Interference Mitigation Performance Requirements for LTE; rapporteur: Intel | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 85%, Sep.17
| noted | No | |||
| RP‑171144 | TR 36.747 v1.0.0 on Enhanced CRS and 4Rx SU-MIMO Interference Mitigation Performance Requirements for LTE; for information | Huawei | draft TR | Information | Yes |
Yes
| noted | No | ||||
| 10.4 | Open REL-14 LTE & UMTS WIs (not spectrum related) | |||||||||||
| 10.4.1 | Perf. part: Further Indoor Positioning Enh. for UTRA and LTE [UTRA_LTE_iPos_enh2-Perf] | RP‑170948 | Status report of WI Perf. part: Further Indoor Positioning enhancements for UTRA and LTE; rapporteur: Huawei, NextNav | RAN4 | WI status report | Yes |
Yesconclusion: approved: Perf.: 100%, June 17; Perf. part is completed
| noted | No | |||
| RP‑171270 | RAN4 CRs to Perf. part: Further Indoor Positioning Enhancements for UTRA and LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.4.2 | Core part: LTE UE TRP & TRS and UTRA Hand Phantom related UE TRP and TRS Req. [LTE_UTRA_TRP_TRS-Core] | RP‑171007 | Status Report of WI: Core part: LTE UE TRP and TRS and UTRA Hand Phantom related UE TRP and TRS Requirements; rapporteur: Telecom Italia | RAN4 | WI status report | Yes |
YesMCC: this WI had already one exception promising completion by RAN #76; WI achieved 85% in 54 months (4,5 years), are we confident that the remaining 15% can be achieved in 3 months?
Telecom Italia: in the worst case that the work is not completed in Sep.17 the missing parts could split off so we would not need big deimplementation efforts
conclusion: approved: Core: 85%, Sep.17
| noted | No | |||
| RP‑171010 | Revised WID: LTE UE TRP and TRS and UTRA Hand Phantom related UE TRP and TRS Requirements | TELECOM ITALIA S.p.A. | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171009 | Exception sheet of WI: Core part: LTE UE TRP and TRS and UTRA Hand Phantom related UE TRP and TRS Requirements | TELECOM ITALIA S.p.A. | WI exception request | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171271 | RAN4 CRs to Core part: LTE UE TRP & TRS and UTRA Hand Phantom related UE TRP and TRS Requirements | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.5 | Open REL-14 LTE WIs (spectrum related) | |||||||||||
| 10.5.1 | LTE Advanced intra-band CA for xDL/yUL including contiguous and non-contiguous spectrum [LTE_CA_R14_intra] | RP‑170958 | Status report of WI LTE Advanced intra-band CA for xDL/yUL including contiguous and non-contiguous spectrum; rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171272 | RAN4 CRs to LTE Advanced intra-band CA for xDL/yUL including contiguous and non-contiguous spectrum | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170964 | TR 36.714-00-00 v1.0.0 on LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for x Down Link (DL) / y Up Link (UL) including contiguous and non-contiguous spectrum; for approval | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170960 | Revised WID: Rel-14 Basket WI for LTE Advanced Intra-band CA including contiguous and non-contiguous spectrum | Ericsson | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.2 | LTE Advanced inter-band CA Rel-14 for 2DL/1UL [LTE_CA_R14_2DL1UL] | RP‑171027 | Status Report LTE Advanced inter-band CA Rel-14 for 2DL/1UL; rapporteur: Qualcomm | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171273 | RAN4 CRs to LTE Advanced inter-band CA Rel-14 for 2DL/1UL | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171028 | TR 36 714-02-01 v1.0.0 LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for 2 Down Link (DL) / 1 Up Link (UL); for approval | Qualcomm Incorporated | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171025 | Revision of WID:LTE Advanced inter-band CA Rel-14 for 2DL1UL | Qualcomm Incorporated | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.3 | LTE Advanced inter-band CA Rel-14 for 3DL/1UL [LTE_CA_R14_3DL1UL] | RP‑171081 | Status report for WI: LTE Advanced inter-band CA Rel-14 for 3DL/1UL; rapporteur: Huawei | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171274 | RAN4 CRs to LTE Advanced inter-band CA Rel-14 for 3DL/1UL | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170987 | TR 36.714-03-01 v1.0.0: LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for 3 Down Link (DL) / 1 Up Link (UL); for approval | Huawei, HiSilicon | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171082 | Revised WID: LTE Advanced inter-band CA Rel-14 for 3DL/1UL | Huawei, HiSilicon | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.4 | LTE Advanced inter-band CA Rel-14 for 4DL/1UL [LTE_CA_R14_4DL1UL] | RP‑170959 | Status report of WI LTE_CA_R14_4DL1UL; rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171275 | RAN4 CRs to LTE Advanced inter-band CA Rel-14 for 4DL/1UL | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170965 | TR 36.714-04-01 v1.0.0 on LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for 4 Down Link (DL) / 1 Up Link (UL); for approval | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170961 | Revised WID: Rel-14 Basket WI for LTE Advanced Inter-band CA Rel-14 for 4DL/1UL | Ericsson | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.5 | LTE Advanced inter-band CA Rel-14 for 5DL/1UL [LTE_CA_R14_5DL1UL] | RP‑170934 | Status Report of WI LTE Advanced inter-band CA Rel-14 for 5DL/1UL; Rapporteur: Nokia | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171276 | RAN4 CRs to LTE Advanced inter-band CA Rel-14 for 5DL/1UL | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170932 | TR 36.714-05-01 v1.0.0 on TE Advanced intra-band Carrier Aggregation (CA) Rel-14 for 5 Down Link (DL) / 1 Up Link (UL); for approval | Nokia | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170933 | Revised WI: LTE Advanced inter-band CA Rel-14 for 5DL/1UL | Nokia | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.6 | LTE Advanced inter-band CA Rel-14 for 2DL/2UL [LTE_CA_R14_2DL2UL] | RP‑171083 | Status report for WI: LTE Advanced inter-band CA Rel-14 for 2DL/2UL; rapporteur: Huawei | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171277 | RAN4 CRs to LTE Advanced inter-band CA Rel-14 for 2DL/2UL | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170951 | TR 36.714-02-02 v1.0.0:LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for 2 Down Link (DL) / 2 Up Link (UL); for approval | Huawei Technologies France | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171084 | Revised WID: LTE Advanced inter-band CA Rel-14 for 2DL/2UL | Huawei, HiSilicon | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.7 | LTE Advanced inter-band CA Rel-14 for xDL/2UL with x=3,4,5 [LTE_CA_R14_xDL2UL] | RP‑170943 | Status report for WI LTE Advanced inter-band CA Rel-14 for xDL/2UL with x=3,4,5; rapporteur: LG Electronics | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171278 | RAN4 CRs to LTE Advanced inter-band CA Rel-14 for xDL/2UL | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170941 | TR 36.714-00-02 v1.0.0 on LTE Advanced inter-band CA for xDL/2UL with x=3,4,5 in rel-14 | LG Electronics Inc. | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170942 | Revised WID: LTE Advanced inter-band CA Rel-14 for xDL/2UL with x=3,4,5 | LG Electronics Inc. | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.5.8 | New band support for Rel-14 NB-IOT [NB_IOT_R14_bands] | RP‑170969 | Status report for WI New band support for Rel-14 NB-IOT; rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑171279 | RAN4 CRs to New band support for Rel-14 Narrowband Internet of Things (NB-IOT) | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171051 | Adding Band 4 to NB-IoT Bands | T-Mobile USA Inc. | discussion | Approval | Yes |
YesProposal: RAN approves adding Band 4 to NB-IoT bands to support UE category NB1 starting from Release-13 and NB2 starting from Release-14.
MCC: This is a Rel-14 WI that had a 3 months exception to complete by RAN #76. Neither WID RP-170139 nor exception request sheet RP-170141 talks about band 4.
T-Mobile: wants to have it in REL-14
Ericsson: is anyway REL-independent and can be added in a new REL-15 basket
Nokia: there is already a basket WI for REL-15 in RP-171131 which includes band 4
MCC: it turned out later that RP-171131 is on a different basket WI but a REL-15 basket for bands to support UE cat.NB1 can be created in Sep.17 and the bands would be then supported in a REL independent way starting from REL-13
conclusion: band 4 will be added in REL-15 basket in Sep.17 in a release independent way starting from REL-13
| noted | No | ||||
| RP‑170970 | Summary for WI new band support for Rel-14 NB-IoT | Ericsson | WI summary | Yes |
Yes
| noted | No | |||||
| 10.5.9 | Core part: Introduction of new band support for 4Rx antenna ports for LTE [LTE_4Rx_AP_DL_bands-Core] | RP‑171080 | Status report for WI: Core part: Introduction of new band support for 4Rx antenna ports; rapporteur: Huawei | RAN4 | WI status report | Yes |
YesMCC: REL-14 WI LTE_4Rx_AP_DL_bands-Core had a 3 months exception to complete by RAN #76, no CRs are provided to RAN #76?
Huawei: there were 2 CRs to this WI:
R4-1702301 in RP-170574 approved by RAN #75 and
R4-1706077 in RP-171304 (see AI 14.4.6) using just the WI code LTE_4Rx_AP_DL-Core although it should have used LTE_4Rx_AP_DL-Core, LTE_4Rx_AP_DL_bands-Core because it merged CRs of 2 WIs in one CR
conclusion: approved: 100%, June 17; Core part WI is completed
| noted | No | |||
| 10.6 | Small Technical Enhancements and Improvements for REL-14 [TEI14] | RP‑170888 | LS on EUTRAN sharing enhancement (R2-1706003; to: SA2, RAN3, RAN, SA; cc: -; contact: Ericsson) | RAN2 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||
| RP‑170899 | Reply LS to R2-1706003 = RP-170888 on EUTRAN sharing enhancement (S2-173701; to: RAN2, RAN, SA, SA5; cc: RAN3; contact: Ericsson) | SA2 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170902 | Reply to LS R2-1706003 = RP-170888 on EUTRAN sharing enhancement (R3-172026; to: RAN2, RAN; cc: SA2, SA; contact: Ericsson) | RAN3 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑171251 | EUTRAN Sharing enhancement | Ericsson | discussion | Decision | Yes |
YesProposal 1 : Approve the RAN2 CRs
| noted | No | ||||
| RP‑171246 | RAN2 CRs EUTRAN Sharing enhancement | RAN2 | CR pack | Approval | Yes |
NoMCC: Acc. to RAN2 chairman's report: E-UTRAN sharing enhancement:
Enables PLMNs sharing a RAN to configure independent values of TAC and Cell-ID in broadcast system information;
RAN2 technically endorsed 36.300 and 36.331 CRs under TEI14 (provided to RAN in CR pack RP-171246);
RAN2 also sent LS to SA2, RAN3 and RAN requesting that SA2/RAN3 provide feedback on the CRs;
RAN is requested to make final decision on the CRs considering any feedback received from SA2 or RAN3;
RAN2 chair: any impact in RAN3 or SA2 was the open issue, acc. to the LSs there are no impacts so we could go ahead and approve the CRs
Nokia: this is a late addition to REL-14, it seems some changes are needed, at least we have no confirmation from SA so we should postpone the CRs
conclusion: will postpone the CRs to joint RAN-SA session on Wed evening
| available | No | ||||
| RP‑171210 | Corrections for Rel-14 (36.212/36213) | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171225 | RAN2 CRs to Small Technical Enhanements and Improvements for REL-14 | RAN2 | CR pack | Approval | Yes |
YesMCC: company CR in RP-171425 in order to revise R2-1706185 of RP-171225
conclusion: partially approved, i.e. all CRs of RP-171225 are approved except R2-1706185 which is revised in RP-171425
| partially approved | No | ||||
| RP‑171425 | Miscellaneous general corrections and clarifications resulting from ASN.1 review | Ericsson | CR | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171324 | Small Technical Enhancements and Improvements for REL-14 | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171280 | RAN4 CRs to Small Technical Enhanements and Improvements for REL-14 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7 | Closed REL-14 LTE WIs (not spectrum related) | |||||||||||
| 10.7.1 | Core part: Support for V2V services based on LTE sidelink [LTE_SL_V2V-Core] | RP‑171199 | Maintenance of Rel-14 Support for V2V services based on LTE sidelink | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171226 | RAN2 CRs to Support for V2V services based on LTE sidelink | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171281 | RAN4 CRs to Core part: Support for V2V services based on LTE sidelink | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.2 | Core part: LTE-based V2X Services [LTE_V2X-Core] | RP‑171203 | Maintenance of Rel-14 V2X | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171227 | RAN2 CRs to LTE-based V2X Services | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171407 | RAN2 CRs to LTE-based V2X Services (part 2) | RAN2 | CR pack | Approval | Yes |
YesMCC: late submission; 8 RAN1, 9 RAN2 and 14 RAN4 CRs? How complete was this WI when it was declared 100% complete at RAN #75?
| approved | No | ||||
| RP‑171282 | RAN4 CRs to Core part: LTE-based V2X Services | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.3 | Core part: L2 latency reduction techniques for LTE [LTE_LATRED_L2-Core] | RP‑171228 | RAN2 CRs to L2 latency reduction techniques for LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.7.4 | Core part: Perf. enhancements for high speed scenario in LTE [LTE_high_speed-Core] | RP‑171229 | RAN2 CRs to Performance enhancements for high speed scenario in LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171283 | RAN4 CRs to Core part: Performance enhancements for high speed scenario in LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.5 | Core part: SRS switching between LTE component carriers [LTE_SRS_switch-Core] | RP‑171200 | Maintenance of Rel-14 SRS (sounding reference signal) switching between LTE component carriers | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171230 | RAN2 CRs to SRS (sounding reference signal) switching between LTE component carriers | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171284 | RAN4 CRs to Core part: SRS switching between LTE component carriers | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.6 | Core part: DL Multiuser Superposition Transmission for LTE [LTE_MUST-Core] | |||||||||||
| 10.7.7 | Core part: 4Rx antenna ports with CA for LTE DL [LTE_4Rx_AP_DL_CA-Core] | |||||||||||
| 10.7.8 | Core part: Enhanced LAA for LTE [LTE_eLAA-Core] | RP‑171201 | Maintenance of Rel-14 Enhanced LAA | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171231 | RAN2 CRs to Enhanced LAA for LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171285 | RAN4 CRs to Core part: Enhanced LAA for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.9 | Core part: Enhancements on FD-MIMO for LTE [LTE_eFDMIMO-Core] | RP‑171194 | Maintenance of Rel-14 eFD-MIMO | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171232 | RAN2 CRs to Enhancements on Full-Dimension (FD) MIMO for LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.10 | Core part: Further mobility enhancements in LTE [LTE_eMob-Core] | RP‑171233 | RAN2 CRs to Further mobility enhancements in LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171286 | RAN4 CRs to Core part: Further mobility enhancements in LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.11 | Core part: UL Capacity Enhancements for LTE [LTE_UL_CAP_enh-Core] | RP‑171192 | Maintenance of Rel-14 Uplink Capacity Enhancements for LTE | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171234 | RAN2 CRs to Uplink Capacity Enhancements for LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171287 | RAN4 CRs to Core part: Uplink Capacity Enhancements for LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.12 | Core part: Voice and Video Enhancement for LTE [LTE_VoLTE_ViLTE_enh-Core] | RP‑170881 | Reply LS to C3-171255 = RP-170038 on RAN-Assisted Codec Adaptation (R2-1703968; to: CT3, SA4; cc: RAN3, RAN, SA2; contact: Ericsson) | RAN2 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||
| RP‑170885 | Reply LS to R2-1703968 = RP-170881 and C3-171255 = RP-170038 on RAN-Assisted Codec Adaptation (S4-170430; to: RAN2, CT3; cc: RAN3, SA2, RAN; contact: Intel) | SA4 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑171206 | Maintenance of Rel-14 Voice and Video enhancement for LTE | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171235 | RAN2 CRs to Voice and Video Enhancement for LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.13 | Core part: Flexible eNB-ID and Cell-ID in E-UTRAN [LTE_FNBID-Core] | RP‑171325 | Flexible eNB-ID and Cell-ID in E-UTRAN - Core | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.7.14 | Core part: Enh. LTE-WLAN Aggregation (LWA) [LTE_WLAN_aggr-Core] | RP‑170883 | Response LS to SP-160457 = RP-161378 on Progress on Security for LWIP (R3-171272; to: SA, SA3; cc: RAN; contact: Nokia) | RAN3 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||
| RP‑171236 | RAN2 CRs to Enhanced LTE-WLAN Aggregation (LWA) | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 10.7.15 | Core part: Enh. LTE WLAN Radio Level Integration with IPsec Tunnel [LTE_WLAN_eLWIP-Core] | RP‑171326 | Enhanced LTE WLAN Radio Level Integration with IPsec Tunnel (eLWIP) - Core Part | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.8 | Closed REL-14 LTE & UMTS WIs (not spectrum related) | |||||||||||
| 10.8.1 | Multi-Band BS testing with three or more bands [MB_BS_test_3B] | |||||||||||
| 10.8.2 | Core part: Further Indoor Positioning Enh. for UTRA and LTE [UTRA_LTE_iPos_enh2-Core] | RP‑171288 | RAN4 CRs to Core part: Further Indoor Positioning Enhancements for UTRA and LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.8.3 | Core part: Enh. of Dedicated Core Networks for UMTS and LTE [eDECOR-UTRA_LTE-Core] | RP‑171237 | RAN2 CRs to Enhancements of Dedicated Core (DECOR) Networks for UMTS and LTE | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.9 | Closed REL-14 LTE WIs (spectrum related) | |||||||||||
| 10.9.1 | LTE 2.6 GHz FDD Suppl. DL band (2570-2620 MHz) and LTE CA (2DL/1UL) with Band 3 for region 1 [LTE_FDD_2600_CA_B3] | |||||||||||
| 10.9.2 | AWS-3/4 Band for LTE [LTE_AWS_3_4] | |||||||||||
| 10.9.3 | Citizens Broadband Radio Service 3.5GHz band for LTE in the US [LTE_TDD_3550_CBRS_US] | RP‑171289 | RAN4 CRs to Citizens Broadband Radio Service (CBRS) 3.5GHz band for LTE in the United States | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.9.4 | LTE Band 41 UE power class 2 operation [LTE_B41_UE_PC2-Core] | RP‑171290 | RAN4 CRs to LTE Band 41 UE power class 2 operation | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.9.5 | LTE Advanced inter-band CA Rel-14 for 3DL/3UL [LTE_CA_R14_3DL3UL] | |||||||||||
| 10.9.6 | Core part: Addition of 1.4 and 3 MHz Channel BW to E-UTRA operating band 65 for CGC operations in Region 1 [LTE_1980_2170_REG1_addBWs-Core] | |||||||||||
| 10.9.7 | Core part: Addition of band 25 and 26 to LTE MTC cat.0 [LC_MTC_LTE_cat0_B25_B26-Core] | RP‑171291 | RAN4 CRs to Addition of band 25 and 26 to LTE MTC cat.0 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 10.9.8 | Core part: Addition of bands 25 and 40 to LTE MTC cat.1 [LTE_MTCe2_L1_cat1_B25_B40-Core] | |||||||||||
| 10.10 | Closed REL-14 LTE SIs | |||||||||||
| 10.11 | Open REL-15 LTE WIs (not spectrum related) | |||||||||||
| 10.11.1 | Shortened TTI and processing time for LTE [LTE_sTTIandPT] | RP‑170971 | Status report for WI Shortened TTI and processing time for LTE; rapporteur: Ericsson | RAN1 | WI status report | Yes |
YesMCC: Perf. part % complete missing
| revised | No | RP‑171429 | ||
| RP‑171444 | On completion of the sTTIandPT Work Item | Ericsson | discussion | discussion | Yes |
Noproposals:
- Scope of sTTIandPT WI remains unchanged
- Extend the work item completion to RAN #78 (Dec)
- Transfer some of the TUs from HRLLC WI to sTTIandPT WI during Q3 and Q4
Huawei: RAN2 TU: agrees that more work needs to be done than what was indicated before but 6 times is a bit too much, suggests 1TU for Aug. and adding more later;
LG: worried how HRLLC work can be completed
Huawei: status report was submitted with target date Sep. and now it is shifted to Dec. although scope was unchanged; suggests to keep Sep. target and check the situation in Sep.17;
Ericsson: we took comments from Vodafone into account;
Nokia: suggests to make a realistic assessment how long the work will need, to complete by Sep. is not realistic;
Interdigital: agrees with Nokia and RAN2 can only work when RAN1 has completed their work
Mediatek: supports Ericsson, Nokia and Interdigital
RAN chair: it seems shifting to Dec.17 is more realistic (as this is also of interest for SA)
Huawei: is this now more RAN2 led? as RAN1 has no relation to SA
conclusion: no scope change of sTTIandPT agreed, Core part completion target is moved to Dec.17, TU split can be discussed further and will be seen in RP-171429
| available | No | ||||
| RP‑171429 | Status report for WI Shortened TTI and processing time for LTE; rapporteur: Ericsson | RAN1 | WI status report | - | No |
NoMCC: late submission; % complete of Perf. part?
conclusion: approved: Core: 65%, Sep.17; Perf.: ?%, March 18
| reserved | No | RP‑170971 | |||
| RP‑171468 | Revised WID: Shortened TTI and processing time for LTE | Ericsson | WID revised | Approval | No |
No
| reserved | No | ||||
| 10.11.2 | Core part: Signalling reduction to enable light connection for LTE [LTE_LIGHT_CON-Core] | RP‑171070 | Status report for WI: Core part: Signalling reduction to enable light connection for LTE, rapporteur: Huawei | RAN2 | WI status report | Yes |
YesMCC: this WI has no Perf. part; why does the status report have a % complete and target date for Perf. part?; target date change;
| revised | No | RP‑171469 | ||
| RP‑171469 | Status report for WI: Core part: Signalling reduction to enable light connection for LTE, rapporteur: Huawei | RAN2 | WI status report | - | No |
Noconclusion: approved: Core: 79%, March 18, Perf.: 0%, March 18?
| reserved | No | RP‑171070 | |||
| RP‑171133 | Scope of LTE connectivity to 5G-CN | Huawei, HiSilicon | discussion | Discussion | No |
YesHuawei: does not belong under light connection and is withdrawn
| withdrawn | Yes | ||||
| RP‑171436 | Revised WID: Signalling reduction to enable light connection for LTE | Huawei | WID revised | Approval | Yes |
YesWID revision creates a Perf. part WI
Nokia: target dates out-of date
Vodafone: SA stopped the work on this?
Mediatek: why Dec.17?
Huawei: has chosen first available date
Mediatek: change it to June 18, RRC inactive in NR is supposed to complete in June 18 and this is here the LTE related work;
Ericsson: we need to wait for SA2 outcome first anyway
Huawei: if it does not matter, we can take Dec.17 for the moment
LG: no TU allocation for RAN2
conclusion: completion March 18 is agreed for Core part and Perf. part
feature is on hold until Sep.17 (SA2 needs to progress sufficiently)
| revised | No | RP‑171459 | |||
| RP‑171459 | Revised WID: Signalling reduction to enable light connection for LTE | Huawei | WID revised | Approval | No |
No
| reserved | No | RP‑171436 | |||
| 10.11.3 | Further enh. to CoMP Operation for LTE [New WI: feCOMP_LTE] | RP‑171030 | Status report of WI: Further enhancements to Coordinated Multi-Point (CoMP) Operation for LTE; rapporteur: Intel Corporation | RAN1 | WI status report | Yes |
NoMCC: next time please remove confusing SI target date; target date change;
conclusion: approved: Core: 70%, March 18; Perf.: 0%, March 18 ?
| available | No | |||
| RP‑171031 | Revision of WI: Further enhancements to Coordinated Multi-Point (CoMP) Operation for LTE | Intel Corporation, ZTE | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.11.4 | Highly Reliable Low Latency Communication for LTE [New WI: LTE_HRLLC] | RP‑170972 | Status report for WI Ultra Reliable Low Latency Communication for LTE; rapporteur: Ericsson | RAN1 | WI status report | Yes |
Yes
| revised | No | RP‑171442 | ||
| RP‑171442 | Status report for WI Ultra Reliable Low Latency Communication for LTE; rapporteur: Ericsson | RAN1 | WI status report | - | No |
NoMCC: late submission;
conclusion: approved: Core: 0%, June 18; Perf.: 0%, Dec.18 ?
| reserved | No | RP‑170972 | |||
| 10.11.5 | V2X phase 2 based on LTE [New WI: LTE_eV2X] | RP‑170876 | Reply LS to NGMN_LS_170122 = RP-170049 to NGMN V2X Task-Force (SP-170278; to: NGMN V2X Task Force; cc: RAN, SA1, SA2, SA3; contact: LG Electronics) | SA | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||
| RP‑170887 | Reply LS to S1-171461 = RP-170042 on eV2X Normative Requirements (5GAA_LS_S-170064; to: SA1; cc: SA, RAN, 5GAA WG1; contact: Intel) | 5GAA WG4 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑170896 | Reply LS to RP-170841 on the support of Unicast and Groupcast transmission over PC5 for eV2X (S2-173610; to: RAN; cc: SA, SA1, SA3, RAN2; contact: LG Electronics) | SA2 | LS in | Yes |
Yesconclusion: no LS answer from RAN
| noted | No | |||||
| RP‑171068 | Status report for WI: V2X phase 2 based on LTE; rapporteur: Huawei | RAN1 | WI status report | Yes |
Yesconclusion: approved: Core: 15%, June 18; Perf.: 0%, Dec.18
| noted | No | |||||
| RP‑171069 | Revision of WI: V2X phase 2 based on LTE | Huawei, HiSilicon | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.11.6 | UE Positioning Accuracy Enh. for LTE [New WI: LCS_LTE_acc_enh] | RP‑171008 | Status report of WI UE Positioning Accuracy Enhancements for LTE; rapporteur: Nokia | RAN2 | WI status report | Yes |
YesEricsson: UE-based positioning was added to the WID without online discussion. As discussed on the RAN reflector, there seems very little support for that objective and no progress in RAN2. We would like to discuss a down-scoping of that aspect.
Qualcomm: we consider it useful for NB-IOT
Sequans: also considers it useful
RAN chair: so we keep it for now?
Ericsson: then have it with 2nd priority as long as there is no operator support
Nokia: would be ok with this; completion date Dec.17 and TUs only shown until June; so suggests to revise the WID
conclusion: approved: Core: 10%, June 18; Perf.: 0%, June 18
| noted | No | |||
| RP‑171460 | Revised WID on UE Positioning Accuracy Enhancements for LTE | Nokia | WID revised | discussion | No |
Yesapproved unseen
| approved | No | ||||
| 10.11.7 | Enh. for high capacity stationary wireless link and introduction of 1024 QAM for LTE DL [New WI: LTE_1024QAM_DL] | RP‑171066 | Status report for WI: Enhancements for high capacity stationary wireless link and introduction of 1024 QAM for LTE DL; rapporteur: Huawei | RAN1 | WI status report | Yes |
YesMCC: target date change;
conclusion: approved: Core: 20%, March 18; Perf.: 0%, June 18
| noted | No | |||
| RP‑171036 | Revised WID: Enhancements for high capacity stationary wireless link and introduction of 1024 QAM for LTE | Qualcomm Incorporated, Huawei | WID revised | Approval | No |
Yes
| withdrawn | Yes | ||||
| RP‑171067 | Revision of WI: Enhancements for high capacity stationary wireless link and introduction of 1024 QAM for LTE DL | Huawei, Qualcomm | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.11.8 | Enh. to LTE operation in unlicensed spectrum [New WI: LTE_unlic] | RP‑171152 | Status report for WI: Enhancements to LTE operation in unlicensed spectrum; rapporteur: Nokia | RAN1 | WI status report | Yes |
YesMCC: target date change (+9 months); Perf. part % complete not provided;
conclusion: approved: Core: 15%, June 18; Perf.: 0%, Dec.18
| noted | No | |||
| 10.11.9 | Core part: Further video enhancements for LTE [New WI: LTE_ViLTE_enh2-Core] | RP‑170999 | Status report of WI: Core part: Further video enhancements for LTE; rapporteur: CMCC | RAN2 | WI status report | Yes |
Yes
| revised | No | RP‑171400 | ||
| RP‑171400 | Status report of WI: Core part: Further video enhancements for LTE; rapporteur: CMCC | RAN2 | WI status report | - | Yes |
YesMCC: late submission
conclusion: approved: 15%, Dec.17
| noted | No | RP‑170999 | |||
| RP‑170998 | Revision of WI: Further video enhancements for LTE | CMCC | WID revised | Approval | Yes |
Yes
| revised | No | RP‑171392 | |||
| RP‑171392 | Revision of WI: Further video enhancements for LTE | CMCC | WID revised | Approval | Yes |
Yes
| approved | No | RP‑170998 | |||
| 10.11.10 | Core part: QoE Measurement Collection for streaming services in E-UTRAN [New WI: LTE_QMC_Streaming-Core] | RP‑170954 | Status report of WI Core part: Quality of Experience (QoE) Measurement Collection for streaming services in E-UTRAN; rapporteur: China Unicom | RAN2 | WI status report | Yes |
Yesconclusion: approved: Core: 25%, Dec.17
| noted | No | |||
| RP‑170956 | Revision of WI Quality of Experience (QoE) Measurement Collection for streaming services in E-UTRAN | China Unicom | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.11.11 | Enhancing LTE CA Utilization [New WI: LTE_euCA] | RP‑171187 | Status report for WI: Enhancing LTE CA utilization; rapporteur: Nokia | RAN2 | WI status report | Yes |
Yesconclusion: approved: Core: 0%, June 18; Perf.: 0%, Dec.18
| noted | No | |||
| 10.11.12 | Core part: LTE connectivity to 5G-CN [New WI: LTE_5GCN_connect-Core] | RP‑171072 | Status report for WI: Core part: LTE connectivity to 5G-CN; rapporteur: Huawei | RAN2 | WI status report | Yes |
Yesconclusion: approved: Core: 5%, June 18
| noted | No | |||
| RP‑171073 | Revision of WID: LTE connectivity to 5G-CN | Huawei, HiSilicon | WID revised | Approval | Yes |
YesMediatek: study is not completed, suggestion in SA is to put it on hold, we have not done any solution so far;
Ericsson: SA2 study is for EPC and not 5G-CN
RAN chair: does anyone disagree that this work needs to be added?
Nokia: RRC-inactive would be ok but what is LTE-inactive?
Samsung: we need to avoid to make the same mistake we did on light connection, SA work is not yet over, we would start parallel work, our preference would be not to rush;
| revised | No | RP‑171432 | |||
| RP‑171432 | Revision of WID: LTE connectivity to 5G-CN | Huawei, HiSilicon | WID revised | Approval | No |
No
| reserved | No | RP‑171073 | |||
| 10.11.13 | WIs approved with working agreement at RAN #75 | RP‑171188 | Considerations for the Release-15 NB-IoT and eMTC | KT Corp. | discussion | Discussion | Yes |
YesRAN chair: item for early consideration
| not treated | No | ||
| RP‑171045 | Considerations on evolution of NB-IoT/eMTC | ZTE Corporation | discussion | Yes |
Yesproposal:
- In Rel-15, enhancement should focus on be enhancement of specific aspects of individual technology
- Support of both eMTC and NB-IoT mode and switching between two air interface should be based UE implementation.
- No specification optimization for dual mode operation in Rel-15
- For any future release, enhancement shall consider convergence to the final evolution path
- General enhancement should be adopted for both technologies with minor variations
- Differentiations targeting specific use case of each technology should be kept
RAN chair: item for early consideration
CMCC: optimization for dual mode operation in future REL?
Deutsche Telekom: last bullet of the proposals is unclear and not appreciated
| noted | No | |||||
| RP‑171182 | NB-IoT and eMTC considerations | Deutsche Telekom AG | discussion | Yes |
YesRAN chair: item for early consideration
| revised | No | RP‑171420 | ||||
| RP‑171420 | NB-IoT and eMTC considerations | Deutsche Telekom AG | discussion | - | Yes |
Yesproposals:
- It is out of scope of the Rel-15 eMTC WID that the maximum supported UE channel bandwidth of a Rel-15 eMTC UE can be less than 6 PRB in UL and DL.
- It is out of scope of the Rel-15 NB-IoT WID that the maximum supported UE channel bandwidth of a Rel-15 NB-IoT UE can be more than 1 PRB in UL and DL.
- No new UE category for Rel-15 eMTC and NB-IoT is introduced.
- Reflect the above in revisions of the Rel-15 eMTC and NB-IoT WIDs.
Deutsche Telekom: additional supporters were added, contents is identical
Mediatek: supports the Tdoc
Qualcomm: needs some modifications, 2nd proposal was only raised by Huawei
RAN chair: first proposal can be revised, 2nd proposal not needed, 3rd bullet should be softened
RAN chair: seems we need to revise the WIDs for REL-15 eMTC and NB-IOT
Qualcomm: would have a problem to approve the way forward in RP-171420
conclusion: offline discussions to revise the WIDs in RP-171427 and RP-171428
| noted | No | RP‑171182 | |||
| RP‑171467 | Way forward on NB-IoT and eMTC evolution and UE capability | Huawei | discussion | discussion | No |
No
| reserved | No | ||||
| 10.11.13.1 | Even further enhanced MTC for LTE [New WI: LTE_eMTC4] | RP‑171180 | Status report of WI Even further enhanced MTC for LTE; rapporteur: Ericsson | RAN1 | WI status report | Yes |
Yes
| revised | No | RP‑171412 | ||
| RP‑171412 | Status report of WI Even further enhanced MTC for LTE; rapporteur: Ericsson | RAN1 | WI status report | - | Yes |
YesMCC: late submission;
RAQN4 vice-chair (Huawei): TU change was granted
conclusion: approved: Core: 10%, June 18; Perf.: 0%, Dec.18
| noted | No | RP‑171180 | |||
| RP‑171190 | OTDOA enhancements for Rel-15 eMTC | Huawei, HiSilicon | discussion | Discussion | Yes |
Yes
| revised | No | RP‑171424 | |||
| RP‑171424 | OTDOA enhancements for Rel-15 eMTC | Huawei, HiSilicon | discussion | Discussion | Yes |
YesProposal: Add the following objective to the Rel-15 eFeMTC WID:
• Specify PRS frequency hopping to support coherent detection of PRS over multiple narrowbands/widebands without an increase in the transmitted bandwidth of PRS, including associated RAN4 requirements. [RAN1, RAN4, RAN2]
Intel: sceptic that this can work
Ericsson: too early to introduce this, would need to be checked
Qualcomm: same view
conclusion: can come back on this later if more support
| noted | No | RP‑171190 | |||
| RP‑171183 | Revised WI: Even further enhanced MTC for LTE | Ericsson LM | WID revised | Approval | Yes |
YesRAN chair: after treatment of RP-171420 we need to revise the note in the WID
conclusion: obsolete bullet should be removed and note to be revised
| revised | No | RP‑171427 | |||
| RP‑171427 | Revised WI: Even further enhanced MTC for LTE | Ericsson LM | WID revised | Approval | No |
No
| reserved | No | RP‑171183 | |||
| 10.11.13.2 | Further NB-IoT enhancements [New WI: NB_IOTenh2] | RP‑171062 | Status report for WI: Further NB-IoT enhancements; rapporteur: Huawei | RAN1 | WI status report | Yes |
Yesconclusion: approved: Core: 8%, June 18; Perf.: 0%, Dec.18
| noted | No | |||
| RP‑171005 | Motivation for accelerating NB-IoT work in 2017 | VEOLIA | discussion | Decision | Yes |
YesRAN chair: item for early consideration
| revised | No | RP‑171396 | |||
| RP‑171396 | Motivation for accelerating NB-IoT work in 2017 | VEOLIA | discussion | Decision | Yes |
YesRAN chair: item for early consideration
| revised | No | RP‑171435 | RP‑171005 | ||
| RP‑171435 | Motivation for accelerating NB-IoT work in 2017 | VEOLIA | discussion | Decision | Yes |
YesProposal 1 - To prioritize R15 power consumption enhancements to be
completed by Dec 17 for early implementations
Deutsche Telekom: confirms that power consumption can be improved, supports that work is done in 3GPP and accelerated, signalling may affect ASN.1 so we can only freeze features that have no ASN.1 impact;
Vodafone: supports that Veolia brought up this topic and that power consumption need to be further improved, we should check first which functionalities need to be prioritized before we look into ASN.1 freeze aspects;
Ericsson: there are quite many enhancements that are proposed, there are certainly things that could be done more easily than others, so we could prioritize them in RAN2;
Huawei: we should check at RAN #76 what we could do to satisfies Veolia's requirements;
RAN 1 chair: having a step-by-step approach is possible?
Veolia: the market needs actually already a tighter time schedule so our dates here are relaxed already
Sprint: we have a serious problem with proposal 1 to prioritize this over other topics
RAN chair: having a list of points that can be prioritized together with corresponding required TUs would be useful
Vodafone: most of the points are already part of the REL-15 WI and we should prioritize within the WI and not prioritize over other WIs/SIs
conclusion: offline discussion to come up with a prioritization in RP-171440 (rapporteur: Huawei)
Proposal 2 - Add NB-IoT RAN 1 / RAN 2 Ad Hoc Meetings in 2017
Nokia: prefers to better schedule the work and solve it during the normal meetings
Sprint: supports this
NEC: rather extending a normal meeting than having another trip to Sophia Antipolis
LG: not supporting to have the ad hoc
Huawei: supports to have an ad hoc as it may help progressing the prioritization
AT&T: we are afraid that if we create a precedence case every WI will ask for an ad hoc for their topic
Nokia: supports AT&T, we saw in the past that too many meetings are actually doing the opposite of acceleration
RAN2 chair: we had no discussion of this topic in RAN2 and it looks a bit odd to schedule an ad hoc before we have treated the topic at least once
Veolia: we need to find a way to complete the work by Dec.17
Telstra: reminds that NB-IOT is having worse power consumption figures compared to non-3GPP technology and we lose market share if we do not address this problem
Sequans: does not support to have the ad hoc as for some companies there are not different people who attend the different meetings
RAN chair: suggests to proceed as planned until Aug. and review the TUs for LTE in Sep.17
Huawei: may be more easier to have an ad hoc in Oct./Nov.
conclusion: no extra ad hoc considered so far, we will revisit the situation at RAN #77 in Sep.17 and concentrate first on the prioritization (see RP-171440)
Proposal 3 - Increase Time Units per meeting RAN1/RAN2
RAN2 chair: this is not a possible option after the planning we did last time
RAN1 chair: RAN1 is already fully loaded in the 3rd quarter
conclusion: proposal 3 is not agreed
| noted | No | RP‑171396 | |||
| RP‑171440 | Way forward on NB-IOT prioritization | Huawei | discussion | discussion | No |
No
| reserved | No | ||||
| RP‑171006 | Motivation for further enhancements in NB-IoT to address Smart Water Metering | VEOLIA | discussion | Decision | Yes |
YesRAN chair: item for early consideration
| revised | No | RP‑171423 | |||
| RP‑171423 | Motivation for further enhancements in NB-IoT to address Smart Water Metering | VEOLIA | discussion | Decision | Yes |
YesProposal 1: To add in WI “NB_IOTenh2” the Support of NB-IoT as multi-hop relay
[RAN2, RAN1]
Ericsson: there are other options like REL-10 relay or small cell with a cable?
Veolia: adding further equipment is costly
Deutsche Telekom: intention is to add further functionality to the existing WI and not a new WI, correct:?
RAN chair: has the same understanding
Qualcomm: existing relay solution may be more complex, what is proposed could be an interesting longer term study;
Intel: sees some overlap with the wearables topic?
Telstra: a study is definitely needed and whatever the solution is it must be a low cost solution
LG: there is also some overlap with the MTC WI
RAN chair: we will not work on this in the 3 months, we do not need to take a decision now but we can use the next the 3 months to find a solution how to handle this;
Huawei: what about an LS to RAN2 tasking them to check
Ericsson: SI is over, WI not having TUs and we will only treat LSs so wearables is not a proper place for this; also sees a fundamental difference to wearables
| noted | No | RP‑171006 | |||
| RP‑171063 | Revision of WI: Further NB-IoT enhancements; rapporteur: Huawei | Huawei, HiSilicon | WID revised | Approval | Yes |
YesNokia: some more explanation needed; what would you use the counting for?
RAN chair: can discuss the counting further offline
| revised | No | RP‑171428 | |||
| RP‑171428 | Revision of WI: Further NB-IoT enhancements; rapporteur: Huawei | Huawei, HiSilicon | WID revised | Approval | No |
No
| reserved | No | RP‑171063 | |||
| 10.12 | Open REL-15 LTE WIs (spectrum related) | |||||||||||
| 10.12.1 | 450MHz E-UTRA FDD Band for LTE PPDR and PMR/PAMR in Europe [LTE450_Europe_PPDR] | RP‑170911 | Status report of WI 450MHz E-UTRA FDD Band for LTE PPDR and PMR/PAMR in Europe; rapporteur: Airbus DS SLC | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 75%, Sep.17; Perf.: 50%, Sep.17
| noted | No | |||
| RP‑170912 | TR 36.748 v1.0.0 for 450MHz E-UTRA FDD Band for LTE PPDR and PMR/PAMR in Europe | Airbus DS SLC | draft TR | Information | Yes |
Yes
| noted | No | ||||
| 10.12.2 | Core part: E-UTRA 700MHz in Europe for Broadband-PPDR-Core [LTE700_Europe_PPDR-Core] | RP‑170910 | Status report of WI Core part: E-UTRA 700MHz in Europe for Broadband-PPDR; rapporteur: Airbus DS SLC | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core:80%, Sep.17
| noted | No | |||
| 10.12.3 | FDD operating band in the L-band for LTE [LTE_FDD_L_Band] | RP‑171095 | Status Report of WI: FDD operating band in the L-band for LTE; rapporteur: NTT DOCOMO, INC. | RAN4 | WI status report | Yes |
Yes
| revised | No | RP‑171402 | ||
| RP‑171402 | Status Report of WI: FDD operating band in the L-band for LTE; rapporteur: NTT DOCOMO, INC. | RAN4 | WI status report | - | Yes |
YesMCC: late submission, target date change
conclusion: approved: Core: 99%, Sep.17; Perf.: 99%, Sep.17
| noted | No | RP‑171095 | |||
| RP‑171096 | Revised Work Item on an FDD operating band in the L-band for LTE | NTT DOCOMO, INC. | WID revised | Approval | Yes |
Yes
| revised | No | RP‑171403 | RP‑162536 | ||
| RP‑171403 | Revised Work Item on an FDD operating band in the L-band for LTE | NTT DOCOMO, INC. | WID revised | Approval | Yes |
Yes
| approved | No | RP‑171096 | |||
| RP‑171097 | TR 36.751 v1.0.0 on FDD operating band in the L-band for LTE; for information | NTT DOCOMO, INC. | draft TR | Information | Yes |
Yes
| noted | No | ||||
| 10.12.4 | TDD operating band in the L-band for LTE [LTE_TDD_L_Band] | RP‑171079 | Status report for WI: TDD operating band in the L-band for LTE; rapporteur: Huawei | RAN4 | WI status report | Yes |
YesMCC: target date change;
conclusion: approved: Core: 70%, Sep.17; Perf.: 0%, Sep.17
| noted | No | |||
| 10.12.5 | LTE Extended 1.5 GHz SDL band (1427 – 1518 MHz) and LTE CA (2DL/1UL) with Band 20 [LTE_SDL_1500ext] | RP‑171151 | Status Report of WI: LTE Extended 1.5 GHz SDL band (1427 – 1518 MHz) and LTE Carrier Aggregation (2DL/1UL) with Band 20; rapporteur: Qualcomm Incorporated | RAN4 | WI status report | Yes |
YesMCC: late submission, target date change;
conclusion: approved: Core: 50%, Sep.17; Perf.: 0%, Sep.17
| noted | No | |||
| RP‑171389 | Revised WID: LTE Extended 1.5 GHz SDL band (1427 - 1518 MHz) and LTE CA (2DL/1UL) with Band 20 | Orange | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.12.6 | Core part: Add UE Power Class 2 to band 41 intra-band contiguous LTE CA [LTE_CA_C_B41_PC2-Core] | RP‑171003 | Status_Report for WI Core part: Add UE Power Class 2 to band 41 intra-band contiguous LTE Carrier Aggregation; rapporteur: Sprint | RAN4 | WI status report | Yes |
YesMCC: target date change;
Sprint: also rapporteur changed
conclusion: approved: Core: 50%, Dec.17
| noted | No | |||
| RP‑171004 | Revision of WI – Add UE Power Class 2 to band 41 intra-band contiguous LTE carrier aggregation | SPRINT Corporation | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.12.7 | Core part: Addition of Power Class 1 UE to bands B3/B20/B28 for LTE [LTE_HPUE_B3_B20_B28-Core] | RP‑171078 | Status report for WI: Addition of power class 1 UE to B3/B20/B28 for LTE; rapporteur: Huawei | RAN4 | WI status report | Yes |
YesMCC: status report has no Perf. part information and is claiming 100% complete although we are not approving any REL-15 CRs at RAN #76 and no CRs are submitted to RAN #76
NTT DOCOMO: is not 100% complete
| revised | No | RP‑171461 | ||
| RP‑171461 | Status report for WI: Addition of power class 1 UE to B3/B20/B28 for LTE; rapporteur: Huawei | RAN4 | WI status report | - | No |
Noconclusion: approved: Core: 99%, Sep.17; Perf.: 0%, Dec.17?
| reserved | No | RP‑171078 | |||
| 10.12.8 | 450 MHz Band for LTE in Region 3 [New WI: LTE450_Reg3] | RP‑170953 | Status report for WI 450 MHz Band for LTE in Region 3; rapporteur: China Unicom | RAN4 | WI status report | Yes |
YesMCC: Perf. part target is missing, target date shift (by 1 year);
| revised | No | RP‑171462 | ||
| RP‑171462 | Status report for WI 450 MHz Band for LTE in Region 3; rapporteur: China Unicom | RAN4 | WI status report | - | Yes |
Yesconclusion: approved: Core: 30%, Dec.17; Perf.: 0%, Dec.17
| noted | No | RP‑170953 | |||
| RP‑170952 | Revised WID on 450 MHz Band for LTE in Region 3 | China Unicom | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.12.9 | US 600 MHz Band for LTE [New WI: LTE600_US] | RP‑171141 | Status Report on WI US 600 MHz Band for LTE; rapporteur: Ericsson | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 95%, Sep.17; Perf.: 95%, Sep.17
| noted | No | |||
| RP‑171142 | Revised WID on US 600 MHz Band for LTE | T-Mobile US, Ericsson | WID revised | Approval | Yes |
Yes
| approved | No | RP‑170740 | |||
| 10.12.10 | Core part: V2X new band combinations for LTE [New WI: LTE_V2X_CA_bands-Core] | RP‑170945 | Status report of WI on V2X new band combinations; rapporteur: LG Electronics | RAN4 | WI status report | Yes |
YesMCC: target date change (note: this is a basket WI going until the end of the REL);
conclusion: approved: Core: 20%, June 18
| noted | No | |||
| RP‑170944 | Revised WID on V2X new band combinations in rel-15 | LG Electronics Inc. | WID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.12.11 | LAA/eLAA for the CBRS 3.5GHz band in the US [New WI: LTE_3550_CBRS_US_LAA] | RP‑171331 | Status report for WI LAA/eLAA for the CBRS 3.5GHz band in the United States; rapporteur: AT&T | RAN4 | WI status report | Yes |
YesMCC: late request;
conclusion: approved: Core: 50%, Dec.17; Perf.: 50%, Dec.17
| noted | No | |||
| 10.13 | Open REL-15 LTE & UMTS WIs (not spectrum related) | |||||||||||
| 10.13.1 | Enh. of BS RF and EMC requirements for AAS [AASenh_BS_LTE_UTRA] | RP‑171075 | Status report for WI: Enhancements of Base Station (BS) RF and EMC requirements for Active Antenna System (AAS), rapporteur: Huawei | RAN4 | WI status report | Yes |
Yesconclusion: approved: Core: 60%, Dec.17; Perf.: 20%, June 18
| noted | No | |||
| RP‑171076 | Revision of WID: Enhancements of Base Station (BS) RF and EMC requirements for Active Antenna System (AAS) | Huawei, HiSilicon | WID revised | Approval | Yes |
YesHuawei: Nokia requested additional changes
Ericsson: would like to approve the TR only with Perf. part
| revised | No | RP‑171463 | |||
| RP‑171463 | Revision of WID: Enhancements of Base Station (BS) RF and EMC requirements for Active Antenna System (AAS) | Huawei, HiSilicon | WID revised | Approval | No |
No
| reserved | No | RP‑171076 | |||
| 10.14 | Open REL-15 LTE SIs (not spectrum related) | |||||||||||
| 10.14.1 | Study on further enh. to LTE D2D, UE to network relays for IoT and wearables [FS_feD2D_IoT_relay_wearable] | RP‑171071 | Status report for SI: Study on further enhancements LTE Device to Device, UE to Network Relays for IoT and Wearables; rapporteur: Huawei | RAN2 | WI status report | Yes |
Yesconclusion: approved: 80%, Sep.17
| noted | No | |||
| RP‑171312 | TR 36.746 v1.0.0 on Study on further enhancements to LTE Device to Device (D2D), User Equipment (UE) to network relays for Internet of Things (IoT) and wearables; for information | LG Electronics | draft TR | Information | Yes |
Yes
| noted | No | ||||
| 10.14.2 | Study on interference cancellation receiver for LTE BS [FS_LTE_IC_BS] | RP‑170938 | Status report for SI: Study on interference cancellation receiver for LTE BS, rapporteur: China Telecom | RAN4 | WI status report | Yes |
Yesconclusion: approved: 100%, June 17; SI is completed
| noted | No | |||
| RP‑170937 | TR 36.766 v2.0.0 for Study on interference cancellation receiver for LTE BS; for approval | China Telecom, Huawei | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| 10.14.3 | Study on UL data compression in LTE [FS_LTE_UDC] | RP‑171107 | Status Report for SI: Study on UL data compression in LTE; rapporteur: CATT | RAN2 | WI status report | Yes |
Yes
| revised | No | RP‑171388 | ||
| RP‑171388 | Status Report for SI: Study on UL data compression in LTE; rapporteur: CATT | RAN2 | WI status report | Yes |
YesMCC: late request;
original proposal: 100%, June 17
conclusion: after discussion of RP-171108 the SI will continue
| revised | No | RP‑171426 | RP‑171107 | |||
| RP‑171426 | Status Report for SI: Study on UL data compression in LTE; rapporteur: CATT | RAN2 | WI status report | - | Yes |
YesRAN2 chair: no TU change so RAN2 would not have no TUs, 1TU was expected
| revised | No | RP‑171464 | RP‑171388 | ||
| RP‑171464 | Status Report for SI: Study on UL data compression in LTE; rapporteur: CATT | RAN2 | WI status report | - | No |
Yesconclusion: approved: 90%, Sep.17
| noted | No | RP‑171426 | |||
| RP‑171139 | TR 36.754 v1.0.0 on Study on UL data compression for E-UTRA; for approval | CATT | draft TR | Approval | Yes |
YesMediatek: we should approve the TR here as it is more than 80% complete and then have CRs to change it
RAN2 chair: is not what we do usually but ok
| approved | No | ||||
| RP‑171140 | TR 36.754 v1.0.0 on Study on UL data compression for E-UTRA; for approval | CATT | draft TR | Approval | No |
Yes
| withdrawn | Yes | ||||
| 10.14.4 | Study on SON for eCoMP for LTE [FS_LTE_SON_eCOMP] | RP‑171011 | Status report of SI Study on SON for eCoMP for LTE; rapporteur: Nokia | RAN3 | WI status report | Yes |
Yesconclusion: approved:
| noted | No | |||
| RP‑171012 | TR 36.742 v2.0.0 on Study on SON for eCoMP for LTE; for approval | Nokia, Alcatel-Lucent Shanghai Bell | draft TR | Approval | Yes |
Yes
| approved | No | ||||
| 10.14.5 | Study on enhanced LTE Support for Aerial Vehicles [New SI: FS_LTE_Aerial] | RP‑171053 | Status Report of SI Study on Enhanced LTE Support for Aerial Vehicles; rapporteur: NTT DOCOMO, INC. | RAN2 | WI status report | Yes |
Yesconclusion: approved:
| noted | No | |||
| RP‑171050 | Revision of SID on Enhanced Support for Aerial Vehicles | NTT DOCOMO, INC. | SID revised | Approval | Yes |
Yes
| approved | No | ||||
| 10.14.6 | Study on Architecture Evolution for E-UTRAN [New SI: FS_LTE_arch_evo] | RP‑171332 | Status report for SI Study on Architecture Evolution for E-UTRAN; rapporteur: China Unicom | RAN3 | WI status report | Yes |
YesMCC: late request
conclusion: approved: 0%, Dec.17
| noted | No | |||
| 10.15 | LTE UE capabilities/FGIs/IoT bits/UE categories | RP‑171037 | Introduction of a new DL category | Qualcomm Incorporated | discussion | Decision | Yes |
Yesproposals:
- The DL peak data rates of the new UE category should be a multiple of 200Mbps
- The following new DL category should be added : Cat x: 2000Mbps DL
- The 2000Mbps DL category should be defined for Rel-14.
- The pairing with UL categories is TBD.
Mediatek: legacy carrier or green field spectrum?
RAN chair: suggests to discuss and decide in Sep.17
Qualcomm: as there is some operator support why not deciding already now
Qualcomm: providing band combinations was never a prerequisite for a category, we can rely on interested operators to bring them up
conclusion: we will come back to this in Sep.17
| noted | No | ||
| RP‑171247 | RAN2 CRs to Introduction of a new UL UE category for 300Mbps with 64QAM | RAN2 | CR pack | Approval | Yes |
YesMCC: Acc. to RAN2 chair: new UL category for 300Mbps with UL 64 QAM; proposed and postponed at RAN#75 to enable RAN2 review of CRs;
RAN2 technically endorsed 36.331 and 36.306 CRs from Rel-14 (provided to RAN in CR pack RP-171247); RAN2 asks RAN to make final decision
Mediatek: wondering whether there is any RAN4 band combination already for this? It would require 4CC CA in UL;
Intel: it is already supported in core specs and it does not require to have a band combination already, there is no band combination for this but this may come later
| approved | No | ||||
| 11 | UMTS | |||||||||||
| 11.1 | New WI/SI proposals for UMTS | RP‑171213 | Motivation for WI: Simplified HS-SCCH for UMTS | Ericsson | discussion | Decision | Yes |
No
| available | No | ||
| RP‑171214 | New WI proposal: Simplified HS-SCCH for UMTS | Ericsson | WID new | Approval | Yes |
Yes
| revised | No | RP‑171443 | |||
| RP‑171443 | New WI proposal: Simplified HS-SCCH for UMTS | Ericsson | WID new | Approval | Yes |
No
| available | No | RP‑171214 | |||
| 11.2 | Small Technical Enhancements and Improvements for REL-14 [TEI14] | RP‑171238 | RAN2 CRs to Small Technical Enhancements and Improvements for REL-14 | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 11.3 | Closed REL-14 UMTS WIs | |||||||||||
| 11.3.1 | Core part: RRC optimization for UMTS [UTRA_RRCopt-Core] | |||||||||||
| 11.3.2 | Core part: DTX/DRX enhancements in CELL_FACH [FACH_DTXDRX-Core] | |||||||||||
| 11.3.3 | Core part: Multi-Carrier Enhancements for UMTS [UTRA_MCe-Core] | RP‑171327 | Multi-Carrier Enhancements for UMTS - Core part | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 11.3.4 | Core part: QoE Measurement Collection for streaming services in UTRAN [UMTS_QMC_Streaming-Core] | RP‑171239 | RAN2 CRs to Quality of Experience (QoE) Measurement Collection for streaming services in UTRAN | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171328 | Quality of Experience (QoE) Measurement Collection for streaming services in UTRAN | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 11.4 | Closed REL-14 UMTS SIs | |||||||||||
| 11.5 | UMTS UE capabilities/IoT bits/UE categories | |||||||||||
| 11.6 | Open REL-15 UMTS WIs | |||||||||||
| 11.6.1 | Core part: DL interf. mitigation for UMTS [New WI: UTRA_DL_IM-Core] | RP‑171134 | Status report of WI: Core part: DL interference mitigation for UMTS; rapporteur: Qualcomm | RAN2 | WI status report | Yes |
NoQualcomm: Highlight the RAN2 agreement to standardize the feature starting from Rel-14, for RAN approval. (RAN2 Rel-14 CRs package is in RP-171240);
MCC: shifting this WI back from REL-15 into frozen REL-14 would be an exception (because it is for UMTS and there is consensus among the affected WG(s) and because we are freezing ASN.1 at this meeting and impacts were taken into account);
conclusion: approved: 100%, June 17; Core part is shifted back from REL-15 to REL-14 and is completed ?
| available | No | |||
| RP‑171240 | RAN2 CRs to DL interference mitigation for UMTS | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171136 | Revision of WI: Core part: DL interference mitigation for UMTS | Qualcomm Incorporated | WID revised | Approval | Yes |
No
| available | No | ||||
| RP‑171135 | Summary of WI: DL interference mitigation for UMTS | Qualcomm Incorporated | WI summary | Yes |
No
| available | No | |||||
| 11.7 | Open REL-15 UMTS SIs | |||||||||||
| 11.7.1 | Study on scheduling enhancements with CA for UMTS [New SI: FS_UTRA_CA_sched_enh] | RP‑171064 | Status report for SI: Study on scheduling enhancements with carrier aggregation for UMTS; rapporteur: Huawei | RAN1 | WI status report | Yes |
Yesconclusion: approved: 100%, June 17; SI is completed
| noted | No | |||
| RP‑170990 | TR 25.708 V1.0.0 Study on Scheduling Enhancements with Carrier Aggregation for UMTS; for approval | Huawei | draft TR | Approval | Yes |
No
| available | No | ||||
| RP‑171065 | Revision of SI: Study on scheduling enhancements with carrier aggregation for UMTS | Huawei, HiSilicon | SID revised | Approval | Yes |
No
| available | No | ||||
| 11.7.2 | Study on a simplified HS-SCCH for UMTS [New SI: FS_UTRA_simple_HSSCCH] | RP‑171211 | Status report of SI Study on a simplified HS-SCCH for UMTS; rapporteur: Ericsson | RAN1 | WI status report | Yes |
NoMCC: this SI was exceptionally approved after RAN #76 without target date and without new/affected spec, the TR is brought here for approval but requires a SID update beforehand to allocate a TR number;
conclusion: approved: 100%, June 17; SI is completed ?
| available | No | |||
| RP‑171212 | Revised SI: Study on a simplified HS-SCCH for UMTS | Ericsson | SID revised | Approval | Yes |
No
| available | No | ||||
| RP‑171316 | TR 25.7XX v1.0.0 on Study on a simplified HS-SCCH for UMTS; for approval | Ericsson | draft TR | Approval | No |
NoMCC: The TR must be created via a SID revision in RP-171212 first
| reserved | No | ||||
| 12 | GERAN | |||||||||||
| 12.1 | New WI/SI proposals for GERAN (led by RAN6) | |||||||||||
| 12.2 | Open REL-14 GERAN WIs | |||||||||||
| 12.2.1 | Positioning Enhancements for GERAN [ePOS_GERAN] | RP‑170919 | Status report of WI Positioning Enhancements for GERAN; rapporteur: Ericsson | RAN6 | WI status report | Yes |
Yesconclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed
| noted | No | |||
| RP‑170923 | RAN6 agreed CRs for REL-14 WI: Positioning Enhancements for GERAN (ePOS_GERAN) | RAN6 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171052 | Revised Work Item on Positioning Enhancements for GERAN | Ericsson LM | WID revised | Approval | Yes |
No
| available | No | RP‑161260 | |||
| RP‑170920 | Summary for WI Positioning Enhancements for GERAN | Ericsson LM | WI summary | Yes |
No
| available | No | |||||
| 12.2.2 | Radio Interface Enhancements for Extended Coverage GSM for support of Cellular IoT [CIoT_EC_GSM_radio_enh] | RP‑171320 | Status report for WI Radio Interface Enhancements for Extended Coverage GSM for support of Cellular Internet of Things; rapporteur: Nokia | RAN6 | WI status report | Yes |
NoMCC: late request
conclusion: approved: Core: 100%, June 17; Perf.: 100%, June 17; Core and Perf. part WI are completed ?
| available | No | |||
| RP‑170924 | RAN6 agreed CRs for REL-14 WI: Radio Interface Enhancements for Extended Coverage GSM for support of Cellular Internet of Things (CIoT_EC_GSM_radio_enh) | RAN6 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171321 | WI summary for WI Radio Interface Enhancements for Extended Coverage GSM for support of Cellular Internet of Things | Nokia | WI summary | Yes |
No
| available | No | |||||
| 12.3 | Small Technical Enhancements and Improvements for REL-14 [TEI14] | RP‑170925 | RAN6 agreed CRs for REL-14 WI Small Technical Enhancements and Improvements for REL-14 (TEI14, eDecor) | RAN6 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 12.4 | Closed REL-14 GERAN WIs | |||||||||||
| 12.4.1 | Core part: Dedicated Core Networks for GERAN [DECOR_GERAN-Core] | RP‑170926 | RAN6 agreed CR for the REL-14 WI Dedicated Core Networks for GERAN (DECOR_GERAN-Core) | RAN6 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 12.5 | Closed REL-14 GERAN SIs | |||||||||||
| 13 | New and open RAN5 UE Conformance testing WIs and SIs | |||||||||||
| 13.1 | New WI/SI proposals for UE conformance testing (led by RAN5) | RP‑170931 | New WID on UE Conformance Test Aspects - Addition of 1.4 and 3 MHz Channel Bandwidth to E-UTRA operating band 65 for CGC (Complementary Ground Component) operations in Region 1 | Dish Network | WID new | Approval | Yes |
No
| available | No | ||
| RP‑171057 | New WI Proposal: UE Conformance Test Aspects – EIEI (Evolution to and Interworking with eCall in IMS) | Qualcomm Incorporated | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171058 | New WI Proposal: UE Conformance Test Aspects – Requirements for a new UE category 1bis with single receiver based on category 1 for LTE | Qualcomm Incorporated | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171106 | New WID: UE Conformance Test Aspects- Voice Enhancement for LTE | CATT, CMCC | WID new | Approval | Yes |
Yes
| revised | No | RP‑171385 | |||
| RP‑171385 | New WID: UE Conformance Test Aspects- Voice and Video Enhancement for LTE | CATT, CMCC | WID new | Approval | Yes |
No
| available | No | RP‑171106 | |||
| RP‑171130 | New WI Proposal: UE Conformance Test Aspects –Support for LTE-based V2X Services | Huawei, CATT | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171391 | RAN5 agreed non TTCN CR(s) WI MS Conformance Test Aspects - Enhancements on LTE-based V2X Services (LTE_V2X-UEConTest) | RAN5 | CR pack | Approval | Yes |
NoMCC: A WI for LTE_V2X-UEConTest does not yet exist, it is proposed in RP-171130
| available | No | ||||
| RP‑171155 | New WID on: UE Conformance Test Aspects - Enhancements of Dedicated Core Networks for UTRA and LTE | Ericsson | WID new | Approval | Yes |
No
| available | No | ||||
| RP‑171154 | New WID on: UE Conformance Test Aspects – 5G system with NR and LTE | Ericsson, CMCC | WID new | Approval | Yes |
No
| available | No | ||||
| 13.2 | Open Rel-5 WIs | |||||||||||
| 13.2.1 | UE Conformance Test Aspects – IMS for Converged IP Communications [IMS_CONV_IP_COM-UEConTest] | RP‑171153 | Status report for UE Conformance Test Aspects - IMS for Converged IP Communications; rapporteur: ROHDE & SCHWARZ | RAN5 | WI status report | Yes |
Yesconclusion: approved: 20%, Dec.17
| noted | No | |||
| RP‑171334 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – IMS for Converged IP Communications (IMS_CONV_IP_COM-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.3 | Open Rel-12 WIs | |||||||||||
| 13.3.1 | UE Conf. Test Aspects – LTE D2D Proximity Services [LTE_D2D_Prox-UEConTest] | RP‑171055 | Status report of WI: UE Conformance Test aspects - LTE Device–to-Device Proximity Services; rapporteur: Qualcomm | RAN5 | WI status report | Yes |
Yesconclusion: approved: 100%, June 17; WI is completed
| noted | No | |||
| RP‑171335 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – UE Conformance Test Aspects – LTE Device-to-Device Proximity Services (LTE_D2D_PROX-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.3.2 | UE Conf. Test Aspects - E-UTRA Small cell enh. - Physical layer aspects [LTE_SC_enh_L1-UEConTest] | RP‑171085 | Status report for WI: UE Conformance Test Aspects - E-UTRA small cell enhancements - Physical layer aspects; rapporteur: Huawei | RAN5 | WI status report | Yes |
Yesconclusion: approved: 100%, June 17; WI is completed
| noted | No | |||
| RP‑171336 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - E-UTRA Small cell enhancements - Physical layer aspects (LTE_SC_enh_L1-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.3.3 | UE Conf. Test Aspects - Dual connectivity for LTE [LTE_SC_enh_dualC-UEConTest] | RP‑171157 | Status report for WI UE Conformance Test Aspects - Dual connectivity for LTE; rapporteur: Ericsson | RAN5 | WI status report | Yes |
NoMCC: target date change; RAN #77 is in Sep.17 and not in Aug.17;
conclusion: approved: 93%, Sep.17 ?
| available | No | |||
| RP‑171337 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Dual connectivity for LTE (LTE_SC_enh_dualC-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.3.4 | UE Conf. Test Aspects - Further Enh. to LTE TDD for DL-UL Interf. Management and Traffic Adaptation [LTE_TDD_eIMTA-UEConTest] | RP‑171105 | Status report for WI: UE Conformance Test Aspects - Further Enhancements to LTE TDD for DL-UL Interference Management and Traffic Adaptation; rapporteur: CATT | RAN5 | WI status report | Yes |
YesMCC: WI was at 60% at RAN #75;
conclusion: approved: 60%, Dec.17
| noted | No | |||
| RP‑171338 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Further Enhancements to LTE TDD for DL-UL Interference Management and Traffic Adaptation (LTE_TDD_eIMTA-UEConTest) | RAN5 | CR pack | Approval | No |
Yes
| withdrawn | Yes | ||||
| 13.3.5 | UE Conf. Test Aspects - Increasing the minimum number of carriers for UE monitoring in UTRA and E-UTRA [LTE_UTRA_IncMon-UEConTest] | RP‑171158 | Status report for WI UE Conformance Test Aspects - Increasing the minimum number of carriers for UE monitoring in UTRA and E-UTRA; rapporteur: Ericsson | RAN5 | WI status report | Yes |
NoMCC: target date change;
conclusion: approved: 12%, Dec.17 ?
| available | No | |||
| RP‑171339 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects: Increasing the minimum number of carriers for UE monitoring in UTRA and E-UTRA (LTE_UTRA_IncMon-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.4 | Open Rel-13 WIs | |||||||||||
| 13.4.1 | UE Conf. Test Aspects - Rel-13 LTE CA configurations [LTE_CA_Rel13-UEConTest] | RP‑171159 | Status report for WI UE Conformance Test Aspects - Rel-13 CA configurations; rapporteur: Ericsson | RAN5 | WI status report | Yes |
Yesconclusion: approved: 59%. Dec.17
| noted | No | |||
| RP‑171340 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Rel-13 LTE CA configurations (LTE_CA_Rel13-UEConTest) (Batch 1) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171341 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Rel-13 LTE CA configurations (LTE_CA_Rel13-UEConTest) (Batch 2) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171342 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Rel-13 LTE CA configurations (LTE_CA_Rel13-UEConTest) (Batch 3) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.4.2 | UE Conf. Test Aspects - LTE DL 4 Rx antenna ports [LTE_4Rx_AP_DL-UEConTest] | RP‑171160 | Status report for WI UE Conformance Test Aspects - LTE DL 4 Rx antenna ports; rapporteur: Ericsson | RAN5 | WI status report | Yes |
NoMCC: target date change;
conclusion: approved: 85%, Sep.17 ?
| available | No | |||
| RP‑171343 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - LTE DL 4 Rx antenna ports (LTE_4Rx_AP_DL-UEConTest) | RAN5 | CR pack | Approval | Yes |
NoMCC: it turned out that R5-173055 which is included in RP-171343 was actually withdrawn in RAN5 and should therefore not be part of this CR pack;
conclusion: partially approved, i.e. all CRs of RP-171343 are approved except R5-173055 which is withdrawn ?
| available | No | ||||
| 13.4.3 | UE Conf. Test Aspects - Licensed-Assisted Access using LTE [LTE_LAA-UEConTest] | RP‑171056 | Status report of WI: UE Conformance Test Aspects - Licensed-Assisted Access using LTE; rapporteur: Qualcomm | RAN5 | WI status report | Yes |
NoMCC: target date change;
conclusion: approved: 90%, Sep.17 ?
| available | No | |||
| RP‑171344 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Licensed-Assisted Access using LTE (LTE_LAA-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.4.4 | UE Conf. Test Aspects - Further LTE Physical Layer Enh. for MTC [LTE_MTCe2_L1-UEConTest] | RP‑171161 | Status report for WI UE Conformance Test Aspects – Further LTE Physical Layer Enhancements for MTC; rapporteur: Ericsson | RAN5 | WI status report | Yes |
NoMCC: target date change; RAN #77 is in Sep.17 and not in Aug. 17;
conclusion: approved: 90%, Sep.17 ?
| available | No | |||
| RP‑171345 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Further LTE Physical Layer Enhancements for MTC (LTE_MTCe2_L1-UEConTest) (Batch 1) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171346 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Further LTE Physical Layer Enhancements for MTC (LTE_MTCe2_L1-UEConTest) (Batch 2) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171347 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Further LTE Physical Layer Enhancements for MTC (LTE_MTCe2_L1-UEConTest) (Batch 3) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171348 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Further LTE Physical Layer Enhancements for MTC (LTE_MTCe2_L1-UEConTest) (Batch 4) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171156 | Revised WID: UE Conformance Test Aspects – Further LTE Physical Layer Enhancements for MTC | Ericsson | WID revised | Approval | Yes |
No
| available | No | ||||
| 13.4.5 | UE Conf. Test Aspects - WLAN/3GPP Radio Level Integration and Interworking Enh. [LTE_WLAN_radio-UEConTest] | RP‑170914 | Status Report of WI UE Conformance Test Aspects - WLAN/3GPP Radio Level Integration and Interworking Enhancements; rapporteur: Intel Corporation (UK) Ltd. | RAN5 | WI status report | Yes |
Yesconclusion: approved: 32%, Sep.17
| noted | No | |||
| RP‑171349 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - WLAN/3GPP Radio Level Integration and Interworking Enhancement Interworking (LTE_WLAN_radio-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.4.6 | UE Conf. Test Aspects - Narrowband IoT [NB_IOT-UEConTest] | RP‑171001 | Status report of WI: UE Conformance Test Aspects - Narrowband IoT; rapporteur: CMCC | RAN5 | WI status report | Yes |
NoMCC: target date change; RAN4 had a huge number of corrections at RAN #76;
conclusion: approved: 95%, Sep.17
| available | No | |||
| RP‑171350 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Narrowband Internet of Things (NB-IOT) (NB_IOT-UEConTest) (Batch 1) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171351 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Narrowband Internet of Things (NB-IOT) (NB_IOT-UEConTest) (Batch 2) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171352 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Narrowband Internet of Things (NB-IOT) (NB_IOT-UEConTest) (Batch 3) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171353 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Narrowband Internet of Things (NB-IOT) (NB_IOT-UEConTest) (Batch 4) | RAN5 | CR pack | Approval | No |
Yes
| withdrawn | Yes | ||||
| 13.4.7 | UE Conf. Test Aspects - LTE CA Enh. Beyond 5 Carriers: PUCCH on Scell [LTE_CA_enh_b5C_PUCCH-UEConTest] | RP‑171087 | Status report for WI: LTE Carrier Aggregation Enhancement Beyond 5 Carriers - PUCCH on Scell; rapporteur: Huawei | RAN5 | WI status report | Yes |
NoMCC: target date change;
conclusion: approved: 8%, March 18 ?
| available | No | |||
| 13.4.8 | UE Conf. Test Aspects - Support for Mission Critical Push To Talk over LTE [New WI: MCPTT-ConTest] | RP‑170947 | Status Report of UE Conformance Test Aspects - Support for Mission Critical Push To Talk over LTE [MCPTT-ConTest]; rapporteur: U.S. Department of Commerce | RAN5 | WI status report | Yes |
NoMCC: late submission;
conclusion: approved: 30%, Dec.17 ?
| available | No | |||
| 13.4.9 | UE Conf. Test Aspects - Interference Mitigation for DL Control Channels of LTE [New WI: LTE_IM_DLCCH-UEConTest] | RP‑170975 | Status Report of WI: UE Conformance Test Aspects – Interference Mitigation for Downlink Control Channels of LTE; rapporteur: Intel Corporation | RAN5 | WI status report | Yes |
YesMCC: target date unclear: Dec.17 (RAN #78) or March 18 (RAN #79) ?
| revised | No | RP‑171319 | ||
| RP‑171319 | Status Report of WI: UE Conformance Test Aspects – Interference Mitigation for Downlink Control Channels of LTE; rapporteur: Intel Corporation | RAN5 | WI status report | Yes |
NoMCC: late request;
conclusion: approved: 5%, March 18 ?
| available | No | RP‑170975 | ||||
| 13.5 | Open Rel-14 WIs | |||||||||||
| 13.5.1 | UE Conf. Test Aspects - LTE UE TRP and TRS and UTRA Hand Phantom [LTE_UTRA_TRP_TRS-UEConTest] | RP‑170936 | Status report for WI UE Conformance Test Aspects - LTE UE TRP and TRS and UTRA Hand Phantom; rapporteur: ZTE | RAN5 | WI status report | Yes |
Yesconclusion: approved: 78%, Sep.17
| noted | No | |||
| RP‑171354 | RAN5 agreed non TTCN CR(s) WI MS Conformance Test Aspects - LTE UE TRP and TRS and UTRA Hand Phantom (LTE_UTRA_TRP_TRS-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.2 | UE Conf. Test Aspects – Rel-14 CA configurations [LTE_CA_R14-UEConTest] | RP‑171162 | Status report for WI UE Conformance Test Aspects - Rel-14 CA configurations; rapporteur: Ericsson | RAN5 | WI status report | Yes |
Yesconclusion: approved: 12%, March 18
| noted | No | |||
| RP‑171355 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects - Rel-14 CA configurations (LTE_CA_R14-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.3 | UE Conf. Test Aspects - Radiated Performance of Multiple-antenna Receivers in the LTE UE [LTE_MIMO_OTA-UEConTest] | RP‑170974 | Status Report of WI: UE Conformance Test Aspects – Radiated Performance of Multiple-antenna Receivers in the LTE UE; rapporteur: Intel Corporation | RAN5 | WI status report | Yes |
NoMCC: target date shift by 9 months;
conclusion: approved: 27%, March 18 ?
| available | No | |||
| RP‑171356 | RAN5 agreed non TTCN CR(s) WI MS Conformance Test Aspects - x (LTE_MIMO_OTA-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑170986 | Revision of WI UE Conformance Test Aspects – Radiated Performance of Multiple-antenna Receivers in the UE | Intel Corporation (UK) Ltd | WID revised | Approval | Yes |
No
| available | No | ||||
| RP‑170988 | WI exception request for UE Conformance Test Aspects – Radiated Performance of Multiple-antenna Receivers in the UE | Intel Corporation (UK) Ltd | WI exception request | Approval | No |
YesMCC: exception requests are not used for RAN5 WIs
| withdrawn | Yes | ||||
| 13.5.4 | UE Conf. Test Aspects - Support for V2V services based on LTE sidelink [LTE_SL_V2V-UEConTest] | RP‑171086 | Status report for WI: Support for V2V services based on LTE sidelink; rapporteur: Huawei | RAN5 | WI status report | Yes |
YesMCC: WI was 15% complete at RAN #75;
conclusion: approved: 15%, Sep.17
| noted | No | |||
| RP‑171357 | RAN5 agreed non TTCN CR(s) WI MS Conformance Test Aspects - Support for V2V services based on LTE sidelink (LTE_SL_V2V-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.5 | UE Conf. Test Aspects - Enhanced LAA for LTE [LTE_eLAA-UEConTest] | RP‑170915 | Status Report | Intel Corporation (UK) Ltd | WI status report | No |
Yessee RP-170916 instead
| withdrawn | Yes | |||
| RP‑170916 | Status Report of WI UE Conformance Test Aspects - Enhanced LAA for LTE [LTE_eLAA_UEConTest]; rapporteur: Intel Corporation (UK) Ltd | RAN5 | WI status report | Yes |
Yesconclusion: approved: 6%, Sep.17
| noted | No | |||||
| RP‑171358 | RAN5 agreed non TTCN CR(s) WI MS Conformance Test Aspects -Enhanced LAA for LTE (LTE_eLAA-UEConTest) | RAN5 | CR pack | Approval | No |
Yes
| withdrawn | Yes | ||||
| 13.5.6 | UE Conf. Test Aspects – CBRS 3.5GHz Band for LTE in the US (Band 48) [LTE_TDD_3550_CBRS_US-UEConTest] | RP‑171313 | Status report of WI UE Conformance Test Aspects - Citizens Broadband Radio Service (CBRS) 3.5GHz Band for LTE in the United States (Band 48); rapporteur: Nokia | RAN5 | WI status report | Yes |
NoMCC: late request
conclusion: approved: 100%, June 17; WI is completed ?
| available | No | |||
| RP‑171359 | RAN5 agreed non TTCN CR(s) under WI UE Conformance Test Aspects – Citizens Broadband Radio Service (CBRS) 3.5GHz Band for LTE in the United States (Band 48) (LTE_TDD_3550_CBRS_US-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.7 | UE Conf. Test Aspects - LTE 2.6 GHz FDD SDL band (2570-2620 MHz) and LTE CA (2DL/1UL) with Band 3 for Region 1 (Band 69) [New WI: LTE_FDD_2600_CA_B3-UEConTest] | RP‑170950 | Status Report for WI UE Conformance Test Aspects - LTE 2.6 GHz FDD SDL band (2570-2620 MHz) and LTE Carrier Aggregation (2DL/1UL) with Band 3 for Region 1 (Band 69); rapporteur: Bureau Veritas, Orange | RAN5 | WI status report | Yes |
Yesconclusion: approved: 43%, Dec.17
| noted | No | |||
| RP‑171360 | RAN5 agreed non TTCN CR(s) under WI UE Conformance Test Aspects – LTE 2.6 GHz FDD SDL band (2570-2620 MHz) and LTE Carrier Aggregation (2DL/1UL) with Band 3 for Region 1 (Band 69) (LTE_FDD_2600_CA_B3-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.8 | UE Conf. Test Aspects - RAT Independent Further Indoor Positioning Enh. for LTE [New WI: LTE_iPos_enh2_RI-UEConTest] | RP‑170949 | Status report of WI UE Conformance Test Aspects - RAT Independent Further Indoor Positioning Enhancements for LTE; rapporteur: NextNav | RAN5 | WI status report | Yes |
Yesconclusion: approved: 24%, Dec.17
| noted | No | |||
| RP‑171378 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – RAT Independent Further Indoor Positioning Enhancements for LTE (LTE_iPos_enh2_RI-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.9 | UE Conf. Test Aspects - SRS switching between LTE component carriers [New WI: LTE_SRS_switch-UEConTest] | RP‑171088 | Status report for WI: UE Conformance Test Aspects - SRS (sounding reference signal) switching between LTE component carriers; rapporteur: Huawei | RAN5 | WI status report | Yes |
Yesconclusion: approved: 5%, March 18
| noted | No | |||
| RP‑171379 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – SRS (sounding reference signal) switching between LTE component carriers (LTE_SRS_switch-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.10 | UE Conf. Test Aspects - QoE Measurement Collection for streaming services in UTRAN [New WI: UMTS_QMC_Streaming-UEConTest] | RP‑171089 | Status report for WI: UE Conformance Test Aspects - Quality of Experience (QoE) Measurement Collection for streaming services in UTRAN; rapporteur: Huawei | RAN5 | WI status report | Yes |
Yesconclusion: approved: 20%, Dec.17
| noted | No | |||
| RP‑171380 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – Quality of Experience (QoE) Measurement Collection for streaming services in UTRAN (UMTS_QMC_Streaming-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.11 | UE Conf. Test Aspects - Perf. enh for high speed scenario in LTE [New WI: LTE_high_speed-UEConTest] | RP‑171000 | Status report of WI: UE Conformance Test Aspects - Performance enhancements for high speed scenario in LTE, rapporteur: CMCC | RAN5 | WI status report | Yes |
Yesconclusion: approved: 5%, June 18
| noted | No | |||
| RP‑171381 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – Performance enhancements for high speed scenario in LTE (LTE_high_speed-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.12 | UE Conf. Test Aspects - New band support for Rel-14 NB-IoT [New WI: NB_IOT_R14_bands-UEConTest] | RP‑171163 | Status report for WI UE Conformance Test Aspects - New band support for Rel-14 NB-IoT; rapporteur: Ericsson | RAN5 | WI status report | Yes |
Yesconclusion: approved: 30%, Dec.17
| noted | No | |||
| RP‑171382 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – New band support for Rel-14 NB-IoT (NB_IOT_R14_bands-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.13 | UE Conf. Test Aspects - 4 Rx antenna ports with CA for LTE DL [New WI: LTE_4Rx_AP_DL_CA-UEConTest] | RP‑171164 | Status report for WI UE Conformance Test Aspects - 4 Rx antenna ports with CA for LTE DL; rapporteur: Ericsson | RAN5 | WI status report | Yes |
Yesconclusion: approved: 5%, March 18
| noted | No | |||
| RP‑171383 | RAN5 agreed non TTCN CR(s) WI UE Conformance Test Aspects – 4 Rx antenna ports with CA for LTE DL (LTE_4Rx_AP_DL_CA-UEConTest) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 13.5.14 | Test - (Small) Technical Enhancements and Improvements for Rel-14 [TEI14_Test] | RP‑171384 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-14 Conformance Testing (TEI14_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14 | Maintenance for closed WIs/SIs for REL-13 and earlier | |||||||||||
| 14.1 | TSG RAN WG1 | |||||||||||
| 14.1.1 | Approval of CRs to closed Rel-8 WIs and WIs of previous releases | |||||||||||
| 14.1.2 | Approval of CRs to closed Rel-9 WIs (incl. TEI9) | |||||||||||
| 14.1.3 | Approval of CRs to closed Rel-10 WIs (incl. TEI10) | |||||||||||
| 14.1.4 | Approval of CRs to closed Rel-11 WIs (incl. TEI11) | |||||||||||
| 14.1.5 | Approval of CRs to closed Rel-12 WIs (incl. TEI12) | |||||||||||
| 14.1.6 | Approval of CRs to closed Rel-13 WIs (incl. TEI13) | RP‑171193 | Maintenance of Rel-13 LTE carrier aggregation enhancement beyond 5 carriers | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171196 | Maintenance of Rel-13 Further LTE Physical Layer Enhancements for MTC | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171197 | Maintenance of Rel-13 NB-IoT feature | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171198 | Corrections for Rel-13 (36.211/36213) | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171209 | Maintenance of Rel-13 Elevation Beamforming/Full-Dimension (FD) MIMO for LTE | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.1.7 | Approval of linked CR packages led by RAN WG1 | RP‑171099 | Correction on the power control of NPRACH in 36.213 Rel-13 | Huawei, HiSilicon | CR | Approval | No |
No
| reserved | No | ||
| RP‑171098 | Correction on the power control of NPRACH in 36.213 Rel-14 | Huawei, HiSilicon | CR | Approval | No |
No
| reserved | No | ||||
| RP‑171101 | Correction on the power control of NPRACH in 36.321 Rel-13 | Huawei, HiSilicon | CR | Approval | No |
No
| reserved | No | ||||
| RP‑171100 | Correction on the power control of NPRACH in 36.321 Rel-14 | Huawei, HiSilicon | CR | Approval | No |
No
| reserved | No | ||||
| RP‑171103 | Correction on the power control of NPRACH in 36.331 Rel-13 | Huawei, HiSilicon | CR | Approval | No |
No
| reserved | No | ||||
| RP‑171102 | Correction on the power control of NPRACH in 36.331 Rel-14 | Huawei, HiSilicon | CR | Approval | No |
No
| reserved | No | ||||
| 14.2 | TSG RAN WG2 | |||||||||||
| 14.2.1 | Approval of CRs to closed Rel-8 WIs and WIs of previous releases | RP‑171241 | RAN2 CRs to Approval of CRs to closed Rel-8 Wis and Wis of previous releases | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.2.2 | Approval of CRs to closed Rel-9 WIs (incl. TEI9) | |||||||||||
| 14.2.3 | Approval of CRs to closed Rel-10 WIs (incl. TEI10) | |||||||||||
| 14.2.4 | Approval of CRs to closed Rel-11 WIs (incl. TEI11) | |||||||||||
| 14.2.5 | Approval of CRs to closed Rel-12 WIs (incl. TEI12) | RP‑171242 | RAN2 CRs to Approval of CRs to closed Rel-12 WIs (incl. TEI12) | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171179 | Entry-Level UE Support UL 64QAM | MediaTek Inc. | discussion | Yes |
NoProposal 1: RAN Plenary meeting approves the CRs to enable UL64QAM in Cat-4 devices
| available | No | |||||
| RP‑171248 | RAN2 CRs to Entry-Level UE Support UL 64QAM | RAN2 | CR pack | Approval | Yes |
NoMCC: Acc. to RAN2 chairman:
new UE category combination to enable UE category 4 with UL 64 QAM: purpose to enable UL 64 QAM to be supported by a lower DL category than currently possible;
RAN2 technically endorsed 36.331 and 36.306 CRs from Rel-12 (provided to RAN in CR pack RP-171248);
RAN asked to make decision on the need and the starting release of the CRs
MCC: Why do CR titles talk about UL 64 QAM while CRs are for DL? It is rather: introduction of a new DL UE cat.4 supporting UL 64 QAM with UL UE cat.5;
Any relation with RP-171247 CRs (which introduced UL UE cat.21)?
| available | No | ||||
| 14.2.6 | Approval of CRs to closed Rel-13 WIs (incl. TEI13) | RP‑171243 | RAN2 CRs to Approval of CRs to closed Rel-13 WIs (incl. TEI13), part 1 | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171244 | RAN2 CRs to Approval of CRs to closed Rel-13 WIs (incl. TEI13), part 2 | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171245 | RAN2 CRs to Approval of CRs to closed Rel-13 WIs (incl. TEI13), part 3 | RAN2 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.2.7 | Approval of linked CR packages led by RAN WG2 | |||||||||||
| 14.3 | TSG RAN WG3 | |||||||||||
| 14.3.1 | Approval of CRs to closed Rel-8 WIs and WIs of previous releases | |||||||||||
| 14.3.2 | Approval of CRs to closed Rel-9 WIs (incl. TEI9) | |||||||||||
| 14.3.3 | Approval of CRs to closed Rel-10 WIs (incl. TEI10) | |||||||||||
| 14.3.4 | Approval of CRs to closed Rel-11 WIs (incl. TEI11) | |||||||||||
| 14.3.5 | Approval of CRs to closed Rel-12 WIs (incl. TEI12) | |||||||||||
| 14.3.6 | Approval of CRs to closed Rel-13 WIs (incl. TEI13) | RP‑171329 | CRs to closed Rel-13 WIs (incl. TEI13) | RAN3 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.3.7 | Approval of linked CR packages led by RAN WG3 | |||||||||||
| 14.4 | TSG RAN WG4 | |||||||||||
| 14.4.1 | Approval of CRs to closed Rel-8 WIs and WIs of previous releases | RP‑171292 | RAN4 CRs to TEI8 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.4.2 | Approval of CRs to closed Rel-9 WIs (incl. TEI9) | RP‑171293 | RAN4 CRs to closed Rel-9 WIs (incl. TEI9) | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.4.3 | Approval of CRs to closed Rel-10 WIs (incl. TEI10) | RP‑171294 | RAN4 CRs to closed Rel-10 WIs (incl. TEI10) | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171395 | RAN4 agreed CRs to Rel-10 WI Carrier Aggregation for LTE | RAN4 | CR Pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.4.4 | Approval of CRs to closed Rel-11 WIs (incl. TEI11) | RP‑171295 | RAN4 CRs to TEI11 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.4.5 | Approval of CRs to closed Rel-12 WIs (incl. TEI12) | RP‑171296 | RAN4 CRs to closed Rel-12 WIs (incl. TEI12) | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171297 | RAN4 CRs to TEI12 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.4.6 | Approval of CRs to closed Rel-13 WIs (incl. TEI13) | RP‑171298 | RAN4 CRs to closed Rel-13 WIs | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171299 | RAN4 CRs to closed Rel-13 WIs: NB_IOT part1 | RAN4 | CR pack | Approval | Yes |
NoMCC: 45 essential RAN4 corrections to REL-13 WI NB_IOT completed in Dec.16 ?
| available | No | ||||
| RP‑171300 | RAN4 CRs to closed Rel-13 WIs: NB_IOT part2 | RAN4 | CR pack | Approval | Yes |
NoMCC: 45 essential RAN4 corrections to REL-13 WI NB_IOT completed in Dec.16 ?
| available | No | ||||
| RP‑171301 | RAN4 CRs to closed Rel-13 WIs: NB_IOT part3 | RAN4 | CR pack | Approval | Yes |
NoMCC: 45 essential RAN4 corrections to REL-13 WI NB_IOT completed in Dec.16 ?
| available | No | ||||
| RP‑171302 | RAN4 CRs to closed Rel-13 WIs: NB_IOT part4 | RAN4 | CR pack | Approval | Yes |
NoMCC: 45 essential RAN4 corrections to REL-13 WI NB_IOT completed in Dec.16 ?
| available | No | ||||
| RP‑171303 | RAN4 CRs to closed Rel-13 WIs: NB_IOT part5 | RAN4 | CR pack | Approval | Yes |
YesMCC: 45 essential RAN4 corrections to REL-13 WI NB_IOT completed in Dec.16 ?
| approved | No | ||||
| RP‑171304 | RAN4 CRs to closed Rel-13 WIs: LTE DL 4 Rx antenna ports | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171305 | RAN4 CRs to closed Rel-13 WIs: Base Station (BS) RF requirements for Active Antenna System (AAS) - Core part | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171306 | RAN4 CRs to closed Rel-13 WIs: Base Station (BS) RF requirements for Active Antenna System (AAS) - Perf. Part | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171307 | RAN4 CRs to closed Rel-13 WIs: Licensed-Assisted Access using LTE | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171308 | RAN4 CRs to closed Rel-13 WIs: Further LTE Physical Layer Enhancements for MTC - Core part | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171309 | RAN4 CRs to closed Rel-13 WIs: Further LTE Physical Layer Enhancements for MTC - Perf. part Part 1 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171310 | RAN4 CRs to closed Rel-13 WIs: Further LTE Physical Layer Enhancements for MTC - Perf. part Part 2 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171311 | RAN4 CRs to closed Rel-13 WIs: TEI13 | RAN4 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.4.7 | Approval of linked CR packages led by RAN WG4 | |||||||||||
| 14.5 | TSG RAN WG5 | |||||||||||
| 14.5.1 | Approval of CRs to closed REL-10 WIs (incl. TEI10_Test) and WIs of previous releases | RP‑171361 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel 99 Conformance Testing(TEI_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171362 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-7 Conformance Testing(TEI7_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171363 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-8 Conformance Testing(TEI8_Test) (Batch 1) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171364 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-8 Conformance Testing(TEI8_Test) (Batch 2) | RAN5 | CR pack | Approval | No |
Yes
| withdrawn | Yes | ||||
| RP‑171365 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-9 Conformance Testing(TEI9_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171374 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-10 Conformance Testing (TEI10_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.5.2 | Approval of CRs to closed REL-11 WIs (incl. TEI11_Test) | RP‑171375 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-11 Conformance Testing (TEI11_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.5.3 | Approval of CRs to closed REL-12 WIs (incl. TEI12_Test) | RP‑171376 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-12 Conformance Testing (TEI12_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 14.5.4 | Approval of CRs to closed REL-13 WIs (incl. TEI13_Test) | RP‑171366 | CR to 34.229-3: Add new verified and e-mail agreed TTCN test cases in the TC lists in 34.229-3 (prose), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑171367 | CR to 34.229-3: Add new verified and e-mail agreed TTCN test cases in the TC lists in 34.229-3 (TTCN), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171368 | CR to 34.123-3: Add new verified and e-mail agreed TTCN test cases in the TC lists in 34.123-3 (prose), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171369 | CR to 34.123-3: Add new verified and e-mail agreed TTCN test cases in the TC lists in 34.123-3 (TTCN), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171370 | CR to 36.523-3: Add new verified and e-mail agreed TTCN test cases in the TC lists in 36.523-3 (prose), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171371 | CR to 36.523-3: Add new verified and e-mail agreed TTCN test cases in the TC lists in 36.523-3 (TTCN), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171372 | CR to 37.751-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171373 | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (TTCN), Annex A | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| RP‑171377 | RAN5 agreed non TTCN CR(s) under WI Small Technical Enhancements and Improvements for Rel-13 Conformance Testing (TEI13_Test) | RAN5 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.5.5 | Approval of linked CR packages led by RAN WG5 | |||||||||||
| 14.6 | TSG RAN WG6 | |||||||||||
| 14.6.1 | Approval of CRs to closed Rel-8 WIs and WIs of previous releases | |||||||||||
| 14.6.2 | Approval of CRs to closed Rel-9 WIs (incl. TEI9) | |||||||||||
| 14.6.3 | Approval of CRs to closed Rel-10 WIs (incl. TEI10) | |||||||||||
| 14.6.4 | Approval of CRs to closed Rel-11 WIs (incl. TEI11) | |||||||||||
| 14.6.5 | Approval of CRs to closed Rel-12 WIs (incl. TEI12) | |||||||||||
| 14.6.6 | Approval of CRs to closed Rel-13 WIs (incl. TEI13) | RP‑170927 | RAN6 agreed CRs for REL-13 WI Core Part: Extended DRX (eDRX) for GSM (eDRX_GSM) | RAN6 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| RP‑170928 | RAN6 agreed CRs for REL-13 WI: Extended Coverage GSM (EC-GSM) for support of Cellular Internet of Things (CIoT_EC_GSM) | RAN6 | CR pack | Approval | Yes |
Yes
| approved | No | ||||
| 14.6.7 | Approval of linked CR packages led by RAN WG6 | |||||||||||
| 14.7 | Closed SIs for REL-13 and earlier | RP‑171202 | Maintenance to TR36.873 - Study on 3D channel model for LTE | RAN1 | CR pack | Approval | Yes |
Yes
| approved | No | ||
| 15 | Inter WG/TSG-related discussions & decisions | RP‑171470 | Agenda for joint RAN - SA session during TSG #76 | RAN chairman (Nokia), SA chairman (Samsung) | agenda | No |
No
| reserved | No | |||
| 16 | Terms of Reference (ToR) | |||||||||||
| 17 | Project management | RP‑170874 | 3GPP Work Plan review at Plenary #76 | ETSI MCC | Work Plan | Information | No |
No
| reserved | No | ||
| RP‑171458 | Multiple meeting check-ins from a single computer | ETSI MCC | discussion | discussion | Yes |
No
| available | No | ||||
| 18 | Future meeting schedule | RP‑171189 | Proposal to control the workload at RAN#77 | Huawei | discussion | Discussion | Yes |
Noproposal:
• allow approval of new LTE WIs for RAN1/2/3/4 at RAN#77 within the available TU
• consider reducing the online time used at RAN#77:
- option 1: retain a 4 day-TSG but close earlier each day when possible (e.g. 2 or 3 pm)
- option 2: shorten RAN#77 to 3 days, e.g. Mon-Wed or Tue-Thu or Wed-Fri
| available | No | ||
| 19 | Any other business | |||||||||||
| 20 | Closing of the meeting |