CN114765868A

CN114765868A - Method performed by user equipment and user equipment

Info

Publication number: CN114765868A
Application number: CN202110051741.2A
Authority: CN
Inventors: 罗超; 刘仁茂; 马小骏
Original assignee: Sharp Corp
Current assignee: Sharp Corp
Priority date: 2021-01-14
Filing date: 2021-01-14
Publication date: 2022-07-19
Also published as: WO2022152160A1

Abstract

The invention provides a method executed by user equipment and the user equipment, wherein the method executed by the user equipment comprises the following steps: obtaining downlink BWP configuration information, and determining one or more parameters of initial downlink BWP, including bandwidth of the initial downlink BWP

Is determined as

And starting resource block of the initial downlink BWP

Is determined as

Wherein the content of the first and second substances,

and

respectively the starting resource block and the bandwidth of the CORESET with the index of 0,

is a predefined maximum transmission bandwidth configuration,

is the bandwidth configured in the downlink BWP configuration information.

Description

Method performed by user equipment and user equipment

Technical Field

The present invention relates to a method performed by a user equipment and a user equipment.

Background

The red map feature introduced in 5G systems aims to reduce the complexity of 5G UEs in several respects, for example to reduce the maximum channel bandwidth of the UE. The limitation of the reccap UE on the maximum channel bandwidth makes it necessary for various BWP-based operations in 5G to adapt the maximum channel bandwidth for the UE in terms of initial access, resource allocation, etc.

Prior art documents

Non-patent document

Non-patent document 1: RP-170855, New WID on New Radio Access Technology

Non-patent document 2: RP-202933, New WID on support of reduced capability NR devices

Disclosure of Invention

To solve at least part of the above problems, the present invention provides a method performed by a user equipment and the user equipment, which improves resource utilization efficiency of a red map UE and a non-red map UE at the time of initial access by determining an initial downlink BWP (or initial uplink BWP) of the red map UE within a conventional initial downlink BWP (or initial uplink BWP).

According to the invention, a method performed by a user equipment is proposed, characterized by comprising: obtaining downlink BWP configuration information, and determining one or more parameters of initial downlink BWP, including bandwidth of the initial downlink BWP

Is determined as

And starting resource block of the initial downlink BWP

Is determined as

Wherein,

and

is a predefined maximum transmission bandwidth configuration,

is the bandwidth configured in the downlink BWP configuration information.

Further, according to the present invention, there is provided a method performed by a user equipment, characterized by comprising: obtaining and/or determining scheduling information related to one PUSCH transmission, and determining one or more PRBs for the PUSCH transmission. Wherein if the scheduling information is indicated by a RAR uplink grant (RAR UL grant) and the scheduling information is indicated by a DCI format 0_0, where CRC of the DCI format 0_0 is scrambled with TC-RNTI, and the active uplink BWP includes all RBs of the initial uplink BWP, and SCS of the active uplink BWP is the same as SCS of the initial uplink BWP, and CP of the active uplink BWP is the same as CP of the initial uplink BWP, VRB numbered n is mapped to VRB numbered n

The PRB of (1). Wherein,

and

the starting RB for the initial upstream BWP and the active upstream BWP, respectively.

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.

Accordingly, the present invention provides a method for improving resource utilization efficiency of a recmap UE and a non-recmap UE at the time of initial access by determining an initial downlink BWP (or initial uplink BWP) of the recmap UE within a conventional initial downlink BWP (or initial uplink BWP).

In addition, the invention provides a method, when the initial transmission or the retransmission of the PUSCH which can be scheduled by the RAR uplink permission is transmitted, a VRB-to-PRB mapping mode which is different from the VRB-to-PRB mapping mode used for non-RedCap UE is used for the RedCap UE, so that the resource allocation starting point of the RedCap UE can be compatible with the non-RedCap UE, the multiplexing capability of the RAR uplink permission is improved, and the efficiency of resource allocation and utilization is further improved.

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 a first embodiment of the present invention.

Fig. 2 is a flow chart illustrating a method performed by a user equipment according to a second embodiment of the present invention.

Fig. 3 shows a block diagram of a user equipment UE 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. 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.

Embodiments according to the present invention are described in detail below with a 5G 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 is applicable to more other wireless communication systems, such as a communication system after 5G and a 4G mobile communication system before 5G.

Some terms referred to by the present invention are described below, and the terms referred to by the present invention are defined herein, unless otherwise specified. The terms given in the invention may adopt different naming manners in LTE, LTE-Advanced Pro, NR and the following communication systems, but the unified terms adopted in the invention can be replaced by the terms adopted in the corresponding systems when being applied to the specific systems.

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

AMF: access and Mobility Management Function

AS: access Stratum, Access Stratum

BWP: bandwidth Part, Bandwidth fragment

CBR: channel Busy Ratio, Channel Busy Ratio

CD-SSB: cell Defining SSB, Cell definition SSB

CORESET: control Resource Set, controlling Resource Set

And (3) CP: cyclic Prefix, Cyclic Prefix

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

CRB: common Resource Block, Common Resource Block

CSI: channel-state Information, Channel state Information

CSS: common Search Space, Common Search Space

DC: dual connectivity, Dual connectivity

DFT-s-OFDM: discrete Fourier transform Spread Orthogonal Frequency Division Multiplexing

DL: downlink, Downlink

DM-RS: demodulation reference signal (DMRS)

eMBB: enhanced Mobile Broadband, Enhanced Mobile Broadband

eNB: E-UTRAN Node B, E-UTRAN Node B

E-UTRAN: evolved UMTS Terrestrial Radio Access Network

FDD: frequency Division Duplexing

FDRA: frequency Domain Resource Assignment, Frequency Domain Resource allocation

FR 1: frequency Range 1, Frequency Range 1

FR 2: frequency Range 1, Frequency Range 2

And g NB: NR Node B, NR Node B

HARQ: hybrid Automatic Repeat Request (HARQ)

HARQ-ACK: HARQ Acknowledgement, HARQ Acknowledgement

HD-FDD: half-duplex FDD

ID: identity, Identifier

IE: information Element, Information Element

LPWA: Low-Power Wide-Area, Low-Power Wide Area

LTE: long Term Evolution, Long Term Evolution

And (3) LTE-A: long Term Evolution-Advanced, Long Term Evolution-upgraded version

MAC: medium Access Control, Medium Access Control

MAC CE: MAC Control Element, MAC Control Element

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

MIB: master Information Block, Master Information Block

MIMO: multiple Input Multiple Output, Multiple Input Multiple Output

MME: mobility Management Entity

NAS: Non-Access-Stratum, Non-Access Stratum

NDI: new Data Indicator, New Data Indicator

NR: new Radio, fine generation Radio access technology, fifth generation Radio access technology

OFDM: orthogonal Frequency Division Multiplexing

PBCH: physical Broadcast Channel, Physical Broadcast Channel

PCell: primary Cell

PDCCH: physical Downlink Control Channel, Physical Downlink Control Channel

PDCP: packet Data Convergence Protocol (PDMP)

PRACH: physical Random Access Channel, Physical Random Access Channel

PRB: physical Resource Block, Physical Resource Block

PSCell: primary SCG Cell, Primary SCG Cell

PSS: primary Synchronization Signal, Primary Synchronization Signal

RB: resource Block, Resource Block

RBG: resource Block Group, Resource Block Group

RE: resource Element, Resource Element

RLC: radio Link Control, Radio Link Control protocol

RRC: radio Resource Control, Radio Resource Control

RV: redundancy Version of Reduncyny Version

SCell: secondary Cell, sub-Cell

SCG: secondary Cell Group, subcell Group

SCS: subcarrier Spacing, Subcarrier Spacing

SIB: system Information Block

SpCell: special Cell, Special Cell

And (3) SSB: SS/PBCH block, Sync Signal/physical broadcast channel Block

SSS: secondary Synchronization Signal, Secondary Synchronization Signal

S-GW: serving Gateway

SUL: supplement Uplink, supplement Uplink

TB: transport Block, Transport Block

TDD: time Division Duplexing

UE: user Equipment, User Equipment

UL: uplink, Uplink

UMTS: universal Mobile Telecommunications System, Universal Mobile communications System

UPF: user Plane Function

URLLC: ultra Reliable Low Latency Communication

And (3) USS: UE-specific Search Space, user-specific Search Space

VRB: virtual Resource Block, Virtual Resource Block

In all examples and embodiments of the invention, unless otherwise specified:

alternatively, the "starting RB" may also be referred to as the first RB, or the smallest RB, or the lowest RB, or the smallest numbered RB, or the lowest numbered RB.

Optionally, the "number" may be replaced by an "index".

Alternatively, the "index" may be replaced with a "number".

Alternatively, "CORESET 0" refers to CORESET for the type 0-PDCCH CSS set.

Alternatively, a "RedCap UE" may be a UE that supports RedCap functionality, and/or a UE that has RedCap functionality enabled, and/or a UE that has RedCap functionality configured.

Alternatively, a "non-RedCap UE" may be a UE that does not support RedCap functionality, and/or a UE that does not enable RedCap functionality, and/or a UE that is not configured with RedCap functionality.

Alternatively, VRB numbered x may also be referred to as VRB x.

Alternatively, PRB numbered y may also be referred to as PRB y.

Optionally, where applicable, "send" and "transmit" may be interchanged.

Alternatively, where applicable, a "symbol" (symbol) may refer to an OFDM symbol (OFDM symbol).

Optionally, any two of "within X", "in X", and "on X" may be interchanged where applicable (e.g., when an operation(s) is performed on a resource (s)). Where X may be one or more carriers, or one or more BWPs, or one or more resource pools (resource pools), or one or more links (e.g., UL, also like DL, also like SL), or one or more channels (e.g., PDCCH), or one or more subchannels, or one or more RBGs, or one or more RBs, or one or more "occasions" (e.g., PDCCH listening occasions, also like psch transmission occasions, also like psch reception occasions, also like psch transmission occasions, also like pscch reception occasions, again like pscch reception occasions, etc.), or one or more OFDM symbols, or one or more slots, or one or more subframes, or one or more half-frames, or one or more arbitrary time and/or frequency and/or code domain and/or spatial domain resources, etc.

Alternatively, "higher layer" may refer to one or more protocol layers or protocol sub-layers above the physical layer. E.g., the MAC layer, as well as the RLC layer, as well as the PDCP layer, as well as the RRC layer.

Optionally, "pre-provisioning" (pre-configuration) may be pre-provisioning in a higher layer protocol. Such as presetting (e.g., per specification of a higher layer protocol) at a particular memory location in the UE, or presetting (e.g., per specification of a higher layer protocol) at a particular memory location accessible by the UE.

Alternatively, "configuration" may be in a higher layer protocol through signaling. For example configured for the UE through RRC signaling.

Optionally, "configured" may be replaced with "preconfigured". And vice versa.

Optionally, "configured" may be replaced with "configured or preconfigured". And vice versa.

Alternatively, "a parameter has been configured" may be replaced with "a parameter has been provided". And vice versa.

Alternatively, "some information is indicated by a certain parameter" may be replaced with "some information is provided by a certain parameter". And vice versa.

Alternatively, "providing some information by some parameter" may be replaced with "configuring some information by some parameter". And vice versa.

Alternatively, "some parameter has been configured" may be replaced with "some parameter has been indicated by signaling". And vice versa.

Optionally, "unconfigured" may be replaced with "unconfigured". And vice versa.

Optionally, "unconfigured" may be replaced with "unconfigured and/or unconfigured". And vice versa.

Alternatively, "unconfigured" may be replaced with "unconfigured" (pre-) configured ". And vice versa.

Optionally, where applicable (e.g., where no ambiguity arises), the parameter X may refer to "X-r 8", or "X-r 9", or "X-r 10", or "X-r 11", or "X-r 12", or "X-r 13", or "X-r 14", or "X-r 15", or "X-r 16", or "X-r 17", etc. And vice versa. For example, "pdsch-HARQ-ACK-codebook" may be used to refer to the parameter pdsch-HARQ-ACK-codebook-r 16, where applicable. And vice versa.

Alternatively, a time-domain resource may also be referred to as a time (time) resource.

Alternatively, the frequency-domain resource may also be referred to as a frequency resource.

Alternatively, a Resource Block (RB) may refer to a Virtual Resource Block (VRB), a Physical Resource Block (PRB), a Common Resource Block (CRB), or a resource block defined in other manners.

Alternatively, the numbering of the frequency domain resources may start from 0. For example, a set of subcarriers in a resource block may be denoted as {0, 1.., 11} with the corresponding set of subcarrier numbers.

Alternatively, the numbering of the time domain resources may start from 0. For example, for 30kHz SCS, the set of slots in a subframe may be denoted as {0, 1} with the corresponding set of slot numbers.

New needs and/or use cases are continuously identified in the evolution of 5G technology, for example, in the process of industrial transformation and digitization, a large number of industrial sensors (such as pressure sensors, humidity sensors, etc.) and actuators need to be connected into a 5G network, some of which have no particularly strong requirements for reliability and latency, but it is desirable to have smaller device size and longer battery life on the basis of having wireless connection capability. This may be considered a type of requirement that is intermediate between LPWA and URLLC/eMBB. For another example, in the construction of a smart city, a large number of monitoring cameras are required, which puts certain demands on the rate of uplink data transmission (for example, a high-end monitoring device may need a data rate of 7.5 to 25 Mbps). As another example, the number of wearable devices (e.g., smartwatches, bracelets, etc.) has increased rapidly in recent years, again requiring smaller device sizes and longer battery life (e.g., one to two weeks), with peak rates of up to 50Mbps in the uplink and up to 150Mbps in the downlink.

The above requirements and/or use cases present new challenges to the complexity and/or device price of 5G UEs. To address these challenges, the 3GPP established redmap (reduced capability) work item (work item) is dedicated to reducing the complexity of 5G UEs in several aspects, such as reducing the maximum channel bandwidth (maximum channel bandwidth) of the UE, reducing the minimum number of receive branches (or minimum number of receive antenna ports), reducing the maximum number of downlink MIMO layers, introducing HD-FDD type a, etc.

For example, in terms of reducing the maximum channel bandwidth of UEs, the maximum channel bandwidth supported by a conventional 5G UE in FR1 is 100MHz, and the maximum channel bandwidth supported in FR2 is 200MHz (alternatively, the maximum bandwidth that some UEs can support is 400 MHz). In contrast, the maximum channel bandwidth supported by the red map UE at FRi is reduced to 20MHz, and the maximum channel bandwidth supported by FR2 is reduced to 100 MHz. The change of the red map UE over the maximum channel bandwidth brings new problems for BWP based operation in 5G.

5G supports the use of multiple sets of waveform parameters (numerology, referring to subcarrier spacing, or a combination of subcarrier spacing and cyclic prefix) in one serving cell, e.g., subcarrier spacing (SCS, which may be denoted by the symbol Δ f; corresponding "subcarrier spacing configuration", or "SCS configuration", which may be denoted by the symbol μ) and/or cyclic prefix listed in Table 1.

Table 15G supported waveform parameter sets

μ	Δf＝2^μ·15[kHz]	Cyclic prefix (Cyclic prefix, CP)
			0	15	Normal (Normal)
1	30	Is normal
			2	60	Normal, Extended (Extended)
3	120	Is normal and normal
			4	240	Is normal and normal

In 5G, in a given transmission direction (for example, denoted as x, where x ═ DL may represent downlink and x ═ UL may represent uplink) of a cell configured by the UE, one or more waveform parameter sets may be respectively defined with a resource grid (resource grid) whose lowest-numbered CRB (or called starting CRB or first CRB or minimum CRB or lowest CRB, for example, denoted as starting CRB or first CRB or minimum CRB) in the frequency domain

) Bandwidth (e.g., noted as

To represent

Number of RBs) may be indicated by a parameter carrierBandwidth, where each RB may contain

And (4) sub-carriers. In the time domain, one resource grid includes one subframe, and each subframe includes

One OFDM symbol (e.g. for normal CP,

). The center frequency of subcarrier 0 of CRB0 points to the same location in the frequency domain for all waveform parameter sets. This position is also called "point a".

Without causing ambiguity, the above

And/or

And/or

Etc. mu and/or x in the symbol may be removed.

One or more BWPs (bandwidth parts) may be configured in a given transmission direction in a cell configured by the UE, each BWP including one or more consecutive RBs. For example, at least one downlink BWP called "initial downlink BWP" is configured (e.g., configured by the parameter initialldownlinlnkbwp) in the downlink. In addition to the initial downstream BWP, one or more other downstream BWPs may be additionally configured downstream (e.g., configured via a BWP-Downlink IE). At the same time, only one downlink BWP, including the initial downlink BWP, is in an active state, which is called active downlink BWP.

In uplink, if a cell configured by the UE configures an uplink carrier (referred to as an "UL carrier" or a "non-SUL carrier"), at least one uplink BWP referred to as an "initial uplink BWP" is configured in the cell; if the cell configures two uplink carriers (respectively referred to as "non-UL carrier" and "SUL carrier"), the cell configures at least one uplink BWP called "initial uplink BWP" for the two uplink carriers (for example, configures through parameter initialuplink BWPs corresponding to the two uplink carriers, respectively). In addition to the initial upstream BWP, one or more other upstream BWPs may be additionally configured on the "non-SUL carrier" or "SUL carrier", respectively (e.g., configured via an information element BWP-Uplink). On the "non-SUL carrier", only one upstream BWP, including the initial upstream BWP, is active at the same time, called active upstream BWP. On the "SUL carrier" (if configured), only one upstream BWP, including the initial upstream BWP, is active at the same time, referred to as the active upstream BWP.

Each BWP may be configured with one or more of the following:

SCS (subcarrier spacing). For example as indicated by the parameter subanticriersspacing in the information element BWP.

CP (cyclic prefix). For example indicated by the parameter cyclicPrefix in the information element BWP.

Starting RB (or called first RB, or minimum RB, or lowest RB, or least numbered RB, or lowest numbered RB, e.g., its CRB number is noted

). For example,

wherein

(or as O)_carrier) CRB, RB, which is the lowest number of resource grid (or carrier) corresponding to SCS of BWP_startIt may be indicated by the parameter locationandwidth.

Bandwidth (alternatively referred to as "BWP Bandwidth", e.g. noted

). For example, in the case of a liquid,

wherein L is_RBMay be indicated by the parameter locationandbeamwidth.

ID (alternatively referred to as "BWP ID", e.g. noted

). Such as indicated by the parameter bwp-Id. The BWP ID of the initial upstream BWP or the initial downstream BWP has a value of 0, and the BWP IDs of the other BWPs are an integer greater than 0 (e.g., 1, as another example, 2, as another example, 3, as another example, 4).

The number (or index) of PRBs within a BWP is 0, 1, … …,

respectively correspond toCRB numbering

The VRBs within a BWP are numbered (or indexed) 0, 1, … …,

the frequency domain resources allocated for a physical signal or physical channel within the BWP may correspond to one or more VRBs that need to be mapped to PRBs when determining the physical resources actually occupied by the physical signal or physical channel. The mapping manner from VRBs to PRBs may be interleaving mapping (interleaved mapping) or non-interleaving mapping (non-interleaved mapping).

As previously described, the red map UE reduces the maximum channel bandwidth supported compared to other 5G UEs. This means that a reccap UE may not be able to operate in an initial downlink BWP or an initial uplink BWP in a cell when the bandwidth of such BWP is large. Therefore, the problem that the reccap UE needs to solve when accessing to a cell is how to determine its "initial downlink BWP" and "initial uplink BWP", and the resulting resource allocation related problem (e.g. mapping of VRBs to PRBs).

[ example one ]

A method performed by a user equipment according to a first embodiment of the present invention is described below with reference to fig. 1.

As shown in fig. 1, in a first embodiment of the present invention, a user equipment UE performs steps including: step S101 and step S103.

Specifically, in step S101, information related to the initial BWP is acquired and/or determined.

Alternatively, the "information on initial BWP" belongs to one cell (e.g., denoted as c). For example, the cell c is a primary cell (PCell). As another example, the Cell c is a Special Cell (Special Cell, e.g. PCell in MCG or PSCell in SCG in dual connectivity operation; and PCell in non-dual connectivity operation).

Optionally, part or all of the "information on initial BWP" is broadcast by the cell c.

Optionally, the "information related to initial BWP" contains information whether or not the recmap UE is allowed to camp on the cell c. For example, the "information whether the recmap UE is allowed to camp on the cell c" may be indicated in system information (e.g. MIB, also as SIB).

Optionally, the "information on initial BWP" includes information on whether the cell c has been barred. For example, the "information whether the cell c has been barred" may be indicated by a parameter cellBarred in the MIB (for example, a value "barred" indicates that the cell c has been barred, and a value "notBarred" indicates that the cell c has not been barred).

Optionally, the "information related to initial BWP" contains information of SSB (e.g., CD-SSB in the cell c). For example, the SSB information may include the starting RB of the SSB (e.g., noted as

). As another example, the SSB information may include the SSB bandwidth (e.g., noted as

For example

). Optionally, the information of the SSB is determined by one or more synchronization procedures, e.g. including a cell search procedure.

Optionally, the "information related to initial BWP" contains a first maximum transmission bandwidth configuration (e.g. noted as

To represent

One RB). Wherein, canOptionally, the first maximum transmission bandwidth configuration

May be a predefined value (e.g., a predefined value associated with a frequency range corresponding to a corresponding carrier and/or BWP). For example, for FR1,

a maximum transmission bandwidth configuration corresponding to a 20MHz channel bandwidth; specifically, for example, for 15kHz SCS,

as another example, for a 30kHz SCS,

as another example, for a 60kHz SCS,

as another example, for FR2,

may be a maximum transmission bandwidth configuration corresponding to a 100MHz channel bandwidth; specifically, for example, for a 60kHz SCS,

as another example, for a 120kHz SCS,

as another example, for FR2,

may be a maximum transmission bandwidth configuration corresponding to a 50MHz channel bandwidth; specifically, for example, for a 60kHz SCS,

as another example, for a 120kHz SCS,

optionally, the "information related to initial BWP" contains a first common subcarrier spacing (e.g. noted SCS)_cWith respective first common subcarrier spacing configured as mu_c). Optionally, the first common subcarrier spacing SCS_cMay be indicated by the parameter subanticriersspacincommon in the MIB.

Optionally, the "information related to the initial BWP" includes configuration information of CORESET 0 (alternatively referred to as CORESET #0, alternatively referred to as "CORESET with index 0").

Optionally, the SCS of CORESET0 is equal to the first common subcarrier spacing SCS_c。

Alternatively, one or more parameters of CORESET0 may be indicated by a parameter controlResourceSetZero in the parameter pdcch-ConfigSIBl in the MIB. For example, the value of the parameter controlResourceSetZero may be one of {0, 1.,. 15} for indicating information including one or more of the following:

SSB and CORESET0 multiplexing mode (alternatively referred to as "SSB and CORESET multiplexing mode"). For example, the "SSB and CORESET0 multiplexing mode" may be SSB and CORESET0 multiplexing mode 1, or SSB and CORESET0 multiplexing mode 2, or SSB and CORESET0 multiplexing mode 3.

Bandwidth of CORESET 0. E.g. expressed in RB numbers, e.g. as

Offset between CORESET0 and SSB (e.g., based on the first common subcarrier spacing SCS)_cDetermination, e.g. as

Represent

One RB). For example, in the case of a liquid,

wherein

Is based on the first common subcarrier spacing SCS_cAnd the first RB of the SSB (i.e., the

Corresponding RB) of the overlapping CRBs,

the CRB corresponding to the RB that is the smallest index of CORESET 0.

It may be a positive integer, or a negative integer, or 0. In the prior art are known

And

in this case, the CRB corresponding to the RB with the smallest index of CORESET0 may be determined as:

Optionally, the "information related to the initial BWP" includes configuration information of the first downlink BWP (e.g., note the corresponding starting RB as

Having a bandwidth of

)。

Alternatively, the first downlink BWP may be indicated by a parameter initialdown BWP (e.g. parameter initialdown BWP in downlinlingcomon of parameter servingCellConfigCommon in SIB 1). Optionally, the information element corresponding to the parameter initialldownlinkbwp is BWP-DownlinkCommon. For example,

and/or

May be indicated by a parameter locationiandBandwidth in said parameter initialDownlinkBWP.

Optionally, the first downstream BWP comprises the entire CORESET 0.

Optionally, the "information related to the initial BWP" includes configuration information of the second downlink BWP (e.g. note the corresponding starting RB as

A bandwidth of

Wherein, optionally,

)。

alternatively, the second downlink BWP may be indicated by a parameter initialdowenlinkbwp 2 (e.g. parameter initialdowenlinlinkbwp 2 in downlinligcommon of the parameter servingCellConfigCommon in SIB 1). Optionally, the information element corresponding to the parameter initialldownlinkbwp 2 is BWP-downlinlnkcommon. For example,

and/or

May be indicated by a parameter locationandwidth in said parameter initialldownlinkbwp 2.

Optionally, the second downstream BWP includes the entire CORESET 0.

Optionally, the second downlink BWP is configured only when the "information on whether to allow the redirection UE to camp on" indicates that the redirection UE is allowed to camp on the cell c.

Optionally, the "information on the initial BWP" contains information whether the non-redcp UEs are allowed to use the second downlink BWP. Wherein, optionally, the "information whether the non-red map UE is allowed to use the second downlink BWP" may be indicated by a parameter configured by a higher layer protocol.

Optionally, the "information related to the initial BWP" includes configuration information of the first upstream BWP (e.g. note the corresponding starting RB as

A bandwidth of

)。

Optionally, said first upstream BWP may be indicated by a parameter initializonbwp (e.g. parameter initializonbwp in uplinkconfigugcommon of the parameter servingCellConfigCommon in SIB 1). Optionally, the information element corresponding to the parameter initializuplinbwp is BWP-UplinkCommon. For example,

and/or

May be indicated by a parameter locationAndBandwidth in the parameter initialuplinbwp.

Optionally, for TDD, the first upstream BWP contains the entire CORESET 0.

Optionally, the configuration information of the first uplink BWP includes configuration information related to the PRACH. For example, the PRACH-related configuration information indicates M_{UL，BWP，0，1}(e.g., M)_{UL，BWP，0，1}1 as another example_{UL，BWP，0，1}2, also as M_{UL，BWP，0，1}4 as another example_{UL，BWP，0，1}8, e.g. indicated by the corresponding parameter msg 1-FDM) PRACH transmission occasions (PRACH transmission occasion), numbered 0, 1, … …, M in order from low to high in frequency_{UL，BWP，0，1}-1. PRACH Transmission opportunity 0 relative to the starting RB

Frequency offset (e.g. as

) May be indicated by a corresponding parameter msgl-FrequencyStart. The M is_{UL，BWP，0，1}The number of RBs occupied by each PRACH transmission opportunity in the frequency domain (e.g., SCS calculation based on the first uplink BWP, for example, is recorded as

) Is equal to

The number of SSBs (or SSB indices) associated with each PRACH transmission opportunity (e.g., denoted as

) And the number of contention-based PRACH preambles associated with each SSB and each PRACH transmission opportunity (e.g., denoted as

) May be indicated by a corresponding parameter SSB-perRACH-occupancy and cb-preambl perssb, and accordingly, the number of contention-based PRACH preambles (e.g., denoted as contention-based PRACH preambles) associated with each SSB

) Can be equal to

Optionally, the "information related to the initial BWP" includes configuration information of the second uplink BWP (e.g. note the corresponding start RB as

A bandwidth of

)。

Optionally, the second upstream BWP mayAs indicated by the parameter initialuplink bwp2 (e.g. parameter initialuplink bwp2 in uplinkConfigCommon of the parameter servingCellConfigCommon in SIB 1). Optionally, the information element corresponding to the parameter initialinkbwp 2 is BWP-UplinkCommon. For example, in the case of a liquid,

and/or

May be indicated by a parameter locationandwidth in said parameter initialuplinks bwp 2.

Optionally, for TDD, the second upstream BWP contains the entire CORESET 0.

Optionally, the configuration information of the second uplink BWP includes configuration information related to a PRACH. For example, the PRACH-related configuration information indicates M_{UL，BWP，0，2}(e.g., M)_{UL，BWP，0，2}1 as another example_{UL，BWP，0，2}2 as another example_{UL，BWP，0，2}4 as another example_{UL，BWP，0，2}8, e.g. indicated by a corresponding parameter msgl-FDM) PRACH transmission occasions, numbered 0, 1, … …, M in order from low to high in frequency_{UL，BWP，0，2}-1. PRACH Transmission opportunity 0 relative to the starting RB

Frequency offset (e.g. as

) May be indicated by a corresponding parameter msgl-FrequencyStart. Said M_{UL，BWP，0，2}The number of RBs occupied by each PRACH transmission opportunity in the frequency domain (e.g., SCS calculation based on the second uplink BWP, for example, is recorded as

) Is equal to

SSB (or so-called SSB) associated with each PRACH transmission opportunity SSB index) number (e.g., noted as

) May be indicated by a corresponding parameter SSB-perRACH-OccasionAndCB-preamble SSB, and accordingly, the number of contention-based PRACH preambles associated with each SSB (e.g., denoted as contention-based PRACH preamble number)

) Can be equal to

Optionally, the second uplink BWP is configured only when the "information on whether to allow the rectap UE to camp on" indicates that the rectap UE is allowed to camp on the cell c.

Optionally, the "information on the initial BWP" contains information whether the non-redcp UEs are allowed to use the second uplink BWP. Wherein, optionally, the "information whether the non-red map UE is allowed to use the second uplink BWP" may be indicated by a parameter configured by a higher layer protocol.

Further, in step S103, an initial downlink BWP is determined (e.g., the corresponding start RB is written as

A bandwidth of

) And/or initial upstream BWP (e.g., noting the corresponding starting RB as

A bandwidth of

)。

Optionally, one or more parameters of the initial downlink BWP are determined before one or more parameters of the initial uplink BWP are determined. For example, for TDD, in determining

Then, will

Is determined as

As another example, for FDD, in determining

Then, will

Is determined as

Wherein

Is a predefined constant or a value configured by higher layer protocols. As another example, for TDD and/or FDD, in determining

Then, will

Is determined as

Optionally, one or more parameters of the initial uplink BWP are determined before one or more parameters of the initial downlink BWP are determined. For example, for TDD, in determining

Then, will

Is determined as

As another example, for TDD, in determining

Then, will

Is determined as

As another example, for TDD and/or FDD, in determining

Then, will

Is determined as

Optionally, if the first downlink BWP condition is satisfied, a first downlink BWP operation is performed to determine one or more parameters of the initial downlink BWP.

Optionally, the first downlink BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a "non-RedCap UE".

The first downlink BWP is unconfigured.

Optionally, the first downlink BWP operation comprises one or more of:

will be

Is determined as

Will be

Is determined as

Optionally, if a second downlink BWP condition is satisfied, a second downlink BWP operation is performed to determine one or more parameters of the initial downlink BWP.

Optionally, the second downlink BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a "non-RedCap UE".

The first downlink BWP is configured.

Optionally, the second downlink BWP operation comprises one or more of:

will be

Is determined as

Will be

Is determined as

Optionally, if a third downlink BWP condition is satisfied, a third downlink BWP operation is performed to determine one or more parameters of the initial downlink BWP.

Optionally, the third downlink BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a RedCap UE.

The "information whether or not to allow the rectap UE to camp on" indicates that the rectap UE is allowed to camp on the cell c.

The cell c is not barred.

The first downlink BWP is unconfigured.

The first downlink BWP is configured.

The second downlink BWP is configured.

Optionally, the third downlink BWP operation comprises one or more of:

will be

Is determined as

Will be

Is determined as

Optionally, if a fourth downlink BWP condition is satisfied, a fourth downlink BWP operation is performed to determine one or more parameters of the initial downlink BWP.

Optionally, the fourth downlink BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a RedCap UE.

The cell c is not barred.

The first downlink BWP is unconfigured.

The second downlink BWP is not configured.

Optionally, the fourth downlink BWP operation comprises one or more of:

will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

If

Then will be

Is determined as inOne item is as follows:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

If

Then will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

If

(or, if

Or, if

) Then will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

Will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

if

Then will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

if

Then will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

if

(or, if

Or, if

) Then will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

optionally, if a fifth downlink BWP condition is satisfied, a fifth downlink BWP operation is performed to determine one or more parameters of the initial downlink BWP.

Optionally, the fifth downlink BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a RedCapeUE.

The cell c is not barred.

The first downlink BWP is configured.

The second downlink BWP is not configured.

Optionally, the fifth downlink BWP operation comprises one or more of:

will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

If

Then will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

If

Then will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

If

(or, if

Or, if

) Then will be

Is determined as one of the following:

◆

(e.g., for TDD)

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

Will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

if

Then will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

if

Then will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

if

(or, if

Or, if

) Then will be

Is determined as one of the following:

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

◆

optionally, determining

And/or

The order of (a) may be: first, determine

Re-determination

(for example,

depend on

) (ii) a Or first determining

Re-determination

(for example,

depend on

) (ii) a Or, independently determine

And

(for example,

and

not dependent on each other).

Optionally, determining

And/or

The manner of (2) is frequency range dependent. For example for FR1 and FR2, determination

The way of (2) is different; as another example for FR1 and FR2, determination

In a different manner.

Optionally, determining

And/or

The manner of (c) is related to the duplex mode. For example, for TDD and FDD, the determination

The way of (2) is different; as another example, for TDD and FDD, the determination

In a different manner.

Optionally, determining

And/or

The mode of (1) is related to the "SSB and CORESET 0 multiplexing mode". For example, for two or more of SSB and CORESET 0 multiplexing mode 1, SSB and CORESET 0 multiplexing mode 2, SSB and CORESET 0 multiplexing mode 3, a determination is made

The way of (2) is different; as another example, for two or more of SSB and CORESET 0 multiplexing mode 1, SSB and CORESET 0 multiplexing mode 2, SSB and CORESET 0 multiplexing mode 3, a determination is made

In a different manner.

Optionally, if a first upstream BWP condition is satisfied, a first upstream BWP operation is performed to determine one or more parameters of the initial upstream BWP.

Optionally, the first upstream BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

The UE is a "non-RedCap UE".

The first upstream BWP is configured. (optionally, the first uplink BWP is always configured in cell c, i.e., "the first uplink BWP is configured" always holds.)

The second upstream BWP is unconfigured.

Optionally, the first upstream BWP operation comprises one or more of:

will be

Is determined as

Will be

Is determined as

Optionally, if a second upstream BWP condition is satisfied, a second upstream BWP operation is performed to determine one or more parameters of the initial upstream BWP.

Optionally, the second upstream BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a "non-RedCap UE".

The "information whether or not a recmap UE is allowed to camp" indicates that a recmap UE is allowed to camp on the cell c.

The second upstream BWP is configured.

The "information whether the non-RedCap UE is allowed to use the second upstream BWP" indicates that the non-RedCap UE is not allowed to use the second upstream BWP.

Optionally, the second upstream BWP operation comprises one or more of:

will be

Is determined as

Will be

Is determined as

Optionally, if a third upstream BWP condition is satisfied, a third upstream BWP operation is performed to determine one or more parameters of the initial upstream BWP.

Optionally, the third upstream BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a "non-RedCap UE".

The second upstream BWP is configured.

The "information whether the non-RedCap UE is allowed to use the second upstream BWP" indicates that the non-RedCap UE is allowed to use the second upstream BWP.

Optionally, the third upstream BWP operation comprises one or more of:

by probability

Will be provided with

Is determined as

By probability

Will be provided with

Is determined as

By probability

Will be provided with

Is determined as

According to probability

Will be provided with

Is determined as

By probability

Will be provided with

Is determined as

By probability

Will be provided with

Is determined as

By probability

Will be provided with

Is determined as

By probability

Will be provided with

Is determined as

Wherein,

may be a predefined value (e.g. a

) Or indicated by a parameter configured by a higher layer protocol, or equal to

Or is equal to

Or determined by the UE in a manner implemented by the UE; wherein r is₁Is equal to

(or

Or

Or

Or alternatively

Or

Or

Or alternatively

Or

Or the number of PRACH time and/or frequency domain resources in the first uplink BWP calculated in other ways), r)₂Is equal to

(or M_{UL，BWP，0，2}Or is or

Or

Or

Or

Or alternatively

Or

Or

Or the number of PRACH time domain and/or frequency domain resources in the second uplink BWP calculated in other manners).

Optionally, if a fourth upstream BWP condition is satisfied, a fourth upstream BWP operation is performed to determine one or more parameters of the initial upstream BWP.

Optionally, the fourth upstream BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a RedCapeUE.

The second upstream BWP is unconfigured.

The cell c is not barred.

Optionally, the fourth upstream BWP operation comprises one or more of:

will be

Is determined as

(e.g., for TDD)

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Optionally, if a fifth upstream BWP condition is satisfied, a fifth upstream BWP operation is performed to determine one or more parameters of the initial upstream BWP.

Optionally, the fifth upstream BWP condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a RedCap UE.

The second upstream BWP is configured.

The cell c is not barred.

Optionally, the fifth upstream BWP operation comprises one or more of:

will be

Is determined as

(e.g., for TDD)

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Will be

Is determined as

Optionally, determining

And/or

The order of (a) may be: first, determine

Re-determination

(for example,

depend on

) (ii) a Or to determine first

Re-determination

(for example,

depend on

) (ii) a Or, independently determine

And

(for example,

and

not dependent on each other).

Optionally, determining

And/or

The way of (2) is different; as another example for FR1 and FR2, determination

In a different manner.

Optionally, determining

And/or

The manner of (2) is related to the duplex mode. For example, for TDD and FDD, the determination

In a different manner.

Optionally, in the first embodiment of the present invention, the cell c may also be referred to as a "serving cell".

Alternatively, in the first embodiment of the present invention, the "for FR 1" may mean that the corresponding carrier frequency is on one band (band) of FR 1.

Alternatively, in the first embodiment of the present invention, the "for FR 2" may mean that the corresponding carrier frequency is on one frequency band of FR 2.

Optionally, in the first embodiment of the present invention, the "PRACH transmission occasion" may also be referred to as "RACH transmission occasion", or "PRACH occasion", or "RACH occasion". Optionally, one "PRACH transmission occasion" corresponds to one or more OFDM symbols in the time domain (e.g., the one or more OFDM symbols are referred to as constituting one PRACH time instance). At a given PRACH time instance, there may be one or more PRACH transmission occasions in the frequency domain.

Alternatively, in the first embodiment of the present invention,

is the number of RBs occupied by one PRACH transmission opportunity in the frequency domain.

May be a predefined constant related to the PRACH preamble length and/or the PRACH subcarrier spacing and/or the subcarrier spacing of the corresponding uplink BWP.

May be based on SCS of the corresponding uplink BWP, when the bandwidth of one PRACH transmission occasion in the frequency domain is equivalent to the PUSCH occupancy in the corresponding uplink BWP

Bandwidth per RB.

Alternatively, in the first embodiment of the present invention,

may be determined from one or more of the following:

·

·

if

(or, if

Or, if

Then

If

(or, if

Or, if

) Then, then

If

Then

If

Then

If

Then the

If

Then

If

Then

If

Then

Alternatively, in the first embodiment of the present invention,

may be determined from one or more of the following:

·

·

·

if

Then

If

Then

If

(or, if

Or, if

) Then, then

Thus, according to the first embodiment, the present invention provides a method for improving resource utilization efficiency of a red map UE and a non-red map UE at the time of initial access by determining an initial downlink BWP (or an initial uplink BWP) of the red map UE within a conventional initial downlink BWP (or an initial uplink BWP).

[ example two ]

The method performed by the user equipment according to the second embodiment of the present invention is described below with reference to fig. 2.

As shown in fig. 2, in the second embodiment of the present invention, the steps performed by the user equipment UE include: step S201 and step S203.

Specifically, in step S201, scheduling information related to one PUSCH transmission is acquired and/or determined.

Optionally, the PUSCH transmission is one PUSCH transmission within active uplink BWP. For example, the number of the active upstream BWP is denoted as i, and the corresponding starting RB (e.g., indicated by CRB number) is denoted as

Accordingly, the starting RB (e.g., indicated by CRB number) for the initial upstream BWP is

Wherein, optionally, the initial uplink BWP of the red map UE and the non-red map UE may be the same or different; optionally, the initial uplink BWP of the red map UE and/or the non-red map UE is determined according to the steps in the first embodiment of the present invention.

Optionally, the scheduling information may include frequency domain resource allocation information. For example, the frequency domain resource allocation information may be indicated by a "PUSCH frequency resource allocation" (PUSCH frequency resource allocation) field in the RAR uplink grant; as another example, the Frequency domain resource allocation information may be indicated by a "Frequency domain resource allocation" field in DCI format 0_ 0. Optionally, the corresponding frequency resource allocation manner is "uplink resource allocation type 1" (uplink resource allocation type 1). Optionally, a Resource Indication Value (RIV) in the frequency domain resource allocation information indicates a starting VRB (for example, denoted as RB)_start) One or more of the first (e.g. noted as L)_RBsAnd) consecutive VRBs (or simply RBs).

Further, in step S203, one or more PRBs for the PUSCH transmission are determined.

Optionally, converting said L_RBs VRBs are mapped to PRBs.

Optionally, the mapping from VRBs to PRBs is a non-interleaved mapping.

Optionally, if the first VRB-to-PRB mapping condition is satisfied, performing a first VRB-to-PRB mapping operation.

Optionally, the first VRB-to-PRB mapping condition may comprise one or more of the following (in any combination of and or, where applicable):

the UE is a non-RedCap UE.

The scheduling information is indicated by a RAR uplink grant (RAR UL grant).

The scheduling information is indicated by DCI format 0_ 0; wherein the CRC of the DCI format 0_0 is scrambled by TC-RNTI.

The active upstream BWP contains all RBs of the initial upstream BWP.

The SCS of the active upstream BWP is the same as the SCS of the initial upstream BWP.

The CP of the active upstream BWP is the same as the CP of the initial upstream BWP.

Optionally, the first VRB-to-PRB mapping operation may be to map the VRB numbered n to the VRB numbered n

The PRB of (1).

Optionally, if a second VRB-to-PRB mapping condition is satisfied, performing a second VRB-to-PRB mapping operation.

Optionally, the second VRB-to-PRB mapping condition may comprise one or more of the following (in any combination of and or, where applicable):

The UE is a RedCap UE.

The scheduling information is indicated by a RAR uplink grant (RAR UL grant).

The active upstream BWP contains all RBs of the initial upstream BWP.

The CP of the active upgoing BWP is the same as the CP of the initial upgoing BWP.

Optionally, the second VRB-to-PRB mapping operation may be to map the VRB numbered n to the VRB numbered n

The PRB of (1).

Optionally, if a third VRB-to-PRB mapping condition is satisfied, performing a third VRB-to-PRB mapping operation.

Optionally, the third VRB-to-PRB mapping condition may comprise one or more of the following (in any combination of and or, where applicable):

the first VRB-to-PRB mapping condition is not satisfied.

The second VRB-to-PRB mapping condition is not satisfied.

Alternatively, the second VRB-to-PRB mapping operation may be to map the VRB numbered n to the PRB numbered n.

Thus, according to the second embodiment, the present invention provides a method, when transmitting the initial transmission or retransmission of the PUSCH scheduled by the RAR uplink grant, for the red map UE, using a different VRB-to-PRB mapping manner than for the non-red map UE, so that the resource allocation starting point of the red map UE can be compatible with the non-red map UE, thereby improving the multiplexing capability of the RAR uplink grant, and further improving the efficiency of resource allocation and utilization.

[ 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. 3.

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

As shown in fig. 3, the user equipment UE30 includes a processor 301 and a memory 302. The processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 302 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 302 has stored thereon program instructions. Which when executed by the processor 301 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, for example modules that may be developed or that may be developed in the future, available for a base station, AMF, UPF, MME, S-GW or UE, etc. The various designations shown above are exemplary only and not The invention is not limited to the specific cells as examples of these identities. Many variations and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments. It will be understood by those skilled in the art that some or all of the mathematical expressions or mathematical equations or mathematical inequalities may be simplified or transformed or rewritten to some extent, such as by combining constant terms, exchanging two additive terms, exchanging two multiplicative terms, shifting a term from the left to the right of an equation or inequality after changing the sign, shifting a term from the right to the left of an equation or inequality after changing the sign, and so on; a mathematical expression or a mathematical equation or a mathematical inequality before and after simplification or transformation or rewriting may be regarded as equivalent. It will be understood by those skilled in the art that a subset of a set may be the set itself, e.g., a ═ a₁，a₂The subset of { a } may be₁，a₂}, or { a }₁Either a or a₂Either an empty set.

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 the present invention, a "base station" may refer to a mobile communication data and/or control switching center having a certain transmission power and a certain coverage area, and for example, includes functions of resource allocation scheduling, data receiving and sending, 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 on a computer readable medium such as an optical medium (e.g., CD-ROM), floppy or hard disk or other data structures or other media 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, but in the alternative, the processor may be any conventional 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

1. A method performed by a user equipment, UE, comprising:

obtaining downlink BWP configuration information, and

determining one or more parameters of an initial downlink BWP, including

Bandwidth of the initial downlink BWP

Is determined as

And

starting resource block of the initial downlink BWP

Is determined as

Wherein,

and

is a predefined maximum transmission bandwidth configuration,

is the bandwidth configured in the downlink BWP configuration information.

2. A method performed by a user equipment, UE,

obtaining configuration information of a first upstream BWP and a second upstream BWP, an

One or more parameters of the initial upstream BWP are determined. Wherein,

determining the bandwidth of the initial upstream BWP as the bandwidth configured in the first upstream BWP according to a probability p, and determining the bandwidth of the initial upstream BWP as the bandwidth configured in the second upstream BWP according to a probability 1-p; and

and determining the initial resource block of the initial uplink BWP as the initial resource block configured in the first uplink BWP according to the probability p, and determining the initial resource block of the initial uplink BWP as the initial resource block configured in the second uplink BWP according to the probability 1-p.

Wherein,

the probability p is equal to

Wherein r is₁And r₂The number of PRACH resources configured in the first uplink BWP and the second uplink BWP, respectively.

3. 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-2.