Communication methods and communication devices

Abstract

This invention provides a communication method and communication device that enable accurate reception of System Information Block (SIB) 1 and improve reliability. [Solution] The method includes receiving first downlink control information (DCI) from a network device used to schedule first data, and determining, based on the first DCI, that the first data includes a first system information block 1 (SIB1). The first DCI includes first instruction information, which indicates that the first data includes a first SIB1. Alternatively, one or more pieces of information associated with the first DCI, such as scrambling information, DCI format information, time-domain resource information, or frequency-domain resource information, may differ from those associated with the second DCI, where the second DCI is used to schedule second data, and the second data includes a second SIB1.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to communication methods and communication devices.

Background Art

[0002] Currently, mobile communication networks are becoming increasingly complex. Usually, a terminal device can transmit services by establishing a connection with a network device. Usually, 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, the terminal device may not be able to access the network. For example, when the network device has successfully upgraded, but the terminal device has not successfully upgraded or the terminal device cannot be upgraded, resulting in the terminal device being incompatible with the network device, the terminal device may not be able to accurately receive, parse, or decode the SIB1 transmitted by the network device, and thus cannot access the network. Based on this, how to ensure the success of the terminal device's access to the network to improve communication reliability has become one of the urgent issues that need to be solved currently.

Summary of the Invention

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

[0004] In accordance with a first aspect, the present application provides a communication method which is applied to a terminal device. The method includes receiving first downlink control information DCI from a network device which is used to schedule first data, and determining, based on the first DCI, that the first data includes a first system information block 1 SIB1 which includes information about network access in a first operating mode. The first DCI includes first instruction information which indicates that the first data includes the first SIB1, or one or more of the following information related to the first DCI, such that scrambling information, downlink control information format DCI format information, time-domain resource information, or frequency-domain resource information, is different from that related to a second DCI, the second DCI is used to schedule a second SIB1 which includes information about network access in a second operating mode.

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

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

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

[0008] In this application, the second instruction information is carried in the first message (i.e., the RRC message), thereby enabling the terminal device to determine the type or version of the first SIB1 contained in the first message based on the second instruction information, ensuring that the terminal device can correctly perform RRC ASN.1 decoding. This also helps to improve communication reliability.

[0009] In possible implementations, the first SIB1 is associated with the first radio link control RLC entity, or the first SIB1 is associated with the first logical channel LCH. The first RLC entity is distinct from the second RLC entity, or the first LCH is distinct from the second LCH. The second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1.

[0010] In this application, the terminal device determines the type or version of the first SIB1 based on a logical channel or RLC entity, thereby enabling the terminal device to 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 directive information related to the first message, the third directive information indicating that the first message contains a first SIB1.

[0012] In this invention, the terminal device obtains third instruction information related to the first message, and then determines the type or version of the first SIB1 based on the third instruction information, thereby ensuring that the terminal device can correctly perform RRC ASN.1 decoding.

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

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

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

[0016] In this invention, the terminal device receives fourth instruction information and, based on this information, determines whether the network device should transmit the first SIB1. If the terminal device determines that the network device should not transmit the first SIB1, it no longer needs to monitor the PDCCH corresponding to the first SIB1. This saves energy for the terminal device.

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

[0018] In a second aspect, the present invention provides a communication method, the method being applied to a terminal device. The method includes receiving third downlink control information DCI from a network device, wherein the third DCI is used to schedule at least two data, or 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, wherein the at least two data include first data and second data, the first data includes first system information block 1 SIB1, the second data includes second SIB1, 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.

[0019] In this application, one DCI is used to schedule two SIB1s, or a DCI for the first SIB1 is used to schedule a DCI for the second SIB1, thereby enabling the terminal device to accurately identify the same data and accurately execute HARQ combinations, thereby improving 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 this application, the time-domain resource information and frequency-domain resource information of the first data are configured dynamically or quasi-statically in the third DCI, thereby enabling the terminal device to accurately receive the first data and / or the second data based on the information configured in the third DCI.

[0022] In possible implementations, the time-domain resource information for the first data includes the 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 for the first data includes the 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 for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or the frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI. The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

[0023] In this application, the time-domain resource information and / or frequency-domain resource information for the first data are indirectly configured, specifically, by setting 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, so that the terminal device can accurately receive the corresponding first data by determining a specific time-domain resource and / or frequency-domain resource for the first data based on the interval set 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. Optionally, the terminal device may, in order to accurately receive the corresponding first data, alternatively determine a specific time-domain resource and / or frequency-domain resource for the first data based on the interval set in the third DCI and by referring to the time-domain resource and / or frequency-domain resource of the third DCI. In a possible embodiment, the third DCI includes the time-domain resource information and / or frequency-domain resource information of the fourth DCI.

[0024] In this application, the time-domain resource information and frequency-domain resource information of the 4th DCI are configured dynamically or quasi-statically in the 3rd DCI, so that the terminal device can accurately receive the 4th DCI based on the information configured in the 3rd DCI, and then receive the 1st data based on the 4th DCI.

[0025] In possible implementations, the time-domain resource information of the 4th DCI includes the interval between the time-domain resource of the 4th DCI and the time-domain resource of the 2nd data, or the time-domain resource information of the 4th DCI includes the interval between the time-domain resource of the 4th DCI and the time-domain resource of the 3rd DCI, and / or The frequency domain resource information of the 4th DCI includes the interval between the frequency domain resource of the 4th DCI and the frequency domain resource of the 2nd data, or the frequency domain resource information of the 4th DCI includes the interval between the time domain resource of the 4th DCI and the frequency domain resource of the 3rd DCI. The intervals between time-domain resources are used to determine the time-domain resources of the 4th DCI, and the intervals between frequency-domain resources are used to determine the frequency-domain resources of the 4th DCI.

[0026] In this application, the time domain resource information and / or frequency domain resource information of the fourth DCI are indirectly configured. Specifically, an interval between the time domain resource of the fourth DCI and the time domain resource of the second data and / or an interval between the frequency domain resource of the fourth DCI and the frequency domain resource of the second data are set. Thereby, the terminal device can accurately receive the corresponding fourth DCI by referring to the interval set in the third DCI and the time domain resource and / or frequency domain resource of the second data included in the third DCI to determine the specific time domain resource and / or frequency domain resource for the fourth DCI. Optionally, the terminal device may alternatively determine the specific time domain resource and / or frequency domain resource for the fourth DCI based on the interval set in the third DCI and by referring to the time domain resource and / or frequency domain resource of the third DCI to accurately receive the corresponding fourth DCI. Therefore, the first data can be accurately received based on the fourth DCI.

[0027] In a possible implementation, the following interval between the time domain resource for the first data and the time domain resource for the second data, interval between the time domain resource for the first data and the time domain resource for the third DCI, interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI one or more of the intervals are predefined, The interval between time domain resources is used to determine the time domain resource for the first data, and the interval between frequency domain resources is used to determine the 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 are predefined in the protocol, so that the terminal device can accurately receive the corresponding first data by determining a specific time-domain resource and / or frequency-domain resource for the first data based on the predefined interval and by referring to the time-domain resource and / or frequency-domain resource of the second data included in the 3DCI. Alternatively, the interval between the time-domain resource of the first data and the time-domain resource of the 3DCI and / or the interval between the frequency-domain resource of the first data and the frequency-domain resource of the 3DCI are predefined in the protocol, so that the terminal device can accurately receive the corresponding first data by determining a specific time-domain resource and / or frequency-domain resource for the first data based on the predefined interval and by referring to the time-domain resource and / or frequency-domain resource of the 3DCI.

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

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

[0031] In this application, the second instruction information is carried in the first message (i.e., the RRC message), thereby enabling the terminal device to determine the type or version of the first SIB1 contained in the first message based on the second instruction information, ensuring that the terminal device can correctly perform RRC ASN.1 decoding. This also helps to improve communication reliability.

[0032] In possible implementations, the first SIB1 is associated with the first radio link control RLC entity, or the first SIB1 is associated with the first logical channel LCH. The first RLC entity is distinct from the second RLC entity, or the first LCH is distinct from the second LCH. The second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1.

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

[0034] In a possible implementation, the method further includes obtaining third directive information related to the first message, the third directive information indicating that the first message contains a first SIB1.

[0035] In this invention, the terminal device obtains third instruction information related to the first message, and then determines the type or version of the first SIB1 based on the third instruction information, thereby ensuring that the terminal device can correctly perform RRC ASN.1 decoding.

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

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

[0038] In a possible implementation, the method further includes receiving a master information block MIB from a network device, the MIB containing fourth directive information, the fourth directive information instructing the network device to transmit a 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 invention, the terminal device receives fourth instruction information and, based on this information, determines whether the network device should transmit the first SIB1. If the terminal device determines that the network device should not transmit the first SIB1, it no longer needs to monitor the PDCCH corresponding to the first SIB1. This saves energy for the terminal device.

[0041] In a third aspect, the present invention provides a communication method, the method being applied to a network device. The method includes determining a first downlink control information DCI used to schedule first data, the first data comprising a first system information block 1 SIB1, the first SIB1 comprising information relating to network access in a first operating mode, and transmitting the first DCI to a terminal device, the first DCI comprising first instruction information, the first instruction information indicating that the first data comprises the first SIB1, or one or more of the following information related to the first DCI, such as scrambling information, downlink control information format DCI format information, time-domain resource information, or frequency-domain resource information, differs from that related to a second DCI, the second DCI being used to schedule a second SIB1, the second SIB1 comprising information relating to network access in a second operating mode.

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

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

[0044] In a possible implementation, the method further includes sending a fourth instruction information to a terminal device instructing a network device to send a first SIB1, which is carried by the fourth instruction information, a master information block MIB, or a second DCI.

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

[0046] In accordance with a fourth aspect, the present invention provides a communication method, the method being applied to a network device. The method includes transmitting a third downlink control information DCI to a terminal device, wherein the third DCI is used to schedule at least two data, or the third DCI is used to schedule a second data and a fourth DCI, and the fourth DCI is used to schedule a first data, and transmitting the first data and the second data to the terminal device, wherein the at least two data include the first data and the second data, the first data includes a first system information block 1 SIB1, the second data includes a second SIB1, 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.

[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 possible implementations, the time-domain resource information for the first data includes the 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 for the first data includes the 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 for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or the frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI. The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

[0049] In a possible implementation, the 3rd DCI includes time-domain resource information and / or frequency-domain resource information of the 4th DCI.

[0050] In this application, the time-domain resource information and frequency-domain resource information of the 4th DCI are configured dynamically or quasi-statically in the 3rd DCI, so that the terminal device can accurately receive the 4th DCI based on the information configured in the 3rd DCI, and then receive the 1st data based on the 4th DCI.

[0051] In possible implementations, the time-domain resource information of the 4th DCI includes the interval between the time-domain resource of the 4th DCI and the time-domain resource of the 2nd data, or the time-domain resource information of the 4th DCI includes the interval between the time-domain resource of the 4th DCI and the time-domain resource of the 3rd DCI, and / or The frequency domain resource information of the 4th DCI includes the interval between the frequency domain resource of the 4th DCI and the frequency domain resource of the 2nd data, or the frequency domain resource information of the 4th DCI includes the interval between the time domain resource of the 4th DCI and the frequency domain resource of the 3rd DCI. The intervals between time-domain resources are used to determine the time-domain resources of the 4th DCI, and the intervals between frequency-domain resources are used to determine the frequency-domain resources of the 4th DCI.

[0052] In this application, the time-domain resource information and / or frequency-domain resource information of the 4th DCI are indirectly configured, specifically, by setting an interval between the time-domain resource of the 4th DCI and the time-domain resource of the second data and / or an interval between the frequency-domain resource of the 4th DCI and the frequency-domain resource of the second data, so that the terminal device can accurately receive the corresponding 4th DCI by determining a specific time-domain resource and / or frequency-domain resource for the 4th DCI based on the interval set in the 3rd DCI and by referring to the time-domain resource and / or frequency-domain resource of the second data included in the 3rd DCI. Optionally, the terminal device may, in order to accurately receive the corresponding 4th DCI, alternatively determine a specific time-domain resource and / or frequency-domain resource for the 4th DCI based on the interval set in the 3rd DCI and by referring to the time-domain resource and / or frequency-domain resource of the 3rd DCI. Thus, the first data can be accurately received based on the 4th DCI.

[0053] In possible implementations, the following: The interval between the time-domain resource for the first data and the time-domain resource for the second data. The interval between the time-domain resource for the first data and the time-domain resource for the third DCI, The interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or Interval between frequency domain resources for the first data and frequency domain resources for the third DCI One or more of the intervals are predefined, The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

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

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

[0056] In a possible implementation, the method further includes sending a master information block (MIB) to a terminal device, the MIB containing fourth instruction information, the fourth instruction information instructing a network device to send a 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] In accordance with a fifth aspect, the present application provides a communication device. The communication device may be a terminal device, and the device is A transceiver unit configured to receive first downlink control information DCI, used for scheduling first data, from a network device, A processing unit configured to determine, based on the first DCI, that the first data includes a first system information block 1 SIB1 containing information about network access in a first operating mode, The first DCI includes first instruction information, which indicates that the first data includes the first SIB1, or one or more of the following information related to the first DCI—scrambling information, downlink control information format DCI format information, time-domain resource information, or frequency-domain resource information—is different from that related to the second DCI, the second DCI is used to schedule the second SIB1, and the second SIB1 includes information about network access in the second operating mode.

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

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

[0061] In possible implementations, the first SIB1 is associated with the first radio link control RLC entity, or the first SIB1 is associated with the first logical channel LCH. The first RLC entity is distinct from the second RLC entity, or the first LCH is distinct from the second LCH. The second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1.

[0062] In a possible implementation, the transceiver unit is further configured to acquire third directive information related to the first message, the third directive information indicating that the first message contains a first SIB1.

[0063] In possible implementations, the transceiver unit is specifically configured to obtain third-party instruction information from the physical PHY layer, the terminal device's medium access control MAC layer, the radio link control RLC layer, or the packet data convergence protocol PDCP layer via the radio resource control RRC layer.

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

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

[0066] In accordance with a sixth aspect, the present invention provides a communication device. The device may be a terminal device, and the device includes a transceiver unit configured to receive third downlink control information DCI from a network device, the third DCI being used to schedule at least two 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 receive first data and / or second data from the network device based on the third DCI, the at least two data including first data and second data, the first data including first system information block 1 SIB1, the second data including second SIB1, the first SIB1 including information regarding network access in a first operating mode, and the second SIB1 including information regarding network access in a second operating 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 possible implementations, the time-domain resource information for the first data includes the 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 for the first data includes the 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 for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or the frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI. The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

[0069] In possible implementations, the following: The interval between the time-domain resource for the first data and the time-domain resource for the second data. The interval between the time-domain resource for the first data and the time-domain resource for the third DCI, The interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or Interval between frequency domain resources for the first data and frequency domain resources for the third DCI One or more of the intervals are predefined, The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

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

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

[0072] In possible implementations, the first SIB1 is associated with the first radio link control RLC entity, or the first SIB1 is associated with the first logical channel LCH. The first RLC entity is distinct from the second RLC entity, or the first LCH is distinct from the second LCH. The second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1.

[0073] In a possible implementation, the transceiver unit is further configured to acquire third directive information related to the first message, the third directive information indicating that the first message contains a first SIB1.

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

[0075] In a possible implementation, the transceiver unit is further configured to receive a master information block (MIB) from a network device, the MIB containing a fourth directive, the fourth directive instructing the network device to transmit a 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] In accordance with a seventh aspect, the present application provides a communication device. The device may be a network device, and the device is A processing unit configured to determine first downlink control information DCI used for scheduling first data, wherein the first data includes first system information block 1 SIB1, and the first SIB1 includes information regarding network access in a first operating mode, and the processing unit Includes a transceiver unit configured to transmit a first DCI to a terminal device, The first DCI includes first instruction information, which indicates that the first data includes the first SIB1, or one or more of the following information related to the first DCI—scrambling information, downlink control information format DCI format information, time-domain resource information, or frequency-domain resource information—is different from that related to the second DCI, the second DCI is used to schedule the second SIB1, and the second SIB1 includes information about network access in the second operating mode.

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

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

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

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

[0082] In accordance with the eighth aspect, the present invention provides a communication device. The device may be a network device, and the device includes a transceiver unit configured to transmit third downlink control information DCI to a terminal device, wherein the third DCI is used to schedule at least two data, or the third DCI is used to schedule second data and fourth DCI, and the fourth DCI is used to schedule first data. The transceiver unit is configured to transmit first data and second data to a terminal device, wherein at least two data include first data and second data, the first data includes first system information block 1 SIB1, the second data includes second SIB1, 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.

[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 possible implementations, the time-domain resource information for the first data includes the 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 for the first data includes the 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 for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or the frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI. The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

[0085] In possible implementations, the following: The interval between the time-domain resource for the first data and the time-domain resource for the second data. The interval between the time-domain resource for the first data and the time-domain resource for the third DCI, The interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or Interval between frequency domain resources for the first data and frequency domain resources for the third DCI One or more of the intervals are predefined, The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

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

[0087] In a possible implementation, the first message includes second directive information, which 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 a terminal device, the MIB containing fourth instruction information, which instructs the network device to transmit a 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] In accordance with the 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 by the hardware running corresponding software. The hardware or software includes one or more modules corresponding to the functions. The unit or module may be software and / or hardware. For the operations performed by the communication device and their advantageous effects, see the methods according to the first or third aspect and their advantageous effects. Repetition is omitted.

[0091] In accordance with the 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 by the hardware running corresponding software. The hardware or software includes one or more modules corresponding to the functions. The unit or module may be software and / or hardware. For the operations performed by the communication device and their advantageous effects, see the methods according to the second or fourth aspect and their advantageous effects. Repetition is omitted.

[0092] In accordance with the eleventh aspect, the present application provides a communication device, which may be a terminal device. The communication device includes a processor and a transceiver. The processor and transceiver are configured to execute a computer program or instructions stored in at least one memory, so that the device can implement a method according to either the first or third aspect.

[0093] As another example, a communication device includes a processor, transceivers, and memory. The processor, transceivers, and memory are coupled to each other. The processor and transceivers are configured to implement a method according to either the first or third embodiment.

[0094] In accordance with the twelfth aspect, the present application provides a communication device. The device may be a network device. The communication device includes a processor and a transceiver. The processor and transceiver are configured to execute a computer program or instructions stored in at least one memory so that the device can implement a method according to either the second or fourth aspect.

[0095] As another example, a communication device includes a processor, transceivers, and memory. The processor, transceivers, and memory are coupled to each other. The processor and transceivers are configured to implement a method according to either the second or fourth embodiment.

[0096] In accordance with the 13th aspect, the present application provides a computer-readable storage medium. The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a computer, a method according to any one of the first to fourth aspects is implemented.

[0097] In accordance with the fourteenth aspect, the present application provides a computer program product including instructions. The computer program product includes computer program code. When the computer program code is executed on a computer, a method according to any one of the first to fourth aspects is implemented.

[0098] A chip system is provided according to the 15th aspect. The chip system includes a processor and further includes memory, and may implement a method according to any one of the first to fourth aspects or a possible design thereof.

[0099] A communication system is provided according to the 16th aspect. The communication system includes a terminal device according to the 9th aspect and a network device according to the 10th aspect. [Brief explanation of the drawing]

[0100] [Figure 1] This is a diagram of the network architecture of a 5G system. [Figure 2] This is a diagram of channel mapping. [Figure 3] This diagram shows how SIB1 and SI messages are scheduled based on DCI. [Figure 4] This is a diagram of downlink transmission between layers. [Figure 5]This is a diagram showing the structure of MAC PDU. [Figure 6a] This diagram shows how, according to an embodiment of the present invention, the MAC layer of a terminal device distributes the first data upward layer by layer. [Figure 6b] This diagram shows how, according to an embodiment of the present invention, the MAC layer of a terminal device distributes first data to the RRC layer via the RLC layer. [Figure 6c] This diagram shows how, according to an embodiment of the present invention, the MAC layer of a terminal device directly distributes the first data to the RRC layer. [Figure 7a] This diagram shows how, according to an embodiment of the present invention, the PHY layer of a terminal device distributes first data upward layer by layer. [Figure 7b] This diagram shows how, according to an embodiment of the present invention, the PHY layer of a terminal device distributes first data to the RRC layer via the RLC layer. [Figure 7c] This diagram shows how, according to an embodiment of the present invention, the PHY layer of a terminal device directly distributes the first data to the RRC layer. [Figure 8a] This diagram shows how data is received by a terminal device and processed at each layer, according to an embodiment of the present invention. [Figure 8b] This is another figure showing how data is received by a terminal device and processed at each layer, according to an embodiment of the present invention. [Figure 9] This is a schematic flowchart of a communication method according to an embodiment of the present invention. [Figure 10] This is a diagram of a scheduling mode according to an embodiment of the present invention. [Figure 11] This is another schematic flowchart of the communication method according to the embodiment of the present invention. [Figure 12] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 13] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 14] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 15] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 16] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 17] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 18] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 19] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 20] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 21] This is a diagram of another scheduling mode according to an embodiment of the present invention. [Figure 22] This is another schematic flowchart of the communication method according to the embodiment of the present invention. [Figure 23] This is a diagram illustrating a scenario in which SIB1 is scheduled based on the 6th DCI, according to an embodiment of the present invention. [Figure 24] This is a diagram of another scenario in which SIB1 is scheduled based on the 6th DCI, according to an embodiment of the present invention. [Figure 25] This is a diagram showing the structure of a communication device according to an embodiment of the present invention. [Figure 26] This is a diagram showing the structure of another communication device according to an embodiment of the present invention. [Figure 27] This is a diagram showing the structure of another communication device according to an embodiment of the present invention. [Figure 28] This is a diagram showing the structure of another communication device according to an embodiment of the present invention. [Modes for carrying out the invention]

[0101] The following describes the technical solution in the embodiments of this application with reference to the accompanying drawings.

[0102] In this application, " / " means "or" unless otherwise specified. For example, A / B may mean A or B. The terms "and / or" in this specification describe only the relationship between related objects and indicate that three relationships may exist. For example, A and / or B may mean the following three cases: A exists only, both A and B exist, and B exists only. Furthermore, "at least one" means one or more, and "multiple" means two or more. Terms such as "first," "second," etc. are not intended to limit the quantity or order of execution, and terms such as "first," "second," etc. do not indicate a clear distinction. In this application, terms such as "example," "for example," etc. are used to give an example, illustration, or description. Any embodiment or design scheme described in this application as "example" or "for example" should not be construed as being preferable or advantageous to other embodiments or design schemes. More precisely, terms such as "example," "for example," etc. are intended to present related concepts in a concrete manner.

[0103] The technical solutions in embodiments of this application may be applied to various communication systems, such as global systems 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 systems (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR), and future communication systems. This is not limited to these.

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

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

[0106] The following provides a detailed description of the terminal device, RAN, CN, and DN shown in Figure 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 the core network through a wireless 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 (AP), remote terminals, access terminals, user terminals, user agents, user devices, etc. For example, terminal devices may include mobile phones (or "cellular" phones), computers equipped with mobile terminal devices, or portable, packet-size, handheld, or computer-integrated mobile devices, such as personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), or other devices. Terminal devices may further include limited devices, such as low-power devices, devices with limited storage capacity, or devices with limited computing power.

[0109] 2. RAN

[0110] A 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 (or air interface). Certainly, in future communications, the names of these interfaces may remain unchanged or may be replaced by other names. This is not limited to the present invention.

[0111] An access network device is a node or device that connects terminal devices to a wireless network. For example, an access network device includes, but is not limited to, a next-generation node B (gNB), an evolved node B (eNB), a next-generation evolved node B (ng-eNB), a wireless backhaul device, a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home node B ((home evolved node B, HeNB) or (home node B, 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. This is not limited to these.

[0112] 3.CN

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

[0114] AMF network elements are control plane network elements provided by the operator network and are involved in access control and mobility management for terminal devices to access the operator network. For example, AMF network elements include functions such as mobility status management, temporary user identification assignment, user authorization, and authentication.

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

[0116] UPF network elements are gateways provided by operators and serve as gateways for communication between the operator network and the DN. UPF network elements include user plane-related functions such as data packet routing and transmission, packet discovery, quality of service (QoS) processing, lawful interception, uplink packet discovery, and downlink data packet storage.

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

[0118] AF network elements are functional network elements that provide various business services. They interact with the core network through other network elements and can interact with the policy management framework to perform policy management.

[0119] Furthermore, although not shown in the diagram, 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 this application, access network devices and core network devices may be collectively referred to as network devices.

[0121] 4.DN

[0122] A DN (Digital Network) is sometimes called a packet data network (PDN) and is a network that extends beyond the operator network. An operator network can access multiple DNs. Application services supporting multiple services may be deployed in a DN to provide multiple possible services to terminal devices.

[0123] In Figure 1, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. For the meaning of these interface sequence numbers, please refer to the definitions provided in the relevant standard protocols, which are not limited to those defined here.

[0124] The 5G communication system is used as an example for illustrative purposes in Figure 1, and it should be understood that the solutions in the embodiments of this application are also applicable to other possible communication systems, such as LTE communication systems or future 6th generation (6G) communication systems. 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 a single device, or by multiple devices together, or as a functional module within a device. This is not particularly limited in the embodiments of this application.

[0125] The following describes the relevant technical features of the embodiments of this application. This description is provided for ease of understanding the embodiments and should not be interpreted as a limitation on the scope of protection claimed herein.

[0126] 1. System information (SI)

[0127] Currently, an SI (System Integration) can include a master information block (MIB) and several system information blocks (SIBs). SIs can be classified into two categories: minimum SI (MSI) and other SI (MSI).

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

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

[0130] 2. SIB1

[0131] Currently, even if a network device supports the functionality of multiple protocol versions, it only supports one SIB1. Specifically, in a cell, the network device sends only one SIB1, and all UEs receiving the SIB1 within 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 sends only one SIB1 does not mean that the SIB1 remains immutable at all times. The SIB1 can change. This can be understood as the network device sending only one SIB1 within a certain period (for example, within the period of the SIB1).

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

[0133] Currently, SIB1 is transmitted via PDSCH, and the PDSCH for transmitting SIB1 is scheduled by DCI, which is scrambled 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 SI messages (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 SI messages (specifically, both are SI-RNTI in the current NR protocol, and only one value for SI-RNTI is supported, and the value of SI-RNTI is FFFF). The length of SI-RNTI is 16 bits. Furthermore, in NR, the transmission of SIB1 may collide with the transmission of SI messages in the time domain. Specifically, the DCI for scheduling SIB1 may collide with the DCI for scheduling SI messages in the time domain. For example, from a protocol perspective, the search spaces for SIB1 and SI messages (i.e., other system information) are set up separately. The UE determining the occasion for monitoring the PDCCH based on the search space settings can be understood as the UE determining the time-domain resources in which it can acquire SIB1 or SI messages through monitoring, based on the search space settings. Note that collisions may be understood as overlaps in this application. Here, the DCI, which is scrambled by using SI-RNTI, is used to schedule SIB1 or SI messages, and one bit in the DCI (specifically, the system information indicator field in the NR protocol) indicates whether the DCI is scheduling SIB1 or SI messages.

[0134] For example, Figure 3 shows scheduling of SIB1 and SI messages based on DCI. As shown in Figure 3, a network device may schedule SIB1 and SI messages separately by using two DCIs, or the network device may schedule data corresponding to SIB1 and data corresponding to SI messages separately by using two DCIs. The format of the two DCIs is 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 DCIs are scheduling SIB1 or SI messages based on the system information indicators within the DCIs.

[0135] Regarding the reception of SIB1 and SI messages, it is important to note that the transmission of SIB1 may conflict with the transmission of SI messages in terms of 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. For the reception of SIB1 and SI messages, the UE's MAC layer supports HARQ decryption. Therefore, it is necessary to indicate in the DCI whether it is scheduling SIB1 or an SI message. If no indication is included, the UE may incorrectly perform HARQ decryption on SIB1 and SI messages received separately. This will result in a decryption error.

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

[0137] In NR, the SI windows of SIB messages do not overlap and are separated in the two time domains for the transmission of different SI messages. Therefore, if a UE receives two DCIs that are scrambled using SI-RNTI, and both indicate that the DCIs are scheduling SI messages, the UE can determine whether the SI messages scheduled by the two DCIs are the same SI message, based on the time domain resources that the DCIs are monitoring (for example, 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 decryption can be performed on the data corresponding to the newly received DCI and the previously received data. If the SI messages scheduled by the two DCIs are different SI messages, HARQ decoding must 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 the NAS, radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, and physical layer (PHY). The user plane protocol stack may include the service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0140] Figure 4 illustrates downlink transmission between layers. In Figure 4, down arrows indicate transmission and up arrows indicate reception. After generating the signaling to be transmitted (e.g., an RRC message or RRC PDU), the RRC layer of the access network device may distribute the signaling to the corresponding PDCP entity. For ease of explanation, signaling may be referred to as data or replaced by data below. In the case of data received from the RRC layer (e.g., a PDCP SDU), the PDCP entity may acquire the PDCP PDU through specific processing or without processing, and then distribute the PDCP PDU to the RLC entity corresponding to the PDCP entity. In the case of data received from the PDCP layer (e.g., an RLC SDU), the RLC entity may acquire the RLC PDU through specific processing or without processing, and then distribute the RLC PDU to the corresponding MAC entity. In the case of data received from the RLC layer (e.g., MAC SDU), the MAC entity may obtain the MAC PDU through specific processing or without processing, and then deliver the MAC PDU to the PHY layer. The PHY layer performs transmission through the air interface. Correspondingly, after receiving data (e.g., transport block, TB) the PHY layer of the terminal device delivers the TB to the MAC layer. In the case of data received from the PHY (e.g., TB or MAC PDU), the MAC entity may obtain the MAC SDU through specific processing or without processing, and then deliver the MAC SDU to the corresponding RLC layer. In the case of data received from the MAC layer (e.g., RLC PDU), the RLC entity may obtain the RLC SDU through specific processing or without processing, and then deliver the RLC SDU to the corresponding PDCP entity. In the case of data received from the RLC layer (e.g., PDCP PDU), the PDCP entity may obtain the PDCP SDU through specific processing or without processing, and then deliver the PDCP SDU to the RLC layer.In the case of data received from the PDCP layer (e.g., RRC messages or RRC PDUs), the data may also be called signaling, and the RRC layer performs RRC decoding or ASN.1 decoding to determine the meaning of the received data (e.g., a bit string).

[0141] For the 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 a higher 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 a higher layer and the data delivered to a lower layer may be the same (e.g., the data is transmitted transparently), or they may be different (e.g., the data delivered to a lower layer is obtained by encapsulating / processing the data received from the higher layer at that layer). For example, data received from a higher layer by a PDCP entity is called a PDCP SDU, and data sent to a lower layer by a PDCP entity is called a PDCP PDU. Similarly, data received from a higher layer by an RLC entity is called an RLC SDU, and data sent to a lower layer by an RLC entity is called an RLC PDU. Data received from a higher layer by a MAC entity is called a MAC SDU, and data sent to a lower layer by a MAC entity is called a MAC PDU. For example, regarding reception: data received by a layer from a lower layer is called a PDU, and data distributed by a layer to a higher layer is called an SDU. For a layer, the data received from a lower layer and the data distributed to a higher layer may be the same (for example, the data is transmitted transparently), or they may be different (for example, the data distributed to a higher layer is obtained by processing the data received from the lower layer at that layer).For example, data received from lower layers by a PDCP entity is called a PDCP PDU, data sent to upper layers by a PDCP entity is called a PDCP SDU, data received from lower layers by an RLC entity is called an RLC PDU, data sent to upper layers by an RLC entity is called an RLC SDU, data received from lower layers by a MAC entity is called a MAC PDU, and data sent to upper layers by a MAC entity is called a MAC SDU.

[0142] In the embodiments of this application, the upper and lower layers 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 lower layer of the RRC layer. However, in the case of the MAC layer, the RLC layer is an upper layer of the MAC layer. As another example, the lower layers of the RRC layer may include one or more of the following: the PHY layer, MAC layer, RLC layer, and PDCP layer.

[0143] Please note that data (or signaling) is not necessarily transmitted or received through all of the above layers. For example, SIB1 and SI messages do not currently need to be transmitted through the PDCP layer.

[0144] It should be noted that in the case of the RLC layer, multiple transmission modes, such as TM, may exist. For example, TM is currently used in the RLC layer for the transmission of SIB1 and SI messages.

[0145] Figure 5 is a diagram of the structure of a MAC PDU. As shown in Figure 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] Note that currently, for the transmission of SIB1 and SI messages, the UE processes the received data (e.g., TB) by using the broadcast-compatible HARQ process. When new data is transmitted, the UE attempts to decode the received data. When data is retransmitted, the UE attempts to perform decryption. If the UE succeeds in performing decryption, the UE delivers the decoded MAC PDU or MAC SDU to the RLC layer. Since the MAC PDU format for 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 transmissions. After receiving data (RLC PDU) from the UE's MAC layer, the UE's RLC layer distributes the RLC PDU or RLC SDU to the RRC layer without any further processing.

[0148] Note that data or signaling (for example, data corresponding to SIB1 or data containing SIB1) has different names at different layers within the protocol. For example, data or signaling is called TB at the physical layer, MAC PDU or MAC SDU at the MAC layer, RLC PDU or RLC SDU at the RLC layer, PDCP PDU or PDCP SDU at the PDCP layer, and 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. Messages corresponding to a logical channel (BCCH) or transport channel (DL-SCH) (e.g., RRC messages, RRC PDUs, RRC message sets, or RRC message classes), or messages transmitted over a logical channel (BCCH) or transport channel (DC-SCH) (e.g., RRC messages, RRC PDUs, RRC message sets, or RRC message classes (e.g., classes)) may be broadcast control channel-downlink shared channel-Messages (BCCH-DL-SCH-Messages). The message structure of a BCCH-DL-SCH-Message or BCCH-DL-SCH-Message may include indicative information to indicate whether the BCCH-DL-SCH-Message contains an SIB1 or SI message, thereby enabling the UE to accurately perform RRC decoding or ASN.1 decoding. For example, a UE receives a DCI that has been scrambled using SI-RNTI, and the DCI indicates that the data or PDSCH scheduled by the DCI is or contains SIB1. The UE's MAC layer performs decoding (HARQ decryption may be performed). After successfully decoding the data scheduled by the DCI that has been scrambled using SI-RNTI, the UE's MAC layer delivers the data to the UE's RRC layer. The UE's RRC layer determines, based on the indication information in the received RRC message, RRC PDU, RRC message set, or RRC message class, that the received RRC message, RRC PDU, RRC message set, or RRC message class contains SIB1. 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 distribution of data to the UE's RRC layer can be understood as follows: the UE's MAC layer distributes data to the UE's RLC layer, and the UE's RLC layer distributes data to the UE's RRC layer.

[0151] 6. SI Message

[0152] Currently, multiple SIBs with the same periodicity may be mapped to a single SI message. A system information message or the message definition of a system information message may include directive information to indicate a specific SIB contained in an RRC message, SI message, or RRC PDU, thereby enabling the UE to perform RRC decoding or ASN.1 decoding.

[0153] 7. DCI Format

[0154] Different DCI formats may support different features. Different DCI formats may support different RNTIs.

[0155] 8. Full and delta configuration of SIB1

[0156] Full configuration is a full or complete configuration mode, and configuring in this mode can be resource-intensive. Delta configuration is a partial configuration mode, where new and / or upgraded parts of a later version are primarily configured relative to the base version. For example, a terminal device may obtain a complete SIB1 of a later version by combining the base version SIB1 with a delta configuration of a later version SIB1.

[0157] 9. Control Resource Set (CORESET)

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

[0159] 10.Search space (SS)

[0160] The search space may represent time-domain resource information for the control channel. The control channel is the physical downlink control channel (PDCCH). The search space includes either a common search space (CSS) or a user-specific search space (USS). The common search space may include the search space corresponding to SIB1, the search space corresponding to paging, the search space corresponding to other system information, the search space corresponding to random access, and so on.

[0161] It should be noted that terminal devices can transmit services by establishing a connection to network devices. Normally, terminal devices can obtain information about accessible networks by receiving SIB1 from network devices. However, in some cases, terminal devices may fail to access the network. For example, if a network device is successfully upgraded but a terminal device fails to upgrade, or if a terminal device cannot be upgraded, and therefore the terminal device is incompatible with the network device, 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 terminal devices or the network in this scenario, many terminal devices may not be able to access the network, resulting in service failure. Therefore, how to solve the problem of low communication reliability due to terminal devices not being able to access the network (successfully) or perform communication (correctly) is currently one of the urgent issues that needs to be resolved.

[0162] Based on this, embodiments of the present application provide a communication method in which communication reliability can be improved. Furthermore, the solution of the present application is applicable to all scenarios in which two or more SIB1s need to be transmitted, and the solution for correctly performing HARQ combinations at the MAC layer and decoding at the RRC layer is universal. Moreover, all access-related information in the present application is described by using SIB1s. However, the names of SIB1s are not limited in the present application. Specifically, the solution of the present application is applicable to the transmission of access-related information. For example, the SIB1s of the present application may be replaced with or understood as information.

[0163] It should be noted that in the embodiments of this 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, resources for DCI 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 this application, DCI scrambling information may be understood as scrambling information corresponding to DCI, DCI format information may be understood as format information corresponding to DCI, DCI time-domain resource information may be understood as time-domain resource information corresponding to DCI, and DCI frequency-domain resource information may be understood as frequency-domain resource information corresponding to DCI.

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

[0165] A DCI used to schedule the first SIB1 may also be described as a DCI used to schedule the first data, which includes the first SIB1. Accordingly, a DCI used to schedule the second SIB1 may be described as a DCI used to schedule the second data, which includes the second SIB1. Specifically, in embodiments 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." Accordingly, in embodiments 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, the DCI used to schedule the SI message may also be described as the DCI used to schedule the third data, which includes the SI message; in the description of an SIB1 set, the DCI used to schedule the SIB1 set may also be described as the DCI used to schedule the fourth data, which includes the SIB1 set; and so on. This is not limited to the above.

[0166] It should be noted that in embodiments of this application, “time-domain resources for DCI” may be understood as the range of time-domain resources for DCI, the search space corresponding to DCI, the range of time-domain resources on which a terminal device monitors DCI, or the time-domain resources on which DCI may exist or appear. For example, a network device may separately configure a search space corresponding to a DCI used to schedule a first SIB1 and a search space corresponding to a DCI used to schedule a second SIB1, and a terminal device may receive one or two of the two search space configurations, or a network device may configure search space configuration parameters corresponding to a DCI used to schedule a first SIB1 and a search space configuration parameters corresponding to a DCI used to schedule a second SIB1, and a terminal device may receive the search space configuration parameters and determine the search space corresponding to a DCI used to schedule a first SIB1 and a search space corresponding to a DCI used to schedule a second SIB1 according to a predefined or protocol-specified method. This is not limited to this application.

[0167] It should be noted that in embodiments of this application, “frequency domain resources for DCI” may be understood as the range of frequency domain resources for DCI, the control resource set corresponding to DCI, the range of frequency domain resources on which a terminal device monitors DCI, or the frequency domain resources on which DCI may exist or appear. For example, a network device may separately configure a control resource set corresponding to DCI used to schedule a first SIB1 and a control resource set corresponding to DCI used to schedule a second SIB1, and a terminal device may receive one or two of the two control resource set settings, or a network device may configure control resource set setting parameters corresponding to DCI used to schedule a first SIB1 and control resource set setting parameters corresponding to DCI used to schedule a second SIB1, and a terminal device may receive the control resource set setting parameters and determine the control resource set corresponding to DCI used to schedule a first SIB1 and the control resource set corresponding to DCI used to schedule a second SIB1 according to a predefined or protocol-specified method. This is not limited to this application.

[0168] It should be noted that the monitoring occasions or search spaces for the DCI used to schedule the first SIB1, and the monitoring occasions or search spaces for the DCI used to schedule the second SIB1, may be predefined in the protocol or determined according to pre-set rules. For example, the overall 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 portion of the common search space corresponds to the DCI used to schedule the first SIB1, and a portion of the common search space corresponds to the DCI used to schedule the second SIB1. This is not limited to the above.

[0169] In the embodiments of this application, "different time-domain resources" may be understood as the time-domain resources not overlapping, and "same time-domain resources" may be understood as the time-domain resources being partially or completely the same, or partially or completely overlapping, and it should be noted that the time-domain resources are not limited to being completely the same. Accordingly, for the understanding of "different frequency domains" and "same frequency domains," please refer to the descriptions of "different time domains" and "same time domains" under the condition that "time domain" is replaced by "frequency domain." Further details are not provided here. DCI in this application may be understood as PDCCH. In the embodiments of this application, "the terminal device determines, based on the first data, that the first data contains the first SIB1" may be understood as follows: the terminal device determines, based on the first data, that the first message contains the first SIB1, or the terminal device determines, based on the first message, that the first message contains the first SIB1. Accordingly, "the terminal device determines, based on the second data, that the second data contains the second SIB1" can be understood as follows: the terminal device determines, based on the second data, that the second message contains the second SIB1, or the terminal device determines, based on the second message, that the second message contains the second SIB1. Accordingly, "the terminal device determines, based on the fourth data, that the fourth data contains the SIB1 set" can be understood as follows: the terminal device determines, based on the fourth data, that the fourth message contains the SIB1 set, or the terminal device determines, based on the fourth message, that the fourth message contains the SIB1 set.

[0170] In this embodiment, 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] The fact that the first data includes the first message can be understood as follows: (1) The first data is associated with the first message, and it should be noted that 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 other layers. In this case, the bits of the first message may not match the bits of the first data. For example, an example is used in description where the length of the first data is 100 bits, and the bit values ​​of the first data are all 0. The length of the first message may be 90 bits, and the bit values ​​of the first message are all 0. (2) The first data includes the bits of the first message. For example, an example is used in description where the length of the first data is 100 bits, and the bit values ​​of the first data are all 0. The length of the first message may be 90 bits, and the bit values ​​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 values ​​of the first data are the same as those of the first message is not limited in this application.

[0172] The understanding that the second data contains the second message may be the same as the understanding that the first data contains the first message, provided that "first" in the relevant description above is replaced with "second". Further details are not provided here again. Accordingly, the understanding that the third data contains the third message may be the same as the understanding that the first data contains the first message, provided that "first" in the relevant description above is replaced with "third". Further details are not provided here again. Accordingly, the understanding that the fourth data contains the fourth message may be the same as the understanding that the first data contains the first message, provided that "first" in the relevant description above is replaced with "fourth". Further details are not provided here again.

[0173] Note that, with respect to the RRC layer, data received from lower layers may typically be referred to as messages, RRC messages, RRC PDUs, RRC message sets, RRC message classes, etc., and this is not limited to these terms. For example, with respect to the RRC layer, data received from lower layers (e.g., first data) may be called the first RRC message, first RRC PDU, first RRC message set, or first RRC message class. As another example, data received from lower layers (e.g., second data) may be called the second RRC message, second RRC PDU, second RRC message set, or second RRC message class. As yet another example, data received from lower layers (e.g., third data) may be called the third RRC message, third RRC PDU, third RRC message set, or third RRC message class. As another example, for an RRC layer, data received from lower layers (e.g., fourth data) may be called a fourth RRC message, fourth RRC PDU, fourth RRC message set, or fourth RRC message class.

[0174] It should be noted that "all or 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. Where possible, the MAC PDU format corresponding to the logical channel and 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. Where possible, the MAC PDU format corresponding to the logical channel and 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 part of the first data (i.e., the first MAC SDU) to the RRC layer for decoding. For ease of description, "all or part of the first data" may be written as "first data" in this application. Similarly, for an understanding of all or part of the second, third, 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." Further details are not provided here again.

[0175] It should be noted that all or part of the first data delivered by the terminal device's MAC layer or PHY layer may be, or may not be, the first message received by the terminal device's RRC layer. For example, all or part of the first data may be delivered directly from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer. As another example, all or part of the first data may be transmitted transparently from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer through other examples. As yet another example, all or part of the first data may be delivered from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer after being processed at other layers.

[0176] It should be noted that, in this application, the distribution of data or instruction information from the MAC layer or PHY layer of the terminal device to the RRC layer of the terminal device can be understood as follows: the data or instruction information may be distributed directly from the MAC layer or PHY layer of the terminal device to the RRC layer of the terminal device, or the data or instruction information may be transparently transmitted from the MAC layer or PHY layer of the terminal device to the RRC layer of the terminal device through other layers, or the data or instruction information may be distributed from the MAC layer or PHY layer of the terminal device to the RRC layer of the terminal device after being processed at other layers.

[0177] For example, the delivery of the first data from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer can be understood as follows: the first data may be delivered directly from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer, or the first data may be transparently transmitted from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer through other layers, or the first data may be delivered from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer after being processed at other layers. Similarly, for an understanding of the delivery of the second, third, or fourth data from the terminal device's MAC layer or PHY layer to the terminal device's RRC layer, please refer to the description of the first data, provided that "first" is replaced with "second," "third," or "fourth." Further details are not provided here again. Similarly, to understand how the third or seventh instruction information is delivered to the terminal device's RRC layer by the terminal device's MAC or PHY layer, please refer to the description of the first data, under the condition that the "first data" is replaced by the "third instruction information" or "seventh instruction information." Further details are not provided here.

[0178] For example, the distribution of the first data from the terminal device's MAC layer to the RRC layer can be understood as follows: the terminal device's MAC layer distributes the first data to the terminal device's RLC layer, the RLC layer distributes the first data to the PDCP layer, and the PDCP layer then distributes the first data to the RRC layer. That is, the terminal device's MAC layer distributes the first data upward layer by layer (for example, Figure 6a shows the distribution of the first data upward layer by layer by the terminal device's MAC layer according to an embodiment of the present application). Alternatively, the distribution of the first data from the terminal device's MAC layer to the RRC layer can be understood as follows: the terminal device's MAC layer distributes the first data to the terminal device's RRC layer through either the RLC layer or the PDCP layer (for example, Figure 6b shows the distribution of the first data from the terminal device's MAC layer to the RRC layer through the RLC layer according to an embodiment of the present application). Alternatively, the distribution of the first data from the terminal device's MAC layer to the RRC layer can be understood as follows: the terminal device's MAC layer directly distributes the first data to the terminal device's RRC layer (for example, Figure 6c shows the distribution of the first data directly to the RRC layer by the terminal device's MAC layer, according to an embodiment of the present application). This will be specifically determined based on the actual scenario and is not limited thereto.

[0179] As another example, the distribution of the first data from the terminal device's PHY layer to the RRC layer can be understood as follows: the terminal device's PHY layer distributes the first data to the terminal device's MAC layer, the terminal device's MAC layer distributes the first data to the terminal device's RLC layer, the RLC layer distributes the first data to the PDCP layer, and finally the PDCP layer distributes the first data to the RRC layer. That is, the terminal device's PHY layer distributes the first data upward layer by layer (for example, Figure 7a shows the distribution of the first data upward layer by layer by the terminal device's PHY layer according to an embodiment of the present application). Alternatively, the distribution of the first data from the terminal device's PHY layer to the RRC layer can be understood as follows: the terminal device's PHY layer distributes the first data to the terminal device's RRC layer through one or two of the MAC layer, RLC layer, and PDCP layer (for example, Figure 7b shows the distribution of the first data from the terminal device's PHY layer to the RRC layer through the RLC layer according to an embodiment of the present application). Alternatively, the distribution of the first data from the terminal device's PHY layer to the RRC layer can be understood as follows: the terminal device's PHY layer directly distributes the first data to the terminal device's RRC layer (for example, Figure 7c shows the distribution of the first data directly to the RRC layer by the terminal device's PHY layer according to an embodiment of the present application). This will be determined specifically based on the actual scenario and is not limited thereto.

[0180] To facilitate understanding the different representations of data scheduled by DCI at different layers in the embodiments of this application, further details will be provided below with reference to Figures 8a and 8b.

[0181] Figure 8a shows a diagram illustrating the reception of data by a terminal device and the execution of processing at each layer, according to an embodiment of the present invention. As shown in Figure 8a, the terminal device receives first data, which is a first MAC PDU. The MAC layer may obtain a first MAC SDU directly or through specific processing (e.g., decomposition 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 a first RLC PDU, which may obtain a first RLC SDU directly (e.g., in 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, sorting, header restoration, and data restoration), the first PDCP PDU may be the same as or different from the first PDCP SDU. The PDCP layer distributes the first PDCP SDU to the RRC layer. The RRC layer receives the first RRC PDU.

[0182] Figure 8b is another diagram illustrating a terminal device receiving data and processing being performed at each layer according to an embodiment of the present invention. As shown in Figure 8b, the terminal device receives first data, which is a first MAC PDU. The MAC layer may obtain a first MAC SDU directly or through specific processing (e.g., decomposition 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 a first RLC PDU, which may obtain a first RLC SDU directly (e.g., in 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 a first RRC PDU.

[0183] Note that when a layer directly distributes data to another layer, the data distributed by the layer may be the same as the data received by the other layer, but the data will have different names in different layers. For example, when the MAC layer distributes the 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 distributes the 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 distributes the 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 distributes the first RLC SDU to the RRC layer, the first RLC SDU is the same as the first RRC PDU.

[0184] Please note that, in order to understand the processing of the second, third, or fourth data in each layer, you may refer to the explanation of the first data, under the condition that "first" is replaced with "second," "third," or "fourth." Further details will not be provided here.

[0185] It should be noted that in the embodiments of this 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 as 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 as the association of the first data with the first LCH. Accordingly, 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 as 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 as the association of the second data with the second LCH. Accordingly, 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 a third RLC entity may also be described as the association of a third message with a third RLC entity, or as the association of third data with a third RLC entity. The association of an SI message with a third LCH may also be described as the association of a third message with a third LCH, or as the association of third data with a third LCH. For ease of description, in this application, the association of a first SIB1 with a first RLC entity or a first SIB1 with a first LCH is used for illustrative purposes, the association of a second SIB1 with a second RLC entity or a second SIB1 with a second RLC is used for illustrative purposes, and the association of an SI message with a third RLC entity or a third LCH is used for illustrative purposes.

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

[0187] The resource information in the embodiments of this application may include time-domain resource information and / or frequency-domain resource information.

[0188] Note that "generated" in this application may be understood as "determined." "Constitute" and "show" in this application may be understood as "include." "Identify" as used in this application may be written as "determined." "Understood as" as used in this application may be written as "include" or "replaced by." "Carried by" as used in this application may be written as "implicitly included in." This is not limited to the above.

[0189] The following describes in detail the communication method and communication device provided in this application.

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

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

[0192] Accordingly, the network device transmits a first downlink control information DCI. The first DCI is used to schedule first data, which includes a first SIB1. The first SIB1 contains information about network access in a first operating mode. Alternatively, this is understood as the first SIB1 being an SIB1 related to the first operating mode.

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

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

[0195] It should be noted that the SIBs included in an SI message may include one or more of SIB2 through SIB14, or may include further SIBs that may be added in the future, such as SIB15 and SIB16. This is not limited to these SIBs.

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

[0197] Note that in this embodiment of the present application, the first operating mode may be secure mode and the second operating mode may be normal mode, or in this embodiment of the present application, the first operating mode may be normal mode and the second operating mode may be secure mode. This is not limited herein. Secure mode can be understood as one or more of the following: restricted operating modes, operating modes used when compatibility issues occur, and operating modes that can be used to identify and / or resolve issues. Normal mode can be understood as one or more of the following: operating modes used when no compatibility issues occur.

[0198] For example, after accessing the network in secure mode, the terminal device may perform one or more of the following processes: reporting a problem, identifying a problem, updating, upgrading, error correction, etc. Another example is when a terminal device cannot access the network in normal mode; in such a case, the terminal device may access the network in secure mode. Another example is when a compatibility issue occurs with the terminal device, or between the terminal device and the network device; in such a case, the terminal device cannot access the network in normal mode, and the terminal device may access the network in secure mode.

[0199] Note that in this embodiment of the present application, secure mode may be understood as the first protocol version, and normal mode may be understood as the second protocol version. In this embodiment of the present application, the first SIB1 may also be understood as the first protocol version of SIB1, and the second SIB1 may be understood as the second protocol version of SIB1. The first protocol version may be the base protocol version (referred to as the base version), or it may be described as the preceding protocol version (referred to as the preceding version), and the second protocol version may be the subsequent protocol version (referred to as the subsequent version). Alternatively, the first protocol version may be the subsequent version, and the second protocol version may be the base version, the preceding version, etc. This is not limited here. The base version SIB1 may be the SIB1 of 5G R18, the first version of SIB1 of 6G, etc. This is not limited here. The subsequent version SIB1 may be the SIB1 of a future communication system, etc. This is not limited here. The base version of SIB1 may be used for secure mode communication, or it may be used for normal mode communication. For example, if a terminal device supporting a later protocol version performs normal communication, the terminal device may combine the base version of SIB1 with the delta configuration of the later version of SIB1 to obtain the complete SIB1 of the later version, or it may use the full configuration of the later version of SIB1. In possible implementations, the information elements and values ​​of the information elements of SIB1 for secure mode are all or some of the same as the information elements and values ​​of the information elements of SIB1 for normal mode. In other possible implementations, SIB1 for secure mode and SIB1 for normal mode may have different settings, for example, they may contain different information elements. If two SIB1s contain the same information elements, the information elements may have different values.For ease of understanding, two SIB1s (e.g., the first SIB1 and the second SIB1) are primarily used below as examples for the detailed description of this embodiment of the present application.

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

[0201] There are numerous ways in which a terminal device can determine, based on the first DCI, that the first data contains the first SIB1. These are described below with reference to Implementations 1-5. Note that specific implementations may be carried out by the physical layer or MAC layer of the terminal device, or by other layers (e.g., other newly defined layers). This is not limited to the present invention.

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

[0203] The first instruction information indicates the type of system message scheduled by the first DCI, or the type of system message contained in the data scheduled by the first DCI. For ease of description, "system message type" is sometimes referred to as "system message type." A system message type includes at least one of the following: first SIB1, second SIB1, or SI message.

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

[0205] In practice, for example, the first instruction information may indicate that the first DCI is scheduling either 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 any other number of bits; this is not limited herein. Optionally, the first field may be a newly defined field. For example, it is assumed that the length of the first field is 1 bit. A value of 0 in the first field may indicate that the DCI is scheduling the first SIB1, and a value of 1 in the first field may indicate that the DCI is scheduling the second SIB1. Alternatively, a value of 0 in the first field may indicate that DCI is scheduling the second SIB1, and a value of 1 in the first field may indicate that DCI is scheduling the first SIB1. This is not limited to the above.

[0206] Optionally, the first 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 DCI will schedule a system message of the corresponding type. For example, a value of 1 indicates that DCI will schedule a system message of the corresponding type, or a value of 0 indicates that DCI will not schedule a system message of the corresponding type. Note that the system message types corresponding to each bit in the bitmap may be set in advance by the protocol or by the network, but are not limited to this application. For example, the bitmap may be 2 bits long, with the first and second bits from left to right corresponding to the first SIB1 and second SIB1, respectively. A value of 1 in the first bit indicates that DCI will schedule the first SIB1. A value of 0 in the first bit indicates that DCI will not schedule the first SIB1.

[0207] Optionally, if the first instruction information indicates that the first DCI will schedule a first SIB1 or a second SIB1, the first instruction information may further execute a combined instruction with the second field or the tenth instruction information (e.g., the system information indicator field) to indicate a specific SIB1 to be scheduled by the DCI, or to indicate that an SIB message will be scheduled. Different values ​​of the second field or the tenth instruction information may indicate whether the DCI will schedule an SIB1 or an SI message. Specifically, whether the DCI will schedule an SIB1 or an SI message may first be determined based on the second field or the tenth instruction information. If it is determined that the DCI will schedule 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 instruction information within the DCI.

[0208] In other embodiments, the first instruction information may indicate that the first DCI is scheduling a first SIB1, a second SIB1, or an SI message. Different values ​​of the first field may indicate a specific SIB1 (e.g., first SIB1 or second SIB1) or SI message scheduled by the first DCI, or a specific SIB1 (e.g., first SIB1 or second SIB1) or SI message contained in data scheduled by the first DCI. The length of the first field may be 2 bits, 4 bits, or any other number of bits; this is not limited herein. For example, assume 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 is scheduling a first SIB1, a value of 10 in the first field may indicate that the DCI is scheduling a second SIB1, and a value of 00 in the first field may indicate that the DCI is scheduling an SI message. Alternatively, a value of 01 in the first field can indicate that DCI is scheduling the first SIB1, a value of 10 in the first field can indicate that DCI is scheduling the second SIB1, and a value of 11 in the first field can indicate that DCI is scheduling an SI message. Examples are not explained one by one here.

[0209] Optionally, the first 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 DCI will schedule a system message of the corresponding type. For example, a bit value of 1 indicates that DCI will schedule a system message of the corresponding type, or a bit value of 0 indicates that DCI will not schedule a system message of the corresponding type. Note that the system message types corresponding to each bit in the bitmap may be set in advance by the protocol or by the network. This is not limited to the present invention.

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

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

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

[0213] Please note that in Implementation 1, one or more of the following DCIs corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI) may be the same as those corresponding to the DCI used to schedule the second SIB1 (e.g., the second DCI).

[0214] (1) The time-domain resources may be the same. Here, the time-domain resources include the range of time-domain resources monitored by the DCI for scheduling the SIB, the search space, etc.

[0215] (2) The frequency domain resources may be the same, where the frequency domain resources include the range of frequency domain resources monitored by the DCI for scheduling the SIB, the 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 for DCI may be the same. For example, the scrambling information may include SI-RNTI, and the value of 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 content scrambled by different DCIs or types of system messages scrambled by different DCIs based on the scrambling information of different DCIs. For example, a terminal device may determine, based on the scrambling information of a first DCI, that data scrambled by a first DCI includes a first SIB1. For example, a terminal device may determine, based on the scrambling information of a second DCI, that data scrambled by a second DCI includes a second SIB1. The scrambling information of the first DCI is different from the scrambling information of the second DCI.

[0220] For example, the scrambling information for the first DCI may be SI-RNTI, and the scrambling information for the second DCI may be another RNTI (e.g., a newly defined RNTI), or the scrambling information for the second DCI may be SI-RNTI, and the scrambling information for the first DCI may be another RNTI (e.g., a newly defined RNTI). This is not limited here. Another example is that the scrambling information for the first DCI may be RNT (e.g., a newly defined RNTI1), and the scrambling information for the second DCI may be another RNTI (a newly defined RNTI2). This is not limited here. Note that the scrambling information for the fifth DCI may be the same as the scrambling information for the first DCI, or the scrambling information for the fifth DCI may be the same as the scrambling information for the second DCI, or the scrambling information for the fifth DCI may be different from both the scrambling information for the first DCI and the scrambling information for the second DCI. This is not limited to the present application.

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

[0222] Note that in Implementation 2, one or more of the following: time-domain resources, frequency-domain resources, and DCI format, corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI), 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 the first SIB1 based on the DCI format of the first DCI.

[0224] It can be understood that terminal devices may distinguish between content scheduled by different DCIs or between types of system messages scheduled by different DCIs, based on the DCI format of different DCIs.

[0225] For example, a 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, a 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 DCI format used to schedule the first SIB1 may be DCI format 1_0, and the DCI format used to schedule the second SIB1 may be another DCI format (e.g., a newly defined DCI format), or the DCI format used to schedule the second SIB1 may be DCI format 1_0, and the DCI format used to schedule the first SIB1 may be another DCI format (e.g., a newly defined DCI format). As another example, both the DCI format used to schedule the first SIB1 and the DCI format used to schedule the second SIB1 may be a newly defined DCI format. This is not limited here.

[0226] It should be noted that the DCI format of the 5th DCI may be the same as the DCI format of the 1st DCI, or the DCI format of the 5th DCI may be the same as the DCI format of the 2nd DCI, or the DCI format of the 5th DCI may be different from both the DCI format of the 1st DCI and the DCI format of the 2nd DCI. This is not limited to the present invention.

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

[0228] Note that in Implementation 3, one or more of the following: time-domain resources, frequency-domain resources, and DCI scrambling information, corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI), 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 time-domain resources for the first DCI.

[0230] It can be understood that a terminal device may distinguish content scheduled by different DCIs based on time-domain resources for those 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 resource for the fifth DCI may be the same as the time-domain resource for the first DCI, or the time-domain resource for the fifth DCI may be the same as the time-domain resource for the second DCI, or the time-domain resource for the fifth DCI may be different from both the time-domain resource for the first DCI and the time-domain resource for the second DCI. This is not limited to the present invention.

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

[0233] Note that in Implementation 4, one or more of the following: frequency domain resources, DCI format, and DCI scrambling information, corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI), 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 the first SIB1 based on frequency domain resources for the first DCI.

[0235] It can be understood that a terminal device may distinguish content scheduled by different DCIs based on frequency-domain resources for those 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, the control resource set for the DCI used to schedule the first SIB1 is CORESET#0, and the control resource set for the DCI used to schedule the second SIB1 is CORESET#1.

[0236] It should be noted that the frequency domain resources for the 5th DCI may be the same as the frequency domain resources for the 1st DCI, or the frequency domain resources for the 5th DCI may be the same as the frequency domain resources for the 2nd DCI, or the frequency domain resources for the 5th DCI may be different from both the frequency domain resources for the 1st DCI and the frequency domain resources for the 2nd DCI. This is not limited to the present invention.

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

[0238] Note that in Implementation 5, one or more of the following: time-domain resources, DCI format, and DCI scrambling information, corresponding to the DCI used to schedule the first SIB1 (e.g., the first DCI), 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 five implementations described above may be combined with each other or implemented independently. This is not limited to the present invention. It should also be noted that implementations 2, 3, 4, and 5 may be performed before the terminal device receives, successfully receives, or monitors a DCI. This will be determined specifically based on the actual application scenario and is not limited thereto. 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 to the present invention. For example, in embodiments 2, 3, 4, and 5, step S902 may be performed before step S901. As another example, in embodiment 1, step S902 may be performed after step S901.

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

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

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

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

[0245] After a terminal device receives first data from a network device based on first DCI, the terminal device may further decode (e.g., ASN.1 decode) the content contained in the first data based on the first data. Specifically, the terminal device may identify the content contained in the first data in one or more of the following implementations (1) to (3), and then decode the identified content according to the decoding scheme corresponding to the identified content. The three implementations may be understood as being performed at the RRC layer of the terminal device, or they may be performed at other layers (e.g., other newly defined layers), but are not limited thereto. Specifically, after successfully receiving the first data, the MAC layer, PHY layer, or other newly defined layer of the terminal device may deliver all or part of the first data to the RRC layer or other layer (e.g., another newly defined layer) of the terminal device, and the first data is then decoded at the RRC layer or other layer (e.g., another newly defined layer) of the terminal device. Implementations (1) to (3) are described separately in detail below.

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

[0247] The second instruction information may be carried in the first data or first message transmitted by the network device to the terminal device, and the second instruction information indicates the type of system message contained in the first data or first message, i.e., the system message type. The system message type includes at least one of the first SIB1, second SIB1, or SI message.

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

[0249] In practice, for example, the second instruction information may indicate that the first data or first message contains a first SIB1 or a second SIB1. Different values ​​of the third field may indicate a specific SIB1 (e.g., first SIB1 or second SIB1) contained in the first data or first message. The length of the third field may be 1 bit, 2 bits, 4 bits, or any other number of bits. This is not limited herein. For example, assume the length of the third field is 1 bit. A value of 0 in the third field may indicate that the first data or first message contains a first SIB1, and a value of 1 in the third field may indicate that the first data or first message contains a second SIB1. Alternatively, a value of 0 in the third field may indicate that the first data or first message contains a second SIB1, and a value of 1 in the third field may indicate that the first data or first message contains a first SIB1. This is not limited herein.

[0250] Optionally, the third 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 first message contains a system message of the corresponding type. For example, a bit value of 1 indicates that the first data or first message contains a system message of the corresponding type, or a bit value of 0 indicates that the first data or first message does not contain a system message of the corresponding type. Note that the system message types corresponding to each bit in the bitmap may be set in advance by the protocol or set by the network. This is not limited to this application. For example, the length of the bitmap is 2 bits, and the first and second bits from left to right correspond to the first SIB1 and second SIB1, respectively. If the value of the first bit is 1, it indicates that the first data or first message contains the first SIB1. If the value of the first bit is 0, it indicates that the first data or first message does not contain the first SIB1.

[0251] Optionally, if the second instruction indicates that the first data or first message contains a first SIB1 or a second SIB1, the second instruction may further perform a combined instruction with the fourth field or eleventh instruction to indicate a specific SIB1 contained in the first data or first message, or to indicate that an SIB message is contained. Different values ​​of the fourth field or eleventh instruction may indicate whether the first data or first message contains an SIB1 or an SI message. Specifically, whether the first data or first message contains an SIB1 or an SI message may first be determined based on the fourth field or eleventh instruction. If it is determined that the first data or first message contains an SIB1, the specific SIB1 contained in the first data or first message is further determined based on a specific value of the third field or second instruction in the DCI.

[0252] In other embodiments, the second instruction information may indicate that the first data or first message contains a first SIB1, a second SIB1, or an SI message. Different values ​​of the third field may indicate a specific SIB1 (e.g., the first SIB1 or the second SIB1) or SI message contained in the first data or first message. The length of the third field may be 2 bits, 4 bits, or any other number of bits; this is not limited herein. For example, assume that the length of the third field is 2 bits. In this case, a value of 01 in the third field may indicate that the first data or first message contains a first SIB1, a value of 10 in the third field may indicate that the first data or first message contains a second SIB1, and a value of 00 in the third field may indicate that the first data or first message contains an SI message. Alternatively, a value of 01 in the third field may indicate that the first data or first message contains the first SIB1; a value of 10 in the third field may indicate that the first data or first message contains the second SIB1; and a value of 11 in the third field may indicate that the first data or first message contains an SI message. Examples are not explained one by one here.

[0253] Optionally, the third 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 first message contains a system message of the corresponding type. For example, a bit value of 1 indicates that the first data or first message contains a system message of the corresponding type, or a bit value of 0 indicates that the first data or first message does not contain a system message of the corresponding type. Note that the system message types corresponding to each bit in the bitmap may be set in advance by the protocol or by the network. This is not limited to the present application. For example, the bitmap may have a length of 3 bits, where the first, second, and third bits from left to right correspond to the first SIB1, second SIB1, and SI message, respectively. If the value of the first bit is 1, it indicates that the first data or first message contains the first SIB1. If the value of the first bit is 0, it indicates that the first data or first message does not contain the first SIB1.

[0254] In implementation (2), the terminal device acquires third instruction information related to the first message.

[0255] The phrase "the terminal device obtains third instruction information related to the first message" can be understood as follows: The terminal device's RRC layer obtains third instruction information related to the first message from the terminal device's lowest layer. The third instruction information indicates the type of system message contained in the first data or first message, i.e., the system message type. The system message type includes at least one of the following: first SIB1, second SIB1, or SI message.

[0256] The “lowest layer of the terminal device” may include any one of the following: the terminal device’s PHY layer, the terminal device’s MAC layer, the terminal device’s RLC layer, or the terminal device’s PDCP layer. Here, the lowest layer of the terminal device may distribute the third instruction information to the RRC layer layer by layer, or distribute the third instruction 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 may distribute the third instruction information directly to the RRC layer of the terminal device.

[0257] It can be understood that the RRC layer of a terminal device not only acquires a first message but also acquires third instruction information associated with the first message. Based on the third instruction information, the RRC layer of the terminal device may determine the type of system message contained in the first data or first message. It should be noted that the implementation of acquiring a first message by the RRC layer of a terminal device may be the same as or different from the implementation of acquiring third instruction information by the RRC layer of a terminal device. This is not limited to the present invention.

[0258] Note that it should be noted that the third indication information may not be included in the first data. For example, the third indication information may be generated by the terminal device based on DCI (e.g., the information of the first DCI). For example, when the third indication information is generated by the 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, it may be included in any one of the following corresponding to the first data: the MAC sub-header of the first MAC PDU, the RLC header of the first RLC PDU, or the PDCP header of the first PDCP PDU. For example, when the third indication information is generated by the MAC layer of the terminal device, the third indication information may be included in the MAC sub-header (e.g., the MAC sub-header of the first MAC PDU). When the third indication information is generated by the RLC layer of the terminal device, the third indication information may be included in the RLC header (e.g., the RLC header of the first RLC PDU). When the third indication information is generated by the PDCP layer of the terminal device, the third indication information may be included in the PDCP header (e.g., the PDCP header of the first PDCP PDU).

[0259] During actual implementation, the specific expression form of the third indication information may be the first indication information obtained based on the first DCI, the information extracted from the first indication information, etc. This is not limited here. Therefore, 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 form of the third indication information may be the information obtained from the scrambling information of the DCI, or may be the scrambling information of the DCI, etc. This is not limited here. Alternatively, the specific expression form of the third indication information may be the information obtained from the DCI format, or may be the DCI format, etc. This is not limited here. Alternatively, the specific expression form of the third indication information may be the information obtained from the monitoring occasion, the search space, or the time domain resource for the DCI, or may be the monitoring occasion, the search space, or the time domain resource for the DCI. This is not limited here. Alternatively, the specific expression form of the third indication information may be the information obtained from the frequency domain resource or the control resource set for the DCI, or may be the frequency domain resource where the DCI is monitored, the control resource set, etc. This is not limited here.

[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 one or both of the SI message and the first SIB1 and the second SIB1 may correspond to the same logical channel and / or the same RLC entity. This is not limited in this 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, the second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1. The first RLC entity is different from the second RLC entity, and the first LCH is different from the second LCH.

[0262] Therefore, a terminal device (for example, the terminal device's RRC layer or other layers) may determine the content contained in received data or a received message based on LCH or RLC entities associated with different data or messages. For example, a terminal device may determine that the first data contains a first SIB1 based on the first LCH or first RLC entity associated with the first data. As another example, it may determine that the second data contains a second SIB1 based on the second LCH or second RLC entity associated with the second data. As yet another example, it may determine that the third data contains an SI message based on the third LCH or third RLC entity associated with the third data.

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

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

[0265] Please note that one or more of Implementation 1 to Implementation 5 may be combined with one or more of Implementation (1) to Implementation (3). This is not limited to the above.

[0266] For example, Implement 1 and Implement (1) are used as examples. The terminal device monitors the scrambled PDCCH using SI-RNTI. The terminal device receives the scrambled DCI using SI-RNTI. Based on the fact that the system information indicator field contained in the DCI is 0, the terminal device decides that the DCI will schedule SIB1. Based on the first instruction information contained in the DCI, the terminal device decides that the SIB1 scheduled by the DCI is the first SIB1. The terminal device performs decoding using the broadcast-compatible HARQ process. If decoding is successful, the terminal device's MAC layer distributes the data to the terminal device's RRC layer for processing through the RLC layer. If decoding fails, the terminal device re-receives another scrambled DCI using SI-RNTI, and the re-received DCI also indicates that the DCI will schedule the first SIB1. The terminal device may perform decryption on the currently received data and the previously received data. If decoding is successful, the MAC layer of the terminal device similarly distributes the data to the RRC layer of the terminal device for processing through the RLC layer. Based on the second instruction information contained in the RRC message, the RRC layer may determine that the RRC message contains a first SIB1 and then perform RRC decoding by using the ASN.1 of the first SIB1.

[0267] As another example, MAC layer processing and RRC layer processing are performed according to implementation 1 and implementation (2), respectively. The terminal device monitors the scrambled PDCCH using SI-RNTI. The terminal device receives the scrambled DCI using SI-RNTI. Based on the fact that the system information indicator field contained in the DCI is 0, the terminal device (in the prior art) decides that the DCI will schedule SIB1. Based on the first instruction information contained in the DCI, the terminal device decides that the SIB1 scheduled by the DCI is the first SIB1. The terminal device performs decoding using the broadcast-compatible HARQ process. If decoding is successful, the terminal device's MAC layer delivers the data to the terminal device's higher layer (e.g., the RRC layer). If decoding fails, the terminal device re-receives another scrambled DCI using SI-RNTI, and the re-received DCI also indicates that the DCI will schedule the first SIB1. The terminal device may perform decryption on the currently received data and the previously received data. If decoding is successful, the MAC layer of the terminal device similarly distributes the data to the higher layer of the terminal device (e.g., the RRC layer). Based on the third instruction information received from the MAC layer, the RRC layer may determine that the RRC message contains the first SIB1 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 the scrambled PDCCH using SI-RNTI. The terminal device receives the scrambled DCI using SI-RNTI. Based on the fact that the system information indicator field contained in the DCI is 0, the terminal device decides that the DCI will schedule SIB1. Based on the first instruction information contained in the DCI, the terminal device decides that the SIB1 scheduled by the DCI is the first SIB1. The terminal device performs decoding using the broadcast-compatible HARQ process. If decoding is successful, the terminal device's MAC layer delivers the data to the terminal device's RRC layer through the RLC layer. If decoding fails, the terminal device re-receives another scrambled DCI using SI-RNTI, and the re-received DCI also indicates that the DCI will schedule the first SIB1. The terminal device may perform decryption on the currently received data and the previously received data. If 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 contains the first SIB1 by receiving data from the RLC entity corresponding to the first SIB1, and can then perform RRC decoding using the ASN.1 of the first SIB1.

[0269] It can be understood that other combinations between Implementations 2-5 and Implementations (1)-(3) will not be explained one by one here by using examples.

[0270] Optionally, in some feasible implementations, in scenarios involving three or more SIB1s, specifically in scenarios where a network device may transmit additional SIB1s (e.g., third and fourth SIB1s) in addition to the first and second SIB1s, similar to the above description of the first and second SIB1s, different SIB1s may also be distinguished based on one or more of the following for decoding by a terminal device (e.g., the MAC layer, PHY layer, or other layer of the terminal device): first instruction information or first field in the DCI, scrambling information in the DCI, DCI format, time-domain resources for the DCI, or frequency-domain resources for the DCI. Correspondingly, for decoding by a terminal device (or the RRC layer or other layer of the terminal device), different SIB1s may also be distinguished based on one or more of the following: second instruction information, third instruction information, or logical channels (or RLC entities).

[0271] For example, suppose there are four SIB1s: one corresponding to version N, one to version N+1, one to version N+2, and one to version N+3. The SIB1 corresponding to version N is the earlier version SIB1. The SIB1s corresponding to version N+1, N+2, and N+3 are all later versions of SIB1. For decoding by a terminal device (e.g., the terminal device's MAC layer, PHY layer, or other layers):

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

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

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

[0275] In implementation 4, if a time-domain resource for DCI is used to distinguish between different versions of SIB1, then 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 resources 1 through 4 are distinct from each other. Thus, a terminal device may determine a particular SIB1 to be scheduled by DCI based on the time-domain resource for DCI.

[0276] In implementation 5, if frequency domain resources for DCI are used to distinguish different versions of SIB1, then 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 resources 1 through 4 are distinct from each other. Thus, a terminal device may determine a particular SIB1 to be scheduled by DCI based on the frequency domain resources for DCI.

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

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

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

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

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

[0282] Correspondingly, the network device may send the fourth indication information to the terminal device. The fourth indication information indicates whether a specific SIB1 (for example, the first SIB1 and / or the second SIB1) exists in the cell or on the network device, or whether the network device should send a specific SIB1 (for example, the first SIB1 and / or the second SIB1), or whether the cell or the network device supports a specific operation mode (for example, the first operation mode and / or the second operation mode), or whether the cell or the network device may indicate whether to send different SIB1s 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 particular cell or network device transmits a different SIB1 by using the solution of this embodiment of the application, or whether a network device transmits a particular SIB1 (e.g., a first SIB1) by using the solution of this embodiment of the application, or whether a cell or network device supports a particular operating mode (e.g., a first operating mode). Furthermore, if the terminal device can know in advance that a 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 saves energy for the terminal device. It should be noted that the step of the terminal device receiving the fourth instruction information from the network device may be performed before step S901, or at the same time as step S901 is performed. This is not limited herein. The field used to carry the fourth instruction information may contain one bit, two bits, or more bits. This is not limited herein. Furthermore, the reception of the fourth instruction information by a terminal device from a network device can be understood as follows: the terminal device receives an MIB from the network device, and the MIB contains the fourth instruction information. Alternatively, the reception of the fourth instruction information by a terminal device from a network device can be understood as follows: the terminal device receives a second DCI from the network device, and the second DCI contains the fourth instruction information. Alternatively, the reception of the fourth instruction information by a terminal device from a network device can be understood as follows: the terminal device receives a fifth DCI from the network device, and the fifth DCI contains the fourth instruction information. That is, the fourth instruction information may be carried in an MIB, or in a second DCI for scheduling a second SIB1 or second data, or in a fifth DCI for scheduling an SI message.

[0284] Note that if the first SIB1 is an SIB1 associated with a preceding version or secure mode, and the second SIB1 is an SIB1 associated with a subsequent version or normal mode, the fourth instruction information may be carried by the MIB, or by the DCI for scheduling the second SIB1, or by the DCI for scheduling the SI message. If the first SIB1 is an SIB1 associated with a subsequent version or normal mode, and the second SIB1 is an SIB1 associated with a preceding version or secure mode, the fourth instruction information may be carried by the second SIB1 or the second data, in addition to the MIB, the DCI for scheduling the second SIB or second data, or the DCI for scheduling the SI message.

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

[0286] In this embodiment of the present application, the network device transmits or broadcasts, for example, at least one data including first data corresponding to a first SIB1 and / or second data corresponding to a second SIB1, to ensure that a terminal device can obtain the first SIB1 and / or the second SIB1. It is assumed that the first SIB1 is an SIB1 associated with secure mode and the second SIB1 is an SIB1 associated with normal mode. If the terminal device cannot obtain the second SIB1 or cannot access the network based on the second SIB1 due to compatibility issues, the terminal device can still obtain the first SIB1 and access the network based on the first SIB1. This ensures a basic communication channel between the terminal device and the network device, thereby enabling basic communication between the terminal device and the network device. Different SIB1s are scheduled by independent DCIs. For example, the first data is scheduled based on a first DCI and the second data is scheduled based on a second DCI. This solves the problem of the network device scheduling different SIB1s. This ensures that a terminal device can obtain the first SIB1 and / or the second SIB1. For the terminal device PHY layer or MAC layer, DCIs used to schedule different SIB1s are distinguished based on the first instruction information within the DCI, the scrambling information of the DCI, the DCI format, the time-domain resources for the DCI, or the frequency-domain resources for the DCI. In this way, the terminal device can accurately identify the content scrambled by the DCI and correctly perform HARQ combinations to improve the reliability of data reception. For the terminal device's RRC layer, the terminal device can accurately identify the content contained in the first message and correctly perform RRC decoding to obtain accurate information based on the second instruction information, inter-layer interactions (i.e., third instruction information), or logical channels within the first message.Furthermore, whether a 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 itself. This helps conserve energy in terminal devices.

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

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

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

[0290] The 4th DCI is used to schedule the 1st data. Compared to a solution where at least two data are scheduled by the 3rd DCI, the scheduling mode in which the 2nd data and the 4th DCI are scheduled by the 3rd DCI is more flexible.

[0291] For ease of understanding, an example in which at least two data points, the first data and the second data, are included will be primarily used below for the detailed description of this embodiment of the application. For understanding the first and second data in this embodiment of the application, please refer to the relevant description of the first and second data in step S901 of Figure 9. Further details will not be described here again.

[0292] The following specifically describes the solution used by the 3rd DCI to schedule at least two data sets. The at least two data sets include the first data set and the second data set. The first data set includes the first SIB1, and the second data set includes the second SIB1.

[0293] For example, Figure 12 is a diagram of a scheduling mode according to an embodiment of the present invention. As shown in Figure 12, a network device can schedule at least two SIB1s, or at least two 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, a terminal device may determine resource information for data corresponding to a second SIB1 and resource information for data corresponding to a first SIB1 based on the DCI. In other words, a terminal device may determine resource information for second data and resource information for first data based on the DCI.

[0294] Specifically, the third DCI includes scheduling information for the second data. For example, resource information for the second data (e.g., time-domain resource information and / or frequency-domain resource information) is set in the third DCI. Note that the method for specifying the resource information for the second data in the third DCI is not limited in this application, and direct or indirect specification may be performed. The scheduling information in this embodiment of this 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 for the first data may be dynamically set in the third DCI (this may be called dynamic setting), or statically set (this may be called static setting), or quasi-statically set (this may be called quasi-static setting). This is not limited to the present invention.

[0296] Dynamic configuration can be understood as the scheduling information for the first data being set in the third DCI. For example, the third DCI carries or includes information about time-domain and frequency-domain resources for the first data.

[0297] The 3rd DCI may carry or include information about time-domain resources for the first data by direct and / or indirect instructions. "The 3rd DCI may carry or include information about time-domain resources for the first data by direct instructions" can be understood or indicated as the information about time-domain resources for the first data being directly set in the 3rd DCI (for example, the information about time-domain resources for the first data may include one or more of the following: the start of the time-domain resources for the first data, the length of the time-domain resources for the first data, and the end of the time-domain resources for the first data). "The 3rd DCI may carry or include information about time-domain resources for the first data by indirect instructions" can be understood or indicated as one of the following implementations:

[0298] (1) Information regarding the interval between the time-domain resource for the 3rd DCI and the time-domain resource for the 1st data is shown in the 3rd 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 shown in the third DCI.

[0300] The 3rd DCI may carry or include frequency domain information for the first data by direct and / or indirect instruction. For an understanding of "the 3rd DCI may carry or include information for frequency domain resources for the first data by direct instruction," see the above explanation of "the 3rd DCI may carry or include information for time domain resources for the first data by direct instruction," provided that "time domain" is replaced with "frequency domain." Further details are not provided here again. Accordingly, for an understanding of "the 3rd DCI may carry or include information for frequency domain resources for the first data by indirect instruction," see the above explanation of "the 3rd DCI may carry or include information for time domain resources for the first data by indirect instruction," provided that "time domain" is replaced with "frequency domain." Further details are not provided here again.

[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. This will be specifically determined based on the actual application scenario and is not limited thereto. The interval between frequency-domain resources may be of various granularities, such as carriers or frequency bands. This will be specifically determined based on the actual application scenario and is not limited thereto.

[0302] Please note that the time domain start point for the "interval between the time domain resource for the 3DCI 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 3DCI, the end of the time domain resource for the 3DCI, the point in time before the start of the time domain resource for the 3DCI, the point in time after the end of the time domain resource for the 3DCI, the symbol / slot / subframe / frame to which the time domain resource for the 3DCI belongs, the start of the symbol / slot / subframe / frame to which the time domain resource for the 3DCI belongs, the end of the symbol / slot / subframe / frame to which the time domain resource for the 3DCI belongs, the point in time before the start of the symbol / slot / subframe / frame to which the time domain resource for the 3DCI belongs, and the point in time after the end of the symbol / slot / subframe / frame to which the time domain resource for the 3DCI belongs. The end of the time domain for the "interval between the time domain resource for the 3rd DCI and the time domain resource for the 1st data" may be any one of the following: the start of the time domain resource for the 1st DCI, the end of the time domain resource for the 1st DCI, a point in time before the start of the time domain resource for the 1st DCI, a point in time after the end of the time domain resource for the 1st DCI, the symbol / slot / subframe / frame to which the time domain resource for the 1st DCI belongs, the start of the symbol / slot / subframe / frame to which the time domain resource for the 1st DCI belongs, the end of the symbol / slot / subframe / frame to which the time domain resource for the 1st DCI belongs, a point in time before the start of the symbol / slot / subframe / frame to which the time domain resource for the 1st DCI belongs, and a point in time after the end of the symbol / slot / subframe / frame to which the time domain resource for the 1st DCI belongs. Similarly, for the understanding of the "interval between the time domain resource for the 2nd data and the time domain resource for the 1st data," only the substitution of "of the 3rd DCI" with "of the 2nd data" is required. Further details are not provided here again.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 zero. In possible implementations, the time-domain resource for the second data may be the same as the time-domain resource for the first data. The positional order of the second and first data in the time domain is not limited in this application.

[0303] The start (or end) of the "interval between the frequency domain resource for the 3rd DCI and the frequency domain resource for the first data" may be any one of the following: the start of the frequency domain resource for the 3rd DCI, the end of the frequency domain resource for the 3rd DCI, the frequency before the start of the frequency domain resource for the 3rd DCI, and the frequency after the end of the frequency domain resource for the 3rd DCI. The end (or start) of the "interval between the frequency domain resource for the 3rd DCI and the frequency domain resource for the first data" may be any one of the following: the start of the frequency domain resource for the 1st DCI, the end of the frequency domain resource for the 1st DCI, the frequency before the start of the frequency domain resource for the 1st DCI, and the frequency after the end of the frequency domain resource for the 1st DCI. In this embodiment of the present application, the interval between the frequency domain resource for the 3rd DCI and the frequency domain resource for the first data may alternatively be 0. In possible implementations, the frequency domain resource for the 3rd DCI may be the same as the frequency domain resource for the first data. It should be understood that the positional order of the third DCI and the first data in the frequency domain is not limited in this application. Similarly, the understanding of "the interval between the frequency domain resources for the second data and the frequency domain resources for the first data" only requires that "third DCI" be replaced with "second data". Further details are not provided here.

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

[0305] Static configuration can be understood as determining the scheduling information for the first data based on the first prior information.

[0306] In possible implementations, the first transcendental information includes first interval information and second interval information. The first transcendental information may be set by a network device, for example by using RRC messages, or it may be pre-configured, or it may be defined by a protocol. This is not limited to the above.

[0307] The first interval information includes information about the interval between a time-domain resource for the third DCI and a time-domain resource for the first data, or information about the 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 the interval between a frequency-domain resource for the third DCI and a frequency-domain resource for the first data, or information about the interval between a frequency-domain resource for the second data and a frequency-domain resource for the first data. Optionally, the first priori information may further include one or more of the following: information about the length of the time-domain resource for the first data, information about the length of the frequency-domain resource for the first data, information about the MCS, and information about the TBS.

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

[0309] A quasi-static configuration can be understood as the time-domain resource information for the first data being dynamically configured in the third DCI, while the frequency-domain resource information (or second interval information) for the first data being statically configured. Alternatively, a quasi-static configuration can be understood as the frequency-domain resource information for the first data being dynamically configured in the third DCI, while the time-domain resource information (or first interval information) for the first data being statically configured.

[0310] The following specifically describes the solution used by the 3rd DCI to schedule the 2nd and 4th data.

[0311] The 4th DCI is used to schedule the first data. The first data includes the first SIB1, and the second data includes the 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. Based on the third DCI, the terminal device may determine the resource information for the data corresponding to the second SIB1 and the resource information for the fourth DCI.

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

[0314] The scheduling information for the 4th DCI may be dynamically set in the 3rd DCI (this may be called dynamic setting), or the scheduling information for the 4th DCI may be statically set (this may be called static setting), or the scheduling information for the 4th DCI may be quasi-statically set (this may be called quasi-static setting). This is not limited to the present invention.

[0315] Regarding the understanding of how the scheduling information for the 4th DCI is set dynamically, statically, or quasi-statically, please note that the above explanation of how the scheduling information for the 1st data is set dynamically, statically, or quasi-statically can be referenced, provided that the "1st data" is replaced by the "4th DCI". Further details are not provided here.

[0316] In some feasible implementations, a network device may schedule two SIB1s, namely the first SIB1 and the second SIB1. In such scenarios, 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, SIB1 may be the 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 contain scheduling information for another SIB1, or data corresponding to one SIB1 may contain scheduling information for another 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 may be described as follows: The DCI for the data corresponding to the second SIB1 is used to schedule the data corresponding to the second SIB1. The second SIB1 or the data corresponding to the second SIB1 contains scheduling information for the first SIB1. Alternatively, this may be understood as the second SIB1 or the data corresponding to the second SIB1 being able to schedule the first SIB1, or as the second SIB1 or the data corresponding to the second SIB1 containing scheduling information for the data corresponding to the first SIB1, or as the second SIB1 or the data corresponding to the second SIB1 being able to schedule the first SIB1 or the data corresponding to the first SIB1. A terminal device may determine the position of a PDSCH corresponding to data corresponding to the second SIB1 based on the DCI corresponding to the data corresponding to the second SIB1, and may determine the position of a PDSCH corresponding to data corresponding to the first SIB1 based on the second SIB1 or the data corresponding to the second SIB1. The scheduling information for the first SIB1 may be dynamically set in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information for the first SIB1 may be statically set, or the scheduling information for the first SIB1 may be quasi-statically set. This is not limited thereto. Furthermore, regarding the understanding that the scheduling information for the first SIB1 may be dynamically set in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information for the first SIB1 may be statically set, or the scheduling information for the first SIB1 may be quasi-statically set, please note that the above explanation in Figure 12, which states that the scheduling information for the first data may be dynamically set in the third DCI, or the scheduling information for the first data may be statically set, or the scheduling information for the first data may be quasi-statically set, should be referred to. Details will not be described again here.

[0319] Optionally, in some feasible implementations, a network device may further transmit fifth directive information to a terminal device, which may indicate that the second SIB1 is present on the network device or should be transmitted by the network device. The fifth directive information may be carried in an MIB transmitted by the network device to the terminal device, or it may be carried in a DCI used to schedule the second SIB1, etc., but is not limited thereto. Optionally, whether the first SIB1 is present on the network may be further determined based on whether the second SIB1 or the data corresponding to the second SIB1 contains scheduling information for the first SIB1.

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

[0321] For example, Figure 15 is a diagram of another scheduling mode according to an embodiment of the present invention. As shown in Figure 15, a DCI for data corresponding to a second SIB1 is used to schedule data corresponding to a second SIB1, and data corresponding to a second SIB1 includes scheduling information for a DCI corresponding to data corresponding to a first SIB1. Specifically, a second SIB1 or data corresponding to a second SIB1 can schedule a DCI corresponding to data corresponding to a first SIB1, and a DCI corresponding to data corresponding to a first SIB1 is used to schedule data corresponding to a first SIB1. A terminal device may determine the location of a PDSCH corresponding to a second SIB1 or data corresponding to a second SIB1 based on a DCI corresponding to a second SIB1 or data corresponding to a second SIB1, may determine the location of a DCI corresponding to data corresponding to a first SIB1 based on a second SIB1 or data corresponding to a second SIB1, and may determine the location of a PDSCH corresponding to data corresponding to a first SIB1 based on a DCI corresponding to data corresponding to a first SIB1. The scheduling information for the DCI corresponding to the first SIB1 may be dynamically set in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information for the DCI corresponding to the data corresponding to the first SIB1 may be statically set, or the scheduling information for the DCI corresponding to the data corresponding to the first SIB1 may be quasi-statically set. This is not limited herein. Note that for understanding that the scheduling information for the DCI corresponding to the data corresponding to the first SIB1 may be dynamically set in the second SIB1 or the data corresponding to the second SIB1, or the scheduling information for the DCI corresponding to the data corresponding to the first SIB1 may be statically set, or the scheduling information for the DCI corresponding to the data corresponding to the first SIB1 may be quasi-statically set, please refer to the above explanation in Figure 12 regarding the possibility that the scheduling information for the first data may be dynamically set in the third DCI, or that the scheduling information for the first data may be statically set, or that the scheduling information for the first data may be quasi-statically set.Further details will not be provided here.

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

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

[0324] In some feasible implementations, a network device may alternatively schedule three or more SIB1 instances. Specifically, the following describes four scheduling modes in scenarios where a network device may alternatively schedule three or more SIB1 instances.

[0325] To facilitate understanding, the data corresponding to four SIB1 versions—namely, the data corresponding to SIB1 for version N, the data corresponding to SIB1 for version N+1, the data corresponding to SIB1 for version N+2, and the data corresponding to SIB1 for version N+3—will be primarily used as examples below for explanation. Of the four SIB1 versions, the data corresponding to SIB1 for version N may be understood as the data corresponding to an earlier version of SIB1, and the data corresponding to SIB1 for versions N+1 to N+3 may be understood as the data corresponding to a later version of SIB1. For ease of description, the data corresponding to SIB1 for version N may be called SIB1 for version N, the data corresponding to SIB1 for version N+1 may be called SIB1 for version N+1, the data corresponding to SIB1 for version N+2 may be called SIB1 for version N+2, and the data corresponding to SIB1 for version N+3 may be called SIB1 for version N+3.

[0326] In the first scheduling mode, a level-based scheduling mode may be used in scenarios where a network device schedules three or more SIB1 instances. Specifically, an earlier version of SIB1 contains scheduling information for a later version of SIB1. Alternatively, this can be described as follows: Data corresponding to an earlier version of SIB1 contains scheduling information for a later version of SIB1.

[0327] The scheduling information for a later version of SIB1 may be dynamically set in the earlier version of SIB1 or the data corresponding to the earlier version of SIB1, or it may be statically set, or it may be quasi-statically set. This is not limited to the above. Note that for understanding that the scheduling information for a later version of SIB1 may be dynamically set in the earlier version of SIB1 or the data corresponding to the earlier version of SIB1, or it may be statically set, or it may be quasi-statically set, refer to the above explanation in Figure 12 that the scheduling information for the first data may be dynamically set in the 3DCI, or the scheduling information for the first data may be statically set, or the scheduling information for the first data may be quasi-statically set. Further details are not provided here.

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

[0329] Optionally, in the second scheduling mode, level cross-scheduling mode may be used in scenarios where a network device schedules three or more SIB1s. For example, an earlier version of SIB1 may contain scheduling information for one or more later versions of SIB1, or data corresponding to an earlier version of SIB1 may contain scheduling information for one or more later versions of SIB1.

[0330] The scheduling information for one or more subsequent versions of SIB1 may be dynamically set in the preceding version of SIB1 or the data corresponding to the preceding version of SIB1, or the scheduling information for one or more subsequent versions of SIB1 may be statically set, or the scheduling information for one or more subsequent versions of SIB1 may be quasi-statically set. This is not limited herein. Note that for understanding that the scheduling information for one or more subsequent versions of SIB1 may be dynamically set in the preceding version of SIB1 or the data corresponding to the preceding version of SIB1, or the scheduling information for subsequent versions of SIB1 may be statically set, or the scheduling information for subsequent versions of SIB1 may be quasi-statically set, refer to the above explanation in Figure 12 regarding the possibility that the scheduling information for the first data may be dynamically set in the third DCI, or the scheduling information for the first data may be statically set, or the scheduling information for the first data may be quasi-statically set. Further details are not provided here. Optionally, the version of the subsequent version of SIB1 may be further indicated in the base version of SIB1.

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

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

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

[0334] Optionally, in the fourth scheduling mode, the hybrid scheduling mode may be used as an alternative in scenarios where a network device schedules three or more SIB1s. For example, one DCI may contain scheduling information for multiple versions of SIB1 (e.g., earlier versions and / or several later versions), and the earlier version of SIB1 or the data corresponding to the earlier version of SIB1 does not need to contain scheduling information for any later versions of SIB1, while the later version of SIB1 scheduled by the DCI, or the data corresponding to the later version of SIB1, may contain scheduling information for even later versions of SIB1.

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

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

[0337] In the examples shown in Figures 16 to 21, version N of SIB1 can be understood as the base version of SIB1, while other SIB1 versions, such as versions N+1 to N+3, are considered later versions of SIB1.

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

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

[0340] S1103a: The terminal device determines the resource information of the 4th DCI and / or the resource information of the 2nd data based on the 3rd DCI.

[0341] In some feasible implementations, the terminal device may determine the resource information of the 4th DCI and / or the resource information of the 2nd data based on the 3rd DCI. Note that step S1103a may also be an optional step.

[0342] S1103b: The terminal device receives the 4th DCI based on the 3rd DCI.

[0343] In some feasible implementations, the terminal device may receive the 4th DCI based on the 3rd DCI. Note that step S1103b may also be an optional step.

[0344] S1103c: The terminal device determines the resource information for the first data based on the 4th DCI.

[0345] In some feasible implementations, the terminal device may determine the resource information for the first data based on the 4th 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 feasible implementations, one possible understanding of how a terminal device receives first and / or second data from a network device is as follows: The terminal device receives first and / or second data from the network device based on the third DCI. Another possible understanding is as follows: The terminal device receives second data from the network device based on the third DCI, and / or the terminal device receives first data from the network device based on the fourth DCI.

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

[0349] Specifically, regarding decoding by a 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 the data scheduled by the 3rd DCI. If the 3rd DCI is used to schedule at least two data (e.g., the first data and the 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 data corresponding to the second SIB1 in Figure 12, in accordance with the implementation shown in Figure 12 in step S1101. If the 3rd DCI is used to schedule the second data and the 4th 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 data corresponding to the second SIB1 in Figure 13, in accordance with the implementation shown in Figure 13 in step S1101.

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

[0351] Furthermore, in the case where the terminal device determines, based on the first data, that the first data includes the first SIB1, and / or, based on the second data, that the second data includes the second SIB1, please note that the above explanation of the terminal device determining, based on the first data, that the first data includes the first SIB1 can be referenced in step S904 of Figure 9. Details are not described again here.

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

[0353] Note that for a description of the fourth instruction information in this embodiment of the present application, please refer to the description of the fourth instruction information in step S905 of Figure 9. Details are not described again here. Note that the fourth instruction information may be carried in an MIB transmitted to the terminal device by the m network device, or the fourth instruction information may be carried in the third DCI. This is not limited here. For example, the terminal device may acquire the fourth instruction information and, based on the fourth instruction information, decide whether the third DCI will schedule the first data and the second data. Furthermore, the terminal device may receive the first data. For example, the terminal device may acquire the fourth instruction information and, based on the fourth instruction information, decide whether the third DCI will schedule 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 steps S1101 and S1102 above may be considered as independent embodiments, or as optional steps, they may be combined with one or more steps in this embodiment of the present application. This is not limited herein. Steps S1101 and S1103a to S1103c, steps S1101 and S1103a and S1103b, or steps S1101 and S1103a above may be considered as independent embodiments, or as optional steps, they may be combined with one or more steps in this embodiment of the present application. This is not limited herein. Steps S1104 and S1105 above may be considered as independent embodiments, or as optional steps, they may be combined with one or more steps in this embodiment of the present application. This is not limited herein. Step S1106 above may be considered as an independent embodiment, or as optional steps, they may be combined with one or more steps in this embodiment of the present application. This is not limited herein. 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 determined specifically based on the actual application scenario and is not limited herein. For example, S1105 may be executed before or after S1103b. This is not limited to this case.

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

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

[0357] S2201: The terminal device receives the 6th downlink control information DCI from the network device.

[0358] In several feasible implementations, the 6th DCI is received from a network device and used to schedule the 4th data, which includes a set of SIB1. The set of SIB1 includes at least one SIB1. At least one SIB1 may include SIB1 associated with different versions or different operating modes. Specifically, different SIB1s may be mapped to a single set of SIB1s, which are then scheduled by a single DCI. For example, at least one SIB1 may include a first SIB1. As another example, the set of SIB1s may include a first SIB1 and a second SIB1. Note that for an understanding of the first SIB1 and the second SIB1, refer to the description of the first SIB1 and the second SIB1 in Figure 9 in this embodiment of the present application. Further details are not described here again.

[0359] Note that in possible implementations, a set of SIB1 or at least one SIB1 may include the base version of SIB1. This is not limited herein. In possible implementations, a set of SIB1 or at least one SIB1 may include one or more subsequent versions of SIB1. This is not limited herein.

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

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

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

[0363] Step S2202 may be understood as being performed at the PHY layer or MAC layer of the terminal device, or it may be performed at other layers (e.g., other newly defined layers). This will be specifically determined based on the actual application scenario and is not limited thereto. Note that step S2202 is an optional step. Note that for the terminal device, determining whether the 6th DCI contains an SIB1 set, or whether the 6th DCI schedules an SIB1 set or an SI message, may be performed according to the solution in Figure 9 (e.g., any one of implementations 1 to 5 in step S902 of Figure 9). Specifically, in the five implementations in Figure 9, determining that the first data contains a first SIB1 based on the first DCI can be replaced in this embodiment, for the sake of understanding, by determining that the fourth data contains an SIB1 set based on the 6th DCI. Further details are not described here again.

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

[0365] Step S2203 may be understood as being performed at the PHY layer or MAC layer of the terminal device, or it may be performed at other layers (e.g., other newly defined layers). This will be specifically determined based on the actual application scenario and is not limited thereto. 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. Note 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 several feasible implementations, a terminal device (e.g., the terminal device's PHY layer, MAC layer, or other layer) receives the fourth data from a network device based on the sixth DCI, and after distributing all or part of the fourth data to a higher layer of the terminal device (e.g., the terminal device's RRC layer or other layer; for ease of description, the terminal device's RRC layer is used below as an example), the terminal device's RRC layer may further decode the content contained in the fourth data or the content corresponding to the fourth data based on the fourth data. Based on this, the terminal device's RRC layer may determine, based on the fourth data, that the fourth data contains an SIB1 set. Note that any one of implementations (1) to (3) in step S904 of Figure 9 may be referenced for an implementation in which the terminal device determines, based on the fourth data, that the fourth data contains an SIB1 set. Specifically, in the three implementations of Figure 9, determining that the first data includes the first SIB1 based on the first data may, for the sake of understanding, be replaced in this embodiment by determining that the fourth data includes the SIB1 set based on the fourth data. Further details are not described here again. Note that step S2204 may be an optional step.

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

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

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

[0371] In the first implementation, the fourth data, fourth message, or SIB1 set may include sixth directive information, the sixth directive information indicating a specific SIB1 or a group of specific SIB1s included in the fourth data, fourth message, or SIB1 set.

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

[0373] The specific form of instruction provided by the sixth instruction information may include, but is not limited to, one of the following forms:

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

[0375] Format 2: If the SIB1 set may contain up to three or more SIB1s, the sixth instruction information may be in the form of a bitmap, where one SIB1 corresponds to one bit, and each bit indicates whether a corresponding SIB1 exists. Optionally, when the instruction is in the form of a bitmap, to conserve bits, the base version of SIB1 does not need to be indicated and is assumed to exist by default. Specifically, the bitmap only needs to indicate multiple subsequent versions of SIB1. For example, suppose the SIB1 set contains four versions of SIB1: version N, version N+1, version N+2, and version N+3. Version N is the base version of SIB1, and versions N+1 through N+3 are multiple subsequent versions of SIB1. Therefore, the bitmap length is 4 bits, corresponding sequentially from left to right to version N of SIB1, version N+1 of SIB1, version N+2 of SIB1, and version N+3 of SIB1. Assuming that 0 indicates that SIB1 does not exist and 1 indicates that SIB1 exists, the bitmap can be represented as 1111. Optionally, to save bits, the bit length may be 3 bits, and the base version of SIB1 does not need to be indicated alternatively. Specifically, the base version of SIB1 is assumed to exist explicitly by default. In this case, the bitmap can be represented as 111.

[0376] Format 3: If a set of SIB1 contains more than one SIB1, to save bits, the sixth instruction information may alternatively be information indicating the presence of the latest version of SIB1. Specifically, it is assumed by default that the network should transmit all previous versions of SIB1 prior to the latest version. For example, the sixth instruction information occupies 4 bits, where 0000 represents version R15 of SIB1, 0001 represents version R16 of SIB1, and so on. Assuming the sixth instruction information is 0001, it is determined that the set of SIB1 contains version R16 of SIB1 and all versions of SIB1 prior to version R16.

[0377] In the second implementation, the terminal device obtains the seventh instruction information related to the fourth message.

[0378] The statement "the terminal device obtains the seventh instruction information related to the fourth message" can be understood as follows: the terminal device's RRC layer obtains the seventh instruction information related to the fourth message from the terminal device's lowest layer.

[0379] The seventh instruction information indicates the fourth data, the fourth message, or an SIB1 included in the SIB1 set, or a specific SIB1 or multiple specific SIB1s. Based on the seventh instruction information, the terminal device determines the fourth data, the fourth message, or an SIB1 included in the SIB1 set.

[0380] The “lowest layer of the terminal device” may include any one of the following: the terminal device’s PHY layer, the terminal device’s MAC layer, the terminal device’s RLC layer, or the terminal device’s PDCP layer. Here, the lowest layer of the terminal device may, layer by layer, deliver the seventh instruction information to the RRC layer, or deliver the seventh instruction information to the RRC layer through one or more layers between the lowest layer of the terminal device and the terminal device’s RRC layer, or the terminal device may deliver the seventh instruction information directly to the terminal device’s RRC layer.

[0381] It can be understood that the RRC layer of a terminal device not only acquires the fourth message but also acquires seventh instruction information associated with the fourth message. Based on the seventh instruction information, the RRC layer of the terminal device may determine the fourth data, the fourth message, or a specific SIB1 or a set of specific SIB1s included in the SIB1 set. It should be noted that the implementation of acquiring the fourth message by the terminal device's RRC layer may be the same as or different from the implementation of acquiring the seventh instruction information by the terminal device's RRC layer. This is not limited to the present invention.

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

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

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

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

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

[0387] It should be noted that the reception of the 8th instruction information by a terminal device from a network device can be understood as follows: the terminal device receives an MIB from the network device, and the MIB contains the 8th instruction information. In other words, the 8th instruction information may be carried in the MIB. Alternatively, the 8th instruction information may be carried in the 6th DCI for scheduling the SIB1 set. Alternatively, the 8th instruction information may be carried in the DCI for scheduling the SI message. Specifically, the terminal device determines whether the SIB1 set exists on the network device or should be transmitted by the network device based on the 8th instruction information in the MIB, the 8th instruction information in the 6th DCI for scheduling the SIB1 set, or the 8th instruction information in the DCI for scheduling the SI message. In possible terminal implementations, the terminal device may interpret the fields 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 steps S2201 and S2202 above may be considered as independent embodiments, or may be combined with one or more steps in this embodiment of the present application as optional steps. This is not limited herein. Steps S2203, S2204, and S2205 above, or steps S2203 and S2205 above, may be considered as independent embodiments, or may be combined with one or more steps in this embodiment of the present application as optional steps. This is not limited herein. Step S2206 above may be considered as an independent embodiment, or may be combined with one or more steps in this embodiment of the present application as optional steps. This is not limited herein. Note that the numbering order 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 determined specifically based on the actual application scenario and is not limited herein. For example, S2206 may be executed before or after S2201. This is not limited herein.

[0389] In this embodiment of the present application, different SIB1s are mapped to a single set of SIB1s, and the set of SIB1s is scheduled by a single DCI. This ensures that a terminal device can obtain a first SIB1 or a basic version of SIB1, that a terminal device can access the network based on the first SIB1 or a basic version of SIB1, and that a basic communication channel is secured 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 SIB1s and the DCI used to schedule SI messages are distinguished based on instruction information in the DCI, scrambling information in the DCI, the DCI format, time-domain resources for the DCI, or frequency-domain resources for the DCI. In this way, the terminal device can accurately identify the content scheduled by the DCI and correctly execute HARQ combinations to improve the reliability of data reception. For the RRC layer of the terminal device, the terminal device can correctly identify the content contained in the fourth message based on instruction information, inter-layer interactions, or logical channels in the fourth message. Furthermore, regarding the RRC layer of a terminal device, the terminal device can correctly perform RRC decoding to obtain the correct information by accurately identifying a specific SIB1 or multiple specific SIB1s included in the SIB1 set within the fourth message based on the sixth instruction information within the fourth message or the seventh instruction information related to the fourth message. In addition, whether a network device should transmit the fourth data is indicated in the eighth instruction information within the MIB, the DCI for scheduling the fourth data, or the DCI for scheduling the third data. This also helps the terminal device to correctly receive and decode the SIB1 set, improves reception reliability, and saves energy.

[0390] It should be noted that this application further includes the following embodiments in addition to the solutions described in Figures 9, 11, and 22. It should also be noted that the following embodiments may be carried out in combination with some of the steps in the embodiments described above, or independently.

[0391] Optionally, in a feasible implementation, an earlier version of a terminal device may access a network device by using SIB1 associated with the basic version or secure mode, but the network device may modify SIB1 or other SIBs associated with a later version or normal mode. The earlier version of a terminal device does not require SIB1 or other SIBs associated with a later version or normal mode. Therefore, in order to avoid the impact of changes to SIs associated with a later version or normal mode (e.g., SIB1 associated with a later version or normal mode, and / or other SIBs associated with a later version or normal mode) on an earlier version of a terminal device, ninth instruction information may be included in the DCI or short message to notify of SI changes, and the ninth instruction information may indicate whether the SI change relates to an SI associated with the basic version or secure mode (e.g., SIB1 associated with a basic version or secure mode, and / or other SIBs associated with a basic version or secure mode), or whether the SI change relates only to an SI associated with a later version or normal mode. The length of the ninth instruction information may be 1 bit, for example. This will be specifically determined based on the actual application scenario and is not limited herein. Since the ninth instruction information is transmitted to the terminal device, it is easy to understand that energy can be saved for the terminal device.

[0392] It should be noted that during implementation, if a terminal device cannot access a network device in normal mode, the terminal device will normally attempt to access the network device in secure mode. However, there may be abnormal cases where a terminal device cannot access a network device in secure mode. In this case, the terminal device may abandon access in secure mode based on the maximum attempt time or maximum number of attempts. Specifically, a maximum attempt time or maximum number of attempts may be set, and if the time or number of attempts to access in secure mode exceeds the pre-set maximum attempt time or maximum number of attempts, the terminal device will abandon access in secure mode. This will save energy on the terminal device.

[0393] Note that, for terminal devices accessing network devices in secure mode, when configuring the terminal device, the network device needs to send parameters related to secure mode, such as the settings of a previous version. Note that the terminal device may receive information from the serving cell, which may indicate whether a nearby cell can assist the terminal device in accessing the network device in secure mode. For terminal devices accessing network devices in secure mode, during cell reselection, cells that can assist the terminal device in accessing the network device in 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 of this application or some steps in different embodiments may be combined with each other to form a new embodiment. Furthermore, unless otherwise specified or a logical contradiction arises, the terminology and / or descriptions in different embodiments are consistent and can be referenced to one another.

[0395] The communication device provided in this application is described below with reference to Figures 25 to 28.

[0396] Figure 25 is a diagram of the structure of a communication device according to an embodiment of the present invention. The communication device shown in Figure 25 may be configured to perform some or all of the functions of a terminal device in embodiments of the methods described in Figures 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 Figure 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 called a communication unit. Alternatively, the transceiver unit 2501 may be divided into a receiving unit and a transmitting unit. The descriptions of the processing unit 2502 and the transceiver unit 2501 are similar below. Details are not 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 is used to schedule first data, and the processing unit 2502 is configured to determine, based on the first DCI, that the first data includes first system information block 1 SIB1, the first SIB1 includes information about network access in a first operating mode. The first DCI includes first instruction information, the first instruction information indicates that the first data includes first SIB1, or one or more of the following information related to 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 related to the second DCI, the second DCI is used to schedule second SIB1, the second SIB1 includes information about network access in a second operating mode.

[0398] Optionally, the first data includes the first message, and the first message includes the first SIB1. Optionally, the first message further includes second instruction information, which indicates that the first message includes the first SIB1. Optionally, the first SIB1 is associated with the first radio link control RLC entity, or the first SIB1 is associated with the first logical channel LCH. The first RLC entity is distinct from the second RLC entity, or the first LCH is distinct from the second LCH. The second RLC entity is associated with the second SIB1, and the second LCH is associated with the second SIB1.

[0399] Optionally, the transceiver unit 2501 is further configured to acquire third instruction information related to the first message, the third instruction information indicating that the first message contains a first SIB1.

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

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

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

[0403] Optionally, the 3rd DCI includes time-domain resource information and / or frequency-domain resource information for the 1st data. Optionally, the time-domain resource information for the 1st data includes the interval between the time-domain resource for the 1st data and the time-domain resource for the 2nd data, or the time-domain resource information for the 1st data includes the interval between the time-domain resource for the 1st data and the time-domain resource for the 3rd DCI, and / or The frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or the frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI. The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

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

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

[0406] Optionally, the first message may further include second directive information, which indicates that the first message contains 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, the second RLC entity is related to the second SIB1, and the second LCH is related to the second SIB1.

[0408] Optionally, the transceiver unit 2501 is further configured to acquire third instruction information related to the first message, the third instruction information indicating that the first message contains a first SIB1.

[0409] Optionally, the transceiver unit 2501 may be further configured to acquire third instruction information from the physical PHY layer or the medium access control MAC, radio link control RLC, or packet data convergence protocol PDCP layer via the radio resource control RRC layer.

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

[0411] Optionally, the 3rd DCI includes 4th instruction information, which instructs the network device to transmit the 1st SIB1.

[0412] For other possible implementations of the communication device, please refer to the relevant descriptions of the terminal device functions in the embodiments of the method corresponding to Figures 9 to 24. Further details are not provided here.

[0413] Figure 26 is a diagram illustrating the structure of another communication device according to an embodiment of the present invention. The communication device shown in Figure 26 may be configured to perform some or all of the functions of a network device in the embodiments of the methods described in Figures 9 to 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 Figure 26 may include a transceiver unit 2601 and a processing unit 2602.

[0414] In implementation, 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 first system information block 1 SIB1, the first SIB1 includes information about network access in a first operating mode, and transceiver unit 2601 is configured to transmit the first DCI to a terminal device, the first DCI includes first instruction information, the first instruction information indicates that the first data includes the first SIB1, or one or more of the following information related to 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 related to the second DCI, the second DCI is used to schedule second SIB1, the second SIB1 includes information about network access in a second operating mode.

[0415] Optionally, the first data includes the first message, and the first message includes the first SIB1. Optionally, the first message further includes second instruction information, which indicates that the first message includes the first SIB1.

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

[0417] In other implementations, the transceiver unit 2601 is configured to transmit a third downlink control information DCI to a terminal device, the third DCI being used to schedule at least two data, or the third DCI being used to schedule a second data and a fourth DCI, the fourth DCI being used to schedule a first data, and the transceiver unit 2601 is configured to transmit the first data and the second data to a terminal device, the at least two data including the first data and the second data, the first data including a first system information block 1 SIB1, the second data including a second SIB1, the first SIB1 including information about network access in a first operating mode, and the second SIB1 including information about network access in a second operating mode.

[0418] Optionally, the 3rd DCI includes time-domain resource information and / or frequency-domain resource information for the 1st data. Optionally, the time-domain resource information for the 1st data includes the interval between the time-domain resource for the 1st data and the time-domain resource for the 2nd data, or the time-domain resource information for the 1st data includes the interval between the time-domain resource for the 1st data and the time-domain resource for the 3rd DCI, and / or The frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the second data, or the frequency domain resource information for the first data includes the interval between the frequency domain resource for the first data and the frequency domain resource for the third DCI. The interval between time-domain resources is used to determine the time-domain resources for the first data, and the interval between frequency-domain resources is used to determine the frequency-domain resources for the first data.

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

[0420] Optionally, the first data includes the first message, and the first message includes the first SIB1. Optionally, the first message includes second instruction information, and the second instruction information indicates that the first message includes the first SIB1.

[0421] Optionally, the transceiver unit 2601 is further configured to transmit a master information block (MIB) to a terminal device, the MIB containing a fourth instruction information which instructs the network device to transmit a first SIB1.

[0422] Optionally, the third DCI includes fourth instruction information, which instructs the network device to transmit the first SIB1. For other possible implementations of the communication device, see the relevant descriptions of the network device functions in the embodiments of the method corresponding to Figures 9 to 24. Further details are not provided here.

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

[0424] For example, terminal device 2700 is a mobile phone. After terminal device 2700 is powered on, the processor may read the software program in the memory unit, interpret and execute the instructions of the software program, and process the data of the software program. If the 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 in the form of electromagnetic waves via the antenna. When data is to be transmitted to terminal device 2700, the control circuit receives the radio frequency signal via the antenna, converts the radio frequency signal into a baseband signal, outputs the baseband signal to the processor, the processor converts the baseband signal into data, and processes the data.

[0425] Those skilled in the art will understand that, for the sake of ease of description, Figure 27 shows only one memory and one processor. In some embodiments, the terminal device 2700 may include multiple processors and memories. Memory may also be called a storage medium, storage device, etc. This is not limited to 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 for the software programs. The processor in Figure 27 incorporates the functions of a baseband processor and a central processing unit. Those skilled in the art will understand that the baseband processor and the central processing unit may alternatively be independent processors interconnected by technologies such as buses. The terminal device 2700 may include multiple baseband processors to adapt to different network standards. The terminal device 2700 may include multiple processing units to enhance the processing capabilities 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 baseband processing chip. The central processing unit may also be referred to as a central processing circuit or central processing chip. The functions for processing communication protocols and communication data may be built within the processor or stored in a memory unit in the form of a software program, and the processor executes the software program to implement the baseband processing functions.

[0427] In this example, the antenna and control circuit with transceiver functionality may be considered as the transceiver unit 2710 of the terminal device 2700, and the processor with processing functionality may be considered as the processing unit 2720 of the terminal device 2700. As shown in Figure 27, the terminal device 2700 includes the transceiver unit 2710 and the processing unit 2720. The transceiver unit may also be called a transceiver, transceiver device, transceiver unit, etc. Optionally, a component within the transceiver unit 2710 configured to implement receiving functionality may be considered a receiving unit, and a component within the transceiver unit 2710 configured to implement 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 called a receiving device, receiver, receiving circuit, etc., and the transmitting unit may also be called a transmitting device, transmitter, transmitting circuit, etc.

[0428] Figure 28 is a diagram of the structure of another communication device according to an embodiment of the present application. As shown in Figure 28, the communication device may be a network device described in an embodiment of the present application and is configured to implement the functions of the network device in Figures 9 to 24. The network device 28 includes a baseband device 281, a radio frequency device 282, and an antenna 283. In the uplink direction, the radio frequency device 282 receives information transmitted by a terminal device through the antenna 283 and transmits the information transmitted by the terminal device to the baseband device 281 for processing. In the downlink direction, the baseband device 281 processes information for the terminal device and transmits the processed information to the radio frequency device 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 help the network device perform the functions of the network device in the embodiment of the method described above. 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, e.g., one or more ASICs, one or more DSPs, one or more FPGAs, or a combination thereof. These integrated circuits may be integrated together to form a chip. The storage unit 2812 and the processing unit 2811 may reside on a single 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 reside on different chips. In other words, the storage unit 2812 is an off-chip storage element. The memory unit 2812 may be a single memory, or it may be a collective term for multiple memories or memory elements.

[0430] The network device may be programmed by one or more processing units to implement some or all of the steps in the embodiments of the above method, for example, by implementing the corresponding functions of the network device in Figures 9 to 24. One or more processing units may support the same standard wireless access technology, or they may support different standard wireless access technologies.

[0431] Embodiments of the present invention further provide a computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions are executed by a processor, the method process in the above embodiment of the method is carried out.

[0432] Embodiments of the present invention further provide a computer program product. When the computer program product is executed on a processor, the method process in the above embodiment of the method is carried out.

[0433] Those skilled in the art will notice, in combination with the examples described in the embodiments disclosed herein, that the units and steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the function is performed 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 implementation should not be considered to be beyond the scope of this application.

[0434] It should be understood that in some embodiments provided herein, the disclosed systems, apparatus, and methods may be carried out in other ways. For example, the embodiments of the apparatus described above are merely examples. For example, 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., they may be located in one place or distributed across multiple units. Some or all units may be selected in accordance with the practical requirements to achieve the objectives of the solutions of the embodiments.

[0435] If the function is implemented in the form of a software function unit and sold or used as a standalone product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solution of the present application, or parts of the technical solution that contribute to the prior art, may be implemented in the form of a software product. The computer software product is stored on a storage medium and contains several instructions that instruct a computer device (which may be a personal computer, server, network device, etc.) to perform all or part 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 to the 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 media that can carry or store expected program code in the form of instructions or data structures and that can be accessed by a computer.Furthermore, as an example, rather than being a restrictive description, 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 merely illustrates 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 modification or substitution that a person skilled in the art could easily conceive 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. Accordingly, the scope of protection of the embodiments of the present application should be subject to the scope of protection of the claims.

[0437] This application is a divisional application from Japanese Patent Application No. 2024-531296, which claims priority to Chinese Patent Application No. 202111418043.8, filed with the China National Intellectual Property Administration on November 25, 2021, with the title of the invention being "COMMUNICATION METHOD AND COMMUNICATION APPARATUS," and which references the entire text of the earlier Chinese Patent Application in this application.

Claims

1. A communication method applicable to terminal devices, Receiving first downlink control information (DCI) from a network device, which is used to schedule the first data, Based on the first DCI, it is determined that the first system information block 1 (SIB1) contains the first data. It has, The first DCI includes first instruction information, which indicates that the first data includes the first SIB1, or one or more pieces of information associated with the first DCI, such as scrambling information, downlink control information (DCI) format information, time-domain resource information, or frequency-domain resource information, are different from those associated with the second DCI, the second DCI is used to schedule the second data, and the second data includes the second SIB1. method.

2. The first data includes a first message, and the first message includes the first SIB1. The method according to claim 1.

3. The first message further includes second instruction information, which indicates that the first message includes the first SIB1. The method according to 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, the second RLC entity is related to the second SIB1, and the second LCH is related to the second SIB1, The method according to claim 2.

5. The method further comprises obtaining third instruction information related to the first message, The third instruction information indicates that the first message includes the first SIB1. The method according to claim 2.

6. Obtaining the third instruction information related to the first message mentioned above is: The Radio Resource Control (RRC) layer of the terminal device obtains the third instruction information from the physical (PHY) layer of the terminal device, or from the medium access control (MAC) layer, radio link control (RLC) layer, or packet data convergence protocol (PDCP) layer of the terminal device. The method according to claim 5.

7. The method further comprises receiving a fourth instruction information from the network device that instructs the network device to transmit the first SIB1, The fourth instruction information is carried by the Master Information Block (MIB) or the second DCI. The method according to claim 1.

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

9. The first SIB1 includes information regarding network access in the first operating mode, or The second SIB1 includes information regarding network access in the second operating mode, The method according to claim 1.

10. A communication method applicable to network devices, The first data is to determine the first downlink control information (DCI) used to schedule the first data, wherein the first data includes the first system information block 1 (SIB1), The first DCI is transmitted to the terminal device. It has, The first DCI includes first instruction information, which indicates that the first data includes the first SIB1, or one or more pieces of information associated with the first DCI, such as scrambling information, downlink control information (DCI) format information, time-domain resource information, or frequency-domain resource information, are different from those associated with the second DCI, and the second DCI is used to schedule the second SIB1. method.

11. The first SIB1 includes information regarding network access in the first operating mode, or The second SIB1 includes information regarding network access in the second operating mode, The method according to claim 10.

12. The first data includes a first message, and the first message includes the first SIB1. The method according to claim 10.

13. The first message further includes second instruction information, which indicates that the first message includes the first SIB1. The method according to claim 12.

14. The method further comprises sending a fourth instruction information to the terminal device instructing the network device to transmit the first SIB1, The fourth instruction information, the master information block (MIB), or the second DCI are carried by The method according to claim 10.

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

16. A communication device, The aforementioned communication device is a terminal device and has a processor and a transceiver. The processor and the transceiver are configured to execute a computer program or instruction stored in at least one memory, enabling the communication device to carry out the method according to any one of claims 1 to 9. Communication device.

17. A communication device, The aforementioned communication device is a network device and has a processor and a transceiver. The processor and the transceiver are configured to execute a computer program or instruction stored in at least one memory, enabling the communication device to carry out the method according to any one of claims 10 to 15. Communication device.

18. Stores computer programs or instructions, When the computer program or instruction is executed by a computer, the method described in any one of claims 1 to 9 is carried out. Computer-readable storage medium.

19. Stores computer programs or instructions, When the computer program or instruction is executed by a computer, the method described in any one of claims 10 to 15 is carried out. Computer-readable storage medium.

Images