[go: up one dir, main page]

WO2017171348A2 - Procédé d'exécution d'une opération relative à un enregistrement de localisation dans une structure de tranches dans un système de communication sans fil, et dispositif associé - Google Patents

Procédé d'exécution d'une opération relative à un enregistrement de localisation dans une structure de tranches dans un système de communication sans fil, et dispositif associé Download PDF

Info

Publication number
WO2017171348A2
WO2017171348A2 PCT/KR2017/003309 KR2017003309W WO2017171348A2 WO 2017171348 A2 WO2017171348 A2 WO 2017171348A2 KR 2017003309 W KR2017003309 W KR 2017003309W WO 2017171348 A2 WO2017171348 A2 WO 2017171348A2
Authority
WO
WIPO (PCT)
Prior art keywords
location registration
function
timer
network
periodic
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/KR2017/003309
Other languages
English (en)
Korean (ko)
Other versions
WO2017171348A3 (fr
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 WO2017171348A2 publication Critical patent/WO2017171348A2/fr
Publication of WO2017171348A3 publication Critical patent/WO2017171348A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration

Definitions

  • the following description relates to a wireless communication system, and more particularly, to a method and apparatus for performing an operation related to location registration in a slice structure.
  • Wireless communication systems are widely deployed to provide various kinds of communication services such as voice and data.
  • a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.).
  • multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency (SC-FDMA).
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • MCD division multiple access
  • MCDMA multi-carrier frequency division multiple access
  • MC-FDMA multi-carrier frequency division multiple access
  • D2D communication establishes a direct link between user equipments (UEs), and directly communicates voice and data between terminals without passing through an evolved NodeB (eNB).
  • UEs user equipments
  • eNB evolved NodeB
  • the D2D communication may include a scheme such as UE-to-UE communication, Peer-to-Peer communication, and the like.
  • the D2D communication scheme may be applied to machine-to-machine (M2M) communication, machine type communication (MTC), and the like.
  • M2M machine-to-machine
  • MTC machine type communication
  • D2D communication has been considered as a way to solve the burden on the base station due to the rapidly increasing data traffic.
  • the D2D communication unlike the conventional wireless communication system, since the data is exchanged between devices without passing through a base station, the network can be overloaded.
  • the D2D communication it is possible to expect the effect of reducing the procedure of the base station, the power consumption of the devices participating in the D2D, increase the data transmission speed, increase the capacity of the network, load balancing, cell coverage expansion.
  • V2X vehicle to everything
  • a technical task is to efficiently perform location registration, for example, location registration, under a network slicing structure.
  • the first MM function in a method in which a first mobility management (MM) function performs an operation related to location registration of a user equipment (UE) in a wireless communication system, the first MM function is determined from the UE.
  • An embodiment of the present invention provides a first MM function apparatus for performing an operation related to location registration of a user equipment (UE) in a wireless communication system, the apparatus comprising: a transceiver; And a processor, wherein the processor is further configured to receive an attach request from a UE via the transceiver, the first MM function determines a first periodic location registration timer value, and sets the first periodic location registration timer value. And transmitting a response to the attach request to the UE, receiving information including a second periodic location registration timer, and comparing the first periodic location registration timer value with the second periodic location registration timer value.
  • the first MM function apparatus determines a timer having a small value as a third periodic position registration timer as a result of the comparison.
  • the information including the second periodic location registration timer may be a location registration service subscription request.
  • the location registration service subscription request is transmitted from the second MM function of the selected slice by the UE performing a session setup request, and the first MM function transmits the third periodic location registration timer to the second MM function. Can be.
  • the second MM function may be configured to transmit the location registration subscription request to an MM function that transmits and receives a NAS message with the UE.
  • the first MM function may transmit a session setup request to the second MM function.
  • the first MM function may also determine a third location registration range when determining the third periodic location registration timer.
  • the third location registration range may be an area in which the first location registration range determined by the first MM function and the second location registration range determined by the second MM function are common.
  • the present invention it is possible to efficiently provide mobility management when network slicing is used. Specifically, according to the present invention, due to the different timer for each slice, it is possible to eliminate the inefficiency of the UE to perform location registration repeatedly.
  • FIG. 1 is a diagram illustrating a schematic structure of an EPS (Evolved Packet System) including an Evolved Packet Core (EPC).
  • EPS Evolved Packet System
  • EPC Evolved Packet Core
  • FIG. 2 is an exemplary view showing the architecture of a general E-UTRAN and EPC.
  • 3 is an exemplary view showing the structure of a radio interface protocol in a control plane.
  • FIG. 4 is an exemplary view showing the structure of a radio interface protocol in a user plane.
  • 5 is a flowchart illustrating a random access procedure.
  • RRC radio resource control
  • FIG 8 illustrates a possible scenario when the UE is served from one or more network slices.
  • FIG. 9 illustrates an architecture reference model usable in a 5G system.
  • 10 to 11 illustrate a method of performing a terminal location registration related operation according to each embodiment of the present invention.
  • FIG. 12 is a diagram illustrating a configuration of a node device according to an embodiment of the present invention.
  • each component or feature may be considered to be optional unless otherwise stated.
  • Each component or feature may be embodied in a form that is not combined with other components or features.
  • some components and / or features may be combined to form an embodiment of the present invention.
  • the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
  • Embodiments of the present invention may be supported by standard documents disclosed in relation to at least one of the Institute of Electrical and Electronics Engineers (IEEE) 802 series system, 3GPP system, 3GPP LTE and LTE-A system, and 3GPP2 system. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.
  • IEEE Institute of Electrical and Electronics Engineers
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • Evolved Packet System A network system composed of an Evolved Packet Core (EPC), which is a packet switched (PS) core network based on Internet Protocol (IP), and an access network such as LTE / UTRAN.
  • EPC Evolved Packet Core
  • PS packet switched
  • IP Internet Protocol
  • UMTS is an evolutionary network.
  • NodeB base station of GERAN / UTRAN. It is installed outdoors and its coverage is macro cell size.
  • eNodeB base station of E-UTRAN. It is installed outdoors and its coverage is macro cell size.
  • UE User Equipment
  • the UE may be referred to in terms of terminal, mobile equipment (ME), mobile station (MS), and the like.
  • the UE may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smart phone, a multimedia device, or the like, or may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.
  • the term UE or UE may refer to an MTC device.
  • HNB Home NodeB
  • HeNB Home eNodeB: A base station of an EPS network, which is installed indoors and its coverage is micro cell size.
  • Mobility Management Entity A network node of an EPS network that performs mobility management (MM) and session management (SM) functions.
  • Packet Data Network-Gateway (PDN-GW) / PGW A network node of an EPS network that performs UE IP address assignment, packet screening and filtering, charging data collection, and the like.
  • SGW Serving Gateway
  • Non-Access Stratum Upper stratum of the control plane between the UE and the MME.
  • Packet Data Network A network in which a server supporting a specific service (eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server, etc.) is located.
  • a server supporting a specific service eg, a Multimedia Messaging Service (MMS) server, a Wireless Application Protocol (WAP) server, etc.
  • MMS Multimedia Messaging Service
  • WAP Wireless Application Protocol
  • PDN connection A logical connection between the UE and the PDN, represented by one IP address (one IPv4 address and / or one IPv6 prefix).
  • RAN Radio Access Network: a unit including a NodeB, an eNodeB and a Radio Network Controller (RNC) controlling them in a 3GPP network. It exists between UEs and provides a connection to the core network.
  • RNC Radio Network Controller
  • HLR Home Location Register
  • HSS Home Subscriber Server
  • PLMN Public Land Mobile Network
  • Proximity Service (or ProSe Service or Proximity based Service): A service that enables discovery and direct communication between physically close devices or communication through a base station or through a third party device. In this case, user plane data is exchanged through a direct data path without passing through a 3GPP core network (eg, EPC).
  • EPC 3GPP core network
  • EPC Evolved Packet Core
  • FIG. 1 is a diagram illustrating a schematic structure of an EPS (Evolved Packet System) including an Evolved Packet Core (EPC).
  • EPS Evolved Packet System
  • EPC Evolved Packet Core
  • SAE System Architecture Evolution
  • SAE is a research project to determine network structure supporting mobility between various kinds of networks.
  • SAE aims to provide an optimized packet-based system, for example, supporting various radio access technologies on an IP basis and providing enhanced data transfer capabilities.
  • the EPC is a core network of an IP mobile communication system for a 3GPP LTE system and may support packet-based real-time and non-real-time services.
  • a conventional mobile communication system i.e., a second generation or third generation mobile communication system
  • the core network is divided into two distinct sub-domains of circuit-switched (CS) for voice and packet-switched (PS) for data.
  • CS circuit-switched
  • PS packet-switched
  • the function has been implemented.
  • the sub-domains of CS and PS have been unified into one IP domain.
  • EPC IP Multimedia Subsystem
  • the EPC may include various components, and in FIG. 1, some of them correspond to a serving gateway (SGW), a packet data network gateway (PDN GW), a mobility management entity (MME), and a serving general packet (SGRS) Radio Service (Supporting Node) and Enhanced Packet Data Gateway (ePDG) are shown.
  • SGW serving gateway
  • PDN GW packet data network gateway
  • MME mobility management entity
  • SGRS serving general packet
  • Radio Service Upporting Node
  • ePDG Enhanced Packet Data Gateway
  • the SGW acts as a boundary point between the radio access network (RAN) and the core network, and is an element that functions to maintain a data path between the eNodeB and the PDN GW.
  • the SGW serves as a local mobility anchor point. That is, packets may be routed through the SGW for mobility in the E-UTRAN (Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later).
  • E-UTRAN Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later.
  • SGW also provides mobility with other 3GPP networks (RANs defined before 3GPP Release-8, such as UTRAN or GERAN (Global System for Mobile Communication (GSM) / Enhanced Data Rates for Global Evolution (EDGE) Radio Access Network). It can also function as an anchor point.
  • RANs defined before 3GPP Release-8 such as UTRAN or GERAN (Global System for Mobile Communication (GSM) / Enhanced Data Rates for Global Evolution (EDGE) Radio Access Network). It can also function as an anchor point.
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data Rates for Global Evolution
  • the PDN GW corresponds to the termination point of the data interface towards the packet data network.
  • the PDN GW may support policy enforcement features, packet filtering, charging support, and the like.
  • 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 SGW and the PDN GW are configured as separate gateways, two gateways may be implemented according to a single gateway configuration option.
  • the MME is an element that performs signaling and control functions to support access to the network connection of the UE, allocation of network resources, tracking, paging, roaming and handover, and the like.
  • the MME controls control plane functions related to subscriber and session management.
  • the MME manages a number of eNodeBs and performs signaling for the selection of a conventional gateway for handover to other 2G / 3G networks.
  • the MME also performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.
  • SGSN handles all packet data, such as user's mobility management and authentication to other 3GPP networks (eg GPRS networks).
  • 3GPP networks eg GPRS networks.
  • 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 an IP service network provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access. (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 handovers) (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 related control and mobility support between the GPRS core and SGW's 3GPP anchor functionality.It also provides user plane tunneling if no direct tunnel is established.
  • the 3GPP Anchor function of Serving GW In addition, if Direct Tunnel is not established, it provides the user plane tunnelling.
  • S5 Reference point providing user plane tunneling and tunnel management between the SGW and the PDN GW.
  • the PDN may be an operator external public or private PDN or, for example, an in-operator PDN for the provision of IMS services. It is the reference point between the PDN GW and the packet data network.
  • 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.
  • 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.
  • FIG. 2 is an exemplary view showing the architecture of a general E-UTRAN and EPC.
  • an eNodeB can route to a gateway, schedule and send paging messages, schedule and send broadcaster channels (BCHs), and resources in uplink and downlink while an RRC (Radio Resource Control) connection is active.
  • BCHs broadcaster channels
  • RRC Radio Resource Control
  • paging can occur, LTE_IDLE state management, user plane can perform encryption, SAE bearer control, NAS signaling encryption and integrity protection.
  • FIG. 3 is an exemplary diagram illustrating a structure of a radio interface protocol in a control plane between a terminal and a base station
  • FIG. 4 is an exemplary diagram illustrating a structure of a radio interface protocol in a user plane between a terminal and a base station. .
  • the air 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 widely 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 medium access control (MAC) layer of the second layer serves to map various logical channels to various transport channels, and also logical channel multiplexing to map several logical channels to one transport channel. (Multiplexing).
  • the MAC layer is connected to the upper layer RLC layer by a logical channel, and 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
  • 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.
  • 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 If 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 If 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).
  • 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 NAS layer performs functions such as default bearer management and dedicated bearer management, and is responsible for controlling the terminal to use the PS service from the network.
  • 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 a QoS characteristic of a maximum bit rate (MBR) or / and a guaranteed bit rate (GBR).
  • 5 is a flowchart illustrating a random access procedure in 3GPP LTE.
  • the random access procedure is used for the UE to get UL synchronization with the base station or to be allocated UL radio resources.
  • the UE receives a root index and a physical random access channel (PRACH) configuration index from the eNodeB.
  • 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.
  • the UE sends the randomly selected random access preamble to the eNodeB.
  • the UE selects one of the 64 candidate random access preambles.
  • the corresponding subframe is selected by the PRACH configuration index.
  • the UE transmits the selected random access preamble in the selected subframe.
  • the eNodeB Upon receiving the random access preamble, the eNodeB sends a random access response (RAR) to the UE.
  • RAR random access response
  • the random access response is detected in two steps. First, the UE detects a PDCCH masked with random access-RNTI (RA-RNTI). The UE 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 is in a logical connection with an entity of the RRC layer of the eNodeB.
  • the RRC state is referred to as an RRC connected state.
  • the non-state is called the 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.
  • the UE in the idle state can not be identified by the eNodeB, the core network (core network) is managed by the tracking area (Tracking Area) unit that is larger than the cell unit.
  • the tracking area is a collection unit of cells. That is, the idle state (UE) is determined only in the presence of the UE in a large area, and in order to receive a normal mobile communication service such as voice or data, the UE must transition to the connected state (connected state).
  • the UE When a user first powers up a UE, the UE first searches for an appropriate cell and then stays in an idle state in that cell. When the UE staying in the idle state needs to establish an RRC connection, the UE establishes an RRC connection with the RRC layer of the eNodeB through an RRC connection procedure and transitions to an RRC connected state. .
  • the UE in the idle state needs to establish an RRC connection. For example, a user's call attempt or uplink data transmission is required, 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 a UE sends an RRC connection request message to an eNodeB, an eNodeB sends an RRC connection setup message to the UE, and a UE completes RRC connection setup to the eNodeB. (RRC connection setup complete) message is sent. This process will be described in more detail with reference to FIG. 6 as follows.
  • the eNB When the RRC connection request message is received from the UE, the eNB accepts the RRC connection request of the UE when the radio resources are sufficient, and transmits an RRC connection setup message, which is a response message, to the UE. .
  • the UE When the UE receives the RRC connection setup message, it transmits an RRC connection setup complete message to the eNodeB. When the UE successfully transmits an RRC connection establishment message, the UE establishes an RRC connection with the eNodeB and transitions to the RRC connected mode.
  • the UE performs a tracking area update (TAU) to manage the reachability and location of the UE in the idle mode.
  • TAU tracking area update
  • the UE periodically performs a TAU (periodic TAU or P-TAU) even if the MME does not depart from the range of tracking the location of the UE. At this time, P-TAU is performed based on a periodic location registration timer.
  • Table 2 below shows the periodic tracking area update timer (see T3412 and TS 24.301).
  • the timer value is included in the ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT message in the network and provided to the UE.
  • the network may provide the UE with an longer periodic tracking area update timer to reduce network load from P-TAU signaling.
  • the network may provide the UE with an longer periodic tracking area update timer to reduce network load from P-TAU signaling.
  • Table 3 below is the TAU Accept message format described in TS 24.301.
  • the markings 9.x, 9.x.x.x, etc. in the table are indexes in the TS 24.301 document.
  • Protocol discriminator 9 M V 1/2 Security header type Security header type 9.3.1 M V 1/2 Tracking area update accept message identity Message type 9.8 M V One EPS update result EPS update result 9.9.3.13 M V 1/2 Spare half octet Spare half octet 9.9.2.9 M V 1/2 5A T3412 value GPRS timer 9.9.3.16 O TV 2 50 GUTI EPS mobile identity 9.9.3.12 O TLV 13 54 TAI list Tracking area identity list 9.9.3.33 O TLV 8-98 57 EPS bearer context status EPS bearer context status 9.9.2.1 O TLV 4 13 Location area identification Location area identification 9.9.2.2 O TV 6 23 MS identity Mobile identity 9.9.2.3 O TLV 7-10 53 EMM cause EMM cause 9.9.3.9 O TV 2 17 T3402 value GPRS timer 9.9.3.16 O TV 2 59 T3423 value GPRS timer 9.9.3.16 O TV 2 4A Equivalent PLMNs PLMN list 9.9.2.8
  • the MME shall include the T3412 value IE in the normal and combined TAU procedures.
  • the MME may include the T3412 value IE in the periodic TAU procedure.
  • the network may include a T3412 extended value IE to provide a longer periodic tracking area update timer to the UE.
  • the P-TAU timer T3412 and the longer P-TAU timer T3412 extended value may be set to values of various sizes such as GPRS Timer and GPRS Timer 3 disclosed in TS 24.008 and may be provided to the UE.
  • network slicing may include three layers, a service instance layer, a network slice instance layer, and a resource layer.
  • the service instance layer represents the service to be supported (end user service or business service). Each of these services may be represented by a service instance.
  • the service instance may represent an operator service or a third party provided service.
  • Network slice instances provide the network characteristics required for service instances. Network slice instances can be shared among multiple service instances provided by network operators.
  • the UE may be provided with service from one or more network slices as illustrated in FIG.
  • the UE may be provided with services from multiple slices, and may send and receive traffic through several slices at the same time, but may also exchange traffic through only one slice at a time.
  • the UE when Service # 1 is provided with Slice # 1 and Service # 2 is provided with Slice # 2, the UE generates mobile originated (MO) traffic for Service # 1. Can be sent through.
  • MO mobile originated traffic for Service # 1.
  • Another example is when there is no traffic transmitted and received by the UE (in a mobile communication system such as EPS, the UE may be in the IDLE state in this case) and mobile terminated (MT) traffic for Service # 2 occurs. This can be delivered via Slice # 2.
  • the UE may be served from one or more network slices, which may be in one of three scenarios as illustrated in FIG. 8.
  • group A targets logical separation / isolation between CN instances where the UE obtains service from different network slices and different CN instances.
  • This group features independent subscription management / mobility management for each network slice dealing with the UE, with the potential side effect of additional signaling in the network and radio.
  • isolation in the CN portion of the network is easiest to achieve.
  • Group B assumes that some network functions are common among the network slices, while others are in separate network slices.
  • Group C assumes that control plane processing is common between slices while the user plane is processed with other network slices.
  • MME has been divided into Core Access and Mobility Management Function (AMF) and Session Management Function (SMF) in 5G CN (Core Network).
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • 5G CN Core Network
  • the NAS interaction and mobility management (MM) with the UE are performed by the AMF
  • the session management (SM) is performed by the SMF.
  • the SMF manages a user plane function (UPF), which has a user-plane function, that is, a gateway for routing user traffic.
  • the SMF is responsible for the control-plane portion of the S-GW and the P-GW in the conventional EPC.
  • the user-plane part can be considered to be in charge of the UPF.
  • PDU Protocol Data Unit
  • the PDU session refers to an association between the UE and the DN providing the PDU connectivity service of the Ethernet type or the unstructured type as well as the IP type.
  • UDM Unified Data Management
  • PCF Policy Control Function
  • the functions can be provided in an expanded form to satisfy the requirements of the 5G system. For details on the 5G system architecture, each function and each interface, TS 23.501 is applicable.
  • Group A all control-plane and user-plane functions are included in each slice.
  • AMF, SMF, and UPF are all included in each slice.
  • AMFs in charge of mobility management are commonly located instead of being included for each slice. That is, there is one AMF in common regardless of how many slices a UE is served by.
  • SMF responsible for session management and UPF which is a gateway, are included in each slice.
  • SMFs in charge of session management are commonly located instead of being included in each slice. That is, there is one SMF in common regardless of how many slices a UE is served by.
  • SMF responsible for mobility management and UPF which is a gateway, are included in each slice.
  • the access management function that the UE performs authentication upon initial registration is commonly used regardless of the slice, and the functions, such as reachability and location tracking, are included in the slice.
  • SMF and UPF are also included in the slice.
  • Group C all control-plane functions are commonly located. Therefore, AMF and SMF are not included in each slice, and there is a common one regardless of how many slices a UE is served. UPF, on the other hand, is included in each slice.
  • each slice may have a control plane (CP) function, if such CP function is a function of the MM or MM (ie reachability, location tracking, etc.).
  • CP control plane
  • the P-TAU can be controlled by a plurality of MM functions.
  • the CP function is shared by the slices as in Group C, a plurality of CP instances may be running for each slice. In this case, the P-TAU may be controlled by the MM function belonging to each CP instance.
  • the MM function (MME in the case of EPS) does not use a constant value as a P-TAU timer value provided to the UE, but various values based on network conditions, operator policy, local configuration, subscriber information, etc. It may be set to provide to the UE. This may also be the case in a network system structure sliced to provide various services. That is, a periodic location registration timer may be set in consideration of a service provided by each slice and / or reflecting a situation of each slice (eg, signaling load of a slice). At the same time, if a UE receiving services from multiple slices needs to perform periodic location registration with multiple CP functions in the network, in this case, a different location registration timer causes the UE to perform periodic location registration. do.
  • the CP function may inform the UE of the periodic location registration timer. It is unclear whether to provide. Therefore, the following describes a method for efficiently providing an MM under a network slicing structure according to an embodiment of the present invention.
  • the MM function may be a part of the MM function or a periodic location registration function.
  • a slice may mean the same as a network slice and a network slice instance.
  • step S1001 the UE (UE-1 in the figure) transmits an attach request to perform an attach to the network.
  • the UE may request an operation of setting up a session with an attach request.
  • the session setup operation may be requested to the network.
  • the session may be a PDU session or a PDN connection.
  • the UE transmits an attach request message to the network.
  • the UE may transmit a general MM Request message to the network.
  • slice # 1 is selected for the UE. Selection of the slice includes information (APN, service descriptor, application related information, UE capability information, etc.) included in the message (attach request message and / or session setup request message) received from the UE described in step S1001, RAT / RAN One or more of the type / information, subscriber information, and network configuration information may be used.
  • information API, service descriptor, application related information, UE capability information, etc.
  • Attach request message and / or session setup request message received from the UE described in step S1001
  • RAT / RAN One or more of the type / information, subscriber information, and network configuration information may be used.
  • MM function # 1 which is an MM function belonging to slice # 1 (or operating for slice # 1), determines a first periodic location registration (update) timer (ie, P_timer # 1) value.
  • the first periodic location registration timer is used to determine the characteristics of the service provided by the slice, the situation of the user plane function of the slice (e.g. load / congestion of the gateway of the slice), the situation of the control plane function of the slice (e.g. signaling signaling of the slice). / Congestion), subscriber information, and network settings.
  • the MM function # 1 may also determine the location registration range (ie, A # 1) for the UE while determining the first periodic location registration timer value. This may be determined based on one or more of characteristics of a service provided by the slice, a service area of a user plane function of the slice, subscriber information, and network configuration.
  • the location registration range indicates an area / range in which the UE should perform location registration with the network if it is out of the range.
  • the MM function # 1 transmits a response / allow message for the attach request to the UE.
  • the response / allow message for the attach request may include the first periodic location registration timer value and / or location registration range.
  • the UE stores the received first location registration timer value (ie, sets its location registration timer P_timer to the received timer value P_timer # 1). Then start P_timer # 1.
  • MM function # 1 also manages a periodic location registration timer value for the UE and starts it. The UE also stores the received location registration range.
  • step S1005 P_timer, the location registration timer of the UE, expires (step S1005), and the UE performs location registration with the network. That is, in step S1006, the UE transmits a location update request, and in step S1007, the MM function # 1 transmits a location update acceptance message in response. In step S1008, the UE sends a session setup request message to the network for setting up an additional session. These messages are delivered to MM function # 1 in the exchange of NAS messages with the UE. That is, the second MM function and the like may be configured to transmit the location registration subscription request to the MM function for transmitting and receiving NAS messages with the UE.
  • step S1009 slice # 2 is selected for the UE.
  • the selection criteria are as described above in step S1002.
  • the MM function # 1 delivers the session setup request received from the UE to the MM function # 2 which belongs to slice # 2 or operates for slice # 2, thereby completing the session setup. That is, the MM function # 1 transmits a session setup request message to the MM function # 2 (step S1010).
  • step S1011 the MM function # 2 determines a second periodic location registration timer (ie, P_timer # 2) value and a location registration range (ie, A # 2) for the UE. For details, refer to step S1003.
  • the MM function # 2 transmits a location registration service subscription request including the determined P_timer # 2 value and A # 2 to the MM function # 1, which is an MM function that exchanges a NAS message with the UE. That is, the second MM function may be configured to transmit the location registration subscription request to an MM function that transmits and receives a NAS message with the UE.
  • the purpose of the location registration service subscription request is to inform the MM function # 2 that it wants to check reachability with a period of P_timer # 2 for the UE, or vice versa, if the MM function # 2 does not reach reachability with a period of P_timer # 2 for the UE. It may be a request.
  • the purpose of the location registration service subscription request may be to request that the UE notifies when it leaves the A # 2 area.
  • the MM function # 1 transmits a response to the location registration service subscription request to the MM function # 2.
  • the MM function # 1 compares the first periodic position registration timer value set by the self and the second periodic position registration timer value received from the MM function # 2 to check / recognize the smallest value (step S1014). .
  • a small value (the smallest value when the timer to be compared is received from several MM functions) is determined as a new P_timer value (third periodic location registration timer) for the UE.
  • P_timer # 2 is smaller than P_timer # 1.
  • step S1015 the MM function # 1 compares the position registration range set by itself with the position registration range received from the MM function # 2 to check / recognize overlapping ranges (common areas). This range is then determined as a new location registration range for the UE.
  • a # 1 includes TAI # 1, TAI # 2, TAI # 3, TAI # 4, and TAI # 5, and A # 2 represents TAI # 2, TAI # 3, TAI # 4, and TAI # 6. It is assumed to be included. Accordingly, the newly determined location registration range A # 3 includes TAI # 2, TAI # 3, and TAI # 4.
  • the MM function # 1 transmits a message indicating that the information on location registration has been changed to the UE (step S1016).
  • a message location update information message
  • the UE having received the location update information message stores the received location registration timer value and location registration range. And start the periodic location registration timer according to the new location registration timer value.
  • the response message is then sent to the MM function #.
  • MM function # 1 also manages a periodic location registration timer value for the UE and starts it.
  • the MM function # 1 informs the MM function # 2 of the P_timer value and location registration range provided to the UE (via a Notify message). It also informs the UE that it is reachable. This is for re-starting the P_timer value for the UE managed by the MM function of another slice. If the MM function # 2 requests the MM function # 1 to notify the UE only when the UE does not reachability in the period of P_timer # 2, this notification may not be transmitted.
  • the MM function # 1 may start and manage the P_timer value for each slice.
  • the UE can not only reach reachability of the UE to the slice corresponding to the P_timer period of each slice, or vice versa, but only when not reachable. This applies throughout the present invention.
  • Steps S1020 to S1024 describe the case where the timer of the UE expires. Specifically, when the UE's own location registration timer P_timer expires (step S1020), the UE performs location registration with the network (steps S1021 to S1022). The UE restarts P_timer, which is a location registration timer. The MM function # 1 also restarts P_timer, which is a location registration timer for the UE.
  • the MM function # 1 notifies the MM function # 2 that the UE is reachable (via a Notify message). This may be an explicit or implicit notification that the UE has performed location registration.
  • the MM function # 2 re-starts P_timer, which is a location registration timer for the UE. If, in S1022, the MM function # 1 allocates the location registration range to a new location registration range other than A # 3, unlike this shown in FIG. 10, this information is provided to the MM function # 2.
  • Steps S1025 to S1029 are explanations for the case where the UE is out of the location registration range as the UE moves.
  • the UE moves out of the location registration range A # 3 (step S1025).
  • the UE performs location registration with the network (steps S1026 to S1027).
  • the MM function # 1 responds by allocating a new location registration range A # 4 to the UE.
  • the UE re-starts P_timer, which is a location registration timer.
  • the MM function # 1 also restarts P_timer, which is a location registration timer for the UE.
  • the MM function # 1 informs the MM function # 2 of a new location registration range of the UE (via a Notify message).
  • the MM function # 2 re-starts P_timer, which is a location registration timer for the UE.
  • the MM function # 1 may notify the MM function # 2 of the reachability of the UE based on a periodic location registration timer requested by the MM function # 2, which is the MM function of another slice, or notify the UE if the UE has become unreachable.
  • the second embodiment is an example in which a node / entity performing a function of the MM controller exists separately from the MM function.
  • the MM controller may be referred to as an MM coordinator, an MM anchor point, a mobility controller, a mobility coordinator, a mobility anchor point, or a central MM function.
  • the MM controller may control the MM function for all slices belonging to a specific slice serving the UE but serving the UE, and control the MM function for all slices serving the UE without belonging to the specific slice.
  • the MM function may be controlled for all slices serving the UE belonging to the slice including the MM function.
  • the unit of location registration is a unit of cell, a location registration area of RAN, a tracking area unit, a TA collection unit, a location registration area unit, a location registration area collection unit, a CN location registration area unit CN location registration area Vowel units may vary. This also applies to the unit of location registration of the first embodiment.
  • a UE attaches to a network.
  • the UE may request an operation of setting up a session with an attach request.
  • the session setup operation may be requested to the network.
  • the MM controller may forward the session setup request to the network function in charge of the session setup if the session setup request is included in the UE.
  • the session may be interpreted as a PDU session or a PDN connection.
  • the UE transmits the Attach Request message to the network.
  • the UE may transmit the general MM Request message to the network.
  • slice # 1 is selected for the UE.
  • the selection criteria may include information (eg, APN, service descriptor, application related information, UE capability information, etc.) included in the message received from the UE described in step S1101 (that is, an attach request message and / or a session setup request message), RAT / One or more of RAN type / information, subscriber information, and configuration information of a network may be used.
  • MM function # 1 which is an MM function belonging to slice # 1 or operating for slice # 1, determines a periodic location registration timer (ie, P_timer # 1) value.
  • the MM function # 1 transmits a location registration service subscription request including the determined P_timer # 1 value to the MM controller.
  • the purpose of the location registration service subscription request is to inform the MM function # 1 that it wants to check reachability with a period of P_timer # 1 for the UE, or vice versa, when the MM function # 1 does not reach reachability with a period of P_timer # 1 for the UE. It may be a request.
  • step S1105 the MM controller transmits a response to the location registration service subscription request to the MM function # 1. At this time or later, the MM controller may transmit information indicating that the UE is reachable to the MM function # 1.
  • step S1106 the MM controller sends a response / allow message for the attach request to the UE.
  • the periodic location registration timer value is included.
  • the UE stores the received location registration timer value (ie, sets its location registration timer P_timer to the received timer value P_timer # 1). And start it.
  • the MM controller also manages the periodic location registration timer value for the UE and starts it.
  • step S1107 the UE's own location registration timer P_timer expires.
  • steps S1108 to S1109 the UE performs location registration with the network.
  • the MM controller notifies (via a Notify message) that the UE is reachable to the MM function # 1. This may be an explicit or implicit notification that the UE has performed location registration.
  • the MM function # 1 restarts P_timer, which is a location registration timer for the UE.
  • step S1114 the MM function # 1 is requested to inform the UE when the reachability is not reachable in the period of P_timer # 1, steps S1110 to 11 may be omitted.
  • the MM controller notifies the MM function # 1 that the UE is no longer reachable. This may be an explicit or implicit notification that the UE has not performed location registration. The same applies to MM functions belonging to different slices. That is, it is applied throughout the present invention.
  • step S1112 the UE sends a request message to set up an additional session to the network.
  • These messages may be received by the MM controller, or may be received by session management (SM) related network functions. In the latter case, it may be a function that performs an SM control function for all slices in the same form as an SM controller, or may be an SM function belonging to a slice in which a session is formed by the session setup request.
  • SM session management
  • step S1113 slice # 2 is selected for the UE.
  • the selection criteria refer to step S1102.
  • MM function # 2 which is an MM function belonging to slice # 2 or operating for slice # 2, determines a periodic location registration timer (ie, P_timer # 2) value. See step S1103 for details.
  • the MM function # 2 transmits a message including P_timer # 2 to the MM controller. This is the same operation performed by the MM function # 1 and the MM controller in steps S1104 to S1105.
  • step S1117 the MM controller checks / recognizes the smallest value by comparing the periodic location registration timer value (ie, P_timer value) received from all slices serving the UE. This value is then determined as a new P_timer value for the UE.
  • P_timer value the periodic location registration timer value
  • step S1118 if the newly determined P_timer value is smaller than the P_timer value previously provided to the UE, the MM controller sends a message informing the UE of the new P_timer value.
  • P_timer # 2 is smaller than P_timer # 1. Accordingly, a message including a P_timer # 2 value, which is a new P_timer value, is transmitted to the UE.
  • step S1119 the UE, which has received this, stores the received location registration timer value (ie, sets its location registration timer P_timer to the received timer value P_timer # 2). And start it.
  • the MM controller also manages the periodic location registration timer value for the UE and starts it.
  • the MM controller starts the newly adjusted P_timer value, and thus slices other slices (that is, slices other than the slice providing the P_timer value on which the new P_timer value is based). ) (Via Notify message) that the UE is reachable. This is to re-start the P_timer value for the UE managed by the MM function of each slice. If the MM function # 1 requests the UE to notify the UE when it is not reachable with a period of P_timer # 1, this notification is not transmitted.
  • the MM controller may start and manage the P_timer value for each slice.
  • the UE can not only reach reachability of the UE to the slice corresponding to the P_timer period of each slice, or vice versa, but only when not reachable. This applies throughout the present invention.
  • step S1122 the UE's own location registration timer P_timer expires.
  • steps S1123 to S1124 the UE performs location registration with the network.
  • steps S1125 to S1126 the MM controller informs MM function # 2 that the UE is reachable (via a Notify message). This may be an explicit or implicit notification that the UE has performed location registration.
  • the MM function # 2 re-starts P_timer, which is a location registration timer for the UE.
  • the MM controller may notify the MM function # 1 of the reachability of the UE based on the periodic location registration timer requested by the MM function # 1.
  • the MM controller may notify each MM function of the reachability of the UE based on the periodic location registration timer requested by the MM function of each slice, or notify the UE when the UE has become unreachable.
  • the MM function is in / belongs to the CN (Core Network), but otherwise i) if the RAN function has an MM function and the MM controller is also in the RAN, ii) there is an MM function in the RAN slice and the MM controller Is in the CN, iii) the MM function in the CN slice and the MM controller can be extended even in the RAN.
  • the MM controller described the function of adjusting the periodic position registration timer value differently for each slice, but this is also applicable when the position registration range (for example, TAI list in EPS) is set differently for each slice. . In this case, a smaller location registration range can be provided to the UE. Accordingly, the MM controller may simultaneously adjust the periodic location registration timer value and the location registration range.
  • the position registration range for example, TAI list in EPS
  • the RAN (or AN: Access network) is illustrated as being common regardless of the slice, but the RAN may be different for each slice.
  • the same RAT or RAN is also sliced so that an appropriate RAN slice may be selected, or a different RAN may be selected because the RAT is different.
  • the UE exchanges a message with the network, it may be in the form of a NAS message or an AS message.
  • FIG. 12 is a diagram showing the configuration of a preferred embodiment of a terminal device and a network node device according to an example of the present invention.
  • the terminal device 100 may include a transceiver 110, a processor 120, and a memory 130.
  • the transceiver 110 may be configured to transmit various signals, data and information to an external device, and to receive various signals, data and information to an external device.
  • the terminal device 100 may be connected to an external device by wire and / or wirelessly.
  • the processor 120 may control the overall operation of the terminal device 100, and may be configured to perform a function of the terminal device 100 to process and process information to be transmitted and received with an external device.
  • the memory 130 may store the processed information for a predetermined time and may be replaced with a component such as a buffer (not shown).
  • the processor 120 may be configured to perform a terminal operation proposed in the present invention.
  • the network node device 200 may include a transceiver 210, a processor 220, and a memory 230.
  • the transceiver 210 may be configured to transmit various signals, data and information to an external device, and to receive various signals, data and information to an external device.
  • the network node device 200 may be connected to an external device by wire and / or wirelessly.
  • the processor 220 may control the overall operation of the network node device 200, and may be configured to perform a function of calculating and processing information to be transmitted / received with an external device.
  • the memory 230 may store the processed information for a predetermined time and may be replaced with a component such as a buffer (not shown).
  • the processor 220 may be configured to perform the network node operation proposed in the present invention.
  • the processor 220 receives an attach request from the UE through the transmission and reception apparatus, the first MM function determines a first periodic location registration timer value, and includes the first periodic location registration timer value. Transmit a response to the attach request to the UE, receive information including a second periodic location registration timer, compare the first periodic location registration timer value with the second periodic location registration timer value, As a result of the comparison, a timer having a small value may be determined as a third periodic location registration timer.
  • the specific configuration of the terminal device 100 and the network device 200 as described above may be implemented so that the above-described matters described in various embodiments of the present invention can be applied independently or two or more embodiments are applied at the same time, overlapping The description is omitted for clarity.
  • Embodiments of the present invention described above may be implemented through various means.
  • embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
  • a method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). It may be implemented by field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, and the like.
  • the method according to the embodiments of the present invention may be implemented in the form of an apparatus, procedure, or function for performing the above-described functions or operations.
  • the software code may be stored in a memory unit and driven by a processor.
  • the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.

Landscapes

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

Abstract

Un mode de réalisation de la présente invention concerne un procédé pour l'exécution, par une première fonction de gestion de mobilité (MM), d'une opération relative à un enregistrement de localisation d'un équipement d'utilisateur (UE) dans un système de communication sans fil. Le procédé comprend les étapes consistant à : recevoir une demande de rattachement, d'un UE, par une première fonction MM; déterminer une première valeur de temporisateur d'enregistrement de localisation périodique, par la première fonction MM; transmettre une réponse à la demande de rattachement, la réponse contenant la première valeur de temporisateur d'enregistrement de localisation périodique, à l'UE, par la première fonction MM; recevoir des informations comprenant un deuxième temporisateur d'enregistrement de localisation périodique, par la première fonction MM; comparer la première valeur de temporisateur d'enregistrement de localisation périodique à une valeur du deuxième temporisateur d'enregistrement de localisation périodique, par la première fonction MM; et déterminer, en tant qu'un troisième temporisateur d'enregistrement de localisation périodique, un temporisateur ayant la plus petite valeur déterminée suite à la comparaison, par la première fonction MM.
PCT/KR2017/003309 2016-03-28 2017-03-28 Procédé d'exécution d'une opération relative à un enregistrement de localisation dans une structure de tranches dans un système de communication sans fil, et dispositif associé Ceased WO2017171348A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662314351P 2016-03-28 2016-03-28
US62/314,351 2016-03-28

Publications (2)

Publication Number Publication Date
WO2017171348A2 true WO2017171348A2 (fr) 2017-10-05
WO2017171348A3 WO2017171348A3 (fr) 2018-09-07

Family

ID=59964942

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/003309 Ceased WO2017171348A2 (fr) 2016-03-28 2017-03-28 Procédé d'exécution d'une opération relative à un enregistrement de localisation dans une structure de tranches dans un système de communication sans fil, et dispositif associé

Country Status (1)

Country Link
WO (1) WO2017171348A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019074344A1 (fr) * 2017-10-13 2019-04-18 Samsung Electronics Co., Ltd. Procédé et système de maintien de continuité de service par un équipement utilisateur (ue) dans un système de communication sans fil
WO2019088599A1 (fr) * 2017-10-31 2019-05-09 엘지전자 주식회사 Procédé de protection de données chiffrées par une clé de réseau domestique dans un système de communication sans fil et dispositif associé
US11558774B2 (en) 2017-10-13 2023-01-17 Samsung Electronics Co., Ltd. User equipment (UE) and core network for managing network slice congestion in wireless communication system
US11910243B2 (en) 2018-11-02 2024-02-20 Nokia Solutions And Networks Oy Methods and apparatuses for network slice minimum and maximum resource quotas

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101542408B1 (ko) * 2009-03-23 2015-08-06 엘지전자 주식회사 Ｈｏｍｅ (ｅ)ＮｏｄｅＢ에 대한 단말의 접속을 제어하는 방법
US8787337B2 (en) * 2010-08-13 2014-07-22 Intel Corporation Techniques for managing mobility management signaling in a wireless network
CN102448045B (zh) * 2010-09-30 2015-05-20 电信科学技术研究院 一种处理移动性管理上下文的方法和设备
EP2442596B1 (fr) * 2010-10-15 2014-04-02 Alcatel Lucent Procédé et appareil pour fournir la gestion de la mobilité distribuée dans un réseau
CN102595368B (zh) * 2011-01-17 2015-01-07 华为技术有限公司 一种注册方法、系统和设备

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019074344A1 (fr) * 2017-10-13 2019-04-18 Samsung Electronics Co., Ltd. Procédé et système de maintien de continuité de service par un équipement utilisateur (ue) dans un système de communication sans fil
CN110771219A (zh) * 2017-10-13 2020-02-07 三星电子株式会社 无线通信系统中通过用户设备维护服务连续性的方法和系统
US11096245B2 (en) 2017-10-13 2021-08-17 Samsung Electronics Co., Ltd. Method and system for maintaining service continuity by user equipment (UE) in wireless communication system
CN110771219B (zh) * 2017-10-13 2022-09-09 三星电子株式会社 无线通信系统中通过用户设备维护服务连续性的方法和系统
US11558774B2 (en) 2017-10-13 2023-01-17 Samsung Electronics Co., Ltd. User equipment (UE) and core network for managing network slice congestion in wireless communication system
US11743971B2 (en) 2017-10-13 2023-08-29 Samsung Electronics Co., Ltd Method and system for maintaining service continuity by user equipment (UE) in wireless communication system
US12058563B2 (en) 2017-10-13 2024-08-06 Samsung Electronics Co., Ltd. User Equipment (UE) and core network for managing network slice congestion in wireless communication system
WO2019088599A1 (fr) * 2017-10-31 2019-05-09 엘지전자 주식회사 Procédé de protection de données chiffrées par une clé de réseau domestique dans un système de communication sans fil et dispositif associé
US11910243B2 (en) 2018-11-02 2024-02-20 Nokia Solutions And Networks Oy Methods and apparatuses for network slice minimum and maximum resource quotas

Also Published As

Publication number Publication date
WO2017171348A3 (fr) 2018-09-07

Similar Documents

Publication Publication Date Title
WO2019160376A1 (fr) Procédé d'émission et de réception de signal par smf dans un système de communication sans fil et dispositif associé
WO2018084635A1 (fr) Procédé de passage d'un ngs à un eps dans un système de communication sans fil et appareil associé
WO2018155934A1 (fr) Procédé de réception de données relatives à un accès non-3gpp par l'intermédiaire d'un accès 3gpp dans un système de communication sans fil, et dispositif associé
WO2017142362A1 (fr) Procédé d'émission/réception de message associé à l'enregistrement de position dans un système de communication sans fil et appareil approprié
WO2019022442A9 (fr) Procédé de prise en charge de transmission de sms pour un équipement d'utilisateur pouvant recevoir un service à partir d'un système 5g 3gpp et d'eps dans un système de communication sans fil, et appareil associé
WO2017026872A1 (fr) Procédé de transmission et de réception de signal par ue à distance dans un système de communication sans fil et dispositif associé
WO2016190670A1 (fr) Procédé et terminal de transmission de trafic de données dans un système de communication sans fil
WO2017126948A1 (fr) Procédé d'émission et de réception de message véhicule à tout (v2x) dans un réseau local au sein d'un système de communication sans fil et appareil associé
WO2017086618A1 (fr) Procédé de communication directe de dispositif à dispositif dans un système de communication sans fil et dispositif correspondant
WO2015174702A1 (fr) Procédé et appareil pour une émission et une réception de signal de hss/mme dans un système de communication sans fil
WO2016039579A1 (fr) Procédé pour établir un appel de groupe mcptt dans un système de communication sans fil et dispositif associé
WO2017191973A1 (fr) Procédé pour réaliser un enregistrement de localisation par l'intermédiaire d'un ue à distance dans un système de communication sans fil, et appareil associé
WO2017171427A1 (fr) Procédé de transmission d'informations système et station de base, et procédé de réception d'informations système et équipement d'utilisateur
WO2018221943A1 (fr) Procédé d'émission-réception de signal en association avec un ajout de psa multiconnexion dans un système de communication sans fil, et appareil associé
WO2018008922A2 (fr) Procédé permettant de prendre en charge une signalisation nas par une station de base dans un système de communication sans fil, et appareil s'y rapportant
WO2016126092A1 (fr) Procédé de sélection du réseau mobile terrestre public par un terminal dans un système de communication sans fil et appareil associé
WO2016111603A1 (fr) Procédé de transmission et de réception de signaux associés à une récupération de connexion pdn dans un système de communication sans fil, et dispositif associé
WO2019059740A1 (fr) Procédé de transmission/réception d'un signal associé à une prise en charge de voix d'un ims par un ng-ran dans un système de communication sans fil, et appareil associé
WO2016144009A1 (fr) Procédé et terminal de régulation de trafic réseau dans un système de communication sans fil
WO2018009025A1 (fr) Procédé permettant de transmettre et de recevoir des signaux se rapportant à une connexion au réseau de données par paquets (pdn) dans un système de communication sans fil et dispositif s'y rapportant
WO2016163635A1 (fr) Procédé de sélection d'un plmn d'un terminal dans un système de communication sans fil, et appareil associé
WO2016126093A1 (fr) Procédé permettant à un terminal de sélectionner un réseau mobile terrestre public dans un système de communication sans fil, et dispositif à cet effet
WO2017026772A1 (fr) Procédé servant à sélectionner une fonction de commande de session d'appel de mandataire (p-cscf) et à transmettre un message de protocole d'initiation de session (sip) dans un système de communication sans fil et dispositif associé
WO2016153327A2 (fr) Procédé de réception et de transmission d'un signal lié à un psm sans tau dans un système de communication sans fil, et appareil associé
WO2016056815A1 (fr) Procédé d'émission/réception d'un signal relatif à une mobilité nbifom dans un système de communication sans fil, et appareil associé

Legal Events

Date Code Title Description
NENP Non-entry into the national phase in:

Ref country code: DE

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

Ref document number: 17775772

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 17775772

Country of ref document: EP

Kind code of ref document: A2