WO2023039852A1 - 系统信息传输方法和装置 - Google Patents

系统信息传输方法和装置 Download PDF

Info

Publication number
WO2023039852A1
WO2023039852A1 PCT/CN2021/119138 CN2021119138W WO2023039852A1 WO 2023039852 A1 WO2023039852 A1 WO 2023039852A1 CN 2021119138 W CN2021119138 W CN 2021119138W WO 2023039852 A1 WO2023039852 A1 WO 2023039852A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
type
bandwidth part
downlink bandwidth
configuration
Prior art date
Application number
PCT/CN2021/119138
Other languages
English (en)
French (fr)
Inventor
牟勤
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2021/119138 priority Critical patent/WO2023039852A1/zh
Priority to CN202180002825.5A priority patent/CN113940128A/zh
Publication of WO2023039852A1 publication Critical patent/WO2023039852A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular to a system information transmission method and device.
  • Reduced capability UE user equipment, terminal
  • NR-lite or Redcap terminal for short.
  • Reduced capability UE user equipment, terminal
  • NR-lite or Redcap terminal for short.
  • a reduced capability UE Also known as a reduced capability UE.
  • Embodiments of the present disclosure provide a system information transmission method and device, so as to realize on-demand SI transmission.
  • an embodiment of the present disclosure provides a system information transmission method, the method is executed by a network side device, and the method includes: according to the received configuration corresponding to the system information SI request message sent by the terminal, in the configuration corresponding to the configuration The requested SI is sent on the first initial downlink bandwidth part or the second initial downlink bandwidth part.
  • the requested SI is sent on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the configuration, thus,
  • both the first type of terminal and the second type of terminal can monitor , which avoids separate transmission in the two initial downlink bandwidth parts, and can improve the transmission efficiency of the network side device.
  • the on-demand SI is transmitted on the second initial bandwidth part, avoiding the first type of terminal in the first initial downlink bandwidth part and the second initial downlink bandwidth part Switching back and forth can save the power consumption of the first type of terminal.
  • an embodiment of the present disclosure provides another system information transmission method, which is executed by a first type of terminal, and the method includes: sending a system information SI request message, and according to the configuration corresponding to the SI request message, in the The requested SI is received on the corresponding first initial downlink bandwidth part or the second initial downlink bandwidth part.
  • the embodiments of the present disclosure provide a system information transmission device, which has the function of implementing some or all of the functions of the network side equipment in the method example described in the first aspect above, for example, the function of the system information transmission device can be It possesses the functions of some or all of the embodiments in the present disclosure, and may also possess the function of independently implementing any one of the embodiments in the present disclosure.
  • the functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the system information transmission device may include a transceiver module in its structure, and the transceiver module is used to support communication between the system information transmission device and other devices.
  • the system information transmission device may further include a storage module, which is used to be coupled with the transceiver module and the processing module, and stores necessary computer programs and data of the system information transmission device.
  • the device for transmitting system information includes: a transceiver module configured to, according to the configuration corresponding to the received system information SI request message sent by the terminal, in the first initial downlink bandwidth part or the first initial downlink bandwidth part corresponding to the configuration 2. Send the requested SI on the initial downlink bandwidth part.
  • the embodiment of the present disclosure provides another system information transmission device, the communication device has some or all functions of the terminal equipment in the method described in the second aspect above, for example, the function of the communication device can have the The functions in some or all of the embodiments may also have the functions of independently implementing any one of the embodiments in the present disclosure.
  • the functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform corresponding functions in the foregoing method.
  • the transceiver module is used to support communication between the communication device and other equipment.
  • the communication device may further include a storage module, which is used to be coupled with the transceiver module and the processing module, and stores necessary computer programs and data of the communication device.
  • the processing module may be a processor
  • the transceiver module may be a transceiver or a communication interface
  • the storage module may be a memory
  • the system information transmission device includes: a transceiver module, configured to send a system information SI request message, and according to the configuration corresponding to the SI request message, in the first initial downlink bandwidth part corresponding to the configuration or The requested SI is received on the second initial downlink bandwidth part.
  • an embodiment of the present disclosure provides a communication device, where the communication device includes a processor, and when the processor invokes a computer program in a memory, executes the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, where the communication device includes a processor, and when the processor invokes a computer program in a memory, it executes the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device, the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device, the device includes a processor and an interface circuit, the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to make the The device executes the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, the device includes a processor and an interface circuit, the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to make the The device executes the method described in the second aspect above.
  • an embodiment of the present disclosure provides a system information transmission system, the system 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 fifth aspect
  • the embodiment of the present invention provides a computer-readable storage medium, which is used to store instructions used by the above-mentioned terminal equipment, and when the instructions are executed, the terminal equipment executes the above-mentioned first aspect. method.
  • an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned network equipment, and when the instructions are executed, the network equipment executes the method described in the above-mentioned second aspect .
  • the present disclosure further provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in the first aspect above.
  • the present disclosure further provides a computer program product including a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect above.
  • the present disclosure provides a chip system
  • the chip system includes at least one processor and an interface, used to support the terminal device to implement the functions involved in the first aspect, for example, determine or process the data involved in the above method and at least one of information.
  • the chip system further includes a memory, and the memory is configured to store necessary computer programs and data of the terminal device.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the present disclosure provides a chip system
  • the chip system includes at least one processor and an interface, used to support the network device to implement the functions involved in the second aspect, for example, determine or process the data involved in the above method and at least one of information.
  • the chip system further includes a memory, and the memory is used for saving necessary computer programs and data of the network device.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the first aspect above.
  • the present disclosure provides a computer program that, when run on a computer, causes the computer to execute the method described in the second aspect above.
  • FIG. 1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a system information transmission method provided by an embodiment of the present disclosure
  • Fig. 3 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 4 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 5 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 6 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 7 is a flow chart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 11 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 12 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 13 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 14 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 15 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 16 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • FIG. 17 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • Fig. 18 is a structural diagram of a system information transmission device provided by an embodiment of the present disclosure.
  • FIG. 19 is a structural diagram of a communication device provided by an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • FIG. 1 is a schematic structural diagram of a communication system 10 provided by an embodiment of the present disclosure.
  • the communication system 10 may include, but is not limited to, a network side device and a terminal.
  • the number and shape of the devices shown in FIG. The above network side equipment, two or more terminals.
  • the communication system 10 shown in FIG. 1 includes one network side device 101 and one terminal 102 as an example.
  • LTE long term evolution
  • 5th generation 5th generation
  • 5G new radio new radio, NR
  • other future new mobile communication systems etc.
  • the network-side device 101 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals.
  • the network side device 101 may be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or a A base station or an access node in a wireless fidelity (wireless fidelity, WiFi) system, etc.
  • eNB evolved NodeB
  • TRP transmission reception point
  • gNB next generation base station
  • a base station or an access node in a wireless fidelity (wireless fidelity, WiFi) system etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network side device.
  • the network side device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), where the CU may also be called a control unit (control unit).
  • the structure of the DU can separate the protocol layers of network-side devices, such as base stations. The functions of some protocol layers are centrally controlled by the CU, and the remaining part or all of the functions of the protocol layers are distributed in the DU, which is centrally controlled by the CU.
  • the terminal 102 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • a terminal may also be called a terminal (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), etc.
  • the terminal can be a car with communication function, smart car, mobile phone, wearable device, tablet computer (Pad), computer with wireless transceiver function, virtual reality (virtual reality, VR) terminal, augmented reality (augmented reality) , AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid Terminals, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal.
  • MTC machine type communication, machine type communication
  • NB-IoT narrow band-internet of things, narrowband Internet of Things
  • NB-IoT currently only supports a maximum rate of several hundred k
  • MTC currently only supports a maximum rate of several M.
  • IoT services such as video surveillance, smart home, wearable devices, and industrial sensor monitoring
  • these services usually require a speed of tens to 100M, and there are relative delays.
  • MTC in LTE NB-IoT technology is difficult to meet the requirements.
  • 5G NR new air interface
  • RedCap Lightweight air interface
  • this new terminal type is called a lightweight terminal (Reduced capability, Redcap terminal) or simply RedCap (lightweight air interface).
  • RedCap similar to IoT devices in LTE, RedCap based on 5G systems usually needs to meet the following requirements: low cost, low complexity; a certain degree of coverage enhancement; power saving.
  • the current NR new air interface
  • the current design cannot meet the above requirements of RedCap. Therefore, the current NR system needs to be modified to meet the requirements of RedCap.
  • the RF (radio frequency, radio frequency) bandwidth of NR-IoT can be limited, such as limited to 5MHz or 10MHz, or the buffer size of RedCap can be limited, thereby limiting each reception The size of the transport block, etc.
  • the possible optimization direction is to simplify the communication process, reduce the number of times RedCap terminals detect downlink control channels, etc.
  • on-demand SI in the on-demand SI transmission in the NR system, in the current system information transmission, some system information can be set to broadcast mode or non-broadcast mode, and the system information in the non-broadcast mode is on- demand SI.
  • on-demand SI has the following two application methods:
  • Method 1 The network device will configure a dedicated PRACH (physical random access channel, physical random access channel) resource, and the terminal will send a specific sign-in code preamble to obtain the required system information.
  • PRACH physical random access channel, physical random access channel
  • 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).
  • an embodiment of the present disclosure provides a system information transmission method to at least solve the problem of configuring a separate initial DL/UL BWP for Redcap terminals in the related art. There will be multiple initial DL/UL BWPs in the network side device, which cannot be performed. Technical issues of on-demand SI transmission.
  • FIG. 2 is a flowchart of a system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a network side device, and the method may include but not limited to the following steps:
  • the terminals include a first-type terminal and a second-type terminal; the first-type terminal can be a Redcap terminal, the second-type terminal can be an ordinary terminal, and the terminal capability of the first-type terminal is the same as that of the second-type terminal. Terminal capabilities vary from terminal to terminal.
  • the first initial downlink bandwidth part can be used by the first type of terminal and the second type of terminal, and the second initial downlink bandwidth part can only be used by the first type of terminal.
  • 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, so the network side device can, according to the configuration corresponding to the received SI request message, Determine the type of the terminal sending the SI request message, and determine whether the requested SI should be sent on the first initial downlink bandwidth part or the result of the requested SI should be sent on the second initial downlink bandwidth part, so that the network side device can according to the terminal type, and the result of determining that the requested SI should be sent on the first initial downlink bandwidth part or that the requested SI should be sent on the second initial downlink bandwidth part, in the corresponding first initial downlink bandwidth part or the second The requested SI is sent on the initial downlink bandwidth portion.
  • the network side device determines that the type of the terminal is the first type of terminal according to the configuration corresponding to the received SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth part. In this case, the network side device sends the requested SI to the first type of terminal on the first initial downlink bandwidth part.
  • the network side device determines that the type of the terminal is the first type of terminal according to the configuration corresponding to the received SI request message sent by the terminal, and determines that the requested terminal should be sent on the second initial downlink bandwidth part.
  • the network side device sends the requested SI to the first type of terminal on the second initial downlink bandwidth part, so that when it is determined that the requested SI should be sent on the second initial downlink bandwidth part, the network side device Sending the requested SI on the second initial downlink bandwidth part, the network side device does not need to transmit the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, which can improve the transmission efficiency of the network side device; and the first type The terminal can reside in the second initial downlink bandwidth part and receive the requested SI on the second initial downlink bandwidth part, which avoids the first type of terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink part, and can save the second initial downlink bandwidth part. Power consumption of a class of terminals.
  • the network side device determines that the type of the terminal is a second-type terminal according to the configuration corresponding to the received SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth part. In the case of SI, the network side device sends the requested SI to the second type of terminal on the first initial downlink bandwidth part.
  • the network side device sends the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the configuration according to the received configuration corresponding to the system information SI request message sent by the terminal. . Therefore, when the first type of terminal and the second type of terminal reside in the first initial downlink bandwidth part at the same time, and when the on-demand SI is transmitted on the first initial downlink bandwidth part, both the first type of terminal and the second type of terminal It can be detected that transmission in two initial downlink bandwidth parts is avoided, and the transmission efficiency of the network side device can be improved.
  • the on-demand SI is transmitted on the second initial bandwidth part, avoiding the first type of terminal in the first initial downlink bandwidth part and the second initial downlink bandwidth part Switching back and forth can save the power consumption of the first type of terminal.
  • FIG. 3 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the network side device, and the method may include but not limited to the following steps:
  • S31 In response to receiving the SI request message sent by the terminal of the first type based on the first configuration, send the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the first configuration.
  • the network side device receives the SI request message sent by the first type of terminal based on the first configuration, may determine that the terminal type is the first type of terminal, and determine that the SI request message should be sent on the first initial downlink bandwidth part. The requested SI should still send the result of the requested SI on the second initial downlink bandwidth part.
  • the first configuration includes first specific physical random access channel PRACH resources. That is, S31 of the embodiment may be: in response to receiving the SI request message sent by the first type of terminal using the first specific PRACH resource, in the first initial downlink bandwidth part or the second initial downlink bandwidth corresponding to the first configuration The requested SI is sent on the bandwidth part.
  • the first type of terminal can use the first specific PRACH resource to send the SI request message; the second type of terminal can use the second specific PRACH resource to send the SI request message; the first type of terminal uses the first specific PRACH The resource is different from the second specific PRACH resource used by the second type of terminal. Therefore, the network side device may determine, according to the received first specific PRACH resource or second specific PRACH resource, that the type of the terminal sending the SI request message is the first type terminal or the second type terminal.
  • the first initial downlink bandwidth part can be used by the second type of terminal and the first type of terminal, and the second initial downlink bandwidth part can only be used by the first type of terminal.
  • the first type of terminal may be a Redcap terminal
  • the second type of terminal may be an ordinary terminal
  • the terminal capability of the first type of terminal is different from that of the second type of terminal.
  • the first type of terminal and the second type of terminal use different PRACH resources; after the network side device receives the PRACH resource for sending the SI request message, it can determine to send the SI request message according to the PRACH resource corresponding to the SI request message. Whether the terminal of the request message is a first-type terminal or a second-type terminal. The corresponding network side device can determine according to the type of the terminal and based on the first configuration that the requested SI should be sent on the first initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part, corresponding to The requested SI is sent on the first initial downlink bandwidth part or the second initial downlink bandwidth part.
  • the terminal sending the SI request message is the first type of terminal, and it is determined based on the first configuration that the first initial downlink bandwidth part Whether the requested SI should be sent on the second initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part corresponds to sending the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part.
  • the network side device determines that the terminal type is the first type of terminal according to the received SI request message including the first specific PRACH resource, and determines that the requested SI should be sent in the first initial downlink bandwidth part based on the first configuration. In the case of , the network side device sends the requested SI to the first type of terminal in the first initial downlink bandwidth part, or, the network side device determines that the terminal type is the first type according to the received SI request message including the first specific PRACH resource A type of terminal, and when it is determined based on the first configuration that the requested SI should be sent in the second initial downlink bandwidth part, the network side device sends the requested SI to the first type of terminal in the second initial downlink bandwidth part.
  • the network side device transmits the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, and the transmission efficiency of the network side device can be improved, and the terminal of the first type resides in the second initial downlink bandwidth part
  • the requested SI can be received on the second initial downlink bandwidth part, avoiding the first type of terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink part, and saving the power consumption of the first type of terminal.
  • the first specific PRACH resource includes at least one of the following:
  • a specific preamble ; a specific PRACH transmission opportunity; a specific frequency resource; a specific initial uplink bandwidth part.
  • the first specific PRACH resource of the first type of terminal may include a specific preamble and/or a specific PRACH transmission opportunity and/or a specific frequency resource and/or a specific initial uplink bandwidth part.
  • FIG. 4 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the network side device, and the method may include but not limited to the following steps:
  • S41 Send first configuration information; wherein, the configuration information includes first specific PRACH resources and/or second specific PRACH resources.
  • step S41 can be implemented alone, or can be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with step S21 and/or step S31 in the embodiments of the present disclosure.
  • the embodiment does not limit this.
  • the first configuration information may be a SIB1 message, a system information block (system information block, SIB).
  • SIB system information block
  • the first configuration information includes the first specific PRACH resource
  • the network side device sends the first configuration information including the first specific PRACH resource to the first type of terminal to inform the first type of terminal to send the SI request message.
  • PRACH resources include the first specific PRACH resource
  • the first configuration information includes the second specific PRACH resource
  • the network side device sends the first configuration information including the second specific PRACH resource to the second type of terminal to inform the second type of terminal to send the SI request message.
  • PRACH resources include the second specific PRACH resource
  • the first configuration information includes the first specific PRACH resource and the second specific PRACH resource
  • the network side device sends the first configuration information including the first specific PRACH resource to the first type of terminal, and sends the first configuration information including the second specific PRACH resource.
  • the configuration information of the PRACH resource is sent to the second type of terminal, so as to respectively inform the first type of terminal and the second type of terminal of the PRACH resource used for sending the SI request message.
  • the network side device sends the first configuration information so that the first type of terminal determines the first specific PRACH resource; but this Those skilled in the art can understand that the first type of terminal can also determine the first specific PRACH resource in other ways, such as determining through a communication protocol, or receiving the first configuration information of the first specific PRACH resource from other devices, or pre-setting It exists in the first type of terminal, which is not limited in this embodiment of the present disclosure.
  • the second type of terminal may be many ways for the second type of terminal to determine the second specific PRACH resource, such as the previous example, which will not be repeated here.
  • FIG. 5 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a network side device, and the method may include but not limited to the following steps:
  • S51 In response to receiving the SI request message sent by the terminal of the first type based on the second configuration, send the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the second configuration.
  • the network side device receives the SI request message sent by the first type of terminal based on the second configuration, can determine that the terminal type is the first type of terminal, and determine that it should be sent on the first initial downlink bandwidth part The requested SI should still send the result of the requested SI on the second initial downlink bandwidth part.
  • the second configuration includes the third message Msg3 including the SI request message sent by the first type of terminal using the second initial uplink bandwidth part, that is, S41 of the embodiment may be: in response to receiving the first A type of terminal uses the third message Msg3 including the SI request message sent by the second initial uplink bandwidth part to send the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the second configuration.
  • the initial uplink bandwidth used by the first type of terminal and the second type of terminal to send the third message Msg3 may be different, wherein the first type of terminal may use the first initial uplink bandwidth or the second initial uplink bandwidth Send the third message Msg3, and the second type of terminal can only use the first initial uplink bandwidth part to send the third message Msg3. Therefore, according to the received third message Msg3 sent by the first type of terminal using the second initial uplink bandwidth part, the network side device can determine that the third message Msg3 is sent by the first type of terminal, thereby determining the type of the first type of terminal For the first type of terminal.
  • the first initial downlink bandwidth part can be used by the second type of terminal and the first type of terminal, and the second initial downlink bandwidth part can only be used by the first type of terminal.
  • the first type of terminal may be a Redcap terminal
  • the second type of terminal may be an ordinary terminal
  • the terminal capability of the first type of terminal is different from that of the second type of terminal.
  • the network side device receives the third message Msg3 including the SI request message sent by the second initial uplink bandwidth part used by the first type of terminal, and can determine that the terminal type is the first type of terminal, and the corresponding network side The device can determine whether the requested SI should be sent on the first initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part according to the type of the terminal and based on the second configuration.
  • the requested SI is sent on the bandwidth part or the second initial downlink bandwidth part.
  • the terminal type is the first type of terminal, and based on the second configuration, it is determined that the Whether to send the requested SI on the first initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part, correspondingly send the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part .
  • the network side device determines that the terminal type is the first type terminal according to the received third message Msg3 including the SI request message sent by the second initial uplink bandwidth part used by the first type terminal, and determines based on the second configuration In the case that the requested SI should be sent in the first initial downlink bandwidth part, the network side device sends the requested SI to the first type of terminal in the first initial downlink bandwidth part, or, the network side device sends the requested SI according to the received information including the first An SI request message for a specific PRACH resource determines that the terminal type is the first type of terminal, and it is determined based on the second configuration that the requested SI should be sent in the second initial downlink bandwidth part, then the network side device will transmit the requested SI in the second initial downlink bandwidth In part, the requested SI is sent to the first type of terminal.
  • the network side device transmits the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, and the transmission efficiency of the network side device can be improved, and the terminal of the first type resides in the second initial downlink bandwidth part
  • the requested SI can be received on the second initial downlink bandwidth part, avoiding the first type of terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink part, and saving the power consumption of the first type of terminal.
  • the third message Msg3 includes an information field of the SI request message.
  • FIG. 6 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the network side device, and the method may include but not limited to the following steps:
  • S61 Receive a first message from a terminal of the first type; wherein, the first message is a random access request message, and random access is received in the second initial uplink bandwidth.
  • the terminal of the first type when it randomly accesses the network-side device, it may send a random access request to the network-side device, thereby initiating random access to the network-side device.
  • step S61 can be implemented alone, or can be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with step S21 and/or step S31 and/or step S41 and /or step S51 is implemented together, which is not limited in this embodiment of the present disclosure.
  • FIG. 7 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the network side device, and the method may include but not limited to the following steps:
  • S71 Send second configuration information; wherein, the second configuration information includes first SI scheduling information, and the first SI scheduling information is used to configure transmission of the requested SI only on the first initial downlink bandwidth part.
  • the network side device sends the second configuration information including the first SI scheduling information to the terminal, and the first SI scheduling information indicates that the terminal can only receive the requested SI on the first initial downlink bandwidth, and responds to the terminal
  • the network side device sends the requested SI to the terminal on the first initial downlink bandwidth, where the terminal includes a first-type terminal and a second-type terminal.
  • the terminals include a first-type terminal and a second-type terminal; the first-type terminal can be a Redcap terminal, the second-type terminal can be an ordinary terminal, and the terminal capability of the first-type terminal is the same as that of the second-type terminal. Terminal capabilities vary from terminal to terminal.
  • the first SI scheduling information is used to configure the transmission of the requested SI only on the first initial downlink bandwidth part. It can be understood that in this case, regardless of the type of the terminal Also the terminal of the second type can only receive the requested SI on the first initial downlink bandwidth part.
  • the second configuration information may be a SIB1 message, a system information block (system information block, SIB).
  • the second configuration information includes the first SI scheduling information
  • the network side device sends the second configuration information including the first SI scheduling information to the terminal to inform the first type of terminal to receive the first initial downlink bandwidth part. SI is requested.
  • the network side device sends the second configuration information to make the first type of terminal determine the first SI scheduling information; but this Those skilled in the art can understand that the first type of terminal can also determine the first SI scheduling information in other ways, such as determining through a communication protocol, or receiving configuration information of the first SI scheduling information from other devices, or pre-existing the first SI scheduling information. In a type of terminal, the embodiment of the present disclosure does not limit this.
  • S71 can be implemented alone, or can be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S21 and/or S31 and/or S41 and/or S51 and and/or S61 are implemented together, which is not limited in this embodiment of the present disclosure.
  • FIG. 8 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a network side device, and the method may include but not limited to the following steps:
  • S81 Send second configuration information; wherein, the second configuration information includes second SI scheduling information, and the second SI scheduling information is used to configure the requested SI transmission of the second type of terminal in the first initial downlink bandwidth part, and the first type The requested SI of the terminal is transmitted on the second initial downlink bandwidth part.
  • the terminals include a first-type terminal and a second-type terminal; the first-type terminal can be a Redcap terminal, the second-type terminal can be an ordinary terminal, and the terminal capability of the first-type terminal is the same as that of the second-type terminal. Terminal capabilities vary from terminal to terminal.
  • the network side device sends second configuration information including second SI scheduling information to the terminal, and the second SI scheduling information indicates that the requested SI of the second type of terminal is transmitted in the first initial downlink bandwidth part, and The requested SI of the first type of terminal is transmitted on the second initial downlink bandwidth part, and in response to the SI request message sent by the first type of terminal, the network side device sends the requested SI on the second initial downlink bandwidth, and responds to the second type of For the SI request message sent by the terminal, the network side device sends the requested SI on the first initial downlink bandwidth.
  • the second configuration information is sent to the first type of terminal to inform the first type of terminal to receive the requested SI in the second initial bandwidth part; the second configuration information is sent to the second type of terminal to inform the first type of terminal The Type 2 terminal receives the requested SI in the first initial bandwidth portion.
  • the network side device sends the second configuration information to make the first type of terminal and the second type
  • the terminal determines the second SI scheduling information; but those skilled in the art can 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 determining through a communication protocol, or receiving from other devices
  • the configuration information to the second SI scheduling information may be pre-stored in the first-type terminal and the second-type terminal, which is not limited in this embodiment of the present disclosure.
  • the network side device after receiving the SI request information sent by the terminal, determines that the type of the terminal is a first-type terminal, and sends the requested Si.
  • the network side device can only transmit the requested SI in the second initial downlink bandwidth part, avoiding that the network side device needs to transmit the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, and can improve the network side.
  • the transmission efficiency of the equipment, and the first type of terminal resides in the second initial downlink bandwidth part, and can receive the requested SI on the second initial downlink bandwidth part, avoiding the first type of terminal in the first initial downlink bandwidth part and the second Switching back and forth in the initial downlink part can save power consumption of the first type of terminal.
  • S81 can be implemented alone, or can be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S21 and/or S31 and/or S41 and/or S51 and /or S61 and/or S71 are implemented together, which is not limited in this embodiment of the present disclosure.
  • FIG. 9 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the network side device, and the method may include but not limited to the following steps:
  • S91 Send a random access response RAR message to the first type of terminal; where the RAR message is sent on the second initial downlink bandwidth part.
  • step S91 may be implemented alone, or may be implemented in combination with any other steps in the embodiment of the present disclosure, for example, in combination with step S21 and/or step S31 and/or S41 and/or in the embodiment of the present disclosure Or S51 and/or S61 and/or step S71 and/or step S81 are implemented together, which is not limited in this embodiment of the present disclosure.
  • the network side device receives the SI request message sent by the first type of terminal on the first specific PRACH resource, or, after receiving the random access message sent by the first type of terminal on the second initial uplink bandwidth part, input, and send a RAR message to the first type of terminal to inform that the first type of terminal can access the network side device.
  • FIG. 10 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a first type of terminal, and the method may include but 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 part or the second initial downlink bandwidth part corresponding to the configuration according to the configuration corresponding to sending the system information SI request message.
  • the terminals include a first-type terminal and a second-type terminal; the first-type terminal can be a Redcap terminal, the second-type terminal can be an ordinary terminal, and the terminal capability of the first-type terminal is the same as that of the second-type terminal. Terminal capabilities vary from terminal to terminal.
  • the first initial downlink bandwidth part can be used by the first type of terminal and the second type of terminal, and the second initial downlink bandwidth part can only be used by the first type of terminal.
  • 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, so the network side device can, according to the configuration corresponding to the received SI request message, Determine the type of the terminal sending the SI request message, and determine whether the requested SI should be sent on the first initial downlink bandwidth part or the result of the requested SI should be sent on the second initial downlink bandwidth part, so that the network side device can according to the terminal type, and the result of determining that the requested SI should be sent on the first initial downlink bandwidth part or that the requested SI should be sent on the second initial downlink bandwidth part, in the corresponding first initial downlink bandwidth part or the second The requested SI is sent on the initial downlink bandwidth portion.
  • the network side device determines that the type of the terminal is the first type of terminal according to the configuration corresponding to the received SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth part. In this case, the network side device sends the requested SI to the first type of terminal on the first initial downlink bandwidth part.
  • the network side device determines that the type of the terminal is the first type of terminal according to the configuration corresponding to the received SI request message sent by the terminal, and determines that the requested terminal should be sent on the second initial downlink bandwidth part.
  • the network side device sends the requested SI to the first type of terminal on the second initial downlink bandwidth part, so that when it is determined that the requested SI should be sent on the second initial downlink bandwidth part, the network side device Sending the requested SI on the second initial downlink bandwidth part, the network side device does not need to transmit the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, which can improve the transmission efficiency of the network side device; and the first type The terminal can reside in the second initial downlink bandwidth part and receive the requested SI on the second initial downlink bandwidth part, which avoids the first type of terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink part, and can save the second initial downlink bandwidth part. Power consumption of a class of terminals.
  • the network side device determines that the type of the terminal is a second-type terminal according to the configuration corresponding to the received SI request message sent by the terminal, and determines that the requested SI should be sent on the first initial downlink bandwidth part. In the case of SI, the network side device sends the requested SI to the second type of terminal on the first initial downlink bandwidth part.
  • the network side device sends the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the configuration according to the received configuration corresponding to the system information SI request message sent by the terminal. . Therefore, when the first type of terminal and the second type of terminal reside in the first initial downlink bandwidth part at the same time, and when the on-demand SI is transmitted on the first initial downlink bandwidth part, both the first type of terminal and the second type of terminal It can be monitored that separate transmissions in the two initial downlink bandwidth parts are avoided, and the transmission efficiency of the network side device can be improved.
  • the on-demand SI is transmitted on the second initial bandwidth part, avoiding the first type of terminal in the first initial downlink bandwidth part and the second initial downlink bandwidth part Switching back and forth can save the power consumption of the first type of terminal.
  • FIG. 11 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a first type of terminal, and the method may include but 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 part or the second initial downlink bandwidth part corresponding to the first configuration.
  • the network side device receives the SI request message sent by the first type of terminal based on the first configuration, may determine that the terminal type is the first type of terminal, and determine that the SI request message should be sent on the first initial downlink bandwidth part. The requested SI should still send the result of the requested SI on the second initial downlink bandwidth part.
  • the first configuration includes first specific physical random access channel PRACH resources. That is, S111 in this embodiment may be: using the first specific PRACH resource to send the SI request message, and receiving the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the first configuration.
  • the first type of terminal can use the first specific PRACH resource to send the SI request message; the second type of terminal can use the second specific PRACH resource to send the SI request message; the first type of terminal uses the first specific PRACH The resource is different from the second specific PRACH resource used by the second type of terminal. Therefore, the network side device may determine, according to the received first specific PRACH resource or second specific PRACH resource, that the type of the terminal sending the SI request message is the first type terminal or the second type terminal.
  • the first initial downlink bandwidth part can be used by the second type of terminal and the first type of terminal, and the second initial downlink bandwidth part can only be used by the first type of terminal.
  • the first type of terminal may be a Redcap terminal
  • the second type of terminal may be an ordinary terminal
  • the terminal capability of the first type of terminal is different from that of the second type of terminal.
  • the first type of terminal and the second type of terminal use different PRACH resources; after the network side device receives the PRACH resource for sending the SI request message, it can determine to send the SI request message according to the PRACH resource corresponding to the SI request message. Whether the terminal of the request message is a first-type terminal or a second-type terminal. The corresponding network side device can determine according to the type of the terminal and based on the first configuration that the requested SI should be sent on the first initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part, corresponding to The requested SI is sent on the first initial downlink bandwidth part or the second initial downlink bandwidth part.
  • the terminal sending the SI request message is the first type of terminal, and it is determined based on the first configuration that the first initial downlink bandwidth part Whether the requested SI should be sent on the second initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part corresponds to sending the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part.
  • the network side device determines that the terminal type is the first type of terminal according to the received SI request message including the first specific PRACH resource, and determines that the requested SI should be sent in the first initial downlink bandwidth part based on the first configuration. In the case of , the network side device sends the requested SI to the first type of terminal in the first initial downlink bandwidth part, or, the network side device determines that the terminal type is the first type according to the received SI request message including the first specific PRACH resource A type of terminal, and when it is determined based on the first configuration that the requested SI should be sent in the second initial downlink bandwidth part, the network side device sends the requested SI to the first type of terminal in the second initial downlink bandwidth part.
  • the network side device transmits the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, and the transmission efficiency of the network side device can be improved, and the terminal of the first type resides in the second initial downlink bandwidth part
  • the requested SI can be received on the second initial downlink bandwidth part, avoiding the first type of terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink part, and saving the power consumption of the first type of terminal.
  • the first specific PRACH resource includes at least one of the following:
  • a specific preamble ; a specific PRACH transmission opportunity; a specific frequency resource; a specific initial uplink bandwidth part.
  • the first specific PRACH resource of the first type of terminal may include a specific preamble and/or a specific PRACH transmission opportunity and/or a specific frequency resource and/or a specific initial uplink bandwidth part.
  • FIG. 12 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the first type of terminal, and the method may include but not limited to the following steps:
  • S121 Receive first configuration information of a network side device; wherein, the configuration information includes a first specific PRACH resource and/or a second specific PRACH resource.
  • step S121 can be implemented alone, or can be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with step S101 and/or step S111 in the embodiments of the present disclosure.
  • the embodiment does not limit this.
  • the first configuration information includes the first specific PRACH resource
  • the network side device sends the first configuration information including the first specific PRACH resource to the first type of terminal to inform the first type of terminal to send the SI request message.
  • PRACH resources include the first specific PRACH resource
  • the first configuration information includes the second specific PRACH resource
  • the network side device sends the first configuration information including the second specific PRACH resource to the second type of terminal to inform the second type of terminal to send the SI request message.
  • PRACH resources include the second specific PRACH resource
  • the first configuration information includes the first specific PRACH resource and the second specific PRACH resource
  • the network side device sends the first configuration information including the first specific PRACH resource to the first type of terminal, and sends the first configuration information including the second specific PRACH resource.
  • the configuration information of the PRACH resource is sent to the second type of terminal, so as to respectively inform the first type of terminal and the second type of terminal of the PRACH resource used for sending the SI request message.
  • the network side device sends the first configuration information so that the first type of terminal determines the first specific PRACH resource; but this Those skilled in the art can understand that the first type of terminal can also determine the first specific PRACH resource in other ways, such as determining through a communication protocol, or receiving the first configuration information of the first specific PRACH resource from other devices, or pre-setting It exists in the first type of terminal, which is not limited in this embodiment of the present disclosure.
  • the second type of terminal may be many ways for the second type of terminal to determine the second specific PRACH resource, such as the previous example, which will not be repeated here.
  • FIG. 13 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a first type of terminal, and the method may include but 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 part or the second initial downlink bandwidth part corresponding to the second configuration.
  • the network side device receives the SI request message sent by the first type of terminal based on the second configuration, can determine that the terminal type is the first type of terminal, and determine that it should be sent on the first initial downlink bandwidth part The requested SI should still send the result of the requested SI on the second initial downlink bandwidth part.
  • the second configuration includes the third message Msg3 including the SI request message sent by the first type of terminal using the second initial uplink bandwidth part, that is, S131 in the embodiment may be: use the second initial uplink bandwidth
  • the bandwidth part sends a third message Msg3 including an SI request message, and the requested SI is received on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the second configuration.
  • the initial uplink bandwidth used by the first type of terminal and the second type of terminal to send the third message Msg3 may be different, wherein the first type of terminal may use the first initial uplink bandwidth or the second initial uplink bandwidth Send the third message Msg3, and the second type of terminal can only use the first initial uplink bandwidth part to send the third message Msg3. Therefore, according to the received third message Msg3 sent by the first type of terminal using the second initial uplink bandwidth part, the network side device can determine that the third message Msg3 is sent by the first type of terminal, thereby determining the type of the first type of terminal For the first type of terminal.
  • the first initial downlink bandwidth part can be used by the second type of terminal and the first type of terminal, and the second initial downlink bandwidth part can only be used by the first type of terminal.
  • the first type of terminal may be a Redcap terminal
  • the second type of terminal may be an ordinary terminal
  • the terminal capability of the first type of terminal is different from that of the second type of terminal.
  • the network side device receives the third message Msg3 including the SI request message sent by the second initial uplink bandwidth part used by the first type of terminal, and can determine that the terminal type is the first type of terminal, and the corresponding network side The device can determine whether the requested SI should be sent on the first initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part according to the type of the terminal and based on the second configuration.
  • the requested SI is sent on the bandwidth part or the second initial downlink bandwidth part.
  • the terminal type is the first type of terminal, and based on the second configuration, it is determined that the Whether to send the requested SI on the first initial downlink bandwidth part or the result of sending the requested SI on the second initial downlink bandwidth part, correspondingly send the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part .
  • the network side device determines that the terminal type is the first type terminal according to the received third message Msg3 including the SI request message sent by the second initial uplink bandwidth part used by the first type terminal, and determines based on the second configuration In the case that the requested SI should be sent in the first initial downlink bandwidth part, the network side device sends the requested SI to the first type of terminal in the first initial downlink bandwidth part, or, the network side device sends the requested SI according to the received information including the first An SI request message for a specific PRACH resource determines that the terminal type is the first type of terminal, and it is determined based on the second configuration that the requested SI should be sent in the second initial downlink bandwidth part, then the network side device will transmit the requested SI in the second initial downlink bandwidth In part, the requested SI is sent to the first type of terminal.
  • the network side device transmits the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, and the transmission efficiency of the network side device can be improved, and the terminal of the first type resides in the second initial downlink bandwidth part
  • the requested SI can be received on the second initial downlink bandwidth part, avoiding the first type of terminal switching back and forth between the first initial downlink bandwidth part and the second initial downlink part, and saving the power consumption of the first type of terminal.
  • the third message Msg3 includes an information field of the SI request message.
  • the third message Msg3 includes an information field of the SI request message.
  • FIG. 14 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a first type of terminal, and the method may include but 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.
  • the terminal of the first type when it randomly accesses the network-side device, it may send a random access request to the network-side device, thereby initiating random access to the network-side device.
  • step S141 may be implemented alone, or may be implemented in combination with any other steps in the embodiment of the present disclosure, for example, in combination with step S101 and/or step S111 and/or step S121 and /or step S131 is implemented together, which is not limited in this embodiment of the present disclosure.
  • FIG. 15 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by a first type of terminal, and the method may include but not limited to the following steps:
  • S151 Receive second configuration information of the network side device; wherein, the second configuration information includes first SI scheduling information, and the first SI scheduling information is used to configure the transmission of the requested SI only on the first initial downlink bandwidth part.
  • the network side device sends the second configuration information including the first SI scheduling information to the terminal, and the first SI scheduling information indicates that the terminal can only receive the requested SI on the first initial downlink bandwidth, and responds to the terminal
  • the network side device sends the requested SI to the terminal on the first initial downlink bandwidth, where the terminal includes a first-type terminal and a second-type terminal.
  • the terminals include a first-type terminal and a second-type terminal; the first-type terminal can be a Redcap terminal, the second-type terminal can be an ordinary terminal, and the terminal capability of the first-type terminal is the same as that of the second-type terminal. Terminal capabilities vary from terminal to terminal.
  • the first SI scheduling information is used to configure the transmission of the requested SI only on the first initial downlink bandwidth part. It can be understood that in this case, regardless of the type of the terminal Also the terminal of the second type can only receive the requested SI on the first initial downlink bandwidth part.
  • the first configuration information may be a SIB1 message, a system information block (system information block, SIB).
  • SIB system information block
  • the second configuration information includes the first SI scheduling information
  • the network side device sends the second configuration information including the first SI scheduling information to the terminal to inform the first type of terminal to receive the first initial downlink bandwidth part. SI is requested.
  • the network side device sends the second configuration information to make the first type of terminal determine the first SI scheduling information; but this Those skilled in the art can understand that the first type of terminal can also determine the first SI scheduling information in other ways, such as determining through a communication protocol, or receiving configuration information of the first SI scheduling information from other devices, or pre-existing the first SI scheduling information. In a type of terminal, the embodiment of the present disclosure does not limit this.
  • S151 can be implemented alone, or can be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S101 and/or S111 and/or S121 and/or S131 and and/or S141 are implemented together, which is not limited in this embodiment of the present disclosure.
  • FIG. 16 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is performed by the first type of terminal, and the method may include but not limited to the following steps:
  • S161 Receive second configuration information of the network side device; wherein, the second configuration information includes second SI scheduling information, and the second SI scheduling information is used to configure the requested SI transmission of the second type of terminal in the first initial downlink bandwidth part, And the requested SI of the terminal of the first type is transmitted on the second initial downlink bandwidth part.
  • the terminals include a first-type terminal and a second-type terminal; the first-type terminal can be a Redcap terminal, the second-type terminal can be an ordinary terminal, and the terminal capability of the first-type terminal is the same as that of the second-type terminal. Terminal capabilities vary from terminal to terminal.
  • the network side device sends second configuration information including second SI scheduling information to the terminal, and the second SI scheduling information indicates that the requested SI of the second type of terminal is transmitted in the first initial downlink bandwidth part, and The requested SI of the first type of terminal is transmitted on the second initial downlink bandwidth part, and in response to the SI request message sent by the first type of terminal, the network side device sends the requested SI on the second initial downlink bandwidth, and responds to the second type of For the SI request message sent by the terminal, the network side device sends the requested SI on the first initial downlink bandwidth.
  • the second configuration information is sent to the first type of terminal to inform the first type of terminal to receive the requested SI in the second initial bandwidth part; the second configuration information is sent to the second type of terminal to inform the first type of terminal The Type 2 terminal receives the requested SI in the first initial bandwidth part.
  • the network side device sends the second configuration information to make the first type of terminal and the second type
  • the terminal determines the second SI scheduling information; but those skilled in the art can 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 determining through a communication protocol, or receiving from other devices
  • the configuration information to the second SI scheduling information may be pre-stored in the first-type terminal and the second-type terminal, which is not limited in this embodiment of the present disclosure.
  • the network side device after receiving the SI request information sent by the terminal, determines that the type of the terminal is a first-type terminal, and sends the requested Si.
  • the network side device can only transmit the requested SI in the second initial downlink bandwidth part, avoiding that the network side device needs to transmit the requested SI in the first initial downlink bandwidth part and the second initial downlink bandwidth part respectively, and can improve the network side.
  • the transmission efficiency of the equipment, and the first type of terminal resides in the second initial downlink bandwidth part, and can receive the requested SI on the second initial downlink bandwidth part, avoiding the first type of terminal in the first initial downlink bandwidth part and the second Switching back and forth in the initial downlink part can save power consumption of the first type of terminal.
  • S161 may be implemented alone, or may be implemented in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S101 and/or S111 and/or S121 and/or S131 and /or S141 and/or S151 are implemented together, which is not limited in this embodiment of the present disclosure.
  • FIG. 17 is a flowchart of another system information transmission method provided by an embodiment of the present disclosure.
  • the method is executed by a first type of terminal, and the method may include but not limited to the following steps:
  • S171 Receive a random access response RAR message from a network side device; where the RAR message is received on the second initial downlink bandwidth part.
  • step S171 can be implemented alone, or can be implemented in combination with any other steps in the embodiment of the present disclosure, for example, in combination with step S101 and/or step S111 and/or S121 and/or in the embodiment of the present disclosure Or S131 and/or S141 and/or S151 and/or S161 are implemented together, which is not limited in this embodiment of the present disclosure.
  • the network side device receives the SI request message sent by the first type of terminal on the first specific PRACH resource, or, after receiving the random access message sent by the first type of terminal on the second initial uplink bandwidth part, input, and send a RAR message to the first type of terminal to inform that the first type of terminal can access the network side device.
  • the methods provided in the embodiments of the present disclosure are introduced from the perspectives of the network side device and the first type of terminal respectively.
  • the network-side device and the first-type terminal may include a hardware structure and a software module, and realize the above-mentioned various functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • Function A certain function among the above-mentioned functions may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 18 is a schematic structural diagram of a system information transmission device 1 provided by an embodiment of the present disclosure.
  • the system information transmission device 1 shown in FIG. 18 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 realize the sending function, the receiving module is used to realize the receiving function, and the sending and receiving module 11 can realize the sending function and/or the receiving function.
  • the system information transmission device 1 may be a terminal (such as the first type of terminal in the foregoing method embodiments), or a device in a terminal, or a device that can be matched with a terminal.
  • the system information transmission device 1 may be a network-side device, or a device in the network-side device, or a device that can be matched with the network-side device.
  • the system information transmission device 1 is a network side device:
  • the device includes: a transceiver module 11 configured to send the requested SI on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the configuration according to the configuration corresponding to the received system information SI request message sent by the terminal.
  • the system information transmission device 1 is a terminal (such as the first type of terminal in the foregoing method embodiments):
  • the device includes: a transceiver module 11, configured to send a system information SI request message, and according to the configuration corresponding to the SI request message, receive the received information on the first initial downlink bandwidth part or the second initial downlink bandwidth part corresponding to the configuration Request SI. .
  • system information transmission device 1 in the above embodiment, the specific manner in which each module executes operations has been described in detail in the embodiment related to the method, and will not be described in detail here.
  • the system information transmission device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the system information transmission methods provided in some of the above embodiments, which will not be repeated here.
  • FIG. 19 is a schematic structural diagram of a communication device 1000 provided by an embodiment of the present disclosure.
  • the communication device 1000 may be a network-side device, or a terminal (such as the first type of terminal in the foregoing method embodiments), or a chip, a chip system, or a processor that supports the network-side device to implement the above method, or It is a chip, a chip system, or a processor that supports the terminal to implement the above method.
  • the communication device 1000 may be used to implement the methods described in the foregoing method embodiments, and for details, refer to the descriptions in the foregoing method embodiments.
  • the communication device 1000 may be a network-side device, or a terminal, or a chip, a chip system, or a processor that supports the network-side device to implement the above method, or a chip, a chip system, or a chip that supports the terminal to implement the above method. processor etc.
  • the device can be used to implement the methods described in the above method embodiments, and for details, refer to the descriptions in the above method embodiments.
  • the communication device 1000 may include one or more processors 1001 .
  • the processor 1001 may be a general purpose processor or a special purpose processor or the like. For example, it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer programs , to process data for computer programs.
  • the communication device 1000 may further include one or more memories 1002, on which a computer program 1004 may be stored, and the memory 1002 executes the computer program 1004, so that the communication device 1000 executes the methods described in the foregoing method embodiments .
  • data may also be stored in the memory 1002 .
  • the communication device 1000 and the memory 1002 can be set separately or integrated together.
  • the communication device 1000 may further include a transceiver 1005 and an antenna 1006 .
  • the transceiver 1005 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1005 may include a receiver and a transmitter, and the receiver may be called a receiver or a receiving circuit for realizing a receiving function; the transmitter may be called a transmitter or a sending circuit for realizing a sending function.
  • 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 runs the code instructions to enable the communication device 1000 to execute the methods described in the foregoing method embodiments.
  • the communication device 1000 is a network-side device: the transceiver 1005 is used to execute S21 in FIG. 2 ; S31 in FIG. 3 ; S41 in FIG. 4 ; S51 in FIG. 5 ; S61 in FIG. 6 ; S71 in FIG. 7 ; S81 in Fig. 8; S91 in Fig. 9 .
  • the communication device 1000 is a terminal (such as the first type of terminal in the foregoing method embodiments): the transceiver 1005 is used to execute S101 in FIG. 10; S111 in FIG. 11; S121 in FIG. 12; S131 in FIG. 13; S141 in 14; S151 in FIG. 15; S161 in FIG. 16; S171 in FIG. 17.
  • the processor 1001 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits for realizing the functions of receiving and sending can be separated or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit may be used for signal transmission or transfer.
  • the processor 1001 may store a computer program 1003, and the computer program 1003 runs on the processor 1001 to enable the communication device 1000 to execute the methods described in the foregoing method embodiments.
  • the computer program 1003 may be solidified in the processor 1001, and in this case, the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit, and the circuit may implement the function of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure can be implemented on integrated circuits (integrated circuits, ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • 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 not be the same as that shown in Figure 19. limit.
  • a communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • a set of one or more ICs may also include storage components for storing data and computer programs;
  • ASIC such as modem (Modem);
  • FIG. 20 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • the chip 1100 includes a processor 1101 and an interface 1103 .
  • the number of processors 1101 may be one or more, and the number of interfaces 1103 may be more than one.
  • Interface 1103 configured to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to execute the method for transmitting system information as described in some of the above embodiments.
  • Interface 1103 configured to receive code instructions and transmit them to the processor.
  • the processor 1101 is configured to run code instructions to execute the method for transmitting system information as described in some of the above embodiments.
  • the chip 1100 also includes a memory 1102 for storing necessary computer programs and data.
  • An embodiment of the present disclosure also provides a system information transmission system, which includes the system information transmission device as a terminal (such as the first type of terminal in the foregoing method embodiment) in the embodiment of FIG. 18 and a system as a network side device
  • a system information transmission device or, the system includes a communication device serving as a terminal (such as the first type of terminal in the foregoing method embodiment) and a communication device serving as a network-side device in the aforementioned embodiment in FIG. 19 .
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any one of the above method embodiments are realized.
  • the present disclosure also provides a computer program product, which implements the functions of any one of the above method embodiments when the computer program product is executed by a computer.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs. When the computer program is loaded and executed on the computer, all or part of the processes or functions according to the embodiments of the present disclosure will be generated.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer program can be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program can be downloaded from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk (solid state disk, SSD)
  • At least one in the present disclosure can also be described as one or more, and a plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by "first”, “second”, “third”, “A”, “B”, “C” and “D”, etc.
  • the technical features described in the “first”, “second”, “third”, “A”, “B”, “C” and “D” have no sequence or order of magnitude among the technical features described.
  • each table in the present disclosure may be configured or predefined.
  • the values of the information in each table are just examples, and may be configured as other values, which are not limited in the present disclosure.
  • the corresponding relationship shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, for example, splitting, merging, and so on.
  • the names of the parameters shown in the titles of the above tables may also adopt other names understandable by the communication device, and the values or representations of the parameters may also be other values or representations understandable by the communication device.
  • other data structures can also be used, for example, arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables can be used wait.
  • Predefinition in the present disclosure can be understood as definition, predefinition, storage, prestorage, prenegotiation, preconfiguration, curing, or prefiring.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种系统信息传输方法和装置，该方法由网络侧设备执行，该方法包括：根据接收到的终端发送的系统信息SI请求消息对应的配置，在配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。由此，在第一类终端和第二类终端同时驻留在第一初始下行带宽部分，且on-demand SI在第一初始下行带宽部分上传输时，第一类终端和第二类终端都能监测到，避免了分别在两个初始下行带宽部分传输，能够提高网络侧设备的传输效率。且在第一类终端驻留在第二初始下行带宽部分时，on-demand SI在第二初始带宽部分上传输，避免了第一类终端在第一初始下行带宽部分和第二初始下行带宽部分来回切换，可以节省第一类终端的功耗。

Description

系统信息传输方法和装置 技术领域
本公开涉及通信技术领域，尤其涉及一种系统信息传输方法和装置。
背景技术
在目前的3GPP(third generation partnership project，第三代合作伙伴计划)标准化中，提出了新的终端类型叫做Reduced capability UE(user equipment，终端)或简称为NR-lite或Redcap终端，在一些场景下也称为能力缩减UE。
随着Redcap终端引入到NR(new radio，新空口)系统中，会针对Redcap终端配置单独的initial DL BWP(initial downlink bandwidth partinitial，初始下行带宽部分)和单独的initial UL BWP(initial uplink bandwidth partinitial，初始上行带宽部分)，而网络侧设备中原本还具有的一个initial DL BWP和一个initial UL BWP，这将会导致网络侧设备具有多个initial DL BWP和多个initial UL BWP，此时，如何进行按需on-demand SI(system information，系统信息)的传输是亟需解决的问题。
发明内容
本公开实施例提供一种系统信息传输方法和装置，以实现按需on-demandSI的传输。
第一方面，本公开实施例提供一种系统信息传输方法，该方法由网络侧设备执行，该方法包括：根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
在该技术方案中，根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI，由此，在第一类终端和第二类终端同时驻留在第一初始下行带宽部分，且on-demand SI在第一初始下行带宽部分上传输时，第一类终端和第二类终端都能监测到，避免了分别在两个初始下行带宽部分分别传输，能够提高网络侧设备的传输效率。而在第一类终端驻留在第二初始下行带宽部分时，on-demand SI在第二初始带宽部分上传输，避免了第一类终端在第一初始下行带宽部分和第二初始下行带宽部分来回切换，可以节省第一类终端的功耗。
第二方面，本公开实施例提供另一种系统信息传输方法，该方法由第一类终端执行，该方法包括：发送系统信息SI请求消息，根据所述SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
第三方面，本公开实施例提供一种系统信息传输装置，该系统信息传输装置具有实现上述第一方面所述的方法示例中网络侧设备的部分或全部功能，比如系统信息传输装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该系统信息传输装置的结构中可包括收发模块，收发模块用于支持系统信息传输装置与其他设备之间的通信。所述系统信息传输装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存系统信息传输装置必要的计算机程序和数据。
在一种实现方式中，所述系统信息传输装置包括：收发模块，用于根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
第四方面，本公开实施例提供一种另系统信息传输装置，该通信装置具有实现上述第二方面所述的方法中终端设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
作为示例，处理模块可以为处理器，收发模块可以为收发器或通信接口，存储模块可以为存储器。
在一种实现方式中，所述系统信息传输装置包括：收发模块，用于发送系统信息SI请求消息，根据所述SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
第五方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法。
第八方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第二方面所述的方法。
第九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种系统信息传输系统，该系统包括第三方面所述的系统信息传输装置以及第四方面所述的系统信息传输装置，或者，该系统包括第五方面所述的通信装置以及第六方面所述的通信装置，或者，该系统包括第七方面所述的通信装置以及第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置以及第十方面所述的通信装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种可读存储介质，用于储存为上述网络设备所用的指令，当所述 指令被执行时，使所述网络设备执行上述第二方面所述的方法。
第十四方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本公开提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持网络设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存网络设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种通信系统的架构图；
图2是本公开实施例提供的一种系统信息传输方法的流程图；
图3是本公开实施例提供的另一种系统信息传输方法的流程图；
图4是本公开实施例提供的又一种系统信息传输方法的流程图；
图5是本公开实施例提供的又一种系统信息传输方法的流程图；
图6是本公开实施例提供的又一种系统信息传输方法的流程图；
图7是本公开实施例提供的又一种系统信息传输方法的流程图；
图8是本公开实施例提供的又一种系统信息传输方法的流程图；
图9是本公开实施例提供的又一种系统信息传输方法的流程图；
图10是本公开实施例提供的又一种系统信息传输方法的流程图；
图11是本公开实施例提供的又一种系统信息传输方法的流程图；
图12是本公开实施例提供的又一种系统信息传输方法的流程图；
图13是本公开实施例提供的又一种系统信息传输方法的流程图；
图14是本公开实施例提供的又一种系统信息传输方法的流程图；
图15是本公开实施例提供的又一种系统信息传输方法的流程图；
图16是本公开实施例提供的又一种系统信息传输方法的流程图；
图17是本公开实施例提供的又一种系统信息传输方法的流程图；
图18是本公开实施例提供的一种系统信息传输装置的结构图；
图19是本公开实施例提供的一种通信装置的结构图；
图20是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
为了更好的理解本公开实施例公开的一种系统信息传输方法，下面首先对本公开实施例适用的通信系统进行描述。
请参见图1，图1为本公开实施例提供的一种通信系统10的架构示意图。该通信系统10可包括但不限于一个网络侧设备和一个终端，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络侧设备，两个或两个以上的终端。图1所示的通信系统10以包括一个网络侧设备101和一个终端102为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的网络侧设备101是网络侧的一种用于发射或接收信号的实体。例如，网络侧设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对网络侧设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的网络侧设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络侧设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端102是用户侧的一种用于接收或发射信号的实体，如手机。终端也可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本公开的实施例对终端所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
在LTE 4G系统中，为了支持物联网业务提出了MTC(machine type communication，机器型通信)，NB-IoT(narrow band-internet of things，窄带物联网)两大技术。这两大技术主要针对的是低速率，高时延等场景，比如抄表，环境监测等场景。
其中，NB-IoT目前最大只能支持几百k的速率，而MTC目前最大只能支持几M的速率。但同时 一方面，随着物联网业务的不断发展，比如视频监控，智能家居，可穿戴设备和工业传感监测等业务的普及，这些业务通常要求几十到100M的速率，并且对时延也有相对较高的要求，但是LTE中的MTC，NB-IoT技术很难满足要求。基于此，提出了在5G NR(新空口)中再设计一种新的终端用以来覆盖这种中端物联网设备的要求。在目前的3GPP(the 3rd generation partnership project，第三代合作伙伴项目)标准化中，这种新的终端类型叫做轻量化终端(Reduced capability，Redcap终端)或者简称为RedCap(轻量空口)。另一方面，同LTE中的物联网设备类似，基于5G系统中的RedCap通常需要满足如下要求：低造价，低复杂度；一定程度的覆盖增强；功率节省。
然而，目前的NR(新空口)是针对高速率低时延等高端终端设计的，当前的设计无法满足RedCap的上述要求。因此需要对目前的NR系统进行改造用以满足RedCap的要求。比如，为了满足低造价，低复杂度等要求，可以限制NR-IoT的RF(radio frequency，射频)带宽，比如限制到5M Hz或者10M Hz,或者限制RedCap的缓冲的大小，进而限制每次接收传输块的大小等等。针对功率节省，可能的优化方向是简化通信流程，减少RedCap终端检测下行控制信道的次数等。
相关技术中，NR系统中的按需on-demand SI的传输，在当前的系统信息传输中，有部分的系统信息可以设置为广播模式或者非广播模式，其中非广播模式的系统信息为on-demand SI。相关技术中，on-demand SI有如下两种申请方式：
方式一：网络设备会配置专用的PRACH(physical randomaccess channel，物理随机接入信道)资源，终端会发送特定的签到码preamble，从而获取所需的系统信息。
方式二：网络侧设备不会配置专用的PRACH资源，终端在第三消息(Msg3)发送on-demand SI的请求。
然而，随着Redcap终端引入到NR系统中，针对Redcap终端配置单独的initial DL BWP和单独的initial UL BWP，而网络侧设备中原本还具有的一个initial DL BWP和一个initial UL BWP，这将会导致网络侧设备具有多个initial DL BWP和多个initial UL BWP，此时，如何进行按需on-demand SI(system information，系统信息)的传输是亟需解决的问题。
基于此，本公开实施例中提供一种系统信息传输方法，以至少解决相关技术中针对Redcap终端配置单独的initial DL/UL BWP，网络侧设备中会存在多个initial DL/UL BWP，无法进行按需on-demand SI的传输的技术问题。
下面结合附图对本公开所提供的系统信息传输方法和装置进行详细地介绍。
请参见图2，图2是本公开实施例提供的一种系统信息传输方法的流程图。
如图2所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S21：根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
在一些可能的实现方式中，终端包括第一类终端和第二类终端；第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
其中，第一初始下行带宽部分可以由第一类终端和第二类终端使用，第二初始下行带宽部分仅能第一类终端使用。
在本公开实施例中，第一类终端发送的SI请求消息对应的配置与第二类终端发送的SI请求消息对应的配置不同，因此网络侧设备能够根据接收到的SI请求消息对应的配置，确定发送该SI请求消息的终端的类型，以及确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部 分上发送被请求SI的结果，从而网络侧设备可以根据终端的类型，以及确定的应该在第一初始下行带宽部分上发送被请求SI或者确定的应该在第二初始下行带宽部分上发送被请求SI的结果，在对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
示例性实施例中，在网络侧设备根据接收到的终端发送的SI请求消息对应的配置，确定终端的类型为第一类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分上向第一类终端发送被请求SI。
另一示例性实施例中，在网络侧设备根据接收到的终端发送的SI请求消息对应的配置，确定终端的类型为第一类终端，以及确定应该在第二初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第二初始下行带宽部分上向第一类终端发送被请求SI，从而，在确定应该在第二初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第二初始下行带宽部分上发送被请求SI，网络侧设备无需分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率；并且第一类终端可以驻留在第二初始下行带宽部分，在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
又一示例性实施例中，在网络侧设备根据接收到的终端发送的SI请求消息对应的配置，确定终端的类型为第二类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分上向第二类终端发送被请求SI。
通过实施本公开实施例，网络侧设备根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。由此，在第一类终端和第二类终端同时驻留在第一初始下行带宽部分，且on-demand SI在第一初始下行带宽部分上传输时，第一类终端和第二类终端都能监测到，避免了分别在两个初始下行带宽部分传输，能够提高网络侧设备的传输效率。且在第一类终端驻留在第二初始下行带宽部分时，on-demand SI在第二初始带宽部分上传输，避免了第一类终端在第一初始下行带宽部分和第二初始下行带宽部分来回切换，可以节省第一类终端的功耗。
请参见图3，图3是本公开实施例提供的另一种系统信息传输方法的流程图。
如图3所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S31：响应于接收到第一类终端基于第一配置发送的SI请求消息，在与第一配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
在本公开的实施例中，网络侧设备接收到第一类终端基于第一配置发送的SI请求消息，可以确定其终端类型为第一类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果。
在一些可能的实施方式中，第一配置包括第一特定物理随机接入信道PRACH资源。即，所述实施例的S31可以为：响应于接收到第一类终端使用第一特定PRACH资源发送的SI请求消息，在与第一配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
本公开的所有实施例中，第一类终端可以使用第一特定PRACH资源发送SI请求消息；第二类终端可以使用第二特定PRACH资源发送SI请求消息；第一类终端使用的第一特定PRACH资源与第二类终端使用的第二特定PRACH资源不同。从而，网络侧设备可以根据接收到的第一特定PRACH资源或者第二特定PRACH资源，以确定发送该SI请求消息的终端的类型为第一类终端或者第二类终端。
在一些可能的实施方式中，第一初始下行带宽部分可以由第二类终端和第一类终端使用，第二初始 下行带宽部分仅能由第一类终端使用。在一些可能的实施方式中，第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在上述实施例中，第一类终端和第二类终端使用不同的PRACH资源；网络侧设备在接收到发送SI请求消息的PRACH资源后，可以根据SI请求消息对应的PRACH资源，确定发送该SI请求消息的终端是第一类终端还是第二类终端。相应的网络侧设备能够根据终端的类型，以及基于第一配置确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果，对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。即，响应于接收到的SI请求消息是通过第一特定PRACH资源发送的，可以确定发送该SI请求消息的终端为第一类终端，并且基于第一配置确定了应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。
基于此，在网络侧设备根据接收到的包括第一特定PRACH资源的SI请求消息，确定终端类型为第一类终端，以及基于第一配置确定了应该在第一初始下行带宽部分发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分向第一类终端发送被请求SI，或者，在网络侧设备根据接收到的包括第一特定PRACH资源的SI请求消息，确定终端类型为第一类终端，以及基于第一配置确定了应该在第二初始下行带宽部分发送被请求SI的情况下，则网络侧设备在第二初始下行带宽部分上向第一类终端发送被请求SI。从而避免了网络侧设备分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率，并且，第一类终端驻留在第二初始下行带宽部分时，可以在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
在一些实施例中，第一特定PRACH资源包括以下至少一者：
特定的前导码preamble；特定的PRACH传输时机；特定的频率资源；特定的初始上行带宽部分。
本公开实施例中，第一类终端的第一特定PRACH资源可以包括特定的前导码preamble和/或特定的PRACH传输时机和/或特定的频率资源和/或特定的初始上行带宽部分。
请参见图4，图4是本公开实施例提供的又一种系统信息传输方法的流程图。
如图4所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S41：发送第一配置信息；其中，配置信息包括第一特定PRACH资源和/或第二特定PRACH资源。
需要说明的是，步骤S41可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的步骤S21和/或步骤S31一起被实施，本公开实施例并不对此做出限定。
在本公开的实施例中，第一配置信息可以为SIB1消息，系统信息块(system information block，SIB)。
上述实施例中，第一配置信息包括第一特定PRACH资源，网络侧设备将包含第一特定PRACH资源的第一配置信息发送至第一类终端，以告知第一类终端发送SI请求消息所使用的PRACH资源。
上述实施例中，第一配置信息包括第二特定PRACH资源，网络侧设备将包含第二特定PRACH资源的第一配置信息发送至第二类终端，以告知第二类终端发送SI请求消息所使用的PRACH资源。
上述实施例中，第一配置信息包括第一特定PRACH资源和第二特定PRACH资源，网络侧设备将包含第一特定PRACH资源的第一配置信息发送至第一类终端，以及将包含第二特定PRACH资源的配置信息发送至第二类终端，以分别告知第一类终端和第二类终端发送SI请求消息所使用的PRACH资 源。
当然，第一类终端确定第一特定PRACH资源的方式可以有很多种，上述实施例中是以网络侧设备通过发送第一配置信息的方式使得第一类终端确定第一特定PRACH资源；但是本领域内技术人员可以理解，第一类终端还可以通过其他方式确定第一特定PRACH资源，例如通过通信协议确定，或是从其他设备接收到第一特定PRACH资源的第一配置信息，或是预存在第一类终端中，本公开实施例并不对此作出限定。相应的，第二类终端确定第二特定PRACH资源的方式也可以有很多种，如前举例，在此不再赘述。
请参见图5，图5是本公开实施例提供的又一种系统信息传输方法的流程图。
如图5所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S51：响应于接收到的第一类终端基于第二配置发送的SI请求消息，在与第二配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
在本公开的实施例中，网络侧设备接收到第一类终端基于第二配置发送的SI请求消息，可以确定其终端类型为第一类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果。
在一些可能的实施方式中，第二配置包括第一类终端使用第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，即所述实施例的S41可以为：响应于接收到第一类终端使用第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，在与第二配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
本公开实施例中，第一类终端和第二类终端发送第三消息Msg3使用的初始上行带宽部分可以不同，其中，第一类终端可以使用第一初始上行带宽部分或者第二初始上行带宽部分发送第三消息Msg3，而第二类终端仅可以使用第一初始上行带宽部分发送第三消息Msg3。从而，网络侧设备根据接收到的第一类终端使用第二初始上行带宽部分发送的第三消息Msg3，可以确定第三消息Msg3为第一类终端发送的，从而可以确定第一类终端的类型为第一类终端。
在一些可能的实施方式中，第一初始下行带宽部分可以由第二类终端和第一类终端使用，第二初始下行带宽部分仅能由第一类终端使用。在一些可能的实施方式中，第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在上述实施例中，网络侧设备接收到第一类终端使用的第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，可以确定其终端类型为第一类终端，相应的网络侧设备能够根据终端的类型，以及基于第二配置确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果，对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。即，响应于接收到的第一类终端使用的第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，可以确定其终端类型为第一类终端，并且基于第二配置确定了应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果，对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。
基于此，在网络侧设备根据接收到的第一类终端使用的第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，确定终端类型为第一类终端，以及基于第二配置确定了应该在第一初始下行带宽部分发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分向第一类终端发送被请求SI，或者，在网络侧设备根据接收到的包括第一特定PRACH资源的SI请求消息，确定终端类型为第一类终 端，以及基于第二配置确定了应该在第二初始下行带宽部分发送被请求SI的情况下，则网络侧设备在第二初始下行带宽部分上向第一类终端发送被请求SI。从而避免了网络侧设备分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率，并且，第一类终端驻留在第二初始下行带宽部分时，可以在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
在一些实施例中，第三消息Msg3包括SI请求消息的信息域。
请参见图6，图6是本公开实施例提供的又一种系统信息传输方法的流程图。
如图6所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S61：接收第一类终端的第一消息；其中，第一消息为随机接入请求消息，在第二初始上行带宽部分接收随机接入。
可以理解的是，第一类终端在随机接入网络侧设备时，可以采用向网络侧设备发送随机接入请求的方式，从而向网络侧设备发起随机接入。
需要说明的是，步骤S61可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的步骤S21和/或步骤S31和/或步骤S41和/或步骤S51一起被实施，本公开实施例并不对此做出限定。
请参见图7，图7是本公开实施例提供的又一种系统信息传输方法的流程图。
如图7所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S71：发送第二配置信息；其中，第二配置信息包括第一SI调度信息，第一SI调度信息应用于配置被请求SI仅在第一初始下行带宽部分上的传输。
在本公开的实施例中，网络侧设备向终端发送包括第一SI调度信息的第二配置信息，第一SI调度信息指示终端仅能在第一初始下行带宽上接收被请求SI，响应于终端发送的SI请求消息，网络侧设备在第一初始下行带宽上向终端发送被请求SI，其中，终端包括第一类终端和第二类终端。
在一些可能的实现方式中，终端包括第一类终端和第二类终端；第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在本公开的实施例中，第一SI调度信息应用于配置被请求SI仅在第一初始下行带宽部分上的传输，可以理解的是，在此情况下，不论终端的类型为第一类终端还是第二类终端，都仅能在第一初始下行带宽部分上接收被请求SI。
在本公开的实施例中，第二配置信息可以为SIB1消息，系统信息块(system information block，SIB)。
上述实施例中，第二配置信息包括第一SI调度信息，网络侧设备将包含第一SI调度信息的第二配置信息发送至终端，以告知第一类终端在第一初始下行带宽部分上接收被请求SI。
当然，第一类终端确定第一SI调度信息的方式可以有很多种，上述实施例中是以网络侧设备通过发送第二配置信息的方式使得第一类终端确定第一SI调度信息；但是本领域内技术人员可以理解，第一类终端还可以通过其他方式确定第一SI调度信息，例如通过通信协议确定，或是从其他设备接收到第一SI调度信息的配置信息，或是预存在第一类终端中，本公开实施例并不对此作出限定。需要说明的是，S71可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21和/或S31和/或S41和/或S51和/或S61一起被实施，本公开实施例并不对此做出限定。
请参见图8，图8是本公开实施例提供的又一种系统信息传输方法的流程图。
如图8所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S81：发送第二配置信息；其中，第二配置信息包括第二SI调度信息，第二SI调度信息应用于配置第二类终端的被请求SI在第一初始下行带宽部分传输，以及第一类终端的被请求SI在第二初始下行带宽部分上传输。
在一些可能的实现方式中，终端包括第一类终端和第二类终端；第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在本公开的实施例中，网络侧设备向终端发送包括第二SI调度信息的第二配置信息，第二SI调度信息指示第二类终端的被请求SI在第一初始下行带宽部分传输，以及第一类终端的被请求SI在第二初始下行带宽部分上传输，响应于第一类终端发送的SI请求消息，网络侧设备在第二初始下行带宽上发送被请求SI，响应于第二类终端发送的SI请求消息，网络侧设备在第一初始下行带宽上发送被请求SI。
在本公开的实施例中，向第一类终端发送第二配置信息，以告知第一类终端在第二初始带宽部分接收被请求SI；向第二类终端发送第二配置信息，以告知第二类终端在第一初始带宽部分接收被请求SI。
当然，第一类终端和第二类终端确定第二SI调度信息的方式可以有很多种，上述实施例中是以网络侧设备通过发送第二配置信息的方式使得第一类终端和第二类终端确定第二SI调度信息；但是本领域内技术人员可以理解，第一类终端和第二类终端还可以通过其他方式确定第二SI调度信息，例如通过通信协议确定，或是从其他设备接收到第二SI调度信息的配置信息，或是预存在第一类终端和第二类终端中，本公开实施例并不对此作出限定。
在本公开的实施例中，在网络侧设备接收终端发送的SI请求信息之后，确定终端的类型为第一类终端的情况下，在第二初始下行带宽部分上向第一类终端发送被请求SI。由此，网络侧设备可以仅在第二初始下行带宽部分传输被请求SI，避免了网络侧设备需要分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率，且第一类终端驻留在第二初始下行带宽部分，可以在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
需要说明的是，S81可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S21和/或S31和/或S41和/或S51和/或S61和/或S71一起被实施，本公开实施例并不对此做出限定。
请参见图9，图9是本公开实施例提供的又一种系统信息传输方法的流程图。
如图9所示，该方法由网络侧设备执行，该方法可以包括但不限于如下步骤：
S91：向第一类终端发送随机接入响应RAR消息；其中，在第二初始下行带宽部分上发送RAR消息。
需要说明的是，步骤S91可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的步骤S21和/或步骤S31和/或S41和/或S51和/或S61和/或步骤S71和/或步骤S81一起被实施，本公开实施例并不对此做出限定。
在本公开的实施例中，网络侧设备接收第一类终端在第一特定PRACH资源上发送的SI请求消息，或者，在接收到第一类终端在第二初始上行带宽部分上发送的随机接入，向第一类终端发送RAR消息，以告知第一类终端可以接入网络侧设备。
请参见图10，图10是本公开实施例提供的又一种系统信息传输方法的流程图。
如图10所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S101：发送系统信息SI请求消息，根据发送系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
在一些可能的实现方式中，终端包括第一类终端和第二类终端；第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
其中，第一初始下行带宽部分可以由第一类终端和第二类终端使用，第二初始下行带宽部分仅能第一类终端使用。
在本公开实施例中，第一类终端发送的SI请求消息对应的配置与第二类终端发送的SI请求消息对应的配置不同，因此网络侧设备能够根据接收到的SI请求消息对应的配置，确定发送该SI请求消息的终端的类型，以及确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果，从而网络侧设备可以根据终端的类型，以及确定的应该在第一初始下行带宽部分上发送被请求SI或者确定的应该在第二初始下行带宽部分上发送被请求SI的结果，在对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
示例性实施例中，在网络侧设备根据接收到的终端发送的SI请求消息对应的配置，确定终端的类型为第一类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分上向第一类终端发送被请求SI。
另一示例性实施例中，在网络侧设备根据接收到的终端发送的SI请求消息对应的配置，确定终端的类型为第一类终端，以及确定应该在第二初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第二初始下行带宽部分上向第一类终端发送被请求SI，从而，在确定应该在第二初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第二初始下行带宽部分上发送被请求SI，网络侧设备无需分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率；并且第一类终端可以驻留在第二初始下行带宽部分，在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
又一示例性实施例中，在网络侧设备根据接收到的终端发送的SI请求消息对应的配置，确定终端的类型为第二类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分上向第二类终端发送被请求SI。
通过实施本公开实施例，网络侧设备根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。由此，在第一类终端和第二类终端同时驻留在第一初始下行带宽部分，且on-demand SI在第一初始下行带宽部分上传输时，第一类终端和第二类终端都能监测到，避免了分别在两个初始下行带宽部分分别传输，能够提高网络侧设备的传输效率。而在第一类终端驻留在第二初始下行带宽部分时，on-demand SI在第二初始带宽部分上传输，避免了第一类终端在第一初始下行带宽部分和第二初始下行带宽部分来回切换，可以节省第一类终端的功耗。
请参见图11，图11是本公开实施例提供的另一种系统信息传输方法的流程图。
如图11所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S111：基于第一配置发送SI请求消息，在与第一配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
在本公开的实施例中，网络侧设备接收到第一类终端基于第一配置发送的SI请求消息，可以确定其终端类型为第一类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初 始下行带宽部分上发送被请求SI的结果。
在一些可能的实施方式中，第一配置包括第一特定物理随机接入信道PRACH资源。即，所述实施例的S111可以为：使用第一特定PRACH资源发送SI请求消息，在与第一配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
本公开的所有实施例中，第一类终端可以使用第一特定PRACH资源发送SI请求消息；第二类终端可以使用第二特定PRACH资源发送SI请求消息；第一类终端使用的第一特定PRACH资源与第二类终端使用的第二特定PRACH资源不同。从而，网络侧设备可以根据接收到的第一特定PRACH资源或者第二特定PRACH资源，以确定发送该SI请求消息的终端的类型为第一类终端或者第二类终端。
在一些可能的实施方式中，第一初始下行带宽部分可以由第二类终端和第一类终端使用，第二初始下行带宽部分仅能由第一类终端使用。在一些可能的实施方式中，第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在上述实施例中，第一类终端和第二类终端使用不同的PRACH资源；网络侧设备在接收到发送SI请求消息的PRACH资源后，可以根据SI请求消息对应的PRACH资源，确定发送该SI请求消息的终端是第一类终端还是第二类终端。相应的网络侧设备能够根据终端的类型，以及基于第一配置确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果，对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。即，响应于接收到的SI请求消息是通过第一特定PRACH资源发送的，可以确定发送该SI请求消息的终端为第一类终端，并且基于第一配置确定了应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。
基于此，在网络侧设备根据接收到的包括第一特定PRACH资源的SI请求消息，确定终端类型为第一类终端，以及基于第一配置确定了应该在第一初始下行带宽部分发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分向第一类终端发送被请求SI，或者，在网络侧设备根据接收到的包括第一特定PRACH资源的SI请求消息，确定终端类型为第一类终端，以及基于第一配置确定了应该在第二初始下行带宽部分发送被请求SI的情况下，则网络侧设备在第二初始下行带宽部分上向第一类终端发送被请求SI。从而避免了网络侧设备分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率，并且，第一类终端驻留在第二初始下行带宽部分时，可以在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
在一些实施例中，第一特定PRACH资源包括以下至少一者：
特定的前导码preamble；特定的PRACH传输时机；特定的频率资源；特定的初始上行带宽部分。
本公开实施例中，第一类终端的第一特定PRACH资源可以包括特定的前导码preamble和/或特定的PRACH传输时机和/或特定的频率资源和/或特定的初始上行带宽部分。
请参见图12，图12是本公开实施例提供的又一种系统信息传输方法的流程图。
如图12所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S121：接收网络侧设备的第一配置信息；其中，配置信息包括第一特定PRACH资源和/或第二特定PRACH资源。
需要说明的是，步骤S121可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起 被实施，例如结合本公开实施例中的步骤S101和/或步骤S111一起被实施，本公开实施例并不对此做出限定。
上述实施例中，第一配置信息包括第一特定PRACH资源，网络侧设备将包含第一特定PRACH资源的第一配置信息发送至第一类终端，以告知第一类终端发送SI请求消息所使用的PRACH资源。
上述实施例中，第一配置信息包括第二特定PRACH资源，网络侧设备将包含第二特定PRACH资源的第一配置信息发送至第二类终端，以告知第二类终端发送SI请求消息所使用的PRACH资源。
上述实施例中，第一配置信息包括第一特定PRACH资源和第二特定PRACH资源，网络侧设备将包含第一特定PRACH资源的第一配置信息发送至第一类终端，以及将包含第二特定PRACH资源的配置信息发送至第二类终端，以分别告知第一类终端和第二类终端发送SI请求消息所使用的PRACH资源。
当然，第一类终端确定第一特定PRACH资源的方式可以有很多种，上述实施例中是以网络侧设备通过发送第一配置信息的方式使得第一类终端确定第一特定PRACH资源；但是本领域内技术人员可以理解，第一类终端还可以通过其他方式确定第一特定PRACH资源，例如通过通信协议确定，或是从其他设备接收到第一特定PRACH资源的第一配置信息，或是预存在第一类终端中，本公开实施例并不对此作出限定。相应的，第二类终端确定第二特定PRACH资源的方式也可以有很多种，如前举例，在此不再赘述。
请参见图13，图13是本公开实施例提供的又一种系统信息传输方法的流程图。
如图13所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S131：基于第二配置发送SI请求消息，在与第二配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
在本公开的实施例中，网络侧设备接收到第一类终端基于第二配置发送的SI请求消息，可以确定其终端类型为第一类终端，以及确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果。
在一些可能的实施方式中，第二配置包括第一类终端使用第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，即所述实施例的S131可以为：使用第二初始上行带宽部分发送包括SI请求消息的第三消息Msg3，在与第二配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
本公开实施例中，第一类终端和第二类终端发送第三消息Msg3使用的初始上行带宽部分可以不同，其中，第一类终端可以使用第一初始上行带宽部分或者第二初始上行带宽部分发送第三消息Msg3，而第二类终端仅可以使用第一初始上行带宽部分发送第三消息Msg3。从而，网络侧设备根据接收到的第一类终端使用第二初始上行带宽部分发送的第三消息Msg3，可以确定第三消息Msg3为第一类终端发送的，从而可以确定第一类终端的类型为第一类终端。
在一些可能的实施方式中，第一初始下行带宽部分可以由第二类终端和第一类终端使用，第二初始下行带宽部分仅能由第一类终端使用。在一些可能的实施方式中，第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在上述实施例中，网络侧设备接收到第一类终端使用的第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，可以确定其终端类型为第一类终端，相应的网络侧设备能够根据终端的类型，以及基于第二配置确定应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部 分上发送被请求SI的结果，对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。即，响应于接收到的第一类终端使用的第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，可以确定其终端类型为第一类终端，并且基于第二配置确定了应该在第一初始下行带宽部分上发送被请求SI还是应该在第二初始下行带宽部分上发送被请求SI的结果，对应的在第一初始下行带宽部分或第二初始下行带宽部分上发送被请求SI。
基于此，在网络侧设备根据接收到的第一类终端使用的第二初始上行带宽部分发送的包括SI请求消息的第三消息Msg3，确定终端类型为第一类终端，以及基于第二配置确定了应该在第一初始下行带宽部分发送被请求SI的情况下，网络侧设备在第一初始下行带宽部分向第一类终端发送被请求SI，或者，在网络侧设备根据接收到的包括第一特定PRACH资源的SI请求消息，确定终端类型为第一类终端，以及基于第二配置确定了应该在第二初始下行带宽部分发送被请求SI的情况下，则网络侧设备在第二初始下行带宽部分上向第一类终端发送被请求SI。从而避免了网络侧设备分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率，并且，第一类终端驻留在第二初始下行带宽部分时，可以在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
在一些实施例中，第三消息Msg3包括SI请求消息的信息域。
在一些实施例中，第三消息Msg3包括SI请求消息的信息域。
请参见图14，图14是本公开实施例提供的又一种系统信息传输方法的流程图。
如图14所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S141：发送第一消息；其中，第一消息为随机接入请求消息，在第二初始上行带宽部分接收随机接入。
可以理解的是，第一类终端在随机接入网络侧设备时，可以采用向网络侧设备发送随机接入请求的方式，从而向网络侧设备发起随机接入。
需要说明的是，步骤S141可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的步骤S101和/或步骤S111和/或步骤S121和/或步骤S131一起被实施，本公开实施例并不对此做出限定。
请参见图15，图15是本公开实施例提供的又一种系统信息传输方法的流程图。
如图15所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S151：接收网络侧设备的第二配置信息；其中，第二配置信息包括第一SI调度信息，第一SI调度信息应用于配置被请求SI仅在第一初始下行带宽部分上的传输。
在本公开的实施例中，网络侧设备向终端发送包括第一SI调度信息的第二配置信息，第一SI调度信息指示终端仅能在第一初始下行带宽上接收被请求SI，响应于终端发送的SI请求消息，网络侧设备在第一初始下行带宽上向终端发送被请求SI，其中，终端包括第一类终端和第二类终端。
在一些可能的实现方式中，终端包括第一类终端和第二类终端；第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在本公开的实施例中，第一SI调度信息应用于配置被请求SI仅在第一初始下行带宽部分上的传输，可以理解的是，在此情况下，不论终端的类型为第一类终端还是第二类终端，都仅能在第一初始下行带宽部分上接收被请求SI。
在本公开的实施例中，第一配置信息可以为SIB1消息，系统信息块(system information block，SIB)。
上述实施例中，第二配置信息包括第一SI调度信息，网络侧设备将包含第一SI调度信息的第二配置信息发送至终端，以告知第一类终端在第一初始下行带宽部分上接收被请求SI。
当然，第一类终端确定第一SI调度信息的方式可以有很多种，上述实施例中是以网络侧设备通过发送第二配置信息的方式使得第一类终端确定第一SI调度信息；但是本领域内技术人员可以理解，第一类终端还可以通过其他方式确定第一SI调度信息，例如通过通信协议确定，或是从其他设备接收到第一SI调度信息的配置信息，或是预存在第一类终端中，本公开实施例并不对此作出限定。需要说明的是，S151可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S101和/或S111和/或S121和/或S131和/或S141一起被实施，本公开实施例并不对此做出限定。
请参见图16，图16是本公开实施例提供的又一种系统信息传输方法的流程图。
如图16所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S161：接收网络侧设备的第二配置信息；其中，第二配置信息包括第二SI调度信息，第二SI调度信息应用于配置第二类终端的被请求SI在第一初始下行带宽部分传输，以及第一类终端的被请求SI在第二初始下行带宽部分上传输。
在一些可能的实现方式中，终端包括第一类终端和第二类终端；第一类终端可以为Redcap终端，第二类终端可以为普通的终端，第一类终端的终端能力与第二类终端的终端能力不同。
在本公开的实施例中，网络侧设备向终端发送包括第二SI调度信息的第二配置信息，第二SI调度信息指示第二类终端的被请求SI在第一初始下行带宽部分传输，以及第一类终端的被请求SI在第二初始下行带宽部分上传输，响应于第一类终端发送的SI请求消息，网络侧设备在第二初始下行带宽上发送被请求SI，响应于第二类终端发送的SI请求消息，网络侧设备在第一初始下行带宽上发送被请求SI。
在本公开的实施例中，向第一类终端发送第二配置信息，以告知第一类终端在第二初始带宽部分接收被请求SI；向第二类终端发送第二配置信息，以告知第二类终端在第一初始带宽部分接收被请求SI。
当然，第一类终端和第二类终端确定第二SI调度信息的方式可以有很多种，上述实施例中是以网络侧设备通过发送第二配置信息的方式使得第一类终端和第二类终端确定第二SI调度信息；但是本领域内技术人员可以理解，第一类终端和第二类终端还可以通过其他方式确定第二SI调度信息，例如通过通信协议确定，或是从其他设备接收到第二SI调度信息的配置信息，或是预存在第一类终端和第二类终端中，本公开实施例并不对此作出限定。
在本公开的实施例中，在网络侧设备接收终端发送的SI请求信息之后，确定终端的类型为第一类终端的情况下，在第二初始下行带宽部分上向第一类终端发送被请求SI。由此，网络侧设备可以仅在第二初始下行带宽部分传输被请求SI，避免了网络侧设备需要分别在第一初始下行带宽部分和第二初始下行带宽部分传输被请求SI，能够提高网络侧设备的传输效率，且第一类终端驻留在第二初始下行带宽部分，可以在第二初始下行带宽部分上接收被请求SI，避免了第一类终端在第一初始下行带宽部分和第二初始下行部分来回切换，可以节省第一类终端的功耗。
需要说明的是，S161可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S101和/或S111和/或S121和/或S131和/或S141和/或S151一起被实施，本公开实施例并不对此做出限定。
请参见图17，图17是本公开实施例提供的又一种系统信息传输方法的流程图。
如图17所示，该方法由第一类终端执行，该方法可以包括但不限于如下步骤：
S171：接收网络侧设备的随机接入响应RAR消息；其中，在第二初始下行带宽部分上接收RAR消息。
需要说明的是，步骤S171可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的步骤S101和/或步骤S111和/或S121和/或S131和/或S141和/或S151和/或S161一起被实施，本公开实施例并不对此做出限定。
在本公开的实施例中，网络侧设备接收第一类终端在第一特定PRACH资源上发送的SI请求消息，或者，在接收到第一类终端在第二初始上行带宽部分上发送的随机接入，向第一类终端发送RAR消息，以告知第一类终端可以接入网络侧设备。
上述本公开提供的实施例中，分别从网络侧设备、第一类终端的角度对本公开实施例提供的方法进行了介绍。为了实现上述本公开实施例提供的方法中的各功能，网络侧设备和第一类终端可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图18，为本公开实施例提供的一种系统信息传输装置1的结构示意图。图18所示的系统信息传输装置1可包括收发模块11。收发模块11可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块11可以实现发送功能和/或接收功能。
系统信息传输装置1可以是终端(如前述方法实施例中的第一类终端)，也可以是终端中的装置，还可以是能够与终端匹配使用的装置。或者，系统信息传输装置1可以是网络侧设备，也可以是网络侧设备中的装置，还可以是能够与网络侧设备匹配使用的装置。
系统信息传输装置1为网络侧设备：
该装置，包括：收发模块11，用于根据接收到的终端发送的系统信息SI请求消息对应的配置，在配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
系统信息传输装置1为终端(如前述方法实施例中的第一类终端)：
该装置，包括：收发模块11，用于发送系统信息SI请求消息，根据所述SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。。
关于上述实施例中的系统信息传输装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。本公开上述实施例中提供的系统信息传输装置1，与上面一些实施例中提供的系统信息传输方法取得相同或相似的有益效果，此处不再赘述。
请参见图19，图19是本公开实施例提供的一种通信装置1000的结构示意图。通信装置1000可以是网络侧设备，也可以是终端(如前述方法实施例中的第一类终端)，也可以是支持网络侧设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端实现上述方法的芯片、芯片系统、或处理器等。该通信装置1000可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以是网络侧设备，也可以是终端，也可以是支持网络侧设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行 控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，以使得通信装置1000执行上述方法实施例中描述的方法。可选的，所述存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行所述代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为网络侧设备：收发器1005用于执行图2中的S21；图3中的S31；图4中的S41；图5中的S51；图6中的S61；图7中的S71；图8中的S81；图9中的S91。
通信装置1000为终端(如前述方法实施例中的第一类终端)：收发器1005用于执行图10中的S101；图11中的S111；图12中的S121；图13中的S131；图14中的S141；图15中的S151；图16中的S161；图17中的S171。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是终端设备(如前述方法实施例中的终端设备)，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图19的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图20，为本公开实施例中提供的一种芯片的结构图。
芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中终端设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的系统信息传输方法。
对于芯片用于实现本公开实施例中网络侧设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的系统信息传输方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种系统信息传输的系统，该系统包括前述图18实施例中作为终端(如前述方法实施例中的第一类终端)的系统信息传输装置和作为网络侧设备的系统信息传输装置，或者，该系统包括前述图19实施例中作为终端(如前述方法实施例中的第一类终端)的通信装置和作为网络侧设备的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (32)

  1. 一种系统信息传输方法，其特征在于，所述方法由网络侧设备执行，所述方法包括：
    根据接收到的终端发送的系统信息SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
  2. 根据权利要求1所述的方法，其特征在于，所述配置包括第一配置；所述方法，还包括：
    响应于接收到第一类终端基于第一配置发送的SI请求消息，在与第一配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
  3. 根据权利要求2所述的方法，其特征在于，所述第一配置包括第一特定物理随机接入信道PRACH资源和/或第二特定PRACH资源；其中，所述第一类终端使用的所述第一特定PRACH资源与第二类终端使用的所述第二特定PRACH资源不同；所述第一类终端的终端能力与所述第二类终端的终端能力不同；所述响应于接收到的第一类终端基于第一配置发送的SI请求消息，包括：
    响应于接收到所述第一类终端使用第一特定PRACH资源发送的所述SI请求消息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一特定PRACH资源包括以下至少一者：
    特定的前导码preamble；
    特定的PRACH传输时机；
    特定的频率资源；
    特定的初始上行带宽部分。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法，还包括：
    发送第一配置信息；其中，所述第一配置信息包括所述第一特定PRACH资源和/或所述第二特定PRACH资源。
  6. 根据权利要求1所述的方法，其特征在于，所述配置包括第二配置；所述方法，还包括：
    响应于接收到第一类终端基于第二配置发送的SI请求消息，在与第二配置相对应的第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
  7. 根据权利要求6所述的方法，其特征在于，所述响应于接收到第一类终端基于第二配置发送的SI请求消息，包括：
    响应于接收到所述第一类终端使用第二初始上行带宽部分发送的包括SI请求消息的第三消息。
  8. 根据权利要求7所述的方法，其特征在于，所述第三消息包括所述SI请求消息的信息域。
  9. 根据权利要求7或8所述的方法，其特征在于，所述方法，还包括：
    接收所述第一类终端的第一消息；其中，所述第一消息为随机接入请求消息，在所述第二初始上行 带宽部分接收所述随机接入。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述方法，还包括：
    发送第二配置信息；其中，所述第二配置信息包括第一SI调度信息；所述第一SI调度信息应用于配置所述被请求SI在第一初始带宽部分上的传输。
  11. 根据权利要求1至9中任一项所述的方法，其特征在于，所述方法，还包括：
    发送第二配置信息；其中，所述第二配置信息包括第二SI调度信息；所述第二SI调度信息应用于配置第二类终端的被请求SI在第一初始下行带宽部分传输，以及第一类终端的被请求SI在第二初始下行带宽部分上传输。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法，还包括：
    向所述第一类终端发送随机接入响应RAR消息；其中，在第二初始下行带宽部分上发送所述RAR消息。
  13. 一种系统信息传输方法，其特征在于，所述方法由第一类终端执行，所述方法包括：
    发送系统信息SI请求消息，根据所述SI请求消息对应的配置，在所述配置对应的第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
  14. 根据权利要求13所述的方法，其特征在于，所述配置包括第一配置；所述方法，还包括：
    基于第一配置发送系统信息SI请求消息，在与所述第一配置相对应的所述第一初始下行带宽部分或者所述第二初始下行带宽部分上发送所述被请求SI。
  15. 根据权利要求14所述的方法，其特征在于，所述第一配置包括第一特定物理随机接入信道PRACH资源和/或第二特定PRACH资源；其中，所述第一类终端使用的所述第一特定PRACH资源与第二类终端使用的所述第二特定PRACH资源不同；所述第一类终端的终端能力与所述第二类终端的终端能力不同；所述响应于接收到的第一类终端基于第一配置发送的SI请求消息，包括：
    使用所述第一特定PRACH资源发送所述SI请求消息。
  16. 根据权利要求15所述的方法，其特征在于，所述第一特定PRACH资源包括以下至少一者：
    特定的前导码preamble；
    特定的PRACH传输时机；
    特定的频率资源；
    特定的初始上行带宽部分。
  17. 根据权利要求15或16所述的方法，其特征在于，所述方法，还包括：
    接收网络侧设备的第一配置信息；其中，所述第一配置信息包括所述第一特定PRACH资源和/或所述第二特定PRACH资源。
  18. 根据权利要求13所述的方法，其特征在于，所述配置包括第二配置；所述方法，还包括：
    基于第二配置发送SI请求消息，在与所述第二配置相对应的所述第一初始下行带宽部分或者所述第二初始下行带宽部分上发送所述被请求SI。
  19. 根据权利要求18所述的方法，其特征在于，所述基于第二配置发送的SI请求消息，包括：
    使用第二初始上行带宽部分发送包括SI请求消息的第三消息。
  20. 根据权利要求19所述的方法，其特征在于，所述第三消息包括所述SI请求消息的信息域。
  21. 根据权利要求19或20所述的方法，其特征在于，所述方法，还包括：
    发送第一消息；其中，所述第一消息为随机接入请求消息，在所述第二初始上行带宽部分发送所述随机接入。
  22. 根据权利要求13至21中任一项所述的方法，其特征在于，所述方法，还包括：
    接收网络侧设备的第二配置信息；其中，所述第二配置信息包括第一SI调度信息；所述第一SI调度信息应用于配置所述被请求SI在第一初始带宽部分上的传输。
  23. 根据权利要求13至21中任一项所述的方法，其特征在于，所述方法，还包括：
    接收网络侧设备的第二配置信息；其中，所述第二配置信息包括第二SI调度信息；所述第二SI调度信息应用于配置第二类终端的被请求SI在第一初始下行带宽部分传输，以及第一类终端的被请求SI在第二初始下行带宽部分上传输。
  24. 根据权利要求22或23所述的方法，其特征在于，所述方法，还包括：
    接收网络侧设备的随机接入响应RAR消息；其中，在第二初始下行带宽部分上接收所述RAR消息。
  25. 一种系统信息传输装置，其特征在于，包括：
    收发模块，用于响应于第一类终端发送的系统信息SI请求消息，在第一初始下行带宽部分或者第二初始下行带宽部分上发送被请求SI。
  26. 一种系统信息传输装置，其特征在于，包括：
    收发模块，用于向网络侧设备发送系统信息SI请求消息，在第一初始下行带宽部分或者第二初始下行带宽部分上接收被请求SI。
  27. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至12中任一项所述的方法。
  28. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求13至24中任一项所述的方法。
  29. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至12中任一项所述的方法。
  30. 一种通信装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求13至24中任一项所述的方法。
  31. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至12中任一项所述的方法被实现。
  32. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求13至24中任一项所述的方法被实现。
PCT/CN2021/119138 2021-09-17 2021-09-17 系统信息传输方法和装置 WO2023039852A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/119138 WO2023039852A1 (zh) 2021-09-17 2021-09-17 系统信息传输方法和装置
CN202180002825.5A CN113940128A (zh) 2021-09-17 2021-09-17 系统信息传输方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/119138 WO2023039852A1 (zh) 2021-09-17 2021-09-17 系统信息传输方法和装置

Publications (1)

Publication Number Publication Date
WO2023039852A1 true WO2023039852A1 (zh) 2023-03-23

Family

ID=79289386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/119138 WO2023039852A1 (zh) 2021-09-17 2021-09-17 系统信息传输方法和装置

Country Status (2)

Country Link
CN (1) CN113940128A (zh)
WO (1) WO2023039852A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023151065A1 (zh) * 2022-02-13 2023-08-17 北京小米移动软件有限公司 初始带宽部分配置方法及装置、初始带宽部分切换方法及装置
CN114731713A (zh) * 2022-02-14 2022-07-08 北京小米移动软件有限公司 一种监测下行带宽部分的方法、装置及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112075113A (zh) * 2020-08-06 2020-12-11 北京小米移动软件有限公司 资源配置方法、装置、通信设备和存储介质
WO2021161622A1 (ja) * 2020-02-13 2021-08-19 日本電気株式会社 Ｒａｎノード、無線端末、及びこれらのための方法
WO2021181001A1 (en) * 2020-03-12 2021-09-16 Nokia Technologies Oy Enabling access for a reduced capability new radio (nr) device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021161622A1 (ja) * 2020-02-13 2021-08-19 日本電気株式会社 Ｒａｎノード、無線端末、及びこれらのための方法
WO2021181001A1 (en) * 2020-03-12 2021-09-16 Nokia Technologies Oy Enabling access for a reduced capability new radio (nr) device
CN112075113A (zh) * 2020-08-06 2020-12-11 北京小米移动软件有限公司 资源配置方法、装置、通信设备和存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
XIAOMI: "Discussion on the remaining issues of the higher layer related topics for RedCap", 3GPP DRAFT; R1-2107930, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210816 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052033722 *

Also Published As

Publication number Publication date
CN113940128A (zh) 2022-01-14

Similar Documents

Publication Publication Date Title
WO2023039852A1 (zh) 系统信息传输方法和装置
WO2023102743A1 (zh) 接入控制方法及装置
WO2024050776A1 (zh) 一种信息确定方法/装置/设备及存储介质
WO2023150988A1 (zh) 一种位置信息的上报方法及其装置
WO2023087156A1 (zh) 一种新空口和新空口侧行链路切换的方法及装置
WO2023019410A1 (zh) 一种传输下行控制信息dci的方法及其装置
CN115280875A (zh) 全球导航卫星系统gnss定位测量方法及装置
WO2023283782A1 (zh) 一种信道状态反馈的方法及其装置
WO2024036519A1 (zh) 一种侧行链路pdcp复用的激活方法及装置
WO2023108369A1 (zh) 资源确定方法和装置
WO2023142085A1 (zh) 寻呼触发方法及装置
WO2023035202A1 (zh) 一种跟踪参考信号周期的确定方法及其装置
WO2023010429A1 (zh) 一种带宽部分的同步方法及其装置
WO2023115578A1 (zh) 一种混合自动重传请求状态增强方法及其装置
WO2023029058A1 (zh) 一种时间偏移量的确定方法及其装置
WO2023015457A1 (zh) 传输增强的方法和装置
WO2022266963A1 (zh) 资源分配方法及其装置
WO2023130321A1 (zh) 一种数据压缩方法和装置
WO2024045078A1 (zh) 一种终端处理能力的上报方法、数据处理方法及其装置
CN115191145B (zh) 一种多prach传输方法及其装置
WO2023044620A1 (zh) 一种传输配置指示状态的确定方法及其装置
WO2023065326A1 (zh) 一种通信模式的确定方法及其装置
WO2023173257A1 (zh) 一种请求系统信息的方法及其装置
WO2024045042A1 (zh) 一种能力交互触发方法/装置/设备及存储介质
WO2023044807A1 (zh) 一种控制信令的执行方法及其装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21957134

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2021957134

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021957134

Country of ref document: EP

Effective date: 20240417