WO2016104897A1 - Procédé pour le traitement efficace de signal dans l'état activé de réduction de signalisation en mode veille en mobilité de flux ip baseé sur réseau - Google Patents

Procédé pour le traitement efficace de signal dans l'état activé de réduction de signalisation en mode veille en mobilité de flux ip baseé sur réseau Download PDF

Info

Publication number
WO2016104897A1
WO2016104897A1 PCT/KR2015/006745 KR2015006745W WO2016104897A1 WO 2016104897 A1 WO2016104897 A1 WO 2016104897A1 KR 2015006745 W KR2015006745 W KR 2015006745W WO 2016104897 A1 WO2016104897 A1 WO 2016104897A1
Authority
WO
WIPO (PCT)
Prior art keywords
nbifom
isr
request
network
terminal
Prior art date
Application number
PCT/KR2015/006745
Other languages
English (en)
Korean (ko)
Inventor
윤명준
류진숙
김현숙
김래영
김재현
김태훈
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2016104897A1 publication Critical patent/WO2016104897A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present disclosure relates to mobile communication.
  • 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.
  • the EPC may include various components, and in FIG. 1, some of them correspond to a Serving Gateway (S-GW) 52, a PDN Packet Data Network Gateway (GW) 53, and a Mobility Management Entity (MME). 51, a Serving General Packet Radio Service (GPRS) Supporting Node (SGSN), and an enhanced Packet Data Gateway (ePDG).
  • S-GW Serving Gateway
  • 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.
  • the SGSN handles all packet data, such as user's mobility management and authentication to other connecting 3GPP networks (e.g., GPRS networks, UTRAN / GERAN).
  • 3GPP networks e.g., GPRS networks, 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 within PLMN-to-PLMN-to-for example (for PLMN-to-PLMN handover). (It enables user and bearer information exchange for inter 3GPP access network mobility in Idle and / or active state.
  • This reference point can be used intra-PLMN or inter-PLMN (eg in the case of Inter-PLMN HO).)
  • S4 Reference point between SGW and SGSN that provides relevant control and mobility support between the GPRS core and SGW's 3GPP anchor functionality. It provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW.In addition, if Direct Tunnel is not established, it provides the user plane tunneling .
  • S5 Reference point providing user plane tunneling and tunnel management between the SGW and PDN GW.
  • SGW relocation Because of UE mobility and for connections to the PDN GW where the SGW is not co-located for the required PDN connectivity.
  • It provides user plane tunneling and tunnel management between Serving GW and PDN GW. used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW 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.
  • Packet data network may be an operator external public or private packet data network or an intra operator packet data network, eg for provision of IMS services.This reference point corresponds to Gi for 3GPP accesses.
  • 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 is responsible for routing to the gateway, scheduling and sending paging messages, scheduling and sending broadcaster channels (BCHs), and uplink and downlink resources while the RRC connection is active. Function for dynamic allocation, configuration and provision for measurement of the eNodeB 20, radio bearer control, radio admission control, and connection mobility control. Within the EPC, paging can occur, LTE_IDLE state management, user planes can perform encryption, EPS bearer control, NAS signaling encryption and integrity protection.
  • BCHs broadcaster channels
  • 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 a 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 There are several cases in which the UE in RRC_IDLE state needs to establish an RRC connection. For example, when an uplink data transmission is necessary due to a user's call attempt, or when a paging message is received from E-UTRAN, Send a response message.
  • 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 This is called EPS Bearer ID.
  • MLR maximum bit rate
  • GRR guaranteed bit rate
  • AMBR aggregated maximum bit rate
  • 5a 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 radio resource control
  • an RRC state is shown depending on whether 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. 4B.
  • 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 that 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 the RRC connected mode.
  • 6A and 6B show an architecture for connecting a WLAN to an EPC.
  • FIG. 6A shows an architecture in which a WLAN is connected to a P-GW via an S2a interface.
  • a WLAN access network (particularly, in the case of the S2a interface, is a trusted WLAN access network because it is an interface that connects trusted non-3GPP access with the EPC) is connected to the P-GW via the S2a interface.
  • the structure of the Trusted WLAN Access Network (TWAN) will be referred to the contents described in TS 23.402.
  • FIG. 6B shows an architecture in which a WLAN is connected to a P-GW via an S2b interface.
  • the WLAN access network (in particular, the S2b interface is an untrusted WLAN access network because it is an interface that connects untrusted non-3GPP access with the EPC) is connected to the P-GW via the S2b interface. It is connected to the P-GW via an evolved packet data gateway (ePDG).
  • ePDG evolved packet data gateway
  • WLAN a trusted WLAN and an untrusted WLAN may be referred to as WLANs without distinction.
  • FIG. 7A is an exemplary diagram illustrating an example of IFOM technology.
  • the IFOM provides the same PDN connection through several different accesses at the same time. This IFOM provides a bypass to seamless WLAN.
  • IFOM also provides for passing the IP flow of the same PDN connection from one access to another.
  • FIG. 7B is an exemplary diagram illustrating an example of the MAPCON technology.
  • MAPCON technology is to connect multiple PDN connections, easily IP flows to other APNs through other access systems.
  • This MAPCON technology allows the UE 10 to create a new PDN connection on an access that was not previously used.
  • the UE 10 may create a new PDN connection in an optional one of several previously used accesses.
  • the UE 10 may transfer all or some of all PDN connections that are already connected to another access.
  • the operator In order to divert traffic to non-3GPP access, the operator provides a policy to the terminal, and the terminal may bypass its data to the wireless LAN according to the policy.
  • an access network discovery and selection function (ANDSF) based on 3GPP has been improved to provide a policy related to a wireless LAN.
  • 8A and 8B illustrate a network control entity for access network selection.
  • the ANDSF may be present in the home network of the UE 10 (hereinafter referred to as “HPLMN”). Also, as can be seen with reference to FIG. 8B, the ANDSF may also exist in a visited network of the UE 10 (hereinafter referred to as 'VPLMN'). As such, when located in the home network, it may be referred to as H-ANDSF 61, and may be called as V-ANDSF 62 when located in the visited network.
  • ANDSF 60 collectively refers to H-ANDSF 61 or V-ANDSF 62.
  • the ANDSF may provide information about an inter-system mobility policy, information for access network discovery, and information about inter-system routing, for example, a routing rule.
  • IFOM is performed by the UE's initiative decision and uses DSMIP (Dual Stack Mobile IP), which is a host-based mobility protocol.
  • DSMIP Direct Stack Mobile IP
  • NBIFOM Network Based IP Flow Mobility
  • an intermediate network node e.g., MME or SGSN
  • P-GW PDN Gateway
  • a method of processing ISR Idle mode Signaling Reduction
  • the step of checking whether the ISR deactivation condition is satisfied Locally deactivating the ISR when the ISR deactivation condition is satisfied, wherein the ISR deactivation condition is that both the UE and the Packet Data Network (PDN) gateway are NBIFOM (Network Based IP Flow Mobility).
  • ISR Interle mode Signaling Reduction
  • the terminal In case that the terminal is attached to the WLAN as an SCM (attachment) to the WLAN or located in the WLAN coverage, the terminal after the establishment of the PDN canon for the terminal established the existing tracking area (TA) or routing (RA) It may be a case of moving to another TA or RA out of an area) and a case in which the terminal is currently in an ISR activation state.
  • TA tracking area
  • RA routing
  • locally deactivating the ISR may include locally deactivating the ISR by changing a temporary identity used in next update (TIN) of at least one of a tracking area update (TAU) and a routing area update (RAU). It may include.
  • TIN temporary identity used in next update
  • TAU tracking area update
  • RAU routing area update
  • the step of checking whether the ISR deactivation condition is satisfied may be performed by the UE performing NBIFOM Capability Negotiation (NBIFOM Capability Negotiation) confirming NBIFOM capability with the PDN gateway. It may include checking whether both the UE and the PDN gateway support NBIFOM.
  • a method for processing Network Based IP Flow Mobility (NBIFOM) in the network entity that is in charge of the control plane in the mobile communication network NBIFOM request from the network node Receiving a Downlink Data Notification (DDN) message that includes information indicating that the message is due to; Transmitting a paging including information indicating that the terminal is due to the NBIFOM request; Receiving a service request including information indicating that the terminal is due to the NBIFOM request; If the network entity does not support the NBIFOM, it may include transmitting a denial of service to the terminal.
  • DDN Downlink Data Notification
  • the method may further include transmitting a DDN rejection message to the network node that includes information indicating that a service is not supported when the network entity does not support the NBIFOM.
  • the network node receives an update bearer request generated by the NBIFOM request from another network node, and when the DDN rejection message is received, sends the update bearer response including information indicating that the service is not supported. Can be sent to
  • the terminal for processing ISR (Idle mode Signaling Reduction) in a wireless communication system, the storage means for storing the ISR deactivation condition; A controller for determining whether the ISR deactivation condition is satisfied and locally deactivating the ISR when the ISR deactivation condition is satisfied, wherein the ISR deactivation condition includes: the terminal and a packet data network (PDN) gateway; Are all supporting Network Based IP Flow Mobility (NBIFOM), when the terminal is attached to the WLAN as an SCM or located in WLAN coverage, the terminal is established after the PDN is established for the terminal. This may be a case where the mobile station moves out of the existing tracking area or routing area and moves to another TA or RA, and the terminal is currently in an ISR activation state.
  • ISR Interference Signaling Reduction
  • the controller may locally deactivate the ISR by changing a temporary identity used in next update (TIN) of at least one of a tracking area update (TAU) and a routing area update (RAU).
  • TIN temporary identity used in next update
  • TAU tracking area update
  • RAU routing area update
  • the controller may perform NBIFOM Capability Negotiation (NBIFOM Capability Negotiation) confirming NBIFOM capability with each other in the PDN connection establishment process, so that both the UE and the PDN gateway support NBIFOM. It may be to check whether or not.
  • NBIFOM Capability Negotiation NBIFOM Capability Negotiation
  • a network entity in charge of a control plane in a mobile communication network provides a downlink data notification (DDN) message including information indicating that the network node is due to an NBIFOM request.
  • DDN downlink data notification
  • the controller may control the transceiver to transmit a DDN rejection message including information indicating that a service is not supported to the network node when the network entity does not support the NBIFOM.
  • 1 is a structural diagram of an evolved mobile communication network.
  • Figure 2 is an exemplary view showing the architecture of a general E-UTRAN and a general EPC.
  • 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.
  • 5a is a flowchart illustrating a random access procedure in 3GPP LTE.
  • RRC radio resource control
  • 6A and 6B show an architecture for connecting a WLAN to an EPC.
  • FIG. 7A is an exemplary diagram illustrating an example of an IFOM technique
  • FIG. 7B is an exemplary diagram illustrating an example of a MAPCON technique.
  • 8A and 8B illustrate a network control entity for access network selection.
  • FIG. 10 shows a UE initiated IP flow mobility process.
  • 11 shows a situation in which UTRAN and E-UTRAN are mixed.
  • FIG. 12 is a flowchart illustrating a flow of idle mode signaling reduction (ISR) for solving a problem situation illustrated in FIG. 11.
  • ISR idle mode signaling reduction
  • 13 is a signal flow diagram illustrating downlink data transmission when ISR is activated.
  • FIG. 16 illustrates a signaling reduction gain according to the first method during the second disclosure of the present specification.
  • FIG. 17 illustrates signaling gains when the local ISR deactivation scheme according to the first disclosure and the signaling reduction scheme through the DDN according to the second disclosure are applied together.
  • FIG. 18 is a block diagram illustrating a configuration of a UE 100 and an MME 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.
  • GSM EDGE Radio Access Network An acronym for GSM EDGE Radio Access Network, and refers to a wireless access section connecting a core network and a terminal by GSM / EDGE.
  • UTRAN Abbreviation for Universal Terrestrial Radio Access Network, and refers to a wireless access section connecting a terminal and a core network of 3G mobile communication.
  • E-UTRAN Abbreviation for Evolved Universal Terrestrial Radio Access Network, and refers to a 4G mobile communication, that is, a wireless access section connecting a terminal to a LTE network.
  • UMTS stands for Universal Mobile Telecommunication System and means a core network of 3G mobile communication.
  • UE / MS means User Equipment / Mobile Station, terminal equipment.
  • EPS stands for Evolved Packet System and means a core network supporting a Long Term Evolution (LTE) network.
  • LTE Long Term Evolution
  • UMTS evolved network
  • PDN Public Data Network
  • PDN connection connection from the terminal to the PDN, that is, association (connection) between the terminal represented by the IP address and the PDN represented by the APN
  • 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. (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 A base station of a UMTS network, which is installed outdoors, and a cell coverage scale corresponds to a macro cell.
  • eNodeB A base station of an evolved packet system (EPS), which is installed outdoors, and a cell coverage size corresponds to a macro cell.
  • EPS evolved packet system
  • NodeB A term referring to NodeB and eNodeB.
  • MME Mobility Management Entity
  • 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.)
  • NAS Non-Access-Stratum: Upper stratum of the control plane (control plane) between the UE and the MME. Support mobility management, session management, IP address maintenance between UE and network
  • RAT Abbreviation for Radio Access Technology, which means GERAN, UTRAN, E-UTRAN and the like.
  • Local Operating Environment Information This is a set of implementation specific parameters which describe the local environment in which the UE is operating.
  • Presence Reporting Area This area is defined for the purpose of reporting the presence of the UE in the 3GPP packet domain due to policy control and / or charging reasons.
  • the presence reporting area consists of a neighboring or non-neighboring tracking area or a set of eNodeBs and / or cells.
  • ANDSF Access Network Discovery and Selection Function: Provides a policy that allows a terminal to discover and select available access on an operator basis as a network entity.
  • ISRP Inter-System Routing Policy
  • IFOM IP Flow Mobility
  • MAPCON Multi Access PDN Connectivity
  • NSWO non-seamless WLAN offload
  • IP Flow Mobility (IFOM) rule This rule prioritizes the access technology / access networks that should be used by the UE when it is able to route traffic that matches a particular IP traffic filter on a particular APN or any APN. It's a list. In addition, this rule may specify for which wireless access the traffic that matches a particular IP traffic filter on a particular APN or any APN is restricted.
  • IOM IP Flow Mobility
  • MAPCON Multi Access PDN Connectivity
  • This rule is a list of prioritized access technologies / access networks that should be used by the UE when it is possible to route PDN connections to a particular APN.
  • this rule may specify to which radio access the PDN connection to a particular APN should be restricted.
  • Non-seamless WLAN offload (NSWO) rule This rule specifies which traffic should be bypassed non-seamlessly to the WLAN or not.
  • ISMP Inter-System Mobility Policy
  • RAN rule Evaluates a RAN rule programmed in the UE with Radio Access Network (RAN) Assistance Parameters received from the network.
  • the RAN rule is also referred to as WLAN interworking supported by the RAN used without ANDSF ISRP / ISMP.
  • the AS (Access Stratum) layer of the UE carries the move-traffic-to-WLAN indication and WLAN identifier together to the upper layer of the UE. In this case, the UE selects the WLAN to move all offloadable PDN connections to the WLAN.
  • the access stratum (AS) layer of the UE delivers a move-traffic-from-WLAN indication to a higher layer of the UE.
  • the UE moves all PDN connections on the WLAN to 3GPP.
  • a detailed description of the RAN rule can be found with reference to 3GPP TS 23.401, TS 23.060, TS 23.402, TS 36.300, TS 36.304, TS 36.331, TS 25.304 and TS 25.331.
  • Multi-access PDN connection A PDN connection in which traffic can be routed through 3GPP access and / or WLAN access. Each IP flow is only routed through one accessor at a time.
  • NBIFOM One of the main operations of NBIFOM is a process of installing a routing rule between the UE and a P-GW (PDN Gateway).
  • a UE or P-GW
  • the PGW or UE
  • the PGW sends an acknowledgment / reject to it as a response message.
  • the NBIFOM procedure is divided into UE initiated and Network initiated NBIFOM procedures according to the initiated entity.
  • a network initiated IP flow mobility process may be performed as follows.
  • UE 100 attaches to PDN GW 530 via E-UTRAN and TWAN (Trusted WLAN Access Network) simultaneously.
  • E-UTRAN E-UTRAN
  • TWAN Trusted WLAN Access Network
  • PCRF 550b determines to update the routing rule.
  • the PCRF 550a, 550b sends a Policy and Charging Rules Provision message including the routing rule to the PDN GW 530.
  • the PDN GW 530 sends an S-GW 520 an Update Bearer Request or Update Notification (as specified in RFC 7077) that includes the new routing rule.
  • the S-GW 520 forwards this information to the MME 510 via an update bearer request.
  • the MME 510 sends the routing rule to the UE 100 via NAS signaling.
  • the UE determines whether to accept or reject the routing rule.
  • the UE 100 sends the approved routing rule to the MME 510 via NAS signaling.
  • the MME 510 returns an Update Bearer Response message to the S-GW 520.
  • the message includes a routing rule approved by the UE 100.
  • the MME 510 communicates the information to the S-GW 520 via an Update Bearer Response / Update Notification Acknowledgment (as specified in RFC 7077).
  • FIG. 10 shows a UE initiated IP flow mobility process.
  • the UE initiated IP flow mobility process may be performed as follows.
  • UE 100 simultaneously connects to 3GPP or non-3GPP accesses and establishes multiple IP flows of the same PDN connection.
  • the UE 100 sends a Bearer Resource Modification (Request Bearer Resource Modification) message including a routing rule requested by the UE 100 to the eNodeB 200.
  • Bearer Resource Modification Request Bearer Resource Modification
  • the eNodeB 200 sends a Bearer Resource Command message including the routing rule to the MME 510.
  • the MME 510 transmits the routing rule to the PDN GW 530 through the S-GW 520.
  • the PDN GW 530 initiates the IP_CAN modification process and provides the routing rules to the PCRFs 550a and 550b.
  • the PDN GW 530 performs a dedicated bearer activation procedure or bearer modification procedure to confirm the routing rule, as described in TS 23.401.
  • 11 shows a situation in which UTRAN and E-UTRAN are mixed.
  • an eNodeB of an E-UTRAN may be located in an area where a NodeB of the UTRAN (ie, a third generation radio access network) exists.
  • the illustrated Tracking Area Identity (TAI) list indicates an area where E-UTRAN provides a service as an E-UTRAN location registration unit and includes cells of one or more eNodeBs.
  • TAI Tracking Area Identity
  • routing area indicates an area where the UTRAN provides a service as a UTRAN location registration unit and includes one or more NodeB cells.
  • the illustrated UE 100 is located at the boundary between the E-UTRAN and the UTRAN, and can camp on any one.
  • camping on means that the UE 100 accesses a cell after completing a cell selection procedure or a cell reselection procedure.
  • the location registration is performed by the MME 510, while the UE 100 camps on the UTRAN cell.
  • location registration is performed by a Serving General Packet Radio Service Support Node (SGSN) 420.
  • SGSN Serving General Packet Radio Service Support Node
  • the location registration procedure may be continued, thereby causing waste of network resources.
  • FIG. 12 is a flowchart illustrating a flow of idle mode signaling reduction (ISR) for solving a problem situation illustrated in FIG. 11.
  • ISR idle mode signaling reduction
  • ISR Interle mode Signaling Reduction
  • the ISR scheme enables the UE 100 to not perform location registration from a later location when the UE 100 has already registered a location by traveling between the E-UTRAN and the UTRAN once in an idle mode. Specifically, it is as follows.
  • the UE 100 may contact the MME 510. Send an Attach Request message.
  • the MME 510 sends an update location request message to the HSS 540 to inform the attach of the UE 100.
  • the HSS 540 stores an ID of the MME 510 attached by the UE 100, and the HSS 540 sends an update location acknowledgment message containing subscriber information. Send to MME 510 to respond. The MME 510 sends an attach accept message to the UE 100. Through this, the UE 100 completes the attachment procedure to the MME 510 of the E-UTRAN cell that is currently camping on, and also registers the location of the UE 100 to the HSS 540.
  • the UE 100 moves in the E-UTRAN cell and moves to the coverage area of the UTRAN cell. At this time, the UE 100 reselects the UTRAN. Therefore, the UE 100 must register its location by performing a Routing Area Update (RAU) procedure on the UTRAN.
  • RAU Routing Area Update
  • the UE 100 sends a RAU Request message to the SGSN 420 to perform location registration with the HSS 540 through the Serving General Packet Radio Service Support Node (SGSN) 420.
  • the SGSN 420 recognizes from the RAU request message that the UE 100 previously registered location with the MME 510. Accordingly, the SGSN 420 sends a context request message to the MME 510 to obtain a context for the UE 100 from the MME 510 to which the UE 100 has registered a location.
  • SGSN Serving General Packet Radio Service Support Node
  • the MME 510 sends a context response message containing the context for the UE 100 to the SGSN 420 in response to the context request message sent by the SGSN 420.
  • the MME 510 notifies the SGSN 420 that the MME 510 itself can support the ISR function by including the 'ISR capability' or 'ISR Supported' parameter in the context response message.
  • the context information about the UE 100 included in the context response message typically includes MM (Mobility Management) context information and EPS PDN connection information of the UE.
  • the EPS PDN Connection information includes bearer context information.
  • the MME 510 may include context information for the UE 100 to be included in the context response message based on the MM context and EPS bearer context information of the UE 100 maintained by the MME 510. Set.
  • the SGSN 420 determines whether to activate ISR for the UE 100.
  • the SGSN 420 analyzes or confirms the 'ISR capability' or ISR Supported 'parameter of the context response message (Context Response) received from the MME 510 to confirm that the MME 510 supports the ISR function. Can be.
  • the SGSN 420 also supports the ISR function, so the SGSN 420 determines to activate the ISR.
  • the SGSN 420 determines to activate the ISR function. Accordingly, the SGSN 420 sends a context acknowledgment message to the MME 510 as a response to the context response message sent by the MME 510.
  • the context confirmation message includes the parameter 'ISR Activated' to inform the MME 510 that the ISR function is activated for the UE 100.
  • the SGSN 420 and the MME 510 store mutual IDs.
  • the MME 510 that receives a context acknowledgment (Context Ack) message including the 'ISR Activated' parameter from the SGSN 420 maintains the context for the UE 100.
  • Context Ack context acknowledgment
  • the SGSN 420 sends an Update Location Request message to inform the HSS 540 of the location registration of the UE 100.
  • the HSS 540 stores an ID of the SGSN 420 in which the UE 100 performs the RAU, and confirms an update location including the subscriber information of the UE 100 in the SGSN 420. ) Respond by sending a message.
  • the SGSN 420 sends a RAU Accept message to the UE 100.
  • the RAU acceptance includes the 'ISR Activated' parameter to inform the UE 100 that the ISR function is activated.
  • the location of the terminal is registered through the attachment procedure and the RAU procedure, and the ISR is activated because the MME 510 and the SGSN 420 support the ISR function.
  • the UE 100 moves back from the UTRAN to the E-UTRAN, even if the E-UTRAN cell is reselected, since the ISR is currently active, the UE 100 registers the location with the MME 510. You do not have to do it.
  • the UE 100 does not leave the routing area (RA) registered through the SGSN 420 and the tracking area identity (TA) registered through the MME 540, as long as it does not leave the network. There is no need to perform location registration again.
  • This feature is called ISR.
  • a routing area (RA) registered by the UE 100 through the SGSN 420 and a tracking area identity (TAI) list registered through the MME 510 are referred to as an ISR area.
  • the ISR function can reduce waste of network resources by eliminating the repetitive location registration procedure when the UE frequently moves between the E-UTRAN and the UTRAN / GERAN.
  • the S-GW receives a data or signaling message from the P-GW If received, the UE knows that ISR is active and sends a DDN message to both MME / SGSN.
  • MT Mobile Terminating
  • the MME / SGSN receiving the DDN message makes a paging request to each of the eNodeB / RNC. After the UE receives the paging in the cell to which it belongs, the UE responds to the paging with the service request.
  • the MME informs the S-GW that the UE is in the E-UTRAN network through a bearer change request.
  • the S-GW sends a stop paging indication to the SGSN after the UE knows that the UE is in the E-UTRAN network, and the SGSN receives the paging to stop paging.
  • SGSN informs the S-GW that the UE is in the UTRAN / GERAN network by requesting a bearer change, and the S-GW sends a stop paging indication to the MME.
  • the downlink data transfer process when the ISR is activated is as follows.
  • 13 is a signal flow diagram illustrating downlink data transmission when ISR is activated.
  • FIG. 13 assumes that ISR (Idle mode Signaling Reduction) is activated.
  • FIG. 13 shows how downlink data is transmitted to a UE in idle mode (or ECM_IDLE state) when 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 100 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.
  • WLAN connection modes supported by TWAN connecting to WLAN through S2a interface include SCM (Single-Connection Mode) and MCM (Multi-Connection Mode).
  • SCM can operate using the existing WLAN-AP as it is, but can support only one connection / connection.
  • MCM must support WLCP (WLANP) in addition to existing WLAN-AP, and UE must also support WLCP. But it has the advantage of supporting multiple connections / connections at the same time.
  • WLANP WLANCP
  • NBIFOM can forward routing rules to the UE through WLCP in WLAN MCM, but SCM has not yet presented a way to forward routing rules.
  • SCM has not yet presented a way to forward routing rules.
  • NBIFOM forwards through 3GPP network and extended EAP protocol (extended). A method of delivering routing rules using the EAP protocol is under discussion.
  • the TWAN and / or the UE does not support the MCM or the UE is not yet connected to the WLAN (i.e., connected only to 3GPP access) or other circumstances for which routing rules cannot be sent to the WLAN. Suggest an action.
  • the routing rule that the P-GW intends to transmit to the UE may be for changing an IP flow (s) from WLAN to 3GPP access, or vice versa to change from 3GPP access to WLAN.
  • a network (usually a P-GW) checks whether a UE, a serving network node (eg, MME or SGSN), and S-GW support NBIFOM.
  • a serving network node eg, MME or SGSN
  • S-GW support NBIFOM
  • the P-GW supports NBIFOM. This process is called a NBIFOM capability discovery / negotiation process.
  • the UE When the UE makes a PDN connection / connection request (PDN connection request), it informs the Protocol Configuration Option (PCO) whether NBIFOM is supported, and the P-GW also informs the UE whether the NBIFOM is supported by the PCO through the above check.
  • PDN connection request PDN connection request
  • PCO Protocol Configuration Option
  • the MME / SGSN / S-GW may inform the P-GW whether the NBIFOM is supported by the UE during the PDN connection request process.
  • the NBIFOM capability discovery / negotiation is made when a PDN connection is made. Therefore, when the serving node (eg, MME / SGSN) is changed due to mobility of the UE, a situation in which the serving node supports NBIFOM in the P-GW may send a NBIFOM request.
  • the serving node eg, MME / SGSN
  • the UE attaches to the E-UTRAN access and then leaves the E-UTRAN to become an ISR activated state through a Routing Area Update (RAU) process in the UTRAN.
  • RAU Routing Area Update
  • the UE initially performs a PDN connection request at the time of attachment in the E-UTRAN. At this time, the UE informs the network that it supports NBIFOM, and the MME and S-GW also inform the P-GW that they support NBIFOM. This allows the P-GW to enable NBIFOM.
  • the UE additionally makes a PDN connection to the WLAN to receive services such as video streaming.
  • the MME supports NBIFOM, but SGSN does not support NBIFOM. This means that the SGSN cannot carry the NBIFOM request transmitted by the P-GW to the UE.
  • the WLAN operates in SCM mode and cannot send an NBIFOM request to the WLAN, thus sending a routing rule through 3GPP access.
  • the UE i.e., MME and SGSN
  • MME and SGSN serving nodes serving the UE
  • NBIFOM a service request for NBIFOM to switch to connected mode and wastes power by performing unnecessary operations.
  • the network can also put unnecessary load on the network by performing unnecessary signaling.
  • the P-GW 530 when the P-GW 530 receives a request to change a routing rule from the PCRF 550, the P-GW 530 transmits an Update bearer request message to the UE 100 for an NBIFOM request.
  • the S-GW 520 Upon receiving this, the S-GW 520 knows that the UE 100 is in an activated ISR state and transmits a downlink data notification (DDN) message to both the MME 510a / SGSN 510b.
  • DDN downlink data notification
  • MME (510a) / SGSN (510b) receives the paging to the UE (100).
  • the UE 100 is in the UTRAN network, listens to paging, and sends a service request to the SGSN 510b.
  • the SGSN 510b receives the resource allocation in the radio section and sets the UE 100 to the connected mode, and then sends a bearer change request to the S-GW 520.
  • the S-GW 520 that receives the bearer change request to the SGSN 510b knows that the UE 100 is connected to the UTRAN network and sends a stop paging indication to the MME 510a, and the MME 510a sends a stop paging indication. You will receive this and will stop paging.
  • the S-GW 520 performs a bearer change request / response procedure with the P-GW 530 and then transmits an update bearer request that has been buffered to the SGSN 510b. do.
  • the SGSN 510b that received the update bearer request could not interpret the message as it was an NBIFOM request and sent an update bearer response, Cause IE, the cause information, as "Service not supported” to send the request. I will refuse.
  • the S-GW 520 receives the update bearer response and transmits Cause IE, which is the cause information, to the P-GW 530 as "Service not supported".
  • the disclosures herein propose a mechanism for reducing signaling caused by NBIFOM requests when the UE is in ISR mode.
  • the disclosures herein describe how to prevent paging of both UTRAN / E-UTRAN through local ISR deactivation when the UE satisfies the condition that the NBIFOM request occurs in the P-GW and the DDN message.
  • the S-GW 520 informs that the data buffered is an NBIFOM request, and proposes a method of not performing a service request when the MME / SGSN does not support NBIFOM. Each operation may be performed independently or may be performed together.
  • the first of the disclosures proposes a signaling reduction scheme through local ISR deactivation
  • the second of the disclosures of the disclosure proposes a signaling reduction scheme through DDN.
  • the first disclosure of the present specification provides a method for reducing signaling through local ISR deactivation as follows.
  • ISR is a method for reducing signaling when inter-RAT cell reselection is performed.
  • the ISR activation is determined by the network and the RAU / Tracking Area Update (RAU) acknowledgment (ACK) message indicates whether to activate the ISR.
  • RAU Tracking Area Update
  • ACK acknowledgment
  • the UE 100 When the ISR is activated, the UE 100 does not need to perform the RAU / TAU if it is in the tracking area and the routing area where the location registration has already been performed even if the RAT is changed.
  • the UE 100 does not know which access (ie, whether it is in E-UTRAN or in UTRAN / GERAN), and if there is incoming (MT) data, the S-GW 520 may determine the MME ( 510a) / SGSN 510b both request paging to receive a response from the UE.
  • the UE 100 may deactivate the ISR locally without signaling with the network by changing the Temporary Identity used in Next update (TIN) value in the TAU / RAU under certain conditions.
  • TIN Temporary Identity used in Next update
  • the UE 100 may deactivate the ISR by changing the TIN value of the TAU / RAU in the following procedure.
  • the procedure to be performed may be performed in the following order.
  • the UE 100 performs NBIFOM capability negotiation during a PDN connection establishment to confirm that both the UE 100 and the P-GW 530 support NBIFOM.
  • the UE 100 checks whether the UE 100 moves out of a tracking area (TA) / routing area (RA) where a PDN connection is established and moves to another TA / RA.
  • TA tracking area
  • RA routing area
  • the UE 100 performs local ISR deactivation.
  • the terminal UE 100 may check whether the ISR deactivation condition is satisfied and, if the ISR deactivation condition is satisfied, locally deactivate the ISR.
  • the ISR deactivation condition if the terminal and the PDN (Packet Data Network) gateway (P-GW, 530) both support NBIFOM (Network Based IP Flow Mobility), the terminal is attached to the WLAN to the SCM (Attach) or located in WLAN coverage, when the terminal moves out of the existing tracking area (TA) or routing area (TA) to another TA or RA after the PDN is established for the terminal and This may mean a case where the UE is currently in an ISR activation state.
  • PDN Packet Data Network gateway
  • the deactivation of the local ISR may be performed by changing the TIN of at least one of the TAU and the RAU.
  • the terminal in the process of establishing a PDN connection, whether the terminal and the PDN gateway both support the NBIFOM by performing the NBIFOM capability negotiation to confirm the NBIFOM capability (Capability) with the PDN gateway. You can check.
  • 'NBIFOM capability negotiation' may mean a process in which the UE and the P-GW confirm each other's NBIFOM capability.
  • the NBIFOM capability negotiation process is performed while the PDN establishment process is performed.
  • the PGW supports NBIFOM and checks and responds to the NBIFOM capability.
  • PCO Protocol Configuration Option
  • intermediate nodes eg, MME, SGW, SGSN, TWAG, etc.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • SGSN Serving Gateway
  • TWAG TWAG
  • an existing process needs to be changed and intermediate nodes must support them.
  • steps 3a, 4a, and 6a of FIG. 15 may be signaling, which is substantially reduced.
  • a process of checking whether ISR is supported through signaling between MME 510a / SGSN 510b is performed.
  • the MME 510a / SGSN 510b knows whether they support NBIFOM
  • the MME 510a / SGSN 510b checks each other's NBIFOM capabilities through signaling between the MME 510a / SGSN 510b and according to the NBIFOM capability. It may be determined whether to allow ISR activation of the UE.
  • the MME 510a / SGSN 510b indicates whether NBIFOM is supported in the context request message, and the node receiving the context request sets an ISR supported indication as follows.
  • the second disclosure of the present specification provides a method for reducing signaling through DDN as follows.
  • the S-GW 520 When the S-GW 520 receives the NBIFOM request from the P-GW 530, and sends the DDN message to the MME 510a / SGSN 510b when the UE is ISR activated. At this time, the DDN message is sent with the information that occurred due to the NBIFOM request of the P-GW (530). This can be implemented, for example, by marking or marking 'NBIFOM triggered' using the 'private extension field' of the DDN.
  • the signaling scheme via DDN may be divided into a first scheme and a second scheme as follows.
  • the MME 510a / SGSN 510b that has received the DDN finds the UE 100 through paging, and the MME 510a / SGSN 510b that has received the service request from the UE 100 has its own. If the NBIFOM is supported, the service request procedure is performed. If the NBIFOM is not supported, the UE 100 transmits a child through a service reject (Cause # 97: Message type non-existent or not implemented). Maintain Idle) mode.
  • a service reject Create # 97: Message type non-existent or not implemented. Maintain Idle
  • the MME 510a / SGSN 510b sets the cause information (Cause Information Element (IE)) as 'Service not supported' and sends a DDN Failure message to the S-GW 520.
  • S-GW 520 updates the bearer response with the cause information (Cause IE) as 'Service not supported' in response to the NBIFOM request of the P-GW 530.
  • Send In this case, the P-GW 530 knows that the MME 510a / SGSN 510b does not support NBIFOM and no longer sends an NBIFOM request.
  • FIG. 16 illustrates a signaling reduction gain according to the first method during the second disclosure of the present specification.
  • the S-GW 520 when the S-GW 520 receives an update bearer request for an NBIFOM request, the S-GW 520 marks or marks 'NBIFOM triggered' in a 'private extension field' of the DDN message to display a DDN message.
  • MME 510a / SGSN 510b To MME 510a / SGSN 510b.
  • the DDN message may include information indicating that the DDN message is due to the NBIFOM request (eg, 'NBIFOM triggered' information marked in the 'private extension field').
  • the MME 510a / SGSN 510b receiving the paging performs paging.
  • 'NBIFOM triggered' is also marked and sent to the paging message.
  • the paging message may also include information indicating that the paging message is due to the NBIFOM request (eg, 'NBIFOM triggered').
  • the UE 100 is in the UTRAN network, listens to paging, and sends a service request.
  • the UE 100 may indicate that the service request is a response to the request or triggered paging (NBIFOM triggered paging) by the NBIFOM. Mark and send NBIFOM triggered '.
  • the SGSN 510b receiving the service request knows that the service request is triggered by the NBIFOM request, the SGSN 510b does not support the NBIFOM and thus receives the service information of the UE 100 as the cause information (for example, cause value # 97).
  • Reject (Step 5a of FIG. 16) as 'Message type non-existent or not implemented' and cause information (Cause IE) to the S-GW 520.
  • the S-GW 520 receives the stop paging indication to the MME 510a since the UE 100 responds to the paging of the SGSN 510b but may determine that the SGSN 510b does not support NBIFOM. To stop paging.
  • the S-GW 520 sets the cause information (Cause IE) as 'Service not supported', thereby updating the update bearer response ( If the P-GW 530 sends an update bearer response, the P-GW 530 does not support the NBIFOM in the MME 510a / SGSN 510b.
  • the P-GW 530 no longer sends an NBIFOM request.
  • the signaling reduction through the DDN according to the first scheme is performed by the steps 'S1-AP: Initial Context setup request', 'Radio Bearer Establishment' and the like as shown in FIG. 'S1-AP: Initial Context setup Complete' and steps 7 to 11 (update bearer response) may be signaling to substantially reduce.
  • a network entity eg, MME 510a / SGSN 510b requests NBIFOM from a network node (eg, S-GW 520).
  • a network node eg, S-GW 520.
  • DDN Downlink Data Notification
  • a paging including information indicating that the NBIFOM request is due to the UE and indicates that the NBIFOM request is received from the terminal. If a service request including information is received and the network entity does not support the NBIFOM, signaling may be reduced by transmitting a denial of service to the terminal.
  • the network entity may transmit a DDN rejection message to the network node that includes information indicating that a service is not supported.
  • the network node receives an update bearer request generated by the NBIFOM request from another network node (for example, P-GW 530), and if the DDN rejection message is received, the service is not supported. And may send an update bearer response to the other network node that includes the information.
  • another network node for example, P-GW 530
  • the network entity when the network entity receives a context request message from another network entity and the network entity does not support NBIFOM, the network entity indicates whether or not ISR is supported in response to the context request.
  • the ISR Supported 'parameter may be set to not supported regardless of whether the network entity supports ISR, and the context response may be transmitted.
  • the network node may transmit the DDN message including information indicating that the request is due to an NBIFOM request to the network entity.
  • PDN Packet Data Network
  • the MME 510a or SGSN 510b receiving the DDN does not support NBIFOM, it notifies the NDN that it does not support NBIFOM in response to the DDN (additionally, it will not perform paging).
  • Information (cause information: cause IE) is transmitted to the S-GW 520.
  • the MME 510a or SGSN 510b may set and transmit cause information (cause IE) informing the information while sending a DDN acknowledgment message to the S-GW 520. .
  • cause information cause IE
  • the MME 510a or SGSN 510b that does not support the NBIFOM does not perform paging.
  • DDN DDN Rejection Indication
  • a serving node that is, a serving node that supports NBIFOM
  • the S-GW 520 receives the DDN. It can be inferred that it is located in the RAT of the serving node that does not currently support NBIFOM.
  • the S-GW 520 updates the bearer response with the cause information (Cause IE) as 'Service not supported' in response to the NBIFOM request of the P-GW 530. Send)
  • the P-GW 530 knows that the MME 510a / SGSN 510b does not support NBIFOM and no longer sends an NBIFOM request.
  • FIG. 17 illustrates signaling gains when the local ISR deactivation scheme according to the first disclosure and the signaling reduction scheme through the DDN according to the second disclosure are applied together.
  • the network end determines the NBIFOM request without ending up to the UE 100.
  • the steps 3a, 4a, 4b, 5, 6a, 7, 8, 9, 10 and 11 can be signaling which is actually reduced.
  • FIG. 18 is a block diagram illustrating a configuration of a UE 100 and an MME 510 according to an embodiment of the present invention.
  • the UE 100 includes a storage means 102, a processor 101, and a transceiver 103.
  • the MME 510 includes a storage means 512, a processor 511, and a transceiver 513.
  • the storage means 102, 512 store the method described above.
  • the processors 101 and 511 control the storage means 102 and 512 and the transceivers 103 and 513. Specifically, the controllers 101 and 511 execute the methods stored in the storage means 102 and 512, respectively. The processors 101 and 511 transmit the aforementioned signals through the transceivers 103 and 513.

Landscapes

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

Abstract

Selon un mode de réalisation, la présente invention concerne un procédé pour le traitement efficace d'un signal dans un état activé de réduction de signalisation en mode veille (ISR) en mobilité de flux IP basée sur réseau (NB-IFOM) Le procédé, qui est un procédé de traitement de réduction de signalisation en mode veille (ISR) par un terminal dans un système de communication sans fil, peut comprendre les étapes suivantes: la vérification qu'une condition de désactivation d'ISR a été satisfaite; et la désactivation locale d'ISR lorsque la condition de désactivation d'ISR a été satisfaite, la condition de désactivation d'ISR incluant un cas où le terminal et une passerelle de réseau à commutation de paquets (PDN) fonctionnent sous une mobilité de flux IP basée sur réseau (NB-IFOM), un cas où le terminal est connecté à un réseau local sans fil (WLAN) par une gestion SCM ou est situé dans la zone de couverture d'un réseau local sans fil, un cas où une connexion de réseau PDN au terminal est établie et ensuite le terminal quitte la zone de suivi (TA) ou zone de routage (RA) existantes et se déplace vers une autre zone de suivi ou une autre zone de routage, et un cas où le terminal est actuellement dans un état activé d'ISR.
PCT/KR2015/006745 2014-12-24 2015-07-01 Procédé pour le traitement efficace de signal dans l'état activé de réduction de signalisation en mode veille en mobilité de flux ip baseé sur réseau WO2016104897A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201462096550P 2014-12-24 2014-12-24
US62/096,550 2014-12-24

Publications (1)

Publication Number Publication Date
WO2016104897A1 true WO2016104897A1 (fr) 2016-06-30

Family

ID=56150887

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/006745 WO2016104897A1 (fr) 2014-12-24 2015-07-01 Procédé pour le traitement efficace de signal dans l'état activé de réduction de signalisation en mode veille en mobilité de flux ip baseé sur réseau

Country Status (1)

Country Link
WO (1) WO2016104897A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109804703A (zh) * 2016-09-29 2019-05-24 索尼公司 电信设备和方法
CN110612744A (zh) * 2018-02-13 2019-12-24 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
CN112637906A (zh) * 2019-08-16 2021-04-09 华为技术有限公司 寻呼的方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140106620A (ko) * 2011-11-29 2014-09-03 인터디지탈 패튼 홀딩스, 인크 Ip 이동성 관리 방법
WO2014182057A1 (fr) * 2013-05-07 2014-11-13 엘지전자 주식회사 Procédé de désactivation d'une fonction d'isr pour un service de proximité

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140106620A (ko) * 2011-11-29 2014-09-03 인터디지탈 패튼 홀딩스, 인크 Ip 이동성 관리 방법
WO2014182057A1 (fr) * 2013-05-07 2014-11-13 엘지전자 주식회사 Procédé de désactivation d'une fonction d'isr pour un service de proximité

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Network based IP Flow Mobility (Release 13)", 3GPP TSGSSA, 3GPP TR 23.861 V1.12.0, 17 December 2014 (2014-12-17) *
CATT: "Solution to the Open Issues Related to SCM", S2-143879, 3GPP TSG-SA WG2 #106 S2-143879, 11 November 2014 (2014-11-11), San Francisco, California, USA *
ERICSSON: "UE Indication to Network in Solution 7", 3GPP TSG-SA WG2 #106 S2-144097, 11 November 2014 (2014-11-11), San Francisco, California, USA, pages 2 - 144097 *
NOKIA NETWORKS: "Paging Priority Setting in the MME", 3GPP TSG-SA WG2 #106 S2-144249, 11 November 2014 (2014-11-11), San Francisco, California, USA, pages 2 - 144249 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109804703A (zh) * 2016-09-29 2019-05-24 索尼公司 电信设备和方法
CN109804703B (zh) * 2016-09-29 2023-06-16 索尼公司 电信设备和方法
US11818776B2 (en) 2016-09-29 2023-11-14 Sony Group Corporation Telecommunications apparatus and methods
CN110612744A (zh) * 2018-02-13 2019-12-24 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
CN110612744B (zh) * 2018-02-13 2024-03-08 Oppo广东移动通信有限公司 无线通信的方法、终端设备和网络设备
CN112637906A (zh) * 2019-08-16 2021-04-09 华为技术有限公司 寻呼的方法和装置

Similar Documents

Publication Publication Date Title
WO2018128456A1 (fr) Procédé et terminal pour effectuer une commande d'accès dans un système de communication mobile de 5ème génération
WO2016159521A1 (fr) Procédé et équipement d'utilisateur pour exécuter une sélection de réseau et un acheminement de trafic
WO2015160215A2 (fr) Procédé permettant de communiquer des règles de routage
WO2016076606A1 (fr) Procédé et équipement d'utilisateur pour bloquer l'accès à un réseau par un acdc
WO2018231007A1 (fr) Procédé permettant de répondre à une demande et dispositif de réseau
WO2019198960A1 (fr) Procédé et smf permettant la prise en charge d'une qos
WO2019216526A1 (fr) Procédé et équipement utilisateur pour réaliser un contrôle d'accès en 5gs
WO2017142170A1 (fr) Procédé et terminal de création, modification, et libération de session dans un réseau de communications mobiles de prochaine génération
WO2018088812A1 (fr) Procédé et équipement utilisateur de transfert intercellulaire
WO2016003140A1 (fr) Procédé d'interdiction d'accès réseau pour chaque application et équipement utilisateur
WO2017171184A1 (fr) Procédé pour tentative d'accès réseau à partir d'une rat nb-iot
WO2017034352A1 (fr) Procédé de connexion de station de base et équipement utilisateur le mettant en œuvre
WO2014112826A1 (fr) Procédé et terminal permettant de déterminer un transfert pour le trafic déchargé sur un wlan
WO2015142048A1 (fr) Procédé d'exécution et équipement utilisateur pour procédure de demande de service
WO2018066919A1 (fr) Procédé de connexion à un réseau et équipement utilisateur
WO2018128519A1 (fr) Procédé par lequel un ue relais ayant une connexion avec un ue distant connecte un réseau dans un système de communication sans fil et appareil associé
WO2016024832A1 (fr) Procédé et équipement d'utilisateur servant à bloquer un accès au réseau en fonction de l'application
WO2015170858A1 (fr) Procédé pour traiter csfb ou srvcc pendant un service sipto
WO2014058242A1 (fr) Procédé de traitement de recherche de mobile et procédé permettant de relayer des données de liaison descendante
WO2015016546A1 (fr) Procédé de radiomessagerie et appareil pour service ims
WO2018079947A1 (fr) Procédé de prise en charge de mobilité d'équipement utilisateur dans un système de communication sans fil et dispositif associé
WO2016126109A1 (fr) Procédé et équipement d'utilisateur destinés à la sélection d'un réseau et au routage du trafic
WO2016105004A1 (fr) Procédé d'émission et de réception de capacité de nbifom dans un système de communication sans fil ainsi que dispositif associé
WO2015137631A1 (fr) Procédé pour la mise en œuvre de service de proximité, et dispositif utilisateur
WO2018088630A1 (fr) Procédé de transmission de message rrc et dispositif sans fil

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

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

Country of ref document: EP

Kind code of ref document: A1