WO2020067733A1 - Terminal effectuant un enregistrement dans un accès non 3 gpp et procédé effectué par celui-ci - Google Patents

Terminal effectuant un enregistrement dans un accès non 3 gpp et procédé effectué par celui-ci Download PDF

Info

Publication number
WO2020067733A1
WO2020067733A1 PCT/KR2019/012504 KR2019012504W WO2020067733A1 WO 2020067733 A1 WO2020067733 A1 WO 2020067733A1 KR 2019012504 W KR2019012504 W KR 2019012504W WO 2020067733 A1 WO2020067733 A1 WO 2020067733A1
Authority
WO
WIPO (PCT)
Prior art keywords
timer
value
3gpp
registration
terminal
Prior art date
Application number
PCT/KR2019/012504
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 엘지전자 주식회사
Priority to US17/274,253 priority Critical patent/US11457425B2/en
Publication of WO2020067733A1 publication Critical patent/WO2020067733A1/fr
Priority to US17/943,937 priority patent/US11638232B2/en

Links

Images

Classifications

    • 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/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • 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

Definitions

  • This specification relates to next-generation mobile communications, such as 5G mobile communications.
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • 5th generation mobile communication refers to providing data transmission speeds of up to 20 Gbps and haptic transmission speeds of at least 100 Mbps, anywhere.
  • the official name is' IMT-2020 'and aims to commercialize it in' 2020 worldwide.
  • the 5th generation mobile communication supports a number of numerology or subcarrier spacing (SCS) to support various services. For example, if the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and if the SCS is 30 kHz / 60 kHz, it is dense-urban, lower latency. And a wider carrier bandwidth, and when the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.
  • SCS subcarrier spacing
  • the NR frequency band is defined as a frequency range of two types (FR1, FR2).
  • FR1 is 410 MHz-7125 MHz
  • FR2 is 24250 MHz-52600 MHz, which may mean a millimeter wave (mmW).
  • mmW millimeter wave
  • the ITU proposes three usage scenarios, e.g., Enhanced Mobile BroadBand (eMBB) Massive Machine Type Communication (mMTC) and Ultra Reliable and Low Latency Communications (URLLC).
  • eMBB Enhanced Mobile BroadBand
  • mMTC Massive Machine Type Communication
  • URLLC Ultra Reliable and Low Latency Communications
  • URLLC relates to a use scenario that requires high reliability and low latency.
  • services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (eg, latency of less than 1 ms).
  • latency of 4G (LTE) is statistically 21-43ms (best 10%) and 33-75ms (median). This is insufficient to support a service that requires a latency of 1 ms or less.
  • the eMBB usage scenario relates to a usage scenario requiring a mobile ultra-wideband.
  • FIG. 1 is a structural diagram of a next generation mobile communication network.
  • 5GC 5G Core
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • Function (43) UPF (User Plane Function) 44
  • AF Application Function
  • UDM Unified Data Management
  • N3IWF Non-3GPP InterWorking Function
  • the UE 10 is connected to the data network via the UPF 44 through a Next Generation Radio Access Network (NG-RAN).
  • NG-RAN Next Generation Radio Access Network
  • the UE 10 may also be provided with data service through untrusted non-3rd Generation Partnership Project (non-3GPP) access, for example, a wireless local area network (WLAN).
  • non-3GPP non-3rd Generation Partnership Project
  • WLAN wireless local area network
  • an N3IWF 49 can be deployed.
  • FIG. 2 is an exemplary diagram illustrating an expected structure of a next-generation mobile communication from a node perspective.
  • the UE is connected to the data network (DN) through the next-generation Radio Access Network (RAN).
  • DN data network
  • RAN next-generation Radio Access Network
  • the illustrated control plane function (CPF) node includes all or part of the functions of the mobility management entity (MME) of the 4th generation mobile communication, the control plane function of the serving gateway (S-GW) and the PDN gateway (P-GW). Do all or part of it.
  • the CPF node includes an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • the illustrated User Plane Function (UPF) node is a kind of gateway through which user data is transmitted and received.
  • the UPF node may perform all or part of the user plane functions of the S-GW and P-GW of the 4G mobile communication.
  • the illustrated PCF Policy Control Function
  • Policy Control Function is a node that controls the operator's policy.
  • the illustrated application function is a server for providing various services to the UE.
  • the illustrated Unified Data Management is a type of server that manages subscriber information, such as the Home Subscriber Server (HSS) of the 4th generation mobile communication.
  • the UDM stores and manages the subscriber information in a Unified Data Repository (UDR).
  • UDM Unified Data Repository
  • the illustrated authentication server function (AUSF) authenticates and manages the UE.
  • the illustrated network slice selection function (NSSF) is a node for network slicing as described below.
  • a UE may simultaneously access two data networks using multiple protocol data unit or packet data unit (PDU) sessions.
  • PDU packet data unit
  • FIG. 3 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.
  • FIG 3 shows an architecture for a UE to access two data networks simultaneously using one PDU session.
  • N1 represents a reference point between the UE and the AMF.
  • N2 represents a reference point between (R) AN and AMF.
  • N3 represents a reference point between (R) AN and UPF.
  • N4 represents a reference point between SMF and UPF.
  • N5 represents a reference point between PCF and AF.
  • N6 represents a reference point between UPF and DN.
  • N7 represents a reference point between SMF and PCF.
  • N8 represents a reference point between UDM and AMF.
  • N9 represents a reference point between UPFs.
  • N10 represents a reference point between UDM and SMF.
  • N11 represents a reference point between AMF and SMF.
  • N12 represents a reference point between AMF and AUSF.
  • N13 represents a reference point between UDM and AUSF.
  • N14 represents a reference point between AMFs.
  • N15 represents a reference point between PCF and AMF.
  • N16 represents a reference point between SMFs.
  • N22 represents a reference point between AMF and NSSF.
  • FIG. 4 is another exemplary view showing a structure of a radio interface protocol between a UE and a gNB.
  • the wireless interface protocol is based on a 3GPP wireless access network standard.
  • the radio interface protocol consists of a horizontal physical layer, a data link layer, and a network layer. Vertically, a user plane and control for data information transmission It is divided into control planes for signal transmission.
  • the protocol layers are based on the lower three layers of the Open System Interconnection (OSI) reference model widely known in communication systems, L1 (first layer), L2 (second layer), L3 (third layer) ).
  • OSI Open System Interconnection
  • the first layer provides an information transfer service using a physical channel.
  • the physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. And, data is transferred between different physical layers, that is, between the physical layer of the transmitting side and the receiving side through a physical channel.
  • the second layer includes a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer.
  • MAC medium access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • the third layer includes Radio Resource Control (hereinafter abbreviated as RRC).
  • RRC Radio Resource Control
  • the RRC layer is defined only in the control plane, and is associated with the configuration (setting), resetting (Re-setting) and release (Release) of radio bearers (Radio Bearers), logical channels, transport channels, and physical channels. Take control.
  • RB means a service provided by the second layer for data transmission between the terminal and the E-UTRAN.
  • the NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management (Mobility Management).
  • the NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM).
  • MM mobility management
  • SM session management
  • the NAS entity for MM provides the following general functions.
  • NAS procedures related to AMF include:
  • AMF supports the following functions.
  • the NAS entity for the SM performs session management between the UE and the SMF.
  • the SM signaling message is processed, that is, generated and processed in the NAS-SM layer of the UE and SMF.
  • the content of the SM signaling message is not interpreted by the AMF.
  • the NAS entity for MM creates a NAS-MM message that derives how and where to send the SM signaling message via a security header indicating the NAS transmission of SM signaling, and additional information about the receiving NAS-MM.
  • the NAS entity for the SM When receiving SM signaling, the NAS entity for the SM performs integrity check of the NAS-MM message and interprets additional information to derive a method and place to derive the SM signaling message.
  • the RRC layer, the RLC layer, the MAC layer, and the PHY layer located under the NAS layer are collectively referred to as an access layer (Access Stratum: AS).
  • Network systems for next generation mobile communications (i.e., 5G) also support non-3GPP access.
  • An example of the non-3GPP access is WLAN access.
  • the WLAN access can include both trusted and untrusted WLANs.
  • AMF performs registration management (RM) and connection management (CM) for non-3GPP access as well as 3GPP access.
  • RM registration management
  • CM connection management
  • one disclosure of the present specification provides a method performed by a terminal performing registration in a non-3GPP (3rd generation partnership project) access.
  • the terminal may receive a rejection message including the value of the back-off timer.
  • the terminal may determine the value of the non-3GPP de-registration timer based on the value of the back-off timer. At this time, the value of the non-3GPP deregistration timer may be determined to be larger than the value of the back-off timer.
  • one disclosure of the present specification also provides a terminal that has performed registration in non-3GPP (3rd generation partnership project) access.
  • the terminal may include a transmitting and receiving unit for receiving a rejection message including a value of a back-off timer.
  • the terminal may include a processor that determines the value of the non--3GPP de-registration timer based on the value of the back-off timer. At this time, the value of the non-3GPP deregistration timer may be determined to be larger than the value of the back-off timer.
  • FIG. 1 is a structural diagram of a next generation mobile communication network.
  • FIG. 2 is an exemplary diagram illustrating an expected structure of a next-generation mobile communication from a node perspective.
  • FIG. 3 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.
  • FIG. 4 is another exemplary view showing a structure of a radio interface protocol between a UE and a gNB.
  • 5A and 5B are signal flows illustrating an exemplary registration procedure.
  • 6A and 6B are signal flow diagrams illustrating an exemplary PDU session establishment procedure.
  • FIG. 7 is an exemplary view showing a flowchart according to the first disclosure.
  • FIG 8 is an exemplary view showing a flow chart according to the first method of the first disclosure.
  • FIG 9 is an exemplary view showing a flowchart according to a second method of the first disclosure.
  • FIG. 10 is an exemplary view showing a flowchart according to a third method of the first disclosure.
  • FIG. 11 illustrates a wireless communication system according to an embodiment.
  • FIG. 12 is a block diagram of a network node according to an embodiment.
  • FIG. 13 is a block diagram showing the configuration of a terminal according to an embodiment.
  • 15 shows an AI system 1 according to an embodiment.
  • first and second used in the present specification 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 other components.
  • first component may be referred to as a second component without departing from the scope of rights, and similarly, the second component may also be referred to as a first component.
  • a component When a component is referred to as being connected to or connected to another component, it may be directly connected to or connected to the other component, but other components may exist in the middle. On the other hand, when it is mentioned that one component is directly connected to or connected to another component, it should be understood that no other component exists in the middle.
  • a user equipment is illustrated by way of example, but the illustrated UE may be referred to in terms of UE 100 (Terminal), ME (Mobile Equipment), 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.
  • UE / MS User Equipment / Mobile Station, meaning UE (100) device.
  • EPS Abbreviation for Evolved Packet System, which means a core network that supports a Long Term Evolution (LTE) network.
  • LTE Long Term Evolution
  • UMTS evolved network
  • PDN Public Data Network
  • PDN-GW Packet Data Network Gateway
  • Network node of EPS network that performs UE IP address allocation, packet screening & filtering, and charging data collection
  • Serving GW Network node of EPS network that performs mobility function, packet routing, idle mode packet buffering, triggering MME to page UE function
  • eNodeB It is installed outdoors as a base station of Evolved Packet System (EPS), and the cell coverage scale corresponds to a macro cell.
  • EPS Evolved Packet System
  • MME Mobility Management Entity, and serves to control each entity in the EPS to provide session and mobility for the UE.
  • a session is a channel for data transmission, and its unit may be a PDN, a bearer, or an IP flow unit. As defined in 3GPP, the difference between each unit can be divided into the entire target network unit (APN or PDN unit), the QoS classifying unit (Bearer unit), and the destination IP address unit.
  • APN stands for Access Point Name, and is provided to the UE as the name of the access point managed by the network. That is, it is a string that refers to or distinguishes a PDN. In order to access the requested service or network (PDN), it goes through the corresponding P-GW, which is a predefined name (string) in the network to find this P-GW.
  • PDN Access Point Name
  • P-GW a predefined name (string) in the network to find this P-GW.
  • APN may be of the form internet.mnc012.mcc345.gprs.
  • PDN connection (connection) represents a connection from the UE to the PDN, that is, the association (connection) between the UE represented by the ip address and the PDN represented by the APN. This means the connection between the entities in the core network (UE (100) -PDN GW) so that a session can be established.
  • UE Context The context information of the UE used to manage the UE in the network, that is, the context information composed of the UE id, mobility (current location, etc.), and attributes of the session (QoS, priority, etc.)
  • NAS Non-Access-Stratum: upper stratum of a control plane between a UE and an MME. Supports mobility management between the UE and the network, session management, and IP address maintenance.
  • PLMN An abbreviation for Public Land Mobile Network, which means the network identification number of the operator.
  • HPLMN Home PLMN
  • VPLMN Visited PLMN
  • DNN Abbreviation for Data Network Name, similar to APN, it is provided to the UE as the name of the access point managed by the network. In 5G systems, DNN is used equivalently to APN.
  • NSSP Network Slice Selection Policy
  • S-NSSAI Session Network Slice Selection Assistance Information
  • the UE needs to obtain authorization to enable mobility tracking, enable data reception, and receive services. To this end, the UE must register with the network.
  • the registration procedure is performed when the UE needs to perform initial registration for the 5G system.
  • the registration procedure is performed when the UE performs periodic registration update, when moving to a new tracking area (TA) in idle mode, and when the UE needs to perform periodic registration update.
  • TA tracking area
  • the ID of the UE can be obtained from the UE.
  • AMF can deliver PEI (IMEISV) to UDM, SMF and PCF.
  • PEI IMEISV
  • 5A and 5B are signal flows illustrating an exemplary registration procedure.
  • the terminal may transmit an AN message to the RAN.
  • the AN message may include an AN parameter and a registration request message.
  • the registration request message may include information such as registration type, subscriber permanent ID or temporary user ID, security parameters, NSSAI (Network Slice Selection Assistance Information), 5G capability of the terminal, and protocol data unit (PDU) session status.
  • NSSAI Network Slice Selection Assistance Information
  • 5G capability of the terminal and protocol data unit (PDU) session status.
  • PDU protocol data unit
  • the AN parameter may include SUPI (Subscription Permanent Identifier) or temporary user ID, selected network and NSSAI.
  • the terminal is "initial registration” (ie, the terminal is in a non-registration state), "mobility registration update” (i.e., the terminal is in a registered state and starts the registration procedure due to mobility) or “regular registration update It may indicate whether it is “(that is, the terminal is in the registered state and the registration procedure is started due to the periodic update timer expiration).” If a temporary user ID is included, the temporary user ID indicates the last serving AMF. If the terminal is already registered through non-3GPP access in a PLMN different from the PLMN of 3GPP access, the terminal may not provide a temporary ID of the terminal allocated by the AMF during the registration procedure through non-3GPP access.
  • Security parameters can be used for authentication and integrity protection.
  • the PDU session state may indicate a PDU session (previously set) available in the terminal.
  • the RAN may select AMF based on (R) AT and NSSAI.
  • (R) AN cannot select the appropriate AMF, it selects an arbitrary AMF according to the local policy and delivers a registration request to the selected AMF. If the selected AMF cannot service the terminal, the selected AMF selects another AMF that is more suitable for the terminal.
  • the RAN sends an N2 message to the new AMF.
  • the N2 message includes an N2 parameter and a registration request.
  • the registration request may include a registration type, a subscriber permanent identifier or temporary user ID, security parameters, NSSAI and MICO mode default settings, and the like.
  • the N2 parameter includes location information, cell identifier and RAT type related to the cell that the terminal is camping.
  • steps 4 to 17 described later may not be performed.
  • the newly selected AMF may transmit an information request message to the previous AMF.
  • the new AMF can send an information request message containing the complete registration request information to the previous AMF to request the UE's SUPI and MM context. have.
  • the previous AMF sends an information response message to the newly selected AMF.
  • the information response message may include SUPI, MM context, and SMF information.
  • the previous AMF transmits an information response message including the UE's SUPI and MM context.
  • the previous AMF may include SMF information including the ID of the SMF and the PDU session ID in the information response message.
  • the new AMF sends an Identity Request message to the UE if the SUPI is not provided by the terminal or retrieved from the previous AMF.
  • the terminal sends an Identity Response message including the SUPI to the new AMF.
  • the AMF can decide to trigger the AUSF.
  • AMF can select AUSF based on SUPI.
  • AUSF can initiate authentication of the UE and NAS security functions.
  • the new AMF can send an information response message to the old AMF.
  • the new AMF can send the information response message to confirm the delivery of the UE MM context.
  • the registration is rejected and the new AMF can send a rejection message to the old AMF.
  • the new AMF can send an Identity Request message to the UE.
  • an Identity Request message may be sent by the AMF to retrieve the PEI.
  • the new AMF checks the ME identifier.
  • the new AMF selects UDM based on SUPI.
  • the new AMF starts an update location procedure. .
  • UDM starts canceling a location for a previous AMF.
  • the old AMF discards the MM context and notifies all possible SMF (s), and the new AMF creates an MM context for the terminal after obtaining the AMF-related subscription data from UDM.
  • the AMF acquires the allowed NSSAI based on the requested NSSAI, UE subscription and local policy. If AMF is not suitable to support the allowed NSSAI, it will reroute registration requests.
  • the new AMF can select PCF based on SUPI.
  • the new AMF sends a UE Context Establishment Request message to PCF.
  • the AMF may request an operator policy for the terminal from the PCF.
  • the PCF sends a UE Context Establishment Acknowledged message to the new AMF.
  • the new AMF sends an N11 request message to the SMF.
  • the new AMF when the AMF is changed, notifies each SMF of a new AMF serving the terminal.
  • the AMF verifies the PDU session status from the UE with available SMF information.
  • available SMF information may be received from the previous AMF.
  • the new AMF may request the SMF to release network resources associated with an inactive PDU session at the terminal.
  • the new AMF sends an N11 response message to the SMF.
  • the previous AMF transmits a UE Context Termination Request message to PCF.
  • the previous AMF may delete the UE context in the PCF.
  • the PCF may transmit a UE Context Termination Request message to the previous AMF.
  • the new AMF sends a registration acceptance message to the UE.
  • the registration acceptance message may include a temporary user ID, registration area, mobility restriction, PDU session status, NSSAI, periodic registration update timer, and allowed MICO mode.
  • the registration acceptance message may include allowed NSSAI and information of the mapped NSSAI.
  • the allowed NSSAI information for the access type of the UE may be included in an N2 message including a registration acceptance message.
  • the mapped NSSAI information is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI set for the HPLMN.
  • a temporary user ID may be further included in the registration acceptance message.
  • information indicating the mobility restriction may be additionally included in the registration acceptance message.
  • the AMF may include information indicating the PDU session status for the terminal in the registration acceptance message.
  • the UE may remove any internal resource associated with the PDU session that is not marked as active in the received PDU session state. If the PDU session state information is in the Registration Request, the AMF may include information indicating the PDU session state to the terminal in the registration acceptance message.
  • the terminal transmits a registration completion message to the new AMF.
  • PDU session establishment procedure Two types of PDU session establishment procedures may exist in the protocol data unit (PDU) session establishment procedure.
  • PDU protocol data unit
  • the network can send a device trigger message to the UE's application (s).
  • 6A and 6B are signal flow diagrams illustrating an exemplary PDU session establishment procedure.
  • the terminal sends a NAS message to AMF.
  • the message may include S-NSSAI (Session Network Slice Selection Assistance Information), DNN, PDU session ID, request type, N1 SM information, and the like.
  • S-NSSAI Session Network Slice Selection Assistance Information
  • the terminal includes the S-NSSAI from the allowed NSSAI of the current access type. If the information on the mapped NSSAI is provided to the terminal, the terminal may provide both the allowed NSSAI-based S-NSSAI and the mapped NSSAI-based corresponding S-NSSAI.
  • the mapped NSSAI information is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI set for the HPLMN.
  • the terminal may extract and store information of the allowed S-NSSAI and the mapped S-NSSAI included in the registration acceptance message received from the network (ie, AMF). have. Accordingly, the terminal may transmit the PDU session establishment request message including both the allowed NSSAI-based S-NSSAI and the mapped NSSAI-based corresponding S-NSSAI.
  • the terminal can generate a new PDU session ID.
  • the UE may start a PDU session establishment procedure initiated by the UE by transmitting a NAS message including the PDU session establishment request message in N1 SM information.
  • the PDU session establishment request message may include a request type, SSC mode, and protocol configuration options.
  • the request type indicates "initial request”. However, if there is an existing PDU session between 3GPP access and non-3GPP access, the request type may indicate "existing PDU session”.
  • the NAS message transmitted by the terminal is encapsulated in the N2 message by AN.
  • the N2 message is transmitted to the AMF, and may include user location information and access technology type information.
  • -N1 SM information may include an SM PDU DN request container including information on PDU session authentication by an external DN.
  • the AMF may determine that the message corresponds to a request for a new PDU session when the request type indicates " initial request " and the PDU session ID is not used for an existing PDU session of the UE.
  • the AMF can determine the default S-NSSAI for the requested PDU session according to the UE subscription.
  • the AMF can store the PDU session ID and the SMF ID in association.
  • AMF sends SM request message to SMF.
  • the SM request message may include a subscriber permanent ID, DNN, S-NSSAI, PDU session ID, AMF ID, N1 SM information, user location information, and access technology type.
  • the N1 SM information may include a PDU session ID and a PDU session establishment request message.
  • the AMF ID is used to identify the AMF serving the terminal.
  • the N1 SM information may include a PDU session establishment request message received from the UE.
  • the SMF sends a subscriber data request message to the UDM.
  • the subscriber data request message may include a subscriber permanent ID and DNN.
  • step 3 if the request type indicates "existing PDU session", the SMF determines that the request is due to a handover between 3GPP access and non-3GPP access.
  • the SMF can identify an existing PDU session based on the PDU session ID.
  • the SMF can request the subscription data.
  • the UDM may send a subscription data response message to the SMF.
  • the subscription data may include information about the authenticated request type, authenticated SSC mode, and basic QoS profile.
  • the SMF can check whether the UE request complies with the user subscription and local policy. Alternatively, the SMF rejects the UE request through NAS SM signaling (including the related SM rejection cause) delivered by the AMF, and the SMF notifies the AMF that the PDU session ID should be considered to be released.
  • NAS SM signaling including the related SM rejection cause
  • the SMF sends a message to the DN via UPF.
  • the SMF selects the UPF and triggers the PDU.
  • the SMF ends the PDU session establishment procedure and notifies the UE of rejection.
  • the SMF may start establishing a PDU-CAN session towards the PCF to obtain basic PCC rules for the PDU session. If the request type in step 3 indicates "existing PDU session", the PCF may start modifying the PDU-CAN session instead.
  • step 3 If the request type in step 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If step 5 is not performed, the SMF can also select UPF. For request type IPv4 or IPv6, the SMF can allocate an IP address / prefix for a PDU session.
  • the SMF can start the PDU-CAN session start.
  • the SMF may start the N4 session establishment procedure using the selected UPF, otherwise the N4 session modification procedure may be initiated using the selected UPF.
  • the SMF sends an N4 session establishment / modification request message to the UPF.
  • the SMF may provide packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session.
  • CN tunnel information may be provided to the UPF.
  • the UPF can respond by sending an N4 session establishment / modification response message.
  • CN tunnel information may be provided to the SMF.
  • the SMF sends an SM response message to the AMF.
  • the message may include a cause, N2 SM information, and N1 SM information.
  • the N2 SM information may include PDU session ID, QoS profile, and CN tunnel information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the PDU session establishment acceptance message may include an authorized QoS rule, SSC mode, S-NSSAI, and assigned IPv4 address.
  • the N2 SM information is information that the AMF should deliver to the RAN and may include the following.
  • -CN tunnel information This corresponds to the core network address of the N3 tunnel corresponding to the PDU session.
  • -PDU session ID This can be used to indicate to the terminal the association between the AN resources for the terminal and the PDU session by the AN signaling for the terminal.
  • the N1 SM information includes a PDU session acceptance message that the AMF should provide to the terminal.
  • Multiple QoS rules may be included in N1 SM information and N2 SM information in the PDU session establishment acceptance message.
  • the SM response message also includes information that enables the PDU session ID and AMF to determine which target UE as well as which access should be used for the terminal.
  • AMF sends an N2 PDU session request message to the RAN.
  • the message may include N2 SM information and a NAS message.
  • the NAS message may include a PDU session ID and a PDU session establishment acceptance message.
  • the AMF may send a NAS message including a PDU session ID and a PDU session establishment acceptance message.
  • the AMF includes the received N2 SM information from the SMF in the N2 PDU session request message and transmits it to the RAN.
  • the RAN may exchange specific signaling with the UE related to information received from the SMF.
  • the RAN also allocates RAN N3 tunnel information for the PDU session.
  • the RAN delivers the NAS message provided in step 10 to the terminal.
  • the NAS message may include PDU session ID and N1 SM information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the RAN transmits the NAS message to the terminal only when the required RAN resource is established and the allocation of the RAN tunnel information is successful.
  • the RAN sends an N2 PDU session response message to the AMF.
  • the message may include PDU session ID, cause, and N2 SM information.
  • the N2 SM information may include a PDU session ID, (AN) tunnel information, and a list of allowed / rejected QoS profiles.
  • the RAN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.
  • AMF can send the SM request message to SMF.
  • the SM request message may include N2 SM information.
  • the AMF may be to transmit N2 SM information received from the RAN to the SMF.
  • the SMF may initiate an N4 session establishment procedure with the UPF. Otherwise, the SMF can initiate the N4 session modification procedure using UPF.
  • the SMF can provide AN tunnel information and CN tunnel information. CN tunnel information may only be provided if SMF selects CN tunnel information in step 8.
  • the UPF may transmit an N4 session establishment / modification response message to the SMF.
  • the SMF can send the SM response message to the AMF.
  • AMF can send related events to SMF. Occurs when the RAN tunnel information changes or AMF is relocated.
  • SMF transmits information to the terminal through the UPF. Specifically, in the case of PDU Type IPv6, the SMF can generate an IPv6 Router Advertisement and transmit it to the UE through N4 and UPF.
  • the SMF will provide the user with source access (3GPP or non-3GPP access). Release the plane.
  • the SMF may call "UDM_Register UE serving NF service" including the SMF address and DNN.
  • UDM can store the SMF's ID, address and associated DNN.
  • the SMF If the PDU session establishment is not successful during the procedure, the SMF notifies the AMF.
  • the network system i.e., 5GC
  • the next generation mobile communication i.e., 5G
  • non-3GPP access An example of the non-3GPP access is WLAN access.
  • the WLAN access can include both trusted and untrusted WLANs.
  • AMF performs registration management (RM) and connection management (CM) for non-3GPP access as well as 3GPP access.
  • RM registration management
  • CM connection management
  • a network system for a conventional 4th generation mobile communication (ie, LTE) allows the terminal to manage reachability to the terminal, that is, to confirm that a signal can be reached to the terminal.
  • a TAU tracking area update
  • the network first enters the idle state (idle mode) and the first timer, for example, a reach timer (Mobile Reachable timer) Drive.
  • the network again starts a second timer, such as an Implicit Detach timer.
  • the network performs an operation of implicitly detaching the terminal.
  • the network system for 5G manages the reachability of the terminal through 3GPP access similar to this mechanism.
  • the network for 5G does not separately manage the reachability of the terminal through non-3GPP access. That is, the network for 5G de-registers the terminal immediately (implicitly) without driving the arrival timer when the terminal is in an idle state for a predetermined period of time through non-3GPP access. . Specifically, the terminal enters the idle state and does not drive a separate periodic registration update timer (eg, T3512), but only a non-3GPP de-registration timer (ie, a non-3gpp de-registration timer).
  • a separate periodic registration update timer eg, T3512
  • a non-3GPP de-registration timer ie, a non-3gpp de-registration timer
  • a network node e.g., AMF also does not drive the arrival timer, but does not run a non-3GPP internal deregistration timer (i.e., non-3gpp implicit de-registration timer) having a value greater than the value of the non-3GPP deregistration timer of the terminal. Drive.
  • a non-3GPP internal deregistration timer i.e., non-3gpp implicit de-registration timer
  • a periodic registration update procedure is periodically performed via 3GPP access.
  • the procedure is managed by a first timer operating inside the terminal, that is, a periodic registration update timer (eg, T3512).
  • AMF is a second timer, that is, an internal de-registration timer (eg, implicit de-registration timer) to manage when the terminal will be deregistered internally through 3GPP access. ).
  • an internal de-registration timer eg, implicit de-registration timer
  • the AMF is a third timer, i.e., a non-3GPP internal deregistration timer, to manage when the terminal will be deregistered internally through non-3GPP access.
  • a non-3GPP internal deregistration timer i.e., a non-3GPP internal deregistration timer, to manage when the terminal will be deregistered internally through non-3GPP access.
  • non-3GPP implicit de-registration timer is managed.
  • a fourth timer that is, a non-3GPP deregistration timer (eg, Run non-3GPP de-registration timer).
  • the AMF starts a third timer, that is, a non-3GPP internal deregistration timer, for the terminal registered through the non-3GPP access when the N1 NAS signaling connection through non-3GPP access is released.
  • the terminal that has performed registration through the non-3GPP access also has a fourth timer, that is, a non-3GPP deregistration timer (eg, non, when the N1 NAS signaling connection through the non-3GPP access is released) -3GPP de-registration timer) is started.
  • a non-3GPP deregistration timer eg, non, when the N1 NAS signaling connection through the non-3GPP access is released
  • a fourth timer that is, non The -3GPP deregistration timer (eg, non-3GPP de-registration timer) may be stopped.
  • the value of the third timer that is, the non-3GPP internal de-registration timer (eg, non-3GPP implicit de-registration timer) is the fourth timer, that is, the non-3GPP de-registration timer (eg, non-3GPP de-registration timer) ).
  • the value of the first timer that is, the periodic registration update timer (eg, T3512) may be included in a registration acceptance message transmitted by the network (REGISTRATION ACCEPT message) and transmitted to the terminal.
  • the terminal may apply the value in all tracking areas in the tracking area list allocated to the terminal until a new value is received.
  • the periodic registration update timer can be applied only to a terminal registered through 3GPP access.
  • the first reception that is, the registration reception message including the value of the periodic registration update timer (for example, T3512) includes the indication that the timer is deactivated or the value is 0, the first timer, That is, the periodic registration update timer (eg, T3512) is deactivated, and the terminal does not perform the periodic registration update procedure.
  • the periodic registration update timer eg, T3512
  • the first timer that is, a periodic registration update timer (eg, T3512) Resets and restarts to the initial value.
  • the first timer that is, a periodic registration update timer (eg, T3512 ) Can be stopped.
  • the terminal When the terminal subscribes to an emergency service and when the first timer, i.e., the periodic registration update timer (e.g., T3512) expires, the terminal does not initiate a periodic registration update procedure, and from the network Deregistration of can be performed internally. When the terminal camps on to a suitable cell, the terminal may perform re-registration in order to receive normal service again.
  • the first timer i.e., the periodic registration update timer (e.g., T3512) expires
  • the terminal does not initiate a periodic registration update procedure, and from the network Deregistration of can be performed internally.
  • the terminal may perform re-registration in order to receive normal service again.
  • the periodic registration update timer (eg, T3512) expires, the periodic registration update procedure is started.
  • the network may manage a periodic registration update procedure of the terminal through a reachability timer (ie, a mobile reachable timer).
  • a reachability timer ie, a mobile reachable timer
  • the value of the reachability timer should be greater than the value of the first timer, that is, the periodic registration update timer (eg, T3512).
  • the value of the reachability timer may be set larger than the value of the first timer, that is, the periodic registration update timer (eg, T3512) by 4 minutes.
  • the network stops sending a paging message to the terminal.
  • the AMF sets the value of the reachability timer to be the same as the value of the first timer, that is, the periodic registration update timer (eg, T3512).
  • the AMF deregisters the terminal internally.
  • the reachability timer may be reset and started with the values as described above.
  • the reachability timer may be stopped.
  • the network starts an internal de-registration timer (eg, implicit de-registration timer) for 3GPP access.
  • the value of the internal deregistration timer (eg, implicit de-registration timer) for the 3GPP access is determined by the network.
  • the value of the internal deregistration timer (eg, implicit de-registration timer) for the 3GPP access is set to 4 minutes (minutes) larger than the value of the first timer, that is, the periodic registration update timer (eg, T3512). Can be.
  • the network de-registers the terminal internally. If an NAS signaling connection is established to the terminal before the internal deregistration timer for the terminal expires, the internal deregistration timer (eg, implicit de-registration timer) is stopped.
  • the internal deregistration timer eg, implicit de-registration timer
  • the network may It is deregistered internally, and enters the deregistered state (ie, 5GMM-DEREGISTERED state) for the non-3GPP access. If a NAS signaling connection is established for the terminal through the non-3GPP access before the third timer, that is, the non-3GPP internal deregistration timer expires, the third timer, that is, the non-3GPP internal deregistration timer ( For example, the non-3GPP implicit de-registration timer) may be stopped.
  • the third timer that is, the non-3GPP internal deregistration timer (eg, non-3GPP implicit de-registration timer) may be stopped.
  • the terminal accesses the non-3GPP. For, enter into the deregistration state (ie, 5GMM-DEREGISTERED state). If a NAS signaling connection is established for the terminal through the non-3GPP access before the fourth timer, that is, the non-3GPP deregistration timer expires, the fourth timer, that is, the non-3GPP deregistration timer (eg, The non-3GPP de-registration timer) is stopped.
  • the deregistration state ie, 5GMM-DEREGISTERED state
  • the AMF provides a value of a back-off timer (eg T3346) through a mobility management message, and the value of the back-off timer (eg T3346) If the value of the first timer, i.e., the periodic registration update timer (e.g., T3512), is greater than the value of the AMF, the sum of timer values is greater than the value of the back-off timer (e.g., T3346). , Set the value of the reachability timer and the value of the internal deregistration timer.
  • the AMF provides a value of a back-off timer (eg T3346) through a mobility management message, and the value of the back-off timer (eg T3346) If the value of the fourth timer, that is, the non-3GPP de-registration timer (eg, non-3GPP de-registration timer) is greater than the value of the AMF, the third timer, that is, the non-3GPP internal de-registration timer (eg, non- The value of the 3GPP implicit de-registration timer is set larger than the value of the back-off timer (eg, T3346).
  • the value of the back-off timer may be transmitted to the terminal in a network congestion situation.
  • the network may apply MM congestion control through AMF.
  • the network sets the cause value (cause # 22) and the back-off timer (for example, T3346) indicating the congestion status for the mobility management request of the terminal.
  • the terminal receives the cause value and the value of the back-off timer (eg T3346), the terminal drives the back-off timer (eg T3346). While the timer is running, most MM procedures are prohibited.
  • the value of the third timer that is, the non-3GPP internal deregistration timer (eg, non-3GPP implicit de-registration timer) is the back-off timer. It was set to be larger than the value of (Back-off timer) (eg T3346).
  • a fourth timer that is, a non-3GPP deregistration timer (eg, non-3GPP de), than the value of the back-off timer (eg, T3346) If the value of -registration timer) is large, the AMF sets the value of the third timer, that is, the non-3GPP internal deregistration timer (eg, non-3GPP implicit de-registration timer) to the back-off timer (Back-off). timer) (for example, T3346).
  • the first timer for 3GPP access that is, the periodic registration update timer (eg, T3512) and the non-3GPP deregistration timer for non-3GPP access.
  • the first timer i.e., the periodic registration update timer (e.g., T3512) expires
  • the terminal maintains the registration state (5GMM-REGISTERED state), but when the non-3GPP deregistration timer expires, the network
  • the problem may additionally occur because the terminal is immediately unregistered implicitly.
  • AMF Sets a value of its third timer, that is, a non-3GPP internal de-registration timer (eg, non-3GPP implicit de-registration timer) larger than the back-off timer (eg, T3346).
  • a non-3GPP internal de-registration timer eg, non-3GPP implicit de-registration timer
  • the back-off timer eg, T3346
  • the terminal of the fourth timer that is, the non--3GPP de-registration timer (eg, non-3GPP de-registration timer) is set larger than the value of the back-off timer (Back-off timer) (eg, T3346 timer) Receive the value.
  • the non--3GPP de-registration timer eg, non-3GPP de-registration timer
  • Back-off timer eg, T3346 timer
  • the AMF is a third timer, that is, a value of a non-3GPP internal de-registration timer (eg, non-3GPP implicit de-registration timer) and a value of the back-off timer (eg, T3346 timer). Set it larger
  • the terminal cannot transmit the MO signal through non-3GPP access, so the fourth timer, that is, non-3GPP The deregistration timer (eg, non-3GPP de-registration timer) will expire.
  • the terminal de-registers for non-3GPP access i.e., 5GMM-DEREGISTERED state
  • the AMF is separately set to set the value of the third timer, that is, the non-3GPP internal deregistration timer (eg, non-3GPP implicit de-registration timer). There is no need to perform the operation at all.
  • a non-3GPP internal deregistration timer eg, non-3GPP implicit de-registration timer
  • the back-off timer eg, T3346 timer
  • the existing solution was to solve the problem that the terminal unintentionally unregistered by driving the back-off timer, but the problem is not solved at all, and the AMF is only required to perform unnecessary operations. Particularly, in the congestion situation, additionally causes a problem of weighting only the AMF. In addition, due to this problem, the quality of service of the terminal is deteriorated, and unnecessary signaling (transmission and reception of signals due to a procedure for re-registration) occurs.
  • the disclosure of the present specification aims to present a method of not unnecessarily unregistering a terminal registered through non-3GPP access in a next generation mobile communication system (ie, a 5G system).
  • a next generation mobile communication system ie, a 5G system
  • FIG. 7 is an exemplary view showing a flowchart according to the first disclosure.
  • the AMF 410 may deliver a value of the fourth timer, that is, a non-3GPP de-registration timer (eg, a non-3GPP de-registration timer) to the terminal through a registration procedure.
  • the terminal 100 may use a default value for the fourth timer, that is, a non-3GPP de-registration timer (eg, a non-3GPP de-registration timer). If the AMF does not deliver the value of the timer, the terminal can use a previously stored value or a preset default value (eg, 54 minutes).
  • the AMF operates as follows.
  • the AMF is the fourth timer, that is, the non-3GPP After setting the back-off timer (eg, T3346 timer) to have a value less than the value of the deregistration timer (eg, non-3GPP de-registration timer), it can be delivered to the terminal.
  • the back-off timer eg, T3346 timer
  • the value of the T3346 timer ⁇ the value of the non-3GPP deregistration timer (e.g., the non-3gpp de-registration timer)
  • the AMF will generate a back-off timer (Back) as follows: -off timer) (for example, T3346 timer).
  • T3346 timer value ⁇ min [non-3GPP deregistration timer value, (reachability timer value + internal deregistration timer value)]
  • the non-3GPP de-registration timer eg, non-3gpp de-registration timer
  • the first approach of the first initiation Simultaneous delivery of values of a back-off timer (eg T3346 timer) and a non-3GPP de-registration timer (eg non-3gpp de-registration timer)
  • a back-off timer eg T3346 timer
  • a non-3GPP de-registration timer eg non-3gpp de-registration timer
  • a back-off timer for example, T3346
  • a mobility registration procedure Reject message including the value of the timer.
  • FIG 8 is an exemplary view showing a flow chart according to the first method of the first disclosure.
  • the new timer to be used by the terminal 100 may be transmitted by including a value of a non-3GPP de-registration timer (eg, a non-3gpp de-registration timer).
  • the AMF is a value that satisfies the condition of the value of the value of the back-off timer (eg T3346 timer) ⁇ the fourth timer, that is, the non-3GPP de-registration timer (eg, non-3gpp de-registration timer). It can be delivered to the terminal.
  • the value of the fourth timer that is, the non--3GPP de-registration timer (eg, non-3gpp de-registration timer) is 54 minutes, so the value of the back-off timer (eg, T3346 timer) is 50 minutes shorter than 50. You can allocate minutes.
  • the format of the service rejection message may be as follows.
  • the value of the fourth timer in the service rejection message may be greater than a value of a back-off timer (eg, a T3346 timer).
  • a non-3GPP de-registration timer eg, a non-3gpp de-registration timer
  • the value of the fourth timer may be set to be 4 minutes before the value of the back-off timer (eg, T3346 timer). You can.
  • the format of the registration rejection message may be as follows.
  • the value of the fourth timer in the registration rejection message may be greater than a value of a back-off timer (eg, a T3346 timer).
  • a non-3GPP de-registration timer eg, a non-3gpp de-registration timer
  • the value of the fourth timer may be set to be 4 minutes before the value of the back-off timer (eg, T3346 timer). You can.
  • Second method of first initiation T3346 does not transmit the value of the timer, only a non-3GPP de-registration timer (eg, a non-3gpp de-registration timer) value is delivered
  • the network may transmit a value of a back-off timer (eg, T3346 timer) to the terminal along with a cause value (eg, # 22) for a back-off operation.
  • a back-off timer eg, T3346 timer
  • a cause value eg, # 22
  • this is optional and the timer value may not be delivered.
  • the terminal 100 may operate a back-off timer by selecting a random value within a range of 15 minutes to 30 minutes.
  • FIG 9 is an exemplary view showing a flowchart according to a second method of the first disclosure.
  • the AMF 410 when the AMF 410 transmits a rejection message including a cause value, the fourth timer, that is, the non-3GPP de-registration timer (eg, a non-3gpp de-registration timer) ) Can only be set.
  • the AMF 410 may transmit a rejection message including the cause value and the value of the fourth timer, that is, the non-3GPP deregistration timer (eg, a non-3gpp de-registration timer).
  • the terminal 100 may operate a back-off timer by selecting a random value within a range of 15 minutes to 30 minutes.
  • the value of the fourth timer that is, the non-3GPP deregistration timer (eg, non-3gpp de-registration timer) should be at least 30 minutes, and is generally 34 minutes, which is 4 minutes larger than the maximum value of the back-off timer. Can be set.
  • the third method of the first disclosure when the non-3GPP deregistration timer (eg, non-3gpp de-registration timer) is operated with a default value
  • the network separately operates the fourth timer, that is, the non-3GPP
  • the value of the back-off timer can be set to 50 minutes or less without passing the value of the deregistration timer (for example, non-3gpp de-registration timer).
  • FIG. 10 is an exemplary view showing a flowchart according to a third method of the first disclosure.
  • the AMF 410 sets only the value of the back-off timer (eg T3346 timer), and then sets the value of the back-off timer (eg T3346 timer) and the cause value.
  • a rejection message can be sent.
  • the terminal 100 may set a value of the non-3GPP de-registration timer (eg, non-3gpp de-registration timer).
  • the terminal may operate by setting a value of the fourth timer, that is, a non-3GPP de-registration timer (eg, a non-3gpp de-registration timer) as a default value.
  • the default value for the fourth timer that is, the non-3GPP deregistration timer (eg, non-3gpp de-registration timer) may be greater than the value of the back-off timer (eg, T3346 timer).
  • the value of the fourth timer, that is, the non-3GPP de-registration timer may be set to 4 minutes larger than the maximum value of the back-off timer.
  • the AMF 410 may also not deliver a back-off timer (eg T3346 timer).
  • the cultivation of the terminal 100 may drive a back-off timer (eg, a T3346 timer) by selecting a random value within a range of 15 minutes to 30 minutes, which is a basic operation value.
  • the value of the fourth timer that is, the non-3GPP deregistration timer (eg, a non-3gpp de-registration timer) may be set to 4 minutes larger than the value of the back-off timer.
  • the AMF 410 wants to include a back-off timer (for example, a T3346 timer) in the mobility management message to be delivered
  • a back-off timer for example, a T3346 timer
  • the AMF 410 is the third A value of a back-off timer (eg, a T3346 timer) may be set smaller than a value of a timer, that is, a non-3GPP internal deregistration timer (eg, a non-3GPP implicit de-registration timer).
  • the value of the back-off timer (eg, T3346 timer) may be set to be less than 4 minutes than the value of the fourth timer, that is, the non-3GPP de-registration timer (eg, non-3gpp de-registration timer).
  • the terminal may receive a rejection message including a value of a back-off timer. And, the terminal may determine the value of the non-3GPP de-registration timer based on the value of the back-off timer. At this time, the value of the non-3GPP deregistration timer may be determined to be larger than the value of the back-off timer.
  • the value of the non-3GPP deregistration timer may be determined to be 4 minutes larger than the value of the back-off timer.
  • the rejection message may include one or more of a registration rejection message and a service rejection message.
  • the non-3GPP deregistration timer may be driven.
  • the non-3GPP deregistration timer may be started.
  • the value of the non-3GPP deregistration timer may be set smaller than the value of a non-3GPP implicit deregistration timer driven by an access and mobility management function (AMF) node.
  • AMF access and mobility management function
  • the value of the non-3GPP deregistration timer may be set larger than the value of the back-off timer.
  • the back-off timer can be used for congestion control.
  • the back-off timer may be a T3346 timer.
  • FIG. 11 illustrates a wireless communication system according to an embodiment.
  • the wireless communication system may include a first device 100a and a second device 100b.
  • the first device 100a includes a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle), UAV), AI (Artificial Intelligence) module, robot, Augmented Reality (AR) device, Virtual Reality (VR) device, Mixed Reality (MR) device, Hologram device, Public safety device, MTC device, IoT device, Medical device, Pin It may be a tech device (or financial device), a security device, a climate / environment device, a device related to 5G services, or another device related to the fourth industrial revolution.
  • a tech device or financial device
  • a security device a climate / environment device, a device related to 5G services, or another device related to the fourth industrial revolution.
  • the second device 100b includes a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle), UAV), AI (Artificial Intelligence) module, robot, Augmented Reality (AR) device, Virtual Reality (VR) device, Mixed Reality (MR) device, Hologram device, Public safety device, MTC device, IoT device, Medical device, Pin It may be a tech device (or financial device), a security device, a climate / environment device, a device related to 5G services, or another device related to the fourth industrial revolution.
  • the terminal is a mobile phone, a smart phone, a laptop computer, a terminal for digital broadcasting, personal digital assistants (PDA), portable multimedia p-layer (PMP), navigation, a slate PC, It may include a tablet PC (tablet PC), ultrabook (ultrabook), wearable device (wearable device, for example, a smart watch (smartwatch), glass type (smart glass), head mounted display (HMD), and the like.
  • the HMD may be a display device worn on the head.
  • HMD can be used to implement VR, AR or MR.
  • a drone may be a vehicle that does not ride and is flying by radio control signals.
  • the VR device may include a device that implements an object or background of a virtual world.
  • the AR device may include a device that is implemented by connecting an object or background of the virtual world to an object or background of the real world.
  • the MR device may include a device that fuses and implements an object or background in the virtual world, such as an object or background in the real world.
  • the hologram device may include a device that implements a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing the interference phenomenon of light generated when two laser lights called holography meet.
  • the public safety device may include a video relay device or a video device wearable on a user's body.
  • the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation.
  • the MTC device and the IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors.
  • a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating or preventing a disease.
  • a medical device may be a device used for the purpose of diagnosing, treating, reducing or correcting an injury or disorder.
  • a medical device may be a device used for the purpose of examining, replacing, or modifying a structure or function.
  • the medical device may be a device used to control pregnancy.
  • the medical device may include a medical device, a surgical device, a (in vitro) diagnostic device, a hearing aid, or a surgical device.
  • the security device may be a device installed in order to prevent a risk that may occur and to maintain safety.
  • the security device may be a camera, CCTV, recorder or black box.
  • the fintech device may be a device capable of providing financial services such as mobile payment.
  • the fintech device may include a payment device or a point of sales (POS).
  • a climate / environmental device may include a device that monitors or predicts the climate / environment.
  • the first device 100a may include at least one processor such as a processor 1020a, at least one memory such as a memory 1010a, and at least one transceiver such as a transceiver 1031a.
  • the processor 1020a may perform the functions, procedures, and / or methods described above.
  • the processor 1020a may perform one or more protocols.
  • the processor 1020a may perform one or more layers of a radio interface protocol.
  • the memory 1010a is connected to the processor 1020a, and may store various types of information and / or instructions.
  • the transceiver 1031a is connected to the processor 1020a and can be controlled to transmit and receive wireless signals.
  • the second device 100b may include at least one processor such as a processor 1020b, at least one memory device such as a memory 1010b, and at least one transceiver such as a transceiver 1031b.
  • the processor 1020b may perform the functions, procedures, and / or methods described above.
  • the processor 1020b may implement one or more protocols.
  • the processor 1020b may implement one or more layers of a radio interface protocol.
  • the memory 1010b is connected to the processor 1020b, and may store various types of information and / or instructions.
  • the transceiver 1031b is connected to the processor 1020b and can be controlled to transmit and receive wireless signals.
  • the memory 1010a and / or the memory 1010b may be connected to each other inside or outside the processor 1020a and / or the processor 1020b, or other processors through various technologies such as wired or wireless connection. It may be connected to.
  • the first device 100a and / or the second device 100b may have one or more antennas.
  • antenna 1036a and / or antenna 1036b may be configured to transmit and receive wireless signals.
  • FIG. 12 is a block diagram of a network node according to an embodiment.
  • a base station when a base station is divided into a central unit (CU) and a distributed unit (DU), the network node is illustrated in more detail.
  • CU central unit
  • DU distributed unit
  • the base stations W20 and W30 may be connected to the core network W10, and the base station W30 may be connected to the neighboring base station W20.
  • the interface between the base stations W20 and W30 and the core network W10 may be referred to as NG, and the interface between the base station W30 and the neighboring base stations W20 may be referred to as Xn.
  • the base station W30 may be divided into CU (W32) and DU (W34, W36). That is, the base station W30 may be hierarchically separated and operated.
  • the CU (W32) may be connected to one or more DUs (W34, W36), for example, an interface between the CU (W32) and the DUs (W34, W36) may be referred to as F1.
  • the CU (W32) may perform the function of the upper layer (upper layers) of the base station, and the DUs (W34, W36) may perform the function of the lower layers (lower layers) of the base station.
  • the CU (W32) is a logical node hosting a radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layer of a base station (eg, gNB).
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the DUs W34 and W36 may be logical nodes hosting radio link control (RLC), media access control (MAC), and physical (PHY) layers of the base station.
  • the CU (W32) may be a logical node hosting the RRC and PDCP layer of the base station (eg, en-gNB).
  • the operation of the DUs W34 and W36 may be partially controlled by the CU W32.
  • One DU (W34, W36) may support more than one cell.
  • One cell can be supported by only one DU (W34, W36).
  • One DU (W34, W36) may be connected to one CU (W32), and one DU (W34, W36) may be connected to a plurality of CUs by appropriate implementation.
  • FIG. 13 is a block diagram showing the configuration of a terminal according to an embodiment.
  • the terminal includes a memory 1010, a processor 1020, a transceiver 1031, a power management module 1091, a battery 1092, a display 1041, an input 1053, a speaker 1042, and a microphone 1052, SIM (subscriber identification module) card, which includes one or more antennas.
  • SIM subscriber identification module
  • the processor 1020 can be configured to implement the proposed functions, procedures and / or methods described herein. Layers of the radio interface protocol may be implemented in the processor 1020.
  • the processor 1020 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices.
  • the processor 1020 may be an application processor (AP).
  • the processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator).
  • DSP digital signal processor
  • CPU central processing unit
  • GPU graphics processing unit
  • modem modulator and demodulator
  • HELIO TM series processor the example of the processor 1020 is made by the A-series processors, MediaTek ® made by the SNAPDRAGON TM Series processor, the EXYNOS TM series processor, Apple ® manufactured by Samsung ® manufactured by Qualcomm ®, It may be an ATOM TM series processor manufactured by INTEL ® or a corresponding next generation processor.
  • the power management module 1091 manages power for the processor 1020 and / or the transceiver 1031.
  • the battery 1092 supplies power to the power management module 1091.
  • the display 1041 outputs the results processed by the processor 1020.
  • the input unit 1053 receives input to be used by the processor 1020.
  • the input unit 1053 may be displayed on the display 1041.
  • a SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers, and keys associated therewith. You can also store contact information on many SIM cards.
  • IMSI international mobile subscriber identity
  • the memory 1010 is operatively coupled with the processor 1020 and stores various information for operating the processor 610.
  • the memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, a memory card, a storage medium, and / or other storage devices.
  • ROM read-only memory
  • RAM random access memory
  • flash memory a memory card
  • storage medium e.g., hard disk drives
  • / or other storage devices e.g., hard disk drives, a magnetic tape, etc.
  • modules may be stored in memory 1010 and executed by processor 1020.
  • the memory 1010 may be implemented inside the processor 1020. Alternatively, the memory 1010 may be implemented outside the processor 1020 and may be communicatively connected to the processor 1020 through various means known in the art.
  • the transceiver 1031 is operatively coupled with the processor 1020 and transmits and / or receives wireless signals.
  • the transceiver 1031 includes a transmitter and a receiver.
  • the transceiver 1031 may include a baseband circuit for processing radio frequency signals.
  • the transmitting and receiving unit controls one or more antennas to transmit and / or receive wireless signals.
  • the processor 1020 transmits command information to the transmission / reception unit 1031 to transmit, for example, a radio signal constituting voice communication data.
  • the antenna functions to transmit and receive wireless signals.
  • the transceiver 1031 may transmit a signal for processing by the processor 1020 and convert the signal to a base band.
  • the processed signal may be converted into audible or readable information output through the speaker 1042.
  • the speaker 1042 outputs sound-related results processed by the processor 1020.
  • the microphone 1052 receives sound related inputs to be used by the processor 1020.
  • the user inputs command information, such as a telephone number, for example, by pressing (or touching) a button of the input unit 1053 or by voice driving using a microphone 1052 (voice activation).
  • the processor 1020 receives such command information and processes it to perform an appropriate function, such as dialing a telephone number. Operational data may be extracted from the SIM card or the memory 1010. In addition, the processor 1020 may recognize the user and also display command information or driving information on the display 1041 for convenience.
  • the always-on PDU session for URLLC having the characteristics of low latency may be used for artificial intelligence, robot, autonomous driving, and extended reality among 5G scenarios below.
  • the 5G usage scenario illustrated in FIG. 14 is merely exemplary, and the technical features described herein may be applied to other 5G usage scenarios not illustrated in FIG. 14.
  • the three main requirements areas of 5G are: (1) enhanced mobile broadband (eMBB) area, (2) massive MTC (mMTC; massive machine type communication) area, and (3) high reliability / Ultra-reliable and low latency communications (URLLC) domain.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC Ultra-reliable and low latency communications
  • KPI key performance indicator
  • eMBB focuses on improving overall data rate, latency, user density, capacity and coverage of mobile broadband connections.
  • eMBB targets throughput of about 10 Gbps.
  • eMBB goes far beyond basic mobile Internet access and covers media and entertainment applications in rich interactive work, cloud or augmented reality.
  • Data is one of the key drivers of 5G, and it may not be possible to see dedicated voice services for the first time in the 5G era.
  • voice is expected to be processed as an application program simply using the data connection provided by the communication system.
  • the main causes of increased traffic volume are increased content size and increased number of applications requiring high data rates.
  • Streaming services audio and video
  • interactive video and mobile internet connections will become more widely used as more devices connect to the internet.
  • Cloud storage and applications are rapidly increasing in mobile communication platforms, which can be applied to both work and entertainment.
  • Cloud storage is a special use case that drives the growth of uplink data rates.
  • 5G is also used for remote work on the cloud and requires much lower end-to-end delay to maintain a good user experience when a tactile interface is used.
  • cloud gaming and video streaming are another key factor in demanding improved mobile broadband capabilities.
  • Entertainment is essential for smartphones and tablets anywhere, including in high mobility environments such as trains, cars and airplanes.
  • Another use case is augmented reality and information retrieval for entertainment.
  • augmented reality requires a very low delay and an instantaneous amount of data.
  • mMTC is designed to enable communication between large amounts of low-cost devices powered by batteries, and is intended to support applications such as smart metering, logistics, field and body sensors.
  • mMTC targets 10 years of battery and / or 1 million devices per km2.
  • mMTC can form a sensor network by allowing seamless connection of embedded sensors in all fields, and is one of the most anticipated 5G use cases. Potentially, 2020 is expected to reach 20.4 billion IoT devices. Smart networks using industrial IoT are one of the areas where 5G plays a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.
  • URLLC enables devices and machines to communicate with high reliability and very low latency and high availability, enabling mission-critical applications such as autonomous vehicle-to-vehicle communication and control, industrial control, factory automation, telesurgery and healthcare, smart grid and public Ideal for safety applications.
  • URLLC aims for a delay of about 1ms.
  • URLLC includes new services that will transform the industry through high-reliability / ultra-low-latency links, such as remote control of key infrastructure and autonomous vehicles. Reliability and level of delay are essential for smart grid control, industrial automation, robotics, drone control and coordination.
  • 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means to provide streams rated at hundreds of megabits per second to gigabit per second.
  • FTTH fiber-to-the-home
  • DOCSIS cable-based broadband
  • Such fast speeds may be required to deliver TVs in resolutions of 4K or higher (6K, 8K and higher) as well as virtual reality (VR) and augmented reality (AR).
  • VR and AR applications include almost immersive sports events. Certain applications may require special network settings. For VR games, for example, a gaming company may need to integrate a core server with a network operator's edge network server to minimize latency.
  • Automotive is expected to be an important new driver for 5G, with many examples of use for mobile communications to vehicles. For example, entertainment for passengers requires high capacity and high mobile broadband simultaneously. This is because future users continue to expect high-quality connections regardless of their location and speed.
  • Another example of use in the automotive field is the augmented reality dashboard.
  • the augmented reality contrast board allows the driver to identify objects in the dark over what is being viewed through the front window.
  • the augmented reality dashboard superimposes information to inform the driver about the distance and movement of the object.
  • wireless modules will enable communication between vehicles, exchange of information between the vehicle and the supporting infrastructure, and exchange of information between the vehicle and other connected devices (eg, devices carried by pedestrians).
  • the safety system helps to reduce the risk of accidents by guiding an alternative course of action to help the driver drive more safely.
  • the next step will be a remotely controlled vehicle or an autonomous vehicle.
  • This requires very reliable and very fast communication between different autonomous vehicles and / or between the vehicle and the infrastructure.
  • autonomous vehicles will perform all driving activities, and drivers will focus only on traffic beyond which the vehicle itself cannot identify.
  • the technical requirements of autonomous vehicles require ultra-low delay and ultra-high-speed reliability to increase traffic safety to a level that cannot be achieved by humans.
  • Smart cities and smart homes referred to as smart societies, will be embedded as high-density wireless sensor networks as examples of smart networks.
  • the distributed network of intelligent sensors will identify the conditions for cost and energy efficient maintenance of a city or home. Similar settings can be made for each assumption. Temperature sensors, window and heating controllers, burglar alarms and consumer electronics are all connected wirelessly. Many of these sensors typically require low data rates, low power and low cost. However, for example, real-time HD video may be required in certain types of devices for surveillance.
  • the smart grid interconnects these sensors using digital information and communication technologies to collect information and act accordingly. This information can include supplier and consumer behavior, allowing smart grids to improve efficiency, reliability, economics, production sustainability and the distribution of fuels such as electricity in an automated manner.
  • the smart grid can be viewed as another sensor network with low latency.
  • the health sector has many applications that can benefit from mobile communications.
  • the communication system can support telemedicine that provides clinical care from a distance. This helps to reduce barriers to distance and can improve access to medical services that are not continuously available in remote rural areas. It is also used to save lives in critical care and emergency situations.
  • Mobile communication-based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
  • Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Therefore, the possibility of replacing the cable with a wireless link that can be reconfigured is an attractive opportunity in many industries. However, achieving this requires that the wireless connection operate with cable-like delay, reliability, and capacity, and that management is simplified. Low latency and very low error probability are new requirements that need to be connected to 5G.
  • Logistics and cargo tracking is an important use case for mobile communications that enables the tracking of inventory and packages from anywhere using location-based information systems. Logistics and freight tracking use cases typically require low data rates, but require wide range and reliable location information.
  • Machine learning refers to the field of studying the methodology to define and solve various problems in the field of artificial intelligence. do.
  • Machine learning is defined as an algorithm that improves the performance of a job through steady experience.
  • An artificial neural network is a model used in machine learning, and may mean an overall model having a problem-solving ability, composed of artificial neurons (nodes) forming a network through a combination of synapses.
  • An artificial neural network may be defined by a connection pattern between neurons of different layers, a learning process for updating model parameters, and an activation function (activation function) that generates output values.
  • a robot can mean a machine that automatically handles or acts on a task given by its own capabilities.
  • a robot having a function of recognizing the environment and performing an operation by determining itself can be referred to as an intelligent robot.
  • Robots can be classified into industrial, medical, household, and military according to the purpose or field of use.
  • the robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving a robot joint.
  • a driving unit including an actuator or a motor to perform various physical operations such as moving a robot joint.
  • the movable robot includes a wheel, a brake, a propeller, and the like in the driving unit, so that it can travel on the ground or fly in the air through the driving unit.
  • Autonomous driving refers to the technology of driving on its own, and autonomous driving means a vehicle that operates without a user's manipulation or with a minimum manipulation of the user.
  • a technology that maintains a driving lane a technology that automatically adjusts speed such as adaptive cruise control, a technology that automatically drives along a predetermined route, and a technology that automatically sets a route when a destination is set, etc. All of this can be included.
  • the vehicle includes a vehicle having only an internal combustion engine, a hybrid vehicle having both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include a train, a motorcycle, etc. as well as a vehicle.
  • the autonomous vehicle can be viewed as a robot having an autonomous driving function.
  • Augmented reality refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR).
  • VR technology provides real-world objects or backgrounds only as CG images
  • AR technology provides CG images made virtually on real objects
  • MR technology is a computer that mixes and combines virtual objects in the real world.
  • MR technology is similar to AR technology in that it shows both real and virtual objects.
  • a virtual object is used as a complement to a real object, whereas in MR technology, there is a difference in that a virtual object and a real object are used with equal characteristics.
  • HMD Head-Mount Display
  • HUD Head-Up Display
  • mobile phone tablet PC, laptop, desktop, TV, digital signage, etc. It can be called.
  • 15 shows an AI system 1 according to an embodiment.
  • the AI system 1 includes at least one of an AI server 200, a robot 100a, an autonomous vehicle 100b, an XR device 100c, a smartphone 100d, or a home appliance 100e. It is connected to the cloud network 10.
  • the robot 100a to which the AI technology is applied, the autonomous vehicle 100b, the XR device 100c, the smartphone 100d, or the home appliance 100e may be referred to as the AI devices 100a to 100e.
  • the cloud network 10 may form a part of the cloud computing infrastructure or may mean a network existing in the cloud computing infrastructure.
  • the cloud network 10 may be configured using a 3G network, a 4G or a Long Term Evolution (LTE) network, or a 5G network.
  • LTE Long Term Evolution
  • each device (100a to 100e, 200) constituting the AI system 1 may be connected to each other through the cloud network (10).
  • the devices 100a to 100e and 200 may communicate with each other through a base station, but may communicate with each other directly without passing through the base station.
  • the AI server 200 may include a server performing AI processing and a server performing operations on big data.
  • the AI server 200 includes at least one or more among robots 100a, autonomous vehicles 100b, XR devices 100c, smart phones 100d, or home appliances 100e, which are AI devices constituting the AI system 1. It is connected through the cloud network 10 and can assist at least some of the AI processing of the connected AI devices 100a to 100e.
  • the AI server 200 may train the artificial neural network according to the machine learning algorithm in place of the AI devices 100a to 100e, and may directly store the learning model or transmit it to the AI devices 100a to 100e.
  • the AI server 200 receives input data from the AI devices 100a to 100e, infers a result value to the received input data using a learning model, and issues a response or control command based on the inferred result value. It can be generated and transmitted to AI devices 100a to 100e.
  • the AI devices 100a to 100e may infer a result value with respect to input data using a direct learning model and generate a response or control command based on the inferred result value.
  • AI technology is applied to the robot 100a, and may be implemented as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, and an unmanned flying robot.
  • the robot 100a may include a robot control module for controlling an operation, and the robot control module may mean a software module or a chip implemented with hardware.
  • the robot 100a acquires state information of the robot 100a using sensor information obtained from various types of sensors, detects (recognizes) surrounding environment and objects, generates map data, or moves and travels. You can decide on a plan, determine a response to user interaction, or determine an action.
  • the robot 100a may use sensor information acquired from at least one sensor among a lidar, a radar, and a camera in order to determine a movement route and a driving plan.
  • the robot 100a may perform the above operations using a learning model composed of at least one artificial neural network.
  • the robot 100a may recognize a surrounding environment and an object using a learning model, and may determine an operation using the recognized surrounding environment information or object information.
  • the learning model may be directly learned from the robot 100a or may be learned from an external device such as the AI server 200.
  • the robot 100a may perform an operation by generating a result using a direct learning model, but transmits sensor information to an external device such as the AI server 200 and receives the result generated accordingly. You may.
  • the robot 100a determines a moving path and a driving plan using at least one of map data, object information detected from sensor information, or object information obtained from an external device, and controls the driving unit to determine the determined moving path and driving plan. Accordingly, the robot 100a can be driven.
  • the map data may include object identification information for various objects arranged in a space in which the robot 100a moves.
  • the map data may include object identification information for fixed objects such as walls and doors and movable objects such as flower pots and desks.
  • the object identification information may include a name, type, distance, and location.
  • the robot 100a may perform an operation or travel by controlling a driving unit based on a user's control / interaction. At this time, the robot 100a may acquire intention information of an interaction according to a user's motion or voice utterance, and determine an answer based on the obtained intention information to perform an operation.
  • the autonomous driving vehicle 100b is applied with AI technology and can be implemented as a mobile robot, a vehicle, or an unmanned aerial vehicle.
  • AI technology is applied to the XR device 100c, HMD (Head-Mount Display), HUD (Head-Up Display) provided in a vehicle, television, mobile phone, smart phone, computer, wearable device, home appliance, digital signage , It can be implemented as a vehicle, a fixed robot or a mobile robot.
  • HMD Head-Mount Display
  • HUD Head-Up Display
  • the robot 100a is applied with AI technology and autonomous driving technology, and can be implemented as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, and an unmanned flying robot.
  • the robot 100a is applied with AI technology and XR technology, and can be implemented as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flying robot, and a drone.
  • the autonomous vehicle 100b is applied with AI technology and XR technology, and may be implemented as a mobile robot, a vehicle, or an unmanned aerial vehicle.

Landscapes

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

Abstract

La présente invention concerne un procédé réalisé par un terminal qui réalise un enregistrement dans un accès de projet de partenariat de troisième génération (3GPP). Selon le procédé, le terminal peut recevoir un message de rejet qui comprend une valeur d'une minuterie de réduction de puissance. De plus, le terminal peut déterminer une valeur d'une minuterie de désenregistrement non 3GPP sur la base de la valeur de la minuterie de réduction de puissance. Dans ce cas, la valeur de la minuterie de désenregistrement non 3GPP peut être déterminée comme étant supérieure à la valeur de la minuterie de réduction de puissance.
PCT/KR2019/012504 2018-09-28 2019-09-26 Terminal effectuant un enregistrement dans un accès non 3 gpp et procédé effectué par celui-ci WO2020067733A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/274,253 US11457425B2 (en) 2018-09-28 2019-09-26 Terminal performing registration in non-3GPP access and method performed by same
US17/943,937 US11638232B2 (en) 2018-09-28 2022-09-13 Terminal performing registration in non-3GPP access and method performed by same

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20180116377 2018-09-28
KR10-2018-0116377 2018-09-28

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US17/274,253 A-371-Of-International US11457425B2 (en) 2018-09-28 2019-09-26 Terminal performing registration in non-3GPP access and method performed by same
US17/943,937 Continuation US11638232B2 (en) 2018-09-28 2022-09-13 Terminal performing registration in non-3GPP access and method performed by same

Publications (1)

Publication Number Publication Date
WO2020067733A1 true WO2020067733A1 (fr) 2020-04-02

Family

ID=69950145

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/012504 WO2020067733A1 (fr) 2018-09-28 2019-09-26 Terminal effectuant un enregistrement dans un accès non 3 gpp et procédé effectué par celui-ci

Country Status (2)

Country Link
US (2) US11457425B2 (fr)
WO (1) WO2020067733A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11457425B2 (en) 2018-09-28 2022-09-27 Lg Electronics Inc. Terminal performing registration in non-3GPP access and method performed by same
US12063711B2 (en) * 2018-11-08 2024-08-13 Nec Corporation Procedure to update the parameters related to unified access control
WO2020147030A1 (fr) * 2019-01-16 2020-07-23 华为技术有限公司 Procédé d'enregistrement de cellule et dispositif terminal
US20210377789A1 (en) * 2020-06-02 2021-12-02 Qualcomm Incorporated Non-access stratum congestion indications
US11968562B2 (en) * 2020-08-10 2024-04-23 Samsung Electronics Co., Ltd. Method and UE for enhancing NAS signaling in radio capability signaling optimization

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018008944A1 (fr) * 2016-07-04 2018-01-11 엘지전자(주) Procédé de gestion d'inscription dans un système de communication sans fil et dispositif associé

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8787337B2 (en) * 2010-08-13 2014-07-22 Intel Corporation Techniques for managing mobility management signaling in a wireless network
EP2451228B1 (fr) * 2010-11-04 2016-08-03 HTC Corporation Procédés pour la configuration d'un temporisateur dans un système de communication sans fil
KR101275036B1 (ko) * 2011-02-14 2013-06-17 에이치티씨 코퍼레이션 타이머 설정 방법
US10986602B2 (en) * 2018-02-09 2021-04-20 Intel Corporation Technologies to authorize user equipment use of local area data network features and control the size of local area data network information in access and mobility management function
US11457425B2 (en) 2018-09-28 2022-09-27 Lg Electronics Inc. Terminal performing registration in non-3GPP access and method performed by same

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018008944A1 (fr) * 2016-07-04 2018-01-11 엘지전자(주) Procédé de gestion d'inscription dans un système de communication sans fil et dispositif associé

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Implicit de-registration over non-3GPP access", C1-181376, 3GPP TSG CT WG1 MEETING #109, 19 February 2018 (2018-02-19), Montreal, Canada, XP051395840 *
QUALCOMM INCORPORATED: "Clarification for the non-3GPP deregistration timer", C1-183211, 3GPP TSG CT WG1 MEETING #111, 14 May 2018 (2018-05-14), Osaka, Japan, XP051439620 *
ZTE: "Non-3GPP deregistration timer", C1-172905, 3GPP TSG CT WG1 MEETING #105, 13 August 2017 (2017-08-13), Krakow, Poland, XP051312958 *
ZTE: "Non-3GPP de-registration timer", C1-185084, 3GPP TSG CT WG1 MEETING #112, 13 August 2018 (2018-08-13), West Palm Beach, FL (USA, XP051572088 *

Also Published As

Publication number Publication date
US20230007614A1 (en) 2023-01-05
US20210360569A1 (en) 2021-11-18
US11638232B2 (en) 2023-04-25
US11457425B2 (en) 2022-09-27

Similar Documents

Publication Publication Date Title
WO2020171529A1 (fr) Procédé permettant de réaliser une communication liée à un état de désactivation de données de commutation de paquets
WO2020141965A1 (fr) Procédé et dispositif de réalisation d'un enregistrement sur un réseau dans un système de communication sans fil
WO2020067749A1 (fr) Contrôle d'accès pour la transmission de données
WO2020189958A1 (fr) Transmission de petites données sans procédure de commutation de chemin
WO2021241905A1 (fr) Sélection efficace de plmn lors d'une défaillance d'authentification pour chaque tranche de réseau dans un réseau d'itinérance
WO2020149522A1 (fr) Ue permettant l'établissement d'une session pdu et twif
WO2020111912A1 (fr) Procédé d'émission et de réception de signal de recherche de mobile dans un système de communications sans fil, et appareil associé
WO2020060007A1 (fr) Procédé et dispositif sans fil pour gérer une session de pdu dans une communication mobile 5g
WO2020067733A1 (fr) Terminal effectuant un enregistrement dans un accès non 3 gpp et procédé effectué par celui-ci
WO2020166767A1 (fr) Procédé et terminal permettant d'afficher des informations pour utiliser une session pdu à ma
WO2020256425A1 (fr) Procédé et appareil pour la prise en charge de sessions de pdu redondantes
WO2020166881A1 (fr) Procédé et dispositif de session pdu ma
WO2020141956A1 (fr) Procédé de sélection de réseau dans un système de communication sans fil
WO2020138985A1 (fr) Procédé permettant de fournir un service de communication dans un système de communication sans fil
WO2021020933A1 (fr) Mesure pour un changement de plmn
WO2021091186A1 (fr) Procédé de commande de réseau pour transmission de politique d'ue
WO2020036466A1 (fr) Procédé, dispositif de communication, et nœud de réseau pour transmettre ou recevoir un message de radiomessagerie
WO2022050659A1 (fr) Commande du trafic
WO2021177716A2 (fr) Communication liée à une multidiffusion
WO2020022716A1 (fr) Procédé et dispositif de commande d'état de transmission de données dans un système de communication sans fil
WO2022075562A1 (fr) Communication liée à une multidiffusion
WO2020067711A1 (fr) Procédé et appareil d'entrée dans un état connecté avec un réseau pour poursuivre une transmission dans un système de communication sans fil
WO2021162500A1 (fr) Communication liée à une session pdu multi-accès
WO2021172768A1 (fr) Procédé et appareil de sélection manuelle de groupe d'accès fermé dans un système de communication sans fil
WO2021187881A1 (fr) Indication de prise en charge de réseau pour des informations d'appariement de session de pdu fournies par un ue

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

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

Country of ref document: EP

Kind code of ref document: A1