Method and network apparatus for cross-carrier scheduling

Abstract

Methods and network apparatuses for cross-carrier scheduling are disclosed. A method for cross-carrier scheduling can include determining that a candidate DCI schedules a DG PDSCH for a UE, the DG PDSCH at least partially overlapping with a SPS PDSCH for the UE, wherein the DCI is configured to be transmitted on a first CC having a first SCS and the DG PDSCH is configured for transmission on a second CC having a second SCS different from the first SCS; determining a timing gap based on a minimum of the first SCS and the second SCS; determining that an available time between the scheduled SPS PDSCH and the DCI is equal to or greater than the timing gap; in response to determining that the available time between the scheduled SPS PDSCH and the DCI is equal to or greater than the timing gap, cancelling the SPS PDSCH; and transmitting the DCI to the UE.

Description

[0001] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 049,737, filed July 9, 2020, with the U.S. Patent and Trademark Office, and U.S. Provisional Patent Application No. 17 / 119,637, filed December 11, 2020, with the U.S. Patent and Trademark Office, the entire disclosure of which is incorporated herein by reference. Technical Field

[0002] The specific embodiments described herein relate to systems and methods for processing semi-persistently scheduled or dynamically granted communications in cellular communication protocols involving cross-carrier scheduling (CCS). Background Technology

[0003] In certain cellular communication protocols (such as the cellular communication protocol of the 3rd Generation Partnership Project (3GPP) 5th Generation New Radio (5G-NR) specification for cellular networks), downlink traffic from network devices or network systems to user equipment (UEs) (e.g., smartphones, IoT devices, or other computing or electronic devices) is wirelessly transmitted over a physical downlink shared channel (PDSCH) that can be dynamically scheduled (dynamically licensed or DG) or semi-statically scheduled (SPS). In some implementations, SPS PDSCHs scheduled for transmission on specific resources (e.g., time resources and frequency resources) can be cancelled to allow DG PDSCHs to be transmitted on those resources. Summary of the Invention

[0004] According to one embodiment of this disclosure, a method for cross-carrier scheduling includes: determining by a network a candidate cross-carrier scheduling Dynamic Grant (DG) PDSCH for a User Equipment (UE), the DG PDSCH at least partially overlapping with a scheduled Semi-Static Schedule (SPS) PDSCH for the UE, wherein the candidate DCI is configured to be transmitted on a first component carrier (CC) having a first subcarrier spacing (SCS), and the DG PDSCH is configured to be transmitted on a second CC having a second SCS different from the first SCS. The method further includes: identifying by the network the minimum of the first SCS and the second SCS; determining by the network a timing gap based on the minimum of the first SCS and the second SCS; and determining by the network that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap. The method further includes: canceling the SPS PDSCH by the network in response to determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap; and sending the candidate DCI to the UE by the network.

[0005] According to another embodiment of this disclosure, a network apparatus configured for cross-carrier scheduling includes: a processor; and a non-transitory processor-executable medium storing instructions that, when executed by the processor, cause the processor to perform specific processing. The processing includes: determining a candidate cross-carrier scheduling DCI schedule DG PDSCH for a UE, the DG PDSCH at least partially overlapping with a scheduled semi-static scheduling SPS PDSCH for the UE, wherein the candidate DCI is configured to be transmitted on a first CC having a first SCS, and the DG PDSCH is configured to be transmitted on a second CC having a second SCS different from the first SCS; identifying the minimum of the first SCS and the second SCS; determining a timing gap based on the minimum of the first SCS and the second SCS; and determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap. The processing further includes: canceling the SPS PDSCH in response to determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap; and sending the candidate DCI to the UE.

[0006] According to another embodiment of this disclosure, a method for cross-carrier scheduling includes: determining by the network a candidate cross-carrier scheduling DCI scheduling dynamic grant DG PDSCH for a UE, the DG PDSCH at least partially overlapping with an SPS PDSCH for the UE, wherein the candidate DCI is configured to be transmitted on a first CC having a first SCS, and the DG PDSCH is configured to be transmitted on a second CC having a second SCS different from the first SCS. The method further includes: identifying the first SCS and / or the second SCS by the network; determining a timing gap by the network based on the first SCS and / or the second SCS; determining by the network that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap; canceling the SPS PDSCH by the network in response to determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap; and sending the candidate DCI to the UE. Attached Figure Description

[0007] The accompanying drawings, together with the description, illustrate specific example embodiments.

[0008] Figure 1 An example communication system configured to provide communication between a network device and a UE according to some embodiments is shown.

[0009] Figure 2 An example of CCS via a UE is shown according to some embodiments.

[0010] Figure 3 Examples of scheduling involving DG PDSCH and SPS PDSCH are shown according to some embodiments.

[0011] Figure 4 Examples of proposed scheduling involving DG PDSCH and SPS PDSCH are shown according to some embodiments.

[0012] Figure 5 Examples of CCS processing according to some embodiments are shown.

[0013] Figure 6 Another example of CCS processing according to some embodiments is shown.

[0014] Figure 7 Examples of systems configured for CCS according to some embodiments are shown. Detailed Implementation

[0015] In the following detailed description, specific exemplary embodiments are described by way of illustration. This disclosure should not be construed as strictly limited to the embodiments expressly set forth herein.

[0016] In cellular communications (such as cellular communications conforming to standards and / or protocols included in 3GPP 5G NR technology for cellular networks), downlink traffic from a network device or “gNodeB” (gNB) to a user equipment (UE) (e.g., a smartphone, IoT device, or other communication device configured to communicate with a 5G network) is transmitted via the Physical Downlink Shared Channel (PDSCH). Such communications may be simply referred to herein as “PDSCH”. Specific logic, scheduling, or control parameters for the PDSCH, which may include resources for transmission (such as time and frequency resources reserved for transmission), can be set, defined, or determined through communications transmitted via one or more Physical Downlink Control Channels (PDCCH). Such communications may be simply referred to herein as “PDCCH”.

[0017] According to specific 3GPP 5G protocols, the DG PDSCH is scheduled by the network device to send downlink control information (DCI) to the UE via the PDCCH. According to specific 3GPP 5G protocols, the DCI can be, for example, format DCI 1_0 or DCI 1_1. Along with other information, the DCI also includes time and frequency resources that indicate the UE's expected reception of the DG PDSCH. The UE can then receive the PDSCH at the indicated time and frequency accordingly.

[0018] According to specific 3GPP 5G protocols, SPS PDSCH communication can be implemented, allowing a UE to receive one or more PDSCHs without a separate DCI for each PDSCH. For example, in SPS PDSCH communication, the network device can send the UE a first SPS PDSCH scheduled by a PDCCH (which may be referred to as an SPS PDSCH with a PDCCH). In some respects, this can be similar to the scheduling of DG PDSCHs via a PDCCH. However, here, the first PDCCH may specify that it is not only a DG PDSCH, but also the first occasion of a series of SPS PDSCHs (this can be specified explicitly or implicitly). The UE can learn about the time and frequency resources of subsequent SPS PDSCHs (referred to as SPS PDSCHs without a PDCCH) based on the Radio Resource Control (RRC) configuration of the first SPS PDSCH. Therefore, the UE can be notified to anticipate and receive multiple PDSCHs without a separate PDCCH for each individual PDSCH. The UE can continue to anticipate scheduled (e.g., periodic) PDSCHs until another DCI is sent via the PDCCH that ends the SPS.

[0019] Figure 1A communication system 100 is illustrated that can be used for cellular communications (e.g., according to applicable 3GPP standards). The communication system 100 may include a network device 102, a network 104, and a UE 106. The techniques described herein may be implemented by the communication system 100 (or by one or more components of the communication system 100).

[0020] The network device can be a gNB device and can be configured to schedule transmissions between the gNB and the UE and communicate with one or more other gNBs. The network device can be a 5G network device. Note that the term "network device" can be used herein to refer to a network system, and a network device is not limited to a single physical device, but can also refer to multiple distributed devices (or components thereof) performing networking functions.

[0021] Network 104 may include, for example, a local area network (LAN) (such as a cellular communication network). UE 106 may include, for example, any device configured to communicate via network 104 (e.g., a mobile device, smartphone, tablet computer, desktop computer, laptop computer, LAN device serving a local device and connecting the local device to network 104, Internet of Things device, or any other suitable communication device). Note that the term UE is not necessarily limited to a device operated by a user and may refer to a device that operates independently of user control.

[0022] Figure 2 An example of a CCS via a UE according to some embodiments is shown. The depicted CCS can be implemented by UE 106. As depicted, UE 106 can handle communication in a first cell (referred to in the context as the "scheduling cell") and a second cell (referred to in the context as the "scheduled cell"). The currently depicted example shows two cells with different subcarrier spacings (SCS), where the scheduling cell has a 15 kHz SCS (and parameter configuration (numerology, or parameter set or digital scheme) μ = 0), and the scheduled cell has a 30 kHz SCS (and parameter configuration μ = 1). The 3GPP 5G standard defines specific parameter configurations μ corresponding to specific SCS (including μ = 0 and SCS = 15 kHz, μ = 1 and SCS = 30 kHz, μ = 2 and SCS = 60 kHz, μ = 3 and SCS = 120 kHz, μ = 4 and SCS = 240 kHz), and the 3GPP 5G standard supports, for example... Figure 2 The CCS shown is between cells with different parameter configurations.

[0023] Figure 2The image shows UE 106 decoding PDCCH 202 received in the first three symbols of slot n of the scheduled cell. PDCCH 202 includes DCI (such as DCI) of DG PDSCH 204 scheduled in slot m+1 of the scheduled cell. Figure 3 As shown in the diagram and described in detail below, DCI 302), and UE 106 receives DG PDSCH 204 according to the schedule.

[0024] Such a CCS can be useful for various reasons. For example, 5G frequency range 1 (FR1, 450 MHz to 6 GHz) can be used to receive PDCCHs that schedule PDSCHs in 5G frequency range 2 (FR2, 24.25 GHz to 52.6 GHz). Generally, although communication via FR1 may be slightly slower (in terms of data / second) than communication via FR2, FR1 tends to have better coverage and is more reliable than FR2; therefore, using FR1 for PDCCH and FR2 for PDSCH can be useful. Cross-carrier scheduling involving using FR2 for PDCCH and FR1 for PDSCH is also supported in the 3GPP 5G standard.

[0025] Because (generally speaking) in smaller SCS cells (such as Figure 2 Decoding the PDCCH received on a cell (as shown in the diagram) takes longer than decoding the PDCCH received on a higher SCS cell. Therefore, one potential problem with CCSs with different parameter configurations is that they may involve more buffering due to slower PDCCH decoding, whereas in a self-scheduled scheme, PDCCH processing can be implemented in the same higher SCS cell as the PDSCH. To mitigate this decoding problem, the 3GPP 5G specification implements a timing gap Δ between the end of the last symbol of the received PDCCH (hereinafter referred to as the "end of PDCCH") and the beginning of the first symbol of the received PDSCH (hereinafter referred to as the "beginning of PDSCH"), such that the earliest possible start time of the PDSCH is Δ symbols from the end of the PDCCH. This allows for additional time for decoding the received PDCCH (e.g., this can begin after the PDCCH is received). The following shows the Δ value specified in the 3GPP 5G specification at the time of this disclosure:

[0026] Table 1

[0027] 15 4 30 5 60 10 120 14

[0028] Note that the above considers the SCS of the scheduling cell, but ignores the SCS of the scheduled cell.

[0029] Therefore, it may be important to consider the time required to decode the CCS-scheduled PDCCH by implementing an appropriate timing gap Δ.

[0030] Now refer to Figure 3 , Figure 3 An example of scheduling 300 configured by network device 102 is shown. Note that, although... Figure 3 The horizontal axis represents time, but it can also represent the number of symbols for a given specified SCS (or, correspondingly, a specified parameter configuration). Generally, throughout this disclosure, specifications or requirements regarding timing or time quantities are interchangeable with specifications or requirements regarding the number of symbols and the corresponding SCS or parameter configuration. Where the number of symbols or the SCS (or parameter configuration) is known, predetermined, assumed, or already specified, specifications or requirements regarding timing or time quantities are interchangeable with only one of the specifications or requirements for the number of symbols, the SCS, or the parameter configuration. For example, if the given context involves a predetermined number of symbols, a specification or requirement expressed as a timing requirement (e.g., referring to...) Figure 4 The timing gaps (T or available time) discussed in other figures are interchangeable with specifications or requirements expressed as SCS or parameter configuration requirements. As another example, if the given context involves a predetermined SCS or parameter configuration, specifications or requirements expressed as timing requirements (e.g., timing gaps T or references) are used. Figure 4 The available time discussed may be interchangeable with specifications or requirements expressed as the number of symbols. Thus, as will be clear from the context, for example, "time gap" or "available time" may refer to a time period, or the number of symbols when the SCS or parameter configuration is known, predetermined, assumed, or has been specified, or the SCS or parameter configuration when the number of symbols is known, predetermined, assumed, or has been specified.

[0031] According to some embodiments, scheduling 300 involves DG PDSCH 304 and SPS PDSCH 306. DCI 302 schedules DG PDSCH 304 (e.g., similar to DG PDSCH 204 described above), and SPS PDSCH 306 in the depicted scheduling was previously scheduled via an ongoing SPS. DCI 302 is received via PDCCH (such as PDCCH 202). Figure 3 The timing gap T between the end of the last symbol received by DCI 302 (which may be referred to here as the “end of DCI 302”) and the start of SPS PDSCH is also described, which will be discussed in detail below.

[0032] Network device 102 can configure scheduling 300, and network device 102 and UE 106 can implement scheduling 300 (e.g., network device 102 can send one or more communications according to the schedule, and UE 106 can receive communications according to the schedule). Network device 102 can configure scheduling 300 in a manner that enables UE 106 to manage the schedule (including being able to use scheduled resources (including time resources and frequency resources) to receive communications, taking into account UE 106's processing time requirements or specifications). Network device 102 can configure scheduling 300 according to 3GPP 5G standards, and in some embodiments, scheduling 300 can be configured according to capabilities indicated by UE 106 to network device 102 (e.g., capabilities indicated by UE 106 for CCS) (e.g., indicators or parameters representing timing capabilities for CCS sent by UE 106 to network device 102).

[0033] Because DG PDSCH 304 and SPS PDSCH 306 partially overlap, scheduling 300 indicates a conflict or contradiction between DG PDSCH 304 and SPS PDSCH 306. The conflict indicated in scheduling 300 can be resolved by network device 102 canceling SPS PDSCH 306. Such cancellation can be achieved by network device 102 sending DCI 302 to UE 106. Upon receiving DCI 302 for scheduling DG PDSCH 304, UE 106 will determine that DG PDSCH 304 and SPS PDSCH 306 overlap, and will correspondingly cancel SPS PDSCH 306 (therefore, it can be said that DCI 302 implicitly contains instructions for canceling SPS PDSCH 306). However, after receiving DCI 302, UE 106 needs some time to process DCI 302 (including decoding DCI 302, determining the existence of overlap, and canceling SPS PDSCH 306) – this time is within Figure 3The timing interval T represents this. If DCI 302 is received too close to SPS PDSCH 306, UE 106 may not be able to process the cancellation of SPS PDSCH 306 before it begins, and this could be problematic because SPS PDSCH 306 may be partially processed and subsequently cancelled (thus wasting resources) or not cancelled at all (leading to delays or other complications in DG PDSCH 304 transmission). To avoid such problems, network device 102 ensures that DCI 302 is sent in a timely manner, such that UE 106 completes reception of DCI 302 at least one timing interval T before the start of SPS PDSCH 306. Note that network device 102 can know the time that UE 106 takes to process DCI 302 (e.g., it can know the maximum possible time or the maximum reasonable time) (e.g., because such a maximum processing time is established in the 3GPP 5G standard, and / or because DCI can indicate this to network device 102), and can ensure that DCI 302 is sent in a timely manner to be received at the beginning of timing gap T.

[0034] Note that the term “assured” as used herein may mean a guarantee, or may mean a probability equal to or greater than an acceptable threshold (e.g., 95%+ probability, 99%+ probability, 99.9%+ probability or greater).

[0035] Therefore, when performing scheduling processing, network device 102 can analyze DCI 302 to determine whether it can be transmitted at least a time interval T before the start of SPS PDSCH 306. If network device 102 determines that the candidate time for transmitting DCI 302 is at least a time interval T before the start of SPS PDSCH 306, then network device 102 can responsively determine to continue transmitting DCI 302 (thus implicitly canceling SPS PDSCH 306). If network device 102 determines that the candidate time for transmitting DCI 302 is not at least a time interval T before the start of SPS PDSCH 306 (too close to the start of SPS PDSCH 306 to ensure that UE 106 can cancel SPS PDSCH 306), then network device 102 can responsively determine not to continue transmitting DCI 302 at the candidate time.

[0036] One technique for implementing time slot T is to use a fixed number of symbols (e.g., 14 symbols, which is the number of symbols in a time slot according to the 3GPP 5G standard). For example, 14 symbols may be suitable for self-scheduling (non-cross-carrier scheduling). However, in CCS involving cells with different SCSs, this technique can be improved by taking into account the different SCSs (e.g., by selecting the optimal SCS for a fixed number of symbols, and / or by selecting an optimized number of symbols based on the scheduling cell SCS, the scheduled cell SCS, or both).

[0037] Furthermore, this technique can be improved by establishing a schedule that ensures adaptation to (i) the above reference by selecting or determining an appropriate timing interval T. Figure 2 The described CCS decoding requirements (the use of Δ timing gaps may be considered) and (ii) the above reference Figure 3 The SPS PDSCH cancellation processing requirements just discussed (such as determining that the SPS PDSCH and candidate DG PDSCH overlap and canceling the SPS PDSCH).

[0038] Here (for example, refer to) Figure 5 and Figure 6 This paper describes techniques for providing improved scheduling and adaptability to various timing requirements in CCS. Using such improved techniques, network and UE behavior is clearly defined regarding how to ensure scheduling adapts to various timing requirements for the reception of SPS PDSCH and DG PDSCH. Without such behavior, UEs may receive DCIs they cannot adapt to because DCIs may not arrive in time to cancel SPS PDSCH, or SPS PDSCHs may have to be canceled after processing has begun, or different UEs may have different understandings of which DCIs they might expect the network to adapt to. This adds complexity to the system and places heavy demands on network equipment and UEs. The improved techniques discussed here help avoid or mitigate such problems.

[0039] Note that, although Figure 3A single SPS PDSCH overlapping with candidate DG PDSCH 304 is shown, but in some embodiments, more than one SPS PDSCH may overlap, and the conflict or contradiction resolution techniques described herein (including protocols for canceling overlapping SPS PDSCHs) can be applied to more than one SPS PDSCH. In such embodiments, according to the techniques described herein, network device 102 may determine whether to send candidate DCI 302 in a timely manner to cancel each of the overlapping SPS PDSCHs. If network device 102 determines that at least one overlapping SPS PDSCH cannot be guaranteed to be canceled in a timely manner, network device 102 may respond by determining not to send DCI 302 and not to implement DG PDSCH 304. If network device 102 determines that each overlapping SPS PDSCH is guaranteed to be canceled in a timely manner, network device 102 may respond by determining to send DCI 302, thereby implicitly indicating the cancellation of each overlapping SPS PDSCH. Furthermore, note that although Figure 3 The example shown involves an SPS PDSCH that begins before the start of the DG PDSCH, but the techniques described herein are also applicable to scheduling one or more SPS PDSCHs that begin after the start of the DG PDSCH and overlap with it. In such scenarios, as in... Figure 3 As depicted in the scenario, the timing gap begins at the end of the DCI.

[0040] Now refer to Figure 4 , Figure 4 The diagram illustrates a proposed schedule 400 that network device 102 can analyze during scheduling processing. The proposed schedule 400 may include candidate DCI 402 (which may be similar to DCI 302), candidate DG PDSCH 404 (which may be similar to DG PDSCH 304), SPS PDSCH 406 (which may be similar to SPS PDSCH 306), and a timing gap T corresponding to the processing time of the UE for processing DCI 402 (including the cancellation of SPSPDSCH 406) (which may be similar to...). Figure 3 The timing gaps T shown are as follows. As used herein, candidate DCI and candidate DG PDSCH refer to the DCI and PDSCH that the network device is attempting to schedule. DCI and DG PDSCH may also be referred to as candidate DCI and candidate DGPDSCH when the network device is determining whether it can successfully schedule DCI and PDSCH.

[0041] The proposed scheduling 400 also includes an available time 408 from the end of candidate DCI 402 to the start of SPS PDSCH 406 (note that in scenarios involving multiple overlapping SPS PDSCHs, the available time begins at the end of the DCI and ends at the start of the first SPS PDSCH among the multiple SPS PDSCHs). The available time 408 may correspond to the available time for the UE to process candidate DCI 402 (including, where appropriate, decoding candidate DCI 402 and canceling SPS PDSCH 406 (or multiple SPSPDSCHs)).

[0042] Network device 102 can analyze candidate DCI 402 (received on a scheduled cell with a first SCS) of scheduling candidate DG PDSCH 404 (received on a scheduled cell with a second SCS different from the first SCS), and network device 102 can determine whether candidate DCI 402 can be transmitted given a specific timing requirement or timing specification (including whether candidate DCI 402 will arrive within sufficient time for the receiving UE to process candidate DCI 402). In some embodiments, network device 102 can determine whether available time 408 is at least as large as (equal to or greater than) the timing gap T, and if so, network device 102 can determine that proposed scheduling 400 is feasible and can continue to propose scheduling 400. Specific details of such analysis are discussed herein.

[0043] Now refer to Figure 5 , Figure 5 An example of CCS processing 500 according to some embodiments is shown. CCS processing 500 can be applied to proposed scheduling 400. As a brief overview, CCS processing 500 involves using a fixed number of symbols for timing gap T, and using the minimum SCS of the scheduling cell SCS and the scheduled cell SCS. CCS processing 500 includes determining a DG PDSCH (502) that the CCS DCI schedules at least partially overlaps with at least one SPS PDSCH, identifying the minimum of a first SCS (e.g., the SCS of the scheduling cell) for the first component carrier (CC) of the DCI and a second SCS (e.g., the SCS of the scheduled cell) for the second CC of the DG PDSCH (e.g., the SCS of the scheduled cell). CCS processing 500 also includes determining the timing gap T based on the minimum of the first and second SCS (506), determining that the available time between the SPS PDSCH and the DCI is equal to or greater than the timing gap T, and canceling the SPS PDSCH in response (508), and transmitting the DCI (510).

[0044] The following describes a detailed example of the operation of CCS processing 500. At (502), network device 102 determines whether a candidate CCS DCI 402 can be sent from scheduling candidate DG PDSCH 404. In this example, network device 102 determines that candidate DG PDSCH 404 at least partially overlaps with SPS PDSCH 406 and continues operation (504). In other embodiments, network device 102 may determine that no SPS PDSCH overlaps with DG PDSCH, and network device 102 may continue sending candidate DCI 402. In other embodiments, network device 102 determines that multiple SPS PDSCHs at least partially overlap with candidate DG PDSCH 404, and network device 102 selects the earliest starting SPS PDSCH with the multiple SPS PDSCHs, and continues operation (504) through (510) using the selected SPS PDSCH, thereby ensuring that the timing gap T is sufficient to accommodate the earliest SPS PDSCH, and therefore also accommodates other subsequent SPS PDSCHs.

[0045] In step (504), network device 102 identifies the minimum SCS of the scheduling cell and the SCS of the scheduled cell. Network device 102 may compare the SCS of the scheduling cell with the SCS of the scheduled cell and may select the minimum SCS of the two. In response to determining that one of the SCSs is the minimum possible SCS under the 3GPP 5G standard (e.g., 15kHz), because network device 102 may assume that other SCSs cannot be smaller than the minimum possible SCS under the 3GPP 5G standard, network device 102 may select that SCS and omit evaluating or comparing other SCSs (such processing constitutes an example implementation of network device 102 identifying the minimum SCS of the scheduling cell and the SCS of the scheduled cell). In this example, the two SCSs are different, but in embodiments where the two SCSs are the same, network device 102 may select either SCS.

[0046] In (506), network device 102 may determine timing gap T based on the smallest of the identified first SCS and second SCS (which may be simply referred to as the “minimum SCS”). Timing gap T may be a time quantity corresponding to (e.g., equal to) a predetermined number of symbols having the smallest of the first SCS and second SCS (minimum SCS) (e.g., the number of symbols specified in the 3GPP 5G specification (such as 14 symbols)), or it may be an SCS value equal to the minimum SCS in the context of a specified number of symbols (such as 14 symbols) (e.g., in the 3GPP 5G specification), or it may be a parameter configuration corresponding to the minimum SCS in such a context.

[0047] As mentioned above, generally speaking, communication transmitted via a smaller SCS is more reliable but slower to process (e.g., slower decoding) compared to communication transmitted via a larger SCS. Therefore, by using the smallest SCS (slower processing) when determining the timing gap T, the timing gap T is large enough to account for the slow processing of candidate DCI 402 by UE 106.

[0048] At (508), network device 102 can determine that the available time 408 between SPS PDSCH 406 and candidate DCI 402 is equal to or greater than the timing gap T. In response to determining that the available time 408 between SPS PDSCH 406 and candidate DCI 402 is equal to or greater than the timing gap T, network device 102 can cancel SPS PDSCH. Such cancellation can be achieved by network device 102 sending candidate DCI 402 to UE 106. Upon receiving candidate DCI 402 of scheduling candidate DG PDSCH 404, UE 106 will determine that candidate DG PDSCH 404 overlaps with SPS PDSCH 406, and will cancel SPS PDSCH 406 in response (therefore, it can be said that candidate DCI 402 implicitly includes the instruction to cancel SPS PDSCH 406).

[0049] At (510), network device 102 sends candidate DCI 402 to UE 106. Through the aforementioned operation, network device 102 ensures that candidate DCI 402 will be received by UE 106 in a timely manner, so that even if candidate DCI 402 can be received via a small SPS and therefore may take a longer time to process, UE will process candidate DCI 402 before SPS PDSCH 406 begins.

[0050] Generally, without CCS processing 500, DCIs may not arrive in time to cancel SPPS PDSCH, or SPPS PDSCH processing may have to be cancelled after SPPS PDSCH processing has begun, or different UEs may have different understandings of which DCIs they might expect to adapt to. Therefore, UEs may receive DCIs they cannot adapt to, which increases system complexity and places heavy demands on network equipment and UEs. CCS processing 500 helps avoid or mitigate these problems.

[0051] Now refer to Figure 6 , Figure 6Another example of CCS processing 600 according to some embodiments is shown. CCS processing 600 may be applied to proposed scheduling 400. As a brief overview, CCS processing 600 includes determining a DG PDSCH (602) that at least partially overlaps with at least one SPSPDSCH for CCS DCI scheduling, identifying a first SCS (e.g., the SCS of the scheduling cell) for a first CC for DCI and / or a second SCS (e.g., the SCS of the scheduled cell) for a second CC for DG PDSCH (604). CCS processing 600 also includes determining a timing gap T (606) based on the identified first SCS and / or second SCS, determining that the available time between the SPS PDSCH and DCI is equal to or greater than the timing gap, and canceling the SPS PDSCH in response (608), and sending the DCI (610).

[0052] Operations (604) and (606) will now be described in more detail with reference to the example embodiments. Note that operation (602) may be similar to or the same as operation (502) described above, operation (608) may be similar to or the same as operation (508) described above, and operation (610) may be similar to or the same as operation (510) described above.

[0053] At (604), network device 102 may identify a first SCS and / or a second SCS, and at (606), network device 102 may determine a timing gap T based on the identified first SCS and / or second SCS. Therefore, the timing gap T can be determined considering the first SCS and / or the second SCS, which can affect the processing time of the DCI, thereby affecting the desired timing gap T that allows the UE 106 sufficient time to process the DCI. Some example embodiments of such processing are described below.

[0054] Example 1: Network device 102 identifies a first SCS (Scheduling Cell SCS) and determines a timing gap T based on the first SCS. In one implementation, the timing gap T is determined as a predetermined number of symbols with the first SCS. The predetermined number of symbols can be a number specified by the 3GPP cellular 5G standard (e.g., 14 symbols). In another implementation, UE 106 may indicate a specific number of symbols as a capability to network device 102, and the timing gap T is determined as a specific number of symbols with the first SCS.

[0055] Example 2: Network device 102 identifies a second SCS (Scheduled Cell SCS) and determines a timing gap T based on the second SCS. In one implementation, the timing gap T is determined as a predetermined number of symbols with the second SCS. The predetermined number of symbols can be a number specified by the 3GPP cellular 5G standard (e.g., 14 symbols). In another implementation, UE 106 may indicate a specific number of symbols as a capability to network device 102, and the timing gap T is determined as a specific number of symbols with the second SCS.

[0056] Example 3: Network device 102 identifies the smallest of the first SCS and the second SCS (“minimum SCS”), and determines the timing gap T based on the minimum SCS. This example can be similar to... Figure 5 The CCS processing 500 is shown in the diagram. In one implementation, the timing gap T is determined as a predetermined number of symbols based on a minimum SCS parameter configuration. The predetermined number of symbols can be a number specified by the 3GPP cellular 5G standard (e.g., 14 symbols). In another implementation, the UE 106 may indicate a specific number of symbols as a capability to the network device 102, and the timing gap T is determined as a specific number of symbols with a minimum SCS.

[0057] Example 4: Network device 102 identifies both the first SCS and the second SCS, and determines the timing gap T based on both the first SCS and the second SCS. In one implementation, a specific number of symbols is specified for each possible SCS pair, as shown in the table below, where A x，y Indicates the number of symbols used for timing gap T when the first SCS corresponds to parameter configuration x and the second SCS corresponds to parameter configuration y.

[0058] Table 2

[0059]

[0060]

[0061] Various A x，y Values ​​can be stored in a lookup table accessible, for example, by network device 102. Various A values ​​can be specified in cellular standards such as the 3GPP 5G standard. x，y Value. In some implementations, network device 102 determines the timing gap T as the number A of symbols with the first SCS. x，y In other implementations, network device 102 determines the timing gap T as the number of symbols A with the second SCS. x，y .

[0062] Example 5: Network device 102 identifies at least a first SCS and determines a timing gap T based on the first SCS. In one implementation, a specific number of symbols is specified for each possible SCS value, as shown in the table below, where A x Indicates the number of symbols used for timing gap T when the first SCS corresponds to parameter configuration x.

[0063] Table 3

[0064]

[0065] Various A x Values ​​can be stored in a lookup table accessible, for example, by network device 102. Various A values ​​can be specified in cellular standards such as the 3GPP 5G standard. x Value. In some implementations, network device 102 determines the timing gap T as the number A of symbols with the first SCS. x In other implementations, network device 102 determines the timing gap T as the number of symbols A with the second SCS. x .

[0066] Example 6: Network device 102 identifies a first SCS and / or a second SCS, and determines a timing gap T based on the first SCS and / or the second SCS. In one implementation, the timing gap T is determined to have a number of symbols equal to a predetermined number of symbols plus an additional number of symbols (which may be referred to as an additional offset). The predetermined number of symbols (e.g., 14 symbols) may be specified in cellular standards such as the 3GPP 5G standard. The additional number of symbols may be specified (e.g., in cellular standards such as the 3GPP 5G standard) for a given first SCS / second SCS pair (e.g., similar to how the total number of symbols for timing gap T is specified in Table 2) or for a given first SCS (e.g., similar to how the total number of symbols for timing gap T is specified in Table 3). Such values ​​may be stored in a lookup table accessible to network device 102. The timing gap T may be determined by network device 102 to have a total number of symbols equal to the predetermined number of symbols plus the additional number of symbols, and the total number of symbols may have either the first SCS or the second SCS.

[0067] Example 7A: Applicable when μ scheduled (Parameter configuration of the scheduled cell) > μ schedulling When configuring cell parameters, network device 102 identifies the first SCS and the second SCS, and determines the timing gap T based on the first SCS and the second SCS. Network device 102 determines the number of symbols in timing gap T to be equal to (i). and (ii) The smaller of the two. The value of Δ can be set appropriately (e.g., for the case of CCS with different parameter configurations, it can be the PDCCH-to-PDSCH gap defined in Rel-16 of the 3GPP 5G standard, or it can be determined in a manner similar to the additional offset discussed in Example 6). The sign of the timing gap T can have the first SCS.

[0068] Example 7B: Applicable when μ scheduled (Parameter configuration of the scheduled cell) > μ schedulling When configuring cell parameters, network device 102 identifies the first SCS and the second SCS, and determines the timing gap T based on the first SCS and the second SCS. Network device 102 determines the number of symbols in timing gap T to be equal to (i). The smaller of (ii)14+Δ. The value of Δ can be set appropriately (e.g., it can be determined in a manner similar to the additional offset discussed in Example 6 (e.g., via a lookup table)). The sign of the timing gap T can have a second SCS.

[0069] Example 8: Applicable when μ scheduled <μ schedulling At that time, network device 102 identifies the first SCS and the second SCS, and determines the timing gap T based on the first SCS and the second SCS. Network device 102 determines the timing gap T as a predetermined number of symbols with the second SCS (e.g., the number of symbols specified in a cellular communication standard such as the 3GPP 5G standard) (e.g., 14 symbols) plus an additional offset of Δ symbols with the first SCS. The value of the additional offset can be determined in a similar manner to the additional offset discussed in Embodiment 6.

[0070] One or more of the above embodiments can be used to implement operations (604) and (606) of CCS processing 600.

[0071] Generally, without CCS processing 600, DCIs may not be compatible with the system because they may not arrive in time to cancel SPPS PDSCH, or SPPS PDSCH processing may have to be canceled after SPPS PDSCH processing has begun, or different UEs may have different understandings of which DCIs they might expect the network to adapt to. This adds complexity to the system and places heavy demands on network equipment and UEs. CCS processing 600 helps avoid or mitigate these problems.

[0072] Figure 7 An example of a system 700 configured to implement CCS according to some embodiments is shown. (Refer to...) Figure 7Electronic device 701 (which may be similar to or the same as UE 106) in network environment (or system) 700 may communicate with electronic device 702 via a first network 798 (e.g., a short-range wireless communication network, such as a Wi-Fi network), or with electronic device 704 or server 708 (which may be similar to or the same as network 104) via a second network 799 (which may be similar to or the same as network 104) (e.g., a long-range wireless communication network, such as a cellular communication network, such as a 5G network). Electronic device 701 may communicate with electronic device 704 via server 708. Electronic device 701 may include processor 720, memory 730, input device 750, sound output device 755, display device 760, audio module 770, sensor module 776, interface 777, haptic module 779, camera module 780, power management module 788, battery 789, communication module 790, subscriber identification module (SIM) 796, and / or antenna module 797. In one embodiment, at least one component (e.g., display device 760 or camera module 780) may be omitted from electronic device 701, or one or more other components may be added to electronic device 701. In one embodiment, some components may be implemented as a single integrated circuit (IC). For example, sensor module 776 (e.g., fingerprint sensor, iris sensor, or illuminance sensor) may be embedded in display device 760 (e.g., display), or display device 760 may also include one or more sensors in addition to sensor module 776.

[0073] In some embodiments, electronic device 701 may include configurations for implementing cross-carrier scheduling (such as...) Figure 5 The cross-carrier scheduling process 500 or shown in the figure Figure 6 The computing device or processor shown in the figure is a cross-carrier scheduling process 600.

[0074] Processor 720 can execute, for example, software (e.g., program 740) to control at least one other component (e.g., hardware or software component) of electronic device 701 connected to processor 720, and can perform various data processing and / or calculations. As at least part of data processing and / or calculations, processor 720 can load commands or data received from another component (e.g., sensor module 776 or communication module 790) into volatile memory 732, process the commands or data stored in volatile memory 732, and store the resulting data in non-volatile memory 734. Processor 720 may include a main processor 721 (e.g., central processing unit (CPU) or application processor (AP)) and an auxiliary processor 723 (e.g., graphics processing unit (GPU), image signal processor (ISP), sensor hub processor, or communication processor (CP)) that can operate independently of or in conjunction with the main processor 721. Additionally or optionally, auxiliary processor 723 may be adapted to consume less power than main processor 721 and / or perform specific functions. The auxiliary processor 723 can be implemented separately from the main processor 721 or as part of the main processor 721.

[0075] The auxiliary processor 723 may replace the main processor 721 when the main processor 721 is inactive (e.g., in sleep) or, when the main processor 721 is active (e.g., executing an application), work with the main processor 721 to control at least some of the functions or states associated with at least one component of the electronic device 701 (e.g., display device 760, sensor module 776, or communication module 790). According to one embodiment, the auxiliary processor 723 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., a camera module 780 or communication module 790) functionally associated with the auxiliary processor 723.

[0076] The memory 730 may store various data used by at least one component of the electronic device 701 (e.g., processor 720 or sensor module 776). The various data may include, for example, software (e.g., program 740) and input or output data for commands associated therewith. The memory 730 may include volatile memory 732 and / or non-volatile memory 734.

[0077] The program 740 may be stored as software in the memory 730 and may include, for example, an operating system (OS) 742, middleware 744, or application 746.

[0078] Input device 750 can receive commands or data from outside electronic device 701 (e.g., a user) that will be used by another component of electronic device 701 (e.g., processor 720). Input device 750 may include, for example, a microphone, mouse, and / or keyboard.

[0079] The sound output device 755 can output sound signals to the outside of the electronic device 701. The sound output device 755 may include, for example, a speaker or a receiver. The speaker can be used for general purposes (such as playing multimedia or recording), and the receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of the speaker.

[0080] Display device 760 can visually provide information to the outside of electronic device 701 (e.g., to a user). Display device 760 may include, for example, a display, a holographic device, and / or a projector, and control circuitry for controlling a respective one of the display, holographic device, and projector. According to one embodiment, display device 760 may include touch circuitry adapted to detect touch, or sensor circuitry adapted to measure the intensity of the force caused by touch (e.g., a pressure sensor).

[0081] The audio module 770 can convert sound into electrical signals and vice versa. According to one embodiment, the audio module 770 can acquire sound via an input device 750 and / or output sound via a sound output device 755 or headphones of an external electronic device 702 that is directly (e.g., wired) or wirelessly connected to the electronic device 701.

[0082] Sensor module 776 can detect the operating state of electronic device 701 (e.g., power or temperature) and / or the environmental state outside electronic device 701 (e.g., user state), and then generate an electrical signal or data value corresponding to the detected state. Sensor module 776 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an accelerometer, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, and / or an illuminance sensor.

[0083] Interface 777 may support one or more specified protocols for direct (e.g., wired) or wireless connection of electronic device 701 to external electronic device 702. According to one embodiment, interface 777 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital Card (SD) interface, and / or an audio interface.

[0084] The connection terminal 778 may include a connector via which the electronic device 701 can be physically connected to an external electronic device 702. According to one embodiment, the connection terminal 778 may include, for example, an HDMI connector, a USB connector, an SD card connector, and / or an audio connector (e.g., a headphone connector).

[0085] The haptic module 779 can convert electrical signals into mechanical stimuli (e.g., vibration or motion) and / or electrical stimuli that can be recognized by a user via touch or kinesthesia. According to one embodiment, the haptic module 779 may include, for example, a motor, a piezoelectric element, and / or an electrical stimulator.

[0086] The camera module 780 can capture still or moving images. According to one embodiment, the camera module 780 may include one or more lenses, an image sensor, an image signal processor, and / or a flash.

[0087] The power management module 788 manages the power supplied to the electronic device 701. The power management module 788 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

[0088] The battery 789 can supply power to at least one component of the electronic device 701. According to one embodiment, the battery 789 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, and / or a fuel cell.

[0089] Communication module 790 can support the establishment of a direct (e.g., wired) or wireless communication channel between electronic device 701 and external electronic devices (e.g., electronic device 702, electronic device 704, and / or server 708), and perform communication via the established communication channel. Communication module 790 may include one or more communication processors that can operate independently of processor 720 (e.g., AP), and can support direct (e.g., wired) and / or wireless communication. According to one embodiment, communication module 790 may include wireless communication module 792 (e.g., cellular communication module, short-range wireless communication module, and / or Global Navigation Satellite System (GNSS) communication module) or wired communication module 794 (e.g., local area network (LAN) communication module or power line communication (PLC) module). A corresponding one of these communication modules can communicate via a first network 798 (e.g., such as...). A wireless fidelity (Wi-Fi) direct connection and / or a short-range communication network conforming to the Infrared Data Association (IrDA) standard) or a second network 799 (e.g., a long-range communication network such as a cellular network, the Internet and / or a computer network (e.g., a LAN or a wide area network (WAN)) communicates with an external electronic device. Bluetooth is a registered trademark of Bluetooth Special Interest Group (SIG) Inc., Kirkland, Washington. These various types of communication modules can be implemented as a single component (e.g., a single IC) or as multiple components separate from each other (e.g., multiple ICs). Wireless communication module 792 can use user information (e.g., International Mobile Subscriber Identity (IMSI)) stored in user identification module 796 to identify and authenticate electronic device 701 in a communication network (such as a first network 798 or a second network 799).

[0090] Antenna module 797 can transmit signals and / or power to and / or receive signals and / or power from the outside of electronic device 701 (e.g., external electronic device). According to one embodiment, antenna module 797 may include one or more antennas, whereby at least one antenna suitable for a communication scheme used in a communication network (such as a first network 798 and / or a second network 799) can be selected, for example, by communication module 790 (e.g., wireless communication module 792). Signals and / or power can then be transmitted and / or received between communication module 790 and external electronic device via the selected at least one antenna.

[0091] At least some of the aforementioned components can be interconnected and transmit signals (e.g., commands and / or data) between them via peripheral communication schemes (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI) and / or mobile industrial processor interface (MIPI)).

[0092] According to one embodiment, commands and / or data can be sent and / or received between electronic device 701 and external electronic device 704 via server 708 connected to a second network 799. Each of electronic devices 702 and 704 can be a device of the same or different type as electronic device 701. All or some of the operations to be performed at or by electronic device 701 can be performed at one or more of external electronic devices 702, 704, or 708. For example, if electronic device 701 is required to perform a function and / or service automatically or in response to a request from a user or another device, electronic device 701 may perform the function and / or service instead of performing it, or may request one or more external electronic devices to perform at least a portion of the function and / or service in addition to performing the function and / or service. The one or more external electronic devices receiving the request may perform at least a portion of the requested function and / or service, and / or additional functions and / or additional services associated with the request, and transmit the result of the execution to electronic device 701. Electronic device 701 can provide the result as at least part of a response to a request, with or without further processing. For this purpose, cloud computing, distributed computing, and / or client-server computing technologies may be used, for example.

[0093] One embodiment may be implemented as software (e.g., program 740) including one or more instructions stored in a storage medium (e.g., internal memory 736 or external memory 738) readable by a machine (e.g., electronic device 701). For example, a processor of electronic device 701 may invoke at least one of the one or more instructions stored in the storage medium and execute it under the control of the processor with or without one or more other components. Thus, the machine may be operable to perform at least one function according to the invoked at least one instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. Machine-readable storage media may be provided in the form of non-transitory storage media. The term "non-transitory" indicates that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but this term does not distinguish between cases where data is semi-permanently stored in the storage medium and cases where data is temporarily stored in the storage medium.

[0094] According to one embodiment, the disclosed method may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., an optical disc read-only memory (CD-ROM)) or via an app store (e.g., the Play Store). TMThe computer program product may be distributed online (e.g., downloaded or uploaded) or directly between two user devices (e.g., smartphones). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium (such as the memory of a manufacturer's server, an app store's server, or a relay server).

[0095] Embodiments of this disclosure have been described in detail herein with reference to the accompanying drawings. It should be noted that even if the same or similar elements are shown in different drawings, they may be designated by the same reference numerals / letters. Specific details such as detailed configurations and components are provided in the description herein to aid in a comprehensive understanding of the embodiments of this disclosure. Various changes and modifications may be made to the embodiments described herein without departing from the scope of this disclosure. For clarity and conciseness, certain detailed descriptions may be omitted.

[0096] This disclosure provides various modifications and embodiments. It should be understood that this disclosure is not limited to the various embodiments expressly described or detailed herein, and that this disclosure includes modifications, equivalents, and alternatives within the scope of this disclosure.

[0097] Although terms including ordinal numbers such as first, second, etc., may be used to describe various elements, the elements are not limited by these terms. These terms are used to distinguish one element from another and do not imply any specific order. As used herein, the term “and / or” includes any and all combinations of one or more related items. Unless the context clearly indicates otherwise, the singular form is intended to include the plural form as well. In this disclosure, it should be understood that the terms “comprising” or “having” indicate the presence of features, quantities, steps, operations, structural elements, components, or combinations thereof, without excluding the possibility of the presence of one or more other features, quantities, steps, operations, structural elements, components, or combinations thereof, or the addition of one or more other features, quantities, steps, operations, structural elements, components, or combinations thereof.

[0098] According to one embodiment, at least one of the above-described components (e.g., a manager, a processor-executable instruction set, a program, or a module) may comprise a single entity or multiple entities. One or more of the above-described components may be omitted, or one or more other components may be added. Optionally or additionally, multiple components (e.g., a manager, a processor-executable instruction set, a program, or a module) may be integrated into a single component. In this case, the integrated component can still perform one or more functions of each of the multiple components in the same or similar manner as they were performed by the corresponding one of the multiple components prior to integration. Operations performed by the manager, processor-executable instruction set, program, module, or other component may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

[0099] While specific reference is made to the 3GPP 5G specification herein, the technologies disclosed herein can be applied to or extended to other specifications, including cellular specifications (3GPP or others, such as 3GPP 4G or LTE specifications, any cellular specification that follows 5G (e.g., 6G specifications)).

Claims

1. A method for cross-carrier scheduling, comprising: The network device determines the candidate downlink control information (DCI) for user equipment, schedules the dynamically licensed physical downlink shared channel (PDSCH) (DG PDSCH), and the DG PDSCH at least partially overlaps with the scheduled semi-static scheduling (SPS PDSCH) for user equipment. The candidate DCI is configured to be transmitted on a first component carrier having a first subcarrier spacing, and the DGPDSCH is configured to be transmitted on a second component carrier having a second subcarrier spacing different from the first subcarrier spacing. The network device identifies the smallest of the first subcarrier spacing and the second subcarrier spacing. The timing gap is determined by the network device based on the minimum of the first subcarrier interval and the second subcarrier interval; The network device determines that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap. In response to determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the time slot, the network device cancels the SPS PDSCH; and The network device sends the candidate DCI to the user equipment.

2. The method according to claim 1, wherein, The steps for determining the timing gap include: determining the number of designated symbols having the smallest of the first subcarrier gap and the second subcarrier gap.

3. The method according to claim 2, wherein, The specified number of symbols is a predetermined number of symbols specified by the cellular standard.

4. The method according to claim 2, further comprising: The network device receives a specified number of symbols from the user equipment as an indication of the user equipment's capabilities.

5. The method according to any one of claims 2 to 4, further comprising: The network device determines that each of a plurality of scheduled SPS PDSCHs at least partially overlaps with a DG PDSCH, the plurality of scheduled SPS PDSCHs including the scheduled SPS PDSCH; The network device determines that the scheduled SPS PDSCH has the earliest start among the plurality of scheduled SPS PDSCHs; and The network device selects the scheduled SPS PDSCH for analysis, including determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap.

6. A network apparatus configured for cross-carrier scheduling, comprising: processor; and Non-transitory processor-executable medium stores instructions that, when executed by a processor, cause the processor to: The candidate downlink control information (DCI) for user equipment is determined, and the dynamically licensed physical downlink shared channel (PDSCH) of the DG is scheduled. The DG PDSCH overlaps at least partially with the scheduled semi-static scheduling (SPS PDSCH) for user equipment. The candidate DCI is configured to be transmitted on a first component carrier having a first subcarrier spacing, and the DG PDSCH is configured to be transmitted on a second component carrier having a second subcarrier spacing different from the first subcarrier spacing. Identify the smallest of the first subcarrier spacing and the second subcarrier spacing; The timing gap is determined based on the minimum of the first subcarrier interval and the second subcarrier interval; Determine that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap; In response to determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the time slot, the SPS PDSCH is cancelled; and Send candidate DCIs to the user equipment.

7. The network device according to claim 6, wherein, The steps for determining the timing gap include: determining the number of designated symbols having the smallest of the first subcarrier gap and the second subcarrier gap.

8. The network device according to claim 7, wherein, The specified number of symbols is a predetermined number of symbols specified by the cellular standard.

9. The network device according to claim 7, wherein, When executed by the processor, the instructions also cause the processor to: process a specified number of symbols as an indication of the capabilities of the user equipment, wherein the indication of the capabilities of the user equipment is received from the user equipment.

10. The network device according to any one of claims 7 to 9, wherein, When executed by the processor, the instruction also causes the processor to: Each of a plurality of scheduled SPPS PDSCHs is determined to at least partially overlap with a DG PDSCH, the plurality of scheduled SPPS PDSCHs including the scheduled SPPS PDSCH; Determine the earliest start of the scheduled SPS PDSCH among the plurality of scheduled SPS PDSCHs; and Select the scheduled SPS PDSCH for analysis that includes determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the time interval.

11. A method for cross-carrier scheduling, comprising: The network device determines the candidate downlink control information (DCI) for user equipment, schedules the dynamically licensed physical downlink shared channel (PDSCH) (DG PDSCH), and the DG PDSCH at least partially overlaps with the scheduled semi-static scheduling (SPS PDSCH) for user equipment. The candidate DCI is configured to be transmitted on a first component carrier having a first subcarrier spacing, and the DGPDSCH is configured to be transmitted on a second component carrier having a second subcarrier spacing different from the first subcarrier spacing. The network device identifies the first subcarrier spacing and / or the second subcarrier spacing; The timing gap is determined by the network device based on the identified first subcarrier interval and / or second subcarrier interval; The network device determines that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the timing gap. In response to determining that the available time between the scheduled SPS PDSCH and the candidate DCI is equal to or greater than the time slot, the network device cancels the SPS PDSCH; and Send candidate DCIs to the user equipment.

12. The method according to claim 11, wherein, The timing gap is determined by the network device based on the number of symbols with the first subcarrier interval.

13. The method according to claim 11, wherein, The timing gap is determined by the network device based on the number of symbols with a second subcarrier spacing.

14. The method of claim 11, further comprising: The number of symbols is determined by the network device based on both the first subcarrier interval and the second subcarrier interval, wherein the timing gap is determined by the network device based on the number of symbols having either the first subcarrier interval or the second subcarrier interval.

15. The method of claim 11, further comprising: The network device determines the additional offset based on the first subcarrier spacing and / or the second subcarrier spacing, wherein the timing gap is determined by the network device based on the number of symbols used for non-cross-carrier scheduling by the cellular communication standard plus the additional offset.

16. The method according to claim 11, wherein, The network device determines the timing gap to be equal to the minimum of the following: (14 symbols) ) and (14 symbols) Δ), Wherein, Δ is an additional offset based on the first subcarrier spacing and / or the second subcarrier spacing. It is the parameter configuration corresponding to the second subcarrier spacing, and It is the parameter configuration corresponding to the first subcarrier spacing.

17. The method according to claim 11, wherein, The network device determines the timing gap to be equal to the minimum of the following: (14 symbols) ) and (14 symbols) ), Wherein, Δ is an additional offset based on the first subcarrier spacing and / or the second subcarrier spacing. It is the parameter configuration corresponding to the second subcarrier spacing, and It is the parameter configuration corresponding to the first subcarrier spacing.

18. The method of claim 11, further comprising: The network device receives from the user equipment an indication of the user equipment's timing capabilities for cross-carrier scheduling, wherein the network device further determines timing gaps based on the indication of the user equipment's timing capabilities for cross-carrier scheduling.

Images