[go: up one dir, main page]

WO2022169223A1 - Communication associée à une pluralité d'usim - Google Patents

Communication associée à une pluralité d'usim Download PDF

Info

Publication number
WO2022169223A1
WO2022169223A1 PCT/KR2022/001584 KR2022001584W WO2022169223A1 WO 2022169223 A1 WO2022169223 A1 WO 2022169223A1 KR 2022001584 W KR2022001584 W KR 2022001584W WO 2022169223 A1 WO2022169223 A1 WO 2022169223A1
Authority
WO
WIPO (PCT)
Prior art keywords
amf
message
information
request message
paging
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2022/001584
Other languages
English (en)
Korean (ko)
Inventor
윤명준
김래영
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2022169223A1 publication Critical patent/WO2022169223A1/fr
Anticipated expiration legal-status Critical
Ceased 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
    • 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/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • 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

  • This specification relates to mobile communication.
  • 3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology that enables high-speed packet communications. Many initiatives have been proposed for LTE goals, including those aimed at reducing user and provider costs, improving service quality, and expanding and improving coverage and system capacity. 3GPP LTE requires lower cost per bit, improved service availability, flexible use of frequency bands, simple structure, open interface, and appropriate power consumption of the terminal as upper-level requirements.
  • 3GPP is a timely and successful new Radio Access Technology (RAT) that meets both urgent market needs and long-term requirements set out in the International Mobile Telecommunications (ITU-R) international mobile telecommunications (IMT)-2020 process.
  • RAT Radio Access Technology
  • ITU-R International Mobile Telecommunications
  • IMT international mobile telecommunications
  • the technical components needed to standardize should be identified and developed.
  • NR must be able to use a spectral band in the range of at least 100 GHz that can be used for wireless communications in the far future.
  • NR aims to be a single technology framework that covers all usage scenarios, requirements and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), and more. do. NR may be forward compatible in nature.
  • eMBB enhanced mobile broadband
  • mMTC massive machine-type-communications
  • URLLC ultra-reliable and low latency communications
  • NR may be forward compatible in nature.
  • 3GPP 3rd Generation Partnership Project
  • 4G network / 5G network it is basically assumed that one UE has one Universal Subscriber Identity Module (USIM).
  • USIM Universal Subscriber Identity Module
  • UEs supporting dual or multi USIM have been released.
  • UEs supporting multiple USIMs are mainstream.
  • the UE may transmit a NAS message including a leave indication to the AMF of SIM A. Then, the AMF initiates a connection release procedure (eg, an AN release procedure). Since the AMF does not know which PDU sessions are active, unnecessary signaling such as requesting deactivation of all PDU sessions of the UE may occur.
  • MUSIM multi USIM
  • connection release procedure when the AMF performs connection release, the terminal context and resource of the base station are released first, and then the resource of the core network is released. In this case, data is continuously transmitted in the core network, but there is a problem in that the base station discards data because there is no terminal context and resources. In this case, since the charging for the UE is determined based on the data transmitted from the UPF, there may be a problem in that charging occurs even for discarded data.
  • the UE may request a paging restriction requesting paging only for a specific service while requesting leaving.
  • the RAN may perform an operation related to paging restriction.
  • data is transmitted from the core network to the RAN, and there may be a problem in that the RAN discards the data according to the paging restriction. Even in this case, the same billing problem as before may occur.
  • an object of the present disclosure is to propose a method for solving the above-described problems.
  • one disclosure of the present specification provides a method for AMF to perform communication related to a plurality of USIMs.
  • the method includes: receiving a release request message including information related to leaving of the UE from the UE; transmitting, to the RAN node, an N2 message to inform that the UE is leaving, based on the reception of information related to the UE's leaving; receiving a UE context release request message including a list of activated PDU sessions from the RAN node; and transmitting a request message requesting to deactivate the PDU session to the SMF.
  • the AMF includes at least one processor; and at least one memory that stores instructions and is operably electrically connectable with the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: receiving a release request message including information related to leaving from the UE; transmitting, to the RAN node, an N2 message to inform that the UE is leaving, based on the reception of information related to the UE's leaving; receiving a UE context release request message including a list of activated PDU sessions from the RAN node; and transmitting a request message requesting to deactivate the PDU session to the SMF.
  • the apparatus includes at least one processor; and at least one memory that stores instructions and is operably electrically connectable with the at least one processor, wherein the operations performed based on the instructions being executed by the at least one processor include: identifying a release request message containing information related to leaving ; generating an N2 message for notifying that the UE is leaving, based on receiving information related to leaving of the UE; receiving a UE context release request message including a list of activated PDU sessions from the RAN node; and generating a request message requesting to deactivate the PDU session.
  • one disclosure of the present specification provides a non-transitory computer-readable storage medium recording instructions.
  • the instructions when executed by one or more processors, cause the one or more processors to: identify a release request message including information related to leaving the UE; generating an N2 message for notifying that the UE is leaving, based on receiving information related to leaving of the UE; receiving a UE context release request message including a list of activated PDU sessions from the RAN node; and generating a request message requesting to deactivate the PDU session.
  • FIG. 1 shows an example of a communication system to which an implementation of the present specification is applied.
  • FIG. 2 shows an example of a wireless device to which the implementation of the present specification is applied.
  • FIG 3 shows an example of a wireless device to which the implementation of the present specification is applied.
  • FIG 4 shows an example of a network node to which the implementation of the present specification is applied.
  • 5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.
  • FIG. 6 is another exemplary diagram showing the structure of a radio interface protocol (Radio Interface Protocol) between the UE and the gNB.
  • Radio Interface Protocol Radio Interface Protocol
  • 7A and 7B are signal flow diagrams illustrating an exemplary registration procedure.
  • 8A and 8B are signal flow diagrams illustrating an exemplary PDU session establishment procedure.
  • 11 is an example showing the overall procedure of the AN Release procedure.
  • 13A to 13C show a first example to which a fourth example of the disclosure of the present specification is applied.
  • 14A to 14D show a second example to which a fourth example of the disclosure of the present specification is applied.
  • FIG 16 shows an example of the operation of the operation of the AMF according to the disclosure of the present specification.
  • the multiple access system examples include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a system, a single SC-FDMA (single) system. It includes a carrier frequency division multiple access) system, and a multicarrier frequency division multiple access (MC-FDMA) system.
  • CDMA may be implemented over a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • TDMA may be implemented through a 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 implemented through a wireless 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 WiMAX
  • IEEE 802.20 IEEE 802.20
  • E-UTRA evolved UTRA
  • UTRA is part of the universal mobile telecommunications system (UMTS).
  • 3GPP (3rd generation partnership project) LTE (long-term evolution) is a part of E-UMTS (evolved UMTS) using E-UTRA.
  • 3GPP LTE uses OFDMA in downlink (DL) and SC-FDMA in uplink (UL).
  • Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G NR (new radio).
  • the implementation of the present specification is mainly described in the context of a 3GPP-based wireless communication system.
  • the technical characteristics of the present specification are not limited thereto.
  • the following detailed description is provided based on a mobile communication system corresponding to the 3GPP-based wireless communication system, but aspects of the present specification that are not limited to the 3GPP-based wireless communication system may be applied to other mobile communication systems.
  • a or B (A or B) may mean “only A”, “only B” or “both A and B”.
  • a or B (A or B)” may be interpreted as “A and/or B (A and/or B)”.
  • A, B or C(A, B or C) herein means “only A”, “only B”, “only C”, or “any and any combination of A, B and C ( any combination of A, B and C)”.
  • a slash (/) or a comma (comma) used herein may mean “and/or”.
  • A/B may mean “A and/or B”. Accordingly, “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” means “A and can be construed the same as “at least one of A and B”.
  • “at least one of A, B and C” means “only A”, “only B”, “only C”, or “A, B and C” 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” means may mean “at least one of A, B and C”.
  • parentheses used herein may mean “for example”. Specifically, when displayed as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” in the present specification is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of “control information”. Also, even when displayed as “control information (ie, PDCCH)”, “PDCCH” may be proposed as an example of “control information”.
  • UE user equipment
  • ME mobile equipment
  • the illustrated UE may be referred to as a terminal, mobile equipment (ME), and the like.
  • the UE may be a portable device such as a notebook computer, a mobile phone, a PDA, a smart phone, a multimedia device, or the like, or a non-portable device such as a PC or an in-vehicle device.
  • the UE is used as an example of a wireless communication device (or a wireless device, or a wireless device) capable of wireless communication.
  • An operation performed by the UE may be performed by a wireless communication device.
  • a wireless communication device may also be referred to as a wireless device, a wireless device, or the like.
  • AMF may mean an AMF node
  • SMF may mean an SMF node
  • UPF may mean a UPF node.
  • a base station generally refers to a fixed station that communicates with a wireless device, and an evolved-NodeB (eNodeB), an evolved-NodeB (eNB), a BTS (Base Transceiver System), an access point ( Access Point), it may be called other terms such as gNB (Next generation NodeB).
  • eNodeB evolved-NodeB
  • eNB evolved-NodeB
  • BTS Base Transceiver System
  • Access Point Access Point
  • gNB Next generation NodeB
  • FIG. 1 shows an example of a communication system to which an implementation of the present specification is applied.
  • the 5G usage scenario shown in FIG. 1 is only an example, and the technical features of the present specification may be applied to other 5G usage scenarios not shown in FIG. 1 .
  • the three main requirements categories for 5G are (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable, low-latency communication. (URLLC; ultra-reliable and low latency communications) category.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra-reliable, low-latency communications
  • Partial use cases may require multiple categories for optimization, while other use cases may focus on only one key performance indicator (KPI).
  • KPI key performance indicator
  • eMBB goes far beyond basic mobile Internet access and covers rich interactive work and media and entertainment applications in the cloud and augmented reality.
  • Data is one of the key drivers of 5G, and for the first time in the 5G era, dedicated voice services may not be provided.
  • voice processing will be simplified as an application that utilizes the data connection provided by the communication system.
  • the main reasons for the increase in traffic are the increase in the size of content and the increase in applications that require high data transfer rates.
  • streaming services audio and video
  • video chat video chat
  • mobile Internet access will become more prevalent.
  • Many of these applications require an always-on connection to push real-time information and alerts for users.
  • Cloud storage and applications are rapidly increasing in mobile communication platforms and can be applied to both work and entertainment.
  • Cloud storage is a special use case that accelerates the increase in uplink data transfer rates.
  • 5G is also used for remote work in the cloud. When using tactile interfaces, 5G requires much lower end-to-end latency to maintain a good user experience.
  • entertainment such as cloud gaming and video streaming is another key factor driving demand for mobile broadband capabilities.
  • Smartphones and tablets are essential for entertainment in all places, including in highly mobile environments such as trains, vehicles, and airplanes.
  • Another use example is augmented reality for entertainment and information retrieval. In this case, augmented reality requires very low latency and instantaneous data volumes.
  • one of the most anticipated 5G use cases relates to the ability to seamlessly connect embedded sensors in all fields, namely mMTC.
  • mMTC Internet-of-things
  • Industrial IoT is one of the key roles enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure through 5G.
  • URLLC includes ultra-reliable, low-latency links such as autonomous vehicles and new services that will change the industry through remote control of the main infrastructure. Reliability and latency are essential to controlling smart grids, automating industries, achieving robotics, and controlling and coordinating drones.
  • 5G is a means of delivering streaming rated at hundreds of megabits per second at gigabit per second, and can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such high speed is required to deliver TVs with resolutions above 4K (6K, 8K and above), as well as virtual and augmented reality.
  • Virtual reality (VR) and augmented reality (AR) applications include highly immersive sports games. Certain applications may require special network configuration. For VR games, for example, gaming companies should integrate core servers into network operators' edge network servers to minimize latency.
  • Automobiles are expected to be a significant new motivating force in 5G, with many use cases for in-vehicle mobile communications. For example, entertainment for passengers requires broadband mobile communications with high simultaneous capacity and high mobility. This is because future users continue to expect high-quality connections regardless of location and speed.
  • Another use case in the automotive sector is AR dashboards.
  • the AR dashboard allows the driver to identify an object in a dark place other than the one visible from the front window, and displays the distance to the object and the movement of the object by overlapping information transfer to the driver.
  • wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices, such as those accompanied by pedestrians.
  • Safety systems lower the risk of accidents by guiding the driver through alternative courses of action to make driving safer.
  • the next step will be remotely controlled or autonomous vehicles. This requires very high reliability and very fast communication between different autonomous vehicles and between vehicles and infrastructure. In the future, autonomous vehicles will perform all driving activities and drivers will only focus on traffic unless the vehicle can identify them. The technological requirements of autonomous vehicles require ultra-low latency and ultra-high reliability to increase traffic safety to a level that humans cannot achieve.
  • Smart cities and smart homes/buildings will be embedded in high-density wireless sensor networks.
  • a distributed network of intelligent sensors will identify conditions for cost- and energy-efficient maintenance of a city or house.
  • a similar configuration can be performed for each household. All temperature sensors, window and heating controllers, burglar alarms and appliances will be connected wirelessly. Many of these sensors typically have low data rates, power, and cost. However, real-time HD video may be required by certain types of devices for monitoring.
  • the smart grid uses digital information and communication technology to collect information and connect sensors to operate according to the collected information. Since this information can include the behavior of suppliers and consumers, smart grids can improve the distribution of fuels such as electricity in ways such as efficiency, reliability, economics, production sustainability, automation and more.
  • the smart grid can also be considered as another low-latency sensor network.
  • Mission-critical applications are one of the 5G usage scenarios.
  • the health section contains many applications that can benefit from mobile communications.
  • the communication system may support telemedicine providing clinical care from a remote location. Telemedicine can help reduce barriers to distance and improve access to health care services that are not consistently available in remote rural areas. Telemedicine is also used in emergency situations to perform critical care and save lives.
  • a wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
  • Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. The possibility of replacing cables with reconfigurable radio links is therefore an attractive opportunity for many industries.
  • a wireless connection with similar latency, reliability and capacity as a cable must be established, and the management of the wireless connection needs to be simplified.
  • 5G connection When a 5G connection is required, low latency and very low error probability are new requirements.
  • Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable inventory and package tracking from anywhere.
  • Logistics and freight applications typically require low data rates, but location information with a wide range and reliability.
  • a communication system 1 includes wireless devices 100a to 100f , a base station (BS) 200 , and a network 300 .
  • BS base station
  • 1 illustrates a 5G network as an example of a network of the communication system 1, the implementation of the present specification is not limited to the 5G system, and may be applied to future communication systems beyond the 5G system.
  • Base station 200 and network 300 may be implemented as wireless devices, and certain wireless devices may act as base station/network nodes in relation to other wireless devices.
  • the wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (eg, 5G NR or LTE), and may also be referred to as a communication/wireless/5G device.
  • RAT radio access technology
  • the wireless devices 100a to 100f are not limited thereto, and the robot 100a, the vehicles 100b-1 and 100b-2, the extended reality (XR) device 100c, the portable device 100d, and home appliances are not limited thereto.
  • It may include a product 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400 .
  • a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication.
  • Vehicles may include unmanned aerial vehicles (UAVs) (eg drones).
  • XR devices may include AR/VR/mixed reality (MR) devices, and may include head-mounted devices (HMDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, and the like. mounted device) or HUD (head-up display).
  • Portable devices may include smartphones, smart pads, wearable devices (eg, smart watches or smart glasses), and computers (eg, laptops).
  • Home appliances may include TVs, refrigerators, and washing machines.
  • IoT devices may include sensors and smart meters.
  • the wireless devices 100a to 100f may be referred to as user equipment (UE).
  • the UE is, for example, a mobile phone, a smartphone, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, an autonomous driving function.
  • the UAV may be an aircraft that does not have a person on board and is navigated by a radio control signal.
  • the VR device may include a device for realizing an object or a background of a virtual environment.
  • the AR device may include a device implemented by connecting an object or background in a virtual world to an object or background in the real world.
  • the MR apparatus may include a device implemented by merging the background of an object or virtual world with the background of the object or the real world.
  • the hologram device may include a device for realizing a 360-degree stereoscopic image by recording and reproducing stereoscopic information using an interference phenomenon of light generated when two laser lights called a hologram meet.
  • the public safety device may include an image relay device or an image device that can be worn on a user's body.
  • MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation.
  • MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.
  • a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease.
  • a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or injury.
  • a medical device may be a device used for the purpose of examining, replacing, or modifying structure or function.
  • the medical device may be a device used for pregnancy control purposes.
  • a medical device may include a device for treatment, a device for driving, an (ex vivo) diagnostic device, a hearing aid, or a device for a procedure.
  • a security device may be a device installed to prevent a risk that may occur and to maintain safety.
  • the security device may be a camera, closed circuit television (CCTV), recorder or black box.
  • the fintech device may be a device capable of providing financial services such as mobile payment.
  • a fintech device may include a payment device or a POS system.
  • the weather/environment device may include a device for monitoring or predicting the weather/environment.
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 200 .
  • 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 through the network 300 .
  • the network 300 may be configured using a 3G network, a 4G (eg, LTE) network, a 5G (eg, NR) network, and a 5G or later network.
  • the wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but communicate directly without passing through the base station 200/network 300 (eg, sidelink communication). You may.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (eg, vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication).
  • the IoT device eg, a sensor
  • the IoT device may directly communicate with another IoT device (eg, a sensor) or other wireless devices (100a to 100f).
  • Wireless communications/connections 150a , 150b , 150c may be established between the wireless devices 100a - 100f and/or between the wireless devices 100a - 100f and the base station 200 and/or between the base station 200 .
  • the wireless communication/connection includes uplink/downlink communication 150a, sidelink communication 150b (or device-to-device (D2D) communication), inter-base station communication 150c (eg, relay, integrated access and backhaul), etc.), and may be established through various RATs (eg, 5G NR).
  • the wireless devices 100a to 100f and the base station 200 may transmit/receive wireless signals to each other through the wireless communication/connections 150a, 150b, and 150c.
  • the wireless communication/connection 150a, 150b, 150c may transmit/receive signals through various physical channels.
  • various configuration information setting processes for transmission/reception of radio signals various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and at least a part of a resource allocation process and the like may be performed.
  • AI refers to a field that studies artificial intelligence or methodologies that can make it
  • machine learning refers to a field that defines various problems dealt with in the field of artificial intelligence and studies methodologies to solve them.
  • Machine learning is also defined as an algorithm that improves the performance of a certain task through continuous experience.
  • a robot can mean a machine that automatically handles or operates a task given by its own capabilities.
  • a robot having a function of recognizing an environment and performing an operation by self-judgment may be referred to as an intelligent robot.
  • Robots can be classified into industrial, medical, home, military, etc. depending on the purpose or field of use.
  • the robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving the robot joints.
  • the movable robot includes a wheel, a brake, a propeller, and the like in the driving unit, and can travel on the ground or fly in the air through the driving unit.
  • Autonomous driving refers to a technology that drives itself, and an autonomous driving vehicle refers to a vehicle that runs without or with minimal user manipulation.
  • autonomous driving includes technology that maintains a driving lane, technology that automatically adjusts speed such as adaptive cruise control, technology that automatically drives along a predetermined route, and technology that automatically sets a route when a destination is set. Technology, etc. may all be included.
  • the vehicle includes a vehicle having only an internal combustion engine, a hybrid vehicle having both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include not only automobiles, but also trains, motorcycles, and the like.
  • Autonomous vehicles can be viewed as robots with autonomous driving capabilities.
  • Expanded reality refers to VR, AR, and MR.
  • VR technology provides only CG images of objects or backgrounds in the real world
  • AR technology provides virtual CG images on top of real objects
  • MR technology provides CG by mixing and combining virtual objects with the real world.
  • technology MR technology is similar to AR technology in that it shows both real and virtual objects.
  • AR technology virtual objects are used in a form that complements real objects
  • MR technology virtual objects and real objects are used with equal characteristics.
  • NR supports multiple numerology or subcarrier spacing (SCS) to support various 5G services. For example, when SCS is 15 kHz, it supports wide area in traditional cellular band, and when SCS is 30 kHz/60 kHz, dense-urban, lower latency and wider area are supported. It supports a wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.
  • SCS subcarrier spacing
  • the NR frequency band may be defined as two types of frequency ranges (FR1, FR2).
  • the numerical value of the frequency range is subject to change.
  • the frequency ranges of the two types (FR1, FR2) may be as shown in Table 1 below.
  • FR1 may mean "sub 6GHz range”
  • FR2 may mean “above 6GHz range”
  • mmW millimeter wave
  • FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include an unlicensed band. The unlicensed band can be used for a variety of purposes, for example, for communication for vehicles (eg, autonomous driving).
  • the wireless communication technology implemented in the wireless device of the present specification may include narrowband IoT (NB-IoT, narrowband IoT) for low-power communication as well as LTE, NR, and 6G.
  • NB-IoT narrowband IoT
  • the NB-IoT technology may be an example of a low power wide area network (LPWAN) technology, and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is not limited to the above-described name.
  • LPWAN low power wide area network
  • the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology.
  • the LTE-M technology may be an example of an LPWAN technology, and may be called by various names such as enhanced MTC (eMTC).
  • eMTC enhanced MTC
  • LTE-M technology is 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC , and/or 7) may be implemented in at least one of various standards such as LTE M, and is not limited to the above-described name.
  • the wireless communication technology implemented in the wireless device of the present specification may include at least one of ZigBee, Bluetooth, and/or LPWAN in consideration of low-power communication, and limited to the above-mentioned names it is not
  • the ZigBee technology can create PAN (personal area networks) related to small/low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.
  • FIG. 2 shows an example of a wireless device to which the implementation of the present specification is applied.
  • the first wireless device 100 and the second wireless device 200 may transmit/receive radio signals to/from an external device through various RATs (eg, LTE and NR).
  • various RATs eg, LTE and NR.
  • ⁇ first wireless device 100 and second wireless device 200 ⁇ are ⁇ radio devices 100a to 100f and base station 200 ⁇ in FIG. 1, ⁇ wireless device 100a to 100f ) and wireless devices 100a to 100f ⁇ and/or ⁇ base station 200 and base station 200 ⁇ .
  • 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 .
  • Processing chip 101 may include at least one processor, such as processor 102 , and at least one memory, such as memory 104 .
  • the memory 104 is exemplarily shown to be included in the processing chip 101 . Additionally and/or alternatively, the memory 104 may be located external to the processing chip 101 .
  • the processor 102 may control the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information/signal, and transmit a wireless signal including the first information/signal through the transceiver 106 . The processor 102 may receive a wireless signal including the second information/signal through the transceiver 106 , and store information obtained by processing the second information/signal in the memory 104 .
  • Memory 104 may be operatively coupled to processor 102 .
  • Memory 104 may store various types of information and/or instructions.
  • the memory 104 may store software code 105 that, when executed by the processor 102 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • the software code 105 may implement instructions that, when executed by the processor 102 , perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • software code 105 may control processor 102 to perform one or more protocols.
  • software code 105 may control processor 102 to perform one or more air interface protocol layers.
  • the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR).
  • the transceiver 106 may be coupled to the processor 102 to transmit and/or receive wireless signals via one or more antennas 108 .
  • Each transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be used interchangeably with a radio frequency (RF) unit.
  • 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 .
  • Processing chip 201 may include at least one processor, such as processor 202 , and at least one memory, such as memory 204 .
  • the memory 204 is exemplarily shown included in the processing chip 201 . Additionally and/or alternatively, the memory 204 may be located external to the processing chip 201 .
  • the processor 202 may control the memory 204 and/or the transceiver 206 , and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information/signal, and transmit a wireless signal including the third information/signal through the transceiver 206 . The processor 202 may receive a wireless signal including the fourth information/signal through the transceiver 206 , and store information obtained by processing the fourth information/signal in the memory 204 .
  • Memory 204 may be operatively coupled to processor 202 .
  • Memory 204 may store various types of information and/or instructions.
  • the memory 204 may store software code 205 that, when executed by the processor 202 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • the software code 205 may implement instructions that, when executed by the processor 202 , perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • software code 205 may control processor 202 to perform one or more protocols.
  • software code 205 may control processor 202 to perform one or more air interface protocol layers.
  • the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR).
  • the transceiver 206 may be coupled to the processor 202 to transmit and/or receive wireless signals via one or more antennas 208 .
  • Each transceiver 206 may include a transmitter and/or a receiver.
  • the transceiver 206 may be used interchangeably with the RF unit.
  • the second wireless device 200 may represent a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102 , 202 .
  • the one or more processors 102, 202 may include one or more layers (eg, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, A functional layer such as a radio resource control (RRC) layer and a service data adaptation protocol (SDAP) layer) may be implemented.
  • layers eg, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, A functional layer such as a radio resource control (RRC) layer and a 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, 202 may be configured to perform one or more protocol data units (PDUs or packet data units) and/or one or more service data units (SDUs) according to the descriptions, functions, procedures, proposals, methods and/or operational flow diagrams disclosed herein. unit) can be created.
  • One or more processors 102 , 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein.
  • the one or more processors 102, 202 may be configured to provide PDUs, SDUs, messages, control information, data or signals including information (eg, baseband signal) and provide it to one or more transceivers 106 , 206 .
  • One or more processors 102 , 202 may receive signals (eg, baseband signals) from one or more transceivers 106 , 206 , and may be described, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein.
  • PDU, SDU, message, control information, data or information may be acquired according to
  • One or more processors 102 , 202 may be referred to as controllers, microcontrollers, microprocessors, and/or microcomputers.
  • One or more processors 102 , 202 may be implemented by hardware, firmware, software, and/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 gates
  • the descriptions, functions, procedures, suggestions, methods, and/or flow diagrams disclosed herein may be implemented using firmware and/or software, and the firmware and/or software may be implemented to include modules, procedures, functions. .
  • Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein may be included in one or more processors 102 , 202 , or stored in one or more memories 104 , 204 . It may be driven by the above processors 102 and 202 .
  • the descriptions, functions, procedures, suggestions, methods, and/or flow diagrams disclosed herein may be implemented using firmware or software in the form of code, instructions, and/or a collection of instructions.
  • One or more memories 104 , 204 may be coupled to one or more processors 102 , 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and/or instructions.
  • the one or more memories 104 and 204 may include read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer readable storage media and/or these may be composed of a combination of One or more memories 104 , 204 may be located inside and/or external to one or more processors 102 , 202 .
  • one or more memories 104 , 204 may be coupled to one or more processors 102 , 202 through various technologies, such as wired or wireless connections.
  • the one or more transceivers 106, 206 may transmit user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein to one or more other devices. .
  • the one or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods and/or flow charts disclosed herein, from one or more other devices. have.
  • one or more transceivers 106 , 206 may be coupled to one or more processors 102 , 202 and may transmit and receive wireless signals.
  • one or more processors 102 , 202 may control one or more transceivers 106 , 206 to transmit user data, control information, wireless signals, etc. to one or more other devices.
  • one or more processors 102 , 202 may control one or more transceivers 106 , 206 to receive user data, control information, radio signals, and the like from one or more other devices.
  • One or more transceivers 106 , 206 may be coupled to one or more antennas 108 , 208 .
  • One or more transceivers 106, 206 may be connected via one or more antennas 108, 208 to user data, control information, radio signals/channels referred to in the descriptions, functions, procedures, proposals, methods and/or operational flow diagrams disclosed herein. It may be set to transmit and receive, etc.
  • the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers are configured to process received user data, control information, radio signals/channels, etc., using one or more processors (102, 202), such as received user data, control information, radio signals/channels, and the like. etc. can be converted from an RF band signal to a baseband signal.
  • One or more transceivers 106 and 206 may convert user data, control information, radio signals/channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals.
  • one or more transceivers 106 , 206 may include (analog) oscillators and/or filters.
  • one or more transceivers 106, 206 may up-convert OFDM baseband signals to OFDM signals via (analog) oscillators and/or filters under the control of one or more processors 102, 202; , an up-converted OFDM signal may be transmitted at a carrier frequency.
  • One or more transceivers 106, 206 receive the OFDM signal at the carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through an (analog) oscillator and/or filter under the control of one or more processors 102, 202. can be down-converted.
  • the UE may operate as a transmitting device in an uplink (UL) and a receiving device in a downlink (DL).
  • the base station may operate as a receiving device in the UL and a transmitting device in the DL.
  • a processor 102 coupled to, mounted on, or shipped to the first wireless device 100 may perform a UE operation according to an implementation of the present disclosure or may configure the transceiver 106 to perform a UE operation according to an implementation of the present disclosure.
  • a processor 202 coupled, mounted, or shipped to the second wireless device 200 is configured to perform a base station operation according to an implementation of the present specification or to control the transceiver 206 to perform a base station operation according to an implementation of the present specification. can be
  • a base station may be referred to as a Node B (Node B), an eNode B (eNB), or a gNB.
  • Node B Node B
  • eNB eNode B
  • gNB gNode B
  • FIG 3 shows an example of a wireless device to which the implementation of the present specification is applied.
  • the wireless device may be implemented in various forms according to usage examples/services (refer to FIG. 1 ).
  • the wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 , and may be configured by various components, devices/parts and/or modules.
  • each wireless device 100 , 200 may include a communication device 110 , a control device 120 , a memory device 130 , and an additional component 140 .
  • the communication device 110 may include communication circuitry 112 and a transceiver 114 .
  • communication circuitry 112 may include one or more processors 102 , 202 of FIG. 2 and/or one or more memories 104 , 204 of FIG. 2 .
  • transceiver 114 may include one or more transceivers 106 , 206 of FIG.
  • the control device 120 is electrically connected to the communication device 110 , the memory device 130 , and the additional component 140 , and controls the overall operation of each wireless device 100 , 200 .
  • the control device 120 may control the electrical/mechanical operation of each of the wireless devices 100 and 200 based on the program/code/command/information stored in the memory device 130 .
  • the control device 120 transmits the information stored in the memory device 130 to the outside (eg, other communication devices) through the communication device 110 through the wireless/wired interface, or the communication device ( 110), information received from the outside (eg, other communication devices) may be stored in the memory device 130 .
  • the additional component 140 may be variously configured according to the type of the wireless device 100 or 200 .
  • the additional component 140 may include at least one of a power unit/battery, an input/output (I/O) device (eg, an audio I/O port, a video I/O port), a drive unit, and a computing device.
  • I/O input/output
  • Wireless devices 100 and 200 include, but are not limited to, robots (100a in FIG. 1 ), vehicles ( 100b-1 and 100b-2 in FIG. 1 ), XR devices ( 100c in FIG. 1 ), and portable devices ( FIG. 1 ). 100d), home appliances (100e in FIG. 1), IoT devices (100f in FIG.
  • the wireless devices 100 and 200 may be used in a moving or fixed location according to usage examples/services.
  • all of the various components, devices/parts and/or modules of the wireless devices 100 and 200 may be connected to each other via a wired interface, or at least some of them may be wirelessly connected via the communication device 110 .
  • the control device 120 and the communication device 110 are connected by wire, and the control device 120 and the first device (eg, 130 and 140 ) are communication devices. It may be connected wirelessly through 110 .
  • Each component, device/portion and/or module within the wireless device 100, 200 may further include one or more elements.
  • the control device 120 may be configured by one or more processor sets.
  • control device 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphic processing device, and a memory control processor.
  • AP application processor
  • ECU electronice control unit
  • the memory device 130 may be configured by RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and/or a combination thereof.
  • UE's shows an example.
  • the UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the wireless device 100 or 200 of FIG. 3 .
  • UE 100 includes processor 102 , memory 104 , transceiver 106 , one or more antennas 108 , power management module 110 , battery 112 , display 114 , keypad 116 , SIM a (subscriber identification module) card 118 , a speaker 120 , and a microphone 122 .
  • the processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • the processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein.
  • a layer of air interface protocol may be implemented in the processor 102 .
  • the processor 102 may include an ASIC, other chipset, logic circuitry, 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), and a modem (modulator and demodulator).
  • DSP digital signal processor
  • CPU central processing unit
  • GPU graphics processing unit
  • modem modulator and demodulator
  • Examples of the processor 102 include SNAPDRAGONTM series processors made by Qualcomm®, EXYNOSTM series processors made by Samsung®, A series processors made by Apple®, HELIOTM series processors made by MediaTek®, ATOMTM series processors made by Intel®, or a corresponding next-generation processor. It can be found in the processor.
  • the memory 104 is operatively coupled to the processor 102 , and stores various information for operating the processor 102 .
  • Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and/or other storage devices.
  • modules eg, procedures, functions, etc.
  • Modules may be stored in memory 104 and executed by processor 102 .
  • the memory 104 may be implemented within the processor 102 or external to the processor 102 , in which case it may be communicatively coupled with the processor 102 through various methods known in the art.
  • the transceiver 106 is operatively coupled with the processor 102 and transmits and/or receives wireless signals.
  • the transceiver 106 includes a transmitter and a receiver.
  • the transceiver 106 may include baseband circuitry for processing radio frequency signals.
  • the transceiver 106 controls one or more antennas 108 to transmit and/or receive wireless signals.
  • the power management module 110 manages power of the processor 102 and/or the transceiver 106 .
  • the battery 112 supplies power to the power management module 110 .
  • the display 114 outputs the result processed by the processor 102 .
  • Keypad 116 receives input for use by processor 102 .
  • the keypad 116 may be displayed on the display 114 .
  • SIM card 118 is an integrated circuit for securely storing an international mobile subscriber identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone or computer. You can also store contact information on many SIM cards.
  • IMSI international mobile subscriber identity
  • the speaker 120 outputs sound related results processed by the processor 102 .
  • Microphone 122 receives sound related input for use by processor 102 .
  • the 5G system (5GS; 5G system) structure consists of the following network functions (NFs).
  • Data Network e.g. operator services, internet access or third-party services
  • 5 shows the 5G system structure of a non-roaming case using a reference point representation that shows how various network functions interact with each other.
  • UDSF, NEF and NRF are not described for the sake of clarity of the point-to-point plot. However, all network functions shown can interact with UDSF, UDR, NEF and NRF as needed.
  • connection between UDRs and other NFs is not shown in FIG. 5 .
  • connection between NWDAF and other NFs is not shown in FIG. 5 .
  • the 5G system architecture includes the following reference points.
  • - N1 the reference point between the UE and the AMF.
  • the reference point between the PCF and the AMF in the roaming scenario, indicates the reference point between the AMF and the PCF of the visited network.
  • AF by a third party other than an operator may be connected to 5GC through NEF.
  • the air interface protocol is based on the 3GPP radio access network standard.
  • the air interface protocol is horizontally composed of a physical layer, a data link layer, and a network layer, and vertically a user plane for data information transmission and control. It is divided into a control plane for signal transmission.
  • the protocol layers are L1 (first layer), L2 (second layer), and L3 (third layer) based on the lower three layers of the open system interconnection (OSI) reference model widely known in communication systems. ) can be distinguished.
  • OSI open system interconnection
  • the first layer provides an information transfer service using a physical channel.
  • the physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. And, data is transferred between different physical layers, that is, between the physical layers of the transmitting side and the receiving side through a physical channel.
  • the second layer includes a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer.
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the third layer includes radio resource control (hereinafter abbreviated as RRC).
  • RRC radio resource control
  • the RRC layer is defined only in the control plane, and is related to the establishment (establishment), re-establishment (Re-establishment) and release (Release) of radio bearers (Radio Bearer; abbreviated as RB) of logical channels, transport channels and physical channels. responsible for control In this case, the RB means a service provided by the second layer for data transfer between the UE and the E-UTRAN.
  • the NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management (Mobility Management).
  • the NAS layer is divided into a NAS entity for MM (Mobility Management) and a NAS entity for SM (session management).
  • the NAS entity for MM provides the following general functions.
  • NAS procedures related to AMF including the following.
  • AMF supports the following functions.
  • the NAS entity for SM performs session management between the UE and the SMF.
  • the SM signaling message is processed, ie, generated and processed in the NAS-SM layer of the UE and SMF.
  • the content of the SM signaling message is not interpreted by the AMF.
  • the NAS entity for MM creates a NAS-MM message that derives how and where to forward the SM signaling message with a security header indicating the NAS transmission of the SM signaling, additional information about the receiving NAS-MM.
  • the NAS entity for the SM Upon receiving the SM signaling, the NAS entity for the SM performs an integrity check of the NAS-MM message and interprets the additional information to derive a method and a place to derive the SM signaling message.
  • the RRC layer, the RLC layer, the MAC layer, and the PHY layer located below the NAS layer are collectively referred to as an access layer (Access Stratum: AS).
  • a network system (ie, 5GC) for next-generation mobile communication (ie, 5G) also supports non-3GPP access.
  • An example of the non-3GPP access is typically a WLAN access.
  • the WLAN access may include both a trusted WLAN and an untrusted WLAN.
  • AMF performs registration management (RM: Registration Management) and connection management (CM: Connection Management) for 3GPP access as well as non-3GPP access.
  • RM Registration Management
  • CM Connection Management
  • a Multi-Access (MA) PDU session using both 3GPP access and non-3GPP access may be used.
  • the MA PDU session is a PDU session that can be serviced simultaneously with 3GPP access and non-3GPP access using one PDU session.
  • the UE needs to obtain an authorization to enable mobility tracking and to receive data, and to receive services. For this, the UE must register with the network.
  • the registration procedure is performed when the UE needs to do initial registration with the 5G system.
  • the registration procedure is performed when the UE performs periodic registration update, when moving from an idle mode to a new tracking area (TA), and when the UE needs to perform periodic registration update.
  • TA new tracking area
  • the ID of the UE may be obtained from the UE.
  • AMF can pass PEI (IMEISV) to UDM, SMF and PCF.
  • PEI IMEISV
  • 7A and 7B are signal flow diagrams illustrating an exemplary registration procedure.
  • the UE may send an AN message to the RAN.
  • the AN message may include an AN parameter and a registration request message.
  • the registration request message includes information such as registration type, subscriber permanent ID or temporary user ID, security parameters, Network Slice Selection Assistance Information (NSSAI), 5G capability of the UE, protocol data unit or packet data unit (PDU) session state, etc. can do.
  • NSSAI Network Slice Selection Assistance Information
  • 5G capability of the UE protocol data unit or packet data unit (PDU) session state, etc. can do.
  • the AN parameters may include a Subscription Permanent Identifier (SUPI) or a temporary user ID, a selected network, and an NSSAI.
  • SUPI Subscription Permanent Identifier
  • NSSAI Network Access Management Function
  • the registration type is "initial registration” (i.e. the UE is in a non-registered state), "Mobility registration update” (i.e. the UE is in a registered state and initiates the registration procedure due to mobility) or "Regular registration update” ( That is, the UE is in the registered state and starts the registration procedure due to the expiration of the periodic update timer).
  • the temporary user ID indicates the last serving AMF. If the UE is already registered through non-3GPP access in a PLMN different from the PLMN of 3GPP access, the UE may not provide the temporary ID of the UE assigned by AMF during registration procedure through non-3GPP access.
  • Security parameters can be used for authentication and integrity protection.
  • the PDU session state may indicate a (previously established) PDU session usable in the UE.
  • the RAN may select an AMF based on (R)AT and NSSAI.
  • the (R)AN cannot select an appropriate AMF, it selects an arbitrary AMF according to a local policy, and transmits a registration request to the selected AMF. If the selected AMF cannot service the UE, the selected AMF selects another more suitable AMF for the UE.
  • the RAN transmits an N2 message to the new AMF.
  • the N2 message includes an N2 parameter and a registration request.
  • the registration request may include registration type, subscriber permanent identifier or temporary user ID, security parameters, NSSAI and MICO mode default settings, and the like.
  • the N2 parameters include location information related to the cell the UE is camping on, cell identifier and RAT type.
  • steps 4 to 17 to be described later may not be performed.
  • the newly selected AMF may transmit an information request message to the previous AMF.
  • the new AMF may send an information request message containing the complete registration request information to the old AMF to request the SUPI and MM context of the UE. have.
  • the previous AMF transmits an information response message to the newly selected AMF.
  • the information response message may include SUPI, MM context, and SMF information.
  • the previous AMF sends an information response message including the UE's SUPI and MM context.
  • the previous AMF may include SMF information including the ID of the SMF and the PDU session ID in the information response message.
  • the new AMF sends an Identity Request message to the UE if the SUPI is not provided by the UE or retrieved from the previous AMF.
  • the UE transmits an Identity Response message including the SUPI to the new AMF.
  • the AMF may decide to trigger the AUSF.
  • the AMF may select the AUSF based on the SUPI.
  • AUSF may initiate authentication of UE and NAS security functions.
  • the new AMF may transmit an information response message to the previous AMF.
  • the new AMF may transmit the information response message to confirm delivery of the UE MM context.
  • the new AMF may transmit an Identity Request message to the UE.
  • an Identity Request message may be sent for the AMF to retrieve the PEI.
  • the new AMF checks the ME identifier.
  • step 14 to be described later the new AMF selects a UDM based on SUPI.
  • the new AMF starts the Update Location procedure. .
  • it may be started when the UDM starts canceling the location for the previous AMF (Cancel Location).
  • the old AMF discards the MM context and notifies all possible SMF(s), and the new AMF creates the MM context for the UE after obtaining the AMF related subscription data from the UDM.
  • the AMF When network slicing is used, the AMF obtains the allowed NSSAI based on the requested NSSAI, UE subscription and local policy. Reroute registration requests if AMF is not eligible to support allowed NSSAI.
  • the new AMF may select a PCF based on SUPI.
  • the new AMF transmits a UE Context Establishment Request message to the PCF.
  • the AMF may request an operator policy for the UE from the PCF.
  • the PCF transmits a UE Context Establishment Acknowledged message to the new AMF.
  • the new AMF transmits an N11 request message to the SMF.
  • the new AMF when the AMF is changed, notifies each SMF of the new AMF serving the UE.
  • the AMF verifies the PDU session state from the UE with the available SMF information.
  • available SMF information may be received from the previous AMF.
  • the new AMF may request the SMF to release the network resources associated with the PDU session not activated at the UE.
  • the new AMF transmits an N11 response message to the SMF.
  • the previous AMF transmits a UE Context Termination Request message to the PCF.
  • the old AMF may delete the UE context in the PCF.
  • the PCF may transmit a UE Context Termination Request message to the previous AMF.
  • the new AMF sends a registration accept message to the UE.
  • the registration acceptance message may include temporary user ID, registration area, mobility restriction, PDU session status, NSSAI, regular registration update timer, and allowed MICO mode.
  • the registration accept message may include information of the allowed NSSAI and the mapped NSSAI.
  • the allowed NSSAI information for the access type of the UE may be included in the N2 message including the registration accept message.
  • the information of the mapped NSSAI is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI configured for the Home Public Land Mobile Network (HPLMN).
  • the temporary user ID may be further included in the registration acceptance message.
  • information indicating the mobility restriction may be additionally included in the registration accept message.
  • the AMF may include information indicating the PDU session state for the UE in the registration accept message.
  • the UE may remove any internal resources associated with a PDU session not marked as active in the received PDU session state. If the PDU session state information is in the Registration Request, the AMF may include information indicating the PDU session state to the UE in the registration accept message.
  • the UE transmits a registration complete message to the new AMF.
  • PDU Packet Data Unit or Protocol Data Unit
  • PDU session establishment procedure two types of PDU session establishment procedures may exist as follows.
  • the network may send a device trigger message to the application(s) of the UE.
  • 8A and 8B are exemplary PDU It is a signal flow diagram showing the session establishment procedure.
  • the procedure shown in FIGS. 8A and 8B assumes that the UE has already registered on the AMF according to the registration procedure shown in FIGS. 7A and 7B . Therefore, it is assumed that the AMF has already obtained the user subscription data from the UDM.
  • the UE sends a NAS message to the AMF.
  • the message may include Session Network Slice Selection Assistance Information (S-NSSAI), DNN, PDU session ID, request type, N1 SM information, and the like.
  • S-NSSAI Session Network Slice Selection Assistance Information
  • the UE includes the S-NSSAI from the allowed NSSAI of the current access type. If information on the mapped NSSAI is provided to the UE, the UE may provide both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information of the mapped NSSAI.
  • the mapped NSSAI information is information that maps each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI configured for HPLMN.
  • the UE extracts and stores the information of the allowed S-NSSAI and the mapped S-NSSAI included in the registration accept message received from the network (ie, AMF) in the registration procedure of FIGS. 7A and 7B. may be doing Accordingly, the UE may transmit the PDU session establishment request message by including both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the mapped NSSAI information.
  • the UE may generate a new PDU session ID.
  • the UE may start the PDU session establishment procedure initiated by the UE by sending a NAS message including the PDU session establishment request message in the N1 SM information.
  • the PDU session establishment request message may include a request type, an SSC mode, and a protocol configuration option.
  • the request type indicates "initial request”. However, when there is an existing PDU session between 3GPP access and non-3GPP access, the request type may indicate "existing PDU session”.
  • the NAS message transmitted by the UE is encapsulated in the N2 message by the AN.
  • the N2 message is transmitted to the AMF and may include user location information and access technology type information.
  • - N1 SM information may include an SM PDU DN request container including information on PDU session authentication by external DN.
  • the AMF may determine that the message corresponds to a request for a new PDU session when the message indicates that the request type is "initial request" and the PDU session ID is not used for the existing PDU session of the UE.
  • the AMF may determine the default S-NSSAI for the requested PDU session according to the UE subscription.
  • the AMF may store the PDU session ID and the SMF ID in association.
  • AMF transmits the SM request message to the SMF.
  • the SM request message may include a subscriber permanent ID, DNN, S-NSSAI, PDU session ID, AMF ID, N1 SM information, user location information, and an access technology type.
  • the N1 SM information may include a PDU session ID and a PDU session establishment request message.
  • the AMF ID is used to identify the AMF serving the UE.
  • the N1 SM information may include a PDU session establishment request message received from the UE.
  • SMF transmits subscriber data request message to UDM.
  • the subscriber data request message may include a subscriber permanent ID and DNN.
  • the SMF determines that the request is due to handover between 3GPP access and non-3GPP access.
  • the SMF may identify an existing PDU session based on the PDU session ID.
  • the SMF may request the subscription data.
  • the UDM may send a subscription data response message to the SMF.
  • the subscription data may include information about an authenticated request type, an authenticated SSC mode, and a basic QoS profile.
  • the SMF may check whether the UE request complies with user subscription and local policies. Alternatively, the SMF rejects the UE request through NAS SM signaling (including the relevant SM rejection cause) delivered by the AMF, and the SMF informs the AMF that the PDU session ID should be considered as released.
  • NAS SM signaling including the relevant SM rejection cause
  • SMF sends a message to DN through UPF.
  • the SMF selects the UPF and triggers the PDU.
  • the SMF terminates the PDU session establishment procedure and notifies the UE of rejection.
  • SMF may initiate PDU-CAN session establishment towards PCF to obtain basic PCC rules for PDU session. If the request type in step 3 indicates "existing PDU session", the PCF may start modifying the PDU-CAN session instead.
  • step 3 If the request type in step 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If step 5 is not performed, SMF can also select UPF. In case of the request type IPv4 or IPv6, the SMF may allocate an IP address/prefix for the PDU session.
  • the SMF may start the PDU-CAN session initiation.
  • the SMF may start the N4 session establishment procedure using the selected UPF, otherwise the N4 session modification procedure may start using the selected UPF.
  • the SMF transmits an N4 session establishment/modification request message to the UPF.
  • the SMF may provide packet detection, enforcement and reporting rules to be installed in the UPF for the PDU session.
  • the SMF is allocated CN tunnel information, the CN tunnel information may be provided to the UPF.
  • the UPF may respond by sending an N4 session establishment/modification response message.
  • the CN tunnel information may be provided to the SMF.
  • the SMF transmits an SM response message to the AMF.
  • the message may include a cause, N2 SM information, and N1 SM information.
  • the N2 SM information may include a PDU session ID, QoS profile, and CN tunnel information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the PDU session establishment acceptance message may include an allowed QoS rule, SSC mode, S-NSSAI, and an assigned IPv4 address.
  • the N2 SM information is information that the AMF needs to deliver to the RAN, and may include the following.
  • PDU Session ID This may be used to indicate to the UE the association between the PDU session and AN resources for the UE by AN signaling to the UE.
  • the N1 SM information includes a PDU session acceptance message that the AMF should provide to the UE.
  • Multiple QoS rules may be included in N1 SM information and N2 SM information in the PDU session establishment accept message.
  • the SM response message also contains the PDU Session ID and information allowing the AMF to determine which access should be used for the UE as well as which target UE.
  • the AMF transmits an N2 PDU session request message to the RAN.
  • the message may include N2 SM information and a NAS message.
  • the NAS message may include a PDU session ID and a PDU session establishment acceptance message.
  • the AMF may transmit a NAS message including a PDU session ID and a PDU session establishment acceptance message.
  • the AMF transmits the received N2 SM information from the SMF to the RAN by including it in the N2 PDU session request message.
  • the RAN may do a specific signaling exchange with the UE related to the information received from the SMF.
  • the RAN also allocates RAN N3 tunnel information for the PDU session.
  • the RAN delivers the NAS message provided in step 10 to the UE.
  • the NAS message may include a PDU session ID and N1 SM information.
  • the N1 SM information may include a PDU session establishment acceptance message.
  • the RAN sends the NAS message to the UE only when the necessary RAN resources are established and the allocation of the RAN tunnel information is successful.
  • the RAN transmits an N2 PDU session response message to the AMF.
  • the message may include a PDU session ID, cause, and N2 SM information.
  • the N2 SM information may include a PDU session ID, (AN) tunnel information, and a list of allowed/rejected QoS profiles.
  • the RAN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.
  • the AMF may transmit the SM request message to the SMF.
  • the SM request message may include N2 SM information.
  • the AMF may be to transfer the N2 SM information received from the RAN to the SMF.
  • the SMF may start the N4 session establishment procedure together with the UPF. Otherwise, the SMF may use the UPF to initiate the N4 session modification procedure.
  • the SMF may provide AN tunnel information and CN tunnel information.
  • the CN tunnel information may be provided only when the SMF selects the CN tunnel information in step 8.
  • the UPF may transmit an N4 session establishment/modification response message to the SMF.
  • the SMF may transmit the SM response message to the AMF. After this process, the AMF can deliver the related event to the SMF. Occurs during handover when RAN tunnel information is changed or AMF is relocated.
  • SMF transmits information to UE through UPF. Specifically, in the case of PDU Type IPv6, the SMF may generate an IPv6 Router Advertisement and transmit it to the UE through N4 and UPF.
  • the SMF will send the user through source access (3GPP or non-3GPP access). release the plane
  • the SMF may call "UDM_Register UE serving NF service" including the SMF address and DNN.
  • the UDM may store the ID, address and associated DNN of the SMF.
  • the SMF informs the AMF.
  • the 3GPP system may support a terminal (eg, ME, UE) including a plurality of simultaneously registered USIMs.
  • a terminal eg, ME, UE
  • a plurality of Universal Subscriber Identity Modules may be included in the same Universal Integrated Circuit Card (UICC) or may be included in different UICCs.
  • UICC Universal Integrated Circuit Card
  • the operation of the terminal related to simultaneous handling of a plurality of USIMs may vary according to the capability of the terminal.
  • the function of the terminal may mean, for example, a terminal capable of single Rx (reception)/single Tx (transmission), a terminal capable of dual Rx/single Tx, or a terminal capable of dual Rx/dual Tx.
  • Dual Rx may enable Multiple USIM UE (MUSIM UE) to simultaneously receive traffic from two networks (eg, a network corresponding to each of two USIMs included in the MUSIM UE).
  • Dual Tx may enable the MUSIM UE to transmit traffic to both networks simultaneously.
  • a single Rx may allow a MUSIM UE to receive traffic from one network at a time.
  • a single Tx may allow a MUSIM UE to send traffic to one network at a time.
  • the MSUM UE may allow the user to set the user's preference for the same service or different services based on multiple USIMs. Multiple USIMs may be provided by the same MNO or different MNOs.
  • a MUSIM UE actively engaged in communication related to one USIM may i) whether to monitor a paging channel related to another registered USIM or ii) a paging request related to another registered USIM. It may be determined whether to present a triggered mobile terminated service to the user.
  • the 3GPP system shall not restrict the use of the USIM of another operator by one operator.
  • the 3GPP system may refer to a communication system supporting communication technologies such as LTE and 5G.
  • the 3GPP system must be able to securely support a MUSIM UE having a plurality of USIMs from the same MNO or different MNOs in the same UE.
  • the 3GPP system may provide an appropriate security mechanism.
  • Each USIM may appear as a separate device in the 3GPP system.
  • Mobile terminated services for the Multi-USIM device may be supported.
  • the 3GPP system may inform the UE of information on the type of traffic that triggered paging as part of the paging procedure. This information can be used to determine whether the user or MUSIM should respond to a mobile terminated call while the UE is engaged in active communication based on another USIM.
  • the granularity of paging information can distinguish the following service categories:
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • SMS Short Message Service
  • USSD Unstructured Supplementary Service Data
  • the 3GPP system may defer active communication. For example, when the UE needs to perform another USIM-related activity, the 3GPP system may postpone active communication.
  • the 3GPP system may resume the deferred communication. For example, if the UE completes another USIM-related activity, the 3GPP system may resume the deferred communication.
  • the 3GPP system should be able to minimize paging collisions for paging related to multiple USIMs in the UE.
  • the paging collision may mean a situation in which paging occurrences related to a plurality of USIMs overlap in time.
  • UEs operating with a single Rx must choose to monitor a single paging channel at a time, which may cause paging to other paging channels to fail.
  • the 3GPP system should provide a mechanism to minimize signaling overhead for services related to multiple USIMs of a MUSIM UE.
  • the 3GPP system should be able to minimize the influence of services related to one USIM on the services related to other USIMs of the MUSIM UE.
  • the 3GPP system provides a means for the MUSIM UE to receive an incoming call related to one USIM and switch over to the incoming call when a call related to another USIM is in progress. can do. This requirement may not apply for passive mode MUSIM UEs.
  • the 3GPP system may enable a MUSIM UE to provide a voice service from one USIM and simultaneously provide a data service from another USIM.
  • the 3GPP system can minimize the influence of a MUSIM UE on an ongoing data service related to one USIM while a user is simultaneously answering a call related to another USIM. This requirement is for passive mode MUSIM UEs. may not apply.
  • the 3GPP system can minimize unnecessary signaling and resource usage for the MUSIM UE operating in the Dual SIM Dual Standby (DSDS) mode.
  • DSDS Dual SIM Dual Standby
  • paging cause can be applied 1) only to requesting UEs or 2) indiscriminately to all UEs. Whether and how (if necessary) the UE distinguishes between paging for non-voice services and paging from legacy Radio Access Network (RAN) nodes is not defined.
  • "voice” may mean MultiMedia Telephony (MMTel) voice (5GS and EPS) and CS domain voice (EPS only).
  • MMTel MultiMedia Telephony
  • EPS CS domain voice
  • the UE may provide the network with support information including information for temporarily limiting/filtering MT (Mobile Terminaing) data in this network while the UE leaves. It is not defined whether the UE can provide information for temporarily limiting/filtering MT data in other situations.
  • MT Mobile Terminaing
  • the Multi-USIM device When the Multi-USIM device receives a paging by Network-A in RRC_Idle mode, and the device decides to accept the paging, the UE may perform an existing procedure (eg, sending a Service Request message).
  • an existing procedure eg, sending a Service Request message
  • the Multi-USIM device When the Multi-USIM device receives the paging by Network-A in RRC_Idle mode, the device decides not to accept the paging, if the UE supports the NAS BUSY indication, the UE sends the NAS BUSY indication to the network through the NAS message can be transmitted
  • Whether the BUSY indication is supported when the UE is in the RRC_Inactive state may vary depending on the RAN decision.
  • the UE Man Machine Interface (MMI) may not require input from the user to determine whether the UE responds to paging or not.
  • EPS Evolved Packet System
  • the UE may initiate a Tracking Area Update (TAU) procedure to the MME of one network to request an international mobile subscriber identity (IMSI) offset.
  • TAU Tracking Area Update
  • IMSI international mobile subscriber identity
  • the UE may provide the IMSI offset to the MME during the TAU procedure.
  • the MME may return the IMSI offset to the UE in TAU acceptance.
  • the MME may provide the UE_ID derived based on the IMSI and the IMSI offset to the RAN.
  • the RAN and the UE may calculate a Paging Frame (PF)/Paging Occasion (PO) using the UE ID as an IMSI.
  • PF Paging Frame
  • PO Paging Occasion
  • - NAS-level leaving MM procedure may be supported for leaving in E-UTRA/EPS connection.
  • the UE may transmit a NAS MM message indicating a leave request to release the RRC-Connected state.
  • the previous support information for temporarily limiting/filtering MT data/signaling processing may be revoke.
  • the UE In the NAS MM message (EPS case) indicating the leave request, the UE provides a leave indication to the CN, and the UE may provide support information to the network in the exit procedure related to MT data/signaling handling.
  • EPS case NAS MM message
  • Support information may include information for temporarily limiting/filtering MT data/signaling processing. This information may be, for example:
  • a terminal having multiple SIMs may receive a service based on another SIM (e.g. SIM B) while receiving a service based on one SIM (e.g. SIM A) (that is, the terminal is in a connected state).
  • the terminal in order for the terminal to receive a service based on another SIM (e.g. SIM B), the terminal performs a leaving procedure for the network of SIM A. That is, the leaving procedure is performed only when the terminal is in the connected state, and when the network receives a signal related to the leaving procedure from the terminal, the network releases the terminal's connection.
  • the network may send the UE to the IDLE state or the RRC_Inactive state.
  • the AMF when the AMF receives the leaving indication from the terminal, the AMF is configured to perform the AN release.
  • the leaving indication is information transmitted by the UE, and may be information indicating that the UE currently leaves the network.
  • the terminal sends a registration request message including capability information (eg, MUSIM-related capability) to the AMF when performing the registration procedure to know whether MUSIM-related features (eg, leaving, busy, paging restriction) can be used. It can be sent to the AMF.
  • capability information eg, MUSIM-related capability
  • MUSIM-related features eg, leaving, busy, paging restriction
  • a detailed operation according to the procedure shown in FIG. 9 may be performed in the same manner as an operation according to the prior art (eg, refer to 3GPP TS 23.502 V16.7.0 Section 3.2.6 AN Release).
  • the AN Release procedure is mainly started in the RAN.
  • the RAN may initiate an AN Release procedure.
  • the inactivity timer may be a timer that expires when there is no data transmission between the RAN and the UE for a predetermined time.
  • the RAN may make the UE into RRC_Idle or RRC_Inactive state.
  • the RAN may transmit the currently activated (ie, activated) PDU Session information in step 1b.
  • the RAN may transmit the N2 UE Context Release Request message including the currently activated PDU session information to the AMF.
  • AMF When AMF receives a message including activated PDU Session information, AMF must first perform steps 5 to 7 before performing step 2. This is to release the network-side resource first so that there is no charging issue. For example, since the AMF performs steps 5 to 7 first, all resources related to the activated PDU session of the UE may be released at the network end. Accordingly, by not transmitting data from the core network end to the RAN, the data is not discarded in the RAN, so an additional charging problem for the UE may not occur.
  • the AMF may perform steps 5 to 7 with each SMF that manages the corresponding PDU session based on the PDU Session ID uploaded by the RAN. After steps 5 to 7 are performed, the AMF may perform the procedure according to steps 2, 3, and 4.
  • the AMF receives the NAS message including the leave indication from the UE, the AN release procedure is started in the AMF rather than the RAN. That is, the AN Release procedure is performed from step 2 in the example of FIG. 9 .
  • the AMF since the AMF does not have information on the currently activated PDU Session, the AMF cannot determine which SMFs to request the user plane resource release (or deactivation). Therefore, in this case, the AMF must request deactivation from the SMFs related to all PDU Sessions of the UE. Therefore, unnecessary signaling for deactivation must be performed even for a PDU Session that has already been deactivated (ie, a PDU Session in which the user plane is not activated).
  • the UE may have both an activated PDU session and a deactivated PDU session, but the AMF does not know information about the currently activated PDU session. Therefore, since the AMF must request deactivation from the SMFs related to all PDU sessions of the UE, unnecessary signaling for deactivation must be performed even for the already deactivated PDU sessions. In addition, the reason why the terminal sends a leave indication may be because the terminal wants a service through another SIM. Therefore, it should be possible to perform the AN Release procedure as quickly as possible. However, due to such unnecessary signaling, the AN Release procedure may take a long time.
  • the terminal may transmit paging restriction information while requesting leaving.
  • the paging restriction may be a function of the terminal requesting paging only for a specific service.
  • the paging restriction information transmitted by the terminal may include information that wants to receive paging only for a specific PDU session / PDN connection.
  • the network eg AMF
  • the network determines whether to perform paging by checking the paging restriction when downlink data to the terminal occurs.
  • the terminal can only request paging for the voice service (eg, by the terminal sending paging restriction information), and in this case, the network does not perform paging to the terminal when downlink data other than the voice service occurs. does not
  • This paging restriction may be applied when the terminal is in Connection Management (CM)-IDLE state or RRC_Inactive state.
  • CM-IDLE Connection Management
  • MME Mobility Management Entity
  • AMF Access Management Function
  • the RAN When the UE is in the RRC_Inactive state, the downlink tunnel is connected to the RAN, so data is directly transmitted from the core network to the RAN, and the RAN can perform paging restriction. However, in this case, when the generated data is data that the UE does not want to paging, the RAN may discard this data. If the RAN discards this data, a charging issue occurs. This is because, after the data is transmitted from the core network to the RAN, the RAN discards the data. Specifically, charging for the terminal is generally determined based on the amount of data actually transmitted from the UPF. If the RAN randomly discards data, the charging record collected in the UPF and the amount of data actually transmitted to the terminal may be different. , overcharge for the terminal may occur.
  • a first example of the disclosure of the present specification describes an example of a method in which a terminal notifies an activated PDU session ID.
  • the first example of the disclosure of the present specification describes an example of an operation of notifying an activated PDU Session ID together when the terminal transmits a leave indication.
  • An example according to the first example of the disclosure of this specification is a NAS message (eg, Service Request message, Registration Request message) transmitted by the terminal while performing the leaving procedure is currently activated (ie, user plane resource is created). It may include a method of including information of PDU Session.
  • NAS message eg, Service Request message, Registration Request message
  • the AMF may perform the AN Release procedure.
  • the AMF may request deactivation from the SMFs managing the activated PDU Session.
  • AMF can transmit a response to the NAS message (e.g. Service Accept message, Registration Accept message) to the UE while performing PDU Session deactivation.
  • the NAS message e.g. Service Accept message, Registration Accept message
  • the AMF sends a UE Context Release Command (eg, step 2 in the example of FIG. 9, step 6 in the example of FIG. 10) to the RAN in order to send the UE to the IDLE state.
  • a UE Context Release Command (eg, step 2 in the example of FIG. 9, step 6 in the example of FIG. 10) to the RAN in order to send the UE to the IDLE state.
  • the AMF may transmit the UE Context Release Command message by including the response to the NAS message in the UE Context Release Command message.
  • the RAN may switch the UE to the IDLE state by performing an RRC Connection Release procedure for the UE.
  • the AMF may not transmit a response to the NAS message transmitted by the terminal.
  • the UE may consider the RRC Connection Release as a response to the NAS message and determine that the leaving procedure has been successfully completed. For example, even if the terminal does not receive a response from the AMF to the NAS message (eg, Service Request message, Registration Request message) sent to perform the leaving procedure, if the RRC Connection Release procedure is performed, the terminal Release can be considered as a response to a NAS message.
  • the NAS message eg, Service Request message, Registration Request message
  • FIG. 10 shows an example of the leaving procedure.
  • do 10 is of the disclosure of this specification in the first example An example of the following leaving procedure is shown.
  • FIG. 10 shows an example of an operation in which the UE transmits a NAS message including an activated PDU session ID.
  • the terminal may transmit a Service Request message or a Registration Request message.
  • the terminal may transmit a Service Request message or a Registration Request message including information on leaving, information for paging restriction, and/or information on activated PDU Session.
  • Information on the activated PDU Session may be interpreted as information requesting to deactivate the activated PDU Session(s).
  • the AMF requests PDU Session deactivation from the SMFs that manage the activated PDU Session by using the information transmitted by the terminal (eg, information on the activated PDU Session).
  • the terminal e.g, information on the activated PDU Session.
  • information for paging restriction can be transmitted to the SMF that needs to transmit the information.
  • the SMF may be a different SMF or the same SMF as the SMF that manages the activated PDU session.
  • SMF may release user plane resource for Downlink by performing N4 Session Modification procedure for UPF.
  • the SMF may inform the AMF that deactivation of the PDU Session has occurred.
  • AMF may transmit a Service Accept message or a Registration Accept message to the terminal while performing steps 2 to 4.
  • the AMF may transmit a UE Context Release Command message to the RAN in order to release the connection to the UE. If the AMF does not perform step 5, the UE Context Release Command message may be transmitted by including Service Accept or Registration Accept in this message (UE Context Release Command message).
  • the RAN may perform an RRC Connection Release procedure for the UE. If the AMF transmits a NAS message (Service Accept or Registration Accept), before performing RRC Connection Release, the RAN may transmit a NAS message to the UE. Alternatively, while transmitting the RRC Release message for RRC Connection Release, the RAN may transmit the RRC Release message by including the NAS message in the RRC Release message.
  • NAS message Service Accept or Registration Accept
  • a second example of the disclosure of the present specification describes an example of a method in which the terminal transmits information related to leave in AN signaling.
  • the second example of the disclosure of the present specification may include an operation in which the terminal notifies information indicating leave through AN signaling when the terminal performs a leaving procedure.
  • An example according to the second example of the disclosure of the present specification may include an operation of including an indication/cause indicating that the terminal is leaving in RRC signaling when the terminal performs a leaving procedure.
  • the RAN may transmit the currently activated PDU Session information to the AMF while transmitting the NAS message transmitted by the UE to the AMF.
  • the AMF may receive the currently activated PDU Session information from the RAN. Based on this (eg, currently activated PDU Session information), the AMF may request deactivation from the SMFs that manage the activated PDU Session. The AMF may transmit a response to the NAS message (e.g. Service Accept message, Registration Accept message) to the UE while performing PDU Session deactivation. After deactivation of all activated PDU Sessions is performed, the AMF may transmit a UE Context Release Command message to the RAN in order to send the UE to the IDLE state.
  • the NAS message e.g. Service Accept message, Registration Accept message
  • the AMF may transmit the UE Context Release Command message by including the response to the NAS in the UE Context Release Command message.
  • the RAN may switch the UE to the IDLE state by performing an RRC Connection Release procedure for the UE.
  • the AMF may not transmit a response to the NAS message transmitted by the terminal.
  • the UE may consider the RRC Connection Release as a response to the NAS message and determine that the leaving procedure has been successfully completed.
  • the AMF does not transmit the UE Context Release to the RAN, and the RAN may immediately perform the RRC Release based on the indication/cause indicating that the UE is leaving included in the AS signaling.
  • a third example of the disclosure of the present specification describes an example of a method in which the AMF directly manages the PDU session activation state.
  • a third example of the disclosure of the present specification includes an operation in which the AMF directly manages the PDU Session activation state.
  • the SMF may perform user plane setup by transmitting an N2 message to the RAN.
  • the SMF may transmit the N2 message to the RAN via the AMF.
  • the AMF since the AMF transmits a PDU Session Resource Setup message at this time, it is possible to know which PDU Session is activated. Also, when the PDU session is deactivated, when the AMF transmits the N2 message received from the SMF to the RAN, the AMF transmits the PDU Session Resource Release, so that the AMF can know that the PDU session is deactivated.
  • the AMF can store activation / deactivation information for the PDU Session as a part of the UE Context.
  • the AMF transmits a NAS message for leaving to the AMF based on the stored activation / deactivation information for the PDU Session, the AMF may request deactivation of the PDU session from the SMFs managing the activated PDU Session. .
  • This operation can be performed only when the terminal raises the capability to support multi sim operation (eg, when the terminal transmits this capability to the AMF). For example, when the terminal transmits an indication / capability indicating that multi sim is supported in the registration process, and the AMF accepts the request of the terminal, the AMF may perform the operation described in the third example of the disclosure of this specification. .
  • a fourth example of the disclosure of the present specification describes an example of a method for solving a charging problem due to a paging restriction.
  • the NG-RAN may transmit an N2 UE context release request message to the AMF. . Then, the AMF may request to release the N3 tunnel by triggering the Nsmf_PDUSession_UpdateSMContext.
  • the AMF may transmit an N2 UE Context Release Command message. If the RRC connection is released first, the NG-RAN must discard all packets received through the N3 tunnel. Since the NG-RAN does not report the number of discarded packets, the network charges the UE based on the packets transmitted in the UPF. At this time, due to the discarded packets in the NG-RAN, the network has a problem of excessively charging the UE. To avoid this problem, the AN Release procedure can be designed to release the N3 tunnel first before releasing the RRC connection, unless there is an error such as Radio Link Failure (RLF).
  • RLF Radio Link Failure
  • 11 is an example showing the overall procedure of the AN Release procedure.
  • a specific operation according to the procedure shown in FIG. 11 may be performed in the same manner as an operation according to the prior art (eg, refer to 3GPP TS 23.502 V16.7.0 Section 3.2.6 AN Release).
  • operations indicated by “AN Release procedure” may be performed in the same manner as steps 2 to 7 of the example of FIG. 9 .
  • the conventional procedure according to FIG. 11 may cause a charging issue. This is because, from step 3 to step 6, all traffic is discarded by the NG-RAN.
  • the fourth example of the disclosure of the present specification proposes a procedure such as the following example of FIG. 12 .
  • step 3 of the example of FIG. 12 may correspond to step 1b of the example of FIG. 9 .
  • step 4 of the example of FIG. 11 may correspond to step 5 of the example of FIG. 9 .
  • Step 5 of the example of FIG. 12 may correspond to steps 6a and 6b of the example of FIG. 9 .
  • Step 6 of the example of FIG. 12 may correspond to step 7 of the example of FIG. 9 .
  • Step 7 of the example of FIG. 12 may correspond to step 2 of the example of FIG. 9 .
  • Step 8 of the example of FIG. 12 may correspond to step 3 of the example of FIG. 9 .
  • Step 9 of the example of FIG. 12 may correspond to step 4 of the example of FIG. 9 .
  • step 2 of FIG. 12 the AMF transmits an N2 message (eg, a UE context modification request message) to inform that the UE is leaving (leaving), and then the NG-RAN can trigger the AN release procedure.
  • N2 message eg, a UE context modification request message
  • the N2 UE Context Release Request in step 3 may include a list of PDU sessions so that the AMF can deactivate the PDU session.
  • AMF may first trigger N3 tunnel release (eg, AMF performs step 4 to step 6 first) and then release the NG-RAN connection (eg, AMF may perform step 7 to step 9) ).
  • N3 tunnel release eg, AMF performs step 4 to step 6 first
  • NG-RAN connection eg, AMF may perform step 7 to step 9 .
  • the NG-RAN may decide to keep the UE in the RRC_Inactive state. In this case, the NG-RAN may not trigger the AN Release procedure.
  • the following operation may be proposed to avoid a charging issue.
  • the AMF may notify the NG-RAN, and the NG-RAN may determine to perform the AN release procedure.
  • a similar problem may occur when the UE is in RRC_Inactive state and paging restriction is enforced by the NG-RAN. For example, if the NG-RAN receives a packet from the UPF and the packet is restricted by a paging restriction, this packet should be discarded by the NG-RAN without interaction with the core network.
  • Observation 3 When the UE is in the RRC_Inactive state, a charging issue may occur if paging restriction is enforced by the NG-RAN.
  • the UPF can enforce the paging restriction when the terminal is in Inactive.
  • the AMF may request the NG-RAN to notify the AMF when the UE enters the RRC_Inactive state by using the N2 Notification procedure. And, when the AMF learns from the NG-RAN that the UE is in the RRC_Inactive state, the AMF may transmit paging restriction information to the SMF. Based on the paging restriction information, the SMF can update the N4 rule so that the UPF can perform the paging restriction. Then, the SMF may transmit the updated N4 rule to the UPF.
  • the AMF again clears the paging restriction for the SMF (eg, the AMF sends a request to stop the paging restriction to the SMF) Should be. Then, by updating the N4 rule for the UPF, the SMF may allow paging to operate normally. In this case, there is a problem that signaling occurs in the network when the UE is changed to the RRC Inactive state and whenever the UE is changed to the RRC Connected state.
  • the AMF may maintain the UE in the CM-IDLE state. As an example, the AMF may perform this operation by using the N2 notification procedure. For example, the AMF may transmit an N2 message including "RRC Inactive Transition Report Request" to the NG-RAN.
  • the AMF informs the NG-RAN that the UE is leaving, the NG-RAN may request the NG-RAN to report the RRC status of the UE to the AMF.
  • the AMF may trigger an AN release procedure.
  • the AMF informs the NG-RAN of leaving (eg, the AMF performs step 2 in FIG. 12 ), and the AMF sends the terminal to the NG-RAN in the RRC_Inactive state. Can you tell me if I can send it to .
  • the AMF may inform the NG-RAN of whether the UE may be directly sent to the RRC_Inactive state.
  • the AMF may indirectly inform the NG-RAN of information such as whether the terminal has transmitted a paging restriction.
  • the network eg, AMF
  • the network is the CN in the initial context setup process for the terminal. Assistance information may not be transmitted to the NG-RAN.
  • the NG-RAN may put the UE in the RRC_Inactive state only when it has CN assistance information. Accordingly, when the NG-RAN does not receive the CN assistance information, the NG-RAN does not put the UE into the RRC_Inactive state.
  • the name of the CN assistance information may be, for example, Core Network Assistance Information for RRC INACTIVE or RRC Inactive Assistance Information.
  • the NG-RAN may change the UE state to the RRC_Inactive state only when receiving CN assistance information from the AMF.
  • the CN assistance information may include information such as a registration area of the terminal and a periodic registration timer.
  • the NG-RAN may determine the RAN-based Notification Area (RNA) of the UE based on the CN assistance information.
  • RNA may be a region similar to the Registration area managed by NG-RAN. When the UE leaves the RNA, the NG-RAN may transmit RRC signaling to the UE to perform an RNA update procedure.
  • the AMF may perform an operation as in the following example. For example, when the AMF transmits information on whether the UE may send the UE to the RRC Inactive state (can change the UE state to the RRC Inactive state) to the NG-RAN, the AMF considers the following example situation By doing so, it is possible to determine whether the terminal may be sent to the RRC Inactive state (the state of the terminal may be changed to the RRC Inactive state):
  • the AMF may decide not to change the status of the UE to RRC_Inactive;
  • the AMF may determine whether to change the state of the Multi-SIM terminal to the CM-IDLE state based on the operator policy. That is, the AMF may determine whether or not to change the state of the Multi-SIM terminal to the RRC_Inactive state based on the operator policy;
  • AMF may determine whether to change the state of the terminal to the RRC_Inactive state based on whether the network (eg, AMF) supports the paging restriction of the terminal. (For example, if the network (eg, AMF) supports the paging restriction, the AMF may decide not to send the RRC_Inactive regardless of whether the UE requests the paging restriction); and/or
  • the AMF may determine whether to change the state of the terminal to the RRC_Inactive state (eg, if the terminal is in a non-allowed area, the AMF is It may be decided not to change to the RRC_Inactive state of the UE).
  • the AMF may perform one of the four operations exemplified above.
  • the AMF may be performed by combining at least one of the four operations.
  • the AMF may request the NG-RAN to report the RRC status of the UE.
  • the AMF may trigger the AN Release procedure.
  • the AMF may perform the operation of the AMF described in the fourth example of the disclosure of the present specification. For example, if AMF knows that NG-RAN can buffer (AMF is based on capability information exchange in operator configuration or NG interface setup process or capability information exchange in initial context setup process, etc., NG-RAN It can be seen that this buffering can be done), AMF may allow the NG-RAN to maintain the state of the UE in the RRC_Inactive state.
  • the AMF may not perform the operation of the AMF described in the fourth example of the disclosure of the present specification.
  • the terminal may provide the AMF with information on how long to leave. For example, the terminal may provide an indication of leaving only for a short period or timer information on how long to leave. Based on this information, the AMF can determine whether NG-RAN buffering is possible while the terminal is leaving.
  • FIGS. 13A to 13C are a first example to which a fourth example of the disclosure of the present specification is applied
  • FIGS. 14A to 14D are a second example to which a fourth example of the disclosure of the present specification is applied
  • FIG. 15 is a diagram of the present specification.
  • the fourth example of the disclosure may be a third example to which it applies.
  • FIGS. 13A to 13C will be described below. do it with
  • the UE may send an AN message to the RAN.
  • the AN message may include an AN parameter and a registration request message.
  • the registration request message may include information such as registration type, subscriber permanent ID or temporary user ID, security parameters, NSSAI, UE 5G capability, PDU session status, and the like.
  • the registration request message may include a Release Request indication and/or paging restriction information (eg, information requesting a paging restriction). That is, the UE may transmit a registration request message including a Release Request indication and/or paging restriction information (eg, information requesting a paging restriction).
  • step 1) when the UE is using E-UTRA, if the UE in MUSIM mode (eg, UE performing MUSIM-related communication) wants to immediately enter the CM-IDLE state, the UE releases Request indication may be included in the registration request message, and optionally, paging restriction information may be further included in the registration request message.
  • Request indication may be included in the registration request message, and paging restriction information may be further included in the registration request message.
  • steps 2) to 20 conventional procedures (eg, the description of steps 2 to 21 in the example of FIGS. 7A and 7B and/or 3GPP TS 23.502 V16.7.0 Section 4.2.2.2.2 General Restriction) can be applied.
  • the new AMF may send a registration accept message to the UE.
  • the registration acceptance message may include information such as a temporary user ID, registration area, mobility restriction, PDU session state, NSSAI, and periodic registration update timer.
  • step 21) may be performed as in the following example.
  • the AMF may delete all stored paging restriction information for this UE and suspend the paging restriction accordingly.
  • the registration request message includes a Release Request indication
  • the following operations may be performed:
  • the AMF may update the UE context based on the received paging restriction information.
  • the AMF may apply a paging restriction in a network triggered service request procedure.
  • a conventional procedure eg, refer to the example of 3GPP TS 23.502 V16.7.0 Section 4.2.3.3 may be applied.
  • the AMF may trigger the AN Release procedure without setting user plane resources.
  • the AMF may trigger the AN Release procedure, as described in 3GPP TS 23.502 V16.7.0 Section 4.2.6 or various examples of the disclosure herein.
  • steps 21b) to 25 conventional procedures (eg, the description of the examples in FIGS. 7A and 7B and/or 3GPP TS 23.502 V16.7.0 Section 4.2.2.2.2 General Restriction) may be applied.
  • a description of the overlapping part with the conventional UE Triggered Service Request procedure (eg, 3GPP TS 23.502 V16.7.0 Section 4.2.3.2 UE Triggered Service Request) will be omitted.
  • the description of 3GPP TS 23.502 V16.7.0 Section 4.2.3.2 UE Triggered Service Request may be applied.
  • a UE in CM-ILDE state may initiate a service request procedure to send an uplink signaling message, user data or a response to a network paging request.
  • the UE may use a service request procedure.
  • the UE may use a service request procedure.
  • the UE may use a service request procedure.
  • the UE may use the service request procedure under the following conditions:
  • the UE in MUSIM mode may not be expected to execute the UE trigger service request procedure together with the Release Request indication when regulatory prioritized services (eg, emergency service, emergency callback waiting) are in progress. .
  • regulatory prioritized services eg, emergency service, emergency callback waiting
  • UE sends an AN message (AN parameter, service request message (List Of PDU Sessions To Be Activated), a list of allowed PDU sessions (List Of Allowed) PDU Sessions), security parameters (including security parameters, and PDU session status)) may be transmitted to (R) AN.
  • AN parameter service request message (List Of PDU Sessions To Be Activated), a list of allowed PDU sessions (List Of Allowed) PDU Sessions), security parameters (including security parameters, and PDU session status)
  • the service request message may include a Release Request indication and/or paging restriction information (eg, information requesting a paging restriction).
  • paging restriction information eg, information requesting a paging restriction
  • step 1) if the UE is using E-UTRA, the UE is in MUSIM mode (eg, a UE performing MUSIM-related communication), and the UE is in the CM-CONNECTED state, the UE is CM-CONNECTED If it wants to leave the state, the UE may include a Release Request indication in the service request message, and optionally may further include paging restriction information in the service request message.
  • MUSIM mode eg, a UE performing MUSIM-related communication
  • the UE is in the CM-CONNECTED
  • the UE may include a Release Request indication in the service request message, and optionally may further include paging restriction information in the service request message.
  • step 1) if the UE is using E-UTRA, the UE is in MUSIM mode (eg, a UE performing MUSIM-related communication), and the UE is in a CM-IDLE state, the UE is in paging restriction information If you want to delete, the UE may include the Release Request indication in the service request message, and may not include the paging restriction information in the service request message. That is, the UE may inform the network (eg, AMF) that the UE wants to delete the paging restriction information by not including the paging restriction information in the service request message.
  • MUSIM mode eg, a UE performing MUSIM-related communication
  • CM-IDLE state e.g., the UE is in paging restriction information
  • the UE may include the Release Request indication in the service request message, and may not include the paging restriction information in the service request message. That is, the UE may inform the network (eg, AMF) that the UE wants to delete the paging restriction information
  • the AMF may initiate a NAS authentication/security procedure.
  • the AMF may delete all paging restriction information stored for this UE, and accordingly stop the paging restriction.
  • Nsmf_PDUSession_UpdateSMContext Request may be, for example, a message requesting update of an SM context related to a PDU session.
  • Nsmf_PDUSession_UpdateSMContext Request is a PDU session ID, operation type (Operation Type), UE location information (UE location information), access type (Access Type), RAT type and UE presence in LADN service area (UE presence in LADN service area), etc. may include information from
  • the Nsmf_PDUSession_UpdateSMContext Request may further include paging restriction information.
  • the AMF may transmit the Nsmf_PDUSession_UpdateSMContext Request message including the paging restriction information to the SMF.
  • AMF may send an N2 request message to (R)AN.
  • N2 request is N2 SM information received from SMF, security context (security context), handover restriction list (Handover Restriction List), subscribed UE-AMBR (Subscribed UE-AMBR (Aggregate Maximum Bit Rate)), MM NAS service acceptance (MM NAS Service Accept List of recommended cells / TAs / NG-RAN node identifiers, and may include UE Radio Capability.
  • the allowed NSSAI for the access type of the UE may be included in the N2 message have.
  • the N2 request message may further include a Release Request indication.
  • the AMF may transmit an N2 request message including a Release Request indication to the RAN.
  • step 1) When the service request message received in step 1) includes a Release Request indication, an operation as in the following example may be performed:
  • - AMF may update the UE context with the received paging restrictions information. If paging restriction information is not provided (eg, if paging restriction information is not received from the UE), the paging restriction may not be applied.
  • the AMF does not set (or establish) the user plane resource, and after the service request procedure is completed, the AMF may inform the NG-RAN that the UE has indicated a Release Request.
  • the NG-RAN may decide whether to keep the UE in the RRC_Inactive state or release the connection. If the NG-RAN decides to release the connection, the NG-RAN may trigger an AN Release procedure.
  • the NG-RAN may trigger the AN Release procedure as described in 3GPP TS 23.502 V16.7.0 Section 4.2.6 or various examples of the disclosure of this specification.
  • the AMF may request the NG-RAN to report the RRC status information.
  • AMF may request NG-RAN to report RRC status information, as described in 3GPP TS 23.502 V16.7.0 Section 4.8.3.
  • the AMF may trigger the AN Release procedure as described in 3GPP TS 23.502 V16.7.0 Section 4.2.6 or various examples of the disclosure herein.
  • 15 is a diagram of the disclosure of the present specification; 4th example A third example to be applied is shown.
  • FIG. 15 will be described below focusing on the difference from the conventional procedure (eg, 3GPP TS 23.502 V16.7.0 Section 4.2.3.3 Network Triggered Service Request).
  • the network initiation service request procedure involves the network signaling with the UE (eg, N1 signaling to the UE, short message service (SMS) that the UE will receive (mobile-terminated), mobile terminating: the destination of data is the UE) It can be used in case there is a need to activate the user plane for a PDU session to pass user data.
  • SMS short message service
  • the network may initiate a network service request procedure.
  • SMF is Namf_Communication_N1N2MessageTransfer(SUPI, PDU session ID, N2 SM information (QFI(s), QoS profile(s), CN N3 tunnel information, S-NSSAI and paging policy) Including indication), Area of validity for N2 SM information, ARP ((Allocation and Retention Priority), paging policy indication, including 5QI and N1N2TransferFailure Notification Target Address) may be transmitted to the AMF, or ii) signaling from NF to AMF: NF may transmit Namf_Communication_N1N2MessageTransfer (including SUPI and N1 message) to the AMF.
  • Namf_Communication_N1N2MessageTransfer including SUPI and N1 message
  • the AMF can respond to the SMF.
  • the AMF may send a Namf_Communication_N1N2MessageTransfer response directly to the SMF with the cause "Attempting to reach UE".
  • Cause "Attempting to reach UE” tells the SMF that the N2 SM information provided in step 3a may be overridden by the AMF if the UE is reachable and the SMF will be asked to provide the N2 SM information again.
  • the AMF may reject the Namf_Communication_N1N2MessageTransfer request message.
  • the AMF may immediately transmit a Namf_Communication_N1N2MessageTransfer response to the SMF with a "N1/N2 transfer success" cause.
  • the AMF may block paging for this UE based on the local policy and the stored paging restriction information.
  • the AMF may transmit a Namf_Communication_N1N2MessageTransfer response message to the Network Function (NF) with an indication that the request is rejected due to restricted paging.
  • the NF receiving the response message may refer to the NF transmitting the request message to the AMF in step 3a).
  • a fifth example of the disclosure of the present specification is an example of the operation of a terminal (eg, UE) and/or a network (eg, NG-RAN, AMF, SMF, UPF, etc.) according to various examples of the disclosure of the present specification described above explain
  • the operation of the terminal and/or the operation of the network (eg, NG-RAN, AMF, SMF, UPF, etc.) described in the eighth example of the disclosure of the present specification is only an example, and the scope of the disclosure of the present specification is It is not limited by the content described in the eighth example of the disclosure of the present specification.
  • the terminal and/or the network may perform the operations described in the first to fifth examples of the disclosure of the present specification, even if not described in the fifth example of the disclosure of the present specification.
  • 16 is a diagram according to the disclosure of the present specification. AMF's action of action An example is shown.
  • the operation of the AMF illustrated in the example of FIG. 16 is merely an example, and the scope of the disclosure is not limited by the operation illustrated in FIG. 16 .
  • the AMF is an operation not shown in FIG. 16
  • the operation described in the first to fourth examples of the disclosure of the present specification may be performed.
  • the AMF may receive a release request message.
  • the AMF may receive a release request message from the UE.
  • the release request message may include information related to leaving (eg, a leaving indication).
  • the information related to leaving may include information that the UE supporting MUSIM performs SIM A-based communication and leaves from SIM A-based communication in order to perform SIM B-based communication.
  • a UE supporting MUSIM may mean a UE supporting communication based on multiple USIMs.
  • the release request message may be transmitted while being included in the service request message or the registration request message.
  • the release request message may further include information on paging restrictions.
  • the information related to the paging restriction may include information on at least one service for which the UE requests a paging message.
  • the AMF may determine whether to transmit a paging message to the UE based on the information related to the paging restriction.
  • the AMF may not transmit a paging message for a service restricted by the paging restriction, but may transmit a paging message for a service permitted according to the paging restriction.
  • the AMF may transmit a message to the RAN node to inform that the UE is leaving. For example, based on the reception of information related to the UE's leaving, the AMF may transmit an N2 message to the RAN node to inform that the UE is leaving. Upon receiving the N2 message, the RAN may trigger an AN release procedure.
  • the AMF may determine whether to maintain the state of the UE in the CM-IDLE state or change the state of the UE to the RRC Inactive state based on the reception of information related to paging restriction. have.
  • the AMF determines the state of the UE as a CM-IDLE state, for example, based on at least one of whether paging restrictions are accepted, operator policy, whether paging restrictions are supported and/or whether service area restrictions are applied for the UE. It can be determined whether to maintain as or to change the state of the UE to the RRC Inactive state.
  • CM-IDLE state for example, based on at least one of whether paging restrictions are accepted, operator policy, whether paging restrictions are supported and/or whether service area restrictions are applied for the UE. It can be determined whether to maintain as or to change the state of the UE to the RRC Inactive state.
  • the AMF may transmit to the RAN node an N2 message further including information to maintain the state of the UE in the CM-IDLE state or information to change the state of the UE to the RRC Inactive state.
  • the AMF may receive a UE context release request message.
  • the RAN may send a UE context release request message to the AMF after triggering the AN release procedure.
  • the UE context release request message may include information on a list of activated PDU sessions.
  • the AMF may transmit a request message for deactivating the PDU session to the SMF for the activated PDU sessions transmitted by the RAN. For example, the AMF may transmit a request message for deactivating a PDU session included in the list of activated PDU sessions to the SMF. For reference, if there is no activated PDU session, the AMF may not transmit a request message for deactivating the PDU session. For example, if there is no active PDU session, step S1604 may not be performed. For example, before performing step S1604, the AMF may determine whether to transmit a request message for deactivating the PDU session based on the list of activated PDU sessions.
  • the AMF may not perform step S1604.
  • the AMF may transmit a request message for deactivating all activated PDU sessions by performing step S1604.
  • the operation of the AMF, the operation of the UE, the operation of the SMF, and the operation of the RAN shown in the example of FIG. 17 are only examples, and the scope of the disclosure is not limited by the operation illustrated in FIG. 17 .
  • the AMF, the UE, the SMF, and/or the RAN may perform the operations described in the first to fourth examples of the disclosure above, even if the operations are not shown in FIG. 16 .
  • the AMF may receive a release request message.
  • the AMF may receive a release request message from the UE.
  • the release request message may include information related to leaving (eg, a leaving indication).
  • the information related to leaving may include information that the UE supporting MUSIM performs SIM A-based communication and leaves from SIM A-based communication in order to perform SIM B-based communication.
  • a UE supporting MUSIM may mean a UE supporting communication based on a plurality of USIMs.
  • the release request message may be transmitted while being included in the service request message or the registration request message.
  • the release request message may further include information on paging restrictions.
  • the information related to the paging restriction may include information on at least one service for which the UE requests a paging message.
  • the AMF may determine whether to transmit a paging message to the UE based on the information related to the paging restriction.
  • the AMF may not transmit a paging message for a service restricted by the paging restriction, but may transmit a paging message for a service permitted according to the paging restriction.
  • the AMF may transmit a message to the RAN node to inform that the UE is leaving. For example, based on the reception of information related to the UE's leaving, the AMF may transmit an N2 message to the RAN node to inform that the UE is leaving. Upon receiving the N2 message, the RAN may trigger an AN release procedure.
  • the AMF may determine whether to maintain the state of the UE in the CM-IDLE state or change the state of the UE to the RRC Inactive state based on the reception of information related to the paging restriction. have.
  • the AMF determines the state of the UE as a CM-IDLE state, for example, based on at least one of whether paging restrictions are accepted, operator policy, whether paging restrictions are supported and/or whether service area restrictions are applied for the UE. It can be determined whether to maintain as or to change the state of the UE to the RRC Inactive state.
  • CM-IDLE state for example, based on at least one of whether paging restrictions are accepted, operator policy, whether paging restrictions are supported and/or whether service area restrictions are applied for the UE. It can be determined whether to maintain as or to change the state of the UE to the RRC Inactive state.
  • the AMF may transmit to the RAN node an N2 message further including information to maintain the state of the UE in the CM-IDLE state or information to change the state of the UE to the RRC Inactive state.
  • the AMF may receive a UE context release request message.
  • the RAN may send a UE context release request message to the AMF after triggering the AN release procedure.
  • the UE context release request message may include information on a list of activated PDU sessions.
  • the AMF may transmit a request message for deactivating at least one PDU session to the SMF.
  • the AMF may transmit a request message for deactivating a PDU session included in the list of activated PDU sessions to the SMF.
  • the AMF may not transmit a request message for deactivating the PDU session. For example, if there is no active PDU session, step S1704 may not be performed. For example, before performing step S1704, the AMF may determine whether to transmit a request message for deactivating the PDU session based on the list of activated PDU sessions. For example, when an activated PDU session does not exist in the list of activated PDU sessions, the AMF may not perform step S1704. As another example, when at least one activated PDU session exists in the list of activated PDU sessions, the AMF may transmit a request message for deactivating all activated PDU sessions by performing step S1704.
  • communication of a terminal supporting MUSIM can be effectively supported. For example, when the terminal wants to leave, unnecessary signaling can be reduced. Also, when the terminal wants to leave, the terminal can be quickly switched to the IDLE state. A billing problem that may occur due to the MUSIM operation may be resolved. For example, since the AMF receives a list of activated PDU sessions from the RAN, the AMF requests deactivation only for the activated PDU sessions, thereby preventing unnecessary signaling.
  • activated PDU Session information may be transmitted together with the NAS message while the terminal transmits the NAS message for leaving.
  • the AMF may request PDU Session deactivation from the SMFs managing the activated PDU Session.
  • the AMF may perform an operation to prevent the terminal from being maintained in the RRC_Inactive state. For example, the AMF may perform the N2 release procedure when the terminal is in the RRC_Inactive state through the N2 Notification procedure.
  • the AMF may transmit information notifying the NG-RAN that the terminal has left and not keeping the terminal in the RRC_Inactive state to the NG-RAN.
  • the operation of the terminal (eg, UE) described in this specification may be implemented by the apparatus of FIGS. 1 to 4 described above.
  • the terminal eg, UE
  • the terminal may be the first device 100 or the second device 200 of FIG. 2 .
  • an operation of a terminal (eg, UE) described herein may be processed by one or more processors 102 or 202 .
  • the operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of an instruction/program (e.g. instruction, executable code) executable by one or more processors 102 or 202 .
  • One or more processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 105 or 206 , and execute instructions/programs stored in one or more memories 104 or 204 as disclosed herein. It is possible to perform the operation of the terminal (eg, UE) described in .
  • instructions for performing an operation of a terminal (eg, UE) described in the disclosure of the present specification may be stored in a non-volatile computer-readable storage medium in which it is recorded.
  • the storage medium may be included in one or more memories 104 or 204 .
  • the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform the operation of the terminal (eg, UE) described in the disclosure of the present specification.
  • FIGS. 1 to 3 the operation of a network node (eg, AMF, SMF, UPF, etc.) or a base station (eg, NG-RAN, gNB, eNB, RAN, E-UTRAN, etc.) described in this specification is illustrated in FIGS. 1 to 3 to be described below. It can be implemented by the device of For example, the network node or base station may be the first apparatus 100 or the second apparatus 200 of FIG. 2 .
  • the operation of a network node or base station described herein may be handled by one or more processors 102 or 202 .
  • the operation of the terminal described herein may be stored in one or more memories 104 or 204 in the form of an instruction/program (e.g.
  • processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 106 or 206 , and execute instructions/programs stored in one or more memories 104 or 204 as disclosed herein. It is possible to perform the operation of the network node or the base station described in .
  • the instructions for performing the operations of the network node or the base station described in the disclosure of the present specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium in which it is recorded.
  • the storage medium may be included in one or more memories 104 or 204 .
  • the instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform operations of a network node or a base station described in the disclosure of the present specification.

Landscapes

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

Abstract

Un mode de réalisation de la présente invention concerne un procédé permettant à une fonction de gestion d'accès et de mobilité (AMF) de réaliser une communication liée à une pluralité de modules d'identité d'abonné universels (USIM). Le procédé peut comprendre les étapes suivantes : recevoir, en provenance d'un UE, un message de demande de libération comprenant des informations relatives au départ de l'UE ; sur la base des informations reçues associées au départ de l'UE, transmettre à un nœud RAN un message N2 pour notifier que l'UE s'en va; recevoir, en provenance du nœud RAN, un message de demande de libération de contexte d'UE comprenant une liste de sessions PDU activées ; et transmettre à une SMF un message de demande pour demander de désactiver une session PDU.
PCT/KR2022/001584 2021-02-05 2022-01-28 Communication associée à une pluralité d'usim Ceased WO2022169223A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2021-0016914 2021-02-05
KR20210016914 2021-02-05
KR10-2021-0054908 2021-04-28
KR20210054908 2021-04-28

Publications (1)

Publication Number Publication Date
WO2022169223A1 true WO2022169223A1 (fr) 2022-08-11

Family

ID=82742285

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/001584 Ceased WO2022169223A1 (fr) 2021-02-05 2022-01-28 Communication associée à une pluralité d'usim

Country Status (1)

Country Link
WO (1) WO2022169223A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12439375B2 (en) * 2021-09-30 2025-10-07 Mediatek Inc. MUSIM paging restriction in 5GS

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190088536A (ko) * 2017-05-09 2019-07-26 후아웨이 테크놀러지 컴퍼니 리미티드 세션 관리 방법, 단말, 및 시스템
US20200214072A1 (en) * 2017-08-14 2020-07-02 China Academy Of Telecommunications Technology Method and device for processing non-matching between ue and network state

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190088536A (ko) * 2017-05-09 2019-07-26 후아웨이 테크놀러지 컴퍼니 리미티드 세션 관리 방법, 단말, 및 시스템
US20200214072A1 (en) * 2017-08-14 2020-07-02 China Academy Of Telecommunications Technology Method and device for processing non-matching between ue and network state

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONNMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) (Release 17)", 3GPP TR 23.761 V1.2.0, 1 November 2020 (2020-11-01), XP055811323, [retrieved on 20210608] *
VIVO: "E-mail discussion: [Post111-e][917][Multi-SIM] Multi-Sim (vivo)", 3GPP DRAFT; R2-2009325, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051942290 *
VIVO: "KI#3, Sol#4: update to support local leaving negotiation", 3GPP DRAFT; S2-2003827, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051890400 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12439375B2 (en) * 2021-09-30 2025-10-07 Mediatek Inc. MUSIM paging restriction in 5GS

Similar Documents

Publication Publication Date Title
WO2020171529A1 (fr) Procédé permettant de réaliser une communication liée à un état de désactivation de données de commutation de paquets
WO2021177716A2 (fr) Communication liée à une multidiffusion
WO2021241905A1 (fr) Sélection efficace de plmn lors d'une défaillance d'authentification pour chaque tranche de réseau dans un réseau d'itinérance
WO2022215909A1 (fr) Procédé de gestion de sessions pdu
WO2021187783A1 (fr) Prise en charge de continuité de service entre snpn et plmn
WO2021167304A1 (fr) Communication relative à un état de désactivation du service de données ps
WO2020138985A1 (fr) Procédé permettant de fournir un service de communication dans un système de communication sans fil
WO2021187936A1 (fr) Procédé de communication utilisant une tranche de réseau
WO2021177734A1 (fr) Support de continuité de service pour transfert entre snpn et plmn
WO2022050659A1 (fr) Commande du trafic
WO2022014981A1 (fr) Procédé pour permettre une continuité de service lorsqu'une situation de catastrophe est terminée, et dispositif prenant en charge celui-ci
WO2021162393A1 (fr) Communication liée à des sessions de pdu multi-accès
WO2020060007A1 (fr) Procédé et dispositif sans fil pour gérer une session de pdu dans une communication mobile 5g
WO2021020933A1 (fr) Mesure pour un changement de plmn
WO2022035204A1 (fr) Communication associée à une tranche de réseau
WO2022098053A1 (fr) Mesure relative à un flux qos
WO2023287154A1 (fr) Session pdu à trajets multiples
WO2023140601A1 (fr) Communication associée à des tranches de réseau
WO2022014944A1 (fr) Traitement de nssai rejetées en raison d'une défaillance de nssaa
WO2021162500A1 (fr) Communication liée à une session pdu multi-accès
WO2021187881A1 (fr) Indication de prise en charge de réseau pour des informations d'appariement de session de pdu fournies par un ue
WO2022235034A1 (fr) Communication liée au contexte d'un eu
WO2022035205A1 (fr) Communication associée à une tranche de réseau
WO2021177732A1 (fr) Communication directe
WO2022035257A1 (fr) Traitement d'une défaillance de nssaa provoquée par une erreur de réseau ou une expiration de délai

Legal Events

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

Ref document number: 22749973

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22749973

Country of ref document: EP

Kind code of ref document: A1