CN113677004A - Resource allocation method of broadcast signal and related device - Google Patents

Resource allocation method of broadcast signal and related device Download PDF

Info

Publication number
CN113677004A
CN113677004A CN202010414667.1A CN202010414667A CN113677004A CN 113677004 A CN113677004 A CN 113677004A CN 202010414667 A CN202010414667 A CN 202010414667A CN 113677004 A CN113677004 A CN 113677004A
Authority
CN
China
Prior art keywords
coreset
pdsch
offset
resource
occupied
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010414667.1A
Other languages
Chinese (zh)
Inventor
乔梁
张佳胤
贾琼
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202010414667.1A priority Critical patent/CN113677004A/en
Priority to PCT/CN2021/093291 priority patent/WO2021228130A1/en
Publication of CN113677004A publication Critical patent/CN113677004A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/30Resource management for broadcast services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA

Abstract

The embodiment of the application discloses a resource allocation method, which is used for ensuring that the frequency domain resource for sending broadcast signals meets the OCB requirement under the condition of high frequency (such as not less than 60 GHz). The method in the embodiment of the application comprises the following steps: the network equipment determines frequency domain resources used for sending broadcast signals, the proportion of the frequency domain resources occupied in the total bandwidth is larger than or equal to a preset proportion, and the network equipment sends the broadcast signals to the terminal equipment.

Description

Resource allocation method of broadcast signal and related device
Technical Field
The embodiment of the application relates to the field of communication, in particular to a resource allocation method of a broadcast signal and a related device.
Background
A significant feature of the fifth generation (5th generation, 5G) mobile communication system compared with the fourth generation (4th generation, 4G) mobile communication system is the increased support for ultra-reliable and low-latency communications (URLLC) services. The types of services of URLLC include many, and typical use cases include industrial control, unmanned driving, telesurgery, smart grid, and the like. For URLLC traffic, a typical requirement is that 32 bytes of data are sent within 1 millisecond (ms) with a reliability of 99.999%. It should be noted that the above performance index is only an example, different URLLC services may have different requirements on reliability, for example, in some extremely harsh industrial control application scenarios, the transmission success probability of URLLC service data needs to reach 99.9999999% within 0.25 ms.
The communication between the network device and the terminal device needs to satisfy the requirement of Occupying Channel Bandwidth (OCB), that is, in the communication between the network device and the terminal device, the channel is occupied by bandwidth not less than a preset proportion, and in the current configuration method, in a high frequency band (e.g., 60 gigahertz (GHz)), the communication between the network device and the terminal device may not satisfy the OCB requirement.
Disclosure of Invention
The embodiment of the application provides a resource allocation method and related equipment.
In a first aspect of the embodiments of the present application, a resource allocation method is provided, including:
the network device determines a frequency domain resource for transmitting a broadcast signal, where the frequency domain resource needs to meet an OCB requirement, that is, a proportion occupied by the frequency domain resource in a system bandwidth is greater than or equal to a preset proportion, the system bandwidth represents a bandwidth used when the network device and the terminal device communicate, the broadcast signal may include system information and a synchronization information block (SS/PBCH block), the system information is transmitted by a zeroth Type control resource set (control resource set0, CORESET #0 is carried by a zeroth Type physical downlink control channel (Type0 physical downlink control channel, Type 0PDCCH), and the network device transmits the broadcast signal to the terminal device according to the determined frequency domain resource.
In the configuration, in a shared access system of a high frequency band (e.g., 60GHz), in the communication between the network device and the terminal device, a ratio occupied by a frequency domain resource for transmitting a broadcast signal in a system bandwidth is greater than or equal to a preset ratio, and the communication between the network device and the terminal device meets the OCB requirement.
Based on the first aspect of the embodiments of the present application, in the first implementation manner of the first aspect of the embodiments of the present application, the number of resource blocks occupied by core set #0 may be 6 × N1 or 6 × N2, where N1 is any positive integer from 4 to 60, and N2 is any positive integer from 1 to 15.
The embodiment of the application provides a specific possible number of resource blocks occupied by the CORESET # 0.
Based on the first aspect of the embodiments of the present application or the first implementation manner of the first aspect, in the second implementation manner of the first aspect of the embodiments of the present application, the CORESET #0 may include a plurality of CORESET #0 sub-blocks, where the plurality of CORESET #0 sub-blocks are not consecutive in the frequency domain.
The embodiment of the application provides a case that the core set #0 comprises a plurality of core set #0 sub-blocks, namely, the core set #0 may not be continuous.
Based on the second implementation manner of the first aspect of the embodiment of the present application, in the third implementation manner of the first aspect of the embodiment of the present application, information used for indicating an interval between two adjacent CORESET #0 sub-blocks is carried in radio resource management (RRC) signaling or Downlink Control Information (DCI).
In the embodiment of the application, a way for determining the number of resource blocks occupied by the CORESET #0 interval by the network device is provided.
Based on any one of the first implementation manner to the third implementation manner of the first aspect of the embodiment of the present application, in a fourth implementation manner of the first aspect of the embodiment of the present application, the network device may configure, according to the broadcast signal, the first offset, where the first offset is an offset between a lowest frequency position of the Type 0PDCCH and a lowest frequency position of the SS/PBCH block, and a resource block occupied by the first offset is a multiple of 6, 10, 20, or 24.
Based on the fourth implementation manner of the first aspect of the embodiment of the present application, in the fifth implementation manner of the first aspect of the embodiment of the present application, the network device may generate a resource configuration table, where the resource configuration table is used to store the resource block occupied by the configured CORESET #0 and the resource block occupied by the first offset.
The embodiment of the application provides a mode for storing a resource block occupied by CORESET #0 and a resource block occupied by a first offset.
Based on any one of the first implementation manner to the fifth implementation manner of the first aspect of the embodiment of the present application, in a sixth implementation manner of the first aspect of the embodiment of the present application, the core set #0 carries a frequency domain position of a Physical Downlink Shared Channel (PDSCH), and the frequency domain position of the PDSCH includes a starting frequency position of the PDSCH and a number of resource blocks occupied by the PDSCH.
Based on any one of the first implementation manner to the sixth implementation manner of the first aspect of the present embodiment, in a seventh implementation manner of the first aspect of the present embodiment, the network device may configure the second offset according to the broadcast signal, where the second offset is an offset between a lowest frequency position of the PDSCH and a lowest frequency position of the SS/PBCH block, or the second offset is an offset between a lowest frequency position of the PDSCH and a lowest frequency position of the PDCCH.
Based on the sixth implementation manner or the seventh implementation manner of the first aspect of the embodiments of the present application, in an eighth implementation manner of the first aspect of the embodiments of the present application, the PDSCH may include multiple PDSCH sub-blocks, and the multiple PDSCH sub-blocks are not consecutive in the frequency domain.
The embodiment of the application provides a case that the PDSCH comprises a plurality of PDSCH sub-blocks, namely the PDSCH can be discontinuous.
Based on the eighth implementation manner of the first aspect of the present embodiment, in the ninth implementation manner of the first aspect of the present embodiment, the network device determines, through RRC signaling or DCI indication, resource blocks occupied by the PDSCH sub-blocks, and/or an upper limit of the resource blocks occupied by the PDSCH sub-blocks, where the PDSCH interval is an interval in two consecutive PDSCH sub-blocks.
In the embodiment of the application, a mode that the network equipment determines the resource blocks occupied by the PDSCH intervals, the resource blocks occupied by the PDSCH sub-blocks and/or the upper limit of the resource blocks occupied by the PDSCH sub-blocks is provided.
Based on any implementation manner of the first aspect of the present application to the ninth implementation manner of the first aspect, in a tenth implementation manner of the first aspect of the present application, the broadcast signal includes a reference signal and/or a reservation signal, the reference signal is used for channel quality detection or beam measurement, and the reservation signal is any signal that satisfies that a ratio of frequency domain resources occupied in a total bandwidth is greater than or equal to a preset ratio, and includes an SS/PBCH block.
In a second aspect of the embodiments of the present application, a resource allocation method is provided, including:
the terminal device receives a broadcast signal from the network device, the frequency domain resource needs to meet the OCB requirement, that is, the proportion occupied by the frequency domain resource in the system bandwidth is greater than or equal to a preset proportion, the system bandwidth represents the bandwidth used when the network device and the terminal device communicate, the broadcast signal may include system information and SS/PBCH block, the system information is indicated by CORESET #0, and the CORESET #0 is carried in Type 0PDCCH for transmission.
In the configuration, in a shared access system of a high frequency band (e.g., 60GHz), in the communication between the network device and the terminal device, a ratio occupied by a frequency domain resource for transmitting a broadcast signal in a system bandwidth is greater than or equal to a preset ratio, and the communication between the network device and the terminal device meets the OCB requirement.
Based on the second aspect of the embodiments of the present application, in the first implementation manner of the second aspect of the embodiments of the present application, the number of resource blocks occupied by CORESET #0 may be 6 × N1 or 6 × N2, where N1 is any positive integer from 4 to 60, and N2 is any positive integer from 1 to 12.
The embodiment of the application provides a specific possible number of resource blocks occupied by the CORESET # 0.
Based on the second aspect of the embodiments of the present application or the first implementation manner of the second aspect, in the second implementation manner of the second aspect of the embodiments of the present application, the CORESET #0 may include a plurality of CORESET #0 sub-blocks, and the plurality of CORESET #0 sub-blocks are not consecutive in the frequency domain.
The embodiment of the application provides a case that the core set #0 comprises a plurality of core set #0 sub-blocks, namely, the core set #0 may not be continuous.
Based on any one of the second to third implementation manners of the second aspect of the embodiments of the present application, in a third implementation manner of the second aspect of the embodiments of the present application, the terminal device may obtain, according to the broadcast signal, the first offset, where the first offset is an offset between a lowest frequency position of the Type 0PDCCH and a lowest frequency position of the SS/PBCH block, and a resource block occupied by the first offset is a multiple of 6, 10, 20, or 24.
Based on the third implementation manner of the second aspect of the embodiment of the present application, in the fourth implementation manner of the second aspect of the embodiment of the present application, the terminal device may obtain, according to the broadcast information, a resource configuration table, where the resource configuration table is used to store the resource block occupied by the configured CORESET #0 and the resource block occupied by the first offset.
The embodiment of the application provides a way for the terminal equipment to acquire the resource block occupied by the CORESET #0 and the resource block occupied by the first offset.
Based on any one of the second implementation manner to the fourth implementation manner of the second aspect of the embodiment of the present application, in a fifth implementation manner of the second aspect of the embodiment of the present application, the terminal device may determine the frequency domain position of the PDSCH according to CORESET #0, where the frequency domain position of the PDSCH is used to determine a resource indication value RIV, the RIV is used to determine LRBs and RBstart, the LRBs is the number of resource blocks continuously occupied by the PDSCH, and the RBstart is the starting frequency domain position of the PDSCH. The LRBs and RBstart satisfy the following formulas:
Figure RE-GDA0002589493220000031
or the like, or, alternatively,
Figure RE-GDA0002589493220000032
the number of resource blocks occupied for CORESET #0, or,
Figure RE-GDA0002589493220000033
the number of resource blocks occupied by a plurality of CORESET #0 sub-blocks and/or the number of resource blocks occupied by CORESET #0 intervals.
Based on any one of the second to fifth implementation manners of the second aspect of the present application, in a sixth implementation manner of the second aspect of the present application, the terminal device may determine the second offset according to the broadcast signal, where the second offset is an offset between a lowest frequency position of the PDSCH and a lowest frequency position of the SS/PBCH block, or the second offset is an offset between a lowest frequency position of the PDSCH and a lowest frequency position of the PDCCH.
Based on the fifth implementation manner or the sixth implementation manner of the second aspect of the embodiments of the present application, in the seventh implementation manner of the first aspect of the embodiments of the present application, the PDSCH may include multiple PDSCH sub-blocks, and the multiple PDSCH sub-blocks are not consecutive in the frequency domain.
The embodiment of the application provides a case that the PDSCH comprises a plurality of PDSCH sub-blocks, namely the PDSCH can be discontinuous.
Based on the seventh implementation manner of the second aspect of the embodiment of the present application, in the eighth implementation manner of the second aspect of the embodiment of the present application, the terminal device may determine, through RRC signaling or DCI indication, a resource block occupied by a PDSCH interval, a resource block occupied by a PDSCH sub-block, and/or an upper limit of the resource block occupied by the PDSCH sub-block, where the PDSCH interval is an interval in two consecutive PDSCH sub-blocks.
In the embodiment of the application, a mode that the terminal equipment determines the resource blocks occupied by the PDSCH intervals, the resource blocks occupied by the PDSCH sub-blocks and/or the upper limit of the resource blocks occupied by the PDSCH sub-blocks is provided.
Based on any one of the second to eighth implementation manners of the second aspect of the embodiments of the present application, in a ninth implementation manner of the first aspect of the embodiments of the present application, the broadcast signal includes a reference signal and/or a reservation signal, the reference signal is used for channel quality detection or beam measurement, and the reservation signal is any signal that satisfies that a ratio of total bandwidth occupation of frequency domain resources is greater than or equal to a preset ratio, and includes an SS/PBCH block.
A third aspect of the embodiments of the present application provides a network device, where the network device may perform the method of the first aspect and the embodiments of the first aspect.
A fourth aspect of the present embodiment provides a terminal device, where the terminal device may perform the method of the second aspect and embodiments of the second aspect.
A fifth aspect of embodiments of the present application provides a computer storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform the method according to the first aspect and the first implementation manner or the second aspect and the second implementation manner.
A sixth aspect of embodiments of the present application provides a computer program product, which, when executed on a computer, causes the computer to perform the methods according to the first aspect and the embodiments of the first aspect or the second aspect and the embodiments of the second aspect.
Drawings
FIG. 1 is a schematic diagram of a network framework in an embodiment of the present application;
FIG. 2 is a diagram illustrating various types of multiplexing in an embodiment of the present application;
FIG. 3 is a flowchart illustrating a resource allocation method according to an embodiment of the present application;
FIG. 4 is a diagram illustrating a discontinuity of a zeroth class of control resource sets in an embodiment of the present application;
fig. 5.1 to 5.4 are schematic diagrams of frequency domain resources in the embodiment of the present application;
fig. 6.1 to 6.4 are schematic diagrams of frequency domain resources in the embodiment of the present application;
7.1 to 7.3 show the intention of resource allocation in the embodiment of the present application;
fig. 8.1 to 8.4 are schematic diagrams of frequency domain resources in the embodiment of the present application;
fig. 9.1 to 9.4 are schematic diagrams of frequency domain resources in the embodiment of the present application;
FIGS. 10.1 and 10.2 are schematic diagrams of frequency domain resources in an embodiment of the present application;
FIG. 11 is a schematic diagram of frequency domain resources in an embodiment of the present application;
fig. 12.1 and 12.2 are schematic diagrams of frequency domain resources in an embodiment of the present application;
fig. 13 is a schematic structural diagram of a network device in an embodiment of the present application;
fig. 14 is a schematic structural diagram of a terminal device in an embodiment of the present application;
FIG. 15 is a schematic diagram of another structure of a network device in the embodiment of the present application;
fig. 16 is another schematic structural diagram of a terminal device in the embodiment of the present application.
Detailed Description
The embodiment of the application provides a resource allocation method of a broadcast signal.
The technical scheme provided by the embodiment of the application can be applied to various communication systems, such as: a Long Term Evolution (LTE) system, a fifth generation (5G) mobile communication system, a wireless fidelity (WiFi) system, a future communication system, or a system in which multiple communication systems are integrated, which is not limited in the embodiments of the present application. Among them, 5G may also be referred to as New Radio (NR).
The technical scheme provided by the embodiment of the application can be applied to various communication scenes, for example, one or more of the following communication scenes: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), Machine Type Communication (MTC), large-scale Machine Type Communication (MTC), device-to-device (D2D), vehicle-to-evolution (V2X), vehicle-to-vehicle (V2V), and internet of things (IoT), among others.
The technical scheme provided by the embodiment of the application can be applied to communication among communication devices. The communication between the communication devices may include: communication between a network device and a terminal device, communication between a network device and a network device, and/or communication between a terminal device and a terminal device. In the embodiments of the present application, the term "communication" may also be described as "transmission", "information transmission", or "signal transmission", and the like, which is not limited herein. The transmission may include sending and/or receiving. In the embodiment of the present application, a technical solution is described by taking communication between a network device and a terminal device as an example, and those skilled in the art may also use the technical solution to perform communication between other scheduling entities and subordinate entities, for example, communication between a macro base station and a micro base station, for example, communication between a first terminal device and a second terminal device. The scheduling entity may allocate an air interface resource to the subordinate entity. The air interface resources include one or more of the following resources: time domain resources, frequency domain resources, code resources, and spatial resources. In the embodiments of the present application, the plurality of types may be two, three, four, or more, and the embodiments of the present application are not limited.
Referring to fig. 1, fig. 1 is a schematic diagram of an architecture of a communication system to which the embodiment of the present application can be applied, including:
network device 101, terminal device 102.
Network device 101, which may also be referred to as a base station. Currently, some examples of network devices are: a Node B (gnb) that continues to evolve, a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), or a wireless fidelity (Wifi) access point (access point, AP).
In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device, or may be an apparatus capable of supporting the network device to implement the function, for example, a system on chip, and the apparatus may be installed in the network device or used in cooperation with the network device. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, taking a device for implementing a function of a network device as an example, the technical solution provided in the embodiment of the present application is described.
Terminal equipment 102, also referred to as User Equipment (UE), Mobile Station (MS), Mobile Terminal (MT), etc., refers to equipment that provides voice and/or data connectivity to a user. Such as a handheld device, a vehicle-mounted device, etc., having a wireless connection function. Currently, some examples of terminals are: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (smart security), a wireless terminal in city (smart city), a wireless terminal in home (smart home), and the like. It is understood that the number of terminal devices in actual operation is not limited, and may be 3, for example.
In the embodiment of the present application, the apparatus for implementing the function of the terminal device may be the terminal device, or may be an apparatus capable of supporting the terminal device to implement the function, for example, a chip system, and the apparatus may be installed in the terminal device or used in cooperation with the terminal device. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a terminal device is taken as an example of a terminal device, and the technical solution provided in the embodiment of the present application is described.
Three multiplexes of SS/PBCH block and quasi co-located (QCLed) system information block 1(system information block 1, SIB 1)/Remaining Minimum System Information (RMSI) supported by the NR system, see fig. 2, namely pattern1, pattern2 and pattern3, respectively, and for pattern1, the SS/PBCH block and CORESET #0 (or Type0-PDCCH)/PDSCH exist in a time division multiplexing form, and are mainly applied to FR 1; in pattern2, the SS/PBCH block and the PDSCH of QCled exist in a frequency division multiplexing mode; in pattern3, the SS/PBCH block and QCled CORESET #0 (or Type0-PDCCH)/PDSCH exist in a frequency division multiplexing mode. The pattern2 and the pattern3 are mainly used for FR2 and higher frequency bands (including a shared frequency band operating at 60 GHz). in the embodiment of the present application, the configuration of frequency domain resources under the pattern2 and/or the pattern3 is mainly discussed.
With reference to the network framework diagram of fig. 1, a resource allocation method according to an embodiment of the present application includes steps 301 to 303:
301. the method comprises the steps that the network equipment determines frequency domain resources used for sending broadcast signals, the occupied proportion of the frequency domain resources in a system bandwidth is larger than or equal to a preset proportion, and the system bandwidth represents the bandwidth used when the network equipment and the terminal equipment communicate;
in a shared access system of a high frequency band (e.g., 60GHz), a requirement of occupying an Optical Channel Bandwidth (OCB) is required to be satisfied when a network device and a terminal device communicate with each other, that is, in the communication between the network device and the terminal device, a channel to which the network device belongs is occupied by a bandwidth of not less than a preset proportion, where the preset proportion is generally 70%.
In the embodiment of the present application, a Resource Block (RB) occupied by a frequency domain resource for transmitting a broadcast signal is referred to as an occupied resource block. The Resource Block may also be defined as a Physical Resource Block (PRB).
The broadcast signal includes system information and a synchronization information block (SS/PBCH block), the system information being indicated by a control resource set of the zeroth class (core #0 or core #0), the core #0 being transmitted through the Type0 PDCCH.
The resource blocks occupied by the core set #0 may be continuous or discontinuous, in this embodiment, the resource block occupied by the core set #0 is referred to as the core set #0 resource block, when the resource block occupied by the core set #0 is discontinuous, the core set #0 is divided into a plurality of core set #0 sub-blocks, and the content included in the plurality of core set #0 sub-blocks may be the same or different, in this embodiment, the core set #0 sub-block may also be a core set #0 subset, in this embodiment, only the core set #0 sub-block is taken as an example for explanation, refer to fig. 4, the core set #0 includes a plurality of core set #0 sub-blocks 401 to 401, and the interval between adjacent core set #0 sub-blocks is the core set #0 interval 404 to 405.
The offset (offset) between the starting position of the Type 0PDCCH and the starting position of the SS/PBCH block is a first offset, and the occupied resource block is an offset resource block.
Taking multiplexing conditions based on pattern3 as an example, referring to fig. 5.1, when the value of CORESET #0 and the value of the first offset are positive, the frequency domain position of Type 0PDCCH is higher than the SS/PBCH block, otherwise, referring to fig. 5.2, when the value of CORESET #0 and the value of the first offset are negative, the frequency domain position of Type 0PDCCH is lower than the number of CORESET #0 resource blocks in the present embodiment of SS/PBCH block, which is the absolute value of the value of CORESET #0, and the number of offset resource blocks is the absolute value of the first offset. Under the multiplexing condition of pattern2, the value of CORESET #0 and the value of the first offset are similar to the frequency domain location relationship of Type 0PDCCH and SS/PBCH block and the multiplexing condition of pattern3, and are not repeated herein with reference to fig. 5.3 and fig. 5.4.
The occupied resource blocks may include a control resource set0 (CORESET #0) resource block of the zeroth class and an offset resource block (offset).
The following describes two cases of resource block continuous and discontinuous occupied by CORESET #0 respectively:
first, when the resource blocks occupied by the CORESET #0 are continuous, the network device may configure more CORESET #0 resource blocks and/or offset resource blocks to meet the OCB requirement, which is described below by taking the condition based on pattern3 as an example.
1) The network device may configure more CORESET #0 resource blocks, see fig. 5.1 or fig. 5.2.
In the Type 0PDCCH, the CORESET #0 resource block is a Control Channel Element (CCE) unit, 1CCE is 6 Physical Resource Blocks (PRB), the number of CORESET #0 resource blocks may be a1, a1 satisfies a1 ═ 6 × N1, and N1 may take any positive integer from 4 to 60, that is, a1 satisfies a multiple of 6, and may be 24, 48, 72, 96, 120, 126, 288, …, or 360.
The number of CORESET #0 resource blocks may also be a2, a2 satisfies a2 ═ 24 × N2, and N2 may take any positive integer from 1 to 15, that is, a2 may have the same value as 24, 48, 72, 96, 120, 144, 168, 192, 216, 240, 264, 288, or 360.
2) The network device can configure more offset resource blocks, see fig. 6.1 and 6.2.
The number of offset resource blocks may be a multiple of 10, 24, 20, or 6.
When the offset is a multiple of 10, the number of offset resource blocks may be any one of 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200, 210, 220, 230, 240, 250, 260, 270, 280, 290, 300, and so on.
When the number of offset resource blocks is a multiple of 24, and when the CORESET #0 occupies 24 resource blocks in total, the number of offset resource blocks can be equal to 24, 48, 72, 96, 120, 144, 168, 192, 216, 240, or 360, the number of offset resource blocks is 24 × n1, and n1 is any positive integer from 1 to 11; when the CORESET #0 occupies 48 resource blocks, the number of offset resource blocks can be equal to 24, 48, 72, 96, 120, 144, 168, 192, 216, 240 or 300, the number of offset resource blocks is 24 × n2, and n2 is any positive integer from 1 to 10; when CORESET #0 occupies 96 resource blocks, the number of offset resource blocks may be equal to 24, 48, 72, 96, 120, 144, 168, or 192, the number of offset resource blocks is 24 × n3, and n3 is any positive integer from 1 to 8.
When the number of offset resource blocks is a multiple of 20, and when the CORESET #0 occupies 24 resource blocks, the number of offset resource blocks can be equal to 20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 220, 240, 260, or 280, the number of offset resource blocks is 20 × n4, and n4 is any positive integer from 1 to 14; when the CORESET #0 occupies 48 resource blocks, the number of offset resource blocks can be 20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 220, 240, or 260, the number of offset resource blocks is 20 × n5, and n5 is any positive integer from 1 to 13; when CORESET #0 occupies 96 resource blocks, the number of offset resource blocks may be equal to 20, 40, 60, 80, 100, 120, 140, 160, 180, or 200, the number of offset resource blocks is 20 × n6, and n6 is any positive integer from 1 to 10.
When the number of offset resource blocks is a multiple of 6, and when the CORESET #0 occupies 24 resource blocks, the number of offset resource blocks can be equal to 6, 12, …, or 282, the number of offset resource blocks is 6 × n7, and n7 is any positive integer from 1 to 47; when the CORESET #0 occupies 48 resource blocks, the number of offset resource blocks can be equal to 24, 48, 72, 96, 120, 144, 168, 192, 216 or 240, the number of offset resource blocks is 6 × n8, and n8 is any positive integer from 1 to 44; when CORESET #0 occupies 96 resource blocks, the number of offset resource blocks may be equal to 24, 48, 72, 96, 120, 144, 168, or 192, the number of offset resource blocks may be 6 × n9, and n9 is any positive integer from 1 to 19.
3) The network device may configure more CORESET #0 resource blocks and offset resource blocks.
When the number of offset resource blocks is a multiple of 24:
when the CORESET #0 occupies 120 resource blocks, the number of offset resource blocks can be equal to 24, 48, 72, 96, 120, 144 or 168, the number of offset resource blocks is 24 × n10, and n10 is any positive integer from 1 to 7;
when the CORESET #0 occupies 144 resource blocks, the number of offset resource blocks can be equal to 24, 48, 72, 96, 120 or 144, the number of offset resource blocks is 24 × n11, and n11 is any positive integer from 1 to 6;
when the CORESET #0 occupies 168 resource blocks, the number of offset resource blocks can be equal to 24, 48, 72, 96 or 120, the number of offset resource blocks is 4 × n12, and n12 is any positive integer from 1 to 5;
when the core set #0 occupies 192 resource blocks, the number of offset resource blocks can be equal to 24, 48, 72 or 96, the number of offset resource blocks is 24 × n13, and n13 is any positive integer from 1 to 5;
when the CORESET #0 occupies 216 resource blocks, the number of the offset resource blocks can be equal to 24, 48 or 72, the number of the offset resource blocks is 24 multiplied by n14, and the value of n14 is any positive integer from 1 to 3;
when the CORESET #0 occupies 240 resource blocks, the number of offset resource blocks can be equal to 24 or 48, the number of offset resource blocks is 24 × n15, and the value of n15 is 1 or 2;
when the CORESET #0 occupies 264 resource blocks, the number of offset resource blocks may be 24 × n16, and the value of n16 is 1.
When the number of offset resource blocks is a multiple of 20:
when the CORESET #0 occupies 120 resource blocks, the number of offset resource blocks can be 20, 40, 60, 80, 100, 120, 140, 160, 180, the number of offset resource blocks is 20 × n17, and the value of n17 is any positive integer from 1 to 9;
when CORESET #0 occupies 144 resource blocks, the number of offset resource blocks may be 20, 40, 60, 80, 100, 120, 140, 160, etc., the number of offset resource blocks is 20 × n18, and n18 is any positive integer from 1 to 8;
when the CORESET #0 occupies 168 resource blocks, the number of offset resource blocks can be 20, 40, 60, 80, 100, 120, 140, etc., the number of offset resource blocks is 20 × n19, and the value of n19 is any positive integer from 1 to 7;
when the core set #0 occupies 192 resource blocks, the number of offset resource blocks may be 20, 40, 60, 80, 100, etc., the number of offset resource blocks is 20 × n20, and the value of n20 is any positive integer from 1 to 5;
when the CORESET #0 occupies 216 resource blocks, the number of offset resource blocks can be 20, 40, 60, 80, etc., the number of offset resource blocks is 20 × n21, and the value of n21 is any positive integer from 1 to 4;
when the CORESET #0 occupies 240 resource blocks, the number of offset resource blocks can be 20, 40, 60, etc., the number of offset resource blocks is 20 × n22, and the value of n22 is any positive integer from 1 to 3;
when the CORESET #0 occupies 264 resource blocks, the number of offset resource blocks can be equal to 20 or 40, the number of offset resource blocks is 20 × n23, and the value of n23 is 1 or 2;
when CORESET #0 occupies 288 resource blocks, the number of offset resource blocks may be 20, the number of offset resource blocks is 20 × n24, and n24 takes a value of 1.
When the number of offset resource blocks is a multiple of 6: ,
when the CORESET #0 occupies 120 resource blocks, the number of offset resource blocks can be equal to 6, 12, …, or 186, the number of offset resource blocks is 6 × n25, and the value of n25 is any positive integer from 1 to 31;
when the CORESET #0 occupies 44 resource blocks, the number of offset resource blocks can be equal to 6, 12, … or 162, the number of offset resource blocks is 6 × n26, and the value of n26 is any positive integer from 1 to 27;
when the CORESET #0 occupies 168 resource blocks, the number of offset resource blocks can be equal to 6, 12, …, or 138, the number of offset resource blocks is 6 × n27, and the value of n27 is any positive integer from 1 to 23;
when the core set #0 occupies 192 resource blocks, the number of offset resource blocks can be equal to 6, 12, …, or 114, the number of offset resource blocks is 6 × n28, and the value of n28 is any positive integer from 1 to 19;
when the CORESET #0 occupies 216 resource blocks, the number of offset resource blocks can be equal to 6, 12, …, or 90, the number of offset resource blocks is 6 × n29, and the value of n29 is any positive integer from 1 to 15;
when the CORESET #0 occupies 240 resource blocks, the number of offset resource blocks can be equal to 6, 12, … or 66, the number of offset resource blocks is 6 × n30, and the value of n30 is any positive integer from 1 to 11;
when the CORESET #0 occupies 264 resource blocks, the number of offset resource blocks can be equal to 6, 12, … or 42, the number of offset resource blocks is 6 × n31, and n31 takes any positive integer from 1 to 7;
when the CORESET #0 occupies 288 resource blocks, the number of offset resource blocks may be equal to 6, 12, 18, the number of offset resource blocks is 6 × n32, and n32 takes any positive integer from 1 to 3.
When the offset is a multiple of 10, the number of offset resource blocks may be any one of 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 200, 210, 220, 230, 240, 250, 260, 270, 280, 290, 300, and so on.
The network device may generate a resource configuration table, where the resource configuration table includes the Number of resource blocks occupied by core set #0 as Number of RBs and the Number of resource blocks occupied by offset as offset (RBs). When the SSB and Type0 PDCCH/PDSCH employ 240KHz, 480KHz, 960KHz or 1920KHz simultaneously, i.e. in TS38.213, the slot symbols (Set of resource blocks and slots of coordinated Set for Type 0-Type PDCCH search space Set { SS/PBCH block, PDCCH } is {240, 240} KHz, {480, 480} KHz, {960, 960} KHz, or {1920, 1920} KHz) of the resource block and Type 0PDCCH search space Set support two table designs "when the { SS/PBCH block, PDCCH } subcarrier spacing is {240, 240} KHz, {480, 480KHz } 960, KHz } resource configuration table:
1) referring to fig. 7.1, the existing values and the supportable subcarrier spacing (SCS) are integrated into the Table of {120KHz, 120KHz }, i.e. Table 13-8(TS 38.213g10), and the resource block value occupied by CORESET #0 and the resource block value occupied by offset are shown in the schematic Table corresponding to "reserved", and any one or more of {400MHz, 500MHz, 800MHz, 1000MHz, 2000MHz, 2160MHz } are supportable for index #8 to # 15.
2) Referring to FIG. 7.2, the different combinations correspond to different tables such as one or more of {240, 240} KHz, {480, 480} KHz, {960, 960} KHz, {1920, 1920} KHz, etc., and the supportable bandwidths are 400MHz, 500MHz, 800MHz, 1000MHz, 2000MHz, and/or 2160 MHz.
Based on the multiplexing situation of pattern2, the network device may also configure more CORESET #0 resource blocks and/or offset resource blocks to meet the OCB requirement:
1) the CORESET #0 resource block is added, referring to fig. 5.3 and 5.4, the specific configuration is similar to the CORESET #0 resource block added in the multiplexing situation based on pattern3, and details are not repeated here.
2) Referring to fig. 6.3 and 6.4, the specific configuration is similar to that of adding the offset resource block in the multiplexing situation based on pattern3, and details thereof are not repeated here.
3) The CORESET #0 resource block and the offset resource block are added, and the specific configuration manner is similar to that of adding the CORESET #0 resource block and the offset resource block based on the multiplexing situation of pattern3, and the description is omitted here.
Based on multiplexing of pattern2, the resource allocation table may support a table as shown in fig. 7.3, where the resource allocation table includes the number of resource blocks occupied by CORESET #0 and the number of resource blocks occupied by the first offset, and different combinations correspond to different tables: the SSB and the Type 0PDCCH may support one or more of the following combinations {240, 480} KHz, {240, 960} KHz, {240, 1920} KHz, {480, 240} KHz, {480, 960} KHz, {480, 1920} KHz, {960, 240} KHz, {960, 480} KHz, {960, 1920} KHz, {1920, 240} KHz, {1920, 480} KHz, {1920, 960} KHz, and so on. The supportable bandwidths are 400MHz, 500MHz, 800MHz, 1000MHz, 2000MHz, and/or 2160 MHz.
And II, when the resource blocks occupied by the CORESET #0 are discontinuous.
Taking the multiplexing case of pattern3 as an example, referring to fig. 8.1 and 8.2, CORESET #0 has X CORESET #0 sub-blocks, and the interval of the X CORESET #0 sub-blocks is Y CORESET #0 intervals (as shown in fig. 8.1, X is 4, and Y is 5), where X satisfies the condition: and X is A/B, wherein A represents the number of resource blocks occupied by the X CORESET #0 sub-blocks, and the value of the number of the resource blocks satisfies integral multiple of 6 or 24. And B represents the number of the resource blocks occupied by each CORESET #0 subset, the minimum value of the number is 6 or 24, and the values are multiples of 6 and/or multiples of 24 respectively. Taking a as an example, where a is 96 and B is 24, X is 4, i.e., divided into 4 blocks, and the number Y of CORESET #0 intervals is 5. Wherein, the CORESET #0 sub-block can also be called a CORESET #0 subset. Referring to fig. 8.3 and fig. 8.4, in the multiplexing situation based on pattern2, the resource blocks occupied by CORESET #0 may be discontinuous, and the specific configuration rule is similar to that in the multiplexing situation of pattern3, and details thereof are not repeated here.
The network device may determine the resource blocks occupied by the CORESET #0 interval through radio resource management (RRC) signaling or Downlink Control Information (DCI) indication.
Occupied resource blocks may include a CORESET #0 resource block, an offset resource block, and a CORESET #0 spaced resource block.
The number of resource blocks occupied by each CORESET #0 interval may be 6, 5, 4, 3, 2 or 1.
1) The network equipment can be configured with more CORESET #0 resource blocks
The number of CORESET #0 resource blocks may be a21, a21 satisfies a21 ═ 6 × N21, and N21 may take any positive integer from 4 to 60, that is, a21 may have a value of 24, 48, 72, 96, 120, 126, …, or 360.
The number of CORESET #0 resource blocks may also be a22, a22 satisfies a22 ═ 24 × N22, and N22 may take any positive integer from 1 to 15, that is, a22 may have a value of 24, 48, 72, 96, 120, 144, 168, 192, 216, 240, 264, or 360.
2) The network device may configure more resource blocks of offset.
The number of offset resource blocks may be a multiple of 10, 24, 20, or 6.
When the offset value is a multiple of 24, the number of offset resource blocks may take one or more values of 24, 48, 72, 96, 120, 144, 168, 192, 216, 240, or 264;
when the offset value is a multiple of 20, the number of offset resource blocks may take one or more values of 20, 40, 60, 80, 100, 120, 140, 160, 180, 200, 220, 240, 260, …, or 360;
when the offset value is a multiple of 6, the number of offset resource blocks may take one or more values of 6, 12, …, or 360;
when the offset value is a multiple of 10, the number of offset resource blocks may take one or more values of 10, 20, …, or 330.
3) The network device may configure more CORESET #0 resource blocks and offset resource blocks.
At this time, the number of the CORESET #0 resource blocks and the offset resource blocks is similar to that when CORESET #0 is continuous, and the description thereof is omitted.
The configuration of occupying resource blocks in Type0-PDCCH is described above, and the case of PDSCH in the frequency domain is described below.
Referring to fig. 9.1 to 9.4, in the frequency domain, a resource block occupied by the PDSCH and a resource block occupied by CORESET #0 may coexist.
And the network equipment configures the frequency domain position of the PDSCH through CORESET #0, wherein the frequency domain position of the PDSCH comprises the lowest frequency position of the PDSCH and the number of resource blocks occupied by the PDSCH.
For the frequency domain location of PDSCH, according to the definition in TS38.212 g10, may be passed
Figure RE-GDA0002589493220000111
The bit bits are used to indicate that,
Figure RE-GDA0002589493220000112
indicating the number of resource blocks occupied by CORESET # 0. Therefore, the number of resource blocks occupied by PDSCH in the frequency domain changes following the number of resource blocks occupied by CORESET # 0.
The terminal equipment determines the frequency domain position of the PDSCH according to CORESET #0, the frequency domain position of the PDSCH is used for determining a resource indication value RIV (resource indication value), the RIV is used for the number of resource blocks (LRBs) continuously occupied by the PDSCH and the PDSCH is the lowest frequency domain position (RBstart), and the LRBs and the Rbstart meet the following formula.
Figure RE-GDA0002589493220000113
Or the like, or, alternatively,
Figure RE-GDA0002589493220000114
wherein
Figure RE-GDA0002589493220000115
The number of resource blocks occupied for CORESET #0, or,
Figure RE-GDA0002589493220000116
the number of resource blocks occupied by the subsets of the CORESET #0 and/or the number of resource blocks occupied by the CORESET #0 interval are assumed to occupy 48 resource blocks in total in the frequency domain, X is 4, Y is 5RBs, and therefore, the resource blocks are used for calculating RIV
Figure RE-GDA0002589493220000121
And each resource block.
Referring to fig. 10.1 and fig. 10.2, the network device may determine a second offset (offset1) according to the broadcast signal, where the second offset is an offset between a lowest frequency position of the PDSCH and a lowest frequency position of the SS/PBCH block, or the second offset is an offset between a lowest frequency position of the PDSCH and a lowest frequency position of the PDCCH, and a resource block occupied by the second offset is an offset1 resource block, and when the number of resource blocks occupied by the terminal device in combination with the number of resource blocks occupied by the SSB and/or type0-PDCCH channels having a frequency division multiplexing relationship cannot satisfy the OCB requirement, the network device may configure the second offset so that the occupied resource blocks satisfy the OCB requirement.
The PDSCH may be discontinuous, referring to fig. 11, the PDSCH includes multiple PDSCH sub-blocks, the interval between two adjacent PDSCH sub-blocks is a PDSCH interval, and the network device may determine, through RRC signaling or DCI indication, resource blocks occupied by the PDSCH interval, resource blocks occupied by the PDSCH sub-blocks, and/or an upper limit of the resource blocks occupied by the PDSCH sub-blocks, that is, the maximum number of the resource blocks occupied by each PDSCH sub-block. Herein, the PDSCH sub-blocks referred to herein may also be referred to as PDSCH subsets.
Referring to fig. 12.1 and 12.2, when the base station configures the terminal
Figure RE-GDA0002589493220000122
When the OCB requirement cannot be met, a reference signal (others) and the PDSCH may be shared by frequency division multiplexing, and the reference signal may be used for channel quality detection.
302. The network equipment sends a broadcast signal to the terminal equipment; the network device transmits a broadcast signal to the terminal device according to the frequency domain resource configured in step 301.
303. The terminal device demodulates the broadcast signal.
The terminal device obtains the frequency domain resources configured by the network device according to the resource configuration table, such as the resource block occupied by the CORESET #0, the resource block occupied by the first offset, and the like, and the terminal device and the network device communicate according to the various frequency domain resources.
In this configuration, in a shared access system of a high frequency band (e.g., 60GHz), in the communication between a network device and a terminal device, a ratio occupied by frequency domain resources for transmitting a broadcast signal in a system bandwidth is greater than or equal to a preset ratio, and the communication between the network device and the terminal device meets an OCB requirement.
In the above description of the resource allocation method in the embodiment of the present application, referring to fig. 13, the following description of the device in the embodiment of the present application, where an embodiment of the network device 1300 in the embodiment of the present application includes:
a determining unit 1301 is configured to determine a frequency domain resource for transmitting a broadcast signal.
A sending unit 1302, configured to send a broadcast signal to a terminal device.
In this embodiment, operations performed by each unit in the network device are similar to those described in the embodiment shown in fig. 3, and are not described herein again.
Referring to fig. 14, an embodiment of a terminal device 1400 in the embodiment of the present application includes:
a receiving unit 1401 for receiving a broadcast signal from a network device.
A demodulation unit 1402 for demodulating the broadcast signal.
In this embodiment, operations performed by each unit in the network device are similar to those described in the embodiment shown in fig. 3, and are not described herein again.
Fig. 15 is a schematic structural diagram of a network device according to an embodiment of the present application, where the network device 1500 may include one or more processors 1501 and a memory 1505, where the memory 1505 stores one or more applications or data.
Memory 1505 may be volatile storage or persistent storage, among others. The program stored in the memory 1505 may include one or more modules, each of which may include a sequence of instructions operating on a network device. Further, the processor 1501 may be configured to communicate with the memory 1505, to execute a series of instruction operations in the memory 1505 on the network device 1500.
The network apparatus 1500 may also include one or more power supplies 1502, one or more wired or wireless network interfaces 1503, and one or more input-output interfaces 1504.
The processor 1501 may perform the operations performed by the network device in the embodiment shown in fig. 3, which are not described herein again.
Fig. 16 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure, where the terminal device 1600 may include one or more processors 1601 and a memory 1605, and the memory 1605 stores one or more applications or data therein.
The memory 1605 may be volatile storage or persistent storage, among others. The program stored in the memory 1605 may include one or more modules, each of which may include a sequence of instructions operating on the terminal device. Further, the processor 1601 may be configured to communicate with the memory 1605 to execute a series of instruction operations in the memory 1605 on the terminal device 1600.
Terminal apparatus 1600 may also include one or more power supplies 1602, one or more wired or wireless network interfaces 1603, and one or more input-output interfaces 1604.
The processor 1601 may perform the operations performed by the terminal device in the embodiment shown in fig. 3, which is not described herein again.
The present application provides a network device coupled with a memory for reading and executing instructions stored in the memory, so that the network device implements the steps of the method executed by the network device in fig. 3. In one possible design, the network device is a chip or a system on a chip.
The present application provides a terminal device, which is coupled to a memory and configured to read and execute the instructions stored in the memory, so that the network device implements the foregoing steps of the method executed by the network device in fig. 3. In one possible design, the network device is a chip or a system on a chip.
The present application provides a chip system comprising a processor for enabling a network device or a terminal device to implement the functions referred to in the above aspects, e.g. to send or process data and/or information referred to in the above methods. In one possible design, the system-on-chip further includes a memory for storing necessary program instructions and data. The chip system may be formed by a chip, or may include a chip and other discrete devices.
In another possible design, when the chip system is a chip in a network device or a terminal device, the chip includes: a processing unit, which may be for example a processor, and a communication unit, which may be for example an input/output interface, a pin or a circuit, etc. The processing unit may execute the computer executable instructions stored by the storage unit to cause the chip in the network device or the terminal device to perform the steps of the method performed by the network device or the terminal device in the embodiment shown in fig. 3. Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the UE or the base station, and the like, such as a read-only memory (ROM) or another type of static storage device that can store static information and instructions, a Random Access Memory (RAM), and the like.
The embodiments of the present application further provide a processor, coupled to the memory, for performing the method and functions related to the network device in any of the embodiments.
The embodiments of the present application further provide a processor, coupled to the memory, for performing the method and functions related to the terminal device in any of the embodiments.
The embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a computer, implements the method flows related to the network device or the terminal device in any of the above method embodiments. Correspondingly, the computer may be the network device or the terminal device.
It should be understood that the processor mentioned in the network device, the terminal device, the chip system, etc. in the above embodiments of the present application, or the processor provided in the above embodiments of the present application, may be a Central Processing Unit (CPU), and may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It should also be understood that the number of processors in the network device, the terminal device, the chip system, and the like in the above embodiments in the present application may be one or multiple, and may be adjusted according to practical application scenarios, and this is merely an exemplary illustration and is not limited. The number of the memories in the embodiment of the present application may be one or multiple, and may be adjusted according to an actual application scenario, and this is merely an exemplary illustration and is not limited.
It should also be understood that the memories or readable storage media and the like mentioned in the network devices, terminal devices, chip systems and the like in the embodiments of the present application may be volatile memories or nonvolatile memories, or may include both volatile and nonvolatile memories. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
It should be further noted that, when the network device or the terminal device includes a processor (or a processing unit) and a memory, the processor in this application may be integrated with the memory, or the processor and the memory are connected through an interface, and may be adjusted according to an actual application scenario, and is not limited.
The present invention further provides a computer program or a computer program product including the computer program, where when the computer program is executed on a computer, the computer will implement the method flows of any one of the above method embodiments with a network device or a terminal device. Correspondingly, the computer may be the network device or the terminal device.
In the above-described embodiment of fig. 3, the implementation may be wholly or partially implemented by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or other network devices) to execute all or part of the steps of the method according to the embodiment shown in fig. 3 of the present application. And the storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances and are merely descriptive of the various embodiments of the application and how objects of the same nature can be distinguished. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The names of the messages/frames/information, modules or units, etc. provided in the embodiments of the present application are only examples, and other names may be used as long as the roles of the messages/frames/information, modules or units, etc. are the same.
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the embodiments of the present application, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that in the description of the present application, unless otherwise indicated, "/" indicates a relationship where the objects associated before and after are an "or", e.g., a/B may indicate a or B; in the present application, "and/or" is only an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, and may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural.
The word "if" or "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (26)

1. A method for resource allocation, comprising:
the method comprises the steps that network equipment determines frequency domain resources used for sending broadcast signals, the proportion of the frequency domain resources occupied in system bandwidth is larger than or equal to a preset proportion, the broadcast signals comprise system information and a synchronous information block SS/PBCH block, the system information is indicated by a zeroth Type control resource set CORESET #0, and the CORESET #0 is carried in a zeroth Type physical downlink control channel Type 0PDCCH for transmission;
and the network equipment sends the broadcast signal to the terminal equipment.
2. A method for resource allocation, comprising:
the method comprises the steps that terminal equipment receives a broadcast signal from network equipment, the occupied proportion of frequency domain resources used for sending the broadcast signal in a channel is larger than or equal to a preset proportion, the broadcast signal comprises system information and a synchronous information block SS/PBCH block, the system information is indicated by a zeroth Type control resource set CORESET #0, and the CORESET #0 is transmitted through a zeroth Type physical downlink control channel Type0 PDCCH;
and the terminal equipment demodulates the broadcast signal to carry out random access.
3. The method according to claim 1 or 2, wherein the number of resource blocks occupied by the CORESET #0 is 6 xN 1 or 6 xN 2, wherein N1 is any positive integer from 4 to 60, and wherein N2 is any positive integer from 1 to 12.
4. The method according to any one of claims 1 to 3, wherein said CORESET #0 comprises a plurality of CORESET #0 sub-blocks, said plurality of CORESET #0 sub-blocks being discontinuous in the frequency domain.
5. The method of claim 4, wherein information indicating the interval between two adjacent CORESET #0 sub-blocks is carried in radio resource management (RRC) signaling or Downlink Control Information (DCI).
6. The method of any of claims 3 to 5, wherein a first offset is included in the broadcast signal, wherein the first offset is an offset between a lowest frequency location of the Type 0PDCCH and a lowest frequency location of an SS/PBCH block, and wherein resource blocks occupied by the first offset are multiples of 6, 10, 20, or 24.
7. The method of claim 6, further comprising: and the network equipment generates a resource configuration table, wherein the resource configuration table comprises the resource blocks occupied by the CORESET #0 and the resource blocks occupied by the first offset.
8. The method according to any one of claims 1 to 7, wherein the CORESET #0 carries a frequency domain position of a Physical Downlink Shared Channel (PDSCH), and the frequency domain position of the PDSCH comprises a starting frequency position of the PDSCH and a number of resource blocks occupied by the PDSCH.
9. The method of any of claims 1 to 8, wherein a second offset is included in the broadcast signal, wherein the second offset is an offset between a lowest frequency location of the PDSCH and a lowest frequency location of the SS/PBCH block, or wherein the second offset is an offset between a lowest frequency location of the PDSCH and a lowest frequency location of the PDCCH.
10. The method of claim 8 or 9, wherein the PDSCH comprises a plurality of PDSCH sub-blocks, the plurality of PDSCH sub-blocks being non-contiguous in frequency domain.
11. The method of claim 10, wherein information of a gap between two adjacent PDCCH sub-blocks, a resource block occupied by the PDSCH sub-block, and/or an upper limit of the resource block occupied by the PDSCH sub-block is carried in RRC signaling or DCI signaling.
12. The method according to any of claims 1 to 11, wherein the terminal device determines the frequency domain position of the PDSCH according to the CORESET #0, wherein the frequency domain position of the PDSCH is used for determining the resource indication value RIV, and wherein the RIV is used for determining LRBsAnd RBstartSaid L isRBsNumber of resource blocks, the RB, continuously occupied for PDSCHstartIs a starting frequency domain location for the PDSCH;
said LRBsAnd said RBstartThe following formula is satisfied:
Figure FDA0002494592420000021
or the like, or, alternatively,
Figure FDA0002494592420000022
the above-mentioned
Figure FDA0002494592420000023
The number of resource blocks occupied by the CORESET #0, or
Figure FDA0002494592420000024
The number of resource blocks occupied by the plurality of CORESET #0 sub-blocks and/or the number of resource blocks occupied by the CORESET #0 sub-blocks at intervals.
13. A network device, comprising:
the device comprises a determining unit, a transmitting unit and a receiving unit, wherein the determining unit is used for determining frequency domain resources used for transmitting broadcast signals, the proportion of the frequency domain resources occupied in system bandwidth is greater than or equal to a preset proportion, the broadcast signals comprise system information and a synchronous information block SS/PBCH block, the system information is indicated by a zeroth Type control resource set CORESET #0, and the CORESET #0 is carried in a zeroth Type physical downlink control channel Type 0PDCCH for transmission;
a sending unit, configured to send the broadcast signal to the terminal device.
14. A terminal device, comprising:
the receiving unit is used for receiving a broadcast signal from network equipment, wherein the occupied proportion of the frequency domain resource used for sending the broadcast signal in the channel is greater than or equal to a preset proportion, the broadcast signal comprises system information and a synchronous information block SS/PBCH block, the system information is indicated by a zeroth Type control resource set CORESET #0, and the CORESET #0 is transmitted through a zeroth Type physical downlink control channel Type0 PDCCH;
a demodulation unit for demodulating the broadcast signal for random access.
15. The apparatus according to claim 13 or 14, wherein the number of resource blocks occupied by CORESET #0 is 6 × N1 or 6 × N2, wherein N1 is any positive integer from 4 to 60, and wherein N2 is any positive integer from 1 to 12.
16. The apparatus according to any one of claims 13 to 15, wherein said CORESET #0 comprises a plurality of CORESET #0 sub-blocks, said plurality of CORESET #0 sub-blocks being discontinuous in the frequency domain.
17. The apparatus of claim 16, wherein information indicating the interval between two adjacent CORESET #0 sub-blocks is carried in radio resource management (RRC) signaling or Downlink Control Information (DCI).
18. The apparatus of any of claims 15-17, wherein a first offset is included in the broadcast signal, wherein the first offset is an offset between a lowest frequency location of the Type 0PDCCH and a lowest frequency location of an SS/PBCH block, and wherein resource blocks occupied by the first offset are multiples of 6, 10, 20, or 24.
19. The apparatus of claim 18, wherein the method further comprises: the network device comprises a generating unit, configured to generate a resource configuration table, where the resource configuration table includes the resource block occupied by the CORESET #0 and the resource block occupied by the first offset.
20. The apparatus according to any one of claims 13 to 19, wherein the CORESET #0 carries a frequency domain position of a physical downlink shared channel PDSCH, and the frequency domain position of the PDSCH includes a starting frequency position of the PDSCH and a number of resource blocks occupied by the PDSCH.
21. The apparatus of any of claims 13-20, wherein a second offset is included in the broadcast signal, wherein the second offset is an offset between a lowest frequency location of the PDSCH and a lowest frequency location of the SS/PBCH block, or wherein the second offset is an offset between a lowest frequency location of the PDSCH and a lowest frequency location of the PDCCH.
22. The apparatus of claim 19 or 20, wherein the PDSCH comprises a plurality of PDSCH sub-blocks, the plurality of PDSCH sub-blocks being non-contiguous in frequency domain.
23. The apparatus of claim 22, wherein information of a gap between two adjacent PDCCH sub-blocks, a resource block occupied by the PDSCH sub-block, and/or an upper limit of the resource block occupied by the PDSCH sub-block is carried in RRC signaling or DCI signaling.
24. The device according to any of claims 13 to 23, wherein the terminal device comprises a determining unit configured to determine a frequency domain location of the PDSCH according to the CORESET #0, wherein the frequency domain location of the PDSCH is used to determine a resource indication value RIV, and wherein the RIV is used to determine LRBsAnd RBstartSaid L isRBsNumber of resource blocks, the RB, continuously occupied for PDSCHstartIs a starting frequency domain location for the PDSCH;
said LRBsAnd said RBstartThe following formula is satisfied:
Figure FDA0002494592420000031
or the like, or, alternatively,
Figure FDA0002494592420000032
the above-mentioned
Figure FDA0002494592420000033
The number of resource blocks occupied by the CORESET #0, or
Figure FDA0002494592420000034
The number of resource blocks occupied by the plurality of CORESET #0 sub-blocks and/orThe number of resource blocks occupied by the CORESET #0 interval.
25. A computer-readable storage medium for storing a computer program, characterized in that the computer program comprises instructions for implementing the method of any of the preceding claims 1 to 12.
26. A computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to carry out the method of any one of claims 1 to 12.
CN202010414667.1A 2020-05-15 2020-05-15 Resource allocation method of broadcast signal and related device Pending CN113677004A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010414667.1A CN113677004A (en) 2020-05-15 2020-05-15 Resource allocation method of broadcast signal and related device
PCT/CN2021/093291 WO2021228130A1 (en) 2020-05-15 2021-05-12 Resource configuration method for broadcast signal, and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010414667.1A CN113677004A (en) 2020-05-15 2020-05-15 Resource allocation method of broadcast signal and related device

Publications (1)

Publication Number Publication Date
CN113677004A true CN113677004A (en) 2021-11-19

Family

ID=78525279

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010414667.1A Pending CN113677004A (en) 2020-05-15 2020-05-15 Resource allocation method of broadcast signal and related device

Country Status (2)

Country Link
CN (1) CN113677004A (en)
WO (1) WO2021228130A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115002814A (en) * 2022-06-09 2022-09-02 中国联合网络通信集团有限公司 Resource load determination method, device and storage medium

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107889238B (en) * 2016-09-30 2021-04-20 华为技术有限公司 Resource configuration method, network equipment and terminal equipment
CN109150265B (en) * 2017-06-15 2021-08-31 华为技术有限公司 Method for sending and receiving reference signal, network equipment and terminal equipment
CN107911203B (en) * 2017-08-11 2023-11-14 华为技术有限公司 Method, network device, terminal device and system for transmitting and receiving reference signal
CN109802801B (en) * 2017-11-17 2021-12-14 华为技术有限公司 Method, device and system for transmitting and receiving signals
CN110830219B (en) * 2018-08-14 2021-03-30 成都华为技术有限公司 Resource management method and device
CN110971322B (en) * 2018-09-30 2022-02-15 维沃移动通信有限公司 Information transmission method, network equipment and terminal

Also Published As

Publication number Publication date
WO2021228130A1 (en) 2021-11-18

Similar Documents

Publication Publication Date Title
CN109600832B (en) Paging message transmission method and device
EP4181453A1 (en) Method for transmitting synchronization signal block, and communication apparatus
US11626964B2 (en) Data transmission method, network device, and terminal device
US20170195995A1 (en) Device-to device (d2d) synchronization message signaling
US11477307B2 (en) Media access control protocol data unit processing method and apparatus
CN112088566A (en) Method and apparatus for downlink control information size alignment in mobile communication
CN109792672B (en) Data transmission method, network equipment and terminal equipment
TWI680654B (en) Method and ap paratus for trans port block size determination
EP3952585A1 (en) Random access preamble sending method, and communication apparatus
CN109600839B (en) Indication method, determination method, sending equipment and receiving equipment
KR20220092967A (en) Link identifier indication method, transmission/reception capability indication method, and related devices
CN111418248B (en) Enhancing new radio PUSCH for URLLC in mobile communications
WO2021031939A1 (en) Data transmission method and device
TW201841529A (en) Methods for downlink control signal design in mobile communications
US20230049307A1 (en) Device-to-Device Based Resource Determining Method and Device
CN113169815A (en) Channel occupancy time indication for NR-based unlicensed operation
WO2019062149A1 (en) Method for processing physical downlink control channel, and related devices
WO2020199790A1 (en) Information indication method and communication apparatus
WO2021228130A1 (en) Resource configuration method for broadcast signal, and related device
CN111385880B (en) Method and device for determining time domain resources
CN112005597A (en) Frequency domain resource allocation for compact downlink control information in mobile communications
US11477793B2 (en) Information transmission method and device
EP3917244A1 (en) Method and device for signal transmission
EP4319373A1 (en) Wireless communication method, first device, and second device
US20240040510A1 (en) Explicit power saving operations for a network-controlled repeater (ncr) in wireless communications

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination