Method executed by user equipment, and user equipment

Abstract

Provided in the present invention are a method executed by user equipment (UE) and the user equipment. The method executed by the user equipment comprises: according to a first PDSCH bandwidth parameter and MCCH change notification information in a DCI and / or a distance between a first PDSCH and a second PDSCH, the UE determines a processing of the first PDSCH. The first PDSCH is a PDSCH scheduled by the DCI. The second PDSCH is the next PDSCH received by the UE after the first PDSCH. The processing of the first PDSCH comprises, when the first PDSCH bandwidth is greater than a preset value and the MCCH change notification information indicates that the distance between the first PDSCH and the second PDSCH is greater than a preset value, the UE receives the first PDSCH. Therefore, the user equipment can determine the PDSCH processing according to the actual PDSCH transmission condition, such that eRedCapUE can update MBS configuration information in time, user service is guaranteed, and the UE and the network efficiency are improved.

Description

Method performed by user equipment and user equipment Technical Field

[0001] The present invention relates to the technical field of wireless communications, and in particular to a method executed by a user equipment and corresponding user equipment. Background Art

[0002] This section introduces various aspects that may help to better understand the present invention. Therefore, the statements in this section should be read in this light and should not be understood as an admission of what is or is not prior art.

[0003] Several typical applications have been defined in 5G systems. For example, industrial wireless sensor applications aim to accelerate industrial transformation and digitalization, enabling greater flexibility in industrial production processes, improving productivity and efficiency, reducing maintenance, and enhancing operational safety. Video surveillance equipment is being used in smart city development to facilitate better urban management and services. Wearable devices can be used for intelligent services in healthcare, daily life, and other areas. Devices for these applications are expected to be less complex and consume less power to reduce costs and expand their scope. Release 17 reduces the bandwidth of some device types from 100 MHz to 20 MHz, thereby reducing device costs. To further reduce terminal device complexity, new approaches can be adopted, such as reducing the peak data rate supported by these devices to around 10 Mbps or further reducing the user equipment bandwidth from a maximum of 20 MHz to a maximum of 5 MHz. These approaches, or a combination of them, can further reduce device complexity and lower costs at various levels. At the same time, the coexistence of these devices with other types of NR user equipment in the same cell must be considered to maintain ecosystem integrity, maximize ecosystem scale, and improve network efficiency. These new service demands place new demands on existing NR networks. For example, if a network supports user equipment with a data transmission bandwidth of no more than 5MHz, network configuration parameters or the resource parameters used by terminals for data transmission must meet relevant requirements. Furthermore, the impact of common channel configuration and scheduling within the cell on system deployment must be considered. The methods of the present invention provide a better approach for meeting these device requirements within the network. While meeting relevant constraints, they can ensure coexistence with existing devices within the network, achieving better network utilization efficiency.

[0004] Summary of the Invention

[0005] To address at least some of the aforementioned issues, the present invention provides a method and user equipment, which enable the user equipment to determine PDSCH processing based on actual PDSCH transmission conditions, enabling the eRedCap UE to promptly update MBS configuration information and ensure user service. Furthermore, the network can flexibly schedule resources used by network users to receive MBS services, thereby improving network efficiency.

[0006] According to the present invention, a method performed by a user equipment (UE) is provided, comprising: the UE determining processing of a first PDSCH based on a first PDSCH bandwidth parameter and MCCH change notification information indicated in a DCI, and / or a distance between the first PDSCH and a second PDSCH; wherein the first PDSCH is a PDSCH scheduled by the DCI; and the second PDSCH is the first PDSCH received by the UE after the first PDSCH; the processing of the PDSCH comprises, when the first PDSCH bandwidth is greater than a predetermined value, and the MCCH change notification information indicates an MCCH change, or the distance between the first PDSCH and the second PDSCH is greater than a predetermined value, the UE receiving the first PDSCH. The predetermined value of the bandwidth may be determined based on an SCS used by the PDSCH.

[0007] In the above method, the MCCH change notification information may indicate an MCCH change, and the LSB low-order bit of the MCCH change notification field in the DCI format 4_0 scrambled with MCCH-RNTI is 1.

[0008] In the above method, the distance between the first PDSCH and the second PDSCH may be the number of time slots between the time slot where the first PDSCH is located and the time slot where the second PDSCH is located.

[0009] In the above method, the distance between the first PDSCH and the second PDSCH may be the number of symbols between the last symbol of the first PDSCH and the first symbol of the second PDSCH.

[0010] In addition, according to the present invention, a user equipment is proposed, comprising: a processor; and a memory storing instructions, wherein the instructions execute the above method when executed by the processor.

[0011] Effects of the Invention

[0012] According to the present invention, the user equipment can determine whether relevant data processing is required according to actual scheduling parameters to achieve the goal of communicating with the network, and can enable the network to flexibly schedule resources for network users to receive MBS services, thereby improving network efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0014] FIG1 shows a method executed by a user equipment UE according to an embodiment of the present invention.

[0015] FIG2 shows another method performed by a user equipment UE according to an embodiment of the present invention.

[0016] FIG3 is a schematic diagram illustrating multi-beam scheduling and PDSCH transmission in a cell according to an embodiment of the present invention.

[0017] FIG4 is a block diagram showing a simplified structure of a user equipment UE according to the present invention. DETAILED DESCRIPTION

[0018] The present invention is described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention is not limited to the specific embodiments described below, which are provided merely as examples to convey the scope of the subject matter to those skilled in the art. In addition, for the sake of brevity, detailed descriptions of known technologies not directly related to the present invention are omitted to prevent confusion in understanding the present invention.

[0019] Generally, unless clearly given and / or implied different meanings in the context of using the term, all terms used in this article will be interpreted according to their ordinary meaning in the relevant technical field. Unless clearly stated, all references to one element, device, assembly, part, step, etc. should be openly interpreted as referring to at least one instance of this element, device, assembly, part, step, etc. Unless a step must be clearly described as being after or before another step and / or implicitly a step must be after or before another step, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Equally, any advantage of any embodiment may be applicable to any other embodiment, and vice versa.

[0020] The following describes multiple embodiments of the present invention using the 5G / NR mobile communication system and its subsequent evolutionary versions as example application environments. However, it should be noted that the present invention is not limited to the following embodiments, but is applicable to many other wireless communication systems, such as communication systems after 5G and 4G and 3G mobile communication systems before 5G, 802.11 wireless networks, and the like.

[0021] The following describes some of the terms used in this disclosure. Unless otherwise specified, the terms used in this disclosure are defined herein. The terms used in this disclosure may be named differently in LTE, LTE-Advanced, LTE-Advanced Pro, NR, and later or other communication systems. However, this disclosure uses unified terminology. When applied to a specific system, the terms can be replaced with those used in the corresponding system.

[0022] 3GPP: 3rd Generation Partnership Project

[0023] LTE: Long Term Evolution

[0024] NR: New Radio, New Wireless, New Air Interface

[0025] UE: User Equipment

[0026] gNB: NR base station

[0027] FR1: Frequency range 1 as defined in TS 38.104, frequency range 1 defined by TS38.104

[0028] FR2: Frequency range 2 as defined in TS 38.104, frequency range 2 defined by TS38.104

[0029] BWP: BandWidth Part, bandwidth fragment / part

[0030] SFN: System frame number, system frame number

[0031] OFDM: Orthogonal Frequency Division Multiplexing

[0032] CP: Cyclic Prefix

[0033] TA: Timing Advance, uplink timing advance

[0034] SCS: sub-carrier spacing, sub-carrier spacing

[0035] TDD: Time Division Duplexing

[0036] FDD: Frequency Division Duplexing

[0037] DCI: Downlink Control Information, downlink control information

[0038] MCS: Modulation and Coding Scheme, modulation and coding scheme

[0039] HARQ: Hybrid Automatic Repeat Request

[0040] CORESET: Control resource set, control resource set

[0041] MIB: Master Information Block

[0042] SIB: system information block

[0043] SIB1: System Information Block Type 1, system information block type 1

[0044] SSB: SS / PBCH block, synchronization signal / physical broadcast channel block

[0045] PSS: Primary Synchronization Signal

[0046] SSS: Secondary Synchronization Signal

[0047] SRS: Sounding Reference Signal, detection reference signal

[0048] DMRS: Demodulation Reference Signal

[0049] CSI-RS: Channel State Information Reference Signal

[0050] TRS: Tracking Reference Signal

[0051] RACH: random-access channel, random access channel

[0052] PBCH: Physical broadcast channel

[0053] PUCCH: Physical Uplink Control Channel, physical uplink control channel

[0054] PUSCH: Physical Uplink Shared Channel, physical uplink shared channel

[0055] PRACH: Physical random-access channel, physical random access channel

[0056] PDSCH: Physical downlink shared channel, physical downlink shared channel

[0057] PDCCH: Physical downlink control channel, physical downlink control channel

[0058] UL-SCH: Uplink Shared Channel, uplink shared channel

[0059] DL-SCH: Downlink Shared Channel, uplink shared channel

[0060] RNTI: Radio Network Temporary Identifier, wireless network temporary identification number

[0061] MBS: Multicast / Broadcast Service

[0062] MTCH: MBS Traffic Channel, MBS service information channel

[0063] MCCH: MBS Control Channel, MBS control information channel

[0064] MCCH-RNTI: MBS Control Channel RNTI, MBS control information channel RNTI

[0065] G-RNTI: Group RNTI, group RNTI

[0066] G-CS-RNTI: Group Configured SchedulingRNTI, configured scheduling group RNTI

[0067] MRB: MBS Radio Bearer

[0068] QCL: Quasi co-location

[0069] The following is a description of the technology associated with the present invention. Unless otherwise specified, the same terms in the embodiments and the related technology have the same meanings.

[0070] It is worth noting that the user, user equipment, and terminal equipment mentioned in this specification are synonymous. The term "UE" may also be used to refer to user equipment, and no specific distinction or limitation is made in the following text. Similarly, network equipment refers to equipment that communicates with user equipment, including but not limited to base stations, gNBs, eNBs, wireless access points, wireless relays, and terminals with relay capabilities. No specific distinction or limitation is made in the following text. A base station may be used as one form of network equipment implementation for illustration purposes, and other forms of network equipment can be easily substituted in specific implementations.

[0071] The network can provide users with MBS (Multicast and Broadcast Services) services. When using broadcast services in MBS services, the same service is used for all UEs in the cell, that is, all UEs in the cell (which have been authenticated by higher layers to support the MBS service) can receive the relevant control information channel MCCH and service information channel MTCH to implement related service functions. The UE can receive MBS configuration information for broadcast sessions transmitted through MCCH, such as a list of all broadcast service sessions being transmitted through MTCH, and related broadcast session information, such as MBS session ID, MTCH scheduling information, MTCH service information of neighboring cells, etc. The MCCH content is transmitted periodically in a time domain window determined by parameters such as the MCCH repetition period, MCCH window length and offset. MTCH is used to transmit information about related service channels, and the PDSCH scheduled by the G-RNTI scrambled DCI for broadcast is used to transmit service information for broadcasting MTCH.

[0072] MCCH uses the DCI with MCCH-RNTI scrambled CRC to schedule PDSCH transmission, and the corresponding PDSCH can be recorded as MCCH-PDSCH. MTCH uses the DCI with G-RNTI scrambled CRC to schedule PDSCH transmission, and the corresponding PDSCH can be recorded as MTCH-PDSCH. For example, DCI format 4_0 with MCCH-RNTI or G-RNTI scrambled CRC may be used to schedule MCCH-PDSCH or MTCH-PDSCH. MTCH-PDSCH may also be transmitted using time slot repetition, that is, MTCH is repeatedly transmitted on multiple consecutive time slots, and the UE can perform related merging to obtain better reception performance. The bandwidth information of the scheduled PDSCH carried in the DCI includes the number of PRBs, and the symbol information includes the symbol position and the number of symbols. The UE can determine the time-frequency position of the resources used by the relevant PDSCH based on the DCI.

[0073] UEs in RRC states RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED can receive MBS broadcast services.

[0074] Depending on the needs of the service, the content of MCCH transmission may change. MCCH uses a modification period parameter to assist the MCCH change process, and the content of MCCH will only change in each adjustment period. The network uses MCCH change notification to notify the UE. When the UE receives the change notification indicating the MCCH change, the UE obtains the updated MCCH within the adjustment period in which the notification is received. For example, the network can indicate the change notification by setting certain field domains of the DCI that schedules MCCH-PDSCH, that is, the DCI that uses MCCH-RNTI to scramble CRC.

[0075] Specifically, when using DCI format 4_0 with MCCH-RNTI scrambled CRC, a 2-bit MCCH change notification field (MCCH change notification) is used in the DCI to indicate relevant MCCH change information. For example, when the high-order bit (MSB) is set to 1, it indicates the start of one or more new MBS services. When the low-order bit (LSB) is set to 1, it indicates an MCCH change other than the start of a new MBS service, such as a configuration change of an ongoing MBS session, an MBS session stop, or a change in neighboring cell information, etc. In addition, when the CRC of DCI format 4_0 is scrambled by G-RNTI, this field is a reserved field and is not used to indicate an MCCH change notification.

[0076] When a UE starts receiving an MBS broadcast service, it should apply the MCCH acquisition procedure to acquire the MCCH. For example, the UE should apply the MCCH acquisition procedure to acquire the MCCH after receiving SIB20. Furthermore, a UE receiving broadcast MRB data should apply the MCCH information acquisition procedure upon receiving an MCCH information change message, and the change is due to an MCCH information adjustment rather than simply the start of a new MBS service (i.e., the LSB bit in the DCI is set to 1).

[0077] MCCH contains the configuration information of all broadcast services in the cell, as well as the configuration information of neighboring cell broadcast services. If there are a variety of broadcast services in the network, the corresponding MCCH transmission content will be relatively large, requiring more physical resources for transmission. On the other hand, MCCH information changes usually use an overlay storage method, that is, the MCCH information acquisition process overwrites any stored MCCH information, that is, the incremental modification method is not used, and if the field does not exist in the MCCH information, the UE does not use the corresponding historical configuration. Therefore, for the initially configured MCCH or the MCCH containing a change indication, the network may use more physical resources for transmission when using PDSCH to transmit the MCCH.

[0078] For example, according to the relevant description in TS38.331-h40, the MCCH information acquisition process includes:

[0079] If the process is triggered by an MCCH information change notification, the UE obtains the MBSBroadcastConfiguration message on the MCCH starting from the timeslot in which the change notification is received in the connected cell. That is, the UE receives the PDSCH scheduled by the DCI containing the MCCH information change notification and obtains the MBSBroadcastConfiguration message transmitted on it.

[0080] If the UE receives a cell broadcasting SIB20 or the UE receives an sCellSIB20,

[0081] The UE obtains the MBSBroadcastConfiguration message on the MCCH starting from the next repetition period of the MCCH in the connected cell.

[0082] eRedCap is a terminal type that reduces terminal complexity by limiting bandwidth or peak rate. This can be identified, for example, by the supportOfRedCap-r18 parameter. eRedCap UEs can be divided into several subtypes based on the different feature parameter groups they use. For example, an eRedCap UE using the FG48-1 feature group in the FR1 band limits the number of PRBs used in some shared data channels to no more than the number corresponding to a 5 MHz bandwidth, i.e., 25 and 12 at SCSs of 15 kHz and 30 kHz, respectively. Other channels use no more than the number of PRBs corresponding to a 20 MHz bandwidth. An eRedCap UE using the FG48-2 feature group can use PRBs corresponding to a maximum bandwidth of 20 MHz, and its peak data transmission rate is limited to approximately 10 Mbps. The feature group parameters used by the UE are reported to the gNB through the UE capability reporting process.

[0083] eRedCap UEs can also support MBS services. To reduce the implementation complexity of eRedCap UEs, the bandwidth of the relevant channels used for MBS services can be limited. At the same time, to avoid affecting other UEs in the cell, ensure the flexibility of base station resource allocation, and ensure the reliability of UEs receiving MBS services, the present invention proposes a method for eRedCap UEs to determine the relevant reception based on the received information when receiving MBS services. This method enables the UE to determine PDSCH processing based on the actual PDSCH transmission situation, allowing the eRedCap UE to update MBS configuration information in a timely manner, ensuring user services and improving UE and network performance.

[0084] FIG1 shows a method executed by a user equipment UE according to an embodiment of the present invention.

[0085] As shown in Figure 1, in step S101, a UE receives a DCI containing an MCCH-RNTI scrambled CRC, which schedules a first PDSCH. The DCI includes bandwidth information of the scheduled PDSCH and indication bits related to MCCH change information.

[0086] In step S102 , the UE determines whether it needs to process the first PDSCH scheduled by the DCI according to the bandwidth information indicated in the DCI and the change information of the MCCH or the distance between the second PDSCH received by the UE and the first PDSCH.

[0087] FIG2 illustrates another method performed by a user equipment (UE) according to an embodiment of the present invention. As shown in FIG2 , in step S201, the UE receives a DCI containing a scrambled CRC and an MCCH-RNTI or a broadcast G-RNTI, which schedules a first PDSCH. The DCI includes bandwidth information for the scheduled PDSCH.

[0088] In step S202 , the UE determines whether it needs to process the first PDSCH scheduled by the DCI according to the bandwidth information of the first PDSCH indicated in the DCI or the RNTI associated with the second PDSCH received by the UE.

[0089] According to the above method, the eRedCap UE can determine the relevant receiving method according to the received information when receiving MBS services, so that the eRedCap UE can change the MBS configuration information in time, thereby improving the UE and network performance.

[0090] The relevant processes are described in detail below.

[0091] [Example 1]

[0092] When receiving MBS broadcast services, the eRedCap terminal first obtains MCCH information. MCCH contains a list of all broadcast service sessions in the cell that are being transmitted through MTCH, as well as related broadcast session information, such as MBS session ID, MTCH scheduling information, MTCH service information of neighboring cells, etc. The network uses DCI-scheduled PDSCH with MCCH-RNTI scrambled CRC to transmit MCCH information. The network uses periodic transmission to transmit MCCH, that is, when the UE is performing MBS broadcast services, if it has received MCCH and the valid time has not expired, and no MCCH changes have been received, the UE can assume that the relevant broadcast parameter configuration indicated by MCCH has not changed, and the relevant MCCH-PDSCH can be processed without processing. For eRedCap UEs, in order to reduce the burden on UEs to process data, when the bandwidth of the MCCH-PDSCH is greater than the maximum bandwidth of the dedicated PDSCH associated with the eRedCap UE according to the PDSCH bandwidth parameter in the DCI, the UE may require additional processing time or buffering to process it. At this time, if there is another PDSCH that needs to be processed in the next time slot or several symbols after the MCCH-PDSCH, the UE may not process the MCCH-PDSCH, that is, it can discard the PDSCH. In addition, when the MCCH is associated with an MCCH change, the UE should receive the MCCH information as soon as possible to obtain the latest configuration information to avoid interruption of MBS services. Similarly, similar problems exist for the MTCH-PDSCH scheduled by the DCI used to broadcast the G-RNTI scrambled CRC.

[0093] According to an exemplary embodiment, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception unless MCCH change notification information is present in the DCI that schedules the PDSCH and indicates an MCCH change; and the PDSCH satisfies the following conditions,

[0094] -The PDSCH is scheduled by the DCI of the MCCH-RNTI scrambled CRC.

[0095] -When the SCS is 15 kHz, the number of PRBs in its bandwidth is greater than 25; or when the SCS is 15 kHz, the number of PRBs is greater than 12.

[0096] - The UE receives another PDSCH after the PDSCH, and the distance between the another PDSCH and the PDSCH scheduled by the DCI is less than a predetermined value.

[0097] Here, eRedCap UEs that do not indicate feature group FG48-2 include several cases. The first case is for eRedCap UEs in the RRC_IDLE or RRC_INACTIVE states. Regardless of whether they use feature group FG48-1 or FG48-2, the UE has not yet reported its specific feature group type to the gNB. In this case, UEs that do not indicate feature group FG48-2 include UEs that use feature group FG48-1 or FG48-2. In the other case, for eRedCap UEs in the RRC_CONNECTED state, the relevant UE features have been reported to the gNB through the UE capability reporting procedure. In this case, UEs that do not indicate feature FG48-2 do not include eRedCap UEs that use feature group FG48-2.

[0098] The processing of PDSCH also includes several cases. If the DCI indicates an MCCH change and the number of PRBs of the PDSCH scheduled by the DCI is greater than 25 or 12 (corresponding to different SCSs, respectively), the UE should receive the PDSCH scheduled by the DCI. On the other hand, if the DCI indicates an MCCH change and the number of PRBs of the PDSCH scheduled by the DCI is greater than 25 or 12, the UE does not expect to be scheduled with another PDSCH within a predetermined distance.

[0099] Alternatively, if the DCI indicates an MCCH change, and the number of PRBs of the PDSCH scheduled by the DCI is greater than 25 or 12 (corresponding to different SCSs, respectively), and the UE is scheduled or configured with another PDSCH less than a predetermined distance, the UE should receive the PDSCH scheduled by the DCI and may not process the other PDSCH.

[0100] Additionally, when the number of PRBs for a DCI-scheduled PDSCH is no greater than 25 or 12, the bandwidth is no greater than the maximum bandwidth for eRedCap UE-dedicated PDSCH demodulation, and the UE can receive the PDSCH without additional restrictions. This includes receiving, decoding, and sending the PDSCH to higher layers upon verification. If the PDSCH is not processed, it can be discarded and feedback can be provided or not provided based on the relevant HARQ settings.

[0101] Optionally, the MCCH change is a change other than a change initiating a new MBS service. Specifically, the DCI corresponding to scheduling the MCCH-PDSCH indicates an MCCH information change, and the low-order bit (LSB) of the change notification field is 1.

[0102] Optionally, the UE determines the distance between another PDSCH received by the UE and the PDSCH scheduled by the DCI according to the distance in the time slot where the PDSCH is located. For example, the predetermined value may be one time slot. Specifically, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH on a time slot n, which is scheduled by a DCI with MCCH-RNTI scrambled CRC, when the SCS is 15kHz and the number of PRBs is greater than 25 or when the SCS is 15kHz and the number of PRBs is greater than 12, if the UE receives another PDSCH on the next time slot n+1; unless the MCCH change notification information in the DCI indicates an MCCH change.

[0103] Optionally, an eRedCap UE can process a PDSCH in time slot n that is scheduled by a DCI with MCCH-RNTI scrambled CRC and the number of PRBs for the PDSCH is greater than 25 when the SCS is 15 kHz or greater than 12 when the SCS is 30 kHz, if the DCI indicates an MCCH information change indication or there is no PDSCH to be received in time slot n+1.

[0104] Optionally, the processing of PDSCH scheduled by DCI with G-RNTI scrambled CRC is also considered. Specifically, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH on time slot n that is scheduled by DCI with G-RNTI or MCCH-RNTI scrambled CRC for broadcast, with a PRB number greater than 25 when the SCS is 15 kHz or a PRB number greater than 12 when the SCS is 15 kHz, if time slot repetition is configured for this PDSCH or the UE receives another PDSCH on the next time slot n+1, unless the MCCH change notification information in the DCI indicates an MCCH change.

[0105] Optionally, when determining the distance between another PDSCH received by the UE and the PDSCH scheduled by the DCI, the UE determines the distance between the last symbol of the PDSCH and the first symbol of the other PDSCH. The predetermined value may be the number of symbols of 1 time slot, for example, 14 when a normal CP is used. Specifically, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception that is scheduled by a DCI with an MCCH-RNTI scrambled CRC and a number of PRBs greater than 25 when the SCS is 15 kHz or a number of PRBs greater than 12 when the SCS is 15 kHz, if the UE receives another PDSCH and the interval between the last symbol of the PDSCH and the first symbol of the other PDSCH is less than the predetermined number of symbols.

[0106] Optionally, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception on time slot n, which is scheduled by DCI with MCCH-RNTI scrambled CRC, with the number of PRBs greater than 25 when the SCS is 15 kHz or the number of PRBs greater than 12 when the SCS is 15 kHz, if the UE receives another PDSCH and the interval from the last symbol of the PDSCH to the first symbol of the other PDSCH is less than a predetermined number of symbols; unless the MCCH change notification information in the DCI indicates an MCCH change.

[0107] Optionally, an eRedCap UE that does not indicate feature group FG48-2 does not need to process the reception of a PDSCH that is scheduled by DCI with G-RNTI or MCCH-RNTI scrambled CRC for broadcast, with the number of PRBs greater than 25 when the SCS is 15 kHz or the number of PRBs greater than 12 when the SCS is 15 kHz, if slot repetition is configured for that PDSCH or the UE receives another PDSCH and the interval from the last symbol of that PDSCH to the first symbol of that other PDSCH is less than a predetermined number of symbols.

[0108] Optionally, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception that is scheduled by a DCI with a G-RNTI or MCCH-RNTI scrambled CRC for broadcast, with the number of PRBs greater than 25 when the SCS is 15 kHz or the number of PRBs greater than 12 when the SCS is 15 kHz, if the PDSCH is configured with time slot repetition or the UE receives another PDSCH and the interval from the last symbol of the PDSCH to the first symbol of the other PDSCH is less than a predetermined number of symbols, unless the MCCH change notification information in the DCI indicates an MCCH change.

[0109] Optionally, when there may be multiple MCCH reception cycles in the MCCH change window, the UE uses the above method only on the first MCCH reception cycle in the change window.

[0110] [Example 2]

[0111] When receiving MBS broadcast services, the eRedCap terminal first obtains MCCH information. MCCH contains a list of all broadcast service sessions in the cell that are being transmitted through MTCH, as well as related broadcast session information, such as MBS session ID, MTCH scheduling information, MTCH service information of neighboring cells, etc. The network uses DCI-scheduled PDSCH with MCCH-RNTI scrambled CRC to transmit MCCH information. The network uses periodic transmission to transmit MCCH, that is, when the UE is performing MBS broadcast services, if it has received MCCH and the valid time has not expired, and no MCCH changes have been received, the UE can assume that the relevant broadcast parameter configuration indicated by MCCH has not changed, and the relevant MCCH-PDSCH can be processed without processing. For eRedCap UEs, to reduce the burden on UE data processing, when the bandwidth of the MCCH-PDSCH exceeds the maximum bandwidth of the dedicated PDSCH associated with the eRedCap UE according to the PDSCH bandwidth parameter in the DCI, the UE may require additional processing time or buffering to process it. At this time, if there is another PDSCH to be processed in the next time slot or several symbols after the MCCH-PDSCH, the UE may not process the MCCH-PDSCH, that is, it can discard the PDSCH. In addition, when the MCCH associated with an MCCH changes, the UE should receive the MCCH information as soon as possible to obtain the latest configuration information to avoid interruption of MBS services.

[0112] According to an exemplary embodiment, an eRedCap UE shall process a PDSCH reception that is scheduled by a DCI with an MCCH-RNTI scrambled CRC, and in which the MCCH change notification information in the DCI indicates an MCCH change. An eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception that is scheduled by a DCI with an MCCH-RNTI scrambled CRC for broadcast, that does not indicate an MCCH change, and that has a PRB number greater than 25 or 12, and at the same time, the UE receives another PDSCH at a distance less than a predetermined distance from the PDSCH.

[0113] The processing of PDSCH includes several cases. If the DCI indicates an MCCH change and the number of PRBs of the PDSCH scheduled by the DCI is greater than 25 or 12 (corresponding to different SCSs, respectively), the UE should receive the PDSCH scheduled by the DCI. On the other hand, if the DCI indicates an MCCH change and the number of PRBs of the PDSCH scheduled by the DCI is greater than 25 or 12, the UE does not expect to be scheduled with another PDSCH within a predetermined distance.

[0114] Alternatively, if the DCI indicates an MCCH change, and the number of PRBs of the PDSCH scheduled by the DCI is greater than 25 or 12 (corresponding to different SCSs, respectively), and the UE is scheduled or configured with another PDSCH at a distance less than a predetermined distance, the UE should receive MCCH-PDSCH and may not process the other PDSCH.

[0115] In addition, when the number of PRBs for a DCI-scheduled PDSCH is no greater than 25 or 12, the UE can also receive the PDSCH. Reception here includes receiving, decoding, and sending the PDSCH to higher layers if the verification is correct. If the PDSCH is not processed, it can be discarded and feedback may or may not be provided based on the relevant HARQ settings.

[0116] Optionally, the MCCH change is a change other than a change for initiating a new MBS service. Specifically, the DCI corresponding to the scheduling of the MCCH-PDSCH indicates an MCCH information change, and the LSB of the change notification field is 1. No MCCH change is indicated, which means that the DCI does not indicate an MCCH information change, and the LSB of the change notification field of the DCI is 0.

[0117] Optionally, the UE determines the distance between another PDSCH received by the UE and the PDSCH scheduled by the DCI based on the distance between the time slots in which the PDSCH is located. The predetermined value may be one time slot. Specifically, the eRedCap UE shall process a PDSCH reception, which is scheduled by a DCI with MCCH-RNTI scrambled CRC, and the MCCH change notification information in the DCI indicates the MCCH change. An eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception on a time slot n, which is scheduled by a DCI with MCCH-RNTI scrambled CRC for broadcast, which does not indicate an MCCH change, and the number of PRBs of the PDSCH is greater than 25 or 12, and at the same time, the UE receives another PDSCH in time slot n+1.

[0118] Optionally, when the UE determines the distance between another PDSCH received by the UE and the PDSCH scheduled by the DCI, it is based on the interval from the last symbol of the PDSCH to the first symbol of the other PDSCH. The predetermined value can be the number of symbols of 1 time slot, for example, 14 when using a normal CP. Specifically, the eRedCap UE should process a PDSCH reception that is scheduled by a DCI with an MCCH-RNTI scrambled CRC, and the MCCH change notification information in the DCI indicates an MCCH change. An eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception that is scheduled by a DCI with an MCCH-RNTI scrambled CRC for broadcast, the DCI does not indicate an MCCH change, and the number of PRBs of the PDSCH is greater than 25 or 12. At the same time, the UE is receiving another PDSCH, and the interval from the last symbol of the PDSCH to the first symbol of the other PDSCH is less than the predetermined number of symbols.

[0119] Optionally, when there may be multiple MCCH reception cycles in the MCCH change window, the UE uses the above method only on the first MCCH reception cycle in the change window.

[0120] [Example 3]

[0121] NR supports the use of beam or spatial parameters for data transmission to achieve better coverage. For example, in the FR1 frequency band, up to 4 or 8 beams can be used to transmit SSB, depending on the carrier frequency. Each beam can cover different areas in the cell, so that UEs in the cell can receive SSB with better performance. Other public or dedicated channels can also use beam transmission. For example, the spatial parameters are set using the relevant SSB beam as the QCL reference, and multiple beams are used to transmit PDCCH and PDSCH, where the PDCCH transmits DCI with SI-RNTI scrambled CRC and the PDSCH is scheduled by the DCI for transmitting system broadcast information, etc. When using this transmission method, the network transmits the same data on multiple beams, so that UEs receiving any beam can obtain the same content. A specific example is shown in Figure 3. PDCCH and PDSCH are transmitted using 4 beams with different QCL references in 4 consecutive time slots. The UE can select one or more for reception (based on measurement).

[0122] The network can also use this method when transmitting MBS broadcast channels. Depending on network configuration parameters, the same MCCH or MTCH data may be transmitted in consecutive time slots using beams with different QCL references. In this case, the UE only needs to receive the channel on a specific beam.

[0123] Optionally, a UE that does not indicate feature FG48-2 does not need to process a PDSCH reception on time slot n, which is scheduled by DCI with MCCH-RNTI scrambled CRC, with the number of PRBs greater than 25 when the SCS is 15 kHz or the number of PRBs greater than 12 when the SCS is 15 kHz, if the UE receives a second PDSCH on the next time slot n+1, unless the second PDSCH is a PDSCH scheduled by DCI with MCCH-RNTI scrambled CRC using a different QCL reference than that of the PDSCH.

[0124] Optionally, a UE that does not indicate feature FG48-2 can receive a PDSCH on time slot n, which is scheduled by DCI of CRC scrambled by MCCH-RNTI, and the number of PRBs is greater than 25 when the SCS is 15kHz or the number of PRBs is greater than 12 when the SCS is 15kHz. The UE schedules or configures a second PDSCH on the next time slot n+1, which is a PDSCH scheduled by DCI of CRC scrambled by MCCH-RNTI using a different QCL reference from that of the PDSCH.

[0125] Optionally, a UE that does not indicate feature FG48-2 does not need to process a PDSCH reception on time slot n, which is scheduled by DCI with CRC scrambled by the G-RNTI for broadcast, with a PRB number greater than 25 when the SCS is 15 kHz or a PRB number greater than 12 when the SCS is 15 kHz, if the PDSCH is configured with time slot repetition or the UE receives a second PDSCH on the next time slot n+1, unless the second PDSCH is a PDSCH scheduled by DCI with CRC scrambled by the same G-RNTI using a different QCL reference than the PDSCH.

[0126] Optionally, a UE that does not indicate feature FG48-2 may receive a PDSCH on time slot n, which is scheduled by a DCI with a CRC scrambled by the G-RNTI or MCCH-RNTI for broadcast, and the number of PRBs is greater than 25 when the SCS is 15 kHz or the number of PRBs is greater than 12 when the SCS is 15 kHz, and the UE schedules or configures a second PDSCH on the next time slot n+1, which is a PDSCH scheduled by a DCI with a CRC scrambled by the same G-RNTI using a different QCL reference than the PDSCH.

[0127] In addition, the UE may not receive relevant system information during periods other than system information update periods. Optionally, a UE that does not indicate feature FG48-2 need not process a PDSCH reception in slot n that is scheduled by a DCI with a CRC scrambled by a G-RNTI or MCCH-RNTI for broadcast, with a PRB number greater than 25 when the SCS is 15 kHz or a PRB number greater than 12 when the SCS is 15 kHz, if slot repetition is configured for the PDSCH or the UE receives a second PDSCH in the next slot n+1, unless the second PDSCH is a PDSCH scheduled by a DCI with a CRC scrambled by an SI-RNTI.

[0128] Optionally, a UE that does not indicate feature FG48-2 can receive a PDSCH on time slot n, which is scheduled by DCI with CRC scrambled by G-RNTI or MCCH-RNTI for broadcast, and when the SCS is 15kHz, the number of PRBs is greater than 25 or when the SCS is 15kHz, the number of PRBs is greater than 12. The UE schedules or configures a second PDSCH on the next time slot n+1, which is a PDSCH with DCI scrambled by SI-RNTI.

[0129] 4 is used to illustrate a user equipment as a modified example that can execute the method executed by the user equipment described in detail above in the present invention.

[0130] FIG4 is a block diagram showing a user equipment UE according to the present invention.

[0131] As shown in Figure 4, the user equipment UE20 includes a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 202 may include, for example, a volatile memory (such as a random access memory (RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory. The memory 202 stores program instructions. When executed by the processor 201, these instructions may execute the above-described method performed by the user equipment as described in detail in the present invention.

[0132] The method of the present invention and the related devices have been described above in conjunction with the preferred embodiments. Those skilled in the art will understand that the method shown above is only exemplary, and the various embodiments described above can be combined with each other when no contradiction occurs. The method of the present invention is not limited to the steps and sequence shown above. The network node and user equipment shown above may include more modules, for example, modules that can be developed or developed in the future and can be used for base stations, MMEs, or UEs, etc. The various identifiers shown above are only exemplary and not restrictive, and the present invention is not limited to the specific information elements used as examples of these identifiers. Those skilled in the art can make many changes and modifications based on the teachings of the illustrated embodiments.

[0133] It should be understood that the above embodiments of the present invention can be implemented through software, hardware, or a combination of software and hardware. For example, the various components within the base station and user equipment in the above embodiments can be implemented through a variety of devices, including but not limited to analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and the like.

[0134] In this application, "base station" refers to a mobile communication data and control switching center with high transmission power and wide coverage area, including functions such as resource allocation and scheduling, and data reception and transmission. "User equipment" refers to a user's mobile terminal, such as a mobile phone or laptop, that can communicate wirelessly with a base station or micro base station.

[0135] In addition, the embodiments of the present invention disclosed herein can be implemented on a computer program product. More specifically, the computer program product is a product as follows: having a computer-readable medium, on which computer program logic is encoded, and when executed on a computing device, the computer program logic provides relevant operations to implement the above-mentioned technical solutions of the present invention. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention. This arrangement of the present invention is typically provided as software, code and / or other data structures arranged or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), a floppy disk or a hard disk, or other media such as firmware or microcode on one or more ROM or RAM or PROM chips, or downloadable software images, shared databases, etc. in one or more modules. Software or firmware or this configuration can be installed on a computing device so that one or more processors in the computing device execute the technical solutions described in the embodiments of the present invention.

[0136] In addition, each functional module or each feature of the base station device and user equipment used in each of the above embodiments can be implemented or executed by a circuit, which is typically one or more integrated circuits. The circuits designed to perform the various functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC) or a general-purpose integrated circuit, a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, or a discrete hardware component, or any combination of the above devices. The general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller or state machine. The general-purpose processor or each circuit may be configured by a digital circuit, or may be configured by a logic circuit. In addition, when, due to advances in semiconductor technology, advanced technologies that can replace current integrated circuits emerge, the present invention may also use integrated circuits obtained using the advanced technology.

[0137] Although the present invention has been described above in conjunction with the preferred embodiments of the present invention, it will be understood by those skilled in the art that various modifications, substitutions, and changes may be made to the present invention without departing from the spirit and scope of the present invention. Therefore, the present invention should not be limited by the above-described embodiments, but should be limited by the appended claims and their equivalents.

Claims

1. A method performed by a user equipment UE, comprising: The UE determines processing of the first PDSCH according to the first PDSCH bandwidth parameter and MCCH change notification information in the DCI, and / or the distance between the first PDSCH and the second PDSCH; The first PDSCH is a PDSCH scheduled by the DCI; The second PDSCH is a PDSCH received by the UE after the first PDSCH; The processing of the PDSCH includes: when the first PDSCH bandwidth is greater than a predetermined value and the MCCH change notification information indicates that the MCCH is changed or when the distance between the first PDSCH and the second PDSCH is greater than a predetermined value, the UE receives the first PDSCH.

2. The method according to claim 1, characterized in that The MCCH change notification information indicates that the MCCH is changed to the LSB low bit of the MCCH change notification field in the DCI format 4_0 is 1.

3. The method according to claim 1, characterized in that The distance between the first PDSCH and the second PDSCH is the number of time slots between the time slot where the first PDSCH is located and the time slot where the second PDSCH is located.

4. The method according to claim 1, characterized in that: The distance between the first PDSCH and the second PDSCH is the number of symbols between the last symbol of the first PDSCH and the first symbol of the second PDSCH.

5. A user equipment, comprising: processor; as well as Memory, which stores instructions, Wherein, when the instructions are executed by the processor, the method according to any one of claims 1 to 4 is performed.

Images