Presentation is loading. Please wait.

Presentation is loading. Please wait.

CB: #31_EN-DC_Data_VolRep

Similar presentations


Presentation on theme: "CB: #31_EN-DC_Data_VolRep"— Presentation transcript:

1 CB: #31_EN-DC_Data_VolRep

2 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

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

4 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 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

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

6 Additional S1 procedures?
One company also proposed a new S1 procedure to activate the reporting There is however a clear statement in 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

7 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

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

9 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 ( ) ? or keep FFS S1, base on R (E///) X2, base on R (Hua)

10 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?


Download ppt "CB: #31_EN-DC_Data_VolRep"

Similar presentations


Ads by Google