WO2021098570A1 - Procédé de détermination d'occasion de prach et dispositif terminal, dispositif de réseau - Google Patents
Procédé de détermination d'occasion de prach et dispositif terminal, dispositif de réseau Download PDFInfo
- Publication number
- WO2021098570A1 WO2021098570A1 PCT/CN2020/128150 CN2020128150W WO2021098570A1 WO 2021098570 A1 WO2021098570 A1 WO 2021098570A1 CN 2020128150 W CN2020128150 W CN 2020128150W WO 2021098570 A1 WO2021098570 A1 WO 2021098570A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- rmsi
- ssb
- target
- time domain
- domain unit
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0833—Random access procedures, e.g. with 4-step access
Definitions
- the embodiments of the present disclosure relate to the field of communication technologies, and particularly, to a method for determining a Physical Random Access Channel (PRACH) occasion and a terminal device, network device.
- PRACH Physical Random Access Channel
- the base station will configure a set of physical random access channel (PRACH) occassions for a terminal device. Furthermore, the protocol regulates a series of rules to determine which PRACH occassions are valid and which PRACH occassion are invalid in the set of PRACH occassions. The terminal device can only use the valid PRACH occassions (referred to as valid PRACH occassions) for random access.
- PRACH physical random access channel
- the terminal device can not obtain the uplink and downlink resource configuration before a random access process, which will lead to the terminal device unable to distinguish which PRACH occassions are valid and which PRACH occassions are invalid.
- the embodiments of the present disclosure provide a method for determining a PRACH occasion and a terminal device, network device.
- the method for determining a PRACH occasion includes:
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- the method for determining a PRACH occasion includes:
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- the device for determining Physical Random Access Channel (PRACH) occasion provided in the embodiments of the present disclosure is applied to a terminal device and includes:
- a determination unit configured to determine a PRACH occasion overlapped with a target time domain unit as an invalid PRACH occasion, the invalid PRACH occasion being not used for random access, wherein
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- the device for determining Physical Random Access Channel (PRACH) occasion provided in the embodiments of the present disclosure is applied to a network device and includes:
- a determination unit configured to determine a PRACH occasion overlapped with a target time domain unit as an invalid PRACH occasion, the invalid PRACH occasion being not used for random access, wherein
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- a terminal device provied in the embodiments of the present disclosure includes a memory for storing a computer program, and a processor for calling and running the computer program stored in the memory to perform the method for determining a PRACH occassion as described above.
- a network device provied in the embodiments of the present disclosure includes a memory for storing a computer program, and a processor for calling and running the computer program stored in the memory to perform the method for determining a PRACH occassion as described above.
- a chip provided in the embodiments of the present disclosure is used for implementing the method for determining a PRACH occassion as described above.
- the chip includes a processor configured to call a computer program from a memory and run the program to cause a device equipped with the chip to perform the method for determining a PRACH occasson as described above.
- a computer-readable storage medium provided in the the embodiments of the present disclosure has stored thereon a computer program causing a computer to perform the method for determining a PRACH occasion as described above.
- a computer program product provided in the the embodiments of the present disclosure has stored thereon a computer program causing a computer to perform the method for determining a PRACH occasion as described above.
- a computer program provided in the the embodiments of the present disclosure causes a computer to perform the method for determining a PRACH occasion as described above when executed in the computer.
- the PRACH occasion in a collision with a time domain unit where RMSI is located is determined as an invalid PRACH occasion, such that the problem of possible resource collision between RMSI and PRACH occassion in the unlicensed frequency band can be solved, so as to effectively ensure that a network device and terminal device have the same understanding of the valid PRACH occasion, and guarantee the random access message transmitted between a terminal device and network device can be effectively received and avoid ineffective transmission of random access message.
- FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present disclosure.
- FIG. 2 is a schematic flow chart of a method for determining a PRACH occassion provided by an embodiment of the present disclosure
- FIG. 3A is a first schematic diagram of a candidate SSB and RMSI associated with a target SSB provided by an embodiment of the present disclosure
- FIG. 3B is a first schematic diagram of an invalid PRACH occasion provided by an embodiment of the present disclosure.
- FIG. 4A is a second schematic diagram of a candidate SSB and RMSI associated with a target SSB provided by an embodiment of the present disclosure
- FIG. 4B is a second schematic diagram of an invalid PRACH occasion provided by an embodiment of the present disclosure.
- FIG. 5A is a third schematic diagram of a candidate SSB and RMSI associated with a target SSB provided by an embodiment of the present disclosure
- FIG. 5B is a third schematic diagram of an invalid PRACH occasion provided by an embodiment of the present disclosure.
- FIG. 6A is a fourth schematic diagram of a candidate SSB and RMSI associated with a target SSB provided by an embodiment of the present disclosure
- FIG. 6B is a fourth schematic diagram of the invalid PRACH occasion provided by an embodiment of the present disclosure.
- FIG. 7A is a first diagram of time domain locations of RMSI PDCCH and RMSI PDSCH provided by an embodiment of the present disclosure
- FIG. 7B is a second diagram of time domain locations of RMSI PDCCH and RMSI PDSCH provided by an embodiment of the present disclosure
- FIG. 7C is a third diagram of time domain locations of RMSI PDCCH and RMSI PDSCH provided by an embodiment of the present disclosure
- FIG. 7D is a fourth diagram of time domain locations of RMSI PDCCH and RMSI PDSCH provided by an embodiment of the present disclosure.
- FIG. 8 is a first structual diagram of a device for determining a PRACH occassion provided by an embodiment of the present disclosure
- FIG. 9 is a second structual diagram of a device for determining a PRACH occassion provided by an embodiment of the present disclosure.
- FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure.
- FIG. 11 is a schematic structure diagram of a chip in an embodiment of the present disclosure.
- FIG. 12 is a schematic block diagram of a communication system provided by an embodiment of the present disclosure.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- FDD frequency division duplex
- TDD Time division duplex
- UMTS Universal Mobile Telecommunication System
- WiMAX Worldwide Interoperability for Microwave Access
- 5G 5th generation
- the communication system 100 may include a network device 110, which may be a device communicating with a terminal device 120 (also referred to as a communication terminal, terminal) .
- the network device 110 may provide communication coverage for a specific geographic area and may communicate with a terminal located within the coverage area.
- the network device 110 may be a bse transceiver station (BTS) in a GSM system or CDMA system, or may be a NodeB (NB) in a WCDMA system, or may be an Evolutional base station (Evolutional Node B, eNB or eNodeB) or a wireless controller in network in a cloud radio access network (CRAN) in an LTE system, or the network device can be mobile switching center, relay station, access point, on-board equipment, wearable equipment, hub, switch, bridge, router, network-side device in 5G network or network device in a future evolved Public Land Mobile Network (PLMN) , etc.
- BTS bse transceiver station
- NB NodeB
- Evolutional Node B Evolutional Node B
- eNB or eNodeB Evolutional Node B
- CRAN cloud radio access network
- PLMN Public Land Mobile Network
- the communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110.
- the "terminal device” used herein includes but is not limited to the connection via wired lines, such as public switched telephone networks (PSTN) and digital subscriber lines Line, DSL, digital cable, direct cable connection; and/or another data connection/network; and/or via wireless interface, such as for cellular network, wireless local area network (WLAN) , such as DVB-H Digital television network, satellite network, AM-FM broadcast transmitter of the network; and/or device set to receive/send communication signals of another terminal device; and/or Internet of things (IOT) device.
- wired lines such as public switched telephone networks (PSTN) and digital subscriber lines Line, DSL, digital cable, direct cable connection; and/or another data connection/network
- wireless interface such as for cellular network, wireless local area network (WLAN) , such as DVB-H Digital television network, satellite network, AM-FM broadcast transmitter of the network; and/or device set to receive/send communication signals
- a terminal device set to communicate via a wireless interface may be referred to as a "wireless communication terminal” , “wireless terminal” or “mobile terminal” .
- mobile terminals include, but are not limited to, satellites or cellular phones; personal communications systems that can combine cellular radiotelephony with data processing, fax, and data communication capabilities System (PCS) terminals; PDAs that may include radiophones, pagers, Internet/intranet access, web browsers, notebooks, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or handheld receivers or other electronic devices including radiophone transceivers.
- PCS data communication capabilities System
- GPS Global Positioning System
- a terminal device can refer to access terminal, user equipment (UE) , user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
- Access terminals can be cellular telephone, cordless telephone, session initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital processing (PDP) Assistant, PDA) , handheld device with wireless communication function, computing device or other processing device connected to wireless modem, on-board device, wearable device, terminal device in 5G network or terminal device in PLMN evolving in the future.
- SIP session initiation protocol
- WLL wireless local loop
- PDA personal digital processing
- the terminal devices 120 may perform communications on Device-to-Device (D2D) direct connection.
- D2D Device-to-Device
- a 5G system or 5G network may also be referred to as New Radio (NR) system or NR system.
- NR New Radio
- FIG. 1 illustrates an example of a network device and two terminal devices.
- the communication system 100 may include a plurality of network devices and there may be other numbers of terminal devices within the coverage of each network device, which is not limited by the embodiments of the present disclosure.
- the communication system 100 may also include other network entities such as a network controller, a mobile management entity, etc., which are not limited by the embodiments of the present disclosure.
- the communication device may include the network device 110 and the terminal devices 120 with the communication function.
- the network device 110 and the terminal devices 120 may be the specific devices as described above, which will not be described here in detail.
- the communication device may also include other devices in the communication system 100, such as the network controller, the mobile management entity and other network entities, which are not limited in the embodiment of the present disclosure.
- gNB could configure a set of PRACH occasions for a terminal device.
- the set of PRACH occasions are present periodically.
- the protocol regulates a series of rules to determine which PRACH occasions are valid and which PRACH occasions are invalid among the above-mentioned set of PRACH occasions.
- PRACH resources on a downlink symbol should not be considered as valid PRACH resources and is scheduled for transmitting physical downlink shared channel (PDSCH)
- PDSCH physical downlink shared channel
- PUSCH physical uplink shared channel
- the PRACH resources refer to PRACH occasions.
- a UE is provided a number N of SS/PBCH blocks associated with one PRACH occasion and a number R of contention based preambles per SS/PBCH block per valid PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB. If N ⁇ 1, one SS/PBCH block is mapped to 1/N consecutive valid PRACH occasions and R contention based preambles with consecutive indexes associated with the SS/PBCH block per valid PRACH occasion start from preamble index 0.
- R contention based preambles with consecutive indexes associated with SS/PBCH block n, 0 ⁇ n ⁇ N-1, per valid PRACH occasion start from preamble index where is provided by totalNumberOfRA-Preambles and is an integer multiple of N. ”
- a UE determines from MIB that a CORESET for Type0-PDCCH CSS set is present, as described in 3GPP specification 38.213 Subclause 4.1, the UE determines a number of consecutive resource blocks and a number of consecutive symbols for the CORESET of the Type0-PDCCH CSS set from the four most significant bits of pdcch-ConfigSIB1, as described in Tables 13-1 through 13-10, and determines PDCCH monitoring occasions from the four least significant bits of pdcch-ConfigSIB1, included in MIB, as described in 3GPP specification 38.213 Tables 13-11 through 13-15.
- each SSB will be associated with one RMSI.
- CORESET of the Type0-PDCCH CSS and PDCCH monitoring occasions will be used for RMSI PDCCH reception.
- LBT Listen Before Talk
- RMSI should be transmitted on the downlink symbol.
- the terminal device can obtain downlink configuration and PRACH related configuration before initiating random access process. Therefore, the terminal device can calculate which PRACH occasion is valid based on these downlink configurations and PRACH related configurations.
- the terminal device can not obtain the uplink and downlink resource allocation before the random access process. How to identify the valid PRACH occasion to deal with the resource conflict between RMSI and PRACH occasions will be a problem to be solved.
- FIG. 2 illustrates a schematic flow chart of a method 200 for determining a PRACH occasion according to an embodiment of the present disclosure. As illustrated in FIG. 2, the method includes the following operations.
- a terminal device determines a PRACH occasion overlapped with a target time domain unit as an invalid PRACH occasion, and the invalid PRACH occasion is not used for random access.
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- the method 200 may be performed by a terminal device, for example, the terminal device may be a terminal device as illustrated in FIG. 1; or the method 200 may be performed by a network device, for example, the network device may be a network device as illustrated in FIG. 1.
- the method 200 executed by the terminal device is described as an example, but it is also applicable to the network device implementation, and will not be elaborated here.
- the terminal device determines a PRACH occassion of the set of PRACH occasions that overlaps with the target time domain unit as an invalid PRACH occasion.
- the method 200 may further include: obtaining, by the terminal device a set of PRACH occasions.
- the terminal device can receive a set of PRACH occasions configured by the network device, that is, the set of PRACH occasions in the embodiment of the present disclosure.
- the PRACH occasions in the set of PRACH occasions can be used for the random access process, and the set of PRACH occasions can include at least one PRACH occasion.
- the PRACH occasions in the set of PRACH occasions in the embodiment of the present disclosure may include the PRACH occasion on the unlicensed frequency band, and the terminal device and network device can determine which PRACH occasion is valid and which PRACH occasion is invalid in the set of PRACH occasions.
- the invalid PRACH occasion (referred to as invalid PRACH occasion) cannot be used for random access
- the valid PRACH occasion (referred to as valid PRACH occasion) can be used for random access.
- the method 200 may further include that the terminal device determines the PRACH occasion (i.e., the valid PRACH occasion) for random access in the sef of PRACH occasions except the invalid PRACH occasions. In other words, the terminal device will not use invalid PRACH occasions for random access.
- the implementations of a target time domain unit have the following manners.
- the target time domain unit is a slot where RMSI is located.
- the slot has a first PDSCH and/or a first physical downlink control channel (PDCCH) , the first PDSCH is used to carry RMSI, and the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- PDCH physical downlink control channel
- the PRACH occasion if a PRACH occasion overlaps with the slot containing RMSI (which can be full overlap or partial overlap) , the PRACH occasion is invalid.
- the invalid PRACH occasion is not used for the transmission of preamble, and the invalid PRACH occasion is not used for mapping between SS/PBCH blocks and valid PRACH occasions.
- the slot containing RMSI refers to the slot containing RMSI PDCCH and/or RMSI PDSCH, wherein RMSI PDCCH is the first PDCCH in the above scheme, and RMSI PDSCH is the first PDSCH in the above scheme.
- RMSI is the RMSI associated with the actual transmitted SS/PBCH block or QCLed SS/PBCH block.
- each candidate SSB location has a candidate SSB index.
- the candidate SSB indexes corresponding to the 20 candidate SSB positions are 0, 1, ..., 19.
- There is a factor Q associated with QCL, for example, Q 8.
- the SSB with candidate SSB index i+n*Q is quasi addressable (QCled) .
- the SSB can be sent at the SSB candidate location with i+n*Q candidate SSB index.
- the slot also include the target SSB, and the target SSB is associated with the RMSI. That is, the slot has a target SSB and at least one of the first PDSCH and the first PDCCH.
- the slot containing RMSI can also be understood as the slot containing the target SSB. Based on this, if the PRACH occasion overlaps with the slot containing the target SSB (which can be full overlap or partial overlap) , the PRACH occasion is invalid. The invalid PRACH occasion is not used for the transmission of preamble, and the invalid PRACH occasion is not used for mapping between SS/PBCH blocks and valid PRACH occasions.
- the target SSB may refer to the actual transmitted SS/PBCH block or QCled SS/PBCH block.
- QCled SS/PBCH block refers to the SS/PBCH block with quasi co-location with the actual transmitted SS/PBCH block.
- each candidate SSB location has a candidate SSB index.
- the candidate SSB indexes corresponding to the 20 candidate SSB positions are 0, 1, ..., 19.
- There is a factor Q associated with QCL, for example, Q 8.
- the SSB with candidate SSB index i+n*Q is QCled.
- SSBs can be sent at candidate SSB locations with candidate SSB index i+ n*Q.
- SSB index mod (candidate SSB index, Q) .
- the target time domain unit is a half slot where the RMSI is located.
- the half slot has a first PDSCH and/or a first PDCCH
- the first PDSCH is used to carry the RMSI
- the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- the PRACH occasion if the PRACH occasion overlaps with the half slot containing RMSI (which can be full overlap or partial overlap) , the PRACH occasion is invalid.
- the invalid PRACH occasion is not used for the transmission of preamble, and the invalid PRACH occasion is not used for mapping between SS/PBCH blocks and valid PRACH occasions.
- the half slot containing RMSI refers to a half slot containing RMSI PDCCH and/or RMSI PDSCH, wherein RMSI PDCCH is the first PDCCH in the above scheme, and RMSI PDSCH is the first PDSCH in the above scheme.
- RMSI is the RMSI associated with the actual transmitted SS/PBCH block or QCled SS/PBCH block.
- each candidate SSB location has a candidate SSB index.
- the candidate SSB indexes corresponding to the 20 candidate SSB positions are 0, 1 ..., 19.
- There is a factor Q associated with QCL, for example, Q 8.
- the SSB with candidate SSB index i+ n*Q is quasi co-location (QCled) .
- the SSB can be sent at the SSB candidate location with i+ n*Q candidate SSB index.
- the target SSB is also provided in the half slot, and the target SSB is associated with the RMSI.
- the half slot has a target SSB and at least one of the first PDSCH and the first PDCCH.
- the half slot including RMSI can also be understood as the half slot containing the target SSB. Based on this, if the PRACH occasion overlaps with the half slot containing the target SSB (which can be full overlap or partial overlap) , the PRACH occasion is invalid. The invalid PRACH occasion is not used for the transmission of preamble, and the invalid PRACH occasion is not used for mapping between SS/PBCH blocks and valid PRACH occasions.
- the target SSB is the actual transmitted SS/PBCH block or QCled SS/PBCH block.
- QCled SS/PBCH block refers to the SS/PBCH block with quasi co-location with the actual tansmitted SS/PBCH block.
- each candidate SSB location has a candidate SSB index.
- the candidate SSB indexes corresponding to the 20 candidate SSB positions are 0, 1, ..., 19.
- There is a factor Q associated with QCL, for example, Q 8.
- the SSB with candidate SSB index i+ n*Q is QCled.
- the SSB can be sent at candidate SSB locations with candidate SSB index i+n*Q.
- SSB index mod (candidate SSB index, Q) .
- the target time domain unit is at least one symbol where the RMSI is located.
- the at least one symbol has a first PDSCH and/or a first PDCCH
- the first PDSCH is used to carry the RMSI
- the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- the PRACH occasion if the PRACH occasion overlaps with at least one symbol containing RMSI (which can be full or partial overlap) , the PRACH occasion is invalid.
- the invalid PRACH occasion is not used for the transmission of preamble, and the invalid PRACH occasion is not used for mapping between SS/PBCH blocks and valid PRACH occasions.
- At least one symbol containing RMSI refers to at least one symbol containing RMSI PDCCH and/or RMSI PDSCH, wherein RMSI PDCCH is the first PDCCH in the above scheme, and RMSI PDSCH is the first PDSCH in the above scheme.
- RMSI is RMSI associated with the actual transmitted SS/PBCH block or QCled SS/PBCH block.
- the symbol may refer to an Orthogonal Frequency Division Multiplexing (OFDM) symbol.
- OFDM Orthogonal Frequency Division Multiplexing
- the method 200 of the embodiment of the present disclosure may futher include that: the terminal device determines at least one symbol where the RMSI is located, that is, the terminal device determines at least one symbol where a first PDSCH is located.
- the position of the symbol occupied by the first PDSCH determined by the terminal device may be a position relative to one slot or a position relative to a half slot.
- the half-slot in the embodiment of the present disclosure refers to dividing a complete slot into two parts.
- the half-slot can refer to the first half or the second half of the slot, that is to say, the duration of the half slot is equal to half of the time length of one slot.
- only one RMSI may be included in one slot.
- the DCI information on the RMSI PDCCH indicates that the RMSI PDSCH are located in the symbols k1th to k2th of the same slot. If there is only one RMSI in a slot, all RMSI PDSCHs are in k1th to k2th symbols in the slot where PDCCH is located.
- two RMSIs may be included in one slot.
- the SSB indexes of these two RMSI are different. It can be assumed that the RMSI PDSCH associated with SSBs having even indexes is located in the k1th to k2th symbols in the first half of the slot where the SSB is located; the RMSI PDSCH associated with SSBs having odd SSB indexes is located in the k3 to k4 symbols in the last half of the slot where the SSB is located. Then, according to RMSI PDCCH, the terminal device can determine that the symbols occupied by RMSI PDSCH in a slot may be the k1th to k2th symbols, or the k3 to k4 symbols.
- a slot usually includes at least two RMSIs.
- a slot includes two RMSIs.
- the two half slots in the embodiment of the present disclosure may be located in the same slot or in different slots.
- the terminal device can determine that the second RMSI PDSCH occupies (k1+X) th to (k2+X) th symbols of the second half of the slot; similarly, based on the half slot, it can continue to determine the position (s) of occupied by RMSI PDSCH. in one or more half slots.
- the terminal device can determine that the first RMSI PDSCH occupies the (k3-Y) th to (k4-Y) th symbols in the slot.
- X and/or Y can be pre-defined constants in the protocol, or can be notified to the terminal device by the network side, so that the terminal device can determine the resource location of each RMSI PDSCH.
- the values or determination methods of k1 to k4 involved in the embodiment of the disclosure can be determined by scheduling information carried in RMSI PDCCH, or it can be agreed in advance by the protocol.
- the embodiment of the present disclosure is not limited to this.
- the method 200 of the present disclosure embodiment may also include that: the terminal device determines a target SSB, specifically, the terminal device determines the actual transmitted SSB and SSB having QCL relationship with the actual transmission SSB.
- the actual transmitted SSB is the SBB transmitted between the terminal device and the network device.
- the actually transmitted SSB is the SSB which is received by the terminal device from the network device.
- the terminal device determines the target SSB, which can include that: the terminal device receives the SSB sent by the network device and determines the SSB as the actual transmitted SSB; the terminal device determines the SSB index of the actually transmitted SSB, and determines the SSB with QCL relationship with the actual transmitted SSB according to the SSB index, wherein the actually transmitted SSB and SSB with QCL relationship with the actually transmitted SSB both belong to the target SSB.
- the SSB may be sent on one or more candidate SSB locations corresponding to the SSB index.
- the specific sending position or candidate SSB location depends on the channel occupation of the network device, network device scheduling implementation and other factors.
- the method 200 of the present disclosure embodiment may further include that: the terminal device determines the RMSI associated with the target SSB, that is, the terminal device determines the RMSI associated with the target SSB according to the target SSB.
- the terminal device can determine the associated RMSI based on the target SSB in a variety of ways.
- the ways in which the terminal device determines the RMSI associated with the target SSB may include preconfiguring the RMSI associated with the target SSB, the RMSI associated with the target SSB being indicated in a Master Information Block (MIB) , or the RMSI associated with the target SSB being indicated in a Radio Resource Control (RRC) signaling.
- MIB Master Information Block
- RRC Radio Resource Control
- the terminal device can derive the resource location of the corresponding RMSI PDCCH; in addition, the terminal device can also derive the resource location of the RMSI PDCCH through the scheduling information in the RMSI PDCCH, so as to receive the RMSI PDSCH and obtain RMSI from the RMSI PDCCH.
- any SSB in the embodiment of the present disclosure may refer to a synchronization signal (SS) /physical broadcast channel (PBCH) block.
- An SSB can include a primary synchronization signal (PSS) of an OFDM symbol, a secondary synchronization signal (SSS) of an OFDM symbol or PBCH of two OFDM symbols.
- PSS primary synchronization signal
- SSS secondary synchronization signal
- the time-frequency resources occupied by PBCH may include Demodulation Reference Signal (DMRS) which is used for demodulation of PbCH, but the embodiment of the present disclosure is not limited to this.
- DMRS Demodulation Reference Signal
- the technical schemes of the embodiments of the disclosure provide some methods for determining a valid PRACH occasion in NR-U system. Based on these methods, a network device and terminal device can identify a valid PRACH occasion, and then successfully map the SSB to a PRACH occasion, and conduct random access process.
- the terminal device and the network device determine an invalid PRACH occasion in a set of PRACH occasions that conflicts with the target time domain unit where RMSI is located.
- the PRACH occasion is regarded as an invalid PRACH occasion.
- the PRACH occasion is regarded as an invalid PRACH occasion.
- the PRACH occasion is regarded as an invalid PRACH occasion.
- the PRACH occasion is regarded as an invalid PRACH occasion.
- FIG. 8 is a first schematic diagram of structture of a device for determining a PRACH occasion provided in an embodiment of the present disclosure.
- the device is applied to a terminal device and includes a determination unit 801.
- the determination unit 801 is configured to determine a PRACH occasion overlapped with a target time domain unit as an invalid PRACH occasion, the invalid PRACH occasion being not used for random access.
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- the target time domain unit is a slot where the RMSI is located.
- the slot has a first physical downlink shared channel (PDSCH) and/or a first physical downlink control channel (PDCCH) , the first PDSCH is used to carry the RMSI, and the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- PDSCH physical downlink shared channel
- PDCCH physical downlink control channel
- the slot further has the target SSB, and the target SSB is associated with the RMSI.
- the target time domain unit is a half slot where the RMSI is located.
- the half slot has a first PDSCH and/or a first PDCCH
- the first PDSCH is used to carry the RMSI
- the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- the half slot further has the target SSB, and the target SSB is associated with the RMSI.
- the target time domain unit is at least one symbol where the RMSI is located.
- the at least one symbol has a first PDSCH and/or a first PDCCH
- the first PDSCH is used to carry the RMSI
- the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- FIG. 9 is a second schematic diagram of structure of a device for determining a PRACH occasion provided in an embodiment of the present disclosure.
- the device is applied to a network device and includes a determination unit 901.
- the determination unit 901 is configured to determine a PRACH occasion overlapped with a target time domain unit as an invalid PRACH occasion, the invalid PRACH occasion being not used for random access.
- the target time domain unit is a time domain unit where residual minimum system information (RMSI) is located, the RMSI is associated with a target SS/PBCH block (SSB) , and the target SSB is an actually transmitted SSB or an SSB having quasi co-location (QCL) relationship with the actually transmitted SSB.
- RMSI residual minimum system information
- SSB target SS/PBCH block
- QCL quasi co-location
- the target time domain unit is a slot where the RMSI is located.
- the slot has a first physical downlink shared channel (PDSCH) and/or a first physical downlink control channel (PDCCH) , the first PDSCH is used to carry the RMSI, and the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- PDSCH physical downlink shared channel
- PDCCH physical downlink control channel
- the slot further has the target SSB, and the target SSB is associated with the RMSI.
- the target time domain unit is a half slot where the RMSI is located.
- the half slot has a first PDSCH and/or a first PDCCH
- the first PDSCH is used to carry the RMSI
- the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- the half slot further has the target SSB, and the target SSB is associated with the RMSI.
- the target time domain unit is at least one symbol where the RMSI is located.
- the at least one symbol has a first PDSCH and/or a first PDCCH
- the first PDSCH is used to carry the RMSI
- the first PDCCH is used to schedule the PDSCH carrying the RMSI.
- FIG. 10 is a schematic structural diagram of a communication device 1000 provided in the embodiments of the present disclosure.
- the communication device can be a terminal device or network device.
- the communication device 1000 illustrated in FIG. 10 includes processor 1010, and processor 1010 can call and run computer programs from memory to realize the method in the embodiments of the present disclosure.
- the communication device 1000 may further include a memory 1020.
- the processor 1010 can invoke and run the computer program from memory 1020 to implement the method in the embodiments of the disclosure.
- the memory 1020 may be a separate device independent of or integrated into the processor 1010.
- the communication device 1000 may also include a transceiver 1030.
- the processor 1010 may control the transceiver 1030 to communicate with other devices, in particular, to send information or data to other devices, or receive information or data sent by other devices.
- the transceiver 1030 may include a transmitter and a receiver.
- the transceiver 1030 may further include an antenna (s) , the number of which may be one or more.
- the communication device 1000 can be specifically a network device of the embodiment of the present disclosure, and the communication device 1000 can realize the corresponding process realized by the network device in each method of the embodiments of the present disclosure. For the sake of simplicity, it will not be elaborated here.
- the communication device 1000 can be a mobile terminal/terminal device according to the embodiments of the present disclosure, and the communication device 1000 can realize the corresponding flow realized by the mobile terminal/terminal device in the various methods of the embodiments of the present disclosure. For the sake of brevity, it will not be described here.
- FIG. 11 is a schematic structural diagram of a chip according to an embodiment of the present disclosure.
- the chip 1100 illustrated in FIG. 11 includes processor 1110, and processor 1110 can invoke and run computer programs from memory to implement the method in the embodiments of the disclosure.
- the chip 1100 may also include a memory 1120.
- the processor 1110 can invoke and run the computer program from memory 1120 to implement the method in the embodiments of the disclosure.
- the memory 1120 may be a separate device independent of or integrated into the processor 1110.
- the chip 1100 may also include an input interface 1130.
- the processor 1110 can control the input interface 1130 to communicate with other devices or chips, and in particular can obtain information or data sent by other devices or chips.
- the chip 1100 may also include an output interface 1140.
- the processor 1110 may control the output interface 1140 to communicate with other devices or chips, and in particular may output information or data to other devices or chips.
- the chip can be applied to the network device in the embodiments of the present disclosure, and the chip can realize the corresponding process realized by the network device in each method of the embodiments of the disclosure.
- the chip can realize the corresponding process realized by the network device in each method of the embodiments of the disclosure.
- the chip can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the chip can realize the corresponding flow realized by the mobile terminal/terminal device in each method of the embodiment of the disclosure. For the sake of simplicity, it will not be described here.
- chips mentioned in the embodiments of the present disclosure can also be referred to as system level chips, system chips, chip systems or on-chip system chips, etc.
- FIG. 12 is a schematic block diagram of a communication system 1200 provided by an embodiment of the present disclosure. As illustrated in FIG. 12, the communication system 1200 includes UE 1210 and a network device 1220.
- the UE 1210 can be used to realize the corresponding functions realized by the UE in the above method
- the network device 1220 can be used to realize the corresponding functions realized by the network device in the above method. For the sake of simplicity, it will not be elaborated here.
- the processor of the embodiment of the present disclosure may be an integrated circuit chip with signal processing capability.
- each step of the above method embodiment can be completed by the instruction in the form of integrated logic circuit of hardware or software in the processor.
- the above processors can be general purpose processors, digital signal processors (DSPS) , application specific integrated circuits (ASICs) , field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.
- DSPS digital signal processors
- ASICs application specific integrated circuits
- FPGAs field programmable gate arrays
- the disclosed methods, steps and logic block diagrams in the embodiments of the present disclosure can be implemented or executed.
- the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
- the steps of the method disclosed in connection with the embodiment of the present disclosure can be directly embodied in the execution completion of the hardware decoding processor, or by the combination of the hardware and software modules in the decoding processor.
- the software module can be located in random memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register and other mature storage media in the art.
- the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
- the memory in the embodiments of the present disclosure may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
- the nonvolatile memory can be read-only memory (ROM) , programmable ROM (PROM) , erasable Prom (EPROM) , electrically erasable EPROM (EEPROM) or flash memory.
- Volatile memory can be random access memory (RAM) , which is used as an external cache.
- RAM direct Rambus RAM
- SRAM static RAM
- DRAM dynamic RAM
- SDRAM synchronous DRAM
- DDR SDRAM double data rate SDRAM
- esdram enhanced SDRAM
- SLDRAM synchlink DRAM
- DR RAM direct Rambus RAM
- the memory in the embodiment of the present disclosure can also be static RAM (SRAM) , dynamic RAM (DRAM) , synchronous dynamic random access memory (synchronous DRAM (SDRAM) , double data rate SDRAM (DDR SDRAM) , enhanced SDRAM (ESDRAM) , synchronous link DRAM (SLDRAM) , direct RAM (DR RAM) , etc.
- SRAM static RAM
- DRAM dynamic RAM
- SDRAM synchronous dynamic random access memory
- DDR SDRAM double data rate SDRAM
- ESDRAM enhanced SDRAM
- SLDRAM synchronous link DRAM
- DRAM synchronous link DRAM
- DR RAM direct RAM
- DR RAM direct RAM
- the embodiments of the present disclosure also provide a computer-readable storage medium for storing computer programs.
- the computer-readable storage medium can be applied to the network device in the embodiment of the present disclosure, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiment of the present disclosure. For the sake of brevity, it will not be repeated here.
- the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present disclosure, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiment of the present disclosure. For the sake of brevity, it will not be repeated here.
- the embodiment of the present disclosure also provides a computer program product, including a computer program instruction.
- the computer program product can be applied to the network device in the embodiments of the present disclosure, and the computer program instruction enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiment of the disclosure.
- the computer program instruction enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiment of the disclosure.
- the network device in the embodiments of the present disclosure
- the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the computer program instruction enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in the various methods of the embodiment of the disclosure, for the sake of brevity, it will not be repeated here.
- the embodiment of the present disclosure also provides a computer program.
- the computer program can be applied to the network device in the embodiments of the present disclosure.
- the computer program runs on the computer, the computer executes the corresponding process realized by the network device in each method of the embodiment of the disclosure. For the sake of brevity, it will not be described here.
- the computer program can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure.
- the computer program runs on the computer, the computer executes the corresponding process realized by the mobile terminal/terminal device in the various methods of the embodiment of the disclosure. For the sake of brevity, it will not be elaborated here.
- the disclosed systems, devices and methods can be realized in other ways.
- the embodiment of the device described above is only schematic.
- the division of the unit is only a logical function division, and there can be another division method in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not implemented.
- the mutual coupling or direct coupling or communication connection illustrated or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electric, mechanical or other forms.
- the unit described as a separation part may or may not be physically separated, and the unit displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to the actual needs to achieve the purpose of the embodiment.
- each functional unit in each embodiment of the present disclosure may be integrated in one processing unit, each unit may exist physically alone, or two or more units may be integrated in one unit.
- the function is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the technical solution of the present disclosure in essence or in the form of a software product, which is stored in a storage medium, includes several instructions for making a computer device (which can be a personal computer, a server, a network device, etc. ) ) Perform all or part of the steps of the method according to each embodiment of the present disclosure.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM) , random access memory (RAM) , disk or optical disk and other media that can store program code.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
La présente demande divulgue un procédé de détermination d'une occasion de canal d'accès aléatoire physique (PRACH) et un dispositif terminal, un dispositif de réseau qui peut résoudre une collision de ressources entre des informations de système minimal résiduel (RMSI) et une occasion de PRACH. Le procédé comprend : la détermination, par un dispositif terminal, d'une occasion de PRACH en chevauchement avec une unité de domaine temporel cible en tant qu'occasion de PRACH invalide, l'occasion de PRACH invalide n'étant pas utilisée pour un accès aléatoire, l'unité de domaine temporel cible étant une unité de domaine temporel dans laquelle des RMSI sont situées, les RMSI étant associées à un bloc SS/PBCH (SSB) cible et le SSB cible est un SSB effectivement transmis ou un SSB ayant une relation de quasi-co-localisation (QCL) avec le SSB effectivement transmis.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201962938291P | 2019-11-20 | 2019-11-20 | |
US62/938,291 | 2019-11-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021098570A1 true WO2021098570A1 (fr) | 2021-05-27 |
Family
ID=75980782
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/128150 WO2021098570A1 (fr) | 2019-11-20 | 2020-11-11 | Procédé de détermination d'occasion de prach et dispositif terminal, dispositif de réseau |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2021098570A1 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023083290A1 (fr) * | 2021-11-11 | 2023-05-19 | 维沃移动通信有限公司 | Procédé et appareil d'accès aléatoire, terminal et dispositif côté réseau |
WO2024036523A1 (fr) * | 2022-08-17 | 2024-02-22 | 北京小米移动软件有限公司 | Procédé et appareil de transmission de canal d'accès aléatoire physique, dispositif, et support de stockage lisible |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106301688A (zh) * | 2016-08-30 | 2017-01-04 | 吉林大学 | 一种prach抗干扰技术中支持小区间联合检测的方法 |
US20190149380A1 (en) * | 2017-11-16 | 2019-05-16 | Alireza Babaei | Bandwidth Part Slot Format Indication |
WO2019097016A1 (fr) * | 2017-11-16 | 2019-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Longueur de fenêtre de réponse d'accès aléatoire en nouvelle radio |
CN109803440A (zh) * | 2017-11-16 | 2019-05-24 | 电信科学技术研究院 | 一种进行随机接入的方法及设备 |
-
2020
- 2020-11-11 WO PCT/CN2020/128150 patent/WO2021098570A1/fr active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106301688A (zh) * | 2016-08-30 | 2017-01-04 | 吉林大学 | 一种prach抗干扰技术中支持小区间联合检测的方法 |
US20190149380A1 (en) * | 2017-11-16 | 2019-05-16 | Alireza Babaei | Bandwidth Part Slot Format Indication |
WO2019097016A1 (fr) * | 2017-11-16 | 2019-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Longueur de fenêtre de réponse d'accès aléatoire en nouvelle radio |
CN109803440A (zh) * | 2017-11-16 | 2019-05-24 | 电信科学技术研究院 | 一种进行随机接入的方法及设备 |
Non-Patent Citations (1)
Title |
---|
ETSI MCC: "RAN4#90 Meeting Report", R4-1902801, 12 April 2019 (2019-04-12), pages 670 - 687, XP051703349 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023083290A1 (fr) * | 2021-11-11 | 2023-05-19 | 维沃移动通信有限公司 | Procédé et appareil d'accès aléatoire, terminal et dispositif côté réseau |
WO2024036523A1 (fr) * | 2022-08-17 | 2024-02-22 | 北京小米移动软件有限公司 | Procédé et appareil de transmission de canal d'accès aléatoire physique, dispositif, et support de stockage lisible |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11800517B2 (en) | Method for transmitting downlink signal and terminal device | |
WO2020150957A1 (fr) | Procédé de communication sans fil pour spectre sans licence, et dispositif | |
JP7465289B2 (ja) | 制御情報の伝送方法、端末装置及びネットワーク装置 | |
US11805519B2 (en) | Method for determining transmission bandwidth, device and storage medium | |
US12041641B2 (en) | Resource indication method and terminal device | |
EP3503664A1 (fr) | Dispositif et procédé de communication sans fil | |
US20210176742A1 (en) | Resource allocation method, terminal device, and network device | |
US11902796B2 (en) | Communication method, terminal device, and network device | |
WO2021092774A1 (fr) | Procédé de communication sans fil, dispositif de réseau et dispositif terminal | |
WO2020177040A1 (fr) | Procédé de communication sans fil, dispositif terminal et dispositif de réseau | |
US12185381B2 (en) | Method for determining random access resource and network device | |
CN112703699A (zh) | 传输数据信道的方法和终端设备 | |
EP3735053A1 (fr) | Procédé d'émission de signal, dispositif terminal et dispositif réseau | |
US20210211328A1 (en) | Wireless communication method, transmitting node and receiving node | |
CN113039842B (zh) | 无线通信方法、终端设备和网络设备 | |
EP3869880A1 (fr) | Procédé et dispositif de configuration d'ensemble de ressources de canal de commande de liaison montante physique (pucch) et de détermination de symbole de démarrage | |
JP2021536206A (ja) | リソース決定及び設定方法、装置、端末、ネットワーク装置 | |
WO2021098570A1 (fr) | Procédé de détermination d'occasion de prach et dispositif terminal, dispositif de réseau | |
CN111837430B (zh) | 无线通信的方法、终端设备和网络设备 | |
CN112237037B (zh) | 一种控制信息的传输方法、设备及存储介质 | |
US11856539B2 (en) | Method and device for transmitting downlink control information | |
US20210367825A1 (en) | Wireless communication method, terminal device and network device | |
CN112567822A (zh) | 一种上行信号传输方法、终端和存储介质 | |
WO2020034161A1 (fr) | Procédé de transmission de signal de liaison descendante, terminal, et support de stockage lisible par ordinateur | |
WO2021000239A1 (fr) | Procédé de communication sans fil, dispositif de réseau et dispositif terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20888929 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20888929 Country of ref document: EP Kind code of ref document: A1 |