Downlink resource multiplexing enhancement method, device, system, equipment and storage medium

Abstract

The present disclosure provides a downlink resource multiplexing enhancement method, device, system, equipment and storage medium, relating to the technical field of communication. The method comprises: monitoring Redcap downlink service conditions in the case of coexistence of Redcap and Legacy services; and configuring Redcap BWP resources and Legacy BWP resources according to the Redcap downlink service conditions to enhance the multiplexing of Redcap PDSCH and Legacy PDSCH on downlink resources. The present disclosure can configure multiple different downlink resource multiplexing enhancement schemes for different Redcap downlink service conditions to improve the multiplexing degree of Redcap PDSCH and Legacy PDSCH under different service conditions, not only improving the transmission rate of downlink service data, but also improving network resource utilization, network performance and user experience.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, system, device and storage medium for enhancing downlink resource multiplexing. Background Technology

[0002] RedCap (Reduced Capability) is a new technology standard proposed in 3GPP Rel-17 that supports features such as low power consumption, low cost, low latency, and strong coverage, and can reduce the complexity of UE (User Equipment, also known as terminal equipment or terminal).

[0003] In 3GPP Rel-17, the Non-Cell Defined Synchronization Signal Block (NCD-SSB) was used instead of the Cell Defined Synchronization Signal Block (CD-SSB) for RedCap. With the further enhancement of RedCap technology in 3GPP Rel-18, how to enhance uplink and downlink capabilities in scenarios where RedCap coexists with Legacy services (or UEs) is one of the main research topics in 3GPP Rel-18.

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] This disclosure provides a downlink resource reuse enhancement method, apparatus, system, device, and storage medium, which at least to some extent overcomes the technical problem that there is no downlink reuse capability enhancement solution for scenarios where RedCap and Legacy services (or UEs) coexist.

[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0007] According to one aspect of this disclosure, a method for enhancing downlink resource reuse is provided, the method comprising: monitoring the downlink service status of Redcap when Redcap and Legacy services coexist; and configuring Redcap BWP resources and Legacy BWP resources according to the downlink service status of Redcap to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0008] In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. This includes: when there is no Redcap downlink service, configuring Redcap BWP resources to be occupied only by NCD-SSB, and the resource blocks RB or resource units RE in Redcap BWP resources other than those occupied by NCD-SSB are unavailable to Legacy PDSCH, wherein Legacy PDSCH occupies only Legacy BWP resources.

[0009] In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. This includes: when Redcap downlink service exists, configuring the RB corresponding to NCD-SSB in Redcap BWP resources so that, except for the RE occupied by NCD-SSB, the remaining REs are unavailable to Redcap PDSCH, and the remaining RBs in Redcap BWP resources, except for the RB corresponding to NCD-SSB, are available to Redcap PDSCH. In this case, Legacy PDSCH only occupies Legacy BWP resources.

[0010] In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. This includes: when there is no Redcap downlink service, configuring Redcap BWP resources to be occupied only by NCD-SSB, and ensuring that the remaining RBs in Redcap BWP resources, except for those occupied by NCD-SSB, are available to Legacy PDSCH, and that the remaining REs in the RBs corresponding to NCD-SSB in Redcap BWP resources, except for those occupied by NCD-SSB, are available to Legacy PDSCH. In this case, Legacy PDSCH occupies not only Legacy BWP resources but also a portion of the RBs and REs within Redcap BWP resources.

[0011] In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. This includes: when there is Redcap downlink service and the traffic volume of Redcap service is higher than or equal to a first threshold, configuring the remaining RBs in Redcap BWP resources, except for the RB corresponding to NCD-SSB, to be available to Redcap PDSCH, and configuring the remaining REs in the RB corresponding to NCD-SSB in Redcap BWP resources, except for the REs occupied by NCD-SSB, to be available to Redcap PDSCH. Here, Legacy PDSCH only occupies Legacy BWP resources, and the first threshold is the traffic volume corresponding to when Redcap PDSCH fully occupies Redcap BWP resources.

[0012] In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. This includes: when there is Redcap downlink service and the traffic volume of Redcap service is higher than a second threshold and lower than a first threshold, configuring the remaining REs in the RB corresponding to NCD-SSB within the Redcap BWP resource, excluding the REs occupied by NCD-SSB, to be available to Redcap PDSCH. Furthermore, within the Redcap BWP resource, excluding the RB corresponding to NCD-SSB, the RBs closer to NCD-SSB are available to Redcap PDSCH, and the RBs farther from NCD-SSB are available to Legacy PDSCH. The Legacy PDSCH occupies not only Legacy BWP resources but also a portion of the RBs within the Redcap BWP resource. The first threshold is the traffic volume corresponding to when Redcap PDSCH fully occupies the Redcap BWP resource, and the second threshold is the traffic volume corresponding to when Redcap PDSCH fully occupies the RB corresponding to NCD-SSB within the Redcap BWP resource.

[0013] In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. This includes: when there is Redcap downlink service and the traffic volume of Redcap service is lower than or equal to a second threshold, configuring the remaining REs in the RB corresponding to NCD-SSB within the Redcap BWP resource, excluding the REs occupied by NCD-SSB, to be available for Redcap PDSCH, and configuring the remaining RBs in the Redcap BWP resource, excluding the RB corresponding to NCD-SSB, to be available for Legacy PDSCH. The second threshold is the traffic volume corresponding to when Redcap PDSCH fully occupies the RB corresponding to NCD-SSB within the Redcap BWP resource.

[0014] In some embodiments, the Redcap BWP resource is located within a first bandwidth range or a second bandwidth range of the cell bandwidth resource or the maximum Legacy BWP resource, wherein when the cell bandwidth resource or the maximum Legacy BWP resource represents the direction of bandwidth value from small to large from bottom to top, the first bandwidth range is the upper part of the cell bandwidth resource or the maximum Legacy BWP resource, and the second bandwidth range is the lower part of the cell bandwidth resource or the maximum Legacy BWP resource.

[0015] In some embodiments, the method further includes: configuring Legacy BWP resources to be occupied by CD-SSB, and the RB or RE of Legacy BWP resources other than the portion occupied by CD-SSB to be available to Legacy PDSCH.

[0016] In some embodiments, NCD-SSB and CD-SSB occupy the same time slot resources.

[0017] In some embodiments, NCD-SSB and CD-SSB occupy different time slot resources.

[0018] According to another aspect of this disclosure, a downlink resource reuse enhancement device is also provided, the device comprising: a service monitoring module for monitoring the downlink service status of Redcap when Redcap and Legacy services coexist; and a resource configuration module for configuring Redcap BWP resources and Legacy BWP resources according to the downlink service status of Redcap, so as to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0019] According to another aspect of this disclosure, a communication system is also provided, comprising: a Redcap terminal, a Legacy terminal, a network-side device, and a network management system; wherein, the Redcap terminal transmits service data of Redcap services with the network-side device; the Legacy terminal transmits service data of Legacy services with the network-side device; the network management system is used to monitor the downlink service status of Redcap services when Redcap and Legacy services coexist, and configure Redcap BWP resources and Legacy BWP resources according to the downlink service status of Redcap services, so as to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0020] According to another aspect of this disclosure, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the downlink resource multiplexing enhancement method described above by executing the executable instructions.

[0021] According to another aspect of this disclosure, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the downlink resource multiplexing enhancement method described in any of the preceding claims.

[0022] According to another aspect of this disclosure, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the downlink resource multiplexing enhancement method described above.

[0023] The downlink resource reuse enhancement method, apparatus, system, device, and storage medium provided in the embodiments of this disclosure enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH when Redcap and Legacy services coexist. This is achieved by monitoring the downlink service status of Redcap and configuring Redcap BWP resources and Legacy BWP resources according to the downlink service status of Redcap, thereby enhancing the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0024] Furthermore, various downlink resource reuse enhancement schemes are configured for different Redcap downlink service scenarios to improve the reuse of Redcap PDSCH and Legacy PDSCH under different service scenarios. This not only improves the transmission rate of downlink service data, but also improves network resource utilization, enhances network performance, and improves user experience.

[0025] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0026] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0027] Figure 1 This diagram illustrates a communication system architecture according to an embodiment of the present disclosure.

[0028] Figure 2 This diagram illustrates a flowchart of a downlink resource reuse enhancement method according to an embodiment of the present disclosure;

[0029] Figure 3 This diagram illustrates a first scheme for enhanced resource reuse configuration in an embodiment of this disclosure.

[0030] Figure 4 This diagram illustrates a second scheme for enhanced resource reuse configuration in an embodiment of this disclosure.

[0031] Figure 5 This diagram illustrates a third scheme for enhanced resource reuse configuration in an embodiment of this disclosure.

[0032] Figure 6 This diagram illustrates a fourth scheme for enhanced resource reuse configuration in embodiments of this disclosure.

[0033] Figure 7 A schematic diagram of a fifth scheme for enhanced resource reuse configuration in embodiments of this disclosure is shown;

[0034] Figure 8 A schematic diagram of a sixth scheme for enhanced resource reuse configuration in the embodiments of this disclosure is shown;

[0035] Figure 9 This diagram illustrates a downlink resource multiplexing enhancement device according to an embodiment of the present disclosure;

[0036] Figure 10 This diagram illustrates a structural block diagram of an electronic device according to an embodiment of the present disclosure.

[0037] Figure 11 A schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure is shown. Detailed Implementation

[0038] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0039] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0040] To facilitate understanding, before introducing the embodiments of this disclosure, the following explanations are provided for several terms involved in the embodiments of this disclosure:

[0041] 3GPP: 3rd Generation Partnership Project;

[0042] RedCap: Reduced Capability;

[0043] UE: User Equipment, also known as terminal equipment or terminal;

[0044] SSB: Synchronization Signal Block;

[0045] CD-SSB: Cell Defining Synchronization Signal Blocks;

[0046] NCD-SSB: Non-Cell Defining Synchronization Signal Blocks;

[0047] BWP: Bandwidth Part;

[0048] PDSCH: Physical Downlink Shared Channel;

[0049] RB: Resource Block;

[0050] RE: Resource Element;

[0051] RM: Rate Matching;

[0052] CORESET: In 5G NR, it is called "control resource set". It is a set of physical resources in a specific area of ​​the downlink resource grid, used to carry PDCCH (Physical Downlink Control Channel).

[0053] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0054] Figure 1 A schematic diagram of a communication system architecture to which the downlink resource multiplexing enhancement method of this disclosure can be applied is shown. Figure 1 As shown, the communication system includes: Redcap terminal 10, Legacy terminal 20, network-side equipment 30, and network management system 40.

[0055] Specifically, Redcap terminal 10 transmits Redcap service data with network-side device 30; Legacy terminal 20 transmits Legacy service data with network-side device 30.

[0056] The network management system 40 is used to monitor the Redcap downlink service status when Redcap and Legacy services coexist, and to configure Redcap BWP resources and Legacy BWP resources according to the Redcap downlink service status, so as to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0057] The medium that provides a communication link between Redcap terminal 10 or Legacy terminal 20 and network-side device 30 can be a wired network or a wireless network.

[0058] Optionally, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPsec) can be used to encrypt all or some links. In other embodiments, custom and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0059] Redcap terminal 10 can be a low-power electronic device such as an industrial wireless sensor, video surveillance equipment, or wearable device; Legacy terminal 20 can be a high-power electronic device such as a smartphone, tablet, laptop, or desktop computer. It should be noted that the specific types of Redcap terminal 10 and Legacy terminal 20 are not limited in this embodiment of the invention.

[0060] Optionally, the client for the application installed on different terminals may be the same, or the client for the same type of application based on different operating systems. Depending on the terminal platform, the specific form of the application's client may also differ.

[0061] The network-side device 30 can be a base station, relay, or access point, etc. The base station can be a 5G or later version base station (e.g., 5G NR NB), or a base station in other communication systems (e.g., eNB base station). It should be noted that the specific type of the network-side device 30 is not limited in this embodiment of the disclosure.

[0062] Those skilled in the art will know that Figure 1The number of Redcap terminals 10, Legacy terminals 20, network-side devices 30, and network management systems 40 shown in this embodiment is merely illustrative. Any number of Redcap terminals 10, Legacy terminals 20, network-side devices 30, and network management systems 40 can be used as needed. This disclosure does not limit the number of these components.

[0063] Under the above system architecture, this disclosure provides a downlink resource reuse enhancement method, which can be executed by any electronic device with computing capabilities.

[0064] In some embodiments, the downlink resource multiplexing enhancement method provided in this disclosure can be executed by the network management system in the above-mentioned communication system; in other embodiments, the downlink resource multiplexing enhancement method provided in this disclosure can be executed by the network-side device in the above-mentioned communication system; in other embodiments, the downlink resource multiplexing enhancement method provided in this disclosure can also be implemented by the network-side device in the above-mentioned communication system through interaction with the Redcap terminal or Legacy terminal.

[0065] Figure 2 This diagram illustrates a flowchart of a downlink resource reuse enhancement method according to an embodiment of the present disclosure, as follows: Figure 2 As shown, the downlink resource reuse enhancement method provided in this embodiment includes the following steps:

[0066] S202, Monitor Redcap downlink services when Redcap and Legacy services coexist.

[0067] It should be noted that, in this embodiment of the disclosure, Redcap services refer to services performed by degraded capability terminals, including but not limited to: eMBB, uRLLC and mMTC services; Legacy services refer to services performed by traditional terminals (i.e., ordinary capability terminals), including but not limited to: eMBB, uRLLC and mMTC services.

[0068] S204. Configure Redcap BWP and Legacy BWP resources according to Redcap downlink service requirements to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0069] It should be noted that, in this embodiment of the disclosure, Redcap BWP resources refer to BWP resources allocated for Redcap UEs; and Legacy BWP resources refer to BWP resources allocated for Legacy UEs. In this embodiment of the disclosure, Redcap PDSCH refers to the Physical Downlink Shared Channel for transmitting Redcap service data; and Legacy PDSCH refers to the Physical Downlink Shared Channel for transmitting Legacy service data.

[0070] In some embodiments, the downlink resource reuse enhancement method provided in this disclosure may further include the following steps: configuring Legacy BWP resources to be occupied by CD-SSB, and the RB or RE of Legacy BWP resources other than the portion occupied by CD-SSB to be available to Legacy PDSCH.

[0071] It should be noted that, in the embodiments disclosed herein, NCD-SSB and CD-SSB may occupy the same time slot resources or different time slot resources.

[0072] It should also be noted that in scenarios where Redcap and Legacy services coexist, a portion of the Legacy BWP resources originally allocated to the terminal needs to be allocated as Redcap resources. For ease of description, in this embodiment, the maximum Legacy BWP resources originally allocated to the terminal are collectively referred to as "cell bandwidth resources". The BWP resources allocated from the cell bandwidth resources for transmitting Redcap service data are called Redcap BWP resources, and the remaining BWP resources in the cell bandwidth resources used for transmitting Legacy service data are called Legacy BWP resources.

[0073] In some embodiments, the Redcap BWP resource in this disclosure may be located within a first bandwidth range or a second bandwidth range of the cell bandwidth resource or the maximum Legacy BWP resource. When the direction from bottom to top of the cell bandwidth resource or the maximum Legacy BWP resource represents the direction of bandwidth value from small to large, the first bandwidth range is the upper part of the cell bandwidth resource or the maximum Legacy BWP resource, and the second bandwidth range is the lower part of the cell bandwidth resource or the maximum Legacy BWP resource.

[0074] It should be noted that in this embodiment, the cell bandwidth resource refers to the maximum Legacy BWP resource allocated to the terminal. However, in actual scenarios, the Legacy BWP resource allocated to the terminal (e.g., 90MHz or 85Hz) may be less than or equal to the cell bandwidth resource (100Hz). Taking the cell bandwidth resource as an example, combined with... Figures 3-8The embodiments of this disclosure will be described below, assuming that Figures 3-8 In this embodiment, the direction from bottom to top represents the direction of bandwidth values ​​from smallest to largest. Therefore, the first bandwidth range of the cell bandwidth resource is the upper part (maximum bandwidth portion) of the cell bandwidth resource, and the second bandwidth range is the lower part (minimum bandwidth portion) of the cell bandwidth resource. For example, Figures 3-8 The Redcap BWP resource shown is located at the upper part of the cell bandwidth resource (the largest portion of the bandwidth).

[0075] Optionally, the Redcap BWP resources in this embodiment of the disclosure may be, but are not limited to, values ​​such as 20MHz, 10MHz, or 5MHz.

[0076] As can be seen from the above, the downlink resource reuse enhancement method provided in this embodiment enhances the reuse of downlink resources by monitoring the downlink service status of Redcap and Legacy services when Redcap and Legacy services coexist. This is achieved by configuring Redcap BWP and Legacy BWP resources based on the Redcap downlink service status. Furthermore, various downlink resource reuse enhancement schemes are configured for different Redcap downlink service scenarios to improve the reuse rate of Redcap PDSCH and Legacy PDSCH under different service conditions. This not only increases the transmission rate of downlink service data but also improves network resource utilization, enhances network performance, and improves user experience.

[0077] Still with Figures 3-8 The downlink resource multiplexing enhancement method provided in this embodiment will be described in detail using the cell bandwidth resources shown as an example. Figures 3-8 As shown, the Redcap BWP resource is placed in the upper part of the cell bandwidth resource (the largest bandwidth part), and the NCD-SSB and CD-SSB occupy the same time slot resource. It should be noted that the downlink resource multiplexing enhancement method provided in this embodiment is also applicable to the case where the Redcap BWP is placed in the lower part of the cell bandwidth (the largest bandwidth part), and where the CD-SSB and NCD-SSB are in different time slots. Figures 3-8 The part shown in Figure 11 is the time-frequency domain resource location of CORESET in Legacy BWP, that is, the time-frequency domain resource location of the control channel PDCCH.

[0078] In specific implementation, the configuration schemes for enhancing downlink resource reuse in this disclosure include, but are not limited to, the following six:

[0079] The first option is to configure Redcap BWP resources to be occupied only by NCD-SSB when there is no Redcap downlink service. In addition, the resource blocks RB or resource units RE in Redcap BWP resources other than those occupied by NCD-SSB are not available to Legacy PDSCH. Legacy PDSCH occupies only Legacy BWP resources.

[0080] Specific configuration schemes are as follows: Figure 3 As shown, when there is no Redcap downlink service (i.e., no Redcap PDSCH), only the NCD-SSB occupies the Redcap BWP (i.e., the part shown in icon 10). Other RBs / REs are not available to the Legacy PDSCH (i.e., the part shown in icon 40). The Legacy PDSCH is only within the Legacy BWP. The Legacy BWP resources are occupied by the CD-SSB (i.e., the part shown in icon 20), and the RBs or REs of the Legacy BWP resources other than the part occupied by the CD-SSB (i.e., the part shown in icon 30) are available to the Legacy PDSCH.

[0081] Among the above schemes, Redcap PDSCH and Legacy PDSCH have the lowest reuse rate, Redcap BWP has extremely low RE resource utilization, Redcap and Legacy UE have the lowest processing complexity, and the lowest cost.

[0082] The second option is to configure the RB corresponding to NCD-SSB within the Redcap BWP resource so that, apart from the RE occupied by NCD-SSB, the remaining REs are unavailable to Redcap PDSCH, and the remaining RBs within the Redcap BWP resource, apart from the RB corresponding to NCD-SSB, are available to Redcap PDSCH. In this case, Legacy PDSCH only occupies Legacy BWP resources.

[0083] Specific configuration schemes are as follows: Figure 4As shown, when there is a Redcap downlink service (with Redcap PDSCH), the remaining REs (i.e., the portion shown in icon 50) within the RB corresponding to NCD-SSB in the Redcap BWP, except for the REs occupied by NCD-SSB (i.e., the portion shown in icon 10), are unavailable to the Redcap PDSCH. The RBs above and below NCD-SSB (i.e., the portion shown in icon 60) are available to the Redcap PDSCH. The Legacy PDSCH is only available within the Legacy BWP. The Legacy BWP resources are occupied by CD-SSB (i.e., the portion shown in icon 20), and the RBs or REs of the Legacy BWP resources other than the portion occupied by CD-SSB (i.e., the portion shown in icon 30) are available to the Legacy PDSCH.

[0084] In the above scheme, Redcap PDSCH and Legacy PDSCH have low reuse, Redcap BWP has low RE resource utilization, Redcap and Legacy UE have low processing complexity, and low cost.

[0085] The third option is to configure Redcap BWP resources to be used only by NCD-SSB when there is no Redcap downlink service. In addition to the RBs occupied by NCD-SSB, the remaining RBs in Redcap BWP resources are available to Legacy PDSCH. In addition to the REs occupied by NCD-SSB, the remaining REs in the RBs corresponding to NCD-SSB in Redcap BWP resources are available to Legacy PDSCH. In addition to occupying Legacy BWP resources, Legacy PDSCH also occupies some of the RBs and REs in Redcap BWP resources.

[0086] Specific configuration schemes are as follows: Figure 5As shown, when there is no Redcap downlink service (no Redcap PDSCH), only the NCD-SSB occupies the Redcap BWP (i.e., the portion shown in icon 10). Besides the portion occupied by the Legacy PDSCH within the Legacy BWP (i.e., the portion shown in icon 30), the RBs above and below the NCD-SSB within the Redcap BWP (i.e., the portion shown in icon 80) are available to the Legacy PDSCH. Furthermore, the remaining REs within the RBs corresponding to the NCD-SSB within the Redcap BWP, excluding the REs occupied by the NCD-SSB (i.e., the portion shown in icon 70), are all available to the Legacy PDSCH. The Legacy PDSCH performs rate matching (RM) on these RE resources. Legacy BWP resources are occupied by the CD-SSB (i.e., the portion shown in icon 20), and the RBs or REs of the Legacy BWP resources other than the portion occupied by the CD-SSB (i.e., the portion shown in icon 30) are available to the Legacy PDSCH.

[0087] Among the above schemes, Redcap PDSCH and Legacy PDSCH have the highest reuse rate, Redcap BWP has the highest RE resource utilization rate, that is, Legacy UE has the highest utilization rate of the entire RE resource within the cell bandwidth, Legacy UE has the highest downlink rate, high processing complexity, and high cost; Redcap UE has low processing complexity and low cost.

[0088] The fourth option: When there is Redcap downlink service and the Redcap service volume is higher than or equal to the first threshold, configure the remaining RBs in the Redcap BWP resource, except for the RB corresponding to NCD-SSB, to be available for Redcap PDSCH. Also, in the Redcap BWP resource, the remaining REs in the RB corresponding to NCD-SSB, except for the REs occupied by NCD-SSB, are available for Redcap PDSCH. The Legacy PDSCH only occupies the Legacy BWP resource. The first threshold is the service volume corresponding to when Redcap PDSCH fully occupies the Redcap BWP resource.

[0089] Specific configuration schemes are as follows: Figure 6As shown, when there is Redcap downlink traffic and the traffic volume is large (with Redcap PDSCH, Redcap BWP is fully occupied), in addition to the NCD-SSB (i.e., the part shown in icon 10), the RBs above and below the NCD-SSB in the Redcap BWP (i.e., the part shown in icon 60) are available to Redcap PDSCH. In addition, the remaining REs in the RBs corresponding to the NCD-SSB in the Redcap BWP, except for the REs occupied by the NCD-SSB (i.e., the part shown in icon 90), are available to Redcap PDSCH. Redcap PDSCH performs rate matching on these RE resources. Legacy BWP resources are occupied by CD-SSB (i.e., the part shown in icon 20), and the RBs or REs of Legacy BWP resources other than the part occupied by CD-SSB (i.e., the part shown in icon 30) are available to Legacy PDSCH.

[0090] In the above scheme, Redcap PDSCH and Legacy PDSCH have low reuse, Redcap BWP has the highest RE resource utilization, that is, Redcap UE has the highest utilization of the entire RE resource in Redcap BWP, Redcap UE has the highest downlink rate, high processing complexity, and high cost; Legacy UE has low processing complexity and low cost.

[0091] The fifth option: When there is Redcap downlink service and the Redcap service volume is higher than the second threshold but lower than the first threshold, configure the RBs corresponding to NCD-SSB within the Redcap BWP resource, excluding the REs occupied by NCD-SSB, so that the remaining REs are available for Redcap PDSCH. Furthermore, within the Redcap BWP resource, excluding the RBs corresponding to NCD-SSB, the RBs closer to NCD-SSB are available for Redcap PDSCH, while the RBs farther from NCD-SSB are available for Legacy PDSCH. The Legacy PDSCH occupies not only Legacy BWP resources but also a portion of the RBs within the Redcap BWP resource. The first threshold is the service volume corresponding to when Redcap PDSCH fully occupies the Redcap BWP resource, and the second threshold is the service volume corresponding to when Redcap PDSCH fully occupies the RBs corresponding to NCD-SSB within the Redcap BWP resource.

[0092] Specific configuration schemes are as follows: Figure 7As shown, when there is Redcap downlink traffic and the traffic volume is medium (there is Redcap PDSCH, but Redcap BWP is not fully occupied), the remaining REs (i.e., the part shown in icon 90) in the RB corresponding to NCD-SSB within Redcap BWP, except for the REs occupied by NCD-SSB (i.e., the part shown in icon 10), are available to Redcap PDSCH. Redcap PDSCH performs rate matching on these RE resources. The RBs above and below NCD-SSB within Redcap BWP (close to NCD-SSB, i.e., the part shown in icon 60) are available to Redcap PDSCH. The remaining RBs above and below NCD-SSB within Redcap BWP (far from NCD-SSB, i.e., the part shown in icon 80) are available to Legacy PDSCH. Legacy BWP resources are occupied by CD-SSB (i.e., the part shown in icon 20), and the RBs or REs of Legacy BWP resources other than the part occupied by CD-SSB (i.e., the part shown in icon 30) are available to Legacy PDSCH.

[0093] Among the above schemes, Redcap PDSCH and Legacy PDSCH have a high degree of reuse, Redcap BWP has the highest RE resource utilization, Redcap UE downlink rate has high processing complexity and high cost; Legacy UE downlink rate has high processing complexity and high cost.

[0094] The sixth option: When there is Redcap downlink service and the Redcap service volume is lower than or equal to the second threshold, configure the RB corresponding to NCD-SSB in the Redcap BWP resource so that the remaining REs, excluding those occupied by NCD-SSB, are available for Redcap PDSCH, and the remaining RBs in the Redcap BWP resource, excluding those corresponding to NCD-SSB, are available for Legacy PDSCH. The second threshold is the service volume when the Redcap PDSCH fully occupies the RB corresponding to NCD-SSB in the Redcap BWP resource.

[0095] Specific configuration schemes are as follows: Figure 8As shown, when there is Redcap downlink traffic and the traffic volume is low (with Redcap PDSCH, only the remaining RE resources in the RB corresponding to NCD-SSB, excluding the RE occupied by NCD-SSB), the remaining RE resources in the RB corresponding to NCD-SSB in Redcap BWP, excluding the RE occupied by NCD-SSB (i.e., the part shown in icon 10), are available to Redcap PDSCH. Redcap PDSCH performs rate matching on these RE resources. The RBs above and below NCD-SSB in Redcap BWP (i.e., the part shown in icon 80) are available to Legacy PDSCH. Legacy BWP resources are occupied by CD-SSB (i.e., the part shown in icon 20), and the RBs or REs of Legacy BWP resources other than the part occupied by CD-SSB (i.e., the part shown in icon 30) are available to Legacy PDSCH.

[0096] Among the above schemes, Redcap PDSCH and Legacy PDSCH have high reusability, Redcap BWP has the highest RE resource utilization, Redcap UE has low downlink rate, medium processing complexity, and medium cost; Legacy UE has high downlink rate, high processing complexity, and high cost.

[0097] It should be noted that during Legacy PDSCH rate matching, the base station sends the Legacy rate matching model (i.e., Legacy RM Pattern) to the terminal so that the Legacy PDSCH can perform rate matching for the corresponding REs. During Redcap PDSCH rate matching, the base station sends the Redcap rate matching model (i.e., Redcap RMPattern) to the terminal so that the Redcap PDSCH can perform rate matching for the corresponding REs.

[0098] Based on the same inventive concept, this disclosure also provides a downlink resource multiplexing enhancement device, as described in the following embodiments. Since the principle by which this device embodiment solves the problem is similar to that of the above-described method embodiment, the implementation of this device embodiment can refer to the implementation of the above-described method embodiment, and repeated details will not be elaborated further.

[0099] Figure 9 This diagram illustrates a downlink resource multiplexing enhancement device according to an embodiment of the present disclosure, such as... Figure 9 As shown, the device includes a business monitoring module 91 and a resource configuration module 92.

[0100] The service monitoring module 91 is used to monitor the Redcap downlink service status when Redcap and Legacy services coexist; the resource configuration module 92 is used to configure Redcap BWP resources and Legacy BWP resources according to the Redcap downlink service status, so as to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0101] It should be noted that the aforementioned business monitoring module 91 and resource configuration module 92 correspond to S202 to S204 in the method embodiments. The examples and application scenarios implemented by these modules and their corresponding steps are the same, but they are not limited to the content disclosed in the aforementioned method embodiments. It should also be noted that these modules, as part of an apparatus, can be executed in a computer system, such as a set of computer-executable instructions.

[0102] In some embodiments, the resource configuration module 92 may include: a first configuration submodule 921, configured to configure Redcap BWP resources to be occupied only by NCD-SSB when there is no Redcap downlink service, and the resource blocks RB or resource units RE in the Redcap BWP resources other than the part occupied by NCD-SSB are unavailable to Legacy PDSCH, wherein Legacy PDSCH occupies only Legacy BWP resources.

[0103] In some embodiments, the resource configuration module 92 may further include: a second configuration submodule 922, configured to configure, when there is a Redcap downlink service, that the remaining REs in the RB corresponding to NCD-SSB within the Redcap BWP resource, except for the REs occupied by NCD-SSB, are unavailable to the Redcap PDSCH, and that the remaining RBs in the Redcap BWP resource, except for the RB corresponding to NCD-SSB, are available to the Redcap PDSCH, wherein the Legacy PDSCH only occupies the Legacy BWP resource.

[0104] In some embodiments, the resource configuration module 92 may further include: a third configuration submodule 923, configured to configure Redcap BWP resources to be occupied only by NCD-SSB when there is no Redcap downlink service, and that the remaining RBs in Redcap BWP resources, except for the RBs occupied by NCD-SSB, are available to Legacy PDSCH, and that the remaining REs in the RBs corresponding to NCD-SSB in Redcap BWP resources, except for the REs occupied by NCD-SSB, are available to Legacy PDSCH, wherein Legacy PDSCH occupies not only Legacy BWP resources but also a portion of the RBs and REs in Redcap BWP resources.

[0105] In some embodiments, the resource configuration module 92 may further include: a fourth configuration submodule 924, configured to configure the remaining RBs in the Redcap BWP resource, excluding the RBs corresponding to NCD-SSB, to be available for Redcap PDSCH when there is Redcap downlink service and the service volume of Redcap service is higher than or equal to a first threshold, and the remaining REs in the RBs corresponding to NCD-SSB in the Redcap BWP resource, excluding the REs occupied by NCD-SSB, to be available for Redcap PDSCH, wherein the Legacy PDSCH only occupies the Legacy BWP resource, and the first threshold is the service volume corresponding to when Redcap PDSCH occupies the Redcap BWP resource.

[0106] In some embodiments, the resource configuration module 92 may further include: a fifth configuration submodule 925, configured to configure, when there is a Redcap downlink service and the traffic volume of the Redcap service is higher than a second threshold and lower than a first threshold, that the remaining REs in the RB corresponding to NCD-SSB within the RedcapBWP resource, excluding the REs occupied by NCD-SSB, are available for Redcap PDSCH, and that, in the remaining RBs in the Redcap BWP resource, excluding the RB corresponding to NCD-SSB, the RBs closer to NCD-SSB are available for Redcap PDSCH, and the RBs farther from NCD-SSB are available for Legacy PDSCH, wherein the Legacy PDSCH occupies not only the LegacyBWP resource but also a portion of the RBs within the Redcap BWP resource, the first threshold is the traffic volume corresponding to when the Redcap PDSCH fully occupies the Redcap BWP resource, and the second threshold is the traffic volume corresponding to when the Redcap PDSCH fully occupies the RB corresponding to NCD-SSB within the Redcap BWP resource.

[0107] In some embodiments, the resource configuration module 92 may further include: a sixth configuration submodule 926, configured to configure, when there is a Redcap downlink service and the traffic volume of the Redcap service is lower than or equal to a second threshold, that the remaining REs in the RB corresponding to the NCD-SSB within the Redcap BWP resource, excluding the REs occupied by the NCD-SSB, are available for the Redcap PDSCH, and that the remaining RBs in the Redcap BWP resource, excluding the RB corresponding to the NCD-SSB, are available for the Legacy PDSCH, wherein the second threshold is the traffic volume corresponding to when the Redcap PDSCH fully occupies the RB corresponding to the NCD-SSB within the Redcap BWP resource.

[0108] In some embodiments of this disclosure, the Redcap BWP resource is located within a first bandwidth range or a second bandwidth range of the cell bandwidth resource or the maximum Legacy BWP resource. When the direction from bottom to top of the cell bandwidth resource or the maximum Legacy BWP resource represents the direction of bandwidth value from small to large, the first bandwidth range is the upper part of the cell bandwidth resource or the maximum Legacy BWP resource, and the second bandwidth range is the lower part of the cell bandwidth resource or the maximum Legacy BWP resource.

[0109] In some embodiments, the resource configuration module 92 is further configured to: configure Legacy BWP resources to be occupied by CD-SSB, and to make the RB or RE of Legacy BWP resources other than the portion occupied by CD-SSB available to Legacy PDSCH.

[0110] It should be noted that, in the embodiments disclosed herein, NCD-SSB and CD-SSB may occupy the same time slot resources or different time slot resources.

[0111] The downlink resource reuse enhancement method and apparatus provided in this disclosure can achieve, but are not limited to, the following technical effects: ① By considering the processing complexity and design cost of Redcap UE and Legacy UE under different service conditions in the coexistence scenario of Redcap and Legacy services (or UEs), different downlink resource reuse enhancement schemes can be selected, which can maximize the reuse capability of Redcap PDSCH and Legacy PDSCH, improve network resource utilization, and enhance network performance; ② Improve the reuse degree, reuse flexibility, and diversity of Redcap PDSCH and Legacy PDSCH under different service conditions; ③ Improve the utilization rate of RE resources within Redcap BWP; ④ Improve the reuse efficiency of Redcap UE and Legacy PDSCH. The UE's downlink rate and system throughput; ⑤ It is suitable for both FR1 and FR2, both Legacy (eMBB, uRLLC and mMTC) services and Redcap (eMBB, uRLLC and mMTC) services, and has universality and practicality; ⑥ It improves the completeness, diversity, regularity and compatibility of the protocol, improves the user experience of 5G and later communication systems, and has broad application prospects.

[0112] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0113] The following reference Figure 10 To describe an electronic device 1000 according to such an embodiment of the present disclosure. Figure 10 The electronic device 1000 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0114] like Figure 10 As shown, the electronic device 1000 is manifested in the form of a general-purpose computing device. The components of the electronic device 1000 may include, but are not limited to: at least one processing unit 1010, at least one storage unit 1020, and a bus 1030 connecting different system components (including storage unit 1020 and processing unit 1010).

[0115] The storage unit stores program code that can be executed by the processing unit 1010, causing the processing unit 1010 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, the processing unit 1010 can perform the following steps of the above method embodiments: monitoring the Redcap downlink service status when Redcap and Legacy services coexist; configuring Redcap BWP resources and Legacy BWP resources according to the Redcap downlink service status to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

[0116] Storage unit 1020 may include readable media in the form of volatile storage units, such as random access memory (RAM) 10201 and / or cache memory 10202, and may further include read-only memory (ROM) 10203.

[0117] Storage unit 1020 may also include a program / utility 10204 having a set (at least one) program module 10205, such program module 10205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0118] Bus 1030 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the multiple bus structures.

[0119] Electronic device 1000 can also communicate with one or more external devices 1040 (e.g., keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable a user to interact with electronic device 1000, and / or any device that enables electronic device 1000 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1050. Furthermore, electronic device 1000 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1060. As shown, network adapter 1060 communicates with other modules of electronic device 1000 via bus 1030. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0120] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0121] Specifically, according to embodiments of this disclosure, the process described above with reference to the flowchart can be implemented as a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the inactive security configuration information delivery method described above.

[0122] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. Figure 11 This illustration shows a schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure, such as... Figure 11As shown, the computer-readable storage medium 1100 stores a program product capable of implementing the methods described above. In some possible embodiments, various aspects of this disclosure may also be implemented as a program product comprising program code that, when run on a terminal device, causes the terminal device to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure.

[0123] More specific examples of computer-readable storage media in this disclosure may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0124] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.

[0125] Optionally, the program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0126] In practical implementation, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0127] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0128] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0129] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

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

Claims

1. A method for enhancing downlink resource reuse, characterized in that, include: When Redcap and Legacy services coexist, monitor the downlink service status of Redcap. Configure Redcap BWP and Legacy BWP resources according to Redcap downlink service requirements to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. The method further includes: Configure Legacy BWP resources to be occupied by CD-SSB, and ensure that the RB or RE of Legacy BWP resources other than the portion occupied by CD-SSB are available to Legacy PDSCH.

2. The downlink resource reuse enhancement method according to claim 1, characterized in that, Based on the Redcap downlink service requirements, configure Redcap BWP and Legacy BWP resources to enhance the reuse of downlink resources between Redcap PDSCH and Legacy PDSCH, including: When there is no Redcap downlink service, the Redcap BWP resource is configured to be occupied only by NCD-SSB, and the resource blocks RB or resource units RE in the Redcap BWP resource other than the part occupied by NCD-SSB are not available to Legacy PDSCH. Among them, Legacy PDSCH only occupies Legacy BWP resources.

3. The downlink resource reuse enhancement method according to claim 1, characterized in that, Based on the Redcap downlink service requirements, configure Redcap BWP and Legacy BWP resources to enhance the reuse of downlink resources between Redcap PDSCH and Legacy PDSCH, including: When Redcap downlink services exist, the RB corresponding to NCD-SSB within the Redcap BWP resource is configured such that, apart from the RE occupied by NCD-SSB, the remaining REs are unavailable to Redcap PDSCH. In addition, the RBs within the Redcap BWP resource, apart from the RB corresponding to NCD-SSB, are available to Redcap PDSCH. Among these, Legacy PDSCH only occupies Legacy BWP resources.

4. The downlink resource reuse enhancement method according to claim 1, characterized in that, Based on the Redcap downlink service requirements, configure Redcap BWP and Legacy BWP resources to enhance the reuse of downlink resources between Redcap PDSCH and Legacy PDSCH, including: When there is no Redcap downlink service, the Redcap BWP resource is configured to be occupied only by the NCD-SSB. In addition to the RB occupied by the NCD-SSB, the remaining RBs in the Redcap BWP resource are available to the Legacy PDSCH. In addition to the RE occupied by the NCD-SSB, the remaining REs in the RBs corresponding to the NCD-SSB in the Redcap BWP resource are available to the Legacy PDSCH. The Legacy PDSCH occupies not only the Legacy BWP resource but also a portion of the RBs and REs in the Redcap BWP resource.

5. The downlink resource reuse enhancement method according to claim 1, characterized in that, Based on the Redcap downlink service requirements, configure Redcap BWP and Legacy BWP resources to enhance the reuse of downlink resources between Redcap PDSCH and Legacy PDSCH, including: When there is Redcap downlink service and the traffic volume of Redcap service is higher than or equal to the first threshold, the remaining RBs in the RedcapBWP resource, except for the RB corresponding to NCD-SSB, are available to Redcap PDSCH. In addition, the remaining REs in the RB corresponding to NCD-SSB in the Redcap BWP resource, except for the RE occupied by NCD-SSB, are available to Redcap PDSCH. The Legacy PDSCH only occupies the Legacy BWP resource. The first threshold is the traffic volume corresponding to when Redcap PDSCH fully occupies the Redcap BWP resource.

6. The downlink resource reuse enhancement method according to claim 1, characterized in that, Based on the Redcap downlink service requirements, configure Redcap BWP and Legacy BWP resources to enhance the reuse of downlink resources between Redcap PDSCH and Legacy PDSCH, including: When there is Redcap downlink service and the Redcap service volume is higher than the second threshold but lower than the first threshold, the remaining REs in the RB corresponding to NCD-SSB within the Redcap BWP resource, excluding the REs occupied by NCD-SSB, are available for Redcap PDSCH. Furthermore, within the Redcap BWP resource, excluding the RB corresponding to NCD-SSB, the RBs closer to NCD-SSB are available for Redcap PDSCH, while the RBs farther from NCD-SSB are available for Legacy PDSCH. The Legacy PDSCH occupies not only Legacy BWP resources but also a portion of the RBs within the Redcap BWP resource. The first threshold is the service volume corresponding to when Redcap PDSCH fully occupies the Redcap BWP resource, and the second threshold is the service volume corresponding to when Redcap PDSCH fully occupies the RB corresponding to NCD-SSB within the Redcap BWP resource.

7. The downlink resource reuse enhancement method according to claim 6, characterized in that, Based on the Redcap downlink service requirements, configure Redcap BWP and Legacy BWP resources to enhance the reuse of downlink resources between Redcap PDSCH and Legacy PDSCH, including: When there is Redcap downlink service and the Redcap service volume is lower than or equal to the second threshold, the remaining REs in the RB corresponding to NCD-SSB within the Redcap BWP resource, excluding the REs occupied by NCD-SSB, are available for Redcap PDSCH, and the remaining RBs in the Redcap BWP resource, excluding the RB corresponding to NCD-SSB, are available for Legacy PDSCH. The second threshold is the service volume corresponding to when Redcap PDSCH fully occupies the RB corresponding to NCD-SSB within the Redcap BWP resource.

8. The downlink resource reuse enhancement method according to any one of claims 1 to 7, characterized in that, The RedcapBWP resource is located within a first bandwidth range or a second bandwidth range of the cell bandwidth resource or the maximum Legacy BWP resource. When the direction from bottom to top of the cell bandwidth resource or the maximum Legacy BWP resource represents the direction of bandwidth value from small to large, the first bandwidth range is the upper part of the cell bandwidth resource or the maximum Legacy BWP resource, and the second bandwidth range is the lower part of the cell bandwidth resource or the maximum Legacy BWP resource.

9. The downlink resource reuse enhancement method according to claim 1, characterized in that, NCD-SSB and CD-SSB occupy the same time slot resources.

10. The downlink resource reuse enhancement method according to claim 1, characterized in that, NCD-SSB and CD-SSB occupy different time slot resources.

11. A downlink resource reuse enhancement device, characterized in that, include: The business monitoring module is used to monitor the downlink business status of Redcap when Redcap and Legacy services coexist. The resource configuration module is used to configure Redcap BWP resources and Legacy BWP resources according to the Redcap downlink service situation, so as to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH; The resource configuration module is further configured to: configure Legacy BWP resources to be occupied by CD-SSB, and ensure that the RB or RE of Legacy BWP resources other than the portion occupied by CD-SSB are available to Legacy PDSCH.

12. A communication system, characterized in that, include: Redcap terminals, Legacy terminals, network-side devices, and network management systems; Specifically, the Redcap terminal transmits Redcap service data with the network-side equipment; the Legacy terminal transmits Legacy service data with the network-side equipment. The network management system is used to monitor the downlink service status of Redcap when Redcap and Legacy services coexist, and to configure Redcap BWP resources and Legacy BWP resources according to the downlink service status of Redcap, so as to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. The network management system is also used to: configure Legacy BWP resources to be occupied by CD-SSB, and to ensure that the RB or RE of Legacy BWP resources other than those occupied by CD-SSB are available to Legacy PDSCH.

13. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the downlink resource multiplexing enhancement method according to any one of claims 1 to 10 by executing the executable instructions.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the downlink resource reuse enhancement method according to any one of claims 1 to 10.

Images