Methods and apparatus for reactivation and determination of semi-static scheduling

Abstract

This disclosure relates to a method and apparatus for reactivating and determining semi-static scheduling (SPS). The method for determining the reactivation of a semi-static scheduling includes: determining the type of semi-static scheduling to be reactivated based on an instruction from a network-side device. According to this disclosure, when instructing a terminal to reactivate a SPS, the network-side device can indicate the type of SPS to be reactivated. This allows the terminal to accurately determine the type of SPS that needs to be reactivated, thereby reactivating the corresponding type of SPS and ceasing communication with the network-side device through the configuration of the reactivated SPS, thus avoiding the impact on communication performance caused by reactivating an incorrect type of SPS.

Description

[0001] This application is based on a Chinese patent application, application number PCT / CN2021 / 129893, filed on November 10, 2021. Priority is claimed in the aforementioned Chinese patent application, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and more specifically, to a method for determining the reactivation of semi-static scheduling, a device for determining the reactivation of semi-static scheduling, a device for determining the reactivation of semi-static scheduling, a communication device, and a computer-readable storage medium. Background Technology

[0003] In related technologies, semi-static scheduling (SPS) has been proposed, which can configure periodic resources for terminals. After SPS is activated, downlink resource scheduling is no longer required when performing downlink transmission. The terminal receives downlink transmission according to the configuration of the activated SPS, which helps to save signaling overhead.

[0004] Subsequently, network-side devices can also instruct the terminal to activate SPS as needed. After the terminal activates SPS according to the instruction, it stops receiving downlink transmissions according to the configuration of SPS.

[0005] Furthermore, a terminal can be configured with multiple SPSs, and the network can instruct the terminal to activate one of the multiple SPSs as needed. However, in some cases, the terminal cannot accurately distinguish which SPS is being deactivated by the deactivation instruction sent by the network, leading to some problems. Summary of the Invention

[0006] In view of the above, embodiments of this disclosure provide a method for determining the reactivation of semi-static scheduling, a device for determining the reactivation of semi-static scheduling, a device for determining the reactivation of semi-static scheduling, a communication device, and a computer-readable storage medium to solve the technical problems in the related art.

[0007] According to a first aspect of the present disclosure, a method for determining the reactivation of semi-static scheduling is provided, executed by a terminal, the method comprising: determining the type of semi-static scheduling to be reactivated based on an instruction from a network-side device.

[0008] According to a second aspect of the present disclosure, a semi-static scheduling reactivation method is proposed, executed by a network-side device, the method comprising: determining the type of the semi-static scheduling (SPS) for which a terminal is to be reactivated; and instructing the terminal to determine the type.

[0009] According to a third aspect of the present disclosure, a semi-static scheduling reactivation determination apparatus is provided, comprising one or more processors configured to: determine the type of semi-static scheduling to be reactivated based on an instruction from a network-side device.

[0010] According to a fourth aspect of the present disclosure, a semi-static scheduling reactivation apparatus is provided, comprising one or more processors configured to: determine the type of a semi-static scheduling (SPS) for which a terminal is to be reactivated; and instruct the terminal to determine the type.

[0011] According to a fifth aspect of the present disclosure, a communication device is provided, comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the above-described semi-static scheduling reactivation determination method is implemented.

[0012] According to a sixth aspect of the present disclosure, a communication device is provided, comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the above-described semi-static scheduling reactivation method is implemented.

[0013] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided for storing a computer program that, when executed by a processor, implements the steps in the above-described semi-static scheduling reactivation determination method.

[0014] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided for storing a computer program that, when executed by a processor, implements the steps in the above-described semi-static scheduling reactivation method.

[0015] According to embodiments of this disclosure, when instructing a terminal to reactivate an SPS, the network-side device can instruct the terminal to reactivate the type of SPS. This enables the terminal to accurately determine the type of SPS that needs to be reactivated, thereby reactivating the corresponding type of SPS and stopping communication with the network-side device through the configuration of the reactivated SPS, thus avoiding the impact on communication performance caused by reactivating the wrong type of SPS. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a schematic flowchart illustrating a semi-static scheduling reactivation determination method according to an embodiment of the present disclosure.

[0018] Figure 2 This is a schematic diagram illustrating a configuration of a group common SPS according to an embodiment of the present disclosure.

[0019] Figure 3 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure.

[0020] Figure 4 This is a temporal schematic diagram illustrating a reactivation process according to an embodiment of the present disclosure.

[0021] Figure 5 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure.

[0022] Figure 6 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure.

[0023] Figure 7 This is a temporal schematic diagram illustrating another reactivation according to an embodiment of the present disclosure.

[0024] Figure 8 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure.

[0025] Figure 9 This is a temporal schematic diagram illustrating another reactivation according to an embodiment of the present disclosure.

[0026] Figure 10 This is a schematic flowchart illustrating a semi-static scheduling reactivation method according to an embodiment of the present disclosure.

[0027] Figure 11 This is a schematic flowchart illustrating another semi-static scheduling reactivation method according to embodiments of the present disclosure.

[0028] Figure 12 This is a schematic flowchart illustrating another semi-static scheduling reactivation method according to embodiments of the present disclosure.

[0029] Figure 13 This is a schematic flowchart illustrating another semi-static scheduling reactivation method according to embodiments of the present disclosure.

[0030] Figure 14This is a schematic flowchart illustrating another semi-static scheduling reactivation method according to embodiments of the present disclosure.

[0031] Figure 15 This is a schematic block diagram illustrating a reactivation apparatus for semi-static scheduling according to embodiments of the present disclosure.

[0032] Figure 16 This is a schematic block diagram illustrating an apparatus for determining the reactivation of a semi-static schedule according to embodiments of the present disclosure. Detailed Implementation

[0033] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0034] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0035] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, a first RNTI may also be referred to as a second RNTI without departing from the scope of embodiments of this disclosure, and similarly, a second RNTI may also be referred to as a first RNTI. Depending on the context, the word "if" as used herein may be interpreted as "when," "in response to a determination," or "when," or "in the event of a determination."

[0036] For the sake of brevity and ease of understanding, this document uses the terms "greater than" or "less than", "higher than" or "lower than" to describe size relationships. However, it will be understood by those skilled in the art that the term "greater than" also includes the meaning of "greater than or equal to", and "less than" also includes the meaning of "less than or equal to"; the term "higher than" also includes the meaning of "higher than or equal to", and "lower than" also includes the meaning of "lower than or equal to".

[0037] Figure 1This is a schematic flowchart illustrating a semi-static scheduling reactivation determination method according to an embodiment of the present disclosure. The semi-static scheduling reactivation determination method shown in this embodiment can be executed by a terminal, which includes, but is not limited to, communication devices such as mobile phones, tablets, wearable devices, sensors, and IoT devices. The terminal can communicate with network-side devices, which include, but are not limited to, network-side devices in 4G, 5G, and 6G communication systems, such as base stations and core networks.

[0038] In one embodiment, the network-side device can configure one or more SPS configurations for the terminal. When a certain SPS needs to be used, the device can instruct the terminal to activate one of the SPSs and receive downlink information according to the configuration of the activated SPS.

[0039] Subsequently, the network-side device can also instruct the terminal to activate the SPS as needed. After activating the SPS according to the network-side device's instruction, the terminal stops receiving downlink transmissions according to the SPS configuration. However, in some cases, some terminals may fail to correctly decode the instruction sent by the network-side device, resulting in an inability to correctly determine the SPS that needs to be deactivated. The network-side device can determine whether the terminal has correctly decoded the instruction based on the information fed back by the terminal. If it is determined that the terminal has not correctly decoded the instruction, the network-side device can instruct the destination again to reactivate the SPS.

[0040] The network-side equipment can configure various types of SPS for the terminal. The following embodiments mainly focus on the configuration of group common SPS and UE-specific SPS for the terminal by the network-side equipment, and provide an exemplary description of the technical solution of this disclosure.

[0041] For group common SPS, during initial deactivation, downlink control information (DCI) scrambled with the group scheduled-radio network temporary identity (GS-RNTI) can be transmitted in the group common physical downlink control channel (PDCCH) to indicate deactivation. After receiving the indication, the terminal can decode the DCI and determine the RNTI used for decoding. Then, based on the RNTI (specifically, the RNTI value), the SPS that needs to be deactivated is the group common SPS.

[0042] It should be noted that the scrambling of DCI described in all embodiments of this disclosure can specifically be a cyclic redundancy check (CRC) of scrambling DCI, which is referred to as scrambling of DCI in this disclosure.

[0043] The terminal may be a terminal that supports MBS (Multicast Broadcast service), and the terminal may also support unicast services.

[0044] The aforementioned group common SPS can be configured for terminals in the same group. However, since different terminals in the same group may have different channel transmission conditions, some terminals may be able to correctly demodulate and determine the RNTI, while others may not. Terminals that correctly demodulate and determine the RNTI can return an ACK to the network-side device, while terminals that fail to correctly demodulate and determine the RNTI can return an NACK to the network-side device. The network-side device can determine which terminals failed to correctly demodulate and determine the RNTI based on the received feedback.

[0045] For terminals that have not correctly demodulated and determined their RNTI, network-side equipment can re-instruct the terminal to reactivate the group common SPS. Currently, one method for re-instructing the terminal is through the UE-specific physical downlink control channel (PDCCH). However, the UE-specific PDCCH is primarily used to deactivate UE-specific SPS in a semi-static scheduling manner. When using the UE-specific PDCCH to deactivate group common SPS, the terminal has difficulty distinguishing which type of SPS the UE-specific PDCCH is deactivating.

[0046] like Figure 1 As shown, the semi-static scheduling reactivation determination method may include the following steps:

[0047] In step S101, the type of semi-static scheduling to be reactivated is determined according to the instructions of the network-side device.

[0048] In one embodiment, when instructing a terminal to reactivate an SPS, the network-side device can specify the type of SPS to be reactivated. This allows the terminal to accurately determine the type of SPS that needs to be reactivated, thereby reactivating the corresponding type of SPS and ceasing communication with the network-side device through the configuration of the reactivated SPS, such as ceasing to receive downlink information, thus avoiding the impact on communication performance caused by reactivating an incorrect type of SPS.

[0049] In one embodiment, the type includes at least one of the following: group common SPS; UE-specific SPS.

[0050] The network-side device can instruct the terminal to reactivate either the group common SPS or the UE-specific SPS. When the terminal determines to reactivate the group common SPS according to the instruction, it can reactivate the group common SPS and stop communicating with the network-side device according to the configuration of the group common SPS; when the terminal determines to reactivate the UE-specific SPS according to the instruction, it can reactivate the UE-specific SPS and stop communicating with the network-side device according to the configuration of the UE-specific SPS.

[0051] In one embodiment, the indication of the network-side device includes at least one of the following:

[0052] Explicit instructions and implicit instructions.

[0053] The network-side device can instruct the terminal in two ways: explicit instruction, such as sending one or more messages to the terminal, the content of which directly indicates the type; or implicit instruction, such as sending messages to the terminal that have other functions and are not directly used to indicate the type. The terminal can determine the type of SPS that needs to be reactivated based on the information in some way. For example, the information may be a DCI in the User-Specific Search Space (USS), which is scrambled by RNTI. This DCI is not used to indicate the type, but the terminal can determine the type based on the RNTI of the scrambled DCI.

[0054] Figure 2 This is a schematic diagram illustrating a configuration of a group common SPS according to an embodiment of the present disclosure.

[0055] like Figure 2 As shown, for example, for terminals that support MBS, the network-side equipment must at least configure a group common SPS for the terminal, where the group common SPS is surrounded by 5 time slots, for example... Figure 2In the groupcommon SPS, the Physical Downlink Shared Channel (PDSCH) is located in slot #n+1, and the next one is located in slot #n+6, with an interval of 5 slots.

[0056] The network-side device performs initial deactivation of the group common SPS in slot #n. For example, it sends the group common PDCCH to terminals belonging to the same group in slot #n. The DCI in the group common PDCCH is scrambled using GS-RNTI. If the terminal correctly demodulates and determines the RNTI corresponding to the DCI, it can stop communicating with the network-side device according to the configuration of the group common PDCCH. For example, it can stop receiving the PDSCH of the group common SPS in slots #n+1 and #n+6.

[0057] The network-side device can determine whether the terminal has correctly demodulated and determined the RNTI corresponding to the DCI based on the information fed back by each terminal. For example, if the terminal returns an ACK confirmation message, the network-side device determines that the terminal has correctly demodulated and determined the RNTI. If the terminal returns an NACK unacknowledged message, the network-side device determines that the terminal has not correctly demodulated and determined the RNTI.

[0058] In addition, if the network-side equipment also configures the terminal with UE-specific SPS, it can transmit DCI scrambled by CS-RNTI in the USS for reactivation.

[0059] The following embodiments are mainly in Figure 2 Based on the embodiments shown, several methods by which network-side devices instruct terminals to reactivate group common SPS are illustrated.

[0060] Figure 3 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of this disclosure. Figure 3 As shown, the type of semi-static scheduling to be reactivated based on the instructions of the network-side device includes:

[0061] In step S301, downlink control information (DCI) for deactivating SPS is received from the user equipment dedicated search space (USS).

[0062] In step S302, the type is determined based on the Radio Network Temporary Identifier (RNTI) scrambled with the DCI.

[0063] It should be noted that the terminal can determine whether a DCI is used to deactivate SPS through an agreed-upon method, and the determination criteria include at least one of the following:

[0064] The CRC of DCI is scrambled by CS-RNTI or by GS-RNTI;

[0065] The NDI (New data indicator) field in DCI is 0;

[0066] If a DFI exists in a DCI, the DFI field (DCI format indicator) is 0;

[0067] The DCI includes a PDSCH to HARQ (Hybrid Automatic Repeat reQuest) feedback timing indication field, which is used to indicate the availability of uplink subframes.

[0068] After making the above judgment, the terminal can further determine whether the validation field in the DCI meets the deactivation condition. If the deactivation condition is met, the terminal will determine how to receive the PDSCH of the SPS based on the higher-level configuration information corresponding to the configuration of the SPS to be deactivated and the dynamic scheduling information in the DCI.

[0069] In one embodiment, the network-side device may transmit a DCI for deactivating the SPS in the USS, for example, the DCI carried in the UE-specific PDCCH, to instruct the terminal that has not correctly demodulated and determined the RNTI to reactivate the group common SPS.

[0070] The terminal can pre-store the correspondence between RNTIs and SPS types, such as those agreed upon by the protocol or pre-configured by the network-side device. After receiving the DCI used to deactivate the SPS from the USS, the terminal can determine the RNTI that scrambled the DCI. For example, it can descramble the DCI using the RNTI. The RNTI that successfully descrambled the DCI corresponds to the RNTI that scrambled the DCI. Therefore, the RNTI that scrambled the DCI can be determined based on the RNTI that successfully descrambled the DCI. Furthermore, based on the RNTI that scrambled the DCI and the correspondence, the type of SPS corresponding to the RNTI that scrambled the DCI can be determined.

[0071] Figure 4 This is a temporal schematic diagram illustrating a reactivation process according to an embodiment of the present disclosure.

[0072] like Figure 4As shown, if the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to deactivate the group common SPS in slot #n, the network-side device can send a UE-specific PDCCH (carrying a DCI scrambled with the RNTI) to the terminal, for example, in slot #n+5, to instruct the terminal to reactivate the group common SPS. After the terminal reactivates the group common SPS, it can stop communicating with the network-side device according to the configuration of the group common SPS, for example, it can stop receiving the PDSCH of the group common SPS in slot #n+6.

[0073] In one embodiment, determining the type based on the RNTI scrambled with the DCI includes:

[0074] In response to the RNTI of the scrambled DCI being a first RNTI, determine to reactivate group common SPS; and / or in response to the RNTI of the scrambled DCI being a second RNTI, determine to reactivate UE-specific SPS.

[0075] The terminal can pre-store the correspondence between RNTI and SPS types, such as the one agreed upon by the protocol or pre-configured by the network-side equipment. In this correspondence, the first RNTI corresponds to group common SPS and the second RNTI corresponds to UE-specific SPS.

[0076] The first RNTI and / or the second RNTI may be different from the RNTI in the related art, or may reuse the RNTI in the related art, and can be selected according to the needs.

[0077] In one embodiment, the first RNTI is different from the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS, and / or different from the CS-RNTI (Configured Scheduled-Radio Network Temporary Identity) used to scramble the DCI for initial deactivation of UE-specific SPS.

[0078] The DCI for initial deactivation of group common SPS is in the CSS (Common Search Space), and the information transmitted in the CSS can be received by multiple terminals; the DCI for initial deactivation of UE-specific SPS is in the USS, and the information transmitted in the USS is generally only received by the specified terminal.

[0079] However, in some cases, there may be partial overlap between the CSS and USS. If the DCI used to deactivate the SPS transmitted in the USS happens to be located in this overlapping part, it will cause multiple terminals to receive the DCI used to deactivate the SPS transmitted in the USS. If the RNTI scrambling the DCI used to deactivate the SPS transmitted in the USS is the same as the CS-RNTI used to scramble the DCI used to initially deactivate the UE-specific SPS, or the same as the GS-RNTI used to scramble the DCI used to initially deactivate the group common SPS, it may cause other terminals to receive the DCI used to deactivate the SPS transmitted in the USS and also deactivate the corresponding SPS based on the RNTI determined by successful decoding, resulting in other terminals erroneously deactivating the SPS.

[0080] Therefore, based on this embodiment, a new RNTI can be introduced as the first RNTI, which is different from the GS-RNTI that scrambles the DCI for initial deactivation of group common SPS and the CS-RNTI that scrambles the DCI for initial deactivation of UE-specific SPS, thereby avoiding other terminals from erroneously deactivating SPS.

[0081] In one embodiment, the first RNTI is the same as the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS.

[0082] Although introducing a new RNTI as the first RNTI can prevent other terminals from erroneously activating SPS, the adjustment to the communication architecture is relatively large. Moreover, the erroneous activation of SPS generally only occurs when there is some overlap between CSS and USS, which is not very common.

[0083] Therefore, this embodiment can also reuse the GS-RNTI that scrambles the DCI used for the initial deactivation of the group common SPS to scramble the DCI transmitted in the USS for deactivating the SPS. After the terminal receives the DCI transmitted in the USS for deactivating the SPS, it can determine that the RNTI used to scramble the DCI is the GS-RNTI, and thus determine that the network-side device needs to instruct the reactivation of the group common SPS. This helps to reduce modifications to the communication architecture.

[0084] Figure 5 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure. Figure 5 As shown, the type of semi-static scheduling to be reactivated based on the instructions of the network-side device includes:

[0085] In step S501, in response to supporting the reception of DCI for deactivating group common SPS in USS, when DCI scrambled by CS-RNTI is received in USS, it is determined to reactivate group common SPS.

[0086] In one embodiment, the protocol can pre-define that when the terminal receives a DCI scrambled by CS-RNTI in the USS, the network-side device will instruct the terminal to reactivate the group common SPS if the terminal supports receiving the DCI for deactivating the group common SPS in the USS.

[0087] When the terminal itself supports receiving DCI for deactivating group common SPS in the USS, if it receives DCI scrambled by CS-RNTI in the USS, it can be assumed that the network-side device instructs the terminal to reactivate group common SPS, thereby reactivating group common SPS, rather than interpreting it as the network-side device instructing the terminal to reactivate UE-specific SPS.

[0088] In one embodiment, the terminal is configured with group common SPS and not with UE-specific SPS.

[0089] When a terminal receives DCI scrambled by CS-RNTI in the USS, it does not consider the network-side device to instruct the terminal to reactivate the UE-specific SPS. In other words, it will not reactivate the UE-specific SPS. This can lead to the inability to successfully reactivate the UE-specific SPS even if the terminal is configured with the UE-specific SPS. Therefore, in this case, the network-side device can choose to configure only the group common SPS for the terminal instead of configuring the UE-specific SPS for the terminal, thereby reducing resource waste.

[0090] Of course, network-side devices can also configure both group common SPS and UE-specific SPS for the terminal, depending on actual needs.

[0091] In one embodiment, determining the type of semi-static scheduling to be reactivated based on the indication from the network-side device includes:

[0092] In response to supporting the reception of a DCI for deactivating group common SPS in a preset USS, when a DCI scrambled by CS-RNTI is received in the preset USS, it is determined to reactivate group common SPS.

[0093] In one embodiment, the protocol can pre-define that when the terminal supports receiving DCI for deactivating group common SPS in a preset USS, the terminal receives DCI scrambled by CS-RNTI in the preset USS, and the network-side device instructs the terminal to reactivate group common SPS by default.

[0094] When the terminal itself supports receiving DCI for deactivating group common SPS in the preset USS, if it receives DCI scrambled by CS-RNTI in the preset USS, it can be assumed that the network-side device instructs the terminal to reactivate group common SPS, and thus reactivate group common SPS, rather than considering that the network-side device instructs the terminal to reactivate UE-specific SPS.

[0095] When DCI scrambled by CS-RNTI is received in a USS other than the preset USS, it can be considered that the network-side device instructs the terminal to reactivate the UE-specific SPS, thereby reactivating the UE-specific SPS. Figure 5The difference between the embodiments shown is that this embodiment only instructs the terminal to reactivate group common SPS by default for DCI scrambled by CS-RNTI transmitted in the preset USS. For DCI scrambled by CS-RNTI transmitted in other USS, the terminal does not instruct to reactivate group common SPS by default.

[0096] Figure 6 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure. Figure 6 As shown, the terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resources, and the determination of the type of semi-static scheduling for re-deactivation according to the instructions of the network-side device includes:

[0097] In step S601, the type is determined based on the RNTI of the DCI transmitted by the scrambling network-side device on the second frequency domain resource.

[0098] It should be noted that the DCI may be located in the USS of the terminal. However, if the second frequency domain resources are exclusively allocated to the terminal, the DCI may or may not be located in the USS of the terminal.

[0099] In one embodiment, the group common SPS and / or UE-specific SPS configured by the network-side device for the terminal may be configured for a first frequency domain resource. In this case, the network-side device may transmit a DCI scrambled by RNTI on a second frequency domain resource to indicate the type of SPS that the terminal needs to reactivate.

[0100] Of course, network-side devices can also transmit DCI scrambled by RNTI on the first frequency domain resources to indicate the type of SPS that the terminal needs to reactivate. The specific type can be selected by the network-side device as needed.

[0101] In one embodiment, the first frequency domain resource includes a first component carrier (CC), and the second frequency domain resource includes a second CC; and / or the first frequency domain resource includes a first bandwidth portion (BWP), and the second frequency domain resource includes a second BWP.

[0102] Figure 7 This is a temporal schematic diagram illustrating another reactivation according to an embodiment of the present disclosure.

[0103] like Figure 7As shown, for example, if the network-side device configures group common SPS and UE-specific SPS for the terminal on the first CC, and the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to deactivate group common SPS in slot #n, the network-side device can send a UE-specific PDCCH (carrying a DCI scrambled with RNTI) to the terminal on the second CC, for example, in slot #n+5, to instruct the terminal to reactivate group common SPS on the first CC. After the terminal reactivates group common SPS, it can stop communicating with the network-side device according to the configuration of group common SPS, for example, it can stop receiving the PDSCH of group common SPS in slot #n+6.

[0104] For example, if the network-side device configures group common SPS and UE-specific SPS for the terminal on the first BWP, the network-side device can send a DCI scrambled by RNTI to the terminal in the USS on the second BWP to instruct the terminal to reactivate either group common SPS or UE-specific SPS.

[0105] It should be noted that in this embodiment, the DCI format can be DCI format 1_1 or DCI format 1_2. Since these two DCI formats can carry information about the frequency domain, it is convenient to indicate the frequency domain resources where the SPS to be deactivated is located, such as indicating the CC, BWP, etc. where the SPS to be deactivated is located.

[0106] Figure 8 This is a schematic flowchart illustrating another semi-static scheduling reactivation determination method according to embodiments of the present disclosure. Figure 8 As shown, the type of semi-static scheduling to be reactivated based on the instructions of the network-side device includes:

[0107] In step S801, the DCI for deactivating the SPS transmitted in the USS is received;

[0108] In step S802, the type is determined based on the identifier of the USS where the DCI is located.

[0109] In one embodiment, the terminal may pre-store the correspondence between the USS identifier (e.g., ID) and the SPS type, such as as agreed by the protocol or pre-configured by the network-side device.

[0110] After receiving the DCI used to deactivate the SPS in the USS, the terminal can determine the identifier of the USS where the DCI is located, and then identify the type of the corresponding SPS based on the correspondence between the identifier and the type of SPS.

[0111] Figure 9 This is a temporal schematic diagram illustrating another reactivation according to an embodiment of the present disclosure.

[0112] like Figure 9 As shown, for example, the network-side equipment configures at least two USS identifiers for the terminal, namely USS#1 and USS#2. In the correspondence between USS identifiers and SPS types pre-stored by the terminal, USS#1 corresponds to UE-specific SPS, and USS#2 corresponds to group common SPS.

[0113] If the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to deactivate the group common SPS in slot #n, the network-side device can send a UE-specific PDCCH to the terminal in slot #n+5. The DCI scrambled with the RNTI carried in this PDCCH is located in the USS corresponding to USS #2. Upon receiving the DCI carried in the UE-specific PDCCH transmitted in slot #n+5, the terminal can determine that the DCI is in the USS corresponding to USS #2, and thus determine that USS #2 corresponds to the group common SPS. This allows the terminal to deactivate the group common SPS and subsequently stop receiving downlink information from the PDSCH corresponding to the group common SPS (e.g., located in slot #n+6).

[0114] Alternatively, the terminal can also send a UE-specific PDCCH to the terminal in the USS corresponding to USS#1 as needed. For example, a UE-specific PDCCH can be sent to the terminal in slot#n+4. When the terminal receives the DCI carried by the UE-specific PDCCH transmitted in slot#n+4, it can determine that the DCI is in the USS corresponding to USS#1. In this way, it can determine that USS#1 corresponds to the UE-specific SPS, thereby deactivating the UE-specific SPS. Subsequently, it can stop receiving downlink information in the PDSCH corresponding to the UE-specific SPS (e.g., located in slot#n+7).

[0115] In the above embodiments, the network-side device instructs the terminal to activate which SPS primarily through implicit indication. That is, the DCI is not directly used to indicate the type of SPS the terminal needs to activate, but rather through an RNTI that scrambles the DCI. The following embodiments mainly focus on explicit indication methods, providing illustrative examples of the technical solutions disclosed herein.

[0116] In one embodiment, determining the type of semi-static scheduling to be reactivated based on the indication from the network-side device includes:

[0117] The type is determined based on the indication information sent by the network-side device.

[0118] In one embodiment, the indication information includes at least one of the following: Media Access Control Layer Control Element (MACCE); Radio Access Control (RRC) signaling; DCI.

[0119] In one embodiment, the network-side device can explicitly indicate to the terminal the type of SPS that needs to be deactivated, for example, by sending one or more indication messages to the terminal. The content carried in these indication messages directly indicates the type. The indication messages can be sent in the form of MAC CE, RRC signaling, or DCI, depending on the specific requirements.

[0120] In one embodiment, the indication information includes DCI, and determining the type based on the indication information sent by the network-side device includes:

[0121] The type is determined based on information fields other than the verification field in the DCI.

[0122] In one embodiment, when the network-side device instructs the terminal to activate a specific type of SPS via the DCI, such as activating a group common SPS or a UE-specific SPS, it can use some information fields in the DCI for indication. However, regarding the validation field in the DCI, since the bits in the validation field are used for authentication, changing them can cause a series of problems. Therefore, in this embodiment, when instructing the terminal to activate a specific type of SPS via the DCI, the indication is made through information fields other than the validation field. Accordingly, after receiving the DCI, the terminal can determine the type of SPS to be activated based on the information fields other than the validation field in the DCI, so as to avoid causing problems due to changes in the bits in the validation field.

[0123] In one embodiment, determining the type based on information fields other than the verification field in the DCI includes:

[0124] The type is determined based on the Hybrid Automatic Repeat Request Process Number (HPN) field in the DCI.

[0125] In one embodiment, the terminal is configured with multiple SPS configurations of the aforementioned type, and the method further includes:

[0126] Based on the value corresponding to the HPN field, determine the target SPS configuration among the multiple SPS configurations of the aforementioned type to be deactivated.

[0127] In one embodiment, the network-side device indicates the type via an information field other than the verification field in the DCI.

[0128] For example, the type can be indicated by the HPN field in the DCI. Accordingly, after receiving the DCI, the terminal can determine the type of the deactivated SPS based on the HPN field in the DCI.

[0129] It should be noted that the HPN domain can also be used as an authentication domain in some cases (such as when only one SPS configuration is configured for the terminal). The network-side device only indicates the type through the HPN domain when the HPN domain is not used as an authentication domain. For example, it indicates the type through 1 bit. When the value is 1, the type indicated is group common SPS. When the value is 0, the type indicated is UE-specific SPS.

[0130] In addition, some information fields in DCI, such as FDRA (Frequency Domain Resource Assignment), RV (Redundancy Version), and MCS (Modulation and Coding Scheme), can also be used as verification fields in some cases. When the terminal indicates the type through these information fields, the type should only be indicated through the HPN field if these information fields are not used as verification fields.

[0131] In one embodiment, the type of SPS to be deactivated can be determined based on the information fields other than the verification field in the DCI. The information fields other than the verification field in the DCI are the information fields other than the FDRA, RV, MCS, and HPN information fields in the non-verification field of the DCI. For example, 1 bit can be used to indicate the type of SPS to be deactivated, 0 indicates that it is used to deactivate UE-specific SPS, and 1 indicates that it is used to deactivate group common SPS.

[0132] In one embodiment, for a certain type of SPS, the terminal may have multiple SPS configurations (e.g., each SPS configuration may have different parameters, such as different periods). These multiple SPS configurations may be configured by network-side devices or determined based on protocol agreements.

[0133] When a terminal has multiple SPS configurations of the aforementioned type, the network-side device, while instructing the terminal to activate the type of SPS through the HPN domain, can further instruct the terminal to specifically activate which SPS configuration of the aforementioned type. For example, the SPS configuration to be activated is called the target SPS configuration.

[0134] The network-side devices and terminals can each store the association between the values ​​corresponding to the HPN field and the SPS configuration. When the network-side device activates a specific SPS configuration using the value corresponding to the HPN field, the terminal can determine the SPS configuration corresponding to that value based on the association and then activate that SPS configuration. This allows for the specific deactivation of a particular SPS configuration, improving the accuracy of SPS deactivation.

[0135] For example, the HPN field is 4 bits and can indicate values ​​from 0 to 15. For instance, if the terminal has 8 sets of UE-specific SPS type SPS configurations with indices from 0 to 7, the first association between the value corresponding to the HPN field and the UE-specific SPS type SPS configuration includes: value 0 associated with index 0, value 1 associated with index 1, value 2 associated with index 2, value 3 associated with index 3, value 4 associated with index 4, value 5 associated with index 5, value 6 associated with index 6, and value 7 associated with index 7.

[0136] When a network-side device needs to deactivate a UE-specific SPS type SPS, it can indicate this by using the HPN field value from 0 to 7. For example, if it needs to activate the SPS configuration corresponding to index 1, the HPN field value in the sent DCI can be 1. After receiving the DCI, the terminal determines that the HPN field value is 1. Based on the first association relationship, it can determine that the corresponding index is 1, thereby deactivating the SPS configuration corresponding to index 1 in the UE-specific SPS type.

[0137] In one embodiment, a terminal can be configured with any one or more types of SPS. For example, a terminal may be configured with multiple types of SPS and have multiple SPS configurations in each type of SPS. The network-side device can activate one SPS configuration in one type of multiple SPS through the HPN domain, or it can activate one SPS configuration in another type of multiple SPS through the HPN domain.

[0138] For example, in the above embodiment, the terminal has 8 sets of UE-specific SPS type SPS configurations, and the network-side device can activate any one of these 8 SPS configurations by indicating the value 0 to 7 corresponding to the HPN field.

[0139] Based on this, the terminal can also have (e.g., network-side configuration or determined based on protocol agreement) 8 sets of SPS configurations of the group common SPS type, with indices 0 to 7 respectively; the second association between the value corresponding to the HPN field and the SPS configuration of the group common SPS type includes: value 8 associated with index 0, value 9 associated with index 1, value 10 associated with index 2, value 11 associated with index 3, value 12 associated with index 4, value 13 associated with index 5, value 14 associated with index 6, and value 15 associated with index 7.

[0140] When a network-side device needs to deactivate an SPS of the group common SPS type, it can indicate this by setting the value of the HPN field to 8 to 15. For example, if it needs to activate the SPS configuration corresponding to index 3, the value of the HPN field in the sent DCI can be 10. After the terminal receives the DCI, it determines that the value of the HPN field is 1. Based on the second association relationship, it can determine that the corresponding index is 2, thereby deactivating the SPS configuration corresponding to index 2 in the group common SPS type.

[0141] In one embodiment, the terminal can determine which SPS configuration of type group common SPS to activate based on the formula mod(HPN value, M), where HPN value represents the value corresponding to the HPN field, M represents the number of SPS configurations of type group common SPS, and mod represents the modulo operation. Specifically, the terminal only determines which SPS configuration of type group common SPS to activate based on this formula when HPN value is greater than or equal to 8.

[0142] For example, when M=8, when the network-side device needs to deactivate the SPS configuration corresponding to index 3, the HPN value in the sent DCI can be 10. The terminal substitutes HPN value=10 and M=8 into the above formula to calculate mod(10,8) and the value obtained is 2. It can be determined that the SPS configuration corresponding to index 2 in the group common SPS type will be deactivated.

[0143] It should be noted that the number of UE-specific SPS type SPS configurations and the number of groupcommon SPS type SPS configurations that the terminal has are not limited to the 8 sets described in the above embodiments, and can be set as needed.

[0144] In one embodiment, the range of HPN values ​​used to indicate the group common SPS type can be determined based on the number of SPS configurations of both UE-specific SPS and group common SPS types. For example, if the network side is configured with 4 UE-specific SPS type SPS configurations and 4 group common SPS type SPS configurations, then HPN values ​​0-3 are used to indicate the deactivation of the UE-specific SPS index, and HPN values ​​4-7 are used to indicate the deactivation of the group common SPS index.

[0145] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes:

[0146] In response to determining that the network-side device has activated one type of SPS, namely the group common SPS and the UE-specific SPS, it is not expected that the network-side device will activate the other type of SPS, namely the group common SPS and the UE-specific SPS, through CS-RNTI scrambled DCI.

[0147] In one embodiment, when the terminal is configured with both group common SPS and UE-specific SPS, since the terminal generally cannot use both types of SPS simultaneously, the terminal does not expect the network-side device to activate the other type of SPS through CS-RNTI scrambled DCI when one type of SPS has already been activated by the network-side device.

[0148] For example, if the network-side device has already activated group common SPS, the terminal does not expect the network-side device to activate UE-specific SPS through DCI scrambled by CS-RNTI; for example, if the network-side device has already activated UE-specific SPS, the terminal does not expect the network-side device to activate group common SPS through DCI scrambled by CS-RNTI.

[0149] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes:

[0150] In response to determining that the network-side device has activated one type of SPS, namely the group common SPS and the UE-specific SPS, it is not expected that the network-side device will activate the other type of SPS, namely the group common SPS and the UE-specific SPS, through CS-RNTI scrambled DCI.

[0151] In one embodiment, when the terminal is configured with both group common SPS and UE-specific SPS, the terminal generally cannot use both types of SPS simultaneously. Therefore, if the network-side device has activated one type of SPS, the other type of SPS will generally not be activated. Thus, the terminal does not expect the network-side device to activate the other type of SPS through CS-RNTI scrambled DCI.

[0152] For example, when the network-side device has already activated group common SPS, the terminal does not expect the network-side device to activate UE-specific SPS through DCI scrambled by CS-RNTI. In other words, in this case, when the terminal receives DCI scrambled by CS-RNTI, it will activate group common SPS by default according to DCI scrambled by CS-RNTI.

[0153] For example, when the network-side device has already activated UE-specific SPS, the terminal does not expect the network-side device to activate group common SPS through DCI scrambled by CS-RNTI. In other words, in this case, when the terminal receives DCI scrambled by CS-RNTI, it will activate UE-specific SPS by default according to DCI scrambled by CS-RNTI.

[0154] Figure 10This is a schematic flowchart illustrating a semi-static scheduling reactivation method according to an embodiment of this disclosure. The semi-static scheduling reactivation method shown in this embodiment can be executed by a network-side device, which can communicate with a terminal. The terminal includes, but is not limited to, communication devices such as mobile phones, tablets, wearable devices, sensors, and IoT devices. The network-side device includes, but is not limited to, network-side devices in 4G, 5G, and 6G communication systems, such as base stations and core networks.

[0155] In one embodiment, the network-side device can configure one or more SPS configurations for the terminal. When a certain SPS needs to be used, the device can instruct the terminal to activate one of the SPSs and receive downlink information according to the configuration of the activated SPS.

[0156] Subsequently, the network-side device can also instruct the terminal to activate the SPS as needed. After activating the SPS according to the network-side device's instruction, the terminal stops receiving downlink transmissions according to the SPS configuration. However, in some cases, some terminals may fail to correctly decode the instruction sent by the network-side device, resulting in an inability to correctly determine the SPS that needs to be deactivated. The network-side device can determine whether the terminal has correctly decoded the instruction based on the information fed back by the terminal. If it is determined that the terminal has not correctly decoded the instruction, the network-side device can instruct the destination again to reactivate the SPS.

[0157] The network-side equipment can configure various types of SPS for the terminal. The following embodiments mainly focus on the configuration of group common SPS and UE-specific SPS for the terminal by the network-side equipment, and provide an exemplary description of the technical solution of this disclosure.

[0158] For group common SPS, during initial deactivation, downlink control information (DCI) scrambled with the group scheduled-radio network temporary identity (GS-RNTI) can be transmitted in the group common physical downlink control channel (PDCCH) to indicate deactivation. After receiving the indication, the terminal can decode the DCI and determine the RNTI used for decoding. Then, based on the RNTI (specifically, the RNTI value), the SPS that needs to be deactivated is the group common SPS.

[0159] It should be noted that the scrambling of DCI described in all embodiments of this disclosure can specifically be a cyclic redundancy check (CRC) of scrambling DCI, which is referred to as scrambling of DCI in this disclosure.

[0160] The terminal may be a terminal that supports MBS (Multicast Broadcast service), and the terminal may also support unicast services.

[0161] The aforementioned group common SPS can be configured for terminals in the same group. However, since different terminals in the same group may have different channel transmission conditions, some terminals may be able to correctly demodulate and determine the RNTI, while others may not. Terminals that correctly demodulate and determine the RNTI can return an ACK to the network-side device, while terminals that fail to correctly demodulate and determine the RNTI can return an NACK to the network-side device. The network-side device can determine which terminals failed to correctly demodulate and determine the RNTI based on the received feedback.

[0162] For terminals that have not correctly demodulated and determined their RNTI, network-side equipment can re-instruct the terminal to reactivate the group common SPS. Currently, one method for re-instructing the terminal is through the UE-specific physical downlink control channel (PDCCH). However, the UE-specific PDCCH is primarily used to deactivate UE-specific semi-static scheduling SPS. When using the UE-specific PDCCH to deactivate group common SPS, the terminal has difficulty distinguishing which type of SPS the UE-specific PDCCH is deactivating.

[0163] like Figure 10 As shown, the semi-static scheduling reactivation method may include the following steps:

[0164] In step S1001, the type of semi-static scheduling (SPS) for which the terminal is expected to be reactivated is determined;

[0165] In step S1002, the terminal is instructed to determine the type.

[0166] In one embodiment, when instructing a terminal to reactivate an SPS, the network-side device can determine the type of semi-static scheduling SPS that the terminal is expected to reactivate as needed, and then instruct the terminal to reactivate the type of SPS. Accordingly, the terminal can accurately determine the type of SPS that needs to be reactivated, and then reactivate the corresponding type of SPS, and stop communicating with the network-side device through the configuration of the reactivated SPS, such as stopping receiving downlink information, to avoid reactivating the wrong type of SPS and affecting the communication effect.

[0167] In one embodiment, the type includes at least one of the following: group common SPS; UE-specific SPS.

[0168] The network-side device can instruct the terminal to reactivate either the group common SPS or the UE-specific SPS. When the terminal determines to reactivate the group common SPS according to the instruction, it can reactivate the group common SPS and stop communicating with the network-side device according to the configuration of the group common SPS; when the terminal determines to reactivate the UE-specific SPS according to the instruction, it can reactivate the UE-specific SPS and stop communicating with the network-side device according to the configuration of the UE-specific SPS.

[0169] In one embodiment, the indication of the network-side device includes at least one of the following:

[0170] Explicit instructions and implicit instructions.

[0171] The network-side device can instruct the terminal in two ways: explicit instruction, such as sending one or more messages to the terminal, the content of which directly indicates the type; or implicit instruction, such as sending messages to the terminal that have other functions and are not directly used to indicate the type. The terminal can determine the type of SPS that needs to be reactivated based on the information in some way. For example, the information may be a DCI in the User-Specific Search Space (USS), which is scrambled by RNTI. This DCI is not used to indicate the type, but the terminal can determine the type based on the RNTI of the scrambled DCI.

[0172] like Figure 2As shown, for example, for terminals that support MBS, the network-side equipment must at least configure a group common SPS for the terminal, where the group common SPS is surrounded by 5 time slots, for example... Figure 2 In the groupcommon SPS, the Physical Downlink Shared Channel (PDSCH) is located in slot #n+1, and the next one is located in slot #n+6, with an interval of 5 slots.

[0173] The network-side device performs initial deactivation of the group common SPS in slot #n. For example, it sends the group common PDCCH to terminals belonging to the same group in slot #n. The DCI in the group common PDCCH is scrambled using GS-RNTI. If the terminal correctly demodulates and determines the RNTI corresponding to the DCI, it can stop communicating with the network-side device according to the configuration of the group common PDCCH. For example, it can stop receiving the PDSCH of the group common SPS in slots #n+1 and #n+6.

[0174] The network-side device can determine whether the terminal has correctly demodulated and determined the RNTI corresponding to the DCI based on the information fed back by each terminal. For example, if the terminal returns an ACK confirmation message, the network-side device determines that the terminal has correctly demodulated and determined the RNTI. If the terminal returns an NACK unacknowledged message, the network-side device determines that the terminal has not correctly demodulated and determined the RNTI.

[0175] In addition, if the network-side equipment also configures the terminal with UE-specific SPS, it can transmit DCI scrambled by CS-RNTI in the USS for reactivation.

[0176] Figure 11 This is a schematic flowchart illustrating another semi-static scheduling reactivation method according to embodiments of the present disclosure. Figure 11 As shown, instructing the terminal to determine the type includes:

[0177] In step S1101, a Radio Network Temporary Identifier (RNTI) for scrambling the Downlink Control Information (DCI) used to deactivate the SPS in the User Equipment Dedicated Search Space (USS) is determined according to the type.

[0178] In step S1102, the DCI is scrambled using the determined RNTI;

[0179] In step S1103, the USS transmits the DCI to the terminal so that the terminal determines the type based on the RNTI of the scrambled DCI.

[0180] It should be noted that the terminal can determine whether a DCI is used to deactivate SPS through an agreed-upon method, and the determination criteria include at least one of the following:

[0181] The CRC of DCI is scrambled by CS-RNTI or by GS-RNTI;

[0182] The NDI (New data indicator) field in DCI is 0;

[0183] If a DFI exists in a DCI, the DFI field (DCI format indicator) is 0;

[0184] The DCI includes a PDSCH to HARQ (Hybrid Automatic Repeat reQuest) feedback timing indication field, which is used to indicate the availability of uplink subframes.

[0185] After making the above judgment, the terminal can further determine whether the validation field in the DCI meets the deactivation conditions. If the deactivation conditions are met, the terminal will determine how to receive the PDSCH of the SPS based on the higher-level configuration information corresponding to the configuration of the SPS to be deactivated and the dynamic scheduling information in the DCI.

[0186] In one embodiment, the network-side device may transmit a DCI for deactivating the SPS in the USS, for example, the DCI carried in the UE-specific PDCCH, to instruct the terminal that has not correctly demodulated and determined the RNTI to reactivate the group common SPS.

[0187] The terminal can pre-store the correspondence between RNTIs and SPS types, such as those agreed upon by the protocol or pre-configured by the network-side device. After receiving the DCI used to deactivate the SPS from the USS, the terminal can determine the RNTI that scrambled the DCI. For example, it can descramble the DCI using the RNTI. The RNTI that successfully descrambled the DCI corresponds to the RNTI that scrambled the DCI. Therefore, the RNTI that scrambled the DCI can be determined based on the RNTI that successfully descrambled the DCI. Furthermore, based on the RNTI that scrambled the DCI and the correspondence, the type of SPS corresponding to the RNTI that scrambled the DCI can be determined.

[0188] like Figure 4As shown, if the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to deactivate the group common SPS in slot #n, the network-side device can send a UE-specific PDCCH (carrying a DCI scrambled with the RNTI) to the terminal, for example, in slot #n+5, to instruct the terminal to reactivate the group common SPS. After the terminal reactivates the group common SPS, it can stop communicating with the network-side device according to the configuration of the group common SPS, and can stop receiving the PDSCH of the group common SPS in slot #n+6.

[0189] In one embodiment, determining the RNTI for DCI scrambling in the USS according to the type includes:

[0190] In response to the expectation that the terminal will reactivate the group common SPS, the DCI is scrambled by a first RNTI; and / or in response to the expectation that the terminal will reactivate the UE-specific SPS, the DCI is scrambled by a second RNTI.

[0191] The network-side equipment and the terminal can pre-store the correspondence between RNTI and SPS types. In this correspondence, the first RNTI corresponds to group common SPS, and the second RNTI corresponds to UE-specific SPS. When the network-side equipment needs to instruct the terminal to reactivate group common SPS, it can scramble the DCI using the first RNTI. When it needs to instruct the terminal to reactivate UE-specific SPS, it can scramble the DCI using the second RNTI.

[0192] The first RNTI and / or the second RNTI may be different from the RNTI in the related art, or may reuse the RNTI in the related art, and can be selected according to the needs.

[0193] In one embodiment, the first RNTI is different from the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS, and / or different from the CS-RNTI used to scramble the DCI for initial deactivation of UE-specific SPS.

[0194] The DCI for initial deactivation of group common SPS is in the CSS (Common Search Space), and the information transmitted in the CSS can be received by multiple terminals; the DCI for initial deactivation of UE-specific SPS is in the USS, and the information transmitted in the USS is generally only received by the specified terminal.

[0195] However, in some cases, there may be partial overlap between the CSS and USS. If the DCI used to deactivate the SPS transmitted in the USS happens to be located in this overlapping part, it will cause the DCI used to deactivate the SPS transmitted in the USS to be received by multiple terminals. If the RNTI scrambling the DCI used to deactivate the SPS transmitted in the USS is the same as the CS-RNTI used to scramble the DCI used to initially deactivate the UE-specific SPS, or the same as the GS-RNTI used to scramble the DCI used to initially deactivate the group common SPS, it may cause other terminals to receive the DCI used to deactivate the SPS transmitted in the USS and also deactivate the corresponding SPS based on the RNTI determined by successful decoding, resulting in other terminals erroneously deactivating the SPS.

[0196] Therefore, based on this embodiment, a new RNTI can be introduced as the first RNTI, which is different from the GS-RNTI that scrambles the DCI for initial deactivation of group common SPS and the CS-RNTI that scrambles the DCI for initial deactivation of UE-specific SPS, thereby avoiding other terminals from erroneously deactivating SPS.

[0197] In one embodiment, the first RNTI is the same as the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS.

[0198] Although introducing a new RNTI as the first RNTI can prevent other terminals from erroneously activating SPS, the adjustment to the communication architecture is relatively large. Moreover, the erroneous activation of SPS generally only occurs when there is some overlap between CSS and USS, which is not very common.

[0199] Therefore, this embodiment can also reuse the GS-RNTI that scrambles the DCI used for the initial deactivation of the group common SPS to scramble the DCI transmitted in the USS for deactivating the SPS. After the terminal receives the DCI transmitted in the USS for deactivating the SPS, it can determine that the RNTI used to scramble the DCI is the GS-RNTI, and thus determine that the network-side device needs to instruct the reactivation of the group common SPS. This helps to reduce modifications to the communication architecture.

[0200] Figure 12 This is a schematic flowchart illustrating yet another semi-static scheduling reactivation method according to embodiments of the present disclosure. Figure 12 As shown, instructing the terminal to determine the type includes:

[0201] In step S1201, in response to determining that the terminal supports receiving DCI for deactivating group common SPS in the USS, and expecting the terminal to reactivate group common SPS, DCI transmitted in the USS is scrambled by CS-RNTI.

[0202] In step S1202, the USS transmits the DCI to the terminal so that the terminal determines to reactivate the group common SPS based on the CS-RNTI of the scrambled DCI.

[0203] In one embodiment, the protocol can pre-define that when the terminal receives a DCI scrambled by CS-RNTI in the USS, the network-side device will instruct the terminal to reactivate the group common SPS if the terminal supports receiving the DCI for deactivating the group common SPS in the USS.

[0204] When it is determined that the terminal itself supports receiving DCI for deactivating group common SPS in the USS, if the terminal needs to reactivate group common SPS, it can receive DCI scrambled by CS-RNTI in the USS. After receiving DCI scrambled by CS-RNTI in the USS, the terminal can assume that the network-side device instructs the terminal to reactivate group common SPS, and thus reactivate group common SPS, instead of thinking that the network-side device instructs the terminal to reactivate UE-specific SPS.

[0205] In one embodiment, the terminal is configured with group common SPS and not with UE-specific SPS.

[0206] When a terminal receives DCI scrambled by CS-RNTI in the USS, it does not consider the network-side device to instruct the terminal to reactivate the UE-specific SPS. In other words, it will not reactivate the UE-specific SPS. This can lead to the inability to successfully reactivate the UE-specific SPS even if the terminal is configured with the UE-specific SPS. Therefore, in this case, the network-side device can choose to configure only the group common SPS for the terminal instead of configuring the UE-specific SPS for the terminal, thereby reducing resource waste.

[0207] Of course, network-side devices can also configure both group common SPS and UE-specific SPS for the terminal, depending on actual needs.

[0208] In one embodiment, instructing the terminal to determine the type includes:

[0209] In response to determining that the terminal supports receiving DCI for deactivating group common SPS in a preset USS, and expecting the terminal to reactivate group common SPS, the DCI transmitted in the preset USS is scrambled by CS-RNTI.

[0210] The preset USS transmits the DCI to the terminal so that the terminal can determine to reactivate the group common SPS based on the CS-RNTI of the scrambled DCI.

[0211] In one embodiment, the protocol can pre-define that when the terminal supports receiving DCI for deactivating group common SPS in a preset USS, the terminal receives DCI scrambled by CS-RNTI in the preset USS, and the network-side device instructs the terminal to reactivate group common SPS by default.

[0212] When the terminal itself supports receiving DCI for deactivating group common SPS in the preset USS, if it receives DCI scrambled by CS-RNTI in the preset USS, it can be assumed that the network-side device instructs the terminal to reactivate group common SPS, and thus reactivate group common SPS, rather than considering that the network-side device instructs the terminal to reactivate UE-specific SPS.

[0213] When DCI scrambled by CS-RNTI is received in a USS other than the preset USS, it can be considered that the network-side device instructs the terminal to reactivate the UE-specific SPS, thereby reactivating the gUE-specific SPS. Figure 12 The difference between the embodiments shown is that this embodiment only instructs the terminal to reactivate group common SPS by default for DCI scrambled by CS-RNTI transmitted in the preset USS. For DCI scrambled by CS-RNTI transmitted in other USS, the terminal does not instruct to reactivate group common SPS by default.

[0214] Figure 13 This is a schematic flowchart illustrating yet another semi-static scheduling reactivation method according to embodiments of the present disclosure. Figure 13 As shown, the terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resources, and instructing the terminal to determine the type includes:

[0215] In step S1301, the RNTI for scrambling the DCI transmitted on the second frequency domain resource is determined according to the type;

[0216] In step S1302, the DCI is scrambled using the determined RNTI;

[0217] In step S1303, the DCI is transmitted to the terminal on the second frequency domain resource so that the terminal determines the type based on the RNTI of the scrambled DCI.

[0218] It should be noted that the DCI may be located in the USS of the terminal. However, if the second frequency domain resources are exclusively allocated to the terminal, the DCI may or may not be located in the USS of the terminal.

[0219] In one embodiment, the group common SPS and / or UE-specific SPS configured by the network-side device for the terminal may be configured for a first frequency domain resource. In this case, the network-side device may transmit a DCI scrambled by RNTI on a second frequency domain resource to indicate the type of SPS that the terminal needs to reactivate.

[0220] Of course, network-side devices can also transmit DCI scrambled by RNTI on the first frequency domain resources to indicate the type of SPS that the terminal needs to reactivate. The specific type can be selected by the network-side device as needed.

[0221] In one embodiment, the first frequency domain resource includes a first component carrier (CC), and the second frequency domain resource includes a second CC; and / or the first frequency domain resource includes a first bandwidth portion (BWP), and the second frequency domain resource includes a second BWP.

[0222] like Figure 7 As shown, for example, if the network-side device configures group common SPS and UE-specific SPS for the terminal on the first CC, and the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to deactivate group common SPS in slot #n, the network-side device can send a UE-specific PDCCH (carrying a DCI scrambled with RNTI) to the terminal on the second CC, for example, in slot #n+5, to instruct the terminal to reactivate group common SPS on the first CC. After the terminal reactivates group common SPS, it can stop communicating with the network-side device according to the configuration of group common SPS, for example, it can stop receiving the PDSCH of group common SPS in slot #n+6.

[0223] For example, if the network-side device configures group common SPS and UE-specific SPS for the terminal on the first BWP, the network-side device can send a DCI scrambled by RNTI to the terminal in the USS on the second BWP to instruct the terminal to reactivate either group common SPS or UE-specific SPS.

[0224] It should be noted that in this embodiment, the DCI format can be DCI format 1_1 or DCI format 1_2. Since these two DCI formats can carry information about the frequency domain, it is convenient to indicate the frequency domain resources where the SPS to be deactivated is located, such as indicating the CC, BWP, etc. where the SPS to be deactivated is located.

[0225] Figure 14 This is a schematic flowchart illustrating yet another semi-static scheduling reactivation method according to embodiments of the present disclosure. Figure 14 As shown, instructing the terminal to determine the type includes:

[0226] In step S1401, the identifier of the USS is determined according to the type;

[0227] In step S1402, the USS corresponding to the identifier transmits a DCI scrambled by CS-RNTI to the terminal, so that the terminal determines the type based on the identifier of the USS where the DCI is located.

[0228] In one embodiment, the network-side device and the terminal may pre-store the mapping between USS identifiers (e.g., IDs) and SPS types. The network-side device can first determine the type of SPS that the terminal needs to reactivate, and then, based on the mapping between USS identifiers and SPS types, query the identifier of the USS corresponding to the determined type. Subsequently, it can transmit the DCI for deactivating the SPS to the terminal from the USS corresponding to the queried USS identifier. After receiving the DCI for deactivating the SPS from the USS, the terminal can determine the identifier of the USS containing the DCI, and then, based on the mapping between identifiers and SPS types, identify the type of the corresponding SPS.

[0229] like Figure 9 As shown, for example, the network-side equipment configures at least two USS identifiers for the terminal, namely USS#1 and USS#2. In the correspondence between USS identifiers and SPS types pre-stored by the terminal, USS#1 corresponds to UE-specific SPS, and USS#2 corresponds to group common SPS.

[0230] If the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to deactivate the group common SPS in slot #n, the network-side device can send a UE-specific PDCCH to the terminal in slot #n+5. The DCI scrambled with the RNTI carried in this PDCCH is located in the USS corresponding to USS #2. Upon receiving the DCI carried in the UE-specific PDCCH transmitted in slot #n+5, the terminal can determine that the DCI is in the USS corresponding to USS #2, and thus determine that USS #2 corresponds to the group common SPS. This allows the terminal to deactivate the group common SPS and subsequently stop receiving downlink information from the PDSCH corresponding to the group common SPS (e.g., located in slot #n+6).

[0231] Alternatively, the terminal can also send a UE-specific PDCCH to the terminal in the USS corresponding to USS#1 as needed. For example, a UE-specific PDCCH can be sent to the terminal in slot#n+4. When the terminal receives the DCI carried by the UE-specific PDCCH transmitted in slot#n+4, it can determine that the DCI is in the USS corresponding to USS#1. In this way, it can determine that USS#1 corresponds to the UE-specific SPS, thereby deactivating the UE-specific SPS. Subsequently, it can stop receiving downlink information in the PDSCH corresponding to the UE-specific SPS (e.g., located in slot#n+7).

[0232] In the above embodiments, the network-side device instructs the terminal to activate which SPS primarily through implicit indication. That is, the DCI is not directly used to indicate the type of SPS the terminal needs to activate, but rather through an RNTI that scrambles the DCI. The following embodiments mainly focus on explicit indication methods, providing illustrative examples of the technical solutions disclosed herein.

[0233] In one embodiment, instructing the terminal to determine the type includes:

[0234] Send indication information to the terminal to indicate the type.

[0235] In one embodiment, the indication information includes at least one of the following: Media Access Control Layer Control Element (MACCE); Radio Access Control (RRC) signaling; DCI.

[0236] In one embodiment, the network-side device can explicitly indicate to the terminal the type of SPS that needs to be deactivated, for example, by sending one or more indication messages to the terminal. The content carried in these indication messages directly indicates the type. The indication messages can be sent in the form of MAC CE, RRC signaling, or DCI, depending on the specific requirements.

[0237] In one embodiment, the indication information includes DCI, and sending the indication information to the terminal to indicate the type includes:

[0238] The type is indicated by information fields other than the verification field in the DCI.

[0239] In one embodiment, when the network-side device instructs the terminal to activate a specific type of SPS via the DCI, such as activating a group common SPS or a UE-specific SPS, it can use some information fields in the DCI for indication. However, regarding the validation field in the DCI, since the bits in the validation field are used for authentication, changing them can cause a series of problems. Therefore, in this embodiment, when instructing the terminal to activate a specific type of SPS via the DCI, the indication is made through information fields other than the validation field. Accordingly, after receiving the DCI, the terminal can determine the type of SPS to be activated based on the information fields other than the validation field in the DCI, so as to avoid causing problems due to changes in the bits in the validation field.

[0240] In one embodiment, indicating the type via an information field other than the verification field in the DCI includes:

[0241] The type is indicated by the Hybrid Automatic Repeat Request Process Number (HPN) field in the DCI.

[0242] In one embodiment, the terminal is configured with multiple SPS configurations of the aforementioned type, and the method further includes:

[0243] The target SPS configuration in the multiple SPS configurations of the aforementioned type is activated by using the value corresponding to the HPN field.

[0244] In one embodiment, the network-side device indicates the type via an information field other than the verification field in the DCI.

[0245] For example, the type can be indicated by the HPN field in the DCI. Accordingly, after receiving the DCI, the terminal can determine the type of the deactivated SPS based on the HPN field in the DCI.

[0246] It should be noted that the HPN domain can also be used as an authentication domain in some cases (such as when only one SPS configuration is configured for the terminal). The network-side device only indicates the type through the HPN domain when the HPN domain is not used as an authentication domain. For example, it indicates the type through 1 bit. When the value is 1, the type indicated is group common SPS. When the value is 1, the type indicated is UE-specific SPS.

[0247] In addition, some information fields in DCI, such as FDRA (Frequency Domain Resource Assignment), RV (Redundancy Version), and MCS (Modulation and Coding Scheme), can also be used as verification fields in some cases. When the terminal indicates the type through these information fields, the type should only be indicated through the HPN field if these information fields are not used as verification fields.

[0248] In one embodiment, the type of SPS to be deactivated can be determined based on the information fields other than the verification field in the DCI. The information fields other than the verification field in the DCI are the information fields in the non-verification field of the DCI excluding the FDRA, RV, MCS, and HPN information fields. For example, 1 bit can be used to indicate the type of SPS to be deactivated, 0 indicates that it is used to deactivate UE-specific SPS, and 1 indicates that it is used to deactivate group common SPS.

[0249] In one embodiment, for a certain type of SPS, the terminal may have multiple SPS configurations (e.g., each SPS configuration may have different parameters, such as different periods). These multiple SPS configurations may be configured by network-side devices or determined based on protocol agreements.

[0250] When a terminal has multiple SPS configurations of the aforementioned type, the network-side device, while instructing the terminal to activate the type of SPS through the HPN domain, can further instruct the terminal to specifically activate which SPS configuration of the aforementioned type. For example, the SPS configuration to be activated is called the target SPS configuration.

[0251] The network-side devices and terminals can each store the association between the values ​​corresponding to the HPN field and the SPS configuration. When the network-side device activates a specific SPS configuration using the value corresponding to the HPN field, the terminal can determine the SPS configuration corresponding to that value based on the association and then activate that SPS configuration. This allows for the specific deactivation of a particular SPS configuration, improving the accuracy of SPS deactivation.

[0252] For example, the HPN field is 4 bits and can indicate values ​​from 0 to 15. For instance, if the terminal has 8 sets of UE-specific SPS type SPS configurations with indices from 0 to 7, the first association between the value corresponding to the HPN field and the UE-specific SPS type SPS configuration includes: value 0 associated with index 0, value 1 associated with index 1, value 2 associated with index 2, value 3 associated with index 3, value 4 associated with index 4, value 5 associated with index 5, value 6 associated with index 6, and value 7 associated with index 7.

[0253] When a network-side device needs to deactivate a UE-specific SPS type SPS, it can indicate this by using the HPN field value from 0 to 7. For example, if it needs to activate the SPS configuration corresponding to index 1, the HPN field value in the sent DCI can be 1. After receiving the DCI, the terminal determines that the HPN field value is 1. Based on the first association relationship, it can determine that the corresponding index is 1, thereby deactivating the SPS configuration corresponding to index 1 in the UE-specific SPS type.

[0254] In one embodiment, a terminal can be configured with any one or more types of SPS. For example, a terminal may be configured with multiple types of SPS and have multiple SPS configurations in each type of SPS. The network-side device can activate one SPS configuration in one type of multiple SPS through the HPN domain, or it can activate one SPS configuration in another type of multiple SPS through the HPN domain.

[0255] For example, in the above embodiment, the terminal has 8 sets of UE-specific SPS type SPS configurations, and the network-side device can activate any one of these 8 SPS configurations by indicating the value 0 to 7 corresponding to the HPN field.

[0256] Based on this, the terminal can also have (e.g., network-side configuration or determined based on protocol agreement) 8 sets of SPS configurations of the group common SPS type, with indices 0 to 7 respectively; the second association between the value corresponding to the HPN field and the SPS configuration of the group common SPS type includes: value 8 associated with index 0, value 9 associated with index 1, value 10 associated with index 2, value 11 associated with index 3, value 12 associated with index 4, value 13 associated with index 5, value 14 associated with index 6, and value 15 associated with index 7.

[0257] When a network-side device needs to deactivate an SPS of the group common SPS type, it can indicate this by setting the value of the HPN field to 8 to 15. For example, if it needs to activate the SPS configuration corresponding to index 3, the value of the HPN field in the sent DCI can be 10. After the terminal receives the DCI, it determines that the value of the HPN field is 1. Based on the second association relationship, it can determine that the corresponding index is 2, thereby deactivating the SPS configuration corresponding to index 2 in the group common SPS type.

[0258] In one embodiment, the terminal can determine which SPS configuration of type group common SPS to activate based on the formula mod(HPN value, M), where HPN value represents the value corresponding to the HPN field, M represents the number of SPS configurations of type group common SPS, and mod represents the modulo operation. Specifically, the terminal only determines which SPS configuration of type group common SPS to activate based on this formula when HPN value is greater than or equal to 8.

[0259] For example, when M=8, when the network-side device needs to deactivate the SPS configuration corresponding to index 3, the HPN value in the sent DCI can be 10. The terminal substitutes HPN value=10 and M=8 into the above formula to calculate mod(10,8) and the value obtained is 2. It can be determined that the SPS configuration corresponding to index 2 in the group common SPS type will be deactivated.

[0260] It should be noted that the number of UE-specific SPS type SPS configurations and the number of groupcommon SPS type SPS configurations that the terminal has are not limited to the 8 sets described in the above embodiments, and can be set as needed.

[0261] In one embodiment, the range of HPN values ​​used to indicate the group common SPS type can be determined based on the number of SPS configurations of both UE-specific SPS and group common SPS types. For example, if the network side is configured with 4 UE-specific SPS type SPS configurations and 4 group common SPS type SPS configurations, then HPN values ​​0-3 are used to indicate the deactivation of the UE-specific SPS index, and HPN values ​​4-7 are used to indicate the deactivation of the group common SPS index.

[0262] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes:

[0263] In response to the activation of one type of SPS, namely the group common SPS and the UE-specific SPS, the activation of the other type of SPS, namely the group common SPS and the UE-specific SPS, by DCI scrambled via CS-RNTI is stopped.

[0264] In one embodiment, when a terminal is configured with both group common SPS and UE-specific SPS, since the terminal generally cannot use both types of SPS simultaneously, the network side can stop activating the other type of SPS via CS-RNTI scrambled DCI when one type of SPS has already been activated by the network-side device.

[0265] For example, if the network-side device has already activated group common SPS, the network side can stop activating UE-specific SPS through DCI scrambled by CS-RNTI; for example, if the network-side device has already activated UE-specific SPS, the network side can stop activating group common SPS through DCI scrambled by CS-RNTI.

[0266] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes:

[0267] In response to the activation of one type of SPS in the group common SPS and the UE-specific SPS, the activation of the other type of SPS in the group common SPS and the UE-specific SPS via CS-RNTI scrambled DCI is stopped.

[0268] In one embodiment, when a terminal is configured with both group common SPS and UE-specific SPS, since the terminal generally cannot use both types of SPS simultaneously, the network-side device can stop activating the other type of SPS via CS-RNTI scrambled DCI when one type of SPS has been activated by the network-side device, as the other type of SPS is generally not activated.

[0269] For example, when the network-side device has already activated group common SPS, the network-side device can stop activating UE-specific SPS through DCI scrambled by CS-RNTI. That is, in this case, the network-side device activates group common SPS through DCI scrambled by CS-RNTI.

[0270] For example, when the network-side device has already activated UE-specific SPS, the network-side device can stop activating group common SPS through DCI scrambled by CS-RNTI. That is, in this case, the network-side device activates UE-specific SPS through DCI scrambled by CS-RNTI.

[0271] Corresponding to the aforementioned methods for determining and reactivating semi-static scheduling, this disclosure also provides embodiments of apparatus for determining and reactivating semi-static scheduling.

[0272] Embodiments of this disclosure illustrate a semi-static scheduling reactivation determination apparatus. This apparatus can be applied to terminals, including but not limited to mobile phones, tablets, wearable devices, sensors, IoT devices, and other communication devices. The terminal can communicate with network-side devices, including but not limited to network-side devices in 4G, 5G, and 6G communication systems, such as base stations and core networks.

[0273] In one embodiment, the apparatus includes one or more processors, the processors being configured to:

[0274] The type of semi-static scheduling to be reactivated is determined based on the instructions from the network-side device.

[0275] In one embodiment, the type includes at least one of the following:

[0276] Group common SPS;

[0277] User Equipment-Specific Semi-Static Scheduling (UE-specific SPS)

[0278] In one embodiment, the indication of the network-side device includes at least one of the following:

[0279] Explicit instructions and implicit instructions.

[0280] In one embodiment, the processor is configured to:

[0281] Receive downlink control information (DCI) for deactivating SPS transmitted in the user equipment dedicated search space (USS);

[0282] The type is determined based on the Radio Network Temporary Identifier (RNTI) scrambled with the DCI.

[0283] In one embodiment, the processor is configured to:

[0284] In response to the RNTI of the scrambled DCI being a first RNTI, determine to reactivate group common SPS; and / or in response to the RNTI of the scrambled DCI being a second RNTI, determine to reactivate UE-specific SPS.

[0285] In one embodiment, the first RNTI is different from the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS, and / or different from the CS-RNTI used to scramble the DCI for initial deactivation of UE-specific SPS.

[0286] In one embodiment, the first RNTI is the same as the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS.

[0287] In one embodiment, the processor is configured to: in response to supporting the reception of a DCI for deactivating the group common SPS in the USS, upon receiving a DCI scrambled by CS-RNTI in the USS, determine to reactivate the group common SPS.

[0288] In one embodiment, the terminal is configured with group common SPS and not with UE-specific SPS.

[0289] In one embodiment, the processor is configured to:

[0290] In response to supporting the reception of a DCI for deactivating group common SPS in a preset USS, when a DCI scrambled by CS-RNTI is received in the preset USS, it is determined to reactivate group common SPS.

[0291] In one embodiment, the terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resource, and the processor is configured to determine the type based on the RNTI of the DCI transmitted by the network-side device on the second frequency domain resource.

[0292] In one embodiment, the first frequency domain resource includes a first component carrier (CC), and the second frequency domain resource includes a second CC; and / or the first frequency domain resource includes a first bandwidth portion (BWP), and the second frequency domain resource includes a second BWP.

[0293] In one embodiment, the processor is configured to: receive a DCI for deactivating the SPS transmitted in the USS; and determine the type based on the identifier of the USS where the DCI is located.

[0294] In one embodiment, the processor is configured to determine the type based on indication information sent by the network-side device.

[0295] In one embodiment, the indication information includes at least one of the following: Media Access Control Layer Control Element (MACCE); Radio Access Control (RRC) signaling; DCI.

[0296] In one embodiment, the indication information includes a DCI, and the processor is configured to determine the type based on information fields other than the verification field in the DCI.

[0297] In one embodiment, the processor is configured to determine the type based on the Hybrid Automatic Repeat Request Process Number (HPN) field in the DCI.

[0298] In one embodiment, the terminal is configured with multiple SPS configurations of the aforementioned type, and the processor is further configured to: determine, based on the value corresponding to the HPN domain, to deactivate a target SPS configuration among the multiple SPS configurations of the aforementioned type.

[0299] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the processor is further configured to: in response to determining that the network-side device has activated one type of SPS, the group common SPS and the UE-specific SPS, not expect the network-side device to activate the other type of SPS, the group common SPS and the UE-specific SPS, via CS-RNTI scrambled DCI.

[0300] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the processor is further configured to: in response to determining that the network-side device has activated one type of SPS, the group common SPS and the UE-specific SPS, not expect the network-side device to activate the other type of SPS, the group common SPS and the UE-specific SPS, through CS-RNTI scrambled DCI.

[0301] Embodiments of this disclosure illustrate a semi-static scheduling reactivation apparatus. This apparatus can be applied to network-side devices that can communicate with terminals, including but not limited to mobile phones, tablets, wearable devices, sensors, and IoT devices. The network-side devices include, but are not limited to, network-side devices in 4G, 5G, and 6G communication systems, such as base stations and core networks.

[0302] In one embodiment, the apparatus includes one or more processors, the processors being configured to:

[0303] Determine the type of semi-static scheduling (SPS) that the terminal is expected to be reactivated;

[0304] Instruct the terminal to determine the type.

[0305] In one embodiment, the type includes at least one of the following:

[0306] Group common SPS;

[0307] User Equipment-Specific Semi-Static Scheduling (UE-specific SPS)

[0308] In one embodiment, the indication of the network-side device includes at least one of the following:

[0309] Explicit instructions and implicit instructions.

[0310] In one embodiment, the processor is configured to:

[0311] Based on the type, determine the Radio Network Temporary Identifier (RNTI) for scrambling the Downlink Control Information (DCI) used to deactivate the SPS in the User Equipment Dedicated Search Space (USS).

[0312] The DCI is scrambled using a defined RNTI;

[0313] The USS transmits the DCI to the terminal so that the terminal determines the type based on the RNTI scrambled with the DCI.

[0314] In one embodiment, the processor is configured to:

[0315] In response to the expectation that the terminal will reactivate the group common SPS, the DCI is scrambled by a first RNTI; and / or in response to the expectation that the terminal will reactivate the UE-specific SPS, the DCI is scrambled by a second RNTI.

[0316] In one embodiment, the first RNTI is different from the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS, and / or different from the CS-RNTI used to scramble the DCI for initial deactivation of UE-specific SPS.

[0317] In one embodiment, the first RNTI is the same as the GS-RNTI used to scramble the DCI for initial deactivation of group common SPS.

[0318] In one embodiment, the processor is configured to:

[0319] In response to determining that the terminal supports receiving DCI for deactivating group common SPS in the USS, and expecting the terminal to reactivate group common SPS, DCI transmitted in the USS is scrambled by CS-RNTI.

[0320] The USS transmits the DCI to the terminal so that the terminal determines to reactivate the group common SPS based on the CS-RNTI scrambled with the DCI.

[0321] In one embodiment, the terminal is configured with group common SPS and not with UE-specific SPS.

[0322] In one embodiment, the processor is configured to:

[0323] In response to determining that the terminal supports receiving DCI for deactivating group common SPS in a preset USS, and expecting the terminal to reactivate group common SPS, the DCI transmitted in the preset USS is scrambled by CS-RNTI.

[0324] The preset USS transmits the DCI to the terminal so that the terminal can determine to reactivate the group common SPS based on the CS-RNTI of the scrambled DCI.

[0325] In one embodiment, the terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resources, and the processor is configured to:

[0326] The RNTI for scrambling DCI transmitted on the second frequency domain resource is determined according to the type.

[0327] The DCI is scrambled using a defined RNTI;

[0328] The DCI is transmitted to the terminal on a second frequency domain resource so that the terminal determines the type based on the RNTI of the scrambled DCI.

[0329] In one embodiment, the first frequency domain resource includes a first component carrier (CC), and the second frequency domain resource includes a second CC; and / or the first frequency domain resource includes a first bandwidth portion (BWP), and the second frequency domain resource includes a second BWP.

[0330] In one embodiment, the processor is configured to:

[0331] The USS identifier is determined based on the type described;

[0332] The USS corresponding to the identifier transmits a DCI scrambled by CS-RNTI to the terminal, so that the terminal can determine the type based on the identifier of the USS where the DCI is located.

[0333] In one embodiment, the processor is configured to:

[0334] Send indication information to the terminal to indicate the type.

[0335] In one embodiment, the indication information includes at least one of the following: Media Access Control Layer Control Element (MACCE); Radio Access Control (RRC) signaling; DCI.

[0336] In one embodiment, the indication information includes DCI, and the processor is configured to:

[0337] The type is indicated by information fields other than the verification field in the DCI.

[0338] In one embodiment, the processor is configured to indicate the type via the Hybrid Automatic Repeat Request Process Number (HPN) field in the DCI.

[0339] In one embodiment, the terminal is configured with multiple SPS configurations of the aforementioned type, and the processor is further configured to activate a target SPS configuration among the multiple SPS configurations of the aforementioned type using the value corresponding to the HPN field.

[0340] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the processor is further configured to: in response to the activation of one type of SPS, the group common SPS and the UE-specific SPS, stop activating the other type of SPS, the group common SPS and the UE-specific SPS, via DCI scrambled by CS-RNTI.

[0341] In one embodiment, the terminal is configured with the group common SPS and the UE-specific SPS, and the processor is further configured to: in response to the activation of one type of SPS, the group common SPS and the UE-specific SPS, stop activating the other type of SPS, the group common SPS and the UE-specific SPS, via DCI scrambled by CS-RNTI.

[0342] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments of the relevant methods, and will not be elaborated upon here.

[0343] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0344] Embodiments of this disclosure also provide a communication device, such as the terminal described above, comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the semi-static scheduling reactivation determination method described in any of the above embodiments is implemented.

[0345] Embodiments of this disclosure also provide a communication device, such as the network-side device described above, comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the semi-static scheduling reactivation method described in any of the above embodiments is implemented.

[0346] Embodiments of this disclosure also propose a computer-readable storage medium for storing a computer program that, when executed by a processor, implements the steps in the semi-static scheduling reactivation determination method described in any of the above embodiments.

[0347] Embodiments of this disclosure also provide a computer-readable storage medium for storing a computer program that, when executed by a processor, implements the steps in the semi-static scheduling reactivation method described in any of the above embodiments.

[0348] like Figure 15 As shown, Figure 15 This is a schematic block diagram illustrating a re-deactivation device 1500 for semi-static scheduling according to embodiments of the present disclosure. The device 1500 can be provided as a base station. (Refer to...) Figure 15 The apparatus 1500 includes a processing component 1522, a wireless transmit / receive component 1524, an antenna component 1526, and a signal processing section specific to the wireless interface. The processing component 1522 may further include one or more processors. One of the processors in the processing component 1522 may be configured to implement the semi-static scheduling reactivation method described in any of the above embodiments.

[0349] Figure 16 This is a schematic block diagram illustrating a reactivation determination device 1600 for semi-static scheduling according to embodiments of the present disclosure. For example, device 1600 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0350] Reference Figure 16 The device 1600 may include one or more of the following components: a processing component 1602, a memory 1604, a power supply component 1606, a multimedia component 1608, an audio component 1610, an input / output (I / O) interface 1612, a sensor component 1614, and a communication component 1616.

[0351] Processing component 1602 typically controls the overall operation of device 1600, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1602 may include one or more processors 1620 to execute instructions to complete all or part of the steps of the semi-static scheduling reactivation determination method described above. Furthermore, processing component 1602 may include one or more modules to facilitate interaction between processing component 1602 and other components. For example, processing component 1602 may include a multimedia module to facilitate interaction between multimedia component 1608 and processing component 1602.

[0352] Memory 1604 is configured to store various types of data to support the operation of device 1600. Examples of such data include instructions for any application or method operating on device 1600, contact data, phonebook data, messages, pictures, videos, etc. Memory 1604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0353] Power supply component 1606 provides power to various components of device 1600. Power supply component 1606 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to device 1600.

[0354] Multimedia component 1608 includes a screen that provides an output interface between the device 1600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1608 includes a front-facing camera and / or a rear-facing camera. When the device 1600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0355] Audio component 1610 is configured to output and / or input audio signals. For example, audio component 1610 includes a microphone (MIC) configured to receive external audio signals when device 1600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1604 or transmitted via communication component 1616. In some embodiments, audio component 1610 also includes a speaker for outputting audio signals.

[0356] I / O interface 1612 provides an interface between processing component 1602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0357] Sensor assembly 1614 includes one or more sensors for providing status assessments of various aspects of device 1600. For example, sensor assembly 1614 may detect the on / off state of device 1600, the relative positioning of components such as the display and keypad of device 1600, changes in the position of device 1600 or a component of device 1600, the presence or absence of user contact with device 1600, the orientation or acceleration / deceleration of device 1600, and temperature changes of device 1600. Sensor assembly 1614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1614 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0358] Communication component 1616 is configured to facilitate wired or wireless communication between device 1600 and other devices. Device 1600 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, 4G LTE, 5G NR, or combinations thereof. In one exemplary embodiment, communication component 1616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1616 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0359] In an exemplary embodiment, the apparatus 1600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described semi-static scheduling reactivation determination method.

[0360] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1604 including instructions, which can be executed by a processor 1620 of the device 1600 to complete the aforementioned semi-static scheduling reactivation determination method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0361] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0362] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

[0363] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0364] The methods and apparatus provided in the embodiments of this disclosure have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this disclosure. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this disclosure. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this disclosure. Therefore, the content of this specification should not be construed as a limitation of this disclosure.

Claims

1. A method for determining reactivation in semi-static scheduling, characterized in that, The method, executed by a terminal, includes: The type of semi-static scheduling to be reactivated is determined according to the instructions of the network-side device; the type includes at least one of the following: group common SPS; UE-specific SPS; DCI for activating the group common SPS carried in CSS; DCI for activating the UE-specific SPS carried in USS. The type of semi-static scheduling to be reactivated based on the instructions of the network-side device includes: when a DCI scrambled by CS-RNTI is received in the USS, the group common SPS is reactivated.

2. The method according to claim 1, characterized in that, The method further includes: Before receiving a DCI scrambled by CS-RNTI in the USS, when receiving a DCI scrambled by group scheduling RNTI in the CSS, it is determined to reactivate the group common SPS; If the group scheduling RNTI is not successfully demodulated, an unacknowledged message (NACK) is sent to the network-side device.

3. The method according to claim 1, characterized in that, The indications of the network-side device include at least one of the following: Explicit instructions and implicit instructions.

4. The method according to claim 1, characterized in that, The type of semi-static scheduling for reactivation determined according to the instructions of the network-side device includes: Receive downlink control information (DCI) for deactivating SPS transmitted in the user equipment dedicated search space (USS); The type is determined based on the Radio Network Temporary Identifier (RNTI) scrambled with the DCI.

5. The method according to claim 4, characterized in that, The step of determining the type based on the RNTI scrambled with the DCI includes: In response to the RNTI of the scrambled DCI being the first RNTI, it is determined to reactivate the group common SPS; and / or In response to the RNTI of the scrambled DCI being a second RNTI, it is determined to reactivate the UE-specific SPS.

6. The method according to claim 5, characterized in that, The first RNTI is different from the group scheduling-RNTI used to scramble the DCI for initial deactivation of group common SPS, and / or different from the CS-RNTI used to scramble the DCI for initial deactivation of UE-specific SPS.

7. The method according to claim 5, characterized in that, The first RNTI is the same as the group scheduling-RNTI used to scramble the DCI for initial deactivation of the group common SPS.

8. The method according to claim 1, characterized in that, The terminal was configured with group common SPS and not with UE-specific SPS.

9. The method according to claim 1, characterized in that, The type of semi-static scheduling for reactivation determined according to the instructions of the network-side device includes: In response to supporting the reception of a DCI for deactivating group common SPS in a preset USS, when a DCI scrambled by CS-RNTI is received in the preset USS, it is determined to reactivate group common SPS.

10. The method according to claim 1, characterized in that, The terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resources, and the determination of the type of semi-static scheduling for reactivation based on the indication of the network-side device includes: The type is determined based on the RNTI of the DCI transmitted by the scrambled network-side device on the second frequency domain resource.

11. The method according to claim 10, characterized in that, The first frequency domain resource includes a first component carrier (CC), and the second frequency domain resource includes a second CC; and / or The first frequency domain resource includes a first bandwidth portion (BWP), and the second frequency domain resource includes a second bandwidth portion (BWP).

12. The method according to claim 1, characterized in that, The type of semi-static scheduling for reactivation determined according to the instructions of the network-side device includes: Receive the DCI transmitted in the USS for deactivating the SPS; The type is determined based on the identifier of the USS where the DCI is located.

13. The method according to claim 1, characterized in that, The type of semi-static scheduling for reactivation determined according to the instructions of the network-side device includes: The type is determined based on the indication information sent by the network-side device.

14. The method according to claim 13, characterized in that, The indication information includes at least one of the following: Media Access Control Layer (MAC) control element CE; Radio Access Control (RRC) signaling; DCI.

15. The method according to claim 14, characterized in that, The indication information includes DCI, and determining the type based on the indication information sent by the network-side device includes: The type is determined based on information fields other than the verification field in the DCI.

16. The method according to claim 15, characterized in that, Determining the type based on information fields other than the verification field in the DCI includes: The type is determined based on the Hybrid Automatic Repeat Request (HPN) field in the DCI.

17. The method according to claim 16, characterized in that, The terminal is configured with multiple SPS configurations of the aforementioned type, and the method further includes: Based on the value corresponding to the HPN field, determine the target SPS configuration among the multiple SPS configurations of the aforementioned type to deactivate.

18. The method according to claim 1, characterized in that, The terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes: In response to determining that the network-side device has activated one type of SPS, namely the group common SPS and the UE-specific SPS, it is not expected that the network-side device will activate the other type of SPS, namely the group common SPS and the UE-specific SPS, through CS-RNTI scrambled DCI.

19. The method according to claim 1, characterized in that, The terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes: In response to determining that the network-side device has activated one type of SPS, namely the group common SPS and the UE-specific SPS, it is not expected that the network-side device will activate the other type of SPS, namely the group common SPS and the UE-specific SPS, through CS-RNTI scrambled DCI.

20. A semi-static scheduling reactivation method, characterized in that, Performed by a network-side device, the method includes: Determine the type of semi-static scheduling (SPS) that the terminal is expected to be reactivated; The terminal is instructed to determine the type; the type includes at least one of the following: group common SPS; UE-specific SPS; DCI for activating the group common SPS carried in CSS; DCI for activating the UE-specific SPS carried in USS. Wherein, instructing the terminal to determine the type includes: In the USS, a DCI scrambled by CS-RNTI is sent to the associated terminal. The DCI scrambled by CS-RNTI is used to determine the reactivation of the group common SPS.

21. The method according to claim 20, characterized in that, The method further includes: Before sending the DCI scrambled by CS-RNTI to the terminal in the USS, the DCI scrambled by group scheduling RNTI is sent to the terminal in the CSS to deactivate the group common SPS. The terminal received an unacknowledged message (NACK), indicating that the terminal had failed to demodulate the group scheduling RNTI.

22. The method according to claim 20, characterized in that, The indications of the network-side device include at least one of the following: Explicit instructions and implicit instructions.

23. The method according to claim 20, characterized in that, The step of instructing the terminal to determine the type includes: Based on the type, determine the Radio Network Temporary Identifier (RNTI) for scrambling the Downlink Control Information (DCI) used to deactivate the SPS in the User Equipment Dedicated Search Space (USS). The DCI is scrambled using a defined RNTI; The USS transmits the DCI to the terminal so that the terminal determines the type based on the RNTI scrambled with the DCI.

24. The method according to claim 23, characterized in that, The determination of the RNTI for scrambling the DCI in the USS according to the type includes: In response to the desired reactivation of the group common SPS by the terminal, the DCI is scrambled via the first RNTI; and / or In response to the desired reactivation of the UE-specific SPS by the terminal, the DCI is scrambled via a second RNTII.

25. The method according to claim 24, characterized in that, The first RNTI is different from the group scheduling-RNTI used to scramble the DCI for initial deactivation of group common SPS, and / or different from the CS-RNTI used to scramble the DCI for initial deactivation of UE-specific SPS.

26. The method according to claim 25, characterized in that, The first RNTI is the same as the group scheduling-RNTI used to scramble the DCI for initial deactivation of the group commonSPS.

27. The method according to claim 20, characterized in that, The step of instructing the terminal to determine the type includes: In response to determining that the terminal supports receiving DCI for deactivating group common SPS in the USS, and expecting the terminal to reactivate group common SPS, DCI transmitted in the USS is scrambled by CS-RNTI. The USS transmits the DCI to the terminal so that the terminal determines to reactivate the group common SPS based on the CS-RNTI scrambled with the DCI.

28. The method according to claim 24, characterized in that, The terminal was configured with group common SPS and not with UE-specific SPS.

29. The method according to claim 20, characterized in that, The terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resource, and instructing the terminal to determine the type includes: The RNTI for scrambling DCI transmitted on the second frequency domain resource is determined according to the type. The DCI is scrambled using a defined RNTI; The DCI is transmitted to the terminal on a second frequency domain resource so that the terminal determines the type based on the RNTI of the scrambled DCI.

30. The method according to claim 29, characterized in that, The first frequency domain resource includes a first component carrier (CC), and the second frequency domain resource includes a second CC; and / or The first frequency domain resource includes a first bandwidth portion (BWP), and the second frequency domain resource includes a second bandwidth portion (BWP).

31. The method according to claim 20, characterized in that, The step of instructing the terminal to determine the type includes: The USS identifier is determined based on the type described; The USS corresponding to the identifier transmits a DCI scrambled by CS-RNTI to the terminal, so that the terminal can determine the type based on the identifier of the USS where the DCI is located.

32. The method according to claim 20, characterized in that, The step of instructing the terminal to determine the type includes: Send indication information to the terminal to indicate the type.

33. The method according to claim 32, characterized in that, The indication information includes at least one of the following: Media Access Control Layer (MAC) control element CE; Radio Access Control (RRC) signaling; DCI.

34. The method according to claim 33, characterized in that, The indication information includes DCI, and sending the indication information to the terminal to indicate the type includes: The type is indicated by information fields other than the verification field in the DCI.

35. The method according to claim 34, characterized in that, The indication of the type via information fields other than the verification field in the DCI includes: The type is indicated by the Hybrid Automatic Repeat Request Process Number (HPN) field in the DCI.

36. The method according to claim 35, characterized in that, The terminal is configured with multiple SPS configurations of the aforementioned type, and the method further includes: The target SPS configuration in the multiple SPS configurations of the aforementioned type is activated by using the value corresponding to the HPN field.

37. The method according to claim 20, characterized in that, The terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes: In response to the activation of one type of SPS, namely the group common SPS and the UE-specific SPS, the activation of the other type of SPS, namely the group common SPS and the UE-specific SPS, by DCI scrambled via CS-RNTI is stopped.

38. The method according to claim 20, characterized in that, The terminal is configured with the group common SPS and the UE-specific SPS, and the method further includes: In response to the activation of one type of SPS in the group common SPS and the UE-specific SPS, the activation of the other type of SPS in the group common SPS and the UE-specific SPS via CS-RNTI scrambled DCI is stopped.

39. A semi-static scheduling reactivation determination device, characterized in that, Includes one or more processors, said processors being configured to: The type of semi-static scheduling to be reactivated is determined according to the instructions of the network-side device; the type includes at least one of the following: group common SPS; UE-specific SPS; DCI for activating the group common SPS carried in CSS; DCI for activating the UE-specific SPS carried in USS. The type of semi-static scheduling to be reactivated based on the instructions of the network-side device includes: when a DCI scrambled by CS-RNTI is received in the USS, the group common SPS is reactivated.

40. A semi-static scheduling reactivation device, characterized in that, Includes one or more processors, said processors being configured to: Determine the type of semi-static scheduling (SPS) that the terminal is expected to be reactivated; The terminal is instructed to determine the type; the type includes at least one of the following: group common SPS; UE-specific SPS; DCI for activating the group common SPS carried in CSS; DCI for activating the UE-specific SPS carried in USS. Wherein, instructing the terminal to determine the type includes: In the USS, a DCI scrambled by CS-RNTI is sent to the associated terminal. The DCI scrambled by CS-RNTI is used to determine the reactivation of the group common SPS.

41. A communication device, characterized in that, include: processor; Memory used to store computer programs; When the computer program is executed by the processor, it implements the reactivation determination method for the semi-static scheduling as described in any one of claims 1 to 19.

42. A communication device, characterized in that, include: processor; Memory used to store computer programs; When the computer program is executed by the processor, it implements the semi-static scheduling reactivation method according to any one of claims 20 to 38.

43. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps in the semi-static scheduling reactivation determination method according to any one of claims 1 to 19.

44. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps in the semi-static scheduling reactivation method according to any one of claims 20 to 38.

Images