Semi-persistent scheduling reactivation, determination method and apparatus

Abstract

The present disclosure relates to a semi-persistent scheduling reactivation determining method and device, wherein the semi-persistent scheduling reactivation determining method comprises determining the type of reactivated semi-persistent scheduling according to the indication of a network side device. According to the present disclosure, when indicating the terminal to reactivate the semi-persistent scheduling, the network side device can indicate the type of reactivated semi-persistent scheduling, so that the terminal can accurately determine the type of semi-persistent scheduling to be reactivated, and then reactivate the semi-persistent scheduling of the corresponding type, and communicate smoothly with the network side device through the configuration of the reactivated semi-persistent scheduling, avoiding the situation that the terminal cannot communicate smoothly with the network side device due to the reactivation of the wrong type of semi-persistent scheduling, and affecting the communication effect.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method for determining reactivation of semi-static scheduling, a method for reactivating semi-static scheduling, a device for determining reactivation of semi-static scheduling, a device for reactivating semi-static scheduling, a communication device, and a computer-readable storage medium. Background Art

[0002] In related technologies, semi-persistent scheduling (SPS) is proposed, which can configure periodic resources for the terminal. After activating the SPS, downlink resource scheduling is no longer necessary when performing downlink transmission. The terminal receives downlink transmission according to the configuration of the activated SPS, which is conducive to saving signaling overhead.

[0003] 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 the activation instruction sent by the network is for, which leads to some problems. Summary of the Invention

[0004] In view of this, the embodiments of the present disclosure propose a semi-static scheduling reactivation determination method, a semi-static scheduling reactivation method, a semi-static scheduling reactivation determination device, a semi-static scheduling reactivation device, a communication device and a computer-readable storage medium to solve the technical problems in the related art.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for determining reactivation of semi-persistent scheduling is proposed, which is executed by a terminal. The method includes: determining the type of reactivated semi-persistent scheduling according to an instruction of a network-side device.

[0006] According to the second aspect of an embodiment of the present disclosure, a semi-static scheduling reactivation method is proposed, which is executed by a network side device. The method includes: determining the type of semi-static scheduling SPS that the terminal is expected to reactivate; and instructing the terminal to enable the terminal to determine the type.

[0007] According to a third aspect of an embodiment of the present disclosure, a device for determining reactivation of semi-static scheduling is proposed, comprising one or more processors, wherein the processors are configured to determine the type of reactivated semi-static scheduling according to an instruction of a network-side device.

[0008] According to the fourth aspect of an embodiment of the present disclosure, a semi-static scheduling reactivation device is proposed, comprising one or more processors, wherein the processors are configured to: determine the type of semi-static scheduling SPS that the terminal is expected to reactivate; and instruct the terminal to enable the terminal to determine the type.

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

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

[0011] According to a seventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is proposed for storing a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method for determining the reactivation of semi-static scheduling are implemented.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a computer-readable storage medium is proposed for storing a computer program. When the computer program is executed by a processor, the steps in the above-mentioned semi-static scheduling reactivation method are implemented.

[0013] According to an embodiment of the present disclosure, when the network side device instructs the terminal to reactivate the SPS, it can instruct the terminal on the type of SPS to be reactivated. Accordingly, the terminal can accurately determine the type of SPS that needs to be reactivated, and then reactivate the corresponding type of SPS, and communicate smoothly with the network side device through the configuration of the reactivated SPS, thereby avoiding reactivating the wrong type of SPS, which may cause an inability to communicate smoothly with the network side device and affect the communication effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0015] Figure 1 The figure is a schematic flow chart of a method for determining reactivation of semi-persistent scheduling according to an embodiment of the present disclosure.

[0016] Figure 2 It is a schematic diagram showing the configuration of a group common SPS according to an embodiment of the present disclosure.

[0017] Figure 3 It is a schematic flowchart of another method for determining reactivation of semi-persistent scheduling according to an embodiment of the present disclosure.

[0018] Figure 4 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0019] Figure 5 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0020] Figure 6 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0021] Figure 7 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0022] Figure 8 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0023] Figure 9 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0024] Figure 10 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0025] Figure 11 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0026] Figure 12 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0027] Figure 13 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0028] Figure 14 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0029] Figure 15 is another reactivation time-domain diagram according to embodiments of the present disclosure.

[0030] Figure 16 is another reactivation time-domain diagram according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0031] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present disclosure.

[0032] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include 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 or all possible combinations of one or more associated listed items.

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

[0034] For the purpose of brevity and ease of understanding, the terms "greater than," "less than," "higher than," and "lower than" are used herein to describe size relationships. However, those skilled in the art will understand that the term "greater than" also encompasses the meaning of "greater than or equal to," and "less than" also encompasses the meaning of "less than or equal to," and the term "higher than" also encompasses the meaning of "higher than or equal to," and "lower than" also encompasses the meaning of "lower than or equal to."

[0035] Figure 1 This is a schematic flow chart illustrating a method for determining reactivation of semi-persistent scheduling according to an embodiment of the present disclosure. The method for determining reactivation of semi-persistent scheduling illustrated in this embodiment can be executed by a terminal, including but not limited to a mobile phone, tablet computer, wearable device, sensor, IoT device, or other communication device. 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.

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

[0037] In some cases, some terminals fail to correctly decode the instructions sent by the network side device, resulting in the failure to correctly determine the SPS that needs to be activated. The network side device can determine whether the terminal has correctly decoded the instructions based on the information fed back by the terminal. If it is determined that the terminal has not correctly decoded the instructions, the network side device can instruct the terminal again to reactivate the SPS.

[0038] There can be multiple types of SPS configured by the network side device for the terminal. The following embodiments mainly provide an illustrative description of the technical solution of the present disclosure by focusing on the configuration of group common SPS and UE-specific SPS configured by the network side device for the terminal.

[0039] For group common SPS, during initial activation, the downlink control information DCI (Downlink Control Information) encrypted by the group scheduled radio network temporary identity GS-RNTI (Group Scheduled-Radio Network Temporary Identity) can be transmitted in the group common physical downlink control channel groupcommon PDCCH (Physical Downlink Control Channel) to indicate activation. After receiving the indication, the terminal can decode the DCI and determine the RNTI used for decoding, and then determine that the SPS to be activated is the group common SPS based on the RNTI (specifically, the value of the RNTI).

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

[0041] The terminal may be a terminal supporting MBS (Multicast Broadcast Service), and the terminal may also support unicast service.

[0042] The above-mentioned group common SPS can be configured for terminals in the same group. However, since the channel transmission conditions of different terminals belonging to the same group may be different, some terminals can correctly demodulate and determine the RNTI, while some terminals cannot correctly demodulate and determine the RNTI. The terminals that correctly demodulate and determine the RNTI can return confirmation information ACK to the network side device, and the terminals that cannot correctly demodulate and determine the RNTI can return non-confirmation information NACK to the network side device. The network side device can determine which terminals have not correctly demodulated and determined the RNTI based on the feedback received.

[0043] For terminals that have not correctly demodulated and determined the RNTI, the network-side device can re-instruct the terminal to reactivate the group common SPS. Currently, one way to re-instruct the terminal is through the user equipment-specific physical downlink control channel UE-specific PDCCH. However, the current UE-specific PDCCH is mainly used to activate the user equipment-specific semi-static scheduling UE-specific SPS. When using the UE-specific PDCCH to activate the group common SPS, it is difficult for the terminal to distinguish which type of SPS the UE-specific PDCCH is activating.

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

[0045] In step S101 , the type of reactivated semi-persistent scheduling is determined according to an instruction from a network-side device.

[0046] In one embodiment, when the network side device instructs the terminal to reactivate the SPS, it can instruct the terminal on the type of SPS to be reactivated. Based on this, the terminal can accurately determine the type of SPS that needs to be reactivated, and then reactivate the corresponding type of SPS, and communicate smoothly with the network side device through the configuration of the reactivated SPS, such as receiving downlink information, to avoid reactivating the wrong type of SPS, which may result in an inability to communicate smoothly with the network side device and affect the communication effect.

[0047] In one embodiment, the type includes at least one of the following: group common semi-persistent scheduling groupcommon SPS; user equipment specific semi-persistent scheduling UE-specific SPS.

[0048] The network-side device may instruct the terminal to reactivate the group common SPS or reactivate the UE-specific SPS. When the terminal determines to reactivate the group common SPS according to the instruction, it may reactivate the group common SPS and communicate 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 may reactivate the UE-specific SPS and communicate with the network-side device according to the configuration of the UE-specific SPS;

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

[0050] Explicit indication, implicit indication.

[0051] The way in which the network side device indicates the terminal may be an explicit indication, such as sending one or more messages to the terminal, and the content carried in the message directly indicates the type; the way in which the network side device indicates the terminal may be an implicit indication, such as sending information to the terminal, the information has other functions and is not directly used to indicate the type, and the terminal can determine the type of SPS that needs to be reactivated based on the information in some way, for example, the information is a DCI in the user-specific search space USS (User-Specific Search Space), and the DCI is encrypted by RNTI. The DCI is not used to indicate the type, but the terminal can determine the type based on the RNTI of the scrambled DCI.

[0052] Figure 2 It is a schematic diagram showing the configuration of a group common SPS according to an embodiment of the present disclosure.

[0053] like Figure 2 As shown, for example, for a terminal supporting MBS, the network side device configures at least the group common SPS configuration for the terminal, wherein 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 in slot #n+1 and the next one is in slot #n+6, with an interval of 5 slots.

[0054] The network-side device initially activates the group common SPS in slot #n. For example, in slot #n, the group common PDCCH is sent to the terminals belonging to the same group. The DCI in the group common PDCCH is scrambled by GS-RNTI. If the terminal correctly demodulates and determines the RNTI corresponding to the DCI, it can communicate with the network-side device according to the configuration of the group common PDCCH, for example, receiving the PDSCH of the group common SPS in slot #n+1 and slot #n+6.

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

[0056] In addition, if the network-side device also configures UE-specific SPS configuration for the terminal, DCI scrambled by CS-RNTI can be transmitted in USS for reactivation.

[0057] The following embodiments are mainly Figure 2 Based on the illustrated embodiment, several ways in which a network-side device instructs a terminal to reactivate a group common SPS are exemplified.

[0058] Figure 3 FIG. 1 is a schematic flow chart of another method for determining reactivation of semi-static scheduling according to an embodiment of the present disclosure. Figure 3 As shown, the type of semi-persistent scheduling to be reactivated according to the instruction of the network side device includes:

[0059] In step S301, downlink control information DCI for activating SPS transmitted in a user equipment-specific search space USS is received;

[0060] In step S302, the type is determined according to the Radio Network Temporary Identifier (RNTI) used to scramble the DCI.

[0061] It should be noted that the terminal may determine whether the DCI is for activating SPS in a predetermined manner, and the judgment condition includes at least one of the following:

[0062] The CRC of the DCI is scrambled by the CS-RNTI or the GS-RNTI.

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

[0064] If DFI is present in the DCI, the DFI field (DCI format indicator) is 0;

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

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

[0067] In one embodiment, the network side device may transmit DCI for activating SPS in the USS, for example, the DCI is 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.

[0068] The terminal may pre-store a correspondence between the RNTI and the type of SPS, such as that agreed upon by the protocol or pre-configured by the network-side device. After the terminal receives the DCI for activating the SPS in the USS, it may determine the RNTI that scrambles the DCI, for example, by descrambling the DCI through the RNTI, and the RNTI that successfully descrambles the DCI corresponds to the RNTI that scrambled the DCI, thereby determining the RNTI that scrambled the DCI based on the RNTI that successfully descrambled the DCI, and then determining the type of SPS corresponding to the RNTI that scrambled the DCI based on the RNTI that scrambled the DCI and the correspondence.

[0069] Figure 4 FIG. 4 is a time domain schematic diagram of reactivation according to an embodiment of the present disclosure.

[0070] like Figure 4As shown, the terminal does not correctly demodulate the RNTI corresponding to the DCI for activating the group common SPS in slot #n, and the network side device can send a UE-specific PDCCH (carrying a DCI scrambled by an 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, the terminal can receive the PDSCH of the group common SPS in slot #n+6 according to the configuration of the group common SPS.

[0071] In one embodiment, the determining the type according to the RNTI scrambling the DCI comprises:

[0072] In response to the RNTI scrambling the DCI being a first RNTI, determining to reactivate the group common SPS; and / or in response to the RNTI scrambling the DCI being a second RNTI, determining to reactivate the UE-specific SPS.

[0073] The terminal can pre-store a correspondence between the RNTI and the type of SPS, for example, agreed by a protocol or pre-configured by the network side device, in which the first RNTI corresponds to the group common SPS and the second RNTI corresponds to the UE-specific SPS.

[0074] The first RNTI and / or the second RNTI can be different from the RNTI in the related art, or can reuse the RNTI in the related art, which can be selected as needed.

[0075] In one embodiment, the first RNTI is different from a GS-RNTI (Group Scheduling-Radio Network Temporary Identity) used for scrambling the DCI for initial activation of the group common SPS, and / or different from a CS-RNTI (Configured Scheduling-Radio Network Temporary Identity) used for scrambling the DCI for initial activation of the UE-specific SPS.

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

[0077] But in some cases, there is a partial overlap between the CSS and the USS. If the DCI for activating SPS transmitted in the USS is located in the overlapping part, the DCI for activating SPS transmitted in the USS will be received by multiple terminals. If the RNTI scrambling the DCI for activating SPS transmitted in the USS is the same as the CS-RNTI scrambling the DCI for UE-specific SPS initial activation, or the same as the GS-RNTI scrambling the DCI for group common SPS initial activation, other terminals may receive the DCI for activating SPS transmitted in the USS and activate the corresponding SPS according to the RNTI determined by successful decoding, resulting in the misactivation of SPS by other terminals.

[0078] Therefore, based on the embodiment, a new RNTI can be introduced as the first RNTI, which is different from the GS-RNTI scrambling the DCI for group common SPS initial activation and the CS-RNTI scrambling the DCI for UE-specific SPS initial activation, so as to avoid the misactivation of SPS by other terminals.

[0079] In one embodiment, the first RNTI is the same as the GS-RNTI scrambling the DCI for group common SPS initial activation.

[0080] Although the introduction of a new RNTI as the first RNTI can avoid the misactivation of SPS by other terminals, the introduction of a new RNTI requires relatively large adjustment of the communication architecture, and the misactivation of SPS generally only occurs when there is a partial overlap between the CSS and the USS, which is not very common.

[0081] Therefore, the embodiment can also reuse the GS-RNTI scrambling the DCI for group common SPS initial activation to scramble the DCI for activating SPS transmitted in the USS. After receiving the DCI for activating SPS transmitted in the USS, the terminal can determine that the network side device needs to indicate the reactivation of group common SPS after determining that the RNTI scrambling the DCI is the GS-RNTI. Accordingly, this is conducive to reducing the modification of the communication architecture.

[0082] Figure 5 is another schematic flowchart of a method for determining the reactivation of semi-persistent scheduling according to an embodiment of the present disclosure. As shown in Figure 5 the type of semi-persistent scheduling determined to be reactivated according to the indication of the network side device comprises:

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

[0084] In one embodiment, the protocol can pre-agree with the terminal that when the terminal supports receiving DCI for activating group common SPS in USS, when the terminal receives DCI encrypted by CS-RNTI in USS, it is assumed that the network side device instructs the terminal to reactivate group common SPS.

[0085] Then when the terminal itself supports receiving DCI for activating group common SPS in USS, if DCI encrypted by CS-RNTI is received in USS, it can be assumed that the network side device instructs the terminal to reactivate groupcommon SPS, thereby reactivating group common SPS, and it will not be considered that the network side device instructs the terminal to reactivate UE-specific SPS.

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

[0087] When the terminal receives the DCI encrypted by CS-RNTI in the USS, it does not think that the network-side device instructs the terminal to reactivate the UE-specific SPS, that is, the UE-specific SPS will not be reactivated. This may result in the terminal not being able to reactivate the UE-specific SPS smoothly even if the UE-specific SPS is configured for the terminal. Therefore, in this case, the network-side device can choose to only configure the group common SPS configuration for the terminal instead of configuring the UE-specific SPS configuration for the terminal to reduce resource waste.

[0088] Of course, the network side device can also configure both the group common SPS configuration and the UE-specific SPS configuration for the terminal, and the specific selection can be made according to actual needs.

[0089] Figure 6 FIG. 1 is a schematic flow chart showing another method for determining reactivation of semi-static scheduling according to an embodiment of the present disclosure. Figure 6As shown, the terminal is configured with group common SPS and / or UE-specific SPS on the first frequency domain resource, and the type of reactivated semi-static scheduling is determined according to the indication of the network side device, which includes:

[0090] In step S601, the type is determined according to the RNTI with which the network side device scrambles the DCI transmitted on the second frequency domain resource.

[0091] It should be noted that the DCI can be in the USS of the terminal, and in the case that the second frequency domain resource is exclusively configured for the terminal, the DCI can be in the USS of the terminal or not.

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

[0093] Of course, the network side device can also transmit the DCI scrambled by RNTI on the first frequency domain resource to indicate the type of SPS that the terminal needs to reactivate, which can be selected by the network side device as needed.

[0094] 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 part (BWP), and the second frequency domain resource includes a second BWP.

[0095] Figure 7 Another time-domain diagram for reactivation is shown according to an embodiment of the present disclosure.

[0096] As Figure 7As shown, for example, 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 activate the group common SPS in slot #n. The network side device can send UE-specific PDCCH (which carries RNTI-encrypted DCI) to the terminal on the second CC, for example, in slot #n+5, to instruct the terminal to reactivate the group common SPS on the first CC. After the terminal reactivates the group common SPS, it can receive the PDSCH of the group common SPS in slot #n+6 according to the configuration of the group common SPS.

[0097] For example, 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 DCI encrypted by RNTI to the terminal in the USS on the second BWP to instruct the terminal to reactivate group common SPS or reactivate UE-specific SPS.

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

[0099] Figure 8 FIG. 1 is a schematic flow chart showing another method for determining reactivation of semi-static scheduling according to an embodiment of the present disclosure. Figure 8 As shown, the type of semi-persistent scheduling to be reactivated according to the instruction of the network side device includes:

[0100] In step S801, a DCI for activating an SPS transmitted in a USS is received;

[0101] In step S802, the type is determined according to the identifier of the USS where the DCI is located.

[0102] In one embodiment, the terminal may pre-store a correspondence between an identifier (eg, ID) of the USS and a type of the SPS, such as that agreed upon by a protocol or pre-configured by a network-side device.

[0103] After receiving the DCI for activating 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 according to the correspondence between the identifier and the type of the SPS.

[0104] Figure 9 FIG. 4 is a time domain schematic diagram showing another reactivation according to an embodiment of the present disclosure.

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

[0106] The terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to activate the group common SPS in slot#n. The network-side device can send a UE-specific PDCCH to the terminal in slot#n+5, in which the DCI encrypted with the RNTI carried is in the USS corresponding to USS#2. The terminal receives the DCI carried by the UE-specific PDCCH transmitted in slot#n+5, and can determine that the DCI is in the USS corresponding to USS#2, and further determine that USS#2 corresponds to the group common SPS, thereby activating the groupcommon SPS. Subsequently, the downlink information can be received on the PDSCH corresponding to the group common SPS (for example, located in slot#n+6).

[0107] In addition, the terminal can also send a UE-specific PDCCH to the terminal in the USS corresponding to USS#1 as needed. For example, the UE-specific PDCCH is sent to the terminal on slot#n+4. The terminal receives the DCI carried by the UE-specific PDCCH transmitted on slot#n+4. It can determine that the DCI is in the USS corresponding to USS#1, and then determine that USS#1 corresponds to the UE-specific SPS, thereby activating the UE-specific SPS. Subsequently, the downlink information can be received on the PDSCH corresponding to the UE-specific SPS (for example, located in slot#n+7).

[0108] In the above embodiments, the network-side device instructs the terminal which SPS to activate 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 the RNTI scrambled in the DCI. The following embodiments primarily illustrate the technical solution of the present disclosure with reference to explicit indication.

[0109] In one embodiment, determining the type of reactivated semi-persistent scheduling according to an instruction of a network-side device includes:

[0110] The type is determined according to the indication information sent by the network side device.

[0111] In one embodiment, the indication information includes at least one of the following: medium access control layer control element MACCE; radio access control RRC signaling; DCI.

[0112] In one embodiment, the network-side device may explicitly indicate the type of SPS that the terminal needs to activate, such as by sending one or more indication messages to the terminal, wherein the content carried in the indication message directly indicates the type. The indication message may be sent in the form of a MAC CE, RRC signaling, or DCI, and the specific selection may be made as needed.

[0113] Figure 10 This is a schematic flow chart illustrating a method for reactivating semi-persistent scheduling according to an embodiment of the present disclosure. The method for reactivating semi-persistent scheduling illustrated in this embodiment can be performed by a network-side device that can communicate with a terminal, including but not limited to mobile phones, tablets, wearable devices, sensors, IoT devices, and other communication 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.

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

[0115] In some cases, some terminals fail to correctly decode the instructions sent by the network side device, resulting in the failure to correctly determine the SPS that needs to be activated. The network side device can determine whether the terminal has correctly decoded the instructions based on the information fed back by the terminal. If it is determined that the terminal has not correctly decoded the instructions, the network side device can instruct the end point again and reactivate the SPS.

[0116] There can be multiple types of SPS configured by the network side device for the terminal. The following embodiments mainly provide an illustrative description of the technical solution of the present disclosure by focusing on the configuration of group common SPS and UE-specific SPS configured by the network side device for the terminal.

[0117] For group common SPS, during initial activation, the downlink control information DCI (Downlink Control Information) encrypted by the group scheduled radio network temporary identity GS-RNTI (Group Scheduled-Radio Network Temporary Identity) can be transmitted in the group common physical downlink control channel groupcommon PDCCH (Physical Downlink Control Channel) to indicate activation. After receiving the indication, the terminal can decode the DCI and determine the RNTI used for decoding, and then determine that the SPS to be activated is the group common SPS based on the RNTI (specifically, the value of the RNTI).

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

[0119] The terminal may be a terminal supporting MBS (Multicast Broadcast Service), and the terminal may also support unicast service.

[0120] The above-mentioned group common SPS can be configured for terminals in the same group. However, since the channel transmission conditions of different terminals belonging to the same group may be different, some terminals can correctly demodulate and determine the RNTI, while some terminals cannot correctly demodulate and determine the RNTI. The terminals that correctly demodulate and determine the RNTI can return confirmation information ACK to the network side device, and the terminals that cannot correctly demodulate and determine the RNTI can return non-confirmation information NACK to the network side device. The network side device can determine which terminals have not correctly demodulated and determined the RNTI based on the feedback received.

[0121] For a terminal that has not correctly demodulated the RNTI, the network side device can re-indicate the terminal to reactivate the group common SPS. At present, one way to re-indicate the terminal is to use the UE-specific PDCCH, but the UE-specific PDCCH is mainly used to activate the UE-specific SPS. When the UE-specific PDCCH is used to activate the group common SPS, the terminal has difficulty in distinguishing which type of SPS the UE-specific PDCCH is used to activate.

[0122] As shown in Figure 10 The reactivation method of the semi-static scheduling can include the following steps:

[0123] In step S1001, the type of the semi-static scheduling SPS that the terminal is expected to reactivate is determined.

[0124] In step S1002, the terminal is indicated to determine the type.

[0125] In one embodiment, when indicating the terminal to reactivate the SPS, the network side device can determine the type of the semi-static scheduling SPS that the terminal is expected to reactivate as needed, and then indicate the type of the SPS that the terminal is expected to reactivate. In this way, the terminal can accurately determine the type of the SPS that needs to be reactivated, reactivate the SPS of the corresponding type, and communicate with the network side device smoothly through the reactivated SPS, for example, receive downlink information, thereby avoiding the problem that the terminal cannot communicate with the network side device smoothly due to reactivation of the wrong type of SPS, and affecting the communication effect.

[0126] In one embodiment, the type includes at least one of the following: group common semi-static scheduling (group common SPS); and UE-specific semi-static scheduling (UE-specific SPS).

[0127] The network side device can indicate the terminal to reactivate the group common SPS or reactivate the UE-specific SPS. When the terminal determines to reactivate the group common SPS according to the indication, the terminal can reactivate the group common SPS and communicate 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 indication, the terminal can reactivate the UE-specific SPS and communicate with the network side device according to the configuration of the UE-specific SPS.

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

[0129] Explicit indication, implicit indication.

[0130] The way in which the network side device indicates the terminal may be an explicit indication, such as sending one or more messages to the terminal, and the content carried in the message directly indicates the type; the way in which the network side device indicates the terminal may be an implicit indication, such as sending information to the terminal, the information has other functions and is not directly used to indicate the type, and the terminal can determine the type of SPS that needs to be reactivated based on the information in some way, for example, the information is a DCI in the user-specific search space USS (User-Specific Search Space), and the DCI is encrypted by RNTI. The DCI is not used to indicate the type, but the terminal can determine the type based on the RNTI of the scrambled DCI.

[0131] like Figure 2 As shown, for example, for a terminal supporting MBS, the network side device configures at least the group common SPS configuration for the terminal, wherein 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 in slot #n+1 and the next one is in slot #n+6, with an interval of 5 slots.

[0132] The network-side device initially activates the group common SPS in slot #n. For example, in slot #n, the group common PDCCH is sent to the terminals belonging to the same group. The DCI in the group common PDCCH is scrambled by GS-RNTI. If the terminal correctly demodulates and determines the RNTI corresponding to the DCI, it can communicate with the network-side device according to the configuration of the group common PDCCH, for example, receiving the PDSCH of the group common SPS in slot #n+1 and slot #n+6.

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

[0134] In addition, if the network-side device also configures UE-specific SPS configuration for the terminal, DCI scrambled by CS-RNTI can be transmitted in USS for reactivation.

[0135] Figure 11 FIG. 1 is a schematic flow chart showing another method for reactivating semi-persistent scheduling according to an embodiment of the present disclosure. Figure 11 As shown, the instructing the terminal to enable the terminal to determine the type includes:

[0136] In step S1101, a radio network temporary identifier RNTI for scrambling downlink control information DCI for activating SPS in a user equipment-specific search space USS is determined according to the type;

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

[0138] In step S1103, the DCI is transmitted to the terminal in the USS, so that the terminal determines the type according to the RNTI used to scramble the DCI.

[0139] It should be noted that the terminal may determine whether the DCI is for activating SPS in a predetermined manner, and the judgment condition includes at least one of the following:

[0140] The CRC of the DCI is scrambled by the CS-RNTI or the GS-RNTI.

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

[0142] If DFI is present in the DCI, the DFI field (DCI format indicator) is 0;

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

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

[0145] In one embodiment, the network side device may transmit DCI for activating SPS in the USS, for example, the DCI is 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.

[0146] The terminal may pre-store a correspondence between the RNTI and the type of SPS, such as that agreed upon by the protocol or pre-configured by the network-side device. After the terminal receives the DCI for activating the SPS in the USS, it may determine the RNTI that scrambles the DCI, for example, by descrambling the DCI through the RNTI, and the RNTI that successfully descrambles the DCI corresponds to the RNTI that scrambled the DCI, thereby determining the RNTI that scrambled the DCI based on the RNTI that successfully descrambled the DCI, and then determining the type of SPS corresponding to the RNTI that scrambled the DCI based on the RNTI that scrambled the DCI and the correspondence.

[0147] like Figure 4 As shown, the terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to activate the group common SPS in slot #n. The network side device can send a UE-specific PDCCH (carrying RNTI-encrypted DCI) 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 receive the PDSCH of the group common SPS in slot #n+6 according to the configuration of the group common SPS.

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

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

[0150] The network-side device and the terminal may pre-store a correspondence between RNTI and SPS type, in which the first RNTI corresponds to the group common SPS and the second RNTI corresponds to the UE-specific SPS. When the network-side device needs to instruct the terminal to reactivate the group common SPS, it may scramble the DCI using the first RNTI; when it needs to instruct the terminal to reactivate the UE-specific SPS, it may scramble the DCI using the second RNTI.

[0151] Among them, the first RNTI and / or the second RNTI may be different from the RNTI in the related technology, or the RNTI in the related technology may be reused, and the specific selection can be made according to needs.

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

[0153] The DCI for the initial activation 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 the initial activation of UE-specific SPS is in the USS, and the information transmitted in the USS is generally only received by the specified terminal.

[0154] However, in some cases, there will be partial overlap between CSS and USS. If the DCI transmitted in USS for activating SPS happens to be located in this overlapping part, then the DCI transmitted in USS for activating SPS will be received by multiple terminals. If the RNTI of the DCI transmitted in USS for activating SPS is scrambled, it is the same as the CS-RNTI used to scramble the DCI for initial activation of UE-specific SPS, or the same as the GS-RNTI used to scramble the DCI for initial activation of group common SPS. Then other terminals may receive the DCI transmitted in USS for activating SPS and activate the corresponding SPS according to the RNTI determined by successful decoding, resulting in incorrect activation of SPS by other terminals.

[0155] 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 the initial activation of the group common SPS and the CS-RNTI that scrambles the DCI for the initial activation of the UE-specific SPS, thereby avoiding incorrect activation of the SPS by other terminals.

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

[0157] Although introducing a new RNTI as the first RNTI can avoid erroneous activation of SPS by other terminals, the introduction of the new RNTI makes relatively large adjustments to the communication architecture, and erroneous activation of SPS generally only occurs when there is partial overlap between CSS and USS, while partial overlap between CSS and USS is not very common.

[0158] Therefore, this embodiment can also reuse the GS-RNTI that scrambles the DCI for the initial activation of the group common SPS to scramble the DCI for activating the SPS transmitted in the USS. After the terminal receives the DCI for activating the SPS transmitted in the USS, after determining that the RNTI that scrambled the DCI is the GS-RNTI, it can be determined that the network-side device needs to instruct the reactivation of the group common SPS. Accordingly, it is helpful to reduce modifications to the communication architecture.

[0159] Figure 12 FIG. 1 is a schematic flow chart showing another method for reactivating semi-static scheduling according to an embodiment of the present disclosure. Figure 12 As shown, the instructing the terminal to enable the terminal to determine the type includes:

[0160] In step S1201, in response to determining that the terminal supports receiving DCI for activating the group common SPS in the USS and expecting the terminal to reactivate the group common SPS, scrambling the DCI transmitted in the USS by using the CS-RNTI;

[0161] In step S1202, the DCI is transmitted to the terminal in the USS, so that the terminal determines to reactivate the group common SPS according to the CS-RNTI that scrambles the DCI.

[0162] In one embodiment, the protocol can pre-agree with the terminal that when the terminal supports receiving DCI for activating group common SPS in USS, when the terminal receives DCI encrypted by CS-RNTI in USS, it is assumed that the network side device instructs the terminal to reactivate group common SPS.

[0163] Then when it is determined that the terminal itself supports receiving DCI for activating group common SPS in USS, if the terminal needs to reactivate group common SPS, it can receive DCI encrypted by CS-RNTI in USS. After the terminal receives DCI encrypted by CS-RNTI in USS, it can be assumed that the network side device instructs the terminal to reactivate groupcommon SPS, thereby reactivating group common SPS, and it will not be considered that the network side device instructs the terminal to reactivate UE-specific SPS.

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

[0165] When the terminal receives the DCI encrypted by CS-RNTI in the USS, it does not think that the network-side device instructs the terminal to reactivate the UE-specific SPS, that is, the UE-specific SPS will not be reactivated. This may result in the terminal not being able to reactivate the UE-specific SPS smoothly even if the UE-specific SPS is configured for the terminal. Therefore, in this case, the network-side device can choose to only configure the group common SPS configuration for the terminal instead of configuring the UE-specific SPS configuration for the terminal to reduce resource waste.

[0166] Of course, the network side device can also configure both the group common SPS configuration and the UE-specific SPS configuration for the terminal, and the specific selection can be made according to actual needs.

[0167] Figure 13 FIG. 1 is a schematic flow chart showing another method for reactivating semi-static scheduling according to an embodiment of the present disclosure. Figure 13 As shown, the terminal is configured with a group common SPS and / or a UE-specific SPS on the first frequency domain resource, and the instructing the terminal to enable the terminal to determine the type includes:

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

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

[0170] In step S1303, the DCI is transmitted to the terminal on the second frequency domain resources, so that the terminal determines the type according to the RNTI used to scramble the DCI.

[0171] It should be noted that the DCI may be in the USS of the terminal, and when the second frequency domain resources are exclusively configured for the terminal, the DCI may be in the USS of the terminal or may not be in the USS of the terminal.

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

[0173] Of course, the network side device may also transmit DCI encrypted by RNTI on the first frequency domain resource to indicate the type of SPS that the terminal needs to reactivate, and the specific selection may be made by the network side device according to needs.

[0174] In one embodiment, the first frequency domain resources include a first component carrier CC, and the second frequency domain resources include a second CC; and / or the first frequency domain resources include a first bandwidth part BWP, and the second frequency domain resources include a second BWP.

[0175] like Figure 7 As shown, for example, 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 activate the group common SPS in slot #n. The network side device can send UE-specific PDCCH (which carries RNTI-encrypted DCI) to the terminal on the second CC, for example, in slot #n+5, to instruct the terminal to reactivate the group common SPS on the first CC. After the terminal reactivates the group common SPS, it can receive the PDSCH of the group common SPS in slot #n+6 according to the configuration of the group common SPS.

[0176] For example, 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 DCI encrypted by RNTI to the terminal in the USS on the second BWP to instruct the terminal to reactivate group common SPS or reactivate UE-specific SPS.

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

[0178] Figure 14 FIG. 1 is a schematic flow chart showing another method for reactivating semi-static scheduling according to an embodiment of the present disclosure. Figure 14 As shown, the instructing the terminal to enable the terminal to determine the type includes:

[0179] In step S1401, the identification of the USS is determined according to the type;

[0180] In step S1402, the DCI scrambled by the CS-RNTI is transmitted to the terminal in the USS corresponding to the identifier, so that the terminal determines the type according to the identifier of the USS where the DCI is located.

[0181] In one embodiment, the network-side device and the terminal may pre-store a correspondence between the identifier (e.g., ID) of the USS and the type of the SPS. The network-side device may first determine the type of SPS that the terminal needs to reactivate, and then, based on the correspondence between the identifier of the USS and the type of the SPS, query the identifier of the USS corresponding to the determined type, and then transmit the DCI for activating the SPS to the terminal in the USS corresponding to the queried USS identifier. After the terminal receives the DCI for activating the SPS in the USS, it may determine the identifier of the USS where the DCI is located, and then, based on the correspondence between the identifier and the type of the SPS, identify the corresponding type of the SPS.

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

[0183] The terminal fails to correctly demodulate and determine the RNTI corresponding to the DCI used to activate the group common SPS in slot#n. The network-side device can send a UE-specific PDCCH to the terminal in slot#n+5, in which the DCI encrypted with the RNTI carried is in the USS corresponding to USS#2. The terminal receives the DCI carried by the UE-specific PDCCH transmitted in slot#n+5, and can determine that the DCI is in the USS corresponding to USS#2, and further determine that USS#2 corresponds to the group common SPS, thereby activating the groupcommon SPS. Subsequently, the downlink information can be received on the PDSCH corresponding to the group common SPS (for example, located in slot#n+6).

[0184] In addition, the terminal can also send a UE-specific PDCCH to the terminal in the USS corresponding to USS#1 as needed. For example, the UE-specific PDCCH is sent to the terminal on slot#n+4. The terminal receives the DCI carried by the UE-specific PDCCH transmitted on slot#n+4. It can determine that the DCI is in the USS corresponding to USS#1, and then determine that USS#1 corresponds to the UE-specific SPS, thereby activating the UE-specific SPS. Subsequently, the downlink information can be received on the PDSCH corresponding to the UE-specific SPS (for example, located in slot#n+7).

[0185] In the above embodiments, the network-side device instructs the terminal which SPS to activate 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 the RNTI scrambled in the DCI. The following embodiments primarily illustrate the technical solution of the present disclosure with reference to explicit indication.

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

[0187] Sending indication information to the terminal to indicate the type.

[0188] In one embodiment, the indication information includes at least one of the following: medium access control layer control element MACCE; radio access control RRC signaling; DCI.

[0189] In one embodiment, the network-side device may explicitly indicate the type of SPS that the terminal needs to activate, such as by sending one or more indication messages to the terminal, wherein the content carried in the indication message directly indicates the type. The indication message may be sent in the form of a MAC CE, RRC signaling, or DCI, and the specific selection may be made as needed.

[0190] Corresponding to the aforementioned embodiments of the semi-persistent scheduling reactivation determination method and the semi-persistent scheduling reactivation method, the present disclosure also provides embodiments of a semi-persistent scheduling reactivation determination device and a semi-persistent scheduling reactivation device.

[0191] The embodiments of the present disclosure illustrate a semi-persistent scheduling reactivation determination device, which can be applied to terminals, including but not limited to mobile phones, tablet computers, wearable devices, sensors, IoT devices, and other communication devices. The terminals 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.

[0192] In one embodiment, the apparatus comprises one or more processors configured to:

[0193] The type of reactivated semi-persistent scheduling is determined according to the instruction of the network-side device.

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

[0195] Group common semi-persistent scheduling group common SPS;

[0196] UE-specific semi-persistent scheduling (SPS).

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

[0198] Explicit indication, implicit indication.

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

[0200] receiving downlink control information DCI for activating SPS transmitted in a user equipment-specific search space USS;

[0201] The type is determined according to the Radio Network Temporary Identifier (RNTI) used to scramble the DCI.

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

[0203] In response to the RNTI for scrambling the DCI being the first RNTI, determining to reactivate the group common SPS; and / or in response to the RNTI for scrambling the DCI being the second RNTI, determining to reactivate the UE-specific SPS.

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

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

[0206] In one embodiment, the processor is configured to: in response to supporting receiving a DCI for activating the group common SPS in the USS, determine to reactivate the group common SPS when the DCI scrambled by the CS-RNTI is received in the USS.

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

[0208] 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 determine the type based on the RNTI of the DCI transmitted by the network side device on the second frequency domain resources.

[0209] In one embodiment, the first frequency domain resources include a first component carrier CC, and the second frequency domain resources include a second CC; and / or the first frequency domain resources include a first bandwidth part BWP, and the second frequency domain resources include a second BWP.

[0210] In one embodiment, the processor is configured to: receive DCI for activating SPS transmitted in a USS; and determine the type according to an identifier of the USS where the DCI is located.

[0211] In one embodiment, the processor is configured to: determine the type according to indication information sent by the network side device.

[0212] In one embodiment, the indication information includes at least one of the following: medium access control layer control element MACCE; radio access control RRC signaling; DCI.

[0213] The embodiments of the present disclosure illustrate a semi-persistent scheduling reactivation device, which can be applied to network-side devices that can communicate with terminals, including but not limited to mobile phones, tablets, wearable devices, sensors, IoT devices, and other communication 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.

[0214] In one embodiment, the apparatus comprises one or more processors configured to:

[0215] Determine the type of semi-persistent scheduling (SPS) that the terminal is expected to reactivate;

[0216] The terminal is instructed to determine the type.

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

[0218] Group common semi-persistent scheduling group common SPS;

[0219] UE-specific semi-persistent scheduling (SPS).

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

[0221] Explicit indication, implicit indication.

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

[0223] Determine, according to the type, a radio network temporary identifier RNTI for scrambling downlink control information DCI for activating SPS in a user equipment-specific search space USS;

[0224] Scrambling the DCI using the determined RNTI;

[0225] The DCI is transmitted to the terminal in the USS, so that the terminal determines the type according to the RNTI used to scramble the DCI.

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

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

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

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

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

[0231] In response to determining that the terminal supports receiving DCI for activating the group common SPS in the USS and that the terminal is expected to reactivate the group common SPS, scrambling the DCI transmitted in the USS by using the CS-RNTI;

[0232] The DCI is transmitted to the terminal in the USS, so that the terminal determines to reactivate the group common SPS according to the CS-RNTI that scrambles the DCI.

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

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

[0235] Determine, according to the type, an RNTI for scrambling the DCI transmitted on the second frequency domain resources;

[0236] Scrambling the DCI using the determined RNTI;

[0237] The DCI is transmitted to the terminal on a second frequency domain resource, so that the terminal determines the type according to the RNTI used to scramble the DCI.

[0238] In one embodiment, the first frequency domain resources include a first component carrier CC, and the second frequency domain resources include a second CC; and / or the first frequency domain resources include a first bandwidth part BWP, and the second frequency domain resources include a second BWP.

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

[0240] determining an identification of the USS according to the type;

[0241] The DCI scrambled by the CS-RNTI is transmitted to the terminal in the USS corresponding to the identifier, so that the terminal determines the type according to the identifier of the USS where the DCI is located.

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

[0243] Sending indication information to the terminal to indicate the type.

[0244] In one embodiment, the indication information includes at least one of the following: medium access control layer control element MACCE; radio access control RRC signaling; DCI.

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

[0246] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0247] An embodiment of the present disclosure further proposes a communication device, such as the above-mentioned terminal, 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-mentioned embodiments is implemented.

[0248] An embodiment of the present disclosure further proposes a communication device, such as the above-mentioned network-side device, 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-mentioned embodiments is implemented.

[0249] An embodiment of the present disclosure further provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the steps in the method for determining reactivation of semi-persistent scheduling described in any of the above embodiments.

[0250] Embodiments of the present disclosure further provide a computer readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the method for reactivation of semi-persistent scheduling according to any of the above embodiments are implemented.

[0251] As shown in Figure 15 , Figure 15 is a schematic block diagram of an apparatus 1500 for reactivation of semi-persistent scheduling according to embodiments of the present disclosure. The apparatus 1500 can be provided as a base station. Referring 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 portion specific to the wireless interface, the processing component 1522 can further include one or more processors. One of the processors in the processing component 1522 can be configured to implement the method for reactivation of semi-persistent scheduling according to any of the above embodiments.

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

[0253] Referring to Figure 16 , the apparatus 1600 can 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.

[0254] The processing component 1602 usually controls overall operations of the apparatus 1600, such as operations associated with display, telephone call, data communication, camera operation and recording operation. The processing component 1602 can include one or more processors 1620 to execute instructions to complete all or part of the steps of the method for reactivation determination of semi-persistent scheduling described above. Further, the processing component 1602 can include one or more modules to facilitate interaction between the processing component 1602 and other components. For example, the processing component 1602 can include a multimedia module to facilitate the interaction between the multimedia component 1608 and the processing component 1602.

[0255] The memory 1604 is configured to store various types of data to support operations on the device 1600. Examples of such data include instructions for any application or method operating on the device 1600, contact data, phone book data, messages, pictures, videos, etc. The 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 memory, flash memory, magnetic disk, or optical disk.

[0256] The power supply component 1606 provides power to the various components of the device 1600. The power supply component 1606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 1600.

[0257] The 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 touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1608 includes a front camera and / or a rear camera. When the device 1600 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.

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

[0259] I / O interface 1612 provides an interface between processing component 1602 and peripheral interface modules, such as a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, volume buttons, a start button, and a lock button.

[0260] Sensor assembly 1614 includes one or more sensors for providing various aspects of the status assessment of device 1600. For example, sensor assembly 1614 can detect the open / closed state of device 1600, the relative positioning of components, such as the display and keypad of device 1600. Sensor assembly 1614 can also detect 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 changes in the temperature of device 1600. Sensor assembly 1614 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1614 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1614 can also include an accelerometer, a gyroscope, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0261] The communication component 1616 is configured to facilitate wired or wireless communication between the device 1600 and other devices. The device 1600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G LTE, 5G NR, or a combination thereof. In an exemplary embodiment, the communication component 1616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1616 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0262] 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.

[0263] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is further provided, such as memory 1604 including instructions. The instructions may be executed by processor 1620 of apparatus 1600 to implement the above-described semi-persistently scheduled reactivation determination method. For example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, or the like.

[0264] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the disclosure herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0265] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

[0266] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements that are inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device that includes the element.

[0267] The above is a detailed introduction to the methods and devices provided in the embodiments of the present disclosure. Specific examples are used herein to illustrate the principles and implementation methods of the present disclosure. The description of the above embodiments is only used to help understand the methods and core ideas of the present disclosure. At the same time, for those skilled in the art, according to the ideas of the present disclosure, there may be changes in the specific implementation methods and application scopes. In summary, the contents of this specification should not be understood as limiting the present disclosure.

Claims

1. A method for determining reactivation of semi-persistent scheduling, characterized in that: Executed by a terminal, the method includes: Determining a type of reactivated semi-persistent scheduling according to an instruction from a network-side device, the type comprising at least one of: group common semi-persistent scheduling (SPS); user equipment-specific semi-persistent scheduling (UE-specific SPS); a DCI for activating the group common SPS is carried in a CSS, and a DCI for activating the UE-specific SPS is carried in a USS, where the USS and the CSS overlap; The determining of the type of reactivated semi-persistent scheduling according to an instruction of a network-side device includes: receiving a DCI transmitted in a USS for activating an SPS; The type is determined according to an identifier of the USS where the DCI is located.

2. The method according to claim 1, characterized in that The indication from the network side device includes at least one of the following: Explicit indication, implicit indication.

3. The method according to claim 1, characterized in that Determining the type of reactivated semi-persistent scheduling according to an instruction of a network-side device includes: receiving downlink control information DCI for activating SPS transmitted in a user equipment-specific search space USS; The type is determined according to the Radio Network Temporary Identifier (RNTI) used to scramble the DCI.

4. The method according to claim 3, characterized in that Determining the type according to the RNTI for scrambling the DCI includes: In response to the RNTI for scrambling the DCI being the first RNTI, determining to reactivate the group common SPS; and / or In response to the RNTI used to scramble the DCI being the second RNTI, determining to reactivate the UE-specific SPS.

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

6. The method according to claim 4, characterized in that The first RNTI is the same as the GS-RNTI used to scramble the DCI for the initial activation of the group common SPS.

7. The method according to claim 1, characterized in that Determining the type of reactivated semi-persistent scheduling according to an instruction of a network-side device includes: In response to supporting reception of DCI for activating the group common SPS in the USS, when the DCI scrambled by the CS-RNTI is received in the USS, it is determined to reactivate the group common SPS.

8. The method according to claim 7, characterized in that The terminal is configured with group common SPS but not with UE-specific SPS.

9. The method according to claim 1, characterized in that The terminal is configured with a group common SPS and / or a UE-specific SPS on the first frequency domain resource, and determining the type of reactivated semi-persistent scheduling according to an instruction of the network side device includes: The type is determined according to the RNTI of the DCI transmitted by the network side device on the second frequency domain resource.

10. The method according to claim 9, characterized in that The first frequency domain resources include a first component carrier CC, and the second frequency domain resources include a second CC; and / or The first frequency domain resources include a first bandwidth part BWP, and the second frequency domain resources include a second BWP.

11. The method according to claim 1, characterized in that Determining the type of reactivated semi-persistent scheduling according to an instruction of a network-side device includes: The type is determined according to the indication information sent by the network side device.

12. The method according to claim 11, characterized in that The indication information includes at least one of the following: Medium Access Control Layer Control Element MAC CE; Radio access control RRC signaling; DCI.

13. A semi-persistent scheduling reactivation method, characterized in that: The method is performed by a network-side device and includes: Determine the type of semi-persistent scheduling (SPS) that the terminal is expected to reactivate; Instructing the terminal to determine the type, where the type includes at least one of: group common semi-persistent scheduling (SPS); user equipment-specific semi-persistent scheduling (UE-specific SPS); a DCI for activating the group common SPS is carried in a CSS, and a DCI for activating the UE-specific SPS is carried in a USS, where the USS and the CSS overlap; The step of instructing the terminal to determine the type includes: A DCI for activating the SPS is sent to the terminal in the USS, and an identifier of the USS where the DCI is located is used to determine the type.

14. The method according to claim 13, characterized in that The indication from the network side device includes at least one of the following: Explicit indication, implicit indication.

15. The method according to claim 14, characterized in that The instructing the terminal to determine the type includes: Determine, according to the type, a radio network temporary identifier RNTI for scrambling downlink control information DCI for activating SPS in a user equipment-specific search space USS; Scrambling the DCI using the determined RNTI; The DCI is transmitted to the terminal in the USS, so that the terminal determines the type according to the RNTI used to scramble the DCI.

16. The method according to claim 15, characterized in that The determining, according to the type, the RNTI for scrambling the DCI in the USS includes: In response to the terminal being expected to reactivate the group common SPS, scrambling the DCI using a first RNTI; and / or In response to the terminal being expected to reactivate the UE-specific SPS, the DCI is scrambled by a second RNTII.

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

18. The method according to claim 17, characterized in that The first RNTI is the same as the GS-RNTI used to scramble the DCI for the initial activation of the group common SPS.

19. The method according to claim 13, wherein The instructing the terminal to determine the type includes: In response to determining that the terminal supports receiving DCI for activating the group common SPS in the USS and that the terminal is expected to reactivate the group common SPS, scrambling the DCI transmitted in the USS by using the CS-RNTI; The DCI is transmitted to the terminal in the USS, so that the terminal determines to reactivate the group common SPS according to the CS-RNTI that scrambles the DCI.

20. The method according to claim 19, characterized in that The terminal is configured with group common SPS but not with UE-specific SPS.

21. The method according to claim 13, wherein The terminal is configured with a group common SPS and / or a UE-specific SPS on the first frequency domain resources, and the instructing the terminal to enable the terminal to determine the type includes: Determine, according to the type, an RNTI for scrambling the DCI transmitted on the second frequency domain resources; Scrambling the DCI using the determined RNTI; The DCI is transmitted to the terminal on a second frequency domain resource, so that the terminal determines the type according to the RNTI used to scramble the DCI.

22. The method according to claim 21, characterized in that The first frequency domain resources include a first component carrier CC, and the second frequency domain resources include a second CC; and / or The first frequency domain resources include a first bandwidth part BWP, and the second frequency domain resources include a second BWP.

23. The method according to claim 13, wherein The instructing the terminal to determine the type includes: Sending indication information to the terminal to indicate the type.

24. The method according to claim 23, wherein The indication information includes at least one of the following: Medium Access Control Layer Control Element MAC CE; Radio access control RRC signaling; DCI.

25. A semi-persistent scheduling reactivation determination device, characterized in that: comprising one or more processors configured to: Determining a type of reactivated semi-persistent scheduling according to an instruction from a network-side device, the type comprising at least one of: group common semi-persistent scheduling (SPS); user equipment-specific semi-persistent scheduling (UE-specific SPS); a DCI for activating the group common SPS is carried in a CSS, and a DCI for activating the UE-specific SPS is carried in a USS, where the USS and the CSS overlap; The determining of the type of reactivated semi-persistent scheduling according to an instruction of a network-side device includes: receiving a DCI transmitted in a USS for activating an SPS; The type is determined according to an identifier of the USS where the DCI is located.

26. A semi-statically scheduled reactivation device, characterized in that: comprising one or more processors configured to: Determine the type of semi-persistent scheduling (SPS) that the terminal is expected to reactivate; Instructing the terminal to determine the type, where the type includes at least one of: group common semi-persistent scheduling (SPS); user equipment-specific semi-persistent scheduling (UE-specific SPS); a DCI for activating the group common SPS is carried in a CSS, and a DCI for activating the UE-specific SPS is carried in a USS, where the USS and the CSS overlap; The step of instructing the terminal to determine the type includes: A DCI for activating the SPS is sent to the terminal in a USS, and an identifier of the USS where the DCI is located is used to determine the type.

27. A communication device, characterized in that: include: processor; memory for storing computer programs; When the computer program is executed by a processor, the semi-persistent scheduling reactivation determination method according to any one of claims 1 to 12 is implemented.

28. A communication device, characterized in that: include: processor; memory for storing computer programs; Wherein, when the computer program is executed by a processor, the semi-persistent scheduling reactivation method according to any one of claims 13 to 24 is implemented.

29. A computer-readable storage medium for storing a computer program, characterized in that: When the computer program is executed by a processor, the steps in the semi-persistent scheduling reactivation determination method according to any one of claims 1 to 12 are implemented.

30. A computer-readable storage medium for storing a computer program, characterized in that: When the computer program is executed by a processor, the steps in the semi-persistent scheduling reactivation method according to any one of claims 13 to 24 are implemented.

Images