Communication method, communication device, and communication system
Patent Information
- Application Number
- PCT/CN2025/086024
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-28
- Publication Date
- 2026-10-01
Smart Images
Figure CN2025086024_01102026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment and communication systems Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device and communication system. Background Technology
[0002] Semi-persistent Scheduling (SPS) is a resource allocation mechanism designed to optimize data transmission efficiency for periodic services such as voice calls. SPS improves overall system performance by reducing the frequency of control channel usage, making it particularly suitable for regular and predictable data traffic. Summary of the Invention
[0003] This disclosure proposes a communication method, communication device, and communication system that can solve the technical problem of how to save detection power consumption of terminal devices.
[0004] A first aspect of this disclosure provides a communication method performed by a network device, the method comprising: sending a demodulation reference signal (DMRS) sequence of a Physical Downlink Shared Channel (PDSCH) to a terminal device, the SPS PDSCH belonging to a first SPS schedule; wherein the scrambling code identifier (ID) of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0005] A second aspect of this disclosure provides a communication method executed by a terminal device, the method comprising: receiving a DMRS sequence of an SPS PDSCH sent by a network device, the SPS PDSCH belonging to a first SPS schedule; wherein the scrambling code ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0006] A third aspect of this disclosure provides a network device, including a processing module and a transceiver module, wherein the transceiver module is configured to send a DMRS sequence of an SPS PDSCH to a terminal device, the SPS PDSCH belonging to a first SPS schedule; wherein the scrambling code ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0007] A fourth aspect of this disclosure provides a terminal device, including: a transceiver module and a processing module, wherein the transceiver module is configured to receive a DMRS sequence of an SPS PDSCH sent by a network device, the SPS PDSCH belonging to a first SPS schedule; wherein the scrambling code ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0008] A fifth aspect of this disclosure provides a communication device for performing the method described in the first aspect embodiment or the method described in the second aspect embodiment.
[0009] A sixth aspect of this disclosure provides a communication system including a network device and a terminal device, wherein the network device is configured to implement the method described in the first aspect embodiment, and the terminal device is configured to implement the method described in the second aspect embodiment.
[0010] A seventh aspect embodiment of this disclosure provides a storage medium that, when the instructions are executed on a communication device, causes the communication device to perform the method as described in the first aspect embodiment or the method as described in the second aspect embodiment.
[0011] An eighth aspect of this disclosure provides a program product including at least one program and instructions, which, when executed by a communication device, implement the method described in the first aspect embodiment or the method described in the second aspect embodiment.
[0012] The technical solution provided in this disclosure allows a network device to send a DMRS sequence of an SPS PDSCH to a terminal device. This SPS PDSCH belongs to the first SPS scheduler, and the scrambling code ID of the DMRS sequence can then indicate whether the first SPS scheduler has been released. This eliminates the need for the terminal device to obtain the SPS scheduler release indication information through blind detection based on Downlink Control Information (DCI), thus saving the detection power consumption of the terminal device.
[0013] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description
[0014] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.
[0015] Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure.
[0016] Figure 1B is a schematic diagram of an example provided by an embodiment of this disclosure.
[0017] Figure 1C is a schematic diagram of another example provided by an embodiment of this disclosure.
[0018] Figure 2A is an interactive schematic diagram of a communication method provided in an embodiment of this disclosure.
[0019] Figure 2B is a schematic diagram of another example provided by an embodiment of this disclosure.
[0020] Figure 2C is a schematic diagram of yet another example provided in the embodiments of this disclosure.
[0021] Figure 2D is an interactive schematic diagram of another communication method provided in an embodiment of this disclosure.
[0022] Figure 3 is a schematic diagram of an example of a communication method provided in an embodiment of this disclosure.
[0023] Figure 4A is a structural block diagram of a network device provided in an embodiment of this disclosure.
[0024] Figure 4B is a structural block diagram of a terminal device provided in an embodiment of this disclosure.
[0025] Figure 5A is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure.
[0026] Figure 5B is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation
[0027] The embodiments of this disclosure are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure. It should be noted that, unless otherwise specified, the embodiments of this disclosure and the features in the embodiments can be combined with each other.
[0028] This disclosure presents a communication method, communication device, and communication system.
[0029] In a first aspect, embodiments of this disclosure propose a communication method executed by a network device, the method comprising: sending a DMRS sequence of an SPS PDSCH to a terminal device, the SPS PDSCH belonging to a first SPS schedule; wherein, the scrambling code identifier ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0030] The technical solution provided in this disclosure eliminates the need for terminal devices to obtain SPS scheduling release indication information based on DCI blind detection, thus saving detection power consumption of terminal devices.
[0031] In conjunction with some embodiments of the first aspect, the scrambling ID of the DMRS sequence is also used to identify the terminal device. This allows for targeted indication for each terminal device, enabling each device to clearly identify its own information.
[0032] In conjunction with some embodiments of the first aspect, the scrambling ID of the DMRS sequence is used to indicate whether the SPS schedule is released, including:
[0033] The scrambling ID of the DMRS sequence belongs to the first set, and the first SPS scheduler is released;
[0034] The scrambling ID of the DMRS sequence belongs to the second set, and the first SPS scheduler does not release it.
[0035] This method clearly determines whether the SPS scheduler is released. When the scrambling code ID of the DMRS sequence belongs to the first set, it can be determined that the SPS scheduler is released. When the scrambling code ID of the DMRS sequence belongs to the second set, it can be determined that the SPS scheduler is not released.
[0036] In conjunction with some embodiments of the first aspect, the method further includes:
[0037] Send a first scrambling code ID and a second scrambling code ID to the terminal device, wherein the first scrambling code ID belongs to the first set and the second scrambling code ID belongs to the second set.
[0038] This method allows terminal devices to clearly determine whether an SPS scheduler is released. For example, if the scrambling code ID of the DMRS sequence of the SPS PDSCH sent by the network device matches the first scrambling code ID, it is determined that the first SPS scheduler to which the SPS PDSCH belongs is released; if the scrambling code ID of the DMRS sequence of the SPS PDSCH sent by the network device matches the second scrambling code ID, it is determined that the first SPS scheduler to which the SPS PDSCH belongs is not released.
[0039] In conjunction with some embodiments of the first aspect, sending the first scrambling code ID and the second scrambling code ID to the terminal device includes:
[0040] A first Radio Resource Control (RRC) message is sent to the terminal device. The first RRC message includes a first scrambling code ID and a second scrambling code ID. This first RRC message is used to configure parameters for the first SPS scheduling. The first RRC message can be an RRC message used to configure necessary parameters such as the SPS PDSCH transmission period, the number of HARQ processes, and the MCS table. After the network device sends this SPS configuration information via the first RRC message, it can instruct the activation of SPS PDSCH transmission, and the terminal device can then begin periodically receiving PDSCH. In this way, the first and second scrambling code IDs, along with this SPS configuration information, can be sent to the terminal device together without sending additional RRC messages, reducing transmission overhead.
[0041] In conjunction with some embodiments of the first aspect, the scrambling code ID is associated with a Configured Scheduling (CS) - Radio Network Temporary Identifier (RNTI) group, which is used to identify the terminal device.
[0042] This method allows for targeted instructions to be given to each terminal device, enabling each terminal device to clearly understand its own information.
[0043] In conjunction with some embodiments of the first aspect, the CS-RNTI group includes at least one of the following:
[0044] A third set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the third set, and the first SPS schedule is released;
[0045] A fourth set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the fourth set, and the first SPS scheduler is not released.
[0046] This method can clearly determine whether SPS scheduling is released. When the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the third set, it can be determined that SPS scheduling is released. When the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the fourth set, it can be determined that SPS scheduling is not released.
[0047] In conjunction with some embodiments of the first aspect, the method further includes:
[0048] Send a first CS-RNTI and a second CS-RNTI to the terminal device, wherein the first CS-RNTI belongs to the third set and the second CS-RNTI belongs to the fourth set.
[0049] This method allows terminal devices to clearly determine whether an SPS scheduler is released. For example, if the CS-RNTI corresponding to the scrambling code ID of the DMRS sequence of the SPS PDSCH sent by the network device matches the first CS-RNTI, it is determined that the first SPS scheduler to which the SPS PDSCH belongs is released; if the CS-RNTI corresponding to the scrambling code ID of the DMRS sequence of the SPS PDSCH sent by the network device matches the second CS-RNTI, it is determined that the first SPS scheduler to which the SPS PDSCH belongs is not released.
[0050] In conjunction with some embodiments of the first aspect, sending a first CS-RNTI and a second CS-RNTI to the terminal device includes:
[0051] A second RRC message is sent to the terminal device. This second RRC message includes the first CS-RNTI and the second CS-RNTI, and is used to configure the parameters of the first SPS scheduling. This second RRC message can be an RRC message used to configure necessary parameters such as the SPS PDSCH transmission period, the number of HARQ processes, and the MCS table. After the network device sends this SPS configuration information via the second RRC message, it can instruct the activation of SPS PDSCH transmission, and the terminal device can then begin periodically receiving PDSCH. In this way, the first and second CS-RNTIs, along with this SPS configuration information, can be sent to the terminal device together without sending additional RRC messages, reducing transmission overhead.
[0052] In conjunction with some embodiments of the first aspect, the scrambling code ID includes at least one of the following:
[0053] Scrambling code ID0; Scrambling code ID1.
[0054] This method allows for the explicit identification of the type of scrambling ID used to indicate whether SPS scheduling should release it.
[0055] In conjunction with some embodiments of the first aspect, the scrambling ID of the DMRS sequence is used to indicate the release of the first SPS schedule, and the SPS PDSCH is the last PDSCH of the first SPS schedule.
[0056] This method avoids a significant gap between the SPS scheduling release instruction and the actual last transmitted SPS PDSCH, thus reducing transmission latency.
[0057] In conjunction with some embodiments of the first aspect, the DMRS sequence is generated by a generator polynomial, which includes the scrambling code ID. The scrambling code ID of the DMRS sequence of the SPS PDSCH indicates whether the first SPS scheduler has been released, eliminating the need for the terminal device to obtain the SPS scheduler release indication information based on blind detection using DCI, thus saving detection power consumption for the terminal device.
[0058] Secondly, embodiments of this disclosure propose a communication method executed by a terminal device, the method comprising: receiving a DMRS sequence of an SPS PDSCH sent by a network device, the SPS PDSCH belonging to a first SPS schedule; wherein, the scrambling code identifier ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0059] The technical solution provided in this disclosure eliminates the need for terminal devices to obtain SPS scheduling release indication information based on DCI blind detection, thus saving detection power consumption of terminal devices.
[0060] In conjunction with some embodiments of the second aspect, the scrambling ID of the DMRS sequence is also used to identify the terminal device.
[0061] In conjunction with some embodiments of the second aspect, the scrambling ID of the DMRS sequence is used to indicate whether the SPS schedule is released, including:
[0062] The scrambling ID of the DMRS sequence belongs to the first set, and the first SPS scheduler is released;
[0063] The scrambling ID of the DMRS sequence belongs to the second set, and the first SPS scheduler does not release it.
[0064] In conjunction with some embodiments of the second aspect, the method further includes:
[0065] The network device receives a first scrambling code ID and a second scrambling code ID, wherein the first scrambling code ID belongs to the first set and the second scrambling code ID belongs to the second set.
[0066] In conjunction with some embodiments of the second aspect, receiving the first scrambling code ID and the second scrambling code ID sent by the network device includes: receiving a first Radio Resource Control (RRC) message sent by the network device, the first RRC message including the first scrambling code ID and the second scrambling code ID, the first RRC message being used to configure parameters of the first SPS scheduling.
[0067] In conjunction with some embodiments of the second aspect, the scrambling code ID is associated with a Configuration Scheduling (CS)-Radio Network Temporary Identifier (RNTI) group, which is used to identify the terminal device.
[0068] In conjunction with some embodiments of the second aspect, the CS-RNTI group includes at least one of the following:
[0069] A third set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the third set, and the first SPS schedule is released;
[0070] A fourth set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the fourth set, and the first SPS scheduler is not released.
[0071] In conjunction with some embodiments of the second aspect, the method further includes:
[0072] The network device receives a first CS-RNTI and a second CS-RNTI, where the first CS-RNTI belongs to the third set and the second CS-RNTI belongs to the fourth set.
[0073] In conjunction with some embodiments of the second aspect, the receiving network device sending the first CS-RNTI and the second CS-RNTI includes:
[0074] The system receives a second RRC message sent by a network device. The second RRC message includes the first CS-RNTI and the second CS-RNTI. The second RRC message is used to configure the parameters of the first SPS scheduling.
[0075] In conjunction with some embodiments of the second aspect, the scrambling code ID includes at least one of the following:
[0076] Scrambling code ID0;
[0077] Scrambling code ID1.
[0078] In conjunction with some embodiments of the second aspect, the scrambling ID of the DMRS sequence is used to indicate the release of the first SPS schedule, and the SPS PDSCH is the last PDSCH of the first SPS schedule.
[0079] In conjunction with some embodiments of the second aspect, the DMRS sequence is generated by a generator polynomial, which includes the scrambling code ID.
[0080] Thirdly, embodiments of this disclosure provide a network device comprising: a processing module and a transceiver module, wherein the transceiver module is configured to send a DMRS sequence of an SPS PDSCH to a terminal device, the SPS PDSCH belonging to a first SPS schedule; wherein the scrambling code ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0081] Fourthly, this disclosure provides a terminal device comprising: a transceiver module and a processing module, wherein the transceiver module is configured to receive a DMRS sequence of an SPS PDSCH sent by a network device, the SPS PDSCH belonging to a first SPS schedule; wherein the scrambling code ID of the DMRS sequence is used to indicate whether the first SPS schedule is released.
[0082] Fifthly, embodiments of this disclosure provide a communication device for performing the method as described in the first aspect embodiment or the method as described in the second aspect embodiment.
[0083] In a sixth aspect, embodiments of this disclosure provide a communication system, including: a network device and a terminal device; the network device is configured to perform the method described in the first aspect embodiment, and the terminal device is configured to perform the method described in the second aspect embodiment.
[0084] In a seventh aspect, embodiments of this disclosure provide a storage medium that, when the instructions are executed on a communication device, causes the communication device to perform the method as described in the first aspect embodiment or the second aspect embodiment.
[0085] Eighthly, embodiments of this disclosure provide a program product comprising at least one of a program and instructions, wherein the program and at least one of the instructions, when executed by a communication device, implement the method as described in the first aspect embodiment or the second aspect embodiment.
[0086] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect embodiment or the second aspect embodiment.
[0087] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described above as in the first aspect embodiment or the second aspect embodiment.
[0088] It is understood that the aforementioned network devices, terminal devices, communication devices, communication systems, storage media, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0089] This disclosure provides a communication method, communication device, and communication system. In some embodiments, the terms "communication method" can be substituted for "information processing method," "information sending method," and "information receiving method," and the terms "communication device" can be substituted for "information processing device," "information sending device," and "information receiving device," and the terms "information processing system," "communication system," "information sending system," and "information receiving system" can be substituted for each other.
[0090] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0091] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0092] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0093] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0094] In the embodiments disclosed herein, "multiple" refers to two or more.
[0095] In some embodiments, the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0096] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.
[0097] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.
[0098] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0099] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0100] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.
[0101] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0102] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.
[0103] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0104] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0105] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", "client", and "narrowband Internet of Things (NB-IoT) device" can be used interchangeably.
[0106] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminal devices. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminal devices with communication between multiple terminal devices (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal devices can also be configured to have all or part of the functions of the access network devices. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminal devices (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink link, etc., can be replaced with sidelink link.
[0107] In some embodiments, the terminal device may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal device.
[0108] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0109] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0110] In some embodiments, the threshold mentioned in this embodiment may be a numerical value, a constant, or some fixed value.
[0111] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0112] The correspondences shown in the tables of this disclosure can be configured or predefined. The values of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values or representations of the parameters can also be other values or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.
[0113] The predefined terms in this disclosure can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned, etc.
[0114] The term "release" in this disclosure can be understood as deactivation, deactivation, disabling, or cessation.
[0115] The communication methods, communication equipment, and communication systems provided in this disclosure will now be described in detail with reference to the accompanying drawings.
[0116] Figure 1A shows a structural diagram of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the system architecture may include a network device 101 and a terminal device 102.
[0117] In some embodiments, network device 101 may include at least one of access network device and core network device.
[0118] In some embodiments, the access network device is, for example, a node or device that connects a terminal device to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.
[0119] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0120] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0121] In some embodiments, the terminal device 102 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.
[0122] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0123] The following embodiments of this disclosure can be applied to the communication system or some of the subjects shown in FIG1A, but are not limited thereto. The subjects shown in FIG1A are illustrative. The communication system may include all or some of the subjects in FIG1A, or may include other subjects other than those in FIG1A. The number and form of each subject are arbitrary. The connection relationship between the subjects is illustrative. The subjects may not be connected to each other or may be connected in any way. The connection may be direct or indirect, wired or wireless.
[0124] The embodiments disclosed herein can be applied to satellite communications, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G NR, Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0125] In some embodiments, the commonly used scheduling method in New Radio (NR) is dynamic scheduling, which involves scheduling a Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) using a Downlink Control Information (DCI). Taking DCI-driven dynamic scheduling of PDSCH as an example, as shown in Figure 1B, the base station (gNB) first sends a DCI (DCI#1), and then sends PDSCH#1 at a specific location based on the scheduling information carried in the DCI. DCI#1 carries indication information such as time-frequency resources for PDSCH#1. Correspondingly, the terminal device blindly detects DCI#1 on the Physical Downlink Control Channel (PDCCH) channel, and then receives the corresponding PDSCH based on the time-frequency resource indication information of this DCI. Then, it blindly detects the next DCI and receives the corresponding PDSCH based on the time-frequency resource indication information of that DCI. Similarly, before sending the PDSCH, the base station will first send a DCI to dynamically indicate the PDSCH's time and frequency resources and other transmission parameters. Correspondingly, the terminal device will first use a blind detection DCI to dynamically obtain the PDSCH's transmission parameters, and then receive the PDSCH based on the PDSCH transmission parameters carried in the DCI.
[0126] In some embodiments, unlike dynamic scheduling, semi-persistent scheduling (SPS) for PDSCH can reduce the number of blind DCI detections by the terminal device, further reducing latency and power consumption. For example, a DCI or RRC reconfiguration message can indicate several (persistent) PDSCHs or PUSCHs. Once the terminal device receives a specific DCI or RRC reconfiguration message, it begins periodically receiving PDSCHs or sending PUSCHs until this persistent scheduling stops. During this persistent scheduling period, the terminal device does not need to perform DCI detections again; this is semi-persistent scheduling. Compared to dynamic scheduling, semi-persistent scheduling (SPS) reduces the number of blind DCI detections required by the terminal device, lowering transmission latency and power consumption.
[0127] In some embodiments, the SPS PDSCH scheduling process can be divided into two parts: first, pre-configuring necessary parameters such as the SPS PDSCH transmission period through Radio Resource Control (RRC); and second, activating or releasing SPS PDSCH transmission through DCI. Before configuring SPS parameters in RRC signaling, the base station also assigns a Configured Scheduling (CS) – Radio Network Temporary Identifier (RNTI) – to each terminal device to identify different terminal devices. Combining the two parts of the SPS PDSCH scheduling process, as shown in Figure 1C, the base station sending SPS PDSCH or the terminal device receiving SPS PDSCH involves two steps:
[0128] Step 1: The base station sends the necessary parameters for the SPS PDSCH via RRC configuration or reconfiguration signaling, including the period, the number of Hybrid Automatic Repeat Request (HARQ) processes, and the Modulation and Coding Scheme (MCS) table. Correspondingly, the terminal equipment receives the necessary parameter configuration for the SPS PDSCH.
[0129] Step 2: The base station sends CS-RNTI scrambled DCIs (including DCI#1 or DCI#2) to activate or release SPS transmission. DCI#1 is used to activate SPS PDSCH transmission; that is, after DCI#1 is sent, PDSCH#1 can be sent at the first candidate resource location of the SPS PDSCH. DCI#1 also contains frequency domain resource configuration information, including Frequency Domain Resource Allocation (FDRA) indication information and MCS indication information. DCI#2 is used to release SPS PDSCH transmission; that is, before DCI#2 is sent, the base station sends PDSCH#1 and PDSCH#2 sequentially according to the period configured in the RRC. After DCI#2 is sent, the time-frequency resource location where PDSCH#3 is located is no longer used to send PDSCH#3. Correspondingly, the terminal device receives the period and other configuration information in the RRC, listens to the corresponding CS-RNTI scrambled DCI, and then determines the start and end positions for receiving SPS PDSCH based on the DCI.
[0130] Based on the SPS PDSCH transmission mechanism described above, the PDCCH allocated to SPS for scheduling activation or release must simultaneously satisfy the following:
[0131] 1) The Cyclic Redundancy Check (CRC) associated with the DCI format is scrambled by CS-RNTI or G-CS-RNTI. In the embodiments of this disclosure, CS-RNTI is used uniformly without distinguishing between CS-RNTI and G-CS-RNTI.
[0132] 2) The NDI field in the DCI format is set to "0".
[0133] 3) If a DFI field exists in the DCI format, this field is set to "0".
[0134] 4) The TDRA field in the DCI format is indicated by a single SLIV.
[0135] 5) When scheduling is active and a PDSCH-to-HARQ_feedback timing indication exists, the PDSCH-to-HARQ_feedback timing indication field does not provide an inapplicable value.
[0136] When DCI indicates SPS scheduling activation, in addition to indicating activation, it is also necessary to indicate FDRA and MCS parameters; when DCI indicates SPS scheduling release, only a release message is needed.
[0137] In some embodiments, the terminal device obtains the SPS schedule release indication information based on DCI blind detection. From the perspective of the terminal device, the DCI-based SPS schedule release indication method requires high power consumption. In some examples, power consumption simulation tests show that the relative power consumption required for PDCCH blind detection is higher than that for sequence detection. From the system's perspective, the actual end position of SPS PDSCH transmission depends on the location of the DCI carrying the schedule release indication information. Since there is a significant gap between the DCI carrying the schedule release indication information and the actual last transmitted SPS PDSCH, the transmission latency will be high. From the base station's perspective, the DCI only carries 1 bit of transmission release verification information. The resource overhead of sending the DCI is relatively high compared to the number of information bits transmitted, meaning that transmitting 1 bit of information via DCI results in low resource efficiency.
[0138] To this end, this disclosure proposes a communication scheme that reuses the demodulation reference signal (DMRS) of the SPS PDSCH to indicate the SPS transmission release information. The user identification information and SPS scheduling release information are carried by the scrambling code of the DMRS, so as to save the detection power consumption of the terminal, and at the same time reduce the DCI resource overhead on the network side and the processing latency of the terminal's SPS downlink reception. For details, please refer to the description of the following method embodiments.
[0139] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the method includes the following steps:
[0140] In step S2101, the network device sends the first scrambling code ID and the second scrambling code ID to the terminal device.
[0141] In some embodiments, the terminal device receives a first scrambling code ID and a second scrambling code ID sent by the network device.
[0142] In some embodiments, the first scrambling code ID may be at least one, and the second scrambling code ID may be at least one, and the first scrambling code ID and the second scrambling code ID may be used by the terminal device to generate multiple DMRS sequences.
[0143] In some embodiments, the first scrambling code ID and the second scrambling code ID may be scrambling code ID0 and / or scrambling code ID1.
[0144] In some embodiments, the DMRS sequence is generated by a generator polynomial, which includes a scrambling code ID.
[0145] For example, DMRS sequences are generated using a Cinit generator polynomial, which includes scrambling codes ID0 and ID1. The terminal device can generate multiple DMRS sequences based on at least one first scrambling code ID and at least one second scrambling code ID.
[0146] In some embodiments, the first scrambling code ID and the second scrambling code ID can be used to identify a terminal device. For example, a first set is formed by at least one first scrambling code ID, a second set is formed by at least one second scrambling code ID, and the first set and the second set are further combined to form a scrambling code ID group. This scrambling code ID group contains the first set and the second set, and can be used to identify a terminal device, i.e., the scrambling code ID group belonging to that terminal device. The first set and the second set can be predefined by the protocol. In this way, the network device can assign a corresponding scrambling code ID group to each terminal device. Each scrambling code ID group includes at least two values, i.e., at least one first scrambling code ID and at least one second scrambling code ID. For example, the network device can assign a scrambling code ID group containing a1 and b1 to terminal device 1, and simultaneously assign a scrambling code ID group containing a2 and b2 to terminal device 2. Terminal device 1 generates two DMRS sequences based on a1 and b1, and terminal device 2 generates two DMRS sequences based on a2 and b2. When terminal device 1 uses the DMRS sequence generated by a1 or b1 to detect the DMRS sequence of the SPS PDSCH (e.g., the DMRS sequence generated by a1 or b1 detects the same scrambling code ID as the DMRS of the SPS PDSCH), it can determine that the scrambling code of the current SPS PDSCH DMRS carries its own identification information. The scrambling code ID of the current SPS PDSCH DMRS sequence is used to indicate itself.
[0147] For example, the first set can be (1…32760) or a subset thereof, and the second set can be (32761…65522) or a subset thereof. The ranges of values for the first set and the second set can be interchanged.
[0148] For example, the first set can be the set of odd numbers in (1…65522) or a subset thereof, and the second set can be the set of even numbers in (1…65522) or a subset thereof. Similarly, the ranges of values for the first and second sets can be interchanged.
[0149] For example, the first set can be the set of values in (1…65522) that are modulo 2 0 or a subset thereof, and the second set can be the set of values in (1…65522) that are modulo 2 1 or a subset thereof. Similarly, the ranges of values in the first and second sets can be interchanged.
[0150] In some examples, the method of dividing the first set and the second set can be used for both scrambling code ID0 and scrambling code ID1, that is, scrambling code ID0 and scrambling code ID1 are divided according to the above rules at the same time, without distinguishing whether DMRS sequence initialization is enabled.
[0151] In some examples, the method for dividing the first and second sets can also be associated with the enabled state of DMRS sequence initialization. For instance, when DMRS sequence initialization is disabled, the method for dividing the first and second sets is only used for scrambling code ID0.
[0152] In some embodiments, the first scrambling code ID and the second scrambling code ID can be used as a reference for the terminal device when determining whether the SPS schedule has been released. That is, the network device sends the standard for determining whether the SPS schedule has been released to the terminal device in advance.
[0153] In some examples, a first set is formed by at least one first scrambling code ID, meaning that the first scrambling code ID belongs to the first set. For example, if the scrambling code ID of the DMRS sequence of a subsequent SPS PDSCH sent by the network device belongs to the first set, the SPS schedule release to which the SPS PDSCH belongs can be determined.
[0154] In some examples, a second set is formed by at least one second scrambling code ID, meaning that the second scrambling code ID belongs to the second set. For example, if the scrambling code ID of the DMRS sequence of an SPS PDSCH sent by a network device belongs to the second set, it is determined that the SPS schedule to which the SPS PDSCH belongs will not be released.
[0155] In some embodiments, the network device sends a first RRC message to the terminal device. The first RRC message includes a first scrambling code ID and a second scrambling code ID. This first RRC message is used to configure parameters for the first SPS scheduling. For example, the network device can send the first scrambling code ID and the second scrambling code ID via an RRC message, which can be an RRC configuration message or an RRC reconfiguration message, etc.
[0156] In some embodiments, the first RRC message may be an RRC message used to configure necessary parameters such as the SPS PDSCH transmission period, the number of HARQ processes, and the MCS table. After the network device sends this SPS configuration information via the first RRC message, it can instruct the activation of SPS PDSCH transmission, and subsequently, the terminal device can begin periodically receiving PDSCH. In this way, the first scrambling code ID and the second scrambling code ID, along with this SPS configuration information, can be sent to the terminal device without sending additional RRC messages, thus reducing transmission overhead.
[0157] In step S2102, the network device sends the DMRS sequence of the SPS PDSCH to the terminal device.
[0158] In some embodiments, the terminal device may receive the DMRS sequence of the SPS PDSCH sent by the network device.
[0159] In some embodiments, the SPS PDSCH belongs to the first SPS schedule. For example, in the first SPS schedule, the terminal device periodically receives the PDSCH and receives the current SPS PDSCH and the DMRS sequence of the current SPS PDSCH.
[0160] In some embodiments, the scrambling code ID of the DMRS sequence of the current SPS PDSCH can be scrambling code ID0 and / or scrambling code ID1.
[0161] In some embodiments, the scrambling ID of the DMRS sequence can be used to identify the terminal device. That is, the terminal device can determine whether the scrambling ID of the current SPS PDSCH's DMRS sequence carries its own identification information by using the scrambling ID of the current DMRS sequence. For example, the terminal device pre-generates multiple DMRS sequences based on at least one first scrambling ID and at least one second scrambling ID. If the generated multiple DMRS sequences detect the presence of the current SPS PDSCH's DMRS sequence scrambling ID among the first and second scrambling IDs, it indicates that the current SPS PDSCH's DMRS scrambling ID carries its own identification information. If the generated multiple DMRS sequences detect the absence of the current SPS PDSCH's DMRS sequence scrambling ID among the first and second scrambling IDs, it indicates that the current SPS PDSCH's DMRS scrambling ID does not carry its own identification information.
[0162] For example, since the same SPS PDSCH can be received by multiple terminal devices, a single terminal device can also determine whether the scrambling code corresponds to the current terminal device by detecting the scrambling value of the DMRS sequence of the SPS PDSCH.
[0163] In some embodiments, the scrambling code ID of the DMRS sequence can be used to indicate whether the SPS schedule has been released. That is, the terminal device can determine whether the scrambling code of the DMRS carries SPS schedule release information by using the scrambling code ID of the DMRS sequence.
[0164] In some examples, the terminal device pre-generates multiple DMRS sequences based on at least one first scrambling code ID and at least one second scrambling code ID. If, based on the generated multiple DMRS sequences, it is detected that the scrambling code ID of the current SPS PDSCH's DMRS sequence belongs to a first set, then it can be determined that the scrambling code ID of the current SPS PDSCH's DMRS sequence carries SPS scheduling release information, and correspondingly, it is determined that the first SPS schedule to which the current SPS PDSCH belongs is released. If, based on the generated multiple DMRS sequences, it is detected that the scrambling code ID of the current SPS PDSCH's DMRS sequence belongs to a second set, then it can be determined that the scrambling code ID of the current SPS PDSCH's DMRS sequence does not carry SPS scheduling release information, and correspondingly, it is determined that the first SPS schedule to which the current SPS PDSCH belongs is not released.
[0165] For example, the terminal device determines whether to deactivate the SPS (i.e., SPS scheduling release) by detecting the DMRS scrambling value. When the terminal device detects that the scrambling code ID of the DMRS sequence belongs to the second set, it only performs channel estimation based on the DMRS; when the terminal device detects that the scrambling code ID of the DMRS sequence belongs to the second set, in addition to performing channel estimation based on the DMRS, it can also obtain the SPS scheduling release indication information.
[0166] In some embodiments, if the scrambling ID of the DMRS sequence of the current SPS PDSCH is used to indicate the release of the first SPS schedule, then the current SPS PDSCH is the last PDSCH of the first SPS schedule.
[0167] For example, as shown in Figure 2B, the scrambled CS-RNTI and verification field corresponding to the CRC of the DCI can indicate the SPS PDSCH schedule release for a specific terminal device or terminal device group. From the perspective of the terminal device, this method of SPS schedule release indication based on DCI requires high power consumption. From the perspective of the system, the actual end position of SPS PDSCH transmission depends on the position of the DCI carrying the schedule release indication information. Since there is a significant gap between the DCI carrying the schedule release indication information and the actual last transmitted SPS PDSCH, the transmission latency will be high. From the perspective of the base station, the DCI only carries 1 bit of transmission release verification information. The resource overhead of sending the DCI is relatively high compared to the number of information bits transmitted, that is, transmitting 1 bit of information through DCI results in low resource efficiency. As shown in Figure 2C, this embodiment of the present disclosure proposes a new method for identifying users and indicating SPS transmission release information based on PDSCH DMRS. The terminal device does not need to blindly detect the DCI to obtain SPS schedule release information, and the power consumption of the terminal device can be saved by sequence detection. If the scrambling ID of the DMRS sequence of the current SPS PDSCH is used to indicate the release of the first SPS schedule, then the current SPS PDSCH is the last PDSCH of the first SPS schedule. Therefore, there is no gap between it and the actual last transmitted SPS PDSCH, and the base station does not need to send DCI to carry SPS schedule release information. Directly reusing the DMRS sequence in the PDSCH can save network overhead.
[0168] The communication method involved in this embodiment may include at least one of steps S2101 to S2102. For example, step S2101 may be implemented as a standalone embodiment, and step S2102 may be implemented as a standalone embodiment. Alternatively, some or all of the steps in steps S2101 to S2102 may be combined and implemented as a standalone embodiment, and this embodiment does not limit this.
[0169] This disclosure proposes a communication scheme that reuses the DMRS signal of the SPS PDSCH to indicate SPS transmission release information, and carries user identification information and SPS scheduling release information through the scrambling code of the DMRS, so as to save the detection power consumption of the terminal, and at the same time reduce the DCI resource overhead on the network side and the processing latency of the terminal's SPS downlink reception.
[0170] Figure 2D is an interactive schematic diagram of another communication method according to an embodiment of the present disclosure. As shown in Figure 2D, the method includes the following steps:
[0171] Step S2201: The network device sends the first CS-RNTI and the second CS-RNTI to the terminal device.
[0172] In some embodiments, the terminal device receives a first CS-RNTI and a second CS-RNTI sent by the network device.
[0173] In some embodiments, there may be at least one first CS-RNTI and at least one second CS-RNTI.
[0174] In some embodiments, the first CS-RNTI and the second CS-RNTI can be used to identify a terminal device. For example, a third set is formed by at least one first CS-RNTI, and a fourth set is formed by at least one second CS-RNTI. The third set and the fourth set are then combined to form a CS-RNTI group, which includes the third set and the fourth set. This CS-RNTI group can be used to identify a terminal device, that is, the CS-RNTI group belonging to that terminal device. The third set and the fourth set can be predefined by the protocol. In this way, the network device can assign a corresponding CS-RNTI group to each terminal device. Each CS-RNTI group includes at least two values, that is, at least one first CS-RNTI and at least one second CS-RNTI.
[0175] In some embodiments, the DMRS sequence is generated using a generator polynomial that includes scrambling code IDs. For example, the DMRS sequence is generated using a Cinit generator polynomial that includes scrambling code ID0 and scrambling code ID1. Network devices can send a pre-assigned CS-RNTI group (i.e., at least one first CS-RNTI and at least one second CS-RNTI) to terminal devices via scrambling code ID0 and / or scrambling code ID1. The terminal device generates an initial DMRS value (Cinit) using each value in the pre-assigned CS-RNTI group, and then further generates multiple DMRS sequences. When the terminal device detects a DMRS sequence with the same scrambling code ID as the current SPS PDSCH DMRS sequence using the DMRS sequence generated based on scrambling code ID0 or scrambling code ID1, the terminal device can determine that the current DMRS sequence carries its own identification information.
[0176] In some embodiments, the first CS-RNTI and the second CS-RNTI can be used as a reference for the terminal device when determining whether the SPS schedule has been released. That is, the network device sends the standard for how to determine whether the SPS schedule has been released to the terminal device in advance.
[0177] In some examples, a third set is obtained by consisting of at least one first CS-RNTI. For example, if the CS-RNTI corresponding to the scrambling ID of the DMRS sequence of a subsequent SPS PDSCH sent by the network device belongs to the third set, the SPS schedule release to which the SPS PDSCH belongs can be determined.
[0178] In some examples, a fourth set is formed by at least one second CS-RNTI. For instance, if the CS-RNTI corresponding to the scrambling ID of the DMRS sequence of an SPS PDSCH sent by a network device belongs to the fourth set, it is determined that the SPS schedule to which the SPS PDSCH belongs will not be released.
[0179] In some embodiments, the network device sends a second RRC message to the terminal device. This second RRC message includes a first CS-RNTI and a second CS-RNTI, and is used to configure parameters for the first SPS scheduling. For example, the network device can send the first CS-RNTI and the second CS-RNTI via an RRC message, which can be an RRC configuration message or an RRC reconfiguration message, etc.
[0180] In some embodiments, the second RRC message can be an RRC message used to configure necessary parameters such as the SPS PDSCH transmission period, HARQ process count, and MCS table. After the network device sends this SPS configuration information via the second RRC message, it can instruct the activation of SPS PDSCH transmission, and subsequently, the terminal device can begin periodically receiving PDSCH. In this way, the first and second CS-RNTIs, along with this SPS configuration information, can be sent to the terminal device together without sending additional RRC messages, reducing transmission overhead.
[0181] In step S2202, the network device sends the DMRS sequence of the SPS PDSCH to the terminal device.
[0182] In some embodiments, the terminal device may receive the DMRS sequence of the SPS PDSCH sent by the network device.
[0183] In some embodiments, the SPS PDSCH belongs to the first SPS schedule. For example, in the first SPS schedule, the terminal device periodically receives the PDSCH and receives the current SPS PDSCH and the DMRS sequence of the current SPS PDSCH.
[0184] In some embodiments, the scrambling code ID of the DMRS sequence of the current SPS PDSCH can be scrambling code ID0 and / or scrambling code ID1.
[0185] In some embodiments, the scrambling ID of the DMRS sequence of the current SPS PDSCH is associated with a CS-RNTI group, which can be used to identify the terminal device. That is, the terminal device can determine whether the scrambling ID of the DMRS sequence carries its own identification information by using the CS-RNTI corresponding to the scrambling ID of the current SPS PDSCH DMRS sequence. For example, the terminal device pre-generates multiple DMRS sequences based on the scrambling IDs corresponding to at least one first CS-RNTI and at least one second CS-RNTI. If the generated multiple DMRS sequences detect a CS-RNTI corresponding to the scrambling ID of the current SPS PDSCH DMRS sequence in the first and second CS-RNTIs, it indicates that the scrambling ID of the current SPS PDSCH DMRS carries its own identification information. If the generated multiple DMRS sequences detect a CS-RNTI corresponding to the scrambling ID of the current SPS PDSCH DMRS sequence in the first and second CS-RNTIs, it indicates that the scrambling ID of the current SPS PDSCH DMRS does not carry its own identification information.
[0186] For example, since the same SPS PDSCH can be received by multiple terminal devices, a single terminal device can also determine whether the scrambling code corresponds to the current terminal device by detecting the scrambling value of the DMRS sequence of the SPS PDSCH.
[0187] In some embodiments, the scrambling code ID of the DMRS sequence can be used to indicate whether the SPS schedule has been released. That is, the terminal device can determine whether the scrambling code of the DMRS carries SPS schedule release information by using the CS-RNTI corresponding to the scrambling code ID of the DMRS sequence.
[0188] In some examples, the terminal device pre-generates multiple DMRS sequences based on the scrambling code IDs corresponding to at least one first CS-RNTI and at least one second CS-RNTI. If, based on the generated multiple DMRS sequences, it is detected that the CS-RNTI corresponding to the scrambling code ID of the current SPS PDSCH's DMRS sequence belongs to the third set, then it can be determined that the scrambling code ID of the current SPS PDSCH's DMRS sequence carries SPS scheduling release information. Accordingly, it is determined that the first SPS schedule to which the current SPS PDSCH belongs is released. For example, in addition to channel estimation based on DMRS, SPS scheduling release indication information can also be obtained. If, based on the generated multiple DMRS sequences, it is detected that the CS-RNTI corresponding to the scrambling code ID of the current SPS PDSCH's DMRS sequence belongs to the fourth set, then it can be determined that the scrambling code ID of the current SPS PDSCH's DMRS sequence does not carry SPS scheduling release information. Accordingly, it is determined that the first SPS schedule to which the current SPS PDSCH belongs is not released, and only channel estimation is performed based on DMRS.
[0189] In some embodiments, if the scrambling ID of the DMRS sequence of the current SPS PDSCH is used to indicate the release of the first SPS schedule, then the current SPS PDSCH is the last PDSCH of the first SPS schedule.
[0190] For example, as shown in Figure 2B, the scrambled CS-RNTI and verification field corresponding to the CRC of the DCI can indicate the SPS PDSCH schedule release for a specific terminal device or terminal device group. From the perspective of the terminal device, this method of SPS schedule release indication based on DCI requires high power consumption. From the perspective of the system, the actual end position of SPS PDSCH transmission depends on the position of the DCI carrying the schedule release indication information. Since there is a significant gap between the DCI carrying the schedule release indication information and the actual last transmitted SPS PDSCH, the transmission latency will be high. From the perspective of the base station, the DCI only carries 1 bit of transmission release verification information. The resource overhead of sending the DCI is relatively high compared to the number of information bits transmitted, that is, transmitting 1 bit of information through DCI results in low resource efficiency. As shown in Figure 2C, this embodiment of the present disclosure proposes a new method for identifying users and indicating SPS transmission release information based on PDSCH DMRS. The terminal device does not need to blindly detect the DCI to obtain SPS schedule release information, and the power consumption of the terminal device can be saved by sequence detection. If the scrambling ID of the DMRS sequence of the current SPS PDSCH is used to indicate the release of the first SPS schedule, then the current SPS PDSCH is the last PDSCH of the first SPS schedule. Therefore, there is no gap between it and the actual last transmitted SPS PDSCH, and the base station does not need to send DCI to carry SPS schedule release information. Directly reusing the DMRS sequence in the PDSCH can save network overhead.
[0191] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2202. For example, step S2201 may be implemented as a standalone embodiment, and step S2202 may be implemented as a standalone embodiment. In addition, some or all of the steps in steps S2201 to S2202 may be selected and combined as a standalone embodiment, which is not limited in this embodiment.
[0192] This disclosure proposes a communication scheme that reuses the DMRS signal of the SPS PDSCH to indicate SPS transmission release information, and carries user identification information and SPS scheduling release information through the scrambling code of the DMRS, so as to save the detection power consumption of the terminal, and at the same time reduce the DCI resource overhead on the network side and the processing latency of the terminal's SPS downlink reception.
[0193] Figure 3 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the method includes:
[0194] Step S301: The network device sends the DMRS sequence of the SPS PDSCH to at least one terminal device.
[0195] In some embodiments, the SPS PDSCH belongs to the first SPS schedule.
[0196] In some embodiments, the scrambling ID of the DMRS sequence of the SPS PDSCH is used to indicate whether the first SPS schedule is released.
[0197] Optionally, the alternative implementations of step S301 can be found in Figures 2A to 2D, and will not be repeated here.
[0198] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0199] This disclosure proposes a communication scheme that reuses the DMRS signal of the SPS PDSCH to indicate SPS transmission release information, and carries user identification information and SPS scheduling release information through the scrambling code of the DMRS, so as to save the detection power consumption of the terminal, and at the same time reduce the DCI resource overhead on the network side and the processing latency of the terminal's SPS downlink reception.
[0200] The following are some exemplary specific solutions proposed in the embodiments of this disclosure:
[0201] This embodiment of the disclosure reuses the DMRS signal of the SPS PDSCH to indicate the SPS transmission release information, and carries user identification information and SPS scheduling release information through the scrambling code of the DMRS, so as to save the detection power consumption of the terminal device, and at the same time reduce the DCI resource overhead on the network side and the processing latency of the SPS downlink reception of the terminal device.
[0202] Method Overview:
[0203] This disclosure proposes a novel method for identifying users and indicating SPS transmission release information based on PDSCH DMRS. Compared to related technologies that use the scrambled CS-RNTI corresponding to the DCI CRC and the verification field to indicate the SPS PDSCH scheduling release for a specific terminal device or terminal device group, the key points of this disclosure include:
[0204] 1) How to carry terminal device identification information through DMRS scrambling codes.
[0205] 2) How to carry 1 bit of SPS PDSCH scheduling release information through DMRS.
[0206] The first key point – how to carry terminal device identification information through DMRS scrambling codes – will be discussed in detail below.
[0207] In related technologies, the base station assigns a CS-RNTI to each terminal device via an RRC message, and then scrambles the corresponding CS-RNTI in the DCI to carry the user's identification information. Each RNTI type has a corresponding value range. CS-RNTI and G-CS-RNTI both belong to the hexadecimal range 0001 to FFF2. For example, the base station can assign a CS-RNTI of 0001 to terminal device #1, and a CS-RNTI of 0002 to terminal device #2. When terminal device #1 detects the DCI with 0001, it can determine that the current DCI is addressed to itself, and that the scrambled RNTI type is CS-RNTI.
[0208] In this embodiment of the disclosure, within the value range of CS-RNTI, the base station assigns a CS-RNTI group to each terminal device, and each CS-RNTI group includes at least two values. The CS-RNTI group is used to identify the terminal device. For example, the base station can assign CS-RNTIs 0001 and 0002 to terminal device #1, and assign CS-RNTIs 0003 and 0004 to terminal device #2. When terminal device #1 detects a DCI using 0001 or 0002, it can determine that the current DCI is sent to itself, and the scrambling RNTI type is CS-RNTI.
[0209] In relevant NR technologies, DMRS sequences are generated using an initialization value Cinit generator polynomial. In the Cinit generator polynomial, Configure scrambling ID0 and scrambling ID1 using high-level parameters.
[0210] In this embodiment of the disclosure, for example, the base station can send a CS-RNTI group pre-assigned to the terminal device using scrambling code ID0 or scrambling code ID1. The terminal device generates an initial value Cinit for the DMRS using each value in the pre-assigned CS-RNTI group, and then further generates multiple DMRS sequences. When the terminal device detects that the scrambling code IDs of the PDSCH DMRS are the same using the DMRS sequences generated according to scrambling code ID0 or scrambling code ID1, the terminal device can determine that the current DMRS sequence carries its own identification information.
[0211] Regarding the second key point – how to carry 1 bit of SPS PDSCH scheduling release information through DMRS – we will now begin to explain.
[0212] The first key point describes how the base station allocates CS-RNTI groups to each terminal device, with each CS-RNTI group containing at least two values. To carry SPS PDSCH scheduling release information, in each CS-RNTI group, at least one CS-RNTI is used to map the SPS scheduling release information, while at least one CS-RNTI is not mapped to it. The at least one CS-RNTI not mapped to SPS scheduling release information belongs to a first set, and the at least one CS-RNTI mapped to SPS scheduling release information belongs to a second set.
[0213] For example, the first set can be (1…32760) or a subset thereof, and the second set can be (32761…65522) or a subset thereof. The ranges of values for the first set and the second set can be interchanged.
[0214] For example, the first set can be the set of odd numbers in (1…65522) or a subset thereof, and the second set can be the set of even numbers in (1…65522) or a subset thereof. Similarly, the ranges of values for the first and second sets can be interchanged.
[0215] For example, the first set can be the set of values in (1…65522) that are modulo 2 0 or a subset thereof, and the second set can be the set of values in (1…65522) that are modulo 2 1 or a subset thereof. Similarly, the ranges of values in the first and second sets can be interchanged.
[0216] The aforementioned DMRS carrying SPS scheduling release indication information can be replaced with: the DMRS is also used to indicate that the current SPS PDSCH is the last PDSCH of this SPS scheduling.
[0217] The above set partitioning method can be used for both scrambling code ID0 and scrambling code ID1, that is, scrambling code ID0 and scrambling code ID1 can be partitioned according to the above rules at the same time, without distinguishing whether DMRS sequence initialization is enabled.
[0218] The above set partitioning method can also be associated with the enable state of DMRS sequence initialization. When DMRS sequence initialization is disabled, the above set partitioning method is only used for scrambling code ID0.
[0219] The corresponding terminal device behaviors are as follows, based on the above method:
[0220] On the one hand, since the same SPS PDSCH can be received by multiple terminal devices, a single terminal device can also determine whether the scrambling code corresponds to the current terminal device by detecting the DMRS scrambling value.
[0221] On the other hand, the terminal device determines whether to deactivate SPS by detecting the DMRS scrambling value. When the terminal device detects that the DMRS scrambling value belongs to the first set, it only performs channel estimation based on the DMRS; when the terminal device detects that the DMRS scrambling value belongs to the second set, in addition to performing channel estimation based on the DMRS, it can also obtain the SPS scheduling release indication information.
[0222] In some embodiments, the base station transmits a PDSCH DMRS sequence generated by scrambling code ID0 and / or scrambling code ID1. Scrambling code ID0 and / or scrambling code ID1 are associated with CS-RNTI groups pre-allocated by the base station for the terminal device. In each CS-RNTI group, at least one CS-RNTI is used to map SPS scheduling release information, and at least one CS-RNTI is not used to map SPS scheduling release information.
[0223] Accordingly, in some embodiments, the terminal device receives or detects a PDSCH DMRS sequence generated by scrambling code ID0 and / or scrambling code ID1. Here, scrambling code ID0 and / or scrambling code ID1 are associated with CS-RNTI groups pre-allocated by the base station to the terminal device. In each CS-RNTI group, at least one CS-RNTI is used to map SPS scheduling release information, and at least one CS-RNTI is not used to map SPS scheduling release information.
[0224] For the technical solution proposed in this disclosure, the terminal device does not need to blindly detect the DCI to obtain the SPS scheduling release information; sequence detection can save power consumption of the terminal device. The network does not need to send the DCI carrying the SPS scheduling release information; directly reusing the DMRS sequence in the PDSCH can save network overhead.
[0225] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal device in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by the network device (e.g., access network device, core network functional node, core network device, etc.) in any of the above methods.
[0226] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0227] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0228] Figure 4A is a schematic diagram of the network device proposed in an embodiment of this disclosure. The network device is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, the network device may include at least one of: a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is configured to send a demodulation reference signal (DMRS) sequence of a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) to a terminal device, wherein the SPS PDSCH belongs to a first SPS schedule; wherein the scrambling code identifier (ID) of the DMRS sequence is used to indicate whether the first SPS schedule is released. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform at least one of the other steps performed by the network device in any of the above methods, which will not be described in detail here.
[0229] Figure 4B is a schematic diagram of the structure of a terminal device proposed in an embodiment of this disclosure. The terminal device is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the terminal device may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module is configured to receive a demodulation reference signal (DMRS) sequence of a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) sent by a network device, wherein the SPS PDSCH belongs to a first SPS schedule; wherein the scrambling code identifier (ID) of the DMRS sequence is used to indicate whether the first SPS schedule has been released. Optionally, the transceiver module is used to perform the transmission and / or reception communication steps performed by the terminal device in any of the above methods, which will not be described in detail here. Optionally, the processing module is used to perform other steps performed by the terminal device in any of the above methods, which will not be described in detail here.
[0230] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0231] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0232] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.
[0233] Figure 5A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be the network device or terminal device described above. Specifically, it can be a network device (e.g., access network device), a terminal device (e.g., user equipment), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal device in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0234] As shown in Figure 5A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0235] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform the communication steps such as sending and / or receiving in the above method, and the processor 6101 performs other processing steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0236] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.
[0237] The communication device 6100 described in the above embodiments may be a network device or a terminal device, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0238] Figure 5B is a schematic diagram of the structure of the chip 6200 proposed in an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, the schematic diagram of the chip 6200 shown in Figure 5B can be referenced, but the invention is not limited thereto.
[0239] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0240] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.
[0241] In some embodiments, the interface circuit 6202 performs communication steps such as sending and / or receiving in the above-described method. For example, the interface circuit 6202 performing communication steps such as sending and / or receiving in the above-described method refers to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs other processing steps.
[0242] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0243] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0244] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0245] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
1. A communication method characterized by comprising: Performed by a network device, the method includes: Send a demodulation reference signal (DMRS) sequence of the semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) to the terminal device, wherein the SPS PDSCH belongs to the first SPS scheduling. The scrambling code ID of the DMRS sequence is used to indicate whether the first SPS scheduler is released.
2. The method of claim 1, wherein, The scrambling ID of the DMRS sequence is also used to identify the terminal device.
3. The method according to claim 1 or 2, characterized in that, The scrambling ID of the DMRS sequence is used to indicate whether the SPS schedule has been released, including: The scrambling ID of the DMRS sequence belongs to the first set, and the first SPS scheduler is released; The scrambling ID of the DMRS sequence belongs to the second set, and the first SPS scheduler does not release it.
4. The method according to claim 3, characterized in that, The method further includes: Send a first scrambling code ID and a second scrambling code ID to the terminal device, wherein the first scrambling code ID belongs to the first set and the second scrambling code ID belongs to the second set.
5. The method according to claim 3, characterized in that, Sending the first scrambling code ID and the second scrambling code ID to the terminal device includes: A first Radio Resource Control (RRC) message is sent to the terminal device. The first RRC message includes the first scrambling code ID and the second scrambling code ID. The first RRC message is used to configure the parameters of the first SPS scheduling.
6. The method according to claim 1, characterized in that, The scrambling code ID is associated with the Configuration Scheduling CS-RNTI group, which is used to identify the terminal device.
7. The method according to claim 6, characterized in that, The CS-RNTI group includes at least one of the following: A third set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the third set, and the first SPS schedule is released; A fourth set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the fourth set, and the first SPS scheduler is not released.
8. The method according to claim 7, characterized in that, The method further includes: Send a first CS-RNTI and a second CS-RNTI to the terminal device, wherein the first CS-RNTI belongs to the third set and the second CS-RNTI belongs to the fourth set.
9. The method according to claim 8, characterized in that, Sending the first CS-RNTI and the second CS-RNTI to the terminal device includes: A second RRC message is sent to the terminal device. The second RRC message includes the first CS-RNTI and the second CS-RNTI. The second RRC message is used to configure the parameters of the first SPS scheduling.
10. The method according to any one of claims 1 to 9, characterized in that, The scrambling ID includes at least one of the following: Scrambling code ID0; Scrambling code ID1.
11. The method according to any one of claims 1 to 10, characterized in that, The scrambling ID of the DMRS sequence is used to indicate the release of the first SPS schedule, and the SPS PDSCH is the last PDSCH of the first SPS schedule.
12. The method according to any one of claims 1 to 11, characterized in that, The DMRS sequence is generated by a generator polynomial, which includes the scrambling code ID.
13. A communication method, characterized in that, The method, executed by a terminal device, includes: The network device receives a demodulation reference signal (DMRS) sequence of the semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH), wherein the SPS PDSCH belongs to the first SPS scheduling. The scrambling code ID of the DMRS sequence is used to indicate whether the first SPS scheduler is released.
14. The method according to claim 13, characterized in that, The scrambling ID of the DMRS sequence is also used to identify the terminal device.
15. The method according to claim 13 or 14, characterized in that, The scrambling ID of the DMRS sequence is used to indicate whether the SPS schedule has been released, including: The scrambling ID of the DMRS sequence belongs to the first set, and the first SPS scheduler is released; The scrambling ID of the DMRS sequence belongs to the second set, and the first SPS scheduler does not release it.
16. The method according to claim 15, characterized in that, The method further includes: The network device receives a first scrambling code ID and a second scrambling code ID, wherein the first scrambling code ID belongs to the first set and the second scrambling code ID belongs to the second set.
17. The method according to claim 16, characterized in that, The first scrambling code ID and the second scrambling code ID sent by the receiving network device include: The network device receives a first Radio Resource Control (RRC) message, which includes a first scrambling code ID and a second scrambling code ID. The first RRC message is used to configure the parameters of the first SPS scheduling.
18. The method according to claim 13, characterized in that, The scrambling code ID is associated with the Configuration Scheduling CS-RNTI group, which is used to identify the terminal device.
19. The method according to claim 18, characterized in that, The CS-RNTI group includes at least one of the following: A third set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the third set, and the first SPS schedule is released; A fourth set consisting of at least one CS-RNTI, wherein the CS-RNTI corresponding to the scrambling ID of the DMRS sequence belongs to the fourth set, and the first SPS scheduler is not released.
20. The method according to claim 19, characterized in that, The method further includes: The network device receives a first CS-RNTI and a second CS-RNTI, where the first CS-RNTI belongs to the third set and the second CS-RNTI belongs to the fourth set.
21. The method according to claim 20, characterized in that, The first CS-RNTI and the second CS-RNTI sent by the receiving network device include: The system receives a second RRC message sent by a network device. The second RRC message includes the first CS-RNTI and the second CS-RNTI. The second RRC message is used to configure the parameters of the first SPS scheduling.
22. The method according to any one of claims 13 to 21, characterized in that, The scrambling ID includes at least one of the following: Scrambling code ID0; Scrambling code ID1.
23. The method according to any one of claims 13 to 22, characterized in that, The scrambling ID of the DMRS sequence is used to indicate the release of the first SPS schedule, and the SPS PDSCH is the last PDSCH of the first SPS schedule.
24. The method according to any one of claims 13 to 23, characterized in that, The DMRS sequence is generated by a generator polynomial, which includes the scrambling code ID.
25. A communication system, characterized in that, The method includes a network device and a terminal device, wherein the network device is configured to implement the method of any one of claims 1 to 12, and the terminal device is configured to implement the method of any one of claims 13 to 24.
26. A communication device, characterized in that, The communication device is used to perform the method according to any one of claims 1 to 12 or 13 to 24.
27. A storage medium storing instructions, characterized in that, When the instructions are executed on a communication device, the communication device performs the method of any one of claims 1 to 12 or 13 to 24.
28. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs and instructions is executed by a communication device, it implements the method of any one of claims 1 to 12 or 13 to 24.