1 / 3

Load balancing capability - Harmonized among Samsung/NSN/Motorola

Load balancing capability - Harmonized among Samsung/NSN/Motorola. Jaejeong(Brian) Shim, Giovanni Maggi, Joseph Schumacher. Problem.

gabby
Download Presentation

Load balancing capability - Harmonized among Samsung/NSN/Motorola

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Load balancing capability - Harmonized among Samsung/NSN/Motorola Jaejeong(Brian) Shim, Giovanni Maggi, Joseph Schumacher

  2. Problem • When a BS cannot support an MS trying initial network entry, HO, or reentry from idle mode, it has to move the MS to another BS which can support the MS. However, current specification does not support the operation. • BS can use RNG-RSP (with ranging status=abort) or DREG-CMD (with action code = 00), but they cannot designate specific target BS to the MS. • BS can use the ‘Downlink frequency override’ TLV. But the TLV cannot designate a specific BS and it is not available when reuse factor = 1. • Even though MS can obtain the Service level prediction of each target BS during handover, the system load of target BS may change when the MS moves to the BS. • Current Draft specification allows the MS to scan and to initiate at any time handover to target cells different from the ones indicated by the serving BS. Moreover MS can execute handover without even notifying the target BSID to the BS. • Such behavior may lead to conflicting decisions between MS and the BS.

  3. Proposal • Load balancing initiated by BS • RNG-RSP with a Preamble Index Override TLV • Preamble Index(es) of new target BS(s) where the MS should redo ranging. • unsolicited SCN-RSP (with Report mode=0b10, Event-triggered report)followed by BSHO-REQ message • BS-initiated HO (Rejection of service flow creation) • Constrain ping-pong as a consequence of load balancing • Ranging Abort Timer in RNG-RSP message • Timer defined by BS to prohibit network entry of an MS for specific time duration. The MS that received the Ranging Abort Timer in RNG-RSP message shall not try network entry to the BS before the timer expires. • BS_Controlled_HO flag and its operation • A flag in HO type support TLV of DCD message • If BS_Controlled_HO flag is set to 1 • HO notification is mandatory. • HO to one of BSs specified in MOB_BSHO-RSP is required.

More Related