Indication of resource location, receiving method and apparatus

Abstract

The application provides a resource position indication method and device. The method comprises: a first type of node sending resource position information to a second type of node, the resource position information being used for at least indicating a frequency domain position of a resource; wherein the frequency domain position comprises at least one of: a frequency domain position of a first resource, a frequency domain position of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a physical downlink shared channel (PDSCH) occupied resource, a common control resource set (CORESET). Through the application, the problem that a base station cannot indicate the resource position of a BWP, a PDSCH and a common CORESET in the related art is solved, and the technical effect that the resource position can be effectively indicated is achieved.

Description

[0001] This application is a divisional application of the Chinese Patent Application No. 201710687231.8, filed on August 11, 2017, entitled "Indication of Resource Position, Receiving Method and Device". TECHNICAL FIELD

[0002] The present application relates to the field of communication, in particular to an indication of resource position, receiving method and device. BACKGROUND

[0003] In future wireless communication systems (e.g. 5G), higher carrier frequencies than those used in the fourth generation communication system will be used for communication, such as 28GHz, 45GHz, etc., and the 5G new radio access technology (RAT) system potentially works up to 100GHz. Since the carrier frequency corresponding to high frequency communication has a shorter wavelength, more antenna elements can be accommodated in a unit area, and more antenna elements mean that beamforming method can be used to improve antenna gain, thereby ensuring the coverage performance of high frequency communication.

[0004] After using the beamforming method, the transmitting end can concentrate the transmitting energy in a certain direction, and the energy in other directions is very small or even zero, that is, each beam has its own directivity, and each beam can only cover the terminals in a certain direction. The transmitting end, i.e. the base station, needs to transmit beams in dozens or even hundreds of directions to complete the omnidirectional coverage. In the prior art, the initial beam direction measurement and identification in the process of terminal initial access to the network is inclined, and the base station side transmitting beams are polled in a time interval for the terminal to measure and identify the preferred beam or port. Specifically, in a synchronization signal transmission period, there are multiple synchronization signal blocks (SS blocks), each SS block carries a synchronization signal of a specific beam / port (group), and a synchronization signal transmission period completes a beam sweep, i.e. the transmission of all beams / ports.

[0005] In the prior art, the physical carrier center frequency (i.e. the direct current frequency) is placed at the frequency domain position corresponding to each channel number. The frequency interval between adjacent channel numbers is called the channel raster or carrier raster interval. The frequency domain step size of the terminal searching for the synchronization signal is called the frequency raster or UE raster interval. In the LTE system, the UE raster interval is the same as the channel raster interval, i.e. the terminal searches for the synchronization signal at the frequency domain position corresponding to all possible channel numbers (i.e. channel numbers),Figure 1 is a schematic diagram of the prior art in which the terminal raster is the same as the channel raster, as shown in Figure 1 .

[0006] In NR, in order to make the spectrum deployment more flexible and reduce the complexity of the terminal frequency domain search, the industry proposes to use a larger terminal raster interval, that is, the terminal raster interval can be greater than the channel raster interval. In this case, the center frequency point of the synchronization signal, broadcast channel or other related signals / channels is likely to be different from the center frequency point of the physical carrier. The minimum carrier bandwidth and synchronization bandwidth have been determined in the current standard discussion, which means that the maximum value of the terminal raster interval is determined, and the minimum value of the terminal raster interval is greater than or equal to the channel raster interval. If the terminal raster interval takes an intermediate value, since the NR system bandwidth is usually large, a physical carrier bandwidth may contain multiple SS blocks in the frequency domain.

[0007] In addition, the working bandwidth of high frequency communication is usually high, up to several hundred MHz, in order to reduce the resource scheduling overhead and also to enable terminals with small bandwidth capability to communicate normally, the prior art has proposed to divide the physical carrier bandwidth of the future wireless communication system (New Radio, referred to as NR) into multiple bandwidth parts (Bandwidth part, referred to as BWP), and schedule resources for data transmission for the terminal or transmit broadcast type information to the terminal within the BWP. Instead of scheduling the terminal or transmitting broadcast type information to the terminal within the entire physical carrier as in LTE. In NR, the common control information carried in the common control resource set common CORESET(s) is very important information, for example, paging, part of the UE specific control information and part of the broadcast type information are related to the common control information, and the frequency spectrum resources scheduled by the common CORESET(s) need to be in a certain BWP or physical downlink shared channel (Physical Downlink Shared Channel, referred to as PDSCH) resource, therefore, how the base station indicates the resource location of the BWP, PDSCH and common CORESET(s) is crucial.

[0008] Therefore, the base station in the prior art cannot indicate the resource location of the BWP, PDSCH and common CORESET(s), and no effective solution has been proposed for this problem. SUMMARY

[0009] The embodiments of the present application provide a resource location indication and receiving method and device to at least solve the problem that the base station in the prior art cannot indicate the resource location of the BWP, PDSCH and common CORESET(s).

[0010] According to one embodiment of the present application, a method for indicating resource location is provided, comprising: a first type of node sending resource location information to a second type of node, the resource location information being used for indicating at least frequency domain location of a resource; wherein the frequency domain location comprises at least one of: frequency domain location of a first resource, frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a physical downlink shared channel (PDSCH) occupied resource, a common control resource set.

[0011] Optionally, the frequency domain location of the first resource is frequency domain location of a configured synchronization signal block (SS block); and the frequency domain location of the second resource is frequency domain location of a common control resource set.

[0012] Optionally, the common control resource set is contained in a BWP or a PDSCH occupied resource; or the common control resource set partially overlaps with a BWP or a PDSCH occupied resource; or the common control resource set does not partially overlap with a BWP or a PDSCH occupied resource; or there is no fixed relationship between the common control resource set and a BWP or a PDSCH occupied resource.

[0013] Optionally, control information carried by the common control resource set schedules a resource within a BWP or a PDSCH occupied resource.

[0014] Optionally, the first type of node indicating the frequency domain location of the first resource to the second type of node comprises: indicating offset of the first resource in the frequency domain relative to a reference point; or indicating offset of the first resource in the frequency domain relative to a reference point and bandwidth of the first resource; wherein the reference point comprises center or boundary of any one of: a physical carrier, a downlink synchronization signal bandwidth, a downlink synchronization signal block (SS block).

[0015] Optionally, the first type of node indicating the frequency domain location of the second resource to the second type of node comprises: indicating offset of the second resource in the frequency domain relative to a reference point or the first resource; or indicating offset of the second resource in the frequency domain relative to a reference point or the first resource and bandwidth of the second resource or relationship between bandwidth of the second resource and bandwidth of the first resource; wherein the reference point comprises center or boundary of any one of: a physical carrier, a downlink synchronization signal bandwidth, a downlink synchronization signal block (SS block).

[0016] Optionally, indicating the frequency domain location of the BWP comprises indicating index of the BWP.

[0017] Optionally, the manner of determining the frequency domain position of the first resource as the frequency domain position of a configured synchronization signal block (SS block) comprises: the first type of node configuring one or more SS blocks in a system bandwidth, wherein the frequency domain position of each SS block corresponds to an index; and configuring the frequency domain position of the first resource as one of the frequency domain positions of the one or more SS blocks.

[0018] Optionally, the indication of the frequency domain position of the configured SS block comprises: indication of the index of the frequency domain position of the configured SS block.

[0019] Optionally, the indication by the first type of node to the second type of node of the frequency domain position of the resource comprises: carrying the resource position information by the first type of node using a physical broadcast channel; or carrying the resource position information by the first type of node using radio resource control (RRC) dedicated signaling; or carrying the frequency domain position information of the first resource by the first type of node using a physical broadcast channel, and carrying the frequency domain position information of the second resource using RRC dedicated signaling, or carrying part of the frequency domain position information of the first resource and / or the frequency domain position information of the second resource using a physical broadcast channel and carrying the other part using RRC signaling.

[0020] Optionally, the RRC dedicated signaling is sent by a node adjacent to the first type of node to the second type of node.

[0021] Optionally, the offset in the frequency domain comprises at least one of: an offset amount, a left-right offset indication.

[0022] Optionally, the offset amount in the frequency domain is represented by one or more of: a relative channel number, a relative channel group number, a relative physical resource block (PRB) number, a relative PRB group number, a relative subcarrier number.

[0023] Optionally, the frequency domain position of the resource is a center position of the resource in the frequency domain; or the frequency domain position of the resource is a boundary position of the resource in the frequency domain; or the frequency domain position of the resource is a center position of the resource in the frequency domain and a bandwidth of the frequency domain resource; or the frequency domain position of the resource is a boundary position of the resource in the frequency domain and a bandwidth of the frequency domain resource; or the frequency domain position of the resource is a bandwidth of the frequency domain resource.

[0024] According to another embodiment of the present application, a method for receiving resource location is provided, comprising: receiving, by a second type of node, resource location information sent by a first type of node, the resource location information being used for indicating frequency domain location of a resource; wherein the frequency domain location comprises at least one of: frequency domain location of a first resource, frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a physical downlink shared channel (PDSCH) occupied resource, a common control resource set.

[0025] Optionally, the frequency domain location of the first resource is a frequency domain location of a configured synchronization signal block (SS block); and the frequency domain location of the second resource is a frequency domain location of a common control resource set.

[0026] Optionally, the method further comprises: receiving, by the second type of node, the frequency domain location of the first resource indicated by the first type of node, and determining the frequency domain location of the second resource according to a predefined rule.

[0027] Optionally, the predefined rule is a relationship between one or more factors and a frequency domain offset, wherein the factors comprise at least one of: a synchronization signal block index, a physical cell identity, a system frame number, and frequency band information.

[0028] According to another embodiment of the present application, an apparatus for indicating resource location is provided, applied to a first type of node, comprising: a sending module, configured to send, to a second type of node, resource location information, the resource location information being used for indicating at least a frequency domain location of a resource; wherein the frequency domain location comprises at least one of: frequency domain location of a first resource, frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a physical downlink shared channel (PDSCH) occupied resource, a common control resource set.

[0029] Optionally, the frequency domain location of the first resource is a frequency domain location of a configured synchronization signal block (SS block); and the frequency domain location of the second resource is a frequency domain location of a common control resource set.

[0030] According to another embodiment of the present application, an apparatus for receiving resource location is provided, applied to a second type of node, comprising: a receiving module, configured to receive resource location information sent by a first type of node, the resource location information being used for indicating frequency domain location of a resource; wherein the frequency domain location comprises at least one of: frequency domain location of a first resource, frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a physical downlink shared channel (PDSCH) occupied resource, a common control resource set.

[0031] Optionally, the frequency domain position of the first resource is the frequency domain position of the configured synchronization signal block SS block; the frequency domain position of the second resource is the frequency domain position of the public control resource set.

[0032] According to yet another embodiment of the present invention, a storage medium is provided. The storage medium includes a stored program, wherein the program executes any one of the above methods when running.

[0033] According to yet another embodiment of the present invention, a processor is provided, which is configured to run a program, wherein the program executes any one of the above methods when running.

[0034] Through the present invention, a first-type node sends resource location information to a second-type node. This resource location information is used to indicate at least the frequency domain location of the resource. The frequency domain location includes at least one of the following: the frequency domain location of the first resource, the frequency domain location of the second resource; and the first resource or the second resource includes at least one of the following: a bandwidth part (BWP), resources occupied by a physical downlink shared channel (PDSCH), or a common control resource set (CRES). In other words, by sending resource location information from the first-type node to the second-type node to indicate the frequency domain location of the resource, the problem in the prior art where base stations are unable to indicate the resource locations of BWP, PDSCH, and common CORESET(s) is resolved, achieving the technical effect of effectively indicating the resource location. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0036] Figure 1 Schematic diagram of the terminal grid and the channel grid being the same in the prior art;

[0037] Figure 2 is a flow chart of a method for indicating a resource location according to an embodiment of the present invention;

[0038] Figure 3 2 is a schematic diagram of the frequency domain positions of the SS block, BWP, and Common CORESET in the NR carrier according to an embodiment of the present invention;

[0039] Figure 4 1 is a schematic diagram of the frequency domain position of the SS block, BWP, and Common CORESET in the NR carrier according to an embodiment of the present invention (I);

[0040] Figure 5is a schematic diagram of frequency domain positions of a SS block, a BWP and a Common CORESET in a NR carrier according to an embodiment of the present application (two);

[0041] Figure 6 is a schematic diagram of an indication method of resource positions according to an embodiment of the present application;

[0042] Figure 7 is a schematic diagram of an indication method of resource positions according to an embodiment of the present application (one);

[0043] Figure 8 is a schematic diagram of an indication method of resource positions according to an embodiment of the present application (two);

[0044] Figure 9 is a schematic diagram of an indication method of resource positions according to an embodiment of the present application (three);

[0045] Figure 10 is a schematic diagram of an indication method of resource positions according to an embodiment of the present application (four);

[0046] Figure 11 is a schematic diagram of an indication method of resource positions according to an embodiment of the present application (five);

[0047] Figure 12 is a structural block diagram of an indication device of resource positions according to an embodiment of the present application;

[0048] Figure 13 is a flow chart of a receiving method of resource positions according to an embodiment of the present application;

[0049] Figure 14 is a structure of a receiving device of resource positions according to an embodiment of the present application;

[0050] Figure 15 is a structural block diagram of a base station according to an embodiment of the present application;

[0051] Figure 16 is a structural block diagram of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0052] Hereinafter, the present application will be described in detail with reference to the accompanying drawings and embodiments. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0053] It should be noted that the terms "first", "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence.

[0054] Embodiment 1

[0055] In this embodiment, a method for indicating a resource location is provided. Figure 2 FIG. 1 is a flow chart of a method for indicating a resource location according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0056] In step S202, the first type of node sends resource location information to the second type of node, where the resource location information is at least used to indicate the frequency domain location of the resource; wherein the frequency domain location includes at least one of the following: the frequency domain location of the first resource, the frequency domain location of the second resource; the first resource or the second resource includes at least one of the following: a bandwidth part BWP, resources occupied by a physical downlink shared channel PDSCH, and a public control resource set.

[0057] Optionally, the first type of node executing the above steps may be a base station, specifically, a transmit-receive point (TRP), a relay node, a macro base station, a micro base station, a pico base station, a home base station, a remote radio frequency, an access point (AP), etc. Examples of the second type of node include a terminal and a relay node. In the following embodiments, the first type of node takes a base station as an example, and the second type of node takes a terminal as an example, but is not limited thereto.

[0058] Through the above step S202, the problem in the related art that the base station cannot indicate the resource locations of BWP, PDSCH and commonCORESET(s) is solved, and the technical effect of effectively indicating the resource locations is achieved.

[0059] Optionally, the frequency domain position of the first resource is the frequency domain position of the configured synchronization signal block SS block; the frequency domain position of the second resource is the frequency domain position of the public control resource set.

[0060] Optionally, the above-mentioned public control resource set is included in the resources occupied by BWP or PDSCH; or, the public control resource set partially overlaps with the resources occupied by BWP or PDSCH; or, the public control resource set does not overlap with the resources occupied by BWP or PDSCH at all; or, there is no fixed relationship between the public control resource set and the resources occupied by BWP or PDSCH.

[0061] Optionally, the resources scheduled by the control information carried by the above-mentioned common control resource set are located within the resources occupied by the BWP or PDSCH.

[0062] In an optional implementation manner, the first type node indicates the frequency domain position of the first resource to the second type node in the following manner:

[0063] Indicates the offset of the first resource relative to the reference point in the frequency domain; or indicates the offset of the first resource relative to the reference point in the frequency domain and the bandwidth of the first resource;

[0064] It should be noted that the above reference points include the center or boundary of any one of the following: physical carrier, downlink synchronization signal bandwidth, downlink synchronization signal block SS block.

[0065] In an optional implementation manner, the first type node indicates the frequency domain position of the first resource to the second type node in the following manner:

[0066] Indicates an offset of the second resource relative to the reference point or the first resource in the frequency domain; or indicates an offset of the second resource relative to the reference point or the first resource in the frequency domain, and a bandwidth of the second resource or a relationship between the bandwidth of the second resource and the bandwidth of the first resource;

[0067] It should be noted that the above reference points include the center or boundary of any one of the following: physical carrier, downlink synchronization signal bandwidth, downlink synchronization signal block SS block.

[0068] Optionally, indicating the frequency domain position of the BWP includes indicating an index of the BWP.

[0069] In an optional embodiment, the method of determining the frequency domain position of the first resource as the frequency domain position of the configured synchronization signal block SSblock includes: the first type of node configures one or more SS blocks within the system bandwidth, wherein the frequency domain position of each SS block corresponds to an index; and configuring the frequency domain position of the first resource to be one of the frequency domain positions of the one or more SS blocks.

[0070] Optionally, indicating the frequency domain position of the configured SS block includes: indicating a frequency domain position index of the configured SS block.

[0071] In an optional embodiment, the first type of node indicates the frequency domain position of the resource to the second type of node, including: the first type of node uses a physical broadcast channel to carry the above-mentioned resource location information; or, the first type of node uses wireless resource control RRC to carry the above-mentioned resource location information; or, the first type of node uses a physical broadcast channel to carry the frequency domain location information of the first resource, and uses RRC dedicated signaling to carry the frequency domain location information of the second resource, or, part of the frequency domain position of the first resource and / or the frequency domain location information of the second resource is carried by a physical broadcast channel, and the other part is carried by RRC signaling.

[0072] Optionally, the RRC dedicated signaling is sent by a node adjacent to the first type of node to the second type of node.

[0073] Optionally, the offset in the frequency domain includes at least one of the following: an offset amount, a left-right offset indication.

[0074] Optionally, the offset amount in the frequency domain is represented by one or more of the following: a relative channel number, a relative channel group number, a relative physical resource block (PRB) number, a relative PRB group number, a relative subcarrier number.

[0075] In an optional embodiment, the frequency domain location of the resource is a center location of the resource in the frequency domain; or the frequency domain location of the resource is a boundary location of the resource in the frequency domain; or the frequency domain location of the resource is a center location of the resource in the frequency domain and a bandwidth of the frequency domain resource; or the frequency domain location of the resource is a boundary location of the resource in the frequency domain and a bandwidth of the frequency domain resource; or the frequency domain location of the resource is a bandwidth of the frequency domain resource.

[0076] The present embodiment is described below in conjunction with specific examples.

[0077] It should be noted that in the following optional embodiments, the relative channel (group) / PRB (group) / subcarrier number: generally, the relative channel (group) / PRB (group) / subcarrier number of A relative to B refers to the number of channel grids (groups) / PRB (groups) / subcarriers that the frequency domain location of A differs from the frequency domain location of B.

[0078] Left-right offset of A relative to B in the frequency domain: when the frequency domain location of A is higher than the frequency domain location of B, it is a right offset; when the frequency domain location of A is lower than the frequency domain location of B, it is a left offset.

[0079] Optional Embodiment 1

[0080] This optional embodiment describes indicating the frequency domain locations of the first and second resources using the offset in the frequency domain relative to a reference point.

[0081] As Figure 3 The frequency domain locations of the SS block, BWP, and Common CORESET in the NR carrier are given, where n is the channel number corresponding to the center frequency point of the SS block, m is the channel number corresponding to the center frequency point of the BWP, and m+k is the channel number corresponding to the center frequency point of the Common CORESET.

[0082] Specifically, the base station can schedule the BWP or a part of the BWP resource by the physical downlink control channel (PDCCH) carried by the Common CORESET, the first resource is taken as an example of the BWP, the second resource is taken as an example of the Common CORESET, and the reference point is taken as an example of the center of the SS block. In this embodiment, the base station indicates the terminal the offset and of the center frequency of the BWP and the Common CORESET relative to the center frequency of the SS block and the bandwidth of the BWP and the Common CORESET, and the specific indication includes the relative channel number, the left-right offset indication and the bandwidth, as shown in Table 1. The relative channel number is the number of channel grids between the frequency domain position of the center frequency of the BWP or the Common CORESET and the frequency domain position of the center frequency of the SS block. The left-right offset indication is an indication of whether the center frequency of the BWP or the Common CORESET is left offset or right offset relative to the center frequency of the SS block. When the center frequency of the BWP or the Common CORESET is higher than the center frequency of the SS block, it is right offset. When the center frequency of the BWP or the Common CORESET is lower than the center frequency of the SS block, it is left offset.

[0083] Table 1

[0084]

[0085] Preferably, the base station can send the terminal the information such as the offset of the center frequency of the BWP and the Common CORESET relative to the center frequency of the SS block, the left-right offset indication and the bandwidth of the BWP and the Common CORESET by the physical broadcast channel or the RRC dedicated signaling, or part of the physical broadcast channel and part of the RRC dedicated signaling.

[0086] Preferably, the RRC dedicated signaling can also be sent to the terminal by the adjacent base station.

[0087] The offset of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block using the relative channel number is only an example. If the frequency difference between the center frequency of the BWP or the Common CORESET and the center frequency of the SS block is not an integer multiple of the channel raster, the offset of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block cannot be accurately represented using only the relative channel number, and other methods need to be considered.

[0088] The offset of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block can also be represented using the relative subcarrier number of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block, where the relative subcarrier number refers to the number of subcarriers between the frequency domain position of the center frequency of the BWP or the Common CORESET and the frequency domain position of the center frequency of the SS block, and the center frequency of the BWP or the Common CORESET is higher than the center frequency of the SS block, which is a right offset, and the center frequency of the BWP or the Common CORESET is lower than the center frequency of the SS block, which is a left offset. For example, the frequency domain of the center frequency of the BWP is higher than the frequency of the center frequency of the SS block (the subcarriers are numbered in ascending order from low frequency to high frequency), and the difference between them is K subcarriers, then the offset of the center frequency of the BWP relative to the center frequency of the SS block is the relative subcarrier number K, and it is a right offset; or,

[0089] represented using the relative PRB number of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block; or,

[0090] represented using the relative PRB number of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block, and the relative subcarrier number of the center frequency of the BWP or the Common CORESET relative to the frequency domain position corresponding to the relative PRB number; or,

[0091] represented using the relative channel number of the center frequency of the BWP or the Common CORESET relative to the center frequency of the SS block, and the relative subcarrier number of the center frequency of the BWP or the Common CORESET relative to the frequency domain position corresponding to the relative channel number; or,

[0092] The relative channel number of the center frequency point of the BWP or Common CORESET relative to the center frequency point of the SS block and the relative PRB number of the center frequency point of the BWP or Common CORESET relative to the frequency domain position corresponding to the relative channel number are used to represent; or

[0093] The relative channel number of the center frequency point of the BWP or Common CORESET relative to the center frequency point of the SS block and the relative PRB number of the center frequency point of the BWP or Common CORESET relative to the frequency domain position corresponding to the relative channel number, and the relative subcarrier number of the center frequency point of the BWP or Common CORESET relative to the frequency domain position corresponding to the relative PRB number are used to represent.

[0094] The bandwidths of the first resource and the second resource are not limited to the indication method in Table 1, and N1 bandwidths can be predefined, so that the bandwidth of a certain resource can be represented by log2(N1) bits of information, such as 4 bandwidths: 100 RBs, 50 RBs, 30 RBs, and 20 RBs. The bandwidth of a certain resource can be represented by 2 bits of information.

[0095] If the bandwidth of the BWP is fixed, such as 50 RBs, the base station does not need to indicate the bandwidth of the BWP to the terminal. Similarly, if the bandwidth of the Common CORESET is fixed, such as 20 RBs, the base station does not need to indicate the bandwidth of the Common CORESET to the terminal. That is, the base station only needs to indicate the offset of the center frequency point of the BWP or Common CORESET relative to the center frequency point of the SS block to the terminal.

[0096] In addition, if the offset of the center frequency point of the BWP or Common CORESET relative to the center frequency point of the SS block is fixed, for example, the offset and the left and right offsets are fixed, the base station only needs to indicate the size of the bandwidth to the terminal. If only the offset is fixed, it only needs to indicate whether it is left offset or right offset, and the size of the bandwidth.

[0097] In addition, the position of the BWP or Common CORESET can also be indicated by the offset of the boundary (for example, the left boundary, that is, the starting frequency domain position, or the right boundary, that is, the ending frequency domain position) of the BWP or Common CORESET relative to the center frequency point of the SS block, which can be represented by the number of RBs offset relative to the reference point, for example, an offset of 0 RBs means that the center frequency point position coincides with the center frequency point position of the SS block, and the indication method is similar to the indication method of the offset of the center frequency point of the BWP or Common CORESET relative to the center frequency point of the SS block.

[0098] Specifically, the center or the boundary (e.g. the left boundary, i.e. the starting frequency domain position, or the right boundary, i.e. the ending frequency domain position) of the BWP or the Common CORESET can be indicated by a 1-bit left or right shift indication and a resource indication value (RIV), and the bandwidth of the BWP or the bandwidth of the Common CORESET.

[0099] The bandwidth of the RB can be determined according to the subcarrier spacing adopted by the SS block, or can be determined according to the subcarrier spacing notified by the PBCH or the minimum system information (RMSI) or the RRC dedicated signaling. One RB contains 12 subcarriers in the frequency domain.

[0100] In addition, it should be noted that the base station indicates the resources to the terminal in the following two cases in a similar manner to the above embodiments: 1) the first resource is the resource occupied by the downlink data channel PDSCH, and the second resource is the Common CORESET; 2) the first resource is the Common CORESET, and the second resource is the BWP or the resource occupied by the downlink data channel PDSCH.

[0101] In the above embodiments, the reference point is taken as the center frequency point of the SS block, and when the reference point is the center or the boundary of the NR carrier, the center or the boundary of the downlink synchronization signal bandwidth, or the boundary of the SS block, the offset of the center frequency point of the BWP or the Common CORESET relative to the reference point can be indicated in a similar manner. For example, when the reference point is the right boundary of the SS block, Table 2 shows the offset of the center frequency point of the BWP and the Common CORESET relative to the right boundary frequency point of the SS block and the bandwidth.

[0102] Table 2

[0103]

[0104] In summary, when the position of the BWP or the Common CORESET is any one of the center frequency point and the boundary, and the reference point is any one of the center or the boundary of the NR carrier, the center or the boundary of the downlink synchronization signal bandwidth, and the center or the boundary of the SS block, the frequency domain position of the BWP or the Common CORESET can be indicated in a similar manner to the above embodiments.

[0105] Optional Embodiment 2

[0106] The optional embodiment describes that the frequency domain position of the first resource is indicated by the offset in the frequency domain relative to the reference point, and the frequency domain position of the second resource is indicated by the offset in the frequency domain relative to the first resource.

[0107] As Figure 4 The frequency domain positions of the SS block, the PDSCH and the Common CORESET in the NR carrier are given, where k1, k2 and k3 are the subcarrier numbers corresponding to the center frequency points of the SS block, the PDSCH and the Common CORESET respectively, and the base station can schedule the resources occupied by the PDSCH by using the PDCCH carried by the Common CORESET. The first resource takes the resources occupied by the PDSCH as an example, the second resource takes the Common CORESET as an example, and the reference point takes the center of the SS block as an example. In this embodiment, the base station indicates the terminal the offset of the center frequency point of the PDSCH relative to the center frequency point of the SS block and the bandwidth of the PDSCH, and the offset of the center frequency point of the Common CORESET relative to the center frequency point of the PDSCH and the bandwidth of the Common CORESET, and the specific indication contents include the relative subcarrier number, the left and right offset indication and the bandwidth, as shown in Table 3.

[0108] Wherein, the relative subcarrier number of the center frequency point of the PDSCH relative to the center frequency point of the SS block indicates the number of subcarriers between the frequency domain position of the center frequency point of the PDSCH and the frequency domain position of the center frequency point of the SS block, and when the center frequency point of the PDSCH is higher than the center frequency point of the SS block, it is right offset, and when the center frequency point of the PDSCH is lower than the center frequency point of the SS block, it is left offset.

[0109] Wherein, the relative subcarrier number of the center frequency point of the Common CORESET relative to the center frequency point of the PDSCH indicates the number of subcarriers between the frequency domain position of the center frequency point of the Common CORESET and the frequency domain position of the center frequency point of the PDSCH, and when the center frequency point of the Common CORESET is higher than the center frequency point of the PDSCH, it is right offset, and when the center frequency point of the Common CORESET is lower than the center frequency point of the PDSCH, it is left offset.

[0110] Table 3

[0111]

[0112] For the case that the first resource is Common CORESET and the second resource is PDSCH occupied resource, similar way can be adopted to indicate. Specifically, the base station indicates to the terminal the offset of the center frequency point of the Common CORESET relative to the center frequency point of the SS block and the bandwidth of the Common CORESET, and the offset of the center frequency point of the PDSCH relative to the center frequency point of the Common CORESET and the bandwidth of the PDSCH, the specific indication contents include relative subcarrier number, left and right offset indication and bandwidth, as shown in Table 4. It should be noted that since the center frequency point of the PDSCH is lower than the center frequency point of the Common CORESET, when indicating the offset of the center frequency point of the PDSCH relative to the center frequency point of the Common CORESET, the left and right offset indication is 0, that is, the center frequency point of the PDSCH is left offset relative to the center frequency point of the Common CORESET.

[0113] Table 4

[0114]

[0115] If the bandwidth of the PDSCH is fixed, such as 50 RBs. The base station does not need to indicate the bandwidth of the PDSCH to the terminal. Similarly, if the bandwidth of the Common CORESET is fixed, such as 20 RBs. The base station does not need to indicate the bandwidth of the Common CORESET to the terminal.

[0116] The base station can use the physical broadcast channel or the RRC dedicated signaling to inform the terminal of the frequency domain position of the PDSCH and the Common CORESET, or use the physical broadcast channel to inform the terminal of the frequency domain position of the PDSCH occupied resource, and use the RRC dedicated signaling to inform the terminal of the frequency domain position of the Common CORESET, or use the physical broadcast channel to inform the terminal of the frequency domain position of the Common CORESET, and use the RRC dedicated signaling to inform the terminal of the frequency domain position of the PDSCH dedicated resource. The RRC dedicated signaling can also be sent to the terminal by the adjacent base station.

[0117] Optional embodiment 3

[0118] This optional embodiment describes indicating the frequency domain position of the first resource by using the offset in the frequency domain relative to the reference point, and the second type of node calculates the frequency domain position of the second resource according to the pre-defined rule.

[0119] As Figure 5The frequency domain positions of the SS block, the BWP and the Common CORESET in the NR carrier are given. The first resource takes the BWP as an example, the second resource takes the Common CORESET as an example, and the reference point takes the center of the SS block as an example. In the embodiment, the base station indicates the terminal the offset of the center frequency point of the BWP relative to the center frequency point of the SS block and the bandwidth of the BWP, the bandwidth of the Common CORESET, and the specific indication includes the relative subcarrier number, the left and right offset indication and the bandwidth, as shown in Table 5, wherein "-" indicates that the item does not exist.

[0120] The relative subcarrier number of the center frequency point of the BWP relative to the center frequency point of the SS block indicates the number of subcarriers between the frequency domain position of the center frequency point of the BWP and the frequency domain position of the center frequency point of the SS block, and when the center frequency point of the BWP is higher than the center frequency point of the SS block, it is right offset, and when the center frequency point of the PDSCH is lower than the center frequency point of the SS block, it is left offset.

[0121] The terminal calculates the offset of the center frequency point of the Common CORESET relative to the center frequency point of the BWP according to a predefined rule.

[0122] The predefined rule defines a relationship between one or more factors and the offset of the center frequency point of the Common CORESET relative to the reference point or the center frequency point of the BWP, and the factors include at least one of the following: synchronization signal block index, physical cell identifier, system frame number, frequency band information.

[0123] The predefined rule can be a default frequency domain offset, for example, offset by 4 RBs; or it can be defined according to any one or more of the timing information, the physical cell identifier, the frequency band information, specifically, for example: SS block index, physical cell identifier CellID, system frame number SFN, frequency band range, etc. Wherein the SS block index is the index of the SS block where the terminal completes the downlink synchronization, the SFN is the number of the radio frame where the terminal completes the downlink synchronization. The frequency band range is divided in advance, and each frequency band range corresponds to a unique frequency band range identifier. The principle of determining the predefined rule is to calculate the offset of the center frequency point of the Common CORESET relative to the center frequency point of the BWP according to different SS block index (group), physical cell identifier CellID (group), system frame number SFN (group), frequency band range (group) as much as possible. Different, in order to reduce the mutual interference between adjacent cells when transmitting information using the Common CORESET.

[0124] For example, the predefined rule can be that the center frequency of the SS block index N2 corresponding to the Common CORESET is offset by N2 RBs from the center frequency of the BWP; or,

[0125] the center frequency of the SS block index N2 corresponding to the Common CORESET is offset by K*floor(N2 / M) RBs from the center frequency of the BWP, where floor represents the floor function; or,

[0126] the center frequency of the SS block index N2 corresponding to the Common CORESET is offset by K*mod(N2, M) RBs from the center frequency of the BWP, where mod is the modulo operation; or,

[0127] In a similar manner, the predefined rule can also be determined according to the physical cell identifier CellID, the system frame number SFN, and the frequency band range.

[0128] For example, the predefined rule is to offset K*floor(X / M) or K*mod(X, M) RBs, where X can be CellID, SFN, or a frequency band range identifier.

[0129] The predefined rule can also be a combination of the above-mentioned various manners, for example, offset by K*floor(N2 / M)+L*mod(CellID, M) RBs.

[0130] In the above formula, N2 and X are non-negative integers, K and L are positive integers, and M is an integer greater than 1.

[0131] For example, taking the SS block index 2 where the terminal successfully completes downlink synchronization as an example, according to the predefined rule that the center frequency of the SS block index N2 corresponding to the Common CORESET is offset by N2 RBs from the center frequency of the BWP, the center frequency of the Common CORESET is offset by 2 RBs from the center frequency of the BWP, and then according to the left and right offset indication 1 and the bandwidth of the Common CORESET being 20 RBs, the frequency domain position of the Common CORESET can be determined.

[0132] The above-mentioned offset is in units of RBs, which is only an example, and the actual offset can be any unit capable of measuring frequency, such as Y kHz / MHz, RB group, subcarrier, subcarrier group, channel raster, channel raster group, etc.

[0133] The base station indicates the resource to the terminal in the following ways, which are similar to the above embodiments: 1) the first resource is a Common CORESET, and the second resource is a BWP; 2) the first resource is a Common CORESET, and the second resource is a resource occupied by a downlink service channel PDSCH; 3) the first resource is a resource occupied by a downlink service channel PDSCH, and the second resource is a Common CORESET. The main idea is that the first resource is an offset in the frequency domain relative to a reference point, and the second resource is an offset in the frequency domain relative to the first resource and calculated by the terminal according to a predefined rule.

[0134] Table 5

[0135]

[0136]

[0137] Optional Embodiment 4

[0138] This optional embodiment describes indicating the frequency domain position of a BWP by indicating a BWP index.

[0139] The base station uniformly divides the system bandwidth (i.e., the bandwidth of the physical carrier) into several BWPs, as shown in FIG. 1. Figure 6 The base station divides the physical carrier into four BWPs, corresponding to indexes 0, 1, 2, and 3. Assuming that the terminal already knows the center frequency of the physical carrier and the division method of the BWP within the system bandwidth, the base station can directly indicate the index of the BWP to the terminal using 2 bits of information, for example, directly indicating to the terminal that the index of the BWP is 3. The terminal can then obtain the frequency domain position of BWP 3 according to the center frequency of the physical carrier and the bandwidth and the division method of the BWP, and can know that the resource carrying the control information of the Common CORESET is located within BWP 3. This greatly reduces the overhead of indicating the frequency domain position of BWP 3 compared to indicating the offset and bandwidth of BWP 3 relative to a reference point.

[0140] In addition, the base station can indicate the frequency domain position of the Common CORESET by the methods in the above embodiments, which will not be described here.

[0141] The base station can indicate the BWP index and the frequency domain position of the Common CORESET to the terminal using RRC dedicated signaling, or indicate the BWP index using a physical broadcast channel and indicate the frequency domain position of the Common CORESET using RRC dedicated signaling, or indicate the frequency domain position of the Common CORESET using a physical broadcast channel and indicate the BWP index using RRC dedicated signaling.

[0142] Optional Embodiment 5

[0143] This optional embodiment describes that the frequency domain location of the resource is indicated by indicating the frequency domain location index of the configured SS block, and indicating the offset of the frequency domain location of the Common CORESET relative to the configured SS block.

[0144] The base station configures one or more SS blocks in the system bandwidth, and the frequency domain location of each SS block corresponds to an index, as shown in the following table. Figure 7 As shown, the base station configures two SS blocks in the system bandwidth, and the corresponding indexes are 0 and 1 respectively. Assuming that the terminal has known the frequency domain location of each SS block, and the BWP in which it is located and the bandwidth of the BWP. The base station can directly indicate the frequency domain location index of the configured SS block to the terminal by using 1-bit information. The terminal can obtain the frequency domain location of the configured SS block according to the configuration information of the SS block, and can know that the resource scheduled by the control information carried by the Common CORESET is located in the BWP2. The advantage of this is that compared with indicating the offset of the BWP2 relative to the reference point and the bandwidth, the overhead of indicating the frequency domain location of the BWP2 is greatly reduced.

[0145] Then the base station indicates the center frequency point or the boundary of the Common CORESET relative to the center frequency point or the boundary of the configured SS block, and the bandwidth of the Common CORESET to the terminal, so that the terminal obtains the frequency domain location of the Common CORESET resource. The terminal can successfully obtain the information carried by the Common CORESET according to the BWP (i.e. BWP2) in which the resource scheduled by the Common CORESET is located and the time domain location of the Common CORESET resource obtained by other methods.

[0146] Optional embodiment 6

[0147] This optional embodiment describes a method of jointly indicating the bandwidths of the Common CORESET, the BWP and the PDSCH by using the relationship between the bandwidth of the Common CORESET resource and the bandwidth of the BWP or the PDSCH.

[0148] If the bandwidth of the first resource and the bandwidth of the second resource have a fixed relationship, the bandwidths of the first resource and the second resource can be jointly indicated. Assuming that the bandwidth of the first resource and the bandwidth of the second resource have a plurality of fixed relationships, the bandwidth of one of the resources can be indicated, and it is indicated which relationship the bandwidths of the two resources belong to.

[0149] For example, the first resource is BWP and the second resource is Common CORESET, there are two relationships between the bandwidth of the first resource and the bandwidth of the second resource: 1) the bandwidth of the second resource is the same as the bandwidth of the first resource; 2) the bandwidth of the second resource is half of the bandwidth of the first resource. The base station only needs to indicate the bandwidth of the first resource and the relationship between the bandwidth of the first resource and the bandwidth of the second resource is the first or the second, without indicating the bandwidth of the two resources respectively, thereby saving the resource overhead of indication, especially when the bandwidth is large.

[0150] Optional Embodiment 7

[0151] This optional embodiment takes indicating the frequency domain position of BWP as an example to describe the specific implementation method of indicating the frequency domain position of resource.

[0152] The left and right offset indication of 1 bit and the resource indication value RIV can be used to indicate the offset of the boundary or center of BWP relative to the reference point and the bandwidth of BWP, including the following cases:

[0153] 1) The bandwidth of BWP is fixed, that is, the bandwidth of BWP is known in advance to the base station and the terminal, and the number of bits occupied by RIV is determined by the maximum offset of the left boundary or the right boundary or the center of BWP relative to the reference point, that is, by the number of bits required to represent the maximum offset, and the value of RIV is equal to the offset of the left boundary or the right boundary or the center of BWP relative to the reference point. For example, the maximum offset is 31 RBs, and the offset of the center of BWP relative to the reference point is 12 RBs. Since at least 5 bits of information are required to represent the maximum offset, the number of bits occupied by RIV is 5, RIV = 12, and RIV is represented in binary as RIV = 01100.

[0154] 2) The bandwidth of BWP is not fixed, and the reference point is outside the BWP. The indication method is: when the BWP is located to the right of the reference point, the left boundary and the bandwidth of the BWP are indicated; when the BWP is located to the left of the reference point, the right boundary and the bandwidth of the BWP are indicated. Specifically, the maximum offset of the boundary of BWP relative to the reference point is the physical carrier bandwidth or a fixed value, the base station determines the RIV value according to the offset of the boundary of BWP relative to the reference point and the bandwidth of BWP, sends the RIV value to the terminal, and then the terminal calculates the offset of the boundary of BWP relative to the reference point and the bandwidth according to the received RIV value, and obtains the boundary position of BWP according to the obtained left and right offset indication. Assume that the maximum offset is the physical carrier bandwidth, represented by N RBs. Let L represent the bandwidth of BWP as L RBs, and S represent the offset of the boundary of BWP relative to the reference point as S RBs. The left boundary of BWP is located to the right of the reference point, as shown in Figure 8 ; and the right boundary of BWP is located to the left of the reference point, as shown inFigure 9 The number of bits occupied by RIV is The value of RIV is:

[0155] If RIV = N(L-1) + S Formula 1

[0156] Otherwise RIV = N(N-L+1) + N-1-S Formula 2

[0157] After the terminal receives RIV, it first calculates the value of

[0158] For Formula 1,

[0159] For Formula 2,

[0160] where % represents the modulo operation, and since L+S≤N (otherwise the BWP will exceed the bandwidth range of the physical carrier), for Formula 1, and for Formula 2, Therefore, the terminal can know whether Formula 1 or Formula 2 is used for the calculation of RIV according to the size relationship between the value of and N.

[0161] If Formula 1 is used, S = RIV % N; and if Formula 2 is used, S = N-1-RIV % N. After the terminal obtains the values of S and L, it obtains the offset of the boundary of the BWP relative to the reference point and the bandwidth, and then, together with the left and right offset indications, it determines whether it is the left boundary or the right boundary, thereby obtaining the frequency domain position of the BWP, i.e., the boundary position and the bandwidth of the BWP.

[0162] 3) The bandwidth of the BWP is not fixed, and the center frequency position and the bandwidth of the BWP are indicated, including: the offset of the center frequency of the BWP relative to the reference point and the left and right offset indications, and the bandwidth of the BWP. The specific method is as follows: the protocol pre-determines the maximum offset N of the center frequency of the BWP relative to the reference point, the base station determines the value of RIV according to the offset of the center frequency of the BWP relative to the reference point and the bandwidth of the BWP, and then the terminal inversely calculates the offset of the center frequency of the BWP relative to the reference point and the bandwidth according to the received value of RIV, and then obtains the center frequency position and the bandwidth of the BWP according to the obtained left and right offset indications. Assuming that the maximum offset is the bandwidth of the physical carrier, N represents that the bandwidth of the physical carrier is N RBs, 2L represents that the bandwidth of the BWP is 2L RBs (that is, the bandwidth is an even number of RBs), that is, half of the bandwidth of the BWP is L RBs, S represents that the offset of the center frequency of the BWP relative to the reference point is S RBs, and the center frequency of the BWP is located to the right of the reference point, as shown inFigure 10 As shown in FIG. 3, the center frequency point of the BWP is located on the left side of the reference point, as shown in FIG. 4. Figure 11

[0163] The number of bits occupied by RIV is The value of RIV is:

[0164] RIV = N(L-1) + S Formula 5

[0165] After the terminal receives RIV, the values of L and S are calculated, that is, S = RIV % N; therefore, the terminal can obtain the bandwidth of the BWP according to RIV The offset is S = RIV % N, and the terminal obtains the values of S and 2L, that is, the offset of the center frequency point of the BWP relative to the reference point and the bandwidth, and then the left and right offset indications are obtained, so as to obtain the frequency domain position of the BWP.

[0166] In implementation, a corresponding method is selected according to actual conditions.

[0167] In all the above embodiments, the base station also needs to indicate the time domain position of the Common CORESET to the terminal, so that the terminal can quickly receive the information carried by the Common CORESET. The time domain position of the Common CORESET can be indicated by other methods, for example, if the Common CORESET is periodically transmitted, the transmission period, the wireless frame in which the starting position is located, and the starting position and the number of continuous OFDM symbols of the Common CORESET in each transmission period can be indicated. If the Common CORESET is not periodically transmitted, the time domain offset (for example, delayed by n OFDM symbols) of the Common CORESET relative to a certain reference position and the number of continuous OFDM symbols can be indicated.

[0168] ​The embodiment provides a method for indicating resource positions, including: a first type of node indicating frequency domain positions of resources to a second type of node, including at least one of the following: indicating frequency domain positions of first resources, and indicating frequency domain positions of second resources. Wherein, the first resources refer to resources occupied by a bandwidth part BWP or a physical downlink shared channel PDSCH, and the second resources refer to resources of common CORESET(s). Alternatively, the first resources refer to resources of common CORESET(s), and the second resources refer to resources occupied by a bandwidth part BWP or a physical downlink shared channel PDSCH, so that the base station can indicate resource positions of the BWP, the PDSCH and the common CORESET(s) to the terminal, and the problem that the base station cannot indicate resource positions of the BWP, the PDSCH and the common CORESET(s) in the related art is solved. In addition, the frequency domain positions of the second resources are calculated by the terminal according to a predefined rule, the indication overhead is reduced, and the mutual interference between adjacent cells when using the indicated resource transmission information can be reduced to a certain extent. In addition, the method for jointly indicating resource bandwidths can also reduce the resource indication overhead.

[0169] Optionally, the technical features in each of the above embodiments can be combined for use in one embodiment without conflict. Each embodiment is only the optimal implementation of the present application.

[0170] From the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be realized by means of software and the necessary general hardware platform, and of course, it can also be realized by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk), and includes a plurality of instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device) to execute the methods described in the embodiments of the present application.

[0171] Embodiment 2

[0172] In the embodiment, a resource position indication device is also provided, which is used to implement the above embodiments and preferred embodiments, and will not be described again. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware is also possible and is contemplated.

[0173] Figure 12 is a structural block diagram of a resource position indication device according to an embodiment of the present application, which is applied to a base station, such asFigure 12 The apparatus shown includes:

[0174] 1) a sending module 122 configured to send resource location information to a second type of node, the resource location information being used at least to indicate a frequency domain location of a resource;

[0175] The frequency domain location includes at least one of a frequency domain location of a first resource and a frequency domain location of a second resource; the first resource or the second resource includes at least one of a bandwidth part (BWP), a physical downlink shared channel (PDSCH) occupied resource, and a common control resource set.

[0176] The apparatus shown solves the problem that a base station cannot indicate the resource locations of a BWP, a PDSCH, and a common CORESET(s) in the related art, and achieves the technical effect that the resource locations can be effectively indicated. Figure 12

[0177] Optionally, the frequency domain location of the first resource is a frequency domain location of a configured synchronization signal block (SS block), and the frequency domain location of the second resource is a frequency domain location of a common control resource set.

[0178] Optionally, the frequency domain location of the first resource is a frequency domain location of a configured synchronization signal block (SS block), and the frequency domain location of the second resource is a frequency domain location of a common control resource set.

[0179] Optionally, the common control resource set is contained in a BWP or a PDSCH occupied resource, or the common control resource set partially overlaps with the BWP or the PDSCH occupied resource, or the common control resource set does not partially overlap with the BWP or the PDSCH occupied resource, or there is no fixed relationship between the common control resource set and the BWP or the PDSCH occupied resource.

[0180] Optionally, control information carried by the common control resource set is scheduled in a BWP or a PDSCH occupied resource.

[0181] In an optional embodiment, the first type of node indicates the frequency domain location of the first resource to the second type of node in the following manner:

[0182] indicating an offset of the first resource in the frequency domain relative to a reference point; or indicating an offset of the first resource in the frequency domain relative to a reference point and a bandwidth of the first resource.

[0183] It should be noted that the reference point includes a center or a boundary of any one of the following: a physical carrier, a downlink synchronization signal bandwidth, and a synchronization signal block (SS block). ​

[0184] In an optional implementation, the first type of node indicating the frequency domain location of the first resource to the second type of node comprises the following manners:

[0185] indicating the frequency domain offset of the second resource relative to the reference point or the first resource; or, indicating the frequency domain offset of the second resource relative to the reference point or the first resource, and the bandwidth of the second resource or the relationship between the bandwidth of the second resource and the bandwidth of the first resource.

[0186] It should be noted that the reference point includes the center or boundary of any one of the following: physical carrier, downlink synchronization signal bandwidth, downlink synchronization signal block (SS block).

[0187] Optionally, indicating the frequency domain location of the BWP comprises indicating the index of the BWP.

[0188] In an optional implementation, the manner of determining the frequency domain location of the first resource as the frequency domain location of the configured synchronization signal block (SS block) comprises: the first type of node configuring one or more SS blocks in the system bandwidth, wherein the frequency domain location of each SS block corresponds to an index; and configuring the frequency domain location of the first resource as one of the frequency domain locations of the one or more SS blocks.

[0189] Optionally, indicating the frequency domain location of the configured SS block comprises indicating the index of the frequency domain location of the configured SS block.

[0190] In an optional implementation, the first type of node indicating the frequency domain location of the resource to the second type of node comprises: the first type of node carrying the resource location information by using a physical broadcast channel; or, the first type of node carrying the resource location information by using radio resource control (RRC) dedicated signaling; or, the first type of node carrying the frequency domain location information of the first resource by using a physical broadcast channel, carrying the frequency domain location information of the second resource by using RRC dedicated signaling, or part of the frequency domain location information of the first resource and / or the frequency domain location information of the second resource is carried by using a physical broadcast channel and the other part is carried by using RRC signaling.

[0191] Optionally, the RRC dedicated signaling is sent by a node adjacent to the first type of node to the second type of node.

[0192] Optionally, the frequency domain offset comprises at least one of the following: offset amount, left-right offset indication.

[0193] Optionally, the above-mentioned offset in the frequency domain is represented by one or more of the following: relative channel number, relative channel group number, relative physical resource block PRB number, relative PRB group number, relative subcarrier number.

[0194] In an optional embodiment, the frequency domain position of the resource is the center position of the resource on the frequency domain; or, the frequency domain position of the resource is the boundary position of the resource on the frequency domain; or, the frequency domain position of the resource is the center position of the resource on the frequency domain and the bandwidth of the frequency domain resource; or, the frequency domain position of the resource is the boundary position of the resource on the frequency domain and the bandwidth of the frequency domain resource; or, the frequency domain position of the resource is the bandwidth of the frequency domain resource.

[0195] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0196] Example 3

[0197] In this embodiment, a method for receiving a resource location is also provided. Figure 2 The scheme shown corresponds to a flow chart of a method for receiving a resource location according to an embodiment of the present invention, such as Figure 13 As shown, the process includes the following steps:

[0198] In step S1302, the second type of node receives resource location information sent by the first type of node, which is used to indicate the frequency domain location of the resource; wherein the frequency domain location includes at least one of the following: the frequency domain location of the first resource, the frequency domain location of the second resource; the first resource or the second resource includes at least one of the following: a bandwidth part BWP, resources occupied by a physical downlink shared channel PDSCH, and a common control resource set.

[0199] Optionally, the first type of node executing the above steps may be a base station, specifically, a transmit-receive point (TRP), a relay node, a macro base station, a micro base station, a pico base station, a home base station, a remote radio frequency, an access point (AP), etc. Examples of the second type of node include a terminal and a relay node. In the following embodiments, the first type of node takes a base station as an example, and the second type of node takes a terminal as an example, but is not limited thereto.

[0200] Through the above step S1302, the problem in the related art that the terminal cannot obtain the resource locations of BWP, PDSCH and commonCORESET(s) is solved, and the technical effect of being able to effectively obtain the resource locations is achieved.

[0201] Optionally, the frequency domain location of the first resource is a frequency domain location of a configured synchronization signal block (SS block), and the frequency domain location of the second resource is a frequency domain location of a common control resource set (CORESET).

[0202] In an optional embodiment, the frequency domain location of the first resource indicated by the first type of node can also be received by the second type of node, and the frequency domain location of the second resource is determined according to a predefined rule.

[0203] It should be noted that the predefined rule is a relationship between one or more factors and a frequency domain offset, wherein the factors include at least one of the following: a synchronization signal block index, a physical cell identifier, a system frame number, and band information.

[0204] Optionally, the second type of node receives the resource location information to obtain the frequency domain location of at least one of the first resource and the second resource.

[0205] Optionally, the second type of node receives the resource location information to obtain the frequency domain location of the resource of the common CORESET and the frequency domain location of the resource scheduled by the control information of the common CORESET, and then obtains the control information carried by the common CORESET in combination with the time domain location of the resource obtained in the optional embodiment.

[0206] From the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software and a general hardware platform, and of course, it can also be implemented by hardware, but in many cases, the former is a better embodiment. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk), and includes a plurality of instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device) to execute the method described in the embodiments of the present application.

[0207] Embodiment 4

[0208] In this embodiment, a resource location receiving device is also provided, which is used to implement the above embodiments and preferred embodiments, and has been described above. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware or a combination of software and hardware is also possible and is contemplated.

[0209] Figure 14is a structural block diagram of a device for receiving a resource location according to an embodiment of the present invention, which is applied to a terminal, such as Figure 14 As shown, the device includes:

[0210] 1) A receiving module 142, configured to receive resource location information indicating a frequency domain location of a resource sent by a first type of node;

[0211] Among them, the frequency domain position includes at least one of the following: the frequency domain position of the first resource, the frequency domain position of the second resource; the first resource or the second resource includes at least one of the following: the bandwidth part BWP, the resources occupied by the physical downlink shared channel PDSCH, and the public control resource set.

[0212] pass Figure 14 The device shown solves the problem in the related art that the terminal cannot obtain the resource locations of BWP, PDSCH and commonCORESET(s), and achieves the technical effect of effectively obtaining the resource locations.

[0213] Optionally, the frequency domain position of the first resource is the frequency domain position of the configured synchronization signal block SS block; the frequency domain position of the second resource is the frequency domain position of the public control resource set.

[0214] In an optional implementation manner, the frequency domain position of the first resource indicated by the first type node may also be received by the second type node, and the frequency domain position of the second resource may be determined according to a predefined rule.

[0215] It should be noted that the above-mentioned predefined rules are the relationship between one or more predefined factors and the frequency domain offset, wherein the factor includes at least one of the following: synchronization signal block index, physical cell identifier, system frame number, and frequency band information.

[0216] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0217] Example 5

[0218] An embodiment of the present invention further provides a storage medium, which includes a stored program, wherein when the program is run, any of the above methods is executed.

[0219] Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

[0220] S1, a first type of node sends resource location information to a second type of node, the resource location information being used at least for indicating a frequency domain location of a resource; wherein the frequency domain location comprises at least one of: a frequency domain location of a first resource, a frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a resource occupied by a physical downlink shared channel (PDSCH), a common control resource set.

[0221] Optionally, the storage medium is further configured to store program code for executing the following steps:

[0222] S2, the second type of node receives the resource location information sent by the first type of node and used for indicating the frequency domain location of the resource; wherein the frequency domain location comprises at least one of: a frequency domain location of a first resource, a frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a resource occupied by a physical downlink shared channel (PDSCH), a common control resource set.

[0223] Optionally, in the embodiment, the storage medium can include but is not limited to: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0224] Embodiments of the application also provide a processor for running a program, wherein the program performs the steps in any of the above methods when running.

[0225] Optionally, in the embodiment, the program is used to perform the following steps:

[0226] S1, a first type of node sends resource location information to a second type of node, the resource location information being used at least for indicating a frequency domain location of a resource; wherein the frequency domain location comprises at least one of: a frequency domain location of a first resource, a frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a resource occupied by a physical downlink shared channel (PDSCH), a common control resource set.

[0227] Optionally, in the embodiment, the program is used to perform the following steps:

[0228] S2, the second type of node receives the resource location information sent by the first type of node and used for indicating the frequency domain location of the resource; wherein the frequency domain location comprises at least one of: a frequency domain location of a first resource, a frequency domain location of a second resource; the first resource or the second resource comprises at least one of: a bandwidth part (BWP), a resource occupied by a physical downlink shared channel (PDSCH), a common control resource set.

[0229] Optionally, the specific examples in the embodiments can refer to the examples described in the above embodiments and optional implementation manners, and the embodiments will not be described here.

[0230] Embodiment 6

[0231] The embodiments of the application also provide a base station, as shown in the following table. Figure 15 The base station comprises a processor 150 and a memory 152 storing processor-executable instructions, when the instructions are executed by the processor, the following operations are performed: sending resource location information to a second type of node, the resource location information at least indicating a frequency domain location of a resource; wherein the frequency domain location comprises at least one of the following: a frequency domain location of a first resource, a frequency domain location of a second resource; the first resource or the second resource comprises at least one of the following: a bandwidth part BWP, a resource occupied by a physical downlink shared channel PDSCH, a common control resource set.

[0232] The embodiments of the application also provide a terminal, as shown in the following table. Figure 16 The terminal comprises a processor 160 and a memory 162 storing processor-executable instructions, when the instructions are executed by the processor, the following operations are performed: receiving resource location information sent by a first type of node and used for indicating a frequency domain location of a resource; wherein the frequency domain location comprises at least one of the following: a frequency domain location of a first resource, a frequency domain location of a second resource; the first resource or the second resource comprises at least one of the following: a bandwidth part BWP, a resource occupied by a physical downlink shared channel PDSCH, a common control resource set.

[0233] Obviously, those skilled in the art should understand that the modules or steps of the application described above can be realized by general computing devices, which can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be realized by program codes executable by computing devices, so that they can be stored in storage devices and executed by computing devices, and in some cases, the steps shown or described can be executed in different order, or they can be manufactured into individual integrated circuit modules, or multiple modules or steps can be manufactured into a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.

[0234] The above only describes the preferred embodiments of the application and is not used to limit the application. For those skilled in the art, the application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. within the principles of the application shall be included in the protection scope of the application.

Claims

1. A method for indicating a resource location, characterized in that: include: The first type of node sends resource location information to the second type of node on a physical broadcast channel PBCH, where the resource location information is used to indicate a frequency domain location of a common control resource set, wherein the frequency domain location includes an offset in the frequency domain. The frequency domain position of the common control resource set is determined based on the resource position information and according to the offset in the frequency domain, wherein the offset in the frequency domain is the offset of the frequency domain position of the common control resource set relative to the frequency domain position of the synchronization signal block (SSBlock) boundary, and the offset in the frequency domain is represented by the number of physical resource blocks (PRBs) and one or more subcarriers. The frequency domain position of the synchronization signal block is indicated by the boundary position of the synchronization signal block in the frequency domain and the bandwidth of the synchronization signal block.

2. The method according to claim 1, characterized in that The frequency domain position of the synchronization signal block is configured as one of the frequency domain positions of one or more synchronization signal SS blocks, and each frequency domain position of the synchronization signal block corresponds to an index.

3. The method according to claim 1, characterized in that The offset in the frequency domain includes an offset amount, or a left or right offset indication.

4. A method for receiving a resource location, characterized in that: include: The second type of node receives, on a physical broadcast channel PBCH, resource location information sent by the first type of node and used to indicate a frequency domain location of a common control resource set, wherein the frequency domain location includes an offset in the frequency domain; Based on the resource location information, determining the frequency domain location of the common control resource set according to the frequency domain offset, where the frequency domain offset is an offset of the frequency domain location of the common control resource set relative to the frequency domain location of a synchronization signal block (SS Block) boundary, and the frequency domain offset is represented by a physical resource block (PRB) number and one or more subcarriers. The frequency domain position of the synchronization signal block is indicated by the boundary position of the synchronization signal block in the frequency domain and the bandwidth of the synchronization signal block.

5. The method according to claim 4, characterized in that The offset in the frequency domain includes an offset amount, or a left or right offset indication.

6. The method according to claim 4, characterized in that The frequency domain position of the synchronization signal block is configured as one of the frequency domain positions of one or more synchronization signal SS blocks, and each frequency domain position of the synchronization signal block corresponds to an index.

7. A resource location indication device, applied to a first type of node, characterized in that: include: a sending module, configured to send resource location information to the second type of node on a physical broadcast channel PBCH, wherein the resource location information is used to indicate a frequency domain location of a common control resource set, wherein the frequency domain location includes an offset in the frequency domain, The frequency domain position of the common control resource set is determined based on the resource position information and according to the offset in the frequency domain, wherein the offset in the frequency domain is the offset of the frequency domain position of the common control resource set relative to the frequency domain position of the synchronization signal block (SSBlock) boundary, and the offset in the frequency domain is represented by the number of physical resource blocks (PRBs) and one or more subcarriers. The frequency domain position of the synchronization signal block is indicated by the boundary position of the synchronization signal block in the frequency domain and the bandwidth of the synchronization signal block.

8. The device according to claim 7, characterized in that The frequency domain position of the synchronization signal block is configured as one of the frequency domain positions of one or more synchronization signal SS blocks, and each frequency domain position of the synchronization signal block corresponds to an index.

9. The device according to claim 7, characterized in that The offset in the frequency domain includes an offset amount, or a left or right offset indication.

10. A device for receiving a resource location, applied to a second type of node, characterized in that: include: A receiving module is configured to receive resource location information indicating a frequency domain location of a common control resource set sent by a first type of node on a physical broadcast channel (PBCH), wherein the frequency domain location includes an offset in the frequency domain. Based on the resource location information, determining the frequency domain location of the common control resource set according to the frequency domain offset, where the frequency domain offset is an offset of the frequency domain location of the common control resource set relative to the frequency domain location of a synchronization signal block (SS Block) boundary, and the frequency domain offset is represented by a physical resource block (PRB) number and one or more subcarriers. The frequency domain position of the synchronization signal block is indicated by the boundary position of the synchronization signal block in the frequency domain and the bandwidth of the synchronization signal block.

11. The device according to claim 10, characterized in that The offset in the frequency domain includes an offset amount, or a left or right offset indication.

12. The device according to claim 10, characterized in that The frequency domain position of the synchronization signal block is configured as one of the frequency domain positions of one or more synchronization signal SS blocks, and each frequency domain position of the synchronization signal block corresponds to an index.

13. A storage medium, characterized in that: The storage medium includes a stored program, wherein the method according to any one of claims 1 to 6 is executed when the program is executed.

14. A processor, characterized in that: The processor is configured to run a program, wherein the program executes the method according to any one of claims 1 to 6 when running.

15. A base station, characterized in that: include: A processor and a memory storing instructions executable by the processor, wherein when the instructions are executed by the processor, the processor performs the following operations: sending resource location information to the second type of node on a physical broadcast channel (PBCH), where the resource location information is used to indicate a frequency domain location of a common control resource set, wherein the frequency domain location includes an offset in the frequency domain; The frequency domain position of the common control resource set is determined based on the resource position information and according to the offset in the frequency domain, wherein the offset in the frequency domain is the offset of the frequency domain position of the common control resource set relative to the frequency domain position of the synchronization signal block (SSBlock) boundary, and the offset in the frequency domain is represented by the number of physical resource blocks (PRBs) and one or more subcarriers. The frequency domain position of the synchronization signal block is indicated by the boundary position of the synchronization signal block in the frequency domain and the bandwidth of the synchronization signal block.

16. The base station according to claim 15, characterized in that The frequency domain position of the synchronization signal block is configured as one of the frequency domain positions of one or more synchronization signal SS blocks, and each frequency domain position of the synchronization signal block corresponds to an index.

17. The base station according to claim 15, characterized in that The offset in the frequency domain includes an offset amount, or a left or right offset indication.

18. A terminal, characterized in that: include: A processor and a memory storing instructions executable by the processor, wherein when the instructions are executed by the processor, the processor performs the following operations: receiving resource location information for indicating a frequency domain location of a common control resource set sent by a first type of node on a physical broadcast channel (PBCH), wherein the frequency domain location includes an offset in the frequency domain; Based on the resource location information, determining the frequency domain location of the common control resource set according to the frequency domain offset, where the frequency domain offset is an offset of the frequency domain location of the common control resource set relative to the frequency domain location of a synchronization signal block (SS Block) boundary, and the frequency domain offset is represented by a physical resource block (PRB) number and one or more subcarriers. The frequency domain position of the synchronization signal block is indicated by the boundary position of the synchronization signal block in the frequency domain and the bandwidth of the synchronization signal block.

19. The terminal according to claim 18, characterized in that The offset in the frequency domain includes an offset amount, or a left or right offset indication.

20. The terminal according to claim 18, wherein The frequency domain position of the synchronization signal block is configured as one of the frequency domain positions of one or more synchronization signal SS blocks, and each frequency domain position of the synchronization signal block corresponds to an index.

Images