EP4216622A2 - Procédé d'enregistrement de réseau pour orientation de trafic et dispositif le prenant en charge - Google Patents

Procédé d'enregistrement de réseau pour orientation de trafic et dispositif le prenant en charge Download PDF

Info

Publication number
EP4216622A2
EP4216622A2 EP22200098.6A EP22200098A EP4216622A2 EP 4216622 A2 EP4216622 A2 EP 4216622A2 EP 22200098 A EP22200098 A EP 22200098A EP 4216622 A2 EP4216622 A2 EP 4216622A2
Authority
EP
European Patent Office
Prior art keywords
3gpp access
access
registration
3gpp
pdu session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP22200098.6A
Other languages
German (de)
English (en)
Other versions
EP4216622A3 (fr
Inventor
Myungjune YOUN
Hyunsook Kim
Laeyoung Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP4216622A2 publication Critical patent/EP4216622A2/fr
Publication of EP4216622A3 publication Critical patent/EP4216622A3/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00222—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between different packet switched [PS] network technologies, e.g. transferring data sessions between LTE and WLAN or LTE and 5G
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present disclosure relates to a network registration method for traffic steering and a device supporting the same.
  • 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications.
  • 3GPP 3rd generation partnership project
  • LTE long-term evolution
  • Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity.
  • the 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.
  • ITU international telecommunication union
  • NR new radio
  • 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process.
  • ITU-R ITU radio communication sector
  • IMT international mobile telecommunications
  • the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.
  • the NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc.
  • eMBB enhanced mobile broadband
  • mMTC massive machine-type-communications
  • URLLC ultra-reliable and low latency communications
  • the NR shall be inherently forward compatible.
  • the Access Traffic Steering, Switching & Splitting (ATSSS) feature enables communication between the User Equipment (UE) and User Plane Function (UPF) simultaneously over multiple paths, typically over one 3GPP access path and over one non-3GPP access path.
  • UE User Equipment
  • UPF User Plane Function
  • the 5G system can provide services with improved user experience, can distribute the traffic across multiple accesses in a policy-based fashion, can provide new high-data-rate services, etc.
  • the 5G Core Network supports various types of non-3GPP accesses.
  • 5GC may support untrusted non-3GPP access, trusted non-3GPP access, wireline access, etc.
  • UE User Equipment
  • MA PDU Multi-Access Protocol Data Unit
  • a method performed by a UE adapted to operate in a wireless communication system includes, transmitting a registration request message to an Access and mobility Management Function (AMF) over a second non-3GPP access.
  • the registration request message includes information related to access switching from a first non-3GPP access to the second non-3GPP access.
  • the method includes, transmitting a PDU session establishment request message to a Session Management Function (SMF) over the second non-3GPP access.
  • SMF Session Management Function
  • the PDU session establishment request message includes information about a MA PDU session.
  • the method includes, receiving, from the AMF, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • a method performed by an AMF adapted to operate in a wireless communication system includes, receiving a registration request message from a UE over a second non-3GPP access.
  • the registration request message includes information related to access switching from the first non-3GPP access to the second non-3GPP access.
  • the method includes, based on the registration request message, i) performing a normal registration procedure, and ii) delaying a Unified Data Management (UDM) registration procedure.
  • UDM Unified Data Management
  • the method includes, receiving, from a SMF, information informing that the access switching from the first non-3GPP access to the second non-3GPP access is completed for the UE, performing an Access Network (AN) release procedure over the first non-3GPP access, performing the delayed UDM registration procedure, and transmitting, to the UE, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • AN Access Network
  • an apparatus for implementing the above method is provided.
  • the present disclosure may have various advantageous effects.
  • the UE can support service continuity by supporting access addition for the MA PDU session between different types of non-3GPP accesses.
  • the UE finds a new non-3GPP access, by supporting access switching between non-3GPP accesses, traffic using the MA PDU session can be transmitted smoothly.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • MC-FDMA multicarrier frequency division multiple access
  • CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE).
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • EDGE enhanced data rates for GSM evolution
  • OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA).
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • E-UTRA evolved UTRA
  • UTRA is a part of a universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA.
  • 3GPP LTE employs OFDMA in DL and SC-FDMA in UL.
  • Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G new radio (NR).
  • implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system.
  • the technical features of the present disclosure are not limited thereto.
  • the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.
  • a or B may mean “only A”, “only B”, or “both A and B”.
  • a or B in the present disclosure may be interpreted as “A and/or B”.
  • A, B or C in the present disclosure may mean “only A”, “only B”, “only C”, or "any combination of A, B and C”.
  • slash (/) or comma (,) may mean “and/or”.
  • A/B may mean “A and/or B”.
  • A/B may mean "only A”, “only B”, or “both A and B”.
  • A, B, C may mean "A, B or C”.
  • At least one of A and B may mean “only A”, “only B” or “both A and B”.
  • the expression “at least one of A or B” or “at least one of A and/or B” in the present disclosure may be interpreted as same as “at least one of A and B”.
  • At least one of A, B and C may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”.
  • at least one of A, B or C or “at least one of A, B and/or C” may mean “at least one of A, B and C”.
  • parentheses used in the present disclosure may mean “for example”.
  • control information PDCCH
  • PDCCH control information
  • PDCCH control information
  • PDCCH control information
  • FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.
  • the 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1 .
  • Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra-reliable and low latency communications
  • the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300.
  • FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.
  • the BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS/network node with respect to other wireless devices.
  • the wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication/radio/5G devices.
  • RAT radio access technology
  • the wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400.
  • the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles.
  • the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone).
  • UAV unmanned aerial vehicle
  • the XR device may include an AR/VR/Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc.
  • the hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook).
  • the home appliance may include a TV, a refrigerator, and a washing machine.
  • the IoT device may include a sensor and a smartmeter.
  • the wireless devices 100a to 100f may be called user equipments (UEs).
  • a UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather/environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.
  • PDA personal digital assistant
  • PMP portable multimedia player
  • PC slate personal computer
  • tablet PC a tablet PC
  • ultrabook a vehicle, a vehicle having an autonomous
  • the wireless devices 100a to 100f may be connected to the network 300 via the BSs 200.
  • An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300.
  • the network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network.
  • the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200/network 300.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication).
  • the IoT device e.g., a sensor
  • the IoT device may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
  • Wireless communication/connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and/or between wireless device 100a to 100f and BS 200 and/or between BSs 200.
  • the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc.
  • the wireless devices 100a to 100f and the BSs 200/the wireless devices 100a to 100f may transmit/receive radio signals to/from each other through the wireless communication/connections 150a, 150b and 150c.
  • the wireless communication/connections 150a, 150b and 150c may transmit/receive signals through various physical channels.
  • various configuration information configuring processes e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping
  • resource allocating processes for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.
  • NR supports multiples numerologies (and/or multiple subcarrier spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz/60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.
  • numerologies and/or multiple subcarrier spacings (SCS)
  • the NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2.
  • the numerical value of the frequency range may be changed.
  • the frequency ranges of the two types may be as shown in Table 1 below.
  • FR1 may mean "sub 6 GHz range”
  • FR2 may mean "above 6 GHz range”
  • mmW millimeter wave
  • FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving). [Table 2] Frequency Range designation Corresponding frequency range Subcarrier Spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz
  • the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G.
  • NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and/or LTE Cat NB2, and may not be limited to the above-mentioned names.
  • LPWAN low power wide area network
  • the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology.
  • LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC).
  • eMTC enhanced machine type communication
  • LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and may not be limited to the above-mentioned names.
  • the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and/or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names.
  • ZigBee technology may generate personal area networks (PANs) associated with small/low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.
  • PANs personal area networks
  • FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.
  • a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR).
  • RATs e.g., LTE and NR
  • ⁇ the first wireless device 100 and the second wireless device 200 ⁇ may correspond to at least one of ⁇ the wireless device 100a to 100f and the BS 200 ⁇ , ⁇ the wireless device 100a to 100f and the wireless device 100a to 100f ⁇ and/or ⁇ the BS 200 and the BS 200 ⁇ of FIG. 1 .
  • the first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and/or one or more antennas 108.
  • a transceiver such as a transceiver 106
  • a processing chip such as a processing chip 101
  • antennas 108 one or more antennas 108.
  • the processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. It is exemplarily shown in FIG. 2 that the memory 104 is included in the processing chip 101. Additional and/or alternatively, the memory 104 may be placed outside of the processing chip 101.
  • the processor 102 may control the memory 104 and/or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver 106. The processor 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory 104.
  • the memory 104 may be operably connectable to the processor 102.
  • the memory 104 may store various types of information and/or instructions.
  • the memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 105 may control the processor 102 to perform one or more protocols.
  • the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.
  • the processor 102 and the memory 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
  • the transceiver 106 may be connected to the processor 102 and transmit and/or receive radio signals through one or more antennas 108.
  • Each of the transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be interchangeably used with radio frequency (RF) unit(s).
  • the first wireless device 100 may represent a communication modem/circuit/chip.
  • the second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and/or one or more antennas 208.
  • the processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. It is exemplarily shown in FIG. 2 that the memory 204 is included in the processing chip 201. Additional and/or alternatively, the memory 204 may be placed outside of the processing chip 201.
  • the processor 202 may control the memory 204 and/or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver 206. The processor 202 may receive radio signals including fourth information/signals through the transceiver 106 and then store information obtained by processing the fourth information/signals in the memory 204.
  • the memory 204 may be operably connectable to the processor 202.
  • the memory 204 may store various types of information and/or instructions.
  • the memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the software code 205 may control the processor 202 to perform one or more protocols.
  • the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.
  • the processor 202 and the memory 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
  • the transceiver 206 may be connected to the processor 202 and transmit and/or receive radio signals through one or more antennas 208.
  • Each of the transceiver 206 may include a transmitter and/or a receiver.
  • the transceiver 206 may be interchangeably used with RF unit.
  • the second wireless device 200 may represent a communication modem/circuit/chip.
  • One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202.
  • the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer).
  • layers e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer).
  • PHY physical
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • the one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206.
  • the one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers.
  • the one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be adapted to include the modules, procedures, or functions.
  • Firmware or software adapted to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202.
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.
  • the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands.
  • the one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof.
  • the one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202.
  • the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.
  • the one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices.
  • the one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices.
  • the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals.
  • the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices.
  • the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.
  • the one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208.
  • the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).
  • the one or more transceivers 106 and 206 may convert received user data, control information, radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202.
  • the one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals.
  • the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.
  • the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and/or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency.
  • the one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the one or more processors 102 and 202.
  • a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL).
  • a BS may operate as a receiving device in UL and as a transmitting device in DL.
  • the first wireless device 100 acts as the UE
  • the second wireless device 200 acts as the BS.
  • the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure.
  • the processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.
  • a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB
  • FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.
  • the wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 1 ).
  • wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.
  • each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140.
  • the communication unit 110 may include a communication circuit 112 and transceiver(s) 114.
  • the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and/or the one or more memories 104 and 204 of FIG. 2 .
  • the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG.
  • the control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200.
  • the control unit 120 may control an electric/mechanical operation of each of the wireless devices 100 and 200 based on programs/code/commands/information stored in the memory unit 130.
  • the control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.
  • the additional components 140 may be variously configured according to types of the wireless devices 100 and 200.
  • the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit.
  • the wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1 ), the vehicles (100b-1 and 100b-2 of FIG. 1 ), the XR device (100c of FIG. 1 ), the hand-held device (100d of FIG. 1 ), the home appliance (100e of FIG. 1 ), the IoT device (100f of FIG.
  • the wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example/service.
  • the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110.
  • the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110.
  • Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements.
  • the control unit 120 may be configured by a set of one or more processors.
  • control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor.
  • memory unit 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.
  • FIG. 4 shows an example of UE to which implementations of the present disclosure is applied.
  • a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the wireless device 100 or 200 of FIG. 3 .
  • a UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.
  • SIM subscriber identification module
  • the processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • the processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.
  • Layers of the radio interface protocol may be implemented in the processor 102.
  • the processor 102 may include ASIC, other chipset, logic circuit and/or data processing device.
  • the processor 102 may be an application processor.
  • the processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator).
  • DSP digital signal processor
  • CPU central processing unit
  • GPU graphics processing unit
  • modem modulator and demodulator
  • processor 102 may be found in SNAPDRAGON TM series of processors made by Qualcomm ® , EXYNOS TM series of processors made by Samsung ® , A series of processors made by Apple ® , HELIO TM series of processors made by MediaTek ® , ATOM TM series of processors made by Intel ® or a corresponding next generation processor.
  • the memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102.
  • the memory 104 may include ROM, RAM, flash memory, memory card, storage medium and/or other storage device.
  • modules e.g., procedures, functions, etc.
  • the modules can be stored in the memory 104 and executed by the processor 102.
  • the memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.
  • the transceiver 106 is operatively coupled with the processor 102, and transmits and/or receives a radio signal.
  • the transceiver 106 includes a transmitter and a receiver.
  • the transceiver 106 may include baseband circuitry to process radio frequency signals.
  • the transceiver 106 controls the one or more antennas 108 to transmit and/or receive a radio signal.
  • the power management module 110 manages power for the processor 102 and/or the transceiver 106.
  • the battery 112 supplies power to the power management module 110.
  • the display 114 outputs results processed by the processor 102.
  • the keypad 116 receives inputs to be used by the processor 102.
  • the keypad 116 may be shown on the display 114.
  • the SIM card 118 is an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards.
  • IMSI international mobile subscriber identity
  • the speaker 120 outputs sound-related results processed by the processor 102.
  • the microphone 122 receives sound-related inputs to be used by the processor 102.
  • FIG. 5 shows an example of 5G system architecture to which implementations of the present disclosure is applied.
  • the 5G system (5GS) architecture consists of the following network functions (NF).
  • FIG. 5 depicts the 5G system architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other.
  • the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary.
  • the UDR and its connections with other NFs are not depicted in FIG. 5 .
  • the NWDAF and its connections with other NFs are not depicted in FIG. 5 .
  • the 5G system architecture contains the following reference points:
  • a couple of NFs may need to be associated with each other to serve a UE.
  • FIGS. 6 and 7 show an example of a registration procedure to which implementations of the present disclosure is applied.
  • a UE needs to register with the network to get authorized to receive services, to enable mobility tracking and to enable reachability.
  • the UE initiates the registration procedure using one of the following registration types:
  • the general registration procedure in FIGS. 6 and 7 applies on all these registration procedures, but the periodic registration update need not include all parameters that are used in other registration cases.
  • the general registration procedure in FIGS. 6 and 7 is also used for the case of registration in 3GPP access when the UE is already registered in a non-3GPP access, and vice versa. Registration in 3GPP access when the UE is already registered in a non-3GPP access scenario may require an AMF change.
  • the Registration Request message may include AN parameters.
  • the AN parameters include, e.g., 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)) and Requested network slice selection assistance information (NSSAI).
  • the AN parameters also include establishment cause. The establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the Requested NSSAI as part of the AN parameters is dependent on the value of the access stratum connection establishment NSSAI inclusion mode parameter.
  • the Registration Request message may include a registration type.
  • the registration type indicates if the UE wants to perform an initial registration (i.e., the UE is in RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in RM-REGISTERED state and initiates a registration procedure due to mobility or due to the UE needs to update its capabilities or protocol parameters, or to request a change of the set of network slices it is allowed to use), a periodic registration update (i.e., the UE is in RM-REGISTERED state and initiates a registration procedure due to the periodic registration update timer expiry) or an emergency registration (i.e., the UE is in limited service state).
  • an initial registration i.e., the UE is in RM-DEREGISTERED state
  • a mobility registration update i.e., the UE is in RM-REGISTERED state and initiates a registration procedure due to mobility or due to the UE needs to update its capabilities or protocol parameters, or
  • the UE When the UE is performing an initial registration, the UE shall indicate its UE identity in the Registration Request message as follows, listed in decreasing order of preference:
  • the UE When the UE performing an initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE shall also indicate the native 5G-GUTI as additional GUTI. If more than one native 5G-GUTIs are available, the UE shall select the 5G-GUTI in decreasing order of preference among items (ii)-(iv) in the list above.
  • the UE When the UE is performing an initial registration with a native 5G-GUTI, then the UE shall indicate the related GUAMI information in the AN parameters. When the UE is performing an initial registration with its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.
  • the SUCI shall be included if the UE does not have a valid 5G-GUTI available; the permanent equipment identifier (PEI) shall be included when the UE has no subscriber permanent identifier (SUPI) and no valid 5G-GUTI. In other cases, the 5G-GUTI is included and it indicates the last serving AMF
  • the Registration Request message may also include security parameters, PDU Session Status, etc.
  • the security parameters are used for authentication and integrity protection.
  • the PDU Session Status indicates the previously established PDU sessions in the UE. When the UE is connected to the two AMFs belonging to different PLMN via 3GPP access and non-3GPP access then the PDU Session status indicates the established PDU Session of the current PLMN in the UE.
  • Step 2 The (R)AN selects an AMF.
  • the (R)AN based on (R)AT and requested NSSAI, if available, selects an AMF
  • the (R)AN can forward the Registration Request message to the AMF based on the N2 connection of the UE.
  • the (R)AN If the (R)AN cannot select an appropriate AMF, it forwards the Registration Request message to an AMF which has been configured, in the (R)AN, to perform AMF selection.
  • Step 3 The (R)AN transmits a Registration Request message to the new AMF
  • the Registration Request message corresponds to N2 message.
  • the Registration Request message may include whole information and/or a part of information included in the Registration Request message received from the UE which is described in step 1.
  • the Registration Request message may include N2 parameters.
  • the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information and cell identity related to the cell in which the UE is camping, UE context request which indicates that a UE context including security information needs to be setup at the NG-RAN.
  • the N2 parameters shall also include the establishment cause.
  • steps 4 to 19 may be omitted.
  • Step 4 If the UE's 5G-GUTI was included in the Registration Request message and the serving AMF has changed since last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation on the old AMF including the complete registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.
  • NAS non-access stratum
  • Step 5 The Old AMF may respond to the new AMF for the Namf Communication_UEContextTransfer invocation by including the UE's SUPI and UE context.
  • Step 6 If the SUCI is not provided by the UE nor retrieved from the old AMF, the identity request procedure may be initiated by the new AMF sending the Identity Request message to the UE requesting the SUCI.
  • Step 7 The UE may respond with an Identity Response message including the SUCI.
  • the UE derives the SUCI by using the provisioned public key of the home PLMN (HPLMN).
  • HPLMN home PLMN
  • Step 8 The new AMF may decide to initiate UE authentication by invoking an AUSF. In that case, the new AMF selects an AUSF based on SUPI or SUCI.
  • Step 9 Authentication/security may be established by the UE, new AMF, AUSF and/or UDM.
  • Step 10 If the AMF has changed, the new AMF may notify the old AMF that the registration of the UE in the new AMF is completed by invoking the Namf Communication_RegistrationCompleteNotify service operation. If the authentication/security procedure fails, then the registration shall be rejected, and the new AMF may invoke the Namf Communication_RegistrationCompleteNotify service operation with a reject indication reason code towards the old AMF. The old AMF may continue as if the UE context transfer service operation was never received.
  • Step 11 If the PEI was not provided by the UE nor retrieved from the old AMF, the Identity Request procedure may be initiated by the new AMF sending an Identity Request message to the UE to retrieve the PEI.
  • the PEI shall be transferred encrypted unless the UE performs emergency registration and cannot be authenticated.
  • Step 12 the new AMF may initiate ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation.
  • Step 13 If step 14 below is to be performed, the new AMF, based on the SUPI, may select a UDM, then UDM may select a UDR instance.
  • Step 14 The new AMF may register with the UDM.
  • Step 15 The new AMF may select a PCF.
  • Step 16 The new AMF may optionally perform an AM Policy Association Establishment/Modification.
  • Step 17 The new AMF may transmit Update/Release SM Context message (e.g., Nsmf PDUSession_UpdateSMContext and/or Nsmf_PDUSession_ReleaseSMContext) to the SMF.
  • Update/Release SM Context message e.g., Nsmf PDUSession_UpdateSMContext and/or Nsmf_PDUSession_ReleaseSMContext
  • Step 18 If the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE Context Modification Request to the N3IWF/TNGF/W-AGF.
  • Step 19 The N3IWF/TNGF/W-AGF may send a UE Context Modification Response to the new AMF
  • Step 20 After the new AMF receives the response message from the N3IWF/TNGF/W-AGF in step 19, the new AMF may register with the UDM.
  • Step 21 The new AMF transmits a Registration Accept message to the UE.
  • the new AMF sends a Registration Accept message to the UE indicating that the Registration Request has been accepted.
  • 5G-GUTI is included if the new AMF allocates a new 5G-GUTI. If the UE is already in RM-REGISTERED state via another access in the same PLMN, the UE shall use the 5G-GUTI received in the Registration Accept message for both registrations. If no 5G-GUTI is included in the Registration Accept message, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration. If the new AMF allocates a new registration area, it shall send the registration area to the UE via Registration Accept message. If there is no registration area included in the Registration Accept message, the UE shall consider the old registration area as valid.
  • Mobility Restrictions is included in case mobility restrictions applies for the UE and registration type is not emergency registration.
  • the new AMF indicates the established PDU sessions to the UE in the PDU Session status.
  • the UE removes locally any internal resources related to PDU sessions that are not marked as established in the received PDU Session status.
  • the UE is connected to the two AMFs belonging to different PLMN via 3GPP access and non-3GPP access then the UE removes locally any internal resources related to the PDU session of the current PLMN that are not marked as established in received PDU Session status. If the PDU Session status information was in the Registration Request message, the new AMF shall indicate the PDU Session status to the UE.
  • the Allowed NSSAI provided in the Registration Accept message is valid in the registration area and it applies for all the PLMNs which have their tracking areas included in the registration area.
  • the Mapping Of Allowed NSSAI is the mapping of each S-NSSAI of the Allowed NSSAI to the HPLMN S-NSSAIs.
  • the Mapping Of Configured NSSAI is the mapping of each S-NSSAI of the Configured NSSAI for the serving PLMN to the HPLMN S-NSSAIs.
  • the new AMF performs a UE Policy Association Establishment.
  • Step 22 The UE may send a Registration Complete message to the new AMF when it has successfully updated itself.
  • the UE may send a Registration Complete message to the new AMF to acknowledge if a new 5G-GUTI was assigned.
  • Step 23 For registration over 3GPP Access, if the new AMF does not release the signaling connection, the new AMF may send the RRC Inactive Assistance Information to the NG-RAN. For registration over non-3GPP Access, if the UE is also in CM-CONNECTED state on 3GPP access, the new AMF may send the RRC Inactive Assistance Information to the NG-RAN.
  • Step 24 The new AMF may perform information update towards the UDM.
  • Step 25 The UE may execute Network Slice-Specific Authentication and Authorization procedure.
  • a PDU session establishment procedure is described.
  • FIGS. 8 and 9 show an example of a PDU session establishment procedure to which implementations of the present disclosure is applied.
  • a PDU session establishment may correspond to:
  • a PDU session may be associated either (a) with a single access type at a given time, i.e., either 3GPP access or non-3GPP access, or (b) simultaneously with multiple access types, i.e., one 3GPP access and one non-3GPP access.
  • a PDU session associated with multiple access types is referred to as multi access PDU (MA PDU) session and it may be requested by access traffic steering, switching, splitting (ATSSS)-capable UEs.
  • MA PDU multi access PDU
  • FIGS. 8 and 9 specify the procedures for establishing PDU sessions associated with a single access type at a given time.
  • the UE initiates the UE requested PDU session establishment procedure by the transmission of a NAS message containing a PDU Session Establishment Request message within the N1 SM container.
  • the PDU Session Establishment Request message includes a PDU session ID, Requested PDU Session Type, a Requested session and service continuity (SSC) mode, 5GSM Capability, protocol configuration options (PCO), SM PDU DN Request Container, UE Integrity Protection Maximum Data Rate, etc.
  • the Request Type indicates "Initial request” if the PDU session establishment is a request to establish a new PDU session and indicates “Existing PDU Session” if the request refers to an existing PDU session switching between 3GPP access and non-3GPP access or to a PDU session handover from an existing packet data network (PDN) connection in EPC.
  • the Request Type indicates "Emergency Request” if the PDU session establishment is a request to establish a PDU session for emergency services.
  • the Request Type indicates "Existing Emergency PDU Session” if the request refers to an existing PDU session for emergency services switching between 3GPP access and non-3GPP access or to a PDU session handover from an existing PDN connection for emergency services in EPC.
  • the UE includes the S-NSSAI from the Allowed NSSAI of the current access type. If the Mapping of Allowed NSSAI was provided to the UE, the UE shall provide both the S-NSSAI of the visited PLMN (VPLMN) from the Allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI.
  • VPN visited PLMN
  • Step 2 The AMF selects an SMF. If the Request Type indicates "Initial request” or the request is due to handover from EPS or from non-3GPP access serving by a different AMF, the AMF stores an association of the S-NSSAI(s), the data network name (DNN), the PDU session ID, the SMF ID as well as the Access Type of the PDU session.
  • the AMF stores an association of the S-NSSAI(s), the data network name (DNN), the PDU session ID, the SMF ID as well as the Access Type of the PDU session.
  • the AMF selects an SMF and stores an association of the new PDU Session ID, the S-NSSAI(s), the selected SMF ID as well as Access Type of the PDU Session.
  • the AMF selects the SMF based on SMF-ID received from UDM.
  • the AMF updates the Access Type stored for the PDU session.
  • the PDU session establishment procedure can be performed in the following cases:
  • the AMF shall reject the PDU session establishment request with an appropriate reject cause.
  • the AMF shall reject a request coming from an emergency registered UE and the Request Type indicates neither "Emergency Request” nor "Existing Emergency PDU Session".
  • Step 3 If the AMF does not have an association with an SMF for the PDU session ID provided by the UE (e.g., when Request Type indicates "initial request"), the AMF invokes Create SM Context Request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF already has an association with an SMF for the PDU session ID provided by the UE (e.g., when Request Type indicates "existing PDU Session"), the AMF invokes Update SM Context Request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).
  • Create SM Context Request procedure e.g., Nsmf_PDUSession_CreateSMContext Request.
  • the AMF sends the S-NSSAI of the serving PLMN from the Allowed NSSAI to the SMF.
  • the AMF also sends the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI to the SMF.
  • the AMF ID is the UE's GUAMI which uniquely identifies the AMF serving the UE.
  • the AMF forwards the PDU session ID together with the N1 SM container containing the PDU Session Establishment Request message received from the UE.
  • the generic public subscription identifier (GPSI) shall be included if available at AMF
  • the AMF provides the PEI instead of the SUPI when the UE in limited service state has registered for emergency services without providing a SUPI.
  • the AMF indicates that the SUPI has not been authenticated.
  • the SMF determines that the UE has not been authenticated when it does not receive a SUPI for the UE or when the AMF indicates that the SUPI has not been authenticated.
  • the AMF may include a PCF ID in the Nsmf_PDUSession_CreateSMContext Request. This PCF ID identifies the home PCF (H-PCF) in the non-roaming case and the visited PCF (V-PCF) in the LBO roaming case.
  • H-PCF home PCF
  • V-PCF visited PCF
  • Step 4 If session management subscription data for corresponding SUPI, DNN and S-NSSAI of the HPLMN is not available, then SMF may retrieve the session management subscription data from the UDM and subscribes to be notified when this subscription data is modified.
  • Step 5 The SMF transmits either Create SM Context Response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or Update SM Context Response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to the AMF, depending on the request received in step 3.
  • Create SM Context Response message e.g., Nsmf_PDUSession_CreateSMContext Response
  • Update SM Context Response message e.g., Nsmf_PDUSession_UpdateSMContext Response
  • the SMF If the SMF received Nsmf_PDUSession_CreateSMContext Request in step 3 and the SMF is able to process the PDU session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM Context ID.
  • the SMF When the SMF decides to not accept to establish a PDU session, the SMF rejects the UE request via NAS SM signaling including a relevant SM rejection cause by responding to the AMF with Nsmf_PDUSession_CreateSMContext Response.
  • the SMF also indicates to the AMF that the PDU session ID is to be considered as released, the SMF proceeds to step 20 below and the PDU session establishment procedure is stopped.
  • Step 6 Optional secondary authentication/authorization may be performed.
  • Step 7a If dynamic policy and charging control (PCC) is to be used for the PDU session, the SMF may perform PCF selection.
  • PCC dynamic policy and charging control
  • Step 7b The SMF may perform an SM Policy Association Establishment procedure to establish an SM Policy association with the PCF and get the default PCC rules for the PDU session.
  • Step 8 The SMF selects one or more UPFs.
  • Step 9 The SMF may perform an SMF initiated SM Policy Association Modification procedure to provide information on the policy control request trigger condition(s) that have been met.
  • Step 10 If Request Type indicates "initial request", the SMF may initiate an N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate an N4 Session Modification procedure with the selected UPF
  • the SMF may send an N4 Session Establishment/Modification Request to the UPF and provides packet detection, enforcement and reporting rules to be installed on the UPF for this PDU session.
  • the UPF may acknowledge by sending an N4 Session Establishment/Modification Response.
  • Step 11 The SMF transmits a N1N2Message Transfer message (e.g., Namf_Communication_N1N2MessageTransfer) to the AMF.
  • N1N2Message Transfer message e.g., Namf_Communication_N1N2MessageTransfer
  • the N1N2Message Transfer message may include N2 SM information.
  • the N2 SM information carries information that the AMF shall forward to the (R)AN which may include:
  • the N1N2Message Transfer message may include N1 SM container.
  • the N1 SM container contains the PDU Session Establishment Accept message that the AMF shall provide to the UE.
  • the PDU Session Establishment Accept message includes S-NSSAI from the Allowed NSSAI.
  • the PDU Session Establishment Accept message includes the S-NSSAI from the Allowed NSSAI for the VPLMN and also it includes the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI that SMF received in step 3.
  • QoS Rules QoS flow level, QoS parameters if needed for the QoS Flow(s) associated with those QoS rule(s) and QoS Profiles may be included in the PDU Session Establishment Accept message within the N1 SM container and in the N2 SM information.
  • the N1N2Message Transfer message shall include the N1 SM container with a PDU Session Establishment Reject message and shall not include any N2 SM information.
  • the (R)AN sends the NAS message containing the PDU Session Establishment Reject message to the UE. In this case, steps 12-17 are skipped.
  • Step 12 The AMF sends the NAS message containing PDU Session ID and PDU Session Establishment Accept message targeted to the UE and the N2 SM information received from the SMF within the N2 PDU Session Request message to the (R)AN.
  • Step 13 The (R)AN may issue AN specific signaling exchange with the UE that is related with the information received from SMF. For example, in case of a NG-RAN, an RRC connection reconfiguration may take place with the UE establishing the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12.
  • the (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) provided in step 12 to the UE.
  • the (R)AN shall only provide the NAS message to the UE if the AN specific signaling exchange with the UE includes the (R)AN resource additions associated to the received N2 command.
  • step 11 If the N2 SM information is not included in the step 11, then the following steps 14 to 16b and step 17 are omitted.
  • Step 14 The (R)AN transmits a N2 PDU Session Response message to the AMF.
  • the N2 PDU Session Response message may include PDU session ID, Cause, N2 SM information (PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI(s), User Plane Enforcement Policy Notification)), etc.
  • Step 15 The AMF transmits an Update SM Context Request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to the SMF.
  • the AMF forwards the N2 SM information received from (R)AN to the SMF.
  • Step S16a The SMF initiates an N4 Session Modification procedure with the UPF.
  • the SMF provides AN Tunnel Info to the UPF as well as the corresponding forwarding rules.
  • Step S16b The UPF provides an N4 Session Modification Response to the SMF.
  • the UPF may deliver any DL packets to the UE that may have been buffered for this PDU session.
  • Step 16c If the SMF has not yet registered for this PDU session, then the SMF may register with the UDM for a given PDU Session.
  • Step 17 The SMF transmits an Update SM Context Response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to the AMF.
  • an Update SM Context Response message e.g., Nsmf_PDUSession_UpdateSMContext Response
  • the AMF forwards relevant events subscribed by the SMF.
  • Step 18 If during the procedure, any time after step 5, the PDU session establishment is not successful, the SMF may inform the AMF by invoking Nsmf_PDUSession_SMContextStatusNotify (Release). The SMF may also release any N4 session(s) created, any PDU session address if allocated (e.g., IP address) and release the association with PCF, if any. In this case, step 19 is skipped.
  • Step 19 In the case of PDU Session Type IPv6 or IPv4v6, the SMF may generate an IPv6 Router Advertisement and send it to the UE.
  • Step 20 The SMF may perform SMF initiated SM Policy Association Modification.
  • Step 21 If the PDU Session establishment failed after step 4, the SMF may unsubscribe to the modifications of session management subscription data, if the SMF is no more handling a PDU session of the UE.
  • Non-3GPP access is described.
  • the 5G Core Network supports connectivity of UEs via non-3GPP access networks, e.g. Wireless Local Area Network (WLAN) access networks.
  • WLAN Wireless Local Area Network
  • the 5GC supports both untrusted non-3GPP access networks and Trusted Non-3GPP Access Networks (TNANs).
  • TNANs Trusted Non-3GPP Access Networks
  • N3IWF An untrusted non-3GPP access network is connected to the 5GC via a N3IWF, whereas a trusted non-3GPP access network is connected to the 5GC via a Trusted Non-3GPP Gateway Function (TNGF).
  • TNGF Trusted Non-3GPP Gateway Function
  • a non-3GPP access network may advertise the PLMNs for which it supports trusted connectivity and the type of supported trusted connectivity (e.g. "5G connectivity"). Therefore, the UEs may discover the non-3GPP access networks that can provide trusted connectivity to one or more PLMNs.
  • 5G connectivity the type of supported trusted connectivity
  • the UE may decide to use trusted or untrusted non-3GPP access for connecting to a 5G PLMN.
  • N1 instances exist for the UE, i.e., there are one N1 instance over NG-RAN and one N1 instance over non-3GPP access.
  • a UE simultaneously connected to the same 5GC of a PLMN over a 3GPP access and a non-3GPP access is served by a single AMF in this 5GC.
  • a UE When a UE is connected to a 3GPP access of a PLMN, if the UE selects a N3IWF and the N3IWF is located in a PLMN different from the PLMN of the 3GPP access, e.g., in a different VPLMN or in the HPLMN, the UE is served separately by the two PLMNs. The UE is registered with two separate AMFs. PDU sessions over the 3GPP access are served by V-SMFs different from the V-SMF serving the PDU Sessions over the non-3GPP access. The same may be true when the UE uses trusted non-3GPP access, i.e., the UE may select one PLMN for 3GPP access and a different PLMN for trusted non-3GPP access.
  • the PLMN selection for the 3GPP access does not depend on the PLMN that is used for non-3GPP access. In other words, if a UE is registered with a PLMN over a non-3GPP access, the UE performs PLMN selection for the 3GPP access independently of this PLMN
  • a UE establishes an IPsec tunnel with the N3IWF or with the TNGF in order to register with the 5GC over non-3GPP access.
  • N1 NAS signaling over non-3GPP accesses is protected with the same security mechanism applied for N1 over a 3GPP access.
  • FIG. 10 shows an example of an architecture for a 5GC with an untrusted non-3GPP access to which implementations of the present disclosure is applied.
  • FIG. 11 shows an example of an architecture for a 5GC with a trusted non-3GPP access to which implementations of the present disclosure is applied.
  • ATSSS Access Traffic Steering, Switching & Splitting
  • the ATSSS feature is an optional feature that may be supported by the UE and the 5GC.
  • the ATSSS feature enables a multi-access PDU connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network and two independent N3/N9 tunnels between the PDU Session Anchor (PSA) and RAN/AN.
  • the multi-access PDU connectivity service is realized by establishing a Multi-Access PDU (MA PDU) Session, i.e., a PDU session that may have user-plane resources on two access networks. This assumes both 3GPP access and non-3GPP access are allowed for the S-NSSAI of the PDU session.
  • MA PDU Multi-Access PDU
  • the UE may request a MA PDU session when the UE is registered via both 3GPP and non-3GPP accesses, or when the UE is registered via one access only.
  • the UE After the establishment of a MA PDU session, and when there are user-plane resources on both access networks, the UE applies network-provided policy (i.e., ATSSS rules) and considers local conditions (such as network interface availability, signal loss conditions, user preferences, etc.) for deciding how to distribute the uplink traffic across the two access networks.
  • the UPF anchor of the MA PDU session applies network-provided policy (i.e., N4 rules) and feedback information received from the UE via the user-plane (such as access network Unavailability or Availability) for deciding how to distribute the downlink traffic across the two N3/N9 tunnels and two access networks.
  • the UE applies the ATSSS rules and considers local conditions for triggering the establishment or activation of the user plane resources over another access.
  • the type of a MA PDU Session may be one of IPv4, IPv6, IPv4v6, and Ethernet.
  • the ATSSS feature may be supported over any type of access network, including untrusted and trusted non-3GPP access networks, wireline 5G access networks, etc., as long as a MA PDU session can be established over this type of access network.
  • the UE due to mobility, moves from being served by a source AMF supporting ATSSS to a target AMF not supporting ATSSS, the MA PDU session is released.
  • MA PDU session is managed by using the session management functionality, with the following additions and modifications.
  • a MA PDU session may be established either:
  • the AMF indicates as part of the registration procedure whether ATSSS is supported or not.
  • ATSSS is not supported, the UE does not:
  • An ATSSS-capable UE may decide to request a MA PDU session based on the provisioned URSP rules.
  • the UE requests a MA PDU session when the UE applies a URSP rule, which triggers the UE to establish a new PDU session and the Access Type Preference component of the URSP rule indicates "Multi-Access".
  • 3GPP NR Rel-18 how the MA PDU session can support more types of access paths will be discussed. More specifically, how the traffic of an MA PDU session can be switched between two non-3GPP access paths (e.g., untrusted non-3GPP access and trusted non-3GPP access) in the same PLMN may be discussed.
  • two non-3GPP access paths e.g., untrusted non-3GPP access and trusted non-3GPP access
  • a case in which traffic is switched between one non-3GPP access path from the UE to a N3IWF in PLMN-1 and another non-3GPP access path from the UE to a TNGF in PLMN-1 may be considered.
  • the UE registrations via two non-3GPP access paths in PLMN-1 may be maintained only for the duration needed to switch the traffic from a source non-3GPP access path to a target non-3GPP access path. After switching the traffic, only one UE registration via non-3GPP access may exist.
  • the UE may also be able to access PLMN-1 directly using 3GPP radio technology.
  • the MA PDU session may have three access paths for the duration needed to switch the traffic from a source non-3GPP access path to a target non-3GPP access path.
  • the existing steering modes and the existing steering functionalities is reused and, if needed, potential enhancements may be considered to support the above case.
  • FIG. 12 shows an example in which traffic of a MA PDU session is switched between an untrusted non-3GPP access and a trusted non-3GPP access to which implementations of the present disclosure is applied.
  • the UE While the UE receives service over an untrusted non-3GPP access of the 5GC through a Stand-alone Non-Public Network (SNPN) in 3GPP access, and when Wi-Fi becomes available, the UE may receive service over a trusted non-3GPP access using Wi-Fi. In this case, traffic of the MA PDU session may be switched from an untrusted non-3GPP access to a trusted non-3GPP access.
  • SNPN Stand-alone Non-Public Network
  • the UE and the network independently perform registration in the 3GPP access and the non-3GPP access. However, if registration is performed through a different RAT and/or access type in the same 3GPP access or non-3GPP access, the previous registration may be deregistered by the network. For example, if the UE is registered over an untrusted non-3GPP access, when the UE performs registration over a trusted non-3GPP access, since the UE, AMF and UDM manage only one registration on a non-3GPP access, registration over an untrusted non-3GPP access may be deregistered.
  • the present disclosure provides various implementations to solve the above-described problems.
  • the various implementations of the present disclosure to be described below may be performed or applied in combination and/or complement.
  • the various implementations of the present disclosure to be described below are described assuming access switching over non-3GPP accesses, but this is only an example, and various implementations of the present disclosure may be similarly applied to access switching over 3GPP accesses.
  • First implementation A method of managing registration for untrusted non-3GPP access and trusted non-3GPP access respectively in non-3GPP access
  • the UE and the network may manage registration per non-3GPP access type and/or RAT type (i.e., trusted non-3GPP access and untrusted non-3GPP access).
  • RAT type i.e., trusted non-3GPP access and untrusted non-3GPP access.
  • the UE and the network manage only one registration status for 3GPP access and non-3GPP access, respectively.
  • the registration status of the non-3GPP access may be managed and/or supported by being classified per non-3GPP access type and/or per RAT type.
  • the RAT type identifies the transmission technology used in the access network for both 3GPP accesses and non-3GPP accesses, for example, NR, NB-IoT, untrusted non-3GPP, trusted non-3GPP, trusted IEEE 802.11 non-3GPP access, Wireline, Wireline-Cable, etc.
  • the non-3GPP access type and/or the RAT type may be defined separately as an untrusted non-3GPP access and a trusted non-3GPP access, if the registration status is managed by distinguishing the non-3GPP access type and/or the RAT type, a plurality of registrations may be supported simultaneously in the non-3GPP access.
  • the AMF may create and manage the registration status of the UE per RAT type.
  • information about the RAT type may be notified.
  • the UDM may store information about the RAT type together with the access type (e.g., 3GPP access, non-3GPP access).
  • the access type e.g., 3GPP access, non-3GPP access.
  • the AMF transmits information about the RAT type to the UDM, but the AMF does not manage the registration status per RAT type, and the UDM does not manage the registration status per RAT type.
  • the SMF performs registration for a PDU session with the UDM
  • information about the RAT type may be notified together, and the UDM may store it.
  • the SMF or other network node may inform the AMF through which access type and/or which RAT type the NAS signaling should be transmitted when requesting transmission for NAS signaling.
  • Second implementation A method of delaying UDM registration in AMF until non-3GPP access switching is completed
  • the UE and the network may temporarily allow registration for untrusted non-3GPP access and trusted non-3GPP access.
  • the UE and the network may operate as follows.
  • the SMF may indicate to the UE whether non-3GPP access switching is supported. Based on this indication, the UE may determine to change non-3GPP access from an untrusted non-3GPP access to a trusted non-3GPP access. Whether and when to switch non-3GPP access may be determined by the UE. If the UE determines to switch access, the UE performs registration over the new non-3GPP access (i.e., trusted non-3GPP access) with new registration type to indicate the registration is for switching non-3GPP access.
  • the new non-3GPP access i.e., trusted non-3GPP access
  • the AMF follows normal registration procedure, but does not perform UDM registration.
  • the UE sends PDU Session Establishment Request message to add new non-3GPP access (i.e., trusted non-3GPP access) to the existing MA PDU session.
  • new non-3GPP access i.e., trusted non-3GPP access
  • the UE and UPF starts sending traffic over the new non-3GPP access (i.e., trusted non-3GPP access) and stops sending traffic over the old non-3GPP access (i.e., untrusted non-3GPP access).
  • the AMF triggers AN release procedure over the old non-3GPP access (i.e., untrusted non-3GPP access) and performs UDM registration.
  • FIG. 13 shows an example of a method performed by a UE to which implementations of the present disclosure is applied.
  • step S 1300 the method includes performing a first registration procedure over a first non-3GPP access.
  • step S1310 the method includes establishing a MA PDU session over the first non-3GPP access.
  • step S1320 the method includes transmitting a registration request message of a second registration procedure to an AMF over a second non-3GPP access.
  • the registration request message includes information related to access switching from the first non-3GPP access to the second non-3GPP access. At this time, registration over the first non-3GPP access is maintained.
  • the first non-3GPP access or the second non-3GPP access may be any one of an untrusted non-3GPP access, a trusted non-3GPP access, or a wireline access.
  • the first non-3GPP access may be an untrusted non-3GPP access and the second non-3GPP access may be a trusted non-3GPP access.
  • the first non-3GPP access may be a trusted non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access.
  • both the first non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access or a trusted non-3GPP access.
  • the method may further comprise performing a registration procedure over a 3GPP access before performing the access switching.
  • establishing the MA PDU session may comprise receiving, from the SMF, information about whether the access switching in a non-3GPP access is supported. Based on the received information about whether the access switching in a non-3GPP access is supported, the method may further comprise determining the access switching from the first non-3GPP access to the second non-3GPP access.
  • the information related to the access switching may be a registration type set to "non-3GPP access switching registration" and/or "temporary registration".
  • the UE may perform a newly defined type of registration.
  • the information related to the access switching may be a registration type set to "mobility registration update" that is not used in a non-3GPP access.
  • the information related to the access switching may be a new indicator in the registration request message.
  • the UE may use the conventional registration type as it is.
  • step S1330 the method includes receiving a registration accept message from the AMF in response to the registration request message.
  • step S1340 the method includes transmitting a PDU session establishment request message to a SMF over the second non-3GPP access.
  • the PDU session establishment request message includes information about the MA PDU session.
  • the information about the MA PDU session may include at least one of a request type set to "MA PDU Request" in the PDU session establishment request message or a PDU session Identifier (ID) of the MA PDU session.
  • step S1350 the method includes receiving a PDU session establishment accept message from the SMF in response to the PDU session establishment request message.
  • step S1360 the method includes receiving, from the AMF, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • the UE may communicate with at least one of a mobile device, a network and/or an autonomous vehicle other than the UE.
  • the method in perspective of the UE described above in FIG. 13 may be performed by the first wireless device 100 shown in FIG. 2 , the wireless device 100 shown in FIG. 3 , and/or the UE 100 shown in FIG. 4 .
  • the UE comprises at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor.
  • the at least one memory stores instructions to cause the at least one processor to perform following operations.
  • the UE performs a first registration procedure over a first non-3GPP access.
  • the UE establishes a MA PDU session over the first non-3GPP access.
  • the UE transmits a registration request message of a second registration procedure to an AMF over a second non-3GPP access.
  • the registration request message includes information related to access switching from the first non-3GPP access to the second non-3GPP access. At this time, registration over the first non-3GPP access is maintained.
  • the first non-3GPP access or the second non-3GPP access may be any one of an untrusted non-3GPP access, a trusted non-3GPP access, or a wireline access.
  • the first non-3GPP access may be an untrusted non-3GPP access and the second non-3GPP access may be a trusted non-3GPP access.
  • the first non-3GPP access may be a trusted non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access.
  • both the first non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access or a trusted non-3GPP access.
  • the UE may perform a registration procedure over a 3GPP access before performing the access switching.
  • establishing the MA PDU session may comprise receiving, from the SMF, information about whether the access switching in a non-3GPP access is supported. Based on the received information about whether the access switching in a non-3GPP access is supported, the UE may determine the access switching from the first non-3GPP access to the second non-3GPP access.
  • the information related to the access switching may be a registration type set to "non-3GPP access switching registration" and/or "temporary registration".
  • the UE may perform a newly defined type of registration.
  • the information related to the access switching may be a registration type set to "mobility registration update" that is not used in a non-3GPP access.
  • the information related to the access switching may be a new indicator in the registration request message.
  • the UE may use the conventional registration type as it is.
  • the UE receives a registration accept message from the AMF in response to the registration request message.
  • the UE transmits a PDU session establishment request message to a SMF over the second non-3GPP access.
  • the PDU session establishment request message includes information about the MA PDU session.
  • the information about the MA PDU session may include at least one of a request type set to "MA PDU Request" in the PDU session establishment request message or a PDU session ID of the MA PDU session.
  • the UE receives a PDU session establishment accept message from the SMF in response to the PDU session establishment request message.
  • the UE receives, from the AMF, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • the method in perspective of the UE described above in FIG. 13 may be performed by control of the processor 102 included in the first wireless device 100 shown in FIG. 2 , by control of the communication unit 110 and/or the control unit 120 included in the wireless device 100 shown in FIG. 3 , and/or by control of the processor 102 included in the UE 100 shown in FIG. 4 .
  • a processing apparatus adapted to control a UE in a wireless communication system comprises at least one processor, and at least one memory operably connectable to the at least one processor.
  • the at least one processor is adapted to perform following operations comprising: performing a first registration procedure over a first non-3GPP access, establishing a MA PDU session over the first non-3GPP access, transmitting a registration request message of a second registration procedure including information related to access switching from the first non-3GPP access to the second non-3GPP access to an AMF over a second non-3GPP access, receiving a registration accept message from the AMF in response to the registration request message, transmitting a PDU session establishment request message including information about the MA PDU session to a SMF over the second non-3GPP access, receiving a PDU session establishment accept message from the SMF in response to the PDU session establishment request message, and receiving, from the AMF, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • the method in perspective of the UE described above in FIG. 13 may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2 .
  • a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof.
  • a software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.
  • storage medium may be coupled to the processor such that the processor can read information from the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the processor and the storage medium may reside as discrete components.
  • the computer-readable medium may include a tangible and non-transitory computer-readable storage medium.
  • non-transitory computer-readable media may include RAM such as synchronous dynamic random access memory (SDRAM), ROM, non-volatile random access memory (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures.
  • RAM such as synchronous dynamic random access memory (SDRAM), ROM, non-volatile random access memory (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures.
  • RAM such as synchronous dynamic random access memory (SDRAM), ROM, non-volatile random access memory (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures.
  • NVRAM non-volatile random access memory
  • EEPROM electrically erasable programmable read-only memory
  • the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer.
  • a non-transitory computer-readable medium has stored thereon a plurality of instructions.
  • CRM stores instructions to cause at least one processor to perform following operations comprising: performing a first registration procedure over a first non-3GPP access, establishing a MA PDU session over the first non-3GPP access, transmitting a registration request message of a second registration procedure including information related to access switching from the first non-3GPP access to the second non-3GPP access to an AMF over a second non-3GPP access, receiving a registration accept message from the AMF in response to the registration request message, transmitting a PDU session establishment request message including information about the MA PDU session to a SMF over the second non-3GPP access, receiving a PDU session establishment accept message from the SMF in response to the PDU session establishment request message, and receiving, from the AMF, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • FIG. 14 shows an example of a method performed by an AMF to which implementations of the present disclosure is applied.
  • step S1400 the method includes performing a first registration procedure for a UE over a first non-3GPP access.
  • step S 1400 the method includes receiving a registration request message of a second registration procedure from the UE over a second non-3GPP access.
  • the registration request message includes information related to access switching from the first non-3GPP access to the second non-3GPP access.
  • the first non-3GPP access or the second non-3GPP access may be any one of an untrusted non-3GPP access, a trusted non-3GPP access, or a wireline access.
  • the first non-3GPP access may be an untrusted non-3GPP access and the second non-3GPP access may be a trusted non-3GPP access.
  • the first non-3GPP access may be a trusted non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access.
  • both the first non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access or a trusted non-3GPP access.
  • the method may further comprise performing a registration procedure for the UE over a 3GPP access before performing the access switching.
  • the information related to the access switching may be a registration type set to "non-3GPP access switching registration" and/or "temporary registration".
  • the UE may perform a newly defined type of registration.
  • the information related to the access switching may be a registration type set to "mobility registration update" that is not used in a non-3GPP access.
  • the information related to the access switching may be a new indicator in the registration request message.
  • the UE may use the conventional registration type as it is.
  • the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access. For example, if the information related to the access switching is a registration type set to "non-3GPP access switching registration" and/or "temporary registration", the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access. For example, if the information related to the access switching is a registration type set to "mobility registration update" that is not used in the non-3GPP access, the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access. For example, if the information related to the access switching is a new indicator in the registration request message, the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access.
  • the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access based on the UE context it has.
  • the method may further comprise, based on a comparison of a UE context stored in the AMF for the first non-3GPP access and a UE context for the second non-3GPP access, determining the access switching from the first non-3GPP access to the second non-3GPP access. That is, by storing a new UE context (i.e., a current non-3GPP access type) that does not previously exist when the UE performs registration, and comparing the stored UE context with the UE context in the access where the new registration request was received, the AMF may recognize that the new registration request is for switching from the first non-3GPP access to the second non-3GPP access.
  • a new UE context i.e., a current non-3GPP access type
  • the UE context may include at least one of User Location Information (ULI), a global N3IWF ID, or a global TNGF ID.
  • ULI User Location Information
  • N3IWF ID a global N3IWF ID
  • TNGF ID a global TNGF ID
  • the ULI may be updated as soon as signaling is received.
  • the AMF may not recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access.
  • Table 3 shows an example of ULI.
  • N3IWF user location information >>IP Address M Transport Layer Address 9.3.2.4 UE's local IP address used to reach the N3IWF - >>Port Number O OCTET STRING (SIZE(2)) UDP or TCP source port number if NAT is detected.
  • - >TNGF user location information YES ignore >>TNAP ID M OCTET STRING TNAP Identifier used to identify the TNAP. Details in TS 29.571 [35].
  • - IP Address M Transport Layer UE's local IP address used - Address 9.3.2.4 to reach the TNGF.
  • TWIF user location information YES ignore >>TWAP ID M OCTET STRING TWAP Identifier used to identify the TWAP. Details in TS 29.571 [35]. - >>IP Address M Transport Layer Address 9.3.2.4 Non-5G-Capable over WLAN device's local IP address used to reach the TWIF. - >>Port Number O OCTET STRING (SIZE(2)) UDP or TCP source port number if NAT is detected. - > W-AGF user location information Indicates the location information via wireline access as specified in TS 23.316 [34]. YES ignore >>W-AGF user location information M 9.3.1.164 -
  • step S 1420 the method includes, based on the registration request message, i) performing a normal registration procedure, and ii) delaying a UDM registration procedure. That is, when the UE performs registration for the access switching in a non-3GPP access, the AMF performs registration of a new second non-3GPP access switching while maintaining the previous registration of the first non-3GPP access switching. At this time, registration to UDM is not performed and is delayed.
  • the method may further comprise, before the access switching from the first non-3GPP access to the second non-3GPP access is completed, based on a network node that requests signaling related to a non-3GPP access not requesting to transmit over the second non-3GPP access, transmitting the signaling related to the non-3GPP access over the first non-3GPP access. That is, if the network node requesting signaling does not request to send signaling over the new second non-3GPP access, the AMF may transmit all signaling to be transmitted over the non-3GPP access to the previous first non-3GPP access.
  • step S 1430 the method includes transmitting a registration accept message to the UE in response to the registration request message.
  • step S1440 the method includes receiving, from a SMF, information informing that the access switching from the first non-3GPP access to the second non-3GPP access is completed for the UE.
  • the SMF may inform the AMF that the access switching from the first non-3GPP access to the second non-3GPP access is completed. Accordingly, the AMF may know that the access switching in the non-3GPP access has been completed.
  • the UE may notify the completion of the access switching from the first non-3GPP access to the second non-3GPP access to the AMF by performing registration or through a separate procedure. For example, the UE may add and transmit information, while performing registration, indicating that the access switching from the first non-3GPP access to the second non-3GPP access is completed to the AMF and/or may define a new registration type informing this.
  • step S 1450 the method includes performing an AN release procedure over the first non-3GPP access.
  • step S 1460 the method includes performing the delayed UDM registration procedure.
  • step S1470 the method includes transmitting, to the UE, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • the method may further comprise, after the access switching from the first non-3GPP access to the second non-3GPP access is completed, notifying another network node (e.g., PCF) that RAT type information of the UE has changed.
  • another network node e.g., PCF
  • the method may further comprise, after the access switching from the first non-3GPP access to the second non-3GPP access is completed, deleting a UE context related to the first non-3GPP access.
  • the method may further comprise, after the access switching from the first non-3GPP access to the second non-3GPP access is completed, transmitting signaling related to a non-3GPP access over the second non-3GPP access.
  • the method in perspective of the AMF described above in FIG. 14 may be performed by the second wireless device 200 shown in FIG. 2 and/or the wireless device 200 shown in FIG. 3 .
  • the AMF comprises at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor.
  • the at least one memory stores instructions to cause the at least one processor to perform following operations.
  • the AMF performs a first registration procedure for a UE over a first non-3GPP access.
  • the AMF receives a registration request message of a second registration procedure from the UE over a second non-3GPP access.
  • the registration request message includes information related to access switching from the first non-3GPP access to the second non-3GPP access.
  • the first non-3GPP access or the second non-3GPP access may be any one of an untrusted non-3GPP access, a trusted non-3GPP access, or a wireline access.
  • the first non-3GPP access may be an untrusted non-3GPP access and the second non-3GPP access may be a trusted non-3GPP access.
  • the first non-3GPP access may be a trusted non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access.
  • both the first non-3GPP access and the second non-3GPP access may be an untrusted non-3GPP access or a trusted non-3GPP access.
  • the AMF may perform a registration procedure for the UE over a 3GPP access before performing the access switching.
  • the information related to the access switching may be a registration type set to "non-3GPP access switching registration" and/or "temporary registration".
  • the UE may perform a newly defined type of registration.
  • the information related to the access switching may be a registration type set to "mobility registration update" that is not used in a non-3GPP access.
  • the information related to the access switching may be a new indicator in the registration request message.
  • the UE may use the conventional registration type as it is.
  • the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access. For example, if the information related to the access switching is a registration type set to "non-3GPP access switching registration" and/or "temporary registration", the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access. For example, if the information related to the access switching is a registration type set to "mobility registration update" that is not used in the non-3GPP access, the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access. For example, if the information related to the access switching is a new indicator in the registration request message, the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access.
  • the AMF may recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access based on the UE context it has.
  • the AMF may further determine the access switching from the first non-3GPP access to the second non-3GPP access. That is, by storing a new UE context (i.e., a current non-3GPP access type) that does not previously exist when the UE performs registration, and comparing the stored UE context with the UE context in the access where the new registration request was received, the AMF may recognize that the new registration request is for switching from the first non-3GPP access to the second non-3GPP access.
  • a new UE context i.e., a current non-3GPP access type
  • the UE context may include at least one of ULI, a global N3IWF ID, or a global TNGF ID.
  • ULI is included and transmitted whenever signaling is transmitted from the AN to the AMF and has a different format, so the AMF may know over which non-3GPP access the UE has previously accessed based on the ULI.
  • the new registration request also includes the ULI, by comparing the previously transmitted ULI with the ULI in the new registration request, the AMF may recognize that the new registration request is for switching from the first non-3GPP access to the second non-3GPP access.
  • the ULI may be updated as soon as signaling is received.
  • the AMF may not recognize that the UE performs registration for switching from the first non-3GPP access to the second non-3GPP access.
  • the AMF i) performs a normal registration procedure, and ii) delays a UDM registration procedure. That is, when the UE performs registration for the access switching in a non-3GPP access, the AMF performs registration of a new second non-3GPP access switching while maintaining the previous registration of the first non-3GPP access switching. At this time, registration to UDM is not performed and is delayed.
  • the AMF may further transmit the signaling related to the non-3GPP access over the first non-3GPP access. That is, if the network node requesting signaling does not request to send signaling over the new second non-3GPP access, the AMF may transmit all signaling to be transmitted over the non-3GPP access to the previous first non-3GPP access.
  • the AMF transmits a registration accept message to the UE in response to the registration request message.
  • the AMF receives, from a SMF, information informing that the access switching from the first non-3GPP access to the second non-3GPP access is completed for the UE.
  • the SMF may inform the AMF that the access switching from the first non-3GPP access to the second non-3GPP access is completed. Accordingly, the AMF may know that the access switching in the non-3GPP access has been completed.
  • the UE may notify the completion of the access switching from the first non-3GPP access to the second non-3GPP access to the AMF by performing registration or through a separate procedure. For example, the UE may add and transmit information, while performing registration, indicating that the access switching from the first non-3GPP access to the second non-3GPP access is completed to the AMF and/or may define a new registration type informing this.
  • the AMF performs an AN release procedure over the first non-3GPP access.
  • the AMF performs the delayed UDM registration procedure.
  • the AMF transmits, to the UE, a deregistration request message informing that the UE is deregistered over the first non-3GPP access.
  • the AMF may further notify another network node (e.g., PCF) that RAT type information of the UE has changed.
  • PCF another network node
  • the AMF may further delete a UE context related to the first non-3GPP access.
  • the AMF may further transmit signaling related to a non-3GPP access over the second non-3GPP access.
  • FIG. 15 shows an example of a procedure for switching from an untrusted non-3GPP access to a trusted non-3GPP access to which implementations of the present disclosure is applied.
  • the present disclosure may have various advantageous effects.
  • the UE can support service continuity by supporting access addition for the MA PDU session between different types of non-3GPP accesses.
  • the UE finds a new non-3GPP access, by supporting access switching between non-3GPP accesses, traffic using the MA PDU session can be transmitted smoothly.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
EP22200098.6A 2022-01-24 2022-10-06 Procédé d'enregistrement de réseau pour orientation de trafic et dispositif le prenant en charge Pending EP4216622A3 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR20220010144 2022-01-24

Publications (2)

Publication Number Publication Date
EP4216622A2 true EP4216622A2 (fr) 2023-07-26
EP4216622A3 EP4216622A3 (fr) 2023-10-11

Family

ID=83688631

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22200098.6A Pending EP4216622A3 (fr) 2022-01-24 2022-10-06 Procédé d'enregistrement de réseau pour orientation de trafic et dispositif le prenant en charge

Country Status (3)

Country Link
US (1) US20230239828A1 (fr)
EP (1) EP4216622A3 (fr)
KR (1) KR20230114172A (fr)

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102314865B1 (ko) * 2017-03-16 2021-10-19 삼성전자 주식회사 단말이 Temporary User ID(임시 사용자 식별자)를 이용해 5G 네트워크에 등록하는 방안
MX2019011294A (es) * 2017-04-27 2019-12-05 Lg Electronics Inc Metodo para realizar un procedimiento relacionado con el registro de amf por udm en un sistema de comunicacion inalambrico y dispositivo para el mismo.
JP6959695B2 (ja) * 2017-08-11 2021-11-05 アイディーエーシー ホールディングス インコーポレイテッド 複数のアクセスネットワークの間でのトラフィックステアリングおよび切り替え
CN114868435B (zh) * 2019-08-22 2023-12-26 欧芬诺有限责任公司 针对多址接入的策略控制

Also Published As

Publication number Publication date
KR20230114172A (ko) 2023-08-01
EP4216622A3 (fr) 2023-10-11
US20230239828A1 (en) 2023-07-27

Similar Documents

Publication Publication Date Title
US20240172179A1 (en) Paging Time Adjustment in a Wireless Network
CN114503536B (zh) 与应用服务器的改变有关的通信
US11716122B2 (en) Beam management enhancement for FR2 with V-Pol/H-Pol virtualization
US11490351B2 (en) Efficient PLMN selection upon authentication failure for each network slice in roaming network
US12041526B2 (en) Layer 2 UE to UE data forwarding
US20230199632A1 (en) Access to Second Network
CN112219428A (zh) 用于无线通信系统中用户设备的策略管理的设备和方法
CN114143871B (zh) 网络连接方法、网络去连接方法及通信装置
CN114557031B (zh) 用于将非3gpp上的pdu会话移动到3gpp接入的方法
EP4181589A1 (fr) Procédé pour permettre une continuité de service lorsqu'une situation de catastrophe est terminée, et dispositif prenant en charge celui-ci
EP4322691A1 (fr) Procédé de gestion de sessions pdu
US20230189192A1 (en) Access to Second Network by Wireless Device
US20230136425A1 (en) N14 interface support indicator for service continuity
US20220322152A1 (en) Method for measuring performance for qos
EP4224930A1 (fr) Support de continuité de service pour une session pdu à routage domestique lorsqu'il n'y a pas d'interface n14 entre un réseau source et un réseau cible
US20220311478A1 (en) Uplink multiple input multiple output enhancements for fr2 with v-pol/h-pol virtualization
EP4216622A2 (fr) Procédé d'enregistrement de réseau pour orientation de trafic et dispositif le prenant en charge
EP4443949A1 (fr) Procédé de mesure d'utilisation de trafic
CN118844091A (zh) 用于业务传输的网络注册方法和支持该方法的设备
US20220312278A1 (en) Interruption and measurement exception with smtc2-lp in idle and inactive rrm
KR20240109885A (ko) 이동 무선통신 시스템에서 단말 정책을 제공하기 위한 방법 및 장치
CN116567768A (zh) 一种确定用户设备路由选择策略的方法和装置
CN118542002A (zh) 无线通信方法、装置、设备、存储介质及程序产品

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20221006

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/06 20090101ALN20230906BHEP

Ipc: H04W 36/14 20090101ALN20230906BHEP

Ipc: H04W 60/00 20090101AFI20230906BHEP