Communication method, terminal, network device and storage medium

Abstract

Disclosed in embodiments of the present disclosure are a communication method, a terminal, a network device and a storage medium. The method applied to a terminal comprises: on a first carrier, sending a random access sequence to a network device by means of a physical random access channel (PRACH); and on a second carrier, monitoring downlink control information (DCI) sent by the network device and scrambled by a random access radio network temporary identifier (RA-RNTI), wherein the second carrier is determined by the PRACH, or is associated with the first carrier.

Description

Communication method, terminal, network device and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese Patent Application No. 202410071135.0 filed in China on January 17, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The embodiments of the present disclosure relate to the field of wireless communication technologies, and in particular, to a communication method, a terminal, a network device, and a storage medium. Background Art

[0004] To efficiently utilize multi-carrier resources, a universal multi-carrier architecture, known as a resilient network architecture, has been proposed. In this architecture, multiple uplink and downlink carriers form a serving cell. System messages and paging messages are transmitted on only one carrier, known as the anchor carrier. The remaining carriers are known as non-anchor carriers.

[0005] It is usually not necessary to transmit system messages and paging messages on non-anchor carriers. In some cases, the synchronization signal block (SSB) may not be sent. In other cases, sparse primary synchronization signal (PSS) or secondary synchronization signal (SSS) signals may be sent, thereby reducing the overhead of broadcasting information on non-anchor carriers. In addition, the channel quality of the non-anchor carrier can be inferred from the channel quality of the anchor carrier, and a suitable non-anchor carrier can be selected to initiate random access based on the carrier selection criteria configured by the network. However, although the network overhead is reduced, the anchor carrier and the non-anchor carrier, that is, each carrier can be used as a carrier for random access by the terminal, resulting in the network equipment needing to perform random access detection on each uplink carrier, and the network equipment consumes a lot of power. Summary of the Invention

[0006] The embodiments of the present disclosure provide a communication method, terminal, network device, and storage medium. A random access sequence is sent via PRACH on a specific carrier, i.e., a first carrier, and DCI is monitored on a second carrier determined by PRACH or associated with the first carrier. This can avoid the additional power consumption caused by the network device monitoring PRACH on all carriers, reduce the power consumption of the network device, and achieve energy saving.

[0007] The technical solution of the embodiment of the present disclosure is implemented as follows:

[0008] An embodiment of the present disclosure provides a communication method, applied to a terminal, the method comprising:

[0009] Sending a random access sequence to the network device via a physical random access channel PRACH on the first carrier;

[0010] Monitoring downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI and sent by the network device on a second carrier; wherein the second carrier is determined by the PRACH, or is associated with the first carrier.

[0011] The above method further includes:

[0012] When the DCI is monitored, obtaining random access response RAR uplink scheduling grant information according to the DCI;

[0013] Using the RAR uplink scheduling grant information, sending a physical uplink shared channel (PUSCH) to the network device on a third carrier;

[0014] The second carrier is determined by the PRACH, and the third carrier is associated with the second carrier;

[0015] Alternatively, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

[0016] The above method further includes:

[0017] For the third carrier or the first carrier, configure a power offset value for transmitting message 3Msg3 and the random access sequence.

[0018] In the above method, the third carrier is associated with the second carrier, wherein:

[0019] The second carrier is a time division duplex (TDD) carrier, and the third carrier is the same carrier as the second carrier;

[0020] Alternatively, the second carrier is a frequency division duplex (FDD) carrier, and the third carrier is an uplink carrier in the same FDD frequency band as the second carrier;

[0021] Alternatively, configuring the third carrier to be associated with the second carrier through a network;

[0022] Alternatively, the third carrier is a carrier indicated in the DCI or RAR monitored on the second carrier.

[0023] In the above method, the second carrier is associated with the first carrier, wherein:

[0024] The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier;

[0025] Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier;

[0026] Alternatively, the second carrier is associated with the first carrier through network configuration.

[0027] In the above method, the third carrier is determined by the PRACH, and the time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling grant information and the RAR end time slot includes a time offset value other than the following parameters:

[0028] The timeslot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling grant information;

[0029] an additional value other than the slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0030] Cell-specific timeslot offset value.

[0031] In the above method, the second carrier is determined by the PRACH, and the method further includes:

[0032] Receive the correspondence between the PRACH and the second carrier sent by the network device to determine the second carrier.

[0033] In the above method, the third carrier is determined by the PRACH, and the method further includes:

[0034] A correspondence between the PRACH and the third carrier sent by the network device is received to determine the third carrier.

[0035] The above method further includes:

[0036] Receive the maximum number of times the random access sequence is transmitted on the first carrier and / or the power boost step size of the PRACH sent by the network device.

[0037] The above method further includes:

[0038] receiving a window length of a random access response window for monitoring the DCI sent by the network device;

[0039] The window length corresponds to the number of time slots, wherein the time slot lengths included in the random access response windows of different carriers are determined by their respective subcarrier spacings;

[0040] Alternatively, the window length corresponds to an absolute time length, wherein the number of time slots included in the random access response windows of different carriers is determined by the respective subcarrier spacings.

[0041] The above method further includes:

[0042] When no DCI format in which a cyclic redundancy check code CRC is scrambled by the RA-RNTI is detected within the random access response window of the second carrier, the random access sequence is sent through the PRACH on the first carrier.

[0043] The above method further includes:

[0044] When any of the following conditions is met, the PRACH is sent on the uplink carrier associated with the second carrier:

[0045] A DCI format in which the CRC is scrambled by the RA-RNTI is detected, and the least significant bit (LSB) of the system frame number (SFN) in the detected DCI format is different from the LSB of the SFN of the PRACH;

[0046] A transport block TB in a physical downlink shared channel PDSCH is not correctly received within a random access response window of the second carrier;

[0047] The random access preamble identifier RAPID corresponding to the PRACH is not recognized.

[0048] The above method further includes:

[0049] A first time sent by the network device is predefined or received, wherein a start time of the random access response window of the second carrier is related to the first time.

[0050] An embodiment of the present disclosure provides a communication method, applied to a network device, the method comprising:

[0051] Receiving, on the first carrier, a random access sequence sent by the terminal through a physical random access channel PRACH;

[0052] Downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI and sent to the terminal on a second carrier; wherein the second carrier is determined by the PRACH, or is associated with the first carrier.

[0053] The above method further includes:

[0054] receiving, on a third carrier, a PUSCH sent by the terminal based on the random access response RAR uplink scheduling grant information associated with the DCI;

[0055] The second carrier is determined by the PRACH, and the third carrier is associated with the second carrier;

[0056] Alternatively, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

[0057] In the above method, the third carrier is associated with the second carrier, wherein:

[0058] The second carrier is a time division duplex (TDD) carrier, and the third carrier is the same carrier as the second carrier;

[0059] Alternatively, the second carrier is a frequency division duplex (FDD) carrier, and the third carrier is an uplink carrier in the same FDD frequency band as the second carrier;

[0060] Alternatively, configuring the third carrier to be associated with the second carrier through a network;

[0061] Alternatively, the third carrier is a carrier indicated in the DCI or RAR monitored on the second carrier.

[0062] The above method further includes associating the second carrier with the first carrier, wherein:

[0063] The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier;

[0064] Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier;

[0065] Alternatively, the second carrier is associated with the first carrier through network configuration.

[0066] In the above method, the third carrier is determined by the PRACH, and the time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling grant information and the RAR end time slot includes a time offset value other than the following parameters:

[0067] The timeslot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling grant information;

[0068] an additional value other than the slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0069] Cell-specific timeslot offset value.

[0070] In the above method, the second carrier is determined by the PRACH, and the method further includes:

[0071] Sending a correspondence between the random access resource of the PRACH and the second carrier to the terminal, so that the terminal can determine the second carrier.

[0072] In the above method, the third carrier is determined by the PRACH, and the method further includes:

[0073] Sending a correspondence between the random access resources of the PRACH and the third carrier to the terminal, so that the terminal can determine the third carrier.

[0074] The above method further includes:

[0075] Sending, to the terminal, a maximum number of times the random access sequence is transmitted on the first carrier and / or a power boost step size of the PRACH.

[0076] The above method further includes:

[0077] Sending a window length of a random access response window for monitoring the DCI to the terminal;

[0078] The window length corresponds to the number of time slots, wherein the time slot lengths included in the random access response windows of different carriers are determined by their respective subcarrier spacings;

[0079] Alternatively, the window length corresponds to an absolute time length, wherein the number of time slots included in the random access response windows of different carriers is determined by the respective subcarrier spacings.

[0080] The above method further includes:

[0081] The random access sequence sent by the terminal through the PRACH is received on the first carrier or an uplink carrier associated with the second carrier.

[0082] The above method further includes:

[0083] A first time is sent to the terminal, wherein a start time of the random access response window of the second carrier is related to the first time.

[0084] An embodiment of the present disclosure provides a terminal, comprising: a first processor, a first memory, and a first communication bus;

[0085] The first communication bus is used to implement a communication connection between the first processor and the first memory;

[0086] The first processor is configured to execute one or more computer programs stored in the first memory to implement a communication method applied to a terminal.

[0087] An embodiment of the present disclosure provides a network device, comprising: a second processor, a second memory, and a second communication bus;

[0088] The second communication bus is used to implement a communication connection between the second processor and the second memory;

[0089] The second processor is configured to execute one or more computer programs stored in the second memory to implement a communication method applied to a network device.

[0090] An embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed, the above-mentioned communication method is implemented.

[0091] The embodiments of the present disclosure provide a communication method, a terminal, a network device, and a storage medium. The method applied to the terminal includes: sending a random access sequence to the network device via a physical random access channel PRACH on a first carrier; monitoring downlink control information DCI sent by the network device and scrambled by a random access network temporary identifier RA-RNTI on a second carrier; wherein the second carrier is determined by PRACH or associated with the first carrier. The technical solution provided by the embodiments of the present disclosure sends a random access sequence via PRACH on a specific carrier, i.e., the first carrier, and monitors DCI on a second carrier determined by PRACH or associated with the first carrier. This can avoid the extra power consumption caused by the network device monitoring PRACH on all carriers, reduce the power consumption of the network device, and achieve energy saving. BRIEF DESCRIPTION OF THE DRAWINGS

[0092] FIG1 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0093] FIG2 is a schematic diagram of an exemplary carrier configuration provided by an embodiment of the present disclosure;

[0094] FIG3 is a first schematic diagram of an exemplary communication process provided by an embodiment of the present disclosure;

[0095] FIG4 is a second schematic diagram of an exemplary communication process provided by an embodiment of the present disclosure;

[0096] FIG5 is a third schematic diagram of an exemplary communication process provided by an embodiment of the present disclosure;

[0097] FIG6 is a second flow chart of a communication method provided in an embodiment of the present disclosure;

[0098] FIG7 is a first structural diagram of a terminal provided by an embodiment of the present disclosure;

[0099] FIG8 is a second structural diagram of a terminal provided by an embodiment of the present disclosure;

[0100] FIG9 is a first structural diagram of a network device provided by an embodiment of the present disclosure;

[0101] FIG10 is a second structural diagram of a network device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0102] In order to make the purpose, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not intended to limit the present disclosure.

[0103] The following will specifically explain the technical solution of the present disclosure and how it solves the above-mentioned technical problems through embodiments and in conjunction with the accompanying drawings. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0104] In addition, the technical solutions described in the embodiments of the present disclosure can be arbitrarily combined without conflict.

[0105] The present disclosure provides a communication method applicable to a terminal and a network device. The terminal may be a mobile phone or a computer, and the network device may be a base station, which is not limited in the present disclosure.

[0106] FIG1 is a flow chart of a communication method provided by an embodiment of the present disclosure. As shown in FIG1 , in an embodiment of the present disclosure, the communication method applied to a terminal mainly includes the following steps:

[0107] S101. Send a random access sequence to a network device via a physical random access channel PRACH on a first carrier;

[0108] S102: Monitor downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI and sent by a network device on a second carrier; wherein the second carrier is determined by a PRACH, or is associated with the first carrier.

[0109] In an embodiment of the present disclosure, the terminal may send a random access sequence to a network device through a physical random access channel (PRACH) on a first carrier, and further monitor downlink control information (DCI) scrambled by a random access network temporary identifier (RA-RNTI) sent by the network device on a second carrier.

[0110] It should be noted that, in the embodiments of the present disclosure, the first carrier can be specifically described as a specific carrier, an anchor carrier, a first frequency resource, a first cell, etc., and the embodiments of the present disclosure are not limited thereto.

[0111] It is understood that in the embodiments of the present disclosure, a terminal initiates random access to a network device on a first carrier, i.e., executes step S101 above. In this case, the terminal needs to further monitor the network device's response to the random access request, i.e., executes step S102 above. The network device may send DCI to the terminal on a second carrier, thereby enabling the terminal to monitor DCI on the second carrier. Alternatively, the network device may send DCI on all carriers, and the terminal may monitor only on the desired carrier, which may also serve as the second carrier.

[0112] In the embodiment of the present disclosure, considering that the random access sequence is always sent on the first carrier, the terminal may also receive the maximum number of transmissions of the random access sequence on the first carrier and / or the power boost step size of the PRACH sent by the network device.

[0113] It should be noted that in the embodiments of the present disclosure, random access fails after the terminal receives the random access sequence a maximum number of times. The power boost step size is expressed in decibels (dB). The specific maximum number and power boost step size can be set based on actual needs and application scenarios and are not limited in the embodiments of the present disclosure.

[0114] In an embodiment of the present disclosure, considering the implementation of monitoring DCI, the terminal can receive the window length of the random access response window for monitoring DCI sent by the network device; the window length corresponds to the number of time slots, wherein the time slot time length included in the random access response window of different carriers is determined by their respective subcarrier spacing; or, the window length corresponds to the absolute time length, wherein the number of time slots included in the random access response window of different carriers is determined by their respective subcarrier spacing.

[0115] In an embodiment of the present disclosure, the terminal may further perform the following steps: upon monitoring DCI, obtaining random access response (RAR) uplink scheduling authorization information according to the DCI; using the RAR uplink scheduling authorization information, sending a physical uplink shared channel (PUSCH) to the network device on a third carrier; wherein the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier; or, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

[0116] It should be noted that, in the embodiments of the present disclosure, the RAR uplink scheduling grant information can be described as uplink (UL) grant information carried in the RAR, or uplink grant information.

[0117] In an embodiment of the present disclosure, the second carrier is determined by PRACH, or the third carrier is determined by PRACH, and specifically can be determined by the random access resource where the PRACH is located, including random access transmission timing, random access sequence, etc.

[0118] It should be noted that in the embodiments of the present disclosure, considering that after receiving a random access sequence on the first carrier, the network device may need some transition time before turning on the second and third carriers. Based on this, the terminal can introduce a time offset T1 for the start time of the random access response window. The terminal can predefine or receive a first time sent by the network device, where the start time of the random access response window of the second carrier is related to the first time. The first time can be the time offset T1.

[0119] Specifically, in an embodiment of the present disclosure, the current random access response window starts at the first symbol of the earliest control resource set CORESET at least 1 symbol interval after the last symbol of the PRACH opportunity of the PRACH transmission is received. The CORESET is the CORESET of the physical downlink control channel (PDCCH) of the type 1-PDCCH CSS type configured by the terminal. If When both parameters are not 0, the start of the random access response window will introduce an additional T TA +k mac ms, T TA is the time advance of the uplink frame compared to the downlink frame, k mac Configured by the higher layer, or when not configured, it is 0. When the network device needs to wake up the second carrier and its associated uplink carrier based on PRACH, considering the wake-up conversion time of the carrier, it is necessary to introduce a T-removal window for the random access response window. TA , k mac The starting time offset outside the parameters is the first time T1. T1 can be the sum of some time variables or a single time variable. T1 can be a predefined value or configured by a system message, which is not limited in the present embodiment.

[0120] In an embodiment of the present disclosure, taking into account the different path losses corresponding to different carriers, when the path loss reference signal transmission of the third carrier is located on the downlink carrier associated with the first carrier, when message 3 (Message3, Msg3) is transmitted on the third carrier, and the third carrier is different from the first carrier, the estimated path loss is the same, but the actual third carrier frequency used for uplink transmission may be quite different from that of the first carrier, resulting in a large difference in the propagation path loss. If the same target receiving power is configured for different third carriers, the terminal will send the same power on different third carriers. After experiencing different path losses, the receiving power reaching the network device cannot all reach the same target receiving power. Based on this, the terminal can configure the power offset value for Msg3 and the random access sequence transmission for the third carrier or the first carrier.

[0121] In an embodiment of the present disclosure, the terminal uses RAR uplink scheduling authorization information to schedule PUSCH transmission, that is, the transmission of Msg3. The PUSCH is located on the third carrier, and the third carrier can be the first carrier. Specifically, the third carrier is associated with the second carrier, and the second carrier is determined by PRACH. When the second carrier determined based on PRACH is the carrier associated with the first carrier, the third carrier is the same as the first carrier.

[0122] In an embodiment of the present disclosure, the terminal may receive a correspondence between a random access resource of a PRACH and a second carrier sent by a network device to determine the second carrier.

[0123] In an embodiment of the present disclosure, the second carrier is determined by a PRACH, and the third carrier is associated with the second carrier, wherein:

[0124] The second carrier is a time division duplexing (TDD) carrier, and the third carrier is the same carrier as the second carrier. Exemplarily, the first carrier is used to configure a downlink bandwidth (Bandwidth Part, BWP) of the second carrier and an uplink BWP (initial BWP) of the third carrier for the terminal, and Msg3 of the random access process is located on the configured uplink BWP of the third carrier.

[0125] Alternatively, the second carrier is a frequency division duplexing (FDD) carrier, and the third carrier is an uplink carrier in the same FDD frequency band as the second carrier;

[0126] Alternatively, the third carrier is associated with the second carrier through network configuration;

[0127] Alternatively, the third carrier is a carrier indicated in the DCI or RAR monitored on the second carrier.

[0128] It should be noted that in the embodiments of the present disclosure, based on relevant technologies, the transmission of Msg3 and Msg1 (i.e., PRACH) needs to be located on the same BWP of the same carrier. However, Msg1 and Msg3 in the present disclosure can be located on different carriers, which may depend on the PRACH selected by the terminal, as shown in Figure 2. If the second carrier determined based on the PRACH is the downlink carrier associated with the first carrier, the transmission of Msg3 will still be located on the first carrier. If the second carrier determined based on the PRACH is not the downlink carrier associated with the first carrier, the transmission of Msg3 will be determined by the above-mentioned method of determining the third carrier.

[0129] In the embodiment of the present disclosure, random access is initiated on the first carrier so that network devices on other uplink carriers do not have to monitor PRACH all the time, thereby saving power consumption of the network devices. However, if the network device has already turned on other uplink carriers at this time, some behaviors need to be redesigned.

[0130] In an embodiment of the present disclosure, the terminal may further perform the following steps: when no DCI format in which a cyclic redundancy check (CRC) is scrambled by the RA-RNTI is detected within the random access response window of the second carrier, the terminal may transmit a random access sequence via the PRACH on the first carrier. This generally means that the terminal attempts to transmit the PRACH again.

[0131] It can be understood that in the embodiment of the present disclosure, in the above situation, the terminal cannot determine whether the network device has successfully received the PRACH, and cannot determine whether the network device has started receiving other carriers. Therefore, at this time, the random access sequence is still sent through the PRACH on the first carrier, that is, retransmission is achieved.

[0132] In an embodiment of the present disclosure, the terminal may further send a PRACH on an uplink carrier associated with the second carrier when any of the following conditions is met:

[0133] A DCI format in which the CRC is scrambled by the RA-RNTI is detected, and the least significant bit (LSB) of the system frame number (SFN) in the detected DCI format is different from the LSB of the SFN of the PRACH;

[0134] A transport block (TB) in a physical downlink shared channel (PDSCH) is not correctly received within a random access response window of the second carrier;

[0135] The Random Access Preamble Identifier (RAPID) corresponding to the PRACH was not identified.

[0136] It should be noted that, in an embodiment of the present disclosure, if the terminal detects a DCI format, and the LSB of the SFN in the detected DCI format is different from the LSB of the SFN of the PRACH, it means that the network device has responded to other terminals. At this time, it means that the network device has turned on the reception of other carriers. Therefore, at this time, the terminal sends a random access sequence through the PRACH on the uplink carrier associated with the second carrier, instead of the first carrier, to reduce the congestion probability of the PRACH of the first carrier. This usually corresponds to trying to send the PRACH again.

[0137] It should be noted that, in the embodiment of the present disclosure, the situation where the TB in the PDSCH is not correctly received within the random access response window of the second carrier is also due to the response of the network device, indicating that the network device has turned on the reception of other carriers. Therefore, at this time, the terminal sends a random access sequence through the PRACH on the uplink carrier associated with the second carrier, instead of the first carrier, thereby reducing the congestion probability of the PRACH of the first carrier.

[0138] It should be noted that, in the embodiment of the present disclosure, in the above situation, the network needs to configure random access resources for random access on the uplink carrier associated with the second carrier.

[0139] For example, in the embodiments of the present disclosure, three frequency bands are assumed: Band 8 (900 MHz FDD band), Band 3 (1.8 GHz FDD band), and Band 41 (2.6 GHz TDD band). Band 8 is assumed to be the anchor carrier. The uplink frequency band of Band 8 corresponds to the first carrier, the downlink frequency band of Band 8, the downlink frequency band of Band 3, and Band 41 (TDD frequencies do not distinguish between uplink and downlink) all correspond to the second carrier. The uplink frequency band of Band 8 and Band 41 serve as the third carrier (i.e., the first carrier is also a part of the third carrier).

[0140] Referring to Figure 3, Terminal 1 selects the random access resource corresponding to band 8 to send a PRACH. Since band 8 is an FDD band, its associated downlink carrier is the FDD downlink band corresponding to band 8. Therefore, Terminal 1 monitors the RA-RNTI-scrambled DCI on the FDD downlink band corresponding to band 8 to read the RAR. After monitoring, the scheduled PUSCH is sent on the FDD uplink band corresponding to band 8, which is the first carrier. In this case, the first carrier can also be considered as one of the third carriers.

[0141] Referring to Figure 4, Terminal 2 selects the random access resource corresponding to band 3 and transmits a PRACH on the first carrier, band 8. Since band 3 is an FDD band, its associated downlink carrier is the FDD downlink band corresponding to band 3. Therefore, Terminal 2 monitors the RA-RNTI-scrambled DCI on the FDD downlink band corresponding to band 3 to read the RAR. Upon monitoring, the scheduled PUSCH is transmitted on the FDD uplink band corresponding to band 3, i.e., the third carrier. At this time, when performing random access response detection on the downlink band of band 3, the start time of the random access response window needs to take into account an additional time offset, T1.

[0142] As shown in Figure 5, Terminal 3 selects the random access resource corresponding to band 41 to transmit the PRACH on the first carrier, band 8. Therefore, Terminal 3 monitors the RA-RNTI-scrambled DCI in the downlink timeslot of band 41 to read the RAR. Upon monitoring, the scheduled PUSCH is transmitted in the uplink timeslot of band 41, i.e., the third carrier. In this case, the second and third carriers are the same carrier. When performing random access response detection on band 41, the start time of the random access response window must take into account an additional time offset, T1.

[0143] In the embodiments of the present disclosure, a solution for changing the carrier of Msg3 is also involved.

[0144] In the embodiments of the present disclosure, a PRACH is transmitted on a first carrier, and DCI scrambled by the RA-RNTI is monitored on a second carrier. The terminal obtains a random access response using the RA-RNTI-scrambled DCI. The uplink scheduling grant information in the random access response schedules PUSCH transmission, i.e., Msg3. This PUSCH is located on a third carrier, which is determined by the PRACH.

[0145] In an embodiment of the present disclosure, the terminal may receive a correspondence between a random access resource of a PRACH and a third carrier sent by a network device to determine the third carrier.

[0146] In an embodiment of the present disclosure, the third carrier is determined by PRACH, and the second carrier is associated with the first carrier, wherein:

[0147] The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier; for example, the terminal monitors the DCI scrambled by the RA-RNTI on the activated BWP of the second carrier;

[0148] Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier;

[0149] Alternatively, the second carrier is associated with the first carrier through network configuration.

[0150] In the embodiment of the present disclosure, for the above situation, since the carrier is changed before Msg3 is transmitted, based on this, the time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling grant information and the RAR end time slot may include a time offset value T2 in addition to the following parameters:

[0151] The time slot offset value K2 indicated by the time domain resource allocation information in the RAR uplink scheduling grant information;

[0152] The additional value delta in addition to the slot offset value K2 corresponding to the subcarrier spacing of the PUSCH;

[0153] Cell-specific timeslot offset value K cell,offset .

[0154] It should be noted that, in the embodiment of the present disclosure, T2 may be a predefined value, or may be configured through a system message, which is not limited in the embodiment of the present disclosure.

[0155] It should be noted that, in the embodiment of the present disclosure, considering that the third carrier may be in an on state, the network may indicate whether T2 needs to be considered in the time slot offset value.

[0156] FIG6 is a flow chart of a communication method provided by an embodiment of the present disclosure. As shown in FIG6 , in an embodiment of the present disclosure, the communication method applied to a network device mainly includes the following steps:

[0157] S201. Receive, on a first carrier, a random access sequence sent by a terminal via a physical random access channel PRACH;

[0158] S202: Send downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI to the terminal on a second carrier; wherein the second carrier is determined by a PRACH, or is associated with the first carrier.

[0159] In an embodiment of the present disclosure, corresponding to the above-mentioned communication method applied to a terminal, the network device may further perform the following steps: receiving, on a third carrier, a PUSCH sent by the terminal based on RAR uplink scheduling grant information associated with the DCI;

[0160] The second carrier is determined by the PRACH, and the third carrier is associated with the second carrier;

[0161] Alternatively, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

[0162] In an embodiment of the present disclosure, the third carrier is associated with the second carrier, wherein:

[0163] The second carrier is a TDD carrier, and the third carrier is the same carrier as the second carrier;

[0164] Alternatively, the second carrier is an FDD carrier, and the third carrier is an uplink carrier in the same FDD frequency band as the second carrier;

[0165] Alternatively, the third carrier is associated with the second carrier through network configuration;

[0166] Alternatively, the third carrier is a carrier indicated in the DCI or RAR monitored on the second carrier.

[0167] In an embodiment of the present disclosure, the second carrier is associated with the first carrier, wherein:

[0168] The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier;

[0169] Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier;

[0170] Alternatively, the second carrier is associated with the first carrier through network configuration.

[0171] It should be noted that, in the embodiments of the present disclosure, the relevant descriptions of the first carrier, the second carrier, and the third carrier are consistent with the above-mentioned communication method applied to the terminal, and will not be repeated here.

[0172] In an embodiment of the present disclosure, if the second carrier is determined by PRACH, the network device sends the correspondence between the random access resources of PRACH and the second carrier to the terminal for the terminal to determine the second carrier. If the third carrier is determined by PRACH, the network device sends the correspondence between the random access resources of PRACH and the third carrier to the terminal for the terminal to determine the third carrier.

[0173] In the embodiment of the present disclosure, the third carrier is determined by the PRACH, and the time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling grant information and the RAR end time slot may include a time offset value T2 in addition to the following parameters:

[0174] The time slot offset value K2 indicated by the time domain resource allocation information in the RAR uplink scheduling grant information;

[0175] The additional value delta in addition to the slot offset value K2 corresponding to the subcarrier spacing of the PUSCH;

[0176] Cell-specific timeslot offset value K cell,offset .

[0177] It should be noted that in the embodiment of the present disclosure, in the scheme of changing the carrier of Msg3, since the carrier is changed before Msg3 transmission, considering the scheduling of Msg3 PUSCH in RAR, an additional time offset value can be considered, which will not be repeated here.

[0178] In an embodiment of the present disclosure, the network device may further send the maximum number of times the random access sequence is transmitted on the first carrier and / or the power boost step of the PRACH to the terminal to restrict the number of times the terminal initiates random access on the first carrier.

[0179] In an embodiment of the present disclosure, the network device may further send a window length of a random access response window for monitoring DCI to the terminal;

[0180] The window length corresponds to the number of time slots, where the time slot lengths included in the random access response windows of different carriers are determined by their respective subcarrier spacings;

[0181] Alternatively, the window length corresponds to an absolute time length, wherein the number of time slots included in the random access response windows of different carriers is determined by the respective subcarrier spacings.

[0182] In the embodiment of the present disclosure, the network device may also receive a random access sequence sent by the terminal through the PRACH on the first carrier or an uplink carrier associated with the second carrier.

[0183] In an embodiment of the present disclosure, the network device may further send a first time to the terminal, wherein the start time of the random access response window of the second carrier is related to the first time.

[0184] It should be noted that, in the embodiments of the present disclosure, the above contents have been described in the communication method applied to the terminal and will not be repeated here.

[0185] Based on the above communication method applied to network devices and terminals, it can be seen that the technical solution provided by the embodiment of the present disclosure, by designing a random access sequence to be sent via PRACH on a first carrier and monitoring DCI on a second carrier determined by PRACH or associated with the first carrier, can avoid the additional power consumption caused by the network device monitoring PRACH on all carriers, thereby achieving energy saving. Moreover, when the terminal needs to retransmit PRACH, the carrier for retransmitting PRACH is determined based on the monitoring status of the network device on other carriers, which can ensure the performance of PRACH while saving energy on the network device.

[0186] The present disclosure provides a terminal. FIG7 is a first structural diagram of a terminal provided by the present disclosure. As shown in FIG7 , in the embodiment of the present disclosure, the terminal includes:

[0187] The first communication module 301 is configured to send a random access sequence to a network device via a physical random access channel PRACH on a first carrier; and monitor downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI sent by the network device on a second carrier; wherein the second carrier is determined by the PRACH, or is associated with the first carrier.

[0188] In one embodiment of the present disclosure, the first communication module 301 is further configured to, when monitoring the DCI, obtain random access response RAR uplink scheduling authorization information according to the DCI; and use the RAR uplink scheduling authorization information to send a physical uplink shared channel PUSCH to the network device on a third carrier; wherein the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier; or, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

[0189] In an embodiment of the present disclosure, the first communication module 301 is further configured to configure a power offset value for transmitting message 3Msg3 and the random access sequence for the third carrier or the first carrier.

[0190] In one embodiment of the present disclosure, the third carrier is associated with the second carrier, wherein:

[0191] The second carrier is a time division duplex (TDD) carrier, and the third carrier is the same carrier as the second carrier;

[0192] Alternatively, the second carrier is a frequency division duplex (FDD) carrier, and the third carrier is an uplink carrier in the same FDD frequency band as the second carrier;

[0193] Alternatively, configuring the third carrier to be associated with the second carrier through a network;

[0194] Alternatively, the third carrier is a carrier indicated in the DCI or RAR monitored on the second carrier.

[0195] In an embodiment of the present disclosure, the second carrier is associated with the first carrier, wherein:

[0196] The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier;

[0197] Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier;

[0198] Alternatively, the second carrier is associated with the first carrier through network configuration.

[0199] In one embodiment of the present disclosure, the third carrier is determined by the PRACH, and the time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling grant information and the RAR end time slot includes a time offset value other than the following parameters:

[0200] The timeslot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling grant information;

[0201] an additional value other than the slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0202] Cell-specific timeslot offset value.

[0203] In one embodiment of the present disclosure, the second carrier is determined by the PRACH, and the first communication module 301 is further configured to receive a correspondence between the random access resources of the PRACH and the second carrier sent by the network device to determine the second carrier.

[0204] In one embodiment of the present disclosure, the third carrier is determined by the PRACH, and the first communication module 301 is further configured to receive a correspondence between the random access resources of the PRACH sent by the network device and the third carrier to determine the third carrier.

[0205] In an embodiment of the present disclosure, the first communication module 301 is further configured to receive, from the network device, a maximum number of times the random access sequence is transmitted on the first carrier and / or a power boost step size of the PRACH.

[0206] In an embodiment of the present disclosure, the first communication module 301 is further configured to receive a window length of a random access response window for monitoring the DCI sent by the network device;

[0207] The window length corresponds to the number of time slots, wherein the time slot lengths included in the random access response windows of different carriers are determined by their respective subcarrier spacings;

[0208] Alternatively, the window length corresponds to an absolute time length, wherein the number of time slots included in the random access response windows of different carriers is determined by the respective subcarrier spacings.

[0209] In one embodiment of the present disclosure, the first communication module 301 is further configured to send the random access sequence through the PRACH on the first carrier when no DCI format in which the cyclic redundancy check code CRC is scrambled by the RA-RNTI is detected within the random access response window of the second carrier.

[0210] In one embodiment of the present disclosure, the first communication module 301 is further configured to send a PRACH on an uplink carrier associated with the second carrier when any of the following conditions is met:

[0211] A DCI format in which the CRC is scrambled by the RA-RNTI is detected, and the least significant bit (LSB) of the system frame number (SFN) in the detected DCI format is different from the LSB of the SFN of the PRACH;

[0212] A transport block TB in a physical downlink shared channel PDSCH is not correctly received within a random access response window of the second carrier;

[0213] The random access preamble identifier RAPID corresponding to the PRACH is not recognized.

[0214] In an embodiment of the present disclosure, the first communication module 301 is further configured to predefine or receive a first time sent by the network device, wherein the start time of the random access response window of the second carrier is related to the first time.

[0215] Figure 8 is a second schematic diagram of the structure of a terminal provided by an embodiment of the present disclosure. As shown in Figure 8, in an embodiment of the present disclosure, the terminal includes: a first processor 401, a first memory 402 and a first communication bus 403;

[0216] The first communication bus 403 is used to implement a communication connection between the first processor 401 and the first memory 402;

[0217] The first processor 401 is configured to execute one or more computer programs stored in the first memory 402 to implement a communication method applied to a terminal.

[0218] The present disclosure provides a network device. FIG9 is a first structural diagram of a network device provided by the present disclosure. As shown in FIG9 , the network device includes:

[0219] The second communication module 501 is configured to receive, on a first carrier, a random access sequence sent by a terminal through a physical random access channel PRACH; and send, on a second carrier, downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI to the terminal; wherein the second carrier is determined by the PRACH, or is associated with the first carrier.

[0220] In one embodiment of the present disclosure, the second communication module 501 is further used to receive, on a third carrier, a PUSCH sent by the terminal based on the random access response RAR uplink scheduling authorization information associated with the DCI; wherein the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier; or, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

[0221] In one embodiment of the present disclosure, the third carrier is associated with the second carrier, wherein:

[0222] The second carrier is a time division duplex (TDD) carrier, and the third carrier is the same carrier as the second carrier;

[0223] Alternatively, the second carrier is a frequency division duplex (FDD) carrier, and the third carrier is an uplink carrier in the same FDD frequency band as the second carrier;

[0224] Alternatively, configuring the third carrier to be associated with the second carrier through a network;

[0225] Alternatively, the third carrier is a carrier indicated in the DCI or RAR monitored on the second carrier.

[0226] In an embodiment of the present disclosure, the second carrier is associated with the first carrier, wherein:

[0227] The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier;

[0228] Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier;

[0229] Alternatively, the second carrier is associated with the first carrier through network configuration.

[0230] In one embodiment of the present disclosure, the third carrier is determined by the PRACH, and the time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling grant information and the RAR end time slot includes a time offset value other than the following parameters:

[0231] The timeslot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling grant information;

[0232] an additional value other than the slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0233] Cell-specific timeslot offset value.

[0234] In one embodiment of the present disclosure, the second carrier is determined by the PRACH, and the second communication module 501 is further configured to send a correspondence between the random access resources of the PRACH and the second carrier to the terminal, so that the terminal can determine the second carrier.

[0235] In one embodiment of the present disclosure, the third carrier is determined by the PRACH, and the second communication module 501 is further configured to send a correspondence between the random access resources of the PRACH and the third carrier to the terminal, so that the terminal can determine the third carrier.

[0236] In an embodiment of the present disclosure, the second communication module 501 is further configured to send, to the terminal, a maximum number of times the random access sequence is transmitted on the first carrier, and / or a power boost step size of the PRACH.

[0237] In an embodiment of the present disclosure, the second communication module 501 is further configured to send a window length of a random access response window for monitoring the DCI to the terminal;

[0238] The window length corresponds to the number of time slots, wherein the time slot lengths included in the random access response windows of different carriers are determined by their respective subcarrier spacings;

[0239] Alternatively, the window length corresponds to an absolute time length, wherein the number of time slots included in the random access response windows of different carriers is determined by the respective subcarrier spacings.

[0240] In an embodiment of the present disclosure, the second communication module 501 is further configured to receive the random access sequence sent by the terminal through the PRACH on the first carrier or an uplink carrier associated with the second carrier.

[0241] In an embodiment of the present disclosure, the second communication module 501 is further configured to send a first time to the terminal, wherein a start time of the random access response window of the second carrier is related to the first time.

[0242] Figure 10 is a second structural diagram of a network device provided by an embodiment of the present disclosure. As shown in Figure 10, the network device includes: a second processor 601, a second memory 602, and a second communication bus 603;

[0243] The second communication bus 603 is used to implement a communication connection between the second processor 601 and the second memory 602;

[0244] The second processor 601 is configured to execute one or more computer programs stored in the second memory 602 to implement a communication method applied to a network device.

[0245] The present disclosure provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned communication method when executed by a processor. The computer-readable storage medium can be a volatile memory (volatile memory), such as a random-access memory (RAM); or a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); or can be a respective device including one or any combination of the above-mentioned memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc.

[0246] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0247] The present disclosure is described with reference to the implementation flow diagrams and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flow diagram and / or block diagram can be implemented by computer program instructions, as well as the combination of the processes and / or boxes in the flow diagram and / or block diagram. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flow diagram and / or one or more boxes in the block diagram.

[0248] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in implementing one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0249] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0250] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this utility model should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A communication method, applied to a terminal, the method comprising: Sending a random access sequence to a network device via a Physical Random Access Channel (PRACH) on a first carrier; Listening on a second carrier for Downlink Control Information (DCI) scrambled by a Random Access Radio Network Temporary Identifier (RA-RNTI) sent by the network device; wherein, the second carrier is determined by the PRACH, or is associated with the first carrier.

2. The method according to claim 1, further comprising: When the DCI is listened, obtaining Random Access Response (RAR) uplink scheduling authorization information according to the DCI; Using the RAR uplink scheduling authorization information to send a Physical Uplink Shared Channel (PUSCH) to the network device on a third carrier; wherein, the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier; or, the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

3. The method according to claim 2, further comprising: Configuring a power offset value for Message 3 (Msg3) and the transmission of the random access sequence for the third carrier or the first carrier.

4. The method according to claim 2, wherein, The third carrier is associated with the second carrier, wherein: The second carrier is a Time Division Duplex (TDD) carrier, and the third carrier is the same carrier as the second carrier; or, the second carrier is a Frequency Division Duplex (FDD) carrier, and the third carrier is an uplink carrier in the same FDD band as the second carrier; or, the third carrier is associated with the second carrier through network configuration; or, the third carrier is the carrier indicated in the DCI or RAR listened on the second carrier.

5. The method according to claim 1 or 2, wherein The second carrier is associated with the first carrier, wherein: The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier; or, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD band as the first carrier; or, the second carrier is associated with the first carrier through network configuration.

6. The method according to claim 2, wherein The third carrier is determined by the PRACH, and the time slot offset value between the transmission time slot of the PUSCH scheduled by the RAR uplink scheduling authorization information and the RAR end time slot includes a time offset value other than the following parameters: The time slot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling authorization information; An additional value other than the time slot offset value corresponding to the subcarrier spacing of the PUSCH; A cell-specific time slot offset value.

7. The method according to claim 1 or 2, wherein The second carrier is determined by the PRACH, the method further comprising: Receiving the correspondence between the random access resources of the PRACH and the second carrier sent by the network device to determine the second carrier.

8. The method according to claim 2, wherein The third carrier is determined by the PRACH, the method further comprising: Receiving the correspondence between the random access resources of the PRACH and the third carrier sent by the network device to determine the third carrier.

9. The method according to claim 1, further comprising: Receive the maximum number of times to transmit the random access sequence on the first carrier sent by the network device, and / or the power ramp step of the PRACH.

10. The method according to claim 1, further comprising: Receiving the window length of the random access response window for listening to the DCI sent by the network device; The window length corresponds to the number of time slots, where the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings; Alternatively, the window length corresponds to an absolute time length, where the number of time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings.

11. The method according to claim 1, further comprising: When a DCI format scrambled by the RA-RNTI with a cyclic redundancy check code CRC is not detected within the random access response window of the second carrier, transmitting the random access sequence on the first carrier through the PRACH.

12. The method according to claim 1, further comprising: When any of the following conditions is met, transmitting a PRACH on an uplink carrier associated with the second carrier: Detecting a DCI format scrambled by the RA-RNTI, and the least significant bit LSB of the system frame number SFN in the detected DCI format is different from the LSB of the SFN of the PRACH; Not correctly receiving the transport block TB in the physical downlink shared channel PDSCH within the random access response window of the second carrier; Not recognizing the random access preamble identifier RAPID corresponding to the PRACH.

13. The method according to claim 1, further comprising: Predefining or receiving a first time sent by the network device, where the start time of the random access response window of the second carrier is related to the first time.

14. A communication method, applied to a network device, the method comprising: Receiving a random access sequence sent by a terminal through a physical random access channel PRACH on a first carrier; Sending a downlink control information DCI scrambled by a random access network temporary identifier RA-RNTI to the terminal on a second carrier; where the second carrier is determined by the PRACH, or is associated with the first carrier.

15. The method according to claim 14, further comprising: Receiving a PUSCH sent by the terminal based on the random access response RAR uplink scheduling authorization information associated with the DCI on a third carrier; Where the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier; Or the second carrier is associated with the first carrier, and the third carrier is determined by the PRACH.

16. The method according to claim 15, wherein, The third carrier is associated with the second carrier, where: The second carrier is a time division duplex TDD carrier, and the third carrier is the same carrier as the second carrier; Or the second carrier is a frequency division duplex FDD carrier, and the third carrier is an uplink carrier in the same FDD band as the second carrier; Or the third carrier is associated with the second carrier through network configuration; Alternatively, the third carrier is the carrier indicated in the DCI or RAR monitored on the second carrier.

17. The method according to claim 14 or 15, wherein, The second carrier is associated with the first carrier, where: The first carrier is a TDD carrier, and the second carrier is the same carrier as the first carrier; Alternatively, the first carrier is an FDD carrier, and the second carrier is a downlink carrier in the same FDD frequency band as the first carrier; Alternatively, the second carrier is associated with the first carrier through network configuration.

18. The method according to claim 15, wherein, The third carrier is determined by the PRACH. The time slot offset value between the PUSCH transmission time slot scheduled by the RAR uplink scheduling authorization information and the RAR end time slot includes time offset values other than the following parameters: The time slot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling authorization information; An additional value other than the time slot offset value corresponding to the subcarrier spacing of the PUSCH; A cell-specific time slot offset value.

19. The method according to claim 14 or 15, wherein The second carrier is determined by the PRACH. The method further includes: Sending the correspondence between the random access resources of the PRACH and the second carrier to the terminal for the terminal to determine the second carrier.

20. The method according to claim 15, wherein The third carrier is determined by the PRACH. The method further includes: Sending the correspondence between the random access resources of the PRACH and the third carrier to the terminal for the terminal to determine the third carrier.

21. The method according to claim 14, further including: Sending to the terminal the maximum number of times of transmitting the random access sequence on the first carrier, and / or, the power ramp step of the PRACH.

22. The method according to claim 14, further including: Sending to the terminal the window length of the random access response window for monitoring the DCI; The window length corresponds to the number of time slots. Among them, the time slot time lengths included in the random access response windows of different carriers are determined by their respective subcarrier spacings; Alternatively, the window length corresponds to an absolute time length. Among them, the number of time slots included in the random access response windows of different carriers are determined by their respective subcarrier spacings.

23. The method according to claim 14, further including: Receiving, on the first carrier or an uplink carrier associated with the second carrier, the random access sequence sent by the terminal through the PRACH.

24. The method according to claim 14, further including: Sending a first time to the terminal, where the start time of the random access response window of the second carrier is related to the first time.

25. A terminal, comprising: A first processor, a first memory, and a first communication bus; The first communication bus is used to implement the communication connection between the first processor and the first memory; The first processor is used to execute one or more computer programs stored in the first memory to implement the communication method according to any one of claims 1-13.

26. A network device, comprising: A second processor, a second memory, and a second communication bus; The second communication bus is used to implement the communication connection between the second processor and the second memory; The second processor is configured to execute one or more computer programs stored in the second memory to implement the communication method according to any one of claims 14-24.

27. A computer-readable storage medium having a computer program stored thereon, which when executed implements the communication method according to any one of claims 1-24.

Images