CN118020361A - Method and system for managing multicast communications in a wireless communication network - Google Patents

Abstract

The embodiment of the invention discloses a wireless communication method, which comprises the following steps: the wireless communication device determining a first timer for multicasting; the wireless communication device determining a second timer for bandwidth part BWP deactivation; the wireless communication device receives a multicast transmission from the network based on the first timer and the second timer.

Description

Method and system for managing multicast communications in a wireless communication network

Technical Field

Embodiments of the present invention relate to the field of wireless communications, and in particular, relate to systems, methods, apparatuses, and non-transitory computer readable media for managing multicast communications in a wireless communication network.

Background

The first stage standardization work of the fifth generation mobile communication technology 5G has been completed. A series of unicast functions specified in the New Radio, NR, versions (including but not limited to Rel-15 and Rel-16) are employed. However, support for broadcast/multicast functions has not been specified.

In a 5G wireless communication network, channels carrying multicast broadcast services (Multicast Broadcast Service, MBS), including a group common physical downlink control channel (Group Common Physical Downlink Control Channel, GC-PDCCH) and a group common physical downlink shared channel (Group Common Physical Downlink SHARED CHANNEL, GC-PDSCH), may be configured for transmission within a common frequency range (Common Frequency Range, CFR). In NR Rel-17, CFR is limited to the active unicast Downlink (DL) Bandwidth portion (BWP). According to a conventional rule for managing a BWP deactivation timer (e.g., BWP-inactivatytimer), a User Equipment (UE) may switch its active unicast DL BWP to a default DL BWP in response to expiration of the BWP deactivation timer, regardless of whether the UE is receiving an MBS. In some cases, the default DL BWP may not include CFR. Therefore, upon switching to the default DL BWP, the reception of the MBS may be interrupted or terminated. This will seriously affect the user experience.

Disclosure of Invention

According to an embodiment of the present invention, there is provided a wireless communication method including: the wireless communication device determining a first timer for multicasting; the wireless communication device determining a second timer for bandwidth part BWP deactivation; the wireless communication device receives a multicast transmission from the network based on the first timer and the second timer.

According to another embodiment of the present invention, there is provided a wireless communication method including: the network configures a first timer for multicasting for the wireless communication device; the network configures the wireless communication device with a second timer for bandwidth part BWP deactivation; the network sends a multicast transmission to the wireless communication device based on the first timer and the second timer.

According to yet another embodiment of the present invention, there is provided a wireless communication device including at least one processor and a memory, wherein the at least one processor is configured to read code from the memory and implement the steps of embodiments of the present invention.

According to yet another embodiment of the present invention, a computer program product is provided, comprising a computer readable program medium code stored thereon, which code, when executed by at least one processor, causes the at least one processor to implement the steps in embodiments of the present invention.

The above and other aspects and implementations thereof are described in more detail in the accompanying drawings, description and claims.

Drawings

These and other aspects and features of embodiments of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific implementations in conjunction with the accompanying figures, wherein:

FIG. 1A is a schematic illustration of SPS PDSCH selection in accordance with an embodiment of the invention;

Fig. 1B is a schematic diagram of a wireless communication network according to an embodiment of the present invention;

Fig. 1C is a block diagram of a wireless communication system for transmitting and receiving downlink and uplink communication signals according to an embodiment of the present invention;

Fig. 2 is a diagram of activating BWP and CFR according to an embodiment of the present invention;

fig. 3 is a flow chart of a method for managing multicast communications according to an embodiment of the present invention;

Fig. 4 is a flow chart of a method for managing multicast communications according to an embodiment of the present invention;

fig. 5 is a flow chart of a method for managing multicast communications in accordance with yet another embodiment of the present invention;

fig. 6 is a flow chart of a method for managing multicast communications in accordance with yet another embodiment of the present invention;

Fig. 7 is a flow chart of a method for managing multicast communications in accordance with another embodiment of the present invention;

Fig. 8 is a diagram of a DCI format for a paging PDCCH according to an embodiment of the present invention;

Fig. 9 is a mapping table between bit fields and indications of short message indicators in a paging PDCCH according to an embodiment of the present invention;

Fig. 10 is a diagram illustrating mapping between bits of a short message and the short message in a paging PDCCH according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of an active BWP, a default BWP, and a CFR according to an embodiment of the present invention;

fig. 12 is a schematic diagram of an activated BWP, a default BWP, and a CFR according to still another embodiment of the present invention.

Detailed Description

Embodiments of the present invention will now be described in detail with reference to the drawings, which are provided as illustrative examples of embodiments to enable those skilled in the art to practice the implementations and alternatives as will be apparent to those of skill in the art. It is noted that the figures and examples below are not meant to limit the scope of embodiments of the invention to a single implementation, but other implementations are possible by exchanging some or all of the elements described or shown. Furthermore, where certain elements of embodiments of the present invention can be partially or fully implemented using known components, only those portions of such known components that are necessary for an understanding of the embodiments of the present invention will be described, and detailed descriptions of other portions of such known components will be omitted so as not to obscure the embodiments of the present invention. Implementations described as being implemented in software should not be limited thereto but may include embodiments implemented in hardware or a combination of software and hardware and vice versa, as would be apparent to one skilled in the art unless the embodiments of the invention are otherwise specified. In this specification, the implementation of showing individual components should not be considered limiting. Conversely, embodiments of the invention are intended to encompass other implementations that include multiple identical components, and vice versa, unless explicitly stated otherwise. Furthermore, applicants do not impart unusual or special meaning to any term in the specification or claims unless so expressly specified. Furthermore, embodiments of the invention include current and future known equivalents to the known components referred to by way of example.

In current NR systems, uplink (UL) and DL transmissions are based on active unicast UL BWP and active unicast DL BWP, respectively. The UE is configured with one or more BWP by the network (e.g., base station) according to a predefined maximum BWP number (e.g., 4) per cell. In NR Rel-15 and Rel-16, only one configured BWP can be activated at a time to transmit data or information. Thus, having the UE operate on a portion of the bandwidth rather than the entire carrier may save energy. The network (e.g., base station) may configure a BWP deactivation timer (e.g., BWP-inactivatytimer) for the UE. Currently, upon receiving a downlink control information (Downlink Control Information, DCI) format scrambled by a radio network temporary identity (Radio Network Temporary Identifier, RNTI), e.g., cell-RNTI (C-RNTI) or configuration scheduling RNTI (CS-RNTI), a cyclic redundancy check (Cyclic Redundancy Check, CRC), the BWP deactivation timer is reset. In response to determining that the BWP-inactivatetimer expires, the UE may switch the active unicast DL BWP to a default DL BWP.

In NR Rel-17, with respect to MBS, a network node (e.g., a base station) may use the same transmission mechanism to transmit the same information to a group of UEs or all UEs in a cell. MBS transmissions may be made on PDSCH received by the group of UEs or all UEs. Such a PDSCH carrying MBS information may be referred to as GC-PDSCH or MBS PDSCH. Different UEs may encounter a variety of different network environments (e.g., channel conditions). To improve the efficiency of MBS transmissions, UEs with similar network environments are expected to fall into the same UE group. Thus, in some implementations, the selected transmission mechanism may better match the network environment of each UE in the group of UEs.

According to the case where a group of UEs receives the same PDSCH to acquire MBS information, different implementations may be employed to schedule PDSCH for the group of UEs. One example includes dynamically scheduling GC-PDSCH using GC-PDCCH, which can be scheduled by all UEs in the group that can detect the same PDCCH. The CRC of DCI carried on the GC-PDCCH is scrambled using a group RNTI (G-RNTI).

In some embodiments, discontinuous reception (Discontinuous Reception, DRX) operation is applicable to GC-PDCCH monitoring. The DRX pattern of the G-RNTI may be configured (including at least one of a period, an offset, a DRX-onDurationTimer, DRX-InactigitTimer, etc.) by radio resource control (Radio Resource Control, RRC) signaling. The UE may determine DRX on and off periods according to the configuration parameters. The DRX patterns of different G-RNTIs may be the same or different. More specifically, the GC-PDCCH carrying the DCI format with the CRC scrambled by the G-RNTI can be monitored only during the DRX on period corresponding to the G-RNTI. For legacy unicast reception, the UE-specific DRX mode may be determined from the C-RNTI. The UE may then be configured to determine whether to use Point-to-Point (PTP) retransmissions for multicast broadcast service transport blocks (Multicast Broadcast SERVICE TEST bid, MBS TB). In other words, the UE may be configured to whether to use unicast PDCCH (or UE-specific PDCCH) for retransmission scheduling of MBS TBs. The configuration signaling may be RRC signaling, MAC layer signaling, or DCI. The UE may also monitor a DCI format of CRC scrambled by the C-RNTI during a DRX on period corresponding to the G-RNTI if PTP retransmission of the MBS TB is enabled.

Another embodiment is to use SPS-based GC-PDSCH transmission or SPS-based MBS transmission. The GC-PDSCH is transmitted according to SPS configuration and activation commands. That is, the SPS configuration is transmitted through RRC signaling including at least one of a period, the number of HARQ processes, PUCCH resources corresponding to the SPS PDSCH, HARQ ID offset, PDSCH aggregation factor, SPS index, and the like. Further, SPS may be further activated or deactivated by DCI, indicating more configurations of SPS PDSCH. After the DCI activates SPS, a plurality of periodic SPS PDSCH will be used to transmit data from the network to the UE. The activated or deactivated DCI may activate PDCCH or UE-specific activated PDCCH transmission through GC. The GC activates CRC scrambling of DCI carried on the PDCCH using G-CS-RNTI. The CRC of DCI carried on the UE-specific activation PDCCH is scrambled using CS-RNTI.

In some embodiments, the UE may be configured with multiple SPS configurations. Some of which are configured for unicast services. Some SPS configurations are used for MBS. Each SPS configuration is identified by (or associated with) an SPS index. The UE may receive at most N PDSCH in one slot, wherein at most M PDSCH may overlap in the time domain according to the capability of the UE. If there are a plurality of SPS PDSCH in one slot, the UE receives SPS PDSCH according to the following rule: starting from the SPS PDSCH with the smallest (or largest) SPS index. The UE determines whether the SPS PDSCH is a reserved PDSCH one by one in ascending (or descending) order of SPS indices until the number of reserved PDSCH is equal to the maximum number of PDSCH that the UE can receive in the slot or no SPS PDSCH in the slot needs to be determined. If the number of SPS PDSCH overlapping in the time domain is not greater than M in consideration of SPS PDSCH (assuming that the SPS PDSCH to be determined is a reserved PDSCH), the SPS PDSCH is determined as a reserved PDSCH. The UE receives only the selected persistent PDSCH.

Alternatively, SPS PDSCH received by the UE in a slot in which all SPS PDSCH to be determined is considered a candidate PDSCH set may be selected. Step 1: SPS PDSCH with the lowest (or largest) SPS index in the candidate set is selected, and the selected PDSCH will be excluded from the candidate set. Considering the selected SPS PDSCH (assuming that the selected SPS PDSCH is a reserved PDSCH), if the number of reserved PDSCH overlapping in the time domain is not greater than M, the selected PDSCH is determined as a reserved PDSCH. Otherwise, it cannot be determined to leave the PDSCH. Step 2: stopping if (1) the number of remaining PDSCH is equal to N, or (2) there are no SPS PDSCH remaining in the candidate set; otherwise (number of remaining PDSCH is less than N and there are remaining PDSCH in the candidate set), jump to step 1.

In some embodiments, if the SPS PDSCH overlaps with any uplink symbols indicated by RRC signaling, the SPS PDSCH is discarded first, which would result in the SPS PDSCH not being included in the candidate set. If there is a PDSCH scheduled by DCI in a slot, the UE receives the PDSCH, which should be considered when selecting the SPS PDSCH. This results in the condition in step 2 becoming "the total number of PDSCH retaining PDSCH and downlink control information scheduling is equal to N" and "the total number of PDSCH retaining PDSCH and downlink control information scheduling is less than N", respectively.

It should be understood that two PDSCH overlapping in the time domain refers to only two PDSCH overlapping in the time domain, and does not include two PDSCH overlapping in the frequency domain.

Fig. 1A is a schematic diagram of SPS PDSCH selection according to an embodiment of the invention. In one slot, there are six SPS PDSCH, which are represented by PDSCH 0 with SPS index 0, PDSCH 1 with SPS index 1, PDSCH 2 with SPS index 2, PDSCH 3 with SPS index 3, PDSCH 4 with SPS index 4, and PDSCH 5 with SPS index 6, respectively. The UE can receive a maximum of 4 PDSCH (i.e., n=4) in a slot, where a maximum of 2 PDSCH (i.e., m=2) overlap in the time domain.

First, the PDSCH is not reserved. Since the index is the lowest (i.e., SPS 0), the first PDSCH to be determined is PDSCH 0. In consideration of PDSCH 0, there is no PDSCH overlapping with other PDSCH in the slot. The maximum number of overlapping PDSCH in the time domain is 1, less than M. Thus, PDSCH 0 is determined to retain PDSCH. The persistent PDSCH includes PDSCH 0. The number of remaining PDSCH in the slot is 1, less than N, and SPS PDSCH is also in the slot. Thus, the SPS PDSCH continues to be selected.

The next PDSCH to be determined is PDSCH 1. Considering that PDSCH 1 overlaps PDSCH 0 in the time domain, the maximum number of overlapping PDSCH in the time domain is 2, not greater than M. Thus, PDSCH 1 is determined to retain PDSCH. The persistent PDSCH includes PDSCH 0 and PDSCH 1. The number of remaining PDSCH in the slot is 2, less than N, and SPS PDSCH in the slot. Thus, the SPS PDSCH continues to be selected.

The next PDSCH to be determined is PDSCH 2. Consider that PDSCH 2, PDSCH 1, and PDSCH 0 overlap each other. The maximum number of overlapping PDSCH in the time domain is 3, greater than M. Therefore, PDSCH 2 is not determined to be reserved. The persistent PDSCH includes PDSCH 0 and PDSCH 1. The number of remaining PDSCH in the slot is 2, less than N, and SPS PDSCH in the slot. Thus, the SPS PDSCH continues to be selected.

The next PDSCH to be determined is PDSCH 3. It is considered that PDSCH 3 overlaps PDSCH 0 only in the time domain. The maximum number of overlapping PDSCH in the time domain is 2, not greater than M. Thus, PDSCH 3 is determined to retain PDSCH. The persistent PDSCH includes PDSCH 0, PDSCH 1, and PDSCH 3. The number of remaining PDSCH in the slot is 3, less than N, and SPS PDSCH in the slot. Thus, the SPS PDSCH continues to be selected.

The next PDSCH to be determined is PDSCH 4. It is considered that PDSCH 4 overlaps PDSCH 3 only in the time domain. The maximum number of overlapping PDSCH in the time domain is 2, not greater than M. Thus, PDSCH 4 is determined to retain PDSCH. The reserved PDSCH includes PDSCH 0, PDSCH 1, PDSCH 3, and PDSCH 4. The number of remaining PDSCH in this slot is 4, equal to N. Therefore, the SPS PDSCH is stopped from being selected, and the remaining PDSCH includes PDSCH 0, PDSCH 1, PDSCH 3, and PDSCH 4. The UE receives PDSCH 0, PDSCH 1, PDSCH 3, and PDSCH 4 in slots.

The UE may receive N PDSCH at most in a slot, wherein, based on UE capability, O PDSCH at most for MBS may overlap in the time domain, P PDSCH at most for unicast service may overlap in the time domain, and Q PDSCH at most for unicast service and MBS may overlap in the time domain. If there are a plurality of SPS PDSCH for MBS or unicast service in one slot, the UE receives the SPS PDSCH according to the following rule. The UE determines whether the SPS PDSCH is a reserved PDSCH one by one in ascending (or descending) order of the SPS index starting from the SPS PDSCH with the smallest (or largest) SPS index until the number of reserved PDSCH is equal to the maximum number of PDSCH receivable by the UE in the slot or there are no remaining SPS PDSCH in the slot. If the number of overlapped PDSCHs of the MBS is not more than O, the number of overlapped PDSCHs in the time domain of the unicast service is not more than P, and the number of overlapped PDSCHs in the time domain of the MBS and the unicast service is not more than Q in consideration of the SPS PDSCH (assuming that the SPS PDSCH to be determined is the reserved PDSCH), the SPS PDSCH is determined as the reserved PDSCH.

Alternatively, the SPS PDSCH received by the UE in the slot may be selected by the following method. All SPS PDSCH to be determined in the slot are considered as candidate PDSCH sets.

Step 1: SPS PDSCH with the lowest (or largest) SPS index in the candidate set is selected. The selected PDSCH will be excluded from the candidate set. Considering the selected SPS PDSCH (assuming that the selected SPS PDSCH is a reserved PDSCH), if the number of overlapping PDSCH of MBS is not greater than O, the number of overlapping PDSCH in the time domain of unicast service is not greater than P, and the number of overlapping PDSCH in the time domain of MBS and unicast service is not greater than Q, the selected PDSCH is determined as the reserved PDSCH. Otherwise, it cannot be determined to leave the PDSCH.

Step 2: stopping if (1) the number of remaining PDSCH is equal to N or (2) there are no SPS PDSCH remaining in the candidate set; otherwise (e.g., the number of remaining PDSCH is less than N and there are remaining PDSCH in the candidate set), then step 1 is skipped.

Still referring to fig. 1A, according to UE capability, the UE may receive at most 3 PDSCH in one slot (i.e., n=3), at most 2 PDSCH for MBS overlap in the time domain (i.e., o=2), at most 2 PDSCH for MBS and unicast service overlap in the time domain (i.e., q=2), and PDSCH not supporting unicast service overlap (i.e., p=1). SPS1, SPS 3, and SPS 6 are used to transmit MBS, SPS 0, SPS2, and SPS 4 are used to transmit unicast services.

Starting from SPS 0, the first SPS PDSCH to be determined is PDSCH 0.PDSCH 0 is determined to be the persistent PDSCH. The persistent PDSCH includes PDSCH 0. The number of reserved PDSCH is 1, and SPS PDSCH remains in the slot. Thus, the SPS PDSCH continues to be selected.

The next SPS PDSCH to be determined is PDSCH 1, and the number of PDSCHs where mbs and unicast services overlap in the time domain (i.e., PDSCH 0 and PDSCH 1) is 2, which is equal to Q. MBS has only 1 PDSCH (e.g., PDSCH 1). The number of SPS PDSCH overlapping in the time domain of MBS is 1, less than O. Unicast service has only 1 PDSCH (e.g., PDSCH 0). The number of SPS PDSCH overlapping in the time domain of unicast service is 1, which is not greater than P. Thus, PDSCH 1 is determined to retain PDSCH. The persistent PDSCH includes PDSCH 0 and PDSCH 1. The number of reserved PDSCH is 2 and less than N, and SPS PDSCH remains in the slot. Thus, the SPS PDSCH continues to be selected.

The next SPS PDSCH to be determined is PDSCH 2, and the number of overlapping PDSCH of the unicast service in the time domain (e.g., PDSCH 0 overlapping PDSCH 2) is 2, which is greater than P. Thus, PDSCH 2 cannot be determined to retain PDSCH. The number of reserved PDSCH is 2, less than N, and SPS PDSCH remains in the slot. Thus, the SPS PDSCH continues to be selected.

The next SPS PDSCH to be determined is PDSCH 3, and the number of PDSCH overlapping in time domain (i.e., PDSCH 0 overlapping PDSCH 1, PDSCH 0 overlapping PDSCH 3) of mbs and unicast service is 2, not greater than Q. MBS has only 2 PDSCH (e.g., PDSCH 1 and PDSCH 3), but does not overlap in the time domain. It can be seen that the number of SPS PDSCH overlapping in the time domain by MBS is 1, which is less than O. Unicast service has only 1 PDSCH (e.g., PDSCH 0). The number of SPS PDSCH overlapping in the time domain of unicast service is 1, which is not greater than P. Thus, PDSCH 3 is determined to retain PDSCH. The persistent PDSCH includes PDSCH 0, PDSCH 1, and PDSCH 3. The number of reserved PDSCH is 3 and equal to N. Thus, the SPS PDSCH is stopped from being selected. In this slot, the reserved PDSCH includes PDSCH 0, PDSCH 1, and PDSCH 3. The UE receives only these three PDSCH but does not receive other PDSCH (e.g., PDSCH 2, 4, 5).

After selecting the SPS PDSCH, the UE may not receive one or more SPS PDSCH. If the UE does not receive the SPS PDSCH for the MBS, the UE will generate a NACK or ACK for the SPS PDSCH for the MBS. Whether to generate a NACK or ACK for SPS PDSCH not received by the UE is configured by the network. For example, the UE does not receive PDSCH 5 carrying MBS data, and if the network configures the UE to generate a NACK for the SPS PDSCH of the MBS that the UE did not receive, a NACK is generated for PDSCH 5. If the network configures the UE to generate an ACK for SPS PDSCH of MBS that the UE did not receive, an ACK is generated for PDSCH 5.

In some arrangements, the SPS configuration includes a first SPS index and a second SPS index. The first SPS index and the second SPS index are both configured by the network. The first SPS index is used to identify SPS configurations when the GC PDCCH activates or deactivates SPS configurations. In other words, the GC PDCCH or GC MAC CE that activates or deactivates SPS represents the first SPS index that activates or deactivates SPS configuration. The second SPS index is used to identify SPS configurations when the UE-specific PDCCH or UE-specific MAC CE activates or deactivates SPS configurations. In other words, the UE-specific PDCCH or UE-specific MAC CE, when activating or deactivating SPS, indicates the second SPS index of the SPS configuration to be activated or deactivated.

For example, the network configures the first SPS index and the second SPS index of SPS a as 1 and 3, respectively. The first SPS index and the second SPS index of SPS B are 3 and 1, respectively. When the GC PDCCH or group common MAC CE activates or deactivates the SPS configuration with SPS index 1, SPS a is activated or deactivated accordingly. When the GC PDCCH or group common MAC CE activates or deactivates the SPS configuration with SPS index 3, SPS B is activated or deactivated accordingly. When the UE-specific PDCCH or UE-specific MAC CE activates or deactivates SPS with SPS index 1, SPS B is activated or deactivated accordingly. When the UE-specific PDCCH or UE-specific MAC CE activates or deactivates SPS with SPS index 3, SPS a is activated or deactivated accordingly.

When the SPS PDSCH is selected, the SPS index may be the first SPS index or the second SPS index.

In some arrangements, the network may configure a priority index for SPS configuration. The priority index is used to select the SPS PDSCH in the slot according to the method described above. In this case, the UE receives the SPS PDSCH according to the following rule. Starting from the SPS PDSCH with the lowest (or largest) priority index, the UE determines whether the SPS PDSCH is a reserved PDSCH one by one in the ascending (or descending) order of the priority index until the number of reserved PDSCH is equal to the maximum number of PDSCH receivable by the UE in the slot or there are no remaining SPS PDSCH in the slot.

The frequency range of MBS transmissions may also be referred to as CFR. In some embodiments, CFR may be defined as MBS-specific frequency regions within the BWP of MBS transmission or unicast DL BWP.

In the embodiment of the present invention, the size of DCI carried on the GC-PDCCH should be consistent with the size of DCI format 1_0 monitored in the Common Search Space (CSS). If the cell is configured with CORESET #0, the size of the frequency domain resource allocation (Frequency Domain Resource Allocation, FDRA) field of DCI format 1_0 monitored in CSS is determined according to the bandwidth of control resource SET (core) # 0. Otherwise, if the cell is not configured CORESET #0, the FDRA field size in DCI format 1_0 monitored in the CSS is determined according to the bandwidth of the initial DL BWP. The size of FDRA field in DCI carried on GC-PDCCH may be determined according to the bandwidth of CFR. Then, if the bandwidth (N _CFR) of CFR is greater than the bandwidth (M) of CORESET #0 (if CORESET #0 is configured for the cell) or the bandwidth of initial DL BWP (if CORESET #0 is not configured for the cell), the granularity of frequency domain resource allocation will be K, which is the maximum value in the set {1,2,4,8}, and the following condition is satisfied:

Otherwise, k=1. The value of P is equal to 2 ⁿ, n is the number of reserved bits in the DCI format, or n is configured by signaling (e.g., DCI, MAC layer signaling or RRC signaling). In the embodiment of the present invention, the value of P is configured through signaling (e.g., DCI, MAC layer signaling, or RRC signaling). In an embodiment of the invention, the value of P is determined according to some predefined rule.

Fig. 1B illustrates a wireless communication network 100. The wireless communication network 100 corresponds to group communication in a cellular network. In the wireless communication network 100, a network-side communication node or Base Station (BS) may include one or more of a next generation node B (gNB), an E-u tran node B (also referred to as an evolved node B, eNodeB or eNB), a micro Base Station, a femto Station, a transmission/reception Point (Total Rating Point, TRP), an Access Point (AP), or the like. The terminal-side node or UE may include a long-range communication system (e.g., without limitation, a mobile device, a smart phone, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a tablet, a notebook) or a short-range communication system (e.g., without limitation, a wearable device, a vehicle with an in-vehicle communication system, or the like). As shown in fig. 1B, the network-side communication node is represented by BS102, and the terminal-side communication node is represented by UE 104a or 104B. In some embodiments, the BS102 is sometimes referred to as a "wireless communication node" and the UEs 104a/104b are sometimes referred to as "wireless communication devices".

As shown in fig. 1B, BS102 may provide wireless communication services to UEs 104a and 104B within cell 101. UE 104a may communicate with BS102 via communication channel 103 a. Also, the UE 104b may communicate with the BS102 via a communication channel 103 b. The communication channels (e.g., 103a and 103 b) may be over an interface including, but not limited to, a Uu interface, also known as a universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS) air interface. BS102 is connected to Core Network (CN) 108 through external interface 107 (e.g., iu interface).

Fig. 1C illustrates a block diagram of a wireless communication system 150 for transmitting and receiving downstream and upstream communication signals in accordance with an embodiment of the present invention. Referring to fig. 1B and 1C, in a system 150, data symbols may be transmitted and received in a wireless communication environment, such as the wireless communication network 100 of fig. 1B.

The system 150 generally includes the BS102 and UEs 104a and 104b. BS102 includes BS transceiver module 110, BS antenna 112, BS memory module 116, BS processor module 114, and network communication module 118. These modules/components are interconnected as desired by a data communication bus 120. UE 104a includes a UE transceiver module 130a, a UE antenna 132a, a UE memory module 134a, and a UE processor module 136a. These modules/components are interconnected as needed by a data communication bus 140 a. Similarly, UE 104b includes a UE transceiver module 130b, a UE antenna 132b, a UE memory module 134b, and a UE processor module 136b. These modules/components are interconnected as needed by a data communication bus 140 b. BS102 communicates with UEs 104a and 104b via communication channel 155, which may be any wireless channel, or other medium known in the art suitable for data transmission in accordance with embodiments of the present invention.

The system 150 may include any number of modules/elements in addition to those shown in fig. 1C. The various illustrative blocks, modules, elements, circuits, and processing logic associated with the arrangements disclosed herein may be implemented in hardware, computer readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software depends upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described by the embodiments of the invention may implement these functions in an appropriate manner for each particular application, but these implementation decisions should not be interpreted as limiting the scope of the present invention.

The wireless transmission from the antenna of each UE 104a and 104b to the antenna of BS102 is referred to as an uplink transmission, and the wireless transmission from the antenna of BS102 to the antenna of each UE 104a and 104b is referred to as a downlink transmission. According to an embodiment of the present invention, both UE transceiver modules 130a and 130b may be referred to as uplink transceivers or UE transceivers. The upstream transceiver may include transmitter circuitry and receiver circuitry that are each coupled to antennas 132a and 132 b. The duplex switch may couple the uplink transmitter or receiver with the uplink antenna in a time duplex manner. Likewise, BS transceiver module 110 may be referred to herein as a downlink transceiver or BS transceiver. The downstream transceiver may include RF transmitter circuitry and receiver circuitry, each coupled to an antenna 112. The downstream duplex switch may also couple a downstream transmitter or receiver with antenna 112 in a time duplex manner. Operation of transceivers 110, 130a, and 130b are coordinated in time such that the upstream receiver is coupled to antennas 132a and 132b to receive transmissions on wireless communication channel 155 while the downstream transmitter is coupled to antenna 112. In an exemplary embodiment, UEs 104a and 104b may use UE transceivers 130a and 130b through respective antennas 132a and 132b to communicate with BS102 over wireless communication channel 155. The wireless communication channel 155 may be any wireless channel or other medium suitable for transmitting data in the downlink DL and/or uplink UL, as described in embodiments of the present invention.

The UE transceivers 130a/130b and BS transceiver 110 are configured to communicate over a wireless data communication channel 155 and cooperate with a suitably configured antenna arrangement that may support a particular wireless communication protocol and modulation scheme. In some arrangements, the UE transceivers 130a/130b and BS transceiver 110 are configured to support industry standards, such as long term evolution (Long Term Evolution, LTE) and emerging 5G standards or similar. However, it should be understood that the application of the present disclosure is not necessarily limited to a particular standard and related protocol. In contrast, the UE transceiver 130a/130b and the BS transceiver 110 may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

The processor modules 136a and 136b, and 114, respectively, may be implemented or realized by general purpose processors, content addressable memories, digital signal processors, application specific integrated circuits, field programmable gate arrays, any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In this manner, a processor may be implemented as a microprocessor, controller, microcontroller, state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the methods or algorithms associated with the present disclosure may be embodied directly in hardware, in firmware, in software modules executed by the processor modules 114, 136a, and 136b, respectively, or in any practical combination thereof. The Memory modules 116, 134a, 134b may be implemented as random access Memory (Random Access Memory, RAM), flash Memory, read-Only Memory (ROM), erasable programmable Read-Only Memory (EPROM), electrically erasable programmable Read-Only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory, EEPROM), registers, hard disk, a removable disk, a CD-ROM, or other suitable form of storage medium. In this regard, the memory modules 116, 134a, and 134b may be coupled to the processor modules 114, 136a, and 136b, respectively, such that the processor modules 114, 136a, and 136b may read information from the memory modules 116, 134a, and 134b, respectively, and write information to the memory modules 116, 134a, and 134b, respectively. The memory modules 116, 134a, and 134b may also be integrated into their respective processor modules 114, 136a, and 136 b. In some arrangements, the memory modules 116, 134a, and 134b may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions by the processor modules 114, 136a, and 136b, respectively. Memory modules 116, 134a, and 134b may also each include non-volatile memory for storing instructions to be executed by processor modules 114, 136a, and 136b, respectively.

Network interface 118 generally represents the hardware, software, firmware, processing logic, and/or other components of BS102 that may enable bi-directional communication between BS transceiver 110 and other network components and communication nodes configured to communicate with BS 102. For example, the network interface 118 may be configured to support Internet or WiMAX traffic. In a typical deployment, the network interface 118 provides an 802.3 Ethernet interface to allow the BS transceiver 110 to communicate with a conventional Ethernet-based computer network, but is not limited thereto. In this manner, the network interface 118 may comprise a physical interface for connecting to a computer network (e.g., mobile switching center (Mobile SWITCHING CENTER, MSC)). The term "configured to" or "configured to" as used herein in connection with a specified operation or function refers to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function. Network interface 118 may enable BS102 to communicate with other BSs or core networks via wired or wireless connections.

BS102 may communicate with multiple UEs (including UEs 104a and 104 b) using multicast or broadcast (collectively referred to as MBS). Multiple UEs may each receive MBS channels (e.g., MBS PDSCH, MBS PDCCH, etc.) via multicast and/or broadcast. To receive the MBS channel, multiple UEs have a common understanding of the configuration of the MBS channel, including but not limited to the frequency resource range of the resource allocation, the scrambling code Identifier (ID), etc. The embodiment of the invention discloses an implementation method for improving the reliability of receiving MBS by UE.

In some embodiments, receiving a DCI format with a G-RNTI scrambling a CRC can reset the BWP deactivation timer. Since the UE will continue to monitor PDCCH to detect unicast DCI formats from the set of search spaces configured for unicast DL traffic, this mechanism partially violates the original intention of setting default DL BWP and results in unnecessary power consumption.

As shown in fig. 2, in some implementations of wireless communication network 100 and wireless communication system 150, for multicast of Radio Resource Control (RRC) -CONNECTED UEs, CFR 220 for GC PDCCH and/or GC-PDSCH is limited to frequency resources of dedicated unicast BWP (also referred to as active BWP 210) to support simultaneous reception of unicast and multicast in the same time slot. There are two options for the CFR 220 of the GC-PDCCH and/or GC-PDSCH.

As used in the embodiments of the present invention, BWP refers to a portion of continuous frequency resources in a cell. In other words, BWP is a continuous frequency range available for communication between the BS and the UE. Some transmission parameters and channel configurations are BWP specific. Different UEs may have different BWP configurations. In one embodiment, only one of the BWPs can be activated at most, but four BWPs can be configured at most by one UE due to insufficient time. In other words, for a UE, a given serving cell can only activate at most one active DL BWP and one active UL BWP in a given time.

In a first option, CFR is defined as MBS-specific BWP, which is associated with dedicated unicast BWP and uses the same system parameters (e.g., subcarrier spacing (Subcarrier Spacing, SCS) and Cyclic Prefix (CP)). Thus, for a UE that only supports activation of one BWP at a time, it is necessary to switch BWP between multicast reception of MBS-specific BWP and unicast reception of related dedicated BWP. Whereas for UEs capable of activating two BWP simultaneously, no BWP switch between multicast reception of MBS-specific BWP and unicast reception of its associated dedicated unicast BWP is required.

In a second option, the CFR is defined as an "MBS frequency region" having a plurality of consecutive physical resource blocks (Physical Resource Blocks, PRBs) configured in a dedicated unicast BWP. The starting PRB and PRB length of the MBS frequency region are represented using appropriate mechanisms. In a second option, an MBS frequency region (e.g., MBS BWP) is used for MBS transmission, which is associated with unicast BWP. MBS BWP and unicast BWP can be used for both MBS PDSCH and unicast PDSCH transmissions (two BWP needs to be activated simultaneously) without BWP handover. The embodiments of the present invention disclosed herein relate to both options.

Various implementations disclosed in embodiments of the present invention define mechanisms for one or more timers used in MBS-related operations. More specifically, UE behavior is defined when the MBS timer expires and when the MBS timer wakes up after expiration to perform MBS-related operations. The embodiment of the invention also discloses the condition of MBS timer verification. The embodiment of the invention improves the stability of MBS related operation, and the monitoring of the GC-PDCCH on the power supply of the UE can be reversed, thereby improving the experience of the UE.

Fig. 3 is a flow chart of a method 300 for managing multicast communications according to an embodiment of the present invention. Referring to fig. 1A-3, the method 300 may be performed by the BS102 and a UE (e.g., UE 104 a).

At 310, the UE 104a determines a first timer for multicast. In some embodiments, the first timer is a timer for MBS-related operations. The timer for MBS-related operations is a dedicated timer defined for MBS-related operations or CFRs (e.g., CFR 220). Such a dedicated timer may be referred to as a first timer, an MBS-related operation timer, an MBS timer, a CFR timer, or a GC-PDCCH monitoring timer.

In some embodiments, at 305, the network (e.g., BS 102) configures a first timer for the UE 104a for multicasting. In these embodiments, the network (e.g., BS 102) communicates the first timer or parameters thereof to the UE 104a via appropriate signaling or indication. The UE 104a receives a first timer or a parameter thereof as part of the determination at 310. In other embodiments, the network (e.g., BS 102) does not configure the first timer for the UE 104a, but rather the UE 104a determines the first timer at 310 based on other suitable mechanisms.

At 320, UE 104a determines a second timer for BWP deactivation. For example, the second timer may be referred to as a BWP deactivation timer or BWP-INACTIVITYTIMER. In some examples, the network (e.g., BS 102) configures a second timer for BWP deactivation for UE 104a at 315. In these examples, the network (e.g., BS 102) communicates the second timer or parameters thereof to UE 104a via appropriate signaling or indication. The UE 104a receives a second timer or a parameter thereof as part of the determination at 320. In other examples, the network (e.g., BS 102) does not configure the second timer for UE 104a, but rather UE 104a determines the second timer at 320 according to other suitable mechanisms.

At 325, the network (e.g., BS 102) sends a multicast transmission based on the first timer and the second timer. At 330, the UE 104a receives the multicast transmission based on the first timer and the second timer.

Fig. 4 is a flow chart of a method 400 for managing multicast communications according to an embodiment of the present invention. Referring to fig. 1A-4, the method 400 may be performed by the BS102 and a UE (e.g., UE 104 a). In certain embodiments, block 330 comprises at least one of blocks 410, 420, 430, 440, 450, and 460, and block 325 comprises at least one of blocks 425, 435, 452, and 454.

At 410, the UE determines that a first timer expires (e.g., no longer running, has expired, etc.), and a second timer is running (e.g., still running, has not expired, etc.). That is, the MBS timer (first timer) is configured by the network 102 to the UE 104a for receiving MBS and has expired, but the BWP deactivation timer has not yet expired. In response to 410, ue 104a may perform one or more of 420, 430, 440, 450, or 460.

In some embodiments, the UE 104a stops MBS-related operations in response to 410. For example, the UE stops monitoring DCI formats of CRC scrambled by G-RNTI, stops monitoring DCI formats of CRC scrambled by group common configuration scheduling RNTI (e.g., G-CS-RNTI), stops receiving SPS PDSCH scrambled by group common configuration scheduling RNTI (which may be the same or different from G-CS-RNTI), stops receiving all transmissions related to MBS, stops related operations according to CFR configuration, and so on. The network (e.g., BS 102) may send MBS to other UEs within the group. At 420, the UE stops receiving DCI scrambling the CRC by the RNTI for the multicast.

At 425, BS102 continues to send SPS downlink transmissions for multicasting to UE 104 a. At 430, the UE continues to receive SPS downlink transmissions (e.g., PDSCH) for the multicast. BS102 then transmits a UE-specific downlink control channel (e.g., PDCCH carrying DCI format of CRC scrambled by C-RNTI or CS-RNTI) to UE 104a to activate or deactivate SPS transmissions of MBS.

At 440, the UE receives signaling corresponding to activating, deactivating, or modifying transmission parameters for SPS downlink transmission. At 435, BS102 transmits signaling corresponding to activating, deactivating, or modifying transmission parameters for SPS downlink transmission. For example, the signaling includes media access layer (MEDIA ACCESS LAYER, MAC) signaling (e.g., MAC Control Element (CE)). For example, MAC layer signaling may be carried on one of the SPS PDSCH, with the activation, deactivation, and/or modification commands being effective at the next SPS PDSCH or at a specified point in time (e.g., a time offset after the PDSCH carrying the MAC layer signaling).

In some embodiments, the UE 104a continues to provide feedback (e.g., hybrid automatic repeat request acknowledgement (Hybrid Automatic Repeat Request Acknowledgement, HARQ-ACK)) for MBS Transport Blocks (TBs) carried on the SPS PDSCH. For example, at 450, the UE 104a sends feedback to the BS102 for the multicast SPS downlink transmission, and the BS102 receives the same feedback at 452. In this regard, at 454, in response to receiving the feedback at 452, BS102 sends at least one retransmission of the SPS downlink transmission for the multicast, and UE 104a receives the same retransmission at 460.

For example, the UE may provide a feedback ACK or negative acknowledgement (Negative Acknowledgement, NACK) in the UE-specific resources according to the reception of the MBS TBs. In response to determining that the UE fails to receive MBS TBs on the SPS PDSCH occasion, the UE 104a sends NACK feedback to the BS 102. In response to receiving the NACK feedback, BS102 may retransmit the MBS TBs in a dynamic scheduling mode. That is, retransmission of MBS TB is scheduled by a UE-specific PDCCH carrying a DCI format with a CRC scrambled by a C-RNTI or CS-RNTI. In other words, in response to sending feedback with NACK for the SPS downlink transmission for the multicast, the UE 104a starts receiving DCI scrambled with a CRC by the RNTI for the multicast, wherein the DCI is used to schedule at least one retransmission of the SPS downlink transmission for the multicast. Regarding BS102, in response to receiving feedback with NACK for SPS downlink transmission for multicast, BS102 starts sending DCI to UE 104a that scrambles CRC with RNTI for multicast, which is used to schedule at least one retransmission of SPS downlink transmission for multicast.

In some embodiments where the UE is configured with a NACK-only feedback mode, the UE stops providing feedback for MBS TBs carried on the SPS PDSCH in response to the UE determining that the first timer is expired and the second timer is running. Or the UE may continue to provide NACK feedback in a feedback resource shared by a group of UEs receiving the same MBS TB in response to determining that the UE fails to receive the MBS TB on the SPS PDSCH occasion. In addition, the UE resumes monitoring DCI formats scrambled with CRC by G-RNTI or G-CS-RNTI. I.e. the monitoring of the GC-PDCCH is triggered by the NACK feedback of the UE. BS102 may then retransmit the MBS TBs scheduled by the UE-specific PDCCH or GC-PDCCH.

In some embodiments, after introducing the MBS timer, the UE switches to a default DL BWP in response to determining that both the MBS timer and the BWP deactivation timer have expired.

Fig. 5 is a flow chart of an example method 500 for managing multicast communications in accordance with yet another embodiment of the present invention. Referring to fig. 1A-3 and 5, method 500 may be performed by BS102 and a UE (e.g., UE 104 a). In certain embodiments, block 330 comprises one or more of blocks 510, 520, 530, 540, 550, and 560, and block 325 comprises one or more of blocks 515, 525, 535, 552, and 554.

At 510, the UE determines that a first timer is running (e.g., still running, not yet expired, unexpired, etc.), and a second timer expires (e.g., no longer running, expired, etc.). That is, the MBS timer (first timer) is configured by the network 102 to the UE 104a for receiving MBS and has not yet expired, but the BWP deactivation timer has expired. In response to 510, the ue 104a may perform one or more of 520, 530, 540, 550, or 560.

At 520, UE 104a switches the frequency range for information reception from active BWP (e.g., active BWP 220) to CFR (e.g., CFR 210). For example, after expiration of the second timer (e.g., BWP deactivation timer), UE 104a switches from activating BWP to CFR to save power, because the bandwidth of CFR is not greater than activating BWP. Then, the bandwidth modification from the active BWP to the CFR will bring some delay. At 515, BS102 communicates information transmissions using the frequency range of the CFR (instead of activating BWP) with the UE.

At 530, instead of switching in some arrangements 520, the UE 104a continues to use the frequency range of the active BWP for information reception. In other words, the UE 104a does not switch to CFR after the BWP deactivation timer expires. In such an embodiment, no switching bandwidth is required. At 525, BS102 communicates information transmissions using the frequency range of the activated BWP with UE 104 a.

At 540, the UE 104a receives an SPS downlink transmission (e.g., SPS PDSCH) for the unicast, and at 535, the BS102 sends the SPS downlink transmission for the unicast. An embodiment of SPS downlink transmission includes SPS PDSCH scrambled by C-RNTI or CS-RNTI. In response to 510, the ue 104a stops monitoring the DCI format of the CRC scrambled by the C-RNTI or CS-RNTI, but still receives the SPS PDSCH for unicast. In response to determining that the transmission parameters of the SPS PDSCH change, BS102 indicates the updated transmission parameters through appropriate signaling, such as MAC layer signaling (e.g., MAC CE). For example, MAC layer signaling may be carried on one SPS PDSCH. The updated transmission parameters are validated for the next SPS PDSCH, next modification period, or specified point in time (e.g., time offset) after the PDSCH carrying MAC layer signaling.

In some embodiments, the deactivation of SPS transmissions may be indicated by appropriate signaling (e.g., MAC layer signaling). Also, the UE 104a will deactivate SPS transmissions for the next SPS PDSCH, the next modification period, or a specified point in time (e.g., time offset) after the PDSCH carrying MAC layer signaling.

In some embodiments, the UE 104a stops providing feedback (e.g., HARQ-ACKs) for unicast TBs carried on SPS downlink transmissions. In some embodiments, the UE 104a continues to provide feedback (e.g., ACK/NACK) in the UE-specific resources based on receipt of the unicast TBs. For example, at 550, UE 104a sends feedback to BS102 for the unicast SPS downlink transmission, and at 552, BS102 receives feedback for the unicast SPS downlink transmission. In this regard, at 554, in response to receiving the feedback at 552, BS102 sends at least one retransmission of the SPS downlink transmission for unicast, and UE 104a receives the same retransmission at 560.

For example, in response to determining that the UE fails to receive unicast TBs on the SPS PDSCH occasion, the UE 104a sends NACK feedback to the BS 102. The UE 104a then resumes monitoring the DCI format scrambled by the C-RNTI or CS-RNTI for CRC. That is, in response to sending feedback with NACK for unicast SPS downlink transmission, the UE 104a starts monitoring GC-PDCCH. BS102 may retransmit the unicast TBs in dynamic scheduling mode. That is, BS102 schedules retransmission of unicast TBs using a UE-specific PDCCH that carries a DCI format of a CRC scrambled by a C-RNTI or CS-RNTI. In other words, in response to sending feedback with NACK for SPS downlink transmissions for unicast, the UE 104a starts receiving DCI scrambled with CRC by RNTI for unicast, where the DCI is used to schedule at least one retransmission of SPS downlink transmissions for unicast. On the network side, in response to receiving feedback with NACK for SPS downlink transmission for unicast, BS102 starts transmitting DCI scrambled with CRC by RNTI for multicast, where the DCI is used to schedule at least one retransmission of SPS downlink transmission for unicast.

Fig. 6 is a flow chart of a method 600 for managing multicast communications in accordance with yet another embodiment of the present invention. Referring to fig. 1A-3 and 6, method 600 may be performed by BS102 and a UE (e.g., UE 104 a). In certain embodiments, block 330 comprises one or more of blocks 610 and 620, and block 325 comprises block 615.

At 610, the UE determines that a first timer expires (e.g., no longer running, has expired, etc.), and a second timer is running (e.g., still running, has not expired, etc.). That is, the MBS timer (first timer) is configured by the network 102 to the UE 104a for receiving MBS and has expired, but the BWP deactivation timer has not yet expired.

In some embodiments, in response to 610, the ue 104a stops MBS-related operations. For example, the UE 104a stops monitoring DCI formats of CRCs scrambled by G-RNTI, stops monitoring DCI formats of CRCs scrambled by group common configuration scheduling RNTI (e.g., G-CS-RNTI), stops receiving SPS PDSCH scrambled by group common configuration scheduling RNTI (which may be the same or different from G-CS-RNTI), stops receiving all transmissions related to MBS, disables related operations configured under CFR, and so on.

The network (e.g., BS 102) may wake up UE 104a to perform the stopped MBS-related operations. In response to 610, the ue 104a may perform 620. For example, at 620, the UE receives a UE-specific downlink control channel (e.g., PDCCH) that schedules a downlink physical channel (e.g., MBS TBPDSCH) corresponding to the multicast. At 615, BS102 transmits a UE-specific downlink control channel that schedules a downlink physical channel corresponding to the multicast. For example, the network side (e.g., BS 102) schedules PDSCH carrying MBS TBs using UE-specific PDCCH carrying DCI formats with CRC scrambled by C-RNTI or CS-RNTI. In some cases, the MBS TBs are identified by an upper layer (e.g., the MAC layer of UE 104 a). In some embodiments, the MBS TB is identified by an indication in DCI carried on a UE-specific PDCCH.

For example, the MBS timer is restarted and the UE 104a resumes MBS-related operations. In some embodiments, recovery of MBS-related operations begins after a certain point in time. The point in time may be a time offset after the UE 104a receives PDSCH carrying MBS TBs. In some embodiments, the time offset may be defined in terms of UE capabilities. Accordingly, at 630, in response to receiving a UE-specific downlink control channel that schedules a downlink physical channel corresponding to a multicast or paging downlink control channel, UE 104a performs at least one of recovering MBS operations or resetting the first timer.

Fig. 7 is a flow chart of a method 700 for managing multicast communications in accordance with another embodiment of the present invention. Referring to fig. 1A-3 and 7, method 700 may be performed by BS102 and a UE (e.g., UE 104 a). In some arrangements, block 330 includes one or more of blocks 710, 720, and 730, and block 325 includes block 715.

At 710, the UE determines that a first timer is expired (e.g., no longer running, expired, etc.), and a second timer is running (e.g., still running, not yet expired, unexpired, etc.). That is, the MBS timer (first timer) is configured by the network 102 to the UE 104a for receiving MBS and has expired, but the BWP deactivation timer has not yet expired.

In some embodiments, the ue 104a stops MBS-related operations in response to 710. For example, the UE 104a stops monitoring DCI formats of CRCs scrambled by G-RNTI, stops monitoring DCI formats of CRCs scrambled by group common configuration scheduling RNTI (e.g., G-CS-RNTI), stops receiving SPS PDSCH scrambled by group common configuration scheduling RNTI (which may be the same or different from G-CS-RNTI), stops receiving all transmissions related to MBS, disables related operations configured under CFR, and so on.

The network (e.g., BS 102) may wake up UE 104a to perform the stopped MBS-related operations. In response to 710, the ue 104a may perform 720. For example, at 720, the UE receives a paging downlink control channel (e.g., paging PDCCH) indicating resumption of MBS operations. At 715, BS102 transmits a paging downlink control channel indicating resumption of MBS operations. Blocks 715 and 720 allow the UE 104a to resume MBS-related operations. For example, paging transmissions (including at least one of paging PDCCH and paging PDSCH) may be used to indicate MBS-related operation recovery.

Then, the MBS timer is restarted and the UE 104a resumes MBS-related operations. In some arrangements, recovery of MBS-related operations begins after a certain point in time. The point in time may be a time offset after the UE 104a receives PDSCH carrying MBS TBs. In some embodiments, the time offset may be defined in terms of UE capabilities. Accordingly, at 730, in response to receiving the paging downlink control channel indicating recovery of the MBS-related operation, the UE 104a performs at least one of recovering the MBS-related operation or resetting the first timer.

The paging downlink control channel (e.g., paging PDCCH) may indicate that recovery of MBS-related operations may be achieved using a field of the packetized PDCCH. For example, fig. 8 is a schematic diagram of a DCI format for paging PDCCH 800 according to an embodiment of the present invention. As an example of the paging PDCCH 800, a DCI format 1_0 of a CRC scrambled by a P-RNTI is shown in fig. 8. The DCI format of the paging PDCCH 800 includes fields such as a short message indicator field 810, a short message field 820, a paging schedule information field 830, and a reserved field 840. Reserved field 840 may have one or more bits (e.g., 8 bits). In some embodiments, the codepoints of the information field represent particular values or bits of the information field.

In some embodiments, short message indicator field 810 has one or more bits (e.g., 2 bits) in the DCI format. The short message indicator field 810 is used to indicate the validity of the remaining information fields 820, 830, and 840 in the DCI format, as shown in fig. 9, fig. 9 shows a mapping 900 between bit fields and indications. A bit field or code point of "01" indicates that only the scheduling information paging field 830 is valid in the DCI and that bits in the short message field 820 are reserved. A bit field or code point of "10" indicates that only the short message field 820 is valid in the DCI, and the bits in the scheduling information paging field 830 are reserved. A bit field or code point of "11" indicates that both the short message field 820 and the scheduling information paging field 830 in the DCI are valid. As shown, a bit field or code point of "00" is reserved.

In some examples, short message field 820 has one or more bits (e.g., 8 bits) in the DCI format. The short message field 820 contains one or more short messages. Fig. 10 is a diagram illustrating a mapping 1000 between bits of a short message field 820 and short messages in a paging PDCCH according to various arrangements. As shown, a bit or code point of "1" corresponds to a systemInfoModification (system information modification) short message. Bit or code point "2" corresponds to a short message of etwsAndCmasIndication (indicated by etws and Cmas). Bit or code point "3" corresponds to a short message stopping page monitoring (stopPagingMonitoring). Bits or codepoints 4-8 are not currently used.

The scheduling information paging field 830 has one or more bits containing bandwidth related information. The scheduling information paging field 830 is used to indicate scheduling information of paging PDSCH. The scheduling information includes frequency domain resource allocation information, time domain resource allocation, virtual resource block (Virtual Resource Blocks, VRB) to PRB mapping, modulation and coding scheme (Modulation and Coding Scheme, MCS), TB scaling, etc.

In some embodiments, the code point of short message indicator field 810 indicates the resumption of MBS-related operations. In particular, a reserved value or code point of the short message indicator field 810 is used for indication. For example, a value or code point "00" of the short message indicator field 810 is defined as an MBS-related operation resume indication. More specifically, for the UE 104a that stops performing MBS-related operations when the MBS timer expires, the UE 104a is responsive to receiving a paging PDCCH indicating a short message field value of "00" on its paging occasion. UE 104a resumes MBS-related operations.

In some embodiments, at least one reserved bit in short message field 820 indicates that MBS-related operations are resumed. In particular, one or more reserved bits or code points corresponding thereto in the short message field 820 are used for indication. For example, as shown in fig. 10, one or more bits (e.g., bits 4-8) in the short message field 820 are reserved. One or more of the reserved bits may be used for MBS-related operation recovery indication.

In one embodiment, 1 bit of the reserved bits is used for MBS-related operation recovery indication. In response to determining that the value of the bit is set to a predetermined value (e.g., 1), the UE 104a resumes MBS-related operation.

In another embodiment, a plurality of reserved bits are used in the short message field 820 for MBS-related operation recovery indication. Each bit corresponds to a particular MBS or a particular MBS group. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores a specific MBS service or a specific MBS service group corresponding to or mapped to the bit.

Or MBS-related operations are also classified into different types. Each of the reserved bits in the short message field 820 corresponds to a type of MBS-related operation. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores the MBS type corresponding to or mapped to the bit.

Or preconfiguring the mapping relation between at least one reserved bit in the short message field and the UE ID in an RRC signaling mode and the like. Then, the value of one of the bits is set to a predetermined value (e.g., 1), indicating that the UE corresponding to the bit should resume MBS-related operations.

In some embodiments, the combination of at least one reserved bit in short message field 820 and at least one reserved bit in reserved portion 840 in the DCI format indicates that MBS-related operations are resumed. As shown in fig. 10, several bits (e.g., 4-8 bits) in the short message field 820 are reserved. In addition, another 8 bits in the DCI format (e.g., in reserved portion 840) are also reserved. One or more bits of each reserved bit in the short message field 820 and the reserved portion 840 may be used for MBS-related operation recovery indication.

For example, 1 bit of the reserved bits in the short message field 820 is used to indicate that MBS-related operations need to be resumed. In response to determining that the value of the bit is set to a predetermined value (e.g., 1), UE 104a further determines which type of MBS-related operation to resume according to the indication of at least one or all reserved bits in reserved portion 840 of the DCI format.

In some embodiments, each bit of at least one or all reserved bits in reserved portion 840 of the DCI format corresponds to a particular MBS service or a particular MBS service group. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores a specific MBS service or a specific MBS service group corresponding to or mapped to the bit.

Or MBS-related operations may be classified into different types. Each bit of at least one or all reserved bits in reserved portion 840 of the DCI format corresponds to a type of MBS-related operation. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores the MBS type corresponding to or mapped to the bit.

Or the mapping relationship between at least one reserved bit in the DCI format and the UE ID is preconfigured, for example, through RRC signaling. Then, the value of one of the bits is set to a predefined value (e.g., 1), indicating that the UE corresponding to the bit should resume MBS-related operations.

In some embodiments, the combination of at least one reserved bit in short message field 820 and at least one bit in scheduling information field 830 indicates that MBS-related operations are resumed. As shown in fig. 10, several bits (e.g., 4-8 bits) in the short message field 820 are reserved. In some examples where the value of the short message indication field 810 is set to "10", all bits for the scheduling information indicated by the paging field 830 are reserved. One or more of these bits of the scheduling information paging field 830 may be used for MBS-related operation recovery indication.

For example, 1 bit of the reserved bits in the short message field 820 is used to indicate that MBS-related operations need to be resumed. In response to determining that the value of this bit is set to a predetermined value (e.g., 1), UE 104a further determines which type of MBS-related operation to resume based on the indication of at least one or all of the reserved bits in scheduling information paging field 830, which were originally used for the scheduling information indication.

In some embodiments, each of at least one or all of the reserved bits in the scheduling information paging field 830 that was originally used for the scheduling information indication corresponds to a particular MBS service or a particular group of MBS services. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores a specific MBS service or a specific MBS service group corresponding to or mapped to the bit.

Or MBS-related operations may be classified into different types. Each of at least one or all of the reserved bits in the scheduling information paging field 830 that is initially used for the scheduling information indication corresponds to a type of MBS-related operation. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores the MBS type corresponding to or mapped to the bit.

Or in one embodiment, 1 bit in the reserved bits in the short message field is used to indicate that MBS-related operations need to be resumed. The value of the bit is set to a predefined value (e.g., 1) indicating whether the UE should resume to perform MBS-related operations. More specifically, the mapping relationship between the bits initially used for the scheduling information indication and the UE ID is preconfigured by means of RRC signaling or the like. Then, the value of one of the bits is set to a predetermined value (e.g., 1), indicating that the UE corresponding to the bit should resume MBS-related operations.

In some embodiments, a combination of at least one reserved bit in short message field 820, at least one bit in scheduling information field 830, and at least one reserved bit in reserved portion 840 in the DCI format indicates that MBS-related operations are resumed. As shown in fig. 10, several bits (e.g., 4-8 bits) in the short message field 820 are reserved. In some examples where the value of the short message indication field 810 is set to "10", all bits indicated by the paging field 830 for scheduling information are reserved. One or more of these bits of the scheduling information paging field 830 may be used for MBS-related operation recovery indication.

For example, 1 bit of the reserved bits in the short message field 820 is used to indicate that certain MBS-related operations need to be resumed. In response to determining that the value of the bit is set to a predetermined value (e.g., 1), UE 104a further determines which type of MBS-related operation to resume based on the indication of at least one or all reserved bits in scheduling information paging field 830 that was originally used for the indication of scheduling information and the indication of at least one or all reserved bits in reserved portion 840 of the DCI format.

In some embodiments, each of at least one or all of the reserved bits in the scheduling information paging field 830 that was originally used for the scheduling information indication and the reserved portion 840 of the DCI format each of the at least one or all of the reserved bits corresponds to a particular MBS service or a particular group of MBS services. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores a specific MBS service or a specific MBS service group corresponding to or mapped to the bit.

Or MBS-related operations may be classified into different types. Each of at least one or all of the reserved bits in the scheduling information paging field 830, which is initially used for the scheduling information indication, and the reserved portion 840 of the DCI format, each of at least one or all of the reserved bits corresponds to a type of MBS-related operation. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a restores the MBS type corresponding to or mapped to the bit.

Or in one embodiment, 1 bit in the short message field reserved bits is used to indicate that MBS-related operations need to be resumed. The value of the bit is set to a predefined value (e.g., "1") indicating whether the UE should resume to perform MBS-related operations. More specifically, the mapping relationship between the bits initially used for the scheduling information indication and the reserved bits in the DCI format and the UE ID is preconfigured by RRC signaling or the like. Then, the value of one of the bits is set to a predefined value (e.g., "1"), indicating that the UE corresponding to the bit should resume MBS-related operations.

In some embodiments, a combination of a reservation value or code point in the short message indicator field 810 and the paging PDSCH scheduled by the paging downlink control channel (received at 720) is used to indicate MBS-related operations recovery. For example, a value or code point "00" of the short message indication field 810 is defined as an MBS-related operation recovery indication.

In response to the UE 104a receiving a paging PDCCH with the short message indicator field 810 set to "00" on its paging occasion, the UE 104a receives a paging PDSCH according to the indication of the scheduling information paging field 830 in the DCI format. The UE 104a further determines which type of MBS-related operation to resume based on the indication in the paging PDSCH. For example, each bit of some or all reserved bits in the paging PDSCH corresponds to a particular MBS service or a particular MBS service group. Then, in response to determining that the value of one of the bits is set to a predetermined value, e.g., 1, the ue 104a determines to resume a specific MBS service or a specific MBS service group corresponding to the bit.

Or in response to the UE 104a receiving a paging PDCCH with the short message indicator field 810 set to "00" on its paging occasion, the UE 104a receives a paging PDSCH according to the indication of the scheduling information paging field 830 in the DCI format. UE 104a further determines which UE needs to resume MBS-related operations. More specifically, the UE ID of the UE that should resume MBS-related operations is included in the paging PDSCH. Or the mapping relation between the bits in the paging PDSCH and the UE ID is preconfigured by means of RRC signaling and the like. The value of one of the bits is set to a predefined value (e.g., "1"), indicating that MBS-related operations are to be resumed by the UE (e.g., UE ID) corresponding to or mapped to the bit.

In some embodiments, a combination of reserved bits in short message field 820 and paging PDSCH (received at 720) scheduled by paging downlink control channel is used to indicate MBS-related operations recovery. As shown in fig. 10, several bits (e.g., 4-8 bits) in the short message field 820 are reserved. One or more of the reserved bits in the short message field 820 may be used for MBS-related operation recovery indication.

For example, in response to determining that the value of one or more bits of the reserved bits in the short message field 820 is set to a predetermined value, e.g., 1, the ue 104a receives the paging PDSCH according to the indication of the scheduling information paging field 830 in the DCI format. The UE 104a further determines which type of MBS-related operation to resume based on the indication in the paging PDSCH. For example, each of some or all of the reserved bits in the paging PDSCH corresponds to a particular MBS service or a particular group of MBS services. Then, in response to determining that the value of one of the bits is set to a predetermined value (e.g., 1), the UE 104a determines to resume the particular MBS service or the particular MBS service group corresponding to the bit.

Or UE 104a further determines which UE needs to resume MBS-related operations. More specifically, the UE ID of the UE that should resume MBS-related operations is included in the paging PDSCH. Or the mapping relation between the bits in the paging PDSCH and the UE ID is preconfigured by means of RRC signaling and the like. The value of one of the bits is set to a predetermined value (e.g., "1"), indicating that MBS-related operations are to be resumed by the UE (e.g., UE ID) corresponding to or mapped to the bit.

In some embodiments, a combination of a code point in the short message indicator field and at least one of the remaining bits in the DCI format indicates that MBS-related operations are resumed. As one example, the code point "00" of the short message indicator field is defined as an MBS-related operation resume indication.

If the UE receives a paging PDCCH with the short message indicator field set to '00' in its paging occasion, the UE further determines which type of MBS-related operation should be resumed according to the indication of some or all reserved bits in the DCI format.

Each bit of some or all of the reserved bits in the DCI format corresponds to a particular MBS service or a particular MBS service group. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, the value of one of the bits is set to a predetermined value (e.g., 1) indicating that reception of the MBS service corresponding to the bit needs to be resumed.

Or MBS-related operations are also classified into different types. Each bit of some or all reserved bits in the DCI format corresponds to a type of MBS-related operation. The above-mentioned mapping relationship is defined by a signaling configuration or in a specification. Then, the value of one of the bits is set to a predefined value (e.g., 1), indicating that the MBS-related operation corresponding to the bit needs to be restored.

Or if the UE receives a paging PDCCH with the short message indication field set to "00" in its paging occasion, the UE may further determine whether MBS-related operation should be resumed. More specifically, the mapping relationship between the reserved bits in the DCI format and the UE ID is preconfigured, for example, through RRC signaling. Then, the value of one of the bits is set to a predetermined value (e.g., 1), indicating that the UE corresponding to the bit should resume MBS-related operations.

In some embodiments, authentication conditions for a first timer (e.g., MBS timer) are defined. UE 104a determines that the MBS timer is deemed invalid. In response to determining at least one of: 1) The CFR of the multicast transmission is fully contained in the default downlink BWP; 2) The CFR of the multicast transmission is fully contained in the default downlink BWP and the CFR of the default BWP contains the multicast transmission.

Regarding condition 1), the CFR is fully contained in the default DL BWP. As shown in fig. 11, the CFR may be the same as the CFR associated with activating BWP. In fig. 11, in some implementations of wireless communication network 100 and wireless communication system 150, for multicasting by RRC-connected UEs (e.g., UE 104 a), CFR 1120 for GC PDCCH and/or GC-PDSCH is limited to frequency resources of dedicated unicast BWP (also referred to as active BWP 1110) to support simultaneous reception of unicast and multicast in the same time slot. Default BWP 1130 (or default DL BWP) is located entirely within active BWP 1110. As shown in fig. 11, CFR 1120 may be the same as the CFR associated with activating BWP 1110.

Or as shown in fig. 12, the CFR may be different from the CFR associated with activating BWP. In fig. 12, in some implementations of wireless communication network 100 and wireless communication system 150, for multicasting by RRC-connected UEs (e.g., UE 104 a), CFR 1220 for GC PDCCH and/or GC-PDSCH is limited to frequency resources of dedicated unicast BWP (also referred to as active BWP 1210) to support simultaneous reception of unicast and multicast in the same time slot. The default BWP 1230 (or default DL BWP) is entirely outside the active BWP 1210. As shown in fig. 12, CFR 1240 differs from CFR 1220 associated with activating BWP 1210.

Regarding condition 2), the CFR is included in the default DL BWP, and the CFR associated with the default BWP includes MBS services to be received by the UE. As shown in fig. 12, CFR 1240 differs from CFR 1220 associated with activating BWP 1210.

The subject matter described in embodiments of the invention sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely illustrative, and that in fact many other architectures can be implemented which achieve the same functionality. Any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Thus, any two components in an embodiment of the invention that are combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being "operably connected," or "operably coupled," to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably coupled," to each other to achieve the desired functionality. Specific examples of operably coupled include, but are not limited to, physically mateable and/or physically interactable components and/or wirelessly interactable components and/or logically interactable components.

With respect to the use of plural and/or singular terms in embodiments of the present invention, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. For clarity, various singular/plural permutations may be explicitly set forth herein.

It will be understood by those within the art that, in general, terms used herein, and especially those in the appended claims (e.g., bodies of the appended claims), are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "including" should be interpreted as "including but not limited to," etc.).

Although the figures and description may show a particular order of method steps, the order of the steps may be different than that depicted and described, unless otherwise specified by the embodiments of the invention. Furthermore, two or more steps may be performed concurrently or with partial concurrence, unless otherwise specified by embodiments of the present invention. Such variations may depend, for example, on the software and hardware system selected and the designer's choice. All such variations are within the scope of the present disclosure. Likewise, software implementations of the described methods may be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.

Those skilled in the art will further understand that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim containing such introduced claim recitation to disclosures containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should typically be interpreted to mean "at least one" or "one or more"); as well as the use of definite articles to introduce claim recitations. Furthermore, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations" (without other modifiers), typically referring to at least two recitations, or two or more recitations).

Further, where a convention analogous to "at least one of A, B and C, etc." is used, such a construction in general is designed in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to a system having a alone, B alone, C, A and B together alone, a and C together, B and C together, and/or A, B and C together, etc.). Where a convention analogous to "at least one of A, B or C, etc." is used, in general such a construction is designed in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to a system having a alone, B alone, C, A and B together, a and C together, B and C together, and/or A, B and C together, etc.). Those skilled in the art will further appreciate that virtually any separate word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including a term, either term, or both. For example, the phrase "a or B" will be understood to include the possibilities of "a" or "B" or "a and B".

Further, unless otherwise indicated, the use of words such as "about," "approximately," "substantially," etc. mean plus or minus 10%.

The foregoing description of illustrative implementations has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosed implementations. It is intended that the scope of the disclosure be defined by the following claims and their equivalents.

Claims (28)

1. A method of wireless communication, comprising:

The wireless communication device determining a first timer for multicasting;

the wireless communication device determining a second timer for bandwidth part BWP deactivation;

the wireless communication device receives a multicast transmission from a network based on the first timer and the second timer.

2. The method of claim 1, further comprising, in response to determining that the first timer is expired and the second timer is running, performing at least one of:

the wireless communication device stops receiving downlink control information DCI scrambled by a radio network temporary identity RNTI for the multicast by a cyclic redundancy check CRC;

The wireless communication device continues to receive semi-persistent scheduling (SPS) downlink transmissions for the multicast;

the wireless communication device receiving signaling corresponding to activating, deactivating or modifying transmission parameters for the SPS downlink transmission;

The wireless communication device sending feedback to the network for the SPS downlink transmission of the multicast; or alternatively

The wireless communication device receives at least one retransmission of the SPS downlink transmission for the multicast from the network.

3. The method of claim 2, further comprising, in response to sending feedback with a negative acknowledgement, NACK, for the SPS downlink transmission for the multicast,

The wireless communication device starts receiving the DCI scrambled with the RNTI for the multicast, wherein the DCI is used to schedule at least one retransmission of the SPS downlink transmission for the multicast.

4. The method of claim 1, further comprising, in response to determining that the first timer is running and the second timer expires, performing at least one of:

The wireless communication device switches the frequency range for information reception from an active BWP to a common frequency range CFR;

the wireless communication device continuing to use the frequency range of the active BWP for the information reception;

the wireless communication device receives a semi-persistent scheduling, SPS, downlink transmission for unicast;

The wireless communication device sending feedback to the network for the SPS downlink transmission of the unicast; or alternatively

The wireless communication device receives at least one retransmission of the SPS downlink transmission for the unicast from the network.

5. The method of claim 4, further comprising, in response to sending the feedback with a negative acknowledgement, NACK, for the SPS downlink transmission for the unicast,

The wireless communication device begins receiving DCI scrambled with an RNTI for the unicast CRC, wherein the DCI is used to schedule the one less retransmission for the SPS downlink transmission for the unicast.

6. The method of claim 1, further comprising, in response to determining that the first timer expires and the second timer is running, the wireless communication device receiving a user equipment, UE, specific downlink control channel from the network, the UE specific downlink control channel scheduling a downlink physical channel corresponding to the multicast.

7. The method of claim 1, further comprising, after determining that the first timer expires and the second timer is running, the wireless communication device receiving a paging downlink control channel from the network indicating a resumption of multicast broadcast service, MBS, operation.

8. The method of claim 7, further comprising, in response to receiving the paging downlink control channel indicating resumption of the MBS operation, performing at least one of:

The wireless communication device resumes the MBS operation; or alternatively

The wireless communication device resets the first timer.

9. The method of claim 7, wherein,

The paging downlink control channel includes a short message indicator field;

the code point of the short message indicator field indicates that the MBS operation resumes.

10. The method of claim 7, wherein,

The paging downlink control channel comprises a short message field;

At least one reserved bit in the short message field indicates that the MBS operation resumes.

11. The method of claim 7, wherein,

The paging downlink control channel comprises a short message field and at least one reserved bit;

The combination of at least one reserved bit in the short message field and at least one reserved bit in the DCI format indicates the MBS operation resume.

12. The method of claim 7, wherein,

The paging downlink control channel comprises a short message field and a scheduling information field;

the combination of at least one reserved bit in the short message field and at least one bit in the scheduling information field indicates the MBS operation resume.

13. The method of claim 7, wherein,

The paging downlink control channel comprises a short message field, a scheduling information field and at least one reserved bit;

The combination of at least one reserved bit in the short message field, at least one bit in the scheduling information field, and at least one reserved bit in the DCI format indicates the MBS operation resume.

14. The method of claim 7, wherein,

The paging downlink control channel comprises a short message indicator field and a paging downlink channel scheduled by the paging downlink control channel;

the combination of the code point in the short message indicator field and the information carried in the paging downlink channel indicates that the MBS operation resumes.

15. The method of claim 7, wherein,

The paging downlink control channel comprises a short message field and a paging downlink channel scheduled by the paging downlink control channel;

the combination of at least one reserved bit in the short message field and the information carried in the paging downlink channel indicates that the MBS operation resumes.

16. The method of claim 7, wherein,

The paging downlink control channel includes a short message indicator field;

The combination of the code point in the short message indicator field and at least one bit of the remaining bits in the DCI format indicates the MBS operation resume.

17. The method of claim 1, further comprising determining that the first timer is invalid in response to determining at least one of:

The default downlink BWP completely contains the common frequency range CFR for the multicast transmission; or alternatively

The default downstream BWP completely includes a CFR for the multicast transmission, the CFR of the default BWP including the multicast transmission.

18. A wireless communication device comprising at least one processor and a memory, wherein the at least one processor is configured to read codes from the memory and implement the method of claim 1.

19. A computer program product comprising computer readable program medium code stored thereon, which when executed by at least one processor causes the at least one processor to implement the method of claim 1.

20. A method of wireless communication, comprising:

The network configures a first timer for multicasting for the wireless communication device;

The network configures the wireless communication device with a second timer for bandwidth part BWP deactivation;

The network sends a multicast transmission to the wireless communication device based on the first timer and the second timer.

21. The method of claim 20, wherein the first timer expires and the second timer is running, the method further comprising at least one of:

the network continues to send a semi-persistent scheduling, SPS, downlink transmission for the multicast to the wireless communication device;

The network transmitting signaling to the wireless communication device corresponding to activating, deactivating or modifying transmission parameters for the SPS downlink transmission;

The network receiving feedback from the wireless communication device for the SPS downlink transmission of the multicast; or alternatively

The network sends at least one retransmission of the SPS downlink transmission for the multicast to the wireless communication device.

22. The method of claim 21, further comprising, in response to receiving the feedback with a negative acknowledgement, NACK, for the SPS downlink transmission of the multicast,

The network transmits to the wireless communication device downlink control information DCI scrambled by a radio network temporary identity RNTI for the multicast, cyclic redundancy check, CRC, wherein the DCI is used to schedule the at least one retransmission of the SPS downlink transmission for the multicast.

23. The method of claim 20, wherein the first timer is running and the second timer expires, the method further comprising at least one of:

The wireless communication equipment uses the frequency range of the common frequency range CFR for information transmission when communicating;

the network uses the wireless communication device to transmit the information using a frequency range of an active BWP;

the network transmitting a semi-persistent scheduling, SPS, downlink transmission for unicast to the wireless communication device;

the network receiving feedback from the wireless communication device for the SPS downlink transmission of the unicast; or alternatively

The network sends at least one retransmission of the SPS downlink transmission for the unicast to the wireless communication device.

24. The method of claim 23, further comprising, in response to receiving the feedback with a negative acknowledgement, NACK, for the SPS downlink transmission of the unicast,

The network transmits DCI scrambled with a CRC by an RNTI for the multicast to the wireless communication device, wherein the DCI is used to schedule the at least one retransmission for the SPS downlink transmission for the unicast.

25. The method of claim 20, wherein the first timer expires and the second timer is running, the method further comprising the network transmitting a user equipment, UE, specific downlink control channel to the wireless communication device, the UE specific downlink control channel scheduling a downlink physical channel for the multicast.

26. The method of claim 20, wherein the first timer expires and the second timer is running, the method further comprising transmitting, by the network to the wireless communication device, a paging downlink control channel indicating resumption of multicast broadcast service, MBS, operation.

27. A wireless communication device comprising at least one processor and a memory, wherein the at least one processor is configured to read codes from the memory and implement the method of claim 20.

28. A computer program product comprising computer readable program medium code stored thereon, which when executed by at least one processor causes the at least one processor to implement the method of claim 20.