Communication method and communication device

Abstract

The present application provides a communication method and a communication device. The method includes receiving a first DCI from a network device, and determining based on the first DCI that the first data scheduled by the first DCI includes a first SIB1, where the first SIB1 includes information about network access in a first operation mode. The first DCI includes first indication information, where the first indication information indicates that the first data includes the first SIB1. Alternatively, one or more of the following information related to the first DCI, scrambling information, DCI format information, time domain resource information, or frequency domain resource information, is different from that related to a second DCI, where the second DCI is used to schedule a second SIB1, where the second SIB1 includes information about network access in a second operation mode. In the present application, the specific SIB1 scheduled by the DCI is determined based on information about the DCI, so that the terminal device can accurately identify the content scheduled by the DCI. This helps to improve communication reliability.

Description

[Technical Field]

[0001] The present application relates to the field of communication technologies, and in particular to communication methods and devices. [Background technology]

[0002] Currently, mobile communication networks are becoming increasingly complex. Typically, a terminal device can transmit services by establishing a connection with a network device. Typically, a terminal device can obtain information about accessible networks by receiving and parsing a system information block 1 (SIB1) from the network device. However, in some cases, a terminal device cannot access a network. For example, if a terminal device is incompatible with a network device because the network device has been successfully upgraded but the terminal device has not been successfully upgraded or cannot be upgraded, the terminal device may not be able to correctly receive, parse, or decode the SIB1 sent by the network device, and thus cannot access the network. Based on this, how to ensure successful network access by a terminal device to improve communication reliability has become one of the most pressing issues currently to be resolved. Summary of the Invention

[0003] The present application provides a communication method and a communication device to improve communication reliability.

[0004] According to a first aspect, the present application provides a communication method, the method being applicable to a terminal device. The method includes receiving, from a network device, first downlink control information (DCI) used to schedule first data; and determining, based on the first DCI, that the first data includes a first system information block (SIB1) containing information about network access in a first operation mode. The first DCI includes first indication information, the first indication information indicating that the first data includes a first SIB1; or, one or more of the following information associated with the first DCI, including scrambling information, downlink control information format (SIB1) information, time domain resource information, or frequency domain resource information, is different from that associated with a second DCI, the second DCI being used to schedule a second SIB1, the second SIB1 containing information about network access in a second operation mode.

[0005] In this application, a terminal device receives a first DCI from a network device, and determines the type or version of SIB1 scheduled by the first DCI based on the first indication information, the scrambling information of the first DCI, the DCI format, the time domain resource information of the first DCI, or the frequency domain resource information of the first DCI carried in the first DCI, so that the terminal device can correctly identify the content scheduled by the DCI and correctly perform HARQ combining to improve the reliability of data reception and the reliability of subsequent communications.

[0006] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0007] In a possible implementation, the first message further includes second indication information, which indicates that the first message includes the first SIB1.

[0008] In this application, the second indication information is carried in the first message (i.e., the RRC message), so that the terminal device can determine the type or version of the first SIB1 included in the first message based on the second indication information, and ensure that the terminal device can correctly perform RRC ASN.1 decoding, which also helps to improve communication reliability.

[0009] In a possible implementation, the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH), the first RLC entity is different from the second RLC entity, or the first LCH is different from the second LCH, the second RLC entity is associated with a second SIB1, and the second LCH is associated with the second SIB1.

[0010] In the present application, the terminal device determines the type or version of the first SIB1 based on the logical channel or RLC entity, so that the terminal device can correctly identify the content contained in the RRC message and correctly perform RRC decoding to obtain accurate information.

[0011] In a possible implementation, the method further includes obtaining third indication information associated with the first message, the third indication information indicating that the first message includes the first SIB1.

[0012] In this application, the terminal device obtains third indication information associated with the first message, and then determines the type or version of the first SIB1 based on the third indication information to ensure that the terminal device can correctly perform RRC ASN.1 decoding.

[0013] In a possible implementation, obtaining the third indication information associated with the first message includes a radio resource control (RRC) layer of the terminal device obtaining the third indication information from a physical (PHY) layer of the terminal device or a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) layer of the terminal device.

[0014] In this application, the third indication information may be generated in the physical layer, MAC layer, RLC layer, or PDCP layer of the terminal device and transmitted to an upper layer (e.g., the RRC layer). For example, the third indication information may be included in a newly defined MAC, RLC, or PDCP subheader. The third indication information may be used to determine a decoding scheme in the RRC layer to ensure that the terminal device can correctly perform RRC ASN.1 decoding. This inter-layer interaction mode is diverse, easy to operate, and highly applicable.

[0015] In a possible implementation, the method further includes receiving fourth instruction information from the network device instructing the network device to send the first SIB1, the fourth instruction information being carried in the master information block MIB or the second DCI.

[0016] In this application, the terminal device receives the fourth indication information and determines whether the network device should transmit the first SIB1 based on the fourth indication information. In this way, if the terminal device determines that the network device should not transmit the first SIB1, the terminal device no longer needs to monitor the PDCCH corresponding to the first SIB1. This can save the energy of the terminal device.

[0017] In a possible implementation, the method further includes receiving first data from the network device based on the first DCI.

[0018] According to a second aspect, the present application provides a communication method, the method being applied to a terminal device, the method including: receiving third downlink control information (DCI) from a network device, where the third DCI is used to schedule at least two pieces of data, or where the third DCI is used to schedule second data and fourth DCI, and the fourth DCI is used to schedule first data; and receiving first data and / or second data from the network device based on the third DCI, where the at least two pieces of data include the first data and the second data, the first data including a first system information block 1 (SIB1) and the second data including a second SIB1, where the first SIB1 includes information regarding network access in a first operation mode and the second SIB1 includes information regarding network access in a second operation mode.

[0019] In the present application, one DCI is used to schedule two SIB1s, or a DCI for a first SIB1 is used to schedule a DCI for a second SIB1, so that the terminal device can accurately identify the same data and accurately perform HARQ combining to improve the reliability of data reception.

[0020] In a possible implementation, the third DCI includes time domain resource information and / or frequency domain resource information of the first data.

[0021] In the present application, the time domain resource information and frequency domain resource information of the first data are dynamically or quasi-statically configured in the third DCI, so that the terminal device can accurately receive the first data and / or the second data based on the information configured in the third DCI.

[0022] In a possible implementation, the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the second data, or the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the third DCI, and / or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the second data, or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the third DCI; The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0023] In this application, the time domain resource information and / or frequency domain resource information of the first data is indirectly configured, specifically, an interval between the time domain resource of the first data and the time domain resource of the second data and / or an interval between the frequency domain resource of the first data and the frequency domain resource of the second data is configured, so that the terminal device can determine the time domain resource and / or frequency domain resource of the second data based on the interval configured in the third DCI and by referring to the time domain resource and / or frequency domain resource of the second data included in the third DCI. For the first data specific time Area Resources and / or is around Optionally, the terminal device may alternatively determine the frequency domain resources based on the interval set in the third DCI and with reference to the time domain resources and / or frequency domain resources of the third DCI to accurately receive the corresponding first data. For the first data specific time Area Resources and / or is aroundIn a possible implementation, the third DCI may include time domain resource information and / or frequency domain resource information of the fourth DCI.

[0024] In the present application, the time domain resource information and frequency domain resource information of the fourth DCI are dynamically or quasi-statically configured in the third DCI, so that the terminal device can accurately receive the fourth DCI based on the information configured in the third DCI, and then receive the first data based on the fourth DCI.

[0025] In a possible implementation, the time domain resource information of the fourth DCI includes an interval between the time domain resource of the fourth DCI and the time domain resource of the second data, or the time domain resource information of the fourth DCI includes an interval between the time domain resource of the fourth DCI and the time domain resource of the third DCI, and / or the frequency domain resource information of the fourth DCI includes an interval between a frequency domain resource of the fourth DCI and a frequency domain resource of the second data, or the frequency domain resource information of the fourth DCI includes an interval between a time domain resource of the fourth DCI and a frequency domain resource of the third DCI; The interval between the time domain resources is used to determine the time domain resources of the fourth DCI, and the interval between the frequency domain resources is used to determine the frequency domain resources of the fourth DCI.

[0026] In this application, the time domain resource information and / or frequency domain resource information of the fourth DCI is indirectly configured, specifically, the interval between the time domain resource of the fourth DCI and the time domain resource of the second data and / or the interval between the frequency domain resource of the fourth DCI and the frequency domain resource of the second data is set, so that the terminal device can determine the time domain resource and / or the frequency domain resource of the second data based on the interval set in the third DCI and by referring to the time domain resource and / or the frequency domain resource of the second data included in the third DCI. For the 4th DCI specific timeArea Resources and / or is around Optionally, the terminal device may alternatively determine the frequency domain resources based on the intervals set in the third DCI and with reference to the time domain resources and / or frequency domain resources of the third DCI to accurately receive the corresponding fourth DCI. For the 4th DCI specific time Area Resources and / or is around The frequency domain resource may be determined so that the first data can be accurately received based on the fourth DCI.

[0027] In a possible implementation, an interval between a time domain resource for the first data and a time domain resource for the second data; an interval between a time domain resource for the first data and a time domain resource for the third DCI; an interval between the frequency domain resource for the first data and the frequency domain resource for the second data; or an interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI; One or more intervals are predefined, The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0028] In this application, the interval between the time domain resource of the first data and the time domain resource of the second data and / or the interval between the frequency domain resource of the first data and the frequency domain resource of the second data is pre-specified in the protocol, so that the terminal device determines the time domain resource and / or the frequency domain resource of the second data based on the pre-defined interval and with reference to the time domain resource and / or the frequency domain resource of the second data included in the third DCI. For the first data specific time Area Resources and / or is aroundAlternatively, the interval between the time domain resource of the first data and the time domain resource of the third DCI and / or the interval between the frequency domain resource of the first data and the frequency domain resource of the third DCI may be pre-specified in the protocol, so that the terminal device may determine the frequency domain resource based on the pre-defined interval and with reference to the time domain resource and / or the frequency domain resource of the third DCI. For the first data specific time Area Resources and / or is around The wavenumber domain resource can be determined to accurately receive the corresponding first data.

[0029] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0030] In a possible implementation, the first message further includes second indication information, which indicates that the first message includes the first SIB1.

[0031] In this application, the second indication information is carried in the first message (i.e., the RRC message), so that the terminal device can determine the type or version of the first SIB1 included in the first message based on the second indication information, and ensure that the terminal device can correctly perform RRC ASN.1 decoding, which also helps to improve communication reliability.

[0032] In a possible implementation, the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH), the first RLC entity is different from the second RLC entity, or the first LCH is different from the second LCH, the second RLC entity is associated with a second SIB1, and the second LCH is associated with the second SIB1.

[0033] In the present application, the terminal device determines the type or version of the first SIB1 based on the logical channel or RLC entity, so that the terminal device can correctly identify the content contained in the RRC message and correctly perform RRC decoding to obtain accurate information.

[0034] In a possible implementation, the method further includes obtaining third indication information associated with the first message, the third indication information indicating that the first message includes the first SIB1.

[0035] In this application, the terminal device obtains third indication information associated with the first message, and then determines the type or version of the first SIB1 based on the third indication information to ensure that the terminal device can correctly perform RRC ASN.1 decoding.

[0036] In a possible implementation, obtaining the third indication information associated with the first message includes a radio resource control (RRC) layer of the terminal device obtaining the third indication information from a physical (PHY) layer of the terminal device or a medium access control (MAC), radio link control (RLC), or packet data convergence protocol (PDCP) layer of the terminal device.

[0037] In this application, the third indication information may be generated in the physical layer, MAC layer, RLC layer, or PDCP layer of the terminal device and transmitted to an upper layer (e.g., the RRC layer). For example, the third indication information may be included in a newly defined MAC, RLC, or PDCP subheader. The third indication information may be used to determine a decoding scheme in the RRC layer to ensure that the terminal device can correctly perform RRC ASN.1 decoding. This inter-layer interaction mode is diverse, easy to operate, and highly applicable.

[0038] In a possible implementation, the method further includes receiving a master information block MIB from the network device, the MIB including fourth instruction information, the fourth instruction information instructing the network device to transmit the first SIB1.

[0039] In a possible implementation, the third DCI includes fourth instruction information, which instructs the network device to transmit the first SIB1.

[0040] In this application, the terminal device receives the fourth indication information and determines whether the network device should transmit the first SIB1 based on the fourth indication information. In this way, if the terminal device determines that the network device should not transmit the first SIB1, the terminal device no longer needs to monitor the PDCCH corresponding to the first SIB1. This can save the energy of the terminal device.

[0041] According to a third aspect, the present application provides a communication method, applied to a network device, comprising: determining first downlink control information (DCI) used to schedule first data, the first data including a first system information block 1 (SIB1), the first SIB1 including information related to network access in a first operation mode; and transmitting the first DCI to a terminal device, the first DCI including first indication information, the first indication information indicating that the first data includes the first SIB1, or one or more of scrambling information, downlink control information format (DCI format information), time domain resource information, or frequency domain resource information associated with the first DCI being different from that associated with a second DCI, the second DCI being used to schedule a second SIB1, the second SIB1 including information related to network access in a second operation mode.

[0042] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0043] In a possible implementation, the first message further includes second indication information, which indicates that the first message includes the first SIB1.

[0044] In a possible implementation, the method further includes transmitting fourth instruction information to the terminal device instructing the network device to transmit the first SIB1, the fourth instruction information being carried in a master information block MIB or a second DCI.

[0045] In a possible implementation, the method further comprises transmitting the first data to the terminal device.

[0046] According to a fourth aspect, the present application provides a communication method, the method being applied to a network device, the method including: transmitting third downlink control information (DCI) to a terminal device, where the third DCI is used to schedule at least two pieces of data, or the third DCI is used to schedule second data and a fourth DCI, and the fourth DCI is used to schedule first data; and transmitting the first data and second data to the terminal device, where the at least two pieces of data include the first data and the second data, the first data including a first system information block 1 (SIB1) SIB1 and the second data including a second SIB1, where the first SIB1 includes information regarding network access in a first operation mode, and the second SIB1 includes information regarding network access in a second operation mode.

[0047] In a possible implementation, the third DCI includes time domain resource information and / or frequency domain resource information of the first data.

[0048] In a possible implementation, the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the second data, or the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the third DCI, and / or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the second data, or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the third DCI; The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0049] In a possible implementation, the third DCI includes time domain resource information and / or frequency domain resource information of the fourth DCI.

[0050] In the present application, the time domain resource information and frequency domain resource information of the fourth DCI are dynamically or quasi-statically configured in the third DCI, so that the terminal device can accurately receive the fourth DCI based on the information configured in the third DCI, and then receive the first data based on the fourth DCI.

[0051] In a possible implementation, the time domain resource information of the fourth DCI includes an interval between the time domain resource of the fourth DCI and the time domain resource of the second data, or the time domain resource information of the fourth DCI includes an interval between the time domain resource of the fourth DCI and the time domain resource of the third DCI, and / or the frequency domain resource information of the fourth DCI includes an interval between a frequency domain resource of the fourth DCI and a frequency domain resource of the second data, or the frequency domain resource information of the fourth DCI includes an interval between a time domain resource of the fourth DCI and a frequency domain resource of the third DCI; The interval between the time domain resources is used to determine the time domain resources of the fourth DCI, and the interval between the frequency domain resources is used to determine the frequency domain resources of the fourth DCI.

[0052] In this application, the time domain resource information and / or frequency domain resource information of the fourth DCI is indirectly configured, specifically, the interval between the time domain resource of the fourth DCI and the time domain resource of the second data and / or the interval between the frequency domain resource of the fourth DCI and the frequency domain resource of the second data is set, so that the terminal device can determine the time domain resource and / or the frequency domain resource of the second data based on the interval set in the third DCI and by referring to the time domain resource and / or the frequency domain resource of the second data included in the third DCI. For the 4th DCI specific time Area Resources and / or is around Optionally, the terminal device may alternatively determine the frequency domain resources based on the intervals set in the third DCI and with reference to the time domain resources and / or frequency domain resources of the third DCI to accurately receive the corresponding fourth DCI. For the 4th DCI specific time Area Resources and / or is around The frequency domain resource may be determined so that the first data can be accurately received based on the fourth DCI.

[0053] In a possible implementation, an interval between a time domain resource for the first data and a time domain resource for the second data; an interval between a time domain resource for the first data and a time domain resource for the third DCI; an interval between the frequency domain resource for the first data and the frequency domain resource for the second data; or an interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI; One or more intervals are predefined, The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0054] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0055] In a possible implementation, the first message includes second indication information, and the second indication information indicates that the first message includes the first SIB1.

[0056] In a possible implementation, the method further includes transmitting a master information block MIB to the terminal device, the MIB including fourth instruction information, which instructs the network device to transmit the first SIB1.

[0057] In a possible implementation, the third DCI includes fourth instruction information, which instructs the network device to transmit the first SIB1.

[0058] According to a fifth aspect, the present application provides a communication device, which may be a terminal device, comprising: a transceiver unit configured to receive, from a network device, first downlink control information DCI used for scheduling first data; a processing unit configured to determine, based on the first DCI, that the first data includes a first system information block 1 SIB1 including information regarding network access in the first operation mode; The first DCI includes first indication information, which indicates that the first data includes a first SIB1, or one or more of the following information associated with the first DCI, such as scrambling information, downlink control information format DCI format information, time domain resource information, or frequency domain resource information, is different from that associated with a second DCI, which is used to schedule a second SIB1, and the second SIB1 includes information regarding network access in the second operating mode.

[0059] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0060] In a possible implementation, the first message further includes second indication information, which indicates that the first message includes the first SIB1.

[0061] In a possible implementation, the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH), the first RLC entity is different from the second RLC entity, or the first LCH is different from the second LCH, the second RLC entity is associated with a second SIB1, and the second LCH is associated with the second SIB1.

[0062] In a possible implementation, the transceiver unit is further configured to obtain third indication information associated with the first message, the third indication information indicating that the first message includes the first SIB1.

[0063] In a possible implementation, the transceiver unit is particularly configured to obtain the third indication information from a physical PHY layer, a medium access control MAC layer, a radio link control RLC layer or a packet data convergence protocol PDCP layer of the terminal device by a radio resource control RRC layer.

[0064] In a possible implementation, the transceiver unit is further configured to receive fourth instruction information from the network device instructing the network device to transmit the first SIB1, the fourth instruction information being carried in the master information block MIB or the second DCI.

[0065] In a possible implementation, the transceiver unit is further configured to receive first data from the network device based on the first DCI.

[0066] According to a sixth aspect, the present application provides a communications apparatus. The apparatus may be a terminal device, and includes a transceiver unit configured to receive third downlink control information (DCI) from a network device, where the third DCI is used to schedule at least two pieces of data, or the third DCI is used to schedule second data and fourth DCI, and the fourth DCI is used to schedule the first data. The transceiver unit is configured to receive first data and / or second data from the network device based on the third DCI, where the at least two pieces of data include the first data and the second data, where the first data includes a first system information block 1 (SIB1) and the second data includes a second SIB1, where the first SIB1 includes information regarding network access in a first operation mode and the second SIB1 includes information regarding network access in a second operation mode.

[0067] In a possible implementation, the third DCI includes time domain resource information and / or frequency domain resource information of the first data.

[0068] In a possible implementation, the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the second data, or the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the third DCI, and / or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the second data, or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the third DCI; The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0069] In a possible implementation, an interval between a time domain resource for the first data and a time domain resource for the second data; an interval between a time domain resource for the first data and a time domain resource for the third DCI; an interval between the frequency domain resource for the first data and the frequency domain resource for the second data; or an interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI; One or more intervals are predefined, The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0070] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0071] In a possible implementation, the first message further includes second indication information, which indicates that the first message includes the first SIB1.

[0072] In a possible implementation, the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH), the first RLC entity is different from the second RLC entity, or the first LCH is different from the second LCH, the second RLC entity is associated with a second SIB1, and the second LCH is associated with the second SIB1.

[0073] In a possible implementation, the transceiver unit is further configured to obtain third indication information associated with the first message, the third indication information indicating that the first message includes the first SIB1.

[0074] In a possible implementation, the transceiver unit is further configured to obtain third indication information by a radio resource control (RRC) layer from a physical (PHY) layer or a medium access control (MAC), radio link control (RLC), or packet data convergence protocol (PDCP) layer.

[0075] In a possible implementation, the transceiver unit is further configured to receive a master information block MIB from the network device, the MIB including fourth instruction information, the fourth instruction information instructing the network device to transmit the first SIB1.

[0076] In a possible implementation, the third DCI includes fourth instruction information, which instructs the network device to transmit the first SIB1.

[0077] According to a seventh aspect, the present application provides a communications apparatus, which may be a network device, comprising: a processing unit configured to determine first downlink control information DCI used to schedule first data, the first data including a first system information block 1 SIB1, the first SIB1 including information about network access in a first operation mode; a transceiver unit configured to transmit the first DCI to the terminal device; The first DCI includes first indication information, which indicates that the first data includes a first SIB1, or one or more of the following information associated with the first DCI, such as scrambling information, downlink control information format DCI format information, time domain resource information, or frequency domain resource information, is different from that associated with a second DCI, which is used to schedule a second SIB1, and the second SIB1 includes information regarding network access in the second operating mode.

[0078] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0079] In a possible implementation, the first message further includes second indication information, which indicates that the first message includes the first SIB1.

[0080] In a possible implementation, the transceiver unit is further configured to transmit fourth instruction information to the terminal device instructing the network device to transmit the first SIB1, the fourth instruction information being carried in a master information block MIB or a second DCI.

[0081] In a possible implementation, the transceiver unit is further adapted to transmit the first data to the terminal device.

[0082] According to an eighth aspect, the present application provides a communications apparatus. The apparatus may be a network device, and includes a transceiver unit configured to transmit third downlink control information (DCI) to a terminal device, the third DCI being used to schedule at least two pieces of data, or the third DCI being used to schedule second data and fourth DCI, and the fourth DCI being used to schedule first data. The transceiver unit is configured to transmit the first data and second data to the terminal device, the at least two pieces of data including the first data and the second data, the first data including a first system information block 1 (SIB1) SIB1 and the second data including a second SIB1, the first SIB1 including information regarding network access in a first operation mode, and the second SIB1 including information regarding network access in a second operation mode.

[0083] In a possible implementation, the third DCI includes time domain resource information and / or frequency domain resource information of the first data.

[0084] In a possible implementation, the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the second data, or the time domain resource information of the first data includes an interval between the time domain resource for the first data and the time domain resource for the third DCI, and / or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the second data, or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the third DCI; The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0085] In a possible implementation, an interval between a time domain resource for the first data and a time domain resource for the second data; an interval between a time domain resource for the first data and a time domain resource for the third DCI; an interval between the frequency domain resource for the first data and the frequency domain resource for the second data; or an interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI; One or more intervals are predefined, The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0086] In a possible implementation, the first data comprises a first message, and the first message comprises a first SIB1.

[0087] In a possible implementation, the first message includes second indication information, and the second indication information indicates that the first message includes the first SIB1.

[0088] In a possible implementation, the transceiver unit is further configured to transmit a master information block MIB to the terminal device, the MIB including fourth instruction information, the fourth instruction information instructing the network device to transmit the first SIB1.

[0089] In a possible implementation, the third DCI includes fourth instruction information, which instructs the network device to transmit the first SIB1.

[0090] According to a ninth aspect, the present application provides a communication device. The device may be a terminal device, a device within a terminal device, or a device that can be used with a terminal device. Alternatively, the communication device may be a chip system. The communication device may perform a method according to the first or third aspect. The functions of the communication device may be implemented in hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. The units or modules may be software and / or hardware. For operations performed by the communication device and their advantageous effects, please refer to the method according to the first or third aspect and their advantageous effects. Repetitive description will be omitted.

[0091] According to a tenth aspect, the present application provides a communication device. The device may be a network device, a device within a network device, or a device that can be used with a network device. Alternatively, the communication device may be a chip system. The communication device may perform a method according to the second or fourth aspect. The functions of the communication device may be implemented in hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. The units or modules may be software and / or hardware. For operations performed by the communication device and their advantageous effects, please refer to the method according to the second or fourth aspect and their advantageous effects. Repetitive description will be omitted.

[0092] According to an eleventh aspect, the present application provides a communications apparatus, which may be a terminal device, including a processor and a transceiver, the processor and the transceiver being configured to execute computer programs or instructions stored in at least one memory such that the apparatus can perform a method according to either the first or third aspect.

[0093] As another example, a communications device includes a processor, a transceiver, and a memory, the processor, the transceiver, and the memory coupled to each other, the processor and the transceiver configured to perform a method according to either the first aspect or the third aspect.

[0094] According to a twelfth aspect, the present application provides a communications apparatus, which may be a network device, comprising a processor and a transceiver, the processor and the transceiver configured to execute computer programs or instructions stored in at least one memory such that the apparatus can perform a method according to either the second aspect or the fourth aspect.

[0095] As another example, a communications device includes a processor, a transceiver, and a memory, the processor, the transceiver, and the memory coupled to each other, the processor and the transceiver configured to perform a method according to either the second aspect or the fourth aspect.

[0096] According to a thirteenth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program or instructions which, when executed by a computer, perform a method according to any one of the first to fourth aspects.

[0097] According to a fourteenth aspect, the present application provides a computer program product comprising instructions, the computer program product comprising computer program code, which, when executed on a computer, performs a method according to any one of the first to fourth aspects.

[0098] According to a fifteenth aspect, there is provided a chip system, the chip system including a processor and further including a memory, and may implement a method according to any one of the first to fourth aspects or any possible design thereof.

[0099] According to a sixteenth aspect, there is provided a communication system, the communication system including a terminal device according to the ninth aspect and a network device according to the tenth aspect. [Brief explanation of the drawings]

[0100] [Figure 1] A diagram of the network architecture of a 5G system. [Figure 2] FIG. 1 is a diagram of channel mapping. [Figure 3] A diagram showing scheduling of SIB1 and SI messages based on DCI. [Figure 4] FIG. 1 is a diagram of downlink transmission between layers. [Figure 5]1 is a diagram of the structure of a MAC PDU. [Figure 6a] FIG. 2 illustrates a diagram of delivering first data upwards layer by layer by a MAC layer of a terminal device according to an embodiment of the present application. [Figure 6b] 2 is a diagram illustrating first data being delivered by a MAC layer of a terminal device through an RLC layer to an RRC layer according to an embodiment of the present application; [Figure 6c] 1 is a diagram illustrating first data being delivered directly to an RRC layer by a MAC layer of a terminal device according to an embodiment of the present application; [Figure 7a] FIG. 2 illustrates a diagram of delivering first data upwards layer by layer by a PHY layer of a terminal device according to an embodiment of the present application. [Figure 7b] 2 is a diagram illustrating first data being delivered by a PHY layer of a terminal device through an RLC layer to an RRC layer according to an embodiment of the present application; [Figure 7c] 1 is a diagram illustrating first data being delivered directly to an RRC layer by a PHY layer of a terminal device according to an embodiment of the present application; [Figure 8a] FIG. 2 is a diagram illustrating receiving data by a terminal device and performing processing at each layer according to an embodiment of the present application. [Figure 8b] FIG. 10 is another diagram of receiving data by a terminal device and performing processing at each layer according to an embodiment of the present application. [Figure 9] 1 is a schematic flowchart of a communication method according to an embodiment of the present application; [Figure 10] FIG. 2 is a diagram of a scheduling mode according to an embodiment of the present application. [Figure 11] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 12] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 13] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 14] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 15] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 16] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 17] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 18] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 19] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 20] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 21] FIG. 10 is a diagram of another scheduling mode according to an embodiment of the present application. [Figure 22] 4 is another schematic flowchart of a communication method according to an embodiment of the present application; [Figure 23] A diagram of a scenario in which SIB1 is scheduled based on the 6th DCI according to an embodiment of the present application. [Figure 24] A diagram of another scenario in which SIB1 is scheduled based on the 6th DCI according to an embodiment of the present application. [Figure 25] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 26] FIG. 10 is a diagram of the structure of another communication device according to an embodiment of the present application. [Figure 27] FIG. 10 is a diagram of the structure of another communication device according to an embodiment of the present application. [Figure 28] FIG. 2 is a diagram of the structure of another communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0101] The following will clarify the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. sea ​​urchin Write it down.

[0102] In the present description, " / " indicates "or" unless otherwise specified. For example, A / B may indicate A or B. The term "and / or" herein describes only an association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent three cases: only A exists, both A and B exist, and only B exists. Furthermore, "at least one" means one or more, and "multiple" means two or more. Terms such as "first," "second," etc. do not limit the quantity or order of execution, and terms such as "first," "second," etc. do not indicate a clear distinction. In the present description, terms such as "example," "for example," etc. are used to provide an example, illustration, or description. Any embodiment or design scheme described in the present description as "example" or "for example" should not be construed as preferred or advantageous over other embodiments or design schemes. Rather, terms such as "example," "for example," etc. are intended to present the relevant concept in a concrete manner.

[0103] The technical solutions in the embodiments of the present application may be applied to various communication systems, such as, but not limited to, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS) systems, Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) systems or New Radio (NR), and future communication systems.

[0104] For ease of understanding, in the embodiments of the present application, a 5G system is used as an example to describe in detail the network elements related to the present application.

[0105] 1 is a diagram of a network architecture of a 5G system. As shown in FIG. 1, the network architecture may include a terminal device portion, a (radio) access network ((R)AN), a core network (CN), and a data network (DN). The (R)AN (hereinafter referred to as RAN) is configured to connect terminal devices to a radio network, and the CN is configured to manage terminal devices and provide a gateway for communication with the DN.

[0106] The following describes in detail the terminal device, RAN, CN, and DN in FIG. 1 separately.

[0107] 1. Terminal Device

[0108] Terminal devices include devices that provide voice and / or data connectivity to users and may include, for example, portable devices with wireless communication capabilities or processing devices connected to wireless modems. Terminal devices may communicate with a core network through a radio access network. Terminal devices may include user equipment (UE), wireless terminal devices, mobile terminal devices, device-to-device (D2D) communication terminal devices, vehicle-to-everything (V2X) terminal devices, machine-to-machine / machine-type communications (M2M / MTC) terminal devices, internet of things (IoT) terminal devices, subscriber units, subscriber stations, mobile stations, remote stations, access points (APs), remote terminals, access terminals, user terminals, user agents, user devices, etc. For example, a terminal device may include a mobile telephone (also called a "cellular" telephone), a computer with a mobile terminal device, or a portable, packet-sized, handheld, or computer-embedded mobile device, such as a personal communication service (PCS) telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or other device. Terminal devices may also include limited devices, such as low power devices, devices with limited storage capacity, or devices with limited computing power.

[0109] 2.RAN

[0110] The RAN may include one or more RAN devices (i.e., access network devices), and the interface between the access network device and the terminal device may be a Uu interface (also called an air interface). Indeed, in future communications, the names of these interfaces may remain unchanged or may be replaced by other names, which is not a limitation of the present application.

[0111] An access network device is a node or device that connects a terminal device to a wireless network. For example, an access network device may include, but is not limited to, a next-generation NodeB (gNB), an evolved NodeB (eNB), a next-generation evolved NodeB (ng-eNB), a wireless backhaul device, a radio network controller (RNC), a NodeB (NodeB, NB), a base station controller (BSC), a base transceiver station (BTS), a home evolved NodeB (HeNB) or home NodeB (HNB), a baseband unit (BBU), a transmitting and receiving point (TRP), a transmitting point (TP), and a mobile switching center in a 5G communication system.

[0112] 3.CN

[0113] The CN may include one or more CN devices. A 5G communication system is used as an example. The CN may include an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, an application function (AF) network element, etc.

[0114] The AMF network element is a control plane network element provided by an operator network, and is responsible for access control and mobility management for terminal devices to access the operator network. For example, the AMF network element includes functions such as mobility status management, temporary user identity allocation, user authorization and authentication, etc.

[0115] The SMF network element is a control plane network element provided by the operator network and is responsible for managing PDU sessions of terminal devices. A PDU session is a channel for transmitting PDUs. The terminal device and the DN need to transmit PDUs to each other using PDU sessions. The SMF network element is responsible for establishing, maintaining, deleting, etc. the PDU sessions. The SMF network element includes session-related functions such as session management (e.g., session establishment, modification, and versioning, including tunnel maintenance between the UPF and the RAN), selection and control of UPF network elements, service and session continuity (SSC) mode selection, roaming, etc.

[0116] The UPF network element is a gateway provided by an operator for communication between the operator network and the DN, and includes user plane related functions such as data packet routing and transmission, packet detection, quality of service (QoS) processing, lawful interception, uplink packet detection, and downlink data packet storage.

[0117] The PCF network element is a control plane function provided by an operator and is configured to provide PDU session policies to the SMF network element, which may include charging-related policies, QoS-related policies, authentication-related policies, etc.

[0118] The AF network element is a functional network element that provides various business services, interacts with the core network through other network elements, and can interact with the policy management framework to perform policy management.

[0119] Additionally, although not shown, the CN may further include other possible network elements, such as a network exposure function (NEF) network element or a unified data repository (UDR) network element.

[0120] It should be noted that in the embodiments of the present application, the access network devices and the core network devices may be collectively referred to as network devices.

[0121] 4.DN

[0122] A DN, sometimes called a packet data network (PDN), is a network that spans an operator network. An operator network may have access to multiple DNs. Application services corresponding to multiple services may be deployed in the DN to provide multiple possible services to a terminal device.

[0123] Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 in Figure 1 are interface sequence numbers. The meanings of these interface sequence numbers should be referred to as defined in the relevant standard protocols, and are not limited here.

[0124] It may be understood that a 5G communication system is used as an example for illustration in FIG. 1 , and the solutions in the embodiments of the present application are also applicable to other possible communication systems, such as an LTE communication system or a future sixth generation (6G) communication system. Each of the above network elements or functions may be a hardware device, a software function executed on dedicated hardware, or a virtual function instantiated on a platform (e.g., a cloud platform). Optionally, each of the above network elements or functions may be implemented by one device, or may be implemented together by multiple devices, or may be a functional module within a device. This is not particularly limited in the embodiments of the present application.

[0125] The following describes relevant technical features in the embodiments of the present application, which are provided for the purpose of facilitating understanding of the embodiments of the present application and should not be construed as limiting the scope of protection claimed in the present application.

[0126] 1. System Information (SI)

[0127] Currently, an SI may include a master information block (MIB) and several system information blocks (SIB). SI may be divided into two categories: minimum SI (MSI) and other SI (mOSI).

[0128] The MSI contains basic information used for initial access and information used to obtain the OSI. A UE needs to receive MIB and SIB1 from a cell to access, or camp on, a cell. The MSI includes MIB and SIB1. The MIB contains the cell's barring status information and basic physical layer information of the cell, such as CORESET#0, used to receive further system information. The MIB is periodically broadcast on the broadcast channel (BCH). The SIB1 defines the scheduling of other types of system information blocks and contains information used for initial access. The SIB1, sometimes referred to as the Remaining Minimum SI (RMSI), is periodically broadcast on the downlink shared channel (DL-SCH) or transmitted to a connected UE on the DL-SCH using dedicated signaling.

[0129] The OSI includes SIBs other than SIB1, such as SIB2 to SIB14, and potentially additional SIBs that may be expanded in the future. These SIBs may be broadcast periodically on the DL-SCH, broadcast on an on-demand basis on the DL-SCH, or transmitted to connected UEs on the DL-SCH using dedicated signaling. Note that for the OSI, SIBs with the same periodicity may be mapped to one SI message for transmission. For example, Figure 2 is a channel mapping diagram. As shown in Figure 2, the logical, transport, and physical channels currently corresponding to the MIB are the broadcast control channel (BCCH), the broadcast channel (BCH), and the physical broadcast channel (PBCH), respectively. Currently, the logical, transport, and physical channels corresponding to the SIB1 or SI message are the BCCH, the downlink shared channel (DL-SCH), and the physical downlink shared channel (PDSCH), respectively.

[0130] 2.SIB1

[0131] Currently, even if a network device supports multiple protocol version capabilities, the network device supports only one SIB1. Specifically, in a cell, the network device transmits only one SIB1, and all UEs receiving SIB1 in the cell receive the same SIB1 regardless of whether the protocol versions supported by the UEs are the same. Note that the fact that the network device transmits only one SIB1 does not mean that SIB1 remains unchanged at all times. SIB1 may change. This can be understood as the network device transmitting only one SIB1 within a certain period (e.g., within the period of SIB1).

[0132] 3. Downlink control information (DCI) for scheduling SIB1

[0133] Currently, SIB1 is transmitted on a PDSCH, and the PDSCH for transmitting SIB1 is scheduled by a DCI that is scrambled by using a system information radio network temporary identity (SI-RNTI). Furthermore, the format of the DCI for scheduling SIB1 is the same as the format of the DCI for scheduling an SI message (specifically, both are DCI format 1_0 in the current NR protocol), and the scrambling information of the DCI for scheduling SIB1 is the same as the scrambling information of the DCI for scheduling an SI message (specifically, both are SI-RNTI in the current NR protocol, and only one value of SI-RNTI is supported, which is FFFF). The length of the SI-RNTI is 16 bits. Furthermore, in NR, the transmission of SIB1 may collide with the transmission of an SI message in the time domain. Specifically, the DCI for scheduling SIB1 may collide with the DCI for scheduling an SI message in the time domain. For example, from a protocol perspective, the search spaces for SIB1 and SI messages (i.e., other system information) are configured separately. The UE's determination of an occasion for monitoring the PDCCH based on the search space configuration can be understood as the UE's determination of a time domain resource from which the UE can obtain SIB1 or SI messages through monitoring based on the search space configuration. Note that collision can also be understood as overlap in this application. Here, DCI scrambled by using SI-RNTI is used to schedule SIB1 or SI messages, and one bit in the DCI (specifically, a system information indicator field in the NR protocol) indicates whether the DCI schedules SIB1 or SI messages.

[0134] For example, Figure 3 is a diagram of scheduling SIB1 and SI messages based on DCI. As shown in Figure 3, the network device separately schedules SIB1 and SI messages by using two DCIs, or the network device separately schedules data corresponding to SIB1 and data corresponding to SI messages by using two DCIs. The formats of the two DCIs are the same. The scrambling information of the two DCIs is the same, and both are SI-RNTI. After receiving the two DCIs, the UE may determine whether the DCI schedules SIB1 or SI messages based on the system information indicator in the DCI.

[0135] It should be noted that, for the reception of SIB1 and SI messages, the transmission of SIB1 may collide with the transmission of SI messages in time; the scrambling information and DCI format of the DCI corresponding to SIB1 are the same as those of the DCI corresponding to SI messages; the DCI for scheduling SIB1 and the DCI for scheduling SI messages do not include HARQ process ID information; and for the reception of SIB1 and SI messages, the MAC layer of the UE supports HARQ joint decoding. Therefore, whether the DCI is scheduling SIB1 or an SI message needs to be indicated in the DCI. If the indication is not included, the UE may erroneously perform HARQ joint decoding on SIB1 and SI messages that are received separately, which may result in a decoding error.

[0136] In LTE, SIB1 and SI messages are transmitted separately in the time domain. Therefore, in LTE, one SI-RNTI is still used to schedule SIB1 and SI messages, but the UE may determine whether SIB1 or SI messages are received based on the time domain information (e.g., search space) of the DCI. Therefore, in LTE, it is not necessary for the DCI to indicate whether it is scheduling SIB1 or SI messages.

[0137] In NR, for the transmission of different SI messages, the SI windows of SIB messages are non-overlapping and separated in the time domain. Therefore, when a UE receives two DCIs scrambled by using the SI-RNTI and both indicate that the DCIs schedule SI messages, the UE may determine whether the SI messages scheduled by the two DCIs are the same SI message based on the time domain resource on which the DCIs are monitored (e.g., based on whether the two DCIs belong to the same SI window). If the SI messages scheduled by the two DCIs are the same SI message, HARQ joint decoding may be performed on data corresponding to the newly received DCI and previously received data. If the SI messages scheduled by the two DCIs are different SI messages, HARQ decoding needs to be performed separately on the data corresponding to the newly received DCI.

[0138] 4. MAC layer processing and RLC layer processing corresponding to SIB1

[0139] Currently, the control plane protocol stack may include a NAS, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer (PHY). The user plane protocol stack may include a service data adaptation protocol (SDAP) layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer.

[0140] Figure 4 is a diagram of downlink transmission between layers. In Figure 4, a downward arrow indicates transmission and an upward arrow indicates reception. After generating signaling to be transmitted (e.g., an RRC message or an RRC PDU), the RRC layer of the access network device may deliver the signaling to a corresponding PDCP entity. For ease of description, signaling may be referred to as or substituted with data hereinafter. For data (e.g., PDCP SDUs) received from the RRC layer, the PDCP entity may obtain the PDCP PDU with or without specific processing, and then deliver the PDCP PDU to an RLC entity corresponding to the PDCP entity. For data (e.g., RLC SDUs) received from the PDCP layer, the RLC entity may obtain the RLC PDU with or without specific processing, and then deliver the RLC PDU to a corresponding MAC entity. For data (e.g., MAC SDUs) received from the RLC layer, the MAC entity may obtain the MAC PDU with or without specific processing and then deliver the MAC PDU to the PHY layer. The PHY layer performs transmission over the air interface. Correspondingly, after receiving data (e.g., a transport block (TB)), the PHY layer of the terminal device delivers the TB to the MAC layer. For data (e.g., TB or MAC PDUs) received from the PHY, the MAC entity may obtain the MAC SDU with or without specific processing and then deliver the MAC SDU to the corresponding RLC layer. For data (e.g., RLC PDUs) received from the MAC layer, the RLC entity may obtain the RLC SDU with or without specific processing and then deliver the RLC SDU to the corresponding PDCP entity. For data (e.g., PDCP PDUs) received from the RLC layer, the PDCP entity may obtain the PDCP SDU with or without specific processing and then deliver the PDCP SDU to the RRC layer.For data received from the PDCP layer (e.g., RRC messages or RRC PDUs), which may also be referred to as signaling, the RRC layer performs RRC decoding or ASN.1 decoding to determine the meaning of the received data (e.g., bit strings).

[0141] For transmission or reception of data (or signaling), the data may be encapsulated / processed at each layer accordingly, or transmitted transparently. For example, for transmission, data received by a layer from its upper layer is called a service data unit (SDU), and data delivered by a layer to a lower layer is called a protocol data unit (PDU). For a layer, the data received from the upper layer and the data delivered to the lower layer may be the same (e.g., the data is transmitted transparently) or may be different (e.g., the data delivered to the lower layer is obtained at that layer by encapsulating / processing the data received from the upper layer). For example, data received by a PDCP entity from a higher layer is called a PDCP SDU, data transmitted by a PDCP entity to a lower layer is called a PDCP PDU, data received by an RLC entity from a higher layer is called an RLC SDU, data transmitted by an RLC entity to a lower layer is called an RLC PDU, data received by a MAC entity from a higher layer is called a MAC SDU, and data transmitted by a MAC entity to a lower layer is called a MAC PDU. For example, for reception, data received by a layer from its lower layer is called a PDU, and data delivered by a layer to a higher layer is called an SDU. For a layer, the data received from the lower layer and the data delivered to the higher layer may be the same (e.g., the data is transmitted transparently) or may be different (e.g., the data delivered to the higher layer is obtained at that layer by processing the data received from the lower layer).For example, data received by a PDCP entity from a lower layer is called a PDCP PDU, data transmitted by a PDCP entity to a higher layer is called a PDCP SDU, data received by an RLC entity from a lower layer is called an RLC PDU, data transmitted by an RLC entity to a higher layer is called an RLC SDU, data received by a MAC entity from a lower layer is called a MAC PDU, and data transmitted by a MAC entity to a higher layer is called a MAC SDU.

[0142] The upper layer and the lower layer in the embodiments of the present application are relative concepts. For example, the RLC layer is used as an example. In the case of the RRC layer, the RLC layer is a layer lower than the RRC layer. However, in the case of the MAC layer, the RLC layer is a layer higher than the MAC layer. As another example, the layer lower than the RRC layer may include any one or more of the following: a PHY layer, a MAC layer, an RLC layer, and a PDCP layer.

[0143] It should be noted that data (or signaling) is not necessarily transmitted or received through all of the above layers, for example, SIB1 and SI messages may not currently be transmitted through the PDCP layer.

[0144] It should be noted that for the RLC layer, there may be multiple transmission modes, such as TM, which is currently used at the RLC layer for the transmission of SIB1 and SI messages.

[0145] 5 is a diagram of a MAC PDU structure. As shown in FIG. 5, in this embodiment of the present application, the MAC PDU format corresponding to the logical channel (i.e., BCCH) and transport channel (i.e., DL-SCH) for SIB1 is transparent MAC. In other words, a MAC PDU can be used for transmission mapped from BCCH to DL-SCH. Specifically, one MAC PDU contains only one MAC SDU, and the MAC SDU is the same as the MAC PDU.

[0146] It should be noted that currently, for the transmission of SIB1 and SI messages, the UE processes the received data (e.g., TB) by using a HARQ process corresponding to broadcast. If the data is newly transmitted, the UE attempts to decode the received data. If the data is retransmitted, the UE attempts to perform decoding. If the UE successfully performs decoding, the UE delivers the decoded MAC PDU or MAC SDU to the RLC layer. Because the MAC PDU format corresponding to SIB1 is transparent MAC, the content of the MAC PDU is the same as that of the MAC SDU, and the MAC PDU does not need to be disassembled or demultiplexed.

[0147] As shown in Figure 4, the transmission mode at the RLC layer may be TM. Specifically, TM is used at the RLC layer for BCCH-related transmission. After receiving data (RLC PDU) from the MAC layer of the UE, the RLC layer of the UE delivers the RLC PDU or RLC SDU to the RRC layer without any processing.

[0148] It should be noted that data or signaling (e.g., data corresponding to or including SIB1) has different names at different layers within the protocol, e.g., data or signaling is called a TB at the physical layer, a MAC PDU or MAC SDU at the MAC layer, an RLC PDU or RLC SDU at the RLC layer, a PDCP PDU or PDCP SDU at the PDCP layer, and an RRC signaling, RRC message, or RRC PDU at the RRC layer.

[0149] 5. Abstract Syntax Notation One (ASN.1) corresponding to SIB1

[0150] Currently, the logical channel (BCCH) and transport channel (DL-SCH) corresponding to SIB1 are the same as those corresponding to SI messages. A message (e.g., an RRC message, an RRC PDU, an RRC message set, or an RRC message class) corresponding to the logical channel (BCCH) or the transport channel (DL-SCH), or a message (e.g., an RRC message, an RRC PDU, an RRC message set, or an RRC message class (e.g., a class)) transmitted on the logical channel (BCCH) or the transport channel (DC-SCH) may be a broadcast control channel-downlink shared channel-message (BCCH-DL-SCH-Message). The message structure of the BCCH-DL-SCH-Message or the BCCH-DL-SCH-Message may include indication information to indicate whether the BCCH-DL-SCH-Message contains SIB1 or an SI message, so that the UE can accurately perform RRC decoding or ASN.1 decoding. For example, the UE receives a DCI scrambled by using the SI-RNTI, and the DCI indicates that the data or PDSCH scheduled by the DCI is or includes SIB1. The MAC layer of the UE performs decoding (HARQ joint decoding may be performed). After successfully decoding the data scheduled by the DCI scrambled by using the SI-RNTI, the MAC layer of the UE delivers the data to the RRC layer of the UE. The RRC layer of the UE determines that the received RRC message, RRC PDU, RRC message set, or RRC message class includes SIB1 based on the indication information in the received RRC message, RRC PDU, RRC message set, or RRC message class. The UE may decode each bit in the received RRC message based on the ASN.1 of SIB1 to obtain accurate information.It should be noted that the delivery of data to the RRC layer of the UE can be understood as follows: the MAC layer of the UE delivers data to the RLC layer of the UE, and the RLC layer of the UE delivers data to the RRC layer of the UE.

[0151] 6.SI Message

[0152] Currently, multiple SIBs with the same periodicity may be mapped to one SI message. A system information message or a message definition of a system information message may include indication information to indicate a specific SIB included in an RRC message, an SI message, or an RRC PDU, so that the UE can perform RRC decoding or ASN.1 decoding.

[0153] 7.DCI Format

[0154] Different DCI formats may correspond to different functions. Different DCI formats may correspond to different RNTIs.

[0155] 8.SIB1 full configuration and delta configuration

[0156] Full configuration is a full or complete configuration mode, where configuration in this mode may waste resources. Delta configuration is a partial configuration mode, where new and / or upgraded parts of a later version relative to a base version are primarily configured. For example, a terminal device may combine a base version SIB1 with a delta configuration of a later version SIB1 to obtain a complete SIB1 of the later version.

[0157] 9. Control resource set (CORESET)

[0158] CORESET may indicate the frequency domain resources of the control channel and / or the length of symbols occupied in the time domain, where the symbols may be orthogonal frequency division multiplexing (OFDM) symbols.

[0159] 10.Search space (SS)

[0160] The search space may indicate time-domain resource information of a control channel, which may be a physical downlink control channel (PDCCH). The search space may include a common search space (CSS) or a user-specific search space (USS). The common search space may include a search space corresponding to SIB1, a search space corresponding to paging, a search space corresponding to other system information, a search space corresponding to random access, etc.

[0161] It should be noted that a terminal device may transmit a service by establishing a connection to a network device. Typically, a terminal device may obtain information about accessible networks by receiving SIB1 from the network device. However, in some cases, a terminal device may fail to access a network. For example, if a terminal device is incompatible with a network device because the network device has been successfully upgraded but the terminal device has failed to upgrade or cannot be upgraded, the terminal device may not correctly receive, parse, or decode the SIB1 sent by the network device, and thus cannot access the network. For example, in an Internet of Things (IoT) scenario, there are many terminal devices, and these terminal devices are characterized by long online times and difficulty in upgrading. If compatibility issues occur in the terminal devices or the network in this scenario, many terminal devices may be unable to access the network, resulting in service failure. Therefore, how to solve the problem of low communication reliability due to terminal devices being unable to (normally) access the network or (accurately) perform communication has become one of the current urgent problems that need to be solved.

[0162] Based on this, an embodiment of the present application provides a communication method, in which communication reliability can be improved. It should be noted that the solution of the present application is applicable to all scenarios in which two or more SIB1s need to be transmitted, and the solution regarding how to correctly perform HARQ combining in the MAC layer and how to correctly perform decoding in the RRC layer is universal. Furthermore, all access-related information in the present application is described using SIB1s. However, the name of SIB1 is not limited in the present application. Specifically, the solution of the present application is applicable to the transmission of access-related information. For example, SIB1 in the present application may be replaced with or understood as information.

[0163] It should be noted that in the embodiments of the present application, time domain resources for DCI may be understood as time domain resources corresponding to DCI, frequency domain resources for DCI may be understood as frequency domain resources corresponding to DCI, DCI content resources may be understood as resources corresponding to DCI, time domain resources for data may be understood as time domain resources corresponding to data, frequency domain resources for data may be understood as frequency domain resources corresponding to data, and resources for data may be understood as resources corresponding to data. In the embodiments of the present application, scrambling information of DCI may be understood as scrambling information corresponding to DCI, format information of DCI may be understood as format information corresponding to DCI, time domain resource information of DCI may be understood as time domain resource information corresponding to DCI, and frequency domain resource information of DCI may be understood as frequency domain resource information corresponding to DCI.

[0164] It should be noted that in the embodiments of the present application, the DCI may schedule data transmitted in a PDSCH, a TB, a MAC PDU, etc. This is not a limitation hereof. For example, the Xth data (e.g., one or more of the first data, the second data, the third data, or the fourth data) in the embodiments of the present application may be data transmitted in a PDSCH, a TB, or a MAC PDU. This is not a limitation hereof. Therefore, the scheduling information included in the DCI may be understood as scheduling information for data, for example, resource information corresponding to the data. Furthermore, since the data includes SIB1, the DCI including scheduling information for data may also be described as the DCI including scheduling information for SIB1 in the embodiments of the present application. In describing an SI message, the DCI used to schedule the SI message may also be described as the DCI used to schedule the third data, where the third data includes the SI message. In describing an SIB1 set, the DCI used to schedule the SIB1 set may also be described as the DCI used to schedule the fourth data, where the fourth data includes the SIB1 set.

[0165] The DCI used to schedule the first SIB1 may also be described as a DCI used to schedule first data, where the first data includes the first SIB1. Correspondingly, the DCI used to schedule the second SIB1 may also be described as a DCI used to schedule second data, where the second data includes the second SIB1. Specifically, in an embodiment of the present application, "the first DCI schedules the first data, and the first data includes the first SIB1" may also be described as "the first DCI is used to schedule the first SIB1." Correspondingly, in an embodiment of the present application, "the second DCI schedules the second data, and the second data includes the second SIB1" may also be described as "the second DCI is used to schedule the second SIB1." Furthermore, in the following description of an SI message, a DCI used to schedule an SI message may also be described as a DCI used to schedule third data, where the third data includes the SI message, and in the description of an SIB1 set, a DCI used to schedule the SIB1 set may also be described as a DCI used to schedule fourth data, where the fourth data includes the SIB1 set, etc. This is not limited here.

[0166] It should be noted that in the embodiments of the present application, a "time domain resource for a DCI" may be understood as a range of time domain resources for the DCI, a search space corresponding to the DCI, a range of time domain resources for which a terminal device monitors the DCI, or a time domain resource in which the DCI may exist or appear. For example, the network device may separately configure a search space corresponding to the DCI used to schedule the first SIB1 and a search space corresponding to the DCI used to schedule the second SIB1, and the terminal device receives one or two of the two search space configurations. Alternatively, the network device may configure a search space configuration parameter corresponding to the DCI used to schedule the first SIB1 and a search space configuration parameter corresponding to the DCI used to schedule the second SIB1, and the terminal device receives the search space configuration parameter and determines the search space corresponding to the DCI used to schedule the first SIB1 and the search space corresponding to the DCI used to schedule the second SIB1 according to a predefined or protocol-specified method. This is not a limitation of the present application.

[0167] Note that in the embodiments of the present application, a "frequency domain resource for a DCI" may be understood as a range of frequency domain resources for the DCI, a control resource set corresponding to the DCI, a range of frequency domain resources for which a terminal device monitors the DCI, or a frequency domain resource on which the DCI may exist or appear. For example, the network device may separately configure a control resource set corresponding to the DCI used to schedule the first SIB1 and a control resource set corresponding to the DCI used to schedule the second SIB1, and the terminal device may receive one or two of the two control resource set configurations. Alternatively, the network device may configure a control resource set configuration parameter corresponding to the DCI used to schedule the first SIB1 and a control resource set configuration parameter corresponding to the DCI used to schedule the second SIB1, and the terminal device receives the control resource set configuration parameter and determines the control resource set corresponding to the DCI used to schedule the first SIB1 and the control resource set corresponding to the DCI used to schedule the second SIB1 according to a predefined or protocol-specified method. This is not a limitation of the present application.

[0168] It should be noted that the monitoring occasion or search space for the DCI used to schedule the first SIB1 and the monitoring occasion or search space for the DCI used to schedule the second SIB1 may be predefined in a protocol or may be determined according to a predetermined rule. For example, the entire search space for the DCI used to schedule the first SIB1 and the DCI used to schedule the second SIB1 may be a common search space indicated by the MIB. A part of the common search space corresponds to the DCI used to schedule the first SIB1, and a part of the common search space corresponds to the DCI used to schedule the second SIB1. This is not limited here.

[0169] It should be noted that in the embodiments of the present application, "different time domain resources" may be understood as time domain resources that do not overlap, and "same time domain resources" may be understood as time domain resources that are partially or completely the same, or time domain resources that partially or completely overlap, and are not limited to being completely the same. Accordingly, for an understanding of "different frequency domains" and "same frequency domains," please refer to the descriptions of "different time domains" and "same time domains," with the proviso that "time domain" is replaced with "frequency domain." Details will not be described again here. The DCI in the present application may be understood as a PDCCH. In the embodiments of the present application, "the terminal device determines, based on the first data, that the first data includes the first SIB1" may be understood as follows: the terminal device determines, based on the first data, that the first message includes the first SIB1; alternatively, the terminal device determines, based on the first message, that the first message includes the first SIB1. Correspondingly, "the terminal device determines, based on the second data, that the second data includes the second SIB1" can be understood as follows: the terminal device determines, based on the second data, that the second message includes the second SIB1, or alternatively, the terminal device determines, based on the second message, that the second message includes the second SIB1. Correspondingly, "the terminal device determines, based on the fourth data, that the fourth data includes the SIB1 set" can be understood as follows: the terminal device determines, based on the fourth data, that the fourth message includes the SIB1 set, or alternatively, the terminal device determines, based on the fourth message, that the fourth message includes the SIB1 set.

[0170] It should be noted that in the embodiment of the present application, the first data may include the first message, or the first message may be the same as the first data, in which case the first message includes the first SIB1. Correspondingly, the second data may include the second message, or the second message may be the same as the second data, in which case the second message includes the second SIB1. Correspondingly, the third message may be a message included in the third data, in other words, the third data may include the third message, or the third message may be the same as the third data, in which case the third message includes the SI message.

[0171] It should be noted that the first data including the first message can be understood as follows: (1) Note that the first data is associated with the first message, and the first message is obtained based on the first data. For example, the first message is obtained by a specific process in the process in which the MAC layer of the terminal device delivers all or part of the first data to the RRC layer through another layer. In this case, the bits of the first message may not match the bits of the first data. For example, an example in which the length of the first data is 100 bits is used for the description, and the values ​​of the bits of the first data are all 0. The length of the first message may be 90 bits, and the values ​​of the bits of the first message are all 0. (2) The first data includes the bits of the first message. For example, an example in which the length of the first data is 100 bits is used for the description, and the values ​​of the bits of the first data are all 0. The length of the first message may be 90 bits, and the values ​​of the bits of the first message are all 0. For example, the first message is the 90 least significant bits of the first data. Whether the bit value of the first data is the same as that of the first message is not limited in the present application.

[0172] The understanding that the second data includes the second message may be the same as the understanding that the first data includes the first message, provided that "first" in the above related descriptions is replaced with "second". Details will not be described again here. Correspondingly, the understanding that the third data includes the third message may be the same as the understanding that the first data includes the first message, provided that "first" in the above related descriptions is replaced with "third". Details will not be described again here. Correspondingly, the understanding that the fourth data includes the fourth message may be the same as the understanding that the first data includes the first message, provided that "first" in the above related descriptions is replaced with "fourth". Details will not be described again here.

[0173] It should be noted that for the RRC layer, data received from a lower layer may typically be referred to as a message, an RRC message, an RRC PDU, an RRC message set, an RRC message class, etc. This is not limited thereto. For example, for the RRC layer, data received from a lower layer (e.g., first data) may be referred to as a first RRC message, a first RRC PDU, a first RRC message set, or a first RRC message class. As another example, for the RRC layer, data received from a lower layer (e.g., second data) may be referred to as a second RRC message, a second RRC PDU, a second RRC message set, or a second RRC message class. As another example, for the RRC layer, data received from a lower layer (e.g., third data) may be referred to as a third RRC message, a third RRC PDU, a third RRC message set, or a third RRC message class. As another example, for the RRC layer, the data received from a lower layer (eg, the fourth data) may be referred to as a fourth RRC message, a fourth RRC PDU, a fourth RRC message set, or a fourth RRC message class.

[0174] It should be noted that "all or a part of the first data" in this application may be understood as the first MAC PDU or the first MAC SDU. For example, the first data is the first MAC PDU. When possible, the MAC PDU format corresponding to the logical channel and the transport channel corresponding to the first SIB1 is transparent MAC. Therefore, the first MAC PDU is the same as the first MAC SDU, and the MAC layer of the terminal device needs to deliver all of the first data (i.e., the first MAC PDU or the first MAC SDU) to the RRC layer for decoding. As another example, the first data is the first MAC PDU. When possible, the MAC PDU format corresponding to the logical channel and the transport channel corresponding to the first SIB1 is not transparent MAC. Therefore, the first MAC PDU is different from the first MAC SDU, and the MAC layer of the terminal device needs to deliver only a part of the first data (i.e., the first MAC SDU) to the RRC layer for decoding. For ease of description, in this application, "all or a part of the first data" may be described as "first data." Similarly, for understanding all or part of the second data, third data, or fourth data, please refer to the above description of all or part of the first data, provided that "first" is replaced with "second," "third," or "fourth." Details will not be described again here.

[0175] It should be noted that all or part of the first data delivered by the MAC layer or PHY layer of the terminal device may be the same as or different from the first message received by the RRC layer of the terminal device. For example, all or part of the first data may be delivered directly to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device. As another example, all or part of the first data may be transmitted transparently by the MAC layer or PHY layer of the terminal device to the RRC layer of the terminal device through another example. As another example, all or part of the first data may be delivered to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device after being processed by another layer.

[0176] It should be noted that in this application, the delivery of data or indication information to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device can be understood as follows: the data or indication information may be delivered directly to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device, or the data or indication information may be transmitted transparently to the RRC layer of the terminal device through another layer by the MAC layer or PHY layer of the terminal device, or the data or indication information may be delivered to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device after being processed by another layer.

[0177] For example, the first data being delivered to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device can be understood as follows: the first data may be directly delivered to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device, or the first data may be transparently transmitted to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device through another layer, or the first data may be delivered to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device after being processed by another layer. Similarly, for understanding that the second data, third data, or fourth data are delivered to the RRC layer of the terminal device by the MAC layer or PHY layer of the terminal device, please refer to the description of the first data, with the proviso that "first" is replaced with "second," "third," or "fourth." Details will not be described again here. Similarly, for understanding that the third indication information or the seventh indication information is delivered to the RRC layer of the terminal device by the MAC layer or the PHY layer of the terminal device, please refer to the description of the first data, provided that the "first data" is replaced with the "third indication information" or the "seventh indication information". Details will not be described again here.

[0178] For example, the MAC layer of the terminal device delivering the first data to the RRC layer can be understood as follows: the MAC layer of the terminal device delivers the first data to the RLC layer of the terminal device, the RLC layer delivers the first data to the PDCP layer, and the PDCP layer then delivers the first data to the RRC layer. That is, the MAC layer of the terminal device delivers the first data upwards layer by layer (e.g., FIG. 6a is a diagram showing the MAC layer of the terminal device delivering the first data upwards layer by layer according to an embodiment of the present application). Alternatively, the MAC layer of the terminal device delivering the first data to the RRC layer can be understood as follows: the MAC layer of the terminal device delivers the first data to the RRC layer of the terminal device through either the RLC layer or the PDCP layer (e.g., FIG. 6b is a diagram showing the MAC layer of the terminal device delivering the first data to the RRC layer through the RLC layer according to an embodiment of the present application). Alternatively, the MAC layer of the terminal device delivering the first data to the RRC layer may be understood as follows: the MAC layer of the terminal device directly delivers the first data to the RRC layer of the terminal device (for example, FIG. 6c is a diagram showing the MAC layer of the terminal device directly delivering the first data to the RRC layer according to an embodiment of the present application). This is specifically determined based on an actual scenario and is not limited here.

[0179] As another example, the PHY layer of the terminal device delivering the first data to the RRC layer can be understood as follows: the PHY layer of the terminal device delivers the first data to the MAC layer of the terminal device, the MAC layer of the terminal device delivers the first data to the RLC layer of the terminal device, then the RLC layer delivers the first data to the PDCP layer, and finally the PDCP layer delivers the first data to the RRC layer. That is, the PHY layer of the terminal device delivers the first data upwards layer by layer (e.g., FIG. 7a is a diagram showing the PHY layer of the terminal device delivering the first data upwards layer by layer according to an embodiment of the present application). Alternatively, the PHY layer of the terminal device delivering the first data to the RRC layer can be understood as follows: the PHY layer of the terminal device delivers the first data to the RRC layer of the terminal device through any one or two of the MAC layer, the RLC layer, and the PDCP layer (e.g., FIG. 7b is a diagram showing the PHY layer of the terminal device delivering the first data to the RRC layer through the RLC layer according to an embodiment of the present application). Alternatively, the PHY layer of the terminal device delivering the first data to the RRC layer may be understood as follows: the PHY layer of the terminal device directly delivers the first data to the RRC layer of the terminal device (for example, FIG. 7c is a diagram showing the PHY layer of the terminal device directly delivering the first data to the RRC layer according to an embodiment of the present application). This is specifically determined based on an actual scenario and is not limited here.

[0180] In order to facilitate understanding of the different descriptions at different layers of data scheduled by DCI in the embodiment of the present application, the following will be further described with reference to Figures 8a and 8b.

[0181] 8a is a diagram illustrating data reception by a terminal device and processing performed at each layer according to an embodiment of the present application. As shown in FIG. 8a, the terminal device receives first data, which is a first MAC PDU. The MAC layer may obtain the first MAC SDU directly or through specific processing (e.g., disassembly and multiplexing), and the first MAC PDU may be the same as or different from the first MAC SDU. The MAC layer delivers the first MAC SDU to the RLC layer. The RLC layer receives the first RLC PDU, and the RLC layer may obtain the first RLC SDU directly (e.g., in the case of transparent transmission) or through specific processing (e.g., RLC header removal and / or RLC SDU reassembly), and the first RLC PDU may be the same as or different from the first RLC SDU. The RLC layer delivers the first RLC SDU to the PDCP layer. The PDCP layer receives the first PDCP PDU, and the PDCP layer may obtain the first PDCP SDU directly or through specific processing (e.g., one or more of the following: PDCP header removal, decryption, integrity protection check, reordering, header recovery, and data recovery), where the first PDCP PDU may be the same as or different from the first PDCP SDU. The PDCP layer delivers the first PDCP SDU to the RRC layer. The RRC layer receives the first RRC PDU.

[0182] 8b is another diagram illustrating data reception by a terminal device and processing performed at each layer according to an embodiment of the present application. As shown in FIG. 8b, the terminal device receives first data, which is a first MAC PDU. The MAC layer may obtain the first MAC SDU directly or through specific processing (e.g., disassembly and multiplexing), and the first MAC PDU may be the same as or different from the first MAC SDU. The MAC layer delivers the first MAC SDU to the RLC layer. The RLC layer receives the first RLC PDU, which may obtain the first RLC SDU directly (e.g., in the case of transparent transmission) or through specific processing (e.g., RLC header removal and / or RLC SDU reassembly), and the first RLC PDU may be the same as or different from the first RLC SDU. The RLC layer delivers the first RLC SDU to the RRC layer. The RRC layer receives the first RRC PDU.

[0183] It should be noted that when a layer delivers data directly to another layer, the data delivered by the layer may be the same as the data received by the other layer, but the data may have different names at different layers. For example, when the MAC layer delivers a first MAC SDU to the RLC layer, the first MAC SDU is the same as the first RLC PDU. For example, when the RLC layer delivers a first RLC SDU to the PDCP layer, the first RLC SDU is the same as the first PDCP PDU. For example, when the PDCP layer delivers a first PDCP SDU to the RRC layer, the first PDCP SDU is the same as the first RRC PDU. For example, when the RLC layer delivers a first RLC SDU to the RRC layer, the first RLC SDU is the same as the first RRC PDU.

[0184] It should be noted that for understanding the processing of the second data, the third data, or the fourth data in each layer, the description of the first data may be referred to, provided that "first" is replaced with "second," "third," or "fourth." Details will not be described again here.

[0185] It should be noted that in the embodiments of the present application, the association of the first SIB1 with the first RLC entity may also be described as the association of the first message with the first RLC entity, or the association of the first data with the first RLC entity; the association of the first SIB1 with the first LCH may also be described as the association of the first message with the first LCH, or the association of the first data with the first LCH. Correspondingly, the association of the second SIB1 with the second RLC entity may also be described as the association of the second message with the second RLC entity, or the association of the second data with the second RLC entity; the association of the second SIB1 with the second LCH may also be described as the association of the second message with the second LCH, or the association of the second data with the second LCH. Correspondingly, the SI message may be associated with the third RLC entity, or the SI message may be associated with the third LCH. The association of an SI message with the third RLC entity may also be described as the association of a third message with the third RLC entity, or as the association of third data with the third RLC entity. The association of an SI message with the third LCH may also be described as the association of a third message with the third LCH, or as the association of third data with the third LCH. For ease of description, in this application, the first SIB1 is associated with the first RLC entity or the first SIB1 is associated with the first LCH, the second SIB1 is associated with the second RLC entity or the second SIB1 is associated with the second RLC, and the SI message is associated with the third RLC entity or the SI message is associated with the third LCH.

[0186] It should be noted that when a DCI schedules a SIB1 (e.g., the first SIB1 or the second SIB1), an SI message, or a SIB1 set, it can be understood as when a DCI schedules data corresponding to a SIB1 (e.g., the first SIB1 or the second SIB1), an SI message, or a SIB1 set.

[0187] The resource information in the embodiment of the present application may include time domain resource information and / or frequency domain resource information.

[0188] It should be noted that "produced" in this application can be understood as "determined." "Comprise" and "indicate" in this application can be understood as "include." "Identify" described in this application can be written as "determine." "Understood as" described in this application can be written as "include" or "substituted with." "Carried in" described in this application can be written as "impliedly included in." This is not limited here.

[0189] The following provides a detailed description of the communication method and communication device provided in this application.

[0190] 9 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 9, the communication method includes the following steps S901 to S901.

[0191] S901: A terminal device receives first downlink control information DCI from a network device.

[0192] Accordingly, the network device transmits first downlink control information (DCI). The first DCI is used to schedule first data, and the first data includes a first SIB1. The first SIB1 includes information about network access in the first operating mode. Alternatively, this is understood as the first SIB1 being a SIB1 associated with the first operating mode.

[0193] In some possible implementations, the network device may transmit at least one DCI, and different DCIs are used to schedule different data. For ease of understanding, in this embodiment of the present application, an example in which the at least one DCI transmitted by the network device includes a first DCI and / or a second DCI is mainly used for explanation. The second DCI is used to schedule second data, and the second data includes a second SIB1. The second SIB1 includes information about network access in the second operating mode. Alternatively, this can be understood as the second SIB1 being a SIB1 related to the second operating mode.

[0194] Optionally, the at least one DCI transmitted by the network device may further include a fifth DCI, where the fifth DCI is used to schedule third data, and the third data includes an SI message, where the SI message includes at least one SIB.

[0195] It should be noted that the SIBs included in the SI message may include any one or more of SIB2 to SIB14, or may include additional SIBs that may be expanded in the future, such as SIB15 and SIB16, but this is not limited here.

[0196] For example, Figure 10 is a diagram of a scheduling mode according to an embodiment of the present application. As shown in Figure 10, the network device separately schedules the first SIB1 and the second SIB1 by using two DCIs. It can be understood that the network device separately schedules the data corresponding to the first SIB1 and the data corresponding to the second SIB1 by using two DCIs.

[0197] It should be noted that in this embodiment of the present application, the first operation mode may be a secure mode and the second operation mode may be a normal mode, or alternatively, in this embodiment of the present application, the first operation mode may be a normal mode and the second operation mode may be a secure mode. This is not limited here. The secure mode may be understood as any one or more of the following: a restricted operation mode, an operation mode used when compatibility issues occur, and an operation mode that can be used to identify and / or resolve issues. The normal mode may be understood as any one or more of the following: an operation mode used when compatibility issues do not occur.

[0198] For example, after accessing the network in secure mode, the terminal device may perform any one or more of the following processes: reporting a problem, identifying a problem, updating, upgrading, correcting errors, etc. As another example, if the terminal device cannot access the network in normal mode, the terminal device may access the network in secure mode. As another example, if a compatibility issue occurs with the terminal device or if a compatibility issue occurs between the terminal device and a network device, the terminal device cannot access the network in normal mode, and the terminal device may access the network in secure mode.

[0199] It should be noted that in this embodiment of the present application, the secure mode may be understood as a first protocol version, and the normal mode may be understood as a second protocol version. In this embodiment of the present application, the first SIB1 may also be understood as an SIB1 of the first protocol version, and the second SIB1 may also be understood as an SIB1 of the second protocol version. The first protocol version may be a base protocol version (referred to as a base version), or may be described as a predecessor protocol version (referred to as a predecessor version), and the second protocol version may be a later protocol version (referred to as a later version). Alternatively, the first protocol version may be a later version, and the second protocol version may be a base version, a predecessor version, etc. This is not limited here. The base version SIB1 may be an SIB1 of 5G R18, an SIB1 of the first version of 6G, etc. This is not limited here. The later version SIB1 may be an SIB1 in a future communication system, etc. This is not limited here. The basic version of SIB1 may be used for communication in secure mode, or the basic version of SIB1 may be used for communication in normal mode. For example, when a terminal device supporting a later protocol version performs normal communication, the terminal device may combine the basic version of SIB1 with the delta configuration of the later version of SIB1 to obtain the complete SIB1 of the later version, or may use the full configuration of SIB1 of the later version. In a possible implementation, the information elements and information element values ​​of SIB1 for secure mode are all or part of the information elements and information element values ​​of SIB1 for normal mode. In another possible implementation, SIB1 for secure mode and SIB1 for normal mode may have different configurations, for example, may include different information elements. When two SIB1s are included in the same information element, the information elements may have different values.For ease of understanding, two SIB1s (eg, a first SIB1 and a second SIB1) are mainly used below as an example for detailed description in this embodiment of the present application.

[0200] S902: The terminal device determines, based on the first DCI, that the first data includes a first system information block 1 SIB1.

[0201] There are many ways for the terminal device to determine that the first data includes the first SIB1 based on the first DCI. The following will be described with reference to Examples 1 to 5. Note that specific implementations may be performed by the physical layer or MAC layer of the terminal device, or may be performed by other layers (e.g., other newly defined layers). This is not limited in the present application.

[0202] Implementation 1: The terminal device determines that the first data includes a first SIB1 based on the first indication information included in the first DCI.

[0203] The first indication information indicates the type of system message scheduled by the first DCI or indicates the type of system message included in the data scheduled by the first DCI. For ease of description, the "type of system message" may be referred to as a "system message type." The system message type may include a first SIB1, a second SIB2, a 1 , or SI message.

[0204] The first indication information may be carried in a first field within the first DCI.

[0205] In implementation, for example, the first indication information may indicate that the first DCI schedules the first SIB1 or the second SIB1. Different values ​​of the first field may indicate a specific SIB1 (e.g., the first SIB1 or the second SIB1) scheduled by the first DCI, or a specific SIB1 (e.g., the first SIB1 or the second SIB1) included in the data scheduled by the first DCI. The length of the first field may be 1 bit, 2 bits, 4 bits, or another number of bits. This is not limited in the present application. Optionally, the first field may be a newly defined field. For example, the length of the first field is assumed to be 1 bit. A value of 0 in the first field may indicate that the DCI schedules the first SIB1, and a value of 1 in the first field may indicate that the DCI schedules the second SIB1. Alternatively, a value of 0 in the first field may indicate that the DCI schedules the second SIB1, and a value of 1 in the first field may indicate that the DCI schedules the first SIB1, but this is not limited thereto.

[0206] Optionally, the first field may alternatively be represented in the form of a bitmap. Each bit in the bitmap corresponds to a system message type, and the value of each bit indicates whether the DCI schedules the corresponding type of system message. For example, a bit value of 1 indicates that the DCI schedules the corresponding type of system message, or a bit value of 0 indicates that the DCI does not schedule the corresponding type of system message. Note that the system message type corresponding to each bit in the bitmap may be preset in a protocol or may be set by the network. This is not a limitation of the present application. For example, the length of the bitmap is two bits, and the first and second bits of the two bits, from left to right, correspond to the first SIB1 and the second SIB1, respectively. A value of 1 for the first bit indicates that the DCI schedules the first SIB1. A value of 0 for the first bit indicates that the DCI does not schedule the first SIB1.

[0207] Optionally, when the first indication information indicates that the first DCI schedules the first SIB1 or the second SIB1, the first indication information may further perform a combined indication with the second field or the tenth indication information (e.g., a system information indicator field) to indicate a specific SIB1 to be scheduled by the DCI or to indicate that an SIB message is scheduled. Different values ​​of the second field or the tenth indication information may indicate whether the DCI schedules an SIB1 or an SI message. Specifically, whether the DCI schedules an SIB1 or an SI message may be first determined based on the second field or the tenth indication information. When it is determined that the DCI schedules an SIB1, the specific SIB1 to be scheduled by the DCI is further determined based on a specific value of the first field or the first indication information in the DCI.

[0208] In another implementation, the first indication information may indicate that the first DCI schedules the first SIB1, the second SIB1, or an SI message. Different values ​​of the first field may indicate a specific SIB1 (e.g., the first SIB1 or the second SIB1) or an SI message scheduled by the first DCI, or a specific SIB1 (e.g., the first SIB1 or the second SIB1) or an SI message included in the data scheduled by the first DCI. The length of the first field may be 2 bits, 4 bits, or another number of bits. This is not limited in the present application. For example, it is assumed that the length of the first field is 2 bits. In this case, a value of 01 in the first field may indicate that the DCI schedules the first SIB1, a value of 10 in the first field may indicate that the DCI schedules the second SIB1, and a value of 00 in the first field may indicate that the DCI schedules an SI message. Alternatively, a value of 01 in the first field may indicate that the DCI schedules a first SIB1, a value of 10 in the first field may indicate that the DCI schedules a second SIB1, and a value of 11 in the first field may indicate that the DCI schedules an SI message. Examples will not be described one by one here.

[0209] Optionally, the first field may alternatively be represented in the form of a bitmap. Each bit in the bitmap corresponds to a system message type, and the value of each bit indicates whether the DCI schedules a system message of the corresponding type. For example, if the bit value is 1, it indicates that the DCI schedules a system message of the corresponding type, or if the bit value is 0, it indicates that the DCI does not schedule a system message of the corresponding type. Note that the system message type corresponding to each bit in the bitmap may be set in advance by a protocol or may be set by the network, but this is not a limitation of the present application.

[0210] For example, the length of the bitmap is 3 bits, and the first, second, and third bits from left to right of the 3 bits correspond to the first SIB1, the second SIB1, and the SI message, respectively. If the value of the first bit is 1, it indicates that the DCI schedules the first SIB1. If the value of the first bit is 0, it indicates that the DCI does not schedule the first SIB1.

[0211] Optionally, the first field may be a newly defined field, or may be an extended field, such as an extended system information indicator field or an extended HARQ process ID field. Specifically, in this embodiment of the present application, the meanings corresponding to different values ​​of the system information indicator field or the HARQ process ID field in the prior art may be extended so that the extended field can indicate different SIB1s, such as the first SIB1 and the second SIB1, in addition to the SI message. For ease of description, an example in which the first field is an extended system information indicator field is used for explanation in this embodiment of the present application. The extended system information indicator field may include 2 bits, 3 bits, etc., but this is not limited thereto.

[0212] For ease of understanding, an example in which the length of the extended system information indicator field is 2 bits is used for explanation in this embodiment of the present application. See Table 1 for example. The meanings of different values ​​of the extended system information indicator field may be shown in Table 1. A value of 00 in the field indicates that the DCI schedules the first SIB1. A value of 01 in the field indicates that the DCI does not schedule an SI message. A value of 10 in the field indicates that the DCI schedules the second SIB1. A value of 11 in the field may be reserved or used for other purposes, which is not limited herein. Alternatively, the meanings corresponding to corresponding values ​​of the fields may be exchanged, which is not limited herein. [Table 1]

[0213] It should be noted that in implementation 1, one or more of the following corresponding to the DCI (e.g., the first DCI) used to schedule the first SIB1 may be the same as that corresponding to the DCI (e.g., the second DCI) used to schedule the second SIB1.

[0214] (1) The time domain resources may be the same, where the time domain resources include the range of time domain resources, search space, etc., over which DCIs for scheduling SIBs are monitored.

[0215] (2) The frequency domain resources may be the same, where the frequency domain resources include a range of frequency domain resources where DCI for scheduling SIBs is monitored, a control resource set, etc.

[0216] (3) The DCI format may be the same. For example, the DCI format may be DCI format 1_0.

[0217] (4) The scrambling information of the DCI may be the same. For example, the scrambling information may include the SI-RNTI, and the value of the SI-RNTI may be FFFF.

[0218] Implementation 2: The terminal device may determine that the first data includes the first SIB1 based on the scrambling information of the first DCI.

[0219] A terminal device may distinguish between content scrambled by different DCIs or between types of system messages scrambled by different DCIs based on the scrambling information of the different DCIs. For example, a terminal device may determine that data scrambled by a first DCI includes a first SIB1 based on the scrambling information of a first DCI. For example, a terminal device may determine that data scrambled by a second DCI includes a second SIB1 based on the scrambling information of a second DCI. The scrambling information of the first DCI is different from the scrambling information of the second DCI.

[0220] For example, the scrambling information of the first DCI may be the SI-RNTI, and the scrambling information of the second DCI may be another RNTI (e.g., a newly defined RNTI), or the scrambling information of the second DCI may be the SI-RNTI, and the scrambling information of the first DCI may be another RNTI (e.g., a newly defined RNTI). This is not limited herein. As another example, the scrambling information of the first DCI may be the RNT (e.g., the newly defined RNTI1), and the scrambling information of the second DCI may be another RNTI (e.g., the newly defined RNTI2). This is not limited herein. It should be noted that the scrambling information of the fifth DCI may be the same as the scrambling information of the first DCI, or the scrambling information of the fifth DCI may be the same as the scrambling information of the second DCI, or the scrambling information of the fifth DCI may be different from both the scrambling information of the first DCI and the scrambling information of the second DCI. This is not a limitation of the present application.

[0221] It may be understood that a terminal device may distinguish content scheduled by different DCIs based on scrambling information (e.g., RNTI) of the different DCIs. For example, the terminal device may determine whether data scheduled by different DCIs includes the first SIB1 or the second SIB1 based on the scrambling information of the different DCIs. As another example, the terminal device may determine whether data scheduled by different DCIs includes the first SIB1, the second SIB1, or an SI message based on the scrambling information of the different DCIs.

[0222] It should be noted that in implementation 2, one or more of the following corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI): time domain resources, frequency domain resources, and DCI format may be the same as those corresponding to the DCI used to schedule the second SIB1 (e.g., the second DCI).

[0223] Implementation 3: The terminal device may determine that the first data includes a first SIB1 based on the DCI format of the first DCI.

[0224] It may be understood that the terminal device may distinguish between the content scheduled by different DCIs or the type of system message scheduled by different DCIs based on the DCI formats of the different DCIs.

[0225] For example, the terminal device may determine, based on the DCI format of the first DCI, that the data scheduled by the first DCI includes the first SIB1. For example, the terminal device may determine, based on the DCI format of the second DCI, that the data scheduled by the second DCI includes the second SIB1. The first DCI is different from the scrambling of the second DCI. For example, the format of the DCI used to schedule the first SIB1 may be DCI format 1_0, and the format of the DCI used to schedule the second SIB1 may be another DCI format (e.g., a newly defined DCI format). Alternatively, the format of the DCI used to schedule the second SIB1 may be DCI format 1_0, and the format of the DCI used to schedule the first SIB1 may be another DCI format (e.g., a newly defined DCI format). As another example, both the format of the DCI used to schedule the first SIB1 and the format of the DCI used to schedule the second SIB1 may be newly defined DCI formats. This is not limited here.

[0226] It should be noted that the DCI format of the fifth DCI may be the same as the DCI format of the first DCI, or the DCI format of the fifth DCI may be the same as the DCI format of the second DCI, or the DCI format of the fifth DCI may be different from both the DCI format of the first DCI and the DCI format of the second DCI, which is not limited in the present application.

[0227] The terminal device may distinguish content scheduled by different DCIs based on the DCI formats of the different DCIs. For example, the terminal device may determine whether data scheduled by different DCIs includes a first SIB1 or a second SIB1 based on the DCI formats of the different DCIs. As another example, the terminal device may determine whether data scheduled by different DCIs includes a first SIB1, a second SIB1, or an SI message based on the DCI formats of the different DCIs.

[0228] It should be noted that in implementation 3, one or more of the following corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI): time domain resources, frequency domain resources, and DCI scrambling information may be the same as those corresponding to the DCI used to schedule the second SIB1 (e.g., the second DCI).

[0229] Implementation 4: The terminal device may determine that the first data includes the first SIB1 based on the time domain resource for the first DCI.

[0230] It may be understood that a terminal device may distinguish content scheduled by different DCIs based on time domain resources for the different DCIs. For example, a terminal device may determine that data scheduled by a first DCI includes a first SIB1 based on time domain resources for a first DCI. For example, a terminal device may determine that data scheduled by a second DCI includes a second SIB1 based on time domain resources for a second DCI. The time domain resources for the first DCI are different from the time domain resources for the second DCI.

[0231] For example, the search space for the DCI used to schedule the first SIB1 (i.e., the first DCI) is CSS#0, and the search space for the DCI used to schedule the second SIB1 (i.e., the second DCI) is CSS#1. Note that the time domain resources for the fifth DCI may be the same as the time domain resources for the first DCI, or the time domain resources for the fifth DCI may be the same as the time domain resources for the second DCI, or the time domain resources for the fifth DCI may be different from both the time domain resources for the first DCI and the time domain resources for the second DCI. This is not a limitation in the present application.

[0232] It may be understood that a terminal device may distinguish time-scheduled content for different DCIs based on time domain resources for the different DCIs. For example, a terminal device may determine whether data scheduled by different DCIs includes a first SIB1 or a second SIB1 based on time domain resources for the different DCIs. As another example, a terminal device may determine whether data scheduled by different DCIs includes a first SIB1, a second SIB1, or an SI message based on time domain resources for the different DCIs.

[0233] It should be noted that in implementation 4, one or more of the following corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI): frequency domain resources, DCI format, and DCI scrambling information may be the same as those corresponding to the DCI used to schedule the second SIB1 (e.g., the second DCI).

[0234] Implementation 5: The terminal device may determine that the first data includes a first SIB1 based on the frequency domain resource for the first DCI.

[0235] It may be understood that a terminal device may distinguish content scheduled by different DCIs based on frequency domain resources for the different DCIs. For example, a terminal device may determine that data scheduled by a first DCI includes a first SIB1 based on frequency domain resources for a first DCI. For example, a terminal device may determine that data scheduled by a second DCI includes a second SIB1 based on frequency domain resources for a second DCI. The frequency domain resources for the first DCI are different from the frequency domain resources for the second DCI. For example, a control resource set for a DCI used to schedule a first SIB1 is CORESET#0, and a control resource set for a DCI used to schedule a second SIB1 is CORESET#1.

[0236] It should be noted that the frequency domain resources for the fifth DCI may be the same as the frequency domain resources for the first DCI, or the frequency domain resources for the fifth DCI may be the same as the frequency domain resources for the second DCI, or the frequency domain resources for the fifth DCI may be different from both the frequency domain resources for the first DCI and the frequency domain resources for the second DCI, which is not limited in this application.

[0237] It may be understood that a terminal device may distinguish time-scheduled content for different DCIs based on frequency domain resources for the different DCIs. For example, a terminal device may determine whether data scheduled by different DCIs includes a first SIB1 or a second SIB1 based on frequency domain resources for the different DCIs. As another example, a terminal device may determine whether data scheduled by different DCIs includes a first SIB1, a second SIB1, or an SI message based on frequency domain resources for the different DCIs.

[0238] It should be noted that in implementation 5, one or more of the following corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI): time domain resource, DCI format, and DCI scrambling information may be the same as those corresponding to the DCI used to schedule the second SIB1 (e.g., the second DCI).

[0239] It should be noted that the above five implementations may be combined with each other or implemented independently. This is not limited in the present application. It should be noted that Implementations 2, 3, 4, and 5 may be performed before the terminal device receives, successfully receives, or monitors a DCI. This is specifically determined based on an actual application scenario and is not limited here. For example, in Implementations 2, 3, 4, and 5, the terminal device receiving one or more DCIs may be understood as the terminal device monitoring one or more DCIs.

[0240] It should be noted that step S902 may be performed before or after step S901. This is not limited in the present application. For example, in implementations 2, 3, 4, and 5, step S902 may be performed before step S901. As another example, in implementation 1, step S902 may be performed after step S901.

[0241] In any one or more of the five implementations, in step S902, the terminal device may determine the content included in the data scheduled by the DCI, which helps to ensure that the terminal device can accurately perform HARQ combined decoding and improve transmission reliability.

[0242] S903: The terminal device receives first data from the network device.

[0243] It should be noted that the terminal device may receive the first data from the network device based on the first DCI. Specifically, the terminal device may receive the first data from the network device based on the scheduling information included in the first DCI.

[0244] S904: The terminal device determines, based on the first data, that the first data includes a first SIB1.

[0245] After the terminal device receives the first data from the network device based on the first DCI, the terminal device may further decode (e.g., ASN.1 decode) the content included in the first data based on the first data. Specifically, the terminal device may identify the content included in the first data using any one or more of the following implementations (1) to (3), and then decode the identified content according to a decoding method corresponding to the identified content. The three implementations may be understood as being performed in the RRC layer of the terminal device, or may be performed in another layer (e.g., another newly defined layer). This is not limited here. Specifically, after successfully receiving the first data, the MAC layer, PHY layer, or another newly defined layer of the terminal device may deliver all or part of the first data to the RRC layer or another layer (e.g., another newly defined layer) of the terminal device, and then the first data is decoded in the RRC layer or another layer (e.g., another newly defined layer) of the terminal device. The following describes implementations (1) to (3) in detail separately.

[0246] In implementation (1), the first data or the first message may include second indication information, and the second indication information indicates that the first data or the first message includes the first SIB1.

[0247] The second indication information may be carried in the first data or the first message sent by the network device to the terminal device, and the second indication information indicates the type of the system message included in the first data or the first message, i.e., the system message type. The system message type may be a first SIB1, a second SIB2, a 1 , or SI messages.

[0248] The second indication information may be carried in a third field in the first data or the first message.

[0249] In practice, for example, 2 The indication information may indicate that the first data or the first message includes the first SIB1 or the second SIB1. 3 Different values ​​of the field may indicate a particular SIB1 (e.g., a first SIB1 or a second SIB1) included in the first data or the first message. 3 The length of the field may be 1 bit, 2 bits, 4 bits, or any other number of bits. This is not limited in this application. For example, 3 The field is assumed to be 1 bit long. 3 A value of 0 in the field may indicate that the first data or the first message contains a first SIB1, and 3 A value of 1 in the field may indicate that the first data or the first message includes a second SIB1. 3 A value of 0 in the field may indicate that the first data or the first message includes a second SIB1, and 3 A value of 1 in the field may indicate that the first data or the first message includes the first SIB1, which is not limited here.

[0250] Optionally, 3 Alternatively, the field may be represented in the form of a bitmap. Each bit in the bitmap corresponds to a system message type, and the value of each bit indicates whether the first data or the first message includes a system message of the corresponding type. For example, a bit value of 1 indicates that the first data or the first message includes a system message of the corresponding type, or a bit value of 0 indicates that the first data or the first message does not include a system message of the corresponding type. Note that the system message type corresponding to each bit in the bitmap may be preset by a protocol or may be set by the network. This is not a limitation of the present application. For example, the length of the bitmap is two bits, and the first and second bits from left to right correspond to the first SIB1 and the second SIB1, respectively. A value of 1 for the first bit indicates that the first data or the first message includes the first SIB1. A value of 0 for the first bit indicates that the first data or the first message does not include the first SIB1.

[0251] Optionally, 2 If the indication information indicates that the first data or the first message includes the first SIB1 or the second SIB1, 2 The indication information further performs a combination indication with the fourth field or the eleventh indication information to indicate a specific SIB1 included in the first data or the first message, or the SIB message IncludedA different value of the fourth field or the eleventh indication information may indicate whether the first data or the first message includes an SIB1 or an SI message. Specifically, whether the first data or the first message includes an SIB1 or an SI message may first be determined based on the fourth field or the eleventh indication information. If it is determined that the first data or the first message includes an SIB1, the specific SIB1 included in the first data or the first message may further be determined based on the fourth field or the eleventh indication information in the DCI. 3 Field or 2 It is determined based on the particular value of the indicator information.

[0252] In other implementations, 2 The indication information may indicate that the first data or the first message includes a first SIB1, a second SIB1, or an SI message. 3 Different values ​​of the field may indicate a particular SIB1 (e.g., a first SIB1 or a second SIB1) or SI message included in the first data or first message. 3 The length of the field may be 2 bits, 4 bits, or other number of bits. This is not limited in this application. For example, 3 The length of the field is assumed to be 2 bits. 3 A value of 01 in the field can indicate that the first data or the first message contains a first SIB1, and 3 A value of 10 in the field may indicate that the first data or the first message includes a second SIB1, and 3 A value of 00 in the field may indicate that the first data or message contains an SI message. 3 A value of 01 in the field can indicate that the first data or the first message contains a first SIB1, and 3 A value of 10 in the field may indicate that the first data or the first message includes a second SIB1, and 3A value of 11 in the field may indicate that the first data or message contains an SI message. Examples will not be described one by one here.

[0253] Optionally, 3 Alternatively, the field may be represented in the form of a bitmap. Each bit in the bitmap corresponds to a system message type, and the value of each bit indicates whether the first data or the first message includes a system message of the corresponding type. For example, a bit value of 1 indicates that the first data or the first message includes a system message of the corresponding type, or a bit value of 0 indicates that the first data or the first message does not include a system message of the corresponding type. Note that the system message type corresponding to each bit in the bitmap may be preset by a protocol or may be set by the network. This is not a limitation of the present application. For example, the bitmap is three bits long, and the first, second, and third bits of the three bits correspond, from left to right, to the first SIB1, second SIB1, and SI message, respectively. A value of 1 for the first bit indicates that the first data or the first message includes the first SIB1. A value of 0 for the first bit indicates that the first data or the first message does not include the first SIB1.

[0254] In implementation (2), the terminal device obtains third indication information associated with the first message.

[0255] The phrase "the terminal device obtains third indication information associated with the first message" can be understood as follows: the RRC layer of the terminal device obtains third indication information associated with the first message from the lowest layer of the terminal device. The third indication information indicates the type of the system message included in the first data or the first message, i.e., the system message type. The system message type can be a first SIB1, a second SIB2, a 1 , or SI messages.

[0256] The "lowest layer of the terminal device" may include any one of the following: a PHY layer of the terminal device, a MAC layer of the terminal device, an RLC layer of the terminal device, or a PDCP layer of the terminal device, where the lowest layer of the terminal device may deliver the third indication information to the RRC layer by layer, or may deliver the third indication information to the RRC layer through one or more layers between the lowest layer of the terminal device and the RRC layer of the terminal device, or the lowest layer of the terminal device delivers the third indication information directly to the RRC layer of the terminal device.

[0257] It can be understood that the RRC layer of the terminal device not only acquires the first message but also acquires third indication information related to the first message. The RRC layer of the terminal device can determine the type of the first data or the system message included in the first message based on the third indication information. Note that the implementation of acquiring the first message by the RRC layer of the terminal device may be the same as or different from the implementation of acquiring the third indication information by the RRC layer of the terminal device. This is not limited in the present application.

[0258] It should be noted that the third indication information does not have to be included in the first data. For example, the third indication information may be generated by the terminal device based on DCI (e.g., information of the first DCI). For example, if the third indication information is generated by a PHY layer of the terminal device, the third indication information may not be included in the first data. Alternatively, the third indication information may be included in the first data, for example, in any one of the following corresponding to the first data: a MAC subheader of the first MAC PDU, an RLC header of the first RLC PDU, or a PDCP header of the first PDCP PDU. For example, if the third indication information is generated by a MAC layer of the terminal device, the third indication information may be included in a MAC subheader (e.g., a MAC subheader of the first MAC PDU). If the third indication information is generated by an RLC layer of the terminal device, the third indication information may be included in an RLC header (e.g., an RLC header of the first RLC PDU). If the third indication information is generated by a PDCP layer of the terminal device, the third indication information may be included in a PDCP header (e.g., a PDCP header of the first PDCP PDU).

[0259] Note that, in actual implementation, the specific expression format of the third indication information may be first indication information obtained based on the first DCI, information extracted from the first indication information, etc. This is not limited herein. Thus, the RRC layer of the terminal device may determine that the first data or the first message includes the first SIB1 based on the received third indication information. Alternatively, the specific expression format of the third indication information may be information obtained from scrambling information of the DCI, or may be the scrambling information of the DCI, etc. This is not limited herein. Alternatively, the specific expression format of the third indication information may be information obtained from a DCI format, or may be the DCI format, etc. This is not limited herein. Alternatively, the specific expression format of the third indication information may be information obtained from a monitoring occasion, a search space, or a time domain resource for the DCI, or may be the monitoring occasion, search space, or a time domain resource for the DCI, This is not limited herein. Alternatively, the specific expression format of the third indication information may be information obtained from a frequency domain resource or a control resource set for DCI, or may be a frequency domain resource or a control resource set on which DCI is monitored, etc. This is not limited herein.

[0260] Optionally, in implementation (1) and / or implementation (2), the first SIB1 and the second SIB1 may correspond to the same logical channel and / or the same RLC entity. Note that the SI message and one or both of the first SIB1 and the second SIB1 may correspond to the same logical channel and / or the same RLC entity, but this is not a limitation of the present application.

[0261] In implementation (3), the first SIB1 may be associated with the first RLC entity, or the first SIB1 may be associated with the first logical channel LCH, and the second RLC entity may be associated with the second SIB1, and the second LCH may be associated with the second SIB1, where the first RLC entity is different from the second RLC entity, and the first LCH is different from the second LCH.

[0262] Thus, the terminal device (e.g., an RRC layer or other layer of the terminal device) may determine the content included in the received data or message based on the LCHs or RLC entities associated with different data or messages. For example, the terminal device may determine that the first data includes a first SIB1 based on a first LCH or a first RLC entity associated with the first data. As another example, the terminal device may determine that the second data includes a second SIB1 based on a second LCH or a second RLC entity associated with the second data. As another example, the terminal device may determine that the third data includes an SI message based on a third LCH or a third RLC entity associated with the third data.

[0263] For example, the first SIB1 may correspond to a logical channel (i.e., BCCH) in the prior art, and the second SIB1 may correspond to another logical channel (e.g., newly defined logical channel 1), or the second SIB1 may correspond to a logical channel (i.e., BCCH) in the prior art, and the first SIB1 may correspond to another logical channel (e.g., newly defined logical channel 1). This is not limited here.

[0264] It should be noted that the third RLC entity may be different from both the first RLC entity and the second RLC entity, or may be the same as both the first RLC entity and the second RLC entity, or may be the same as one of the first RLC entity and the second RLC entity. This is not limited here. Alternatively, this can be written as follows: the third LCH may be different from both the first LCH and the second LCH, or the third LCH may be the same as all or part of the first LCH and the second LCH. Optionally, when the third LCH is the same as all or part of the first LCH and the second LCH, or when the third RLC entity is the same as all or part of the first RLC entity and the second RLC entity, whether the RRC message (e.g., the first message) includes an SI message or a first SIB1, whether the RRC message (e.g., the first message) includes an SI message or a second SIB1, or whether the RRC message (e.g., the first message) includes an SI message, a first SIB1, or a second SIB1 needs to be further determined according to implementation (1) or implementation (2).

[0265] It should be noted that any one or more of the embodiments 1 to 5 may be combined with any one or more of the embodiments (1) to (3), but this is not limited thereto.

[0266] For example, implementation 1 and implementation (1) are used as examples. The terminal device monitors a PDCCH scrambled by using the SI-RNTI. The terminal device receives a DCI scrambled by using the SI-RNTI. The terminal device determines that the DCI schedules SIB1 based on the system information indicator field being 0. The terminal device determines that the SIB1 scheduled by the DCI is the first SIB1 based on the first indication information included in the DCI. The terminal device performs decoding by using a HARQ process corresponding to broadcast. If the decoding is successful, the MAC layer of the terminal device delivers the data to the RRC layer of the terminal device for processing through the RLC layer. If the decoding fails, the terminal device re-receives another DCI scrambled by using the SI-RNTI, and the re-received DCI also indicates that the DCI schedules the first SIB1. The terminal device may perform joint decoding on the currently received data and the previously received data. If the decoding is successful, the MAC layer of the terminal device similarly delivers the data through the RLC layer to the RRC layer of the terminal device for processing. The RRC layer may determine that the RRC message includes the first SIB1 based on the second indication information included in the RRC message, and then perform RRC decoding by using the ASN.1 of the first SIB1.

[0267] As another example, the MAC layer processing and the RRC layer processing are performed according to Implementation 1 and Implementation 2, respectively. The terminal device monitors a PDCCH scrambled by using the SI-RNTI. The terminal device receives a DCI scrambled by using the SI-RNTI. The terminal device determines (in the prior art) that the DCI schedules SIB1 based on the system information indicator field included in the DCI being 0. The terminal device determines that the SIB1 scheduled by the DCI is the first SIB1 based on the first indication information included in the DCI. The terminal device performs decoding by using a HARQ process corresponding to broadcast. If the decoding is successful, the MAC layer of the terminal device delivers the data to an upper layer (e.g., an RRC layer) of the terminal device. If the decoding fails, the terminal device re-receives another DCI scrambled by using the SI-RNTI, and the re-received DCI also indicates that the DCI schedules the first SIB1. The terminal device may perform joint decoding on the currently received data and the previously received data. If the decoding is successful, the MAC layer of the terminal device similarly delivers the data to an upper layer (e.g., an RRC layer) of the terminal device. The RRC layer may determine that the RRC message includes the first SIB1 based on the third indication information received from the MAC layer, and then perform RRC decoding by using the ASN.1 of the first SIB1.

[0268] For example, implementations 1 and (3) are used as examples. The terminal device monitors a PDCCH scrambled by using the SI-RNTI. The terminal device receives a DCI scrambled by using the SI-RNTI. The terminal device determines that the DCI schedules SIB1 based on the system information indicator field being 0. The terminal device determines that the SIB1 scheduled by the DCI is the first SIB1 based on the first indication information included in the DCI. The terminal device performs decoding by using a HARQ process corresponding to broadcast. If the decoding is successful, the MAC layer of the terminal device delivers data to the RRC layer of the terminal device through the RLC layer. If the decoding fails, the terminal device re-receives another DCI scrambled by using the SI-RNTI, and the re-received DCI also indicates that the DCI schedules the first SIB1. The terminal device may perform joint decoding on the currently received data and the previously received data. If the decoding is successful, the MAC layer of the terminal device similarly delivers the data to the RRC layer of the terminal device through the RLC layer. The RRC layer can determine that the RRC message includes the first SIB1 by receiving the data from the RLC entity corresponding to the first SIB1, and can then perform RRC decoding by using the ASN.1 of the first SIB1.

[0269] It can be understood that other combinations between the embodiments 2 to 5 and the embodiments (1) to (3) are not described one by one here by using examples.

[0270] Optionally, in some possible implementations, in a scenario with three or more SIBs, specifically in a scenario where the network device may transmit further SIBs (e.g., third and fourth SIBs) in addition to the first and second SIBs, similar to the above description of the first and second SIBs, different SIBs may be distinguished based on one or more of the first indication information or first field in the DCI, the scrambling information of the DCI, the DCI format, the time domain resource for the DCI, or the frequency domain resource for the DCI, for decoding by the terminal device (e.g., the MAC layer, the PHY layer, or another layer of the terminal device). Correspondingly, different SIBs may also be distinguished based on one or more of the second indication information, the third indication information, or the logical channel (or RLC entity) for decoding by the terminal device (or the RRC layer or another layer of the terminal device).

[0271] For example, assume there are four SIB1s: SIB1 corresponding to version N, SIB1 corresponding to version N+1, SIB1 corresponding to version N+2, and SIB1 corresponding to version N+3. SIB1 corresponding to version N is the previous version SIB1. SIB1 corresponding to version N+1, SIB1 corresponding to version N+2, and SIB1 corresponding to version N+3 are all subsequent version SIB1s. For decoding by a terminal device (e.g., a MAC layer, a PHY layer, or other layer of a terminal device):

[0272] In implementation 1, when the first indication information in the DCI is used to distinguish different SIB1s, the following may be defined: a value of 0000 in the first field used to carry the first indication information indicates a SIB1 corresponding to version N, a value of 0001 in the first field indicates a SIB1 corresponding to version N+1, a value of 0010 in the first field indicates a SIB1 corresponding to version N+2, and a value of 0011 in the first field indicates a SIB1 corresponding to version N+3. Thus, the terminal device may determine a specific SIB1 to be scheduled by the DCI based on a specific value of the first field in the DCI.

[0273] In implementation 2, when the scrambling information of the DCI is used to distinguish SIB1 of different versions, the following may be defined: the scrambling information of the DCI used to schedule SIB1 corresponding to version N is the newly defined RNTI1, the scrambling information of the DCI used to schedule SIB1 corresponding to version N+1 is the newly defined RNTI2, the scrambling information of the DCI used to schedule SIB1 corresponding to version N+2 is the newly defined RNTI3, and the scrambling information of the DCI used to schedule SIB1 corresponding to version N+3 is the newly defined RNTI4. Thus, the terminal device may determine a specific SIB1 to be scheduled by the DCI based on the scrambling information of the DCI.

[0274] In implementation 3, when a DCI format is used to distinguish SIB1s of different versions, the following may be defined: the format of the DCI used to schedule SIB1 corresponding to version N is newly defined format 1, the format of the DCI used to schedule SIB1 corresponding to version N+1 is newly defined format 2, the format of the DCI used to schedule SIB1 corresponding to version N+2 is newly defined format 3, and the format of the DCI used to schedule SIB1 corresponding to version N+3 is newly defined format 4. Thus, the terminal device may determine the specific SIB1 to be scheduled by the DCI based on the format of the DCI.

[0275] In implementation 4, when time domain resources for DCI are used to distinguish SIB1 of different versions, the following may be defined: the time domain resource for DCI used to schedule SIB1 corresponding to version N may be time domain resource 1, the time domain resource for DCI used to schedule SIB1 corresponding to version N+1 may be time domain resource 2, the time domain resource for DCI used to schedule SIB1 corresponding to version N+2 may be time domain resource 3, and the time domain resource for DCI used to schedule SIB1 corresponding to version N+3 may be time domain resource 4. Time domain resource 1 to time domain resource 4 are different from each other. Therefore, the terminal device may determine a specific SIB1 to be scheduled by the DCI based on the time domain resource for the DCI.

[0276] In implementation 5, when frequency domain resources for DCI are used to distinguish SIB1 of different versions, the following may be defined: the frequency domain resource for DCI used to schedule SIB1 corresponding to version N may be frequency domain resource 1, the frequency domain resource for DCI used to schedule SIB1 corresponding to version N+1 may be frequency domain resource 2, the frequency domain resource for DCI used to schedule SIB1 corresponding to version N+2 may be frequency domain resource 3, and the frequency domain resource for DCI used to schedule SIB1 corresponding to version N+3 may be frequency domain resource 4. Frequency domain resource 1 to frequency domain resource 4 are different from each other. Therefore, the terminal device may determine a specific SIB1 to be scheduled by the DCI based on the frequency domain resource for the DCI.

[0277] For decoding by the terminal device (e.g., the RRC layer or other layer of the terminal device):

[0278] In implementation (1), when the second indication information included in the data is used to distinguish different SIB1s, the following may be defined: a value of 0000 in the third field used to carry the second indication information indicates a SIB1 corresponding to version N, a value of 0001 in the field indicates a SIB1 corresponding to version N+1, a value of 0010 in the field indicates a SIB1 corresponding to version N+2, and a value of 0011 in the field indicates a SIB1 corresponding to version N+3. Thus, the terminal device may determine a particular SIB1 included in the data based on a particular value of the third field included in the data.

[0279] In implementation (2), when the third indication information is used to distinguish SIB1s of different versions, different meanings corresponding to different values ​​of the field used to carry the third indication information may be predefined to indicate a specific SIB1 included in the data. For example, a value of 0000 in the field indicates a SIB1 corresponding to version N, a value of 0001 in the field indicates a SIB1 corresponding to version N+1, a value of 0010 in the field indicates a SIB1 corresponding to version N+2, and a value of 0011 in the field indicates a SIB1 corresponding to version N+3. Thus, the terminal device may determine a specific SIB1 included in the data based on a specific value of the third indication information.

[0280] In implementation (3), when different logical channels (or RLC entities) are used to distinguish SIB1 of different versions, the following may be defined: the logical channels or RLC entities corresponding to the versions are different. For example, the logical channel corresponding to SIB1 corresponding to version N is the newly defined logical channel 1 (or RLC1), the logical channel corresponding to SIB1 corresponding to version N+1 is the newly defined logical channel 2 (or RLC2), the logical channel corresponding to SIB1 corresponding to version N+2 is the newly defined logical channel 3 (or RLC3), and the logical channel corresponding to SIB1 corresponding to version N+3 is the newly defined logical channel 4 (or RLC4). Therefore, the terminal device can determine the specific SIB1 included in the data based on the corresponding logical channel or RLC entity.

[0281] S905: The terminal device receives or acquires fourth indication information from the network device.

[0282] Correspondingly, the network device may send fourth indication information to the terminal device. The fourth indication information may indicate whether a specific SIB1 (e.g., the first SIB1 and / or the second SIB1) exists in the cell or on the network device, or indicate whether the network device should send a specific SIB1 (e.g., the first SIB1 and / or the second SIB1), or indicate whether the cell or the network device supports a specific operation mode (e.g., the first operation mode and / or the second operation mode), or indicate whether the cell or the network device sends a different SIB1 by using the solution in this embodiment of the present application.

[0283] It should be noted that, according to the solution in step S905, the terminal device can know whether a specific cell or network device transmits a different SIB1 by using the solution in this embodiment of the present application, or the terminal device can know whether a network device transmits a specific SIB1 (e.g., the first SIB1), or the terminal device can know whether a cell or network device supports a specific operation mode (e.g., the first operation mode) by using the solution in this embodiment of the present application. Furthermore, if the terminal device can know in advance that the first SIB1 does not exist in the cell or on the network, the terminal device does not need to monitor the PDCCH corresponding to the first SIB1. This can save the energy of the terminal device. It should be noted that the step of receiving the fourth indication information from the network device by the terminal device may be performed before step S901 or may be performed simultaneously when step S901 is performed. This is not limited herein. The field used to carry the fourth indication information may include one bit, two bits, or more bits. This is not limited herein. Furthermore, the terminal device receiving the fourth indication information from the network device can be understood as follows: the terminal device receives an MIB from the network device, and the MIB includes the fourth indication information. Alternatively, the terminal device receiving the fourth indication information from the network device can be understood as follows: the terminal device receives a second DCI from the network device, and the second DCI includes the fourth indication information. Alternatively, the terminal device receiving the fourth indication information from the network device can be understood as follows: the terminal device receives a fifth DCI from the network device, and the fifth DCI includes the fourth indication information. That is, the fourth indication information can be carried in the MIB, or in the second DCI for scheduling the second SIB1 or the second data, or in the fifth DCI for scheduling the SI message.

[0284] It should be noted that, when the first SIB1 is a SIB1 associated with an earlier version or a secure mode and the second SIB1 is a SIB1 associated with a later version or a normal mode, the fourth indication information may be carried in the MIB, or in the DCI for scheduling the second SIB1, or in the DCI for scheduling an SI message. When the first SIB1 is a SIB1 associated with a later version or a normal mode and the second SIB1 is a SIB1 associated with an earlier version or a secure mode, the fourth indication information may be carried in the second SIB1 or the second data in addition to the MIB, the DCI for scheduling the second SIB or the second data, or the DCI for scheduling an SI message.

[0285] It should be noted that the above steps S901 and S902 may each be considered as an independent embodiment, or may be combined with one or more steps in this embodiment of the present application as an optional step, which is not limited herein. The above steps S903 and S904 may each be considered as an independent embodiment, or may be combined with one or more steps in this embodiment of the present application as an optional step, which is not limited herein. The above step S905 may each be considered as an independent embodiment, or may be combined with one or more steps in this embodiment of the present application as an optional step, which is not limited herein. Furthermore, the numbering order of the steps in this embodiment of the present application does not indicate the order in which the steps are performed. The order in which the steps are performed is specifically determined based on an actual application scenario, and is not limited herein.

[0286] In this embodiment of the present application, the network device transmits or broadcasts at least one data item, for example, including first data corresponding to the first SIB1 and / or second data corresponding to the second SIB1, to ensure that the terminal device can acquire the first SIB1 and / or the second SIB1. It is assumed that the first SIB1 is an SIB1 associated with the secure mode, and the second SIB1 is an SIB1 associated with the normal mode. If the terminal device cannot acquire the second SIB1 or cannot access the network based on the second SIB1 due to compatibility issues, the terminal device can still acquire the first SIB1 and access the network based on the first SIB1. This can ensure a basic communication channel between the terminal device and the network device, so that basic communication can be performed between the terminal device and the network device. Different SIB1s are scheduled by independent DCIs. For example, the first data is scheduled based on the first DCI, and the second data is scheduled based on the second DCI. This can solve the problem of the network device scheduling different SIB1s. This can ensure that the terminal device can acquire the first SIB1 and / or the second SIB1. For the terminal device PHY layer or MAC layer, the DCI used to schedule different SIB1s is distinguished based on the first indication information in the DCI, the scrambling information of the DCI, the DCI format, the time domain resource for the DCI, or the frequency domain resource for the DCI. In this way, the terminal device can accurately identify the content scrambled by the DCI and correctly perform HARQ combining to improve the reliability of data reception. For the terminal device RRC layer, the terminal device can accurately identify the content included in the first message based on the second indication information, the inter-layer interaction (i.e., the third indication information), or the logical channel in the first message and correctly perform RRC decoding to obtain accurate information.Furthermore, whether the network device should transmit the first data is indicated in the MIB, the DCI for scheduling the second data, the DCI for scheduling the third data, or the second data, which helps to save energy for the terminal device.

[0287] 11 is another schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 11, the communication method includes the following steps S1101 to S1106.

[0288] S1101: A terminal device receives third downlink control information DCI from a network device, and the third DCI is used to schedule at least two pieces of data, or the third DCI is used to schedule second data and a fourth DCI.

[0289] Accordingly, the network device may transmit or broadcast a third DCI. The scrambling information of the third DCI may be SI-RNTI, a newly defined RNTI, etc. This is not limited here. The DCI format of the third DCI may be DCI format 1_0, a newly defined DCI format, etc. This is not limited here.

[0290] The fourth DCI is used to schedule the first data. Compared with the solution in which at least two data are scheduled by the third DCI, the scheduling mode in which the second data and the fourth DCI are scheduled by the third DCI is more flexible.

[0291] For ease of understanding, an example in which at least two data include first data and second data is mainly used below for detailed description in this embodiment of the present application. For understanding the first data and second data in this embodiment of the present application, please refer to the relevant description of the first data and second data in step S901 of Figure 9. Details will not be described again here.

[0292] The following specifically describes a solution in which the third DCI is used to schedule at least two pieces of data, including first data and second data, where the first data includes a first SIB1 and the second data includes a second SIB1.

[0293] For example, Figure 12 is a diagram of a scheduling mode according to an embodiment of the present application. As shown in Figure 12, a network device may schedule at least two SIB1s or at least two pieces of data corresponding to at least two SIB1s by using one DCI. For example, the DCI shown in Figure 12 may be used to schedule data corresponding to a second SIB1 and data corresponding to a first SIB1. Specifically, the terminal device may determine, based on the DCI, resource information for the data corresponding to the second SIB1 and resource information for the data corresponding to the first SIB1. In other words, the terminal device may determine, based on the DCI, resource information corresponding to the second data and resource information corresponding to the first data.

[0294] Specifically, the third DCI includes scheduling information of the second data. For example, resource information of the second data (e.g., time domain resource information and / or frequency domain resource information) is configured in the third DCI. It should be noted that the method of indicating the resource information of the second data in the third DCI is not limited in the present application, and direct indication or indirect indication may be performed. The scheduling information in this embodiment of the present application may include one or more of the following: resource information, transport block size (TBS), modulation and coding scheme (MCS), etc.

[0295] Optionally, the scheduling information of the first data may be dynamically configured in the third DCI (this may be referred to as dynamic configuration), or the scheduling information of the first data may be statically configured (this may be referred to as static configuration), or the scheduling information of the first data may be semi-statically configured (this may be referred to as semi-static configuration), which is not limited in the present application.

[0296] Dynamic configuration may be understood as scheduling information of the first data being configured in the third DCI, for example, the third DCI carrying or including information regarding time domain resources and frequency domain resources for the first data.

[0297] The third DCI may carry or include information regarding the time domain resource for the first data by direct indication and / or indirect indication. "The third DCI may carry or include information regarding the time domain resource for the first data by direct indication" may be understood as or indicate that the information regarding the time domain resource for the first data is directly set in the third DCI (e.g., the information regarding the time domain resource for the first data may include any one or more of the following: the start of the time domain resource for the first data, the length of the time domain resource for the first data, and the end of the time domain resource for the first data). "The third DCI may carry or include information regarding the time domain resource for the first data by indirect indication" may be understood as or indicate any one of the following implementations:

[0298] (1) Information regarding the interval between the time domain resource for the third DCI and the time domain resource for the first data is indicated in the third DCI.

[0299] (2) Information regarding the interval between the time domain resource for the second data and the time domain resource for the first data is indicated in the third DCI.

[0300] The third DCI may carry or include information about the frequency domain for the first data by direct indication and / or indirect indication. For an understanding of "the third DCI may carry or include information about the frequency domain resource for the first data by direct indication", please refer to the above description of "the third DCI may carry or include information about the time domain resource for the first data by direct indication", provided that "time domain" is replaced with "frequency domain". Details will not be described again here. Correspondingly, for an understanding of "the third DCI may carry or include information about the time domain resource for the first data by indirect indication", please refer to the above description of "the third DCI may carry or include information about the time domain resource for the first data by indirect indication", provided that "time domain" is replaced with "frequency domain". Details will not be described again here.

[0301] It should be noted that in this embodiment of the present application, the interval between time domain resources may be of various granularities, such as slots, symbols, subframes, or frames, which are specifically determined based on actual application scenarios and are not limited herein. The interval between frequency domain resources may be of various granularities, such as carriers or frequency bands, which are specifically determined based on actual application scenarios and are not limited herein.

[0302] It should be noted that the time domain starting point of the "interval between the time domain resource for the third DCI and the time domain resource for the first data" may be any one of the following: the start of the time domain resource for the third DCI, the end of the time domain resource for the third DCI, a point before the start of the time domain resource for the third DCI, a point after the end of the time domain resource for the third DCI, the symbol / slot / subframe / frame to which the time domain resource for the third DCI belongs, the start of the symbol / slot / subframe / frame to which the time domain resource for the third DCI belongs, the end of the symbol / slot / subframe / frame to which the time domain resource for the third DCI belongs, a point before the start of the symbol / slot / subframe / frame to which the time domain resource for the third DCI belongs, and a point after the end of the symbol / slot / subframe / frame to which the time domain resource for the third DCI belongs. The time-domain end point of the "interval between the time-domain resources for the third DCI and the time-domain resources for the first data" may be any one of the following: the start of the time-domain resources for the first DCI, the end of the time-domain resources for the first DCI, a point before the start of the time-domain resources for the first DCI, a point after the end of the time-domain resources for the first DCI, the symbol / slot / subframe / frame to which the time-domain resources for the first DCI belong, the start of the symbol / slot / subframe / frame to which the time-domain resources for the first DCI belong, the end of the symbol / slot / subframe / frame to which the time-domain resources for the first DCI belong, a point before the start of the symbol / slot / subframe / frame to which the time-domain resources for the first DCI belong, and a point after the end of the symbol / slot / subframe / frame to which the time-domain resources for the first DCI belong. Similarly, in understanding the "interval between the time-domain resources for the second data and the time-domain resources for the first data," it is sufficient to replace "the third DCI" with "the second data." Details will not be described again here.It should be noted that in this embodiment of the present application, the interval between the time domain resource for the second data and the time domain resource for the first data may alternatively be 0. In a possible implementation, the time domain resource for the second data may be the same as the time domain resource for the first data. The position order of the second data and the first data in the time domain is not limited in the present application.

[0303] The start point (or end point) of the "interval between the frequency domain resources for the third DCI and the frequency domain resources for the first data" may be any one of the following: the start of the frequency domain resources for the third DCI, the end of the frequency domain resources for the third DCI, the frequency before the start of the frequency domain resources for the third DCI, and the frequency after the end of the frequency domain resources for the third DCI. The end point (or start point) of the "interval between the frequency domain resources for the third DCI and the frequency domain resources for the first data" may be any one of the following: the start of the frequency domain resources for the first DCI, the end of the frequency domain resources for the first DCI, the frequency before the start of the frequency domain resources for the first DCI, and the frequency after the end of the frequency domain resources for the first DCI. Note that in this embodiment of the present application, the interval between the frequency domain resources for the third DCI and the frequency domain resources for the first data may alternatively be 0. In a possible implementation, the frequency domain resources for the third DCI may be the same as the frequency domain resources for the first data. It can be understood that the position order of the third DCI and the first data in the frequency domain is not limited in the present application. Similarly, when understanding "an interval between a frequency domain resource for the second data and a frequency domain resource for the first data," it is sufficient that "the third DCI" is replaced with "the second data." Details will not be described again here.

[0304] For example, the interval between the time domain resource for the third DCI and the time domain resource for the first data may be the interval between the end of the time domain resource for the third DCI and the start of the time domain resource for the first data, or may be the interval between the start of the time domain resource for the third DCI and the start of the time domain resource for the first data. This is not limited here. For example, the interval between the time domain resource for the third DCI and the time domain resource for the first data may be the interval between the start slot of the slot to which the time domain resource for the third DCI belongs and the start slot of the slot to which the time domain resource for the first data belongs, or may be the interval between the end slot of the slot to which the time domain resource for the third DCI belongs and the end slot of the slot to which the time domain resource for the first data belongs.

[0305] Static configuration may be understood as determining scheduling information for the first data based on first a priori information.

[0306] In a possible implementation, the first a priori information includes first interval information and second interval information. The first a priori information may be configured by a network device, for example, by using an RRC message, or may be pre-configured or defined in a protocol. This is not limited herein.

[0307] The first interval information includes information about an interval between a time domain resource for the third DCI and a time domain resource for the first data, or information about an interval between a time domain resource for the second data and a time domain resource for the first data. The second interval information includes information about an interval between a frequency domain resource for the third DCI and a frequency domain resource for the first data, or information about an interval between a frequency domain resource for the second data and a frequency domain resource for the first data. Optionally, the first a priori information may further include any one or more of information about a length of a time domain resource for the first data, information about a length of a frequency domain resource for the first data, information about an MCS, and information about a TBS.

[0308] In another possible implementation, the first a priori information includes information about time domain resources and frequency domain resources for the first data. Specifically, in the case of static configuration, the third DCI does not include resource information of the first data, but the terminal device may determine resource information of the first data based on the first a priori information and resource information of the third DCI or resource information of the second data.

[0309] The semi-static configuration may be understood as information about time domain resources for the first data being dynamically configured in the third DCI, and information about frequency domain resources for the first data (or second interval information) being statically configured. Alternatively, the semi-static configuration may be understood as information about frequency domain resources for the first data being dynamically configured in the third DCI, and information about time domain resources for the first data (or first interval information) being statically configured.

[0310] The following specifically describes a solution in which the third DCI is used to schedule the second data and the fourth data.

[0311] The fourth DCI is used to schedule the first data, where the first data includes a first SIB1 and the second data includes a second SIB1.

[0312] For example, Figure 13 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 13, the DCI corresponding to the data corresponding to the second SIB1 is the third DCI in this embodiment of the present application, and the DCI corresponding to the data corresponding to the first SIB1 is the fourth DCI in this embodiment of the present application. Specifically, for ease of description, the DCI corresponding to the data corresponding to the second SIB1 in Figure 13 may be referred to as the third DCI, and the DCI corresponding to the data corresponding to the first SIB1 in Figure 13 may be referred to as the fourth DCI. The third DCI is used to schedule the fourth DCI and the data corresponding to the second SIB1, and the fourth DCI is used to schedule the data corresponding to the first SIB1. The terminal device may determine resource information for the data corresponding to the second SIB1 and resource information for the fourth DCI based on the third DCI.

[0313] Specifically, the third DCI includes scheduling information of the second data. For example, resource information of the second data (for example, time domain resource information and / or frequency domain resource information) is configured in the third DCI. Note that the method of indicating the resource information of the second data in the third DCI is not limited in the present application, and direct indication or indirect indication may be performed.

[0314] The scheduling information of the fourth DCI may be dynamically configured in the third DCI (this may be referred to as dynamic configuration), or the scheduling information of the fourth DCI may be statically configured (this may be referred to as static configuration), or the scheduling information of the fourth DCI may be semi-statically configured (this may be referred to as semi-static configuration), which is not limited in the present application.

[0315] It should be noted that for understanding that the scheduling information of the fourth DCI is dynamically set, statically set, or quasi-statically set, reference may be made to the above description of the scheduling information of the first data being dynamically set, statically set, or quasi-statically set, provided that "first data" is replaced with "fourth DCI." Details will not be described again here.

[0316] Optionally, in some possible implementations, in a scenario where a network device may schedule two SIB1s, ie, a first SIB1 and a second SIB1, the following further describes two other scheduling modes.

[0317] In the first scheduling mode, alternatively, one SIB1 may be scheduled based on one DCI. For example, the SIB1 may be a second SIB1. Then, another SIB1 is scheduled based on the second SIB1. For example, the other SIB1 may be the first SIB1. Specifically, one SIB1 may include scheduling information for another SIB1, or data corresponding to one SIB1 may include scheduling information for the other SIB1.

[0318] For example, Figure 14 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 14, the DCI for the data corresponding to the second SIB1 is used to schedule the second SIB1. Alternatively, this can be written as follows: the DCI corresponding to the data corresponding to the second SIB1 is used to schedule the data corresponding to the second SIB1. The data corresponding to the second SIB1 or the second SIB1 includes scheduling information for the first SIB1. Alternatively, this can be understood as the data corresponding to the second SIB1 or the second SIB1 may schedule the first SIB1, or the data corresponding to the second SIB1 or the second SIB1 includes scheduling information for the data corresponding to the first SIB1, or the data corresponding to the second SIB1 or the second SIB1 may schedule the first SIB1 or the data corresponding to the first SIB1. The terminal device may determine a position of a PDSCH corresponding to the data corresponding to the second SIB1 based on DCI corresponding to the data corresponding to the second SIB1, and may determine a position of a PDSCH corresponding to the data corresponding to the first SIB1 based on the data corresponding to the second SIB1 or the second SIB1. The scheduling information of the first SIB1 may be dynamically configured in the data corresponding to the second SIB1 or the second SIB1, or the scheduling information of the first SIB1 may be statically configured, or the scheduling information of the first SIB1 may be semi-statically configured. This is not limited here. It should be noted that for understanding that the scheduling information of the first SIB1 may be dynamically set in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information of the first SIB1 may be statically set, or the scheduling information of the first SIB1 may be semi-statically set, refer to the above description in Figure 12 that the scheduling information of the first data may be dynamically set in the third DCI, or the scheduling information of the first data may be statically set, or the scheduling information of the first data may be semi-statically set. Details will not be described again here.

[0319] Optionally, in some possible implementations, the network device may further transmit fifth indication information to the terminal device, where the fifth indication information may indicate that the second SIB1 is present on the network device or should be transmitted by the network device. The fifth indication information may be carried in an MIB transmitted by the network device to the terminal device, or the fifth indication information may be carried in a DCI used to schedule the second SIB1, etc. This is not limited here. Optionally, whether the first SIB1 is present in the network may be further determined based on whether the second SIB1 or data corresponding to the second SIB1 includes scheduling information for the first SIB1.

[0320] In the second scheduling mode, one SIB1 may be scheduled based on one DCI. For example, the SIB1 may be the second SIB1. Then, the DCI for another SIB1 is scheduled based on the SIB1. For example, the other SIB1 may be the first SIB1. Specifically, one SIB1 may include scheduling information for the DCI of the other SIB1, or data corresponding to one SIB1 may include scheduling information for the DCI for the other SIB1.

[0321] For example, Figure 15 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 15, DCI for data corresponding to the second SIB1 is used to schedule the data corresponding to the second SIB1, and the data corresponding to the second SIB1 includes scheduling information for DCI corresponding to data corresponding to the first SIB1. Specifically, the data corresponding to the second SIB1 or the second SIB1 can schedule DCI corresponding to data corresponding to the first SIB1, and DCI corresponding to data corresponding to the first SIB1 is used to schedule the data corresponding to the first SIB1. The terminal device may determine a position of a PDSCH corresponding to data corresponding to the second SIB1 or the second SIB1 based on the DCI corresponding to the second SIB1 or the DCI corresponding to data corresponding to the second SIB1, may determine a position of a DCI corresponding to data corresponding to the first SIB1 based on the data corresponding to the second SIB1 or the second SIB1, and may determine a position of a PDSCH corresponding to data corresponding to the first SIB1 based on the DCI corresponding to data corresponding to the first SIB1. The scheduling information of the DCI corresponding to the first SIB1 may be dynamically configured in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information of the DCI corresponding to the data corresponding to the first SIB1 may be statically configured, or the scheduling information of the DCI corresponding to the data corresponding to the first SIB1 may be semi-statically configured. This is not limited here. Note that, for understanding that the scheduling information of the DCI corresponding to the data corresponding to the first SIB1 may be dynamically configured in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information of the DCI corresponding to the data corresponding to the first SIB1 may be statically configured, or the scheduling information of the DCI corresponding to the data corresponding to the first SIB1 may be semi-statically configured, refer to the above description in FIG. 12 that the scheduling information of the first data may be dynamically configured in the third DCI, or the scheduling information of the first data may be statically configured, or the scheduling information of the first data may be semi-statically configured.The details will not be described again here.

[0322] Optionally, in some possible implementations, the network device may further transmit fifth indication information to the terminal device, where the fifth indication information may indicate that the second SIB1 is present on the network device or should be transmitted by the network device. The fifth indication information may be carried in an MIB transmitted by the network device to the terminal device, or the fifth indication information may be carried in a DCI used to schedule the second SIB1, etc. This is not limited here. Optionally, whether the first SIB1 (i.e., the first SIB1) is present in the network may be further determined based on whether the second SIB1 or data corresponding to the second SIB1 includes scheduling information for the first SIB1.

[0323] In addition, compared to the scheduling mode shown in Figure 14, in Figure 15, the time domain resources, frequency domain resources, MCS, TBS, etc. for data corresponding to the first SIB1 can be flexibly indicated in the DCI for scheduling the first SIB1, making scheduling more flexible.

[0324] Optionally, in some possible implementations, the network device may alternatively schedule three or more SIBs. Specifically, in scenarios in which the network device may alternatively schedule three or more SIBs, the following specifically describes four scheduling modes.

[0325] For ease of understanding, data corresponding to four SIB1s, i.e., data corresponding to SIB1 corresponding to version N, data corresponding to SIB1 corresponding to version N+1, data corresponding to SIB1 corresponding to version N+2, and data corresponding to SIB1 corresponding to version N+3, are mainly used below as examples for explanation. Among the four SIB1s, data corresponding to SIB1 corresponding to version N may be understood as data corresponding to SIB1 of the earlier version, and data corresponding to SIB1 corresponding to each of versions N+1 to N+3 may be understood as data corresponding to SIB1 of the later version. For ease of description, data corresponding to SIB1 corresponding to version N may be referred to as SIB1 corresponding to version N, data corresponding to SIB1 corresponding to version N+1 may be referred to as SIB1 corresponding to version N+1, data corresponding to SIB1 corresponding to version N+2 may be referred to as SIB1 corresponding to version N+2, and data corresponding to SIB1 corresponding to version N+3 may be referred to as SIB1 corresponding to version N+3.

[0326] In the first scheduling mode, a level-by-level scheduling mode may be used in a scenario where a network device schedules three or more SIBs. Specifically, an earlier version of SIB1 includes scheduling information for a later version of SIB1. Alternatively, this can be written as follows: data corresponding to an earlier version of SIB1 includes scheduling information for a later version of SIB1.

[0327] The scheduling information of the later version SIB1 may be dynamically configured in the earlier version SIB1 or data corresponding to the earlier version SIB1, or may be statically configured, or may be semi-statically configured. This is not limited here. Note that for understanding that the scheduling information of the later version SIB1 may be dynamically configured in the earlier version SIB1 or data corresponding to the earlier version SIB1, or may be statically configured, or may be semi-statically configured, refer to the above description in Figure 12 that the scheduling information of the first data may be dynamically configured in the third DCI, or may be statically configured, or may be semi-statically configured. Details will not be described again here.

[0328] For example, Figure 16 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 16, a DCI for SIB1 of version N is used to schedule SIB1 of version N or data corresponding to SIB1 of version N, SIB1 of version N can schedule data corresponding to SIB1 of version N+1 or SIB1 of version N+1, SIB1 of version N+1 can schedule data corresponding to SIB1 of version N+2 or SIB1 of version N+2, and SIB1 of version N+2 can schedule data corresponding to SIB1 of version N+3 or SIB1 of version N+3. Specifically, the DCI for SIB1 of version N includes scheduling information for SIB1 of version N, SIB1 of version N includes scheduling information for SIB1 of version N+1, SIB1 of version N+1 includes scheduling information for SIB1 of version N+2, and SIB1 of version N+2 includes scheduling information for SIB1 of version N+3.

[0329] Optionally, in the second scheduling mode, a level-crossing scheduling mode may be used in a scenario where a network device schedules three or more SIBs 1. For example, an earlier version of SIB 1 may include scheduling information for one or more later versions of SIB 1, or data corresponding to an earlier version of SIB 1 may include scheduling information for one or more later versions of SIB 1.

[0330] The scheduling information of one or more SIB1s of the later version may be dynamically configured in the SIB1s of the earlier version or in data corresponding to the SIB1s of the earlier version, or may be statically configured, or may be semi-statically configured. This is not limited here. Note that for understanding that the scheduling information of one or more SIB1s of the later version may be dynamically configured in the SIB1s of the earlier version or in data corresponding to the SIB1s of the earlier version, or may be statically configured, or may be semi-statically configured, refer to the above description in FIG. 12 that the scheduling information of the first data may be dynamically configured in the third DCI, or may be statically configured, or may be semi-statically configured. Details will not be described again here. Optionally, the version of the SIB1s of the later version may be further indicated in the SIB1s of the basic version.

[0331] For example, Figure 17 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 17, a DCI for SIB1 of version N is used to schedule SIB1 of version N or data corresponding to SIB1 of version N, SIB1 of version N can schedule SIB1 of version N+1 and SIB1 of version N+2 or data corresponding to SIB1 of version N+1 and data corresponding to SIB1 of version N+2, SIB1 of version N+1 can schedule SIB1 of version N+2 and SIB1 of version N+3 or data corresponding to SIB1 of version N+2 and data corresponding to SIB1 of version N+3, and SIB1 of version N+2 can schedule SIB1 of version N+3 or data corresponding to SIB1 of version N+3. Specifically, the DCI for SIB1 of version N includes scheduling information of SIB1 of version N, SIB1 of version N includes scheduling information of SIB1 of version N+1 and SIB1 of version N+2, SIB1 of version N+1 includes scheduling information of SIB1 of version N+2 and SIB1 of version N+3, and SIB1 of version N+2 includes scheduling information of SIB1 of version N+3.

[0332] It should be noted that, compared with the level-by-level scheduling mode, in the level-crossing scheduling mode, reception of some version SIB1s may be skipped. For example, Figure 18 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 18, the DCI for SIB1 of version N is used to schedule SIB1 of version N or data corresponding to SIB1 of version N, SIB1 of version N is used to schedule SIB1 of version N+2 or data corresponding to SIB1 of version N+2, and SIB1 of version N+2 is used to schedule SIB1 of version N+3 or data corresponding to SIB1 of version N+3. Specifically, the DCI for SIB1 of version N includes scheduling information for SIB1 of version N, SIB1 of version N includes scheduling information for SIB1 of version N+2, and SIB1 of version N+2 includes scheduling information for SIB1 of version N+3.

[0333] Optionally, in the third scheduling mode, in a scenario where a network device schedules three or more SIB1s, a scheduling mode in which one DCI is used to schedule SIB1s of all versions may be alternatively used. For example, Figure 19 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 19, the network device may schedule SIB1 of version N, SIB1 of version N+1, SIB1 of version N+2, and SIB1 of version N+3 by using one DCI. Alternatively, the network device may schedule data corresponding to SIB1 of version N, data corresponding to SIB1 of version N+1, data corresponding to SIB1 of version N+2, and data corresponding to SIB1 of version N+3 by using one DCI. Specifically, the DCI includes scheduling information for SIB1 of version N, SIB1 of version N+1, SIB1 of version N+2, and SIB1 of version N+3, or the DCI includes scheduling information for data corresponding to SIB1 of version N, data corresponding to SIB1 of version N+1, data corresponding to SIB1 of version N+2, and data corresponding to SIB1 of version N+3. The scheduling information for SIB1 of the later version may be dynamically, statically, or semi-statically configured in the DCI. Optionally, the version of SIB1 of the later version may be further indicated in the DCI.

[0334] Optionally, in the fourth scheduling mode, in a scenario where a network device schedules three or more SIBs, a hybrid scheduling mode may alternatively be used. For example, one DCI may include scheduling information for multiple versions of SIBs (e.g., earlier versions and / or several later versions), where the earlier version of SIBs or data corresponding to the earlier version of SIBs need not include any scheduling information for the later version of SIBs, and the later version of SIBs scheduled by the DCI or data corresponding to the later version of SIBs may include scheduling information for further later versions of SIBs.

[0335] For example, Figure 20 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 20, a network device can schedule both SIB1 of version N and SIB1 of version N+1 by using one DCI, SIB1 of version N+1 can schedule SIB1 of version N+2, and SIB1 of version N+2 can schedule SIB1 of version N+3. Alternatively, a network device can schedule both data corresponding to SIB1 of version N and data corresponding to SIB1 of version N+1 by using one DCI, data corresponding to SIB1 of version N+1 can schedule data corresponding to SIB1 of version N+2, and data corresponding to SIB1 of version N+2 can schedule data corresponding to SIB1 of version N+3.

[0336] As another example, Figure 21 is a diagram of another scheduling mode according to an embodiment of the present application. As shown in Figure 21, a network device can schedule both SIB1 of version N and SIB1 of version N+1 by using one DCI, SIB1 of version N+1 can schedule SIB1 of version N+2 and SIB1 of version N+3, and SIB1 of version N+2 can schedule SIB1 of version N+3. Alternatively, a network device can schedule both data corresponding to SIB1 of version N and data corresponding to SIB1 of version N+1 by using one DCI, data corresponding to SIB1 of version N+1 can schedule data corresponding to SIB1 of version N+2 and data corresponding to SIB1 of version N+3, and data corresponding to SIB1 of version N+2 can schedule data corresponding to SIB1 of version N+3.

[0337] It should be noted that in the examples of Figures 16 to 21, SIB1 of version N may be understood as SIB1 of the base version, and SIB1 other than SIB1 of version N, for example, SIB1 of version N+1 to version N+3, are later version SIB1.

[0338] S1102: The terminal device determines resource information of the first data and / or resource information of the second data based on the third DCI.

[0339] In some possible implementations, the terminal device may determine resource information of the first data and / or resource information of the second data based on the third DCI. Note that step S1102 is an optional step.

[0340] S1103a: The terminal device determines resource information of the fourth DCI and / or resource information of the second data based on the third DCI.

[0341] In some possible implementations, the terminal device may determine resource information of the fourth DCI and / or resource information of the second data based on the third DCI. Note that step S1103a may also be an optional step.

[0342] S1103b: The terminal device receives a fourth DCI based on the third DCI.

[0343] In some possible implementations, the terminal device may receive a fourth DCI based on the third DCI. Note that step S1103b may also be an optional step.

[0344] S1103c: The terminal device determines resource information of the first data based on the fourth DCI.

[0345] In some possible implementations, the terminal device may determine the resource information of the first data based on the fourth DCI. Note that step S1103c may also be an optional step.

[0346] S1104: The terminal device receives the first data and / or the second data from the network device.

[0347] In some possible implementations, one possible understanding of the description of the terminal device receiving the first data and / or the second data from the network device is as follows: the terminal device receives the first data and / or the second data from the network device based on the third DCI. Another possible understanding is as follows: the terminal device receives the second data from the network device based on the third DCI, and / or the terminal device receives the first data from the network device based on the fourth DCI.

[0348] In some possible implementations, the terminal device may receive first data and / or second data from the network device based on the third DCI. For example, it is assumed that the first operation mode is a secure mode and the second operation mode is a normal mode. If the operation mode supported by the terminal device is the first operation mode, the terminal device may receive the first data based on the third DCI. Optionally, if the operation mode supported by the terminal device is the second operation mode and a full configuration is used for the second SIB1, the terminal device may receive the second data based on the third DCI. Optionally, if the operation mode supported by the terminal device is the second operation mode and a delta configuration is used for the second SIB1, the terminal device may receive the first data and the second data based on the third DCI and combine them to obtain the complete second SIB1.

[0349] Specifically, for decoding by the terminal device, based on the different scheduling modes described in step S1101, the terminal device (e.g., the MAC layer of the terminal device or the PHY layer of the terminal device) may successfully receive or decode data scheduled by the third DCI. When the third DCI is used to schedule at least two pieces of data (e.g., first data and second data), the terminal device (e.g., the MAC layer of the terminal device or the PHY layer of the terminal device) may receive the first data and / or the second data, i.e., the data corresponding to the first SIB1 and / or the second SIB1 in FIG. 12, according to the implementation shown in FIG. 12 in step S1101. When the third DCI is used to schedule the second data and the fourth DCI, the terminal device (e.g., the MAC layer of the terminal device or the PHY layer of the terminal device) may receive the first data and / or the second data, i.e., the data corresponding to the first SIB1 and / or the second SIB1 in FIG. 13, according to the implementation shown in FIG. 13 in step S1101.

[0350] S1105: The terminal device determines, based on the first data, that the first data includes a first SIB1, and / or the terminal device determines, based on the second data, that the second data includes a second SIB1.

[0351] It should be noted that for an implementation in which the terminal device determines, based on the first data, that the first data includes the first SIB1 and / or determines, based on the second data, that the second data includes the second SIB1, reference may be made to the above description of determining, based on the first data, that the first data includes the first SIB1 in step S904 of FIG. Details will not be described again here.

[0352] S1106: The terminal device receives or acquires fourth instruction information from the network device.

[0353] It should be noted that for the description of the fourth indication information in this embodiment of the present application, reference is made to the description of the fourth indication information in step S905 of FIG. 9 . Details will not be described again here. It should be noted that the fourth indication information may be carried in the MIB transmitted by the network device to the terminal device, or the fourth indication information may be carried in the third DCI. This is not limited here. For example, the terminal device may obtain the fourth indication information and determine, based on the fourth indication information, whether the third DCI schedules the first data and the second data. Furthermore, the terminal device may receive the first data. For example, the terminal device may obtain the fourth indication information and determine, based on the fourth indication information, whether the third DCI schedules the second data and the fourth DCI. Furthermore, the terminal device may receive the fourth DCI and the first data.

[0354] It should be noted that the above steps S1101 and S1102 may each be considered as an independent embodiment, or may be combined as an optional step with one or more steps in this embodiment of the present application. This is not a limitation hereof. The above steps S1101 and S1103a to S1103c, steps S1101, S1103a, and S1103b, or steps S1101 and S1103a may each be considered as an independent embodiment, or may be combined as an optional step with one or more steps in this embodiment of the present application. This is not a limitation hereof. The above steps S1104 and S1105 may each be considered as an independent embodiment, or may be combined as an optional step with one or more steps in this embodiment of the present application. This is not a limitation hereof. The above step S1106 may each be considered as an independent embodiment, or may be combined as an optional step with one or more steps in this embodiment of the present application. This is not a limitation hereof. It should be noted that the numbering order of the steps in this embodiment of the present application does not indicate the order in which the steps are executed. The order in which the steps are executed is specifically determined based on the actual application scenario, and is not limited here. For example, S1105 may be executed before or after S1103b. This is not limited.

[0355] In this embodiment of the present application, the network device transmits or broadcasts first data corresponding to the first SIB1, second data corresponding to the second SIB1, and / or the like to ensure that the terminal device can acquire the first SIB1 and / or the second SIB1. It is assumed that the first SIB1 is an SIB1 associated with the secure mode, and the second SIB1 is an SIB1 associated with the normal mode. If the terminal device cannot acquire the second SIB1 or cannot access the network based on the second SIB1 due to compatibility issues, the terminal device can still acquire the first SIB1 and access the network based on the first SIB1. This can ensure a basic communication channel between the terminal device and the network device, so that basic communication can be performed between the terminal device and the network device. In this embodiment of the present application, one DCI (i.e., the third DCI) is used to schedule two SIBs, or the DCI for the second SIB is used to schedule the DCI for the first SIB, or data corresponding to the second SIB or the second SIB includes scheduling information for the first SIB, or data corresponding to the second SIB or the second SIB includes scheduling information for the DCI for the first SIB. This provides an effective method for scheduling different SIBs. Optionally, in this way, the terminal device can accurately identify the data, so that it can accurately perform HARQ combining to improve the reliability of data reception. For the RRC layer of the terminal device, different SIBs are distinguished based on the indication information, the inter-layer interaction indication (i.e., the third indication information), or the logical channel in the RRC message. In this way, the terminal device can accurately identify the data included in the RRC message, so that it can accurately perform RRC decoding to obtain the correct information, which improves communication reliability. Furthermore, whether the network device should transmit the first data or the second data is indicated in the third DCI or MIB for scheduling, which helps to save energy of the terminal device.

[0356] FIG. 22 is a schematic flowchart of a communication method according to an embodiment of the present application.

[0357] S2201: A terminal device receives sixth downlink control information DCI from a network device.

[0358] In some possible implementations, a sixth DCI is received from a network device, and the sixth DCI is used to schedule fourth data, where the fourth data includes a SIB1 set. The SIB1 set includes at least one SIB1. The at least one SIB1 may include SIB1s associated with different versions or different operation modes. Specifically, different SIB1s may be mapped to one SIB1 set, and then the SIB1 set is scheduled by one DCI. For example, the at least one SIB1 may include a first SIB1. As another example, the SIB1 set may include a first SIB1 and a second SIB1. Note that for understanding the first SIB1 and the second SIB1, in this embodiment of the present application, reference may be made to the description of the first SIB1 and the second SIB1 in FIG. 9. Details will not be described again here.

[0359] It should be noted that in a possible implementation, the SIB1 set or at least one SIB1 may include a basic version of SIB1, which is not a limitation here. In a possible implementation, the SIB1 set or at least one SIB1 may include one or more later versions of SIB1, which is not a limitation here.

[0360] For example, Figure 23 is a diagram of a scenario in which an SIB1 set is scheduled based on a sixth DCI according to an embodiment of the present application. As shown in Figure 23, the SIB1 set scheduled by the DCI includes a first SIB1 and a second SIB1. The first SIB1 may be understood as an earlier version of the SIB1, and the second SIB1 may be understood as a later version of the SIB1. Specifically, the first SIB1 and the second SIB1 may be mapped to the SIB1 set, and the SIB1 set or data corresponding to the SIB1 set (i.e., the fourth data) is scheduled by the DCI (i.e., the sixth DCI).

[0361] As another example, Figure 24 is a diagram of another scenario in which a SIB1 set is scheduled based on the sixth DCI according to an embodiment of the present application. As shown in Figure 24, data corresponding to the SIB1 set scheduled by the DCI includes SIB1 of version N, SIB1 of version N+1, SIB1 of version N+2, and SIB1 of version N+3. SIB1 of version N may be understood as the SIB1 of the base version, and SIB1 of version N+1 to SIB1 of version N+3 may be understood as SIB1s of multiple later versions. Specifically, SIB1 of version N, SIB1 of version N+1, SIB1 of version N+2, and SIB1 of version N+3 may be mapped to the SIB1 set, and the SIB1 set or data corresponding to the SIB1 set is scheduled by the sixth DCI.

[0362] S2202: The terminal device determines, based on the sixth DCI, that the fourth data includes the SIB1 set.

[0363] Step S2202 may be understood to be performed in the PHY layer or MAC layer of the terminal device, or may be performed in another layer (e.g., another newly defined layer). This is specifically determined based on an actual application scenario and is not limited thereto. It should be noted that step S2202 is an optional step. It should be noted that for a terminal device, determining whether the sixth DCI includes an SIB1 set or determining whether the sixth DCI schedules an SIB1 set or an SI message may be performed according to the solution in FIG. 9 (e.g., any one of Implementations 1 to 5 in step S902 of FIG. 9). Specifically, in the five implementations in FIG. 9, determining that the first data includes the first SIB1 based on the first DCI may be replaced by determining that the fourth data includes an SIB1 set based on the sixth DCI in this embodiment for ease of understanding. Details will not be described again here.

[0364] S2203: The terminal device receives fourth data from the network device based on the sixth DCI.

[0365] Step S2203 may be understood to be performed in the PHY layer or MAC layer of the terminal device, or may be performed in other layers (e.g., other newly defined layers). This is specifically determined based on actual application scenarios and is not limited here. It can be understood that the terminal device receiving the fourth data from the network device based on the sixth DCI can be understood as follows: the terminal device receives the fourth data from the network device based on the scheduling information in the sixth DCI. It should be noted that step S2203 is an optional step.

[0366] S2204: The terminal device determines, based on the fourth data, that the fourth data includes the SIB1 set.

[0367] In some possible implementations, after the terminal device (e.g., a PHY layer, a MAC layer, or another layer of the terminal device) receives the fourth data from the network device based on the sixth DCI and delivers all or a part of the fourth data to an upper layer of the terminal device (e.g., an RRC layer or another layer of the terminal device; for ease of description, the RRC layer of the terminal device is hereinafter used as an example for explanation), the RRC layer of the terminal device may further decode content included in or content corresponding to the fourth data based on the fourth data. Based on this, the RRC layer of the terminal device may determine that the fourth data includes the SIB1 set. Note that for the implementation of determining that the fourth data includes the SIB1 set based on the fourth data by the terminal device, any one of Implementations (1) to (3) in step S904 of FIG. 9 may be referred to. Specifically, in the three implementations of Figure 9, determining that the first data includes the first SIB1 based on the first data may be replaced by determining that the fourth data includes the SIB1 set based on the fourth data for ease of understanding in this embodiment. Details will not be described again here. Note that step S2204 may be an optional step.

[0368] S2205: The terminal device determines SIB1 included in the SIB1 set based on the fourth data.

[0369] In some possible implementations, the terminal device determines that the fourth data or the fourth message includes a SIB1 set, and the terminal device needs to further determine a specific SIB1 or multiple specific SIB1s included in the SIB1 set. The specific SIB1 or multiple specific SIB1s, a specific version of a SIB1 or multiple SIB1s of specific versions, or a SIB1 associated with a specific operating mode or multiple SIB1s associated with a specific mode included in the fourth data, the fourth message, or the SIB1 set can be identified in one of the following two implementations. "The terminal device determines the SIB1 included in the SIB1 set based on the fourth data" can be understood as follows: the terminal device determines the SIB1 included in the SIB1 set based on the fourth message, or the terminal device determines the SIB1 included in the SIB1 set based on the SIB1 set, or the terminal device determines the SIB1 included in the fourth message based on the fourth data, or the terminal device determines the SIB1 included in the fourth message based on the fourth message, or the terminal device determines the SIB1 included in the fourth message based on the SIB1 set, or the terminal device determines the SIB1 included in the fourth data based on the fourth data, or the terminal device determines the SIB1 included in the fourth data based on the fourth message, or the terminal device determines the SIB1 included in the fourth data based on the SIB1 set.

[0370] How the terminal device determines a specific SIB1 or multiple specific SIB1s included in the SIB1 set based on the fourth data will be described below in the first and second implementations.

[0371] In a first implementation, sixth indication information may be included in the fourth data, the fourth message, or the SIB1 set, and the sixth indication information indicates a specific SIB1 or multiple specific SIB1s included in the fourth data, the fourth message, or the SIB1 set.

[0372] Specifically, the sixth indication information may be carried in the fourth data transmitted by the network device to the terminal device, and the sixth indication information indicates a specific SIB1 or multiple specific SIB1s included in the fourth data, the fourth message, or the SIB1 set, a SIB of a specific version or multiple SIB1s of a specific version, or a SIB1 associated with a specific operating mode or multiple SIB1s associated with a specific operating mode, or indicates content included in the fourth data, the fourth message, or the SIB1 set.

[0373] The specific form of the instruction by the sixth instruction information may include any one of the following forms, which are not limited here.

[0374] Format 1: When the SIB1 set can include up to two SIB1s (e.g., a first SIB1 and a second SIB1), the sixth indication information may occupy one bit, and the sixth indication information indicates whether the first SIB1 exists, or whether only the second SIB1 exists, or whether the second SIB1 exists, or whether only the first SIB1 exists.

[0375] Format 2: When the SIB1 set can include three or more SIB1s, the sixth indication information may be implemented in the form of a bitmap, where one SIB1 corresponds to one bit, and each bit indicates whether the corresponding SIB1 exists. Optionally, when the indication is implemented in the form of a bitmap, to save bits, the SIB1 of the base version does not need to be indicated and is assumed to exist by default. Specifically, the bitmap only needs to indicate multiple later versions of the SIB1. For example, assume that the SIB1 set includes four versions of the SIB1, namely, SIB1 of version N, SIB1 of version N+1, SIB1 of version N+2, and SIB1 of version N+3. The SIB1 of version N is the base version SIB1, and the SIB1 of version N+1 to version N+3 are the later versions of the SIB1. Therefore, the bitmap is 4 bits long, corresponding sequentially from left to right to SIB1 of version N, SIB1 of version N+1, SIB1 of version N+2, and SIB1 of version N+3. Assuming that 0 indicates that SIB1 is not present and 1 indicates that SIB1 is present, the bitmap may be represented as 1111. Optionally, to save bits, the bitmap may be 3 bits long, and SIB1 of the base version may alternatively not be indicated. Specifically, SIB1 of the base version is considered to be explicitly present by default. In this case, the bitmap may be represented as 111.

[0376] Format 3: When the SIB1 set includes three or more SIB1s, the sixth indication information may alternatively be information indicating the presence of the latest version of SIB1 in order to save bits. Specifically, it is considered by default that the network should transmit all SIB1s of earlier versions than the latest version of SIB1. For example, the sixth indication information occupies four bits, where 0000 represents SIB1 of version R15, 0001 represents SIB1 of version R16, etc. Assuming the sixth indication information is 0001, it is determined that the SIB1 set includes SIB1 of version R16 and all SIB1 versions earlier than version R16.

[0377] In a second implementation, the terminal device obtains seventh indication information associated with the fourth message.

[0378] "The terminal device obtains the seventh indication information associated with the fourth message" can be understood as follows: the RRC layer of the terminal device obtains the seventh indication information associated with the fourth message from the lowest layer of the terminal device.

[0379] The seventh indication information indicates the fourth data, the fourth message, or the SIB1 included in the SIB1 set, or a specific SIB1 or a plurality of specific SIB1s. 7 Based on the indication information, the fourth data, the fourth message, or the SIB1 included in the SIB1 set is determined.

[0380] The "lowest layer of the terminal device" may include any one of the following: a PHY layer of the terminal device, a MAC layer of the terminal device, an RLC layer of the terminal device, or a PDCP layer of the terminal device, where the lowest layer of the terminal device may deliver the seventh indication information to the RRC layer on a layer-by-layer basis, or may deliver the seventh indication information to the RRC layer through one or more layers between the lowest layer of the terminal device and the RRC layer of the terminal device, or the terminal device may deliver the seventh indication information directly to the RRC layer of the terminal device.

[0381] It can be understood that the RRC layer of the terminal device not only acquires the fourth message but also acquires seventh indication information related to the fourth message. The RRC layer of the terminal device can determine the fourth data, the fourth message, or a specific SIB1 or multiple specific SIB1s included in the SIB1 set based on the seventh indication information. Note that the implementation of acquiring the fourth message by the RRC layer of the terminal device may be the same as or different from the implementation of acquiring the seventh indication information by the RRC layer of the terminal device. This is not limited in the present application.

[0382] Note that the seventh indication information does not have to be included in the fourth data. For example, the seventh indication information may be generated by the terminal device based on the sixth DCI. For example, if the seventh indication information is generated by a PHY layer of the terminal device, the seventh indication information may not be included in the fourth data. Alternatively, the seventh indication information may be included in the fourth data, for example, in any one of the following corresponding to the fourth data: a MAC subheader of a fourth MAC PDU, an RLC header of a fourth RLC PDU, and a PDCP header of a fourth PDCP PDU. For example, if the seventh indication information is generated by a MAC layer of the terminal device, the seventh indication information may be included in a MAC subheader (e.g., a MAC subheader of the fourth MAC PDU). If the seventh indication information is generated by an RLC layer of the terminal device, the seventh indication information may be included in an RLC header (e.g., an RLC header of the fourth RLC PDU). If the seventh indication information is generated by a PDCP layer of the terminal device, the seventh indication information may be included in a PDCP header (e.g., a PDCP header of the fourth PDCP PDU).

[0383] Optionally, the SIB1 set and the SI message may correspond to the same logical channel and / or the same RLC entity.

[0384] It should be noted that the description of the solution in which the RRC layer of the terminal device determines a specific SIB1 or multiple specific SIB1s included in the SIB1 set of the received RRC message in this embodiment of the present application according to the above two implementations may be regarded as an independent embodiment, or may be combined with one or more steps in this embodiment of the present application as an optional step, which is not limited herein.

[0385] S2206: The terminal device receives or acquires eighth instruction information from the network device.

[0386] Optionally, in some possible implementations, the terminal device needs to know whether a specific cell transmits a different SIB1 by using the solution for transmitting an SIB1 set in this embodiment of the present application. Specifically, the network device may transmit eighth indication information to the terminal device, and the eighth indication information may indicate whether an SIB1 set exists in the network or whether the network device should transmit the SIB1 set. Correspondingly, the terminal device may receive the eighth indication information from the network device, and the terminal device may determine whether an SIB1 set exists in the network or whether the network device should transmit the SIB1 set based on the eighth indication information. The field used to carry the eighth indication information may include one bit, two bits, or more bits. This is not limited herein.

[0387] It should be noted that the terminal device receiving the eighth indication information from the network device can be understood as follows: the terminal device receives the MIB from the network device, and the MIB includes the eighth indication information. In other words, the eighth indication information can be carried in the MIB. Alternatively, the eighth indication information may be carried in the sixth DCI for scheduling the SIB1 set. Alternatively, the eighth indication information may be carried in the DCI for scheduling the SI message. Specifically, the terminal device receives the eighth indication information in the MIB, the sixth DCI for scheduling the SIB1 set, No. 8 Instruction Information or based on eighth indication information in the DCI for scheduling the SI message, determine that the SIB1 set exists on the network device or should be transmitted by the network device. In a possible terminal implementation, the terminal device may interpret the field in the DCI by using the DCI corresponding to the SIB1 set, and / or the terminal device may perform decoding by using the ASN.1 of the RRC message corresponding to the SIB1 set.

[0388] It should be noted that the above steps S2201 and S2202 may be regarded as independent embodiments, or may be combined with one or more steps in this embodiment of the present application as an optional step, and this is not limited thereto. The above steps S2203, S2204, and S2205, or steps S2203 and S2205, may be regarded as independent embodiments, or may be combined with one or more steps in this embodiment of the present application as an optional step, and this is not limited thereto. The above step S2206 may be regarded as an independent embodiment, or may be combined with one or more steps in this embodiment of the present application as an optional step, and this is not limited thereto. It should be noted that the numbering order in this embodiment of the present application does not indicate the order in which the steps are performed. The order in which the steps are performed is specifically determined based on an actual application scenario, and this is not limited thereto. For example, S22 06 is S 22 It may be executed before or after 01. This is not limited.

[0389] In this embodiment of the present application, different SIB1s are mapped to one SIB1 set, and the SIB1 set is scheduled by one DCI. This can ensure that the terminal device can acquire the first SIB1 or the basic version of the SIB1, can ensure that the terminal device can access the network based on the first SIB1 or the basic version of the SIB1, and can secure a basic communication channel between the terminal device and the network device so that basic communication can be performed between the terminal device and the network. For the PHY layer or MAC layer of the terminal device, the DCI used to schedule the SIB1 and the DCI used to schedule the SI message are distinguished based on the indication information in the DCI, the scrambling information of the DCI, the DCI format, the time domain resource for the DCI, or the frequency domain resource for the DCI. In this way, the terminal device can accurately identify the content scheduled by the DCI and correctly perform HARQ combining to improve the reliability of data reception. For the RRC layer of the terminal device, the terminal device can correctly identify the content included in the fourth message based on the indication information, the interaction between layers, or the logical channel in the fourth message. Furthermore, for the RRC layer of the terminal device, the terminal device can accurately identify a specific SIB1 or multiple specific SIB1s included in the SIB1 set in the fourth message based on the sixth indication information in the fourth message or the seventh indication information associated with the fourth message, and correctly perform RRC decoding to obtain correct information. Furthermore, whether the network device should transmit the fourth data is indicated in the eighth indication information in the MIB, the DCI for scheduling the fourth data, or the DCI for scheduling the third data. This helps the terminal device correctly receive and decode the SIB1 set, improves reception reliability, and also helps save energy.

[0390] It should be noted that the present application further includes the following implementations in addition to the solutions described in Figures 9, 11, and 22. It should be noted that the following implementations may be combined with some steps in the above embodiments or may be implemented independently.

[0391] Optionally, in a possible implementation, a terminal device of an earlier version may access a network device by using SIB1 associated with the basic version or the secure mode, but the network device may change SIB1 or other SIBs associated with the later version or the normal mode. The terminal device of the earlier version does not need SIB1 or other SIBs associated with the later version or the normal mode. Therefore, to avoid the impact of changes to SIs associated with the later version or the normal mode (e.g., SIB1 associated with the later version or the normal mode and / or other SIBs associated with the later version or the normal mode) on terminal devices of an earlier version, ninth indication information may be included in a DCI or a short message for notifying the SI change, and the ninth indication information may indicate that the SI change is related to SIs associated with the basic version or the secure mode (e.g., SIB1 associated with the basic version or the secure mode and / or other SIBs associated with the basic version or the secure mode). SIB ), or indicates whether the SI change is related to the SI associated with the later version or the normal mode only. The length of the ninth indication information may be 1 bit, etc. This is specifically determined based on the actual application scenario and is not limited here. It can be easily understood that since the ninth indication information is transmitted to the terminal device, energy can be saved for the terminal device.

[0392] It should be noted that in specific implementation, if a terminal device cannot access a network device in normal mode, the terminal device will usually attempt to access the network device in secure mode. However, an abnormal situation may occur in which the terminal device cannot access the network device in secure mode. In this case, the terminal device may abandon access in secure mode based on a maximum retry time or a maximum number of retry attempts. Specifically, a maximum retry time or a maximum number of retry attempts may be set, and when the time or number of retry attempts in secure mode is equal to or greater than the preset maximum retry time or the maximum number of retry attempts, the terminal device abandons access in secure mode. This can save the energy of the terminal device.

[0393] It should be noted that for a terminal device accessing a network device in a secure mode, when performing configuration of the terminal device, the network device needs to send parameters related to the secure mode, such as a previous version of the configuration. It should be noted that the terminal device may receive information from a serving cell, and the information indicates whether nearby cells support the terminal device accessing the network device in a secure mode. For a terminal device accessing a network device in a secure mode, during cell reselection, cells that can support the terminal device accessing the network device in a secure mode may be preferentially selected. For example, information about nearby cells may be included in the system information.

[0394] It should be noted that different embodiments or some steps in different embodiments of the present application may be combined with each other to form a new embodiment, and unless otherwise specified or a logical contradiction occurs, the terms and / or descriptions in different embodiments are consistent and may be cross-referenced.

[0395] The communication device provided herein is described below with reference to FIGS.

[0396] FIG. 25 is a diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in FIG. 25 may be configured to perform some or all of the functions of the terminal device in the method embodiments described in FIGS. 9 to 24. The device may be a terminal device, a device within a terminal device, or a device that can be used with a terminal device. Alternatively, the communication device may be a chip system. The communication device shown in FIG. 25 may include a transceiver unit 2501 and a processing unit 2502. The processing unit 2502 is configured to process data. The transceiver unit 2501 is integrated with a receiving unit and a transmitting unit. The transceiver unit 2501 may also be referred to as a communication unit. Alternatively, the transceiver unit 2501 may be divided into a receiving unit and a transmitting unit. Below, the description of the processing unit 2502 and the transceiver unit 2501 is similar. Details will not be described again below.

[0397] In implementation, the transceiver unit 2501 is configured to receive first downlink control information (DCI) from a network device, the first DCI being used to schedule first data, and the processing unit 2502 is configured to determine, based on the first DCI, that the first data includes a first system information block 1 (SIB1), the first SIB1 including information about network access in a first operation mode, the first DCI including first indication information, the first indication information indicating that the first data includes the first SIB1, or one or more of the following information associated with the first DCI, including scrambling information, downlink control information format (DCI format information), time domain resource information, or frequency domain resource information, is different from that associated with a second DCI, the second DCI being used to schedule a second SIB1, the second SIB1 including information about network access in a second operation mode.

[0398] Optionally, the first data includes a first message, the first message including a first SIB1. Optionally, the first message further includes second indication information, the second indication information indicating that the first message includes the first SIB1. Optionally, the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH). The first RLC entity is different from a second RLC entity, or the first LCH is different from a second LCH. The second RLC entity is associated with a second SIB1, and the second LCH is associated with the second SIB1.

[0399] Optionally, the transceiver unit 2501 is further configured to obtain third indication information associated with the first message, the third indication information indicating that the first message includes the first SIB1.

[0400] Optionally, the transceiver unit 2501 is specifically configured to obtain third indication information from a physical PHY layer, a medium access control MAC layer, a radio link control RLC layer, or a packet data convergence protocol PDCP layer by a radio resource control RRC layer.

[0401] Optionally, the transceiver unit 2501 is further configured to receive fourth instruction information from the network device, the fourth instruction information instructing the network device to transmit the first SIB1, the fourth instruction information being carried in a master information block MIB or a second DCI. Optionally, the transceiver unit 2501 is further configured to receive first data from the network device based on the first DCI.

[0402] In another implementation, the transceiver unit 2501 is configured to receive third downlink control information DCI from the network device, where the third DCI is used to schedule at least two pieces of data, or the third DCI is used to schedule second data and a fourth DCI, where the fourth DCI is used to schedule first data, and the transceiver unit 2501 is configured to receive first data and / or second data from the network device based on the third DCI, where the at least two pieces of data include the first data and the second data, where the first data includes a first system information block 1 SIB1 and the second data includes a second SIB1, where the first SIB1 includes information regarding network access in a first operating mode, and the second SIB1 includes information regarding network access in a second operating mode.

[0403] Optionally, the third DCI includes time domain resource information and / or frequency domain resource information of the first data, and optionally, the time domain resource information of the first data includes an interval between the time domain resources for the first data and the time domain resources for the second data, or the time domain resource information of the first data includes an interval between the time domain resources for the first data and the time domain resources for the third DCI, and / or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the second data, or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the third DCI; The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0404] Optionally, the following: an interval between a time domain resource for the first data and a time domain resource for the second data; an interval between a time domain resource for the first data and a time domain resource for the third DCI; an interval between the frequency domain resource for the first data and the frequency domain resource for the second data; or an interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI; One or more intervals are predefined, The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0405] Optionally, the first data includes a first message, and the first message includes a first SIB1.

[0406] Optionally, the first message further includes second indication information, where the second indication information indicates that the first message includes the first SIB1.

[0407] Optionally, the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH); The first RLC entity is different from the second RLC entity, or the first LCH is different from the second LCH, and the second RLC entity is associated with a second SIB1, and the second LCH is associated with a second SIB1.

[0408] Optionally, the transceiver unit 2501 is further configured to obtain third indication information associated with the first message, the third indication information indicating that the first message includes the first SIB1.

[0409] Optionally, the transceiver unit 2501 is further configured to obtain third indication information from a physical PHY layer or a medium access control MAC, radio link control RLC, or packet data convergence protocol PDCP layer by a radio resource control RRC layer.

[0410] Optionally, the transceiver unit 2501 is further configured to receive a master information block MIB from the network device, the MIB including fourth instruction information, the fourth instruction information instructing the network device to transmit the first SIB1.

[0411] Optionally, the third DCI includes fourth instruction information, and the fourth instruction information instructs the network device to send the first SIB1.

[0412] Other possible implementations of the communication device are shown in the method embodiments corresponding to Figs. Terminal Device Please refer to the relevant description of the function of , the details will not be described again here.

[0413] FIG. 26 is a diagram of the structure of another communication device according to an embodiment of the present application. The communication device shown in FIG. 26 may be configured to perform some or all of the functions of the network device in the method embodiments described in FIGS. 9-24. The device may be a network device, a device within a network device, or a device that can be used with a network device. Alternatively, the communication device may be a chip system. The communication device shown in FIG. 26 may include a transceiver unit 2601 and a processing unit 2602.

[0414] In implementation, the processing unit 2602 is configured to determine first downlink control information (DCI), the first DCI is used to schedule first data, the first data includes a first system information block 1 (SIB1), the first SIB1 includes information about network access in a first operation mode, the transceiver unit 2601 is configured to transmit the first DCI to the terminal device, the first DCI includes first indication information, the first indication information indicates that the first data includes the first SIB1, or one or more of the following information associated with the first DCI, including scrambling information, downlink control information format (DCI format information), time domain resource information, or frequency domain resource information, is different from that associated with a second DCI, the second DCI is used to schedule a second SIB1, and the second SIB1 includes information about network access in a second operation mode.

[0415] Optionally, the first data includes a first message, the first message including the first SIB1. Optionally, the first message further includes second indication information, the second indication information indicating that the first message includes the first SIB1.

[0416] Optionally, the transceiver unit 2601 is further configured to send fourth instruction information to the terminal device, the fourth instruction information instructing the network device to send the first SIB1, the fourth instruction information being carried in a master information block MIB or a second DCI. Optionally, the transceiver unit 2601 is further configured to send first data to the terminal device.

[0417] In another implementation, the transceiver unit 2601 is configured to transmit third downlink control information DCI to the terminal device, where the third DCI is used to schedule at least two pieces of data, or the third DCI is used to schedule second data and a fourth DCI, and the fourth DCI is used to schedule first data, and the transceiver unit 2601 is configured to transmit the first data and second data to the terminal device, where the at least two pieces of data include the first data and the second data, where the first data includes a first system information block 1 SIB1 and the second data includes a second SIB1, where the first SIB1 includes information regarding network access in a first operating mode, and the second SIB1 includes information regarding network access in a second operating mode.

[0418] Optionally, the third DCI includes time domain resource information and / or frequency domain resource information of the first data, and optionally, the time domain resource information of the first data includes an interval between the time domain resources for the first data and the time domain resources for the second data, or the time domain resource information of the first data includes an interval between the time domain resources for the first data and the time domain resources for the third DCI, and / or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the second data, or the frequency domain resource information of the first data includes an interval between a frequency domain resource for the first data and a frequency domain resource for the third DCI; The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0419] Optionally, the following: an interval between a time domain resource for the first data and a time domain resource for the second data; an interval between a time domain resource for the first data and a time domain resource for the third DCI; an interval between the frequency domain resource for the first data and the frequency domain resource for the second data; or an interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI; One or more intervals are predefined, The interval between the time domain resources is used to determine a time domain resource for the first data, and the interval between the frequency domain resources is used to determine a frequency domain resource for the first data.

[0420] Optionally, the first data includes a first message, the first message including the first SIB1. Optionally, the first message includes second indication information, the second indication information indicating that the first message includes the first SIB1.

[0421] Optionally, the transceiver unit 2601 is further configured to send a master information block MIB to the terminal device, where the MIB includes fourth instruction information, and the fourth instruction information instructs the network device to send the first SIB1.

[0422] Optionally, the third DCI includes fourth instruction information, and the fourth instruction information instructs the network device to transmit the first SIB1. For other possible implementations of the communication device, see the embodiments of the methods corresponding to FIGS. 9 to 24. Rune Please refer to the relevant description of the network device's functions, and the details will not be described again here.

[0423] FIG. 27 is a structural diagram of another communication device according to an embodiment of the present application. As shown in FIG. 27, the communication device may be a terminal device described in the embodiment of the present application and is configured to implement the functions of the terminal devices in FIGS. 9 to 24. For ease of description, FIG. 27 only shows the main components of the terminal device 2700. As shown in FIG. 27, the terminal device 2700 includes a processor, a memory, a control circuit, an antenna, and an input / output device. The processor is primarily configured to process communication protocols and communication data, control the entire terminal device 2700, execute software programs, and process data of the software programs. The memory is primarily configured to store software programs and data. The control circuit is primarily configured to convert between baseband signals and radio frequency signals and process radio frequency signals. The antenna is primarily configured to transmit and receive radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touchscreen, a display, a microphone, or a keyboard, is primarily configured to receive data input by a user and output data to the user.

[0424] For example, the terminal device 2700 is a mobile phone. After the terminal device 2700 is powered on, the processor can read a software program in the storage unit, interpret and execute instructions of the software program, and process data of the software program. When data needs to be transmitted wirelessly, the processor performs baseband processing on the data to be transmitted and then outputs the baseband signal to the control circuit. The control circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside through an antenna in the form of electromagnetic waves. When data is transmitted to the terminal device 2700, the control circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

[0425] Those skilled in the art will appreciate that for ease of description, Figure 27 shows only one memory and one processor. In some embodiments, terminal device 2700 may include multiple processors and memories. Memory may also be referred to as a storage medium, a storage device, etc. This is not a limitation of this embodiment of the present invention.

[0426] In any implementation, the processor may include a baseband processor and a central processing unit. The baseband processor is primarily configured to process communication protocols and communication data. The central processing unit is primarily configured to control the entire terminal device 2700, execute software programs, and process data of the software programs. The processor in FIG. 27 incorporates the functions of a baseband processor and a central processing unit. Those skilled in the art will appreciate that the baseband processor and the central processing unit may alternatively be independent processors and interconnected using technology such as a bus. The terminal device 2700 may include multiple baseband processors to accommodate different network standards. The terminal device 2700 may include multiple processing units to increase the processing power of the terminal device 2700. The components of the terminal device 2700 may be connected via various buses. The baseband processor may also be referred to as a baseband processing circuit or a baseband processing chip. The central processing unit may also be referred to as a central processing circuit or a central processing chip. The functions for processing communication protocols and communication data may be built into the processor or may be stored in a storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing functions.

[0427] In an example, an antenna and control circuitry with transceiver functionality may be considered a transceiver unit 2710 of the terminal device 2700, and a processor with processing functionality may be considered a processing unit 2720 of the terminal device 2700. As shown in FIG. 27 , the terminal device 2700 includes a transceiver unit 2710 and a processing unit 2720. The transceiver unit may also be referred to as a transceiver, a transceiver device, a transceiver unit, etc. Optionally, a component within the transceiver unit 2710 configured to implement a receiving functionality may be considered a receiving unit, and a component within the transceiver unit 2710 configured to implement a transmitting functionality may be considered a transmitting unit. That is, the transceiver unit 2710 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiving device, a receiver, a receiving circuit, etc., and the transmitting unit may also be referred to as a transmitting device, a transmitter, a transmitting circuit, etc.

[0428] 28 is a diagram of the structure of another communication device according to an embodiment of the present application. As shown in FIG. 28, the communication device may be a network device described in the embodiment of the present application and is configured to implement the functions of the network devices in FIGS. 9 to 24. The network device 28 includes a baseband unit 281, a radio frequency unit 282, and an antenna 283. In the uplink direction, the radio frequency unit 282 receives information transmitted by a terminal device through the antenna 283 and transmits the information transmitted by the terminal device to the baseband unit 281 for processing. In the downlink direction, the baseband unit 281 processes information for the terminal device and transmits the processed information to the radio frequency unit 282, which processes information for the terminal device and transmits the processed information to the terminal device via the antenna 283.

[0429] The baseband device 281 includes one or more processing units 2811, a storage unit 2812, and an interface 2813. The processing unit 2811 is configured to assist the network device in performing the functions of the network device in the above-described method embodiments. The storage unit 2812 is configured to store software programs and / or data. The interface 2813 is configured to exchange information with the radio frequency device 282, and the interface includes an interface circuit configured to input and output information. In implementation, the processing unit is an integrated circuit, such as one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of these integrated circuits. These integrated circuits may be integrated together to form a chip. The storage unit 2812 and the processing unit 2811 may be located on one chip. In other words, the storage unit 2812 is an on-chip storage element. Alternatively, the storage unit 2812 and the processing unit 2811 may be located on different chips. In other words, the storage unit 2812 is an off-chip storage element. The storage unit 2812 may be a single memory or may refer collectively to multiple memories or storage elements.

[0430] The network device may schedule a program by one or more processing units to implement some or all of the steps in the above method embodiments, for example, to implement corresponding functions of the network device in Figures 9 to 24. The one or more processing units may support radio access technologies of the same standard, or may support radio access technologies of different standards.

[0431] An embodiment of the present application further provides a computer-readable storage medium, which stores instructions that, when executed by a processor, perform the method processes in the above method embodiments.

[0432] An embodiment of the present application further provides a computer program product, which, when run on a processor, performs the method processes in the above method embodiments.

[0433] Those skilled in the art will realize that, in combination with the examples described in the embodiments disclosed herein, the units and steps can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is implemented by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but it should not be considered that the implementation goes beyond the scope of the present application.

[0434] It should be understood that in some embodiments provided in the present application, the disclosed systems, devices, and methods may be implemented in other ways. For example, the above-described device embodiments are merely examples. For example, the unit division is merely a logical functional division. Units described as separate parts may or may not be physically separated, and parts shown as units may or may not be physical units, i.e., may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions of the embodiments.

[0435] When a function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may essentially be implemented in the form of a software product, or a part of the technical solution may be implemented in the form of a software product. A computer software product is stored in a storage medium and includes some instructions that instruct a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or some of the steps of the method described in the embodiments of the present application. The computer-readable storage medium may be any available medium accessible by a computer. For example, computer-readable media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, removable hard disk, other optical disk storage, magnetic disk storage media, other magnetic storage devices, or any other medium that can carry or store expected program code in the form of instructions or data structures and that can be accessed by a computer.Additionally, by way of example, and not limitation, many forms of RAM may be used, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), or direct rambus random access memory (direct rambus RAM, DR RAM).

[0436] The above description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the embodiments of the present application. Any modifications or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the embodiments of the present application should fall within the scope of protection of the embodiments of the present application. Therefore, the scope of protection of the embodiments of the present application should be governed by the scope of protection of the claims.

[0437] This application claims priority from Chinese Patent Application No. 202111418043.8, filed with the State Intellectual Property Office of the People's Republic of China on November 25, 2021, for an invention entitled "COMMUNICATION METHOD AND COMMUNICATION APPARATUS," and the entire text of the prior Chinese patent application is incorporated herein by reference.

Claims

1. 1. A communication method, applied to a terminal device, comprising: receiving first downlink control information (DCI) from the network device used to schedule first data; determining, based on the first DCI, that the first data includes a first system information block 1 (SIB1); and the first DCI includes first indication information, the first indication information indicating that the first data includes the first SIB1, and one or more of scrambling information, downlink control information (DCI) format information, time domain resource information, or frequency domain resource information associated with the first DCI is different from that associated with a second DCI, the second DCI is used to schedule second data, and the second data includes a second SIB1; method.

2. the first data includes a first message, and the first message includes the first SIB1; The method of claim 1.

3. the first message further includes second indication information, and the second indication information indicates that the first message includes the first SIB1; The method of claim 2.

4. the first SIB1 is associated with a first radio link control (RLC) entity, or the first SIB1 is associated with a first logical channel (LCH); the first RLC entity is different from the second RLC entity, or the first LCH is different from the second LCH, and the second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1; The method of claim 2.

5. The method further includes obtaining third indication information associated with the first message; the third indication information indicating that the first message includes the first SIB1; The method of claim 2.

6. The step of obtaining third indication information associated with the first message includes: obtaining, by a radio resource control (RRC) layer of the terminal device, the third indication information from a physical (PHY) layer of the terminal device, or a medium access control (MAC) layer, a radio link control (RLC) layer, or a packet data convergence protocol (PDCP) layer of the terminal device; The method of claim 5.

7. The method further includes receiving fourth instruction information from the network device instructing the network device to transmit the first SIB1; The fourth indication information is carried in a master information block (MIB) or the second DCI. The method of claim 1.

8. The method further comprises receiving the first data from the network device based on the first DCI. The method of claim 1.

9. the first SIB1 includes information about network access in a first mode of operation, or The second SIB1 includes information regarding network access in the second operation mode; The method of claim 1.

10. 1. A communication method applied to a network device, comprising: determining first downlink control information (DCI) used to schedule first data, the first data including a first system information block 1 (SIB1); transmitting the first DCI to a terminal device; and the first DCI includes first indication information, the first indication information indicating that the first data includes the first SIB1, and one or more of scrambling information, downlink control information (DCI) format information, time domain resource information, or frequency domain resource information associated with the first DCI is different from that associated with a second DCI, and the second DCI is used to schedule a second SIB1; method.

11. the first SIB1 includes information about network access in a first mode of operation, or The second SIB1 includes information regarding network access in the second operation mode; The method of claim 10.

12. the first data includes a first message, and the first message includes the first SIB1; The method of claim 10.

13. the first message further includes second indication information, and the second indication information indicates that the first message includes the first SIB1; The method of claim 12.

14. The method further includes transmitting fourth instruction information to the terminal device, the fourth instruction information instructing the network device to transmit the first SIB1; The fourth indication information is carried in a master information block (MIB) or the second DCI. The method of claim 10.

15. The method further comprises transmitting the first data to the terminal device. The method of claim 10.

16. A communication device, the communication device is a terminal device or a device for a terminal device, the communication device having a processor and a transceiver; The processor and the transceiver are configured to execute computer programs or instructions stored in at least one memory to enable the communication device to perform the method of any one of claims 1 to 9. Communication equipment.

17. A communication device, the communication device is a network device or a device for a network device, the communication device having a processor and a transceiver; The processor and the transceiver are configured to execute computer programs or instructions stored in at least one memory to enable the communication device to perform the method of any one of claims 10 to 15. Communication equipment.

18. storing computer programs or instructions; When the computer program or the instructions are executed by a computer, the method according to any one of claims 1 to 9 is carried out. A computer-readable storage medium.

19. storing computer programs or instructions; When the computer program or the instructions are executed by a computer, the method according to any one of claims 10 to 15 is carried out. A computer-readable storage medium.

Images