WO2016153277A1

WO2016153277A1 - Method for reporting number of terminals existing within geographical area in wireless communication system, and apparatus therefor

Info

Publication number: WO2016153277A1
Application number: PCT/KR2016/002946
Authority: WO
Inventors: 류진숙; 김재현; 김현숙; 김래영; 김태훈
Original assignee: 엘지전자(주)
Priority date: 2015-03-23
Filing date: 2016-03-23
Publication date: 2016-09-29

Abstract

Disclosed are a method for reporting the number of terminals existing within a geographical area in a wireless communication system, and an apparatus therefor. Specifically, the method for reporting the number of terminals existing within a geographical area in a wireless communication system comprises: transmitting, by a mobility management entity (MME), a paging message to a terminal via a base station, if a monitoring event for reporting the number of terminals existing within a geographical area is established; and receiving a cell identifier (cell ID) of the terminal from the base station along with a message transmitted from the terminal in response to the paging message, wherein if the paging message comprises a monitoring usage indication, a tracking area update (TAU) message can be transmitted from the terminal in response to the paging message.

Description

Method for reporting number of terminals existing in geographical area in wireless communication system and apparatus therefor

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a wireless communication system, and more particularly, to a method for reporting or supporting the number of terminals existing in a specific geographic area and an apparatus for supporting the same.

Mobile communication systems have been developed to provide voice services while ensuring user activity. However, the mobile communication system has expanded not only voice but also data service.As a result of the explosive increase in traffic, a shortage of resources and users are demanding higher speed services, a more advanced mobile communication system is required. have.

The requirements of the next generation of mobile communication systems will be able to accommodate the explosive data traffic, dramatically increase the data rate per user, greatly increase the number of connected devices, very low end-to-end latency, and high energy efficiency. It should be possible. Dual connectivity, Massive Multiple Input Multiple Output (MIMO), In-band Full Duplex, Non-Orthogonal Multiple Access (NOMA), Super Various technologies such as wideband support and device networking have been studied.

An object of the present invention is to propose a method for identifying and reporting the number of terminals existing in a specific geographic area and a method of supporting the same.

In addition, an object of the present invention is to propose a method for identifying and reporting the number of terminals in an idle mode currently located in a specific geographic area and a method of supporting the same.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned above will be clearly understood by those skilled in the art from the following description. Could be.

One aspect of the present invention is a method for reporting the number of terminals existing in a geographic area in a wireless communication system, wherein when a monitoring event for reporting the number of terminals existing in a geographic area is set, mobility A management entity (MME: Mobility Management Entity) transmitting a paging message to a terminal through a base station and receiving a cell ID (cell ID) of the terminal from the base station together with a message transmitted in response to the paging message from the terminal. And if the paging message includes a monitoring usage indication, a tracking area update (TAU) message may be transmitted from the terminal in response to the paging message.

Preferably, the method may further include storing information indicating that the paging message is a paging message for reporting the number of terminals existing in a geographic area.

Preferably, a service request message is generated in response to the paging message from a terminal in which information indicating that the paging message is a paging message for reporting the number of terminals existing in a geographical area is stored. When transmitted, the method may further include transmitting a service reject message to the terminal through the base station in response to the service request message.

Preferably, the service reject message may include a cause value of monitoring usage.

Preferably, the service request message may include information indicating whether there is data to be transmitted by the terminal to the network.

Preferably, if the service request message includes information indicating that the terminal has data to transmit to the network, a service request procedure may proceed.

Preferably, the method may further include counting and reporting a number of terminals located in a predetermined cell to the network node using the received cell ID.

Preferably, when a time period for reporting the number of terminals present in a geographic area is set when the monitoring event is set, a message is transmitted in response to the paging message in the time period. Only the number of terminals can be counted.

Another aspect of the present invention provides a method for supporting reporting of the number of terminals existing in a geographic area in a wireless communication system, the monitoring event for reporting the number of terminals existing in a geographic area by a terminal. Is set to a mobility management entity (MME), receiving a paging message from the MME through the base station and transmitting a message to the MME through the base station in response to the paging message from the MME; And a direction indicating that the paging message is monitoring usage, a tracking area update (TAU) message may be transmitted in response to the paging message.

Preferably, a service request message may be transmitted in response to the paging message.

Preferably, a service reject message may be transmitted from the MME in response to the service request message through the base station.

Preferably, if the service reject message includes a cause value of monitoring usage, the terminal may perform an idle mode operation.

According to an embodiment of the present invention, it is possible to effectively count the number of idle mode terminals currently present in a specific geographic area more accurately.

In addition, according to an embodiment of the present invention, in order to determine the number of idle mode terminals currently present in a specific geographic area, unnecessary core network signaling and user plane setup may be minimized. .

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. .

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, included as part of the detailed description in order to provide a thorough understanding of the present invention, provide embodiments of the present invention and together with the description, describe the technical features of the present invention.

1 is a view briefly illustrating an EPS (Evolved Packet System) to which the present invention can be applied.

2 shows an example of a network structure of an evolved universal terrestrial radio access network (E-UTRAN) to which the present invention can be applied.

3 illustrates the structure of an E-UTRAN and an EPC in a wireless communication system to which the present invention can be applied.

4 shows a structure of a radio interface protocol between a terminal and an E-UTRAN in a wireless communication system to which the present invention can be applied.

5 shows an S1 interface protocol structure in a wireless communication system to which the present invention can be applied.

6 is a diagram exemplarily illustrating a structure of a physical channel in a wireless communication system to which the present invention can be applied.

7 is a diagram illustrating EMM and ECM states in a wireless communication system to which the present invention can be applied.

8 illustrates a bearer structure in a wireless communication system to which the present invention can be applied.

FIG. 9 is a diagram illustrating a transmission path of a control plane and a user plane in an EMM registered state in a wireless communication system to which the present invention can be applied.

10 is a diagram illustrating an ECM connection establishment procedure in a wireless communication system to which the present invention can be applied.

11 is a diagram for explaining a contention based random access procedure in a wireless communication system to which the present invention can be applied.

12 is a diagram illustrating a terminal trigger service request procedure in a wireless communication system to which the present invention can be applied.

13 is a diagram illustrating a network trigger service request procedure in a wireless communication system to which the present invention can be applied.

14 is a diagram illustrating a paging procedure in a wireless communication system that can be applied to the present invention.

15 is a diagram briefly illustrating a periodic tracking area update procedure in a wireless communication system to which the present invention can be applied.

FIG. 16 is a diagram illustrating a Machine-Type Communication (MTC) architecture in a wireless communication system to which the present invention may be applied.

17 illustrates an architecture for service capability exposure in a wireless communication system to which the present invention can be applied.

18 illustrates a procedure for setting a monitoring event in a wireless communication system to which the present invention can be applied.

19 to 22 are diagrams illustrating a method for reporting the number of terminals existing in a geographic area according to an embodiment of the present invention.

23 illustrates a block diagram of a communication device according to an embodiment of the present invention.

24 is a block diagram of a communication device according to one embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, one of ordinary skill in the art appreciates that the present invention may be practiced without these specific details.

In some instances, well-known structures and devices may be omitted or shown in block diagram form centering on the core functions of the structures and devices in order to avoid obscuring the concepts of the present invention.

In this specification, a base station has a meaning as a terminal node of a network that directly communicates with a terminal. The specific operation described as performed by the base station in this document may be performed by an upper node of the base station in some cases. That is, it is obvious that various operations performed for communication with a terminal in a network composed of a plurality of network nodes including a base station may be performed by the base station or other network nodes other than the base station. A 'base station (BS)' may be replaced by terms such as a fixed station, a Node B, an evolved-NodeB (eNB), a base transceiver system (BTS), an access point (AP), and the like. . In addition, a 'terminal' may be fixed or mobile, and may include a user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), and an AMS ( Advanced Mobile Station (WT), Wireless Terminal (WT), Machine-Type Communication (MTC) Device, Machine-to-Machine (M2M) Device, Device-to-Device (D2D) Device, etc.

Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal and a receiver may be part of a base station.

Specific terms used in the following description are provided to help the understanding of the present invention, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present invention.

The following techniques are code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and NOMA It can be used in various radio access systems such as non-orthogonal multiple access. CDMA may be implemented by 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). OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA). UTRA is part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA, and employs OFDMA in downlink and SC-FDMA in uplink. LTE-A (advanced) is the evolution of 3GPP LTE.

Embodiments of the present invention may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802, 3GPP and 3GPP2. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.

For clarity, the following description focuses on 3GPP LTE / LTE-A, but the technical features of the present invention are not limited thereto.

Terms that can be used in this document are defined as follows.

UMTS (Universal Mobile Telecommunications System): A third generation mobile communication technology based on Global System for Mobile Communication (GSM) developed by 3GPP

Evolved Packet System (EPS): A network system consisting of an Evolved Packet Core (EPC), which is a packet switched core network based on Internet Protocol (IP), and an access network such as LTE and UTRAN. UMTS is an evolutionary network.

NodeB: base station of UMTS network. It is installed outdoors and its coverage is macro cell size.

eNodeB: base station of EPS network. It is installed outdoors and its coverage is macro cell size.

User Equipment: User Equipment. A terminal may be referred to in terms of terminal, mobile equipment (ME), mobile station (MS), and the like. In addition, the terminal may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smartphone, a multimedia device, or the like, or may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device. The term "terminal" or "terminal" in the MTC related content may refer to an MTC terminal.

IMS (IP Multimedia Subsystem): A subsystem for providing multimedia services based on IP.

International Mobile Subscriber Identity (IMSI): An internationally uniquely assigned user identifier in a mobile communications network.

Machine Type Communication (MTC): Communication performed by a machine without human intervention. It may also be referred to as M2M (Machine to Machine) communication.

MTC terminal (MTC UE or MTC device or MTC device): a terminal (eg, vending machine, etc.) having a function of communicating via a mobile communication network (for example, communicating with an MTC server via a PLMN) and performing an MTC function; Meter reading, etc.).

MTC server: A server on a network that manages an MTC terminal. It may exist inside or outside the mobile communication network. It may have an interface that an MTC user can access. In addition, the MTC server may provide MTC related services to other servers (Services Capability Server (SCS)), or the MTC server may be an MTC application server.

(MTC) application: services (e.g., remote meter reading, volume movement tracking, weather sensors, etc.)

(MTC) application server: a server on a network where (MTC) applications run

MTC feature: A function of a network to support an MTC application. For example, MTC monitoring is a feature for preparing for loss of equipment in an MTC application such as a remote meter reading, and low mobility is a feature for an MTC application for an MTC terminal such as a vending machine.

MTC User: The MTC user uses a service provided by the MTC server.

MTC subscriber: An entity having a connection relationship with a network operator and providing a service to one or more MTC terminals.

MTC group: A group of MTC terminals that share at least one MTC feature and belongs to an MTC subscriber.

Services Capability Server (SCS): An entity for communicating with an MTC InterWorking Function (MTC-IWF) and an MTC terminal on a Home PLMN (HPLMN), which is connected to a 3GPP network. SCS provides the capability for use by one or more MTC applications.

External Identifier: An identifier used by an external entity (e.g., an SCS or application server) of a 3GPP network to point to (or identify) an MTC terminal (or a subscriber to which the MTC terminal belongs). Globally unique. The external identifier is composed of a domain identifier and a local identifier as follows.

Domain Identifier: An identifier for identifying a domain in a control term of a mobile communication network operator. One provider may use a domain identifier for each service to provide access to different services.

Local Identifier: An identifier used to infer or obtain an International Mobile Subscriber Identity (IMSI). Local identifiers must be unique within the application domain and are managed by the mobile telecommunications network operator.

RAN (Radio Access Network): a unit including a Node B, a Radio Network Controller (RNC), and an eNodeB controlling the Node B in a 3GPP network. It exists at the terminal end and provides connection to the core network.

Home Location Register (HLR) / Home Subscriber Server (HSS): A database containing subscriber information in the 3GPP network. The HSS may perform functions such as configuration storage, identity management, and user state storage.

RANAP (RAN Application Part): between the RAN and the node in charge of controlling the core network (ie, Mobility Management Entity (MME) / Serving General Packet Radio Service (GPRS) Supporting Node) / MSC (Mobile Switching Center) Interface.

Public Land Mobile Network (PLMN): A network composed for the purpose of providing mobile communication services to individuals. It may be configured separately for each operator.

Non-Access Stratum (NAS): A functional layer for transmitting and receiving signaling and traffic messages between a terminal and a core network in a UMTS and EPS protocol stack. The main function is to support the mobility of the terminal and to support the session management procedure for establishing and maintaining an IP connection between the terminal and the PDN GW.

Service Capability Exposure Function (SCEF): An entity in the 3GPP architecture for service capability exposure that provides a means for securely exposing the services and capabilities provided by the 3GPP network interface.

Hereinafter, the present invention will be described based on the terms defined above.

General system to which the present invention can be applied

1 is a diagram briefly illustrating an EPS (Evolved Packet System) to which the present invention may be applied.

The network structure diagram of FIG. 1 briefly reconstructs a structure of an EPS (Evolved Packet System) including an Evolved Packet Core (EPC).

Evolved Packet Core (EPC) is a key element of System Architecture Evolution (SAE) to improve the performance of 3GPP technologies. SAE is a research project to determine network structure supporting mobility between various kinds of networks. SAE aims to provide an optimized packet-based system, for example, supporting various radio access technologies on an IP basis and providing improved data transfer capability.

Specifically, the EPC is a core network of an IP mobile communication system for a 3GPP LTE system and may support packet-based real-time and non-real-time services. In a conventional mobile communication system (i.e., a second generation or third generation mobile communication system), the core network is divided into two distinct sub-domains of circuit-switched (CS) for voice and packet-switched (PS) for data. The function has been implemented. However, in the 3GPP LTE system, an evolution of the third generation mobile communication system, the sub-domains of CS and PS have been unified into one IP domain. That is, in the 3GPP LTE system, the connection between the terminal and the terminal having the IP capability (capability), the IP-based base station (for example, eNodeB (evolved Node B)), EPC, application domain (for example, IMS) It can be configured through. That is, EPC is an essential structure for implementing end-to-end IP service.

The EPC may include various components, and in FIG. 1, some of them correspond to a Serving Gateway (SGW) (or S-GW), PDN GW (Packet Data Network Gateway) (or PGW or P-GW), A mobility management entity (MME), a Serving General Packet Radio Service (GPRS) Supporting Node (SGSN), and an enhanced Packet Data Gateway (ePDG) are shown.

The SGW acts as a boundary point between the radio access network (RAN) and the core network, and is an element that functions to maintain a data path between the eNodeB and the PDN GW. In addition, when the UE moves over the area served by the eNodeB, the SGW serves as a local mobility anchor point. That is, packets may be routed through the SGW for mobility in the E-UTRAN (Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later). SGW also provides mobility with other 3GPP networks (RANs defined before 3GPP Release-8, such as UTRAN or GERAN (Global System for Mobile Communication (GSM) / Enhanced Data rates for Global Evolution (EDGE) Radio Access Network). It can also function as an anchor point.

The PDN GW corresponds to the termination point of the data interface towards the packet data network. The PDN GW may support policy enforcement features, packet filtering, charging support, and the like. Also, untrusted networks such as 3GPP networks and non-3GPP networks (e.g., Interworking Wireless Local Area Networks (I-WLANs), trusted divisions such as Code Division Multiple Access (CDMA) networks or Wimax). It can serve as an anchor point for mobility management with the network.

Although the example of the network structure of FIG. 1 shows that the SGW and the PDN GW are configured as separate gateways, two gateways may be implemented according to a single gateway configuration option.

The MME is an element that performs signaling and control functions for supporting access to a network connection, allocation of network resources, tracking, paging, roaming, handover, and the like. The MME controls the control plane functions related to subscriber and session management. The MME manages a number of eNodeBs and performs signaling for the selection of a conventional gateway for handover to other 2G / 3G networks. The MME also performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.

SGSN handles all packet data, such as user's mobility management and authentication to other 3GPP networks (eg GPRS networks).

The ePDG acts as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).

As described with reference to FIG. 1, a terminal having IP capability includes an IP service network provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access. For example, IMS).

1 illustrates various reference points (eg, S1-U, S1-MME, etc.). In the 3GPP system, a conceptual link defining two functions existing in different functional entities of E-UTRAN and EPC is defined as a reference point. Table 1 below summarizes the reference points shown in FIG. 1. In addition to the examples of Table 1, various reference points may exist according to the network structure.

Among the reference points shown in FIG. 1, S2a and S2b correspond to non-3GPP interfaces. S2a is a reference point that provides the user plane with relevant control and mobility resources between trusted non-3GPP access and PDN GW. S2b is a reference point that provides the user plane with relevant control and mobility support between the ePDG and the PDN GW.

The E-UTRAN system is an evolution from the existing UTRAN system and may be, for example, a 3GPP LTE / LTE-A system. Communication networks are widely deployed to provide various communication services, such as voice (eg, Voice over Internet Protocol (VoIP)) over IMS and packet data.

Referring to FIG. 2, an E-UMTS network includes an E-UTRAN, an EPC, and one or more UEs. The E-UTRAN consists of eNBs providing a control plane and a user plane protocol to the UE, and the eNBs are connected through an X2 interface.

X2 user plane interface (X2-U) is defined between eNBs. 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 eNBs. X2-CP performs functions such as context transfer between eNBs, control of user plane tunnel between source eNB and target eNB, delivery of handover related messages, and uplink load management.

The eNB is connected to the terminal through a wireless interface and is connected to an evolved packet core (EPC) through the S1 interface.

The S1 user plane interface (S1-U) is defined between the eNB and the serving gateway (S-GW). The S1 control plane interface (S1-MME) is defined between the eNB 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. The S1 interface supports a many-to-many-relation between eNB and MME / S-GW.

MME provides NAS signaling security, access stratum (AS) security control, inter-CN inter-CN signaling to support mobility between 3GPP access networks, and performing and controlling paging retransmission. Idle mode UE reachability, tracking area identity (TAI) management (for children and active mode terminals), PDN GW and SGW selection, for handover with MME changes Bearer management functions including MME selection, SGSN selection for handover to 2G or 3G 3GPP access network, roaming, authentication, dedicated bearer establishment, Public Alert System (PWS) Warning System (including Earthquake and Tsunami Warning System (ETWS) and Commercial Mobile Alert System (CMAS)) support for sending messages. Can.

Referring to FIG. 3, an eNB may select a gateway (eg, MME), route to the gateway during radio resource control (RRC) activation, scheduling of a broadcast channel (BCH), and the like. Dynamic resource allocation to the UE in transmission, uplink and downlink, and may perform the function of mobility control connection in the LTE_ACTIVE state. As mentioned above, within the EPC, the gateway is responsible for paging initiation, LTE_IDLE state management, ciphering of the user plane, System Architecture Evolution (SAE) bearer control, and NAS signaling encryption. It can perform the functions of ciphering and integrity protection.

FIG. 4 (a) shows the radio protocol structure for the control plane and FIG. 4 (b) shows the radio protocol structure for the user plane.

Referring to FIG. 4, the layers of the air interface protocol between the terminal and the E-UTRAN are based on the lower three layers of the open system interconnection (OSI) standard model known in the art of communication systems. It may be divided into a first layer L1, a second layer L2, and a third layer L3. The air interface protocol between the UE and the E-UTRAN consists of a physical layer, a data link layer, and a network layer horizontally, and vertically stacks a protocol stack for transmitting data information. (protocol stack) It is divided into a user plane and a control plane, which is a protocol stack for transmitting control signals.

The control plane refers to a path through which control messages used by the terminal and the network to manage a call are transmitted. The user plane refers to a path through which data generated at an application layer, for example, voice data or Internet packet data, is transmitted. Hereinafter, each layer of the control plane and the user plane of the radio protocol will be described.

A physical layer (PHY), which is a first layer (L1), provides an information transfer service to a higher layer by using a physical channel. The physical layer is connected to a medium access control (MAC) layer located at a higher level through a transport channel, and data is transmitted between the MAC layer and the physical layer through the transport channel. Transport channels are classified according to how and with what characteristics data is transmitted over the air interface. In addition, data is transmitted between different physical layers through a physical channel between a physical layer of a transmitter and a physical layer of a receiver. The physical layer is modulated by an orthogonal frequency division multiplexing (OFDM) scheme and utilizes time and frequency as radio resources.

There are several physical control channels used at the physical layer. A physical downlink control channel (PDCCH) is a resource allocation of a paging channel (PCH) and a downlink shared channel (DL-SCH) and uplink shared channel (UL-SCH) to the UE. : informs hybrid automatic repeat request (HARQ) information related to uplink shared channel (HARQ). In addition, the PDCCH may carry an UL grant that informs the UE of resource allocation of uplink transmission. The physical control format indicator channel (PDFICH) informs the UE of the number of OFDM symbols used for PDCCHs and is transmitted every subframe. A physical HARQ indicator channel (PHICH) carries a HARQ acknowledgment (ACK) / non-acknowledge (NACK) signal in response to uplink transmission. The physical uplink control channel (PUCCH) carries uplink control information such as HARQ ACK / NACK, downlink request and channel quality indicator (CQI) for downlink transmission. A physical uplink shared channel (PUSCH) carries a UL-SCH.

The MAC layer of the second layer (L2) provides a service to a radio link control (RLC) layer, which is a higher layer, through a logical channel. In addition, the MAC layer multiplexes / demultiplexes into a transport block provided as a physical channel on a transport channel of a MAC service data unit (SDU) belonging to the logical channel and mapping between the logical channel and the transport channel. Includes features

The RLC layer of the second layer (L2) supports reliable data transmission. Functions of the RLC layer include concatenation, segmentation, and reassembly of RLC SDUs. In order to guarantee the various quality of service (QoS) required by the radio bearer (RB), the RLC layer has a transparent mode (TM), an unacknowledged mode (UM) and an acknowledgment mode (AM). There are three modes of operation: acknowledge mode. AM RLC provides error correction through an automatic repeat request (ARQ). Meanwhile, when the MAC layer performs an RLC function, the RLC layer may be included as a functional block of the MAC layer.

The packet data convergence protocol (PDCP) layer of the second layer (L2) performs user data transmission, header compression, and ciphering functions in the user plane. Header compression is relatively large and large in order to allow efficient transmission of Internet protocol (IP) packets, such as IPv4 (internet protocol version 4) or IPv6 (internet protocol version 6), over a small bandwidth wireless interface. It means the function to reduce the IP packet header size that contains unnecessary control information. The function of the PDCP layer in the control plane includes the transfer of control plane data and encryption / integrity protection.

A radio resource control (RRC) layer located at the lowest part of the third layer L3 is defined only in the control plane. The RRC layer serves to control radio resources between the terminal and the network. To this end, the UE and the network exchange RRC messages with each other through the RRC layer. The RRC layer controls the logical channel, transport channel and physical channel with respect to configuration, re-configuration and release of radio bearers. The radio bearer means a logical path provided by the second layer (L2) for data transmission between the terminal and the network. Establishing a radio bearer means defining characteristics of a radio protocol layer and a channel to provide a specific service, and setting each specific parameter and operation method. The radio bearer may be further divided into two signaling radio bearers (SRBs) and data radio bearers (DRBs). The SRB is used as a path for transmitting RRC messages in the control plane, and the DRB is used as a path for transmitting user data in the user plane.

A non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.

One cell constituting the base station is set to one of the bandwidth, such as 1.25, 2.5, 5, 10, 20Mhz to provide a downlink or uplink transmission service to multiple terminals. Different cells may be configured to provide different bandwidths.

A downlink transport channel for transmitting data from a network to a terminal includes a broadcast channel (BCH) for transmitting system information, a PCH for transmitting a paging message, and a DL-SCH for transmitting user traffic or control messages. There is this. Traffic or control messages of the downlink multicast or broadcast service may be transmitted through the DL-SCH or may be transmitted through a separate downlink multicast channel (MCH). Meanwhile, an uplink transport channel for transmitting data from a terminal to a network includes a random access channel (RACH) for transmitting an initial control message, and an UL-SCH (uplink shared) for transmitting user traffic or a control message. channel).

The logical channel is on top of the transport channel and is mapped to the transport channel. The logical channel may be divided into a control channel for transmitting control region information and a traffic channel for delivering user region information. The control channel includes a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a dedicated control channel (DCCH), multicast And a control channel (MCCH: multicast control channel). Traffic channels include a dedicated traffic channel (DTCH) and a multicast traffic channel (MTCH). PCCH is a downlink channel that carries paging information and is used when the network does not know the cell to which the UE belongs. CCCH is used by a UE that does not have an RRC connection with the network. A point-to-multipoint downlink channel used to convey multimedia broadcast and multicast service (MBMS) control information from an MCCH network to a UE. The DCCH is a point-to-point bi-directional channel used by a terminal having an RRC connection for transferring dedicated control information between the UE and the network. DTCH is a point-to-point channel dedicated to one terminal for transmitting user information that may exist in uplink and downlink. MTCH is a point-to-multipoint downlink channel for carrying traffic data from the network to the UE.

In the case of an uplink connection between a logical channel and a transport channel, the DCCH may be mapped to the UL-SCH, the DTCH may be mapped to the UL-SCH, and the CCCH may be mapped to the UL-SCH. Can be. In the case of a downlink connection between a logical channel and a transport channel, the BCCH may be mapped with the BCH or DL-SCH, the PCCH may be mapped with the PCH, and the DCCH may be mapped with the DL-SCH. The DTCH may be mapped with the DL-SCH, the MCCH may be mapped with the MCH, and the MTCH may be mapped with the MCH.

FIG. 5A illustrates a control plane protocol stack in an S1 interface, and FIG. 5B illustrates a user plane interface protocol structure in an S1 interface.

Referring to FIG. 5, the S1 control plane interface (S1-MME) is defined between the base station and the MME. Similar to the user plane, the transport network layer is based on IP transport. However, it is added to the SCTP (Stream Control Transmission Protocol) layer above the IP layer for reliable transmission of message signaling. The application layer signaling protocol is referred to as S1-AP (S1 application protocol).

The SCTP layer provides guaranteed delivery of application layer messages.

Point-to-point transmission is used at the transport IP layer for protocol data unit (PDU) signaling transmission.

A single SCTP association per S1-MME interface instance uses a pair of stream identifiers for the S-MME common procedure. Only some pairs of stream identifiers are used for the S1-MME dedicated procedure. The MME communication context identifier is assigned by the MME for the S1-MME dedicated procedure, and the eNB communication context identifier is assigned by the eNB for the S1-MME dedicated procedure. The MME communication context identifier and the eNB communication context identifier are used to distinguish the UE-specific S1-MME signaling transmission bearer. Communication context identifiers are each carried in an S1-AP message.

When the S1 signaling transport layer notifies the S1AP layer that the signaling connection is disconnected, the MME changes the state of the terminal that used the signaling connection to the ECM-IDLE state. And, the eNB releases the RRC connection of the terminal.

S1 user plane interface (S1-U) is defined between the eNB and the S-GW. The S1-U interface provides non-guaranteed delivery of user plane PDUs between the eNB and the S-GW. The transport network layer is based on IP transmission, and a GPRS Tunneling Protocol User Plane (GTP-U) layer is used above the UDP / IP layer to transfer user plane PDUs between the eNB and the S-GW.

Referring to FIG. 6, a physical channel transmits signaling and data through a radio resource including one or more subcarriers in a frequency domain and one or more symbols in a time domain.

One subframe having a length of 1.0 ms is composed of a plurality of symbols. The specific symbol (s) of the subframe (eg, the first symbol of the subframe) can be used for the PDCCH. The PDCCH carries information about dynamically allocated resources (eg, a resource block, a modulation and coding scheme (MCS), etc.).

EMM And ECM status

It looks at the status of EPS mobility management (EMM) and EPS connection management (ECM).

Referring to FIG. 7, an EMM registered state (EMM-REGISTERED) according to whether a UE is attached or detached from a network in order to manage mobility of the UE in a NAS layer located in a control plane of the UE and the MME. And an EMM deregistration state (EMM-DEREGISTERED) may be defined. The EMM-REGISTERED state and the EMM-DEREGISTERED state may be applied to the terminal and the MME.

As in the case of powering on the terminal for the first time, the initial terminal is in the EMM-DEREGISTERED state, and the terminal performs a process of registering with the corresponding network through an initial attach procedure to access the network. If the access procedure is successfully performed, the UE and the MME are transitioned to the EMM-REGISTERED state. In addition, when the terminal is powered off or the radio link fails (when the packet error rate exceeds the reference value on the wireless link), the terminal is detached from the network and transitioned to the EMM-DEREGISTERED state.

In addition, an ECM-connected state and an ECM idle state (ECM-IDLE) may be defined to manage a signaling connection between the terminal and the network. ECM-CONNECTED state and ECM-IDLE state may also be applied to the UE and the MME. The ECM connection consists of an RRC connection established between the terminal and the base station and an S1 signaling connection established between the base station and the MME. In other words, when the ECM connection is set / released, it means that both the RRC connection and the S1 signaling connection are set / released.

The RRC state indicates whether the RRC layer of the terminal and the RRC layer of the base station are logically connected. That is, when the RRC layer of the terminal and the RRC layer of the base station is connected, the terminal is in the RRC connected state (RRC_CONNECTED). If the RRC layer of the terminal and the RRC layer of the base station is not connected, the terminal is in the RRC idle state (RRC_IDLE).

The network can grasp the existence of the terminal in the ECM-CONNECTED state in units of cells and can effectively control the terminal.

On the other hand, the network cannot grasp the existence of the UE in the ECM-IDLE state, and manages the core network (CN) in a tracking area unit that is a larger area than the cell. When the terminal is in the ECM idle state, the terminal performs Discontinuous Reception (DRX) set by the NAS using an ID assigned only in the tracking area. That is, the UE may receive broadcast of system information and paging information by monitoring a paging signal at a specific paging occasion every UE-specific paging DRX cycle.

In addition, when the terminal is in the ECM-IDLE state, the network does not have context information of the terminal. Accordingly, the UE in the ECM-IDLE state may perform a terminal-based mobility related procedure such as cell selection or cell reselection without receiving a command from the network. In the ECM idle state, when the location of the terminal is different from the location known by the network, the terminal may inform the network of the location of the terminal through a tracking area update (TAU) procedure.

On the other hand, when the terminal is in the ECM-CONNECTED state, the mobility of the terminal is managed by the command of the network. In the ECM-CONNECTED state, the network knows the cell to which the UE belongs. Accordingly, the network may transmit and / or receive data to or from the terminal, control mobility such as handover of the terminal, and perform cell measurement on neighbor cells.

As described above, the terminal needs to transition to the ECM-CONNECTED state in order to receive a normal mobile communication service such as voice or data. As in the case of powering on the terminal for the first time, the initial terminal is in the ECM-IDLE state as in the EMM state, and when the terminal is successfully registered in the network through an initial attach procedure, the terminal and the MME are in the ECM connection state. Transition is made. In addition, if the terminal is registered in the network but the traffic is inactivated and the radio resources are not allocated, the terminal is in the ECM-IDLE state, and if a new traffic is generated uplink or downlink to the terminal, a service request procedure UE and MME is transitioned to the ECM-CONNECTED state through.

EPS Bearer (bearer)

When a terminal is connected to a packet date network (PDN) (peer entity in FIG. 8), a PDN connection is generated, and the PDN connection may also be referred to as an EPS session. PDN is a service provider's external or internal IP (internet protocol) network to provide service functions such as the Internet or IMS (IP Multimedia Subsystem).

EPS sessions have one or more EPS bearers. The EPS bearer is a transmission path of traffic generated between the UE and the PDN GW in order to deliver user traffic in EPS. One or more EPS bearers may be set per terminal.

Each EPS bearer may be divided into an E-UTRAN radio access bearer (E-RAB) and an S5 / S8 bearer, and the E-RAB is divided into a radio bearer (RB: radio bearer) and an S1 bearer. Can lose. That is, one EPS bearer corresponds to one RB, S1 bearer, and S5 / S8 bearer, respectively.

The E-RAB delivers the packet of the EPS bearer between the terminal and the EPC. If there is an E-RAB, the E-RAB bearer and the EPS bearer are mapped one-to-one. A data radio bearer (DRB) transfers a packet of an EPS bearer between a terminal and an eNB. If the DRB exists, the DRB and the EPS bearer / E-RAB are mapped one-to-one. The S1 bearer delivers the packet of the EPS bearer between the eNB and the S-GW. The S5 / S8 bearer delivers an EPS bearer packet between the S-GW and the P-GW.

The UE binds a service data flow (SDF) to the EPS bearer in the uplink direction. SDF is an IP flow or collection of IP flows that classifies (or filters) user traffic by service. A plurality of SDFs may be multiplexed onto the same EPS bearer by including a plurality of uplink packet filters. The terminal stores mapping information between the uplink packet filter and the DRB in order to bind between the SDF and the DRB in the uplink.

P-GW binds SDF to EPS bearer in downlink direction. A plurality of SDFs may be multiplexed on the same EPS bearer by including a plurality of downlink packet filters. The P-GW stores the mapping information between the downlink packet filter and the S5 / S8 bearer to bind between the SDF and the S5 / S8 bearer in the downlink.

The eNB stores a one-to-one mapping between the DRB and the S1 bearer to bind between the DRB and the S1 bearer in the uplink / downlink. S-GW stores one-to-one mapping information between S1 bearer and S5 / S8 bearer in order to bind between S1 bearer and S5 / S8 bearer in uplink / downlink.

EPS bearers are classified into two types: a default bearer and a dedicated bearer. The terminal may have one default bearer and one or more dedicated bearers per PDN. The minimum default bearer of the EPS session for one PDN is called a default bearer.

The EPS bearer may be classified based on an identifier. EPS bearer identity is assigned by the terminal or the MME. The dedicated bearer (s) is combined with the default bearer by Linked EPS Bearer Identity (LBI).

When the terminal initially accesses the network through an initial attach procedure, a PDN connection is generated by assigning an IP address, and a default bearer is generated in the EPS section. Even if there is no traffic between the terminal and the corresponding PDN, the default bearer is not released unless the terminal terminates the PDN connection, and the default bearer is released when the corresponding PDN connection is terminated. Here, the bearer of all sections constituting the terminal and the default bearer is not activated, the S5 bearer directly connected to the PDN is maintained, the E-RAB bearer (ie DRB and S1 bearer) associated with the radio resource is Is released. When new traffic is generated in the corresponding PDN, the E-RAB bearer is reset to deliver the traffic.

While the terminal uses a service (for example, the Internet, etc.) through a default bearer, the terminal may use an insufficient service (for example, Videon on Demand (VOD), etc.) to receive a Quality of Service (QoS) with only the default bearer. Dedicated bearer is generated when the terminal requests (on-demand). If there is no traffic of the terminal dedicated bearer is released. The terminal or the network may generate a plurality of dedicated bearers as needed.

The IP flow may have different QoS characteristics depending on what service the UE uses. The network determines the allocation of network resources or a control policy for QoS at the time of establishing / modifying an EPS session for the terminal and applies it while the EPS session is maintained. This is called PCC (Policy and Charging Control). PCC rules are determined based on operator policy (eg, QoS policy, gate status, charging method, etc.).

PCC rules are determined in units of SDF. That is, the IP flow may have different QoS characteristics according to the service used by the terminal, IP flows having the same QoS are mapped to the same SDF, and the SDF becomes a unit for applying the PCC rule.

The main entities for performing such a PCC function may be Policy and Charging Control Function (PCRF) and Policy and Charging Enforcement Function (PCEF).

PCRF determines PCC rules for each SDF when creating or changing EPS sessions and provides them to the P-GW (or PCEF). After setting the PCC rule for the SDF, the P-GW detects the SDF for each IP packet transmitted and received and applies the PCC rule for the SDF. When the SDF is transmitted to the terminal via the EPS, it is mapped to an EPS bearer capable of providing a suitable QoS according to the QoS rules stored in the P-GW.

PCC rules are divided into dynamic PCC rules and pre-defined PCC rules. Dynamic PCC rules are provided dynamically from PCRF to P-GW upon EPS session establishment / modification. On the other hand, the predefined PCC rule is preset in the P-GW and activated / deactivated by the PCRF.

The EPS bearer includes a QoS Class Identifier (QCI) and Allocation and Retention Priority (ARP) as basic QoS parameters.

QCI is a scalar that is used as a reference to access node-specific parameters that control bearer level packet forwarding treatment, and the scalar value is pre-configured by the network operator. ) For example, a scalar may be preset to any one of integer values 1-9.

The main purpose of ARP is to determine if a bearer's establishment or modification request can be accepted or rejected if resources are limited. In addition, ARP can be used to determine which bearer (s) to drop by the eNB in exceptional resource constraints (eg, handover, etc.).

The EPS bearer is classified into a guaranteed bit rate (GBR) type bearer and a non-guaranteed bit rate (non-GBR) type bearer according to the QCI resource type. The default bearer may always be a non-GBR type bearer, and the dedicated bearer may be a GBR type or non-GBR type bearer.

GBR bearer has GBR and Maximum Bit Rate (MBR) as QoS parameters in addition to QCI and ARP. MBR means that fixed resources are allocated to each bearer (bandwidth guarantee). On the other hand, the non-GBR bearer has an MBR (AMBR: Aggregated MBR) combined as a QoS parameter in addition to QCI and ARP. AMBR means that resources are not allocated for each bearer, but the maximum bandwidth that can be used like other non-GBR bearers is allocated.

If the QoS of the EPS bearer is determined as above, the QoS of each bearer is determined for each interface. Since the bearer of each interface provides QoS of the EPS bearer for each interface, the EPS bearer, the RB, and the S1 bearer all have a one-to-one relationship.

While the terminal uses the service through the default bearer, if the service is insufficient to receive the QoS provided only by the default bearer, a dedicated bearer is generated on-demand.

9 (a) illustrates the ECM-CONNECTED state, and FIG. 9 (b) illustrates the ECM-IDLE.

When the terminal successfully attaches to the network and becomes the EMM-Registered state, the terminal receives the service using the EPS bearer. As described above, the EPS bearer is configured by divided into DRB, S1 bearer, S5 bearer for each interval.

As illustrated in FIG. 9A, in the ECM-CONNECTED state in which user traffic is present, a NAS signaling connection, that is, an ECM connection (that is, an RRC connection and an S1 signaling connection) is established. In addition, an S11 GTP-C (GPRS Tunneling Protocol Control Plane) connection is established between the MME and the SGW, and an S5 GTP-C connection is established between the SGW and the PDN GW.

In addition, in the ECM-CONNECTED state, the DRB, S1 bearer, and S5 bearer are all configured (ie, radio or network resource allocation).

As shown in FIG. 9B, in the ECM-IDLE state in which there is no user traffic, the ECM connection (that is, the RRC connection and the S1 signaling connection) is released. However, the S11 GTP-C connection between the MME and the SGW and the S5 GTP-C connection between the SGW and the PDN GW are maintained.

In addition, in the ECM-IDLE state, both the DRB and the S1 bearer are released, but the S5 bearer maintains the configuration (ie, radio or network resource allocation).

Referring to FIG. 10, the UE transmits an RRC Connection Request message to the eNB in order to request an RRC connection (S1001).

The RRC Connection Request message includes a UE ID (eg, SAE temporary mobile subscriber identity (S-TMSI) or random ID) and an establishment cause.

The establishment cause may be a NAS procedure (e.g., attach, detach, tracking area update, service request, extended service request). It depends on.

The eNB transmits an RRC Connection Setup message to the UE in response to the RRC Connection Request message (S1002).

After receiving the RRC Connection Setup message, the terminal transitions to the RRC_CONNECTED mode.

The terminal transmits an RRC Connection Setup Complete message to the eNB in order to confirm successful completion of RRC connection establishment (S1003).

The terminal transmits the NAS message (eg, an initial attach message, a service request message, etc.) to the eNB in the RRC Connection Setup Complete message.

The eNB obtains a Service Request message from the RRC Connection Setup Complete message and delivers it to the MME through an initial UE message, which is an S1AP message (S1004).

The control signal between the base station and the MME is transmitted through the S1AP message in the S1-MME interface. The S1AP message is delivered for each user through the S1 signaling connection, and the S1 signaling connection is defined by an identifier pair (ie, eNB UE S1AP ID and MME UE S1AP ID) allocated by the base station and the MME to identify the UE.

The eNB allocates an eNB UE S1AP ID to an Initial UE message and transmits it to the MME. The MME receives an Initial UE message and allocates an MME S1AP UE ID to establish an S1 signaling connection between the eNB and the MME.

Random Access Procedure

Hereinafter, a random access procedure provided by the LTE / LTE-A system will be described.

The random access procedure is used for the terminal to obtain uplink synchronization with the base station or to receive uplink radio resources. After the terminal is powered on, the terminal acquires downlink synchronization with the initial cell and receives system information. From the system information, a set of available random access preambles and information about radio resources used for transmission of the random access preambles are obtained. The radio resource used for the transmission of the random access preamble may be specified by a combination of at least one subframe index and an index on the frequency domain. The terminal transmits a random access preamble selected randomly from the set of random access preambles, and the base station receiving the random access preamble sends a timing alignment (TA) value for uplink synchronization to the terminal through a random access response. As a result, the terminal acquires uplink synchronization.

The random access procedure is a common procedure in frequency division duplex (FDD) and time division duplex (TDD). The random access procedure is irrelevant to the cell size, and is independent of the number of serving cells when carrier aggregation (CA) is configured.

First, a case where the UE performs a random access procedure may be as follows.

When the terminal performs an initial access in the RRC idle state because there is no RRC connection with the base station

When performing the RRC connection re-establishment procedure

When the UE first accesses the target cell during the handover process

When the random access procedure is requested by the command of the base station

In case of data to be transmitted in downlink during non-synchronized uplink time synchronization during RRC connection state

When there is data to be transmitted on the uplink in a situation in which the uplink time synchronization is not synchronized (non-synchronized) during the RRC connection state or when a designated radio resource used for requesting a radio resource is not allocated.

In the case of performing positioning of the UE in a situation in which timing advance is needed during the RRC connection state

When performing recovery process in case of radio link failure or handover failure

In 3GPP Rel-10, a common consideration is to apply a timing advance (TA) value applicable to one specific cell (eg, a Pcell) to a plurality of cells in a wireless access system supporting carrier aggregation. However, the UE may merge a plurality of cells belonging to different frequency bands (that is, largely spaced on the frequency) or a plurality of cells having different propagation characteristics. In addition, in the case of a specific cell, a small cell or a secondary base station such as a remote radio header (RRH) (ie, a repeater), a femto cell, or a pico cell may be used to expand coverage or remove coverage holes. In a situation where a secondary eNB (SeNB: secondary eNB) is disposed in a cell, the terminal communicates with a base station (ie, macro eNB) through one cell, and when communicating with a secondary base station through another cell, Cells may have different propagation delay characteristics. In this case, when uplink transmission using one TA value in a common manner may be seriously affected in synchronization of uplink signals transmitted on a plurality of cells. Therefore, it may be desirable to have a plurality of TAs in a CA situation in which a plurality of cells are merged. In 3GPP Rel-11, it is considered that an TA is independently allocated to a specific cell group unit to support multiple TAs. do. This is called a TA group (TAG: TA group). The TAG may include one or more cells, and the same TA may be commonly applied to one or more cells included in the TAG. In order to support such multiple TAs, a MAC TA command control element is composed of a 2-bit TAG identifier (TAG ID) and a 6-bit TA command field.

When the UE for which carrier aggregation is configured performs the random access procedure described above with respect to the PCell, the UE performs the random access procedure. In the case of a TAG (ie, a pTAG: primary TAG) to which a Pcell belongs, all cell (s) in the pTAG are replaced with a TA determined based on the Pcell or adjusted through a random access procedure accompanying the Pcell. Applicable to On the other hand, in the case of a TAG (ie, sTAG: secondary TAG) composed only of S cells, a TA determined based on a specific S cell in the sTAG may be applied to all cell (s) in the sTAG, where TA is a base station. Can be obtained by a random access procedure. Specifically, in the sTAG, the SCell is configured as an RACH resource, and the base station requests an RACH access from the SCell to determine the TA. That is, the base station initiates the RACH transmission on the S cells by the PDCCH order transmitted in the P cell. The response message for the SCell preamble is transmitted through the PCell using a random access radio network temporary identifier (RA-RNTI). The UE may apply the TA determined based on the SCell that has successfully completed the random access to all cell (s) in the corresponding sTAG. As such, the random access procedure may be performed in the SCell to obtain a timing alignment of the sTAG to which the SCell belongs.

In the LTE / LTE-A system, in the process of selecting a random access preamble (RACH preamble), a contention-based random access procedure in which the UE randomly selects and uses one preamble within a specific set And a non-contention based random access procedure using a random access preamble allocated by a base station only to a specific terminal. However, the non- contention based random access procedure may be used only for the terminal positioning and / or the timing advance alignment for the sTAG when requested by the above-described handover procedure, a command of the base station. After the random access procedure is completed, general uplink / downlink transmission occurs.

Meanwhile, a relay node (RN) also supports both a contention-based random access procedure and a contention-free random access procedure. When the relay node performs a random access procedure, it suspends the RN subframe configuration at that point. In other words, this means temporarily discarding the RN subframe configuration. Thereafter, the RN subframe configuration is resumed when the random access procedure is completed successfully.

(1) first message (Msg 1, message 1)

First, the UE randomly selects one random access preamble (RACH preamble) from a set of random access preambles indicated through system information or a handover command, and A physical RACH (PRACH) resource capable of transmitting a random access preamble is selected and transmitted.

The random access preamble is transmitted in 6 bits in the RACH transmission channel, and the 6 bits are 5 bits of a random identity for identifying the UE transmitting the RACH, and 1 bit (eg, a third for indicating additional information). Message (indicating the size of Msg 3).

The base station receiving the random access preamble from the terminal decodes the preamble and obtains an RA-RNTI. The RA-RNTI associated with the PRACH in which the random access preamble is transmitted is determined according to the time-frequency resource of the random access preamble transmitted by the corresponding UE.

(2) a second message (Msg 2, message 2)

The base station transmits a random access response addressed to the RA-RNTI obtained through the preamble on the first message to the terminal. The random access response includes a random access preamble identifier (RA preamble index / identifier), an uplink grant (UL grant) indicating an uplink radio resource, a temporary cell identifier (TC-RNTI), and a time synchronization value ( TAC: time alignment commands) may be included. The TAC is information indicating a time synchronization value that the base station sends to the terminal to maintain uplink time alignment. The terminal updates the uplink transmission timing by using the time synchronization value. When the terminal updates the time synchronization, a time alignment timer is started or restarted. The UL grant includes an uplink resource allocation and a transmit power command (TPC) used for transmission of a scheduling message (third message), which will be described later. TPC is used to determine the transmit power for the scheduled PUSCH.

After the UE transmits the random access preamble, the base station attempts to receive its random access response within the random access response window indicated by the system information or the handover command, and PRACH The PDCCH masked by the RA-RNTI corresponding to the PDCCH is detected, and the PDSCH indicated by the detected PDCCH is received. The random access response information may be transmitted in the form of a MAC packet data unit (MAC PDU), and the MAC PDU may be transmitted through a PDSCH. The PDCCH preferably includes information of a terminal that should receive the PDSCH, frequency and time information of a radio resource of the PDSCH, a transmission format of the PDSCH, and the like. As described above, once the UE successfully detects the PDCCH transmitted to the UE, the UE can properly receive the random access response transmitted to the PDSCH according to the information of the PDCCH.

The random access response window refers to a maximum time period in which a terminal that transmits a preamble waits to receive a random access response message. The random access response window has a length of 'ra-ResponseWindowSize' starting from subframes after three subframes in the last subframe in which the preamble is transmitted. That is, the UE waits to receive a random access response during the random access window obtained after three subframes from the subframe in which the preamble is terminated. The terminal may acquire a random access window size ('ra-ResponseWindowsize') parameter value through system information, and the random access window size may be determined as a value between 2 and 10.

If the terminal successfully receives a random access response having the same random access preamble identifier / identifier as the random access preamble transmitted to the base station, the monitoring stops the random access response. On the other hand, if the random access response message is not received until the random access response window ends, or if a valid random access response having the same random access preamble identifier as the random access preamble transmitted to the base station is not received, the random access response is received. Is considered to have failed, and then the UE may perform preamble retransmission.

As described above, the reason why the random access preamble identifier is needed in the random access response is that the UL grant, the TC-RNTI, and the TAC are used by any terminal because one random access response may include random access response information for one or more terminals. This is because we need to know if it is valid.

(3) third message (Msg 3, message 3)

When the terminal receives a valid random access response to the terminal, it processes each of the information included in the random access response. That is, the terminal applies the TAC, and stores the TC-RNTI. In addition, by using the UL grant, the data stored in the buffer of the terminal or newly generated data is transmitted to the base station. In the case of initial access of the UE, an RRC connection request generated in the RRC layer and delivered through the CCCH may be included in the third message and transmitted. The RRC connection reestablishment request delivered through the RRC connection reestablishment request may be included in the third message and transmitted. It may also include a NAS connection request message.

The third message should include the identifier of the terminal. In the contention-based random access procedure, it is not possible to determine which terminals perform the random access procedure in the base station, because the terminal needs to be identified for future collision resolution.

There are two methods for including the identifier of the terminal. In the first method, if the UE has a valid cell identifier (C-RNTI) allocated in the corresponding cell before the random access procedure, the UE transmits its cell identifier through an uplink transmission signal corresponding to the UL grant. do. On the other hand, if a valid cell identifier has not been allocated before the random access procedure, the UE transmits its own unique identifier (eg, S-TMSI or random number). In general, the unique identifier is longer than the C-RNTI.

Terminal specific scrambling is used for transmission on the UL-SCH. If the UE is assigned a C-RNTI, scrambling is performed based on the C-RNTI, but if the UE is not yet assigned a C-RNTI, scrambling cannot be based on the C-RNTI and is instead received in a random access response. One TC-RNTI is used. If the UE transmits data corresponding to the UL grant, it starts a timer for contention resolution (contention resolution timer).

(4) Fourth message (Msg 4, message 4)

When the base station receives the C-RNTI of the terminal through the third message from the terminal, the base station transmits a fourth message to the terminal using the received C-RNTI. On the other hand, when the unique identifier (ie, S-TMSI or random number) is received from the terminal through the third message, the fourth message is transmitted using the TC-RNTI allocated to the terminal in the random access response. Send to the terminal. For example, the fourth message may include an RRC connection setup message.

After transmitting the data including its identifier through the UL grant included in the random access response, the terminal waits for an instruction of the base station to resolve the collision. That is, it attempts to receive a PDCCH to receive a specific message. There are two methods for receiving the PDCCH. As mentioned above, when the third message transmitted in response to the UL grant is its C-RNTI, it attempts to receive the PDCCH using its C-RNTI, and the identifier is a unique identifier (that is, In the case of S-TMSI or a random number, it attempts to receive the PDCCH using the TC-RNTI included in the random access response. Then, in the former case, if the PDCCH is received through its C-RNTI before the conflict resolution timer expires, the terminal determines that the random access procedure has been normally performed, and terminates the random access procedure. In the latter case, if the PDCCH is received through the TC-RNTI before the conflict resolution timer expires, the data transmitted by the PDSCH indicated by the PDCCH is checked. If the unique identifier is included in the content of the data, the terminal determines that the random access procedure is normally performed, and terminates the random access procedure. The terminal acquires the C-RNTI through the fourth message, and then the terminal and the network transmit and receive a terminal-specific message using the C-RNTI.

The following describes a method for conflict resolution in random access.

The reason for collision in performing random access is basically because the number of random access preambles is finite. That is, since the base station cannot grant the UE-specific random access preamble to all the UEs, the UE randomly selects and transmits one of the common random access preambles. Accordingly, when two or more terminals select and transmit the same random access preamble through the same radio resource (PRACH resource), the base station determines that one random access preamble is transmitted from one terminal. For this reason, the base station transmits a random access response to the terminal and predicts that the random access response will be received by one terminal. However, as described above, since collision may occur, two or more terminals receive one random access response, and thus, each terminal performs an operation according to reception of a random access response. That is, a problem occurs in that two or more terminals transmit different data to the same radio resource by using one UL Grant included in the random access response. Accordingly, all of the data transmission may fail, or only the data of a specific terminal may be received at the base station according to the location or transmission power of the terminals. In the latter case, since both of the two or more terminals assume that the transmission of their data was successful, the base station should inform the terminals that have failed in the competition information about the fact of the failure. That is, contention of failure or success of the competition is called contention resolution.

There are two methods of conflict resolution. One method is to use a contention resolution timer, and the other is to transmit an identifier of a successful terminal to the terminals. The former case is used when the terminal already has a unique C-RNTI before the random access procedure. That is, the terminal already having the C-RNTI transmits data including its C-RNTI to the base station according to the random access response, and operates the collision resolution timer. When the PDCCH information indicated by the C-RNTI is received before the conflict resolution timer expires, the UE determines that the UE has succeeded in the competition and ends the random access normally. Conversely, if the PDCCH indicated by its C-RNTI has not been transmitted before the conflict resolution timer expires, it is determined that it has failed in the race, and the random access procedure is performed again or failed to a higher layer. Can be informed. The latter case of the collision resolution method, that is, a method of transmitting an identifier of a successful terminal is used when the terminal does not have a unique cell identifier before the random access procedure. That is, when the UE itself does not have a cell identifier, the UE transmits data including an identifier higher than the cell identifier (S-TMSI or random number) according to UL Grant information included in the random access response, and the UE operates a collision resolution timer. Let's do it. Before the conflict resolution timer expires, if data including its higher identifier is transmitted to the DL-SCH, the terminal determines that the random access procedure is successful. On the other hand, if the conflict resolution timer is not expired, if the data including its higher identifier is not transmitted to the DL-SCH, the UE is determined that the random access process has failed.

Meanwhile, unlike the contention-based random access procedure illustrated in FIG. 11, the random access procedure is terminated by only transmitting the first message and transmitting the second message. However, before the terminal transmits the random access preamble to the base station as the first message, the terminal is allocated a random access preamble from the base station, and transmits the allocated random access preamble to the base station as a first message, and sends a random access response from the base station. The random access procedure is terminated by receiving.

Service Request Procedure

The UE-triggered Service Request procedure is generally performed when the UE intends to initiate a new service by initiation.

1-2. The UE initiates a UE-triggered Service Request procedure by sending a Service Request message to the MME.

The Service Request message is included in the RRC Connection Setup Complete message in the RRC connection and transmitted, and is included in the Initial UE message in the S1 signaling connection.

3. The MME requests and receives information for authentication from the HSS for terminal authentication, and performs mutual authentication with the terminal.

4. The MME transmits an Initial Context Setup Request message to the base station so that the base station eNB can configure the S-GW and the S1 bearer and set up the UE and the DRB.

5. The base station transmits an RRC connection reconfiguration message to the terminal to generate a DRB.

After completing this procedure, the generation of the DRB between the base station and the terminal is completed, all uplink EPS bearer is configured from the terminal to the P-GW. The terminal may transmit uplink traffic to the P-GW.

6. The base station transmits an initial context setup complete message including the 'S1 eNB TEID' to the MME in response to the initial context setup request message.

7. The MME delivers the 'S1 eNB TEID' received from the base station to the S-GW through a Modify Bearer Request message.

After completing this procedure, the generation of the downlink S1 bearer between the base station and the S-GW is completed, so that all the downlink EPS bearers are configured from the P-GW to the UE. The terminal may receive downlink traffic from the P-GW.

8. If the cell in which the UE is located (E-UTRAN Cell Global Identifier (ECGI) or Tracking Area (TAI)) is changed, the S-GW sends a P-Modify Bearer Request (Modify Bearer Request) message. Notify by sending to GW.

9. If necessary, the P-GW may perform a PCRF and IP connectivity access network (IP-CAN) session modification procedure.

10. If the P-GW receives a Modify Bearer Request message from the S-GW, the P-GW sends a Modified Bearer Response message to the S-GW in response.

11. The S-GW sends a Modify Bearer Response message to the MME in response to the Modify Bearer Request message.

A network-triggered service request procedure is generally performed when a downlink data is to be transmitted to a UE in an ECM-IDLE state in a network.

1. When downlink data reaches the P-GW from an external network, the P-GW forwards the downlink data to the S-GW.

2. If the downlink S1 bearer is released (ie, ECM-IDLE state) and thus cannot transmit downlink data to the eNB (ie, there is no 'S1 eNB TEID' value in the S-GW), The S-GW buffers the received downlink data. The S-GW transmits a downlink data notification message to the MME / SGSN in which the UE is registered for signaling connection and bearer setup for the UE.

The MME / SGSN transmits a downlink data notification ACK message to the S-GW in response to the downlink data notification message.

3. The MME / SGSN transmits a paging message to all eNB / RNC (or BSC (base station controller)) belonging to the tracking area which the terminal has most recently registered.

4. When the eNB / RNC (or BSC) receives a paging message from the MME / SGSN, the eNB / RNC (or BSC) broadcasts a paging message.

5. When the UE recognizes that there is downlink data directed to the UE, it performs a service request procedure and establishes an ECM connection. That is, in this case, the service request procedure is initiated by paging transmitted from the network.

The service request procedure may be performed in the same manner as the procedure of FIG. 12. When the procedure is completed, the UE may receive downlink data from the S-GW.

6. When the paging response is received, the S-GW sends a "Stop Paging" message to the MME / SGSN.

When the MME / SGSN commands paging transmission to the eNB / RNC (or BSC) or cells, the eNB / RNC (or BSC) is a paging occasion through the IMSI value and the DRX cycle of the terminal. Calculate and transmit the paging message at the corresponding paging occasion. If there is no response from the UE for a certain time to the paging transmission, the MME may consider the paging transmission failure and may command paging retransmission to the eNB / RNC (or BSC) or cells.

That is, the paging retransmission is determined when the MME terminal does not receive a service request from the terminal. The paging retransmission does not supervise or do not retransmit the paging. When the MME transmits paging to a large number of cells, since the UE transmits a service request belonging to one of the cells, the eNB transmits a service request to the cell if there is no response to paging. You will judge that it is not located.

Meanwhile, when the MME / SGSN does not receive a response from the terminal even after the paging repetition / retransmission procedure, the MME / SGSN notifies the S-GW of the paging failure by using a downlink data notification reject message.

If a Downlink Data Notification Reject message is received, the S-GW may delete the buffered packet (s).

Paging

The paging procedure may be used to transmit paging information to a UE in RRC_IDLE mode in a network, or to notify a UE in RRC_IDLE / RRC_CONNECTED mode of a change in system information or in RRC_IDLE / RRC_CONNECTED mode. It is used to inform the UE of ETWS primary notification and / or ETWS secondary notification, or to inform the UE of CMAS notification in RRC_IDLE / RRC_CONNECTED mode.

Referring to FIG. 14, the MME initiates a paging procedure by transmitting an S1AP paging message to the base station (S1401).

As described above, the location of the UE in the ECM-IDLE state is managed by the MME based on a tracking area (TA). In this case, since the UE may be registered in one or more TAs, the MME may transmit a PAGING message to a plurality of eNBs covering a cell belonging to the TA (s) in which the UE is registered. Here, each cell may belong to only one TA, and each eNB may include cells belonging to different TAs.

Here, the MME transmits a paging message to each eNB through the S1AP interface (or S1AP protocol). Hereinafter, this is referred to as an 'S1AP PAGING message' (or paging request).

Table 2 illustrates the S1AP PAGING message.

Referring to Table 2, the IE / Group Name indicates the name of an information element (IE) or an information element group (IE group). 'M' in the presence field indicates an IE / IE group always included in the message as mandatory IE, and 'O' is an optional IE and may or may not be included in the message. / IE group, 'C' represents a conditional (IE) IE / IE group included in the message only when a specific condition is satisfied. The Range field indicates the number of repetitive IEs / IE groups that can be repeated.

The IE type and reference field indicates the type of the IE (eg, enumerated data (ENUMERATED), integer (INTEGER), octet string (OCTET STRING), etc.) and the value that the IE can have. If a range exists, a range of values is shown.

The Criticality field indicates criticality information applied to the IE / IE group. The criticality information refers to information indicating how to operate at the receiver when the receiver does not understand all or a part of the IE / IE group. '-' Indicates that criticality information is not applied, and 'YES' indicates that criticality information is applied. 'GLOBAL' indicates that one of the criticality information is common to the repetition of the IE and the IE. 'EACH' indicates that each of the repetitions of the IE has unique criticality information. The assigned Criticality field indicates actual criticality information.

The information element (IE) or IE group included in the S1AP PAGING message will be described in more detail as follows.

Message Type IE uniquely identifies the message being sent.

UE Identity Index value IE is used by an eNB to calculate a paging frame (PF) (eg, UE Identity Index = UE IMSI mod 1024).

UE Paging Identity IE is an identifier for identifying a paged terminal and is indicated by one of IMSI and SAE Temporary Mobile Subscriber Identity (S-TMSI). S-TMSI means an identifier capable of uniquely identifying a terminal in one MME group.

In general paging, S-TMSI is used as the terminal paging identifier. On the other hand, when IMSI is used as the terminal paging identifier, this is paging with IMSI. When the terminal receives paging with the IMSI value, the terminal performs a re-attach procedure.

Paging DRX IE is used to calculate a paging frame (PF) at the base station when the terminal uses a terminal-specific DRX cycle length. The UE may specify the DRX cycle length in an Attach Request message or a Tracking Area Update (TAU) message.

CN Domain IE indicates whether paging occurred in a Circuit Switched (CS) domain or a Packet Switched (PS) domain.

The Tracking Area Identifier Tracking Area Identity (TAI List) IE is used to inform the base station of a TA to which a paging message should be broadcast. TAI means an identifier used to uniquely identify a TA.

Closed Subscriber Group (CSG) Identifier List (CSG ID List) IE indicates a CSG set to which a terminal is subscribed. This prevents the base station from paging to the terminal in the CSG cell to which the terminal is not subscribed.

Paging Priority IE indicates paging priority for paging a terminal.

UE Radio Capability for Paging IE includes paging specific terminal radio capability information.

The eNB that receives the S1AP paging message from the MME configures a paging message (hereinafter referred to as an 'RRC Paging message' (or paging information)).

Table 3 illustrates the RRC Paging message.

Referring to Table 3, a single RRC paging message may carry information of multiple S1AP paging messages. That is, the RRC paging message may include multiple paging records (eg, 16) for paging multiple terminals.

Each paging record includes a terminal identifier (ue-Identity) field and a CN domain (cn-Domain) field. This is the content delivered from the S1AP Paging message.

The systemInfoModification field is not transmitted from the S1AP Paging message and is generated by the base station. This field is used to trigger the terminal to re-acquire a set of system information blocks (SIBs).

The Extended Access Barring (EAB) Parameter Change (eab-ParamModification) field is used to indicate EAB parameter (SIB 14) change.

The ETWS-Indication field is not delivered from the S1AP Paging message and is generated by the base station. This field applies only to an ETWS capable UE and is used to trigger the UE to reacquire SIB 1. SIB 1 content indicates the ETWS content in the SIB 10 and SIB 11 to the terminal.

The CMAS Indication field is applied only to a CMAS capable UE and is used to trigger the UE to reacquire SIB 1. SIB 1 content indicates to the terminal the CMAS content in SIB 12.

The eNB configuring the RRC paging message as described above transmits downlink control information (DCI) attached with a cyclic redundancy check (CRC) scrambled with P-RNTI (Paging-RNTI) from the PDCCH to the UE (S1402), and the RRC paging message Is transmitted to the terminal through the PDSCH (S1403).

That is, the base station delivers an RRC paging message to the terminal through a PCCH logical channel, a PCH transport channel, and a PDSCH physical channel.

In more detail, the base station determines the PDCCH format according to the DCI to be sent to the terminal, and attaches the CRC to the DCI. In the CRC, a radio network temporary identifier (RNTI) is scrambled (or masked) according to an owner or a purpose of the PDCCH. If the PDCCH is for a specific UE, a unique identifier (eg, C-RNTI (cell-RNTI)) of the UE may be masked to the CRC. Alternatively, if the PDCCH is for a paging message, a paging indication identifier (for example, p-RNTI (p-RNTI)) may be masked to the CRC.

That is, the UE monitors the PDCCH based on the P-RNTI in a subframe belonging to its paging occasion 1412. When the PDCCH masked with the P-RNTI is detected, the terminal decodes the DCI transmitted on the PDCCH. This DCI indicates the PDSCH resource to which the paging message is transmitted to the UE. The terminal decodes the RRC paging message from the PDSCH resource indicated by the DCI.

The paging cycle 1413 may be determined cell-specifically and may also be UE-specifically determined. In addition, a paging occasion 1412 is determined for each terminal based on its paging cycle 1413 and its identifier (ie, IMSI). Therefore, the paging message is not transmitted to all the terminals at the possible paging occasion 1411 possible at the base station, but is transmitted according to the paging occasion of the corresponding terminal. The paging timing will be described later in more detail.

The paging procedure may be used for not only receiving a mobile terminated (MT) call from each terminal, but also for changing system information, receiving a cell broadcast message (that is, receiving an ETWS / CAMS alert message), or notifying EAB of a change. have.

One of the paging records included in the RRC paging message contains a UE identity (e.g., IMSI or S-TMSI) (that is, the paging procedure is used for MT call purposes). In the RRC_IDLE mode, the UE initiates a random access procedure to establish an RRC connection with the network (for example, to transmit a service request).

In addition, when the system information modification (systemInfoModification) is included in the RRC paging message, the terminal reacquires the required system information using a system information acquisition procedure.

In addition, when an ETWS indication (etws-Indication) is included in the RRC paging message and the terminal supports ETWS, the terminal immediately reacquires SIB 1. That is, the terminal does not wait until the next system information change period boundary. If the scheduling information list (schedulingInfoList) included in SIB 1 indicates that SIB 10 exists, the terminal acquires SIB 10 based on the scheduling information (schedulingInfor). In addition, when a scheduling information list (schedulingInfoList) included in SIB 1 indicates that SIB 11 exists, the terminal acquires SIB 11 based on scheduling information (schedulingInfor).

In addition, when the RRC paging message includes a CMAS indication (cmas-Indication), and the terminal supports the CMAS, the terminal immediately reacquires SIB 1. That is, the terminal does not wait until the next system information change period boundary. When the scheduling information list (schedulingInfoList) included in SIB 1 indicates that SIB 12 exists, the terminal acquires SIB 12 based on the scheduling information (schedulingInfor).

As described above, when the RRC paging message includes a cell broadcast message (ie, an ETWS / CAMS message) indication, the UE receives SIB 10, SIB 11, and SIB 12 with reference to schedulingInfoList of SIB 1. The received SIB 10, SIB 11, SIB 12 is delivered to the upper layer (eg, RRC layer) of the terminal. In the upper layer of the terminal, if a message identifier belonging to the cell broadcast message transmitted through SIB 10, SIB 11, and SIB 12 is included in the search list of the terminal, it is displayed on the terminal. Discard it.

In addition, when the UE in RRC_IDLE mode supports EAB and the ERC parameter change (eab-ParamModification) field is included in the RRC paging message, the UE considers that previously stored SIB 14 is not valid and immediately reacquires SIB 1. . That is, the terminal does not wait until the next system information change period boundary. The terminal reacquires SIB 14 using a system information acquisition procedure.

Hereinafter, a paging occasion will be described.

3GPP LTE / LTE-A system defines a discontinuous reception (DRX) technique of the terminal in order to minimize the power consumption of the terminal.

The UE using the DRX monitors whether a paging message is transmitted only at one paging occasion every paging cycle (ie, DRX cycle).

One paging frame (PF) refers to one radio frame that may include one or more paging time point (s).

One paging point (PO) refers to one subframe in which there may be a P-RNTI transmitted on a PDCCH addressing a paging message. That is, a paging occasion is defined as a specific subframe in the PF in which the UE checks the paging message.

PF and PO are determined using the IMSI and DRX values of the terminal. The UE may calculate PF and PO using its IMSI and DRX values. In addition, the eNB can also calculate the PF and PO for each terminal through the IMSI value received from the MME.

The DRX parameter (ie, paging / PCCH configuration information) may be included in the common radio resource configuration ('RadioResourceConfigCommon') IE, which is an RRC message used to specify common radio resource configuration, and transmitted. The common radio resource configuration IE may be transmitted through an RRC message such as an RRC connection reconfiguration message or an SI message. The SI message is a message used to transmit one or more SIBs.

In addition, the UE may request its DRX cycle through an Attach Request or a Tracking Area Update Request message. In this case, the DRX cycle length set that can be requested by the UE is the same as the length set used in the system information.

Table 4 illustrates PCCH configuration information in the common radio resource configuration IE.

Referring to Table 4, the PCCH configuration information includes a 'defaultPagingCycle' field indicating a basic paging cycle length, a 'nB' parameter for obtaining a paging frame and a paging time.

The 'defaultPagingCycle' field may be set to any one of {rf32, rf64, rf128, rf256} as the default paging cycle length. rf means a radio frame, and the number after rf represents the number of radio frames. For example, if 'defaultPagingCycle' = rf32, the paging default cycle consists of 32 radio frames. If 'defaultPagingCycle' = rf64, the paging default cycle consists of 64 radio frames.

The value of the 'nB' parameter is indicated in multiples of 'T' (4T, 2T, T, T / 2, T / 4, T / 8, T / 16 or T / 32). For example, if 'nB' = fourT, the value of the 'nB' parameter is 4 * T. If 'nB' = quarterT, the value of the 'nB' parameter is T / 4.

Here, 'T' represents a DRX cycle of the terminal. 'T' is determined to be the shortest value among UE specific DRX cycles (when allocated by the upper layer) and a basic DRX cycle ('defaultPagingCycle' field value) broadcast in system information. If the UE-specific DRX cycle is not set by the higher layer, it is determined as the basic DRX cycle.

PF is determined according to Equation 1 below.

In Equation 1, N represents min (T, nB), and UE_ID represents (IMSI mod 1024).

The UE does not monitor all subframes of the PF determined as described above, and monitors only the subframes identified by the PO determined according to Equation 2 and Table 5 (or Table 6) below.

In Equation 2, Ns represents max (1, nB / T).

Table 5 illustrates a subframe pattern for determining PO in FDD.

Table 6 illustrates a subframe pattern for determining PO in TDD.

The subframe index corresponding to the PO is determined by applying the i_s value determined in Equation 2 to Tables 5 and 6 above. That is, the terminal monitors only the subframe corresponding to the PO in the determined PF.

For example, if the DRX cycle of the terminal is 320ms (that is, 32 radio frames = rf32), the radio frame 4 and the radio frame 36, ... may be determined as PF based on Equation 1 above. In this case, the UE monitors the paging message only in subframe 9 of radio frame 4 and subframe 9 of radio frame 36, which are determined POs, based on Equation 2 and Table 5 (or Table 6).

Periodic TAU Procedure

The tracking area update (TAU) procedure is performed when the UE in ECM-IDLE state attempts to register a new location or when the TAU timer elapses.

1-2. When the TAU timer of the UE in the ECM-IDLE state has elapsed, a periodic TAU (P-TAU) procedure for reporting a tracking area (TA) to the MME is triggered.

The UE initiates the P-TAU procedure by sending a TAU Request message to the MME.

The TAU Request message is included in the RRC Connection Setup Complete message in the RRC connection and transmitted, and is included in the Initial UE message in the S1 signaling connection.

3. The MME receiving the TAU Request message resets the TAU timer, modifies bearer request including the E-UTRAN Cell Global Identifier (ECGI) and the TAI. request) Send a message to the S-GW.

4-5. When the cell (ECGI) or tracking area (TAI) where the UE is located is changed, the S-GW sends a notification to the P-GW by sending a Modify Bearer Request message.

The P-GW performs an EPS session modification procedure and transmits a Modify Bearer Response message to the S-GW in response to a Modify Bearer Request message.

6. The S-GW sends a Modify Bearer Response message to the MME in response to the Modify Bearer Request message.

7-8. The MME transmits a TAU Accept message to the UE in response to the TAU Request message.

The TAU Accept message may include a TAU timer or the like.

The TAU Accept message is included in the Downlink NAS Transport message in the S1 signaling connection and transmitted, and is included in the DL Information Transfer message in the RRC connection.

9. After completing the location update of the terminal, the MME releases the connection with the terminal used for periodic TAU-related message transmission and reception to the base station eNB to release the user context set in the E-UTRAN. Context Release Command) message.

10. The base station deletes the context of the terminal and releases the resources allocated to the terminal. The base station releases an RRC connection release message to the terminal by transmitting an RRC connection release message.

11. The base station transmits a UE context release complete message to the MME in response to the UE context release command message, thereby releasing the S1 signaling connection between the base station and the MME.

After this procedure, the UE transitions back to the ECM-IDLE state.

DRX (Discontinuous Reception) mode

In the 3GPP LTE / LTE-A system, an ECM connection (ECM (EPS connection management))-CONNECTED state and an ECM idle (ECM-IDLE) state are defined to manage a signaling connection between a terminal and a network. The ECM connection state and the ECM idle state may also be applied to the terminal and the MME. The ECM connection consists of an RRC connection established between the terminal and the base station and an S1 signaling connection established between the base station and the MME. The RRC state indicates whether the RRC layer of the terminal and the RRC layer of the base station are logically connected. That is, when the RRC layer of the terminal and the RRC layer of the base station is connected, the terminal is in an RRC_CONNECTED state. If the RRC layer of the terminal and the RRC layer of the base station is not connected, the terminal is in the RRC idle (RRC_IDLE) state.

Here, the RRC_CONNECTED state refers to a state in which the terminal can receive service in units of cells while the terminal is connected to a specific cell, and the terminal is managed in units of cells.

In the RRC_IDLE state, the terminal does not have a connection with a base station and maintains only a connection with a mobility management entity (MME), and the terminal is managed in a tracking area (TA) unit that is larger than a cell. . That is, the RRC_IDLE state terminal wakes up intermittently and monitors a paging channel (PCH) in order to check whether there is a paging message transmitted to it. That is, the terminal performs a discontinuous reception (DRX) set by a non-access stratum (NAS) using a uniquely assigned ID in the tracking area. The terminal may receive a broadcast of system information and paging information by monitoring a paging signal at a particular paging opportunity every terminal-specific paging DRX cycle. Through such a network state definition, a terminal without active services can minimize its power consumption and the base station can efficiently use resources.

As described above, the terminal needs to transition to the ECM connection state in order to receive a normal mobile communication service such as voice or data. As in the case of powering on the terminal for the first time, the initial terminal is in the ECM idle state, and when the terminal successfully registers with the corresponding network through an initial attach procedure, the terminal and the MME transition to the ECM connected state. . In addition, if the terminal is registered in the network but the traffic is deactivated and the radio resources are not allocated, the terminal is in the ECM idle state, and if new uplink or downlink traffic is generated in the terminal, a service request procedure is performed. The UE and the MME are transitioned to the ECM connected state.

The 3GPP LTE / LTE-A system defines a sleep mode and an active mode even in the RRC_CONNECTED state in order to minimize power consumption of the UE.

This allows the terminal to enter the Dormant mode while maintaining the cell connection as long as there is no data transmitted / received for a predetermined time in the RRC_CONNECTED state terminal. Dormant mode terminal must wake up intermittently to monitor the physical control channel to receive data that can be transmitted to it.

As such, the wireless communication system uses a discontinuous reception (DRX) technique of the terminal to minimize the power of the terminal.

The DRX defined in the 3GPP LTE / LTE-A system can be used in both the human mode and the RRC_IDLE state of the terminal, and the DRX technique used for each state is as follows.

1) Human mode in RRC_CONNECTED state

Short DRX: short DRX cycle (2ms ~ 640ms)

Long DRX: long DRX cycle (10ms ~ 2560ms)

2) RRC_IDLE status

Paging DRX: paging DRX cycle (320ms to 2560ms)

The UE may monitor the PDCCH based on an RNTI (eg, C-RNTI, SI-RNTI, P-RNTI, etc.) which is a unique identifier of the UE.

Monitoring of the PDCCH can be controlled by the DRX operation, the parameters related to the DRX is transmitted by the base station to the terminal by the RRC message. In particular, the UE should always receive the SI-RNTI, P-RNTI and the like regardless of the DRX operation configured by the RRC message. Here, the remaining PDCCHs except for the PDCCH scrambled with C-RNTI are always received through a common search space of the main serving cell (eg, P cell).

If the terminal has a DRX parameter configured in the RRC connected state, the terminal performs discontinuous monitoring on the PDCCH based on the DRX operation. On the other hand, if the DRX parameter is not configured, the UE monitors the continuous PDCCH.

That is, the UE searches for the PDCCH by performing blind decoding in a UE-specific search space in the PDCCH region based on the DRX operation. When the UE unmasks the CRC of the PDCCH using the RNTI, if the CRC error is not detected, the UE determines that the corresponding PDCCH transmits its control information.

Discontinuous PDCCH monitoring may mean that the UE monitors the PDCCH only in a specific subframe, and continuous PDCCH monitoring may mean that the UE monitors the PDCCH in all subframes. On the other hand, if PDCCH monitoring is required in a DRX independent operation such as a random access procedure, the UE monitors the PDCCH according to the requirements of the corresponding operation.

In addition, as described above, the terminal receiving the paging message may perform DRX for the purpose of reducing power consumption.

To this end, the network configures a plurality of paging occasions (paging occasions) for each time period called a paging cycle, a specific terminal receives a paging message only at a time of a specific paging opportunity, and a terminal at a time other than the specific paging opportunity. Do not receive a paging channel. In addition, one paging opportunity may correspond to one TTI.

Extended DRX (eDRX) extends the existing maximum 2.56ms paging DRX cycle from minutes to minutes to minimize the power consumption of the terminal. to be. The eDRX may be applied to an idle mode and a connected mode.

In the case of the UE supporting the eDRX mode, an unreachable state of the UE may mean an unreachable state (that is, a DRX interval in which the UE does not monitor a paging channel) by paging.

In contrast, in the case of a terminal supporting the eDRX mode, the accessible state of the terminal is immediately accessible to the terminal by the ECM-CONNECTED mode and / or paging (that is, the terminal monitors a paging channel). Section).

In other words, the eDRX may determine that the DRX interval is relatively longer than the normal DRX mode and thus may not be temporarily accessible even in the idle interval. In other words, support for generic DRX (2.56 seconds) enables data delivery up to 2.56 seconds, but with eDRX (10 minutes), instantaneous data delivery is not possible because the maximum delay is 10 minutes. It can be considered to be practically unreachable.

Power Saving mode (Power Saving Mode)

Power Saving Mode (PSM) is one of 3GPP Release-12 (rel-12) advanced MTC (Enhancements for MTC) features, which allows the terminal to receive paging and mobility management. A function that minimizes power consumption of a terminal by defining a period in which all access stratum (AS) operations are disabled, that is, a terminal supporting PSM is updated with an attach and tracking area. At the time of (TAU), the network agrees or is provided with an active time and a periodic TAU timer (P-TAU).

When receiving the Active Time value in the network, the UE receives the paging by maintaining the ECM-IDLE state for the corresponding Active Time when the switch from ECM-CONNECTED to ECM-IDLE. When the Active Time expires, the PSM enters into the PSM and stops all AS (Access Stratrum) operations.

In addition, the MME starts an active timer with an Active Time value whenever the UE enters the ECM-IDLE mode. When the active timer expires, the MME infers that the terminal is unreachable.

That is, the active time means a time for which a terminal supporting a state using a power saving function (eg, a power saving mode (PSM), etc.) maintains an ECM-IDLE (or RRC_IDLE) state.

When the UE expires the periodic TAU timer, the UE enables the AS operation again and performs the TAU, and the network stops the implicit detach timer of the UE. The UE may wake up whenever desired for a mobile originated call (eg, uplink data packet transfer).

On the other hand, for a mobile terminated call (eg, downlink data packet receiving), the user wakes up every P-TAU cycle to perform a TAU, and during this time, the paging reception operation is performed. After executing, it enters PSM mode again and sleeps.

MTC Machine-Type Communication

An end-to-end application between a terminal (or MTC terminal) used for MTC and an MTC application may use services provided by the 3GPP system and optional services provided to the MTC server. . The 3GPP system may provide transport and communication services (including 3GPP bearer services, IMS and SMS) including various optimizations to facilitate MTC.

FIG. 16 illustrates that a terminal used for MTC is connected to a 3GPP network (UTRAN, E-UTRAN, GERAN, I-WLAN, etc.) through a Um / Uu / LTE-Uu interface. The architecture of FIG. 16 includes various MTC models (Direct Model, Indirect Model, Hybrid Model).

First, the entities shown in FIG. 16 will be described.

In FIG. 16, an application server is a server on a network on which an MTC application is executed. For the MTC application server, the above-described technology for implementing various MTC applications may be applied, and a detailed description thereof will be omitted. In addition, in FIG. 16, the MTC application server may access the MTC server through the reference point API, and a detailed description thereof will be omitted. Alternatively, the MTC Application Server may be collocated with the MTC Server.

An MTC server (eg, the SCS server of FIG. 16) is a server on a network managing an MTC terminal and may be connected to a 3GPP network to communicate with terminals and PLMN nodes used for MTC.

The MTC-Interworking Function (MTC-IWF) manages the interworking between the MTC server and the operator core network and may serve as a proxy for the MTC operation. In order to support the MTC indirect or hybrid model, the MTC-IWF can relay or interpret the signaling protocol on the reference point Tsp to activate certain functions in the PLMN. The MTC-IWF performs the functions of authenticating the MTC server before the MTC server establishes communication with the 3GPP network, authenticating the control plane request from the MTC server, and various functions related to trigger instructions described below. can do.

Short Message Service-Service Center (SMS-SC) / Internet Protocol Short Message GateWay (IP-SM-GW) may manage transmission and reception of SMS. The SMS-SC may be responsible for relaying, storing, and transmitting a short message between an Short Message Entity (SME) (an entity that transmits or receives a short message) and a terminal. The IP-SM-GW may be in charge of protocol interaction between the IP-based terminal and the SMS-SC.

The charging data function (CDF) / charging gateway function (CGF) may perform an operation related to charging.

The HLR / HSS may function to store subscriber information (IMSI, etc.), routing information, configuration information, and the like and provide the MTC-IWF.

The MSC / SGSN / MME may perform a control function such as mobility management, authentication, resource allocation, etc. for the UE's network connection. In connection with the triggering described below, a function of receiving a trigger instruction from the MTC-IWF and processing the message in the form of a message provided to the MTC terminal may be performed.

The Gateway GPRS Support Node (GGSN) / Serving-Gateway (S-GW) + Packet Date Network-Gateway (P-GW) may function as a gateway that manages the connection between the core network and the external network.

Table 7 summarizes the main reference points in FIG.

In Table 7, one or more reference points of T5a, T5b, and T5c are referred to as T5.

On the other hand, user plane communication with the MTC server in the case of indirect and hybrid models, and communication with the MTC application server in the case of direct and hybrid models may be performed using existing protocols through reference points Gi and SGi. .

Specific matters related to the contents described with reference to FIG. 16 may be incorporated in this document by referring to 3GPP TS 23.682 document (incorporated by reference).

The architecture for Service Capability Exposure illustrated in FIG. 17 allows the 3GPP network to securely expose its services and capabilities provided by the 3GPP network interface to external third party service provider applications. Makes it possible to do

Service Capability Exposure Function (SCEF) is a key entity within the 3GPP architecture for service capability exposure that provides a means to securely expose the services and capabilities provided by the 3GPP network interface. )to be. In other words, the SCEF is a key entity for providing a service function belonging to a trust domain operated by a mobile communication operator. SCEF provides an API interface to third party service providers and provides 3GPP service functions to third party service providers through connection with various entities of 3GPP. SCEF functionality may be provided by the SCS.

If the Tsp function may be exposed through an application program interface (API), the MTC-IWF may be co-located with the SCEF. A protocol (eg DIAMETER, RESTful APIs, XML over HTTP, etc.) is selected to specify a new 3GPP interface depending on multiple arguments, where multiple arguments are used to facilitate the disclosure of the requested information or the specific interface. Including but not limited to necessity.

Monitoring Enhancements (MONTE) refers to items that provide a convenience function for third party MTC operators to remotely monitor their MTC terminals. That is, when a third party service provider registers a desired monitoring event as an SCEF through an application server, the SCEF may report whether an event has occurred to the AS when the corresponding event occurs.

3GPP defines the following monitoring events for MTC monitoring.

1) Roaming Status, Serving Network (Roaming Status, and Serving Network of the UE)

2) Location of the UE

3) Change in association of the MTC Device and UICC

4) Loss of connectivity

5) UE Reachability

6) Communication Failure

7) Reporting the number of UEs present in a certain area

In particular, in the case of reporting the number of UEs present in a certain area, the corresponding UE is monitored via MME / SGSN and HSS solution as follows. The monitoring event is configured for, and the monitoring result of the monitoring event can also be reported.

3GPP TR 23.789 defines the reporting of the number of UEs present in a certain area as follows.

Monitoring event: reporting the number of UEs present in a geographic area

When requested to generate a onetime report for terminal (s) located in a geographic area, the SCEF may determine the geographic area of the cell (s) and / or RA (s) / TA (s). Map with a list and identify the MME (s) / SGSN (s) serving that cell (s) and / or RA (s) / TA (s).

The SCEF requests such MME (s) / SGSN (s) via a direct new interface to count the terminal (s) in these cell (s) and / or RA (s) / TA (s).

SCS / AP (i.e., Application Service Provider (ASP)) specifies.

Mapping of serving provider (ie, Mobile Network Operator (MNO)) network lists of specific geographic area and cell (s) and / or RA (s) / TA (s), and associated serving nodes (Eg, MME (s) / SGSN (s)) is set in the SCEF.

If the list contains cell (s) and the request is for a last know location, then the MME (s) / SGSN (s) indicate that the last known location indicates that cell (s). Collect all terminal (s) indicated. If the list includes RA (s) / TA (s), the MME (s) / SGSN (s) collects all terminal (s) registered in that RA (s) / TA (s).

If the list includes cell (s) and the request is for a current location, the MME (s) / SGSN (s) may be paging within these cell (s) to identify terminal (s) that are not already connected. )do.

For already connected terminal (s), the MME (s) / SGSN (s) queries the RAN to receive the current cell of the terminal. The MME (s) / SGSN (s) report the counting results to the SCEF. The SCEF combines reports from all involved MME (s) / SGSN (s) and reports the total sum to the SCS / AS.

Method for reporting the number of terminals existing in the geographical area

The above-described monitoring event (that is, reporting the number of terminals present in the geographic area) performs a paging procedure to acquire information on the cell (s) to which the terminal belongs, not to transmit data to the terminal. .

In other words, in order to count and report the number of UEs belonging to a specific cell (s), the MME / SGSN must wake up the UE in an idle mode. However, in this case, the E-RAB setup procedure is unnecessary because the terminal is not intended for data transmission by switching to the ECM_CONNECTED mode.

However, in the conventional method, when the terminal receives the paging, the terminal transmits a service request, and accordingly, a user plane setup procedure is performed.

As such, when paging is transmitted to count the number of terminals, all terminals existing in the corresponding geographic area perform a user plane setup through a service request procedure. ) May be wasted as well as signaling congestion.

Currently, the 3GPP study group defines the following procedure as a method for setting monitoring events.

1. The SCS / AS requests a monitoring request that includes a setting for a specific monitoring event such as a monitoring event ID, related parameters, a monitoring event priority, a monitoring destination node, and the like. Send a Monitoring Request message to the SCEF.

2. The SCEF checks that the SCS / AS is authorized to send the monitoring request and that the SCS has not exceeded the quota or rate for submitting the monitoring request. If this check fails, the SCEF sends a Monitoring Response message containing a cause value indicating the reason for the failure condition, at which point the procedure is aborted.

3. The SCEF sends to the HSS a Monitoring Request message that includes detailed information about the monitoring event setup (eg, Monitoring Event ID). The SCEF stores a Monitoring Event ID, a Monitoring Destination Node and possibly other parameters.

4. The HSS verifies the monitoring event information. For option A, the monitoring event is set in the HSS as part of the terminal subscription data.

5. The HSS sends a Monitoring Response to the SCEF when the Monitoring Request is accepted. For option B, the HSS includes the address (s) of the serving node (s).

6. The SCEF forwards the Monitoring Response to the SCS / AS. If the cause value received from the HSS is not allowed by the SCS / AS to monitor the event or the terminal or there is no valid subscription information, then the cause value indicating the reason for the failure condition ( A confirmation message containing a cause value is delivered, and the procedure ends at this step.

(For option A) 7. Based on the type of event configuration requested, the HSS determines the destination node for the monitoring event. For example, in the case of monitoring event setting in the MME, the HSS sends a message including the monitoring event data to the MME. The UE may be registered in both the MME and SGSN, in which case a Submit Request is sent to both nodes. Submit Request indicates a target address (eg, HSS or SCEF) for monitoring event setup and event reporting.

8. When the SGSN / MME receives a Submit Request, it sets up a monitoring event by creating a monitoring setup context. The MME / SGSN confirms the submission of the monitoring request. The monitoring configuration context is stored as part of the terminal context. Target addresses for event reporting (eg HSS or SCEF) are also stored in the monitoring configuration context.

(For option B) 7. Based on the type of event configuration requested, the SCEF uses the information received from the SCS and the HSS or other information to determine the destination node for the monitoring event. For example, in the case of monitoring event setting (or active / inactive) in the MME, the SCEF sends a message containing the monitoring event data to the MME. The UE may be registered in both the MME and SGSN, in which case a Submit Request is sent to both nodes. Submit Request indicates a target address (eg, SCEF address) for monitoring event setup and event reporting.

8. When the SGSN / MME receives a Submit Request, it sets up a monitoring event by creating a monitoring setup context. The MME / SGSN confirms the submission of the monitoring request. If the monitoring event setting is specific to the terminal, the monitoring setting context is stored as part of the terminal context. The SCEF address is also stored in the monitoring configuration context. In order for the target SGSN / MME to know the monitoring event triggered by the Mobility Management (MM) procedure and perform the corresponding action (e.g., monitoring event reporting, etc.), the monitoring set context is the mobility procedure (e.g. Exchanged between SGSN / MME (s) during Handover (HO) / Tracking Area Update (TAU) / Routing Area Update (RAU).

9. The serving node is set up for monitoring.

10. If the MME / SGSN deletes the monitoring context of the terminal due to the purge of the terminal, the HSS may know that the monitoring context of the corresponding terminal is deleted when the purge message is received. For option A, no signaling is performed in this situation.

11. For option B, the serving node may instruct the target address for event reporting (eg, SCEF) to delete the subscribed monitoring event.

As described in the procedure of FIG. 18 described above, a corresponding monitoring event may be set in the MME / SGSN.

In this case, when the AS / SCS requests a monitoring request, the following parameters other than the event type (for example, an event for reporting the number of terminals existing in the geographic area) are included in the monitoring request message. Is being discussed.

In a monitoring event that reports the number of terminal (s) present in the geographic area, "parameters1" indicates whether the monitoring request is for a current location or last known location (Last). Known Location), and also indicates the corresponding geographic area. Only one time report requests are supported.

If the current location is indicated by the parameter 1, the MME / SGSN will send paging to all the terminal (s) to determine the actual location of the terminal (s).

On the other hand, if the last known location (Last Known Location) is indicated by the parameter 1, the MME / SGSN uses the last known cell information, and will not transmit paging to all the terminal (s). .

The SCEF maps a geographic area with a list of cell (s) and / or a list of Routing Area Identifier (RAI) / Tracking Area Identifier (TAI) (s). . The SCEF then determines the node address of the routing area (RA) / tracking area (TA) (s) to service the corresponding cell (s) and / or RA (s) / TA (s). ) / SGSN (s).

The SCEF requests the identified MME (s) / SGSN (s) via a direct new interface to count the terminal (s), which request may be made by the cell (s) and / or RA (s) / TA (s). It contains a list and "parameters5" indicating the current / last known location.

Mapping of geographic area and cell (s) and / or serving provider (ie, Mobile Network Operator (MNO)) network lists of cell (s) and / or RA (s) / TA (s), and associated serving nodes ( For example, the identifier of MME (s) / SGSN (s)) is set in the SCEF.

If the request is for a last know location of granularity or a request for RA / TA granularity, the MME (s) / SGSN (s) is the last stored MME / SGSN. Known cell or RA / TA registration information collects all terminal (s) indicating the requested location.

When not necessarily reported to the MME / SGSN every time the cell location changes, the last known location (last known location) may be derived from the current location of the terminal.

On the other hand, if the request is for a current location on a cell level basis, the MME (s) / SGSN (s) transmit paging in these cells to identify terminals that are not already connected. For terminal (s) already connected, the MME (s) / SGSN (s) need to query the RAN to receive the current cell of the terminal.

For example, when there is no paging response from the terminal depending on the applied paging strategy and the coverage condition of the terminal or when the terminal is not reachable as the terminal applies a power saving function. For this reason the MME / SGSN may miss some terminal (s).

The MME (s) / SGSN (s) report the counting results to the SCEF. The SCEF combines reports from all involved MME (s) / SGSN (s) and reports the total sum to the SCS / AS.

As described above, even when using parameters 1 (parameters 1) and 5 (parameters 5) under discussion, in case of a request for a current location, the MME / SGSN counts and reports the number of UEs belonging to a specific cell (s). In order to transmit the paging to the terminal in the idle mode (Idle mode). As a result, the problem of resource waste and signaling congestion caused by the service request procedure is not solved.

Accordingly, the present invention proposes a method for effectively reporting the number of terminals in a specific geographic area while minimizing unnecessary core network (CN) signaling and user plane setup (CN) procedures.

That is, the MME / SGSN is not for downlink data transmission to the terminal, but for the reason for acquiring cell (s) information (ie, the number of terminals located in the cell) in a specific geographic area. In the case of transmitting a message, the following procedure is proposed.

In a monitoring event that reports the number of terminal (s) present in a geographic area, the MME / SGSN is located in the TAU / RAU containing the area (eg, cell (s)) for which reporting is desired. If the UE in idle mode is present in the corresponding TAU / RAU, the paging transmission is performed in all cell (s) belonging to the corresponding TAU / RAU.

In this case, when the terminal indicated as a stationary UE in the subscriber information is in the idle mode, the location of the terminal is the last known cell of the terminal. ) And may exclude paging transmission to the corresponding terminal.

When the MME / SGSN determines paging transmission, the triggering condition of the paging is not the user data setup, but the cell location (that is, the number of terminals existing in a specific geographic area). Information may be stored and / or indicated through paging.

Example One

The present invention proposes a method of adding an indicator (for example, a monitoring usage indicator) indicating that the paging message is a paging message for a monitoring event of reporting the number of terminals in a specific region. By adding a monitoring usage indicator, the UE may perform TAU / RAU instead of a service request in response to receiving a paging message. Through this, the MME may acquire a Cell ID (Cell ID) (eg, an E-UTRAN Cell Global Identifier (ECGI) or a Cell Global Identifier (CGI)) of the corresponding UE.

This will be described in detail with reference to the drawings below.

19 is a diagram illustrating a method for reporting the number of terminals existing in a geographic area according to an embodiment of the present invention.

Referring to FIG. 19, when the MME / SGSN is configured through SCEF to report the number of current UEs belonging to a specific cell (s), a cell requiring a count of the number of UEs ( The paging message is transmitted through the base station to the terminal in the idle mode among the terminals belonging to the TAU / RAU included in the (S1901, S1902).

In this case, the paging message may include an indication of monitoring usage of the paging message.

Here, the monitoring usage indication is one of the indicators for indicating that the corresponding paging message is for a monitoring event called 'Reporting the number of UEs present in a certain area'. It is merely an example, and may be referred to by another name or an indicator previously defined.

In addition, the MME / SGSN indicates information indicating that the paging message transmitted to the terminal is a paging message for location reporting (or location monitoring usage) (that is, 'the And indication information for indicating that the information is for a monitoring event called 'Reporting the number of UEs present in a certain area'.

As described above, the MME / SGSN may transmit an S1AP paging message (or paging request) to the base station through the S1AP interface (or S1AP protocol), and the base station that receives the S1AP paging message from the MME / SGSN may receive the RRC. A paging message (or paging information) may be configured and transmitted to the terminal.

According to the procedure of FIG. 18 illustrated above, a monitoring event for reporting on the number of current terminals belonging to a specific cell (s) may be set in the MME / SGSN. Here, the submit request message illustrated in FIG. 18 may be referred to as another name (eg, a monitoring request).

If a monitoring usage indication is included in the paging message received from the MME / SGSN through the base station, the terminal performs a TAU / RAU procedure (S1903).

That is, when the terminal receives a paging message including a monitoring usage indication, the terminal may transmit a TAU / RAU request message to the MME / SGSN through the base station in response.

In this case, when the terminal receives a paging message including a monitoring usage indication, the terminal performs a TAU / RAU procedure instead of performing a conventional service request procedure, and corresponds to an operation (for example, TAU timer reset, etc.).

In step S1904, the TAU procedure of FIG. 15 may be identically applied. In other words, when relocation of the MME / S-GW is required, an operation corresponding thereto may be performed.

In more detail, the NAS layer of the terminal configures a TAU / RAU request message, and the TAU / RAU request message is an RRC message (for example, an RRC connection setup complete message). It can be included in the transmission to the base station.

The base station includes a cell identifier of a cell to which the corresponding UE belongs (ie, a cell to which the UE transmits a TAU / RAU request message) together with a TAU / RAU request message received from the UE. (Cell ID) (eg, ECGI, CGI, etc.) may be transmitted to the MME.

That is, the base station may include a TAU / RAU request message received from the terminal in an S1AP message (eg, an initial UE message) and transmit the same to the MME. In this case, the S1AP message may include a cell identifier (Cell ID) of the cell to which the terminal belongs.

The MME obtains a cell identifier (Cell ID) of the terminal (S1905).

Here, the MME / SGSN obtains a cell identifier of the corresponding terminal through the S1AP message received from the base station, thereby counting the number of terminals located in the cell (s) requiring a count of the number of terminals, and counting the number of terminals. The number may be reported to the network node (eg SCEF).

In this case, since the TAU / RAU procedure is completed by the step S1904, both the TAU timer and the UE reachability timer are reset.

Through the above procedure, the terminal receiving the paging for reporting the number of terminals in a specific geographic area performs a tracking area update procedure rather than a service request procedure differently from the existing one. Signaling in the core network and unnecessary E-RAB setup procedures can be minimized.

Example 2

Unlike the first embodiment, the UE may transmit a service request in response to the paging message received from the MME / SGSN. However, in the present invention, even when the MME / SGSN transmits a paging message to obtain a cell ID through monitoring, even if the MME / SGSN is in a normal operation, the service rejection is performed in response to the service request message. ) Proposes a method for transmitting a message to a terminal.

In this case, a new cause value of performing a service reject may be added as a monitoring usage.

In the case of a current service reject message, only a cause for a case in which the terminal is not able to operate normally such as an abnormal operation or congestion is defined. According to each cause (cause), the terminal does not camp (camping) for the corresponding PLMN for a certain period or normal operation in the corresponding Cell / TA is impossible for a certain time. In the present invention, however, when the MME / SGSN transmits a service rejection message, an additional user plane setup is performed after acquiring a cell ID of the terminal, rather than processing the abnormal operation as described above. In order to prevent the UE from performing a procedure and an unnecessary initial context setup procedure, a terminal is required to perform a new Mobile Oriented (MO), TAU, and Mobile Terminated (MT) procedure. A cause value is required.

As such, by adding the cause value of the monitoring usage to the service reject message, the terminal can normally perform the idle mode procedure after receiving the service reject message. have.

This will be described in detail with reference to the drawings below.

20 is a diagram illustrating a method for reporting the number of terminals existing in a geographic area according to an embodiment of the present invention.

Referring to FIG. 20, when the MME / SGSN is configured through SCEF to report the current number of UEs belonging to a specific cell (s), the MME / SGSN needs a count of the number of UEs ( S), and transmits a paging message to the terminal in the idle mode (idle mode) of the terminal belonging to the TAU / RAU through the base station (S2001, S2002).

In this case, the MME / SGSN indicates information indicating that the paging message transmitted to the terminal is a paging message for location reporting (or location monitoring usage) (that is, the number of terminals existing in a specific region. And reporting information for indicating that the information is for a reporting event (Reporting the number of UEs present in a certain area).

When the terminal receives a paging message from the MME / SGSN through the base station (S2003), the terminal sends a service request (Service Request) message to the MME / SGSN through the base station in response (S2004).

In this case, the UE may transmit information to the MME / SGSN by including information indicating whether there is data to be transmitted to the network (that is, there is data to be transmitted or there is no data to be transmitted) in a service request message. In view, the NAS layer of the terminal configures a service request message and includes a service request message in an RRC message (eg, an RRC connection setup complete message) to the base station. Can transmit

In addition, the base station includes a cell identifier (Cell ID) of a cell to which the terminal belongs (ie, a cell to which the terminal transmits a service request message) together with a service request message received from the terminal. , ECGI, CGI, etc.) may be transmitted to the MME.

That is, the base station may include a service request message received from the terminal in an S1AP message (eg, an initial UE message) and transmit it to the MME. In this case, the S1AP message may include a cell identifier (Cell ID) of the cell to which the terminal belongs.

The MME / SGSN obtains a cell identifier (Cell ID) of the terminal.

In addition, the MME / SGSN confirms whether information indicating that the paging message transmitted to the terminal in step S2001 is a paging message for location reporting (or location monitoring usage) is stored / indicated. (S2005).

If the MME / SGSN receives a service request message in response to a paging message from a terminal in which location reporting (or location monitoring usage) is indicated / stored, The service reject message is transmitted to the terminal through the base station by including the monitoring usage as a value (S2006).

That is, the MME / SGSN receives a cell ID (eg, ECGI, CGI, etc.) when a service request message is received from a terminal that stores / indicates that the corresponding paging is for cell location. After acquiring, the UE transmits a service reject message by including a new cause value for the corresponding UE.

Monitoring usage Cause value means that the MME monitors a "Location report" (ie, "Reporting the number of UEs present in a certain area"). Used to perform monitoring events for reporting on events. When receiving a Service Reject message including this cause value, the terminal may perform a normal idle mode procedure.

The new cause value (named for monitoring purposes in the present invention) described above may be referred to by other names, such as location acquisition usage, and may also be used for other purposes than the above. However, even in this case, the terminal may perform an idle mode procedure after receiving a service reject message including the cause value.

If the service request message received in step S2004 includes information indicating that the terminal has data to be transmitted to the network, the MME / SGSN will accept the received service request message. Can be. That is, in this case, even if a service request message is received in response to the paging message from the terminal where location reporting (or location monitoring usage) is indicated / stored, The procedure after step 5. illustrated in FIG. 13 may be performed.

When the terminal includes the monitoring usage as a cause value in the received Service Reject message, the terminal considers the normal operation and performs the previous idle mode procedure (S2007).

Through the above procedure, when a service request procedure is initiated from a terminal receiving a paging for reporting the number of terminals in a specific geographic area, the signaling of the core network and unnecessary E-RAB setup procedure are rejected by rejecting it. Can be minimized.

Meanwhile, in

Embodiments

1 and 2, when setting a monitoring event (that is, reporting the number of UEs present in the geographical area) to the MME / SGSN through the SCEF in the SCS / AS, a parameter may be added.

For example, the SCS / AS may include a time period for reporting in the monitoring request. That is, a time period for reporting the number of terminals may be set together when setting the monitoring event in the MME / SGSN.

This is because the SCS / AS knows a sleep period (for example, an application sleep period, etc.) of a desired UE, and determines an appropriate time for counting the number of UEs belonging to a specific cell (s) for a certain time. Can be.

That is, when the MME / SGSN does not receive a response to the paging transmission (that is, a TAU / RAU request message or a service request message) from the terminal during the corresponding time period in which the MME / SGSN is set, the MME / SGSN no longer performs paging transmission. The terminal may stop and report only a terminal that successfully responds during the corresponding time period and report it to a network node (for example, SCEF).

21 is a diagram illustrating a method for reporting the number of terminals existing in a geographic area according to an embodiment of the present invention.

Referring to FIG. 21, in the MME / SGSN, a monitoring event for reporting the number of terminals existing in a specific geographic area is set (S2101).

The MME / SGSN transmits a paging message to the terminal through the base station (S2102).

In this case, the MME / SGSN indicates information indicating that the paging message transmitted to the terminal is a paging message for location reporting (or location monitoring usage) (that is, ' Instruction information for indicating the purpose of the monitoring event 'Reporting the number of UEs present in a certain area') may be stored / instructed, and a paging message may be transmitted to the terminal. Alternatively, this order may be reversed.

In addition, as in the first embodiment, the MME / SGSN may include a monitoring usage indication in the corresponding paging message and transmit the same to the terminal.

As described above, the MME / SGSN may transmit an S1AP paging message (or paging request) to the base station through the S1AP interface (or S1AP protocol), and the base station receiving the S1AP paging message from the MME / SGSN An RRC paging message (or paging information) may be configured and transmitted to the terminal.

The MME / SGSN receives a cell ID (cell ID) of the terminal from the base station together with the message transmitted in response to the paging message from the terminal (S2103).

Here, the MME acquires a cell identifier of the corresponding terminal through the S1AP message received from the base station, thereby counting the number of terminals located in the cell (s) requiring a count of the number of terminals and counting the number of terminals. Report to a network node (eg SCEF).

At this time, the message transmitted in response to the paging message from the terminal may correspond to the TAU / RAU request message as in the first embodiment, and may correspond to the service request (Service Request) message as in the second embodiment.

More specifically, the NAS layer of the terminal configures a TAU / RAU request / Service Request message, and RRC the TAU / RAU request / Service Request The message may be included in a message (eg, an RRC connection setup complete message) and transmitted to the base station.

In addition, the base station includes a cell (ie, a TAU / RAU request / service) to which a cell belongs, together with a TAU / RAU request / Service Request message received from the terminal. A cell identifier (eg, ECGI, CGI, etc.) of a cell that has transmitted a service request message may be transmitted to the MME.

That is, the base station may include a TAU / RAU request / Service Request message received from the UE in an S1AP message (eg, an initial UE message) and transmit the same to the MME. have. In this case, the S1AP message may include a cell identifier (Cell ID) of the cell to which the terminal belongs.

On the other hand, when receiving a service request (Service Request) message in response to the paging message from the terminal in which location reporting (or location monitoring usage) is indicated / stored in step S2102, MME / The SGSN may transmit a service reject message including a monitoring usage as a cause value to the terminal through the base station.

22 is a diagram illustrating a method for reporting the number of terminals existing in a geographic area according to an embodiment of the present invention.

Referring to FIG. 22, when a monitoring event for reporting the number of terminals existing in a specific geographic area is set to the MME / SGSN, the terminal receives a paging message through the base station from the MME / SGSN (S2201). .

Here, as in the first embodiment, the paging message may include a monitoring usage indication.

The terminal transmits a message to the MME through the base station in response to the paging message (S2202).

In this case, as in the first embodiment, when the paging message includes a monitoring usage indication (monitoring usage), the terminal may transmit a TAU / RAU request (TAU / RAU request) message to the MME / SGSN through the base station in response; .

Alternatively, as in the second embodiment, the terminal may transmit a service request message to the MME / SGSN through the base station in response.

As described above, the NAS layer of the terminal configures a TAU / RAU request / Service Request message and performs a TAU / RAU request / Service Request. The RRC message may be included in an RRC message (eg, an RRC connection setup complete message) and transmitted to the base station.

On the other hand, as in the second embodiment, when receiving a service reject message including a monitoring usage (cause value) from the MME / SGSN in response to the service request (Service Request) message The terminal may perform a normal idle mode procedure.

General apparatus to which the present invention can be applied

Referring to FIG. 23, a wireless communication system includes a network node 2310 and a plurality of terminals (UEs) 2320.

The network node 2310 includes a processor 2311, a memory 2312, and a communication module 2313. The processor 2311 implements the functions, processes, and / or methods proposed in FIGS. 1 to 22. Layers of the wired / wireless interface protocol may be implemented by the processor 2311. The memory 2312 is connected to the processor 2311 and stores various information for driving the processor 2311. The communication module 2313 is connected to the processor 2311 and transmits and / or receives a wired / wireless signal. As an example of the network node 2310, a base station, an MME, an HSS, an SGW, a PGW, an application server, or the like may correspond thereto. In particular, when the network node 2310 is a base station, the communication module 2313 may include a radio frequency unit (RF) unit for transmitting / receiving a radio signal.

The terminal 2320 includes a processor 2321, a memory 2232, and a communication module (or RF unit) 2323. The processor 2321 implements the functions, processes, and / or methods proposed in FIGS. 1 to 22. Layers of the air interface protocol may be implemented by the processor 2321. The memory 2232 is connected to the processor 2321 and stores various information for driving the processor 2321. The communication module 2323 is connected to the processor 2321 to transmit and / or receive a radio signal.

The

memories

2312 and 2322 may be inside or outside the

processors

2311 and 2321, and may be connected to the

processors

2311 and 2321 by various well-known means. In addition, the network node 2310 (in the case of a base station) and / or the terminal 2320 may have a single antenna or multiple antennas.

In particular, FIG. 24 is a diagram illustrating the terminal of FIG. 23 in more detail.

Referring to FIG. 24, the terminal may include a processor (or a digital signal processor (DSP) 2410, an RF module (or RF unit) 2435, and a power management module 2405). ), Antenna 2440, battery 2455, display 2415, keypad 2420, memory 2430, SIM card Subscriber Identification Module card) 2425 (this configuration is optional), a speaker 2445 and a microphone 2450. The terminal may also include a single antenna or multiple antennas. Can be.

The processor 2410 implements the functions, processes, and / or methods proposed in FIGS. 1 to 22. The layer of the air interface protocol may be implemented by the processor 2410.

The memory 2430 is connected to the processor 2410 and stores information related to the operation of the processor 2410. The memory 2430 may be inside or outside the processor 2410 and may be connected to the processor 2410 by various well-known means.

The user enters command information, such as a telephone number, for example by pressing (or touching) a button on keypad 2420 or by voice activation using microphone 2450. The processor 2410 receives the command information, processes the telephone number, and performs a proper function. Operational data may be extracted from the SIM card 2425 or the memory 2430. In addition, the processor 2410 may display command information or driving information on the display 2415 for the user to recognize and for convenience.

The RF module 2435 is coupled to the processor 2410 to transmit and / or receive RF signals. The processor 2410 communicates command information to the RF module 2435 to, for example, transmit a radio signal constituting voice communication data to initiate communication. The RF module 2435 is composed of a receiver and a transmitter for receiving and transmitting a radio signal. Antenna 2440 functions to transmit and receive wireless signals. Upon receiving a wireless signal, the RF module 2435 may forward the signal and convert the signal to baseband for processing by the processor 2410. The processed signal may be converted into audible or readable information output through the speaker 2445.

The embodiments described above are the components and features of the present invention are combined in a predetermined form. Each component or feature is to be considered optional unless stated otherwise. Each component or feature may be embodied in a form that is not combined with other components or features. It is also possible to combine some of the components and / or features to form an embodiment of the invention. The order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is obvious that the claims may be combined to form an embodiment by combining claims that do not have an explicit citation relationship in the claims or as new claims by post-application correction.

Embodiments according to the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of a hardware implementation, an embodiment of the present invention may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), FPGAs ( field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, and the like.

In the case of implementation by firmware or software, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above. The software code may be stored in memory and driven by the processor. The memory may be located inside or outside the processor, and may exchange data with the processor by various known means.

It will be apparent to those skilled in the art that the present invention may be embodied in other specific forms without departing from the essential features of the present invention. Accordingly, the above detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the invention should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the invention are included in the scope of the invention.

In the wireless communication system of the present invention, a method for reporting or supporting the number of terminals existing in a geographical area has been described based on an example applied to the 3GPP LTE / LTE-A system. In addition to the LTE-A system, it is possible to apply to various wireless communication systems.

Claims

A method for reporting the number of terminals existing in a geographical area in a wireless communication system,

When a monitoring event for reporting the number of terminals existing in the geographical area is set, a mobility management entity (MME) transmitting a paging message to the terminal through the base station; And

Receiving a cell identifier (cell ID) of the terminal from the base station together with a message transmitted in response to the paging message from the terminal,

When the paging message includes a monitoring usage indication, report the number of terminals existing in the geographical area where a tracking area update (TAU) message is transmitted from the terminal in response to the paging message. How to.
The method of claim 1,

And storing information indicating that the paging message is a paging message for reporting the number of terminals existing in a geographical area.
The method of claim 2,

When a service request message is transmitted in response to the paging message from a terminal that stores information indicating that the paging message is a paging message for reporting the number of terminals existing in a geographic area,

And transmitting a service reject message to the terminal through the base station in response to the service request message.
The method of claim 3,

The service reject message is a method for reporting the number of terminals present in a geographic area that includes a cause value of monitoring usage.
The method of claim 3,

The service request message is a method for reporting the number of terminals existing in a geographical area including information indicating whether there is data to be transmitted to the terminal by the network.
The method of claim 5,

When the service request message includes information indicating that the terminal has data to be transmitted to the network, for reporting the number of terminals existing in the geographical area where a service request procedure is performed. Way.
The method of claim 1,

A method for reporting the number of terminals existing in a geographic area further comprising counting and reporting a number of terminals located in a predetermined cell to the network node using the received cell ID. .
The method of claim 1,

When a time period for reporting the number of terminals existing in a geographic area is set when the monitoring event is set, only the number of terminals transmitting a message in response to the paging message in the time period is set. Method for reporting the number of terminals present in the counted geographic area.
A method for supporting reporting of the number of terminals present in a geographical area in a wireless communication system,

Receiving a paging message from the MME through a base station when a monitoring event for reporting the number of terminals existing in a geographical area is set in a mobility management entity (MME); And

Transmitting, by the terminal, a message to the MME through the base station in response to the paging message;

If the paging message includes an indication indicating that the monitoring usage (monitoring usage), in response to the paging message report the number of terminals present in the geographic area to which a tracking area update (TAU) message is transmitted How to.
The method of claim 9,

A method for reporting the number of terminals existing in a geographic area in which a service request message is transmitted in response to the paging message.
The method of claim 10,

A method for reporting the number of terminals existing in a geographical area in which a service reject message is transmitted in response to the service request message from the MME through the base station.
The method of claim 11,

If the service reject message includes a cause value of monitoring usage, the terminal reports the number of terminals present in the geographic area in which an idle mode operation is performed. Way.