Method executed by user equipment and user equipment

Abstract

The invention provides a method executed by user equipment UE and the user equipment. The method executed by the user equipment comprises the steps that the UE determines processing of a first PDSCH according to a first PDSCH bandwidth parameter and MCCH change notification information in DCI and / or the distance between the first PDSCH and a second PDSCH; wherein the first PDSCH is a PDSCH which is scheduled by the DCI (Downlink Control Information); the second PDSCH is the first PDSCH received by the UE after the first PDSCH, and the first PDSCH is the first PDSCH received by the UE after the first PDSCH; the processing of the PDSCH comprises: when the bandwidth of a first PDSCH is greater than a predetermined value and the MCCH change notification information indicates that the MCCH is changed or the distance between the first PDSCH and a second PDSCH is greater than a predetermined value, the UE receives the first PDSCH. Therefore, the user equipment can determine the processing of the PDSCH according to the actual PDSCH transmission condition, so that the eRedCap UE can update the MBS configuration information in time, the user service is ensured, and the UE and network efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technology, 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 from this perspective and should not be understood as an admission of what is or is not prior art.

[0003] Several typical applications are defined in the 5G system. For example, industrial wireless sensor applications are committed to accelerating industrial transformation and digitalization to obtain flexibility in industrial production processes, improve productivity and efficiency, and help reduce maintenance and improve operational safety. Video surveillance equipment is used in smart city construction to help achieve better urban management and services. Wearable devices can be used for intelligent services in many aspects such as medical care and life. The devices for these applications are expected to have lower complexity and less power consumption to reduce costs and expand the scope of application. In R17, the bandwidth of some device types was reduced from 100MHz to 20MHz, thereby reducing device costs. To further reduce the complexity of terminal devices, some new methods can be adopted, such as reducing the peak data rate supported by these devices to about 10Mbps, or further reducing the user equipment bandwidth from a maximum of 20MHz to a maximum of 5MHz. These methods or their combination can further reduce the complexity of devices and reduce costs at different 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 the integrity of the ecosystem, maximize the scale of the ecosystem, and improve network benefits. These new business needs put forward some new requirements for existing NR networks. For example, if the network supports a data transmission bandwidth of no more than 5MHz for user equipment, the network configuration parameters or the resource parameters used by the terminal to transmit data must meet relevant requirements, and the impact of common channel configuration and scheduling in the cell on system deployment must be considered. The relevant method of the present invention provides a better method for realizing these device requirements in the network, and can ensure coexistence with existing equipment in the network when relevant constraints are met, thereby obtaining better network utilization efficiency. Summary of the invention

[0004] In order to solve at least part of the above problems, the present invention provides a method executed by a user equipment and a user equipment, which enables the user equipment to determine the processing of PDSCH according to the actual PDSCH transmission situation, so that the eRedCapUE can update the MBS configuration information in time to ensure user services. And it enables the network to flexibly schedule resources for network users to receive MBS services, thereby improving network efficiency.

[0005] According to the present invention, a method performed by a user equipment UE is provided, comprising: the UE determines the processing of a first PDSCH according to a first PDSCH bandwidth parameter and MCCH change notification information in an indication of a DCI, and / or the distance between the first PDSCH and a second PDSCH; wherein the first PDSCH is a PDSCH scheduled by the DCI; 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 that the MCCH is changed or the distance between the first PDSCH and the second PDSCH is greater than a predetermined value, the UE receives the first PDSCH. The predetermined value of the bandwidth can be determined according to the SCS used by the PDSCH.

[0006] In the above method, the MCCH change notification information may indicate 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.

[0007] 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.

[0008] 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.

[0009] 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.

[0010] Effects of the Invention

[0011] 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 the network can flexibly schedule resources for network users to receive MBS services, thereby improving network efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] 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:

[0013] Figure 1 It represents a method executed by a user equipment UE related to an embodiment of the present invention.

[0014] Figure 2Another method performed by a user equipment UE related to the embodiment of the present invention is shown.

[0015] Figure 3 It is a schematic diagram showing the use of multi-beam scheduling and PDSCH transmission in a cell related to an embodiment of the present invention.

[0016] Figure 4 FIG. 4 is a block diagram showing a simplified structure of a user equipment UE according to the present invention. DETAILED DESCRIPTION

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

[0018] 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 common meanings in the relevant technical field. Unless clearly stated, all references to one element, device, assembly, part, step, etc. should be publicly interpreted as referring to at least one instance of the element, device, assembly, part, step, etc. Unless a step must be clearly described as after or before another step and / or a step must be after or before another step implicitly, 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. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa.

[0019] The following uses the 5G / NR mobile communication system and its subsequent evolution versions as example application environments to specifically describe multiple embodiments of the present invention. However, it should be noted that the present invention is not limited to the following embodiments, but is applicable to more other wireless communication systems, such as communication systems after 5G and 4G and 3G mobile communication systems before 5G, 802.11 wireless networks, etc.

[0020] The following describes some of the terms involved in the present invention. Unless otherwise specified, the terms involved in the present invention are defined herein. The terms given in the present invention may be named differently in LTE, LTE-Advanced, LTE-Advanced Pro, NR and subsequent or other communication systems, but unified terms are used in the present invention, and when applied to a specific system, they can be replaced by the terms used in the corresponding system.

[0021] 3GPP: 3rd Generation Partnership Project

[0022] LTE: Long Term Evolution

[0023] NR: New Radio

[0024] UE:User Equipment

[0025] gNB: NR base station

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

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

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

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

[0030] OFDM: Orthogonal Frequency Division Multiplexing

[0031] CP: Cyclic Prefix

[0032] TA: Timing Advance, uplink timing advance

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

[0034] TDD: Time Division Duplexing

[0035] FDD: Frequency Division Duplexing

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

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

[0038] HARQ: Hybrid Automatic Repeat Request

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

[0040] MIB: Master Information Block

[0041] SIB: system information block

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

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

[0044] PSS: Primary Synchronization Signal

[0045] SSS: Secondary Synchronization Signal, auxiliary synchronization signal

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

[0047] DMRS: Demodulation Reference Signal

[0048] CSI-RS: Channel State Information Reference Signal, channel state information reference signal

[0049] TRS: Tracking Reference Signal, tracking reference signal

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

[0051] PBCH: Physical broadcast channel

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

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

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

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

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

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

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

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

[0060] MBS: Multicast / Broadcast Service

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

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

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

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

[0065] G-CS-RNTI: Group Configured Scheduling RNTI, group RNTI for configuration scheduling

[0066] MRB: MBS Radio Bearer

[0067] QCL: Quasi co-location

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

[0069] It is worth pointing out that the user, user equipment and terminal equipment involved in the specification of the present invention have the same meaning. UE can also be used to represent user equipment in the text, and no specific distinction or limitation will be made in the following text. Similarly, network equipment is equipment that communicates with user equipment, including but not limited to base station equipment, gNB, eNB, wireless AP, wireless relay, terminal with relay capability, etc., and no specific distinction or limitation will be made in the following text. In the text, a base station can be used as a form of network equipment implementation for illustration, and other forms of network equipment can be easily used for replacement in specific implementation.

[0070] The network can provide users with MBS (Multicast and Broadcast Services) services. When the broadcast service is used in the MBS service, the same service is used for all UEs in the cell, that is, all UEs in the cell (certified by the higher layer to support the MBS service) can receive the relevant control information channel MCCH and the 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 in a periodic transmission mode 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 broadcast MTCH.

[0071] MCCH uses the PDSCH transmission scheduled by the DCI with MCCH-RNTI scrambled CRC, and the corresponding PDSCH can be recorded as MCCH-PDSCH. MTCH uses the PDSCH transmission scheduled by the DCI with G-RNTI scrambled CRC, 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 in a time slot repetition manner, that is, MTCH is repeatedly transmitted on multiple consecutive time slots, and the UE can perform relevant 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, etc. The UE can determine the time-frequency position of the resources used by the relevant PDSCH based on the DCI.

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

[0073] 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, using the DCI that scrambles the CRC with MCCH-RNTI.

[0074] 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 MCCH changes other than the start of a new MBS service, such as configuration changes of an ongoing MBS session, MBS session stop, or neighbor information changes, 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 MCCH change notifications.

[0075] When the UE starts to receive the MBS broadcast service, the UE shall apply the MCCH acquisition procedure to acquire the MCCH. For example, the UE applies the MCCH acquisition procedure to acquire the MCCH after receiving SIB20. In addition, once the UE receiving the broadcast MRB data receives the MCCH information change information, and the change is due to the MCCH information adjustment rather than just starting a new MBS service (that is, the LSB bit in the DCI is set to 1), the MCCH information acquisition procedure shall be applied.

[0076] 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 many types 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 MCCH.

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

[0078] If the process is triggered by the MCCH information change notification, the UE obtains the MBSBroadcastConfiguration message on the MCCH starting from the time slot when the change notification is received in the connected cell. That is, the UE receives the DCI-scheduled PDSCH containing the MCCH information change notification and obtains the MBSBroadcastConfiguration transmitted thereon.

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

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

[0081] eRedCap is a terminal type that reduces terminal complexity by limiting bandwidth or peak rate, for example, it can be identified by the supportOfRedCap-r18 parameter. eRedCap UE can be divided into several subtypes according to the different feature parameter groups used. For example, an eRedCap UE using the FG48-1 feature group limits the number of PRBs used by some shared data channels in the FR1 band to no more than the number of PRBs corresponding to the 5MHz bandwidth, that is, 25 and 12 respectively when the SCS is 15kHz and 30kHz; the number of PRBs used by other channels is no more than the number of PRBs corresponding to the 20MHz bandwidth. An eRedCap UE using the FG48-2 feature group can use PRBs corresponding to a maximum bandwidth of 20M, and its peak rate of data transmission is limited to about 10Mbps. The feature group parameters used by the UE can be reported to the gNB through the UE capability reporting process.

[0082] eRedCap UE can also support MBS services. In order to reduce the implementation complexity requirements of eRedCap UE, the bandwidth of the relevant channels used for MBS services can be limited; at the same time, in order to avoid affecting other UEs in the cell, ensure the flexibility of the base station in resource configuration, and the reliability of UE receiving MBS services, the present invention proposes a method for eRedCap UE to determine the relevant reception according to the received information when receiving MBS services, so that the UE determines the processing of PDSCH according to the actual PDSCH transmission situation, so that the eRedCap UE can update the MBS configuration information in time, guarantee the user's service, and improve the UE and network performance.

[0083] Figure 1 It represents a method executed by a user equipment UE related to an embodiment of the present invention.

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

[0085] 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.

[0086] Figure 2 Another method performed by a user equipment UE related to an embodiment of the present invention is shown. Figure 2As shown, in step S201, the UE receives a DCI of MCCH-RNTI or a G-RNTI for broadcast scrambled CRC, and the DCI schedules the first PDSCH. The DCI includes bandwidth information of the scheduled PDSCH.

[0087] 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.

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

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

[0090] [Example 1]

[0091] 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, the valid time has not exceeded, 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 UE, in order to reduce the burden of UE processing data, when the bandwidth of 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 need additional processing time or cache to process. At this time, if there are other PDSCHs that need 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.

[0092] 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,

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

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

[0095] - 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.

[0096] Here, the eRedCap UE that does not indicate feature group FG48-2 includes several cases. In the first case, for the eRedCap UE in RRC_IDLE or RRC_INACTIVE state, whether it is for the UE using feature group FG48-1 or FG48-2, the UE has not reported its specific feature group type to the gNB. At this time, the UE that does not indicate feature group FG48-2 includes the UE using feature group FG48-1 or FG48-2. In another case, for the eRedCap UE in the RRC_CONNECTED state, the relevant UE features have been reported to the gNB through the UE capability reporting process. At this time, the UE that does not indicate feature FG48-2 does not include the eRedCap UE using the FG48-2 feature.

[0097] 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.

[0098] 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 the predetermined distance, the UE should receive the PDSCH scheduled by the DCI and may not process the other PDSCH.

[0099] In addition, when the number of PRBs of the DCI scheduled PDSCH is not greater than 25 or 12, the bandwidth is not greater than the maximum bandwidth value of the eRedCapUE demodulation dedicated PDSCH, and the UE can receive the PDSCH without additional restrictions. The above reception includes relevant reception, decoding, and sending to the upper layer when the verification is correct. If not processed, the PDSCH can be discarded, and feedback or no feedback is given according to the relevant HARQ settings.

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

[0101] 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 eRedCapUE 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, the number of PRBs is greater than 25 or when the SCS is 15kHz, 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.

[0102] Optionally, the eRedCap UE can process PDSCH in time slot n, which is scheduled by DCI with MCCH-RNTI scrambled CRC and the number of PRBs of 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.

[0103] 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 a timeslot n 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 15kHz or the number of PRBs greater than 12 when the SCS is 15kHz, if the PDSCH is configured with timeslot repetition or the UE receives another PDSCH on the next timeslot n+1, unless the MCCH change notification information in the DCI indicates an MCCH change.

[0104] Optionally, the UE determines the distance between another PDSCH received by the UE and the PDSCH scheduled by the DCI according to the interval from the last symbol of the PDSCH to 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 conventional 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 MCCH-RNTI scrambled CRC, when the SCS is 15 kHz, the number of PRBs is greater than 25 or when the SCS is 15 kHz, the number of PRBs is greater than 12, 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 the predetermined number of symbols.

[0105] Optionally, an eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception on timeslot n, which is scheduled by DCI with MCCH-RNTI scrambled CRC, with the number of PRBs greater than 25 when the SCS is 15kHz or the number of PRBs greater than 12 when the SCS is 15kHz, 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.

[0106] Optionally, an eRedCap UE that does not indicate feature group FG48-2 does not need to process the reception of a PDSCH 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 timeslot repetition is configured for this PDSCH or the UE receives another PDSCH and the interval from the last symbol of this PDSCH to the first symbol of the other PDSCH is less than a predetermined number of symbols.

[0107] Optionally, an eRedCap UE that does not indicate feature group FG48-2 does not need to process the reception of a PDSCH 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.

[0108] 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.

[0109] [Example 2]

[0110] 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, the valid time has not exceeded, 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 UE, in order to reduce the burden of UE processing data, when the bandwidth of 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 need additional processing time or cache to process. At this time, if there are other PDSCHs to be processed after the next time slot or several symbols of 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.

[0111] According to an exemplary embodiment, 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 an MCCH change. The eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception, 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 at a distance less than a predetermined distance from the PDSCH.

[0112] 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.

[0113] 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 the predetermined distance, the UE should receive the MCCH-PDSCH and may not process the other PDSCH.

[0114] In addition, when the number of PRBs of the DCI-scheduled PDSCH is not greater than 25 or 12, the UE can also receive the PDSCH. The reception here includes relevant reception, decoding, and sending to the upper layer when the verification is correct. If not processed, the PDSCH can be discarded, and feedback or no feedback is given according to the relevant HARQ settings.

[0115] Optionally, the MCCH change is a change other than the change of starting a new MBS service. Specifically, the DCI corresponding to the scheduling of the MCCH-PDSCH indicates the MCCH information change, and the low-order bit (LSB) of the change notification field is 1. No indication of MCCH change means that the DCI does not indicate the MCCH information change, and the low-order bit (LSB) of the change notification field of the DCI is 0.

[0116] 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 the UE receives another PDSCH in time slot n+1.

[0117] 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 conventional CP. Specifically, the eRedCap UE should process a PDSCH reception, which is scheduled by a DCI with an MCCH-RNTI scrambled CRC, and the MCCH change notification information in the DCI indicates the MCCH change. The eRedCap UE that does not indicate feature group FG48-2 does not need to process a PDSCH reception, which is scheduled by a DCI with an 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. 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.

[0118] 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.

[0119] [Example 3]

[0120] NR supports the use of beam or spatial parameters for data transmission to obtain better coverage. For example, in the FR1 frequency band, up to 4 or 8 beams can be used to transmit SSB, depending on the different carrier frequencies. 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, such as using the relevant SSB beam as the QCL reference to set spatial parameters, using multiple beams to transmit PDCCH and PDSCH, where PDCCH transmits DCI with SI-RNTI scrambled CRC and 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 Figure 3 As shown, 4 beams with different QCL references are used for PDCCH and PDSCH transmission in 4 consecutive time slots, and the UE can select one or more for reception (based on measurements).

[0121] The network can also use this method to transmit MBS broadcast channels. Depending on the parameters configured by the network, 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 certain beam.

[0122] 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 MCCH-RNTI, 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 CRC scrambled by MCCH-RNTI using a different QCL reference from that of the PDSCH.

[0123] Optionally, a UE that does not indicate characteristic 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.

[0124] 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 as the PDSCH.

[0125] Optionally, a UE that does not indicate characteristic 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 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 with CRC scrambled by the same G-RNTI using a different QCL reference from the PDSCH.

[0126] In addition, the UE may not receive relevant system information during non-system information update periods. Optionally, a UE that does not indicate feature FG48-2 does not need to process a PDSCH reception in time slot n, which is scheduled by DCI with CRC scrambled by G-RNTI or MCCH-RNTI for broadcast, 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, if the PDSCH is configured with time slot repetition or the UE receives a second PDSCH in the next time slot n+1, unless the second PDSCH is a PDSCH scheduled by DCI with CRC scrambled by SI-RNTI.

[0127] 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 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 with DCI scrambled by SI-RNTI CRC.

[0128] Next, use Figure 4 A user equipment as a variation example that can execute the method executed by the user equipment described in detail above of the present invention is described.

[0129] Figure 4 It is a block diagram showing a user equipment UE involved in the present invention.

[0130] like Figure 4 As shown, 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 memories, etc. The memory 202 stores program instructions. When the instructions are executed by the processor 201, the above method performed by the user equipment described in detail in the present invention may be executed.

[0131] The method of the present invention and the related equipment have been described above in conjunction with the preferred embodiments. Those skilled in the art will appreciate that the method shown above is only exemplary, and the embodiments described above can be combined with each other without contradiction. 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 that serve as examples of these identifiers. Those skilled in the art may make many changes and modifications based on the teachings of the illustrated embodiments.

[0132] It should be understood that the above embodiments of the present invention can be implemented by software, hardware, or a combination of software and hardware. For example, the various components inside the base station and user equipment in the above embodiments can be implemented by 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.

[0133] In this application, "base station" may refer to a mobile communication data and control exchange center with a large transmission power and a wide coverage area, including functions such as resource allocation scheduling, data reception and transmission, etc. "User equipment" may refer to a user mobile terminal, such as a mobile phone, a notebook, etc., which can communicate wirelessly with a base station or a micro base station.

[0134] 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 a 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 solution 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 operation (method) described in the embodiment 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 in one or more modules, shared databases, etc. The software or firmware or such a configuration can be installed on a computing device so that one or more processors in the computing device execute the technical solution described in the embodiment of the present invention.

[0135] In addition, each functional module or each feature of the base station device and the user equipment used in each of the above embodiments can be implemented or executed by a circuit, which is usually 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 above-mentioned 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 the advancement of semiconductor technology, an advanced technology that can replace the current integrated circuit appears, the present invention may also use an integrated circuit obtained using the advanced technology.

[0136] Although the present invention has been illustrated above in conjunction with the preferred embodiments of the present invention, it will be appreciated 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 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-order bit of the MCCH change notification field in the DCI format 40 being 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