WO2010102425A1 - Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base - Google Patents

Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base Download PDF

Info

Publication number
WO2010102425A1
WO2010102425A1 PCT/CN2009/000271 CN2009000271W WO2010102425A1 WO 2010102425 A1 WO2010102425 A1 WO 2010102425A1 CN 2009000271 W CN2009000271 W CN 2009000271W WO 2010102425 A1 WO2010102425 A1 WO 2010102425A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
radio link
link control
broadcast multicast
access control
Prior art date
Application number
PCT/CN2009/000271
Other languages
English (en)
Chinese (zh)
Inventor
陈宇
王河
汪勇刚
Original Assignee
上海贝尔股份有限公司
阿尔卡特朗讯
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 上海贝尔股份有限公司, 阿尔卡特朗讯 filed Critical 上海贝尔股份有限公司
Priority to CN200980155712.8A priority Critical patent/CN102301672B/zh
Priority to PCT/CN2009/000271 priority patent/WO2010102425A1/fr
Publication of WO2010102425A1 publication Critical patent/WO2010102425A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

  • the present invention relates to the field of mobile communications, and more particularly to an evolved multimedia broadcast multicast service (E-MBMS service) packet transmission method, and a gateway and a base station implementing the packet transmission method.
  • E-MBMS service evolved multimedia broadcast multicast service
  • E-MBMS Evolved Multimedia Broadcast Multicast Service
  • SYNC separate synchronous
  • RLC Radio Link Control
  • the present invention discloses a technical solution suitable for sharing a SYNC entity, but the present invention can also achieve less overhead for an independent SYNC entity structure.
  • Figure 1A shows a schematic diagram of a U-plane architecture for MBMS content synchronization
  • Figure 1B shows the logical architecture of E-MBMS.
  • Statistical multiplexing is the purpose of multiplexing multiple MBMS services to save resources.
  • 3GPP has decided to support this technology.
  • Statistical multiplexing discards the way in which each service in the previous version of the protocol allocates fixed resources, but multiple services reuse and share the same resource, realizing the complementary resources between multiple services by real-time changes in the bit rate of the service itself. Thereby reducing the total resource requirements.
  • each service is serially multiplexed in the base station to the MAC PDU generated by the same MAC entity, but each service still has its own RLC entity. Therefore, although statistical multiplexing is similar to treating multiple services as one service transmission, different services are ultimately distinguished, so different services are carried on different RLC PDUs.
  • the order of service multiplexing is determined in advance by the central control entity MCE (MBMS Coordination Entity) of the MBMS and informed to the base station (refer to FIG. 1B).
  • MCE MBMS Coordination Entity
  • the MBMS service needs to synchronize data between base stations.
  • the method is to add a synchronization (SYNC) entity from the gateway to the base station (refer to Figure 1A).
  • SYNC synchronization
  • the data encapsulated by this SYNC entity provides information such as number, byte count, packet count, and so on.
  • the size of the lost packet can be known according to the number, byte count, and packet count in the subsequently received data packet, and the exact time at which the transmission is resumed is determined.
  • Fig. 1C is a diagram showing an example of packet transmission from the gateway 100 to the base stations 201 to 203.
  • the gateway 100 receives service packets of different E-MBMS services, and forwards the service packets to different base stations (eNBs) 201-203 through IP multicast.
  • the services of these different E-MBMS services are multiplexed together at the MAC layer.
  • the base stations 201 to 203 use a single frequency network (FSN) technology to transmit MBMS signals, which has the advantage that signals from different base stations 201 to 203 mutually benefit rather than interfere with each other.
  • FSN single frequency network
  • SFN technology requires fairly strict synchronization. However, during IP multicast transmissions from gateway 100 to base stations 201 ⁇ 203, packets may be lost or experience different delays. Therefore, the SYNC protocol is required.
  • the SYNC protocol can work properly with the existing MAC/RLC protocol; however, if multiple services are multiplexed together, some uncertainty may cause the network to be corrupted. Below, the above uncertainty issues will be discussed in detail.
  • FIG. 2A is a diagram for explaining the base station 202 parsing a packet loss situation. For example, as shown in FIG.
  • 2B to 2D show the structure of the MAC sub-header, the RLC header fixed part, and the RLC header extension, respectively.
  • the MAC data transmitted in each slot of the physical layer constitutes a transport block (TB).
  • TB transport block
  • PDU packet data unit
  • Each MAC PDU can contain several MAC Service Data Units (SDUs).
  • SDU Service Data Unit
  • Each MAC SDU is an RLC Packet Data Unit (PDU).
  • Each RLC PDU can in turn contain several RLC SDUs.
  • the MAC sub-header is located at the beginning of each MAC PDU, the RLC header is located at the beginning of each RLC PDU, and each RLC header contains an RLC header fixed part. How many RLC SDUs are included in the RLC PDU, how many RLC header extensions are included in the RLC header, and the RLC header extension is followed by the fixed part of the RLC header.
  • LCID Logical channel identifier
  • R1 reserved bits
  • FI Frame information indicating whether an RLC SDU has segmentation at the beginning or end of the RLC PDU.
  • the base station 202 may interpret this as three different scenarios as shown by (a) ⁇ (c) in Figure 2A, including three, four or five MAC headers, respectively. .
  • the solid shaded portion located at the far right in FIG. 2A is padding data - (padd ing); if the solid shaded portion represents business data, the corresponding field needs to be added in the corresponding ⁇ 1 header, but The problems set forth in the present invention are not affected.
  • RLD SDU 4 is the last SDU of Service 3 in the current scheduling period. The same assumptions apply to FIGS. 4A, 4B, and 6 shown and described later. According to (a) in Fig. 2A,
  • the first TB consists of a MAC PDU consisting of an RLC.
  • the RLC PDU includes only one RLC SDU (RLC SDU 1 ). Therefore, at the beginning of the first TB, a MAC sub-header, an RLC header fixed part, and an RLC header extension part are included;
  • the second TB consists of a MAC PDU consisting of one RLC PDU containing two RLC SDUs (RLC SDU 2 and RLC)
  • SDU 3 therefore, at the beginning of the second TB, includes a MAC sub-header, an RLC header fixed part, and two RLC header extensions;
  • the third TB is composed of a MAC PDU consisting of one RLC PDU, the RLC PDU containing only one RLC SDU (RLC SDU 4 ), and therefore, at the beginning of the third TB, a MAC sub-header is included.
  • the first TB is composed of a MAC PDU consisting of one RLC PDU, the RLC PDU containing only one RLC SDU (RLC SDU 1 ), and therefore, at the beginning of the first TB, a MAC sub-header is included.
  • the second TB is composed of a MAC PDU consisting of one RLC PDU, the RLC PDU containing only one RLC SDU (RLC SDU 2 ), and therefore, at the beginning of the second TB, a MAC sub-header is included.
  • the third TB consists of one MAC PDU consisting of two RLC PDUs, and each RLC PDU contains only one RLC SDU (RLC SDU 3 and RLC SDU 4), so at the beginning of the third TB, Included two MAC sub-headers, one RLC header fixed part and one RLC header extension part, and at the beginning of the second RLC PDU, an RLC header fixed part and an RLC header extension part are included;
  • the first TB consists of a MAC PDU consisting of two RLC PDUs, and each RLC PDU contains only one RLC SDU (RLC SDU 1 and RLC SDU 2 ), so at the beginning of the first TB, Contains two
  • a MAC sub-header, an RLC header fixed part, and an RLC header extension part, and at the beginning of the second RLC PDU, include an RLC header fixed part and an RLC header extension part;
  • the second TB consists of one MAC PDU, which contains two RLC PDUs, and each RLC PDU contains only one RLC SDU ( RLC SDU)
  • RLC SDU 4 also extends to the third TB, therefore, at the beginning of the first TB, ie at the beginning of the first RLC PDU, contains two MAC sub-headers, one RLC header a fixed part and an RLC header extension, and at the beginning of the second RLC PDU, an RL ( ⁇ ⁇ fixed part;
  • the third TB consists of a MAC PDU consisting of an RLC PDU containing only one RLC SDU (part of the RLC SDU 4), so at the beginning of the first TB, the packet is ⁇ A MAC sub-header, an RLC header fixed part, and an RLC header extension. Therefore, if the base station 202 adds the MAC/RLC header according to one of (a) to (c) in FIG. 2A, since the base station 202 itself may erroneously analyze the situation of the lost TB, the added MAC/RLC header is different.
  • the MAC/RLC headers added by the other base stations 201 and 203 cause the length of the entire data to be different (the right side of the RLC SDU 4 is not aligned), and the base stations 201 to 203 cannot resynchronize at a common starting point. Therefore, unless the base station 20 2 knows With the exact reuse scheme, synchronization will be compromised.
  • an E-MBMS service packet transmission method including: adding a MAC sub-header and a MAC sub-header at the beginning of a last MAC PDU carrying an MBMS service in each scheduling period
  • the number of services is equal to the number of services in the last position in the MAC PDU; at the beginning of other MAC PDUs, no MAC sub-header is added.
  • the E-MBMS service packet transmission method further includes: adding an RLC header fixed part at the beginning of the RLC PDU.
  • the E-MBMS service packet transmission method further includes: adding a fixed part and an extension part at the beginning of the RLC PDU where the last segment of one RLC SDU carrying one MBMS service is located in each scheduling period RLC header; and at the beginning of other RLC PDUs, no RLC ⁇ header is added.
  • an E-MBMS service packet transmission method including: adding an evolved MAC sub-header and a MAC sub-header at the beginning of a last MAC PDU carrying an MBMS service in each scheduling period And the number of MAC sub-headers is equal to the number of services in the last position of the MAC PDU; at the beginning of other MAC PDUs, the evolved MAC sub- ⁇ is added.
  • the E-MBMS service packet transmission method further includes: at the beginning of the RLC PDU, no RL is added, that is, the transparent RLC mode is adopted.
  • the E-MBMS service packet transmission method further includes: in each scheduling In the period, the RLC header of the last segment of an RLC SDU carrying one MBMS service is added, and the RLC header of the extended part is added, that is, the non-feedback RLC mode is adopted; and at the beginning of other RLC SDUs, the RLC header is not added. That is, the transparent RLC mode is adopted.
  • the format of the evolved MAC sub-header is R/R/E/LCID, where R represents a reserved bit, E represents an extended bit, and LCID represents a logical channel identifier. More preferably, a reserved bit R in the evolved MAC sub-header is enabled to indicate whether a transparent RLC mode or a no-feedback RLC mode is employed.
  • an E-MBMS service packet transmission method comprising: receiving an IP data packet carrying an MBMS service; and when receiving the IP data packet correctly, according to the first or the first according to the present invention
  • the E-MBMS service packet transmission method according to the second aspect forming a TB that carries the MBMS service; and transmitting the generated TB to the UE.
  • the E-MBMS service packet transmission method further includes: according to the total number of multiplexed MBMS services and the packet count, in accordance with the first or second scheme according to the present invention, in the case of an error in the reception-receive error
  • the E-MBMS service packet transmission method determines the number of fixed parts of the MAC sub-header and the RLC header; according to the determined number of fixed positions of the MAC sub-header and the RLC header, it is determined that other base stations that have not received a reception error occur
  • the transmission time of the transmission data to be generated by the data packet processing and the header insertion processing performed by the erroneous IP data packet; and the silence during the determined transmission duration to maintain strictness between the respective base stations receiving the MBMS service Synchronize.
  • a base station including: a MAC sub-header insertion unit, configured to add a MAC sub-header and a MAC in the beginning of a last MAC PDU carrying an MBMS service in each scheduling period.
  • the number of sub-headers is equal to the number of services in the last position of the MAC PDU, and at the beginning of other MAC PDUs, no MAC sub-header is added.
  • no RL is added.
  • the base station further includes: an RLC header insertion unit, configured to add a fixed part and an extended part at the beginning of the RLC PDU where the last segment of an RLC SDU carrying one MBMS service is located in each scheduling period RLC header, as well as in it At the beginning of his RLC PDU, no RLC header is added.
  • a base station including: a MAC sub-header insertion unit, which adds an evolved MAC sub-header and a MAC sub-header at the beginning of the last MAC PDU carrying an MBMS service in each scheduling period. And the number of MAC sub-headers is equal to the number of services in the last position of the MAC PDU, and at the beginning of other MAC PDUs, the evolved MAC sub-header is added.
  • the base station further includes: an RLC header insertion unit, configured to add a fixed part and a beginning of the RLC PDU where the last segment of one RLC SDU of one MBMS service is located in each scheduling period
  • the extended part of the RLC 4 header that is, adopts the non-feedback RLC mode, and at the beginning of other RLC PDUs, does not add the RLC header, that is, adopts the transparent RLC mode.
  • the format of the evolved MAC sub-header is R/R/E/LCID, where R represents a reserved bit, E represents an extended bit, and LCID represents a logical channel identifier. More preferably, a reserved bit R in the evolved MAC sub-header is enabled to indicate whether a transparent RLC mode or a no-feedback RLC mode is employed.
  • a base station comprising: a receiving unit, configured to receive an IP data packet carrying an MBMS service; and a TB forming unit, configured to, when receiving the IP data packet correctly, according to the present invention
  • the E-MBMS service packet transmission method according to the first or second aspect, forming a TB that carries the MBMS service; and a transmission unit, configured to transmit the generated TB to the UE.
  • the base station further includes: a header determining unit, configured to: according to the total number of multiplexed MBMS services and the packet count, in the case of a reception error, according to the first or second aspect of the present invention
  • the E-MBMS service packet transmission method determines the number of fixed portions of the MAC sub-header and the RLC header; the transmission duration determining unit is configured to determine that no reception occurs according to the determined number of the MAC sub-header and the fixed portion of the RLC header Wrong data base packet processing performed by other base stations for IP data packets that have received errors
  • the header insertion process processes the transmission duration of the transmission data to be generated; and a transmission control unit for controlling the transmission unit to remain silent during the determined transmission duration to maintain the base station and other base stations receiving the MBMS service Strict synchronization.
  • Each transport block (TB) uses an evolved MAC header for scheduling assistance
  • each business has a MAC ⁇ header
  • a reserved bit in the MAC header is used to indicate whether the transparent mode or the no feedback mode is used
  • the RLC adopts a transparent mode
  • the overhead is small due to the transparent mode in which the MAC sub-header is not added;
  • Figure 1A shows a schematic diagram of a ⁇ plane architecture for MBMS content synchronization.
  • Figure 1B shows the logical architecture of the E-MBMS.
  • Fig. 1C is a diagram showing an example of packet transmission from the gateway 100 to the base stations 201 to 203.
  • FIG 2 A is a schematic diagram for explaining a base station 202 where packet loss parsing.
  • 2B 2D show the structure of the MAC sub-header, the RLC header fixed part, and the RLC header extension part, respectively.
  • Figure 3 is a schematic diagram showing a scheduling period in accordance with the present invention.
  • Figure 4A is a diagram for explaining the analysis of packet loss conditions by the base station 202 in accordance with the present invention, in which the RLC header fixed portion is still employed.
  • Figure 4B is a diagram for explaining the analysis of the packet loss situation by the base station 202 according to the present invention, in which the RLC header fixed portion is completely removed, and only the RLC header extension portion is employed.
  • Figure 5 is a diagram for explaining an evolved MAC sub-header according to another embodiment of the present invention.
  • 6 is a schematic diagram for explaining the parsing of a packet loss situation by the base station 202 according to the present invention, in which the evolved MAC sub-header proposed by the present invention, that is, the R/R/E/LCID header, and completely removing the RLC header fixed is used. In part, only the RLC header extension is used.
  • FIG. 7 is a schematic diagram showing a base station (BS or eNB) 700 for implementing the present invention. detailed description
  • the base station 202 does not know the exact multiplexing scheme, the number of multiplexed services is known.
  • the scheduling period proposed by the present invention is as shown in FIG. Packets belonging to the same service are grouped together; different services are transmitted one by one in accordance with a predetermined transmission order; and padding data is added only after the last service. Therefore, the logical channel changes only when a service switch occurs in the transport block (TB). Therefore, a viable MAC solution is:
  • the last MAC packet data unit (PDU) carrying a specific service includes a MAC sub-header, and the number of MAC sub-headers is equal to the number of services in the last position in the MAC PDU;
  • the format of the sub-header is the same as that of FIG. 2B, and is used to indicate the length of the corresponding MAC service data unit (SDU) in the MAC PDU; •
  • a transparent MAC sub-header is used, ie no MAC sub-header is inserted. Since the base station 202 (Fig. 1C) can learn the number of RLC SDUs by packet counting information, a feasible RLC solution is:
  • the RLC header including the fixed part and the extended part is used, and only the RLC header is used for the last piece of RLC SDU, that is, in each scheduling period, the last segment of an RLC SDU carrying a specific MBMS service is located.
  • the sequence number (SN) in the RLC header can be counted based on the RLC SDU or RLC PDU. If counting according to the RLC PDU, the user equipment (UE) can know how many RLC PDUs the RLC SDU can be divided according to the size of the SN, the SDU, and the size of the TB.
  • FIG. 4A is a diagram for explaining the analysis of packet loss conditions by the base station 202 in accordance with the present invention, in which the RLC header fixed portion is still employed.
  • the number of MAC sub-headers and RLC headers is determined (alignment of the right side of the RLC SDU 4;).
  • the number of MAC sub-headers is three, and the number of RLC headers (the RLC header includes the RLC header fixed part and the RLC header extension part) is four. .
  • Figure 4B is a diagram for explaining the analysis of the packet loss situation by the base station 202 according to the present invention, in which the RLC header fixed portion is completely removed, and only the RLC header extension portion is used.
  • the number of fixed portions of the MAC sub-header and the RLC header is determined (aligned to the right of the RLC SDU 4). .
  • the number of MAC sub-headers is three, and the number of fixed portions of the RLC header is zero.
  • the MAC sub-report included in the lost packet can be determined according to the present invention
  • the number of fixed parts of the header and the RLC header and according to the prior art, when each RLC SDU has one LI, the number of extension parts of the RLC header can be determined, and the base station 202 (Fig. 1C) can determine the need in case of TB loss.
  • the length of the added MAC/RLC header keeping its entire data length the same as that of base stations 201 and 203, still maintains synchronization between base stations 201-203. It should be noted that: In a scheduling period, the same service is continuously transmitted in time, and different services are time-division multiplexed.
  • a MAC sub-header is added at the beginning of the MAC PDU.
  • final refers to the last data packet of a service within a scheduling period, rather than the order of the services or data within a MAC PDU.
  • 100-bit data of service 1, 200-bit data of service 2, and 300-bit data of service 3 are included, and the rest are service data of service 4 (not the last data, also That is to say, in the next immediately adjacent MAC PDU in this scheduling period, the service data of the service 4 is still included, in this case, 100 bits of the service 1 due to the continuity of the service data and the time division multiplexing between different services.
  • the data, the 200-bit data of Service 2, and the 300-bit data of Service 3 are the last data of the respective services 1, 2, and 3.
  • this MAC PDU contains three services in the last position, so it is necessary to insert three MAC sub-headers at the beginning of this MAC PDU.
  • data for services 1, 2, and/or 3 may still be included in the next scheduling period.
  • the above specific numbers are only for the purpose of example, and the actual application may be different from the above specific numbers, but those skilled in the art can adjust themselves as needed, but such adjustment does not exceed the scope of the present invention.
  • the UE will attempt to start receiving from the first subframe until all subframes of interest are received. However, the UE wants to receive the second service but fails In the case of successfully decoding the first MAC PDU (including the MAC sub-header), the UE cannot know which MAC PDU the service of interest starts from. Therefore, additional information is required.
  • the following improvement schemes are proposed. For specific illustration, reference may be made to FIG. 5:
  • the MAC header can be added twice for the last service in the MAC PDU, one of which is the above R/R/E/LCID header and the other is the normal R/R/E/ The LCID/F/L header (referred to as the normal MAC header in this specification). Even if there is no service data for a particular service, it still needs to transmit the normal MAC header of the service.
  • Feedback mode. 6 is a schematic diagram for explaining the parsing of a packet loss situation by the base station 202 according to the present invention, in which the evolved MAC sub-header proposed by the present invention, that is, the R/R/E/LCID header, and completely removing the RLC header fixed is used. In part, only the RLC header extension is used.
  • the number of fixed portions of the MAC sub-header and the RLC header is determined (alignment of the right side of the RLC SDU 4) .
  • FIG. 7 is a schematic diagram showing a base station (BS or eNB) 700 for implementing the above technical solution of the present invention.
  • the base station 700 includes a receiving unit 730, a transport block (TB) forming unit 740, a transmitting unit 750, a head determining unit 760, a transmission duration determining unit 770, and a transmission control unit 780.
  • TB transport block
  • the base station 700 includes a receiving unit 730, a transport block (TB) forming unit 740, a transmitting unit 750, a head determining unit 760, a transmission duration determining unit 770, and a transmission control unit 780.
  • the receiving unit 730 receives the IP data packet carrying the MBMS service.
  • the TB forming unit 740 forms a TB carrying the MBMS service.
  • the TB forming unit 740 may include a MAC sub-header insertion unit 710 and an RLC header insertion unit 720, the MAC sub-header insertion unit 710 performs a MAC sub-header insertion operation, and the RLC header insertion unit 720 performs an RLC header insertion operation.
  • the MAC sub-header insertion unit 710 adds a MAC sub-header at the beginning of the last MAC PDU carrying an MBMS service in each scheduling period, and the number of MAC sub-headers is equal to that in the MAC PDU. The number of services in the last location, and at the beginning of other MAC PDUs, does not add a MAC subheader.
  • the MAC sub-header insertion unit 710 adds a MAC sub-frame in the R/R/E/LCID format at the beginning of the last MAC PDU carrying an MBMS service in each scheduling period.
  • the MAC sub-header in the R/R/E/LCID/F/L format, and the number of MAC sub-headers in the R/R/E/LCID/F/L format is equal to the number of services in the last position in the MAC PDU, And at the beginning of other MAC PDUs, only the MAC sub-header in R/R/E/LCID format is added.
  • the RLC header insertion unit 720 can completely remove the fixed portion of the RLC header (at the beginning of each RLC PDU), and insert the RLC header extension only at the beginning of each RLC PDU.
  • the RLC header insertion unit 720 may add an RLC header including a fixed part and an extended part at the beginning of the RLC PDU where the last segment of one RLC SDU carrying an MBMS service is located, and at the beginning of other RLC PDUs, does not add RLC ⁇ .
  • one of the reserved bits R may be used to indicate whether RLC transparent mode or RLC no feedback mode is employed.
  • the MAC sub-header insertion unit 710 completes the MAC sub-header insertion operation and the RLC header. After the insertion unit 720 completes the RLC ⁇ header insertion operation, the TB formation unit 740 outputs the generated TB to the transmission unit 750.
  • Transmission unit 750 transmits the generated TB to the User Equipment (UE).
  • UE User Equipment
  • the header determining unit 760 determines the MAC sub-portion based on the total number of multiplexed MBMS services and the packet count. The number of fixed parts of the header and RLC header.
  • the transmission duration determining unit 770 determines, according to the determined number of the MAC sub-header and the fixed portion of the RLC header, data packet processing and header insertion processing performed by other base stations that have not received a reception error for the IP data packet in which the reception error occurs (by The TB forming unit 740 of the other base station completes the transmission duration of the transmission data to be generated.
  • Transmission Control Unit 780 maintains transmission unit 750 silent during the determined transmission duration to maintain strict synchronization between base station 700 and other base stations receiving the MBMS service.
  • base station 700 can be base station 202 shown in Figure 1C; and other base stations can be base stations 201 and 203 shown in Figure 1C. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué (service E-MBMS), et une passerelle et une station de base pour la mise en oeuvre du procédé. Selon un aspect de l'invention, on ajoute un en-tête secondaire de commande d'accès multimédia (commande MAC) au début de la dernière unité de données par paquets (unité PDU) de MAC porteuse de service MBMS dans chaque période de programmation, et le nombre d'en-têtes secondaires MAC équivaut au nombre des services se trouvant à la fin de l'unité PDU de MAC; néanmoins, le mode transparent d'en-tête secondaire de MAC est adopté au début des autres unités PDU de MAC, ce qui signifie qu'on n'ajoute aucun en-tête secondaire de MAC.
PCT/CN2009/000271 2009-03-13 2009-03-13 Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base WO2010102425A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN200980155712.8A CN102301672B (zh) 2009-03-13 2009-03-13 演进多媒体广播组播业务分组传输方法、网关和基站
PCT/CN2009/000271 WO2010102425A1 (fr) 2009-03-13 2009-03-13 Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/000271 WO2010102425A1 (fr) 2009-03-13 2009-03-13 Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base

Publications (1)

Publication Number Publication Date
WO2010102425A1 true WO2010102425A1 (fr) 2010-09-16

Family

ID=42727770

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/000271 WO2010102425A1 (fr) 2009-03-13 2009-03-13 Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base

Country Status (2)

Country Link
CN (1) CN102301672B (fr)
WO (1) WO2010102425A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3562119A4 (fr) * 2017-01-20 2019-10-30 Huawei Technologies Co., Ltd. Procédé de traitement de données, dispositif de communication, et dispositif de réseau
CN115396687A (zh) * 2022-08-25 2022-11-25 广州方硅信息技术有限公司 处理媒体资源中业务数据的方法、装置、直播系统和设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016064221A1 (fr) 2014-10-22 2016-04-28 Samsung Electronics Co., Ltd. Procédé et système pour transmettre et recevoir une unité de données de protocole dans des réseaux de communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008116868A1 (fr) * 2007-03-23 2008-10-02 Nokia Corporation Fonctionnement distribué
CN101292551A (zh) * 2005-09-14 2008-10-22 株式会社Ntt都科摩 无线基站和用户公共数据传输方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101098175A (zh) * 2006-06-26 2008-01-02 大唐移动通信设备有限公司 演进多媒体广播组播业务的发送、接收方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101292551A (zh) * 2005-09-14 2008-10-22 株式会社Ntt都科摩 无线基站和用户公共数据传输方法
WO2008116868A1 (fr) * 2007-03-23 2008-10-02 Nokia Corporation Fonctionnement distribué

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ALCATEL-LUCENT: "Multiple packets loss recovery and RLC PDU format in eMBMS, R3-070938", 11 May 2007 (2007-05-11), Retrieved from the Internet <URL:http://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_56/docs/?C=N,O=D> *
NOKIA ET AL.: "MAC Header Structure, R2-071730", 11 May 2007 (2007-05-11), pages 1 - 5, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_58/Documents/> *
ZTE: "Idle detection in MBMS synchronization, R3-083188", 14 November 2008 (2008-11-14), Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG3_Iu/TSGR3_62/docs> *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3562119A4 (fr) * 2017-01-20 2019-10-30 Huawei Technologies Co., Ltd. Procédé de traitement de données, dispositif de communication, et dispositif de réseau
CN115396687A (zh) * 2022-08-25 2022-11-25 广州方硅信息技术有限公司 处理媒体资源中业务数据的方法、装置、直播系统和设备

Also Published As

Publication number Publication date
CN102301672B (zh) 2014-07-09
CN102301672A (zh) 2011-12-28

Similar Documents

Publication Publication Date Title
US20200178210A1 (en) Method For Content Synchronization When Broadcasting Data In A Wireless Network
EP1770897B1 (fr) Procédé, dispositif et système de communication mobile pour la retransmission de paquets
CA2691154C (fr) Procede pour fournir une pluralite de services
US7289535B2 (en) Method of accommodating fragmentation and burst in a wireless protocol
EP1919235B1 (fr) Station de base, réseau de communication mobile et méthode pour synchroniser la livraison de données de radiodiffusion dans un réseau de communication mobile à fréquence unique
EP2262182B1 (fr) Procédé de synchronisation d&#39;une passerelle et de stations de base, et passerelle et station de base correspondantes
US7978734B2 (en) Multichannel MAC data stream for wireless communication
EP2471223B1 (fr) Multiplexage amélioré pour entité rlc unique
US9467892B2 (en) Method and apparatus for transmitting data packet
JP2010534997A (ja) ＶｏＩＰパケットを伝送する方法
US9838851B2 (en) Subframe processing method and device
US20080192748A1 (en) Method of broadcasting in a telecommunications network in a segmentation re-assembly mode
US9386598B2 (en) Method and apparatus for synchronization processing
KR20090087773A (ko) 이동 통신 시스템에서 패킷 데이터 유닛의 재전송 및 상태보고 장치 및 방법
WO2010102425A1 (fr) Procédé de transmission par paquets de service de multidiffusion de diffusion multimédia évolué, passerelle et station de base
US11889445B2 (en) Infrastructure equipment, communications device and methods
WO2009105981A1 (fr) Procédé de mise à jour de clé de cryptage de trafic de groupe et système associé

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980155712.8

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09841294

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09841294

Country of ref document: EP

Kind code of ref document: A1