Source: https://patents.google.com/patent/EP2603049B1/en
Timestamp: 2020-01-26 22:06:54
Document Index: 699241542

Matched Legal Cases: ['art 1', 'art 2', 'art 3', 'arts 1', 'art 1', 'art 1', 'art 2', 'art 1', 'art 2', 'art 3']

EP2603049B1 - Control station, core network node, mobile communication system and communication method - Google Patents
Control station, core network node, mobile communication system and communication method Download PDF
EP2603049B1
EP2603049B1 EP13152689.9A EP13152689A EP2603049B1 EP 2603049 B1 EP2603049 B1 EP 2603049B1 EP 13152689 A EP13152689 A EP 13152689A EP 2603049 B1 EP2603049 B1 EP 2603049B1
EP13152689.9A
EP2603049A1 (en
2008-10-31 Priority to JP2008281441 priority Critical
2009-09-09 Application filed by NEC Corp filed Critical NEC Corp
2009-09-09 Priority to EP20090823416 priority patent/EP2352347A4/en
2013-06-12 Publication of EP2603049A1 publication Critical patent/EP2603049A1/en
2018-04-18 Publication of EP2603049B1 publication Critical patent/EP2603049B1/en
239000011162 core materials Substances 0 claims description title 28
3GPP (3rd Generation Partnership Projects) defines a service called "MBMS" (Multimedia Broadcast Multicast Service) (Non Patent Literature 1 ∼ 7).
Figure 1 illustrates an example of configuration of a mobile communication system of W-CDMA (Wideband-Code Division Multiple Access) that provides MBMS using an MBSFN (Non Patent Literature 1).
As shown in Figure 1, the related mobile communication system includes BM-SC (Broadcast Multicast-Service Center) 100, GGSN (Gateway GPRS Support Node, GPRS=General Packet Radio Service) 200, SGSN (Serving GPRS Support Node) 300, RNC (Radio Network Controller: control station) 400, Node B (NB) 500 and UE 800.
Figure 1 shows two RNCs 400-1 and 400-2 as RNC 400.
RNCs 400-1 and 400-2 are nodes provided with a function of controlling RAN 450. For example, RNCs 400-1 and 400-2 determine radio resources of S-CCPCH in cells 600 under their control, instruct Node B 500 to set the S-CCPCH, determine transmission timing for transmitting MBMS data in cell 600 under their control and transmit MBMS data to each Node B 500 in synchronization with the transmission timing. Since details of these operations are defined in 3GPP and are commonly known, descriptions thereof will be omitted. Assume that "under control" in the present specification refers to subordinate nodes connected to the own node, cells formed by the subordinate nodes, MBSFN clusters or the like.
Here, with reference to Figure 2, gains of UE 800 when MBSFN is used will be described in comparison with gains when MBSFN is not used. In Figure 2, (a) shows frequency utilization efficiency of UE 800 when MBSFN is used, disclosed in Table 7 of Non Patent Literature 2 and (b) shows frequency utilization efficiency of UE 800 when MBSFN is not used, disclosed in Table 8 of Non Patent Literature 2.
JP 2008/245060 A discloses that a MBMS session start request message that includes a transmission schedule is transmitted to a base station from a subscriber node
"Universal Mobile Telecommunications System (UMTS); UTRAN lu interface Radio Access Network Application Part (RANAP) signalling (3GPP TS 25.413 version 7.9.0 Release 7); ETSI TS 125 413; Chapter 8: RANAP Procedures", ETSI TS 125 413 V7.9.0, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 125 413, no. V7.9.0, 1 July 2008 (2008-07-01), pages 79-83 discloses a control station in a mobile communication system wherein the control station comprises a communication unit that is adapted to receive, from a core network node, a MBMS session start request message that includes a timing information including time to MBMS data transfer and an information related to a time of MBMS data transfer.
This object is achieved by a control station according to claim 1, a core network node according to claim 5, a mobile communication system according to claim 8 and a communication method according to claim 10; the dependent claims are related to further developments of the invention.
Figure 1 is a block diagram illustrating an example of a configuration of a related mobile communication system;
Figure 2 is a diagram illustrating gains of a UE when MBSFN is used;
Figure 3 is a diagram illustrating an example of a configuration of a mobile communication system of the present invention;
Figure 4 is a block diagram illustrating an example of a configuration of the BM-SC, GGSN, SGSN and RNC shown in Figure 3;
Figure 5 is a C-plane sequence chart illustrating an example of operation at the start of a session of MBMS in the mobile communication system of the present invention;
Figure 6 is a diagram illustrating a C-plane protocol stack used to transmit/receive the C-plane message shown in Figure 5;
Figure 7 is a diagram illustrating an example of a Session Start Request message transmitted from the BM-SC to GGSN in step S10 shown in Figure 5;
Figure 8 is a diagram illustrating an example of an MBMS Session Start Request message transmitted from the GGSN to SGSN in step S20 shown in Figure 5;
Figure 9 is a diagram illustrating an example of an MBMS Session Start Request message transmitted from the SGSN to RNC in step S30 shown in Figure 5;
Figure 10 is a block diagram illustrating another example of the configuration of the BM-SC, GGSN, SGSN and RNC shown in Figure 3;
Figure 11 is a diagram illustrating another example of the Session Start Request message transmitted from the BM-SC to GGSN in step S10 shown in Figure 5;
Figure 12 is a diagram illustrating another example of the MBMS Session Start Request message transmitted from the GGSN to SGSN in step S20 shown in Figure 5;
Figure 13 is a diagram illustrating another example of the MBMS Session Start Request message transmitted from the SGSN to RNC in step S30 shown in Figure 5;
Figure 14 is a diagram illustrating an example of a database stored in the storage unit of the RNC shown in Figure 10;
Figure 15 is a diagram illustrating a further example of the Session Start Request message transmitted from the BM-SC to GGSN in step S10 shown in Figure 5;
Figure 16 is a diagram illustrating a configuration of TMGI shown in Figure 15;
Figure 17 is a diagram illustrating an example of the MBMS Service ID shown in Figure 16 broken down into three parts;
Figure 18 is a diagram illustrating another example of the database stored in the storage unit of the RNC shown in Figure 10;
Figure 19 is a block diagram illustrating another example of the configuration of the mobile communication system of the present invention;
Figure 20 is a block diagram illustrating an example of the configuration of the BM-SC, GGSN, SGSN and RNC shown in Figure 19;
Figure 21 is a block diagram illustrating a further example of the configuration of the mobile communication system of the present invention;
Figure 22 is a block diagram illustrating an example of the configuration of the BM-SC and Node B shown in Figure 21;
Figure 23 is a block diagram illustrating a still further example of the configuration of the mobile communication system of the present invention; and
Figure 24 is a block diagram illustrating an example of the configuration of the BM-SC and Node B shown in Figure 23.
(1) First exemplary embodiment (1-1) Configuration of first exemplary embodiment
As shown in Figure 3, although an overall configuration of the mobile communication system of the present exemplary embodiment is the same as that in Figure 1, functions are added to BM-SC 100, GGSN 200, SGSN 300, and RNCs 400-1 and 400-2.
Thus, configurations of BM-SC 100, GGSN 200, SGSN 300, and RNCs 400-1 and 400-2 will be described with reference to Figure 4.
As shown in Figure 4, BM-SC 100 serves as a core network node to instruct RNCs 400-1 and 400-2 with respect to MBSFN information that is necessary to form MBSFN cluster 700 under the control of RNCs 400-1 and 400-2 via GGSN 200 and SGSN 300 and includes control unit 101 and communication unit 102.
In addition to the aforementioned operations, control unit 101 controls BM-SC 100 as a whole and performs various types of operation, for example, user authentication described in Figure 1, MBMS data management and delivery scheduling.
In addition to the aforementioned operation, control unit 301 controls SGSN 300 as a whole and performs various types of operation such as routing, mobility management and session management described in Figure 1.
Next, operation of the mobile communication system of the present exemplary embodiment at the start of MBMS, that is, at the start of a session, will be described according to a C-plane (Control Plane) sequence chart shown in Figure 5. The "C-plane" refers to a control plane and shows a protocol for signals used for control in a network.
In order to transmit/receive C-plane messages shown in Figure 5, the present exemplary embodiment uses a C-plane protocol stack shown in Figure 6 without changing it. Since this protocol stack is defined in 3GPP, detailed descriptions thereof will be omitted.
As shown in Figure 5, communication unit 102 of BM-SC 100 transmits a Session Start Request message to GGSN 200 at the start of a session of MBMS in step S10. Details of the Session Start Request message are described in Non Patent Literature 3.
In the present exemplary embodiment, control unit 101 of BM-SC 100 newly adds parameters of MBSFN-Frequency 12, MBSFN-Scrambling-Code 13, MBSFN-Channelisation-Code 14, MBSFN-Slot-Format 15 and MBSFN-Tx-Timing 16 in the Session Start Request message in step S10 as shown in Figure 7. Each Node B 500 uses the set values of frequency, scrambling code, channelization code and slot format in these parameters to set S-CCPCH, and each Node B 500 transmits MBMS data with a set value of the transmission timing.
Next, communication unit 202 of GGSN 200 returns a Session Start Response message which is a response message to the Session Start Request message to BM-SC 100 in step S 11.
The Session Start Request message and Session Start Response message transmitted and received between BM-SC 100 and GGSN 200 are transmitted through Gmb interface 151 shown in Figure 6 using Diameter Protocol 150. Details of Diameter Protocol 150 are described in Non Patent Literature 3.
In the present exemplary embodiment, control unit 201 of GGSN 200 newly adds parameters corresponding to MBSFN-Frequency 12, MBSFN-Scrambling-Code 13, MBSFN-Channelisation-Code 14, MBSFN-Slot-Format 15 and MBSFN-Tx-Timing 16, included in the above Session Start Request message as shown in Figure 8, in the MBMS Session Start Request message in step S20. Suppose the number of bits of each of these parameters is the same as the number of bits of the parameters included in the Session Start Request message.
The MBMS Session Start Request message and MBMS Session Start Response message transmitted and received between GGSN 200 and SGSN 300 are transmitted through Gn interface 251 shown in Figure 6, using GTP-C Protocol 250. Details of GTP-C Protocol 250 are described in Non Patent Literature 4.
In the present exemplary embodiment, control unit 301 of SGSN 300 adds a group called "MBSFN Information" as shown in Figure 9 in the MBMS Session Start Request message in step S30 and includes therein MBSFN-Frequency, MBSFN-Scrambling-Code, MBSFN-Channelisation-Code, MBSFN-Slot-Format and MBSFN-Tx-Timing as IE (Information Element) to be new parameters.
The MBMS Session Start Request message and MBMS Session Start Response message transmitted and received between SGSN 300, and RNC 400-1 and 400-2 are transmitted through Iu-PS interface 351 shown in Figure 6, using RANAP Protocol 350. Details of RANAP Protocol 350 are described in Non Patent Literature 5.
(2) Second exemplary embodiment (2-1) Configuration of second exemplary embodiment
The overall configuration of a mobile communication system of the present exemplary embodiment is similar to that in Figure 3.
Thus, as shown in Figure 10, RNC 400-1 adopts a configuration with storage unit 404 that stores a table which associates the above described MBSFN-Indicator with a combination of set values of radio resources added to the configuration in Figure 4. The same applies to RNC 400-2, too.
Since the C-plane sequence chart at the start of a session of MBMS of the mobile communication system of the present exemplary embodiment is similar to that in Figure 5, descriptions thereof will be omitted.
However, in the present exemplary embodiment, control unit 101 of BM-SC 100 newly adds parameters of MBSFN-Tx-Timing 16 and MBSFN-Indicator 17 as shown in Figure 11 in the Session Start Request message in step S10.
Furthermore, in the present exemplary embodiment, control unit 201 of GGSN 200 newly adds parameters corresponding to MBSFN-Tx-Timing 16 and MBSFN-Indicator 17 included in the above described Session Start Request message as shown in Figure 12 in the MBMS Session Start Request message in step S20.
Furthermore, in the present exemplary embodiment, control unit 301 of SGSN 300 includes MBSFN-Tx-Timing and MBSFN-Indicator as a new IE in MBSFN Information as shown in Figure 13 in the MBMS Session Start Request message in step S30.
Furthermore, in the present exemplary embodiment, storage unit 404 of RNC 400-1 stores a database as shown in Figure 14 beforehand.
Upon receiving a MBMS Session Start Request message in step S30, control unit 402 of RNC 400-1 refers to the database in Figure 14 using the value of MBSFN-Indicator included therein as an argument.
In the example in Figure 14, when the value of MBSFN-Indicator is 0, control unit 402 of RNC 400-1 determines not to use MBSFN and performs conventional processing of MBMS. In this case, the value of MBSFN-Tx-Timing is ignored.
(3) Third exemplary embodiment (3-1) Configuration of third exemplary embodiment
An overall configuration of a mobile communication system of the present exemplary embodiment is similar to that in Figure 3.
Furthermore, configurations of BM-SC 100, GGSN 200, SGSN 300, and RNCs 400-1 and 400-2 of the present exemplary embodiment are similar to those in Figure 10.
Since a C-plane sequence chart of the mobile communication system of the present exemplary embodiment at the start of a session of MBMS is similar to that in Figure 5, descriptions thereof will be omitted.
As shown in Figure 15, TMGI 18 is originally defined in the Session Start Request message. TMGI 18 has a configuration as shown in Figure 16. Details of the configuration of TMGI 18 are described in Non Patent Literature 7.
The present exemplary embodiment breaks down the 24 bits of MBMS Service ID 170 into three parts as shown in Figure 17. Part 1 corresponds to one bit, specifically the 24th bit, part 2 corresponds to seven bits, specifically the 17th to 23rd bits and part 3 corresponds to 16 bits, specifically the first to 16th bits. Parts 1 to 3 are assigned the following roles respectively.
Part 1: Use or non-use of MBSFN. "1" in this bit means use of MBSFN and "0" means non-use.
Storage unit 404 of RNC 400-1 stores a database as shown in Figure 18 beforehand.
Upon receiving the MBMS Session Start Request message in step S30, control unit 402 of RNC 400-1 determines to use MBSFN when "1" is set in the bit of part 1 of TMGI included in this and refers to the database in Figure 18 using the values of seven bits of part 2 as an argument.
In the database in Figure 14 used in the above described second exemplary embodiment, since the argument has 4 bits, only four set values of frequency, scrambling code, channelisation code and slot format can be defined.
By contrast, since the argument in the database in Figure 18 used in the present exemplary embodiment has 7 bits, the set value of transmission timing is also defined in the database.
For example, in the database in Figure 18, the transmission timing is definable only in minute units of transmission time. When the current time is 16:55 and "0" is set in the transmission timing, control unit 402 of RNC 400-1 performs scheduling such that MBMS data is transmitted from Node B 500 at 17:00 which corresponds to the next time "0" minutes are set.
On the other hand, control unit 402 of RNC 400-1 determines not to use MBSFN when "0" is set in the bit of part 1 of TMGI included in the MBMS Session Start Request message in step S30, does not handle the values of part 2 and handles the values of part 3 as MBMS Service ID.
(4) Fourth exemplary embodiment (4-1) Configuration of fourth exemplary embodiment
Furthermore, configurations of BM-SC 100, GGSN 200, SGSN 300, and RNCs 400-1 and 400-2 of the present exemplary embodiment are also similar to those in Figure 4 or Figure 10.
(5) Fifth exemplary embodiment (5-1) Configuration of fifth exemplary embodiment
Furthermore, configurations of BM-SC 100, GGSN 200, SGSN 300, and RNCs 400-1 and 400-2 of the present exemplary embodiment are also similar to those in Figure 10.
Storage unit 404 of RNCs 400-1 and 400-2 stores a database as shown in Figure 18 that associates MBSFN-Indicator with a combination of radio resources and transmission timing set values beforehand.
Hereinafter, at the start of a session of MBMS, processing will be carried out according to the C-plane sequence chart in Figure 5 using a method similar to that in the aforementioned third exemplary embodiment. Thus, the MBSFN-Indicator value selected above is reported from BM-SC 100 to RNCs 400-1 and 400-2 and MBSFN cluster 700 is formed.
(6) Sixth exemplary embodiment (6-1) Configuration of sixth exemplary embodiment
As shown in Figure 19, an overall configuration of the mobile communication system of the present exemplary embodiment is different from that in Figure 3 in the following points. Figure 19 shows three RNCs 400-1 ∼ 400-3 as RNC 400.
That is, in the mobile communication system of the present exemplary embodiment, only RNC 400-1 of RNCs 400-1 ∼ 400-3 under the control of SGSN 300 receives MBSFN information reported from SGSN 300 via Iu interface 410-3. Furthermore, RNC 400-1 and RNC 400-2 are connected via Iur interface 410-1 and RNC 400-1 and RNC 400-3 are connected via Iur interface 410-2. Though not shown in the figure, RNC 400-2 and RNC 400-3 are connected to SGSN 300 via an Iu interface.
Furthermore, as shown in Figure 20, when compared to Figure 10, communication unit 403 of RNC 400-1 is further configured to transmit/receive messages and MBMS data to/from another RNC 400 under the control of the same BM-SC 100.
On the other hand, when compared to Figure 10, communication unit 403 of RNC 400-2 is configured to transmit/receive messages and MBMS data to/from only another RNC 400 under the control of the same BM-SC 100 and not to directly transmit/receive messages and MBMS data to/from SGSN 300. The same applies to RNC 400-3, too.
However, in the aforementioned first to fifth exemplary embodiments, communication unit 102 of BM-SC 100 transmits a Session Start Request message to all RNCs 400-1 ∼ 400-3 under control thereof, whereas in the present exemplary embodiment, communication unit 102 transmits a Session Start Request message to only one RNC 400 (RNC 400-1 in Figure 19) under control thereof.
Avoiding transmission of a Session Start Request message to all RNCs 400-1 ∼ 400-3 can save the resources of the Iu interface between SGSN 300, and RNCs 400-2 and 400-3.
In this case, communication unit 403 of RNC 400-1 transfers the Session Start Request to another RNC 400 under the control of same BM-SC 100 to which MBMS data is to be transmitted (RNC 400-2, 400-3 in Figure 19) via Iur interfaces 410-1 and 410-2 respectively.
In this case, communication unit 403 of RNC 400-1 transfers the Session Start Request message and another message to another RNC 400 under the control of same BM-SC 100 to which MBMS data is to be transmitted (RNC 400-2, 400-3 in Figure 19) via Iur interfaces 410-1 and 410-2 respectively.
RNCs 400-1 ∼ 400-3 instruct setting of radio resources of S-CCPCH in cell 600 under their control and transmit MBMS data based on the MBSFN information directly or indirectly received from BM-SC 100.
Thus, the present exemplary embodiment can also form wide-range MBSFN cluster 700 extending over RNCs 400-1 ∼ 400-3.
When the present exemplary embodiment adopts a configuration of reporting an MBSFN-Indicator to RNC 400-1 using a method similar to that of the third exemplary embodiment, BM-SC 100, GGSN 200 or SGSN 300 may negotiate with RNCs 400-1 ∼ 400-3 over the MBSFN-Indicator as in the case of the fifth exemplary embodiment.
(7) Seventh exemplary embodiment (7-1) Configuration of seventh exemplary embodiment
As shown in Figure 21, the mobile communication system of the present exemplary embodiment includes BM-SC 100 and Node B 500.
Figure 21 omits nodes (GGSN and SGSN) between BM-SC 100 and Node B 500 and illustrates a configuration applicable to both networks of evolved HSPA and LTE.
Furthermore, Figure 21 illustrates three Nodes B 500-1 ∼ 500-3 as Nodes B 500 and these Nodes B 500-1 ∼ 500-3 are connected to a CN (not shown) including BM-SC 100.
As shown in Figure 22, the configuration of BM-SC 100 is similar to that in Figure 4 or Figure 10.
This allows time synchronization to be established between Nodes B 500-1 ∼ 500-3.
The method of establishing time synchronization between Nodes B 500-1 ∼ 500-3 is not limited to the aforementioned method by GPS, but the method described in Figure 4 may also be used.
This allows all cells 600 under the control of Nodes B 500-1 ∼ 500-3 to use the same radio resource for S-CCPCH.
Time synchronization is established between Nodes B 500-1 ∼ 500-3.
This allows all cells 600 under the control of Nodes B 500-1 ∼ 500-3 to transmit the same MBMS data at the same transmission timing.
Thus, all cells 600 under the control of Nodes B 500-1 ∼ 500-3 can transmit the same MBMS data using the same frequency and at the same transmission timing, and can thereby form wide-range MBSFN cluster 700 extending over Node B 500-1 ∼ 500-3.
The present exemplary embodiment can also form wide-range MBSFN cluster 700 extending over Nodes B 500-1 ∼ 500-3.
(8) Eighth exemplary embodiment (8-1) Configuration of eighth exemplary embodiment
As shown in Figure 23, the mobile communication system of the present exemplary embodiment is different from that in Figure 21 in that only Node B 500-1 of Nodes B 500-1 ∼ 500-3 under the control of BM-SC 100 receives a report about MBSFN information from BM-SC 100 and in that Nodes B 500-1 ∼ 500-3 are connected via an interface. The interface between Nodes B 500-1 ∼ 500-3 is an X2 interface in the case of an LTE network, for example. Though not shown in the figure, Nodes B 500-2 and RNC 500-3 are connected to BM-SC 100 via an interface.
Furthermore, as shown in Figure 24, communication unit 503 of Node B 500-1, compared to that in Figure 22, is further configured to transmit/receive messages and MBMS data to/from another Node B 500.
On the other hand, communication unit 503 of Node B 500-2, compared to that in Figure 22, is configured only to transmit/receive messages and MBMS data to/from another Node B 500 and not to directly transmit/receive these messages and MBMS data to/from BM-SC 100. The same applies to Node B 500-3, too.
In the present exemplary embodiment, BM-SC 100 can directly or indirectly instruct Nodes B 500-1 ∼ 500-3 with respect to MBSFN information, and can thereby form wide-range MBSFN cluster 700 extending over Nodes B 500-1 ∼ 500-3.
Subcarrier numbers and symbol numbers for allocating MBMS data are instructed. (Pattern 2)
MBMS data allocation time and frequency are additionally instructed. (Pattern 3)
A control station (400-1, 400-2) in a mobile communication system that includes base stations (500) adapted to transmit MBMS data to mobile stations (800), the control station (400-1, 400-2) comprising:
a communication unit (403) that is adapted to receive, from a core network node (300), a MBMS session start request message that includes a timing information including Time to MBMS Data Transfer and MBSFN information related to a transmission timing, a frequency, a scrambling code, a channelization and a slot format of the MBMS data, and
a time synchronization unit (401) adapted to establish time synchronization with another control station (400-1. 400-2) connected to the same core network node (300) for synchronously transmitting the same MBMS data using the same MBSFN information in all cells under the control of the core network node (300).
The control station according to claim 1, wherein
the MBSFN information related to the frequency indicates a frequency for transmitting the MBMS data.
The control station according to claim 1 or 2, wherein
the control station (400-1, 400-2) is adapted to receive, from the core network node (300), at least any one of a subcarrier numbers and symbol numbers for allocating MBMS data, MSMS data allocation time and frequency, and resource block numbers.
The control station according to claim 1, further comprising a control unit (402) that is adapted to perform a scheduling related to communication between the control station and the base station based on the MBSFN information.
A core network node (300) in a mobile communication system that includes a plurality of control stations (400-1, 400-2) connected to the core network (300) and base stations (500) connected to the control stations (400-1, 400-2) adapted to transmit MBMS data to a mobile stations (800), the core network node (300) comprising
a communication unit (302) that is adapted to transmit, to the plurality of control stations, a MBMS session start request message that includes a timing information including Time to MBMS Data Transfer and MBSFN information related to a transmission timing, a frequency, a scrambling code, a channelization code and a slot format of the MBMS data, such that the same MBMS data is synchronously transmitted using the same MBSFN information in all cells under the control of the core network node (300)
The core network node according to claim 4, wherein
The core network node according to claim 5 or 6, wherein
the core network node (300) is adapted to transmit, to the base stations (500), at least any one of a subcarrier numbers and symbol numbers for allocating MBMS data, MSMS data allocation time and frequency, and resource block numbers.
mobile stations (800);
base stations (500) adapted to transmit MBMS data to the mobile stations (800);
a plurality of control stations (400) which is connected to the base stations (500) are connected; and
a core network node (300) according to one of claims 4 to 6 which is connected to the plurality of control stations (400-1, 400-2);
wherein the core network node (300) is adapted to transmit, to the plurality of control stations (400-1, 400-2), a MBMS session start request message that includes a timing information including Time to MBMS Data Transfer and MBSFN information related to a transmission timing, a frequency, a scrambling code, a channelization code and a slot format of the MBMS data; and
wherein the control stations (400-1, 400-2) comprise each a communication unit (403) that is adapted to receive, from the core network node (300), the MBMS session start request message that includes the timing information including TIME to MBMS Data Transfer and the MBSFN information related to the transmission timing, the frequency, the scrambling code, the channelization code and the slot format of the MBMS data; and
a time synchronization unit (401) adapted to establish time synchronization with another control station (400-1, 400-2) connected to the same core network node (300) for synchronously transmitting the same MBMS data using the same MBSFN information in all cells under the control of the network node (300).
The mobile communication system according to claim 8, wherein the control stations (400-1, 400-2) comprise each
a control unit (402) that is adapted to perform a scheduling related to communication between the control station and the base station based on the MBSFN information.
A communication method performed by a mobile communication system comprising mobile stations (800), base stations (500) transmitting MBMS data to the mobile stations (800), a plurality of control stations (400-1, 400-2) connected to the base station and a core network node (300) connected to the plurality of control stations (400-1, 400-2), comprising the step of:
transmitting, from the core network node (300) to the plurality of control stations (400-1, 400-2), a MBMS session start request message that includes a timing information including Time to MBMS Data Transfer and MBSFN information related to a transmission timing, a frequency, a scrambling code, a channelization code and a slot format of the MBMS data, and establishing time synchronization by one control station (400-1, 400-2) with another control station (400-1, 400-2) connected to the same core network node (300) for synchronously transmitting the same MBMS data using the MBSFN information in all cells under the control of the core network node (300).
A communication method according to claim 10, wherein a scheduling related to communication between the control station and the base station is performed by the plurality of control stations (400-1, 400-2) based on the MBSFN information.
EP13152689.9A 2008-10-31 2009-09-09 Control station, core network node, mobile communication system and communication method Active EP2603049B1 (en)
JP2008281441 2008-10-31
EP20090823416 EP2352347A4 (en) 2008-10-31 2009-09-09 Mobile communication system, core network node, control station, base station, communication method and program
EP09823416.4 Division 2009-09-09
EP20090823416 Division EP2352347A4 (en) 2008-10-31 2009-09-09 Mobile communication system, core network node, control station, base station, communication method and program
EP2603049A1 EP2603049A1 (en) 2013-06-12
EP2603049B1 true EP2603049B1 (en) 2018-04-18
ID=42128671
EP20090823416 Withdrawn EP2352347A4 (en) 2008-10-31 2009-09-09 Mobile communication system, core network node, control station, base station, communication method and program
EP13152689.9A Active EP2603049B1 (en) 2008-10-31 2009-09-09 Control station, core network node, mobile communication system and communication method
US (3) US9113440B2 (en)
EP (2) EP2352347A4 (en)
JP (3) JP5718642B2 (en)
KR (3) KR101277102B1 (en)
CN (2) CN102204369B (en)
WO (1) WO2010050303A1 (en)
EP3242497A1 (en) * 2004-07-29 2017-11-08 Samsung Electronics Co., Ltd. Method for providing notifications for multi-media broadcast/multicast service
JP4641273B2 (en) * 2006-03-24 2011-03-02 三菱電機株式会社 Base station concentrator and inter-device synchronization control method in base station concentrator system
WO2008054318A2 (en) * 2006-11-01 2008-05-08 Telefonaktiebolaget Lm Ericsson (Publ) Method for content synchronization when broadcasting data in a wireless network
JP4369958B2 (en) 2007-01-15 2009-11-25 株式会社エヌ・ティ・ティ・ドコモ Communication system, multicast switching apparatus, and communication method
JP2008281441A (en) 2007-05-10 2008-11-20 Aloka Co Ltd Radiation measuring device
EP2286605A1 (en) * 2008-06-10 2011-02-23 Telefonaktiebolaget L M Ericsson (PUBL) Sae application for mbms
2009-09-09 EP EP20090823416 patent/EP2352347A4/en not_active Withdrawn
2009-09-09 CN CN200980143468.3A patent/CN102204369B/en active IP Right Grant
2009-09-09 US US13/122,476 patent/US9113440B2/en active Active
2009-09-09 KR KR20137000579A patent/KR101277102B1/en active IP Right Grant
2009-09-09 KR KR20127021565A patent/KR101277105B1/en active IP Right Grant
2009-09-09 EP EP13152689.9A patent/EP2603049B1/en active Active
2009-09-09 CN CN201510587799.3A patent/CN105142219B/en active IP Right Grant
2009-09-09 WO PCT/JP2009/065717 patent/WO2010050303A1/en active Application Filing
2009-09-09 KR KR20117007732A patent/KR101277099B1/en active IP Right Grant
2009-09-09 JP JP2010535726A patent/JP5718642B2/en active Active
2014-02-19 JP JP2014029481A patent/JP2014112938A/en active Pending
2014-11-19 JP JP2014234275A patent/JP5910705B2/en active Active
2015-07-09 US US14/795,200 patent/US9942727B2/en active Active
2018-02-21 US US15/901,311 patent/US10477360B2/en active Active
"Universal Mobile Telecommunications System (UMTS); UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling (3GPP TS 25.413 version 7.9.0 Release 7); ETSI TS 125 413; Chapter 8: RANAP Procedures", ETSI TS 125 413 V7.9.0, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 125 413, no. V7.9.0, 1 July 2008 (2008-07-01), pages 79 - 83, XP002713956 *
JP5910705B2 (en) 2016-04-27
KR20120112801A (en) 2012-10-11
KR20110053469A (en) 2011-05-23
CN105142219B (en) 2019-05-07
KR101277105B1 (en) 2013-06-20
CN102204369A (en) 2011-09-28
US20180192257A1 (en) 2018-07-05
CN105142219A (en) 2015-12-09
KR101277102B1 (en) 2013-06-20
JP2015073297A (en) 2015-04-16
US20150312728A1 (en) 2015-10-29
KR101277099B1 (en) 2013-06-20
JPWO2010050303A1 (en) 2012-03-29
US9942727B2 (en) 2018-04-10
EP2352347A4 (en) 2013-11-13
KR20130020830A (en) 2013-02-28
JP2014112938A (en) 2014-06-19
CN102204369B (en) 2015-10-21
US10477360B2 (en) 2019-11-12
US20110182228A1 (en) 2011-07-28
WO2010050303A1 (en) 2010-05-06
EP2352347A1 (en) 2011-08-03
US9113440B2 (en) 2015-08-18
JP5718642B2 (en) 2015-05-13
EP2603049A1 (en) 2013-06-12
CN101371519B (en) 2012-12-12 Encoding beacon signals to provide identification in peer-to-peer communication
US8638706B2 (en) 2014-01-28 Method and apparatus for scheduling and synchronizing a multimedia broadcast/multicast service
JP2009010978A (en) 2009-01-15 Radio communication system for providing multimedia broadcast and multicast service (mbms)
AU2003264960B2 (en) 2005-12-15 Providing multicast services in a point-to-multipoint manner for a radio communication system
EP2903377A1 (en) 2015-08-05 Mobile communication system
2013-06-12 AC Divisional application: reference to earlier application
Ref document number: 2352347
Ref document number: 1184005
Ipc: H04W 88/12 20090101ALN20171115BHEP
Ipc: H04L 12/18 20060101ALN20171115BHEP
Ipc: H04W 72/00 20090101AFI20171115BHEP
Ipc: H04W 88/12 20090101ALN20171117BHEP
Ipc: H04W 72/00 20090101AFI20171117BHEP
Ipc: H04L 12/18 20060101ALN20171117BHEP
Ref document number: 991759
Ref document number: 602009051919