CN114650604A

CN114650604A - PDSCH transmission method and device and electronic equipment

Info

Publication number: CN114650604A
Application number: CN202011503589.9A
Authority: CN
Inventors: 李娜
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-12-17
Filing date: 2020-12-17
Publication date: 2022-06-21
Also published as: WO2022127701A1

Abstract

The application discloses a PDSCH transmission method, a PDSCH transmission device and electronic equipment, and belongs to the technical field of communication. The PDSCH transmission method comprises the following steps: executed by a terminal, comprising: if the plurality of PDSCHs scheduled by the network side equipment conflict, determining the received or decoded PDSCH according to at least one item of information: a scheduling mode of the PDSCH; PDSCH is a group common PDSCH or unicast PDSCH; scheduling Downlink Control Information (DCI) of the PDSCH; priority information of the PDSCH; a starting symbol of the PDSCH; frequency domain location of PDSCH. The technical scheme of the embodiment of the application can improve the effectiveness of the communication system.

Description

PDSCH transmission method and device and electronic equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a PDSCH transmission method, apparatus, and electronic device.

Background

User Equipment (UE), also referred to as a terminal, may be interested in multiple services simultaneously, and the services of interest may be different for different UEs. When a UE receives multiple broadcast/multicast services, unicast services, and/or multicast services simultaneously, since a PDSCH (Physical Downlink Shared Channel) is sent to multiple UEs, there may be a case where multiple PDSCHs overlap or exceed the UE reception capability from a UE perspective.

Disclosure of Invention

The embodiment of the application provides a PDSCH transmission method, a PDSCH transmission device and electronic equipment, which can improve the effectiveness of a communication system.

In a first aspect, an embodiment of the present application provides a PDSCH transmission method, which is executed by a terminal, and includes:

if the PDSCHs scheduled by the network side equipment conflict, determining the received or decoded PDSCH according to at least one item of information:

a scheduling mode of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

In a second aspect, an embodiment of the present application provides a method for transmitting a PDSCH, where the method is performed by a network side device, and the method includes:

transmitting a plurality of PDSCHs to a terminal in one time slot, wherein the time domain and/or the frequency domain of the PDSCHs are overlapped, or the PDSCHs exceed the receiving capability of the terminal, wherein the receiving capability is the capability of the terminal to receive a plurality of unicast and/or group public PDSCHs in one time slot;

the PDSCHs are scheduled by Downlink Control Information (DCI); or

At least part of the plurality of PDSCHs are group common DCI scheduled PDSCHs or semi-persistently scheduled PDSCHs.

In a third aspect, an embodiment of the present application provides a PDSCH transmitting apparatus, including:

a processing module, configured to determine, if multiple PDSCHs scheduled by the network side device collide, a received or decoded PDSCH according to at least one of the following information:

a scheduling manner of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

In a fourth aspect, an embodiment of the present application provides a PDSCH transmitting apparatus, including:

a sending module, configured to send multiple PDSCHs to a terminal in one time slot, where time domains and/or frequency domains of the multiple PDSCHs are overlapped, or the multiple PDSCHs exceed a receiving capability of the terminal, where the receiving capability is a capability of the terminal to receive multiple unicast and/or group common PDSCHs in one time slot;

the PDSCHs are scheduled by Downlink Control Information (DCI); or

In a fifth aspect, embodiments of the present application further provide an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method described above.

In a sixth aspect, the present application provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method as described above.

In a seventh aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect or the second aspect.

In the embodiment of the present application, if multiple PDSCHs scheduled by the network side device collide with each other, the terminal may receive or decode the PDSCHs according to one or more pieces of set information.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

FIG. 1 shows a schematic diagram of a wireless communication system;

fig. 2 is a flowchart illustrating a PDSCH transmission method performed by a terminal according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a PDSCH transmission method performed by a network device according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating the overlapping of time domain and/or frequency domain resources of PDSCH1 and PDSCH2 according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a UE1 and a UE2 configuring one or more SPS PDSCHs in an embodiment of the disclosure;

fig. 6 and 7 are diagrams illustrating a UE configuring or scheduling four PDSCHs in one time slot according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a PDSCH transmitting device on a terminal side according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a PDSCH transmitting device on a network side device side according to an embodiment of the present application;

fig. 10 is a schematic diagram showing the composition of a terminal according to an embodiment of the present application;

fig. 11 shows a schematic composition diagram of a network-side device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below clearly with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

The techniques described herein are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-advanced (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. The following description describes the NR system for purposes of example, and NR terminology is used in much of the description below, but the techniques may also be applied to applications other than NR system applications.

The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Referring to fig. 1, fig. 1 is a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may also be referred to as a terminal Device or a User Equipment (UE), where the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or a vehicle-mounted Device, and the specific type of the terminal 11 is not limited in this embodiment. The network-side device 12 may be a Base Station or a core network, wherein the Base Station may be a 5G or later-version Base Station (e.g., a gNB, a 5G NR NB, etc.), or a Base Station in other communication systems (e.g., an eNB, a WLAN access point, or other access points, etc.), or a location server (e.g., an E-SMLC or an lmf (location Manager function)), wherein the Base Station may be referred to as a node B, an evolved node B, an access point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, or some other suitable terminology in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the base station in the NR system is taken as an example, but the embodiment of the present application does not limit the specific type of the base station and the specific communication system.

In the Broadcast Multicast transmission of LTE (Long Term Evolution), MBSFN mode MBMS (Multimedia Broadcast Multicast Service) Service transmission and SC-PTM (Single-Cell Point-To-Multipoint) mode Multicast Service transmission are supported. In the MBSFN scheme, the MBMS transmission is performed through a PMCH (Physical Multicast Channel) Physical Channel in an MBSFN (Multimedia Broadcast Multicast service Single Frequency Network) subframe. The Control information is transmitted through system information (e.g., SIB (system information block) 13) and MCCH (broadcast Control Channel), and the data is transmitted through MTCH (broadcast Traffic Channel). The control information (control channel parameter and service channel parameter, scheduling information, etc.) and data information of the MBMS service are transmitted in a broadcast manner, so that idle (idle) state UEs and connected state UEs can both receive the MBMS service, and the data information of the MBMS is transmitted only in MBSFN subframes. SC-PTM is a multicast transmission mode standardized after MBMS service, and is the biggest difference with the MBSFN mode that the SC-PTM is transmitted only in single cell scheduling and the service scheduling is carried out by G-RNTI (group RNTI, group radio network temporary identifier). A Physical Downlink Shared Channel (PDSCH) scheduled by a PDCCH (Physical Downlink Control Channel). The Control information is transmitted through system information (e.g., SIB20) and an SC-MCCH (Single Cell Multicast Control Channel, Single Cell broadcast Traffic Channel), and the data is transmitted through an SC-MTCH (Single Cell Multicast Traffic Channel). The SC-MCCH is transmitted through a PDSCH scheduled by a PDCCH (Single Cell RNTI, Radio Network Temporary Identity) and the SC-MTCH is transmitted through a PDSCH scheduled by G-RNTI PDCCH. Namely, the control channel parameters, the service identification, the period information and the like are broadcasted in the broadcast message, the scheduling information is notified by the PDCCH scrambled by the G-RNTI, the data part is sent in a multicast mode, and the method is equivalent to that interested UE monitors the G-RNTI to obtain data scheduling and then receives the data scheduling.

In the LTE, one UE can simultaneously receive a plurality of broadcast multicast services, in an MBSFN mode, different services have different MBSFN configurations, the UE can distinguish different services through the MBSFN, in the SC-PTM, different services use different G-RNTIs, and the UE can distinguish different services through the G-RNTI.

At present, NR (New Radio, New air interface) technology does not support broadcast/multicast (broadcast/multicast) features, but there are many important usage scenarios, such as public safety and critical tasks (public safety and mission critical), V2X applications (V2X applications), transparent IPv4/IPv6 multicast transmission (transparent IPv4/IPv6 multicast transmission), IPTV, wireless software transmission (software over wireless), group communication and internet of things applications (outer communications and IoT applications), etc., which can provide substantial improvements, especially in terms of system efficiency and user experience.

One UE in the NR may receive more than one, e.g., 2/4/7, unicast PDSCHs transmitted in different symbols (i.e., TDM) based on the UE's capability in one slot. After introducing the multicast broadcast characteristic, the NR supports TDM transmission of the unicast PDSCH and the group common PDSCH in one time slot, that is, different symbol transmission in one time slot, and also supports transmission of the unicast PDSCH and the group common PDSCH in different Frequency domain resources, that is, FDM (Frequency Division Multiplexing) transmission.

For broadcast multicast service transmission, since the group common PDSCH is sent to multiple UEs, for a certain UE, the situation that the time-frequency domain resources of multiple group common PDSCHs overlap or multiple PDSCHs exceed the UE receiving capability may occur, and in this situation, the problem how the UE receives the PDSCH needs to be solved.

An embodiment of the present application provides a PDSCH transmission method, which is executed by a terminal, as shown in fig. 2, and includes:

step 101: if the plurality of PDSCHs scheduled by the network side equipment conflict, determining the received or decoded PDSCH according to at least one item of information:

a scheduling mode of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH, for example, receiving or decoding the PDSCH according to the order of the DCI;

priority information of the PDSCH;

starting symbols of the PDSCH, wherein the starting symbols represent the time sequence of the PDSCH;

the frequency domain location of the PDSCH, such as low frequency, takes precedence over high frequency.

If the UE does not support TDM (time division multiplexing) or FDM (frequency division multiplexing) transmission of multiple PDSCHs in one timeslot, scheduling multiple PDSCHs in one timeslot is a collision, or time domain resources of multiple PDSCHs overlap and also a collision.

In addition, if the UE supports receiving M TDM PDSCHs at most in one timeslot, the base station schedules N PDSCHs, where N > M, the UE needs to select M PDSCHs to receive or decode among the N PDSCHs (where time domain symbols of the M PDSCHs do not overlap), or multiple PDSCH time domain resources overlap to cause a collision, where M and N are positive integers.

If the UE supports receiving M FDM PDSCHs at most in one timeslot, the base station schedules N PDSCHs, where N > M, the UE needs to select M PDSCHs from the N PDSCHs to receive or decode (where frequency domain positions of the M PDSCHs are not overlapped), and M and N are positive integers.

Where M or N depends on the capability of the UE, may be indicated by the UE and/or configured by the base station.

The received (received) or decoded (decode) PDSCH may be a decoded PDSCH, or may be a received PDSCH.

The group common PDSCH means PDSCH transmitted by the base station to a group of terminals or multiple terminals through the same resource, and may also be called multicast PDSCH or multicast PDSCH, and is mainly used for MBS or MBMS service transmission.

In some embodiments, the priority information comprises any one of:

receiving and/or decoding priority, which may be configured or indicated by the network side device; the receiving and/or decoding priority of the PDSCH may be directly configured or indicated, or may be indirectly configured or indicated, for example, by a value of a Radio Network Temporary Identity (RNTI) corresponding to the PDSCH, and/or a Control-resource set (CORESET), and/or a search space set (search space set).

A physical layer priority, which may be configured or indicated by the network side device;

the service priority and/or the logical channel priority may be configured or indicated by the network side device or reported by the terminal;

in some embodiments, the colliding plurality of PDSCHs are dynamically scheduled PDSCHs, and the determining the received or decoded PDSCH based on at least one of the following information comprises:

if the plurality of PDSCHs include a group common PDSCH and a unicast PDSCH, determining a received or decoded PDSCH by adopting any one of the following modes:

receiving or decoding a unicast PDSCH;

receiving or decoding the unicast PDSCH if the DCI for scheduling the unicast PDSCH is not earlier than the DCI for scheduling the group common PDSCH;

if the DCI for scheduling the unicast PDSCH is earlier than the DCI for scheduling the group common PDSCH, determining the received or decoded PDSCH according to any one of the following information: priority information of the PDSCH, a starting symbol of the PDSCH, and a frequency domain position of the PDSCH.

Wherein receiving or decoding the unicast PDSCH means preferentially receiving or decoding the unicast PDSCH, and may be receiving or decoding only the unicast PDSCH without receiving or decoding the group common PDSCH.

if the plurality of PDSCHs only include a group common PDSCH, determining a received or decoded PDSCH according to any one of the following information:

priority information of the PDSCH;

a starting symbol of the PDSCH and/or a starting symbol and/or an ending symbol of the DCI scheduling the PDSCH;

frequency domain location of PDSCH, such as low frequency over high frequency;

whether the DCI scheduling the PDSCH is a terminal-specific DCI.

In some embodiments, the determining the PDSCH reception or decoding manner based on whether the PDSCH is a group common PDSCH or a unicast PDSCH includes:

if the dynamically scheduled PDSCH is a unicast PDSCH, receiving or decoding the dynamically scheduled PDSCH; and if the dynamically scheduled PDSCH is the group common PDSCH, receiving or decoding the dynamically scheduled PDSCH, or determining a PDSCH receiving or decoding mode according to whether the dynamically scheduled PDSCH is the PDSCH scheduled by the terminal specific DCI.

Wherein receiving or decoding the unicast PDSCH means preferentially receiving or decoding the dynamically scheduled PDSCH, and may be receiving or decoding only the dynamically scheduled PDSCH without receiving or decoding the semi-persistently scheduled PDSCH.

In some embodiments, the determining, according to whether the dynamically scheduled PDSCH is the terminal-specific DCI scheduled PDSCH, a PDSCH receiving or decoding manner includes:

if the dynamically scheduled PDSCH is the PDSCH scheduled by the terminal specific DCI, receiving or decoding the dynamically scheduled PDSCH, and if the dynamically scheduled PDSCH is not the PDSCH scheduled by the terminal specific DCI, determining the received or decoded PDSCH according to any one of the following information: priority information of PDSCH, starting symbol of PDSCH and/or starting symbol and/or ending symbol of DCI scheduling PDSCH, frequency domain position of PDSCH, such as low frequency in preference to high frequency.

In some embodiments, the determining the PDSCH receiving or decoding manner according to whether the PDSCH is a group common PDSCH or a unicast PDSCH includes:

if the PDSCHs only comprise unicast PDSCHs, receiving or decoding the PDSCHs according to the size of a semi-persistent scheduling configuration index;

if the plurality of PDSCHs include a group common PDSCH, determining a received or decoded PDSCH according to any one of the following information: priority information of PDSCH, starting symbol of PDSCH and/or time order of DCI scheduling PDSCH, frequency domain location of PDSCH, such as low frequency is prioritized over high frequency.

An embodiment of the present application further provides a PDSCH transmission method, which is executed by a network side device, as shown in fig. 3, and includes:

step 201: the method comprises the steps of sending a plurality of PDSCHs to a terminal in one time slot, wherein the time domains and/or the frequency domains of the PDSCHs are overlapped, or the PDSCHs exceed the receiving capability of the terminal, wherein the receiving capability is the capability of the terminal for receiving a plurality of unicast and/or group public PDSCHs in one time slot.

If the UE does not support TDM (time division multiplexing) or FDM (frequency division multiplexing) transmission of multiple PDSCHs in one timeslot, scheduling multiple PDSCHs in one timeslot is a collision, or time domain resources of multiple PDSCHs are overlapped and also a collision, that is, the UE can only receive one unicast PDSCH or a group of common PDSCHs in one timeslot

In addition, if the UE supports receiving M TDM PDSCHs at most in one timeslot, the base station schedules N PDSCHs, where N > M, the UE needs to select M PDSCHs from the N PDSCHs to receive or decode, or multiple PDSCH time domain resources overlap to cause a collision.

If the UE supports receiving M FDM PDSCHs at most in one time slot, the base station schedules N PDSCHs, where N > M, the UE needs to select M PDSCHs from the N PDSCHs to receive or decode.

In some embodiments, the plurality of PDSCHs are PDSCHs scheduled by downlink control information, DCI.

In some embodiments, at least a portion of the plurality of PDSCHs are group common DCI scheduled PDSCHs or semi-persistently scheduled PDSCHs.

In some embodiments, the plurality of PDSCHs comprises any one of:

unicast PDSCH and group common PDSCH scheduled by group common DCI;

at least two group common PDSCHs scheduled by the group common DCI;

a semi-persistently scheduled group common PDSCH;

unicast PDSCH and semi-persistently scheduled group common PDSCH.

That is, for the dynamically scheduled PDSCH, the network side device is allowed to schedule a plurality of collisions between the group common PDSCH or a collision between the group common PDSCH and the unicast PDSCH; for the group common PDSCH and the unicast PDSCH, if the group common PDSCH is UE-specific DCI scheduled, not allowing a collision between the group common PDSCH and the unicast PDSCH, i.e., only allowing a collision between the group common PDSCH and the unicast PDSCH that is scheduled by the group common DCI; for the group common PDSCH and the group common PDSCH, if both are UE-specific DCI scheduled, no collision between the group common PDSCH and the group common PDSCH is allowed, i.e., only collision between the group common PDSCH scheduled by the group common DCI and another group common PDSCH is allowed. Herein, the group common PDSCH may also be referred to as a multicast PDSCH.

For SPS PDSCH, the network side device is allowed to schedule collisions between multiple group common PDSCH or collisions between group common PDSCH and unicast PDSCH.

In a specific example, as shown in fig. 4, DCI1 and DCI 2 schedule unicast PDSCH1 and group common PDSCH2, respectively, where DCI 2 is group common DCI. DCI1 precedes DCI 2. In fig. 4(a), the time-frequency domain resources of PDSCH1 and PDSCH2 overlap, and the UE cannot receive both PDSCHs at the same time. In fig. 4(b), the time-frequency domain resources of PDSCH1 and PDSCH2 do not overlap, but PDSCH1 and PDSCH2 are within one slot, and the UE does not support the group common PDSCH and unicast PDSCH on different symbols (i.e., TDM) received within one slot. In fig. 4(c), the time domain resources of PDSCH1 and PDSCH2 overlap and the frequency domain resources do not overlap, but the UE does not support reception of a group common PDSCH and unicast PDSCH of different frequency domains (i.e., FDM) within one slot. In none of the three cases, the UE can receive PDSCH1 and PDSCH2 simultaneously. Therefore, a certain rule needs to be defined to determine which PDSCH of PDSCH1 and PDSCH2 is received by the UE.

For dynamically scheduled PDSCH, if the UE is scheduled with multicast PDSCH and unicast PDSCH on overlapping resource transmissions, or the UE is not able to receive both PDSCHs simultaneously due to UE capabilities: this scenario is not allowed to occur if the multicast PDSCH is unicast DCI scheduled. I.e. the terminal does not expect the above scenario to occur. If the multicast PDSCH is scheduled by the group common DCI, the UE may always receive the unicast PDSCH and not receive the multicast PDSCH; if the DCI corresponding to the unicast PDSCH is not later than the DCI corresponding to the multicast PDSCH, the UE receives the unicast PDSCH and does not receive the multicast PDSCH, otherwise, the UE receives the PDSCH according to one of the following modes:

receiving and/or decoding priorities of the PDSCH configured or indicated by a network side device (such as a base station);

service priority and/or logical channel priority corresponding to the PDSCH;

the time sequence of the starting symbols of the PDSCH;

the frequency domain location of the PDSCH, e.g., low frequency, takes precedence over high frequency.

In another specific example, for a multicast SPS PDSCH, it is determined by:

(1) the configuration is carried out through multicast RRC messages, so that the UE in a multicast group has the same corresponding configuration index of SPS (semi-persistent scheduling) PDSCH, and can be activated or deactivated through multicast DCI (downlink control information), or activated or deactivated through unicast DCI (downlink control information), wherein the multicast RRC is also called group common RRC or multicast RRC, the multicast DCI is also called group common DCI or multicast DCI, and the unicast DCI is also called UE specific DCI;

(2) through the UE-specific RRC message configuration, therefore, the UE in the multicast group may not have the same configuration index corresponding to the SPS PDSCH, and may be activated or deactivated through the unicast DCI.

As shown in fig. 5, both UE1 and UE2 receive MBS1(Multicast Broadcast Service), and the base station schedules MBS1 traffic data through SPS PDSCH. For the UE1, only one SPS PDSCH is supported for configuration, and multiple SPS PDSCHs are not supported. While UE2 supports multiple SPS PDSCHs, UE2 also receives other MBS traffic or unicast traffic data.

It is assumed that the multicast SPS PDSCH is configured by group common RRC signaling, i.e. the configuration index of the SPS PDSCH is the same for different UEs in one MBS group. Since UE1 only supports configuring one SPS PDSCH, the base station configures SPS PDSCH 0 for transmitting MBS1 traffic data. For the UE2, other MBS traffic or unicast traffic data is transmitted over SPS PDSCH 1. For the UE2, which has activated two groups of common SPS PDSCH simultaneously, SPS PDSCH 0 and SPS PDSCH1 may overlap in the time-frequency domain in a certain time slot, or both groups of common PDSCH may not be received in one time slot but in one time slot by the UE capability. Therefore, a certain rule needs to be defined to determine which SPS PDSCH the UE receives, wherein the UE can determine the received or decoded PDSCH according to one of the following ways:

service priority and/or logical channel priority corresponding to the PDSCH;

the time sequence of the starting symbols of the PDSCH;

In the above scenario where two PDSCHs collide with each other, the UE may determine the PDSCH to be received or decoded according to one of the specific rules. The following is a scenario of multiple PDSCH collisions, where the UE may determine the received or decoded PDSCH according to the at least one specific rule, and when the UE needs to determine the received or decoded PDSCH according to multiple rules, the present invention does not limit the order of use or priority of the different rules.

In a specific example, the UE supports receiving 2 time-division multiplexed group common PDSCHs in one time slot. As shown in FIG. 6, PDSCHs 1-4 are all group common PDSCHs. The UE needs to select two PDSCHs with non-overlapping time domains from the PDSCHs 1-4 for reception and decoding. Wherein the UE may select two time-domain non-overlapping PDSCHs for reception and decoding according to at least one of:

a scheduling mode of the PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

For example, PDSCH1, PDSCH3 and PDSCH4 are group common DCI scheduled or SPS PDSCH, and PDSCH2 is UE-specific DCI scheduled, the UE may first determine to preferentially receive PDSCH2 in the dynamically scheduled group common PDSCH according to whether DCI corresponding to the group common PDSCH is group common DCI or UE-specific DCI, and therefore the UE does not receive PDSCH1 and PDSCH3 because PDSCH1 and PDSCH3 overlap with PDSCH2 time domain resources, and it is determined that the UE receives PDSCH2 and PDSCH4 in one time slot because the UE can receive two PDSCHs whose time domains do not overlap in the time slot.

For another example, PDSCH2 is SPS PDSCH, PDSCH3 and PDSCH4 are group common DCI scheduled, and PDSCH1 is UE-specific DCI scheduled, the UE may determine whether PDSCH is DCI dynamically scheduled, determine that the reception priority of PDSCH1, PDSCH3, PDSCH4 is greater than PDSCH2, and determine that the reception priority of PDSCH1 is greater than PDSCH3 and PDSCH4 according to whether DCI corresponding to the group common PDSCH is UE-specific DCI or group common DCI, so that the UE determines to receive PDSCH1 preferentially, the UE does not receive PDSCH2 because PDSCH2 overlaps with PDSCH1 time domain resources, the UE may receive two PDSCH with time domain in one time slot, and then select to receive one PDSCH from PDSCH3 and PDSCH4, because PDSCH3 and PDSCH4 are both group common PDSCH scheduled group common DCI, and the UE may determine to receive the DCI scheme provided in the embodiment of the present application, that at least one of the following:

priority information of the PDSCH;

frequency domain location of PDSCH.

For example, the UE determines to receive PDSCH3 and not PDSCH4 according to the corresponding priorities of PDSCH3 and PDSCH4.

In another specific example, the UE supports reception of one group common PDSCH and one unicast PDSCH on different symbols within one slot, i.e., one multicast PDSCH and one unicast PDSCH time division multiplexed within one slot. In FIG. 7 PDSCH1 is a unicast PDSCH, PDSCHs 2-4 are group common PDSCHs, and PDSCH2 and PDSCH3 are SPS PDSCHs, while PDSCH4 is a group common DCI scheduled PDSCH. The UE may first determine to preferentially receive the unicast PDSCH, i.e., PDSCH1, according to a collision processing principle of the unicast PDSCH and the multicast PDSCH, determine not to receive PDSCH2 because PDSCH2 overlaps PDSCH1, and in the remaining PDSCH3 and PDSCH4, the UE may preferentially receive the DCI scheduled PDSCH, i.e., PDSCH1 and PDSCH4, in the time slot, according to a collision processing manner between the group common PDSCHs, for example, in the dynamically scheduled PDSCH and SPS PDSCH.

It should be noted that, in the PDSCH transmission method provided in the embodiment of the present application, the execution subject may be a PDSCH transmission device, or a module used in the PDSCH transmission device to execute a loading PDSCH transmission method. In the embodiment of the present application, a PDSCH transmission method performed by a PDSCH transmission device is taken as an example to describe the PDSCH transmission method provided in the embodiment of the present application.

An embodiment of the present application provides a PDSCH transmitting device, which is applied to a terminal 300, and as shown in fig. 8, the device includes:

a processing module 310, configured to determine, if multiple PDSCHs scheduled by the network side device collide, a received or decoded PDSCH according to at least one of the following information:

a scheduling mode of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

In some embodiments, the apparatus further comprises:

a receiving module, configured to receive the determined PDSCH; and/or

And a decoding module for decoding the determined PDSCH.

In some embodiments, the priority information comprises any one of:

receiving and/or decoding priorities;

a physical layer priority;

a traffic priority and/or a logical channel priority;

in some embodiments, the plurality of collided PDSCHs are dynamically scheduled PDSCHs, and the processing module is specifically configured to determine the received or decoded PDSCH in any one of the following manners if the plurality of PDSCHs include a group common PDSCH and a unicast PDSCH:

receiving or decoding a unicast PDSCH;

In some embodiments, the multiple collided PDSCHs are dynamically scheduled PDSCHs, and the processing module 310 is specifically configured to determine the received or decoded PDSCH according to any one of the following information if the multiple PDSCHs only include a group common PDSCH:

priority information of the PDSCH;

frequency domain location of PDSCH;

whether the DCI scheduling the PDSCH is a terminal-specific DCI.

In some embodiments, the plurality of collided PDSCHs includes a dynamically scheduled PDSCH and a semi-persistently scheduled PDSCH, and the processing module 310 is specifically configured to receive or decode the dynamically scheduled PDSCH if the dynamically scheduled PDSCH is a unicast PDSCH; and if the dynamically scheduled PDSCH is the group common PDSCH, receiving or decoding the dynamically scheduled PDSCH, or determining a PDSCH receiving or decoding mode according to whether the dynamically scheduled PDSCH is the PDSCH scheduled by the terminal specific DCI.

In some embodiments, the processing module 310 is specifically configured to receive or decode the dynamically scheduled PDSCH if the dynamically scheduled PDSCH is the DCI-scheduled PDSCH, and determine the received or decoded PDSCH according to any one of the following information if the dynamically scheduled PDSCH is not the DCI-scheduled PDSCH: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the starting symbol and/or the ending symbol of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

In some embodiments, the multiple colliding PDSCHs are semi-persistently scheduled PDSCHs, and the processing module 310 is specifically configured to receive or decode the PDSCHs according to a semi-persistently scheduled configuration index size if the multiple PDSCHs only include unicast PDSCHs; if the PDSCHs include a group common PDSCH, determining a received or decoded PDSCH according to any one of the following information: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the time sequence of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

The PDSCH transmitting device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a Network Attached Storage (NAS), a personal computer (personal computer, PC), a Television (TV), a teller machine, a self-service machine, and the like, and the embodiments of the present application are not limited in particular.

The PDSCH transmitting device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

An embodiment of the present application provides a PDSCH transmitting device, which is applied to a network side device 400, and as shown in fig. 9, the device includes:

a sending module 410, configured to send multiple PDSCHs to a terminal in one time slot, where time domains and/or frequency domains of the multiple PDSCHs are overlapped, or the multiple PDSCHs exceed a receiving capability of the terminal, where the receiving capability is a capability of the terminal to receive multiple unicast and/or group common PDSCHs in one time slot.

In some embodiments, the apparatus further comprises:

the apparatus includes a determining module configured to determine a plurality of PDSCHs to be transmitted to a terminal, where the PDSCHs to be transmitted to different terminals may be different.

In some embodiments, the plurality of PDSCHs comprises any one of:

unicast PDSCH and group common PDSCH scheduled by group common DCI;

at least two group common PDSCHs scheduled by the group common DCI;

a semi-persistently scheduled group common PDSCH;

unicast PDSCH and semi-persistently scheduled group common PDSCH.

Optionally, an embodiment of the present application further provides an electronic device, which includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements each process of the above-mentioned PDSCH transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and the non-mobile electronic devices described above.

The electronic device of the embodiment may be a terminal. Fig. 10 is a schematic diagram of a hardware structure of a terminal for implementing various embodiments of the present application, where the terminal 50 includes, but is not limited to: a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. Those skilled in the art will appreciate that the terminal configuration shown in fig. 10 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present application, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

It should be understood that, in the embodiment of the present application, the radio frequency unit 51 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted to the base station. Generally, the radio frequency unit 51 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 51 may also communicate with a network and other devices through a wireless communication system.

The memory 59 may be used to store software programs as well as various data. The memory 59 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 59 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 510 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 59 and calling data stored in the memory 59, thereby performing overall monitoring of the terminal. Processor 510 may include one or at least two processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.

The terminal 50 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 via a power management system, so that functions of managing charging, discharging, and power consumption are performed via the power management system.

In addition, the terminal 50 includes some functional modules that are not shown, and will not be described in detail herein.

In some embodiments, the processor 510 is configured to determine the received or decoded PDSCH according to at least one of the following information if multiple PDSCHs scheduled by the network side device collide:

a scheduling mode of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

In some embodiments, the priority information comprises any one of:

receiving and/or decoding priorities;

a physical layer priority;

a traffic priority and/or a logical channel priority;

if the plurality of PDSCHs include a group common PDSCH and a unicast PDSCH, determining a received or decoded PDSCH by any one of:

receiving or decoding a unicast PDSCH;

priority information of the PDSCH;

frequency domain location of PDSCH;

whether the DCI scheduling the PDSCH is a terminal-specific DCI.

if the dynamically scheduled PDSCH is the PDSCH scheduled by the terminal specific DCI, receiving or decoding the dynamically scheduled PDSCH, and if the dynamically scheduled PDSCH is not the PDSCH scheduled by the terminal specific DCI, determining the received or decoded PDSCH according to any one of the following information: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the starting symbol and/or the ending symbol of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

if the PDSCHs include a group common PDSCH, determining a received or decoded PDSCH according to any one of the following information: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the time sequence of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

The electronic device of this embodiment may also be a network side device. As shown in fig. 11, the network-side device 600 includes: antenna 61, radio frequency device 62, baseband device 63. The antenna 61 is connected to a radio frequency device 62. In the uplink direction, the rf device 62 receives information via the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes information to be transmitted and transmits the information to the radio frequency device 62, and the radio frequency device 62 processes the received information and transmits the processed information through the antenna 61.

The above-mentioned band processing means may be located in the baseband means 63, and the method performed by the network side device in the above embodiment may be implemented in the baseband means 63, where the baseband means 63 includes a processor 64 and a memory 65.

The baseband device 63 may include at least one baseband board, for example, and a plurality of chips are disposed on the baseband board, as shown in fig. 11, wherein one chip, for example, the processor 64, is connected to the memory 65 to call up the program in the memory 65 to perform the network side device operation shown in the above method embodiment.

The baseband device 63 may further include a network interface 66 for exchanging information with the radio frequency device 62, such as a Common Public Radio Interface (CPRI).

The processor may be a single processor or a combination of multiple processing elements, for example, the processor may be a CPU, an ASIC, or one or more integrated circuits configured to implement the method performed by the above network-side device, for example: one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, or the like. The storage element may be a memory or a combination of a plurality of storage elements.

The memory 65 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a Read-only memory (ROM), a programmable Read-only memory (PROM), an erasable programmable Read-only memory (erasabprom, EPROM), an electrically erasable programmable Read-only memory (EEPROM), or a flash memory. The volatile memory may be a Random Access Memory (RAM) which functions as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (staticiram, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (syncronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhanced synchronous dynamic random access memory (EnhancedSDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct memory bus random access memory (DRRAM). The memory 65 described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, the processor 64 is configured to transmit multiple PDSCHs to a terminal in one time slot, where the multiple PDSCHs overlap in time domain and/or frequency domain, or exceed the terminal's reception capability, which is the terminal's capability to receive multiple unicast and/or group common PDSCHs in one time slot.

In some embodiments, the plurality of PDSCHs comprises any one of:

unicast PDSCH and group common PDSCH scheduled by group common DCI;

at least two group common PDSCHs scheduled by the group common DCI;

a semi-persistently scheduled group common PDSCH;

unicast PDSCH and semi-persistently scheduled group common PDSCH.

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the foregoing PDSCH transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the PDSCH transmission method according to the embodiment, and can achieve the same technical effect, and the details are not repeated here to avoid repetition.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for transmitting a Physical Downlink Shared Channel (PDSCH) is executed by a terminal and comprises the following steps:

if the plurality of PDSCHs scheduled by the network side equipment conflict, determining the received or decoded PDSCH according to at least one item of information:

a scheduling mode of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

2. The PDSCH transmission method of claim 1, wherein the priority information includes any of:

receiving and/or decoding priorities;

a physical layer priority;

traffic priority and/or logical channel priority.

3. The PDSCH transmission method according to claim 1 or 2, wherein the collided PDSCH are dynamically scheduled PDSCH, and the determining the received or decoded PDSCH according to at least one of the following information comprises:

receiving or decoding a unicast PDSCH;

4. The PDSCH transmission method according to claim 1 or 2, wherein the collided PDSCH are dynamically scheduled PDSCH, and the determining the received or decoded PDSCH according to at least one of the following information comprises:

priority information of the PDSCH;

frequency domain location of PDSCH;

whether the DCI scheduling the PDSCH is a terminal-specific DCI.

5. The PDSCH transmission method according to claim 1 or 2, wherein the plurality of colliding PDSCHs includes a dynamically scheduled PDSCH and a semi-persistently scheduled PDSCH, and determining a PDSCH reception or decoding manner according to whether the PDSCH is a group common PDSCH or a unicast PDSCH comprises:

6. The PDSCH transmission method according to claim 5, wherein the determining the PDSCH receiving or decoding mode according to whether the dynamically scheduled PDSCH is the PDSCH scheduled by the terminal specific DCI comprises:

7. The method of claim 1 or 2, wherein the plurality of colliding PDSCHs are semi-persistently scheduled PDSCHs, and determining a PDSCH reception or decoding manner according to whether the PDSCH is a group common PDSCH or a unicast PDSCH comprises:

if the plurality of PDSCHs include a group common PDSCH, determining a received or decoded PDSCH according to any one of the following information: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the time sequence of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

8. A method for transmitting a Physical Downlink Shared Channel (PDSCH) is executed by a network side device and comprises the following steps:

the PDSCHs are scheduled by Downlink Control Information (DCI); or

9. The PDSCH transmission method of claim 8, wherein the plurality of PDSCHs include any of:

unicast PDSCH and group common PDSCH scheduled by group common DCI;

at least two group common PDSCHs scheduled by the group common DCI;

a semi-persistently scheduled group common PDSCH;

unicast PDSCH and semi-persistently scheduled group common PDSCH.

10. A physical downlink shared channel PDSCH transmission apparatus, comprising:

a scheduling mode of the PDSCH;

PDSCH is a group common PDSCH or unicast PDSCH;

scheduling Downlink Control Information (DCI) of the PDSCH;

priority information of the PDSCH;

a starting symbol of the PDSCH;

frequency domain location of PDSCH.

11. The PDSCH transmission device of claim 10, wherein the priority information includes any of:

receiving and/or decoding priorities;

a physical layer priority;

traffic priority and/or logical channel priority.

12. The PDSCH transmitting device of claim 10 or 11, wherein the multiple colliding PDSCHs are dynamically scheduled PDSCHs, and the processing module is specifically configured to determine the received or decoded PDSCH in any one of the following manners if the multiple PDSCHs include a group common PDSCH and a unicast PDSCH:

receiving or decoding a unicast PDSCH;

13. The PDSCH transmitting device of claim 10 or 11, wherein the multiple colliding PDSCHs are dynamically scheduled PDSCHs, and the processing module is specifically configured to determine the received or decoded PDSCH according to any of the following information if the multiple PDSCHs only include a group common PDSCH:

priority information of the PDSCH;

frequency domain location of PDSCH;

whether the DCI scheduling the PDSCH is a terminal-specific DCI.

14. The PDSCH transmitting device of claim 10 or 11, wherein the collided PDSCHs include a dynamically scheduled PDSCH and a semi-persistently scheduled PDSCH, and the processing module is specifically configured to receive or decode the dynamically scheduled PDSCH if the dynamically scheduled PDSCH is a unicast PDSCH; and if the dynamically scheduled PDSCH is the group common PDSCH, receiving or decoding the dynamically scheduled PDSCH, or determining a PDSCH receiving or decoding mode according to whether the dynamically scheduled PDSCH is the PDSCH scheduled by the terminal specific DCI.

15. The PDSCH transmitting device of claim 14, wherein the processing module is specifically configured to receive or decode the dynamically scheduled PDSCH if the dynamically scheduled PDSCH is a terminal-specific DCI scheduled PDSCH, and to determine the received or decoded PDSCH according to any of the following information if the dynamically scheduled PDSCH is not a terminal-specific DCI scheduled PDSCH: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the starting symbol and/or the ending symbol of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

16. The PDSCH transmitting device of claim 10 or 11, wherein the multiple colliding PDSCHs are semi-persistently scheduled PDSCHs, and the processing module is specifically configured to receive or decode the PDSCHs according to a semi-persistently scheduled configuration index size if the multiple PDSCHs only include unicast PDSCHs; if the plurality of PDSCHs include a group common PDSCH, determining a received or decoded PDSCH according to any one of the following information: the priority information of the PDSCH, the starting symbol of the PDSCH and/or the time sequence of the DCI scheduling the PDSCH, and the frequency domain position of the PDSCH.

17. A physical downlink shared channel PDSCH transmission apparatus, comprising:

a sending module, configured to send multiple PDSCHs to a terminal in a time slot, where time domains and/or frequency domains of the multiple PDSCHs are overlapped, or the multiple PDSCHs exceed a receiving capability of the terminal, where the receiving capability is a capability of the terminal to receive multiple unicast and/or group common PDSCHs in a time slot;

the PDSCHs are scheduled by Downlink Control Information (DCI); or

18. The PDSCH transmitting device of claim 17, wherein the plurality of PDSCHs include any of:

unicast PDSCH and group common PDSCH scheduled by group common DCI;

at least two group common PDSCHs scheduled by the group common DCI;

a semi-persistently scheduled group common PDSCH;

unicast PDSCH and semi-persistently scheduled group common PDSCH.

19. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method of any one of claims 1-7 or implementing the steps of the method of any one of claims 8-9.

20. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1-7 or carry out the steps of the method according to any one of claims 8-9.