System information transmission method and apparatus

Abstract

The embodiment of the disclosure discloses a system information transmission method and device, the method is executed by a network side device, and the method comprises the following steps: transmitting requested system information (SI) on a first initial downlink bandwidth part or a second initial downlink bandwidth part corresponding to configuration of a system information (SI) request message sent by a terminal according to the received configuration. Therefore, when the first type terminal and the second type terminal reside in the first initial downlink bandwidth part at the same time, and the on-demand SI is transmitted on the first initial downlink bandwidth part, the first type terminal and the second type terminal can both be monitored, avoiding transmission on two initial downlink bandwidth parts respectively, and the transmission efficiency of the network side device can be improved. Moreover, when the first type terminal resides in the second initial downlink bandwidth part, the on-demand SI is transmitted on the second initial bandwidth part, avoiding the first type terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink bandwidth part, and the power consumption of the first type terminal can be saved.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a system information transmission method and apparatus. Background Technology

[0002] In the current 3GPP (Third Generation Partnership Project) standardization, a new type of terminal has been proposed called Reduced Capability UE (user equipment), or simply NR. Lite or Redcap terminals are also known as capability-reduced UEs in some scenarios.

[0003] With the introduction of Redcap terminals into NR (new radio) systems, each Redcap terminal will be configured with a separate initial DL BWP (initial downlink bandwidth part initial) and a separate initial UL BWP (initial uplink bandwidth part initial). However, the network-side equipment originally already had one initial DL BWP and one initial UL BWP. This will result in the network-side equipment having multiple initial DL BWPs and multiple initial UL BWPs. At this point, how to perform on-demand SI (system information) transmission is an urgent problem to be solved. Summary of the Invention

[0004] This disclosure provides a system information transmission method and apparatus to achieve on-demand SI transmission.

[0005] In a first aspect, embodiments of this disclosure provide a system information transmission method, which is executed by a network-side device. The method includes: transmitting the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the configuration of a received system information SI request message sent by a terminal.

[0006] In this technical solution, based on the configuration corresponding to the system information (SI) request message sent by the received terminal, the requested SI is sent on either the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the configuration. Therefore, when both the first type of terminal and the second type of terminal reside simultaneously on the first initial downlink bandwidth portion, and the on-demand SI is transmitted on the first initial downlink bandwidth portion, both types of terminals can detect it, avoiding separate transmissions on the two initial downlink bandwidth portions and improving the transmission efficiency of the network-side equipment. Conversely, when the first type of terminal resides on the second initial downlink bandwidth portion, the on-demand SI is transmitted on the second initial downlink bandwidth portion, avoiding the first type of terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first type of terminal.

[0007] Secondly, this disclosure provides another system information transmission method, which is executed by a first type of terminal. The method includes: sending a system information (SI) request message, and receiving the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the configuration, according to the configuration corresponding to the SI request message.

[0008] Thirdly, embodiments of this disclosure provide a system information transmission device. This system information transmission device has some or all of the functions of the network-side device in the method example described in the first aspect above. For example, the system information transmission device may have some or all of the functions in the embodiments of this disclosure, or it may have the functions of implementing any one embodiment of this disclosure individually. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0009] In one implementation, the system information transmission device may include a transceiver module for supporting communication between the system information transmission device and other devices. The system information transmission device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the system information transmission device.

[0010] In one implementation, the system information transmission device includes a transceiver module, configured to transmit the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the configuration corresponding to the received system information SI request message sent by the terminal.

[0011] Fourthly, embodiments of this disclosure provide a system information transmission device. This communication device has some or all of the functions of the terminal device described in the second aspect above. For example, the communication device may have some or all of the functions in the embodiments of this disclosure, or it may have the functions of any one embodiment of this disclosure implemented individually. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0012] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0013] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0014] In one implementation, the system information transmission device includes: a transceiver module, configured to send a system information (SI) request message, and receive the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the configuration, based on the configuration corresponding to the SI request message.

[0015] Fifthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0016] In a sixth aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0017] In a seventh aspect, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0018] Eighthly, embodiments of this disclosure provide a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0019] Ninthly, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0020] In a tenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0021] Eleventhly, embodiments of this disclosure provide a system information transmission system, which includes the system information transmission device described in the third aspect and the system information transmission device described in the fourth aspect; or, the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect; or, the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect; or, the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0022] In a twelfth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0023] In a thirteenth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the network device described above, which, when executed, cause the network device to perform the method described in the second aspect above.

[0024] In a fourteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0025] In a fifteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0026] In a sixteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0027] In a seventeenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting network devices in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0028] In an eighteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0029] In a nineteenth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0031] Figure 1 This is an architecture diagram of a communication system provided in an embodiment of this disclosure; Figure 2 This is a flowchart of a system information transmission method provided in an embodiment of this disclosure; Figure 3 This is a flowchart of another system information transmission method provided in this embodiment of the disclosure; Figure 4 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 5 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 6 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 7 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 8 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 9 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 10 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 11 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 12 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 13 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 14 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 15 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 16 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 17 This is a flowchart of yet another system information transmission method provided in this disclosure embodiment; Figure 18 This is a structural diagram of a system information transmission device provided in an embodiment of this disclosure; Figure 19 This is a structural diagram of a communication device provided in an embodiment of this disclosure; Figure 20 This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0032] To better understand the system information transmission method disclosed in this disclosure, the communication system to which this disclosure applies will be described below.

[0033] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system 10 provided in an embodiment of this disclosure. The communication system 10 may include, but is not limited to, a network-side device and a terminal. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, there may be two or more network-side devices and two or more terminals. Figure 1 The communication system 10 shown is exemplified by including a network-side device 101 and a terminal 102.

[0034] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, long term evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0035] The network-side device 101 in this disclosure is an entity on the network side used for transmitting or receiving signals. For example, the network-side device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of this disclosure do not limit the specific technology or device form used in the network-side device. The network-side device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure, the protocol layer of the network-side device, such as a base station, can be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0036] In this disclosure, terminal 102 is a user-side entity used to receive or transmit signals, such as a mobile phone. A terminal can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. A terminal can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, and so on. This disclosure does not limit the specific technology or device form used in the terminal.

[0037] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0038] In LTE 4G systems, two major technologies were proposed to support IoT services: MTC (machine type communication) and NB-IoT (narrow band internet of things). These two technologies are mainly aimed at scenarios with low data rates and high latency, such as meter reading and environmental monitoring.

[0039] Currently, NB-IoT can only support speeds of a few hundred kilobytes per second (Mbps), while MTC can only support speeds of a few megabytes per second (Mbps). However, with the continuous development of IoT services, such as video surveillance, smart homes, wearable devices, and industrial sensing, these services typically require speeds of tens to 100 megabytes per second (Mbps) and have relatively high latency requirements, which LTE's MTC and NB-IoT technologies struggle to meet. Therefore, a new type of terminal needs to be designed in 5G NR (New Radio) to cover these mid-range IoT devices. In the current 3GPP (3rd Generation Partnership Project) standardization, this new terminal type is called a Reduced Cap (RedCap) terminal or simply RedCap. Furthermore, similar to IoT devices in LTE, RedCap in 5G systems typically needs to meet the following requirements: low cost, low complexity, a certain degree of coverage enhancement, and power savings.

[0040] However, current NR (New Radio) is designed for high-end terminals with high speed and low latency, and the current design cannot meet the requirements of RedCap. Therefore, the current NR system needs to be modified to meet the requirements of RedCap. For example, to meet the requirements of low cost and low complexity, the RF (radio frequency) bandwidth of NR-IoT can be limited, such as to 5 MHz or 10 MHz, or the size of the RedCap buffer can be limited, thereby limiting the size of each received transmission block, etc. For power saving, possible optimization directions are to simplify the communication process and reduce the number of times the RedCap terminal detects the downlink control channel.

[0041] In related technologies, the transmission of on-demand SI in NR systems involves some system information that can be set to broadcast or non-broadcast mode. The non-broadcast system information is referred to as on-demand SI. Related technologies offer two application methods for on-demand SI: Method 1: Network devices will be configured with dedicated PRACH (physical random access channel) resources, and the terminal will send a specific check-in code preamble to obtain the required system information.

[0042] Method 2: The network-side device does not configure dedicated PRACH resources, and the terminal sends an on-demand SI request in the third message (Msg3).

[0043] However, with the introduction of Redcap terminals into the NR system, each Redcap terminal is configured with a separate initial DLBWP and a separate initial UL BWP. Meanwhile, the network-side devices already have one initial DL BWP and one initial UL BWP. This results in the network-side devices having multiple initial DL BWPs and multiple initial ULBWPs. At this point, how to perform on-demand SI (system information) transmission is an urgent problem to be solved.

[0044] Based on this, this disclosure provides a system information transmission method to at least solve the technical problem in the related art where a separate initial DL / UL BWP is configured for the Redcap terminal, and multiple initial DL / UL BWPs exist in the network-side device, making it impossible to perform on-demand SI transmission.

[0045] The system information transmission method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0046] Please see Figure 2 , Figure 2 This is a flowchart of a system information transmission method provided in an embodiment of this disclosure.

[0047] like Figure 2 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S21: Based on the configuration corresponding to the system information (SI) request message sent by the terminal, send the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the configuration.

[0048] In some possible implementations, the terminal includes a first type of terminal and a second type of terminal; the first type of terminal can be a Redcap terminal, and the second type of terminal can be a regular terminal. The terminal capabilities of the first type of terminal are different from those of the second type of terminal.

[0049] The first initial downlink bandwidth portion can be used by both Type 1 and Type 2 terminals, while the second initial downlink bandwidth portion can only be used by Type 1 terminals.

[0050] In this embodiment of the disclosure, the configuration corresponding to the SI request message sent by the first type of terminal is different from the configuration corresponding to the SI request message sent by the second type of terminal. Therefore, the network-side device can determine the type of terminal that sent the SI request message based on the configuration corresponding to the received SI request message, and determine whether the requested SI should be sent on the first initial downlink bandwidth portion or on the second initial downlink bandwidth portion. Thus, the network-side device can send the requested SI on the corresponding first initial downlink bandwidth portion or second initial downlink bandwidth portion based on the type of terminal and the result of determining whether the requested SI should be sent on the first initial downlink bandwidth portion or the result of determining whether the requested SI should be sent on the second initial downlink bandwidth portion.

[0051] In an exemplary embodiment, when the network-side device determines that the terminal type is a first type terminal based on the configuration corresponding to the SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth portion, the network-side device sends the requested SI to the first type terminal on the first initial downlink bandwidth portion.

[0052] In another exemplary embodiment, when the network-side device determines that the terminal type is a first type terminal based on the configuration corresponding to the SI request message sent by the terminal, and determines that the requested SI should be sent on the second initial downlink bandwidth portion, the network-side device sends the requested SI to the first type terminal on the second initial downlink bandwidth portion. Thus, when it is determined that the requested SI should be sent on the second initial downlink bandwidth portion, the network-side device sends the requested SI on the second initial downlink bandwidth portion, eliminating the need for the network-side device to transmit the requested SI separately on the first and second initial downlink bandwidth portions, thereby improving the transmission efficiency of the network-side device. Furthermore, the first type terminal can reside on the second initial downlink bandwidth portion and receive the requested SI on the second initial downlink bandwidth portion, avoiding the first type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving the power consumption of the first type terminal.

[0053] In another exemplary embodiment, when the network-side device determines that the terminal type is a second type terminal based on the configuration corresponding to the SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth portion, the network-side device sends the requested SI to the second type terminal on the first initial downlink bandwidth portion.

[0054] By implementing the embodiments of this disclosure, the network-side device transmits the requested SI on either the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the configuration received from the terminal's System Information (SI) request message. Therefore, when both the first type of terminal and the second type of terminal reside simultaneously on the first initial downlink bandwidth portion, and the on-demand SI is transmitted on the first initial downlink bandwidth portion, both types of terminals can detect it, avoiding separate transmissions on the two initial downlink bandwidth portions and improving the transmission efficiency of the network-side device. Furthermore, when the first type of terminal resides on the second initial downlink bandwidth portion, the on-demand SI is transmitted on the second initial bandwidth portion, avoiding the first type of terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first type of terminal.

[0055] Please see Figure 3 , Figure 3 This is a flowchart of another system information transmission method provided in this embodiment.

[0056] like Figure 3 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S31: In response to receiving an SI request message sent by a first type of terminal based on a first configuration, the requested SI is sent on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the first configuration.

[0057] In the embodiments of this disclosure, when a network-side device receives an SI request message sent by a first type of terminal based on a first configuration, it can determine that the terminal type is a first type of terminal and determine whether the requested SI should be sent on a first initial downlink bandwidth portion or on a second initial downlink bandwidth portion.

[0058] In some possible implementations, the first configuration includes a first specific physical random access channel (PRACH) resource. That is, S31 of the embodiment can be: in response to receiving an SI request message sent by a first type of terminal using the first specific PRACH resource, the requested SI is sent on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the first configuration.

[0059] In all embodiments of this disclosure, a first type of terminal can send an SI request message using a first specific PRACH resource; a second type of terminal can send an SI request message using a second specific PRACH resource; the first specific PRACH resource used by the first type of terminal is different from the second specific PRACH resource used by the second type of terminal. Therefore, the network-side device can determine whether the terminal sending the SI request message is a first type of terminal or a second type of terminal based on the received first specific PRACH resource or second specific PRACH resource.

[0060] In some possible implementations, the first initial downlink bandwidth portion can be used by both Type II and Type I terminals, while the second initial downlink bandwidth portion can only be used by Type I terminals. In some possible implementations, the Type I terminal can be a Redcap terminal, and the Type II terminal can be a regular terminal, with the terminal capabilities of the Type I terminal differing from those of the Type II terminal.

[0061] In the above embodiments, the first type of terminal and the second type of terminal use different PRACH resources. After receiving the PRACH resource for sending the SI request message, the network-side device can determine whether the terminal sending the SI request message is a first type terminal or a second type terminal based on the PRACH resource corresponding to the SI request message. Accordingly, the network-side device can, based on the terminal type and the result of determining whether the requested SI should be sent on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion based on the first configuration, send the requested SI on the corresponding first initial downlink bandwidth portion or the second initial downlink bandwidth portion. That is, in response to the received SI request message being sent through the first specific PRACH resource, it can be determined that the terminal sending the SI request message is a first type terminal, and based on the result of determining whether the requested SI should be sent on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion based on the first configuration, the requested SI is sent on the corresponding first initial downlink bandwidth portion or the second initial downlink bandwidth portion.

[0062] Based on this, when the network-side device determines that the terminal type is a first-type terminal based on the received SI request message including the first specific PRACH resource, and determines based on the first configuration that the requested SI should be sent in the first initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the first initial downlink bandwidth portion. Alternatively, when the network-side device determines that the terminal type is a first-type terminal based on the received SI request message including the first specific PRACH resource, and determines based on the first configuration that the requested SI should be sent in the second initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the second initial downlink bandwidth portion. This avoids the network-side device transmitting the requested SI separately in the first and second initial downlink bandwidth portions, improving the transmission efficiency of the network-side device. Furthermore, when the first-type terminal resides in the second initial downlink bandwidth portion, it can receive the requested SI in the second initial downlink bandwidth portion, avoiding the first-type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first-type terminal.

[0063] In some embodiments, the first specific PRACH resource includes at least one of the following: A specific preamble; a specific PRACH transmission timing; specific frequency resources; a specific initial uplink bandwidth portion.

[0064] In this embodiment of the disclosure, the first specific PRACH resource of the first type of terminal may include a specific preamble and / or a specific PRACH transmission timing and / or a specific frequency resource and / or a specific initial uplink bandwidth portion.

[0065] Please see Figure 4 , Figure 4 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0066] like Figure 4 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S41: Send first configuration information; wherein the configuration information includes a first specific PRACH resource and / or a second specific PRACH resource.

[0067] It should be noted that step S41 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with step S21 and / or step S31 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0068] In embodiments of this disclosure, the first configuration information may be an SIB1 message, or system information block (SIB).

[0069] In the above embodiments, the first configuration information includes a first specific PRACH resource. The network-side device sends the first configuration information containing the first specific PRACH resource to the first type of terminal to inform the first type of terminal of the PRACH resource used to send the SI request message.

[0070] In the above embodiments, the first configuration information includes a second specific PRACH resource. The network-side device sends the first configuration information containing the second specific PRACH resource to the second type of terminal to inform the second type of terminal of the PRACH resource used to send the SI request message.

[0071] In the above embodiments, the first configuration information includes a first specific PRACH resource and a second specific PRACH resource. The network-side device sends the first configuration information containing the first specific PRACH resource to the first type of terminal and sends the configuration information containing the second specific PRACH resource to the second type of terminal, so as to inform the first type of terminal and the second type of terminal of the PRACH resource used to send the SI request message.

[0072] Of course, there are many ways for the first type of terminal to determine the first specific PRACH resource. In the above embodiment, the network-side device determines the first specific PRACH resource by sending first configuration information. However, those skilled in the art will understand that the first type of terminal can also determine the first specific PRACH resource in other ways, such as through a communication protocol, by receiving first configuration information of the first specific PRACH resource from other devices, or by having it pre-stored in the first type of terminal. This disclosure does not limit this. Correspondingly, there are also many ways for the second type of terminal to determine the second specific PRACH resource, as exemplified above, which will not be repeated here.

[0073] Please see Figure 5 , Figure 5 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0074] like Figure 5 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S51: In response to the received SI request message sent by the first type of terminal based on the second configuration, the requested SI is sent on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the second configuration.

[0075] In the embodiments of this disclosure, when a network-side device receives an SI request message sent by a first-type terminal based on a second configuration, it can determine that the terminal type is a first-type terminal and determine whether the requested SI should be sent on the first initial downlink bandwidth portion or on the second initial downlink bandwidth portion.

[0076] In some possible implementations, the second configuration includes a third message Msg3, which includes an SI request message, sent by the first type of terminal using the second initial uplink bandwidth portion. That is, S41 of the embodiment can be: in response to receiving the third message Msg3, which includes an SI request message, sent by the first type of terminal using the second initial uplink bandwidth portion, the requested SI is sent on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the second configuration.

[0077] In this embodiment, the initial uplink bandwidth used by the first type of terminal and the second type of terminal to send the third message Msg3 can be different. The first type of terminal can use either the first initial uplink bandwidth or the second initial uplink bandwidth to send the third message Msg3, while the second type of terminal can only use the first initial uplink bandwidth to send the third message Msg3. Therefore, based on the received third message Msg3 sent by the first type of terminal using the second initial uplink bandwidth, the network-side device can determine that the third message Msg3 was sent by the first type of terminal, and thus determine that the type of the first type of terminal is indeed the first type of terminal.

[0078] In some possible implementations, the first initial downlink bandwidth portion can be used by both Type II and Type I terminals, while the second initial downlink bandwidth portion can only be used by Type I terminals. In some possible implementations, the Type I terminal can be a Redcap terminal, and the Type II terminal can be a regular terminal, with the terminal capabilities of the Type I terminal differing from those of the Type II terminal.

[0079] In the above embodiments, when the network-side device receives a third message Msg3 containing an SI request message sent by the second initial uplink bandwidth portion used by the first type of terminal, it can determine that the terminal type is a first type of terminal. Accordingly, the network-side device can determine, based on the terminal type and the second configuration, whether to send the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion, and send the requested SI on either the first or second initial downlink bandwidth portion. That is, in response to the received third message Msg3 containing an SI request message sent by the second initial uplink bandwidth portion used by the first type of terminal, it can determine that the terminal type is a first type of terminal, and based on the second configuration, it can determine whether to send the requested SI on the first or second initial downlink bandwidth portion, and send the requested SI on either the first or second initial downlink bandwidth portion.

[0080] Based on this, when the network-side device determines that the terminal type is a first-type terminal based on the third message Msg3, which includes an SI request message, sent by the second initial uplink bandwidth portion used by the first-type terminal, and determines based on the second configuration that the requested SI should be sent in the first initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the first initial downlink bandwidth portion. Alternatively, when the network-side device determines that the terminal type is a first-type terminal based on the received SI request message including a first specific PRACH resource, and determines based on the second configuration that the requested SI should be sent in the second initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the second initial downlink bandwidth portion. This avoids the network-side device transmitting the requested SI separately in the first and second initial downlink bandwidth portions, improving the transmission efficiency of the network-side device. Furthermore, when the first-type terminal resides in the second initial downlink bandwidth portion, it can receive the requested SI in the second initial downlink bandwidth portion, avoiding the first-type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first-type terminal.

[0081] In some embodiments, the third message Msg3 includes the information field of the SI request message.

[0082] Please see Figure 6 , Figure 6 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0083] like Figure 6 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S61: Receive the first message from the first type of terminal; wherein the first message is a random access request message, and random access is received in the second initial uplink bandwidth portion.

[0084] It is understandable that when a type of terminal randomly accesses a network-side device, it can initiate random access by sending a random access request to the network-side device.

[0085] It should be noted that step S61 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with step S21 and / or step S31 and / or step S41 and / or step S51 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0086] Please see Figure 7 , Figure 7 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0087] like Figure 7 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S71: Send second configuration information; wherein the second configuration information includes first SI scheduling information, which is applied to configure the requested SI to transmit only on the first initial downlink bandwidth portion.

[0088] In embodiments of this disclosure, the network-side device sends second configuration information including first SI scheduling information to the terminal. The first SI scheduling information indicates that the terminal can only receive requested SIs on the first initial downlink bandwidth. In response to the SI request message sent by the terminal, the network-side device sends requested SIs to the terminal on the first initial downlink bandwidth. The terminal includes a first type of terminal and a second type of terminal.

[0089] In some possible implementations, the terminal includes a first type of terminal and a second type of terminal; the first type of terminal can be a Redcap terminal, and the second type of terminal can be a regular terminal. The terminal capabilities of the first type of terminal are different from those of the second type of terminal.

[0090] In embodiments of this disclosure, the first SI scheduling information is used to configure the requested SI to be transmitted only on the first initial downlink bandwidth portion. It is understood that, in this case, regardless of whether the terminal is a first type terminal or a second type terminal, the requested SI can only be received on the first initial downlink bandwidth portion.

[0091] In embodiments of this disclosure, the second configuration information may be an SIB1 message, or system information block (SIB).

[0092] In the above embodiments, the second configuration information includes the first SI scheduling information. The network-side device sends the second configuration information containing the first SI scheduling information to the terminal to inform the first type of terminal to receive the requested SI on the first initial downlink bandwidth portion.

[0093] Of course, there are many ways for the first type of terminal to determine the first SI scheduling information. In the above embodiment, the network-side device determines the first type of terminal by sending the second configuration information. However, those skilled in the art will understand that the first type of terminal can also determine the first SI scheduling information in other ways, such as through a communication protocol, or by receiving configuration information of the first SI scheduling information from other devices, or by having it pre-stored in the first type of terminal. This disclosure does not limit this. It should be noted that S71 can be implemented alone, or it can be implemented in combination with any other step in this disclosure, such as in combination with S21 and / or S31 and / or S41 and / or S51 and / or S61 in this disclosure. This disclosure does not limit this.

[0094] Please see Figure 8 , Figure 8 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0095] like Figure 8 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S81: Send second configuration information; wherein the second configuration information includes second SI scheduling information, which is used to configure the transmission of the requested SI of the second type of terminal in the first initial downlink bandwidth portion, and the transmission of the requested SI of the first type of terminal in the second initial downlink bandwidth portion.

[0096] In some possible implementations, the terminal includes a first type of terminal and a second type of terminal; the first type of terminal can be a Redcap terminal, and the second type of terminal can be a regular terminal. The terminal capabilities of the first type of terminal are different from those of the second type of terminal.

[0097] In embodiments of this disclosure, the network-side device sends second configuration information, including second SI scheduling information, to the terminal. The second SI scheduling information indicates that the requested SI of the second type of terminal is transmitted in the first initial downlink bandwidth portion, and that the requested SI of the first type of terminal is transmitted in the second initial downlink bandwidth portion. In response to the SI request message sent by the first type of terminal, the network-side device sends the requested SI in the second initial downlink bandwidth. In response to the SI request message sent by the second type of terminal, the network-side device sends the requested SI in the first initial downlink bandwidth.

[0098] In embodiments of this disclosure, second configuration information is sent to a first type of terminal to inform the first type of terminal to receive the requested SI in the second initial bandwidth portion; second configuration information is also sent to a second type of terminal to inform the second type of terminal to receive the requested SI in the first initial bandwidth portion.

[0099] Of course, there are many ways for the first type of terminal and the second type of terminal to determine the second SI scheduling information. In the above embodiment, the network-side device sends the second configuration information so that the first type of terminal and the second type of terminal can determine the second SI scheduling information. However, those skilled in the art will understand that the first type of terminal and the second type of terminal can also determine the second SI scheduling information in other ways, such as through communication protocols, or by receiving configuration information of the second SI scheduling information from other devices, or by having it pre-stored in the first type of terminal and the second type of terminal. This disclosure does not limit this.

[0100] In the embodiments of this disclosure, after the network-side device receives the SI request information sent by the terminal, if it determines that the terminal type is a first type terminal, it sends the requested SI to the first type terminal on the second initial downlink bandwidth portion. Therefore, the network-side device can transmit the requested SI only on the second initial downlink bandwidth portion, avoiding the need for the network-side device to transmit the requested SI separately on the first and second initial downlink bandwidth portions, thus improving the transmission efficiency of the network-side device. Furthermore, since the first type terminal resides on the second initial downlink bandwidth portion, it can receive the requested SI on that portion, avoiding the first type terminal switching back and forth between the first and second initial downlink bandwidth portions, which saves power consumption for the first type terminal.

[0101] It should be noted that S81 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S21 and / or S31 and / or S41 and / or S51 and / or S61 and / or S71 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0102] Please see Figure 9 , Figure 9 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0103] like Figure 9 As shown, this method is executed by a network-side device, and the method may include, but is not limited to, the following steps: S91: Send a Random Access Response (RAR) message to a Type 1 terminal; wherein the RAR message is sent on the second initial downlink bandwidth portion.

[0104] It should be noted that step S91 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with step S21 and / or step S31 and / or S41 and / or S51 and / or S61 and / or step S71 and / or step S81 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0105] In embodiments of this disclosure, the network-side device receives an SI request message sent by a first type of terminal on a first specific PRACH resource, or, upon receiving a random access request sent by a first type of terminal on a second initial uplink bandwidth portion, sends a RAR message to the first type of terminal to inform it that it can access the network-side device.

[0106] Please see Figure 10 , Figure 10 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0107] like Figure 10 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S101: Send a System Information (SI) request message, and receive the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the configuration corresponding to the System Information (SI) request message.

[0108] In some possible implementations, the terminal includes a first type of terminal and a second type of terminal; the first type of terminal can be a Redcap terminal, and the second type of terminal can be a regular terminal. The terminal capabilities of the first type of terminal are different from those of the second type of terminal.

[0109] The first initial downlink bandwidth portion can be used by both Type 1 and Type 2 terminals, while the second initial downlink bandwidth portion can only be used by Type 1 terminals.

[0110] In this embodiment of the disclosure, the configuration corresponding to the SI request message sent by the first type of terminal is different from the configuration corresponding to the SI request message sent by the second type of terminal. Therefore, the network-side device can determine the type of terminal that sent the SI request message based on the configuration corresponding to the received SI request message, and determine whether the requested SI should be sent on the first initial downlink bandwidth portion or on the second initial downlink bandwidth portion. Thus, the network-side device can send the requested SI on the corresponding first initial downlink bandwidth portion or second initial downlink bandwidth portion based on the type of terminal and the result of determining whether the requested SI should be sent on the first initial downlink bandwidth portion or the result of determining whether the requested SI should be sent on the second initial downlink bandwidth portion.

[0111] In an exemplary embodiment, when the network-side device determines that the terminal type is a first type terminal based on the configuration corresponding to the SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth portion, the network-side device sends the requested SI to the first type terminal on the first initial downlink bandwidth portion.

[0112] In another exemplary embodiment, when the network-side device determines that the terminal type is a first type terminal based on the configuration corresponding to the SI request message sent by the terminal, and determines that the requested SI should be sent on the second initial downlink bandwidth portion, the network-side device sends the requested SI to the first type terminal on the second initial downlink bandwidth portion. Thus, when it is determined that the requested SI should be sent on the second initial downlink bandwidth portion, the network-side device sends the requested SI on the second initial downlink bandwidth portion, eliminating the need for the network-side device to transmit the requested SI separately on the first and second initial downlink bandwidth portions, thereby improving the transmission efficiency of the network-side device. Furthermore, the first type terminal can reside on the second initial downlink bandwidth portion and receive the requested SI on the second initial downlink bandwidth portion, avoiding the first type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving the power consumption of the first type terminal.

[0113] In another exemplary embodiment, when the network-side device determines that the terminal type is a second type terminal based on the configuration corresponding to the SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth portion, the network-side device sends the requested SI to the second type terminal on the first initial downlink bandwidth portion.

[0114] By implementing the embodiments of this disclosure, the network-side device transmits the requested SI on either the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the configuration received from the terminal's System Information (SI) request message. Therefore, when both the first-type terminal and the second-type terminal reside simultaneously on the first initial downlink bandwidth portion, and the on-demand SI is transmitted on the first initial downlink bandwidth portion, both the first-type terminal and the second-type terminal can detect it, avoiding separate transmissions on the two initial downlink bandwidth portions and improving the transmission efficiency of the network-side device. Conversely, when the first-type terminal resides on the second initial downlink bandwidth portion, the on-demand SI is transmitted on the second initial bandwidth portion, avoiding the first-type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first-type terminal.

[0115] Please see Figure 11 , Figure 11 This is a flowchart of another system information transmission method provided in this embodiment.

[0116] like Figure 11 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S111: Send an SI request message based on the first configuration, and receive the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the first configuration.

[0117] In the embodiments of this disclosure, when a network-side device receives an SI request message sent by a first type of terminal based on a first configuration, it can determine that the terminal type is a first type of terminal and determine whether the requested SI should be sent on a first initial downlink bandwidth portion or on a second initial downlink bandwidth portion.

[0118] In some possible implementations, the first configuration includes a first specific physical random access channel (PRACH) resource. That is, S111 of the embodiment can be: sending an SI request message using the first specific PRACH resource, and receiving the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the first configuration.

[0119] In all embodiments of this disclosure, a first type of terminal can send an SI request message using a first specific PRACH resource; a second type of terminal can send an SI request message using a second specific PRACH resource; the first specific PRACH resource used by the first type of terminal is different from the second specific PRACH resource used by the second type of terminal. Therefore, the network-side device can determine whether the terminal sending the SI request message is a first type of terminal or a second type of terminal based on the received first specific PRACH resource or second specific PRACH resource.

[0120] In some possible implementations, the first initial downlink bandwidth portion can be used by both Type II and Type I terminals, while the second initial downlink bandwidth portion can only be used by Type I terminals. In some possible implementations, the Type I terminal can be a Redcap terminal, and the Type II terminal can be a regular terminal, with the terminal capabilities of the Type I terminal differing from those of the Type II terminal.

[0121] In the above embodiments, the first type of terminal and the second type of terminal use different PRACH resources. After receiving the PRACH resource for sending the SI request message, the network-side device can determine whether the terminal sending the SI request message is a first type terminal or a second type terminal based on the PRACH resource corresponding to the SI request message. Accordingly, the network-side device can, based on the terminal type and the result of determining whether the requested SI should be sent on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion based on the first configuration, send the requested SI on the corresponding first initial downlink bandwidth portion or the second initial downlink bandwidth portion. That is, in response to the received SI request message being sent through the first specific PRACH resource, it can be determined that the terminal sending the SI request message is a first type terminal, and based on the result of determining whether the requested SI should be sent on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion based on the first configuration, the requested SI is sent on the corresponding first initial downlink bandwidth portion or the second initial downlink bandwidth portion.

[0122] Based on this, when the network-side device determines that the terminal type is a first-type terminal based on the received SI request message including the first specific PRACH resource, and determines based on the first configuration that the requested SI should be sent in the first initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the first initial downlink bandwidth portion. Alternatively, when the network-side device determines that the terminal type is a first-type terminal based on the received SI request message including the first specific PRACH resource, and determines based on the first configuration that the requested SI should be sent in the second initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the second initial downlink bandwidth portion. This avoids the network-side device transmitting the requested SI separately in the first and second initial downlink bandwidth portions, improving the transmission efficiency of the network-side device. Furthermore, when the first-type terminal resides in the second initial downlink bandwidth portion, it can receive the requested SI in the second initial downlink bandwidth portion, avoiding the first-type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first-type terminal.

[0123] In some embodiments, the first specific PRACH resource includes at least one of the following: A specific preamble; a specific PRACH transmission timing; specific frequency resources; a specific initial uplink bandwidth portion.

[0124] In this embodiment of the disclosure, the first specific PRACH resource of the first type of terminal may include a specific preamble and / or a specific PRACH transmission timing and / or a specific frequency resource and / or a specific initial uplink bandwidth portion.

[0125] Please see Figure 12 , Figure 12 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0126] like Figure 12 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S121: Receive first configuration information from the network-side device; wherein the configuration information includes a first specific PRACH resource and / or a second specific PRACH resource.

[0127] It should be noted that step S121 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with step S101 and / or step S111 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0128] In the above embodiments, the first configuration information includes a first specific PRACH resource. The network-side device sends the first configuration information containing the first specific PRACH resource to the first type of terminal to inform the first type of terminal of the PRACH resource used to send the SI request message.

[0129] In the above embodiments, the first configuration information includes a second specific PRACH resource. The network-side device sends the first configuration information containing the second specific PRACH resource to the second type of terminal to inform the second type of terminal of the PRACH resource used to send the SI request message.

[0130] In the above embodiments, the first configuration information includes a first specific PRACH resource and a second specific PRACH resource. The network-side device sends the first configuration information containing the first specific PRACH resource to the first type of terminal and sends the configuration information containing the second specific PRACH resource to the second type of terminal, so as to inform the first type of terminal and the second type of terminal of the PRACH resource used to send the SI request message.

[0131] Of course, there are many ways for the first type of terminal to determine the first specific PRACH resource. In the above embodiment, the network-side device determines the first specific PRACH resource by sending first configuration information. However, those skilled in the art will understand that the first type of terminal can also determine the first specific PRACH resource in other ways, such as through a communication protocol, by receiving first configuration information of the first specific PRACH resource from other devices, or by having it pre-stored in the first type of terminal. This disclosure does not limit this. Correspondingly, there are also many ways for the second type of terminal to determine the second specific PRACH resource, as exemplified above, which will not be repeated here.

[0132] Please see Figure 13 , Figure 13 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0133] like Figure 13 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S131: Send an SI request message based on the second configuration, and receive the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the second configuration.

[0134] In the embodiments of this disclosure, when a network-side device receives an SI request message sent by a first-type terminal based on a second configuration, it can determine that the terminal type is a first-type terminal and determine whether the requested SI should be sent on the first initial downlink bandwidth portion or on the second initial downlink bandwidth portion.

[0135] In some possible implementations, the second configuration includes a third message Msg3, which includes an SI request message, sent by the first type of terminal using the second initial uplink bandwidth portion. That is, S131 of the embodiment can be: sending a third message Msg3, which includes an SI request message, using the second initial uplink bandwidth portion, and receiving the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion corresponding to the second configuration.

[0136] In this embodiment, the initial uplink bandwidth used by the first type of terminal and the second type of terminal to send the third message Msg3 can be different. The first type of terminal can use either the first initial uplink bandwidth or the second initial uplink bandwidth to send the third message Msg3, while the second type of terminal can only use the first initial uplink bandwidth to send the third message Msg3. Therefore, based on the received third message Msg3 sent by the first type of terminal using the second initial uplink bandwidth, the network-side device can determine that the third message Msg3 was sent by the first type of terminal, and thus determine that the type of the first type of terminal is indeed the first type of terminal.

[0137] In some possible implementations, the first initial downlink bandwidth portion can be used by both Type II and Type I terminals, while the second initial downlink bandwidth portion can only be used by Type I terminals. In some possible implementations, the Type I terminal can be a Redcap terminal, and the Type II terminal can be a regular terminal, with the terminal capabilities of the Type I terminal differing from those of the Type II terminal.

[0138] In the above embodiments, when the network-side device receives a third message Msg3 containing an SI request message sent by the second initial uplink bandwidth portion used by the first type of terminal, it can determine that the terminal type is a first type of terminal. Accordingly, the network-side device can determine, based on the terminal type and the second configuration, whether to send the requested SI on the first initial downlink bandwidth portion or the second initial downlink bandwidth portion, and send the requested SI on either the first or second initial downlink bandwidth portion. That is, in response to the received third message Msg3 containing an SI request message sent by the second initial uplink bandwidth portion used by the first type of terminal, it can determine that the terminal type is a first type of terminal, and based on the second configuration, it can determine whether to send the requested SI on the first or second initial downlink bandwidth portion, and send the requested SI on either the first or second initial downlink bandwidth portion.

[0139] Based on this, when the network-side device determines that the terminal type is a first-type terminal based on the third message Msg3, which includes an SI request message, sent by the second initial uplink bandwidth portion used by the first-type terminal, and determines based on the second configuration that the requested SI should be sent in the first initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the first initial downlink bandwidth portion. Alternatively, when the network-side device determines that the terminal type is a first-type terminal based on the received SI request message including a first specific PRACH resource, and determines based on the second configuration that the requested SI should be sent in the second initial downlink bandwidth portion, the network-side device sends the requested SI to the first-type terminal in the second initial downlink bandwidth portion. This avoids the network-side device transmitting the requested SI separately in the first and second initial downlink bandwidth portions, improving the transmission efficiency of the network-side device. Furthermore, when the first-type terminal resides in the second initial downlink bandwidth portion, it can receive the requested SI in the second initial downlink bandwidth portion, avoiding the first-type terminal switching back and forth between the first and second initial downlink bandwidth portions, thus saving power consumption for the first-type terminal.

[0140] In some embodiments, the third message Msg3 includes the information field of the SI request message.

[0141] In some embodiments, the third message Msg3 includes the information field of the SI request message.

[0142] Please see Figure 14 , Figure 14 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0143] like Figure 14As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S141: Send a first message; wherein the first message is a random access request message, and random access is received in the second initial uplink bandwidth portion.

[0144] It is understandable that when a type of terminal randomly accesses a network-side device, it can initiate random access by sending a random access request to the network-side device.

[0145] It should be noted that step S141 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with step S101 and / or step S111 and / or step S121 and / or step S131 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0146] Please see Figure 15 , Figure 15 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0147] like Figure 15 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S151: Receive second configuration information from the network-side device; wherein the second configuration information includes first SI scheduling information, which is used to configure the requested SI to transmit only on the first initial downlink bandwidth portion.

[0148] In embodiments of this disclosure, the network-side device sends second configuration information including first SI scheduling information to the terminal. The first SI scheduling information indicates that the terminal can only receive requested SIs on the first initial downlink bandwidth. In response to the SI request message sent by the terminal, the network-side device sends requested SIs to the terminal on the first initial downlink bandwidth. The terminal includes a first type of terminal and a second type of terminal.

[0149] In some possible implementations, the terminal includes a first type of terminal and a second type of terminal; the first type of terminal can be a Redcap terminal, and the second type of terminal can be a regular terminal. The terminal capabilities of the first type of terminal are different from those of the second type of terminal.

[0150] In embodiments of this disclosure, the first SI scheduling information is used to configure the requested SI to be transmitted only on the first initial downlink bandwidth portion. It is understood that, in this case, regardless of whether the terminal is a first type terminal or a second type terminal, the requested SI can only be received on the first initial downlink bandwidth portion.

[0151] In embodiments of this disclosure, the first configuration information may be an SIB1 message, or system information block (SIB).

[0152] In the above embodiments, the second configuration information includes the first SI scheduling information. The network-side device sends the second configuration information containing the first SI scheduling information to the terminal to inform the first type of terminal to receive the requested SI on the first initial downlink bandwidth portion.

[0153] Of course, there are many ways for the first type of terminal to determine the first SI scheduling information. In the above embodiment, the network-side device determines the first type of terminal by sending the second configuration information. However, those skilled in the art will understand that the first type of terminal can also determine the first SI scheduling information in other ways, such as through a communication protocol, or by receiving configuration information of the first SI scheduling information from other devices, or by having it pre-stored in the first type of terminal. This disclosure does not limit this. It should be noted that S151 can be implemented alone, or it can be implemented in combination with any other step in this disclosure, such as in combination with S101 and / or S111 and / or S121 and / or S131 and / or S141 in this disclosure. This disclosure does not limit this.

[0154] Please see Figure 16 , Figure 16 This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0155] like Figure 16 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S161: Receive second configuration information from the network-side device; wherein the second configuration information includes second SI scheduling information, which is used to configure the transmission of the requested SI of the second type of terminal in the first initial downlink bandwidth portion, and the transmission of the requested SI of the first type of terminal in the second initial downlink bandwidth portion.

[0156] In some possible implementations, the terminal includes a first type of terminal and a second type of terminal; the first type of terminal can be a Redcap terminal, and the second type of terminal can be a regular terminal. The terminal capabilities of the first type of terminal are different from those of the second type of terminal.

[0157] In embodiments of this disclosure, the network-side device sends second configuration information, including second SI scheduling information, to the terminal. The second SI scheduling information indicates that the requested SI of the second type of terminal is transmitted in the first initial downlink bandwidth portion, and that the requested SI of the first type of terminal is transmitted in the second initial downlink bandwidth portion. In response to the SI request message sent by the first type of terminal, the network-side device sends the requested SI in the second initial downlink bandwidth. In response to the SI request message sent by the second type of terminal, the network-side device sends the requested SI in the first initial downlink bandwidth.

[0158] In embodiments of this disclosure, second configuration information is sent to a first type of terminal to inform the first type of terminal to receive the requested SI in the second initial bandwidth portion; second configuration information is also sent to a second type of terminal to inform the second type of terminal to receive the requested SI in the first initial bandwidth portion.

[0159] Of course, there are many ways for the first type of terminal and the second type of terminal to determine the second SI scheduling information. In the above embodiment, the network-side device sends the second configuration information so that the first type of terminal and the second type of terminal can determine the second SI scheduling information. However, those skilled in the art will understand that the first type of terminal and the second type of terminal can also determine the second SI scheduling information in other ways, such as through communication protocols, or by receiving configuration information of the second SI scheduling information from other devices, or by having it pre-stored in the first type of terminal and the second type of terminal. This disclosure does not limit this.

[0160] In the embodiments of this disclosure, after the network-side device receives the SI request information sent by the terminal, if it determines that the terminal type is a first type terminal, it sends the requested SI to the first type terminal on the second initial downlink bandwidth portion. Therefore, the network-side device can transmit the requested SI only on the second initial downlink bandwidth portion, avoiding the need for the network-side device to transmit the requested SI separately on the first and second initial downlink bandwidth portions, thus improving the transmission efficiency of the network-side device. Furthermore, since the first type terminal resides on the second initial downlink bandwidth portion, it can receive the requested SI on that portion, avoiding the first type terminal switching back and forth between the first and second initial downlink bandwidth portions, which saves power consumption for the first type terminal.

[0161] It should be noted that S161 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with S101 and / or S111 and / or S121 and / or S131 and / or S141 and / or S151 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0162] Please see Figure 17 , Figure 17This is a flowchart of another system information transmission method provided in the embodiments of this disclosure.

[0163] like Figure 17 As shown, this method is executed by a first-type terminal, and the method may include, but is not limited to, the following steps: S171: Receive the Random Access Response (RAR) message from the network-side device; wherein, the RAR message is received on the second initial downlink bandwidth portion.

[0164] It should be noted that step S171 can be implemented alone or in combination with any other step in the embodiments of this disclosure, such as in combination with step S101 and / or step S111 and / or S121 and / or S131 and / or S141 and / or S151 and / or S161 in the embodiments of this disclosure. The embodiments of this disclosure do not limit this.

[0165] In embodiments of this disclosure, the network-side device receives an SI request message sent by a first type of terminal on a first specific PRACH resource, or, upon receiving a random access request sent by a first type of terminal on a second initial uplink bandwidth portion, sends a RAR message to the first type of terminal to inform it that it can access the network-side device.

[0166] In the embodiments provided above, the methods provided by the present disclosure are described from the perspectives of network-side devices and first-type terminals, respectively. To implement the functions of the methods provided in the embodiments of the present disclosure, the network-side devices and the first-type terminals may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions can be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0167] Please see Figure 18 This is a schematic diagram of the structure of a system information transmission device 1 provided in an embodiment of this disclosure. Figure 18 The system information transmission device 1 shown may include a transceiver module 11. The transceiver module 11 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 11 can implement both sending and / or receiving functions.

[0168] The system information transmission device 1 can be a terminal (such as the first type of terminal in the aforementioned method embodiments), a device within a terminal, or a device that can be used in conjunction with a terminal. Alternatively, the system information transmission device 1 can be a network-side device, a device within a network-side device, or a device that can be used in conjunction with a network-side device.

[0169] System information transmission device 1 is a network-side device: The device includes a transceiver module 11, configured to transmit the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the configuration corresponding to the received system information (SI) request message sent by the terminal.

[0170] System information transmission device 1 is a terminal (such as the first type of terminal in the aforementioned method embodiments): The device includes: a transceiver module 11, configured to send a System Information (SI) request message, and receive the requested SI on a first initial downlink bandwidth portion or a second initial downlink bandwidth portion corresponding to the configuration corresponding to the SI request message.

[0171] Regarding the system information transmission device 1 in the above embodiments, the specific methods by which each module performs its operations have been described in detail in the embodiments related to the method, and will not be elaborated upon here. The system information transmission device 1 provided in the above embodiments of this disclosure achieves the same or similar beneficial effects as the system information transmission methods provided in some of the above embodiments, and will not be repeated here.

[0172] Please see Figure 19 , Figure 19 This is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of this disclosure. The communication device 1000 can be a network-side device, a terminal (such as the first type of terminal in the aforementioned method embodiments), a chip, chip system, or processor that supports the network-side device in implementing the above methods, or a chip, chip system, or processor that supports the terminal in implementing the above methods. This communication device 1000 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0173] The communication device 1000 can be a network-side device, a terminal, a chip, chip system, or processor that supports the network-side device in implementing the above methods, or a chip, chip system, or processor that supports the terminal in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0174] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0175] Optionally, the communication device 1000 may further include one or more memories 1002, which may store a computer program 1004. The memories 1002 execute the computer program 1004 to cause the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1002 may also store data. The communication device 1000 and the memories 1002 may be provided separately or integrated together.

[0176] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0177] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 executes the code instructions to cause the communication device 1000 to perform the method described in the above method embodiments.

[0178] Communication device 1000 is a network-side device: transceiver 1005 is used to perform... Figure 2 S21 in; Figure 3 S31 in; Figure 4 S41 in; Figure 5 S51 in; Figure 6 S61 in; Figure 7 S71 in the middle; Figure 8 S81 in; Figure 9 S91 in the middle.

[0179] The communication device 1000 is a terminal (such as the first type of terminal in the aforementioned method embodiments): the transceiver 1005 is used to execute... Figure 10 S101 in; Figure 11 S111 in; Figure 12 S121 in; Figure 13 S131 in; Figure 14 S141 in; Figure 15 S151 in; Figure 16 S161 in; Figure 17 S171 in the middle.

[0180] In one implementation, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0181] In one implementation, processor 1001 may store computer program 1003, which runs on processor 1001 and causes communication device 1000 to execute the methods described in the above method embodiments. Computer program 1003 may be embedded in processor 1001, in which case processor 1001 may be implemented in hardware.

[0182] In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0183] The communication device described in the above embodiments may be a terminal device (such as the terminal device in the foregoing method embodiments), but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may vary. Figure 19 The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) Independent integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs; (3) ASIC, such as modem; (4) Modules that can be embedded in other devices; (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc. (6) Others, etc.

[0184] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 20 This is a structural diagram of a chip provided in an embodiment of this disclosure.

[0185] Chip 1100 includes processor 1101 and interface 1103. The number of processors 1101 can be one or more, and the number of interfaces 1103 can be multiple.

[0186] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure: Interface 1103 is used to receive code instructions and transmit them to the processor.

[0187] Processor 1101 is configured to run code instructions to perform the system information transmission method as described in some of the embodiments above.

[0188] For cases where the chip is used to implement the functions of the network-side device in the embodiments of this disclosure: Interface 1103 is used to receive code instructions and transmit them to the processor.

[0189] Processor 1101 is configured to run code instructions to perform the system information transmission method as described in some of the embodiments above.

[0190] Optionally, chip 1100 may also include memory 1102, which is used to store necessary computer programs and data.

[0191] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0192] This disclosure also provides a system for system information transmission, the system including the aforementioned... Figure 18 In the embodiments, the system information transmission device serves as a terminal (such as the first type of terminal in the aforementioned method embodiments) and the system information transmission device serves as a network-side device; alternatively, the system includes the aforementioned... Figure 19 The embodiments include a communication device as a terminal (such as the first type of terminal in the aforementioned method embodiments) and a communication device as a network-side device.

[0193] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0194] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0195] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0196] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0197] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0198] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0199] The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0200] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0201] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0202] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A system information transmission method, characterized in that, The method is executed by a network-side device, and the method includes: Receive a third message MSG3, which includes a system information SI request message, on the second initial uplink bandwidth portion; Send configuration information, which includes first SI scheduling information, which is used to configure SI transmission on a first initial downlink bandwidth portion; The SI is transmitted on the first initial downlink bandwidth portion.

2. The method according to claim 1, characterized in that, The step of transmitting the SI on the first initial downlink bandwidth portion includes: In response to receiving a third message MSG3 containing a System Information (SI) request message sent by a first type of terminal using a first specific physical random access channel (PRACH) resource, the SI is transmitted on the first initial downlink bandwidth portion; the first specific PRACH resource used by the first type of terminal is different from the second specific PRACH resource used by the second type of terminal, and the terminal capabilities of the first type of terminal are different from those of the second type of terminal.

3. The method according to claim 2, characterized in that, The first specific PRACH resource includes at least one of the following: A specific preamble; Specific PRACH transmission timing; Specific frequency resources; A specific portion of the initial uplink bandwidth.

4. The method according to claim 2, characterized in that, The method further includes: Send first configuration information; wherein the first configuration information includes the first specific PRACH resource and / or the second specific PRACH resource.

5. The method according to any one of claims 1 to 4, characterized in that, The MSG3 includes the information field of the SI request message.

6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive random access request messages sent by the first type of terminal on the second initial uplink bandwidth portion; and / or Send a Random Access Response (RAR) message to the first type of terminal on the first initial downlink bandwidth portion.

7. A system information transmission method, characterized in that, The method is executed by a network-side device, and the method includes: Send configuration information, which includes first SI scheduling information. The first SI scheduling information is used to configure the transmission of SI on a first initial downlink bandwidth portion. The first SI scheduling information is used to instruct SI request messages to be sent on a second initial uplink bandwidth portion or a first specific PRACH resource. The first specific PRACH resource used by the first type of terminal is different from the second specific PRACH resource used by the second type of terminal.

8. The method according to claim 7, characterized in that, The method further includes: Receive the SI request message sent by the first type of terminal on the second initial uplink bandwidth portion or the first specific PRACH resource; and / or The SI is transmitted on the first initial downlink bandwidth portion.

9. The method according to claim 7, characterized in that, The first specific PRACH resource includes at least one of the following: A specific preamble; Specific PRACH transmission timing; Specific frequency resources; A specific portion of the initial uplink bandwidth.

10. The method according to any one of claims 7 to 9, characterized in that, The method further includes: Receive random access request messages sent by the first type of terminal on the second initial uplink bandwidth portion; and / or Send a Random Access Response (RAR) message to the first type of terminal on the first initial downlink bandwidth portion.

11. A system information transmission method, characterized in that, The method is executed by a first type of terminal, and the method includes: A third message MSG3, including a system information SI request message, is sent on the second initial uplink bandwidth portion; Receive configuration information, the configuration information including first SI scheduling information, the first SI scheduling information being used to configure SI transmission on a first initial downlink bandwidth portion; The SI is received on the first initial downlink bandwidth portion.

12. The method according to claim 11, characterized in that, The SI is a third message MSG3 sent by the network-side device after receiving the first terminal device using the first specific PRACH resource, which includes a system information SI request message, and is determined to be sent in the first initial downlink bandwidth portion; the first specific PRACH resource used by the first type of terminal is different from the second specific PRACH resource used by the second type of terminal, and the terminal capabilities of the first type of terminal are different from those of the second type of terminal.

13. The method according to claim 12, characterized in that, The first specific PRACH resource includes at least one of the following: A specific preamble; Specific PRACH transmission timing; Specific frequency resources; A specific portion of the initial uplink bandwidth.

14. The method according to claim 12, characterized in that, The method further includes: Receive first configuration information; wherein the first configuration information includes the first specific PRACH resource and / or the second specific PRACH resource.

15. The method according to any one of claims 11 to 14, characterized in that, The MSG3 includes the information field of the SI request message.

16. The method according to any one of claims 11 to 14, characterized in that, The method further includes: Send a random access request message on the second initial uplink bandwidth portion; and / or Receive a Random Access Response (RAR) message on the first initial downlink bandwidth portion.

17. A system information transmission method, characterized in that, The method is executed by a first type of terminal, and the method includes: The configuration information includes first SI scheduling information, which is used to configure the transmission of SI on a first initial downlink bandwidth portion. The first SI scheduling information is used to instruct the SI request message to be sent on a second initial uplink bandwidth portion or a first specific PRACH resource. The first specific PRACH resource used by the first type of terminal is different from the second specific PRACH resource used by the second type of terminal.

18. The method according to claim 17, characterized in that, The method further includes: Send the SI request message on the second initial uplink bandwidth portion or the first specific PRACH resource; and / or The SI is received on the first initial downlink bandwidth portion.

19. The method according to claim 17, characterized in that, The first specific PRACH resource includes at least one of the following: A specific preamble; Specific PRACH transmission timing; Specific frequency resources; A specific portion of the initial uplink bandwidth.

20. The method according to any one of claims 17 to 19, characterized in that, The method further includes: Send a random access request message on the second initial uplink bandwidth portion; and / or Receive a Random Access Response (RAR) message on the first initial downlink bandwidth portion.

21. A system information transmission device, characterized in that, The system information transmission device is used to perform the method according to any one of claims 1 to 10, 11 to 20.

22. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 1 to 10; Alternatively, the processor executes a computer program stored in the memory to cause the apparatus to perform the method as described in any one of claims 11 to 20.

23. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method as described in any one of claims 1 to 10; or the processor is configured to execute the code instructions to perform the method as described in any one of claims 11 to 20.

24. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 10 to be implemented; or, when executed, cause the method of any one of claims 11 to 20 to be implemented.

Images