[go: up one dir, main page]

WO2018190636A1 - Procédé et appareil de fourniture d'informations de système - Google Patents

Procédé et appareil de fourniture d'informations de système Download PDF

Info

Publication number
WO2018190636A1
WO2018190636A1 PCT/KR2018/004251 KR2018004251W WO2018190636A1 WO 2018190636 A1 WO2018190636 A1 WO 2018190636A1 KR 2018004251 W KR2018004251 W KR 2018004251W WO 2018190636 A1 WO2018190636 A1 WO 2018190636A1
Authority
WO
WIPO (PCT)
Prior art keywords
system information
base station
message
information
broadcast
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2018/004251
Other languages
English (en)
Korean (ko)
Inventor
변대욱
쑤지안
김상원
김석중
이재욱
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to MX2019008617A priority Critical patent/MX2019008617A/es
Priority to SG11201900188UA priority patent/SG11201900188UA/en
Priority to BR112019015576-7A priority patent/BR112019015576A2/pt
Priority to CA3036482A priority patent/CA3036482C/fr
Priority to EP18784633.2A priority patent/EP3471463B1/fr
Priority to RU2019108844A priority patent/RU2727722C1/ru
Priority to MYPI2019000846A priority patent/MY197833A/en
Priority to AU2018251514A priority patent/AU2018251514B2/en
Priority to JP2019504736A priority patent/JP6661830B2/ja
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to CN201880021567.3A priority patent/CN110463275B/zh
Priority claimed from KR1020180041939A external-priority patent/KR101952345B1/ko
Priority to US16/048,848 priority patent/US10512030B2/en
Publication of WO2018190636A1 publication Critical patent/WO2018190636A1/fr
Priority to PH12019500359A priority patent/PH12019500359A1/en
Anticipated expiration legal-status Critical
Priority to US16/711,163 priority patent/US11375436B2/en
Priority to US17/725,247 priority patent/US11882515B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present invention relates to a wireless communication system, and more particularly, to a method for providing system information in a scenario in which a central unit and a distributed unit of a base station are divided, and an apparatus for supporting the same.
  • a 5G communication system or a pre-5G communication system is called a system after a 4G network (beyond 4G network) or after a long term evolution (LTE) system (post LTE).
  • System information refers to essential information for communication between the terminal and the base station.
  • system information is divided into MIB (Master Information Block) and SIB (System Information Block).
  • MIB is the most essential information
  • SIB is divided into SIB-x according to its importance or frequency.
  • the MIB is transmitted through a physical broadcast channel (PBCH), which is a physical channel, and the SIB is transmitted through a PDCCH as common control information.
  • PBCH physical broadcast channel
  • the generated information should be transmitted to the terminal through a distributed unit (DU).
  • DU distributed unit
  • the system information to be broadcast is also generated in the RRC layer of the central unit (CU)
  • signaling between the CU and the DU may be required for the DU to broadcast the system information.
  • a CU receives a system information request from a terminal through a DU
  • signaling between the CU and the DU may be necessary for the DU to broadcast the system information.
  • the CU-DU split scenario there is no procedure for the DU to transmit the system information requested by the terminal to the terminal. Therefore, in the CU-DU partitioning scenario, a method for providing system information and an apparatus supporting the same need to be proposed.
  • a method of distributing system information by a distributed unit (DU) of a base station in a wireless communication system includes receiving from the CU of the base station the system information owned by the CU of the base station held by a central unit (CU) of the base station; Receiving a request for the system information from a terminal; Receiving a message from the CU of the base station, the message commanding to broadcast the system information; And broadcasting the requested system information.
  • DU distributed unit
  • a distributed unit (DU) of a base station that broadcasts system information in a wireless communication system.
  • DU of the base station is a memory; Transceiver; And a processor that connects the memory and the transceiver, wherein the processor is configured to transmit the system information owned by the CU of the base station to which the transceiver is held by a central unit of the base station.
  • the transceiver To receive from the CU of the base station, and control the transceiver to receive a request for the system information from the terminal, and to receive a message from the CU of the base station that commands the transceiver to broadcast the requested system information. And control the transceiver to broadcast the requested system information.
  • FIG. 1 shows a structure of an LTE system.
  • FIG. 2 shows an air interface protocol of an LTE system for a control plane.
  • FIG 3 shows an air interface protocol of an LTE system for a user plane.
  • MIB master information block
  • SIB1 system information block
  • SIB system information blocks
  • FIG. 9 shows a scenario of separated base station deployment (Centralized Deployment).
  • FIG. 10 illustrates a functional split between a central unit and a distributed unit in a split base station deployment scenario.
  • FIG. 11 illustrates a procedure for providing system information according to an embodiment of the present invention.
  • FIG. 12 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • FIG. 13 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • FIG. 14 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • 15 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • 16 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • FIG. 17 is a block diagram illustrating a method in which a DU of a base station provides system information according to an embodiment of the present invention.
  • FIG. 18 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented with wireless technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA may be implemented by wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), and the like.
  • IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.
  • UTRA is part of a universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is part of evolved UMTS (E-UMTS) using evolved-UMTS terrestrial radio access (E-UTRA), which employs OFDMA in downlink and SC in uplink -FDMA is adopted.
  • LTE-A (advanced) is the evolution of 3GPP LTE.
  • 5G communication system is the evolution of LTE-A.
  • FIG. 1 shows a structure of an LTE system.
  • Communication networks are widely deployed to provide various communication services such as IMS and Voice over internet protocol (VoIP) over packet data.
  • VoIP Voice over internet protocol
  • an LTE system structure includes one or more UEs 10, an evolved-UMTS terrestrial radio access network (E-UTRAN), and an evolved packet core (EPC).
  • the terminal 10 is a communication device moved by a user.
  • the terminal 10 may be fixed or mobile and may be called by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), and a wireless device.
  • MS mobile station
  • UT user terminal
  • SS subscriber station
  • wireless device a wireless device.
  • the E-UTRAN may include one or more evolved node-eB (eNB) 20, and a plurality of terminals may exist in one cell.
  • the eNB 20 provides an end point of a control plane and a user plane to the terminal.
  • the eNB 20 generally refers to a fixed station communicating with the terminal 10, and may be referred to in other terms such as a base station (BS), a base transceiver system (BTS), an access point, and the like.
  • BS base station
  • BTS base transceiver system
  • One eNB 20 may be arranged per cell. There may be one or more cells within the coverage of the eNB 20.
  • One cell may be configured to have one of bandwidths such as 1.25, 2.5, 5, 10, and 20 MHz to provide downlink (DL) or uplink (UL) transmission service to various terminals. In this case, different cells may be configured to provide different bandwidths.
  • DL means communication from the eNB 20 to the terminal 10
  • UL means communication from the terminal 10 to the eNB 20.
  • the transmitter may be part of the eNB 20 and the receiver may be part of the terminal 10.
  • the transmitter may be part of the terminal 10 and the receiver may be part of the eNB 20.
  • the EPC may include a mobility management entity (MME) that serves as a control plane, and a system architecture evolution (SAE) gateway (S-GW) that serves as a user plane.
  • MME mobility management entity
  • SAE system architecture evolution gateway
  • S-GW gateway
  • the MME / S-GW 30 may be located at the end of the network and is connected to an external network.
  • the MME has information about the access information of the terminal or the capability of the terminal, and this information may be mainly used for mobility management of the terminal.
  • S-GW is a gateway having an E-UTRAN as an endpoint.
  • the MME / S-GW 30 provides the terminal 10 with the endpoint of the session and the mobility management function.
  • the EPC may further include a packet data network (PDN) -gateway (GW).
  • PDN-GW is a gateway with PDN as an endpoint.
  • the MME includes non-access stratum (NAS) signaling to the eNB 20, NAS signaling security, access stratum (AS) security control, inter CN (node network) signaling for mobility between 3GPP access networks, idle mode terminal reachability ( Control and execution of paging retransmission), tracking area list management (for terminals in idle mode and active mode), P-GW and S-GW selection, MME selection for handover with MME change, 2G or 3G 3GPP access Bearer management, including roaming, authentication, and dedicated bearer settings, SGSN (serving GPRS support node) for handover to the network, public warning system (ETWS) and commercial mobile alarm system (PWS) It provides various functions such as CMAS) and message transmission support.
  • NAS non-access stratum
  • AS access stratum
  • inter CN node network
  • MME selection for handover with MME change
  • 2G or 3G 3GPP access Bearer management including roaming, authentication, and dedicated bearer settings
  • SGSN serving GPRS support no
  • S-GW hosts can be based on per-user packet filtering (eg, through deep packet inspection), legal blocking, terminal IP (Internet protocol) address assignment, transport level packing marking in DL, UL / DL service level charging, gating and It provides various functions of class enforcement, DL class enforcement based on APN-AMBR.
  • MME / S-GW 30 is simply represented as a "gateway", which may include both MME and S-GW.
  • An interface for user traffic transmission or control traffic transmission may be used.
  • the terminal 10 and the eNB 20 may be connected by the Uu interface.
  • the eNBs 20 may be interconnected by an X2 interface. Neighboring eNBs 20 may have a mesh network structure by the X2 interface.
  • the eNBs 20 may be connected with the EPC by the S1 interface.
  • the eNBs 20 may be connected to the EPC by the S1-MME interface and may be connected to the S-GW by the S1-U interface.
  • the S1 interface supports a many-to-many-relation between eNB 20 and MME / S-GW 30.
  • the eNB 20 may select for the gateway 30, routing to the gateway 30 during radio resource control (RRC) activation, scheduling and transmission of paging messages, scheduling channel information (BCH), and the like.
  • RRC radio resource control
  • BCH scheduling channel information
  • the gateway 30 may perform paging initiation, LTE idle state management, user plane encryption, SAE bearer control, and encryption and integrity protection functions of NAS signaling in the EPC.
  • FIG. 2 shows an air interface protocol of an LTE system for a control plane.
  • 3 shows an air interface protocol of an LTE system for a user plane.
  • the layer of the air interface protocol between the UE and the E-UTRAN is based on the lower three layers of the open system interconnection (OSI) model, which is well known in communication systems, and includes L1 (first layer), L2 (second layer), and L3 (third layer). Hierarchical).
  • the air interface protocol between the UE and the E-UTRAN may be horizontally divided into a physical layer, a data link layer, and a network layer, and vertically a protocol stack for transmitting control signals.
  • Layers of the radio interface protocol may exist in pairs in the UE and the E-UTRAN, which may be responsible for data transmission of the Uu interface.
  • the physical layer belongs to L1.
  • the physical layer provides an information transmission service to a higher layer through a physical channel.
  • the physical layer is connected to a higher layer of a media access control (MAC) layer through a transport channel.
  • Physical channels are mapped to transport channels.
  • Data may be transmitted between the MAC layer and the physical layer through a transport channel.
  • Data between different physical layers, that is, between the physical layer of the transmitter and the physical layer of the receiver may be transmitted using radio resources through a physical channel.
  • the physical layer may be modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and utilizes time and frequency as radio resources.
  • OFDM orthogonal frequency division multiplexing
  • the physical layer uses several physical control channels.
  • a physical downlink control channel (PDCCH) reports resource allocation of a paging channel (PCH) and a downlink shared channel (DL-SCH), and hybrid automatic repeat request (HARQ) information related to the DL-SCH to the UE.
  • the PDCCH may carry an uplink grant to report to the UE regarding resource allocation of uplink transmission.
  • the physical control format indicator channel (PCFICH) informs the UE of the number of OFDM symbols used for the PDCCH and is transmitted every subframe.
  • a physical hybrid ARQ indicator channel (PHICH) carries a HARQ ACK (non-acknowledgement) / NACK (non-acknowledgement) signal for UL-SCH transmission.
  • a physical uplink control channel (PUCCH) carries UL control information such as HARQ ACK / NACK, a scheduling request, and a CQI for downlink transmission.
  • the physical uplink shared channel (PUSCH) carries an uplink shared channel (UL-SCH).
  • the physical channel includes a plurality of subframes in the time domain and a plurality of subcarriers in the frequency domain.
  • One subframe consists of a plurality of symbols in the time domain.
  • One subframe consists of a plurality of resource blocks (RBs).
  • One resource block is composed of a plurality of symbols and a plurality of subcarriers.
  • each subframe may use specific subcarriers of specific symbols of the corresponding subframe for the PDCCH.
  • the first symbol of the subframe may be used for the PDCCH.
  • the PDCCH may carry dynamically allocated resources, such as a physical resource block (PRB) and modulation and coding schemes (MCS).
  • a transmission time interval (TTI) which is a unit time at which data is transmitted, may be equal to the length of one subframe.
  • One subframe may have a length of 1 ms.
  • a DL transport channel for transmitting data from a network to a UE includes a broadcast channel (BCH) for transmitting system information, a paging channel (PCH) for transmitting a paging message, and a DL-SCH for transmitting user traffic or control signals. And the like.
  • BCH broadcast channel
  • PCH paging channel
  • DL-SCH supports dynamic link adaptation and dynamic / semi-static resource allocation by varying HARQ, modulation, coding and transmit power.
  • the DL-SCH may enable the use of broadcast and beamforming throughout the cell.
  • System information carries one or more system information blocks. All system information blocks can be transmitted in the same period. Traffic or control signals of a multimedia broadcast / multicast service (MBMS) are transmitted through a multicast channel (MCH).
  • MCH multicast channel
  • the UL transport channel for transmitting data from the terminal to the network includes a random access channel (RAC) for transmitting an initial control message, a UL-SCH for transmitting user traffic or a control signal, and the like.
  • the UL-SCH can support dynamic link adaptation due to HARQ and transmit power and potential changes in modulation and coding.
  • the UL-SCH may enable the use of beamforming.
  • RACH is generally used for initial connection to a cell.
  • the MAC layer belonging to L2 provides a service to a radio link control (RLC) layer, which is a higher layer, through a logical channel.
  • RLC radio link control
  • the MAC layer provides a mapping function from a plurality of logical channels to a plurality of transport channels.
  • the MAC layer also provides a logical channel multiplexing function by mapping from multiple logical channels to a single transport channel.
  • the MAC sublayer provides data transfer services on logical channels.
  • the logical channel may be divided into a control channel for information transmission in the control plane and a traffic channel for information transmission in the user plane according to the type of information to be transmitted. That is, a set of logical channel types is defined for other data transfer services provided by the MAC layer.
  • the logical channel is located above the transport channel and mapped to the transport channel.
  • the control channel is used only for conveying information in the control plane.
  • the control channel provided by the MAC layer includes a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a dedicated control channel (DCCH).
  • BCCH is a downlink channel for broadcasting system control information.
  • PCCH is a downlink channel used for transmitting paging information and paging a terminal whose cell-level location is not known to the network.
  • CCCH is used by the terminal when there is no RRC connection with the network.
  • MCCH is a one-to-many downlink channel used to transmit MBMS control information from the network to the terminal.
  • DCCH is a one-to-one bidirectional channel used by the terminal for transmitting dedicated control information between the terminal and the network in an RRC connection state.
  • the traffic channel is used only for conveying information in the user plane.
  • the traffic channel provided by the MAC layer includes a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH).
  • DTCH is used for transmission of user information of one UE in a one-to-one channel and may exist in both uplink and downlink.
  • MTCH is a one-to-many downlink channel for transmitting traffic data from the network to the terminal.
  • the uplink connection between the logical channel and the transport channel includes a DCCH that can be mapped to the UL-SCH, a DTCH that can be mapped to the UL-SCH, and a CCCH that can be mapped to the UL-SCH.
  • the downlink connection between the logical channel and the transport channel is a BCCH that can be mapped to a BCH or DL-SCH, a PCCH that can be mapped to a PCH, a DCCH that can be mapped to a DL-SCH, a DTCH that can be mapped to a DL-SCH, MCCH that can be mapped to MCH and MTCH that can be mapped to MCH.
  • the RLC layer belongs to L2.
  • the function of the RLC layer includes adjusting the size of the data by segmentation / concatenation of the data received from the upper layer in the radio section such that the lower layer is suitable for transmitting data.
  • the RLC layer is divided into three modes: transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM). Provides three modes of operation.
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledged mode
  • AM RLC provides retransmission through automatic repeat request (ARQ) for reliable data transmission.
  • ARQ automatic repeat request
  • the function of the RLC layer may be implemented as a functional block inside the MAC layer, in which case the RLC layer may not exist.
  • the packet data convergence protocol (PDCP) layer belongs to L2.
  • the PDCP layer introduces an IP packet, such as IPv4 or IPv6, over a relatively low bandwidth air interface to provide header compression that reduces unnecessary control information so that the transmitted data is transmitted efficiently. Header compression improves transmission efficiency in the wireless section by transmitting only the information necessary for the header of the data.
  • the PDCP layer provides security. Security functions include encryption to prevent third party inspection and integrity protection to prevent third party data manipulation.
  • the radio resource control (RRC) layer belongs to L3.
  • the RRC layer at the bottom of L3 is defined only in the control plane.
  • the RRC layer serves to control radio resources between the terminal and the network.
  • the UE and the network exchange RRC messages through the RRC layer.
  • the RRC layer is responsible for the control of logical channels, transport channels and physical channels in connection with the configuration, re-configuration and release of RBs.
  • RB is a logical path provided by L1 and L2 for data transmission between the terminal and the network. That is, RB means a service provided by L2 for data transmission between the UE and the E-UTRAN. Setting up an RB means defining the characteristics of the radio protocol layer and channel to provide a particular service, and determining each specific parameter and method of operation.
  • RBs may be classified into two types: signaling RBs (SRBs) and data RBs (DRBs).
  • SRBs signaling RBs
  • DRBs data RBs
  • the non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.
  • the RLC and MAC layers may perform functions such as scheduling, ARQ and HARQ.
  • the RRC layer (ended at the eNB at the network side) may perform functions such as broadcast, paging, RRC connection management, RB control, mobility function, and UE measurement report / control.
  • the NAS control protocol (terminated at the gateway's MME at the network side) may perform functions such as SAE bearer management, authentication, LTE_IDLE mobility handling, paging initiation at LTE_IDLE, and security control for signaling between the terminal and the gateway.
  • the RLC and MAC layer may perform the same function as the function in the control plane.
  • the PDCP layer may perform user plane functions such as header compression, integrity protection and encryption.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • S-GW serving gateway
  • P-GW packet data network gateway
  • 5G core network or NextGen core network
  • functions, reference points, protocols, etc. are defined for each network function (NF). That is, 5G core network does not define functions, reference points, protocols, etc. for each entity.
  • the 5G system structure includes one or more UEs 10, a Next Generation-Radio Access Network (NG-RAN), and a Next Generation Core (NGC).
  • NG-RAN Next Generation-Radio Access Network
  • NNC Next Generation Core
  • the NG-RAN may include one or more gNBs 40, and a plurality of terminals may exist in one cell.
  • the gNB 40 provides the terminal with the control plane and the end point of the user plane.
  • the gNB 40 generally refers to a fixed station communicating with the terminal 10 and may be referred to as other terms such as a base station (BS), a base transceiver system (BTS), an access point, and the like.
  • BS base station
  • BTS base transceiver system
  • One gNB 40 may be arranged per cell. There may be one or more cells within coverage of the gNB 40.
  • the NGC may include an Access and Mobility Function (AMF) and a Session Management Function (SMF) that are responsible for the functions of the control plane.
  • AMF Access and Mobility Function
  • SMF Session Management Function
  • the AMF may be responsible for the mobility management function
  • the SMF may be responsible for the session management function.
  • the NGC may include a user plane function (UPF) that is responsible for the function of the user plane.
  • UPF user plane function
  • Terminal 10 and gNB 40 may be connected by an NG3 interface.
  • the gNBs 40 may be interconnected by Xn interface.
  • Neighboring gNBs 40 may have a mesh network structure with an Xn interface.
  • the gNBs 40 may be connected to the NGC by the NG interface.
  • the gNBs 40 may be connected to the AMF by the NG-C interface and may be connected to the UPF by the NG-U interface.
  • the NG interface supports a many-to-many-relation between gNB 40 and MME / UPF 50.
  • the gNB host may determine functions for radio resource management, IP header compression and encryption of user data stream, and routing to AMF from information provided by the terminal. Selection of an AMF at UE attachment when no routing to an AMF can be determined from the information provided by the UE, Routing of User Plane data to one or more UPFs towards UPF (s)), Scheduling and transmission of paging messages (originated from the AMF), transmission and scheduling of system broadcast information (derived from AMF or O & M) Scheduling and transmission of system broadcast information (originated from the AMF or O & M), or setting up and measuring measurement reports for scheduling and mobility (Me It can perform functions such as asurement and measurement reporting configuration for mobility and scheduling.
  • Access and Mobility Function (AMF) hosts can be used for NAS signaling termination, NAS signaling security, AS Security control, and inter CN node signaling for mobility between 3GPP access networks.
  • node signaling for mobility between 3GPP access networks IDLE mode UE reachability (including control and execution of paging retransmission), UE in ACTIVE mode and IDLE mode Tracking Area list management (for UE in idle and active mode), AMF selection for handovers with AMF change, Access Authentication, Or perform key functions such as access authorization including check of roaming rights.
  • a user plane function (UPF) host is an anchor point for Intra- / Inter-RAT mobility (when applicable), an external PDU session point for the interconnection to the data network (if applicable).
  • (External PDU session point of interconnect to Data Network) Packet routing & forwarding, Packet inspection and User plane part of Policy rule enforcement, Traffic usage reporting ( Traffic usage reporting, Uplink classifier to support routing traffic flows to a data network, Branching point to support multi- homed PDU session, QoS handling for the user plane, e.g.
  • packet filtering gating, QoS handling for user plane, eg packet filtering, gating, UL / DL rate enforcement, uplink traffic verification (SDF to QoS flow mapping), transport level packet marking in downlink and uplink It can perform main functions such as packet marking in the uplink and downlink, or downlink packet buffering and downlink data notification triggering.
  • QoS handling for user plane eg packet filtering, gating, UL / DL rate enforcement, uplink traffic verification (SDF to QoS flow mapping), transport level packet marking in downlink and uplink
  • SDF to QoS flow mapping uplink traffic verification
  • transport level packet marking in downlink and uplink It can perform main functions such as packet marking in the uplink and downlink, or downlink packet buffering and downlink data notification triggering.
  • the Session Management Function (SMF) host is responsible for session management, UE IP address allocation and management, selection and control of UP functions, and traffic to the appropriate destinations.
  • Configure traffic steering at UPF to route traffic to proper destination, control part of policy enforcement and QoS, or downlink data notification Can perform key functions such as
  • MIB master information block
  • SIB1 system information block
  • SIB system information blocks
  • the LTE cell broadcasts the basic parameters necessary for the operation of the IDLE_MODE terminal and the CONNECTED_MODE terminal into a plurality of information blocks.
  • information blocks include MIBs, SIB1, SIB2, and other System Information Blocks (SIBn).
  • the MIB includes the most basic parameters necessary for the terminal to access the cell.
  • the MIB message is broadcasted through the BCH at a period of 40 ms, and the MIB transmission is repeated in all radio frames within the 40 ms period.
  • the terminal receives the SIB message using the parameter received from the MIB.
  • SIBs There are several types of SIBs.
  • SIB1 includes information related to cell access, and in particular, includes scheduling information of other SIBs SIB2 to SIBn except SIB1.
  • SIBs having the same transmission period among other SIs except SIB1 are included in the same system information (SI) message and transmitted. Therefore, the scheduling information includes a mapping relationship between each SIB and SI message.
  • the SI message is transmitted in a window of the time domain (SI-window), and each SI message is associated with one SI-window. Since SI-windows of different SIs do not overlap, only one SI message is transmitted in any SI-window. Therefore, the scheduling information includes the length of the SI-window and the SI transmission period.
  • the time / frequency at which the SI message is transmitted is determined by the dynamic scheduling of the base station.
  • SIB1 is broadcast on a downlink common channel (DL-SCH) in eight radio frame periods (ie, 80 ms periods), and SIB1 is repeatedly retransmitted on subframe 5 of a radio frame of SFN mod 2 within an 80 ms period.
  • DL-SCH downlink common channel
  • SIB2 includes information necessary for the terminal to access the cell. This includes information about uplink cell bandwidth, random access parameters, parameters related to uplink power control, and the like.
  • SIB3 includes cell reselection information.
  • SIB4 includes frequency information of a serving cell and intra frequency information of a neighbor cell related to cell reselection.
  • SIB5 includes information on another E-UTRA frequency and information on inter frequencies of neighboring cells related to cell reselection.
  • SIB6 includes information on UTRA frequency and information on UTRA neighbor cells related to cell reselection.
  • SIB7 includes information on GERAN frequencies related to cell reselection.
  • SIB8 includes information about a neighbor cell.
  • SIB9 includes an ID of a Home eNodeB (HeNB).
  • SIB10 to SIB12 include public warning messages, for example earthquake warnings.
  • SIB14 is used to support enhanced access barring and controls terminals accessing a cell.
  • SIB15 includes information required for MBMS reception of an adjacent carrier frequency.
  • SIB16 includes GPS time and Coordinated Universal Time (UTC) related information.
  • SIB17 includes RAN assistance information.
  • SIB9 is not needed in the mode in which the HeNB is constructed by the operator, and SIB13 is not necessary unless the MBMS is provided in the cell.
  • Random access is used for the terminal to obtain uplink synchronization with the base station or receive uplink radio resources.
  • the terminal acquires downlink synchronization with the initial cell and receives system information. From the system information, a set of available random access preambles and information about radio resources used for transmission of the random access preambles are obtained.
  • the radio resource used for transmission of the random access preamble may be specified as a combination of a radio frame and / or at least one or more subframes.
  • the terminal transmits a random access preamble randomly selected from the set of random access preambles, and the base station receiving the random access preamble sends a TA (timing alignment) value for uplink synchronization to the terminal through a random access response. As a result, the terminal acquires uplink synchronization.
  • TA timing alignment
  • the base station allocates a designated random access preamble to a specific terminal, and the terminal performs non-contention random access with the corresponding random access preamble. That is, in the process of selecting a random access preamble, a contention-based random access using a randomly selected one by a terminal within a specific set and a non-competitive random access using a random access preamble allocated by a base station only to a specific terminal There can be.
  • Non-competitive random access may be used when requested by a procedure for handover or a command of a base station.
  • the terminal randomly selects one random access preamble from a set of random access preambles indicated by system information or a handover command.
  • a radio resource capable of transmitting the random access preamble is selected to transmit the selected random access preamble.
  • the radio resource may be a specific subframe, which may be to select a physical random access channel (PRACH).
  • PRACH physical random access channel
  • the terminal After the random access preamble transmission, the terminal attempts to receive a random access response in the random access response receiving window indicated by the system information or the handover command, and accordingly receives a random access response (S620).
  • the random access response is transmitted in a MAC PDU format, and the MAC PDU may be transmitted in a physical downlink shared channel (PDSCH).
  • the physical downlink control channel (PDCCH) is also delivered in order for the terminal to properly receive the information delivered to the PDSCH. That is, the PDCCH includes information of a terminal receiving the PDSCH, frequency and time information of radio resources of the PDSCH, a transmission format of the PDSCH, and the like.
  • the random access response may include a random access preamble identifier (ID), an UL grant (uplink radio resource), a temporary C-RNTI (Temporary Cell-Radio Network Temporary Identifier), and a time alignment command (TAC). Since one random access response may include random access response information for one or more terminals, a random access preamble identifier may be included to indicate to which terminal the included UL Grant, temporary C-RNTI, and TAC are valid.
  • the random access preamble identifier may be an identifier for the random access preamble received by the base station.
  • the TAC may be included as information for the UE to adjust uplink synchronization.
  • the random access response may be indicated by a random access identifier on the PDCCH, that is, a random access-radio network temporary identifier (RA-RNTI).
  • RA-RNTI random access-radio network temporary identifier
  • the terminal When receiving the random access response valid to the terminal, the terminal processes the information included in the random access response, and performs the scheduled transmission to the base station (S630). That is, the terminal applies the TAC and stores the temporary C-RNTI. In addition, by using the UL Grant, data or newly generated data stored in the buffer of the terminal is transmitted to the base station. In this case, information that can identify the terminal should be included. This is because, in the contention-based random access procedure, the base station cannot determine which terminals perform random access, and thus it is necessary to identify the terminal in order to resolve the collision.
  • the terminal There are two methods for including the information identifying the terminal. If the UE already has a valid cell identifier assigned in the cell before performing random access, the UE transmits its cell identifier through the UL Grant. On the other hand, if a valid cell identifier has not been allocated before the random access procedure, the terminal transmits its own unique identifier (eg, S-TMSI or Random ID). In general, the unique identifier is longer than the cell identifier. If the terminal transmits data through the UL Grant, it initiates a timer (contention resolution timer) for conflict resolution.
  • a timer contention resolution timer
  • the terminal After receiving the random access response, the terminal transmits data including its identifier through the allocated UL Grant, and waits for an instruction of the base station to resolve the collision (S640). That is, it attempts to receive a PDCCH to receive a specific message.
  • Two methods may be proposed as a method of receiving a PDCCH.
  • its identifier transmitted through the UL Grant is a cell identifier
  • it may attempt to receive the PDCCH using its cell identifier. In this case, if the PDCCH is received through its cell identifier before the conflict resolution timer expires, the UE determines that the random access has been normally performed and terminates the random access.
  • the terminal may determine that the random access is normally performed and may terminate the random access.
  • contention-free random access may be terminated by the terminal receiving a random access response.
  • Non-competition based random access may be initiated by request, such as handover and / or command of a base station. However, in the above two cases, contention based random access may also be performed.
  • the terminal is assigned a designated random access preamble with no possibility of collision from the base station.
  • the allocation of the random access preamble may be performed through the handover command and the PDCCH command (S710).
  • the UE After receiving the random access preamble designated for the UE, the UE transmits the corresponding random access preamble to the base station (S720).
  • the base station When the base station receives the random access preamble, the base station transmits a random access response to the terminal in response (S730).
  • the procedure related to the random access response may refer to S620 of FIG. 6 described above.
  • the new type of system information may be divided into minimum system information and other system information.
  • the minimum system information may be broadcast periodically.
  • the minimum system information may include basic information necessary for initial access to the cell and information for obtaining other system information that is provisioned or periodically broadcast on an on-demand basis.
  • the minimum system information may include at least one of a SFN, a list of PLMNs, a cell ID, a cell camping parameter, and a RACH parameter. If the network allows an on-demand mechanism, the parameters needed to request other system information may be included in the minimum system information.
  • the other system information may mean all system information that is not broadcast in the minimum system information.
  • the RRC_INACTIVE state is newly introduced in addition to the existing RRC_CONNETED state and RRC_IDLE state.
  • the RRC_INACTIVE state is a state introduced to efficiently manage a specific terminal (eg, mMTC terminal).
  • the terminal in the RRC_INACTIVE state performs a radio control procedure similar to the terminal in the RRC_IDLE state to reduce power consumption.
  • the terminal in the RRC_INACTIVE state maintains the connection state between the terminal and the network similarly to the RRC_CONNECTED state in order to minimize the control procedure required when transitioning to the RRC_CONNECTED state.
  • the radio connection resources are released, but the wired connection can be maintained.
  • radio access resources may be released, but the NG interface between gNB and NGC or the S1 interface between eNB and EPC may be maintained.
  • the core network recognizes that the terminal is normally connected to the base station.
  • the base station may not perform connection management for the terminal in the RRC_INACTIVE state.
  • the MME may maintain the S1 connection of the activated UE.
  • the AMF may maintain the NG connection of the activated UE.
  • the RRC_INACTIVE state may be used in a concept similar to a lightly connected mode, a lightly connected mode, or a semi-connected mode.
  • 5G RAN is a non-centralized deployment scenario and co-sited deployment according to the type of base station functions deployed in a central unit and a distributed unit, and coexistence with 4G base stations. It may be divided into a Deployment with E-UTRA scenario and a Centralized Deployment scenario.
  • 5G RAN, gNB, Next Generation NodeB, New RAN, and NR BS New Radio Base Station
  • 5G RAN, gNB, Next Generation NodeB, New RAN, and NR BS New Radio Base Station
  • FIG. 9 shows a scenario of separated base station deployment (Centralized Deployment).
  • the gNB may be divided into a central unit and a distribution unit. That is, gNB may be separated and operated hierarchically.
  • the central unit may perform the function of the upper layers of the base station, and the distributed unit may perform the function of the lower layers of the base station.
  • FIG. 10 illustrates a functional split between a central unit and a distributed unit in a split base station deployment scenario.
  • the RRC layer is in the central unit and the PDCP layer, RLC layer, MAC layer, physical layer and RF are in the distributed unit.
  • the RRC layer and PDCP layer are in the central unit and the RLC layer, MAC layer, physical layer and RF are in the distributed unit.
  • the RRC layer, PDCP layer and RLC upper layer are in the central unit and the RLC lower layer, MAC layer, physical layer and RF are in the distributed unit.
  • the RRC layer, PDCP layer and RLC layer are in the central unit and the MAC layer, physical layer and RF are in the distributed unit.
  • the RRC layer, PDCP layer, RLC layer and MAC upper layer are in the central unit and the MAC lower layer, physical layer and RF are in the distributed unit.
  • the RRC layer, PDCP layer, RLC layer and MAC layer are in the central unit and the physical layer and RF are in the distributed unit.
  • the RRC layer, PDCP layer, RLC layer, MAC layer and upper physical layer are in the central unit, and the lower physical layer and RF are in the distributed unit.
  • the RRC layer, PDCP layer, RLC layer, MAC layer and physical layer are in the central unit and the RF is in the distributed unit.
  • the central unit may be referred to as a CU, and the distribution unit may be referred to as a DU.
  • the CU may be a logical node hosting a radio resource control (RRC), a service data adaptation protocol (SDAP) and a packet data convergence protocol (PDCP) layer of the gNB, and the DU may be a radio link control (RLC) of the gNB. It may be a logical node that hosts a media access control (MAC) and a physical (PHY) layer. Alternatively, the CU may be a logical node hosting the RRC and PDCP layers of en-gNB.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • It may be a logical node that hosts a media access control (MAC) and a physical (PHY) layer.
  • the CU may be a logical node hosting the RRC and PDCP layers of en-gNB.
  • the generated information should be transmitted to the terminal through the DU.
  • system information to be broadcast is also generated at the RRC layer of the CU, signaling between the CU and the DU may be required for the DU to broadcast the system information.
  • signaling between the CU and the DU may be necessary for the DU to broadcast the system information.
  • the CU-DU split scenario there is no procedure for the DU to transmit the system information requested by the terminal to the terminal.
  • FIG. 11 illustrates a procedure for providing system information according to an embodiment of the present invention.
  • the DU of the base station may receive system information from the CU of the base station.
  • the system information may be received via the F1 interface.
  • the F1 interface may mean an interface between a CU and a DU.
  • the system information may be system information owned by the CU of the base station.
  • the DU of the base station may receive from the CU all other system information except for SIB1 among the system information held by the CU.
  • System information held by the CU may be included in the RRC container.
  • the system information held by the CU of the base station may be transmitted from the CU of the base station to the DU of the base station in the F1 setup procedure.
  • the system information may be included in an F1 setup response message.
  • the DU of the base station may receive information related to the system information from the CU of the base station.
  • the information related to the system information includes a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, and broadcast activation. ), DU ID, cell ID, or beam ID.
  • the F1 setup response message may be defined as shown in Table 1.
  • M YES reject Cells to be Activated List 0 .. 1 > Cells to be Activated List Item 1 .. ⁇ maxCellingNBDU> List of cells to be activated YES reject >> NCGI M - - >> gNB-CU System Information M RRC container with system information owned by gNB-CU - - >> PCI O Physical Cell ID - -
  • the F1 setup response message transmitted from the CU to the DU may include gNB-CU System Information.
  • the gNB-CU System Information may be an RRC container including system information held by a CU.
  • the gNB-CU System Information may include all other system information except SIB1 among the system information held by the CU.
  • the DU of the base station may receive a request for system information from the terminal.
  • the terminal may be in an RRC_INACTIVE state.
  • the terminal may be in an RRC_IDLE state.
  • the system information request by the terminal may be included in message 3 in a random access procedure.
  • the DU of the base station may not interpret the message 3 because there is no RRC layer. Therefore, the DU of the base station needs to send message 3 to the base station CU.
  • the system information may be on-demand system information or other system information.
  • the DU of the base station may transmit a request for system information received from the terminal to the CU.
  • a message including a container to piggyback the request for system information may be transmitted from the DU to the CU.
  • the request for the system information may be included in an initial UL RRC message transfer message.
  • the initial UL RRC message delivery message may be transmitted by the DU to deliver an initial layer 3 message to the CU on the F1 interface.
  • the initial UL RRC message transfer message may be defined as shown in Table 2.
  • the DU of the base station may receive a message from the CU instructing to broadcast the requested system information.
  • the message may be an SI broadcast request message.
  • the message may be a system information delivery command message.
  • the message may include information indicating the requested system information.
  • the message may include an identifier, index or number for the requested system information.
  • the message may include Other SI type. Accordingly, the DU may know that system information corresponding to the other system information type should be broadcast.
  • the message may include timing information for broadcasting.
  • the timing information for the broadcast may be a time interval for broadcast of other system information.
  • the SI broadcast request message or the system information delivery command message may be defined as shown in Table 3.
  • the CU of the base station may transmit a message including the other system information type to the DU, and the DU may broadcast system information corresponding to the other system information type.
  • the CU of the base station may transmit a message including the broadcast time interval to the DU, and the DU may broadcast system information corresponding to the other system information type based on the broadcast time interval.
  • the DU of the base station may provide the requested system information to the terminal.
  • the system information may be provided to the terminal through broadcast signaling or dedicated signaling.
  • the CU may provide the DU with information necessary for broadcasting system information and system information and system information held by the CU.
  • the DU receiving the request for system information from the terminal may transmit the request to the CU, and may receive information indicating the system information that needs to be broadcasted or transmitted from the CU.
  • the CU provides information related to the SIB to the DU in advance, signaling between the CU and the DU due to the system information request of the UE may be reduced.
  • the CU instructs the DU only of the type of system information to be broadcast, signaling between the CU and the DU due to the system information request of the UE may be reduced.
  • FIG. 12 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • the CU may provide an indication for the requested SIB to the DU.
  • the CU may provide the DU with information related to the requested SIB. For example, when the DU receives a system information request from the UE through message 3 in a random access procedure, an indication of the requested SIB or information related to the requested SIB may be provided to the DU from the CU.
  • the CU may provide the DU with information related to some or all of the SIBs supported by the CU.
  • the CU may provide the DU with information related to all of the system information owned by the CU.
  • the CU may provide the DU with all other system information except SIB1 among system information owned by the CU.
  • the CU may transmit information related to the updated SIB to the DU.
  • the DU may release information related to the requested SIB.
  • the CU may transmit a message to the DU including information related to all the SIBs provided by the CU.
  • the CU may transmit a message to the DU including information related to some SIBs provided by the CU.
  • the information related to the partial SIB may be minimum system information or system information about the SIB frequently requested by the terminal.
  • the information related to the some SIB may be transmitted to efficiently manage the resources of the DU for storing the information related to the SIB.
  • the message may be an F1 Setup Response message or an F1 Setup Request message.
  • the CU may send a message to the DU including information related to the SIBx.
  • Information related to the SIB included in the message may be provided for each SIB.
  • the information related to the SIB includes a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, and broadcast activation. It may include at least one of DU ID, cell ID or beam ID.
  • the information related to the SIB may include system information and information necessary for broadcasting the system information in the DU.
  • the container may be used to transmit system information from the CU to the DU including one or more parameters to be broadcast.
  • the timing information for the broadcast may be information or time for assisting scheduling for broadcasting system information in the DU.
  • the timing information for broadcasting may include at least one of a length of a window in which system information is broadcast, a number of times in which system information is broadcast, or a position in the window when system information is broadcast.
  • the logical channel related information may include logical channel information for indicating a logical channel for transmitting system information.
  • the logical channel information may be a logical channel ID.
  • the broadcast activation may indicate whether the provided system information is broadcast. The broadcast activation may be set when system information is always broadcasted or frequently requested by the terminal.
  • the F1 setup response message or F1 setup request message may include a cell ID for each cell. If the DU controls, manages or covers one or more beams, the F1 setup response message or F1 setup request message may include a beam ID for each beam.
  • the DU may broadcast system information related to the SIB on which the broadcast is activated.
  • the terminal may transmit a system information request to the DU to request on-demand system information.
  • the system information request may be included in message 3 in a random access procedure.
  • the terminal may be in an RRC_IDLE state.
  • the terminal may be in an RRC_INACTIVE state.
  • the on-demand system information may be system information provided through broadcast signaling or dedicated signaling at the request of the terminal.
  • step S1204 upon receiving the system information request from the terminal, the DU may transmit the system information request to the CU.
  • a message including a container for piggybacking the system information request may be transmitted from the DU to the CU.
  • the message may be an initial UE message or a new message.
  • the CU may identify the requested on-demand system information based on the received system information request. And, depending on whether the CU provided the DU with information related to all the SIBs supported by the CU in step S1201, two possible options may exist.
  • the CU may transmit the information about the requested SIB to the DU.
  • the information on the requested SIB may indicate the requested SIB.
  • the information on the requested SIB may be an identifier, an index, or a number for the SIB identified based on the system information request.
  • the CU may send the SIB type to the DU. Through this, the CU may instruct the DU to broadcast the requested SIB, and the DU may broadcast system information related to the indicated SIB.
  • the CU may send a message to the DU including a container to piggyback the response to the system information request.
  • the message may be a downlink RRC transport message or a new message.
  • the CU avoids responding to the system information request.
  • the backing may send a message containing the container to the DU.
  • the message may be a downlink RRC transport message or a new message.
  • the CU may transmit a message for providing information related to the requested SIB to the DU.
  • the CU may send a message to the DU including information related to SIBy.
  • the message may be a system information broadcast request message or a new message.
  • Information related to the SIB included in the message may be provided for each SIB.
  • the information related to the SIB includes a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, and broadcast activation. It may include at least one of DU ID, cell ID or beam ID.
  • the DU may store information related to the requested SIB.
  • the DU may transmit a system information broadcast response message or a new message to the CU.
  • the response message may include at least one of an SIB ID, a DU ID, a cell ID, or a beam ID corresponding to the ID included in the message received in step S1205b.
  • the CU indicates that the entity (eg, DU, cell and / or beam) indicated by the CU cannot broadcast the corresponding system information. It can be recognized.
  • step S1206 when receiving a message from the CU, the DU may send a message 4 to the terminal.
  • the DU may broadcast system information related to the requested SIB.
  • System information related to the requested SIB may be broadcast after transmission of message 4.
  • the DU may broadcast system information related to the SIB in the beam or cell indicated by the ID.
  • the CU may send a system information broadcast request message (SI Broadcast Request message) or a new message to the DU.
  • SI Broadcast Request message may include information related to the SIB for each SIB.
  • the CU may send a message to the DU including information related to the updated SIBz.
  • the CU may send a message to the DU containing information related to the SIBz to be updated.
  • the information related to the SIB may include a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, or broadcast activation. It may include at least one of.
  • the broadcast activation may indicate that system information related to SIBz is not broadcast.
  • the DU may replace the previously provided information associated with the SIB with the received one.
  • the DU may transmit a system information broadcast response message (SI Broadcast Response message) including a SIB ID related to the updated SIB or a new message to the CU.
  • SI Broadcast Response message SI Broadcast Response message
  • step S1210 for a requested SIB, if there is no request for on-demand system information for a specific time, the DU can efficiently manage the resource of the DU for storing information related to the requested SIB. It may be determined whether to release the information related to the.
  • step S1211 when determining release for the information related to the requested SIB, the DU sends a System Release Information (SI Release Indication) message or a new message to indicate that the DU no longer has information related to the SIB.
  • SI Release Indication System Release Information
  • the message may include an identifier, index, or number for the released SIB.
  • the message may include the type of SIB released.
  • the DU may release information related to the indicated SIB.
  • the CU may provide the DU with information necessary for broadcasting system information and system information.
  • the information may basically be provided when supporting broadcasting of system information.
  • the information may be provided at the request of the terminal.
  • the CU provides information related to the SIB to the DU in advance, signaling between the CU and the DU due to the on-demand system information request of the UE may be reduced.
  • resources of the DU for storing information related to the requested SIB can be efficiently managed.
  • FIG. 13 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • the CU may provide the DU with information related to some or all of the SIB provided by the CU. Additionally, if the CU receives a request from the DU for system information related to the SIB corresponding to the on-demand system information by the terminal, or if the CU decides to update the information related to the SIB, the CU is requested or updated. Information related to the SIB may be transmitted to the DU. Further, if there is no request for on-demand system information for the requested SIB, the DU may release information related to the requested SIB.
  • the CU may transmit a message to the DU including information related to all SIBs provided by the CU.
  • the CU may transmit a message to the DU including information related to some SIBs provided by the CU.
  • the information related to the partial SIB may be minimum system information or system information about the SIB frequently requested by the terminal.
  • the information related to the some SIB may be transmitted to efficiently manage the resources of the DU for storing the information related to the SIB.
  • the message may be an F1 Setup Response message or an F1 Setup Request message.
  • the CU may send a message to the DU including information related to the SIBx.
  • Information related to the SIB included in the message may be provided for each SIB.
  • the information related to the SIB includes a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, and broadcast activation. It may include at least one of DU ID, cell ID or beam ID.
  • the information related to the SIB may include system information and information necessary for broadcasting the system information in the DU.
  • the container may be used to transmit system information from the CU to the DU including one or more parameters to be broadcast.
  • the timing information for the broadcast may be information or time for assisting scheduling for broadcasting system information in the DU.
  • the timing information for broadcasting may include at least one of a length of a window in which system information is broadcast, a number of times in which system information is broadcast, or a position in the window when system information is broadcast.
  • the logical channel related information may include logical channel information for indicating a logical channel for transmitting system information.
  • the logical channel information may be a logical channel ID.
  • the broadcast activation may indicate whether the provided system information is broadcast. The broadcast activation may be set when system information is always broadcasted or frequently requested by the terminal.
  • the F1 setup response message or F1 setup request message may include a cell ID for each cell. If the DU controls, manages or covers one or more beams, the F1 setup response message or F1 setup request message may include a beam ID for each beam.
  • the DU may broadcast system information related to the SIB on which the broadcast is activated.
  • the terminal may transmit a system information request to the DU to request on-demand system information.
  • the system information request may be included in message 1 in a random access procedure.
  • the preamble transmitted by the terminal may be mapped to all SIBs.
  • the preamble transmitted by the terminal may be mapped to one or more SIBs. This mapping may be broadcast by the DU or may be preset between the DU and the terminal.
  • the UE may transmit a plurality of preambles in which each preamble is mapped to the SIB to the DU.
  • the terminal may be in an RRC_IDLE state.
  • the terminal may be in an RRC_INACTIVE state.
  • the DU may identify whether the received on-demand system information can broadcast system information related to the SIB requested. If the DU can broadcast system information related to the SIB requested by the received on-demand system information, the DU may omit signaling with the CU. For example, where possible, steps S1305a, S1305b, and S1305c may be omitted. If the DU cannot broadcast system information related to the SIB requested by the received on-demand system information, the DU may perform signaling with the CU.
  • the DU may send a message to the CU including information about the requested SIB.
  • the information on the requested SIB may indicate the requested SIB.
  • the information on the requested SIB may be an identifier, an index, or a number for the SIB identified based on the system information request.
  • the message may be an on-demand system information indication message or a new message.
  • the CU may identify the requested on-demand system information.
  • the CU may transmit a message for providing information related to the requested SIB to the DU.
  • the CU may send a message to the DU including information related to SIBy.
  • the message may be a system information broadcast request message or a new message.
  • Information related to the SIB included in the message may be provided for each SIB.
  • the information related to the SIB includes a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, and broadcast activation. It may include at least one of DU ID, cell ID or beam ID.
  • the DU may store information related to the requested SIB.
  • the DU may transmit a system information broadcast response message or a new message to the CU.
  • the response message may include at least one of an SIB ID, a DU ID, a cell ID, or a beam ID corresponding to the ID included in the message received in step S1305b.
  • the CU indicates that the entity (eg, DU, cell and / or beam) indicated by the CU cannot broadcast the corresponding system information. It can be recognized.
  • step S1306 the DU may send a message 2 to the terminal.
  • the DU may broadcast system information related to the requested SIB.
  • the DU may broadcast system information related to the SIB in the beam or cell indicated by the ID.
  • the CU may send a system information broadcast request message (SI Broadcast Request message) or a new message to the DU.
  • SI Broadcast Request message may include information related to the SIB for each SIB.
  • the CU may send a message to the DU including information related to the updated SIBz.
  • the CU may send a message to the DU containing information related to the SIBz to be updated.
  • the information related to the SIB may include a SIB ID, a container including system information, timing information for broadcasting, logical channel related information, or broadcast activation. It may include at least one of.
  • the broadcast activation may indicate that system information related to SIBz is not broadcast.
  • the DU may replace the previously provided information associated with the SIB with the received one.
  • the DU may transmit a system information broadcast response message (SI Broadcast Response message) including a SIB ID related to the updated SIB or a new message to the CU.
  • SI Broadcast Response message SI Broadcast Response message
  • step S1310 for a requested SIB, if there is no request for on-demand system information for a specific time, the DU can efficiently manage the resource of the DU for storing information related to the requested SIB. It may be determined whether to release the information related to the.
  • step S1311 when determining release for the information related to the requested SIB, the DU sends a System Release Information (SI Release Indication) message or a new message to indicate that the DU no longer has information related to the SIB.
  • SI Release Indication System Release Information
  • the message may include an identifier, index, or number for the released SIB.
  • the message may include the type of SIB released.
  • the DU may release information related to the indicated SIB.
  • the CU may provide the DU with information necessary for broadcasting system information and system information.
  • the information may basically be provided when supporting broadcasting of system information.
  • the information may be provided at the request of the terminal.
  • the CU provides information related to the SIB to the DU in advance, signaling between the CU and the DU due to the on-demand system information request of the UE may be reduced.
  • resources of the DU for storing information related to the requested SIB can be efficiently managed.
  • FIG. 14 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • the CU if the CU receives a request for grouped system information broadcast of the terminal through the DU, or if the CU determines to broadcast one or more grouped system information, the CU May transmit one or more grouped system information (eg, MIB, SIB1 and SIB2 in LTE) to the DU using a message for each grouped system information.
  • grouped system information eg, MIB, SIB1 and SIB2 in LTE
  • the terminal may transmit a system information request to the DU to request on-demand system information.
  • the system information request may be included in message 1 in a random access procedure.
  • the preamble transmitted by the terminal may be mapped to all system information groups.
  • the preamble transmitted by the terminal may be mapped to one or more system information groups. This mapping may be broadcast by the DU or may be preset between the DU and the terminal.
  • the UE may transmit a plurality of preambles in which each preamble is mapped to a system information group, to the DU.
  • the terminal may be in an RRC_IDLE state.
  • the terminal may be in an RRC_INACTIVE state.
  • the DU may transmit a message including the requested system information group to the CU based on message 1 received from the terminal.
  • the message may be an On-demand SI Indication message or a new message.
  • the CU receives an on-demand system information indication message or a new message including the system information group x, or if the CU decides to broadcast the system information group x, the CU requests to broadcast the system information group x.
  • the message may be sent to the DU.
  • the message may be a SIx Broadcast Request message or a new message.
  • the x may mean a group x. For example, if system information group 2 and system information group 3 are to be broadcast, the CU may use the SI2 broadcast request message and the SI3 broadcast request message, respectively.
  • the SIx broadcast request message or new message may include a system information group x, timing information for broadcasting, logical channel related information, DU ID, cell ID, and beam. It may include at least one of ID or on-demand SI related information.
  • the SIx broadcast request message or the new message may include information necessary for broadcasting the system information group x in the system information group x and the DU.
  • the system information group x may include one or more parameters to be broadcast.
  • the timing information for the broadcast may be information or time for assisting scheduling for broadcasting the system information group x in the DU.
  • For each parameter in the system information group x there may be timing information for broadcasting for each parameter, which may have different values.
  • the logical channel related information may include logical channel information for indicating a logical channel for transmitting the system information group x.
  • the logical channel information may be a logical channel ID.
  • the SIx broadcast request message or new message may include a cell ID for each cell.
  • the SIx broadcast request message or new message may include a beam ID for each beam.
  • the on-demand system information related information may include at least one of a length of a window in which system information is broadcast, a number of times in which system information is broadcast, or a position in the window when system information is broadcast.
  • the DU may transmit a SIx Broadcast Response message or a new message to the CU.
  • the response message may include at least one of a DU ID, a cell ID, or a beam ID corresponding to the ID included in the request message in step S1403. If the ID included in the request message is not included in the response message, the CU can recognize that the entity (eg, DU, cell and / or beam) indicated by the CU cannot broadcast system information group x. have.
  • the DU may store information included in the request message. And, based on the stored information, the DU may broadcast the system information group x. If the SIx broadcast request message or the new message includes the cell ID or the beam ID, the DU may broadcast the system information group x in the beam or cell indicated by the ID. If the SIx broadcast request message or the new message includes the on-demand system information related information, the DU may have all the information included in the on-demand system information related information or the request message during the time of broadcasting the system information. Thereafter, the DU may remove or discard the on-demand system information related information or all the information.
  • the DU may broadcast the system information group x included in the request message from the CU.
  • a CU may manage system information to be broadcast to a terminal within coverage of the CU.
  • the CU may provide system information according to a request of the terminal.
  • 15 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • the CU if the CU receives a request for grouped system information broadcast of the terminal through the DU, or if the CU determines to broadcast one or more grouped system information, the CU May send one or more grouped system information (eg, MIB, SIB1 and SIB2 in LTE) to the DU using one message including all grouped system information.
  • grouped system information eg, MIB, SIB1 and SIB2 in LTE
  • the terminal may transmit a system information request to the DU to request on-demand system information.
  • the system information request may be included in message 1 in a random access procedure.
  • the preamble transmitted by the terminal may be mapped to all system information groups.
  • the preamble transmitted by the terminal may be mapped to one or more system information groups. This mapping may be broadcast by the DU or may be preset between the DU and the terminal.
  • the UE may transmit a plurality of preambles in which each preamble is mapped to a system information group, to the DU.
  • the terminal may be in an RRC_IDLE state.
  • the terminal may be in an RRC_INACTIVE state.
  • the DU may transmit a message including the requested system information group to the CU based on message 1 received from the terminal.
  • the message may be an On-demand SI Indication message or a new message.
  • step S1503 if the CU receives an on-demand system information indication message or new message including the system information group, or if the CU decides to broadcast one or more system information groups, the CU broadcasts one or more system information groups.
  • a request message can be sent to the DU.
  • the message may be an SI broadcast request message or a new message.
  • the message may include information for each system information group.
  • the message may include information about the first system information group and information about the second system information group.
  • the information on the first system information group includes system information group 1, timing information for broadcasting, logical channel related information, DU ID, cell ID, beam It may include at least one of ID or on-demand SI related information.
  • the information on the second system information group includes system information group 2, timing information for broadcasting, logical channel related information, DU ID, cell ID, It may include at least one of beam ID or on-demand SI related information.
  • the information on each system information group may include information necessary for broadcasting the system information group in the system information group and the DU.
  • the system information group may include one or more parameters to be broadcast.
  • the timing information for the broadcast may be information or time for assisting scheduling for broadcasting a system information group in the DU.
  • For each parameter in the system information group there may be timing information for broadcasting for each parameter, which may have different values.
  • the logical channel related information may include logical channel information for indicating a logical channel for transmitting a system information group.
  • the logical channel information may be a logical channel ID.
  • the SI broadcast request message or new message may include a cell ID for each cell.
  • the SI broadcast request message or new message may include a beam ID for each beam.
  • the on-demand system information related information may include at least one of a length of a window in which system information is broadcast, a number of times in which system information is broadcast, or a position in the window when system information is broadcast.
  • the DU may transmit an SI broadcast response message or a new message to the CU.
  • the response message may include at least one of a DU ID, a cell ID, or a beam ID corresponding to the ID included in the request message in step S1503.
  • the CU is determined by an entity (eg, DU, cell and / or beam) indicated by the CU. 1 It may be recognized that the system information group cannot be broadcast.
  • the DU may store information included in the first system information group and / or the second system information group. In addition, based on the stored information, the DU may broadcast the system information group 1 and / or the system information group 2. For example, for the first system information group, if the SI broadcast request message or the new message includes the cell ID or the beam ID, the DU may broadcast the system information group 1 in the beam or cell indicated by the ID. For example, if the SI broadcast request message or the new message includes on-demand system information related information for the first system information group, the DU may, during the time of broadcasting the system information for the first system information group, the first system. It may have all the information included in the request message for the information group or information related to the on-demand system information. Thereafter, the DU may remove or discard all information about the first system information group or information related to the on-demand system information.
  • the DU may broadcast the system information group 1 and / or the system information group 2 included in the information on the first system information group and / or the second system information group, respectively.
  • a CU may manage system information to be broadcast to a terminal within coverage of the CU.
  • the CU may provide system information to the DU according to the request of the terminal.
  • signaling between the CU and the DU can be reduced.
  • 16 illustrates a procedure for providing on-demand system information according to an embodiment of the present invention.
  • the CU may provide the DU with grouped system information to be broadcasted provided by the CU.
  • the grouped system information may be MIB, SIB1 or SIB2 in LTE.
  • the CU receives a request from the DU for grouped system information corresponding to on-demand system information by the terminal, or if the CU decides to update the grouped system information, the CU is requested or updated. Grouped system information may be transmitted to the DU.
  • the CU may transmit a message to the DU including all system information groups provided by the CU. Or, the CU may send a message to the DU including a group of system information provided by the CU.
  • the some system information group may be a minimum system information group or a system information group frequently requested by the terminal.
  • the some system information group may be transmitted to efficiently manage resources of the DU for storing information related to the system information group.
  • the message may be an F1 Setup Response message or an F1 Setup Request message.
  • the CU may send a message to the DU including information related to system information group x.
  • Information related to the system information group included in the message may be provided for each system information group.
  • the information related to the system information group includes at least one of a system information group, timing information for broadcasting, logical channel related information, DU ID, cell ID, and beam ID. It may include any one.
  • the information related to the system information group may include information necessary for broadcasting the system information group in the system information group and the DU.
  • the system information group may include one or more parameters to be broadcast.
  • the timing information for the broadcast may be information or time for assisting scheduling for broadcasting a system information group in the DU.
  • the timing information for broadcasting may include at least one of a length of a window in which system information is broadcast, a number of times in which system information is broadcast, or a position in the window when system information is broadcast.
  • For each parameter in the system information group there may be timing information for broadcasting for each parameter, which may have different values.
  • the logical channel related information may include logical channel information for indicating a logical channel for transmitting a system information group.
  • the logical channel information may be a logical channel ID.
  • the F1 setup response message or F1 setup request message may include a cell ID for each cell. If the DU controls, manages or covers one or more beams, the F1 setup response message or F1 setup request message may include a beam ID for each beam.
  • the DU may broadcast system information based on the information received from the CU.
  • the terminal may transmit a system information request to the DU to request on-demand system information.
  • the system information request may be included in message 1 or message 3 in a random access procedure.
  • the preamble transmitted by the terminal may be mapped to all system information groups.
  • the preamble transmitted by the terminal may be mapped to one or more system information groups. This mapping may be broadcast by the DU or may be preset between the DU and the terminal.
  • the UE may transmit a plurality of preambles in which each preamble is mapped to a system information group, to the DU.
  • the terminal may be in an RRC_IDLE state.
  • the terminal may be in an RRC_INACTIVE state.
  • the DU may identify whether the received on-demand system information may be broadcast. If the DU is able to broadcast the received on-demand system information, the DU may broadcast system information corresponding to the requested on-demand system information.
  • step S1604 if the DU has a part of the system information group provided by the CU, and the DU cannot broadcast the system information corresponding to the on-demand system information received from the terminal, the DU is in the message 1 or message 3
  • the message including the system information group requested by the UE may be transmitted to the CU.
  • the message may be a system information on-demand indication message or a new message.
  • the requested system information group may be related to the on-demand system information.
  • step S1605 if the CU receives a system information on-demand indication message or a new message, or if the CU decides to update the system information group, the CU may send a message to the DU requesting or providing the updated system information group.
  • the CU may send a message to the DU that includes information related to the requested or updated system information group y.
  • the message may be a system information broadcast request message or a new message.
  • Information related to the system information group included in the message may be provided for each system information group.
  • the information related to the system information group includes at least one of a system information group, timing information for broadcasting, logical channel related information, DU ID, cell ID, and beam ID. It may include any one.
  • the DU may transmit a system information broadcast response message (SI Broadcast Response message) or a new message to the CU.
  • SI Broadcast Response message a system information broadcast response message
  • the response message may include at least one of a DU ID, a cell ID, or a beam ID corresponding to the ID included in the message received in step S1605.
  • the CU broadcasts the system information group y to an entity (eg, DU, cell and / or beam) indicated by the CU. You can see that you can't.
  • the DU may store information included in the system information group y.
  • the DU may replace the previous information with information included in the system information group y.
  • the DU may broadcast a system information group based on the stored or replaced information. For the system information group y, if a SI Broadcast Request message or a new message includes the cell ID or beam ID, the DU may broadcast the system information group y in the beam or cell indicated by the ID. have.
  • step S1608 with respect to the system information group, if there is no request for on-demand system information for a specific time, the DU efficiently manages resources of the DU for storing information related to the system information group. All information related to can be released.
  • the CU may provide the DU with system information to be broadcasted to a terminal within the coverage of the CU.
  • the CU may provide system information to the DU according to the request of the terminal.
  • signaling between the CU and the DU due to the on-demand system information request of the terminal may be reduced.
  • FIG. 17 is a block diagram illustrating a method in which a DU of a base station provides system information according to an embodiment of the present invention.
  • the DU of the base station may receive the system information owned by the CU of the base station, which is held by the central unit (CU) of the base station, from the CU of the base station. have.
  • the system information held by the CU of the base station may be included in a container and transmitted from the CU of the base station to the DU of the base station.
  • the system information held by the CU of the base station may be transmitted from the CU of the base station to the DU of the base station in the F1 setup procedure.
  • the system information received from the CU of the base station may be all system information except for SIB1 among the system information held by the CU of the base station.
  • the CU may be a logical node hosting a radio resource control (RRC), a service data adaptation protocol (SDAP), and a packet data convergence protocol (PDCP) layer of the base station, and the DU may be an RLC (RLC) of the base station. It may be a logical node hosting a radio link control (MAC), a media access control (MAC), and a physical (PHY) layer.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC RLC
  • It may be a logical node hosting a radio link control (MAC), a media access control (MAC), and a physical (PHY) layer.
  • MAC radio link control
  • MAC media access control
  • PHY physical
  • the system information may be on-demand system information broadcast by a request of the terminal.
  • the system information may be other system information.
  • the DU of the base station may receive a request for the system information from the terminal.
  • the request for the system information may be transmitted from the terminal to the DU of the base station in a random access procedure.
  • the request for system information may be included in message 3.
  • the system information received from the CU of the base station may include the requested system information.
  • the DU of the base station may additionally receive the requested system information from the CU of the base station.
  • the DU of the base station may transmit a request for the system information to the CU of the base station.
  • the request for the system information may be included in a container and transmitted from the DU of the base station to the CU of the base station.
  • the DU of the base station may receive a message for commanding to broadcast the system information from the CU of the base station.
  • the message instructing to broadcast the requested system information may include the type of the requested system information.
  • the message instructing to broadcast the requested system information may include time information for broadcasting the requested system information.
  • the time information may be a broadcast time interval.
  • the DU of the base station may broadcast the requested system information.
  • the DU of the base station may transmit the requested system information to the terminal through dedicated signaling.
  • FIG. 18 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
  • the terminal 1800 includes a processor 1801, a memory 1802, and a transceiver 1803.
  • the memory 1802 is connected to the processor 1801 and stores various information for driving the processor 1801.
  • the transceiver 1803 is connected to the processor 1801 to transmit and / or receive a radio signal.
  • the processor 1801 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the terminal may be implemented by the processor 1801.
  • the DU 1810 of the base station includes a processor 1811, a memory 1812, and a transceiver 1813.
  • the memory 1812 is connected to the processor 1811 and stores various information for driving the processor 1811.
  • the transceiver 1813 is coupled to the processor 1811 to transmit and / or receive wireless signals.
  • Processor 1811 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the DU of the base station may be implemented by the processor 1811.
  • the CU 1820 of the base station includes a processor 1821, a memory 1822, and a transceiver 1823.
  • the memory 1822 is connected to the processor 1821 and stores various information for driving the processor 1821.
  • the transceiver 1823 is coupled to the processor 1821 to transmit and / or receive signals.
  • Processor 1821 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the CU of the base station may be implemented by the processor 1821.
  • the processor may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices.
  • the memory may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device.
  • the transceiver may include baseband circuitry for processing wireless signals.
  • the above technique may be implemented as a module (process, function, etc.) for performing the above-described function.
  • the module may be stored in memory and executed by a processor.
  • the memory may be internal or external to the processor and may be coupled to the processor by various well known means.

Landscapes

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

Abstract

L'invention concerne un procédé de diffusion d'informations de système, dans un système de communication sans fil, par une unité distribuée (DU) d'une station de base ainsi qu'un appareil destiné à prendre en charge le procédé. Le procédé peut comprendre les étapes suivantes : la réception, en provenance d'une unité centrale (CU) d'une station de base, d'informations de système détenues par la CU de la station de base ; la réception, à partir d'un terminal, d'une demande d'informations de système ; la réception, en provenance de la CU de la station de base, d'un message commandant la diffusion des informations de système ; et la diffusion des informations de système demandées.
PCT/KR2018/004251 2017-04-13 2018-04-11 Procédé et appareil de fourniture d'informations de système Ceased WO2018190636A1 (fr)

Priority Applications (14)

Application Number Priority Date Filing Date Title
JP2019504736A JP6661830B2 (ja) 2017-04-13 2018-04-11 システム情報を提供する方法及び装置
BR112019015576-7A BR112019015576A2 (pt) 2017-04-13 2018-04-11 Método e aparelho para fornecer informações do sistema
CN201880021567.3A CN110463275B (zh) 2017-04-13 2018-04-11 提供系统信息的方法和装置
EP18784633.2A EP3471463B1 (fr) 2017-04-13 2018-04-11 Procédé et appareil de fourniture d'informations de système
RU2019108844A RU2727722C1 (ru) 2017-04-13 2018-04-11 Способ и устройство для предоставления информации системы
MYPI2019000846A MY197833A (en) 2017-04-13 2018-04-11 Method and apparatus for providing system information
AU2018251514A AU2018251514B2 (en) 2017-04-13 2018-04-11 Method and apparatus for providing system information
MX2019008617A MX2019008617A (es) 2017-04-13 2018-04-11 Metodo y aparato para proporcionar informacion del sistema.
CA3036482A CA3036482C (fr) 2017-04-13 2018-04-11 Procede et appareil de fourniture d'informations de systeme
SG11201900188UA SG11201900188UA (en) 2017-04-13 2018-04-11 Method and apparatus for providing system information
US16/048,848 US10512030B2 (en) 2017-04-13 2018-07-30 Method and device for providing system information
PH12019500359A PH12019500359A1 (en) 2017-04-13 2019-02-20 Method and apparatus for providing system information
US16/711,163 US11375436B2 (en) 2017-04-13 2019-12-11 Method and device for providing system information
US17/725,247 US11882515B2 (en) 2017-04-13 2022-04-20 Method and device for providing system information

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US201762484897P 2017-04-13 2017-04-13
US62/484,897 2017-04-13
US201762492327P 2017-05-01 2017-05-01
US62/492,327 2017-05-01
US201762519889P 2017-06-15 2017-06-15
US62/519,889 2017-06-15
US201762529442P 2017-07-06 2017-07-06
US62/529,442 2017-07-06
KR1020180041939A KR101952345B1 (ko) 2017-04-13 2018-04-11 시스템 정보를 제공하는 방법 및 장치
KR10-2018-0041939 2018-04-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/048,848 Continuation US10512030B2 (en) 2017-04-13 2018-07-30 Method and device for providing system information

Publications (1)

Publication Number Publication Date
WO2018190636A1 true WO2018190636A1 (fr) 2018-10-18

Family

ID=63792702

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/004251 Ceased WO2018190636A1 (fr) 2017-04-13 2018-04-11 Procédé et appareil de fourniture d'informations de système

Country Status (2)

Country Link
AU (1) AU2018251514B2 (fr)
WO (1) WO2018190636A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111278060A (zh) * 2019-01-18 2020-06-12 维沃移动通信有限公司 一种以太帧传输方法和相关设备
CN111491370A (zh) * 2019-01-29 2020-08-04 华为技术有限公司 一种通信方法、网元、系统及存储介质
JP2021503808A (ja) * 2017-11-17 2021-02-12 中▲興▼通▲訊▼股▲ふぇん▼有限公司Ｚｔｅ Ｃｏｒｐｏｒａｔｉｏｎ 警報情報を伝送するための方法および装置
WO2025030547A1 (fr) * 2023-08-10 2025-02-13 Zte Corporation Systèmes et procédés pour prendre en charge une réception de multidiffusion dans un état rrc_inactive

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080039818A (ko) * 2006-11-01 2008-05-07 엘지전자 주식회사 무선 통신 시스템에서의 하향링크 데이터 전송 및 수신방법
KR20110093612A (ko) * 2010-02-09 2011-08-18 엘지전자 주식회사 무선 통신 시스템에서 시스템 정보 송수신 방법 및 장치
US20160234736A1 (en) * 2015-02-10 2016-08-11 Qualcomm Incorporated On-demand system information
KR20160135090A (ko) * 2015-05-15 2016-11-24 주식회사 케이티 단말의 무선연결 구성방법 및 그 장치
KR20170022933A (ko) * 2015-08-21 2017-03-02 삼성전자주식회사 무선 통신 시스템 내 단말의 통신 방법 및 장치

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180206178A1 (en) * 2017-01-13 2018-07-19 Futurewei Technologies, Inc. System and Method for Communicating System Information

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080039818A (ko) * 2006-11-01 2008-05-07 엘지전자 주식회사 무선 통신 시스템에서의 하향링크 데이터 전송 및 수신방법
KR20110093612A (ko) * 2010-02-09 2011-08-18 엘지전자 주식회사 무선 통신 시스템에서 시스템 정보 송수신 방법 및 장치
US20160234736A1 (en) * 2015-02-10 2016-08-11 Qualcomm Incorporated On-demand system information
KR20160135090A (ko) * 2015-05-15 2016-11-24 주식회사 케이티 단말의 무선연결 구성방법 및 그 장치
KR20170022933A (ko) * 2015-08-21 2017-03-02 삼성전자주식회사 무선 통신 시스템 내 단말의 통신 방법 및 장치

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021503808A (ja) * 2017-11-17 2021-02-12 中▲興▼通▲訊▼股▲ふぇん▼有限公司Ｚｔｅ Ｃｏｒｐｏｒａｔｉｏｎ 警報情報を伝送するための方法および装置
US11381952B2 (en) 2017-11-17 2022-07-05 Zte Corporation Method and apparatus for transmitting warning information
CN111278060A (zh) * 2019-01-18 2020-06-12 维沃移动通信有限公司 一种以太帧传输方法和相关设备
CN111278060B (zh) * 2019-01-18 2023-10-24 维沃移动通信有限公司 一种以太帧传输方法和相关设备
CN111491370A (zh) * 2019-01-29 2020-08-04 华为技术有限公司 一种通信方法、网元、系统及存储介质
WO2025030547A1 (fr) * 2023-08-10 2025-02-13 Zte Corporation Systèmes et procédés pour prendre en charge une réception de multidiffusion dans un état rrc_inactive

Also Published As

Publication number Publication date
AU2018251514A1 (en) 2019-01-31
AU2018251514B2 (en) 2020-02-06

Similar Documents

Publication Publication Date Title
KR102164229B1 (ko) 시스템 정보를 제공하는 방법 및 장치
WO2018230997A1 (fr) Procédé d'exécution d'une procédure de transfert intercellulaire dans un système de communication sans fil et dispositif associé
WO2018164469A1 (fr) Procédé et dispositif de transmission de données dans un scénario de partage cu-du
WO2017196056A2 (fr) Procédé et appareil de demande de sib dans un système de communication sans fil
WO2017196058A1 (fr) Procédé et dispositif de transmission d'une demande d'informations système dans un système de communication sans fil
WO2018230989A1 (fr) Procédé et appareil pour traiter la défaillance d'une demande d'informations de système
WO2018203709A1 (fr) Procédé et appareil permettant d'effectuer un accès à une cellule
WO2018208114A1 (fr) Procédé et appareil d'attribution de ressource de liaison latérale à l'aide d'un ue de relais dans un système de communication sans fil
WO2018174627A1 (fr) Procédé et dispositif pour indiquer le type de support utilisé pour le prochain message dans un système de communication sans fil
WO2019027205A1 (fr) Procédé et appareil de reprise de connexion rrc dans un scénario de division de cu-du
EP3497980A1 (fr) Procédé et appareil permettant d'effectuer un contrôle d'interdiction d'accès
WO2015142081A1 (fr) Procédé et appareil permettant d'annuler un rapport d'état de tampon déclenché pour la transmission dispositif-dispositif dans un système de communication sans fil
WO2018016865A1 (fr) Procédé et appareil de demande de sib d'intérêt
WO2019031808A1 (fr) Procédé de transmission et de réception de signaux dans un système de communication sans fil et dispositif associé
WO2016117889A1 (fr) Procédé d'établissement d'une procédure d'accès aléatoire dans un système d'agrégation de porteuses et dispositif associé
WO2018074874A1 (fr) Procédé de déclenchement de resélection de ressource pour une transmission de liaison latérale priorisée sur la transmission de liaison montante dans un système de communication sans fil, et dispositif associé
WO2018143656A1 (fr) Procédé et dispositif pour demander des informations de système
WO2017171427A1 (fr) Procédé de transmission d'informations système et station de base, et procédé de réception d'informations système et équipement d'utilisateur
WO2018066905A1 (fr) Procédé et dispositif pour réaliser une communication v2x
WO2019022477A1 (fr) Procédé et appareil de sélection de porteuse pour une transmission de liaison latérale dans un système de communication sans fil
WO2016126029A1 (fr) Procédé pour appliquer une nouvelle configuration de pucch dans un système d'agrégation de porteuses, et dispositif associé
WO2018084635A1 (fr) Procédé de passage d'un ngs à un eps dans un système de communication sans fil et appareil associé
WO2015002456A1 (fr) Méthode de sélection ou de resélection de relais pour service de proximité
WO2016072590A1 (fr) Procédé pour annuler des requêtes de planification déclenchées par un rapport d'état de mémoire tampon de liaison latérale dans un système de communication de dispositif à dispositif (d2d) et dispositif associé
WO2016117937A1 (fr) Procédé pour initier une procédure d'accès aléatoire dans un système d'agrégation de porteuses et dispositif associé

Legal Events

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

Ref document number: 18784633

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018784633

Country of ref document: EP

Effective date: 20190109

ENP Entry into the national phase

Ref document number: 2019504736

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018251514

Country of ref document: AU

Date of ref document: 20180411

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3036482

Country of ref document: CA

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019015576

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112019015576

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190729