Resource configuration method and device, communication equipment and storage medium

By sending the downlink control channel common configuration information of the bandwidth part BWP to the RedCap terminal, configuring the public control resources and search space, the RedCap terminal resource configuration problem is solved, and efficient utilization and coverage enhancement is achieved.

CN118944846APending Publication Date: 2024-11-12BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411155318.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-14
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

After introducing the capacity reduction terminal (RedCap), how to efficiently utilize the bandwidth part (BWP) resources to meet their low cost, low complexity and power saving requirements while ensuring enhanced coverage, it is difficult for the existing technology to effectively configure resources to meet these needs .

Method used

The access network device sends downlink control channel common configuration information for the initial bandwidth part BWP to the RedCap terminal, configures additional common control resource sets (CORESET) and public search space, and instructs the terminal to perform predetermined operations, such as random access response, search Call monitoring and system message monitoring ensure efficient and reliable utilization of resources.

Benefits of technology

It realizes the efficient utilization of RedCap terminals in BWP resource configuration, meets its requirements of low cost, low complexity and power saving, and improves coverage capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118944846A_ABST
    Figure CN118944846A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a resource configuration method, which is executed by access network equipment and comprises the following steps of: sending downlink control channel public configuration information for initial bandwidth part (BWP) configuration to a first type terminal; wherein the downlink control channel public configuration information is used for indicating the first type terminal to execute a predetermined resource of a predetermined operation; the predetermined resource comprises at least one of the following: an additional common control resource set CORESET; additional public search space; a common control resource set (CORESET0); and a common search space 0.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application with the application date of April 14, 2022, application number 202280001222.8, and invention name “Resource allocation method, device, communication equipment and storage medium”. Technical Field

[0002] The present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and in particular to a resource configuration method, apparatus, communication equipment and storage medium. Background Art

[0003] In the process of continuous network evolution, a new type of terminal, namely Reduced Capability (Redcap) terminal, has been introduced. This type of terminal is different from ordinary terminals, for example, different from enhanced Mobile Broadband (eMBB) terminals. This type of terminal usually needs to meet the following requirements: 1. Low cost and low complexity; 2. A certain degree of coverage enhancement; 3. Power saving.

[0004] In the related art, a bandwidth part (BWP) is defined. With the introduction of RedCap terminals, how to use BWP is an issue that needs to be considered for RedCap terminals. Summary of the invention

[0005] The embodiments of the present disclosure disclose a method, an apparatus, a communication device and a storage medium for resource configuration.

[0006] According to a first aspect of an embodiment of the present disclosure, a method for resource configuration is provided, wherein the method is performed by an access network device, and the method includes:

[0007] Sending downlink control channel common configuration information for the initial bandwidth part BWP configuration to the first type terminal;

[0008] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0009] Additional common control resource set CORESET;

[0010] Additional public search spaces;

[0011] Common control resource set CORESET0;

[0012] and the public search space 0.

[0013] In one embodiment, the predetermined operation includes at least one of the following:

[0014] Random access response RAR monitoring operation;

[0015] Paging monitoring operation;

[0016] And the operation of system message monitoring.

[0017] In one embodiment, the identifier of the additional public CORESET is different from or the same as the identifier of the public CORESET configured for the second type of terminal; and / or, the identifier of the additional public search space is different from or the same as the identifier of the public search space configured for the second type of terminal.

[0018] In one embodiment, in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional common CORESET is not included in the bandwidth range of CORESET0.

[0019] In one embodiment, at least one of the following is included:

[0020] The additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation;

[0021] The additional common search space is configured as a common search space used for the first type of terminal to perform the predetermined operation;

[0022] The CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation;

[0023] And, the common search space 0 is configured as a common search space used for the first type terminal to perform the predetermined operation.

[0024] In one embodiment, the reserved resources also include resources configured for the second type of terminal in a reserved message; the reserved message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform the reserved operation.

[0025] In one embodiment, at least one of the following is included:

[0026] The CORESET associated with the search space for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for paging monitoring configured for the first type of terminal;

[0027] The CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring by the first type of terminal;

[0028] The search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal;

[0029] And, the search space for system message monitoring configured for the second type of terminals is configured as the search space for system message monitoring used by the first type of terminals.

[0030] In one embodiment, it includes at least one of the following: the additional common CORESET is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring;

[0031] The common control resource set CORESET0 is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring;

[0032] The additional common search space is configured as a search space used by the first type of terminals for RAR monitoring;

[0033] And, the common search space 0 is configured as the search space used by the first type of terminals for RAR monitoring.

[0034] According to a second aspect of an embodiment of the present disclosure, a method for resource configuration is provided, wherein the method is performed by a first type terminal, and the method includes:

[0035] Receiving downlink control channel common configuration information for initial bandwidth part BWP configuration sent by the access network device to the first type of terminal;

[0036] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0037] Additional common control resource set CORESET;

[0038] Additional public search spaces;

[0039] Common control resource set CORESET0;

[0040] and the public search space 0.

[0041] In one embodiment, the predetermined operation includes at least one of the following:

[0042] Random access response RAR monitoring operation;

[0043] Paging monitoring operation;

[0044] And the operation of system message monitoring.

[0045] In one embodiment, the identifier of the additional public CORESET is different from or the same as the identifier of the public CORESET configured for the second type of terminal; and / or, the identifier of the additional public search space is different from or the same as the identifier of the public search space configured for the second type of terminal.

[0046] In one embodiment, in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional common CORESET is not included in the bandwidth range of CORESET0.

[0047] In one embodiment, at least one of the following is included:

[0048] The additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation;

[0049] The additional common search space is configured as a common search space used for the first type of terminal to perform the predetermined operation;

[0050] The CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation;

[0051] And, the common search space 0 is configured as a common search space used for the first type terminal to perform the predetermined operation.

[0052] In one embodiment, the reserved resources also include resources configured for the second type of terminal in a reserved message; the reserved message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform the reserved operation.

[0053] In one embodiment, at least one of the following is included:

[0054] The CORESET associated with the search space for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for paging monitoring configured for the first type of terminal;

[0055] The CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring by the first type of terminal;

[0056] The search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal;

[0057] And, the search space for system message monitoring configured for the second type of terminals is configured as the search space for system message monitoring used by the first type of terminals.

[0058] In one embodiment, it includes at least one of the following: the additional common CORESET is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring;

[0059] The common control resource set CORESET0 is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring;

[0060] The additional common search space is configured as a search space used by the first type of terminals for RAR monitoring;

[0061] And, the common search space 0 is configured as the search space used by the first type of terminals for RAR monitoring.

[0062] According to a third aspect of an embodiment of the present disclosure, a device for resource configuration is provided, wherein the device includes:

[0063] A sending module, configured to send downlink control channel common configuration information configured for an initial bandwidth part BWP to a first type of terminal;

[0064] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0065] Additional common control resource set CORESET;

[0066] Additional public search spaces;

[0067] Common control resource set CORESET0;

[0068] and the public search space 0.

[0069] According to a fourth aspect of an embodiment of the present disclosure, a device for resource configuration is provided, wherein the device includes:

[0070] A receiving module, configured to receive downlink control channel common configuration information for an initial bandwidth part BWP configuration sent by an access network device to a first type of terminal;

[0071] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0072] Additional common control resource set CORESET;

[0073] Additional public search spaces;

[0074] Common control resource set CORESET0;

[0075] and the public search space 0.

[0076] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided, the communication device including:

[0077] processor;

[0078] a memory for storing instructions executable by the processor;

[0079] The processor is configured to implement the method described in any embodiment of the present disclosure when running the executable instructions.

[0080] According to a sixth aspect of an embodiment of the present disclosure, a computer storage medium is provided, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method described in any embodiment of the present disclosure is implemented.

[0081] In an embodiment of the present disclosure, downlink control channel common configuration information for initial bandwidth part BWP configuration is sent to a first type of terminal; wherein the downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. In this way, after receiving the downlink control channel common configuration information for initial bandwidth part BWP configuration sent by the access network device, the first type of terminal can perform a predetermined operation based on the predetermined resource indicated by the downlink control channel common configuration information, so that the first type of terminal can efficiently and reliably utilize the resources of BWP compared to the method of not configuring the downlink control channel common configuration information for the initial BWP. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] Figure 1The diagram is a schematic structural diagram of a wireless communication system according to an exemplary embodiment.

[0083] Figure 2 The diagram is a flow chart of a resource configuration method according to an exemplary embodiment.

[0084] Figure 3 The diagram is a flow chart of a resource configuration method according to an exemplary embodiment.

[0085] Figure 4 The diagram is a flow chart of a resource configuration method according to an exemplary embodiment.

[0086] Figure 5 The diagram is a flow chart of a resource configuration method according to an exemplary embodiment.

[0087] Figure 6 The diagram is a flow chart of a resource configuration method according to an exemplary embodiment.

[0088] Figure 7 The diagram is a flow chart of a resource configuration method according to an exemplary embodiment.

[0089] Figure 8 The diagram is a schematic structural diagram of a device for resource configuration according to an exemplary embodiment.

[0090] Fig. 9 The diagram is a schematic structural diagram of a device for resource configuration according to an exemplary embodiment.

[0091] Fig.10 The diagram is a schematic diagram of the structure of a terminal according to an exemplary embodiment.

[0092] Fig.11 It is a block diagram of a base station according to an exemplary embodiment. DETAILED DESCRIPTION

[0093] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present disclosure as detailed in the appended claims.

[0094] The terms used in the disclosed embodiments are only for the purpose of describing specific embodiments and are not intended to limit the disclosed embodiments. The singular forms of "a", "an" and "the" used in the disclosed embodiments and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

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

[0096] For the purpose of brevity and ease of understanding, the terms "greater than" or "less than" are used herein to characterize size relationships. However, those skilled in the art can understand that the term "greater than" also covers the meaning of "greater than or equal to", and "less than" also covers the meaning of "less than or equal to".

[0097] Please refer to Figure 1 , which shows a schematic diagram of the structure of a wireless communication system provided by an embodiment of the present disclosure. Figure 1 As shown, the wireless communication system is a communication system based on mobile communication technology, and the wireless communication system may include: a plurality of user equipments 110 and a plurality of base stations 120 .

[0098] Among them, the user equipment 110 can be a device that provides voice and / or data connectivity to the user. The user equipment 110 can communicate with one or more core networks via a radio access network (RAN). The user equipment 110 can be an Internet of Things user equipment, such as a sensor device, a mobile phone, and a computer with an Internet of Things user equipment. For example, it can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device. For example, a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote user device, an access terminal, a user terminal, a user agent, a user device, or a user equipment. Alternatively, the user equipment 110 can also be a device of an unmanned aerial vehicle. Alternatively, the user equipment 110 can also be a vehicle-mounted device, for example, it can be a driving computer with wireless communication function, or a wireless user device connected to an external driving computer. Alternatively, the user equipment 110 may also be a roadside device, for example, a street lamp, a signal lamp or other roadside device with a wireless communication function.

[0099] The base station 120 may be a network-side device in a wireless communication system. The wireless communication system may be a fourth generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or, the wireless communication system may be a 5G system, also known as a new air interface system or a 5G NR system. Alternatively, the wireless communication system may be a next generation system of the 5G system. The access network in the 5G system may be referred to as NG-RAN (New Generation-Radio Access Network).

[0100] Among them, the base station 120 can be an evolved base station (eNB) adopted in the 4G system. Alternatively, the base station 120 can also be a base station (gNB) adopting a centralized distributed architecture in the 5G system. When the base station 120 adopts a centralized distributed architecture, it usually includes a centralized unit (CU) and at least two distributed units (DU). The centralized unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link layer control protocol (RLC) layer, and a media access control (MAC) layer; the distributed unit is provided with a physical (Physical, PHY) layer protocol stack. The specific implementation method of the base station 120 is not limited in the embodiment of the present disclosure.

[0101] A wireless connection may be established between the base station 120 and the user equipment 110 via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.

[0102] In some embodiments, an E2E (End to End) connection may also be established between the user devices 110, such as V2V (vehicle to vehicle) communication, V2I (vehicle to Infrastructure) communication, and V2P (vehicle to pedestrian) communication in vehicle to everything (V2X) communication.

[0103] Here, the above-mentioned user equipment can be considered as the terminal equipment of the following embodiments.

[0104] In some embodiments, the wireless communication system may further include a network management device 130 .

[0105] Several base stations 120 are respectively connected to a network management device 130. The network management device 130 may be a core network device in a wireless communication system. For example, the network management device 130 may be a mobility management entity (MME) in an evolved packet core (EPC). Alternatively, the network management device may be other core network devices, such as a serving gateway (SGW), a public data network gateway (PGW), a policy and charging rules function (PCRF), or a home subscriber server (HSS). The embodiments of the present disclosure do not limit the implementation form of the network management device 130.

[0106] In order to facilitate the understanding of those skilled in the art, the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art can understand that the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.

[0107] In order to better understand the technical solutions described in any embodiment of the present disclosure, first, the application scenarios in the related technologies are described:

[0108] In the fourth generation mobile communication technology 4G system, in order to support the Internet of Things business, two major technologies, Machine Type Communication (MTC) and Narrow Band Internet of Things (NB-IoT), were proposed.

[0109] These two technologies are mainly aimed at scenarios such as low rates and high latency. For example, scenarios such as meter reading and environmental monitoring. In one embodiment, NB-IoT can only support a maximum rate of several hundred k, and MTC can only support a maximum rate of several M. However, with the continuous development of IoT services, such as the popularization of services such as video surveillance, smart homes, wearable devices, and industrial sensor monitoring, these services usually require rates of tens to 100M, and also have relatively high requirements for latency. Therefore, MTC and NB-IoT technologies in the fourth generation of mobile communication technology are difficult to meet the requirements. Based on this situation, it is proposed to design a new terminal type in the fifth generation of mobile communication technology 5G new air interface to cover the requirements of this mid-range IoT device.

[0110] In one embodiment, this new terminal type is called Reduced Capability UE (RedCap) or NR-lite for short. Here, RedCap based on 5G NR-lite usually needs to meet the following requirements: low cost, low complexity; a certain degree of coverage enhancement; power saving.

[0111] Since the 5G new air interface is designed for high-end terminals such as high speed and low latency, the relevant design cannot meet the above requirements of NR-lite. The new air interface (NR, New Radio) system needs to be modified to meet the requirements of NR-lite. In one embodiment, in order to meet the requirements of low cost, low complexity, etc., the RF bandwidth of NR-IoT can be limited, for example, the RF bandwidth is limited to 20MHz. In one embodiment, the size of the NR-lite buffer can be limited, thereby limiting the size of each received transmission block, etc. In one embodiment, for power saving, possible optimization directions are to simplify the communication process, reduce the number of times NR-lite users detect downlink control channels, etc.

[0112] In one embodiment, the information element (IE) field PDCCH-ConfigCommon is used to configure cell-specific physical downlink control channel (PDCCH) parameters provided in a system information block (SIB) and dedicated signaling.

[0113] In one embodiment, commonControlResourceSet is an additional common control resource set that can be configured and used for any common or terminal-specific search space. If the network configures this field, it uses a non-zero ControlResourceSetId for this ControlResourceSet. The network configures commonControlResourceSet in SIB1 to be included in the bandwidth of control resource set CORESET#0.

[0114] In one embodiment, the parameters of the common CORESET#0 can be used for any common or terminal-specific search space.

[0115] After the introduction of Redcap terminals, an initial BWP for downlink random access response (RAR) can be configured in SIB1 for Redcap terminals. The initial BWP can also be the initial BWP used for paging. How to configure the common search space on the initial BWP has not yet been defined.

[0116] like Figure 2 As shown, this embodiment provides a method for resource configuration, wherein the method is performed by an access network device, and the method includes:

[0117] Step 21: Sending physical downlink control channel PDCCH common configuration information configured for the initial bandwidth part BWP to the first type of terminal;

[0118] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0119] Additional common control resource set CORESET;

[0120] Additional public search spaces;

[0121] Common control resource set CORESET0;

[0122] and the public search space 0.

[0123] Here, the first type terminal and the second type terminal involved in the present disclosure may be, but are not limited to, a mobile phone, a wearable device, a vehicle-mounted terminal, a road side unit (RSU), a smart home terminal, an industrial sensor device and / or a medical device, etc. The first type terminal and the second type terminal are different types of terminals. In one embodiment, the first type terminal may be a Redcap terminal, and the second type terminal may be a non-Redcap terminal other than a Redcap terminal.

[0124] The access network device involved in the present disclosure may be a base station. Here, the base station may be various types of base stations, for example, a base station of a fifth generation mobile communication (5G) network or other evolved base stations.

[0125] In one embodiment, a downlink initial BWP is configured for a first type of terminal; PDCCH common configuration information for the initial BWP configuration is sent to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate a reserved resource for the first type of terminal to perform a reserved operation; the reserved resources include at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0.

[0126] It should be noted that the PDCCH common configuration information may be carried in the PDCCH common configuration (PDCCH-configCommon) field of the RedCap-specific initial DL BWP configuration or the PDCCH common system information block configuration (PDCCH-configCommonSIB) field.

[0127] It should be noted that the frequency domain resource information of PDCCH and the number of orthogonal frequency division multiplexing (OFDM) symbols occupied in the time domain are encapsulated in CORESET; the information such as the starting OFDM symbol of PDCCH, the monitoring period, and the associated CORESET are encapsulated in the search space. Here, the public search space is mainly used during access and cell switching, for example, for monitoring control information related to the broadcast control channel BCCH, paging, RAR, etc. Among them, RAR and other related messages are messages for random access responses, including msg2, msg4, msgB, etc.

[0128] In one embodiment, physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration is sent to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the first type of terminal to perform a predetermined resource for a predetermined operation; the predetermined resource includes at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. wherein the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.

[0129] In one embodiment, the identifier of the additional public CORESET is different from the identifier of the public CORESET configured for the second type of terminal. It should be noted that the identifier of the additional public CORESET may not be 0.

[0130] In one embodiment, the identifier of the additional common search space is different from the identifier of the common search space configured for the second type of terminal. It should be noted that the identifier of the additional common search space may not be zero.

[0131] In one embodiment, the identifier of the additional public CORESET is the same as the identifier of the public CORESET configured for the second type of terminal. It should be noted that the identifier of the additional public CORESET may not be 0.

[0132] In one embodiment, the identifier of the additional common search space is the same as the identifier of the common search space configured for the second type of terminal. It should be noted that the identifier of the additional common search space may not be zero.

[0133] In one embodiment, if the initial BWP bandwidth does not include the bandwidth of CORSET0, an additional public CORESET or an additional public search space may be configured; wherein the bandwidth of the additional public CORESET does not need to be included in the bandwidth range of CORESET0.

[0134] In one embodiment, the CORESET associated with all or part of the common search space for the first type of terminal may be configured based on the additional common CORESET. Alternatively, the CORESET associated with all or part of the common search space for the first type of terminal may be configured based on the additional common search space.

[0135] It should be noted that the CORESET associated with all search spaces here can be understood as the CORESET associated with the search space required for the terminal to perform all scheduled operations, and all scheduled operations may include: random access response RAR monitoring operations, paging monitoring operations, and system message monitoring operations, etc., but are not limited to the above operations. The CORESET associated with a partial search space can be understood as the CORESET associated with the search space required to perform some scheduled operations, and some scheduled operations are part of all scheduled operations. Similarly, the entire search space here can be understood as the search space required for the terminal to perform all scheduled operations, and all scheduled operations may include: random access response RAR monitoring operations, paging monitoring operations, and system message monitoring operations, etc., but are not limited to the above operations. The partial search space can be understood as the search space required to perform some scheduled operations, and some scheduled operations are part of all scheduled operations.

[0136] In one embodiment, the additional common CORESET is configured as a common search space associated CORESET for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response RAR monitoring operation; paging monitoring operation; and system message monitoring operation.

[0137] In one embodiment, the additional common search space is configured as a common search space for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response (RAR) monitoring operation; paging monitoring operation; and system message monitoring operation.

[0138] In one embodiment, physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration is sent to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the first type of terminal to perform a predetermined resource for a predetermined operation; the predetermined resource includes at least one of the following: an additional common control resource set CORESET; and, an additional common search space. The additional common CORESET is configured as a CORESET associated with the common search space for the first type of terminal to perform all predetermined operations; and / or, the additional common search space is configured as a common search space for the first type of terminal to perform all predetermined operations.

[0139] In one embodiment, the common control resource set CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response RAR monitoring operation; paging monitoring operation; and system message monitoring operation.

[0140] In one embodiment, the common control resource set CORESET0 may be used by a search space configured on an initial BWP configured for a first type of terminal and an initial BWP configured for a second type of terminal.

[0141] In one embodiment, the common control resource set CORESET0 can be used by the search space configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal. The bandwidth range of the initial BWP configured for the first type of terminal does not include the bandwidth of the common control resource set CORESET0.

[0142] In one embodiment, the common search space 0 is configured as a common search space for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response (RAR) monitoring operation; paging monitoring operation; and system message monitoring operation.

[0143] In one embodiment, physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration is sent to the first type terminal; wherein the downlink control channel common configuration information is used to indicate the predetermined resources for the first type terminal to perform a predetermined operation; the predetermined resources include at least one of the following: a common control resource set CORESET0; and a common search space 0. The common CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform all the predetermined operations; and / or the common search space 0 is configured as a common search space for the first type terminal to perform all the predetermined operations.

[0144] In one embodiment, the common search space 0 may be used by a search space configured on an initial BWP configured for a first type of terminal and an initial BWP configured for a second type of terminal.

[0145] In one embodiment, the common search space 0 can be used by the search space configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal. The bandwidth range of the initial BWP configured for the first type of terminal does not include the bandwidth of the common control resource set CORESET0.

[0146] In one embodiment, the additional public CORESET is configured as a CORESET associated with a public search space for the first type of terminal to perform the predetermined operation; and / or, the additional public search space is configured as a public search space for the first type of terminal to perform the predetermined operation; and / or, the CORESET0 is configured as a CORESET associated with a public search space for the first type of terminal to perform the predetermined operation; and / or, the public search space 0 is configured as a public search space for the first type of terminal to perform the predetermined operation.

[0147] In one embodiment, the additional public CORESET is configured as a CORESET associated with a public search space for the first type of terminal to perform some predetermined operations; and / or, the additional public search space is configured as a public search space for the first type of terminal to perform some predetermined operations; and / or, CORESET0 is configured as a CORESET associated with a public search space for the first type of terminal to perform some predetermined operations; and / or, public search space 0 is configured as a public search space for the first type of terminal to perform some predetermined operations. The predetermined operation includes at least one of the following: random access response RAR monitoring operation; paging monitoring operation; and system message monitoring operation.

[0148] In one embodiment, physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration is sent to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the predetermined resources for the first type of terminal to perform a predetermined operation; the predetermined resources include at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. The additional common CORESET is configured as a CORESET associated with the common search space for the first type of terminal to perform part of the predetermined operation; and / or, the additional common search space is configured as a common search space for the first type of terminal to perform part of the predetermined operation; and / or, CORESET0 is configured as a CORESET associated with the common search space for the first type of terminal to perform part of the predetermined operation; and / or, the common search space 0 is configured as a common search space for the first type of terminal to perform part of the predetermined operation.

[0149] It should be noted that CORESET0 and search space 0 can be configured in the master information block (MIB), and other CORESETs and / or search spaces with non-zero identifiers need to be configured in SIB1. For example, CORESET1 and / or search space 1 are configured in SIB1.

[0150] In one embodiment, the reserved resources also include resources configured for the second type of terminal in the reserved message; the reserved message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform a predetermined operation.

[0151] In one embodiment, CORESET0 and / or search space 0 are configured for the second type of terminal in MIB; additional CORESET x and / or additional search space CORESET x are configured for the second type of terminal in SIB1, where x is not 0, but may be 1, 2, etc.

[0152] In one embodiment, CORESET0 and / or search space 0 are configured for the second type of terminal in MIB for monitoring of SIB1; CORESET x and / or search space CORESET x are configured for the second type of terminal in SIB1, where x is not 0, but can be 1, 2, etc. Among them, monitoring of Other SI, or monitoring of paging; or monitoring of RAR can be associated with CORESET0 and / or search space 0, or CORESET x and / or search space CORESET x configured for the second type of terminal in MIB; that is, the configuration of COREST and search space can be associated with the configuration of CORESET0 and / or search space 0 or additional CORESET and / or additional search space configuration in MIB.

[0153] In one embodiment, the CORESET associated with the search space used for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space used for paging monitoring by the first type of terminal.

[0154] In one embodiment, the CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring configured for the first type of terminal.

[0155] In one embodiment, the search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal.

[0156] In one embodiment, the search space configured for the second type of terminal for monitoring system messages is configured as the search space used for the first type of terminal for monitoring system messages.

[0157] In one embodiment, the additional common CORESET configured for the second type of terminal is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring;

[0158] In one embodiment, the common control resource set CORESET0 is configured as a CORESET associated with a search space used by the first type of terminal for RAR monitoring;

[0159] In one embodiment, the additional common search space configured for the second type of terminal is configured as a search space used by the first type of terminal for RAR monitoring;

[0160] In one embodiment, the common search space 0 is configured as a search space used by the first type of terminals for RAR monitoring.

[0161] In one embodiment, the additional common CORESET or CORESE0 associated with the RAR search space configured for the second type of terminal can be configured as the CORESET associated with the search space used for RAR monitoring by the first type of terminal, that is, the two are multiplexed. However, a different search space can be additionally configured for the first type of terminal for RAR monitoring. At this time, the network will schedule random access response messages of different types of terminals in different search spaces respectively.

[0162] In one embodiment, if the initial BWP configured for the second type of terminal does not include CORESET0, it means that it does not overlap with the initial BWP bandwidth of the first type of terminal; at this time, the RAR search space configured for the second type of terminal needs to be separately configured with an additional common CORESET, for example, commonControlResourceSet-Redcap or an additional public CORESET with a different public CORESET ID from the public CORESET ID attached to the initial BWP bandwidth of the first type of terminal, for example, an additional public CORESET2. At this time, the network will schedule random access response messages of different types of terminals on different initial BWPs.

[0163] In one embodiment, the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type of terminal to configure an additional (or additional) common CORESET; the ID of the additional common CORESET can be the same as or different from the additional CORESET included in the initial BWP configured for the second type of terminal. For example, the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type of terminal to configure an additional common CORESET#2 or common CORESET-Redcap for RAR monitoring; while the monitoring of paging messages, system messages, etc. configured by the first type of terminal can still continue to use an additional common CORESET configured for the second type of terminal, for example, an additional common CORESET#1 or CORSET0; this can avoid confusion.

[0164] In one embodiment, if the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type of terminal is used to configure an additional common CORESET#1 for RAR monitoring; and the monitoring of paging messages, system messages, etc. configured for the first type of terminal can still continue to use a common CORESET0 configured for the second type of terminal (assuming that the second type of terminal does not use an additional CORESET), so that no confusion will occur.

[0165] In one embodiment, if the initial BWP configured for the second type of terminal includes CORESET0, it means that there is an overlap with the initial BWP bandwidth of the first type of terminal; at this time, the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type of terminal needs to be included in CORESET0. As a preferred embodiment, the configuration of the second type of terminal can be completely the same. Among them, the system message monitoring and paging message monitoring can completely reuse the configuration of the second type of terminal; the monitoring of RAR messages can also completely reuse the configuration of the second type of terminal, or the RAR search space can be separately configured with an additional common CORESET, for example, commonControlResourceSet-Redcap or common CORESET1.

[0166] In the embodiment of the present disclosure, downlink control channel common configuration information for the initial bandwidth part BWP configuration is sent to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the predetermined resources for the first type of terminal to perform a predetermined operation; the predetermined resources include at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. In this way, after receiving the downlink control channel common configuration information for the initial bandwidth part BWP configuration sent by the access network device, the first type of terminal can perform the predetermined operation based on the predetermined resources indicated by the downlink control channel common configuration information, so that the first type of terminal can efficiently and reliably use the resources of the BWP compared to the method of not configuring the downlink control channel common configuration information for the initial BWP.

[0167] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0168] In order to better understand the embodiments of the present disclosure, the technical solution of the present disclosure is further described below through three exemplary embodiments:

[0169] Example 1

[0170] In the downlink initial BWP configured for the second type of terminal, the corresponding PDCCH-configCommon configuration is as follows: CORESET0 and / or search space 0 are configured in the MIB. The CORESET0 and / or search space 0 are used to receive SIB1. Here, the CORESET0 or search space 0 can also be used for other system message monitoring, paging message monitoring, and RAR monitoring. It should be noted that the resources for other system message monitoring, paging message monitoring, and RAR monitoring can also be associated with CORESET1 and search space 1 configured in SIB1.

[0171] In the downlink initial BWP configured for the first type of terminal, if CORESET0 is not included, the corresponding PDCCH-configCommon configuration is as follows:

[0172] Using CORESET0 and search space 0 configured for the second type of terminal to receive SIB1 (SIB1 monitoring is in CORESET0 and SS0, and other types of monitoring are not restricted);

[0173] At least one of CORESET0, CORESET1, search space 0 and search space 1 configured for the second type of terminal is used to monitor other system messages, paging monitoring, etc. As a preferred embodiment, the first type of terminal configuration and the second type of terminal configuration can be completely the same;

[0174] It should be noted that the search space monitored by the RAR of the first type of terminal may be different from the search space configured for the second type of terminal, such as search space 1, etc. And / or, the CORESET monitored by the RAR may adopt an additional common CORESET, such as CORESET1, etc.

[0175] It should be noted that only the search space of RAR monitoring is within the initial BWP bandwidth configured for the first type of terminal, while the search space or associated CORESET of paging monitoring and SI monitoring are the initial BWP configured for the second type of terminal. At this time, receiving the message requires transceiver conversion.

[0176] Example 2

[0177] In the downlink initial BWP configured for the second type of terminal, the corresponding PDCCH-configCommon configuration is as follows:

[0178] CORESET0 and / or search space 0 are configured in the MIB. The CORESET0 and / or search space 0 are used for system message monitoring;

[0179] CORESET1 or search space 1 is configured on the initial BWP of SIB1, and the resources for paging message monitoring and RAR monitoring can also be associated with CORESET1 and search space 1 configured in SIB1.

[0180] For the downlink initial BWP configured for the first type of terminal, if CORESET0 is not included, the corresponding PDCCH-configCommon configuration is as follows:

[0181] Using CORESET0 and / or search space 0 configured for the second type of terminal to monitor the system message SIB1;

[0182] Using at least one of CORESET1 and search space 1 configured for the second type of terminal to perform paging monitoring;

[0183] Using at least one of CORESET1 and search space 1 configured for the second type of terminal to perform other system monitoring;

[0184] It should be noted that the search space monitored by the RAR may adopt an additional common search space configured on the downlink initial BWP configured for the first type of terminal, for example, search space 2.

[0185] It should be noted that the search space monitored by the RAR may adopt the additional common CORESET configured on the downlink initial BWP configured by the first type of terminal, for example, CORESET2.

[0186] It should be noted that only the search space of RAR monitoring is within the initial BWP bandwidth configured for the first type of terminal, while the search space or associated CORESET of paging monitoring and SI monitoring are the initial BWP configured for the second type of terminal. At this time, receiving the message requires transceiver conversion.

[0187] Example 3

[0188] In the downlink initial BWP configured for the second type of terminal, the corresponding PDCCH-configCommon configuration is as follows: CORESET0 and / or search space 0 are configured in the MIB. The CORESET0 and / or search space 0 are used to receive SIB1. Here, the CORESET0 or search space 0 can also be used for other system message monitoring, paging message monitoring, and RAR monitoring. It should be noted that the resources for other system message monitoring, paging message monitoring, and RAR monitoring can also be associated with CORESET1 and search space 1 configured in SIB1.

[0189] For the downlink initial BWP configured for the first type of terminal, if it is included in Coreset0, the corresponding PDCCH-configCommon configuration is as follows:

[0190] Receiving SIB using CORESET0 and search space 0 configured for the second type of terminal;

[0191] At least one of CORESET0, CORESET1, search space 0 and search space 1 configured for the second type of terminal is used to perform other system message monitoring, paging monitoring and RAR monitoring, etc. As a preferred embodiment, the first type of terminal configuration and the second type of terminal configuration can be completely the same;

[0192] It should be noted that the search space monitored by the RAR of the first type of terminal may be different from the search space configured for the second type of terminal, for example, search space 1, etc. And / or, the CORESET monitored by the RAR may adopt an additional common CORESET, for example, CORESET1, etc. (the physical resource location may be the same as or different from that configured for the first type of terminal)

[0193] In one embodiment, the identifier of the additional public CORESET is different from or the same as the identifier of the public CORESET configured for the second type of terminal; and / or the identifier of the additional public search space is different from or the same as the identifier of the public search space configured for the second type of terminal.

[0194] like Figure 3 As shown, this embodiment provides a method for resource configuration, wherein the method is performed by an access network device, and the method includes:

[0195] Step 31, sending physical downlink control channel PDCCH common configuration information for the initial bandwidth part BWP configuration to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the reserved resources for the first type of terminal to perform the reserved operation; the reserved resources include at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. wherein the identifier of the additional common CORESET is different from or the same as the identifier of the common CORESET configured for the second type of terminal; and / or the identifier of the additional common search space is different from or the same as the identifier of the common search space configured for the second type of terminal.

[0196] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0197] In one embodiment, in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional common CORESET is not included in the bandwidth range of CORESET0.

[0198] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform a predetermined operation;

[0199] and / or,

[0200] The additional common search space is configured as a common search space for the first type of terminal to perform a predetermined operation;

[0201] and / or,

[0202] CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform a predetermined operation;

[0203] and / or,

[0204] The common search space 0 is configured as a common search space for the first type terminal to perform a predetermined operation.

[0205] like Figure 4 As shown, this embodiment provides a method for resource configuration, wherein the method is performed by an access network device, and the method includes:

[0206] Step 41, sending physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration to the first type terminal; wherein the downlink control channel common configuration information is used to indicate the predetermined resources for the first type terminal to perform the predetermined operation; the predetermined resources include at least one of the following: additional common control resource set CORESET; additional common search space; common control resource set CORESET0; and common search space 0. The predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type terminal are configured as the common search space for the first type terminal to perform the predetermined operation.

[0207] In some embodiments, at least one of the following is included:

[0208] The CORESET associated with the search space for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for paging monitoring configured for the first type of terminal;

[0209] The CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring configured for the first type of terminal;

[0210] The search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal;

[0211] And, the search space for system message monitoring configured for the second type of terminals is configured as the search space for system message monitoring by the first type of terminals.

[0212] In some embodiments, at least one of the following is included: an additional common CORESET is configured as a CORESET associated with a search space used by the first type of terminal for RAR monitoring;

[0213] The common control resource set CORESET0 is configured as a CORESET associated with the search space for RAR monitoring by the first type of terminals;

[0214] The additional common search space is configured as a search space for the first type of terminal to use for RAR monitoring;

[0215] And, the common search space 0 is configured as the search space used by the first type of terminals for RAR monitoring.

[0216] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0217] like Figure 5 As shown, this embodiment provides a method for resource configuration, wherein the method is executed by a first type of terminal, and the method includes:

[0218] Step 51: receiving downlink control channel common configuration information for initial bandwidth part BWP configuration sent by the access network device to the first type of terminal;

[0219] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0220] Additional common control resource set CORESET;

[0221] Additional public search spaces;

[0222] Common control resource set CORESET0;

[0223] and the public search space 0.

[0224] Here, the first type terminal and the second type terminal involved in the present disclosure may be, but are not limited to, a mobile phone, a wearable device, a vehicle-mounted terminal, a road side unit (RSU), a smart home terminal, an industrial sensor device and / or a medical device, etc. The first type terminal and the second type terminal are different types of terminals. In one embodiment, the first type terminal may be a Redcap terminal, and the second type terminal may be a non-Redcap terminal other than a Redcap terminal.

[0225] The access network device involved in the present disclosure may be a base station. Here, the base station may be various types of base stations, for example, a base station of a fifth generation mobile communication (5G) network or other evolved base stations.

[0226] It should be noted that the PDCCH common configuration information may be carried in the PDCCH common configuration (PDCCH-configCommon) field of the RedCap-specific initial DL BWP configuration or the PDCCH common system information block configuration (PDCCH-configCommonSIB) field.

[0227] It should be noted that the frequency domain resource information of PDCCH and the number of orthogonal frequency division multiplexing (OFDM) symbols occupied in the time domain are encapsulated in CORESET; the PDCCH starting OFDM symbol and monitoring period, associated CORESET and other information are encapsulated in the search space. Here, the public search space is mainly used during access and cell switching, for example, for monitoring control information related to broadcast control channels BCCH, paging, RAR, etc.

[0228] In one embodiment, a physical downlink control channel PDCCH common configuration information for an initial bandwidth part BWP configuration sent by an access network device to a first type of terminal is received; wherein the downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. wherein the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.

[0229] In one embodiment, the identifier of the additional public CORESET is different from the identifier of the public CORESET configured for the second type of terminal. It should be noted that the identifier of the additional public CORESET may not be 0.

[0230] In one embodiment, the identifier of the additional common search space is different from the identifier of the common search space configured for the second type of terminal. It should be noted that the identifier of the additional common search space may not be zero.

[0231] In one embodiment, the identifier of the additional public CORESET is the same as the identifier of the public CORESET configured for the second type of terminal. It should be noted that the identifier of the additional public CORESET may not be 0.

[0232] In one embodiment, the identifier of the additional common search space is the same as the identifier of the common search space configured for the second type of terminal. It should be noted that the identifier of the additional common search space may not be zero.

[0233] In one embodiment, if the initial BWP bandwidth does not include the bandwidth of CORSET0, the access network device may configure an additional public CORESET or an additional public search space; wherein the bandwidth of the additional public CORESET does not need to be included in the bandwidth range of CORESET0.

[0234] In one embodiment, the access network device may configure the CORESET associated with all or part of the public search space for the first type of terminal based on the additional public CORESET. Alternatively, the access network device may configure all or part of the public search space for the first type of terminal based on the additional public search space.

[0235] It should be noted that the CORESET associated with all search spaces here can be understood as the CORESET associated with the search space required for the terminal to perform all scheduled operations, and all scheduled operations may include: random access response RAR monitoring operations, paging monitoring operations, and system message monitoring operations, etc., but are not limited to the above operations. The CORESET associated with a partial search space can be understood as the CORESET associated with the search space required to perform some scheduled operations, and some scheduled operations are part of all scheduled operations. Similarly, the entire search space here can be understood as the search space required for the terminal to perform all scheduled operations, and all scheduled operations may include: random access response RAR monitoring operations, paging monitoring operations, and system message monitoring operations, etc., but are not limited to the above operations. The partial search space can be understood as the search space required to perform some scheduled operations, and some scheduled operations are part of all scheduled operations.

[0236] In one embodiment, the additional common CORESET is configured as a common search space associated CORESET for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response RAR monitoring operation; paging monitoring operation; and system message monitoring operation.

[0237] In one embodiment, the additional common search space is configured as a common search space for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response (RAR) monitoring operation; paging monitoring operation; and system message monitoring operation.

[0238] In one embodiment, a physical downlink control channel PDCCH common configuration information for an initial bandwidth part BWP configuration sent by a receiving access network device to a first type of terminal; wherein the downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: an additional common control resource set CORESET; and, an additional common search space. The additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform all predetermined operations; and / or, the additional common search space is configured as a common search space for the first type of terminal to perform all predetermined operations.

[0239] In one embodiment, the common control resource set CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response RAR monitoring operation; paging monitoring operation; and system message monitoring operation.

[0240] In one embodiment, the common control resource set CORESET0 may be used by a search space configured on an initial BWP configured for a first type of terminal and an initial BWP configured for a second type of terminal.

[0241] In one embodiment, the common control resource set CORESET0 can be used by the search space configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal. The bandwidth range of the initial BWP configured for the first type of terminal does not include the bandwidth of the common control resource set CORESET0.

[0242] In one embodiment, the common search space 0 is configured as a common search space for the first type of terminal to perform all predetermined operations, wherein the predetermined operations include at least one of the following: random access response (RAR) monitoring operation; paging monitoring operation; and system message monitoring operation.

[0243] In one embodiment, a physical downlink control channel PDCCH common configuration information for an initial bandwidth part BWP configuration sent by an access network device to a first type of terminal is received; wherein the downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: a common control resource set CORESET0; and a common search space 0. The common CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform all predetermined operations; and / or the common search space 0 is configured as a common search space for the first type of terminal to perform all predetermined operations.

[0244] In one embodiment, the common search space 0 may be used by a search space configured on an initial BWP configured for a first type of terminal and an initial BWP configured for a second type of terminal.

[0245] In one embodiment, the common search space 0 can be used by the search space configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal. The bandwidth range of the initial BWP configured for the first type of terminal does not include the bandwidth of the common control resource set CORESET0.

[0246] In one embodiment, the additional public CORESET is configured as a CORESET associated with a public search space for the first type of terminal to perform the predetermined operation; and / or, the additional public search space is configured as a public search space for the first type of terminal to perform the predetermined operation; and / or, the CORESET0 is configured as a CORESET associated with a public search space for the first type of terminal to perform the predetermined operation; and / or, the public search space 0 is configured as a public search space for the first type of terminal to perform the predetermined operation.

[0247] In one embodiment, the additional public CORESET is configured as a CORESET associated with a public search space for the first type of terminal to perform some predetermined operations; and / or, the additional public search space is configured as a public search space for the first type of terminal to perform some predetermined operations; and / or, CORESET0 is configured as a CORESET associated with a public search space for the first type of terminal to perform some predetermined operations; and / or, public search space 0 is configured as a public search space for the first type of terminal to perform some predetermined operations. The predetermined operation includes at least one of the following: random access response RAR monitoring operation; paging monitoring operation; and system message monitoring operation.

[0248] In one embodiment, a physical downlink control channel PDCCH common configuration information for an initial bandwidth portion BWP configuration sent by an access network device to a first type of terminal is received; wherein the downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. The additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform a portion of the predetermined operation; and / or, the additional common search space is configured as a common search space for the first type of terminal to perform a portion of the predetermined operation; and / or, CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform a portion of the predetermined operation; and / or, the common search space 0 is configured as a common search space for the first type of terminal to perform a portion of the predetermined operation.

[0249] It should be noted that CORESET0 and search space 0 can be configured in the master information block (MIB), and other CORESETs and / or search spaces with non-zero identifiers need to be configured in SIB1. For example, CORESET0 and / or search space 0 are configured in SIB1.

[0250] In one embodiment, the reserved resources also include resources configured for the second type of terminal in the reserved message; the reserved message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform a predetermined operation.

[0251] In one embodiment, CORESET0 and / or search space 0 are configured for the second type of terminal in MIB; CORESET x and / or search space CORESET x are configured for the second type of terminal in SIB1, where x is not 0, but may be 1, 2, etc.

[0252] In one embodiment, the CORESET associated with the search space used for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space used for paging monitoring by the first type of terminal.

[0253] In one embodiment, the CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring configured for the first type of terminal.

[0254] In one embodiment, the search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal.

[0255] In one embodiment, the search space configured for the second type of terminal for monitoring system messages is configured as the search space used for the first type of terminal for monitoring system messages.

[0256] In one embodiment, the additional common CORESET or common control resource set CORESET0 is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring;

[0257] In one embodiment, the common control resource set CORESET0 is configured as a CORESET associated with a search space used by the first type of terminal for RAR monitoring;

[0258] In one embodiment, the additional common search space is configured as the search space used by the first type of terminal for RAR monitoring.

[0259] In one embodiment, the common search space 0 is configured as a search space used by the first type of terminals for RAR monitoring.

[0260] In one embodiment, the additional common CORESET or CORESE0 associated with the RAR search space configured for the second type of terminal can be configured as the CORESET associated with the search space used for RAR monitoring by the first type of terminal, that is, the two are multiplexed. However, a different search space can be additionally configured for the first type of terminal for RAR monitoring. At this time, the network will schedule random access response messages of different types of terminals in different search spaces respectively.

[0261] In one embodiment, if the initial BWP configured for the second type of terminal does not include CORESET0, it means that it does not overlap with the initial BWP bandwidth of the first type of terminal; at this time, the RAR search space configured for the second type of terminal needs to be separately configured with an additional common CORESET, for example, commonControlResourceSet-Redcap or an additional public CORESET with a different public CORESET ID from the public CORESET ID attached to the initial BWP bandwidth of the first type of terminal, for example, an additional public CORESET2. At this time, the network will schedule random access response messages of different types of terminals on different initial BWPs.

[0262] In one embodiment, the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type of terminal to configure an additional (or additional) common CORESET; the ID of the additional common CORESET may be the same as the additional CORESET included in the initial BWP configured for the second type of terminal, or the two may be different. For example, the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type of terminal to configure an additional common CORESET#2 or common CORESET-Redcap for RAR monitoring; while the monitoring of paging messages, system messages, etc. configured by the first type of terminal can still continue to use an additional common CORESET configured for the second type of terminal, for example, an additional common CORESET#1 or CORSET0; this can avoid confusion.

[0263] In one embodiment, if the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type of terminal is used to configure an additional common CORESET#1 for RAR monitoring; and the monitoring of paging messages, system messages, etc. configured for the first type of terminal can still continue to use a common CORESET0 configured for the second type of terminal (assuming that the second type of terminal does not use an additional CORESET), so that no confusion will occur.

[0264] In one embodiment, if the initial BWP configured for the second type of terminal includes CORESET0, it means that there is an overlap with the initial BWP bandwidth of the first type of terminal; at this time, the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type of terminal needs to be included in CORESET0. As a preferred embodiment, the configuration of the second type of terminal can be completely the same. Among them, the system message monitoring and paging message monitoring can completely reuse the configuration of the second type of terminal; the monitoring of RAR messages can also completely reuse the configuration of the second type of terminal, or the RAR search space can be separately configured with an additional common CORESET, for example, commonControlResourceSet-Redcap or common CORESET1.

[0265] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0266] In one embodiment, the identifier of the additional public CORESET is different from or the same as the identifier of the public CORESET configured for the second type of terminal; and / or the identifier of the additional public search space is different from or the same as the identifier of the public search space configured for the second type of terminal.

[0267] like Figure 6 As shown, this embodiment provides a method for resource configuration, wherein the method is executed by a first type of terminal, and the method includes:

[0268] Step 61, receiving physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration sent by the access network device to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the reserved resources for the first type of terminal to perform a predetermined operation; the reserved resources include at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. wherein the identifier of the additional common CORESET is different from or the same as the identifier of the common CORESET configured for the second type of terminal; and / or the identifier of the additional common search space is different from or the same as the identifier of the common search space configured for the second type of terminal.

[0269] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0270] In one embodiment, in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional common CORESET is not included in the bandwidth range of CORESET0.

[0271] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform a predetermined operation;

[0272] and / or,

[0273] The additional common search space is configured as a common search space for the first type of terminal to perform a predetermined operation;

[0274] and / or,

[0275] CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform a predetermined operation;

[0276] and / or,

[0277] The common search space 0 is configured as a common search space for the first type terminal to perform a predetermined operation.

[0278] like Figure 7 As shown, this embodiment provides a method for resource configuration, wherein the method is executed by a first type of terminal, and the method includes:

[0279] Step 71: Send physical downlink control channel PDCCH common configuration information for initial bandwidth part BWP configuration to the first type of terminal; wherein the downlink control channel common configuration information is used to indicate the predetermined resources for the first type of terminal to perform a predetermined operation; the predetermined resources include at least one of the following: an additional common control resource set CORESET; an additional common search space; a common control resource set CORESET0; and a common search space 0. The predetermined resources also include resources configured for the second type of terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform a predetermined operation.

[0280] In some embodiments, at least one of the following is included:

[0281] The CORESET associated with the search space for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for paging monitoring configured for the first type of terminal;

[0282] The CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring configured for the first type of terminal;

[0283] The search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal;

[0284] And, the search space for system message monitoring configured for the second type of terminals is configured as the search space for system message monitoring by the first type of terminals.

[0285] In some embodiments, at least one of the following is included: an additional common CORESET is configured as a CORESET associated with a search space used by the first type of terminal for RAR monitoring;

[0286] The common control resource set CORESET0 is configured as a CORESET associated with the search space for RAR monitoring by the first type of terminals;

[0287] The additional common search space is configured as a search space for the first type of terminal to use for RAR monitoring;

[0288] And, the common search space 0 is configured as the search space used by the first type of terminals for RAR monitoring.

[0289] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0290] like Figure 8 As shown, an embodiment of the present disclosure provides a device for resource configuration, wherein the device includes:

[0291] The sending module 81 is configured to send downlink control channel common configuration information configured for the initial bandwidth part BWP to the first type of terminal;

[0292] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0293] Additional common control resource set CORESET;

[0294] Additional public search spaces;

[0295] Common control resource set CORESET0;

[0296] and the public search space 0.

[0297] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0298] like Fig. 9 As shown, an embodiment of the present disclosure provides a device for resource configuration, wherein the device includes:

[0299] The receiving module 91 is configured to receive downlink control channel common configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type of terminal;

[0300] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following:

[0301] Additional common control resource set CORESET;

[0302] Additional public search spaces;

[0303] Common control resource set CORESET0;

[0304] and the public search space 0.

[0305] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

[0306] The present disclosure provides a communication device, the communication device comprising:

[0307] processor;

[0308] a memory for storing processor-executable instructions;

[0309] The processor is configured to implement the method applied to any embodiment of the present disclosure when running executable instructions.

[0310] The processor may include various types of storage media, which are non-temporary computer storage media that can continue to memorize information stored thereon after the communication device loses power.

[0311] The processor may be connected to the memory via a bus or the like to read the executable program stored in the memory.

[0312] An embodiment of the present disclosure further provides a computer storage medium, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method of any embodiment of the present disclosure is implemented.

[0313] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0314] like Fig.10 As shown, an embodiment of the present disclosure provides a structure of a terminal.

[0315] Reference Fig.10 The terminal 800 shown in this embodiment provides a terminal 800, which can be a mobile phone, a computer, a digital broadcast terminal, a message sending and receiving device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0316] Reference Fig.10 The terminal 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0317] The processing component 802 generally controls the overall operation of the terminal 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0318] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0319] The power component 806 provides power to various components of the terminal 800. The power component 806 can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the terminal 800.

[0320] The multimedia component 808 includes a screen that provides an output interface between the terminal 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0321] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the terminal 800 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0322] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

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

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

[0325] In an exemplary embodiment, terminal 800 can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above methods.

[0326] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the terminal 800 to complete the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0327] like Fig.11 As shown, an embodiment of the present disclosure shows a structure of a base station. For example, the base station 900 can be provided as a network side device. Fig.11 The base station 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions executable by the processing component 922, such as an application. The application stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute instructions to perform any method of the aforementioned method applied in the base station.

[0328] The base station 900 may also include a power supply component 926 configured to perform power management of the base station 900, a wired or wireless network interface 950 configured to connect the base station 900 to a network, and an input / output (I / O) interface 958. The base station 900 may operate based on an operating system stored in the memory 932, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, FreeBSD TM or the like.

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

[0330] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method of resource allocation, in, The method is performed by an access network device, and the method includes: Sending downlink control channel common configuration information for initial bandwidth part BWP configuration; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: Additional common control resource set CORESET; Additional public search spaces; Common control resource set CORESET0; Public search space 0.

2. The method according to claim 1, in, The predetermined operation includes at least one of the following: Random access response RAR monitoring operation; Paging monitoring operation; System message monitoring operations.

3. The method according to claim 1, in, The identifier of the additional public CORESET is different from or the same as the identifier of the public CORESET configured for the second type of terminal; and / or the identifier of the additional public search space is different from or the same as the identifier of the public search space configured for the second type of terminal.

4. The method according to claim 1, in, In response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional common CORESET is not included in the bandwidth range of CORESET0.

5. The method according to claim 1, in, Include at least one of the following: The additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation; The additional common search space is configured as a common search space used for the first type of terminal to perform the predetermined operation; The CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation; The common search space 0 is configured as a common search space used for the first type of terminal to perform the predetermined operation.

6. The method according to claim 5, in, The reserved resources also include resources configured for the second type of terminal in the reserved message; the reserved message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform the reserved operation.

7. The method according to claim 6, in, Include at least one of the following: The CORESET associated with the search space for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for paging monitoring configured for the first type of terminal; The CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring by the first type of terminal; The search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal; The search space for system message monitoring configured for the second type of terminals is configured as the search space for system message monitoring used by the first type of terminals.

8. The method according to claim 7, in, The method comprises at least one of the following: the additional common CORESET is configured as a CORESET associated with a search space used by the first type of terminal for RAR monitoring; The common control resource set CORESET0 is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring; The additional common search space is configured as a search space used by the first type of terminals for RAR monitoring; The common search space 0 is configured as a search space used by the first type of terminals for RAR monitoring.

9. The method according to any one of claims 1 to 8, It is characterized in that The identifier of the additional common control resource set CORESET is not 0, and / or the identifier of the additional common search space is not 0.

10. The method according to any one of claims 1 to 9, It is characterized in that If the initial BWP configured for the second type of terminal includes the CORESET0, the CORESET0 includes an additional common control resource set configured for the second type of terminal.

11. The method according to any one of claims 1 to 10, It is characterized in that If the initial BWP configured for the second type of terminal includes the CORESET0, there is an overlap in bandwidth between the initial BWP configured for the second type of terminal and the initial BWP configured for the first type of terminal.

12. The method according to any one of claims 1 to 11, It is characterized in that If the bandwidth of the initial BWP does not include the bandwidth of all common control resource sets CORESET0, the bandwidth of the additional common CORESET does not need to be included in the bandwidth range of CORESET0.

13. The method according to any one of claims 1 to 12, It is characterized in that If the initial BWP does not include the common control resource set CORESET0, use all the CORESETs and / or search space #0 configured for the second type of terminal to perform at least one of the following: Receive SIB1; Receive other system messages; Paging monitoring.

14. A method of resource allocation, in, The method is performed by a first type terminal, and the method includes: Receiving downlink control channel common configuration information for initial bandwidth part BWP configuration; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: Additional common control resource set CORESET; Additional public search spaces; Common control resource set CORESET0; Public search space 0.

15. The method according to claim 14, in, The predetermined operation includes at least one of the following: Random access response RAR monitoring operation; Paging monitoring operation; System message monitoring operations.

16. The method according to claim 14, in, The identifier of the additional public CORESET is different from or the same as the identifier of the public CORESET configured for the second type of terminal; and / or the identifier of the additional public search space is different from or the same as the identifier of the public search space configured for the second type of terminal.

17. The method according to claim 14, in, In response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional common CORESET is not included in the bandwidth range of CORESET0.

18. The method according to claim 14, in, Include at least one of the following: The additional common CORESET is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation; The additional common search space is configured as a common search space used for the first type of terminal to perform the predetermined operation; The CORESET0 is configured as a CORESET associated with a common search space for the first type of terminal to perform the predetermined operation; The common search space 0 is configured as a common search space used for the first type of terminal to perform the predetermined operation.

19. The method according to claim 18, in, The reserved resources also include resources configured for the second type of terminal in the reserved message; the reserved message includes at least one of the following: MIB and SIB1; the resources configured for the second type of terminal include at least one of resources for paging monitoring, system message monitoring and RAR monitoring; the resources configured for the second type of terminal are configured as a common search space for the first type of terminal to perform the reserved operation.

20. The method according to claim 19, in, Include at least one of the following: The CORESET associated with the search space for paging monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for paging monitoring configured for the first type of terminal; The CORESET associated with the search space for system message monitoring configured for the second type of terminal is configured as the CORESET associated with the search space for system message monitoring by the first type of terminal; The search space for paging monitoring configured for the second type of terminal is configured as the search space for paging monitoring used by the first type of terminal; The search space for system message monitoring configured for the second type of terminals is configured as the search space for system message monitoring used by the first type of terminals.

21. The method according to claim 20, in, The method comprises at least one of the following: the additional common CORESET is configured as a CORESET associated with a search space used by the first type of terminal for RAR monitoring; The common control resource set CORESET0 is configured as a CORESET associated with the search space used by the first type of terminal for RAR monitoring; The additional common search space is configured as a search space used by the first type of terminals for RAR monitoring; The common search space 0 is configured as a search space used by the first type of terminals for RAR monitoring.

22. The method according to any one of claims 14 to 21, It is characterized in that The identifier of the additional common control resource set CORESET is not 0, and / or the identifier of the additional common search space is not 0.

23. The method according to any one of claims 14 to 22, It is characterized in that If the initial BWP configured for the second type of terminal includes the CORESET0, the CORESET0 includes an additional common control resource set configured for the second type of terminal.

24. The method according to any one of claims 14 to 23, It is characterized in that If the initial BWP configured for the second type of terminal includes the CORESET0, there is an overlap in bandwidth between the initial BWP configured for the second type of terminal and the initial BWP configured for the first type of terminal.

25. The method according to any one of claims 14 to 24, It is characterized in that If the bandwidth of the initial BWP does not include the bandwidth of all common control resource sets CORESET0, the bandwidth of the additional common CORESET does not need to be included in the bandwidth range of CORESET0.

26. The method according to any one of claims 14 to 25, It is characterized in that If the initial BWP does not include the common control resource set CORESET0, use all the CORESETs and / or search space #0 configured for the second type of terminal to perform at least one of the following: Receive SIB1; Receive other system messages; Paging monitoring.

27. A device for resource allocation, in, The device comprises: A sending module, configured to send downlink control channel common configuration information configured for the initial bandwidth part BWP; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: Additional common control resource set CORESET; Additional public search spaces; Common control resource set CORESET0; Public search space 0.

28. A device for resource allocation, in, The device comprises: A receiving module, configured to receive downlink control channel common configuration information configured for an initial bandwidth part BWP; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type of terminal to perform a predetermined operation; the predetermined resource includes at least one of the following: Additional common control resource set CORESET; Additional public search spaces; Common control resource set CORESET0; Public search space 0.

29. A communication device, in, include: Memory; The processor is connected to the memory and is configured to implement the method of any one of claims 1 to 13 or 14 to 26 by executing computer executable instructions stored on the memory.

30. A computer storage medium storing computer executable instructions, wherein the computer executable instructions can implement the method of any one of claims 1 to 13 or 14 to 26 after being executed by a processor.