KR20090082079A - Apparatus and method for establishing data path for multicast and broadcast service in cellular network - Google Patents

Abstract

An apparatus and a method for establishing a data path for a multicast and broadcast service in a cellular network are provided to perform the setup, release and change of a path between network entities for wireless broadcasting services. A method for establishing a data path for a multicast and broadcast service in a cellular network comprises the steps of: transmitting a session start request message to a control station in order for a broadcasting server to request a connection setup before the transmission of MBS data(201); enabling the control station to set up a multicast connection between the control station and a broadcasting server based on the information of the session start request message; making the control station transmit a response message of the session start request message to the broadcasting server; enabling the control station to transmit a registration request message to at least one base station which belongs to a correspondent broadcasting zone to request the setup of an R6 data path and the reservation for the wireless resource(205); enabling at least one base station to set up the multicast connection between the control station and the base station based on the information of the path registration request message; and enabling the base station to transmit the path registration response message to the base station as the response for the path registration request message(209).

Description

Apparatus and method for setting data path for broadcasting service in cellular network {APPARATUS AND METHOD FOR ESTABLISHING DATA PATH FOR MULTICAST AND BROADCAST SERVICE IN CELLULAR NETWORK}

The present invention relates to an apparatus and method for providing a multicast and broadcast service in a cellular network, and more particularly, to set up, release, and change a data path for a broadcast service between corresponding network entities. An apparatus and method for modification.

In general, communication systems have been developed mainly for voice services, and are gradually developing into communication systems capable of not only voice but also data services and various multimedia services. However, the voice-oriented communication system has a relatively small transmission bandwidth and a high usage fee, and thus do not satisfy the rapidly increasing service needs of users. In addition, due to the development of the communication industry and increasing user demand for Internet services, there is an increasing need for a communication system capable of efficiently providing Internet services. Accordingly, it has been introduced into a broadband wireless access system for efficiently providing Internet services with broadband.

The wireless access method of the broadband wireless access system is being standardized by the IEEE 802.16 standardization group of the Institute of Electrical and Electronics Engineers, one of the international standardization organizations. Compared to the conventional wireless technology for the wireless service, the broadband wireless access system has a wider bandwidth and can transmit a lot of data in a short time, and all users can share a channel (or resource) to efficiently use the channel. . In addition, quality of service (QoS) is guaranteed so that users can receive different quality services according to the characteristics of the service.

The main services of the broadband wireless access system include the Internet, Voice over IP (VoIP), and non-real time streaming services. Recently, MBS (Multicast Broadcast Service), a real-time broadcast service, has been proposed as a new service. The MBS can simultaneously transmit various channels such as high-definition video and high-quality audio due to the high data rate using the macro diversity technique. Here, the macro diversity scheme means transmitting the same data at the same resource and at the same time for each MBS zone.

At present, various standards (or standards) are provided for broadcast services, but a specific method is not defined for data path setting for actually delivering broadcast content. In order to deliver broadcast content, a data path between a network entity located in a Core Service Network (CSN) and a network entity located in an Access Service Network (ASN) before broadcasting starts. Should be established, and therefore specific measures regarding the establishment, release and modification of these data paths should be prepared.

Accordingly, an object of the present invention is to provide an apparatus and method for setting, releasing and changing a data path for a broadcast service in a cellular network providing a broadcast service.

Another object of the present invention is to provide an apparatus and method for setting a data path for a broadcast service through signaling before starting broadcast in a cellular network providing a broadcast service.

Another object of the present invention is to provide an apparatus and method for establishing a data path for a broadcast service between an MCBCS server and an ASN_GW using IGMP in a cellular network providing a broadcast service.

Another object of the present invention is to provide an apparatus and method for establishing a data path for a broadcast service between ASN_GW and a base station using IGMP in a cellular network providing a broadcast service.

Another object of the present invention is to provide an apparatus and method for setting, releasing and changing a data path in units of a broadcasting zone (MBS zone) in a cellular network providing a broadcast service.

According to one aspect of the present invention for achieving the above object, in a method for providing a broadcast service in a cellular network, the broadcast server, before the start of the broadcast, transmitting a session start request message to the control station; A control station setting a data path between the broadcast server and the control station in response to the session start request message; transmitting, by the control station, a response message for the session start request message to the broadcast server; Transmitting, by the control station, a path registration request message to at least one base station belonging to the corresponding broadcast zone; and by the at least one base station, a data path between the control station and the base station in response to the path registration request message. And setting a path and transmitting a path registration response message to the control station. .

Preferably, the method comprises the steps of the broadcast server receiving a content registration request from a content server, and upon receiving the content registration request, the broadcast server assigns a content ID and a broadcast channel IP address to each content. The method may further include generating a mapping table for each content.

Preferably, the method, at the end of the broadcast, the broadcast server, the step of transmitting a session release request message to the control station, the control station, in response to the session release request message, the data between the broadcast server and the control station; Releasing a path, transmitting, by the control station, a response message to the session release request message to the broadcast server, and controlling, by the control station, at least one base station belonging to the corresponding broadcast zone; And transmitting, by the at least one base station, a data path between the control station and the base station in response to the path release request message, and transmitting a path release response message to the control station. Characterized in that.

Preferably, in the method, after setting a path, the broadcast server transmits a session change request message to a control station, and the control station changes parameter information of a corresponding broadcast channel in response to the session change request message. And transmitting, by the control station, a response message to the session change request message to the broadcast server, and by the control station to at least one base station belonging to the MBS zone serving the corresponding broadcast channel. Transmitting a change request message; and transmitting, by the at least one base station, a path change response message to the control station to change parameter information of a corresponding broadcast channel in response to the path change request message. do

Preferably, the method further comprises the steps of: when the broadcast is started, the broadcast server multicasting or unicasting a broadcast packet to a control station using an R3 multicast or unicast IP address; Storing the received broadcast packet using the broadcast channel IP address in the corresponding MCID queue of the corresponding broadcast zones, and the control station packetizes the broadcast packet stored in the queue according to the burst size of the radio section. Generating a media access control (MAC) service data unit (SDU); time stamping an absolute broadcast time on the MAC SDU; and attaching a GRE header to the MAC SDU to generate a tunneling packet; The control station further includes the step of attaching an R6 multicast IP header to the tunneling packet to generate an IP packet, and multicasting the IP packet to base stations belonging to a corresponding broadcast zone. It is characterized by.

As described above, the present invention can efficiently perform path establishment, release, and change between network entities (NEs) for a wireless broadcast service that is emerging as a main service in a cellular network. Since the present invention secures the data paths for the R3 and R6 interfaces before the content delivery, the contents can be delivered without delay immediately after the broadcast is started. In addition, since the present invention performs data path establishment in units of MBS zones (broadcast zones), signaling overhead can be significantly reduced.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

Hereinafter, a method for setting up, releasing, and modifying a data path for a broadcast service between network entities in a cellular network providing a broadcast service will be described.

Here, the broadcast service is a multicast and broadcast service (MCBCS), a multicast and broadcast service (MBS), a multi media broadcast and multicast service (MBMS), a broadcast / multicast service (BCMCS), a DMB, according to a standard group and an operator's intention. May be called MediaFLO, etc.

In the following description, the name of a network entity (NE: Network Entity or Network Element) is defined according to a corresponding function, and may vary depending on the intention of the standardization group and the operator. For example, the base station may be called an access point (AP), a radio access station (RAS), a node-B, or a base station (BS). In addition, the base station controller may be referred to as a radio network controller (RNC), a base station controller (BSC), an access control router (ACR), or an access service network gateway (ASN-GW). The GW may perform router functions as well as base station controller functions.

In addition, although an OFDM / OFDMA-based broadband wireless communication system is described below by way of example, the present invention can be easily applied to other wireless communication systems that provide a broadcast service.

1 illustrates a network structure according to an embodiment of the present invention.

As shown, it includes a content server 100, MCBCS server 102, ASN_GW 104, network manager (WSM: WiBro System Manager) (106) and the base station 108. Here, the ASN_GW 104 and the base station 108 may be classified into an access service network (ASN).

Referring to FIG. 1, the content server 100 creates and stores broadcast content and registers the content with the MCBCS server 102 using a response layer protocol (eg, HTTP) before the broadcast service. In this case, the content server 100 may transmit a content type, a service bit rate, a service time, a service area, and the like to the MCBCS server 102.

The MCBCS server 102 has an interface with an external content server 100 and an AAA server (not shown). The MCBCS server 102 delivers actual broadcast traffic, MBS zone management information, etc. to an ASN, and provides a service guide (broadcast schedule, mapping table, etc.). ) And a service authorization key for each content to the terminal. At this time, the MCBCS server 102 and the terminal communicates using an application layer protocol (eg, HTTP). When a content registration request is received from the content server 100 through an application layer protocol (eg, HTTP), the MCBCS server 102 allocates a broadcast channel multicast or unicast IP address and content ID to each content. In addition, the MCBCS server 102, content ID, multicast IP address, service time (delivery date, delivery time), data rate, MCID, MBS zone ID, transmission zone ID (Transmission Zone ID) for each content. ID) etc. are held in the mapping table. This mapping table is used to convey various signaling and IP packets to ASN_GW 104. In addition, the MCBCS server 102 delivers the broadcast content from the content server 100 to the ASN according to the broadcast schedule. The MCBCS server 102 may transmit air scheduling information (permutation, MCS level, MIMO, transmission rate, transmission period, compression, broadcasting start / end time, etc.) for the broadcast service to the ASN. As another example, the air scheduling information may be transferred from the network manager (WSM or EMS or OMC) 110 to the ASN.

ASN_GW 104 transmits traffic from the core network to the base station 108, and transmits traffic from the base station 108 to the core network. The ASN_GW 104 manages a service flow (SF), a connection, and mobility for each terminal. Here, a unique service flow (SF) is generated for each uplink and downlink connection. It also has an interface with a CSN such as an AAA server. The MBS controller is configured in an access service network (eg, a block in ASN_GW), performs a data / time synchronization function for broadcast traffic from the MCBCS server 102, and performs the data. / Cast the time-synchronized broadcast packet to base stations in the same MBS zone. The MBS controller can be classified into two types: an MBS proxy for signaling and an MBS data path function (DPF) for broadcasting data traffic processing, including synchronization.

The base station 108 has a wireless interface with the terminal and transmits broadcast content from the MBS controller in the ASN_GW 104 through a predetermined resource at a predetermined time. Here, when supporting macro diversity for a broadcast service, base stations belonging to the same MBS zone broadcast the same content through the same resource at the same time.

The network manager 106 is responsible for the maintenance and maintenance of the network entities of the ASN, and delivers PLD (Program Loading Data) required for initialization of the ASN_GW 104 and the base station 108 to the network entity. Although not shown, there may also be a network manager (MCBCS OMC) that manages the MCBCS server 102. The network manager managing the ASN_GW 104 and the base station 108 may be divided into three groups, such as the ANS_GW OMC (Operation and Maintenance Center), the BS OMC, the ASN_GW OMC, and the upper OMC managing the BS OMC, depending on the network configuration. ASN_GW OMC and the upper OMC may exist as one unified OMC. In general, it is assumed that an integrated OMC exists either per NAP network or per ASN. The MCBCS server 102 may transmit configuration information to the ASN through the integrated OMC. In this case, it is assumed that the interface between the MCBCS OMC and the ASN does not exist.

A terminal (not shown) is a subject consuming a broadcast service. The terminal receives and stores a service guide (including a broadcast schedule and a mapping table) from the MCBCS server 102 through an application layer in order to receive, change, and delete broadcast traffic even in an idle mode. When the terminal requests the service guide, the MCBCS server 102 checks whether the terminal is a broadcast service subscriber through authentication, and in the case of the broadcast service subscriber, downloads the service guide to the terminal. In this case, the service guide may include a broadcast schedule (time, transmission rate, etc.), a broadcast channel IP address, an MCID, an MBS zone ID, a content ID, an encryption key, and the like. The terminal may identify the MBS zone to which it currently belongs through a broadcasting message (eg, DCD).

Meanwhile, a broadcast service can be broadly classified into a broadcast service and a multicast service. In this case, a classification criterion is whether the terminal joins an IGMP. When the terminal performs the IGMP join, it may be classified as a multicast service, otherwise it may be classified as a broadcast service.

In addition, the case in which the UE performs IGMP join can be divided into a dynamic multicast method and a static multicast method. The dynamic multicast method indicates a method of switching broadcast and unicast according to the number of users receiving a broadcast channel. The fixed multicast method indicates a method of turning off a broadcast when there is no switching but no user receives the broadcast channel. The broadcast represents broadcasting a designated broadcast channel at a designated time.

Meanwhile, broadcast services may be classified into a static MBS transmission scheme and a dynamic MBS transmission scheme. The classification criteria are whether IGMP joins the terminal and whether resource allocation is changed on the radio section (R1 interface) from the start of the broadcast until the end of the broadcast. Regardless of whether IGMP joins the terminal or not, resource allocation does not change, and is classified as a fixed MBS transmission scheme. On the other hand, depending on whether the terminal IGMP join or resource allocation is changed, it can be classified as a dynamic MBS transmission scheme. Here, the resource allocation state may be changed according to the time zone for one MBS zone, that is, the resource allocation state may be changed when the broadcast starts with the new broadcast configuration after the broadcast ends, but this is not the case.

Although not shown, a policy server, an AAA (Authentication, Authorization, Accounting) server and the like may exist in the core service network.

The AAA server may manage authentication and billing information, and may include a subscription profile repository (SPR) function for managing profile information for each subscriber. In addition, the AAA server may manage the security key and the lifetime derived from the subscriber-specific broadcast service authorization information and initial authentication. A policy server provides policy information (eg QoS policy information) determined by an operator (or operator) to a corresponding network entity. Here, the policy server may exist in the MCBCS server 102, may exist in other network entities, or may exist as a separate server.

Base stations belonging to the same MBS zone register with a multicasting group through IGMP (Internet group management protocol), and ASN_GW multicasts broadcast packets to corresponding base stations through a multicast IP address (multi-BS MBS). That is, the base station may receive the MBS packet from the master ASN_GW (or anchor ASN_GW) of the MBS zone, not the ASN_GW that manages the base station. Here, the base station receives IGMP triggering from its ASN_GW. Meanwhile, the MCBCS server 102 also transmits broadcast traffic to the ASN_GW 104 in a multicasting manner, in which the ASN_GW 104 transmits an IGMP message to the MCBCS server 102 to receive a multicast packet. Activates the receive function for. In general, since the ASN_GW 104 and the MCBCS server 102 are not adjacent to each other, the IGMP message is actually transmitted to the multicast router connected to the MCBCS server 102 instead of being directly transmitted to the MCBCS server 102. do.

Here, the identifier of the broadcast zone unit in the ASN is an MBS Zone ID, and the identifier of a subcell unit is a BSID (Base Station IDentifier). In addition, it is assumed that the data path of the R6 interface is different for each MBS zone even for the same broadcast content. The reason is that time stamping and packetization for multi-BS MBS is performed in ASN_GW 104.

As described above, a separate server function is required for the MCBCS service. In the present invention, the server function located in the NAP is defined as an MBS server, and the server function located in the NSP is defined as an MCBCS server. When the NAP and the NSP are the same, the MBS server and the MCBCS server may be integrated into one server. Here, BS grouping, that is, allocation of BSID per MBS zone is assumed to be performed by the MBS server or the integrated OMC located in the NAP.

If there are several NSPs and an MCBCS server exists for each NSP, NAP sharing is resolved as follows. Each NSP notifies the MBS server of the desired broadcasting area (eg area code, MBS zone ID, etc.) and broadcasting channel configuration information (channel identifier (content ID or IP layer identifier), transmission rate, service time, service quality, etc.). The MBS server may comprehensively determine information received from a plurality of MCBCS servers and NAP resources to efficiently determine multicast CID (MCID) and air scheduling and inform each MCBCS server. If each MCBCS server determines the MBS zone ID, MCID, and air scheduling, NAP and NSPs must negotiate offline so that MBS zone IDs do not overlap. If the NAP becomes one of several NSPs, an MBS server may be included in the MCBCS server so that MCBCS servers of different NSPs may communicate with the MCBCS server of the NAP to perform the above functions. Alternatively, the MBS server does not exist separately, and the NAP may perform the broadcast service by configuring the MBS zone ID and anchor ASN_GW MCBCS DPF and MCID offline with the NSPs.

In addition, it is assumed that BS grouping (BSID list) for each MBS zone, that is, BSID allocation per MBS zone is performed by an integrated OMC or MBS server located in the NAP area. And, it is assumed that the BSID list mapped to the MBS zone is configured by the operator in advance.

Even if there are multiple NSPs in the CSN, if the NAP becomes one of the NSPs, the MBS server function may be included in the MCBCS server of the NSP owned by the NAP. Since the corresponding MCBCS server also includes the MBS server function, it is located at the boundary between the CSN and the NAP network, and the MCBCS servers of other NSPs communicate with the MCBCS server of the NSP owned by the NAP.

In order to provide a wireless broadcasting service in a cellular network, it is necessary to efficiently set up, release, and modify data paths between network entities located in CSNs and ASNs. Hereinafter, a method of setting, releasing, and changing the data path will be described in detail. Hereinafter, in the present invention, unless the MBS zone configuration is changed for each base station, it is assumed that the base station does not perform IGMP join and rib on the R6 interface. That is, even if the broadcast channel configuration in the MBS zone is changed, if the MBS zone configuration is not changed (that is, if the same MBS zone ID is maintained for the base station), the corresponding base station may not perform IGMP ribs. In the present invention, a data path for a broadcast service includes a static path establishment method through configuration and a dynamic path establishment method through signaling before starting broadcast. Here, the fixed path setting method and the dynamic path setting method are shown in Table 1 below.

Static route configuration Dynamic Route Setting (Signaling Based) Advantages -Eliminate signaling overhead between each network entity for data path establishment and release (between ASN_GW and BS, between MCBCS server and ASN_GW)-Eliminate abnormal situations that can occur in signaling-Integrate OMC with MCBCS server when easy scenarios are needed ASN_GW OMC can be operated by itself without interworking procedure -MCBCS server can dynamically control data path setting-Easy to change configuration-Similar to standard Disadvantages -Different from standard-not easy to change configuration via OMC Signaling overhead-Signaling abnormalities may occur Service viewpoint Appropriate when pre-determined broadcasting schedule * Suitable for emergency / disaster broadcasting (Easy real-time processing when fixed IDs are used) Broadcast schedule cannot be set in advance and suitable when various IDs are not set

First, the fixed route setting method will be described.

Basically, the fixed path setting is a method of providing a broadcast service using information previously set in the ASN_GW and the base station. Through the interworking between the MCBCS server and the OMC, information for broadcasting service is set in advance in the ASN_GW and the base station. Subsequently, when multicast traffic (broadcast traffic) is received from the MCBCS server at the corresponding broadcast time, the ASN_GW uses the preset GRE key (MBS zone ID, MCID, etc.) and the R6 multicast IP address, and the like. Multicast broadcast traffic to belonging base stations. Here, the R6 interface represents an interface between the ASN_GW and the base station, and the R3 interface represents an interface between the MCBCS server and the ASN_GW. That is, the ASN_GW performs an IGMP join procedure for transmitting and receiving multicast traffic through an R3 / R6 interface, and multicasts multicast traffic from an MCBCS server to base stations.

To do this, look at the information to be set in the ASN_GW and the base station is shown in Table 2 below.

ASN_GW Base station (BS) -R3 broadcasting channel IP address-MBS zone ID, MCID-Broadcasting service start and end time-MBS zone air scheduling information-MCID air scheduling information-MBS MAP message air scheduling information-GRE key-ASN_GW is IGMP Join & Leave Network element address to be carried out-Transmission type (single BS MBS, Multi BS MBS, etc.)-R6 multicast IP address-(R3 broadcast channel IP address, MBS zone ID & MCID) mapping relationship-(R3 broadcast channel IP address, MBS zone ID) Mapping relationship -R6 multicast IP address-MBS zone ID, MCID,-Broadcasting service start and end time-Air scheduling information for each MBS zone-Air scheduling information for each MCID-Air scheduling information for MBS MAP messages-GRE key-Base station should do IGMP Join & Leave Network element address-Transmission type (single BS MBS, Multi BS MBS, etc.)-(R6 multicast IP, MBS zone ID) mapping relationship

Next, a dynamic path establishment method through signaling will be described.

ASN_GW configures a data path for a broadcast service through signaling before starting broadcasting.

2 illustrates a procedure for setting a data path for a broadcast service according to an embodiment of the present invention.

Referring to FIG. 2, before the broadcast start (or before MBS data delivery), the MCBCS server 102 sends an R3 Session Start Req message to the ASN_GW 104 to request a multicast connection setup in step 201. send. At this time, the session start request message is MBS zone ID, R3 broadcast channel IP address, (R3 broadcast channel IP vs MBS zone ID & MCID) mapping information, MCIDs corresponding to MBS zone ID, broadcast service start and end time (Delivery Start Time & Delivery End Time), air scheduling information by MBS zone, air scheduling information by MCID, air scheduling information by MBS MAP message, network element address that ASN_GW should IGMP Join & Leave, transmission type (Dynamic multicast or Static multicast; Single BS MBSor Multi BS MBS with macro diversity or multi-BS MBS without macro diversity, etc.), source ID (MCBCS server ID), destination ID (ASN_GW ID) may include at least one.

When the R3 session start request message is received, the ASN_GW 104 joins an IGMP with a multicast router to establish a multicast connection based on the multicast IP address included in the session start request message in step 203. Send a message. If MCBCS data transmission of R3 interface is unicast, that is, IP-in-IP (outer IP is unicast IP for ASN_GW and MCBCS server communication, inner IP is broadcast multicast IP address), IGMP join and rib Of course, no procedure is necessary. That is, the ASN_GW 104 transmits an IGMP join message to a multicast router connected to the MCBCS server 102 to activate a reception function for a specific multicast address. In this case, the IGMP join may be performed as many as the number of R3 broadcast channel IP addresses included in the session start request message. That is, IGMP join may be performed for each broadcast channel.

After performing the IGMP join, the ASN_GW 104, in step 205, the base station 108 in the corresponding MBS zone to request R6 data path establishment and air resource reservation at the base station. R6 MBS path registration request (MBS_path_Reg_Req) message is sent. Here, the MBS path registration request message, MBS zone ID, R6 multicast IP address, MCIDs corresponding to the MBS zone ID, Generic Routing Encapsulation (GRE) key, delivery service start and end time (Delivery Start Time & Delivery) End Time), Air Scheduling Information by MBS Zone, Air Scheduling Information by MCID, Air Scheduling Information for MBS MAP Message, Network Element Address to be IGMP Join & Leave by Base Station, Transmission Type (Dynamic Multicast or Static Multicast; Single BS MBS or Multi BS) MBS with macro diversity or Multi-BS MBS without macro diversity, etc.), a Source ID (ASN_GW ID), and a Destination ID (BSID).

In step 207, the base station 108 receiving the MBS path registration request message transmits an IGMP join message to the multicast router to set up a multicast route based on the information of the R6 MBS path registration request message. That is, the base stations 108 transmit an IGMP join message to a multicast router connected to the ASN_GW 104 to activate a reception function for a specific multicast address. In this case, the IGMP join may be performed by the number of R6 multicast IP addresses included in the MBS path registration request message. That is, IGMP join may be performed in units of MBS zones.

As such, after the multicast connection is set up, the base station 108 transmits an R6 MBS path registration response (MBS_Path_Reg_Req) message to the ASN_GW 104 in response to the R6 MBS path registration request message in step 209. Herein, the R6 MBS path registration response message includes information indicating whether to set a path for each MBS zone ID, MBS zone ID (success or failure), and detailed information on failure when the path setting fails (Detailed failure report per MBS zone ID). , ex failed MCID list), Source ID (BSID), Destination ID (ASN_GW ID), and the like.

On the other hand, if a multicast connection to the R3 interface is established, the ASN_GW 104 responds to the MCBCS server 102 using an R3 Session Start Response message in step 211. Here, the session start response message may include information indicating whether to set a path for each MBS zone ID or MBS zone ID (Success or failure report per MBS zone ID), and detailed information on failure when the path setting fails. MBS zone ID, ex failed MCID list), Source ID (ASN_GW ID), Destination ID (MCBCS server ID) and the like. That is, the data path between the MCBCS server, ASN_GW, and BS is set by the same procedure.

In the above-described embodiment, when the MBBCS server transmits an R3 session start request message including a broadcast channel application layer ID or a broadcast channel IP address to ASN_GW (MBS Proxy / primary MBS DPF), the ASN_GW responds to the R3 session start response. The message may include an upper layer vs. MAC layer broadcast channel ID mapping relationship generated by ASN_GW or NAP explicitly or implicitly to respond to the MCBCS server. Here, the implicit method indicates a method of including a MAC layer ID in a multicast IP address or an application layer ID (eg, content ID, program ID, etc.).

Meanwhile, as described above, in the case of performing the IGMP join, whether the session start request message or the MBS path registration request is successful may be indirectly checked through IGMP, and the GRE key does not need to be exchanged. Signaling for each interface is sufficient, not 2 way handshake (req / rsp / ack) but 2 way handshake (req / rsp). In case of signaling using unicast, 2way or 3way can be used.

The above-described procedure of FIG. 2 may be performed when newly creating an MBS zone or adding a broadcast channel to the MBS zone.

Meanwhile, in the above-described embodiment of FIG. 2, the ASN_GW 104 may forward the session start response message to the MCBCS server 102 regardless of the result of the R6 response message (MBS_Path Reg_Rsp). Of course. In this case, the data path setting procedure is shown in FIG. 7.

As shown in FIG. 7, before the MBS data is delivered, the MCBCS server 102 sends an R3 session initiation request message to the ASN_GW 104 (or MBS proxy / Primary MBS DPF) to request multicast connection setup in step 701. send. Upon receipt of the R3 session start request message, the ASN_GW 104 establishes a multicast connection based on the multicast IP address included in the R3 session start request message in step 703. Sends an IGMP join message. That is, the ASN_GW 104 transmits an IGMP join message to a multicast router connected to the MCBCS server 102 to activate a reception function for a specific multicast address.

In this way, after establishing a multicast connection with the MCBCS server, the ASN_GW 104 transmits the R3 session start response message to the MCBCS server 102 in step 705. Here, the session start response message may include information (success or failure) indicating whether to set a path for each broadcast channel. Here, the transmission order of the R3 session start response message and the IGMP join message may be exchanged. Subsequently, the procedure of steps 707 to 711 is the same as the procedure of steps 205 to 209 of FIG. 2, and thus a detailed description thereof will be omitted.

3 illustrates a procedure for releasing a data path for a broadcast service according to an embodiment of the present invention.

Referring to FIG. 3, after the broadcast ends (or when MBS data is delivered), the MCBCS server 102 requests an R3 session release from the ASN_GW 104 to request a release of a multicast connection in step 301. Release Req) message. In this case, the R3 session release request message may include an MBS zone ID, release MCIDs corresponding to the MBS zone ID, a multicast IP address, and the like.

When the R3 session release message is received, the ASN_GW 104 multi-connects to the MCBCS server 102 to release the multicast connection based on the multicast IP address included in the R3 session release request message in step 303. Send an IGMP leave message to the multicast router.

After performing the IGMP rib, the ASN_GW 104 sends an R6 MBS path release request (MBS_path_DeReg_Req) message to the base stations 108 in the corresponding MBS zone to request the release of the R6 data path and the radio resource release from the base station in step 305. Send it. The MBS path release request message may include a BSID, an MBS zone ID, a Generic Routing Encapsulation (GRE) key, release MCIDs corresponding to the MBS zone, a multicast IP address, and the like.

On the other hand, the base station 108 receiving the R6 MBS path release request message to the multicast router (Multicast router) connected to the ASN_GW 104 to release the multicast connection based on the information of the received message in step 307 Send an IGMP rib message. As such, after releasing the multicast connection, the base station 108 transmits an R6 MBS path release response (MBS_Path_DeReg_Rsp) message to the ASN_GW 104 in response to the R6 MBS path release request message in step 309.

On the other hand, when the multicast connection with the MCBCS server 102 is released, the ASN_GW 104 transmits an R3 Session Release Res message to the MCBCS server 102 in step 311. That is, the data path between the MCBCS server-ASN_GW-BS is released by the above procedure.

In addition, the above-described procedure of FIG. 3 may be performed when deleting the MBS zone or deleting some channels in the MBS zone.

2 and 3, since the R6 multicast IP address and the MBS zone ID have a 1: 1 relationship, the base station may perform IGMP join / leave transactions as many as the number of MBS zones.

When performing signaling for data path establishment / release, if bearer traffic transmitted through the corresponding interface (R3 or R6) is multicast, IGMP join / leave is performed as described above, but bearer traffic is transmitted through unicast. In this case, the IGMP procedure described above is not necessary. The bearer traffic IP address has a 1: 1 or 1: n relationship with the broadcast channel on the R3 interface, and has a 1: 1 relationship with the MBS zone on the R6 interface. The number of messages in IGMP joins / ribs is proportional to the number of multicast IP addresses. In the case of the R6 interface according to the present invention, multicast IP addresses are allocated in units of MBS zones. As a result, signaling overhead of backhaul can be significantly reduced. have.

Meanwhile, the ASN_GW 104 may deliver the Session Release Res message to the MCBCS server 102 irrespective of the result of the R6 response message (MBS_Path Dereg_Rsp). In this case, the data path release procedure is shown in FIG. 8.

As shown in FIG. 8, when the MBS data delivery is completed, the MCBCS server 102 requests the R3 session release to the ASN_GW 104 (or MBS proxy / Primary MBS DPF) to request the release of the multicast connection in step 801. Send a message. When the R3 session release request message is received, the ASN_GW 104 sends a message to the MCBCS server 102 to release the multicast connection based on the multicast IP address included in the R3 session release request message in step 803. Send IGMP leave messages to the connected multicast router (MR).

As such, after releasing the multicast connection with the MCBCS server 102, the ASN_GW 104 transmits the R3 session release response message to the MCBCS server 102 in step 805. In this case, the R3 session release response message may include information indicating success or failure for each channel. Meanwhile, the transmission order of the session release response message and the IGMP rib message may be exchanged. Thereafter, since the procedure of steps 807 to 811 is the same as the procedure of steps 305 to 309 of FIG. 3, a detailed description thereof will be omitted.

4 illustrates a procedure for changing a data path for a broadcast service according to an embodiment of the present invention.

Referring to FIG. 4, when a parameter change for a specific broadcast channel is required, the MCBCS server 102 transmits a session modification request message to the ASN_GW 104 in step 401. Here, the session change request message may include an MBS zone ID, an MCID of a broadcast channel requiring change, changed parameter information (eg, air scheduling information, etc.).

When the session change request message is received, the ASN_GW 104 changes parameter information of the corresponding broadcast channel in step 403 and requests MBS path change to the base stations 108 of the corresponding MBS zone serving the broadcast channel (MBS_Path_Mod_Req). Send a message. Here, the MBS path change request message may include a BSID, an MBS zone ID, MCIDs of broadcast channels requiring change, changed parameter information (eg, air scheduling information, etc.).

On the other hand, the base station 108 receiving the MBS path change request message changes the parameter information of the corresponding broadcast channel of the MBS zone in step 405, MBS path change response in response to the MBS path change request message (MBS_Path_Mod_Rsp) Sends a message to the ASN_GW 104. Here, the MBS path change response message may include a base station identifier (BSID), MBS zone ID, MCIDs, information indicating whether to change parameters for each broadcast channel, and detailed information on failure when the change fails.

On the other hand, when the MBS path change response message is received from the base stations, the ASN_GW 104 transmits a Session Modification Rsp message to the MCBCS server 102 in step 407. Here, the session change response message may include MBS zone ID, corresponding MCIDs, information indicating whether to change parameters for each broadcasting channel, or information on failure when the change fails.

The above-described procedure of FIG. 4 may be performed when changing parameter information (eg, air scheduling information) of a setup broadcast channel. Meanwhile, the functions of the session change request message and session change response message may be replaced with a session start request message and a session start response message.

Meanwhile, the ASN_GW 104 may forward the session change response message to the MCBCS server 102 irrespective of the result of the R6 response message (MBS_Path Mod_Rsp). In this case, the data path change procedure is shown in FIG. 9.

As shown in FIG. 9, when a session change request message is received from the MCBCS server 102, the ASN_GW 104 changes parameter information of a corresponding broadcast channel in step 903, and sends a session change response message to the MCBCS server. Send to 102. Here, the session change response message may include information (success or failure) indicating whether to change the path for each broadcast channel. Thereafter, the procedure of steps 905 to 907 is the same as the procedure of steps 403 to 405 of FIG. 4, and thus a detailed description thereof will be omitted.

The functional unit in ASN_GW that handles the session initiation / session release / session change described above is defined as an MBS proxy, and the functional units that handle IGMP join / leave and MBS_Path_Reg / Dereg are defined as MBS data path functions (DPFs). Here, the MBS proxy and the primary MBS DPF are co-located (ie, exist in the same ANS_GW), and may exist in each MBS zone.

The MBS DPF may be divided into 'primary MBS DPF' and 'serving MBS DPF', and the primary MBS DPF processes IGMP join / rib with the MCBCS server, and the base station belongs to the corresponding MBS zone in the same ASN Send MBS_Path_Reg / Dereg to them. If other ASNs belong to the same MBS zone, the primary MBS DPF transmits MBS_Path_Reg / Dereg through an R4 interface (primary MBS PDF-> serving MBS PDF of another ASN).

In addition, Primary MBS PDF is in charge of time stamping and packetization for synchronization. If there are multiple ASNs in the MBS zone, the primary MBS DPF relays the synchronized packet to the Serving MBS DPF of the other ASN, and the Serving MBS DPF relays the synchronized packet to base stations in the same MBS zone that it manages. do.

2 to 4, the minimum unit of the content included in the messages according to the present invention assumes a broadcast channel, and it is assumed that broadcast channels broadcast in the same time zone in one MBS zone are included in one message. do. In addition, it is assumed that messages according to the present invention may include set information about at least one MBS zone.

In addition, in the case of multi-BS MBS, when any one of the broadcast channels broadcast in the same time zone for one MBS zone for one subcell fails to set the data path, the corresponding subcell is assigned to the corresponding MBS zone. Do not provide services. However, even if the path setting for some broadcasting channels fails according to the operator policy, the corresponding MBS zone may be serviced.

In addition, it is assumed that the IP address of the signaling uses the IP address of the receiving NE. Therefore, the IP address of the R6 signaling message may be the IP address of the BS. In this case, in order to distinguish which subcell the MBS zone ID belongs to, the signaling message may include an identifier (eg BSID) of the corresponding subcell together with the MBS zone ID.

Meanwhile, when emergency / disaster broadcasting is required, data path setting between MCBCS server-ASN_GW-BS is required as shown in FIG. 2. In order to remove such signaling delay, MCID, MBS zone ID, R3 / R6 multicast IP for emergency broadcasting The address and GRE key can be configured and operated in advance.

In addition, in order to provide emergency broadcasting to a terminal in a sleep state and an idle state, the present invention provides an MBS_MAP_IE during a listening window period for a terminal in a sleep state and a paging listening interval for a terminal in an idle state. Assume to send. For emergency broadcasting, we assume single-BS MBS, not multi-BS MBS. In the case of the single-BS MBS, MBS_MAP_IE may include both the 16-bit CID, the location and size of a data burst including emergency broadcast information, and air scheduling information. According to the current standard, the terminal cannot read only the CID and cannot distinguish whether it is an emergency broadcast. The present invention proposes a fixed assignment of a specific CID for emergency broadcast. At this time, both MCID (Multicast CID) and TCID (Transport CID) can be used, but since TCID is used for unicast traffic, it is preferable to fix a specific MCID as an emergency broadcast CID.

Looking at the identifiers mentioned in the present invention are as follows.

The content ID is a broadcast channel identifier of an application layer, the MBS zone ID is an identifier for a broadcast service region, and the MCID is a broadcast channel identifier of a unique MAC layer in the MBS zone. Here, the method of managing the MBS zone ID, MCID, and R6 multicast address in the ASN is shown in Table 3 below.

Item function Maximum management number Up to 127 MBS zone queries per ASN_GW (0 is used to indicate a base station that does not support MBS) ASN_GW: MBS zone ID = 1: n Information acquisition and information management ASN_GW Obtain and manage the following information from OMC or MCBCS server.-NE (multicast router or MCBCS server) to which ASN_GW should perform IGMP Join / Leave address-R3 Broadcast channel IP: MCID = 1: n-R3 Broadcast channel IP: Content ID = 1: 1 (or1: n)-MBS zone ID: BSID = n: m-MBS zone ID: MCID = 1: n-Broadcasting service start and end time-MBS zone air scheduling information-MCID air scheduling information-MBS Air scheduling information for MAP message (Air scheduling information: permutation, MCS level, transmission period, start and end time, location and size of MBS area) -GRE key: (MBS zone ID, MCID) = 1: 1 (can support multiple MBS zones in one subcell)-MBS zone ID: R6 multicast IP address = 1: 1-R6 multicast IP address : MCID = 1: n When a plurality of ASN_GWs are included in one MBS zone, base station management through signaling is handled by each ASN_GW, but in the case of bearer traffic, all base stations in the MBS zone are connected to one ASN_GW connected to a multicast router. Receive traffic from (master ASN_GW or anchor ASN_GW). That is, for R6 multicast IP address, base stations perform IGMP Join & Leave with multicast router. Which ASN_GW is the master can be determined and configured by the MCBCS server.

As shown in Table 3, one MBS zone ID may include a plurality of subcells (BSID). In addition, a plurality of MBS zones may be supported in one subcell. Since the MBS zone ID and MCID are previously determined according to the broadcast schedule, the integrated OMC allocates an R6 multicast IP address for each MBS zone ID and delivers it to ASN_GW.

Hereinafter, an overall data communication procedure based on the above description will be described.

5 illustrates an operation procedure of ASN_GW according to an embodiment of the present invention.

Referring to FIG. 5, first, in step 501, the ASN_GW 104 checks whether a trigger indicating data path establishment for a broadcast channel is received from the MCBCS server 102. Here, the triggering indicating the data path setting may be the session start request message described above. Upon receiving the session start request message, the ASN_GW 104 proceeds to step 503 and stores information extracted from the session start request message. This stored information can then be used for signaling and traffic transmission. In addition, the ASN_GW 104 activates a reception function for a specific multicast address by performing an IGMP join to a multicast router connected to the MCBCS server 102 using the extracted information. . In another embodiment, the ASN_GW 104 may perform an IGMP join at an appropriate time before the broadcast starts according to the broadcast schedule.

After performing the IGMP join, the ASN_GW 104 transmits the MBS path establishment triggering to the base stations 108 in the MBS zone in step 505. In this case, the MBS path setting triggering may be the MBS path registration request (MBS_Path_Reg_Req) message described above.

Meanwhile, the base stations 108 that receive the MBS path registration request message store information extracted from the MBS path registration request message. This stored information can then be used for signaling and traffic transmission. The base station 108 performs an IGMP join to a multicast router connected to the ASN_GW 104 by using the extracted information to activate a reception function for a specific multicast address and to activate an MBS path. The response to the registration request message is transmitted to the ASN_GW 104. In this case, the response to the MBS path registration request message may be the MBS path registration response (MBS_Path_Reg_Rsp) message described above. In another embodiment, the base station 108 may perform an IGMP join at an appropriate time before the start of the broadcast according to the broadcast schedule.

Therefore, after transmitting the MBS path registration request message, the ASN_GW 104 checks whether a response to the MBS path registration request message (MBS path registration response) is received from the base stations 108 belonging to the MBS zone in step 507. do. When the response is received from the base stations 108, the ASN_GW 104 proceeds to step 509 and transmits a response (session initiation response) to the MCBCS server 102 to establish a data path. As another example, the response to the data path establishment (session start response) message may be transmitted to the MCBCS server 102 irrespective of the result of the R6 response message. As described above, after setting the data path for the broadcast service, the ASN_GW 104 checks whether the corresponding R3 broadcast channel IP (R3 MIP) packet is received from the MCBCS server 102 in step 511. When the R3 broadcast data packet starts to be received according to the broadcast start, the ASN_GW 104 stores the R3 broadcast data packets received in step 513 in the corresponding MCID queue of the corresponding MBS zones.

In operation 517, the ASN_GW 104 packetizes the packets stored in the MCID queue in consideration of the burst size of a radio section. In other words, IP packets stored in the MCID queue are fragmented and packed according to the burst size of a radio section to generate a MAC SDU.

In step 517, the ASN_GW 104 timestamps the absolute broadcast time to each MAC SDU (Service Data Unit) generated through the packetization, and a Generic Routing Encapsulation (GRE) header before the MAC SDU. To create a tunneling packet (GRE packet). In this case, broadcast related information such as MBS zone ID and MCID is recorded in the GRE header.

In addition, the ASN_GW 104 generates an IP packet by attaching an R6 multicast IP header for multicast to the tunneling packet in step 519, attaches an L2 header (for example, an Ethernet header) to the IP packet, and then encodes a physical layer. Multicast to the base stations in the MBS zone. Steps 511 to 519 are continuously performed unless the data path for the corresponding MBS zone is released. In addition, when a plurality of ASN_GWs exist in one MBS zone, a specific one may be designated as an anchor ANS_GW, and the anchor ASN_GW may perform the above-described data and time synchronization.

In step 521, the ASN_GW 104 checks whether triggering indicating data path release for an arbitrary broadcast zone (or broadcast channel) is received from the MCBCS server 102. Here, the triggering for instructing release of the data path may be the session release request message described above. Upon receiving the session release request message, the ASN_GW 104 proceeds to step 523 and transmits an IGMP leave message to a multicast router connected to the MCBCS server 102 to transmit the IGMP leave message to the MCBCS server 102. Releases the data path between ASN_GW 104. In another embodiment, the ASN_GW 104 may perform IGMP ribs at an appropriate time after the broadcast ends according to the broadcast schedule.

After performing the IGMP rib, the ASN_GW 104 transmits the MBS path release triggering to the base stations 108 in the MBS zone in step 525. In this case, the MBS path release triggering may be the MBS path release request (MBS_path_DeReg_Req) message described above. Meanwhile, the base stations 108 receiving the MBS path release request message transmit an IGMP rib message to a multicast router connected to the ASN_GW 104 to establish a data path between the ASN_GW 104 and the base station 108. It releases and sends a response to the MBS path release request message (MBS path release response) to the ASN_GW 104.

Accordingly, the ASN_GW 104 checks whether the MBS path release response is received from the base stations 108 in step 527. When the MBS path release response message is received from the base stations in the MBS zone, the ASN_GW 104 receives the MBN path release response. In step 529, it transmits a response (session release response) to the data path release to the MCBCS server 102. As another example, the response to the data path release (session release response) message may be sent to the MCBCS server 102 irrespective of the result of the R6 response message.

In step 531, the ASN_GW 104 checks whether triggering indicating a data path change for a certain broadcast channel is received from the MCBCS server 102. Here, the triggering for instructing the data path change may be the session change request message described above.

Upon receiving the session change request message, the ASN_GW 104 proceeds to step 533 to change parameter information of the corresponding broadcast channel and to transmit MBS path change triggering to the base stations of the MBS zone serving the broadcast channel. In this case, the MBS path change triggering may be the MBS path change request (MBS_path_Mod_Req) message described above.

On the other hand, the base station 108 receiving the MBS path change request message changes the parameter information of the corresponding broadcast channel, and in response to the MBS path change request message MBS path change response (MBS_Path_Mod_Rsp) message to the ASN_GW 104 To send.

Accordingly, the ASN_GW 104 checks whether the MBS path change response message is received from the base stations 108 in step 535. Upon receiving the MBS path change response message, the ASN_GW 104 proceeds to step 537 to transmit a Session Modification Rep message to the MCBCS server 102. As another example, the session change response message may be transmitted to the MCBCS server 102 regardless of the result of the R6 response message.

6 shows a configuration of ASN_GW according to an embodiment of the present invention.

As shown, the ASN_GW includes a controller 600, an R3 interface 602, an R6 interface 604, a buffer 606, a packet synchronizer 608, and a tunneling packet generator 610.

Referring to FIG. 6, the controller 600 controls the overall operation of the ASN_GW 104. In addition, the controller 600 manages a variety of information for a broadcast service as shown in Table 2, and provides a broadcast service based on the information as shown in Table 2.

The R3 interface unit 602 interprets an IP packet received from the MCBCS server 102, generates a transmission IP packet, and transmits the generated IP packet to the MCBCS server 102. In this case, when it is determined that the received packet is signaling, the R3 interface unit 602 extracts signaling information from the received packet and provides it to the controller 600. In addition, the R3 interface unit 602 generates a packet including signaling information and transmits the packet to the MCBCS server 102 under the control of the controller 600.

The R6 interface unit 604 interprets the IP packet received from the base station 108, generates a transmission IP packet, and transmits the generated IP packet to the base station 608. In this case, when it is determined that the received packet is signaling, the R6 interface unit 604 extracts signaling information from the received packet and provides it to the controller 600. In addition, the R3 interface unit 604 generates a packet including signaling information and transmits the packet to the base station 108 under the control of the control unit 500.

When a Session Start Req message is received from the MCBCS server 102 according to the present invention, the control unit 600 controls the R3 interface unit 602 to join the IGMP to the MCBCS server 102 ( join). After performing the IGMP join, the controller 600 controls the R6 interface unit 604 to transmit a MBS path registration request (MBS_Path_Reg_Req) message to the base stations belonging to the MBS zone. After transmitting the MBS path registration request message, when the MBS path registration response message is received from the base station, the controller 600 controls the R3 interface unit 602 to start the session response to the MCBCS server 102 ( session start rsp) message. As another example, the session start response message may be transmitted to the MCBCS server 102 regardless of the result of the R6 response message.

As such, after setting the data path for the broadcast service, the R3 interface unit 602 classifies the received packet by the R3 broadcast channel IP address and provides the classified packets to the buffer 606. The buffer 606 stores the R3 broadcast packet from the R3 interface unit 602 in a corresponding MCID queue of the MBS zones, and outputs the packet under the control of the controller 600.

The packet synchronous unit 608 divides and packs the packets from the buffer 606 according to the burst size of the radio section to generate a MAC service data unit (SDU). The tunneling packet generation unit 610 timestamps the absolute broadcast time to each MAC SDU (Service Data Unit) from the packet synchronization unit 608, and attaches a GRE header to the MAC SDU before the tunneling packet (GRE). Packets) are generated and provided to the R6 interface unit 604. In this case, broadcast related information such as MBS zone ID and MCID may be recorded in the GRE header.

Then, the R6 interface unit 604 attaches the R6 multicast IP header for multicast to the GRE packet to generate an IP packet, attaches an L2 header (Ethernet header) to the IP packet, and physical layer to enable actual transmission. Encode and multicast to base stations in the MBS zone.

In addition, when a Session Release Req message is received from the MCBCS server 102 according to the present invention, the control unit 600 controls the R3 interface unit 602 to control the IGMP to the MCBCS server 102. Perform a leave. After performing the IGMP rib, the controller 600 controls the R6 interface unit 604 to transmit a MBS path release request (MBS_Path_DeReg_Req) message to the base stations belonging to the MBS zone. After transmitting the MBS path release request message, if the MBS path release response message is received from the base station, the controller 600 controls the R3 interface unit 602 to release the session release response to the MCBCS server 102 ( session release rsp) message. In this way, the data path is released. As another example, the session release response message may be transmitted to the MCBCS server 102 regardless of the result of the R6 response message.

In addition, when a Session Mod Req message is received from the MCBCS server 102 according to the present invention, the controller 600 changes parameter information (eg, air scheduling information, etc.) of the corresponding broadcast channel. The controller 600 controls the R6 interface 604 to transmit an MBS path change request (MBS_Path_Mod_Req) message to base stations belonging to the MBS zone serving the corresponding broadcast channel. After the MBS path change request message is transmitted, when the MBS path change response message is received from the base station, the controller 600 controls the R3 interface unit 602 to transmit the session change response to the MCBCS server 102. session Mod rsp) message. In this way, the parameters of the broadcast channel are changed. As another example, the session change response message may be transmitted to the MCBCS server 102 regardless of the result of the R6 response message.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

1 is a diagram illustrating a network structure according to an embodiment of the present invention.

2 is a diagram illustrating a procedure for setting a data path for a broadcast service according to an embodiment of the present invention.

3 is a diagram illustrating a procedure for releasing a data path for a broadcast service according to an embodiment of the present invention.

4 is a diagram illustrating a procedure for changing a data path for a broadcast service according to an embodiment of the present invention.

5 is a diagram illustrating an operation procedure of ASN_GW according to an embodiment of the present invention.

6 is a diagram illustrating a configuration of ASN_GW according to an embodiment of the present invention.

Claims (51)

In the method for providing a broadcast service in a cellular network, Transmitting, by the broadcast server, a session initiation request message to the control station to request the multicast connection setup before the MBS data is delivered; Setting, by the control station, a multicast connection between the broadcast server and the control station based on information of the session start request message; After setting the multicast connection, transmitting, by the control station, a response message to the session start request message to the broadcast server; Transmitting, by the control station, a path registration request message to at least one base station belonging to the corresponding broadcast zone in order to request R6 data path establishment and radio resource reservation; Establishing, by the at least one base station, a multicast connection between the control station and the base station based on the information of the path registration request message; And after setting up the multicast connection, the at least one base station, transmitting a path registration response message to the control station in response to the path registration request message. The method of claim 1, The control station establishes a data path between the broadcast server and the control station through an Internet group management protocol (IGMP) join, and the base station joins the control station through an Internet group management protocol (IGMP) join. And establishing a data path between the base station and the base station. The method of claim 1, The data path setting between the broadcast server and the control station is performed on a content basis, and the data path setting between the control station and the base station is performed on a broadcast zone basis. The method of claim 1, The session start request message includes: MBS zone ID, R3 broadcast channel IP address, (R3 broadcast channel IP vs MBS zone ID & MCID) mapping information, MCIDs corresponding to MBS zone ID, broadcast service start and end time, and MBS zone And at least one of air scheduling information, MCID-specific air scheduling information, air scheduling information on MBS MAP message, and network element address, transport type, source ID, and destination ID to which ASN_GW should perform IGMP Join & Leave. The method of claim 1, The route registration request message may include an MBS zone ID, an R6 multicast IP address, MCIDs corresponding to the MBS zone ID, a Generic Routing Encapsulation (GRE) key, a broadcast service start and end time (ToD), and air scheduling for each MBS zone. Information, air scheduling information for each MCID, air scheduling information for an MBS MAP message, and a network element address to which the base station should IGMP Join & Leave, transmission type, source ID, and destination ID. The method of claim 1, Receiving, by the broadcast server, a content registration request from a content server; And receiving, by the broadcast server, a content ID and a broadcast channel IP address for each content and generating a mapping table for each content. The method of claim 6, The content registration request, characterized in that at least one of the content type, service data rate, service area, service time. The method of claim 6, The mapping table stores a mapping relationship between content ID, broadcast channel IP address, service time, transmission rate, MCID, MBS zone ID, and transmission zone ID. The method of claim 1, The control station, R3 broadcast channel IP address, MBS zone ID and corresponding MCIDs, broadcast service start and end time, air scheduling information for each MBS zone, air scheduling information for each MCID, air scheduling information for MBS MAP message, GRE key, At least one of NE address, broadcast transmission type, R6 multicast IP address, (R3 broadcast channel IP address vs MBS zone ID & MCID) mapping relationship, and (R6 multicast IP vs MBS zone ID) mapping relationship to be controlled by IGMP Join & Leave It acquires and manages one from the network manager, The base station, R6 multicast IP address, MBS zone ID and corresponding MCIDs, broadcast service start and end time, MBS zone air scheduling information, MCID air scheduling information, MBS MAP message, air scheduling information, GRE key, base station And obtaining and managing at least one of the NE address, transport type, and (R6 multicast IP vs MBS zone ID) mapping relationship to be IGMP Join & Leave from the network manager. The method of claim 9, The mapping relationship between the information managed by the control station and the base station is as follows. R3 broadcasting channel IP address: MCID = 1: n R3 Broadcasting Channel IP Address: Content ID = 1: 1 MBS Zone ID: BSID = n: m MBS Zone ID: MCID = 1: n GRE key: (broadcasting zone ID, MCID) = 1: 1 MBS Zone ID: R6 Multicast IP Address = 1: 1 R6 Multicast IP Address: MCID = 1: n  The method of claim 1, When the MBS data transfer is completed, transmitting, by the broadcast server, a session release request message to a control station to request multicast release; Releasing, by the control station, the multicast connection between the broadcast server and the control station based on the information of the session release request message; After the release of the multicast connection, the control station transmitting a session release response message to the broadcast server in response to the session release request message; Transmitting, by the control station, a path release request message to at least one base station belonging to the corresponding broadcast zone to request R6 data path release and radio resource release; Releasing, by the at least one base station, the multicast connection between the control station and the base station based on the information of the path release request message; And after the release of the multicast connection, the at least one base station transmitting a route release response message to the control station in response to the request message in the route request message. The method of claim 11, The session release request message, characterized in that at least one of the MBS zone ID and the release MCID corresponding to the MBS zone ID. The method of claim 11, wherein the path release request message includes at least one of a base station identifier, an MBS zone ID, a GRE key, and release MCIDs corresponding to the corresponding MBS zone ID. The method of claim 1, Transmitting a session change request message to the control station by the broadcast server after setting the path; Changing, by the control station, parameter information of a corresponding broadcast channel in response to the session change request message; Transmitting, by the control station, a response message to the session change request message to the broadcast server; Transmitting, by the control station, a path change request message to at least one base station belonging to the corresponding MBS zone serving the corresponding broadcast channel; And transmitting, by the at least one base station, a path change response message to the control station to change parameter information of a corresponding broadcast channel in response to the path change request message. The method of claim 14, The session change request message includes at least one of an MBS zone ID, an MCID of a broadcast channel requiring change, and changed parameter information. The method of claim 14, The route change request message may include at least one of an MBS zone ID, MCIDs of broadcast channels requiring change, and changed parameter information. The method of claim 1, When the broadcast starts, the broadcast server multicasts or unicasts the broadcast packet to the control station using the R3 broadcast channel IP address, Storing, by the control station, a broadcast packet received using an R3 broadcast channel IP address in a corresponding MCID queue of corresponding broadcast zones; Generating a MAC (Media Access Control) service data unit (SDU) by packetizing the broadcast packet stored in the queue according to a burst size of a radio section; Generating, by the control station, time stamping the absolute broadcast time on the MAC SDU and attaching a GRE header to the MAC SDU to generate a tunneling packet; The control station further comprises the step of attaching an R6 multicast IP header to the tunneling packet to generate an IP packet, and multicasting the IP packet to base stations belonging to the corresponding broadcast zone. The method of claim 17, The GRE header comprises a MBS zone ID, MCID. The method of claim 17, And when there are a plurality of control stations in the broadcast zone, the base stations belonging to the broadcast zone receive broadcast traffic from one control station connected to a multicast router. The method of claim 1, When the emergency broadcast is received, the base station transmits MBS map information (MAP_IE) for the emergency broadcast during the listening window period for the terminal in the sleep state, and during the PLI (Paging Listening Interval) period for the terminal in the idle state. And transmitting the MBS map information. The method of claim 20, The MBS map information, CID, the location and size of the data burst containing the emergency broadcast information, characterized in that at least one of the air scheduling information. The method of claim 21, The CID is characterized in that the MCID (Multicast CID) fixed for emergency broadcasting. The method of claim 20, And the MCID, R3 / R6 broadcast channel IP address, and GRE key information for emergency broadcasting are configured in advance in the control station and the base station. A method of operating a control station for a broadcast service in a cellular network, Setting a data path between the broadcast server and the control station by a set time or a session start request message from the broadcast server before MBS data is delivered; Transmitting a session start response message to the broadcast server in response to the session start request message; After the data path is set, transmitting a path registration request message to at least one base station belonging to the corresponding broadcast zone; And receiving a path registration response message indicating a data path setting between the control station and the base station from the base station belonging to the broadcasting zone. The method of claim 24, The data path between the broadcast server and the control station and the data path between the control station and the base station are performed through an IGMP join, and data path setting between the broadcast server and the control station is performed in units of content. Data path setting between is performed in units of broadcast zones. The method of claim 24, The session start request message includes: MBS zone ID, R3 broadcast channel IP address, (R3 broadcast channel IP vs MBS zone ID & MCID) mapping information, MCIDs corresponding to MBS zone ID, broadcast service start and end time, and MBS zone And at least one of air scheduling information, MCID-specific air scheduling information, air scheduling information on MBS MAP message, and network element address, transport type, source ID, and destination ID to which ASN_GW should perform IGMP Join & Leave. The method of claim 24, The route registration request message may include an MBS zone ID, an R6 multicast IP address, MCIDs corresponding to the MBS zone ID, a Generic Routing Encapsulation (GRE) key, a broadcast service start and end time (ToD), and air scheduling for each MBS zone. Information, air scheduling information for each MCID, air scheduling information for an MBS MAP message, and a network element address to which the base station should IGMP Join & Leave, transmission type, source ID, and destination ID. The method of claim 24, The control station, R3 broadcast channel IP address, MBS zone ID and corresponding MCIDs, broadcast service start and end time, air scheduling information for each MBS zone, air scheduling information for each MCID, air scheduling information for MBS MAP message, GRE key, At least one of NE address, broadcast transmission type, R6 multicast IP address, (R3 broadcast channel IP address vs MBS zone ID & MCID) mapping relation, and (R6 multicast IP address vs MBS zone ID) mapping relation to be controlled by the control station. It acquires and manages one from the network manager, The base station, R6 multicast IP address, MBS zone ID and corresponding MCIDs, broadcast service start and end time, MBS zone air scheduling information, MCID air scheduling information, MBS MAP message, air scheduling information, GRE key, base station And obtaining at least one of the NE address, broadcast transmission type, (R6 multicast IP address vs MBS zone ID) mapping relationship to be IGMP Join & Leave from the network manager. The method of claim 28, The mapping relationship between the information managed by the control station and the base station is as follows. R3 broadcasting channel IP address: MCID = 1: n R3 Broadcasting Channel IP Address: Content ID = 1: 1 MBS Zone ID: BSID = n: m MBS Zone ID: MCID = 1: n GRE key: (broadcasting zone ID, MCID) = 1: 1 MBS Zone ID: R6 Multicast IP Address = 1: 1 R6 Multicast IP Address: MCID = 1: n The method of claim 24, When the MBS data transfer is completed, releasing a data path between the broadcast server and the control station by a set time or by a session release request message from the broadcast server; Transmitting a session release response message to the broadcast server in response to the session release request message; After the data path is released, transmitting a path release request message to at least one base station belonging to the corresponding broadcast zone; And receiving a path release response message indicating a data path release between the control station and the base station from a base station belonging to the broadcast zone. The method of claim 30, The session release request message, characterized in that at least one of the MBS zone ID, the release MCID corresponding to the MBS zone ID. The method of claim 30, The path release request message may include at least one of a base station identifier, an MBS zone ID, a GRE key, and release CIDs corresponding to the corresponding MBS zone ID. The method of claim 24, Changing parameter information of a corresponding broadcast channel by a session change request message from the broadcast server after setting a path; Transmitting a session change response message to the broadcast server in response to the session change request message; Transmitting, after changing the parameter information, a path change request message to at least one base station belonging to a corresponding broadcast zone serving a corresponding broadcast channel; And receiving a route change response message indicating a parameter change for the corresponding broadcast channel from a base station belonging to the broadcast zone. The method of claim 33, wherein The session change request message includes at least one of an MBS zone ID, an MCID of a broadcast channel requiring change, and changed parameter information. The method of claim 33, wherein The route change request message may include at least one of an MBS zone ID, MCIDs of broadcast channels requiring change, and changed parameter information. The method of claim 24, Receiving a broadcast packet from the broadcast server; Storing the received broadcast packet in a corresponding MCID queue of corresponding broadcast zones using an R3 broadcast channel IP address; Generating a media access control (MAC) service data unit (SDU) by packetizing the broadcast packet stored in the queue according to a burst size of a radio section; Generating a tunneling packet by time stamping the absolute broadcast time on the MAC SDU and attaching a GRE header to the MAC SDU; And generating an IP packet by attaching an R6 multicast IP header to the tunneling packet, and multicasting the IP packet to base stations belonging to a corresponding broadcast zone. The method of claim 36, The GRE header comprises a MBS zone ID, MCID. A control station apparatus for broadcast service in a cellular network, A first interface unit for interfacing with the broadcast server; A second interface unit for interfacing with the base station; When the session start request message is received from the broadcast server, the first interface unit is controlled to set a data path between the broadcast server and the control station, and a session start response message is transmitted to the broadcast server. The second interface unit is then used. And controlling the controller to transmit a path registration request message to base stations belonging to the corresponding broadcast zone, and to receive a path registration response message indicating a data path setting between the control station and the base station from the base stations. The method of claim 38, The data path between the broadcast server and the control station and the data path between the control station and the base station are performed through an IGMP join, and data path setting between the broadcast server and the control station is performed in units of content. Data path setting between the apparatus is characterized in that performed in the unit of broadcast zone. The method of claim 38, The session start request message includes: MBS zone ID, R3 broadcast channel IP address, (R3 broadcast channel IP address vs MBS zone ID & MCID) mapping information, MCIDs corresponding to MBS zone ID, broadcast service start and end time, MBS And at least one of zone air scheduling information, MCID air scheduling information, air scheduling information for MBS MAP message, network element address, transport type, source ID, and destination ID to which ASN_GW should perform IGMP Join & Leave. The method of claim 38, The route registration request message may include an MBS zone ID, an R6 multicast IP address, MCIDs corresponding to the MBS zone ID, a Generic Routing Encapsulation (GRE) key, a broadcast service start and end time (ToD), and air scheduling for each MBS zone. Information, air scheduling information for each MCID, air scheduling information for the MBS MAP message, and a network element address to which the base station should perform IGMP Join & Leave, transmission type, source ID, and destination ID. The method of claim 38, The control unit, R3 broadcast channel IP address, MBS zone ID and corresponding MCIDs, broadcast service start and end time, air scheduling information for each MBS zone, air scheduling information for each MCID, scheduling information for the MBS MAP message, GRE key, control At least one of NE address, broadcast transmission type, R6 multicast IP address, (R3 broadcast channel IP address vs MBS zone ID & MCID) mapping relationship, and (R6 multicast IP address vs MBS zone ID) mapping relationship that the station should perform IGMP Join & Leave. Obtaining and managing from the network manager. The method of claim 42, wherein The mapping relationship of the managed information is as follows. R3 broadcasting channel IP address: MCID = 1: n R3 Broadcasting Channel IP Address: Content ID = 1: 1 MBS Zone ID: BSID = n: m MBS Zone ID: MCID = 1: nGRE Key: (Broadcast Zone ID, MCID) = 1: 1 MBS Zone ID: R6 Multicast IP Address = 1: 1 R6 Multicast IP Address: MCID = 1: n The method of claim 38, When the session release request message is received from the broadcast server, the controller controls the first interface to release the data path between the broadcast server and the control station, and transmits a session release response message to the broadcast server. And controlling a second interface unit to transmit a path cancellation request message to base stations belonging to the corresponding broadcast zone, and receiving a path cancellation response message informing of data path release between the control station and the base station from the base stations. Device. The method of claim 44, The session release request message, characterized in that at least one of the MBS zone ID and the release MCID corresponding to the MBS zone ID. The method of claim 44, The path release request message may include at least one of a base station identifier, an MBS zone ID, a GRE key, and release MCIDs corresponding to the corresponding MBS zone ID. The method of claim 38, When the session change request message is received from the broadcast server, the controller changes parameter information of the corresponding broadcast channel, controls the first interface unit to transmit a session change response message to the broadcast server, and then the second interface. And transmitting a route change request message to base stations belonging to the corresponding broadcast zone serving the corresponding broadcast channel, and receiving a route change response message informing the parameter change of the corresponding broadcast channel from the base stations. Device. The method of claim 47, The session change request message includes at least one of an MBS zone ID, an MCID of a broadcast channel requiring change, and changed parameter information. The method of claim 47, The route change request message may include at least one of an MBS zone ID, MCIDs of broadcast channels requiring change, and changed parameter information. The method of claim 38, A buffer for storing the received broadcast packet from the first interface unit in a corresponding MCID queue of corresponding broadcast zones using an R3 broadcast channel IP address; A packet synchronization unit for packetizing the broadcast packet stored in the queue according to a burst size of a radio section to generate a media access control (SDU) service data unit (SDU); And a tunneling packet generation unit for time stamping the absolute broadcast time on the MAC SDU and generating a tunneling packet by attaching a GRE header to the MAC SDU. And the second interface unit attaches an R6 multicast IP header to the tunneling packet to generate an IP packet, and multicasts the IP packet to base stations belonging to a corresponding broadcast zone. 51. The method of claim 50, The GRE header includes an MBS zone ID and MCID.

Images