WO2018066922A1 - Procédé d'exécution de vérification de validité d'un bloc d'informations système et appareil prenant en charge ledit procédé - Google Patents

Procédé d'exécution de vérification de validité d'un bloc d'informations système et appareil prenant en charge ledit procédé Download PDF

Info

Publication number
WO2018066922A1
WO2018066922A1 PCT/KR2017/010947 KR2017010947W WO2018066922A1 WO 2018066922 A1 WO2018066922 A1 WO 2018066922A1 KR 2017010947 W KR2017010947 W KR 2017010947W WO 2018066922 A1 WO2018066922 A1 WO 2018066922A1
Authority
WO
WIPO (PCT)
Prior art keywords
system information
information block
version
validation
stored system
Prior art date
Application number
PCT/KR2017/010947
Other languages
English (en)
Korean (ko)
Inventor
김상원
이영대
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2018066922A1 publication Critical patent/WO2018066922A1/fr

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

Definitions

  • the terminal relates to a technique for performing a validity check on each of the stored system information blocks.
  • 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).
  • OSI On-demand System Information
  • the existing system information may also be used in the new serving cell.
  • the terminal should determine whether to use the existing system information block in the new serving cell or request new service information to the network.
  • the terminal should determine whether the system information blocks currently held are valid. In this case, the terminal may perform an update only for an invalid system information block.
  • a terminal performs a validity check of a system information block (SIB) in a wireless communication system, storing a system information block received from a serving cell step; Receiving validation information for validating the stored system information block from a current serving cell; And validity checking of the system information block by comparing a validity area for each stored system information block, version information of the stored system information block, and a version index indicating the update status of each version with the validation information.
  • SIB system information block
  • the validity check information may include information regarding a cell ID of a current serving cell, a version of a system information block considered to be valid, and the index for each version.
  • the performing of the validation check may include the cell ID in a cell list of a valid area of the stored system information block, a version of the stored system information block and a version included in the validation information, and the stored When the version index of the system information block and the version index included in the validity check information are the same, the terminal may determine that the stored system information block is valid.
  • the performing of the validation check may include that the cell ID is not included in the cell list of the valid region of the stored system information block, the version of the stored system information block is not the same as the version included in the validation information, or Alternatively, when the version index of the stored system information block and the version index included in the validity check information are not the same, the terminal may determine that the stored system information block is invalid.
  • the method may further include discarding the stored system information block.
  • the performing of the validity checking may include comparing a value tag of the stored system information block with a value tag included in the validation information, wherein the system information block is determined to be invalid, and the stored system If the value tag of the information block and the value tag included in the validation information are the same and the cell ID is not included in the cell list of the valid region of the stored system information block, the terminal retains the stored system information block as it is. can do.
  • the method may further include requesting transmission of a new system information block for the discarded system information to a current serving cell.
  • the method may further include receiving valid timer setting information for each system information block from the serving cell.
  • the performing of the validity check may include determining that the validity timer is not valid for the expired system information block.
  • a terminal for validating a system information block in a wireless communication system comprising: a memory; Transceiver; And a processor connecting the memory and the transceiver, wherein the processor stores a system information block received from a serving cell and receives validation information for validating the stored system information block from a current serving cell. And storing the stored system information block by comparing a validity area for each stored system information block, version information of the stored system information block, and a version-specific index indicating an update status of each of the versions with the validation information, respectively.
  • a terminal is provided, which is configured to perform a validity check of.
  • the validity check information may include information regarding a cell ID of a current serving cell, a version of a system information block considered to be valid, and the index for each version.
  • the processor may include the cell ID in a cell list of a valid area of the stored system information block, a version of the stored system information block is the same as a version included in the validation information, and a version of the stored system information block. If the per-index and the per-version index included in the validity check information are the same, the terminal may be configured to determine that the stored system information block is valid.
  • the processor may not include the cell ID in the cell list of the valid region of the stored system information block, or the version of the stored system information block is not the same as the version included in the validity check information, or the stored system information. If the version-specific index of the block and the version-specific index included in the validity check information are not the same, the terminal may be configured to determine that the stored system information block is invalid.
  • the processor may be configured to discard the stored system information block.
  • the processor is configured to perform the validation by comparing the value tag of the stored system information block with the value tag included in the validation information, and determines that the system information block is not valid, but the stored system information. If the value tag of the block and the value tag included in the validation information are the same and the cell ID is not included in the cell list of the valid region of the stored system information block, the processor retains the stored system information block as it is. It can be configured to.
  • the terminal may save radio resources by not updating or receiving all system information or updating or receiving only invalid 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. 7 is a flowchart illustrating a method of performing system information validation according to an embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a method of performing system information validation according to an embodiment of the present invention.
  • FIG. 9 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 serving gateway (S-GW) that serves as a user plane.
  • MME mobility management entity
  • S-GW serving 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
  • SI system information
  • 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 MIB transmission is repeated in all radio frames within a 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.
  • System information is commonly applied to all terminals connected in a cell, and the terminal must always maintain the latest system information for proper operation. If the system information is changed, the UE should know in advance when the base station transmits the new system information.
  • 3GPP has introduced the concept of a BCCH modification period. It demonstrates concretely below.
  • the base station if the base station intends to update the system information in the n + 1th change interval, the base station notifies the terminals of the update of the system information during the nth change interval.
  • the terminal notified of the update of the system information in the nth change interval section receives and applies new system information as soon as the n + 1th change interval starts.
  • the base station If an update of the system information is scheduled, the base station includes the system information modification indicator in the paging message.
  • the paging message is a message received by the idle mode terminal, but because the notification of the update of the system information through the paging message, the connected mode terminal should also receive the paging message from time to time to check whether the system information is updated.
  • on-demand system information (OSI) has been proposed.
  • OSI on-demand system information
  • the terminal may request system information from the cell, and the network receiving the request may transmit the requested system information to the terminal.
  • the existing system information may also be used in the new serving cell.
  • the terminal may determine whether to use the system information currently held in the new serving cell or request new service information from the network.
  • the terminal should determine whether the system information currently held is valid. In this case, the terminal may update the invalid system information. That is, the terminal may save radio resources by updating only the system information that needs updating without updating all system information.
  • the terminal may receive and store system information received from the existing serving cell.
  • the serving cell may be changed or existing system information may be updated.
  • the terminal may receive information (hereinafter, validation information) necessary for validating existing system information from a current serving cell (a new serving cell when the serving cell is changed).
  • the terminal may determine whether the existing system information is valid in the current serving cell. If the system information is valid in the current serving cell, the terminal may utilize the system information. If the system information is not valid in the current serving cell, the terminal may discard the system information.
  • system information may be transmitted and stored in the form of an information block, and examples of the information block include SIB1, SIB2, and other System Information Blocks (SIBn).
  • FIG. 7 is a flowchart illustrating a method of checking the validity of a system information block according to an embodiment of the present invention.
  • the terminal may receive a system information block from the first cell and store it.
  • the stored system information is common system information, and may be used not only in the serving cell but also in adjacent cells in some cases.
  • the terminal may store at least one of the following information together with the system information block.
  • Validity area by system information block (validity area or cell list by SIB)
  • the terminal may store a plurality of versions for one system information block.
  • Each of the different versions of the system information block may have different value tags, valid areas, and valid timer settings.
  • the terminal may store four versions for each system information block. Therefore, while using the first version of the specific system information block, the terminal may retrieve the second version stored without additional reception from the base station when the second version is needed.
  • the version information of the system information block may indicate whether the system information block is a first version, a second version, a third version, or a fourth version.
  • the terminal may store the maximum number of versions of the system information block that can be stored, a new system information block may occur.
  • the terminal may delete a system information block corresponding to a part of the stored version and allocate version information corresponding to the deleted system information to the new system information block.
  • the terminal may update the version of the corresponding system information block.
  • the terminal needs to distinguish whether the system information block corresponding to the first version is the system information block before the update or the system information block after the update.
  • the value tag (version index) for each version indicates the update status of each version of the system information block. That is, by checking the version index of the system information block, the terminal can prevent the system information block before updating even if the version information (for example, the first version) is the same.
  • the terminal may store a first version, a second version, a third version, and a fourth version for a specific system information block.
  • indices of 1, 3, 5, and 5 may be allocated to the first version, the second version, the third version, and the fourth version, respectively.
  • the updated first version may have an index of nine.
  • the terminal may confirm that the index of the first version is 9, thereby knowing that the corresponding system information block is data after the update.
  • different indexes value tags
  • the index of the third version is 5
  • the index of the fourth version is 5
  • the terminal distinguishes the version information (whether it is the third version or the fourth version) by It may be recognized that the system information block and the fourth version of the system information block are different system information blocks.
  • the valid area for each system information block indicates an area where the system information block is considered valid, and may include a list of cells in which the system information block is valid.
  • the terminal may start the timer upon receiving the system information block from the system serving cell.
  • the timer of the existing system information block corresponding to the system information block may be stopped. If the timer expires, the terminal may consider the system information block as invalid. In addition, the terminal may delete the system information block whose timer has expired.
  • the terminal may change the serving cell to the second cell.
  • the serving cell of the terminal may be changed to the second cell by handover or cell-reselection procedure.
  • the changing of the serving cell is not an essential step, and even when at least some of the system information blocks are updated, the present embodiment of performing the validity check on the stored system information blocks may be applied.
  • the first cell and the second cell may be classified according to whether the current cell is a serving cell of the terminal. Therefore, when the serving cell is not changed, both the first cell and the second cell may be the same cell as the serving cell of the current terminal.
  • the terminal may receive validation information necessary for validating the system information block from the second cell.
  • the validity check information may include at least one of the following information.
  • the validation information may be a value tag of a currently valid system information block, a cell ID of a current serving cell, version information of the system information block, and an index for each version.
  • the terminal may perform a validity check on the stored system information block.
  • the terminal may determine whether the system information block is valid by comparing the stored system information block with the validity check information.
  • the terminal may include a valid region of a stored system information block, a version of the system information, and a version-specific index, a cell ID of a current serving cell, a version of a system information block included in validation information and the version If the respective indexes match, it may be determined that the corresponding system information block is valid.
  • the terminal may determine that the stored system information block is valid.
  • the terminal If, as a result of performing a validity check on a system information block, the value tag of the validation information and the value tag of the system information block are not the same, or the valid area of the system information block in which the cell ID of the new serving cell is stored (cell If the index of the system information block and the index of the stored system information block that are not included in the list, or the index of the stored system information block is not the same, or the index for each version is not the same, the terminal is not valid. You can judge. That is, when at least one of the valid region, the version, and the version-specific index of the stored system information block does not match the validation information, the terminal may consider the system information block to be invalid.
  • the terminal may determine that the valid information timer is not valid even for the expired system information block.
  • the terminal may use the corresponding system information block.
  • the terminal may discard the system information block. Furthermore, the terminal may newly receive the corresponding system information block from the second cell (current serving cell). In one example, the UE may delete the same type of system information block as the received system information block for all valid system information blocks received from the current serving cell. In addition, for all system information blocks that the terminal considers invalid, the terminal may discard the system information block.
  • the corresponding system information block is determined. Since the terminal is not currently valid in the serving cell, the terminal may discard the corresponding system information block. If the cell ID of the current serving cell is not included in the valid area list of the system information block stored in the terminal, the system information block may not be discarded. This is because when the terminal moves to a cell included in the valid region list, the system information may be regarded as a valid system information block again.
  • FIG. 8 is a flowchart illustrating a method of checking the validity of a system information block according to an embodiment of the present invention.
  • the terminal may receive the system information block from the serving cell and store it.
  • the system information is common system information, which may be used in adjacent cells in some cases.
  • the system information may be received and stored in the form of an information block, and examples of the information block include SIB1, SIB2, and other System Information Blocks (SIBn).
  • SIB1, SIB2, and other System Information Blocks (SIBn) The terminal may store at least one of the following information together with the system information block.
  • Validity area by system information block (validity area or cell list by SIB)
  • the terminal may receive validation information necessary for validating the system information block from the current serving cell.
  • the validity check information may include at least one of the following information.
  • the validity check information may include at least one of a cell ID of a current serving cell, version information of a system information block considered to be valid, and information on an index indicating the update status of the version.
  • the current serving cell in which the terminal receives the validation information in step S704 may be the same as or different from the existing serving cell in which the terminal receives the system information block in step S702.
  • the terminal may perform validation of the system information block by comparing the stored validity area for each system information block, the version of the system information block, and the version-specific index with the validation information. Specifically, the terminal includes the cell ID in the cell list of the valid area of the stored system information block, the version of the stored system information block is the same as the version included in the validation information, and the When the version index and the version index included in the validity check information are the same, the terminal may determine that the stored system information block is valid.
  • the terminal does not include the cell ID in the cell list of the valid region of the stored system information block, the version of the stored system information block and the version included in the validation information, or the stored system information block If the version index of the and the version index included in the validity check information is not the same, the terminal may determine that the stored system information block is invalid. If it is determined that the stored system information block is invalid, the terminal may discard the stored system information block. In addition, the terminal may request transmission of a new system information block for the discarded system information block to the current serving cell.
  • the terminal may retain the stored system information block as it is.
  • the terminal may receive valid timer setting information for each system information block from the serving cell, and may determine that the valid timer is not valid for the expired system information block.
  • FIG. 9 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
  • the base station 900 includes a processor 901, a memory 902, and a transceiver 903.
  • the memory 902 is connected to the processor 901 and stores various information for driving the processor 901.
  • the transceiver 903 is coupled to the processor 901 to transmit and / or receive wireless signals.
  • Processor 901 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the base station may be implemented by the processor 901.
  • the terminal 910 includes a processor 911, a memory 912, and a transceiver 913.
  • the memory 912 is connected to the processor 911 and stores various information for driving the processor 911.
  • the transceiver 913 is connected to the processor 911 to transmit and / or receive a radio signal.
  • Processor 911 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the terminal may be implemented by the processor 911.
  • 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-described 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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention porte sur un procédé qui permet d'exécuter, au moyen d'un terminal, une vérification de validité d'un bloc d'informations système (SIB) dans un système de communication sans fil, et sur un appareil prenant en charge ledit procédé. Le procédé comprend les étapes consistant : à stocker des blocs d'informations système reçus d'une cellule de desserte ; à recevoir, d'une cellule de desserte actuelle, des informations de vérification de validité pour vérifier la validité des blocs d'informations système stockés ; à exécuter une vérification de validité du bloc d'informations système par comparaison des informations de vérification de validité avec une zone de validité de chacun des blocs d'informations système stockés, des informations de version des blocs d'informations système stockés et un indice spécifique à la version qui ordonne l'état de mise à jour de chaque version, respectivement.
PCT/KR2017/010947 2016-10-03 2017-09-29 Procédé d'exécution de vérification de validité d'un bloc d'informations système et appareil prenant en charge ledit procédé WO2018066922A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662403209P 2016-10-03 2016-10-03
US62/403,209 2016-10-03
US201762459995P 2017-02-16 2017-02-16
US62/459,995 2017-02-16

Publications (1)

Publication Number Publication Date
WO2018066922A1 true WO2018066922A1 (fr) 2018-04-12

Family

ID=61831081

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/010947 WO2018066922A1 (fr) 2016-10-03 2017-09-29 Procédé d'exécution de vérification de validité d'un bloc d'informations système et appareil prenant en charge ledit procédé

Country Status (1)

Country Link
WO (1) WO2018066922A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020061154A1 (fr) * 2018-09-18 2020-03-26 Google Llc Gestion d'informations système invalides dans un équipement utilisateur
CN113453313A (zh) * 2021-05-31 2021-09-28 翱捷科技股份有限公司 一种物联网设备进出省电模式快速驻留方法及装置
US11690000B2 (en) 2017-06-16 2023-06-27 Panasonic Intellectual Property Corporation Of America User equipment and base station participating in a system information acquisition procedure

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100790093B1 (ko) * 2005-01-27 2007-12-31 삼성전자주식회사 네트워크 공유 시스템에서 단말기가 시스템 정보의 유효성을 판단하여 시스템 정보를 수신하는 방법 및 장치
US20100255838A1 (en) * 2009-04-01 2010-10-07 Chih-Hsiang Wu Method of Handling System Information Reception and Related Communication Device
KR20110036074A (ko) * 2008-06-23 2011-04-06 콸콤 인코포레이티드 무선 통신 시스템에서 시스템 정보 수정을 관리하기 위한 방법 및 장치
KR20140040811A (ko) * 2011-07-14 2014-04-03 엘지전자 주식회사 무선 통신 시스템에서 시스템 정보 보고 방법 및 이를 지원하는 장치
US20150079981A1 (en) * 2011-07-13 2015-03-19 Zte Corporation Method and Device for Receiving System Information

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100790093B1 (ko) * 2005-01-27 2007-12-31 삼성전자주식회사 네트워크 공유 시스템에서 단말기가 시스템 정보의 유효성을 판단하여 시스템 정보를 수신하는 방법 및 장치
KR20110036074A (ko) * 2008-06-23 2011-04-06 콸콤 인코포레이티드 무선 통신 시스템에서 시스템 정보 수정을 관리하기 위한 방법 및 장치
US20100255838A1 (en) * 2009-04-01 2010-10-07 Chih-Hsiang Wu Method of Handling System Information Reception and Related Communication Device
US20150079981A1 (en) * 2011-07-13 2015-03-19 Zte Corporation Method and Device for Receiving System Information
KR20140040811A (ko) * 2011-07-14 2014-04-03 엘지전자 주식회사 무선 통신 시스템에서 시스템 정보 보고 방법 및 이를 지원하는 장치

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11690000B2 (en) 2017-06-16 2023-06-27 Panasonic Intellectual Property Corporation Of America User equipment and base station participating in a system information acquisition procedure
WO2020061154A1 (fr) * 2018-09-18 2020-03-26 Google Llc Gestion d'informations système invalides dans un équipement utilisateur
CN112673677A (zh) * 2018-09-18 2021-04-16 谷歌有限责任公司 用户设备中的无效系统信息处置
CN113453313A (zh) * 2021-05-31 2021-09-28 翱捷科技股份有限公司 一种物联网设备进出省电模式快速驻留方法及装置

Similar Documents

Publication Publication Date Title
WO2018124810A1 (fr) Procédé et appareil destinés à l'établissement de drb
WO2018062907A1 (fr) Procédé de gestion de contexte d'ue et dispositif permettant de le prendre en charge
WO2018008925A1 (fr) Procédé et appareil de notification de mme d'une recherche infructueuse d'un terminal
WO2018084630A1 (fr) Procédé et dispositif pour recevoir des informations système
WO2018230983A1 (fr) Procédé d'établissement d'un rapport sur la capacité d'un ue et dispositif prenant en charge le procédé
WO2017191919A1 (fr) Procédé et appareil de commande de puissance de liaison montante dans un transfert sans rach
WO2018128463A1 (fr) Procédé et dispositif d'émission/réception de données
WO2018164471A1 (fr) Procédé et appareil pour recevoir un service mbms sur la base d'un faisceau
WO2018062848A1 (fr) Procédé de réalisation d'un processus de rétablissement de connexion rrc et appareil le prenant en charge
WO2018169319A1 (fr) Procédé de détermination de validité d'un bloc d'informations système et appareil de prise en charge dudit procédé
WO2018182224A1 (fr) Procédé de commande d'accès et dispositif de mise en œuvre dudit procédé
WO2017191994A1 (fr) Procédé et appareil de réception de bloc osi dans un système de communication sans fil
WO2017135740A1 (fr) Procédé et appareil pour la mise en œuvre de communications v2x
WO2018164528A1 (fr) Procédé de transfert de capacité d'équipement utilisateur et appareil le prenant en charge
WO2018236172A1 (fr) Procédé de réalisation de mesure et dispositif le prenant en charge
WO2019022397A1 (fr) Procédé permettant de modifier une porteuse radio dans un scénario de division d'unité cu-du
WO2018084621A1 (fr) Procédé de changement d'état de rrc de terminal, et dispositif le prenant en charge
WO2018143608A1 (fr) Procédé de demande de bloc d'informations de système et dispositif prenant en charge ledit procédé
WO2017095020A1 (fr) Procédé et appareil pour transmettre une identité d'équipement utilisateur dans un système de communication sans fil
EP3525530B1 (fr) Procédé et dispositif de configuration de zone de notification faisant appel à un réseau ran
US20190387570A1 (en) Method and device for determining rrc state
WO2017052154A1 (fr) Procédé et dispositif au moyen duquel un service d'ordre prioritaire est transmis
WO2018084592A1 (fr) Procédé et dispositif pour recevoir des données utilisateur de liaison descendante
WO2017222290A1 (fr) Procédé pour rapporter l'état de commande de ressource radio rrc d'un terminal et appareil pour le prende en charge
WO2018084589A1 (fr) Procédé et dispositif permettant de déterminer s'il faut ou non suspendre un support radio

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17858716

Country of ref document: EP

Kind code of ref document: A1