Patent Description:
In a long term evolution (Long Term Evolution, LTE) system, a multicast broadcast service (Multicast and Broadcast Service, MBS) is transmitted in an unacknowledged mode (Unacknowledged Mode, UM). In addition, a sender of the MBS does not support hybrid automatic repeat request (Hybrid automatic repeat request, HARQ) retransmission, and this means that data packets arrive in order definitely and that a receiver of the MBS does not perform any reordering operation. Therefore, there is no packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer for performing a reordering operation in a layer <NUM> (L2) protocol stack of the receiver, and there is only a radio link control (Radio Link Control, RLC) layer.

<CIT> discloses an improved method of receiving the point-to-multipoint service data in a wireless communication system in order to minimize a data loss by a reception entity.

<CIT> discloses that an unacknowledged mode (UM) radio link control (RLC) entity receives RLC protocol data units (PDUs) delivered through one or more logical channels and re-orders the received PDUs by referring to their sequence numbers and by using a receive window and a timer to minimize delivery delay time, to reduce missing PDUs received from each logical channel, and to process the PDUs by avoiding duplicate PDUs.

<CIT>discloses data multicast or broadcast on a control channel to support narrowband communication. Data for a broadcast or multicast service may be sent over a control channel. A network device may broadcast a message to indicate a plurality of enhanced multimedia broadcast multicast service (eMBMS) services offered by the network. The mobile device may transmit an indication to the network device identifying an eMBMS service of interest. The network device may transmit a configuration message before broadcasting or multicasting data of the eMBMS service of interest. The configuration message may notify the mobile device of a control channel on which to receive the data related to the eMBMS service. The network device may then broadcast or multicast the eMBMS service data on the control channel. The data may be segmented at a particular protocol layer and mapped to several transmission time intervals within each repetition of the control channel.

In a new radio (New Radio, NR) system, a supported MBS has features different from those in LTE. For example, some MBSs need to support certain transmission reliability, and HARQ feedback (feedback) and retransmission mechanisms may be required. This causes arrival of data packets of an MBS out of order and causes a problem that a receiver cannot receive the MBS correctly.

An objective of embodiments of this application is to provide a multicast service receiving method, a multicast service configuration method, a terminal, and a network-side device as defined in the appended set of claims to resolve a problem that a receiver cannot correctly receive an MBS in a case that data packets of the MBS arrive out of order.

In the embodiments of this application, the terminal can separately perform, based on network-side configurations, different operations on an MBS service that requires out-of-order processing and an MBS service that does not require out-of-order processing, to receive the services correctly and ensure MBS service experience of the terminal and system efficiency.

Apparently, the described embodiments are only some rather than all of the embodiments of this application.

The terms "first", "second", and the like in this specification and claims of this application are used to distinguish between similar objects instead of describing a specific order or sequence. It should be understood that the terms used in this way are interchangeable in appropriate circumstances, so that the embodiments of this application can be implemented in other orders than the order illustrated or described herein. In addition, objects distinguished by "first" and "second" usually fall within one class, and a quantity of objects is not limited. For example, there may be one or more first objects. In addition, the term "and/or" in the specification and claims indicates at least one of connected objects, and the character "/" generally represents an "or" relationship between associated objects.

It should be noted that technologies described in the embodiments of this application are not limited to a long time evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in other wireless communications systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency-division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application are usually used interchangeably. The described technologies may be used for the foregoing systems and radio technologies, and may also be used for other systems and radio technologies. However, in the following descriptions, a new radio (New Radio, NR) system is described for an illustration purpose, and NR terms are used in most of the following descriptions, although these technologies may also be applied to other applications than an NR system application, for example, a 6th generation (6th Generation, <NUM>) communications system.

<FIG> is a schematic diagram of a wireless communications system to which an embodiment of this application may be applied. The wireless communications system includes a terminal <NUM> and a network-side device <NUM>. The terminal <NUM> may also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal <NUM> may be a terminal-side device such as a mobile phone, a tablet personal computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device), a vehicular device (VUE), or a pedestrian terminal (PUE). The wearable device includes a hand ring, an earphone, glasses, or the like. It should be noted that a specific type of the terminal <NUM> is not limited in the embodiments of this application. The network-side device <NUM> may be a base station or a core network. The base station may be referred to as a NodeB, an evolved NodeB, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home NodeB, a home evolved NodeB, a WLAN access point, a Wi-Fi node, a transmission and reception point (Transmitting Receiving Point, TRP), or another appropriate term in the art, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only a base station in an NR system is used as an example, but a specific type of the base station is not limited.

A multicast service receiving method, a multicast service configuration method, a terminal, and a network-side device provided in the embodiments of this application are hereinafter described in detail by using specific embodiments and application scenarios thereof with reference to the accompanying drawings.

In the LTE system, a multicast broadcast service (Multicast and Broadcast Service, MBS) or multimedia multicast broadcast service (Multimedia Broadcast Multicast Service, MBMS) can be sent in an MBMS single frequency network (Multimedia Broadcast multicast service Single Frequency Network, MBSFN) mode and sent in a single cell point to multipoint (Single cell Point to Multipoint, SC-PTM) mode. In the MBSFN mode, cells in a same MBSFN area synchronously send a same broadcast service, so that user equipment (User Equipment, UE, also referred to as a terminal) receives the service conveniently. Control information (control channel parameters, traffic channel parameters, scheduling information, and the like) and data information of the MBMS service are all sent in a broadcast mode, so that both UE in an idle (idle) state and UE in a connected state can receive the MBMS service. A greatest difference between the SC-PTM mode and the MBSFN mode is that scheduling and sending are performed only in a single cell and that service scheduling is performed by using a g-RNTI (group RNTI). The control channel parameters, a service identity, period information, and the like are broadcast in a broadcast message. The scheduling information is notified by using a physical downlink control channel (Physical Downlink Control Channel, PDCCH) scrambled by the g-RNTI. A data part is sent in a multicast mode. This means that interested UE listens to the g-RNTI to obtain data scheduling and then perform reception.

<FIG> is a schematic diagram of an architecture of an LTE MBMS user plane protocol stack. It can be seen from <FIG> that there is no PDCP layer in an L2 protocol stack of an LTE multicast service and that there is only an RLC layer. Enhancements made at the RLC layer for the multicast service mainly include introduction of a corresponding logical channel, a multicast traffic channel (Multicast Traffic Channel, MTCH), and a multicast control channel (Multicast Control Channel, MCCH), and subsequent addition of a single cell multicast traffic channel (Single Cell Multicast Traffic Channel, SC-MTCH), and a single cell multicast control channel (Single Cell Multicast Control Channel, SC-MCCH). In addition, for reception of the MTCH, MCCH, SC-MTCH, and SC-MCCH, it is clearly indicated that no reordering operation is performed, and a reordering window UM_Window_Size is equal to <NUM>.

Both the LTE MBMS transmission mode and the SC-PTM transmission mode use an unacknowledged mode (Unacknowledged Mode, UM) for transmission. In addition, a sender does not support any hybrid automatic repeat request (Hybrid automatic repeat request acknowledgement, HARQ) retransmission. This means that data packets arrive in order definitely and that a receiver does not perform any reordering operation, where a reordering window size is <NUM>. When the UE is interested in the multicast service, an RLC entity of the MTCH (media access control (Media Access Control, MAC) and a physical layer (Physical Layer, PHY) are configured accordingly) is established for reception. When the UE is not interested in the multicast service, the corresponding RLC entity is released. For sending in the MBSFN mode, because all base stations in a specific area perform sending synchronously, when the UE moves between cells, the RLC entity for receiving the MTCH does not need to be reestablished or reset. However, because an SC-PTM service is sent by a single cell, even if its neighboring cells support the same SC-PTM service, the SC-PTM service is sent independently. Therefore, when the UE is handed over between cells, the UE releases an RLC entity corresponding to an old SC-MTCH and establishes an RLC entity of a new SC-MTCH for multicast service reception in a new cell.

Considering that functions of an NR L2 protocol stack are adjusted in comparison with those in LTE, and typically a data packet reordering function is migrated from an RLC layer to a PDCP layer, an L2 protocol stack for receiving an NR MBS service may need to support the PDCP layer protocol. These differences mean that an L2 (mainly the RLC and PDCP layers) behavior for receiving an MBS in NR needs to be redesigned and cannot be the same as that in LTE; otherwise, a receiving error is caused, and an unnecessary packet loss and user experience degradation are caused.

To resolve the foregoing problem, referring to <FIG>, an embodiment of this application provides a multicast service receiving method. The method is applied to a terminal and includes the following steps.

Step <NUM>: Receive configuration information of an MBS service sent by a network-side device, where the configuration information of the MBS service includes information for determining whether to enable reordering for a PDCP layer and/or an RLC layer.

In this embodiment of this application, optionally, each MBS service corresponds to its own configuration information.

Step <NUM>: Receive the MBS service based on the configuration information of the MBS service.

In this embodiment of this application, the terminal can separately perform, based on network-side configurations, different operations on an MBS service that requires out-of-order processing and an MBS service that does not require out-of-order processing, to receive the services correctly and ensure MBS service experience of the terminal and system efficiency.

The information for determining whether to enable reordering for the PDCP layer and/or the RLC layer in the configuration information of the MBS service may be in various forms. The following uses examples for description.

It should be noted that the PDCP layer does not always exist for MBS-related RBs. The PDCP layer may exist for some MBS services, and may not exist for some MBS services. However, the RLC layer always exists for all MBS-related RBs. A difference lies in that operations performed are different, for example, whether reordering is enabled.

The reordering parameter of the PDCP layer may include at least one of the following: a reordering window, a reordering timer, and an SN space size.

The reordering parameter of the RLC layer may include at least one of the following: a reordering window, a reordering timer, and an SN space size.

In this embodiment of this application, the reordering window, the reordering timer, and the SN space size may be all configured by the network side, or all prescribed in a protocol, or partially set by the network side and partially prescribed in a protocol. For example, the reordering timer is configured by the network side, the SN space size is prescribed in a protocol, and the reordering window is prescribed as half of the SN space size. For another example, the SN space size is configured by the network side, and the reordering window is prescribed as half of the SN space size.

In this embodiment of this application, whether to enable reordering for the PDCP layer may be directly indicated in the configuration parameter of the PDCP layer, or may not be directly indicated in the configuration parameter of the PDCP layer; instead, whether to enable reordering for the PDCP layer is indicated by whether the reordering parameter of the PDCP layer is configured. For example, if the reordering window is configured in the reordering parameter of the PDCP layer, it is determined to enable reordering for the PDCP layer. For another example, if the SN space size is configured in the reordering parameter of the PDCP layer, it is determined to enable reordering for the PDCP layer.

To be specific, the method further includes:.

In this embodiment of this application, whether to enable reordering for the RLC layer may be directly indicated in the configuration parameter of the RLC layer, or may not be directly indicated in the configuration parameter of the RLC layer; instead, whether to enable reordering for the RLC layer is indicated by whether the reordering parameter of the RLC layer is configured. For example, if the reordering window is configured in the reordering parameter of the RLC layer, it is determined to enable reordering for the RLC layer. For another example, if the SN space size is configured in the reordering parameter of the RLC layer, it is determined to enable reordering for the RLC layer.

Further optionally, the configuration information of the MBS service includes both the configuration parameter of the PDCP layer and the configuration parameter of the RLC layer, and reordering is configured as enabled for both the PDCP layer and the RLC layer, or reordering is configured as disabled for both the PDCP layer and the RLC layer.

In some embodiments of this application, if the configuration information of the MBS service does not explicitly or implicitly indicate whether the PDCP layer is required, whether the PDCP layer is required is prescribed in a protocol, and the PDCP layer may be required by default. For example, regardless of a radio bearer (RB) type, to unify protocol stacks, an NR MBS requires a PDCP layer, but different operations (for example, whether reordering is required) are performed.

In some embodiments of this application, the receiving the MBS service based on the configuration information of the MBS service includes one of the following:.

In this embodiment of this application, the configuration information of the MBS service may further include other L2 layer configurations.

In this embodiment of this application, the configuration information of the MBS service may further include configurations of other layers (such as a MAC layer).

(II) In some embodiments of this application, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes: indication information, used to indicate whether to enable reordering for the PDCP layer and/or the RLC layer. The indication information may be represented by one bit.

In other words, the indication information is used to explicitly indicate whether to enable reordering for the PDCP layer and/or the RLC layer.

Optionally, the receiving the MBS service based on the configuration information of the MBS service includes one of the following:.

For each MBS service, the foregoing (I) and (II) are intended to explicitly indicate whether to enable reordering for the PDCP layer and/or the RLC layer. Certainly, whether to enable reordering for the PDCP layer and/or the RLC layer may alternatively be implicitly indicated.

(III) In some embodiments of this application, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes: first configuration information, used to implicitly indicate whether to enable reordering for the PDCP layer and/or the RLC layer.

Optionally, the first configuration information includes at least one of the following: a HARQ feedback (feedback) configuration parameter, a QoS related parameter, a block error rate, and whether to enable an in-order delivery function for a service layer.

Optionally, the HARQ feedback configuration parameter includes at least one of the following: whether the MBS service requires a HARQ feedback; and a parameter used for the HARQ feedback. The parameter used for the HARQ feedback includes, for example, NACK based or ACK/NACK based; whether all UEs perform feedbacks in one time-frequency position or UEs perform feedbacks in a specific position or a group position; HARQ process (process) count reservation and calculation method introduced for supporting the feedback; or the maximum number of retransmissions.

Optionally, the first configuration information includes the HARQ feedback configuration parameter; and the receiving the MBS service based on the configuration information of the MBS service includes one of the following:.

(<NUM>) If the MBS service does not require the HARQ feedback (disable), determining at least one of the following: not requiring the PDCP layer; disabling reordering for the PDCP layer; disabling reordering for the RLC layer; and using a first group of default configuration parameters for the PDCP layer and/or the RLC layer, where the first group of default configuration parameters includes at least one of the following: a reordering window size is <NUM> and a reordering timer length is <NUM>.

For example, if the MBS service does not require the HARQ feedback (disable), there is no disorder, and it is determined that the PDCP layer is not required.

For example, if the MBS service does not require the HARQ feedback (disable), there is no disorder, and it is determined that the PDCP layer is required (the PDCP layer may exist for a unified architecture), but reordering does not need to be enabled.

For example, if the MBS service does not require the HARQ feedback (disable), there is no disorder, and it is determined that reordering does not need to be enabled for the RLC layer.

(<NUM>) If the MBS service requires the HARQ feedback (enable), determining at least one of the following: requiring the PDCP layer; enabling reordering for the PDCP layer; enabling reordering for the RLC layer; and using a second group of default configuration parameters for the PDCP layer and/or the RLC layer, where the second group of default configuration parameters includes at least one of the following: a reordering window size is N1 and a reordering timer length is m1, where both N1 and m1 are non-zero positive values.

For example, if the MBS service requires the HARQ feedback (enable), it is determined that the PDCP layer is required, and reordering is enabled for the PDCP layer.

For example, if the MBS service requires the HARQ feedback (enable), it is determined that reordering needs to be enabled for the RLC layer.

(<NUM>) If the MBS service requires the HARQ feedback, determining at least one of the following: requiring the PDCP layer; enabling reordering for the PDCP layer; enabling reordering for the RLC layer; and using a third group of default configuration parameters for the PDCP layer and using a fourth group of default configuration parameters for the RLC layer, where the third group of default configuration parameters includes at least one of the following: a reordering window size is N2 and a reordering timer length is m2, and the fourth group of default configuration parameters includes at least one of the following: a reordering window size is N3 and a reordering timer length is m3, where N2, m2, N3, and m3 are all non-zero positive values.

The foregoing (<NUM>) to (<NUM>) are intended to determine, according to whether the MBS service requires the HARQ feedback, whether to enable reordering for the PDCP layer and/or the RLC layer.

In this embodiment of this application, whether to enable reordering for the PDCP layer and/or the RLC layer may also be determined according to whether the MBS service requires the HARQ feedback and other configurations.

(<NUM>) If the MBS service requires the HARQ feedback, and only one HARQ process (process) is configured for the MBS service, or the network-side device explicitly or implicitly indicates that MBS data packets are not out of order, determining at least one of the following: not requiring the PDCP layer; disabling reordering for the PDCP layer; disabling reordering for the RLC layer; and using a first group of default configuration parameters for the PDCP layer and/or the RLC layer, where the first group of default configuration parameters includes at least one of the following: a reordering window size is <NUM> and a reordering timer length is <NUM>.

For example, although the MBS service requires the HARQ feedback, only one HARQ process (process) is configured for the MBS service, or the network-side device explicitly or implicitly indicates that MBS data packets are not out of order. In this case, there is no disorder, and it is determined to disable reordering for the PDCP layer.

(<NUM>) If the MBS service requires the HARQ feedback, and a plurality of HARQ processes are configured for the MBS service, or the network-side device explicitly or implicitly indicates that MBS data packets are out of order, determining at least one of the following: requiring the PDCP layer; enabling reordering for the PDCP layer; enabling reordering for the RLC layer; and using a second group of default configuration parameters for the PDCP layer and/or the RLC layer, where the second group of default configuration parameters includes at least one of the following: a reordering window size is N1 and a reordering timer length is m1, where both N1 and m1 are non-zero positive values.

For example, if the MBS service requires the HARQ feedback, and a plurality of HARQ processes are configured for the MBS service, or the network-side device explicitly or implicitly indicates that MBS data packets are out of order, it is determined to enable reordering for the PDCP layer.

(<NUM>) If the MBS service requires the HARQ feedback, and a plurality of HARQ processes are configured for the MBS service, or the network-side device explicitly or implicitly indicates that MBS data packets are out of order, determining at least one of the following: requiring the PDCP layer; enabling reordering for the PDCP layer; enabling reordering for the RLC layer; and using a third group of default configuration parameters for the PDCP layer and using a fourth group of default configuration parameters for the RLC layer, where the third group of default configuration parameters includes at least one of the following: a reordering window size is N2 and a reordering timer length is m2, and the fourth group of default configuration parameters includes at least one of the following: a reordering window size is N3 and a reordering timer length is m3, where N2, m2, N3, and m3 are all non-zero positive values.

Whether to enable reordering for the PDCP layer and/or the RLC layer can also be determined based on other configuration information of the MBS service such as the QoS related parameter, the block error rate, and whether to enable the in-order delivery function for the service layer, in addition to the HARQ feedback configuration parameter. For example, when the block error rate is required to be lower than a preset threshold, it is determined to enable reordering for the PDCP layer and/or the RLC layer.

In this embodiment of this application, optionally, in addition to the foregoing content, the configuration information of the MBS service may further include:.

The terminal obtains the configuration information of the MBS service from the network side. If the terminal is interested in the MBS service, the terminal can establish a related protocol stack based on the configuration on the network side, and perform related initialization and update operations to correctly receive and process the MBS service.

The following describes how to perform an initialization process of the PDCP layer and the RLC layer after the terminal obtains the configuration information of the MBS service.

Because the PDCP layer and the RLC layer can be configured together or separately, a configuration mode does not affect a final initialization behavior. In this embodiment, initialization behaviors of the two layers are described separately.

In this embodiment of this application, optionally, the receiving the MBS service based on the configuration information of the MBS service includes one of the following:.

Main functions of the PDCP layer are to implement functions such as header compression, security, and reordering, for an NR MBS service, and these functions may not be required. Therefore, the entire PDCP layer can be directly removed in this case.

For an NR MBS service, it is possible that only the header compression function and/or the security function are/is required. In this case, alternatively, the PDCP layer may be established with the reordering function removed.

For an NR MBS service, it is possible that none of the header compression function and the security and reordering functions is required, but to unify the protocol stacks, the PDCP layer can be established to perform transparent transmission or basic functions.

Optionally, the establishing the PDCP layer for which reordering is disabled includes at least one of the following:.

In the process of receiving the MBS service at the PDCP layer, it is specified that reordering is not performed.

The count value is fixed to <NUM> bits, and the SN space size is variable, such as <NUM> bits or <NUM> bits. The SN is low bits of the count value, and remaining high bits are referred to as an HFN. This means that the SN forms the low bits of the count value and that the HFN forms the high bits of the count value. When the SN is <NUM> bits, the <NUM>-bit SN and a <NUM>-bit HFN constitute a complete count value. When the SN is <NUM> bits, the <NUM>-bit SN and a <NUM>-bit HFN constitute a complete count value.

Optionally, the establishing the PDCP layer for which reordering is enabled includes at least one of the following:.

In the process of receiving the MBS service at the PDCP layer, it is specified that reordering is performed.

The establishing the RLC layer for which reordering is enabled includes at least one of the following:.

In the process of receiving the MBS service at the RLC layer, it is specified that reordering is performed.

Optionally, the establishing the RLC layer for which reordering is disabled includes at least one of the following:.

In the process of receiving the MBS service at the RLC layer, it is specified that reordering is not performed.

The following describes a subsequent status update process after the terminal obtains the configuration information of the MBS service and performs initialization operations on the PDCP layer and the RLC layer.

When the PDCP layer is configured not to support out-of-order reception, its SN and count value are both initialized to <NUM> (similar to an ordinary data radio bearer (Data Radio Bearer, DRB)), the reordering timer is <NUM>, and there is no need to perform the reordering function.

Optionally, the receiving the MBS service based on the configuration information of the MBS service includes: if reordering is configured as disabled for the PDCP layer, considering each received data packet as a data packet that is outside the reordering window and that does not require any duplication detection and packet deletion processing, directly obtaining a service data unit (Service Data Unit, SDU) through parsing (depending on the configuration of the service, operations mainly include decompressing a header, deciphering and/or integrity verification, removing a PDCP header, and the like) and then delivering the SDU to the higher layer, and directly setting an SN part of a variable RX_NEXT or RX_DELIV (a count value is <NUM> bits, its low bit part is an SN, and a high bit part is an HFN; and if the SN is <NUM> bits, the HFN is <NUM> high bits; or if the SN is <NUM> bits, the HFS is <NUM> high bits) of the PDCP layer to an SN of the received data packet or SN+<NUM>, and setting an HFN part to <NUM> or any other arbitrary or prescribed value that ensures that the count value is positive, where the arbitrary value usually corresponds to an MBS service that does not require a security operation, and the prescribed value usually corresponds to an MBS service that requires unified security processing at a sender and a receiver.

When the PDCP layer is configured to support out-of-order reception, its SN and count value are both initialized and set based on the SN carried in the first received data packet (different from an ordinary DRB), the reordering timer length is a positive value, and the reordering function needs to be performed.

Optionally, the receiving the MBS service based on the configuration information of the MBS service includes:.

When the RLC layer is configured not to support out-of-order reception, values of all its SN variables are initialized to <NUM> (similar to an ordinary DRB), the reordering timer is <NUM>, and there is no need to perform the reordering function.

Optionally, the receiving the MBS service based on the configuration information of the MBS service includes:
if reordering is configured as disabled for the RLC layer, considering that segments of each received RLC protocol data unit (Protocol Data Unit, PDU) are in order, that is, for a data packet with RLC SN=x, first receiving a first segment, then receiving a second segment, then receiving a third segment, until a last segment is successfully received, and then receiving a data packet with RLC SN=x+<NUM>. No timer is started or restarted, and there is no need to perform the reordering function. This means that if the first segment is received and then the third segment is received, the UE considers the second segment is lost and will not be retransmitted. In this case, it may be directly determined that the data packet with RLC SN=x fails to be received, and it is unnecessary to wait any longer, and a data packet with RLC SN=x+<NUM> is expected, that is, the RX_Next_Reassembly and/or RX_Next_Highest variables are/is directly set to x+<NUM>.

When the RLC layer is configured to support out-of-order reception, values of all its SN variables are initialized and set based on a first received SN (different from an ordinary DRB), the reordering timer is a positive value, and the reordering function needs to be performed.

In this embodiment of this application, optionally, the receiving the MBS service based on the configuration information of the MBS service includes: if reordering is configured as enabled for the RLC layer, directly delivering a completely received RLC SDU to the higher layer without ordering, and the PDCP performs reordering to reorder every RLC PDU segment.

For example, if a first segment is received and then a third segment is received, a second segment is considered as lost, the reordering timer is started, and the RX_Timer_Trigger variable records an SN number of a corresponding PDU that currently triggers the reordering timer; if the second segment is received before the reordering timer expires, the reordering timer is stopped, reordering is considered as successful, and segments constitute a complete SDU for delivery to the higher layer; if the second segment is still not received when the reordering timer expires, reordering is considered as failed, corresponding waiting for the data packet with this SN is stopped, and an incomplete segment is deleted or a received incomplete segment is delivered to the higher layer, and the higher layer finds a way to parse a part of the data packet.

In this embodiment of this application, optionally, both the PDCP layer and the RLC layer support reordering. This is applied to a case of out-of-order reception, and a correct data receiving process is performed. Alternatively, neither the PDCP layer nor the RLC layer supports reordering. This is applied to a case of in-order reception and a correct data receiving process is performed.

In this embodiment of this application, optionally, an MRB or a DRB is used to carry the MBS service.

The foregoing embodiment mainly focuses on the configuration of the multicast radio bearer (Multicast Radio Bearer, MRB) and L2 layer processing. There are also some other scenarios. For example, the MBS service is carried by unicast (Unicast) or the DRB, or switching is performed between the DRB and the MRB that both carry the MBS service. Similar processing modes may also be considered, to ensure smooth reception of MBS data.

From a perspective of the DRB, initialization and update processing of its PDCP and RLC layer variables are all existing processes. For example, the variables are initialized to <NUM>, and the reordering window size is half of the SN space. Generally, reordering needs to be performed (because the conventional unicast HARQ feedback and retransmission are supported by default), the reordering timer size is configured separately for each bearer, and unacknowledged (UM) and acknowledged (AM) modes may be optionally configured. For the DRB carrying the MBS service, the existing configuration can be directly reused.

Alternatively, the DRB carrying the MBS service is configured in a way different from existing unicast. For example, some new configuration parameters can be introduced, such as duration of the reordering timer, or a reordering function switch is introduced for the PDCP layer and RLC layer of the DRB (that is, the reordering function is not supported by default, and whether the reordering function is supported can be configured).

Generally, a new DRB should be a newly established L2 entity (in a scenario of new establishment, a new configuration can be determined arbitrarily), and initialized. Alternatively, a related L2 entity of the MRB may be considered and directly used for continuity (generally, configuration parameters of PDCP and RLC should be consistent in the continuity scenario; otherwise, continuity is impossible).

To be specific, optionally, the method further includes:.

Because the DRB carrying the MBS service is configured by using dedicated RRC signaling, switching is generally accompanied by dedicated signaling. The dedicated signaling may carry a configuration parameter of the new DRB or even values of some state variables. For example, an initial value of the DRB starts from SN=<NUM>, to continue from the MRB.

Generally, a new MRB should be a newly established L2 entity (in a scenario of new establishment, a new configuration may not consider connection with the previous DRB), and initialized. Alternatively, a related state variable of the previous DRB may be considered for continuity (generally, configuration parameters of PDCP and RLC should be consistent in the continuity scenario; otherwise, continuity is impossible).

Because the MRB needs to take into account idle (Idle)/inactive (Inactive) UEs, there is a high probability that a broadcast/SIB mode is used to send the configuration information of the MBS service. The network side may send a switching indication to the UE, so that the UE reads related configurations from the SIB. Alternatively, the network side may directly send the configuration information of the service carried by the MRB to the corresponding UE by using dedicated signaling, so that the UE receives the service carried by the MRB as soon as possible.

Referring to <FIG>, an embodiment of this application further provides a multicast service configuration method. The method is applied to a network-side device and includes the following step.

Step <NUM>: Send configuration information of an MBS service to a terminal, where the configuration information of the MBS service includes information for determining whether to enable reordering for a PDCP layer and/or an RLC layer.

In this embodiment of this application, the network side configures the configuration information of the MBS service for the terminal, so that the terminal can perform a protocol stack operation corresponding to the MBS service, thereby correctly receiving and processing the MBS service, and ensuring MBS service experience of the terminal and system efficiency.

Optionally, the configuration information of the MBS service is sent to the terminal in at least one of the following modes:.

In this embodiment of this application, the information for determining whether to enable reordering for a PDCP layer and/or an RLC layer in the configuration information of the MBS service may be in various forms. The following uses examples for description.

In some embodiments of this application, optionally, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes at least one of the following:.

The reordering parameter of the PDCP layer may include at least one of the following: a reordering window and a reordering timer. The reordering parameter of the RLC layer may include at least one of the following: a reordering window and a reordering timer.

In some embodiments of this application, optionally, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes:
indication information, used to indicate whether to enable reordering for the PDCP layer and/or the RLC layer.

In some embodiments of this application, optionally, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes:.

It should be noted that the multicast service receiving method provided in this embodiment of this application may be performed by a multicast service receiving apparatus, or a control module configured to perform the multicast service receiving method in the multicast service receiving apparatus. In this embodiment of this application, the multicast service receiving apparatus provided in this embodiment of this application is described by using an example in which the multicast service receiving apparatus performs the multicast service receiving method.

Referring to <FIG>, an embodiment of this application further provides a multicast service receiving apparatus <NUM>, including:.

In this embodiment of this application, the terminal can correctly receive and process the MBS service under control of the network side, thereby ensuring the MBS service experience of the terminal and system efficiency.

Optionally, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes at least one of the following:.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a first execution module, configured to: if the configuration parameter of the PDCP layer includes the reordering parameter of the PDCP layer, perform at least one of the following: determining to enable reordering for the PDCP layer; determining to enable reordering for the RLC layer; if the reordering parameter of the PDCP layer is configured, using the configured reordering parameter, or if the reordering parameter of the PDCP layer is not configured, using a default value; and using a default value for the reordering parameter of the RLC layer; or if the configuration parameter of the PDCP layer does not include the reordering parameter of the PDCP layer, perform at least one of the following: determining to disable reordering for the PDCP layer; and determining to disable reordering for the RLC layer. The configured reordering parameter of the PDCP layer includes at least one of the following: a reordering window, a reordering timer, and a sequence number SN space size.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a second execution module, configured to: if the configuration parameter of the RLC layer includes the reordering parameter of the RLC layer, perform at least one of the following: determining to enable reordering for the PDCP layer; determining to enable reordering for the RLC layer; if the reordering parameter of the RLC layer is configured, using the configured reordering parameter, or if the reordering parameter of the RLC layer is not configured, using a default value; and using a default value for the reordering parameter of the PDCP layer; or if the configuration parameter of the RLC layer does not include the reordering parameter of the RLC layer, determine to disable reordering for the RLC layer. The configured reordering parameter of the RLC layer includes at least one of the following: a reordering window, a reordering timer, and an SN space size.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a third execution module, configured to perform one of the following:.

Optionally, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes:
indication information, used to indicate whether to enable reordering for the PDCP layer and/or the RLC layer.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a fourth execution module, configured to perform one of the following:.

Optionally, the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer includes:.

Optionally, the first configuration information includes the HARQ feedback configuration parameter; and
the multicast service receiving apparatus <NUM> further includes:
a fifth execution module, configured to perform one of the following:.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a sixth execution module, configured to perform one of the following:.

Optionally, an SN part of an initial value of RX_NEXT is equal to the SN of the first received data packet or SN+<NUM> modulo SN space size, and an HFN part needs to ensure RX_NEXT; for example, the HFN part is <NUM> or <NUM>;.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a seventh execution module, configured to perform one of the following:.

Optionally, the establishing the RLC layer for which reordering is enabled includes at least one of the following:.

Optionally, an initial value of RX_Next_Reassembly is set to the SN of the first received RLC PDU or SN+<NUM> modulo SN space size;.

Optionally, the second receiving module is configured to: if reordering is configured as disabled for the PDCP layer, for each received data packet, directly obtain an SDU through parsing and then deliver the SDU to a higher layer, and directly set an SN part of a variable RX_NEXT or RX_DELIV of the PDCP layer to an SN of the received data packet or SN+<NUM>, and set an HFN part to <NUM> or any other arbitrary or prescribed value that ensures that a count value is positive.

Optionally, an MRB or a DRB is used to carry the MBS service.

Optionally, the multicast service receiving apparatus <NUM> further includes:
an eighth execution module, configured to: if switching from an MRB to a DRB is required, receive configuration information of the MBS service of the DRB, and establish a new PDCP layer and/or RLC layer for the DRB based on the configuration information of the MBS service of the DRB; or if switching from an MRB to a DRB is required, use a PDCP layer configuration and/or an RLC configuration of the MRB for the DRB.

Optionally, the multicast service receiving apparatus <NUM> further includes:
a ninth execution module, configured to: if switching from a DRB to an MRB is required, receive configuration information of the MBS service of the MRB, and establish a new PDCP layer and/or RLC layer for the MRB based on the configuration information of the MBS service of the MRB; or if switching from a DRB to an MRB is required, use a PDCP layer configuration and/or an RLC configuration of the DRB for the MRB.

Optionally, the configuration information of the MBS service of the MRB is configured in at least one of the following modes:.

The multicast service receiving apparatus in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile terminal, or may be a nonmobile terminal. For example, the mobile terminal may include but is not limited to the foregoing illustrated type of the terminal <NUM>. The nonmobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine, a self-service machine, or the like. This is not specifically limited in this embodiment of this application.

The multicast service receiving apparatus in this embodiment of this application may be an apparatus having an operating system. The operating system may be an Android (Android) operating system, an iOS operating system, or other possible operating systems, and is not specifically limited in this embodiment of this application.

The multicast service receiving apparatus provided in this embodiment of this application can implement each process implemented by the method embodiment in <FIG>, with the same technical effect achieved. To avoid repetition, details are not described herein again.

It should be noted that the multicast service configuration method provided in this embodiment of this application may be performed by a multicast service configuration apparatus, or a control module configured to perform the multicast service configuration method in the multicast service configuration apparatus. In this embodiment of this application, the multicast service configuration apparatus provided in this embodiment of this application is described by using an example in which the multicast service configuration apparatus performs the multicast service configuration method.

Referring to <FIG>, an embodiment of this application further provides a multicast service configuration apparatus <NUM>, including:
a sending module <NUM>, configured to send configuration information of an MBS service to a terminal, where the configuration information of the MBS service includes information for determining whether to enable reordering for a PDCP layer and/or an RLC layer.

In this application, the network side configures the configuration information of the MBS service for the terminal, so that the terminal can correctly receive and process the MBS service, thereby ensuring the MBS service experience of the terminal and system efficiency.

Optionally, the sending module is configured to send the configuration information of the MBS service to the terminal in at least one of the following modes:.

The multicast service configuration apparatus provided in this embodiment of this application can implement each process implemented by the method embodiment in <FIG>, with the same technical effect achieved. To avoid repetition, details are not described herein again.

This application provides a multicast broadcast service receiving method to resolve a problem of correct assignment of an SN (Sequence Number, sequence number) when the multicast broadcast service is sent based on service features and received by UE and better support transmission of the multicast broadcast service. The UE can efficiently receive and process the multicast broadcast service correctly based on a transmission parameter of the multicast broadcast service configured by the network. This further improves service QoS (Quality of Service, quality of service) guarantee, that is, user experience and system efficiency.

As shown in <FIG>, an embodiment of this application further provides a communications device <NUM>, including a processor <NUM>, a memory <NUM>, and a program or instructions stored in the memory <NUM> and capable of running on the processor <NUM>. For example, when the communications device <NUM> is a terminal, and the program or instructions are executed by the processor <NUM>, each process of the foregoing multicast service receiving method embodiment is implemented, with the same technical effect achieved. When the communications device <NUM> is a network-side device, and the program or instructions are executed by the processor <NUM>, each process of the foregoing multicast service configuration method embodiment is implemented, with the same technical effect achieved. To avoid repetition, details are not described herein again.

<FIG> is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of this application. The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, and a processor <NUM>.

A person skilled in the art may understand that the terminal <NUM> may further include a power supply (for example, a battery) supplying power to all components. The power supply may be logically connected to the processor <NUM> through a power management system. In this way, functions such as charge management, discharge management, and power consumption management are implemented by using the power management system. The terminal structure shown in <FIG> does not constitute a limitation on the terminal. The terminal may include more or fewer components than those shown in the figure, or some components are combined, or component arrangements are different.

It should be understood that, in this embodiment of this application, the input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a still picture or video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. The display unit <NUM> may include a display panel <NUM>, and the display panel <NUM> may be configured in a form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit <NUM> includes a touch panel <NUM> and other input devices <NUM>. The touch panel <NUM> is also referred to as a touchscreen. The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The other input devices <NUM> may include but are not limited to a physical keyboard, a function key (such as a volume control key or a switch key), a trackball, a mouse, and a joystick.

In this embodiment of this application, after receiving downlink data from a network-side device, the radio frequency unit <NUM> sends the downlink data to the processor <NUM> for processing, and in addition, sends uplink data to the network-side device. Generally, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory <NUM> may be configured to store software programs or instructions and various data. The memory <NUM> may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store an operating system, an application program or instructions (such as an audio play function and an image play function) required by at least one function, and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may further include a non-volatile memory. The non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory, for example, at least one disk storage device, a flash memory device, or another non-volatile solid-state storage device.

The processor <NUM> may include one or more processing units. Optionally, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes the operating system, a user interface, an application program, or an instruction. The modem processor mainly processes wireless communication. For example, the modem processor is a baseband processor. It may be understood that the modem processor may alternatively not be integrated in the processor <NUM>.

The radio frequency unit <NUM> is configured to receive configuration information of a multicast broadcast service MBS service sent by a network-side device, where the configuration information of the MBS service includes information for determining whether to enable reordering for a packet data convergence protocol PDCP layer and/or a radio link control RLC layer.

The processor <NUM> is configured to receive the MBS service based on the configuration information of the MBS service.

Optionally, the processor <NUM> is further configured to: if the configuration parameter of the PDCP layer includes the reordering parameter of the PDCP layer, perform at least one of the following: determining to enable reordering for the PDCP layer; determining to enable reordering for the RLC layer; if the reordering parameter of the PDCP layer is configured, using the configured reordering parameter, or if the reordering parameter of the PDCP layer is not configured, using a default value; and using a default value for the reordering parameter of the RLC layer; or if the configuration parameter of the PDCP layer does not include the reordering parameter of the PDCP layer, perform at least one of the following: determining to disable reordering for the PDCP layer; and determining to disable reordering for the RLC layer. The configured reordering parameter of the PDCP layer includes at least one of the following: a reordering window, a reordering timer, and a sequence number SN space size.

Optionally, the processor <NUM> is further configured to: if the configuration parameter of the RLC layer includes the reordering parameter of the RLC layer, perform at least one of the following: determining to enable reordering for the PDCP layer; determining to enable reordering for the RLC layer; if the reordering parameter of the RLC layer is configured, using the configured reordering parameter, or if the reordering parameter of the RLC layer is not configured, using a default value; and using a default value for the reordering parameter of the PDCP layer; or if the configuration parameter of the RLC layer does not include the reordering parameter of the RLC layer, perform at least one of the following: determining to disable reordering for the PDCP layer; and determining to disable reordering for the RLC layer. The configured reordering parameter of the RLC layer includes at least one of the following: a reordering window, a reordering timer, and an SN space size.

Optionally, the processor <NUM> is further configured to perform one of the following:.

Optionally, the first configuration information includes the HARQ feedback configuration parameter, and the processor <NUM> is further configured to perform one of the following:.

Optionally, an SN part of an initial value of RX_NEXT is equal to the SN of the first received data packet or SN+<NUM> modulo SN space size, and a hyperframe number HFN part needs to ensure that RX_NEXT is positive;.

Optionally, the processor <NUM> is further configured to: if reordering is configured as disabled for the PDCP layer, for each received data packet, directly obtain an SDU through parsing and then deliver the SDU to a higher layer, and directly set an SN part of a variable RX_NEXT or RX_DELIV of the PDCP layer to an SN of the received data packet or SN+<NUM>, and set an HFN part to <NUM> or any other arbitrary or prescribed value that ensures that a count value is positive.

Optionally, the processor <NUM> is further configured to: if switching from an MRB to a DRB is required, receive configuration information of the MBS service of the DRB, and establish a new PDCP layer and/or RLC layer for the DRB based on the configuration information of the MBS service of the DRB; or if switching from an MRB to a DRB is required, use a PDCP layer configuration and/or an RLC configuration of the MRB for the DRB.

Optionally, the processor <NUM> is further configured to: if switching from a DRB to an MRB is required, receive configuration information of the MBS service of the MRB, and establish a new PDCP layer and/or RLC layer for the MRB based on the configuration information of the MBS service of the MRB; or if switching from a DRB to an MRB is required, use a PDCP layer configuration and/or an RLC configuration of the DRB for the MRB.

An embodiment of this application further provides a network-side device. As shown in <FIG>, the network device <NUM> includes an antenna <NUM>, a radio frequency apparatus <NUM>, and a baseband apparatus <NUM>. The antenna <NUM> is connected to the radio frequency apparatus <NUM>. In an uplink direction, the radio frequency apparatus <NUM> receives information by using the antenna <NUM>, and sends the received information to the baseband apparatus <NUM> for processing. In a downlink direction, the baseband apparatus <NUM> processes to-be-sent information, and sends the information to the radio frequency apparatus <NUM>; and the radio frequency apparatus <NUM> processes the received information and then sends the information out by using the antenna <NUM>.

The method performed by the network-side device in the foregoing embodiment may be implemented in the baseband apparatus <NUM>, and the baseband apparatus <NUM> includes a processor <NUM> and a memory <NUM>.

The baseband apparatus <NUM> may include, for example, at least one baseband processing unit, where a plurality of chips are disposed on the baseband processing unit. As shown in <FIG>, one of the chips is, for example, the processor <NUM>, connected to the memory <NUM>, to invoke a program in the memory <NUM> to perform the operation of the network device shown in the foregoing method embodiment.

The baseband apparatus <NUM> may further include a network interface <NUM>, configured to exchange information with the radio frequency apparatus <NUM>, where the interface is, for example, a common public radio interface (common public radio interface, CPRI for short).

Specifically, the network-side device in this embodiment of this application further includes a program or instructions stored in the memory <NUM> and capable of running on the processor <NUM>. When the processor <NUM> invokes the program or instructions in the memory <NUM>, the method performed by each module shown in <FIG> is performed, with the same technical effect achieved. To avoid repetition, details are not described herein again.

An embodiment of this application further provides a readable storage medium. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, each process of the foregoing multicast service receiving method embodiment is implemented, with the same technical effect achieved. To avoid repetition, details are not described herein again.

An embodiment of this application further provides a readable storage medium. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, each process of the foregoing multicast service configuration method embodiment is implemented, with the same technical effect achieved. To avoid repetition, details are not described herein again.

The processor is a processor in the terminal in the foregoing embodiment. The readable storage medium includes a computer-readable storage medium, for example, a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disc.

In addition, an embodiment of this application provides a chip. The chip includes a processor and a communications interface. The communications interface is coupled to the processor. The processor is configured to run a program or instructions on a network-side device to implement each process of the foregoing multicast service receiving method embodiment, with the same technical effect achieved. To avoid repetition, details are not described herein again.

In addition, an embodiment of this application provides a chip. The chip includes a processor and a communications interface. The communications interface is coupled to the processor. The processor is configured to run a program or instructions on a network-side device to implement each process of the foregoing multicast service configuration method embodiment, with the same technical effect achieved. To avoid repetition, details are not described herein again.

It should be understood that the chip provided in this embodiment of this application may also be referred to as a system-level chip, a system chip, a chip system, a system-on-chip, or the like.

In addition, an embodiment of this application provides a program product. The program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the foregoing multicast service receiving method embodiment, with the same technical effect achieved. To avoid repetition, details are not described herein again.

In addition, an embodiment of this application provides a program product. The program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the foregoing multicast service configuration method embodiment, with the same technical effect achieved. To avoid repetition, details are not described herein again.

It may be understood that the embodiments described in the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, a module, unit, subunit, submodule, subunit, or the like may be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processors (Digital Signal Processor, DSP), digital signal processing devices (DSP Device, DSPD), programmable logic devices (Programmable Logic Device, PLD), field-programmable gate arrays (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and other electronic units for performing the functions described in this application, or a combination thereof.

It should be noted that in this specification, the term "comprise", "include", or any of their variants are intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In absence of more constraints, an element preceded by "includes a. " does not preclude existence of other identical elements in the process, method, article, or apparatus that includes the element. In addition, it should be noted that the scope of the method and apparatus in the implementations of this application is not limited to performing the functions in an order shown or discussed, and may further include performing the functions in a substantially simultaneous manner or in a reverse order depending on the functions used. For example, the method described may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

According to the foregoing description of the implementations, a person skilled in the art may clearly understand that the methods in the foregoing embodiments may be implemented by using software in combination with a necessary general hardware platform, and certainly may alternatively be implemented by using hardware. However, in most cases, the former is a preferred implementation. Based on such an understanding, the technical solutions of this application essentially or the part contributing to the prior art may be implemented in a form of a software product. The computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the methods described in the embodiments of this application.

Claim 1:
A multicast service receiving method, performed by a terminal and comprising:
receiving (<NUM>) configuration information of a multicast broadcast service, MBS, service sent by a network-side device, wherein the configuration information of the MBS service comprises information for determining whether to enable reordering for a packet data convergence protocol, PDCP, layer and/or a radio link control, RLC, layer; and
receiving (<NUM>) the MBS service based on the configuration information of the MBS service;
wherein the information for determining whether to enable reordering for the PDCP layer and/or the RLC layer comprises:
first configuration information, used to implicitly indicate whether to enable reordering for the PDCP layer and/or the RLC layer, wherein
the first configuration information comprises at least one of the following: a hybrid automatic repeat request, HARQ, feedback configuration parameter, a quality of service, QoS, related parameter, a block error rate, and whether to enable an in-order delivery function for a service layer; and
the HARQ feedback configuration parameter comprises at least one of the following: whether the MBS service requires a HARQ feedback; and a parameter used for the HARQ feedback.