WO2021233320A1 - 一种通信方法以及相关装置 - Google Patents

一种通信方法以及相关装置 Download PDF

Info

Publication number
WO2021233320A1
WO2021233320A1 PCT/CN2021/094486 CN2021094486W WO2021233320A1 WO 2021233320 A1 WO2021233320 A1 WO 2021233320A1 CN 2021094486 W CN2021094486 W CN 2021094486W WO 2021233320 A1 WO2021233320 A1 WO 2021233320A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
sib
parameter
changed
system information
Prior art date
Application number
PCT/CN2021/094486
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 华为技术有限公司
Publication of WO2021233320A1 publication Critical patent/WO2021233320A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and related devices.
  • the terminal equipment and the access network equipment on the uplink and downlink according to the 3rd generation partnership project established various protocol layers through the radio bearer (Radio bearer, RB) transmits various data, such as transmitting control signaling on a signaling radio bearer or transmitting service data on a data radio bearer.
  • These protocol layers include the physical (PHY) layer, the media access control (MAC) layer, the radio link control (RLC), and the packet data convergence protocol (PDCP) layer.
  • the radio resource control (radio resource control, RRC) layer etc.
  • the access network equipment can be further divided into a centralized unit (CU) and a distributed unit (DU) architecture according to the protocol layer.
  • the CU and DU include control plane connection and user plane connection.
  • the user The plane connection is also called a user plane (UP) tunnel.
  • a user plane tunnel is determined by an uplink tunnel endpoint on the CU and a downlink tunnel endpoint on the DU.
  • the CU is used to implement the functions of the PDCP layer and the RRC layer
  • the DU is used to implement the functions of the PHY layer, the MAC layer and the RLC layer.
  • SI System information
  • SIB master information block
  • SIB system information blocks
  • SIB1 is generated in the DU, and the CU does not set the parameters associated with the SIB; other SIBs (such as SIB2-9 in 5G) are generated in the CU, and the CU sets the parameters associated with the SIB.
  • the CU can set the SIB and its associated parameters.
  • the parameter tells DU. With the evolution of communication technology, a new type of SIB appears. The generation and parameter setting of this type of SIB are different from the above two types of SIBs. This type of SIB is generated in the DU. How to deal with this type of SIB is worthwhile Questions to consider.
  • the embodiment of the present application provides a communication method.
  • an embodiment of the present application proposes a communication method, including:
  • the distributed unit DU sends a first message to the centralized unit CU.
  • the first message carries a system information block SIB, and the SIB is generated by the DU.
  • the DU receives a second message sent by the CU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the system information block may be called "SIBx.”
  • the distributed unit generating the system information block "SIBx" may be: the distributed unit is responsible for encoding and generating the system information block SIBx (the gNB-DU is responsible for the encoding of SIBx).
  • the system information block may be "SIB10".
  • the first message is an F1 setup request message (F1 setup request).
  • the system information block is carried in the first cell of the F1 establishment request message.
  • the first information element may be: a gNB-DU System information (gNB-DU System information) information element.
  • gNB-DU System information gNB-DU System information
  • Each first information element corresponds to a cell, and is used to indicate the master information block message and the system information block message of the cell.
  • the first message is a newly defined F1 message, which is dedicated to bear the foregoing system information block x message (SIBx message).
  • the embodiment of the present application provides a communication device.
  • the distributed unit reports the generated system information block to the centralized unit, and the centralized unit can learn that the system information block has been Generated so that parameters can be configured for the system information block.
  • This method is suitable for the system information block generated in the distributed unit.
  • the system information block is configured by a centralized unit. By using this method, the distributed unit can obtain the configuration parameters of the system information block, so that the system information block can be broadcasted in the cell. The configuration parameters of the system information block.
  • the parameter includes at least one of the following: a value tag (valueTag) or an area scope (areaScope).
  • a value tag valueTag: used to identify whether the SIB has changed, and the DU uses the value tag to inform the user equipment whether the SIB associated with the value tag has changed.
  • the value label is an integer type, and the value range of the value label is ⁇ 0-31 ⁇ . When the SIB changes, the value label is sequentially accumulated.
  • the value label of SIB2 is 0, when the SIB2 changes, the value label changes from 0 to 1.
  • the user equipment can determine that the SIB2 has changed according to the value tag.
  • AreaScope used to identify whether the SIB is area-specific or cell-specific.
  • the parameter may be a value label and/or an area location. This parameter can also include other parameters, which are not limited here.
  • the method further includes: the DU configures the relevant parameters of the SIB based on the parameters.
  • the DU configures the relevant parameters of the SIB based on the parameter, so that the user equipment in the DU can learn whether the SIB has changed, and/or the DU can learn the SIB's Range of use.
  • the method further includes: the DU receives a third message sent by the CU, the third message carrying the changed parameter, the changed parameter and The SIB is associated.
  • the centralized unit sends a third message to the distributed unit to configure the changed parameters to the system information block in the distributed unit.
  • the system information block may be a changed system information block, or the system information block may be The unchanged system information block.
  • the centralized unit may configure the changed parameters to the system information block in the distributed unit by sending a third message to the distributed unit. This makes the solution applicable to multiple scenarios and improves the flexibility of implementation.
  • the method before the DU receives the third message sent by the CU, the method further includes: after the system information block in the distributed unit is changed, the DU reports to the CU A fourth message is sent, the fourth message carries the changed SIB, and the changed SIB is generated by the DU.
  • the fourth message carries indication information of the changed system information block.
  • the indication information of the changed system information block is used to indicate that the distributed unit has generated the changed system information block.
  • the distributed unit may send a fourth message to the centralized unit, the fourth message indicating the changed system information block or the changed system information block information.
  • the distributed unit can notify the centralized unit that the system information block has changed through a variety of methods. Improved the flexibility of the solution.
  • the first message is an F1 establishment request message, and in another optional implementation, the first message is a newly defined F1 message, It is dedicated to bear the system information block x message (SIBx message).
  • the first message is an uplink system information block transfer (UL SIB transfer) message; the second message is an F1 establishment response message.
  • the second message is a newly defined F1 message, which is dedicated to bear the parameters associated with the aforementioned SIBx.
  • the second message is a downlink system information block transfer (DL SIB transfer) message.
  • the third message is a DU configuration update message.
  • the third message is a newly defined F1 message, It is dedicated to bear SIBx related parameters;
  • the fourth message is a DU configuration update confirmation message.
  • the fourth message is a newly defined F1 message, which is dedicated to bear the SIBx message.
  • an embodiment of the present application proposes a communication method, including:
  • the centralized unit CU receives the first message sent by the distributed unit DU, the first message carries the system information block SIB, and the SIB is generated by the DU.
  • the system information block is called "SIBx"; the CU sends a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the distributed unit generating the system information block "SIBx" may be: the distributed unit is responsible for encoding and generating the system information block SIBx (the gNB-DU is responsible for the encoding of SIBx).
  • the system information block may be "SIB10".
  • the first message is an F1 setup request message (F1 setup request).
  • the system information block is carried in the first cell of the F1 establishment request message.
  • the first information element may be: a gNB-DU System information (gNB-DU System information) information element.
  • gNB-DU System information gNB-DU System information
  • Each first information element corresponds to a cell, and is used to indicate the master information block message and the system information block message of the cell.
  • the first message is a newly defined F1 message, which is dedicated to bear the foregoing system information block x message (SIBx message).
  • the embodiment of the application provides a communication device.
  • a system information block is generated in a distributed unit
  • the distributed unit reports the generated or changed system information block to the centralized unit, and the centralized unit can obtain the information according to the report.
  • the system information block has been generated so that parameters can be configured for the system information block.
  • This method is suitable for the system information block generated in the distributed unit.
  • the system information block is configured by a centralized unit. By using this method, the distributed unit can obtain the configuration parameters of the system information block, so that the system information block can be broadcasted in the cell.
  • the configuration parameters of the system information block is provided.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the second message carries the value label, or the second message carries the value label and the area range, or the second message carries the area range.
  • a value tag (valueTag): used to identify whether the SIB has changed, and the DU uses the value tag to inform the user equipment whether the SIB associated with the value tag has changed.
  • the value label is an integer type, and the value range of the value label is ⁇ 0-31 ⁇ . When the SIB changes, the value label is sequentially accumulated.
  • the value label of SIB2 is 0, when the SIB2 changes, the value label changes from 0 to 1.
  • the user equipment can determine that the SIB2 has changed according to the value tag.
  • AreaScope used to identify whether the SIB is area-specific or cell-specific.
  • the parameter may be a value label and/or an area location. This parameter can also include other parameters, which are not limited here.
  • the method further includes: the CU sends a third message to the DU, the third message carrying the changed parameter, the changed parameter and the SIB association.
  • the centralized unit sends a third message to the distributed unit to configure the changed parameters to the system information block in the distributed unit.
  • the system information block may be a changed system information block, or the system information block may be The unchanged system information block.
  • the centralized unit may configure the changed parameters to the system information block in the distributed unit by sending a third message to the distributed unit. This makes the solution applicable to multiple scenarios and improves the flexibility of implementation.
  • the method further includes: the CU receives a fourth message sent by the DU, the fourth message carrying the changed SIB, and the changed SIB is transferred from The DU is generated.
  • the fourth message carries indication information of the changed system information block.
  • the indication information of the changed system information block is used to indicate that the distributed unit has generated the changed system information block.
  • the distributed unit may send a fourth message to the centralized unit, the fourth message indicating the changed system information block or the changed system information block information.
  • the distributed unit can notify the centralized unit that the system information block has changed through a variety of methods. Improved the flexibility of the solution.
  • the first message is an F1 establishment request message, and in another optional implementation manner, the first message is a newly defined F1 message, It is dedicated to bear the system information block x message (SIBx message).
  • the first message is an uplink system information block transfer (UL SIB transfer) message; the second message is an F1 establishment response message.
  • the second message is a newly defined F1 message, which is dedicated to bear the parameters associated with the aforementioned SIBx.
  • the second message is a downlink system information block transfer (DL SIB transfer) message.
  • the third message is a DU configuration update message.
  • the third message is a newly defined F1 message, It is dedicated to bear SIBx related parameters;
  • the fourth message is a DU configuration update confirmation message.
  • the fourth message is a newly defined F1 message, which is dedicated to bear the SIBx message.
  • an embodiment of the present application proposes a communication method, including: first, a distributed unit generates a system information block.
  • the system information block is called "SIBx".
  • the system information block may be "SIB10" in the 5G-NR system.
  • the distributed unit sends a fifth message to the centralized unit, and the centralized unit manages the distributed unit.
  • the DU receives a second message sent by the CU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the fifth message carries indication information of the system information block.
  • the indication information of the system information block is used to indicate that the distributed unit has generated the system information block.
  • the fifth message is an F1 setup request message (F1 setup request).
  • the indication information of the system information block is carried in the fifth cell of the F1 establishment request message.
  • the fifth information element may be: gNB-DU System information (gNB-DU System information) information element.
  • Each first information element corresponds to a cell and is used to represent the main information block and system information block of the cell.
  • the indication information of the system information block may be a certain field. For example, the field is "SIBx". When the field "SIBx" is included in the fifth message, it indicates the distribution The formula unit generates the system information block.
  • the indication information of the system information block may also be bits. For example, when a certain bit in the fifth message is "01", it indicates that the distributed unit has generated the system information block.
  • the fifth message may be an F1 establishment request message, and the fifth message may also be other messages, which is not limited here.
  • the embodiment of the present application provides a communication method.
  • the distributed unit reports the indication information of the system information block to the centralized unit, so that the centralized unit can know that the distributed unit generates The system information block, and thus the centralized unit, configures parameters for the system information block.
  • the communication resources between the centralized unit and the distributed unit can be effectively saved.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the second message carries the value label, or the second message carries the value label and the area range, or the second message carries the area range.
  • a value tag (valueTag): used to identify whether the SIB has changed, and the DU uses the value tag to inform the user equipment whether the SIB associated with the value tag has changed.
  • the value label is an integer type, and the value range of the value label is ⁇ 0-31 ⁇ . When the SIB changes, the value label is sequentially accumulated.
  • the value label of SIB2 is 0, when the SIB2 changes, the value label changes from 0 to 1.
  • the user equipment can determine that the SIB2 has changed according to the value tag.
  • AreaScope used to identify whether the SIB is area-specific or cell-specific.
  • the parameter may be a value label and/or an area location. This parameter can also include other parameters, which are not limited here.
  • the method further includes: the DU configures the relevant parameters of the SIB based on the parameters.
  • the DU configures the relevant parameters of the SIB based on the parameter, so that the user equipment in the DU can learn whether the SIB has changed, and/or the DU can learn the SIB's Range of use.
  • the method further includes: the DU receives a third message sent by the CU, the third message carrying the changed parameter, the changed parameter and The SIB is associated.
  • the centralized unit sends a third message to the distributed unit to configure the changed parameters to the system information block in the distributed unit.
  • the system information block may be a changed system information block, or the system information block may be The unchanged system information block.
  • the centralized unit may configure the changed parameters to the system information block in the distributed unit by sending a third message to the distributed unit. This makes the solution applicable to multiple scenarios and improves the flexibility of implementation.
  • the method before the DU receives the third message sent by the CU, the method further includes: the DU sends a sixth message to the CU, the sixth message carrying a change
  • the indication information of the SIB after the change, and the SIB after the change is generated by the DU.
  • the indication information of the changed system information block may be a certain field, for example, the field is "SIBx-changed", when the sixth message includes the field "SIBx-changed" ", it indicates that the system information block generated by the distributed unit has changed.
  • the indication information of the changed system information block may also be bits.
  • the sixth message when a bit in the sixth message is "011", it indicates that the system information block generated by the distributed unit has occurred. change.
  • the sixth message may be an F1 establishment request message, and the sixth message may also be other messages, which is not limited here.
  • the distributed unit can notify the centralized unit that the system information block has changed through a variety of methods. Improved the flexibility of the solution. In addition, the communication resources between the centralized unit and the distributed unit can be effectively saved.
  • the fifth message is an F1 establishment request message; the second message is an F1 establishment response message.
  • the third message is a DU configuration update message; and the sixth message is a DU configuration update confirmation message.
  • an embodiment of the present application proposes a communication method, including:
  • the centralized unit CU receives the fifth message sent by the distributed unit DU.
  • the fifth message carries the indication information of the system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB.
  • the distributed unit sends a fifth message to the centralized unit, and the centralized unit manages the distributed unit.
  • the CU sends a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the fifth message carries indication information of the system information block.
  • the indication information of the system information block is used to indicate that the distributed unit has generated the system information block.
  • the fifth message is an F1 setup request message (F1 setup request).
  • the indication information of the system information block is carried in the fifth cell of the F1 establishment request message.
  • the fifth information element may be: gNB-DU System information (gNB-DU System information) information element.
  • Each first information element corresponds to a cell and is used to represent the main information block and system information block of the cell.
  • the indication information of the system information block may be a certain field. For example, the field is "SIBx". When the field "SIBx" is included in the fifth message, it indicates the distribution The formula unit generates the system information block.
  • the indication information of the system information block may also be bits. For example, when a certain bit in the fifth message is "01", it indicates that the distributed unit has generated the system information block.
  • the fifth message may be an F1 establishment request message, and the fifth message may also be other messages, which is not limited here.
  • the embodiment of the application provides a communication method.
  • the distributed unit reports the indication information of the system information block to the centralized unit, so that the centralized unit can know that the distributed unit generates The system information block, and thus the centralized unit, configures parameters for the system information block.
  • the communication resources between the centralized unit and the distributed unit can be effectively saved.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the second message carries the value label, or the second message carries the value label and the area range, or the second message carries the area range.
  • a value tag (valueTag): used to identify whether the SIB has changed, and the DU uses the value tag to inform the user equipment whether the SIB associated with the value tag has changed.
  • the value label is an integer type, and the value range of the value label is ⁇ 0-31 ⁇ . When the SIB changes, the value label is sequentially accumulated.
  • the value label of SIB2 is 0, when the SIB2 changes, the value label changes from 0 to 1.
  • the user equipment can determine that the SIB2 has changed according to the value tag.
  • AreaScope used to identify whether the SIB is area-specific or cell-specific.
  • the parameter may be a value label and/or an area location. This parameter can also include other parameters, which are not limited here.
  • the method further includes: the CU sends a third message to the DU, the third message carrying the changed parameter, the changed parameter and the SIB association.
  • the centralized unit sends a third message to the distributed unit to configure the changed parameters to the system information block in the distributed unit.
  • the system information block may be a changed system information block, or the system information block may be The unchanged system information block.
  • the centralized unit may configure the changed parameters to the system information block in the distributed unit by sending a third message to the distributed unit. This makes the solution applicable to multiple scenarios and improves the flexibility of implementation.
  • the method further includes: the CU receives a sixth message sent by the DU, the sixth message carrying the changed indication information of the SIB, and the changed The SIB is generated by the DU.
  • the indication information of the changed system information block may be a certain field, for example, the field is "SIBx-changed", when the sixth message includes the field "SIBx-changed" ", it indicates that the system information block generated by the distributed unit has changed.
  • the indication information of the changed system information block may also be bits. For example, when a bit in the sixth message is "011", it indicates that the system information block generated by the distributed unit has occurred. change.
  • the sixth message may be an F1 establishment request message, and the sixth message may also be other messages, which is not limited here.
  • the distributed unit can notify the centralized unit that the system information block has changed through a variety of methods. Improved the flexibility of the solution. In addition, the communication resources between the centralized unit and the distributed unit can be effectively saved.
  • the fifth message is an F1 establishment request message; the second message is an F1 establishment response message.
  • the third message is a DU configuration update message; the sixth message is a DU configuration update confirmation message.
  • an embodiment of the present application proposes a communication device, including:
  • a sending module configured to send a first message to the communication device CU, where the first message carries a system information block SIB, and the SIB is generated by the DU;
  • the receiving module is configured to receive a second message sent by the CU, where the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the processing module is used to configure the relevant parameters of the SIB based on the parameters.
  • the receiving module is further configured to receive a third message sent by the CU, where the third message carries the changed parameter, and the changed parameter is associated with the SIB.
  • the sending module is further configured to send a fourth message to the CU, where the fourth message carries the changed SIB, and the changed SIB is generated by the DU.
  • the first message is an F1 establishment request message; the second message is an F1 establishment response message.
  • the third message is a DU configuration update message; the fourth message is a DU configuration update confirmation message.
  • an embodiment of the present application proposes a communication device, including:
  • a receiving module configured to receive a first message sent by a communication device DU, the first message carries a system information block SIB, and the SIB is generated by the DU;
  • the sending module is configured to send a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an area scope areaScope.
  • the sending module is further configured to send a third message to the DU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the receiving module is further configured to receive a fourth message sent by the DU, where the fourth message carries the changed SIB, and the changed SIB is generated by the DU.
  • the first message is an F1 establishment request message; the second message is an F1 establishment response message; the third message is a DU configuration update message; The fourth message is the DU configuration update confirmation message.
  • an embodiment of the present application proposes a communication device, including:
  • a sending module configured to send a fifth message to the communication device CU, where the fifth message carries indication information of a system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB;
  • the receiving module is configured to receive a second message sent by the CU, where the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the processing module is configured for the DU to configure the relevant parameters of the SIB based on the parameters.
  • the receiving module is further configured to receive a third message sent by the CU, the third message carrying the changed parameter, and the changed parameter Associate with this SIB.
  • the sending module is further configured to send a sixth message to the CU, the sixth message carrying the changed indication information of the SIB, and the changed The SIB is generated by the DU.
  • the fifth message is an F1 establishment request message; the second message is an F1 establishment response message.
  • the third message is a DU configuration update message; the sixth message is a DU configuration update confirmation message.
  • an embodiment of the present application proposes a communication device, including:
  • a receiving module configured to receive a fifth message sent by a communication device, where the fifth message carries indication information of a system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB;
  • the sending module is further configured to send a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the sending module is further configured to send a third message to the DU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the receiving module is further configured to receive a sixth message sent by the DU, the sixth message carrying the changed indication information of the SIB, and the changed The SIB is generated by the DU.
  • the fifth message is an F1 establishment request message; the second message is an F1 establishment response message.
  • the third message is a DU configuration update message; the sixth message is a DU configuration update confirmation message.
  • the embodiments of the present application provide a communication device, which can implement the function performed by the DU in the method involved in the first or third aspect above, or implement the method in the method involved in the second or fourth aspect above
  • the function performed by the CU includes a processor, a memory, a receiver connected to the processor and a transmitter connected to the processor; the memory is used to store program codes and transmit the program codes to the processor; the processor is used for According to the instructions in the program code, the receiver and the transmitter are driven to execute the methods in the first, second, third, or fourth aspects; the receiver and the transmitter are respectively connected to the processor to perform the above aspects The operation of the CU or DU in this method.
  • the transmitter can perform the sending operation, and the receiver can perform the receiving operation.
  • the receiver and transmitter may be a radio frequency circuit, which realizes receiving and sending messages through an antenna; the receiver and transmitter may also be a communication interface, and the processor and the communication interface are connected through a bus, and the processing The device receives or sends messages through the communication interface.
  • an embodiment of the present application provides a communication device.
  • the communication device may include entities such as a network device or a chip.
  • the communication device includes a processor and a memory; the memory is used to store instructions; and the processor is used to execute the memory.
  • the instruction in, causes the communication device to execute the method of any one of the foregoing first aspect, second aspect, third aspect, or fourth aspect.
  • an embodiment of the present application provides a computer-readable storage medium storing one or more computer-executable instructions.
  • the processor executes the first aspect or the first aspect described above. Any one of the possible implementation manners of the second aspect, the third aspect, or the fourth aspect.
  • the embodiments of the present application provide a computer program product (or computer program) that stores one or more computer-executable instructions.
  • the processor executes the aforementioned first Aspect, or the second aspect, the third aspect, or any one of the possible implementation manners of the fourth aspect.
  • this application provides a chip system including a processor for supporting computer equipment to implement the functions involved in the above aspects.
  • the chip system further includes a memory for storing necessary program instructions and data for the computer equipment.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • this application provides a communication system including the communication device in the eighth or ninth aspect described above.
  • Figure 1 is a schematic diagram of a network architecture of a communication system
  • Figure 2 is a schematic diagram of the architecture of using CU-DU in a communication system
  • Figure 3 is a schematic diagram of an architecture of CU
  • FIG. 4 is a schematic diagram of the hardware structure of a network device in an embodiment of the application.
  • FIG. 5a is a schematic diagram of an embodiment of a communication method proposed in an embodiment of this application.
  • FIG. 5b is a schematic diagram of an application scenario proposed by an embodiment of this application.
  • FIG. 5c is a schematic diagram of another application scenario proposed by an embodiment of the application.
  • FIG. 6a is a schematic diagram of an embodiment of another communication method provided by an embodiment of this application.
  • FIG. 6b is a schematic diagram of another application scenario proposed by an embodiment of this application.
  • FIG. 6c is a schematic diagram of another application scenario proposed by an embodiment of this application.
  • FIG. 7 is a schematic diagram of an embodiment of a communication device in an embodiment of the application.
  • FIG. 8 is a schematic diagram of another embodiment of a communication device in an embodiment of this application.
  • FIG. 9 is a schematic diagram of another embodiment of a communication device in an embodiment of this application.
  • FIG. 10 is a schematic diagram of another embodiment of the communication device in the embodiment of this application.
  • the embodiment of the application provides a communication method.
  • the distributed unit reports the system information block to the centralized unit, so that the centralized unit can know that the distributed unit has generated the system information.
  • Block so that the centralized unit configures parameters for the system information block.
  • FIG. 1 is a schematic diagram of a network architecture of a communication system.
  • the communication system includes an access network and a core network.
  • the access network may be a next generation radio access network (NG-RAN), and the core network may be a 5G Core Network (5G Core Network, 5GC).
  • the access network may include access network devices (for example, gNB), and gNBs are connected through an interface (for example, an Xn interface).
  • the gNB and 5GC are connected through an interface (for example: Ng interface).
  • the core network may include access and mobility management functions (AMF).
  • the core network may also include a user plane function (UPF).
  • Figure 2 is a schematic diagram of the CU-DU architecture used in the communication system. As shown in FIG.
  • the access network equipment may include a centralized unit (Centralized Unit, CU) and a distributed unit (Distributed Unit, DU).
  • the functions of the access network equipment are split, and part of the functions of the access network equipment are deployed in a CU, and the other part of the functions of the access network equipment are deployed in the DU.
  • the number of DUs can be one or more. Multiple DUs can share one CU to save costs and facilitate network expansion.
  • the CU and DU are connected through an interface (for example, an F1 interface).
  • CU represents that the access network device is connected to the core network through an interface (for example, an Ng interface).
  • the function division of CU and DU can be divided according to the protocol stack.
  • Radio resource control RRC
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • RLC Radio Link Control
  • MAC media access control
  • PHY physical layer
  • the CU has the processing capabilities of RRC, PDCP and SDAP.
  • DU has RLC, MAC, and PHY processing capabilities. It is worth noting that the above function segmentation is just an example, and there may be other segmentation methods.
  • the CU includes the processing capabilities of RRC, PDCP, RLC, and SDAP
  • the DU has the processing capabilities of MAC and PHY.
  • the CU includes the processing capabilities of RRC, PDCP, RLC, SDAP, and part of the MAC (for example, adding a MAC packet header), and the DU has the processing capability of PHY and part of the MAC (for example, scheduling).
  • the names of CU and DU may change, as long as the access network node that can realize the above-mentioned functions can be regarded as the CU and DU in this patent application.
  • FIG. 3 is a schematic diagram of a CU architecture. As shown in Figure 3, CU includes control plane CU (CU-CP) and user plane CU (CU-+).
  • CU-CP control plane CU
  • CU-+ user plane CU
  • CU-CP and CU-UP can be on different physical devices. CU-CP and CU-UP can also be on the same physical device.
  • the CU-CP and CU-UP are connected through an interface (for example, an E1 interface).
  • CU-CP represents that the access network device is connected to the core network through an interface (for example, an Ng interface).
  • the CU-CP is connected to the DU through an interface (for example, an F1-C interface), and the CU-UP is connected to the DU through an interface (for example, an F1-U interface).
  • the number of CU-CP can be one, and the number of CU-UP can be one or more. Multiple CU-UPs can share one CU-CP.
  • CU-CP mainly has a control plane function.
  • the CU-UP mainly has user-plane functions.
  • the RRC layer can be deployed on the CU-CP, while the SDAP layer is not deployed on the CU-CP.
  • the CU-CP may also have part of the control plane functions of the PDCP layer, for example, it may perform signaling radio bearer (SRB) processing.
  • SRB signaling radio bearer
  • the SDAP layer can be deployed in CU-UP, but the RRC layer is not deployed in CU-UP.
  • the CU-UP can also have the user plane part of the PDCP layer, such as data radio bearer (DRB) processing.
  • DRB data radio bearer
  • FIG. 4 is a schematic diagram of the hardware structure of a communication device in an embodiment of the application.
  • the communication device may be a possible implementation manner of the CU or DU in the embodiment of the present application.
  • the communication device includes at least a processor 402, a memory 403, and a transceiver 404.
  • the memory 403 is further used to store instructions 4032 and data 4034.
  • the communication device may further include an antenna 406, an I/O (Input/Output) interface 410, and a bus 412.
  • the transceiver 404 further includes a transmitter 4042 and a receiver 4044.
  • the processor 402, the transceiver 404, the memory 403, and the I/O interface 410 are communicatively connected to each other through the bus 412, and the antenna 406 is connected to the transceiver 404.
  • the processor 402 may be a general-purpose processor, such as but not limited to a central processing unit (CPU), or a dedicated processor, such as, but not limited to, a digital signal processor (DSP). Application Specific Integrated Circuit (ASIC) and Field Programmable Gate Array (FPGA), etc.
  • the processor 402 may also be a combination of multiple processors.
  • the processor 402 may be used to execute the relevant steps of the communication method in the subsequent method embodiments.
  • the processor 402 may be a processor specifically designed to perform the foregoing steps and/or operations, or a processor that performs the foregoing steps and/or operations by reading and executing instructions 4032 stored in the memory 403.
  • the data 4034 may be used in the process of performing the above steps and/or operations.
  • the transceiver 404 includes a transmitter 4042 and a receiver 4044.
  • the transmitter 4042 is used to transmit signals through an antenna 406.
  • the receiver 4044 is configured to receive signals through at least one antenna among the antennas 406.
  • the transmitter 4042 may be specifically used to perform execution through at least one antenna among the antennas 406. For example, when the communication method in the subsequent method embodiment is applied to the CU or the DU, the CU Or the operation performed by the receiving module or the sending module in the DU.
  • the transceiver 404 is used to support the communication device to perform the aforementioned receiving function and sending function.
  • the processor having processing functions is regarded as the processor 402.
  • the receiver 4044 may also be called a receiver, an input port, a receiving circuit, etc.
  • the transmitter 4042 may be called a transmitter, a transmitter, or a transmitting circuit, etc.
  • the processor 402 may be configured to execute instructions stored in the memory 403 to control the transceiver 404 to receive messages and/or send messages, so as to complete the functions of the communication device in the method embodiment of the present application.
  • the function of the transceiver 404 may be implemented by a transceiver circuit or a dedicated chip for transceiver.
  • the memory 403 may be various types of storage media, such as random access memory (RAM), read only memory (ROM), non-volatile RAM (Non-Volatile RAM, NVRAM), Programmable ROM (Programmable ROM, PROM), erasable PROM (Erasable PROM, EPROM), electrically erasable PROM (Electrically Erasable PROM, EEPROM), flash memory, optical memory and registers, etc.
  • RAM random access memory
  • ROM read only memory
  • non-volatile RAM Non-Volatile RAM
  • NVRAM Non-Volatile RAM
  • PROM Programmable ROM
  • PROM erasable PROM
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable PROM
  • flash memory optical memory and registers, etc.
  • the memory 403 is specifically used to store instructions 4032 and data 4034.
  • the processor 402 can read and execute the instructions 4032 stored in the memory 403 to perform the steps and/or operations described in the
  • the communication device may further include an I/O interface 410, and the I/O interface 410 is used to receive instructions and/or data from a peripheral device, and output instructions and/or data to the peripheral device.
  • I/O interface 410 is used to receive instructions and/or data from a peripheral device, and output instructions and/or data to the peripheral device.
  • FIG. 5a is a schematic diagram of an embodiment of a communication method proposed in an embodiment of the present application.
  • a communication method proposed in an embodiment of the present application includes:
  • the distributed unit sends a first message to the centralized unit, where the first message carries a system information block.
  • step 500 may be further included: the distributed unit generates a system information block.
  • the system information block is called "SIBx".
  • the specific composition and communication mode of the distributed unit are similar to the distributed units described in Figures 1 to 4, and will not be repeated here.
  • the distributed unit generating the system information block "SIBx” may be: the distributed unit is responsible for encoding and generating the system information block SIBx (the gNB-DU is responsible for the encoding of SIBx).
  • the system information block may be "SIB10".
  • the distributed unit After the distributed unit generates the system information block, the distributed unit sends a first message to the centralized unit, and the centralized unit manages the distributed unit.
  • the first message is an F1 setup request message (F1 setup request).
  • the system information block is carried in the first cell of the F1 establishment request message.
  • the first information element may be: a gNB-DU system information (gNB-DU system information) information element.
  • gNB-DU system information gNB-DU system information
  • Each first information element corresponds to a cell, and is used to indicate the master information block message and the system information block message of the cell.
  • the first cell may carry the information shown in Table 1:
  • the character string in the cell type describes the complete content of the main information block or the system information block.
  • the F1 establishment request message contains MIB, SIB1, and SIBx of all cells in the distributed unit, and the SIBx is associated with a certain cell among them.
  • the first message is a newly defined F1 message, dedicated to carrying the above system information block x message (SIBx message), and the content of the system information block x message (SIBx message) is the SIBx encodes the generated character string in accordance with the encoding method agreed by 3GPP.
  • the first message is an uplink system information block transfer (UL SIB transfer) message.
  • the distributed unit receives a second message sent by the centralized unit, where the second message carries parameters.
  • the distributed unit receives the second message sent by the centralized unit, and the second message carries parameters.
  • the parameter has at least one of the following: a value tag (valueTag) or an area scope (areaScope).
  • valueTag value tag
  • areaScope area scope
  • the second message carries the value label
  • the second message carries the value label and the area range
  • the second message carries the area range.
  • a value tag used to identify whether the SIB has changed, and the DU uses the value tag to inform the user equipment whether the SIB associated with the value tag has changed.
  • the value label is an integer.
  • the value range of the value label is ⁇ 0-31 ⁇ .
  • the value label of SIBx is 0, and when the SIBx changes, the value label changes from 0 to 1.
  • the user equipment can determine that the SIBx has changed according to the value tag.
  • AreaScope used to identify whether the SIB is area-specific or cell-specific.
  • the second message is an F1 setup response message (F1 setup response).
  • the parameter is carried in the second information element in the F1 establishment response message.
  • the second information element may be a SIB type to Be Updated Item IE, where the system information block message (SIB message) corresponding to "SIBx" in the information element is empty .
  • SIB message system information block message
  • the F1 establishment response message carries configuration information of the cell, and the cell is a cell that needs to be activated managed by the distributed unit. Taking the second cell as the SIB type item cell to be updated as an example, the second cell may carry the information shown in Table 2:
  • the second information element may be other SIB type to Be Updated Item IEs, where the system information block message (SIB message) corresponding to "SIBx" in the information element )Is empty.
  • SIB message system information block message
  • the second cell may carry the information shown in Table 3:
  • the second message is a newly defined F1 message, which is dedicated to bear the parameters associated with the aforementioned SIBx.
  • the second message is a downlink system information block transfer (DL SIB transfer) message.
  • DL SIB transfer downlink system information block transfer
  • the centralized unit may send the SIBx parameters for a part of the distributed units, that is, the centralized unit determines which distributed units configure the parameters (the distributed units generate the SIBx); In another optional implementation manner, the centralized unit may configure parameters for all distributed units configured with the SIBx.
  • the distributed unit sends a fourth message to the centralized unit, where the fourth message carries the changed system information block.
  • the distributed unit when the system information block in the distributed unit is changed, the distributed unit sends a fourth message to the centralized unit, and the fourth message carries the changed system information block.
  • the fourth message is a DU configuration update (gNB-DU configuration update) message, and the message carries the changed system information block.
  • a DU configuration update gNB-DU configuration update
  • the fourth message carries indication information of the changed system information block.
  • the indication information of the changed system information block is used to indicate that the distributed unit has generated the changed system information block (compared with the system information block in step 501).
  • the fourth message is a newly defined F1 message, which is dedicated to bear the SIBx message.
  • the distributed unit After the distributed unit sends the fourth message to the centralized unit, the centralized unit sends a third message to the distributed unit based on the fourth message, and step 504 is performed.
  • step 503 is an optional step.
  • the centralized unit may also send a third message to the distributed unit without receiving the fourth message, and the third message carries the changed parameters. That is, on the premise that the system information block in the distributed unit is not changed, the centralized unit configures the changed parameters to the distributed unit.
  • the distributed unit receives a third message sent by the centralized unit, where the third message carries the changed parameter.
  • the centralized unit sends a third message to the distributed unit to configure the system information block in the distributed unit with the changed parameters.
  • the system information block may be the changed system information block.
  • the information block may also be an unchanged system information block.
  • step 504 whether the system information block is changed is relative to the system information block in step 501.
  • the change of the system information block means that the content of the SIB has changed, that is, the character string in the SIB message has changed.
  • the third message may be a DU configuration update confirmation (gNB-DU configuration update acknowledge) message.
  • the changed parameter is carried in the third cell in the third message.
  • the third information element is similar to the second information element in the foregoing step 502, and will not be repeated here. It should be noted that, compared with the foregoing second information element, the parameters carried by the third information element may be changed.
  • the second cell carries a value label ⁇ 21 ⁇
  • the third cell carries a value label ⁇ 22 ⁇ .
  • the third information element and the second information element may also be inconsistent.
  • the third information element may be a SIB type item information element to be updated, and the second information element may be another information element to be updated. SIB type item cell.
  • the third message is a newly defined F1 message, which is dedicated to bear SIBx related parameters.
  • the embodiment of the application provides a communication device.
  • the distributed unit reports the generated or changed system information block to the centralized unit, and the centralized unit reports the generated or changed system information block according to the report. It can be learned that the system information block has been generated or changed, so that the system information block can be configured with parameters.
  • This method is suitable for the system information block generated in the distributed unit.
  • the system information block is configured by a centralized unit. By using this method, the distributed unit can obtain the configuration parameters of the system information block, so that the system information block can be broadcasted in the cell. The configuration parameters of the system information block.
  • FIG. 5b is a schematic diagram of a communication method provided by an embodiment of this application. The method includes:
  • the distributed unit generates SIBx.
  • step S1 the distributed unit generates SIBx.
  • the distributed unit sends an F1 establishment request message to the centralized unit, where the F1 establishment request message includes the SIBx.
  • step S2 the distributed unit sends an F1 establishment request message to the centralized unit, and the F1 establishment request message includes SIBx.
  • the content of the SIBx is "ABCD”
  • the F1 establishment request message is shown in Table 4:
  • the distributed unit receives the F1 establishment response message sent by the centralized unit, where the F1 establishment response message includes the value label of the SIBx and the area location.
  • step S3 for example, the F1 establishment response message is shown in Table 5:
  • the distributed unit configures the value label and area location of the SIBx.
  • FIG. 5c is a schematic diagram of another application scenario provided by an embodiment of the application.
  • Another application scenario provided by the embodiment of the present application includes:
  • the distributed unit SIBx has changed.
  • step D1 the SIBx is changed.
  • the character string of the SIBx generated by the distributed unit in step S1 is "ABCD", and the SIBx after the change is "abc".
  • the distributed unit sends a DU configuration update message to the centralized unit, where the DU configuration update message includes the changed SIBx.
  • step D2 the DU configuration update message is shown in Table 6:
  • the distributed unit receives the DU configuration update confirmation message sent by the centralized unit.
  • the DU configuration update confirmation message includes the changed SIBx value label and area location.
  • step D3 the DU configuration update message is shown in Table 7:
  • FIG. 6a is a schematic diagram of an embodiment of another communication method provided by an embodiment of the application.
  • the communication method proposed in the embodiment of the present application further includes:
  • the distributed unit sends a fifth message to the centralized unit, where the fifth message carries indication information of the system information block.
  • step 601 it may further include step 600: the distributed unit generates a system information block.
  • the system information block is called "SIBx".
  • SIBx system information block
  • the specific composition and communication mode of the distributed unit are similar to the distributed units described in Figures 1 to 4, and will not be repeated here.
  • the system information block may be "SIB10" in the 5G-NR system.
  • the distributed unit sends a fifth message to the centralized unit, and the centralized unit manages the distributed unit.
  • the fifth message carries the indication information of the system information block.
  • the indication information of the system information block is used to indicate that the distributed unit has generated the system information block.
  • the fifth message is an F1 setup request message (F1 setup request).
  • the indication information of the system information block is carried in the fifth cell of the F1 establishment request message.
  • the fifth information element may be: gNB-DU system information (gNB-DU system information) information element.
  • gNB-DU system information gNB-DU system information
  • Each first information element corresponds to a cell and is used to represent the main information block and system information block of the cell.
  • the fifth cell may carry the information shown in Table 8:
  • the indication information of the system information block may be a certain field.
  • the field is "SIBx".
  • SIBx When the field "SIBx" is included in the fifth message, it indicates the distribution
  • the formula unit generates the system information block.
  • the indication information of the system information block may also be bits. For example, when a certain bit in the fifth message is "01", it indicates that the distributed unit has generated the system information block.
  • the fifth message may be an F1 establishment request message, and the fifth message may also be other messages, which is not limited here.
  • the fifth message is similar to the foregoing first message, and may also be a newly defined F1 establishment request message.
  • exemplary an uplink system information block transfer (UL SIB transfer) message.
  • UL SIB transfer uplink system information block transfer
  • the distributed unit receives a second message sent by the centralized unit, where the second message carries parameters.
  • Step 602 is similar to the aforementioned step 502, and will not be repeated here.
  • the distributed unit sends a sixth message to the centralized unit, where the sixth message carries the indication information of the changed system information block.
  • the distributed unit sends a sixth message to the centralized unit, and the sixth message carries the indication information of the changed system information block.
  • the sixth message is a DU configuration update (gNB-DU configuration update) message.
  • the DU configuration update message carries indication information of the changed system information block, and the indication information is used to indicate that the system information block (SIBx) in the distributed unit has been changed.
  • the indication information of the changed system information block is specifically carried in the sixth cell in the DU configuration update message.
  • the sixth information element is similar to the foregoing fifth information element, and the sixth information element may carry the information shown in Table 9:
  • the sixth information element may also carry the information shown in Table 10:
  • the indication information of the changed system information block may be a certain field, for example, the field is "SIBx-changed", when the sixth message includes the field "SIBx-changed" ", it indicates that the system information block generated by the distributed unit has changed.
  • the indication information of the changed system information block may also be bits. For example, when a bit in the sixth message is "011", it indicates that the system information block generated by the distributed unit has occurred. change.
  • the sixth message may be an F1 establishment request message, and the sixth message may also be other messages, which is not limited here.
  • the sixth message may also carry a complete changed system information block.
  • the distributed unit receives a third message sent by the centralized unit, where the third message carries the changed parameters.
  • This embodiment is similar to the aforementioned step 504, and will not be repeated here.
  • the embodiment of the application provides a communication method.
  • the distributed unit reports the indication information of the system information block to the centralized unit, so that the centralized unit can know the distributed unit
  • the system information block is generated or changed, so that the centralized unit configures parameters for the system information block.
  • This method is suitable for the system information block generated in the distributed unit.
  • the system information block is configured by a centralized unit.
  • the distributed unit can obtain the configuration parameters of the system information block, so that the system information block can be broadcasted in the cell.
  • the configuration of the system information block can be effectively saved.
  • FIG. 6b is a schematic diagram of an application scenario provided by an embodiment of the application.
  • An application scenario provided by an embodiment of the present application includes:
  • the distributed unit generates SIBx.
  • Step F1 is similar to step S1 and will not be repeated here.
  • the distributed unit sends an F1 establishment request message to the centralized unit, where the F1 establishment request message includes the indication information of the SIBx.
  • step F2 exemplarily, the F1 establishment request message has the information shown in Table 11:
  • the distributed unit receives the F1 establishment response message sent by the centralized unit, where the F1 establishment response message includes the value label of the SIBx and the area location.
  • Step F3 is similar to the aforementioned step S3, and will not be repeated here.
  • the distributed unit configures the value label and area location of SIBx.
  • FIG. 6c is a schematic diagram of another application scenario provided by an embodiment of the application.
  • Another application scenario provided by the embodiment of the present application includes:
  • Step G1 is similar to step D1 and will not be repeated here.
  • the distributed unit sends a DU configuration update message to the centralized unit, where the DU configuration update message includes the indication information of the changed SIBx.
  • step G2 the DU configuration update message is as shown in Table 12:
  • the distributed unit receives the DU configuration update confirmation message sent by the centralized unit, where the DU configuration update confirmation message includes the changed SIBx value label and area location.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the communication device into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one transceiver module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 7 is a schematic diagram of an embodiment of the communication device in an embodiment of this application.
  • the communication device 700 may be deployed in a distributed unit, and the communication device 700 includes:
  • the sending module 701 is configured to send a first message to the centralized unit CU, where the first message carries a system information block SIB, and the SIB is generated by the DU;
  • the receiving module 702 is configured to receive a second message sent by the CU, where the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the processing module 703 is configured to configure related parameters of the SIB based on the parameters.
  • the receiving module 702 is further configured to receive a third message sent by the CU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the sending module 701 is further configured to send a fourth message to the CU, the fourth message carrying the changed SIB, and the changed SIB is generated by the DU.
  • the first message is an F1 establishment request message.
  • the second message is an F1 establishment response message.
  • the third message is a DU configuration update message.
  • the fourth message is a DU configuration update confirmation message.
  • FIG. 8 is a schematic diagram of another embodiment of the communication device in the embodiment of the application.
  • the communication device 800 may be deployed in a centralized unit, and the communication device 800 includes:
  • the receiving module 801 is configured to receive a first message sent by a distributed unit, where the first message carries a system information block SIB, and the SIB is generated by the DU;
  • the sending module 802 is configured to send a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the sending module 802 is further configured to send a third message to the DU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the receiving module 801 is further configured to receive a fourth message sent by the DU, the fourth message carrying the changed SIB, and the changed SIB is generated by the DU.
  • the first message is an F1 establishment request message.
  • the second message is an F1 establishment response message.
  • the third message is a DU configuration update message.
  • the fourth message is a DU configuration update confirmation message.
  • FIG. 9 is a schematic diagram of another embodiment of the communication device in the embodiment of the application.
  • the communication device 900 may be deployed in a distributed unit, and the communication device 900 includes:
  • the sending module 901 is configured to send a fifth message to the centralized unit CU, where the fifth message carries indication information of the system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB;
  • the receiving module 902 is configured to receive a second message sent by the CU, where the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the processing module 903 is configured to configure related parameters of the SIB based on the parameters.
  • the receiving module 902 is further configured to receive a third message sent by the CU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the sending module 901 is further configured to send a sixth message to the CU, the sixth message carrying indication information of the changed SIB, and the changed SIB is generated by the DU .
  • the fifth message is an F1 establishment request message.
  • the second message is an F1 establishment response message.
  • the third message is a DU configuration update message.
  • the sixth message is a DU configuration update confirmation message.
  • FIG. 10 is a schematic diagram of another embodiment of the communication device in the embodiment of the application.
  • the communication device 1000 may be deployed in a centralized unit, and the communication device 1000 includes:
  • the receiving module 1001 is configured to receive a fifth message sent by a distributed unit, where the fifth message carries indication information of a system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB;
  • the sending module 1002 is configured to send a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the sending module 1002 is further configured to send a third message to the DU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the receiving module 1001 is further configured to receive a sixth message sent by the DU, where the sixth message carries the indication information of the changed SIB, and the changed SIB is controlled by the DU. generate.
  • the fifth message is an F1 establishment request message.
  • the second message is an F1 establishment response message.
  • the third message is a DU configuration update message.
  • the sixth message is a DU configuration update confirmation message.
  • the communication device in the foregoing embodiment may be a network device, or a chip applied to the network device, or other combination devices, components, etc. that can realize the functions of the foregoing network device.
  • the receiving module and the sending module may be transceivers, the transceiver may include an antenna and a radio frequency circuit, etc., and the processing module may be a processor, such as a baseband chip.
  • the receiving module and the sending module may be radio frequency units, and the processing module may be a processor.
  • the receiving module may be the input port of the chip system
  • the sending module may be the output interface of the chip system
  • the processing module may be the processor of the chip system, for example: central processing unit (CPU) .
  • CPU central processing unit
  • the memory included in the communication device is mainly used for storing software programs and data, for example, storing the first message and the second message described in the foregoing embodiment.
  • the processor included in the communication device also has the following functions:
  • a transceiver configured to send a first message to the centralized unit CU, where the first message carries a system information block SIB, and the SIB is generated by the DU;
  • the processor is configured to configure related parameters of the SIB based on the parameter, and the parameter includes at least one of the following: a value tag valueTag or an areaScope.
  • the transceiver is further configured to receive a third message sent by the CU, where the third message carries the changed parameter, and the changed parameter is associated with the SIB.
  • the transceiver is further configured to send a fourth message to the CU, where the fourth message carries the changed SIB, and the changed SIB is generated by the DU.
  • the transceiver included in the network device also has the following functions:
  • the first message Used to receive a first message sent by a distributed unit, where the first message carries a system information block SIB, and the SIB is generated by the DU;
  • the second message Used to send a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the transceiver is also used to send a third message to the DU, the third message carries the changed parameter, the changed parameter is associated with the SIB, and the parameter includes at least one of the following: valueTag or area range areaScope.
  • the transceiver is further configured to receive a fourth message sent by the DU, where the fourth message carries the changed SIB, and the changed SIB is generated by the DU.
  • the transceiver included in the network device also has the following functions:
  • the fifth message carries indication information of the system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB;
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the processor is further configured to configure related parameters of the SIB based on the parameters.
  • the transceiver is further configured to receive a third message sent by the CU, where the third message carries the changed parameter, and the changed parameter is associated with the SIB.
  • the transceiver is further configured to send a sixth message to the CU, where the sixth message carries the indication information of the changed SIB, and the changed SIB is generated by the DU.
  • the transceiver included in the network device also has the following functions:
  • the fifth message Used to receive a fifth message sent by a distributed unit, where the fifth message carries indication information of a system information block SIB, and the indication information of the SIB is used to indicate that the DU has generated the SIB;
  • the second message Used to send a second message to the DU, the second message carries a parameter, and the parameter is associated with the SIB.
  • the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • the transceiver is further configured to send a third message to the DU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • the transceiver is further configured to receive a sixth message sent by the DU, the sixth message carrying indication information of the changed SIB, and the changed SIB is generated by the DU.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the communication method described in any of the foregoing method embodiments.
  • the foregoing processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, At this time, the processor may be a general-purpose processor, which is realized by reading the software code stored in the memory.
  • the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • This application also provides a communication system, which includes a CU and a DU.
  • An embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute:
  • Step A Send a first message to the centralized unit CU, the first message carries the system information block SIB, and the SIB is generated by the DU; receive a second message sent by the CU, the second message carries a parameter, the parameter Associate with this SIB.
  • Step B It is used to configure related parameters of the SIB based on the parameter, and the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • Step C for receiving a third message sent by the CU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • Step D Used to send a fourth message to the CU, the fourth message carrying the changed SIB, and the changed SIB is generated by the DU.
  • Step E Used to receive the first message sent by the distributed unit, the first message carries the system information block SIB, the SIB is generated by the DU; it is used to send a second message to the DU, the second message carries parameters , This parameter is associated with this SIB.
  • SIB system information block
  • the SIB is generated by the DU; it is used to send a second message to the DU, the second message carries parameters , This parameter is associated with this SIB.
  • Step F Used to send a third message to the DU, the third message carries the changed parameter, the changed parameter is associated with the SIB, and the parameter includes at least one of the following: valueTag or areaScope .
  • Step G for receiving a fourth message sent by the DU, the fourth message carrying the changed SIB, and the changed SIB is generated by the DU.
  • Step H Send a fifth message to the centralized unit CU.
  • the fifth message carries the indication information of the system information block SIB.
  • the indication information of the SIB is used to indicate that the DU has generated the SIB; and the second message sent by the CU is received.
  • the second message carries a parameter, and the parameter is associated with the SIB.
  • Step I It is used to configure the relevant parameters of the SIB based on the parameter, and the parameter includes at least one of the following: a value tag valueTag, or an areaScope.
  • Step J for receiving a third message sent by the CU, the third message carrying the changed parameter, and the changed parameter is associated with the SIB.
  • Step K used to send a sixth message to the CU, the sixth message carrying indication information of the changed SIB, and the changed SIB is generated by the DU.
  • Step L Used to receive the fifth message sent by the distributed unit, the fifth message carries the indication information of the system information block SIB, the indication information of the SIB is used to indicate that the DU generated the SIB; used to send to the DU
  • the second message the second message carries a parameter, and the parameter is associated with the SIB.
  • Step M Used to send a third message to the DU, the third message carries the changed parameter, the changed parameter is associated with the SIB, and the parameter includes at least one of the following value tags valueTag or areaScope .
  • Step N for receiving a sixth message sent by the DU, where the sixth message carries the indication information of the changed SIB, and the changed SIB is generated by the DU.
  • An embodiment of the present application also provides a computer program product.
  • the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer executes the above steps AD, and/or steps EG, and/ Or step HK, and/or step LN.
  • the embodiment of the present application also provides a chip, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the chip executes the above steps AD, And/or step EG, and/or step HK, and/or step LN.
  • An embodiment of the present application also provides a chip including a processor for calling and running a computer program so that the chip executes steps A-D, and/or steps E-G, and/or steps H-K, and/or steps L-N.
  • the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physically separate.
  • the physical unit can be located in one place or distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the connection relationship between the modules indicates that they have a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.
  • this application can be implemented by means of software plus necessary general hardware.
  • it can also be implemented by dedicated hardware including dedicated integrated circuits, dedicated CPUs, dedicated memory, Dedicated components and so on to achieve.
  • all functions completed by computer programs can be easily implemented with corresponding hardware.
  • the specific hardware structure used to achieve the same function can also be diverse, such as analog circuits, digital circuits or special-purpose circuits. Circuit etc.
  • software program implementation is a better implementation in more cases.
  • the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, such as a computer floppy disk. , U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., including several instructions to make a computer device execute the method described in each embodiment of this application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, a computer, a communication device, or a computing device.
  • the equipment or data center is connected to another website site, computer, communication device, computing device or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission.
  • the computer-readable storage medium may be any usable medium that can be stored by a computer or a data storage device such as a communication device or a data center integrated with one or more usable media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • one embodiment or “an embodiment” mentioned throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment” or “in an embodiment” in various places throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application. The implementation process constitutes any limitation.
  • system and “network” in this article are often used interchangeably in this article.
  • the term “and/or” in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations.
  • the character "/" in this text generally indicates that the associated objects before and after are in an "or” relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B based on A does not mean that B is determined only based on A, and B can also be determined based on A and/or other information.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods in the various embodiments of the present application.

Landscapes

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

Abstract

本申请实施例公开了一种通信方法以及相关装置，可以应用于集中式单元-分布式单元系统。当系统信息块由分布式单元生成时，分布式单元向集中式单元报告该系统信息块，使得集中式单元获知该分布式单元生成了该系统信息块，从而该集中式单元可以为该系统信息块配置参数。该方法适用于在分布式单元中生成的系统信息块、该系统信息块由集中式单元配置参数，通过使用该方法，分布式单元可以获得系统信息块的配置参数，从而能够在小区中广播该系统信息块的配置参数。

Description

一种通信方法以及相关装置
本申请要求于2020年05月22日提交中国专利局、申请号为202010444151.1、发明名称为“一种通信方法以及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法以及相关装置。
背景技术
在无线通信系统中，终端设备和接入网设备之间在上行链路和下行链路上按照第三代合作伙伴计划(the 3rd generation partnership project,3GPP)组织制定的各种协议层通过无线承载(radio bearer，RB)传输各种数据，例如在信令无线承载上传输控制信令或在数据无线承载上传输业务数据。这些协议层包括物理(physical，PHY)层、媒体接入控制(media access control,MAC)层、无线链路控制(radio link control,RLC)、分组数据汇聚协议(packet data convergence protocol,PDCP)层以及无线资源控制(radio resource control，RRC)层等。接入网设备可以按照协议层进一步划分为集中式单元(central unit，CU)和分布式单元(distributed unit,DU)的架构，CU和DU之间包括控制面连接和用户面连接，其中，用户面连接又称为用户面隧道(user plane(UP)tunnel)。一个用户面隧道由CU上的一个上行隧道端点和DU上的一个下行隧道端点来确定。其中，CU用于实现PDCP层的功能和RRC层的功能，DU用于实现PHY层的功能、MAC层的功能以及RLC层的功能。
系统信息(System information，SI)，提供了用户设备(user equipment，UE)进行小区选择和接入所需的参数。系统信息SI包括一个主信息块(master information block，MIB)和若干个系统信息块(system information block，SIB)，例如SIB2、SIB3、和/或SIB4等。
SIB1在DU中生成，CU不对SIB关联的参数进行设置；其他SIB(例如5G中的SIB2～9)在CU中生成，并由CU设置该SIB关联的参数，CU可以将该SIB及其关联的参数告知DU。而随着通信技术的演进，出现了一类新的SIB，这类SIB的生成和参数设置方式与上述两类SIB不同，这类SIB在DU中产生，如何对这类SIB进行处理，是值得考虑的问题。
发明内容
本申请实施例提供了一种通信方法。
第一方面，本申请实施例提出一种通信方法，包括：
分布式单元DU向集中式单元CU发送第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成。该DU接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。具体的，该系统信息块可以称为“SIBx。”该分布式单元生成该系统信息块“SIBx”可以是：该分布式单元负责编码生成该系统信息块SIBx(the gNB-DU is responsible for the encoding of SIBx)。可选的，在5G-NR系统中，该系统信息块可以是“SIB10”。在一种可选的实现方式中，该第一消息为F1建立请求消息(F1setup request)。具体的，该 系统信息块承载于该F1建立请求消息的第一信元内。该第一信元可以是：gNB-DU系统信息(gNB-DU System information)信元。每个第一信元对应一个小区，用以表示该小区的主信息块消息和系统信息块消息。在另一种可选的实现方式中，该第一消息为新定义的F1消息，专用于承载上述系统信息块x消息(SIBx message)。
本申请实施例提供了一种通信装置，当系统信息块在分布式单元中生成时，分布式单元向集中式单元报告生成的系统信息块，集中式单元根据该报告可以获知该系统信息块已经生成，从而可以为该系统信息块配置参数。该方法适用于在分布式单元中生成的系统信息块、该系统信息块由集中式单元配置参数，通过使用该方法，分布式单元可以获得系统信息块的配置参数，从而能够在小区中广播该系统信息块的配置参数。
结合第一方面，在第一方面的一种可能的实现方式中，该参数包括以下至少一个：值标签(valueTag)、或区域范围(areaScope)。例如：第二消息中携带值标签，或，第二消息中携带值标签和区域范围，或，第二消息中携带区域范围。具体的，值标签(valueTag)：用于标识SIB是否改变，DU通过该值标签告知用户设备，该值标签关联的SIB是否改变。具体的，该值标签为整数类型，该值标签的取值范围是{0-31}，当SIB改变时，该值标签依次累加。例如：SIB2的值标签为0，当该SIB2发生改变后，该值标签由0变为1。用户设备可以根据该值标签确定该SIB2发生改变。区域范围(areaScope)：用于标识该SIB是区域特定的(area specific)还是小区特定的(cell specific)。本申请实施例中，该参数可以是值标签和/或区域位置。该参数还可以包括其它参数，此处不做限制。
结合第一方面，在第一方面的一种可能的实现方式中，该DU接收该CU发送的该第二消息之后，还包括：该DU基于该参数配置该SIB的相关参数。本申请实施例中，CU向DU发生该参数后，DU基于该参数配置该SIB的相关参数，使得DU中的用户设备可以获知该SIB是否发生改变，和/或，使得该DU获知该SIB的使用范围。
结合第一方面，在第一方面的一种可能的实现方式中，还包括：该DU接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。集中式单元通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数，该系统信息块可以是变更后的系统信息块，该系统信息块也可以是未变更的系统信息块。本申请实施例中，在系统信息块变更或者未变更的情况下，集中式单元可以通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数。使得本方案可以适用于多种场景，提升了实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，该DU接收该CU发送的该第三消息之前，还包括：分布式单元中系统信息块发生变更后，该DU向该CU发送第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。在另一种可选的实现方式中，该第四消息中携带变更后的系统信息块的指示信息。该变更后的系统信息块的指示信息，用于指示该分布式单元生成了变更后的系统信息块。本申请实施例中，当分布式单元中系统信息块发生变更后，分布式单元可以向集中式单元发送第四消息，该第四消息变更后的系统信息块或变更后的系统信息块的指示信息。分布式单元可以通过多种方法，告知集中式单元系统信息块发生变更。提升了本方案的实现灵活性。
结合第一方面，在第一方面的一种可能的实现方式中，该第一消息是F1建立请求消息，在另一种可选的实现方式中，该第一消息为新定义的F1消息，专用于承载系统信息块x消息(SIBx message)，示例性的，第一消息为上行系统信息块传输(UL SIB transfer)消息；该第二消息是F1建立响应消息，在另一种可选的实现方式中，该第二消息为新定义的F1消息，专用于承载上述的SIBx所关联的参数，示例性的，第二消息为下行系统信息块传输(DL SIB transfer)消息。
结合第一方面，在第一方面的一种可能的实现方式中，该第三消息是DU配置更新消息，在另一种可选的实现方式中，该第三消息为新定义的F1消息，专用于承载SIBx的关联参数；该第四消息是DU配置更新确认消息。在另一种可选的实现方式中，该第四消息为新定义的F1消息，专用于承载SIBx消息。
第二方面，本申请实施例提出了一种通信方法，包括：
首先，集中式单元CU接收分布式单元DU发送的第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成。该系统信息块称为“SIBx”；该CU向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。具体的，该分布式单元生成该系统信息块“SIBx”可以是：该分布式单元负责编码生成该系统信息块SIBx(the gNB-DU is responsible for the encoding of SIBx)。可选的，在5G-NR系统中，该系统信息块可以是“SIB10”。在一种可选的实现方式中，该第一消息为F1建立请求消息(F1setup request)。具体的，该系统信息块承载于该F1建立请求消息的第一信元内。该第一信元可以是：gNB-DU系统信息(gNB-DU System information)信元。每个第一信元对应一个小区，用以表示该小区的主信息块消息和系统信息块消息。在另一种可选的实现方式中，该第一消息为新定义的F1消息，专用于承载上述系统信息块x消息(SIBx message)。
本申请实施例提供了一种通信装置，当系统信息块在分布式单元中生成时，分布式单元向集中式单元报告生成的或者变更后的系统信息块，集中式单元根据该报告可以获知该系统信息块已经生成，从而可以为该系统信息块配置参数。该方法适用于在分布式单元中生成的系统信息块、该系统信息块由集中式单元配置参数，通过使用该方法，分布式单元可以获得系统信息块的配置参数，从而能够在小区中广播该系统信息块的配置参数。
结合第二方面，在第二方面的一种可能的实现方式中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。例如：第二消息中携带值标签，或，第二消息中携带值标签和区域范围，或，第二消息中携带区域范围。具体的，值标签(valueTag)：用于标识SIB是否改变，DU通过该值标签告知用户设备，该值标签关联的SIB是否改变。具体的，该值标签为整数类型，该值标签的取值范围是{0-31}，当SIB改变时，该值标签依次累加。例如：SIB2的值标签为0，当该SIB2发生改变后，该值标签由0变为1。用户设备可以根据该值标签确定该SIB2发生改变。区域范围(areaScope)：用于标识该SIB是区域特定的(area specific)还是小区特定的(cell specific)。本申请实施例中，该参数可以是值标签和/或区域位置。该参数还可以包括其它参数，此处不做限制。
结合第二方面，在第二方面的一种可能的实现方式中，还包括：该CU向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。集中式单元 通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数，该系统信息块可以是变更后的系统信息块，该系统信息块也可以是未变更的系统信息块。本申请实施例中，在系统信息块变更或者未变更的情况下，集中式单元可以通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数。使得本方案可以适用于多种场景，提升了实现灵活性。
结合第二方面，在第二方面的一种可能的实现方式中，还包括：该CU接收该DU发送的第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。在另一种可选的实现方式中，该第四消息中携带变更后的系统信息块的指示信息。该变更后的系统信息块的指示信息，用于指示该分布式单元生成了变更后的系统信息块。本申请实施例中，当分布式单元中系统信息块发生变更后，分布式单元可以向集中式单元发送第四消息，该第四消息变更后的系统信息块或变更后的系统信息块的指示信息。分布式单元可以通过多种方法，告知集中式单元系统信息块发生变更。提升了本方案的实现灵活性。
结合第二方面，在第二方面的一种可能的实现方式中，该第一消息是F1建立请求消息，在另一种可选的实现方式中，该第一消息为新定义的F1消息，专用于承载系统信息块x消息(SIBx message)，示例性的，第一消息为上行系统信息块传输(UL SIB transfer)消息；该第二消息是F1建立响应消息，在另一种可选的实现方式中，该第二消息为新定义的F1消息，专用于承载上述的SIBx所关联的参数，示例性的，第二消息为下行系统信息块传输(DL SIB transfer)消息。
结合第二方面，在第二方面的一种可能的实现方式中，该第三消息是DU配置更新消息，在另一种可选的实现方式中，该第三消息为新定义的F1消息，专用于承载SIBx的关联参数；该第四消息是DU配置更新确认消息。在另一种可选的实现方式中，该第四消息为新定义的F1消息，专用于承载SIBx消息。
第三方面，本申请实施例提出了一种通信方法，包括：首先，分布式单元生成了系统信息块，在本申请实施例中，为了便于说明，该系统信息块称为“SIBx”。可选的，该系统信息块可以是5G-NR系统中的“SIB10”。其次，当分布式单元生成该系统信息块后，该分布式单元向集中式单元发送第五消息，该集中式单元管理该分布式单元。再次，该DU接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。具体的，该第五消息中携带系统信息块的指示信息。该系统信息块的指示信息用于表示该分布式单元生成了该系统信息块。在一种可选的实现方式中，该第五消息为F1建立请求消息(F1setup request)。具体的，该系统信息块的指示信息承载于该F1建立请求消息的第五信元内。该第五信元可以是：gNB-DU系统信息(gNB-DU System information)信元。每个第一信元对应一个小区，用以表示该小区的主信息块和系统信息块。在另一种可选的实现方式中，该系统信息块的指示信息可以是某个字段，示例性的，该字段为“SIBx”，当第五消息中包括字段“SIBx”，则指示该分布式单元生成了该系统信息块。该系统信息块的指示信息还可以是比特位，示例性的，当第五消息中的某个比特位为“01”，则指示该分布式单元生成了该系统信息块。此时，该第五消息可以为F1建立请求消息，该第五消息也可以为其他消息，此处不做限定。
本申请实施例提供了一种通信方法，当系统信息块由分布式单元生成时，分布式单元向集中式单元报告该系统信息块的指示信息，使得集中式单元能够知道该分布式单元生成了该系统信息块，从而该集中式单元为该系统信息块配置参数。并且，可以有效节约集中式单元与分布式单元之间的通信资源。
结合第三方面，在第三方面的一种可能的实现方式中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。例如：第二消息中携带值标签，或，第二消息中携带值标签和区域范围，或，第二消息中携带区域范围。具体的，值标签(valueTag)：用于标识SIB是否改变，DU通过该值标签告知用户设备，该值标签关联的SIB是否改变。具体的，该值标签为整数类型，该值标签的取值范围是{0-31}，当SIB改变时，该值标签依次累加。例如：SIB2的值标签为0，当该SIB2发生改变后，该值标签由0变为1。用户设备可以根据该值标签确定该SIB2发生改变。区域范围(areaScope)：用于标识该SIB是区域特定的(area specific)还是小区特定的(cell specific)。本申请实施例中，该参数可以是值标签和/或区域位置。该参数还可以包括其它参数，此处不做限制。
结合第三方面，在第三方面的一种可能的实现方式中，该DU接收该CU发送的该第二消息之后，还包括：DU基于该参数配置该SIB的相关参数。本申请实施例中，CU向DU发生该参数后，DU基于该参数配置该SIB的相关参数，使得DU中的用户设备可以获知该SIB是否发生改变，和/或，使得该DU获知该SIB的使用范围。
结合第三方面，在第三方面的一种可能的实现方式中，还包括：该DU接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。集中式单元通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数，该系统信息块可以是变更后的系统信息块，该系统信息块也可以是未变更的系统信息块。本申请实施例中，在系统信息块变更或者未变更的情况下，集中式单元可以通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数。使得本方案可以适用于多种场景，提升了实现灵活性。
结合第三方面，在第三方面的一种可能的实现方式中，该DU接收该CU发送的该第三消息之前，还包括：该DU向该CU发送第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。在另一种可选的实现方式中，变更后的系统信息块的指示信息可以是某个字段，示例性的，该字段为“SIBx-changed”，当第六消息中包括字段“SIBx-changed”，则指示该分布式单元所生成的该系统信息块发生了变更。该变更后的系统信息块的指示信息还可以是比特位，示例性的，当第六消息中的某个比特位为“011”，则指示该分布式单元所生成的该系统信息块发生了变更。此时，该第六消息可以为F1建立请求消息，该第六消息也可以为其他消息，此处不做限定。分布式单元可以通过多种方法，告知集中式单元系统信息块发生变更。提升了本方案的实现灵活性。并且，可以有效节约集中式单元与分布式单元之间的通信资源。
结合第三方面，在第三方面的一种可能的实现方式中，该第五消息是F1建立请求消息；该第二消息是F1建立响应消息。
结合第三方面，在第三方面的一种可能的实现方式中，该第三消息是DU配置更新消息； 该第六消息是DU配置更新确认消息。
第四方面，本申请实施例提出了一种通信方法，包括：
首先，集中式单元CU接收分布式单元DU发送的第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB。具体的，当分布式单元生成该系统信息块后，该分布式单元向集中式单元发送第五消息，该集中式单元管理该分布式单元。其次，该CU向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。具体的，该第五消息中携带系统信息块的指示信息。该系统信息块的指示信息用于表示该分布式单元生成了该系统信息块。在一种可选的实现方式中，该第五消息为F1建立请求消息(F1setup request)。具体的，该系统信息块的指示信息承载于该F1建立请求消息的第五信元内。该第五信元可以是：gNB-DU系统信息(gNB-DU System information)信元。每个第一信元对应一个小区，用以表示该小区的主信息块和系统信息块。在另一种可选的实现方式中，该系统信息块的指示信息可以是某个字段，示例性的，该字段为“SIBx”，当第五消息中包括字段“SIBx”，则指示该分布式单元生成了该系统信息块。该系统信息块的指示信息还可以是比特位，示例性的，当第五消息中的某个比特位为“01”，则指示该分布式单元生成了该系统信息块。此时，该第五消息可以为F1建立请求消息，该第五消息也可以为其他消息，此处不做限定。
本申请实施例提供了一种通信方法，当系统信息块由分布式单元生成时，分布式单元向集中式单元报告该系统信息块的指示信息，使得集中式单元能够知道该分布式单元生成了该系统信息块，从而该集中式单元为该系统信息块配置参数。并且，可以有效节约集中式单元与分布式单元之间的通信资源。
结合第四方面，在第四方面的一种可能的实现方式中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。例如：第二消息中携带值标签，或，第二消息中携带值标签和区域范围，或，第二消息中携带区域范围。具体的，值标签(valueTag)：用于标识SIB是否改变，DU通过该值标签告知用户设备，该值标签关联的SIB是否改变。具体的，该值标签为整数类型，该值标签的取值范围是{0-31}，当SIB改变时，该值标签依次累加。例如：SIB2的值标签为0，当该SIB2发生改变后，该值标签由0变为1。用户设备可以根据该值标签确定该SIB2发生改变。区域范围(areaScope)：用于标识该SIB是区域特定的(area specific)还是小区特定的(cell specific)。本申请实施例中，该参数可以是值标签和/或区域位置。该参数还可以包括其它参数，此处不做限制。
结合第四方面，在第四方面的一种可能的实现方式中，还包括：该CU向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。集中式单元通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数，该系统信息块可以是变更后的系统信息块，该系统信息块也可以是未变更的系统信息块。本申请实施例中，在系统信息块变更或者未变更的情况下，集中式单元可以通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数。使得本方案可以适用于多种场景，提升了实现灵活性。
结合第四方面，在第四方面的一种可能的实现方式中，还包括：该CU接收该DU发送 的第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。在另一种可选的实现方式中，变更后的系统信息块的指示信息可以是某个字段，示例性的，该字段为“SIBx-changed”，当第六消息中包括字段“SIBx-changed”，则指示该分布式单元所生成的该系统信息块发生了变更。该变更后的系统信息块的指示信息还可以是比特位，示例性的，当第六消息中的某个比特位为“011”，则指示该分布式单元所生成的该系统信息块发生了变更。此时，该第六消息可以为F1建立请求消息，该第六消息也可以为其他消息，此处不做限定。分布式单元可以通过多种方法，告知集中式单元系统信息块发生变更。提升了本方案的实现灵活性。并且，可以有效节约集中式单元与分布式单元之间的通信资源。
结合第四方面，在第四方面的一种可能的实现方式中，该第五消息是F1建立请求消息；该第二消息是F1建立响应消息。
结合第四方面，在第四方面的一种可能的实现方式中，该第三消息是DU配置更新消息；该第六消息是DU配置更新确认消息。
第五方面，本申请实施例提出一种通信装置，包括：
发送模块，用于向通信装置CU发送第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；
接收模块，用于接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
结合第五方面，在第五方面的一种可能的实现方式中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
结合第五方面，在第五方面的一种可能的实现方式中，
处理模块，用于基于该参数配置该SIB的相关参数。
结合第五方面，在第五方面的一种可能的实现方式中，
接收模块，还用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
结合第五方面，在第五方面的一种可能的实现方式中，
发送模块，还用于向该CU发送第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
结合第五方面，在第五方面的一种可能的实现方式中，该第一消息是F1建立请求消息；该第二消息是F1建立响应消息。
结合第五方面，在第五方面的一种可能的实现方式中，该第三消息是DU配置更新消息；该第四消息是DU配置更新确认消息。
第六方面，本申请实施例提出一种通信装置，包括：
接收模块，用于接收通信装置DU发送的第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；
发送模块，用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
结合第六方面，在第六方面的一种可能的实现方式中，该参数包括以下至少一个：值 标签valueTag、或区域范围areaScope。
结合第六方面，在第六方面的一种可能的实现方式中，
发送模块，还用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
结合第六方面，在第六方面的一种可能的实现方式中，
接收模块，还用于接收该DU发送的第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
结合第六方面，在第六方面的一种可能的实现方式中，该第一消息是F1建立请求消息；该第二消息是F1建立响应消息；该第三消息是DU配置更新消息；该第四消息是DU配置更新确认消息。
第七方面，本申请实施例提出一种通信装置，包括：
发送模块，用于向通信装置CU发送第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；
接收模块，用于接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
结合第七方面，在第七方面的一种可能的实现方式中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
结合第七方面，在第七方面的一种可能的实现方式中，处理模块，用于该DU基于该参数配置该SIB的相关参数。
结合第七方面，在第七方面的一种可能的实现方式中，接收模块，还用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
结合第七方面，在第七方面的一种可能的实现方式中，发送模块，还用于向该CU发送第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
结合第七方面，在第七方面的一种可能的实现方式中，该第五消息是F1建立请求消息；该第二消息是F1建立响应消息。
结合第七方面，在第七方面的一种可能的实现方式中，该第三消息是DU配置更新消息；该第六消息是DU配置更新确认消息。
第八方面，本申请实施例提出一种通信装置，包括：
接收模块，用于接收通信装置发送的第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；
发送模块，还用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
结合第八方面，在第八方面的一种可能的实现方式中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
结合第八方面，在第八方面的一种可能的实现方式中，
发送模块，还用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
结合第八方面，在第八方面的一种可能的实现方式中，接收模块，还用于接收该DU发送的第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
结合第八方面，在第八方面的一种可能的实现方式中，该第五消息是F1建立请求消息；该第二消息是F1建立响应消息。
结合第八方面，在第八方面的一种可能的实现方式中，该第三消息是DU配置更新消息；该第六消息是DU配置更新确认消息。
第九方面，本申请实施例提供了一种通信装置，该通信装置可以实现上述第一、或三方面所涉及方法中DU所执行的功能，或者实现上述第二、或四方面所涉及方法中CU所执行的功能。该通信装置包括处理器、存储器以及与该处理器连接的接收器和与该处理器连接的发射器；该存储器用于存储程序代码，并将该程序代码传输给该处理器；该处理器用于根据该程序代码中的指令驱动该接收器和该发射器执行如上述第一、二、三、或四方面该的方法；接收器和发射器分别与该处理器连接，以执行上述各个方面的该的方法中该CU或者DU的操作。具体地，发射器可以进行发送的操作，接收器可以进行接收的操作。可选的，该接收器与发射器可以是射频电路，该射频电路通过天线实现接收与发送消息；该接收器与发射器还可以是通信接口，处理器与该通信接口通过总线连接，该处理器通过该通信接口实现接收或发送消息。
第十方面，本申请实施例提供一种通信装置，该通信装置可以包括网络设备或者芯片等实体，该通信装置包括：处理器，存储器；该存储器用于存储指令；该处理器用于执行该存储器中的该指令，使得该通信装置执行如前述第一方面或第二方面或第三方面或第四方面中任一项该的方法。
第十一方面，本申请实施例提供了一种存储一个或多个计算机执行指令的计算机可读存储介质，当该计算机执行指令被处理器执行时，该处理器执行如前述第一方面或第二方面或第三方面或第四方面中任意一种可能的实现方式。
第十二方面，本申请实施例提供一种存储一个或多个计算机执行指令的计算机程序产品(或称计算机程序)，当该计算机执行指令被该处理器执行时，该处理器执行前述第一方面或第二方面或第三方面或第四方面中任意一种可能的实现方式。
第十三方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持计算机设备实现上述方面中所涉及的功能。在一种可能的设计中，该芯片系统还包括存储器，该存储器，用于保存计算机设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十四方面，本申请提供了一种通信系统，该通信系统包括如上述第八方面或第九方面中的通信装置。
附图说明
图1为一种通信系统的网络架构示意图；
图2为通信系统中采用CU-DU的架构示意图；
图3为CU的一种架构示意图；
图4为本申请实施例中网络设备的硬件结构示意图；
图5a为本申请实施例提出的一种通信方法的实施例示意图；
图5b为本申请实施例提出的一种应用场景示意图；
图5c为本申请实施例提出的又一种应用场景示意图；
图6a为本申请实施例提供的另一种通信方法的实施例示意图；
图6b为本申请实施例提出的又一种应用场景示意图；
图6c为本申请实施例提出的又一种应用场景示意图；
图7为本申请实施例中通信装置的一种实施例示意图；
图8为本申请实施例中通信装置的又一种实施例示意图；
图9为本申请实施例中通信装置的又一种实施例示意图；
图10为本申请实施例中通信装置的又一种实施例示意图。
具体实施方式
本申请实施例提供了一种通信方法，当系统信息块由分布式单元生成时，分布式单元向集中式单元报告该系统信息块，使得集中式单元能够知道该分布式单元生成了该系统信息块，从而该集中式单元为该系统信息块配置参数。
本申请的说明书和权利要求书及上述附图中的术语“第一”、第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
下面结合附图，对本申请的实施例进行描述。
图1为一种通信系统的网络架构示意图。通信系统包括接入网和核心网。接入网可以是下一代无线接入网络(next generation radio access network，NG-RAN)，核心网可以是5G核心网(5G Core Network，5GC)。接入网可以包括接入网设备(例如，gNB)，gNB之间通过接口(例如Xn接口)连接。gNB和5GC通过接口(例如：Ng接口)连接。核心网可以包括接入与移动性管理功能(access and mobility management function，AMF)。核心网还可以包括用户面功能(user plane function，UPF)。图2为通信系统中采用CU-DU的架构示意图。如图2所示，接入网设备可以包括集中式单元(Centralized Unit，CU)和分布式单元(Distributed Unit，DU)。接入网设备的功能进行了拆分，接入网设备的部分功能部署在一个CU，接入网设备的另外部分功能部署在DU。DU的数量可以是一个或多个。多个DU可以共用一个CU，以节省成本，易于网络扩展。CU和DU之间通过接口(例如，F1接口)连接。CU代表接入网设备通过接口(例如，Ng接口)和核心网连接。CU和DU的功能切分可以按照协议栈进行切分。其中一种可能的方式是将无线资源控制(radio resource control，RRC)以及分组数据汇聚协议(packet data convergence protocol，PDCP)层和业务数据适应(Service Data Adaptation Protocol，SDAP)层部署在CU。无线链路层控制协议(Radio Link Control，RLC)、媒体接入控制(Media Access Control，MAC)、物理层(physical layer， PHY)部署在DU。相应地，CU具有RRC、PDCP和SDAP的处理能力。DU具有RLC、MAC、和PHY的处理能力。值得注意的是，上述功能切分只是一个例子，还有可能有其他切分的方式。例如，CU包括RRC、PDCP、RLC和SDAP的处理能力，DU具有MAC、和PHY的处理能力。又例如CU包括RRC、PDCP、RLC、SDAP和部分MAC(例如加MAC包头)的处理能力，DU具有PHY和部分MAC(例如调度)的处理能力。CU、DU的名字可能会发生变化，只要能实现上述功能的接入网节点都可以看做是本专利申请中的CU、DU。
图3为CU的一种架构示意图。如图3所示，CU包括控制面CU(CU-CP)和用户面CU(CU-+
UP)。CU-CP和CU-UP可以在不同的物理设备上。CU-CP和CU-UP也可以在相同的物理设备上。CU-CP和CU-UP通过接口(例如，E1接口)连接。CU-CP代表接入网设备通过接口(例如，Ng接口)和核心网连接。CU-CP通过接口(例如，F1-C接口)和DU连接，CU-UP通过接口(例如：F1-U接口)和DU连接。CU-CP的数量可以是一个，CU-UP的数量可以是一个或多个。多个CU-UP可以共用一个CU-CP。CU-CP主要具有控制面功能。CU-UP主要具有用户面功能。其中一种可能的实现方式为：对于5G的接入网设备，RRC层可以部署在CU-CP，而SDAP层不部署在CU-CP。CU-CP还可以具有PDCP层的控制面部分功能，例如可以进行信令无线承载(signaling radio bearer，SRB)的处理。SDAP层可以部署在CU-UP，但RRC层不部署在CU-UP。CU-UP还可以具有PDCP层的用户面部分功能，例如进行数据无线承载(DRB)的处理。
图4为本申请实施例中通信装置的硬件结构示意图。该通信装置可以是本申请实施例中CU或DU的一种可能的实现方式。如图4所示，通信装置至少包括处理器402，存储器403，和收发器404，存储器403进一步用于存储指令4032和数据4034。可选的，该通信装置还可以包括天线406，I/O(输入/输出，Input/Output)接口410和总线412。收发器404进一步包括发射器4042和接收器4044。此外，处理器402，收发器404，存储器403和I/O接口410通过总线412彼此通信连接，天线406与收发器404相连。
处理器402可以是通用处理器，例如但不限于，中央处理器(Central Processing Unit，CPU)，也可以是专用处理器，例如但不限于，数字信号处理器(Digital Signal Processor，DSP)，应用专用集成电路(Application Specific Integrated Circuit，ASIC)和现场可编程门阵列(Field Programmable Gate Array，FPGA)等。此外，处理器402还可以是多个处理器的组合。特别的，在本申请实施例提供的技术方案中，处理器402可以用于执行，后续方法实施例中通信方法的相关步骤。处理器402可以是专门设计用于执行上述步骤和/或操作的处理器，也可以是通过读取并执行存储器403中存储的指令4032来执行上述步骤和/或操作的处理器，处理器402在执行上述步骤和/或操作的过程中可能需要用到数据4034。
收发器404包括发射器4042和接收器4044，在一种可选的实现方式中，发射器4042用于通过天线406发送信号。接收器4044用于通过天线406之中的至少一根天线接收信号。特别的，在本申请实施例提供的技术方案中，发射器4042具体可以用于通过天线406之中的至少一根天线执行，例如，后续方法实施例中通信方法应用于CU或DU时，CU或DU中接收模块或发送模块所执行的操作。
在本申请实施例中，收发器404用于支持通信装置执行前述的接收功能和发送功能。 将具有处理功能的处理器视为处理器402。接收器4044也可以称为接收机、输入口、接收电路等，发射器4042可以称为发射机、发射器或者发射电路等。
处理器402可用于执行该存储器403存储的指令，以控制收发器404接收消息和/或发送消息，完成本申请方法实施例中通信装置的功能。作为一种实现方式，收发器404的功能可以考虑通过收发电路或者收发的专用芯片实现。
存储器403可以是各种类型的存储介质，例如随机存取存储器(Random Access Memory，RAM)，只读存储器(Read Only Memory，ROM)，非易失性RAM(Non-Volatile RAM，NVRAM)，可编程ROM(Programmable ROM，PROM)，可擦除PROM(Erasable PROM，EPROM)，电可擦除PROM(Electrically Erasable PROM，EEPROM)，闪存，光存储器和寄存器等。存储器403具体用于存储指令4032和数据4034，处理器402可以通过读取并执行存储器403中存储的指令4032，来执行本申请方法实施例中所述的步骤和/或操作，在执行本申请方法实施例中操作和/或步骤的过程中可能需要用到数据4034。
可选的，该通信装置还可以包括I/O接口410，该I/O接口410用于接收来自外围设备的指令和/或数据，以及向外围设备输出指令和/或数据。
下面介绍本申请实施例的方法部分，请参阅图5a，图5a为本申请实施例提出的一种通信方法的实施例示意图。本申请实施例提出的一种通信方法包括：
501、分布式单元向集中式单元发送第一消息，第一消息中携带系统信息块。
本实施例中，在步骤501之前，还可以包括步骤500：分布式单元生成系统信息块，为了便于说明，该系统信息块称为“SIBx”。该分布式单元的具体组成和通信方式，与前述图1-图4所描述的分布式单元类似，此处不再赘述。具体的，该分布式单元生成该系统信息块“SIBx”可以是：该分布式单元负责编码生成该系统信息块SIBx(the gNB-DU is responsible for the encoding of SIBx)。可选的，在5G-NR系统中，该系统信息块可以是“SIB10”。
当分布式单元生成该系统信息块后，该分布式单元向集中式单元发送第一消息，该集中式单元管理该分布式单元。
在一种可选的实现方式中，该第一消息为F1建立请求消息(F1setup request)。具体的，该系统信息块承载于该F1建立请求消息的第一信元内。该第一信元可以是：gNB-DU系统信息(gNB-DU system information)信元。每个第一信元对应一个小区，用以表示该小区的主信息块消息和系统信息块消息。以第一信元为gNB-DU系统信息信元为例，该第一信元可以携带如表1所示的信息：
Figure PCTCN2021094486-appb-000001
表1
其中，表1中，信元类型中的字符串描述的是主信息块或系统信息块的完整内容。当该第一消息是F1建立请求消息时，该F1建立请求消息中包含了该分布式单元中所有小区的MIB、SIB1、SIBx，该SIBx与其中的某个小区相关联。
在另一种可选的实现方式中，该第一消息为新定义的F1消息，专用于承载上述系统信息块x消息(SIBx message)，系统信息块x消息(SIBx message)的内容，为该SIBx按照3GPP约定的编码方式进行编码所生成的字符串。示例性的，第一消息为上行系统信息块传输(UL SIB transfer)消息。
502、分布式单元接收集中式单元发送的第二消息，第二消息中携带参数。
本实施例中，分布式单元接收集中式单元发送的第二消息，该第二消息中携带参数。在一种可选的实现方式中，该参数以下至少一项：值标签(valueTag)、或区域范围(areaScope)。例如：第二消息中携带值标签，或，第二消息中携带值标签和区域范围，或，第二消息中携带区域范围。
具体的，值标签(valueTag)：用于标识SIB是否改变，DU通过该值标签告知用户设备，该值标签关联的SIB是否改变。该值标签为整数。可选的，该值标签的取值范围是{0-31}，当SIB改变时，该值标签依次累加。示例性的：SIBx的值标签为0，当该SIBx发生改变后，该值标签由0变为1。用户设备可以根据该值标签确定该SIBx发生改变。
区域范围(areaScope)：用于标识该SIB是区域特定的(area specific)还是小区特定的(cell specific)。
在一种可选的实现方式中，该第二消息为F1建立响应消息(F1setup response)。具体的，该参数承载于该F1建立响应消息中的第二信元。可选的，该第二信元可以是待更新SIB类型项信元(SIB type to Be Updated Item IE)，其中，在该信元中“SIBx”对应的系统信息块消息(SIB message)为空。该F1建立响应消息携带小区的配置信息，该小区为该分布式单元所管理的需要激活的小区。以第二信元为待更新SIB类型项信元为例，该第二信元可以携带如表2所示的信息：
Figure PCTCN2021094486-appb-000002
表2
可选的，该第二信元可以是其他待更新SIB类型项信元(additional SIB type to Be Updated Item IEs)，其中，在该信元中“SIBx”所对应的系统信息块消息(SIB message)为空。以第二信元为其他待更新SIB类型项信元为例，该第二信元可以携带如表3所示的信息：
Figure PCTCN2021094486-appb-000003
表3
在另一种可选的实现方式中，该第二消息为新定义的F1消息，专用于承载上述的SIBx所关联的参数。示例性的，第二消息为下行系统信息块传输(DL SIB transfer)消息。
在一种可选的实现方式中，集中式单元可以为一部分的分布式单元发送该SIBx的参数，即由集中式单元确定为哪些分布式单元配置参数(这些分布式单元生成该SIBx)；在另一种可选的实现方式中，集中式单元可以为所有配置了该SIBx的分布式单元配置参数。
503、分布式单元向集中式单元发送第四消息，第四消息携带变更后的系统信息块。
本实施例中，当分布式单元中系统信息块发生变更后，分布式单元向集中式单元发送第四消息，该第四消息携带变更后的系统信息块。
可选的，该第四消息为DU配置更新(gNB-DU configuration update)消息，该消息中携带变更后的系统信息块。
在另一种可选的实现方式中，该第四消息中携带变更后的系统信息块的指示信息。该变更后的系统信息块的指示信息，用于指示该分布式单元生成了变更后的系统信息块(与 步骤501的系统信息块相比较)。
在另一种可选的实现方式中，该第四消息为新定义的F1消息，专用于承载SIBx消息。
当分布式单元向集中式单元发送第四消息后，该集中式单元基于该第四消息，向该分布式单元发送第三消息，进入步骤504。
需要说明的是，步骤503为可选步骤，集中式单元也可以在不接收第四消息的前提下，向该分布式单元发送第三消息，该第三消息中携带变更后的参数。即，在分布式单元中该系统信息块不发生变更的前提下，集中式单元向分布式单元配置变更后的参数。
504、分布式单元接收集中式单元发送的第三消息，第三消息中携带变更后的参数。
本实施例中，集中式单元通过向分布式单元发送第三消息，向该分布式单元中的该系统信息块配置变更后的参数，该系统信息块可以是变更后的系统信息块，该系统信息块也可以是未变更的系统信息块。
在步骤504中，该系统信息块是否发生变更，是相对于步骤501中的系统信息块而言的。具体的，系统信息块发生变更，是指SIB的内容发生了变更，即SIB message中的字符串发生改变。
可选的，该第三消息可以为DU配置更新确认(gNB-DU configuration update acknowledge)消息。具体的，该变更后的参数承载于第三消息中的第三信元内。该第三信元与前述步骤502中的第二信元类似，此处不再赘述。需要说明的是，该第三信元与前述第二信元相比，携带的参数可能发生变更。示例性的，第二信元中携带值标签{21}，第三信元中携带值标签{22}。在一种可选的实现方式中，第三信元与第二信元也可以不一致，示例性的，第三信元可以是待更新SIB类型项信元，第二信元可以是其他待更新SIB类型项信元。
在另一种可选的实现方式中，该第三消息为新定义的F1消息，专用于承载SIBx的关联参数。
本申请实施例提供了一种通信装置，当系统信息块在分布式单元中生成或者发生变更时，分布式单元向集中式单元报告生成的或者变更后的系统信息块，集中式单元根据该报告可以获知该系统信息块已经生成或者发生了变更，从而可以为该系统信息块配置参数。该方法适用于在分布式单元中生成的系统信息块、该系统信息块由集中式单元配置参数，通过使用该方法，分布式单元可以获得系统信息块的配置参数，从而能够在小区中广播该系统信息块的配置参数。
请参阅图5b，图5b为本申请实施例提供的一种通信方法的示意图。该方法包括：
S1、分布式单元生成SIBx。
步骤S1中，分布式单元生成SIBx。
S2、分布式单元向集中式单元发送F1建立请求消息，该F1建立请求消息包括SIBx。
步骤S2中，分布式单元向集中式单元发送F1建立请求消息，该F1建立请求消息包括SIBx。示例性的，该SIBx的内容为“ABCD”，该F1建立请求消息如表4：
Figure PCTCN2021094486-appb-000004
Figure PCTCN2021094486-appb-000005
表4
S3、分布式单元接收集中式单元发送的F1建立响应消息，该F1建立响应消息包括SIBx的值标签和区域位置。
步骤S3中，示例性的，该F1建立响应消息如表5：
Figure PCTCN2021094486-appb-000006
表5
S4、分布式单元配置SIBx的值标签和区域位置。
在图5b所示应用场景的基础上，请参阅图5c，图5c为本申请实施例提供的又一种应用场景示意图。本申请实施例提供的又一种应用场景包括：
D1、分布式单元SIBx发生变更。
步骤D1中，SIBx发生变更，示例性的，步骤S1中分布式单元生成的SIBx的字符串为“ABCD”，发生变更后的该SIBx为“abc”。
D2、分布式单元向集中式单元发送DU配置更新消息，该DU配置更新消息包括变更后的SIBx。
步骤D2中，该DU配置更新消息如表6：
Figure PCTCN2021094486-appb-000007
表6
D3、分布式单元接收集中式单元发送的DU配置更新确认消息，该DU配置更新确认消 息包括变更后的SIBx的值标签和区域位置。
步骤D3中，该DU配置更新消息如表7：
Figure PCTCN2021094486-appb-000008
表7
D4、分布式单元配置变更后的SIBx的值标签和区域位置。
请参阅图6a，图6a为本申请实施例提供的另一种通信方法的实施例示意图。本申请实施例提出的一种通信方法还包括：
601、分布式单元向集中式单元发送第五消息，第五消息中携带系统信息块的指示信息。
本实施例中，在步骤601之前，还可以包括步骤600：分布式单元生成系统信息块，为了便于说明，该系统信息块称为“SIBx”。该分布式单元的具体组成和通信方式，与前述图1-图4所描述的分布式单元类似，此处不再赘述。可选的，该系统信息块可以是5G-NR系统中的“SIB10”。
其次，当分布式单元生成该系统信息块后，该分布式单元向集中式单元发送第五消息，该集中式单元管理该分布式单元。该第五消息中携带系统信息块的指示信息。该系统信息块的指示信息用于表示该分布式单元生成了该系统信息块。
在一种可选的实现方式中，该第五消息为F1建立请求消息(F1setup request)。具体的，该系统信息块的指示信息承载于该F1建立请求消息的第五信元内。该第五信元可以是：gNB-DU系统信息(gNB-DU system information)信元。每个第一信元对应一个小区，用以表示该小区的主信息块和系统信息块。以第五信元为gNB-DU系统信息信元为例，该第五信元可以携带如表8所示的信息：
Figure PCTCN2021094486-appb-000009
Figure PCTCN2021094486-appb-000010
表8
在另一种可选的实现方式中，该系统信息块的指示信息可以是某个字段，示例性的，该字段为“SIBx”，当第五消息中包括字段“SIBx”，则指示该分布式单元生成了该系统信息块。该系统信息块的指示信息还可以是比特位，示例性的，当第五消息中的某个比特位为“01”，则指示该分布式单元生成了该系统信息块。此时，该第五消息可以为F1建立请求消息，该第五消息也可以为其他消息，此处不做限定。
可选的，该第五消息与前述第一消息类似，也可以是新定义的F1建立请求消息。示例性的，上行系统信息块传输(UL SIB transfer)消息。
602、分布式单元接收集中式单元发送的第二消息，第二消息中携带参数。
步骤602与前述步骤502类似，此处不再赘述。
603、分布式单元向集中式单元发送第六消息，第六消息携带变更后的系统信息块的指示信息。
本实施例中，分布式单元向集中式单元发送第六消息，该第六消息携带变更后的系统信息块的指示信息。
可选的，该第六消息为DU配置更新(gNB-DU configuration update)消息。DU配置更新消息中携带变更后的系统信息块的指示信息，该指示信息用于指示分布式单元中的系统信息块(SIBx)发生了变更。在一种可选的实现方式中，该变更后的系统信息块的指示信息具体承载于DU配置更新消息中的第六信元内。该第六信元与前述第五信元类似，该第六信元可以携带如表9所示的信息：
Figure PCTCN2021094486-appb-000011
表9
在另一种可选的实现方式中，该第六信元还可以携带如表10所示的信息：
Figure PCTCN2021094486-appb-000012
表10
在另一种可选的实现方式中，变更后的系统信息块的指示信息可以是某个字段，示例性的，该字段为“SIBx-changed”，当第六消息中包括字段“SIBx-changed”，则指示该分布式单元所生成的该系统信息块发生了变更。该变更后的系统信息块的指示信息还可以是比特位，示例性的，当第六消息中的某个比特位为“011”，则指示该分布式单元所生成的该系统信息块发生了变更。此时，该第六消息可以为F1建立请求消息，该第六消息也可以为其他消息，此处不做限定。
在另一种可选的实现方式中，该第六消息也可以携带完整的变更后的系统信息块。
604、分布式单元接收集中式单元发送的第三消息，第三消息中携带变更后的参数。
本实施例与前述步骤504类似，此处不再赘述。
本申请实施例提供了一种通信方法，当系统信息块由分布式单元生成或变更时，分布式单元向集中式单元报告该系统信息块的指示信息，使得集中式单元能够知道该分布式单元生成或变更了该系统信息块，从而该集中式单元为该系统信息块配置参数。该方法适用于在分布式单元中生成的系统信息块、该系统信息块由集中式单元配置参数，通过使用该方法，分布式单元可以获得系统信息块的配置参数，从而能够在小区中广播该系统信息块的配置。并且，可以有效节约集中式单元与分布式单元之间的通信资源。
在图6a所示实施例的基础上，请参阅图6b，图6b为本申请实施例提供的一种应用场景示意图。本申请实施例提供的一种应用场景包括：
F1、分布式单元生成SIBx。
步骤F1与步骤S1类似，此处不再赘述。
F2、分布式单元向集中式单元发送F1建立请求消息，该F1建立请求消息包括SIBx的指示信息。
步骤F2中，示例性的，该F1建立请求消息如表11所示的信息：
Figure PCTCN2021094486-appb-000013
Figure PCTCN2021094486-appb-000014
表11
F3、分布式单元接收集中式单元发送的F1建立响应消息，该F1建立响应消息包括SIBx的值标签和区域位置。
步骤F3与前述步骤S3类似，此处不再赘述。
F4、分布式单元配置SIBx的值标签和区域位置。
在图6b所示应用场景的基础上，请参阅图6c，图6c为本申请实施例提供的又一种应用场景示意图。本申请实施例提供的又一种应用场景包括：
G1、分布式单元SIBx发生变更。
步骤G1与步骤D1类似，此处不再赘述。
G2、分布式单元向集中式单元发送DU配置更新消息，该DU配置更新消息包括变更后的SIBx的指示信息。
步骤G2中，该DU配置更新消息如表12所示的信息：
Figure PCTCN2021094486-appb-000015
表12
G3、分布式单元接收集中式单元发送的DU配置更新确认消息，该DU配置更新确认消息包括变更后的SIBx的值标签和区域位置。
G4、分布式单元配置变更后的SIBx的值标签和区域位置。
上述主要以方法的角度对本申请实施例提供的方案进行了介绍。可以理解的是，通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个收发模块中。 上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
下面对本申请中的通信装置进行详细描述，请参阅图7，图7为本申请实施例中通信装置的一种实施例示意图。通信装置700可以部署于分布式单元中，通信装置700包括：
发送模块701，用于向集中式单元CU发送第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；
接收模块702，用于接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
在本申请的一些可选实施例中，处理模块703，用于基于该参数配置该SIB的相关参数。
在本申请的一些可选实施例中，接收模块702，还用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
在本申请的一些可选实施例中，发送模块701，还用于向该CU发送第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
在本申请的一些可选实施例中，该第一消息是F1建立请求消息。
在本申请的一些可选实施例中，该第二消息是F1建立响应消息。
在本申请的一些可选实施例中，该第三消息是DU配置更新消息。
在本申请的一些可选实施例中，该第四消息是DU配置更新确认消息。
请参阅图8，图8为本申请实施例中通信装置的又一种实施例示意图。通信装置800可以部署于集中式单元中，通信装置800包括：
接收模块801，用于接收分布式单元发送的第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；
发送模块802，用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
在本申请的一些可选实施例中，发送模块802，还用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
在本申请的一些可选实施例中，接收模块801，还用于接收该DU发送的第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
在本申请的一些可选实施例中，该第一消息是F1建立请求消息。
在本申请的一些可选实施例中，该第二消息是F1建立响应消息。
在本申请的一些可选实施例中，该第三消息是DU配置更新消息。
在本申请的一些可选实施例中，该第四消息是DU配置更新确认消息。
请参阅图9，图9为本申请实施例中通信装置的又一种实施例示意图。通信装置900可以部署于分布式单元中，通信装置900包括：
发送模块901，用于向集中式单元CU发送第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；
接收模块902，用于接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
在本申请的一些可选实施例中，处理模块903，用于基于该参数配置该SIB的相关参数。
在本申请的一些可选实施例中，接收模块902，还用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
在本申请的一些可选实施例中，发送模块901，还用于向该CU发送第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
在本申请的一些可选实施例中，该第五消息是F1建立请求消息。
在本申请的一些可选实施例中，该第二消息是F1建立响应消息。
在本申请的一些可选实施例中，该第三消息是DU配置更新消息。
在本申请的一些可选实施例中，该第六消息是DU配置更新确认消息。
请参阅图10，图10为本申请实施例中通信装置的又一种实施例示意图。通信装置1000可以部署于集中式单元中，通信装置1000包括：
接收模块1001，用于接收分布式单元发送的第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；
发送模块1002，用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
在本申请的一些可选实施例中，发送模块1002，还用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
在本申请的一些可选实施例中，接收模块1001，还用于接收该DU发送的第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
在本申请的一些可选实施例中，该第五消息是F1建立请求消息。
在本申请的一些可选实施例中，该第二消息是F1建立响应消息。
在本申请的一些可选实施例中，该第三消息是DU配置更新消息。
在本申请的一些可选实施例中，该第六消息是DU配置更新确认消息。
上述实施例中的通信装置，可以是网络设备，也可以是应用于网络设备中的芯片或者其他可实现上述网络设备功能的组合器件、部件等。当通信装置是网络设备时，接收模块与发送模块可以是收发器，该收发器可以包括天线和射频电路等，处理模块可以是处理器，例如基带芯片等。当通信装置是具有上述网络设备功能的部件时，接收模块与发送模块可 以是射频单元，处理模块可以是处理器。当通信装置是芯片系统时，接收模块可以是芯片系统的输入端口，发送模块可以是芯片系统的输出接口、处理模块可以是芯片系统的处理器，例如：中央处理器(central processing unit，CPU)。
在本申请实施例中，该通信装置所包括的存储器主要用于存储软件程序和数据，例如存储上述实施例中所描述的第一消息和第二消息等。该通信装置所包括的处理器还具有以下功能：
收发器，用于向集中式单元CU发送第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；
接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
处理器，用于基于该参数配置该SIB的相关参数，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
收发器，还用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
收发器，还用于向该CU发送第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
在本申请实施例中，该网络设备所包括的收发器还具有以下功能：
用于接收分布式单元发送的第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；
用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，
收发器，还用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
收发器，还用于接收该DU发送的第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
在本申请实施例中，该网络设备所包括的收发器还具有以下功能：
向集中式单元CU发送第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；
接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
处理器，还用于基于该参数配置该SIB的相关参数。
收发器，还用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
收发器，还用于向该CU发送第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
在本申请实施例中，该网络设备所包括的收发器还具有以下功能：
用于接收分布式单元发送的第五消息，该第五消息中携带系统信息块SIB的指示信息， 该SIB的指示信息用于指示该DU生成了该SIB；
用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
在本申请的一些可选实施例中，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
收发器，还用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
收发器，还用于接收该DU发送的第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器，用于执行上述任一方法实施例所述的通信方法。
应理解，上述处理装置可以是一个芯片，所述处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于所述处理器之外，独立存在。
本申请还提供一种通信系统，其包括CU和DU。
本申请实施例还提供的一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行：
步骤A：向集中式单元CU发送第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
步骤B：用于基于该参数配置该SIB的相关参数，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
步骤C：用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
步骤D：用于向该CU发送第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
和/或，
步骤E：用于接收分布式单元发送的第一消息，该第一消息中携带系统信息块SIB，该SIB由该DU生成；用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
步骤F：用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联，该参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
步骤G：用于接收该DU发送的第四消息，该第四消息携带变更后的该SIB，该变更后的该SIB由该DU生成。
和/或，
步骤H：向集中式单元CU发送第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；接收该CU发送的第二消息，该第二消息中携带参数，该参数与该SIB关联。
步骤I：用于基于该参数配置该SIB的相关参数,该参数包括以下至少一个：值标签 valueTag、或区域范围areaScope。
步骤J：用于接收该CU发送的第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联。
步骤K：用于向该CU发送第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
和/或，
步骤L：用于接收分布式单元发送的第五消息，该第五消息中携带系统信息块SIB的指示信息，该SIB的指示信息用于指示该DU生成了该SIB；用于向该DU发送第二消息，该第二消息中携带参数，该参数与该SIB关联。
步骤M：用于向该DU发送第三消息，该第三消息携带变更后的该参数，该变更后的该参数与该SIB关联，该参数包括以下至少一项值标签valueTag、或区域范围areaScope。
步骤N：用于接收该DU发送的第六消息，该第六消息携带变更后的该SIB的指示信息，该变更后的该SIB由该DU生成。
本申请实施例还提供的一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述步骤A-D，和/或步骤E-G，和/或步骤H-K，和/或步骤L-N。
本申请实施例还提供一种芯片，包括存储器和处理器，所述存储器用于存储计算机程序，所述处理器用于从所述存储器中调用并运行所述计算机程序，使得芯片执行上述步骤A-D，和/或步骤E-G，和/或步骤H-K，和/或步骤L-N。
本申请实施例还提供一种芯片，包括处理器，所述处理器用于调用并运行计算机程序，使得芯片执行步骤A-D，和/或步骤E-G，和/或步骤H-K，和/或步骤L-N。
另外需说明的是，以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本申请提供的装置实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下，凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现，而且，用来实现同一功能的具体硬件结构也可以是多种多样的，例如模拟电路、数字电路或专用电路等。但是，对本申请而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘、U盘、移动硬盘、ROM、RAM、磁碟或者光盘等，包括若干指令用以使得一台计算机设备执行本申请各个实施例所述的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。 当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、通信装置、计算设备或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、通信装置、计算设备或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的通信装置、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨 论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。
总之，以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (31)

  1. 一种通信方法，其特征在于，包括：
    分布式单元DU向集中式单元CU发送第一消息，所述第一消息中携带系统信息块SIB，所述SIB由所述DU生成；
    所述DU接收所述CU发送的第二消息，所述第二消息中携带参数，所述参数与所述SIB关联。
  2. 根据权利要求1所述的方法，其特征在于，
    所述参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
  3. 根据权利要求1或2所述的方法，其特征在于，所述DU接收所述CU发送的所述第二消息之后，所述方法还包括：
    所述DU基于所述参数配置所述SIB的相关参数。
  4. 根据权利要求1-3中任一所述的方法，其特征在于，所述方法还包括：
    所述DU接收所述CU发送的第三消息，所述第三消息携带变更后的所述参数，所述变更后的所述参数与所述SIB关联。
  5. 根据权利要求4所述的方法，其特征在于，所述DU接收所述CU发送的所述第三消息之前，所述方法还包括：
    所述DU向所述CU发送第四消息，所述第四消息携带变更后的所述SIB，所述变更后的所述SIB由所述DU生成。
  6. 根据权利要求1-5任一所述的方法，其特征在于，
    所述第一消息是F1建立请求消息；
    所述第二消息是F1建立响应消息。
  7. 根据权利要求5所述的方法，其特征在于，
    所述第三消息是DU配置更新消息；
    所述第四消息是DU配置更新确认消息。
  8. 一种通信方法，其特征在于，包括：
    集中式单元CU接收分布式单元DU发送的第一消息，所述第一消息中携带系统信息块SIB，所述SIB由所述DU生成；
    所述CU向所述DU发送第二消息，所述第二消息中携带参数，所述参数与所述SIB关联。
  9. 根据权利要求8所述的方法，其特征在于，
    所述参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述CU向所述DU发送第三消息，所述第三消息携带变更后的所述参数，所述变更后的所述参数与所述SIB关联。
  11. 根据权利要求10所述的方法，其特征在于，所述CU向所述DU发送所述第三消息之前，所述方法还包括：
    所述CU接收所述DU发送的第四消息，所述第四消息携带变更后的所述SIB，所述变 更后的所述SIB由所述DU生成。
  12. 根据权利要求8-11任一项所述的方法，其特征在于，
    所述第一消息是F1建立请求消息；
    所述第二消息是F1建立响应消息。
  13. 根据权利要求11所述的方法，其特征在于，
    所述第三消息是DU配置更新消息；
    所述第四消息是DU配置更新确认消息。
  14. 一种通信装置，其特征在于，包括：处理器、存储器以及与所述处理器连接的接收器和与所述处理器连接的发射器；
    所述存储器用于存储程序代码，并将所述程序代码传输给所述处理器；
    所述处理器用于根据所述程序代码中的指令，驱动所述接收器和所述发射器执行如权利要求1-7所述的方法；
    所述发射器，用于向集中式单元CU发送第一消息，所述第一消息中携带系统信息块SIB，所述SIB由所述DU生成；
    所述接收器，用于接收所述CU发送的第二消息，所述第二消息中携带参数，所述参数与所述SIB关联。
  15. 一种通信装置，其特征在于，包括：处理器、存储器以及与所述处理器连接的接收器和与所述处理器连接的发射器；
    所述存储器用于存储程序代码，并将所述程序代码传输给所述处理器；
    所述处理器用于根据所述程序代码中的指令，驱动所述接收器和所述发射器执行如权利要求8-13所述的方法；
    所述接收器，用于接收分布式单元DU发送的第一消息，所述第一消息中携带系统信息块SIB，所述SIB由所述DU生成；
    所述发射器，用于向所述DU发送第二消息，所述第二消息中携带参数，所述参数与所述SIB关联。
  16. 一种通信装置，其特征在于，包括：接收模块和发送模块；
    所述发送模块，用于向集中式单元CU发送第一消息，所述第一消息中携带系统信息块SIB，所述SIB由所述DU生成；
    所述接收模块，用于接收所述CU发送的第二消息，所述第二消息中携带参数，所述参数与所述SIB关联。
  17. 根据权利要求16所述的通信装置，其特征在于，
    所述参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
  18. 根据权利要求16或17所述的通信装置，其特征在于，还包括：处理模块；
    所述处理模块，用于基于所述参数配置所述SIB的相关参数。
  19. 根据权利要求16-18中任一所述的通信装置，其特征在于，还包括：
    所述接收模块，还用于接收所述CU发送的第三消息，所述第三消息携带变更后的所述参数，所述变更后的所述参数与所述SIB关联。
  20. 根据权利要求19所述的通信装置，其特征在于，还包括：
    所述发送模块，还用于向所述CU发送第四消息，所述第四消息携带变更后的所述SIB，所述变更后的所述SIB由所述DU生成。
  21. 根据权利要求16-20任一所述的通信装置，其特征在于，
    所述第一消息是F1建立请求消息；
    所述第二消息是F1建立响应消息。
  22. 根据权利要求20所述的通信装置，其特征在于，
    所述第三消息是DU配置更新消息；
    所述第四消息是DU配置更新确认消息。
  23. 一种通信装置，其特征在于，包括：接收模块和发送模块；
    所述接收模块，用于接收分布式单元DU发送的第一消息，所述第一消息中携带系统信息块SIB，所述SIB由所述DU生成；
    所述发送模块，用于向所述DU发送第二消息，所述第二消息中携带参数，所述参数与所述SIB关联。
  24. 根据权利要求23所述的通信装置，其特征在于，所述参数包括以下至少一个：值标签valueTag、或区域范围areaScope。
  25. 根据权利要求23或24所述的通信装置，其特征在于，还包括：
    所述发送模块，还用于向所述DU发送第三消息，所述第三消息携带变更后的所述参数，所述变更后的所述参数与所述SIB关联。
  26. 根据权利要求25所述的通信装置，其特征在于，还包括：
    所述接收模块，还用于接收所述DU发送的第四消息，所述第四消息携带变更后的所述SIB，所述变更后的所述SIB由所述DU生成。
  27. 根据权利要求23-26任一项所述的通信装置，其特征在于，
    所述第一消息是F1建立请求消息；
    所述第二消息是F1建立响应消息。
  28. 根据权利要求26所述的通信装置，其特征在于，
    所述第三消息是DU配置更新消息；
    所述第四消息是DU配置更新确认消息。
  29. 一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得如权利要求1-13中任一所述的方法被执行。
  30. 一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如权利要求1-13中任一所述的方法被执行。
  31. 一种通信系统，其特征在于，所述通信系统包括：如权利要求14-15所述的通信装置。
PCT/CN2021/094486 2020-05-22 2021-05-19 一种通信方法以及相关装置 WO2021233320A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010444151.1A CN113709768B (zh) 2020-05-22 2020-05-22 一种通信方法以及相关装置
CN202010444151.1 2020-05-22

Publications (1)

Publication Number Publication Date
WO2021233320A1 true WO2021233320A1 (zh) 2021-11-25

Family

ID=78646431

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094486 WO2021233320A1 (zh) 2020-05-22 2021-05-19 一种通信方法以及相关装置

Country Status (2)

Country Link
CN (1) CN113709768B (zh)
WO (1) WO2021233320A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109526039A (zh) * 2017-09-19 2019-03-26 中国移动通信有限公司研究院 一种发送系统信息的方法和设备
US20190215756A1 (en) * 2018-01-11 2019-07-11 Comcast Cable Communications, Llc Connection Failure Reporting
CN110035472A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 一种传输方法和网络设备
CN110266523A (zh) * 2019-06-03 2019-09-20 京信通信系统（中国）有限公司 系统信息的更新处理方法、装置和基站

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100341262C (zh) * 2002-05-27 2007-10-03 华为技术有限公司 一种使移动终端省电的非连续解调实现方法
CN111277397B (zh) * 2017-05-04 2022-07-15 维沃移动通信有限公司 系统信息传输方法、终端及网络侧设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109526039A (zh) * 2017-09-19 2019-03-26 中国移动通信有限公司研究院 一种发送系统信息的方法和设备
US20190215756A1 (en) * 2018-01-11 2019-07-11 Comcast Cable Communications, Llc Connection Failure Reporting
CN110035472A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 一种传输方法和网络设备
CN110266523A (zh) * 2019-06-03 2019-09-20 京信通信系统（中国）有限公司 系统信息的更新处理方法、装置和基站

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, CHINA TELECOMMUNICATION: "(TP for NPN BL CR for TS 38.473): Further support of NPN over F1", 3GPP DRAFT; R3-203715, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-Meeting; 20200601 - 20200611, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051889446 *

Also Published As

Publication number Publication date
CN113709768B (zh) 2023-09-22
CN113709768A (zh) 2021-11-26

Similar Documents

Publication Publication Date Title
US11516704B2 (en) Information transmission method and apparatus
KR101011441B1 (ko) 버퍼 상태 보고를 수행하기 위한 방법 및 장치
US11968558B2 (en) Data transmission method and apparatus
WO2020192783A1 (zh) 一种无线承载的配置方法、装置及系统
EP3926912A1 (en) Mapping method, nodes, communication device, and storage medium
WO2020125654A1 (zh) 一种bsr上报方法及装置
JP6863485B2 (ja) データ指示方法、装置及び通信システム
CN108616943A (zh) 信息传输方法、基站以及用户设备
WO2020200024A1 (zh) 通信方法和通信装置
EP3595383B1 (en) Resource mapping method, network device and terminal device
US20210219191A1 (en) Handover Method And Base Station
EP4192082A1 (en) Communication method, apparatus and system
WO2022228360A1 (zh) 通信方法及装置
WO2021233320A1 (zh) 一种通信方法以及相关装置
US10944625B2 (en) Bearer configuration method and related products
WO2022237620A1 (zh) Csi测量资源的处理方法及装置、终端及可读存储介质
WO2021000818A1 (zh) 通信方法、装置和系统
CN110971358B (zh) 一种重复传输的激活方法、终端和网络侧设备
WO2019214593A1 (zh) 一种通信方法及装置
WO2021223626A1 (zh) Mbms业务处理方法、基站、用户终端及存储介质
WO2017206031A1 (zh) 信息传输方法及装置
WO2023202329A1 (zh) 信息处理方法、装置、终端及存储介质
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2023040881A1 (zh) 一种信息处理方法、装置、终端设备及网络设备
EP4351192A1 (en) Relay communication method, apparatus and system

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: 21808170

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21808170

Country of ref document: EP

Kind code of ref document: A1