WO2021066346A1 - 비-3gpp 상의 pdu 세션을 3gpp 액세스로 이동시키기 위한 방안 - Google Patents
비-3gpp 상의 pdu 세션을 3gpp 액세스로 이동시키기 위한 방안 Download PDFInfo
- Publication number
- WO2021066346A1 WO2021066346A1 PCT/KR2020/012309 KR2020012309W WO2021066346A1 WO 2021066346 A1 WO2021066346 A1 WO 2021066346A1 KR 2020012309 W KR2020012309 W KR 2020012309W WO 2021066346 A1 WO2021066346 A1 WO 2021066346A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdu session
- access
- smf
- amf
- notification message
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 171
- 230000001960 triggered effect Effects 0.000 claims abstract description 19
- 230000006870 function Effects 0.000 claims description 74
- 230000015654 memory Effects 0.000 claims description 24
- 230000006399 behavior Effects 0.000 claims 2
- 238000007726 management method Methods 0.000 description 62
- 238000012986 modification Methods 0.000 description 39
- 230000004048 modification Effects 0.000 description 39
- 238000010586 diagram Methods 0.000 description 34
- 238000004891 communication Methods 0.000 description 31
- 230000004044 response Effects 0.000 description 30
- 230000005540 biological transmission Effects 0.000 description 20
- 230000011664 signaling Effects 0.000 description 19
- 238000010295 mobile communication Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 9
- 238000013473 artificial intelligence Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 239000013256 coordination polymer Substances 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 230000003190 augmentative effect Effects 0.000 description 4
- 238000003780 insertion Methods 0.000 description 4
- 230000037431 insertion Effects 0.000 description 4
- 230000000737 periodic effect Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000014509 gene expression Effects 0.000 description 3
- 230000008093 supporting effect Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000005641 tunneling Effects 0.000 description 3
- 241001123862 Mico Species 0.000 description 2
- 208000034819 Mobility Limitation Diseases 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 239000004984 smart glass Substances 0.000 description 2
- 208000027418 Wounds and injury Diseases 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000005452 bending Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 201000010099 disease Diseases 0.000 description 1
- 208000035475 disorder Diseases 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000001093 holography Methods 0.000 description 1
- 230000001976 improved effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 208000014674 injury Diseases 0.000 description 1
- 230000035935 pregnancy Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 239000010454 slate Substances 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/00837—Determination of triggering parameters for hand-off
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
- H04W36/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
Definitions
- the present specification relates to mobile communication.
- 1 is a structural diagram of an evolved mobile communication network.
- EPC Evolved Packet Core
- S-GW Serving Gateway
- PDN GW Packet Data Network Gateway
- MME Mobility Management Entity
- SGSN Serving General Packet Radio Service
- SGSN Serving General Packet Radio Service
- ePDG enhanced packet data gateway
- the S-GW 52 operates as a boundary point between the radio access network (RAN) and the core network, and is an element that functions to maintain a data path between the eNodeB 22 and the PDN GW 53.
- the S-GW 52 serves as a local mobility anchor point. That is, packets may be routed through the S-GW 52 for mobility within the E-UTRAN (Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network defined after 3GPP Release-8).
- E-UTRAN Evolved-UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network defined after 3GPP Release-8).
- the S-GW (52) is another 3GPP network (RAN defined before 3GPP Release-8, for example, UTRAN or GERAN (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network) can also function as an anchor point for mobility.
- 3GPP Release-8 for example, UTRAN or GERAN (Global System for Mobile Communication) / EDGE (Enhanced Data rates for Global Evolution) Radio Access Network) can also function as an anchor point for mobility.
- the PDN GW (or P-GW) 53 corresponds to a termination point of a data interface toward a packet data network.
- the PDN GW 53 may support policy enforcement features, packet filtering, charging support, and the like.
- mobility between 3GPP networks and non-3GPP networks e.g., untrusted networks such as I-WLAN (Interworking Wireless local area networks), and trusted networks such as Code Division Multiple Access (CDMA) networks
- I-WLAN Interworking Wireless local area networks
- CDMA Code Division Multiple Access
- the S-GW 52 and the PDN GW 53 are configured as separate gateways, but two gateways may be implemented according to a single gateway configuration option. have.
- the MME 51 is an element that performs signaling and control functions to support access to a network connection of the UE, allocation of network resources, tracking, paging, roaming, and handover. .
- the MME 51 controls control plane functions related to subscriber and session management.
- the MME 51 manages a number of eNodeBs 22 and performs signaling for selection of a conventional gateway for handover to another 2G/3G network.
- the MME 51 performs functions such as security procedures, terminal-to-network session handling, and idle terminal location management.
- SGSN handles all packet data such as user mobility management and authentication to other access 3GPP networks (eg, GPRS network, UTRAN/GERAN).
- 3GPP networks eg, GPRS network, UTRAN/GERAN.
- ePDG serves as a secure node for untrusted non-3GPP networks (eg, I-WLAN, WiFi hotspot, etc.).
- non-3GPP networks eg, I-WLAN, WiFi hotspot, etc.
- a terminal having IP capability is provided by an operator (ie, an operator) through various elements in the EPC based on 3GPP access as well as non-3GPP access. It can access the IP service network (eg IMS).
- IMS IP service network
- FIG. 1 shows various reference points (eg, S1-U, S1-MME, etc.).
- a conceptual link connecting two functions existing in different functional entities of E-UTRAN and EPC is defined as a reference point.
- Table 1 below summarizes the reference points shown in FIG. 1.
- various reference points may exist according to the network structure.
- This reference point can be used within a Public Land Mobile Network (PLMN) or between PLMNs (e.g. in the case of an inter-PLMN handover).
- PLMN Public Land Mobile Network
- S4 A reference point between the SGW and SGSN that provides the associated control and mobility support between the GPRS core and the SGW's 3GPP anchor function.
- S5 A reference point that provides user plane tunneling and tunnel management between SGW and PDN GW. Used for SGW relocation when connection to a PDN GW not co-located with the SGW is required due to UE mobility and for the required PDN connectivity.
- S11 Reference point between MME and SGW SGi PDN A reference point between GW and PDN.
- the PDN may be a public or private PDN outside the operator, or may be, for example, an intra-operator PDN for providing an IMS service. This reference point corresponds to Gi of 3GPP access
- S2a and S2b correspond to non-3GPP interfaces.
- S2a is a reference point that provides control and mobility support between trusted non-3GPP access and PDN GW to the user plane.
- S2b is a reference point that provides related control and mobility support between ePDG and PDNGW to the user plane.
- LTE long term evolution
- LTE-A LTE-Advanced
- 5th generation mobile communication defined by the International Telecommunication Union (ITU) refers to providing a maximum 20Gbps data transmission speed and a sensible transmission speed of at least 100Mbps or more anywhere. Its official name is'IMT-2020' and it aims to be commercialized globally in 2020.
- ITU International Telecommunication Union
- 5G mobile communication supports multiple numerology or subcarrier spacing (SCS) to support various services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and when the SCS is 30 kHz/60 kHz, it is dense-urban, lower latency. And a wider carrier bandwidth, and when the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.
- SCS subcarrier spacing
- the NR frequency band is defined as a frequency range of two types (FR1, FR2).
- FR1 is 410 MHz-7125 MHz
- FR2 is 24250 MHz-52600 MHz, which may mean a millimeter wave (mmW).
- mmW millimeter wave
- FR1 may mean “sub 6GHz range”
- FR2 may mean “above 6GHz range” and may be called millimeter wave (mmW). .
- mmW millimeter wave
- FR1 may include a band of 410MHz to 7125MHz as shown in Table A7 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.) or higher included in FR1 may include an unlicensed band.
- the unlicensed band can be used for a variety of purposes, and can be used, for example, for communication for vehicles (eg, autonomous driving).
- ITU proposes three usage scenarios, e.g. eMBB (enhanced mobile broadband), mMTC (massive machine type communication), and URLLC (Ultra Reliable and Low Latency Communications).
- eMBB enhanced mobile broadband
- mMTC massive machine type communication
- URLLC Ultra Reliable and Low Latency Communications
- URLLC relates to a usage scenario that requires high reliability and low latency.
- services such as automatic driving, factory automation, and augmented reality require high reliability and low latency (for example, a delay time of 1 ms or less).
- the delay time of 4G (LTE) is statistically 21-43ms (best 10%), 33-75ms (median). This is insufficient to support a service that requires a delay time of 1ms or less.
- the eMBB usage scenario relates to a usage scenario requiring mobile ultra-wideband.
- FIG. 2 is a structural diagram of a next-generation mobile communication network.
- 5GC 5G Core
- AMF Access and Mobility Management Function
- SMF Session Management Function
- PCF Policy Control Function
- Functions 43 User Plane Function
- UPF User Plane Function
- AF Application Function
- UDM Unified Data Management
- N3IWF Non-3GPP InterWorking Function
- the UE 10 is connected to the data network via the UPF 44 through a Next Generation Radio Access Network (NG-RAN) (ie, a gNB or a base station).
- NG-RAN Next Generation Radio Access Network
- the UE 10 may receive a data service even through an untrusted non-3rd Generation Partnership Project (WLAN) access, for example, a Wireless Local Area Network (WLAN).
- WLAN Wireless Local Area Network
- an N3IWF 49 may be deployed.
- 3 is an exemplary diagram showing an expected structure of next-generation mobile communication from a node perspective.
- the UE is connected to a data network (DN) through a next-generation radio access network (RAN).
- DN data network
- RAN next-generation radio access network
- the illustrated control plane function (CPF) node is all or part of the functions of a mobility management entity (MME) of 4G mobile communication, and a control plane function of a serving gateway (S-GW) and a PDN gateway (P-GW). Do all or part of.
- the CPF node includes an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).
- AMF Access and Mobility Management Function
- SMF Session Management Function
- the illustrated User Plane Function (UPF) node is a type of gateway through which user data is transmitted/received.
- the UPF node may perform all or part of the user plane functions of S-GW and P-GW of 4G mobile communication.
- the illustrated PCF Policy Control Function
- Policy Control Function is a node that controls the operator's policy.
- the illustrated application function is a server for providing various services to the UE.
- the illustrated Unified Data Management is a kind of server that manages subscriber information, such as a 4G mobile communication HSS (Home Subscriber Server).
- the UDM stores and manages the subscriber information in a Unified Data Repository (UDR).
- UDR Unified Data Repository
- the illustrated authentication server function (AUSF) authenticates and manages the UE.
- the illustrated network slice selection function (NSSF) is a node for network slicing as will be described later.
- the UE may simultaneously access two data networks using multiple protocol data unit or packet data unit (PDU) sessions.
- PDU packet data unit
- FIG. 4 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.
- FIG. 4 an architecture for a UE to access two data networks simultaneously using one PDU session is shown.
- N1 represents a reference point between the UE and AMF.
- N2 represents a reference point between (R)AN and AMF.
- N3 represents a reference point between (R)AN and UPF.
- N4 represents a reference point between SMF and UPF.
- N5 represents the reference point between PCF and AF.
- N6 represents a reference point between UPF and DN.
- N7 represents a reference point between SMF and PCF.
- N8 represents a reference point between UDM and AMF.
- N9 represents a reference point between UPFs.
- N10 represents a reference point between UDM and SMF.
- N11 represents a reference point between AMF and SMF.
- N12 represents a reference point between AMF and AUSF.
- N13 represents a reference point between UDM and AUSF.
- N14 represents a reference point between AMFs.
- N15 represents a reference point between PCF and AMF.
- N16 represents a reference point between SMFs.
- N22 represents a reference point between AMF and NSSF.
- FIG. 5 is another exemplary diagram showing the structure of a radio interface protocol between a UE and a gNB.
- the radio interface protocol is based on the 3GPP radio access network standard.
- the radio interface protocol horizontally consists of a physical layer, a data link layer, and a network layer, and vertically, a user plane and control for data information transmission. It is divided into a control plane for signal transmission.
- the protocol layers are L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the lower 3 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.
- data is transmitted 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 setting (setting), resetting (Re-setting) and release (Release) of radio bearers (Radio Bearer; RB). It is in charge of control.
- RB means a service provided by the second layer for data transmission between the UE and the E-UTRAN.
- the NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management.
- the NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM).
- MM mobility management
- SM session management
- NAS entity for MM provides the following functions in general.
- NAS procedure related to AMF includes the following.
- AMF supports the following functions.
- the NAS entity for the SM performs session management between the UE and the SMF.
- the SM signaling message is processed, that is, generated and processed at the NAS-SM layer of the UE and SMF.
- the contents of the SM signaling message are not interpreted by the AMF.
- the NAS entity for MM creates a NAS-MM message that derives how and where to deliver the SM signaling message through the security header representing the NAS transmission of SM signaling, and additional information about the receiving NAS-MM.
- the NAS entity for the SM upon receiving the SM signaling, performs the integrity check of the NAS-MM message, analyzes the additional information, and derives the method and place to derive the SM signaling message.
- an RRC layer, an RLC layer, a MAC layer, and a PHY layer located below the NAS layer are collectively referred to as an access layer (AS).
- the 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 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 non-3GPP access as well as 3GPP access.
- RM Registration Management
- CM Connection Management
- the handover may fail if resource reservation fails in the access network.
- the SMF informs the AMF that the PDU session has been released.
- the AMF deletes all the context for the corresponding PDU session.
- one disclosure of the present specification aims to present a method capable of solving the above-described problem.
- the method may include receiving a session management (SM) context status notification message from a session management function (SMF).
- the SM context status notification message may be received based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU protocol data unit
- the PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- the method may include updating an access type related to the PDU session based on the SM context status notification message.
- one disclosure of the present specification may include a method of operating a Session Management Function (SMF).
- the operation method may include transmitting a session management (SM) context status notification message to an access and mobility management function (AMF).
- the SM context status notification message may be transmitted based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU protocol data unit
- the PDU session establishment procedure may be triggered for handover of a PDU session between non-3GPP (non-3rd Generation Partnership Project) access and 3GPP access.
- the SM context status notification message may include information on an access type related to the PDU session.
- the chipset includes at least one processor; It may include at least one memory that stores instructions and is operably electrically connected to the at least one processor.
- the operation performed based on the command being executed by the at least one processor may include: receiving a Session Management (SM) context status notification message from a Session Management Function (SMF).
- the SM context status notification message may be received based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- the operation may include updating an access type related to the PDU session based on the SM context status notification message.
- the device includes a transceiver; At least one processor; In addition, it may include at least one memory that stores instructions and is operably electrically connected to the at least one processor.
- the operation performed based on the command being executed by the at least one processor may include: receiving a Session Management (SM) context status notification message from a Session Management Function (SMF).
- the SM context status notification message may be received based on a failure of a protocol data unit (PDU) session establishment procedure.
- SM Session Management
- PDU protocol data unit
- the PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- the operation may include updating an access type related to the PDU session based on the SM context status notification message.
- one disclosure of the present specification may provide a non-volatile computer-readable storage medium for recording instructions.
- the storage medium may contain instructions.
- the one or more processors may cause the one or more processors to perform an operation.
- the operation may include: receiving a session management (SM) context status notification message from a session management function (SMF).
- the SM context status notification message may be received based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU session establishment procedure may be triggered for handover of a PDU session between non-3GPP (non-3rd Generation Partnership Project) access and 3GPP access.
- the operation may include updating an access type related to the PDU session based on the SM context status notification message.
- the chipset includes at least one processor; It may include at least one memory that stores instructions and is operably electrically connected to the at least one processor.
- the operation performed based on the command being executed by the at least one processor may include: transmitting a session management (SM) context status notification message to an access and mobility management function (AMF).
- the SM context status notification message may be transmitted based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- the SM context status notification message may include information on an access type related to the PDU session.
- the device includes a transceiver; At least one processor; In addition, it may include at least one memory that stores instructions and is operably electrically connected to the at least one processor.
- the operation may include: transmitting a session management (SM) context status notification message to an access and mobility management function (AMF).
- SM session management
- AMF access and mobility management function
- the SM context status notification message may be transmitted based on a failure of a protocol data unit (PDU) session establishment procedure.
- the PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- the SM context status notification message may include information on an access type related to the PDU session.
- 1 is a structural diagram of an evolved mobile communication network.
- FIG. 2 is a structural diagram of a next-generation mobile communication network.
- 3 is an exemplary diagram showing an expected structure of next-generation mobile communication from a node perspective.
- FIG. 4 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.
- FIG. 5 is another exemplary diagram showing the structure of a radio interface protocol between a UE and a gNB.
- 6A and 6B are signal flow diagrams illustrating an exemplary registration procedure.
- 7A and 7B are signal flow diagrams illustrating an exemplary PDU session establishment procedure.
- 8A and 8B show a procedure for modifying a PDU session.
- FIG. 9 is an exemplary diagram illustrating an example in which establishment of a new PDU session fails.
- 10A and 10B are exemplary diagrams illustrating a PDU session establishment procedure for non-roaming and local breakout (LBO) roaming.
- 11A and 11B are exemplary diagrams illustrating a procedure for establishing a PDU session for HR roaming.
- FIG. 12 is an exemplary diagram illustrating an example in which handover from a non-3GPP access to a 3GPP access fails in a non-roaming or LBO robang scheme.
- FIGS. 13A and 13B are exemplary diagrams illustrating an example in which a handover from a non-3GPP access to a 3GPP access fails in an HR roaming scheme.
- FIG. 14 is a block diagram illustrating a configuration of a processor in which the disclosure of the present specification is implemented.
- 15 shows a wireless communication system according to an embodiment.
- FIG. 16 illustrates a block diagram of a network node according to an embodiment.
- 17 is a block diagram showing the configuration of the UE 100 according to an embodiment.
- FIG. 18 is a block diagram showing in detail a transmission/reception unit of the first device shown in FIG. 15 or a transmission/reception unit of the device shown in FIG. 27.
- first and second used in the present specification may be used to describe various components, but the components should not be limited by the terms. These terms are only used for the purpose of distinguishing one component from another component. For example, without departing from the scope of the rights, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component.
- a component When a component is connected to or is said to be connected to another component, it may be directly connected to or connected to the other component, but another component may exist in the middle. On the other hand, when a component is directly connected to or directly connected to another component, it should be understood that there is no other component in the middle.
- 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) refers to “only A”, “only B”, “only C”, or “A, B and any combination of C ( It can mean any combination of A, B and C)”.
- a forward slash (/) or comma used herein may mean “and/or (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 “at least one It can be interpreted 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 It can mean 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 It can mean “at least one of A, B and C”.
- parentheses used in the present specification may mean “for example”. Specifically, when indicated as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” of the present specification is not limited to “PDCCH”, and “PDDCH” may be suggested as an example of “control information”. In addition, even when indicated as “control information (ie, PDCCH)”, “PDCCH” may be proposed as an example of “control information”.
- a UE User Equipment
- the illustrated UE may be referred to in terms of UE (100) (Terminal), ME (Mobile Equipment), and the like.
- the UE may be a portable device such as a notebook computer, a mobile phone, a PDA, a smart phone, or a multimedia device, or a non-portable device such as a PC or a vehicle-mounted device.
- the UE needs to obtain authorization in order to enable mobility tracking, enable data reception, and receive services. For this, the UE must register with the network.
- the registration procedure is performed when the UE needs to do initial registration for the 5G system.
- the registration procedure is performed when the UE performs periodic registration update, when it moves from an idle mode to a new TA (tracking area), and when the UE needs to perform periodic registration update.
- the ID of the UE may be obtained from the UE.
- AMF can deliver PEI (IMEISV) to UDM, SMF and PCF.
- PEI IMEISV
- 6A and 6B are signal flow diagrams illustrating an exemplary registration procedure.
- the UE can transmit an AN message to the RAN.
- the AN message may include an AN parameter and a registration request message.
- the registration request message may include information such as a registration type, a subscriber permanent ID or a temporary user ID, a security parameter, Network Slice Selection Assistance Information (NSSAI), 5G capability of the UE, and a protocol data unit (PDU) session state.
- NSSAI Network Slice Selection Assistance Information
- 5G capability of the UE a protocol data unit (PDU) session state.
- PDU protocol data unit
- the AN parameter may include a SUPI (Subscription Permanent Identifier) or a temporary user ID, a selected network, and NSSAI.
- SUPI Subscriber Permanent Identifier
- NSSAI Network Access Management Function
- the registration type is “initial registration” (ie, the UE is in a non-registered state), “mobility registration update” (ie, the UE is in a registered state and starts the registration process due to mobility) or “regular registration update” ( That is, it may indicate whether the UE is in a registered state and starts a registration procedure due to expiration of a 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 Public Land Mobile Network (PLMN) of 3GPP access, the UE does not provide the temporary ID of the UE assigned by the AMF during the registration procedure through the non-3GPP access. I can't.
- Security parameters can be used for authentication and integrity protection.
- the PDU session state may indicate a (previously established) PDU session available in the UE.
- the RAN may select AMF based on (R)AT and NSSAI.
- the (R)AN cannot select an appropriate AMF, it selects a random AMF according to local policy, and transmits a registration request to the selected AMF. If the selected AMF cannot serve the UE, the selected AMF selects another AMF more appropriate for the UE.
- the RAN transmits an N2 message to a new AMF.
- the N2 message includes an N2 parameter and a registration request.
- the registration request may include a registration type, a subscriber permanent identifier or a temporary user ID, a security parameter, and a default setting of NSSAI and MICO modes.
- the N2 parameter includes location information related to a cell in which the UE is camping, a cell identifier, and a RAT type.
- steps 4 to 17 described later may not be performed.
- the newly selected AMF may transmit an information request message to the previous AMF.
- the new AMF may send an information request message containing complete registration request information to the previous 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 transmits an information response message including the SUPI and MM context of the UE.
- SMF information including the ID of the SMF and the PDU session ID may be included in the information response message in the previous AMF.
- the new AMF transmits an Identity Request message to the UE if SUPI is not provided by the UE or is not retrieved from the previous AMF.
- the UE transmits an Identity Response message including the SUPI to the new AMF.
- AMF may decide to trigger AUSF.
- AMF may select AUSF based on SUPI.
- AUSF can 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 described later the new AMF selects UDM based on SUPI.
- the new AMF After the final registration, if the AMF is changed, there is no valid subscription context for the UE in the AMF, or the UE provides a SUPI that does not refer to a valid context in the AMF, the new AMF starts the update location procedure. . Alternatively, it may be started even when the UDM initiates a cancel location for the previous AMF. The old AMF discards the MM context and notifies all possible SMF(s), and the new AMF creates an MM context for the UE after obtaining the AMF-related subscription data from the UDM.
- the AMF When network slicing is used, the AMF obtains the NSSAI allowed based on the requested NSSAI, UE subscription and local policy. If AMF is not suitable to support the allowed NSSAI, it will reroute the registration request.
- the new AMF can 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 available SMF information.
- usable SMF information may be received from the previous AMF.
- the new AMF may request the SMF to release network resources related to a PDU session that is not active in 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 previous AMF may delete the UE context in the PCF.
- the PCF may transmit a UE Context Termination Request message to the previous AMF.
- the new AMF transmits a registration acceptance message to the UE.
- the registration acceptance message may include a temporary user ID, a registration area, a mobility restriction, a PDU session state, an NSSAI, a regular registration update timer, and an allowed MICO mode.
- the registration acceptance message may include the allowed NSSAI and information of the mapped NSSAI.
- the allowed NSSAI information on the access type of the UE may be included in an N2 message including a registration acceptance message.
- the mapped NSSAI information is information obtained by mapping each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI set for HPLMN.
- a temporary user ID may be further included in the registration acceptance message.
- information indicating mobility limitation may be additionally included in the registration acceptance message.
- the AMF may include information indicating the PDU session state for the UE in the registration acceptance message. The UE may remove any internal resources related to a PDU session that is not marked as active in the received PDU session state. If the PDU session state information is in the Registration Request message, the AMF may include information indicating the PDU session state to the UE in the registration acceptance message.
- the UE transmits a registration completion message to the new AMF.
- PDU session establishment procedure As for the protocol data unit (PDU) session establishment procedure, two types of PDU session establishment procedures may exist as follows.
- the network may transmit a device trigger message to the application(s) of the UE.
- 7A and 7B are signal flow diagrams illustrating an exemplary PDU session establishment procedure.
- FIGS. 7A and 7B assume that the UE has already registered on the AMF according to the registration procedure shown in FIG. 6. Therefore, it is assumed that the AMF has already obtained user subscription data from UDM.
- the UE transmits 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 the 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 on the mapped NSSAI.
- the mapped NSSAI information is information obtained by mapping each S-NSSAI of the allowed NSSAI to the S-NASSI of the NSSAI set for HPLMN.
- the UE may extract and store information of the allowed S-NSSAI and the mapped S-NSSAI included in the registration acceptance message received from the network (i.e., AMF) in the registration procedure of FIG. have. Accordingly, the UE may include and transmit both the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on information of the mapped NSSAI in the PDU session establishment request message.
- the network i.e., AMF
- the UE may generate a new PDU session ID.
- the UE may initiate a PDU session establishment procedure initiated by the UE by transmitting 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 through AMF and may include user location information and access technology type information.
- the N1 SM information may include an SM PDU DN request container that includes information on PDU session authentication by an external DN.
- the AMF may determine that the message corresponds to a request for a new PDU session when the request type indicates "initial request" and when 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 with each other.
- the AMF may select SMF.
- the AMF may transmit an Nsmf_PDUSession_CreateSMContext Request message or an Nsmf_PDUSession_UpdateSMContext Request message to the selected SMF.
- the Nsmf_PDUSession_CreateSMContext Request message is SUPI, DNN, S-NSSAI(s), PDU Session ID, AMF ID, Request Type, PCF ID, Priority Access, N1 SM container, User location information, Access Type, PEI, GPSI, UE presence in It may include LADN service area, Subscription For PDU Session Status Notification, DNN Selection Mode, and Trace Requirements.
- the SM container may include a PDU Session Establishment Request message.
- the Nsmf_PDUSession_UpdateSMContext Request message may include SUPI, DNN, S-NSSAI(s), SM Context ID, AMF ID, Request Type, N1 SM container, User location information, Access Type, RAT type, and PEI.
- the N1 SM container may include 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 a subscriber data request message to UDM.
- the subscriber data request message may include a subscriber permanent ID and DNN.
- UDM can transmit subscription data response message to SMF
- step 3 if the request type indicates "existing PDU session", the SMF determines that the request is due to handover between 3GPP access and non-3GPP access.
- the SMF can identify an existing PDU session based on the PDU session ID.
- the SMF may request subscription data.
- the subscription data may include information on an authenticated request type, an authenticated SSC mode, and a basic QoS profile.
- the SMF can check whether the UE request complies with the user subscription and local policy. Alternatively, the SMF rejects the UE request through NAS SM signaling (including the related SM rejection cause) delivered by the AMF, and the SMF informs the AMF that the PDU session ID should be considered to be released.
- NAS SM signaling including the related SM rejection cause
- the SMF transmits the Nsmf_PDUSession_CreateSMContext Response message or the Nsmf_PDUSession_UpdateSMContext Response message to the AMF.
- the Nsmf_PDUSession_CreateSMContext Response message may include Cause, SM Context ID, or N1 SM container.
- the N1 SM container may include a PDU Session Reject.
- step 3 when the SMF receives the Nsmf_PDUSession_CreateSMContext Request message, and the SMF can process the PDU Session establishment request message, the SMF SM context is created and the SM context ID is transmitted to the AMF.
- the SMF selects the PCF.
- the SMF performs an SM policy association establishment procedure in order to establish an SM policy association with the PCF.
- step 3 If the request type of step 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If step 5 is not performed, the SMF may also select UPF. In case of request type IPv4 or IPv6, SMF can allocate IP address/prefix for PDU session.
- the SMF performs the SM policy association modification procedure, and provides information on the policy control request trigger and conditions.
- the request type indicates "initial request", and the SMF starts the N4 session establishment procedure using the selected UPF, otherwise it can start the N4 session modification procedure using the selected UPF.
- the SMF transmits an N4 session establishment/modification request message to the UPF.
- the SMF may provide a packet detection, enforcement and reporting rule to be installed in the UPF for the PDU session.
- CN tunnel information may be provided to the UPF.
- UPF can respond by sending an N4 session establishment/modification response message.
- CN tunnel information may be provided to the SMF.
- the SMF transmits a Namf_Communication_N1N2MessageTransfer message to the AMF.
- the Namf_Communication_N1N2MessageTransfer message may include a PDU Session ID, N2 SM information, and N1 SM container.
- the N2 SM information includes PDU Session ID, QFI (QoS Flow ID), QoS Profile(s), CN Tunnel Info, S-NSSAI from the Allowed NSSAI, Session-AMBR, PDU Session Type, User Plane Security Enforcement information, UE Integrity. May include Protection Maximum Data Rate.
- the N1 SM container may include a PDU session establishment acceptance message.
- the PDU session establishment acceptance message may include an authorized QoS rule, SSC mode, S-NSSAI, and an assigned IPv4 address.
- AMF transmits an N2 PDU session request message to the RAN.
- the message may include N2 SM information and 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 includes the received N2 SM information from the SMF in the N2 PDU session request message and transmits it to the RAN.
- the RAN may exchange specific signaling with the UE related to 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 PDU session ID and N1 SM information.
- the N1 SM information may include a PDU session establishment acceptance message.
- the RAN transmits a NAS message to the UE only when necessary RAN resources are set and allocation of RAN tunnel information is successful.
- the RAN transmits an N2 PDU session response message to the AMF.
- the message may include PDU session ID, cause, and N2 SM information.
- the N2 SM information may include a PDU session ID, (AN) tunnel information, and a list of allowed/rejected QoS profiles.
- -RAN tunnel information may correspond to an access network address of an N3 tunnel corresponding to a PDU session.
- the AMF may transmit the Nsmf_PDUSession_UpdateSMContext Request message to the SMF.
- the Nsmf_PDUSession_UpdateSMContext Request message may include N2 SM information.
- the AMF may be a transmission of 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 can start the N4 session modification procedure using UPF.
- SMF may provide AN tunnel information and CN tunnel information. CN tunnel information may be provided only when the SMF selects CN tunnel information in step 8.
- the UPF may transmit an N4 session modification response message to the SMF.
- the SMF transmits an Nsmf_PDUSession_UpdateSMContext Response message to the AMF.
- the AMF can deliver the related event to the SMF.
- the SMF transmits an Nsmf_PDUSession_SMContextStatusNotify message.
- SMF transmits information to the UE through UPF.
- the SMF may generate an IPv6 Router Advertisement and transmit it to the UE through N4 and UPF.
- the SMF informs the AMF.
- 8A and 8B show a procedure for modifying a PDU session.
- the MA PDU session may be established/managed based on the PDU session modification procedure.
- the PDU session modification procedure may be initiated by the UE or may be initiated by the network.
- the UE may initiate a PDU session modification procedure by transmitting a NAS message.
- the NAS message may include an N1 SM container.
- the N1 SM container may include a PDU session modification request message, a PDU session ID, and information on an integrity protection maximum data rate of the UE.
- the PDU session modification request message may include a PDU session ID, packet filter, requested QoS information, 5GSM core network capability, and the number of packet filters.
- the integrity protection maximum data rate of the UE represents the maximum data rate at which the UE can support UP integrity protection.
- the number of packet filters indicates the number of packet filters supported for QoS rules.
- the NAS message is delivered to an appropriate AMF according to the location information of the UE through the RAN. Then, the AMF transmits the Nsmf_PDUSession_UpdateSMContext message to the SMF.
- the message may include a session management (SM) context ID and an N1 SM container.
- the N1 SM container may include a PDU session modification request message.
- the PCF may inform the SMF of the policy change by initiating an SM policy association modification procedure.
- the UDM may update subscription data of the SMF by transmitting a Nudm_SDM_Notification message.
- the SMF may update session management subscriber data and transmit an ACK message to the UDM.
- the SMF may trigger QoS update.
- the SMF may perform a PDU session modification procedure.
- the AN may notify the SMF when an AN resource to which a QoS flow is mapped is released.
- the AN may transmit an N2 message to the AMF.
- the N2 message may include PDU session ID and N2 SM information.
- the N2 SM information may include QFI (QoS Flow ID), user location information, and an indication indicating that the QoS flow is released.
- the AMF may transmit an Nsmf_PDUSession_UpdateSMContext message.
- the message may include SM context ID and N2 SM information.
- the SMF may transmit a report on the subscription event by performing the SM policy alliance modification procedure. If the PDU session modification procedure is triggered by 1b or 1d, this step can be skipped. If the dynamic PCC is not deployed in the network, the SMF may apply an internal policy to determine the change of the QoS profile.
- Steps 3 to 7 described later may not be performed when PDU session modification requires only the UPF operation.
- the SMF may respond to the AMF by transmitting an Nsmf_PDUSession_UpdateSMContext message.
- the message may include N2 SM information and N2 SM container.
- the N2 SM information may include a PDU session ID, QFI, QoS profile, and session-AMBR.
- the N1 SM container may include a PDU session modification command.
- the PDU session modification command may include a PDU session ID, a QoS rule, a QuS rule operation, a QoS per QoS parameter, and a session-AMBR.
- the N2 SM information may include information to be transmitted by the AMF to the AN.
- the N2 SM information may include a QFI and a QoS profile to notify the AN that one or more QoS flows are added or modified. If PDU session modification is requested by a UE for which user plane resources are not configured, the N2 SM information to be delivered to the AN may include information on establishment of user plane resources.
- the N1 SM container may include a PDU session modification command to be transmitted from the AMF to the UE.
- the PDU session modification command may include a QoS rule and a QoS flow level QoS parameter.
- the SMF may transmit a Namf_Communication_N1N2MessageTransfer message.
- the message may include N2 SM information and N1 SM container.
- the N2 SM information may include a PDU session ID, QFI, QoS profile, and session-AMBR.
- the N1 SM container may include a PDU session modification command.
- the PDU session modification command may include a PDU session ID, a QoS rule, and a QoS flow level QoS parameter.
- the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer message, and then processes 3 to 7 described later can be skipped.
- the AMF may transmit an N1 message to synchronize the UE and the UE context.
- the AMF may transmit an N2 PDU session request message to the AN.
- the N2 PDU session request message may include N2 SM information received from the SMF and a NAS message.
- the NAS message may include a PDU session ID and an N1 SM container.
- the N1 SM container may include a PDU session modification command.
- the AN performs AN signaling exchange with the UE related to the information received from the SMF.
- a UE and RRC connection reconfiguration procedure may be performed.
- the AN transmits an N2 PDU session ACK message in response to the received N2 PDU session request.
- the N2 PDU session ACK message may include N2 SM information and user location information.
- the N2 SM information may include a list of accepted/rejected QFIs, AN tunnel information, and a PDU session ID.
- the AMF transfers the N2 SM information and user location information received from the AN to the SMF through the Nsmf_PDUSession_UpdateSMContext message. Then, the SMF delivers the Nsmf_PDUSession_UpdateSMContext message to the AMF.
- the SMF transmits an N4 session modification request message to the UPF in order to update the N4 session of the UPF included in the PDU session modification.
- the SMF updates the UL packet detection rule of the new QoS flow together with the UPF.
- the UE transmits a NAS message in response to receiving a PDU session modification command.
- the NAS message may include a PDU session ID and an N1 SM container.
- the N1 SM container may include a PDU session modification command ACK.
- the AN transmits the NAS message to the AMF.
- the AMF may transmit the N1 SM container and user location information received from the AN to the SMF through an Nsmf_PDUSession_UpdateSMContext message.
- the N1 SM container may include a PDU session modification command ACK.
- the SMF may deliver an Nsmf_PDUSession_UpdateSMContext response message to the AMF.
- the SMF transmits an N4 session modification request message to the UPF in order to update the N4 session of the UPF included in the PDU session modification.
- the message may include an N4 session ID.
- the SMF may inform the PCF whether or not the PCC determination can be performed through the SM policy alliance modification procedure.
- the SMF may notify an entity requesting user location information related to the PDU session change.
- the handover may fail if resource reservation fails in the access network.
- the SMF informs the AMF that the PDU session has been released.
- the AMF deletes all the context for the corresponding PDU session.
- the UE can no longer send and receive NAS signaling for the PDU session.
- the AMF indicates that there is no corresponding PDU session, so the UE thinks that the PDU session has been released from the network and releases the PDU session locally.
- the AMF since the AMF does not send signaling for local release to the SMF, a problem occurs in that the PDU session context remains intact in the UPF and the access network.
- the PDU session is released due to a handover failure, resulting in a problem that the user's service is disconnected.
- Disclosures of the present specification propose methods for solving the above-described problem.
- a PDU session establishment procedure In order to handover a PDU session between a current 3GPP access and a non-3GPP access, a PDU session establishment procedure is used.
- the request type when creating a new PDU session, the request type may be set to "initial request”.
- a request type When PDU session establishment is for handover, a request type may be set to "Existing PDU Session”.
- the AMF receives a PDU session establishment message, it is configured to immediately create a PDU session context.
- the PDU session is released by transmitting a context status notification message (e.g., Nsmf_PDUSession_SMcontextStatusNotify message). You can tell that it has been done.
- a context status notification message e.g., Nsmf_PDUSession_SMcontextStatusNotify message
- the context status notification message e.g., Nsmf_PDUSession_SMcontextStatusNotify message
- the AMF performs an operation of updating the access type notified by the SMF without deleting the PDU session context.
- the AMF does not immediately update the access type of the PDU session, and a notification indicating that the handover has been successfully performed from the SMF later.
- the access type can be updated. In this case, the AMF should remember that a handover is in progress.
- the AMF may recognize that the handover has failed.
- the AMF uses the NAS signaling as a different access type (e.g., not the access type (e.g., 3GPP access) of the current PDU session). , Non-3GPP access).
- the AMF When the AMF receives a notification from the SMF indicating that the PDU session handover was successful, or receives a message from the access network indicating the success of PDU setup for the PDU session in which the handover is being performed, the AMF determines that the handover has been successfully completed, and the PDU session Update the access type of.
- FIG. 9 is an exemplary diagram illustrating an example in which establishment of a new PDU session fails.
- Step 1 The terminal transmits a PDU session establishment request message to the AMF through the NG-RAN.
- Step 2 When the AMF receives the PDU session establishment request message, it creates and stores a PDU session context. If the PDU session establishment fails, the SMF transmits a PDU session establishment rejection message to the UE using a Namf_Communication_N1N2MessageTransfer Request message or an Nsmf_PDUSession_UpdateSMConext response message. Thereafter, the SMF notifies that the PDU session has been released by transmitting the Nsmf_PDUSession_SMcontextStatusNotify message.
- the SMF may notify the AMF that the PDU session has been released. In this case, the AMF deletes the related PDU session context.
- the PDU session synchronization procedure e.g., registration procedure or service request procedure
- the UE internally releases the PDU session, but the SMF has not been notified of the release, so the PDU session context remains in the NG-RAN and UPF. do.
- the SMF should not notify that the PDU session has been released. That is, the SMF needs to perform different operations according to the request type. For example, if the request type is set to "initial request”, the SMF may notify the release of the PDU session, but if the request type is set to "Existing PDU Session", the SMF shall not notify the release. .
- Proposal 1 During the PDU session establishment procedure, if the procedure fails, the SMF may notify the release of the PDU session by transmitting the Nsmf_PDUSession_SMcontextStatusNotify message only when the request type is set to "initial request".
- the AMF Even if the SMF did not notify the AMF of the release of the PDU session, another problem may arise.
- the AMF receives a PDU session establishment request message including a request type set to "Existing PDU Session"
- the AMF updates the access type of the PDU session. If the handover procedure fails, the access type of the PDU session is changed to be different from the actual access type. In this case, a problem similar to that of Problem 1 above may occur. Since the PDU session state is used to synchronize the PDU session of a particular access, the AMF can mark the PDU session as released, even if the PDU session is still available for other accesses.
- the UE internally releases the PDU session, and the SMF does not notify of the release.
- the PDU session continues to be maintained in the AN and UPF.
- the SMF notifies the AMF that the handover procedure has failed, so that the AMF updates the access type of the PDU session.
- the Nsmf_PDUSession_SMcontextStatusNotify message can be used to notify handover failure.
- the AMF When the AMF receives the notification, the AMF must update the access type of the PDU session from 3GPP access to non-3GPP access or vice versa.
- Another possible approach is for the SMF to explicitly inform the PDU session of the type of access.
- the latter scheme that is, a scheme in which the AMF updates the access type of the PDU session based on information from the SMF, may be preferred.
- Proposal 2 When the request type is set to "Existing PDU Session", the SMF may notify the handover failure of the PDU session by sending an Nsmf_PDUSession_SMcontextStatusNotify message including the access type of the PDU session.
- Proposal 3 When the AMF receives the notification of the handover failure from the SMF, the AMF may update the access type of the PDU session based on the information from the SMF.
- 10A and 10B are exemplary diagrams illustrating a PDU session establishment procedure for non-roaming and local breakout (LBO) roaming.
- the PDU session establishment procedure shown in FIGS. 10A and 10B is mostly the same as the procedure shown in FIGS. 7A and 7B. Accordingly, a detailed description of the same procedure will be omitted, and the description of the procedure of FIGS. 7A and 7B will be used as it is.
- Step 18 SMF transmits Nsmf_PDUSession_SMcontextStatusNotify message to AMF
- the SMF When the PDU session establishment is not successful and the SMF receives a PDU session establishment request message including a request type set to "initial request", the SMF notifies the AMF by sending an Nsmf_PDUSession_SMcontextStatusNotify message. In addition, the SMF releases the N4 session and PDU session address (eg, IP address), and also releases the association with the PCF.
- N4 session and PDU session address eg, IP address
- the SMF cancels the handover procedure and includes status information and cause information.
- the handover failure is notified to the AMF by sending the Nsmf_PDUSession_SMcontextStatusNotify message.
- the SMF includes information on the related access of the PDU session in the state information.
- the AMF updates the associated access type of the PDU session based on the received information.
- the SMF initiates an SM policy association modification procedure to report a change in access.
- 11A and 11B are exemplary diagrams illustrating a procedure for establishing a PDU session for HR roaming.
- Step 1 This step is the same as Step 1 shown in Fig. 7A
- the AMF selects the SMF in the HPLMN using the S-NSSAI having the value defined by the HPLMN.
- the AMF may receive information on an alternative H-SMF from the NRF.
- AMF may store S-NSSAI, DNN, PDU session ID, SMF ID in VPLMN, and access type of PDU session.
- Step 3 In the LBO roaming case, when the V-SMF informs the AMF that the V-SMF cannot process part of the N2 SM information, the AMF proceeds to the step for the HR roaming method, and is different from the V-SMF selected above. Select SMF in VPLMN.
- Step 3a The AMF provides the identifier of the H-SMF selected in step 2, the VPLMN S-NSSAI from the Allowed NSSAI and the corresponding S-NSSAI of the HPLMN.
- H-SMF is provided.
- AMF provides the H-SMF identifier.
- -V-SMF delivers this information to H-SMF without using the DNN selection mode received from AMF.
- the AMF contains the ID of the H-PCF and the V-SMF passes it to the H-SMF.
- Step 3b If the PDU session type is "Unstructured” and the V-SMF receives the "Invoke NEF" flag, steps 4 and 5 may not be performed.
- Step 4 V-SMF selects UPF in VPLMN.
- Step 5 The V-SMF performs an N4 session establishment procedure with the selected V-UPF.
- Step 5a The V-SMF transmits an N4 session establishment request message to the V-UPF. If CN tunnel information is allocated by the SMF, the CN tunnel information can be delivered to the V-UPF.
- Step 5b The V-UPF responds by sending an N4 session establishment response message. If the CN tunnel information is allocated by the V-UPF, the CN tunnel information may be delivered to the V-SMF.
- the V-SMF may transmit an Nsmf_PDUSession_Create request message to the H-SMF.
- the message is S-NSSAI, PDU session ID, V-SMF ID, V-CN-Tunnel-Info, PDU session type, PCO with values defined by SUPI, GPSI, V-SMF SM context ID, DNN, and HPLMN. , The number of packet filters, user location information, access type, PCF ID, SM PDU DN request container, DNN selection mode, AMF ID, and the like.
- the H-SMF needs to establish a PDU session (eg, an SSC mode or an SM PDU DN request container to be used to authenticate the UE).
- the H-SMF may use the DNN selection mode when deciding to accept or reject the UE's request.
- the V-SMF may establish a PDU session with one of the interpersonal H-SMFs according to the operator policy.
- the V-SMF SM context ID includes address information allocated for a service operation related to a PDU session.
- H-SMF stores the relationship between the PDU session and the V-SMF context ID.
- H-SMF can provide H-SMF SM context ID allocated for service operation related to this PDU session to V-SMF. have.
- Step 7-12b These steps are the same as steps 4 to 10 of FIG. 7A. However, there are differences as follows.
- H-SMF may not provide an inactivity timer to H-UPF.
- Step 5 of FIG. 7A may not be performed.
- Step 12c This step is the same as step 16c of Fig. 7B.
- the Nudm_UECM_Registration message includes S-NSSAI, PDU session ID including values defined in SUPI, DNN, and HPLMN.
- the H-SMF transmits an Nsmf_PDUSession_Create response message to the V-SMF.
- the Nsmf_PDUSession_Create response message is a QoS rule, QoS flow level QoS parameter, PCO including session level information that V-SMF cannot understand, selected PDU session type, SSC mode, H-CN tunnel information, QFI, QoS profile, reflection formula It may contain information required by the QoS timer V-SMF.
- the H-SMF determines whether the request is accepted by including an always-on PDU session approval indication in the response message to the V-SMF. I can tell you.
- H-SMF determines that the PDU session needs to be established as an always-on PDU session
- H-SMF is an always-on PDU session approval indication It can be notified to V-SMF by including.
- the H-CN tunnel information includes tunnel information for uplink traffic directed to H-UPF.
- QoS rules and QoS flow level QoS parameters may be included in the Nsmf_PDUSession_Create message.
- Step 14-18 These steps are the same as steps 11-15 of FIG. 7B. Hereinafter, only the differences will be described.
- the V-SMF stores the relationship between the PDU session and the H-SMF ID.
- the V-SMF checks whether the PDU session can be established as an always-on PDU session based on an internal policy.
- the V-SMF includes an always-on PDU session granted indication indicating whether the PDU session is an always-on PDU session in the PDU session establishment acceptance message and transmits it to the UE.
- step 19 may not be performed.
- Step 19a The V-SMF initiates the V-UPF and N4 session modification procedure.
- the V-SMF provides packet detection, enforcement and reporting rules, AN tunnel information, H-CN tunnel information, and V-CN tunnel information to be installed in the V-UPF for the PDU session.
- Step 19b V-UPF provides N4 session modification response to V-SMF.
- the V-UPF delivers the downlink packet to be buffered for the PDU session to the UE.
- Step 20 This step is the same as Step 17 in Fig. 7B. However, there are differences as follows.
- the SMF is the V-SMF, and the H-SMF and the V-SMF transmit a subscription request message to the AMF for a UE reachability event.
- Step 21 This step is the same as Step 18 of Fig. 7B.
- the V-SMF releases the PDU session. Initiate the procedure.
- the V-SMF cancels the handover procedure. And, by transmitting an Nsmf_PDUSession_Update request message including the access type and cause information, this may be notified to the H-SMF.
- the H-SMF may initiate an SM policy association modification procedure to report a change in access.
- the Nsmf_PDUSession_SMcontextStatusNotify message including status information and cause information the V-SMF can notify the AMF of the handover failure.
- the V-SMF may indicate related access of a PDU session in state information.
- the AMF may update the associated access of the PDU session based on the received information.
- Step 22 The H-SMF transfers the IPv6 address setting to the UE through the H-UPF and the V-UPF in the VPLMN.
- H-SMF When the PDU session type is IP6 or IPv4v6, H-SMF generates an IPv6 router advertisement and delivers it to the UE and H-UPF and V-UPF through N4.
- Step 23 If the indication received in step 18 by the V-SMF indicates that the access network (AN) rejects some QFI, the V-SMF notifies the H-SMF by sending an Nsmf_PDUSession_Update request message. If necessary for QoS flows related to QoS rules, the H-SMF is responsible for updating the QoS rules and QoS flow level QoS parameters.
- Step 24 This step is the same as step 20 of Fig. 7B. However, there are differences as follows.
- This step is performed in HPLMN.
- the SMF performs a deregistration procedure for a given PDU session by using a Nudm_UECM_Deregistration message including SUPI, DNN, and PDU session ID.
- the UDM updates the corresponding UE context by transmitting a Nudr_DM_Update message including SUPI, atmospheric pressure data, and UE context.
- FIG. 12 is an exemplary diagram illustrating an example in which handover from a non-3GPP access to a 3GPP access fails in a non-roaming or LBO robang scheme.
- Step 1 It is assumed that the UE has established a PDU session through non-3GPP access.
- the UE transmits a PDU session establishment request message including a request type set to "Existing PDU Session" and a PDU session ID of a non-3GPP access PDU session in order to handover a PDU session over a non-3GPP access to a 3GPP access.
- Step 2 Upon receiving the message from the UE, the AMF updates the access type information of the non-3GPP PDU session to 3GPP access based on the PDU session ID information.
- Step 3-4 The AMF selects an SMF based on the PDU session ID information, and transmits a PDU session establishment request message including the request type to the selected SMF.
- the SMF may determine that the UE has requested a handover of a PDU session over a non-3GPP access to 3GPP access based on the PDU session ID information in the received message and a request set to “Existing PDU Session”.
- the SMF generates N2 SM information for user plane setup with 3GPP access while granting the request of the UE and transmits it to the AMF together with a PDU session establishment acceptance message.
- Step 6 The AMF transmits the N2 SM information received from the SMF and the PDU session establishment acceptance message to the NG-RAN.
- the NG-RAN may reject the SMF request due to lack of radio resources or the like. In this case, the NG-RAN does not deliver the PDU session establishment acceptance message received from the SMF to the UE, and informs that the PDU session has not been established in response to the N2 SM information.
- Step 8-9 The AMF transmits the N2 SM information received from the NG-RAN to the SMF.
- Step 10-11 Based on the response from the NG-RAN, the SMF knows that the user plane setup has failed and transmits a PDU session establishment rejection message to inform that the request of the UE is not accepted.
- Step 12 The SMF transmits the Nsmf_PDUSession_SMcontextStatusNotify message to update the access type information of the PDU session stored in the AMF.
- the access type information is set to non-3GPP and transmitted. Also, a cause indicating that the handover has failed is set.
- Step 13 The AMF updates the access type of the PDU session with the information sent by the SMF, that is, non-3GPP access, based on the information sent by the SMF.
- FIGS. 13A and 13B are exemplary diagrams illustrating an example in which a handover from a non-3GPP access to a 3GPP access fails in an HR roaming scheme.
- Step 1 It is assumed that the UE has established a PDU session through non-3GPP access.
- the UE transmits a PDU session establishment request message including a request type set to "Existing PDU Session" and a PDU session ID of a non-3GPP access PDU session in order to handover a PDU session over a non-3GPP access to a 3GPP access.
- Step 2 The AMF updates the access type information of the non-3GPP PDU session to 3GPP access based on the PDU session ID information in the message received from the UE.
- Step 3-4 The AMF selects the V-SMF based on information (eg, DNN, S-NSSAI) in the message received from the UE, and also selects the H-SMF based on the PDU session ID information of the UE.
- the AMF transmits the PDU session establishment request message to the V-SMF and also transmits the request type sent by the UE. At this time, the H-SMF information selected by AMF is also transmitted.
- the V-SMF delivers the information sent by the AMF to the H-SMF identified based on the H-SMF information received from the AMF.
- the H-SMF may determine that the UE requests handover of a PDU session over non-3GPP access to 3GPP access based on the PDU session ID information in the message received from the UE and the request type set to “Existing PDU Session”.
- the H-SMF informs the V-SMF that the UE's request is allowed.
- Step 7 The V-SMF generates N2 SM information for user plane setup with 3GPP access while granting the request of the UE and transmits it to the AMF together with a PDU session establishment acceptance message.
- Step 8 The AMF transmits the N2 SM information received from the V-SMF and the PDU session establishment acceptance message to the NG-RAN.
- the NG-RAN may reject the request of the V-SMF for reasons such as lack of radio resources.
- the NG-RAN does not transmit the PDU session establishment acceptance message received from the V-SMF to the UE, and includes information indicating that the PDU session has not been established in the response to the N2 SM information.
- Step 10-11 The AMF transmits the N2 SM information received from the NG-RAN to the V-SMF.
- Steps 12-13 The V-SMF notifies the H-SMF that the user plane setup has failed based on the user plane setup response from the NG-RAN.
- Steps 14-15 Since the user plane resource setup has failed, the V-SMF transmits a PDU session establishment rejection message to the UE in order to reject the handover request from the UE.
- Step 16 Since the PDU session handover has failed, the H-SMF transmits an Nsmf_PDUSession_StatusNotify message to clear the PDU session context of the 3GPP access side.
- Step 17 The V-SMF transmits the Nsmf_PDUSession_SMcontextStatusNotify message to clear the PDU session context of the AMF. And the V-SMF deletes the context related to the PDU session. Upon receiving this, the AMF deletes the context related to the PDU session.
- the SMF When the SMF receives a PDU session establishment request message including a request type set to "initial request”, if the PDU session establishment fails, it may notify that the PDU session is released by transmitting an Nsmf_PDUSession_SMcontextStatusNotify message to the AMF.
- the SMF When the SMF receives a PDU session establishment request message including a request type set to "Existing PDU Session”, if PDU session establishment fails, it sends an Nsmf_PDUSession_SMcontextStatusNotify message to AMF to notify the handover failure and inform the access type of the PDU session. have.
- the AMF may update the access type of the PDU session based on the access type included in the Nsmf_PDUSession_SMcontextStatusNotify message received from the SMF.
- the AMF When the AMF receives a PDU session establishment request message including a request type set to "Existing PDU Session", it may be determined that handover is in progress without updating the access type of the PDU session immediately.
- NAS signaling can be transmitted with an access type opposite to the access type (eg, 3GPP access) of the PDU session (eg, non-3GPP access).
- the AMF When receiving the Nsmf_PDUSession_SMcontextStatusNotify message notifying that the PDU session has been released from the SMF, the AMF recognizes that the handover of the PDU session has failed, and may determine that the handover transmission has ended.
- the UE may allow the service to be supported seamlessly.
- FIG. 14 is a block diagram illustrating a configuration of a processor in which the disclosure of the present specification is implemented.
- the processor 1020 in which the disclosure of the present specification is implemented includes a plurality of circuits to implement the proposed functions, procedures, and/or methods described herein. can do.
- the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3.
- the processor 1020 may include more circuits. Each circuit may include a plurality of transistors.
- the processor 1020 may be referred to as an application-specific integrated circuit (ASIC) or an application processor (AP), and includes at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphics processing unit (GPU). can do.
- ASIC application-specific integrated circuit
- AP application processor
- DSP digital signal processor
- CPU central processing unit
- GPU graphics processing unit
- the processor may be included in the UE, the base station, AMF or SMF.
- the first circuit 1010-1 of the processor included in the AMF may receive a session management (SM) context status notification message from a session management function (SMF).
- SM session management
- SMF session management function
- the SM context status notification message may be received based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU protocol data unit
- the PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- a non-3GPP non-3rd Generation Partnership Project
- the second circuit 1020-2 of the processor included in the AMF may update the access type related to the PDU session based on the SM context status notification message.
- the third circuit 1020-3 of the processor included in the AMF may receive a PDU session establishment request message from the AMF user equipment (UE).
- the PDU session establishment request message may include a request type set to "Existing PDU Session".
- the SM context status notification message may include information indicating that handover of the PDU session has failed.
- the SM context status notification message may include information on an access type for the PDU session after handover failure.
- Updating the access type may be performed based on information on the access type included in the SM context status notification message.
- Information on the access type for the PDU session may indicate the non-3GPP access based on the failure of handover of the PDU session between the non-3GPP access and the 3GPP access.
- the access type associated with the PDU session may be updated to the non-3GPP access.
- a fourth circuit (not shown) of the processor included in the AMF may not release the PDU session based on the failure of the PDU session establishment procedure.
- the failure of the PDU session establishment procedure may be based on a resource setup failure of an Access Network (AN).
- AN Access Network
- the first circuit 1010-1 of the processor included in the SMF may transmit a session management (SM) context status notification message to an access and mobility management function (AMF).
- SM session management
- AMF access and mobility management function
- the SM context status notification message may be transmitted based on a failure of a protocol data unit (PDU) session establishment procedure.
- PDU protocol data unit
- the PDU session establishment procedure may be triggered for handover of a PDU session between a non-3GPP (non-3rd Generation Partnership Project) access and a 3GPP access.
- a non-3GPP non-3rd Generation Partnership Project
- the SM context status notification message may include information on an access type related to the PDU session.
- the SM context status notification message may include information indicating that handover of the PDU session has failed.
- the SM context status notification message may include information on an access type for the PDU session after a handover failure.
- Information on the access type for the PDU session may indicate the non-3GPP access based on the failure of handover of the PDU session between the non-3GPP access and the 3GPP access.
- 15 shows a wireless communication system according to an embodiment.
- the wireless communication system may include a first device 100a and a second device 100b.
- the first device 100a may be the UE described in the disclosure of this specification.
- the first device 100a is a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle).
- UAV Ultrasound Vehicle
- AI Artificial Intelligence
- robots Augmented Reality (AR) devices, Virtual Reality (VR) devices, Mixed Reality (MR) devices, hologram devices, public safety devices, MTC devices, IoT devices, medical devices, It may be a fintech device (or financial device), a security device, a climate/environment device, a device related to 5G service, or a device related to the fourth industrial revolution field.
- AR Augmented Reality
- VR Virtual Reality
- MR Mixed Reality
- hologram devices public safety devices
- MTC devices IoT devices
- medical devices It may be a fintech device (or financial device), a security device, a climate/environment device, a device related to 5G service, or a device related to the fourth industrial revolution field.
- the second device 100b may be a network node (eg, AMF or MME) described in the disclosure of the present specification.
- the second device 100b is a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial).
- UAV Vehicle
- AI Artificial Intelligence
- robot Robot
- AR Augmented Reality
- VR Virtual Reality
- MR Magnetic Reality
- hologram device public safety device
- MTC International Mobile communications
- IoT medical device
- Fintech devices or financial devices
- security devices climate/environment devices, devices related to 5G services, or other devices related to the 4th industrial revolution field.
- the UE 100 is a mobile phone, a smart phone, a laptop computer, a digital broadcasting UE device, a personal digital assistants (PDA), a portable multimedia player (PMP), a navigation system, and a slate PC.
- PDA personal digital assistants
- PMP portable multimedia player
- PC tablet PC
- ultrabook wearable device, for example, a watch-type UE device (smartwatch), a glass-type UE device (smart glass), HMD (head mounted display)) And the like.
- the HMD may be a display device worn on the head.
- HMD can be used to implement VR, AR or MR.
- a drone may be a vehicle that is not human and is flying by a radio control signal.
- the VR device may include a device that implements an object or a background of a virtual world.
- the AR device may include a device that connects and implements an object or background of a virtual world, such as an object or background of the real world.
- the MR device may include a device that combines and implements an object or background of a virtual world, such as an object or background of the real world.
- the hologram device may include a device that implements a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing an interference phenomenon of light generated by the encounter of two laser lights called holography.
- the public safety device may include an image relay device or an image device that can be worn on a user's human body.
- the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation.
- the MTC device and the IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors.
- the medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating or preventing a disease.
- the medical device may be a device used for the purpose of diagnosing, treating, alleviating or correcting an injury or disorder.
- a medical device may be a device used for the purpose of examining, replacing or modifying a structure or function.
- the medical device may be a device used for the purpose of controlling pregnancy.
- the medical device may include a device for treatment, a device for surgery, a device for diagnosis (extra-corporeal), a device for hearing aids or a procedure.
- the security device may be a device installed to prevent a risk that may occur and maintain safety.
- the security device may be a camera, CCTV, recorder, or black box.
- the fintech device may be a device capable of providing financial services such as mobile payment.
- the fintech device may include a payment device or a point of sales (POS).
- the climate/environment device may include a device that monitors or predicts the climate/environment.
- the first device 100a may include at least one or more processors such as the processor 1020a, at least one or more memories such as the memory 1010a, and at least one or more transceivers such as the transceiver 1031a.
- the processor 1020a may perform the functions, procedures, and/or methods described above.
- the processor 1020a may perform one or more protocols.
- the processor 1020a may perform one or more layers of a radio interface protocol.
- the memory 1010a is connected to the processor 1020a and may store various types of information and/or commands.
- the transceiver 1031a may be connected to the processor 1020a and controlled to transmit and receive radio signals.
- the second device 100b may include at least one processor such as a processor 1020b, at least one memory device such as a memory 1010b, and at least one transceiver such as a transceiver 1031b.
- the processor 1020b may perform the functions, procedures, and/or methods described above.
- the processor 1020b may implement one or more protocols.
- the processor 1020b may implement one or more layers of a radio interface protocol.
- the memory 1010b is connected to the processor 1020b and may store various types of information and/or commands.
- the transceiver 1031b may be connected to the processor 1020b and controlled to transmit and receive wireless signals.
- the memory 1010a and/or the memory 1010b may be respectively connected inside or outside the processor 1020a and/or the processor 1020b, or other processors through various technologies such as wired or wireless connection. It can also be connected to.
- the first device 100a and/or the second device 100b may have one or more antennas.
- the antenna 1036a and/or the antenna 1036b may be configured to transmit and receive wireless signals.
- FIG. 16 illustrates a block diagram of a network node according to an embodiment.
- FIG. 16 is a diagram illustrating in detail a case where a base station is divided into a central unit (CU) and a distributed unit (DU).
- CU central unit
- DU distributed unit
- the base stations W20 and W30 may be connected to the core network W10, and the base station W30 may be connected to the neighboring base station W20.
- an interface between the base stations W20 and W30 and the core network W10 may be referred to as NG, and an interface between the base station W30 and neighboring base stations W20 may be referred to as Xn.
- the base station W30 may be divided into CU (W32) and DU (W34, W36). That is, the base station W30 may be hierarchically separated and operated.
- the CU (W32) may be connected to one or more DUs (W34, W36), for example, the interface between the CU (W32) and the DU (W34, W36) may be referred to as F1.
- the CU (W32) may perform the function of upper layers of the base station, and the DUs (W34, W36) may perform the function of lower layers of the base station.
- the CU (W32) is a logical node that hosts radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers of a base station (eg, gNB)
- RRC radio resource control
- SDAP service data adaptation protocol
- PDCP packet data convergence protocol
- the DUs W34 and W36 may be logical nodes hosting radio link control (RLC), media access control (MAC), and physical (PHY) layers of the base station.
- the CU (W32) may be a logical node hosting the RRC and PDCP layers of the base station (eg, en-gNB).
- One DU (W34, W36) may support one or more cells. One cell can be supported by only one DU (W34, W36).
- One DU (W34, W36) may be connected to one CU (W32), and one DU (W34, W36) may be connected to a plurality of CUs by appropriate implementation.
- 17 is a block diagram showing the configuration of the UE 100 according to an embodiment.
- the UE 100 illustrated in FIG. 17 is a diagram illustrating the first device of FIG. 15 in more detail.
- the UE 100 includes a memory 1010, a processor 1020, a transmission/reception unit 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042, and a microphone ( 1052), a subscriber identification module (SIM) card, and one or more antennas.
- a memory 1010 a processor 1020, a transmission/reception unit 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042, and a microphone ( 1052), a subscriber identification module (SIM) card, and one or more antennas.
- SIM subscriber identification module
- the processor 1020 may be configured to implement the proposed functions, procedures and/or methods described herein. Layers of the air interface protocol may be implemented in the processor 1020.
- the processor 1020 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and/or a data processing device.
- the processor 1020 may be an application processor (AP).
- the processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator).
- DSP digital signal processor
- CPU central processing unit
- GPU graphics processing unit
- modem modulator and demodulator
- processor 1020 examples include SNAPDRAGONTM series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIOTM series processors manufactured by MediaTek®, INTEL®. It may be an ATOMTM series processor manufactured by or a corresponding next-generation processor.
- the power management module 1091 manages power for the processor 1020 and/or the transceiver 1031.
- the battery 1092 supplies power to the power management module 1091.
- the display 1041 outputs a result processed by the processor 1020.
- the input unit 1053 receives an input to be used by the processor 1020.
- the input unit 1053 may be displayed on the display 1041.
- the SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone and a computer and a key associated therewith. You can even store contact information on many SIM cards.
- IMSI international mobile subscriber identity
- the memory 1010 is operatively coupled to the processor 1020 and stores various information for operating the processor 610.
- the memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and/or other storage device.
- ROM read-only memory
- RAM random access memory
- flash memory memory card
- storage medium storage medium
- other storage device any storage device that stores the instructions for the processor 610.
- modules may be stored in memory 1010 and executed by processor 1020.
- the memory 1010 may be implemented inside the processor 1020. Alternatively, the memory 1010 may be implemented outside the processor 1020 and may be communicatively connected to the processor 1020 through various means known in the art.
- the transceiver 1031 is operatively coupled to the processor 1020 and transmits and/or receives a radio signal.
- the transceiver 1031 includes a transmitter and a receiver.
- the transceiver 1031 may include a baseband circuit for processing radio frequency signals.
- the transceiver controls one or more antennas to transmit and/or receive radio signals.
- the processor 1020 transmits command information to the transmission/reception unit 1031 to transmit, for example, a radio signal constituting voice communication data in order to initiate communication.
- the antenna functions to transmit and receive radio signals.
- the transmission/reception unit 1031 may transmit a signal for processing by the processor 1020 and convert the signal into a baseband.
- the processed signal may be converted into audible or readable information output through the speaker 1042.
- the speaker 1042 outputs a sound-related result processed by the processor 1020.
- the microphone 1052 receives a sound related input to be used by the processor 1020.
- the user for example, presses (or touches) a button of the input unit 1053 or inputs command information such as a phone number by voice driving (voice activation) using the microphone 1052.
- the processor 1020 receives the command information and processes to perform an appropriate function, such as dialing a phone number. Operational data may be extracted from the SIM card or the memory 1010. In addition, the processor 1020 may display command information or driving information on the display 1041 for user recognition and convenience.
- FIG. 18 is a block diagram showing in detail a transmission/reception unit of the first device shown in FIG. 15 or a transmission/reception unit of the device shown in FIG. 17.
- the transmission/reception unit 1031 includes a transmitter 1031-1 and a receiver 1031-2.
- the transmitter 1031-1 includes a DFT (Discrete Fourier Transform) unit 1031-11, a subcarrier mapper 1031-12, an IFFT unit 1031-13 and a CP insertion unit 1031-14, and a wireless transmission unit 1031 -15).
- the transmitter 1031-1 may further include a modulator.
- it may further include a scramble unit (not shown; a scramble unit), a modulation mapper (not shown; a modulation mapper), a layer mapper (not shown; a layer mapper), and a layer permutator (not shown; a layer permutator),
- a scramble unit not shown; a scramble unit
- a modulation mapper not shown; a modulation mapper
- a layer mapper not shown; a layer mapper
- a layer permutator not shown; a layer permutator
- an Inverse Fast Fourier Transform (IFFT) unit 1031- 13 After performing subcarrier mapping of the signal spread by the DFT unit 1031-11 (or precoded in the same sense) through the subcarrier mapper 1031-12, an Inverse Fast Fourier Transform (IFFT) unit 1031- 13) to make a signal on the time axis.
- IFFT Inverse Fast Fourier Transform
- the DFT unit 1031-11 outputs complex-valued symbols by performing DFT on input symbols. For example, when Ntx symbols are input (however, Ntx is a natural number), the DFT size is Ntx.
- the DFT unit 1031-11 may be referred to as a transform precoder.
- the subcarrier mapper 1031-12 maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to a resource block allocated for data transmission.
- the subcarrier mapper 1031-12 may be called a resource element mapper.
- the IFFT unit 1031-13 outputs a baseband signal for data, which is a time domain signal, by performing IFFT on the input symbol.
- the CP insertion unit 1031-14 copies a part of the rear part of the baseband signal for data and inserts it into the front part of the baseband signal for data.
- ISI Inter-symbol Interference
- ICI Inter-Carrier Interference
- the receiver 1031-2 includes a radio receiver 1031-21, a CP removal unit 1031-22, an FFT unit 1031-23, an equalization unit 1031-24, and the like.
- the wireless receiving unit 1031 -21, CP removing unit 1031 -22, and FFT unit 1031 -23 of the receiver 1031-2 are a wireless transmission unit 1031-15 at the transmitting end 1031-1, It performs the reverse function of the CP insertion unit 1031-14 and the IFF unit 1031-13.
- the receiver 1031-2 may further include a demodulator.
- a communication system 1 applied to the disclosure of the present specification includes a wireless device, a base station, and a network.
- the wireless device refers to a device that performs communication using a wireless access technology (eg, 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication/wireless/5G device.
- wireless devices include robots 100a, vehicles 100b-1 and 100b-2, eXtended Reality (XR) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400.
- the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, and the like.
- the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone).
- UAV Unmanned Aerial Vehicle
- XR devices include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices. It can be implemented in the form of a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like.
- Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), computers (eg, notebook computers, etc.).
- Home appliances may include TVs, refrigerators, washing machines, and the like.
- IoT devices may include sensors, smart meters, and the like.
- the base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station/network node to other
- the wireless devices 100a to 100f may be connected to the network 300 through the base station 200.
- AI Artificial Intelligence
- the network 300 may be configured using a 3G network, a 4G (eg, LTE) network, or a 5G (eg, NR) network.
- the wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but may communicate directly (e.g. sidelink communication) without passing through the base station/network.
- the vehicles 100b-1 and 100b-2 may perform direct communication (e.g.
- V2V Vehicle to Vehicle
- V2X Vehicle to Everything
- the IoT device eg, sensor
- the IoT device may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.
- Wireless communication/connections 150a, 150b, and 150c may be established between the wireless devices 100a to 100f/base station 200, and the base station 200/base station 200.
- wireless communication/connection includes various wireless access such as uplink/downlink communication 150a and sidelink communication 150b (or D2D communication), base station communication 150c (eg relay, Integrated Access Backhaul). This can be achieved through technology (eg 5G NR)
- the wireless communication/connection 150a, 150b, 150c may transmit/receive signals through various physical channels.
- transmission/reception of radio signals At least some of a process of setting various configuration information for, a process of processing various signals (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and a resource allocation process may be performed.
- a process of processing various signals eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.
- a resource allocation process may be performed.
- the claims set forth herein may be combined in a variety of ways.
- the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method.
- the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
레퍼런스 포인트 | 설명 |
S1-MME | E-UTRAN와 MME 간의 제어 평면 프로토콜에 대한 레퍼런스 포인트 |
S1-U | 핸드오버 동안 eNB 간 경로 스위칭 및 베어러 당 사용자 평면 터널링에 대한 E-UTRAN와 SGW 간의 레퍼런스 포인트 |
S3 | 유휴(Idle) 및/또는 활성화 상태에서 3GPP 액세스 네트워크 간 이동성에 대한 사용자 및 베어러 정보 교환을 제공하는 MME와 SGSN 간의 레퍼런스 포인트. 이 레퍼런스 포인트는 PLMN(Public Land Mobile Network)-내 또는 PLMN-간(예를 들어, PLMN-간 핸드오버의 경우)에 사용될 수 있음) |
S4 | GPRS 코어와 SGW의 3GPP 앵커 기능 간의 관련 제어 및 이동성 지원을 제공하는 SGW와 SGSN 간의 레퍼런스 포인트. 또한, 직접 터널이 수립되지 않으면, 사용자 평면 터널링을 제공함 |
S5 | SGW와 PDN GW 간의 사용자 평면 터널링 및 터널 관리를 제공하는 레퍼런스 포인트. UE 이동성으로 인해, 그리고 요구되는 PDN 커넥션성을 위해서 SGW가 함께 위치하지 않은 PDN GW로의 연결이 필요한 경우, SGW 재배치를 위해서 사용됨 |
S11 | MME와 SGW 간의 레퍼런스 포인트 |
SGi | PDN GW와 PDN 간의 레퍼런스 포인트. PDN은, 오퍼레이터 외부 공용 또는 사설 PDN이거나 예를 들어, IMS 서비스의 제공을 위한 오퍼레이터-내 PDN일 수 있음. 이 레퍼런스 포인트는 3GPP 액세스의 Gi에 해당함 |
Frequency Range designation | Corresponding frequency range | Subcarrier Spacing |
FR1 | 450MHz - 6000MHz | 15, 30, 60kHz |
FR2 | 24250MHz - 52600MHz | 60, 120, 240kHz |
Frequency Range designation | Corresponding frequency range | Subcarrier Spacing |
FR1 | 410MHz - 7125MHz | 15, 30, 60kHz |
FR2 | 24250MHz - 52600MHz | 60, 120, 240kHz |
Claims (20)
- AMF(Access and Mobility management Function)의 동작 방법으로서,SMF(Session Management Function)으로부터, SM(Session Management) 컨텍스트 상태 통지 메시지를 수신하는 단계와,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 수신되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고;상기 SM 컨텍스트 상태 통지 메시지에 기초하여, 상기 PDU 세션과 관련된 액세스 타입을 업데이트하는 단계를 포함하는 방법.
- 제1항에 있어서,상기 AMF가 UE(User Equipment)로부터 PDU 세션 수립 요청 메시지를 수신하는 단계를 더 포함하고,상기 PDU 세션 수립 요청 메시지는 "Existing PDU Session"으로 설정된 요청 타입을 포함하는 방법.
- 제1항에 있어서,상기 SM 컨텍스트 상태 통지 메시지는 상기 PDU 세션의 핸드오버가 실패했음을 알리는 정보를 포함하는 방법.
- 제1항에 있어서, 상기 SM 컨텍스트 상태 통지 메시지는핸드오버 실패 이후에, 상기 PDU 세션을 위한 액세스 타입에 대한 정보를 포함하는 방법.
- 제5항에 있어서, 상기 액세스 타입을 업데이트하는 단계는상기 SM 컨텍스트 상태 통지 메시지 내에 포함된 상기 액세스 타입에 대한 정보에 기초하여 수행되는 방법.
- 제5항에 있어서, 상기 PDU 세션을 위한 액세스 타입에 대한 정보는상기 비-3GPP 액세스와 3GPP 액세스 간에 상기 PDU 세션의 핸드오버가 실패되는 것에 기초하여, 상기 비-3GPP 액세스를 나타내는 방법.
- 제1항에 있어서,상기 비-3GPP 액세스와 3GPP 액세스 간에 상기 PDU 세션의 핸드오버가 실패되는 것에 기초하여, 상기 PDU 세션과 관련된 액세스 타입은 상기 비-3GPP 액세스로 업데이트되는 방법.
- 제1항에 있어서,상기 PDU 세션 수립 절차의 실패에 기초하여, 상기 PDU 세션을 해제하지 않는 단계를 더 포함하는 방법.
- 제1항에 있어서, 상기 PDU 세션 수립 절차의 실패는 AN(Access Network)의 자원 셋업 실패에 기초한 방법.
- SMF(Session Management Function)의 동작 방법으로서,SM(Session Management) 컨텍스트 상태 통지 메시지를 AMF(Access and Mobility management Function)로 전송하는 단계를 포함하고,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 전송되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고,상기 SM 컨텍스트 상태 통지 메시지는 상기 PDU 세션과 관련된 액세스 타입에 대한 정보를 포함하는 방법.
- 제10항에 있어서,상기 SM 컨텍스트 상태 통지 메시지는 상기 PDU 세션의 핸드오버가 실패했음을 알리는 정보를 포함하는 방법.
- 제10항에 있어서, 상기 SM 컨텍스트 상태 통지 메시지는핸드오버 실패 이후에, 상기 PDU 세션을 위한 액세스 타입에 대한 정보를 포함하는 방법.
- 제10항에 있어서, 상기 PDU 세션을 위한 액세스 타입에 대한 정보는상기 비-3GPP 액세스와 3GPP 액세스 간에 상기 PDU 세션의 핸드오버가 실패되는 것에 기초하여, 상기 비-3GPP 액세스를 나타내는 방법.
- AMF(Access and Mobility management Function)에 장착되는 칩셋으로서,적어도 하나의 프로세서와;명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고, 상기 명령어가 상기 적어도 하나의 프로세서에 의해서 실행되는 것에 기초하여, 수행되는 동작은:SMF(Session Management Function)으로부터, SM(Session Management) 컨텍스트 상태 통지 메시지를 수신하는 단계와,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 수신되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고;상기 SM 컨텍스트 상태 통지 메시지에 기초하여, 상기 PDU 세션과 관련된 액세스 타입을 업데이트하는 단계를 포함하는 칩셋.
- 제14항에 있어서,상기 SM 컨텍스트 상태 통지 메시지는 상기 PDU 세션의 핸드오버가 실패했음을 알리는 정보를 포함하는 칩셋.
- 제14항에 있어서, 상기 SM 컨텍스트 상태 통지 메시지는핸드오버 실패 이후에, 상기 PDU 세션을 위한 액세스 타입에 대한 정보를 포함하는 칩셋.
- AMF(Access and Mobility management Function)을 위한 장치로서,송수신부와;적어도 하나의 프로세서와; 그리고명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고,상기 명령어가 상기 적어도 하나의 프로세서에 의해서 실행되는 것에 기초하여, 수행되는 동작은:SMF(Session Management Function)으로부터, SM(Session Management) 컨텍스트 상태 통지 메시지를 수신하는 단계와,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 수신되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고;상기 SM 컨텍스트 상태 통지 메시지에 기초하여, 상기 PDU 세션과 관련된 액세스 타입을 업데이트하는 단계를 포함하는 장치.
- 명령어들을 기록하고 있는 비휘발성(non-volatile) 컴퓨터 판독가능 저장 매체로서,명령어들을 포함하고,상기 명령어들은, AMF(Access and Mobility management Function)을 위한 장치 내의 하나 이상의 프로세서들에 의해 실행될 때, 상기 하나 이상의 프로세서들로 하여금 동작을 수행하도록 하고:상기 동작은:SMF(Session Management Function)으로부터, SM(Session Management) 컨텍스트 상태 통지 메시지를 수신하는 단계와,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 수신되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고;상기 SM 컨텍스트 상태 통지 메시지에 기초하여, 상기 PDU 세션과 관련된 액세스 타입을 업데이트하는 단계를포함하는 컴퓨터 판독가능한 저장 매체.
- SMF(Session Management Function)에 장착되는 칩셋으로서,적어도 하나의 프로세서와;명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고, 상기 명령어가 상기 적어도 하나의 프로세서에 의해서 실행되는 것에 기초하여, 수행되는 동작은:SM(Session Management) 컨텍스트 상태 통지 메시지를 AMF(Access and Mobility management Function)로 전송하는 단계를 포함하고,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 전송되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고,상기 SM 컨텍스트 상태 통지 메시지는 상기 PDU 세션과 관련된 액세스 타입에 대한 정보를 포함하는 칩셋.
- SMF(Session Management Function)를 위한 장치로서,송수신부와;적어도 하나의 프로세서와; 그리고명령어(instructions)를 저장하고, 상기 적어도 하나의 프로세서와 동작가능하게(operably) 전기적으로 연결가능한, 적어도 하나의 메모리를 포함하고,상기 동작은:SM(Session Management) 컨텍스트 상태 통지 메시지를 AMF(Access and Mobility management Function)로 전송하는 단계를 포함하고,상기 SM 컨텍스트 상태 통지 메시지는, PDU(Protocol Data Unit) 세션 수립 절차의 실패에 기초하여 전송되고,상기 PDU 세션 수립 절차는 비-3GPP(non-3rd Generation Partnership Project) 액세스와 3GPP 액세스 간에 PDU 세션의 핸드오버를 위해서 트리거링되고,상기 SM 컨텍스트 상태 통지 메시지는 상기 PDU 세션과 관련된 액세스 타입에 대한 정보를 포함하는 장치.
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/642,899 US20220361054A1 (en) | 2019-10-02 | 2020-09-11 | Method for moving pdu session on non-3gpp to 3gpp access |
EP20871265.3A EP4021075B1 (en) | 2019-10-02 | 2020-09-11 | Method for moving pdu session on non-3gpp to 3gpp access |
EP23204349.7A EP4329367A1 (en) | 2019-10-02 | 2020-09-11 | Method for moving pdu session on non-3gpp to 3gpp access |
CN202080070157.5A CN114557031B (zh) | 2019-10-02 | 2020-09-11 | 用于将非3gpp上的pdu会话移动到3gpp接入的方法 |
KR1020227011129A KR20220061156A (ko) | 2019-10-02 | 2020-09-11 | 비-3gpp 상의 pdu 세션을 3gpp 액세스로 이동시키기 위한 방안 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR20190122515 | 2019-10-02 | ||
KR10-2019-0122515 | 2019-10-02 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021066346A1 true WO2021066346A1 (ko) | 2021-04-08 |
Family
ID=75337185
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2020/012309 WO2021066346A1 (ko) | 2019-10-02 | 2020-09-11 | 비-3gpp 상의 pdu 세션을 3gpp 액세스로 이동시키기 위한 방안 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20220361054A1 (ko) |
EP (2) | EP4329367A1 (ko) |
KR (1) | KR20220061156A (ko) |
CN (1) | CN114557031B (ko) |
WO (1) | WO2021066346A1 (ko) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022218343A1 (en) * | 2021-04-14 | 2022-10-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for session management function reselection |
WO2023174542A1 (en) * | 2022-03-17 | 2023-09-21 | Nokia Solutions And Networks Oy | Enabling direct service-based requests from radio access network nodes towards 5g core network functions |
WO2024098632A1 (en) * | 2023-03-30 | 2024-05-16 | Zte Corporation | Systems and methods for determining network capability via control plane |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117158033A (zh) * | 2022-03-29 | 2023-12-01 | 北京小米移动软件有限公司 | 基于增强现实业务的会话管理功能选择方法及装置、存储介质 |
WO2024109127A1 (en) * | 2023-07-21 | 2024-05-30 | Zte Corporation | System and methods for flow mobility control |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20180137823A (ko) * | 2017-06-19 | 2018-12-28 | 삼성전자주식회사 | 네트워크 가상화 및 세션 관리 방법 및 장치 |
KR20190020142A (ko) * | 2017-01-09 | 2019-02-27 | 엘지전자 주식회사 | 무선 통신 시스템에서 네트워크간 상호연동 방법 및 이를 위한 장치 |
US20190261260A1 (en) * | 2018-02-17 | 2019-08-22 | Huawei Technologies Co., Ltd. | System and method for ue context and pdu session context management |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101646248B (zh) * | 2008-08-07 | 2011-11-02 | 华为技术有限公司 | 封闭用户组信息处理方法、接入控制方法及系统和设备 |
CN108702724B (zh) * | 2016-11-27 | 2021-06-15 | Lg 电子株式会社 | 无线通信系统中的注销方法及其装置 |
EP3477993B1 (en) * | 2017-04-19 | 2021-09-22 | LG Electronics Inc. | Method for processing pdu session establishment procedure and amf node |
KR102026950B1 (ko) * | 2017-04-19 | 2019-09-30 | 엘지전자 주식회사 | Pdu 세션 수립 절차를 처리하는 방법 및 amf 노드 |
CN109219092B (zh) * | 2017-06-30 | 2021-01-26 | 展讯通信(上海)有限公司 | 从非3gpp接入网切换到3gpp接入网的方法、装置及终端 |
CN110830928B (zh) * | 2018-08-13 | 2021-09-03 | 华为技术有限公司 | 通信方法和装置 |
US11419174B2 (en) * | 2019-02-26 | 2022-08-16 | Mediatek Inc. | Connection recovery method for recovering a connection between a communications apparatus and a data network and the associated communications apparatus |
-
2020
- 2020-09-11 WO PCT/KR2020/012309 patent/WO2021066346A1/ko active Application Filing
- 2020-09-11 KR KR1020227011129A patent/KR20220061156A/ko active Search and Examination
- 2020-09-11 CN CN202080070157.5A patent/CN114557031B/zh active Active
- 2020-09-11 EP EP23204349.7A patent/EP4329367A1/en active Pending
- 2020-09-11 EP EP20871265.3A patent/EP4021075B1/en active Active
- 2020-09-11 US US17/642,899 patent/US20220361054A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20190020142A (ko) * | 2017-01-09 | 2019-02-27 | 엘지전자 주식회사 | 무선 통신 시스템에서 네트워크간 상호연동 방법 및 이를 위한 장치 |
KR20180137823A (ko) * | 2017-06-19 | 2018-12-28 | 삼성전자주식회사 | 네트워크 가상화 및 세션 관리 방법 및 장치 |
US20190261260A1 (en) * | 2018-02-17 | 2019-08-22 | Huawei Technologies Co., Ltd. | System and method for ue context and pdu session context management |
Non-Patent Citations (2)
Title |
---|
NOKIA, NOKIA SHANGHAI BELL, ZTE, HUAWEI: "Insertion of a PSA and UL CL/BP into the data path of a PDU session with an I-SMF", 3GPP DRAFT; C4-193082_29502_R16_INSERTION OF PSA AND UL CL OR BP V2, vol. CT WG4, 16 August 2019 (2019-08-16), Wroclaw, Poland, pages 1 - 24, XP051763942 * |
ZTE: "MA PDU Session Release", 3GPP DRAFT; C4-192126_ATSSS_29502_MA PDU SESSION RELEASE, vol. CT WG4, 2 May 2019 (2019-05-02), Reno, US, pages 1 - 18, XP051706878 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022218343A1 (en) * | 2021-04-14 | 2022-10-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for session management function reselection |
WO2023174542A1 (en) * | 2022-03-17 | 2023-09-21 | Nokia Solutions And Networks Oy | Enabling direct service-based requests from radio access network nodes towards 5g core network functions |
WO2024098632A1 (en) * | 2023-03-30 | 2024-05-16 | Zte Corporation | Systems and methods for determining network capability via control plane |
Also Published As
Publication number | Publication date |
---|---|
KR20220061156A (ko) | 2022-05-12 |
EP4329367A1 (en) | 2024-02-28 |
EP4021075B1 (en) | 2023-11-01 |
CN114557031B (zh) | 2023-06-09 |
CN114557031A (zh) | 2022-05-27 |
EP4021075A4 (en) | 2022-10-12 |
US20220361054A1 (en) | 2022-11-10 |
EP4021075A1 (en) | 2022-06-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021034073A1 (ko) | 비구조화 트래픽을 중계하기 위한 방법 및 릴레이 ue | |
WO2021034093A1 (ko) | 릴레이를 위한 인증 | |
WO2019190166A1 (ko) | Ladn을 위한 pdu 세션 수립 절차를 수행하는 방법, 사용자 장치 및 네트워크 노드 | |
WO2021029512A1 (ko) | 어플리케이션 서버의 변경에 관련된 통신 | |
WO2021049841A1 (ko) | 비-3gpp 상의 ims 음성 세션을 3gpp 액세스로 이동시키기 위한 방안 | |
WO2021066346A1 (ko) | 비-3gpp 상의 pdu 세션을 3gpp 액세스로 이동시키기 위한 방안 | |
WO2021241905A1 (ko) | 로밍 네트워크에서 네트워크 슬라이스 별 인증 실패 시 효율적인 plmn 선택 | |
WO2020218807A1 (ko) | Ma pdu 세션을 위한 pmf 지원 방안 | |
WO2021091115A1 (ko) | Pc5 링크와 uu 링크 사이에서 경로 스위칭 | |
WO2021025308A1 (ko) | 다중 usim을 지원하기 위한 amf의 처리 방안 | |
WO2021034142A1 (ko) | 리모트 ue를 위한 릴레이 ue의 동작 방법 | |
WO2021034126A1 (ko) | 레이어 2 릴레이에 관련된 통신 | |
WO2019103462A1 (ko) | 무선 통신 시스템에서의 서비스 요청 방법 및 이를 위한 장치 | |
WO2021040463A1 (ko) | 3gpp ps data off에 관련된 통신 | |
WO2021040423A1 (ko) | 설정 업데이트와 관련된 통신 | |
WO2021125691A1 (ko) | 통신 경로 스위칭 | |
WO2021157974A1 (ko) | 멀티 액세스 pdu 세션과 관련된 통신 | |
WO2021096193A1 (ko) | 릴레이 통신 | |
WO2021025428A1 (ko) | 복수의 sim에 기초한 발신자 정보 확인 | |
WO2021091186A1 (ko) | Ue policy 전달을 위한 네트워크 제어 방안 | |
WO2021167233A1 (ko) | 네트워크 슬라이스와 관련된 통신 | |
WO2020251226A1 (ko) | 5g 이동통신 시스템에서 npn에 접속하는 방법 및 사용자 장치 | |
WO2021167200A1 (ko) | 네트워크 슬라이스 별 인증 및 인가를 위한 ausf 및 udm의 동작 방안 | |
WO2021133047A1 (ko) | 릴레이 통신 ue가 설정 업데이트 시에 원격 ue를 효율적으로 지원하는 방법 | |
WO2021177529A1 (ko) | Af 요청에 따라 비활성화 혹은 수립되는 pdu 세션의 상태를 화면에 표시하는 방안 |
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: 20871265 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20871265.3 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2020871265 Country of ref document: EP Effective date: 20220321 |
|
ENP | Entry into the national phase |
Ref document number: 20227011129 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |