CN114640430A - Method performed by user equipment and user equipment - Google Patents

Abstract

The invention provides a method executed by User Equipment (UE), which comprises the following steps: receiving bandwidth fragment BWP configuration information configured by a network for a UE type of the UE, wherein the BWP corresponding to the BWP configuration information is different from a cell initial downlink BWP; and the UE determines at least one of the position of a Physical Downlink Control Channel (PDCCH) in a common search space, the width and the value of a frequency domain indication domain in Downlink Control Information (DCI) for data scheduling and the position of a scheduled Physical Downlink Shared Channel (PDSCH) resource according to the received BWP configuration information.

Description

Method performed by user equipment and user equipment

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a method performed by a user equipment and a corresponding user equipment.

Background

In the existing 5G/NR network, three typical service models are defined, enhanced mobile broadband service (eMBB), mass machine-type communication (mtc), and Ultra-Reliable and Low Latency communication (URLLC). In addition to these, there are Time Sensitive Communication (TSC) and the like.

An important goal of 5G is to realize the interconnect industry. The 5G interconnection can be used as a catalyst for next wave industrial transformation and digitalization, so that the flexibility can be enhanced, the productivity and efficiency can be improved, the maintenance cost can be reduced, the operation safety can be improved, and the like. Devices in such environments include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, and the like. These sensors and actuators need to be connected to the 5G radio access network and the core network. TR 22.804 et al describe large-scale Industrial Wireless Sensor Network (IWSN) use cases and requirements that include relatively low-end services requiring smaller size, and/or years of battery life in wireless conditions, in addition to having very high-demand URLLC traffic. The requirements for these services are higher than lpwa (low Power Wide Area network), but lower than URLCC and eMBB.

Similar to the internet industry, 5G interconnection can become a catalyst for the innovation of the next-wave smart city. As an example, TSR22.804 describes smart city use cases and requirements. The intelligent city vertical coverage data collection and processing can more effectively monitor and control city resources and provide service for city residents. Particularly, the deployment of the monitoring camera is an important component of an intelligent city and is also an important component of factories and industries.

Finally, examples of wearable devices include smart watches/rings, eHealth-related devices, medical monitoring devices, and the like. One feature of this scenario is that a compact device size is required.

As a baseline, the requirements of these three use cases are:

the general requirements are as follows:

the complexity of the equipment: the main motivation for new device types is to reduce device cost and complexity compared to eMBB and URLLC devices. Especially in the case of industrial sensors.

Equipment size: most use cases require compact device design.

Deployment scenario: the system should support all FR1/FR2 bands for FDD and TDD.

The concrete requirements of the use case are as follows:

industrial wireless sensors: the reference use cases and requirements are described in TR 22.832 and TS 22.104: communication service availability is 99.99% and end-to-end delay is less than 100 milliseconds. The reference bit rate is less than 2Mbps (possibly asymmetric, such as heavy uplink), which is smooth for all use cases and devices. The battery should last at least several years. For safety-relevant sensors, the delay requirement is low, 5-10ms (TR 22.804)

Video surveillance: in TSR22.804, the reference economical video bit rate is 2-4Mbps, the delay is less than 500ms, and the reliability is 99% -99.9%. High-end video, such as agriculture, requires 7.5-25 Mbps. The traffic pattern may be UL transmission dominated.

Wearable devices: the reference bit rate for the smart wearable application may be 5-50Mbps, in DL, a minimum of 2-5 Mbps. The peak bit rate of the device is higher, such as up to 150Mbps downlink, up to 50Mbps uplink. The battery of the device should last for 1-2 weeks.

The new demand scenario puts more demands on network transmission, and particularly, when terminal equipment needs to obtain service-matched receiving capability under the constraint conditions of smaller volume, lower processing complexity, fewer antenna numbers, smaller bandwidth and the like, improvement on the existing resource allocation method of an air interface and the channel transmission method is needed.

Disclosure of Invention

In order to solve at least a part of the above problems, the present invention provides a method executed by a user equipment and a user equipment, which can enable a terminal with a smaller bandwidth capability to access a network and perform related service transmission, thereby improving the service capability of the network, expanding the compatibility of the network, and greatly reducing the cost of communication network deployment.

According to the invention, a method performed by a user equipment, UE, is proposed, comprising: receiving bandwidth segment BWP configuration information configured by a network for a UE type of the UE, wherein a BWP corresponding to the BWP configuration information is different from a cell initial downlink BWP; and determining at least one of a Physical Downlink Control Channel (PDCCH) position in a common search space, a width and a numerical value of a frequency domain indication domain in Downlink Control Information (DCI) for data scheduling, and a position of a scheduled Physical Downlink Shared Channel (PDSCH) resource according to the received BWP configuration information.

Preferably, if the BWP corresponding to the BWP configuration information includes all resource blocks RB of CORESET0, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth of CORESET0 and a subcarrier spacing parameter; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI and a position of scheduled PDSCH resources using a bandwidth of the BWP and a subcarrier spacing parameter.

Preferably, if the BWP corresponding to the BWP configuration information includes all resource blocks RB of CORESET0, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on a cell initial BWP; if the BWP corresponding to the BWP configuration information does not include all RBs of the CORESET0, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on the BWP and does not receive a PDCCH of a random access search space on a cell initial BWP.

Preferably, if the BWP corresponding to the BWP configuration information includes all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth of CORESET0 and the subcarrier spacing parameter; if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth of the BWP and the subcarrier spacing parameters.

Preferably, if the BWP corresponding to the BWP configuration information includes all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on a cell initial BWP; if the BWP corresponding to the BWP configuration information does not include all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on the BWP and does not receive a PDCCH of a random access search space on a cell initial BWP.

Preferably, if the BWP corresponding to the BWP configuration information includes all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth of CORESET0 and the subcarrier spacing parameter; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources of a frequency domain indication field in the DCI using a bandwidth, subcarrier spacing parameter, and a starting position of BWP of the CORESET 0; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth of the BWP and the subcarrier spacing parameter.

Preferably, if the BWP corresponding to the BWP configuration information includes all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on a cell initial BWP; if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE receiving a PDCCH for a random access procedure of the UE using a CORESET of the same size as CORESET0 on the BWP, and not receiving a PDCCH for a random access procedure on a random access search space on a cell initial BWP; if the BWP corresponding to the BWP configuration information does not include all RBs of the CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the UE receives a PDCCH for a random access procedure of the UE using the CORESET on the BWP and does not receive a PDCCH of a random access search space on a cell initial BWP.

Preferably, if the UE receives BWP configured by the network for the UE, the UE determines at least one of a width and a value of a frequency domain indication field in the DCI and a location of the scheduled PDSCH resource using a bandwidth of the BWP; if the UE does not receive the BWP configured by the network for the UE, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI and a position of the scheduled PDSCH resource using a cell-dependent initial BWP or CORESET 0.

Preferably, if the UE receives a BWP configured by a network for the UE, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on the BWP, and does not receive a PDCCH of the random access search space on a cell initial BWP; and if the UE does not receive the BWP configured by the network for the UE, the UE receives a PDCCH for a random access procedure of the UE by using a random access search space on the initial BWP of the cell.

Furthermore, according to the present invention, there is provided a user equipment comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the method described above.

According to the invention, the terminal with smaller bandwidth capability can access the network and carry out related service transmission, thereby improving the service capability of the network, expanding the compatibility of the network and greatly reducing the deployment cost of the communication network.

Drawings

The above and other features of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:

fig. 1 is a flowchart illustrating a method performed by a user equipment according to embodiment 1 of the present invention.

Fig. 2 is a block diagram schematically illustrating a user equipment to which the present invention relates.

Detailed Description

The invention is described in detail below with reference to the figures and the detailed description. It should be noted that the present invention should not be limited to the specific embodiments described below, which are provided as examples only to convey the scope of the subject matter to those skilled in the art. In addition, for the sake of brevity, detailed descriptions of well-known technologies not directly related to the present invention are omitted to prevent confusion of understanding of the present invention.

In general, all terms used herein are to be interpreted according to their ordinary meaning in the relevant art, unless a different meaning is clearly given and/or implied in the context in which the term is used. All references to a/an/the element, device, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless one step must be explicitly described as being after or before another step and/or implicitly one step must be after or before another step. Any feature of any embodiment disclosed herein may be applied to any other embodiment, where appropriate. Likewise, any advantage of any embodiment may apply to any other embodiment, and vice versa.

Embodiments according to the present invention are described in detail below with a 5G/NR mobile communication system and its subsequent evolution as an example application environment. However, it should be noted that the present invention is not limited to the following embodiments, but may be applied to more other wireless communication systems, such as a communication system after 5G and a 4G mobile communication system before 5G, an 802.11 wireless network, and the like.

Some terms to which the present invention relates will be described below, and the terms to which the present invention relates are defined herein, unless otherwise specified. The terms given in the present invention may adopt different naming manners in LTE, LTE-Advanced Pro, NR and other communication systems afterwards or otherwise, but the present invention adopts unified terms, and when applied to a specific system, the terms adopted in the corresponding system can be replaced.

3 GPP: 3rd Generation partnershift Project, third Generation Partnership Project

LTE: long Term Evolution, Long Term Evolution

NR: new Radio, New Wireless, New air interface

UE: user Equipment, User Equipment

eNB: evolved NodeB, evolved node B

And g NB: NR base station

kssb: SSB subcarrier offset, SSB subcarrier offset

TTI: transmission Time Interval, Transmission Time Interval

OFDM: orthogonal Frequency Division Multiplexing

CP-OFDM: cyclic Prefix Orthogonal Frequency Division Multiplexing with Cyclic Prefix

C-RNTI: cell Radio Network Temporary Identifier

CSI: channel State Information, Channel State Information

HARQ: hybrid Automatic Repeat Request (HARQ)

CSI-RS: channel State Information Reference Signal (CSI-RS)

CRS: cell Reference Signal, Cell specific Reference Signal

PBCH: physical broadcast channel, Physical broadcast channel

PUCCH: physical Uplink Control Channel, Physical Uplink Control Channel

PUSCH: physical Uplink Shared Channel, Physical Uplink Shared Channel

PRACH: physical random-access channel, Physical random-access channel

PDSCH: physical downlink shared channel (pdcch)

PDCCH: physical downlink control channel, Physical downlink control channel

UL-SCH: uplink Shared Channel, Uplink Shared Channel

DL-SCH: downlink Shared Channel, uplink Shared Channel

RACH: random-access channel, random-access channel

DCI: downlink Control Information, Downlink Control Information

CG: configured Grant, configuring scheduling Grant

MCS: modulation and Coding Scheme, Modulation and Coding Scheme

RB: resource Block, Resource Block

RE: resource Element, Resource Element

CRB: common Resource Block, Common Resource Block

And (3) CP: cyclic Prefix, Cyclic Prefix

PRB: physical Resource Block, Physical Resource Block

VRB: virtual resource block, Virtual resource block

FDM: frequency Division Multiplexing, Frequency Division Multiplexing

TDD: time Division Duplexing

FDD: frequency Division Duplexing

RRC: radio Resource Control, Radio Resource Control

RSRP: reference Signal Receiving Power, Reference Signal Receiving Power

SRS: sounding Reference Signal

DMRS: demodulation Reference Signal

CSI-RS：Channel state information reference signal

CRC: cyclic Redundancy Check (CRC)

SFI: slot Format Indication

SIB: system information block, system information block

SIB 1: system Information Block Type1, System Information Block Type1

PSS: primary Synchronization Signal, Primary Synchronization Signal

SSS: secondary Synchronization Signal, Secondary Synchronization Signal

And (3) SSB: synchronization Signal Block, synchronous System information Block

CRB: common resource block, Common resource block

BWP: bandwidth Part, BandWidth fragment/portion

SFN: system Frame Number, System (radio) Frame Number

PCI: physical Cell ID, Physical Cell identity

IE: information Element, Information Element

EN-DC: EUTRA-NR Dual Connection, LTE-NR Dual connectivity

MCG (calcium carbonate): master Cell Group, Master Cell Group

SCG: secondary Cell Group, Secondary Cell Group

A PCell: primary Cell, Primary Cell

SCell: secondary Cell, Secondary Cell

SPS: semi-persistent Scheduling, Semi-persistent Scheduling

TA: timing Advance, uplink Timing Advance

PT-RS: Phase-Tracking Reference Signals

TB: transport Block

TBS: transport Block Size, Transport Block Size

CB: code Block, Code Block/Code Block

QPSK: quadrature Phase Shift Keying (QPSK)

16/64/256 QAM: 16/64/256Quadrature Amplitude Modulation

AGC: auto Gain Control, automatic Gain Control

Tdra (field): time Domain Resource Assignment, Time Domain Resource allocation indication (Domain)

Fdra (field): frequency Domain Resource Assignment, Frequency Domain Resource allocation indication (Domain)

ARFCN: absolute Radio Frequency Channel Number, Absolute Radio Frequency Channel Number

RedCap Device: reduced Capability Device

CORESET: control resource set, Control resource set

CORESET 0: control resource set0, Control resource set number 0

CCE: control channel element, Control channel element

REG: resource Element Group, Resource Element Group

MIB: master Information Block, Master Information Block

DRX: discontinuous Reception, Discontinuous Reception

AL: aggregation Level, Aggregation Level

UCI: uplink Control Information, Uplink Control Information

CSS: common search space, Common search space

And (3) USS: UE-specific search space, user search space

SCS: sub-carrier spacing, subcarrier spacing

SLIV: start and length indicator value, Start and length indicator value

RIV: resource indicator value, a Resource indication value

SS-RSRP: synchronization Signal Reference Signal Received Power, synchronous Reference Signal Received Power

SS-RSRQ: synchronization Signal Reference Signal Received Quality, synchronous Reference Signal Received Quality

FR 1: frequency range 1as defined in TS38.104, Frequency range 1 defined by TS38.104

FR 2: frequency range 2as defined in TS38.104, Frequency range 2 defined by TS38.104

The following is a description of the prior art associated with the inventive arrangements. Unless otherwise specified, the meanings of the same terms in the specific examples are the same as those in the prior art.

It should be noted that the UE referred to in the present specification has the same meaning as the terminal device, and the UE herein may also refer to the terminal device, which is not specifically distinguished and limited hereinafter. Similarly, the network device is a device for communicating with the terminal, and includes but is not limited to a base station device, a gbb, an eNB, a wireless AP, and the like, and is not specifically distinguished and limited hereinafter.

The network uses BWP configuration to determine information such as bandwidth required for traffic transmission with the terminal. The BWP configuration contains parameters such as corresponding bandwidth, location, subcarrier spacing, cyclic prefix, etc. The network and the terminal perform data transmission on BWP. For example, the network may indicate which symbols are used by the scheduled resource blocks on which RBs of the BWP through scheduling information DCI in the PDCCH, and other related receiving or transmitting configuration information, etc. for data transmission with the terminal.

The network configures the CORESET on BWP for PDCCH reception, and the network also configures the parameters of search space to determine the CORESET required to be detected by the terminal and the corresponding parameters of time domain position and the like.

The network may configure an initial uplink BWP and an initial downlink BWP for the cell for the terminal to perform random access or data transmission. If the network does not configure the initial downlink BWP through fields in SIB1 signaling, the terminal takes the bandwidth determined by CORESET0 as the initial downlink BWP.

The terminal device may receive the PDCCH according to the received parameters and the associated protocol procedures. The PDCCH indicates transmission configuration information of the scheduled PDSCH, including time-frequency location of the PDSCH, resource configuration, and other necessary parameters. And the terminal receives the related PDSCH according to the configuration parameters of the PDSCH.

The network device periodically transmits broadcast information containing parameters for determining various configurations of the cell. For example, the cell sends MIB information indicating the CORESET used for receiving the PDCCH and configuration information of the search space, and the terminal may obtain time-frequency location, bandwidth and other relevant configuration parameters of the channel of SIB1 and other information according to the indication of the PDCCH, so as to obtain more relevant information for accessing the cell and services such as data transmission.

A specific example is that the network indicates the parameters related to core set0 and search space 0 in MIB, and the terminal can receive PDCCH on the corresponding time-frequency resource. The PDCCH indicates parameters of PDSCH for transmitting SIB 1. The terminal receives the PDSCH, obtains SIB1 information, and obtains configuration, parameters, and other information for service transmission. The terminal may also receive other SIB information in a similar manner, to obtain more service configuration information.

The SIB1 information may include parameters for the terminal to perform random access and data transmission, such as a downlink initial BWP parameter, an uplink initial BWP parameter, a random access channel parameter, and a random access search space parameter. In a specific example, in the case that the condition for accessing the network is satisfied, for example, when the uplink or downlink bandwidth supported by the terminal is greater than the uplink or downlink BWP bandwidth configured by the network, the terminal may send a random access signal through a random access channel to access the network. After receiving the random access signal of the terminal, the network responds, and indicates related information, such as resource allocation for notifying the UE of uplink transmission, through the PDCCH of the related common search space and the scheduled PDSCH signal. The terminal initiates a relevant request, such as a wireless network connection request signaling, on the indicated uplink resource. The network may respond to the request and schedule the PDSCH to transmit appropriate response information via the PDCCH of the common search space, thereby establishing a wireless link connection between the network and the terminal.

The network may also indicate configuration parameters for a certain type of terminal through SIBl or other RRC signaling so that the type of terminal may perform a random access or data transmission procedure in the network.

The network may define the type or category (type) of the terminal, for example a low complexity terminal may be defined based on a certain physical layer capability or a combination of capabilities of the terminal, such as the number of channels, processing time constraints, maximum bandwidth, duplexing capabilities, etc. The network may also define a terminal type for identifying a plurality of capability sets with different combinations of capabilities. The type information of the terminal may be used for the network to allow or disallow this type of terminal access, or for the network to configure appropriate parameters for this type of terminal for its access or data transmission, or for the network to restrict the use of certain parameters by this type of terminal.

For some terminal devices, when accessing a certain network, according to the received SIB1 information, it finds that the maximum bandwidth supported by the terminal device is smaller than the bandwidth of the uplink initial BWP or the downlink initial BWP indicated by the network, but larger than the maximum bandwidth used by the network for transmitting SIB1 information. At this time, the network may configure a different uplink and/or downlink BWP from the uplink initial BWP or the downlink initial BWP, where the bandwidth of the BWP is less than or equal to the maximum bandwidth supported by the terminal device, so that the terminal devices may perform random access in the cell, and send and receive related information. In this case, the network configuration enables the terminal with smaller bandwidth capability to access the network and perform related service transmission when the initial BWP bandwidth notified in the SIB1 of the network is greater than the terminal capability, thereby improving the service capability of the network, expanding the compatibility of the network, and greatly reducing the cost of communication network deployment. Meanwhile, the scheme also reduces the bandwidth requirement on the terminal, so that the cost, the compatibility and the like of the terminal obtain obvious benefits.

And the terminal receives the network indication information sent by the system. If the maximum uplink or downlink transmission bandwidth supported by the terminal is less than or equal to the carrier bandwidth of the initial uplink or downlink BWP indicated by the network and the uplink or downlink bandwidth supported by the terminal is greater than or equal to the BWP bandwidth configured by the network for the type of terminal, the terminal applies a bandwidth greater than or equal to the BWP bandwidth configured by the type as the transmission bandwidth of the terminal, otherwise the terminal considers that the cell prohibits the access of the terminal.

And the terminal receives the network indication information sent by the system. If the network indication information does not contain the bandwidth of the BWP configured for the type of terminal, if the maximum uplink or downlink transmission bandwidth supported by the terminal is greater than or equal to the carrier bandwidth of the initial uplink or downlink BWP indicated by the network, the terminal applies a bandwidth greater than or equal to the initial uplink or downlink BWP bandwidth indicated by the network as the transmission bandwidth of the terminal, otherwise, the terminal considers that the cell forbids the access of the terminal.

Fig. 1 is a flowchart illustrating a method performed by a user equipment UE according to embodiment 1 of the present invention.

As shown in fig. 1, BWP configuration information of UE type configuration of a UE by a network is received, wherein BWP corresponding to the BWP configuration information is different from cell initial downlink BWP in step 101.

Then, in step 103, at least one of a PDCCH position in a common search space, a width and a numerical value of a frequency domain indication field in DCI for data scheduling, and a position of a scheduled PDSCH resource is determined according to the received BWP configuration information.

Specifically, the terminal may perform a random access procedure or a data transmission procedure in a cell configured with the CORESET0 according to the type and/or capability of the terminal and an indication of a network. And the terminal determines the PDCCH searching position in the related public searching space, the width and the value of the frequency domain indication domain in the DCI scheduled by the data, the position of the scheduled PDSCH resource, the reference wave beam of the DMRS and other information according to the configuration condition.

And the DCI carried by the PDCCH in the common search space uses a PDSCH frequency domain resource allocation mode of Typel in the process of scheduling PDSCH data transmission. The network may be such that the PDSCH is of size

A contiguous segment of RBs is allocated within the BWP band for data transmission. The frequency resource allocation indication field in the DCI indicates a specific allocation to a time-frequency resource location for data transmission using an RIV (resource indication value). The RIV value determines that the bandwidth covered by the scheduled continuous RB in the indication field is

Relative starting position RB in the resource of_startAnd length L_RBs. For example, the following method can be used according to RB_startAnd a length L_RBsThe RIV value transmitted in the DCI is determined, and the corresponding RB can be derived according to the RIV value_startAnd length L_RBsThereby determining resource locations for PDSCH transmission.

If it is not

Then

Otherwise

Where L is_RBsNot less than 1 and not more than

The DCI for downlink data scheduling includes a frequency domain resource allocation indication field indicating the allocation of resources on a bandwidth for the scheduled PDSCH. For example, when the PDSCH resource allocation scheme of Type1 is used, the bit length of the indicator field is set to

Wherein

Is the bandwidth of the BWP used.

The terminal also determines the mapping position of the resource block indicated in the DCI in the actual physical channel according to a suitable method, that is, the terminal maps the indicated resource to the actually transmitted PDSCH resource position according to the relative resource position indicated by the RIV, the starting position of the relevant physical resource, and other configuration parameters such as interleaving parameters. For example, the terminal determines the RB resources indicated by the RIV one by one according to the determined resource start position, or the terminal starts interleaving the number of RBs of the bandwidth associated with the RIV according to the determined resource start position and maps the resources indicated by the RIV according to the interleaving rule.

As an embodiment of this example, the network configures BWP for a certain type of terminal for random access or data transmission of the type of terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal. In the cell configured with the CORESET0, the terminal determines the position relation of BWP and CORESET0 according to the type and/or capability of the terminal and the indication of the network. If the BWP contains all RBs of CORESET0, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the information of the width, value and position of the scheduled PDSCH resource of the frequency domain indication domain in the DCI of the relevant data scheduling. If the BWP does not contain all RBs of the CORESET0, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the information such as the width and value of the frequency domain indication domain in the DCI of the relevant data scheduling and the location of the scheduled PDSCH resource.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0, the terminal receives a PDCCH for the type of terminal random access procedure using a random access search space on the initial BWP indicated by the network. If the BWP does not contain all RBs of the CORESET0, the terminal receives the PDCCH for the type of terminal random access procedure using the random access search space on the BWP and does not receive the PDCCH of the random access search space on the initial BWP.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0, the terminal determines the width of the frequency domain indication field in the DCI of the associated data schedule using the bandwidth of CORESET0 and the subcarrier spacing parameters. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS. If the BWP does not contain CORESET0For all RBs, the terminal determines the width of the frequency domain indication domain in the DCI for the associated data scheduling using the bandwidth of the BWP and the subcarrier spacing parameters. The bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

the number of RBs determined for the BWP bandwidth and its SCS.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data schedule using the bandwidth of CORESET0 and the subcarrier spacing parameters. The RIV value of the frequency domain indicator field in DCI for a common search space is determined by the bandwidth of CORESET0,

number of RBs, RBs determined for CORESET0 bandwidth and its SCS_startOffset of scheduled resource from minimum RB of CORESET0, L_RBsThe number of RBs of the scheduled resource. If the BWP does not contain all RBs of the CORESET0, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the frequency domain indicator field in the DCI for the associated data schedule. The RIV value of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of BWP,

number of RBs, determined for BWP bandwidth and SCS thereof_startOffset for scheduled resource from the smallest RB of the BWP where the DCI is located, L_RBsThe number of RBs that are scheduled resources.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB number of CORESET 0. If the BWP does not contain all RBs of the core set0, the terminal determines the resource allocation of the data channel using the bandwidth of the BWP and the subcarrier spacing parameters, and the scheduled PDSCH resource location is mapped from the smallest RB number of the core set that schedules the PDSCH on the BWP.

As an embodiment of this example, the network configures BWP for a certain type of terminal for random access or data transmission of the type of terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal. In the cell configured with the CORESET0, the terminal determines the position relationship and subcarrier spacing parameter relationship between BWP and CORESET0 according to the type and/or capability of the terminal and the indication of the network. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal determines the width, value and location of the scheduled PDSCH resources of the DCI frequency domain indication field of the associated data scheduling using the bandwidth of CORESET0 and the subcarrier spacing parameter. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the width, value and location of the scheduled PDSCH resources in the DCI that determines the associated data scheduling using the bandwidth of the BWP and the subcarrier spacing parameters.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the terminal of the type. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal receives the PDCCH for the type of terminal random access procedure using the random access search space on the initial BWP indicated by the network. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal receives a PDCCH for the type of terminal random access procedure using a random access search space on the BWP and does not receive a PDCCH for the random access procedure on the random access search space on the initial BWP.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0, and the same subcarrier spacing parameter and cyclic prefix parameter are used, the networkThe bandwidth of CORESET0 and the subcarrier spacing parameter are used to determine the width of the frequency domain indication field in DCI for the associated data schedule. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the width of the frequency domain indication field in the DCI of the associated data scheduling using the bandwidth of the BWP and the subcarrier spacing parameters. The bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

the number of RBs determined for the BWP bandwidth and its SCS.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the value of the frequency domain indicator field in the DCI for the associated data schedule. The RIV value of the frequency domain indicator field in DCI for a common search space is determined by the bandwidth of CORESET0,

number of RBs, RBs determined for CORESET0 bandwidth and its SCS_startOffset of scheduled resource from minimum RB of CORESET0, L_RBsThe number of RBs of the scheduled resource. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data schedule using the bandwidth of the BWP and the subcarrier spacing parameters. The RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

number of RBs, determined for BWP bandwidth and SCS thereof_startOffset for scheduled resource from the smallest RB of the BWP where the DCI is located, L_RBsThe number of RBs of the scheduled resource.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of CORESET 0. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the resource allocation of the data channel using the bandwidth of the BWP and the subcarrier spacing parameters, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

As an embodiment of this example, the network configures BWP for a certain type of terminal for random access or data transmission of the type of terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal. In the cell configured with the CORESET0, the terminal determines the position relationship and subcarrier spacing parameter relationship between BWP and CORESET0 according to the type and/or capability of the terminal and the indication of the network. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal determines the width, value and location of the scheduled PDSCH resources of the associated data scheduled DCI frequency domain indicator field using the bandwidth of CORESET0 and the subcarrier spacing parameter. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the width, value and location of the scheduled PDSCH resources in DCI that determines the relevant data scheduling using the bandwidth of CORESET0 and the bandwidth of the BWP and the subcarrier spacing parameters.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal receives a PDCCH for the type of terminal random access procedure using the random access search space on the initial BWP indicated by the network. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal receives a PDCCH for the type of terminal random access procedure using a random access search space on the BWP and does not receive a PDCCH for the random access procedure on the random access search space on the initial BWP.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the terminal of the type. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width of the frequency domain indication field in the DCI of the associated data schedule. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0, the number of RBs determined for CORESET0 bandwidth and its SCS. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the width of the frequency domain indication field in the DCI of the associated data scheduling using the CORESET0 bandwidth and the number of RBs determined by its SCS. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the value of the frequency domain indicator field in the DCI for the associated data schedule. The RIV value of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the bandwidth of CORESET0 and its SCS, RBstart is the offset of the scheduled resource from the smallest RB of CORESET0, and LRBs is the number of RBs of the scheduled resource. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data schedule using the bandwidth of the BWP and the subcarrier spacing parameters. The RIV value of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0 and the bandwidth of BWP. Note the book

The number of RBs determined for the CORESET0 bandwidth and its SCS,

the number of RBs determined for the BWP bandwidth and its SCS. RIV values for determining usage on BWP

And

the mapping location of the VRB of some combination.

If it is not

Then the

Otherwise

Wherein L'_RBs＝L_RBs/K，RB′_start＝RB_startL and K'_RBsNot more than

If it is not

K is satisfied in the set {1, 2, 4, 8}

Otherwise K is 1.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of CORESET 0. If the BWP does not contain all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the resource allocation of the data channel using the bandwidth of the BWP and the subcarrier spacing parameters, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

As an embodiment of this example, the network configures BWP for a certain type of terminal for random access or data transmission of the type of terminal, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal. In the cell configured with the CORESET0, the terminal determines the position relation and the subcarrier spacing parameter relation of BWP and CORESET0 according to the type and/or capability of the terminal and the indication of the network. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal determines the width, value and location of the scheduled PDSCH resources of the DCI frequency domain indication field of the associated data scheduling using the bandwidth of CORESET0 and the subcarrier spacing parameter. If the BWP does not contain all RBs of the CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal determines the width, value and location of the scheduled PDSCH resources in the DCI of the associated data scheduling using the bandwidth, subcarrier spacing parameter and start location of the BWP of the CORESET 0. If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the width, value and location of the scheduled PDSCH resources of the relevant data scheduled DCI frequency domain indication field using the BWP bandwidth and subcarrier spacing parameters.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal receives the PDCCH for the type of terminal random access procedure using the random access search space on the initial BWP indicated by the network. If the BWP does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal receives a PDCCH for a random access procedure of the type terminal using CORESET0 of the same size on the BWP and does not receive a PDCCH for a random access procedure on CORESET 0. If the BWP does not contain all RBs of the CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the terminal receives a PDCCH for the type of terminal random access procedure using a random access search space on the BWP and does not receive a PDCCH of the random access search space on the initial BWP.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal determines the width of the frequency domain indication field in DCI of the associated data scheduling using the bandwidth of CORESET0 and the subcarrier spacing parameter. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS. If the BWP does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of CORESET0, the subcarrier spacing parameter, and the starting position of the BWP to determine the associated DCI IF for data schedulingThe field indicates the width of the field. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS. If the BWP does not contain all RBs of the CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the terminal determines the resource configuration of the data channel using the bandwidth of the BWP and the subcarrier spacing parameter. The bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

the number of RBs determined for the BWP bandwidth and its SCS.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and the same subcarrier spacing parameter and cyclic prefix parameter are used, the terminal determines the value of the frequency domain indicator field in DCI for the associated data scheduling using the bandwidth of CORESET0 and the subcarrier spacing parameter. The RIV value of the frequency domain indicator field in DCI for a common search space is determined by the bandwidth of CORESET0,

number of RBs, RBs determined for CORESET0 bandwidth and its SCS_startOffset of scheduled resource from minimum RB of CORESET0, L_RBsThe number of RBs of the scheduled resource. If the BWP does not contain all RBs of the CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data schedule using the bandwidth of the CORESET0, the subcarrier spacing parameter, and the start position of the BWP. The RIV value of the frequency domain indicator field in DCI for a common search space is determined by the bandwidth of CORESET 0.

Number of RBs, RBs determined for CORESET0 bandwidth and its SCS_startIs the offset of the scheduled resource from the minimum RB of the CORESET where the DCI is located, L_RBsThe number of RBs of the scheduled resource.

If the BWP does not contain all RBs of CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the terminal determines the value of the frequency domain indicator field in the DCI for the associated data schedule using the bandwidth of the BWP and the subcarrier spacing parameter. The RIV value of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

number of RBs, determined for BWP bandwidth and SCS thereof_startOffset for scheduled resource from the smallest RB of the BWP where the DCI is located, L_RBsThe number of RBs of the scheduled resource.

Optionally, the network configures BWP for a certain type of terminal, and the BWP is used for random access or data transmission of the type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB number of CORESET 0. If the BWP does not contain all RBs of the core set0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the resource configuration of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB number of the core set where the DCI of the PDSCH is scheduled on the BWP. If the BWP does not contain all RBs of the CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal determines the resource allocation of the data channel using the bandwidth of the BWP and the subcarrier spacing parameters, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

As an embodiment of this example, the network configures BWP for a certain type of terminal or does not configure BWP for a terminal device of this type for random access or data transmission by the terminal device of this type. If the terminal receives the BWP configuration associated with the terminal type and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for the terminal type, the terminal uses the BWP bandwidth to determine the width and value of the frequency domain indicator field in the DCI of the associated data scheduling and the location of the scheduled PDSCH resource. If the terminal does not receive the BWP configuration for this type of terminal, the terminal determines the width, value and location of the scheduled PDSCH resources in the DCI of the relevant data scheduling using the initial BWP or CORESET0 associated with the cell.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal device of the type. If the terminal receives the BWP configuration associated with the terminal type, the terminal receives the PDCCH for the random access procedure of the terminal of the type using the random access search space on the BWP and does not receive the PDCCH of the random access search space on the initial BWP. If the terminal does not receive the BWP configuration for the type of terminal, the terminal receives the PDCCH for the random access procedure for the type of terminal using CORESET 0.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal device of the type. If the terminal receives the BWP configuration associated with the terminal type, the terminal determines the width of the frequency domain indication field in the DCI of the associated data scheduling using the BWP bandwidth. The bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

the number of RBs determined for the BWP bandwidth and its SCS. If the terminal does not receive the BWP configuration for the type of terminal, the terminal determines the width of the frequency domain indication field in the DCI of the associated data scheduling using the initial BWP of the cell. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal of the type. If the terminal receives the BWP configuration associated with the terminal type, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data scheduling using the BWP bandwidth. The RIV value of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of BWP,

number of RBs, determined for BWP bandwidth and SCS thereof_startOffset for scheduled resource from the smallest RB of the BWP where the DCI is located, L_RBsThe number of RBs of the scheduled resource. If the terminal does not receive the BWP configuration for the type of terminal, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data scheduling using the initial BWP associated with the cell. The RIV value of the frequency domain indicator field in DCI for a common search space is determined by the bandwidth of CORESET0,

number of RBs, RBs determined for CORESET0 bandwidth and its SCS_startOffset of the scheduled resource from the minimum RB of CORESET0, L_RBSThe number of RBs of the scheduled resource.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal device of the type. If the terminal receives the BWP configuration related to the terminal type, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the resource configuration of the data channel, and the scheduled PDSCH resource position schedules the minimum RB sequence number of the CORESET of the PDSCH from the BWP for mapping. If the terminal does not receive the BWP configuration for this type of terminal, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB number of CORESET 0.

As an embodiment of this example, the network configures BWP for a certain type of terminal or does not configure BWP for a terminal device of this type for random access or data transmission by the terminal device of this type. If the terminal receives the BWP associated with the terminal type and the CORESET on the BWP for carrying the random access search space, the terminal uses the BWP bandwidth configuration to determine the width and value of the frequency domain indicator field in the DCI of the associated data scheduling and the location of the scheduled PDSCH resource. If the terminal does not receive the BWP configuration for the type of terminal or the CORESET configuration for carrying the random access search space on the BWP, the terminal determines the width, value and location of the scheduled PDSCH resources in the DCI of the associated data schedule using the initial BWP or CORESET0 associated with the cell.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal device of the type. If the terminal receives the BWP configuration associated with the terminal type and the CORESET for the random access search space on the BWP, the terminal uses the CORESET on the BWP to receive the PDCCH for the random access procedure of the terminal type and does not receive the PDCCH for the random access procedure on CORESET 0. If the terminal does not receive the BWP configuration for the type of terminal or the CORESET configuration for the random access search space on the BWP, the terminal receives the PDCCH for the random access procedure for the type of terminal using CORESET 0.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal of the type. If the terminal receives the BWP related to the terminal type and the CORESET or search space configuration for carrying type1-PDCCH on the BWP, the terminal determines the width of the frequency domain indication field in the DCI of the related data scheduling using the BWP bandwidth configuration. The bit length of the frequency domain indication field in the DCI for the common search space is determined by the bandwidth of BWP,

the number of RBs determined for the BWP bandwidth and its SCS. If the terminal does not receive the BWP configuration for the type of terminal or the CORESET or search space configuration for carrying type1-PDCCH on the BWP, the terminal uses the initial BWP related to the cellDetermining a width of a frequency domain indication domain in the DCI of the associated data scheduling. The bit length of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of CORESET0,

the number of RBs determined for the CORESET0 bandwidth and its SCS.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal of the type. If the terminal receives the BWP associated with the terminal type and the CORESET and search space configuration for randomly accessing the search space on the BWP, the terminal determines the value of the frequency domain indicator field in the DCI of the associated data schedule using the BWP bandwidth configuration. The RIV value of the frequency domain indication field in DCI for a common search space is determined by the bandwidth of BWP,

number of RBs, determined for BWP bandwidth and SCS thereof_startOffset for scheduled resource from the smallest RB of the BWP where the DCI is located, L_RBSThe number of RBs of the scheduled resource. If the terminal does not receive the BWP configuration for the type of terminal or the CORESET or search space configuration for carrying the type-PDCCH on the BWP, the terminal determines the value of the frequency domain indication field in the DCI of the relevant data scheduling using the initial BWP related to the cell. The RIV value of the frequency domain indicator field in DCI for a common search space is determined by the bandwidth of CORESET0,

number of RBs, RBs determined for CORESET0 bandwidth and its SCS_startOffset of the scheduled resource from the minimum RB of CORESET0, L_RBSThe number of RBs that are scheduled resources.

Optionally, the network configures BWP for a certain type of terminal, or does not configure BWP for the terminal device of the type, for random access or data transmission of the terminal device of the type. If the terminal receives the BWP configuration related to the terminal type and the CORESET or search space configuration for randomly accessing the search space on the BWP, the terminal determines the resource configuration of the data channel using the bandwidth of the BWP and the subcarrier spacing parameter, and the scheduled PDSCH resource location is mapped from the minimum RB number of the CORESET of the PDSCH scheduled on the BWP. If the terminal does not receive the BWP configuration for the type of terminal or the CORESET or search space configuration for the random access search space on the BWP, the terminal determines the resource location of the data channel using the bandwidth of CORESET0 and the subcarrier spacing parameter, and the scheduled PDSCH resource location is mapped from the smallest RB number of CORESET 0.

According to one or a combination of the above methods, the terminal may determine the width of the frequency domain indication field in the DCI for data scheduling for the common search space of the type of terminal, and thus may determine the size of the DCI. The network and the terminal may also be configured to determine the DCI size for the user search space based on the determined DCI size for the common search space. For example, when the DCI for the user search space and the DCI size of the common search space are not equal, and the total DCI type number exceeds the receiving capability of the terminal, the size of the partial DCI is aligned to the determined size of the common search space DCI by zero padding or bit truncation. Accordingly, resource location information of the relevant scheduled PDSCH or PUSCH can be determined according to the value indicated after zero padding or bit truncation.

[ modified examples ]

As a modification, a user equipment capable of executing the method performed by the user equipment described in detail above of the present invention is described below with reference to fig. 2.

Fig. 2 is a block diagram showing a user equipment UE according to the present invention.

As shown in fig. 2, the user equipment UE20 includes a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 202 may include, for example, volatile memory (e.g., random access memory RAM), a Hard Disk Drive (HDD), non-volatile memory (e.g., flash memory), or other memory, among others. The memory 202 has stored thereon program instructions. Which when executed by the processor 201 may perform the above-described method performed by the user equipment as described in detail in the present invention.

The method of the invention and the apparatus involved have been described above in connection with preferred embodiments. It will be appreciated by those skilled in the art that the above illustrated approaches are exemplary only, and that the various embodiments described above can be combined with each other without conflict. The method of the present invention is not limited to the steps or sequence shown above. The network nodes and user equipment shown above may comprise further modules, e.g. modules that may be developed or developed in the future, which may be available to a base station, MME, or UE, etc. The various identifiers shown above are exemplary only and not limiting, and the invention is not limited to the specific cells as examples of such identifiers. Many variations and modifications may be made by those skilled in the art in light of the teachings of the illustrative embodiments.

It should be understood that the above-described embodiments of the present invention can be implemented by software, hardware, or a combination of both software and hardware. For example, various components within the base station and the user equipment in the above embodiments may be implemented by various means, including but not limited to: analog circuit devices, Digital Signal Processing (DSP) circuits, programmable processors, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), programmable logic devices (CPLDs), and the like.

In this application, a "base station" may refer to a mobile communication data and control switching center with a large transmission power and a wide coverage area, and includes functions of resource allocation scheduling, data receiving and transmitting, and the like. "user equipment" may refer to a user mobile terminal, including, for example, a mobile phone, a notebook, etc., which may wirelessly communicate with a base station or a micro base station.

Furthermore, embodiments of the invention disclosed herein may be implemented on a computer program product. More specifically, the computer program product is one of the following: there is a computer readable medium having computer program logic encoded thereon that, when executed on a computing device, provides related operations for implementing the above-described aspects of the present invention. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in embodiments of the present invention. Such arrangements of the invention are typically provided as downloadable software images, shared databases, etc. arranged or encoded in software, code and/or other data structures on a computer readable medium such as an optical medium (e.g., CD-ROM), floppy or hard disk or other medium such as firmware or microcode on one or more ROM or RAM or PROM chips or in one or more modules. The software or firmware or such configurations may be installed on a computing device to cause one or more processors in the computing device to perform the techniques described in embodiments of the present invention.

Further, each functional block or respective feature of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is typically one or more integrated circuits. Circuitry designed to perform the various functions described in this specification may include a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC) or a general purpose integrated circuit, a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit, or may be configured by a logic circuit. Further, when advanced technology capable of replacing the current integrated circuit is developed due to the advancement of semiconductor technology, the present invention can also use the integrated circuit obtained by the advanced technology.

Although the present invention has been described in conjunction with the preferred embodiments thereof, it will be understood by those skilled in the art that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention. Accordingly, the present invention should not be limited by the above-described embodiments, but should be defined by the appended claims and their equivalents.

Claims (10)

1. A method performed by a User Equipment (UE), comprising:

receiving bandwidth segment BWP configuration information configured by a network for a UE type of the UE, wherein a BWP corresponding to the BWP configuration information is different from a cell initial downlink BWP; and

and determining at least one of a Physical Downlink Control Channel (PDCCH) position in a common search space, a width and a numerical value of a frequency domain indication domain in Downlink Control Information (DCI) for data scheduling and a position of a scheduled Physical Downlink Shared Channel (PDSCH) resource according to the received BWP configuration information.

2. The method of claim 1, wherein,

if the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI and a position of scheduled PDSCH resources using a bandwidth of CORESET0 and a subcarrier spacing parameter;

if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI and a position of scheduled PDSCH resources using a bandwidth of the BWP and a subcarrier spacing parameter.

3. The method of claim 1, wherein,

if the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0, the UE receives PDCCH for a random access procedure of the UE using a random access search space on a cell initial BWP;

if the BWP corresponding to the BWP configuration information does not include all RBs of the CORESET0, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on the BWP and does not receive a PDCCH of a random access search space on a cell initial BWP.

4. The method of claim 1, wherein,

if the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI, and a location of scheduled PDSCH resources using a bandwidth of CORESET0 and the subcarrier spacing parameter;

if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth of the BWP and the subcarrier spacing parameters.

5. The method of claim 1, wherein,

if the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on a cell initial BWP;

if the BWP corresponding to the BWP configuration information does not include all RBs of the CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on the BWP and does not receive a PDCCH of a random access search space on a cell initial BWP.

6. The method of claim 1, wherein,

if the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI, and a location of scheduled PDSCH resources using a bandwidth of CORESET0 and the subcarrier spacing parameter;

if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE determines at least one of a width, a value, and a position of scheduled PDSCH resources in the DCI using a bandwidth, subcarrier spacing parameter, and a starting position of BWP of the CORESET 0;

if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI, and a location of the scheduled PDSCH resource using a bandwidth of the BWP and the subcarrier spacing parameter.

7. The method of claim 1, wherein,

if the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on a cell initial BWP;

if the BWP corresponding to the BWP configuration information does not include all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE receiving a PDCCH for a random access procedure of the UE using a CORESET of the same size as CORESET0 on the BWP, and not receiving a PDCCH for a random access procedure on a random access search space on a cell initial BWP;

if the BWP corresponding to the BWP configuration information does not include all RBs of the CORESET0 and uses a different subcarrier spacing parameter or a different cyclic prefix parameter, the UE receives a PDCCH for a random access procedure of the UE using the CORESET on the BWP and does not receive a PDCCH of a random access search space on a cell initial BWP.

8. The method of claim 1, wherein,

if the UE receives BWP configured by a network for the UE, the UE determines at least one of a width and a value of a frequency domain indication field in the DCI and a position of scheduled PDSCH resources using a bandwidth of the BWP;

if the UE does not receive the BWP configured by the network for the UE, the UE determines at least one of a width, a value of a frequency domain indication field in the DCI and a position of the scheduled PDSCH resource using a cell-dependent initial BWP or CORESET 0.

9. The method of claim 1, wherein,

if the UE receives BWP configured by a network for the UE, the UE receives a PDCCH for a random access procedure of the UE using a random access search space on the BWP, and does not receive the PDCCH of the random access search space on cell initial BWP;

and if the UE does not receive the BWP configured by the network for the UE, the UE receives a PDCCH for a random access procedure of the UE by using a random access search space on the initial BWP of the cell.

10. A user equipment, comprising:

a processor; and

a memory having stored therein instructions that, when executed,

wherein the instructions, when executed by the processor, perform the method of any of claims 1 to 9.

Images