JP2012104975A - Mobile communication system, mobile station device, base station device, sgsn, ggsn, and mobile communication method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mobile communication system, etc. capable of effectively utilizing a network resource by allowing the counting function of a base station device to fix a control method to release the network resource.SOLUTION: A mobile communication system performs a broadcast data distribution by a multimedia broadcast/multicast service (MBMS) bearer service to a mobile station device which is connected from a broadcast multicast service center (BM-SC) to a base station device by way of a gateway GPRS support node (GGSN) and a serving GPRS support node (SGSN) with an MBMS bearer established therein. When the broadcast data distribution associated with a flow identifier included in an MBMS bearer context is stopped, the base station device transmits a session stop request associated with the MBMS bearer context to the SGSN, and stops the broadcast data distribution.

Description

  The present invention relates to a mobile communication system or the like that performs broadcast data distribution from a BM-SC to a mobile station apparatus connected to a base station apparatus via a GGSN and an SGSN in which an MBMS bearer is established, using an MBMS bearer service.

  In 3GPP, MBMS (Multimedia Broadcast / Multicast Service) is standardized as a method for providing an MBMS bearer service that performs multicast data distribution and broadcast data distribution by GPRS (General Packet Radio Service).

  For example, according to Non-Patent Document 1, an MBMS service area is defined as a range in which an MBMS session is performed. For example, a service area is set in units of regions such as nationwide and Kanto, and is configured by cells of a plurality of base station devices in the service area. Then, a broadcast distribution route is set in a radio access network such as UTRAN connected to the core network, and a base station device (NodeB) or a radio network control station (RNC) of each cell in the service area is a terminal (UE) An MBMS bearer is set in and the data is distributed.

  Such conventional broadcast data distribution is distributed in units of MBMS service areas, not in units of cells of the base station apparatus. Therefore, even when there is a cell in the MBMS service area where a terminal to be distributed is not located, broadcast data is distributed to the base station apparatus of that cell.

  In the future, such broadcast data distribution services are expected to diversify, such as an increase in broadcast services targeting only a narrow range in addition to the conventional broadcast service having a relatively wide service area.

  Furthermore, if the service forms diversify in this way, the broadcast data to be distributed will also be diversified from public use for wide distribution to those for the personal community, and the types are expected to increase significantly. .

  For example, as described in Non-Patent Document 2, there are use cases such as a guided tour of travel. In addition, for example, a broadcast service for customers in a customer collection facility such as a sports or concert venue or a shopping center is also conceivable. Furthermore, there may be a case where information is distributed only to the victims in the disaster-stricken area.

  In the prior art, communication channels such as MBMS bearers are established for all broadcast distribution data in a unified manner without optimizing with respect to the increasing flow of such service forms and distribution data. Regardless of the presence or absence, data was distributed to the communication channel.

  In recent years, a base station apparatus has started to study a counting function for counting terminals that receive broadcast data. When the base station apparatus detects that there is no receiving terminal, the wireless link communication band allocated for broadcast data delivery between the base station apparatus and the terminal is optimized by changing the mode or releasing the communication band. Use the resources of the section efficiently. Further, when the terminal appears again, the radio resources are reassigned. As described above, studies have been made on the efficient use of radio resources by the counting function.

TS 23.246, Technical Specification Group Services and Architecture; Multimedia Broadcast / Multicast Service (MBMS); Architecture and functional description 3GPP TR 22.947, Technical Specification Group Services and System Aspects; Study on Personal Broadcast Service

  The efficiency improvement based on the counting result of the conventional base station apparatus is only a method of efficiently using the resources of the wireless communication section between the base station apparatus and the terminal, and between the broadcast data distribution source apparatus and the base station apparatus. There was no way to efficiently use resources in the communication section inside the network.

  That is, even if the base station device detects that there is no terminal that receives the broadcast data by the counting function, the broadcast data is delivered from the broadcast distribution source device installed in the network to the base station device. Until now, there was no solution to efficiently use network resources by reducing such unnecessary traffic.

  As described above, the effective use of the radio resource between the base station apparatus and the terminal has been considered so far by the counting function, but the network resource in the network cannot be efficiently used.

  In the above-mentioned Non-Patent Document 1, a procedure for releasing network resources of a terminal is shown. However, this method detects that there is no data to be distributed by a broadcast data delivery device installed in the network. Only the procedure for releasing network resources is shown.

  In other words, there was a method of efficiently releasing and reallocating network resources led by the broadcast data distribution source device, but the base station device could not perform them.

  Further, in the conventional MBMS service, an MBMS bearer is established for each broadcast service, and resources for transmitting broadcast data are allocated. In this broadcast service, contents such as a plurality of video titles can be delivered, and these are managed as a flow. As described above, the MBMS bearer can transmit a plurality of flows.

  Therefore, when the base station apparatus detects that there is no data receiving terminal based on the counting result, the terminal has moved to a different base station apparatus without requesting resource release, or the power is turned off. When the base station apparatus detects the network resource, the network resource is not actually used, but the efficiency cannot be improved.

  For this purpose, network resources can be utilized more efficiently by not only stopping and releasing the resources for each broadcast service but also stopping the delivery for each flow of the MBMS service.

  In order to solve the above-described problems, an object of the present invention is to provide a mobile communication system or the like that can effectively use network resources by defining a control method for releasing network resources by a counting function of a base station apparatus. It is said.

In order to solve the above-described problem, the mobile communication system of the present invention includes:
BM-SC (Broadcast Multicast Service Center) is connected to the base station apparatus via GGSN (Gateway GPRS Support Node) and SGSN (Serving GPRS Support Node) where MBMS (Multimedia Broadcast / Multicast Service) bearers are established In a mobile communication system that performs broadcast data distribution to a mobile station device using an MBMS bearer service,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the MBMS bearer context is transmitted to the SGSN,
Broadcast data distribution is stopped.

In the mobile communication system of the present invention,
The base station apparatus releases MBMS bearer resources with the SGSN when the broadcast data distribution of all flow identifiers included in the MBMS bearer context, which is distributed to the mobile station apparatus, is stopped.

In the mobile communication system of the present invention,
The base station device
A confirmation message including a flow identifier for identifying the content is transmitted to the mobile station apparatus, and the number of mobile station apparatuses receiving broadcast data distribution is counted based on a response from the mobile station apparatus. ,
When the counted number is 0, the broadcast data distribution stop is determined.

In the mobile communication system of the present invention,
The confirmation message includes TMGI (Temporary Mobile Group Identify) in the service identifier and a flow identifier registered in the MBMS bearer context in a flow identifier for identifying the content.

In the mobile communication system of the present invention,
The base station apparatus stops transmission / reception of an IP multicast packet together with transmitting a session stop request to the SGSN.

In the mobile communication system of the present invention,
The SGSN is a flow included in the MBMS bearer context when there is no mobile station device performing broadcast data distribution associated with the flow identifier included in the MBMS bearer context in the mobile station device connected via the SGSN. Send a session stop request associated with the identifier to the GGSN,
Broadcast data distribution is stopped.

In the mobile communication system of the present invention,
The SGSN releases MBMS bearer resources with the SGSN when the broadcast data distribution of all flow identifiers included in the MBMS bearer context distributed to the mobile station apparatus connected via the SGSN is stopped. It is characterized by.

In the mobile communication system of the present invention,
The GGSN is a flow included in the MBMS bearer context when there is no mobile station device performing broadcast data distribution associated with the flow identifier included in the MBMS bearer context in the mobile station device connected via the GGSN. Send a session stop request associated with the identifier to the BM-SC;
Broadcast data distribution is stopped.

In the mobile communication system of the present invention,
The GGSN releases MBMS bearer resources with the BM-SC when the broadcast data distribution of all flow identifiers included in the MBMS bearer context that distributes to the mobile station apparatus connected via the GGSN is stopped. It is characterized by doing.

  The mobile station apparatus of the present invention is connected to the mobile communication system described in the above-mentioned invention.

The base station apparatus of the present invention
In a base station apparatus connected from a BM-SC to a mobile communication system that performs broadcast data distribution by an MBMS bearer service to a mobile station apparatus connected to the base station apparatus via the GGSN and the SGSN where the MBMS bearer is established,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier included in the MBMS bearer context is transmitted to the SGSN,
Broadcast data distribution is stopped.

Moreover, the base station apparatus of the present invention is
When broadcast data distribution of all flow identifiers included in the MBMS bearer context that is distributed to the mobile station apparatus is stopped, MBMS bearer resources with the SGSN are released.

The SGSN of the present invention is
In the SGSN connected from the BM-SC to the mobile communication system that performs broadcast data distribution by the MBMS bearer service to the mobile station device connected to the base station device via the GGSN and the SGSN where the MBMS bearer is established,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier of the MBMS bearer context is transmitted to the SGSN,
The SGSN is
Based on the session stop request transmitted from the base station device, in the mobile station device connected via the SGSN, when there is no mobile station device that performs broadcast data distribution in the flow identifier included in the MBMS bearer context Sends a session stop request associated with the flow identifier included in the MBMS bearer context to the GGSN,
The broadcast data distribution is stopped.

The SGSN of the present invention is
MBMS bearer resources with SGSN are released when broadcast data distribution of all flow identifiers included in an MBMS bearer context distributed to a mobile station apparatus connected via SGSN is stopped. .

The GGSN of the present invention is
In the GGSN connected from the BM-SC to the mobile communication system that performs broadcast data distribution by the MBMS bearer service to the mobile station device connected to the base station device via the GGSN and SGSN where the MBMS bearer is established,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier included in the MBMS bearer context is transmitted to the SGSN,
The SGSN is
When the broadcast data distribution associated with the flow identifier included in the MBMS bearer context is stopped based on the session stop request transmitted from the base station apparatus, the session associated with the flow identifier included in the MBMS bearer context Send a stop request to GGSN,
The GGSN is
Based on the session stop request transmitted from the SGSN, in the mobile station device connected via the GGSN, there is no mobile station device that performs broadcast data distribution associated with the flow identifier included in the MBMS bearer context. Transmits a session stop request associated with the flow identifier included in the MBMS bearer context to the BM-SC,
Broadcast data distribution is stopped.

The GGSN of the present invention is
MBMS bearer resources with BM-SC are released when broadcast data distribution of all flow identifiers included in an MBMS bearer context that distributes to a mobile station apparatus connected via GGSN is stopped And

The mobile communication method of the present invention
A mobile communication method of a mobile communication system for performing broadcast data distribution by MBMS bearer service from a BM-SC to a mobile station device connected to a base station device via a GGSN and an SGSN with an MBMS bearer established,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier included in the MBMS bearer context is transmitted to the SGSN,
The SGSN is
When the broadcast data distribution associated with the flow identifier included in the MBMS bearer context is stopped based on the session stop request transmitted from the base station apparatus, the session associated with the flow identifier included in the MBMS bearer context Send a stop request to GGSN,
The GGSN is
Based on the session stop request transmitted from the SGSN, in the mobile station device connected via the GGSN, there is no mobile station device that performs broadcast data distribution associated with the flow identifier included in the MBMS bearer context. Transmits a session stop request associated with the flow identifier included in the MBMS bearer context to the BM-SC,
Broadcast data distribution is stopped.

  According to the present invention, in a mobile communication system that performs broadcast data distribution by MBMS bearer service from a BM-SC to a mobile station apparatus connected to a base station apparatus via a GGSN and an SGSN with an established MBMS bearer, When the station apparatus stops the broadcast data distribution associated with the flow identifier included in the MBMS bearer context, the station apparatus transmits a session stop request associated with the MBMS bearer context to the SGSN, and stops the broadcast data distribution. Become.

  Thus, conventionally, the BM-SC (broadcast data distribution apparatus) can only lead the session to be paused, the base station apparatus can confirm whether the mobile station apparatus needs to be received, and there is no need for distribution. Even if it was detected, the session could not be stopped, but the base station device can lead the session stop procedure based on the result of necessity of reception of the mobile station device. Become.

It is a figure for demonstrating the outline of the mobile communication system in this embodiment. It is a figure for demonstrating the function structure of BM-SC in this embodiment. It is a figure which shows an example of a data structure of MBMS service DB memorize | stored in BM-SC in this embodiment. It is a figure which shows an example of a data structure of the MBMS bearer context memorize | stored in BM-SC in this embodiment. It is a figure for demonstrating the function structure of GGSN in this embodiment. It is a figure which shows an example of a data structure of the MBMS bearer context memorize | stored in GGSN in this embodiment. It is a figure which shows an example of a data structure of upstream control node DB memorize | stored in GGSN in this embodiment. It is a figure for demonstrating the function structure of SGSN in this embodiment. It is a figure which shows an example of a data structure of the MBMS bearer context memorize | stored in SGSN in this embodiment. It is a figure for demonstrating the function structure of NB in this embodiment. It is a figure which shows an example of a data structure of the MBMS bearer context memorize | stored in NB in this embodiment. It is a figure which shows an example of a data structure of the radio | wireless frame information memorize | stored in NB in this embodiment. It is a figure for demonstrating the flow of the procedure process in this embodiment. It is a figure for demonstrating the flow of the procedure process in this embodiment.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

[1. System configuration]
FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 when the present invention is applied. The mobile communication system 1 includes a BM-SC (Broadcast-Multicast Service Center) 10 that is a broadcast / multicast service center, a GGSN (Gateway GPRS Support Node) 20 that is a gateway device, and a SGSN (Serving GPRS Support Node) that is a service control device. 30 includes a core network 5 including NB 40, which is a base station apparatus, and a UE 50 which is a mobile station apparatus.

  The NB 40 is connected to the core network 5, and the UE 50 can be connected to the NB 40. Specifically, the GGSN 20 is connected to the lower level of the BM-SC 10, and the NB 40 is connected to the lower level of the GGSN 20 via the SGSN 30 or directly. Furthermore, UE50 is connected to the lower level of NB40.

  Here, in FIG. 1 of the present embodiment, each component device is described as one for convenience of explanation, but a plurality of devices are connected. For example, the mobile communication system 1 includes one or a plurality of GGSNs, and one or a plurality of SGSNs and NBs are connected to the lower layers of each GGSN. Also, one or more UEs can be connected to the NB.

[2. Device configuration]
Subsequently, the functional configuration of each apparatus will be described with reference to the drawings.

[2.1 BM-SC]
A functional configuration of the BM-SC 10 will be described with reference to FIG. In the BM-SC 10, a transmission / reception unit 110 and a storage unit 120 are connected to the control unit 100.

  The transmission / reception unit 110 is an interface unit connected to a network, and is connected to the GGSN 20 via the network, for example.

  The storage unit 120 is a functional unit that stores various programs and various data necessary for the operation of the BM-SC 10. The storage unit 120 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like. In the present embodiment, an MBMS service DB 122 and an MBMS bearer context 124 are stored.

  The MBMS service DB 122 is a DB that stores a service identifier for a distributable service by using a broadcast service including a plurality of contents as one MBMS bearer service. FIG. 3 shows an example of the data configuration of the MBMS service DB 122.

Here, various service identifiers are used. For example,
(1) TMGI (Temporary Mobile Group Identity) identifying MBMS bearer context
(2) Other identifiers (for example, identifiers assigned by operators who operate the BM-SC 10 and perform service businesses)
Etc. In the present embodiment, description will be made assuming that TMGI of (1) is used.

  Specifically, TMGI that identifies an MBMS bearer context generated for each service is used when broadcast data is distributed in the MBMS bearer service. Here, TMGI is temporarily assigned subscriber identification information used in the conventional mobile phone service, but is used as information for identifying the MBMS bearer service in the MBMS bearer service.

  The MBMS bearer context 124 is MBMS bearer management information that is generated for each MBMS bearer service and is established to deliver broadcast data. FIG. 4 shows an example of the data configuration of the MBMS bearer context 124.

  Specifically, an MBMS bearer service identifier such as TMGI (for example, “TMGI1”), an identifier of a session established for distribution (for example, “session ID”), and a flow identifier for identifying content to be distributed ( For example, “flow ID”), a mode for identifying whether it is a multicast mode or a broadcast mode (for example, “broadcast”), and status information (for example, “active” for managing whether the state of the MBMS bearer is active or suspended) ), A data delivery destination delivery node (eg, “GGSN20”), and a UE counter (eg, “N”).

  The distribution node stores information for specifying a node to be distributed, and stores, for example, an IP address (in the case of FIG. 4, the IP address of the GGSN 20). A plurality of distribution nodes can be stored.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

  The UE counter is the number of distribution terminals for each data content of the broadcast service. This is based on the number counted by the counting function of the base station apparatus, and is the number of terminals that the user is actually viewing.

  Furthermore, when the information of GGSN that is a plurality of distribution nodes is stored in the MBMS bearer context 124, the BM-SC 10 can store different UE counters for each GGSN and count the number of UEs. Therefore, the BM-SC 10 can store, for each content, the number of content viewing terminals distributed to the GGSN 20.

[2.2 GGSN]
Subsequently, the functional configuration of the GGSN 20 will be described with reference to FIG. In the GGSN 20, a transmission / reception unit 210 and a storage unit 220 are connected to the control unit 200.

  The transmission / reception unit 210 is an interface unit connected to a network, and is connected to the BM-SC 10, the SGSN 30, and the NB 40 via the network, for example.

  The storage unit 220 is a functional unit that stores various programs necessary for the operation of the GGSN 20 and various data. The storage unit 220 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like. In the present embodiment, the MBMS bearer context 222 and the upstream control node DB 224 are stored.

  The MBMS bearer context 222 is generated for each MBMS bearer service, and is management information necessary for delivering broadcast data. FIG. 6 shows an example of the data configuration of the MBMS bearer context 222.

  Specifically, an MBMS bearer service identifier such as TMGI (for example, “TMGI1”), an identifier of a session established for distribution (for example, “session ID”), and a flow identifier (for example, for identifying distribution content) , “Flow ID”), an IP multicast address (for example, “IP multicast address 1”) for performing IP multicast communication, and a mode (for example, “broadcast”) for identifying the multicast mode or the broadcast mode. , State information (for example, “active”) for managing whether the state of the MBMS bearer is active or suspended, a distribution node (for example, “SGSN30”) as a data distribution destination, and a UE counter (for example, “N”) include.

  The distribution node stores information for specifying a node to be distributed, and stores, for example, an IP address (in the case of FIG. 6, the IP address of the SGSN 30). A plurality of distribution nodes can be stored.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

An IP multicast address is stored for each content to be distributed. Therefore, a plurality can be stored. Moreover, it can also allocate for every service, In that case, a single IP multicast address is memorize | stored.

  The UE counter is the number of distribution terminals for each data content of the broadcast service. This is based on the number counted by the counting function of the base station apparatus, and is the number of terminals that the user is actually viewing.

  Furthermore, when the information of SGSN which is a some delivery node is memorize | stored in MBMS bearer context 222, GGSN20 can memorize | store the UE counter which is different for every SGSN, and can count the number of UEs. Therefore, the GGSN 20 can store the number of content viewing terminals distributed to the SGSN 30 for each content.

  The upstream control node DB 224 is a DB for storing information for specifying an upstream broadcast data distribution device. FIG. 7 shows an example of the configuration of the upstream control node DB 224. In the present embodiment, information related to the BM-SC 10 is stored, for example, the IP address of the BM-SC 10 is stored.

  The upstream control node DB 224 stores one upstream control node (BM-SC 10) as shown in FIG. Alternatively, a plurality of upstream control nodes (BM-SC) may be stored for each service. In that case, the information is stored for each MBMS bearer context that can be identified by TMGI or the like.

[2.3 SGSN]
Next, the functional configuration of the SGSN 30 will be described with reference to FIG. The SGSN 30 is configured such that a transmission / reception unit 310 and a storage unit 320 are connected to the control unit 300.

  The transmission / reception unit 310 is an interface unit connected to the network, and is connected to the GGSN 20 and the NB 40 via the network, for example.

  The storage unit 320 is a functional unit that stores various programs necessary for the operation of the SGSN 30 and various data. The storage unit 320 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like. In the present embodiment, an MBMS bearer context 322 is stored.

  The MBMS bearer context 322 is generated for each MBMS bearer service, and is management information necessary for delivering broadcast data. FIG. 9 shows an example of the data configuration of the MBMS bearer context 322.

  Specifically, an MBMS bearer service identifier such as TMGI (for example, “TMGI1”), an identifier of a session established for distribution (for example, “session ID”), and a flow identifier (for example, for identifying distribution content) , “Flow ID”), an IP multicast address (for example, “IP multicast address 1”) for performing IP multicast communication, and a mode (for example, “broadcast”) for identifying the multicast mode or the broadcast mode. , Status information for managing whether the state of the MBMS bearer is active or suspended (for example, “active”), a data distribution destination distribution node (for example, “NB40”), and an upper level distribution node (for example, “NB40”) "GGSN20") and UE counter (eg And a "N").

  Here, the distribution node and the higher-level distribution node store information for specifying the respective nodes, and for example, IP addresses (in the case of FIG. 9, NB40 and the IP address of the GGSN 20) are stored. A plurality of distribution nodes can be stored.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

  An IP multicast address is stored for each content to be distributed. Therefore, a plurality can be stored. Moreover, it can also allocate for every service, In that case, a single IP multicast address is memorize | stored.

  The UE counter is the number of distribution terminals for each data content of the broadcast service. This is based on the number counted by the counting function of the base station apparatus, and is the number of terminals that the user is actually viewing.

  Further, when the SGMS 30 stores information on NBs that are a plurality of distribution nodes in the MBMS bearer context 322, the SGSN 30 can store different UE counters for each NB and count the number of UEs. Therefore, the SGSN 30 can store the number of viewing terminals of content to be delivered to the eNB 40 for each content.

[2.4 NB]
Next, the functional configuration of the NB 40 that is the base station apparatus will be described with reference to FIG. In the NB 40, a transmission / reception unit 410 and a storage unit 420 are connected to the control unit 400.

  The transmission / reception unit 410 is an interface unit connected to the network, and is connected to the GGSN 20 and the SGSN 30 via the network, for example, so that the UE 50 can be connected.

  The storage unit 420 is a functional unit that stores various programs necessary for the operation of the NB 40 and various data. The storage unit 420 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like. In this embodiment, MBMS bearer context 422 and radio frame information 424 are stored.

  The MBMS bearer context 422 is generated for each MBMS bearer service, and is management information necessary for delivering broadcast data. In FIG. 11, an example of a data structure of the MBMS bearer context 422 is shown.

  Specifically, an MBMS bearer service identifier such as TMGI (for example, “TMGI1”), an identifier of a session established for distribution (for example, “session ID”), and a flow identifier (for example, for identifying distribution content) , “Flow ID”), an IP multicast address (for example, “IP multicast address 1”) for performing IP multicast communication, and a mode (for example, “broadcast”) for identifying the multicast mode or the broadcast mode. , Status information (for example, “active”) that manages whether the state of the MBMS bearer is active or suspended, a higher level distribution node (for example, “SGSN30”) that becomes a higher level distribution node, and a UE counter (for example, “N”) ) And are included.

  Here, the higher-level delivery node stores information for specifying the node, for example, an IP address (in the case of FIG. 11, the IP address of the SGSN 30) is stored.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

An IP multicast address is stored for each content to be distributed. Moreover, it can also allocate for every service, In that case, a single IP multicast address is memorize | stored.

  The UE counter is the number of distribution terminals for each data content of the broadcast service, and is based on the number counted by the counting function of the base station device. Specifically, it is the number of terminals that the user is actually viewing.

  The radio frame information 424 stores information on a radio frame for the NB 40 to transmit to the UE 50 through the radio section for each MBMS bearer service. FIG. 12 shows an example of the data structure of the radio frame information 424.

  Specifically, mode information (for example, “frame mode”) indicating the multicast mode or the unicast mode is stored for each identifier for identifying the MBMS bearer service (for example, for each TMGI). Furthermore, in the case of the unicast mode, identification information such as IMSI (International Mobile Subscriber Identity) of the UE 50 that delivers the frame is stored. Here, a plurality of UEs (identification information) for frame delivery can be stored.

[3. Procedure processing]
Subsequently, a procedure process of the mobile communication system 1 in the present embodiment will be described with reference to the drawings.

[3.1 Service announcement procedure]
As shown in FIG. 13, the BM-SC 10 first performs a service announcement procedure for the UE 50. The BM-SC 10 notifies the UE 50 of services and contents that can be distributed (S100).

  The UE 50 thereby detects the broadcast service. The BM-SC 10 notifies the UE 50 by notifying the service identifier that the service stored in the MBMS service DB 122 can be distributed. Furthermore, information describing a service such as a flow identifier such as a program title and a content title, and a distribution start time may be given and notified.

Here, various service identifiers are used. For example,
(1) TMGI
(2) Other identifiers (for example, identifiers that can be set by the carrier and can identify the MBMS bearer service)
Etc. are available. In the present embodiment, description will be made assuming that TMGI of (1) is used.

  Specifically, the flow identifier is stored in the MBMS bearer context 124, and a flow identifier corresponding to TMGI can be used.

  Various notification methods are conceivable. For example, SMS (Short Message Service) or the like is used to notify a pre-registered distributable UE or an unspecified number of UEs. Or the information may be posted on the WEB and the UE may acquire the information by accessing the WEB server.

[3.2 Session start procedure]
Next, the session start procedure will be described with reference to FIG. By the session start procedure, an MBMS bearer is established and a communication path is established.

  The BM-SC 10 specifies a service and transmits a session start request to the GGSN 20 (S300). Here, a TMGI for designating a service and a session identifier for identifying a session are generated and transmitted in a session start request. Furthermore, a flow included for each service is registered in advance, and a flow identifier for identifying each flow is included. This starts the session start procedure.

  Moreover, TMGI, a session identifier, and a flow identifier are registered in the MBMS bearer context 124 by generating the MBMS bearer context 124. Also, status information is registered actively. Here, a plurality of flow identifiers for each content can be stored.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

Further, information regarding the GGSN 20 is stored in the distribution node. A plurality of GGSNs can be registered in the distribution node.

  The registered delivery destination node (GGSN) may be stored in advance by the operator, or a list of delivery nodes (eg, GGSN 20) is stored for each MBMS service area, and the MBMS service is included in the session start request. Send including the area identifier. Then, the corresponding GGSN may be selected and registered based on the transmitted MBMS service area identifier.

  Here, the trigger for the BM-SC 10 to start the session start procedure may be triggered by the completion of the service announcement procedure described above, or may be started at an arbitrary timing due to the operator's policy or the like before that. May be.

  The session start request is transmitted to all GGSNs registered in the delivery node of the MBMS bearer context 124.

  The GGSN 20 receives the session start request, transmits a session start response to the BM-SC 10, and responds (S302). Also, the MBMS bearer context 222 is generated, TMGI, session identifier, and flow identifier are registered, and the state information is activated.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

  Information regarding the SGSN 30 is stored in the distribution node. A plurality of SGSNs can be registered in the distribution node.

  Note that the SGSN 30 that is a distribution node to be registered may be registered in advance by an operator, or a list of distribution nodes (such as SGSN 30) registered for each MBMS service area and a session transmitted from the BM-SC 10 The corresponding SGSN 30 may be selected based on the MBMS service area identifier included in the start request.

  Through the above procedure, an MBMS bearer, which is a delivery path that ensures communication quality for broadcast data delivery, is established between the BM-SC 10 and the GGSN 20.

  Furthermore, in order to perform transmission by the MBMS bearer by IP multicast communication, an IP multicast address is assigned and registered in the MBMS bearer context 222. A plurality of IP multicast addresses are assigned for each flow identifier and stored.

  Alternatively, a single IP multicast address may be assigned to each of a plurality of flows, and in that case, one IP multicast address may be registered for a plurality of flows.

  The GGSN 20 transmits a session start request (S304) to the SGSN 30 registered in the delivery node of the MBMS bearer context 222. In order to specify a service, the session start request includes TMGI, a session identifier, a flow identifier, and an IP multicast address.

  The session start request is transmitted to all SGSNs registered in the delivery node of the MBMS bearer context 222. Here, the SGSN to be transmitted may be different for each flow.

  The SGSN 30 receives the session start request, transmits a session start response to the GGSN 20, and responds (S310). Also, the MBMS bearer context 322 is generated, the TMGI included in the received message, the session identifier, the flow identifier, and the IP multicast address are registered, and the state is activated.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be stored.

  A plurality of IP multicast addresses can be registered for each flow identifier. Alternatively, a single IP multicast address may be assigned to each of a plurality of flows, and in that case, one IP multicast address is registered for the plurality of flows.

  Information regarding the NB 40 is stored in the distribution node. A plurality of NBs can be registered in the distribution node.

  The NB 40, which is a registered distribution node, may be registered in advance by an operator, or a list of distribution nodes (NB 40, etc.) is registered for each MBMS service area, and a session start request transmitted from the GGSN 20 is registered. A corresponding NB may be selected based on the included MBMS service area identifier.

  Furthermore, information (IP address in the present embodiment) related to the GGSN 20 serving as a higher-level delivery node that has transmitted the request is registered.

  Through the above procedure, an MBMS bearer that is a delivery path that secures communication quality for broadcast data delivery between the GGSN 20 and the SGSN 30 is established.

  The SGSN 30 transmits a session start request (S306) to the NB 40 registered in the delivery node of the MBMS bearer context 322. The session start request includes TMGI, a session identifier, a flow identifier, and an IP multicast address.

  The session start request is transmitted to all NBs registered in the delivery node of the MBMS bearer context 322. Here, the NB to be transmitted may be different for each flow.

  The NB 40 receives the session start request, transmits a session start response to the SGSN 30, and responds (S308). Also, an MBMS bearer context 422 is generated, TMGI, a session identifier, a flow identifier, and an IP multicast address are registered, and the state is activated.

  The flow identifier is stored for each content to be distributed. Therefore, a plurality of flow identifiers may be registered. Furthermore, a plurality of IP multicast addresses may be registered for each flow identifier.

  Alternatively, a single IP multicast address may be assigned to each of a plurality of flows, and in that case, one IP multicast address is registered for the plurality of flows.

  Furthermore, the information regarding SGSN30 used as the high-order delivery node which transmitted the request | requirement is registered. Through the above procedure, an MBMS bearer, which is a delivery path that secures communication quality for broadcast data delivery, between the SGSN 30 and the NB 40 is established.

  Here, the NB 40 performs IP multicast participation processing. The NB 40 refers to the MBMS bearer context 422 and makes a participation request using the IP multicast address corresponding to the service. Specifically, an IGMP Membership Report message is transmitted when communicating with IPv4, and an MLD Membership Report is transmitted when communicating with IPv6.

  Thereby, an IP multicast packet is delivered to the MBMS bearer established by BM-SC10, GGSN20, SGSN30, and NB40. Broadcast data is transmitted from the BM-SC 10 to the NB 40 by IP multicast.

  Further, the NB 40 performs radio resource allocation processing to be transmitted to the UE 50, and registers information for delivery in the radio frame information 424. Specifically, mode information indicating whether the radio frame mode is the multicast mode or the unicast mode is registered for each service identifier. TMGI can be used as the service identifier.

  In addition, when transmitting in the multicast mode, the frame is transmitted to an unspecified number of UEs, so there is no need to retain UE information, but when transmitting in the unicast mode, a radio frame is transmitted to each UE. In this case, the IMSI is held as UE information and registered as UE information in the activation procedure.

  With the above service announcement procedure and session start procedure, a communication path is established between the UE 50 and the BM-SC 10, and the data transmitted by the BM-SC 10 can be delivered to the NB 40.

  Here, in the above example, the service announcement procedure is performed and then the session start procedure is performed, but these may be mixed.

  Finally, the NB 40 transmits an MBMS start notification to the UE 50 (S316). The notification includes a service identifier for identifying the service and a flow identifier. Thereby, UE50 starts reception of broadcast data.

Here, various service identifiers are used. For example,
(1) TMGI registered in the MBMS bearer context 422
(2) Session ID registered in MBMS bearer context 422
(3) Other identifiers (for example, identifiers that can identify the MBMS bearer service between the NB 40 and the UE 50)
Etc. In the present embodiment, description will be made assuming that TMGI of (1) is used.

Furthermore, various types of flow identifiers are used. For example,
(1) Flow ID registered in MBMS bearer context 422
(2) Other identifiers (for example, identifiers that can identify content distributed between the NB 40 and the UE 50)
Etc. In the present embodiment, the flow ID of (1) is used. However, in the case of (2), the NB 40 registers the flow identifier and the flow identifier of the MBMS bearer context 422 in association with each other. It will be.

  Here, the NB-SC 10 may notify the UE 50 of the service identifier and the flow identifier by a service announcement procedure or the like without the NB 40 notifying the start of the MBMS. These notification methods can be selected and notified according to the policy of the operator.

  In the above example, the processing when the GGSN 20 receives a session start request has been described. However, when other GGSNs receive a session start request from the BM-SC 10, the same procedure as the GGSN 20 is performed.

  Similarly, in the SGSN, the processing when the SGSN 30 receives a session start request has been described. However, when other SGSNs receive a session start request from the GGSN, the same procedure as the SGSN 30 is performed.

  Similarly, in the NB, the processing when the NB 40 receives a session start request has been described. However, when other NBs receive a session start request from the SGNS, the same procedure as the NB 40 is performed.

  Similarly, in the UE, the process when the UE 50 receives a session start request has been described. However, when other UEs receive a session start request from the NB, the same procedure as the UE 50 is performed.

  Thereby, the broadcast data distributed by the BM-SC 10 is hierarchically delivered to the UE via a plurality of GGSNs, SGSNs, and NBs.

[3.3 Procedure for stopping distribution]
Next, the session stop procedure will be described with reference to FIG. An example in which the session stop procedure is started based on the counting procedure result in the NB 40 will be described, but the start trigger is not limited to this, and the procedure can be started from the NB 40.

  First, a counting procedure that triggers a session stop procedure will be described. The procedure is performed between the NB 40 and the UE 50. NB40 transmits the message which confirms whether it receives service including service identifier and a flow identifier with respect to UE50 connected.

  Here, the NB 40 transmits a message for confirming whether or not it receives a service addressed to the UE 50 registered in the radio frame information 424. However, the NB 40 may transmit it to all the UEs to be connected.

Here, various service identifiers are used. For example,
(1) TMGI registered in the MBMS bearer context 422
(2) Session ID registered in MBMS bearer context 422
(3) Other identifiers (for example, identifiers that can identify the MBMS bearer service between the NB 40 and the UE 50)
Etc. In the present embodiment, description will be made assuming that TMGI of (1) is used.

Furthermore, various types of flow identifiers are used. For example,
(1) Flow ID registered in MBMS bearer context 422
(2) Other identifiers (for example, identifiers that can identify content distributed between the NB 40 and the UE 50)
Etc. In the present embodiment, description will be made assuming that the flow ID (1) is used.

  When receiving the message, the UE 50 responds to the NB 40 including the service identifier and the flow identifier.

  Even if the UE 50 receives the MBMS service start notification and is in a state where broadcast data can be received, the UE 50 does not transmit a response when reception is not required, such as when the viewing application is temporarily turned off. It's okay.

Here, various service identifiers are used. For example,
(1) TMGI registered in the MBMS bearer context 422
(2) Session ID registered in MBMS bearer context 422
(3) Other identifiers (for example, identifiers that can identify the MBMS bearer service between the NB 40 and the UE 50)
Etc. In the present embodiment, description will be made assuming that TMGI of (1) is used.

Furthermore, various types of flow identifiers are used. For example,
(1) Flow ID registered in MBMS bearer context 422
(2) Other identifiers (for example, identifiers that can identify content distributed between the NB 40 and the UE 50)
Etc. In the present embodiment, description will be made assuming that the flow ID (1) is used.

  Thereby, NB40 can acquire the number of UE50 actually required for reception for every flow. The obtained number of UEs 50 is registered in the UE counter of the MBMS bearer context 422. The UE counter counts the number of UEs for each flow.

  Further, the confirmation message of the NB 40 may be transmitted without including the service identifier. In that case, when there is content of the service that needs to be received, the UE 50 responds including the service identifier and the flow identifier.

  The NB 40 that has received the response identifies the MBMS bearer context from the service identifier, and registers the number of UEs 50 that have responded to the UE counter for each flow. Thus, the counting procedure (S400) is completed.

  The NB 40 performs a counting process for confirming whether the UE counter managed for each flow of the MBMS bearer context 422 becomes zero (S402). When the UE counter reaches zero, it is decided to temporarily stop distribution. Therefore, it is detected that there is no UE 50 to receive for each service, and the distribution of the flow of the service is temporarily stopped.

  The NB 40 transmits a session stop request including the TMGI registered in the MBMS bearer context 422, the service identifier, the flow identifier, and the information of the NB 40 to the SGSN 30 (S404). The SGSN to be transmitted is resolved by the SGSN address of the MBMS bearer context 422. When all the flows to be managed are stopped, the state information of the MBMS bearer context 422 is set to standby.

  Here, when the UE counter becomes zero, distribution and reception of broadcast data corresponding to the flow are stopped (S408).

  Note that when the reception is stopped, an IP multicast leaving request may be transmitted. Specifically, when communicating with IPv4, IGMP Membership Report is transmitted, and when communicating with IPv6, MLD Membership Report is transmitted. This stops the distribution and reception of the IP multicast packet.

  The SGSN 30 receives the session stop request and transmits a session stop response to the NB 40 (S406).

  Further, the SGSN 30 sets a UE counter managed for the NB 40 and associated with the flow identifier to zero. Further, the distribution and reception of the broadcast data of the corresponding flow to the NB 40 are stopped (S414).

  Note that when the reception is stopped, an IP multicast leaving request may be transmitted. Specifically, when communicating with IPv4, IGMP Membership Report is transmitted, and when communicating with IPv6, MLD Membership Report is transmitted. This stops the distribution and reception of the IP multicast packet. By stopping the distribution and reception of the IP multicast packet, the distribution and reception of the broadcast data are stopped.

  Here, the SGSN 30 transmits a session stop request to the GGSN 20 if the flow identified by the stopped flow identifier is not distributed to other NBs (S410). The session stop request is transmitted including TMGI registered in the MBMS bearer context 322, the session identifier, the flow identifier, and the SGSN 30 information.

  Further, when there is no other flow to be transmitted to the NB 40 in the MBMS bearer context 322, the entry of the NB 40 is deleted from the distribution node, or marking indicating the suspension is performed. Specifically, if there is no other flow identifier whose UE counter is not zero, deletion or marking is performed.

  Further, when all entries of the NB 40 are deleted or marking indicating that the NB 40 is stopped, the SGSN 30 releases the MBMS bearer resources between the NBs 40. In other words, when the SGSN 30 stops delivering all the flow contents registered in the MBMS bearer context 322 to the NB 40, the SGSN 30 releases the resources of the MBMS bearer. In this case, the state information of the MBMS bearer context 322 is set to standby.

  When a plurality of other NBs 40 are registered in the delivery node of the MBMS bearer context 322 and the flow is being delivered, the session stop procedure is completed without transmitting a session stop request to the GGSN 20.

  The GGSN 20 receives the session stop request and transmits a session stop response to the SGSN 30 (S412).

  Further, the GGSN 20 zeroes the UE counter that is managed for the SGSM 30 and is associated with the flow identifier. Further, the distribution and reception of the broadcast data of the corresponding flow to the SGSN 30 is stopped (S420).

  Note that when the reception is stopped, an IP multicast leaving request may be transmitted. Specifically, when communicating with IPv4, IGMP Membership Report is transmitted, and when communicating with IPv6, MLD Membership Report is transmitted. This stops the distribution and reception of the IP multicast packet. By stopping the distribution and reception of the IP multicast packet, the distribution and reception of the broadcast data are stopped.

  Here, when the flow identified by the stopped flow identifier is not distributed to other SGSNs, the GGSN 20 transmits a session stop request to the BM-SC 10 (S410). The session stop request is transmitted including the TMGI registered in the MBMS bearer context 222, the session identifier, the flow identifier, and the GGSN 20 information.

  Here, when there is no flow to be transmitted to the SGSN 30 in the MBMS bearer context 222, the entry of the SGSN 30 is deleted from the distribution node, or marking indicating that it is stopped is performed. Specifically, if there is no other flow identifier whose UE counter is not zero, deletion or marking is performed.

  Further, when all the SGSN 30 entries are deleted or marked to indicate that they are stopped, the GGSN 20 releases the MBMS bearer resources between the SGSNs 30. In other words, when the GGSN 20 stops delivering all the flow contents registered in the MBMS bearer context 222 to the SGSN 30, the GGSN 20 releases the MBMS bearer resources. In this case, the state information of the MBMS bearer context 222 is set as standby.

  If a plurality of other SGSNs 30 are registered in the delivery node of the MBMS bearer context 222 and a flow is being delivered, the session stop procedure is completed without sending a session stop request to the BM-SC 10. To do.

  The BM-SC 10 receives the session stop request and transmits a session stop response to the GGSN 20 (S418). The session stop response is transmitted including the session identifier and the flow identifier.

  The BM-SC 10 sets the UE counter managed for the GGSN 20 and associated with the flow identifier to zero. When there is no other flow identifier other than the flow to be stopped in the MBMS bearer context, the entry of the GGSN 20 is deleted from the distribution node, or marking indicating that the flow is stopped is performed.

  Furthermore, when all entries of GGSN 20 are deleted or marking indicating suspension is performed, the state information of MBMS bearer context 124 is set to standby, and MBMS bearer resources between BM-SC 10 and GGSN 20 are released. To do. In other words, the BM-SC 10 releases MBMS bearer resources when there is no flow to be transmitted to the GGSN 20.

  When the UE counter managed for each flow of the MBMS bearer context 124 becomes zero, the broadcast data distribution is stopped (S422).

  Through the above procedure, the NB 40 can lead the session temporarily. The session stop procedure of the NB 40 can detect that the delivery for each flow delivered by the MBMS bearer that can be identified by TMGI or the like is unnecessary by the counting procedure.

  Furthermore, it can be started by detecting that the user is not viewing, as in the case where the user is not viewing because the application is turned off. The session stop procedure can be started with this detection as a trigger.

  Further, the session stop procedure may be performed only for the broadcast service. Conventional MBMS services include a multicast mode service and a broadcast mode service. As described above, the broadcast mode service is a service that does not authenticate the subscriber information management and reception of the UE 50, whereas the multicast mode service is a service for each service in response to the UE 50 participation request. This service delivers authentication procedures and distributes them.

  Therefore, the delivery in the multicast mode is delivery to a specific UE, and it is also assumed that the service may not permit the temporary release of the MBMS bearer and the inability to secure resources at the time of restart. For that purpose, a method of pausing only in the broadcast mode is necessary.

  As a specific method of permitting the session stop procedure only for the broadcast service, TMGI is generated when the BM-SC 10 generates the MBMS bearer context 124 in the session start procedure described with reference to FIG. Notify the SGSN 30 and NB 40 and simultaneously notify the mode.

  As to whether to notify the multicast mode or the broadcast mode, the mode may be managed in advance by the MBMS service DB 122 in association with each service, or the service activation procedure defined in the multicast mode communication establishment procedure may be used. You may manage by the presence or absence of the authentication procedure.

  In this way, each device recognizes that the service to be registered is the broadcast mode, and registers it in the MBMS bearer context. Specifically, the BM-SC 10 registers as broadcast in the mode of the MBMS bearer context 124, the GGSN 20 registers as broadcast in the mode of the MBMS bearer context 222, the SGSN 30 registers as broadcast in the mode of the MBMS bearer context 322, and the NB 40 Registers in the mode of the MBMS bearer context 422 as broadcast.

  Thereby, when deciding to stop a session, each device can refer to the MBMS bearer context, and can stop the session in the broadcast mode.

  Specifically, at the time of transmission of a broadcast session stop request (S404), the NB 40 transmits a stop request, releases the MBMS bearer, IP multicast distribution, and reception stop when the mode of the MBMS bearer context 422 is broadcast.

  When transmitting the broadcast session stop request (S410), the SGSN 30 performs stop request transmission, MBMS bearer release, IP multicast distribution, and reception stop when the mode of the MBMS bearer context 322 is broadcast.

  When transmitting the broadcast session stop request (S416), the GGSN 20 transmits a stop request, releases the MBMS bearer, performs IP multicast distribution, and stops receiving when the mode of the MBMS bearer context 222 is broadcast.

  When receiving the broadcast session stop request (S416), the BM-SC 10 releases the MBMS bearer or stops IP multicast distribution when the mode of the MBMS bearer context 124 is broadcast.

  Conventionally, in the BM-SC 10 that is the distribution source of content data, when there is no data to be transmitted for a certain period of time depending on the status of the distribution data, it is detected that there is no transmission data, and the BM-SC 10 leads the session. I could only pause. For this reason, the necessity of reception of the UE 50 can be confirmed by the NB 40, and even if it is detected that there is no need for distribution, the session cannot be stopped. According to the procedure of this embodiment, the NB 40 can lead the session stop procedure based on the result of necessity of reception of the UE 50.

[4. Modified example]
The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and the design and the like within the scope of the present invention are also within the scope of the claims. include.

  In each embodiment, a program that operates in each device is a program that controls a CPU or the like (a program that causes a computer to function) so as to realize the functions of the above-described embodiments. Information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) at the time of processing, then stored in various ROM or HDD storage devices, and read and corrected by the CPU as necessary. • Writing is performed.

  Here, as a recording medium for storing the program, a semiconductor medium (for example, a ROM, a non-volatile memory card, etc.), an optical recording medium / a magneto-optical recording medium (for example, a DVD (Digital Versatile Disc), an MO (Magnetoto) (Optical Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.), magnetic recording medium (eg, magnetic tape, flexible disk, etc.), etc. Also, the loaded program is executed. Thus, not only the functions of the above-described embodiment are realized, but also the functions of the present invention are realized by processing in cooperation with an operating system or other application programs based on the instructions of the programs. There is also.

  In addition, when distributing to the market, the program can be stored and distributed in a portable recording medium, or transferred to a server computer connected via a network such as the Internet. In this case, of course, the storage device of the server computer is also included in the present invention.

  In addition, a part or all of each device in the above-described embodiments may be realized as an LSI (Large Scale Integration) that is typically an integrated circuit. Each functional block of each device may be individually formed as a chip, or a part or all of them may be integrated into a chip. Further, the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. In addition, when integrated circuit technology that replaces LSI appears due to progress in semiconductor technology, it is of course possible to use an integrated circuit based on this technology.

10 BM-SC
100 Control Unit 110 Transmission / Reception Unit 120 Storage Unit 122 MBMS Service DB
124 MBMS Bearer Context 20 GGSN
200 Control Unit 210 Transmission / Reception Unit 220 Storage Unit 222 MBMS Bearer Context 224 Upstream Control Node DB
30 SGSN
300 Control Unit 310 Transmission / Reception Unit 320 Storage Unit 322 Bearer Context 40 NB
400 Control unit 410 Transmission / reception unit 420 Storage unit 422 MBMS bearer context 424 Radio frame information 50 UE

Claims (17)

BM-SC (Broadcast Multicast Service Center) is connected to the base station apparatus via GGSN (Gateway GPRS Support Node) and SGSN (Serving GPRS Support Node) where MBMS (Multimedia Broadcast / Multicast Service) bearers are established In a mobile communication system that performs broadcast data distribution to a mobile station device using an MBMS bearer service,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the MBMS bearer context is transmitted to the SGSN,
A mobile communication system, wherein broadcast data distribution is stopped.   The base station apparatus releases MBMS bearer resources with the SGSN when the broadcast data distribution of all flow identifiers included in the MBMS bearer context, which is distributed to the mobile station apparatus, is stopped. Item 4. The mobile communication system according to Item 1. The base station device
A confirmation message including a flow identifier for identifying the content is transmitted to the mobile station apparatus, and the number of mobile station apparatuses receiving broadcast data distribution is counted based on a response from the mobile station apparatus. ,
3. The mobile communication system according to claim 1, wherein when the counted number is 0, stop of the broadcast data distribution is determined.   4. The confirmation message includes TMGI (Temporary Mobile Group Identify) in the service identifier and a flow identifier registered in the MBMS bearer context in a flow identifier for identifying the content. The mobile communication system according to 1.   The mobile communication system according to any one of claims 1 to 4, wherein the base station apparatus stops transmission / reception of an IP multicast packet together with transmitting a session stop request to the SGSN. The SGSN is a flow included in the MBMS bearer context when there is no mobile station device performing broadcast data distribution associated with the flow identifier included in the MBMS bearer context in the mobile station device connected via the SGSN. Send a session stop request associated with the identifier to the GGSN,
The mobile communication system according to any one of claims 1 to 5, wherein broadcast data distribution is stopped.   The SGSN releases MBMS bearer resources with the SGSN when the broadcast data distribution of all flow identifiers included in the MBMS bearer context distributed to the mobile station apparatus connected via the SGSN is stopped. The mobile communication system according to claim 6. The GGSN is a flow included in the MBMS bearer context when there is no mobile station device performing broadcast data distribution associated with the flow identifier included in the MBMS bearer context in the mobile station device connected via the GGSN. Send a session stop request associated with the identifier to the BM-SC;
The mobile communication system according to any one of claims 1 to 7, wherein broadcast data distribution is stopped.   The GGSN releases MBMS bearer resources with the BM-SC when the broadcast data distribution of all flow identifiers included in the MBMS bearer context that distributes to the mobile station apparatus connected via the GGSN is stopped. The mobile communication system according to claim 8.   A mobile station apparatus connected to the mobile communication system according to any one of claims 1 to 9. BM-SC (Broadcast Multicast Service Center) is connected to the base station apparatus via GGSN (Gateway GPRS Support Node) and SGSN (Serving GPRS Support Node) where MBMS (Multimedia Broadcast / Multicast Service) bearers are established In a base station device connected to a mobile communication system that performs broadcast data distribution by MBMS bearer service to a mobile station device,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier included in the MBMS bearer context is transmitted to the SGSN,
A base station apparatus which stops broadcast data distribution.   The base station according to claim 11, wherein when the broadcast data distribution of all flow identifiers included in the MBMS bearer context for distribution to the mobile station apparatus is stopped, the MBMS bearer resource with the SGSN is released. Station equipment. BM-SC (Broadcast Multicast Service Center) is connected to the base station apparatus via GGSN (Gateway GPRS Support Node) and SGSN (Serving GPRS Support Node) where MBMS (Multimedia Broadcast / Multicast Service) bearers are established In an SGSN connected to a mobile communication system that performs broadcast data distribution by MBMS bearer service to a mobile station device,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier of the MBMS bearer context is transmitted to the SGSN,
The SGSN is
Based on the session stop request transmitted from the base station device, in the mobile station device connected via the SGSN, when there is no mobile station device that performs broadcast data distribution in the flow identifier included in the MBMS bearer context Sends a session stop request associated with the flow identifier included in the MBMS bearer context to the GGSN,
SGSN characterized by stopping broadcast data distribution.   MBMS bearer resources with SGSN are released when broadcast data distribution of all flow identifiers included in an MBMS bearer context distributed to a mobile station apparatus connected via SGSN is stopped. The SGSN according to claim 13. BM-SC (Broadcast Multicast Service Center) is connected to the base station apparatus via GGSN (Gateway GPRS Support Node) and SGSN (Serving GPRS Support Node) where MBMS (Multimedia Broadcast / Multicast Service) bearers are established In the GGSN connected to the mobile communication system that performs broadcast data distribution by the MBMS bearer service to the mobile station device,
In the broadcast data distribution, one or more contents are distributed,
The MBMS bearer context includes at least information of an MBMS bearer to be established by allocating an MBMS bearer resource in the MBMS bearer service, and a flow identifier for identifying the content,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier included in the MBMS bearer context is transmitted to the SGSN,
The SGSN is
When the broadcast data distribution associated with the flow identifier included in the MBMS bearer context is stopped based on the session stop request transmitted from the base station apparatus, the session associated with the flow identifier included in the MBMS bearer context Send a stop request to GGSN,
The GGSN is
Based on the session stop request transmitted from the SGSN, in the mobile station device connected via the GGSN, there is no mobile station device that performs broadcast data distribution associated with the flow identifier included in the MBMS bearer context. Transmits a session stop request associated with the flow identifier included in the MBMS bearer context to the BM-SC,
A GGSN characterized by stopping broadcast data distribution.   MBMS bearer resources with BM-SC are released when broadcast data distribution of all flow identifiers included in an MBMS bearer context that distributes to a mobile station apparatus connected via GGSN is stopped The GGSN according to claim 15. BM-SC (Broadcast Multicast Service Center) is connected to the base station apparatus via GGSN (Gateway GPRS Support Node) and SGSN (Serving GPRS Support Node) where MBMS (Multimedia Broadcast / Multicast Service) bearers are established A mobile communication method of a mobile communication system that performs broadcast data distribution to a mobile station device by MBMS bearer service,
The base station device
When stopping broadcast data distribution associated with the flow identifier included in the MBMS bearer context, a session stop request associated with the flow identifier included in the MBMS bearer context is transmitted to the SGSN,
The SGSN is
When the broadcast data distribution associated with the flow identifier included in the MBMS bearer context is stopped based on the session stop request transmitted from the base station apparatus, the session associated with the flow identifier included in the MBMS bearer context Send a stop request to GGSN,
The GGSN is
Based on the session stop request transmitted from the SGSN, in the mobile station device connected via the GGSN, there is no mobile station device that performs broadcast data distribution associated with the flow identifier included in the MBMS bearer context. Transmits a session stop request associated with the flow identifier included in the MBMS bearer context to the BM-SC,
A mobile communication method characterized by stopping broadcast data distribution.

Images