Semi-static Scheduling of Multicast Broadcast Services

Abstract

Example embodiments of the present disclosure relate to devices, methods, apparatus, and computer-readable storage media for semi-persistently scheduling a multicast broadcast service (MBS) service. In an example embodiment, at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a portion of bandwidth used for MBS services is determined. At least one of enabling, disabling, or modifying the semi-persistent scheduling configuration is indicated to the group of devices.

Description

Technical Field

[0001] Example embodiments of the present disclosure relate generally to the field of communications, and more particularly, to an apparatus, method, device, and computer-readable storage medium for semi-persistently scheduling a multicast broadcast service (MBS) service. Background Art

[0002] As part of the Work Item Description (WID) on Fifth Generation (5G) / New Radio (NR), the Third Generation Partnership Project (3GPP) is currently defining mechanisms for enabling the delivery of multicast and / or broadcast services to multiple user equipments (UEs). One of the key goals of WID is to define group scheduling mechanisms that allow multicast and / or broadcast services to be scheduled using common data channel resources while maintaining maximum commonality with the currently defined unicast scheduling and operation mechanisms. One of the goals of WID (although not currently considered high priority) is to support UEs in idle and inactive modes. It is expected that as part of Rel-17 WID, or as part of a future release, idle and inactive UEs will be supported along with UEs in connected mode. Based on the latest protocols, in Rel-17 Multicast Broadcast Service (MBS), broadcasts need to support all RRC states. Summary of the Invention

[0003] Generally speaking, example embodiments of the present disclosure provide devices, methods, apparatus, and computer-readable storage media for semi-persistently scheduling multicast broadcast service traffic.

[0004] In a first aspect, a device is provided, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the device to determine at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a portion of bandwidth used for multicast broadcast service traffic. The device is further configured to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the portion of bandwidth to the group of devices.

[0005] In a second aspect, a device is provided that includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the device to determine whether a semi-persistent scheduling configuration is enabled, modified, or disabled for a multicast broadcast service (MBS) service on a bandwidth portion. If the semi-persistent scheduling configuration is determined to be enabled, the device is further caused to receive the MBS service on the bandwidth portion according to the semi-persistent scheduling configuration.

[0006] In a third aspect, a method is provided in which at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a bandwidth portion of a multicast broadcast service is determined. The at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration is then indicated to the group of devices.

[0007] In a fourth aspect, a method is provided in which a determination is made as to whether a semi-persistent scheduling configuration is enabled, modified, or disabled on a bandwidth portion for a multicast broadcast service. If the semi-persistent scheduling configuration is determined to be enabled, the multicast broadcast service is received on the bandwidth portion based on the semi-persistent scheduling configuration.

[0008] In a fifth aspect, there is provided an apparatus comprising means for performing the method according to the third aspect or the fourth aspect.

[0009] In a sixth aspect, a computer-readable storage medium is provided comprising program instructions stored thereon. When executed by a processor of a device, the instructions cause the device to perform the method according to the third aspect or the fourth aspect.

[0010] It should be understood that the summary is not intended to identify the key or essential features of the exemplary embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0012] Figure 1 The SPS configuration for different UEs is described;

[0013] Figure 2 An example scheduling of MBS traffic across a BWP of multiple UEs is illustrated;

[0014] Figure 3 shows an example environment in which example embodiments of the present disclosure may be implemented;

[0015] Figure 4 A flowchart illustrating an example method according to some example embodiments of the present disclosure is shown;

[0016] Figure 5 An example of implicit linking of the SPS configuration index with the MBS service is shown;

[0017] Figure 6 Flowcharts illustrating example methods according to some other example embodiments of the present disclosure;

[0018] Figure 7An example process of multiplexing the current SPS framework and configuration for configuring SPS for MBSPDSCH according to some example embodiments of the present disclosure is shown;

[0019] Figure 8 An example process of G-RNTI-based semi-persistent scheduling configuration according to some example embodiments of the present disclosure is shown;

[0020] Figure 9 An example process for dynamic and semi-persistent scheduling using G-RNTI and GCS-RNTI according to some example embodiments of the present disclosure is shown;

[0021] Figure 10 shows an example state transition process according to some example embodiments of the present disclosure; and

[0022] Figure 11 A simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure is shown.

[0023] Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. DETAILED DESCRIPTION

[0024] The principle of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these exemplary embodiments are described only to illustrate and help those skilled in the art understand and implement the present disclosure, and are not intended to limit the scope of the present disclosure. The disclosure described herein can be implemented in various ways except for the manner described below.

[0025] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0026] As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wirelessly communicating with each other or with a base station. Communication may involve sending and / or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information over the air. In some example embodiments, the UE may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from the network side, the UE may send information to the base station on a predetermined schedule.

[0027] Examples of UE include, but are not limited to, smartphones, wireless-enabled tablet computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), wireless customer premises equipment (CPEs), sensors, metering devices, personal wearable devices such as watches, and / or vehicles capable of communication. For the purposes of discussion, some exemplary embodiments will be described with reference to UEs as examples of terminal devices, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of this disclosure.

[0028] As used herein, the term "network device" refers to a device by which services can be provided to terminal devices in a communication network. As an example, a network device may include a base station. As used herein, the term "base station" (BS) refers to a network device by which services can be provided to terminal devices in a communication network. A base station may include any suitable device by which a terminal device or UE can access a communication network. Examples of base stations include relays, access points (APs), transmission points (TRPs), node Bs (NodeBs or NBs), evolved node Bs (eNodeBs or eNBs), new radio (NR) node Bs (gNBs), remote radio modules (RRUs), radio heads (RHs), remote radio heads (RRHs), low-power nodes such as femtos, pico, etc.

[0029] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0030] (a) hardware circuit implementation only (e.g., implementation in analog and / or digital circuits only) and

[0031] (b) combinations of hardware circuitry and software, such as (as applicable): (i) analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of a hardware processor and software (including a digital signal processor), software and memory that work together to enable a device such as a mobile phone or server to perform various functions, and

[0032] (c) A hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, requires software (e.g., firmware) for operation, but when software is not required for operation, the software may not be present.

[0033] This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular base station, or other computing or base station, if applicable to the particular claim element.

[0034] As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations are to be understood as open-ended terms meaning "including, but not limited to." The term "based on" is to be understood as meaning "based, at least in part, on." The terms "an embodiment" and "one embodiment" are to be understood as meaning "at least one embodiment." The term "another embodiment" is to be understood as meaning "at least one another embodiment." Other explicit and implicit definitions may be included below.

[0035] As used herein, the terms "first," "second," etc., may be used herein to describe various elements, and these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0036] In the fourth generation (4G), group scheduling mechanisms are implemented using semi-static or dynamic broadcast signaling of control information pointing to semi-static or dynamic shared data channel resources for evolved multicast broadcast multimedia service (eMBMS) and single cell point-to-multipoint (SC-PTM). eMBMS and SC-PTM require support for UEs in receive-only mode. Therefore, there are many limitations in system design for eMBMS and SC-PTM, such as supporting devices that are not registered with the network, supporting devices in idle mode, etc. Support for UEs in receive-only mode has a significant impact on the use of physical channels, such as the physical downlink shared channel (PDSCH) or the physical multicast channel (PMCH) to send multicast data / traffic channel (MTCH) and multicast control channel (MCCH) information.

[0037] It is important to note that various physical layer scheduling concepts such as bandwidth fractions do not exist for Long Term Evolution (LTE), and logical channels such as the Single Cell Multicast Control Channel (SC-MCCH) / MTCH are not defined for 5G / NR. Therefore, it may not be possible to redefine LTE-based multicast broadcast features for 5G. In addition, the physical downlink control channel (PDCCH) scheduling in 5G / NR is very different from that in LTE, making it challenging to adapt the parameters defined for LTE for use in 5G.

[0038] It is also important to note that for the delivery of multicast traffic in 5G NR, the current primary focus is on UEs in RRC_Connected mode—meaning that the UE is connected to the network or base station, where UE context information is active. However, as discussed above, for previous generations, unique enhancements have been enabled to facilitate optimal delivery of multicast traffic. For 5G NR, the enhancements currently being discussed primarily relate to dynamic downlink data traffic scheduling and radio resource optimization, which are primarily based on the currently defined unicast mechanisms.

[0039] There are also various mechanisms related to reliability improvement techniques. Dynamic scheduling operates similarly to unicast scheduling with some modifications, and is currently considered to support both UE-specific and group-common types of Physical Downlink Control Channel (PDCCH) signaling. Here, the term "UE-specific" means that PDCCH information is individually scheduled for all UEs interested in receiving MBS services, and the term "group-common" means that PDCCH information is scheduled for a group of UEs.

[0040] Currently, limited attention has been paid to semi-persistent scheduling. Although it is primarily applicable to deterministic services, it can significantly reduce the control channel signaling load and ultimately save power. Semi-persistent scheduling (SPS) is used for unicast in 5G / NR.

[0041] Figure 1 Figure 2 shows the SPS configurations of different UEs. Figure 1 As shown in Figure 1, 5G / NR currently supports up to eight semi-persistent scheduling configurations per bandwidth part (BWP). This configuration mainly includes the period of scheduling in data channels such as PDSCH, the number of hybrid automatic repeat request (HARQ) processes, the modulation and coding scheme (MCS) table to be used, the HARQ codebook, and the PDSCH aggregation factor for data repetition. These configurations are sent to the UE using RRC signaling, and each configuration is identified using an SPS configuration index.

[0042] For example, each SPS configuration is enabled using downlink control information (DCI), which is scrambled using the configured scheduling radio network temporary identifier (CS-RNTI), where the value of the SPS configuration index is embedded in the DCI. Once the UE receives the SPS configuration from the DCI, the UE calculates the period.

[0043] After configuring downlink allocations for SPS, the UE may then consider that the Nth downlink allocation occurs in the following time slots:

[0044] (numberOfSlotsPerFrame×SFN+slot number in the frame)=[(numberOfSlotsPerFrame×SFN start time +slots tart time )+N×periodicity×numberOfSlotsPerFrame / 10]modulo(1024×numberOfSlotsPerFrame)

[0045] Therefore, once the SPS configuration is signaled to the UE and activated, the UE will monitor the PDSCH at the configured periodicity and will not require further control signaling from the next generation NodeB (gNB) until the SPS configuration is modified or disabled. This also enables the gNB to configure discontinuous reception (DRX) to the UE to avoid unnecessary monitoring of the PDCCH without the expected modification / disable signaling, thereby achieving power savings for the UE.

[0046] So far, some agreements have been reached on SPS for MBS. For example, it has been agreed to support the SPS group-common PDSCH for MBS of RRC_CONNECTED UEs. However, the detailed procedures remain for further study (FFS). For example, whether to use the group-common PDCCH or UE-specific PDCCH for SPS group-common PDSCH activation / deactivation, whether to support more than one SPS group-common PDSCH configuration per UE, whether and how to configure uplink feedback, how to retransmit the SPS group-common PDSCH, etc.

[0047] The currently defined SPS concept is mainly applicable to unicast services and does not take into account MBS services. The scheduling of MBS services may overlap with the active BWP for unicast.

[0048] Figure 2 FIG. 4 shows an example scheduling of MBS services across BWPs of multiple UEs. Figure 2As shown, MBS traffic for a UE group (e.g., including UE-1, UE-2, and UE-3) is scheduled as BWPs 205 and 210, which are expected to overlap with the active BWP used for unicast to the UE group. There may be multiple MBS services scheduled by the gNB for different UE groups, so it will be challenging to adapt the SPS functionality to enable it to be used more efficiently for MBS. Furthermore, while the BWP concept has been agreed upon for MBS, different connected mode UEs will have different active BWP configurations based on the UE's traffic profile, and frequency domain resources will be allocated within the BWP. Therefore, broadcasting a common configuration to connected mode UEs will be challenging.

[0049] In addition, the DCI used to enable SPS for unicast is scrambled using the CS-RNTI. If the SPS configuration is applied to MBS, the PDSCH resources will be multicast and therefore scrambled using the group RNTI (G-RNTI) or some other cell-specific RNTI. However, there will be no useful way for the UE to distinguish between these two types of scrambling. In addition, the SPS concept is primarily defined for connected mode UEs and needs to be enhanced to support idle / inactive mode UEs.

[0050] SC-PTM with SC-MCCH / SC-MTCH configuration is defined in the LTE specification, for example, scheduled as part of System Information Block 30 (SIB20). Due to the physical layer enhancements inherently supported in 5G, a large amount of information provided in LTE, such as MBS frequency resources, scheduling information, PDCCH configuration, etc., may not be required in 5G.

[0051] Example embodiments of the present disclosure provide a scheme for, for example, group signaling of semi-persistent scheduling (SPS) information for a multicast broadcast service (MBS) service from a network device (e.g., a gNB) to terminal devices (e.g., UEs) interested in receiving the service. Using this scheme, at least one of enabling, disabling, or modifying an SPS configuration is determined for multiple devices on a bandwidth part (BWP) used for the MBS service and indicated to the multiple devices. Thus, multiple devices can determine whether to enable, modify, or disable the SPS configuration on the BWP. If it is determined that the SPS configuration is enabled, the device receives the MBS service on the BWP based on the SPS configuration.

[0052] Here, a bandwidth portion can be defined as an active bandwidth portion that can be defined as a set of frequency resources configured for a device or group of devices to which data and control information will be scheduled. A bandwidth portion has certain predefined characteristics, such as numerology, location of control and data channel resources, and semi-static or semi-persistent scheduling configuration, such as periodicity in the time domain.

[0053] In some example embodiments, existing SPS configurations per serving cell and BWP may be reused to map to MBS. In some other example embodiments, the SPS configuration may be determined as part of the G-RNTI configuration. This allows for efficient use of the SPS configuration for MBS.

[0054] Figure 3 An example environment 300 is shown in which example embodiments of the present disclosure may be implemented.

[0055] Environment 300 may be part of a communication network and include network device 305 and a set of terminal devices 310 - 1 . . . 310 -N (where N represents any suitable positive integer). For purposes of discussion, terminal devices 310 - 1 . . . 310 -N will be collectively or individually referred to as terminal devices 310 .

[0056] Communications between the terminal device 310 and the network device 305 and between the terminal devices 310 via the network device 305 may follow any suitable communication standards or protocols already in existence or to be developed in the future, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Fifth Generation (5G) New Radio (NR), Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and adopt any suitable communication technology, including, for example, Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth, ZigBee and Machine Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Ultra-Reliable Low Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC) and New Radio Unlicensed (NR-U) technology.

[0057] In the environment 300, the network device 105 may semi-persistently (or semi-statically), dynamically, or statically transmit MBS services to the group of terminal devices 310-1 ... 310-N. In some example embodiments, the network device 105 indicates to the terminal device 310 whether to enable, disable, or modify the SPS configuration for each BWP of the MBS service, so that the terminal device 110 may perform corresponding operations.

[0058] It should be understood that for illustration purposes only, Figure 3Network device 105 and terminal device 310 are shown as being included in environment 300, without intending to impose any limitation. In some example embodiments, MBS services may be communicated between multiple terminal devices. Therefore, the enabling, disabling, or modification of the SPS configuration for each BWP of an MBS service may be instructed from a transmitting terminal device to a group of receiving terminal devices. Alternatively, an MBS service may be transmitted, and the corresponding SPS configuration may be instructed from a relay to a group of terminal devices.

[0059] Figure 4 4 shows a flow chart of an example method 400 according to some example embodiments of the present disclosure. The method 400 may be performed by Figure 3 The network device 305 shown may be implemented by other devices that can transmit MBS services.

[0060] At block 405, at least one of enabling, disabling, or modifying SPS configuration is determined on a BWP for MBS service for a device group, such as the terminal device 310. At block 410, the enabling, disabling, or modifying of SPS configuration is indicated to the device group.

[0061] In some example embodiments, downlink control information (DCI) may be used to indicate the activation, disabling, or modification of an SPS configuration. For example, DCI sent using common frequency resources (CFR) on a BWP may include an index of an SPS configuration to indicate the activation of the SPS configuration. Thus, if a device obtains DCI on a CFR, the device may determine that the CFR is semi-persistently scheduled and, therefore, enable the SPS configuration with the index included in the DCI for MBS traffic on the BWP.

[0062] As described above, the resources on the BWP where the MBS service is scheduled are called CFRs. The MBS CFR can be identified on the receiving side by any suitable method that already exists or will be developed in the future. Currently, an SPS configuration can be provided for each BWP via RRC. The index of the SPS configuration can be used to identify each SPS configuration made for a specific BWP. In some example embodiments, one or more indices of the SPS configuration can be provided for the BWP where the MBS CFR is located. Then, a DCI containing the SPS configuration index is sent via PDCCH using a control resource set (CORESET) located within the MBS CFR to indicate that the SPS configuration is enabled on the MBS CFR for the MBS service.

[0063] Based on the current working assumption in 3GPP RAN1, GC-PDCCH signaling for GC-PDSCH is configured in the MBS CFR. Therefore, it is natural to assume that if the SPS activation message is not located within the MBS CFR, the DCI is not related to the MBS PDSCH, but rather to unicast services. In some example embodiments, some existing SPS configurations can be used or retained for MBS services.

[0064] Therefore, the current or existing SPS configuration per BWP can be reused for SPS for MBS. For example, in a scenario where a PDCCH for enabling SPS is scheduled using a CS-RNTI scrambled using a CORESET included in the MBS CFR, it can be indicated that the SPS configuration with the index included in the DCI is related to the MBS PDSCH. In other words, if the index of the SPS configuration to be activated is related to the MBS service, it means that the PDSCH data will be scrambled by the group common identifier (GC-RNTI).

[0065] The decision to configure SPS in an MBS BWP will depend on the network implementation. In some example embodiments, the possibility of SPS configuration for MBS services on the BWP can be indicated to the recipient in advance. This can be done by adding a new field or reusing an existing or reserved field in a signaling message, such as a Radio Resource Control (RRC) message, to indicate the SPS configuration.

[0066] In some example embodiments, the index of the SPS configuration associated with the BWP for the MBS service can be mapped to a corresponding group public identifier, such as a G-RNTI. These SPS configurations need to be synchronized across all devices receiving the same MBS service. For example, for a BWP, a group public identifier associated with the SPS configuration can be determined. In some example embodiments, a type of group public identifier can be configured for the SPS of the MBS. For example, for the use of SPS, a new type of group public identifier, such as a group common configuration scheduling-RNTI (GCS-RNTI), can be defined for the BWP that schedules the MBS CFR. The configuration of the mapped group public identifier can contain the index of the corresponding SPS configuration.

[0067] The association of a group public identifier and an SPS configuration may be indicated to devices that are to receive MBS services. For example, as part of the RRC signaling for the G-RNTI configuration, an additional new field may be added, or an existing or reserved field may be reused, to indicate the index of the corresponding SPS configuration. In some example embodiments, if the index of the SPS configuration is provided as part of the G-RNTI configuration, this indicates that the SPS configuration is enabled or activated for the MBS service.

[0068] In some example embodiments, DCI may be used to indicate the enabling, disabling, or modification of a corresponding SPS configuration. For example, a new or modified field may be included in the DCI to indicate whether the configuration indicated by the DCI is related to dynamic downlink or SPS scheduling of MBS services.

[0069] If a predefined GCS-RNTI is used, the DCI format can be similar to the CS-RNTI. For example, the Hybrid Automatic Repeat Request (HARQ) Process Identifier (ID) field can be used to indicate the index of the SPS configuration mapped to the group public identifier of the MBS service. If the DCI contains different indices for different SPS configurations, it can indicate that the SPS configuration of the MBS service is disabled or modified.

[0070] Depending on the specific implementation, the DCI may be scrambled using a dedicated identifier such as a CS-RNTI or a group common identifier such as a G-RNTI or a specific group common configuration scheduling-RNTI (GCS-RNTI) predefined for SPS of MBS. In some example embodiments, the CS-RNTI, G-RNTI or GCS-RNTI may be used for multicast services. For broadcast services, G-RNTI or GCS-RNTI may be used. In some example embodiments, if a device is joining or leaving an ongoing multicast session, a dedicated identifier such as a UE-specific CS-RNTI may be used to scramble the DCI to add or remove the device from the group of devices used to receive MBS services, or to remove the device from the group of devices.

[0071] The linking of the SPS configuration index and the MBS service can be implicit. For example, an SPS configuration can be initially provided for the BWP where the MBS CFR is located, and then an SPS activation message such as DCI is sent via PDCCH using the CORESET located within the MBS CFR. If the implicit linking between the SPS configuration index and the MBS service scheduling is standardized, a new rule needs to be specified in the standard to determine the UE's behavior. This rule may be related to which index of the activated SPS configuration is to be linked to the rule related to the MBS service, which means that the PDSCH data will be scrambled by the group common identity or GC-RNTI.

[0072] The following will refer to Figure 5 Discuss the implicit link example between the index of SPS configuration and MBS service. Figure 5 As shown, if an SPS activation message is received using a CORESET within an MBS CFR, such as a DCI containing an SPS configuration index, the existing SPS configuration of the BWP is linked to the MBS service. Explicit rules related to the RNTI used to decode the SPS activation message can be defined, whereby CS-RNTI, G-RNTI, or GCS-RNTI can be used depending on the configuration made by the network.

[0073] In some example embodiments, the SPS configuration for MBS services may be determined as a configuration for a group public identifier. For example, the SPS configuration may be defined as part of the G-RNTI configuration. The defined SPS configuration may exclude the index of the SPS configuration, as the G-RNTI is typically linked to the BWP that schedules the MBS service.

[0074] In some example embodiments, the SPS configuration as a configuration of a group public identifier may be broadcast in a predefined system information block (SIB). For example, a newly defined SIB may be used to indicate the SPS configuration so that all receivers are aware of the SPS configuration. An existing SIB may also be reused to broadcast the SPS configuration as a configuration of a group public identifier.

[0075] The SPS configuration can be enabled or activated using a PDCCH scrambled with a group public identifier such as a G-RNTI or GCS-RNTI. For example, the DCI is scrambled with the group public identifier to indicate the enabling or activation of the SPS configuration. This information can be sent using an existing DCI format such as DCI format 1_x or a newly defined DCI format. Since the index of the SPS configuration index may not be required, the number of SPS configurations for unicast may not be limited, thereby improving the utilization of the SPS configuration for unicast.

[0076] In this way, for example, the SPS framework can be incorporated into the G-RNTI configuration via RRC signaling. This gives the network the flexibility to decide whether to use dynamic scheduling or semi-persistent scheduling for a particular MBS service. For example, a static association between the G-RNTI and the SPS configuration can be defined. In this case, if the G-RNTI configuration maps to the SPS configuration, the network is assumed to always use the SPS configuration to schedule MBS services associated with the G-RNTI. This association can also be changed dynamically.

[0077] An example SPS configuration is discussed below. In this example, the SC-PTM RRC configuration (including G-RNTI) performed in Rel-13 is enhanced to define an SPS configuration for MBS services.

[0078]

[0079] The SPS configuration details may be appended to the G-RNTI configuration in the RRC message:

[0080] -nrofHARQ-Processes: number of HARQ processes configured for SPS;

[0081] -harq-ProcID-Offset: offset of the HARQ process used for SPS;

[0082] -periodicity: Configures the periodicity of downlink allocation for SPS.

[0083] - Possible GCS-RNTI configurations

[0084] This will enable the receiver to understand that this particular G-RNTI utilizes SPS instead of dynamic scheduling and reception of GC-PDCCH, where scrambling of the Cyclic Redundancy Check (CRC) by this particular G-RNTI would imply activation of the SPS configuration provided as part of the G-RNTI RRC configuration.

[0085] Different implementation options for SPS configuration of MBS services can be switched based on the service profile and / or state of the device receiving a particular MBS service. For example, an option can be selected based on the state of the receiver (e.g., connected mode or idle or inactive mode), the unicast service received by the receiver, and the type of MBS service (multicast or broadcast service).

[0086] In some example embodiments, when a device is in connected mode, it may receive an indication of enabling, disabling, or modifying an SPS configuration. When the device enters idle or inactive mode, the device may maintain the SPS configuration. The device may continue to monitor the PDCCH for possible modifications and / or disabling of the SPS configuration. For example, a device in idle or inactive mode may monitor the PDCCH based on an appropriate CS-RNTI, G-RNTI, or GCS-RNTI to receive SPS activation, modification, and deactivation messages.

[0087] In some example embodiments, as part of the SPS configuration, the network may also indicate to the MSB receiver whether the SPS configuration will be used after transitioning from connected mode (e.g., RRC connected mode) to idle or inactive mode. For example, a new flag within the configuration may be used to indicate to the device the validity of the SPS configuration after transitioning to idle or inactive mode. If the device only receives SPS MBS services, the device may transition to idle or inactive mode. In the idle / active state, the device may maintain the scheduling information received in the connected state and receive MBS services accordingly. Devices receiving multicast services may need to monitor CS-RNTI, G-RNTI, or GCS-RNTI, while UEs receiving broadcast services will only need to monitor G-RNTI or GCS-RNTI.

[0088] Although receive-only mode (ROM) UEs are not supported in the current release of 5G or NR, idle or inactive mode UEs may still receive MBS configuration information after entering the connected state. In the event that ROM UEs are supported in future releases, the SPS configuration for connected UEs can also be directly extended for such UEs. This extension can be achieved (a) using pre-configuration of SPS and related RNTIs, or (b) using broadcast signaling configured by RRC, so that UEs can receive SPS activation, modification, and deactivation messages via DCI.

[0089] Figure 6 6 shows a flow chart of an example method 600 according to some example embodiments of the present disclosure. The method 600 may be performed by Figure 3 The terminal device 310 shown may be implemented by other devices that can receive MBS services.

[0090] In block 605, it is determined whether the SPS configuration is enabled, modified, or disabled for the MBS service on the BWP. In some example embodiments, the enabling, disabling, or modification of the SPS configuration may be determined based on the DCI. For example, the device may perform blind decoding of the DCI on the BWP using at least one of a dedicated identifier (e.g., CS-RNTI) and a group public identifier (e.g., G-RNTI or GCS-RNTI). If the DCI is decoded, it may be determined based on the DCI whether the SPS configuration is enabled, modified, or disabled. As an example, if the DCI is received on the CFR on the BWP, it may be determined that the SPS configuration is enabled. That is, the CFR is semi-statically or semi-persistently scheduled.

[0091] In some example embodiments, the possibility of an SPS configuration being used for MBS traffic on a BWP may be pre-received. This possibility may be indicated by a new field, or by reusing an existing or reserved field within an RRC message to signal the SPS configuration. Thus, the UE may utilize a rule, such as one configured as part of the G-RNTI configuration, to assume that the SPS configuration is associated with an MBS PDSCH.

[0092] In some example embodiments, the association between the SPS configuration and the group public identifier for the BWP may be predefined or pre-established. Thus, the device may determine whether to enable, disable, or modify the SPS configuration based on the association. For example, the index of the SPS configuration associated with the BWP for the MBS service may be mapped to a corresponding group public identifier, such as a G-RNTI or GCS-RNTI. If the index of the SPS configuration is provided as part of the G-RNTI configuration, the device may assume that the SPS configuration is enabled or activated using the G-RNTI.

[0093] In some example embodiments, if the device decodes a DCI containing an index of an SPS configuration, the device may determine that the SPS configuration is enabled. If the decoded DCI contains different indexes of different SPS configurations, the device may determine that the SPS configuration is disabled or modified.

[0094] As an example, once a device receives a CS-RNTI, an SPS configuration, and a G-RNTI with an optional index of the mapped SPS configuration on an MBS BWP where SPS is configured and linked to a G-RNTI, the device may have two options for using DCI format 1_x scrambled by either the CS-RNTI or the G-RNTI to determine the enablement or activation of the SPS configuration. This means that the device needs to blindly decode format 1_x using either the CS-RNTI or the G-RNTI. New, modified, or even reused fields may be included in the DCI to indicate whether the configuration is related to dynamic downlink or SPS scheduling of MBS services.

[0095] In some example embodiments, one or more SPS configurations may be defined as part of the G-RNTI configuration. The SPS configuration may be received in a predefined SIB. The enabling or activation of the SPS configuration may be indicated by a PDCCH scrambled with the G-RNTI or GCS-RNTI. Therefore, if the UE is configured with this information, the device needs to monitor the MBS-related DCI formats at the configured monitoring opportunities, where the CRC of the DCI assumes scrambling with the G-RNTI or GCS-RNTI. This information may be sent using DCI format 1_x or a newly defined MBS DCI format. In addition, the device may expect an appropriate format of the DCI including a size estimate based on the configured RNTI and depending on whether the device expects dynamic and / or semi-persistent scheduling of MBS services. Once the device receives the DCI, the device may enable or disable the SPS configuration in any appropriate process that already exists or will be developed in the future.

[0096] If it is determined at block 605 that the SPS configuration is enabled, then at block 610, the MBS service is received on the bandwidth portion based on the SPS configuration. In some example embodiments, the device may determine the period of the MBS service based on the SPS configuration and then periodically receive the MBS service on the bandwidth portion using CFR. Detection of the MBS service may utilize a dedicated identifier such as a CS-RNTI or a group public identifier such as a G-RNTI or GCS-RNTI.

[0097] The following will refer to Figures 7 to 9 Some example embodiments of receiving MBS services are discussed, where the UE acts as a device interested in receiving the MBS services, and the gNB acts as a device that schedules SPS for the MBS services.

[0098] Figure 7An example process 700 of multiplexing a current SPS framework and configuring a configuration for configuring SPS for MBSPDSCH according to some example embodiments of the present disclosure is shown.

[0099] like Figure 7 As shown, process 700 begins at block 705. At block 710, the UE determines whether the CS-RNTI is configured as part of the physical cell group configuration. If not, process 700 proceeds to block 715, where process 700 follows the dynamic scheduling process, and then stops at block 720. If, at block 710, it is determined that the CS-RNTI is configured as part of the physical cell group configuration, process 700 proceeds to block 725, where the UE determines whether an SPS configuration is available for the current BWP or active BWP. If not, process 700 proceeds to block 715 to follow the dynamic scheduling process. If yes, at block 730, it is determined whether the SPS configuration index n in the BWP is linked to a G-RNTI. If not, process 700 proceeds to block 715. If yes, at block 735, the UE attempts to perform blind decoding of DCI format 1_x using both the CS-RNTI and the G-RNTI.

[0100] Then, at block 740, a determination is made as to whether the DCI was received with a CRC scrambled by the CS-RNTI or G-RNTI. If not, the process 700 follows the dynamic scheduling process at block 715. If so, the process 700 proceeds to block 745, where a determination is made as to whether the DCI enables SPS with configuration index n. If so, at block 750, the UE begins monitoring the MBS PDSCH with a CRC scrambled by the cell-RNTI or G-RNTI and with the period configured in the SPS configuration with index n and the DCI-based resources. The process 700 then stops at block 720. If it is determined at block 745 that the DCI does not enable SPS with configuration index n, the process 700 proceeds to block 755, where the UE disables PDSCH monitoring for the SPS configuration with index n based on the DCI, and the process 700 then stops at block 720.

[0101] If the UE is configured with a CS-RNTI as part of the cell group configuration for a BWP where MBS CFR is scheduled by a GNB, a new configuration parameter is proposed as part of the G-RNTI RRC configuration to map a specific SPS configuration index to the G-RNTI. Based on this mapping, the UE can interpret that the SPS configuration is related to the MBS PDSCH - where the PDSCH is scrambled with a group common identity (e.g., G-RNTI). The SPS configuration can also be enabled using a PDCCH scrambled with a group common identity (e.g., G-RNTI, also known as GC-PDCCH). If GC-PDCCH is used, it is assumed that the DCI format is modified to indicate to the UE that the DCI is related to SPS activation compared to dynamic scheduling. Even for the option where the group common RNTI is used to activate SPS, it is beneficial to still use the CS-RNTI for UE-specific modifications, especially in scenarios where new UEs join the group.

[0102] Figure 8 An example process 800 for G-RNTI-based semi-persistent scheduling configuration according to some example embodiments of the present disclosure is shown. In process 800, a static association between the G-RNTI and the SPS configuration is considered, whereby if the G-RNTI is mapped to the SPS configuration, the network is assumed to always use SPS to schedule MBS traffic associated with the G-RNTI.

[0103] like Figure 8 As shown, process 800 begins at block 805. At block 810, the UE is configured with a G-RNTI and associated SPS configuration. At block 815, a determination is made as to whether the SPS configuration is available for the current BWP or the active BWP. If not, process 800 follows the dynamic scheduling process at block 820 and then stops at block 825. If yes, at block 830, the UE attempts to perform blind decoding of DCI format 1_x using the G-RNTI.

[0104] Then, at block 835, a determination is made as to whether the DCI is received using a CRC scrambled by the CS-RNTI or G-RNTI. If not, the process 800 proceeds to block 820 to follow the dynamic scheduling process. If so, the process 800 proceeds to block 840, where it is determined whether the DCI enables the SPS associated with the G-RNTI. If so, at block 845, the UE begins monitoring the MBS PDSCH using a CRC scrambled by the cell-RNTI or G-RNTI and using the period configured in the SPS configuration with index n and the DCI-based resources. The process 800 then stops at block 825. If not, the process 800 proceeds to block 850, where the UE disables PDSCH monitoring for the SPS configuration with index n based on the DCI, and the process 800 then stops at block 825.

[0105] The use of GCS-RNTI and G-RNTI for dynamic and semi-persistent scheduling of MBS services can be as follows: Figure 9 Process 900 is shown where the network may configure two scheduling types based on the RNTI used.

[0106] Figure 9 An example process 900 for dynamic and semi-persistent scheduling with G-RNTI and GCS-RNTI is shown according to some example embodiments of the present disclosure.

[0107] like Figure 9 As shown, process 900 starts at block 905. At block 910, it is determined whether G-RNTI and GCS-RNTI are configured. If so, at block 915, the UE attempts to perform blind decoding of format 1_x using G-RNTI and GCS-RNTI, and enables SPS configuration if DCI scrambled with GCS-RNTI is received. Then, process 900 stops at block 920.

[0108] If, at block 910, it is determined that the G-RNTI and GCS-RNTI are not configured, then at block 925, the UE determines whether an SPS configuration is available for the current or active BWP. If not, process 900 follows the dynamic scheduling process at block 930 and then stops at block 920. If yes, then at block 935, the UE attempts to perform blind decoding of format 1_x using the G-RNTI and uses the DCI to check for SPS configuration activation. At block 940, the UE begins monitoring the MBS PDSCH using a CRC scrambled by the cell-RNTI or G-RNTI and using the period configured in the SPS configuration with index n and DCI-based resources. Process 900 then stops at block 920.

[0109] In some example embodiments, a device receives an indication related to an SPC configuration for MBS services in connected mode. For example, a device may receive the configuration in connected mode while maintaining the configuration in idle or inactive mode. In some example embodiments, the SPS configuration may include an indication of whether to use the semi-persistent scheduling configuration after transitioning from connected mode to idle or inactive mode. For example, if the device only receives SPS services, the network may use a new flag within the configuration to indicate to the device whether the semi-persistent scheduling configuration is valid after transitioning from RRC connected mode to idle or inactive mode.

[0110] In idle or inactive mode, the device needs to continue monitoring the PDCCH for possible modifications and / or disabling of the SPS configuration. For example, the device may monitor the PDCCH based on the appropriate CS-RNTI, G-RNTI, or GCS-RNTI to receive SPS activation, modification, and deactivation messages. For example, if the device is receiving a multicast service, the device may need to monitor the CS-RNTI, G-RNTI, or GCS-RNTI. If the device is receiving a broadcast service, the device may only need to monitor the G-RNTI or GCS-RNTI. In some example embodiments, the device may perform blind decoding of the DCI on the BWP using the CS-RNTI, G-RNTI, or GCS-RNTI. If the DCI is decoded, the device can determine whether the SPS configuration is modified or disabled.

[0111] Figure 10 An example state transition process 1000 according to some example embodiments of the present disclosure is shown. In this example, the UE acts as a device interested in receiving MBS services, and the gNB acts as a device that schedules SPS for MBS services.

[0112] like Figure 10 As shown, process 1000 begins at block 1005. At block 1010, a determination is made as to whether the SPS configuration is available for the current BWP or active BWP. If not, process 1000 follows the dynamic scheduling process at block 1015 and then stops at block 1020. If so, at block 1030, a determination is made as to whether the validity flag after state transition is enabled. If not, process 1000 follows the dynamic scheduling process at block 1015. If so, at block 1035, the UE stores the MBS SPS configuration and maintains the configuration while in idle or inactive mode. Process 1000 then stops at block 1020.

[0113] like Figure 10 The state transition process shown may enable the UE to store the SPS scheduling information received in the connected state. After transitioning to the idle or inactive state, the UE may continue to use the stored scheduling information to receive MBS services.

[0114] refer to Figures 3 to 5 All operations and functions described are also applicable to the method 600 and processes 700 to 1000 and have similar effects. For the sake of simplicity, details will be omitted.

[0115] Figure 11 1 is a simplified block diagram of a device 1100 suitable for implementing an exemplary embodiment of the present disclosure. The device 1100 may be implemented at a sender or receiver of an MBS service. As an example, the device 110 may be implemented at or as part of a network device 305 or a terminal device 310, such as Figure 3 shown.

[0116] As shown, device 1100 includes a processor 1110, a memory 1120 coupled to processor 1110, a communication module 1130 coupled to processor 1110, and a communication interface (not shown) coupled to communication module 1130. Memory 1120 stores at least a program 1140. Communication module 1130 is configured to perform bidirectional communication, for example, via multiple antennas. The communication interface may represent any interface necessary for communication.

[0117] Assume that the program 1140 includes program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with example embodiments of the present disclosure, as referred to herein. Figures 3 to 10 The example embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various example embodiments of the present disclosure.

[0118] Memory 1120 can be of any type suitable for the local technology network and can be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 1120 is shown in device 1100, several physically distinct memory modules may be present in device 1100. Processor 1110 can be of any type suitable for the local technology network and can include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor, and a processor based on a multi-core processor architecture. Device 1100 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock that synchronizes a master processor.

[0119] When the device 1100 functions as a network device 305 or as part of a network device 305, the processor 1110 and the communication module 1130 may cooperate to implement the aforementioned Figures 3 to 5 When the device 1100 acts as a terminal device 310 or a part of the terminal device 310, the processor 1110 and the communication module 1130 can cooperate to implement the method 400 described above. Figures 6 to 10 The method 600 is described above. Figures 3 to 10 All operations and functions described above are also applicable to the device 1100 and have similar effects. For the sake of simplicity, the details will be omitted.

[0120] In general, various example embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the exemplary embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other pictorial representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0121] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in a program module, which are executed in a device on a target real or virtual processor to perform the above-mentioned reference Figures 3 to 10 Method 400 or 600 described herein. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, and the like that perform specific tasks or implement specific abstract data types. In various exemplary embodiments, the functionality of program modules can be combined or split between program modules as needed. The machine-executable instructions of program modules can be executed on local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0122] The program code for performing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when executed by the processor or controller, the program code enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, as a separate software package, partially on the machine, partially on a remote machine, or entirely on a remote machine or server.

[0123] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals and computer-readable media.

[0124] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination thereof. More specific examples of computer readable storage media would include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0125] In addition, although operations are described in a particular order, this should not be understood as requiring that the operations be performed in the particular order or sequence shown, or that all of the operations shown be performed, to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to a particular example embodiment. Certain features described in the context of a separate example embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple example embodiments individually or in any appropriate subcombination.

[0126] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0127] Various example embodiments of the technology have been described. In addition to or as an alternative to the above, the following examples are described. Features described in any of the following examples can be used with any other examples described herein.

[0128] In some aspects, a device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: determine at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a device group on a bandwidth portion used for a multicast broadcast service; and indicate to the device group at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the bandwidth portion.

[0129] In some example embodiments, the device is configured to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration by sending downlink control information on the bandwidth to at least the devices in the device group to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

[0130] In some example embodiments, the device is configured to send the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration by sending the downlink control information using common frequency resources on the bandwidth portion, the downlink control information including an index of the semi-persistent scheduling configuration to indicate enabling of the semi-persistent scheduling configuration.

[0131] In some example embodiments, the multicast broadcast service includes a multicast service, and the device is configured to send the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration by: scrambling the downlink control information using a dedicated identifier; and sending the scrambled downlink control information to at least the devices in the device group on the bandwidth to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

[0132] In some example embodiments, the device is further configured to send an indication to the group of devices of a likelihood that the semi-persistent scheduling configuration is used for the multicast broadcast service traffic on the bandwidth portion.

[0133] In some example embodiments, the device is further configured to: determine, for the bandwidth portion, a group public identifier associated with the semi-persistent scheduling configuration; and indicate the association of the group public identifier with the semi-persistent scheduling configuration to the devices in the device group.

[0134] In some example embodiments, the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

[0135] In some example embodiments, the device is configured to indicate the association between the group public identifier and the semi-persistent scheduling configuration by sending an index of the semi-persistent scheduling configuration to at least the devices in the device group in the configuration for the group public identifier to indicate the association between the group public identifier and the semi-persistent scheduling configuration.

[0136] In some example embodiments, the device is configured to send the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration in the following manner: sending the downlink control information to at least the devices in the device group on the bandwidth, the downlink control information including an index of the semi-persistent scheduling configuration to indicate enabling of the semi-persistent scheduling configuration.

[0137] In some example embodiments, the device is configured to send the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration in the following manner: sending the downlink control information to at least the devices in the device group on the bandwidth, the downlink control information including different indexes of different semi-persistent scheduling configurations to indicate disabling or modifying the semi-persistent scheduling configuration.

[0138] In some example embodiments, the device is configured to determine the group public identity associated with the semi-persistent scheduling configuration by determining the semi-persistent scheduling configuration as a configuration for the group public identity.

[0139] In some example embodiments, the device is configured to indicate the association of the group common identity and the semi-persistent scheduling configuration by broadcasting the semi-persistent scheduling configuration to the device group as a configuration for the group common identity in a predefined system information block.

[0140] In some example embodiments, the device is configured to send the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration by: scrambling the downlink control information using the group public identifier; and sending the scrambled downlink control information to at least the devices in the device group on the bandwidth to indicate enabling of the semi-persistent scheduling configuration.

[0141] In some example embodiments, the semi-persistent scheduling configuration includes an indication for transitioning from a connected mode to an idle or inactive mode.

[0142] In some aspects, a device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: determine whether a semi-persistent scheduling configuration is enabled, modified, or disabled on a bandwidth portion used for a multicast broadcast service service; and based on a determination that the semi-persistent scheduling configuration is enabled, receive the multicast broadcast service service on the bandwidth portion based on the semi-persistent scheduling configuration.

[0143] In some example embodiments, the device is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled by: blindly decoding downlink control information on a bandwidth portion using at least one of a dedicated identifier and a group common identifier; and in response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information.

[0144] In some example embodiments, the device is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: determining that the semi-persistent scheduling configuration is enabled in response to the downlink control information being received on a common frequency resource on the bandwidth portion.

[0145] In some example embodiments, the apparatus is further configured to receive an indication of a likelihood that the semi-persistent scheduling configuration is used for the multicast broadcast service traffic on the bandwidth portion.

[0146] In some example embodiments, the apparatus is further configured to receive an indication of an association between the group common identity of the bandwidth portion and the semi-persistent scheduling configuration.

[0147] In some example embodiments, the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

[0148] In some exemplary embodiments, the device is configured to receive the indication of the association between the group public identity and the semi-persistent scheduling configuration by: receiving an index of the semi-persistent scheduling configuration in a configuration for the group public identity.

[0149] In some example embodiments, the device is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: determining that the semi-persistent scheduling configuration is enabled in response to the decoded downlink control information containing the index of the semi-persistent scheduling configuration.

[0150] In some example embodiments, the device is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: determining that the semi-persistent scheduling configuration is disabled or modified in response to the decoded downlink control information containing different indexes of different semi-persistent scheduling configurations.

[0151] In some example embodiments, the apparatus is configured to receive an indication of an association between the group common identity and the semi-persistent scheduling configuration by receiving the semi-persistent scheduling configuration as a configuration of the group common identity in a predefined system information block.

[0152] In some example embodiments, the device is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by determining that the semi-persistent scheduling configuration is enabled in response to the downlink control information being decoded using the group common identifier.

[0153] In some example embodiments, the semi-persistent scheduling configuration includes an indication for transitioning from a connected mode to an idle or inactive mode.

[0154] In some example embodiments, the device is configured to receive the multicast broadcast service on the bandwidth portion by: determining a period of the multicast broadcast service based on the semi-persistent scheduling configuration; and periodically receiving the multicast broadcast service using common frequency resources on the bandwidth portion.

[0155] In some example embodiments, the device is configured to receive the multicast broadcast service using the common frequency resources on the bandwidth portion by periodically detecting the multicast broadcast service using at least one of a dedicated identifier and a group common identifier using the common frequency resources on the bandwidth portion.

[0156] In some example embodiments, the device is in a connected mode.

[0157] In some example embodiments, the device is further configured to, in an idle or inactive mode: perform blind decoding of downlink control information on the bandwidth portion using at least one of a dedicated identifier and a group common identifier; and determine, in response to the downlink control information being decoded, whether the semi-persistent scheduling configuration is modified or disabled based on the downlink control information.

[0158] In some aspects, a method includes determining at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a device group on a portion of bandwidth used for a multicast broadcast service operation; and indicating to the device group at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the portion of bandwidth.

[0159] In some example embodiments, indicating at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes sending downlink control information on the bandwidth to at least devices in the device group to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

[0160] In some example embodiments, sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes sending the downlink control information using common frequency resources on the bandwidth portion, the downlink control information including an index of the semi-persistent scheduling configuration to indicate enabling of the semi-persistent scheduling configuration.

[0161] In some example embodiments, the multicast broadcast service business includes a multicast business, and sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes: scrambling the downlink control information using a dedicated identifier; and sending the scrambled downlink control information to at least the devices in the device group on the bandwidth to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

[0162] In some example embodiments, the method further comprises sending an indication to the group of devices of a likelihood that the semi-persistent scheduling configuration will be used for the multicast broadcast service traffic on the bandwidth portion.

[0163] In some example embodiments, the method further comprises: determining, for the bandwidth portion, a group public identity associated with the semi-persistent scheduling configuration; and indicating the association of the group public identity and the semi-persistent scheduling configuration to the devices of the device group.

[0164] In some example embodiments, the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

[0165] In some example embodiments, indicating the association between the group public identifier and the semi-persistent scheduling configuration includes: sending an index of the semi-persistent scheduling configuration to at least the device in the device group that is in the configuration for the group public identifier to indicate the association between the group public identifier and the semi-persistent scheduling configuration.

[0166] In some example embodiments, sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes sending the downlink control information to at least the devices in the device group on the bandwidth, the downlink control information including an index of the semi-persistent scheduling configuration to indicate enabling of the semi-persistent scheduling configuration.

[0167] In some example embodiments, sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes sending the downlink control information to at least the devices in the device group on the bandwidth, the downlink control information including different indexes of different semi-persistent scheduling configurations to indicate disabling or modifying the semi-persistent scheduling configuration.

[0168] In some example embodiments, determining the group public identity associated with the semi-persistent scheduling configuration includes determining the semi-persistent scheduling configuration as a configuration for the group public identity.

[0169] In some example embodiments, indicating the association of the group public identity and the semi-persistent scheduling configuration includes broadcasting the semi-persistent scheduling configuration to the device group as a configuration for the group public identity in a predefined system information block.

[0170] In some example embodiments, sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes: scrambling the downlink control information using the group public identifier; and sending the scrambled downlink control information to at least the devices in the device group on the bandwidth to indicate enabling of the semi-persistent scheduling configuration.

[0171] In some example embodiments, the semi-persistent scheduling configuration includes an indication of whether the semi-persistent scheduling configuration is to be used after transitioning from connected mode to idle or inactive mode.

[0172] In some aspects, a method includes determining whether a semi-persistent scheduling configuration is enabled, modified, or disabled on a portion of a bandwidth used for a multicast broadcast service; and receiving the multicast broadcast service on the bandwidth portion based on the semi-persistent scheduling configuration in accordance with a determination that the semi-persistent scheduling configuration is enabled.

[0173] In some example embodiments, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled includes: blindly decoding downlink control information on a bandwidth portion using at least one of a dedicated identifier and a group common identifier; and in response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information.

[0174] In some example embodiments, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes: in response to receiving the downlink control information on common frequency resources on the bandwidth portion, determining that the semi-persistent scheduling configuration is enabled.

[0175] In some example embodiments, the method further comprises receiving an indication of a likelihood that the semi-persistent scheduling configuration is used for the multicast broadcast service traffic on the bandwidth portion.

[0176] In some example embodiments, the method further comprises receiving an indication of an association between the group common identity of the bandwidth portion and the semi-persistent scheduling configuration.

[0177] In some example embodiments, the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

[0178] In some example embodiments, receiving an indication of an association between the group public identity and the semi-persistent scheduling configuration includes receiving an index of the semi-persistent scheduling configuration in a configuration for the group public identity.

[0179] In some example embodiments, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes: in response to the decoded downlink control information including the index of the semi-persistent scheduling configuration, determining that the semi-persistent scheduling configuration is enabled.

[0180] In some example embodiments, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes: in response to the decoded downlink control information containing different indexes of different semi-persistent scheduling configurations, determining that the semi-persistent scheduling configuration is disabled or modified.

[0181] In some example embodiments, receiving an indication of an association between the group common identity and the semi-persistent scheduling configuration includes receiving the semi-persistent scheduling configuration as a configuration for the group common identity in a predefined system information block.

[0182] In some example embodiments, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes determining that the semi-persistent scheduling configuration is enabled in response to the downlink control information being decoded using the group common identity.

[0183] In some example embodiments, the semi-persistent scheduling configuration includes an indication of whether the semi-persistent scheduling configuration is to be used after transitioning from connected mode to idle or inactive mode.

[0184] In some example embodiments, receiving the multicast broadcast service on the bandwidth portion includes: determining a period of the multicast broadcast service based on the semi-persistent scheduling configuration; and periodically receiving the multicast broadcast service using common frequency resources on the bandwidth portion.

[0185] In some example embodiments, receiving the MBS service using the common frequency resources on the bandwidth portion includes periodically detecting the MBS service using the common frequency resources on the bandwidth portion with at least one of a dedicated identifier and a group common identifier.

[0186] In some example embodiments, the method is implemented by a device in connected mode.

[0187] In some example embodiments, the method further includes: in an idle or inactive mode, blindly decoding downlink control information on the bandwidth portion using at least one of a dedicated identifier and a group common identifier; and in response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is modified or disabled based on the downlink control information.

[0188] In some aspects, an apparatus includes: means for determining at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a portion of bandwidth used for a multicast broadcast service operation; and means for indicating to the group of devices at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the portion of bandwidth.

[0189] In some example embodiments, the means for indicating at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes means for sending downlink control information on the bandwidth to at least a device in the device group to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

[0190] In some example embodiments, the means for sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes: means for sending the downlink control information using common frequency resources on the bandwidth portion, the downlink control information including an index of the semi-persistent scheduling configuration to indicate enabling of the semi-persistent scheduling configuration.

[0191] In some example embodiments, the multicast broadcast service business includes a multicast business, and the component for sending the downlink control information to indicate at least one of enabling, disabling or modifying the semi-persistent scheduling configuration includes: a component for scrambling the downlink control information using a dedicated identifier; and a component for sending the scrambled downlink control information on the bandwidth to at least the devices in the device group to indicate at least one of enabling, disabling or modifying the semi-persistent scheduling configuration.

[0192] In some example embodiments, the apparatus further comprises means for sending, to the group of devices, an indication of a likelihood that the semi-persistent scheduling configuration will be used for the multicast broadcast service traffic on the bandwidth portion.

[0193] In some example embodiments, the apparatus further comprises: means for determining, for the bandwidth portion, a group public identifier associated with the semi-persistent scheduling configuration; and means for indicating the association of the group public identifier with the semi-persistent scheduling configuration to the devices in the device group.

[0194] In some example embodiments, the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

[0195] In some example embodiments, the component for indicating the association between the group public identifier and the semi-persistent scheduling configuration includes: a component for sending an index of the semi-persistent scheduling configuration to at least the devices in the device group in the configuration for the group public identifier to indicate the association between the group public identifier and the semi-persistent scheduling configuration.

[0196] In some example embodiments, the means for sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes: means for sending the downlink control information to at least the devices in the device group on the bandwidth, the downlink control information including an index of the semi-persistent scheduling configuration to indicate enabling of the semi-persistent scheduling configuration.

[0197] In some example embodiments, the means for sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes: means for sending the downlink control information to at least the devices in the device group on the bandwidth, the downlink control information including different indexes of different semi-persistent scheduling configurations to indicate disabling or modifying the semi-persistent scheduling configuration.

[0198] In some example embodiments, the means for determining the group public identity associated with the semi-persistent scheduling configuration includes means for determining the semi-persistent scheduling configuration as a configuration for the group public identity.

[0199] In some example embodiments, the means for indicating the association of the group public identity and the semi-persistent scheduling configuration comprises means for broadcasting the semi-persistent scheduling configuration to the device group as a configuration for the group public identity in a predefined system information block.

[0200] In some example embodiments, the component for sending the downlink control information to indicate at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration includes: a component for scrambling the downlink control information using the group public identifier; and a component for sending the scrambled downlink control information to at least the devices in the device group on the bandwidth to indicate the enabling of the semi-persistent scheduling configuration.

[0201] In some example embodiments, the semi-persistent scheduling configuration includes an indication for transitioning from a connected mode to an idle or inactive mode.

[0202] In some aspects, an apparatus includes: a component for determining whether a semi-persistent scheduling configuration is enabled, modified, or disabled on a bandwidth portion for a multicast broadcast service service; and a component for receiving the multicast broadcast service service on the bandwidth portion based on the semi-persistent scheduling configuration in accordance with a determination that the semi-persistent scheduling configuration is enabled.

[0203] In some example embodiments, the means for determining whether to enable, modify, or disable the semi-persistent scheduling configuration includes: means for blindly decoding downlink control information on a bandwidth portion using at least one of a dedicated identifier and a group common identifier; and means for determining, in response to the downlink control information being decoded, whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information.

[0204] In some example embodiments, the means for determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes means for determining that the semi-persistent scheduling configuration is enabled in response to the downlink control information being received on common frequency resources on the bandwidth portion.

[0205] In some example embodiments, the apparatus further comprises means for receiving an indication of a likelihood that the semi-persistent scheduling configuration is used for the multicast broadcast service traffic on the bandwidth portion.

[0206] In some example embodiments, the apparatus further comprises means for receiving an indication of an association between the group common identity of the bandwidth portion and the semi-persistent scheduling configuration.

[0207] In some example embodiments, the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

[0208] In some example embodiments, the means for receiving an indication of an association between the group public identity and the semi-persistent scheduling configuration comprises means for receiving an index of the semi-persistent scheduling configuration in a configuration for the group public identity.

[0209] In some example embodiments, the means for determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes means for determining that the semi-persistent scheduling configuration is enabled in response to the decoded downlink control information including the index of the semi-persistent scheduling configuration.

[0210] In some example embodiments, the means for determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes means for determining that the semi-persistent scheduling configuration is disabled or modified in response to the decoded downlink control information containing different indices of different semi-persistent scheduling configurations.

[0211] In some example embodiments, the means for receiving an indication of an association between the group common identity and the semi-persistent scheduling configuration comprises means for receiving the semi-persistent scheduling configuration as a configuration of the group common identity in a predefined system information block.

[0212] In some example embodiments, the means for determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information includes means for determining that the semi-persistent scheduling configuration is enabled in response to the downlink control information being decoded using the group common identifier.

[0213] In some example embodiments, the semi-persistent scheduling configuration includes an indication for transitioning from a connected mode to an idle or inactive mode.

[0214] In some example embodiments, the component for receiving the multicast broadcast service service on the bandwidth portion includes: a component for determining the period of the multicast broadcast service service based on the semi-persistent scheduling configuration; and a component for periodically receiving the multicast broadcast service service using common frequency resources on the bandwidth portion.

[0215] In some example embodiments, the means for receiving the multicast broadcast service using the common frequency resources on the bandwidth portion includes means for periodically detecting the multicast broadcast service using the common frequency resources on the bandwidth portion using at least one of a dedicated identifier and a group common identifier.

[0216] In some example embodiments, the apparatus is implemented by a device in a connected mode.

[0217] In some example embodiments, the apparatus further comprises: means for blindly decoding downlink control information on the bandwidth portion using at least one of a dedicated identifier and a group common identifier in an idle or inactive mode; and means for determining, in response to the downlink control information being decoded, whether the semi-persistent scheduling configuration is modified or disabled based on the downlink control information.

[0218] In some aspects, a computer-readable storage medium includes program instructions stored thereon, which, when executed by a processor of a device, cause the device to perform methods according to some example embodiments of the present disclosure.

Claims

1. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: determining at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a portion of a bandwidth used for multicast broadcast service traffic; as well as Indicating at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the bandwidth portion to the device group, wherein the device is configured to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration by: Using common frequency resources on the bandwidth portion, downlink control information is sent to at least the devices in the device group to indicate at least one of enabling, disabling or modifying the semi-persistent scheduling configuration, wherein the downlink control information includes an index of the semi-persistent scheduling configuration to indicate the enabling of the semi-persistent scheduling configuration.

2. The apparatus according to claim 1 , wherein the MPSS service comprises a multicast service, and the apparatus is configured to send the downlink control information to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration in the following manner: Scrambling the downlink control information using a dedicated identifier; and Scrambled downlink control information is sent to at least the devices in the device group on the bandwidth to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

3. The device according to claim 1, wherein the device is further configured to: An indication of a likelihood that the semi-persistent scheduling configuration may be used for the multicast broadcast service traffic on the bandwidth portion is sent to the group of devices.

4. The device according to claim 1, wherein the device is further configured to: determining, for the bandwidth portion, a group public identifier associated with the semi-persistent scheduling configuration; and An association of the group public identity with the semi-persistent scheduling configuration is indicated to the devices in the device group. The device according to claim 4 , wherein the group public identity is a group public identity of a type configured for semi-persistent scheduling of a multicast broadcast service.

6. The device according to claim 4 or 5, wherein the device is configured to indicate the association between the group public identity and the semi-persistent scheduling configuration in the following manner: In the configuration for the group public identifier, an index of the semi-persistent scheduling configuration is sent to at least the devices in the device group to indicate the association between the group public identifier and the semi-persistent scheduling configuration.

7. The apparatus according to claim 6, wherein the apparatus is configured to send the downlink control information to indicate the at least one of activation, deactivation, or modification of the semi-persistent scheduling configuration in the following manner: The downlink control information is sent to at least the devices in the device group on the bandwidth, wherein the downlink control information includes the index of the semi-persistent scheduling configuration to indicate the activation of the semi-persistent scheduling configuration.

8. The apparatus according to claim 6, wherein the apparatus is configured to send the downlink control information to indicate the at least one of activation, deactivation, or modification of the semi-persistent scheduling configuration in the following manner: The downlink control information is sent to at least the devices in the device group over the bandwidth, where the downlink control information includes different indexes of different semi-persistent scheduling configurations to indicate the disabling or the modification of the semi-persistent scheduling configurations.

9. The device according to claim 4 or 5, wherein the device is configured to determine the group public identity associated with the semi-persistent scheduling configuration by: The semi-persistent scheduling configuration is determined as a configuration for the group public identifier.

10. The device according to claim 9, wherein the device is configured to indicate the association between the group public identity and the semi-persistent scheduling configuration in the following manner: The semi-persistent scheduling configuration is broadcast to the device group as a configuration for the group public identifier in a predefined system information block.

11. The apparatus according to claim 9, wherein the apparatus is configured to send the downlink control information to indicate the at least one of activation, deactivation, or modification of the semi-persistent scheduling configuration in the following manner: scrambling the downlink control information using the group public identity; and Scrambled downlink control information is sent to at least the devices in the device group over the bandwidth to indicate the activation of the semi-persistent scheduling configuration.

12. The apparatus of claim 9, wherein the semi-persistent scheduling configuration includes an indication of whether the semi-persistent scheduling configuration is to be used after transitioning from a connected mode to an idle or inactive mode.

13. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to: receiving downlink control information in a common frequency resource on a bandwidth portion used for a multicast broadcast service (MBS) service, the downlink control information indicating at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration on the bandwidth portion used for the MBS service, wherein the downlink control information includes an index of the semi-persistent scheduling configuration, the index indicating the enabling of the semi-persistent scheduling configuration; determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled on the portion of bandwidth used for the multicast broadcast service traffic; as well as In accordance with a determination that the semi-persistent scheduling configuration is enabled, the multicast broadcast service traffic is received on the bandwidth portion based on the semi-persistent scheduling configuration.

14. The apparatus according to claim 13, wherein the apparatus is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled by: blindly decoding the downlink control information on the bandwidth portion using at least one of a dedicated identifier or a group common identifier; and In response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information.

15. The apparatus according to claim 14, wherein the apparatus is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: In response to the downlink control information being received on the common frequency resources on the bandwidth portion, it is determined that the semi-persistent scheduling configuration is enabled.

16. The device of claim 13, wherein the device is further configured to: An indication of a likelihood that the semi-persistent scheduling configuration is used for the multicast broadcast service traffic on the bandwidth portion is received.

17. The device of claim 15, wherein the device is further configured to: An indication of an association between the group common identity and the semi-persistent scheduling configuration for the bandwidth portion is received. 18 . The apparatus according to claim 17 , wherein the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

19. The apparatus according to claim 17 or 18, wherein the apparatus is configured to receive the indication of the association between the group public identity and the semi-persistent scheduling configuration by: In the configuration for the group public identifier, an index of the semi-persistent scheduling configuration is received.

20. The apparatus according to claim 19, wherein the apparatus is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: In response to the decoded downlink control information including the index of the semi-persistent scheduling configuration, it is determined that the semi-persistent scheduling configuration is enabled.

21. The apparatus according to claim 19, wherein the apparatus is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: In response to the decoded downlink control information containing different indices of different semi-persistent scheduling configurations, it is determined that the semi-persistent scheduling configuration is disabled or modified.

22. The apparatus according to claim 17 or 18, wherein the apparatus is configured to receive the indication of the association between the group public identity and the semi-persistent scheduling configuration by: The semi-persistent scheduling configuration is received as a configuration for the group public identifier in a predefined system information block.

23. The apparatus according to claim 22, wherein the apparatus is configured to determine whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information by: In response to the downlink control information being decoded using the group common identity, it is determined that the semi-persistent scheduling configuration is enabled.

24. The apparatus of claim 22, wherein the semi-persistent scheduling configuration includes an indication of whether the semi-persistent scheduling configuration is to be used after transitioning from a connected mode to an idle or inactive mode.

25. The device of claim 14, wherein the device is configured to receive the MPS traffic on the bandwidth portion by: Determining a period of the multicast broadcast service based on the semi-persistent scheduling configuration; and The MPS service is periodically received using common frequency resources on the bandwidth portion.

26. The device of claim 25, wherein the device is configured to receive the MBS traffic using the common frequency resources on the bandwidth portion by: The multicast broadcast service is periodically detected using the common frequency resources on the bandwidth portion with at least one of a dedicated identifier or a group common identifier.

27. The device of claim 14, wherein the device is in a connected mode.

28. The device of claim 27, wherein the device is further configured to, in idle or inactive mode: performing blind decoding of downlink control information on the bandwidth portion using at least one of a dedicated identifier or a group common identifier; and In response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is modified or disabled based on the downlink control information.

29. A method of communication, comprising: determining at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a portion of a bandwidth used for multicast broadcast service traffic; as well as Indicating at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the bandwidth portion to the device group, wherein indicating at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration comprises: Using common frequency resources on the bandwidth portion, downlink control information is sent to at least the devices in the device group to indicate at least one of enabling, disabling or modifying the semi-persistent scheduling configuration, wherein the downlink control information includes an index of the semi-persistent scheduling configuration to indicate the enabling of the semi-persistent scheduling configuration.

30. The method of claim 29, wherein the MPS service comprises a multicast service, and sending the downlink control information to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration comprises: scrambling the downlink control information using a dedicated identifier; as well as Scrambled downlink control information is sent to at least the devices in the device group on the bandwidth to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration.

31. The method of claim 29, further comprising: An indication of a likelihood that the semi-persistent scheduling configuration may be used for the multicast broadcast service traffic on the bandwidth portion is sent to the group of devices.

32. The method of claim 29, further comprising: determining, for the bandwidth portion, a group public identifier associated with the semi-persistent scheduling configuration; as well as An association between the group public identity and the semi-persistent scheduling configuration is indicated to the devices of the device group.

33. The method according to claim 32, wherein the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

34. The method according to claim 32 or 33, wherein the association indicating the group public identity and the semi-persistent scheduling configuration comprises: In the configuration for the group public identifier, an index of the semi-persistent scheduling configuration is sent to at least the devices in the device group to indicate the association between the group public identifier and the semi-persistent scheduling configuration.

35. The method of claim 34, wherein sending the downlink control information to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration comprises: The downlink control information is sent to at least the devices in the device group on the bandwidth, wherein the downlink control information includes an index of the semi-persistent scheduling configuration to indicate the activation of the semi-persistent scheduling configuration.

36. The method of claim 34, wherein sending the downlink control information to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration comprises: The downlink control information is sent to at least the devices in the device group on the bandwidth, where the downlink control information includes different indexes of different semi-persistent scheduling configurations to indicate the disabling or the modification of the semi-persistent scheduling configurations.

37. The method according to claim 32 or 33, wherein determining the group public identity associated with the semi-persistent scheduling configuration comprises: The semi-persistent scheduling configuration is determined as a configuration for the group public identifier.

38. The method of claim 37, wherein indicating the association between the group public identity and the semi-persistent scheduling configuration comprises: The semi-persistent scheduling configuration is broadcast to the device group as a configuration for the group public identifier in a predefined system information block.

39. The method of claim 37, wherein sending the downlink control information to indicate the at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration comprises: scrambling the downlink control information using the group public identifier; as well as Scrambled downlink control information is sent to at least the devices in the device group over the bandwidth to indicate the activation of the semi-persistent scheduling configuration.

40. The method of claim 37, wherein the semi-persistent scheduling configuration includes an indication of whether the semi-persistent scheduling configuration is to be used after transitioning from a connected mode to an idle or inactive mode.

41. A method of communication, comprising: receiving downlink control information in a common frequency resource on a portion of a bandwidth used for a multicast broadcast service (MBS) traffic, the downlink control information indicating at least one of activation, deactivation, or modification of a semi-persistent scheduling configuration, wherein the downlink control information includes an index of the semi-persistent scheduling configuration, the index indicating the activation of the semi-persistent scheduling configuration; determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled on the portion of bandwidth for the multicast broadcast service traffic; as well as In accordance with a determination that the semi-persistent scheduling configuration is enabled, the multicast broadcast service traffic is received on the bandwidth portion based on the semi-persistent scheduling configuration.

42. The method of claim 41 , wherein determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled comprises: blindly decoding downlink control information on the bandwidth portion using at least one of a dedicated identifier and a group common identifier; as well as In response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information.

43. The method of claim 42, wherein determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information comprises: In response to the downlink control information being received on the common frequency resources on the bandwidth portion, it is determined that the semi-persistent scheduling configuration is enabled.

44. The method of claim 41 , further comprising: An indication of a likelihood that the semi-persistent scheduling configuration is used for the multicast broadcast service traffic on the bandwidth portion is received.

45. The method of claim 43, further comprising: An indication of an association between the group common identity of the bandwidth portion and the semi-persistent scheduling configuration is received.

46. The method according to claim 45, wherein the group public identity is a type of group public identity configured for semi-persistent scheduling of a multicast broadcast service.

47. The method according to claim 45 or 46, wherein receiving the indication of the association between the group public identity and the semi-persistent scheduling configuration comprises: In the configuration for the group public identifier, an index of the semi-persistent scheduling configuration is received.

48. The method of claim 47, wherein determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information comprises: In response to the decoded downlink control information including the index of the semi-persistent scheduling configuration, it is determined that the semi-persistent scheduling configuration is enabled.

49. The method of claim 47, wherein determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information comprises: In response to the decoded downlink control information containing different indices of different semi-persistent scheduling configurations, it is determined that the semi-persistent scheduling configuration is disabled or modified.

50. The method of claim 45, wherein receiving the indication of the association between the group public identity and the semi-persistent scheduling configuration comprises: The semi-persistent scheduling configuration is received as a configuration for the group public identifier in a predefined system information block.

51. The method of claim 50, wherein determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled based on the downlink control information comprises: In response to the downlink control information being decoded using the group common identity, it is determined that the semi-persistent scheduling configuration is enabled.

52. The method of claim 50 or 51, wherein the semi-persistent scheduling configuration comprises an indication of whether the semi-persistent scheduling configuration is to be used after transitioning from connected mode to idle or inactive mode.

53. The method of claim 42, wherein receiving the MPS traffic on the bandwidth portion comprises: Determining a period of the multicast broadcast service based on the semi-persistent scheduling configuration; as well as The MPS service is periodically received using common frequency resources on the bandwidth portion.

54. The method of claim 53, wherein receiving the MPS traffic using the common frequency resources on the bandwidth portion comprises: The multicast broadcast service is periodically detected using the common frequency resource on the bandwidth portion and at least one of a dedicated identifier and a group common identifier.

55. The method of claim 42, wherein the method is implemented by a device in connected mode.

56. The method of claim 55, further comprising, in an idle or inactive mode: performing blind decoding of downlink control information on the bandwidth portion using at least one of a dedicated identifier and a group common identifier; and In response to the downlink control information being decoded, determining whether the semi-persistent scheduling configuration is modified or disabled based on the downlink control information.

57. An apparatus for communication, comprising: means for determining at least one of enabling, disabling, or modifying a semi-persistent scheduling configuration for a group of devices on a portion of bandwidth used for multicast broadcast service traffic; as well as means for indicating to the device group at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the bandwidth portion, wherein the means for indicating at least one of enabling, disabling, or modifying the semi-persistent scheduling configuration on the bandwidth portion comprises: A component for sending downlink control information to at least the devices in the device group using common frequency resources on the bandwidth portion to indicate at least one of enabling, disabling or modifying the semi-persistent scheduling configuration, wherein the downlink control information includes an index of the semi-persistent scheduling configuration to indicate the enabling of the semi-persistent scheduling configuration.

58. An apparatus for communication, comprising: means for receiving downlink control information in a common frequency resource on a portion of a bandwidth used for multicast broadcast service traffic, the downlink control information indicating at least one of activation, deactivation, or modification of a semi-persistent scheduling configuration, wherein the downlink control information comprises an index of the semi-persistent scheduling configuration, the index indicating the activation of the semi-persistent scheduling configuration; means for determining whether the semi-persistent scheduling configuration is enabled, modified, or disabled on the portion of bandwidth used for the multicast broadcast service traffic; as well as means for receiving the multicast broadcast service traffic on the bandwidth portion based on the semi-persistent scheduling configuration in accordance with a determination that the semi-persistent scheduling configuration is enabled.

59. A computer-readable storage medium comprising program instructions stored thereon, which, when executed by a processor of a device, cause the device to perform the method according to any one of claims 29 to 40.

60. A computer-readable storage medium comprising program instructions stored thereon, which, when executed by a processor of a device, cause the device to perform the method according to any one of claims 41 to 56.

Images