Description
RET Implementation through JCP Technical Support Team, Deployment Part Document Number: INJR-PR0516031
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
Document Version 2.0 May 2016
Introduction: Remote Electrical Tilt [RET] RET (Remote Electric Tilt): (RET) allows for accurate control of antenna tilt eliminating site-access requirement, allowing the tilt to be adjusted remotely from the Base station/network control center. During the network optimization activity, coverage/interference can be controlled by RET and its implementation is also easy & fast as it required to implement/configure from remote/LSMR end and no field visit required. Initially we conduct RET directly through LSMR, which plum to keep previous records for any delta in the network implementation. But, It is very important to know exactly ‘what' we have currently configured at each network cell. And equally important, to know 'why' that given value has changed, or optimized. “JCP” is the tool which is recommended to raise work request for RET change through LSMR, to keep records in trajectory. (i.e. Previous RET value, Reference RET value and Implemented RET value).
RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
2
RET Implementation work flow overview: Requester: Generate Work Order Request for Change in RET. RET WO Request is administered by JCP.
Zonal Lead: KPI Pre-Post Report verification after submitted by the requester.
QA Lead: Final Level verification of RET implementation. New value will consider then as a reference after successful execution.
KPI-Pre-Post (Re-Optimization if required) WO Executed RJIL Requester (CM Circle Optimizer)
WO Partially Executed
Samsung Requester (RF Lead)
Force push into history after Zonal Lead approval
Root Cause Analysis for Execution Failure.
Approval
Circle Dy. CTO approved for the RET execution
Work Order Closed
Execution Process
Requester will get WO Status based on Cell execution status Rescheduled
RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
3
Automation Process overview: To implement any change in the RET, “Requester” has to initiate the WO request in JCP. For any individual cell WO can only be raised by the CM Optimizer (from RJIL Team) and RF Lead (from Samsung team). Once WO raised it needs to be approved by respective circle Dy. CTO. After the approval, the cell under WO gets locked, unless the work order get closed. During the execution process, requester will get WO status based on cell execution status.
After the completion of the execution process, If all the cell are successfully executed, status will reflect “Executed” for particular WO. In case, any cell failed in the execution process (out of all), status will reflect “Partially Executed” for that particular WO. In case of successful execution, requested needs to submit pre-post KPI of the cell (of WO) to “Zonal Lead”. After the verification of the zonal lead, QA Lead approval is required to close the Work order. In case of partially executed, requester will identify RCA for the failure reason and rescheduled it after correction or forcefully pushed the WO into the history bucket by Zonal Lead approval (In exception cases only). Therein, requester will submit KPI pre-post to “Zonal Lead” for approval for verification.
Note: - Maximum 100 cells can be implemented in a single Work order. - Once the work order approved by Dy. CTO, Cell will get “LOCKED” until WO gets “CLOSED”. For Partial executed WOs, execution failed cells will be unlocked for Re-Schedule or Re-Optimize only. RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
4
Work Order Status Description: During the execution procedure, requester can observe the status of the work order. The work order Status are as follows: 1.
Cancelled: If WO cancelled is generated by the requester and then cancelled by the Dy. CTO comes in the cancelled category.
2.
Close: If the WO gets closed (irrespective of Execution) comes under closed category.
3.
Executed: If all the cell of the WO implementation executed successful and approved by the Zonal lead and QA lead come under executed category.
4.
Expired: If the WO does not approved by Dy. CTO within a sanctioned time, then the WO gets expired.
5.
Failed: If none of the cell in the WO executed successfully, then the WO comes under Failed.
6.
In Progress: If the WO execution is in progress, it comes under the “In progress” status.
7.
No Action performed: If the WO reference RET approval is pending with NHQ zonal lead, then it reflects in “No action performed status”.
8.
Partially Executed: If all the cell of the WO not implemented successfully then WO will go in Partially executed state.
9.
Re-optimized: If pre-post threshold is not meeting then requester will re-optimize particular cells, then the WO comes under “Re-optimized” status.
10. Time out: Connection issue observed in this case, Need to reschedule WO. 11. Aborted: Aborted due to Failed Retrieve CONNECT FAIL due to site down. RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
5
RET Pass Case (Sample) Below is the JCP RET WO Status Dump Sample, It includes WO ID, LSMR ID, SAP ID, Band, Cell ID, Sector ID, RET Old Value, RET New Value, WO Execution State, Execution Status Cell (Each Cell Status in a WO) and Execution Response. Execution Response includes the LSMR command details and RET response to LSMR on particular command implied for the execution of RET change. Below mentioned case includes, Execution Status of Each Cell (i.e. Pass), and Complete WO Status (i.e. Close).
RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
6
LSMR Execution Process: Retrieve: During the RET change process , retrieve change command scrutinize the present RET value of the particular cell. Below mentioned figure mark the present RET Tilt value (Marked), i.e. 8o ALD Command: In further execution of process, LSMR initiate the ALD command to check the ALD Status. If ALD will be UP, means RET is in operational state. The below mentioned figure initiate the ALD status i.e. “ALD_UP” Change RET Request: After completing RET operational State, LSMR initiate RET Change request from the old value to the new value provided. Below figure mentioned the RET change value from 80=>50 (i.e. 85). Retrieve: After change the RET value, LSMR again initiate the Retrieve command to confirm the new implemented value of RET, before closing the procedure. Below figure mentioned the retrieve value of RET after execution. RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
7
RET Failed Cases:- RET Retrieve Fail Case 1: In this failed case, LSMR receive Result = NOK and REASON = NO DATA, while LSMR initiate its retrieve command to receive present Tilt value of the RET. In below figure, marked is the result shown by LSMR command message.
Reason: Following could be the reason for failed RET Execution under above case: o ALD Connect Issue/ Motor Issue o SITE Down o Type 3/Type 4 Ant Type o ALD ID wrong Configured. o Check Band Availability in the particular cell of which the RET WO has been raised. o In case, change in Ant Type or RET type or both, check configuration as per the new guidelines. Solution: o Under this case, field level activity is required for intact and resolve ALD Connect/ Motor Issue. o Check ALD ID before execution RET change command in LSMR.
Note: In case All above configuration attributes/alarm are ok but RTRV showing “No Data”. It would be related to Bug Observed in current eNB package, as TM block updates RET list every 1 minutes, results no data retrieved intermittently ,Work around solution is to reschedule it again. It will be fixed in next SW pkg release. RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
8
RET Failed Cases:- E-Tilt Value Out-Of-Range (1/2) Case 2: In this failed case, E-Tilt value that was raised in WO was out-of-range of E-Tilt values supported by the RET device. Below figure mentioned the LSMR command message for the above fail cases. Under this case, Initial retrieve command shows the E-Tilt initial value, ALD command will Show “ALD UP”, but RET change command shows wrong output (LSMR command Response shown in Next Slide). In RET change command it shows, New implied value on both side, where as it has to show, previous value and new value likewise. After RET change execution in next retrieve command, it shows previous RET value. Due to range issue in RET, PLD keep comparing RET Device and RET PLD data value, found mismatch and keep trying to correct E-Tilt and fail due to Hardware limitation.
Solution: We can check the supported range of E-Tilt value of RET before executing any higher tilt values (RTRV-RETDEV-INF). RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
9
RET Failed Cases:- E-Tilt Value Out-Of-Range (2/2)
Initial Retrieve Command
Out-of-Range Tilt Command
ALD Status updating Retrieve Command after RET change execution RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
10
RET Failed Cases: No RET Data during Retrieve: Case 3: In this failed case, after Retrieve command from LSMR, response command fails to show RET value, instead it shows “-”. Below figure mentioned the LSMR response command for this test case. In Initial retrieve command response, present RET value is failed to fetch, then ALD UP command response with “ALD UP”, but RET change command shows error. In RET change command it shows, New implied value on both side, where as it has to show, previous value and new value like wise. After RET change execution in next retrieve command, it again fails to show any RET value.
Initial Retrieve Command
After RET Execution Retrieve Value
Reason: The possible reason for this case could be RET Configuration Issue, RET Motor Jam/RET Alarm.
Solution: • Check Local LSMR for RET configuration • Check the ALD/RET module for faulty RET Motor at antenna end and clear the RET/ALD Alarm.
RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
11
RET Failed Cases: Failure due to eNode-B Packet up gradation Case 4: In this failed case, after Initial Retrieve command from LSMR, response command shows “COMMAND FAILURE: DENY”. Below figure mentioned the LSMR response command for this test case. In Initial retrieve command response, it shows Result: NOK, and Reason: Internal Server Error.
Reason: This error is observed due to eNode-B package upgraded 7.5.0 development pending from JCP end. Solution: Now, It has been resolved. RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
12
RET Failed Cases: ALD Down Case 5: In this failed case, after ALD command from LSMR, response command shows ALD Down. Below figure mentioned the LSMR response command for this test case. Under this case, after Initial retrieve command , ALD command will Show “ALD DOWN”. Need to check for ALD down reason.
ALD Status after ALD Command
Initial Retrieve Command
Solution: - ALD Issue to be rectify and clear the ALD alarm. - Post correcting ALD status (once ALD is UP), reschedule the WO.
RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
13
RET Failed Cases: Unable to Raise WO (RET Config Check Required) Case 6: In this failed case, user fails to raise WO for the RET change, as it shows in remark “RET Configuration check required”. a. This issues arouses when some entities (mentioned below) are not configured through LSMR.
If above entities are left blank, then “ALD Config” value is just like a dummy value. b. If SAPID don’t have Connect BOARD ID / Connect Port ID / ANT ID and source is Siteforge then check latest RET.XML file is available at LSMR or not. Jio State
LSMR ID
SAP ID
ENB ID Sector Id Cell ID Bands CLOT RET
Source
Date & Time
ALD config ( 0 or 1) Connect Board ID Connect Port ID ANT ID Cell Status
Karnataka KA-KA-REM-17-A I-KA-HLYL-ENB-B002 6475
2
1657618 2300
-
LSMR
8/1/2018 19:44
1
0
2
1
Active
Karnataka KA-KA-REM-17-A I-KA-HLYL-ENB-B002 6475
0
1657616 2300
-
LSMR
8/1/2018 11:42
1
0
0
1
Active
Karnataka KA-KA-REM-17-A I-KA-HLYL-ENB-B002 6475
1
1657617 2300
-
SITEFORGE 8/1/2018 11:21
1
Active
Note : If above mentioned entities are configured already then share snapshot of LSMR for further enhancement with the issue. Also, need to check RET configuration where CCI antenna has been installed, reconfiguration required as per the new module.
Solution : Filter out SAP ID / Sector ID / BAND and check Connect BOARD ID / Connect Port ID / ANT ID is available then UPLOAD that SAPID for RET Change. RF Technical Support © Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
14
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
View more...
Comments
