Research Article Model Aspects of Open Access to

Research ArticleModel Aspects of Open Access to MultimediaBroadcast Services in the Evolved Packet System

Ivaylo Atanasov and Evelina Pencheva

Technical University of Sofia 8 Kliment Ohridski Boulevard 1000 Sofia Bulgaria

Correspondence should be addressed to Evelina Pencheva enptu-sofiabg

Received 23 October 2015 Revised 29 December 2015 Accepted 6 January 2016

Academic Editor Hwang JN

Copyright copy 2016 I Atanasov and E PenchevaThis is an open access article distributed under the Creative Commons AttributionLicense which permits unrestricted use distribution and reproduction in any medium provided the original work is properlycited

Multimedia broadcast is the most efficient method to distribute identical content to multiple users in the Evolved Packet System(EPS) EPS enables efficient usage of network resources and provisioning of quality of service for every user Third-party controlallows applications in an enterprise domain to invoke network functions like multimedia broadcast In this paper an approach tomodeling the behavior of ServiceCapability Server (SCS) formultimedia broadcast in EPS is presentedThird-party applications canaccess multimedia broadcasting capabilities by using Parlay X Web Service interfaces The SCS for multimedia broadcast exposesParlay X interfaces toward 3rd-party applications and control protocols toward the network The SCS functional behavior has tobe synchronized with the application view on message broadcast and the state of the network resources intended for the broadcastsessionModels ofmulticast session IP connectivity session and bearersrsquo and charging session are proposed and formally describedusing the notation of Label Transition Systems The concept of weak bisimilarity is used to prove that models expose equivalentbehavior that is they are synchronized

1 Introduction

The Evolved Packet System (EPS) is standardized to provideubiquitous access to multimedia services from any enduser device It encompasses both access network and corenetwork The multimedia packet core network plays animportant role in providing superior user experience fromservices and applications It is in charge of provisioningquality of service (QoS) for multimedia bearer services andcharging mechanisms

Multimedia broadcastmulticast service (MBMS) allowsdata to be transmitted to multiple endpoints It allows opti-mizing network resources using a distribution mechanismThe broadcast mode is a unidirectional point-to-multipointtransmission of multimedia data (eg text audio pictureand video) from a single source entity to all users in a broad-cast service area A broadcast service received by the end userdevice involves one or more successive broadcast sessionsA broadcast service might for example consist of a singleongoing session (eg a media stream) or may involve several

intermittent sessions over an extended period of time [1 2]Examples of content appropriate to a distribution schemeare broadcasting TV channels and distribution of area-based multimedia messaging service including commonlyinterested traffic weather or emergency information Thecontent provider (broadcastmulticast source) may providediscrete and continuousmedia as well as service descriptionsand control dataThemultimedia contentmay be provided bya 3rd-party content provider

The broadcast mode is intended to efficiently use EPSresources Current research on MBMS covers differentaspects related to optimisation of radio technology used fordata transmission Relatively low attention is paid on MBMSthird-party control which allows third-party providers froman IT domain to create applications that use network connec-tions streaming messaging and multimedia

In this paper we discuss some model aspects of deploy-ment open access on multimedia message broadcast servicein EPS The open service access allows third-party applica-tions to use broadcast function in the network The Parlay X

Hindawi Publishing CorporationInternational Journal of Digital Multimedia BroadcastingVolume 2016 Article ID 3154801 13 pageshttpdxdoiorg10115520163154801

2 International Journal of Digital Multimedia Broadcasting

Web Services (WS)model provides a high level of abstractionof communication network functions and it facilitates thedevelopment of value added applications

The paper is organized as follows In Section 2 the relatedwork is presented and the novelty of the proposed approachis highlighted In Section 3 the broadcast service architecturein EPS is discussed where the Broadcast Multicast ServiceCentre (BMSC) mediates between third-party applicationsand the network infrastructure Next the Parlay X Mes-sage Broadcast WS functionality is analyzed in Section 4The behavior of BMSC is modeled by formal descriptionsof MBMS session state and message broadcast status inSection 5 In Section 6 it is proved that models consideringQoS and charging aspects of MBMS are synchronized Theconclusion summarizes the contribution

2 Related Work

Research community has studied different architecturalaspects of MBMS deployment in next generation networksIn [3] the authors propose service architecture for effi-cient content delivery based on enhanced MBMS in LTE(Long-Term Evolution) which reduces backhaul traffic Acontext-aware architecture for social networking multimediadistribution which enhances the evolved MBMS systemsby adding usersrsquo situation knowledge on their assessmentsand allows personalized services delivery over optimizednetworks is proposed in [4] In [5] the authors describethe design and implementation of an open-source virtualizedplatform that supports both LTE broadcast services and videostreaming services and analyze service performance

The performance of enhanced MBMS in LTE has beenthoroughly examined in previous researchworks A compari-son of multicastbroadcast services support in LTE-advancedand WiMAX IEEE 80216m is provided in [6] Challengesin supporting multicast services over LTE with particularattention to resource management considered as key aspectsfor efficient provisioning of MBMS services over cellularnetworks are analyzed in [7] In [8] the authors discuss therelationship between LTE evolved MBMS and next gener-ation broadcast television and propose some recommenda-tions aimed at improving efficiency of the respective systemsIn [9] the authors present a compact convenient model forbroadcasting in LTE as well as a set of efficient algorithmsto define broadcasting areas and to actually perform contentscheduling A joint multicastunicast scheduling strategyfor MBMS delivery which improves QoS performance isproposed in [10] In [11] the authors propose a method forforming broadcasting area and assignment of content to themso that radio resources are efficiently exploited and userrequests satisfied In [12] a distributed resource allocationscheme is proposed which includes device-to-device com-munication broadcasting groups and minimizes interferencerelationships In [13]MBMSwith inherently low requirementfor network resources as a candidate solution for using suchresources in a more efficient manner is proposed Highlevel considerations related to implementation of a sessioncontroller supporting application programming interfacesfor message broadcastingmulticasting can be found in [14]

The proposed solutions have to be implemented by thetelecom network operator We study another multimediabroadcasting issue that has been scarcely addressed so farnamely third-party control which allows external applica-tions outside the network to control service provisioningOur research is focused on two standardized technologieswhose synergy has not been studied to date The Parlay XWS is technology aimed at providing a horizontal servicearchitecture which may be shared by different applications Itdefines highly abstracted technology neutral application pro-gramming interfaces (APIs) Integration ofMBMS andParlayX requires translation of high level interfaces into telecom-munication control protocols The innovative approach toefficient MBMS provisioning requires considering also otheradvanced network functions such as policy-based quality ofservice control and flexible charging We examine how threedifferent functions in EPS related to multimedia broadcast-ing policy and charging control and third-party control cancollaborate and take the advantage of network convergence inprovisioning of value added services

3 Broadcast Service Architecture in EPS

Different broadcast business cases may be considered andthe relevance of each used case is up to network operatorsand their relationship with the content owners agenciesand broadcasters Used case examples include mobile TVdigital radio video on demand electronic magazines andnewspapers and configuration and management of intelli-gent objects with internet connectivity

As to 3GPP TS 23246 the components of the 3GPPsolution of MBMS are MBMS bearer service and MBMSuser service The MBMS bearer service enables efficientdistribution of content to multiple users while MBMS userservice is used by user devices when specific end userapplications are activatedThe architecture of MBMS for EPSwith the proposed third-party control is depicted in Figure 1

The multimedia content that has to be broadcasted isprovided by an Application Sever (AS) The MBMS AS maybe deployed by network operator or third-party applicationprovider The Broadcast Multicast Service Centre (BMSC)stores multimedia content to be transmitted controls themultimedia broadcast service and interacts with mediasources and the end usersrsquo devices via Packet Data NetworkGateway (PDNGW) It provides interfaces for both signalingand data transfer to the MBMS GW The MBMS Gateway(GW) distributes the data received from the BMSC to therelevant base stations in the access network The MobilityManagement Entity (MME) communicates with the accessnetwork in the concerned area relaying session controlinformation received by MBMS GW [15]

The end users discover the available MBMS services byservice announcement which provides information aboutservices Service announcement is used to distribute to usersinformation about MBMS service activation parameterslike IP multicast address and service start time Serviceannouncement mechanisms may include short messagebroadcasting MBMS broadcasting or multicasting mode

International Journal of Digital Multimedia Broadcasting 3

Access network

Evolved packet core

MBMS GW BMSC

MME PCRF OCSCDF

PDN GW

Third-partyapplication server(content provider)

Figure 1 Reference architecture of MBMS for EPS

and a push mechanism Service announcement details maybe found in [16]

An MBMS service may contain multiple distinct multi-media streams and it is provided by session setup and ter-mination Each session is bundled with bearer establishmentand release Signaling procedures related to MBMS sessioninitiation update and termination are specified in [15]

In EPS the network controls QoS parameters for sessionbroadcast MBMS bearer services QoS Class Identifier Allo-cation andRetention PriorityMaximumBit Rate (MBR) andGuaranteed Bit Rate (GBR) are applicable to MBMS bearerservice where the MBR is set to be equal to the GBR TheQoS management in EPS is provided by means of policy andcharging control (PCC) which allows network operator toauthorize and control the usage of resources intended formultimedia traffic [17] PCC ensures thatmultimedia servicesare provided with appropriate transport and charging ThePolicy and Charging Rule Function (PCRF) encompassespolicy control decision and flow based charging controlfunctions It receivesMBMS session information fromBMSCas well as information from the access network and makespolicy-based decisions about bearer service session whichare then provided to the MBMS GW The PCC decisionsdetermine the QoS treatment of the bearer traffic

Both MBMS content provider and MBMS user may becharged for multimedia broadcasting sessions EPS providesoffline and online charging mechanisms [18] The BMSCcontains triggers that generate events for online and offlinecharging The Online Charging System (OCS) performsreal-time credit control and its functionality includes trans-action handlings online correlation and management ofuser account balances The Charging Data Function (CDF)receives offline charging information fromBMSC and createscall detail records

4 Parlay X Message Broadcast Web Service

The Parlay X Message Broadcast WS (MBWS) allows third-party applications to send messages to end user devicesin a specific geographical area [19] It provides APIs forsending a broadcast message to the network for monitoringthe delivery status of a sent broadcast message and fornotifications about the message delivery status

The sendBroadcastMessage operation is used to send abroadcast message into the designated area(s)

The getBroadcastStatus operation is used by the 3rd-partyapplication to retrieve the status of sent broadcast messageThe broadcast status values are as follows

(i) MessageWaiting The message is still queued and notdelivered to the network yet

(ii) Broadcasting The message is being broadcasted asmany as requested in the send operation

(iii) Broadcasted The message is successfully delivered tonetwork as many as requested

(iv) BroadcastImpossible This indicates a final state thatdelivery of broadcast message is impossible due tospecific reasons

(v) BroadcastUnknown The message delivery state isunknown

Figure 2 illustrates the MBMS time line and the message sta-tus as seen by 3rd-party applicationThe cancelBroadcastMes-sage operation may be used by the third-party applicationto cancel message broadcasting The operation affects thesubsequent broadcast message delivery

The notifyBroadcastDeliveryReceipt operation is used tonotify the third-party application about the delivery statusof the message In order to receive notification the third-party application needs to start notifications using startDe-liveryReceiptNotification operation The application may endthe receipt of notifications using the stopDeliveryReceiptNoti-fication operation

Wepropose amodifiedmodel compared to that presentedin [19] which is shown in Figure 3 In Null state there is nomessage to be broadcasted As far as the BroadcastUnknownstate is of temporary kind it is absorbed by the BroadcastIm-possible and Broadcasting states

5 Model Aspects of BroadcastMulticast Service Centre

51 Modeling Views on Message Broadcast BMSC needsto communicate with the third-party application using the


Start broadcast service

announcement Local service

activation

Multimedia broadcast service announcement

Session start

Initiation protection

period

Data transfer

Data transfer

Sessionannouncement

Stop broadcast

sendBroadcastMessage(delivery time)

Interval parameter of sendBroadcastMessage

operation

Local service

deactivation

BroadcastingMultimedia

message broadcasting status

service stop

MessageWaiting Broadcasted

Figure 2 Multimedia broadcast service time line and the parameters of sendBroadcastMessage operation

Null

sendBroadcastMessage

Broadcasting

Successful delivery to the network

Broadcasted

Successful completion of repeated messages

getBroadcastStatus

getBroadcastStatus

getBroadcastStatusnotifyBroadcastDeliveryReceipt getBroadcastStatus

notifyBroadcastDeliveryReceipt

stopAnnouncement

MessageWaitingcancelMessage Broadcast

unableToDeliver

stopAnnouncement BroadcastImpossible

Figure 3 Message broadcast state model

Parlay X MBWS Toward the network BMSC has to com-municate with MBMS GW to maintain the MBMS sessionPCRF to provide information about the MBMS session andto receive notifications about bearers authorized for thesession andCDF to send charging dataTherefore the BMSCbehavior has to be synchronized with the behavior of MBMSGW PCRF and CDF and its view on the MBMS session hasto be synchronized with the application view on the state ofmessage broadcast MBMS GW is in charge of establishmentof IP-CAN resources for the MBMS session where IP-CANstands for Internet Protocol Connectivity Access NetworkPCRF controls the QoS that has to be assured for the MBMSsession and CDF gathers charging data

Figure 4 shows the respective state models that haveto be synchronized with the BMSC behavior The BMSChas to transform the MBWS operations and to control

Third-partyapplication

Message broadcast state

model

MBMS gatewayIP-CAN

session state model

PCRFMBMS QoS resource state

model

CDFOCSMBMS

charging session state model

BMSC

MBMS sessionstate model

Figure 4 Synchronization of MBMS state models in the networkand the 3rd-party application view on the message broadcast state


Message broadcast

application

Device(user

equipment)

Session start request

Session start response Session start request

MBMS data

CDFPCRF BMSC MMEMBMS Gateway

Service info

Ack

Access network


Session start responseSession start

responseEstablish bearer

resources

Charging data request

Charging data response

MBMS data

Session stop response

Session stop request





Indication for IP-CANsession modification

Ack

Session stoprequest

Session stopresponse

Release bearerresources

Indication for IP-CANsession termination

Ack

Provision Ack

MBMS data


startDeliveryReceiptNotification


stopDeliveryReceiptNotification

Figure 5 Typical message flow illustrating 3rd-party control of MBMS in the network

the MBMS session appropriately In practice the statemodelsof BMSC MBMS GW PCRF and CDF should expose directcorrespondence between the transitions and the informationthey provide that is they have to expose equivalent behavior

The MBMS session state model describes the states ofthe MBMS session and it is maintained by MBMS GWThe MBMS QoS provisioning requires an MBMS QoS statemodel reflecting the state of bearer resources allocated byPCRF for the broadcast session The control protocol usedfor PCC is Diameter Similar considerations are applied to theMBMS charging model which holds the states of the MBMScharging session The control protocol used for charging isalso Diameter

Typical information flows related to multimedia mes-sage broadcasting with MBMS session establishment QoSresource authorization notification about message broadcaststatus and reporting offline charging data are shown inFigure 5

The MB WS can be used for remote management ofintelligent devices like smart meters which are uniquelyidentified gather information from their environment andcommunicate that information with network applicationsRemote entity management provides means for managingdevice life cycle including software and firmware upgradeand configuration management With the increasing num-ber of connected devices the device management becomescumbersome and costly for the device operator So an EPSoperator can sell the MBMS to the device operator to keepthe fleet updated TheMBMS can deliver all the software andfirmware updates as well as configurations needed to managethe devices up to date

It is a general assumption that IP connectivity is providedto all devices which means that for each device there isan established default bearer Let us assume that the deviceoperator makes use of a message broadcast application Byusing the application the device operator sets the target area


where the devices are deployed and writes a message withconfiguration data Then the message broadcast applicationinvokes the MB WS which in turn sends a message deliveryoperation to the BMSC Subsequently EPS functional entitiessupporting MBMS deliver the configuration data to alldevices in the target area

When the message broadcast application invokes send-BroadcastMessage operation the BMSCopens aDiameter ses-sion with the PCRF for the multimedia broadcast session andprovides the required session information The BMSC cansubscribe to QoS events related to MBMS bearer resourcesThe BMSC performs the MBMS session start procedureThe MBMS GW in turn indicates to the PCRF that an IP-CAN session modification is required and waits for PCCrules Based on session information the PCRF performssession authorization and sends an acknowledgement withthe PCC decisions to the MBMS Gateway The MBMS startsresources reservation in the access network When the IP-CAN session modification is completed the MBMS GWsends acknowledgement to the PCRF The BMSC waits forresource authorization and reservation during the initialprotection period and the message broadcast status is Mes-sageWaiting Before starting the MBMS data transfer theBMSC contacts with the CDF in order to provide charginginformation The MBMS content is sent by the BMSC tothe MBMS gateway and then to the respective part ofaccess network During the MBMS data transfer the messagebroadcast status is Broadcasting The broadcasted content isreceived and decoded by the devices (user equipment) thatare authorized to join the MBMS service Using the messagebroadcast application and the interfaces of the MBWS thedevice operator can subscribe for notifications aboutmessagedelivery (startDeliveryReceiptNotification operation) and benotified of a broadcast delivery status of a specific area Oncethe MBMS data (configuration data) are broadcasted theBMSC starts the procedure for session termination whichis followed by release of bearer resources authorized for theMBMS session The BMSC contacts with the CDF to writethe charging data The message broadcast status becomesBroadcasted The stopDeliveryReceiptNotification operation isused to end delivery receipt notificationThe content provideris charged for the broadcasted contentThePCRF enables alsoQoS-based charging The PCC mechanism supports trafficplane event reporting (eg bearer lost) which may reflect incharging In case of active subscription the PCRFmay notifythe BMSC about any QoS events occurring during messagebroadcasting

In the course of service provisioning the BMSC needsto maintain in a synchronized manner three state machinesdescribing the MBMS session QoS resources authorized forthe session and charging session These state machines haveto be synchronized with the application view on the states ofthe message broadcast

On receiving an indication about IP-CAN session mod-ification the PCRF may reject the requested modification(due to overloading in the respective access network orspending credit limits of the content provider in case of onlinecharging) In this case the PCRF rejects the IP-CAN sessionmodification requested by the MBMS GW and notifies the

BMSC about the event during the initial protection periodThe message broadcast status becomes BroadcastImpossibleDuring message waiting or broadcasting the device operatormay decide to cancel message broadcast In this case thethird-party application invokes the cancelBroadcastMessageoperation to request cancelation of the previous sendBroad-castMessage The BMSC in turn initiates session terminationtoward the MBMS GW and PCRF which results in IP-CANsession termination and release of QoS resources

In the next subsection we provide formal descriptionof the models representing the view on message broadcastof third-party application BMSC MBMS GW PCRF andCDF respectivelyThis will be used to prove formally that themodels are synchronized

52 Formal Description of Models Representing MessageBroadcast Status Let us present the state machines as labeledtransition systems (LTS)

Definition 1 A labeled transition system (LTS) is a quadruple(119878 119860119888119905rarr 119904

0) where 119878 is countable set of states 119860119888119905 is a

countable set of elementary actionsrarrsube 119878 times 119860119888119905 times 119878 is a setof transitions and 119904

0isin 119878 is the set of initial states

521 Application View on Message Broadcast Status Themessage broadcast status from application point of view maybe Null MessageWaiting Broadcasting or Broadcasted Thestatus is Null when there is no message to be broadcastedThe status is MessageWaiting if the message is waiting tobe delivered to the network The status is Broadcastingor Broadcasted if the MBMS data transfer is ongoing orterminated respectively

By 119879App = (119878App 119860119888119905ApprarrApp 1199040App) an LTS represent-

ing the 3rd-party view on the message broadcast status isdenoted where

(i) 119878App = Null MessageWaiting Broadcasting Broad-casted BroadcastImpossible

(ii) 119860119888119905App = sendMessage getBroadcastStatus notify-BroadcastDeliveryReceipt cancelMessage success-fulDelivery unsuccessfulDelivery stopAnnounce-ment unableToDeliver successfulMessageComple-tion

(iii) rarrApp = Null sendMessage MessageWaiting Mes-sageWaiting getBroadcastStatus MessageWaitingMessageWaiting unsuccessfulDeliveryNullMessage-Waiting successfulDelivery Broadcasting Message-Waiting cancelMessage Null MessageWaiting unab-leToDeliver BroadcastImpossible Broadcasting suc-cessfulMessageCompletion Broadcasted Broadcast-ing cancelMessage Null Broadcasting getBroadcast-Status Broadcasting Broadcasted stopAnnounce-ment Null Broadcasted getBroadcastStatus Broad-casted Broadcasted notifyBroadcastDeliveryReceiptBroadcasted BroadcastImpossible getBroadcastSta-tus BroadcastImpossible BroadcastImpossible noti-fyBroadcastDeliveryReceipt BroadcastImpossibleBroadcastImpossible stopAnnouncement Null

(iv) 1199040

App= Null


The getBroadcastStatus and notifyBroadcastDeliveryReceiptoperations do not change the session state or messagebroadcast status

522 BMSC Model of MBMS Session The simplified BMSCview on the MBMS session states includes the followingstates In MBMSIdle state there is no MBMS session Whenthe application invokes the sendBroadcastMessage operationthe BMSC sends session information to the PCRF a sessionstart request to theMBMSGW and it moves to InitialWaitingstate While being in InitialWaiting state the BMSC waitsfor resource authorization andQoS resource reservationThetime delay between a session start indication and actual datashould be long enough for the required network actionsWhen the network is ready to send MBMS data the BMSCsends charging data and moves to DataTransfer state InDataTransfer state MBMS data are transferred to any userequipment which is present When the MBMS user servicedetermines that there are no more data to send the BMSCinitiates session termination sends charging data andmovesto MBMSIdle state In InitialWaiting or DataTransfer statethe BMSC may be notified about any problems related toMBMS bearers and the MBMS session is terminated Itis also possible for third-party application to invoke thecancelBroadcastMessage operation while the BMSC is in Ini-tialWaiting or DataTransfer state which cancels the MBMSsession

By 119879BMSC = (119878BMSC 119860119888119905BMSCrarrBMSC 1199040BMSC) an LTS

representing the BMSC view on the message broadcast statusis denoted where

(i) 119878BMSC = MBMSIdle InitialWaiting DataTransfer(ii) 119860119888119905BMSC = sendBroadcastMessage initialPeriod

dataTransferStop resourceFailed resourceLost can-celBroadcastMessage

(iii) rarrBMSC = MBMSIdle sendBroadcastMessage Ini-tialWaiting InitialWaiting initialPeriod DataTrans-fer InitialWaiting resourceFailed MBMSIdle Initial-Waiting cancelBroadcastMessage MBMSIdle Data-Transfer dataTransferStop MBMSIdle DataTransferresourceLost MBMSIdle DataTransfer cancelBroad-castMessage MBMSIdle

(iv) 1199040

BMSC= MBMSIdle

Figure 6 illustrates the MBMS session state machine

523 MBMS GWModel of IP-CAN Session TheMBMS GWview on the IP-CAN session states for theMBMS user serviceincludes the following states In IPCANIdle state there is nodedicated IP-CAN sessionOn receiving session start instruc-tions the MBMS GW indicates an IP-CAN session modi-fication to the PCRF and moves to WaitForPCCRules stateInWaitForPCCRules state theMBMSwaits for authorizationof IP-CAN session modification Upon receiving the PCCrules theMBMSGW initiates IP-CAN session establishmentin the access network and moves to ResourceReservationstate The MBMS GW moves to SessionActive state after itreceives an acknowledgement that the resources in the access

MBMSIdle

InitialWaiting


DataTransfer

initialPeriod

cancelBroadcastMessagedataTransferStop

resourceFailed

resourceLost

cancelBroadcastMessage

Figure 6 MBMS session state machine

network are reserved The transition to ResourceRelease stateoccurs when a session stop request is received by the BMSCIn ResourceRelease state the MBMS waits for the releaseof IP-CAN bearers In WaitForTermAck state the MBMSGW waits for acknowledgement for session terminationfrom PCRF and then moves to the initial IPCANIdle stateIn ResourceReservation or SessionActive state network theMBMS GWmay receive indications from the PCRF that thebearer modification fails or that the bearers are lost Thesecause the transition to IPCANIdle state

By 119879MBMS = (119878MBMS 119860119888119905MBMSrarrMBMS 1199040MBMS) an LTS

representing the MBMS GW view on the MBMS IP-CANsession state is denoted where

(i) 119878MBMS = IPCANIdle WaitForPCCRules Resour-ceReservation SessionActive ResourceReleaseWait-ForTermAck

(ii) 119860119888119905MBMS = sessionStart pccRules ipCanBear-erEstablishment sessionStop sessionCancel ipCan-BearerRelease ipCanSessionTermAck ipCanBear-erFailed ipCanBearerLost

(iii) rarrMBMS = IPCANIdle sessionStart Wait-ForPCCRules WaitForPCCRules pccRules Resour-ceReservation WaitForPCCRules sessionCancel IP-CANIdle ResourceReservation ipCanBearerEsta-blishment SessionActive ResourceReservation ses-sionCancel IPCANIdle ResourceReservation ip-CanBearerFailed IPCANIdle SessionActive session-Cancel ResourceRelease SessionActive session-Stop ResourceRelease SessionActive ipCanBearer-Lost IPCANIdle ResourceRelease ipCanBearerRe-lease WaitForTermAck WaitForTermAck ipCanSes-sionTermAck IPCANIdle

(iv) 1199040

MBMS= IPCANIdle

The IP-CAN session state machine is depicted in Figure 7

524 PCRF Model of MBMS QoS Resources The PCRF viewon the state of QoS resource intended for MBMS session isas follows In ResourceNull state no QoS resources are autho-rized for the MBMS session When the BMSC sends sessioninformation the PCRF performs session binding which takesinto account the IP-CAN parameters and moves to IPCanS-ession state storing this information In IPCanSession statethe PCRF may receive an indication about IP-CAN session


IPCANIdle

sessionStart

pccRules

ipCanBearerRelease

ipCanBearerEstablishment

SessionActive

sessionCancel sessionStop

ipCanBearerLost

ipCanSessionTermAck

WaitForPCCRulessessionCancelipCanBearerFailed

ResourceReservation

ResourceRelease

WaitForTermAck

Figure 7 IP-CAN session state machine

modification and correlates appropriate service informationwith IP-CAN session InResourceAuthorizing state the PCRFmakes policy decisions and sends them as PCC rules to theMBMS GW On receiving provision acknowledgement thePCRF moves to ResourceAuthorized state The QoS resourcesfor the MBMS session are authorized and reserved andthe MBMS data transfer can start When the MBMS GWdetects that the IP-CAN session termination is required itsends an indication to the PCRF In case of subscriptionthe PCRF may find the PCC rules that require the BMSCto be notified and sends a notification The QoS resourcesauthorized for the MBMS session are released which causesthe transition to ResourceNull state In ResourceAuthorizingstate the PCRF may decide to reject the IP-CAN sessionmodification Also during MBMS data transfer any QoSproblems may be reported by the MBMS GW to the PCRFthus affecting the online charging In case the MBMS GWreports that all bearer resources authorized for the MBMSsession are lost the PCRF moves to ResourceNull state

By 119879PCRF = (119878PCRF 119860119888119905PCRFrarrPCRF 1199040PCRF) an LTS

representing the PCRF GW view on the QoS resource stateis denoted where

(i) 119878PCRF = ResourceNull IPCanSession ResourceAu-thorizing ResourceAuthorized

(ii) 119860119888119905PCRF = sessionInfo ipCanSessionModificationprovisionAck provisionNonAck ipCanSessionTer-mination ipCanBearerRemoved ipCanSessionCan-cel

(iii) rarrPCRF = ResourceNull sessionInfo IPCanSessionIPCanSession ipCanSessionModification Resour-ceAuthorizing IPCanSession ipCanSessionTermina-tion ResourceNull ResourceAuthorizing provision-Ack ResourceAuthorized ResourceAuthorizing

ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved

ipCanSessionCancel provisionNonAck

ipCanSessionCancel

ipCanSessionTermination

ipCanSessionModification

ResourceAuthorizing

ResourceAuthorized

Figure 8 QoS resource state machine

ipCanSessionCancel ResourceNull ResourceAuthor-izing provisionNonAck ResourceNull ResourceAu-thorized ipCanSessionCancel ResourceNull Resour-ceAuthorized ipCanBearerRemoved ResourceNull

(iv) 1199040

PCRF= ResourceNull

Figure 8 illustrates the QoS resource state machine

525MBMSCharging SessionModel Both offline and onlinecharging are possible By applying policy and chargingcontrol on MBMS sessions online charging can reflect theQoS experience during message broadcasting The BMSCcollects charging data such as identification of the contentsource type of user service type of bearer resources usedto deliver the content broadcast and identification of usersreceiving the service The BMSC collects also chargingdata such as session duration data transfer time and datavolume formobile users receiving the service throughMBMSandor content providers delivery of the MBMS contentThe triggers for charging data are bearer service initiationand termination In ChargingIdle state no charging dataare gathered Charging data are provided by the BMSCupon MBMS session initiation IP-CAN bearer resourceestablishmentfailure and MBMS session termination Thecharging data are sent to the CDF (in case of offline charging)or to the Online Charging System On receiving chargingdata related to session start the charging session moves to119860119888119905119894V119890initial state In 119860119888119905119894V119890initial state when charging datafor IP-CAN session establishment are received the chargingsession moves to 119860119888119905119894V119890transfer state The charging data stopinstructions may be received due to normal completion ofmessage broadcast due to some problems in the networkor due to message broadcast cancelation by the third-partyapplication On receiving charging data stop instructions thecharging session moves to ChargingIdle state

By 119879CS = (119878CS 119860119888119905CSrarrCS 1199040CS) an LTS representing the

charging session states is denoted where

(i) 119878CS = ChargingIdle Activeinitial Activetransfer


(ii) 119860119888119905CS = chargingDataStartinit chargingData-Startinterim chargingDataStopnormal chargingDataS-topcanceled chargingDataStopfailed

(iii) rarrCS = ChargingIdle chargingDataStartinitActiveinitial Activeinitial chargingDataStartinterimActivetransfer Activetransfer chargingDataStopnormalChargingIdle Activeinitial chargingDataStopfailedChargingIdle Activeinitial chargingDataStopcanceledChargingIdle Activetransfer chargingDataStopcanceledChargingIdle Activetransfer chargingDataStopfailedChargingIdle

(iv) 1199040

CS= ChargingIdle

The charging session state machine is depicted in Figure 9Having formal description of the models representing

message broadcast status as seen by both the third-partyapplication and the network we can prove that these modelsare synchronized that is they expose equivalent behavior

6 Formal Verification of Models

61 Bisimilarity Concept Intuitively in terms of observedbehavior two state machines are equivalent if one statemachine displays a final result and the other state machinedisplays the same result The idea of equivalence is formal-ized by the concept of bisimilarity [20] Strong bisimilarityrequires existence of homomorphism between transitionsin both state machines In practice strong bisimilarity putsstrong conditions for equivalence which are not always nec-essary For example internal transitions can present actionswhich are intrinsic to the system (ie not observable) Inweak bisimilarity internal transitions can be ignored

The concept of weak bisimilarity is used to study somemodel aspects of BMSC

We will use the following notations

(i) 119904 119886997888rarr 1199041015840 stands for the transition (119904 119886 1199041015840)

(ii) 119904 119886997888rarrmeans that exist1199041015840 119904 119886997888rarr 1199041015840

(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861

997888rarr 1199041sdot sdot sdot119886119899

997888rarr 119904119899

(iv) 119904120583

rArrmeans that exist1199041015840 such as 119904120583

rArr 1199041015840

(v)

rArrmeansrArr if 120583 equiv 120591 or120583

rArr otherwisewhere 120591 is one or more internal (invisible) actions

Definition 2 Two labeled transition systems119879 = (119878 119860rarr 1199040)

and 1198791015840 = (1198781015840 119860rarr1015840 11990410158400) are weakly bisimilar (119879 sim 1198791015840) if there

is a binary relation 119880 sube 119878 times 1198781015840 such that if 11990411198801199051 1199041sube 119878 and

1199051sube 1198781015840 then forall119886 isin 119860119888119905

(i) 1199041

119886

rArr 1199042implies exist119905

2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886

rArr10158401199052implies exist119904

2 1199041

119886

rArr 1199042and 11990421198801199052

So in order to prove that considered LTS expose equivalentbehavior it is necessary to identify a relation between theirstates that satisfies the above conditions

ChargingIdle

chargingDataStopcanceledchargingDataStopfailed


chargingDataStopnormal

chargingDataStartinit

Activeinitial

Activetransfer

chargingDataStartinterim

Figure 9 Charging session state machine

62 Equivalence of Models Representing MessageBroadcast Status

621 Behavioral Equivalence between Models of IP-CANSession and QoS Resources It can be shown that the MBMSGWmodel ofMBMS session andPCRFmodel ofMBMSQoSresources provide the lower level of abstraction so we willstart with considering the synchronization aspects of thesemodels

Proposition 3 The labeled transition systems 119879MBMS and119879PCRF are weakly bisimilar

Proof To prove the bisimilarity between two labeled transi-tion systems it has to be proved that there exists a bisimilarrelation between their states By 119880MP a relation between thestates of 119879MBMS and 119879PCRF is denoted where

119880MP = (IpCANIdle ResourceNull) (Wait-ForPCCRules IpCanSession) (ResourceReservationResourceAuthorizing) (SessionActive ResourceAu-thorized)

The following homomorphism based on functional mappingmay be defined between transitions of 119879MBMS and 119879PCRF

ℎMP(sessionStart) = ℎMP(sessionInfo)ℎMP(pccRule) = ℎMP(ipCanSessionModification)ℎMP(ipCanBearerEstablishment) = ℎMP(provision-Ack)ℎMP(sessionStop) = ℎMP(ipCanSessionTermination)ℎMP(sessionCancel) = ℎMP(ipCanSessionCancel)ℎMP(ipCanBearerFailed) = ℎMP(provisionNonAck)ℎMP(ipCanBearerLost) = ℎMP(ipCanBearerRe-moved)

The homomorphism between the 119879MBMS and 119879PCRF messagesshows the actionrsquos similarity

Table 1 represents the functional mapping between thetransitions in the IP-CAN session state machine and transi-tions in the QoS resources state machine

Based on the established relation between the states of119879MBMS and 119879PCRF and on the homomorphism ℎMP between


Table 1 Functional mapping between transitions of 119879MBMS and 119879PCRF

Transitions in 119879MBMS Transitions in 119879PCRF EventIPCANIdle sessionStartWaitForPCCRules

ResourceNull sessionInfoIPCanSession MBMS session initiation

WaitForPCCRules pccRulesResourceReservation

IPCanSessionipCanSessionModification

ResourceAuthorizing

IP-CAN sessionmodification request

ResourceReservationipCanBearerEstablishmentSessionActive

ResourceAuthorizingprovisionAck

ResourceAuthorized

IP-CAN sessionmodification authorization

SessionActive sessionStopResourceReleaseResourceReleaseipCanBearerReleaseWaitForTermAckWaitForTermAckipCanSessionTermAckIPCANIdle

ResourceAuthorizedipCanSessionTermination

ResourceNullMBMS session stop

ResourceReservationipCanBearerFailed IPCANIdle

ResourceAuthorizingprovisionNonAckResourceNull


fails

SessionActive ipCanBearerLostIPCANIdle

ResourceAuthorizedipCanBearerRemoved

ResourceNull

All bearers are lost duringdata transfer

ResourceReservationsessionCancel IPCANIdle

ResourceAuthorizedipCanSessionCancel

ResourceNull

The application cancels theMBMS user service during

resource reservation

WaitForPCCRules sessionCancelIPCANIdle

IPCANSessionipCanSessionCancel

ResourceNull

The application cancels theMBMS user service duringresource authorization

SessionActive sessionCancelResourceReleaseResourceReleaseipCanBearerReleaseWaitForTermAckWaitForTermAckipCanSessionTermAckIPCANIdle


ResourceNull


data transfer

their transitions it is proved that119879MBMS sim 119879PCRF that is theyare weakly bisimilar and expose equivalent behavior

622 Equivalence of Models of MBMS Session IP-CANSession and QoS Resources A higher level of abstraction onthe network resource state for MBMS is provided by the stateof MBMS session

Proposition 4 The labeled transition systems 119879BMSC 119879MBMSand 119879PCRF are weakly bisimilar

Proof The weak bisimilarity has the property transitivitythat is as a relation it is transitive Then having proved that119879MBMS sim 119879PCRF it has to be proved that 119879BMSC sim 119879MBMS

By 119880BMP a relation between the states of 119879BMSC 119879MBMSand 119879PCRF is denoted where119880BMP = (MBMSIdle IpCANIdle) (InitialWaitingWaitForPCCRules) (DataTransfer SessionActive)

The following homomorphism based on functional mappingmay be defined between transitions of 119879BMSC 119879MBMS and119879PCRF

ℎBMP(sendBroadcastMessage) = ℎBMP(sessionz-Start) = ℎBMP(sessionInfo)

ℎBMP(initialPeriod) = ℎBMP(pccRule) = ℎBMP(ip-CanSessionModification)

ℎBMP(dataTransferStop) = ℎBMP(sessionStop) =ℎBMP(ipCanSessionTermination)

ℎBMP(cancel) = ℎBMP(sessionCancel) = ℎBMP(ip-CanSessionCancel)

ℎBMP(resourcesFailed) = ℎBMP(ipCanBearerFailed) =ℎBMP(provisionNonAck)

ℎBMP(resourcesLost) = ℎBMP(ipCanBearerLost) =ℎBMP(ipCanBearerRemoved)


Table 2 Functional mapping between transitions of 119879BMSC and 119879MBMS

Transitions in 119879BMSC Transitions in 119879MBMS EventMBMSIdlesendBroadcastMessageInitialWaiting

IPCANIdle sessionStartWaitForPCCRules MBMS session initiation

InitialWaiting initialPeriodDataTransfer

WaitForPCCRulespccRules

ResourceReservationResourceReservation

ipCanBearerEstablishmentSessionActive

IP-CAN session modificationrequest

IP-CAN session modificationauthorization

DataTransferdataTransferStopMBMSIdle

SessionActive sessionStopResourceReleaseResourceRelease

ipCanBearerReleaseWaitForTermAckWaitForTermAck

ipCanSessionTermAckIPCANIdle

MBMS session stop

InitialWaiting resourceFailedMBMSIdle

ResourceReservationipCanBearerFailed

IPCANIdle

IP-CAN session modificationauthorization fails

DataTransfer resourceLostMBMSIdle

SessionActiveipCanBearerLost

IPCANIdle

All bearers are lost during datatransfer

InitialWaitingcancelBroadcastMessageMBMSIdle



The application cancels the MBMSuser service during resource

reservation

DataTransfercancelBroadcastMessageMBMSIdle

SessionActive sessionCancelResourceReleaseResourceRelease




authorization

The functional mapping between the transitions in theMBMS session and IP-CAN state machines represented inTable 2 shows that 119880BMP is a bisimilar relation

From the homomorphism ℎBMP and bisimilar property of119880BMP it follows that 119879BMSC sim 119879MBMS

From the bisimulation transitivity it follows that 119879BMSC sim119879MBMS sim 119879PCRF

This means that MBMS session state machine IP-CANstate machine and the QoS resources state machine areweakly bisimilar

623 Equivalence of Application and Network Models Thehighest level of abstraction on message broadcast status isprovided by 3rd-party application Its view has to be syn-chronized also with the network resource state and chargingsession state

Proposition 5 The labeled transition systems 119879App 119879BMSC119879MBMS 119879PCRF and 119879CS are weakly bisimilar

Proof By119880ABMPC a relation between the states of119879App119879BMSC119879MBMS 119879PCRF and 119879CS is denoted where

119880ABMPC = (Null MBMSIdle IpCANIdle Resour-ceNull ChargingIdle) (MessageWaiting InitialWait-ing WaitForPCCRules IpCanSession Activeinitial)(Broadcasting DataTransfer SessionActive Resour-ceAuthorized Activetransfer)

The following homomorphism based on functional mappingmay be defined between transitions of 119879App 119879BMSC 119879MBMS119879PCRF and 119879CS

ℎABMPC(sendMessage) = ℎABMPC(sendBroadcast-Message) = ℎABMPC(sessionStart) = ℎABMPC(ses-sionInfo) = ℎABMPC(sendBroadcastMessage) =ℎABMPC(chargingDataStartinit)ℎABMPC(successfulDelivery) = ℎABMPCC(initialPeri-od) = ℎABMPC(pccRule) = ℎABMPC(ipCanSession-Modification) = ℎABMPCC(chargingDataStartinterim)


ℎABMPC(successfulMessageCompletion) =

ℎABMPC(dataTransferStop) = ℎABMPC(sessionStop) =ℎABMPC(ipCanSessionTermination) = ℎABMPC(charg-ingDataStopnormal)ℎABMPC(cancelMessage) = ℎABMPC(cancel) =ℎABMPC(sessionCancel) = ℎABMPC(ipCanSession-Cancel) = ℎABMPC(chargingDataStopcanceled)ℎABMPC(unsuccessfulDelivery) = ℎABMPC(resources-Failed) = ℎABMPC(ipCanBearerFailed) =ℎABMPC(provisionNonAck) = ℎABMPC(chargingDat-aStopfailed)

In order to define a weak bisimilar relation between the statesof 119879App 119879BMSC 119879MBMS 119879PCRF and 119879CS we establish the validsequences of ordered transitions from - rarrApp - rarrBMSC -rarrMBMS -rarrPCRF and -rarrCS that correspond to 119880ABMPC

Let 120591App119894sub rarrApp where 119894 isin 1 6 be the following

transition sequences

120591App1= (Null sendMessage MessageWaiting)

120591App2= (MessageWaiting getBroadcastStatus Mes-

sageWaiting MessageWaiting successfulDeliveryBroadcasting)

120591App3= (Broadcasting getBroadcastStatus Broad-

casting Broadcasting successfulMessageCompletionBroadcasted Broadcasted getBroadcastStatus Broad-casted Broadcasted notifyBroadcastDeliveryReceiptBroadcasted Broadcasted stopAnnouncement Null)120591App4= (MessageWaiting unableToDeliver Broad-

castImpossible BroadcastImpossible getBroadcast-Status BroadcastImpossible BroadcastImpossiblenotifyBroadcastDeliveryReceipt BroadcastImpossi-ble BroadcastImpossible stopAnnouncement Null)120591App5= (MessageWaiting cancelMessage Null)

120591App6= (Broadcasting cancelMessage Null)

Let 120591BMSC119894sub rarrBMSC where 119894 isin 1 6 be following


120591BMSC1= (MBMSIdle sendBroadcastMessage Initial-

Waiting)120591BMSC2= (InitialWaiting initialPeriod DataTransfer)

120591BMSC3= (DataTransfer dataTransferStopMBMSIdle)

120591BMSC4= (InitialWaiting resourceFailed MBMSIdle)

120591BMSC5= (InitialWaiting cancelBroadcastMessage

MBMSIdle)120591BMSC6= (DataTransfer resourceLost MBMSIdle)

Let 120591MBMS119894sub rarrMBMS where 119894 isin 1 6 be the following

120591MBMS1

= (IPCANIdle sessionStart WaitForPC-CRules)120591MBMS2= (WaitForPCCRules pccRules ResourceR-

eservation ResourceReservation ipCanBearerEstab-lishment SessionActive)

120591MBMS3= (SessionActive sessionStop ResourceRe-

lease ResourceRelease ipCanBearerRelease Wait-ForTermAck WaitForTermAck ipCanSessionTer-mAck IPCANIdle)120591MBMS4= (ResourceReservation ipCanBearerFailed

IPCANIdle)120591MBMC5

= (WaitForPCCRules sessionCancel IP-CANIdle ResourceReservation sessionCancel IP-CANIdle)120591MBMS6= (SessionActive ipCanBearerLost IPCANId-

le)

Let 120591PCRF119894sub rarrPCRF where 119894 isin 1 6 be the following

120591PCRF1= (ResourceNull sessionInfo IPCanSession)

120591PCRF2= (IPCANSession ipCanSessionModifica-

tionResourceAuthorizing ResourceAuthorizing pro-visionAck ResourceAuthorized)120591PCRF3= (ResourceAuthorized ipCanSessionTermi-

nation ResourceNull)120591PCRF4= (ResourceAuthorizing provisionNonAck Re-

sourceNull)120591PCRF5= (IPCANSession ipCanSessionCancel Re-

sourceNull ResourceAuthorized ipCanSessionCan-cel ResourceNull)120591PCRF6= (ResourceAuthorized ipCanBearerRemoved

ResourceNull)

Let 120591CS119894sub rarrCS where 119894 isin 1 6 be following transition

sequences

120591CS1= (ChargingIdle chargingDataStartinit

Activeinitial)

120591CS2= (Activeinitial chargingDataStartinterim

Activetransfer)

120591CS3= (Activetransfer chargingDataStopnormal

ChargingIdle)

120591CS4= (Activeinitial chargingDataStopfailed ChargingI-

dle)120591CS5= (Activeinitial chargingDataStopcanceled Charg-

ingIdle)

120591CS6= (Activetransfer chargingDataStopcanceled Charg-

ingIdle)

Then based on the defined homomorphism ℎABMPC betweenthe actions of 119879App 119879BMSC 119879MBMS 119879PCRF and 119879CS it fol-lows that for 119880ABMPC the sequences (120591App

119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591

CS119894) for 119894 isin 1 6 agree with Definition 2 for weak

bisimilarityHence the state machines that represent the 3rd-party

application view on message broadcast MBMS sessionIP-CAN session QoS resources and charging session arebisimilar that is these state machines expose equivalentbehavior


7 Conclusion

In EPS there are specific features nodes and interfacesdefined to support broadcasting of content to multiple userssimultaneously Parlay XMessage BroadcastWS allows third-party applications to send messages to all mobile terminalsin a specific geographical area The deployment of 3rd-partycontrol on multimedia broadcasting implies more researchon synergy betweenWS APIs and respective communicationcontrol protocols

The paper presents a study on modeling aspects of anetwork node that mediates between 3rd-party applicationservers and the evolved packet core of a mobile networkIt explores the way the network agnostic WS interfacescollaborate with specific control functionality in order toprovide value added multimedia broadcasting services

The results regard model aspects of the behavior of aService Capability Server namely BMSC which exposes Par-lay X WS interfaces toward applications and ldquotalksrdquo networkprotocols toward the network The focus is on collaborationof different functionalities namely service control sessionmanagement QoS control and charging control In thecontext of message broadcast we modeled the states ofMBMS session IP-CANsessionQoS resources and chargingsession and showed that these models are synchronized withthe 3rd-party application view on message broadcast Theproof is based on functionalmapping between the transitionsin state machines and the identification of a homomorphismbetween actions The concept of weak bisimilarity is usedto prove that the state machines expose equivalent behaviorThus the novelty of contribution might be summarized asmodel definitions and proof for bisimilarity

The utilization of standardized Message Broadcast APIsprovides a unified approach for 3rd-party application man-agement and provisioning It allows development of con-verged multimedia broadcast applications in a way which isindependent of the underlying access technologies

Conflict of Interests

The authors declare that there is no conflict of interestsregarding the publication of this paper

References

[1] D Lecompte and F Gabin ldquoEvolved multimedia broad-castmulticast service (eMBMS) in LTE-advanced overviewand Rel-11 enhancementsrdquo IEEE Communications Magazinevol 50 no 11 pp 68ndash74 2012

[2] J Calabuig J F Monserrat D Gozalvez and O Klemp ldquoSafetyon the roads LTE alternatives for sending ITS messagesrdquo IEEEVehicular Technology Magazine vol 9 no 4 pp 61ndash70 2014

[3] I Stephanasik I Chochliouros G Lymperopoulos and KBerberidis ldquoOptimal video delivery in mobile networks usinga cache-accelerated multi area eMBMS architecturerdquo in Artifi-cial Intelligence Applications and Innovations vol 437 of IFIPAdvances in Information and Communication Technology pp13ndash23 Springer Berlin Germany 2014

[4] F C Pinto N Carapeto A Videira T Frazao and MHomem ldquoContext-aware multimedia distribution to mobile

social communitiesrdquo International Journal of Handheld Com-puting Research vol 4 no 3 pp 63ndash92 2013

[5] CM LentiscoMAguayo L Bellido E Pastor DDe-Antonio-Monte and A G Bolivar ldquoA virtualized platform for analyzingLTE broadcast servicesrdquo in Proceedings of the European Confer-ence on Networks and Communications (EuCNC rsquo15) pp 512ndash516 Paris France June 2015

[6] J Calabuig J Monserrat D Martin-Sacristan and J OlmosldquoComparison of multicastbroadcast services in Long TermEvolution Advanced and IEEE 80216m networksrdquo WirelessCommunications and Mobile Computing vol 14 no 7 pp 717ndash728 2014

[7] G Araniti M Condoluci and A Molinaro ldquoResource man-agement of multicast services over LTErdquo in Convergence ofBroadband Broadcast and Cellular Network Technologies pp77ndash93 IGI Global 2014

[8] G K Walker J Wang C Lo X G Zhang and G Bao ldquoRela-tionship between LTE broadcasteMBMS and next generationbroadcast televisionrdquo IEEE Transactions on Broadcasting vol60 no 2 pp 185ndash192 2014

[9] F Malandrino C Casetti C F Chiasserini and S ZhouldquoReal-time scheduling for content broadcasting in LTErdquo inProceedings of the IEEE International Symposium on ModellingAnalysis amp Simulation of Computer and TelecommunicationSystems pp 126ndash131 Paris France September 2014

[10] A de la Fuente A G Armada and R P Leal ldquoJoint mul-ticastunicast scheduling with dynamic optimization for LTEmulticast servicerdquo in Proceedings of the 20th European WirelessConference (EW rsquo14) pp 462ndash467 Barcelona Spain May 2014

[11] C Borgiattino C Casetti C F Chiasserini and F MalandrinoldquoEfficient area formation for LTE broadcastingrdquo in Proceedingsof the 12th Annual IEEE International Conference on SensingCommunication and Networking (SECON rsquo15) pp 202ndash210IEEE Seattle Wash USA June 2015

[12] CW YehM J Shih G Y Lin andH YWei ldquoLTE-D broadcastwith distributed interference-aware D2D resource allocationrdquoin Proceedings of the 7th International Conference on Ubiquitousand Future Networks (ICUFN rsquo15) pp 165ndash170 Sapporo JapanJuly 2015

[13] Y-H Xu C-O Chow M-L Tham and H Ishii ldquoAn enhancedframework for providing multimedia broadcastmulticast ser-vice over heterogeneous networksrdquo Journal of Zhejiang Univer-sity Science vol 15 no 1 pp 63ndash80 2014

[14] J H Kim S K Kim and B S Lee ldquoMessage service methodand message service systemrdquo US Patent 8478313 B2 2013

[15] 3GPP ldquoMultimedia BroadcastMulticast Service (MBMS)architecture and functional descriptionrdquo 3GPP TS 23246 2015Release 13

[16] 3GPP ldquoMultimedia BroadcastMulticast Service (MBMS) pro-tocols and codecsrdquo 3GPP TS 26346 2015 Release 13

[17] 3GPP TS 23203 ldquoPolicy and Charging control architecturerdquoRelease 13 v1350 2015

[18] 3GPP ldquoTelecommunication management charging manage-ment charging architecture and principlesrdquo 3GPP TS 322402015 Release 13 v1300

[19] 3GPP ldquoOpen Service Access (OSA) parlay X web services part15 message broadcastrdquo 3GPP TS 29199-15 2009 Release 9

[20] L Fuchun Z Qiansheng and C Xuesong ldquoBisimilarity controlof decentralized nondeterministic discrete-event systemsrdquo inProceedings of the 33rd Chinese Control Conference (CCC rsquo14)pp 3898ndash3903 IEEE Nanjing China July 2014

International Journal of

AerospaceEngineeringHindawi Publishing Corporationhttpwwwhindawicom Volume 2014

RoboticsJournal of

Hindawi Publishing Corporationhttpwwwhindawicom Volume 2014


Active and Passive Electronic Components

Control Scienceand Engineering

Journal of



RotatingMachinery


Hindawi Publishing Corporation httpwwwhindawicom

Journal ofEngineeringVolume 2014

Submit your manuscripts athttpwwwhindawicom

VLSI Design



Shock and Vibration


Civil EngineeringAdvances in

Acoustics and VibrationAdvances in



Electrical and Computer Engineering

Journal of

Advances inOptoElectronics


Volume 2014

The Scientific World JournalHindawi Publishing Corporation httpwwwhindawicom Volume 2014

SensorsJournal of


Modelling amp Simulation in EngineeringHindawi Publishing Corporation httpwwwhindawicom Volume 2014


Chemical EngineeringInternational Journal of Antennas and

Propagation




Navigation and Observation



DistributedSensor Networks



Web Services (WS)model provides a high level of abstractionof communication network functions and it facilitates thedevelopment of value added applications

The paper is organized as follows In Section 2 the relatedwork is presented and the novelty of the proposed approachis highlighted In Section 3 the broadcast service architecturein EPS is discussed where the Broadcast Multicast ServiceCentre (BMSC) mediates between third-party applicationsand the network infrastructure Next the Parlay X Mes-sage Broadcast WS functionality is analyzed in Section 4The behavior of BMSC is modeled by formal descriptionsof MBMS session state and message broadcast status inSection 5 In Section 6 it is proved that models consideringQoS and charging aspects of MBMS are synchronized Theconclusion summarizes the contribution

2 Related Work

Research community has studied different architecturalaspects of MBMS deployment in next generation networksIn [3] the authors propose service architecture for effi-cient content delivery based on enhanced MBMS in LTE(Long-Term Evolution) which reduces backhaul traffic Acontext-aware architecture for social networking multimediadistribution which enhances the evolved MBMS systemsby adding usersrsquo situation knowledge on their assessmentsand allows personalized services delivery over optimizednetworks is proposed in [4] In [5] the authors describethe design and implementation of an open-source virtualizedplatform that supports both LTE broadcast services and videostreaming services and analyze service performance

The performance of enhanced MBMS in LTE has beenthoroughly examined in previous researchworks A compari-son of multicastbroadcast services support in LTE-advancedand WiMAX IEEE 80216m is provided in [6] Challengesin supporting multicast services over LTE with particularattention to resource management considered as key aspectsfor efficient provisioning of MBMS services over cellularnetworks are analyzed in [7] In [8] the authors discuss therelationship between LTE evolved MBMS and next gener-ation broadcast television and propose some recommenda-tions aimed at improving efficiency of the respective systemsIn [9] the authors present a compact convenient model forbroadcasting in LTE as well as a set of efficient algorithmsto define broadcasting areas and to actually perform contentscheduling A joint multicastunicast scheduling strategyfor MBMS delivery which improves QoS performance isproposed in [10] In [11] the authors propose a method forforming broadcasting area and assignment of content to themso that radio resources are efficiently exploited and userrequests satisfied In [12] a distributed resource allocationscheme is proposed which includes device-to-device com-munication broadcasting groups and minimizes interferencerelationships In [13]MBMSwith inherently low requirementfor network resources as a candidate solution for using suchresources in a more efficient manner is proposed Highlevel considerations related to implementation of a sessioncontroller supporting application programming interfacesfor message broadcastingmulticasting can be found in [14]

The proposed solutions have to be implemented by thetelecom network operator We study another multimediabroadcasting issue that has been scarcely addressed so farnamely third-party control which allows external applica-tions outside the network to control service provisioningOur research is focused on two standardized technologieswhose synergy has not been studied to date The Parlay XWS is technology aimed at providing a horizontal servicearchitecture which may be shared by different applications Itdefines highly abstracted technology neutral application pro-gramming interfaces (APIs) Integration ofMBMS andParlayX requires translation of high level interfaces into telecom-munication control protocols The innovative approach toefficient MBMS provisioning requires considering also otheradvanced network functions such as policy-based quality ofservice control and flexible charging We examine how threedifferent functions in EPS related to multimedia broadcast-ing policy and charging control and third-party control cancollaborate and take the advantage of network convergence inprovisioning of value added services

3 Broadcast Service Architecture in EPS

Different broadcast business cases may be considered andthe relevance of each used case is up to network operatorsand their relationship with the content owners agenciesand broadcasters Used case examples include mobile TVdigital radio video on demand electronic magazines andnewspapers and configuration and management of intelli-gent objects with internet connectivity

As to 3GPP TS 23246 the components of the 3GPPsolution of MBMS are MBMS bearer service and MBMSuser service The MBMS bearer service enables efficientdistribution of content to multiple users while MBMS userservice is used by user devices when specific end userapplications are activatedThe architecture of MBMS for EPSwith the proposed third-party control is depicted in Figure 1

The multimedia content that has to be broadcasted isprovided by an Application Sever (AS) The MBMS AS maybe deployed by network operator or third-party applicationprovider The Broadcast Multicast Service Centre (BMSC)stores multimedia content to be transmitted controls themultimedia broadcast service and interacts with mediasources and the end usersrsquo devices via Packet Data NetworkGateway (PDNGW) It provides interfaces for both signalingand data transfer to the MBMS GW The MBMS Gateway(GW) distributes the data received from the BMSC to therelevant base stations in the access network The MobilityManagement Entity (MME) communicates with the accessnetwork in the concerned area relaying session controlinformation received by MBMS GW [15]

The end users discover the available MBMS services byservice announcement which provides information aboutservices Service announcement is used to distribute to usersinformation about MBMS service activation parameterslike IP multicast address and service start time Serviceannouncement mechanisms may include short messagebroadcasting MBMS broadcasting or multicasting mode


Access network

Evolved packet core

MBMS GW BMSC

MME PCRF OCSCDF

PDN GW
























activation


Session start


period

Data transfer

Data transfer

Sessionannouncement

Stop broadcast



operation

Local service

deactivation



service stop



Null


Broadcasting


Broadcasted


getBroadcastStatus

getBroadcastStatus



stopAnnouncement


unableToDeliver







model

MBMS gatewayIP-CAN

session state model


model

CDFOCSMBMS


BMSC




Message broadcast

application

Device(user

equipment)



MBMS data


Service info

Ack

Access network




resources



MBMS data








Ack

Session stoprequest




Ack

Provision Ack

MBMS data





























(iv) 1199040

App= Null









(iv) 1199040

BMSC= MBMSIdle



MBMSIdle

InitialWaiting


DataTransfer

initialPeriod


resourceFailed

resourceLost









(iv) 1199040

MBMS= IPCANIdle




IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation










Access network

Evolved packet core

MBMS GW BMSC

MME PCRF OCSCDF

PDN GW
























activation


Session start


period

Data transfer

Data transfer

Sessionannouncement

Stop broadcast



operation

Local service

deactivation



service stop



Null


Broadcasting


Broadcasted


getBroadcastStatus

getBroadcastStatus



stopAnnouncement


unableToDeliver







model

MBMS gatewayIP-CAN

session state model


model

CDFOCSMBMS


BMSC




Message broadcast

application

Device(user

equipment)



MBMS data


Service info

Ack

Access network




resources



MBMS data








Ack

Session stoprequest




Ack

Provision Ack

MBMS data





























(iv) 1199040

App= Null









(iv) 1199040

BMSC= MBMSIdle



MBMSIdle

InitialWaiting


DataTransfer

initialPeriod


resourceFailed

resourceLost









(iv) 1199040

MBMS= IPCANIdle




IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation












activation


Session start


period

Data transfer

Data transfer

Sessionannouncement

Stop broadcast



operation

Local service

deactivation



service stop



Null


Broadcasting


Broadcasted


getBroadcastStatus

getBroadcastStatus



stopAnnouncement


unableToDeliver







model

MBMS gatewayIP-CAN

session state model


model

CDFOCSMBMS


BMSC




Message broadcast

application

Device(user

equipment)



MBMS data


Service info

Ack

Access network




resources



MBMS data








Ack

Session stoprequest




Ack

Provision Ack

MBMS data





























(iv) 1199040

App= Null









(iv) 1199040

BMSC= MBMSIdle



MBMSIdle

InitialWaiting


DataTransfer

initialPeriod


resourceFailed

resourceLost









(iv) 1199040

MBMS= IPCANIdle




IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation










Message broadcast

application

Device(user

equipment)



MBMS data


Service info

Ack

Access network




resources



MBMS data








Ack

Session stoprequest




Ack

Provision Ack

MBMS data





























(iv) 1199040

App= Null









(iv) 1199040

BMSC= MBMSIdle



MBMSIdle

InitialWaiting


DataTransfer

initialPeriod


resourceFailed

resourceLost









(iv) 1199040

MBMS= IPCANIdle




IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation



























(iv) 1199040

App= Null









(iv) 1199040

BMSC= MBMSIdle



MBMSIdle

InitialWaiting


DataTransfer

initialPeriod


resourceFailed

resourceLost









(iv) 1199040

MBMS= IPCANIdle




IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation

















(iv) 1199040

BMSC= MBMSIdle



MBMSIdle

InitialWaiting


DataTransfer

initialPeriod


resourceFailed

resourceLost









(iv) 1199040

MBMS= IPCANIdle




IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation










IPCANIdle

sessionStart

pccRules

ipCanBearerRelease


SessionActive


ipCanBearerLost

ipCanSessionTermAck


ResourceReservation

ResourceRelease

WaitForTermAck








ResourceNull

IPCanSession

sessionInfo

provisionAck

ipCanBearerRemoved


ipCanSessionCancel



ResourceAuthorizing

ResourceAuthorized



(iv) 1199040

PCRF= ResourceNull









(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation












(iv) 1199040

CS= ChargingIdle









(iii) 119904120583

rArr 119904119899 where 120583 = 119886

1 1198862 119886

119899 exist1199041 1199042 119904

119899 such

that 1199041198861


997888rarr 119904119899

(iv) 119904120583


rArr 1199041015840

(v)







(i) 1199041

119886


2 1199051

rArr10158401199052and 11990421198801199052

(ii) 1199051

119886


2 1199041

119886

rArr 1199042and 11990421198801199052


ChargingIdle





Activeinitial

Activetransfer



















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation















ResourceAuthorizing




ResourceAuthorized








fails



ResourceNull




ResourceNull





ResourceNull




ResourceNull


data transfer



























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation























MBMS session stop



IPCANIdle




IPCANIdle






reservation






authorization

































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation































120591MBMS1







le)








ResourceNull)


sequences


Activeinitial)


Activetransfer)


ChargingIdle)



ingIdle)


ingIdle)


119894 120591

BMSC119894 120591

MBMS119894

120591PCRF119894 120591





7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation










7 Conclusion







References
























RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation











RoboticsJournal of





Journal of



RotatingMachinery





VLSI Design



Shock and Vibration







Journal of



Volume 2014


SensorsJournal of





Propagation









Documents

Research Article Model Aspects of Open Access to