Communication method, terminal, network device and storage medium

Abstract

The embodiment of the invention discloses a communication method, a terminal, network equipment and a storage medium. The method applied to the terminal comprises the following steps: sending a random access sequence to the network equipment on a first carrier through a physical random access channel (PRACH); monitoring downlink control information (DCI) scrambled by a random access network temporary identifier (RA-RNTI) and sent by the network equipment on a second carrier; wherein the second carrier is determined by the PRACH, or is associated with the first carrier.

Description

Technical Field

[0001] Embodiments of the present application 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

[0002] Currently, in order to efficiently use multi-carrier resources, a general multi-carrier architecture has been proposed, which is called an elastic network architecture. In this architecture, multiple uplink carriers and downlink carriers form a serving cell. System messages and paging messages are only transmitted on one of the carriers, which can be called an anchor carrier, and the other carriers can be called non-anchor carriers.

[0003] System messages and paging messages generally do not need to be transmitted on non-anchor carriers. In some cases, synchronization signal blocks (SSBs) may not be sent, and in other cases, sparse primary synchronization signals (PSS) or secondary synchronization signals (SSS) may be sent, thereby reducing the overhead of broadcast information on non-anchor carriers. In addition, the channel quality of non-anchor carriers can be inferred from the channel quality of the anchor carrier, and a suitable non-anchor carrier can be selected based on the carrier selection criterion configured by the network to initiate random access. However, although the network overhead is reduced, both the anchor carrier and the non-anchor carrier, that is, each carrier can be used by the terminal as a carrier for random access, resulting in the network device needing to perform random access detection on each uplink carrier, and the power consumption of the network device is relatively large. Summary of the Invention

[0004] Embodiments of the present application provide a communication method, a terminal, a network device, and a storage medium. A random access sequence is sent through a physical random access channel (PRACH) on a specific carrier, that is, a first carrier, and a downlink control information (DCI) is listened for on a second carrier determined by the PRACH or associated with the first carrier, which can avoid the additional power consumption caused by the network device listening for PRACH on all carriers, reduce the power consumption of the network device, and achieve energy saving.

[0005] The technical solution of the embodiments of the present application is implemented as follows:

[0006] Embodiments of the present application provide a communication method, which is applied to a terminal. The method includes:

[0007] Sending a random access sequence to a network device through a physical random access channel (PRACH) on a first carrier;

[0008] Monitor the downlink control information DCI scrambled by the random access radio network temporary identity RA-RNTI sent by the network device on the second carrier; wherein, the second carrier is determined by the PRACH or is associated with the first carrier.

[0009] In the above method, it further includes:

[0010] When the DCI is monitored, obtain the random access response RAR uplink scheduling authorization information according to the DCI;

[0011] Use the RAR uplink scheduling authorization information to send a physical uplink shared channel PUSCH to the network device on the third carrier;

[0012] Wherein, the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier;

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

[0014] In the above method, it further includes:

[0015] Configure a power offset value for the message 3 Msg3 and the transmission of the random access sequence for the third carrier or the first carrier.

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

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

[0018] 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;

[0019] Or, the third carrier is associated with the second carrier through network configuration;

[0020] Or, the third carrier is the carrier indicated in the DCI or RAR monitored on the second carrier.

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

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

[0023] 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;

[0024] Alternatively, configure the second carrier to be associated with the first carrier via a network.

[0025] In the above method, 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:

[0026] The time slot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling authorization information;

[0027] An additional value other than the time slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0028] The cell-specific time slot offset value.

[0029] In the above method, the second carrier is determined by the PRACH. The method further includes:

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

[0031] In the above method, the third carrier is determined by the PRACH. The method further includes:

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

[0033] In the above method, it further includes:

[0034] Receiving the maximum number of times to transmit the random access sequence on the first carrier and / or the power ramp step of the PRACH sent by the network device.

[0035] In the above method, it further includes:

[0036] Receiving the window length of the random access response window for listening to the DCI sent by the network device;

[0037] The window length corresponds to the number of time slots. Among them, the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings;

[0038] 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 is determined by their respective subcarrier spacings.

[0039] In the above method, it further includes:

[0040] When a DCI format with a cyclic redundancy check code (CRC) scrambled by a random access radio network temporary identifier (RA-RNTI) is not detected within the random access response window of the second carrier, the random access sequence is transmitted on the first carrier via the physical random access channel (PRACH).

[0041] In the above method, it further includes:

[0042] When any of the following conditions is met, the PRACH is transmitted on an uplink carrier associated with the second carrier:

[0043] A DCI format with a CRC scrambled by an 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;

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

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

[0046] In the above method, it further includes:

[0047] 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.

[0048] An embodiment of the present application provides a communication method applied to a network device. The method includes:

[0049] Receive, on a first carrier, a random access sequence sent by a terminal via the physical random access channel (PRACH);

[0050] Send, on a second carrier, downlink control information (DCI) scrambled by a random access radio network temporary identifier (RA-RNTI) to the terminal; where the second carrier is determined by the PRACH or is associated with the first carrier.

[0051] In the above method, it further includes:

[0052] Receive, on a third carrier, a physical uplink shared channel (PUSCH) sent by the terminal based on random access response (RAR) uplink scheduling authorization information associated with the DCI;

[0053] Wherein, the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier;

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

[0055] In the above method, the third carrier is associated with the second carrier, where:

[0056] The second carrier is a Time Division Duplex (TDD) carrier, and the third carrier is the same carrier as the second carrier;

[0057] 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;

[0058] Or, the third carrier is associated with the second carrier through network configuration;

[0059] Or, the third carrier is the carrier indicated in the DCI or RAR monitored on the second carrier.

[0060] In the above method, it further includes: The second carrier is associated with the first carrier, where:

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

[0062] 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;

[0063] Or, the second carrier is associated with the first carrier through network configuration.

[0064] In the above method, 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:

[0065] The time slot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling authorization information;

[0066] Extra values other than the time slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0067] Cell-specific time slot offset values.

[0068] In the above method, the second carrier is determined by the PRACH. The method further includes:

[0069] 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.

[0070] In the above method, the third carrier is determined by the PRACH. The method further includes:

[0071] Send the 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.

[0072] In the above method, it further includes:

[0073] Send the maximum number of times to transmit the random access sequence on the first carrier and / or the power ramp step of the PRACH to the terminal.

[0074] In the above method, it further includes:

[0075] Send the window length of the random access response window for listening to the DCI to the terminal;

[0076] The window length corresponds to the number of time slots. Among them, the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings;

[0077] 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 is determined by their respective subcarrier spacings.

[0078] In the above method, it further includes:

[0079] On the first carrier or the uplink carrier associated with the second carrier, receive the random access sequence sent by the terminal through the PRACH.

[0080] In the above method, it further includes:

[0081] Send 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.

[0082] An embodiment of the present application provides a terminal, including: a first processor, a first memory, and a first communication bus;

[0083] The first communication bus is used to realize the communication connection between the first processor and the first memory;

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

[0085] An embodiment of the present application provides a network device, including: a second processor, a second memory, and a second communication bus;

[0086] The second communication bus is used to realize the communication connection between the second processor and the second memory;

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

[0088] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed, the above communication method is implemented.

[0089] An embodiment of the present application provides 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 through a Physical Random Access Channel (PRACH) on a first carrier; listening for Downlink Control Information (DCI) scrambled by a Random Access Radio Network Temporary Identifier (RA-RNTI) sent by the network device on a second carrier; where the second carrier is determined by the PRACH or is associated with the first carrier. The technical solution provided by the embodiment of the present application can avoid the additional power consumption caused by the network device listening for PRACH on all carriers by sending a random access sequence through the PRACH on a specific carrier, that is, the first carrier, and listening for DCI on the second carrier determined by the PRACH or associated with the first carrier, reduce the power consumption of the network device, and achieve energy saving. Description of the Drawings

[0090] Figure 1 It is a flowchart of a communication method provided by an embodiment of the present application Figure 1 ;

[0091] Figure 2 It is a schematic diagram of an exemplary carrier configuration provided by an embodiment of the present application;

[0092] Figure 3 It is a schematic diagram of an exemplary communication process provided by an embodiment of the present application Figure 1 ;

[0093] Figure 4 It is a schematic diagram of an exemplary communication process provided by an embodiment of the present application Figure 2 ;

[0094] Figure 5 It is a schematic diagram of an exemplary communication process provided by an embodiment of the present application Figure 3 ;

[0095] Figure 6 It is a flowchart of a communication method provided by an embodiment of the present application Figure 2 ;

[0096] Figure 7 It is a schematic diagram of the structure of a terminal provided by an embodiment of the present application Figure 1 ;

[0097] Figure 8Structural schematic of a terminal provided by an embodiment of the present application Figure 2 ;

[0098] Figure 9 Structural schematic of a network device provided by an embodiment of the present application Figure 1 ;

[0099] Figure 10 Structural schematic of a network device provided by an embodiment of the present application Figure 2 。 Detailed implementation manners

[0100] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be 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 application and are not used to limit the present application.

[0101] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be specifically described below through embodiments in combination 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.

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

[0103] An embodiment of the present application provides a communication method, which is applied to a terminal and a network device. The terminal may specifically be a mobile phone or a computer, and the network device may specifically be a base station. The embodiments of the present application do not make limitations.

[0104] Figure 1 Flow schematic of a communication method provided by an embodiment of the present application Figure 1 。As Figure 1 shown, in the embodiment of the present application, the communication method applied to the terminal mainly includes the following steps:

[0105] S101. Send a random access sequence to the network device through a physical random access channel PRACH on a first carrier;

[0106] S102. Listen for downlink control information DCI scrambled by a random access radio 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.

[0107] In an embodiment of the present application, the terminal may send a random access sequence to the network device on a first carrier through a Physical Random Access Channel (PRACH). Further, the terminal listens on a second carrier for downlink control information (DCI) scrambled by a Radio Access Network Temporary Identifier (RA-RNTI) sent by the network device.

[0108] It should be noted that, in an embodiment of the present application, the first carrier may specifically be described as a specific carrier, an anchor carrier, a first frequency resource, a first cell, etc., and the embodiments of the present application do not make any limitations.

[0109] It can be understood that, in an embodiment of the present application, when the terminal initiates random access to the network device on the first carrier, that is, performs the above step S101, in this case, the terminal needs to further listen for the response of the network device to the random access request, that is, perform the above step S102. The network device may send DCI to the terminal on the second carrier, so that the terminal listens for DCI on the second carrier. In addition, the network device may also send DCI on all carriers, and the terminal only listens on the expected carrier, which may also be used as the second carrier.

[0110] In an embodiment of the present application, considering that the random access sequence is always sent on the first carrier, the terminal may also receive the maximum number of times of transmitting the random access sequence on the first carrier sent by the network device, and / or the power ramp step of the PRACH.

[0111] It should be noted that, in an embodiment of the present application, the random access fails after the number of times the terminal receives the random access sequence reaches the maximum number. The unit of the power ramp step is decibel (dB). The specific maximum number and power ramp step may be set according to actual requirements and application scenarios, and the embodiments of the present application do not make any limitations.

[0112] In an embodiment of the present application, considering the implementation of listening for DCI, the terminal may receive the window length of the random access response window for listening for DCI sent by the network device; the window length corresponds to the number of time slots. Among them, the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings; or the window length corresponds to an absolute time length, and the number of time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings.

[0113] In an embodiment of the present application, the terminal may further perform the following steps: when a DCI is monitored, obtain random access response (RAR) uplink scheduling authorization information according to the DCI; use the RAR uplink scheduling authorization information to send a physical uplink shared channel (PUSCH) to a 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.

[0114] It should be noted that, in an embodiment of the present application, the RAR uplink scheduling authorization information may be described as the UL grant information carried in the RAR, or uplink authorization information.

[0115] In an embodiment of the present application, the above-mentioned second carrier is determined by the PRACH, or the third carrier is determined by the PRACH. Specifically, it may be determined by the random access resource where the PRACH is located, including the random access transmission opportunity, the random access sequence, etc.

[0116] It should be noted that, in an embodiment of the present application, considering that when a random access sequence is received on the first carrier, the network device then activates the second carrier and the third carrier, the network device may require a conversion time. Based on this, the terminal may introduce a time offset T1 for the start time of the random access response window, which may be predefined or the first time sent by the network device received. Among them, the start time of the random access response window of the second carrier is related to the first time, and the first time may be the time offset T1.

[0117] Specifically, in an embodiment of the present application, the current random access response window starts from the first symbol of the earliest control resource set (CORESET) that is at least 1 symbol interval after the last symbol of the PRACH occasion where the PRACH is transmitted. This CORESET is the CORESET for the terminal to receive type1-PDCCH CSS type PDCCH. If when two parameters are not 0, an additional T TA +k mac ms will be introduced at the start of the random access response window. T TA is the time advance of the uplink frame compared to the downlink frame. k mac is configured by the higher layer, or takes 0 when not configured. When the network device needs to wake up the second carrier and its associated uplink carrier based on the PRACH, considering the wake-up conversion time of the carrier, an additional T TA , k macThe starting time offset outside the parameter, i.e., 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 embodiments of this application.

[0118] In the embodiments of this application, considering that the path loss corresponding to different carriers is different, when the path loss reference signal transmission of the third carrier is located in the downlink carrier associated with the first carrier, when transmitting Message 3 (Msg3) on the third carrier and the third carrier is different from the first carrier, the estimated path loss is the same. However, the actual frequency point of the third carrier used for uplink transmission may be quite different from that of the first carrier, resulting in a relatively large difference in the propagated path loss. If the same target receiving power is configured for different third carriers, it will cause the terminal to transmit at 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 a power offset value for the transmission of Msg3 and the random access sequence for the third carrier or the first carrier.

[0119] In the embodiments of this application, the terminal uses the RAR uplink scheduling authorization information to schedule the PUSCH transmission, i.e., 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 the PRACH. When the second carrier determined based on the PRACH is the carrier associated with the first carrier, the third carrier is the same as the first carrier.

[0120] In the embodiments of this application, the terminal can receive the correspondence between the random access resources of the PRACH sent by the network device and the second carrier to determine the second carrier.

[0121] In the embodiments of this application, the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier, where:

[0122] The second carrier is a Time Division Duplexing (TDD) carrier, and the third carrier is the same as the second carrier; Exemplarily, by configuring the downlink BandwidthPart (BWP) of the second carrier and the uplink BWP (initial BWP) of the third carrier for the terminal through the first carrier, Msg3 in the random access process is located on the uplink BWP of the configured third carrier;

[0123] Or, the second carrier is a Frequency Division Duplexing (FDD) carrier, and the third carrier is the uplink carrier in the same FDD band as the second carrier;

[0124] Alternatively, configure the third carrier to be associated with the second carrier via the network;

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

[0126] It should be noted that in the embodiments of the present application, based on the prior art, the transmissions of Msg3 and Msg1 (i.e., PRACH) need to be on the same BWP of the same carrier. However, in the present application, Msg1 and Msg3 can be on different carriers, which can depend on the PRACH selected by the terminal. See Figure 2 as shown. 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 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 for determining the third carrier.

[0127] In the embodiments of the present application, considering that initiating random access on the first carrier is for the network device on other uplink carriers not to always monitor the PRACH, saving the power consumption of the network device. However, if the network device has already enabled other uplink carriers at this time, then some behaviors need to be redesigned at this time.

[0128] In the embodiments of the present application, the terminal can also perform the following steps: within the random access response window of the second carrier, when a DCI format with a cyclic redundancy check (CRC) scrambled by the RA-RNTI is not detected, send a random access sequence on the first carrier through the PRACH. This usually means that the terminal tries to send the PRACH again.

[0129] It can be understood that in the embodiments of the present application, in the above situation, the terminal cannot determine whether the network device has successfully received the PRACH, nor can it determine whether the network device has enabled the reception of other carriers. Therefore, at this time, a random access sequence is still sent on the first carrier through the PRACH, that is, retransmission is achieved.

[0130] In the embodiments of the present application, the terminal can also send the PRACH on the uplink carrier associated with the second carrier when any of the following conditions is met:

[0131] A DCI format with a CRC 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;

[0132] Within the random access response window of the second carrier, the transport block (TB) in the Physical Downlink Shared Channel (PDSCH) is not correctly received;

[0133] The Random Access Preamble Identifier (RAPID) corresponding to the PRACH is not recognized.

[0134] It should be noted that in the embodiments of the present application, 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 indicates that the network device has responded to other terminals. At this time, it means that the network device has started receiving on 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, rather than the first carrier, reducing the congestion probability of the PRACH on the first carrier. Here, it usually also corresponds to attempting to send the PRACH again.

[0135] It should be noted that in the embodiments of the present application, for the situation where the TB in the PDSCH is not correctly received within the random access response window of the second carrier, it is also because the network device has responded, indicating that the network device has started receiving on 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, rather than the first carrier, reducing the congestion probability of the PRACH on the first carrier.

[0136] It should be noted that in the embodiments of the present application, in the above cases, the network needs to configure random access resources for random access on the uplink carrier associated with the second carrier.

[0137] Exemplarily, in the embodiments of the present application, assume there are three frequency bands, band 8: FDD frequency band 900 MHz, band 3: FDD frequency band 1.8 GHz, band 41: TDD frequency point 2.6 GHz. Assume band 8 is the anchor carrier. The uplink frequency band of band 8 corresponds to the first carrier, the downlink frequency band of band 8, and the downlink frequency bands of band 3 and band 41 (the TDD frequency point does not distinguish between uplink and downlink) all correspond to the second carrier; the uplink frequency band of band 8 and band 41 are used as the third carrier (that is, the first carrier is also one of the third carriers).

[0138] See Figure 3, the terminal 1 selects the random access resource corresponding to band8 to send a PRACH. Since band8 is an FDD band, its associated downlink carrier is the FDD downlink band corresponding to band8. Therefore, the terminal 1 monitors the DCI scrambled by RA-RNTI in the FDD downlink band corresponding to band8 to read the RAR. After detecting it, the scheduled PUSCH is sent in the FDD uplink band corresponding to band8, that is, the first carrier. At this time, it can also be considered that the first carrier is one of the third carriers.

[0139] See Figure 4 , the terminal 2 selects the random access resource corresponding to band3 to send a PRACH on the first carrier band8. Since band3 is an FDD band, its associated downlink carrier is the FDD downlink band corresponding to band3. Therefore, the terminal 2 monitors the DCI scrambled by RA-RNTI in the FDD downlink band corresponding to band3 to read the RAR. After detecting it, the scheduled PUSCH is sent in the FDD uplink band corresponding to band3, that is, the third carrier. When performing random access response detection on the downlink band of band3, the start time of the random access response window needs to consider an additional time offset T1.

[0140] See Figure 5 , the terminal 3 selects the random access resource corresponding to band41 to send a PRACH on the first carrier band8. Therefore, the terminal 3 monitors the DCI scrambled by RA-RNTI in the downlink time slot of band41 to read the RAR. After detecting it, the scheduled PUSCH is sent in the uplink time slot of band41, that is, the third carrier. At this time, the second carrier and the third carrier are the same carrier. When performing random access response detection on band41, the start time of the random access response window needs to consider an additional time offset T1.

[0141] In the embodiments of the present application, a solution for Msg3 to change the carrier is also involved.

[0142] In the embodiments of the present application, a PRACH is sent on the first carrier, and the DCI scrambled by RA-RNTI is monitored on the second carrier. The terminal obtains a random access response through the DCI scrambled by RA-RNTI. The uplink scheduling authorization information of the random access response schedules the PUSCH transmission, that is, Msg3. This PUSCH is located on the third carrier, and the third carrier is determined by the PRACH.

[0143] In the embodiments of the present application, the terminal can receive the correspondence between the random access resource of the PRACH sent by the network device and the third carrier to determine the third carrier.

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

[0145] 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;

[0146] 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;

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

[0148] In the embodiment of the present application, 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 other than the following parameters:

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

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

[0151] The cell-specific time slot offset value K cell,offset .

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

[0153] It should be noted that, in the embodiment of the present application, 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.

[0154] Figure 6 A communication method according to an embodiment of the present invention is provided. Figure 2 .like Figure 6 As shown, in an embodiment of the present application, the communication method applied to the network device mainly includes the following steps:

[0155] S201, receiving a random access sequence sent by a terminal through a physical random access channel PRACH on a first carrier;

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

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

[0158] wherein, the second carrier is determined by a PRACH, and the third carrier is associated with the second carrier;

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

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

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

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

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

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

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

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

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

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

[0169] It should be noted that in an embodiment of the present application, the related descriptions of the first carrier, the second carrier, and the third carrier are the same as those in the above communication method applied to a terminal, and will not be elaborated herein.

[0170] In an embodiment of the present application, if the second carrier is determined by a PRACH, the network device sends 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. If the third carrier is determined by a PRACH, the network device sends 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.

[0171] In an embodiment of the present application, the third carrier is determined by the PRACH. The time slot offset value between the time slot for PUSCH transmission scheduled by the RAR uplink scheduling authorization information and the RAR end time slot may include a time offset value T2 other than the following parameters:

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

[0173] An additional value delta other than the time slot offset value K2 corresponding to the subcarrier spacing of the PUSCH;

[0174] The cell-specific time slot offset value K cell,offset 。

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

[0176] In an embodiment of the present application, the network device may also send 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, to restrict the number of times the terminal initiates random access on the first carrier.

[0177] In an embodiment of the present application, the network device may also send to the terminal the window length of the random access response window for listening to the DCI;

[0178] The window length corresponds to the number of time slots. Among them, the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings;

[0179] 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.

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

[0181] In an embodiment of the present application, the network device may also send to the terminal a first time, where the start time of the random access response window of the second carrier is related to the first time.

[0182] It should be noted that in an embodiment of the present application, the above content has been described in the communication method applied to the terminal, and will not be elaborated here.

[0183] Based on the above communication methods applied to network devices and terminals, it can be seen that the technical solution provided by the embodiments of the present application, by designing to send a random access sequence through the PRACH on the first carrier and listening for DCI on the second carrier determined by the PRACH or associated with the first carrier, can avoid the additional power consumption caused by the network device listening for the PRACH on all carriers and achieve energy saving. And when the terminal needs to retransmit the PRACH, determining the carrier for retransmitting the PRACH according to the listening state of the network device on other carriers can ensure the performance of the PRACH while the network device saves energy.

[0184] Embodiments of the present application provide a terminal. Figure 7 The structural schematic diagram of a terminal provided by the embodiments of the present application Figure 1 . As Figure 7 shown, in the embodiments of the present application, the terminal includes:

[0185] A first communication module 301, configured to send a random access sequence to a network device through a physical random access channel (PRACH) on a first carrier; and listen for downlink control information (DCI) scrambled by a random access radio 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.

[0186] In an embodiment of the present application, the first communication module 301 is further configured to, when the DCI is listened, 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, 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.

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

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

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

[0190] 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;

[0191] Alternatively, configure the third carrier to be associated with the second carrier via the network;

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

[0193] In an embodiment of the present application, the second carrier is associated with the first carrier, where:

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

[0195] 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;

[0196] Alternatively, configure the second carrier to be associated with the first carrier via the network.

[0197] In an embodiment of the present application, 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:

[0198] The time slot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling authorization information;

[0199] Extra values other than the time slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0200] Cell-specific time slot offset values.

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

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

[0203] In an embodiment of the present application, the first communication module 301 is further configured to receive the maximum number of times of transmitting the random access sequence on the first carrier sent by the network device, and / or, the power ramp step of the PRACH.

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

[0205] The window length corresponds to the number of time slots. Among them, the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier intervals;

[0206] 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 is determined by their respective subcarrier intervals.

[0207] In an embodiment of the present application, the first communication module 301 is further configured to, when a DCI format scrambled by RA-RNTI for cyclic redundancy check code CRC is not detected within the random access response window of the second carrier, send the random access sequence on the first carrier through the PRACH.

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

[0209] A DCI format scrambled by 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;

[0210] Within the random access response window of the second carrier, the transport block TB in the physical downlink shared channel PDSCH is not correctly received;

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

[0212] In an embodiment of the present application, the first communication module 301 is further configured to pre-define or receive the 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.

[0213] Figure 8 Schematic structure of a terminal provided by an embodiment of the present application Figure 2 As Figure 8 shown, in an embodiment of the present application, the terminal includes: a first processor 401, a first memory 402, and a first communication bus 403;

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

[0215] 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.

[0216] An embodiment of the present application provides a network device. Figure 9 The structural schematic of a network device provided by an embodiment of the present application Figure 1 . As Figure 9 shown, the network device includes:

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

[0218] In an embodiment of the present application, the second communication module 501 is further configured to receive a physical uplink shared channel (PUSCH) sent by the terminal based on random access response (RAR) uplink scheduling authorization information associated with the DCI on a third carrier; wherein, the second carrier is determined by the PRACH, 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.

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

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

[0221] 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;

[0222] Or, the third carrier is associated with the second carrier through network configuration;

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

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

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

[0226] 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;

[0227] Alternatively, configure the second carrier to be associated with the first carrier via a network.

[0228] In an embodiment of the present application, 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:

[0229] The time slot offset value indicated by the time domain resource allocation information in the RAR uplink scheduling authorization information;

[0230] An additional value other than the time slot offset value corresponding to the subcarrier spacing of the PUSCH;

[0231] The cell-specific time slot offset value.

[0232] In an embodiment of the present application, the second carrier is determined by the PRACH. The second communication module 501 is further configured to send 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.

[0233] In an embodiment of the present application, the third carrier is determined by the PRACH. The second communication module 501 is further configured to send 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.

[0234] In an embodiment of the present application, the second communication module 501 is further configured to send the maximum number of times of transmitting the random access sequence on the first carrier and / or the power ramp step of the PRACH to the terminal.

[0235] In an embodiment of the present application, the second communication module 501 is further configured to send the window length of the random access response window for listening to the DCI to the terminal;

[0236] The window length corresponds to the number of time slots. Among them, the time length of the time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings;

[0237] 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 is determined by their respective subcarrier spacings.

[0238] In an embodiment of the present application, 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.

[0239] In an embodiment of the present application, the second communication module 501 is further configured to send 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.

[0240] Figure 10 Schematic structure of a network device provided by an embodiment of the present application Figure 2 . As Figure 10 shown, the network device includes: a second processor 601, a second memory 602, and a second communication bus 603;

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

[0242] 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 the network device.

[0243] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned communication method is implemented. The computer-readable storage medium may be a volatile memory, such as a random access memory (Random-Access Memory, RAM); or a non-volatile memory, such as a read-only memory (Read-Only Memory, ROM), a flash memory, a hard disk (Hard Disk Drive, HDD) or a solid-state drive (Solid-State Drive, SSD); it may also be a respective device including one or any combination of the above memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, etc.

[0244] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories and optical memories, etc.) containing computer-usable program codes.

[0245] This application is described with reference to the schematic implementation flowchart and / or block diagram of a method, device (system), and computer program product according to an embodiment of the present application. It should be understood that each process and / or block in the schematic implementation flowchart and / or block diagram, as well as the combination of processes and / or blocks in the schematic implementation flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in one or more processes and / or one or more blocks in the schematic implementation flowchart. Figure 1 One or more processes and / or Figure 1 blocks.

[0246] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device that implements the functions specified in one or more processes and / or one or more blocks in the schematic implementation flowchart. Figure 1 One or more processes and / or Figure 1 blocks.

[0247] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes and / or one or more blocks in the schematic implementation flowchart. Figure 1 One or more processes and / or Figure 1 blocks.

[0248] As described above, this is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a terminal, the method includes: 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, wherein The method further includes: When the DCI is detected, 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, wherein The method further includes: 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, characterized in that, 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, characterized in that, 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 time slot for transmitting 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, characterized in that, The second carrier is determined by the PRACH, and the method further includes: 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, and the method further includes: 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, wherein The method further includes: Receiving the maximum number of times for transmitting the random access sequence on the first carrier and / or the power ramp step of the PRACH sent by the network device.

10. The method according to claim 1, wherein The method further includes: Receive 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. Among them, 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. Among them, 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, wherein The method further includes: When a DCI format scrambled by the RA-RNTI for the cyclic redundancy check code CRC is not detected within the random access response window of the second carrier, send the random access sequence on the first carrier through the PRACH.

12. The method according to claim 1, characterized in that, The method further includes: When any of the following conditions is met, send a PRACH on the uplink carrier associated with the second carrier: Detect 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; Within the random access response window of the second carrier, the transport block TB in the physical downlink shared channel PDSCH is not correctly received; The random access preamble identifier RAPID corresponding to the PRACH is not recognized.

13. The method according to claim 1, wherein The method further includes: Pre-define or receive the 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, characterized in that, Applied to a network device, the method includes: Receive a random access sequence sent by a terminal on a first carrier through a physical random access channel PRACH; Send 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, wherein The method further includes: Receive a PUSCH sent by the terminal on a third carrier based on the random access response RAR uplink scheduling authorization information associated with the DCI; Among them, the second carrier is determined by the PRACH, and the third carrier is associated with the second carrier; Alternatively, 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; Alternatively, 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; Alternatively, configure the third carrier to be associated with the second carrier through the network; Alternatively, the third carrier is the carrier indicated in the DCI or RAR listened to on the second carrier.

17. The method according to claim 14 or 15, characterized in that 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 band as the first carrier; Alternatively, configure the second carrier to be associated with the first carrier via a network.

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

19. The method according to claim 14 or 15, characterized in that, 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, characterized in that, 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, wherein The method further includes: 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, wherein The method further includes: Sending to the terminal the window length of the random access response window for listening to the DCI; The window length corresponds to the number of time slots. Among them, 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. Among them, the number of time slots included in the random access response windows of different carriers is determined by their respective subcarrier spacings.

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

24. The method according to claim 14, characterized in that, The method further includes: 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, characterized in that, Includes: 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 configured 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, characterized in that, Includes: 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, characterized in that, When the computer program is executed, it implements the communication method according to any one of claims 1-24.

Images