CB: #31_EN-DC_Data_VolRep

Slides:



Advertisements
Similar presentations
Tunneling Protocol Support for 1x CSFB from E-UTRAN
Advertisements

HUAWEI TECHNOLOGIES CO., LTD. Huawei Technologies Co., Ltd. grant a free, irrevocable license to 3GPP2 and its Organizational Partners to.
1 What’s New in the Therapy Prior Authorization Review Process? December 2011 Therapy Clinical Webinars.
X xxx Pre-Registration Context in eHRPD 1 Pre-Registration Context Removal in eHRPD System Sources: China Telecom, ZTE Contact: Li
Draft Operational procedures for registry systems 09 November 2004 Bonn, Germany Technical Breakout Group.
The Treatment of “Spare / Sterilised” Capacity – follow up Draft for discussion purposes only.
1 Project Nexus Data Management Definition Workshop 18 th May 2009.
Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.
Support for CSFB Tony Lee David Wang David Wang June/15/2009 VIA Telecom grants.
Online Marketing Messages Description / guideline Ronni Hartvig November 2010.
Template and guidance for the content of the Partnership Agreement 24 May
Lessons Learned Process – A Strawman.  Lessons Learned  “To pass on any lessons that can be usefully applied to other projects”  “The data in the report.
HUAWEI TECHNOLOGIES CO., LTD. Slide title :40-47pt Slide subtitle :26-30pt Color::white Corporate Font : FrutigerNext LT Medium Font to.
Guidelines for: Release Maintenance, Small Enhancement and Feature Work Items Group Name: TP15 Source: Mow Convenor, (Scarrone Enrico, Telecom Italia)
JDTA Item and Learning Object Versioning – Proposed Approach JDTA Item and Learning Object Versioning – Proposed Approach Jamie Stewart, Steve Wicinski,
Process Description and Quality Guidelines – Two Birds with One Stone European Conference on Quality in Official Statistics Q2014 Rudi Seljak, Tina Steenvoorden.
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Information Service Flow Update Date Submitted: October 22, 2006.
Define Research Problem. 2 Management objectives: –To solve current problem facing company –To improve efficiency –To plan for future Current problems.
1 © NOKIA IPTel2001.PPT/ / DOT Scalable Floor Control in Conferencing Environments : The RBone Approach Dirk Trossen Nokia Research Center Boston.
RMDSRMDS Retail Market Design Services 1 IGG Agenda – March 8 th 2007 Minutes from last IGG meeting10.00 – Review of Action Items10.10.
Indicators to communicate progress towards good status WG DIS, April 2015.
Emergency Cashout Prices and Emergency Curtailment Quantity (ECQ) Adjustment Ritchard Hewitt Gas Code Development Manager.
Update on 3GPP RAN3 Multi-RAT joint coordination
Diameter Group Signaling Thursday, August 02 nd, 2013 draft-ietf-diameter-group-signaling-01 Mark Jones, Marco Liebsch, Lionel Morand IETF 87 Berlin, Germany.
EHRPD-LTE Inter Technology Spectrum Optimization Source: Qualcomm Incorporated Contact: Jun Wang/George Cherian September 9, 2013 Notice ©2013. All rights.
RFC 4068bis draft-ietf-mipshop-fmipv6-rfc4068bis-01.txt Rajeev Koodli.
1 MAPSUP in eHRPD Sources: ZTE Contact: Bi YiFeng Rajesh Bhalla ABSTRACT:
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: September,
By Suman(1RV12LDC29).  Long Term Evolution (LTE) promises higher data rates, 100Mbps in the downlink and 50Mbps in the uplink in LTE’s first phase, and.
3GPP TSG RAN WG2 meeting #92 Nanjing, China 23-27, May 2016 R
109-Mar-12 Quality Function Application Services What’s New in SPEED? - Release Updates March 2012.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: August,
Ultra-Flash CSFB(SRVCC based CSFB)
Week #15 LTE-WLAN Aggregation (LWA)
Power control Considerations and framework for MS-MS Communications
Human Computer Interaction Lecture 21 User Support
WF on RA-RNTI design 3GPP TSG RAN WG1 Meeting NR#3 R1-171xxxx
IEEE MEDIA INDEPENDENT HANDOVER
Professional Skepticism
ONAP security meeting
Update on 3GPP RAN3 Multi-RAT joint coordination
Report of the Handover Rapporteur Group, Session #55 Macau
Use Cases Discuss the what and how of use cases: Basics Benefits
Human Computer Interaction Lecture 21,22 User Support
Healthcare Information Technology Standards Panel
Network instantiation
WG2 - ARC TP#29 Status Report
MAF&MEF Interface Specification discussion of the next steps
Review of Part C of the Code – Applicability
Options for increasing the number of LTE bearers
Intra LTE Handover.
Discussion and Way Forward NB IoT UE Differentiation
Insolvency regime for further education and sixth form colleges
WF on LTE-NR Coexistence
Emergency Call Number Support
A framework for Management and Control of microwave and millimeter wave interface parameters draft-ietf-ccamp-microwave-framework-01
January 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposal of extra control IEs for IEEE.
3GPP RAN1 status on NR-Unlicensed
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Transactions and Concurrency
Lessons Learned Process – A Strawman
3GPP RAN1 status on NR-Unlicensed
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Openings, Transitions, and Closings
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Alignment of Part 4B with ISAE 3000
Point Evidence Terminology Analysis Link 100% 50% 0% To what extent….
Presentation transcript:

CB: #31_EN-DC_Data_VolRep

Scope of come back clarify scenario enable reporting in E-RAB release indication (if agreeable) any other S1AP, X2AP procedures that need updating (if needed) reporting is enabled by OAM WF St2 St3 (if possible) Coordinate with HW, QC, NEC

Clarify scenario The scenarios and principles outlined in 23.401 (in particular parts based on CR3285r3) sets the scene and looking at the input papers companies appears to have a similar understanding

Enable reporting in E-RAB release indication (if agreeable) Two of the input papers proposed to enable reporting in the E-RAB Release Indication message There was no concerns raised on this in the online discussion This is clearly covered by current 23.401 It is therefore proposed to agree inclusion of an optional IE to enable the report of data volumes in the E-RAB Release Indication message

New S1 Volume reporting procedure All companies proposed 1 new class 2 S1 procedure (that will be used during HO or for periodic reporting)

Additional S1 procedures? One company also proposed a new S1 procedure to activate the reporting There is however a clear statement in 23.401 that the PLMN locally activates the Secondary RAT Data Volume Reporting by E-UTRAN O&M It is proposed to agree that reporting is enabled by O&M And as a consequence, no additional S1 procedures are needed

Proposed Way forward S1 X2 Include one optional new IE in the following existing S1 messages: UE Context Suspend Request, UE Context Release Complete, E-RAB Release Response, E-RAB Release Indication, E-RAB Modification Indication, E-RAB Modify Response (with a possibility for the MME to include a request for a report in the E-RAB MODIFY REQUEST message). Add 1 new class 2 S1 procedure (to be used during HO or for periodic reporting) X2 Agree principle that SgNB reports on NR data volume reports for all bearer types (without any trigger?) Add 1 new class 2 procedure SgNB modification Request Acknowledge message can be reused to report the data volume for the dedicated bearers

Stage 2 (for discussion) There is currently Stage 2 input for 36.300, 37.340 and 36.401 Are all needed? For short function description, can take either change for 36.300 or 36.401? How detailed? The 37.340 TP contains a lot of detailes

Stage 3 topics (for discussion) Details on the Volume Report? Huawei propose to include RAT Type Ericsson propose 1 or 2 volumes with start and end time stamps Size of Data Volume IE INTEGER (0..16777215) ? or keep FFS S1, base on R3-174107 (E///) X2, base on R3-173925 (Hua)

Other topics (for discussion) Optimization for X2 HO case One propose possible optimization to avoid additional signalling towards MME during X2 HO Is this optimization needed?