WO2020032397A1 - Procédé, équipement utilisateur et nœud de réseau permettant d'effectuer une procédure de requête de connexion - Google Patents

Procédé, équipement utilisateur et nœud de réseau permettant d'effectuer une procédure de requête de connexion Download PDF

Info

Publication number
WO2020032397A1
WO2020032397A1 PCT/KR2019/008269 KR2019008269W WO2020032397A1 WO 2020032397 A1 WO2020032397 A1 WO 2020032397A1 KR 2019008269 W KR2019008269 W KR 2019008269W WO 2020032397 A1 WO2020032397 A1 WO 2020032397A1
Authority
WO
WIPO (PCT)
Prior art keywords
dnn
message
request message
timer
information
Prior art date
Application number
PCT/KR2019/008269
Other languages
English (en)
Korean (ko)
Inventor
김재현
김래영
박상민
윤명준
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2020032397A1 publication Critical patent/WO2020032397A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic

Definitions

  • the present invention relates to next generation mobile communication.
  • the 3rd generation partnership project (3GPP) which enacts the technical specifications of mobile communication systems, is part of an effort to optimize and improve the performance of 3GPP technologies from the end of 2004 to respond to various forums and new technologies related to 4G mobile communication. He started researching LTE / SAE (Long Term Evolution / System Architecture Evolution) technology.
  • LTE / SAE Long Term Evolution / System Architecture Evolution
  • 3GPP SAE centered on 3GPP SA WG2
  • 3GPP SA WG2 is a study on network technology aimed at determining the network structure and supporting mobility between heterogeneous networks in parallel with LTE work of 3GPP TSG RAN, and recently, important standardization issues of 3GPP. Is one of them. This is a work to develop a 3GPP system into a system that supports various radio access technologies based on IP, and has been aimed at an optimized packet-based system that minimizes transmission delay with improved data transmission capability.
  • the Evolved Packet System (EPS) high-level reference model defined by 3GPP SA WG2 includes non-roaming cases and roaming cases in various scenarios. See TS 23.401 and TS 23.402.
  • the network structure diagram of FIG. 1 is a simple reconfiguration.
  • 1 is a structural diagram of an evolved mobile communication network.
  • the EPC may include various components, and in FIG. 1, some of them correspond to a Serving Gateway (S-GW) 52, a PDN Packet Data Network Gateway (GW) 53, and a Mobility Management Entity (MME). 51, a Serving General Packet Radio Service (SGRS) Supporting Node (SGSN), and an enhanced Packet Data Gateway (ePDG).
  • S-GW Serving Gateway
  • GW Packet Data Network Gateway
  • MME Mobility Management Entity
  • SGRS Serving General Packet Radio Service
  • SGSN Serving General Packet Radio Service
  • ePDG enhanced Packet Data Gateway
  • the S-GW 52 acts as a boundary point between the radio access network (RAN) and the core network, and is an element that functions to maintain a data path between the eNodeB 20 and the PDN GW 53.
  • the S-GW 52 serves as a local mobility anchor point. That is, packets may be routed through the S-GW 52 for mobility in the E-UTRAN (Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later).
  • E-UTRAN Universal Mobile Telecommunications System (Evolved-UMTS) Terrestrial Radio Access Network defined in 3GPP Release-8 or later.
  • the S-GW 52 may be connected to other 3GPP networks (RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access). It can also serve as an anchor point for mobility with a network).
  • 3GPP networks RANs defined before 3GPP Release-8, for example, UTRAN or GERAN (GSM (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access). It can also serve as an anchor point for mobility with a network).
  • PDN GW (or P-GW) 53 corresponds to the termination point of the data interface towards the packet data network.
  • the PDN GW 53 may support policy enforcement features, packet filtering, charging support, and the like.
  • mobility management between 3GPP networks and non-3GPP networks for example, untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), Code Division Multiple Access (CDMA) networks, or trusted networks such as WiMax) Can serve as an anchor point for.
  • untrusted networks such as Interworking Wireless Local Area Networks (I-WLANs), Code Division Multiple Access (CDMA) networks, or trusted networks such as WiMax
  • I-WLANs Interworking Wireless Local Area Networks
  • CDMA Code Division Multiple Access
  • WiMax trusted networks
  • FIG. 1 shows that the S-GW 52 and the PDN GW 53 are configured as separate gateways, two gateways may be implemented according to a single gateway configuration option. have.
  • the MME 51 is an element that performs signaling and control functions to support access to a network connection, allocation of network resources, tracking, paging, roaming and handover, etc. of the UE. .
  • the MME 51 controls control plane functions related to subscriber and session management.
  • the MME 51 manages a number of eNodeBs 20 and performs signaling for the selection of a conventional gateway for handover to other 2G / 3G networks.
  • the MME 51 performs functions such as security procedures, UE-to-network session handling, idle UE location management, and the like.
  • the SGSN handles all packet data such as mobility management and authentication of the user to other connecting 3GPP networks (eg GPRS network, UTRAN / GERAN).
  • 3GPP networks eg GPRS network, UTRAN / GERAN.
  • the ePDG acts as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspots, etc.).
  • untrusted non-3GPP networks eg, I-WLAN, WiFi hotspots, etc.
  • a UE (or UE) having IP capability is provided by an operator (ie, an operator) via various elements in the EPC, based on 3GPP access as well as non-3GPP access. Access to an IP service network (eg, IMS).
  • IMS IP service network
  • FIG. 1 illustrates various reference points (eg, S1-U, S1-MME, etc.).
  • reference points eg, S1-U, S1-MME, etc.
  • Table 1 summarizes the reference points shown in FIG. 1.
  • various reference points may exist according to the network structure.
  • This reference point can be used in PLMN-to-PLMN-to-PLMN-to-for example (for PLMN-to-PLMN handover) .It enables user and bearer information exchange for inter 3GPP access network mobility in Idle and / or active state This reference point can be used intra-PLMN or inter-PLMN (eg in the case of Inter-PLMN HO).
  • S4 Reference point between SGW and SGSN that provides relevant control and mobility support between the GPRS core and SGW's 3GPP anchor functionality.
  • S5 Reference point providing user plane tunneling and tunnel management between the SGW and the PDN GW. It is used for SGW relocation because of UE mobility and for connections to the PDN GW where the SGW is not co-located for the required PDN connectivity.It provides user plane tunneling and tunnel management between Serving GW and PDN GW. used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity.) S11 Reference Point Between MME and SGW SGi Reference point between PDN GW and PDN.
  • the PDN may be an operator external public or private PDN or, for example, an in-operator PDN for the provision of IMS services. It is the reference point between the PDN GW and the packet data network.
  • Packet data network may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services.This reference point corresponds to Gi for 3GPP accesses.
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • 5G 5G mobile communication
  • the fifth generation of mobile communications defined by the International Telecommunication Union (ITU) provides data rates of up to 20 Gbps and immersive rates of at least 100 Mbps anywhere.
  • the official name is “IMT-2020” and it aims to be commercialized worldwide in 2020.
  • the ITU presents three usage scenarios, such as 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 usage scenarios that require high reliability and low latency.
  • services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (eg, 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 requiring a latency of less than 1ms.
  • eMBB usage scenarios relate to usage scenarios that require mobile ultra-wideband.
  • FIG. 2 is an exemplary view showing a predicted structure of a next generation mobile communication from a node perspective.
  • the UE is connected to a data network (DN) via a next generation Radio Access Network (RAN).
  • DN data network
  • RAN Radio Access Network
  • the illustrated Control Plane Function (CPF) node is a control plane function of all or part of the mobility management entity (MME) of the 4th generation mobile communication, a serving gateway (S-GW) and a 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).
  • 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 user plane functions of S-GW and P-GW of 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.
  • Unified Data Management illustrated is a kind of server that manages subscriber information, such as the home subscriber server (HSS) of 4G 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 authenticates and manages a UE.
  • the illustrated Network Slice Selection Function is a node for network slicing as described below.
  • FIG. 3A is an exemplary diagram illustrating an architecture for supporting a protocol data unit (PDU) session over a data network
  • FIG. 3B is an exemplary diagram illustrating an architecture for supporting simultaneous access to two data networks.
  • PDU protocol data unit
  • FIG. 3A illustrates an architecture for allowing a UE to simultaneously connect to two data networks using multiple Protocol Data Unit (PDU) sessions. Two SMFs may be selected for two different PDU sessions.
  • PDU Protocol Data Unit
  • 3b shows an architecture for the UE to access two data networks simultaneously using one PDU session.
  • 3A and 3B also illustrate various reference points (eg, N1, N2, N3, etc.).
  • NG-RAN Next Generation-Radio Access Network
  • 5GC 5G Core network
  • Table 2 summarizes the reference points shown in FIGS. 3A and 3B.
  • various reference points may exist according to the network structure.
  • N5, N7, N8, N10, N11, N12, N13, N15, N22, and N24 represent interactions existing between NF services of NFs (Network Functions). These reference points are realized by corresponding NF service-based interfaces. These reference points are then realized by specifying the identified consumer and producer NF services to realize a particular system procedure.
  • Next-generation mobile communication introduces the concept of network slicing in order to provide various services through one network.
  • the slicing of the network is a combination of network nodes having a function necessary when providing a specific service.
  • the network nodes constituting the slice instance may be hardware independent nodes or logically independent nodes.
  • Each slice instance can consist of any combination of nodes needed to form the entire network.
  • one slice instance may provide a service exclusively to the UE.
  • the slice instance may be composed of a combination of some of the nodes constituting the network.
  • the slice instance may not provide a service to the UE alone, but may provide a service to the UE in association with other existing network nodes.
  • a plurality of slice instances may be associated with each other to provide a service to the UE.
  • Slice instances differ from dedicated core networks in that the entire network node, including the core network (CN) node and the RAN, can be separated. Slice instances are also different from dedicated core networks in that network nodes can be logically separated.
  • CN core network
  • the UE there are two ways of handling signaling requests from the UE in a situation where the UE roams to a visited network, such as a VPLMN (Vissited Public Land Mobile Network).
  • the first scheme the local break out (LBO) scheme, processes signaling requests from the UE in the visited network.
  • LBO local break out
  • the second method the home routing (HR) method, the visited network transmits a signaling request from the UE to the home network of the UE.
  • FIG. 4A is an exemplary diagram illustrating an architecture in which a local breakout (LBO) scheme is applied when roaming
  • FIG. 4B is an exemplary diagram illustrating an architecture in which a home routed (HR) scheme is applied when roaming.
  • LBO local breakout
  • HR home routed
  • data of a user is transferred to a data network in a VPLMN.
  • the PCF in the VPLMN interacts with AF to generate PCC rules for services in the VPLMN.
  • the CPF node in the VPLMN generates a PCC rule based on a policy set therein according to a roaming agreement with a Home Public Land Mobile Network (HPLMN) operator.
  • HPLMN Home Public Land Mobile Network
  • data of the UE is delivered to a data network in the HPLMN.
  • data of the UE may be bypassed to a non-3GPP network, such as a Wireless Local Area Network (WLAN) or Wi-Fi.
  • WLAN Wireless Local Area Network
  • Wi-Fi Wireless Fidelity
  • 5A-5F illustrate architectures for bypassing data with a non-3GPP network.
  • WLAN Wireless Local Area Network
  • Wi-Fi Wireless Local Area Network
  • N3IWF Non-3GPP InterWorking Function
  • interworking Even if the UE is out of coverage of the next generation Radio Access Network (RAN), the UE should be able to receive service even through a 4th generation (4G) mobile communication system. This is called interworking. Hereinafter, interworking will be described in detail.
  • RAN Radio Access Network
  • FIG. 6A shows an architecture for interworking when the UE does not roam
  • FIG. 6B shows an architecture for interworking when the UE roams.
  • a packet data network gateway (PGW) for an existing EPC is divided into a PGW-U serving only a user plane and a PGW-C serving a control plane.
  • the PGW-U is merged into the UPF node of the fifth generation core network
  • the PGW-C is merged into the SMF node of the fifth generation core network.
  • the PCRF Policy and Charging Rules Function
  • HSS for existing EPC can be merged into UDM of 5th generation core network.
  • the UE may access the core network via the E-UTRAN, but the UE may access the core network through the 5G radio access network (RAN) and AMF.
  • RAN radio access network
  • VPLMN Vehicle Land Mobile Network
  • HPLMN Home PLMN
  • the N26 interface illustrated in FIGS. 6A and 6B is an interface connected between the MME and the AMF in order to facilitate interworking between the EPC and the NG core.
  • This N26 interface may be selectively supported according to the operator. That is, the network operator may or may not provide an N26 interface for interworking with the EPC.
  • the UE in order for the UE to move from 5GS to EPS, the UE must separately perform a PDN connection request to move an existing PDU session to a new system. In order for the UE to move from EPS to 5GS, the UE must separately perform a PDU connection request in order to move an existing PDN connection to a new system.
  • the SM request of the UE may fail. If the SM request fails, the PDU session used by the UE is still connected to the 5GS side, but the UE may actually be registered as an EPC. Or, if the SM request fails, the PDN connection used by the UE is still connected to the EPS, but the UE may actually be registered as 5GS. In the above two states, if downlink data is generated through a corresponding PDU session or PDN connection, downlink data may not be delivered to the UE.
  • one disclosure of the present specification provides a method for a user equipment (UE) to perform an attach request procedure.
  • the method includes receiving a reject message associated with a data network name (DNN) based congestion control from a network node of a first system, wherein the reject message includes first information on a back-off timer value associated with a DNN based congestion control and the The back-off timer value includes second information related to overriding of the back-off timer used; Driving a back-off timer associated with the DNN based congestion control based on the first information; And if an intersystem change from the first system to the second system is requested, ignore the back-off timer based on the second information, and attach an attach request message to the second system. And transmitting to the system.
  • DNN data network name
  • the second information may be included in the reject message when the network node of the first system anticipates or recognizes the possibility of the intersystem change based on the location of the UE.
  • the attach request message may include third information indicating that the attach request message is transmitted based on the change between the systems.
  • the attach request message includes a session management message for a PDN connection related to the DNN to which the DNN based congestion control is applied, and the third information is based on the DNN based on a session management message for the PDN connection. Can be used to prevent congestion control from being applied.
  • the attach request message includes fourth information indicating that the request type of the message is handover, and the third information and the fourth information include the DNN based congestion control in the session management message for the PDN connection. Can be used to avoid application.
  • the reject message may include a cause value indicating that the session management message has been rejected due to congestion.
  • the first system may be a 5 th generation system (5GS), and the second system may be an evolved packet system (EPS).
  • 5GS 5 th generation system
  • EPS evolved packet system
  • the method may further include receiving an accept message for the attach request message from the second system.
  • one disclosure of the present specification provides a method in which a network node of a first system performs an attach request procedure.
  • the method includes session management related to a DNN to which the DNN based congestion control is applied while a back-off timer associated with DNN based congestion control is running.
  • an attach request message to the second system.
  • the method includes receiving a back-off timer value associated with the DNN based congestion control from a Session Management Function (SMF) of the first network; And driving the back-off timer based on the back-off timer value.
  • SMF Session Management Function
  • the method may further include predicting or recognizing a possibility of the intersystem change based on the location of the UE.
  • the second information may be included in the reject message when a possibility of change between the systems is expected or recognized.
  • the reject message may include a cause value indicating that the session management message has been rejected due to congestion.
  • the first system may be a 5 th generation system (5GS), and the second system may be an evolved packet system (EPS).
  • 5GS 5 th generation system
  • EPS evolved packet system
  • the network node of the first system may be an access and mobility management function (AMF).
  • AMF access and mobility management function
  • a user equipment for performing an attach request procedure.
  • the UE includes a transceiver; And a processor controlling the transceiver, wherein the processor is configured to control the transceiver to receive a rejection message related to data network name (DNN) based congestion control from a network node of a first system, and the rejection message is based on a DNN.
  • DNN data network name
  • 1 is a structural diagram of an evolved mobile communication network.
  • FIG. 2 is an exemplary view showing a predicted structure of a next generation mobile communication from a node perspective.
  • FIG. 3A is an exemplary diagram illustrating an architecture for supporting a protocol data unit (PDU) session over a data network
  • FIG. 3B is an exemplary diagram illustrating an architecture for supporting simultaneous access to two data networks.
  • PDU protocol data unit
  • FIG. 4A is an exemplary diagram illustrating an architecture in which a local breakout (LBO) scheme is applied when roaming
  • FIG. 4B is an exemplary diagram illustrating an architecture in which a home routed (HR) scheme is applied when roaming.
  • LBO local breakout
  • HR home routed
  • 5A-5F illustrate architectures for bypassing data with a non-3GPP network.
  • FIG. 6A shows an architecture for interworking when the UE does not roam
  • FIG. 6B shows an architecture for interworking when the UE roams.
  • 9A and 9B illustrate problems that may occur in the procedure of moving from 5GS to EPS when there is no N26 interface.
  • 10A and 10B illustrate possible problems in the procedure of moving from EPS to 5GS when there is no N26 interface.
  • FIG. 11 is a signal flow diagram illustrating an example of a scheme according to a first proposal of the first disclosure.
  • FIG. 12 is a signal flow diagram illustrating an example of a scheme according to a second proposal of the first disclosure.
  • FIG. 13 is a signal flow diagram illustrating an example of a scheme according to a third proposal of the first disclosure.
  • FIG. 14 is a signal flow diagram illustrating an example of a scheme according to a first proposal of the second disclosure.
  • 15 is a signal flow diagram illustrating an example of a scheme according to a second proposal of the second disclosure.
  • 16 is a signal flow diagram illustrating an example of a scheme according to a third proposal of the second disclosure.
  • FIG. 17 illustrates a wireless communication device according to the disclosure herein.
  • FIG. 18 is a detailed block diagram of a transceiver of a wireless device or network node shown in FIG.
  • FIG 20 shows an AI system 1 according to an embodiment of the present invention.
  • first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
  • first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
  • a component When a component is said to be connected or connected to another component, it may be directly connected or connected to that other component, but other components may exist in between. On the other hand, when a component is mentioned as being directly connected to or directly connected to another component, it should be understood that there is no other component in between.
  • a user equipment UE
  • the illustrated UE may be referred to in terms of UE 100 (Terminal), Mobile Equipment (ME), and the like.
  • the UE may be a portable device such as a laptop, a mobile phone, a PDA, a smart phone, a multimedia device, or a non-portable device such as a PC or a vehicle-mounted device.
  • UE / MS means User Equipment / Mobile Station, UE 100 device.
  • EPS stands for Evolved Packet System and means a core network supporting a Long Term Evolution (LTE) network.
  • LTE Long Term Evolution
  • UMTS evolved network
  • PDN Public Data Network
  • PDN-GW Packet Data Network Gateway
  • Network node of EPS network that performs UE IP address allocation, Packet screening & filtering, Charging data collection
  • Serving GW Network node of EPS network that performs mobility anchor, packet routing, idle mode packet buffering, Triggering MME to page UE function
  • eNodeB A base station of an evolved packet system (EPS), which is installed outdoors, and a cell coverage size corresponds to a macro cell.
  • EPS evolved packet system
  • MME Mobility Management Entity
  • a session is a channel for data transmission.
  • the unit may be a PDN, a bearer, or an IP flow unit.
  • the difference between each unit can be classified into the entire unit network unit (APN or PDN unit), QoS unit within the unit (Bearer unit), and destination IP address unit as defined in 3GPP.
  • APN Abbreviation for Access Point Name, which is provided to the UE as the name of an access point managed by the network. That is, it is a string indicating or distinguishing a PDN.
  • 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 so that the P-GW can be found.
  • the APN may be in the form of internet.mnc012.mcc345.gprs.
  • PDN connection A connection from a UE to a PDN, that is, an association (connection) of a UE expressed by an IP address and a PDN expressed by an APN.
  • UE Context context information of UE used to manage UE in network, that is, context information consisting of UE id, mobility (current location, etc.), and session attributes (QoS, priority, etc.)
  • NAS Non-Access-Stratum: Upper stratum of the control plane (control plane) between the UE and the MME. Supports mobility management, session management, and IP address management between the UE and the network
  • PLMN 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 UE as a name of an access point managed by a network. In 5G systems, the DNN is used equivalent to the APN.
  • next generation so-called fifth generation or 5G mobile communication network.
  • the following procedure shows a procedure for the UE to move from EPS to 5GS in single registration mode or dual registration mode.
  • the UE operating in the single registration mode may perform the following 1-5 processes. However, the UE operating in the dual registration (DR) mode may perform the procedure 5 without performing the processes 1-4.
  • DR dual registration
  • the UE operating in the Single Registration (SR) mode may also be performed from Step 5. However, however, if IP address retention is not supported, the UE operating in the single registration mode may perform from step 1.
  • the UE decides to perform the TAU procedure.
  • the UE sends a TAU request message to perform the TAU procedure.
  • the TAU request message includes a 4G-GUTI mapped with a 5G-GUTI (globally unique temporary id).
  • the UE may include information informing that the UE moves from 5GS in the TAU request message.
  • the eNodeB (ie, base station) sends the TAU request message to the new MME.
  • the new MME determines from the GUTI of the UE mapped from 5G-GUTI that the previous node was an AFM and if the MME supports interworking between 5GS and EPS without N26 interface, the MME rejects the TAU message. Send to the UE.
  • the UE sends an attach request message.
  • the attach request message is generated as follows.
  • the UE When the UE is operating in exclusive registration mode, the UE includes information indicating that it is moving from 5GS and 4G-GUTI mapped from 5G-GUTI Globally Unique Temporary Identifier) in the attach request message.
  • the UE When the UE is operating in dual registration mode, the UE includes information indicating 4G-GUTI in the attach request message indicating that it is moving from 5GS.
  • the UE If the UE transmits the TAU request message in step 2 but the TAU request is rejected because the MME cannot obtain the UE identifier, the UE includes an International Mobile Subscriber Identity (IMSI) in the attach request message.
  • IMSI International Mobile Subscriber Identity
  • the UE If the UE wants to move the PDU session to the EPC as part of the attach request procedure, the UE includes a PDN connection request message in the attach request message.
  • the PDN connection request message may include a request type set to “Handover”, a data network name (DNN) / access point name (APN), and a PDU session ID.
  • the UE includes a PDU session ID in a Protocol Configuration Option (PCO).
  • PCO Protocol Configuration Option
  • the IP address preservation may not be provided.
  • the UE includes the IMSI in the attach request message. And if already included in the attach request message, the UE may not include the request type set to "Handover" in the PDN connection request message.
  • the UE may provide an EPS ID for all mapped EPS bearers in the EPS bearer state information. If the initial attach request, the EPS bearer state information may be empty.
  • the UE can know this.
  • the UE may not include EPS bearers corresponding to 5G QoS flows in EPS bearer state information.
  • the base station sends the attach request message to the new MME.
  • the MME is an identifier to a previous MME / SGSN / AMF.
  • the request message may not be sent.
  • the MME may send an identifier request message to the UE to request IMSI.
  • the new MME sends a location update request message to HSS + UDM.
  • the MME determines that the previous node is AMF based on the information obtained from the UE, and if the MME is configured to support interworking between 5GS and 4PS without N26 interface, the MME is the initial attach Information indicating that the message may not be transmitted to the HSS + UDM.
  • the HSS + UDM may not transmit a location cancellation message to the previous AMF.
  • the AMF implicitly detaches the UE. And releases the remaining PDU sessions within 5GC as possible.
  • the HSS + UDM sends a location update response message to the new MME.
  • the MME determines the address of the PGW-C + SMF for the Create Session Request based on the APN obtained from the UE and based on the subscriber profile obtained from HSS + UDM.
  • the PGW-C + SMF uses a PDU session ID to associate the delivered PDU connection with a PDU session in 5GC.
  • PGW-U + UPF starts routing downlink data packets to the S-GW.
  • the new MME sends a notification request message to the HSS + UDM and receives a response message.
  • the UE If the UE has a PDU session to move to EPS, and the UE wants to use the same IP address / prefix as it is, the UE performs a PDN connection procedure requested by the UE. At this time, the request type in the PDU connection establishment request message is set to "handover".
  • the UE includes a PDU session ID corresponding to a PDU session to be moved to the APN and the EPS.
  • the UE operating in the exclusive registration mode performs the above procedure for each PDU session as soon as the initial attach procedure for the E-UTRAN is not completed.
  • the UE operating in the dual registration mode may perform the process any time after completing the initial attach procedure for the E-UTRAN.
  • the MME determines the address of the PGW-C + SMF for the session creation request message based on the APN obtained from the UE and based on the subscriber profile obtained from the HSS + UDM. The MME may also determine when HSS + UDM should inform the MME of the new P-GW / SMF.
  • the PGW-C + SMF may use the PDU session ID to associate the PDU session to be moved with a PDU session in the 5GC.
  • PGW-U + UPF may begin routing downlink data to the S-GW.
  • the PGW-C + SMF may begin releasing a PDU session in the 5GS to be moved to the EPS.
  • This procedure may be used for the UE to register with 5GS when the UE is also registered with EPC if the UE supports dual registration mode.
  • the UE may have a PDN connection including one or a plurality of EPS bearers.
  • the UE may assign a PDU session ID and transmit the allocated PDU session ID to the PGW-C + SMF through a Protocol Configuration Option (PCO).
  • PCO Protocol Configuration Option
  • the UE is attached to the EPC.
  • the UE transmits a registration request message including information indicating that the UE moves from EPC to 5GS.
  • the UE using the single registration mode may include a registration type set to "mobile registration update” and 5G-GUTI mapped from 4G-GUTI in the registration request message.
  • the UE using the dual registration mode may include a request type set to “initial registration” and a 5G-GUTI or SUPER (Subscription Permanent Identifier) in the registration request message.
  • the NG-RAN performs AMF selection.
  • the NG-RAN delivers a registration request message to the selected AMF.
  • the AMF interworks with 5GS and EPS without N26 interface.
  • the AMF may treat the registration request as an "initial registration” and the AMF may skip the PDU session state synchronization procedure.
  • the UE operating in the exclusive registration mode may include PDU session IDs corresponding to the PDN connection in the PDU session state information.
  • AMF may not perform a procedure for obtaining UE context from MME. have.
  • the AMF may send an identifier request message to the UE to request SUPI. At this time, the UE transmits an identifier response message including SUPI.
  • the AMF forwards information indicating “initial registration” to the UDM. You can't.
  • the UDM may not transmit a location cancellation request message to the previous MME.
  • the MME may detach the UE and release the PDN connection in the EPC.
  • the new AMF sends a registration accept message to the UE.
  • the registration accept message may include information indicating “interworking without N26”.
  • the AMF may set not to update the PDU state information.
  • the UE may send a registration complete message to the AMF.
  • the UE may perform a PDU session establishment procedure.
  • the UE performs the PDU session establishment procedure requested by the UE.
  • the UE includes a request type set as an "existing PDU session" in the PDU session establishment request message or includes a request type set as an "existing emergency PDU session”.
  • the UE may provide a PDU session ID and a DNN corresponding to an existing PDN connection to be moved from EPS to 5GS.
  • the UE operating in the exclusive registration mode may perform this process for each PDU connection immediately after performing process 8.
  • the UE supporting the dual registration mode may perform this process at any time after step 8.
  • a UE supporting dual registration mode may perform this determination only for a subset of PDU sessions.
  • the AMF may select an SMF for Namf_PDUSession_CreateSMContext service based on the DNN obtained from the UE and based on the ID of the PGW / SMF in the subscriber profile obtained from the HSS + UDM.
  • the AMF may also determine when the HSS + UDM will notify the AMF about the ID of the new PGW-C + SMF in the updated subscriber profile.
  • the AMF may include the PDU session ID in the request message sent to the SMF.
  • the SMF may use the DNN and PDU session ID to determine the correct PDU session.
  • the PGW-C + SMF may perform a procedure for releasing resources in the EPC for PDN connection to be moved from 5GS by performing a bearer deactivation procedure initiated by the PGW.
  • NFs within the 5G system operate under nominal capacity to provide sufficient services and connectivity to the UE, and to keep the 5G system under various operating conditions (peak operating time, extreme conditions). It supports measures.
  • Various measures include load (re) balancing, overload control and NAS level congestion control.
  • NAS level congestion control may be applied generally for the DNN, for the S-NSSAI, for the DNN and the S-NSSAI (ie, for all NAS messages).
  • NAS level congestion control is achieved by providing a back-off timer to the UE.
  • 5GC In order to avoid a large number of UEs initiating (almost) simultaneous requests that are deferred due to the back-off timer, 5GC must select a back-off timer value such that the deferred requests are not synchronized.
  • the UE When the UE receives the back-off timer, i) until the back-off timer expires, or ii) until the UE receives a mobile terminated request from the network, or iii) the UE provides an emergency service. But until the UE initiates signaling for high priority access, the UE shall not initiate any NAS signaling for congestion control applied.
  • AMFs and SMFs can apply NAS level congestion control, but cannot apply NAS level congestion control for high priority access and emergency services.
  • the AMF may reject NAS messages received from UEs using any 5G Access Network (5G-AN). If the NAS request is rejected, the AMF sends a Mobility Management (MM) back-off timer to the UE, and the AMF can store the back-off time per UE if it maintains the UE context. The AMF can immediately reject any subsequent request sent from the UE before the stored back-off time expires.
  • 5G-AN 5G Access Network
  • MM Mobility Management
  • the MM back-off timer While the MM back-off timer is running, the UE cannot initiate any NAS request except for deregistration procedure, high priority access, emergency services and mobile destination services. At the end of any such deregistration procedure, the back-off timer continues to run.
  • the UE While the MM back-off timer is running, if the UE is already in a CM (CONNECTION MANAGEMENT) -CONNECTED state, the UE may perform registration for a mobility registration update. If the UE receives a paging request or NAS notification message from the AMF while the MM back-off timer is running, the UE stops the MM back-off timer and the Service Request procedure or mobility. You must initiate the registration process for registration updates.
  • CM CONNECTION MANAGEMENT
  • the MM back-off timer should not affect cell / radio access technology (RAT) / access type and public land mobile network (PLMN) changes.
  • RAT radio access technology
  • PLMN public land mobile network
  • TA Tracking Area
  • the MM back-off timer should not be a trigger of PLMN reselection.
  • the back-off timer stops when a new PLMN is accessed that is not the equivalent PLMN.
  • CM-CONNECTED is a state in which the UE has a NAS signaling connection with the AMF through N1.
  • CM-IDLE is a state in which the UE has no NAS signaling connection established with the AMF through N1.
  • AMF rejects registration request messages or service requests with the MM back-off timer, and the MM back-off timer adds the UE's Periodic Registration Update timer and an unconditional Deregistration timer. If greater than the value, the AMF adjusts the mobile reachable timer and / or unconditional deregistration timer so that the AMF does not unconditionally unregister the UE while the MM back-off timer is running.
  • APN-based Session Management (SM) congestion control may be activated by the MME, for example due to congestion conditions.
  • MME APN-based Session Management
  • the MME may reject an EPS SM (hereinafter ESM) request (eg, PDN connection, bearer resource allocation or bearer resource change request) from the UE when ESM congestion associated with the APN is detected, and SM back-off
  • ESM EPS SM
  • the reject message including the timer may be transmitted. If the UE does not provide an APN, the MME may use the APN used in the PDN GW selection procedure.
  • the MME may deactivate the PDN connection belonging to the congested APN by sending a NAS deactivation EPS banger context request message including the SM back-off timer to the UE.
  • a NAS deactivation EPS banger context request message including the SM back-off timer to the UE.
  • the SM back-off timer is included in the NAS deactivation EPS bearer context request message, cause information indicating "reactivation requested" should not be set.
  • a UE that does not support the SM back-off timer may rather increase the load of the MME by retrying the session management procedure.
  • the MME may store an SM back-off time per UE and APN. The MME may immediately reject any subsequent request from the UE using the APN before the stored SM back-off time expires. If the MME stores an SM back-off time per UE and APN and the MME decides to send a session management request message to a UE connected to a congested APN, the MME sends the session management request message to the UE before sending the session back to the UE. -Initialize the off time.
  • the UE must do the following until the timer expires:
  • the UE does not start the session management procedure for the congested APN.
  • the UE may initiate a session management procedure for another APN.
  • the UE cannot initiate a session management request of any PDN type without the APN.
  • the UE may start a session management procedure for a particular APN.
  • -SM back-off timer may not be stopped due to cell / TA / PLMN / RAT change.
  • the UE may initiate a session management procedure for high priority access and emergency services even when the SM back-off timer is running.
  • the UE If the UE receives a network initiated EPS session management request message for a congested APN while the SM back-off timer is running, the UE should stop the SM back-off timer associated with this APN and respond to the MME.
  • the higher layer of the UE may have a lower access priority. May request the initiation of a session management procedure without
  • the UE may initiate a PDN disconnection procedure (eg, sending a PDN disconnection request message) when the EPS SM back-off timer is running.
  • a PDN disconnection procedure eg, sending a PDN disconnection request message
  • the UE may not delete the associated SM back-off timer when disconnecting the PDN.
  • the UE must support a separate SM back-off timer for every APN that the UE can activate.
  • APN-based SM congestion control can be applied to NAS ESM signaling initiated from the UE in the control plane. SM congestion control does not prohibit the transmission and reception of data. In addition, SM congestion control does not prohibit initiating a service request procedure to activate a user plane bearer using an APN under ESM congestion control.
  • the MME may perform APN based congestion control for a UE using a specific APN by rejecting the attach procedure while delivering a mobility management (MM) back-off timer.
  • MM mobility management
  • an MM back-off timer may be sent to the UE by the MME.
  • the MME may store the back-off time for each UE. The MME may immediately reject any subsequent request from the UE before the stored back-off time expires.
  • the MME may maintain subscriber data for a period of time. This makes it possible to reject subsequent requests without HSS signaling when congestion conditions due to UEs using a particular APN persist.
  • the UE While the MM back-off timer is running, the UE cannot initiate a NAS request for mobility management procedure. However, the UE may initiate mobility management procedures for high priority access and emergency services even when the MM back-off timer is running. While the MM back-off timer is running, the UE may perform tracking area update if it is already in connected mode.
  • the MM back-off timer While the MM back-off timer is running, if the MM back-off timer is started by receiving a reject message in response to a request with a lower priority, the UE configured to override the low access priority may be left without a lower access priority.
  • the mobility management procedure can be started.
  • the higher layer of the UE may request to activate the PDN connection without low access priority.
  • the UE may have an activated PDN connection that does not have a low access priority.
  • DNN based congestion control is used as one of NAS level congestion control.
  • DNN-based congestion control is used to avoid and deal with NAS signaling congestion of a UE using a specific DNN, regardless of Single Network Slice Selection Assistance Information (S-NSSAI). Both the UE and 5GC support features for providing DNN based congestion control.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the SMF may apply DNN based congestion control for the UE by rejecting the PDU fine establishment / modification request messages sent from the UE with the back-off timer and the DNN associated with the back-off timer.
  • the SMF may release the PDU session belonging to the congested DNN by sending a PDU session release request message with the back-off timer to the UE. If the back-off timer is set in the PDU Session Release Request message, the cause value "Reactivation Requested" must not be set.
  • AMF may provide a NAS Transport Error message for NAS transport message carrying a Session Management (SM) message.
  • the NAS move error message may include the DNN associated with the back-off timer. While the back-off timer for a particular DNN is running, the UE does not send any NAS message for that particular DNN.
  • the UE Upon receiving the back-off timer for the DNN, the UE should perform the following operations until the timer expires.
  • the UE should not initiate any SM procedure for congested DNNs.
  • the UE may initiate SM procedures for other DNNs.
  • no SM procedure for the APN (Access Point Name) corresponding to the DNN should be initiated.
  • the UE does not initiate SM requests of any PDU session type without the DNN.
  • the UE may initiate Session Management procedures for a particular DNN.
  • Cell / TA / PLMN / RAT changes, changes in untrusted non-3GPP access networks or changes in access type do not stop the back-off timer.
  • the UE may initiate SM procedures for emergency services and high priority access while the back-off timer is running.
  • the UE If the UE receives a network initiated SM request message for a congested DNN while the back-off timer is running, the UE should stop the SM back-off timer associated with this DNN and respond to 5GC.
  • the UE may initiate a PDU session release procedure (ie, sending a PDU session release request message) while the back-off timer is running. At this time, the UE does not delete the associated back-off timer when releasing the connection of the PDU session.
  • a PDU session release procedure ie, sending a PDU session release request message
  • the UE must support a separate back-off timer for every DNN that the UE can use.
  • 5GC In order to avoid a large number of UEs initiating (almost) simultaneous requests that are deferred due to the back-off timer, 5GC must select a back-off timer value such that the deferred requests are not synchronized.
  • DNN based SM congestion control may be applied to NAS SM signaling of the control plane initiated by the UE.
  • SM congestion control does not prevent initiation of a data transmission or service request procedure of a UE for activating a user plane connection to a DNN that is subject to SM congestion control.
  • DNN-based congestion control may be applied to a specific DNN to a UE that has been serviced in 5GS.
  • the 5GC may provide the UE with the value of the SM back-off timer, and the UE may request additional SM request messages (eg, PDU session establishment request message, PDU session modification request message) for the corresponding DNN until the timer expires. Etc.).
  • additional SM request messages eg, PDU session establishment request message, PDU session modification request message
  • MT mobile terminated
  • the DNN-based SM back-off timer while the UE is running does not stop even when the RAT / System is changed and continuously prevents additional requests for the same DNN / APN.
  • DNN-based congestion control may be applied to a specific APN to a UE that has been serviced in an EPS.
  • the EPC may provide the UE with the value of the SM back-off timer, and the UE may request additional SM request messages (eg PDU session establishment request message, PDU session modification request message) for the APN until this timer expires. Etc.).
  • additional SM request messages eg PDU session establishment request message, PDU session modification request message
  • transmission of a PDN connection release request message and reception of MT signaling are possible.
  • the running APN-based SM back-off timer of the UE does not stop even when the RAT / system is changed and continuously prevents additional requests for the same DNN / APN.
  • the serving PLMN for this UE does not have an N26 interface and the UE operates in a single registration mode
  • the problem scenario below also occurs in dual registration mode, especially when operating in standalone radio.
  • the UE registers with 5GS, creates one or more PDU sessions, and receives the service.
  • a problem eg, congestion
  • DNN / APN # 1 A problem that the UE is using in 5GS, so that DNN based congestion control is applied. That is, the UE receives and drives the back-off timer for DNN / APN # 1 from 5GC.
  • the attach request message includes a PDN connection request message
  • the PDU connection establishment request is for DNN / APN # 1
  • the UE is DNN / APN based congestion for the corresponding DNN / APN # 1 Since control is being applied (ie, running the associated back-off timer), the attach request message cannot be sent to the network. Note that because the DNN / APN generated in the attach process is being subjected to congestion control, the UE may not register with the EPS even though it attempts to escape from 5GS.
  • step 4 or 5 Since there is no N26 interface, in order to move the PDU session of 5GS to the PDN connection of EPS, operation in PGW-U + UPF common to EPS / 5GS is required. However, in step 4 or 5, since the UE failed to request a PDN connection to transfer the PDU session for the DNN / APN running the back-off timer to the EPS, the session of the session registered on the PGW-C + SMF cannot be used. The downlink is still towards 5GS. The reason is that the UE has not performed the operation of moving the PDU session of the 5GS to the EPS through the attach procedure or the PDN connection establishment procedure, so that the PDU session is still served in the 5GS.
  • incoming (MT) data is generated for DNN / APN # 1 to which DNN / APN based congestion control is applied
  • the PGW-U + UPF receiving the incoming (MT) data sends the incoming call to PGW-C + SMF.
  • MT) informs that the data has arrived and the PGW-C + SMF informs the AMF which is currently considered serving node of the UE. Since the UE is currently moving toward the EPS or is out of 5GS, even if the AMF transmits a paging signal to the UE, the UE cannot respond to this and the incoming (MT) data is lost.
  • the PGW-U + UPF transmits incoming (MT) data to the NG-RAN but the UE cannot receive it. That is, in general, even if DNN / APN based congestion control is applied, there should be no problem in receiving MT data, but there is a problem in that the MT data cannot be received due to inter-system change.
  • 9A and 9B illustrate problems that may occur in the procedure of moving from 5GS to EPS when there is no N26 interface.
  • the UE is registered with 5GS and receives one or more PDU sessions from a specific DN.
  • the SMF may apply DNN based congestion control.
  • the SMF transmits a rejection message or releases a session for the 5G Session Management (5GSM) request of the UE and delivers the value of the back-off timer associated with the DNN (eg, DNN / APN # 1) to the UE. .
  • the SMF may transmit the corresponding information to the AMF, and then, if the UL NAS TRANSPORT message containing the SM request is transmitted from the UE, the AMF may proactively apply congestion control. Then, the AMF may deliver the value of the back-off timer to the UE through a DL NAS TRANSPORT message.
  • the UE receiving the value of the back-off timer drives a back-off timer (eg, T3396) in association with the corresponding DNN / APN. While this back-off timer is running, the UE cannot send an SM request message for the corresponding DNN / APN.
  • a back-off timer eg, T3396
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • the UE Since there is no N26 interface between the MME and the AMF, the UE sends a TAU request or attach request message for interworking in order for the UE to register with EPS. For example, the UE may first transmit a TAU request message and, upon receiving a rejection message, transmit an attach request message.
  • the PDN connection request may be piggybacked on the attach request message and transmitted.
  • the UE may piggyback and transmit the PDN connection request message to set a default bearer in the attach request message.
  • the PDN connection request is related to the DNN / APN to which congestion control is applied, the UE is applying DNN / APN based congestion control for the DNN / APN (that is, the back-off timer related to the DNN / APN).
  • UE is not able to send an attach request message to the network.
  • ADN Even if the UE sends an attach request message to the MME due to a malfunction, ADN also applies congestion control to the corresponding DNN / APN, so the PDN connection procedure may fail and the attach procedure may also fail. . This causes a problem in that the UE cannot register with the EPS even though it attempts to leave 5GS because the congestion control is applied to the associated DNN / APN when the UE performs the attach.
  • the SMF / PGW may send a message such as Downlink Data Notification (DDN) to 5GS, which is known as the location of the current PDU session.
  • DDN Downlink Data Notification
  • the AMF rejects this or the related information is not updated, the AMF may transmit a paging signal to the UE, but all of them fail.
  • DNN / APN based congestion control is applied, the UE should be able to receive incoming data, which may cause a problem that the UE cannot receive MT data due to intersystem change. In the worst case, there may be a problem that the corresponding downlink data is discarded.
  • the UE receives the service by creating one or more PDN connections after attaching to the EPS.
  • APN based congestion control is applied. That is, the UE receives and drives the back-off timer for DNN / APN # 1 from the EPC.
  • the UE performs a registration procedure to 5GS, and then performs a PDU session establishment procedure to move the PDN connection serviced through EPS to 5GS. However, if congestion control is applied for DNN / APN # 1 in the EPS (ie, the back-off timer is running), the UE is prohibited from requesting 5GS to establish a PDU connection.
  • step 5 Since there is no N26 interface between the 5GS and the EPS, in order to move the PDN connection of the EPS to the PDU session of the 5GS, operation in the PGW-U + UPF common to the EPS / 5GS is required. However, in step 4, the downlink of the session registered on the PGW-C + SMF still remains because the UE fails to request the PDU creation to move the PDN connection to the 5GS on the DNN / APN running the back-off timer. It's towards EPS. In other words, since the UE did not perform an operation of moving the PDN connection of the EPS to 5GS through the PDU generation request, the PDN connection is still maintained in the EPS.
  • PGW-U + UPF receiving the MT data is called to PGW-C + SMF.
  • the PGW-C + SMF informs the S-GW and the S-GW informs the MME. Since the UE is currently moving toward 5GS, the UE cannot respond to this even if the MME sends a paging signal to the UE. As a result, the incoming MT data is lost.
  • the S-GW transmits incoming (MT) data to the base station eNb but the UE cannot receive it. That is, although DNN / APN-based congestion control is generally applied, there should be no problem in receiving MT data, but there is a problem that MT data cannot be received due to inter-system change. .
  • 10A and 10B illustrate possible problems in the procedure of moving from EPS to 5GS when there is no N26 interface.
  • FIGS. 10A and 10B 1) Examples of interworking between EPS and 5GS or EPC and 5GCN without an N26 interface are shown in FIGS. 10A and 10B.
  • UE is registered in EPS and is receiving service by creating one or more PDN connections from a specific DN.
  • a problem eg congestion
  • the PGW / SMF and the MME apply APN based congestion control.
  • the MME transmits or releases the rejection message for the ESM (EPS Session Management) request message of the UE and delivers the (SM) back-off timer value associated with the APN (APN / DNN # 1) to the UE. Can be.
  • ESM EPS Session Management
  • the UE receiving the back-off timer value drives an (SM) back-off timer (eg, T3396) associated with the corresponding DNN / APN. While this back-off timer is running, the UE cannot send an SM request message for the corresponding DNN / APN.
  • SM SM back-off timer
  • the UE moves (eg mobility) from EPS to 5GS for some reason.
  • the UE may be out of coverage of the EPS due to movement.
  • the UE performs a registration procedure to register with 5GS. Since there is no N26 interface between 5GS and EPS, when the UE moves to 5GS, the UE performs a registration procedure.
  • the UE If the UE successfully registers with the 5GS, the UE performs an SM request procedure, that is, a PDU session establishment procedure, to move an existing PDN connection to a new system (ie, 5GS). Send a PDU session establishment request message).
  • an SM request procedure that is, a PDU session establishment procedure
  • the UE if congestion control is applied for DNN / APN # 1 in the EPS (ie, the back-off timer is running), the UE is prohibited from requesting 5GS to establish a PDU connection. That is, when the UE sends a PDU session establishment request message for the DNN / APN to which congestion control is applied, the PDU connection procedure may fail due to congestion of the corresponding DN, and eventually, the SM request may fail.
  • the SMF / PGW may send a message such as DDN to the EPS maintaining the PDN connection. Then, the MME may reject this or may transmit a paging signal to the UE when the related information is not updated. However, since the UE has moved to 5GS, all of these have to fail. Even if DNN / APN based congestion control is applied, the UE should be able to receive incoming data, which may cause a problem that the UE cannot receive MT data due to intersystem change. In the worst case, the corresponding incoming data (eg, downlink data) may be discarded and lost.
  • DNN / APN based congestion control is applied, the UE should be able to receive incoming data, which may cause a problem that the UE cannot receive MT data due to intersystem change. In the worst case, the corresponding incoming data (eg, downlink data) may be discarded and lost.
  • Disclosure of the present disclosure is to propose a method for solving a problem that may occur when a specific data network is congested when interworking between 3GPP-based 5G system (5G mobile communication system, next-generation mobile communication system) and EPS. It is done.
  • 3GPP-based 5G system 5G mobile communication system, next-generation mobile communication system
  • EPS next-generation mobile communication system
  • the disclosures herein may be implemented in a combination of one or more of the following measures / acts / configurations / steps.
  • the disclosure and the proposal to be described below are categorized for convenience of description. Each disclosure and suggestion may be performed independently or implemented in combination with other disclosures and suggestions.
  • the UE may be in the following situation.
  • the UE registers first with 5GS, where it can receive information from the network indicating that interworking without N26 is supported (eg, an indication that interworking is supported without an N26 interface). Upon receiving the information or indication, the UE recognizes that the network supports interworking without an N26 interface.
  • the UE may support only single registration or dual registration but may use only one radio. (I.e. you can only receive services from one system at a time and not from both systems at the same time). However, the disclosure herein is not limited to UEs that can only use a single radio.
  • the UE creates one or more PDU sessions to receive the service.
  • the UE is subject to congestion control for a specific DNN (eg, DNN / APN # 1) from 5GS. That is, the UE receives and applies a back-off timer for DNN / APN # 1 from 5GS. At this time, while the back-off timer for DNN / APN # 1 is operated in the 5GS, the UE cannot perform an additional SM procedure for DNN / APN # 1.
  • a specific DNN eg, DNN / APN # 1
  • the UE receives and applies a back-off timer for DNN / APN # 1 from 5GS. At this time, while the back-off timer for DNN / APN # 1 is operated in the 5GS, the UE cannot perform an additional SM procedure for DNN / APN # 1.
  • the UE may move between 5GS to EPS by moving (e.g., by moving out of coverage) or by making a request for a particular capability (e.g., by voice call).
  • An inter-system change may be required.
  • the AMF may perform the operations described below at the time when the possibility of intersystem change is expected / recognized based on information about the location of the UE (eg, a registration area) before the intersystem change is required.
  • the prediction / recognition of the possibility of cross-system change from 5GS to EPS of the UE may be performed by the AMF by identifying the location of the UE (eg, TAI or cell ID) through a registration update procedure recently performed by the UE. Can be.
  • the UE may periodically provide the AMF with information about the current location in addition to the registration update procedure, through which the AMF may determine the location (eg, TAI or cell ID) of the UE to predict / recognize the possibility of cross-system change. Can be.
  • the location eg, TAI or cell ID
  • the AMF may manage the location of the UE based on the TAI or cell ID list. For example, the AMF may manage the location of the UE into 4GS and 5GS based on the TAI or cell ID list. In one example, the AMF uses a TAI or cell ID list, respectively, i) TAI or cell ID (TAI for 4GS or cell ID list A for 4GS) corresponding to 4GS or ii) TAI or cell ID (TAI for 5GS or cell ID list B for 5GS).
  • TAI or cell ID list respectively, i) TAI or cell ID (TAI for 4GS or cell ID list A for 4GS) corresponding to 4GS or ii) TAI or cell ID (TAI for 5GS or cell ID list B for 5GS).
  • the AMF is located in an area corresponding to a TAI or cell ID corresponding to 5GS and then moves to an area corresponding to a 4GS coverage boundary (ie, an area corresponding to a TAI or cell ID corresponding to 4GS). Recognizing that one can predict / recognize the possibility of a cross-system change (a cross-system change from 5GS to 4GS). In addition, the AMF moves from the AMF to an area corresponding to a TAI or cell ID corresponding to 4GS and then moves to an area corresponding to a 5GS coverage boundary (ie, an area corresponding to a TAI or cell ID corresponding to 5GS). Recognizing one, one can anticipate / recognize the possibility of an intersystem change (an intersystem change from 4GS to 5GS).
  • the operation of the first disclosure can be applied to all DNNs / APNs.
  • the operation of the first initiation may be applied only to a specific DNN / APN for a specific service.
  • the specific service may include, for example, a high priority service, an IMS voice call, an ultra reliable service, and the like.
  • the AMF determines the specific DNN (DNN / APN #) of the UE. 1, do not apply / apply congestion control to the SM request for the DNN / APN to which congestion control is applied (do not provide a back-off timer value).
  • the UE may send a PDU session establishment / modification / release request message (hereinafter referred to as SM request message) for a specific DNN (DNN / APN # 1) to 5GS.
  • SM request message a PDU session establishment / modification / release request message
  • the AMF rejects the SM request message transmitted by the UE at the time when the corresponding UE anticipates / recognizes the possibility of intersystem change from 5GS to EPS, and transmits a rejection message to the UE.
  • the rejection message includes a cause of rejection.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the AMF may not provide the UE with the SM (or MM) back-off timer value for the DNN (DNN / APN # 1) associated with the SM request message.
  • the AMF may accept an SM request message sent by the UE and send an accept message to the UE.
  • the UE will not run the back-off timer for congested DNNs (DNN / APN # 1) if a cross-system change is required and the cross-system change is performed with EPS. You may not.
  • the UE may piggyback the PDN connection request message for the congested DNN and transmit an attach request message to the EPS. Alternatively, the UE may transmit a separate PDN connection request message or an EPS bearer resource modification request message for a congested DNN to the EPS.
  • a UE requesting / recognizing that there is no possibility of intersystem change by AMF may transmit a SM request message for congested DNN to 5GS. Then, the AMF may reject the SM request message of the corresponding UE and transmit the rejection message to the UE.
  • the reject message may include a reject cause value and a back-off timer value.
  • the reject cause value may be # 22 congestion
  • the back-off timer value may be the SM back-off timer value (T3396) or the MM back-off timer value (T3346) for a specific DNN (DNN / APN # 1). Can be.
  • the UE drives the back-off timer based on the received back-off timer value and cannot send an SM request message for a specific DNN (DNN / APN # 1) to 5GS until the back-off timer expires. .
  • the UE piggybacks and transmits a PDN connection request message to an attach request message when connecting to a new CN (ie, EPC) to move a PDU session between CNs.
  • a new CN ie, EPC
  • the UE may not transmit a PDN connection request message.
  • the UE may transmit the PDN connection request message for the movement of the PDU session after the EMM-REGISTERED state after transmitting the attach request message.
  • the ESM request message may include information that the message relates to a change between systems.
  • the ESM request message may include information (information such as an indicator or a flag) indicating that the ESM request message is transmitted based on a change between systems (or moving in 5GC), rather than a general purpose.
  • the ESM request message may include information (information such as indicator, flag, etc.) indicating that the transmission of this message is transmitted for session transfer to a new system such as location reporting.
  • the information indicating that the 5GC is included in the Attach Request message may be used as information indicating a change between systems.
  • the UE may include only information regarding the change between systems in the ESM request message for the DNN / APN to which DNN / APN based congestion control is applied. Alternatively, the UE may include information indicating the change between systems in the ESM request message for every DNN / APN.
  • the MME will set a back-off timer value with an ESM rejection message if the APN / DNN associated with the ESM request is congested. May transmit to the UE.
  • the ESM request message sent by the UE meaning an ESM request message or an attach request message that piggybacks the ESM request message
  • Information to be sent for the purpose of, or ii) the request type of the ESM request message is "handover" and the ESM request message includes information indicating a change between ESM request systems.
  • the network eg, MME
  • the MME may send a Create Session Request message to the S-GW without applying congestion control to the ESM request message (the specific procedure is the attach procedure or PDN of the LTE standard). PDN Connectivity Request procedure).
  • the MME may include information indicating that the message is not a general request but a request based on a change between systems in the session creation request message and transmit the information to the S-GW.
  • the S-GW may process the session creation request message received from the MME and forward the request to the SMF + PGW-C.
  • the S-GW may also specify that this request is based on a change between systems.
  • the MME sends a response message to the UE.
  • the MME may optionally send a PDN Connectivity Accept-standalone or piggybacked on Attach Accept to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in the per APN / DNN ESM backoff timer (T3396) value and the cause value (# 22 congestion or due to congestion for interworking). At least one of)).
  • T3396 ESM backoff timer
  • the cause value # 22 congestion or due to congestion for interworking. At least one of
  • FIG. 11 is a signal flow diagram illustrating an example of a scheme according to a first proposal of the first disclosure.
  • FIGS. 9A and 9B Description of the same contents as those of FIGS. 9A and 9B will be omitted, and FIG. 11 will be described based on differences.
  • step 4 of FIG. 11 Operations before step 4 of FIG. 11 are the same as steps 1 to 3 of FIGS. 9A and 9B.
  • the AMF can know the location (eg, TAI or cell ID) of the UE through a registration update procedure recently performed by the UE.
  • the UE may periodically provide the AMF with information about the current location in addition to the registration update procedure, through which the AMF may know the location (eg, TAI or cell ID) of the UE.
  • the AMF may predict / recognize the possibility of intersystem change before a change between systems occurs based on the location of the UE.
  • the UE may send an SM request message (such as a PDU session establishment request or PDU session modification) to the AMF.
  • an SM request message such as a PDU session establishment request or PDU session modification
  • the AMF requests SM for a specific DNN (DNN / APN # 1, DNN / APN to which congestion control applies) of the UE. Do not apply / enforce congestion control (do not send back-off timer).
  • the AMF can accept the SM request message sent by the UE and send an accept message to the UE.
  • the AMF may transmit an SM request message to the SMF / PGW-C.
  • the UE may reject the SM request message transmitted by the UE and transmit a rejection message to the UE.
  • the rejection message may include a cause of rejection.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion.
  • the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the AMF may not provide the UE with the SM (or MM) back-off timer value for the DNN (DNN / APN # 1) associated with the SM request message.
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • the ESM request message may contain information that this message relates to a change between systems.
  • the ESM request message may include information (corresponding to “interworking change” in FIG. 11) indicating that the ESM request message is transmitted based on a change between systems.
  • the ESM request message may include information (corresponding to “session transfer” in FIG. 11) indicating that the transmission of this message is sent for a session transfer to a new system such as location reporting.
  • the MME may process the ESM request without applying congestion control to the ESM request message.
  • the MME may send an ESM request message to the SMF / PGW-C.
  • SMF / PGW-C may update the session context and delete old information.
  • the SMF / PGW-C may transmit an attach accept message or an ESM accept message (eg, PDN accept message) to the MME.
  • the MME may then send an attach accept message or a PDN accept message to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in the per APN / DNN ESM backoff timer (T3396) value and the cause value (# 22 congestion or due to congestion for interworking). At least one of)).
  • the second proposal of the first disclosure is described below. For reference, descriptions of the same contents as the first proposal of the first disclosure will be omitted, and descriptions will be given based on differences from the first proposal of the first disclosure.
  • Congestion control may be performed / applied to the SM request for (DNN / APN # 1, DNN / APN to which congestion control is applied).
  • the UE may send a PDU session establishment / modification / release request message (hereinafter referred to as SM request message) for a specific DNN (DNN / APN # 1) to 5GS.
  • SM request message a PDU session establishment / modification / release request message
  • the AMF rejects the SM request message transmitted by the UE and transmits a rejection message to the UE.
  • the rejection message includes information about overriding the SM back-off timer value (or MM back-off timer value) for a specific DNN (DNN / APN # 1) and the back-off timer when a change between systems is required. (overriding information or overriding indication).
  • the reject message may also include a cause value (cause value).
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion.
  • the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the NAS MM layer of the UE receives the SM back-off timer value.
  • the NAS MM layer of the UE may transmit a SM back-off timer value to the NAS SM layer, and the NAS SM layer may recognize the application of DNN / APN based congestion control.
  • the NAS SM layer drives the back-off timer using the MM back-off timer value provided from AMF as the SM back-off timer value.
  • the UE Even when the UE is running a back-off timer based on the received back-off timer value, if a change is required between systems due to movement, the UE is informed to ignore the back-off timer if a change between systems is required. Based on this, the back-off timer may be ignored and the attach request message may be sent to the EPS. Specifically, the UE ignores the SM back-off timer for a specific DNN (DNN / APN # 1, congested DNN / APN), and requests a PDN connection for a specific DNN (DNN / APN # 1) in an attach request message. The message can be piggybacked and sent to the MME. Alternatively, in case of EPC and UE supporting attach without PDN connection, PDN connection request message is not transmitted, but PDN connection request message is transmitted for moving PDU session after EMM-REGISTERED state after transmitting attach request message. It may be.
  • DNN / APN # 1 congested DNN / APN
  • the UE may not set MS / UE to low priority NAS signaling in an attach request message or PDN connection request message for a specific DNN (DNN / APN # 1) (MS / UE is not configured for NAS).
  • signaling low priority may include a low priority indicator set.
  • the UE may transmit an attach request message or a PDN connection request message for a specific DNN (DNN / APN # 1).
  • the network (MME) then sends a DNN / DNN for an attach request message set to “MS / UE is not set to low priority NAS signaling” or PDN connection request message for a specific DNN (DNN / APN # 1).
  • PDN connection request message can be processed without applying APN-based congestion control.
  • the ESM request message may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (information such as an indicator or a flag) indicating that the ESM request message is transmitted based on a change between systems (or moving in 5GC), rather than a general purpose.
  • the ESM request message may include information (information such as indicator, flag, etc.) indicating that the transmission of this message is transmitted for session transfer to a new system such as location reporting.
  • the information indicating that the 5GC is included in the Attach Request message may be used as information indicating a change between systems.
  • the UE may include only information regarding the change between systems in the ESM request message for the DNN / APN to which DNN / APN based congestion control is applied. Alternatively, the UE may include information indicating the change between systems in the ESM request message for every DNN / APN.
  • the MME will set a back-off timer value with an ESM rejection message if the APN / DNN associated with the ESM request is congested. May transmit to the UE.
  • the ESM request message sent by the UE meaning an ESM request message or an attach request message that piggybacks the ESM request message
  • Information to be sent for the purpose of, or ii) the request type of the ESM request message is "handover" and the ESM request message includes information indicating a change between ESM request systems.
  • the network eg, MME
  • the MME may send a Create Session Request message to the S-GW without applying congestion control to the ESM request message (the specific procedure is the attach procedure or PDN of the LTE standard). PDN Connectivity Request procedure).
  • the MME may include information indicating that the message is not a general request but a request based on a change between systems in the session creation request message and transmit the information to the S-GW.
  • the S-GW may process the session creation request message received from the MME and forward the request to the SMF + PGW-C.
  • the S-GW may also specify that this request is based on a change between systems.
  • the MME sends a response message to the UE.
  • the MME may optionally send a PDN Connectivity Accept-standalone or piggybacked on Attach Accept to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in the per APN / DNN ESM backoff timer (T3396) value and the cause value (# 22 congestion or due to congestion for interworking). At least one of)).
  • T3396 ESM backoff timer
  • the cause value # 22 congestion or due to congestion for interworking. At least one of
  • 5GS sends a SM request message (such as a PDU session establishment / modification / release request message) for a congested DNN by a UE that is expected / recognized that there is no possibility of intersystem change by AMF. Can also be sent to.
  • the AMF may reject the SM request message of the UE and transmit the rejection message to the UE.
  • the reject message may include a reject cause value and a back-off timer value.
  • the reject cause value may be # 22 congestion
  • the back-off timer value may be an SM back-off timer value (T3396) or an MM back-off timer value (T3346) for a specific DNN (DNN / APN # 1). Can be.
  • the UE drives the back-off timer based on the received back-off timer value, and cannot send an SM request message for a specific DNN (DNN / APN # 1) to 5GS until the back-off timer expires. .
  • FIG. 12 is a signal flow diagram illustrating an example of a scheme according to a second proposal of the first disclosure.
  • FIGS. 9A, 9B, and 11 Description of the same contents as those of FIGS. 9A, 9B, and 11 will be omitted, and FIG. 12 will be described based on differences.
  • step 4 of FIG. 12 Operations before step 4 of FIG. 12 are the same as steps 1 to 3 of FIGS. 9A and 9B.
  • steps 4 and 5 of FIG. 12 are the same as those of steps 4 and 5 of FIG.
  • AMF congests the SM request for a specific DNN (DNN / APN # 1, DNN / APN to which congestion control applies) of the UE. Perform / apply control.
  • the AMF may reject the SM request message transmitted by the UE and transmit a rejection message to the UE.
  • the rejection message includes information about overriding the SM back-off timer value (or MM back-off timer value) for a specific DNN (DNN / APN # 1) and the back-off timer if cross-system change is required. (overriding information or overriding indication).
  • the reject message may also include a cause value (cause value).
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • the UE may request a back-off timer if the change between systems is required.
  • the back-off timer can be ignored based on the information to ignore.
  • the UE may transmit an attach request message to the EPS. Specifically, the UE ignores the SM back-off timer for a specific DNN (DNN / APN # 1, congested DNN / APN), and requests a PDN connection for a specific DNN (DNN / APN # 1) in an attach request message.
  • the message can be piggybacked and sent to the MME.
  • PDN connection request message in case of EPC and UE supporting attach without PDN connection, PDN connection request message is not transmitted, but PDN connection request message is transmitted for moving PDU session after EMM-REGISTERED state after transmitting attach request message. It may be.
  • the ESM request message (PDN connection request message piggybacked in the attach request message or PDN connection request message transmitted alone) may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (corresponding to “interworking change” in FIG. 12) indicating that the ESM request message is transmitted based on a change between systems.
  • the ESM request message may include information (corresponding to “session transfer” in FIG.
  • the UE may not set the MS / UE to low priority NAS signaling in the attach request message or PDN connection request message for a specific DNN (DNN / APN # 1) (MS / UE is not configured for NAS).
  • signaling low priority may be set to include a low priority indicator set.
  • step 9 and step 10 of FIG. 12 The operation of step 9 and step 10 of FIG. 12 is the same as that of step 9 and step 10 of FIG.
  • the third proposal of the first disclosure will be described below.
  • descriptions of the same contents as the first proposal or the second proposal of the first disclosure will be omitted, and the description will be mainly focused on differences between the first proposal and the second proposal of the first disclosure.
  • the AMF applies congestion control to the SM request for a specific DNN of the UE as described below. Can be performed / applied.
  • the UE may send an SM request message for a specific DNN (DNN / APN # 1) to 5GS.
  • the AMF rejects the SM request message transmitted by the UE and transmits a rejection message to the UE.
  • the reject message may include a reject cause value.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the reject message may include an SM back-off timer value (or MM back-off timer value) for a specific DNN (DNN / APN # 1).
  • the AMF is expected to recognize that the SM back-off timer (T3396) value (or MM back-off timer (T3346) value) provided to the UE is expected / aware of the possibility of cross-system change. It may be set to have a value smaller than the general SM back-off timer value (or MM back-off timer value) provided to the UE. If cross-system change is required with EPS, the back-off timer driven based on the smaller value of the back-off timer expires faster than the back-off timer of the UE without the possibility of cross-system change. Then, the UE requiring change between systems can quickly send an attach request message, a PDN connection request message, or an EPS bearer resource modification message for a specific DNN (DNN / APN # 1, congested DNN / APN).
  • AMF may use a back-off timer value provided to a UE that is expected / recognized that there is no possibility of cross-system change. May be provided to the UE.
  • the back-off timer value used for the new back-off timer T35xy different from the SM back-off timer T3396 (or MM back-off timer T3346) is included in the reject message and provided to the UE. can do.
  • the new back-off timer T35xy may have a timer value smaller than a typical SM back-off timer T3396 (or MM back-off timer T3346).
  • the NAS MM layer of the UE receives the back-off timer (T35xy) value.
  • the NAS MM layer of the UE may transmit a back-off timer (T35xy) value to the NAS SM layer, and the NAS SM layer may recognize application of DNN / APN based congestion control.
  • the NAS SM layer drives the back-off timer using the back-off timer (T35xy) value provided from the AMF as the SM back-off timer value.
  • the ESM request message may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (information such as an indicator or a flag) indicating that the ESM request message is transmitted based on a change between systems (or moving in 5GC), rather than a general purpose.
  • the ESM request message may include information (information such as indicator, flag, etc.) indicating that the transmission of this message is transmitted for session transfer to a new system such as location reporting.
  • the information indicating that the 5GC is included in the Attach Request message may be used as information indicating a change between systems.
  • the MME will set a back-off timer value with an ESM rejection message if the APN / DNN associated with the ESM request is congested. May transmit to the UE.
  • the ESM request message sent by the UE meaning an ESM request message or an attach request message that piggybacks the ESM request message
  • Information to be sent for the purpose of, or ii) the request type of the ESM request message is "handover" and the ESM request message includes information indicating a change between ESM request systems.
  • the network eg, MME
  • the MME may send a Create Session Request message to the S-GW without applying congestion control to the ESM request message (the specific procedure is the attach procedure or PDN of the LTE standard). PDN Connectivity Request procedure).
  • the MME may include information indicating that the message is not a general request but a request based on a change between systems in the session creation request message and transmit the information to the S-GW.
  • the S-GW may process the session creation request message received from the MME and forward the request to the SMF + PGW-C.
  • the S-GW may also specify that this request is based on a change between systems.
  • the MME sends a response message to the UE.
  • the MME may optionally send a PDN Connectivity Accept-standalone or piggybacked on Attach Accept to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in ESM back-off timer value (ESM backoff timer (T3396) or new back-off timer (T35xy)) and cause value (# 22 congestion or new cause value) by APN / DNN.
  • ESM back-off timer value ESM backoff timer (T3396) or new back-off timer (T35xy)
  • cause value # 22 congestion or new cause value
  • the ESM request message for the purpose of location update based on the change between the systems is allowed and processed, and further ESM request (the ESM request not related to the change between the systems) to the corresponding DNN / APN can be prevented.
  • 5GS sends a SM request message (such as a PDU session establishment / modification / release request message) for a congested DNN by a UE that is expected / recognized that there is no possibility of cross-system change by AMF. Can also be sent to.
  • the AMF may reject the SM request message of the corresponding UE and transmit the rejection message to the UE.
  • the reject message may include a reject cause value and a back-off timer value.
  • the reject cause value may be # 22 congestion
  • the back-off timer value may be the SM back-off timer value (T3396) or the MM back-off timer value (T3346) for a specific DNN (DNN / APN # 1).
  • the UE drives the back-off timer based on the received back-off timer value and cannot send an SM request message for a specific DNN (DNN / APN # 1) to 5GS until the back-off timer expires. .
  • FIG. 13 is a signal flow diagram illustrating an example of a scheme according to a third proposal of the first disclosure.
  • step 4 of FIG. 13 Operations before step 4 of FIG. 13 are the same as steps 1 to 3 of FIGS. 9A and 9B.
  • steps 4 and 5 of FIG. 13 are the same as those of steps 4 and 5 of FIG. 11.
  • AMF congests the SM request for a specific DNN (DNN / APN # 1, DNN / APN to which congestion control applies) of the UE. Perform / apply control.
  • the AMF may reject the SM request message transmitted by the UE and transmit a rejection message to the UE.
  • the reject message may include a reject cause value.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the reject message may include an SM back-off timer value (or MM back-off timer value) for a specific DNN (DNN / APN # 1).
  • the AMF is expected to recognize that the SM back-off timer (T3396) value (or MM back-off timer (T3346) value) provided to the UE is expected / aware of the possibility of cross-system change. It may be set to have a value smaller than the general SM back-off timer value (or MM back-off timer value) provided to the UE.
  • AMF may use a back-off timer value provided to a UE that is expected / recognized that there is no possibility of cross-system change. May be provided to the UE.
  • the back-off timer value used for the new back-off timer T35xy different from the SM back-off timer T3396 (or MM back-off timer T3346) is included in the reject message and provided to the UE. can do.
  • the new back-off timer T35xy may have a timer value smaller than a typical SM back-off timer T3396 (or MM back-off timer T3346).
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • SM back-off timer T3396
  • new back-off timer T35xy
  • the -off timer expires earlier than the back-off timer of the UE which has no possibility of intersystem change. If a change between systems is required due to a cause of movement or the like, and the smaller back-off timer value expires, the UE may send an attach request message to the EPS to move the PDU session from 5GS to EPS.
  • the UE ignores the SM back-off timer for a specific DNN (DNN / APN # 1, congested DNN / APN), and requests a PDN connection for a specific DNN (DNN / APN # 1) in an attach request message.
  • the message can be piggybacked and sent to the MME.
  • PDN connection request message is not transmitted, but PDN connection request message is transmitted for moving PDU session after EMM-REGISTERED state after transmitting attach request message. It may be.
  • the ESM request message (PDN connection request message piggybacked in the attach request message or PDN connection request message transmitted alone) may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (corresponding to “interworking change” in FIG. 13) indicating that the ESM request message is transmitted based on a change between systems.
  • the ESM request message may include information (corresponding to "session transfer” in FIG. 13) indicating that the transmission of this message is sent for a session transfer to a new system such as location reporting.
  • the UE may not set the MS / UE to low priority NAS signaling in the attach request message or PDN connection request message for a specific DNN (DNN / APN # 1) (MS / UE is not configured for NAS).
  • signaling low priority may be set to include a low priority indicator set.
  • step 9 and step 10 of FIG. 13 The operation of step 9 and step 10 of FIG. 13 is the same as that of step 9 and step 10 of FIG.
  • the above-described operation can also be applied to changes between systems when moving from EPS to 5GS.
  • an operation performed by the UE in the 5GS direction may be performed by the UE in the EPS direction
  • an operation performed by the UE in the EPS direction may be performed in the 5GS direction.
  • the operation of the AMF in the first disclosure may be performed by the MME
  • the operation of the MME may be performed by the AMF.
  • the operation of the SMF in the first disclosure may be performed by the PGW, and the operation of the PGW may be performed by the SMF.
  • the MME may predict / recognize the possibility of intersystem change based on information about the location of the UE. And, if the UE sends the ESM request message to the MME, i) the MME may not accept the ESM request message or provide a back-off timer in the ESM rejection message (1 initiation in intersystem change from 5GS to EPS). Example of operation of the first proposal). Alternatively, ii) the MME may provide the ESM reject message with an information to ignore the back-off timer value and the back-off timer (an example of operation of the first proposal of one disclosure in an intersystem change from 5GS to EPS). ). Alternatively, iii) the MME may provide the UE with a smaller value of the back-off timer value. Thereafter, if a change between systems is required due to the movement of the UE, the UE may transmit an SM request message to the AMF.
  • the UE of the second disclosure may be in the same situation as the UE of the first disclosure.
  • the UE registers first with 5GS, and may receive information indicating that interworking without N26 is supported (eg, an indication indicating that interworking is supported without N26 interface) from the network. Upon receiving the information or indication, the UE recognizes that the network supports interworking without an N26 interface.
  • the UE may support only single registration or dual registration but may use only one radio. (I.e. you can only receive services from one system at a time and not from both systems at the same time). However, the disclosure herein is not limited to UEs that can only use a single radio.
  • the UE creates one or more PDU sessions to receive the service.
  • the UE is subject to congestion control for a specific DNN (eg, DNN / APN # 1) from 5GS. That is, the UE receives and applies a back-off timer for DNN / APN # 1 from 5GS. At this time, while the back-off timer for DNN / APN # 1 is operated in the 5GS, the UE cannot perform an additional SM procedure for DNN / APN # 1.
  • a specific DNN eg, DNN / APN # 1
  • the UE receives and applies a back-off timer for DNN / APN # 1 from 5GS. At this time, while the back-off timer for DNN / APN # 1 is operated in the 5GS, the UE cannot perform an additional SM procedure for DNN / APN # 1.
  • the UE may move between 5GS to EPS by moving (e.g., by moving out of coverage) or by making a request for a particular capability (e.g., by voice call).
  • An inter-system change may be required.
  • the AMF may perform the operations described below at the time when the possibility of intersystem change is expected / recognized based on information about the location of the UE (eg, a registration area) before the intersystem change is required.
  • the prediction / recognition of the possibility of cross-system change from 5GS to EPS of the UE may be performed by the AMF by identifying the location of the UE (eg, TAI or cell ID) through a registration update procedure recently performed by the UE. Can be.
  • the UE may periodically provide the AMF with information about the current location in addition to the registration update procedure, through which the AMF may determine the location (eg, TAI or cell ID) of the UE to predict / recognize the possibility of cross-system change. Can be.
  • the location eg, TAI or cell ID
  • the AMF may deliver the SM request message transmitted by the UE to the SMF when the UE is expected / recognized that the possibility of the intersystem change from the 5GS to the EPS is expected in the DNN congestion situation.
  • the AMF may include information related to the prediction / recognition of the possibility of change between systems in the SM request message and transmit the information to the SMF.
  • the information related to the prediction / recognition of the possibility of intersystem change is information indicating that interworking support or DNN-based congestion control is not recommended / not required / not applicable (Interworking support or DNN based congestion control not recommended). / not desirable / not applicable, etc.)
  • SMFs receiving this indication / information operate as follows.
  • the operation of the first disclosure may be applied to all DNNs / APNs.
  • the operation of the first initiation may be applied only to a specific DNN / APN for a specific service.
  • the specific service may include, for example, a high priority service, an IMS voice call, an ultra reliable service, and the like.
  • the AMF transmits information related to the anticipation / cognition of the inter-system change possibility to the SMF. Then, the SMF does not perform / apply congestion control for the SM request message for a specific DNN (DNN / APN # 1, DNN / APN to which congestion control applies) (does not provide a back-off timer value).
  • the UE may send a SM request message for a specific DNN (DNN / APN # 1) to 5GS.
  • the AMF then sends an SM request message to the SMF with information related to the prediction / aware of the possibility of intersystem change.
  • the SMF rejects the SM request message transmitted by the UE and transmits a rejection message to the UE when the inter-system changeability is expected / recognized based on the information related to the prediction / recognition of the changeability between systems.
  • the rejection message includes a cause of rejection.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the SMF may not provide the UE with the SM (or MM) back-off timer value for the DNN (DNN / APN # 1) associated with the SM request message.
  • the SMF may accept an SM request message sent by the UE and send an accept message to the UE.
  • the UE will not run the back-off timer for congested DNNs (DNN / APN # 1) if a cross-system change is required and the cross-system change is performed with EPS. You may not.
  • the UE may piggyback the PDN connection request message for the congested DNN and transmit an attach request message to the EPS. Alternatively, the UE may transmit a separate PDN connection request message or an EPS bearer resource modification request message for a congested DNN to the EPS.
  • a UE requesting / recognizing that there is no possibility of intersystem change by the SMF may transmit an SM request message for a congested DNN to 5GS. Then, the SMF may reject the SM request message of the corresponding UE and transmit a rejection message to the UE.
  • the reject message may include a reject cause value and a back-off timer value.
  • the reject cause value may be # 22 congestion
  • the back-off timer value may be the SM back-off timer value (T3396) or the MM back-off timer value (T3346) for a specific DNN (DNN / APN # 1). Can be.
  • the UE drives the back-off timer based on the received back-off timer value and cannot send an SM request message for a specific DNN (DNN / APN # 1) to 5GS until the back-off timer expires. .
  • the UE piggybacks and transmits a PDN connection request message to an attach request message when connecting to a new CN (ie, EPC) to move a PDU session between CNs.
  • a new CN ie, EPC
  • the UE may not transmit a PDN connection request message.
  • the UE may transmit the PDN connection request message for the movement of the PDU session after the EMM-REGISTERED state after transmitting the attach request message.
  • the ESM request message may include information that the message relates to a change between systems.
  • the ESM request message may include information (information such as an indicator or a flag) indicating that the ESM request message is transmitted based on a change between systems (or moving in 5GC), rather than a general purpose.
  • the ESM request message may include information (information such as indicator, flag, etc.) indicating that the transmission of this message is transmitted for session transfer to a new system such as location reporting.
  • the information indicating that the 5GC is included in the Attach Request message may be used as information indicating a change between systems.
  • the UE may include only information regarding the change between systems in the ESM request message for the DNN / APN to which DNN / APN based congestion control is applied. Alternatively, the UE may include information indicating the change between systems in the ESM request message for every DNN / APN.
  • the MME will set a back-off timer value with an ESM rejection message if the APN / DNN associated with the ESM request is congested. May transmit to the UE.
  • the ESM request message sent by the UE meaning an ESM request message or an attach request message that piggybacks the ESM request message
  • Information to be sent for the purpose of, or ii) the request type of the ESM request message is "handover" and the ESM request message includes information indicating a change between ESM request systems.
  • the network eg, MME
  • the MME may send a Create Session Request message to the S-GW without applying congestion control to the ESM request message (the specific procedure is the attach procedure or PDN of the LTE standard). PDN Connectivity Request procedure).
  • the MME may include information indicating that the message is not a general request but a request based on a change between systems in the session creation request message and transmit the information to the S-GW.
  • the S-GW may process the session creation request message received from the MME and forward the request to the SMF + PGW-C.
  • the S-GW may also specify that this request is based on a change between systems.
  • the MME sends a response message to the UE.
  • the MME may optionally send a PDN Connectivity Accept-standalone or piggybacked on Attach Accept to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in the per APN / DNN ESM backoff timer (T3396) value and the cause value (# 22 congestion or due to congestion for interworking). At least one of)).
  • T3396 ESM backoff timer
  • the cause value # 22 congestion or due to congestion for interworking. At least one of
  • FIG. 14 is a signal flow diagram illustrating an example of a scheme according to a first proposal of the second disclosure.
  • step 4 of FIG. 14 Operations before step 4 of FIG. 14 are the same as steps 1 to 3 of FIGS. 9A and 9B.
  • the AMF may transmit the SM request message transmitted by the UE to the SMF when the UE expects / recognizes the possibility of the intersystem change from the 5GS to the EPS in the DNN congestion situation.
  • the AMF may transmit information to the SMF by including information related to the prediction / recognition of the possibility of change between systems in the SMF.
  • Information relating to the anticipation / awareness of inter-system changeability is defined as interworking support or DNN based congestion control not recommended / not desirable. / not applicable etc.).
  • SMF does not perform / apply congestion control on SM request messages for specific DNNs (DNN / APN # 1, DNN / APN to which congestion control applies) based on information related to the prediction / recognition of the possibility of intersystem change. Do not provide a back-off timer value.
  • the SMF rejects the SM request message transmitted by the UE and transmits a rejection message to the UE when the inter-system changeability is expected / recognized based on information related to the prediction / recognition of the changeability between systems.
  • the rejection message includes a cause of rejection.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion.
  • the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the SMF may not provide the UE with the SM (or MM) back-off timer value for the DNN (DNN / APN # 1) associated with the SM request message.
  • the SMF may accept an SM request message sent by the UE and send an accept message to the UE.
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • step 9 of FIG. 14 Operation of step 9 of FIG. 14 is the same as that of step 8 of FIG.
  • step 10 and step 11 of FIG. 14 is the same as that of step 9 and step 10 of FIG.
  • the second proposal of the second disclosure is described below.
  • the same content as that of the first proposal of the second disclosure will be omitted, and the description will be mainly focused on differences from the first proposal of the second disclosure.
  • the AMF transmits information related to the anticipation / cognition of the inter-system change possibility to the SMF. Then, the SMF may perform / apply congestion control on the SM request message for a specific DNN (DNN / APN # 1, DNN / APN to which congestion control is applied) as described below.
  • the UE may send a PDU session establishment / modification / release request message (hereinafter referred to as SM request message) for a specific DNN (DNN / APN # 1) to 5GS.
  • SM request message a PDU session establishment / modification / release request message
  • the SMF rejects the SM request message transmitted by the UE and transmits a rejection message to the UE.
  • the rejection message includes information about overriding the SM back-off timer value (or MM back-off timer value) for a specific DNN (DNN / APN # 1) and the back-off timer when a change between systems is required. (overriding information or overriding indication).
  • the reject message may also include a cause value (cause value).
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion.
  • the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the UE Even when the UE is running a back-off timer based on the received back-off timer value, if a change is required between systems due to movement, the UE is informed to ignore the back-off timer if a change between systems is required. Based on this, the back-off timer may be ignored and the attach request message may be sent to the EPS. Specifically, the UE ignores the SM back-off timer for a specific DNN (DNN / APN # 1, congested DNN / APN), and requests a PDN connection for a specific DNN (DNN / APN # 1) in an attach request message. The message can be piggybacked and sent to the MME. Alternatively, in case of EPC and UE supporting attach without PDN connection, PDN connection request message is not transmitted, but PDN connection request message is transmitted for moving PDU session after EMM-REGISTERED state after transmitting attach request message. It may be.
  • DNN / APN # 1 congested DNN / APN
  • the UE may not set MS / UE to low priority NAS signaling in an attach request message or PDN connection request message for a specific DNN (DNN / APN # 1) (MS / UE is not configured for NAS).
  • signaling low priority may include a low priority indicator set.
  • the UE may transmit an attach request message or a PDN connection request message for a specific DNN (DNN / APN # 1).
  • the network (MME) then sends a DNN / DNN for an attach request message set to “MS / UE is not set to low priority NAS signaling” or PDN connection request message for a specific DNN (DNN / APN # 1).
  • PDN connection request message can be processed without applying APN-based congestion control.
  • the ESM request message may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (information such as an indicator or a flag) indicating that the ESM request message is transmitted based on a change between systems (or moving in 5GC), rather than a general purpose.
  • the ESM request message may include information (information such as indicator, flag, etc.) indicating that the transmission of this message is transmitted for session transfer to a new system such as location reporting.
  • the information indicating that the 5GC is included in the Attach Request message may be used as information indicating a change between systems.
  • the UE may include only information regarding the change between systems in the ESM request message for the DNN / APN to which DNN / APN based congestion control is applied. Alternatively, the UE may include information indicating the change between systems in the ESM request message for every DNN / APN.
  • the MME will set a back-off timer value with an ESM rejection message if the APN / DNN associated with the ESM request is congested. May transmit to the UE.
  • the ESM request message sent by the UE meaning an ESM request message or an attach request message that piggybacks the ESM request message
  • Information to be sent for the purpose of, or ii) the request type of the ESM request message is "handover" and the ESM request message includes information indicating a change between ESM request systems.
  • the network eg, MME
  • the MME may send a Create Session Request message to the S-GW without applying congestion control to the ESM request message (the specific procedure is the attach procedure or PDN of the LTE standard). PDN Connectivity Request procedure).
  • the MME may include information indicating that the message is not a general request but a request based on a change between systems in the session creation request message and transmit the information to the S-GW.
  • the S-GW may process the session creation request message received from the MME and forward the request to the SMF + PGW-C.
  • the S-GW may also specify that this request is based on a change between systems.
  • the MME sends a response message to the UE.
  • the MME may optionally send a PDN Connectivity Accept-standalone or piggybacked on Attach Accept to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in the per APN / DNN ESM backoff timer (T3396) value and the cause value (# 22 congestion or due to congestion for interworking). At least one of)).
  • T3396 ESM backoff timer
  • the cause value # 22 congestion or due to congestion for interworking. At least one of
  • a UE requesting / recognizing that there is no possibility of intersystem change by AMF may transmit a SM request message for congested DNN to 5GS.
  • the AMF may not transmit information related to the prediction / aware of the possibility of intersystem change to the SMF.
  • the AMF may send information to the SMF that there is no possibility of cross-system change.
  • the SMF may reject the SM request message of the corresponding UE and transmit a rejection message to the UE.
  • the reject message may include a reject cause value and a back-off timer value.
  • the reject cause value may be # 22 congestion
  • the back-off timer value may be the SM back-off timer value (T3396) or the MM back-off timer value (T3346) for a specific DNN (DNN / APN # 1). Can be.
  • the UE drives the back-off timer based on the received back-off timer value and cannot send an SM request message for a specific DNN (DNN / APN # 1) to 5GS until the back-off timer expires. .
  • 15 is a signal flow diagram illustrating an example of a scheme according to a second proposal of the second disclosure.
  • FIGS. 9A, 9B, 11, 12, 13, and 14 Description of the same contents as those of FIGS. 9A, 9B, 11, 12, 13, and 14 will be omitted, and FIG. 15 will be described based on differences.
  • step 4 of FIG. 15 Operation before step 4 of FIG. 15 is the same as steps 1 to 3 of FIGS. 9A and 9B.
  • step 6 of FIG. 15 Operation of step 6 of FIG. 15 is the same as that of step 6 of FIG.
  • SMF performs / applies congestion control on SM request messages for specific DNNs (DNN / APN # 1, DNN / APN to which congestion control applies) based on information related to the prediction / recognition of the possibility of intersystem change. .
  • the SMF rejects the SM request message transmitted by the UE and transmits a rejection message to the UE.
  • the rejection message includes information about overriding the SM back-off timer value (or MM back-off timer value) for a specific DNN (DNN / APN # 1) and the back-off timer when a change between systems is required. (overriding information or overriding indication).
  • the reject message may also include a cause value (cause value).
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • the UE may not change the back-off timer if the change between systems is required.
  • the back-off timer can be ignored based on the information to ignore.
  • the UE may transmit an attach request message to the EPS. Specifically, the UE ignores the SM back-off timer for a specific DNN (DNN / APN # 1, congested DNN / APN), and requests a PDN connection for a specific DNN (DNN / APN # 1) in an attach request message.
  • the message can be piggybacked and sent to the MME.
  • PDN connection request message in case of EPC and UE supporting attach without PDN connection, PDN connection request message is not transmitted, but PDN connection request message is transmitted for moving PDU session after EMM-REGISTERED state after transmitting attach request message. It may be.
  • the ESM request message (PDN connection request message piggybacked in the attach request message or PDN connection request message transmitted alone) may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (corresponding to “interworking change” in FIG. 15) indicating that the ESM request message is transmitted based on a change between systems.
  • the ESM request message may include information (corresponding to “session transfer” in FIG.
  • the UE may not set the MS / UE to low priority NAS signaling in the attach request message or PDN connection request message for a specific DNN (DNN / APN # 1) (MS / UE is not configured for NAS).
  • signaling low priority may be set to include a low priority indicator set.
  • steps 10 and 11 of FIG. 15 are the same as steps 9 and 10 of FIG.
  • the third proposal of the second disclosure is described below.
  • descriptions of the same contents as the first proposal or the second proposal of the second disclosure will be omitted, and the description will be mainly focused on differences between the first proposal and the second proposal of the second disclosure.
  • the AMF transmits information related to the anticipation / cognition of the inter-system change possibility to the SMF. Then, the SMF may perform / apply congestion control on the SM request message for a specific DNN (DNN / APN # 1, DNN / APN to which congestion control is applied) as described below.
  • the UE may send an SM request message for a specific DNN (DNN / APN # 1) to 5GS.
  • the SMF may reject the SM request message transmitted by the UE and transmit a rejection message to the UE.
  • the reject message may include a reject cause value.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the reject message may include an SM back-off timer value for a specific DNN (DNN / APN # 1).
  • the SMF may provide a SM back-off timer (T3396) value provided to a UE that is expected / aware of intersystem changeability, and a typical SM back-off timer value provided to a UE that is expected / aware of non-system changeability. It can be set to have a smaller value. If cross-system change is required with EPS, the back-off timer driven based on the smaller value of the back-off timer expires faster than the back-off timer of the UE without the possibility of cross-system change. Then, the UE requiring change between systems can quickly send an attach request message, a PDN connection request message, or an EPS bearer resource modification message for a specific DNN (DNN / APN # 1, congested DNN / APN).
  • DNN DNN / APN # 1
  • congested DNN / APN congested DNN / APN
  • the SMF may provide a new back-off timer different from the back-off timer provided to the UE that is expected / perceived that there is no cross-system changeability to the UE that is expected / recognized that the cross-system changeability is possible.
  • the back-off timer value used for the new back-off timer T35xy different from the SM back-off timer T3396 (or MM back-off timer T3346) is included in the reject message and provided to the UE. can do.
  • the new back-off timer T35xy may have a timer value smaller than a typical SM back-off timer T3396 (or MM back-off timer T3346).
  • the ESM request message may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (information such as an indicator or a flag) indicating that the ESM request message is transmitted based on a change between systems (or moving in 5GC), rather than a general purpose.
  • the ESM request message may include information (information such as indicator, flag, etc.) indicating that the transmission of this message is transmitted for session transfer to a new system such as location reporting.
  • the information indicating that the 5GC is included in the Attach Request message may be used as information indicating a change between systems.
  • the UE may include only information regarding the change between systems in the ESM request message for the DNN / APN to which DNN / APN based congestion control is applied. Alternatively, the UE may include information indicating the change between systems in the ESM request message for every DNN / APN.
  • the MME will set a back-off timer value with an ESM rejection message if the APN / DNN associated with the ESM request is congested. May transmit to the UE.
  • the ESM request message sent by the UE meaning an ESM request message or an attach request message that piggybacks the ESM request message
  • Information to be sent for the purpose of, or ii) the request type of the ESM request message is "handover" and the ESM request message includes information indicating a change between ESM request systems.
  • the network eg, MME
  • the MME may send a Create Session Request message to the S-GW without applying congestion control to the ESM request message (the specific procedure is the attach procedure or PDN of the LTE standard). PDN Connectivity Request procedure).
  • the MME may include information indicating that the message is not a general request but a request based on a change between systems in the session creation request message and transmit the information to the S-GW.
  • the S-GW may process the session creation request message received from the MME and forward the request to the SMF + PGW-C.
  • the S-GW may also specify that this request is based on a change between systems.
  • the MME sends a response message to the UE.
  • the MME may optionally send a PDN Connectivity Accept-standalone or piggybacked on Attach Accept to the UE.
  • the MME may transmit the PDN connection accept message to the UE in the form of a general accept message.
  • the MME may include information about congestion control for the corresponding APN / DNN and transmit a PDN connection accept message to the UE. For example, information about congestion control can be found in the per APN / DNN ESM backoff timer (T3396) value and the cause value (# 22 congestion or due to congestion for interworking). At least one of)).
  • T3396 ESM backoff timer
  • the cause value # 22 congestion or due to congestion for interworking. At least one of
  • a UE requesting / recognizing that there is no possibility of intersystem change by AMF may transmit a SM request message for congested DNN to 5GS.
  • the AMF may not transmit information related to the prediction / aware of the possibility of intersystem change to the SMF.
  • the AMF may send information to the SMF that there is no possibility of cross-system change.
  • the SMF may reject the SM request message of the corresponding UE and transmit a rejection message to the UE.
  • the reject message may include a reject cause value and a back-off timer value.
  • the reject cause value may be # 22 congestion
  • the back-off timer value may be the SM back-off timer value (T3396) or the MM back-off timer value (T3346) for a specific DNN (DNN / APN # 1). Can be.
  • the UE drives the back-off timer based on the received back-off timer value and cannot send an SM request message for a specific DNN (DNN / APN # 1) to 5GS until the back-off timer expires. .
  • 16 is a signal flow diagram illustrating an example of a scheme according to a third proposal of the second disclosure.
  • step 4 of FIG. 16 Operations before step 4 of FIG. 16 are the same as steps 1 to 3 of FIGS. 9A and 9B.
  • step 6 of FIG. 16 Operation of step 6 of FIG. 16 is the same as that of step 6 of FIG.
  • SMF performs / applies congestion control on SM request messages for specific DNNs (DNN / APN # 1, DNN / APN to which congestion control applies) based on information related to the prediction / recognition of the possibility of intersystem change. .
  • the SMF may reject the SM request message transmitted by the UE and transmit a rejection message to the UE.
  • the reject message may include a reject cause value.
  • the reject cause value may be a 5GMM cause value, for example, # 22 congestion. Alternatively, the reject cause value may be a new cause value (due to congestion for interworking, etc.).
  • the reject message may include an SM back-off timer value for a specific DNN (DNN / APN # 1).
  • the SMF may provide a SM back-off timer (T3396) value provided to a UE that is expected / aware of intersystem changeability, and a typical SM back-off timer value provided to a UE that is expected / aware of non-system changeability. It can be set to have a smaller value.
  • T3396 SM back-off timer
  • the SMF may provide a new back-off timer different from the back-off timer provided to the UE that is expected / perceived that there is no cross-system changeability to the UE that is expected / recognized that the cross-system changeability is possible.
  • the back-off timer value used for the new back-off timer T35xy different from the SM back-off timer T3396 (or MM back-off timer T3346) is included in the reject message and provided to the UE. can do.
  • the new back-off timer T35xy may have a timer value smaller than a typical SM back-off timer T3396 (or MM back-off timer T3346).
  • the UE moves (eg, mobility) from 5GS to EPS for some reason.
  • the UE may be out of coverage of 5GS due to movement.
  • SM back-off timer T3396
  • new back-off timer T35xy
  • the -off timer expires earlier than the back-off timer of the UE which has no possibility of intersystem change. If a change between systems is required due to a cause of movement or the like, and the smaller back-off timer value expires, the UE may send an attach request message to the EPS to move the PDU session from 5GS to EPS.
  • the UE ignores the SM back-off timer for a specific DNN (DNN / APN # 1, congested DNN / APN), and requests a PDN connection for a specific DNN (DNN / APN # 1) in an attach request message.
  • the message can be piggybacked and sent to the MME.
  • PDN connection request message is not transmitted, but PDN connection request message is transmitted for moving PDU session after EMM-REGISTERED state after transmitting attach request message. It may be.
  • the ESM request message (PDN connection request message piggybacked in the attach request message or PDN connection request message transmitted alone) may include information indicating that the message is related to a change between systems.
  • the ESM request message may include information (corresponding to “interworking change” in FIG. 16) indicating that the ESM request message is transmitted based on a change between systems.
  • the ESM request message may include information (corresponding to “session transfer” in FIG. 16) indicating that the transmission of this message is sent for a session transfer to a new system such as location reporting.
  • the UE may not set the MS / UE to low priority NAS signaling in the attach request message or PDN connection request message for a specific DNN (DNN / APN # 1) (MS / UE is not configured for NAS).
  • signaling low priority may be set to include a low priority indicator set.
  • the above-described operation can also be applied to changes between systems when moving from EPS to 5GS.
  • an operation performed by the UE in the 5GS direction may be performed by the UE in the EPS direction
  • an operation performed by the UE in the EPS direction may be performed in the 5GS direction.
  • the operation of the AMF in the second disclosure may be performed by the MME
  • the operation of the MME may be performed by the AMF.
  • the operation of the SMF in the second disclosure may be performed by the PGW, and the operation of the PGW may be performed by the SMF.
  • the MME may predict / recognize the possibility of intersystem change based on information about the location of the UE.
  • the MME may include information related to the prediction / recognition of the possibility of change between systems in the ESM request message and transmit the information to the PGW. If the UE sends an ESM request message to the MME, i) the PGW may not accept the ESM request message or provide a back-off timer in the ESM rejection message (a second initiation in the intersystem change from 5GS to EPS). 1 example of the operation of the proposal).
  • the PGW may provide the ESM rejection message with an information to ignore the back-off timer value and the back-off timer (see the operation of the first proposal of the second disclosure in an intersystem change from 5GS to EPS). example).
  • the PGW may provide the UE with a smaller value of the back-off timer value (example of operation of the third proposal of the second disclosure in an intersystem change from 5GS to EPS). Thereafter, if a change between systems is required due to the movement of the UE, the UE may transmit an SM request message to the AMF.
  • the UE of the third initiation may be in the same situation as the UE of the second initiation or the first initiation.
  • the UE registers first with 5GS, and may receive information indicating that interworking without N26 is supported (eg, an indication indicating that interworking is supported without N26 interface) from the network. Upon receiving the information or indication, the UE recognizes that the network supports interworking without an N26 interface.
  • the UE may support only single registration or dual registration but may use only one radio. (I.e. you can only receive services from one system at a time and not from both systems at the same time). However, the disclosure herein is not limited to UEs that can only use a single radio.
  • the UE creates one or more PDU sessions to receive the service.
  • the UE may move between 5GS to EPS by moving (e.g., by moving out of coverage) or by making a request for a particular capability (e.g., by voice call). An inter-system change may be required.
  • the UE may disable the N1 mode capability. Specifically, in a state where the UE is accessed 5GS based on the N1 mode, the UE may deactivate the N1 mode capability when performing a system-to-system change with the EPS.
  • the N1 mode is an operating mode that allows the UE to access the 5G CN through the 5G access network. If the UE deactivates the N1 mode capability, the UE may be provided with operations and services related to communication only in the E-UTRA.
  • the UE After deactivating the N1 mode capability, the UE describes the first initiation (including the first proposal, the second proposal, and the third proposal) or the second initiation (including the first proposal, the second proposal, and the third proposal).
  • the operation of the UE can be performed.
  • the first proposal item (2) of the first disclosure, the second proposal item (2) of the first disclosure, and the third proposal item (2) of the first disclosure After the UE deactivates the N1 mode capability, the first proposal item (2) of the first disclosure, the second proposal item (2) of the first disclosure, and the third proposal item (2) of the first disclosure , The first proposal item (2) of the second disclosure, the first proposal item (2) of the second disclosure, or the first proposal item (2) of the second disclosure may be performed.
  • the UE may run a re-enabling timer after deactivating the N1 mode capability.
  • the UE may not perform PLMN selection.
  • the UE may perform PLMN selection without considering the N1 mode (ie, not considering 5GS), considering E-UTRA, UTRAN, or GERAN and the like.
  • the UE may reactivate the N1 mode capability. Then, the UE may perform PLMN selection in consideration of both the N1 mode and the E-UTRA RAT based on the N1 mode capability.
  • the UE may reactivate the N1 mode capability when the UE performs a specific 5GS service related to 5GS (such as ultra-low latency service). Then, the UE may perform PLMN selection in consideration of both the N1 mode and the E-UTRA RAT based on the N1 mode capability. Alternatively, the UE may perform PLMN selection by considering only 5GS after reactivating the N1 mode capability.
  • a cross-system change from EPS to 5GS may be required by the need for movement or specific capabilities. If the UE moves to the N1 mode in the E-UTRA RAT, the UE may deactivate the E-UTRA capability. If the UE deactivates the E-UTRA capability, the UE may be provided with operations and services related to communication based on the 5GS N1 mode.
  • the UE After deactivating the E-UTRA capability, the UE, at the first initiation (including the first proposal, the second proposal, and the third proposal) or the second initiation (including the first proposal, the second proposal, and the third proposal)
  • the operation of the described UE may be performed.
  • the first proposal item (2) of the first disclosure, the second proposal item (2) of the first disclosure, and the third proposal item (2) of the first disclosure After the UE deactivates the N1 mode capability, the first proposal item (2) of the first disclosure, the second proposal item (2) of the first disclosure, and the third proposal item (2) of the first disclosure , The first proposal item (2) of the second disclosure, the first proposal item (2) of the second disclosure, or the first proposal item (2) of the second disclosure may be performed.
  • the UE may run a re-activation timer after deactivating the E-UTRA capability.
  • the UE may not perform PLMN selection while the re-activation timer is running.
  • the UE may perform PLMN selection by considering only the N1 mode without considering the E-UTRA.
  • the UE may perform PLMN selection in consideration of the N1 mode, UTRAN or GERAN without considering E-UTRA.
  • the UE may reactivate the E-UTRA capability. Then, the UE may perform PLMN selection in consideration of both the N1 mode and the E-UTRA RAT based on the E-UTRA capability.
  • the E-UTRA capability may be reactivated. Then, the UE may perform PLMN selection in consideration of both the N1 mode and the E-UTRA RAT based on the E-UTRA capability. Alternatively, the UE may perform PLMN selection by considering only the E-UTRAN after reactivating the E-UTRA capability.
  • IMS voice VoIP
  • Information for performing N1 mode capability deactivation and a re-activation timer value related to N1 mode capability deactivation may be preset and provided to the UE from the 5GS CN.
  • the information for performing the E-UTRA capability deactivation and the re-activation timer value related to the E-UTRA capability deactivation may be preset and provided to the UE from the EPS CN.
  • the above information and timer values may be, for example, a UE Route Selection Policy (URSP), a UE configuration update, a Management Object (MO) via OMA-DM or a Universal Subscriber Identity Module. ) May be provided to the UE in a configuration included in the.
  • the UE may store this setting and perform the operation described in the third disclosure based on the stored setting.
  • FIG. 17 illustrates a wireless communication device in accordance with the disclosure herein.
  • a wireless communication system may include a first device 100 and a second device 200, and the first device 100 and the second device 200 may implement the disclosure herein. have.
  • the first device 100 and the second device 200 are wireless communication devices that perform wireless communication.
  • the first device 100 includes a base station, a network node, a transmission terminal, a reception 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 (Artificial Intelligence) Modules, Robots, Augmented Reality Devices, Virtual Reality Devices, Mixed Reality Devices, Hologram Devices, Public Safety Devices, MTC Devices, IoT Devices, Medical Devices, Pins It may be a tech device (or financial device), a security device, a climate / environment device, a device related to 5G service, or another device related to the fourth industrial revolution field.
  • UAV Artificial Intelligence
  • the second device 200 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 (Artificial Intelligence) Modules, Robots, Augmented Reality Devices, Virtual Reality Devices, Mixed Reality Devices, Hologram Devices, Public Safety Devices, MTC Devices, IoT Devices, Medical Devices, Pins It may be a tech device (or financial device), a security device, a climate / environment device, a device related to 5G service, or another device related to the fourth industrial revolution field.
  • UAV Artificial Intelligence
  • the first device 100 may be a UE described in the disclosure herein.
  • the second device 200 may be a network node such as AMF, MME, SMF, or P-GW (PGW-C or PGW-U) described in the present disclosure.
  • the terminal may be a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, a slate PC, a tablet. It may include a tablet PC, an ultrabook, a wearable device (eg, a smartwatch, a glass glass, a head mounted display), and the like.
  • the HMD may be a display device worn on the head.
  • the HMD can be used to implement VR, AR or MR.
  • a drone may be a vehicle in which humans fly by radio control signals.
  • the VR device may include a device that implements an object or a background of a virtual world.
  • the AR device may include a device that connects and implements an object or a background of the virtual world to an object or a background of the real world.
  • the MR device may include a device that fuses and implements an object or a background of the virtual world to an object or a background of the real world.
  • the hologram device may include a device that records and reproduces stereoscopic information to realize a 360 degree stereoscopic image by utilizing interference of light generated by two laser lights, called holography, to meet each other.
  • the public safety device may include an image relay device or an image device wearable on a human body of a user.
  • 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 bulb, a door lock or various sensors.
  • the 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, alleviating or correcting an injury or disorder.
  • a medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or function.
  • the medical device may be a device used for controlling pregnancy.
  • the medical device may include a medical device, a surgical device, an (in vitro) diagnostic device, a hearing aid or a surgical device, and the like.
  • the security device may be a device installed to prevent a risk that may occur and to maintain safety.
  • the security device may be a camera, a CCTV, a recorder or a 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).
  • the climate / environmental device may include a device for monitoring or predicting the climate / environment.
  • the first device 100 may include at least one or more processors, such as the processor 120, at least one or more memories, such as the memory 130, and at least one or more transceivers, such as the transceiver 110.
  • the processor 120 may perform the functions, procedures, and / or methods described above.
  • the processor 120 may perform one or more protocols.
  • the processor 120 may perform one or more layers of a radio interface protocol.
  • the memory 130 may be connected to the processor 120 and store various types of information and / or instructions.
  • the transceiver 110 may be connected to the processor 120 and controlled to transmit and receive a wireless signal.
  • the second device 200 may include at least one processor such as the processor 220, at least one memory device such as the memory 230, and at least one transceiver such as the transceiver 210.
  • the processor 220 may perform the functions, procedures, and / or methods described above.
  • the processor 220 may implement one or more protocols.
  • the processor 220 may implement one or more layers of a radio interface protocol.
  • the memory 230 may be connected to the processor 220 and store various types of information and / or instructions.
  • the transceiver 210 may be connected to the processor 220 and controlled to transmit and receive a wireless signal.
  • the memory 130 and / or the memory 230 may be connected inside or outside the processor 120 and / or the processor 220, respectively, and may be connected to other processors through various technologies such as a wired or wireless connection. It may also be connected to.
  • the first device 100 and / or the second device 200 may have one or more antennas.
  • antenna 9014 and / or antenna 9024 may be configured to transmit and receive wireless signals.
  • the illustrated processor 120, 220, memory 130, 230, and transceiver 110, 210 may each be implemented as separate chips, or at least two blocks / functions may be implemented through one chip.
  • the transceivers 110 and 210 include a transmitter and a receiver. When a specific operation is performed, only one of the transmitter and the receiver may be performed, or both the transmitter and the receiver may be performed.
  • the transceivers 110 and 210 may include one or more antennas for transmitting and / or receiving wireless signals.
  • the transceivers 110 and 210 may include an amplifier for amplifying a received signal and / or a transmitted signal and a bandpass filter for transmission on a specific frequency band.
  • the processors 120 and 220 may implement the functions, processes, and / or methods proposed herein.
  • the processors 120 and 220 may include an encoder and a decoder.
  • the processors 120 and 230 may perform operations according to the above description.
  • Such processors 120 and 220 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, data processing devices, and / or converters to convert baseband signals and wireless signals to and from each other.
  • ASICs application-specific integrated circuits
  • the memories 130 and 230 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media and / or other storage devices.
  • ROM read-only memory
  • RAM random access memory
  • flash memory memory cards, storage media and / or other storage devices.
  • FIG. 18 is a detailed block diagram of a transceiver of the wireless device or network node shown in FIG. 17.
  • the transceiver 110 includes a transmitter 111 and a receiver 112.
  • the transmitter 111 includes a discrete fourier transform (DFT) unit 1111, a subcarrier mapper 1112, an IFFT unit 1113, a CP insertion unit 1144, and a wireless transmitter 1115.
  • the transmitter 111 may further include a modulator.
  • the apparatus may further include a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown) and a layer permutator (not shown). This may be disposed before the DFT unit 1111.
  • the transmitter 111 first passes the information through the DFT 1111 before mapping a signal to a subcarrier. After subcarrier mapping of the signal spread (or precoded in the same sense) by the DFT unit 1111 through the subcarrier mapper 1112, the inverse fast fourier transform (IFFT) unit 1113 is further passed on the time axis. Make it a signal.
  • IFFT inverse fast fourier transform
  • the DFT unit 1111 outputs complex symbols (complex-valued symbols) by performing a DFT on the input symbols. For example, when Ntx symbols are input (where Ntx is a natural number), the DFT size is Ntx.
  • the DFT unit 1111 may be called a transform precoder.
  • the subcarrier mapper 1112 maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission.
  • the subcarrier mapper 1112 may be called a resource element mapper.
  • the IFFT unit 1113 performs an IFFT on the input symbol and outputs a baseband signal for data, which is a time domain signal.
  • the CP inserter 1114 copies a part of the rear part of the baseband signal for data and inserts it in the front part of the baseband signal for data. Interpolation of inter-symbol interference (ISI) and inter-carrier interference (ICI) can be prevented through CP insertion to maintain orthogonality even in multipath channels.
  • ISI inter-symbol interference
  • ICI inter-carrier interference
  • the receiver 112 includes a wireless receiver 1121, a CP remover 1122, an FFT unit 1123, an equalizer 1124, and the like.
  • the radio receiver 1121, the CP remover 1122, and the FFT unit 1123 of the receiver 112 include a radio transmitter 1115, a CP insertion unit 1114, and an IFF unit 1113 at the transmitter 111. Performs the reverse function of The receiver 112 may further include a demodulator.
  • the processor may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices.
  • the memory may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage device.
  • the RF unit may include a baseband circuit for processing a radio signal.
  • the above-described technique may be implemented as a module (process, function, etc.) for performing the above-described function.
  • the module may be stored in memory and executed by a processor.
  • the memory may be internal or external to the processor and may be coupled to the processor by a variety of known means.
  • an always-on PDU session for the low-latency URLLC may be used for artificial intelligence, robot, autonomous driving, extended reality, and the like among the 5G scenarios below.
  • the 5G usage scenario shown in FIG. 19 is merely exemplary, and the technical features of the present invention may be applied to other 5G usage scenarios not shown in FIG. 19.
  • enhanced mobile broadb eMBB
  • massive machine type communication mMTC
  • high reliability ultra-reliable and low latency communications
  • URLLC ultra-reliable and low latency communications
  • KPI key performance indicator
  • eMBB focuses on improving data rate, latency, user density, overall capacity and coverage of mobile broadband access.
  • eMBB aims at throughput of around 10Gbps.
  • 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 may not see dedicated voice services for the first time in the 5G era.
  • voice is expected to be treated as an application program simply using the data connection provided by the communication system.
  • the main reason for the increased traffic volume is the increase in content size and the increase in the number of applications requiring high data rates.
  • Streaming services (audio and video), interactive video, and mobile Internet connections will become more popular as more devices connect to the Internet.
  • Cloud storage and applications are growing rapidly 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 tasks in the cloud and requires much lower end-to-end delays to maintain a good user experience when tactile interfaces are used.
  • cloud gaming and video streaming is another key element that requires the enhancement of mobile broadband capabilities.
  • Entertainment is essential in 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 very low latency and instantaneous amount of data.
  • the mMTC is designed to enable communication between a large number of low-cost devices powered by batteries and to support applications such as smart metering, logistics, field and body sensors.
  • mMTC targets 10 years of battery and / or about 1 million devices per square kilometer.
  • the mMTC enables seamless sensor connectivity in all areas, creating sensor networks and is one of the most anticipated 5G use cases. Potentially, 2020 IoT devices are expected to reach 20 billion. Smart networks using industrial IoT are one of the areas where 5G plays a major role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.
  • URLLC enables devices and machines to communicate very reliably and with very low latency and high availability, enabling mission-critical applications such as autonomous vehicle-to-vehicle communications and control, industrial control, factory automation, telesurgery and healthcare, smart grid and public Ideal for safety applications.
  • URLLC aims for a delay of around 1ms.
  • URLLC includes new services that will transform the industry through highly reliable / ultra-low latency links such as remote control of key infrastructure and autonomous vehicles. The level of reliability and latency is 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 of providing streams that are rated at hundreds of megabits per second to gigabits per second. This high speed may be required to deliver TVs at resolutions of 4K or higher (6K, 8K and higher) as well as virtual reality (VR) and augmented reality (AR).
  • VR and AR applications include nearly immersive sports events. Certain applications may require special network settings. For example, in a VR game, the game company may need to integrate the core server with the network operator's edge network server to minimize latency.
  • Automotive is expected to be an important new driver for 5G, with many uses for mobile communications to vehicles. For example, entertainment for passengers demands both high capacity and high mobile broadband at the same time. This is because future users continue to expect high quality connections regardless of their location and speed.
  • Another use of the automotive sector is augmented reality dashboards.
  • the augmented reality contrast board allows the driver to identify objects in the dark above what they are looking through through the front window.
  • the augmented reality dashboard superimposes information that tells the driver about the distance and movement of the object.
  • wireless modules enable communication between vehicles, the exchange of information between the vehicle and the supporting infrastructure, and the exchange of information between the vehicle and other connected devices (eg, devices carried by pedestrians).
  • the safety system guides alternative courses of action to help drivers drive safer, reducing the risk of an accident.
  • the next step will be a remote controlled vehicle or an autonomous vehicle.
  • This requires very reliable and very fast communication between different autonomous vehicles and / or between cars and infrastructure.
  • autonomous vehicles will perform all driving activities and allow drivers to focus on traffic anomalies that the vehicle itself cannot identify.
  • the technical requirements of autonomous vehicles require ultra-low latency and ultrafast reliability to increase traffic safety to an unachievable level.
  • Smart cities and smart homes referred to as smart societies, will be embedded in high-density wireless sensor networks as an example of smart networks.
  • the distributed network of intelligent sensors will identify the conditions for cost and energy efficient maintenance of the city or home. Similar settings can be made for each hypothesis.
  • Temperature sensors, window and heating controllers, burglar alarms and appliances 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.
  • Smart grids interconnect these sensors using digital information and communication technologies to gather information and act accordingly. This information can include the behavior of suppliers and consumers, allowing smart grids to improve the distribution of fuels such as electricity in efficiency, reliability, economics, sustainability of production, and in an automated manner. 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, providing clinical care at a distance. This can help reduce barriers to distance and improve access to health services that are not consistently available in remote rural areas. It is also used to save lives in critical care and emergencies.
  • Mobile communication based wireless sensor networks may 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. Thus, the possibility of replacing the cable with a reconfigurable wireless link 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 in 5G.
  • Logistics and freight tracking is an important use case for mobile communications that enables the tracking of inventory and packages from anywhere using a location-based information system.
  • the use of logistics and freight tracking typically requires low data rates but requires wide range and reliable location information.
  • Machine learning refers to the field of researching methodologies to define and solve various problems dealt with in the field of artificial intelligence. do.
  • Machine learning is defined as an algorithm that improves the performance of a task through a consistent experience with a task.
  • ANN Artificial Neural Network
  • the artificial neural network may be defined by a connection pattern between neurons of different layers, a learning process of updating model parameters, and an activation function generating an output value.
  • the artificial neural network may include an input layer, an output layer, and optionally one or more hidden layers. Each layer contains one or more neurons, and the artificial neural network may include synapses that connect neurons to neurons. In an artificial neural network, each neuron may output a function value of an active function for input signals, weights, and deflections input through a synapse.
  • the model parameter refers to a parameter determined through learning and includes weights of synaptic connections and deflection of neurons.
  • the hyperparameter means a parameter to be set before learning in the machine learning algorithm, and includes a learning rate, the number of iterations, a mini batch size, an initialization function, and the like.
  • the purpose of learning artificial neural networks can be seen as determining model parameters that minimize the loss function.
  • the loss function can be used as an index for determining an optimal model parameter in the learning process of an artificial neural network.
  • Machine learning can be categorized into supervised learning, unsupervised learning, and reinforcement learning.
  • Supervised learning refers to a method of learning artificial neural networks with a given label for training data, and a label indicates a correct answer (or result value) that the artificial neural network must infer when the training data is input to the artificial neural network.
  • Unsupervised learning may refer to a method of training artificial neural networks in a state where a label for training data is not given.
  • Reinforcement learning can mean a learning method that allows an agent defined in an environment to learn to choose an action or sequence of actions that maximizes cumulative reward in each state.
  • Machine learning which is implemented as a deep neural network (DNN) including a plurality of hidden layers among artificial neural networks, is called deep learning (Deep Learning), which is part of machine learning.
  • DNN deep neural network
  • Deep Learning Deep Learning
  • machine learning is used to mean deep learning.
  • a robot can mean a machine that automatically handles or operates a given task by its own ability.
  • a robot having a function of recognizing the environment, judging itself, and performing an operation may be referred to as an intelligent robot.
  • Robots can be classified into industrial, medical, household, military, etc. according to the purpose or field of use.
  • the robot may include 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, and can travel on the ground or fly in the air through the driving unit.
  • Autonomous driving means a technology that drives by itself, and an autonomous vehicle means a vehicle that runs without a user's manipulation or with minimal manipulation of a user.
  • the technology of maintaining a driving lane the technology of automatically adjusting speed such as adaptive cruise control, the technology of automatically driving along a predetermined route, the technology of automatically setting a route when a destination is set, etc. All of these may 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 together, and an electric vehicle having only an electric motor, and may include not only automobiles but also trains and motorcycles.
  • the autonomous vehicle may be viewed as a robot having an autonomous driving function.
  • Extended reality collectively refers to virtual reality (VR), augmented reality (AR), and mixed reality (MR).
  • VR technology provides real world objects and backgrounds only in CG images
  • AR technology provides virtual CG images on real objects images
  • MR technology mixes and combines virtual objects in the real world.
  • Graphic technology
  • MR technology is similar to AR technology in that it shows both real and virtual objects.
  • virtual objects are used as complementary objects to real objects, whereas in MR technology, virtual objects and real objects are used in an equivalent nature.
  • HMD Head-Mount Display
  • HUD Head-Up Display
  • mobile phone tablet PC, laptop, desktop, TV, digital signage, etc. It can be called.
  • FIG 20 shows an AI system 1 according to an embodiment of the present invention.
  • the AI system 1 may include 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.
  • This cloud network 10 is connected.
  • 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 AI devices 100a to 100e may be UEs or network nodes such as AMF, MME, SMF, P-GW (PGW-C or PGW-U) described in the present disclosure.
  • the cloud network 10 may refer to a network that forms part of the cloud computing infrastructure or exists in the cloud computing infrastructure.
  • the cloud network 10 may be configured using a 3G network, 4G or Long Term Evolution (LTE) network or a 5G network.
  • LTE Long Term Evolution
  • the devices 100a to 100e and 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 the base station, but may communicate with each other directly without passing through the base station.
  • the AI server 200 may include a server that performs AI processing and a server that performs operations on big data.
  • the AI server 200 includes at least one or more of the AI devices constituting the AI system 1, such as a robot 100a, an autonomous vehicle 100b, an XR device 100c, a smartphone 100d, or a home appliance 100e. Connected via the cloud network 10, the AI processing of the connected AI devices 100a to 100e may help at least a part.
  • the AI devices constituting the AI system 1 such as a robot 100a, an autonomous vehicle 100b, an XR device 100c, a smartphone 100d, or a home appliance 100e.
  • the AI processing of the connected AI devices 100a to 100e may help at least a part.
  • the AI server 200 may train the artificial neural network according to the machine learning algorithm on behalf of the AI devices 100a to 100e and directly store the learning model or transmit the training model 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 with respect to the received input data using a learning model, and generates a response or control command based on the inferred result value. Can be generated and transmitted to the AI device (100a to 100e).
  • the AI devices 100a to 100e may infer a result value from input data using a direct learning model and generate a response or control command based on the inferred result value.
  • the robot 100a may be applied to an AI technology, and may 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, or the like.
  • the robot 100a may include a robot control module for controlling an operation, and the robot control module may refer to a software module or a chip implemented in hardware.
  • the robot 100a acquires state information of the robot 100a by using sensor information obtained from various kinds of sensors, detects (recognizes) the surrounding environment and an object, generates map data, moves paths and travels. You can decide on a plan, determine a response to a user interaction, or determine an action.
  • the robot 100a may use sensor information obtained from at least one sensor among a rider, a radar, and a camera to determine a movement route and a travel plan.
  • the robot 100a may perform the above operations by using a learning model composed of at least one artificial neural network.
  • the robot 100a may recognize the surrounding environment and the object using the learning model, and determine the operation using the recognized surrounding environment information or the object information.
  • the learning model may be directly learned by the robot 100a or may be learned by 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 to perform an operation. You may.
  • the robot 100a determines a movement route and a travel plan by 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 movement path and the travel plan. Accordingly, the robot 100a may 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 about 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, location, and the like.
  • the robot 100a may control the driving unit based on the control / interaction of the user, thereby performing an operation or driving.
  • the robot 100a may acquire the intention information of the interaction according to the user's motion or voice utterance, and determine the response based on the obtained intention information to perform the operation.
  • the autonomous vehicle 100b may be implemented by an AI technology and implemented as a mobile robot, a vehicle, an unmanned aerial vehicle, or the like.
  • the autonomous vehicle 100b may include an autonomous driving control module for controlling the autonomous driving function, and the autonomous driving control module may refer to a software module or a chip implemented in hardware.
  • the autonomous driving control module may be included inside as a configuration of the autonomous driving vehicle 100b, but may be configured as a separate hardware and connected to the outside of the autonomous driving vehicle 100b.
  • the autonomous vehicle 100b obtains state information of the autonomous vehicle 100b by using sensor information obtained from various types of sensors, detects (recognizes) an environment and an object, generates map data, A travel route and a travel plan can be determined, or an action can be determined.
  • the autonomous vehicle 100b may use sensor information acquired from at least one sensor among a lidar, a radar, and a camera, similarly to the robot 100a, to determine a movement route and a travel plan.
  • the autonomous vehicle 100b may receive or recognize sensor information from external devices or receive information directly recognized from external devices. .
  • the autonomous vehicle 100b may perform the above operations by using a learning model composed of at least one artificial neural network.
  • the autonomous vehicle 100b may recognize a surrounding environment and an object using a learning model, and determine a driving line using the recognized surrounding environment information or object information.
  • the learning model may be learned directly from the autonomous vehicle 100b or may be learned from an external device such as the AI server 200.
  • the autonomous vehicle 100b 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 can also do
  • the autonomous vehicle 100b determines a moving route and a driving plan by 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 moving route and the driving plan. According to the plan, the autonomous vehicle 100b can be driven.
  • the map data may include object identification information for various objects arranged in a space (eg, a road) on which the autonomous vehicle 100b travels.
  • the map data may include object identification information about fixed objects such as street lights, rocks, buildings, and movable objects such as vehicles and pedestrians.
  • the object identification information may include a name, type, distance, location, and the like.
  • the autonomous vehicle 100b may perform an operation or drive by controlling the driving unit based on the user's control / interaction.
  • the autonomous vehicle 100b may acquire the intention information of the interaction according to the user's motion or voice utterance, and determine the response based on the obtained intention information to perform the operation.
  • AI technology is applied to the XR device 100c, and a head-mount display (HMD), a head-up display (HUD) provided in a vehicle, a television, a mobile phone, a smartphone, a computer, a wearable device, a home appliance, and a digital signage It may be implemented as a vehicle, a fixed robot or a mobile robot.
  • HMD head-mount display
  • HUD head-up display
  • the XR apparatus 100c analyzes three-dimensional point cloud data or image data acquired through various sensors or from an external device to generate location data and attribute data for three-dimensional points, thereby providing information on the surrounding space or reality object. It can obtain and render XR object to output. For example, the XR apparatus 100c may output an XR object including additional information about the recognized object in correspondence with the recognized object.
  • the XR apparatus 100c may perform the above-described operations using a learning model composed of at least one artificial neural network.
  • the XR apparatus 100c may recognize a reality object in 3D point cloud data or image data using a learning model, and may provide information corresponding to the recognized reality object.
  • the learning model may be learned directly from the XR device 100c or learned from an external device such as the AI server 200.
  • the XR apparatus 100c 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. It can also be done.
  • the robot 100a may be implemented using an AI technology and an autonomous driving technology, such as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flying robot, or the like.
  • an autonomous driving technology such as a guide robot, a transport robot, a cleaning robot, a wearable robot, an entertainment robot, a pet robot, an unmanned flying robot, or the like.
  • the robot 100a to which the AI technology and the autonomous driving technology are applied may mean a robot itself having an autonomous driving function, a robot 100a interacting with the autonomous vehicle 100b, and the like.
  • the robot 100a having an autonomous driving function may collectively move devices according to a given copper line or determine a copper line by itself without controlling the user.
  • the robot 100a and the autonomous vehicle 100b having the autonomous driving function may use a common sensing method to determine one or more of a movement route or a driving plan.
  • the robot 100a and the autonomous vehicle 100b having the autonomous driving function may determine one or more of the movement route or the driving plan by using information sensed through the lidar, the radar, and the camera.
  • the robot 100a which interacts with the autonomous vehicle 100b, is present separately from the autonomous vehicle 100b and is linked to the autonomous driving function inside or outside the autonomous vehicle 100b, or the autonomous vehicle 100b. ) May perform an operation associated with the user who boarded.
  • the robot 100a interacting with the autonomous vehicle 100b acquires sensor information on behalf of the autonomous vehicle 100b and provides the sensor information to the autonomous vehicle 100b or obtains sensor information, By generating object information and providing the object information to the autonomous vehicle 100b, the autonomous vehicle function of the autonomous vehicle 100b can be controlled or assisted.
  • the robot 100a interacting with the autonomous vehicle 100b may monitor a user in the autonomous vehicle 100b or control a function of the autonomous vehicle 100b through interaction with the user. .
  • the robot 100a may activate the autonomous driving function of the autonomous vehicle 100b or assist the control of the driver of the autonomous vehicle 100b.
  • the function of the autonomous vehicle 100b controlled by the robot 100a may include not only an autonomous vehicle function but also a function provided by a navigation system or an audio system provided inside the autonomous vehicle 100b.
  • the robot 100a interacting with the autonomous vehicle 100b may provide information or assist a function to the autonomous vehicle 100b outside the autonomous vehicle 100b.
  • the robot 100a may provide traffic information including signal information to the autonomous vehicle 100b, such as a smart signal light, or may interact with the autonomous vehicle 100b, such as an automatic electric charger of an electric vehicle. You can also automatically connect an electric charger to the charging port.
  • the robot 100a may be applied to an AI technology and an XR technology, and may 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, a drone, or the like.
  • the robot 100a to which the XR technology is applied may mean a robot that is the object of control / interaction in the XR image.
  • the robot 100a may be distinguished from the XR apparatus 100c and interlocked with each other.
  • the robot 100a When the robot 100a that is the object of control / interaction in the XR image acquires sensor information from sensors including a camera, the robot 100a or the XR apparatus 100c generates an XR image based on the sensor information. In addition, the XR apparatus 100c may output the generated XR image. The robot 100a may operate based on a control signal input through the XR apparatus 100c or user interaction.
  • the user may check an XR image corresponding to the viewpoint of the robot 100a that is remotely linked through an external device such as the XR device 100c, and may adjust the autonomous driving path of the robot 100a through interaction. You can control the movement or driving, or check the information of the surrounding objects.
  • the autonomous vehicle 100b may be implemented by an AI technology and an XR technology, such as a mobile robot, a vehicle, an unmanned aerial vehicle, and the like.
  • the autonomous vehicle 100b to which the XR technology is applied may mean an autonomous vehicle having a means for providing an XR image, or an autonomous vehicle that is the object of control / interaction in the XR image.
  • the autonomous vehicle 100b, which is the object of control / interaction in the XR image is distinguished from the XR apparatus 100c and may be linked with each other.
  • the autonomous vehicle 100b having means for providing an XR image may acquire sensor information from sensors including a camera and output an XR image generated based on the obtained sensor information.
  • the autonomous vehicle 100b may provide a passenger with an XR object corresponding to a real object or an object in a screen by outputting an XR image with a HUD.
  • the XR object when the XR object is output to the HUD, at least a part of the XR object may be output to overlap the actual object to which the occupant's eyes are directed.
  • the XR object when the XR object is output on the display provided inside the autonomous vehicle 100b, at least a portion of the XR object may be output to overlap the object in the screen.
  • the autonomous vehicle 100b may output XR objects corresponding to objects such as a road, another vehicle, a traffic light, a traffic sign, a motorcycle, a pedestrian, a building, and the like.
  • the autonomous vehicle 100b that is the object of control / interaction in the XR image acquires sensor information from sensors including a camera
  • the autonomous vehicle 100b or the XR apparatus 100c may be based on the sensor information.
  • the XR image may be generated, and the XR apparatus 100c may output the generated XR image.
  • such an autonomous vehicle 100b may operate based on a user's interaction or a control signal input through an external device such as the XR apparatus 100c.
  • the present invention is not limited to the order of the steps, some steps may occur in a different order or at the same time than the other steps described above.
  • those skilled in the art will appreciate that the steps shown in the flowcharts are not exclusive and that other steps may be included or one or more steps in the flowcharts may be deleted without affecting the scope of the present invention.
  • the claims described herein may be combined in various ways.
  • the technical features of the method claims of the present specification may be implemented in a device, and the technical features of the device claims of the present specification may be implemented in a method.
  • the technical features of the method claims of the present specification and the technical features of the device claims may be implemented as a device, and the technical features of the method claims of the present specification and the technical features of the device claims may be implemented in a method.

Landscapes

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

Abstract

La présente invention concerne, selon un mode de réalisation, un procédé selon lequel un équipement utilisateur (UE) effectue une procédure de requête de connexion. Le procédé comprend les étapes consistant à : recevoir un message de rejet associé à une régulation de l'encombrement basée sur un nom de réseau de données (DNN) en provenance d'un nœud de réseau d'un premier système, le message de rejet comprenant des premières informations concernant une valeur de temporisateur de réduction de puissance associée à la régulation de l'encombrement basée sur un DNN et des secondes informations associées à l'annulation d'un temporisateur de réduction de puissance dans lesquelles la valeur de temporisateur de réduction de puissance est utilisée ; commander le temporisateur de réduction de puissance associé à la régulation de l'encombrement basée sur un DNN sur la base des premières informations ; et, lorsqu'un changement inter-système du premier système à un second système est demandé, annuler le temporisateur de réduction de puissance sur la base des secondes informations et envoyer un message de requête de connexion au second système.
PCT/KR2019/008269 2018-08-06 2019-07-05 Procédé, équipement utilisateur et nœud de réseau permettant d'effectuer une procédure de requête de connexion WO2020032397A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2018-0091504 2018-08-06
KR20180091504 2018-08-06

Publications (1)

Publication Number Publication Date
WO2020032397A1 true WO2020032397A1 (fr) 2020-02-13

Family

ID=69415264

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/008269 WO2020032397A1 (fr) 2018-08-06 2019-07-05 Procédé, équipement utilisateur et nœud de réseau permettant d'effectuer une procédure de requête de connexion

Country Status (1)

Country Link
WO (1) WO2020032397A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160100450A1 (en) * 2014-10-07 2016-04-07 Telefonaktiebolaget L M Ericsson (Publ) Methods, Network Nodes, and Computer Program Products For Providing Access Point Name (APN) Based Group Congestion Control
KR20160075868A (ko) * 2012-02-06 2016-06-29 인텔 코포레이션 혼잡 상태의 무선 통신 네트워크에서 대기 시간 처리
WO2018008927A1 (fr) * 2016-07-05 2018-01-11 엘지전자 주식회사 Procédé pour effectuer un contrôle d'accès dans un réseau de communication mobile de prochaine génération, et équipement d'utilisateur
WO2018101574A1 (fr) * 2016-11-29 2018-06-07 엘지전자 주식회사 Procédé d'utilisation de fonction de désactivation de données de commutation de paquets et équipement utilisateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20160075868A (ko) * 2012-02-06 2016-06-29 인텔 코포레이션 혼잡 상태의 무선 통신 네트워크에서 대기 시간 처리
US20160100450A1 (en) * 2014-10-07 2016-04-07 Telefonaktiebolaget L M Ericsson (Publ) Methods, Network Nodes, and Computer Program Products For Providing Access Point Name (APN) Based Group Congestion Control
WO2018008927A1 (fr) * 2016-07-05 2018-01-11 엘지전자 주식회사 Procédé pour effectuer un contrôle d'accès dans un réseau de communication mobile de prochaine génération, et équipement d'utilisateur
WO2018101574A1 (fr) * 2016-11-29 2018-06-07 엘지전자 주식회사 Procédé d'utilisation de fonction de désactivation de données de commutation de paquets et équipement utilisateur

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3(Release 15", 3GPP TS 24.501, 15 June 2018 (2018-06-15) *

Similar Documents

Publication Publication Date Title
WO2020141965A1 (fr) Procédé et dispositif de réalisation d'un enregistrement sur un réseau dans un système de communication sans fil
WO2020171529A1 (fr) Procédé permettant de réaliser une communication liée à un état de désactivation de données de commutation de paquets
WO2020141964A1 (fr) Procédé permettant d'effectuer un enregistrement auprès d'un réseau dans un système de communication sans fil et dispositif correspondant
WO2020080913A1 (fr) Procédé prenant en charge une transmission de données séparée pour des tranches de réseau indépendantes dans un système de communication sans fil
WO2020046094A1 (fr) Procédé et appareil de sélection de réseau mobile terrestre public (plmn) d'accès dans un système de communication sans fil
WO2020067790A1 (fr) Procédé et appareil pour déterminer s'il convient d'effectuer une transmission sur un accès aléatoire ou un octroi configuré dans un système de communication sans fil
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é
WO2020256425A1 (fr) Procédé et appareil pour la prise en charge de sessions de pdu redondantes
WO2020204536A1 (fr) Procédé permettant à un terminal de se connecter à un réseau dans un système de communication sans fil
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
WO2020218764A1 (fr) Procédé pour effectuer un enregistrement auprès d'un réseau dans un système de communication sans fil, et appareil correspondant
WO2020036466A1 (fr) Procédé, dispositif de communication, et nœud de réseau pour transmettre ou recevoir un message de radiomessagerie
WO2020060007A1 (fr) Procédé et dispositif sans fil pour gérer une session de pdu dans une communication mobile 5g
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
WO2020022716A1 (fr) Procédé et dispositif de commande d'état de transmission de données dans un système de communication sans fil
WO2021162393A1 (fr) Communication liée à des sessions de pdu multi-accès
WO2020204310A1 (fr) Procédé pour faire face à une panne de réseau
WO2020076144A1 (fr) Procédé de configuration, à un réseau, de capacité d'un terminal prenant en charge de multiples systèmes d'accès sans fil dans un système de communication sans fil, et dispositif associé
WO2021167304A1 (fr) Communication relative à un état de désactivation du service de données ps
WO2020009440A1 (fr) Procédé et appareil de détermination de service pouvant être pris en charge dans un système de communications sans fil
WO2022050659A1 (fr) Commande du trafic
WO2021162500A1 (fr) Communication liée à une session pdu multi-accès
WO2020067733A1 (fr) Terminal effectuant un enregistrement dans un accès non 3 gpp et procédé effectué par celui-ci

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

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

Country of ref document: EP

Kind code of ref document: A1