Method and device for handling unicast and multicast semi-static scheduling deactivated state

Abstract

The present invention discloses a method and device for handling the deactivated state of semi-static scheduling for unicast and multicast. In an example from the perspective of a base station operating with semi-static scheduling (SPS) for unicast and multicast, the base station uses a first information element containing an sps-Config information element or an sps-ConfigToAddModList information element to configure a user equipment (UE) with a unicast semi-static scheduling operation configuration. The base station determines whether to use an sps-ConfigMulticastToAddModList information element to configure the user equipment with a multicast semi-static scheduling operation configuration based on whether the first information element contains an sps-Config information element or an sps-ConfigToAddModList information element.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication networks, and more particularly, to a method and apparatus for handling a semi-persistent scheduling (SPS) deactivated state for unicast and multicast in a wireless communication system. Background Art

[0002] With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that use Internet Protocol (IP) data packets for communication. This IP data packet communication can provide IP-bearing voice, multimedia, multicast and on-demand communication services for users of mobile communication devices.

[0003] An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-bearing voice and multimedia services. Currently, the 3GPP standards organization is discussing the next generation (e.g., 5G) new radio technology. Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the invention

[0004] According to the present disclosure, one or more devices and / or methods are provided. In an example from the perspective of a base station operating with semi-persistent scheduling (SPS) for unicast and multicast, the base station uses a first information element including an sps-Config information element or an sps-ConfigToAddModList information element to configure a user equipment (UE) with a unicast SPS operation configuration. The base station determines whether to use an sps-ConfigMulticastToAddModList information element to configure the UE with a multicast SPS operation configuration based on whether the first information element includes an sps-Config information element or an sps-ConfigToAddModList information element.

[0005] In an example from the perspective of a base station operating with SPS for unicast and multicast, the base station configures the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element. The base station is not allowed to configure the UE with a unicast SPS operation configuration using the sps-Config information element. The base station is allowed to configure the UE with a unicast SPS operation configuration using the sps-ConfigToAddModList information element.

[0006] In an example from the perspective of a UE operating with SPS for unicast and multicast, the UE receives a first information element including an sps-Config information element or an sps-ConfigToAddModList information element. The UE configures a unicast SPS operation configuration based on the first information element. Based on the first information element including the sps-Config information element, the UE does not monitor for reception of an sps-ConfigMulticastToAddModList information element associated with configuring a multicast SPS operation configuration for the UE. Alternatively and / or in addition, based on the first information element including the sps-ConfigToAddModList information element, the UE monitors for reception of an sps-ConfigMulticastToAddModList information element associated with configuring a multicast SPS operation configuration for the UE.

[0007] In an example from the perspective of a UE operating with SPS for unicast and multicast, the UE receives an sps-ConfigMulticastToAddModList information element. The UE configures a multicast SPS operation configuration based on the sps-ConfigMulticastToAddModList information element. The UE does not listen for reception of an sps-Config information element associated with configuring a unicast SPS operation configuration. The UE listens for reception of an sps-ConfigToAddModList information element associated with configuring a unicast SPS operation configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 A diagram of a wireless communication system is shown according to an exemplary embodiment.

[0009] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to one exemplary embodiment.

[0010] Figure 3 is a functional block diagram of a communication system according to an exemplary embodiment.

[0011] Figure 4According to an exemplary embodiment Figure 3 Functional block diagram of the program code.

[0012] Figure 5 is a diagram illustrating one or more exemplary scenarios associated with semi-persistent scheduling (SPS) configuration of one or more UEs according to an exemplary embodiment.

[0013] Figure 6 is a flow chart according to an exemplary embodiment.

[0014] Figure 7 is a flow chart according to an exemplary embodiment.

[0015] Figure 8 is a flow chart according to an exemplary embodiment.

[0016] Fig. 9 is a flow chart according to an exemplary embodiment.

[0017] Fig.10 is a flow chart according to an exemplary embodiment.

[0018] Fig.11 is a flow chart according to an exemplary embodiment.

[0019] Fig.12 is a flow chart according to an exemplary embodiment.

[0020] Fig.13 is a flow chart according to an exemplary embodiment.

[0021] Fig.14 is a flow chart according to an exemplary embodiment. DETAILED DESCRIPTION

[0022] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP (3 rd3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A or LTE-Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR) radio access for 5G, or some other modulation technology.

[0023] Specifically, the exemplary wireless communication system device described below can be designed to support one or more standards, such as the standards provided by the alliance named "3rd Generation Partnership Project" referred to herein as 3GPP, including: R1-2202951 correction to the introduction of multicast broadcast services in NR; R1-2202968 correction to NR multicast and broadcast services in 38.212; R2-2203818 introduction of NR MBS; R2-2204251 introduction of NR MBS into 38.331; R2-2204261 introduction of NR MBS; RP-220407 status report for WI NR multicast and broadcast services. The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

[0024] Figure 1 A multiple access wireless communication system according to one or more embodiments of the present disclosure is presented. An access network 100 (AN) includes multiple antenna groups, one antenna group includes 104 and 106, another antenna group includes 108 and 110, and another antenna group includes 112 and 114. Figure 1 1, only two antennas are shown for each antenna group, however, each antenna group may utilize more or fewer antennas. An access terminal 116 (AT) communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from access terminal 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In a frequency-division duplexing (FDD) system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the frequency used by reverse link 118.

[0025] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups may each be designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0026] In communications on forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Also, an access network that uses beamforming to transmit to access terminals that are randomly dispersed throughout the coverage area of ​​the access network will generally cause less interference to access terminals in neighboring cells than an access network that transmits to its access terminals via a single antenna.

[0027] An access network (AN) may be a fixed station or base station for communicating with a terminal, and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB (eNB), next generation NodeB (gNB), or some other term. An access terminal (AT) may also be referred to as a user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.

[0028] Figure 2 Embodiments of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) are presented in a multiple-input and multiple-output (MIMO) system 200. At the transmitter system 210, traffic data for a plurality of data streams may be provided from a data source 212 to a transmit (TX) data processor 214.

[0029] In one embodiment, each data stream is transmitted through a respective transmit antenna.TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0030] The decoded data for each data stream may be multiplexed with pilot data using orthogonal frequency-division multiplexing (OFDM) techniques. The pilot data may typically be a known data pattern processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and the decoded data for the data stream may then be modulated (i.e., symbol mapped) based on a particular modulation scheme selected for each data stream (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-ary quadrature amplitude modulation (M-QAM)) to provide modulation symbols. Instructions executed by processor 230 may determine the data rate, coding, and / or modulation for each data stream.

[0031] The modulation symbols for the data stream are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 may apply beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0032] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and / or upconverts) the analog signals to provide a modulated signal suitable for transmission over a MIMO channel. T The antennas 224a to 224t transmit N signals from the transmitters 222a to 222t. T a modulated signal.

[0033] At the receiver system 250, N REach antenna 252a through 252r receives the transmitted modulated signals and may provide the received signal from each antenna 252 to a respective receiver (RCVR) 254a through 254r. Each receiver 254 may condition (e.g., filter, amplify, and downconvert) a respective received signal, digitize the conditioned signal to provide samples, and / or further process the samples to provide a corresponding “received” symbol stream.

[0034] Next, the RX data processor 260 receives the N R The receiver 254 receives and / or processes N based on a particular receiver processing technique. R received symbol streams to provide N T The RX data processor 260 may then demodulate, deinterleave, and / or decode each detected symbol stream to recover the traffic data for the data stream. The processing by the RX processor 260 may be complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0035] Processor 270 may periodically determine which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0036] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message may then be processed by the TX data processor 238 (which also receives traffic data for a plurality of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and / or transmitted back to the transmitter system 210.

[0037] At the transmitter system 210, the modulated signals from the receiver system 250 are received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 may then determine which precoding matrix to use to determine the beamforming weights and may then process the extracted message.

[0038] Figure 3 An alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter is presented. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in or Figure 1The base station (or AN) 100 in the wireless communication system may be an LTE system or an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 may receive a signal input by a user through the input device 302 (for example, a keyboard or a keypad), and may output images and sounds through the output device 304 (for example, a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306. The communication device 300 in the wireless communication system may also be used to implement Figure 1 AN 100 in.

[0039] Figure 4 According to one embodiment of the disclosed subject matter Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 may perform radio resource control. Layer 2 portion 404 may perform link control. Layer 1 portion 406 may perform and / or implement physical connectivity.

[0040] The following quotes one or more parts of R1-2202951 (TS 38.213):

[0041] Overview of changes:…

[0042] 10. Include SPSGC-PDSCH activation / deactivation of DCI format 4_1 / 4_2 in clause 10.2.

[0043] …

[0044] 10.2 PDCCH Verification for DL ​​SPS and UL Grant Type 2

[0045] The UE verifies the DL SPS allocation PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or scheduling release in the following cases:

[0046] - scramble the CRC of the corresponding DCI format with the CS-RNTI provided by the cs-RNTI or the G-CS-RNTI provided by the g-cs-RNTI, and

[0047] - the New Data Indicator field in the DCI format for enabled transport blocks is set to '0', and

[0048] - the DFI Flag field in the DCI format (if present) is set to '0', and

[0049] - If the verification is activated for scheduling and if the PDSN to HARQ_feedback timing indicator field in DCI format is present, the HARQ_feedback timing indicator field does not provide an unavailable value from dl-DataToUL-ACK-r16.

[0050] If a single configuration for UL grant type 2 PUSCH or for SPS PDSCH is provided to the UE, then validation of the DCI format is achieved if all fields of the DCI format are set according to Table 10.2-1 or Table 10.2-2.

[0051] If more than one configuration for UL grant type 2 PUSCH or for SPS PDSCH is provided to the UE, then the value of the HARQ Process Number field in the DCI format indicates the activation for the corresponding UL grant type 2 PUSCH, or for the SPS PDSCH configuration having the same value as the value provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively. If the RV field of the DCI format is set as in Table 10.2-3, then verification of the DCI format is achieved.

[0052] If more than one configuration for UL grant type 2 PUSCH or for SPS PDSCH is provided to the UE

[0053] - If ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList is provided to the UE, the value of the HARQ Process Number field in DCI format indicates the corresponding entry for scheduling the release of one or more UL Grant Type 2 PUSCH or SPS PDSCH configurations

[0054] - If ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList is not provided to the UE, the value of the HARQ Process Number field in the DCI format indicates the release for the corresponding UL grant type 2 PUSCH, or for the release of the SPS PDSCH configuration having the same value as that provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively.

[0055] If all fields of the DCI format are set according to Table 10.2-4, then validation of the DCI format is achieved.

[0056] If the verification is achieved, the UE regards the information in the DCI format as a valid activation or a valid release of the DL SPS or configured UL grant type 2. If the verification is not achieved, the UE discards all the information in the DCI format.

[0057] Table 10.2-1: Special fields for single DL SPS or single UL grant type 2 scheduling activation PDCCH verification when a single SPS PDSCH or UL grant type 2 configuration is provided to the UE in the active DL / UL BWP of the scheduled cell

[0058]

[0059]

[0060] Table 10.2-2: Special fields for single DL SPS or single UL grant type 2 scheduling release PDCCH validation when single SPS PDSCH or UL grant type 2 configuration is provided to the UE in the active DL / UL BWP of the scheduled cell

[0061]

[0062] Table 10.2-3: Special fields for single DL SPS or single UL Grant Type 2 scheduling activation PDCCH validation when multiple DL SPS or UL Grant Type 2 configurations are provided to the UE in the active DL / UL BWP of the scheduled cell

[0063]

[0064] Table 10.2-4: Special fields for single or multiple DL SPS and UL Grant Type 2 scheduling release PDCCH validation when multiple DL SPS or UL Grant Type 2 configurations are provided to the UE in the active DL / UL BWP of the scheduled cell

[0065]

[0066]

[0067] In response to an SPS PDSCH release N symbols after the last symbol of the PDCCH providing the SPS PDSCH release, the UE is expected to provide HARQ-ACK information. If processingType2Enabled of PDSCH-ServingCellConfig is set to enabled for a serving cell with a PDCCH providing an SPS PDSCH release, then for μ=0, N=5, for μ=1, N=5.5, and for μ=2, N=11, otherwise, for μ=0, N=10, for μ=1, N=12, for μ=2, N=22, for μ=3, N=25, for μ=5, N=100, and for μ=6, N=200, where μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH providing the SPS PDSCH release and the SCS configuration of the PUCCH carrying the HARQ-ACK information in response to the SPS PDSCH release.

[0068] The following quotes one or more parts of R1-2202968 (TS 38.212):

[0069] 7.3.1.5.2 Format 4_1

[0070] DCI format 4_1 is used for scheduling of multicast PDSCH in the DL cell.

[0071] The following information is transmitted by means of DCI format 4_1 with CRC scrambled by the G-RNTI configured by G-RNTI-Config or G-CS-RNTI:

[0072] …

[0073] 7.3.1.5.3 Format 4_2

[0074] DCI format 4_2 is used for scheduling of PDSCH in the DL cell.

[0075] The following information is transmitted by means of DCI format 4_2 with CRC scrambled by the G-RNTI configured by G-RNTI-Config or G-CS-RNTI:

[0076] The following quotes one or more parts of R2 2203818 (TS 38.321 Medium Access Control (MAC)):

[0077] 5.3DL-SCH Data Transmission

[0078] 5.3.1DL allocation reception

[0079] A downlink assignment received on the PDCCH indicates the presence of a transmission on the DL-SCH for a specific MAC entity and provides related HARQ information.

[0080] When the MAC entity has a C-RNTI, a Temporary C-RNTI or a CS-RNTI, the MAC entity shall monitor the PDCCH for each PDCCH opportunity during which it does so and for each serving cell:

[0081] 1> If the C-RNTI or temporary C-RNTI or G-RNTI for the MAC entity has received a downlink allocation for this PDCCH opportunity and this serving cell on the PDCCH:

[0082] 2> If this is the first downlink allocation for this temporary C-RNTI:

[0083] 3> Treat NDI as switched.

[0084] 2> if the downlink allocation is for the C-RNTI of the MAC entity and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the CS-RNTI or G-CS-RNTI of the MAC entity or a configured downlink allocation for unicast or MBS multicast; or

[0085] 2> If the downlink allocation is for the G-RNTI of the MAC entity, and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for the CS-RNTI or G-CS-RNTI or other G-RNTI or C-RNTI of the MAC entity, or a configured downlink allocation for unicast or MBS multicast:

[0086] 3>Regardless of the value of NDI, treat NDI as toggled.

[0087] 2> Indicates the presence of a downlink allocation and delivers the associated HARQ information to the HARQ entity.

[0088] 1> else if a downlink allocation for this PDCCH opportunity has been received on the PDCCH for the CS-RNTI or G-CS-RNTI of the MAC entity for this serving cell:

[0089] 2> If the NDI in the received HARQ information is 1:

[0090] 3> Treat the NDI used for the corresponding HARQ process as not yet switched;

[0091] 3> Indicates the presence of a downlink allocation for this serving cell and delivers the associated HARQ information to the HARQ entity.

[0092] 2> If the NDI in the received HARQ information is 0:

[0093] 3> If the PDCCH content indicates SPS deactivation:

[0094] 4> Clear the configured downlink allocation for this serving cell (if any);

[0095] 4> If the timeAlignmentTimer associated with the TAG containing the serving cell on which the HARQ feedback is to be transmitted is running:

[0096] 5> Indicates positive confirmation of SPS deactivation to the physical layer.

[0097] 3> Otherwise if the PDCCH content indicates SPS activation:

[0098] 4>Store the downlink allocation and associated HARQ information for this serving cell as a configured downlink allocation;

[0099] 4> Initialize or reinitialize the configured downlink allocation for this serving cell to start in the associated PDSCH duration and recur according to the rules in clause 5.8.1;

[0100] For each serving cell and each configured downlink allocation (if configured and activated), the MAC entity shall:

[0101] 1> If the PDSCH duration of the configured downlink allocation does not overlap with the PDSCH duration of the downlink allocation received on the PDCCH for this serving cell:

[0102] 2> Instruct the physical layer to receive transport blocks on the DL-SCH and deliver them to the HARQ entity according to the configured downlink allocation in this PDSCH duration;

[0103] 2> Set the HARQ process ID to the HARQ process ID associated with this PDSCH duration;

[0104] 2> The NDI bit for the corresponding HARQ process is considered to be switched;

[0105] 2> Indicate the presence of a configured downlink allocation and deliver the stored HARQ information to the HARQ entity.

[0106] The following quotes one or more parts of R2-2204251 (TS 38.331 Radio Resource Control (RRC)):

[0107] -BWP-DownlinkDedicated

[0108] IE BWP-DownlinkDedicated is used to configure dedicated (UE-specific) parameters of the downlink BWP.

[0109] BWP-DownlinkDedicated Information Element

[0110]

[0111]

[0112] SPS-ConfigToAddModList-r16::=SEQUENCE(SIZE(1..maxNrofSPS-Config-r16))OF SPS-Config

[0113] SPS-ConfigToReleaseList-r16::=SEQUENCE(SIZE(1..maxNrofSPS-Config-r16))OF SPS-ConfigIndex-r16

[0114] SPS-ConfigDeactivationState-r16::=SEQUENCE(SIZE(1..maxNrofSPS-Config-r16))OF SPS-ConfigIndex-r16

[0115] SPS-ConfigDeactivationStateList-r16::=SEQUENCE(SIZE(1..maxNrofSPS-DeactivationState))OF SPS-ConfigDeactivationState-r16

[0116] --TAG-BWP-DOWNLINKDEDICATED-STOP--ASN1 STOP

[0117]

[0118]

[0119]

[0120] -CFR-ConfigMulticast

[0121] The IE CFR-ConfigMulticast indicates the UE-specific common frequency resource configuration for multicast of one dedicated BWP.

[0122] CFR-ConfigMulticast Information Element

[0123]

[0124]

[0125] SPS-ConfigMulticastToAddModList-r17::=SEQUENCE(SIZE(1..8))OF SPS-Config

[0126] SPS-ConfigMulticastToReleaseList-r17::=SEQUENCE(SIZE(1..8))OF SPS-ConfigIndex-r16

[0127] --TAG-CFRCONFIGMULTICAST-STOP

[0128] --ASN1STOP

[0129]

[0130] The following quotes one or more parts of R2-2204261 (TS 38.300 Issue 2):

[0131] 3.1 Abbreviations

[0132] For the purposes of this document, the abbreviations given in TR 21.905 [1], TR 36.300 [2] and hereinafter apply. Abbreviations defined in this document take precedence over definitions of the same abbreviation (if any) in TR 21.905 [1] and TS 36.300 [2].

[0133] …

[0134] G-RNTI Group RNTI

[0135] G-CS-RNTI group configuration scheduling RNTI

[0136] …

[0137] MRB MBS Radio Bearer

[0138] MT Mobile Terminal

[0139] MTCH MBS service channel

[0140] …

[0141] PTM Point to Multipoint

[0142] PTP Point to Point

[0143] …

[0144] …

[0145] 8.1UE Identification

[0146] In this clause, the identities used by NR connected to 5GC are listed. For scheduling at the cell level, the following identities are used:

[0147] -C-RNTI: A unique UE identity used as an identifier for the RRC connection and for scheduling;

[0148] -CS-RNTI: A unique UE identifier used for semi-persistent scheduling in the downlink or for configuring grants in the uplink;

[0149] -INT-RNTI: identifier of the pre-entry in the downlink;

[0150] -MCS-C-RNTI: A unique UE identifier used to indicate an alternative MCS table for PDSCH and PUSCH;

[0151] -P-RNTI: an identifier for paging and system information change notification in the downlink;

[0152] -SI-RNTI: identification of broadcast and system information in downlink;

[0153] - SP-CSI-RNTI: Unique UE identity used for semi-static CSI reporting on PUSCH.

[0154] …

[0155] For MBS, the following identifiers are used:

[0156] -G-RNTI: identifies the dynamic scheduling transmission of MTCH;

[0157] - G-CS-RNTI: identifies the configured scheduled transmission of MTCH;

[0158] - MCCH-RNTI: identifies the MCCH and the transmission of MCCH change notifications.

[0159] …

[0160] 16.x Multicast and Broadcast Services

[0161] 16.x.1 General

[0162] The NR system enables resource-efficient delivery of multicast / broadcast services (MBS).

[0163] For broadcast communication services, the same service and the same specific content data are provided to all UEs in a geographic area at the same time (i.e., all UEs in the MBS service area are authorized to receive the data). Broadcast communication services are delivered to UEs using broadcast sessions. UEs can receive broadcast communication services in RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states.

[0164] For multicast communication services, the same service and the same specific content data are provided simultaneously to a dedicated set of UEs (i.e., not all UEs in the multicast service area are authorized to receive the data). Multicast communication services are delivered to UEs using multicast sessions. UEs may receive multicast communication services in the RRC_CONNECTED state through mechanisms such as PTP and / or PTM delivery, as defined in Section 16.x.5.4. HARQ feedback / retransmission may be applied to both PTP and PTM transmissions.

[0165] […]

[0166] 16.x.4 Group Scheduling

[0167] The following logical channels are used for MBS delivery:

[0168] -MTCH: a point-to-multipoint downlink channel used to transmit MBS data of a multicast session or a broadcast session from the network to the UE;

[0169] - DTCH: a point-to-point channel defined in section 6.2.2 used to transmit MBS data of a multicast session from the network to the UE;

[0170] - MCCH: a point-to-multipoint downlink channel used to transmit MBS broadcast control information associated with one or several MTCHs from the network to the UEs.

[0171] The following connections exist between the logical channel used for group transmission and the transport channel:

[0172] -MCCH can be mapped to DL-SCH;

[0173] -MTCH can be mapped to DL-SCH.

[0174] The following depicts the use of RNTI for group transmission:

[0175] -The UE may use the same or different G-RNTI / G-CS-RNTI to receive different services.

[0176] […]

[0177] 16.x.5.4 Reception of MBS Multicast Data

[0178] For multicast services, the gNB can use the following methods to deliver multicast MBS packets:

[0179] -PTP transmission: The gNB delivers a separate copy of the MBS data packet to each UE independently, i.e., the gNB uses a UE-specific PDCCH with a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI) to schedule a UE-specific PDSCH scrambled by the same UE-specific RNTI.

[0180] -PTM transmission: The gNB delivers a single copy of an MBS data packet to a group of UEs, e.g. the gNB uses a group-common PDCCH with a CRC scrambled by the group-common RNTI to schedule a group-common PDSCH scrambled with the same group-common RNTI.

[0181] If the UE is configured with both PTM and PTP transmission, then the gNB dynamically decides whether to deliver the multicast data by PTM branch and / or PTP branch for a given UE based on the protocol stack defined in section 16.x.3, based on information such as MBS session QoS requirements, number of joined UEs, UE individual feedback on reception quality and other criteria. Regardless of the decision, the same QoS requirements apply.

[0182] 16.x.5.5CA support

[0183] The UE can receive MBS multicast data from the PCell or a single SCell at a time.

[0184] 16.x.5.6DRX

[0185] The following DRX configurations for PTM / PTP transmission are possible:

[0186] - For PTM transmission, multicast DRX mode is configured on a per-G-RNTI / G-CS-RNTI basis independent of UE-specific DRX for unicast transmission;

[0187] - For PTP transmission, the UE-specific DRX pattern for unicast is reused, i.e. the UE-specific DRX pattern is used for both unicast services and PTP transmission of MBS. For PTP transmission for PTM retransmission, the UE monitors the PDCCH scrambled by C-RNTI / CS-RNTI only during the active time of unicast DRX.

[0188] The following quotes one or more portions of RP-220407:

[0189] 2.1RAN1

[0190] 2.1.1 Protocol

[0191] RAN1#107b-e

[0192] Support for group scheduling mechanisms for RRC_CONNECTED UEs

[0193] protocol

[0194] DCI format 4_2 does not contain the following fields:

[0195] ●Scell ​​sleep indication

[0196] BWP indicator

[0197] DCI format 4_2 contains the following fields (configurable):

[0198] ●MCS / NDI / RV for TB2

[0199] ○Support of this field is subject to UE capabilities

[0200] …

[0201] RAN1#108-e

[0202] Support for group scheduling mechanisms for RRC_CONNECTED UEs

[0203] protocol

[0204] In the reply LS on MBS SPS to RAN2, the following items for Q1 are captured:

[0205] RAN1 confirms that RAN2's understanding is correct.

[0206] • RAN1 considers that the maximum number of G-CS-RNTIs configured for a UE should be subject to the UE capabilities.

[0207] protocol

[0208] In the reply LS on MBS SPS to RAN2, the following items for Q2 are captured:

[0209] • From RAN1 perspective, the retransmission scheme (ie, via PTM or PTP) may change per TB per transmission.

[0210] o After a PTP retransmission for the same multicast TB, the UE does not expect to receive a PTM retransmission.

[0211] ○ There is no consensus in RAN1 to support both PTM retransmission and PTP retransmission for different UEs in the same MBS group

[0212] ● A single CS-RNTI is used for PTP retransmissions for all G-CS-RNTIs.

[0213] protocol

[0214] RAN1 believes that for a UE, multiple G-CS-RNTIs cannot be mapped to the same MBS SPS-config at the same time.

[0215] Reply LS to R1-2200888 on MBS SPS endorsed in R1-2202591.

[0216] …

[0217] 2.2RAN2

[0218] 2.2.1 Protocol

[0219] RAN2#116bis-e:

[0220] …

[0221] Agreement on MAC Open Issues

[0222] if the downlink allocation is for a C-RNTI and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for a G-CS-RNTI of the MAC entity or a configured downlink allocation for MBS, or if the downlink allocation is for a G-RNTI and if the previous downlink allocation indicated to the HARQ entity of the same HARQ process was a downlink allocation received for a G-CS-RNTI of the MAC entity or another G-RNTI or C-RNTI or a configured downlink allocation for MBS or unicast,

[0223] ●Regardless of the value of NDI, NDI is considered to be toggled.

[0224] • A one-to-many mapping between G-CS-RNTI and MBS sessions is supported, and it is assumed that this does not introduce additional designation work.

[0225] • Capture CS-RNTI may be used for MBS in section 7.1 in MBS MAC operation CR, ie, PTP for PTM retransmission via CS-RNTI and MBS SPS deactivation via CS-RNTI when MBS SPS is configured.

[0226] • If MBS SPS is configured and CS-RNTI is not configured, retransmission of SPS via PTP and MBS SPS deactivation via CS-RNTI are not supported.

[0227] ● Regardless of whether the SPS is used for unicast or multicast, the sps-ConfigIndex shall be unique in the UE.

[0228] • RAN2 assumes no RAN2 specification impact when more than one NACK-only based feedback is available for transmission in the same PUCCH slot and the UE converts the NACK-only to ACK / NACK HARQ bits.

[0229] ●Removal editor should pay attention to the activity time of MBS DRX.

[0230] • In PTP for PTM retransmission, the UE listens to the UE-specific PDCCH / C-RNTI only during the active time of unicast DRX. When a PTP retransmission is expected, the RTT timer for unicast DRX may be started.

[0231] ● RAN2 confirms RAN1 unification that “multicast MBS reception will affect the BWP switching inactivity timer, but broadcast MBS reception will not” and captures it in the MAC CR.

[0232] • If the UE is receiving a broadcast, it is the network implementation's policy not to configure a preset BWP that does not contain an initial BWP.

[0233] ● Multicast MBS can be supported on the MCG side in both NE-DC and NR-DC scenarios, i.e., MCG bearer type where the MN terminates the MRB.

[0234] ●Remove editor comment for LCID on broadcast in CR running on MAC.

[0235] • The network may not ensure that all MBS sessions associated with one G-RNTI are of interest to the UE, the proposed specification changes are captured in the MBS MAC Operation CR.

[0236] …

[0237] The UE may verify a downlink (DL) semi-persistent scheduling (SPS) allocation physical downlink control channel (PDCCH) and / or a configured uplink (UL) grant type 2 PDCCH for scheduling activation or scheduling release (e.g., deactivation). For example, if fields (e.g., all fields) for a downlink control information (DCI) format (e.g., PDCCH) are set according to the following conditions (e.g., predefined conditions), the UE may verify (e.g., for scheduling activation or scheduling release) the DL SPS allocation PDCCH and / or the configured UL grant type 2 PDCCH: (i) the cyclic redundancy check (CyclicRedundancyCheck) of the DCI format is scrambled with a configured scheduling (CS) radio network temporary identifier (RNTI) (CS-RNTI) (e.g., provided by a "cs-RNTI" parameter) and / or a group CS-RNTI (G-CS-RNTI) (e.g., provided by a "g-cs-RNTI" parameter) Check, CRC); (ii) the new data indicator field in DCI format for enabling the transport block is set to '0'; (iii) the DFI flag field in DCI format (if present) is set to '0'; and (iv) if the verification (e.g., by the UE) is for scheduling activation and if the PDSCH-to-HARQ_feedback timing indicator field in DCI format is present, then the PDSCH-to-HARQ_feedback timing indicator field does not provide an inapplicable value from dl-DataToUL-ACK-r16. The PDSCH-to-HARQ_feedback timing indicator field may be associated with a physical downlink shared channel (PDSCH) and / or a hybrid automatic repeat request (HARQ) associated with the PDSCH.

[0238] In addition to the DL SPS for unicast, the DL SPS for multicast may be (also) used for multiple UEs scheduled in a semi-static manner by the network. A UE may be configured with multiple DL SPS configurations identified by an SPS ID (e.g., sps-ConfigIndex) for unicast or multicast. For example, multiple DL SPS configurations may be distinguished by SPS IDs. In an example, a first SPS ID may identify a first DL SPS configuration, a second SPS ID may identify a second DL SPS configuration, and so on. In some examples, possible SPS IDs (for identifying DL SPS configurations) may be in the range of 0 to 7.

[0239] In some instances, for multicast in the RRC_CONNECTED state, DL SPS for multicast (e.g., DL SPS only for multicast) may be activated and / or deactivated by a Group Common (GC) PDCCH (GC-PDCCH) with a G-CS-RNTI. In some instances, DL SPS for multicast may not be activated by a unicast PDCCH with a CS-RNTI, but may be deactivated by a unicast PDCCH with a CS-RNTI.

[0240] If the UE is configured with a single DL SPS configuration, the UE may receive PDCCH scheduling activation or deactivation for the single DL SPS configuration. According to System A, if the value of the HARQ process number field in the PDCCH is not zero ('0') (for example, if at least one value of the HARQ process number field is not zero ('0')), the UE may (i) not verify the PDCCH scheduling activation or deactivation, and / or (ii) discard the information of the PDCCH (for example, discard all information of the PDCCH). If the DL SPS configuration is for unicast, the network (for example, at least one of the base station, gNB, etc.) may set the value of the HARQ process number field of the HARQ process to '0' (for example, if the DL SPS configuration is for unicast, the network may always set the value of the HARQ process number field to '0'). However, if the DL SPS configuration is for multicast, the network may have difficulty and / or be limited to (always) implementing such settings (for example, limiting the network to always setting the value of the HARQ process number field to '0' may limit efficiency). In an example, a DL SPS for multicast may be configured for multiple UEs (e.g., the same DL SPS for multicast may be configured for each of the multiple UEs), where each of the multiple UEs may have its own set of one or more SPS configurations for multicast and / or unicast. In an example, each SPS configuration for unicast or multicast may be associated with (e.g., may include and / or may be configured with) a unique SPS ID for the UE to know which SPS configuration to activate or deactivate (e.g., the UE may determine whether to activate or deactivate the SPS configuration based on the SPS ID associated with the SPS configuration). Figure 5 One or more scenarios associated with the SPS configuration of UEs A, B, C, D, and E are shown. Figure 5In Table 500 of , SPS ID=0 for unicast is configured for UE A, and SPS ID=4 for multicast is configured for UE A, B, C, and D. If the network sends a command associated with activation or deactivation to an SPS configuration with SPS ID=4 (e.g., the command may include an instruction to activate or deactivate an SPS configuration corresponding to SPS ID=4), UE D may discard the command because the value of the HARQ process number field in the command is not all zero (e.g., the HARQ process number field may indicate SPS ID=4). If the network wants to avoid this situation (e.g., if the network wants to avoid UE D discarding the command), it may set an SPS configuration with SPS ID=0 (e.g., the HARQ process number field may indicate SPS ID=0, and therefore the value of the HARQ process number field may be zero, such as where all values ​​of the HARQ process number field are set to zero). Alternatively and / or in addition, the network will also need to avoid using SPS ID=0 for SPS configurations for UE A, B, and C (e.g., all SPS configurations). Therefore, the configuration flexibility of a network using system A may be limited.

[0241] Table 1 provides an example associated with System A. As shown in Table 1, according to System A, even if the UE is configured with a single SPS configuration with SPS ID (e.g., sps-ConfigIndex) = non-zero, the value of the HARQ process number field of the command (e.g., activation or deactivation command) should still be set to zero (e.g., all values ​​of the HARQ process number field should be set to zero for the UE to verify the activation command); otherwise the UE will ignore and / or discard the activation command (e.g., in the case where the value of the HARQ process number field is all set to zero).

[0242] For example, according to Table 1, if the UE is configured with a single SPS configuration, the value of the HARQ process number field may be set and / or used according to Option 1, regardless of whether the UE is configured with sps-ConfigIndex. In Option 1, the UE may determine whether to verify a command (e.g., command scheduling and / or directing activation or deactivation of an SPS configuration) based on whether the value of the HARQ process number field is equal to a predefined value (e.g., zero). For example, according to Option 1, if the value of the HARQ process number field is equal to a predefined value (e.g., zero) (e.g., only when the value of the HARQ process number field is equal to the predefined value), the UE may verify the command. Alternatively and / or additionally, according to Option 1, if the value of the HARQ process number field is not equal to a predefined value (e.g., the value of the HARQ process number field is non-zero, e.g., where not all values ​​of the HARQ process number field are set to zero), the UE may discard and / or ignore the command.

[0243] Alternatively and / or additionally, according to Table 1, if the UE is configured with multiple SPS configurations, the value of the HARQ process number field may be set and / or used according to Option 2 when the UE is configured with sps-ConfigIndex. In Option 2, the UE may determine the sps-ConfigIndex (e.g., the SPS ID of the SPS configuration) based on the value of the HARQ process number field, and / or may activate or deactivate the SPS configuration identified by the sps-ConfigIndex. For example, in Option 2, the UE may regard the value of the HARQ process number field as the SPS ID of the SPS configuration. Alternatively and / or additionally, in Option 2, the UE may determine whether to verify the command based on one or more other fields in the command (except the HARQ process number field) (e.g., the HARQ process number field may not be used to determine whether to verify the command). If the command is verified (e.g., if the command passes verification), the UE may activate or deactivate the SPS configuration indicated by the HARQ process number field.

[0244]

[0245]

[0246] Table 1

[0247] According to one or more of the techniques of the present disclosure, one or more options are provided for handling the HARQ process number field. The one or more options may include option 3, option 4, and / or option 5. In option 3, the UE may determine whether to verify a command (e.g., command scheduling and / or guide activation or deactivation of an SPS configuration) based on whether the value of the HARQ process number field is equal to a predefined value (e.g., zero, such as where all values ​​of the HARQ process number field are set to zero). For example, according to option 3, if the value of the HARQ process number field is equal to a predefined value (e.g., only when the value of the HARQ process number field is equal to a predefined value), then the UE may verify the command (e.g., if all values ​​of the HARQ process number field are set to zero, then the UE may verify the command). For example, according to option 3, the UE may need to check whether the value of the HARQ process number field is equal to a predefined value (e.g., zero) to determine whether verification is achieved (e.g., the UE may need to check whether all values ​​of the HARQ process number field are set to zero). Alternatively and / or additionally, according to option 3, if the value of the HARQ process number field is not equal to a predefined value (e.g., the value of the HARQ process number field is non-zero, e.g., where not all values ​​of the HARQ process number field are set to zero), then the UE may discard and / or ignore the command.

[0248] In option 4, the UE may regard the value of the HARQ process number field as the SPS ID of the SPS configuration, and / or may perform activation or deactivation (e.g., based on a command) for the SPS configuration identified by the SPS ID indicated by the HARQ process number field. For example, the UE may activate or deactivate the SPS configuration in response to a verification command (e.g., based on a command including the HARQ process number field). In some instances, in option 4, the UE may determine whether to verify the command based on one or more other fields in the command (other than the HARQ process number field) (e.g., the HARQ process number field may not be used to determine whether to verify the command). For example, the HARQ process number field may not be used (e.g., applied and / or considered) in the verification of the PDCCH. If the command is verified (e.g., if the command passes verification), the UE may activate or deactivate the SPS configuration indicated by the HARQ process number field.

[0249] In option 5, the UE may skip the HARQ process number field. For example, the HARQ process number field may not be used (eg, applied and / or considered) for validation (eg, the HARQ process number field may not be used to validate a command including the HARQ process number field).

[0250] Options 3 to 5 are applicable to different conditions as shown in Table 2. Different options may be combined into a method (eg, a specific method) for SPS activation or deactivation for unicast or multicast in different conditions (eg, according to Table 2).

[0251] For example, according to Table 2, if (i) the UE is configured with a single SPS configuration, (ii) the single SPS configuration is used for unicast, and (iii) the UE is not configured with sps-ConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 3 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 3 and / or 5.

[0252] Alternatively and / or additionally, according to Table 2, if (i) the UE is configured with a single SPS configuration, (ii) the single SPS configuration is for unicast, and (iii) the UE is configured with sps-ConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 3, 4 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 3, 4 and / or 5.

[0253] Alternatively and / or additionally, according to Table 2, if (i) the UE is configured with a single SPS configuration, (ii) the single SPS configuration is used for multicast, and (iii) the UE is configured with sps-ConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 4 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 4 and / or 5.

[0254] Alternatively and / or additionally, according to Table 2, if (i) the UE is configured with two SPS configurations, (ii) the first SPS configuration of the two SPS configurations is for unicast, (iii) the second SPS configuration of the two SPS configurations is for multicast, (iv) the UE is not configured with sps-ConfigIndex, and / or (v) the command is used to activate or deactivate the first SPS configuration for unicast, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 3 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 3 and / or 5.

[0255] Alternatively and / or additionally, according to Table 2, if (i) the UE is configured with two SPS configurations, (ii) the first SPS configuration of the two SPS configurations is used for unicast, (iii) the second SPS configuration of the two SPS configurations is used for multicast, and (iv) the UE is configured with sps-ConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 3, 4 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 3, 4 and / or 5.

[0256] Alternatively and / or additionally, according to Table 2, if (i) the UE is configured with more than two SPS configurations, (ii) the first SPS configuration of the more than two SPS configurations is used for unicast, and (iii) the UE is not configured with sps-ConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 3 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 3 and / or 5.

[0257] Alternatively and / or additionally, according to Table 2, if (i) the UE is configured with more than two SPS configurations, (ii) the first SPS configuration among the more than two SPS configurations is for unicast, (iii) the UE is configured with sps-ConfigIndex, and / or (iv) a command is used to activate or deactivate the first SPS configuration for unicast, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 3, 4 and / or 5, and / or the value of the HARQ process number field in the command may be set and / or used according to options 3, 4 and / or 5.

[0258] Alternatively and / or in addition, according to Table 2, if (i) the UE is configured with more than two SPS configurations, (ii) a first SPS configuration among the more than two SPS configurations is used for unicast, (iii) one or more second SPS configurations among the more than two SPS configurations are used for multicast, (iv) the UE is configured with sps-ConfigIndex, and / or (v) a command is used to activate or deactivate one or more second SPS configurations for multicast, then a command (e.g., an activation or deactivation command) may be generated and / or used according to Option 4, and / or the value of the HARQ process number field in the command may be set and / or used according to Option 4.

[0259] Alternatively and / or in addition, according to Table 2, if (i) the UE is configured with more than two SPS configurations including one or more SPS configurations for unicast and one or more SPS configurations for multicast, (ii) the UE is configured with sps-ConfigIndex, and / or (iii) a command is used to activate or deactivate one or more SPS configurations for unicast and one or more SPS configurations for multicast, then a command (e.g., an activation or deactivation command) may be generated and / or used according to Option 4, and / or the value of the HARQ process number field in the command may be set and / or used according to Option 4.

[0260]

[0261]

[0262] Table 2. Example implementation for DL ​​SPS.

[0263] In an example, if two SPS configurations are configured for unicast and multicast, respectively, and the SPS ID is not configured for unicast, the UE may check whether the value of the HARQ process number field is equal to zero (according to option 3), or may skip this field (according to option 5) in response to receiving a command (e.g., an activation or deactivation command) on a PDCCH addressed to the CS-RNTI (e.g., when receiving a command).

[0264] In an example, if a single SPS configuration with an SPS ID is configured for multicast (and, for example, no other SPS configuration is configured for unicast), the UE may consider the value of the HARQ process number field as the SPS ID of the SPS configuration and may perform activation or deactivation (according to option 4) for the corresponding SPS configuration corresponding to the SPS ID indicated by the value of the HARQ process number field, or skip this field (according to option 5) in response to receiving a command (e.g., an activation or deactivation command) on a PDCCH addressed to the G-CS-RNTI (e.g., when the command is received).

[0265] According to one or more of the techniques of the present disclosure, one or more options are provided for handling the HARQ process number field in a context associated with a configuration grant (CG) and / or UL SPS. The one or more options may include option 6, option 7, and / or option 8, which may be applied to the different conditions shown in Table 3.

[0266] In option 6, the UE may determine whether to verify a command (e.g., a command to schedule and / or direct activation or deactivation of a UL SPS configuration and / or a CG configuration) based on whether the value of the HARQ process number field is equal to a predefined value (e.g., zero, e.g., where all values ​​of the HARQ process number field are set to zero). For example, according to option 6, if the value of the HARQ process number field is equal to a predefined value (e.g., only when the value of the HARQ process number field is equal to the predefined value), then the UE may verify the command (e.g., if all values ​​of the HARQ process number field are set to zero, then the UE may verify the command).

[0267] In option 7, the UE may treat the value of the HARQ process number field as an identifier (e.g., ConfiguredGrantConfigIndex) indicating a configuration (e.g., UL SPS configuration and / or CG configuration), and / or may perform activation or deactivation (e.g., based on a command) for the configuration identified by the HARQ process number field. For example, the UE may activate or deactivate the configuration in response to a verification command (e.g., based on a command including the HARQ process number field). In some instances, in option 7, the UE may determine whether to verify the command based on one or more other fields (other than the HARQ process number field) in the command (e.g., the HARQ process number field may not be used to determine whether to verify the command). For example, the HARQ process number field may not be used (e.g., applied and / or considered) in the verification of the PDCCH.

[0268] In option 8, the UE may skip the HARQ process number field. For example, the HARQ process number field may not be used (eg, applied and / or considered) for validation (eg, the HARQ process number field may not be used to validate a command including the HARQ process number field).

[0269] For example, according to Table 3, if (i) the UE is configured with a single CG configuration and (ii) the UE is not configured with ConfiguredGrantConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 6 and / or 8, and / or the value of the HARQ process number field in the command may be set and / or used according to options 6 and / or 8.

[0270] Alternatively and / or additionally, according to Table 3, if (i) the UE is configured with a single CG configuration, and (ii) the UE is configured with ConfiguredGrantConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to options 7 and / or 8, and / or the value of the HARQ process number field in the command may be set and / or used according to options 7 and / or 8.

[0271] Alternatively and / or additionally, according to Table 3, if (i) the UE is configured with multiple CG configurations, and (ii) the UE is configured with ConfiguredGrantConfigIndex, then a command (e.g., an activation or deactivation command) may be generated and / or used according to Option 7, and / or the value of the HARQ process number field in the command may be set and / or used according to Option 7.

[0272]

[0273] Table 3. Example embodiments for UL SPS / CG.

[0274] According to system A, the network may use sps-Config or sps-ConfigToAddModList to configure the UE with a DL SPS configuration for unicast (e.g., only one DL SPS configuration for unicast). For example, the DL SPS configuration may correspond to the only DL SPS configuration configured by the UE. In some instances, using sps-Config (rather than, for example, sps-ConfigToAddModList) is more efficient, simpler, and / or reduces the overhead of a radio resource control (RRC) message (e.g., an RRC message carrying the sps-Config) (e.g., saves some signaling overhead). For example, using sps-Config (rather than, for example, sps-ConfigToAddModList) may be more efficient, simpler, and / or may reduce overhead due to the presence of only one DL SPS configuration (e.g., the UE is configured with the DL SPS configuration). However, if at least one DL SPS configuration for multicast is also configured at the same time (e.g., at the same time as the unicast DL SPS configuration is configured via sps-Config), then verification of SPS activation or deactivation for the unicast DL SPS configuration may have some problems. In this case, more than one DL SPS configuration is configured, so the value of the HARQ process number field will indicate which SPS configuration should be used for activation or deactivation in the case of implementation verification. However, there is no SPS ID configured for unicast DL SPS configuration, so it may be difficult or impossible for the network to perform activation or deactivation (for example, the network may not be able to recognize the unicast DL SPS configuration because there is no SPS ID configured for unicast DL SPS configuration via sps-Config).

[0275] According to one or more of the techniques of the present disclosure, Embodiment 1, Embodiment 2, and Embodiment 3 are provided.

[0276] Example 1

[0277] In Embodiment 1, the network may configure an SPS ID (e.g., using sps-ConfigToAddModList) for a unicast SPS configuration (e.g., the only SPS configuration configured by the UE). For example, the network may always configure an SPS ID (e.g., using sps-ConfigToAddModList) for a unicast SPS configuration that the network configures for the UE (e.g., the network may not configure the UE with a unicast SPS configuration that does not have an SPS ID).

[0278] Alternatively and / or in addition, in Embodiment 1, the network may configure the UE non-in parallel (e.g., simultaneously) with (i) an SPS (e.g., a unicast SPS) for a UE using an sps-Config for unicast (e.g., a unicast SPS configuration without an SPS ID) and (ii) an SPS (e.g., a multicast SPS) for a UE using an sps-ConfigMulticastToAddModList for multicast (e.g., a multicast SPS configuration with an SPS ID). For example, the UE may be configured non-in parallel (e.g., simultaneously) with both a unicast SPS configuration (e.g., without an SPS ID) configured via an sps-Config for unicast and a multicast SPS configuration (with an SPS ID) via an sps-ConfigMulticastToAddModList for multicast. Alternatively and / or in addition, in Embodiment 1, the network may configure the UE non-in parallel (e.g., simultaneously) with (i) an SPS (e.g., a unicast SPS) in a first bandwidth part (Bandwidth Part, BWP) (e.g., one BWP) for a UE using sps-Config for unicast (e.g., a unicast SPS configuration without an SPS ID) and (ii) an SPS (e.g., a multicast SPS) in a first BWP for a UE using sps-ConfigMulticastToAddModList for multicast (e.g., a multicast SPS configuration with an SPS ID). For example, in a first BWP (e.g., one BWP), the UE may be non-in parallel (e.g., simultaneously) configured with both a unicast SPS configuration (e.g., without an SPS ID) configured via sps-Config for unicast and a multicast SPS configuration (with an SPS ID) via sps-ConfigMulticastToAddModList for multicast.

[0279] Example 2

[0280] In embodiment 2, the UE may check (e.g., further check) whether the command (e.g., activation or deactivation command) is for unicast. If the command is for unicast, the UE may (i) use the HARQ process number field in the command to determine whether to verify the command (e.g., the HARQ process number field may be considered and / or applied in the verification of the command), for example, where if the value of the HARQ process number field is equal to a predefined value (e.g., zero, for example, where all values ​​of the HARQ process number field are set to zero) (e.g., only when the value of the HARQ process number field is equal to the predefined value), then the UE verifies the command, or (ii) skip the HARQ process number field (e.g., the HARQ process number field may not be used for verification).

[0281] Example 3

[0282] In embodiment 3, the UE may consider the SPS ID of a unicast SPS configuration (e.g., the only SPS configuration configured by the UE) as zero (e.g., the UE may not be configured with an SPS ID for the unicast SPS configuration, and / or the UE may assume that the SPS ID of the unicast SPS configuration is zero), wherein the UE may not use the HARQ process number field in verification of a command including the HARQ process number field (e.g., the UE may not use the HARQ process number field to determine whether to verify the command).

[0283] To save signaling (e.g., reduce signaling overhead) and / or reduce latency, the network may configure the UE with an SPS deactivation state list containing multiple deactivation states. Each state entry (of the SPS deactivation state list) may be mapped to one or more SPS configurations to be deactivated. When the UE receives a deactivation command on the PDCCH, the HARQ process number field of the PDCCH may be used to indicate which state to apply for deactivation. Figure 5 In the example shown in , UE C is configured with four SPS configurations (e.g., unicast SPS configurations associated with SPS ID 2 and SPS ID 3, and multicast SPS configurations associated with SPS ID 4 and SPS ID 5), and a deactivation list including six deactivation states (e.g., 1, 2, 3, 4, 5, and 6). The first deactivation state "1" corresponds to SPS ID 2 and SPS ID 3, the second deactivation state "2" corresponds to SPS ID 2, the third deactivation state "3" corresponds to SPS ID 3, the fourth deactivation state "4" corresponds to SPS ID 4, the fifth deactivation state "5" corresponds to SPS ID 5, and / or the sixth deactivation state "6" corresponds to SPS ID 2, SPS ID 3, and SPS ID 5. If UE C receives a deactivation command with a value of the HARQ process number field = 6 (e.g., the HARQ process number field indicates that the deactivation command applies to the SPS configuration associated with the sixth deactivation state "6"), then UE C may deactivate three SPS configurations with SPS ID = 2, 3, and 5 (associated with the sixth deactivation state "6"). For example, the three SPS configurations may be deactivated (e.g., in response to the deactivation command) at the same time. How to design a deactivation state list for multicast DL SPS operation may be further analyzed.

[0284] One or more of the techniques provided herein may be used to implement (e.g., design) a deactivation state list for multicast DL SPS operation. Figure 5In the example shown in , if the UE has been configured with a deactivation list for unicast DL SPS, the UE may or may not apply the deactivation list for the G-CS-RNTIs configured by the UE (e.g., all G-CS-RNTIs configured by the UE).

[0285] In some instances, the network may configure whether the G-CS-RNTI configured by the UE (e.g., all G-CS-RNTIs configured by the UE) are applicable to the deactivation list (e.g., whether the deactivation list is applicable to all G-CS-RNTIs configured by the UE).

[0286] In some examples, for each G-CS-RNTI configured by the UE, the network may configure whether a deactivation list applies to the G-CS-RNTI. In an example, even if a state in the deactivation list is associated with (e.g., includes) an SPS ID for multicast, the UE may still not apply the list for one or more G-CS-RNTIs configured by the UE (e.g., the UE may not apply the list for all G-CS-RNTIs configured by the UE).

[0287] In some instances, the deactivation list may correspond to a shared list shared among the UE and other UEs in the UE group (e.g., the UE and the other UEs may be configured with the deactivation list). In some instances, a deactivation list according to table 520 may be used (e.g., the deactivation list may correspond to "a list" in table 520). In some instances, according to table 520, whether the deactivation list is applicable to one or more CS-RNTIs (the UE is configured with the one or more CS-RNTIs) may be based on one or more technologies associated with system A and / or other systems.

[0288] In some examples, the UE may be configured with a first list for unicast (eg, a first deactivation list) and a second list for multicast (eg, a second deactivation list). The first list may correspond to Figure 5 The second list may correspond to "List 1" in Table 520 of , and / or may be used in conjunction with one or more CS-RNTIs (the UE is configured with the one or more CS-RNTIs). Figure 5 “List 2” in Table 520 of , and / or may be used in conjunction with one or more G-CS-RNTIs (e.g., all G-CS-RNTIs) configured by the UE.

[0289] In some examples, the network may configure the G-CS-RNTIs to be applied to the second list for multicast (e.g., all G-CS-RNTIs configured by the UE). For example, the UE may apply the second list for multicast to the G-CS-RNTIs (e.g., all G-CS-RNTIs configured by the UE). For example, the UE may apply the second list for multicast to the G-CS-RNTIs (e.g., all G-CS-RNTIs configured by the UE) based on a configuration provided to the UE (e.g., by the network).

[0290] In some examples, for each G-CS-RNTI configured by the UE, the network may configure whether the second list for multicast is applied to the G-CS-RNTI. In an example, even if the state in the second list for multicast is associated with (e.g., includes) the SPS ID for multicast, the UE may still not apply the second list for multicast for one or more G-CS-RNTIs configured by the UE (e.g., the UE may not apply the second list for multicast for all G-CS-RNTIs configured by the UE).

[0291] In some examples, the UE may be configured with multiple lists, where each of the multiple lists may be associated with one or more G-CS-RNTIs (e.g., one or more G-CS-RNTIs configured by the UE). For example, the UE may be configured with multiple lists for multicast (e.g., multiple deactivation lists for multicast), where each of the multiple lists applies to one or more G-CS-RNTIs (e.g., the UE is configured with the one or more G-CS-RNTIs).

[0292] In some examples, a G-CS-RNTI (e.g., each G-CS-RNTI) may be configured with a dedicated list (e.g., the dedicated list may only apply to the G-CS-RNTI). For example, a UE may be configured with one or more dedicated lists, where each dedicated list is used in conjunction with a G-CS-RNTI.

[0293] In some instances, if (i) the UE is configured with a deactivation state list (e.g., the UE is configured with only one deactivation list) and (ii) an SPS configuration for unicast is not configured (e.g., the UE is not configured with any SPS configuration for unicast), then the UE may consider the deactivation state list to be applicable to multicast (e.g., the UE may apply the deactivation state list for one or more G-CS-RNTIs configured by the UE). Alternatively and / or in addition, if (i) the UE is configured with a deactivation state list (e.g., the UE is configured with only one deactivation list) and (ii) an SPS configuration for unicast (e.g., any SPS configuration for unicast) is configured (e.g., the UE is configured with any SPS configuration for unicast), then the UE may not consider the deactivation state list to be applicable to multicast (e.g., the UE may not apply the deactivation state list for the G-CS-RNTI configured by the UE). Therefore, whether the UE applies a deactivation state list may depend on whether an SPS configuration for unicast is configured (e.g., whether the UE is configured with any SPS configuration for unicast).

[0294] In some instances, considering that not all UEs in the same group (e.g., a group of UEs using the same G-CS-RNTI) have the same SPS configuration for multicast and / or unicast, the network may assign (e.g., always assign) the SPS ID for multicast to a deactivated state, where the state entry is equal to the SPS ID. Figure 5 In the example shown in , UE C is configured with SPS ID=4 and 5 for multicast, where SPS ID=4 is assigned to state entry=4 (e.g., the fourth deactivation state "4") and / or SPS ID=5 is assigned to state entry=5 (e.g., the fifth deactivation state "5"). For example, state entry=4 may cover SPS ID=4 and / or state entry=5 may cover SPS ID=5. In an example, a UE (e.g., UE C) may use a deactivation state list (and / or one or more other deactivation state lists) for both unicast (e.g., CS-RNTI) and multicast (e.g., one or more G-CS-RNTIs).

[0295] In order to enhance the 3GPP specification for wireless communication according to some embodiments herein, enhancements 1 to 4 are provided herein. Enhancements 1 to 4 reflect implementations according to some embodiments herein and include modifications to various sections of the 3GPP specification. According to some embodiments, one, some, and / or all of enhancements 1 to 4 may be implemented, and / or a portion of one, some, and / or all of enhancements 1 to 4 may be implemented.

[0296] In some instances, the UE may receive first information (e.g., an RRC message) to configure more than one DL SPS configuration, wherein the more than one DL SPS configuration includes at least one SPS configuration for unicast and at least one SPS configuration for multicast (each SPS configuration is associated with an SPS ID). The UE may receive second information (e.g., an RRC message) to configure a (single) deactivation state list, wherein each state entry in the deactivation state list is associated with one or more SPS IDs and the SPS ID may be associated with multicast and / or unicast. The UE may receive third information (e.g., a PDCCH or DCI format) for deactivation, wherein the third information includes at least a HARQ process number field indicating a first value. If the third information is associated with multicast (e.g., addressed to a G-CS-RNTI), the UE may deactivate an SPS configuration by treating the first value as an SPS ID. If the third information is associated with unicast (e.g., addressed to G-CS-RNTI), the UE may deactivate for one or more SPS configurations by regarding the first value as a deactivation state (entry), wherein the deactivation state (entry) is associated with unicast and the one or more SPS configurations. More specifically, the first information and the second information may be the same or different RRC messages.

[0297] Enhancements 1 to 2 include modifications to Section 5.4.6 (named “Power Headroom Reporting”) of 3GPP 38.321 v16.6.0.

[0298] In Enhancement 1, Additions 1 to 3 and / or Removals 1 to 3 are made to Section 10.2 of R1-2202951. To distinguish Addition X (e.g., Addition 1, Addition 2, Addition 3) from the content originally included in Section 10.2 of R1-2202951, Addition X is in bold and is preceded by the term "ADDITION X STARTS:" (e.g., "ADDITION 1 STARTS:") and followed by the term "ADDITION X ENDS" (e.g., "ADDITION 1 ENDS"). To show that a portion of Section 10.2 of R1-2202951 is removed via Removal X (e.g., Removal 1, Removal 2, Removal 3), Removal X is in bold and is preceded by the term "REMOVAL X STARTS:" (e.g., "REMOVAL 1 STARTS:") and followed by the term "REMOVAL X ENDS" (e.g., "REMOVAL 1 ENDS").

[0299] Enhancement 1:

[0300] 10.2 PDCCH Verification for DL ​​SPS and UL Grant Type 2

[0301] The UE verifies the DL SPS allocation PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or scheduling release in the following cases:

[0302] […]

[0303] If the UE is provided with a single configuration for UL grant type 2 PUSCH or ADDITION 1 ENDS SPS PDSCH for ADDITION 1 STARTS: unicast, then validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-1 or Table 10.2-2.

[0304] If more than one configuration ADDITION2STARTS: for UL grant type 2 PUSCH or for SPS PDSCH or a single configuration ADDITION 2ENDS for SPS PDSCH for multicast is provided to the UE, then the value of the HARQ Process Number field in the DCI format indicates the activation of the configuration for the corresponding UL grant type 2 PUSCH or for SPS PDSCH with the same value as provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively. If the RV field of the DCI format is set as in Table 10.2-3, then the verification of the DCI format is achieved.

[0305] If more than one configuration ADDITION 3 STARTS for UL grant type 2 PUSCH or for SPS PDSCH is provided to the UE: or a single configuration ADDITION 3 ENDS for SPS PDSCH for multicast

[0306] - If ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList is provided to the UE, the value of the HARQ Process Number field in DCI format indicates the corresponding entry for scheduling the release of one or more UL Grant Type 2 PUSCH or SPS PDSCH configurations

[0307] - If ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList is not provided to the UE, the value of the HARQ Process Number field in the DCI format indicates the release for the corresponding UL grant type 2 PUSCH, or for the release of the SPS PDSCH configuration having the same value as that provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively.

[0308] If all fields of the DCI format are set according to Table 10.2-4, then validation of the DCI format is achieved.

[0309] […]

[0310] Table 10.2-1: Special fields for single DL SPS or single UL grant type 2 scheduling activation PDCCH verification when a single SPS PDSCH or UL grant type 2 configuration is provided to the UE in the active DL / UL BWP of the scheduled cell

[0311]

[0312] Table 10.2-2: Special fields for single DL SPS or single UL grant type 2 scheduling release PDCCH validation when single SPS PDSCH or UL grant type 2 configuration is provided to the UE in the active DL / UL BWP of the scheduled cell

[0313]

[0314] In Enhancement 2, additions 4 to 7 and / or removals 4 to 9 are made to Section 10.2 of R1-2202951. To distinguish an addition X (e.g., addition 4, addition 5, addition 6, addition 7) from what was originally included in Section 10.2 of R1-2202951, the addition X is in bold and is preceded by the term "ADDITION X STARTS:" (e.g., "ADDITION 4 STARTS:") and followed by the term "ADDITION X ENDS" (e.g., "ADDITION 4 ENDS"). To show the portion of Section 10.2 of R1-2202951 that was removed via removal X (e.g., removal 4, removal 5, removal 6, removal 7, removal 8, removal 9), the removal X is in bold and is preceded by the term "REMOVAL X STARTS:" (e.g., "REMOVAL 4 STARTS:") and followed by the term "REMOVAL 4 ENDS" (e.g., "REMOVAL 1 ENDS").

[0315] Enhancement 2:

[0316] 10.2 PDCCH Verification for DL ​​SPS and UL Grant Type 2

[0317] The UE verifies the DL SPS allocation PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or scheduling release in the following cases:

[0318] […]

[0319] If ADDITION 4STARTS: no ADDITION 4ENDS for UL grant type 2 PUSCH or ADDITION 5STARTS: ConfiguredGrantConfigIndex or sps-ConfigIndexADDITION 5ENDS REMOVAL 4STARTS: single configurationREMOVAL 4ENDS for SPS PDSCH is provided to the UE, then verification of the DCI format is achieved with all fields for the DCI format set according to Table 10.2-1 or Table 10.2-2.

[0320] If the UE is provided with ADDITION 6STARTS:ConfiguredGrantConfigIndex or sps-ConfigIndex ADDITION 6ENDS REMOVAL 5STARTS:more than one configuration REMOVAL 5ENDS for UL grant type 2 PUSCH or for SPS PDSCH, then the value of the HARQ Process Number field in the DCI format indicates the activation of the configuration for the corresponding UL grant type 2 PUSCH or for SPS PDSCH with the same value as provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively. If the RV field of the DCI format is set as in Table 10.2-3, then verification of the DCI format is achieved.

[0321] If the UE is provided with ADDITION 7STARTS: ConfiguredGrantConfigIndex or sps-ConfigIndex for UL grant type 2 PUSCH or for SPS PDSCH ADDITION 7ENDS REMOVAL 6STARTS: More than one configuration REMOVAL 6ENDS

[0322] - If ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList is provided to the UE, the value of the HARQ Process Number field in DCI format indicates the corresponding entry for scheduling the release of one or more UL Grant Type 2 PUSCH or SPS PDSCH configurations

[0323] - If ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList is not provided to the UE, the value of the HARQ Process Number field in the DCI format indicates the release for the corresponding UL grant type 2 PUSCH, or for the release of the SPS PDSCH configuration having the same value as that provided by ConfiguredGrantConfigIndex or by sps-ConfigIndex, respectively.

[0324] If all fields of the DCI format are set according to Table 10.2-4, then validation of the DCI format is achieved.

[0325] […]

[0326] Table 10.2-1: Special fields for single DL SPS or single UL grant type 2 scheduling activation PDCCH verification when a single SPS PDSCH or UL grant type 2 configuration is provided to the UE in the active DL / UL BWP of the scheduled cell

[0327]

[0328] Table 10.2-2: Special fields for single DL SPS or single UL grant type 2 scheduling release PDCCH validation when single SPS PDSCH or UL grant type 2 configuration is provided to the UE in the active DL / UL BWP of the scheduled cell

[0329]

[0330]

[0331] In Enhancement 3, Additions 8 to 9 are made to R2-2204251. To distinguish Addition X (e.g., Addition 8, Addition 9) from what was originally included in R2-2204251, Addition X is in bold and is preceded by the term "ADDITION X STARTS:" (e.g., "ADDITION 8 STARTS:") and followed by the term "ADDITION X ENDS" (e.g., "ADDITION 8 ENDS").

[0332] Enhancement 3:

[0333]

[0334]

[0335] In Enhancement 4, additions 10 to 13 are made to R2-2204251. To distinguish addition X (e.g., addition 10, addition 11, addition 12, addition 13) from what was originally included in R2-2204251, addition X is in bold and is preceded by the term "ADDITION X STARTS:" (e.g., "ADDITION 10 STARTS:") and followed by the term "ADDITION X ENDS" (e.g., "ADDITION 10 ENDS").

[0336] Enhancement 4:

[0337] -SPS-Config

[0338] IESPS-Config is used to configure downlink semi-static transmission. Multiple downlink SPS configurations can be configured in one BWP of the serving cell. SPS-Config information element

[0339]

[0340]

[0341]

[0342]

[0343] One, some and / or all of the examples, options, techniques and / or embodiments disclosed herein may be formed and / or combined into new embodiments.

[0344] In some examples, the embodiments disclosed herein, such as the embodiments described with respect to each of Options 1 to 8 and / or Embodiments 1 to 3, may be implemented independently and / or separately. Alternatively and / or additionally, the embodiments described herein, such as a combination of the embodiments described with respect to one, some and / or all of Options 1 to 8 and / or Embodiments 1 to 3, may be implemented. Alternatively and / or additionally, the embodiments described herein, such as a combination of the embodiments described with respect to one, some and / or all of Options 1 to 8 and / or Embodiments 1 to 3, may be implemented in parallel and / or simultaneously.

[0345] The various techniques, embodiments, methods and / or alternatives of the present disclosure may be performed independently and / or separately from each other. Alternatively and / or in addition, the various techniques, embodiments, methods and / or alternatives of the present disclosure may be combined and / or implemented using a single system. Alternatively and / or in addition, the various techniques, embodiments, methods and / or alternatives of the present disclosure may be implemented in parallel and / or simultaneously.

[0346] In some embodiments, in the present disclosure, one, some and / or all instances of the term "sps-ConfigIndex information element" may be replaced by and / or used interchangeably with the term "sps-ConfigIndex," the term "sps-ConfigIndex parameter" and / or the term "sps-ConfigIndex field."

[0347] In some embodiments, in the present disclosure, one, some and / or all instances of the term "sps-Config information element" may be replaced by and / or used interchangeably with the term "sps-Config", the term "sps-Config parameter" and / or the term "sps-Config field".

[0348] In some embodiments, one, some and / or all instances of the term "sps-ConfigToAddModList information element" in the present disclosure may be replaced by and / or used interchangeably with the term "sps-ConfigToAddModList," the term "sps-ConfigToAddModList parameter" and / or the term "sps-ConfigToAddModList field."

[0349] In some embodiments, in the present disclosure, one, some and / or all instances of the term "sps-ConfigMulticastToAddModList information element" may be replaced by and / or used interchangeably with the term "sps-ConfigMulticastToAddModList", the term "sps-ConfigMulticastToAddModList parameter" and / or the term "sps-ConfigMulticastToAddModList field".

[0350] Figure 6 600 is a flow chart according to an exemplary embodiment from the perspective of a base station operating with SPS for unicast and multicast. In step 605, the base station configures the UE with SPS operation for unicast by using sps-Config or sps-ConfigToAddModList. In step 610, if sps-Config is used to configure SPS operation for unicast, the base station is not allowed to configure the UE with SPS operation for multicast by using sps-ConfigMulticastToAddModList. In step 615, if sps-ConfigToAddModList is used to configure SPS operation for unicast, the base station is allowed to configure (and / or configurable) the UE with SPS operation for multicast by using sps-ConfigMulticastToAddModList.

[0351] Return to reference Figure 3 and 4 In an exemplary embodiment of a base station for SPS operation for unicast and multicast, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the base station to: (i) configure the UE for SPS operation for unicast by using sps-Config or sps-ConfigToAddModList; (ii) if sps-Config is used to configure SPS operation for unicast, then it is not allowed to configure the UE for SPS operation for multicast by using sps-ConfigMulticastToAddModList; and (iii) if sps-ConfigToAddModList is used to configure SPS operation for unicast, then it is allowed to configure (and / or configure) the UE for SPS operation for multicast by using sps-ConfigMulticastToAddModList. In addition, the CPU 308 can execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0352] Figure 7 It is a flowchart 700 according to an exemplary embodiment from the perspective of a base station for SPS operation for unicast and multicast. In step 705, the base station configures the UE with the SPS operation for multicast by using sps-ConfigMulticastToAddModList. In step 710, the base station is not allowed to configure the UE with the SPS operation for unicast by using sps-Config. For example, based on the UE configured with the SPS operation for multicast, the base station may not be allowed to use sps-Config to configure the UE with the SPS operation for unicast. In step 715, the base station is allowed to configure (and / or configurable) UE with the SPS operation for unicast by using sps-ConfigToAddModList. For example, when the UE is configured with the SPS operation for multicast, the base station may be allowed to use sps-ConfigToAddModList to configure the UE with the SPS operation for unicast.

[0353] Return to reference Figure 3 and 4 In an exemplary embodiment of a base station for SPS operation for unicast and multicast, the apparatus 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the base station to: (i) configure the UE for SPS operation for multicast by using sps-ConfigMulticastToAddModList; (ii) not be allowed to configure the UE for SPS operation for unicast by using sps-Config; and (iii) be allowed to configure the UE for SPS operation for unicast by using sps-ConfigToAddModList. In addition, the CPU 308 can execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0354] Figure 8Flowchart 800 according to an exemplary embodiment is a perspective of a base station configuring a UE with SPS operation for unicast of sps-Config or sps-ConfigToAddModList and for multicast of sps-ConfigMulticastToAddModList. In step 805, the base station configures the UE with SPS operation for multicast by using sps-ConfigMulticastToAddModList. In step 810, the base station configures the UE with SPS operation for unicast by using sps-ConfigToAddModList (e.g., the base station configures the UE with SPS operation for unicast by always using sps-ConfigToAddModList), wherein the base station is not allowed to use sps-Config to configure the UE with SPS operation for unicast. In step 815, the base station transmits an activation or deactivation command to the UE to activate or deactivate SPS operation for multicast or unicast.

[0355] Return to reference Figure 3 and 4 In an exemplary embodiment of a base station that configures a UE with SPS operation for unicast for sps-Config or sps-ConfigToAddModList and for multicast for sps-ConfigMulticastToAddModList, the device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the base station to: (i) configure the UE with SPS operation for multicast by using sps-ConfigMulticastToAddModList; (ii) configure the UE with SPS operation for unicast by using (e.g., always using) sps-ConfigToAddModList, wherein the base station is not allowed to use sps-Config to configure the UE with SPS operation for unicast; and (iii) transmit an activation or deactivation command to the UE to activate or deactivate SPS operation for multicast or unicast. In addition, the CPU 308 can execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0356] Relative to Figures 6 to 8 In one embodiment, the base station may configure only the UE for SPS operation for unicast by using sps-Config or sps-ConfigToAddModList.

[0357] Fig. 9Flowchart 900 according to an exemplary embodiment from the perspective of a UE for SPS operation for unicast and multicast. In step 905, the UE is configured with SPS operation for unicast by using sps-Config or sps-ConfigToAddModList. In step 910, if sps-Config is used to configure SPS operation for unicast, it is not expected to configure the UE with SPS operation for multicast by using sps-ConfigMulticastToAddModList. In step 915, if sps-ConfigToAddModList is used to configure SPS operation for unicast, it is expected to configure (and / or can be configured with the SPS operation configuration for multicast) the UE by using sps-ConfigMulticastToAddModList.

[0358] Return to reference Figure 3 and 4 In an exemplary embodiment of a UE for SPS operation for unicast and multicast, the device 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the UE to: (i) configure the SPS operation for unicast by using sps-Config or sps-ConfigToAddModList; (ii) if sps-Config is used to configure the SPS operation for unicast, then it is not expected to use sps-ConfigMulticastToAddModList for the SPS operation configuration for multicast; and (iii) if sps-ConfigToAddModList is used to configure the SPS operation for unicast, then it is expected to use sps-ConfigMulticastToAddModList for the SPS operation configuration for multicast (and / or to be configured with the SPS operation configuration for multicast). In addition, the CPU 308 can execute the program code 312 to perform one, some and / or all of the above actions and steps and / or other actions and steps described herein.

[0359] Fig.101000 is a flow chart according to an exemplary embodiment from the perspective of a UE operating with SPS for unicast and multicast. In step 1005, the UE is configured with SPS operation for multicast by sps-ConfigMulticastToAddModList. In step 1010, it is not expected to configure the UE with SPS operation for unicast by sps-Config. In step 1015, it is expected to configure (and / or configure) the UE with SPS operation for unicast by using sps-ConfigToAddModList. In step 1020, the UE receives an activation or deactivation command to activate or deactivate SPS operation for multicast or unicast (e.g., in the case of configuration).

[0360] Return to reference Figure 3 and 4 In an exemplary embodiment of a UE for SPS operation for unicast and multicast, the device 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the UE to: (i) configure SPS operation for multicast through sps-ConfigMulticastToAddModList; (ii) not expect SPS operation configuration for unicast through sps-Config; (iii) expect SPS operation configuration for unicast by using sps-ConfigToAddModList (and / or to be configured); and (iv) receive an activation or deactivation command to activate or deactivate SPS operation for multicast or unicast (for example, if configured). In addition, the CPU 308 can execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0361] Relative to Figures 6 to 10 In one embodiment, sps-Config corresponds to a UE-specific SPS configuration for unicast (eg, a single UE-specific SPS configuration for unicast).

[0362] In one embodiment, sps-ConfigToAddModList corresponds to a list of one or more SPS configurations including SPS index information (and / or other information) for each SPS configuration for unicast.

[0363] In one embodiment, sps-ConfigMulticastToAddModList corresponds to a list of one or more SPS configurations including SPS index information (and / or other information) for each SPS configuration used for multicast.

[0364] Fig.111100 is a flowchart according to an exemplary embodiment from the perspective of a base station operating with SPS for unicast and multicast. In step 1105, the base station uses a first information element including an sps-Config information element or an sps-ConfigToAddModList information element to configure the UE with a unicast SPS operation configuration. Configuring the UE with a unicast SPS operation configuration may include using a first information element (e.g., by transmitting the first information element to the UE) to configure the UE with an SPS operation for unicast. For example, the UE may perform an SPS operation for unicast using a (configured) unicast SPS operation configuration. In step 1110, the base station determines whether to use the sps-ConfigMulticastToAddModList information element to configure the UE with a multicast SPS operation configuration based on whether the first information element includes an sps-Config information element or an sps-ConfigToAddModList information element.

[0365] In some instances, if the base station configures the UE with a unicast SPS operation configuration using an sps-Config information element (e.g., if the first information element includes an sps-Config information element), the unicast SPS operation configuration may be configured without an SPS ID (e.g., sps-ConfigIndex).

[0366] In some instances, if the base station configures the UE with a unicast SPS operation configuration using an sps-ConfigToAddModList information element (e.g., if the first information element includes an sps-ConfigToAddModList information element), then the SPS ID (e.g., sps-ConfigIndex) may be used to configure the unicast SPS operation configuration. For example, an SPS ID may be assigned to a unicast SPS operation configuration.

[0367] In one embodiment, the base station determines not to use the sps-ConfigMulticastToAddModList information element to configure the UE with a multicast semi-persistent scheduling operation configuration based on the first information element including the sps-Config information element. For example, the base station may configure the UE with a multicast SPS operation configuration based on the first information element including the sps-Config information element without using the sps-ConfigMulticastToAddModList information element (e.g., due to configuring a unicast SPS operation configuration without an SPS ID).

[0368] In one embodiment, if the first information element includes the sps-Config information element, the base station is not allowed to configure the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element (e.g., not configured to configure and / or prohibited from configuring). For example, based on the first information element including the sps-Config information element, the base station may not be allowed to configure the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element (e.g., due to configuring a unicast SPS operation configuration without an SPS ID).

[0369] In one embodiment, the base station determines to use the sps-ConfigMulticastToAddModList information element to configure the UE with a multicast semi-persistent scheduling operation configuration based on a first information element including the sps-ConfigToAddModList information element. For example, the base station may use the sps-ConfigMulticastToAddModList information element to configure the UE with a multicast SPS operation configuration based on a first information element including the sps-ConfigToAddModList information element (e.g., because a unicast SPS operation configuration is configured with an SPS ID).

[0370] In one embodiment, if the first information element includes the sps-ConfigToAddModList information element, the base station is allowed (e.g., configured to) configure the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element. For example, based on the first information element including the sps-ConfigToAddModList information element, the base station may be allowed to configure the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element (e.g., due to configuring the unicast SPS operation configuration with the SPS ID).

[0371] In one embodiment, the base station is only configured to (e.g., only able to) configure the UE with a unicast SPS operation configuration using one of the sps-Config information element or the sps-ConfigToAddModList information element. For example, the base station may not be configured to (e.g., may not be able to) configure the UE with a unicast SPS operation configuration using an information element different from one of the sps-Config information element or the sps-ConfigToAddModList information element.

[0372] In one embodiment, the sps-Config information element corresponds to a UE-specific unicast SPS operation configuration. For example, the sps-Config information element may be used by the UE (and, e.g., not by other UEs) to configure a unicast SPS operation configuration that may be used by the UE for operation with unicast SPS (and, e.g., may not be used by other UEs for operation with unicast SPS).

[0373] In one embodiment, the sps-ConfigToAddModList information element corresponds to a list of one or more unicast SPS operation configurations. The list of one or more unicast SPS operation configurations includes SPS index information (and / or other information) for each unicast SPS operation configuration in the list of one or more unicast SPS operation configurations (e.g., the SPS index information may indicate an SPS ID of the unicast SPS operation configuration).

[0374] In one embodiment, the sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast SPS operation configurations. The list of one or more multicast SPS operation configurations includes SPS index information (and / or other information) for each multicast SPS operation configuration in the list of one or more multicast SPS operation configurations (e.g., the SPS index information may indicate an SPS ID of the multicast SPS operation configuration).

[0375] Return to reference Figure 3 and 4 In an exemplary embodiment of a base station operating with SPS for unicast and multicast, the apparatus 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the base station to: (i) configure the UE with a unicast SPS operation configuration using a first information element including an sps-Config information element or an sps-ConfigToAddModList information element; and determine whether to configure the UE with a multicast SPS operation configuration using an sps-ConfigMulticastToAddModList information element based on whether the first information element includes an sps-Config information element or an sps-ConfigToAddModList information element. In addition, the CPU 308 may execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0376] Fig.12It is a flowchart 1200 according to an exemplary embodiment from the perspective of a base station for SPS operation for unicast and multicast. In step 1205, the base station uses the sps-ConfigMulticastToAddModList information element to configure the UE with a multicast SPS operation configuration. Configuring the UE with a multicast SPS operation configuration may include using the sps-ConfigMulticastToAddModList information element (e.g., by transmitting the sps-ConfigMulticastToAddModList information element to the UE) to configure the UE with an SPS operation for multicast. For example, the UE may use (configured) multicast SPS operation configuration to perform SPS operation for multicast. The base station is not allowed to use the sps-Config information element to configure the UE with a unicast SPS operation configuration (e.g., not configured to configure and / or prohibit configuration). Allow (e.g., configure) the base station to use the sps-ConfigToAddModList information element to configure the UE with a unicast SPS operation configuration.

[0377] In some instances, when the sps-ConfigMulticastToAddModList information element is used to configure the UE with a multicast SPS operation configuration, the base station is not allowed to use the sps-Config information element to configure the UE with a unicast SPS operation configuration. This can avoid configuring the UE with a unicast SPS operation configuration that does not have an SPS ID when the UE is (already) configured with a multicast SPS operation configuration.

[0378] In one embodiment, the base station configures the UE with a first unicast SPS operation configuration using the sps-ConfigToAddModList information element. For example, the base station may transmit the sps-ConfigToAddModList information element to the UE, and the UE may configure the first unicast SPS operation configuration using the sps-ConfigToAddModList information element and / or may perform SPS operations for unicast using the first unicast SPS operation configuration. The unicast SPS operation configuration may be configured with an SPS ID (e.g., sps-ConfigIndex). For example, the SPS ID may be assigned to the unicast SPS operation configuration.

[0379] In one embodiment, the base station transmits a command (e.g., an activation or deactivation command) to the UE to activate or deactivate the first unicast SPS operation configuration or the multicast SPS operation configuration. In some instances, the command may include a HARQ process number field indicating the SPS ID of the first unicast SPS operation configuration or the multicast SPS operation configuration. Based on the command, the UE may activate or deactivate the configuration identified by the SPS ID.

[0380] In one embodiment, the base station is only configured to (e.g., only able to) use the sps-Config information element or the sps-ConfigToAddModList information element to configure the UE with a unicast SPS operation configuration. For example, the base station may not be configured to (e.g., may not be able to) use an information element different from the sps-Config information element or the sps-ConfigToAddModList information element to configure the UE with a unicast SPS operation configuration.

[0381] In one embodiment, the sps-Config information element corresponds to a UE-specific unicast SPS operation configuration.

[0382] In one embodiment, the sps-ConfigToAddModList information element corresponds to a list of one or more unicast SPS operation configurations, wherein the list of one or more unicast SPS operation configurations includes SPS index information (and / or other information) for each unicast SPS operation configuration in the list of one or more unicast SPS operation configurations (e.g., the SPS index information may indicate the SPS ID of the unicast SPS operation configuration).

[0383] In one embodiment, the sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast SPS operation configurations, wherein the list of one or more multicast SPS operation configurations includes SPS index information (and / or other information) for each multicast SPS operation configuration in the list of one or more multicast SPS operation configurations (e.g., the SPS index information may indicate the SPS ID of the multicast SPS operation configuration).

[0384] Return to reference Figure 3 and 4 In an exemplary embodiment of a base station operating with SPS for unicast and multicast, the apparatus 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the base station to configure the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element, wherein the base station is not allowed to configure the UE with a unicast SPS operation configuration using the sps-Config information element, and the base station is allowed to configure the UE with a unicast SPS operation configuration using the sps-Config information element. In addition, the CPU 308 may execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0385] Fig.131300 is a flowchart according to an exemplary embodiment from the perspective of a UE operating with SPS for unicast and multicast. In step 1305, the UE receives a first information element including an sps-Config information element or an sps-ConfigToAddModList information element. In step 1310, the UE configures the unicast SPS operation configuration based on the first information element. For example, the UE can use (configured) unicast SPS operation configuration to perform SPS operation for unicast. In step 1315, based on the first information element including the sps-Config information element, the UE does not monitor the reception of the sps-ConfigMulticastToAddModList information element associated with the multicast SPS operation configuration configured for the UE. For example, if the first information element includes the sps-Config information element, it is not expected to use the sps-ConfigMulticastToAddModList information element to configure the UE with the multicast SPS operation configuration. Alternatively and / or additionally, based on the first information element including the sps-ConfigToAddModList information element, the UE monitors reception of a ConfigMulticastToAddModList information element associated with configuring a multicast SPS operation configuration for the UE (e.g., monitoring a channel, such as a DL channel). For example, if the first information element includes the sps-ConfigToAddModList information element, then it may be contemplated that the sps-ConfigMulticastToAddModList information element is used to configure the UE with the multicast SPS operation configuration.

[0386] In some instances, when the UE is configured with a unicast SPS operation configuration configured using the sps-Config information element (e.g., because the unicast SPS operation configuration configured using the sps-Config information element may not have an SPS ID), the UE may not listen for reception of the sps-ConfigMulticastToAddModList information element associated with the multicast SPS operation configuration configured for the UE (and / or may not expect to configure the UE with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element).

[0387] In one embodiment, the first information element includes an sps-ConfigToAddModList information element. During the period of monitoring reception of the sps-ConfigMulticastToAddModList information element, the UE receives the sps-ConfigMulticastToAddModList information element. The UE configures the multicast SPS operation configuration based on the received sps-ConfigMulticastToAddModList information element. The UE may use the multicast SPS operation configuration to perform SPS operation for multicast.

[0388] In one embodiment, the sps-Config information element corresponds to a UE-specific unicast SPS operation configuration, and the sps-ConfigToAddModList information element corresponds to a list of one or more unicast SPS operation configurations.

[0389] In one embodiment, the list of one or more unicast SPS operation configurations includes SPS index information (and / or other information) for each unicast SPS operation configuration in the list of one or more unicast SPS operation configurations (e.g., the SPS index information may indicate the SPS ID of the unicast SPS operation configuration).

[0390] In one embodiment, the received sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast SPS operation configurations, wherein the list of one or more multicast SPS operation configurations includes SPS index information (and / or other information) for each multicast SPS operation configuration in the list of one or more multicast SPS operation configurations (for example, the SPS index information may indicate the SPS ID of the multicast SPS operation configuration).

[0391] Return to reference Figure 3 and 4In an exemplary embodiment of a UE operating with SPS for unicast and multicast, the apparatus 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the UE to: (i) receive a first information element including an sps-Config information element or an sps-ConfigToAddModList information element; (ii) configure a unicast SPS operation configuration based on the first information element; and (iii) (A) based on the first information element including the sps-Config information element, not monitor the reception of the sps-ConfigMulticastToAddModList information element associated with the multicast SPS operation configuration configured for the UE, or (B) based on the first information element including the sps-ConfigToAddModList information element, monitor the reception of the sps-ConfigMulticastToAddModList information element associated with the multicast SPS operation configuration configured for the UE. In addition, the CPU 308 may execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0392] Fig.14 It is a flowchart 1400 according to an exemplary embodiment from the perspective of a UE for unicast and multicast SPS operation. In step 1405, the UE receives the sps-ConfigMulticastToAddModList information element. In step 1410, the UE configures the multicast SPS operation configuration based on the sps-ConfigMulticastToAddModList information element. In step 1415, the UE does not monitor the reception of the sps-Config information element associated with the configuration unicast SPS operation configuration (e.g., the unicast SPS operation configuration without SPS ID). For example, it is not expected to configure the UE with the unicast SPS operation configuration using the sps-Config information element. In step 1420, the UE monitors (e.g., monitors a channel, such as a DL channel) the reception of the sps-ConfigToAddModList information element associated with the configuration unicast SPS operation configuration (e.g., the unicast SPS operation configuration with SPS ID). For example, it is expected to configure the UE with the unicast SPS operation configuration using the sps-ConfigToAddModList information element.

[0393] In some instances, when the UE is configured with a multicast SPS operation configuration using the sps-ConfigMulticastToAddModList information element, the UE does not listen for reception of an sps-Config information element associated with configuring a unicast SPS operation configuration (and / or may not expect to configure the UE with a unicast SPS operation configuration using the sps-Config information element), which can avoid configuring the UE with a unicast SPS operation configuration that does not have an SPS ID when the UE is (already) configured with a multicast SPS operation configuration.

[0394] In one embodiment, the UE receives the sps-ConfigToAddModList information element. In some instances, the UE receives the sps-ConfigToAddModList information element while monitoring the sps-ConfigToAddModList information element. The UE configures the unicast SPS operation configuration based on the received sps-ConfigToAddModList information element. The UE may use the unicast SPS operation configuration to perform SPS operations for unicast.

[0395] In one embodiment, the UE receives a command (e.g., an activation or deactivation command) to activate or deactivate a unicast SPS operation configuration configured based on a received sps-ConfigToAddModList information element. In some instances, based on the command, the UE activates or deactivates a unicast SPS operation configuration configured based on a received sps-ConfigToAddModList information element. In some instances, the command may include a HARQ process number field indicating an SPS ID of a unicast SPS operation configuration configured based on a received sps-ConfigToAddModList information element. Based on the command, the UE may activate or deactivate a unicast SPS operation configuration identified by an SPS ID.

[0396] In one embodiment, the UE receives a command (e.g., an activation or deactivation command) to activate or deactivate a multicast SPS operation configuration configured based on a received sps-ConfigMulticastToAddModList information element. In one embodiment, based on the command, the UE activates or deactivates the multicast SPS operation configuration. In some instances, the command may include a HARQ process number field indicating an SPS ID of the multicast SPS operation configuration. Based on the command, the UE may activate or deactivate the multicast SPS operation configuration identified by the SPS ID.

[0397] In one embodiment, the sps-Config information element corresponds to a UE-specific unicast SPS operation configuration, or the sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast SPS operation configurations.

[0398] In one embodiment, the list of one or more multicast SPS operation configurations includes SPS index information (and / or other information) for each multicast SPS operation configuration in the list of one or more multicast SPS operation configurations (e.g., the SPS index information may indicate an SPS ID of the multicast SPS operation configuration).

[0399] In one embodiment, the received sps-ConfigToAddModList information element corresponds to a list of one or more unicast SPS operation configurations, wherein the list of one or more unicast SPS operation configurations includes SPS index information (and / or other information) for each unicast SPS operation configuration in the list of one or more unicast SPS operation configurations (for example, the SPS index information may indicate the SPS ID of the unicast SPS operation configuration).

[0400] Return to reference Figure 3 and 4 In an exemplary embodiment of a UE operating with SPS for unicast and multicast, the apparatus 300 includes program code 312 stored in the memory 310. The CPU 308 may execute the program code 312 to enable the UE to: (i) receive an sps-ConfigMulticastToAddModList information element; (ii) configure a multicast SPS operation configuration based on the sps-ConfigMulticastToAddModList information element; (iii) not monitor the reception of an sps-Config information element associated with configuring a unicast SPS operation configuration; and (iv) monitor the reception of an sps-ConfigToAddModList information element associated with configuring a unicast SPS operation configuration. In addition, the CPU 308 may execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.

[0401] A communication device (e.g., a UE, a network node, such as a base station and / or a gNB, etc.) may be provided, wherein the communication device may include a control circuit, a processor disposed in the control circuit, and / or a memory disposed in the control circuit and coupled to the processor. The processor may be configured to execute a program code stored in the memory to perform Figures 6 to 14In addition, the processor may execute program code to perform one, some and / or all of the above actions and steps and / or other actions and steps described herein.

[0402] A computer readable medium may be provided. The computer readable medium may be a non-transitory computer readable medium. The computer readable medium may include a flash memory device, a hard disk drive, a disk (e.g., a magnetic disk and / or an optical disk, such as at least one of a digital versatile disc (DVD), a compact disc (CD), etc.), and / or a memory semiconductor, such as at least one of a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), etc. The computer readable medium may include processor executable instructions that, when executed, cause the execution of the processor executable instructions. Figures 6 to 14 One, some and / or all of the method steps depicted in and / or one, some and / or all of the actions and steps described above and / or other actions and steps described herein.

[0403] It will be appreciated that application of one or more of the techniques presented herein may result in one or more benefits, including, but not limited to, increased communication efficiency between devices (e.g., one or more UEs and / or base stations), for example at least in part due to enabling and / or improving verification of SPS deactivation for unicast and / or multicast.

[0404] Various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more aspects of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, by using other structures, functionality, or structures and functionality other than one or more aspects of the aspects set forth herein or different from one or more aspects of the aspects set forth herein, this device can be implemented or this method can be practiced. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and time hopping sequences.

[0405] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0406] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the various aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, analog implementation, or a combination of the two that may be designed using source decoding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein as "software" or "software modules" for convenience), or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0407] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. An IC may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0408] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of an exemplary method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present the elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0409] The steps of the method or algorithm described in conjunction with the various aspects disclosed herein can be implemented directly with hardware, with a software module executed by a processor, or with a combination of the two. Software modules (e.g., containing executable instructions and related data) and other data can reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of a computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine can be referred to as a "processor" in this article) so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium can be integrated with a processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user equipment. In an alternative, the processor and the storage medium can reside in a user equipment as discrete components. Alternatively and / or in addition, in some aspects, any suitable computer program product can include a computer-readable medium, and the computer-readable medium includes a code related to one or more of the aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.

[0410] Although the disclosed subject matter has been described in conjunction with various aspects, it will be understood that the disclosed subject matter is capable of further modification. This application is intended to cover any changes, uses, or adaptations of the disclosed subject matter that generally follow the principles of the disclosed subject matter and include deviations from the present disclosure that occur within the scope of known and customary practice in the art to which the disclosed subject matter relates.

[0411] CROSS-REFERENCE TO RELATED APPLICATIONS

[0412] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 323,664, filed on March 25, 2022, the entire disclosure of which is incorporated herein by reference in its entirety.

Claims

1. A method for semi-static scheduling operation of a base station for unicast and multicast, characterized in that: The method comprises: configuring a user equipment (UE) with a unicast semi-persistent scheduling operation configuration using a first information element including an sps-Config information element or an sps-ConfigToAddModList information element; Based on the first information element including the sps-Config information element, using the sps-ConfigMulticastToAddModList information element to configure the user equipment with a multicast semi-persistent scheduling operation configuration is not allowed; and Based on the first information element including the sps-ConfigToAddModList information element, it is allowed to use the sps-ConfigMulticastToAddModList information element to configure the user equipment with a multicast semi-persistent scheduling operation configuration, in, The sps-Config information element corresponds to a unicast semi-persistent scheduling operation configuration specific to the user equipment; The sps-ConfigToAddModList information element corresponds to a list of one or more unicast semi-static scheduling operation configurations, wherein the list of one or more unicast semi-static scheduling operation configurations includes semi-static scheduling index information for each unicast semi-static scheduling operation configuration of the list of one or more unicast semi-static scheduling operation configurations; The sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast semi-static scheduling operation configurations, wherein the list of one or more multicast semi-static scheduling operation configurations includes semi-static scheduling index information for each multicast semi-static scheduling operation configuration in the list of one or more multicast semi-static scheduling operation configurations.

2. The method according to claim 1, characterized in that: The base station determines, based on the first information element including the sps-ConfigToAddModList information element, to configure the user equipment with the multicast semi-persistent scheduling operation configuration using the sps-ConfigMulticastToAddModList information element.

3. The method according to claim 1, characterized in that: The base station is configured to configure the user equipment in a unicast semi-persistent scheduling operation configuration using only one of: the sps-Config information element; or The sps-ConfigToAddModList information element.

4. A method for semi-static scheduling operation of a base station for unicast and multicast, characterized in that: The method comprises: The sps-ConfigMulticastToAddModList information element is used to configure the user equipment (UE) with a multicast semi-persistent scheduling operation configuration, where: not allowing the base station to configure the user equipment with a unicast semi-persistent scheduling operation configuration using the sps-Config information element; and allowing the base station to configure the user equipment with a unicast semi-persistent scheduling operation configuration using the sps-ConfigToAddModList information element, in, The sps-Config information element corresponds to a unicast semi-persistent scheduling operation configuration specific to the user equipment; The sps-ConfigToAddModList information element corresponds to a list of one or more unicast semi-static scheduling operation configurations, wherein the list of one or more unicast semi-static scheduling operation configurations includes semi-static scheduling index information for each unicast semi-static scheduling operation configuration of the list of one or more unicast semi-static scheduling operation configurations; The sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast semi-static scheduling operation configurations, wherein the list of one or more multicast semi-static scheduling operation configurations includes semi-static scheduling index information for each multicast semi-static scheduling operation configuration in the list of one or more multicast semi-static scheduling operation configurations.

5. The method according to claim 4, characterized in that include: The user equipment is configured with a first unicast semi-persistent scheduling operation configuration using the sps-ConfigToAddModList information element.

6. The method according to claim 5, characterized in that include: A command to activate or deactivate the first unicast semi-persistent scheduling operation configuration or the multicast semi-persistent scheduling operation configuration is transmitted to the user equipment.

7. The method according to claim 4, characterized in that: The base station is only configured to configure the user equipment with a unicast semi-persistent scheduling operation configuration using only the sps-Config information element or the sps-ConfigToAddModList information element.

8. A method for semi-persistent scheduling operation of user equipment for unicast and multicast, characterized in that: The method comprises: Receive the sps-ConfigMulticastToAddModList information element; Configuring a multicast semi-static scheduling operation configuration based on the sps-ConfigMulticastToAddModList information element; not listening for reception of an sps-Config information element associated with configuring a unicast semi-persistent scheduling operation configuration; and monitors the reception of the sps-ConfigToAddModList information element associated with configuring a unicast semi-persistent scheduling operation configuration, Wherein, the sps-Config information element corresponds to a unicast semi-static scheduling operation configuration specific to the user equipment; The sps-ConfigMulticastToAddModList information element corresponds to a list of one or more multicast semi-static scheduling operation configurations, wherein the list of one or more multicast semi-static scheduling operation configurations includes semi-static scheduling index information for each multicast semi-static scheduling operation configuration of the list of one or more multicast semi-static scheduling operation configurations; The received sps-ConfigToAddModList information element corresponds to a list of one or more unicast semi-static scheduling operation configurations, wherein the list of one or more unicast semi-static scheduling operation configurations includes semi-static scheduling index information for each unicast semi-static scheduling operation configuration in the list of one or more unicast semi-static scheduling operation configurations.

9. The method according to claim 8, characterized in that include: Receive the sps-ConfigToAddModList information element; as well as The unicast semi-persistent scheduling operation configuration is configured based on the received sps-ConfigToAddModList information element.

10. The method according to claim 9, characterized in that include: A command is received to activate or deactivate the unicast semi-persistent scheduling operation configuration configured based on the received sps-ConfigToAddModList information element.

11. The method according to claim 9, characterized in that include: Receive a command to activate or deactivate the multicast semi-persistent scheduling operation configuration configured based on the sps-ConfigMulticastToAddModList information element.

Images