Browse Prior Art Database

Abnormal operation of no response from downstream node in MBMS session start

IP.com Disclosure Number: IPCOM000145173D
Published in the IP.com Journal: Volume 7 Issue 1B (2007-02-10)
Included in the Prior Art Database: 2007-Feb-10
Document File: 3 page(s) / 27K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

In the 3GPP (3GPP: Third Generation Partnership Project), a simple description is to involve the MBMS (MBMS: Multimedia Broadcast Multicast Service) Session Start procedure. The BM-SC (BM-SC: Broadcast Multicast. - Service Center) initiates the MBMS Session Start procedure when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs (UE: User Equipment) of the imminent start of the transmission. Through this procedure, MBMS session attributes such as QoS (QoS: Quality of Service), MBMS service Area, estimated session duration, time to MBMS data transfer, are provided to the GGSN(s) (GGSN: Gateway GPRS Support Node) and SGSN(s) (SGSN: Serving GPRS Support Node) that have previously registered for the corresponding MBMS bearer service and to all BSCs/RNCs (BSC: Base Station Controller; RNC: Regional Node Centers) that are connected to a registered SGSN.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

S

Abnormal operation of no response from downstream node in MBMS session start

Idea: Jing He, CN-Beijing; Ying Liu, CN-Beijing

In the 3GPP (3GPP: Third Generation Partnership Project), a simple description is to involve the MBMS (MBMS: Multimedia Broadcast Multicast Service) Session Start procedure. The BM-SC (BM- SC: Broadcast Multicast. - Service Center) initiates the MBMS Session Start procedure when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs (UE: User Equipment) of the imminent start of the transmission. Through this procedure, MBMS session attributes such as QoS (QoS: Quality of Service), MBMS service Area, estimated session duration, time to MBMS data transfer, are provided
to the GGSN(s) (GGSN: Gateway GPRS Support Node) and SGSN(s) (SGSN: Serving GPRS Support Node) that have previously registered for the corresponding MBMS bearer service and to all BSCs/RNCs (BSC: Base Station Controller; RNC: Regional Node Centers) that are connected to a registered SGSN.

In some cases, the upstream nodes initiate MBMS Session Start procedure, but do not receive the MBMS session start response message from downstream node. There are two possible cases: One is that the downstream node does not receive the MBMS session start request message from the upstream node. This means that the message is lost in down direction and no response is launched in downstream node. The other possibility is that the downstream node sends the MBMS session start response message, but the upstream node does not receive it. Hereby the message is lost in up direction. For each node, these errors are occasional not regular but can not be excluded in practice.

A solution is introduced by the following to keep MBMS session setup correctly to avoid the release of resources. For the idea it is necessary to set a timer. If the node that sends a MBMS session start request message does not receive one response message before the timer is expired, the node keeps on sending the same MBMS session start request message to downstream node and waits for a response message. For each request message, the same timer should be set in the node, to judge whether...