[go: up one dir, main page]

WO2016032146A1 - Procédé de traitement de radiomessagerie et procédé de transmission de données de liaison descendante - Google Patents

Procédé de traitement de radiomessagerie et procédé de transmission de données de liaison descendante Download PDF

Info

Publication number
WO2016032146A1
WO2016032146A1 PCT/KR2015/008374 KR2015008374W WO2016032146A1 WO 2016032146 A1 WO2016032146 A1 WO 2016032146A1 KR 2015008374 W KR2015008374 W KR 2015008374W WO 2016032146 A1 WO2016032146 A1 WO 2016032146A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
ddn
paging
mme
network node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2015/008374
Other languages
English (en)
Korean (ko)
Inventor
류진숙
김현숙
김래영
김재현
김태훈
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2016032146A1 publication Critical patent/WO2016032146A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel

Definitions

  • the present invention relates to a paging processing method and a downlink data delivery method.
  • the 3GPP which enacts the technical specifications of the mobile communication system, has been trying to optimize and improve the performance of 3GPP technologies since late 2004 in order to respond to various forums and new technologies related to 4G mobile communication. Started research on Term Evolution / System Architecture Evolution technology.
  • 3GPP SAE centered on 3GPP SA WG2
  • 3GPP SA WG2 is a study on network technology aimed at determining network structure and supporting mobility between heterogeneous networks in parallel with LTE work of 3GPP TSG RAN.
  • Recent important standardization issues of 3GPP Is one of. This is a work to develop a 3GPP system into a system supporting various radio access technologies based on IP, and has been aimed at an optimized packet-based system that minimizes transmission delay with improved data transmission capability.
  • the Evolved Packet System (EPS) high-level reference model defined by 3GPP SA WG2 includes non-roaming cases and roaming cases in various scenarios. See TS 23.401 and TS 23.402.
  • the network structure diagram of FIG. 1 is a simple reconfiguration.
  • 1 is a structural diagram of an evolved mobile communication network.
  • An Evolved Packet Core may include various components, and in FIG. 1, some of them correspond to a Serving Gateway (S-GW) 52, a Packet Data Network Gateway (PW GW) 53, and an MME. (Mobility Management Entity) 51, Serving General Packet Radio Service (GPRS) Supporting Node (SGSN), and Enhanced Packet Data Gateway (ePDG) are shown.
  • S-GW Serving Gateway
  • PW GW Packet Data Network Gateway
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN Serving General Packet Radio Service
  • ePDG Enhanced Packet Data Gateway
  • the S-GW 52 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 22 and the PDN GW 53.
  • the S-GW 52 serves as a local mobility anchor point. That is, packets may be routed through the S-GW 52 for mobility in the E-UTRAN (Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later).
  • E-UTRAN Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later.
  • the S-GW 52 may be connected to other 3GPP networks (RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access). It can also serve as an anchor point for mobility with a network).
  • 3GPP networks RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access). It can also serve as an anchor point for mobility with a network).
  • PDN GW (or P-GW) 53 corresponds to the termination point of the data interface towards the packet data network.
  • the PDN GW 53 may support policy enforcement features, packet filtering, charging support, and the like.
  • mobility management between 3GPP networks and non-3GPP networks for example, untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), code-division multiple access (CDMA) networks, or trusted networks such as WiMax) Can serve as an anchor point for.
  • untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), code-division multiple access (CDMA) networks, or trusted networks such as WiMax
  • I-WLANs Interworking Wireless Local Area Networks
  • CDMA code-division multiple access
  • WiMax trusted networks
  • FIG. 1 shows that the S-GW 52 and the PDN GW 53 are configured as separate gateways, two gateways may be implemented according to a single gateway configuration option. have.
  • the MME 51 is an element that performs signaling and control functions to support access to the network connection of the UE, allocation of network resources, tracking, paging, roaming and handover, and the like. .
  • the MME 51 controls control plane functions related to subscriber and session management.
  • the MME 51 manages a number of eNodeBs 22 and performs signaling for the selection of a conventional gateway for handover to other 2G / 3G networks.
  • the MME 51 performs security procedures, terminal-to-network session handling, idle terminal location management, and the like.
  • SGSN handles all packet data such as user's mobility management and authentication for other 3GPP access networks (eg GPRS network, UTRAN / GERAN).
  • 3GPP access networks eg GPRS network, UTRAN / GERAN.
  • the ePDG acts as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).
  • untrusted non-3GPP networks eg, I-WLAN, WiFi hotspots, etc.
  • a terminal having IP capability is provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access.
  • an IP service network eg, IMS
  • FIG. 1 illustrates various reference points (eg, S1-U, S1-MME, etc.).
  • 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.
  • This reference point can be used in PLMN-to-PLMN-to-for example (for PLMN-to-PLMN handover))
  • S5 Reference point providing user plane tunneling and tunnel management between the SGW and PDN GW. Used for SGW reselection (or relocation) due to UE mobility and when a connection to the PDN GW where the SGW is not located is required for the required PDN connectivity.
  • the PDN may be an operator external public or private PDN or, for example, an in-operator PDN for the provision of IMS services.
  • S2a and S2b correspond to non-3GPP interfaces.
  • S2a is a reference point that provides the user plane with associated control and mobility support 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 PDN GW.
  • Figure 2 is an exemplary view showing the functions of the main nodes of the E-UTRAN and the general EPC in general.
  • the eNodeB 20 may route to a gateway, schedule and transmit paging messages, schedule and transmit a broadcaster channel (BCH), uplink and downlink while an RRC (Radio Resource Control) connection is active.
  • BCH broadcaster channel
  • RRC Radio Resource Control
  • paging occurrence, LTE_IDLE state management user plane can perform encryption, EPS bearer control, encryption and integrity protection of non-access stratum (NAS) signaling.
  • NAS non-access stratum
  • FIG. 3 is an exemplary diagram illustrating a structure of a radio interface protocol in a control plane between a UE and an eNodeB
  • FIG. 4 is a structure of a radio interface protocol in a user plane between a terminal and a base station. Another example is shown.
  • the radio interface protocol is based on the 3GPP radio access network standard.
  • the air interface protocol is composed of a physical layer, a data link layer, and a network layer horizontally, and a user plane and control for data information transmission vertically. It is divided into a control plane for signal transmission.
  • the protocol layers are based on the lower three layers of the Open System Interconnection (OSI) reference model, which is well known in communication systems, and includes L1 (first layer), L2 (second layer), and L3 (third layer). ) Can be separated.
  • OSI Open System Interconnection
  • the physical layer which is the first layer, provides an information transfer service using a physical channel.
  • the physical layer is connected to a medium access control layer on the upper side through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel.
  • data is transferred between different physical layers, that is, between physical layers of a transmitting side and a receiving side through a physical channel.
  • the physical channel is composed of several subframes on the time axis and several sub-carriers on the frequency axis.
  • one subframe includes a plurality of symbols and a plurality of subcarriers on the time axis.
  • One subframe consists of a plurality of resource blocks, and one resource block consists of a plurality of symbols and a plurality of subcarriers.
  • the transmission time interval (TTI) which is a unit time for transmitting data, is 1 ms corresponding to one subframe.
  • the physical channels existing in the physical layer of the transmitting side and the receiving side are physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH) and physical downlink control channel (PDCCH), which are control channels, It may be divided into a Physical Control Format Indicator Channel (PCFICH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and a Physical Uplink Control Channel (PUCCH).
  • PCFICH Physical Control Format Indicator Channel
  • PHICH Physical Hybrid-ARQ Indicator Channel
  • PUCCH Physical Uplink Control Channel
  • the PCFICH transmitted in the first OFDM symbol of the subframe carries a control format indicator (CFI) regarding the number of OFDM symbols (that is, the size of the control region) used for transmission of control channels in the subframe.
  • CFI control format indicator
  • the wireless device first receives the CFI on the PCFICH and then monitors the PDCCH.
  • the PCFICH does not use blind decoding and is transmitted on a fixed PCFICH resource of a subframe.
  • the PHICH carries a positive-acknowledgement (ACK) / negative-acknowledgement (NACK) signal for a UL hybrid automatic repeat request (HARQ).
  • ACK positive-acknowledgement
  • NACK negative-acknowledgement
  • HARQ UL hybrid automatic repeat request
  • the Physical Broadcast Channel (PBCH) is transmitted in the preceding four OFDM symbols of the second slot of the first subframe of the radio frame.
  • the PBCH carries system information necessary for the wireless device to communicate with the base station, and the system information transmitted through the PBCH is called a master information block (MIB).
  • MIB master information block
  • SIB system information block
  • the PDCCH includes resource allocation and transmission format of downlink-shared channel (DL-SCH), resource allocation information of uplink shared channel (UL-SCH), paging information on PCH, system information on DL-SCH, and random access transmitted on PDSCH. Resource allocation of higher layer control messages such as responses, sets of transmit power control commands for individual UEs in any UE group, activation of voice over internet protocol (VoIP), and the like.
  • a plurality of PDCCHs may be transmitted in the control region, and the terminal may monitor the plurality of PDCCHs.
  • the PDCCH is transmitted on an aggregation of one or several consecutive control channel elements (CCEs).
  • CCEs control channel elements
  • CCE is a logical allocation unit used to provide a PDCCH with a coding rate according to a state of a radio channel.
  • the CCE corresponds to a plurality of resource element groups.
  • the format of the PDCCH and the number of bits of the PDCCH are determined according to the correlation between the number of CCEs and the coding rate provided by the CCEs.
  • DCI downlink control information
  • PDSCH also called DL grant
  • PUSCH resource allocation also called UL grant
  • VoIP Voice over Internet Protocol
  • the Medium Access Control (MAC) layer is responsible for mapping various logical channels to various transport channels, and also for multiplexing logical channel multiplexing to map multiple logical channels to one transport channel. Play a role.
  • the MAC layer is connected to the RLC layer, which is the upper layer, by a logical channel.
  • the logical channel includes a control channel for transmitting information of a control plane according to the type of information to be transmitted. It is divided into a traffic channel that transmits user plane information.
  • the Radio Link Control (RLC) layer of the second layer adjusts the data size so that the lower layer is suitable for transmitting data to the radio section by segmenting and concatenating data received from the upper layer. It plays a role.
  • RLC Radio Link Control
  • TM Transparent Mode
  • UM Un-acknowledged Mode
  • AM Acknowledged Mode, Response mode
  • the AM RLC performs a retransmission function through an automatic repeat and request (ARQ) function for reliable data transmission.
  • ARQ automatic repeat and request
  • the Packet Data Convergence Protocol (PDCP) layer of the second layer is an IP containing relatively large and unnecessary control information for efficient transmission in a wireless bandwidth where bandwidth is small when transmitting an IP packet such as IPv4 or IPv6. Performs Header Compression which reduces the packet header size. This transmits only the necessary information in the header portion of the data, thereby increasing the transmission efficiency of the radio section.
  • the PDCP layer also performs a security function, which is composed of encryption (Ciphering) to prevent third-party data interception and integrity protection (Integrity protection) to prevent third-party data manipulation.
  • the radio resource control layer (hereinafter RRC) layer located at the top of the third layer is defined only in the control plane, and the configuration and resetting of radio bearers (abbreviated as RBs) are performed. It is responsible for the control of logical channels, transport channels and physical channels in relation to configuration and release.
  • RB means a service provided by the second layer for data transmission between the terminal and the E-UTRAN.
  • RRC connection When there is an RRC connection (RRC connection) between the RRC of the terminal and the RRC layer of the wireless network, the terminal is in the RRC connected mode (Connected Mode), otherwise it is in the RRC idle mode (Idle Mode).
  • RRC connection RRC connection
  • the RRC state refers to whether or not the RRC of the UE is in a logical connection with the RRC of the E-UTRAN. If the RRC state is connected, the RRC_CONNECTED state is called, and the RRC_IDLE state is not connected. Since the UE in the RRC_CONNECTED state has an RRC connection, the E-UTRAN can grasp the existence of the UE in units of cells, and thus can effectively control the UE. On the other hand, the UE in the RRC_IDLE state cannot identify the existence of the UE by the E-UTRAN, and the core network manages the unit in a larger tracking area (TA) unit than the cell.
  • TA tracking area
  • each TA is identified by a tracking area identity (TAI).
  • TAI tracking area identity
  • the terminal may configure a TAI through a tracking area code (TAC), which is information broadcast in a cell.
  • TAC tracking area code
  • the terminal When the user first turns on the power of the terminal, the terminal first searches for an appropriate cell, then establishes an RRC connection in the cell, and registers the terminal's information in the core network. Thereafter, the terminal stays in the RRC_IDLE state. The terminal staying in the RRC_IDLE state (re) selects a cell as needed and looks at system information or paging information. This is called camping on the cell.
  • the UE staying in the RRC_IDLE state makes an RRC connection with the RRC of the E-UTRAN through an RRC connection procedure and transitions to the RRC_CONNECTED state.
  • RRC_CONNECTED state There are several cases in which a UE in RRC_IDLE state needs to establish an RRC connection. For example, a user's call attempt, a data transmission attempt, etc. are required or a paging message is received from E-UTRAN. Reply message transmission, and the like.
  • a non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management.
  • NAS non-access stratum
  • ESM Evolved Session Management
  • the default bearer resource is characterized in that it is allocated from the network when it is connected to the network when it first accesses a specific Packet Data Network (PDN).
  • PDN Packet Data Network
  • the network allocates an IP address usable by the terminal so that the terminal can use the data service, and also allocates QoS of the default bearer.
  • LTE supports two types of bearer having a guaranteed bit rate (GBR) QoS characteristic that guarantees a specific bandwidth for data transmission and reception, and a non-GBR bearer having a best effort QoS characteristic without guaranteeing bandwidth.
  • GBR guaranteed bit rate
  • Non-GBR bearer is assigned.
  • the bearer allocated to the terminal in the network is called an evolved packet service (EPS) bearer, and when the EPS bearer is allocated, the network allocates one ID. This is called EPS Bearer ID.
  • EPS bearer ID One EPS bearer has QoS characteristics of MBR (maximum bit rate) and GBR (guaranteed bit rate) or AMBR (aggregated maximum bit rate).
  • 5 is a flowchart illustrating a random access procedure in 3GPP LTE.
  • the random access procedure is used for the UE 10 to obtain UL synchronization or to allocate UL radio resources to the base station, that is, the eNodeB 20.
  • the UE 10 receives a root index and a physical random access channel (PRACH) configuration index from the eNodeB 20.
  • PRACH physical random access channel
  • Each cell has 64 candidate random access preambles defined by a Zadoff-Chu (ZC) sequence, and the root index is a logical index for the UE to generate 64 candidate random access preambles.
  • ZC Zadoff-Chu
  • the PRACH configuration index indicates a specific subframe and a preamble format capable of transmitting the random access preamble.
  • UE 10 transmits a randomly selected random access preamble to eNodeB 20.
  • the UE 10 selects one of the 64 candidate random access preambles. Then, the corresponding subframe is selected by the PRACH configuration index.
  • UE 10 transmits the selected random access preamble in the selected subframe.
  • the eNodeB 20 Upon receiving the random access preamble, the eNodeB 20 sends a random access response (RAR) to the UE 10.
  • RAR random access response
  • the random access response is detected in two steps. First, the UE 10 detects a PDCCH masked with a random access-RNTI (RA-RNTI). The UE 10 receives a random access response in a medium access control (MAC) protocol data unit (PDU) on the PDSCH indicated by the detected PDCCH.
  • MAC medium access control
  • RRC 6 shows a connection process in a radio resource control (RRC) layer.
  • RRC radio resource control
  • the RRC state is shown depending on whether the RRC is connected.
  • the RRC state refers to whether or not an entity of the RRC layer of the UE 10 is in a logical connection with an entity of the RRC layer of the eNodeB 20. If the RRC state is connected, the RRC state is connected. A state that is not connected is called an RRC idle state.
  • the E-UTRAN may determine the existence of the corresponding UE in units of cells, and thus may effectively control the UE 10.
  • the UE 10 in the idle state cannot be understood by the eNodeB 20, and is managed by a core network in units of a tracking area, which is a larger area than a cell.
  • the tracking area is a collection unit of cells. That is, the idle state UE (10) is identified only in the presence of a large area unit, in order to receive the normal mobile communication services such as voice or data, the terminal must transition to the connected state (connected state).
  • the UE 10 When the user first powers up the UE 10, the UE 10 first searches for a suitable cell and then remains in an idle state in that cell. When the UE 10 staying in the idle state needs to establish an RRC connection, the UE 10 establishes an RRC connection with the RRC layer of the eNodeB 20 through an RRC connection procedure and performs an RRC connection state ( connected state).
  • the UE in the idle state needs to establish an RRC connection. For example, a user's call attempt or an uplink data transmission is necessary, or a paging message is received from EUTRAN. In this case, the response message may be transmitted.
  • the RRC connection process is largely a process in which the UE 10 sends an RRC connection request message to the eNodeB 20, and the eNodeB 20 transmits an RRC connection setup message to the UE 10. And a process in which the UE 10 sends an RRC connection setup complete message to the eNodeB 20. This process will be described in more detail with reference to FIG. 6 as follows.
  • the UE 10 When the UE 10 in idle state attempts to establish an RRC connection due to a call attempt, a data transmission attempt, or a response to the paging of the eNodeB 20, the UE 10 first performs an RRC connection. A RRC connection request message is transmitted to the eNodeB 20.
  • the eNB 10 When the RRC connection request message is received from the UE 10, the eNB 10 accepts the RRC connection request of the UE 10 when the radio resources are sufficient, and establishes an RRC connection, which is a response message (RRC connection). setup) message is transmitted to the UE 10.
  • RRC connection a response message
  • the UE 10 When the UE 10 receives the RRC connection setup message, the UE 10 transmits an RRC connection setup complete message to the eNodeB 20. When the UE 10 successfully transmits an RRC connection establishment message, the UE 10 establishes an RRC connection with the eNodeB 20 and transitions to an RRC connected state.
  • FIG. 7 is a signal flow diagram illustrating downlink data transmission when ISR is activated.
  • FIG. 7 assumes that ISR (Idle mode Signaling Reduction) is activated.
  • FIG. 7 shows how downlink data is delivered to a UE in idle mode (or ECM_IDLE state) when the ISR is activated.
  • the UE 100 will be described centering on a state where the E-UTRAN cell is camped on.
  • the Serving Gateway (Serving GW: hereinafter referred to as 'S-GW') 520 receives the downlink data packet for the UE 100 via the P-GW 530.
  • the S-GW 50 buffers a downlink data packet and serves a mobility management node or a mobility management entity (MME) serving a UE 100 that is a receiver of the downlink data packet. identify the mobility management entity.
  • MME mobility management entity
  • the S-GW 520 After the identification procedure of the S-GW 520, after confirming that the ISR is activated for the UE 100, the mobility management node, that is, the MME 510 and the SGSN 410, both of the UE ( Identify that it is servicing 100). Therefore, the S-GW 520 must make a paging request to both the MME 510 and the SGSN 410 serving the UE 100.
  • the S-GW 520 sends a downlink data notification message (DDN) to the MME 510 and the SGSN 410, respectively.
  • DDN downlink data notification message
  • each of the MME 510 and SGSN 410 sends a downlink data notification acknowledgment message (DDN ACK) to the S-GW 520. send.
  • DDN ACK downlink data notification acknowledgment message
  • each of the MME 510 and the SGSN 410 sends a paging message to the UE 100 through its network.
  • the MME 510 sends a paging message to each of the eNodeBs 200 belonging to the tracking area (s) registered by the UE 100 (2a). Meanwhile, SGSN 410 sends a paging message to RNC / BSC 300 (2b).
  • the terminal 10 sets up a user plane as a path via the E-UTRAN by performing a service request procedure.
  • the S-GW 520 transmits stop paging for each of the MME 510 and SGSN 410.
  • the S-GW 520 then transmits downlink data to the UE 100 via the E-UTRAN (ie, via the eNodeB 200).
  • Step 4b the UE 100 is paging via the UTRAN / GERAN (ie, 3b described above) ⁇ Step 4b). Then, if the user plane of step 5 described above is set, downlink data is transmitted from the S-GW 520 via UTRAN / GERAN (that is, through the RNC / BSC 300 and NodeB (not shown)). 100).
  • the network manages the location of the UE in units of an ISR, thereby paging to the ISR region in order to transmit downlink data to the UE 100 in an idle mode. do.
  • the existing MME source MME or Old MME
  • DDN downlink data notification
  • DDN ACK downlink data notification acknowledgment
  • Context Request context request
  • DDN ACK downlink data notification acknowledgment
  • S-GW serving gateway
  • the method according to the present disclosure a method for processing paging in the entity that is in charge of the control plane in the mobile communication network, receiving a DDN (Downlink Data Notification) message from the network node Wow; Sending a first DDN ACK message to the network node; If a context request message for a terminal is received from another entity in charge of a control plane after the DDN message is received, transmitting a second DDN ACK message to the network node;
  • the DDN ACK message may include information indicating Temporally Reject.
  • the paging process may not be performed.
  • the method may further include transmitting a paging cancellation message indicating the cancellation of the paging process to the base station requested for paging.
  • the network node may buffer packet data.
  • the network node may buffer the packet data until a guard timer expires.
  • the network node may transmit a DDN message for transmitting the packet data to the other entity.
  • Bearer Change Request Modify Bearer Request
  • the network entity the entity that is in charge of the control plane in the mobile communication network, the transceiver unit for receiving a DDN (Downlink Data Notification) message from the network node;
  • a DDN Downlink Data Notification
  • the terminal if the terminal is to move geographically and change from the existing MME (or SGSN) to the new MME (or SGSN), the mobility of the MME / SGSN after the transmission of the downlink data notification confirmation (DDN ACK) Even if this is recognized, downlink data can be transmitted through the changed MME, thereby improving the quality of service for the user.
  • DDN ACK downlink data notification confirmation
  • 1 is a structural diagram of an evolved mobile communication network.
  • Figure 2 is an exemplary view showing the functions of the main nodes of the E-UTRAN and the general EPC in general.
  • FIG. 3 is an exemplary diagram illustrating a structure of a radio interface protocol in a control plane between a UE and an eNodeB.
  • FIG. 4 is another exemplary diagram illustrating a structure of a radio interface protocol in a user plane between a terminal and a base station.
  • 5 is a flowchart illustrating a random access procedure in 3GPP LTE.
  • RRC 6 shows a connection process in a radio resource control (RRC) layer.
  • RRC radio resource control
  • FIG. 7 is a signal flow diagram illustrating downlink data transmission when ISR is activated.
  • FIG. 8 is an exemplary diagram illustrating a paging processing scheme in the case where MME relocation is recognized after paging transmission according to the first disclosure of the present specification.
  • FIG. 9 is an exemplary diagram illustrating a paging processing scheme in the case where MME re-arrangement before paging transmission is recognized according to the first disclosure of the present specification.
  • FIG. 10 is an exemplary diagram illustrating a paging processing scheme when MME relocation is recognized after paging transmission according to the second disclosure of the present specification.
  • FIG. 11 is an exemplary diagram illustrating a paging processing scheme in a case where MME relocation before paging transmission is recognized according to a second disclosure of the present specification.
  • FIG. 12 is an exemplary diagram illustrating an interface and a protocol between a UE, an eNodeB, and an MME.
  • FIG. 13 is a block diagram illustrating a configuration of a UE 100 and an MME / SGSN 510 according to an embodiment of the present invention.
  • the present invention is described based on the Universal Mobile Telecommunication System (UMTS) and the Evolved Packet Core (EPC), the present invention is not limited to such a communication system, but also to all communication systems and methods to which the technical spirit of the present invention can be applied. Can be applied.
  • UMTS Universal Mobile Telecommunication System
  • EPC Evolved Packet Core
  • first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
  • first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
  • a user equipment UE
  • the illustrated UE may be referred to in terms of terminal, mobile equipment (ME), and the like.
  • the UE may be a portable device such as a laptop, a mobile phone, a PDA, a smart phone, a multimedia device, or a non-portable device such as a PC or a vehicle-mounted device.
  • UMTS stands for Universal Mobile Telecommunication System and means 3rd generation mobile communication network.
  • UE / MS means User Equipment / Mobile Station, terminal equipment.
  • EPC Abbreviation for Evolved Packet Core, and means a core network supporting a Long Term Evolution (LTE) network.
  • LTE Long Term Evolution
  • EPS An abbreviation for Evolved Packet System, which means a mobile communication system including a terminal, an access network including LTE, and an EPC.
  • PDN Public Data Network
  • Independent network where the server that provides the service is located
  • PDN connection Connection from the terminal to the PDN, that is, association between the terminal represented by an IP address and the PDN expressed as an APN (access point name) (connection)
  • PDN-GW Packet Data Network Gateway
  • Network node of EPS network that performs UE IP address allocation, Packet screening & filtering, Charging data collection
  • Serving GW Network node of EPS network performing Mobility anchor, Packet routing, Idle mode packet buffering, Triggering MME to page UE
  • PCRF Policy and Charging Rule Function
  • APN Access Point Name: A name of an access point managed in a network, which is provided to a UE. That is, a string that refers to or distinguishes a PDN. In order to connect to the requested service or network (PDN), the P-GW goes through the name. A predefined name (string) in the network to find this P-GW (example) internet.mnc012.mcc345.gprs
  • Tunnel Endpoint Identifier End point ID of a tunnel established between nodes in a network, and is set for each section in bearer units of each UE.
  • NodeB Base station of the UMTS network, which is installed outdoors, and the cell coverage size corresponds to a macro cell.
  • eNodeB Base station of EPS (Evolved Packet System) is installed outdoors, the cell coverage size corresponds to a macro cell.
  • EPS Evolved Packet System
  • NodeB A term referring to NodeB and eNodeB.
  • MME Abbreviation for Mobility Management Entity, which controls each entity in EPS to provide session and mobility for the UE.
  • a session is a channel for data transmission.
  • the unit may be a PDN, a bearer, or an IP flow unit.
  • the difference in each unit can be divided into the entire target network unit (APN or PDN unit), the QoS classification unit (Bearer unit), and the destination IP address unit as defined in 3GPP.
  • PDN connection (connection) A connection from the terminal to the PDN, that is, the association (connection) between the terminal represented by the IP address and the PDN represented by the APN.
  • UE Context Context information of UE used to manage UE in the network, ie Context Information composed of UE id, mobility (current location, etc.), session attributes (QoS, priority, etc.)
  • OMA DM Open Mobile Alliance Device Management
  • OMA DM Open Mobile Alliance Device Management
  • OAM Operaation Administration and Maintenance
  • OAM is a group of network management functions that provides network fault indication, performance information, and data and diagnostic functions.
  • NAS configuration MO (Management Object): A MO (Management Object) used to configure the UE with parameters associated with NAS Function.
  • the first and second disclosures herein are directed to providing a scheme for handling paging at an entity (eg, MME) that is in charge of a control plane in a mobile communication network.
  • entity eg, MME
  • the first disclosure of this specification describes that the entity receives a downlink data notification (hereinafter referred to as DDN) (message) from a network node (eg, S-GW) and then confirms downlink data notification (hereinafter referred to as DDN ACK) ( Downlink containing information (e.g., Cause Value) indicating Temporally Reject, if successful retransmission or re-selection of the entity (e.g., relocation of the MME) has been successfully sent.
  • DDN rejection link data notification rejection
  • the second disclosure of the present specification provides information indicating a temporary rejection when the entity recognizes the reassignment of the entity after successfully transmitting the DDN ACK (message) after receiving the DDN (message) from the network node ( For example, a method of transmitting a DDN ACK (message) including a Cause Value back to the network node is disclosed.
  • the first DDN ACK may be a first DDN ACK
  • a DDN ACK including information indicating a temporary rejection may be referred to as a second DDN ACK.
  • the paging processing method and the context request before transmission of paging when the Old MME 510a receives the context request after transmitting the paging and recognizes the MME relocation The description will be made by dividing into a paging processing method in the case of receiving MME relocation and receiving MME relocation.
  • the first-first scheme provides a paging processing scheme when the Old MME 510a receives a context request after transmitting paging and recognizes MME reselection or relocation.
  • FIG. 8 is an exemplary diagram illustrating a paging processing scheme in the case where MME relocation is recognized after paging transmission according to the first disclosure of the present specification.
  • the paging processing scheme according to the first-first scheme may be performed in the following order (steps 1 to 7 below).
  • a downlink data notification (DDN) message may be transmitted to the Old MME 510a.
  • the Old MME 510a may successfully transmit (Cause: Successful) a downlink data notification acknowledgment (DDN ACK) message after receiving the DDN message.
  • DDN ACK downlink data notification acknowledgment
  • the Old MME 510a may perform a paging process to the UE 100 through the Old eNodeB 200a.
  • the Old MME 510a may receive a Kentext Request message from the new MME 510b due to MME relocation due to the movement of the UE 100 during the paging process.
  • the Old MME 510a may detect Inter-MME / SGSN Mobility by receiving a context request from the New MME 510b after receiving a DDN message and transmitting a DDN ACK.
  • the Old MME 510a stops the paging process it is performing and sends a downlink data rejection (DDN Reject: DDN failure indication) to the S-GW 520.
  • DDN Reject DDN failure indication
  • the Old MME 510a adds a "temporally reject" as a cause value and sends the DDN rejection message, so that the S-GW 520 sends the packet data of the UE 100. Do not drop, but allow buffering for some time.
  • the New MME 510b receives the downlink packet.
  • An initial context setup procedure is performed to configure S1-U for data transmission.
  • the old MME 510a may transmit a paging cancellation message to stop the paging transmission to the old eNodeB 200a requesting the paging transmission.
  • Steps 6 to 7 described above may be performed regardless of the order.
  • the 1-2 scheme provides a paging processing scheme when the Old MME 510a receives a context request and recognizes MME reselection or relocation (MME relocation) before transmitting the paging. .
  • FIG. 9 is an exemplary diagram illustrating a paging processing scheme in the case where MME re-arrangement before paging transmission is recognized according to the first disclosure of the present specification.
  • the paging processing scheme according to the 1-2 scheme may be performed in the following order (steps 1 to 5 below).
  • a downlink data notification (DDN) message may be transmitted to the Old MME 510a.
  • the Old MME 510a may successfully transmit a Downlink Data Notification Acknowledgment (DDN ACK) message after receiving the DDN message.
  • DDN ACK Downlink Data Notification Acknowledgment
  • the Old MME 510a may receive a Kentext Request message from the new MME 510b with MME relocation due to the movement of the UE 100 before transmitting the paging after transmitting the DDN ACK.
  • the Old MME 510a may detect the Inter-MME / SGSN Mobility by receiving the context request from the New MME 510b after receiving the DDN message and transmitting the DDN ACK.
  • the S-GW 520 can be buffered for a certain time without dropping the packet data of the UE (100).
  • the paging processing method and the context request before transmitting the paging when the Old MME 510a receives the context request after transmitting the paging to recognize the MME relocation The description will be made by dividing into a paging processing method in the case of receiving MME relocation and receiving MME relocation.
  • the 2-1 scheme provides a paging processing scheme in the case where the old MME 510a receives a context request after transmitting paging to recognize the MME relocation.
  • FIG. 10 is an exemplary diagram illustrating a paging processing scheme when MME relocation is recognized after paging transmission according to the second disclosure of the present specification.
  • the paging processing scheme according to the first-first scheme may be performed in the following order (steps 1 to 7 below).
  • a downlink data notification (DDN) message may be transmitted to the Old MME 510a.
  • the Old MME 510a may successfully transmit a Downlink Data Notification Acknowledgment (DDN ACK) message after receiving the DDN message.
  • DDN ACK Downlink Data Notification Acknowledgment
  • the Old MME 510a may perform a paging process to the UE 100 through the Old eNodeB 200a.
  • the Old MME 510a may receive a Kentext Request message from the new MME 510b due to MME relocation due to the movement of the UE 100 during the paging process.
  • the Old MME 510a may detect Inter-MME / SGSN Mobility by receiving a context request from the New MME 510b after receiving a DDN message and transmitting a DDN ACK.
  • the Old MME 510a stops the paging process it is performing and sends a downlink data notification acknowledgment (DDN ACK) back to the S-GW 520.
  • DDN ACK downlink data notification acknowledgment
  • the DDN ACK in step 2 is referred to as the first DDN ACK
  • the DDN ACK in step 6 is referred to as the second DDN ACK. Will be explained.
  • the Old MME 510a adds a "temporally reject" as a cause value and sends the second DDN ACK message, so that the S-GW 520 sends a packet of the UE 100. Allows buffering for some time without dropping data.
  • the S-GW 520 may receive an error even if the S-GW 520 receives the second DDN ACK again with the cause value “temporally rejected” after the successful reception of the first DDN ACK after one DDN transmission.
  • the packet data is buffered for a specific time (for example, guard time) without being recognized as an error).
  • the New MME 510b receives the downlink packet.
  • An initial context setup procedure is performed to configure S1-U for data transmission.
  • the old MME 510a may transmit a paging cancellation message to stop the paging transmission to the old eNodeB 200a requesting the paging transmission.
  • Steps 6 to 7 described above may be performed regardless of the order.
  • Method 2-2 MME reallocation is recognized before paging transmission
  • the second-2 scheme provides a paging processing scheme in the case where the old MME 510a receives a context request and recognizes an MME relocation before transmitting the paging.
  • FIG. 11 is an exemplary diagram illustrating a paging processing scheme in a case where MME relocation before paging transmission is recognized according to a second disclosure of the present specification.
  • the paging processing scheme according to the method 2-2 may be performed in the following order (steps 1 to 5 below).
  • a downlink data notification (DDN) message may be transmitted to the Old MME 510a.
  • the Old MME 510a may successfully transmit a first DDN ACK message, which is a downlink data notification acknowledgment message, after receiving the DDN message.
  • the Old MME 510a may receive a Kentext Request message from the new MME 510b with MME relocation due to the movement of the UE 100 before transmitting the paging after transmitting the DDN ACK.
  • the Old MME 510a may detect the Inter-MME / SGSN Mobility by receiving the context request from the New MME 510b after receiving the DDN message and transmitting the DDN ACK.
  • the S-GW 520 considers the normal operation when the cause value of the second DDN ACK is temporarily rejected even when the DDN ACK is received twice, and drops the packet data for a predetermined time. I never do that.
  • the Old MME 510a successfully transmits the DDN ACK to the S-GW 520 and then does not transmit the DDN rejection message when the MME mobility is detected, the S- A method of causing the GW 520 to buffer downlink data is described.
  • a further disclosure of the present disclosure is that the UE 100 receives a context request from the New MME 510b after the Old MME 510a receives a DDN message from the S-GW 520 and successfully transmits a DDN ACK for it. If the UE recognizes the inter-MME movement operation (when the UE 100 performs a TAU at the MME boundary region and the serving MME is changed), even if paging is not successfully transmitted to the UE 100 (old MME ( 510a already recognizes that the UE 100 cannot receive paging). In step 5, the UE 100 proposes a method not to send a DDN rejection or failure (Downlink Data Notification Reject / Failure).
  • the S-GW 520 does not discard the packet, and when the S-GW 520 receives a bearer modification request from the New MME 510b, the S-GW 520 sends the DDN back to the New MME 510b. And transmit downlink packet data again.
  • the MME receives no response from the UE because the Tracking Area Update procedure with MME change or the Routing Area Update procedure is in progress, it shall not send the Downlink Data Notification Reject message to the Serving GW.
  • the SGSN receives no response from the UE because the Routing Area Update procedure with SGSN change or the Tracking Area Update procedure is in progress, it shall not send the Downlink Data Notification Reject message to the Serving GW.
  • FIG. 12 is an exemplary diagram illustrating an interface and a protocol between a UE, an eNodeB, and an MME.
  • messages transmitted and received between the UE 100 and the eNodeB 200 are messages based on a Radio Resource Control (RRC) protocol.
  • the messages transmitted and received between the eNodeB 200 and the MME 510 are messages based on S1-AP (S1 Application Protocol).
  • the messages transmitted and received between the UE 100 and the MME 510 are messages based on a non-access stratum (NAS) protocol.
  • the messages by the NAS protocol are transmitted by encapsulating the messages by the RRC protocol and the S1-AP message, respectively.
  • FIG. 13 is a block diagram illustrating a configuration of a UE 100 and an MME / SGSN 510 according to an embodiment of the present invention.
  • the UE 100 includes a storage means 101, a controller 102, and a transceiver 103.
  • the MME 510 includes a storage means 511, a controller 512, and a transceiver 513.
  • the S-GW 520 includes a storage means 521, a controller 522, and a transceiver 523.
  • the storage means 101, 511, 521 store the method according to the disclosures herein.
  • the controllers 102, 512, and 522 control the storage means 101, 511, and 521 and the transceivers 103, 513, and 523. Specifically, the controllers 102, 512, 522 execute the methods stored in the storage means 101, 511, 521, respectively. The controllers 102, 512, and 522 transmit the aforementioned signals through the transceivers 103, 513, and 523.

Landscapes

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

Abstract

L'invention concerne un procédé de traitement de radiomessagerie et un procédé de transmission de données de liaison descendante. Un procédé de traitement de radiomessagerie, dans une entité responsable d'un plan de commande dans un réseau de communication mobile, comprend les étapes consistant à : recevoir un message de notification de données de liaison descendante (DDN) en provenance d'un nœud de réseau ; transmettre un premier message ACK de DDN au nœud de réseau ; et, en cas de réception d'un message de demande de contexte d'un terminal en provenance d'une autre entité responsable d'un plan de commande suite à la réception du message de DDN, transmettre un second message ACK de DDN au nœud de réseau, le second message ACK de DDN pouvant comprendre des informations qui indiquent un rejet temporaire.
PCT/KR2015/008374 2014-08-28 2015-08-11 Procédé de traitement de radiomessagerie et procédé de transmission de données de liaison descendante Ceased WO2016032146A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201462042804P 2014-08-28 2014-08-28
US62/042,804 2014-08-28
US201462076479P 2014-11-07 2014-11-07
US62/076,479 2014-11-07

Publications (1)

Publication Number Publication Date
WO2016032146A1 true WO2016032146A1 (fr) 2016-03-03

Family

ID=55399996

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/008374 Ceased WO2016032146A1 (fr) 2014-08-28 2015-08-11 Procédé de traitement de radiomessagerie et procédé de transmission de données de liaison descendante

Country Status (1)

Country Link
WO (1) WO2016032146A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017171451A1 (fr) * 2016-03-30 2017-10-05 엘지전자(주) Procédé de transmission de données tamponnées dans un système de communications sans fil, et appareil associé

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014042482A2 (fr) * 2012-09-14 2014-03-20 삼성전자 주식회사 Procédé et appareil pour commander un service particulier dans un état de congestion de réseau dans un système de communication sans fil
US20140101303A1 (en) * 2012-10-08 2014-04-10 Cisco Technology, Inc. System and method for throttling downlink data notifications in a network environment
US20140128110A1 (en) * 2011-07-15 2014-05-08 Huawei Technologies Co., Ltd Paging Processing Method, User Equipment and System
EP2747467A1 (fr) * 2011-01-07 2014-06-25 NEC Corporation Procédé de communication mobile et système
EP2757825A1 (fr) * 2011-09-15 2014-07-23 China Academy of Telecommunications Technology Procédé, système et dispositif pour la transmission de données

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2747467A1 (fr) * 2011-01-07 2014-06-25 NEC Corporation Procédé de communication mobile et système
US20140128110A1 (en) * 2011-07-15 2014-05-08 Huawei Technologies Co., Ltd Paging Processing Method, User Equipment and System
EP2757825A1 (fr) * 2011-09-15 2014-07-23 China Academy of Telecommunications Technology Procédé, système et dispositif pour la transmission de données
WO2014042482A2 (fr) * 2012-09-14 2014-03-20 삼성전자 주식회사 Procédé et appareil pour commander un service particulier dans un état de congestion de réseau dans un système de communication sans fil
US20140101303A1 (en) * 2012-10-08 2014-04-10 Cisco Technology, Inc. System and method for throttling downlink data notifications in a network environment

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017171451A1 (fr) * 2016-03-30 2017-10-05 엘지전자(주) Procédé de transmission de données tamponnées dans un système de communications sans fil, et appareil associé
US10616810B2 (en) 2016-03-30 2020-04-07 Lg Electronics Inc. Method for transmitting buffered data in wireless communication system, and apparatus therefor

Similar Documents

Publication Publication Date Title
WO2015009070A1 (fr) Procédé de sélection de plmn, et équipement utilisateur
WO2015037882A1 (fr) Procédé de resélection de nœud de réseau responsable du plan de commande
WO2018131970A1 (fr) Procédé de régulation de congestion lors d'une congestion dans un réseau
WO2015002456A1 (fr) Méthode de sélection ou de resélection de relais pour service de proximité
WO2014058242A1 (fr) Procédé de traitement de recherche de mobile et procédé permettant de relayer des données de liaison descendante
WO2015105301A1 (fr) Procédé de transfert de données de liaison descendante et procédé d'exécution de procédure de mise à jour d'emplacement
WO2018101574A1 (fr) Procédé d'utilisation de fonction de désactivation de données de commutation de paquets et équipement utilisateur
WO2014137098A1 (fr) Procédé d'ajustement de plage de service de proximité et procédé de filtrage associé
WO2017034352A1 (fr) Procédé de connexion de station de base et équipement utilisateur le mettant en œuvre
WO2015102444A1 (fr) Procédé de transmission de signal de détection et équipement d'utilisateur pour une communication de proximité
WO2015105339A1 (fr) Procédé de prise en charge d'un mode de gestion de la consommation d'énergie et dispositif radio associé
WO2017171184A1 (fr) Procédé pour tentative d'accès réseau à partir d'une rat nb-iot
WO2015137631A1 (fr) Procédé pour la mise en œuvre de service de proximité, et dispositif utilisateur
WO2014084596A1 (fr) Procédé de connexion d'un service basé ims
WO2017018662A1 (fr) Procédé d'établissement de connexion pdn et équipement d'utilisateur
WO2014061911A1 (fr) Procédé de fourniture d'informations liées à une surveillance mtc
WO2014129794A1 (fr) Procédé et terminal permettant de déterminer un accès sur la base d'une politique
WO2015170862A1 (fr) Procédé pour établir une pluralité de connexions pdn au moyen d'un csipto
WO2016076603A1 (fr) Procédé et équipement d'utilisateur pour bloquer un accès à un réseau par régulation acdc
WO2014182061A1 (fr) Procede pour determiner l'activation d'une capacite isr
WO2015108363A1 (fr) Procédé destiné au support de mode d'économie d'énergie et dispositif sans fil associé
WO2017030343A1 (fr) Procédé de repositionnement de passerelle et procédé de génération d'un support dédié
WO2015163712A1 (fr) Procédé pour réagir à une défaillance d'un pdn particulier
WO2014051260A1 (fr) Procédé de surveillance mtc
WO2017034195A1 (fr) Procédé d'obtention de numéro d'identification de réseau d'opérateur d'un réseau visité

Legal Events

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

Ref document number: 15836671

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15836671

Country of ref document: EP

Kind code of ref document: A1