Resource setting method, apparatus, communication device and storage medium

Abstract

An embodiment of the present disclosure provides a resource configuration method, which is performed by an access network device, and includes the steps of sending downlink control channel common configuration information configured for an initial bandwidth portion (BWP) to a first type terminal, where the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0.

Description

[Technical Field]

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

[0002] During the continuous evolution of networks, new terminals, namely, reduced capability (Redcap) terminals, are being introduced. This type of terminal is different from regular terminals, e.g., enhanced Mobile Broadband (eMBB) terminals. This type of terminal usually needs to meet the following requirements: 1. low cost, 2. low complexity, 3. some degree of coverage extension, and 4. low power consumption.

[0003] In the related technology, the Bandwidth Part (BWP) is defined. With the introduction of RedCap terminals, how to use BWP for RedCap terminals is an issue that needs to be considered. Summary of the Invention [Problem to be solved by the invention]

[0004] Embodiments of the present disclosure disclose a resource configuration method, apparatus, communication device, and storage medium. [Means for solving the problem]

[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a resource configuration method, the method being performed by an access network device, the method comprising: transmitting downlink control channel common configuration information configured for an initial bandwidth portion (BWP) to a first type terminal; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0006] In one embodiment, the predetermined action is: Random Access Response (RAR) monitoring operation; paging monitoring operation; and monitoring system messages.

[0007] In one embodiment, the identifier of the additional common CORESET and the identifier of the common CORESET configured for the second type of terminal are different or the same, and / or the identifier of the additional common search space and the identifier of the common search space configured for the second type of terminal are different or the same.

[0008] 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 within the bandwidth range of CORESET0.

[0009] In one embodiment, The additional common CORESET is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; The additional common search space is set as a common search space for performing the predetermined operation by the first type terminal; and The CORESET0 is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; and the common search space 0 is set as a common search space for performing the predetermined operation by the first type terminal.

[0010] In one embodiment, the predetermined resources further include resources configured for a second type of terminal in a predetermined message, the predetermined message including at least one of an MIB and an SIB1, the resources configured for the second type of terminal including at least one of a resource for paging monitoring, a resource for monitoring a system message, and a resource for RAR monitoring, and the resources configured for the second type of terminal are configured as a common search space for performing the predetermined operation by the first type of terminal.

[0011] In one embodiment, A CORESET associated with a search space for paging monitoring set for the second type terminal is set as a CORESET associated with a search space for paging monitoring of the first type terminal; A CORESET associated with a search space for monitoring system messages set for the second type terminal is set as a CORESET associated with a search space for monitoring system messages of the first type terminal; A search space for paging monitoring set for the second type terminal is set as a search space for paging monitoring of the first type terminal; and a search space for monitoring system messages set for the second type terminal is set as a search space for monitoring system messages of the first type terminal.

[0012] In one embodiment, the additional common CORESET is set as a CORESET associated with a search space for RAR monitoring of the first type terminal; The common control resource set (CORESET) 0 is set as a CORESET associated with a search space for RAR monitoring of the first type terminal; The additional common search space is set as a search space for RAR monitoring of the first type terminal; The common search space 0 is set as a search space for RAR monitoring of the first type terminal.

[0013] According to a second aspect of an embodiment of the present disclosure, there is provided a resource configuration method, the method being performed by a first type terminal, the method comprising: receiving downlink control channel common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0014] In one embodiment, the predetermined action is: Random Access Response (RAR) monitoring operation; paging monitoring operation; and monitoring system messages.

[0015] In one embodiment, the identifier of the additional common CORESET and the identifier of the common CORESET configured for the second type of terminal are different or the same, and / or the identifier of the additional common search space and the identifier of the common search space configured for the second type of terminal are different or the same.

[0016] 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 within the bandwidth range of CORESET0.

[0017] In one embodiment, The additional common CORESET is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; The additional common search space is set as a common search space for performing the predetermined operation by the first type terminal; and The CORESET0 is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; and the common search space 0 is set as a common search space for performing the predetermined operation by the first type terminal.

[0018] In one embodiment, the predetermined resources further include resources configured for a second type of terminal in a predetermined message, the predetermined message including at least one of an MIB and an SIB1, the resources configured for the second type of terminal including at least one of a resource for paging monitoring, a resource for monitoring a system message, and a resource for RAR monitoring, and the resources configured for the second type of terminal are configured as a common search space for performing the predetermined operation by the first type of terminal.

[0019] In one embodiment, A CORESET associated with a search space for paging monitoring set for the second type terminal is set as a CORESET associated with a search space for paging monitoring of the first type terminal; A CORESET associated with a search space for monitoring system messages set for the second type terminal is set as a CORESET associated with a search space for monitoring system messages of the first type terminal; A search space for paging monitoring set for the second type terminal is set as a search space for paging monitoring of the first type terminal; and a search space for monitoring system messages set for the second type terminal is set as a search space for monitoring system messages of the first type terminal.

[0020] In one embodiment, the additional common CORESET is set as a CORESET associated with a search space for RAR monitoring of the first type terminal; The common control resource set (CORESET) 0 is set as a CORESET associated with a search space for RAR monitoring of the first type terminal; The additional common search space is set as a search space for RAR monitoring of the first type terminal; The common search space 0 is set as a search space for RAR monitoring of the first type terminal.

[0021] According to a third aspect of an embodiment of the present disclosure, there is provided a resource configuration device, the device comprising: A transmitting module configured to transmit downlink control channel common configuration information configured for an initial bandwidth portion (BWP) to a first type terminal; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0022] According to a fourth aspect of the present disclosure, there is provided a resource configuration device, the device comprising: A receiving module configured to receive downlink control channel common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal, The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0023] According to a fifth aspect of an embodiment of the present disclosure, there is provided a communication device, the communication device comprising: a processor; a memory for storing executable instructions for said processor; The processor, when executing the executable instructions, is configured to implement a method according to any embodiment of the present disclosure.

[0024] According to a sixth aspect of an embodiment of the present disclosure, there is provided a computer storage medium having a computer-executable program stored thereon, the executable program, when executed by a processor, realizing a method according to any embodiment of the present disclosure.

[0025] In an embodiment of the present disclosure, downlink control channel common configuration information configured for an initial bandwidth portion (BWP) is transmitted to a first type terminal, and the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. In this way, after receiving the downlink control channel common configuration information configured for the initial bandwidth portion (BWP) transmitted from an access network device, the first type terminal can perform a predetermined operation based on the predetermined resources indicated by the downlink control channel common configuration information, and the first type terminal can reliably and efficiently use BWP resources compared to a method in which downlink control channel common configuration information is not configured for the initial BWP. [Brief explanation of the drawings]

[0026] [Figure 1] 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment; [Figure 2] 1 is a schematic flowchart of a resource configuration method according to an exemplary embodiment; [Figure 3] 1 is a schematic flowchart of a resource configuration method according to an exemplary embodiment; [Figure 4] 1 is a schematic flowchart of a resource configuration method according to an exemplary embodiment; [Figure 5] 1 is a schematic flowchart of a resource configuration method according to an exemplary embodiment; [Figure 6] 1 is a schematic flowchart of a resource configuration method according to an exemplary embodiment; [Figure 7] 1 is a schematic flowchart of a resource configuration method according to an exemplary embodiment; [Figure 8]1 is a schematic configuration diagram of a resource setting device according to an exemplary embodiment; [Figure 9] 1 is a schematic configuration diagram of a resource setting device according to an exemplary embodiment; [Figure 10] FIG. 2 is a schematic diagram of a terminal according to an exemplary embodiment; [Figure 11] FIG. 2 is a block diagram of a base station according to an exemplary embodiment; DETAILED DESCRIPTION OF THE INVENTION

[0027] Illustrative embodiments will now be described in detail, examples of which are illustrated in the drawings. Where the following description refers to the drawings, like numerals in different drawings represent the same or similar elements unless otherwise stated. The embodiments described in the following illustrative examples do not represent all embodiments consistent with embodiments of the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of embodiments of the present disclosure, as detailed in the appended claims.

[0028] The terms used in the embodiments of the present disclosure are merely for the purpose of describing particular embodiments and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. Furthermore, the term "and / or" as used herein refers to any and all possible combinations of one or more of the associated listed items.

[0029] In embodiments of the present disclosure, terms such as first, second, and third may be used to describe various pieces of information, but it should be understood that such information should not be limited to these terms. These terms are merely used to distinguish between the same types of information. For example, first information can be referred to as second information, and similarly, second information can be referred to as first information, without departing from the scope of embodiments of the present disclosure. Depending on the context, the word "if" used herein can be interpreted as "when" or "in the case of" or "responsive to a determination."

[0030] For simplicity and ease of understanding, the terms "greater than" and "less than" are used herein to characterize magnitude relationships. However, those skilled in the art will appreciate that the term "greater than" also includes the meaning "greater than or equal to," and the term "less than" also includes the meaning "less than or equal to."

[0031] Referring to Figure 1, a schematic diagram of a wireless communication system provided by an embodiment of the present disclosure is shown. As shown in Figure 1, the wireless communication system is a communication system based on mobile communication technology, and the wireless communication system may include several user equipments (UEs) 110 and several base stations 120.

[0032] User equipment 110 refers to devices that provide voice and / or data connectivity to users. The user equipment 110 can communicate with one or more core networks via a Radio Access Network (RAN). The user equipment 110 may be an Internet of Things device, such as a sensor device, a mobile phone, or a computer with Internet of Things user equipment, and may be a fixed, portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted device. For example, the user equipment 110 may be a station (STA), subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment. Alternatively, the user equipment 110 may be an unmanned aerial vehicle (UAV) device. Alternatively, the user equipment 110 may be an in-vehicle device, such as an electronic control unit with wireless communication capabilities, a wireless user equipment device with an external electronic control unit, or a roadside device, such as a street lamp, traffic light, or other roadside device with wireless communication capabilities.

[0033] The base station 120 may be a network-side device in a wireless communication system. The wireless communication system may be a 4th generation mobile communication (4G) system, also called a Long Term Evolution (LTE) system. Alternatively, the wireless communication system may be a 5G system, also called a new radio system or a 5G NR system. Alternatively, the wireless communication system may be a system that is the next generation of the 5G system. An access network in a 5G system may be called a New Generation-Radio Access Network (NG-RAN).

[0034] The base station 120 may be an evolved base station (eNB) used in a 4G system. Alternatively, the base station 120 may be a base station (gNB) using a centralized distributed architecture in a 5G system. When the base station 120 uses a centralized distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DUs). The central unit is provided with protocol stacks for a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Media Access Control (MAC) layer. The distributed units are provided with a protocol stack for a physical (PHY) layer. The embodiments of the present disclosure are not limited to a specific implementation of the base station 120.

[0035] A wireless connection can be established between the base station 120 and the user equipment 110 via a wireless air interface. In various embodiments, the wireless air interface is a wireless air interface based on a fourth generation mobile communication network technology (4G) standard. Alternatively, the wireless air interface is a wireless air interface based on a fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new radio. Alternatively, the wireless air interface may be a wireless air interface based on a 5G next generation mobile communication network technology standard.

[0036] In some embodiments, an end-to-end (E2E) connection can be established between the user equipment 110, such as vehicle-to-vehicle (V2V) communication in vehicle-to-everything (V2X) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-pedestrian (V2P) communication.

[0037] The above user equipment can be considered as a terminal in the following examples.

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

[0039] The base stations 120 are each 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, a Mobility Management Entity (MME) in an Evolved Packet Core (EPC) network. Alternatively, the network management device may be another core network device, 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 of the network management device 130.

[0040] In order to facilitate the understanding of those skilled in the art, the embodiments of the present disclosure enumerate several embodiments to clearly explain the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art will understand that the several embodiments provided by the embodiments of the present disclosure may be implemented alone, may be implemented in combination with the methods of other embodiments in the embodiments of the present disclosure, or may be implemented alone or in combination with some methods in other related technologies, and the embodiments of the present disclosure are not limited thereto.

[0041] In order to better understand the technical solution described in any embodiment of the present disclosure, the application scenario of the related technology will be described first.

[0042] In the fourth generation mobile communication technology (4G) system, two technologies have been proposed to support Internet of Things services: Machine Type Communication (MTC) and Narrow Band Internet of Things (NB-IoT).

[0043] These two technologies primarily target scenarios with low speeds and high latency, such as meter reading and environmental monitoring. In one example, NB-IoT can only support speeds of a few hundred kHz, while MTC can only support speeds of a few megahertz. However, with the development of Internet of Things services, such as video surveillance, smart home, wearable devices, and industrial sensing and monitoring, these services typically require speeds of tens to hundreds of megahertz and relatively high latency requirements, making it difficult for MTC and NB-IoT technologies in fourth-generation mobile communication technology to meet these requirements. Based on this situation, a new terminal type has been proposed to be redesigned to address the requirements of the Internet of Things in the fifth-generation mobile communication technology (5G) new wireless technology.

[0044] In one embodiment, such a new terminal type is called a reduced capability terminal (RedCap), or abbreviated as NR-lite. A RedCap based on 5G NR-lite typically needs to meet the requirements of low cost, low complexity, some coverage extension, and power saving.

[0045] Because 5G New Radio was designed for high-end terminals, such as those with high speeds and low latency, the related design cannot meet the above requirements of NR-lite. To meet the requirements of NR-lite, the New Radio (NR) system must be modified. In one embodiment, to meet requirements such as low cost and low complexity, the radio frequency bandwidth of NR-IoT can be limited, for example, to 20 MHz. In one embodiment, the size of the NR-lite buffer can be limited, and further, the size of each received transport block can be limited. In one embodiment, a possible optimization for power saving is to simplify the communication flow and reduce the number of times NR-lite users detect the downlink control channel.

[0046] In one embodiment, the information element (IE) field PDCCH-ConfigCommon is used to configure cell-specific Physical Downlink Control Channel (PDCCH) parameters provided in system information blocks (SIBs) and dedicated signaling.

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

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

[0049] After the Redcap terminal is introduced, an initial BWP for the downlink for the Random Access Response (RAR) can be configured individually for the Redcap terminal in SIB1. This initial BWP may also be used for paging. The method for configuring the common search space in the initial BWP is not defined.

[0050] As shown in FIG. 2, in this embodiment, a resource configuration method is provided, which is performed by an access network device, and includes the following step 21:

[0051] In step 21, the physical downlink control channel (PDCCH) common configuration information configured for the initial bandwidth portion (BWP) is transmitted to the first type terminal.

[0052] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0053] The first type terminal and the second type terminal according to the present disclosure may be, but are not limited to, a mobile phone, a wearable device, an in-vehicle terminal, a roadside unit (RSU), a smart home terminal, an industrial sensing device, and / or a medical device. 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.

[0054] The access network device according to the present disclosure may be a base station, where the base station may be of various types, for example, a base station of a fifth generation mobile communication (5G) network, or other evolved base station.

[0055] In one embodiment, a downlink initial BWP is configured in a first type terminal, and PDCCH common configuration information configured for the initial BWP is transmitted to the first type terminal, where the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0.

[0056] In addition, the PDCCH common configuration information can be included in the PDCCH common configuration (PDCCH-configCommon) field or the PDCCH common system information block configuration (PDCCH-configCommonSIB) field of the RedCap-specific initial downlink BWP configuration.

[0057] Information such as frequency domain resource information of the PDCCH and the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols occupied in the time domain is encapsulated in the CORESET, and information such as the PDCCH starting OFDM symbol, monitoring period, and related CORESET is encapsulated in the search space. The common search space is mainly used during access and cell switching, and is used to monitor control information related to the Broadcast Control Channel (BCCH), paging, RAR, etc. Related messages such as RAR, i.e., messages for random access responses, include msg2, msg4, msgB, etc.

[0058] In one embodiment, the method transmits physical downlink control channel (PDCCH) common configuration information configured for the initial bandwidth portion (BWP) to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform a predetermined operation, the predetermined resources including at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. The predetermined operation includes at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0059] In one embodiment, the identifier of the additional common CORESET is different from the common CORESET-like identifier set for the second type terminal. Note that the identifier of the additional common CORESET does not have to be 0.

[0060] 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 terminal. Note that the identifier of the additional common search space does not have to be 0.

[0061] In one embodiment, the identifier of the additional common CORESET is the same as the identifier of the common CORESET set for the second type terminal. Note that the identifier of the additional common CORESET does not have to be 0.

[0062] 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 terminal. Note that the identifier of the additional common search space does not have to be 0.

[0063] In one embodiment, if this initial BWP bandwidth does not include the bandwidth of CORESET0, an additional common CORESET or an additional common search space can be set, and the bandwidth of this additional common CORESET does not need to be included within the bandwidth range of CORESET0.

[0064] In one embodiment, a CORESET associated with all or part of the common search space for the first type terminal can be set based on the additional common CORESET, or all or part of the common search space for the first type terminal can be set based on the additional common search space.

[0065] Note that the CORESET associated with all search spaces herein can be understood as a CORESET associated with search spaces required for the terminal to perform all predetermined operations, and all predetermined operations may include, but are not limited to, a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation. The CORESET associated with a portion of search spaces herein can be understood as a CORESET associated with search spaces required for performing some predetermined operations, and some predetermined operations are a portion of all predetermined operations. Similarly, the entire search space herein can be understood as a search space required for the terminal to perform all predetermined operations, and all predetermined operations may include, but are not limited to, a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation. The portion of search spaces herein can be understood as a search space required for performing some predetermined operations, and some predetermined operations are a portion of all predetermined operations.

[0066] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for performing all predetermined operations by the first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0067] In one embodiment, the additional common search space is configured as a common search space for performing all predetermined operations by the first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0068] In one embodiment, the method transmits physical downlink control channel (PDCCH) common configuration information configured for the initial bandwidth portion (BWP) to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform predetermined operations, the predetermined resources including at least one of an additional common control resource set (CORESET) and an additional common search space, where the additional common CORESET is configured as a CORESET associated with the common search space for performing all predetermined operations by the first type terminal, and / or the additional common search space is configured as a common search space for performing all predetermined operations by the first type terminal.

[0069] In one embodiment, a common control resource set (CORESET) 0 is configured as a CORESET associated with a common search space for performing all predetermined operations by a first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0070] In one embodiment, the common control resource set (CORESET) 0 can be used by the initial BWP set for the first type of terminal and the search space set in the initial BWP set for the second type of terminal.

[0071] In one embodiment, the common control resource set (CORESET) 0 can be used by the search space set in the initial BWP set for the first type terminal and the initial BWP set for the second type terminal, and the bandwidth range of the initial BWP set for the first type terminal does not include the bandwidth of the common control resource set (CORESET) 0.

[0072] In one embodiment, the common search space 0 is set as a common search space for performing all predetermined operations by the first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0073] In one embodiment, a method transmits physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform predetermined operations, the predetermined resources including at least one of a common control resource set (CORESET) 0 and a common search space 0. The common CORESET 0 is configured as a CORESET associated with a common search space for performing all predetermined operations by the first type terminal, and / or the common search space 0 is configured as a common search space for performing all predetermined operations by the first type terminal.

[0074] In one embodiment, the common search space 0 can be used by the search spaces set in the initial BWP set for the first type of terminal and the initial BWP set for the second type of terminal.

[0075] In one embodiment, the common search space 0 can be used by the search spaces set in the initial BWP set for the first type terminal and the initial BWP set for the second type terminal. The bandwidth range of the initial BWP set for the first type terminal does not include the bandwidth of the common control resource set (CORESET) 0.

[0076] In one embodiment, the additional common CORESET is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal, and / or the additional common search space is set as a common search space for performing the predetermined operation by the first type terminal, and / or CORESET0 is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal, and / or common search space0 is set as a common search space for performing the predetermined operation by the first type terminal.

[0077] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for performing some predetermined operations by the first type terminal, and / or the additional common search space is configured as a common search space for performing some predetermined operations by the first type terminal, and / or CORESET0 is configured as a CORESET associated with a common search space for performing some predetermined operations by the first type terminal, and / or common search space0 is configured as a common search space for performing some predetermined operations by the first type terminal. The predetermined operations include at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0078] In one embodiment, a method transmits physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform a predetermined operation, the predetermined resources including at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. The additional common CORESET is configured as a CORESET associated with the common search space for performing some predetermined operations by the first type terminal, and / or the additional common search space is configured as a common search space for performing some predetermined operations by the first type terminal, and / or CORESET 0 is configured as a CORESET associated with the common search space for performing some predetermined operations by the first type terminal, and / or the common search space 0 is configured as a common search space for performing some predetermined operations by the first type terminal.

[0079] Note that CORESET0 and search space 0 can be set in the Master Information Block (MIB), and other CORESETs and / or search spaces other than 0 must be set in SIB1. For example, CORESET1 and / or search space 1 are set in SIB1.

[0080] In one embodiment, the predetermined resources further include resources configured for the second type terminal in the predetermined message, the predetermined message including at least one of MIB and SIB1, the resources configured for the second type terminal including at least one of resources for paging monitoring, resources for system message monitoring, and resources for RAR monitoring, and the resources configured for the second type terminal are configured as a common search space for performing the predetermined operation by the first type terminal.

[0081] In one embodiment, CORESET0 and / or search space 0 are set for the second type of terminal in MIB, and an additional CORESETx and / or additional search space CORESETx are set for the second type of terminal in SIB1, where x may not be 0 but may be 1, 2, etc.

[0082] In one embodiment, for monitoring SIB1, CORESET0 and / or search space 0 are configured for the second type terminal in the MIB, and CORESETx and / or search space CORESETx are configured for the second type terminal in SIB1, where x may not be 0 but may be 1, 2, etc. Monitoring of other SIs, or paging monitoring, or RAR monitoring may be associated with CORESET0 and / or search space 0, or CORESETx and / or search space CORESETx, configured for the second type terminal in the MIB, i.e., the settings for CORESET and search space may be associated with the settings of CORESET0 and / or search space 0 or additional CORESETs and / or additional search spaces configured in the MIB.

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

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

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

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

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

[0088] In one embodiment, the common control resource set (CORESET) 0 is configured as a CORESET associated with a search space for RAR monitoring of the first type terminal.

[0089] In one embodiment, the additional common search space established for the second type of terminal is set as a search space for RAR monitoring of the first type of terminal.

[0090] In one embodiment, the common search space 0 is set as the search space for RAR monitoring of the first type terminal.

[0091] In one embodiment, an additional common CORESET or CORESE0 associated with the RAR search space configured for the second type terminal can be determined as a CORESET associated with the search space for RAR monitoring of the first type terminal, i.e., both are reused. However, a different search space can be configured separately for RAR monitoring of the first type terminal. In this case, the network schedules random access response messages of different types of terminals in different search spaces.

[0092] In one embodiment, if the initial BWP configured for the second type terminal does not include CORESET0, it means that there is no overlap in bandwidth with the initial BWP of the first type terminal. In this case, the RAR search space configured for the second type terminal needs to configure an additional common CORESET separately, such as commonControlResourceSet-Redcap or an additional common CORESET such as an additional common CORESET2 that is different from the common CORESET ID added in the bandwidth of the initial BWP of the first type terminal. In this case, the network schedules random access response messages of different types of terminals using different initial BWPs.

[0093] In one embodiment, in the PDCCH-ConfigCommon field, the commonControlResourceSet needs to be extended for the first type terminal to configure one added (or additional) common CORESET, and the ID of this added common CORESET may be the same as or different from the additional CORESET included in the initial BWP configured for the second type terminal. For example, in the PDCCH-ConfigCommon field, the commonControlResourceSet needs to be extended for the first type terminal to configure one added common CORESET#2 or common CORESET-Redcap for RAR monitoring, while monitoring of paging messages, system messages, etc. configured for the first type terminal can continue to use one added common CORESET, such as CORESET#1 or CORESET0, configured for the second type terminal, thereby avoiding confusion.

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

[0095] In one embodiment, if the initial BWP configured for the second type terminal includes CORESET0, it means that there is bandwidth overlap with the initial BWP of the first type terminal, and in this case, the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type terminal needs to be included in CORESET0. In a preferred embodiment, it may be completely the same as the configuration of the second type terminal. The configuration of the second type terminal can be completely reused for system message monitoring and paging message monitoring, and the configuration of the second type terminal can also be completely reused for RAR message monitoring, or an additional common CORESET can be configured separately for the RAR search space, such as commonControlResourceSet-Redcap or common CORESET1.

[0096] In an embodiment of the present disclosure, downlink control channel common configuration information configured for an initial bandwidth portion (BWP) is transmitted to a first type terminal, and the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. In this way, after receiving the downlink control channel common configuration information configured for the initial bandwidth portion (BWP) transmitted from the access network device, the first type terminal can perform a predetermined operation based on the predetermined resources indicated by the downlink control channel common configuration information, and the first type terminal can reliably use the BWP resources efficiently compared to a method in which downlink control channel common configuration information is not configured for the initial BWP.

[0097] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0098] To better understand the embodiments of the present disclosure, the technical solutions of the present disclosure are described below in three exemplary embodiments.

[0099] Example 1 In a downlink initial BWP configured for a second type terminal, the corresponding PDCCH-configCommon is configured as follows: CORESET0 and / or search space 0 are configured in MIB. This CORESET0 and / or search space 0 are used to receive SIB1. This CORESET0 or search space 0 can also be used for monitoring other system messages, paging message monitoring, RAR monitoring, etc. In addition, resources for monitoring other system messages, paging message monitoring, and RAR monitoring can also be associated with CORESET1 and search space 1 configured in SIB1.

[0100] If the downlink initial BWP configured for the first type terminal does not include CORESET0, the corresponding PDCCH-configCommon is configured as follows: Receive SIB1 using CORESET0 and search space 0 configured for a second type of terminal (SIB1 monitoring is performed in CORESET0 and SS0, and monitoring of other types is not limited); At least one of CORESET0, CORESET1, search space 0, and search space 1 configured for the second type terminal is used to perform monitoring of other system messages, paging monitoring, etc. In a preferred embodiment, the configuration of the first type terminal and the configuration of the second type terminal may be exactly the same.

[0101] In addition, the search space for RAR monitoring of the first type of terminal may be different from the search space set for the second type of terminal, such as search space 1. And / or, the CORESET for RAR monitoring may use an additional common CORESET such as CORESET1.

[0102] Note that the search space for RAR monitoring only is within the initial BWP bandwidth range set for the first type of terminal, and the search space or associated CORESET for the paging monitoring ring and SI monitoring ring is the initial BWP set for the second type of terminal, in which case message reception requires transceiver conversion.

[0103] Example 2 In the downlink initial BWP configured for the second type terminal, the corresponding PDCCH-configCommon is configured as follows: CORESET0 and / or search space 0 are set in the MIB. This CORESET0 and / or search space 0 are used for monitoring system messages. CORESET1 or search space 1 may be configured in the initial BWP of SIB1, and resources for paging message monitoring and RAR monitoring may be associated with CORESET1 and search space 1 configured in SIB1.

[0104] If the downlink initial BWP configured for the first type terminal does not include CORESET0, the corresponding PDCCH-configCommon is configured as follows: monitoring the system message SIB1 using CORESET0 and / or search space 0 configured for the second type terminal; performing paging monitoring using at least one of CORESET1 and search space 1 set for the second type terminal; Monitoring other systems using at least one of CORESET1 and search space 1 set for the second type terminal; In addition, the search space for RAR monitoring can use additional common search spaces such as search space 2 set in the downlink initial BWP set for the first type of terminal.

[0105] In addition, the search space for RAR monitoring can use additional common CORESETs such as CORESET2 set in the downlink initial BWP set for the first type of terminal.

[0106] Note that the search space for RAR monitoring only is within the bandwidth range of the initial BWP set for the first type of terminal, and the search space or associated CORESET for paging monitoring and SI monitoring is the initial BWP set for the second type of terminal, in which case message reception requires transceiver conversion.

[0107] Example 3 In a downlink initial BWP configured for a second type terminal, the corresponding PDCCH-configCommon is configured as follows: CORESET0 and / or search space 0 are configured in MIB. This CORESET0 and / or search space 0 are used to receive SIB1. This CORESET0 or search space 0 can also be used for monitoring other system messages, paging message monitoring, RAR monitoring, etc. In addition, resources for monitoring other system messages, paging message monitoring, and RAR monitoring can also be associated with CORESET1 and search space 1 configured in SIB1.

[0108] If the downlink initial BWP configured for the first type terminal includes Coreset0, the corresponding PDCCH-configCommon is configured as follows: Receive an SIB using CORESET0 and search space 0 configured for a second type of terminal; At least one of CORESET0, CORESET1, search space 0, and search space 1 set for the second type terminal is used to monitor other system messages, paging monitoring, RAR monitoring, etc. In a preferred embodiment, the settings of the first type terminal and the second type terminal may be exactly the same.

[0109] In addition, the search space for RAR monitoring of the first type terminal may be different from the search space set for the second type terminal, such as search space 1, and / or the CORESET for RAR monitoring may use an additional common CORESET such as CORESET1 (the physical resource location may be the same as or different from that set for the first type terminal).

[0110] In one embodiment, the identifier of the additional common CORESET and the identifier of the common CORESET configured for the second type of terminal are different or the same, and / or the identifier of the additional common search space and the identifier of the common search space configured for the second type of terminal are different or the same.

[0111] As shown in FIG. 3, in this embodiment, a resource configuration method is provided, which is performed by an access network device, and includes the following step 31:

[0112] In step 31, physical downlink control channel (PDCCH) common configuration information configured for the initial bandwidth portion (BWP) is transmitted to the first type terminal, where the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. An identifier of the additional common CORESET and an identifier of the common CORESET configured for the second type terminal are different from or the same as each other, and / or an identifier of the additional common search space and an identifier of the common search space configured for the second type terminal are different from or the same as each other.

[0113] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0114] 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 within the bandwidth range of CORESET0.

[0115] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for performing a predetermined operation by a terminal of the first type; and / or The additional common search space is established as a common search space for performing a predetermined operation by the first type terminal; and / or CORESET0 is set as a CORESET associated with a common search space for performing a predetermined operation by a first type terminal; and / or A common search space 0 is set as the common search space for performing a predetermined operation by a first type terminal.

[0116] As shown in FIG. 4, in this embodiment, a resource configuration method is provided, which is performed by an access network device, and includes the following step 41:

[0117] In step 41, physical downlink control channel (PDCCH) common configuration information configured for the initial bandwidth portion (BWP) is transmitted to the first type terminal, where the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. The predetermined resources further include resources configured for the second type terminal in a predetermined message, where the predetermined message includes at least one of an MIB and an SIB1, the resources configured for the second type terminal include at least one of a resource for paging monitoring, a resource for system message monitoring, and a resource for RAR monitoring, and the resources configured for the second type terminal are configured as a common search space for the first type terminal to perform a predetermined operation.

[0118] In one embodiment, A CORESET associated with a search space for paging monitoring set for the second type terminal is set as a CORESET associated with a search space for paging monitoring of the first type terminal; A CORESET associated with a search space for monitoring system messages set for a second type terminal is set as a CORESET associated with a search space for monitoring system messages of a first type terminal; A search space for paging monitoring set for the second type terminal is set as a search space for paging monitoring of the first type terminal; and setting the search space for monitoring system messages set for the second type terminal as the search space for monitoring system messages of the first type terminal.

[0119] In some embodiments, the additional common CORESET is configured as a CORESET associated with a search space for RAR monitoring of the first type of terminal; A common control resource set (CORESET) 0 is set as a CORESET associated with a search space for RAR monitoring of the first type terminal; The additional common search space is set as a search space for RAR monitoring of the first type terminal; and and setting the common search space 0 as the search space for RAR monitoring of the first type terminal.

[0120] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0121] As shown in FIG. 5, in this embodiment, a resource configuration method is provided, which is performed by a first type terminal, and includes the following step 51:

[0122] In step 51, receive downlink control channel common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal.

[0123] The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0124] The first type terminal and the second type terminal according to the present disclosure may be, but are not limited to, a mobile phone, a wearable device, an in-vehicle terminal, a roadside unit (RSU), a smart home terminal, an industrial sensing device, and / or a medical device. 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.

[0125] The access network device according to the present disclosure may be a base station, where the base station may be of various types, for example, a base station of a fifth generation mobile communication (5G) network, or other evolved base station.

[0126] In addition, the PDCCH common configuration information can be included in the PDCCH common configuration (PDCCH-configCommon) field or the PDCCH common system information block configuration (PDCCH-configCommonSIB) field of the RedCap-specific initial downlink BWP configuration.

[0127] In addition, information such as frequency domain resource information of the PDCCH and the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols occupied in the time domain is encapsulated in the CORESET, and information such as the PDCCH start OFDM symbol, monitoring period, and associated CORESET is encapsulated in the search space. The common search space is mainly used during access and cell switching, and is used to monitor control information related to, for example, the Broadcast Control Channel (BCCH), paging, RAR, etc.

[0128] In one embodiment, the method includes receiving physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform a predetermined operation; the predetermined resources including at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. The predetermined operation includes at least one of 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 common CORESET is different from the common CORESET-like identifier set for the second type terminal. Note that the identifier of the additional common CORESET does not have to 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 terminal. Note that the identifier of the additional common search space does not have to be 0.

[0131] In one embodiment, the identifier of the additional common CORESET is the same as the identifier of the common CORESET set for the second type terminal. Note that the identifier of the additional common CORESET does not have to 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 terminal. Note that the identifier of the additional common search space does not have to be 0.

[0133] In one embodiment, if the bandwidth of this initial BWP does not include the bandwidth of CORESET0, the access network device can configure an additional common CORESET or an additional common search space, and the bandwidth of this additional common CORESET does not need to be included within the bandwidth range of CORESET0.

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

[0135] Note that the CORESET associated with all search spaces herein can be understood as a CORESET associated with search spaces required for the terminal to perform all predetermined operations, and all predetermined operations may include, but are not limited to, a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation. The CORESET associated with a portion of search spaces herein can be understood as a CORESET associated with search spaces required for performing some predetermined operations, and some predetermined operations are a portion of all predetermined operations. Similarly, the entire search space herein can be understood as a search space required for the terminal to perform all predetermined operations, and all predetermined operations may include, but are not limited to, a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation. The portion of search spaces herein can be understood as a search space required for performing some predetermined operations, and some predetermined operations are a portion of all predetermined operations.

[0136] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for performing all predetermined operations by the first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0137] In one embodiment, the additional common search space is configured as a common search space for performing all predetermined operations by the first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0138] In one embodiment, the method includes receiving physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform predetermined operations, the predetermined resources including at least one of an additional common control resource set (CORESET) and an additional common search space, where the additional common CORESET is configured as a CORESET associated with the common search space for performing all predetermined operations by the first type terminal, and / or the additional common search space is configured as a common search space for performing all predetermined operations by the first type terminal.

[0139] In one embodiment, a common control resource set (CORESET) 0 is configured as a CORESET associated with a common search space for performing all predetermined operations by a first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0140] In one embodiment, the common control resource set (CORESET) 0 can be used by the initial BWP set for the first type of terminal and the search space set in the initial BWP set for the second type of terminal.

[0141] In one embodiment, the common control resource set (CORESET) 0 can be used by the search space set in the initial BWP set for the first type terminal and the initial BWP set for the second type terminal, and the bandwidth range of the initial BWP set for the first type terminal does not include the bandwidth of the common control resource set (CORESET) 0.

[0142] In one embodiment, the common search space 0 is set as a common search space for performing all predetermined operations by the first type terminal, the predetermined operations including at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0143] In one embodiment, a method includes receiving physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform predetermined operations, the predetermined resources including at least one of a common control resource set (CORESET) 0 and a common search space 0. The common CORESET 0 is configured as a CORESET associated with a common search space for performing all predetermined operations by the first type terminal, and / or the common search space 0 is configured as a common search space for performing all predetermined operations by the first type terminal.

[0144] In one embodiment, the common search space 0 can be used by the search spaces set in the initial BWP set for the first type of terminal and the initial BWP set for the second type of terminal.

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

[0146] In one embodiment, the additional common CORESET is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal, and / or the additional common search space is set as a common search space for performing the predetermined operation by the first type terminal, and / or CORESET0 is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal, and / or common search space0 is set as a common search space for performing the predetermined operation by the first type terminal.

[0147] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for performing some predetermined operations by the first type terminal, and / or the additional common search space is configured as a common search space for performing some predetermined operations by the first type terminal, and / or CORESET0 is configured as a CORESET associated with a common search space for performing some predetermined operations by the first type terminal, and / or common search space0 is configured as a common search space for performing some predetermined operations by the first type terminal. The predetermined operations include at least one of a random access response (RAR) monitoring operation, a paging monitoring operation, and a system message monitoring operation.

[0148] In one embodiment, a method includes receiving physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal, the downlink control channel common configuration information being used to indicate predetermined resources for the first type terminal to perform a predetermined operation, the predetermined resources including at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. The additional common CORESET is configured as a CORESET associated with the common search space for performing some predetermined operations by the first type terminal, and / or the additional common search space is configured as a common search space for performing some predetermined operations by the first type terminal, and / or CORESET 0 is configured as a CORESET associated with the common search space for performing some predetermined operations by the first type terminal, and / or the common search space 0 is configured as a common search space for performing some predetermined operations by the first type terminal.

[0149] Note that CORESET0 and search space 0 can be set in the Master Information Block (MIB), and other CORESETs and / or search spaces other than 0 must be set in SIB1. For example, CORESET0 and / or search space 0 are set in SIB1.

[0150] In one embodiment, the predetermined resources further include resources configured for the second type terminal in the predetermined message, the predetermined message including at least one of MIB and SIB1, the resources configured for the second type terminal including at least one of resources for paging monitoring, resources for system message monitoring, and resources for RAR monitoring, and the resources configured for the second type terminal are configured as a common search space for performing the predetermined operation by the first type terminal.

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

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

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

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

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

[0156] In one embodiment, the additional common CORESET or common control resource set (CORESET) 0 is configured as a CORESET associated with a search space for RAR monitoring of the first type terminal.

[0157] In one embodiment, the common control resource set (CORESET) 0 is configured as a CORESET associated with a search space for RAR monitoring of the first type terminal.

[0158] In one embodiment, the additional common search space is set as a search space for RAR monitoring of the first type of terminal.

[0159] In one embodiment, the common search space 0 is set as the search space for RAR monitoring of the first type terminal.

[0160] In one embodiment, an additional common CORESET or CORESE0 associated with the RAR search space configured for the second type terminal can be configured as a CORESET associated with the search space for RAR monitoring of the first type terminal, i.e., both are reused. However, a different search space can be configured separately for RAR monitoring of the first type terminal. In this case, the network schedules random access response messages of different types of terminals in different search spaces.

[0161] In one embodiment, if the initial BWP configured for the second type terminal does not include CORESET0, it means that there is no overlap in bandwidth with the initial BWP of the first type terminal. In this case, the RAR search space configured for the second type terminal needs to configure an additional common CORESET separately, such as commonControlResourceSet-Redcap or an additional common CORESET such as an additional common CORESET2 that is different from the common CORESET ID added in the bandwidth of the initial BWP of the first type terminal. In this case, the network schedules random access response messages of different types of terminals using different initial BWPs.

[0162] In one embodiment, in the PDCCH-ConfigCommon field, the commonControlResourceSet needs to be extended for the first type terminal to configure one added (or additional) common CORESET, and the ID of this added common CORESET may be the same as or different from the additional CORESET included in the initial BWP configured for the second type terminal. For example, in the PDCCH-ConfigCommon field, the commonControlResourceSet needs to be extended for the first type terminal to configure one added common CORESET#2 or common CORESET-Redcap for RAR monitoring, while monitoring of paging messages, system messages, etc. configured for the first type terminal can continue to use one added common CORESET, such as CORESET#1 or CORESET0, configured for the second type terminal, thereby avoiding confusion.

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

[0164] In one embodiment, if the initial BWP configured for the second type terminal includes CORESET0, it means that there is bandwidth overlap with the initial BWP of the first type terminal. In this case, the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type terminal needs to be included in CORESET0. In a preferred embodiment, it may be completely the same as the configuration of the second type terminal. The configuration of the second type terminal can be completely reused for system message monitoring and paging message monitoring, and the configuration of the second type terminal can also be completely reused for RAR message monitoring, or an additional common CORESET can be configured separately for the RAR search space, such as commonControlResourceSet-Redcap or common CORESET1.

[0165] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0166] In one embodiment, the identifier of the additional common CORESET and the identifier of the common CORESET configured for the second type of terminal are different or the same, and / or the identifier of the additional common search space and the identifier of the common search space configured for the second type of terminal are different or the same.

[0167] As shown in FIG. 6, in this embodiment, a resource configuration method is provided, which is performed by a first type terminal, and includes the following step 61:

[0168] In step 61, physical downlink control channel (PDCCH) common configuration information configured for an initial bandwidth portion (BWP) sent by the access network device to the first type terminal is received, the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, the predetermined resources including at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. An identifier of the additional common CORESET and an identifier of the common CORESET configured for the second type terminal are different from or the same as each other, and / or an identifier of the additional common search space and an identifier of the common search space configured for the second type terminal are different from or the same as each other.

[0169] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0170] 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 within the bandwidth range of CORESET0.

[0171] In one embodiment, the additional common CORESET is configured as a CORESET associated with a common search space for performing a predetermined operation by a terminal of the first type; and / or The additional common search space is established as a common search space for performing a predetermined operation by the first type terminal; and / or CORESET0 is set as a CORESET associated with a common search space for performing a predetermined operation by a first type terminal; and / or A common search space 0 is set as the common search space for performing a predetermined operation by a first type terminal.

[0172] As shown in FIG. 7, in this embodiment, a resource configuration method is provided, which is performed by a first type terminal, and includes the following step 71:

[0173] In step 71, physical downlink control channel (PDCCH) common configuration information configured for the initial bandwidth portion (BWP) is transmitted to the first type terminal, where the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform a predetermined operation, and the predetermined resources include at least one of an additional common control resource set (CORESET), an additional common search space, a common control resource set (CORESET) 0, and a common search space 0. The predetermined resources further include resources configured for the second type terminal in a predetermined message, where the predetermined message includes at least one of an MIB and an SIB1, the resources configured for the second type terminal include at least one of a resource for paging monitoring, a resource for system message monitoring, and a resource for RAR monitoring, and the resources configured for the second type terminal are configured as a common search space for the first type terminal to perform a predetermined operation.

[0174] In one embodiment, A CORESET associated with a search space for paging monitoring set for the second type terminal is set as a CORESET associated with a search space for paging monitoring of the first type terminal; A CORESET associated with a search space for monitoring system messages set for a second type terminal is set as a CORESET associated with a search space for monitoring system messages of a first type terminal; A search space for paging monitoring set for the second type terminal is set as a search space for paging monitoring of the first type terminal; and setting the search space for monitoring system messages set for the second type terminal as the search space for monitoring system messages of the first type terminal.

[0175] In some embodiments, the additional common CORESET is configured as a CORESET associated with a search space for RAR monitoring of the first type of terminal; A common control resource set (CORESET) 0 is set as a CORESET associated with a search space for RAR monitoring of the first type terminal; The additional common search space is set as a search space for RAR monitoring of the first type terminal; and and setting the common search space 0 as the search space for RAR monitoring of the first type terminal.

[0176] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0177] As shown in FIG. 8 , an embodiment of the present disclosure provides a resource configuration device, which includes: a transmitting module 81 configured to transmit downlink control channel common configuration information configured for an initial bandwidth portion (BWP) to a first type terminal; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0178] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0179] As shown in FIG. 9 , in the disclosed embodiment, a resource configuration device is provided, and the device includes: a receiving module 91 configured to receive downlink control channel common configuration information configured for an initial bandwidth portion (BWP) sent by an access network device to a first type terminal; The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: Additional Common Control Resource Sets (CORESETs), and additional common search spaces; Common Control Resource Set (CORESET) 0, Common Search Space 0.

[0180] It should be noted that those skilled in the art can understand that the methods provided by the embodiments of the present disclosure may be performed alone or together with some methods of the embodiments of the present disclosure or some methods of the related art.

[0181] An embodiment of the present disclosure provides a communication device, the communication device comprising: a processor; a memory for storing instructions executable by the processor; The processor, when executing the executable instructions, is configured to implement the method of any embodiment of the present disclosure.

[0182] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to retain information stored thereon even after the communication device is powered off.

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

[0184] An embodiment of the present disclosure provides a computer storage medium having a computer-executable program stored thereon, which, when executed by a processor, implements the method of any embodiment of the present disclosure.

[0185] The specific manner in which each module of the apparatus in the above embodiment performs the operations has already been described in detail in the embodiment relating to the method, so it will not be described in detail here.

[0186] As shown in FIG. 10, one embodiment of the present disclosure provides a structure of a terminal.

[0187] Referring to the terminal 800 shown in FIG. 10 , this embodiment provides a terminal 800, which may specifically be a mobile phone, a computer, a digital broadcast terminal, a message transceiver, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0188] Referring to FIG. 10 , the terminal 800 may include one or more 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.

[0189] The processing component 802 typically controls the overall operation of the terminal 800, such as operations related to display, phone calls, data communications, camera operation, and recording operations. The processing component 802 may include one or more processors 820 for executing instructions to complete all or some of the steps of the above-described methods. The processing component 802 may also include one or more modules to facilitate interaction with other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

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

[0191] The power component 806 provides power for various components of the terminal 800. The power component 806 can include a power management system, one or more power sources, and other components related to generating, managing, and allocating power for the terminal 800.

[0192] The multimedia component 808 includes a screen that provides an output interface between the terminal 800 and a user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel may include one or more touch sensors to detect touches, slides, and gestures on the touch panel. The touch sensors may detect not only the boundaries of a touch or slide operation but also 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 terminal 800 is in an operation mode, such as a photo 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 may have a focal length and optical zoom capability.

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

[0194] The I / O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, volume buttons, a start button, and a lock button.

[0195] The sensor component 814 includes one or more sensors to provide various aspects of status assessment for the terminal 800. For example, the sensor component 814 can detect the on / off state of the terminal 800, the relative positioning of components, such as the display and keypad of the terminal 800, and can further detect changes in the position of the terminal 800 or one of its components, the presence or absence of contact between the user and the terminal 800, the orientation or acceleration / deceleration of the terminal 800, and temperature changes of the terminal 800. The sensor component 814 can also include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor component 814 can further include an optical sensor, such as a CMOS or CCD image sensor used for imaging applications. In some embodiments, the sensor component 814 can further include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0196] 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 WiFi, 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 further includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

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

[0198] In an exemplary embodiment, a non-transitory computer-readable storage medium containing instructions, such as a memory 804 containing instructions, may be provided, which may be executed by a processor 820 of the terminal 800 to complete the method. For example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, or an optical data storage device.

[0199] As shown in FIG. 11, one embodiment of the present disclosure illustrates the structure of a base station. For example, base station 900 may be provided as a network-side device. Referring to FIG. 11, base station 900 includes a processing component 922 including one or more processors and memory resources represented by memory 932 for storing instructions, such as application programs, executed by processing component 922. The application programs stored in memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, processing component 922 is configured to execute instructions to perform any of the methods described above that are applicable to the base station.

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

[0201] Those skilled in the art will readily appreciate other embodiments of the present disclosure after studying the specification and practicing the invention disclosed herein. This disclosure is intended to cover any modifications, uses, or adaptations of the present invention, which modifications, uses, or adaptations follow the general principles of the present invention and include common general knowledge or customary technical means in the art that are not disclosed in this disclosure. The specification and examples are considered to be exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0202] It should be understood that the present invention is not limited to the exact construction described above and illustrated in the drawings, and various modifications and variations can be made without departing from the scope of the present invention, which is limited only by the scope of the appended claims.

Claims

1. 1. A resource configuration method performed by an access network device, comprising: transmitting downlink control channel common configuration information configured for an initial bandwidth portion (BWP); The downlink control channel common configuration information is used to indicate a predetermined resource for a first type terminal to perform a predetermined operation, and the predetermined resource includes: an additional common control resource set (CORESET); additional common search spaces; A common control resource set (CORESET) 0; a common search space 0; If the initial BWP does not include the common control resource set (CORESET) 0, the CORESET and / or common search space 0 configured for the second type terminal is set as the CORESET and / or common search space 0 for performing at least one of receiving SIB1, receiving other system messages, and paging monitoring by the first type terminal; The first type terminal is a Redcap terminal, and the second type terminal is a non-Redcap terminal other than the Redcap terminal; A resource setting method comprising:

2. 2. The resource setting method of claim 1, wherein in response to the initial BWP not including the entire CORESET0, the bandwidth of the additional common CORESET does not need to be included within the bandwidth range of the CORESET0.

3. The additional common CORESET is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; the additional common search space is set as a common search space for performing the predetermined operation by the first type terminal; The CORESET0 is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; the common search space 0 being set as a common search space for performing the predetermined operation by the first type terminal; 2. The resource setting method according to claim 1, wherein:

4. 4. The resource configuration method of claim 3, wherein the predetermined resources further include resources configured for a second type terminal in a predetermined message, the predetermined message including at least one of an MIB and an SIB1, the resources configured for the second type terminal including at least one of a resource for paging monitoring, a resource for monitoring a system message, and a resource for RAR monitoring, and the resources configured for the second type terminal are configured as a common search space for performing the predetermined operation by the first type terminal.

5. A CORESET associated with a search space for paging monitoring configured for the second type terminal is set as a CORESET associated with a search space for paging monitoring of the first type terminal; A CORESET associated with a search space for monitoring system messages set for the second type terminal is set as a CORESET associated with a search space for monitoring system messages of the first type terminal; A search space for paging monitoring set for the second type terminal is set as a search space for paging monitoring of the first type terminal; and a search space for monitoring system messages set for the second type terminal is set as a search space for monitoring system messages of the first type terminal. The resource configuration method of claim 4, further comprising at least one of:

6. The resource configuration method according to any one of claims 1 to 5, 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.

7. 6. The resource setting method according to claim 1, wherein if the initial BWP set for a second type terminal includes the CORESET0, the CORESET0 includes an additional common control resource set set for the second type terminal.

8. A resource setting method according to any one of claims 1 to 5, characterized in that, when the initial BWP set for a second type terminal includes the CORESET0, there is an overlap in bandwidth between the initial BWP set for the second type terminal and the initial BWP of the first type terminal.

9. A resource configuration method performed by a first type terminal, comprising: receiving downlink control channel common configuration information configured for an initial bandwidth portion (BWP); The downlink control channel common configuration information is used to indicate a predetermined resource for the first type terminal to perform a predetermined operation, and the predetermined resource includes: an additional common control resource set (CORESET); additional common search spaces; A common control resource set (CORESET) 0; a common search space 0; If the initial BWP does not include the common control resource set (CORESET) 0, perform at least one of receiving SIB1, receiving other system messages, and paging monitoring using a CORESET and / or a common search space 0 configured for a second type terminal; The resource configuration method, wherein the first type terminal is a Redcap terminal, and the second type terminal is a non-Redcap terminal other than the Redcap terminal.

10. 10. The resource setting method of claim 9, wherein in response to the initial BWP not including the entire CORESET0, the bandwidth of the additional common CORESET does not need to be included within the bandwidth range of the CORESET0.

11. The additional common CORESET is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; the additional common search space is set as a common search space for performing the predetermined operation by the first type terminal; The CORESET0 is set as a CORESET associated with a common search space for performing the predetermined operation by the first type terminal; and the common search space 0 is set as a common search space for performing the predetermined operation by the first type terminal.

12. 12. The resource configuration method of claim 11, wherein the predetermined resources further include resources configured for a second type terminal in a predetermined message, the predetermined message including at least one of an MIB and an SIB1, the resources configured for the second type terminal including at least one of a resource for paging monitoring, a resource for monitoring a system message, and a resource for RAR monitoring, and the resources configured for the second type terminal are configured as a common search space for performing the predetermined operation by the first type terminal.

13. A CORESET associated with a search space for paging monitoring configured for the second type terminal is set as a CORESET associated with a search space for paging monitoring of the first type terminal; A CORESET associated with a search space for monitoring system messages set for the second type terminal is set as a CORESET associated with a search space for monitoring system messages of the first type terminal; A search space for paging monitoring set for the second type terminal is set as a search space for paging monitoring of the first type terminal; and a search space for monitoring system messages configured for the second type terminal is configured as a search space for monitoring system messages of the first type terminal. The resource configuration method of claim 12, further comprising at least one of:

14. The resource configuration method according to any one of claims 9 to 13, 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.

15. 14. The resource setting method according to claim 9, wherein if the initial BWP set for a second type terminal includes the CORESET0, the CORESET0 includes an additional common control resource set set for the second type terminal.

16. A resource setting method according to any one of claims 9 to 13, characterized in that, when the initial BWP set for a second type terminal includes the CORESET0, there is an overlap in bandwidth between the initial BWP set for the second type terminal and the initial BWP of the first type terminal.

17. A resource setting device, a transmitting module configured to transmit downlink control channel common configuration information configured for an initial bandwidth portion (BWP); The downlink control channel common configuration information is used to indicate a predetermined resource for a first type terminal to perform a predetermined operation, and the predetermined resource includes: an additional common control resource set (CORESET); additional common search spaces; A common control resource set (CORESET) 0; a common search space 0; If the initial BWP does not include the common control resource set (CORESET) 0, the CORESET and / or common search space 0 configured for the second type terminal is set as the CORESET and / or common search space 0 for performing at least one of receiving SIB1, receiving other system messages, and paging monitoring by the first type terminal; A resource setting device, characterized in that the first type terminal is a Redcap terminal, and the second type terminal is a non-Redcap terminal other than the Redcap terminal.

18. A resource setting device, a receiving module configured to receive downlink control channel common configuration information configured for an initial bandwidth portion (BWP); The downlink control channel common configuration information is used to indicate a predetermined resource for a first type terminal to perform a predetermined operation, and the predetermined resource includes: an additional common control resource set (CORESET); additional common search spaces; A common control resource set (CORESET) 0; a common search space 0; If the initial BWP does not include the common control resource set (CORESET) 0, perform at least one of receiving SIB1, receiving other system messages, and paging monitoring using a CORESET and / or a common search space 0 configured for a second type terminal; A resource setting device, characterized in that the first type terminal is a Redcap terminal, and the second type terminal is a non-Redcap terminal other than the Redcap terminal.

Images