[go: up one dir, main page]

WO2021210960A1 - Procédé de gestion de cas d'utilisation anormale associés à un découpage en tranches de réseau - Google Patents

Procédé de gestion de cas d'utilisation anormale associés à un découpage en tranches de réseau Download PDF

Info

Publication number
WO2021210960A1
WO2021210960A1 PCT/KR2021/004830 KR2021004830W WO2021210960A1 WO 2021210960 A1 WO2021210960 A1 WO 2021210960A1 KR 2021004830 W KR2021004830 W KR 2021004830W WO 2021210960 A1 WO2021210960 A1 WO 2021210960A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
amf
registration
network
network slices
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/KR2021/004830
Other languages
English (en)
Inventor
Anikethan Ramakrishna Vijaya KUMAR
Kundan Tiwari
Ricky Kaura
Mahmoud Watfa
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
Publication of WO2021210960A1 publication Critical patent/WO2021210960A1/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/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • 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
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • the present invention relates to wireless communication technology and in particular relates to a method for handling abnormal use cases related to network slicing.
  • the present application is based on, and claims priority from an Indian Provisional Application Number 202041016739 filed on 18th April, 2020, the disclosure of which is hereby incorporated by reference herein.
  • the 5G or pre-5G communication system is also called a 'Beyond 4G Network' or a 'Post LTE System'.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave e.g., 60GHz bands
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs Cloud Radio Access Networks
  • D2D device-to-device
  • CoMP Coordinated Multi-Points
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • the Internet which is a human centered connectivity network where humans generate and consume information
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology “wired/wireless communication and network infrastructure”, “service interface technology”, and “Security technology”
  • M2M Machine-to-Machine
  • MTC Machine Type Communication
  • IoT Internet technology services
  • IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.
  • IT Information Technology
  • 5G communication systems to IoT networks.
  • technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC Machine Type Communication
  • M2M Machine-to-Machine
  • Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN Radio Access Network
  • a set of network entities associated with the service request are denoted by a slice or a Single Network Slice Selection Assistance information (S-NSSAI).
  • the S-NSSAI may be associated with a PLMN (e.g., PLMN ID) and includes a network-specific values or a standard values.
  • the S-NSSAI associated with the PLMN is used by the UE in access network of the PLMN. Further, the NSSAI is a collection of up to 8 S-NSSAIs.
  • the S-NSSAI may be Network Slice Specific Authentication and Authorization (NSSAA).
  • NSSAA Network Slice Specific Authentication and Authorization
  • the currently defined handling for NSSAA and certain related handling of pending and rejected slices are not very efficient and there is scope to improve upon the same. For example, when the there is ongoing NSSAA and a new request for the NSSAI is received.
  • NSSAI Network Slice Specific Authentication and Authorization
  • an ambiguity is generated at the User Equipment.
  • the principal object of the embodiments herein is to provide a method for handling abnormal use cases related to network slicing.
  • Another object of the embodiments herein is to handle a pending NSSAI in the User Equipment (UE).
  • UE User Equipment
  • Another object of the embodiments herein is to handle a rejected NSSAI in the UE, when the UE is in a Visitor Public Land Mobile Network (PLMN).
  • PLMN Visitor Public Land Mobile Network
  • the embodiment herein is to provide a method of handling Network Slice Selection Assistance Information (NSSAI), the method comprising creating, by a User Equipment (UE), a REGISTRATION REQUEST message, wherein the REGISTRATION REQUEST message comprises a request for one of a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices, and the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices. Further, sending, by the UE, the REGISTRATION REQUEST message to an Access and Mobility Management Function (AMF).
  • AMF Access and Mobility Management Function
  • the REGISTRATION ACCEPT message comprises one of: at least one of a pending S-NSSAI, an allowed S-NSSAI, a rejected S-NSSAI, for the one or more network slices and a flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) when the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices; and at least one of an allowed NSSAI, and a rejected NSSAI, wherein the rejected NSSAI comprises a combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN when the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLM)
  • NSSAA Network Slice Specific Authentication and Authorization
  • the REGISTRATION REQUEST message is created by the UE during at least one of a registration of the UE with the AMF, a re-registration of the UE with the AMF, and when an additional one or more network slices are required by the UE.
  • receiving, by the UE, the REGISTRATION ACCEPT message from the AMF comprising the pending S-NSSAI for the one or more network slices indicates a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • receiving, by the UE, the REGISTRATION ACCEPT message from the AMF comprising the allowed S-NSSAI for the one or more network slices indicates the UE can use the allowed S-NSSAI for communication without completing the NSSAA.
  • receiving, by the UE, the REGISTRATION ACCEPT message from the AMF comprising the rejected S-NSSAI for the one or more network slices indicates a non-availability of the rejected S-NSSAI for communication.
  • receiving, by the UE, the REGISTRATION ACCEPT message from the AMF comprising the flag with a value zero "0" indicates there is no ongoing NSSAA pending for the one or more network slices with the AMF.
  • receiving, by the UE, the REGISTRATION ACCEPT message from the AMF comprising the flag with a value one "1" indicates the NSSAA is pending for the one or more network slices.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • deleting, by the UE, the pending S-NSSAI based on the value of the flag comprises removing the one or more pending NSSAI stored in the UE when the value of the flag is zero "0".
  • awaiting, by the UE, for the NSSAA procedure based on the value of the flag comprises performing the NSSAA procedure ongoing with the AMF when the value of the flag is one "1".
  • sending, by the UE, a REGISTRATION REQUEST message comprises one or more access requests to the AMF associated with a Home Public Land Mobile Network (HPLMN), or a Visiting Public Land Mobile Network (VPLMN).
  • HPLMN Home Public Land Mobile Network
  • VPLMN Visiting Public Land Mobile Network
  • receiving, by the UE, a REGISTRATION ACCEPT message from the AMF comprising the pending S-NSSAI associated with the one or more network slices includes the pending S-NSSAI from the one or more access requests.
  • the pending S-NSSAI received from the AMF is updated in the UE to replace a previous pending S-NSSAI.
  • the combination of the S-NSSAI indicates a mapping between the one or more network slices of the VPLMN and the HPLMN.
  • the embodiments herein provide a method of handling Network Slice Selection Assistance Information (NSSAI), the method comprising receiving, by an Access and Mobility Management Function (AMF), a REGISTRATION REQUEST message from a User Equipment (UE), wherein the REGISTRATION REQUEST message comprises a request for one of a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices, and the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • AMF Access and Mobility Management Function
  • UE User Equipment
  • S-NSSAI Single-NSSAI
  • S-NSSAI Single-NSSAI
  • HPLMN Home Public Land Mobile Network
  • a REGISTRATION ACCEPT message comprising one of at least one of a pending S-NSSAI, an allowed S-NSSAI, a rejected S-NSSAI, for the one or more network slices and a flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) when the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices; and at least one of an allowed NSSAI, and a rejected NSSAI, wherein the rejected NSSAI comprises a combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN when the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or
  • the REGISTRATION REQUEST message is created during at least one of a registration of the UE with the AMF, a re-registration of the UE with the AMF, and when an additional one or more network slices are required by the UE.
  • receiving, by the AMF, the REGISTRATION REQUEST message from the UE comprises one or more access requests.
  • sending, by the AMF, the REGISTRATION ACCEPT message to the UE comprising the pending S-NSSAI associated with the one or more network slices includes the pending S-NSSAI from the one or more access requests.
  • sending, by the AMF, the REGISTRATION ACCEPT message to the UE comprising the pending S-NSSAI for the one or more network slices indicates a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • sending, by the AMF, the REGISTRATION ACCEPT message to the UE comprising the allowed S-NSSAI for the one or more network slices indicates the UE can use the allowed S-NSSAI for communication without completing the NSSAA.
  • sending, by the AMF, the REGISTRATION ACCEPT message to the UE comprising the rejected S-NSSAI for the one or more network slices indicates a non-availability of the rejected S-NSSAI for communication.
  • sending, by the AMF, the REGISTRATION ACCEPT message to the UE comprising the flag with a value zero "0" indicates there is no ongoing NSSAA pending for the one or more network slices with the AMF.
  • sending, by the AMF, the REGISTRATION ACCEPT message to the UE comprising the flag with a value one "1" indicates the NSSAA is pending for the one or more network slices.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • the combination of the S-NSSAI indicates a mapping between the one or more network slices of the VPLMN and the HPLMN.
  • a User Equipment for handling a pending and a rejected Network Slice Selection Assistance Information (NSSAI), the UE comprising a processor; a memory; and a NSSAI controller communicatively coupled to the processor and the memory, wherein the NSSAI controller is configured to create a REGISTRATION REQUEST message, wherein the REGISTRATION REQUEST message comprises a request for one of a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices, and the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • S-NSSAI Single-NSSAI
  • VPN Visiting Public Land Mobile Network
  • HPLMN Home Public Land Mobile Network
  • the REGISTRATION REQUEST message sends the REGISTRATION REQUEST message to an Access and Mobility Management Function (AMF). Furthermore, receive a REGISTRATION ACCEPT message from the AMF, wherein the REGISTRATION ACCEPT message comprises one of at least one of a pending S-NSSAI, an allowed S-NSSAI, a rejected S-NSSAI, for the one or more network slices and a flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) when the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices; and at least one of an allowed NSSAI, and a rejected NSSAI, wherein the rejected NSSAI comprises a combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN when the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated
  • the NSSAI controller is configured to create the REGISTRATION REQUEST message during at least one of a registration of the UE with the AMF, a re-registration of the UE with the AMF, and when an additional one or more network slices are required by the UE.
  • the NSSAI controller is configured to receive the REGISTRATION ACCEPT message from the AMF comprising the pending S-NSSAI for the one or more network slices indicates a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • the NSSAI controller is configured to receive the REGISTRATION ACCEPT message from the AMF comprising the allowed S-NSSAI for the one or more network slices indicates the UE can use the allowed S-NSSAI for communication without completing the NSSAA.
  • the NSSAI controller is configured to receive the REGISTRATION ACCEPT message from the AMF comprising the rejected S-NSSAI for the one or more network slices indicates a non-availability of the rejected S-NSSAI for communication.
  • the NSSAI controller is configured to receive the REGISTRATION ACCEPT message from the AMF comprising the flag with a value zero "0" indicates there is no ongoing NSSAA pending with the AMF.
  • the NSSAI controller is configured to receive the REGISTRATION ACCEPT message from the AMF comprising the flag with a value one "1" indicates the NSSAA is pending for the one or more network slices.
  • the NSSAI controller is configured to perform at least of deleting the pending S-NSSAI or awaiting for a Network Slice-Specific Authentication and Authorization (NSSAA) procedure from the AMF based on a value of the flag.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • the NSSAI controller is configured to delete the pending S-NSSAI based on the value of the flag comprises removing the one or more pending NSSAI stored in the UE when the value of the flag is zero "0".
  • the NSSAI controller is configured to await for the NSSAA procedure based on the value of the flag comprises performing the NSSAA procedure with the AMF when the value of the flag is one "1".
  • the NSSAI controller is configured to send a REGISTRATION REQUEST message comprises one or more access requests to the AMF associated with a Home Public Land Mobile Network (HPLMN), or a Visiting Public Land Mobile Network (VPLMN).
  • HPLMN Home Public Land Mobile Network
  • VPLMN Visiting Public Land Mobile Network
  • the NSSAI controller is configured to receive a REGISTRATION ACCEPT message from the AMF comprising the pending S-NSSAI associated with the one or more network slices includes the pending S-NSSAI from the one or more access requests.
  • the NSSAI controller is configured to replace a previous pending S-NSSAI with the pending S-NSSAI received from the AMF.
  • the embodiment herein provide an Access and Mobility Management Function (AMF) for handling a pending and a rejected Network Slice Selection Assistance Information (NSSAI),
  • AMF Access and Mobility Management Function
  • NSSAI Network Slice Selection Assistance Information
  • the AMF comprises a processor; a memory; and a NSSAI controller communicatively coupled to the processor and the memory, wherein the NSSAI controller is configured to receive a REGISTRATION REQUEST message from a User Equipment (UE), wherein the REGISTRATION REQUEST message comprises a request for one of a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices, and the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • UE User Equipment
  • S-NSSAI Single-NSSAI
  • HPLMN Home Public Land Mobile Network
  • REGISTRATION ACCEPT message comprises one of at least one of a pending S-NSSAI, an allowed S-NSSAI, a rejected S-NSSAI, for the one or more network slices and a flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) when the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices; and at least one of an allowed NSSAI, and a rejected NSSAI, wherein the rejected NSSAI comprises a combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN when the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • NSSAA Network Slice Specific Authentication and Authorization
  • the NSSAI controller is configured to receive the REGISTRATION REQUEST message from the UE during at least one of a registration of the UE with the AMF, a re-registration of the UE with the AMF, and when an additional one or more network slices are required by the UE.
  • the NSSAI controller is configured to receive the REGISTRATION REQUEST message from the UE comprises one or more access requests.
  • the NSSAI controller is configured to send the REGISTRATION ACCEPT message to the UE comprising the pending S-NSSAI associated with the one or more network slices includes the pending S-NSSAI from the one or more access requests.
  • the NSSAI controller is configured to send the REGISTRATION ACCEPT message to the UE comprising the pending S-NSSAI for the one or more network slices indicates a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • the NSSAI controller is configured to send the REGISTRATION ACCEPT message to the UE comprising the allowed S-NSSAI for the one or more network slices indicates the UE can use the allowed S-NSSAI for communication without completing the NSSAA.
  • the NSSAI controller is configured to send the REGISTRATION ACCEPT message to the UE comprising the rejected S-NSSAI for the one or more network slices indicates a non-availability of the rejected S-NSSAI for communication.
  • the NSSAI controller is configured to send the REGISTRATION ACCEPT message to the UE comprising the flag with a value zero "0" indicates there is no ongoing NSSAA pending for the one or more network slices with the AMF.
  • the NSSAI controller is configured to send the REGISTRATION ACCEPT message to the UE comprising the flag with a value one "1" indicates the NSSAA is pending for the one or more network slices.
  • the principal object of the embodiments herein is to provide an efficient method of handling Network Slice Selection Assistance Information (NSSAI).
  • NSSAI Network Slice Selection Assistance Information
  • FIG. 1 illustrates an existing method for handing a pending Network Slice Selection Assistance Information (NSSAI), according to the prior art
  • FIG. 2 illustrates existing method for handling a rejected Network Slice Selection Assistance Information (NSSAI) in a VPLMN, according to the prior art
  • FIG. 3A illustrates a block diagram of a User Equipment according to the embodiments as disclosed herein;
  • FIG. 3B illustrates a block diagram of an Access and Mobility Management Function (AMF), according to the embodiments as disclosed herein;
  • AMF Access and Mobility Management Function
  • FIG. 4 shows a flowchart for handling Network Slice Selection Assistance Information (NSSAI) during network slicing, according to the embodiments as disclosed herein;
  • NSSAI Network Slice Selection Assistance Information
  • FIG. 5 illustrates a signaling diagram for handing the pending NSSAI, according to the embodiments as disclosed herein;
  • FIG. 6 illustrates a signaling diagram for handing the rejected NSSAI in a VPLMN, according to the embodiments as disclosed herein
  • 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.
  • FIGS. 1 through 6 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
  • FIG. 1 illustrates an existing method for handing a pending Network Slice Selection Assistance Information (NSSAI), according to the prior art.
  • NSSAI Network Slice Selection Assistance Information
  • a User Equipment (UE) (101) sends a REGISTRATION REQUEST with a requested NSSAI to an Access and Mobility Management Function (AMF) (102).
  • the requested NSSAI includes S-NSSAI 'A' and 'B' as shown in signal 1 of FIG.1.
  • the AMF (102) determines that the slices 'A' and 'B' are subjected to Network Slice Specific Authentication and Authorization (NSSAA) as shown in signal 2 of FIG.1. Further, the AMF (102) includes the slices 'A' and 'B' in the pending NSSAI.
  • the pending NSSAI is sent to the UE (101) via a REGISTRATION ACCEPT message as shown in signal 3 of FIG.1. Further, a flag value associated with "NSSAA performed" is set to 1 in 5GS registration result (i.e. registration accept message) as shown in signal 3 of FIG.1.
  • the AMF (102) initiates a NSSAA procedure for the UE (101) towards the AAA server as shown in signal 5 of FIG.1.
  • NSSAA procedure between the AMF (102) and the UE (101) is ongoing, and the UE (101) modifies the requested NSSAI from slices 'A' and 'B' to slices 'C', and 'D' as shown in signal 4 of FIG.1.
  • the UE (101) initiates a mobility registration with the slices 'C', and 'D' in the requested NSSAI in the REGISTRATION REQUEST message as shown in signal 6 of FIG.1.
  • the AMF (102) determines that the slices 'C', and 'D' requested by the UE (101) are not subject to NSSAA as shown in signal 7 of FIG.1.
  • the AMF (102) sends the REGISTRATION ACCEPT message with the S-NSSAI 'C' and 'D' as the allowed NSSAI as shown in signal 8 of FIG.1. Further, the UE (101) still has S-NSSAI's A and B as part of the pending NSSAI as shown in signal 9 of FIG. 1.
  • the AMF (102) may perform the NSSAA procedure with the UE (101) for the S-NSSAI slices 'A' and 'B', where the S-NSSAI slices 'A' and 'B' may be required by the UE (101) because the UE is using the allowed slices 'C' and 'D'.
  • the AMF (102) is unable to move the contents of the pending Network Slice specific Authentication and Authorization (NSSAI) to any of the existing lists such as allowed NSSAI or rejected NSSAI.
  • NSSAI Network Slice specific Authentication and Authorization
  • FIG. 2 illustrates existing method for handling a rejected Network Slice Selection Assistance Information (NSSAI) in a VPLMN, according to the prior art.
  • NSSAI Network Slice Selection Assistance Information
  • the UE (101) is roaming and attempts to register with the AMF (102) in a Visitor Public Land Mobile Network (VPLMN). Further, one S-NSSAI in the VPLMN may be mapped to a plurality of S-NSSAI's corresponding to a Home Public Land Mobile Network (HPLMN). Because the HPLMN may provide one or more services via specific network slices (for example, H1, H2, H3 and H4) whereas the VPLMN provides one or more services via the same network slice (for example, V1) as shown in signal 1 of FIG. 2. The UE (101) is roaming in the VPLMN that offers one or more services via slice V1. The mapped HPLMN N-SSAI's corresponding to slice V1 are H1, H2, H3 and H4.
  • the VPLMN may allow access to a subset of services from the one or more services in the HPLMN.
  • the UE initiates REGISTRATION REQUEST and requests access for all services available as part of the HPLMN S-NSSAI's.
  • the UE (101) sends a requested NSSAI with multiple (VPLMN S-NSSAI + mapped H-PLMN S-NSSAI) s-NSSAI's to the AMF (102) via the REGISTRATION REQUEST message as shown in signal 2 of FIG. 2.
  • the HPLMN currently does not allow H2 to be accessed in the VPLMN.
  • the slices H3 and H4 cannot be accessed in the current Registration Area (RA) of the UE (101). Therefore, the slice H1 is allowed in the current RA of the VPLMN for the UE (101).
  • RA Registration Area
  • the AMF (102) in the VPLMN allows a subset of mapped HPLMN S-NSSAI's and rejects a subset of mapped HPLMN S-NSSAI's as not allowed in the VPLMN as shown in signal 3 of FIG. 2.
  • the AMF (102) indicates a reason for rejecting the mapped HPLMN S-NSSAI's as "rejected NSSAI for the current PLMN or Registration Area (RA)" as shown in signal 3 of FIG. 2.
  • the AMF (102) sends the allowed and rejected NSSAI via the REGISTRATION ACCEPT message to the UE (101).
  • the current rejected NSSAI does not have the necessary IE (information Element) in the REGISTRATION ACCEPT message to notify the actual mapped HPLMN S-NSSAI that has been rejected.
  • the AMF (102) sends the VPLMN S-NSSAI corresponding to the rejected NSSAI with a reason "rejected NSSAI for the current PLMN or SNPN" to the UE (101) as shown in signal 3 of FIG. 2.
  • the UE (101) receives (V1+H1) as the allowed NSSAI and since the rejected NSSAI does not have mapped HPLMN NSSAI values, it would receive V1 in the rejected NSSAI for current PLMN/SNPN and again V1 in the rejected NSSAI for current registration area.
  • the AMF (102) includes a repeated values of the VPLMN S-NSSAI in the rejected NSSAI for the current PLMN or SNPN.
  • the UE (101) would not know if the one or more services is rejected or allowed because the rejected NSSAI includes the VPLMN S-NSSAI values and does not include the corresponding mapped HPLMN S-NSSAI values. Therefore, the UE (101) may re-trigger the registration to access the S-NSSAI again.
  • FIG. 3A and 3B illustrates a block diagram of a User Equipment and an Access and Mobility Management Function (AMF), according to the embodiments as disclosed herein.
  • AMF Access and Mobility Management Function
  • the UE (101) includes a processor (101A), a memory (101B), and a NSSAI controller (101C).
  • the NSSAI controller (101C) is communicatively coupled to the processor (101A) and the memory (101B).
  • the NSSAI controller (101C) is configured to create a REGISTRATION REQUEST message, wherein the REGISTRATION REQUEST message comprises a request for one of a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices, and the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • S-NSSAI Single-NSSAI
  • VPN Visiting Public Land Mobile Network
  • HPLMN Home Public Land Mobile Network
  • the NSSAI controller (101C) sends the REGISTRATION REQUEST message to an Access and Mobility Management Function (AMF) (102).
  • the NSSAI controller (101C) receives a REGISTRATION ACCEPT message from the AMF (102), wherein the REGISTRATION ACCEPT message comprises one of at least one of a pending S-NSSAI, an allowed S-NSSAI, a rejected S-NSSAI, for the one or more network slices and a flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) when the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices; and at least one of an allowed NSSAI, and a rejected NSSAI, wherein the rejected NSSAI comprises a combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN when the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of
  • the NSSAI controller (101C) is configured to create the REGISTRATION REQUEST message during at least one of a registration of the UE (101) with the AMF (102), a re-registration of the UE (101) with the AMF (102), and when an additional one or more network slices are required by the UE (101).
  • the NSSAI controller (101C) is configured to receive the REGISTRATION ACCEPT message from the AMF (102) comprising the pending S-NSSAI for the one or more network slices indicates a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • the NSSAI controller (101C) is configured to receive the REGISTRATION ACCEPT message from the AMF (102) comprising the allowed S-NSSAI for the one or more network slices indicates the UE (101) can use the allowed S-NSSAI for communication without completing the NSSAA.
  • the NSSAI controller (101C) is configured to receive the REGISTRATION ACCEPT message from the AMF (102) comprising the rejected S-NSSAI for the one or more network slices indicates a non-availability of the rejected S-NSSAI for communication.
  • the NSSAI controller (101C) is configured to receive the REGISTRATION ACCEPT message from the AMF (102) comprising the flag with a value zero "0" indicates there is no ongoing NSSAA pending with the AMF (102).
  • the NSSAI controller (101C) is configured to receive the REGISTRATION ACCEPT message from the AMF (102) comprising the flag with a value one "1" indicates the NSSAA is pending for the one or more network slices.
  • the NSSAI controller (101C) is configured to perform at least of deleting the pending S-NSSAI or awaiting for a Network Slice-Specific Authentication and Authorization (NSSAA) procedure from the AMF (102) based on a value of the flag.
  • NSSAA Network Slice-Specific Authentication and Authorization
  • the NSSAI controller (101C) is configured to delete the pending S-NSSAI based on the value of the flag comprises removing the one or more pending NSSAI stored in the UE (101) when the value of the flag is zero "0".
  • the NSSAI controller (101C) is configured to await for the NSSAA procedure based on the value of the flag comprises performing the NSSAA procedure with the AMF (102)when the value of the flag is one "1".
  • the NSSAI controller (101C) is configured to send a REGISTRATION REQUEST message comprises one or more access requests to the AMF (102) associated with a Home Public Land Mobile Network (HPLMN), or a Visiting Public Land Mobile Network (VPLMN).
  • a REGISTRATION REQUEST message comprises one or more access requests to the AMF (102) associated with a Home Public Land Mobile Network (HPLMN), or a Visiting Public Land Mobile Network (VPLMN).
  • the NSSAI controller (101C) is configured to receive a REGISTRATION ACCEPT message from the AMF (102) comprising the pending S-NSSAI associated with the one or more network slices includes the pending S-NSSAI from the one or more access requests.
  • the NSSAI controller (101C) is configured to replace a previous pending S-NSSAI with the pending S-NSSAI received from the AMF (102).
  • the AMF (102) comprises a processor (102A), a memory (102B), a NSSAI controller (102C) communicatively coupled to the processor (102A) and the memory (102B).
  • the NSSAI controller (102C) is configured to receive a REGISTRATION REQUEST message from a User Equipment (UE), wherein the REGISTRATION REQUEST message comprises a request for one of a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices, and the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • UE User Equipment
  • S-NSSAI Single-NSSAI
  • HPLMN Home Public Land Mobile Network
  • the NSSAI controller (102C) creates a REGISTRATION ACCEPT message, wherein the REGISTRATION ACCEPT message comprises one of at least one of a pending S-NSSAI, an allowed S-NSSAI, a rejected S-NSSAI, for the one or more network slices and a flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) when the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices; and at least one of an allowed NSSAI, and a rejected NSSAI, wherein the rejected NSSAI comprises a combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN when the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of a Single-NSSAI (S-NSSAI) associated with a Visiting Public Land Mobile Network (VPLMN) and a Home Public Land Mobile Network (HPLMN
  • the NSSAI controller (102C) is configured to receive the REGISTRATION REQUEST message from the UE (101) during at least one of a registration of the UE (101) with the AMF (102), a re-registration of the UE (101) with the AMF (102), and when an additional one or more network slices are required by the UE (101).
  • the NSSAI controller (102C) is configured to receive the REGISTRATION REQUEST message from the UE (101) comprises one or more access requests.
  • the NSSAI controller (102C) is configured to send the REGISTRATION ACCEPT message to the UE (101) comprising the pending S-NSSAI associated with the one or more network slices includes the pending S-NSSAI from the one or more access requests.
  • the NSSAI controller (102C) is configured to send the REGISTRATION ACCEPT message to the UE (101) comprising the pending S-NSSAI for the one or more network slices indicates a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • the NSSAI controller (102C) is configured to send the REGISTRATION ACCEPT message to the UE (101) comprising the allowed S-NSSAI for the one or more network slices indicates the UE (101) can use the allowed S-NSSAI for communication without completing the NSSAA.
  • the NSSAI controller (102C) is configured to send the REGISTRATION ACCEPT message to the UE (101) comprising the rejected S-NSSAI for the one or more network slices indicates a non-availability of the rejected S-NSSAI for communication.
  • the NSSAI controller (102C) is configured to send the REGISTRATION ACCEPT message to the UE (101) comprising the flag with a value zero "0" indicates there is no ongoing NSSAA pending for the one or more network slices with the AMF (102).
  • the NSSAI controller (102C) is configured to send the REGISTRATION ACCEPT message to the UE (101) comprising the flag with a value one "1" indicates the NSSAA is pending for the one or more network slices.
  • FIG. 4 shows a flowchart for handling Network Slice Selection Assistance Information (NSSAI) during network slicing, according to the embodiments as disclosed herein.
  • NSSAI Network Slice Selection Assistance Information
  • the User Equipment (UE) (101) creates a REGISTRATION REQUEST message.
  • the REGISTRATION REQUEST message comprises the request for the NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices.
  • S-NSSAI Single-NSSAI
  • the UE (101) may create the REGISTRATION REQUEST message with the S-NSSAI network slices 'A' and 'B'.
  • the REGISTRATION REQUEST message comprises the request for the NSSAI with the combination of a Single-NSSAI (S-NSSAI) associated with the Visiting Public Land Mobile Network (VPLMN) and the Home Public Land Mobile Network (HPLMN) of one or more network slices.
  • S-NSSAI Single-NSSAI
  • HPLMN Home Public Land Mobile Network
  • the UE (101) may create the REGISTRATION REQUEST message with the S-NSSAI network slices ⁇ H1, V1 ⁇ , ⁇ H2, V2 ⁇ , ⁇ H3, V3 ⁇ , and ⁇ H4, V4 ⁇ as shown in signal 1 of FIG. 6.
  • the one or more services provided using one or more network slices ('H1', 'H2', 'H3' and 'H4') in the HPLMN are provided using a single network slice ('V1') in the VPLMN.
  • the combination of the S-NSSAI indicates a mapping between the one or more network slices of the VPLMN and the HPLMN
  • the UE (101) creates the REGISTRATION REQUEST message during at least one of a registration of the UE (101) with the AMF (102), a re-registration of the UE (101) with the AMF (102), and when an additional one or more network slices are required by the UE (101).
  • the UE (101) sends the REGISTRATION REQUEST message to an Access and Mobility Management Function (AMF) (102).
  • AMF Access and Mobility Management Function
  • the UE (101) sends the REGISTRATION REQUEST message with the requested S-NSSAI network slices 'A' and 'B' as shown in signal 1 of FIG. 5. Further, the AMF (102) determines that the slices 'A' and 'B' are subjected to Network Slice Specific Authentication and Authorization (NSSAA) as shown in signal 2 of FIG.1. Further, the AMF (102) includes the slices 'A' and 'B' in the pending NSSAI.
  • NSSAA Network Slice Specific Authentication and Authorization
  • the UE (101) sends the REGISTRATION REQUEST message with the requested S-NSSAI network slices ⁇ V1, H1 ⁇ , ⁇ V1, H2 ⁇ , ⁇ V1, H3 ⁇ , and ⁇ V1, H4 ⁇ as shown in signal 2 of FIG. 6.
  • the HPLMN currently does not allow H2 to be accessed in the VPLMN.
  • the slices H3 and H4 cannot be accessed in the current Registration Area (RA) of the UE (101). Therefore, the slice H1 is allowed in the current RA of the VPLMN for the UE (101).
  • the AMF (102) determines that ⁇ V1, H1 ⁇ slice is allowed.
  • the slices ⁇ V1, H2 ⁇ , ⁇ V1, H3 ⁇ is rejected for the current PLMN, and ⁇ V1, H4 ⁇ is rejected for the current registration area as shown in signal 3 of the FIG. 6.
  • the UE (101) sends the REGISTRATION REQUEST message comprising one or more access requests (for example, access for H1, H2, H3 and H4) to the AMF (102).
  • the one or more access requests may be associated with the Home Public Land Mobile Network (HPLMN), or the Visiting Public Land Mobile Network (VPLMN).
  • the UE (101) receives a REGISTRATION ACCEPT message from the AMF (102).
  • the REGISTRATION REQUEST message comprises request for a NSSAI with Single-NSSAI (S-NSSAI) of one or more network slices
  • the REGISTRATION ACCEPT message comprises at least one of the pending S-NSSAI, the allowed S-NSSAI, and the rejected S-NSSAI, for the one or more network slices.
  • the REGISTRATION ACCEPT message comprises the flag indicating a status of Network Slice Specific Authentication and Authorization (NSSAA) as shown in signal 3 and signal 8 of the FIG. 5.
  • NSSAA Network Slice Specific Authentication and Authorization
  • the UE (101) receives the REGISTRATION ACCEPT message from the AMF (102) comprising the pending S-NSSAI for the one or more network slices.
  • the pending S-NSSAI indicates that a successful completion of the NSSAA is required for communication using the pending S-NSSAI.
  • the REGISTRATION ACCEPT message from the AMF (102) comprises the flag with a value one "1" when the NSSAA is pending for the one or more network slices as shown in signal 3 of the FIG. 5.
  • the UE (101) awaits for the NSSAA procedure from the AMF (102) when the value of the flag is one "1".
  • the AMF (102) initiates a NSSAA procedure for the UE (101) towards the AAA server as shown in signal 5 of FIG.1, when the flag with a value one "1" is sent to the UE (101).
  • the UE (101) modifies the requested NSSAI from slices 'A' and 'B' to slices 'C', and 'D' as shown in signal 4 of FIG.5.
  • the UE (101) initiates a mobility registration with the slices 'C', and 'D' in the requested NSSAI in the REGISTRATION REQUEST message as shown in signal 6 of FIG.5.
  • the AMF (102) determines that the slices 'C', and 'D' requested by the UE (101) are not subject to NSSAA as shown in signal 7 of FIG.5.
  • the AMF (102) aborts the ongoing NSSAA for S-NSSAI's 'A' and 'B' and processes the request for access to slices 'C' and 'D'.
  • the AMF (102) upon receiving the new requested NSSAI, identifies that the new slices 'C' and 'D' are different and access to the previously requested S-NSSAI's 'A' and 'B' is no more needed.
  • the AMF (102) sends the REGISTRATION ACCEPT message with the S-NSSAI 'C' and 'D' as the allowed NSSAI as shown in signal 8 of FIG.5.
  • the REGISTRATION ACCEPT message from the AMF (102) comprises the allowed S-NSSAI for the one or more network slices indicating that the UE (101) can use the allowed S-NSSAI for communication without completing the NSSAA.
  • the REGISTRATION ACCEPT message from the AMF (102) comprises the rejected S-NSSAI for the one or more network slices, then the rejected S-NSSAI is not available for communication by the UE (101).
  • the flag indicates that there is no ongoing NSSAA pending for the one or more network slices with the AMF (101) as shown in signal 8 of FIG.5.
  • the UE (101) deletes the pending S-NSSAI by removing the one or more pending NSSAI stored in the UE (101) when the value of the flag is zero "0" as shown in signal 9 of FIG.5.
  • the flag is denoted by "NSSAA performed" in 5GS registration.
  • the UE (101) may replace a previous pending S-NSSAI stored in the UE (101) with the pending S-NSSAI received from the AMF (102) in the REGISTRATION ACCEPT message.
  • AMF (102) sets the value of the "NSSAA performed” flag to 1 when an NSSAA is ongoing for a pending S-NSSAI as shown in signal 3 of FIG. 5.
  • the AMF (102) sets the value of the "NSSAA performed” flag to 0 in the REGISTRATION ACCEPT message, when there is no NSSAA ongoing as shown in signal 8 of FIG. 5.
  • the AMF remembers whether the slice that is subject to NSSAA has been requested by just one access request or by both the access requests and updates the specific access with the right allowed NSSAI (when a slice is subject to NSSAA). Furthermore, the AMF (102) updates the pending/allowed/rejected NSSAI in the one or more access requests.
  • the REGISTRATION REQUEST message comprises request for the NSSAI with a combination of the S-NSSAI associated with the VPLMN and the HPLMN of one or more network slices
  • the REGISTRATION ACCEPT message comprises at least one of the allowed NSSAI, and the rejected NSSAI as shown in signal 4 of the FIG. 6.
  • the rejected NSSAI comprises the combination of a Single-NSSAI (S-NSSAI) associated with the VPLMN and HPLMN and the reason for rejecting the NSSAI as shown in signal 4 of the FIG. 6.
  • the AMF (102) provides the mapped HPLMN S-NSSAI for the rejected NSSAI, in particular for the "rejected NSSAI for the current PLMN or RA" to avoid the ambiguity or the confusion in resolving the HPLMN S-NSSAI for the rejected S-NSSAI at the UE (101).
  • the inclusion of the mapped-HPLMN S-NSSAI avoids the abnormality in network slicing when the UE (101) is roaming in the VPLMN.
  • the UE (101) may remember the "VPLMN S-NSSAI + mapped HPLMN S-NSSAI" combinations sent in the requested NSSAI in the REGISTRATION REQUEST to the AMF (102) and resolve the ambiguity in the HPLMN S-NSSAI for the rejected S-NSSAI.
  • the UE (101) treats the mapped HPLMN S-NSSAI's not included in the requested NSSAI, apart from the ones received in the allowed NSSAI, have been rejected with cause "rejected NSSAI for the current PLMN or SNPN".
  • the UE (101) considers the slices as rejected only for the current registration area.
  • a new rejected NSSAI list may be used that is specific to S-NSSAI and is rejected as a result of a failed NSSAA procedure or after revocation of authorization for a slice or any other reject.
  • the new rejected NSSAI may be indicated for example, as a Rejected NSSAI due to NSSAA.
  • the new Rejected NSSAI due to NSSAA IE contains both the V-PLMN S-NSSAI and the mapped HPLMN S-NSSAI component similar to the NSSAI IE. Additionally, a cause code is included to indicate the reason for rejecting the S-NSSAI entry.
  • the IE should indicate the total length of the contents followed by a list of ⁇ length and S-NSSAI value ⁇ components, where the 'length' indicates the length of each S-NSSAI value and the latter is the S-NSSAI that is being rejected due to NSSAA.
  • the UE (101) constructs the requested NSSAI and checks for presence of certain slices in the rejected/pending NSSAI lists, the UE (101) checks against the mapped HPLMN NSSAI value as well. This is due to the fact that it is possible for only mapped values to be present in some of the lists or it is possible that unique values of comparison is a combination of the (VPLMN NSSAI + the mapped HPLMN NSSAI).
  • Use Case -1 Handling of pending NSSAI based on requested NSSAI of both 3GPP and non-3GPP access.
  • the network maintains the context of the slices requested via 3GPP access and non-3GPP access.
  • the AMF (102) includes the slices that were requested via that particular access in the pending NSSAI.
  • the UE (101) when the UE (101) sends the registration request message for changing the currently registered network slices or attempts to register the network slices (i.e. NSSAA ongoing), if there are one or more network slices not required by the UE and if the NSSAA procedure is ongoing, then the AMF (102) aborts the ongoing NSSAA procedure. Alternatively, if the one or more network slices is a part of the requested NSSAI of the other access, then the AMF (102) initiates the NSSAA procedure. Additionally the AMF (102) might continue to use the current access on which NSSAA was already ongoing to continue with the procedure or might switch the NSSAA onto the access for which the slice is still part of the requested NSSAI.
  • the UE (101) registers via 3GPP access and sends S-NSSAI slices 'A' and 'B' in the requested NSSAI. If the slices 'A' and 'B' are both subject to NSSAA, then NSSAA procedure is started over 3GPP access.
  • the AMF (102) provides the slices 'A' and 'B' in the pending NSSAI in the registration accept message via non-3GPP access.
  • the AMF (102) does not abort the ongoing NSSAA procedure because the slices 'A' and 'B' are still relevant for the non-3GPP access.
  • the AMF (102) continues the NSSAA for slices 'A' and 'B' via the access on which the procedure is already ongoing i.e. 3GPP. In another embodiment, the AMF (102) shifts the procedure onto non-3GPP access. For shifting the NSSAA, the AMF (102) continues with the next steps of the NSSAA and does not initiate it afresh. Alternately depending on implementation, the AMF (102) might start the NSSAA procedure afresh on the next access.
  • the UE (101) sends a first Registration Request over first access to a PLMN containing the Requested NSSAI consisting of S-NSSAI-1. If the S-NSSAI-1 is subject to NSSAA, then the AMF (102) sends the Registration Accept message containing S-NSSAI-1 as pending S-NSSAI to the UE (101) and the AMF (102) initiates the NSSAA procedure for the S-NSSAI-1. Further, the UE (101) stores the S-NSSAI-1 as pending S-NSSAI. The UE (101) may send a second Registration request over second access to the same PLMN and sends the Registration Request containing S-NSSAI-2.
  • the AMF (102) determines if the NSSAA of the S-NSSAI-1 is completed or not. If the NSSAA procedure of the S-NSSAI-1 is not completed then the AMF (102) sends the Registration accept message to the UE (102) containing Pending NSSAI consisting of S-NSSAI-1 and S-NSSAI-2. Alternatively, if the AMF (102) has completed the NSSAA procedure for S-NSSAI-1 then the AMF (102) includes S-NSSAI-2 in the pending NSSAI sent to the UE (101).
  • the UE (101) Upon receiving the Registration accept message, the UE (101) replaces the previous pending NSSAI list with the received pending NSSAI list.
  • the first access and the second access can be 3GPP access and non-3GPP access.
  • the first access and the second access are always different access for example if the first access is 3GPP access then second access in non-3GPP access.
  • the embodiments disclosed herein can be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.

Landscapes

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

Abstract

La présente divulgation concerne un procédé et un système de communication permettant de faire converger un système de communication de 5ème génération (5G) destiné à prendre en charge des débits supérieurs à ceux d'un système de 4ème génération (4G) avec une technologie de l'Internet des objets (IdO). La présente divulgation peut être appliquée à des services intelligents basés sur la technologie de communication 5G et sur la technologie liée à l'IdO, tels que la maison intelligente, le bâtiment intelligent, la ville intelligente, la voiture intelligente, la voiture connectée, les soins de santé, l'enseignement numérique, le commerce de détail intelligent, les services liés à la sûreté et à la sécurité. Des modes de la présente divulgation fournissent un procédé de gestion d'informations d'assistance de sélection de tranche de réseau (NSSAI).
PCT/KR2021/004830 2020-04-18 2021-04-16 Procédé de gestion de cas d'utilisation anormale associés à un découpage en tranches de réseau Ceased WO2021210960A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202041016739 2020-04-18
IN202041016739 2021-04-14

Publications (1)

Publication Number Publication Date
WO2021210960A1 true WO2021210960A1 (fr) 2021-10-21

Family

ID=78084449

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/004830 Ceased WO2021210960A1 (fr) 2020-04-18 2021-04-16 Procédé de gestion de cas d'utilisation anormale associés à un découpage en tranches de réseau

Country Status (1)

Country Link
WO (1) WO2021210960A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023147045A1 (fr) * 2022-01-27 2023-08-03 Interdigital Patent Holdings, Inc. Systèmes et procédés de sélection/resélection de vplmn basées sur des tranches de réseau

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270877A1 (en) * 2017-03-16 2018-09-20 Samsung Electronics Co., Ltd. Network-initiated pdu session connection update method between terminal and network
US20190053148A1 (en) * 2017-08-14 2019-02-14 Samsung Electronics Co., Ltd. Method for capability negotiation and slice information mapping between network and terminal in 5g system
US20190387576A1 (en) * 2017-06-19 2019-12-19 Huawei Technologies Co., Ltd. Registration Method, Session Establishment Method, Terminal, and AMF Entity

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270877A1 (en) * 2017-03-16 2018-09-20 Samsung Electronics Co., Ltd. Network-initiated pdu session connection update method between terminal and network
US20190387576A1 (en) * 2017-06-19 2019-12-19 Huawei Technologies Co., Ltd. Registration Method, Session Establishment Method, Terminal, and AMF Entity
US20190053148A1 (en) * 2017-08-14 2019-02-14 Samsung Electronics Co., Ltd. Method for capability negotiation and slice information mapping between network and terminal in 5g system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 24.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. V16.4.1, 1 April 2020 (2020-04-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 666, XP051861393 *
3GPP: "3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Procedures for the 5G System (5GS);Stage 2(Release 16", 3GPP TS 23.502 V16.4.0 (2020-03), 27 March 2020 (2020-03-27), XP002803444, Retrieved from the Internet <URL:https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3145> [retrieved on 20210623] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023147045A1 (fr) * 2022-01-27 2023-08-03 Interdigital Patent Holdings, Inc. Systèmes et procédés de sélection/resélection de vplmn basées sur des tranches de réseau

Similar Documents

Publication Publication Date Title
WO2020036366A1 (fr) Procédé et appareil de prise en charge d&#39;une tranche de réseau lorsqu&#39;un équipement utilisateur se déplace entre des réseaux 4g et 5g
WO2020251309A1 (fr) Procédé et appareil permettant de fournir un service dans un système de communication sans fil
WO2020036415A1 (fr) Procédé et appareil d&#39;accès mutuellement exclusif à des tranches de réseau dans un système de communication sans fil
WO2018128499A1 (fr) Procédé et appareil pour sélectionner une fonction de gestion d&#39;accès et de mobilité dans un système de communication mobile
WO2019194538A1 (fr) Procédé et appareil pour la fourniture d&#39;un service de notification d&#39;événement de mobilité de terminal dans un système de communications sans fil
WO2017052266A1 (fr) Procédé et appareil d&#39;amélioration de la mobilité dans un système de communications sans fil
EP4101129A1 (fr) Appareil et procédé de prise en charge d&#39;un service d&#39;exposition d&#39;événement d&#39;une upf dans un système de communication sans fil
WO2021182911A1 (fr) Procédé et appareil de fourniture d&#39;une fonction d&#39;accès à l&#39;orientation de trafic dans un système de communication sans fil
EP3725127A1 (fr) Procédé et système de commande de trafic à base de hplmn lors de l&#39;enregistrement d&#39;un ue sur différents plmn
WO2021167290A1 (fr) Procedé et appareil pour améliorer la précision de la sélection de réseau dans un système de communication sans fil
WO2022211424A1 (fr) Procédé et appareil de gestion de session
WO2020226345A1 (fr) Procédé et appareil de configuration de session d&#39;un terminal en fonction du temps ou de la zone de service dans un système de communication sans fil
WO2020166890A1 (fr) Procédé et appareil pour prendre en charge une réauthentification de session pdu autorisée dn et gérer une session pdu en fonction d&#39;un changement de données d&#39;autorisation dn
WO2021201648A1 (fr) Procédé et appareil de gestion de procédure liée à un cag dans un réseau de communication sans fil
WO2022075692A1 (fr) Procédé et appareil pour fournir un service à un serveur d&#39;application périphérique (eas) dans un réseau de données périphérique (edn)
WO2021033975A1 (fr) Procédé et appareil permettant de gérer une collision de liaison descendante et de liaison montante dans un réseau de communication sans fil
WO2023075418A1 (fr) Procédé et appareil de fourniture de tranche de réseau dans un système de communication sans fil
WO2022075705A1 (fr) Système et procédé de synchronisation d&#39;informations de groupe entre un ue et un serveur seal
WO2019216663A1 (fr) Procédé et appareil pour contrôler des problèmes de désadaptation d&#39;état rrc dans un système de communication mobile de prochaine génération
WO2021141288A1 (fr) Procédé permettant de contrôler l&#39;accès d&#39;un terminal à un réseau privé
WO2020209634A1 (fr) Procédé et appareil permettant de réaliser une communication dans un système de communication sans fil
WO2021235891A1 (fr) Procédé et dispositif pour découvrir et sélectionner un réseau pour fournir des données d&#39;abonné d&#39;équipement utilisateur
WO2022240070A1 (fr) Procédé et appareil de fourniture d&#39;un service d&#39;informatique en périphérie dans un système de communication sans fil
WO2021210960A1 (fr) Procédé de gestion de cas d&#39;utilisation anormale associés à un découpage en tranches de réseau
WO2023106865A1 (fr) Procédé d&#39;attribution d&#39;id de groupe pour transmission de groupe de contextes de session pfcp, et appareil associé

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21788136

Country of ref document: EP

Kind code of ref document: A1