CN117897921A

CN117897921A - Data receiving method and device and terminal equipment

Info

Publication number: CN117897921A
Application number: CN202180101937.6A
Authority: CN
Inventors: 王淑坤; 付喆
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-12-03
Filing date: 2021-12-03
Publication date: 2024-04-16
Also published as: WO2023097665A1

Abstract

The embodiment of the application provides a data receiving method and device and terminal equipment, wherein the method comprises the following steps: the terminal device determines the number of PDSCH scheduled in the first time slot, wherein the PDSCH scheduled in the first time slot comprises at least one of the following: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service; and if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment, the terminal equipment receives the PDSCH based on a priority strategy.

Description

Data receiving method and device and terminal equipment

Technical Field

The embodiment of the application relates to the technical field of mobile communication, in particular to a data receiving method and device and terminal equipment.

Background

The terminal device supports reception of multiple service types, which results in the possibility that the terminal device receives multiple service data on one slot. However, the reception capability of the terminal device is limited, and how the terminal device receives service data in the case where the capability thereof is limited is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a data receiving method and device, terminal equipment, a chip, a computer readable storage medium, a computer program product and a computer program.

The data receiving method provided by the embodiment of the application comprises the following steps:

the terminal device determines the number of physical downlink shared channels (Physical Downlink Shared Channel, PDSCH) scheduled in a first time slot, wherein the PDSCH scheduled in the first time slot comprises at least one of: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service;

and if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment, the terminal equipment receives the PDSCH based on a priority strategy.

The data receiving device provided by the embodiment of the application is applied to terminal equipment, and the device comprises:

a determining unit, configured to determine the number of PDSCH scheduled in the first slot, where the PDSCH scheduled in the first slot includes at least one of: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service;

and the receiving unit is used for receiving the PDSCH based on a priority strategy if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment.

The terminal equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the data receiving method.

The chip provided by the embodiment of the application is used for realizing the data receiving method.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the data receiving method.

The computer readable storage medium provided in the embodiments of the present application is used for storing a computer program, where the computer program makes a computer execute the above-mentioned data receiving method.

The computer program product provided by the embodiment of the application comprises computer program instructions, wherein the computer program instructions enable a computer to execute the data receiving method.

The computer program provided in the embodiments of the present application, when executed on a computer, causes the computer to execute the data receiving method described above.

Through the technical scheme, the terminal equipment determines the quantity of the PDSCH scheduled in the first time slot, wherein the PDSCH scheduled in the first time slot comprises at least one of the following steps: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service; and if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment, the terminal equipment receives the PDSCH based on a priority strategy. In this way, the terminal device can receive the PDSCH based on the priority policy under the condition that the capability of the terminal device is limited, so that the PDSCH with high priority can be preferentially received.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

fig. 2 is a schematic diagram of a protocol stack corresponding to a PTM mode and a PTP mode in the embodiment of the present application;

fig. 3 is a schematic flow chart of a data receiving method according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a data receiving device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG. 6 is a schematic block diagram of a chip of an embodiment of the present application;

fig. 7 is a schematic block diagram of a communication system provided in an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

It should be understood that the present embodiments are illustrated by way of example only with respect to communication system 100, but the present embodiments are not limited thereto. That is, the technical solution of the embodiment of the present application may be applied to various communication systems, for example: long term evolution (Long Term Evolution, LTE) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), internet of things (Internet of Things, ioT) systems, narrowband internet of things (Narrow Band Internet of Things, NB-IoT) systems, enhanced Machine-type-Type Communications (eMTC) systems, 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

In the communication system 100 shown in fig. 1, the network device 120 may be an access network device in communication with the terminal device 110. The access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, or a base station (gNB) in a NR system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 may be a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

Terminal device 110 may be any terminal device including, but not limited to, a terminal device that employs a wired or wireless connection with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, an IoT device, a satellite handset, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handset with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further comprise a core network device 130 in communication with the base station, which core network device 130 may be a 5G core,5gc device, e.g. an access and mobility management function (Access and Mobility Management Function, AMF), further e.g. an authentication server function (Authentication Server Function, AUSF), further e.g. a user plane function (User Plane Function, UPF), further e.g. a session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example a session management function+a data gateway (Session Management Function + Core Packet Gateway, smf+pgw-C) device of the core network. It should be appreciated that SMF+PGW-C may perform the functions performed by both SMF and PGW-C. In the network evolution process, the core network device may also call other names, or form a new network entity by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication may also be achieved by establishing connections between various functional units in the communication system 100 through a next generation Network (NG) interface.

For example, the terminal device establishes an air interface connection with the access network device through an NR interface, and is used for transmitting user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with AMF through NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), can establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with AMF through NG interface 2 (N2 for short); the UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with the data network through an NG interface 6 (N6 for short); the AMF may establish a control plane signaling connection with the SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily illustrates one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and each base station may include other number of terminal devices within a coverage area, which is not limited in the embodiment of the present application.

It should be noted that fig. 1 illustrates, by way of example, a system to which the present application is applicable, and of course, the method shown in the embodiment of the present application may be applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship. It should also be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication that there is an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B. It should also be understood that, in the embodiments of the present application, reference to "corresponding" may mean that there is a direct correspondence or an indirect correspondence between the two, or may mean that there is an association between the two, or may be a relationship between an instruction and an indicated, configured, or the like. It should also be understood that "predefined" or "predefined rules" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation manner of the present application is not limited. Such as predefined may refer to what is defined in the protocol. It should also be understood that, in the embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied in future communication systems, which are not limited in this application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

With the speed, delay, and the like of people,The pursuit of high-speed mobility, energy efficiency and the diversity, complexity of future life business for which the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization began developing 5G. The main application scenario of 5G is: enhanced mobile Ultra-wideband (enhanced Mobile Broadband, emmbb), low latency high reliability communication (URLLC), large-scale Machine-based communication (mctc).

On the one hand, embbs still target users to obtain multimedia content, services and data, and their demand is growing very rapidly. On the other hand, since an eMBB may be deployed in different scenarios, such as indoors, urban, rural, etc., its capabilities and requirements are also quite different, so that detailed analysis must be performed in connection with a specific deployment scenario, not in general. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

MBMS

MBMS is a technology for transmitting data from one data source to a plurality of terminal equipments through a shared network resource, which can effectively utilize the network resource while providing a multimedia service, and realize broadcasting and multicasting of a multimedia service of a higher rate (e.g., 256 kbps).

Due to the low MBMS spectrum efficiency, it is not sufficient to effectively carry and support the operation of the mobile tv type service. In LTE, 3GPP has therefore explicitly proposed to enhance the support capability for the downlink high speed MBMS service and to determine the design requirements for the physical layer and the air interface.

The 3gpp R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes the concept of a single frequency network (Single Frequency Network, SFN), i.e. a multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast service Single Frequency Network, MBSFN), wherein the MBSFN uses a unified frequency to simultaneously transmit traffic data in all cells, but synchronization between the cells is guaranteed. The method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocols.

In LTE or LTE-Advanced (LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode. In addition, the reception of the MBMS service is applicable to terminal devices in an idle state or a connected state.

A single cell point-to-multipoint (Single Cell Point To Multiploint, SC-PTM) concept is introduced in 3gpp r13, SC-PTM being based on the MBMS network architecture.

MBMS introduces new logical channels including Single Cell multicast control channel (SC-MCCH) and Single Cell multicast transport channel (SC-MTCH) and Single Cell-Multicast Transport Channel. The SC-MCCH and SC-MTCH are mapped onto a Downlink-Shared Channel (DL-SCH), and further, the DL-SCH is mapped onto a physical Downlink Shared Channel (Physical Downlink Shared Channel, PDSCH), wherein the SC-MCCH and SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a physical Channel. The SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operation.

MBMS introduces a new system information block (System Information Block, SIB) type, SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, the radio frame and subframe for scheduling the SC-MCCH and other information. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m=0, where SFN represents a system frame number of the boundary, and m is a modification period (i.e., SC-MCCH-modification period) of the SC-MCCH configured in SIB20. 2) The radio frame of the scheduling SC-MCCH meets the following conditions: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents the system frame number of the radio frame, MCCH-repetition period represents the repetition period of the SC-MCCH, and MCCH-Offset represents the Offset of the SC-MCCH. 3) The subframes of the scheduling SC-MCCH are indicated by SC-MCCH-Subframe.

The SC-MCCH is scheduled through a physical downlink control channel (Physical Downlink Control Channel, PDCCH). In one aspect, a new radio network temporary identity (Radio Network Tempory Identity, RNTI), i.e., single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (e.g., SC-MCCH PDCCH) for scheduling the SC-MCCH, optionally with the SC-RNTI fixed value FFFC. On the other hand, a new RNTI, i.e., a single cell notification RNTI (Single Cell Notification RNTI, SC-N-RNTI) is introduced to identify a PDCCH (e.g., notification PDCCH) for indicating a change notification of the SC-MCCH, optionally, the SC-N-RNTI is fixed to a value of FFFB; further, the change notification may be indicated with one bit of 8 bits (bits) of DCI 1C. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., scptm configuration) for configuring configuration information of the SC-PTM. The configuration information of the SC-PTM comprises: temporary mobile Group identity (Temporary Mobile Group Identity, TMGI), session identity (session id), group RNTI (G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information, SC-PTM service information of neighbor cells, and the like. Note that SC-PTM in R13 does not support the robust header compression (Robust Header Compression, ROHC) function.

The downlink discontinuous reception of the SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-scheduling cycle, and SC-MTCH-scheduling offset.

When [ (SFN 10) +subframe number ] module (SC-MTCH-scheduling cycle) =sc-MTCH-scheduling offset is satisfied, a timer ondurationtimerscpm is started;

when receiving downlink PDCCH scheduling, starting a timer drx-InactivityTimerSCPTM;

the downstream SC-PTM service is received only when the timer onduration timerscpm or drx-incaactyitimerscpm is running.

The SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely a mode of SIB15 and MBMSInterestindication. The traffic continuity of the terminal device in idle state is based on the concept of frequency priority.

In the technical solution of the embodiment of the present application, a new SIB (referred to as a first SIB) is defined, where the first SIB includes configuration information of a first MCCH, where the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used to configure configuration information of a control channel of an NR MBMS, alternatively, the control channel of the NR MBMS may also be referred to as an NR MCCH (i.e. the first MCCH).

Further, the first MCCH is used to carry the first signaling, and in the embodiment of the present application, the name of the first signaling is not limited, for example, the first signaling is signaling a, where the first signaling includes configuration information of at least one first MTCH, where the first MTCH is a traffic channel (also referred to as a data channel or a transport channel) of an MBMS service, and the first MTCH is used to transport MBMS service data (such as service data of NR MBMS). In other words, the first MCCH is used to configure configuration information of a traffic channel of the NR MBMS, alternatively, the traffic channel of the NR MBMS may also be called as NR MTCH (i.e., the first MTCH).

Specifically, the first signaling is used for configuring a service channel of the NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further optionally, the service information corresponding to the service channel, for example, TMGI, session id, and other identification information for identifying the service. Scheduling information corresponding to the service channel, for example, RNTI used when MBMS service data corresponding to the service channel is scheduled, for example, G-RNTI, DRX configuration information, and the like.

The transmissions of the first MCCH and the first MTCH are scheduled based on the PDCCH. The RNTI used for scheduling the PDCCH of the first MCCH uses a unique network identifier, i.e. a fixed value. The RNTI used for scheduling PDCCH use of the first MTCH is configured through the first MCCH.

It should be noted that, in the embodiment of the present application, the naming of the first SIB, the first MCCH and the first MTCH is not limited. For convenience of description, the first SIB may also be simply referred to as SIB, the first MCCH may also be simply referred to as MCCH, and the first MTCH may also be simply referred to as MTCH, and a PDCCH (i.e. MCCH PDCCH) for scheduling the MCCH and a notification PDCCH are configured through SIB, where a PDSCH (i.e. MCCH PDSCH) for transmitting the MCCH is scheduled through DCI carried in MCCH PDCCH. Further, M PDCCHs for scheduling MTCH (i.e., MTCH 1PDCCH, MTCH 2PDCCH, …, MTCH M PDCCH) are configured through the MCCH, wherein DCI carried by MTCH n PDCCH schedules PDSCH for transmitting MTCH n (i.e., MTCH n PDSCH), n being an integer greater than or equal to 1 and less than or equal to M. The MCCH and the MTCH are mapped to the DL-SCH, and further, the DL-SCH is mapped to the PDSCH, wherein the MCCH and the MTCH belong to a logical channel, the DL-SCH belongs to a transport channel, and the PDSCH belongs to a physical channel.

It should be noted that, although the above scheme is described by taking MBMS as an example, the description of "MBMS" may be replaced by "MBS". The embodiment of the present application is described by taking MBS as an example, and the description of "MBS" may be replaced by "MBMS".

In NR systems, many scenarios require support of multicast type and broadcast type traffic demands, such as in the internet of vehicles, industrial internet, etc. It is necessary to introduce multicast type and broadcast type MBS services in the NR. It should be noted that, the multicast type MBS service refers to an MBS service transmitted through a multicast manner. The broadcast type MBS service refers to an MBS service transmitted through a broadcast manner.

In the NR system, for the multicast type MBS service, the MBS service is addressed to all terminal equipments in a certain group. The terminal device receives the multicast MBS service in the RRC connection state, and the terminal device can receive the multicast MBS service data in a Point-To-Multipoint (PTM) mode or a Point-To-Point (PTP) mode. Referring to fig. 2, the MBS service data of the ptm mode scrambles corresponding scheduling information through a G-RNTI configured by a network side, and the MBS service data of the PTP mode scrambles corresponding scheduling information through a C-RNTI.

For multicast type MBS service, after receiving the MBS service issued by the core network from the shared tunnel (tunnel), the base station may issue the MBS service to all terminal devices in a group through an air interface. Here, the base station may issue the MBS service to all terminal equipments in a group by PTP and/or PTM. For example: a group comprises a terminal device 1, a terminal device 2 and a terminal device 3, wherein the base station can issue MBS service to the terminal device 1 in a PTP mode, issue MBS service to the terminal device 2 in a PTP mode, and issue MBS service to the terminal device 3 in a PTP mode; or the base station can issue MBS business to the terminal equipment 1 in a PTP mode, and issue MBS business to the terminal equipment 2 and the terminal equipment 3 in a PTM mode; or, the base station may send the MBS service to the terminal device 1, the terminal device 2 and the terminal device 3 in the PTM mode. A shared GTP tunnel (Shared GTP tunnel) is used between the core network and the base station for transmitting MBS services, i.e. both PTM-mode MBS services and PTP-mode MBS services are shared. The base station transmits MBS service data to the UE1 and the UE2 according to the PTM mode, and transmits MBS service data to the UE3 according to the PTP mode.

In the MBS service transmission process, there is a scenario that PTP is used for PTM retransmission, that is, a Transport Block (TB) of an MBS service, where a network side performs initial transmission (abbreviated as initial transmission) by a PTM method (that is, scheduling information corresponding to G-RNTI scrambling), and if a terminal device receives a failed feedback Negative Acknowledgement (NACK), the network side performs retransmission (abbreviated as retransmission) by a PTP method (that is, scheduling information corresponding to C-RNTI scrambling). At this time, the primary transmission of the PTM mode and the retransmission of the PTP mode correspond to the same HARQ process identifier and NDI, that is, the HARQ process identifier and NDI carried in the scheduling signaling of the primary transmission are the same as the HARQ process identifier and NDI carried in the scheduling signaling of the retransmission.

The terminal device has limited reception capability for PDSCH, and some terminal devices can only receive one PDSCH in one slot and some terminal devices can receive multiple PDSCH in one slot according to the capability of the terminal device. As an example, the following tables 1 and 2 give the reception capability of the terminal device for PDSCH. As can be seen from tables 1 and 2, some terminal devices can receive only one PDSCH in one slot, and some terminal devices can receive a plurality of 2,4,7 PDSCH in one slot.

TABLE 1

TABLE 2

The terminal device supports reception of multiple service types, which results in the possibility that the terminal device receives multiple service data on one slot. However, the reception capability of the terminal device is limited, and how the terminal device receives service data in the case where the capability thereof is limited is a problem to be solved. For this reason, the following technical solutions of the embodiments of the present application are proposed.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application. Embodiments of the present application include at least some of the following.

Fig. 3 is a flow chart of a data receiving method according to an embodiment of the present application, as shown in fig. 3, where the data receiving method includes the following steps:

step 301: the terminal device determines the number of PDSCH scheduled in the first time slot, wherein the PDSCH scheduled in the first time slot comprises at least one of the following: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service.

Step 302: and if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment, the terminal equipment receives the PDSCH based on a priority strategy.

In the embodiment of the application, the terminal equipment determines the number of the PDSCH scheduled in the first time slot. In some optional embodiments, the terminal device may determine the number of PDSCH scheduled in the first slot according to the scheduling information and/or the pre-configuration information issued by the network side. Here, the scheduling information is carried in DCI, and the pre-configuration information is carried in RRC signaling. Wherein the PDSCH scheduled in the first slot includes at least one of: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service.

It should be noted that, in the embodiments of the present application, the description about "PDSCH" may be replaced by "data" or "TB".

In this embodiment of the present application, if the number of PDSCH scheduled is greater than the number of first capability indicators of the terminal device, the terminal device receives PDSCH based on a priority policy. In some alternative embodiments, the priority policy is configured for the network side (e.g., configured by the network side through RRC signaling), or predefined for the protocol. The priority policy is described below.

Scheme one

In some alternative embodiments, the priority policy includes at least one of:

The priority of PDSCH of unicast service is greater than that of PDSCH of multicast service;

the PDSCH of the multicast service has a higher priority than the PDSCH of the broadcast service.

In some optional embodiments, the PDSCH of the multicast service includes a PDSCH of a multicast dynamic scheduling and/or a PDSCH of a multicast Semi-persistent scheduling (Semi-Persistent Scheduling, SPS), and the priority policy further includes: the priority of the PDSCH of the multicast dynamic schedule is higher than the priority of the PDSCH of the multicast SPS.

In some optional embodiments, the PDSCH of the unicast service includes a PDSCH of a unicast dynamic schedule and/or a PDSCH of a unicast SPS, and the priority policy further includes: the priority of PDSCH of unicast dynamic scheduling is higher than that of PDSCH of unicast SPS.

Through the scheme, the terminal equipment can clearly determine the priority relation of the PDSCH of different service types and the priority relation of the PDSCH of different scheduling modes.

Scheme II

In some alternative embodiments, the priority policy further comprises:

the PDSCH associated with the larger SPS index has a higher priority than the PDSCH associated with the smaller SPS index; or,

the PDSCH associated with the smaller SPS index has a higher priority than the PDSCH associated with the larger SPS index.

In some alternative embodiments, the priority policy further comprises:

the priority of the PDSCH associated with the larger G-RNTI is higher than that of the PDSCH associated with the smaller G-RNTI; or,

the priority of the PDSCH associated with the smaller G-RNTI is higher than that of the PDSCH associated with the larger G-RNTI.

In some alternative embodiments, the priority policy further comprises:

the PDSCH associated with the larger TMGI is higher in priority than the PDSCH associated with the smaller TMGI; or,

the PDSCH of the smaller TMGI association has a higher priority than the PDSCH of the larger TMGI association.

In some alternative embodiments, the priority policy further comprises:

the PDSCH associated with the higher priority is higher in priority than the PDSCH associated with the lower priority.

Here, the terminal device receives first configuration information sent by the network device, where the first configuration information is used to configure the priority of the TMGI of the multicast service. In this way, the terminal device may determine the priority of the corresponding PDSCH according to the priority of the TMGI. For example: for different MBS services in multicast, the network side configures a priority for TMGI of each MBS service.

In the above scheme, the PDSCH may have an association relationship with at least one of the following: SPS index, G-RNTI, TMGI. For example: for a PDSCH of a multicast SPS, it may be associated with one SPS index, one G-RNTI, and one TMGI. For multicast dynamically scheduled PDSCH, it may be associated with one G-RNTI and one TMGI. For a PDSCH unicast SPS, it may be associated with one SPS index.

As an example: PDSCH 1 and PDSCH 2 are both multicast SPS PDSCH, the G-RNTIs associated with these two PDSCHs are the same, the TMGIs are the same, and the SPS indices are different, then if the SPS index associated with PDSCH 1 is greater than the SPS index associated with PDSCH 2, the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2, or conversely, if the SPS index associated with PDSCH 1 is less than the SPS index associated with PDSCH 2, the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2.

As an example: PDSCH 1 and PDSCH 2 are both multicast dynamically scheduled PDSCH, the G-RNTIs associated with these two PDSCHs are the same and the TMGIs are different, and if the TMGI associated with PDSCH 1 is greater than the TMGI associated with PDSCH 2, the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2, or otherwise, if the TMGI associated with PDSCH 1 is less than the TMGI associated with PDSCH 2, the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2.

As an example: PDSCH 1 and PDSCH 2 are both multicast dynamically scheduled PDSCH, and the G-RNTIs associated with these two PDSCHs are different, and if the G-RNTI associated with PDSCH 1 is greater than the G-RNTI associated with PDSCH 2, the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2, or otherwise, if the G-RNTI associated with PDSCH 1 is less than the G-RNTI associated with PDSCH 2, the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2.

As an example: PDSCH 1 and PDSCH 2 are both multicast dynamic scheduling PDSCH, and the G-RNTIs associated with these two PDSCHs are the same and the TMGIs are different, and if the priority of the TMGI associated with PDSCH 1 is higher than the priority of the TMGI associated with PDSCH 2, then the priority of PDSCH 1 is considered to be higher than the priority of PDSCH 2.

As an example: if multiple PDSCH of multicast SPS are located in the same time slot and the terminal device cannot receive the multiple PDSCH at the same time, the terminal device receives PDSCH according to the size of the SPS index associated with PDSCH, or PDSCH according to the size of the TMGI associated with PDSCH, or PDSCH according to the size of the G-RNTI associated with PDSCH.

Through the scheme, the terminal equipment can explicitly associate different SPS indexes and/or priority relations of the G-RNTI and/or PDSCH of the TMGI.

The first and second embodiments may be implemented alone or in combination.

In this embodiment of the present application, the terminal device receives PDSCH based on a priority policy, including: for a plurality of PDSCHs scheduled in the first time slot, the terminal device receives a part of PDSCH in the plurality of PDSCH and discards another part of PDSCH in the plurality of PDSCH, wherein the received part of PDSCH has a higher priority than the discarded part of PDSCH. Here, optionally, the number of received part of PDSCH is equal to or less than the number of first capability indications of the terminal device.

As an example: 5 PDSCH are scheduled in the first time slot, PDSCH 1,PDSCH 2,PDSCH 3,PDSCH 4 and PDSCH 5 are respectively, and the terminal device receives 2 PDSCH at most in one time slot, so the terminal device can determine that the priority order of the 5 PDSCH is from high to low in sequence according to the priority policy: PDSCH 3, PDSCH 2, PDSCH 5, PDSCH 1, PDSCH 4, and the terminal device receives PDSCH 3 and PDSCH 2, and discards PDSCH 5, PDSCH 1, and PDSCH 4.

Further, in some optional embodiments, the terminal device feeds back a Negative Acknowledgement (NACK) for the dropped PDSCH to the network device, and stops a DRX timer associated with the HARQ process identifier corresponding to the dropped PDSCH or waits for the DRX timer to timeout, where the DRX timer includes a DRX retransmission timer and/or a DRX inactivity timer. Here, the DRX retransmission timer is a DRX activation time during operation, the DRX inactivity timer is a DRX activation time during operation, and the terminal device listens to the PDCCH at the DRX activation time.

In some optional embodiments, the terminal device reports a first capability of the terminal device to a network device, where the first capability is used to indicate at least one of:

The maximum number of PDSCH of all the services which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of the multicast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of the broadcast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of unicast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of multicast service and broadcast service that the terminal equipment can receive in the same time slot;

the maximum number of PDSCH of multicast service and unicast service which can be received by the terminal equipment in the same time slot;

the terminal device can receive the maximum number of PDSCH of the broadcast service and the unicast service in the same time slot.

Here, the network device performs PDSCH scheduling for the terminal device according to the first capability reported by the terminal device, so as to ensure that the number of PDSCH scheduled by the terminal device in one time slot does not exceed the number indicated by the first capability as much as possible.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solutions of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application. For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described in detail. As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be considered as disclosed herein. For example, the various embodiments and/or technical features of the various embodiments described herein may be combined with any other of the prior art without conflict, and the combined technical solutions should also fall within the scope of protection of the present application.

It should be further understood that, in the various method embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application. Further, in the embodiment of the present application, the terms "downstream", "upstream" and "sidestream" are used to indicate a transmission direction of signals or data, where "downstream" is used to indicate that the transmission direction of signals or data is a first direction from a station to a user equipment of a cell, "upstream" is used to indicate that the transmission direction of signals or data is a second direction from the user equipment of the cell to the station, and "sidestream" is used to indicate that the transmission direction of signals or data is a third direction from the user equipment 1 to the user equipment 2. For example, "downstream signal" means that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and/or" is merely an association relationship describing the association object, which means that three relationships may exist. Specifically, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Fig. 4 is a schematic structural diagram of a data receiving apparatus according to an embodiment of the present application, which is applied to a terminal device, as shown in fig. 4, where the data receiving apparatus includes:

a determining unit 401, configured to determine the number of PDSCH scheduled in the first slot, where the PDSCH scheduled in the first slot includes at least one of: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service;

and a receiving unit 402, configured to receive PDSCH based on a priority policy if the number of PDSCH scheduled is greater than the number of first capability indicators of the terminal device.

In some alternative embodiments, the priority policy includes at least one of:

In some optional embodiments, the PDSCH of the multicast service includes a PDSCH of a multicast dynamic schedule and/or a PDSCH of a multicast SPS, and the priority policy further includes:

the priority of the PDSCH of the multicast dynamic schedule is higher than the priority of the PDSCH of the multicast SPS.

In some optional embodiments, the PDSCH of the unicast service includes a PDSCH of a unicast dynamic schedule and/or a PDSCH of a unicast SPS, and the priority policy further includes:

The priority of PDSCH of unicast dynamic scheduling is higher than that of PDSCH of unicast SPS.

In some alternative embodiments, the priority policy further comprises:

the priority policy further includes:

In some alternative embodiments, the priority policy further comprises:

In some optional embodiments, the receiving unit 402 is further configured to receive first configuration information sent by a network device, where the first configuration information is used to configure a priority of a TMGI of the multicast service.

In some optional embodiments, the receiving unit 402 is configured to receive a portion of PDSCH in the plurality of PDSCH for the plurality of PDSCH scheduled in the first slot, and discard another portion of PDSCH in the plurality of PDSCH, where the received portion of PDSCH has a higher priority than the discarded portion of PDSCH.

In some alternative embodiments, the apparatus further comprises:

a feedback unit 403, configured to feedback NACK for the discarded PDSCH to the network device;

and stopping the Discontinuous Reception (DRX) timer associated with the HARQ process identifier corresponding to the discarded PDSCH or waiting for the DRX timer to be overtime by the terminal equipment, wherein the DRX timer comprises a DRX retransmission timer and/or a DRX inactivity timer.

In some alternative embodiments, the apparatus further comprises:

a reporting unit, configured to report, to a network device, a first capability of the terminal device, where the first capability is used to indicate at least one of:

It should be understood by those skilled in the art that the above description of the data receiving apparatus of the embodiments of the present application may be understood with reference to the description of the data receiving method of the embodiments of the present application.

Fig. 5 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device may be a terminal device. The communication device 500 shown in fig. 5 comprises a processor 510, from which the processor 510 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 5, the communication device 500 may also include a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the methods in embodiments of the present application.

Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into the processor 510.

Optionally, as shown in fig. 5, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, the number of which may be one or more.

The communication device 500 may specifically be a terminal device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 6 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 600 shown in fig. 6 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 6, the chip 600 may further include a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the methods in embodiments of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the chip 600 may also include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

Optionally, the chip 600 may further include an output interface 640. Wherein the processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

The chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

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

Fig. 7 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in fig. 7, the communication system 700 includes a terminal device 710 and a network device 720.

The terminal device 710 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program. The computer readable storage medium may be applied to a terminal device in the embodiments of the present application, and the computer program makes a computer execute corresponding processes implemented by the terminal device in each method in the embodiments of the present application, which are not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions. The computer program product may be applied to a terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program. The computer program may be applied to the terminal device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of data reception, the method comprising:

the terminal equipment determines the number of the Physical Downlink Shared Channels (PDSCHs) scheduled in a first time slot, wherein the PDSCHs scheduled in the first time slot comprise at least one of the following: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service;

and if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment, the terminal equipment receives the PDSCH based on a priority strategy.
The method of claim 1, wherein the priority policy comprises at least one of:

the priority of PDSCH of unicast service is greater than that of PDSCH of multicast service;

the PDSCH of the multicast service has a higher priority than the PDSCH of the broadcast service.
The method according to claim 1 or 2, wherein the PDSCH of the multicast service comprises a multicast dynamically scheduled PDSCH and/or a multicast semi-persistent scheduling, SPS, PDSCH, the priority policy further comprising:

the priority of the PDSCH of the multicast dynamic schedule is higher than the priority of the PDSCH of the multicast SPS.
The method of any of claims 1-3, wherein the PDSCH of the unicast traffic comprises a unicast dynamically scheduled PDSCH and/or a unicast SPS PDSCH, the priority policy further comprising:

The priority of PDSCH of unicast dynamic scheduling is higher than that of PDSCH of unicast SPS.
The method of any of claims 1-4, wherein the priority policy further comprises:

the PDSCH associated with the larger SPS index has a higher priority than the PDSCH associated with the smaller SPS index; or,

the PDSCH associated with the smaller SPS index has a higher priority than the PDSCH associated with the larger SPS index.
The method of any of claims 1-5, wherein the priority policy further comprises:

the priority of the PDSCH associated with the G-RNTI of the larger group-radio network temporary identifier is higher than that of the PDSCH associated with the smaller G-RNTI; or,

the priority of the PDSCH associated with the smaller G-RNTI is higher than that of the PDSCH associated with the larger G-RNTI.
The method of any of claims 1-6, wherein the priority policy further comprises:

the priority of the PDSCH associated with the larger temporary mobile group identity TMGI is higher than the priority of the PDSCH associated with the smaller TMGI; or,

the PDSCH of the smaller TMGI association has a higher priority than the PDSCH of the larger TMGI association.
The method of any of claims 1-6, wherein the priority policy further comprises:

The PDSCH associated with the higher priority is higher in priority than the PDSCH associated with the lower priority.
The method of claim 8, wherein the method further comprises:

the terminal equipment receives first configuration information sent by the network equipment, wherein the first configuration information is used for configuring the priority of TMGI of the multicast service.
The method according to any one of claims 1 to 9, wherein the terminal device receives PDSCH based on priority policy, comprising:

for a plurality of PDSCHs scheduled in the first time slot, the terminal device receives a part of PDSCH in the plurality of PDSCH and discards another part of PDSCH in the plurality of PDSCH, wherein the received part of PDSCH has a higher priority than the discarded part of PDSCH.
The method of any one of claims 1 to 10, wherein the method further comprises:

and the terminal equipment feeds back a negative acknowledgement NACK for the discarded PDSCH to the network equipment, and stops a Discontinuous Reception (DRX) timer associated with the HARQ process identifier corresponding to the discarded PDSCH or waits for the DRX timer to be overtime, wherein the DRX timer comprises a DRX retransmission timer and/or a DRX non-activation timer.
The method of any one of claims 1 to 11, wherein the method further comprises:

the terminal device reports a first capability of the terminal device to a network device, wherein the first capability is used for indicating at least one of the following:

the maximum number of PDSCH of all the services which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of the multicast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of the broadcast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of unicast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of multicast service and broadcast service that the terminal equipment can receive in the same time slot;

the maximum number of PDSCH of multicast service and unicast service which can be received by the terminal equipment in the same time slot;

the terminal device can receive the maximum number of PDSCH of the broadcast service and the unicast service in the same time slot.
A data receiving apparatus applied to a terminal device, the apparatus comprising:

a determining unit, configured to determine the number of PDSCH scheduled in the first slot, where the PDSCH scheduled in the first slot includes at least one of: PDSCH of multicast service, PDSCH of broadcast service, PDSCH of unicast service;

And the receiving unit is used for receiving the PDSCH based on a priority strategy if the number of the scheduled PDSCH is larger than the number of the first capability instructions of the terminal equipment.
The apparatus of claim 13, wherein the priority policy comprises at least one of:

the priority of PDSCH of unicast service is greater than that of PDSCH of multicast service;

the PDSCH of the multicast service has a higher priority than the PDSCH of the broadcast service.
The apparatus of claim 13 or 14, wherein the PDSCH of the multicast service comprises a multicast dynamically scheduled PDSCH and/or a PDSCH of a multicast SPS, the priority policy further comprising:

the priority of the PDSCH of the multicast dynamic schedule is higher than the priority of the PDSCH of the multicast SPS.
The apparatus of any of claims 13 to 15, wherein the PDSCH of the unicast traffic comprises a unicast dynamically scheduled PDSCH and/or a unicast SPS PDSCH, the priority policy further comprising:

the priority of PDSCH of unicast dynamic scheduling is higher than that of PDSCH of unicast SPS.
The apparatus of any of claims 13-16, wherein the priority policy further comprises:

the PDSCH associated with the larger SPS index has a higher priority than the PDSCH associated with the smaller SPS index; or,

The PDSCH associated with the smaller SPS index has a higher priority than the PDSCH associated with the larger SPS index.
The apparatus of any of claims 13 to 17, wherein the priority policy further comprises:

the priority policy further includes:

the priority of the PDSCH associated with the larger G-RNTI is higher than that of the PDSCH associated with the smaller G-RNTI; or,

the priority of the PDSCH associated with the smaller G-RNTI is higher than that of the PDSCH associated with the larger G-RNTI.
The apparatus of any of claims 13-18, wherein the priority policy further comprises:

the PDSCH associated with the larger TMGI is higher in priority than the PDSCH associated with the smaller TMGI; or,

the PDSCH of the smaller TMGI association has a higher priority than the PDSCH of the larger TMGI association.
The apparatus of any of claims 13-18, wherein the priority policy further comprises:

the PDSCH associated with the higher priority is higher in priority than the PDSCH associated with the lower priority.
The apparatus of claim 20, wherein the receiving unit is further configured to receive first configuration information sent by a network device, the first configuration information being used to configure a priority of a TMGI of the multicast service.
The apparatus of any of claims 13-21, wherein the receiving unit is configured to receive a portion of PDSCH of the plurality of PDSCH and discard another portion of PDSCH of the plurality of PDSCH for a plurality of PDSCH scheduled in the first time slot, where a priority of the received portion of PDSCH is higher than a priority of the discarded another portion of PDSCH.
The apparatus according to any one of claims 13 to 22, wherein the apparatus further comprises:

a feedback unit for feeding back NACK for the discarded PDSCH to the network device;

and stopping the Discontinuous Reception (DRX) timer associated with the HARQ process identifier corresponding to the discarded PDSCH or waiting for the DRX timer to be overtime by the terminal equipment, wherein the DRX timer comprises a DRX retransmission timer and/or a DRX inactivity timer.
The apparatus according to any one of claims 13 to 23, wherein the apparatus further comprises:

a reporting unit, configured to report, to a network device, a first capability of the terminal device, where the first capability is used to indicate at least one of:

the maximum number of PDSCH of all the services which can be received by the terminal equipment in the same time slot;

The maximum number of PDSCH of the multicast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of the broadcast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of unicast service which can be received by the terminal equipment in the same time slot;

the maximum number of PDSCH of multicast service and broadcast service that the terminal equipment can receive in the same time slot;

the maximum number of PDSCH of multicast service and unicast service which can be received by the terminal equipment in the same time slot;

the terminal device can receive the maximum number of PDSCH of the broadcast service and the unicast service in the same time slot.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 12.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 12.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 12.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 12.
A computer program which causes a computer to perform the method of any one of claims 1 to 12.