Method for transmitting data of multicast broadcast service using superframe header in mobile wireless connection system
Claim Score by NHIP
Abstract
There is provided a method of transmitting multicast broadcast service (MBS) data using a superframe including a plurality of subframes in a mobile wireless connection system, the method including transmitting MBS MAP indication information indicating the first at least one first resource unit of an MBS region in the beginning of an MBS scheduling interval (MSI) and MBS control information including subframe offset information; transmitting an MBS MAP through the first resource unit; and transmitting an MBS burst indicated by the MBS MAP, wherein the subframe offset information including an index of the subframe at a point where the MBS burst is ended.

Term
Projected expiry 3 August 2031.
- Priority
- Filed
- Published
- Today
- Projected expiry
13 claims: 2 independent, 11 dependent
- 1Broadest claimClaim Score 56, average(NHIP)A method of transmitting multicast broadcast service (MBS) data using a superframe comprising a plurality of subframes in a mobile wireless connection system, the method comprising:transmitting MBS MAP indication information indicating the first at least one first resource unit of an MBS region in the beginning of an MBS scheduling interval (MSI) and MBS control information comprising subframe offset information;transmitting an MBS MAP through the first resource unit;and transmitting an MBS burst indicated by the MBS MAP, wherein the subframe offset information comprising an index of the subframe at a point where the MBS burst is ended.
- 12A method of receiving multicast broadcast service (MBS) data by a mobile station using a superframe comprising a plurality of subframes in a mobile wireless connection system, the method comprising:receiving MBS MAP indication information indicating the first at least one first resource unit of an MBS region in the beginning of an MBS scheduling interval (MSI) and MBS control information comprising subframe offset information;receiving an MBS MAP through the first resource unit;and receiving an MBS burst indicated by the MBS MAP, wherein the subframe offset information comprising an index of the subframe at a point where the MBS burst is ended.
Independent claims2
59 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001This application claims the benefit of priority of Korean Patent Application No. 10-2009-0084734 filed on Sep. 9, 2009 and Korean Patent Application No. 10-2010-0088568 filed on Sep. 9, 2010, which are incorporated by reference in their entirety herein.
BACKGROUND
00021. Field of the Invention
0003The present invention relates to a mobile wireless access system supporting a mobile multicast broadcast service, and more particularly to a method of providing a multicast broadcast service using a superframe header.
00042. Related Art
00053GPP (3rd Generation Partnership Project) LTE (long term evolution) and IEEE (Institute of Electrical and Electronics Engineers) 802.16m have been developed as a candidate for the next-generation wireless communication system. The 802.16m standard has two aspects, modification from the existing 802.16e standards as continuity from the past and standards for the next-generation international mobile telecommunications (IMT)-Advanced system as continuity to the future. Accordingly, the 802.16m standard has to not only keep compatibility with a mobile WiMAX system based on the 802.16e standard but also satisfy all advanced requirements for the IMT-Advanced system.
0006The wireless communication system generally uses one bandwidth for transmitting data. For example, a second-generation wireless communication system uses a bandwidth of 200 KHz˜1.25 MHz, and a third-generation wireless communication system uses a bandwidth of 5 MHz˜10 MHz. To support increased transmission capacity, the 3GPP LTE or 802.16m has recently continued to increase the bandwidth up to 20 MHz or higher. The increase of the bandwidth is necessary for increasing the transmission capacity, but it may cause high power consumption if supporting a broad bandwidth even when a required service level is low.
0007The IEEE 802.16m system supports evolved multicast broadcast service (E-MBS, which can be simply called MBS). The E-MBS is a point-to-multipoint system where data packets are simultaneously transmitted from one source to a plurality of destinations. The broadcast means capability for transmitting contents to all users. The multicast means contents directed toward a certain group of users subscribed for receiving a certain service. Here, it is possible to support static multicast and dynamic multicast.
0008If a base station provides the MBS and one base station manages many MBS zones, in the worst case, system information may have to be updated per period of the superframe header transmitted from the base station. Further, if the system does not notify what subframe is an MBS subframe, even a mobile station that receives only a unicast service performs decoding the MBS subframe. In this case, the unicast mobile station cannot perform decoding this subframe. Therefore, if this operation is repeated, the unitcast mobile station determines that there is a problem in synchronization with the system, and unnecessarily performs the update for the synchronization. Accordingly, there is needed a method of transmitting MBS data without unnecessarily performing the update.
SUMMARY
0009The present invention is to efficiently provide a multicast broadcast service (MBS) using an MBS MAP message and an MBS frame.
0010In an aspect of the present invention, there is provided a method of transmitting multicast broadcast service (MBS) data using a superframe including a plurality of subframes in a mobile wireless connection system, the method including: transmitting MBS MAP indication information indicating the first at least one first resource unit of an MBS region in the beginning of an MBS scheduling interval (MSI) and MBS control information including subframe offset information; transmitting an MBS MAP through the first resource unit; and transmitting an MBS burst indicated by the MBS MAP, wherin the subframe offset information including an index of the subframe at a point where the MBS burst is ended.
0011In another aspect of the present invention, there is provided a method of receiving multicast broadcast service (MBS) data by a mobile station using a superframe including a plurality of subframes in a mobile wireless connection system, the method including: receiving MBS MAP indication information indicating the first at least one first resource unit of an MBS region in the beginning of an MBS scheduling interval (MSI) and MBS control information including subframe offset information; receiving an MBS MAP through the first resource unit; and receiving an MBS burst indicated by the MBS MAP, wherein the subframe offset information including an index of the subframe at a point where the MBS burst is ended.
0012According to the present invention, a system update may be minimized in a mobile wireless access system supporting the MBS, and the MBS service may be more efficiently provided and con tenuously managed.
BRIEF DESCRIPTION OF THE DRAWINGS
0013<figref idrefs="DRAWINGS">FIG. 1</figref> shows a wireless communication system.
0014<figref idrefs="DRAWINGS">FIG. 2</figref> shows a frame structure and a data transmission method used in a mobile wireless access system supporting a multicast broadcast service.
0015<figref idrefs="DRAWINGS">FIG. 3</figref> is a flowchart showing an MBS data transmission method according to an exemplary embodiment of the present invention.
0016<figref idrefs="DRAWINGS">FIG. 4</figref> shows an example of an MBS frame structure according to an exemplary embodiment of the present invention.
DESCRIPTION OF EXEMPLARY EMBODIMENTS
0017Below, exemplary embodiments of the present invention will be described in detail with reference to accompanying drawings. In giving reference numerals to elements of the respective drawings, it will be noted that the same reference numerals refer to the same elements even though they are shown in different drawings. Further, detailed descriptions may be omitted if it is determined that the detailed descriptions about relevant well-known configuration or function may be beside the point of the present specification while describing the exemplary embodiments of this specification.
0018<figref idrefs="DRAWINGS">FIG. 1</figref> shows a wireless communication system.
0019Referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, a wireless communication system <b>10</b> includes at least one base station (BS) <b>11</b>. Each BS <b>11</b> provides a communication service to certain local regions (generally called cells) <b>15</b><i>a, </i><b>15</b><i>b </i>and <b>15</b><i>c. </i>Also, the cell may be divided again into a plurality of regions (also called sectors). A mobile station (MS) <b>12</b> may be fixed or mobile, which may also be called user equipment (UE), a motile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, a personal digital assistant (PDA), a wireless modem, a handheld device, etc. The BS <b>11</b> generally refers to a fixed station to communicate with the MS <b>12</b>, which may also be called an evolved-node B (eNB), a base transceiver system (BTS), an access point (AP), etc. Further, a packet flow of uplink or downlink between the BS and MS is called a service flow.
0020A multicast broadcast service (MBS) has certain quality of service (QoS) and one service flow, and is provided as being simultaneously mapped to many users. To receive the MBS, a user receiving the corresponding service sets up a parameter and a service flow. The BS providing the MBS belongs to a specific MBS zone, and common contents transmitted based on the corresponding service flow are transmitted as being divided by multicast identifiers (IDs) (multicast station identifier (STID) or E-MBS ID, hereinafter referred to as the E-MBS ID) within each MBS zone. The E-MBS ID is a common ID assigned to a corresponding user for receiving the MBS service. At this time, the MBS contents are transmitted to a region divided as one zone, in which each MBS zone is divided by an MBS zone ID. This content has one channel or service flow ID (FID). At this time, the FID forms a pair with the relevant E-MBS ID, which is assigned to each MBS connection. One user may be assigned with many FIDS, and the MBS contents that belong to one E-MBS ID may be transmitted as being distinguished by the FID.
0021<figref idrefs="DRAWINGS">FIG. 2</figref> shows a frame structure and a data transmission method used in a mobile wireless access system supporting the MBS.
0022Referring to <figref idrefs="DRAWINGS">FIG. 2</figref>, a superframe may include four frames. Each frame includes a plurality of subframes. Each superframe includes a suferframe header (SFH), in which the SFH is a unit of transmitting a plurality of frames and transmitted to the MS while including essential system parameters and system configuration information.
0023A primary superframe header (P-SFH) may be transmitted per superframe, and may be included in the first subframe of each superframe. The P-SFH defines whether to transmit or change the secondary superframe header (S-SFH), and a transmission period may correspond to one or more superframes. The P-SFH may allow the MS to acquire the latest essential system parameters and system configuration information applied to the system on the basis of an S-SFH change count and an S-SFH change bitmap.
0024The system parameters and the system configuration information are updated as follows. The MS receives and stores the S-SFH change count and S-SFH change bitmap included in the P-SFH. If a previously stored S-SFH change count is equal to a newly received S-SFH change count, the S-SFH may not be updated since a previously received S-SFH and a newly received S-SFH are the same information. On the other hand, if a previously stored S-SFH change count is not equal to a newly received S-SFH change count, it is determined that system information is updated. At this time, it is ascertained whether difference in a bit number between a previously stored S-SFH change bitmap and a newly received S-SFH change bitmap is equal to difference between the previously received S-SFH change count and the newly received S-SFH change count. If the two differences are the same, it is determined that the system information of the BS and the system information received by the MS are synchronized with each other, and thus the MS updates the system information by receiving an S-SFH subpacket shown as changed from the S-SFH change bitmap. If the two differences are not the same, it is determined that the system information of the BS and the system information received by the MS are not synchronized with each other, and thus the MS updates the system information by receiving all S-SFH subpackets.
0025In the case that unicast data and multicast data are divided and transmitted by time division multiplexing (TDM), a specific subframe (e.g., an MBS region) is assigned for transmitting MBS data. A transmission format and size of MBS data may be informed through an MBS MAP message, and the MBS MAP may be included per subframe where the MBS data is carried or may be included periodically. A location of the
0026MBS MAP may be informed by the SFH (generally, S-SFH), and the location of the MBS MAP to be next transmitted may be informed through the MBS MAP as well as the SFH. A certain pattern appears in the system between the MBS MAP and the following MBS MAP, and this certain pattern is called an MBS scheduling interval (MSI). Every MBS zone may have one MSI. One BS may manage one or more MBS zones and MSIs. Accordingly, the MSs initiating the MBS service operates in such a manner to receive MBS data by ascertaining a location of the first MBS MAP from the S-SFH, and then receive an MBS MAP, thereby searching the next MBS MAP.
0027By the way, if the transmission period of the S-SFH is not equal to the transmission period of the MBS MAP, a transmission location of the MBS MAP has to be informed through the system information of the S-SFH. However, the system information may be changed per S-SFH transmission period. In this case, if the BS manages many MBS zones, in the worst case it is inefficient since the system information may need to be updated from the BS per S-SFH period.
0028Further, if it is not informed by the system what subframe is the MBS subframe, even the MS receiving only the unicast service performs decoding the MBS subframe. If so, the unicast terminal cannot perform decoding the subframe since the MBS subframe includes no map information element (IE). Therefore, if this operation is repeated, the unicast MS determines that there is a problem in synchronization with the system, and unnecessarily performs the update for the synchronization.
0029Below, a method of transmitting MBS data with a minimum system update will be described.
0030<figref idrefs="DRAWINGS">FIG. 3</figref> is a flowchart showing an MBS data transmission method according to an exemplary embodiment of the present invention.
0031Referring to <figref idrefs="DRAWINGS">FIG. 3</figref>, MBS MAP indication information indicating the first at least one first resource unit of an MBS region in the beginning of the MSI and MBS control information including subframe offset information are transmitted (S<b>310</b>). The MBS MAP is transmitted through the first resource unit (S<b>320</b>). An MBS burst indicated by the MBS MAP is transmitted (S<b>330</b>).
0032The MBS MAP may be received on the basis of the MBS MAP indication information, and the MBS MAP may be transmitted through the first at least one resource unit of the MBS region in the beginning of the MSI. The MBS region may be informed through the SFH-SP2 and system configuration descriptor (SCD) message.
0033Here, the MBS MAP may include the MBS MAP indication information that indicates the location of the following MBS MAP. The first MBS MAP may be received from only the SFH, but there is no need of acquiring information about the MBS MAP from the SFH next time since the MBS MAP indicates the following MBS MAP. Accordingly, there is no need of continuously updating the SFH.
0034Also, the MBS MAP includes MBS region indication information that indicates the MBS region about the FID on the basis of information about the E-MBS ID and FID. Below, the MBS region indication information will be described in detail.
0035At this time, the MBS MAP indication information may be transmitted through a control message instead of the SFH. For example, the MBS MAP indication information may be transmitted through a MAC management message, a MAC header, a map information element, or a control channel. Also, the MBS MAP indication information may be transmitted through both the SFH and the control message.
0036<figref idrefs="DRAWINGS">FIG. 4</figref> shows an example of an MBS frame structure according to an exemplary embodiment of the present invention.
0037Referring to <figref idrefs="DRAWINGS">FIG. 4</figref>, to minimize the system update of the S-SFH, the SFH includes the MBS MAP indication information first transmitted after transmission of the S-SFH and parameters related to the transmission. Here, the MBS MAP indication information is information of indicating the location of the MBS MAP to be transmitted next time, which may include a superframe number, a frame index, a subframe index, a modulation and coding scheme (MCS), and resource information. Table 1 shows the format of the SFH.
0000<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="21pt" align="left" /><colspec colname="1" colwidth="98pt" align="left" /><colspec colname="2" colwidth="56pt" align="left" /><colspec colname="3" colwidth="42pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" rowsep="1">TABLE 1</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry>Syntax</entry><entry>Size (bits)</entry><entry>Notes</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>SFH IE ( ) {</entry><entry /><entry /></row><row><entry /><entry>. . .</entry><entry /><entry /></row><row><entry /><entry>Next MBS MAP Point IE ( )</entry><entry /><entry>Table 2</entry></row><row><entry /><entry>. . .</entry><entry /><entry /></row><row><entry /><entry>}</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0038Table 2 shows the MBS MAP indication information.
0000<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="14pt" align="left" /><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="91pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" rowsep="1">TABLE 2</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry>Size</entry><entry /></row><row><entry /><entry>Syntax</entry><entry>(bits)</entry><entry>Notes</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>Next MBS MAP Point</entry><entry /><entry /></row><row><entry /><entry>IE ( ) {</entry><entry /><entry /></row><row><entry /><entry>Superframe Number</entry><entry>[TBD]</entry><entry /></row><row><entry /><entry>Frame Index</entry><entry>2</entry><entry>0b00: 1<sup>st </sup>frame</entry></row><row><entry /><entry /><entry /><entry>0b01: 2<sup>nd </sup>frame</entry></row><row><entry /><entry /><entry /><entry>0b10: 3<sup>rd </sup>frame</entry></row><row><entry /><entry /><entry /><entry>0b11: 4<sup>th </sup>frame</entry></row><row><entry /><entry>Subframe Index</entry><entry>3</entry><entry>0b000: 1<sup>st </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b001: 2<sup>nd </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b010: 3<sup>rd </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b011: 4<sup>th </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b100: 5<sup>th </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b101: 6<sup>th </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b110: 7<sup>th </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry /><entry>0b111: 8<sup>th </sup>subframe of the</entry></row><row><entry /><entry /><entry /><entry>frame</entry></row><row><entry /><entry>MCS</entry><entry>[4]</entry><entry>MCS depends on supported</entry></row><row><entry /><entry /><entry /><entry>modes, 16 modes.</entry></row><row><entry /><entry>Resource Information</entry><entry /><entry /></row><row><entry /><entry>}</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0039Here, the superframe number refers to a least significant bit (LSB) of a superframe number of the MBS MAP to be transmitted next time, and the MSI may be set as a power of 2 for more efficient transmission. The frame index is an index for indicating a location of a frame where the MBS MAP to be transmitted next time is located among the frames included in the superframe indicated by the superframe number. The subframe index is an index for indicating a location of a subframe where the MBS MAP to be transmitted next time is located among the subframes included in the frame indicated by the frame index. The MCS refers to a modulation and coding scheme for the MBS MAP to be transmitted next time, and is varied depending on supported modes. The supported modes are 16 modes. The resource information refers to MBS region resource information of the MBS MAP to be transmitted next time.
0040The SFH of the first superframe may indicate a transmission location of the MBS MAP included in the second superframe. The MBS MAP indicates the MBS region of the second superframe, and the MBS MAP itself is also included in the second superframe. At this time, the SFH includes the MBS MAP indication information comprising the transmission location of the MBS MAP included in the second superframe, thereby indicating the transmission location of the MBS MAP. In this case, because the first MBS MAP is indicated by the SFH of the previous superframe, there is no need of updating the SFH to separately indicate the MBS MAP. Accordingly, there is no need of updating the S-SFH per superframe. Here, the second superframe is nothing but an example. Alternatively, the SFH of the first superframe may indicate the MBS MAPS included in the third and fourth superframes.
0041The SFH may be updated with new information after transmitting information about the MBS MAP to be transmitted next time.
0042The MBS MAP may include the MBS MAP indication information and the MBS region indication information for indicating the MBS region. The following Table 3 shows the format of the MBS MAP message.
0000<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="98pt" align="left" /><colspec colname="2" colwidth="49pt" align="center" /><colspec colname="3" colwidth="70pt" align="left" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE 3</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry>Size</entry><entry /></row><row><entry>Syntax</entry><entry>(bits)</entry><entry>Notes</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>MBS MAP Message format ( ) {</entry><entry /><entry /></row><row><entry>MBS Region IE ( )</entry><entry /><entry>Table 4</entry></row><row><entry>Next MBS MAP Point IE ( )</entry><entry /><entry>Table 2</entry></row><row><entry>Number of E-MBS ID (i)</entry><entry>[TBD]</entry><entry /></row><row><entry>For (i=0;i<Number of E-MBS</entry><entry /><entry /></row><row><entry>ID; i++) {</entry><entry /><entry /></row><row><entry>E-MBS ID</entry><entry>12</entry><entry /></row><row><entry>Number of FID (k)</entry><entry>[TBD]</entry><entry /></row><row><entry>For (k=0;k<umber of</entry><entry /><entry /></row><row><entry>FID; k++) {</entry><entry /><entry /></row><row><entry>FID</entry><entry> 4</entry><entry /></row><row><entry>Frame offset for MBS</entry><entry> 2</entry><entry>1: current frame</entry></row><row><entry>region</entry><entry /><entry>2: (current frame</entry></row><row><entry /><entry /><entry>+1) th frame</entry></row><row><entry /><entry /><entry>. . . </entry></row><row><entry /><entry /><entry>N: (currentframe+n-</entry></row><row><entry /><entry /><entry>1) th frame</entry></row><row><entry>Subframe offset for MBS</entry><entry> 3</entry><entry>0b000: 1st subframe</entry></row><row><entry>Region</entry><entry /><entry>of the frame</entry></row><row><entry /><entry /><entry>. . . </entry></row><row><entry /><entry /><entry>0b111: 8th subframe</entry></row><row><entry /><entry /><entry>of the frame</entry></row><row><entry>MCS</entry><entry>[4]</entry><entry>MCS depends on</entry></row><row><entry /><entry /><entry>supported mode, 16</entry></row><row><entry /><entry /><entry>modes.</entry></row><row><entry>Resource Information</entry><entry /><entry /></row><row><entry>Allocation pattern</entry><entry /><entry /></row><row><entry>}</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0043The MBS MAP may include the number of E-MBS IDs, and if there is a plurality of E-MBS IDs, the MBS MAP may include values of the respective E-MBS IDs. Also, the MBS MAP may include the transmission location and resource information of the MBS MAP to be transmitted next time, or the superframe number, frame index and MCS included in the SFH. At this time, the number of E-MBS IDs is the number of E-MBS IDs managed by the BS or the number of E-MBS IDs indicated by the MBS MAP.
0044If there is a plurality of FIDs, the MBS MAP may include the number of FIDs and each value of FID with respect to each E-MBS ID. At this time, the number of FIDs is a total number of FIDs corresponding to the service flow per relevant E-MBS ID or the number of FIDs shown in the current MBS MAP with regard to the relevant E-MBS ID.
0045Referring to the table 3, the frame offset for the MBS region, the subframe offset for the MBS region, the MCS, the resource information, and the allocation pattern for transmitting the relevant MBS region are provided with regard to each FID.
0046Here, the frame offset refers to a frame location of the MBS region to be first transmitted after the MBS MAP is transmitted with respect to each FID. The subframe offset refers to a subframe location of the MBS region to be first transmitted after the MBS MAP is transmitted with respect to each FID. Also, the subframe offset includes an index of a subframe at a point where the MBS burst is ended, and the first subframe of the first frame is reserved for transmitting the superframe header. Here, any MBS burst is not transmitted through the superframe header. The bit number of the subframe offset may be 6 bits if the MSI is 0b00, 7 bits if the MSI is 0b01, 8 bits if the MSI is 0b10, and 9 bits if the MSI is 0b11. The index of the subframe offset may start in the beginning of the MSI.
0047In this exemplary embodiment, the frame offset and the subframe offset are included in the MBS MAP, but it is just an example. Alternatively, the frame offset and the subframe offset may be included in other control information, e.g., a MAC management message, a MAC header, an MBS information element, or a control channel.
0048The MCS refers to the modulation and coding scheme of the MBS region with regard to the FID. The resource information includes data within the MBS region or information about a frequency resource index of the MBS MAP. The information about the frequency resource index is a location of an index of a subband logical resource unit (SLRU) where the E-MBS burst is ended. The resource information may include the location of the index of the SLRU. The first MBS stream may start in the SLRU next to the MBS MAP within the MBS region. The MBS resource information indexes the SLRU of the subframe in the MBS region indicated by a zone allocation bitmap transmitted through an SCD message. The allocation pattern for transmitting the MBS region may appear as a period or the like. If only the first pattern is known (e.g., if information about the allocation pattern for the first MBS region is included in the MBS MAP) in the case that the pattern is repetitive, information about the following FID may be known even though it is not received.
0049There are various methods using the MBS region indication information for indicating the MBS region. In the same method as the S-SFH indicates the MBS MAP, the superframe number, the frame index, the subframe index, etc. may be used for the indication. On the contrary, without using the superframe number, it may be transmitted using the frame offset and the subframe offset for each FID or it may be represented with only offset information of the subframe. Lastly, when information about the MBS region is represented it may be regarded that the MBS MAP is transmitted to the first frame (i.e., the current frame) and the last frame of the relevant MBS region, or the MBS MAP is transmitted in the beginning of every MBS region.
0050At this time, the MBS MAP indicating the MBS data burst about each FID may include not only a location where the MBS burst is first transmitted, but also information about time to transmit the MBS burst and a transmission parameter of the MBS burst. Here, the information about time to transmit the following MBS burst may include the transmission interval, period, etc. of the MBS burst. Also, the next MBS burst may be transmitted following the previous MBS bust. That is, the MBS bursts may be sequentially transmitted in accordance with the FIDS after the MBS MAP is transmitted in the MBS region.
0051Table 4 shows the MBS region indication information.
0000<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="98pt" align="left" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE 4</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Syntax</entry><entry>Size (bits)</entry><entry>Notes</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>MBS Region IE ( ) {</entry><entry /><entry /></row><row><entry>Superframe</entry><entry>[TBD]</entry><entry>Size is the same as MSI length</entry></row><row><entry>Bitmap</entry><entry /><entry>in superframe unit</entry></row><row><entry /><entry /><entry>1: multicast is included in the</entry></row><row><entry /><entry /><entry>superframe</entry></row><row><entry /><entry /><entry>0: unicast only in the</entry></row><row><entry /><entry /><entry>superframe</entry></row><row><entry>Frame Bitmap</entry><entry>4 * (number</entry><entry>Maximum length = (Number of</entry></row><row><entry /><entry>of bit set</entry><entry>frame in an superframe) *</entry></row><row><entry /><entry>in the</entry><entry>(length of superframe)</entry></row><row><entry /><entry>superframe</entry><entry>Length = (Number of frame in</entry></row><row><entry /><entry>bitmap)</entry><entry>an superframe) * (number of</entry></row><row><entry /><entry /><entry>set bit in the superframe</entry></row><row><entry /><entry /><entry>bitmap)</entry></row><row><entry /><entry /><entry>1: multicast is included in the</entry></row><row><entry /><entry /><entry>frame</entry></row><row><entry /><entry /><entry>0: unicast only in the frame</entry></row><row><entry>Subframe</entry><entry>(number of</entry><entry>Maximum length = (number of</entry></row><row><entry>Bitmap</entry><entry>subframe</entry><entry>subframe in an frame) *</entry></row><row><entry /><entry>in an</entry><entry>(Maximum length of frame</entry></row><row><entry /><entry>frame) *</entry><entry>bitmap)</entry></row><row><entry /><entry>(number of</entry><entry>Length = (number of subframe</entry></row><row><entry /><entry>bit set in</entry><entry>in an frame) * (length of frame</entry></row><row><entry /><entry>the frame</entry><entry>bitmap)</entry></row><row><entry /><entry>bitmap)</entry><entry>1: multicast is included in the</entry></row><row><entry /><entry /><entry>subframe</entry></row><row><entry /><entry /><entry>0: unicast on ly in the</entry></row><row><entry /><entry /><entry>subframe</entry></row><row><entry>}</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
0052Here, the superframe bitmap indicates whether the superframe is used for multicast or unicast. The frame bitmap indicates whether the frame is used for multicast or unicast. The subframe bitmap indicates whether the subframe is used for multicast or unicast.
0053At this time, if the superframe is used for multicast, the superframe is decoded on the basis of the superframe bitmap. If the frame is used the multicast, the frame is decoded on the basis of the frame bitmap. If the subframe is used the multicast, the subframe is decoded on the basis of the subframe bitmap. Each decoding stage is performed before transmitting the MBS data after transmitting the MBS MAP. It is determined that the superframe, the frame or the subframe receives only the unicast service or receives the multicast service too, so that the unicast MS may be prevented from trying to decode the subframe. Accordingly, it is possible to solve the problem that the unicast MS repetitively fails in the decoding, determines a synchronization trouble with the system, and unnecessarily performs the update
0054Through the MBS region indication information, the information about the MBS region may be transmitted to the unicast MS as well as the multicast MS. It is possible to provide the MBS to an initially accessing MS, a performing handover MS, an idle mode MS, etc. The information about the region may be independently present in an MBS MAP, a MAC management message, a MAC header, a map information element or the SFH, and given to the MS. Also, the information about the region may be present simultaneously in two or more among the MBS MAP, the MAC management message, the MAC header, the map information element and the SFH.
0055While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. The exemplary embodiments should be considered in descriptive sense only and not for purposes of limitation. Therefore, the scope of the invention is defined not by the detailed description of the invention but by the appended claims, and all differences within the scope will be construed as being included in the present invention.
Contents5
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8699512B2 | Cited by | United States of America | Search report |
| US2013010671A1 | Cited by | United States of America | Pre-grant |
| US9042896B2 | Cited by | United States of America | Search report |
| US2010097973A1 | Cited by | United States of America | Pre-grant |
| JP2013537379A | Cited by | Japan | Examiner |
| US2012294221A1 | Cited by | United States of America | Pre-grant |
| US2013178215A1 | Cited by | United States of America | Pre-grant |
| US2012207073A1 | Cited by | United States of America | Pre-grant |
| US8705430B2 | Cited by | United States of America | Search report |
| US2011158148A1 | Cited by | United States of America | Pre-grant |
| US9271262B2 | Cited by | United States of America | Search report |
| US8675540B2 | Cited by | United States of America | Search report |
| US2006239264A1 | Cites | United States of America | Pre-grant |
| US2007253367A1 | Cites | United States of America | Pre-grant |
| US2008267104A1 | Cites | United States of America | Pre-grant |
| US2009225692A1 | Cites | United States of America | Pre-grant |
| US2010014462A1 | Cites | United States of America | Pre-grant |
| US2010205283A1 | Cites | United States of America | Pre-grant |
| US7924703B2 | Cites | United States of America | Pre-grant |
8 priority claims, no other members on record
Priority claims8
| Document | Office | Kind | Date |
|---|---|---|---|
| 20090084734 | Republic of Korea | A | |
| 20090084734 | Republic of Korea | A | |
| 20100088568 | Republic of Korea | A | |
| 20100088568 | Republic of Korea | A | |
| 1020090084734 | – | – | – |
| 1020100088568 | – | – | – |
| KR20090084734 | – | – | – |
| KR20100088568 | – | – | – |
2 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTIONSTCB | STCB | |
| AssignmentAS | AS |
Numbers
- Publication
- 20110058511
- Publication, DOCDB
- 2011058511
- Publication, EPODOC
- US2011058511
- Application
- 12878487
- Application, DOCDB
- 87848710
- Application, EPODOC
- US20100878487
Titles
- English
- METHOD FOR TRANSMITTING DATA OF MULTICAST BROADCAST SERVICE USING SUPERFRAME HEADER IN MOBILE WIRELESS CONNECTION SYSTEM
Classification
- CPC, 3
- H04L12/189
- H04L51/38
- H04W4/06
- IPC, 1
- H04H20 71
- USPC, 1
- 370312000