WO2024037569A1

WO2024037569A1 - Downlink resource multiplexing enhancement method, system, and related device

Info

Publication number: WO2024037569A1
Application number: PCT/CN2023/113387
Authority: WO
Inventors: 张志荣; 郭瀚; 李皛; 侯佳; 林平平
Original assignee: 中国电信股份有限公司
Priority date: 2022-08-19
Filing date: 2023-08-16
Publication date: 2024-02-22
Also published as: CN117676844A

Abstract

The present disclosure provides a downlink resource multiplexing enhancement method, an apparatus, a system, a device, a storage medium and a computer program product, relating to the technical field of communications. The method comprises: when Redcap and legacy services are both present, monitoring a Redcap downlink service situation; and according to the Redcap downlink service situation, configuring a Redcap BWP resource and a legacy BWP resource, so as to enhance downlink resource multiplexing of a Redcap PDSCH and a legacy PDSCH. The present disclosure can configure a plurality of different downlink resource multiplexing enhancement solutions for different Redcap downlink service situations, so as to increase the degree of multiplexing of Redcap PDSCHs and legacy PDSCHs in different service situations, so that the transmission rate of downlink service data is increased and the utilization rate of network resources is increased, thus improving the network performance, and enhancing the user experience.

Description

Downlink resource reuse enhancement method, system and related equipment

Cross-references to related applications

This disclosure claims priority to the Chinese patent application with application number 202211003127. The entire contents of are incorporated herein by reference in their entirety.

Technical field

The present disclosure relates to the field of communication technology, and in particular, to a downlink resource multiplexing enhancement method, device, system, equipment, storage medium and computer program product.

Background technique

RedCap (Reduced Capability, reduced capability) is a new technology standard proposed in 3GPP Rel-17. It supports low power consumption, low cost, low latency, strong coverage and other features, and can reduce UE (User Equipment, user equipment, etc.) called terminal equipment or terminal) complexity.

In 3GPP Rel-17, non-cell-defined synchronization signal block NCD-SSB is used instead of 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 the coexistence scenario of RedCap and Legacy (traditional) services (or UE) is one of the main topics of 3GPP Rel-18 research.

It should be noted that the information disclosed in the above background section is only used to enhance understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to those of ordinary skill in the art.

Contents of the invention

The present disclosure provides a downlink resource multiplexing enhancement method, device, system, equipment, storage medium and computer program product, which at least to a certain extent overcomes the lack of downlink multiplexing for RedCap and Legacy business (or UE) coexistence scenarios in related technologies. Technical issues with capacity enhancement programmes.

Additional features and advantages of the disclosure will be apparent from the following detailed description, or, in part, may be learned by practice of the disclosure.

According to one aspect of the present disclosure, a method for enhancing downlink resource reuse is provided. The method includes: monitoring the Redcap downlink service situation when Redcap and Legacy services coexist; and monitoring the Redcap BWP resources and Legacy services according to the Redcap downlink service situation. BWP resources are configured to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including: when no When there is Redcap downlink service, configure the Redcap BWP resource to be occupied only by NCD-SSB, and the resource block RB or resource unit RE in the Redcap BWP resource except the part occupied by NCD-SSB is not available to Legacy PDSCH. Among them, Legacy PDSCH only occupies Legacy. BWP resources.

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, including: configuring Redcap BWP resources when there is Redcap downlink service In the RB corresponding to the NCD-SSB, except for the RE occupied by the NCD-SSB, the remaining REs are not available to Redcap PDSCH, and in the Redcap BWP resources, except the RB corresponding to the NCD-SSB, the remaining RBs are available to the Redcap PDSCH, where , Legacy PDSCH only occupies Legacy BWP resources.

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, including: configuring Redcap BWP when there is no Redcap downlink service The resource is only occupied by NCD-SSB, and in the Redcap BWP resource, except for the RB occupied by NCD-SSB, the remaining RBs are available to Legacy PDSCH, and in the Redcap BWP resource, the RB corresponding to NCD-SSB except the RE occupied by NCD-SSB In addition, the remaining REs are available to Legacy PDSCH. In addition to occupying Legacy BWP resources, Legacy PDSCH also occupies some RBs and REs within the Redcap BWP resources.

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, including: when there is Redcap downlink service and the traffic volume of Redcap service When it is higher than or equal to the first threshold, except for the RB corresponding to NCD-SSB in the configured Redcap BWP resource, the remaining RBs are available to Redcap PDSCH, and the RB corresponding to NCD-SSB in the Redcap BWP resource is except for the RB occupied by NCD-SSB. In addition to REs, the remaining REs are available to Redcap PDSCH, where Legacy PDSCH only occupies Legacy BWP resources, and the first threshold is the corresponding traffic volume when Redcap PDSCH occupies all Redcap BWP resources.

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, including: when there is Redcap downlink service and the traffic volume of Redcap service When it is higher than the second threshold and less than the first threshold, in addition to the REs occupied by NCD-SSB in the RB corresponding to NCD-SSB in the configured Redcap BWP resources, the remaining REs are available to Redcap PDSCH, and in the Redcap BWP resources except NCD- In addition to the RBs corresponding to SSB, some of the remaining RBs close to NCD-SSB are available to Redcap PDSCH, and some RBs far away from NCD-SSB are available to Legacy PDSCH. Among them, Legacy PDSCH not only occupies Legacy BWP resources, but also occupies Redcap BWP resources. For the internal RBs, the first threshold is the traffic volume corresponding to when the Redcap PDSCH occupies the Redcap BWP resource, and the second threshold is the traffic volume corresponding to the Redcap PDSCH occupies the RB corresponding to the NCD-SSB in the Redcap BWP resource.

In some embodiments, Redcap BWP resources and Legacy BWP resources are configured according to Redcap downlink service conditions to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including: when there is When the Redcap downlink service and the traffic volume of the Redcap service is lower than or equal to the second threshold, in the RB corresponding to the NCD-SSB in the configured Redcap BWP resource, in addition to the REs occupied by the NCD-SSB, the remaining REs are available to the Redcap PDSCH, and Except for the RB corresponding to NCD-SSB in the Redcap BWP resource, the remaining RBs are available to Legacy PDSCH, where the second threshold is the traffic volume corresponding to when Redcap PDSCH fills up the RB corresponding to NCD-SSB in the Redcap BWP resource.

In some embodiments, the Redcap BWP resource is located in the first bandwidth range or the second bandwidth range within the cell bandwidth resource or the maximum Legacy BWP resource, where when the cell bandwidth resource or the maximum Legacy BWP resource goes from bottom to top, it represents the bandwidth value is smaller than In the large direction, the first bandwidth range is the upper end part of the cell bandwidth resource or the maximum Legacy BWP resource, and the second bandwidth range is the lower end part of the cell bandwidth resource or the maximum Legacy BWP resource.

In some embodiments, the method further includes: configuring the Legacy BWP resource to be occupied by the CD-SSB, and the RBs or REs of the Legacy BWP resource except the CD-SSB occupied part are available to the Legacy PDSCH.

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

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

According to another aspect of the present disclosure, a downlink resource multiplexing enhancement device is also provided. The device includes: a service monitoring module, configured to monitor the Redcap downlink service situation when Redcap and Legacy services coexist; a resource configuration module, It is set to configure Redcap BWP resources and Legacy BWP resources according to the Redcap downlink business conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

According to another aspect of the present disclosure, a communication system is also provided. The system includes: a Redcap terminal, a Legacy terminal, a network side device and a network management system; wherein the Redcap service is transmitted between the Redcap terminal and the network side device. data; the business data of the Legacy service is transmitted between the Legacy terminal and the network side device; the network management system is used to monitor the Redcap downlink business situation when the Redcap and Legacy services coexist, and to perform the Redcap downlink service condition according to the Redcap downlink business condition. BWP resources and Legacy BWP resources are configured to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

According to another aspect of the present disclosure, an electronic device is also provided, the electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the The executable instructions are used to execute the downlink resource multiplexing enhancement method described in any one of the above.

According to another aspect of the present disclosure, a computer-readable storage medium is also provided, on which a computer program is stored. When the computer program is executed by a processor, any one of the above downlink resource multiplexing enhancement methods is implemented.

According to another aspect of the present disclosure, a computer program product or computer program is also provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs any one of the above downlink resource multiplexing enhancement methods.

The downlink resource multiplexing enhancement method, device, system, equipment, storage medium and computer program product provided in the embodiments of the present disclosure can monitor the Redcap downlink service situation when Redcap and Legacy services coexist. Then configure the Redcap BWP resources and Legacy BWP resources according to the Redcap downlink business conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

Furthermore, according to different Redcap downlink business conditions, configure a variety of different downlink resource reuse enhancement schemes to improve the reuse of Redcap PDSCH and Legacy PDSCH under different business conditions. This can not only increase the transmission rate of downlink business data, but also It can improve network resource utilization, improve network performance, and enhance user experience.

It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and do not limit the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. Obviously, the drawings in the following description are only some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 shows a schematic diagram of a communication system architecture in an embodiment of the present disclosure;

Figure 2 shows a flow chart of a downlink resource multiplexing enhancement method in an embodiment of the present disclosure;

Figure 3 shows a schematic diagram of the first solution for enhanced configuration of resource multiplexing in an embodiment of the present disclosure;

Figure 4 shows a schematic diagram of the second solution for enhanced configuration of resource multiplexing in an embodiment of the present disclosure;

Figure 5 shows a schematic diagram of a third solution for resource multiplexing enhanced configuration in an embodiment of the present disclosure;

Figure 6 shows a schematic diagram of the fourth solution for resource multiplexing enhanced configuration in the embodiment of the present disclosure;

Figure 7 shows a schematic diagram of the fifth solution of resource multiplexing enhanced configuration in the embodiment of the present disclosure;

Figure 8 shows a schematic diagram of the sixth solution for resource multiplexing enhanced configuration in the embodiment of the present disclosure;

Figure 9 shows a schematic diagram of a downlink resource multiplexing enhancement device in an embodiment of the present disclosure;

Figure 10 shows a structural block diagram of an electronic device in an embodiment of the present disclosure;

Figure 11 shows a schematic diagram of a computer-readable storage medium in an embodiment of the present disclosure.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of the example 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.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or in These functional entities are implemented in different network and/or processor devices and/or microcontroller devices.

To facilitate understanding, before introducing the embodiments of the present disclosure, several terms involved in the embodiments of the present disclosure are first explained as follows:

3GPP: 3rd Generation Partnership Project, translated as the third generation cooperation plan;

RedCap: Reduced Capability, translated as reduced ability;

UE: User Equipment, translated as user equipment, also known as terminal equipment or terminal;

SSB: Synchronization Signal Block, synchronization signal block;

CD-SSB: Cell Defining Synchronization Signal Blocks, cell definition synchronization signal block;

NCD-SSB: Non Cell Defining Synchronization Signal Blocks, non-cell defining synchronization signal blocks;

BWP: Bandwidth Part, bandwidth part;

PDSCH: Physical Downlink Shared Channel, physical downlink shared channel;

RB: Resource Block, resource block;

RE: Resource Element, resource unit;

RM: Rate Matching, rate matching;

CORESET: Known as "control resource set" in 5G NR, it is a set of physical resources in a specific area in the downlink resource grid, used to carry PDCCH (Physical Downlink Control Channel, physical downlink control channel).

Specific implementation modes of the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Figure 1 shows a schematic diagram of a communication system architecture to which the downlink resource multiplexing enhancement method in an embodiment of the present disclosure can be applied. As shown in Figure 1, the communication system includes: Redcap terminal 10, Legacy terminal 20, network side device 30 and network management system 40.

Among them, the service data of the Redcap service is transmitted between the Redcap terminal 10 and the network side device 30; the service data of the Legacy service is transmitted between the Legacy terminal 20 and the network side device 30;

The network management system 40 is used to monitor the Redcap downlink business conditions when Redcap and Legacy services coexist, and configure the Redcap BWP resources and Legacy BWP resources according to the Redcap downlink business conditions to enhance the Redcap PDSCH and Legacy PDSCH's use of downlink resources. Reuse.

The medium that provides the communication link between the Redcap terminal 10 or the Legacy terminal 20 and the network side device 30 may be a wired network or a wireless network.

Optionally, the above-mentioned wireless network or wired network uses standard communication technologies and/or protocols. The network is usually the Internet, but can also be any network, including but not limited to Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless network, private network, or virtual private network). In some embodiments, technologies and/or formats including Hyper Text Mark-up Language (HTML), Extensible Markup Language (XML), etc. are used to represent the data exchanged through the network. data. In addition, you can also use technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (Virtual Private Network, VPN), Internet Protocol Security (Internet Protocol Security, IPsec), etc. Conventional encryption techniques to encrypt all or some links. In other embodiments, customized and/or dedicated data communication technologies may also be used in place of or in addition to the above-described data communication technologies.

The Redcap terminal 10 may be an electronic device with reduced capabilities such as an industrial wireless sensor, a video surveillance device, or a wearable device; the Legacy terminal 20 may be an electronic device with normal capabilities such as a smartphone, a tablet computer, a laptop computer, or a desktop computer. It should be noted that the embodiment of the present invention does not limit the specific types of the Redcap terminal 10 and the Legacy terminal 20 .

Optionally, the clients of the application installed in different terminals are the same, or the clients of the same type of application based on different operating systems. Based on different terminal platforms, the specific form of the client of the application may also be different.

The network side device 30 may be a base station, a relay, an access point, etc. The base station may be a 5G and later version base station (for example: 5G NR NB), or a base station in other communication systems (for example: eNB base station). It should be noted that the network side device 30 is not limited in this embodiment of the disclosure. Concrete type.

Those skilled in the art will know that the numbers of Redcap terminals 10 , Legacy terminals 20 , network side devices 30 and network management systems 40 in Figure 1 are only illustrative. According to actual needs, there can be any number of Redcap terminals 10 and Legacy terminals 20. Network side equipment 30 and network management system 40. The embodiments of the present disclosure do not limit this.

Under the above system architecture, embodiments of the present disclosure provide a downlink resource multiplexing enhancement method, which can be executed by any electronic device with computing processing capabilities.

In some embodiments, the downlink resource multiplexing enhancement method provided in the embodiments of the present disclosure can be executed by the network management system in the above communication system; in other embodiments, the downlink resource multiplexing enhancement method provided in the embodiments of the present disclosure It 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 the embodiment of the present disclosure can also be executed by the network-side device in the above-mentioned communication system and the Redcap terminal or Legacy terminal through implemented interactively.

Figure 2 shows a flow chart of a downlink resource multiplexing enhancement method in an embodiment of the present disclosure. As shown in Figure 2, the downlink resource multiplexing enhancement method provided in an embodiment of the present disclosure includes the following steps:

S202: When Redcap and Legacy services coexist, monitor the Redcap downstream service situation.

It should be noted that the Redcap service in the embodiment of the present disclosure refers to services performed by terminals with reduced capabilities, including but not limited to: eMBB, uRLLC, and mMTC services; the Legacy service in the embodiment of the present disclosure refers to traditional terminals (also That is, services performed by terminals with ordinary capabilities), including but not limited to: eMBB, uRLLC and mMTC services.

S204: Configure Redcap BWP resources and Legacy BWP resources according to Redcap downlink service conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

It should be noted that the Redcap BWP resources in this disclosed embodiment refer to the BWP resources allocated to Redcap UE; the Legacy BWP resources in this disclosed embodiment refer to the BWP resources allocated to Legacy UE. The Redcap PDSCH in the embodiment of the present disclosure refers to the physical downlink shared channel that transmits Redcap service data; the Legacy PDSCH in the embodiment of the present disclosure refers to the physical downlink shared channel that transmits the Legacy service data.

In some embodiments, the downlink resource multiplexing enhancement method provided in the embodiments of the present disclosure may also include the following steps: configuring the Legacy BWP resources to be occupied by CD-SSB, and the RB or RE of the Legacy BWP resources except the part occupied by CD-SSB. Available for Legacy PDSCH.

It should be noted that, in the embodiment of the present disclosure, NCD-SSB and CD-SSB may occupy the same time slot resources, or may occupy different time slot resources.

It should also be noted here that in the scenario where the Redcap service and the Legacy service coexist, a part of the Legacy BWP resources originally allocated to the terminal needs to be divided as Redcap resources; for the convenience of description, in the embodiment of the present disclosure, the Legacy BWP resources originally allocated to the terminal are The maximum Legacy BWP resources are collectively referred to as "cell bandwidth resources"; the BWP resources divided among the cell bandwidth resources for transmitting Redcap service data are called Redcap BWP resources, and the remaining BWP resources used for transmitting Legacy service data in the cell bandwidth resources are Called the Legacy BWP resource.

In some embodiments, the Redcap BWP resources in the embodiments of the present disclosure may be located in the first bandwidth range or the second bandwidth range within the cell bandwidth resource or the maximum Legacy BWP resource, wherein, when the cell bandwidth resource or the maximum Legacy BWP resource changes from When the upward direction represents the direction from small to large bandwidth values, 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.

It should be noted that in the embodiment of the present disclosure, the cell bandwidth resource refers to the maximum Legacy BWP resource allocated to the terminal. In actual scenarios, the Legacy BWP resource (for example, 90MHz or 85Hz) allocated to the terminal may be less than or equal to the cell bandwidth resource. (100 Hz), taking cell bandwidth resources as an example, the embodiments of the present disclosure will be described with reference to Figures 3 to 8. Assuming that the direction from bottom to top in Figures 3 to 8 is the direction from small to large bandwidth values, then the present disclosure In the embodiment, the first bandwidth range of the cell bandwidth resources is the upper part of the cell bandwidth resources (the maximum bandwidth part), and the second bandwidth range is the lower part of the cell bandwidth resources (the minimum bandwidth part). For example, the Redcap BWP resources shown in Figures 3 to 8 are located in the upper part of the cell bandwidth resources (the maximum bandwidth part).

Optionally, the Redcap BWP resource in the embodiment of the present disclosure may be but is not limited to the following values: 20MHz, 10MHz or 5MHz, etc.

It can be seen from the above that the downlink resource multiplexing enhancement method provided in the embodiment of the present disclosure monitors the Redcap downlink service situation when Redcap and Legacy services coexist, and then performs redcap BWP resources and Legacy BWP resources according to the Redcap downlink service situation. Configuration to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH. Furthermore, according to different Redcap downlink business conditions, configure a variety of different downlink resource multiplexing enhancement schemes to improve the reuse of Redcap PDSCH and Legacy PDSCH under different business conditions, which can not only increase the transmission rate of downlink business data, but also It can improve network resource utilization, improve network performance, and enhance user experience.

Still taking the cell bandwidth resources shown in Figures 3 to 8 as an example, the downlink resource multiplexing enhancement method provided in the embodiment of the present disclosure will be described in detail. As shown in Figures 3 to 8, Redcap BWP resources are placed in the cell bandwidth. The upper part of the resource (the part with the largest bandwidth), and NCD-SSB and CD-SSB occupy the same time slot resource. It should be noted that the downlink resource multiplexing enhancement method provided in the embodiment of the present disclosure is also applicable to the situation where Redcap BWP is placed at the lower end of the cell bandwidth (the largest part of the bandwidth), and when CD-SSB and NCD-SSB are in different time slots . The part shown in icon 11 in Figures 3 to 8 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.

In specific implementation, the configuration schemes for enhancing downlink resource multiplexing in the embodiments of the present disclosure include but are not limited to the following six:

The first solution: When there is no Redcap downlink service, configure the Redcap BWP resource to be occupied only by NCD-SSB, and the resource block RB or resource unit RE in the Redcap BWP resource except the part occupied by NCD-SSB is not available to Legacy PDSCH. Among them, Legacy PDSCH only occupies Legacy BWP resources.

The specific configuration scheme is shown in Figure 3. When there is no Redcap downlink service (that is, there is no Redcap PDSCH), the Redcap BWP is only occupied by NCD-SSB (that is, the part shown in Figure 10), and the other RB/RE It is not available for Legacy PDSCH (that is, the part shown in icon 40). Legacy PDSCH is only in Legacy BWP. Legacy BWP resources are occupied by CD-SSB (that is, the part shown in icon 20), and Legacy BWP resources are except CD-SSB. The RB or RE outside the occupied part (i.e., the part shown in Figure 30) is available to Legacy PDSCH.

Among the above solutions, Redcap PDSCH and Legacy PDSCH have the lowest reuse, the RE resource utilization rate in Redcap BWP is extremely low, and Redcap and Legacy UE have the lowest processing complexity and lowest cost.

The second solution: When there is Redcap downlink service, configure the RB corresponding to NCD-SSB in the Redcap BWP resource. Except for the RE occupied by NCD-SSB, the remaining REs are not available to Redcap PDSCH, and the Redcap BWP resource except NCD -Except for the RB corresponding to SSB, the remaining RBs are available for Redcap PDSCH. Among them, Legacy PDSCH only occupies Legacy BWP resources.

The specific configuration scheme is shown in Figure 4. When there is Redcap downlink service (with Redcap PDSCH), the RB corresponding to NCD-SSB in Redcap BWP except the RE occupied by NCD-SSB (that is, the part shown in Figure 10) The remaining RE (that is, the part shown in icon 50) is not available to Redcap PDSCH. The RB above and below NCD-SSB (that is, the part shown in icon 60) is available to Redcap PDSCH. Legacy PDSCH is only within Legacy BWP. Legacy The BWP resource is occupied by CD-SSB (that is, the part shown in icon 20), and the RB or RE of the Legacy BWP resource except the part occupied by CD-SSB (that is, the part shown in icon 30) is available to Legacy PDSCH.

In the above solution, Redcap PDSCH and Legacy PDSCH have low reuse, low utilization of RE resources in Redcap BWP, low processing complexity and low cost of Redcap and Legacy UE.

The third solution: When there is no Redcap downlink service, configure the Redcap BWP resources to be occupied only by NCD-SSB, and except for the RBs occupied by NCD-SSB, the remaining RBs in the Redcap BWP resources are for Legacy PDSCH. Available, and in the RB corresponding to the NCD-SSB in the Redcap BWP resource, except for the RE occupied by the NCD-SSB, the remaining REs are available to the Legacy PDSCH. Among them, the Legacy PDSCH not only occupies the Legacy BWP resource, but also occupies the internal part of the Redcap BWP resource. RB and RE.

The specific configuration scheme is shown in Figure 5. When there is no Redcap downlink service (no Redcap PDSCH), only the NCD-SSB is occupied in the Redcap BWP (that is, the part shown in Figure 10). The Legacy PDSCH is occupied in the Legacy BWP ( In addition to the part shown in icon 30), the RBs above and below NCD-SSB in Redcap BWP (that is, the part shown in icon 80) are available to Legacy PDSCH, and the RB corresponding to NCD-SSB in Redcap BWP except NCD- The remaining REs other than the REs occupied by the SSB (that is, the part shown in Figure 70) are available to the Legacy PDSCH, and the Legacy PDSCH performs rate matching (RM) on these RE resources. The Legacy BWP resource is occupied by CD-SSB (that is, the part shown in icon 20), and the RB or RE of the Legacy BWP resource except the part occupied by CD-SSB (that is, the part shown in icon 30) is available to Legacy PDSCH.

Among the above solutions, Redcap PDSCH and Legacy PDSCH have the highest reuse, and the RE resource utilization rate within Redcap BWP is the highest. That is, Legacy UE has the highest utilization rate of the entire RE resources 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.

The fourth solution: When there is Redcap downlink service and the traffic volume of the Redcap service is higher than or equal to the first threshold, configure the Redcap BWP resource except the RB corresponding to NCD-SSB. The remaining RBs are available to Redcap PDSCH, and the Redcap BWP In addition to the REs occupied by NCD-SSB in the RB corresponding to NCD-SSB in the resource, the remaining REs are available to Redcap PDSCH. Among them, Legacy PDSCH only occupies Legacy BWP resources. The first threshold corresponds to when Redcap PDSCH occupies full Redcap BWP resources. business volume.

The specific configuration scheme is shown in Figure 6. When there is Redcap downlink service and the business volume is large (there is Redcap PDSCH, which occupies the Redcap BWP), in addition to occupying the NCD-SSB (that is, the part shown in Figure 10), the Redcap BWP has 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, and the RB corresponding to the NCD-SSB in the Redcap BWP has the remaining REs (i.e., the icon) except the REs occupied by NCD-SSB. 90) are available to Redcap PDSCH. Redcap PDSCH performs rate matching on these RE resources. Legacy BWP resources are occupied by CD-SSB (that is, the part shown in Figure 20), and Legacy BWP resources are except for the parts occupied by CD-SSB. The external RB or RE (i.e., the part shown in Figure 30) is available to Legacy PDSCH.

Among the above solutions, Redcap PDSCH and Legacy PDSCH have low reuse, and the utilization rate of RE resources in Redcap BWP is the highest. That is, Redcap UE has the highest utilization rate of the entire RE resources 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.

The fifth solution: When there is a Redcap downlink service and the traffic volume of the Redcap service is higher than the second threshold and less than the first threshold, configure the RB corresponding to the NCD-SSB in the Redcap BWP resource except the RE occupied by the NCD-SSB. The remaining REs are available to Redcap PDSCH, and in the Redcap BWP resources, except for the RBs corresponding to NCD-SSB, some of the remaining RBs close to NCD-SSB are available to Redcap PDSCH and away from Some RBs of NCD-SSB are available to Legacy PDSCH. In addition to occupying Legacy BWP resources, Legacy PDSCH also occupies some RBs within Redcap BWP resources. The first threshold is the corresponding traffic volume when Redcap PDSCH occupies the Redcap BWP resources. The second threshold is the corresponding traffic volume when the Redcap PDSCH occupies the RB corresponding to the NCD-SSB in the Redcap BWP resource.

The specific configuration scheme is shown in Figure 7. When there is Redcap downlink service and the traffic volume is medium (there is Redcap PDSCH and the Redcap BWP is not fully occupied), the RB corresponding to the NCD-SSB in the Redcap BWP except the RE occupied by the NCD-SSB (i.e., the part shown in icon 10) The remaining RE (i.e., the part shown in icon 90) are available to Redcap PDSCH. Redcap PDSCH performs rate matching on these RE resources. In the Redcap BWP, the upper and lower parts of NCD-SSB (RB) Close to NCD-SSB, that is, the part shown in icon 60) is available to Redcap PDSCH, and the remaining part RB above and below NCD-SSB in Redcap BWP (far away from NCD-SSB, that is, the part shown in icon 80) is available to Legacy PDSCH, The Legacy BWP resource is occupied by CD-SSB (that is, the part shown in icon 20), and the RB or RE of the Legacy BWP resource except the part occupied by CD-SSB (that is, the part shown in icon 30) is available to Legacy PDSCH.

Among the above solutions, Redcap PDSCH and Legacy PDSCH have a high degree of reuse, and the RE resource utilization rate in Redcap BWP is the highest. Redcap UE has a medium downlink rate, high processing complexity and high cost; Legacy UE has a high downlink rate and high processing complexity. ,higher cost.

The sixth solution: When there is a Redcap downlink service and the traffic volume of the Redcap service is lower than or equal to the second threshold, configure the remaining REs in the RB corresponding to the NCD-SSB in the Redcap BWP resource except the REs occupied by the NCD-SSB. It is available for Redcap PDSCH, and in addition to the RB corresponding to NCD-SSB in the Redcap BWP resource, the remaining RBs are available to Legacy PDSCH. The second threshold is when Redcap PDSCH fills up the RB corresponding to NCD-SSB in the Redcap BWP resource. Business volume.

The specific configuration scheme is shown in Figure 8. When there is Redcap downlink service and the traffic volume is small (with Redcap PDSCH, it only needs to occupy the remaining RE resources in the RB corresponding to NCD-SSB except the RE occupied by NCD-SSB). Redcap In the RB corresponding to the NCD-SSB in the BWP, except for the RE occupied by the NCD-SSB (the part shown in icon 10), the remaining REs (that is, the part shown in icon 90) are available to Redcap PDSCH. Redcap PDSCH is available for these REs. Resources are rate matched. In the Redcap BWP, the RB above and below NCD-SSB (the part shown in icon 80) is available to Legacy PDSCH. The Legacy BWP resources are occupied by CD-SSB (that is, the part shown in icon 20), and Legacy The RB or RE (that is, the part shown in icon 30) of the BWP resource except the CD-SSB occupied part is available to Legacy PDSCH.

Among the above solutions, Redcap PDSCH and Legacy PDSCH have high reuse, and the RE resource utilization rate in Redcap BWP is the highest. Redcap UE has a low downlink rate, medium processing complexity, and medium cost; Legacy UE has a high downlink rate, high processing complexity, and high cost. .

It should be noted that when performing Legacy PDSCH rate matching, the base station will deliver the Legacy rate matching model (ie, Legacy RM Pattern) to the terminal so that the Legacy PDSCH can rate match the corresponding RE. When performing Redcap PDSCH rate matching, the base station will deliver the Redcap rate matching model to the terminal. (i.e. Redcap RM Pattern), so that Redcap PDSCH can rate match the corresponding RE.

Based on the same inventive concept, embodiments of the present disclosure also provide a downlink resource multiplexing enhancement device, as described in the following embodiments. Since the problem-solving principle of this device embodiment is similar to that of the above-mentioned method embodiment, the implementation of this device embodiment can refer to the implementation of the above-mentioned method embodiment, and repeated details will not be repeated.

Figure 9 shows a schematic diagram of a downlink resource multiplexing enhancement device in an embodiment of the present disclosure. As shown in Figure 9, the device includes: a service monitoring module 91 and a resource configuration module 92.

Among them, the business monitoring module 91 is set to monitor the Redcap downlink business situation when Redcap and Legacy services coexist; the resource configuration module 92 is set to configure the Redcap BWP resources and Legacy BWP resources according to the Redcap downlink business conditions, so as to Enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

It should be noted here that the above-mentioned business monitoring module 91 and resource configuration module 92 correspond to S202 to S204 in the method embodiment. The examples and application scenarios implemented by the above-mentioned modules and corresponding steps are the same, but are not limited to the above-mentioned method embodiment. Content disclosed. It should be noted that the above-mentioned modules, as part of the device, can be executed in a computer system such as a set of computer-executable instructions.

In some embodiments, the above-mentioned resource configuration module 92 may include: a first configuration sub-module 921, which is configured to configure the Redcap BWP resources to be occupied only by NCD-SSB when there is no Redcap downlink service, and the Redcap BWP resources exclude NCD-SSB. Resource blocks RB or resource units RE outside the SSB occupied part are not available to Legacy PDSCH, where Legacy PDSCH only occupies Legacy BWP resources.

In some embodiments, the above-mentioned resource configuration module 92 may also include: a second configuration sub-module 922, configured to configure the RB corresponding to the NCD-SSB in the Redcap BWP resource in addition to the RB occupied by the NCD-SSB when there is a Redcap downlink service. Except RE, the remaining RE are not available to Redcap PDSCH, and in the Redcap BWP resources, except the RB corresponding to NCD-SSB, the remaining RBs are available to Redcap PDSCH. Among them, Legacy PDSCH only occupies Legacy BWP resources.

In some embodiments, the above-mentioned resource configuration module 92 may also include: a third configuration sub-module 923, which is configured to configure the Redcap BWP resource to be occupied only by NCD-SSB when there is no Redcap downlink service, and the Redcap BWP resource excludes NCD -Except the RB occupied by SSB, the remaining RBs are available to Legacy PDSCH, and in the RB corresponding to NCD-SSB in the Redcap BWP resource, except for the REs occupied by NCD-SSB, the remaining REs are available to Legacy PDSCH, among which, except Legacy PDSCH In addition to occupying Legacy BWP resources, it also occupies part of the RB and RE within Redcap BWP resources.

In some embodiments, the above-mentioned resource configuration module 92 may also include: a fourth configuration sub-module 924, configured to configure the Redcap BWP resource internal deletion when there is Redcap downlink service and the traffic volume of the Redcap service is higher than or equal to the first threshold. In addition to the RB corresponding to NCD-SSB, the remaining RBs are available to Redcap PDSCH, and in the RB corresponding to NCD-SSB in the Redcap BWP resource, except the REs occupied by NCD-SSB, the remaining REs are available to Redcap PDSCH, among which, Legacy PDSCH Only Legacy BWP resources are occupied, and the first threshold is the corresponding traffic volume when Redcap PDSCH fully occupies Redcap BWP resources.

In some embodiments, the above-mentioned resource configuration module 92 may also include: a fifth configuration sub-module 925, configured to configure the Redcap BWP when there is Redcap downlink service and the traffic volume of the Redcap service is higher than the second threshold and less than the first threshold. In the RB corresponding to NCD-SSB in the resource, except the RE occupied by NCD-SSB, the remaining REs are available to Redcap PDSCH, and in the Redcap BWP resource, except the RB corresponding to NCD-SSB, the remaining RBs close to NCD-SSB Some RBs are available to Redcap PDSCH, and some RBs far away from NCD-SSB are available to Legacy PDSCH. In addition to occupying Legacy BWP resources, Legacy PDSCH also occupies some RBs within Redcap BWP resources. The first threshold is when Redcap PDSCH occupies Redcap BWP. The second threshold is the traffic volume corresponding to when the Redcap PDSCH occupies the RB corresponding to the NCD-SSB in the Redcap BWP resource.

In some embodiments, the above-mentioned resource configuration module 92 may also include: a sixth configuration sub-module 926, configured to configure the NCD within the Redcap BWP resource when there is Redcap downlink service and the traffic volume of the Redcap service is lower than or equal to the second threshold. -Except the REs occupied by NCD-SSB in the RB corresponding to SSB, the remaining REs are available to Redcap PDSCH, and in the Redcap BWP resources, except the RBs corresponding to NCD-SSB, the remaining RBs are available to Legacy PDSCH. Among them, the second The threshold is the corresponding traffic volume when Redcap PDSCH occupies the RB corresponding to NCD-SSB in Redcap BWP resources.

In some embodiments, the Redcap BWP resource in the embodiment of the present disclosure is located in the first bandwidth range or the second bandwidth range within the cell bandwidth resource or the maximum Legacy BWP resource, where when the cell bandwidth resource or the maximum Legacy BWP resource goes from bottom to top When the direction up represents the direction from small to large bandwidth values, 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.

In some embodiments, the above-mentioned resource configuration module 92 is also configured to configure the Legacy BWP resources to be occupied by CD-SSB, and the RBs or REs of the Legacy BWP resources except the CD-SSB occupied part are available to Legacy PDSCH.

In the embodiment of the present disclosure, the above-mentioned first configuration sub-module 921, second configuration sub-module 922, third configuration sub-module 923, fourth configuration sub-module 924, fifth configuration sub-module 925 and sixth configuration sub-module 926 and The examples and application scenarios implemented by the corresponding steps are the same, but are not limited to the contents disclosed in the above method embodiments. It should be noted that the above-mentioned modules, as part of the device, can be executed in a computer system such as a set of computer-executable instructions.

Through the downlink resource multiplexing enhancement method and device provided in the embodiments of the present disclosure, the following technical effects can be achieved but are not limited to: ① According to different business conditions in the coexistence scenario of RedCap and Legacy services (or UE), Redcap UE is taken into consideration Dealing with complexity and design costs with Legacy UE, choosing different downlink resource reuse enhancement solutions can maximize the reuse capabilities of Redcap PDSCH and Legacy PDSCH, improve network resource utilization, and improve network performance; ② Improve different business conditions Next Redcap PDSCH and Legacy PDSCH reuse, reuse flexibility and diversity; ③ Improved RE resource utilization within Redcap BWP, ④ Improved downlink rate and system throughput of Redcap UE and Legacy UE; ⑤ Suitable for both FR1 and FR2, both It is suitable for Legacy (eMBB, uRLLC and mMTC) services and Redcap (eMBB, uRLLC and mMTC) services, and is universal and practical; ⑥ Improves the completeness, diversity, regularity and compatibility of the protocol, and improves The user experience of 5G and post-5G communication systems has broad application prospects.

Those skilled in the art will understand that various aspects of the present disclosure may be implemented as systems, methods, or program products. Therefore, various aspects of the present disclosure may be embodied in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which may be collectively referred to herein as "Circuits", "modules" or "systems".

An electronic device 1000 according to this embodiment of the present disclosure is described below with reference to FIG. 10 . The electronic device 1000 shown in FIG. 10 is only an example and should not bring any limitations to the functions and usage scope of the embodiments of the present disclosure.

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

Wherein, the storage unit stores program code, and the program code can be executed by the processing unit 1010, so that the processing unit 1010 performs various exemplary methods according to the present disclosure described in the "Example Method" section of this specification. Implementation steps. For example, the processing unit 1010 can perform the following steps of the above method embodiment: when Redcap and Legacy services coexist, monitor the Redcap downlink service situation; configure the Redcap BWP resources and Legacy BWP resources according to the Redcap downlink service situation, To enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.

The storage unit 1020 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 10201 and/or a cache storage unit 10202, and may further include a read-only storage unit (ROM) 10203.

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

Bus 1030 may be a local area representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or using any of a variety of bus structures. bus.

Electronic device 1000 may also communicate with one or more external devices 1040 (e.g., keyboard, pointing device, Bluetooth device, etc.), may also communicate with one or more devices that enable a user to interact with electronic device 1000, and/or with Any device that enables the electronic device 1000 to communicate with one or more other computing devices (eg, router, modem, etc.). This communication can occur through the input/output (I/O) interface 1050 OK. Furthermore, the electronic device 1000 may also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the 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 may 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 system, etc.

Through the above description of the embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software, or can be implemented by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a terminal device, a network device, etc.) to execute a method according to an embodiment of the present disclosure.

In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as a computer program product or computer program including computer instructions stored in a computer-readable storage medium middle. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs any of the above methods for issuing inactive security configuration information.

In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, and the computer-readable storage medium may be a readable signal medium or a readable storage medium. Figure 11 shows a schematic diagram of a computer-readable storage medium in an embodiment of the disclosure. As shown in Figure 11, the computer-readable storage medium 1100 stores a program product capable of implementing the above method of the disclosure. In some possible implementations, various aspects of the present disclosure can also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to cause the The terminal device performs the steps according to various exemplary embodiments of the present disclosure described in the above "Example Method" section of this specification.

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 drives, 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 device, magnetic storage device, or any suitable combination of the above.

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 therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium that can send, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device.

Alternatively, program code embodied on a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

When implemented, program code for performing operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and Includes conventional procedural programming languages—such as "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In situations involving remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device, such as provided by an Internet service. (business comes via Internet connection).

It should be noted that although several modules or units of equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into being embodied by multiple modules or units.

Furthermore, although various steps of the methods of the present disclosure are depicted in the drawings in a specific order, this does not require or imply that the steps must be performed in that specific order, or that all of the illustrated steps must be performed to achieve the desired results. result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, etc.

Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software, or can be implemented by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , including several instructions to cause a computing device (which may be a personal computer, a server, a mobile terminal, a network device, etc.) to execute a method according to an embodiment of the present disclosure.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the disclosure that follow the general principles of the disclosure and include common common sense or customary technical means in the technical field that are not disclosed in the disclosure. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

A method for enhancing downlink resource reuse, including:

When Redcap and Legacy services coexist, monitor Redcap downstream services;

According to the Redcap downlink business conditions, Redcap BWP resources and Legacy BWP resources are configured to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.
The downlink resource reuse enhancement method according to claim 1, wherein the Redcap BWP resources and Legacy BWP resources are configured according to the Redcap downlink business situation to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including:

When there is no Redcap downlink service, configure the Redcap BWP resource to be occupied only by NCD-SSB, and the resource block RB or resource unit RE in the Redcap BWP resource except the part occupied by NCD-SSB is not available to Legacy PDSCH. Among them, Legacy PDSCH only Occupies Legacy BWP resources.
The downlink resource reuse enhancement method according to claim 1, wherein the Redcap BWP resources and Legacy BWP resources are configured according to the Redcap downlink business situation to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including:

When Redcap downlink services exist, configure the RBs corresponding to NCD-SSB in the Redcap BWP resources except the REs occupied by NCD-SSB. The remaining REs are not available to Redcap PDSCH, and the RBs corresponding to NCD-SSB in the Redcap BWP resources are excepted. In addition, the remaining RBs are available to Redcap PDSCH, among which Legacy PDSCH only occupies Legacy BWP resources.
The downlink resource reuse enhancement method according to claim 1, wherein the Redcap BWP resources and Legacy BWP resources are configured according to the Redcap downlink business situation to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including:

When there is no Redcap downlink service, configure the Redcap BWP resource to be occupied only by NCD-SSB, and except for the RB occupied by NCD-SSB in the Redcap BWP resource, the remaining RBs are available to Legacy PDSCH, and the NCD-SSB in the Redcap BWP resource is In addition to the REs occupied by NCD-SSB in the corresponding RB, the remaining REs are available to Legacy PDSCH. In addition to occupying Legacy BWP resources, Legacy PDSCH also occupies part of the RBs and REs within the Redcap BWP resources.
The downlink resource reuse enhancement method according to claim 1, wherein the Redcap BWP resources and Legacy BWP resources are configured according to the Redcap downlink business situation to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including:

When there is a Redcap downlink service and the traffic volume of the Redcap service is higher than or equal to the first threshold, in addition to the RB corresponding to NCD-SSB in the Redcap BWP resource, the remaining RBs are configured to be available to Redcap PDSCH, and the NCD-SSB in the Redcap BWP resource is configured In addition to the REs occupied by NCD-SSB in the corresponding RB, the remaining REs are available to Redcap PDSCH. Among them, Legacy PDSCH only occupies Legacy BWP resources. The first threshold is Redcap PDSCH. The corresponding business volume when Redcap BWP resources are fully occupied.
The downlink resource reuse enhancement method according to claim 1, wherein the Redcap BWP resources and Legacy BWP resources are configured according to the Redcap downlink business situation to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including:

When there is a Redcap downlink service and the traffic volume of the Redcap service is higher than the second threshold and less than the first threshold, configure the RB corresponding to the NCD-SSB in the Redcap BWP resource. In addition to the REs occupied by the NCD-SSB, the remaining REs are to the Redcap PDSCH is available, and in the Redcap BWP resources, except for the RB corresponding to NCD-SSB, some of the remaining RBs close to NCD-SSB are available to Redcap PDSCH, and some RBs far away from NCD-SSB are available to Legacy PDSCH. Among them, Legacy PDSCH In addition to occupying the Legacy BWP resources, it also occupies part of the RB within the Redcap BWP resources. The first threshold is the corresponding traffic volume when the Redcap PDSCH occupies the Redcap BWP resources. The second threshold is when the Redcap PDSCH occupies the NCD within the Redcap BWP resources. -The traffic volume corresponding to the RB corresponding to the SSB.
The downlink resource multiplexing enhancement method according to claim 6, wherein the Redcap BWP resources and Legacy BWP resources are configured according to the Redcap downlink business situation to enhance the multiplexing of downlink resources by Redcap PDSCH and Legacy PDSCH, including:

When there is a Redcap downlink service and the traffic volume of the Redcap service is lower than or equal to the second threshold, configure the RB corresponding to the NCD-SSB in the Redcap BWP resource. In addition to the REs occupied by the NCD-SSB, the remaining REs are available to the Redcap PDSCH. And in addition to the RB corresponding to NCD-SSB in the Redcap BWP resource, the remaining RBs are available to Legacy PDSCH, where the second threshold is the corresponding traffic volume when Redcap PDSCH occupies the RB corresponding to NCD-SSB in the Redcap BWP resource.
The downlink resource multiplexing enhancement method according to any one of claims 1 to 7, wherein the Redcap BWP resource is located in the first bandwidth range or the second bandwidth range within the cell bandwidth resource or the maximum Legacy BWP resource, wherein when the cell When the bandwidth resources or the maximum Legacy BWP resources are represented from the bottom to the upward direction of the bandwidth value from small to large, the first bandwidth range is the upper end part of the cell bandwidth resources or the maximum Legacy BWP resources, and the second bandwidth range is the cell Bandwidth resource or the lower part of the largest Legacy BWP resource.
The downlink resource multiplexing enhancement method according to any one of claims 1 to 7, wherein the method further includes:

Configure the Legacy BWP resources to be occupied by CD-SSB, and the RB or RE of the Legacy BWP resources except the part occupied by CD-SSB are available to Legacy PDSCH.
The downlink resource multiplexing enhancement method according to claim 9, wherein NCD-SSB and CD-SSB occupy the same time slot resources.
The downlink resource multiplexing enhancement method according to claim 9, wherein NCD-SSB and CD-SSB occupy different time slot resources.
A downlink resource multiplexing enhancement device, including:

The business monitoring module is set to monitor industries under Redcap when Redcap and Legacy businesses coexist. business situation;

The resource configuration module is set to configure Redcap BWP resources and Legacy BWP resources according to Redcap downlink business conditions to enhance the reuse of downlink resources by Redcap PDSCH and Legacy PDSCH.
A communication system, including: Redcap terminal, Legacy terminal, network side equipment and network management system;

Wherein, the service data of the Redcap service is transmitted between the Redcap terminal and the network side device; the service data of the Legacy service is transmitted between the Legacy terminal and the network side device;

The network management system is used to monitor Redcap downlink business conditions when Redcap and Legacy services coexist, and configure Redcap BWP resources and Legacy BWP resources according to Redcap downlink business conditions to enhance the use of Redcap PDSCH and Legacy PDSCH for downlink resources. of reuse.
An electronic device including:

processor; and

memory for storing executable instructions for the processor;

Wherein, the processor is configured to execute the downlink resource multiplexing enhancement method according to any one of claims 1 to 11 by executing the executable instructions.
A computer-readable storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, the downlink resource multiplexing enhancement method described in any one of claims 1 to 11 is implemented.
A computer program product includes a computer program, wherein when the computer program is executed by a processor, the downlink resource multiplexing enhancement method described in any one of claims 1-11 is implemented.