CN114208356A

CN114208356A - Method and device for re-deactivating and determining semi-persistent scheduling

Info

Publication number: CN114208356A
Application number: CN202180003667.5A
Authority: CN
Inventors: 赵群
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2021-11-10
Filing date: 2021-11-10
Publication date: 2022-03-18
Also published as: WO2023082461A1; WO2023082110A1

Abstract

The disclosure relates to a method and a device for re-deactivating and determining semi-persistent scheduling, wherein the method for re-deactivating and determining semi-persistent scheduling comprises the following steps: and determining the type of the deactivated semi-persistent scheduling according to the indication of the network side equipment. According to the method and the device, when the network side equipment indicates the terminal to deactivate the SPS again, the type of the SPS which is deactivated again can be indicated by the terminal, accordingly, the terminal can accurately determine the type of the SPS which needs to be deactivated again, then the SPS of the corresponding type is deactivated again, the communication with the network side equipment through the configuration of the SPS which is deactivated again is stopped, and the influence on the communication effect caused by the fact that the SPS of the wrong type is deactivated again is avoided.

Description

Method and device for re-deactivating and determining semi-persistent scheduling

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method for determining reactivation of semi-persistent scheduling, a method for reactivating semi-persistent scheduling, a device for determining reactivation of semi-persistent scheduling, a device for reactivating semi-persistent scheduling, a communications device, and a computer-readable storage medium.

Background

In the related art, Semi-Persistent Scheduling (SPS) is proposed, which may configure periodic resources for a terminal, and after the SPS is activated, when downlink transmission is performed, downlink resource Scheduling may not be performed any more, and the terminal receives downlink transmission according to the configuration of the activated SPS, which is beneficial to saving signaling overhead.

The subsequent network side equipment can also instruct the terminal to deactivate the SPS as required, and the terminal stops receiving the downlink transmission according to the configuration of the SPS after the terminal deactivates the SPS according to the instruction.

And, multiple SPS may be configured for the terminal, and the network may instruct the terminal to deactivate one of the multiple SPS as needed. However, in some cases, the terminal cannot accurately distinguish which SPS is deactivated for the deactivation indication sent by the network, thereby causing some problems.

Disclosure of Invention

In view of this, embodiments of the present disclosure propose a method for determining reactivation of semi-persistent scheduling, a method for reactivating semi-persistent scheduling, a device for determining reactivation of semi-persistent scheduling, a device for reactivating semi-persistent scheduling, a communication device, and a computer-readable storage medium, so as to solve technical problems in the related art.

According to a first aspect of the embodiments of the present disclosure, a method for determining re-deactivation of semi-persistent scheduling is provided, where the method is performed by a terminal, and the method includes: and determining the type of the deactivated semi-persistent scheduling according to the indication of the network side equipment.

According to a second aspect of the embodiments of the present disclosure, a method for reactivating semi-persistent scheduling is provided, where the method is performed by a network side device, and the method includes: determining the type of semi-persistent scheduling (SPS) expected to be deactivated again by the terminal; indicating the terminal to enable the terminal to determine the type.

According to a third aspect of the embodiments of the present disclosure, there is provided a semi-persistent scheduled re-deactivation determining apparatus, including one or more processors configured to: and determining the type of the deactivated semi-persistent scheduling according to the indication of the network side equipment.

According to a fourth aspect of the embodiments of the present disclosure, a semi-statically scheduled re-deactivation apparatus is proposed, which includes one or more processors configured to: determining the type of semi-persistent scheduling (SPS) expected to be deactivated again by the terminal; indicating the terminal to enable the terminal to determine the type.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a communication apparatus including: a processor; a memory for storing a computer program; wherein the computer program, when executed by a processor, implements the above-described method of semi-persistent scheduling re-deactivation determination.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a communication apparatus including: a processor; a memory for storing a computer program; wherein the computer program, when executed by a processor, implements the above-described method of semi-persistent scheduling re-deactivation.

According to a seventh aspect of embodiments of the present disclosure, a computer-readable storage medium is proposed, for storing a computer program, which when executed by a processor, implements the steps in the above-mentioned method for determining re-deactivation of semi-persistent scheduling.

According to an eighth aspect of embodiments of the present disclosure, a computer-readable storage medium is proposed for storing a computer program, which when executed by a processor, implements the steps in the above-mentioned method for re-deactivation of semi-persistent scheduling.

According to the embodiment of the disclosure, when the network side equipment indicates the terminal to deactivate the SPS again, the network side equipment can indicate the type of the SPS deactivated again by the terminal, so that the terminal can accurately determine the type of the SPS needing to be deactivated again, further deactivate the SPS of the corresponding type again, stop communicating with the network side equipment through the configuration of the SPS deactivated again, and avoid influencing the communication effect due to the fact that the SPS of the wrong type is deactivated again.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.

Fig. 1 is a schematic flow chart diagram illustrating a method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure.

Fig. 2 is a schematic diagram illustrating a configuration of a group common SPS according to an embodiment of the present disclosure.

Fig. 3 is a schematic flow chart diagram illustrating another method for semi-statically scheduled re-deactivation determination, according to an embodiment of the present disclosure.

Fig. 4 is a time domain diagram illustrating a re-deactivation according to an embodiment of the present disclosure.

Fig. 5 is a schematic flow chart diagram illustrating still another method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure.

Fig. 6 is a schematic flow chart diagram illustrating still another method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure.

Fig. 7 is a time domain schematic diagram illustrating another re-deactivation according to an embodiment of the present disclosure.

Fig. 8 is a schematic flow chart diagram illustrating still another method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure.

Fig. 9 is a time domain schematic diagram illustrating yet another re-deactivation according to an embodiment of the present disclosure.

Fig. 10 is a schematic flow chart diagram illustrating a method for semi-statically scheduled re-deactivation, according to an embodiment of the present disclosure.

Fig. 11 is a schematic flow chart diagram illustrating another method for semi-statically scheduled re-deactivation according to an embodiment of the present disclosure.

Fig. 12 is a schematic flow chart diagram illustrating yet another method for re-deactivation of semi-persistent scheduling according to an embodiment of the present disclosure.

Fig. 13 is a schematic flow chart diagram illustrating yet another method for re-deactivation of semi-persistent scheduling according to an embodiment of the present disclosure.

Fig. 14 is a schematic flow chart diagram illustrating yet another method for re-deactivation of semi-persistent scheduling in accordance with an embodiment of the present disclosure.

Fig. 15 is a schematic block diagram illustrating an apparatus for re-deactivation of semi-persistent scheduling in accordance with an embodiment of the present disclosure.

Fig. 16 is a schematic block diagram illustrating an apparatus for re-deactivation determination for semi-persistent scheduling in accordance with an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

The terminology used in the embodiments of the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the present disclosure. As used in the disclosed embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

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

For the purposes of brevity and ease of understanding, the terms "greater than" or "less than", "above" or "below" are used herein when characterizing a size relationship. But it will be understood by those skilled in the art that: the term "greater than" also covers the meaning of "greater than or equal to," less than "also covers the meaning of" less than or equal to "; the term "higher than" encompasses the meaning of "higher than equal to" and "lower than" also encompasses the meaning of "lower than equal to".

Fig. 1 is a schematic flow chart diagram illustrating a method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure. The re-deactivation determination method for semi-persistent scheduling shown in this embodiment may be executed by a terminal, where the terminal includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, an internet of things device, and other communication devices. The terminal may communicate with a network side device, where the network side device includes, but is not limited to, a network side device in a 4G, 5G, 6G, and other communication systems, such as a base station, a core network, and the like.

In one embodiment, the network side device may configure one or more sets of SPS configurations for the terminal, and when a certain SPS needs to be used, may indicate the terminal, so that the terminal activates one of the SPS, and receives downlink information according to the activated SPS configuration.

The subsequent network side equipment can also instruct the terminal to deactivate the SPS as required, and the terminal stops receiving the downlink transmission according to the configuration of the SPS after deactivating the SPS according to the instruction of the network side equipment. However, in some cases, some terminals fail to correctly decode the indication sent by the network side device, which results in that the SPS that needs to be deactivated cannot be correctly determined, the network side device may determine whether the terminal correctly decodes the indication according to the information fed back by the terminal, and in the case that it is determined that the terminal does not correctly decode the indication, the network side device may again indicate the end point, and reactivate the SPS.

The SPS configured by the network side device for the terminal may be of various types, and the following embodiments mainly describe the technical solution of the present disclosure with respect to a configuration in which the network side device configures a group common semi-persistent scheduling group common SPS for the terminal and a configuration in which a user equipment-specific semi-persistent scheduling UE-specific SPS is configured.

For a Group common SPS, during initial deactivation, Downlink Control information DCI (Downlink Control information) scrambled by a Group Scheduled-Radio Network Temporary Identity GS-RNTI (Group Scheduled-Radio Network Temporary Identity) may be transmitted in a Group common Downlink Control Channel PDCCH (Physical Downlink Control Channel) to indicate deactivation, and after receiving the indication, the terminal may decode the DCI and determine an RNTI used for decoding, and then determine that the SPS to be deactivated is the Group common SPS according to the RNTI (which may be a value of the RNTI).

It should be noted that the scrambling of the DCI described in all embodiments of the present disclosure may specifically be a Cyclic Redundancy Check (CRC) for scrambling the DCI, and the present disclosure is simply referred to as scrambling the DCI.

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

The group common SPS may be configured to terminals in the same group (group), but channel transmission conditions may also be different for different terminals belonging to the same group, so some terminals may correctly demodulate and determine the RNTI, some terminals may not correctly demodulate and determine the RNTI, the terminals that correctly demodulate and determine the RNTI may return acknowledgment information ACK to the network side device, the terminals that do not correctly demodulate and determine the RNTI may return unacknowledged information NACK to the network side device, and the network side device may determine which terminals do not correctly demodulate and determine the RNTI according to the received feedback.

For a terminal that does not correctly demodulate and determine the RNTI, the network side device may re-instruct the terminal to re-deactivate the group common SPS. At present, a method for indicating a terminal again is implemented by a UE-specific PDCCH, which is a dedicated physical downlink control channel of a UE, but at present, the UE-specific PDCCH is mainly used for deactivating a UE-specific SPS, which is a dedicated semi-persistent scheduling of the UE, and when the UE-specific PDCCH is used for deactivating a group common SPS, it is difficult for the terminal to distinguish which type of SPS the UE-specific PDCCH deactivates.

As shown in fig. 1, the method for determining the re-deactivation of the semi-persistent scheduling may include the following steps:

in step S101, the type of the semi-persistent scheduling deactivated again is determined according to the indication of the network side device.

In an embodiment, when the network side device indicates the terminal to deactivate the SPS again, the network side device may indicate the type of the SPS that the terminal deactivates again, and accordingly, the terminal may accurately determine the type of the SPS that needs to be deactivated again, and further deactivate the SPS of the corresponding type again, and stop communicating with the network side device through the configuration of the SPS that is deactivated again, for example, stop receiving downlink information, and avoid affecting communication effects due to the fact that the SPS of the wrong type is deactivated again.

In one embodiment, the type includes at least one of: group common semi-persistent scheduling (SPS); UE-specific semi-persistent scheduling (UE-specific SPS).

The network side device may instruct the terminal to re-deactivate the group common SPS or re-deactivate the UE-specific SPS. When determining to deactivate the group common SPS again according to the indication, the terminal may deactivate the group common SPS again and stop communicating with the network side device according to the configuration of the group common SPS; when the terminal determines to deactivate the UE-specific SPS again according to the indication, the terminal can deactivate the UE-specific SPS again and stop communicating with the network side equipment according to the configuration of the UE-specific SPS;

in one embodiment, the indication of the network side device comprises at least one of:

explicit indication, implicit indication.

The method for indicating the terminal by the network side device may be explicit indication, for example, one or more pieces of information are sent to the terminal, and the content carried in the information directly indicates the type; the method for indicating the terminal by the network side device may be implicit indication, for example, information is sent to the terminal, the information has other functions and is not directly used for indicating the type, and the terminal may determine the type of the SPS that needs to be deactivated again according to the information in some manner, for example, the information is DCI in a User-Specific Search Space USS (User-Specific Search Space), the DCI is scrambled by an RNTI, the DCI is not used for indicating the type, but the terminal may determine the type according to the RNTI of the scrambled DCI.

As shown in fig. 2, for example, for a terminal supporting MBS, the network side device configures at least a configuration of a group common SPS for the terminal, where the periphery of the group common SPS is 5 slots, for example, a Physical Downlink Shared Channel (PDSCH) of the group common SPS in fig. 2 is in slot # n +1, and next in slot # n +6, and is separated by 5 slots.

The network side equipment initially deactivates the group common SPS in slot # n, for example, the group common PDCCH is sent to the terminal belonging to the same group in slot # n, and DCI in the group common PDCCH is scrambled by GS-RNTI. If the terminal correctly demodulates and determines the RNTI corresponding to the DCI, the terminal may stop communicating with the network side device according to the configuration of the group common PDCCH, and for example, stop receiving the PDSCH of the group common SPS in slot # n +1 and slot # n + 6.

The network side device may determine whether the terminal correctly demodulates and determines the RNTI corresponding to the DCI according to the information fed back by each terminal, for example, the terminal returns acknowledgement information ACK, the network side device determines that the terminal correctly demodulates and determines the RNTI, the terminal returns unacknowledged information NACK, and the network side device determines that the terminal incorrectly demodulates and determines the RNTI.

In addition, if the network side device also configures the UE-specific SPS for the terminal, the network side device may transmit DCI scrambled by the CS-RNTI in the USS for re-deactivation.

The following embodiments mainly illustrate several ways for the network side device to instruct the terminal to re-deactivate the group common SPS on the basis of the embodiment shown in fig. 2.

Fig. 3 is a schematic flow chart diagram illustrating another method for semi-statically scheduled re-deactivation determination, according to an embodiment of the present disclosure. As shown in fig. 3, the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device includes:

in step S301, receiving downlink control information DCI for deactivating SPS transmitted in a user equipment-specific search space USS;

in step S302, the type is determined according to the radio network temporary identifier RNTI scrambled with the DCI.

It should be noted that, for whether the DCI is a DCI for deactivating the SPS, the terminal may determine in an agreed manner, where the determination condition includes at least one of the following:

CRC of the DCI is scrambled by CS-RNTI or scrambled by GS-RNTI;

an NDI (New data indicator) field in DCI is 0;

a DCI format indicator (DCI format indicator) field of 0 if a DFI is present in the DCI;

the DCI includes a PDSCH-to-HARQ (Hybrid Automatic Repeat reQuest) feedback timing indication field for indicating an available uplink subframe.

After the terminal performs the above determination, it may further determine whether a validation domain in the DCI satisfies a deactivation condition, and if the deactivation condition is satisfied, determine how to receive the PDSCH of the SPS according to high-level configuration information corresponding to the SPS configuration that needs to be deactivated and dynamic scheduling information in the DCI.

In one embodiment, the network side device may transmit DCI for deactivating SPS in the USS, for example, the DCI is carried in a UE-specific PDCCH to indicate that a terminal which does not correctly demodulate and determine the RNTI deactivates the group common SPS again.

The terminal may pre-store a corresponding relationship between the RNTI and the SPS type, for example, a protocol convention or a pre-configuration by the network side device. After the terminal receives DCI for deactivating SPS in USS, the terminal can determine the RNTI for scrambling the DCI, for example, the DCI is descrambled through the RNTI, the RNTI for descrambling the DCI is corresponding to the RNTI for scrambling the DCI, so that the RNTI for scrambling the DCI can be determined according to the RNTI for descrambling the DCI successfully, and the type of SPS corresponding to the RNTI for scrambling the DCI is determined according to the RNTI for scrambling the DCI and the corresponding relation.

As shown in fig. 4, the terminal does not correctly demodulate and determine the RNTI corresponding to the DCI for deactivating the group common SPS in the slot # n, the network side device may send a UE-specific PDCCH (carrying the DCI scrambled by the RNTI) to the terminal, for example, send in slot # n +5 to instruct the terminal to deactivate the group common SPS again, and after the terminal deactivates the group common SPS again, the terminal may stop communicating with the network side device according to the configuration of the group common SPS, for example, may stop receiving the PDSCH of the group common SPS in slot # n + 6.

In one embodiment, the determining the type according to the RNTI that scrambles the DCI includes:

determining to re-deactivate group common SPS in response to the RNTI for scrambling the DCI being the first RNTI; and/or determining to re-deactivate the UE-specific SPS in response to the RNTI for scrambling the DCI being the second RNTI.

The terminal may pre-store a correspondence between the RNTI and the SPS type, for example, a protocol agreement or a correspondence pre-configured by the network side device, where in the correspondence, the first RNTI corresponds to a group common SPS, and the second RNTI corresponds to a UE-specific SPS.

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 multiplexed, and may be specifically selected according to needs.

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

The DCI for initial deactivation of group Common SPS is in CSS (Common Search Space), information transmitted in CSS may be received by multiple terminals; the DCI for initial deactivation of the UE-specific SPS is in the USS, and the information transmitted in the USS is typically only intended for reception by the terminal.

However, in some cases, there may be a partial overlap between the CSS and the USS, and if the DCI for deactivating the SPS transmitted in the USS is located at the overlapping portion, the DCI for deactivating the SPS transmitted in the USS may be received by multiple terminals, and if the RNTI scrambling the DCI for deactivating the SPS transmitted in the USS is the same as the CS-RNTI scrambling the DCI for initially deactivating the UE-specific SPS, or the GS-RNTI scrambling the DCI for initially deactivating the group common SPS, the DCI for deactivating the SPS transmitted in the USS may be received by other terminals, and then the corresponding SPS may be deactivated according to the RNTI determined by successful decoding, so that the other terminals erroneously deactivate the SPS.

Therefore, based on the embodiment, a new RNTI may be introduced as the first RNTI, which is different from the GS-RNTI for scrambling the DCI for group common SPS initial deactivation and the CS-RNTI for scrambling the DCI for UE-specific SPS initial deactivation, so as to avoid that other terminals erroneously deactivate SPS.

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

Although it is possible to avoid that other terminals erroneously deactivate the SPS by introducing a new RNTI as the first RNTI, the adjustment of the communication framework by introducing the new RNTI is relatively large, and the situation of erroneously deactivating the SPS generally only occurs in the case that there is a partial overlap between the CSS and the USS, which is not very common.

Therefore, in this embodiment, the GS-RNTI scrambling the DCI for initial deactivation of the group common SPS may also be multiplexed, and is used to scramble the DCI for deactivating the SPS transmitted in the USS, and after the terminal receives the DCI for deactivating the SPS transmitted in the USS, and determines that the RNTI scrambling the DCI is the GS-RNTI, it may be determined that the network side device needs to instruct to re-deactivate the group common SPS. Accordingly, modifications to the communication architecture are facilitated to be reduced.

Fig. 5 is a schematic flow chart diagram illustrating still another method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure. As shown in fig. 5, the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device includes:

in step S501, in response to support receiving DCI for deactivating a group common SPS in the USS, it is determined to re-deactivate the group common SPS upon receiving DCI scrambled by the CS-RNTI in the USS.

In one embodiment, the protocol may pre-agree on the terminal, and in a case that the terminal supports receiving DCI for deactivating group common SPS in the USS, when the terminal receives DCI scrambled by the CS-RNTI in the USS, the network side device instructs the terminal to re-deactivate group common SPS by default.

When the terminal itself supports receiving DCI for deactivating the group common SPS in the USS, if DCI scrambled by the CS-RNTI is received in the USS, the network side device may default to instruct the terminal to deactivate the group common SPS again, thereby deactivating the group common SPS again, and may not consider that the network side device instructs the terminal to deactivate the UE-specific SPS again.

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

When the terminal receives the DCI scrambled by the CS-RNTI in the USS, the network side equipment does not think that the terminal instructs the terminal to re-deactivate the UE-specific SPS, namely, the UE-specific SPS is not re-deactivated, which can cause that the UE-specific SPS cannot be successfully re-deactivated even if the terminal is configured with the configuration of the UE-specific SPS, so that the network side equipment can select the configuration of only configuring the group common SPS for the terminal instead of configuring the configuration of the UE-specific SPS for the terminal, thereby reducing resource waste.

Of course, the network side device may configure the configuration of the group common SPS for the terminal, and configure the configuration of the UE-specific SPS for the terminal, which may be specifically selected according to actual needs.

In an embodiment, the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device includes:

in response to supporting reception of DCI for deactivating group common SPS in a preset USS, determining to re-deactivate group common SPS when DCI scrambled by CS-RNTI is received in the preset USS.

In one embodiment, the protocol may pre-agree on the terminal, and when the terminal supports receiving DCI for deactivating group common SPS in the preset USS, and the terminal receives DCI scrambled by CS-RNTI in the preset USS, the network side device instructs the terminal to deactivate group common SPS again by default.

When the terminal supports receiving the DCI for deactivating the group common SPS in the preset USS, if the DCI scrambled by the CS-RNTI is received in the preset USS, the network side device may default to instruct the terminal to deactivate the group common SPS again, so as to deactivate the group common SPS again, and the network side device may not be considered to instruct the terminal to deactivate the UE-specific SPS again.

And when the DCI scrambled by the CS-RNTI is received in other USSs except the preset USS, the network side equipment can be considered to instruct the terminal to re-deactivate the UE-specific SPS, so that the UE-specific SPS is re-deactivated. Unlike the embodiment shown in fig. 5, the present embodiment only indicates re-deactivation of group common SPS by default for CS-RNTI scrambled DCI transmitted in the preset USS, and does not indicate re-deactivation of group common SPS by default for CS-RNTI scrambled DCI transmitted in other USS.

Fig. 6 is a schematic flow chart diagram illustrating still another method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure. As shown in fig. 6, the terminal is configured with a group common SPS and/or a UE-specific SPS on a first frequency domain resource, and the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device includes:

in step S601, the type is determined according to the RNTI scrambling the DCI transmitted by the network side device on the second frequency domain resource.

It should be noted that the DCI may be in the USS of the terminal, and in the case that the second frequency domain resource is configured to the terminal exclusively, the DCI may be in the USS of the terminal or may not be in the USS of the terminal.

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

Of course, the network side device may also transmit DCI scrambled by the RNTI on the first frequency domain resource to indicate the type of SPS that the terminal needs to be deactivated again, and may specifically be selected by the network side device as needed.

In one embodiment, the first frequency domain resource comprises a first component carrier, CC, and the second frequency domain resource comprises a second CC; and/or the first frequency-domain resource comprises a first bandwidth portion BWP and the second frequency-domain resource comprises a second BWP.

As shown in fig. 7, for example, the network side device configures a group common SPS and a UE-specific SPS for the terminal on the first CC, the terminal does not correctly demodulate and determine an RNTI corresponding to the DCI for deactivating the group common SPS in the slot # n, the network side device may send a UE-specific PDCCH (carrying the DCI scrambled by the RNTI) to the terminal on the second CC, for example, send in slot # n +5, to instruct the terminal to deactivate the group common SPS again on the first CC, and after the terminal deactivates the group common SPS again, the network side device may stop communicating with the network side device according to the configuration of the group common SPS, for example, may stop receiving the PDSCH of the group common SPS at slot # n + 6.

For example, the network-side device configures a group common SPS and a UE-specific SPS for the terminal on a first BWP, and the network-side device may send DCI scrambled by the RNTI to the terminal in the USS on a second BWP to instruct the terminal to re-deactivate the group common SPS or re-deactivate the UE-specific SPS.

It should be noted that, in this embodiment, the format of the DCI may be DCI format 1_1 or DCI format 1_2, and since the DCI of the two formats may carry information about frequency domains, it is convenient to indicate a frequency domain resource where an SPS that needs to be deactivated is located, for example, indicate a CC, a BWP, and the like where the SPS that needs to be deactivated is located.

Fig. 8 is a schematic flow chart diagram illustrating still another method for re-deactivation determination for semi-persistent scheduling according to an embodiment of the present disclosure. As shown in fig. 8, the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device includes:

in step S801, DCI for deactivating SPS transmitted in USS is received;

in step S802, the type is determined according to the identifier of the USS where the DCI is located.

In one embodiment, the terminal may store a correspondence between an identifier (e.g., ID) of the USS and a type of the SPS in advance, for example, agreed by a protocol or configured by the network side device in advance.

After receiving the DCI for deactivating the SPS in the USS, the terminal may determine an identifier of the USS where the DCI is located, and then identify a type of the SPS corresponding to the identifier according to a correspondence between the identifier and the type of the SPS.

As shown in fig. 9, for example, the network side device configures at least two USS identifiers, which are USS #1 and USS #2, for the terminal, and in the correspondence between the identifier of the USS and the type of the SPS, which are pre-stored in the terminal, USS #1 corresponds to a UE-specific SPS, and USS #2 corresponds to a group common SPS.

The terminal does not correctly demodulate and determine the RNTI corresponding to the DCI used for deactivating the group common SPS in the slot # n, and the network side device can send the UE-specific PDCCH to the terminal in the slot # n +5, wherein the carried DCI scrambled by the RNTI is in the USS corresponding to the USS # 2. The terminal receives DCI carried by the UE-specific PDCCH transmitted in slot # n +5, may determine that the DCI is in the USS corresponding to USS #2, and may further determine that USS #2 corresponds to a group common SPS, thereby deactivating the group common SPS, and may subsequently stop receiving downlink information in the PDSCH (for example, located in slot # n +6) corresponding to the group common SPS.

In addition, the terminal may also send the UE-specific PDCCH to the terminal in the USS corresponding to USS #1 as needed, for example, send the UE-specific PDCCH to the terminal in slot # n +4, and when the terminal receives DCI carried by the UE-specific PDCCH transmitted in slot # n +4, it may determine that the DCI is in the USS corresponding to USS #1, and may further determine that the UE-specific SPS corresponding to USS #1 is activated, and may then stop receiving downlink information in the PDSCH corresponding to the UE-specific SPS (for example, located in slot # n + 7).

In the above embodiment, the method for the network side device to indicate which SPS is deactivated by the terminal is mainly an implicit indication method, that is, the DCI is not directly used to indicate the type of SPS that the terminal needs to deactivate, but is indicated by the RNTI that scrambles the DCI. The following embodiments mainly aim at the way of explicit indication, and exemplify the technical solution of the present disclosure.

and determining the type according to the indication information sent by the network side equipment.

In one embodiment, the indication information includes at least one of: a medium access control layer control element, MAC CE; radio access control, RRC, signaling; and (6) DCI.

In an embodiment, the network side device may indicate, in an explicit indication manner, the type of SPS that the terminal needs to deactivate, for example, send one or more pieces of indication information to the terminal, where the content carried in the indication information directly indicates the type. The indication information may be transmitted in the form of MAC CE, RRC signaling, or DCI, and may be specifically selected as needed.

Fig. 10 is a schematic flow chart diagram illustrating a method for semi-statically scheduled re-deactivation, according to an embodiment of the present disclosure. The method for reactivating the semi-persistent scheduling shown in this embodiment may be executed by a network side device, where the network side device may communicate with a terminal, and the terminal includes but is not limited to a mobile phone, a tablet, a wearable device, a sensor, an internet of things device, and other communication devices. The network side device includes, but is not limited to, a network side device in a 4G, 5G, 6G, or other communication system, such as a base station, a core network, or the like.

As shown in fig. 10, the method for reactivating semi-persistent scheduling may include the following steps:

in step S1001, determining a type of semi-persistent scheduling SPS for which the terminal is expected to be deactivated again;

in step S1002, the terminal is instructed to determine the type.

In an embodiment, when the network side device indicates the terminal to deactivate the SPS again, the network side device may determine, as needed, the type of the semi-persistent scheduling SPS that the terminal is expected to deactivate again, and then indicate the type of the SPS that the terminal deactivates again, thereby enabling the terminal to accurately determine the type of the SPS that needs to be deactivated again, and then deactivate the SPS of the corresponding type again, and stop communicating with the network side device through the configuration of the SPS that is deactivated again, for example, stop receiving downlink information, and avoid affecting communication effects due to the fact that the SPS of an error type is deactivated again.

explicit indication, implicit indication.

Fig. 11 is a schematic flow chart diagram illustrating another method for semi-statically scheduled re-deactivation according to an embodiment of the present disclosure. As shown in fig. 11, the instructing the terminal to determine the type includes:

in step S1101, a radio network temporary identifier RNTI scrambled with downlink control information DCI for deactivating SPS in the user equipment dedicated search space USS is determined according to the type;

scrambling the DCI by the determined RNTI in step S1102;

in step S1103, the USS transmits the DCI to the terminal, so that the terminal determines the type according to the RNTI that scrambles the DCI.

CRC of the DCI is scrambled by CS-RNTI or scrambled by GS-RNTI;

an NDI (New data indicator) field in DCI is 0;

As shown in fig. 4, the terminal does not correctly demodulate and determine the RNTI corresponding to the DCI for deactivating the group common SPS in the slot # n, the network side device may send a UE-specific PDCCH (carrying the DCI scrambled by the RNTI) to the terminal, for example, send the PDCCH in slot # n +5 to instruct the terminal to deactivate the group common SPS again, after the terminal deactivates the group common SPS again, the terminal may stop communicating with the network side device according to the configuration of the group common SPS, and stop receiving the PDSCH of the group common SPS in slot # n + 6.

In one embodiment, the determining the RNTI that scrambles the DCI in the USS according to the type includes:

scrambling the DCI with a first RNTI in response to the terminal being expected to re-deactivate group common SPS; and/or scrambling the DCI with a second rtii in response to the terminal being expected to re-deactivate UE-specific SPS.

The network side device and the terminal may store a correspondence between the RNTI and the SPS type in advance, where in the correspondence, the first RNTI corresponds to a group common SPS, and the second RNTI corresponds to a UE-specific SPS. The network side equipment can scramble the DCI through the first RNTI when needing to indicate the terminal to deactivate the group common SPS again, and can scramble the DCI through the second RNTI when needing to indicate the terminal to deactivate the UE-specific SPS again.

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

Fig. 12 is a schematic flow chart diagram illustrating yet another method for re-deactivation of semi-persistent scheduling according to an embodiment of the present disclosure. As shown in fig. 12, the instructing the terminal to determine the type includes:

in step S1201, in response to determining that the terminal supports receiving DCI for deactivating a group common SPS in the USS and that the terminal is expected to re-deactivate the group common SPS, scrambling the DCI transmitted in the USS with the CS-RNTI;

in step S1202, the DCI is transmitted to the terminal in the USS, so that the terminal determines to re-deactivate group common SPS according to the CS-RNTI which scrambles the DCI.

When it is determined that the terminal itself supports receiving the DCI for deactivating the group common SPS in the USS, if the terminal needs to deactivate the group common SPS again, the terminal may default to the network side device instructing the terminal to deactivate the group common SPS again after receiving the DCI scrambled by the CS-RNTI in the USS when the terminal receives the DCI scrambled by the CS-RNTI in the USS, so as to deactivate the group common SPS again, and it is not considered that the network side device instructs the terminal to deactivate the UE-specific SPS again.

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

scrambling DCI transmitted in a preset USS through a CS-RNTI in response to determining that the terminal supports receiving DCI for deactivating group common SPS in the preset USS and expecting the terminal to re-deactivate group common SPS;

and transmitting the DCI to the terminal in the preset USS so that the terminal determines to re-deactivate group common SPS according to the CS-RNTI for scrambling the DCI.

And when the DCI scrambled by the CS-RNTI is received in other USSs except the preset USS, the network side equipment can be considered to instruct the terminal to re-deactivate the UE-specific SPS, so that the gUE-specific SPS is re-deactivated. Unlike the embodiment shown in fig. 12, the present embodiment only indicates re-deactivation of group common SPS by default for CS-RNTI scrambled DCI transmitted in the preset USS, and does not indicate re-deactivation of group common SPS by default for CS-RNTI scrambled DCI transmitted in other USS.

Fig. 13 is a schematic flow chart diagram illustrating yet another method for re-deactivation of semi-persistent scheduling according to an embodiment of the present disclosure. As shown in fig. 13, the terminal is configured with a group common SPS and/or a UE-specific SPS on a first frequency domain resource, and the indicating the terminal to determine the type includes:

in step S1301, an RNTI scrambled to the DCI transmitted on the second frequency domain resource is determined according to the type;

in step S1302, scrambling the DCI by the determined RNTI;

in step S1303, the DCI is transmitted to the terminal on a second frequency domain resource, so that the terminal determines the type according to the RNTI that scrambles the DCI.

Fig. 14 is a schematic flow chart diagram illustrating yet another method for re-deactivation of semi-persistent scheduling in accordance with an embodiment of the present disclosure. As shown in fig. 14, the instructing the terminal to determine the type includes:

in step S1401, the identification of the USS is determined according to the type;

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

In one embodiment, the network side device and the terminal may store a correspondence between an identifier (e.g., ID) of the USS and a type of the SPS in advance. The network side device may first determine the type of the SPS that needs to be deactivated again by the terminal, then query the identifier of the USS corresponding to the determined type according to the correspondence between the identifier of the USS and the type of the SPS, and further transmit the DCI for deactivating the SPS to the terminal in the USS corresponding to the queried identifier of the USS. After receiving the DCI for deactivating the SPS in the USS, the terminal may determine an identifier of the USS where the DCI is located, and then identify a type of the SPS corresponding to the identifier according to a correspondence between the identifier and the type of the SPS.

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

and sending indication information to the terminal to indicate the type.

Corresponding to the foregoing embodiments of the method for determining deactivation of semi-persistent scheduling and the method for deactivating deactivation of semi-persistent scheduling, the present disclosure also provides embodiments of a device for determining deactivation of semi-persistent scheduling and a device for deactivating deactivation of semi-persistent scheduling.

The embodiment of the present disclosure illustrates a re-deactivation determining apparatus for semi-persistent scheduling, which may be applied to a terminal, where the terminal includes but is not limited to a mobile phone, a tablet, a wearable device, a sensor, an internet of things device, and other communication apparatuses. The terminal may communicate with a network side device, where the network side device includes, but is not limited to, a network side device in a 4G, 5G, 6G, and other communication systems, such as a base station, a core network, and the like.

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

and determining the type of the deactivated semi-persistent scheduling according to the indication of the network side equipment.

In one embodiment, the type includes at least one of:

group common semi-persistent scheduling (SPS);

UE-specific semi-persistent scheduling (UE-specific SPS).

explicit indication, implicit indication.

In one embodiment, the processor is configured to:

receiving downlink control information DCI which is transmitted in a dedicated search space USS of user equipment and used for deactivating SPS;

and determining the type according to the radio network temporary identifier RNTI scrambled with the DCI.

In one embodiment, the processor is configured to:

In one embodiment, the first RNTI is different from a GS-RNTI used for scrambling DCI for group common SPS initial deactivation and/or different from a CS-RNTI used for scrambling DCI for UE-specific SPS initial deactivation.

In one embodiment, the processor is configured to: in response to supporting reception of DCI for deactivating group common SPS in USS, determining to re-deactivate group common SPS when DCI scrambled by CS-RNTI is received in USS.

In one embodiment, the processor is configured to:

In one embodiment, the terminal is configured with a group common SPS and/or a UE-specific SPS on a first frequency domain resource, and the processor is configured to: and determining the type according to the RNTI of the DCI scrambled and transmitted by the network side equipment on the second frequency domain resource.

In one embodiment, the processor is configured to: receiving a DCI transmitted in the USS for deactivating the SPS; and determining the type according to the identification of the USS where the DCI is located.

In one embodiment, the processor is configured to: and determining the type according to the indication information sent by the network side equipment.

The embodiment of the present disclosure shows a semi-persistent scheduling re-deactivation apparatus, which may be applied to a network side device, where the network side device may communicate with a terminal, and the terminal includes, but is not limited to, a mobile phone, a tablet computer, a wearable device, a sensor, an internet of things device, and other communication apparatuses. The network side device includes, but is not limited to, a network side device in a 4G, 5G, 6G, or other communication system, such as a base station, a core network, or the like.

determining the type of semi-persistent scheduling (SPS) expected to be deactivated again by the terminal;

indicating the terminal to enable the terminal to determine the type.

In one embodiment, the type includes at least one of:

group common semi-persistent scheduling (SPS);

UE-specific semi-persistent scheduling (UE-specific SPS).

explicit indication, implicit indication.

In one embodiment, the processor is configured to:

determining a radio network temporary identifier RNTI scrambled by downlink control information DCI for deactivating SPS in a user equipment dedicated search space USS according to the type;

scrambling the DCI through the determined RNTI;

and transmitting the DCI to the terminal in the USS so that the terminal determines the type according to the RNTI for scrambling the DCI.

In one embodiment, the processor is configured to:

scrambling DCI transmitted in the USS with a CS-RNTI in response to determining that the terminal supports receiving DCI for deactivating group common SPS in the USS and that the terminal is expected to re-deactivate group common SPS;

and transmitting the DCI to the terminal at the USS so that the terminal determines to re-deactivate group common SPS according to the CS-RNTI for scrambling the DCI.

In one embodiment, the processor is configured to:

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

determining RNTI scrambled for DCI transmitted on the second frequency domain resource according to the type;

scrambling the DCI through the determined RNTI;

and transmitting the DCI to the terminal on a second frequency domain resource so that the terminal determines the type according to the RNTI for scrambling the DCI.

In one embodiment, the processor is configured to:

determining the USS identifier according to the type;

and transmitting DCI scrambled by CS-RNTI to the terminal at 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.

In one embodiment, the processor is configured to:

and sending indication information to the terminal to indicate the type.

With regard to 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 related method, and will not be described in detail here.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

An embodiment of the present disclosure further provides a communication apparatus, for example, the terminal, including: a processor; a memory for storing a computer program; wherein the computer program, when executed by a processor, implements the method for determining re-deactivation of semi-persistent scheduling according to any of the above embodiments.

An embodiment of the present disclosure further provides a communication apparatus, for example, the network side device, including: a processor; a memory for storing a computer program; wherein the computer program, when executed by a processor, implements the method for reactivating semi-persistent scheduling of any of the above embodiments.

Embodiments of the present disclosure further provide a computer-readable storage medium for storing a computer program, which, when being executed by a processor, implements the steps of the method for determining re-deactivation of semi-persistent scheduling described in any of the above embodiments.

Embodiments of the present disclosure further provide a computer-readable storage medium for storing a computer program, which, when being executed by a processor, implements the steps in the method for reactivating semi-persistent scheduling according to any of the above embodiments.

As shown in fig. 15, fig. 15 is a schematic block diagram illustrating an apparatus 1500 for re-deactivation of semi-persistent scheduling in accordance with an embodiment of the present disclosure. Apparatus 1500 may be provided as a base station. Referring to fig. 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 may further include one or more processors. One of the processors in the processing component 1522 may be configured to implement the method for semi-persistent scheduling re-deactivation described in any of the embodiments above.

Fig. 16 is a schematic block diagram illustrating an apparatus 1600 for re-deactivation determination for semi-persistent scheduling in accordance with an embodiment of the present disclosure. For example, the apparatus 1600 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, or the like.

Referring to fig. 16, apparatus 1600 may include one or more of the following components: processing component 1602, memory 1604, power component 1606, multimedia component 1608, audio component 1610, input/output (I/O) interface 1612, sensor component 1614, and communications component 1616.

The processing component 1602 generally controls overall operation of the device 1600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1602 may include one or more processors 1620 to execute instructions to perform all or some of the steps of the semi-statically scheduled re-deactivation determination method described above. Further, the processing component 1602 can include one or more modules that facilitate interaction between the processing component 1602 and other components. For example, the processing component 1602 can include a multimedia module to facilitate interaction between the multimedia component 1608 and the processing component 1602.

The memory 1604 is configured to store various types of data to support operation at the apparatus 1600. Examples of such data include instructions for any application or method operating on device 1600, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1604 may be implemented by any type of volatile or non-volatile storage device or 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 or optical disks.

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

The multimedia component 1608 includes a screen that provides an output interface between the device 1600 and a 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 an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a 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 comprises a front-facing camera and/or a rear-facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 1600 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

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

I/O interface 1612 provides an interface between the processing component 1602 and peripheral interface modules, which can be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

Sensor assembly 1614 includes one or more sensors for providing status assessment of various aspects to device 1600. For example, sensor assembly 1614 can detect an open/closed state of device 1600, the relative positioning of components, such as a display and keypad of device 1600, and sensor assembly 1614 can also detect a change in position of device 1600 or a component of device 1600, the presence or absence of user contact with device 1600, orientation or acceleration/deceleration of device 1600, and a change in temperature of device 1600. The sensor assembly 1614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communications component 1616 is configured to facilitate communications between the apparatus 1600 and other devices in a wired or wireless manner. The apparatus 1600 may 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 broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 1616 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

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, micro-controllers, microprocessors or other electronic components for performing the semi-statically scheduled re-deactivation determination methods described above.

In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 1604 comprising instructions, executable by the processor 1620 of the apparatus 1600 to perform the semi-persistent scheduled re-deactivation determination method described above is also provided. 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, and the like.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The method and apparatus provided by the embodiments of the present disclosure are described in detail above, and the principles and embodiments of the present disclosure are explained herein by applying specific examples, and the above description of the embodiments is only used to help understanding the method and core ideas of the present disclosure; meanwhile, for a person skilled in the art, based on the idea of the present disclosure, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present disclosure should not be construed as a limitation to the present disclosure.

Claims

1. A method for determining re-deactivation of semi-persistent scheduling, the method being performed by a terminal and comprising:

2. The method of claim 1, wherein the type comprises at least one of:

group common semi-persistent scheduling (SPS);

UE-specific semi-persistent scheduling (UE-specific SPS).

3. The method of claim 1, wherein the indication of the network-side device comprises at least one of:

explicit indication, implicit indication.

4. The method of claim 2, wherein the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device comprises:

5. The method of claim 4, wherein the determining the type according to the RNTI for scrambling the DCI comprises:

determining to re-deactivate group common SPS in response to the RNTI for scrambling the DCI being the first RNTI;

and/or

And determining to re-deactivate the UE-specific SPS in response to the RNTI for scrambling the DCI being the second RNTI.

6. The method of claim 5, wherein the first RNTI is different from a GS-RNTI used for scrambling DCI for group common SPS initial deactivation and/or different from a CS-RNTI used for scrambling DCI for UE-specific SPS initial deactivation.

7. The method of claim 5, wherein the first RNTI is the same as a GS-RNTI used to scramble DCI for group common SPS initial deactivation.

8. The method of claim 2, wherein the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device comprises:

in response to supporting reception of DCI for deactivating group common SPS in USS, determining to re-deactivate group common SPS when DCI scrambled by CS-RNTI is received in USS.

9. The method of claim 8, wherein the terminal is configured with a group common SPS and is not configured with a UE-specific SPS.

10. The method of claim 2, wherein the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device comprises:

11. The method as claimed in claim 2, wherein the terminal is configured with a group common SPS and/or a UE-specific SPS on the first frequency domain resource, and the determining the type of the re-deactivated semi-persistent scheduling according to the indication of the network side device comprises:

and determining the type according to the RNTI of the DCI scrambled and transmitted by the network side equipment on the second frequency domain resource.

12. The method of claim 11, wherein the first frequency-domain resource comprises a first Component Carrier (CC), and wherein the second frequency-domain resource comprises a second CC; and/or

The first frequency-domain resource comprises a first bandwidth portion BWP and the second frequency-domain resource comprises a second BWP.

13. The method of claim 2, wherein the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device comprises:

receiving a DCI transmitted in the USS for deactivating the SPS;

and determining the type according to the identification of the USS where the DCI is located.

14. The method of claim 2, wherein the determining the type of the semi-persistent scheduling for re-deactivation according to the indication of the network side device comprises:

15. The method of claim 14, wherein the indication information comprises at least one of:

a medium access control layer control element, MAC CE;

radio access control, RRC, signaling;

DCI。

16. a method for reactivating semi-persistent scheduling, the method being performed by a network side device, the method comprising:

indicating the terminal to enable the terminal to determine the type.

17. The method of claim 16, wherein the type comprises at least one of:

group common semi-persistent scheduling (SPS);

UE-specific semi-persistent scheduling (UE-specific SPS).

18. The method of claim 16, wherein the indication of the network-side device comprises at least one of:

explicit indication, implicit indication.

19. The method of claim 17, wherein the instructing the terminal to determine the type comprises:

scrambling the DCI through the determined RNTI;

20. The method of claim 19, wherein the determining the RNTI that scrambles the DCI in the USS according to the type comprises:

scrambling the DCI with a first RNTI in response to the terminal being expected to re-deactivate group common SPS;

and/or

Scrambling the DCI with a second RNTII in response to the terminal being expected to re-deactivate UE-specific SPS.

21. The method of claim 20, wherein the first RNTI is different from a GS-RNTI used to scramble a DCI for group common SPS initial deactivation and/or is different from a CS-RNTI used to scramble a DCI for UE-specific SPS initial deactivation.

22. The method of claim 21, wherein the first RNTI is the same as a GS-RNTI used to scramble a DCI for group common SPS initial deactivation.

23. The method of claim 17, wherein the instructing the terminal to determine the type comprises:

24. The method of claim 23, wherein the terminal is configured with a group common SPS and is not configured with a UE-specific SPS.

25. The method of claim 17, wherein the instructing the terminal to determine the type comprises:

26. The method of claim 17, wherein the terminal is configured with a group common SPS and/or a UE-specific SPS on a first frequency domain resource, and wherein the indicating the terminal to cause the terminal to determine the type comprises:

scrambling the DCI through the determined RNTI;

27. The method of claim 26, wherein the first frequency-domain resource comprises a first Component Carrier (CC), wherein the second frequency-domain resource comprises a second CC; and/or

28. The method of claim 17, wherein the instructing the terminal to determine the type comprises:

determining the USS identifier according to the type;

29. The method of claim 17, wherein the instructing the terminal to determine the type comprises:

and sending indication information to the terminal to indicate the type.

30. The method of claim 29, wherein the indication information comprises at least one of:

a medium access control layer control element, MAC CE;

radio access control, RRC, signaling;

DCI。

31. an apparatus for semi-statically scheduled re-deactivation determination, comprising one or more processors configured to:

32. A semi-statically scheduled re-deactivation apparatus, comprising one or more processors configured to:

indicating the terminal to enable the terminal to determine the type.

33. A communications apparatus, comprising:

a processor;

a memory for storing a computer program;

wherein the computer program when executed by a processor implements the method of re-deactivation determination of semi-persistent scheduling of any of claims 1 to 15.

34. A communications apparatus, comprising:

a processor;

a memory for storing a computer program;

wherein the computer program when executed by a processor implements the method of semi-statically scheduled re-deactivation of any of claims 16 to 30.

35. A computer readable storage medium storing a computer program, the computer program, when executed by a processor, implementing the steps in the method for semi-persistent scheduling re-deactivation determination of any one of claims 1 to 15.

36. A computer readable storage medium storing a computer program, the computer program, when executed by a processor, implementing the steps in the method of semi-persistent scheduling re-deactivation of any of claims 16 to 30.