WO2018062909A1 - Procédé de gestion de zone de radiomessagerie, procédé de réalisation de radiomessagerie, et dispositif prenant en charge ces procédés - Google Patents

Procédé de gestion de zone de radiomessagerie, procédé de réalisation de radiomessagerie, et dispositif prenant en charge ces procédés Download PDF

Info

Publication number
WO2018062909A1
WO2018062909A1 PCT/KR2017/010858 KR2017010858W WO2018062909A1 WO 2018062909 A1 WO2018062909 A1 WO 2018062909A1 KR 2017010858 W KR2017010858 W KR 2017010858W WO 2018062909 A1 WO2018062909 A1 WO 2018062909A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
paging
mme
terminal
list
Prior art date
Application number
PCT/KR2017/010858
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 WO2018062909A1 publication Critical patent/WO2018062909A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • the present invention relates to a technique for managing a paging area for a terminal and performing paging using the same.
  • the higher layer standard defines the protocol state in order to manage the operation state of the terminal in detail, and shows the functions and procedures of the terminal in detail.
  • the RRC state defines the RRC_Connected state and the RRC_Idle state as the basis, and further discusses introducing the RRC_Inactive state.
  • the RRC_INACTIVE state may be a concept similar to the lightly connected mode under discussion in LTE.
  • 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.
  • the S1 (or NG1) connection of the UE is maintained and the UE context may be stored in the anchor eNB (or gNB).
  • the anchor eNB (or gNB) may set a 'paging area' for the terminal based on a cell list or a list of paging area identity (PAI). Within the page area, the terminal does not need to update its location with the anchor eNB (or gNB). A method for efficiently configuring such a paging area is proposed.
  • MME mobility management entity
  • PA paging area
  • the adjusted paging area identification list may be transmitted to the base station through an S1 setup response message or an NG1 setup response message.
  • the adjusted paging area identification list may be transmitted to the base station through a base station configuration update reception acknowledgment message.
  • the terminal may be in a lightly connected mode for the base station and the MME.
  • the mobility management entity may be an access and mobility function (AMF) of a next generation core (NGC).
  • AMF access and mobility function
  • NTC next generation core
  • the base station may be an eNB or a gNB.
  • a plurality of paging areas (PAs) supported by the base station as a mobility management entity (MME) Transmitting information relating to; Receiving a coordinated paging area identity list (coordinated-PAI list) based on the information about the plurality of paging areas from the MME; And performing paging for the terminal by using the adjusted paging area identification list, wherein the adjusted paging area identification list is created based on a plurality of paging areas received from the base station and another base station.
  • a method is provided.
  • the adjusted paging area identification list may be received to the base station via an S1 setup response message or an NG1 setup response message.
  • the adjusted paging area identification list may be received by the base station through a base station configuration update reception acknowledgment message.
  • the terminal may be in a lightly connected mode for the base station and the MME.
  • the mobility management entity may be an access and mobility function (AMF) of a next generation core (NGC).
  • AMF access and mobility function
  • NTC next generation core
  • the base station may be an eNB or a gNB.
  • a method of performing a paging for a terminal by a base station the coordinated-PAI list (coordinated-PAI list) received from a mobility management entity (MME) performing paging for the terminal based on an area identity list); And if the paging for the terminal fails, requesting the MME to perform paging for the terminal, wherein the requesting includes transmitting the adjusted paging area identification list to the MME.
  • MME mobility management entity
  • the core network may configure an efficient terminal's paging area by creating an adjusted PAI list and transmitting it to the base station.
  • 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.
  • FIG. 5 is a flowchart illustrating a paging area management method according to an embodiment of the present invention.
  • FIG. 6 is a flowchart illustrating a paging area management method according to another embodiment of the present invention.
  • FIG. 7 is a flowchart illustrating a paging area management method according to another embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a method for a base station to perform paging for a terminal according to an embodiment of the present invention.
  • FIG. 9 is a flowchart illustrating a paging area management method according to an embodiment of the present invention.
  • FIG. 10 is a block diagram of a 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 E-UTRAN system is an evolution from the existing UTRAN system and may be, for example, a 3GPP LTE / LTE-A system.
  • the E-UTRAN consists of base stations (eNBs) that provide a control plane and a user plane protocol to the terminal, and the base stations are connected through an X2 interface.
  • An X2 user plane interface (X2-U) is defined between base stations.
  • the X2-U interface provides non guaranteed delivery of user plane packet data units (PDUs).
  • An X2 control plane interface (X2-CP) is defined between two neighboring base stations.
  • X2-CP performs functions such as context transfer between base stations, control of a user plane tunnel between a source base station and a target base station, transfer of handover related messages, and uplink load management.
  • the base station is connected to the terminal through a wireless interface and is connected to the evolved packet core (EPC) through the S1 interface.
  • the S1 user plane interface (S1-U) is defined between the base station and the serving gateway (S-GW).
  • the S1 control plane interface (S1-MME) is defined between the base station and the mobility management entity (MME).
  • the S1 interface performs an evolved packet system (EPS) bearer service management function, a non-access stratum (NAS) signaling transport function, network sharing, and MME load balancing function.
  • EPS evolved packet system
  • NAS non-access stratum
  • MME mobility management entity
  • the S1 interface performs an evolved packet system (EPS) bearer service management function, a non-access stratum (NAS) signaling transport function, network sharing, and MME load
  • 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.
  • 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 AMF / 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
  • the RRC_INACTIVE state (RRC inactive state) is newly introduced in addition to the existing RRC_CONNETED state and RRC_IDLE state.
  • the RRC_INACTIVE state may be a concept similar to the lightly connected mode under discussion in LTE.
  • 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 NG2 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. On the other hand, the base station may not perform connection management for the terminal in the RRC_INACTIVE state.
  • the S1 (or NG1) connection of the UE is maintained and the UE context may be stored in the anchor eNB (or gNB).
  • the anchor eNB (or gNB) may set a 'paging area' for the terminal based on a cell list or a list of paging area identity (PAI). Within this page area, the terminal does not need to update its location with the anchor eNB (or gNB).
  • the RAN based paging area may be configured to consist of one or more cells belonging to the same or different anchor eNBs (or gNBs) connected via an X2 (or NG2) interface. If the RAN based paging area is set according to the PAI list, the anchor eNB (or gNB) must determine which of the cells in the PAI list to page.
  • a coordinated PAI list consisting of paging areas supported by a base station is provided to support a lightly connected terminal.
  • paging areas may be supported by each of the anchor eNBs (or gNBs) belonging to the MME (or next generation core CP function).
  • gNB refers to a base station in the NR
  • NG1 refers to an interface between the terminal and the CP function of the NR
  • NG2 indicates an interface between the CP function of the gNB and NG
  • NG3 indicates an interface between the terminal and the gNB
  • NG4 indicates an interface between the gNB.
  • a base station may indicate an eNB or a gNB
  • MME mobility management entity
  • AMF access and mobility function
  • NGC next generation core
  • FIG. 5 is a flowchart illustrating a paging area management method of a terminal according to an embodiment of the present invention.
  • the base station may be notified of a coordinated paging area identity list (coordinated-PAI list) adjusted by the MME.
  • this process may exchange information about a PAI list in which the RAN and the core network are coordinated in an interface setup procedure between the RAN and the core network.
  • the base station may transmit information on a paging area (PA) of the terminal to the MME.
  • the base station may transmit information about a plurality of paging areas supported by the base station.
  • each of the plurality of base stations may transmit information about one or more paging areas supported by the base station to the MME.
  • the MME may receive information about a paging area supported from each of the plurality of base stations.
  • the base station may transmit the information about the plurality of paging areas to the MME through the S1 setup request message or the NG1 setup request message.
  • the MME may transmit a coordinated paging list (coordinated paging list) to the base station.
  • the MME may prepare an adjusted PAI list based on the information about the paging area received from the plurality of base stations, and transmit the same to the base station. That is, the MME may prepare an adjusted PAI list in consideration of information on paging received from a plurality of base stations.
  • the adjusted PAI list may consist of a plurality of paging areas supported by one or more base stations.
  • the adjusted PAI list may indicate an area to which the terminal may move to perform RAN-based paging.
  • the adjusted PAI list is a concept introduced to define a RAN notification area and may be configured with an ID of the RAN area.
  • the adjusted PAI list may include all paging areas supported by a specific base station, but is not limited thereto and may include some of cells belonging to a specific base station.
  • the MME may notify an area in which the terminal may move freely as a list of cell IDs.
  • the MME may build a coordinated PAI list using tracking area identity (TAI). That is, the MME can create a coordinated PAI list by linking a paging area to each value of the TAI list.
  • TAI tracking area identity
  • the MME may configure an efficient terminal's paging area by creating an adjusted PAI list and transmitting it to the base station.
  • the MME may transmit the adjusted PAI list to the base station through the S1 setup response message or the NG1 setup response message.
  • the base station may transmit new information (updated information) to the MME as shown in FIG. 6. That is, in the present embodiment, the procedure may be initiated by the base station (RAN-triggered). Then, the MME may adjust the PAI list based on this new information, and may inform the base station that the PAI list has been successfully adjusted.
  • new information updated information
  • the base station may transmit information on a paging area (PA) of the terminal to the MME.
  • the plurality of base stations may transmit information about a plurality of paging areas supported by the base station to the MME.
  • the base station may transmit information about the plurality of paging areas to the MME through a base station configuration update message.
  • information about the paging area that does not need to be updated may also be conveyed to the MME through the base station configuration update message, and this information may be used to prepare the adjusted PAI list.
  • the MME may transmit a coordinated paging area (coordinated paging list) list to the base station.
  • the MME may prepare an adjusted PAI list based on the information about the paging area received from the base station, and transmit the same to the base station.
  • the MME may update a PAI list composed of paging areas supported by each base station based on the information about the paging area received from the plurality of base stations. The procedure for creating the adjusted PAI has already been described with reference to FIG. 5.
  • the MME may transmit the adjusted PAI list to the base station through the base station configuration update reception acknowledgment message.
  • FIG. 7 is a flowchart illustrating a paging area management method according to another embodiment of the present invention.
  • the MME may transmit the adjusted PAI list to the base station.
  • the MME may transmit the adjusted PAI list to the base station.
  • the procedure may be in the form of a CN network triggered by the MME.
  • the MME may transmit the adjusted PAI list to the base station through an MME configuration update message or an NG configuration update message.
  • the base station may transmit the MME configuration update reception report message or the NG configuration update reception report message to the MME upon successfully receiving the adjusted PAI.
  • FIG. 8 is a flowchart illustrating a method for a base station to perform paging for a terminal according to an embodiment of the present invention.
  • the base station may perform paging for the terminal.
  • the base station may perform paging based on a coordinated-PAI list (coordinated paging area identity list) received from the mobility management entity (MME). That is, the base station may define the RAN notification area using the adjusted PAI list.
  • the base station may receive the adjusted PAI list from the MME before performing the paging. Paging may be paging performed based on the RAN.
  • step S804 if paging fails for the terminal, the base station may request to perform paging for the terminal to the MME. Specifically, after the base station performs paging, if the paging response is not received from the terminal for a predetermined time, the base station may determine that the paging has failed. In this case, the base station may request to perform paging for the terminal to the MME. In addition, the base station may transmit the PAI list adjusted to the MME.
  • the MME may perform paging (CN-initiated paging) initiated by the core network based on the adjusted PAI list received from the base station. Specifically, the MME may initiate paging for a wide area such as a conventional S1 paging area with reference to the adjusted PAI list. In other words, the MME needs to know which base station or cell the PAI list adjusted to initiate paging is composed of.
  • FIG. 9 is a flowchart illustrating a paging area management method according to an embodiment of the present invention.
  • the MME may receive information about a plurality of paging areas (PAs) supported by the base stations from the plurality of base stations.
  • the terminal may be in a lightly connected mode for the base station and the MME.
  • the mobility management entity MME
  • the mobility management entity may be an Access and Mobility Function (AMF) of the Next Generation Core (NGC).
  • the base station may be an eNB or a gNB.
  • the MME may create a coordinated paging area identity list (coordinated-PAI list) based on the information about the plurality of paging areas.
  • the adjusted paging area identification list indicates an area to which the terminal can move, and may include a combination of cell IDs indicating at least one of cells corresponding to the plurality of paging areas.
  • the MME may transmit the created adjusted paging area identification list to the base station.
  • the adjusted paging area identification list may be transmitted to the base station through an S1 setup response message or an NG1 setup response message.
  • the adjusted paging area identification list may be transmitted to the base station through a base station configuration update reception acknowledgment message.
  • FIG. 10 is a block diagram of a wireless communication system in which an embodiment of the present invention is implemented.
  • the terminal 1000 includes a processor 1001, a memory 1002, and a transceiver 1003.
  • the memory 1002 is connected to the processor 1001 and stores various information for driving the processor 1001.
  • the transceiver 1003 is connected to the processor 1001 to transmit and / or receive a radio signal.
  • Processor 1001 implements the proposed functions, processes and / or methods. In the above-described embodiment, the operation of the terminal may be implemented by the processor 1001.
  • Base station 1010 includes a processor 1011, a memory 1012, and a transceiver 1013.
  • the memory 1012 is connected to the processor 1011 and stores various information for driving the processor 1011.
  • the transceiver 1013 is connected to the processor 1011 to transmit and / or receive a radio signal.
  • the processor 1011 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 1011.
  • the MME / AMF 1020 includes a processor 1021, a memory 1022, and a transceiver 1023.
  • the memory 1022 is connected to the processor 1021 and stores various information for driving the processor 1021.
  • the transceiver 1023 is coupled to the processor 1021 to transmit and / or receive wireless signals.
  • Processor 1021 implements the proposed functions, processes, and / or methods. In the above-described embodiment, the operation of the MME / AMF may be implemented by the processor 1021.
  • 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé selon lequel une entité de gestion de mobilité (MME, "mobility management entity") gère la zone de radiomessagerie d'UE dans un système de communication sans fil. Le procédé comprend les étapes consistant à : recevoir, en provenance de multiples stations de base, des informations sur de multiples zones de radiomessagerie (PA, "paging area") prises en charge par les stations de base ; élaborer une liste d'identités de zones de radiomessagerie (PAI, "PA identity") coordonnée sur la base des informations concernant les multiples PA ; et transmettre la liste de PAI coordonnée élaborée aux stations de base.
PCT/KR2017/010858 2016-09-30 2017-09-28 Procédé de gestion de zone de radiomessagerie, procédé de réalisation de radiomessagerie, et dispositif prenant en charge ces procédés WO2018062909A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662403019P 2016-09-30 2016-09-30
US62/403,019 2016-09-30

Publications (1)

Publication Number Publication Date
WO2018062909A1 true WO2018062909A1 (fr) 2018-04-05

Family

ID=61760016

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/010858 WO2018062909A1 (fr) 2016-09-30 2017-09-28 Procédé de gestion de zone de radiomessagerie, procédé de réalisation de radiomessagerie, et dispositif prenant en charge ces procédés

Country Status (1)

Country Link
WO (1) WO2018062909A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010147405A2 (fr) * 2009-06-17 2010-12-23 Samsung Electronics Co., Ltd. Procédés et appareil destiné à prendre en charge un appel à brouillage moindre dans des systèmes de communication multi-niveau
US20120196617A1 (en) * 2009-08-19 2012-08-02 Zte Corporation Method for Acquiring Adjacent eNB Information and Mobile Management Entity
KR20130094004A (ko) * 2012-02-15 2013-08-23 삼성전자주식회사 이동 통신 시스템 및 그 시스템에서 페이징 메시지 처리 방법
KR20140107354A (ko) * 2011-12-02 2014-09-04 퀄컴 인코포레이티드 저전력 기지국들을 포함하는 무선 네트워크들에서의 페이징 영역 식별자 업데이트 및 페이징을 위한 방법들 및 장치들
US20140370922A1 (en) * 2013-06-13 2014-12-18 Christopher Richards Method and apparatus of paging

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010147405A2 (fr) * 2009-06-17 2010-12-23 Samsung Electronics Co., Ltd. Procédés et appareil destiné à prendre en charge un appel à brouillage moindre dans des systèmes de communication multi-niveau
US20120196617A1 (en) * 2009-08-19 2012-08-02 Zte Corporation Method for Acquiring Adjacent eNB Information and Mobile Management Entity
KR20140107354A (ko) * 2011-12-02 2014-09-04 퀄컴 인코포레이티드 저전력 기지국들을 포함하는 무선 네트워크들에서의 페이징 영역 식별자 업데이트 및 페이징을 위한 방법들 및 장치들
KR20130094004A (ko) * 2012-02-15 2013-08-23 삼성전자주식회사 이동 통신 시스템 및 그 시스템에서 페이징 메시지 처리 방법
US20140370922A1 (en) * 2013-06-13 2014-12-18 Christopher Richards Method and apparatus of paging

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Details of Lightly Connected UEs", R2-164986, 3GPP TSG RAN WG2 MEETING #95 GOTHENBURG, 13 August 2016 (2016-08-13), Sweden, XP051134073 *

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
WO2018230983A1 (fr) Procédé d'établissement d'un rapport sur la capacité d'un ue et dispositif prenant en charge le procédé
WO2018182224A1 (fr) Procédé de commande d'accès et dispositif de mise en œuvre dudit procédé
KR101966871B1 (ko) Cu-du 분할 시나리오에서 무선 베어러를 수정하는 방법 및 장치
WO2018080218A1 (fr) Procédé et appareil d'établissement de support
WO2018008925A1 (fr) Procédé et appareil de notification de mme d'une recherche infructueuse d'un terminal
WO2018139888A1 (fr) Procédé de gestion d'un contexte de terminal et dispositif pour le prendre en charge
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
WO2017135740A1 (fr) Procédé et appareil pour la mise en œuvre de communications v2x
WO2018084621A1 (fr) Procédé de changement d'état de rrc de terminal, et dispositif le prenant en charge
US20200162953A1 (en) Method and apparatus for reporting measurement result
WO2015147615A1 (fr) Procédé et appareil pour classer par ordre de priorité une transmission de dispositif à dispositif (d2d) et une réception d2d dans un système de communication sans fil
WO2018128463A1 (fr) Procédé et dispositif d'émission/réception de données
WO2018236172A1 (fr) Procédé de réalisation de mesure et dispositif le prenant en charge
WO2018164528A1 (fr) Procédé de transfert de capacité d'équipement utilisateur et appareil le prenant en charge
WO2018097528A1 (fr) Procédé et dispositif de configuration de zone de notification faisant appel à un réseau ran
WO2018164431A1 (fr) Procédé et dispositif pour effectuer une coordination d'interférence par tranche
WO2018124693A1 (fr) Procédé de commande de flux et appareil prenant en charge ce dernier
WO2018143709A1 (fr) Procédé et dispositif de détermination d'état rrc
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
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é
WO2018084592A1 (fr) Procédé et dispositif pour recevoir des données utilisateur de liaison descendante

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

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

Country of ref document: EP

Kind code of ref document: A1