WO2024210511A2 - Gestion de procédure de désenregistrement dans un réseau sans fil - Google Patents

Gestion de procédure de désenregistrement dans un réseau sans fil Download PDF

Info

Publication number
WO2024210511A2
WO2024210511A2 PCT/KR2024/004328 KR2024004328W WO2024210511A2 WO 2024210511 A2 WO2024210511 A2 WO 2024210511A2 KR 2024004328 W KR2024004328 W KR 2024004328W WO 2024210511 A2 WO2024210511 A2 WO 2024210511A2
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
slice
network
allowed nssai
amf entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2024/004328
Other languages
English (en)
Other versions
WO2024210511A3 (fr
Inventor
Ashok Kumar Nayak
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to KR1020257033062A priority Critical patent/KR20250166955A/ko
Publication of WO2024210511A2 publication Critical patent/WO2024210511A2/fr
Publication of WO2024210511A3 publication Critical patent/WO2024210511A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • Embodiments disclosed herein relate to wireless communication networks, and more particularly to managing network slicing in 3GPP.
  • 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • terahertz bands for example, 95GHz to 3THz bands
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • the principal object of the embodiments herein is to disclose methods, a UE and an AMF entity for managing slice removal in the network, where the UE and the AMF entity can handle the registration status implicitly on removal of the last slice from the Allowed NSSAI.
  • Another object of the embodiments herein is to disclose that the AMF entity to remove the registration state for the UE and moves to a deregistered state implicitly without executing network-initiated deregistration procedure if the AMF entity removes the temporary slice after expiry of validity time or slice after expiry of a slice deregistration inactivity timer after finding that there is no Protocol Data Unit (PDU) session associated with the slice and there is no more default slice can be added.
  • PDU Protocol Data Unit
  • Another object of the embodiments herein is to disclose that the UE to remove the registration state and moves deregistered state implicitly without waiting for network-initiated deregistration procedure to receive if UE removes the temporary slice after expiry of validity time or slice after expiry of the slice deregistration inactivity timer after finding that there is no PDU session associated with the slice and there is no more slice UE wants to add by triggering a mobility registration update.
  • the embodiments herein provide methods for handling a deregistration procedure in a wireless network.
  • the method includes removing, by an AMF entity, a S-NSSAI from an Allowed NSSAI. Further, the method includes determining, by the AMF entity, that the S-NSSAI becomes unavailable, other S-NSSAIs are not present in an Allowed Network Slice Selection Assistance Information (NSSAI), and no default Single-Network Slice Selection Assistance Information (S-NSSAI) is provided in the Allowed NSSAI. Further, the method includes avoiding to initiate, by the AMF entity, a network-initiated deregistration procedure. Further, the method includes moving, by the AMF entity, a registration state for the UE implicitly to a RM-DEREGISTERED state implicitly.
  • the embodiments herein provide methods for handling a deregistration procedure in a wireless network.
  • the method includes determining, by a UE, that at least one S-NSSAI is not present in an Allowed NSSAI when the UE removes a slice. Further, the method includes determining, by the UE, that the UE does not receive a new Allowed NSSAI. Further, the method includes moving, by the UE, a deregistration state (i.e., registration state to a RM-DEREGISTERED state) without triggering a UE initiated deregistration procedure or receiving a network triggered deregistration procedure from an AMF entity implicitly.
  • a deregistration state i.e., registration state to a RM-DEREGISTERED state
  • the AMF entity moves the registration state for the UE to the RM-DEREGISTERED state based on an operator policy.
  • the AMF entity removes the S-NSSAI after a NSSAA re-authentication failure or based on expiry of a slice deregistration inactivity timer after finding that the UE does not have any PDU session associated with that S-NSSAI or the AMF entity removes the S-NSSAI after expiry of validity time for the slice when the slice is a temporary slice.
  • a behavior of the AMF entity for handling the registration status implicitly is applicable per access type (e.g., 3GPP access type, non-3GPP access type or the like) since the Allowed NSSAI and the registration status are maintained per access type.
  • an AMF entity including a slice managing controller coupled with a processor and a memory.
  • the slice managing controller is configured to remove a S-NSSAI from an Allowed NSSAI. Further, the slice managing controller is configured to determine that the S-NSSAI becomes unavailable, other S-NSSAIs are not present in an Allowed Network Slice Selection Assistance Information (NSSAI), and no default S-NSSAI is provided in the allowed NSSAI. Further, the slice managing controller is configured to avoid to initiate a network-initiated deregistration procedure. Further, the slice managing controller is configured to move a registration state for the UE to a RM-DEREGISTERED state implicitly.
  • NSSAI Network Slice Selection Assistance Information
  • the embodiments herein provide a UE including a slice managing controller coupled with a processor and a memory.
  • the slice managing controller is configured to determine that at least one S-NSSAI does not present in an Allowed NSSAI when the UE removes a slice. Further, the slice managing controller is configured to determine that the UE does not receive a new Allowed NSSAI. Further, the slice managing controller is configured to move a deregistration state without triggering a UE initiated deregistration procedure or receiving a network triggered deregistration procedure from an AMF entity implicitly.
  • the notification management client and the notification management server can efficiently perform a communication.
  • FIG. 1 illustrates a process of an AMF entity triggering a network-initiated deregistration procedure in a wireless network
  • FIG. 2 illustrates a procedure, wherein both the UE and the AMF entity implicitly remove the registration status in the wireless network, according to embodiments as disclosed herein;
  • FIG. 3 illustrates various hardware components of the UE, according to the embodiments as disclosed herein;
  • FIG. 4 illustrates various hardware components of the AMF entity, according to the embodiments as disclosed herein;
  • FIG. 5 illustrates a flow chart illustrating a method, implemented by the UE, for handling a deregistration procedure in a wireless network, according to the embodiments as disclosed herein;
  • FIG. 6 illustrates a flow chart illustrating a method, implemented by the AMF entity, for handling a deregistration procedure in the wireless network, according to the embodiments as disclosed herein.
  • 3GPP Release 15 introduced the concept of network slicing, which allows service providers to deploy an exclusive network for a customer (for example, mobile virtual network operator (MVNO), Enterprise) or service (for example, Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low Latency Communications (URLLC), Massive Machine Type Communications (mMTC)), comprising of multiple network functions designed specifically to support the specialized service.
  • MVNO mobile virtual network operator
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low Latency Communications
  • mMTC Massive Machine Type Communications
  • a set of such Network Functions is called "Network Slice", identified using S-NSSAI (Single Network Slice Selection Assistance Information) inside a 3GPP network.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • Session Management Function SMF
  • Policy Control function PCF
  • user plane function PDU selection during protocol data unit (PDU) session establishment
  • NSSRG Network Slice Simultaneous Registration Group
  • URSP User Equipment Routing Selection Policy
  • S-NSSAIs Configured S-NSSAIs.
  • FIG. 1 illustrates a process of an AMF entity (200) triggering a network-initiated deregistration procedure in a wireless network.
  • the UE(s) (100) may register a particular slice but does not use it by triggering a PDU session.
  • TR 23.700-41 studied the slice usage control and solution was agreed that both the UE (100) and the AMF entity (200) will remove the slice implicitly after waiting slice deregistration inactivity timers and does not see any PDU session being established using the slice within that time period.
  • both the UE (100) and the AMF entity (200) remove the slice implicitly without exchanging any signalling explicitly with each other.
  • This concept of solution is agreed and added to TS 23.501 and TS 23.502 as well.
  • 3GPP Rel 18 TR 23.700-41 provides a solution in which the network will provide the temporary slice information (such as time and location) and the UE (100) will behave as such that during this it can avail the services only when it matches the time and location criteria given by the network. As per TS 23.501, both the UE (100) and the AMF entity (200) will remove the slice implicitly without exchanging any explicit signalling information, if the slice becomes unavailable during a particular time period (validity time).
  • the AMF entity (200) determines a new Allowed NSSAI including some default slice. If no default slice could be added, the AMF entity (200) executes a network-initiated deregistration procedure (as depicted in FIG. 1) for the UE (100) which is a waste of radio and network resources as the UE (100) itself has already removed the slice.
  • both the UE (100) and the AMF entity (200) will remove the slice implicitly, if there is no PDU session and the slice deregistration inactivity timer expires. But if there is only one slice present in the Allowed NSSAI for the UE (100), then after slice removal, the AMF entity (200) determines a new Allowed NSSAI including some default slice. If no default slice could be added, then the AMF entity (200) executes a network-initiated deregistration procedure (as depicted in FIG. 1) for the UE (100) which is a waste of radio and network resources as the UE itself has already removed the slice.
  • the AMF entity (200) determines a new Allowed NSSAI including a default slice. If no default slice could be added, the AMF entity (200) executes the network-initiated deregistration procedure for the UE (100) which is a waste of radio and network resources as the UE (100) itself knows that NSSAA has been failed and can be removed on its own.
  • the UE (100) and the AMF entity (200) remove the slice implicitly without exchanging any explicit signalling information after expiry of the validity time (for a temporary slice, when the slice becomes unavailable) or expiry of the slice deregistration inactivity timer.
  • the AMF entity (200) finds that no more slices are present in the Allowed NSSAI and determines that a new Allowed NSSAI is not possible by adding default S-NSSAIs.
  • the network-initiated deregistration procedure is performed between the UE (100) and the AMF entity (200).
  • Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware.
  • the circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
  • circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.
  • a processor e.g., one or more programmed microprocessors and associated circuitry
  • Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.
  • the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
  • the embodiments herein achieve methods for handling a deregistration procedure in a wireless network.
  • the method includes removing, by an AMF entity, a S-NSSAI from an Allowed NSSAI. Further, the method includes determining, by the AMF entity, that the S-NSSAI becomes unavailable, other S-NSSAIs are not present in the allowed NSSAI, and no default S-NSSAI is provided in the allowed NSSAI. Further, the method includes avoiding to initiate, by the AMF entity, a network-initiated deregistration procedure. Further, the method includes moving, by the AMF entity, a registration state for the UE to a RM-DEREGISTERED state implicitly.
  • the methods can be used for managing implicit slice removal in the network, wherein the UE and the AMF entity can handle the registration status implicitly on removal of the last slice from the Allowed NSSAI. Based on the proposed methods, the network-initiated deregistration procedure is entirely skipped when only one slice is present in the Allowed NSSAI and that is removed after the expiry of validity time.
  • the proposed method can be used to reduce the signalling wastage and reduce the battery drainage at the UE and the AMF entity.
  • the UE supporting temporary available network slices only got one S-NSSAI in the Allowed NSSAI with a validity time that is about to expire, and if the UE does not receive an updated Allowed NSSAI from the AMF entity, then the UE shall enter RM-DEREGISTERED state.
  • the AMF entity shall either enter RM-DEREGISTERED state for the UE or execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 of TS 23.502.
  • the operator policy means either the AMF entity can use explicit network-initiated deregistration procedure or implicit deregistration procedure.
  • AMF Access and Mobility Management Function.
  • UE User Equipment.
  • 3GPP 3 rd Generation Partnership Project.
  • NSSAI Network Slice Selection Assistance Information.
  • S-NSSAI Single - Network Slice Selection Assistance Information.
  • PLMN Public Land Mobile Network.
  • TA Tracking Area.
  • FIG. 2 through FIG. 6 where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.
  • FIG. 2 illustrates a procedure, wherein both a UE (100) and an AMF entity (200) implicitly update registration status for the UE (100) in a wireless network (1000), according to embodiments as disclosed herein.
  • the UE (100) can be, for example, but not limited to a laptop, a smart phone, a desktop computer, a notebook, a Device-to-Device (D2D) device, a vehicle to everything (V2X) device, a foldable phone, a smart TV, a tablet, an immersive device, and an internet of things (IoT) device.
  • the wireless network (1000) can be, for example, but not limited to a fourth generation (4G) network, a fifth generation (5G) network, a 6G network, an Open Radio Access Network (ORAN) or the like.
  • 4G fourth generation
  • 5G fifth generation
  • 6G 6G network
  • OFRAN Open Radio Access Network
  • the AMF entity (200) when the AMF entity (200) removes the slice implicitly after expiry of validity time for a temporary slice, when the slice becomes unavailable and no more slices are present in an Allowed NSSAI and a new Allowed NSSAI is not possible by adding default S-NSSAIs, then the AMF entity (200) does not initiate a network-initiated deregistration procedure.
  • the AMF entity (200) removes the registration status for the UE (100) implicitly.
  • the AMF entity (200) when the AMF entity (200) removes the slice implicitly (after expiry of the slice deregistration inactivity timer) and no more slices are present in the Allowed NSSAI and the new Allowed NSSAI is not possible by adding the default S-NSSAIs then, the AMF entity (200) does not initiate the network-initiated deregistration procedure.
  • the AMF entity (200) removes the registration status for the UE (100) implicitly.
  • the AMF entity (200) when the AMF entity (200) removes the slice after NSSAA re-authentication failure, and no more slices are present in the Allowed NSSAI and the new Allowed NSSAI is not possible by adding the default S-NSSAIs, then the AMF entity (200) does not initiate the network-initiated deregistration procedure.
  • the AMF entity (200) removes the registration status for the UE (100) implicitly.
  • the UE (100) when the UE (100) removes the slice implicitly after expiry of validity time for the slice (when the slice becomes unavailable) and no more S-NSSAIs are present in the Allowed NSSAI, then the UE (100) optionally waits for a pre-defined time period. During this time period, if the UE (100) receives a new Allowed NSSAI, from the AMF entity (200), then UE (100) updates the Allowed NSSAI. After expiry of this new time period, if the UE (100) does not receive any new Allowed NSSAI, then the UE (100) implicitly treats it as deregistered and moved to the deregistered state. In an embodiment, the UE (100) can directly move to deregistered state after removing the slice even without waiting pre-defined timer period.
  • the UE (100) when the UE (100) removes the slice implicitly after expiry of slice deregistration inactivity timer and no more S-NSSAIs are present in the Allowed NSSAI, then the UE (100) optionally waits for the pre-defined time period. During this time period, if the UE (100) receives the new Allowed NSSAI, from the AMF entity (200), then the UE (100) updates the Allowed NSSAI. After expiry of this new time period, if the UE (100) does not receive any new Allowed NSSAI, then the UE (100) implicitly treats as deregistered and moved to the deregistered state. In an embodiment, the UE (100) can directly move to deregistered state after removing the slice even without waiting pre-defined timer period.
  • the UE (100) when the UE (100) removes the slice after NSSAA re-authentication failure and no more slices are present in the Allowed NSSAI, then the UE (100) optionally waits for the pre-defined time period. During this time period, if the UE (100) receives the new Allowed NSSAI, from the AMF entity (200), then the UE (100) updates the Allowed NSSAI. After expiry of this new time period, if the UE (100) does not receive any new Allowed NSSAI, then the UE (100) implicitly treats as deregistered and moved to deregistered state. In an embodiment, UE can directly move to deregistered state after removing the slice even without waiting pre-defined timer period.
  • the new timer for which the UE (100) waits to receive any new Allowed NSSAI
  • the UE (100) goes to a deregistered state
  • AMF entity (200) can be UE implementation specific.
  • the behaviour of the UE (100) and the AMF entity (200) for handling the registration status implicitly is applicable per Access Type (e.g., 3GPP access type, non-3GPP access type or the like) as both the Allowed NSSAI and registration is maintained per access type.
  • Access Type e.g., 3GPP access type, non-3GPP access type or the like
  • the UE (100) and the AMF entity (200) remove the slice implicitly without exchanging any explicit signalling information after expiry of the validity time (for a temporary slice, when the slice becomes unavailable) or expiry of the slice deregistration inactivity timer.
  • the AMF entity (200) finds that no more slices are present in the Allowed NSSAI and determines that the new Allowed NSSAI is not possible by adding the default S-NSSAIs.
  • the UE (100) starts a timer after implicit removal of the last slice of the Allowed NSSAI and then expiry of the timer, the UE (100) moves to the deregistration state without triggering any UE initiated deregistration procedure or receiving any network triggered deregistration procedure.
  • the AMF entity (200) removes the UE's registration status to deregistered without triggering any AMF entity (200) initiated procedure or receiving any UE triggered deregistration procedure.
  • the allowed NSSAI is having just one slice (i.e. S-NSSAI-1).
  • the S-NSSAI-1 is related to temporary slice which is not available after 10 am and this validity time information is already provided by the AMF entity (200) to the UE (100).
  • both the AMF entity (200) and UE (100) will remove the S-NSSAI-1 from the Allowed NSSAI.
  • the Allowed NSSAI is empty. If the UE (100) does not have any default S-NSSAI in the subscription and the AMF entity (200) cannot add any S-NSSAI to the Allowed NSSAI then it will implicitly move the UE's registration status to deregistered state without triggering any deregistration procedure to the UE (100).
  • the UE (100) After the UE (100) remove the S-NSSAI-1 from the allowed NSSAI, if the UE (100) does not receive any Allowed NSSAI from the AMF entity (200), then the UE (100) will implicitly move the UE's registration status to deregistered state.
  • the allowed NSSAI is having just one slice (i.e. S-NSSAI-1).
  • S-NSSAI-1 There is slice deregistration inactivity timer associated with the S-NSSAI-1 and this is already provided by the AMF entity (200) to the UE (100).
  • This Slice deregistration inactivity timer is running at both the UE (100) and the AMF entity (200).
  • the UE (100) didn't trigger any PDU session associated with S-NSSAI-1 within that time and after timer expiry, both UE (100) and the AMF entity (200) will remove the S-NSSAI-1 from the Allowed NSSAI.
  • the allowed NSSAI is empty.
  • the UE (100) does not have any default S-NSSAI in the subscription and the AMF entity (200) cannot add any S-NSSAI to the Allowed NSSAI then it will implicitly move the UE's registration status to deregistered state without triggering any deregistration procedure to the UE (100).
  • the UE (100) remove the S-NSSAI-1 from Allowed NSSAI, if the UE (100) does not receive any Allowed NSSAI from the AMF entity (200), then the UE (100) will implicitly move the UE's registration status to the deregistered state.
  • the allowed NSSAI is having just one slice, i.e. S-NSSAI-1.
  • the S-NSSAI-1 is removed from Allowed NSSAI and if some default S-NSSAI is present for the UE (100), the AMF entity (200) adds the default S-NSSAI to Allowed NSSAI and S-NSSAI-1 is added to Rejected S-NSSAI by the AMF entity (200) and sent to the UE (100) using the UE configuration update procedure. But if there is no default S-NSSAI present for the UE (100), then Allowed NSSAI will be empty.
  • the AMF entity (200) cannot add any S-NSSAI to the Allowed NSSAI then it will implicitly move the UE's registration status to deregistered state without triggering any deregistration procedure to the UE (100).
  • the UE (100) already knows that slice re-authentication fails and hence it can remove the S-NSSAI-1 from Allowed NSSAI. Then, the Allowed NSSAI can become empty. If the UE (100) does not receive any Allowed NSSAI from the AMF entity (200), then the UE (100) will implicitly move the UE's registration status to deregistered state.
  • the Allowed NSSAI are maintained per access type, i.e. there will be different Allowed NSSAI content for each access type. Hence, the deregistration will be applicable for the corresponding access type for which Allowed NSSAI has become empty.
  • FIG. 3 illustrates various hardware components of the UE (100), according to the embodiments as disclosed herein.
  • the UE (100) includes a processor (110), a communicator (120), a memory (130) and a slice managing controller (140).
  • the processor (110) is coupled with the communicator (120), the memory (130) and the slice managing controller (140).
  • the slice managing controller (140) may determine that the S-NSSAI does not present in the Allowed NSSAI when the UE (100) removes the slice. Further, the slice managing controller (140) may determine that the UE (100) does not receive the new Allowed NSSAI. Further, the slice managing controller (140) may move the deregistration state without triggering the UE initiated deregistration procedure or receiving the network triggered deregistration procedure from the AMF entity (200) implicitly.
  • the slice managing controller (140) may be implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.
  • the processor (110) may include one or a plurality of processors.
  • the one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).
  • the processor (110) may include multiple cores and is configured to execute the instructions stored in the memory (130).
  • the processor (110) may be configured to execute instructions stored in the memory (130) and to perform various processes.
  • the communicator (120) may be configured for communicating internally between internal hardware components and with external devices via one or more networks.
  • the memory (130) may also store instructions to be executed by the processor (110).
  • the memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
  • EPROM electrically programmable memories
  • EEPROM electrically erasable and programmable
  • the memory (130) may, in some examples, be considered a non-transitory storage medium.
  • non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
  • RAM Random Access Memory
  • FIG. 3 illustrates various hardware components of the UE (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the UE (100).
  • FIG. 4 illustrates various hardware components of the AMF entity (200), according to the embodiments as disclosed herein.
  • the AMF entity (200) includes a processor (210), a communicator (220), a memory (230) and a slice managing controller (240).
  • the processor (210) is coupled with the communicator (220), the memory (230) and the slice managing controller (240).
  • the slice managing controller (240) may remove the S-NSSAI from the Allowed NSSAI. Further, the slice managing controller (240) may determine that the S-NSSAI becomes unavailable, the other S-NSSAIs are not present in the Allowed NSSAI, and no default S-NSSAI is provided in the Allowed NSSAI. Further, the slice managing controller (240) may avoid to initiate the network-initiated deregistration procedure. Further, the slice managing controller (240) may move the registration state for the UE (100) to the RM-DEREGISTERED state implicitly.
  • the slice managing controller (240) may be implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.
  • the processor (210) may include one or a plurality of processors.
  • the one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).
  • the processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (230).
  • the processor (210) may be configured to execute instructions stored in the memory (230) and to perform various processes.
  • the communicator (220) may be configured for communicating internally between internal hardware components and with external devices via one or more networks.
  • the memory (230) may also store instructions to be executed by the processor (210).
  • the memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
  • EPROM electrically programmable memories
  • EEPROM electrically erasable and programmable
  • the memory (230) may, in some examples, be considered a non-transitory storage medium.
  • non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (230) is non-movable.
  • a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
  • RAM Random Access Memory
  • FIG. 4 illustrates various hardware components of the AMF entity (200) but it is to be understood that other embodiments are not limited thereon.
  • the AMF entity (200) may include less or more number of components.
  • the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention.
  • One or more components can be combined together to perform the same or substantially similar function in the AMF entity (200).
  • FIG. 5 illustrates a flow chart (S500) illustrating a method, implemented by the UE (100), for handling the deregistration procedure in the wireless network (1000), according to the embodiments as disclosed herein.
  • the operations (S502-S506) are handled by the slice managing controller (140).
  • the method includes determining that the S-NSSAI is not present in the Allowed NSSAI when the UE (100) removes the slice.
  • the method includes determining that the UE (100) does not receive the new Allowed NSSAI.
  • the method includes moving the registration state to the RM-DEREGISTERED state without triggering the UE (100) initiated deregistration procedure or receiving the network triggered deregistration procedure from the AMF entity (200) implicitly.
  • FIG. 6 illustrates a flow chart (S600) illustrating a method, implemented by the AMF entity (200), for handling the deregistration procedure in the wireless network (1000), according to the embodiments as disclosed herein.
  • the operations (S602-S608) are handled by the slice managing controller (240).
  • the method includes removing the S-NSSAI from the Allowed NSSAI.
  • the method includes determining that the S-NSSAI becomes unavailable, the other S-NSSAIs are not present in the Allowed NSSAI, and the no default S-NSSAI is provided in the allowed NSSAI.
  • the method includes avoiding to initiate the network-initiated deregistration procedure.
  • the method includes moving the registration state for the UE (100) to the RM-DEREGISTERED state implicitly.
  • the network-initiated deregistration procedure is entirely skipped when only one temporary slice is present in the Allowed NSSAI and that is removed after the expiry of validity time.
  • the proposed method can be used to reduce the signalling wastage and reduce the battery drainage at the UE (100) and the AMF entity (200).
  • the embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements.
  • the elements can be at least one of a hardware device, or a combination of hardware device and software module.

Landscapes

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

Abstract

La divulgation concerne un système de communication 5G ou 6G permettant de prendre en charge un débit supérieur de transmission de données. Des modes de réalisation de la présente divulgation concernent des procédés de gestion d'une procédure de désenregistrement dans un réseau sans fil (1000) par une entité AMF (200). Sur la base des procédés de la divulgation, la procédure de désenregistrement lancée par réseau est entièrement sautée lorsqu'une seule tranche temporaire est présente dans les NSSAI autorisées et qu'elle est retirée après l'expiration du temps de validité. Le procédé de la divulgation peut être utilisé pour réduire le gaspillage de signalisation et réduire le drainage de batterie au niveau de l'UE et de l'entité AMF.
PCT/KR2024/004328 2023-04-03 2024-04-03 Gestion de procédure de désenregistrement dans un réseau sans fil Ceased WO2024210511A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020257033062A KR20250166955A (ko) 2023-04-03 2024-04-03 무선 네트워크에서의 등록 취소 절차 처리

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202341025283 2023-04-03
IN202341025283 2024-03-15

Publications (2)

Publication Number Publication Date
WO2024210511A2 true WO2024210511A2 (fr) 2024-10-10
WO2024210511A3 WO2024210511A3 (fr) 2025-09-12

Family

ID=92973210

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/004328 Ceased WO2024210511A2 (fr) 2023-04-03 2024-04-03 Gestion de procédure de désenregistrement dans un réseau sans fil

Country Status (2)

Country Link
KR (1) KR20250166955A (fr)
WO (1) WO2024210511A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12279222B1 (en) * 2024-04-24 2025-04-15 Metapex Inc. Method for operating UE associated with S-NSSAI
US12376064B1 (en) * 2024-06-07 2025-07-29 Metapex Inc. Method and UE for starting slice deregistration inactivity timer

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115669083A (zh) * 2020-05-22 2023-01-31 苹果公司 网络切片特定的认证和授权(nssaa)5g新空口(nr)过程
WO2022035257A1 (fr) * 2020-08-13 2022-02-17 엘지전자 주식회사 Traitement d'une défaillance de nssaa provoquée par une erreur de réseau ou une expiration de délai
US20240259982A1 (en) * 2021-07-22 2024-08-01 Nec Corporation Method of access and mobility management function (amf), method of user equipment (ue), amf and ue
EP4388788A1 (fr) * 2021-08-20 2024-06-26 Nokia Technologies Oy Fourniture de services sur tranche de réseau temporaire dans un système de communication

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12279222B1 (en) * 2024-04-24 2025-04-15 Metapex Inc. Method for operating UE associated with S-NSSAI
US12376064B1 (en) * 2024-06-07 2025-07-29 Metapex Inc. Method and UE for starting slice deregistration inactivity timer

Also Published As

Publication number Publication date
WO2024210511A3 (fr) 2025-09-12
KR20250166955A (ko) 2025-11-28

Similar Documents

Publication Publication Date Title
WO2024210511A2 (fr) Gestion de procédure de désenregistrement dans un réseau sans fil
WO2023244015A1 (fr) Procédé et appareil de recherche et de sélection de plmn après le retrait d'une entrée dans un réseau sans fil
WO2023048510A1 (fr) Procédé et réseau sans fil pour gérer des informations d'abonnements aériens d'uav
US20240244507A1 (en) Network slice admission control based on availability of quota at nsacf apparatus in wireless network
WO2024096614A1 (fr) Procédé et appareil de gestion de collision de période d'indisponibilité dans réseau sans fil
WO2024101810A1 (fr) Gestion d'équipement utilisateur pendant une période d'indisponibilité dans un réseau sans fil
WO2023132700A1 (fr) Procédé et ue de gestion d'expiration de temporisateur pendant une procédure nas en cours dans un réseau sans fil
WO2023132603A1 (fr) Réseau sans fil et procédé pour gérer une zone nssai rejetée dans un réseau sans fil
WO2025014181A1 (fr) Procédé et appareil de gestion d'une zone de service ladn dans un système de communication sans fil
WO2023003310A1 (fr) Procédé et appareil pour sélectionner une bande de fréquence pour un ue dans un réseau sans fil
WO2022250362A1 (fr) Appareil et procédé de gestion de procédure de désenregistrement d'équipement utilisateur pour service d'itinérance en cas de sinistre dans un réseau sans fil
WO2023277469A1 (fr) Procédé et appareil de gestion de l'enregistrement d'un équipement utilisateur sur une tranche de réseau
WO2024215038A1 (fr) Procédés et appareil de gestion d'enregistrement de tranche non-3gpp dans un système de communication sans fil
WO2025071162A1 (fr) Procédés et appareil pour le traitement de session(s) pdu associée(s) à une restriction de zone pour une tranche dans un système de communication sans fil
WO2022240189A1 (fr) Procédé et appareil pour gérer une défaillance de contrôle de sécurité sor pendant une procédure d'enregistrement dans un réseau sans fil
WO2024205295A1 (fr) Procédé et appareil pour bloquer des données de plan de gestion pour nssai et ns-aos partiellement autorisées dans un système de communication sans fil
WO2023128650A1 (fr) Procédé et appareil de gestion d'indication précoce de radiomessagerie avec assistance au sous-groupement de radiomessagerie
WO2024151047A1 (fr) Gestion d'instanciation dynamique d'un serveur d'application de périphérie (eas) dans un réseau de périphérie
WO2024096598A1 (fr) Procédé et appareil de gestion d'identité de zone de suivi interdite appartenant à différents identifiants de réseau mobile terrestre public dans un système de communication
WO2025005551A1 (fr) Procédé et appareil de gestion de session pdu en fonction d'une disponibilité d'emplacement de tranche dans un système de communication sans fil
WO2024128466A1 (fr) Procédé et système de commande de capacité sa d'ue
WO2023214854A1 (fr) Procédé et appareil de négociation de service dans un réseau ido personnel
WO2024136401A1 (fr) Procédé et appareil de gestion d'accès à une tranche de réseau pour un équipement utilisateur dans un système de communication sans fil
WO2026019169A1 (fr) Gestion de liste de plmn interdits à l'expiration de t3245 ou t3247 pour itinérance en cas de catastrophe
WO2025018695A1 (fr) Procédé et appareil de gestion de session pdu pour dnn ladn dans système de communication sans fil

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

Country of ref document: EP

Kind code of ref document: A2

ENP Entry into the national phase

Ref document number: 1020257033062

Country of ref document: KR

Free format text: ST27 STATUS EVENT CODE: A-0-1-A10-A15-NAP-PA0105 (AS PROVIDED BY THE NATIONAL OFFICE)

WWE Wipo information: entry into national phase

Ref document number: KR1020257033062

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 24785214

Country of ref document: EP

Kind code of ref document: A2