WO2022147814A1 - Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications - Google Patents

Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications Download PDF

Info

Publication number
WO2022147814A1
WO2022147814A1 PCT/CN2021/071016 CN2021071016W WO2022147814A1 WO 2022147814 A1 WO2022147814 A1 WO 2022147814A1 CN 2021071016 W CN2021071016 W CN 2021071016W WO 2022147814 A1 WO2022147814 A1 WO 2022147814A1
Authority
WO
WIPO (PCT)
Prior art keywords
data unit
group identity
multicast service
retransmitted
another group
Prior art date
Application number
PCT/CN2021/071016
Other languages
English (en)
Inventor
Jing He
Benoist Pierre Sebire
Manivannan Thyagarajan
Original Assignee
Nokia Shanghai Bell Co., Ltd.
Nokia Solutions And Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co., Ltd., Nokia Solutions And Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co., Ltd.
Priority to PCT/CN2021/071016 priority Critical patent/WO2022147814A1/fr
Priority to CN202180090119.0A priority patent/CN116848812A/zh
Publication of WO2022147814A1 publication Critical patent/WO2022147814A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1816—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of the same, encoded, message

Definitions

  • Various example embodiments relate to methods, apparatuses, and computer readable media for compensating multicast service data loss in telecommunication systems.
  • a multimedia broadcast multicast service may be transmitted simultaneously to multiple mobile stations or user equipments via a multicast traffic channel (MTCH) based on a group identity such as a group radio network temporary identity (G-RNTI) in a serving cell.
  • MTCH multicast traffic channel
  • G-RNTI group radio network temporary identity
  • an apparatus including at least one processor and at least one memory, where the at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to perform: receiving at least one data unit of a multicast service via a multicast traffic channel based on a group identity; receiving at least one retransmitted data unit of the multicast service via the multicast traffic channel based on at least one another group identity; and determining data of the multicast service based on the at least one data unit and the at least one retransmitted data unit.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to further perform: receiving configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and a broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the at least one retransmitted data unit may be received after a measurement gap, and the at least one retransmitted data unit may correspond to at least one data unit missed during the measurement gap.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to further perform: transmitting information associated with at least one missed or improperly received data unit of the multicast service, the at least one retransmitted data unit corresponding to the at least one missed or improperly received data unit.
  • granularities of the at least one data unit and the at least one retransmitted data unit may be at a multicast radio bearer level.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to further perform: decoding the at least one data unit and the at least one retransmitted data unit from the multicast traffic channel in parallel based on the group identity and the at least one another group identity.
  • a method including: receiving at least one data unit of a multicast service via a multicast traffic channel based on a group identity; receiving at least one retransmitted data unit of the multicast service via the multicast traffic channel based on at least one another group identity; and determining data of the multicast service based on the at least one data unit and the at least one retransmitted data unit.
  • the method may further include: receiving configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the at least one retransmitted data unit may be received after a measurement gap, and the at least one retransmitted data unit may correspond to at least one data unit missed during the measurement gap.
  • the method may further include: transmitting information associated with at least one missed or improperly received data unit of the multicast service, the at least one retransmitted data unit corresponding to the at least one missed or improperly received data unit.
  • granularities of the at least one data unit and the at least one retransmitted data unit may be at a multicast radio bearer level.
  • the method may further include: decoding the at least one data unit and the at least one retransmitted data unit from the multicast traffic channel in parallel based on the group identity and the at least one another group identity.
  • an apparatus including: means for receiving at least one data unit of a multicast service via a multicast traffic channel based on a group identity; means for receiving at least one retransmitted data unit of the multicast service via the multicast traffic channel based on at least one another group identity; and means for determining data of the multicast service based on the at least one data unit and the at least one retransmitted data unit.
  • the apparatus may further include: means for receiving configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the at least one retransmitted data unit may be received after a measurement gap, and the at least one retransmitted data unit may correspond to at least one data unit missed during the measurement gap.
  • the apparatus may further include: means for transmitting information associated with at least one missed or improperly received data unit of the multicast service, the at least one retransmitted data unit corresponding to the at least one missed or improperly received data unit.
  • granularities of the at least one data unit and the at least one retransmitted data unit may be at a multicast radio bearer level.
  • the apparatus may further include: means for decoding the at least one data unit and the at least one retransmitted data unit from the multicast traffic channel in parallel based on the group identity and the at least one another group identity.
  • a computer readable medium comprising instructions stored thereon for causing an apparatus to perform: receiving at least one data unit of a multicast service via a multicast traffic channel based on a group identity; receiving at least one retransmitted data unit of the multicast service via the multicast traffic channel based on at least one another group identity; and determining data of the multicast service based on the at least one data unit and the at least one retransmitted data unit.
  • the instructions cause the apparatus to further perform: receiving configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the at least one retransmitted data unit may be received after a measurement gap, and the at least one retransmitted data unit may correspond to at least one data unit missed during the measurement gap.
  • the instructions cause the apparatus to further perform: transmitting information associated with at least one missed or improperly received data unit of the multicast service, the at least one retransmitted data unit corresponding to the at least one missed or improperly received data unit.
  • granularities of the at least one data unit and the at least one retransmitted data unit may be at a multicast radio bearer level.
  • the instructions cause the apparatus to further perform: decoding the at least one data unit and the at least one retransmitted data unit from the multicast traffic channel in parallel based on the group identity and the at least one another group identity.
  • an apparatus including at least one processor and at least one memory, where the at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to perform: transmitting, to a set of mobile stations, at least one data unit of a multicast service via a multicast traffic channel based on a group identity; and retransmitting, to at least one mobile station in the set of mobile stations, at least a part of the at least one data unit via the multicast traffic channel based on at least one another group identity.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to further perform: transmitting, to the at least one mobile stations, configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the retransmission may be after a measurement gap, and the retransmitted part may correspond to a part of the at least one data unit during the measurement gap.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to further perform: receiving, from the at least one mobile stations, information associated with at least one missed or improperly received data unit of the multicast service; and determining the the retransmitted part based on the received information.
  • granularities of the transmission of the at least one data unit and the retransmission of the part of the at least one data unit may be at a multicast radio bearer level.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to further perform: receiving capability information of the set of mobile stations; and configuring the at least one another group identity based on the capability information of the set of mobile stations.
  • a method including: transmitting, to a set of mobile stations, at least one data unit of a multicast service via a multicast traffic channel based on a group identity; and retransmitting, to at least one mobile station in the set of mobile stations, at least a part of the at least one data unit via the multicast traffic channel based on at least one another group identity.
  • the method may further include: transmitting, to the at least one mobile stations, configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the retransmission may be after a measurement gap, and the retransmitted part may correspond to a part of the at least one data unit during the measurement gap.
  • the method may further include: receiving, from the at least one mobile stations, information associated with at least one missed or improperly received data unit of the multicast service; and determining the the retransmitted part based on the received information.
  • granularities of the transmission of the at least one data unit and the retransmission of the part of the at least one data unit may be at a multicast radio bearer level.
  • the method may further include: receiving capability information of the set of mobile stations; and configuring the at least one another group identity based on the capability information of the set of mobile stations.
  • an apparatus including: means for transmitting, to a set of mobile stations, at least one data unit of a multicast service via a multicast traffic channel based on a group identity; and means for retransmitting, to at least one mobile station in the set of mobile stations, at least a part of the at least one data unit via the multicast traffic channel based on at least one another group identity.
  • the apparatus may further include: means for transmitting, to the at least one mobile stations, configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the retransmission may be after a measurement gap, and the retransmitted part may correspond to a part of the at least one data unit during the measurement gap.
  • the apparatus may further include: means for receiving, from the at least one mobile stations, information associated with at least one missed or improperly received data unit of the multicast service; and means for determining the the retransmitted part based on the received information.
  • granularities of the transmission of the at least one data unit and the retransmission of the part of the at least one data unit may be at a multicast radio bearer level.
  • the apparatus may further include: means for receiving capability information of the set of mobile stations; and means for configuring the at least one another group identity based on the capability information of the set of mobile stations.
  • a computer readable medium comprising instructions stored thereon for causing an apparatus to perform: transmitting, to a set of mobile stations, at least one data unit of a multicast service via a multicast traffic channel based on a group identity; and retransmitting, to at least one mobile station in the set of mobile stations, at least a part of the at least one data unit via the multicast traffic channel based on at least one another group identity.
  • the instructions cause the apparatus to further perform: transmitting, to the at least one mobile stations, configuration information associated with the at least one another group identity via at least one of radio resource control reconfiguration information and broadcasted system information.
  • the configuration information associated with the at least one another group identity may be included in at least one of measurement gap configuration information and retransmission configuration information.
  • the retransmission may be after a measurement gap, and the retransmitted part may correspond to a part of the at least one data unit during the measurement gap.
  • the instructions cause the apparatus to further perform: receiving, from the at least one mobile stations, information associated with at least one missed or improperly received data unit of the multicast service; and determining the the retransmitted part based on the received information.
  • granularities of the transmission of the at least one data unit and the retransmission of the part of the at least one data unit may be at a multicast radio bearer level.
  • the instructions cause the apparatus to further perform: receiving capability information of the set of mobile stations; and configuring the at least one another group identity based on the capability information of the set of mobile stations.
  • FIG. 1 illustrates an example of multicast service data compensation in an example embodiment.
  • FIG. 2 illustrates an example of operations for multicast service data compensation in an example embodiment.
  • FIG. 3 illustrates another example of multicast service data compensation in an example embodiment.
  • FIG. 4 illustrates another example of operations for multicast service data compensation in an example embodiment.
  • FIG. 5 illustrates another example of multicast service data compensation in an example embodiment.
  • FIG. 6 illustrates another example of operations for multicast service data compensation in an example embodiment.
  • FIG. 7 illustrates an example method for multicast service data compensation in an example embodiment.
  • FIG. 8 illustrates an example apparatus for multicast service data compensation in an example embodiment.
  • FIG. 9 illustrates another example apparatus for multicast service data compensation in an example embodiment.
  • FIG. 10 illustrates another example method for multicast service data compensation in an example embodiment.
  • FIG. 11 illustrates another example apparatus for multicast service data compensation in an example embodiment.
  • FIG. 12 illustrates another example apparatus for multicast service data compensation in an example embodiment.
  • a downlink transmission of data of a multicast service may be a one-time downlink transmission with a configured group identity (for example, a configured G-RNTI) via an MTCH, and a mobile station or user equipment (UE) , which is expected to receive the multicast service data, may miss or receive improperly one or more data units (DUs) or transport blocks (TBs) of the multicast service, for example due to gap-assisted measurements, decoding errors, cell handovers, or the like.
  • DUs data units
  • TBs transport blocks
  • the UEs which will leave the serving cell during a measurement gap to perform measurement, may miss a part of multicast service data transmitted during the measurement gaps.
  • the UE may loss a part of multicast service data due to the one-time downlink transmission of the downlink multicast service data.
  • the UE may loss one or more multicast service data parts which have been transmitted by the previous serving cell and/or the new serving cell.
  • the missed or improperly received part of the multicast service data may be retransmitted via the MTCH to one or more UEs (for example, those UEs which have suffered from data missing or improper data reception) based on one or more another configured group identities (for example, one or more another G-RNTIs) .
  • the missed or improperly received data part of the multicast service may be compensated without interrupting the normal data transmission of the multicast service.
  • FIG. 1 illustrates an example of the multicast service data compensation in an example embodiment, where the network transmits data units of a multicast service, including data units 110-119, to one or more UEs including UE1 and UE2, based on a group identity G-RNTI1 via an MTCH.
  • a part of UEs including UE1 may perform gap-assisted measurements in a connected state, for example in a RRC_CONNECTED state as specified in 3rd generation partnership project (3GPP) standards, during measurement gaps such as periods 102 and 104 as illustrated in FIG. 1, and to receive data units of the multicast service based on G-RNTI1 during periods out of the measurement gaps, such as periods 101, 103, and 105 as illustrated in FIG. 1, while another part of UEs including UE2 do not have to perform measurements during the measurement gaps such as the periods 102 and 104.
  • 3GPP 3rd generation partnership project
  • the transmissions of the data units 111 and 112 based on G-RNTI1 are within the period 102 corresponding to a measurement gap of the part of UEs including UE1
  • the transmissions of the data units 117 and 118 based on G-RNTI1 are within the period 104 also corresponding to a measurement gap of the part of UEs including UE1
  • the transmissions of the data units 110, 113-116, and 119 based on G-RNTI1 are within periods 101, 103, and 105 which are out of the measurement gaps of UE1.
  • UE2 may receive data units of the multicast service continuously via the MTCH based on G-RNTI1. For example, during periods including 101-105, the UE2 may receive data units 110-119 based on G-RNTI1 via the MTCH, which are transmitted from the network based on G-RNTI1, and may further combine the successfully received data units 110-119 to determine data of the multicast service.
  • UE1 performs gap-assisted measurements during periods 102 and 104. During receptions based on G-RNTI1, UE1 misses the data units 111 and 112 which are transmitted based on G-RNTI1 from the network during the period 102, and the data units 117 and 118 which are transmitted based on G-RNTI1 from the network during the period 104.
  • the network may further transmit data units 120, 121, 122, and 123 based on another group identity G-RNTI2 via the MTCH to the one or more UEs including UE1 which have missed data units 111, 112, 117, and 118 due to gap-assisted measurement during the periods 102 and 104.
  • the data unit 120 transmitted based on G-RNTI2 may be a duplication of the data unit 111 transmitted based on G-RNTI1, possibly with different packet headers due to various protocols at different levels during the data transmission.
  • the data unit 120 transmitted based on G-RNTI2 may be configured with a transport block serial number (SN) which is the same with that configured for the data unit 111 transmitted based on G-RNTI1, so that UE1 may determine the data of the multicast service properly based on the data unit 120 received based on G-RNTI2 and those data units received based on G-RNTI1 (for example, the data units 110, 113-116, and so on) .
  • the transmission of the data unit 120 may correspond to a retransmission of the data unit 111, and the data unit 120 may also be referred to as a retransmitted data unit herein.
  • the retransmitted data unit 121 may correspond to the data unit 112
  • the retransmitted data unit 122 may correspond to the data unit 117
  • the retransmitted data unit 123 may correspond to the data unit 118.
  • the transmissions of the data units 120 and 121 based on G-RNTI2 or the retransmission of the data units 111 and 122 based on G-RNTI2 may be performed via the MTCH during a period after the period 102 corresponding to the measurement gap, for example during the period 103 and in parallel with the transmissions of the data units 113-116 based on the G-RNTI1.
  • the transmissions of the data units 122 and 123 or the retransmission of the data units 117 and 118 based on G-RNTI2 may be performed during a period after the period 104 corresponding to the measurement gap, for example during the period 105 and in parallel with the transmissions of the data units 119 and so on based on the G-RNTI1.
  • the retransmissions of the missed data units may be performed via the MTCH during one or more periods out of the measurement gaps after the period 102.
  • both the data units 120 and 121 may be transmitted during the period 105 based on G-RNTI2 and in parallel with the transmission of the data unit 119 based on G-RNTI1, or the data unit 120 may be transmitted during the period 103 and the data unit 121 may be transmitted during the period 105, or the like.
  • the retransmissions of one or more missed data units (for example, one or more of the data units 120 and 121) based on G-RNTI2 and the normal transmissions of one or more data units based on G-RNTI1 during one or more periods out of the measurement gaps may be performed based on one or more data packets.
  • the data unit 120 associated with G-RNTI2, the data unit 121 associated with G-RNTI2, the data unit 113 associated with G-RNTI1, the data unit 114 associated with G-RNTI1, and so on may be packaged in separated data packets, respectively; the data unit 120 associated with G-RNTI2 and the data unit 121 associated with G-RNTI2 may be packaged in the same data packet; the data unit 120 associated with G-RNTI2 and the data unit 113 associated with G-RNTI1 may be packaged in a data packet, and the data unit 121 associated with G-RNTI2 and the data unit 114 associated with G-RNTI1 may be packaged in another data packet; the data units 120 and 121 associated with G-RNTI2 and the data units 113-116 associated with G-RNTI1 may be packaged in the same data packet; or the like.
  • the normal transmissions of one or more data units based on G-RNTI1 and the retransmissions of the one or more missed data units based on G-RNTI2 may be from either the same or different cells.
  • the normal transmissions of one or more data units based on G-RNTI1 may be from a primary cell (PCell) and the retransmissions of the one or more missed data units based on G-RNTI2 may be from a secondary cell (SCell) .
  • PCell primary cell
  • SCell secondary cell
  • the normal transmissions of one or more data units based on G-RNTI1 may be from a PCell, and the retransmissions of the one or more missed data units based on G-RNTI2 may be from a primary secondary cell (PSCell) .
  • the normal transmissions of one or more data units based on G-RNTI1 may be from a PSCell, and the retransmissions of the one or more missed data units based on G-RNTI2 may be from one or more SCells.
  • UE1 may receive data unit 110 of the multicast service based on G-RNTI1 via the MTCH.
  • UE1 may perform gap-assisted measurement, and thus may miss the data units 111 and 112 from the network.
  • UE1 may receive data units 113-116 of the multicast service based on G-RNTI1 via the MTCH, and may receive the retransmitted data units 120 and 121 (corresponding to the data units 111 and 112, respectively, which are missed by UE1 due to the gap-assisted measurement during the period 102) based on G-RNTI2 via the MTCH, for example in parallel with the receptions of the data units 113-116.
  • UE1 may perform gap-assisted measurement, and thus may miss the data units 117 and 118.
  • UE1 may receive data units 119 and so on of the multicast service based on G-RNTI1 via the MTCH, and may receive the retransmitted data units 122 and 123 (corresponding to the data units 117 and 118, respectively, which are missed by UE1 due to the gap-assisted measurement during the period 104) based on G-RNTI2 via the MTCH.
  • the data part of the multicast service missed by UE1 due to the gap-assisted measurements may be compensated through the data units 120, 121, 122, and 123 retransmitted based on G-RNTI2.
  • UE1 may determine the data of the multicast service based on the data units 110, 113-116, 119, and so on, which are received based on G-RNTI1, and the retransmitted data units 120, 121, 122, 123, and so on.
  • FIG. 2 illustrates example operations for the multicast service data compensation for example in a case as illustrated in FIG. 1.
  • the network may configure a group identity for normal transmissions of data units of the multicast service, such as the G-RNTI1 as illustrated in FIG. 1, and may provide information 201 associated with the configured G-RNTI1 to the target UEs of the multicast service, including the UE1 and the UE2 in the example as illustrated in FIG. 1.
  • the network may further configure another group identity for additional retransmissions of missed data units of the multicast service for example due to gap-assisted measurements, such as the G-RNTI2 as illustrated in FIG. 1, and may provide information 202 associated with the configured G-RNTI2 to one or more target UEs including UE1 which are configured to perform gap-assisted measurements during measurement gaps.
  • another group identity for additional retransmissions of missed data units of the multicast service for example due to gap-assisted measurements, such as the G-RNTI2 as illustrated in FIG. 1, and may provide information 202 associated with the configured G-RNTI2 to one or more target UEs including UE1 which are configured to perform gap-assisted measurements during measurement gaps.
  • the information 202 may be provided via one or more radio resource control (RRC) reconfiguration signaling/messages, or may be broadcasted via a system information block (SIB) .
  • RRC radio resource control
  • SIB system information block
  • the information 202 may be included in a measurement gap configuration, a retransmission configuration, and/or any other suitable configuration information.
  • the information 202 may be provided to the target UEs of the multicast service together with the information 201.
  • the network may transmit data units 203 of the multicast service (for example, including the data units 110-119 as illustrated in FIG. 1) to the target UEs of the multicast service, including UE1 and UE2, via the MTCH based on the configured G-RNTI1, for example without interruption regardless of possible measurement gaps configured to one or more target UEs including UE1.
  • data units 203 of the multicast service for example, including the data units 110-119 as illustrated in FIG. 1
  • the network may transmit data units 203 of the multicast service (for example, including the data units 110-119 as illustrated in FIG. 1) to the target UEs of the multicast service, including UE1 and UE2, via the MTCH based on the configured G-RNTI1, for example without interruption regardless of possible measurement gaps configured to one or more target UEs including UE1.
  • UE2 does not have to perform measurements during the measurement gap periods, and may receive data units 203 of the multicast service continuously via the MTCH based on G-RNTI1. Then, as illustrated in FIG. 2, UE2 may combine the successfully received and decoded data units 203 in an operation 204, to determine the data of the multicast service.
  • the network may retransmit the missed data units 206 to the one or more UEs including UE1 via the MTCH based on the additionally configured G-RNTI2.
  • UE1 may combine the successfully received and decoded data units among the data units 203 (for example, including data units 110, 113-116, and 119 as illustrated in FIG. 1) and the retransmitted data units (for example, including data units 120, 121, 122, and 123 as illustrated in FIG. 1) to determine the data of the multicast service.
  • the data units 203 for example, including data units 110, 113-116, and 119 as illustrated in FIG. 1
  • the retransmitted data units for example, including data units 120, 121, 122, and 123 as illustrated in FIG.
  • FIG. 3 illustrates another example of the multicast service data compensation in an example embodiment, where the network transmits data units of a multicast service, including data units 301-309, to one or more target UEs including UE3 and UE4 based on a group identity G-RNTI3 via an MTCH.
  • UE4 receives and decodes successfully the data units of the multicast service from the network (including the data units 301-309) via the MTCH based on G-RNTI3, while UE3 misses or receives improperly (for example, fails to decode) a part of data units such as the data units 302 and 303.
  • the network may further transmit data units 310 and 311 based on another group identity G-RNTI4 via the MTCH to one or more target UEs of the multicast service, such as UE3, which have suffered from a data loss or an improper data reception.
  • the data unit 310 transmitted based on G-RNTI4 may be a duplication of the data unit 302 transmitted based on G-RNTI3, possibly with different packet headers due to various protocols at different levels during the data transmission.
  • the data unit 310 transmitted based on G-RNTI4 may be configured with a transport block serial number which is the same with that configured for the data unit 302 transmitted based on G-RNTI3, so that UE3 may determine the data of the multicast service properly based on the data unit 310 received based on G-RNTI4 and those data units received based on G-RNTI3 (for example, the data units 301, 304-309, and so on) .
  • the transmission of the data unit 310 may correspond to a retransmission of the data unit 302, and the data unit 310 may also be referred to as a retransmitted data unit herein.
  • the retransmitted data unit 311 may correspond to the data unit 303.
  • the transmissions of the data units 310 and 311 may be in parallel with the transmissions of one or more of the data units 304-309. Further, for example, the retransmissions of one or more missed or improperly received data units (for example, one or more of the data units 310 and 311) based on G-RNTI4 and the normal transmissions of one or more data units based on G-RNTI3 (for example, one or more of the data units 304-309) may be performed based on one or more data packets.
  • the normal transmissions of one or more data units based on G-RNTI3 and the retransmissions of the one or more missed or improperly received data units based on G-RNTI4 may be from either the same or different cells.
  • the normal transmissions of one or more data units based on G-RNTI3 may be from a primary cell and the retransmissions of the one or more missed or improperly received data units based on G-RNTI4 may be from a secondary cell.
  • the normal transmissions of one or more data units based on G-RNTI3 may be from a PCell, and the retransmissions of the one or more missed data units based on G-RNTI4 may be from a PSCell.
  • the normal transmissions of one or more data units based on G-RNTI3 may be from a PSCell, and the retransmissions of the one or more missed data units based on G-RNTI4 may be from one or more SCells.
  • the previous serving cell may transmit one or more data units of the multicast service based on G-RNTI3 via the MTCH, and the new serving cell after handover may retransmit one or more data units missed due to handover based on G-RNTI4 via the MTCH and may continue to transmit the remaining data units of the multicast service based on G-RNTI3 via the MTCH.
  • UE3 may receive and decode data units 301-309 of the multicast service based on G-RNTI3 via the MTCH, and may receive the retransmitted data units 310 and 311 (corresponding to the data units 302 and 303, respectively, which for example are not decoded sucessfully by UE3) based on G-RNTI4 via the MTCH, for example in parallel with the receptions of the data units 304-309.
  • the missed or improperly received data part of the multicast service for example due to decoding failures and cell handovers may be compensated for UE3 through the retransmitted data units 310 and 311 based on G-RNTI4. Then, UE3 may determine the data of the multicast service based on the successfully received data units 301 and 304-309 which are received based on G-RNTI3 via the MTCH, and the retransmitted data units 310 and 311 which are received based on G-RNTI4 via the MTCH.
  • FIG. 4 illustrates example operations for the multicast service data compensation for example in a case as illustrated in FIG. 3.
  • the network may configure a group identity for normal transmissions of data units of the multicast service, such as the G-RNTI3 as illustrated in FIG. 3, and may provide information 401 associated with the configured G-RNTI3 to the target UEs of the multicast service, include the UE3 and the UE4 in the example as illustrated in FIG. 3.
  • the network may further configure another group identity for additional retransmissions of missed or improperly received data units of the multicast service for example due to decoding failure or handover, such as the G-RNTI4 as illustrated in FIG. 3, and may provide information 402 associated with the configured G-RNTI4 to one or more target UEs including UE3 which miss or receive improperly a part of data units of the multicast service for example due to decoding failure, handover, or the like.
  • another group identity for additional retransmissions of missed or improperly received data units of the multicast service for example due to decoding failure or handover, such as the G-RNTI4 as illustrated in FIG. 3, and may provide information 402 associated with the configured G-RNTI4 to one or more target UEs including UE3 which miss or receive improperly a part of data units of the multicast service for example due to decoding failure, handover, or the like.
  • the information 402 may be provided via one or more RRC reconfiguration signaling/messages, or may be broadcasted via a SIB.
  • the information 402 may be included in a measurement gap configuration, a retransmission configuration, and/or any other suitable configuration information.
  • the information 402 may be provided to the target UEs of the multicast service together with the information 401.
  • the network may transmit data units 403 of the multicast service (for example, including the data units 301-309 as illustrated in FIG. 1) to the target UEs of the multicast service, including UE3 and UE4, via the MTCH based on the configured G-RNTI3.
  • data units 403 of the multicast service for example, including the data units 301-309 as illustrated in FIG. 1
  • the target UEs of the multicast service including UE3 and UE4, via the MTCH based on the configured G-RNTI3.
  • UE4 receives and decodes successfully data units 403 of the multicast service continuously via the MTCH based on G-RNTI3. Then, as illustrated in FIG. 4, UE4 may combine the successfully received and decoded data units 403 in an operation 404, to determine the data of the multicast service.
  • UE3 may transmit information 405 associated with the missed or improperly received data units to the network, for example through one or more non-acknowledgement messages which include information for example associated with the transport block serial number of the missed or improperly received data units or the like.
  • the network may retransmit the missed data units 406 to UE3 via the MTCH based on the additionally configured G-RNTI4.
  • UE3 may combine the successfully received and decoded data units among the data units 403 of the multicast service (for example, including data units 301 and 304-309 as illustrated in FIG. 3) and the retransmitted data units (for example, including data units 310 and 311 as illustrated in FIG. 3) , to determine the data of the multicast service.
  • the data units 403 of the multicast service for example, including data units 301 and 304-309 as illustrated in FIG. 3
  • the retransmitted data units for example, including data units 310 and 311 as illustrated in FIG.
  • FIG. 5 illustrates yet another example of the multicast service data compensation in an example embodiment, where the network transmits data units of a multicast service, including data units 510-519, to one or more target UEs including UE5 based on a group identity G-RNTI5 via an MTCH.
  • a part of UEs including UE5 may perform gap-assisted measurements in a connected state, such as RRC_CONNECTED state as specified in 3GPP standards, during measurement gaps such as periods 502 and 504 as illustrated in FIG. 5, and to receive data units of the multicast service based on G-RNTI5 during periods out of the measurement gaps, such as periods 501, 503, and 505 as illustrated in FIG. 5.
  • a connected state such as RRC_CONNECTED state as specified in 3GPP standards
  • the transmissions of the data units 511 and 512 based on G-RNTI5 are within the period 502 corresponding to a measurement gap of UE5, the transmissions of the data units 517 and 518 based on G-RNTI5 are within the period 504 also corresponding to another measurement gap of UE5, and the transmissions of the data units 510, 513-516, and 519 based on G-RNTI5 are within periods 501, 503, and 505 which are out of the measurement gaps of UE5.
  • UE5 performs gap-assisted measurements during periods 502 and 504, and thus misses the data units 511 and 512 which are transmitted based on G-RNTI5 from the network during the period 502, and the data units 517 and 518 which are transmitted based on G-RNTI5 from the network during the period 504. Also, UE5 misses or receives improperly the data unit 515 based on G-RNTI5, for example fails to decode the received data unit 515.
  • the network may further transmit data units 520, 521, 522, and 523 based on another group identity G-RNTI6 via the MTCH to the one or more target UEs including UE5 which have suffered data missing due to gap-assisted measurements. Also, to compensate for the data unit 515 which is missed or received improperly by UE5, the network may further transmit a data unit 530 based on yet another identity G-RNTI7 via the MTCH to UE5.
  • the data unit 520 (or 521 or 522 or 533) transmitted based on G-RNTI6 may be a duplication of the data unit 511 (or 512 or 517 or 518) transmitted based on G-RNTI5, possibly with different packet headers due to various protocols at different levels during the data transmission, and the data unit 520 transmitted based on G-RNTI6 may be configured with a transport block serial number which is the same with that configured for the data unit 511 transmitted based on G-RNTI5.
  • the data unit 530 transmitted based on G-RNTI7 may be a duplication of the data unit 515 transmitted based on G-RNTI5, possibly with different packet headers due to various protocols at different levels during the data transmission, and the data unit 530 transmitted based on G-RNTI7 may be configured with a transport block serial number which is the same with that configured for the data unit 515 transmitted based on G-RNTI5.
  • UE5 may determine the data of the multicast service properly based on the data units 510, 513, 514, 516, and 519 which are successfully received based on G-RNTI5, the data units 520, 521, 522, and 523 which are retransmitted based on G-RNTI6, and the data unit 530 which is retransmitted based on G-RNTI7.
  • the transmissions of the data units 520 and 521 based on G-RNTI6 or the retransmissions of the data units 511 and 522 based on G-RNTI6 may be performed via the MTCH during a period after the period 602 corresponding to the measurement gap, for example during the period 603 and in parallel with the transmissions of the data units 513-516 based on the G-RNTI5.
  • the transmissions of the data units 522 and 523 or the retransmission of the data units 517 and 528 based on G-RNTI6 may be performed during a period after the period 504 corresponding to the measurement gap, for example during the period 505 and in parallel with the transmissions of the data units 519 and so on based on the G-RNTI5.
  • the transmission of the data unit 530 or retransmission of the data unit 515 based on G-RNTI7 may be performed during a period after suffering the decoding failure of the data unit 515 and out of the measurement gaps, for example during the period 519 and in parallel with the transmission of the data unit 519 based on G-RNTI5 and/or the transmissions of the data units 522 and 523 based on G-RNTI6.
  • the retransmissions of the missed or improperly received data units based on G-RNTI6 and/or G-RNTI7 and the normal transmissions of one or more data units based on G-RNTI5 during one or more periods out of the measurement gaps may be performed based on one or more data packets.
  • the normal transmissions of one or more data units based on G-RNTI5 and the retransmission of the one or more missed or improperly received data units based on G-RNTI6 and/or G-RNTI7 may be from either the same or different cells.
  • the normal transmissions of one or more data units based on G-RNTI5 may be from a primary cell and the retransmission of the one or more missed or improperly received data units based on G-RNTI6 and/or G-RNTI7 may be from one or more secondary cells.
  • the normal transmissions of one or more data units based on G-RNTI5 may be from a PCell, and the retransmissions of the one or more missed data units based on G-RNTI6 and/or G-RNTI7 may be from a PSCell.
  • the normal transmissions of one or more data units based on G-RNTI5 may be from a PSCell, and the retransmissions of the one or more missed data units based on G-RNTI5 and/or G-RNTI7 may be from one or more SCells.
  • the transmissions of the data units 510-515 based on G-RNTI5 and/or retransmissions of one or more of the data units 520 and 521 based on G-RNTI6 may be performed by a serving cell before the handover, and the transmissions of the data units 515-519 based on G-RNTI5 and/or retransmissions of one or more of the data units 520-523 based on G-RNTI6 and the data units 520-523 based on G-RNTI7 may be performed by a serving cell after the handover.
  • UE5 may receive data unit 510 of the multicast service based on G-RNTI5 via the MTCH. During the period 502, UE5 may perform gap-assisted measurement, and thus may miss the data units 511 and 512 from the network.
  • UE5 may receive data units 513-516 of the multicast service based on G-RNTI5 via the MTCH, and may receive the retransmitted data units 520 and 521 (corresponding to the data units 511 and 512, respectively, which are missed by UE5 due to the gap-assisted measurement during the period 502) based on G-RNTI6 via the MTCH, for example in parallel with the receptions of the data units 513-516.
  • UE5 may perform gap-assisted measurement, and thus may miss the data units 517 and 518.
  • UE5 may receive data units 519 and so on of the multicast service based on G-RNTI5 via the MTCH, and may receive the retransmitted data units 522 and 523 (corresponding to the data units 517 and 518, respectively, which are missed by UE5 due to the gap-assisted measurement during the period 504) based on G-RNTI6 via the MTCH, and the retransmitted data unit 530 (corresponding to the data unit 515 which is missed due to decoding failure) based on G-RNTI7 via the MTCH.
  • the missed or improperly received data parts of the multicast service by UE5 may be compensated through the data units 520-523 retransmitted based on G-RNTI6 and the data unit 530 retransmitted based on G-RNTI7.
  • UE5 may determine the data of the multicast service based on the data units 510, 513, 514, 516, 519 which are received successfully based on G-RNTI5, the retransmitted data units 520, 521, 522, 523 which are received successfully based on G-RNTI6, and the retransmitted data unit 530 which is received successfully based on G-RNTI7.
  • FIG. 6 illustrates example operations for the multicast service data compensation for example in a case as illustrated in FIG. 5, which may correspond to an example of combination of the operations as illustrated in FIG. 2 and FIG. 4.
  • the network may configure a group identity for normal transmissions of data units of the multicast service, such as the G-RNTI5 as illustrated in FIG. 5, and may provide information 601 associated with the configured G-RNTI5 to the target UEs of the multicast service, including the UE5 in the example as illustrated in FIG. 1.
  • the network may further configure one or more another group identities for additional retransmissions of missed or improperly received data units of the multicast service for example due to gap-assisted measurements, decoding failures, handovers, and so on.
  • the network may configure G-RNTI6 for compensating the data missed due to gap-assisted measurement, and G-RNTI6 for compensating the data missed due to decoding failure and so on.
  • the network may provide information 602 associated with the configured G-RNTI6 to one or more target UEs including UE5 which are configured to perform gap-assisted measurements during measurement gaps, and provide information 603 associated with the configured G-RNTI7 to the target UEs of the multicast service.
  • the information 602 and/or 603 may be provided via one or more RRC reconfiguration signaling/messages, or may be broadcasted via a SIB.
  • the information 602 and/or 603 may be included in a measurement gap configuration, a retransmission configuration, and/or any other suitable configuration information.
  • the information 602 and/or 603 may be provided to the target UEs of the multicast service together with the information 601.
  • the network may transmit data units 604 of the multicast service (for example, including the data units 510-519 as illustrated in FIG. 5) to the target UEs of the multicast service (including UE5) via the MTCH based on the configured G-RNTI5, for example without interruption regardless of possible measurement gaps configured to one or more target UEs including UE5.
  • the network may retransmit the missed data units 606 to the one or more UEs including UE5 via the MTCH based on the additionally configured G-RNTI6.
  • UE5 may transmit information 608 associated with the one or more missed or improperly received data units to the network, for example through a non-acknowledgement message which may include information for example associated with the transport block serial numbers of the one or more missed or improperly received data units or the like.
  • the network may retransmit the missed data units 609 to UE5 via the MTCH based on the additionally configured G-RNTI7, for example during a periods out of the measurement gaps (for example, a period after a measurement gap) .
  • UE5 may combine the successfully received and decoded data units among the data units 604 of the multicast service (for example, including data units 510, 513, 514, 516, and 519 as illustrated in FIG. 5) and the retransmitted data units (for example, including data units 520, 521, 522, 523, and 530 as illustrated in FIG. 5) , to determine the data of the multicast service.
  • the data units 604 of the multicast service for example, including data units 510, 513, 514, 516, and 519 as illustrated in FIG. 5
  • the retransmitted data units for example, including data units 520, 521, 522, 523, and 530 as illustrated in FIG. 5
  • the missed or improperly received part of the multicast service data may be retransmitted/received via the MTCH to/by one or more UEs (for example, those which have suffered from data missing or data loss) based on one or more another configured group identities (for example, one or more another G-RNTIs) .
  • the missed or improperly received data part of the multicast service may be compensated without interrupting the normal data transmission/reception of the multicast service.
  • granularities of the transmitted/retransmission of the data units of the multicast service may be at a multicast radio bearer level. In another example, granularities of the transmitted/retransmission of the data units of the multicast service may also be at a channel level.
  • target UEs of a multicast service may report their respective capability information (for example, including information associated with whether a target UE is capable of decoding multicast service data from the MTCH in parallel based a plurality of group identities) to the network, and the network may configure a plurality of group identities for those target UEs capable of decoding multicast service data from the MTCH in parallel based a plurality of group identities.
  • capability information for example, including information associated with whether a target UE is capable of decoding multicast service data from the MTCH in parallel based a plurality of group identities
  • FIG. 7 illustrates an example method 700 for multicast service data compensation in an example embodiment, which may be performed in a UE as a target of a multicast service, such as UE1, UE2, UE3, UE4, and UE5 in the above examples.
  • the example method 700 may include an operation 701, an operation 702, and an operation 703.
  • the UE may receive at least one data unit of a multicast service (for example, data units 203 in FIG. 2, data units 403 in FIG. 4, and data units 604 in FIG. 6) via an MTCH based on a group identity (for example, G-NRTI1 in FIG. 1 and FIG. 2, G-RNTI3 in FIG. 3 and FIG. 4, and G-RNTI5 in FIG. 5 and FIG. 6) .
  • a group identity for example, G-NRTI1 in FIG. 1 and FIG. 2, G-RNTI3 in FIG. 3 and FIG. 4, and G-RNTI5 in FIG. 5 and FIG. 6 .
  • the UE may receive at least one retransmitted data unit of the multicast service (for example, data units 206 in FIG. 2, data units 406 in FIG. 4, and data units 606 and 609 in FIG. 6) via the MTCH based on at least one another group identity (for example, G-NRTI2 in FIG. 1 and FIG. 2, G-RNTI4 in FIG. 3 and FIG. 4, and G-RNTI6 and G-RNTI7 in FIG. 5 and FIG. 6) .
  • group identity for example, G-NRTI2 in FIG. 1 and FIG. 2, G-RNTI4 in FIG. 3 and FIG. 4, and G-RNTI6 and G-RNTI7 in FIG. 5 and FIG.
  • the UE may determine data of the multicast service based on the at least one data unit and the at least one retransmitted data unit.
  • the at least one another group identity may include at least one of: a group identity for data units missed due to gap-assisted measurement of the UE; a group identity for data units missed or improperly received due to decoding failure; a group identity for data missed or improperly received due to cell handover; and so on.
  • the example method 700 may further include an additional operation, where the UE may receive configuration information associated with the at least one another identity (for example, the information 202 in FIG. 2, the information 402 in FIG. 4, and the information 602 and 603 in FIG. 6) .
  • the reception of the configuration information associated with the at least one another identity may be via RRC reconfiguration information, or broadcasted system information, or the like.
  • the configuration information associated with the at least one another identity may be included in at least one of measurement gap configuration information, retransmission configuration information, and any other suitable configuration information from the network.
  • the at least one retransmitted data unit may be received after a measurement gap of the UE, and the at least one retransmitted data unit may correspond to at least one data unit missed during the measurement gap of the UE.
  • the example method 700 may further include an additional operation, where the UE may transmit information associated with at least one missed or improperly received data unit (for example, the information 405 in FIG. 4, and the information 608 in FIG. 6) to the network (for example, to base station serving the UE in the network or a serving cell associated with a base station in the network) , so that the network may determine and retransmit the at least retransmitted data unit corresponding to the at least one missed or improperly received data unit.
  • the network for example, to base station serving the UE in the network or a serving cell associated with a base station in the network
  • granularities of the at least one data unit and the at least one retransmitted data unit may be at a multicast radio bearer level, so as to provide a fine granularity. In some example embodiments, the granularities of the at least one data unit and the at least one retransmitted data unit may also be at any other suitable level, such as a channel level.
  • the example method 700 may further include an additional operation, where the UE may decode the at least one data unit and the at least one retransmitted data unit from the MTCH in parallel, for example based on the group identity and the at least one another group identity, respectively.
  • the at least one data unit received based on the group identity and the at least one retransmitted data unit received based on the at least one another group identity may be from either the same or different cells, where the different cells may be associated with either the same or different base stations in the network.
  • the at least one data unit received based on the group identity may be from a primary cell
  • the at least one retransmitted data unit received based on the at least one another group identity may be from one or more secondary cells.
  • the at least one data unit received based on the group identity may be from a primary cell
  • the at least one retransmitted data unit received based on the at least one another group identity may be from a primary secondary cell.
  • the at least one data unit received based on the group identity may be from a primary secondary cell, and the at least one retransmitted data unit received based on the at least one another group identity may be from one or more secondary cells.
  • a part of the at least one data unit received based on the group identity may be from a previous serving cell before the cell handover
  • another part of the at least one data unit received based on the group identity may be from a new serving cell after the cell handover
  • the at least one retransmitted data unit received based on the at least one another group identity may be at least one of the previous serving cell and the new serving cell.
  • the UE in addition to receiving the normally transmitted data units of the multicast service via the MTCH based on a configured group identity (for example a G-RNTI) , the UE may also received the missed or improperly received part of the multicast service data which is retransmitted from the network based on one or more another configured group identities (for example, one or more another G-RNTIs) .
  • the missed or improperly received data part of the multicast service may be compensated for the UE without interrupting the normal data reception of the multicast service.
  • FIG. 8 illustrates an example apparatus 800 for multicast service data compensation in an example embodiment, which may be at least a part of a mobile station or UE as a target of a multicast service, such as UE1, UE2, UE3, UE4, and UE5 in the above examples as illustrated in FIG. 1 to FIG. 6.
  • the example apparatus 800 may include at least one processor 801 and at least one memory 802 that may include computer program code 803.
  • the at least one memory 802 and the computer program code 803 may be configured to, with the at least one processor 801, cause the apparatus 800 at least to perform at least the operations of the example method 700 described above.
  • the at least one processor 801 in the example apparatus 800 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU) , a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) . Further, the at least one processor 801 may also include at least one other circuitry or element not shown in FIG. 8.
  • at least one hardware processor including at least one microprocessor such as a central processing unit (CPU) , a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) .
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the at least one memory 802 in the example apparatus 800 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory.
  • the volatile memory may include, but not limited to, for example, a random-access memory (RAM) , a cache, and so on.
  • the non-volatile memory may include, but not limited to, for example, a read only memory (ROM) , a hard disk, a flash memory, and so on.
  • the at least memory 802 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
  • the example apparatus 800 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
  • the circuitries, parts, elements, and interfaces in the example apparatus 800 may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
  • FIG. 9 illustrates another example apparatus 900 for multicast service data compensation in an example embodiment, which may be at least a part of a mobile station or UE as a target of a multicast service, such as UE1, UE2, UE3, UE4, and UE5 in the above examples as illustrated in FIG. 1 to FIG. 6.
  • the example apparatus 900 may include means 901 for performing the operation 701 of the example method 700, means 902 for performing the operation 702 of the example method 700, and means 903 for performing the operation 703 of the example method 700.
  • at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 900.
  • examples of means in the apparatus 900 may include circuitries.
  • examples of means may also include software modules and any other suitable function entities.
  • one or more additional means may be included in the apparatus 900 for performing one or more additional operations of the example method 700.
  • circuitry throughout this disclosure may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) ; (b) combinations of hardware circuits and software, such as (as applicable) (i) a combination of analog and/or digital hardware circuit (s) with software/firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) ; and (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
  • hardware-only circuit implementations such as implementations in only analog and/or digital circuitry
  • combinations of hardware circuits and software such as (as applicable) (i) a
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • FIG. 10 illustrates an example method 1000 for multicast service data compensation in an example embodiment, which may be performed in a base station in the network (for example, the network in the above examples as illustrated in FIG. 1 to FIG. 6) , which is serving one or more UEs as targets of a multicast service.
  • the example method may include an operation 1001 and an operation 1002, which may correspond to the operation 701 and the operation 702 of the example method 700, respectively.
  • At least one data unit of a multicast service may be transmitted to a set of UEs via an MTCH based on a group identity (for example, G-NRTI1 in FIG. 1 and FIG. 2, G-RNTI3 in FIG. 3 and FIG. 4, and G-RNTI5 in FIG. 5 and FIG. 6) .
  • a group identity for example, G-NRTI1 in FIG. 1 and FIG. 2, G-RNTI3 in FIG. 3 and FIG. 4, and G-RNTI5 in FIG. 5 and FIG. 6 .
  • At least a part of the at least one data unit may be retransmitted to at least one UE in the set of UEs via the MTCH based on at least one another group identity (for example, G-NRTI2 in FIG. 1 and FIG. 2, G-RNTI4 in FIG. 3 and FIG. 4, and G-RNTI6 and G-RNTI7 in FIG. 5 and FIG. 6) .
  • group identity for example, G-NRTI2 in FIG. 1 and FIG. 2, G-RNTI4 in FIG. 3 and FIG. 4, and G-RNTI6 and G-RNTI7 in FIG. 5 and FIG. 6 .
  • the at least one another group identity may include at least one of: a group identity for data units missed due to gap-assisted measurement of the UE; a group identity for data units missed or improperly received due to decoding failure; a group identity for data missed or improperly received due to cell handover; and so on.
  • the example method 1000 may further include an additional operation, where configuration information associated with the at least one another identity (for example, the information 202 in FIG. 2, the information 402 in FIG. 4, and the information 602 and 603 in FIG. 6) may be transmitted to the at least one UEs.
  • the transmission of the configuration information associated with the at least one another identity may be via RRC reconfiguration information, or broadcasted system information, or the like.
  • the configuration information associated with the at least one another identity may be included in at least one of measurement gap configuration information, retransmission configuration information, and any other suitable configuration information.
  • the retransmission may be performed after a measurement gap of one or more target UEs of the multicast service, and the retransmitted part may correspond to a part of the at least one data unit during the measurement gap.
  • the example method 1000 may further include an additional operation, where information associated with at least one missed or improperly received data unit (for example, the information 405 in FIG. 4, and the information 608 in FIG. 6) may be received from the at least one UEs, and the retransmitted part may be determined based on the received information.
  • information associated with at least one missed or improperly received data unit for example, the information 405 in FIG. 4, and the information 608 in FIG. 6
  • the example method 1000 may further include an additional operation, where information associated with at least one missed or improperly received data unit (for example, the information 405 in FIG. 4, and the information 608 in FIG. 6) may be received from the at least one UEs, and the retransmitted part may be determined based on the received information.
  • granularities of the transmission of the at least one data unit and the retransmission of the part of the at least one data unit may be at a multicast radio bearer level, so as to provide a fine granularity. In some example embodiments, the granularities of the transmission of the at least one data unit and the retransmission of the part of the at least one data unit may also be at any other suitable level, such as a channel level.
  • the example method 1000 may further include an additional operation, where capability information of the set of UEs may be received from the set of UEs, and the at least one another group identity may be configured based on the capability information of the set of UEs.
  • the transmission of the at least one data unit based on the group identity and the retransmission of at least a part of the at least one data unit based on the at least one another group identity may be performed by either the same or different cells.
  • the at least one data unit of the multicast service may be transmitted from a primary cell based on a group identity, and at least a part of the at least one data unit may be transmitted from one or more secondary cells based on at least one another group identity to compensate the data part missed or improperly received by one or more target UEs of the multicast service.
  • the at least one data unit of the multicast service may be transmitted from a primary cell based on a group identity, and at least a part of the at least one data unit may be transmitted from a primary secondary cell based on at least one another group identity.
  • the at least one data unit of the multicast service may be transmitted from a primary secondary cell based on a group identity, and at least a part of the at least one data unit may be transmitted from one or more secondary cells based on at least one another group identity.
  • the part of the multicast service data missed or improperly received by one or more target UEs may be retransmitted based on one or more another configured group identities (for example, one or more another G-RNTIs) .
  • the missed or improperly received data part of the multicast service may be compensated for the UE without interrupting the normal data reception of the multicast service.
  • FIG. 11 illustrates another example apparatus 1100 for multicast service data compensation in an example embodiment, which may be at least a part of a base station in the network, which is serving one or more UEs as targets of a multicast service.
  • the example apparatus 1100 may include at least one processor 1101 and at least one memory 1102 that may include computer program code 1103.
  • the at least one memory 1102 and the computer program code 1103 may be configured to, with the at least one processor 1101, cause the apparatus 1100 at least to perform at least the operations of the example method 1000 described above.
  • the at least one processor 1101 in the example apparatus 1100 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example FPGA and ASIC. Further, the at least one processor 1101 may also include at least one other circuitry or element not shown in FIG. 11.
  • the at least one memory 1102 in the example apparatus 1100 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory.
  • the volatile memory may include, but not limited to, for example, a RAM, a cache, and so on.
  • the non-volatile memory may include, but not limited to, for example, a ROM, a hard disk, a flash memory, and so on.
  • the at least memory 1102 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
  • the example apparatus 1100 may also include at least one other circuitry, element, and interface, for example at least one I/O interface, at least one antenna element, and the like.
  • the circuitries, parts, elements, and interfaces in the example apparatus 1100 may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
  • FIG. 12 illustrates another example apparatus 1200 for multicast service data compensation in an example embodiment, which may be at least a part of a base station in the network, which is serving one or more UEs as targets of a multicast service.
  • the example apparatus 1200 may include means 1201 for performing the operation 1001 of the example method 1000, and means 1202 for performing the operation 1002 of the example method 1000.
  • at least one I/O interface, at least one antenna element, and the like may also be included in the example apparatus 1200.
  • examples of means in the apparatus 1200 may include circuitries.
  • examples of means may also include software modules and any other suitable function entities.
  • one or more additional means may be included in the apparatus 1200 for performing one or more additional operations of the example method 1000.
  • Another example embodiment may relate to computer program codes or instructions which may cause an apparatus to perform at least respective methods described above.
  • Another example embodiment may be related to a computer readable medium having such computer program codes or instructions stored thereon.
  • a computer readable medium may include at least one storage medium in various forms such as a volatile memory and/or a non-volatile memory.
  • the volatile memory may include, but not limited to, for example, a RAM, a cache, and so on.
  • the non-volatile memory may include, but not limited to, a ROM, a hard disk, a flash memory, and so on.
  • the non-volatile memory may also include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
  • the words “comprise, ” “comprising, ” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to. ”
  • the word “coupled” refers to two or more elements that may be either directly connected, or connected by way of one or more intermediate elements.
  • the word “connected” refers to two or more elements that may be either directly connected, or connected by way of one or more intermediate elements.
  • conditional language used herein such as, among others, “can, ” “could, ” “might, ” “may, ” “e.g., ” “for example, ” “such as” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain example embodiments include, while other example embodiments do not include, certain features, elements and/or states.
  • conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more example embodiments or that one or more example embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular example embodiment.

Landscapes

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

Abstract

L'invention concerne des procédés permettant de compenser une perte de données d'un service de multidiffusion dans des systèmes de télécommunication. Un procédé donné à titre d'exemple peut consister à : recevoir au moins une unité de données d'un service de multidiffusion par le biais d'un canal de trafic de multidiffusion sur la base d'une identité de groupe ; recevoir au moins une unité de données retransmise du service de multidiffusion par le biais du canal de trafic de multidiffusion sur la base d'au moins une autre identité de groupe ; et déterminer les données du service de multidiffusion d'après la ou les premières unités de données et la ou les secondes unités de données retransmise. Des appareils et des supports lisibles par ordinateur associés sont également divulgués.
PCT/CN2021/071016 2021-01-11 2021-01-11 Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications WO2022147814A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/071016 WO2022147814A1 (fr) 2021-01-11 2021-01-11 Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications
CN202180090119.0A CN116848812A (zh) 2021-01-11 2021-01-11 补偿电信系统中的组播服务数据损失

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071016 WO2022147814A1 (fr) 2021-01-11 2021-01-11 Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications

Publications (1)

Publication Number Publication Date
WO2022147814A1 true WO2022147814A1 (fr) 2022-07-14

Family

ID=82357627

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071016 WO2022147814A1 (fr) 2021-01-11 2021-01-11 Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications

Country Status (2)

Country Link
CN (1) CN116848812A (fr)
WO (1) WO2022147814A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008115023A1 (fr) * 2007-03-21 2008-09-25 Electronics And Telecommunications Research Institute Transmission et réception de données mbms dans un système de communication mobile par paquets
WO2009048296A2 (fr) * 2007-10-10 2009-04-16 Lg Electronics Inc. Procédé permettant de retransmettre des trames multidiffusion et procédé permettant de traiter les trames multidiffusion dans un réseau sans fil
CN101536407A (zh) * 2006-11-13 2009-09-16 高通股份有限公司 用于无线网络中的可靠的多播的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101536407A (zh) * 2006-11-13 2009-09-16 高通股份有限公司 用于无线网络中的可靠的多播的方法和装置
WO2008115023A1 (fr) * 2007-03-21 2008-09-25 Electronics And Telecommunications Research Institute Transmission et réception de données mbms dans un système de communication mobile par paquets
WO2009048296A2 (fr) * 2007-10-10 2009-04-16 Lg Electronics Inc. Procédé permettant de retransmettre des trames multidiffusion et procédé permettant de traiter les trames multidiffusion dans un réseau sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Reliability for multicast operation", 3GPP DRAFT; R2-2009961, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20201102 - 20201113, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941482 *

Also Published As

Publication number Publication date
CN116848812A (zh) 2023-10-03

Similar Documents

Publication Publication Date Title
CN110115090B (zh) 通信系统
US11638236B2 (en) Control channel structure design to support V2X traffic
US20170294989A1 (en) Method and device for data transmission
US8805318B2 (en) Method of handling data transmission associated with natural disaster notification in a wireless communication system and related apparatus
CN112640550B (zh) 反馈信息的传输装置及方法
US20170353906A1 (en) Method and device for data transmission
CN116602003A (zh) 多播-广播服务移动性和服务连续性
EP3499925A1 (fr) Procédé et dispositif de transmission de changement d'informations destinés à un service de multidiffusion à cellule unique
CN108370562B (zh) 一种跨载波调度方法、反馈方法及装置
CN113439457A (zh) 连接状态下的移动性增强
US20230027505A1 (en) Downlink data receiving method, downlink data sending method, and device
US20230413286A1 (en) Information transmission processing method and device, and user equipment
WO2022061912A1 (fr) Procédés et appareil d'une opération harq pour la transmission d'un service de diffusion multidiffusion
WO2022147814A1 (fr) Compensation de perte de données d'un service de multidiffusion dans des systèmes de télécommunications
WO2022021339A1 (fr) Procédés, appareils et supports lisibles par ordinateur de réglage de la couverture d'un service de diffusion/multidiffusion multimédia
US20190140786A1 (en) Method, system and apparatus
CN107529147B (zh) 一种无线传输的方法和装置
US20240163027A1 (en) Method and apparatus for negative acknowledgement (nack)-only based hybrid automatic repeat-request acknowledgement (harq-ack) feedback multiplexing
US20240073928A1 (en) Apparatus, method, and computer program
WO2023151076A1 (fr) Procédé et appareil de réception de retransmission à base de ptp pour multidiffusion
US20240163045A1 (en) Wireless communication method, terminal device, and network device
US20240214875A1 (en) User equipment, source base station, target base station, and handover methods for ue mbs mobility with service continuity
WO2023205949A1 (fr) Procédés d'alignement de champ de l'indicateur de nouvelles données (ndi) permettant une réception fiable du trafic de multidiffusion
US20240056901A1 (en) Method and apparatus for multicast and broadcast services
US20240187140A1 (en) 5g multicast-broadcast services (mbs) multiplexing, reliability, and power savings

Legal Events

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

Ref document number: 21916869

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180090119.0

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21916869

Country of ref document: EP

Kind code of ref document: A1