WO2018019230A1

WO2018019230A1 - User terminal, and method and device for transmitting system information

Info

Publication number: WO2018019230A1
Application number: PCT/CN2017/094305
Authority: WO
Inventors: 施小娟; 施风; 谢峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-07-28
Filing date: 2017-07-25
Publication date: 2018-02-01
Also published as: CN107666716A

Abstract

Provided are a user terminal, and a method and device for transmitting system information. The method comprises: a user plane entity sending request information to a lower-layer protocol entity, wherein the request information is used to request system information; and upon receiving the system information sent by the lower-layer protocol entity, the user plane entity sending the system information to an upper-layer protocol entity. The invention solves a technical problem in the prior art in which broadcasting of all system information consumes a large amount of wireless resources.

Description

User terminal, system information transmission method and device

Technical field

The present invention relates to the field of communications, and in particular to a user terminal, a method and apparatus for transmitting system information.

Background technique

After a few decades of development, cellular mobile communication technology has entered the 4G era. In order to meet the higher, faster and newer communication needs of the foreseeable future, the industry has begun to research the future 5G technology. At present, the industry's generally recognized 5G technology goal is to achieve 1000 times mobile data traffic growth per region by 2020, and 10 to 100 times throughput growth per user equipment (User Equipment, UE for short). A 10 to 100-fold increase in the number of devices, a 10 times longer battery life for low-power devices, and a 5-fold delay in end-to-end.

In order to achieve the above objectives, deploying dense networks and using high-frequency bands with greater bandwidth, such as frequencies above 6 GHz and bandwidths up to 500 MHz to 1 GHz, are considered by the industry to be two promising future networks. means. The densely deployed network can effectively overcome the new features of the traditional cellular wireless network due to its wide coverage, uniform coverage, and fixed coverage characteristics, which cannot meet most of the communication services in the future 5G communication, which are concentrated in indoor and outdoor hotspot areas. The use of high-frequency bands (such as the millimeter wave band) can overcome the current situation in which the low-frequency band has been stretched, providing sufficient bandwidth for future 5G communication systems.

In a traditional cellular wireless network, each cell periodically broadcasts its own system information. In 2G, 3G and 4G mobile communication systems, the transmission mechanism of system information is generally in the same line, and has not undergone major mechanism changes, but there are some differences in detail design. The transmission of system information of a traditional cellular wireless network has the following common features:

(1) Each cell transmits all system information in a broadcast manner;

(2) System information is divided into multiple information blocks according to features and functions, where important information blocks, such as Master Information Block (MIB) and System Information Block Type 1 (SIB1), are fixed at a fixed time. The information is transmitted on the domain and the frequency domain resources; and other information blocks (SIBs other than SIB1) are dynamically scheduled and transmitted in the system information transmission window that is configured in SIB1 and does not overlap each other;

(3) Periodic broadcast transmission of all system information;

Take the Long Term Evolution (LTE) system as an example. Compared with the single-digit SIB number at the beginning of the design, it supports the new functions and new requirements, such as supporting cross-system mobility, public security, and positioning. The number of SIBs has been expanded to more than 20, and communication between devices (D2D). It is foreseeable that with the emergence of more new functions, new demands, and new technologies in the 5G era, both the number of SIBs and the information content transmitted by the SIB will continue to increase. In addition, with the further intensive deployment of the 5G era network, Conventional cellular wireless networks, such as the mechanism by which each cell periodically broadcasts all of its system information, consume a large amount of radio resources and device power consumption. On the other hand, many of the transport blocks for specific new technologies are actually limited by the demand, and the continuous cyclic broadcast transmission method wastes valuable wireless resources and is not conducive to equipment energy conservation.

In view of the technical problem that a large amount of radio resources caused by broadcasting all system information in the related art is consumed, an effective solution has not been proposed yet.

Summary of the invention

The embodiment of the invention provides a method and a device for transmitting a user terminal and system information, so as to at least solve the technical problem that a large amount of radio resources caused by broadcasting all system information in the related art is consumed.

According to an aspect of the embodiments of the present invention, a method for transmitting system information is provided, the method comprising: a user plane entity sending request information to a lower layer protocol entity, wherein the request information is used to request system information; and the user plane entity is receiving When the system information sent by the lower layer protocol entity is sent, the system information is sent to the upper layer protocol entity.

According to another aspect of the present invention, a system information transmission apparatus is provided, the apparatus comprising: a first sending module, configured to send request information to a lower layer protocol entity, wherein the request information is used to request system information; The second sending module is configured to send the system information to the upper layer protocol entity when receiving the system information sent by the lower layer protocol entity.

According to another embodiment of the present invention, there is provided a user terminal comprising a processor and a memory, the memory being arranged to store program code, the processor being arranged to execute program code stored in the memory, wherein the memory stores the following steps The program code is: sending the request information to the lower layer protocol entity, wherein the request information is used to request the system information; and when the system information sent by the lower layer protocol entity is received, the system information is sent to the upper layer protocol entity.

In the embodiment of the present invention, the user plane entity sends the request information to the lower layer protocol entity, where the request information is used to request system information; when the user plane entity receives the system information sent by the lower layer protocol entity, the system information is The information is sent to the upper layer protocol entity to complete the transmission of the system information. Since the transmission of the system information is performed on demand, the technical problem of a large amount of wireless resources caused by broadcasting all system information in the related art is solved, and the wireless reduction is realized. The technical effect of the resource being consumed.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a schematic diagram of a computer terminal in accordance with an embodiment of the present invention;

2 is a schematic diagram of signal coverage according to an embodiment of the present invention;

3 is a flowchart of a method of transmitting system information according to an embodiment of the present invention;

4 is a schematic diagram of a base station system according to an embodiment of the present invention;

FIG. 5 is a flowchart of an optional method of transmitting system information according to an embodiment of the present invention; FIG.

Figure 6 is a schematic illustration of omnidirectional coverage in accordance with an embodiment of the present invention;

Figure 7 is a schematic illustration of directional reception in accordance with an embodiment of the present invention;

FIG. 8 is a flowchart of an optional method of transmitting system information according to an embodiment of the present invention; FIG.

9 is a schematic diagram of a system information request according to an embodiment of the present invention;

10 is a flowchart of an optional method of transmitting system information according to an embodiment of the present invention;

11 is a schematic diagram of a system for transmitting system information according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

The method embodiment provided by Embodiment 1 of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device (ie, a user terminal). For example, running on a computer terminal, as shown in FIG. 1, the computer terminal may include one or more (only one shown) processor 101 (the processor 101 may include, but is not limited to, a microprocessor MCU or programmable A processing device such as a logic device FPGA, a memory 103 provided to store data, and a transmission module 105 provided as a communication function. It will be understood by those skilled in the art that the structure shown in FIG. 1 is merely illustrative and does not limit the structure of the above electronic device.

The memory 103 can be configured as a software program and a module for storing application software, such as program instructions/modules corresponding to the control method of the device in the embodiment of the present invention, and the processor 101 executes by executing a software program and a module stored in the memory 103. Various functional applications and data processing, that is, the above methods are implemented. The memory can include high speed random access memory and can also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory can further include memory remotely located relative to the processor, which can be connected to the computer terminal over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

In the above embodiment, the program stores the program code of the following steps: sending the request information to the lower layer protocol entity, wherein the request information is used to request system information; and when receiving the system information sent by the lower layer protocol entity, sending the system information to Upper layer protocol entity.

Optionally, the program further stores the program code of the following step: before sending the request information to the lower layer protocol entity, receiving a request sent by the upper layer protocol entity, where the request sent by the upper layer protocol entity is used to request to receive the system information on demand.

Optionally, the program further stores the program code of the following steps: selecting an access code sequence for requesting system information, or receiving an access code sequence for requesting system information from an upper layer protocol entity; and accessing the code sequence The lower layer protocol entity is notified as the request information.

Optionally, the program further stores the program code of the following steps: generating a control packet for requesting system information, and transmitting the control packet as the request information to the lower layer protocol entity, where the control packet is used to request a predefined class System information; or, the upper layer data packet received from the upper layer protocol entity is sent to the lower layer protocol entity, wherein the upper layer data packet is used to request system information, and the upper layer data packet is used to request a predefined type of system information.

Optionally, the program further stores the program code of the following steps: the control package carries a predefined one The identification information of the requested system information in the class system information; the upper layer data packet carries the identification information of the requested system information in a predefined type of system information.

Optionally, the program further stores the program code of the following steps: receiving the data packet from the lower layer protocol entity, where the data packet carries the logical channel identification information, where the logical channel identification information is used to indicate whether the logical channel is used for carrying The logical channel of the system information; determining whether the system information is included in the data packet according to the logical channel identification information; and when determining that the data packet includes the system information, transmitting the system information obtained after the data packet is unpacked to the upper layer protocol entity.

The transmission module is arranged to receive or transmit data via a network. The above-described network specific examples may include a wireless network provided by a communication provider of a computer terminal. In one example, the transport module includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet. In one example, the transmission module can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.

In order to achieve the 5G technology goal, in addition to using the low frequency band, the new generation 5G network will also develop high frequency bands with larger bandwidth, such as the frequency band above 6 GHz.

Since the traditional cellular wireless network uses a low frequency carrier, the omnidirectional antenna transmits a signal to the wireless space without special transmission requirements, and once the signal is transmitted, it will reach the target coverage of the entire cell. It should be noted that the cell here is a cell that conforms to the definition of the traditional cellular radio network, and may be a sector when the actual network is deployed, that is, the cell here is not limited to 360-degree coverage of the space deployment. The cell, for example, may be a sector covering only 120 degrees. Correspondingly, the omnidirectional antenna here is not limited to an omnidirectional antenna that is 360 degrees in a mathematical sense, but an antenna transmission range that reaches the required coverage of the target cell, such as a corresponding 120 degree range.

Unlike low-frequency carriers, high-frequency carriers have high path loss, high air absorption (such as oxygen absorption, rain fading, fog fading, etc.), and sensitivity to shadow fading. If you continue to use omnidirectional antennas in traditional cellular wireless communication systems. Sending a signal will make the coverage area of the high-frequency carrier much smaller than that of the related communication system using the low-frequency carrier (such as the LTE system). Therefore, the industry generally believes that it is necessary to improve the coverage of the high-frequency carrier by improving the antenna gain of the high-frequency communication system. range. Since the high-frequency carrier has a shorter wavelength, it is possible to accommodate more antenna elements per unit area (Antenna Element), and thus beamforming can be employed. The technology provides higher antenna gain and improves the coverage of the high-frequency carrier. Figure 2 illustrates the coverage difference between the omnidirectional antenna and the beamforming technique. The coverage of the beamforming technique is significantly larger than that of the omnidirectional antenna. range.

The above system information divides the system information into two categories according to the importance of the information, the first type of system information and the second type of system information. The first type of system information can still be transmitted by using a broadcast mechanism; the second type of system information can be transmitted on-demand, by unicast, multicast or broadcast. The first type of system information typically includes system information that must be acquired prior to accessing or camping on the cell associated with access or with cell camping, such that the information that each cell requires periodic broadcast transmission is greatly compressed.

The second type of system information is transmitted on demand instead of periodic broadcast transmission, which can improve resource utilization efficiency and reduce device power consumption. However, the protocol function design of the traditional cellular network cannot support this transmission mode. In addition, the 5G will use the high frequency band. Compared with the traditional cellular wireless network, the high frequency band has a transmission characteristic that is significantly different from the low frequency band. Therefore, how to implement the non-periodic and non-broadcast transmission of the second type of system information in a 5G network, especially in a 5G network using a high frequency band, remains to be solved.

In order to adapt to the many new functions, new requirements, and new technologies introduced in the 5G era, the transmission of system information in a 5G system, especially the non-periodic, non-broadcast on-demand transmission of the second type of system information, is provided according to an embodiment of the present invention. A method embodiment of a method of transmitting system information, it is noted that the steps illustrated in the flowchart of the figures may be performed in a computer system such as a set of computer executable instructions, and, although in a flowchart The logical order is shown, but in some cases the steps shown or described may be performed in an order different than that herein.

FIG. 3 is a flowchart of a method for transmitting system information according to an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps:

Step S301, the user plane entity sends the request information to the lower layer protocol entity, where the request information is used to request the system information.

Step S302: The user plane entity sends the system information to the upper layer protocol entity when receiving the system information sent by the lower layer protocol entity.

With the above embodiment, the user plane entity sends the request information to the lower layer protocol entity, wherein the request information is used to request system information; when the user plane entity receives the system information sent by the lower layer protocol entity, the system information is used. Sending to the upper layer protocol entity to complete the transmission of system information, since the transmission of system information is performed on demand, thereby solving the technical problem that a large amount of radio resources caused by broadcasting all system information in the related art is consumed, and realizing the reduction of radio resources. The technical effect of being consumed.

Optionally, the lower layer protocol entity includes a physical layer protocol entity; the upper layer protocol entity includes a radio resource control RRC protocol entity.

In the above embodiment, the system information in the step S301 and the step S302 is the second type of system information, and the second type of information is system information that is transmitted according to the user's requirements, and does not need to be notified to the user terminal in real time, but the user needs Or the second type of system information may also be system information with a small amount of user demand, without periodic propagation, or the time interval between transmitting two adjacent system information is greater than a preset value, and the user terminal may wait The base station delivers the information, and the method of the present application can also be used for active acquisition. By adopting the method of the present application, non-periodic and non-broadcast on-demand transmission of the second type of system information is realized, the use efficiency of the radio resources is improved, the power consumption of the device is reduced, and many new functions, new demands, and new requirements for the 5G era are satisfied. Technical support.

Optionally, the triggering object for acquiring the system information is an upper layer protocol entity, and before the user plane entity sends the request information to the lower layer protocol entity, the user plane entity receives the request sent by the upper layer protocol entity, and the request sent by the upper layer protocol entity is used to request the on demand Receive system information.

In the above embodiment, the user plane entity sends the request information to the lower layer protocol entity, where the user plane entity sends the request information to the lower layer protocol entity by using the uplink common control transport channel; or the user plane entity sends the uplink shared transport channel to the lower layer protocol entity. Request information.

Optionally, in step S301, the user plane entity sends the request information to the lower layer protocol entity, where the user plane entity selects an access code sequence for requesting system information, or the user plane entity receives the request system from the upper layer protocol entity. The access code sequence of the information; the user plane entity notifies the lower layer protocol entity of the access code sequence as the request information.

After the user plane entity sends the request information to the lower layer protocol entity using the uplink common control transport channel, when the lower layer protocol entity receives the request information on the uplink common control transport channel, the lower layer protocol entity sends the request information on the physical uplink public access channel. .

Specifically, the sending, by the lower layer protocol entity, the request information on the physical uplink public access channel includes: the lower layer protocol entity sends the request information omnidirectionally on the physical uplink public access channel, so that the sent request information covers the receiving end. The required uplink coverage.

Optionally, the user plane entity sends the request information to the lower layer protocol entity by using the uplink shared transport channel, where the user plane entity generates a control packet for requesting system information, and sends the control packet as the request information to the lower layer protocol entity, where the control The packet itself represents a request for a predefined type of system information (such as the second type of system information). Preferably, the control packet also carries information about which system information in the requested type of system information to implement the specific system. Or the user plane entity sends the upper layer data packet received from the upper layer protocol entity to the lower layer protocol entity, wherein the upper layer data packet is used to request system information, and the upper layer data packet itself indicates that the predefined type of system information is requested. (For example, the second type of system information), preferably, the upper layer data packet further carries information about which system information in the requested type of system information to obtain the specific system information.

It should be noted that, after the user plane entity sends the request information to the lower layer protocol entity by using the uplink shared transport channel, when the lower layer protocol entity receives the request information on the uplink shared transport channel, the lower layer protocol entity sends a request on the physical uplink shared channel. information.

The sending of the request information by the lower layer protocol entity on the physical uplink shared channel refers to: the lower layer protocol entity directionally transmits the request information on the physical uplink shared channel, so that the sent request information matches the receiving direction of the receiving end in the sending direction.

Optionally, before the user plane entity sends the request information to the lower layer protocol entity by using the uplink shared transport channel, the user plane entity receives the uplink scheduling that is received by the lower layer protocol entity from the sending end and is used to indicate that the information is transmitted on the physical uplink shared channel. information.

In step S302, when the user plane entity receives the system information sent by the lower layer protocol entity, sending the system information to the upper layer protocol entity includes: the user plane entity receives the data packet from the lower layer protocol entity, where the data packet carries the logic Channel identification information, the logical channel identification information is used to indicate whether the logical channel is a logical channel for carrying system information; the user plane entity determines, according to the logical channel identification information, whether the system information is included in the data packet; and includes determining system information in the data packet. In the case, the user plane entity sends the system information obtained after unpacking the data packet to the upper layer protocol entity.

Specifically, the user plane entity receiving the data packet from the lower layer protocol entity includes: the user plane entity receiving the data packet from the lower layer protocol entity on the downlink shared transport channel.

Before the user plane entity receives the data packet from the lower layer protocol entity, the lower layer protocol entity is in the physical downlink Enjoy receiving packets on the channel.

The following describes the process of receiving the system information, especially the second type of system information, on the user equipment UE at different times in the 5G network, and details the specific implementation process of the application.

It should be noted that, compared with the definition of a cell bound to a physical resource defined in a conventional cellular radio network, the concept of a cell in a 5G system may have a completely new definition, which is mainly due to, on the one hand, network deployment in a 5G system. Forms will change, such as densely deploying networks. For example, deployment architectures may result in centralized deployment based on traditional distributed deployment architectures; on the other hand, the use of high-frequency bands and the introduction of other new technologies.

In a 5G system as shown in FIG. 4, there may be a distributed deployment or a centralized deployment in a 5G system. The distributed deployment of the base station, such as 401 (ie, NR-nodeB1, connected to the core network Core) and 402 (ie, NR-nodeB2), uses the 5G new radio technology (New Radio, NR for short) base stations NR-nodeB1, NR-nodeB2 and Like a base station site in a traditional cellular wireless network, one site contains all the functions of the base station and each independently accesses the core network (Core). In addition to the distributed deployment, there is a centralized deployment mode in Figure 4. The functions of one site on the base station side are divided according to the functions required, and some functions are unified into one central unit (CU), as shown in Figure 4. 403 (ie CU); and another part of the function is implemented in the respective Distributed Unit (DU), as shown in Figure 4, 404 to 406 (corresponding to NR-DU1, NR-DU2, respectively) NR-DU3). The CU implements all or part of the baseband processing function, and at least implements some high-level protocol functions that are not closely related to the scheduling use of the physical resources, and the DU implements the radio frequency function, and may also implement partial baseband processing functions according to different deployment conditions.

As shown in Figure 4, the cell in the 5G system may no longer be bound to the physical resource. For example, 401 and 402 in Figure 4 may form a cell independently, but 404 to 406 do not necessarily form a cell independently, but 404 to 406 and 403. Together form a logical community. In view of this, the concept of a cell in the subsequent embodiment of the present application refers to a newly defined cell concept in a 5G system, and does not limit the binding of a cell to a physical resource or a physical site. In addition, the 5G network node (NR-node) in the subsequent embodiments of the present application may be a distributed deployment base station NR-nodeB including all base station functions, or a DU in a centralized deployment, unless otherwise specified. "DU+CU".

In addition, it should be noted that the receiving end receives the second type of system information on demand (relative to the transmitting end, which is sent on demand), where the on-demand can be triggered by the wireless channel quality event, the service event is triggered, and the system information is updated. Trigger and more. Receiving the second type of system information on demand, which can receive all second type system letters upon triggering The information of the second type corresponding to the trigger event is received on demand according to different trigger events.

For example, it is triggered by a radio channel quality event, for example, the signal quality of the serving cell is worse than the threshold X. The service is triggered by a service event, such as the user equipment UE or the network accessed by the user equipment UE to initiate a certain type of service, such as D2D service, public security. Notification, etc.; triggered by the system information update, the user equipment UE or the network side initiates the need to update the system information.

Embodiments of the present application are described in detail below in conjunction with specific embodiments.

Embodiment 1

The user equipment UE may not establish a Radio Resource Control (RRC) connection with the network. When the UE needs to receive system information as needed, the system information may be obtained by the method of the present application. In Embodiment 1, the UE may be in an idle state or a power saving state. FIG. 5 is a flowchart of system information reception in Embodiment 1.

Step S501: The UE receives the first type of system information of the NR-node sent by the network broadcast.

In this step, if the 5G network is deployed overlapping with an existing related network (such as an LTE network), for example, the NR-node is within the coverage of the LTE macro base station, the first type of system information of the NR-node may be periodically broadcast by the LTE macro base station. send.

If the NR-node broadcasts its own first-class system information, and the NR-node uses a high-frequency carrier, the embodiment needs to adopt a technical means to ensure that the periodic broadcast of the first type of system information can cover the NR- The target coverage that the node needs to achieve. For example, as shown in FIG. 6, the NR-node has multiple (for example, five) radio frequency channels. Therefore, at the same time, T1 can transmit five narrow beams in a beamforming manner, so that the five narrow beams sequentially cover different directions. Then, the five narrow beams are combined to form a wide beam covering a large range, and then the T2, ..., Tn time (as shown in FIG. 6) causes the narrow beams formed by the narrow beams to be sequentially transmitted to different directions until the NR is implemented. The target coverage that -node needs to achieve.

The foregoing first type of system information includes system information related to access and cell camping, such as information related to access and cell camping in MIB, SIB1, and SIB2 in the LTE system.

Step S502: When the UE needs to receive the second type of system information as needed, the UE sends a system information request (ie, request information) to the NR-Node. In this step, a system information request may be sent by performing a random access procedure.

When the UE needs to receive the second type of system information on demand, the upper layer protocol entity of the UE sends an indication to the user plane entity to receive the second type of system information on demand.

After receiving the upper layer protocol entity "instruction to receive the second type of system information on demand", the user plane entity of the UE sends a system information request to the lower layer protocol entity by using an uplink common control transport channel (UL-CCCH). Information (ie request information). Here, the system information request information is represented by an access code sequence dedicated to the requesting system information, and the user plane entity of the UE selects an access code sequence for indicating the requested system information, and notifies the selected access code sequence to Lower layer protocol entity. Alternatively, the access code sequence used to indicate the requesting system information may also be selected by the upper layer protocol entity and sent to the user plane entity in the "indication to receive the second type of system information on demand", and the user plane entity receives Afterwards, the access code sequence is notified to the lower layer protocol entity. After receiving the access code sequence sent by the user plane entity, the lower layer protocol entity sends the omnidirectional transmission access to the NR-Node on the Physical Uplink Common Access Control Channel (P-UL-CACCH). The code sequence, the so-called omnidirectional transmission, refers to the uplink coverage of the access code sequence that is sent on the physical uplink common access channel of the physical uplink common control channel, and the same technology as that of FIG. 6 can be used. The means, that is, the NR-Node sequentially transmits the access code sequence to different directions to cover all uplink coverage areas. Here, the physical uplink public access channel, such as a random access channel (RACH) in the LTE system.

In this embodiment, the user plane entity is, for example, a Media Access Control (MAC) entity, and the lower layer protocol entity is a physical layer entity.

It should be noted that, if the NR-Node in this embodiment is a "DU+CU" as shown in FIG. 4, and a user plane entity (such as a MAC) corresponding to the above UE side function on the network side is located in the DU, and the MAC is The protocol entity is located in the CU. In this embodiment, after the DU receives the access code sequence sent by the UE to indicate the system information, the DU needs to pass the interface between the DU and the CU, as shown in FIG. The Xn interface notifies the CU to send the second type of system information to the UE. This embodiment does not limit the specific time when the DU notifies the CU, and may be notified immediately after the DU receives the access code sequence, or may be after the DU sends the message in response to the UE, or may be in the process of step S503 or after step S503.

In step S502, the system information request is sent by performing a random access procedure, and the random access message flow is described in the related art (such as LTE), and the description is not repeated herein. Corresponding to the random access process, then in this step The UL-CCCH is a Random Access Channel (RACH). The access code sequence dedicated to the requesting system information is a preamble (ie, Preambles) dedicated to representing the requested system information, which is divided from the random access preambles. The P-UL-CCCH is a Physical Random Access Channel (PRACH).

In this embodiment, after receiving the access code sequence requesting system information on the P-UL-CCCH, the NR-Node sends a response message to the UE, where the response message includes beam training measurement between the UE and the NR-Node. The reference signal configuration and the scheduling identifier used to schedule the UE, the response message is sent omnidirectionally.

Step S503, a beam training process is performed between the UE and the NR-Node.

The UE performs a beam training process with the NR-Node according to the reference signal configuration for beam training received in step S502.

After the beam training is completed, the UE and the NR-Node can directly transmit and receive information. The so-called directional transmission information means that the transmitting end transmits information in the sending direction paired with the receiving end receiving direction, and the directional receiving information means that the receiving end receives the information in the receiving direction paired with the sending direction of the transmitting end, as shown in FIG. 7 .

Step S504, the UE receives the second type of system information sent by the NR-Node.

The UE receives the second type of system information that is sent by the NR-Node. Specifically, the lower layer protocol entity of the UE is configured to receive the data packet from the NR-Node on the Physical Downlink Shared Channel (PDSCH), and the lower layer protocol entity passes the A downlink shared transport channel (DL-SCH) between user plane entities (such as MAC) delivers the data packet to the user plane entity. The user plane entity determines, according to the logical channel identification information indicated in the data packet control information, whether the data included in the data packet is system information, and if yes, unpacks the data packet and sends the data packet to the upper layer protocol entity.

Specifically, the data packet control information may be carried in the data packet header. For example, in the physical MAC of the user plane, the logical channel identification information and the logical channel identification information are included in the MAC header of the MAC PDU (Protocol Data Unit). The logical channel is used to indicate the logical channel for carrying the system information, and the broadcast control channel (BCCH) bearer system information is taken as an example. Table 1 shows the meanings of different logical channel identifiers.

Table 1

Logical channel identification

meaning

0000000000	公共控制信道Common control channel
00001-0101000001-01010	逻辑信道的编号Logical channel number
0101101011	广播控制信道Broadcast control channel
0110001100	请求系统信息Request system information
01101-1101101101-11011	保留字段reserved text
1110011100	UE竞争识别标识UE competition identification
……......	……......

For the upper layer protocol entity in the embodiment, such as the RRC entity, the user plane entity may directly send the unpacked data packet to the RRC entity, or may be processed by other user plane entities and then sent to the RRC entity.

Embodiment 2

The user equipment UE may not establish a radio resource control connection with the network, and when the UE needs to receive the system information as needed, the system information may be obtained by the method of the present application. In Embodiment 2, the UE may be in an idle state or a power saving state. FIG. 8 is a flowchart of system information reception in Embodiment 2.

Step S801, the UE receives the first type of system information broadcast of the NR-node sent by the network broadcast.

This step is the same as the description of step S501, and details are not described herein again.

Step S802, when the UE needs to receive the second type of system information as needed, the UE initiates a random access procedure.

When the UE needs to receive the second type of system information on demand, the upper layer protocol entity of the UE sends an indication to the user plane entity to receive the second type of system information on demand. Preferably, in this embodiment, the second type is received on demand. The indication of the system information may carry information of which system information in the second type of system information is received on demand.

After the user plane entity (such as a MAC) of the UE receives the indication that the upper layer protocol entity receives the second type of system information on demand, initiates a random access procedure, and the random access message flow is described with related technologies (such as LTE), and the present invention No longer. It should be noted that, when the high frequency carrier is used, all the messages of the random access procedure in the embodiment are sent in all directions, and after performing the random access procedure, the UE obtains beam training measurement with the NR-Node. The reference signal configuration and the scheduling identifier used to schedule the UE.

Step S803, a beam training process is performed between the UE and the NR-Node.

This step is the same as the description of step S503, and details are not described herein again.

Step S804, the UE receives the uplink scheduling information sent by the NR-Node.

Specifically, the user plane entity of the UE receives the uplink scheduling information of the NR-Node that is received by the lower layer protocol entity from the PDSCH, and the uplink scheduling information is used to indicate that the UE is on the Physical Uplink Shared Channel (PUSCH). The resource used when sending.

Step S805, the UE sends a control packet (ie, system information request, MAC CE) for requesting system information to the NR-Node.

Specifically, after receiving the uplink scheduling information of step S804, the user plane entity of the UE generates a control packet for requesting system information, and adopts an uplink shared transport channel (UL) with the lower layer protocol entity. -SCH) sends the generated control packet to the lower layer protocol entity, and the lower layer protocol entity directs the control packet to the NR-Node on the PUSCH.

In this embodiment, for a user plane entity, such as a MAC entity, the control packet generated by the MAC entity for requesting system information is a MAC CE, and the MAC CE may indicate requesting system information. Once the NR-Node receives the MAC CE, All the second type of system information is sent to the UE in step S806. Specifically, the MAC entity generates a control packet MAC CE for requesting system information, and indicates that the MAC CE is a control packet for requesting system information by using logical channel identifier information included in the packet control information corresponding to the MAC CE. The packet control information may be carried in the packet header. For example, for the user plane entity MAC, the MAC header of the MAC CE corresponding to the embodiment in the MAC header of the MAC PDU includes packet control information, and the logical channel identifier included in the packet control information. The information indicates "Request System Information" as 01100 shown in Table 1.

Preferably, the MAC CE may also indicate which second type of system information is specifically requested, as shown in FIG. 9 is a schematic diagram of a possible MAC CE for requesting system information, the MAC CE consists of 3 bytes (Oct1 to Oct3). The composition, starting from the highest bit to the highest third bit of the third byte, respectively characterizes SIB2-SIB20 (ie, S3 to S21). If the corresponding position is 1, it indicates that the SIB corresponding to the location is requested, otherwise it indicates no request. The other bits are reserved bits (R). Preferably, the user plane entity generates the MAC CE according to the information about which system information of the second type of system information is received on the basis of the indication of receiving the second type of system information received by the upper layer protocol entity.

It should also be noted that if the NR-Node of this embodiment is "DU+CU" as shown in FIG. 4, and the user plane entity (such as MAC) corresponding to the above UE side function on the network side is located in the DU, and the MAC Agreement on top In the CU, in this embodiment, after the DU receives the MAC CE sent by the UE for requesting system information, the DU needs to pass the interface between the DU and the CU, and the Xn interface in FIG. 4 notifies the CU to the location. The UE sends the second type of system information requested in the MAC CE.

Step S806, the UE receives the second type of system information sent by the NR-Node.

After receiving the control packet requesting the system information, the NR-Node sends the second type of system information that is requested in the control packet to the UE, and the specific receiving behavior of the UE is the same as the step S504, which is not described in this embodiment.

Embodiment 3

The user equipment UE may not establish a radio resource control connection with the network, and when the UE needs to receive the system information as needed, the system information may be obtained by the method of the present application. In Embodiment 3, the UE may be in an idle state or a power saving state. FIG. 10 is a flowchart of system information reception in Embodiment 3.

Steps S1001 to S1004 are the same as steps S801 to S804.

In step S1005, the UE initiates an RRC Connection Request (RRC Connection Request) to the NR-Node, and the RRC connection establishment request includes the system information request, and may also include other reasons already defined in the related system.

Specifically, after receiving the uplink scheduling information of step S1004, the user plane entity of the UE sends the upper layer data packet received from the upper layer protocol entity for requesting system information to the lower layer protocol by using the UL-SCH between the lower layer protocol entity and the lower layer protocol entity. The entity, the upper layer data packet contains system information request information; the lower layer protocol entity directs the data packet containing the system information request information to the NR-Node on the PUSCH.

In this embodiment, the upper layer protocol entity is an RRC entity, and the upper layer data packet for requesting system information is an RRC connection setup request message, and the RRC connection establishment request reason included in the message is a system information request, and may even include specific system information requested. Instructions.

The UE receives the second type of system information sent by the NR-Node. In this embodiment, there are two different ways:

In step S1006, the UE receives an RRC Connection Setup message.

The RRC Connection Setup message is as described in the related art.

Step S1007: The UE receives the second type of system information sent by the NR-Node.

After transmitting the RRC connection setup message, the NR-Node sends the second request in the RRC connection setup request to the UE. For the class system information, the specific receiving behavior of the UE is the same as that of step S504, which is not described in this embodiment.

In step S1008, this step is an optional step. If the RRC connection setup request reason sent in step S1005 includes only the system information request, the NR-Node may notify the UE to release the RRC connection after successfully transmitting the second type of system information.

Through the foregoing embodiments, non-periodic and non-broadcast on-demand transmission of the second type of system information can be implemented to improve radio resource usage efficiency and reduce device power consumption.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Example 2

A device for transmitting system information is also provided in the embodiment of the present invention. The device is used to implement the above embodiments and preferred embodiments, and the description thereof has been omitted. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

11 is a schematic diagram of a system for transmitting system information according to an embodiment of the present invention. As shown in FIG. 11, the apparatus may include: a first sending module 111 and a second sending module 112.

The first sending module 111 is configured to send the request information to the lower layer protocol entity, wherein the request information is used to request system information.

The second sending module 112 is configured to send the system information to the upper layer protocol entity when receiving the system information sent by the lower layer protocol entity.

With the above embodiment, the first sending module sends the request information to the lower layer protocol entity, where the request information is used to request the system information; when the second sending module receives the system information sent by the lower layer protocol entity, the system information is sent to the upper layer protocol. Entity to complete the transmission of system information, as system information is transmitted on demand Therefore, the technical problem that a large amount of radio resources caused by broadcasting all system information in the related art is consumed is solved, and the technical effect of reducing the consumption of radio resources is realized.

The above transmission device can be used to control the user terminal of the present application.

In the above embodiment, the non-periodic and non-broadcast on-demand transmission of the second type of system information is implemented, the use efficiency of the radio resources is improved, the power consumption of the device is reduced, and many new functions, new demands, and new requirements for the 5G era are satisfied. Technical support.

Optionally, the apparatus further includes: a receiving module, configured to receive a request sent by the upper layer protocol entity before sending the request information to the lower layer protocol entity, where the request sent by the upper layer protocol entity is used to request to receive the system information on demand.

Optionally, the first sending module includes: a first sending submodule configured to send request information by using an uplink common control transport channel to a lower layer protocol entity; and a second sending submodule configured to use an uplink shared transport channel The request information is sent to the lower layer protocol entity.

Optionally, the first sending module includes: a first request information processing submodule, configured to select an access code sequence for requesting system information, or receive an access code sequence for requesting system information from an upper layer protocol entity; The submodule is configured to notify the underlying protocol entity of the access code sequence as request information.

Optionally, the first sending submodule is configured to send the request information to the lower layer protocol entity by using the uplink common control transport channel, and the lower layer protocol entity is physically uplinked when receiving the request information on the uplink common control transport channel. The request information is sent on the access channel.

Optionally, the first sending submodule is further configured to send the request information to the lower layer protocol entity by using the uplink common control transport channel, and the lower layer protocol entity sends the request information omnidirectionally on the physical uplink public access channel, so that the sent request information is sent. Covers the uplink coverage required by the receiver.

Optionally, the first sending module includes: a second request information processing sub-module, configured to generate a control packet for requesting system information, and send the control packet as request information to the lower layer protocol entity, where the control packet is used to request the advance a type of system information defined; a third request information processing sub-module configured to send an upper layer data packet received from an upper layer protocol entity to a lower layer protocol entity, wherein the upper layer data packet is used to request a predefined class system message.

Optionally, the control packet carries the identification information of the requested system information in a predefined type of system information; the upper layer data packet carries the identification information of the requested system information in a predefined type of system information.

Optionally, the second sending submodule is configured to send the request information to the lower layer protocol entity by using the uplink shared transport channel, and the lower layer protocol entity sends the request information on the uplink shared transport channel, and the lower layer protocol entity sends the request information on the physical uplink shared channel. Request information.

Optionally, the second sending submodule is configured to send the request information to the lower layer protocol entity by using the uplink shared transport channel, and the lower layer protocol entity sends the request information on the physical uplink shared channel, so that the sent request information is sent in the sending direction. The receiving direction of the receiving end matches.

Optionally, the first sending module further includes: a first receiving submodule, configured to receive, after the uplink shared transport channel sends the request information to the lower layer protocol entity, the received lower layer protocol entity is received from the sending end to indicate the physical Uplink scheduling information for transmitting information on the uplink shared channel.

Optionally, the second sending module includes: a second receiving submodule, configured to receive a data packet from a lower layer protocol entity, where the data packet carries logical channel identification information, where the logical channel identification information is used to indicate whether the logical channel is a logical channel for carrying system information; the determining submodule is configured to determine, according to the logical channel identification information, whether the system information is included in the data packet; and the third sending submodule is configured to, when determining that the data packet includes system information, The system information obtained after unpacking the data packet is sent to the upper layer protocol entity.

Optionally, the second receiving submodule is further configured to receive the data packet from the lower layer protocol entity on the downlink shared transport channel.

Optionally, the second receiving submodule is configured to receive the data packet from the lower layer protocol entity, wherein the data packet is a data packet that is directed by the lower layer protocol entity on the physical downlink shared channel.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Example 3

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium Can be set to store program code for performing the following steps:

S1, sending request information to an underlying protocol entity, where the request information is used to request system information;

S2: When receiving the system information sent by the lower layer protocol entity, sending the system information to the upper layer protocol entity.

Optionally, the storage medium is further arranged to store program code for performing the following steps:

S3, sending, by using an uplink common control transport channel, a request information to a lower layer protocol entity;

S4. Send the request information to the lower layer protocol entity by using the uplink shared transport channel.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

Optionally, in this embodiment, the processor executes, according to the stored program code in the storage medium, that the user plane entity sends the request information to the lower layer protocol entity, where the request information is used to request system information; When receiving the system information sent by the lower layer protocol entity, the system information is sent to the upper layer protocol entity.

Optionally, in this embodiment, the processor performs, according to the stored program code in the storage medium, the user plane entity is configured to select an access code sequence for requesting system information, and the user plane entity is configured to use the access code sequence as a request. The information informs the underlying protocol entity.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Having been made within the spirit and principles of the present invention Any modifications, equivalent substitutions, improvements, etc., are intended to be included within the scope of the present invention.

Industrial applicability

In the embodiment of the present invention, the user plane entity sends the request information to the lower layer protocol entity, where the request information is used to request system information; when the user plane entity receives the system information sent by the lower layer protocol entity, the system information is sent to the upper layer protocol. The entity completes the transmission of system information, and the transmission of system information is performed on demand, thereby solving the technical problem that a large amount of radio resources caused by broadcasting all system information in the related art is consumed, and realizing the technology for reducing the consumption of radio resources. effect.

Claims

A method for transmitting system information includes:

The user plane entity sends the request information to the lower layer protocol entity, where the request information is used to request system information;

The user plane entity sends the system information to an upper layer protocol entity when receiving the system information sent by the lower layer protocol entity.
The method of claim 1, wherein before the user plane entity sends the request information to the lower layer protocol entity, the method further comprises:

The user plane entity receives a request sent by the upper layer protocol entity, where the request sent by the upper layer protocol entity is used to request to receive the system information on demand.
The method of claim 1, wherein the sending of the request information to the lower layer protocol entity by the user plane entity comprises:

The user plane entity sends the request information to the lower layer protocol entity by using an uplink common control transport channel; or

The user plane entity sends the request information to the lower layer protocol entity using an uplink shared transport channel.
The method of claim 1, wherein the sending of the request information to the lower layer protocol entity by the user plane entity comprises:

The user plane entity selects an access code sequence for requesting the system information, or the user plane entity receives an access code sequence for requesting the system information from the upper layer protocol entity;

The user plane entity notifies the lower layer protocol entity of the access code sequence as the request information.
The method of claim 3, wherein after the user plane entity sends the request information to the lower layer protocol entity using an uplink common control transport channel, the method further includes:

When the lower layer protocol entity receives the request information on the uplink common control transport channel, the lower layer protocol entity sends the request information on the physical uplink public access channel.
The method of claim 5, wherein the sending, by the lower layer protocol entity, the request information on the physical uplink public access channel comprises:

The lower layer protocol entity sends the request information in an omnidirectional manner on the physical uplink public access channel, so that the sent request information covers the uplink coverage required by the receiving end.
The method of claim 1, wherein the sending of the request information to the lower layer protocol entity by the user plane entity comprises:

The user plane entity generates a control packet for requesting the system information, and sends the control packet as the request information to the lower layer protocol entity, where the control packet is used to request a predefined type System information; or,

The user plane entity sends an upper layer data packet received from the upper layer protocol entity to the lower layer protocol entity, where the upper layer data packet is used to request a predefined type of system information.
The method of claim 7 wherein

The control packet carries identification information of the requested system information in the predefined type of system information;

The upper layer data packet carries identification information of the requested system information in the predefined type of system information.
The method of claim 3, wherein after the user plane entity sends the request information to the lower layer protocol entity using an uplink shared transport channel, the method further includes:

When the lower layer protocol entity receives the request information on the uplink shared transport channel, the lower layer protocol entity sends the request information on the physical uplink shared channel.
The method of claim 9, wherein the sending, by the lower layer protocol entity, the request information on the physical uplink shared channel comprises:

The lower layer protocol entity directionally transmits the request information on the physical uplink shared channel, so that the sent request information matches the receiving direction of the receiving end in the sending direction.
The method of claim 3, wherein the user plane entity uses uplink sharing Before the transmission channel sends the request information to the lower layer protocol entity, the method further includes:

The user plane entity receives uplink scheduling information that is received by the lower layer protocol entity from the sending end and is used to indicate that the information is transmitted on the physical uplink shared channel.
The method of claim 1, wherein the user plane entity, when receiving the system information sent by the lower layer protocol entity, sending the system information to an upper layer protocol entity comprises:

The user plane entity receives a data packet from the lower layer protocol entity, where the data packet carries logical channel identification information, where the logical channel identifier information is used to indicate whether the logical channel is used to carry the system information. Logical channel

Determining, by the user plane entity, whether the system information is included in the data packet according to the logical channel identification information;

When it is determined that the system information is included in the data packet, the user plane entity sends the system information obtained after the data packet is unpacked to the upper layer protocol entity.
The method of claim 12, wherein the user plane entity receiving the data packet from the lower layer protocol entity comprises:

The user plane entity receives a data packet from the lower layer protocol entity on a downlink shared transport channel.
The method according to claim 12 or 13, wherein before the user plane entity receives the data packet from the lower layer protocol entity, the method further comprises:

The lower layer protocol entity directs receiving the data packet on a physical downlink shared channel.
The method of claim 1 wherein

The lower layer protocol entity includes a physical layer protocol entity;

The upper layer protocol entity includes a radio resource control RRC protocol entity.
A system information transmission device, comprising:

a first sending module, configured to send request information to a lower layer protocol entity, where the request information Used to request system information;

The second sending module is configured to: when receiving the system information sent by the lower layer protocol entity, send the system information to an upper layer protocol entity.
The apparatus of claim 16 wherein said apparatus further comprises:

The receiving module is configured to receive the request sent by the upper layer protocol entity before sending the request information to the lower layer protocol entity, where the request sent by the upper layer protocol entity is used to request to receive the system information on demand.
The apparatus of claim 16, wherein the first transmitting module comprises:

a first request information processing submodule, configured to select an access code sequence for requesting the system information, or receive an access code sequence for requesting the system information from the upper layer protocol entity;

The notification submodule is configured to notify the lower layer protocol entity that the access code sequence is used as the request information.
The apparatus of claim 16, wherein the first transmitting module comprises:

a second request information processing sub-module, configured to generate a control packet for requesting the system information, and send the control packet as the request information to the lower layer protocol entity, where the control packet is used to request a pre- a type of system information defined;

The third request information processing sub-module is configured to send the upper layer data packet received from the upper layer protocol entity to the lower layer protocol entity, wherein the upper layer data packet is used to request a predefined type of system information.
The device according to claim 19, wherein

The control packet carries identification information of the requested system information in the predefined type of system information;

The upper layer data packet carries identification information of the requested system information in the predefined type of system information.
The apparatus of claim 16, wherein the second transmitting module comprises:

a second receiving submodule, configured to receive a data packet from the lower layer protocol entity, where the data packet carries logical channel identification information, where the logical channel identification information is used to indicate whether the logical channel is used for a bearer a logical channel for describing system information;

a determining submodule, configured to determine, according to the logical channel identification information, whether the system information is included in the data packet;

The third sending submodule is configured to, when it is determined that the system information is included in the data packet, send the system information obtained by unpacking the data packet to the upper layer protocol entity.
The apparatus of claim 21 wherein said second receiving sub-module is further configured to receive data packets from said lower layer protocol entity on a downlink shared transport channel.
The apparatus of claim 21 or 22, wherein the second receiving submodule is configured to receive a data packet from the lower layer protocol entity, wherein the data packet is a physical downlink shared channel of the lower layer protocol entity Directly receive the received packet.
A user terminal comprising a processor and a memory, the memory being arranged to store program code, the processor being arranged to execute program code stored in the memory, wherein the memory stores program code of the following steps:

Sending request information to an underlying protocol entity, wherein the request information is used to request system information;

When receiving the system information sent by the lower layer protocol entity, the system information is sent to an upper layer protocol entity.
The user terminal according to claim 24, wherein the memory further stores program code of the following steps:

Receiving the request sent by the upper layer protocol entity before sending the request information to the lower layer protocol entity, wherein the request sent by the upper layer protocol entity is used to request to receive the system information on demand.
The user terminal according to claim 24, wherein the memory further stores program code of the following steps:

Selecting an access code sequence for requesting the system information, or receiving from the upper layer protocol entity An access code sequence for requesting the system information;

The access code sequence is notified to the lower layer protocol entity as the request information.
The user terminal according to claim 24, wherein the memory further stores program code of the following steps:

Generating a control packet for requesting the system information, and transmitting the control packet as the request information to the lower layer protocol entity, where the control packet is used to request a predefined type of system information; or

And sending an upper layer data packet received from the upper layer protocol entity to the lower layer protocol entity, where the upper layer data packet is used to request the system information, and the upper layer data packet is used to request a predefined type of system information.
The user terminal according to claim 27, wherein

The control packet carries identification information of the requested system information in the predefined type of system information;

The upper layer data packet carries identification information of the requested system information in the predefined type of system information.
The user terminal according to claim 24, wherein the memory further stores program code of the following steps:

Receiving a data packet from the lower layer protocol entity, where the data packet carries logical channel identification information, where the logical channel identification information is used to indicate whether the logical channel is a logical channel for carrying the system information;

Determining, according to the logical channel identification information, whether the system information is included in the data packet;

When it is determined that the system information is included in the data packet, the system information obtained after the data packet is unpacked is sent to the upper layer protocol entity.