METHOD AND APPARATUS TO PROVIDE SYSTEM INFORMATION

专利摘要:
a method of disseminating system information, in a wireless communication system, through a base station distributed unit (du) and an apparatus are provided to support the method. the method can comprise the steps of: receiving, from a central unit (cu) of a base station, system information pertaining to the base station's cu; receive, from a terminal, a request for system information; receive, from the base station's sky, a message commanding the dissemination of system information; and disseminate the requested system information.
公开号:BR112019015576A2
申请号:R112019015576-7
申请日:2018-04-11
公开日:2020-03-10
发明作者:Byun Daewook；Xu Jian；Kim Sangwon；Kim Seokjung；Lee Jaewook
申请人:Lg Electronics Inc.；
IPC主号:

专利说明:

“METHOD AND APPARATUS TO PROVIDE INFORMATION
SYSTEM"
BACKGROUND OF THE INVENTION
Field of the Invention [001] The present invention relates to a wireless communication system and, more particularly, to a method for providing system information in a scenario where a central unit and a distributed unit of a base station are divided and a device that supports them.
Related Art [002] To meet the wireless data traffic demand from the 4th generation communication system (4G) hit the market, there are continuous efforts to develop 5th generation communication systems (5G) advanced or systems pre-5G communication. For the reasons, the 5G communication system or the pre-5G communication system is called a network communication system in addition to 4G or a long-term post-evolution (LTE) system.
[003] System information refers to information essential for communication between a terminal and a base station. In 3GPP LTE, the system information is divided into a MIB (Master Information Block) and a SIB (System Information Block). The MIB consists of the most essential information. The SIB is subdivided into SIB-x forms according to its importance or cycle. The MIB is transmitted through a PBCH (Physical Diffusion Channel) which is a physical channel. The SIB consists of common control information and is transmitted via a PDCCH differently from the MIB.
SUMMARY OF THE INVENTION [004] Considering that the information generated in the RRC layer is transmitted to a user equipment (UE), the information generated needs to be transmitted to the UE through a distributed unit (DU). An
Petition 870190072500, of 7/29/2019, p. 10/191
2/57 Since the system information to be disseminated is also generated in the RRC layer of a central unit (CU), signaling between the UC and the DU may be necessary for the DU to disseminate the system information. For example, when the UC receives a request for system information from the UE through the DU, signaling between the UC and the DU may be necessary for the DU to disseminate the system information. However, in a scenario where CU and DU are divided, there is no procedure for the DU to transmit system information requested by a UE to the UE. Therefore, it is necessary to propose a method to provide system information in a scenario where a CU and DU are divided and a device that supports them.
[005] According to one modality, a method is presented for disseminating, by a DU from a base station (BS), system information in a wireless communication system. The method may include: receiving system information pertaining to a BS CU from BS BS; receive a request for system information from an UE; receive a message from a command to broadcast BS system information from BS; and disseminate the requested system information.
[006] According to another modality, a DU of a BS is provided to diffuse system information in a wireless communication system. BS DU can include: a memory; a transceiver; and a processor for connecting the memory and the transceiver, wherein the processor can be configured to control the transceiver to: receive system information pertaining to a CU from BS from CU from BS; receive a request for system information from an UE; receive a message from a command to broadcast the system information requested from the BS UC; and disseminate the requested system information.
[007] It is possible to provide system information efficiently.
BRIEF DESCRIPTION OF THE DRAWINGS
Petition 870190072500, of 7/29/2019, p. 10/20
3/57 [008] Figure 1 shows the LTE system architecture.
[009] Figure 2 shows a control plan for an LTE system radio interface protocol.
[010] Figure 3 shows a user plan for an LTE system radio interface protocol.
[011] Figure 4 shows a structure of a 5G system.
[012] Figure 5 shows an example of transmission of master information block (MIB), system information block 1 (SIB1), and other SIBs.
[013] Figure 6 illustrates a contention-based random access procedure.
[014] Figure 7 illustrates a non-contention random access procedure.
[015] Figure 8 shows a procedure for a UE to receive system information of the new type.
[016] Figure 9 shows a split-type gNB deployment scenario (centralized deployment).
[017] Figure 10 shows a function divided between a central unit and a distributed unit in a scenario of implantation of gNB of the divided type.
[018] Figure 11 illustrates a procedure for providing system information according to an embodiment of the present invention.
[019] Figure 12 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[020] Figure 13 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[021] Figure 14 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[022] Figure 15 illustrates a procedure for providing information from the
Petition 870190072500, of 7/29/2019, p. 10/21
4/57 on-demand system according to an embodiment of the present invention.
[023] Figure 16 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[024] Figure 17 is a block diagram illustrating a method for a distributed base station unit to provide system information in accordance with an embodiment of the present invention.
[025] Figure 18 is a block diagram illustrating a wireless communication system according to the modality of the present invention.
DESCRIPTION OF EXEMPLIFYING MODALITIES [026] The technology described below can be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access ( TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA can be implemented with radio technology such as universal terrestrial radio access (UTRA) or CDMA-2000. TDMA can be implemented with radio technology as a global mobile communication system (GSM) ZGeneral packet radio service (GPRS) Enhanced data rate for GSM evolution (EDGE). OFDMA can be implemented with radio technology such as the Institute of Electrical and Electronic Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), etc. IEEE 802.16m is developed from IEEE 802.16e, and provides backward compatibility with an IEEE 802.16e based system. UTRA is a part of a universal mobile telecommunication system (UMTS). The long-term evolution (LTE) of 3rd generation partnership project (3GPP) is a part of an evolved UMTS (E-UMTS) that uses E-UTRA. LTE 3GPP uses OFDMA on a downlink and uses SC-FDMA on an uplink. Advanced LTE (LTE-A) is an evolution of LTE. 5G is an evolution
Petition 870190072500, of 7/29/2019, p. 10/22
5/57 of the LTE-A.
[027] For clarity, the following description will focus on LTE-A. However, the technical resources of the present invention are not limited to it.
[028] Figure 1 shows the LTE system architecture. The communication network is widely installed to provide a variety of communication services such as voice over internet protocol (VoIP) through IMS and packet data.
[029] With reference to Figure 1, the LTE system architecture includes one or more of the user equipment (UE; 10), an evolved UMTS terrestrial radio access network (E-UTRAN) and an evolved packet core (EPC). UE 10 refers to communication equipment carried by a user. UE 10 can be fixed or mobile, and can be referred to as other terminology, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a wireless device, etc.
[030] The E-UTRAN includes one or more of the evolved B-node (eNB) 20, and a plurality of UEs can be located in a cell. ENB 20 provides an endpoint of a control plan and a user plan to the UE 10. The eNB 20 is generally a fixed station that communicates with the UE 10 and can be referred to as other terminology, such as a base station (BS), a base transceiver system (BTS), an access point, etc. One eNB 20 can be implanted per cell. There are one or more cells within the eNB 20 coverage. A single cell is configured to have one of the selected bandwidths from 1.25, 2.5, 5, 10, and 20 MHz, etc., and provides services downlink or uplink transmission to several UEs. In that case, different cells can be configured to provide different bandwidths.
[031] Later in this document, a downlink (DL) denotes communication from eNB 20 to UE 10, and an uplink (UL) denotes
Petition 870190072500, of 7/29/2019, p. 10/23
6/57 communication from UE 10 to eNB 20. In DL, a transmitter can be a part of eNB 20, and a receiver can be a part of UE 10. In UL, a transmitter can be a part of UE 10, and the receiver can be a part of the eNB 20.
[032] The EPC includes a mobility management entity (MME) that is responsible for the control plan functions, and a system architecture evolution gateway (S-GW) that is responsible for the control plan functions. user. The MME / S-GW 30 can be positioned at the end of the network and connected to an external network. The MME has UE access information or UE capacity information, and such information can be used mainly in the management of UE mobility. The S-GW is a gateway whose endpoint is an E-UTRAN. The MME / S-GW 30 provides a session endpoint and mobility management function for the UE 10. The EPC may also include a packet data network (PDN) gateway (PDN-GW). The PDN-GW is a gateway whose endpoint is a PDN.
[033] MME provides several functions including non-access layer (NAS) signaling to eNBs 20, NAS signaling security, access layer security (AS) control, Inter core network node (CN) signaling for mobility between 3GPP access networks, UE accessibility in idle mode (including control and execution of paging relay), tracking area list management (for UE in idle and active mode), P-GW and S-GW selection, selection MME for handovers with MME change, selection of service GPRS support node (SGSN) for handovers for 2G or 3G 3GPP access networks, roaming, authentication, bearer management functions including dedicated bearer establishment, message transmission support for public alert system (PWS) (which includes earthquake and tsunami warning system (ETWS) and commercial mobile alert system (CMAS)). The S-GW host offers several functions, including packet filtering per user (for example, deep inspection of
Petition 870190072500, of 7/29/2019, p. 10/24
7/57 packets), legal interception, Internet Protocol (IP) address allocation, transport level packet marking on DL, UL and DL service level loading, gating and fee application, DL fee application based on APNAMBR. For clarity, the MME / S-GW 30 will be referred to in this document simply as a “gateway”, but it is understood that this entity includes both MME and S-GW.
[034] User traffic or control traffic transmission interfaces can be used. The UE 10 and eNB 20 are connected via a Uu interface. ENBs 20 are interconnected via an X2 interface. Neighboring eNBs can have a mesh network structure that has the X2 interface. The eNBs 20 are connected to the EPC via an S1 interface. The eNBs 20 are connected to the MME via an S1-MME interface, and are connected to the S-GW via the S1-U interface. The S1 interface supports a many-to-many relationship between the eNB 20 and the MME / S-GW.
[035] eNB 20 can perform gateway 30 selection functions, routing towards gateway 30 during activation of radio resource control (RRC), programming and transmission of paging messages, programming and transmission of channel information diffusion (BCH), dynamic resource allocation for UEs 10 in UL and DL, configuration and provisioning of eNB measurements, radio carrier control, radio admission control (RAC) and connection mobility control in the LTE_ACTIVE state . In EPC, and as noted above, gateway 30 can perform paging source functions, LTEJDLE state management, user plane encryption, SAE carrier control, and NAS signaling integrity encryption and protection.
[036] Figure 2 shows a control plan for an LTE system radio interface protocol. Figure 3 shows a user plan for an LTE system radio interface protocol.
Petition 870190072500, of 7/29/2019, p. 10/25
8/57 [037] The layers of a radio interface protocol between the UE and EUTRAN can be classified into a first layer (L1), a second layer (L2) and a third layer (L3) based on the three layers inferior to the open system interconnection model (OSI) which is well known in the communication system. The radio interface protocol between the UE and the E-UTRAN can be horizontally divided into a physical layer, a data link layer, and a network layer, and can be vertically divided into a control plane (plane C) which is a stack of protocols for transmitting the control signal and a user plane (U plane) which is a stack of protocols for transmitting data information. The layers of the radio interface protocol are presented in pairs in the UE and the E-UTRAN, and are responsible for the data transmission of the Uu interface.
[038] A physical layer (PHY) belongs to L1. The PHY layer provides an upper layer with an information transfer service through a physical channel. The PHY layer is connected to a medium access control layer (MAC), which is a top layer of the PHY layer, through a transport channel. A physical channel is mapped to the transport channel. Data is transferred between the MAC layer and the PHY layer through the transport channel. Between different PHY layers, that is, a PHY layer from a transmitter and a PHY layer from a receiver, data is transferred through the physical channel using radio resources. The physical channel is modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and uses time and frequency as a radio resource.
[039] The PHY layer uses several physical control channels. A physical downlink control channel (PDCCH) reports to a UE about the resource allocation of a paging channel (PCH) and a shared downlink channel (DL-SCH), and automatic retry request information.
Petition 870190072500, of 7/29/2019, p. 10/26
9/57 hybrid (HARQ) related to DL-SCH. The PDCCH can transmit an UL grant to report to the UE on the allocation of UL transmission resource. A physical control format indicator channel (PCFICH) reports the number of OFDM symbols used for PDCCHs to the UE, and is transmitted in each subframe. A physical hybrid ARQ indicator channel (PHICH) transmits a HARQ confirmation (ACK) / non-confirmation (NACK) signal in response to UL transmission. A physical uplink control channel (PUCCH) transmits UL control information such as HARQ ACK / NACK for DL transmission, programming request and CQI. A physical uplink shared channel (PUSCH) transmits a UL uplink shared channel (SCH).
[040] A physical channel consists of a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain. A subframe consists of a plurality of symbols in the time domain. A subframe consists of a plurality of resource blocks (RBs). A RB consists of a plurality of symbols and a plurality of subcarriers. In addition, each subframe can use specific subcarriers of symbols specific to a corresponding subframe for a PDCCH. For example, a first symbol in the subframe can be used for the PDCCH. The PDCCH transmits dynamic allocated resources, such as a physical resource block (PRB) and modulation and coding scheme (MCS). A transmission time interval (TTI) which is a unit of time for data transmission can be equal to the duration of a subframe. The duration of a subframe can be 1 ms.
[041] The transport channel is classified into a common transport channel and a dedicated transport channel according to whether the channel is shared or not. A DL transport channel for transmitting data from the network to the UE includes a broadcast channel (BCH) for transmitting system information, a paging channel (PCH) for transmitting a paging message, a DL-SCH
Petition 870190072500, of 7/29/2019, p. 10/271
10/57 to transmit user traffic or control signals, etc. The DL-SCH supports HARQ, dynamic link adaptation varying the modulation, encoding and transmission of energy, and allocation of dynamic and semi-static resources. DL-SCH can also allow diffusion throughout the cell and the use of beam formation. System information carries one or more blocks of system information. All blocks of information in the system can be transmitted with the same periodicity. Traffic and control signals from a multimedia broadcast / multicast service (MBMS) can be transmitted via the DL-SCH or a multicast channel (MCH).
[042] An UL transport channel for transmitting data from the UE to the network includes a random access channel (RACH) to transmit an initial control message, an UL-SCH to transmit user traffic or control signals, etc. UL-SCH supports HARQ and dynamic link adaptation by varying transmission power and potentially modulation and encoding. UL-SCH may also allow the use of beam formation. RACH is typically used for initial access to a cell.
[043] A MAC layer belongs to L2. The MAC layer provides services to a radio link control (RLC) layer, which is an upper layer of the MAC layer, through a logical channel. The MAC layer provides a function for mapping multiple logical channels to multiple transport channels. The MAC layer also provides a logical channel multiplexing function by mapping multiple logical channels to a single transport channel. A MAC sublayer provides data transfer services on logical channels.
[044] Logical channels are classified into control channels for transferring control plan information and traffic channels for transferring user plan information, according to a type of information transmitted. That is, a set of logical channel types is defined to
Petition 870190072500, of 7/29/2019, p. 10/28
11/57 different data transfer services offered by the MAC layer. The logical channels are located above the transport channel, and are mapped to transport channels.
[045] Control channels are used only for the transfer of control plan information. The control channels provided by the MAC layer include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH) and a communication channel. dedicated control (DCCH). BCCH is a downlink channel of broadcast system control information. The PCCH is a downlink channel that transfers paging information and is used when the network does not know the cell location of a UE. CCCH is used by UEs that have no RRC connection to the network. MCCH is a point-to-multipoint downlink channel used to transmit MBMS control information from the network to a UE. DCCH is a two-way point-to-point channel used by UEs that have an RRC connection that transmits dedicated control information between a UE and the network.
[046] Traffic channels are used only for the transfer of user plan information. The traffic channels provided by the MAC layer include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH). The DTCH is a point-to-point channel, dedicated to a UE for the transfer of user information and can be presented in both uplink and downlink. MTCH is a downlink channel from point to multipoint to transmit traffic data from the network to the UE.
[047] Uplink connections between logical channels and transport channels include the DCCH that can be mapped to UL-SCH, the DTCH that can be mapped to UL-SCH and the CCCH that can be mapped to UL-SCH. Downlink connections between logical channels and transport channels
Petition 870190072500, of 7/29/2019, p. 10/29
12/57 include the BCCH that can be mapped to the BCH or DL-SCH, the PCCH that can be mapped to the PCH, the DCCH that can be mapped to the DL-SCH and the DTCH that can be mapped to the DL-SCH, the MCCH that can be mapped to the MCH, and the MTCH that can be mapped to the MCH.
[048] An RLC layer belongs to L2. The RLC layer provides a function of adjusting a data size, so that it is suitable for a lower layer to transmit data, concatenating and segmenting data received from an upper layer in a radio section. In addition, to ensure a variety of quality of service (QoS) required by a radio carrier (RB), the RLC layer provides three modes of operation, namely a transparent mode (TM), an unconfirmed mode (UM) and a confirmed mode (AM). AM RLC provides a retransmission function through an automatic retry request (ARQ) for reliable data transmission. However, an RLC layer function can be implemented with a function block within the MAC layer. In this case, the RLC layer may not exist.
[049] A layer of packet data convergence protocol (PDCP) belongs to L2. The PDCP layer provides a header compression function function that reduces unnecessary control information so that data that is transmitted using IP packets, such as IPv4 or IPv6, can be efficiently transmitted over a radio interface that has a width relatively small bandwidth. Header compression increases transmission efficiency in the radio section by transmitting only the necessary information in a data header. In addition, the PDCP layer provides a security function. The security function includes encryption that prevents third-party inspection, and integrity protection that prevents manipulation of third-party data.
[050] A radio resource control layer (RRC) belongs to L3. THE
Petition 870190072500, of 7/29/2019, p. 10/30
13/57 RLC layer is located in the lower portion of L3, and is only defined in the control plane. The RRC layer has the function of controlling a radio resource between the UE and the network. For this, the UE and the network exchange an RRC message through the RRC layer. The RRC layer controls the logical channels, transport channels and physical channels in relation to the configuration, reconfiguration and release of RBs. An RB is a logical path provided by L1 and L2 for delivering data between the UE and the network. That is, RB means that a service provided L2 with data transmission between the UE and E-UTRAN. The configuration of the RB involves a process to specify a radio protocol layer and channel properties to provide a specific service and to determine its detailed parameters and operations. The RB is classified into two types, that is, a signaling RB (SRB) and a data RB (DRB). The SRB is used as a way to transmit an RRC message on the control plane. DRB is used as a way to transmit user data on the user plan.
[051] A Non-Access Stratum (NAS) layer placed over the RRC layer performs functions such as session management and mobility management.
[052] Referring to Figure 2, the RLC and MAC layers (terminated in the eNB on the network side) can perform functions such as programming, automatic repeat request (ARQ), and hybrid automatic repeat request (HARQ). The RRC layer (terminated in the eNB on the network side) can perform functions such as broadcast, paging, RRC connection management, RB control, mobility and reporting functions and UE measurement control. The NAS control protocol (terminated at the gateway MME on the network side) can perform functions such as SAE port management, authentication, LTEJDLE mobility management, LTEJDLE paging source, and security control for signaling between the gateway and UE.
Petition 870190072500, of 7/29/2019, p. 10/31
14/57 [053] Referring to Figure 3, the RLC and MAC layers (terminated in the eNB on the network side) can perform the same functions as the control plane. The PDCP layer (terminated in the eNB on the network side) can perform user plan functions such as header compression, integrity protection and encryption.
Later in this document, a 5G network structure is described.
[054] Figure 4 shows a structure of a 5G system.
[055] In the case of an evolved packet core (EPC) that has an existing evolved packet system (EPS) core network structure, a function, a reference point, a protocol or the like is defined for each entity as a mobility management entity (MME), a service gateway (S-GW), a packet data network gateway (P-GW) or the like.
[056] On the other hand, in the case of a 5G core network (or a NextGen core network), a function, a reference point, a protocol, or the like is defined for each network function (NF). That is, in the 5G core network, the function, the reference point, the protocol, or similar is not defined for each entity.
[057] Referring to Figure 4, the 5G system structure includes at least one UE 10, a next generation radio access network (NG-RAN), and a next generation core (NGC).
[058] The NG-RAN can include at least one gNB 40, and a plurality of UEs can be present in a cell. GNB 40 provides the UE with control plane and user plane endpoints. GNB 40 is generally a fixed station that communicates with the UE 10 and can be referred to as other terminology, such as a base station (BS), a base transceiver system (BTS), an access point, or the like. A gNB 40 can be arranged in each cell. At least one cell can be present in a coverage of gNB 40.
[059] The NGC may include an access and mobility function (MFA) and a
Petition 870190072500, of 7/29/2019, p. 10/32
15/57 session management function (SMF) that are responsible for a control plan function. The AMF can be responsible for a mobility management role, and the SMF can be responsible for a session management role. The NGC can include a user plan role (UPF) that is responsible for a user plan role.
[060] User traffic or control traffic transmission interfaces can be used. The UE 10 and the gNB 40 can be connected via a Uu interface. The 40 gNBs can be interconnected via an X2 interface. Neighboring gNBs 40 may have a mesh network structure based on an Xn interface. The 40 gNBs can be connected to an NGC via an NG interface. The 40 gNBs can be connected to an AMF via an NG-C interface, and can be connected to an UPF via an NGU interface. The NG interface supports a many-to-many relationship between gNB 40 and AMF / UPF 50.
[061] A gNB host can perform functions such as radio resource management functions, IP header compression, and user data stream encryption, selecting an AMF in the UE setting when no routing to an AMF can be determined from the information provided by the UE, routing data from the user plan towards the UPF (s), programming and transmitting paging messages (originating from the AMF), programming and transmitting system broadcast information (originating from the AMF or O&M) or measurement and configuration of measurement report for mobility and scheduling.
[062] An access and mobility function (AMF) host can perform primary functions such as NAS signaling termination, NAS signaling security, AS security control, internal CN signaling for mobility between 3GPP access networks, UE accessibility in mode inactive (including control and execution of paging relay), management of the list of areas of
Petition 870190072500, of 7/29/2019, p. 10/33
16/57 tracking (for EU in idle and active mode), selection of AMF for handovers with change of AMF, authentication of access or authorization of access, including verification of roaming rights.
[063] A user plan function (UPF) host can perform primary functions such as an intra- / inter-RAT mobility anchor point (where applicable), external PDU session point for data network interconnection, routing & packet forwarding, packet inspection and part of the policy rule application user plan, traffic usage report, uplink classifier to support routing traffic flows to a data network, branch point to support PDU session multi-homed, QoS management for user plan, eg packet filtering, gating, UL / DL rate application, uplink traffic verification (SDF flow mapping for QoS), transport level packet marking on the uplink and downlink, or downlink packet buffering and downlink data notification trigger.
[064] A session management function (SMF) host can perform primary functions such as session management, UE IP address allocation and management, UP function selection and control, configuring traffic routing on the UPF to route the traffic to the appropriate destination, control part of the policy and QoS application, or downlink data notification.
Later in this document, the system information will be described.
[065] Figure 5 shows an example of transmission of master information block (MIB), system information block 1 (SIB1), and other SIBs.
[066] An LTE cell broadcasts the basic parameters necessary for the operation of a UE in IDLE_MODE and a UE in CONNECTED_MODE through a plurality of separate information blocks. Examples of information blocks include a MIB, SIB1, SIB2, and other SIBs (SIBn).
Petition 870190072500, of 7/29/2019, p. 10/34
17/57 [067] Ο ΜΙΒ includes the most essential parameters necessary for a UE to access a cell. With reference to Figure 5, a MIB message is broadcast through a BCH according to a 40 ms periodicity, and the MIB transmission is repeated on all radio frames within the 40 ms periodicity. The UE receives an SIB message using the parameters received through the MIB.
[068] There are different types of SIBs.
[069] SIB1 includes information associated with cell access, and particularly includes programming information in other SIBs (SIB2 to SIBn) other than SIB1. SIBs that have the same transmission periodicity between SIBs except SIB1 are transferred using the same system information (SI) message. In this way, the programming information includes a mapping relationship between each SIB and an SI message. An IS message is transmitted within an IS window in a time domain, and each IS message is associated with an IS window. Since the different SI SI windows do not overlap, only one SI message is transmitted within an SI window. In this way, the programming information includes the duration of an IS window and an IS transmission frequency. The transmission time / frequency of an SI message is determined by dynamic programming by a BS. The SIB1 is broadcast over a shared downlink channel (DL SCH) according to a periodicity of eight radio frames (that is, a periodicity of 80 ms), and the SIB1 is repeatedly retransmitted in a fifth sub-frame of a frame. SFN-mod-2 radio within 80 ms.
[070] SIB2 includes information necessary for a UE to access a cell. SIB2 includes information on an uplink cell bandwidth, a random access parameter, and a
Petition 870190072500, of 7/29/2019, p. 10/35
18/57 uplink power.
[071] SIB3 includes cell reselection includes. The SIB4 includes frequency information in a service cell and intra-frequency information in a neighboring cell for cell reselection. The SIB5 includes frequency information on a different E-UTRA and inter-frequency information on a neighboring cell for cell reselection. The SIB6 includes frequency information in an IITRA and information in a neighboring IITRA cell for cell reselection. The SIB7 includes frequency information in a GERAN for cell reselection. The SIB8 includes information in a neighboring cell.
[072] The SIB9 includes an identifier (ID) of Home eNodeB (HeNB). The SIB10 to SIB12 include a public warning message, for example, for earthquake warning. The SIB14 is used to support is used to support access restrictions and to control the UEs to access a cell. The SIB15 includes information needed to receive an MBMS on contiguous carrier frequencies. The SIB16 includes information related to GPS time and coordinated universal time (UTC). The SIB17 includes auxiliary RAN information.
[073] Not all SIBs need to be present at all times. For example, SIB9 is not needed in a mode where a wireless carrier establishes a HeNB, while SIB13 is not needed if a cell does not provide MBMS.
Later in this document, random access will be described.
[074] Random access is used by a UE to achieve uplink synchronization with a BS or to allocate an uplink radio resource. After the power is turned on, a UE obtains downlink synchronization with an initial cell and receives information from the system. The UE then acquires, from the system information, a set of available random access preambles and information about a radio resource used for the transmission of a random access preamble. The radio resource used to
Petition 870190072500, of 7/29/2019, p. 36/101
19/57 transmission of the random access preamble can be specified as a radio frame and / or a combination of at least one or more subframes. The UE transmits a random access preamble randomly selected from the set of random access preambles, and the BS that received the random access preamble sends a timing alignment (TA) value for uplink synchronization to the UE via a random access response. In this way, the UE obtains uplink synchronization.
[075] That is, the BS allocates a random access preamble dedicated to a specific UE, and the UE performs random access without contention using the random access preamble. That is, there may be a process for selecting a preamble of random access, random access based on contention in which a UE selects and randomly uses a preamble of random access from a specific set and random access without contention in which only a specific UE is allocated to a random access preamble by a BS. Random access without contention can be used for a handover procedure or upon request by a BS command.
[076] Figure 6 illustrates a contention-based random access procedure.
[077] With reference to Figure 6, a UE randomly selects a random access preamble from a set of random access preambles indicated by system information or a handover command. The UE selects a radio resource to transmit the random access preamble in order to transmit the selected random access preamble (S610). The radio resource can be a specific subframe, and the radio resource selection can select a physical random access channel (PRACH).
[078] After the transmission of the preamble of random access, the UE tries to receive a random access response within a window of reception of
Petition 870190072500, of 7/29/2019, p. 37/101
20/57 random access response indicated by the system information or the handover command and, consequently, receives a random access response (S620). The random access response can be transmitted in a MAC PDU format and the MAC PDU can be forwarded through a shared downlink physical channel (PDSCH). In addition, a physical downlink control channel (PDCCH) is also routed so that the UE properly receives the information routed through the PDSCH. That is, the PDCCH includes information on the UE that receives the PDSCH, frequency and time information on a radio resource for the PDSCH, and a transmission format for the PDSCH. Once the PDCCH forwarded to the UE is successfully received, the UE properly receives the random access response transmitted through the PDSCH based on the information in the PDCCH.
[079] The random access response may include a random access preamble identifier (ID), an uplink radio resource (UL grant), a temporary cell-radio network identifier (C-RNTI), and a time alignment command (TAC). Since a random access response can include random access response information for one or more UEs, a random access preamble ID can be included to indicate a UE for which a UL grant, a temporary C-RNTI and a TAC are valid. The random access preamble ID can be a random access preamble ID received by a BS. The TAC can be included as information for the UE to adjust the uplink synchronization. The random access response can be indicated by a random access ID on the PDCCH, that is, a temporary random radio access network identifier (RA-RNTI).
[080] When the UE receives the valid random access response for it, the UE processes the information included in the random access response and performs the scheduled transmission to the BS (S630). That is, the UE applies the TAC and
Petition 870190072500, of 7/29/2019, p. 38/101
21/57 stores the temporary C-RNTI. In addition, the UE transmits data stored in a UE buffer or newly generated data to the BS using the UL grant. In this case, the information to identify the UE needs to be included, this serves to identify the UE in order to avoid a collision since the BS does not determine which UEs perform random access in a contention-based random access process.
[081] There are two methods that include information for identifying an UE. When the UE has a valid cell ID already allocated by a corresponding cell before performing random access, the UE transmits its cell ID through the grant of UL. However, when the UE does not receive a valid cell ID before the random access process, the UE transmits a unique cell ID (for example, S-TMSI or random ID). In general, the unique ID is longer than the cell ID. When the UE transmits data through the UL grant, the UE starts a contention resolution timer.
[082] After transmitting data including the UE ID through the UL grant allocated when receiving the random access response, the UE waits for an instruction from BS to avoid a collision (S640). That is, the UE tries to receive the PDCCH to receive a specific message. There are two methods proposed for receiving a PDCCH. As described above, when the UE ID transmitted through the UL grant is a cell ID, the UE can attempt to receive the PDCCH using the cell ID of the UE. In this case, when the UE receives the PDCCH via the cell ID of the UE before the contention resolution timer expires, the UE determines that the random access was normally performed and ends the random access. When the ID transmitted through the UL grant is the unique ID, the UE may attempt to receive the PDCCH using the temporary C-RNTI included in the random access response. In that case, when the UE receives the PDCCH via the temporary cell ID before the
Petition 870190072500, of 7/29/2019, p. 39/101
22/57 containment resolution expires, the UE identifies data forwarded by the PDSCH indicated by the PDCCH. When the data includes the unique ID of the UE, the UE can determine that random access was normally performed and can terminate random access.
[083] Figure 7 illustrates a non-contention random access procedure.
[084] Unlike contention-based random access, random access without contention can be terminated when a UE receives a random access response.
[085] Random access without contention can be initiated by a request, such as a handover and / or a command from a BS. Here, in these two cases, contention-based random access can also be performed.
[086] The UE is allocated by BS to a designated random access preamble that has no collision possibility. The random access preamble can be allocated through a handover command and a PDCCH command (S710).
[087] After being assigned the random access preamble assigned to the UE, the UE transmits the random access preamble to the BS (S720).
[088] Upon receipt of the random access preamble, BS transmits a random access response to the UE in response (S730). A procedure associated with the random access response was mentioned above in the numerical reference in Figure 6.
[089] The number of system information blocks is continually increasing, and radio resources must broadcast a system information block. Thus, as the number of blocks of system information increases, the amount of radio resources needed to broadcast a block of system information also inevitably increases.
Petition 870190072500, of 7/29/2019, p. 40/101
23/57
To solve this problem, information of the new type system is proposed.
[090] Figure 8 shows a procedure for a UE to receive system information of the new type.
[091] With reference to Figure 8, the new type system information can be divided into minimal system information and other system information. Minimum system information can be periodically disseminated. Minimum system information can include basic information needed for initial access to a cell and information to acquire any other system information that is provisioned on an on-demand basis or is periodically disseminated. Minimum system information can include at least one of an SFN, a list of PLMNs, a cell ID, a cell camp parameter, and a RACH parameter. When a network allows for an on-demand mechanism, a parameter required to request other system information may be included in the minimum system information. The other system information can refer to all system information not broadcast in the minimum system information.
Later in this document, a RRC INACTIVE status of a UE will be described.
[092] In a discussion of the new radio (NR) standardization, a state of RRCJNACTIVE was recently introduced in addition to an existing state RRC_CONNETED and an existing state RRCJDLE. The RRCJNACTIVE state is a state introduced to efficiently manage a specific UE (for example, mMTC UE). A UE in the RRCJNACTIVE state performs a radio control procedure similar to that of a UE in the RRCJDLE state to reduce energy consumption. However, the UE in the RRCJNACTIVE status maintains the connection state between the UE and a network similar to the RRC_CONNECTED state to minimize a control procedure necessary for the
Petition 870190072500, of 7/29/2019, p. 41/101
24/57 transition to RRC_CONNECTED state. In the RRCJNACTIVE state, a radio access feature is released, while a wired connection can be maintained. For example, in the RRCJNACTIVE state, a radio access resource is released, while an NG interface between a gNB and an NGC or an S1 interface between an eNB and an EPC can be maintained. In the RRCJNACTIVE state, a core network recognizes that the UE is normally connected to a BS. However, BS may not perform connection management of the UE in the RRCJNACTIVE state.
[093] For a UE in a lightly connected mode, an MME can keep the UE's S1 connection enabled to hide the state transition and mobility of the core network. That is, for the UE in the RRCJNACTIVE state, an MFA can keep the UE's NG connection activated to hide the transition and mobility of a next generation core (NGC). In this specification, the RRCJNACTIVE status can be used in a sense similar to a lightly connected mode, a lightly connected mode, or a semi-connected mode.
Later in this document, a scenario for the deployment of RAN 5G will be described.
[094] A 5G RAN can be classified into a 'non-centralized deployment' scenario, a 'deployment co-located with E-UTRA and a' centralized deployment 'scenario according to a way to deploy a BS function in a central unit and a distributed unit and according to the possibility of it coexisting with a BS 4G. In this specification, the 5G RAN, a gNB, a next generation B node, a new RAN, and a new radio BS (NR BS) may imply a newly defined BS for 5G.
[095] Figure 9 shows a split-type gNB deployment scenario (centralized deployment).
[096] With reference to Figure 9, a gNB can be divided into one unit
Petition 870190072500, of 7/29/2019, p. 42/101
25/57 central and a distributed unit. That is, gNB can be operated by dividing it in layers. The central unit can perform a gNB upper layer function, and the distributed unit can perform a lower gNB layer function.
[097] Figure 10 shows a function divided between a central unit and a distributed unit in a split-type gNB deployment scenario.
[098] With reference to Figure 10, in the case of option 1, an RRC layer is in a central unit, and an RLC layer, a MAC layer, a physical layer and an RF are in a distributed unit. In the case of option 2, the RRC layer and the PDCP layer are in the central unit, and the RLC layer, the MAC layer, the physical layer and the RF are in the distributed unit. In the case of option 3, the RRC layer, the PDCP layer and an upper RLC layer are in the central unit, and a lower RLC layer, the MAC layer, the physical layer and the RF are in the central unit. In the case of option 4, the RRC layer, the PDCP layer and the RLC layer are in the central unit, and the MAC layer, the physical layer and the RF are in the distributed unit. In the case of option 5, the RRC layer, the PDCP layer, the RLC layer and an upper MAC layer are in the central unit, and a MAC layer, the physical layer and the RF are in the distributed unit. In the case of option 6, the RRC layer, the PDCP layer, the RLC layer and the MAC layer are in the central unit, and the physical layer and the RF layer are in the distributed unit. In the case of option 7, the RRC layer, the PDCP layer, the RLC layer, the MAC layer and an upper physical layer are in the central unit, and a lower physical layer and the RF are in the distributed unit. In the case of option 8, the RRC layer, the PDCP layer, the RLC layer, the MAC layer and the physical layer are in the central unit, and the RF is in the distributed unit.
[099] Later in this document, the central unit can be called a CU, and the distributed unit can be called a DU at present
Petition 870190072500, of 7/29/2019, p. 43/101
26/57 descriptive report. ACU can be a logical node that hosts a radio resource control (RRC), service data adaptation protocol (SDAP), and gNB packet data convergence protocol (PDCP) layers. DU can be a logical node that hosts radio link control (RLC), media access control (MAC), and physical layers (PHY) of gNB. Alternatively, CU can be a logical node that hosts RRC and PDCP layers of an en-gNB.
[0100] Considering that the information generated in the RRC layer is transmitted to a UE, the information generated needs to be transmitted to the UE through the DU. Since the system information that will be disseminated is also generated in the CU's RRC layer, signaling between the UC and DU may be necessary for the DU to disseminate the system information. For example, when the UC receives a request for system information from the UE through the DU, signaling between the UC and the DU may be necessary for the DU to disseminate the system information. However, in a scenario where CU and DU are divided, there is no procedure for the DU to transmit system information requested by a UE to the UE. Later in this document, a method for providing system information in a scenario where a CU and DU are divided and a device that supports them will be described in accordance with an embodiment of the present invention.
[0101] Figure 11 illustrates a procedure for providing system information according to an embodiment of the present invention.
[0102] With reference to Figure 11, in step S1110, a DU of a BS can receive information from the system of a CU of the BS. System information can be received via an F1 interface. The F1 interface can refer to an interface between CU and DU. The system information can be system information pertaining to the BS CU. BS's DU can receive, from CU, all other system information excluding SIB1 from the
Petition 870190072500, of 7/29/2019, p. 44/101
27/57 system belonging to CU. System information pertaining to CU can be included in an RRC container. System information pertaining to the BS CU can be transmitted from the BS CU to the BS DU in an F1 configuration procedure. System information can be included in an F1 configuration response message.
[0103] Additionally, the BS DU can receive information related to the system information from the BS CU. Information related to system information can include at least one of a SIB ID, a container that includes system information (SI), broadcast time information, logical channel related information, broadcast activation, a DU ID , a cell ID and a beam ID.
[0104] For example, the F1 configuration response message can be defined as shown in Table 1.
[TABLE 1]
lE / Group Name Presence Banner Semantic description Criticism Criticality Assigned Message Type M YEA reject Transaction ID M YEA reject List of Cells to be Activated0. 1 > List of cells that will be activated1.<maxCellingNBDU> List of cells that will be activated YEA reject »NCGI M - - »GNB-CU System Information MRRC container with system information pertaining to gNB-CU - - »PCI OPhysical Cell ID - -
[0105] With reference to Table 1, the F1 configuration response message transmitted from CU to DU can include information from the gNB-CU system. The gNB-CU system information can be an RRC container that includes the system information pertaining to CU. For example, system information
Petition 870190072500, of 7/29/2019, p. 45/101
28/57 of gNB-Cll may include all other system information excluding SIB1 from the system information pertaining to CU.
[0106] In step S1120, the BS DU can receive a request for system information from the UE. The UE may be in the RRCJNACTIVE state. The UE may be in the RRCJDLE state. Requesting system information from the UE can be included in message 3 in a random access procedure. When the request for system information is transmitted via message 3, the DU of the BS may not interpret message 3, as the DU does not have the RRC layer. Therefore, the BS DU needs to transmit message 3 to the BS CU. System information can be system information on demand or other system information.
[0107] In step S1130, the DU of the BS can transmit the request for system information, received from the UE to CU. A message that includes a container taking advantage that the request for system information can be transmitted from DU to CU. The request for system information may be included in an initial message transfer message from UL RRC. The UL RRC initial message transfer message can be transmitted by the DU to forward an initial layer 3 message to the CU on the F1 interface.
[0108] For example, the initial message transfer message from UL RRC can be defined as in Table 2.
[TABLE 2]
lE / Group Name Presence Banner Semantic description Criticism and Criticism and Attributed Message Type M YEA ignore IDdegNB-DU UE F1AP M YEA reject NCGI MGlobal NG-RAN Cell Identifier (NCGI) YEA reject C-RNTI C-RNTI allocated to gNB-DU YEA reject RRC container M YEA reject
Petition 870190072500, of 7/29/2019, p. 46/101
29/57
lE / Group Name Presence Banner Semantic description Criticism and Criticism and Attributed DU àCU RRC container OCellGroupConfig IE. At least required to transmit the SRB1 configuration YEA reject
[0109] In step S1140, the DU of the BS can receive, from the CU, a message from a command to spread the requested system information. The message can be a system information broadcast request message. The message can be a system information delivery command message. The message can include information indicating the requested system information. For example, the message can include an identity, an index, or a number for the requested system information. For example, the message may include other types of system information. In this way, DU can know that the system information corresponding to another type of system information needs to be disseminated. In addition, the message may include information about broadcast time. Broadcast time information can be a time interval for broadcasting other system information.
[0110] For example, the system information dissemination request message or the system information delivery command message can be defined as shown in Table 3.
[TABLE 3]
lE / Group Name Presence Banner IE type and reference Semantic description Criticism and Criticism and Attributed Message Type M YEA reject NCGI M NR cell identifier -SI type list1 > SI type IEs1..<maxnoofSITy pes>
Petition 870190072500, of 7/29/2019, p. 47/101
30/57
lE / Group Name Presence Banner IE type and reference Semantic description Criticism and Criticism and Attributed »Other Type of ISSI MENUMERATED Other Type of Sl YEA reject »Diffusion Time Interval MALL Other Sl diffusion time interval FFS FFS
[0111] With reference to Table 3, CU of BS can transmit the message including the other type of system information to the DU, and the DU can disseminate the system information corresponding to the other type of system information. In addition, the BS CU can transmit a message including a broadcast time slot to the DU, and the DU can broadcast the system information corresponding to the other type of system information based on the broadcast time slot.
[0112] In step S1150, the DU of BS can provide the requested system information to the UE based on the message received. System information can be provided to the UE through broadcast or dedicated signaling.
[0113] In accordance with the modality of the present invention, CU can provide DU with system information pertaining to CU and information necessary for the dissemination of system information. Upon receipt of a request for system information from the UE, the DU can transmit the request to the CU and can receive, from the CU, information indicating the system information that needs to be disseminated or transmitted. CU can provide information related to SIB prior to DU, thereby reducing the signaling between CU and DU caused by the request for system information from the UE. In addition, CU can transmit only the type of system information that will be disseminated to the DU, thus reducing the signaling between CU and DU caused by the request for system information from the UE.
Petition 870190072500, of 7/29/2019, p. 48/101
31/57 [0114] Figure 12 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[0115] According to the embodiment of the present invention, a Cll can provide a DLI with an indication about a requested SIB. Alternatively, Cll may provide DLI with information related to the requested SIB. For example, when DLI receives a request for system information from a UE via message 3 in a random access procedure, the indication about the requested SIB or information related to the requested SIB can be provided to the DU from ASS.
[0116] According to the modality of the present invention, during an F1 configuration procedure, CU can provide DU with information related to some or all of the SIBs that CU supports. For example, CU can provide DU with information related to all system information belonging to CU. Alternatively, CU can provide DU with all other system information excluding SIB1 from the system information belonging to CU.
[0117] In accordance with the modality of the present invention, when CU determines to update information related to SIB, CU can transmit updated information related to SIB to DU. Also, when there is no request for system information on demand for the requested SIB, DU can release information related to the requested SIB.
[0118] With reference to Figure 12, in step S1201, when an F1 interface is configured, CU can transmit to DU, a message including information related to all SIBs provided by CU. Alternatively, CU may transmit a message to DU including information related to some SIBs provided by CU. For example, information related to some SIBs can be minimal system information or system information on a
Petition 870190072500, of 7/29/2019, p. 49/101
32/57
SIB often requested by a UE. Information related to some SIBs can be transmitted to efficiently manage DU resources to store information related to a SIB. The message can be an F1 configuration response message or an F1 configuration request message. For example, CU can transmit a message to DU including information related to SIBx.
[0119] The SIB-related information included in the message can be provided by SIB. SIB-related information can include at least one of a SIB ID, a container that includes system information, broadcast time information, logical channel related information, broadcast activation, a DU ID, a cell ID and a beam ID.
[0120] Information related to SIB may include system information and information necessary for DU to disseminate system information. The container can be used to transmit system information including one or more parameters that will be broadcast from CU to DU. Diffusion time information can be information or time to help program the DU to diffuse system information. For example, broadcast time information can include at least one of the duration of a window in which system information is broadcast, the number of times system information is broadcast, or the location of system information broadcast within from the window. For each parameter in the SIB, there may be information about diffusion time per parameter, which may have a different value. Logical channel information can include logical channel information indicating a logical channel through which system information is transmitted. For example, the logical channel information can be a logical channel ID. Broadcast activation can indicate whether the system information provided is broadcast. Broadcast activation can be adjusted when information from the
Petition 870190072500, of 7/29/2019, p. 50/101
33/57 system are always broadcast or are frequently requested by a UE. When the DU controls, manages, or spans one or more cells, the F1 configuration response message or the F1 configuration request message can include a cell ID for each cell. When the DU controls, manages, or encompasses one or more beams, the F1 configuration response message or the F1 configuration request message can include a beam ID for each beam.
[0121] In step S1202, after an F1 configuration procedure is completed, the DU can broadcast the system information related to the SIB whose broadcast is activated.
[0122] In step S1203, a UE can transmit a system information request to the DU to request system information on demand. The request for system information may be included in message 3 in a random access procedure. The UE may be in the RRCJDLE state. The UE may be in the RRCJNACTIVE state. In this specification, the system information on demand can be system information provided via broadcast signaling or dedicated signaling upon request from a UE.
[0123] In step S1204, upon receipt of the system information request from the UE, the DU can transmit the system information request to CU. A message including a container taking advantage of the request for system information can be transmitted from DU to CU. The message can be an initial message from the UE or a new message.
[0124] Upon receiving the message from the DU, CU can identify the requested system information on demand based on the system information request received. There may be two possible options depending on whether CU has provided DU with information related to all SIBs
Petition 870190072500, of 7/29/2019, p. 51/101
34/57 supported by UC in step S1201.
(1) Option A [0125] When CU provides DU with information related to all CU-owned SIBs, CU can transmit information on a SIB requested to DU in step S1205. Information in the requested SIB can indicate the requested SIB. The information in the requested SIB can be an identity, an index, or an SIB number identified based on the system's information request. For example, CU can transmit a type of SIB to DU. Consequently, CU can command DU to broadcast the requested SIB, and DU can broadcast system information related to the indicated SIB.
[0126] Additionally, in step S1205, CU can transmit to DU, a message including a container using a response to the system's information request. The message can be a forward link RRC transport message or a new message.
(2) Option B [0127] When CU provides information related to some SIBs to DU and / or receives a request for information from the system requesting a SIB that is not provided to DU, CU transmits a message to DU, including a container using a response to the system information request in step S1205a. The message can be a forward link RRC transport message or a new message.
[0128] In step S1205b, CU can transmit a message to DU, providing information related to a requested SIB. For example, CU may transmit a message to DU including information related to SIBy. The message can be a system information broadcast request message or a new message. The SIB-related information included in the message can be provided by SIB. Information related to the SIB
Petition 870190072500, of 7/29/2019, p. 52/101
35/57 can include at least one of a SIB ID, a container that includes system information, broadcast time information, logical channel related information, broadcast activation, a DU ID, a cell ID and an ID beam. Upon receipt of the message from the CU, the DU can store the information related to the requested SIB.
[0129] In step S1205c, the DU can transmit a system information broadcast reply message or a new message to CU. For the requested SIB, the response message can include at least one of a SIB ID, a DU ID, a cell ID and a beam ID corresponding to an ID included in the message received in step S1205b. For the SIB, when the ID included in the request message is not included in the response message, CU can recognize that an entity (for example, DU, cell and / or beam) indicated by CU cannot broadcast system information.
[0130] In step S1206, upon receipt of the message from the CU, the DU can transmit message 4 to the UE.
[0131] In step S1207, the DU can broadcast system information related to the requested SIB. System information related to the requested SIB can be broadcast after message 4 is transmitted. For the SIB, when the DU stores a cell ID or a beam ID, the DU can broadcast the SIB-related system information in a beam or cell indicated by the ID.
[0132] In step S1208, when CU determines to update the information related to the SIB, CU can transmit a system information broadcast request message or a new message to DU. The system information broadcast request message or the new message can include information related to SIB by SIB. For example, CU may transmit a message to DU including information related to updated SIBz. For example, CU can transmit a message to DU including
Petition 870190072500, of 7/29/2019, p. 53/101
36/57 information related to SIBz that will be updated. SIB-related information can include at least one of a SIB ID, a container that includes system information, broadcast time information, logical channel related information, and broadcast activation. Enabling broadcast may indicate that system information related to SIBz is not broadcast.
[0133] In step S1209, upon receipt of the message from the CU, the DU can replace the information previously provided to the SIB with the information received related to the SIB. The DU can then transmit a system information broadcast reply message or a new message including a SIB ID related to the updated SIB to CU.
[0134] In step S1210, referring to the requested SIB, when there is no request for system information on demand during a specific period of time, the DU can determine whether to release the information related to the requested SIB to efficiently manage the DU's resources. to store information related to the requested SIB.
[0135] In step S1211, when determining the release of information related to the requested SIB, the DU can transmit a message indicating the release of system information or a new message to the DU to indicate that the DU no longer has the information related to the SIB. The message can include a released SIB identity, index, or number. For example, the message can include the type of the released SIB. After the message is transmitted, the DU can release information related to the indicated SIB.
[0136] In accordance with the modality of the present invention, CU can provide DU with system information and information necessary for the dissemination of system information. The information can basically be provided when the dissemination of the system information is supported. Alternatively, information can be provided upon request from a UE. THE
Petition 870190072500, of 7/29/2019, p. 54/101
37/57
CU can provide SIB-related information prior to DU, thereby reducing signaling between CU and DU caused by a request for system information from the UE. In addition, it is possible to efficiently manage DU resources to store information related to a requested SIB.
[0137] Figure 13 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[0138] According to the modality of the present invention, a CU can provide a DU with information related to some or all of the SIBs that CU provides using an F1 configuration procedure. In addition, when CU receives, from the DU, a request for system information related to a SIB corresponding to system information on demand from a UE, or determines to update information related to the SIB, CU can transmit information related to a requested or updated SIB to the DU. In addition, when there is no request for system information on demand for the requested SIB, DU can release information related to the requested SIB.
[0139] With reference to Figure 13, in step S1301, when an F1 interface is configured, CU can transmit to DU, a message including information related to all SIBs provided by CU. Alternatively, CU may transmit a message to DU including information related to some SIBs provided by CU. For example, information related to some SIBs can be minimal system information or system information in a SIB that is frequently requested by a UE. Information related to some SIBs can be transmitted to efficiently manage DU resources to store information related to a SIB. The message can be an F1 configuration response message or an F1 configuration request message. For example, CU can transmit a message to DU including information related to SIBx.
Petition 870190072500, of 7/29/2019, p. 55/101
38/57 [0140] The SIB-related information included in the message can be provided by SIB. SIB-related information can include at least one of a SIB ID, a container that includes system information, broadcast time information, logical channel related information, broadcast activation, a DU ID, a cell ID and a beam ID.
[0141] Information related to the SIB may include system information and information necessary for the DU to disseminate the system information. The container can be used to transmit system information including one or more parameters that will be broadcast from CU to DU. Diffusion time information can be information or time to help program the DU to diffuse system information. For example, broadcast time information can include at least one of the duration of a window in which system information is broadcast, the number of times system information is broadcast, or the location of system information broadcast within from the window. For each parameter in the SIB, there may be information about diffusion time per parameter, which may have a different value. Logical channel information can include logical channel information indicating a logical channel through which system information is transmitted. For example, the logical channel information can be a logical channel ID. Broadcast activation can indicate whether the system information provided is broadcast. Broadcast activation can be adjusted when system information is always broadcast or is frequently requested by a UE. When the DU controls, manages, or spans one or more cells, the F1 configuration response message or the F1 configuration request message can include a cell ID for each cell. When the DU controls, manages, or spans one or more beams, the F1 configuration response message or the F1 configuration request message can include a beam ID for each
Petition 870190072500, of 7/29/2019, p. 56/101
39/57 beam.
[0142] In step S1302, after an F1 configuration procedure is completed, the DU can broadcast the system information related to the SIB whose broadcast is activated.
[0143] In step S1303, a UE can transmit a system information request to the DU to request system information on demand. The request for system information may be included in message 1 in a random access procedure. To request system information, a preamble transmitted by the UE can be mapped to all SIBs. Alternatively, the preamble transmitted by the UE can be mapped to one or more SIBs. Such mappings can be broadcast by the DU or they can be pre-configured between the DU and the UE. In addition, the UE can transmit a plurality of preambles, each of which is mapped to a SIB, to the DU. The UE may be in the RRCJDLE state. The UE may be in the RRCJNACTIVE state.
[0144] In step S1304, upon receipt of the message from the UE, the DU can identify whether the DU can broadcast the system information related to a SIB in which the system information on demand is requested. When the DU can broadcast the system information related to the SIB where the system information on demand is requested, the DU can ignore the signaling with the CU. For example, if possible, steps S1305a, S1305b and S1305c can be omitted. When the DU is unable to broadcast the system information related to the SIB where the system information on demand is requested, the DU can perform the signaling with the CU.
[0145] In step S1305a, the DU can transmit a message including information in the SIB requested from CU. Information in the requested SIB can indicate the requested SIB. The information in the requested SIB can be an identity, an index, or a SIB number identified based on the information request from the
Petition 870190072500, of 7/29/2019, p. 57/101
40/57 system. The message can be a message indicating system information on demand or a new message.
[0146] In step S1305b, upon receiving the message from the DU, CU can identify the requested system information on demand. CU can transmit a message to DU, providing information related to the requested SIB. For example, CU may transmit a message to DU including information related to SIBy. The message can be a system information broadcast request message or a new message. The SIB-related information included in the message can be provided by SIB. SIB-related information can include at least one of a SIB ID, a container that includes system information, broadcast time information, logical channel related information, broadcast activation, a DU ID, a cell ID and a beam ID. Upon receipt of the message from the CU, the DU can store the information related to the requested SIB.
[0147] In step S1305c, the DU can transmit a system information broadcast reply message or a new message to CU. For the requested SIB, the response message can include at least one of a SIB ID, a DU ID, a cell ID and a beam ID corresponding to an ID included in the message received in step S1305b. For the SIB, when the ID included in the request message is not included in the response message, CU can recognize that an entity (for example, DU, cell and / or beam) indicated by CU cannot broadcast system information.
[0148] In step S1306, the DU can transmit message 2 to the UE.
[0149] In step S1307, after the transmission of message 2, the DU can broadcast system information related to the requested SIB. For the SIB, when the DU stores a cell ID or a beam ID, the DU can broadcast SIB-related system information in a beam or cell indicated by the ID.
Petition 870190072500, of 7/29/2019, p. 58/101
41/57 [0150] In step S1308, when CU determines to update the information related to the SIB, CU can transmit a system information broadcast request message or a new message to DU. The system information broadcast request message or the new message can include information related to SIB by SIB. For example, CU may transmit a message to DU including information related to updated SIBz. For example, CU may transmit a message to DU including information related to SIBz that will be updated. SIB-related information can include at least one of a SIB ID, a container that includes system information, broadcast time information, logical channel related information, and broadcast activation. Enabling broadcast may indicate that system information related to SIBz is not broadcast.
[0151] In step S1309, upon receipt of the message from the CU, the DU can replace the information previously provided to the SIB with the information received related to the SIB. The DU can then transmit a system information broadcast reply message or a new message including a SIB ID related to the updated SIB to CU.
[0152] In step S1310, referring to the requested SIB, when there is no request for system information on demand during a specific period of time, the DU can determine whether to release the information related to the requested SIB to efficiently manage the DU's resources from to store information related to the requested SIB.
[0153] In step S1311, when determining the release of information related to the requested SIB, the DU can transmit a message indicating the release of system information or a new message to the DU to indicate that the DU no longer has the information related to the SIB. The message can include a released SIB identity, index, or number. For example,
Petition 870190072500, of 7/29/2019, p. 59/101
42/57 message may include the type of the released SIB. After transmission of the message, the
DU can release information related to the indicated SIB.
[0154] In accordance with the modality of the present invention, CU can provide DU with system information and information necessary for the dissemination of system information. The information can basically be provided when the dissemination of the system information is supported. Alternatively, information can be provided upon request from a UE. CU can provide SIB-related information prior to DU, thereby reducing signaling between CU and DU caused by a request for system information from the UE. In addition, it is possible to efficiently manage DU resources to store information related to a requested SIB.
[0155] Figure 14 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[0156] In accordance with the modality of the present invention, when a CU receives a request for grouped system information broadcast from a UE through a DU or determines to broadcast one or more grouped system information, the CU may transmit to the DU, one or more grouped system information (for example, MIB, SIB1 and SIB2 in LTE) that will be broadcast using a message for each of the grouped system information.
[0157] In step S1401, a UE can transmit a system information request to the DU to request system information on demand. The request for system information may be included in message 1 in a random access procedure. To request system information, a preamble transmitted by the UE can be mapped to all groups of information in the system. Alternatively, the preamble transmitted by the UE can be mapped to one or more groups of information in the system. Such mappings can be broadcast by DU or they can be pre-configured between the
Petition 870190072500, of 7/29/2019, p. 60/101
43/57
DU and the UE. In addition, the UE can transmit a plurality of preambles, each of which is mapped to a group of system information, to the DU. The UE may be in the RRCJDLE state. The UE may be in the RRCJNACTIVE state.
[0158] In step S1402, upon receipt of the message from the UE, the DU can transmit a message including a group of system information requested from the CU based on message 1 received from the UE. The message can be a message indicating system information on demand or a new message.
[0159] In step S1403, when CU receives a system information on demand message or a new message including system information x or determines to broadcast the system information group x, CU can transmit a message requesting dissemination of the system's information group to DU. The message can be a broadcast request message Six or a new message, x can refer to group x. For example, when it is necessary for the system information group 2 and the system information group 3 to be broadcast, CU can use a SI2 broadcast request message and a SI3 broadcast request message. The broadcast request message or the new message can include at least one group of system x information, broadcast time information, logical channel related information, a DU ID, a cell ID, a beam ID, and information related to system information on demand.
[0160] The broadcast request message Six or the new message may include a group of information from system x and information necessary for the DU to disseminate the group of information from system x. The system information group x can include one or more parameters that will be broadcast. The broadcast time information can be information or time to help program the DU to broadcast the system information group x. For each parameter in the
Petition 870190072500, of 7/29/2019, p. 61/101
44/57 system information group x, there may be information on diffusion time per parameter, which may have a different value. Logical channel information may include logical channel information indicating a logical channel through which the system information group x is transmitted. For example, the logical channel information can be a logical channel ID. When the DU controls, manages, or spans one or more cells, the broadcast request message Six or the new message can include a cell ID for each cell. When the DU controls, manages, or encompasses one or more beams, the broadcast broadcast message Six or the new message may include a beam ID for each beam. Information related to system information on demand may include at least one of the duration of a window in which system information is broadcast, the number of times system information is broadcast, or the location of system information broadcast within from the window.
[0161] In step S1404, upon receipt of the request message from the CU, the DU can transmit the broadcast reply message or a new message to the CU. The response message can include at least one of a DU ID, a cell ID and a beam ID corresponding to an ID included in the request message received in step S1403. When the ID included in the request message is not included in the response message, CU can recognize that an entity (for example, DU, cell and / or beam) indicated by CU cannot broadcast the system information group x.
[0162] In step S1405, upon receipt of the request message from the CU, the DU can store the information included in the request message. The DU can then broadcast the system information group x based on the stored information. When the broadcast request message or new message includes a cell ID or a beam ID, the DU can broadcast the system information group x in a beam or cell indicated by the ID. When
Petition 870190072500, of 7/29/2019, p. 62/101
45/57 the broadcast request message Six or the new message includes information related to system information on demand, DU may have the information related to system information on demand or all the information included in the request message while broadcasting the information of the system. Subsequently, DU can remove or discard information related to system information on demand or all information.
[0163] In step S1406, the DU can broadcast the system information group x included in the request message from the CU.
[0164] In accordance with the modality of the present invention, CU can manage system information that will be broadcast to a UE in CU coverage. Alternatively, CU can provide system information at the request of the UE.
[0165] Figure 15 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[0166] In accordance with the modality of the present invention, when a CU receives a request for grouped system information broadcast from a UE through a DU or determines to broadcast one or more grouped system information, the CU may transmit to the DU, one or more grouped system information (for example, MIB, SIB1 and SIB2 in LTE) that will be broadcast using a single message including all grouped system information.
[0167] In step S1501, a UE can transmit a system information request to the DU to request system information on demand. The request for system information may be included in message 1 in a random access procedure. To request system information, a preamble transmitted by the UE can be mapped to all groups of information in the system. Alternatively, the preamble transmitted by the UE can be mapped to one or more groups of information in the system. Such
Petition 870190072500, of 7/29/2019, p. 63/101
46/57 mappings can be broadcast by DU or they can be pre-configured between the
DU and the UE. In addition, the UE can transmit a plurality of preambles, each of which is mapped to a group of system information, to the DU. The UE may be in the RRCJDLE state. The UE may be in the RRCJNACTIVE state.
[0168] In step S1502, upon receipt of the message from the UE, the DU can transmit a message including a group of system information requested from the CU based on message 1 received from the UE. The message can be a message indicating system information on demand or a new message.
[0169] In step S1503, when CU receives an on-demand system information message or a new message including a system information group or determines to broadcast one or more groups of system information, CU can transmit a message requesting the dissemination of one or more groups of information from the system to the DU. The message can be a system information broadcast request message or a new message. The message can include information by system information group.
[0170] For example, the message may include information in a first group of system information and information in a second group of system information. The information in the first system information group can include at least one system information group 1, broadcast time information, logical channel related information, a DU ID, a cell ID, a beam ID, and information related to system information on demand. Information in the system information group can include at least one system information group 2, broadcast time information, logical channel related information, a DU ID, a cell ID, a beam ID, and related information system information under
Petition 870190072500, of 7/29/2019, p. 64/101
47/57 demand.
[0171] The information in each system information group may include a system information group and information necessary for the DU to disseminate the system information group. The system information group can include one or more parameters that will be broadcast. The broadcast time information can be information or time to help program the DU to broadcast the system information group. For each parameter in the system information group, there may be information on diffusion time per parameter, which may have a different value. Logical channel related information can include logical channel information indicating a logical channel through which the system information group is transmitted. For example, the logical channel information can be a logical channel ID. When the DU controls, manages, or encompasses one or more cells, the system information broadcast request message or the new message can include a cell ID for each cell. When the DU controls, manages, or encompasses one or more beams, the system information broadcast request message or the new message may include a beam ID for each beam. Information related to system information on demand may include at least one of the duration of a window in which system information is broadcast, the number of times system information is broadcast, or the location of system information broadcast within from the window.
[0172] In step S1504, upon receipt of the request message from the CU, the DU can transmit a system information broadcast reply message or a new message to the CU. For each group of system information, the response message can include at least one of a DU ID, a cell ID and a beam ID corresponding to an ID included in the request message received in step S1503. For example, for the
Petition 870190072500, of 7/29/2019, p. 65/101
48/57 first group when the ID included in the request message is not included in the response message, CU can recognize that an entity (eg DU, cell and / or beam) indicated by CU cannot broadcast the first group system information.
[0173] In step S1505, upon receipt of the request message from the CU, the DU can store the information included in the first group of system information and / or in the second group of system information. The DU can then broadcast the system information group 1 and / or the system information group 2 based on the stored information. For example, for the first system information group, when the system information broadcast request message or the new message includes a cell ID or beam ID, the DU can broadcast system information group 1 across a beam or cell indicated by the ID. In addition, when the system information broadcast request message or the new message includes information related to system information on demand in the first group of system information, DU may have all the information in the first group of system information included in the request message or information related to system information on demand while broadcasting system information to the first group of system information. Subsequently, DU can remove or discard all information in the first group of system information or information related to system information on demand.
[0174] In step S1506, the DU may broadcast the system information group 1 and / or the system information group 2 respectively included in the information in the first system information group and / or in the information in the second system information group. system.
[0175] In accordance with the modality of the present invention, CU can manage system information that will be disseminated to a UE in coverage of
Petition 870190072500, of 7/29/2019, p. 66/101
49/57
ASS. Alternatively, CU can provide DU system information at the request of the UE. In addition, CU can provide a plurality of system information at the same time in a single procedure, thereby reducing signaling between CU and DU.
[0176] Figure 16 illustrates a procedure for providing system information on demand according to an embodiment of the present invention.
[0177] According to the modality of the present invention, a CU can provide a DU with grouped system information that will be broadcast, which is provided by CU, using an F1 configuration procedure. For example, the grouped system information can be a MIB, SIB1 or SIB2 in LTE. In addition, when CU receives, from the DU, a request for grouped system information corresponding to system information on demand from a UE or determines to update the grouped system information, CU can transmit the grouped system information requested or updated to DU.
[0178] With reference to Figure 16, in step S1601, when an F1 interface is configured, CU can transmit to DU, a message including all groups of system information provided by CU. Alternatively, CU can transmit a message to the DU including some groups of system information provided by CU. For example, some groups of system information can be a group of minimal system information or a group of system information frequently requested by a UE. Some groups of system information can be transmitted to efficiently manage DU resources to store information related to a group of system information. The message can be an F1 configuration response message or an F1 configuration request message. For example, CU can transmit a message to the DU including information related to the system information group x.
Petition 870190072500, of 7/29/2019, p. 67/101
50/57 [0179] Information related to the system information group included in the message can be provided by system information group. Information related to the system information group can include at least one of the system information group, broadcast time information, logical channel information, a DU ID, a cell ID and a beam ID.
[0180] Information related to the system information group may include the system information group and information necessary for the DU to disseminate the system information group. The system information group can include one or more parameters that will be broadcast. The broadcast time information can be information or time to help program the DU to broadcast the system information group. For example, broadcast time information can include at least one of the duration of a window in which system information is broadcast, the number of times system information is broadcast, or the location of system information broadcast within from the window. For each parameter in the system information group, there may be information on diffusion time per parameter, which may have a different value. Logical channel related information can include logical channel information indicating a logical channel through which the system information group is transmitted. For example, the logical channel information can be a logical channel ID. When the DU controls, manages, or spans one or more cells, the F1 configuration response message or the F1 configuration request message can include a cell ID for each cell. When the DU controls, manages, or encompasses one or more beams, the F1 configuration response message or the F1 configuration request message can include a beam ID for each beam.
[0181] After an F1 configuration procedure is completed, the DU can
Petition 870190072500, of 7/29/2019, p. 68/101
51/57 disseminate system information based on information received from the
ASS.
[0182] In step S1602, a UE can transmit a system information request to the DU to request system information on demand. The request for system information can be included in message 1 or message 3 in a random access procedure. To request system information, a preamble transmitted by the UE can be mapped to all groups of information in the system. Alternatively, the preamble transmitted by the UE can be mapped to one or more groups of information in the system. Such mappings can be broadcast by the DU or they can be pre-configured between the DU and the UE. In addition, the UE can transmit a plurality of preambles, each of which is mapped to a group of system information, to the DU. The UE may be in the RRCJDLE state. The UE may be in the RRCJNACTIVE state.
[0183] In step S1603, upon receipt of the message from the UE, the DU can identify whether the DU can broadcast the system information on demand received. When the DU can broadcast the system information on demand received, the DU can broadcast system information corresponding to the requested system information on demand.
[0184] In step S1604, when the DU has some groups of system information provided by CU and cannot disseminate the system information corresponding to the system information on demand received from the UE, the DU can transmit to CU a message including a group of system information requested via message 1 or message 3. The message can be an indication message on demand for system information or a new message. The system information group requested can be associated with the system information on demand.
[0185] In step S1605, when the CU receives the message indicating
Petition 870190072500, of 7/29/2019, p. 69/101
52/57 system information on demand or the new message or determine to update the system information group, CU may transmit to DU a message providing the requested or updated system information group. For example, CU can transmit a message to DU, including information related to a group of system information requested or updated. The message can be a system information broadcast request message or a new message. Information related to the system information group included in the message can be provided by system information group. Information related to the system information group can include at least one of the system information group, broadcast time information, logical channel information, a DU ID, a cell ID and a beam ID.
[0186] In step S1606, upon receipt of the message from the CU, the DU can transmit a system information broadcast reply message or a new message to the CU. For the requested or updated system information group, the response message can include at least one of a DU ID, a cell ID and a beam ID corresponding to an ID included in the message received in step S1605. For the system information group y, when the ID included in the request message is not included in the response message, CU can recognize that an entity (for example, DU, cell and / or beam) indicated by CU cannot broadcast the system information group x.
[0187] In step S1607, upon receipt of the message from the CU, the DU can store the information included in the system information group y. Alternatively, the DU can replace the previous information with the information included in the system information group y. The DU can then broadcast the system's information group based on the information stored
Petition 870190072500, of 7/29/2019, p. 70/101
53/57 or replaced. For the system information group, when the system information broadcast request message or the new message includes a cell ID or a beam ID, the DU can broadcast the system information group y across a beam or cell indicated by the ID.
[0188] In step S1608, referring to the system information group, when there is no request for system information on demand during a specific period of time, DU can release all information related to the system information group to efficiently manage the DU resources in order to store information related to the system's information group.
[0189] In accordance with the modality of the present invention, CU can provide DU with system information that will be broadcast to a UE in CU coverage. Alternatively, CU can provide DU system information at the request of the UE. In addition, CU can previously provide DU with information related to a group of system information, thereby reducing the signaling between CU and DU caused by a request for system information on demand from the UE.
[0190] Figure 17 is a block diagram illustrating a method for a DU of a BS to provide system information according to an embodiment of the present invention.
[0191] With reference to Figure 17, in step S1710, the DU of the BS can receive system information pertaining to a CU of the BS from the CU of the BS. System information pertaining to the BS CU can be included in a container and can be transmitted from the BS CU to the BS DU. System information pertaining to the BS CU can be transmitted from the BS CU to the BS DU in an F1 configuration procedure. System information received from the BS CU can be all system information
Petition 870190072500, of 7/29/2019, p. 71/101
54/57 excluding SIB1 from the system information pertaining to BS BS.
[0192] CU can be a logical node that hosts radio resource control (RRC), service data adaptation protocol (SDAP), and BS packet data convergence protocol (PDCP) layers, and DU can be a logical node that hosts radio link control (RLC), media access control (MAC), and physical layers (PHY) from BS.
[0193] System information can be system-on-demand information disseminated at the request of a UE. The system information can be other system information.
[0194] In step S1720, the DU of BS can receive a request for system information from the UE. The system information request can be transmitted from the UE to the BS DU in a random access procedure. Requesting system information may be included in message 3.
[0195] System information received from the BS CU may include the requested system information.
[0196] In addition, when the system information received from the BS CU does not include the requested system information, the BS DU can receive the system information requested from the BS CU.
[0197] In addition, the BS DU can transmit the request for system information to the BS CU. The request for system information can be included in a container and can be transmitted from the DU of BS to CU of BS.
[0198] In step S1730, the DU of the BS can receive a message from a command to broadcast the system information from the CU of the BS. The command message to broadcast the requested system information can include the type of system information requested. The command message for
Petition 870190072500, of 7/29/2019, p. 72/101
55/57 disseminating requested system information may include information on timing to disseminate requested system information. Time information can be a widespread time interval.
[0199] In step S1740, the DU of the BS can broadcast the requested system information. Alternatively, the DU of BS can transmit the requested system information to the UE through dedicated signaling.
[0200] Figure 18 is a block diagram illustrating a wireless communication system according to the modality of the present invention.
[0201] An UE 1800 includes a processor 1801, a memory 1802 and a transceiver 1803. Memory 1802 is connected to processor 1801, and stores information for transmission to processor 1801. Transceiver 1803 is connected to processor 1801, and transmits and / or receives radio signals. The 1801 processor implements the proposed functions, processes and / or methods. In the above modality, an operation of the user equipment can be implemented by the 1801 processor.
[0202] An 1810 base station DU includes an 1811 processor, an 1812 memory and an 1813 transceiver. The 1812 memory is connected to the 1811 processor, and stores information for transmission to the 1811 processor. The 1813 transceiver is connected to the 1811 processor , and transmits and / or receives radio signals. The 1811 processor implements the proposed functions, processes and / or methods. In the above modality, a DU operation can be implemented by the 1811 processor.
[0203] An 1820 base station CU includes an 1812 processor, an 1822 memory and an 1823 transceiver. The 1822 memory is connected to the 1821 processor, and stores information for transmission to the 1821 processor. The 1823 transceiver is connected to the 1821 processor , and transmits and / or receives radio signals. The 1821 processor implements functions, processes and / or methods
Petition 870190072500, of 7/29/2019, p. 73/101
56/57 proposed. In the above modality, a CU operation can be implemented by the 1821 processor.
[0204] The processor may include an application-specific integrated circuit (ASIC), a separate chipset, a logic circuit and / or a data processing unit. The memory may include a read memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other equivalent storage devices. The transceiver may include a baseband circuit to process a wireless signal. When the modality is implemented in software, the previously mentioned methods can be implemented with a module (ie, process, function, etc.) to carry out the aforementioned functions. The module can be stored in memory and can be realized by the processor. The memory can be located inside or outside the processor, and can be coupled to the processor using several well-known means.
[0205] Various methods based on this specification have been described with reference to the drawings and reference numbers provided in the drawings based on the above examples. Although each method describes multiple steps or blocks in a specific order for convenience of explanation, the invention disclosed in the claims is not limited to the order of the steps or blocks, and each step or block can be implemented in a different order, or it can be carried out simultaneously with other steps or blocks. In addition, those skilled in the art may know that the invention is not limited to each of the steps or blocks, and at least one different step can be added or removed without departing from the scope and spirit of the invention.
[0206] The previously mentioned modality includes several examples. It should be noted that those skilled in the art know that all possible combinations of examples cannot be explained, and they also know that several
Petition 870190072500, of 7/29/2019, p. 74/101
57/57 combinations can be derived from the technique of this specification.
Therefore, the scope of protection of the invention must be determined by combining several examples described in the detailed explanation, without departing from the scope of the following claims.

权利要求:
Claims (15)
[1]
1. Method of diffusion, by a distributed unit (DU) of a base station (BS), of information from the system to a wireless communication system, FEATURED by the fact that it comprises:
receiving a plurality of system information from a BS central unit (CU);
receiving, from a user device (UE), a first message containing a request for system information;
receive, from CU of BS, a second message indicating at least one system information from the plurality of system system information based on the request; and disseminate to the UE at least one system information.
[2]
2. Method, according to claim 1, CHARACTERIZED by the fact that the second message that indicates at least one system information among the plurality of system information comprises:
an indication of at least one system information from an enumerated list.
[3]
3. Method, according to claim 1, CHARACTERIZED by the fact that the receipt, from CU of BS, of the second message comprises:
receive the second message in an F1 configuration procedure.
[4]
4. Method according to claim 1, CHARACTERIZED by the fact that the at least one system information is a portion of the plurality of system information.
[5]
5. Method, according to claim 1, CHARACTERIZED by the fact that it comprises, in a state where at least one system information is not a portion of the plurality of system information:
receive at least one system information from the BS CU.
Petition 870190072500, of 7/29/2019, p. 99/101
2/3
[6]
6. Method, according to claim 1, CHARACTERIZED by the fact that at least one information from the system excludes SIB1 from the plurality of information from the system.
[7]
7. Method, according to claim 1, CHARACTERIZED by the fact that it additionally comprises:
transmitting a third message, from DU to CU, which comprises requesting system information, and where receiving the second message comprises receiving the second message from CU in response to the third message.
[8]
8. Method, according to claim 1, CHARACTERIZED by the fact that the receipt, from the UE, of the first message containing the request for system information comprises:
receive the first message from the UE in a random access procedure.
[9]
9. Method, according to claim 8, CHARACTERIZED by the fact that the receipt, from the UE, of the first message containing the request for system information comprises:
receive the first message from the UE in a Message 3.
[10]
10. Method, according to claim 1, CHARACTERIZED by the fact that the second message comprises information about time to spread the requested system information.
[11]
11. Method, according to claim 1, CHARACTERIZED by the fact that the at least one system information comprises system information that belongs to CU.
[12]
12. Method, according to claim 11, CHARACTERIZED by the fact that the receipt, from the UE, of the first message containing the request comprises:
Petition 870190072500, of 7/29/2019, p. 100/101
3/3 receive the first message that encapsulates the request.
[13]
13. Method, according to claim 1, CHARACTERIZED by the fact that CU is a logical node that hosts the layers of radio resource control (RRC), service data adaptation protocol (SDAP), and BS packet data convergence (PDCP), where DU is a logical node that hosts radio link control (RLC), media access control (MAC), and BS physical layers (PHY).
[14]
14. Method, according to claim 1, CHARACTERIZED by the fact that at least one system information comprises system information on demand that is configured to be disseminated at the request of the UE.
[15]
15. Distributed unit (DU) of a base station (BS) configured to broadcast information from the system in a wireless communication system, FEATURED by the fact that the DU comprises:
a transceiver;
at least one processor; and at least one computer memory operationally connectable to at least one processor and storage instructions that, when executed, cause at least one processor to perform operations that comprise:
receiving a plurality of system information from a BS central unit (CU);
receiving, from a user device (UE), a first message containing a request for system information;
receive, from CU of BS, a second message indicating at least one system information from the plurality of system system information based on the request; and disseminate to the UE at least one system information.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019015576A2|2020-03-10|METHOD AND APPARATUS TO PROVIDE SYSTEM INFORMATION

---

RU2731497C1|2020-09-03|Method and device for requesting system information

---

KR101789327B1|2017-10-24|Method and apparatus of uplink transmission in wireless communication system

---

JP2016535506A|2016-11-10|Method and apparatus for transmitting a paging message in a wireless communication system

---

EP3454620A1|2019-03-13|Method and apparatus for receiving osi block in wireless communication system

---

US20210092778A1|2021-03-25|Method and apparatus for requesting system information

---

AU2018251514B2|2020-02-06|Method and apparatus for providing system information

---

BR112019007229B1|2021-11-23|METHOD AND DEVICE TO REQUEST SYSTEM INFORMATION

同族专利:

---

公开号 | 公开日

---

EP3471463B1|2021-01-13|

---

CA3036482C|2020-08-25|

---

PH12019500359A1|2019-10-28|

---

JP2019523601A|2019-08-22|

---

KR20180115626A|2018-10-23|

---

CA3036482A1|2018-10-18|

---

MX2019008617A|2019-09-09|

---

JP6661830B2|2020-03-11|

---

SG11201900188UA|2019-02-27|

---

CL2019000888A1|2019-06-28|

---

EP3471463A4|2020-03-04|

---

CN110463275A|2019-11-15|

---

KR102164229B1|2020-10-12|

---

KR101952345B1|2019-02-26|

---

US20200120579A1|2020-04-16|

---

US20180338277A1|2018-11-22|

---

CN110463275B|2021-10-08|

---

US10512030B2|2019-12-17|

---

KR20190020004A|2019-02-27|

---

EP3471463A1|2019-04-17|

---

RU2727722C1|2020-07-23|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

GB2378092B|2001-07-27|2003-11-05|Motorola Inc|Delivery of broadcast information to a mobile station in a radio communication system|

---

US7529215B2|2003-11-17|2009-05-05|Telefonaktiebolaget Lm Ericsson |Encapsulation of independent transmissions over internal interface of distributed radio base station|

---

TWI388145B|2006-09-20|2013-03-01|Interdigital Tech Corp|Method for enhanced dedicated channel transmission overlap detection for compressed mode gap slots|

---

WO2008054158A2|2006-11-01|2008-05-08|Lg Electronics Inc.|Methods of transmitting and receiving downlink data in wireless communication system|

---

BRPI0721568A8|2007-05-04|2019-01-15|Ericsson Telefon Ab L M|power supply station, and remote power system to provide electric power|

---

KR101758272B1|2010-02-09|2017-07-17|엘지전자 주식회사|Method and apparatus of transmitting and receiving system information in a wireless system|

---

US10200920B2|2015-02-10|2019-02-05|Qualcomm Incorporated|On-demand system information|

---

KR102106134B1|2015-05-15|2020-05-04|주식회사 케이티|Methods for configuring wireless connection of user equipment and Apparatuses thereof|

---

KR101956978B1|2015-05-18|2019-03-12|주식회사 케이티|Methods for tranmitting ant receiving system information and apparatuses thereof|

---

WO2017034230A1|2015-08-21|2017-03-02|삼성전자 주식회사|Communication method and device of terminal in wireless communication system|

---

US11026142B2|2016-01-20|2021-06-01|Qualcomm Incorporated|Techniques for providing uplink-based mobility|

---

JPWO2017130800A1|2016-01-26|2018-11-15|株式会社Ｎｔｔドコモ|Base station and transmission method|

---

US10251208B2|2016-08-11|2019-04-02|Futurewei Technologies, Inc.|System and method for connection management|

---

US20180206178A1|2017-01-13|2018-07-19|Futurewei Technologies, Inc.|System and Method for Communicating System Information|KR102153077B1|2016-04-20|2020-09-07|콘비다 와이어리스, 엘엘씨|Downlink synchronization|

---

KR20180135479A|2016-04-20|2018-12-20|콘비다 와이어리스, 엘엘씨|Physical Channels in New Radio|

---

EP3446432A1|2016-04-20|2019-02-27|Convida Wireless, LLC|Configurable reference signals|

---

WO2017184842A1|2016-04-20|2017-10-26|Convida Wireless, Llc|System information provisioning and light weight connection signaling|

---

JP6935426B2|2016-05-11|2021-09-15|コンヴィーダ ワイヤレス， エルエルシー|New wireless downlink control channel|

---

CN109565370B|2016-06-15|2021-06-15|康维达无线有限责任公司|Apparatus for uploading control signaling for new radio|

---

EP3472960A1|2016-06-15|2019-04-24|Convida Wireless, LLC|Grant-less uplink transmission for new radio|

---

EP3473049A1|2016-06-15|2019-04-24|Convida Wireless, LLC|Grant-less operations|

---

EP3497812A1|2016-08-11|2019-06-19|Convida Wireless, LLC|Beamforming sweeping and training in a flexible frame structure for new radio|

---

EP3520243A2|2016-11-03|2019-08-07|Convida Wireless, LLC|Frame structure in nr|

---

CN110856223B|2017-05-05|2020-10-27|华为技术有限公司|Communication method, centralized unit, distributed unit, base station and terminal equipment|

---

EP3941153A1|2017-05-05|2022-01-19|Samsung Electronics Co., Ltd.|Data transmission method and network equipment supporting pdcp duplication function|

---

CN107360557B|2017-06-15|2020-03-24|电信科学技术研究院|System message notification and sending method and device|

---

CN109151737A|2017-06-16|2019-01-04|华为技术有限公司|A kind of communication means and device|

---

CN109413742B|2017-08-18|2021-07-09|华为技术有限公司|Method and device for transmitting system information|

---

CN109412770B|2017-09-23|2019-09-20|华为技术有限公司|Communication means and device|

---

US11265946B2|2017-09-28|2022-03-01|Samsung Electronics Co., Ltd.|Method and device for network access|

---

EP3836729A1|2017-09-28|2021-06-16|Samsung Electronics Co., Ltd.|Method and device for network access|

---

CN109802849B|2017-11-17|2022-03-08|中兴通讯股份有限公司|Method and device for sending alarm information|

---

EP3522647A1|2018-02-02|2019-08-07|Comcast Cable Communications LLC|Wireless communications using traffic information|

---

KR20190116806A|2018-04-05|2019-10-15|삼성전자주식회사|Apparatus and method for beam failure recovery in wireless communication system|

---

US20190320322A1|2018-04-16|2019-10-17|Charter Communications Operating, Llc|Apparatus and methods for integrated high-capacity data and wireless network services|

---

WO2019241235A1|2018-06-11|2019-12-19|Ofinno, Llc|Base station network sharing configuration|

---

US11044597B2|2018-08-07|2021-06-22|Charter Communications Operating, Llc|Apparatus and methods for registration and operation in wireless networks|

---

EP3864917A1|2018-10-12|2021-08-18|Charter Communications Operating, LLC|Apparatus and methods for cell identification in wireless networks|

---

EP3694174B1|2019-02-07|2021-09-01|AO Kaspersky Lab|Systems and methods for protecting automated systems using a gateway|

---

US11140616B2|2019-04-03|2021-10-05|Apple Inc.|On demand system information block acquisition|

---

WO2021002859A1|2019-07-03|2021-01-07|Nokia Technologies Oy|Measurement reporting in wireless network|

---

WO2021028145A1|2019-08-14|2021-02-18|Nokia Solutions And Networks Oy|System information delivery enhancements|

---

WO2021117111A1|2019-12-09|2021-06-17|富士通株式会社|Base station, terminal device, and wireless communication system|

---

WO2021138805A1|2020-01-07|2021-07-15|Oppo广东移动通信有限公司|Method and apparatus for synchronously scheduling a service, and communication device|

法律状态:
2021-10-13| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762484897P| true| 2017-04-13|2017-04-13|

---

US62/484,897|2017-04-13|

---

US201762492327P| true| 2017-05-01|2017-05-01|

---

US62/492,327|2017-05-01|

---

US201762519889P| true| 2017-06-15|2017-06-15|

---

US62/519,889|2017-06-15|

---

US201762529442P| true| 2017-07-06|2017-07-06|

---

US62/529,442|2017-07-06|

---

KR1020180041939A|KR101952345B1|2017-04-13|2018-04-11|Method and apparatus for providing system information|

---

PCT/KR2018/004251|WO2018190636A1|2017-04-13|2018-04-11|Method and apparatus for providing system information|

---

KR10-2018-0041939|2018-04-11|

---