WO2023173341A1

WO2023173341A1 - Methods, devices, and computer readable medium for communication

Info

Publication number: WO2023173341A1
Application number: PCT/CN2022/081279
Authority: WO
Inventors: Fang Xu; Gang Wang
Original assignee: Nec Corporation
Priority date: 2022-03-16
Filing date: 2022-03-16
Publication date: 2023-09-21

Abstract

Embodiments of the present disclosure relate to methods, devices, and computer readable medium for communication. According to embodiments of the present disclosure, a terminal device receives downlink control information (DCI) from a network device. The DCI schedules a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission. The terminal device is a RedCap user equipment. If a processing time for at least one of the PDSCH transmission or the PUSCH transmission is relaxed, the terminal device determines at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission. The at least one time domain parameter satisfies the processing time. In this way, the transmission performed by the reduced capability UE can satisfy the relaxed UE processing time.

Description

METHODS, DEVICES, AND COMPUTER READABLE MEDIUM FOR COMMUNICATION

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices, and computer readable medium for communication.

BACKGROUND

Several technologies have been proposed to improve communication performances. For example, a reduced capability (RedCap) user equipment (UE) has been proposed. The use cases that motivate the specification work on NR RedCap include wearables (e.g. smart watches, wearable medical devices, AR/VR goggles, etc. ) , industrial wireless sensors, and video surveillance. Through the Release-17 NR RedCap work item, third generation project partnership (3GPP) has established a framework for enabling reduced capability NR devices suitable for a range of use cases, including the industrial sensors, video surveillance, and wearables use cases, with requirements on low UE complexity and sometimes also on low UE power consumption. To further expand the market for RedCap use cases with relatively low cost, low energy consumption, and low data rate requirements, e.g., industrial wireless sensor network use cases, some further complexity reduction enhancements should be considered.

SUMMARY

In general, example embodiments of the present disclosure provide a solution for communication.

In a first aspect, there is provided a method for communication. The method comprises receiving, at a terminal device and from a network device, downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission, wherein the terminal device is a reduced processing capability compared with a normal type terminal device; and in accordance with a determination that a processing time for at least one of the PDSCH transmission or the PUSCH transmission is relaxed, determining at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission, wherein the at least one time domain parameter satisfies the processing time.

In a second aspect, there is provided a terminal device. The terminal device comprises a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the terminal device to perform acts comprising: receiving, from a network device, downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission, wherein the terminal device is a reduced processing capability compared with a normal type terminal device; and in accordance with a determination that a processing time for at least one of the PDSCH transmission or the PUSCH transmission is relaxed, determining at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission, wherein the at least one time domain parameter satisfies the processing time.

In a third aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the first aspect.

Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:

Fig. 1 is a schematic diagram of a communication environment in which embodiments of the present disclosure can be implemented;

Fig. 2 illustrates a signaling flow for communications according to some embodiments of the present disclosure;

Figs. 3A and 3B illustrate schematic diagrams of slots according to some embodiments of the present disclosure;

Fig. 4 is a flowchart of an example method in accordance with an embodiment of the present disclosure; and

Fig. 5 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device. In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.

The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.

The terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Terahertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.

The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.

In one embodiment, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

Communications discussed herein may use conform to any suitable standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like. Furthermore, the communications may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.85G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , and the sixth (6G) communication protocols. The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.

As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ” The term “based on” is to be read as “based at least in part on. ” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ” The term “another embodiment” is to be read as “at least one other embodiment. ” The terms “first, ” “second, ” and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.

In some examples, values, procedures, or apparatus are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

As mentioned above, the RedCap UE has been proposed. The capabilities of a RedCap UE compared to those of a normal type UE (i.e., baseline UE) are summarized in Table 1. Bandwidth reduction, reducing the maximum number of multi-input-multi-output (MIMO) layers, and the relaxation of the maximum downlink modulation order all help reduce baseband complexity. Reducing the minimum number of required receive branches and allowing half-duplex (HD) operations in all bands help reduce the bill of material costs in terms of antennas and radio frequency (RF) components.

Table 1

One important objective of 5G is to enable connected industries. 5G connectivity can serve as catalyst for next wave of industrial transformation and digitalization, which improve flexibility, enhance productivity and efficiency, reduce maintenance cost, and improve operational safety. Devices in such environment include e.g. pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc. It is desirable to connect these sensors and actuators to 5G radio access and core networks. The massive industrial wireless sensor network (IWSN) use cases and requirements include not only ultra-reliable low latency communication (URLLC) services with very high requirements, but also relatively low-end services with the requirement of small device form factors, and/or being completely wireless with a battery life of several years. The requirements for these services are higher than lower power wide area (LPWA) (i.e. LTE-MTC/NB-IoT) but lower than URLLC and Enhanced Mobile Broadband (eMBB) .

Similar to connected industries, 5G connectivity can serve as catalyst for the next wave smart city innovations. As an example, TR 22.804 describes smart city use case and requirements for that. The smart city vertical covers data collection and processing to more efficiently monitor and control city resources, and to provide services to city residents. Especially, the deployment of surveillance cameras is an essential part of the smart city but also of factories and industries. Finally, wearables use case includes smart watches, rings, eHealth related devices, and medical monitoring devices etc. One characteristic for the use case is that the device is small in size.

Thus, a RedCap UE may relax UE processing timeline for downlink or uplink transmissions to reduce the device complexity. In this case, the directly associated processing time needs to be specified. Moreover, the indirectly associated processing time needs to be specified.

In order to solve at least part of the above problems or other potential problems, solutions on RedCap timeline are proposed. According to embodiments of the present disclosure, a terminal device receives downlink control information (DCI) from a network device. The DCI schedules a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission. The terminal device is a RedCap user equipment. If a processing time for at least one of the PDSCH transmission or the PUSCH transmission is relaxed, the terminal device determines at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission. The at least one time domain parameter satisfies the processing time. In this way, the transmission performed by the RedCap UE can satisfy the relaxed UE processing time.

Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented. The communication system 100, which is a part of a communication network, comprises a terminal device 110-1, a terminal device 110-2, ..., a terminal device 110-N, which can be collectively referred to as “terminal device (s) 110. ” The number N can be any suitable integer number.

The communication system 100 further comprises a network device. In the communication system 100, the network device 120 and the terminal devices 110 can communicate data and control information to each other. The numbers of terminal devices shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations.

Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.

Embodiments of the present disclosure can be applied to any suitable scenarios. For example, embodiments of the present disclosure can be implemented at reduced capability NR devices. Alternatively, embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.

The term “slot” used herein refers to a dynamic scheduling unit. One slot comprises a predetermined number of symbols. The term “downlink (DL) sub-slot” may refer to a virtual sub-slot constructed based on uplink (UL) sub-slot. The DL sub-slot may comprise fewer symbols than one DL slot. The slot used herein may refer to a normal slot which comprises a predetermined number of symbols and also refer to a sub-slot which comprises fewer symbols than the predetermined number of symbols.

Embodiments of the present disclosure will be described in detail below. Reference is first made to Fig. 2, which shows a signaling chart illustrating process 200 between the terminal device and the network device according to some example embodiments of the present disclosure. Only for the purpose of discussion, the process 200 will be described with reference to Fig. 1. The process 200 may involve the terminal device 110-1and the network device 120 in Fig. 1.

The network device 120 transmits 2010 DCI to the terminal device 110-1 which is a RedCap UE. In some embodiments, the DCI may schedule a PDSCH transmission. Alternatively or in addition, the DCI may schedule a PUSCH transmission. In some embodiments, as shown in Fig. 3A, the terminal device 110-1 may receive the DCI 310-1 which scheduled the PUSCH transmission in the first 3 symbols in the slot 320-1. The DCI decoding may cost 3 symbols and the slot 320-2 may be skipped. If PUSCH preparation time (represented as N2) is doubled, the updated PUSCH scheduling associated with legacy default PUSCH TDRA table (as in Table 4) can be as shown in Table 2.

Table 2

In some embodiments, as shown in Fig. 3B, the terminal device 110-1 may receive the DCI 310-2 which scheduled the PUSCH transmission in the last 3 symbols in the slot 320-1. The DCI decoding may cost 3 symbols. If PUSCH preparation time (represented as N2) is doubled, the updated PUSCH scheduling associated with legacy default PUSCH TDRA table (as in Table 4) can be as shown in Table 3.

Table 3

If a processing time for the PDSCH transmission and/or the PUSCH transmission is relaxed, the terminal device 110-1 determines 2020 at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission. The at least one time domain parameter satisfies the relaxed processing time. The processing time for the PDSCH transmission and/or the PUSCH transmission being relaxed means that the processing time is longer than a processing time associated with a normal type UE (i.e., the baseline UE) . For example, since the terminal device 110-1 is the RedCap UE and has the reduced processing capability, the processing time of the terminal device 110-1 (i.e., the relaxed processing time) may be longer than that of the normal type UE.

In some embodiments, the terminal device 110-1 may determine a time domain resource for the PUSCH transmission based on a first time domain resource allocation (TDRA) table and/or a first subcarrier spacing specific value.

In some embodiments, the first TDRA table may be generated by removing at least one row which does not satisfy the relaxed processing time and insert at least one row with different mapping type which may satisfy the relaxed processing time from a second time domain resource allocation table which is used by the normal type terminal device. Table 4 shows an example of the legacy default TDRA table. In this case, the first TDRA table may be generated by removing the row with j from the TDRA table shown in Table 4 and adding new rows with PUSCH mapping type B in the rows which satisfy the processing timeline, for example, the rows with j+1 or j+2 or j+3. Table 5 shows an example of the updated default TDRA table. Further, the updated default TDRA table supported by a RedCap terminal device may be any suitable form and is not limited to the above example. In this way, the scheduling latency is reduced.

Table 4

Table 5

In some other embodiments, the original TDRA table (as shown in Table 4) may not be changed. In other words, the original TDRA table may be kept. In this case, the terminal device 110-1 may expect the row indexes which satisfy with the relaxed processing timeline.

In some embodiments, the first SCS specific value may be a combination of a second subcarrier spacing specific value and a first increment value, wherein the second subcarrier spacing specific value is used by the normal type terminal device. For example, the updated value j (i.e., the first SCS specific value) =original j (i.e., the second SCS specific value) + delta (i.e., the first increment value) . In some embodiments, the first increment value may be same value for all SCS supported by the terminal device 110-1, for example, for μ=0, 1, 2, delta=1. Alternatively, the first increment value may be different values for different SCS, e.g. for μ=0, delta=1, for μ=1, 2, delta=2. In this case, the first SCS specific value may be used in all the rows of the TDRA table (as shown in Table 4) to determine the exact K2 value. Table 6 shows an example of the second SCS value (represented as j) .

Table 6

μ _PUSCH	j
0	1
1	1
2	2

3

Alternatively, the first SCS specific value may be the second subcarrier spacing specific value multiplying a first scaling factor. For example, the updated value j may be ceil (original j *scaling factor) . This scaling factor may be predefined or configured by RRC parameters.

In some embodiments, the terminal device 110-1 may determine a first slot offset (represented as K0) between the DCI and the PDSCH transmission. In some embodiments, the first slot offset may be in a range from a first number of slots to a first maximum number of slots. The first number may not be smaller than 1. The first maximum number may be not lager than 32. For example, the value range of K0 may be INTEGER (X .. 32) and X is not smaller than 1. Alternatively, the first slot offset may be in a range from a second number of slots to a third number of slots. The second number may not be smaller than 1 and the third number may not be greater than 16. For example, the value range of K0 may be INTEGER (X .. P) . In this case, X may not smaller than 1 and P may not be greater than 16.

In some other embodiments, the terminal device 110-1 may determine a second slot offset (represented as K1) between the PDSCH transmission and a slot carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) of the PDSCH transmission. In some embodiments, the second slot offset may be in a range from a fourth number of slots value to a second maximum number of slots. In this case, the fourth number may not be smaller than 1. The second maximum number may not be larger than 15. For example, the value range of K1 may be INTEGER (Y .. 15) and Y is not smaller than 1.

Alternatively or in addition, the terminal device 110-1 may determine a third slot offset (represented as K2) between the DCI and the PUSCH transmission. In some embodiments, the third slot offset may be in a range from a first number of slots to the first maximum number of slots, and the first number is not smaller than 1. The first maximum number may be not larger than 32. For example, the value range of K2 may be INTEGER (Z .. 32) and Z is not smaller than 1. Alternatively, the third slot offset may be in a range from a fifth number of slots to a sixth number of slots. In this case, the fifth number may not be smaller than 1 and the sixth number may not be greater than 16. For example, the value range of K2 may be INTEGER (Z .. Q) . In this case, Z may not smaller than and Q may not be greater than 16.

In other embodiments, the terminal device 110-1 may determine a value range of a PDSCH-to-HARQ timing indicator field. In some embodiments, the value range of a PDSCH-to-HARQ timing indicator field may be from an eighth value to a third maximum value. In this case, the eighth value may not be smaller than 2. The third maximum value may not be larger than 8. For example, the value range may be set to INTEGER (X.. 8) and X>=2. Alternatively, the value range of the PDSCH-to-HARQ timing indicator field may be a constant, for example, the constant is 7. In this case, the value range may be from a ninth value to a tenth value. The ninth value may not be smaller than 2, and the tenth value may be the ninth value plus the constant.

In some embodiments, the DCI may provide a semi-persistent scheduling (SPS) PDSCH release. For example, the terminal device 110-1 may be expected to provide HARQ-ACK information in response to a SPS PDSCH release after N symbols from the last symbol of a PDCCH providing the SPS PDSCH release. For PDSCH processing capability 1, N=10 for μ=0, N=12 for μ=1, N=22 for μ=2, and N=25 for μ=3, where μ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH providing the SPS PDSCH release and the SCS configuration of a PUCCH carrying the HARQ-ACK information in response to a SPS PDSCH release. For reduced capability UEs, if the UE processing timeline for PDSCH is relaxed, the symbol N needs to be modified accordingly. For example, the terminal device 110-1 may transmit, to the network device 120, HARQ-ACK information of the PDSCH transmission, after a first number of symbols from a last symbol of the DCI. In this case, in some embodiments, the first number of symbols may be a combination of a second number of symbols and a first offset number of symbols. The second number of symbols may be used by the normal type terminal device. For example, the relaxed symbol N (i.e., the first number of symbols) may be original N of processing capability 1 (i.e., the second number of symbols) plus delta (i.e., the first offset number of symbols) . In some embodiments, the first offset number of symbols may be predefined. Alternatively, the first offset number of symbols may be configured by RRC parameters.

In some embodiments, the first number of symbols may be the second number of symbols multiplying a second scaling factor. For example, the relaxed symbol N may be ceil (original N of processing capability 1 *scaling factor) . In this case, this scaling factor may be predefined or configured by RRC parameters, then the relaxed symbol N may be updated for the RedCap UE.

Alternatively, the first number of symbols may be a combination of the third number of symbols multiplying a third scaling factor and a second offset number of symbols. The third number of symbols may be PDSCH processing time of the normal type terminal device. For example, for each SCS, relaxed symbol N may be ceil (PDSCH processing time of capability 1*scaling factor) + delta. This scaling factor may be predefined or configured by RRC parameters. The delta can be a relax factor, e.g. delta < 4 for μ=0/1, and delta <10 for μ=2/3.

In some embodiments, the terminal device 110-1 may determine one or more of: a first time duration for PDSCH processing, a third time duration for PUSCH preparation, or a fifth time duration for HARQ-ACK multiplexing. The terminal device 110-1 may apply at least one of: the first time duration for PDSCH processing, the third time duration for PUSCH preparation, or the fifth time duration for HARQ-ACK multiplexing from initial access phase.

In some embodiments, the first time duration for PDSCH processing may be a second time duration for PDSCH processing (represented as N1) scaled by a fourth scaling factor. The second time duration for PDSCH processing can be used by the normal type terminal device. Alternatively or in addition, the third time duration for PUSCH preparation may be a fourth time duration for PUSCH preparation (represented as N2) scaled by a fifth scaling factor. The fourth time duration for PUSCH preparation may be used by the normal type terminal device. In some other embodiments, the fifth time duration for HARQ-ACK multiplexing may be a sixth time duration for the first PUCCH resource (represented as N3) scaled by a sixth scaling factor. The sixth time duration for the first PUCCH resource may be used by the normal type terminal device. In other words the processing timeline N1, N2, N3 of processing capability 1 may be directly scaled by a factor, e.g. 2 or 1.5, and all reduced capability UEs and network follow this relaxed processing timeline as a default, and for the reduced capability UEs in release 18, only support the extended processing timeline. Table 7 shows examples of N1. Table 8 shows examples of N2. Table 9shows examples of N3.

Table 7

Table 8

	PUSCH preparation time N ₂ [symbols]
0	10
1	12
2	23
3	36

Table 9

	HARQ-ACK multiplexing timeline N ₃ [symbols]
0	8
1	10
2	17
3	20

In some embodiments, after receiving a UE dedicated RRC parameters from the network device 120, the terminal device 110-1 may apply one or more of: the first time duration for PDSCH processing, the third time duration for PUSCH preparation, or the fifth time duration for HARQ-ACK multiplexing. For example, before the terminal device 110-1 receives the dedicated serving cell parameter, the default processing timeline may be processing capability 1. After receive RRC layer UE specific parameters, the processing capability is changed to RedCap specific relaxed capability. If the terminal device 110-1 does not receive the indicator, the terminal device 110-1 may keep processing capability 1 as a default.

In some embodiments, the terminal 110-1 may determine a first hardware processing time. In some embodiments, the first hardware processing time may a second hardware processing time scaled by a seventh scaling factor. The second hardware processing time may be used by the normal type terminal device. For example, the updated Z _μ (i.e., the first hardware processing time) may be ceil (original Z _μ *scaling factor) . This scaling factor may be predefined or configured by RRC parameters. Alternatively, the first hardware processing time may be a combination of the second hardware processing time and a second increment value. For example, the updated Z _μ (i.e., the first hardware processing time) may be original Z _μ (i.e., the second hardware processing time) plus delta (i.e., the second increment value) . This delta may be predefined or configured by RRC parameters. In 3GPP TS 38.214, there may be a definition of Zμ for hardware processing time with 'Minimum scheduling offset’ : when the DCI format 0_1 or 1_1 with 'Minimum applicable scheduling offset indicator' field indicating a change to the applied K0min or K _2min is contained within the first three symbols of slot n, the value of application delay X is determined by,

where K _0minOld is the currently applied K _0min value of the active DL BWP in the scheduled cell and is zero, if minimumSchedulingOffsetK0 is not configured for the active DL BWP in the scheduled cell, Z _μ is determined by the subcarrier spacing of the active DL BWP in the scheduling cell in slot n, and given in Table 9, and μ _PDCCH and μ _PDSCH are the sub-carrier spacing configurations for PDCCH of the active DL BWP in the scheduling cell and PDSCH of the active DL BWP in the scheduled cell, respectively, in slot n. When the DCI format 0_1 or 1_1 with 'Minimum applicable scheduling offset indicator' field is received outside the first three symbols of the slot, value of Z _μ from Table 10 is incremented by one before determining the application delay X. Table 9 below shows examples of second hardware processing time Z _μ.

Table 10

μ	Z _μ
0	1

1	1
2	2
3	2

Alternatively or in addition, the terminal device 110-1 may determine a value range of a HARQ feedback timing indicator field. In some embodiments, the value range of a HARQ feedback timing indicator field may be from an eleventh value to a third maximum value. The eleventh value may not be smaller than 2 and third maximum value may be 8. For example, the value range of default may be set to INTEGER (X.. 8) , here, X>=2. Alternatively, the value range of the HARQ feedback timing indicator field may be a constant, for example, the constant is 7. In this case, the value range of the HARQ feedback timing indicator field may from a twelfth value to a thirteenth value. The twelfth value may not be smaller than 2, and the thirteenth value may be the twelfth value plus the constant.

In some embodiments, the terminal device 110-1 may determine a first time duration for PDSCH corresponding to system information radio network temporary identifier (SI-RNTI) . For example, in 3GPP TS 38.214, there is a timeline for PDSCH corresponding to SI-RNTI : in a given scheduled cell, for any PDSCH corresponding to SI-RNTI, the terminal device 110-1 may not be expected to decode a re-transmission of an earlier PDSCH with a starting symbol less than N symbols after the last symbol of that PDSCH, where the value of N depends on the PDSCH subcarrier spacing configuration μ, with N=13 for μ=0, N=13 for μ=1, N=20 for μ=2, and N=24 for μ=3. For reduced capability UEs, if the UE processing timeline for PUSCH/PDSCH is relaxed, the timeline of PDSCH corresponding to SI-RNTI needs to be updated accordingly. For example, in some embodiments, the first time duration for PDSCH corresponding to SI-RNTI may be a second time duration for PDSCH corresponding to SI-RNTI scaled by an eighth scaling factor. The second time duration for PDSCH corresponding to SI-RNTI may be used by the normal type terminal device. For example, the updated N (i.e., the first time duration for PDSCH corresponding to SI-RNTI) may be ceil (original N (i.e., the second time duration) *a scaling factor) . This scaling factor (i.e., the eighth scaling factor) may be predefined or configured by RRC parameters. Alternatively, the first time duration for PDSCH corresponding to SI-RNTI may be a combination of the second time duration for PDSCH corresponding to SI-RNTI plus a third increment value. For example, the updated N may be original N plus delta (i.e., the third increment value) . This third increment value may be predefined or configured by RRC parameters.

In some embodiments, after receiving a UE dedicated RRC parameters from the network device 120, the terminal device 110-1 may apply the first time duration for PDSCH corresponding to SI-RNTI. In some embodiments, before the terminal device 110-1 receives the serving cell specific parameter, the default processing timeline may be processing capability 1.

Alternatively or in addition, the terminal device 110-1 may determine a first time duration for SPS PDSCH cancelation. In 3GPP TS 38.214, there may be a timeline for SPS PDSCH cancelation: the terminal device 110-1 may not be expected to decode a PDSCH in a serving cell scheduled by a PDCCH and one or multiple PDSCH (s) required to be received in the same serving cell without a corresponding PDCCH transmission if the PDSCHs partially or fully overlap in time except if the PDCCH scheduling the PDSCH ends at least 14 symbols before the earliest starting symbol of the PDSCH (s) without the corresponding PDCCH transmission, where the symbol duration is based on the smallest numerology between the scheduling PDCCH and the PDSCH, in which case the UE shall decode the PDSCH scheduled by the PDCCH. For reduced capability UEs, if the UE processing timeline for PUSCH/PDSCH is relaxed, the timeline of SPS PDSCH cancelation needs to be updated accordingly. In some embodiments, the first time duration for SPS PDSCH cancelation may be a second time duration for SPS PDSCH cancelation scaled by a ninth scaling factor. The second time duration for SPS PDSCH cancelation may be used by the normal type terminal device. For example, the updated N (i.e., the first time duration for SPS PDSCH cancelation) may be ceil (14 symbols*scaling factor) . This scaling factor may be predefined or configured by RRC parameters.

In some embodiments, the first time duration for SPS PDSCH cancelation may be a combination of the second time duration for SPS PDSCH cancelation and a fourth increment value. For example, the updated N may be 14 symbols plus delta (i.e., fourth increment value) . The fourth increment value may be predefined or configured by RRC parameters. Alternatively, the first time duration for SPS PDSCH cancelation may be the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device. For example, the updated N may be PDSCH relaxed processing time of the largest SCS supported by reduced capability UEs with relaxed processing time, e.g. the largest SCS is 30 KHz in FR1, it considers the worst case of decoding time and can reduce the latency. In some other embodiments, the first time duration for SPS PDSCH cancelation may be a combination of the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device and a first decrement value. For example, the updated N may be PDSCH processing time of the largest SCS supported by reduced capability UEs with relaxed processing time –delta (i.e., the first decrement value) , e.g. the largest SCS is 30 KHz in FR1, and delta is less than 10.

In some embodiments, the terminal device 110-1 may determine a first search space set group (SSSG) switching time. In 3GPP TS 38.213, there may be a timeline for SSSG switching: the terminal device 110-1 can be provided by searchSpaceSwitchDelay a number of symbols P _switch where a minimum value of P _switch is provided in Table 11 for UE processing capability 1 and UE processing capability 2 and SCS configuration μ. UE processing capability 1 for SCS configuration μ applies unless the UE indicates support for UE processing capability 2. In some embodiments, the first SSSG switching time may be a second SSSG switching time scaled by a tenth scaling factor. The second SSSG switching time may be used by the normal type terminal device. For example, the updated P _switch (i.e., the first SSSG switching time) may be ceil (original P _switch (i.e., the second SSSG switching time) *scaling factor) . This scaling factor (i.e., the tenth scaling factor) may be predefined or configured by RRC parameters. Alternatively, the first SSSG switching time may be a combination of the second SSSG switching time and a fifth increment value. For example, the updated P _switch may be original P _switch plus delta. This delta value (i.e., the fifth increment value) may be predefined or configured by RRC parameters. In some other embodiments, the first SSSG switching time may be a relaxed SPS PDSCH release time duration corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device. For example, the updated P _switch may be relaxed SPS PDSCH release timeline of largest SCS supported by reduced capability UE, e.g. the largest SCS is 30 KHz in FR1, it considers the worst case of switching time, and can reduce the search space set switch latency.

Table 11

It should be noted that in some embodiments, above mentioned scaling factors may have same values. Alternatively, in some embodiments, at least part of the above mentioned scaling factors may have different values.

Fig. 4 shows a flowchart of an example method 400 in accordance with an embodiment of the present disclosure. The method 400 can be implemented at any suitable devices. Only for the purpose of illustrations, the method 400 can be implemented at a terminal device 110-1 as shown in Fig. 1.

At block 410, the terminal device 110-1 receives DCI from the network device 120. The terminal device 110-1 which is a RedCap UE. In some embodiments, the DCI may schedule a PDSCH transmission. Alternatively or in addition, the DCI may schedule a PUSCH transmission.

At block 420, if a processing time for the PDSCH transmission and/or the PUSCH transmission is relaxed, the terminal device 110-1 determines at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission. The at least one time domain parameter satisfies the processing time. The processing time for the PDSCH transmission and/or the PUSCH transmission being relaxed means that the processing time is longer than a processing time associated with a normal type UE (i.e., the baseline UE) .

In some embodiments, the terminal device 110-1 may determine a time domain resource for the PUSCH transmission based on a first TDRA table and/or a first subcarrier spacing specific value. In some embodiments, the first TDRA table may be generated by removing at least one row which does not satisfy the relaxed processing time and insert at least one row with different mapping type which may satisfy the relaxed processing time from a second time domain resource allocation table which is used by the normal type terminal device. In this case, the first TDRA table may be generated by removing the row with j from the TDRA table shown in Table 4 and adding new row with PUSCH mapping type B in the rows which satisfy the processing timeline, for example, the rows with j+1 or j+2 or j+3. In this way, the latency is reduced.

In some other embodiments, the original TDRA table may not be changed. In other words, the original TDRA table may be kept. In this case, the terminal device 110-1 may expect the row indexes which satisfy with the relaxed processing timeline.

In some embodiments, the first SCS specific value may be a combination of a second subcarrier spacing specific value and a first increment value, wherein the second subcarrier spacing specific value is used by the normal type terminal device. For example, the updated value j (i.e., the first SCS specific value) =original j (i.e., the second SCS specific value) + delta (i.e., the first increment value) . In some embodiments, the first increment value may be same value for all SCS supported by the terminal device 110-1, for example, for μ=0, 1, 2, delta=1. Alternatively, the first increment value may be different values for different SCS, e.g. for μ=0, delta=1, for μ=1, 2, delta=2. In this case, the first SCS specific value may be used in all the rows of the TDRA table to determine the exact K2 value.

In some embodiments, the terminal device 110-1 may determine a first slot offset (represented as K0) between the DCI and the PDSCH transmission. In some embodiments, the first slot offset may be in a range from a first number of slots to the first maximum number of slots. The first number may not be smaller than 1. The first maximum number may be 32. For example, the value range of K0 may be INTEGER (X .. 32) and X is not smaller than 1. Alternatively, the first slot offset may be in a range from a second number of slots to a third number of slots. The second number may not be smaller than 1 and the third number may not be greater than 16. For example, the value range of K0 may be INTEGER (X .. P) . In this case, X may not smaller than and P may not be greater than 16.

In some other embodiments, the terminal device 110-1 may determine a second slot offset (represented as K1) between the PDSCH transmission and a slot carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) of the PDSCH transmission. In some embodiments, the second slot offset may be in a range from a fourth number of slots value to the second maximum number of slots. In this case, the fourth number may not be smaller than 1. The second maximum number may not be larger than 15. For example, the value range of K1 may be INTEGER (Y .. 15) and Y is not smaller than 1.

Alternatively or in addition, the terminal device 110-1 may determine a third slot offset (represented as K2) between the DCI and the PUSCH transmission. In some embodiments, the third slot offset may be in a range from a first number of slots to the first maximum number of slots, and the first number is not smaller than 1. The first maximum number may be 32. For example, the value range of K2 may be INTEGER (Z .. 32) and Z is not smaller than 1. Alternatively, the third slot offset may be in a range from a fifth number of slots to a sixth number of slots. In this case, the fifth number may not be smaller than 1 and the sixth number may not be greater than 16. For example, the value range of K2 may be INTEGER (Z .. Q) . In this case, Z may not smaller than and Q may not be greater than 16.

In other embodiments, the terminal device 110-1 may determine a value range of a PDSCH-to-HARQ timing indicator field. In some embodiments, the value range of a PDSCH-to-HARQ timing indicator field may be from an eighth value to a third maximum value. In this case, the eighth value may not be smaller than 2 and the third maximum value may be 8. For example, the value range may be set to INTEGER (X.. 8) and X>=2. Alternatively, the value range of the PDSCH-to-HARQ timing indicator field may be a constant, for example, the constant is 7. In this case, the value range may be from a ninth value to a tenth value. The ninth value may not be smaller than 2, and the tenth value may be the ninth value plus the constant.

Alternatively, the first number of symbols may be a combination of the third number of symbols multiplying a third scaling factor and a second offset number of symbols. The third number of symbols may be PDSCH processing time of the normal type terminal device. For example, for each SCS, relaxed symbol N may be ceil (PDSCH processing time of capability 1*scaling factor) plus delta. This scaling factor may be predefined or configured by RRC parameters. The delta can be a relax factor, e.g. delta < 4 for μ=0/1, and delta <10 for μ=2/3.

In some embodiments, the first time duration for PDSCH processing may be a second time duration for PDSCH processing (represented as N1) scaled by a fourth scaling factor. The second timer duration for PDSCH processing can be used by the normal type terminal device. Alternatively or in addition, the third time duration for PUSCH preparation may be a fourth time duration for PUSCH preparation (represented as N2) scaled by a fifth scaling factor. The fourth time duration for PUSCH preparation is used by the normal type terminal device. In some other embodiments, the fifth time duration for HARQ-ACK multiplexing may be a sixth time duration for the first PUCCH resource (represented as N3) scaled by a sixth scaling factor. The sixth time duration for the first PUCCH resource may be used by the normal type terminal device. In other words the processing timeline N1, N2, N3 of processing capability 1 may be directly scaled by a factor, e.g. 2 or 1.5, and all reduced capability UEs and network follow this relaxed processing timeline as a default, and for the reduced capability UEs, only support the extended processing timeline.

In some embodiments, the terminal 110-1 may determine a first hardware processing time. In some embodiments, the first hardware processing time may a second hardware processing time scaled by a seventh scaling factor. The second hardware processing time may be used by the normal type terminal device. For example, the updated Z _μ (i.e., the first hardware processing time) may be ceil (original Z _μ *scaling factor) . This scaling factor may be predefined or configured by RRC parameters. Alternatively, the first hardware processing time may be a combination of the second hardware processing time and a second increment value. For example, the updated Z _μ (i.e., the first hardware processing time) may be original Z _μ (i.e., the second hardware processing time) plus delta (i.e., the second increment value) . This delta may be predefined or configured by RRC parameters.

Alternatively or in addition, the terminal device 110-1 may determine a value range of a HARQ feedback timing indicator field. In some embodiments, the value range of a HARQ feedback timing indicator field may be from an eleventh value to a third maximum value. The eleventh value may not be smaller than 2 and the third maximum value may be 8. For example, the value range of default may be set to INTEGER (X.. 8) , here, X>=2. Alternatively, the value range of the HARQ feedback timing indicator field may be a constant, for example, the constant is 7. In this case, the value range of the HARQ feedback timing indicator field may from a twelfth value to a thirteenth value. The twelfth value may not be smaller than 2, and the thirteenth value may be the twelfth value plus the constant.

In some embodiments, the first time duration for SPS PDSCH cancelation may be a combination of the second time duration for SPS PDSCH cancelation and a fourth increment value. For example, the updated N may be 14 symbols plus delta (i.e., fourth increment value) . The fourth increment value may be predefined or configured by RRC parameters. Alternatively, the first time duration for SPS PDSCH cancelation may be the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device. For example, the updated N may be PDSCH relaxed processing time of the largest SCS supported by reduced capability UEs with relaxed processing time, e.g. the largest SCS is 30 KHz in FR1, it considers the worst case of decoding time and can reduce the latency. In some other embodiments, the first time duration for SPS PDSCH cancelation may be a combination of the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device and a first decrement value. For example, the updated N may be PDSCH processing time of the largest SCS supported by reduced capability UEs with relaxed processing time minus delta (i.e., the first decrement value) , e.g. the largest SCS is 30 KHz in FR1, and delta is less than 10.

In some embodiments, the terminal device 110-1 may determine a first search space set group (SSSG) switching time. In some embodiments, the first SSSG switching time may be a second SSSG switching time scaled by a tenth scaling factor. The second SSSG switching time may be used by the normal type terminal device. For example, the updated P _switch (i.e., the first SSSG switching time) may be ceil (original P _switch (i.e., the second SSSG switching time) *scaling factor) . This scaling factor (i.e., the tenth scaling factor) may be predefined or configured by RRC parameters. Alternatively, the first SSSG switching time may be a combination of the second SSSG switching time and a fifth increment value. For example, the updated P _switch may be original P _switch plus delta. This delta value (i.e., the fifth increment value) may be predefined or configured by RRC parameters. In some other embodiments, the first SSSG switching time may be a relaxed SPS PDSCH release time duration corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device. For example, the updated P _switch may be relaxed SPS PDSCH release timeline of largest SCS supported by reduced capability UE, e.g. the largest SCS is 30 KHz in FR1, it considers the worst case of switching time, and can reduce the latency.

In some embodiments, a terminal device comprises circuitry configured to perform receiving, at a terminal device and from a network device, downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission, wherein the terminal device is a reduced processing capability compared with a normal type terminal device; and in accordance with a determination that a processing time for at least one of the PDSCH transmission or the PUSCH transmission is relaxed, determining at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission, wherein the at least one time domain parameter satisfies the processing time.

In some embodiments, the DCI schedules the PUSCH transmission. In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a time domain resource for the PUSCH transmission based on a first time domain resource allocation table or a first subcarrier spacing specific value. In some embodiments, the first time domain resource allocation table is generated by removing at least one row which does not satisfy the relaxed processing time and insert at least one row with different mapping type which may satisfy the relaxed processing time from a second time domain resource allocation table which is used by the normal type terminal device. In some embodiments, the first subcarrier spacing specific value is one of: a combination of a second subcarrier spacing specific value and a first increment value, wherein the second subcarrier spacing specific value is used by the normal type terminal device, or the second subcarrier spacing specific value multiplying a first scaling factor.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a first slot offset between the DCI and the PDSCH transmission. In some embodiments, the first slot offset between the DCI and the PDSCH transmission is in a range from a first number of slots to a first maximum number of slots, and the first number is not smaller than 1 and the first maximum number is 32. In some embodiments, the first slot offset is in a range from a second number of slots to a third number of slots, the second number is not smaller than 1, and the third number is not greater than 16.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a second slot offset between the PDSCH transmission and a slot carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) of the PDSCH transmission. In some embodiments, the second slot offset between the PDSCH transmission and a slot carrying the HARQ-ACK of the PDSCH transmission is in a range from a fourth number of slots value to a second maximum number of slots, and the fourth number is not smaller than 1 and the second maximum number is 15.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a third slot offset between the DCI and the PUSCH transmission is in a range from a first number of slots to a first maximum number of slots, and the first number is not smaller than 1 and the first maximum number is 32. In some embodiments, the third slot offset is in a range from a fifth number of slots to a sixth number of slots, the fifth number is not smaller than 1, and the sixth number is not greater than 16.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a value range of a PDSCH-to-HARQ timing indicator field. In some embodiments, the value range of a PDSCH-to-HARQ timing indicator field is from an eighth value to a third maximum value, and the eighth value is not smaller than 2 and the third maximum value is 8. In some embodiments, the value range of the PDSCH-to-HARQ timing indicator field is a constant, and from a ninth value to a tenth value, the ninth value is not smaller than 2, and the tenth value is the ninth value plus the constant.

In some embodiments, the DCI provides a semi-persistent scheduling (SPS) PDSCH release. In some embodiments, the terminal device comprises circuitry configured to perform transmitting, to the network device, HARQ-ACK information of the PDSCH transmission, after a first number of symbols from a last symbol of the DCI. In some embodiments, the first number of symbols is one of: a combination of a second number of symbols and a first offset number of symbols, wherein the second number of symbols is used by the normal type terminal device, the second number of symbols multiplying a second scaling factor, or a combination of the third number of symbols multiplying a third scaling factor and a second offset number of symbols, wherein the third number of symbols is PDSCH processing time of the normal type terminal device.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining at least one of: a first time duration for PDSCH processing, a third time duration for PUSCH preparation, or a fifth time duration for HARQ-ACK multiplexing. In some embodiments, the first time duration for PDSCH processing is a second time duration for PDSCH processing scaled by a fourth scaling factor, and the second timer duration for PDSCH processing is used by the normal type terminal device, the third time duration for PUSCH preparation is a fourth time duration for PUSCH preparation scaled by a fifth scaling factor, and the fourth timer duration for PDSCH processing is used by the normal type terminal device, or the fifth time duration for HARQ-ACK multiplexing is a sixth time duration for PUSCH preparation scaled by a sixth scaling factor, and the sixth timer duration for PDSCH processing is used by the normal type terminal device.

In some embodiments, the terminal device comprises circuitry configured to perform applying at least one of: the first time duration for PDSCH processing, the third time duration for PUSCH preparation, or the fifth time duration for HARQ-ACK multiplexing from initial access phase.

In some embodiments, the terminal device comprises circuitry configured to perform after receiving a UE dedicated RRC parameters from the network device, applying at least one of: the first time duration for PDSCH processing, the third time duration for PUSCH preparation, or the fifth time duration for HARQ-ACK multiplexing.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a first hardware processing time. In some embodiments, the first hardware processing time is a second hardware processing time scaled by a seventh scaling factor, and the second hardware processing time is used by the normal type terminal device. In some embodiments, the first hardware processing time is a combination of the second hardware processing time and a second increment value.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a value range of a HARQ feedback timing indicator field. In some embodiments, the value range of a HARQ feedback timing indicator field is from an eleventh value to a third maximum value, and the eleventh value is not smaller than 2 and the third maximum value is 8. In some embodiments, the value range of the HARQ feedback timing indicator field is a constant, and from a twelfth value to a thirteenth value, the twelfth value is not smaller than 2, and the thirteenth value is the twelfth value plus the constant.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a first time duration for PDSCH corresponding to system information radio network temporary identifier (SI-RNTI) . In some embodiments, the first time duration for PDSCH corresponding to SI-RNTI is a second time duration for PDSCH corresponding to SI-RNTI scaled by an eighth scaling factor, and the second time duration for PDSCH corresponding to SI-RNTI is used by the normal type terminal device. In some embodiments, the first time duration for PDSCH corresponding to SI-RNTI is a combination of the second time duration for PDSCH corresponding to SI-RNTI plus a third increment value.

In some embodiments, the terminal device comprises circuitry configured to perform after receiving a UE dedicated RRC parameters from the network device, applying the first time duration for PDSCH corresponding to SI-RNTI.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by: determining a first time duration for SPS PDSCH cancelation. In some embodiments, the first time duration for SPS PDSCH cancelation is a second time duration for SPS PDSCH cancelation scaled by a ninth scaling factor, and the second time duration for SPS PDSCH cancelation is used by the normal type terminal device. In some embodiments, the first time duration for SPS PDSCH cancelation is a combination of the second time duration for SPS PDSCH cancelation and a fourth increment value. In some embodiments, the first time duration for SPS PDSCH cancelation is the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device. In some embodiments, the first time duration for SPS PDSCH cancelation is a combination of the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device and a first decrement value.

In some embodiments, the terminal device comprises circuitry configured to perform determining the at least one time domain parameter by determining a first search space set group (SSSG) switching time. In some embodiments, the first SSSG switching time is a second SSSG switching time scaled by a tenth scaling factor, and the second SSSG switching time is used by the normal type terminal device. In some embodiments, the first SSSG switching time is a combination of the second SSSG switching time and a fifth increment value. In some embodiments, the first SSSG switching time is a relaxed SPS PDSCH release time duration corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device.

Fig. 5 is a simplified block diagram of a device 500 that is suitable for implementing embodiments of the present disclosure. The device 500 can be considered as a further example implementation of the terminal device 110-1 or the network device 120 as shown in Fig. 1. Accordingly, the device 500 can be implemented at or as at least a part of the terminal device 110-1 or the network device 120.

As shown, the device 500 includes a processor 510, a memory 520 coupled to the processor 510, a suitable transmitter (TX) and receiver (RX) 540 coupled to the processor 510, and a communication interface coupled to the TX/RX 540. The memory 520 stores at least a part of a program 530. The TX/RX 540 is for bidirectional communications. The TX/RX 540 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.

The program 530 is assumed to include program instructions that, when executed by the associated processor 510, enable the device 500 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Fig. 2 to 4. The embodiments herein may be implemented by computer software executable by the processor 510 of the device 500, or by hardware, or by a combination of software and hardware. The processor 510 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 510 and memory 520 may form processing means 550 adapted to implement various embodiments of the present disclosure.

The memory 520 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 520 is shown in the device 1200, there may be several physically distinct memory modules in the device 500. The processor 510 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 500 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to Figs. 2 to 4. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.

The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.

The terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connections with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.

The network device may have the function of network energy saving, Self-Organising Networks (SON) /Minimization of Drive Tests (MDT) . The terminal may have the function of power saving.

The embodiments of the present disclosure may be performed in test equipment, e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.

The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

Claims

A communication method, comprising:

receiving, at a terminal device and from a network device, downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) transmission or a physical uplink shared channel (PUSCH) transmission, wherein the terminal device is a reduced processing capability compared with a normal type terminal device; and

in accordance with a determination that a processing time for at least one of the PDSCH transmission or the PUSCH transmission is relaxed, determining at least one time domain parameter associated with the PDSCH transmission or the PUSCH transmission, wherein the at least one time domain parameter satisfies the processing time.
The method of claim 1, wherein the DCI schedules the PUSCH transmission, and

wherein determining the at least one time domain parameter comprises:

determining a time domain resource for the PUSCH transmission based on a first time domain resource allocation table or a first subcarrier spacing specific value, and

wherein the first time domain resource allocation table is generated by removing at least one row which does not satisfy the relaxed processing time and inserting at least one row with different mapping type which satisfies the relaxed processing time from a second time domain resource allocation table which is used by the normal type terminal device;

wherein the first subcarrier spacing specific value is one of:

a combination of a second subcarrier spacing specific value and a first increment value, wherein the second subcarrier spacing specific value is used by the normal type terminal device, or

the second subcarrier spacing specific value multiplying a first scaling factor.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a first slot offset between the DCI and the PDSCH transmission; and

wherein the first slot offset between the DCI and the PDSCH transmission is in a range from a first number of slots to a first maximum number of slots, the first number is not smaller than 1 and the first maximum number is 32, or

wherein the first slot offset is in a range from a second number of slots to a third number of slots, the second number is not smaller than 1, and the third number is not greater than 16.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a second slot offset between the PDSCH transmission and a slot carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) of the PDSCH transmission; and

wherein the second slot offset between the PDSCH transmission and a slot carrying the HARQ-ACK of the PDSCH transmission is in a range from a fourth number of slots value to a second maximum number of slots, the fourth number is not smaller than 1, and the second maximum number is 15.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a third slot offset between the DCI and the PUSCH transmission is in a range from a first number of slots to a first maximum number of slots, the first number is not smaller than 1 and the first maximum number is 32, or

wherein the third slot offset is in a range from a fifth number of slots to a sixth number of slots, the fifth number is not smaller than 1, and the sixth number is not greater than 16.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a value range of a PDSCH-to-HARQ timing indicator field; and

wherein the value range of a PDSCH-to-HARQ timing indicator field is from an eighth value to a third maximum value, the eighth value is not smaller than 2, and the third maximum value is 8, or

wherein the value range of the PDSCH-to-HARQ timing indicator field is a constant, and from a ninth value to a tenth value, the ninth value is not smaller than 2, and the tenth value is the ninth value plus the constant.
The method of claim 1, wherein the DCI provides a semi-persistent scheduling (SPS) PDSCH release, and

wherein the method further comprises:

transmitting, to the network device, HARQ-ACK information of the PDSCH transmission, after a first number of symbols from a last symbol of the DCI, and

wherein the first number of symbols is one of:

a combination of a second number of symbols and a first offset number of symbols, wherein the second number of symbols is used by the normal type terminal device,

the second number of symbols multiplying a second scaling factor, or

a combination of the third number of symbols multiplying a third scaling factor and a second offset number of symbols, wherein the third number of symbols is PDSCH processing time of the normal type terminal device.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining at least one of: a first time duration for PDSCH processing, a third time duration for PUSCH preparation, or a fifth time duration for HARQ-ACK multiplexing; and

wherein the first time duration for PDSCH processing is a second time duration for PDSCH processing scaled by a fourth scaling factor, and the second timer duration for PDSCH processing is used by the normal type terminal device,

the third time duration for PUSCH preparation is a fourth time duration for PUSCH preparation scaled by a fifth scaling factor, and the fourth timer duration for PDSCH processing is used by the normal type terminal device, or

the fifth time duration for HARQ-ACK multiplexing is a sixth time duration for PUSCH preparation scaled by a sixth scaling factor, and the sixth timer duration for PDSCH processing is used by the normal type terminal device.

applying at least one of: the first time duration for PDSCH processing, the third time duration for PUSCH preparation, or the fifth time duration for HARQ-ACK multiplexing from initial access phase.
The method of claim 8, further comprising:

after receiving a UE dedicated RRC parameters from the network device, applying at least one of: the first time duration for PDSCH processing, the third time duration for PUSCH preparation, or the fifth time duration for HARQ-ACK multiplexing.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a first hardware processing time; and

wherein the first hardware processing time is a second hardware processing time scaled by a seventh scaling factor, and the second hardware processing time is used by the normal type terminal device, or

wherein the first hardware processing time is a combination of the second hardware processing time and a second increment value.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a value range of a HARQ feedback timing indicator field; and

wherein the value range of a HARQ feedback timing indicator field is from an eleventh value to a third maximum value, the eleventh value is not smaller than 2, and the third maximum value is 8, or

wherein the value range of the HARQ feedback timing indicator field is a constant, and from a twelfth value to a thirteenth value, the twelfth value is not smaller than 2, and the thirteenth value is the twelfth value plus the constant.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a first time duration for PDSCH corresponding to system information radio network temporary identifier (SI-RNTI) ; and

wherein the first time duration for PDSCH corresponding to SI-RNTI is a second time duration for PDSCH corresponding to SI-RNTI scaled by an eighth scaling factor, and the second time duration for PDSCH corresponding to SI-RNTI is used by the normal type terminal device, or

wherein the first time duration for PDSCH corresponding to SI-RNTI is a combination of the second time duration for PDSCH corresponding to SI-RNTI plus a third increment value.
The method of claim 12, further comprising:

after receiving a UE dedicated RRC parameters from the network device, applying the first time duration for PDSCH corresponding to SI-RNTI.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a first time duration for SPS PDSCH cancelation; and

wherein the first time duration for SPS PDSCH cancelation is a second time duration for SPS PDSCH cancelation scaled by a ninth scaling factor, and the second time duration for SPS PDSCH cancelation is used by the normal type terminal device, or

wherein the first time duration for SPS PDSCH cancelation is a combination of the second time duration for SPS PDSCH cancelation and a fourth increment value, or

wherein the first time duration for SPS PDSCH cancelation is the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device, or

wherein the first time duration for SPS PDSCH cancelation is a combination of the relaxed processing time for the PDSCH transmission corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device and a first decrement value.
The method of claim 1, wherein determining the at least one time domain parameter comprises:

determining a first search space set group (SSSG) switching time; and

wherein the first SSSG switching time is a second SSSG switching time scaled by a tenth scaling factor, and the second SSSG switching time is used by the normal type terminal device, or

wherein the first SSSG switching time is a combination of the second SSSG switching time and a fifth increment value, or

wherein the first SSSG switching time is a relaxed SPS PDSCH release time duration corresponding to the largest subcarrier spacing supported by the reduced capability type terminal device.
A terminal device comprising:

a processor; and

a memory coupled to the processor and storing instructions thereon, the instructions, when executed by the processor, causing the terminal device to perform acts comprising the method according to any of claims 1-15.
A computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method according to any of claims 1-15.