WO2023197274A1 - 资源配置的方法、装置、通信设备及存储介质 - Google Patents
资源配置的方法、装置、通信设备及存储介质 Download PDFInfo
- Publication number
- WO2023197274A1 WO2023197274A1 PCT/CN2022/086930 CN2022086930W WO2023197274A1 WO 2023197274 A1 WO2023197274 A1 WO 2023197274A1 CN 2022086930 W CN2022086930 W CN 2022086930W WO 2023197274 A1 WO2023197274 A1 WO 2023197274A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- search space
- type terminal
- public
- coreset
- monitoring
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 98
- 230000006854 communication Effects 0.000 title claims description 42
- 238000004891 communication Methods 0.000 title claims description 41
- 238000012544 monitoring process Methods 0.000 claims description 223
- 230000004044 response Effects 0.000 claims description 28
- 101150096310 SIB1 gene Proteins 0.000 claims description 27
- 238000013468 resource allocation Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 29
- 238000012545 processing Methods 0.000 description 12
- 238000007726 management method Methods 0.000 description 11
- 238000010295 mobile communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 101000687448 Homo sapiens REST corepressor 1 Proteins 0.000 description 1
- 102100024864 REST corepressor 1 Human genes 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 101150000582 dapE gene Proteins 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and in particular, to a resource allocation method, device, communication equipment and storage medium.
- Redcap Reduced capability
- eMBB enhanced Mobile Broadband
- This type of terminal usually needs to meet the following requirements: 1. Low cost and low complexity; 2. A certain degree of coverage enhancement; 3. Power saving.
- bandwidth part (BWP, Bandwidth Part) is defined.
- BWP Bandwidth Part
- the embodiments of the present disclosure disclose a resource configuration method, device, communication device, and storage medium.
- a resource configuration method is provided, wherein the method is executed by an access network device, and the method includes:
- the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations; the predetermined resources include at least one of the following:
- the predetermined operation includes at least one of the following:
- Random access responds to RAR listening operations
- the identifier of the additional public CORESET is different or the same as the identifier of the public CORESET configured for the second type of terminal; and/or, the identifier of the additional public search space is the same as the identifier of the additional public CORESET configured for the second type of terminal.
- the identifiers of the public search spaces are different or the same.
- the bandwidth of the additional public CORESET in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional public CORESET is not included in the bandwidth range of CORESET0.
- At least one of the following is included:
- the additional public CORESET is configured as a CORESET associated with a public search space for the first type terminal to perform the predetermined operation
- the additional public search space is configured as a public search space for the first type terminal to perform the predetermined operation
- the CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform the predetermined operation
- the public search space 0 is configured as a public search space for the first type terminal to perform the predetermined operation.
- the predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include For at least one of paging monitoring, system message monitoring and RAR monitoring resources; the resources configured for the second type terminal are configured as a common search space for the first type terminal to perform the predetermined operation.
- At least one of the following is included:
- the CORESET associated with the search space used for paging monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for paging monitoring for the first type terminal;
- the CORESET associated with the search space configured for the second type terminal for system message monitoring is configured as the CORESET associated with the search space used for system message monitoring for the first type terminal;
- the search space configured for the second type terminal for paging monitoring is configured as the search space used for the first type terminal for paging monitoring;
- the search space configured for the second type terminal for system message monitoring is configured as the search space used for the first type terminal for system message monitoring.
- the additional public CORESET is configured as a CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the common control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the additional public search space is configured as a search space used by the first type terminal for RAR monitoring.
- the public search space 0 is configured as a search space used by the first type terminal for RAR monitoring.
- a resource configuration method is provided, wherein the method is executed by a first type terminal, and the method includes:
- the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations; the predetermined resources include at least one of the following:
- the predetermined operation includes at least one of the following:
- Random access responds to RAR listening operations
- the identifier of the additional public CORESET is different or the same as the identifier of the public CORESET configured for the second type of terminal; and/or, the identifier of the additional public search space is the same as the identifier of the additional public CORESET configured for the second type of terminal.
- the identifiers of the public search spaces are different or the same.
- the bandwidth of the additional public CORESET in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional public CORESET is not included in the bandwidth range of CORESET0.
- At least one of the following is included:
- the additional public CORESET is configured as a CORESET associated with a public search space for the first type terminal to perform the predetermined operation
- the additional public search space is configured as a public search space for the first type terminal to perform the predetermined operation
- the CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform the predetermined operation
- the public search space 0 is configured as a public search space for the first type terminal to perform the predetermined operation.
- the predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include For at least one of paging monitoring, system message monitoring and RAR monitoring resources; the resources configured for the second type terminal are configured as a common search space for the first type terminal to perform the predetermined operation.
- At least one of the following is included:
- the CORESET associated with the search space used for paging monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for paging monitoring for the first type terminal;
- the CORESET associated with the search space configured for the second type terminal for system message monitoring is configured as the CORESET associated with the search space used for system message monitoring for the first type terminal;
- the search space configured for the second type terminal for paging monitoring is configured as the search space used for the first type terminal for paging monitoring;
- the search space configured for the second type terminal for system message monitoring is configured as the search space used for the first type terminal for system message monitoring.
- the additional public CORESET is configured as a CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the common control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the additional public search space is configured as a search space used by the first type terminal for RAR monitoring.
- the public search space 0 is configured as a search space used by the first type terminal for RAR monitoring.
- a device for resource configuration wherein the device includes:
- a sending module configured to send downlink control channel public configuration information configured for the initial bandwidth part BWP to the first type terminal;
- the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations; the predetermined resources include at least one of the following:
- a device for resource configuration wherein the device includes:
- a receiving module configured to receive the downlink control channel public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal;
- the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations; the predetermined resources include at least one of the following:
- a communication device includes:
- memory for storing instructions executable by the processor
- the processor is configured to implement the method described in any embodiment of the present disclosure when running the executable instructions.
- a computer storage medium stores a computer executable program.
- the executable program is executed by a processor, the method described in any embodiment of the present disclosure is implemented.
- the downlink control channel public configuration information configured for the initial bandwidth part BWP is sent to the first type terminal; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform a predetermined operation.
- Predetermined resources; the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space0.
- Figure 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment.
- Figure 2 is a schematic flowchart of a resource configuration method according to an exemplary embodiment.
- Figure 3 is a schematic flowchart of a resource configuration method according to an exemplary embodiment.
- Figure 4 is a schematic flowchart of a resource configuration method according to an exemplary embodiment.
- Figure 5 is a schematic flowchart of a resource configuration method according to an exemplary embodiment.
- Figure 6 is a schematic flowchart of a resource configuration method according to an exemplary embodiment.
- Figure 7 is a schematic flowchart of a resource configuration method according to an exemplary embodiment.
- Figure 8 is a schematic structural diagram of a resource configuration device according to an exemplary embodiment.
- Figure 9 is a schematic structural diagram of a resource configuration device according to an exemplary embodiment.
- Figure 10 is a schematic structural diagram of a terminal according to an exemplary embodiment.
- Figure 11 is a block diagram of a base station according to an exemplary embodiment.
- first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
- first information may also be called second information, and similarly, the second information may also be called first information.
- word “if” as used herein may be interpreted as "when” or "when” or "in response to determining.”
- this article uses the terms “greater than” or “less than” when characterizing the size relationship. However, those skilled in the art can understand that the term “greater than” also encompasses the meaning of “greater than or equal to”, and “less than” also encompasses the meaning of “less than or equal to”.
- FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
- the wireless communication system is a communication system based on mobile communication technology.
- the wireless communication system may include several user equipments 110 and several base stations 120.
- user equipment 110 may be a device that provides voice and/or data connectivity to a user.
- the user equipment 110 may communicate with one or more core networks via a Radio Access Network (RAN).
- RAN Radio Access Network
- the user equipment 110 may be an Internet of Things user equipment, such as a sensor device, a mobile phone, and a computer with an Internet of Things user equipment. , for example, it can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device.
- the user equipment 110 may also be equipment of an unmanned aerial vehicle.
- the user equipment 110 may also be a vehicle-mounted device, for example, it may be an on-board computer with a wireless communication function, or a wireless user equipment connected to an external on-board computer.
- the user equipment 110 may also be a roadside device, for example, it may be a streetlight, a signal light or other roadside device with a wireless communication function.
- the base station 120 may be a network-side device in a wireless communication system.
- the wireless communication system can be the 4th generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as the Long Term Evolution (LTE) system; or the wireless communication system can also be a 5G system, Also called new air interface system or 5G NR system.
- the wireless communication system may also be a next-generation system of the 5G system.
- the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network).
- the base station 120 may be an evolved base station (eNB) used in the 4G system.
- the base station 120 may also be a base station (gNB) that adopts a centralized distributed architecture in the 5G system.
- eNB evolved base station
- gNB base station
- the base station 120 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
- the centralized unit is equipped with a protocol stack including the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control protocol (Radio Link Control, RLC) layer, and the Media Access Control (Media Access Control, MAC) layer; distributed
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Media Access Control
- the unit is provided with a physical (Physical, PHY) layer protocol stack, and the embodiment of the present disclosure does not limit the specific implementation of the base station 120.
- a wireless connection may be established between the base station 120 and the user equipment 110 through a wireless air interface.
- the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
- the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
- an E2E (End to End, end-to-end) connection can also be established between user equipments 110 .
- V2V vehicle to vehicle, vehicle to vehicle
- V2I vehicle to infrastructure, vehicle to roadside equipment
- V2P vehicle to pedestrian, vehicle to person
- the above user equipment can be considered as the terminal equipment of the following embodiments.
- the above-mentioned wireless communication system may also include a network management device 130.
- the network management device 130 may be a core network device in a wireless communication system.
- the network management device 130 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME).
- the network management device can also be other core network devices, such as serving gateway (Serving GateWay, SGW), public data network gateway (Public Data Network GateWay, PGW), policy and charging rules functional unit (Policy and Charging Rules) Function, PCRF) or Home Subscriber Server (HSS), etc.
- serving gateway Serving GateWay, SGW
- public data network gateway Public Data Network GateWay, PGW
- Policy and Charging Rules Policy and Charging Rules
- PCRF Policy and Charging Rules
- HSS Home Subscriber Server
- the embodiments of the present disclosure enumerate multiple implementations to clearly describe the technical solutions of the embodiments of the present disclosure.
- the multiple embodiments provided in the embodiments of the present disclosure can be executed alone or in combination with the methods of other embodiments in the embodiments of the present disclosure. They can also be executed alone or in combination. It is then executed together with some methods in other related technologies; the embodiments of the present disclosure do not limit this.
- MTC Machine Type Communication
- NB-IoT Narrow Band Internet of Things
- NB-IoT can only support a maximum rate of several hundred kbits
- MTC can only support a maximum rate of several Mbits.
- IoT services for example, the popularity of video surveillance, smart home, wearable devices and industrial sensing monitoring services. These services usually require rates of tens to 100M and also have relatively high requirements on latency. Therefore, MTC and NB-IoT technologies in the fourth generation of mobile communication technology are difficult to meet the requirements. Based on this situation, there is a requirement to design a new terminal type in the fifth-generation mobile communication technology 5G new air interface to cover this mid-range IoT device.
- this new terminal type is called reduced capability terminal (RedCap, Reduced capability UE) or NR-lite for short.
- RedCap based on 5G NR-lite usually needs to meet the following requirements: low cost, low complexity; a certain degree of coverage enhancement; power saving.
- the New Radio (NR, New Radio) system needs to be modified to meet the requirements of NR-lite.
- the radio frequency bandwidth of NR-IoT can be limited, for example, the radio frequency bandwidth can be limited to 20 MHz.
- the size of the NR-lite buffer can be limited, thereby limiting the size of each received transmission block, and so on.
- possible optimization directions are to simplify the communication process, reduce the number of times NR-lite users detect downlink control channels, etc.
- the information element (IE) field PDCCH-ConfigCommon is used to configure the cell-specific physical downlink control channel (PDCCH, Physical Downlink Control Channel) provided in the system information block (SIB, system information block) and dedicated signaling. parameter.
- PDCH Physical Downlink Control Channel
- SIB system information block
- commonControlResourceSet is an additional set of common control resources that can be configured and used in any common or terminal-specific search space. If the network is configured with this field, it will use a non-zero ControlResourceSetId for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is included in the bandwidth of the control resource set CORESET#0.
- the parameters of public CORESET#0 may be used in any public or terminal-specific search space.
- a separate initial BWP for the downlink Random Access Response (RAR) can be configured in SIB1 for the Redcap terminal.
- the initial BWP may also be an initial BWP used for paging. There is no definition yet on how to configure the public search space on this initial BWP.
- this embodiment provides a resource configuration method, where the method is executed by the access network device, and the method includes:
- Step 21 Send the physical downlink control channel PDCCH public configuration information configured for the initial bandwidth part BWP to the first type terminal;
- the downlink control channel public configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include at least one of the following:
- the first type terminal and the second type terminal involved in the present disclosure may be, but are not limited to, mobile phones, wearable devices, vehicle-mounted terminals, roadside units (RSU, Road Side Unit), smart home terminals, industrial sensors equipment and/or medical equipment, etc.
- the first type terminal and the second type terminal are different types of terminals.
- the first type terminal may be a Redcap terminal
- the second type terminal may be other non-Redcap terminals other than the Redcap terminal.
- the access network equipment involved in this disclosure may be a base station.
- the base station may be various types of base stations, for example, a base station of a fifth generation mobile communication (5G) network or other evolved base stations.
- 5G fifth generation mobile communication
- a downlink initial BWP is configured for the first type terminal; PDCCH public configuration information for the initial BWP configuration is sent to the first type terminal; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform a predetermined operation Predetermined resources; the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space 0.
- the PDCCH common configuration information can be carried in the PDCCH common configuration (PDCCH-configCommon) field of the RedCap-specific initial downlink BWP configuration (RedCap-specific initial DL BWP configuration) or the PDCCH common system information block configuration (PDCCH-configCommonSIB ) field.
- the frequency domain resource information of the PDCCH and the number of orthogonal frequency division multiplexing (OFDM, Orthogonal Frequency Division Multiplexing) symbols occupied in the time domain are encapsulated in CORESET; the PDCCH starting OFDM symbol, monitoring period, and associated Information such as CORESET is encapsulated in the search space.
- the public search space is mainly used during access and cell switching, for example, for monitoring related control information such as broadcast control channel BCCH, paging, RAR, etc.
- RAR and other related messages are messages responding to random access, including msg2, msg4, msgB, etc.
- the physical downlink control channel PDCCH common configuration information configured for the initial bandwidth part BWP is sent to the first type terminal; wherein the downlink control channel common configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space0.
- the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.
- the identity of the additional public CORESET is different from the identity of the public CORESET configured for the second type terminal. It should be noted that the identifier of the additional public CORESET may not be 0.
- the identity of the additional public search space is different from the identity of the public search space configured for the second type terminal. It should be noted that the identifier of the additional public search space may not be 0.
- the identity of the additional public CORESET is the same as the identity of the public CORESET configured for the second type terminal. It should be noted that the identifier of the additional public CORESET may not be 0.
- the identity of the additional public search space is the same as the identity of the public search space configured for the second type terminal. It should be noted that the identifier of the additional public search space may not be 0.
- an additional public CORESET or an additional public search space may be configured; wherein the bandwidth of the additional public CORESET does not need to be included in the bandwidth range of CORESET0.
- the CORESET associated with all or part of the common search space for the first type terminal may be configured based on the additional public CORESET.
- all or part of the public search space for the first type terminal may be configured based on the additional public search space.
- the CORESET associated with all search spaces here can be understood as the CORESET associated with the search space required for the terminal to perform all scheduled operations. All scheduled operations may include: random access response RAR monitoring operations, paging monitoring operations , and the operation of system message monitoring, etc., however, it is not limited to the above operations.
- the CORESET associated with the partial search space can be understood as the CORESET associated with the search space required to perform part of the predetermined operation, and the partial predetermined operation is a part of all predetermined operations.
- the entire search space here can be understood as the search space required by the terminal to perform all scheduled operations. All scheduled operations can include: random access response RAR monitoring operations, paging monitoring operations, and system message monitoring operations, etc. , however, is not limited to the above operations.
- Partial search space can be understood as the search space required to perform partial predetermined operations, and partial predetermined operations are part of all predetermined operations.
- the additional public CORESET is configured as a common search space associated CORESET for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.
- the additional common search space is configured as a common search space for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.
- the physical downlink control channel PDCCH common configuration information configured for the initial bandwidth part BWP is sent to the first type terminal; wherein the downlink control channel common configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include at least one of the following: an additional common control resource set CORESET; and an additional public search space.
- the additional public CORESET is configured as a CORESET associated with the public search space used by the first type terminal to perform all predetermined operations; and/or, the additional public search space is configured as a CORESET associated with the first type terminal to perform all predetermined operations.
- Public search space is configured as a CORESET associated with the first type terminal to perform all predetermined operations.
- the common control resource set CORESET0 is configured as a common search space associated CORESET for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.
- the common control resource set CORESET0 may be used by the search space configured on the initial BWP configured for the first type terminal and the initial BWP configured for the second type terminal.
- the common control resource set CORESET0 may be used by the search space configured on the initial BWP configured for the first type terminal and the initial BWP configured for the second type terminal.
- the bandwidth range of the initial BWP configured for the first type of terminal does not include the bandwidth of the common control resource set CORESET0.
- the public search space 0 is configured as a common search space for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.
- the physical downlink control channel PDCCH common configuration information configured for the initial bandwidth part BWP is sent to the first type terminal; wherein the downlink control channel common configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include at least one of the following: a common control resource set CORESET0; and a common search space 0.
- the public CORESET0 is configured as a CORESET associated with the public search space used by the first type terminal to perform all predetermined operations; and/or, the public search space 0 is configured as a common search space used for the first type terminal to perform all predetermined operations.
- the common search space 0 may be used by search spaces configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal.
- the common search space 0 may be used by search spaces configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal.
- the bandwidth range of the initial BWP configured for the first type terminal does not include the bandwidth of the common control resource set CORESET0.
- the additional public CORESET is configured as a CORESET associated with a public search space for the first type terminal to perform the predetermined operation; and/or the additional public search space is configured as a common search space for the first type terminal to perform the predetermined operation; and/or, the CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform the predetermined operation; and /Or, the public search space 0 is configured as a public search space for the first type terminal to perform the predetermined operation.
- the additional public CORESET is configured as a CORESET associated with the public search space for the first type terminal to perform part of the predetermined operation; and/or, the additional public search space is configured to be used for the first type terminal to perform part of the predetermined operation.
- a common search space for part of the predetermined operations; and/or, CORESET0 is configured as a CORESET associated with a common search space for the first type terminal to perform part of the predetermined operations; and/or, the public search space 0 is configured for the first type A public search space where the terminal performs some predetermined operations.
- the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.
- the physical downlink control channel PDCCH common configuration information configured for the initial bandwidth part BWP is sent to the first type terminal; wherein the downlink control channel common configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space0.
- the additional public CORESET is configured as a CORESET associated with the public search space used by the first type terminal to perform part of the predetermined operations; and/or, the additional public search space is configured as a CORESET associated with the first type terminal to perform part of the predetermined operations.
- Public search space; and/or, CORESET0 is configured as a CORESET associated with the public search space for the first type terminal to perform part of the predetermined operation; and/or, the public search space 0 is configured to be used for the first type terminal to perform part of the predetermined operation.
- CORESET0 and search space 0 can be configured in the master information block (MIB, Master Information Block), and other CORESET and/or search spaces with non-zero identifiers need to be configured in SIB1.
- CORESET1 and/or search space 1 are configured in SIB1.
- the predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include paging monitoring, system At least one of message listening and RAR listening resources; the resources configured for the second type terminal are configured as a common search space for the first type terminal to perform predetermined operations.
- MIB is configured with CORESET0 and/or search space 0 for the second type terminal; SIB1 is configured with additional CORESET x and/or additional search space CORESET x for the second type terminal, where x is not is 0, it can be 1, 2, etc.
- CORESET0 and/or search space 0 are configured in the MIB for the second type terminal for monitoring of SIB1;
- CORESET x and/or search space CORESET x are configured for the second type terminal in SIB1, where, x is not 0, it can be 1, 2, etc.
- the monitoring of Other SI, or the monitoring of paging; or the monitoring of RAR can be associated with the MIB configured for the second type terminal with CORESET0 and/or search space 0, or CORESET x and/or search space CORESET x; that is, for COREST
- the search space configuration can be associated to the MIB configuration CORESET0 and/or search space 0 or additional CORESET and/or additional search space configuration.
- the CORESET associated with the search space used for paging monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for paging monitoring for the first type terminal.
- the CORESET associated with the search space used for system message monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for system message monitoring for the first type terminal.
- the search space configured for paging monitoring for the second type terminal is configured as the search space used for paging monitoring for the first type terminal.
- the search space configured for the second type terminal for system message monitoring is configured as the search space used for the first type terminal for system message monitoring.
- the additional public CORESET configured for the second type terminal is configured as the search space associated CORESET used by the first type terminal for RAR listening;
- the common control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the additional public search space configured for the second type terminal is configured as the search space used by the first type terminal for RAR monitoring
- the public search space 0 is configured as a search space used by the first type terminal for RAR monitoring.
- the additional public CORESET or CORESE0 associated with the RAR search space configured for the second type terminal can be configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring, that is, the two are complex. use.
- different search spaces may be additionally configured for the first type terminal for RAR monitoring.
- the network will schedule random access response messages for different types of terminals in different search spaces.
- the RAR search space configured for the second type terminal requires Configure an additional public CORESET separately, for example, commonControlResourceSet-Redcap or an additional public CORESET with a different ID than the public CORESET ID attached to the initial BWP bandwidth of the first type of terminal, for example, additional public CORESET 2.
- the network will schedule random access response messages for different types of terminals on different initial BWPs.
- the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type terminal to configure an additional (or additional) public CORESET; the ID of the additional public CORESET can be the same as that configured for the second type terminal.
- the additional CORESET contained on the initial BWP may be the same or different.
- the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type of terminal to configure an additional public CORESET#2 or public CORESET-Redcap for RAR monitoring; while the paging message and system configured for the first type of terminal For message and other monitoring, you can still configure an additional public CORESET for the second type terminal, for example, an additional public CORESET#1 or CORSET0; this can avoid confusion.
- the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type of terminal is used to configure an additional public CORESET#1 for RAR monitoring; while the paging messages and system messages configured for the first type of terminal When listening, you can continue to configure a public CORESET0 for the second type terminal (assuming that the second type terminal does not use additional CORESET), so that confusion will not occur.
- the configuration of the second type terminal can be completely the same.
- system message monitoring and paging message monitoring can completely reuse the configuration of the second type terminal;
- RAR message monitoring can also completely reuse the configuration of the second type terminal, or the RAR search space can be separately configured with additional public CORESET, for example , commonControlResourceSet-Redcap or public CORESET1.
- the downlink control channel common configuration information configured for the initial bandwidth part BWP is sent to the first type terminal; where the downlink control channel common configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations; predetermined
- the resources include at least one of the following: additional common control resource set CORESET; additional common search space; common control resource set CORESET0; and common search space0.
- the corresponding PDCCH-configCommon configuration is as follows: CORESET0 and/or search space 0 are configured in the MIB.
- the CORESET0 and/or search space 0 are used to receive SIB1.
- the CORESET0 or search space 0 can also be used for other system message monitoring, paging message monitoring, RAR monitoring, etc. It should be noted that other system message monitoring, paging message monitoring and RAR monitoring resources can also be associated with CORESET1 and search space 1 configured in SIB1.
- the corresponding PDCCH-configCommon configuration is as follows:
- SIB1 monitoring is at CORESET0 and SS0, and there is no limit for other types of monitoring
- the first type terminal configuration and the second type terminal configuration may be exactly the same;
- the search space monitored by the RAR of the first type terminal may be different from the search space configured for the second type terminal, for example, search space 1, etc.
- the RAR's listening CORESET may adopt an additional public CORESET, for example, CORESET1, etc.
- the corresponding PDCCH-configCommon configuration is as follows:
- CORESET0 and/or search space 0 are configured in the MIB.
- the CORESET0 and/or search space 0 are used for system message monitoring;
- the resources for paging message monitoring and RAR monitoring can also be associated with CORESET1 and search space 1 configured in SIB1.
- the corresponding PDCCH-configCommon configuration is as follows:
- the RAR monitoring search space may adopt an additional public search space configured on the downlink initial BWP configured by the first type terminal, for example, search space 2, etc.
- search space for RAR monitoring can be configured on the downlink initial BWP of the first type of terminal, and additional public CORESET, for example, CORESET2, etc. can be used.
- the corresponding PDCCH-configCommon configuration is as follows: CORESET0 and/or search space 0 are configured in the MIB.
- the CORESET0 and/or search space 0 are used to receive SIB1.
- the CORESET0 or search space 0 can also be used for other system message monitoring, paging message monitoring, RAR monitoring, etc. It should be noted that other system message monitoring, paging message monitoring and RAR monitoring resources can also be associated with CORESET1 and search space 1 configured in SIB1.
- the corresponding PDCCH-configCommon configuration is as follows:
- the first type terminal configuration and the second type terminal configuration may be exactly the same;
- the search space monitored by the RAR of the first type terminal may be different from the search space configured for the second type terminal, for example, search space 1, etc.
- the RAR's listening CORESET may adopt additional public CORESET, for example, CORESET1, etc. (the physical resource location may be the same as or different from that configured for the first type of terminal)
- the identifier of the additional public CORESET is different or the same as the identifier of the public CORESET configured for the second type of terminal; and/or, the identifier of the additional public search space is the same as the identifier of the public search space configured for the second type of terminal.
- the logos are different or the same.
- this embodiment provides a resource configuration method, where the method is executed by the access network device, and the method includes:
- Step 31 Send the physical downlink control channel PDCCH public configuration information configured for the initial bandwidth part BWP to the first type terminal; where the downlink control channel public configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations; the predetermined resources include At least one of the following: additional common control resource set CORESET; additional common search space; common control resource set CORESET0; and common search space0.
- the identifier of the additional public CORESET is different or the same as the identifier of the public CORESET configured for the second type terminal; and/or, the identifier of the additional public search space is different from the identifier of the public search space configured for the second type terminal, or same.
- the bandwidth of the additional public CORESET in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional public CORESET is not included in the bandwidth range of CORESET0.
- the additional public CORESET is configured as a CORESET associated with the public search space for the first type terminal to perform the predetermined operation
- the additional public search space is configured as a public search space for the first type terminal to perform a predetermined operation
- CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform predetermined operations
- the public search space 0 is configured as a public search space for the first type terminal to perform predetermined operations.
- this embodiment provides a resource configuration method, where the method is executed by the access network device, and the method includes:
- Step 41 Send the physical downlink control channel PDCCH public configuration information configured for the initial bandwidth part BWP to the first type terminal; where the downlink control channel public configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include At least one of the following: additional common control resource set CORESET; additional common search space; common control resource set CORESET0; and common search space0.
- the predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include paging monitoring, system message monitoring and RAR. At least one of the monitored resources; the resource configured for the second type terminal is configured as a common search space for the first type terminal to perform a predetermined operation.
- At least one of the following is included:
- the CORESET associated with the search space used for paging monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for paging monitoring for the first type terminal;
- the CORESET associated with the search space configured for the second type terminal for system message monitoring is configured as the CORESET associated with the search space used for system message monitoring for the first type terminal;
- the search space configured for paging monitoring for the second type terminal is configured as the search space used for paging monitoring for the first type terminal;
- the search space configured for the second type terminal for system message monitoring is configured as the search space used for the first type terminal for system message monitoring.
- the additional public CORESET is configured as a CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the common control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the additional public search space is configured as a search space used by the first type terminal for RAR listening.
- the public search space 0 is configured as a search space used by the first type terminal for RAR monitoring.
- this embodiment provides a resource configuration method, wherein the method is executed by a first type terminal, and the method includes:
- Step 51 Receive the downlink control channel public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal;
- the downlink control channel public configuration information is used to instruct the first type terminal to perform predetermined resources for performing predetermined operations;
- the predetermined resources include at least one of the following:
- the first type terminal and the second type terminal involved in the present disclosure may be, but are not limited to, mobile phones, wearable devices, vehicle-mounted terminals, roadside units (RSU, Road Side Unit), smart home terminals, industrial sensors equipment and/or medical equipment, etc.
- the first type terminal and the second type terminal are different types of terminals.
- the first type terminal may be a Redcap terminal
- the second type terminal may be other non-Redcap terminals other than the Redcap terminal.
- the access network equipment involved in this disclosure may be a base station.
- the base station may be various types of base stations, for example, a base station of a fifth generation mobile communication (5G) network or other evolved base stations.
- 5G fifth generation mobile communication
- the PDCCH common configuration information can be carried in the PDCCH common configuration (PDCCH-configCommon) field of the RedCap-specific initial downlink BWP configuration (RedCap-specific initial DL BWP configuration) or the PDCCH common system information block configuration (PDCCH-configCommonSIB ) field.
- the frequency domain resource information of the PDCCH and the number of orthogonal frequency division multiplexing (OFDM, Orthogonal Frequency Division Multiplexing) symbols occupied in the time domain are encapsulated in CORESET; the PDCCH starting OFDM symbol, monitoring period, and associated Information such as CORESET is encapsulated in the search space.
- the public search space is mainly used during access and cell switching, for example, for monitoring related control information such as broadcast control channel BCCH, paging, RAR, etc.
- the physical downlink control channel PDCCH public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal is received; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform Predetermined resources for the predetermined operation;
- the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space 0.
- the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.
- the identity of the additional public CORESET is different from the identity of the public CORESET configured for the second type terminal. It should be noted that the identifier of the additional public CORESET may not be 0.
- the identity of the additional public search space is different from the identity of the public search space configured for the second type terminal. It should be noted that the identifier of the additional public search space may not be 0.
- the identity of the additional public CORESET is the same as the identity of the public CORESET configured for the second type terminal. It should be noted that the identifier of the additional public CORESET may not be 0.
- the identity of the additional public search space is the same as the identity of the public search space configured for the second type terminal. It should be noted that the identifier of the additional public search space may not be 0.
- the access network device can configure an additional public CORESET or an additional public search space; wherein, the bandwidth of the additional public CORESET does not need to be included in the bandwidth of CORESET0. within the range.
- the access network device may configure CORESET associated with all or part of the public search space for the first type terminal based on the additional public CORESET.
- the access network device may configure all or part of the public search space for the first type of terminal based on the additional public search space.
- the CORESET associated with all search spaces here can be understood as the CORESET associated with the search space required for the terminal to perform all scheduled operations. All scheduled operations may include: random access response RAR monitoring operations, paging monitoring operations , and the operation of system message monitoring, etc., however, it is not limited to the above operations.
- the CORESET associated with the partial search space can be understood as the CORESET associated with the search space required to perform part of the predetermined operation, and the partial predetermined operation is a part of all predetermined operations.
- the entire search space here can be understood as the search space required by the terminal to perform all scheduled operations. All scheduled operations can include: random access response RAR monitoring operations, paging monitoring operations, and system message monitoring operations, etc. , however, is not limited to the above operations.
- Partial search space can be understood as the search space required to perform partial predetermined operations, and partial predetermined operations are part of all predetermined operations.
- the additional public CORESET is configured as a common search space associated CORESET for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.
- the additional common search space is configured as a common search space for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.
- the physical downlink control channel PDCCH public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal is received; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform Predetermined resources for predetermined operations; the predetermined resources include at least one of the following: an additional common control resource set CORESET; and an additional public search space.
- the additional public CORESET is configured as a CORESET associated with the public search space used by the first type terminal to perform all predetermined operations; and/or, the additional public search space is configured as a CORESET associated with the first type terminal to perform all predetermined operations. Public search space.
- the common control resource set CORESET0 is configured as a common search space associated CORESET for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.
- the common control resource set CORESET0 may be used by the search space configured on the initial BWP configured for the first type terminal and the initial BWP configured for the second type terminal.
- the common control resource set CORESET0 may be used by the search space configured on the initial BWP configured for the first type terminal and the initial BWP configured for the second type terminal.
- the bandwidth range of the initial BWP configured for the first type of terminal does not include the bandwidth of the common control resource set CORESET0.
- the public search space 0 is configured as a common search space for the first type terminal to perform all predetermined operations.
- the predetermined operation includes at least one of the following: an operation of random access response RAR monitoring; an operation of paging monitoring; and an operation of system message monitoring.
- the physical downlink control channel PDCCH public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal is received; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform Predetermined resources for predetermined operations; the predetermined resources include at least one of the following: a common control resource set CORESET0; and a common search space 0.
- the public CORESET0 is configured as the CORESET associated with the common search space used by the first type terminal to perform all predetermined operations; and/or, the public search space 0 is configured as a common search space used for the first type terminal to perform all predetermined operations.
- the common search space 0 may be used by search spaces configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal.
- the common search space 0 may be used by search spaces configured on the initial BWP configured for the first type of terminal and the initial BWP configured for the second type of terminal.
- the bandwidth range of the initial BWP configured for the first type terminal does not include the bandwidth of the common control resource set CORESET0.
- the additional public CORESET is configured as a CORESET associated with a public search space for the first type terminal to perform the predetermined operation; and/or the additional public search space is configured as a common search space for the first type terminal to perform the predetermined operation; and/or, the CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform the predetermined operation; and /Or, the public search space 0 is configured as a public search space for the first type terminal to perform the predetermined operation.
- the additional public CORESET is configured as a CORESET associated with the public search space for the first type terminal to perform part of the predetermined operation; and/or, the additional public search space is configured to be used for the first type terminal to perform part of the predetermined operation.
- a common search space for part of the predetermined operations; and/or, CORESET0 is configured as a CORESET associated with a common search space for the first type terminal to perform part of the predetermined operations; and/or, the public search space 0 is configured for the first type A public search space where the terminal performs some predetermined operations.
- the predetermined operation includes at least one of the following: a random access response RAR monitoring operation; a paging monitoring operation; and a system message monitoring operation.
- the physical downlink control channel PDCCH public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal is received; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform Predetermined resources for the predetermined operation; the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space 0.
- the additional public CORESET is configured as a CORESET associated with the public search space used by the first type terminal to perform part of the predetermined operations; and/or, the additional public search space is configured as a CORESET associated with the first type terminal to perform part of the predetermined operations.
- Public search space; and/or, CORESET0 is configured as a CORESET associated with the public search space for the first type terminal to perform part of the predetermined operation; and/or, the public search space 0 is configured to be used for the first type terminal to perform part of the predetermined operation.
- CORESET0 and search space 0 can be configured in the master information block (MIB, Master Information Block), and other CORESET and/or search spaces with non-zero identifiers need to be configured in SIB1.
- CORESET0 and/or search space 0 are configured in SIB1.
- the predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include paging monitoring, system At least one of message listening and RAR listening resources; the resources configured for the second type terminal are configured as a common search space for the first type terminal to perform predetermined operations.
- MIB is configured with CORESET0 and/or search space 0 for the second type terminal;
- CORESET x and/or search space CORESET x is configured with SIB1 for the second type terminal, where x is not 0, and can It’s 1, 2, etc.
- the CORESET associated with the search space used for paging monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for paging monitoring for the first type terminal.
- the CORESET associated with the search space used for system message monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for system message monitoring for the first type terminal.
- the search space configured for paging monitoring for the second type terminal is configured as the search space used for paging monitoring for the first type terminal.
- the search space configured for the second type terminal for system message monitoring is configured as the search space used for the first type terminal for system message monitoring.
- the additional public CORESET or public control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the common control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the additional public search space is configured as a search space used by the first type terminal for RAR listening.
- the public search space 0 is configured as a search space used by the first type terminal for RAR monitoring.
- the additional public CORESET or CORESE0 associated with the RAR search space configured for the second type terminal can be configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring, that is, the two are complex. use.
- different search spaces may be additionally configured for the first type terminal for RAR monitoring.
- the network will schedule random access response messages for different types of terminals in different search spaces.
- the RAR search space configured for the second type terminal requires Configure an additional public CORESET separately, for example, commonControlResourceSet-Redcap or an additional public CORESET with a different ID than the public CORESET ID attached to the initial BWP bandwidth of the first type of terminal, for example, additional public CORESET 2.
- the network will schedule random access response messages for different types of terminals on different initial BWPs.
- the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type terminal to configure an additional (or additional) public CORESET; the ID of the additional public CORESET can be the same as that configured for the second type terminal.
- the additional CORESET included in the initial BWP may or may not be the same.
- the commonControlResourceSet in the PDCCH-ConfigCommon field needs to be extended for the first type of terminal to configure an additional public CORESET#2 or public CORESET-Redcap for RAR monitoring; while the paging message and system configured for the first type of terminal For message and other monitoring, you can still configure an additional public CORESET for the second type terminal, for example, an additional public CORESET#1 or CORSET0; this can avoid confusion.
- the commonControlResourceSet in the PDCCH-ConfigCommon field configured for the second type of terminal is used to configure an additional public CORESET#1 for RAR monitoring; while the paging messages and system messages configured for the first type of terminal When listening, you can continue to configure a public CORESET0 for the second type terminal (assuming that the second type terminal does not use additional CORESET), so that confusion will not occur.
- the configuration of the second type terminal can be completely the same.
- system message monitoring and paging message monitoring can completely reuse the configuration of the second type terminal;
- RAR message monitoring can also completely reuse the configuration of the second type terminal, or the RAR search space can be separately configured with additional public CORESET, for example , commonControlResourceSet-Redcap or public CORESET1.
- the identifier of the additional public CORESET is different or the same as the identifier of the public CORESET configured for the second type of terminal; and/or, the identifier of the additional public search space is the same as the identifier of the public search space configured for the second type of terminal.
- the logos are different or the same.
- this embodiment provides a resource configuration method, wherein the method is executed by a first type terminal, and the method includes:
- Step 61 Receive the physical downlink control channel PDCCH public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal; wherein the downlink control channel public configuration information is used to instruct the first type terminal to perform predetermined operations.
- Predetermined resources; the predetermined resources include at least one of the following: additional common control resource set CORESET; additional public search space; common control resource set CORESET0; and public search space 0.
- the identifier of the additional public CORESET is different or the same as the identifier of the public CORESET configured for the second type terminal; and/or, the identifier of the additional public search space is different from the identifier of the public search space configured for the second type terminal, or same.
- the bandwidth of the additional public CORESET in response to the bandwidth of the initial BWP not including the bandwidth of CORESET0, the bandwidth of the additional public CORESET is not included in the bandwidth range of CORESET0.
- the additional public CORESET is configured as a CORESET associated with the public search space for the first type terminal to perform the predetermined operation
- the additional public search space is configured as a public search space for the first type terminal to perform a predetermined operation
- CORESET0 is configured as a CORESET associated with the common search space for the first type terminal to perform predetermined operations
- the public search space 0 is configured as a public search space for the first type terminal to perform predetermined operations.
- this embodiment provides a resource configuration method, wherein the method is executed by a first type terminal, and the method includes:
- Step 71 Send the physical downlink control channel PDCCH public configuration information configured for the initial bandwidth part BWP to the first type terminal; where the downlink control channel public configuration information is used to instruct the first type terminal to perform predetermined resources for predetermined operations;
- the predetermined resources include At least one of the following: additional common control resource set CORESET; additional common search space; common control resource set CORESET0; and common search space0.
- the predetermined resources also include resources configured for the second type terminal in the predetermined message; the predetermined message includes at least one of the following: MIB and SIB1; the resources configured for the second type terminal include paging monitoring, system message monitoring and RAR. At least one of the monitored resources; the resource configured for the second type terminal is configured as a common search space for the first type terminal to perform a predetermined operation.
- At least one of the following is included:
- the CORESET associated with the search space used for paging monitoring configured for the second type terminal is configured as the CORESET associated with the search space used for paging monitoring for the first type terminal;
- the CORESET associated with the search space configured for the second type terminal for system message monitoring is configured as the CORESET associated with the search space used for system message monitoring for the first type terminal;
- the search space configured for paging monitoring for the second type terminal is configured as the search space used for paging monitoring for the first type terminal;
- the search space configured for the second type terminal for system message monitoring is configured as the search space used for the first type terminal for system message monitoring.
- the additional public CORESET is configured as a CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the common control resource set CORESET0 is configured as the CORESET associated with the search space used by the first type terminal for RAR monitoring;
- the additional public search space is configured as a search space for RAR listening by the first type of terminal.
- the public search space 0 is configured as a search space used by the first type terminal for RAR monitoring.
- an embodiment of the present disclosure provides a device for resource configuration, wherein the device includes:
- the sending module 81 is configured to send the downlink control channel common configuration information configured for the initial bandwidth part BWP to the first type terminal;
- the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations; the predetermined resources include at least one of the following:
- an embodiment of the present disclosure provides a device for resource configuration, wherein the device includes:
- the receiving module 91 is configured to receive the downlink control channel public configuration information for the initial bandwidth part BWP configuration sent by the access network device to the first type terminal;
- the downlink control channel common configuration information is used to indicate predetermined resources for the first type terminal to perform predetermined operations; the predetermined resources include at least one of the following:
- An embodiment of the present disclosure provides a communication device.
- the communication device includes:
- Memory used to store instructions executable by the processor
- the processor is configured to: when executing executable instructions, implement the method applied to any embodiment of the present disclosure.
- the processor may include various types of storage media, which are non-transitory computer storage media that can continue to memorize information stored on the communication device after the communication device is powered off.
- the processor can be connected to the memory through a bus, etc., and is used to read the executable program stored in the memory.
- An embodiment of the present disclosure also provides a computer storage medium, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method of any embodiment of the present disclosure is implemented.
- one embodiment of the present disclosure provides a structure of a terminal.
- the terminal 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc. .
- the terminal 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and communications component 816.
- Processing component 802 generally controls the overall operations of terminal 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
- the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method.
- processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components.
- processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
- Memory 804 is configured to store various types of data to support operations at device 800 . Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phonebook data, messages, pictures, videos, etc.
- Memory 804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
- SRAM static random access memory
- EEPROM electrically erasable programmable read-only memory
- EEPROM erasable programmable read-only memory
- EPROM Programmable read-only memory
- PROM programmable read-only memory
- ROM read-only memory
- magnetic memory flash memory, magnetic or optical disk.
- Power supply component 806 provides power to various components of terminal 800.
- Power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to terminal 800.
- Multimedia component 808 includes a screen that provides an output interface between terminal 800 and the user.
- the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
- the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. A touch sensor can not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
- multimedia component 808 includes a front-facing camera and/or a rear-facing camera.
- the front camera and/or the rear camera may receive external multimedia data.
- Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
- Audio component 810 is configured to output and/or input audio signals.
- audio component 810 includes a microphone (MIC) configured to receive external audio signals when terminal 800 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 804 or sent via communication component 816 .
- audio component 810 also includes a speaker for outputting audio signals.
- 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, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
- Sensor component 814 includes one or more sensors that provide various aspects of status assessment for terminal 800 .
- the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the terminal 800, the sensor component 814 can also detect the position change of the terminal 800 or a component of the terminal 800, the user The presence or absence of contact with the terminal 800, the terminal 800 orientation or acceleration/deceleration and the temperature change of the terminal 800.
- Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
- Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
- the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
- the communication component 816 is configured to facilitate wired or wireless communication between the terminal 800 and other devices.
- the terminal 800 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
- the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
- communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications.
- NFC near field communications
- the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
- RFID radio frequency identification
- IrDA infrared data association
- UWB ultra-wideband
- Bluetooth Bluetooth
- the terminal 800 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above method.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGA field programmable Gate array
- controller microcontroller, microprocessor or other electronic components are implemented for executing the above method.
- non-transitory computer-readable storage medium including instructions, such as a memory 804 including instructions, which can be executed by the processor 820 of the terminal 800 to complete the above method is also provided.
- non-transitory computer-readable storage media may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
- an embodiment of the present disclosure shows the structure of a base station.
- the base station 900 may be provided as a network side device.
- base station 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by memory 932 for storing instructions, such as application programs, executable by processing component 922.
- the application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions.
- the processing component 922 is configured to execute instructions to perform any of the foregoing methods applied to the base station.
- Base station 900 may also include a power supply 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 based on an operating system stored in memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本公开实施例提供了一种资源配置的方法,其中,该方法由接入网设备执行,该方法包括:向第一类型终端发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。
Description
本公开涉及无线通信技术领域但不限于无线通信技术领域,尤其涉及一种资源配置的方法、装置、通信设备及存储介质。
在网络的不断演化过程中,引入了新的终端即能力缩减(Redcap,Reduced capability)终端。该类终端不同于普通终端,例如,不同于增强移动带宽(eMBB,enhanced Mobile Broadband)终端。该类终端通常需要满足如下要求:1、低造价,低复杂度;2、一定程度的覆盖增强;3、功率节省。
相关技术中,定义了带宽部分(BWP,Bandwidth Part)。随着RedCap终端的引入,针对RedCap终端,如何使用BWP是需要考虑的问题。
发明内容
本公开实施例公开了一种资源配置的方法、装置、通信设备及存储介质。
根据本公开实施例的第一方面,提供一种资源配置的方法,其中,所述方法由接入网设备执行,所述方法包括:
向第一类型终端发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
在一个实施例中,所述预定操作包括以下至少之一:
随机接入响应RAR监听的操作;
寻呼监听的操作;
以及,***消息监听的操作。
在一个实施例中,所述附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,所述附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
在一个实施例中,响应于所述初始BWP的带宽不包括CORESET0的带宽,所述附加的公共CORESET的带宽不包括在所述CORESET0的带宽范围内。
在一实施例中,包括以下至少之一:
所述附加的公共CORESET被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;
所述附加的公共搜索空间被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间;
所述CORESET0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;
以及,所述公共搜索空间0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
在一个实施例中,所述预定资源还包括预定消息中为第二类型终端配置的资源;所述预定消息包括以下至少之一:MIB和SIB1;所述为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;所述为第二类型终端配置的资源被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
在一个实施例中,包括以下至少之一:
为所述第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为所述第一类型终端用于寻呼监听的搜索空间关联的CORESET;
为所述第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为所述第一类型终端用于***消息监听的搜索空间关联的CORESET;
为所述第二类型终端配置的用于寻呼监听的搜索空间被配置为所述第一类型终端用于寻呼监听的搜索空间;
以及,为所述第二类型终端配置的用于***消息监听的搜索空间被配置为所述第一类型终端用于***消息监听的搜索空间。
在一个实施例中,包括以下至少之一:所述附加的公共CORESET被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
所述公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
所述附加的公共搜索空间被配置为所述第一类型终端用于RAR监听的搜索空间
以及,所述公共搜索空间0被配置为所述第一类型终端用于RAR监听的搜索空间。
根据本公开实施例的第二方面,提供一种资源配置的方法,其中,所述方法由第一类型终端执行,所述方法包括:
接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
在一个实施例中,所述预定操作包括以下至少之一:
随机接入响应RAR监听的操作;
寻呼监听的操作;
以及,***消息监听的操作。
在一个实施例中,所述附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,所述附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
在一个实施例中,响应于所述初始BWP的带宽不包括CORESET0的带宽,所述附加的公共CORESET的带宽不包括在所述CORESET0的带宽范围内。
在一个实施例中,包括以下至少之一:
所述附加的公共CORESET被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;
所述附加的公共搜索空间被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间;
所述CORESET0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;
以及,所述公共搜索空间0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
在一个实施例中,所述预定资源还包括预定消息中为第二类型终端配置的资源;所述预定消息包括以下至少之一:MIB和SIB1;所述为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;所述为第二类型终端配置的资源被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
在一个实施例中,包括以下至少之一:
为所述第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为所述第一类型终端用于寻呼监听的搜索空间关联的CORESET;
为所述第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为所述第一类型终端用于***消息监听的搜索空间关联的CORESET;
为所述第二类型终端配置的用于寻呼监听的搜索空间被配置为所述第一类型终端用于寻呼监听的搜索空间;
以及,为所述第二类型终端配置的用于***消息监听的搜索空间被配置为所述第一类型终端用于***消息监听的搜索空间。
在一个实施例中,包括以下至少之一:所述附加的公共CORESET被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
所述公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
所述附加的公共搜索空间被配置为所述第一类型终端用于RAR监听的搜索空间
以及,所述公共搜索空间0被配置为所述第一类型终端用于RAR监听的搜索空间。
根据本公开实施例的第三方面,提供一种资源配置的装置,其中,所述装置包括:
发送模块,被配置为向第一类型终端发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
根据本公开实施例的第四方面,提供一种资源配置的装置,其中,所述装置包括:
接收模块,被配置为接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
根据本公开实施例的第五方面,提供一种通信设备,所述通信设备,包括:
处理器;
用于存储所述处理器可执行指令的存储器;
其中,所述处理器被配置为:用于运行所述可执行指令时,实现本公开任意实施例所述的方法。
根据本公开实施例的第六方面,提供一种计算机存储介质,所述计算机存储介质存储有计算机可执行程序,所述可执行程序被处理器执行时实现本公开任意实施例所述的方法。
在本公开实施例中,向第一类型终端发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。如此,所述第一类型终端在接收到接入网设备发送的针对初始带宽部分BWP配置的下行控制信道公共配置信息后,就可以基于所述下行控制信道公共配置信息指示的预定资源执行预定操作,相较于未针对初始BWP配置下行控制信道公共配置信息的方式,使得所述第一类型终端可以高效可靠地利用BWP的资源。
图1是根据一示例性实施例示出的一种无线通信***的结构示意图。
图2是根据一示例性实施例示出的一种资源配置的方法的流程示意图。
图3是根据一示例性实施例示出的一种资源配置的方法的流程示意图。
图4是根据一示例性实施例示出的一种资源配置的方法的流程示意图。
图5是根据一示例性实施例示出的一种资源配置的方法的流程示意图。
图6是根据一示例性实施例示出的一种资源配置的方法的流程示意图。
图7是根据一示例性实施例示出的一种资源配置的方法的流程示意图。
图8是根据一示例性实施例示出的一种资源配置的装置的结构示意图。
图9是根据一示例性实施例示出的一种资源配置的装置的结构示意图。
图10是根据一示例性实施例示出的一种终端的结构示意图。
图11是根据一示例性实施例示出的一种基站的框图。
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的,而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。还应当理解,本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解,尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如,在不脱离本公开实施例范围的情况下,第一信息也可以被称为第二信息,类似地,第二信息也可以被称为第一信息。取决于语境,如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
出于简洁和便于理解的目的,本文在表征大小关系时,所使用的术语为“大于”或“小于”。但对于本领域技术人员来说,可以理解:术语“大于”也涵盖了“大于等于”的含义,“小于”也涵盖了“小于等于”的含义。
请参考图1,其示出了本公开实施例提供的一种无线通信***的结构示意图。如图1所示,无线通信***是基于移动通信技术的通信***,该无线通信***可以包括:若干个用户设备110以及若干个基站120。
其中,用户设备110可以是指向用户提供语音和/或数据连通性的设备。用户设备110可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网进行通信,用户设备110可以是物联网用户设备,如传感器设备、移动电话和具有物联网用户设备的计算机,例如,可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如,站(Station,STA)、订户单元(subscriber unit)、订户站(subscriber station),移动站(mobile station)、移动台(mobile)、远程站(remote station)、接 入点、远程用户设备(remote terminal)、接入用户设备(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户设备(user equipment)。或者,用户设备110也可以是无人飞行器的设备。或者,用户设备110也可以是车载设备,比如,可以是具有无线通信功能的行车电脑,或者是外接行车电脑的无线用户设备。或者,用户设备110也可以是路边设备,比如,可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站120可以是无线通信***中的网络侧设备。其中,该无线通信***可以是***移动通信技术(the 4th generation mobile communication,4G)***,又称长期演进(Long Term Evolution,LTE)***;或者,该无线通信***也可以是5G***,又称新空口***或5G NR***。或者,该无线通信***也可以是5G***的再下一代***。其中,5G***中的接入网可以称为NG-RAN(New Generation-Radio Access Network,新一代无线接入网)。
其中,基站120可以是4G***中采用的演进型基站(eNB)。或者,基站120也可以是5G***中采用集中分布式架构的基站(gNB)。当基站120采用集中分布式架构时,通常包括集中单元(central unit,CU)和至少两个分布单元(distributed unit,DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)层、无线链路层控制协议(Radio Link Control,RLC)层、媒体访问控制(Media Access Control,MAC)层的协议栈;分布单元中设置有物理(Physical,PHY)层协议栈,本公开实施例对基站120的具体实现方式不加以限定。
基站120和用户设备110之间可以通过无线空口建立无线连接。在不同的实施方式中,该无线空口是基于***移动通信网络技术(4G)标准的无线空口;或者,该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口,比如该无线空口是新空口;或者,该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中,用户设备110之间还可以建立E2E(End to End,端到端)连接。比如车联网通信(vehicle to everything,V2X)中的V2V(vehicle to vehicle,车对车)通信、V2I(vehicle to Infrastructure,车对路边设备)通信和V2P(vehicle to pedestrian,车对人)通信等场景。
这里,上述用户设备可认为是下面实施例的终端设备。
在一些实施例中,上述无线通信***还可以包含网络管理设备130。
若干个基站120分别与网络管理设备130相连。其中,网络管理设备130可以是无线通信***中的核心网设备,比如,该网络管理设备130可以是演进的数据分组核心网(Evolved Packet Core,EPC)中的移动性管理实体(Mobility Management Entity,MME)。或者,该网络管理设备也可以是其它的核心网设备,比如服务网关(Serving GateWay,SGW)、公用数据网网关(Public Data Network GateWay,PGW)、策略与计费规则功能单元(Policy and Charging Rules Function,PCRF)或者归属签约用户服务器(Home Subscriber Server,HSS)等。对于网络管理设备130的实现形态,本公开实施例不做限定。
为了便于本领域内技术人员理解,本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然,本领域内技术人员可以理解,本公开实施例提供的多个实施例,可以被单独执行,也可以与本公开实施例中其他实施例的方法结合后一起被执行,还可以单独或结合后与其他相关技术中的一些方法一起被执行;本公开实施例并不对此作出限定。
为了更好地理解本公开任一个实施例所描述的技术方案,首先,对相关技术中的应用场景进行说明:
在***移动通信技术4G***中,为了支持物联网业务,提出了机器类通信(MTC,Machine Type Communication)和窄带物联网(NB-IoT,Narrow Band Internet of Thing)两大技术。
这两大技术主要针对的是低速率和高时延等场景。例如,抄表,环境监测等场景。在一个实施例中,NB-IoT最大只能支持几百k的速率,MTC最大只能支持几M的速率。但是,随着物联网业务的不断发展,例如,视频监控、智能家居、可穿戴设备和工业传感监测等业务的普及。这些业务通常要求几十到100M的速率,同时对时延也有相对较高的要求,因此,***移动通信技术中的MTC和NB-IoT技术很难满足要求。基于这种情况,提出了在第五代移动通信技术5G新空口中再设计一种新的终端类型用以覆盖这种中端物联网设备的要求。
在一个实施例中,这种新的终端类型叫做能力缩减终端(RedCap,Reduced capability UE)或者简称为NR-lite。这里,基于5G NR-lite中的RedCap通常需要满足如下要求:低造价,低复杂度;一定程度的覆盖增强;功率节省。
由于5G新空口是针对高速率和低时延等高端终端设计的,因此,相关设计无法满足NR-lite的上述要求。需要对新空口(NR,New Radio)***进行改造用以满足NR-lite的要求。在一个实施例中,为了满足低造价,低复杂度等要求,可以限制NR-IoT的射频带宽,例如,将射频带宽限制到20MHz。在一个实施例中,可以限制NR-lite的缓存(buffer)的大小,进而限制每次接收传输块的大小等。在一个实施例中,针对功率节省,可能的优化方向是简化通信流程,减少NR-lite用户检测下行控制信道的次数等。
在一个实施例中,信息单元(IE)字段PDCCH-ConfigCommon用于配置在***信息块(SIB,system information block)以及专用信令中提供的小区特定物理下行控制信道(PDCCH,Physical Downlink Control Channel)参数。
在一个实施例中,commonControlResourceSet是一个额外的公共控制资源集,可以配置并用于任何公共或特定于终端的搜索空间。如果网络配置了这个字段,它会为这个ControlResourceSet使用一个非0的ControlResourceSetId。网络在SIB1中配置commonControlResourceSet,使其包含在控制资源集CORESET#0的带宽中。
在一个实施例中,公共CORESET#0的参数,可用于任何公共或特定于终端的搜索空间。
在Redcap终端引入之后,可以为Redcap终端在SIB1中单独配置一个下行用于随机接入响应(RAR,Random Access Response)的初始BWP。该初始BWP,也可以为寻呼(paging)使用的初始BWP。关于如何配置该初始BWP上的公共搜索空间尚没有定义。
如图2所示,本实施例中提供一种资源配置的方法,其中,该方法由接入网设备执行,该方法包括:
步骤21、向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;
其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括 以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
这里,本公开所涉及的第一类型终端和第二类型终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU,Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。第一类型终端和第二类型终端为不同类型的终端。在一个实施例中,第一类型终端可以是Redcap终端,第二类型终端可以是Redcap终端之外的其他非Redcap终端。
本公开中涉及的接入网设备可以是基站。这里,基站可以为各种类型的基站,例如,第五代移动通信(5G)网络的基站或其它演进型基站。
在一个实施例中,给第一类型终端配置下行初始BWP;向第一类型终端发送针对初始BWP配置的PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。
需要说明的是,PDCCH公共配置信息可以是携带在RedCap专用初始下行BWP配置(RedCap-specific initial DL BWP configuration)的PDCCH公共配置(PDCCH-configCommon)字段中或者PDCCH公共***信息块配置(PDCCH-configCommonSIB)字段中。
需要说明的是,PDCCH的频域资源信息和时域占用的正交频分复用(OFDM,Orthogonal Frequency Division Multiplexing)符号数等信息封装在CORESET中;PDCCH起始OFDM符号以及监听周期、关联的CORESET等信息封装在搜索空间中。这里,公共搜索空间主要是在接入时和小区切换时使用,例如,用于广播控制信道BCCH、寻呼、RAR等相关的控制信息监听。其中,RAR等相关消息即对于随机接入响应的消息,包括msg2,msg4,msgB等。
在一个实施例中,向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同。需要说明的是,附加的公共CORESET的标识可以不为0。
在一个实施例中,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同。需要说明的是,附加的公共搜索空间的标识可以不为0。
在一个实施例中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识相同。需要说明的是,附加的公共CORESET的标识可以不为0。
在一个实施例中,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识相 同。需要说明的是,附加的公共搜索空间的标识可以不为0。
在一个实施例中,若该初始BWP带宽不包括CORSET0的带宽,则可以配置附加的公共CORESET或者附加的公共搜索空间;其中,该附加的公共CORESET的带宽不用包括在CORESET0的带宽范围内。
在一个实施例中,可以基于附加的公共CORESET,配置针对第一类型终端的全部或者部分公共搜索空间关联的CORESET。或者,可以基于附加的公共搜索空间,配置针对第一类型终端的全部或者部分公共搜索空间。
需要说明的是,这里的全部搜索空间关联的CORESET可以理解为终端执行全部预定操作所需的搜索空间关联的CORESET,全部预定操作可以包含:随机接入响应RAR监听的操作、寻呼监听的操作、以及***消息监听的操作等,但是,并不限于上述操作。部分搜索空间关联的CORESET可以理解为执行部分预定操作所需的搜索空间关联的CORESET,部分预定操作为全部预定操作中的一部分。同理,这里的全部搜索空间可以理解为终端执行全部预定操作所需的搜索空间,全部预定操作可以包含:随机接入响应RAR监听的操作、寻呼监听的操作、以及***消息监听的操作等,但是,并不限于上述操作。部分搜索空间可以理解为执行部分预定操作所需的搜索空间,部分预定操作为全部预定操作中的一部分。
在一个实施例中,附加的公共CORESET被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET。其中,预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,附加的公共搜索空间被配置为用于第一类型终端执行全部预定操作的公共搜索空间。其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;以及,附加的公共搜索空间。其中,附加的公共CORESET被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET;和/或,附加的公共搜索空间被配置为用于第一类型终端执行全部预定操作的公共搜索空间。
在一个实施例中,公共控制资源集CORESET0被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET。其中,预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,公共控制资源集CORESET0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。
在一个实施例中,公共控制资源集CORESET0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。第一类类型终端配置的初始BWP的带宽范围并不包含公共控制资源集CORESET0的带宽。
在一个实施例中,公共搜索空间0被配置为用于第一类型终端执行全部预定操作的公共搜索空间。其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:公共控制资源集CORESET0;以及公共搜索空间0。其中,公共CORESET0被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET;和/或,公共搜索空间0被配置为用于第一类型终端执行全部预定操作的公共搜索空间。
在一个实施例中,公共搜索空间0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。
在一个实施例中,公共搜索空间0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。第一类型终端配置的初始BWP的带宽范围并不包含公共控制资源集CORESET0的带宽。
在一个实施例中,所述附加的公共CORESET被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;和/或,所述附加的公共搜索空间被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间;和/或,所述CORESET0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;和/或,所述公共搜索空间0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
在一个实施例中,附加的公共CORESET被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,附加的公共搜索空间被配置为用于第一类型终端执行部分预定操作的公共搜索空间;和/或,CORESET0被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,公共搜索空间0被配置为用于第一类型终端执行部分预定操作的公共搜索空间。其中,预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,附加的公共CORESET被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,附加的公共搜索空间被配置为用于第一类型终端执行部分预定操作的公共搜索空间;和/或,CORESET0被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,公共搜索空间0被配置为用于第一类型终端执行部分预定操作的公共搜索空间。
需要说明的是,主信息块(MIB,Master Information Block)中可以配置CORESET0和搜索空间0, 其他的标识为非0的CORESET和/或搜索空间需要在SIB1中配置。例如,CORESET1和/或搜索空间1配置在SIB1中。
在一个实施例中,预定资源还包括预定消息中为第二类型终端配置的资源;预定消息包括以下至少之一:MIB和SIB1;为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;为第二类型终端配置的资源被配置为用于第一类型终端执行预定操作的公共搜索空间。
在一个实施例中,MIB中为第二类型终端配置了CORESET0和/或搜索空间0;SIB1中为第二类型终端配置了附加的CORESET x和/或附加的搜索空间CORESET x,其中,x不为0,可以是1、2等。
在一个实施例中,MIB中为第二类型终端配置了CORESET0和/或搜索空间0,用于SIB1的监听;SIB1中为第二类型终端配置了CORESET x和/或搜索空间CORESET x,其中,x不为0,可以是1、2等。其中Other SI的监听,或者寻呼的监听;或者RAR的监听可以关联到MIB中为第二类型终端配置了CORESET0和/或搜索空间0,或者CORESET x和/或搜索空间CORESET x;即对于COREST和搜索空间的配置可以关联到MIB中配置CORESET0和/或搜索空间0或附加的CORESET和/或附加的搜索空间配置。
在一个实施例中,为第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为第一类型终端用于寻呼监听的搜索空间关联的CORESET。
在一个实施例中,为第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为第一类型终端用于***消息监听的搜索空间关联的CORESET。
在一个实施例中,为第二类型终端配置的用于寻呼监听的搜索空间被配置为第一类型终端用于寻呼监听的搜索空间。
在一个实施例中,为第二类型终端配置的用于***消息监听的搜索空间被配置为第一类型终端用于***消息监听的搜索空间。
在一个实施例中,为第二类型终端配置的附加的公共CORESET被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
在一个实施例中,所述公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
在一个实施例中,为第二类型终端配置的附加的公共搜索空间被配置为所述第一类型终端用于RAR监听的搜索空间;
在一个实施例中,所述或者公共搜索空间0被配置为所述第一类型终端用于RAR监听的搜索空间。
在一个实施例中,为第二类型终端配置的RAR搜索空间关联到的附加的公共CORESET或CORESE0可以被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET,即二者复用。但是可以额外为所述第一类型终端用于RAR监听配置不同的搜索空间。此时网络将分别在不同的搜索空间调度不同类型终端的随机接入响应消息。
在一个实施例中,若为第二类型终端配置的初始BWP不包含CORESET0,则意味着和第一类型终端的初始BWP带宽上并不重叠;此时为第二类型终端配置的RAR搜索空间需要单独配置附加的公共CORESET,例如,commonControlResourceSet-Redcap或者和第一类型终端的初始BWP带宽上附加的 公共CORESET ID不同的附加的公共CORESET,例如,附加的公共CORESET 2。此时网络将分别在不同的初始BWP上调度不同类型终端的随机接入响应消息。
在一个实施例中,PDCCH-ConfigCommon字段中commonControlResourceSet需要为第一类型终端进行扩展,用于配置一个额外的(或者附加的)公共CORESET;该额外的公共CORESET的ID可以同第二类型终端配置的初始BWP上包含的附加CORESET相同或者不同。比如,PDCCH-ConfigCommon字段中commonControlResourceSet需要为第一类型终端进行扩展,用于配置一个额外的公共CORESET#2或公共CORESET-Redcap,用于RAR监听;而第一类型终端配置的寻呼消息、***消息等监听还是可以继续沿用为第二类型终端配置一个额外的公共CORESET,例如,额外的公共CORESET#1或者CORSET0;这样可以避免混淆。
在一个实施例中,若为第二类型终端配置的PDCCH-ConfigCommon字段中commonControlResourceSet,用于配置一个额外的公共CORESET#1,用于RAR监听;而第一类型终端配置的寻呼消息、***消息等监听还是可以继续沿用为第二类型终端配置一个公共CORESET0(假设第二类型终端没有用到附加的CORESET),这样也不会发生混淆。
在一个实施例中,若为第二类型终端配置的初始BWP包含CORESET0,则意味着和第一类型终端的初始BWP带宽上存在重叠;此时为第二类型终端配置的PDCCH-ConfigCommon字段中commonControlResourceSet,则需要包含在CORESET0中。作为一种优选实施例,可以完全同第二类型终端的配置。其中,***消息监听、寻呼消息监听可以完全复用第二类型终端的配置;RAR消息的监听也可以完全复用第二类型终端的配置,或者RAR搜索空间可以单独配置附加的公共CORESET,例如,commonControlResourceSet-Redcap或者公共CORESET1。
在本公开实施例中,向第一类型终端发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。如此,第一类型终端在接收到接入网设备发送的针对初始带宽部分BWP配置的下行控制信道公共配置信息后,就可以基于下行控制信道公共配置信息指示的预定资源执行预定操作,相较于未针对初始BWP配置下行控制信道公共配置信息的方式,使得第一类型终端可以高效可靠地利用BWP的资源。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
为了更好地理解本公开实施例,以下通过3个示例性实施例对本公开技术方案进行进一步说明:
示例1
针对第二类型终端配置的下行初始BWP中,对应的PDCCH-configCommon配置如下:在MIB中配置了CORESET0和/或搜索空间0。该CORESET0和/或搜索空间0用于接收SIB1。这里,该CORESET0或者搜索空间0还可以用于其他***消息监听、寻呼消息监听和RAR监听等。需要说明的是,其他系 统消息监听、寻呼消息监听和RAR监听的资源也可以关联到SIB1中配置的CORESET1和搜索空间1。
针对第一类型终端配置的下行初始BWP中,若不包含CORESET0,对应的PDCCH-configCommon配置如下:
采用针对第二类型终端配置的CORESET0和搜索空间0接收SIB1(SIB1监听是在CORESET0和SS0,其他类型监听则无限制);
采用针对第二类型终端配置的CORESET0、CORESET1、搜索空间0和搜索空间1中的至少之一进行其他***消息监听、寻呼监听等。作为优选实施例,可以第一类型终端配置和第二类型终端配置完全相同;
需要说明的是,第一类型终端的RAR的监听的搜索空间可以不同于第二类型终端配置的搜索空间,例如,搜索空间1等。和/或,RAR的监听的CORESET可以采用附加公共CORESET,例如,CORESET1等。
需要说明的是,仅有RAR监听的搜索空间在针对第一类型终端配置的初始BWP带宽范围内,而paging监听和SI监听的搜索空间或者关联的CORESET都为第二类型终端配置的初始BWP,此时接收消息需要收发机转换。
示例2
针对第二类型终端配置的下行初始BWP中,对应的PDCCH-configCommon配置如下:
在MIB中配置了CORESET0和/或搜索空间0。该CORESET0和/或搜索空间0用于***消息监听;
在SIB1的初始BWP上配置CORESET1或者搜索空间1,寻呼消息监听和RAR监听的资源也可以关联到SIB1中配置的CORESET1和搜索空间1。
针对第一类型终端配置的下行初始BWP,若不包含CORESET0,对应的PDCCH-configCommon配置如下:
采用针对第二类型终端配置的CORESET0和/或搜索空间0进行***消息SIB1监听;
采用针对第二类型终端配置的CORESET1和搜索空间1中的至少之一进行寻呼监听;
采用针对第二类型终端配置的CORESET1和搜索空间1中的至少之一进行其他***监听;
需要说明的是,RAR的监听的搜索空间可以采用第一类型终端配置的下行初始BWP上配置的附加的公共搜索空间,例如,搜索空间2等。
需要说明的是,RAR的监听的搜索空间可以采用第一类型终端配置的下行初始BWP上配置的可以采用附加公共CORESET,例如,CORESET2等。
需要说明的是,仅有RAR监听的搜索空间在针对第一类型终端配置的初始BWP带宽范围内,而paging监听和SI监听的搜索空间或者关联的CORESET都为第二类型终端配置的初始BWP,此时接收消息需要收发机转换。
示例3
针对第二类型终端配置的下行初始BWP中,对应的PDCCH-configCommon配置如下:在MIB中 配置了CORESET0和/或搜索空间0。该CORESET0和/或搜索空间0用于接收SIB1。这里,该CORESET0或者搜索空间0还可以用于其他***消息监听、寻呼消息监听和RAR监听等。需要说明的是,其他***消息监听、寻呼消息监听和RAR监听的资源也可以关联到SIB1中配置的CORESET1和搜索空间1。
针对第一类型终端配置的下行初始BWP,若包含Coreset0中,对应的PDCCH-configCommon配置如下:
采用针对第二类型终端配置的CORESET0和搜索空间0接收SIB;
采用针对第二类型终端配置的CORESET0、CORESET1、搜索空间0和搜索空间1中的至少之一进行其他***消息监听、寻呼监听和RAR监听等。作为优选实施例,可以第一类型终端配置和第二类型终端配置完全相同;
需要说明的是,第一类型终端的RAR的监听的搜索空间可以不同于第二类型终端配置的搜索空间,例如,搜索空间1等。和/或,RAR的监听的CORESET可以采用附加公共CORESET,例如,CORESET1等(物理资源位置可以与针对第一类型终端配置的相同或者不同)
在一个实施例中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
如图3所示,本实施例中提供一种资源配置的方法,其中,该方法由接入网设备执行,该方法包括:
步骤31、向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
在一个实施例中,响应于初始BWP的带宽不包括CORESET0的带宽,附加的公共CORESET的带宽不包括在CORESET0的带宽范围内。
在一个实施例中,附加的公共CORESET被配置为用于第一类型终端执行预定操作的公共搜索空间关联的CORESET;
和/或,
附加的公共搜索空间被配置为用于第一类型终端执行预定操作的公共搜索空间;
和/或,
CORESET0被配置为用于第一类型终端执行预定操作的公共搜索空间关联的CORESET;
和/或,
公共搜索空间0被配置为用于第一类型终端执行预定操作的公共搜索空间。
如图4所示,本实施例中提供一种资源配置的方法,其中,该方法由接入网设备执行,该方法包括:
步骤41、向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,预定资源还包括预定消息中为第二类型终端配置的资源;预定消息包括以下至少之一:MIB和SIB1;为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;为第二类型终端配置的资源被配置为用于第一类型终端执行预定操作的公共搜索空间。
在一些实施例中,包括以下至少之一:
为第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为第一类型终端用于寻呼监听的搜索空间关联的CORESET;
为第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为第一类型终端用于***消息监听的搜索空间关联的CORESET;
为第二类型终端配置的用于寻呼监听的搜索空间被配置为第一类型终端用于寻呼监听的搜索空间;
以及,为第二类型终端配置的用于***消息监听的搜索空间被配置为第一类型终端用于***消息监听的搜索空间。
在一些实施例中,包括以下至少之一:附加的公共CORESET被配置为第一类型终端用于RAR监听的搜索空间关联的CORESET;
公共控制资源集CORESET0被配置为第一类型终端用于RAR监听的搜索空间关联的CORESET;
附加的公共搜索空间被配置为第一类型终端用于RAR监听的搜索空间。
以及,公共搜索空间0被配置为第一类型终端用于RAR监听的搜索空间。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图5所示,本实施例中提供一种资源配置的方法,其中,该方法由第一类型终端执行,该方法包括:
步骤51、接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
这里,本公开所涉及的第一类型终端和第二类型终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU,Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。第一类型终端和第二类型终端为不同类型的终端。在一个实施例中,第一类型终端可以是Redcap终端,第二类型终端可以是Redcap终端之外的其他非Redcap终端。
本公开中涉及的接入网设备可以是基站。这里,基站可以为各种类型的基站,例如,第五代移动通信(5G)网络的基站或其它演进型基站。
需要说明的是,PDCCH公共配置信息可以是携带在RedCap专用初始下行BWP配置(RedCap-specific initial DL BWP configuration)的PDCCH公共配置(PDCCH-configCommon)字段中或者PDCCH公共***信息块配置(PDCCH-configCommonSIB)字段中。
需要说明的是,PDCCH的频域资源信息和时域占用的正交频分复用(OFDM,Orthogonal Frequency Division Multiplexing)符号数等信息封装在CORESET中;PDCCH起始OFDM符号以及监听周期、关联的CORESET等信息封装在搜索空间中。这里,公共搜索空间主要是在接入时和小区切换时使用,例如,用于广播控制信道BCCH、寻呼、RAR等相关的控制信息监听。
在一个实施例中,接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同。需要说明的是,附加的公共CORESET的标识可以不为0。
在一个实施例中,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同。需要说明的是,附加的公共搜索空间的标识可以不为0。
在一个实施例中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识相同。需要说明的是,附加的公共CORESET的标识可以不为0。
在一个实施例中,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识相同。需要说明的是,附加的公共搜索空间的标识可以不为0。
在一个实施例中,若该初始BWP带宽不包括CORSET0的带宽,则接入网设备可以配置附加的公共CORESET或者附加的公共搜索空间;其中,该附加的公共CORESET的带宽不用包括在CORESET0的带宽范围内。
在一个实施例中,接入网设备可以基于附加的公共CORESET,配置针对第一类型终端的全部或者部分公共搜索空间关联的CORESET。或者,接入网设备可以基于附加的公共搜索空间,配置针对第一类型终端的全部或者部分公共搜索空间。
需要说明的是,这里的全部搜索空间关联的CORESET可以理解为终端执行全部预定操作所需的搜索空间关联的CORESET,全部预定操作可以包含:随机接入响应RAR监听的操作、寻呼监听的操作、以及***消息监听的操作等,但是,并不限于上述操作。部分搜索空间关联的CORESET可以理解为执行部分预定操作所需的搜索空间关联的CORESET,部分预定操作为全部预定操作中的一部分。同理,这里的全部搜索空间可以理解为终端执行全部预定操作所需的搜索空间,全部预定操作可以包含:随机接入响应RAR监听的操作、寻呼监听的操作、以及***消息监听的操作等,但是,并不限于上述操作。部分搜索空间可以理解为执行部分预定操作所需的搜索空间,部分预定操作为全部预定操作中的一部分。
在一个实施例中,附加的公共CORESET被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET。其中,预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,附加的公共搜索空间被配置为用于第一类型终端执行全部预定操作的公共搜索空间。其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;以及,附加的公共搜索空间。其中,附加的公共CORESET被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET;和/或,附加的公共搜索空间被配置为用于第一类型终端执行全部预定操作的公共搜索空间。
在一个实施例中,公共控制资源集CORESET0被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET。其中,预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,公共控制资源集CORESET0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。
在一个实施例中,公共控制资源集CORESET0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。第一类类型终端配置的初始BWP的带宽范围并不包含公共控制资源集CORESET0的带宽。
在一个实施例中,公共搜索空间0被配置为用于第一类型终端执行全部预定操作的公共搜索空间。其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:公共控制资源集CORESET0;以及公共搜索空间0。其中, 公共CORESET0被配置为用于第一类型终端执行全部预定操作的公共搜索空间关联的CORESET;和/或,公共搜索空间0被配置为用于第一类型终端执行全部预定操作的公共搜索空间。
在一个实施例中,公共搜索空间0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。
在一个实施例中,公共搜索空间0可以被针对第一类型终端配置的初始BWP、第二类型终端配置的初始BWP上配置的搜索空间所使用。第一类型终端配置的初始BWP的带宽范围并不包含公共控制资源集CORESET0的带宽。
在一个实施例中,所述附加的公共CORESET被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;和/或,所述附加的公共搜索空间被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间;和/或,所述CORESET0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;和/或,所述公共搜索空间0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
在一个实施例中,附加的公共CORESET被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,附加的公共搜索空间被配置为用于第一类型终端执行部分预定操作的公共搜索空间;和/或,CORESET0被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,公共搜索空间0被配置为用于第一类型终端执行部分预定操作的公共搜索空间。其中,预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
在一个实施例中,接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,附加的公共CORESET被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,附加的公共搜索空间被配置为用于第一类型终端执行部分预定操作的公共搜索空间;和/或,CORESET0被配置为用于第一类型终端执行部分预定操作的公共搜索空间关联的CORESET;和/或,公共搜索空间0被配置为用于第一类型终端执行部分预定操作的公共搜索空间。
需要说明的是,主信息块(MIB,Master Information Block)中可以配置CORESET0和搜索空间0,其他的标识为非0的CORESET和/或搜索空间需要在SIB1中配置。例如,CORESET0和/或搜索空间0配置在SIB1中。
在一个实施例中,预定资源还包括预定消息中为第二类型终端配置的资源;预定消息包括以下至少之一:MIB和SIB1;为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;为第二类型终端配置的资源被配置为用于第一类型终端执行预定操作的公共搜索空间。
在一个实施例中,MIB中为第二类型终端配置了CORESET0和/或搜索空间0;SIB1中为第二类型 终端配置了CORESET x和/或搜索空间CORESET x,其中,x不为0,可以是1、2等。
在一个实施例中,为第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为第一类型终端用于寻呼监听的搜索空间关联的CORESET。
在一个实施例中,为第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为第一类型终端用于***消息监听的搜索空间关联的CORESET。
在一个实施例中,为第二类型终端配置的用于寻呼监听的搜索空间被配置为第一类型终端用于寻呼监听的搜索空间。
在一个实施例中,为第二类型终端配置的用于***消息监听的搜索空间被配置为第一类型终端用于***消息监听的搜索空间。
在一个实施例中,所述附加的公共CORESET或者公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
在一个实施例中,所述公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;
在一个实施例中,所述附加的公共搜索空间被配置为所述第一类型终端用于RAR监听的搜索空间
在一个实施例中,所述或者公共搜索空间0被配置为所述第一类型终端用于RAR监听的搜索空间。
在一个实施例中,为第二类型终端配置的RAR搜索空间关联到的附加的公共CORESET或CORESE0可以被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET,即二者复用。但是可以额外为所述第一类型终端用于RAR监听配置不同的搜索空间。此时网络将分别在不同的搜索空间调度不同类型终端的随机接入响应消息。
在一个实施例中,若为第二类型终端配置的初始BWP不包含CORESET0,则意味着和第一类型终端的初始BWP带宽上并不重叠;此时为第二类型终端配置的RAR搜索空间需要单独配置附加的公共CORESET,例如,commonControlResourceSet-Redcap或者和第一类型终端的初始BWP带宽上附加的公共CORESET ID不同的附加的公共CORESET,例如,附加的公共CORESET 2。此时网络将分别在不同的初始BWP上调度不同类型终端的随机接入响应消息。
在一个实施例中,PDCCH-ConfigCommon字段中commonControlResourceSet需要为第一类型终端进行扩展,用于配置一个额外的(或者附加的)公共CORESET;该额外的公共CORESET的ID可以同第二类型终端配置的初始BWP上包含的附加CORESET或者也可以二者不同。比如,PDCCH-ConfigCommon字段中commonControlResourceSet需要为第一类型终端进行扩展,用于配置一个额外的公共CORESET#2或公共CORESET-Redcap,用于RAR监听;而第一类型终端配置的寻呼消息、***消息等监听还是可以继续沿用为第二类型终端配置一个额外的公共CORESET,例如,额外的公共CORESET#1或者CORSET0;这样可以避免混淆。
在一个实施例中,若为第二类型终端配置的PDCCH-ConfigCommon字段中commonControlResourceSet,用于配置一个额外的公共CORESET#1,用于RAR监听;而第一类型终端配置的寻呼消息、***消息等监听还是可以继续沿用为第二类型终端配置一个公共CORESET0(假设第二类型终端没有用到附加的CORESET),这样也不会发生混淆。
在一个实施例中,若为第二类型终端配置的初始BWP包含CORESET0,则意味着和第一类型终端的初始BWP带宽上存在重叠;此时为第二类型终端配置的PDCCH-ConfigCommon字段中commonControlResourceSet,则需要包含在CORESET0中。作为一种优选实施例,可以完全同第二类型终端的配置。其中,***消息监听、寻呼消息监听可以完全复用第二类型终端的配置;RAR消息的监听也可以完全复用第二类型终端的配置,或者RAR搜索空间可以单独配置附加的公共CORESET,例如,commonControlResourceSet-Redcap或者公共CORESET1。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
在一个实施例中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
如图6所示,本实施例中提供一种资源配置的方法,其中,该方法由第一类型终端执行,该方法包括:
步骤61、接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
在一个实施例中,响应于初始BWP的带宽不包括CORESET0的带宽,附加的公共CORESET的带宽不包括在CORESET0的带宽范围内。
在一个实施例中,附加的公共CORESET被配置为用于第一类型终端执行预定操作的公共搜索空间关联的CORESET;
和/或,
附加的公共搜索空间被配置为用于第一类型终端执行预定操作的公共搜索空间;
和/或,
CORESET0被配置为用于第一类型终端执行预定操作的公共搜索空间关联的CORESET;
和/或,
公共搜索空间0被配置为用于第一类型终端执行预定操作的公共搜索空间。
如图7所示,本实施例中提供一种资源配置的方法,其中,该方法由第一类型终端执行,该方法包括:
步骤71、向第一类型终端发送针对初始带宽部分BWP配置的物理下行控制信道PDCCH公共配置信息;其中,下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。其中,预定资源还包括预定消息中为第二类型终端配置的资源;预定消息包括以下至少之一:MIB和SIB1;为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;为第二类型终端配置的资源被配置为用于第一类型终端执行预定操作的公共搜索空间。
在一些实施例中,包括以下至少之一:
为第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为第一类型终端用于寻呼监听的搜索空间关联的CORESET;
为第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为第一类型终端用于***消息监听的搜索空间关联的CORESET;
为第二类型终端配置的用于寻呼监听的搜索空间被配置为第一类型终端用于寻呼监听的搜索空间;
以及,为第二类型终端配置的用于***消息监听的搜索空间被配置为第一类型终端用于***消息监听的搜索空间。
在一些实施例中,包括以下至少之一:附加的公共CORESET被配置为第一类型终端用于RAR监听的搜索空间关联的CORESET;
公共控制资源集CORESET0被配置为第一类型终端用于RAR监听的搜索空间关联的CORESET;
附加的公共搜索空间被配置为第一类型终端用于RAR监听的搜索空间
以及,公共搜索空间0被配置为第一类型终端用于RAR监听的搜索空间。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图8所示,本公开实施例中提供一种资源配置的装置,其中,所述装置包括:
发送模块81,被配置为向第一类型终端发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以 与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图9所示,本公开实施例中提供一种资源配置的装置,其中,所述装置包括:
接收模块91,被配置为接收接入网设备向第一类型终端发送的针对初始带宽部分BWP配置的下行控制信道公共配置信息;
其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:
附加的公共控制资源集CORESET;
附加的公共搜索空间;
公共控制资源集CORESET0;
以及公共搜索空间0。
需要说明的是,本领域内技术人员可以理解,本公开实施例提供的方法,可以被单独执行,也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
本公开实施例提供一种通信设备,通信设备,包括:
处理器;
用于存储处理器可执行指令的存储器;
其中,处理器被配置为:用于运行可执行指令时,实现应用于本公开任意实施例的方法。
其中,处理器可包括各种类型的存储介质,该存储介质为非临时性计算机存储介质,在通信设备掉电之后能够继续记忆存储其上的信息。
处理器可以通过总线等与存储器连接,用于读取存储器上存储的可执行程序。
本公开实施例还提供一种计算机存储介质,其中,计算机存储介质存储有计算机可执行程序,可执行程序被处理器执行时实现本公开任意实施例的方法。
关于上述实施例中的装置,其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述,此处将不做详细阐述说明。
如图10所示,本公开一个实施例提供一种终端的结构。
参照图10所示终端800本实施例提供一种终端800,该终端具体可是移动电话,计算机,数字广播终端,消息收发设备,游戏控制台,平板设备,医疗设备,健身设备,个人数字助理等。
参照图10,终端800可以包括以下一个或多个组件:处理组件802,存储器804,电源组件806,多媒体组件808,音频组件810,输入/输出(I/O)的接口812,传感器组件814,以及通信组件816。
处理组件802通常控制终端800的整体操作,诸如与显示,电话呼叫,数据通信,相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令,以完成上述的方法的全部或部分步骤。此外,处理组件802可以包括一个或多个模块,便于处理组件802和其他组件之间的交 互。例如,处理组件802可以包括多媒体模块,以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在终端800上操作的任何应用程序或方法的指令,联系人数据,电话簿数据,消息,图片,视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现,如静态随机存取存储器(SRAM),电可擦除可编程只读存储器(EEPROM),可擦除可编程只读存储器(EPROM),可编程只读存储器(PROM),只读存储器(ROM),磁存储器,快闪存储器,磁盘或光盘。
电源组件806为终端800的各种组件提供电力。电源组件806可以包括电源管理***,一个或多个电源,及其他与为终端800生成、管理和分配电力相关联的组件。
多媒体组件808包括在终端800和用户之间的提供一个输出接口的屏幕。在一些实施例中,屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板,屏幕可以被实现为触摸屏,以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界,而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中,多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式,如拍摄模式或视频模式时,前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜***或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如,音频组件810包括一个麦克风(MIC),当终端800处于操作模式,如呼叫模式、记录模式和语音识别模式时,麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中,音频组件810还包括一个扬声器,用于输出音频信号。
I/O接口812为处理组件802和***接口模块之间提供接口,上述***接口模块可以是键盘,点击轮,按钮等。这些按钮可包括但不限于:主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器,用于为终端800提供各个方面的状态评估。例如,传感器组件814可以检测到设备800的打开/关闭状态,组件的相对定位,例如组件为终端800的显示器和小键盘,传感器组件814还可以检测终端800或终端800一个组件的位置改变,用户与终端800接触的存在或不存在,终端800方位或加速/减速和终端800的温度变化。传感器组件814可以包括接近传感器,被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器,如CMOS或CCD图像传感器,用于在成像应用中使用。在一些实施例中,该传感器组件814还可以包括加速度传感器,陀螺仪传感器,磁传感器,压力传感器或温度传感器。
通信组件816被配置为便于终端800和其他设备之间有线或无线方式的通信。终端800可以接入基于通信标准的无线网络,如Wi-Fi,2G或3G,或它们的组合。在一个示例性实施例中,通信组件816经由广播信道接收来自外部广播管理***的广播信号或广播相关信息。在一个示例性实施例中,通信组件816还包括近场通信(NFC)模块,以促进短程通信。例如,在NFC模块可基于射频识别(RFID)技术,红外数据协会(IrDA)技术,超宽带(UWB)技术,蓝牙(BT)技术和其他技术来实现。
在示例性实施例中,终端800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制 器、微处理器或其他电子元件实现,用于执行上述方法。
在示例性实施例中,还提供了一种包括指令的非临时性计算机可读存储介质,例如包括指令的存储器804,上述指令可由终端800的处理器820执行以完成上述方法。例如,非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图11所示,本公开一实施例示出一种基站的结构。例如,基站900可以被提供为一网络侧设备。参照图11,基站900包括处理组件922,其进一步包括一个或多个处理器,以及由存储器932所代表的存储器资源,用于存储可由处理组件922的执行的指令,例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外,处理组件922被配置为执行指令,以执行上述方法前述应用在所述基站的任意方法。
基站900还可以包括一个电源组件926被配置为执行基站900的电源管理,一个有线或无线网络接口950被配置为将基站900连接到网络,和一个输入输出(I/O)接口958。基站900可以操作基于存储在存储器932的操作***,例如Windows Server TM,Mac OS XTM,UnixTM,LinuxTM,FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后,将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本发明的真正范围和精神由下面的权利要求指出。
应当理解的是,本发明并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。
Claims (20)
- 一种资源配置的方法,其中,所述方法由接入网设备执行,所述方法包括:发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,所述下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。
- 根据权利要求1所述的方法,其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
- 根据权利要求1所述的方法,其中,所述附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,所述附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
- 根据权利要求1所述的方法,其中,响应于所述初始BWP的带宽不包括CORESET0的带宽,所述附加的公共CORESET的带宽不包括在所述CORESET0的带宽范围内。
- 根据权利要求1所述的方法,其中,包括以下至少之一:所述附加的公共CORESET被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;所述附加的公共搜索空间被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间;所述CORESET0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;以及,所述公共搜索空间0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
- 根据权利要求5所述的方法,其中,所述预定资源还包括预定消息中为第二类型终端配置的资源;所述预定消息包括以下至少之一:MIB和SIB1;所述为第二类型终端配置的资源包括用于寻呼监听、***消息监听和RAR监听的资源中的至少一种;所述为第二类型终端配置的资源被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
- 根据权利要求6所述的方法,其中,包括以下至少之一:为所述第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为所述第一类型终端用于寻呼监听的搜索空间关联的CORESET;为所述第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为所述第一类型终端用于***消息监听的搜索空间关联的CORESET;为所述第二类型终端配置的用于寻呼监听的搜索空间被配置为所述第一类型终端用于寻呼监听的 搜索空间;以及,为所述第二类型终端配置的用于***消息监听的搜索空间被配置为所述第一类型终端用于***消息监听的搜索空间。
- 根据权利要求7所述的方法,其中,包括以下至少之一:所述附加的公共CORESET被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;所述公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;所述附加的公共搜索空间被配置为所述第一类型终端用于RAR监听的搜索空间以及,所述公共搜索空间0被配置为所述第一类型终端用于RAR监听的搜索空间。
- 一种资源配置的方法,其中,所述方法由第一类型终端执行,所述方法包括:接收针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。
- 根据权利要求9所述的方法,其中,所述预定操作包括以下至少之一:随机接入响应RAR监听的操作;寻呼监听的操作;以及,***消息监听的操作。
- 根据权利要求9所述的方法,其中,所述附加的公共CORESET的标识与针对第二类型终端配置的公共CORESET的标识不同或者相同;和/或,所述附加的公共搜索空间的标识与针对第二类型终端配置的公共搜索空间的标识不同或者相同。
- 根据权利要求9所述的方法,其中,响应于所述初始BWP的带宽不包括CORESET0的带宽,所述附加的公共CORESET的带宽不包括在所述CORESET0的带宽范围内。
- 根据权利要求9所述的方法,其中,包括以下至少之一:所述附加的公共CORESET被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;所述附加的公共搜索空间被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间;所述CORESET0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间关联的CORESET;以及,所述公共搜索空间0被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
- 根据权利要求13所述的方法,其中,所述预定资源还包括预定消息中为第二类型终端配置的资源;所述预定消息包括以下至少之一:MIB和SIB1;所述为第二类型终端配置的资源包括用于寻呼 监听、***消息监听和RAR监听的资源中的至少一种;所述为第二类型终端配置的资源被配置为用于所述第一类型终端执行所述预定操作的公共搜索空间。
- 根据权利要求14所述的方法,其中,包括以下至少之一:为所述第二类型终端配置的用于寻呼监听的搜索空间关联的CORESET被配置为所述第一类型终端用于寻呼监听的搜索空间关联的CORESET;为所述第二类型终端配置的用于***消息监听的搜索空间关联的CORESET被配置为所述第一类型终端用于***消息监听的搜索空间关联的CORESET;为所述第二类型终端配置的用于寻呼监听的搜索空间被配置为所述第一类型终端用于寻呼监听的搜索空间;以及,为所述第二类型终端配置的用于***消息监听的搜索空间被配置为所述第一类型终端用于***消息监听的搜索空间。
- 根据权利要求15所述的方法,其中,包括以下至少之一:所述附加的公共CORESET被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;所述公共控制资源集CORESET0被配置为所述第一类型终端用于RAR监听的搜索空间关联的CORESET;所述附加的公共搜索空间被配置为所述第一类型终端用于RAR监听的搜索空间以及,所述公共搜索空间0被配置为所述第一类型终端用于RAR监听的搜索空间。
- 一种资源配置的装置,其中,所述装置包括:发送模块,被配置为发送针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,所述下行控制信道公共配置信息用于指示第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。
- 一种资源配置的装置,其中,所述装置包括:接收模块,被配置为接收针对初始带宽部分BWP配置的下行控制信道公共配置信息;其中,所述下行控制信道公共配置信息用于指示所述第一类型终端执行预定操作的预定资源;所述预定资源包括以下至少之一:附加的公共控制资源集CORESET;附加的公共搜索空间;公共控制资源集CORESET0;以及公共搜索空间0。
- 一种通信设备,其中,包括:存储器;处理器,与所述存储器连接,被配置为通过执行存储在所述存储器上的计算机可执行指令,并能够实现权利要求1至8或者9至16任一项所述的方法。
- 一种计算机存储介质,所述计算机存储介质存储有计算机可执行指令,所述计算机可执行指令被处理器执行后能够实现权利要求1至8或者9至16任一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202280001222.8A CN115004616A (zh) | 2022-04-14 | 2022-04-14 | 资源配置的方法、装置、通信设备及存储介质 |
PCT/CN2022/086930 WO2023197274A1 (zh) | 2022-04-14 | 2022-04-14 | 资源配置的方法、装置、通信设备及存储介质 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/086930 WO2023197274A1 (zh) | 2022-04-14 | 2022-04-14 | 资源配置的方法、装置、通信设备及存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023197274A1 true WO2023197274A1 (zh) | 2023-10-19 |
Family
ID=83023164
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/086930 WO2023197274A1 (zh) | 2022-04-14 | 2022-04-14 | 资源配置的方法、装置、通信设备及存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115004616A (zh) |
WO (1) | WO2023197274A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109391971A (zh) * | 2017-08-11 | 2019-02-26 | 维沃移动通信有限公司 | 一种pdcch的搜索空间的配置、监听方法及设备 |
CN110475211A (zh) * | 2018-05-11 | 2019-11-19 | 北京展讯高科通信技术有限公司 | 公共搜索空间的配置方法、监听方法及装置、存储介质、终端、基站 |
WO2021230729A1 (ko) * | 2020-05-15 | 2021-11-18 | 엘지전자 주식회사 | 무선 통신을 위한 신호 송수신 방법 및 이를 위한 장치 |
TW202214030A (zh) * | 2020-08-05 | 2022-04-01 | 香港商翼勝科技有限公司 | 無線電存取方法、使用者設備和基地台 |
WO2022067839A1 (en) * | 2020-10-01 | 2022-04-07 | Apple Inc. | Data scheduling for reduced capability ues |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10856320B2 (en) * | 2018-04-06 | 2020-12-01 | Lenovo (Singapore) Pte. Ltd. | Configuring for bandwidth parts |
JP7271097B2 (ja) * | 2018-07-17 | 2023-05-11 | シャープ株式会社 | 基地局装置、端末装置、および、通信方法 |
US11228967B2 (en) * | 2018-09-07 | 2022-01-18 | Qualcomm Incorporated | Configuration of common search spaces in a downlink bandwidth part |
BR112021002618A2 (pt) * | 2018-09-24 | 2021-05-11 | Google Llc | configuração de espaço de pesquisa comum e aquisição de informação do sistema |
WO2022027323A1 (zh) * | 2020-08-05 | 2022-02-10 | 北京小米移动软件有限公司 | 用于寻呼信息处理的方法、装置及存储介质 |
-
2022
- 2022-04-14 CN CN202280001222.8A patent/CN115004616A/zh active Pending
- 2022-04-14 WO PCT/CN2022/086930 patent/WO2023197274A1/zh unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109391971A (zh) * | 2017-08-11 | 2019-02-26 | 维沃移动通信有限公司 | 一种pdcch的搜索空间的配置、监听方法及设备 |
CN110475211A (zh) * | 2018-05-11 | 2019-11-19 | 北京展讯高科通信技术有限公司 | 公共搜索空间的配置方法、监听方法及装置、存储介质、终端、基站 |
WO2021230729A1 (ko) * | 2020-05-15 | 2021-11-18 | 엘지전자 주식회사 | 무선 통신을 위한 신호 송수신 방법 및 이를 위한 장치 |
TW202214030A (zh) * | 2020-08-05 | 2022-04-01 | 香港商翼勝科技有限公司 | 無線電存取方法、使用者設備和基地台 |
WO2022067839A1 (en) * | 2020-10-01 | 2022-04-07 | Apple Inc. | Data scheduling for reduced capability ues |
Non-Patent Citations (1)
Title |
---|
MODERATOR (ERICSSON): "FL summary #4 on reduced maximum UE bandwidth for RedCap", 3GPP TSG RAN WG1 MEETING #105-E, R1-2106002, 27 May 2021 (2021-05-27), XP052015701 * |
Also Published As
Publication number | Publication date |
---|---|
CN115004616A (zh) | 2022-09-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021203305A1 (zh) | 配置信息传输方法及装置、通信设备及存储介质 | |
EP4120760A1 (en) | Method and device for communication processing | |
CN111096063B (zh) | 非连续接收drx的处理方法、装置及计算机存储介质 | |
CN111543118A (zh) | Rrc状态改变的方法、装置、通信设备及存储介质 | |
WO2023193211A1 (zh) | Rsrp门限确定方法、装置、通信设备及存储介质 | |
WO2023151059A1 (zh) | 下行初始bwp的应用方法及装置、网络设备、终端及存储介质 | |
CN114128366B (zh) | 寻呼参数确定方法、装置、通信设备和存储介质 | |
WO2023201660A1 (zh) | Rsrp门限参数确定方法、装置、通信设备及存储介质 | |
WO2023184121A1 (zh) | 信息传输方法、装置、通信设备和存储介质 | |
WO2023050350A1 (zh) | Cfr的确定方法、装置、通信设备及存储介质 | |
WO2023130472A1 (zh) | 提早识别的方法、装置、通信设备及存储介质 | |
WO2022222145A1 (zh) | 终端能力信息的上报方法、装置、通信设备及存储介质 | |
WO2022205046A1 (zh) | 信息传输方法、装置、通信设备和存储介质 | |
WO2022198409A1 (zh) | Coreset#0的配置方法及装置、通信设备及存储介质 | |
WO2023197274A1 (zh) | 资源配置的方法、装置、通信设备及存储介质 | |
US20220408469A1 (en) | Downlink control information configuration method and apparatus, and communication device and storage medium | |
WO2023197327A1 (zh) | 无线传输的方法、装置、通信设备及存储介质 | |
WO2024031382A1 (zh) | 一种信息传输方法、装置、通信设备及存储介质 | |
WO2024044918A1 (zh) | Pdcch监听的指示方法、装置、通信设备及存储介质 | |
WO2023178616A1 (zh) | 接入控制方法、装置、通信设备及存储介质 | |
WO2024016233A1 (zh) | 初始bwp处理方法、装置、通信设备及存储介质 | |
US20230224973A1 (en) | Method and apparatus for sending data, and user equipment and storage medium | |
WO2024000124A1 (zh) | 寻呼协商方法、装置、通信设备及存储介质 | |
WO2023197330A1 (zh) | 无线传输的方法、装置、通信设备及存储介质 | |
WO2023197188A1 (zh) | 信息传输方法、装置、通信设备和存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22936922 Country of ref document: EP Kind code of ref document: A1 |