EP4090060A2 - Découverte de commande d'admission de tranche de réseau (nsac) et améliorations de l'itinérance - Google Patents

Découverte de commande d'admission de tranche de réseau (nsac) et améliorations de l'itinérance Download PDF

Info

Publication number
EP4090060A2
EP4090060A2 EP22171438.9A EP22171438A EP4090060A2 EP 4090060 A2 EP4090060 A2 EP 4090060A2 EP 22171438 A EP22171438 A EP 22171438A EP 4090060 A2 EP4090060 A2 EP 4090060A2
Authority
EP
European Patent Office
Prior art keywords
nsacf
network
nssai
amf
network slice
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP22171438.9A
Other languages
German (de)
English (en)
Other versions
EP4090060A3 (fr
Inventor
Krisztian Kiss
Alosious Pradeep Prabhakar
Vijay Venkataraman
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.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Publication of EP4090060A2 publication Critical patent/EP4090060A2/fr
Publication of EP4090060A3 publication Critical patent/EP4090060A3/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • 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
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • 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/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • a network may deploy multiple network slices.
  • a network slice refers to an end-to-end logical network that is configured to provide a particular service and/or possesses particular network characteristics.
  • Each network slice may be isolated from one another but run on a shared network infrastructure. Thus, each network slice may share network resources but facilitate different functionality.
  • a network operator may want to limit the number of devices registered to a particular network slice.
  • the network may be equipped with a network slice admission control function (NSACF) to perform this task.
  • NSACF network slice admission control function
  • the NSACF may perform various operations related to managing the number of UEs and/or sessions registered to an individual network slice.
  • Some exemplary embodiments are related to an access and mobility management function (AMF) of a 5G core network configured to perform operations.
  • the operations include transmitting a network function registration request to a network resource function (NRF), receiving a response to the network function registration request from the NRF, transmitting a network function discovery request to the NRF, the network function discovery request including one or more single network slice selection assistance information (S-NSSAI) and an indication that the discovery request is for a network slice admission control function (NSACF) and receiving a network function discovery response from the NRF, wherein the network function discovery response includes a NSACF address.
  • S-NSSAI single network slice selection assistance information
  • NSACF network slice admission control function
  • exemplary embodiments are related to a network slice admission control function (NSACF) of a 5G core network configured to perform operations.
  • the operations include transmitting a network function registration request to a network resource function (NRF), receiving a response to the network function registration request from the NRF, transmitting a network function discovery request to the NRF, the network function discovery request including one or more single network slice selection assistance information (S-NSSAI) and an indication that the discovery request is for an access and mobility management function (AMF) and receiving a network function discovery response from the NRF.
  • NRF network resource function
  • S-NSSAI single network slice selection assistance information
  • AMF access and mobility management function
  • Still further exemplary embodiments are related to a network slice admission control function (NSACF) of a 5G core network configured to perform operations.
  • the operations include maintaining a network slice quota for one or more network slices, wherein the NSACF is configured to enforce network slice admission control (NSAC) for both a visiting public land mobile network (VPLMN) and a home public land mobile network (HPLMN), receiving a number of registered user equipment (UEs) per network slice availability check and update request from an access and mobility management function (AMF) and transmitting a response to the AMF, the response indicating whether a maximum number of registered UEs or sessions for the S-NSSAI has been reached.
  • NSACF network slice admission control function
  • NSAC network slice admission control
  • 3GPP third generation partnership
  • network slicing refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure.
  • Each network slice may be configured to provide a particular set of capabilities and/or characteristics.
  • the physical infrastructure of the 5G network may be sliced into multiple virtual networks, each configured for a different purpose.
  • reference to a network slice may represent any type of end-to-end logical network that is configured to serve a particular purpose and implemented on the 5G physical infrastructure.
  • 5G may support a variety of different use cases, e.g., enhanced mobile broadband (eMBB), enhanced machine type communication (eMTC), industrial internet of things (IIoT), etc.
  • eMBB enhanced mobile broadband
  • eMTC enhanced machine type communication
  • IIoT industrial internet of things
  • a network slice may be characterized by a type of use case, a type of application and/or service or the entity that provides the application and/or service via the network slice.
  • any example in this description that characterizes a network slice in a specific manner is only provided for illustrative purposes.
  • reference to a network slice may represent any type of end-to-end logical network that is configured to serve a particular purpose and implemented on the 5G physical infrastructure.
  • a network slice may be identified by single network slice selection assistance information (S-NSSAI).
  • S-NSSAI single network slice selection assistance information
  • Each instance of S-NSSAI may be associated with a public land mobile network (PLMN) and may include the slice service type (SST) and a slice descriptor (SD).
  • the SST may identify the expected behavior of the corresponding network slice with regard to services, features and characteristics.
  • PLMN public land mobile network
  • SST slice service type
  • SD slice descriptor
  • the SST may identify the expected behavior of the corresponding network slice with regard to services, features and characteristics.
  • the SD may identify any one or more entities associated with the network slice.
  • the SD may indicate an owner or an entity that manages the network slice (e.g., carrier) and/or the entity that the is providing the application/service via the network slice (e.g., a third-party, the entity that provides the application or service, etc.).
  • the same entity may own the slice and provide the service (e.g., carrier services).
  • S-NSSAI refers to a single network slice and the terms "NSSAI" or "S-NSSAIs" may be used interchangeably to refer to one or more network slices.
  • a user equipment may be configured to perform any of a wide variety of different tasks.
  • the UE may be configured to utilize one or more network slices.
  • the UE may utilize a first network slice for one or more carrier services (e.g., voice, multimedia messaging service (MMS), Internet, etc.) and a second different network slice for a third-party service.
  • carrier services e.g., voice, multimedia messaging service (MMS), Internet, etc.
  • MMS multimedia messaging service
  • the configured purpose of a network slice is beyond the scope of the exemplary embodiments.
  • the exemplary embodiments are not limited to any particular type of network slice. Instead, the exemplary embodiments introduce enhancements related to NSAC.
  • the exemplary embodiments are also described with regard to a network slice admission control function (NSACF).
  • the NSACF refers to a network function that is configured to control and restrict the number of UEs and/or packet data unit (PDU) sessions registered to a particular network slice.
  • the NSACF may perform various operations related to enforcing a quota for a maximum number of UEs registered to a particular network slice (e.g., S-NSSAI).
  • a NSACF service area is related to the location of the network function consumer.
  • reference to the term NSACF is merely provided for illustrative purposes.
  • Different networks may refer to a similar concept by a different name, for example, 3GPP networks may use the terms NSACF and network slice quota function (NSQ) interchangeably.
  • the exemplary embodiments relate to NSAC discovery and early admission control (EAC).
  • EAC NSAC discovery and early admission control
  • the exemplary embodiments include enhancements for a NSACF discovery procedure initiated by an access and mobility management function (AMF), enhancements for an AMF discovery procedure initiated by the NSACF and enhancements for an EAC update procedure between the AMF and the NSACF.
  • the exemplary embodiments relate to NSAC within the context of a roaming scenario.
  • the exemplary embodiments include enhancements for a NSACF deployed by a visited public land mobile network (VPLMN) and a NSACF deployed by a home public land mobile network (HPLMN).
  • the exemplary enhancements described here may be used in conjunction with currently implemented NSAC protocols and policies or future implementations of NSAC protocols and policies.
  • Fig. 1 shows an exemplary network arrangement 100 according to various exemplary embodiments.
  • the exemplary network arrangement 100 includes the UE 110.
  • the UE 110 may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (IoT) devices, etc.
  • IoT Internet of Things
  • an actual network arrangement may include any number of UEs being used by any number of users.
  • the example of a single UE 110 is merely provided for illustrative purposes.
  • the UE 110 may be configured to communicate with one or more networks.
  • the network with which the UE 110 may wirelessly communicate is a 5G new radio (NR) radio access network (RAN) 120.
  • NR new radio
  • RAN radio access network
  • the UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, a next generation RAN (NG-RAN), long term evolution (LTE) RAN, a legacy cellular network, a wireless local area network (WLAN), etc.) and the UE 110 may also communicate with networks over a wired connection. Therefore, in this example, the UE 110 may have a 5G NR chipset to communicate with the 5G NR RAN 120.
  • the 5G NR RAN 120 may be a portion of a cellular network that may be deployed by cellular providers (e.g., Verizon, AT&T, T-Mobile, etc.).
  • the 5G NR RAN 120 may include, for example, cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.) that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set.
  • the 5G NR RAN 120 is shown with a gNB 120A.
  • an actual network arrangement may include any number of different types of base stations or cells deployed by any number of RANs.
  • the example of a single 5G NR RAN 120 and a single gNB 120A is merely provided for illustrative purposes.
  • any association procedure may be performed for the UE 110 to connect to the 5G NR RAN 120.
  • the 5G NR RAN 120 may be associated with a particular network carrier where the UE 110 and/or the user thereof has a contract and credential information (e.g., stored on a SIM card).
  • the UE 110 may transmit the corresponding credential information to associate with the 5G NR RAN 120.
  • the UE 110 may associate with a specific base station or cell (e.g., gNB 120A).
  • the network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160.
  • the cellular core network 130 may be considered to be the interconnected set of components that manages the operation and traffic of the cellular network. It may include the evolved packet core (EPC) and/or the 5G core (5GC).
  • the cellular core network 130 also manages the traffic that flows between the cellular network and the Internet 140.
  • the IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol.
  • the IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110.
  • the network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130.
  • the network services backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the
  • Fig. 2 shows an exemplary network architecture 200 according to various exemplary embodiments.
  • the following description will provide a general overview of the various components of the exemplary architecture 200. The specific operations performed by the components with respect to the exemplary embodiments will be described in greater detail after the description of the architecture 200.
  • the components of the exemplary architecture 200 may reside in various physical and/or virtual locations relative to the network arrangement 100 of Fig. 1 . These locations may include, within the access network (e.g., RANs 120), within the core network 130, as separate components outside of the locations described with respect to Fig. 1 , etc.
  • connection labeled Nx e.g., N1, N2, N11, Nsmf, Namf, Nnssf, Nnrf, Nnsacf, etc.
  • Nx e.g., N1, N2, N11, Nsmf, Namf, Nnssf, Nnrf, Nnsacf, etc.
  • connections labeled Nx e.g., N1, N2, N11, Nsmf, Namf, Nnssf, Nnrf, Nnsacf, etc.
  • the UE 110 may exchange signals over the air with the cell 120A.
  • the UE 110 is shown as having a connection to the AMF 205.
  • This connection or interface is not a direct communication link between the UE 110 and the AMF 205, but is a connection that is facilitated by intervening hardware and software components.
  • connection and “interface” may be used interchangeably to describe the Nx interface between the various components.
  • the architecture 200 includes the UE 110 and the 5G NR RAN 120.
  • the UE 110 and the 5G NR RAN 120 are connected to the AMF 205.
  • the AMF 205 is generally responsible for connection and mobility management in the 5G NR RAN 120.
  • the AMF 205 may perform operations related to registration procedure management between the UE 110 and the core network 130.
  • the exemplary embodiments are not limited to an AMF that performs the above reference operations. Those skilled in the art will understand the variety of different types of operations an AMF may perform. Further, reference to a single AMF 205 is merely for illustrative purposes, an actual network arrangement may include any appropriate number of AMFs.
  • the AMF 205 is connected to the session management function (SMF) 210.
  • the SMF 210 may perform operations related to session management such as, but not limited to, session establishment, session release, IP address allocation, policy and quality of service (QoS) enforcement, etc.
  • the exemplary embodiments are not limited to an SMF that performs the above reference operations. Those skilled in the art will understand the variety of different types of operations a SMF may perform. Further, reference to a single SMF 210 is merely for illustrative purposes, an actual network arrangement may include any appropriate number of SMFs.
  • the AMF 205 and the SMF 210 are also connected to the network slice selection function (NSSF) 215, the network resource function (NRF) 220 and the NSACF 225.
  • the NSSF 215 performs operations related to network slicing. For example, the NSSF 215 may select a set of network slice instances serving the UE 110.
  • the NSSF 215 may also manage one or more databases that include a mapping table of S-NSSAI and the frequency bands in which the S-NSSAI is allowed to operate.
  • the NRF 220 may perform operations related to network service discovery functionality which allows network functions to determine where and how to access other network functions.
  • network resource function is merely provided for illustrative purposes. Different networks may refer to a similar entity by a different name, for example, 3GPP networks may use the terms network resource function and network repository function interchangeably.
  • the NSACF 225 may be configured to perform operations related to controlling the number of UEs and/or sessions registered per network slice for network slices that are subject to NSAC. During operation, the NSACF 225 may check a count of registered UEs and/or PDU sessions with the S-NSSAI and determine whether the network slice quota has been reached. The NSACF 225 may then accept or reject the register request based on the count and the quota.
  • a quota concept is merely provided for illustrative purposes. Those skilled in the art will understand that different entities may refer to similar concepts by a different name. For example, 3GPP networks may use the terms quota and admission control to refer to the same concept. Further, reference to a single NSACF 225 is merely for illustrative purposes, an actual network arrangement may include any appropriate number of NSACFs.
  • the NSACF 225 may be configured with a maximum number of PDU session per network slice that are allowed to be served by multiple network slices that are subject to NSAC.
  • the SMF 210 may be triggered to send a request to the NSACF 225 for a maximum number of PDU sessions per network slice admission control during PDU session establishment/release procedures.
  • the NSACF 225 may control (e.g., increase, decrease, etc.) the current number of PDU sessions per network slice such that it does not exceed the maximum number of PDU sessions allowed to be served by that network slice.
  • the NSACF 225 may check whether the maximum number of PDU sessions per network slice for that network slice has already been reached. The NSACF 225 may then accept or reject the request based on the count and the quota.
  • the NSACF 225 may be configured with a maximum number of UEs per network slice which are allowed to be served by each network slice that is subject to NSAC.
  • the AMF 205 may be triggered to send a request to the NSACF 225 for a maximum number of UEs per network slice admission control when the UE's registration status for a network slice subject to NSAC may change.
  • the registration status may change during procedures such as, but not limited to, a UE registration procedure, a UE deregistration procedure, a network slice-specific authentication and authorization procedure, an authentication authorization and accounting (AAA) server triggered network slice-specific re-authorization and re-authorization procedure and a AAA server triggered slice-specific authorization revocation.
  • AAA authentication authorization and accounting
  • the NSACF 225 may control (e.g., increase, decrease, etc.) the current number of UEs registered with a network slice such that it does not exceed the maximum number of UEs allowed to register with that slice.
  • the NSACF 225 may also maintain a list of UE IDs registered with a network slice that is subject to NSAC.
  • the NSACF 225 may first check whether the UE identity is already in the list of UEs registered with that network slice. If not, the NSACF 225 may check whether the maximum number of UEs per network slice for that particular network slice has already been reached. The NSACF 225 may then accept or reject the request based on the count and the quota.
  • exemplary enhancements related to NSAC discovery will be described in detail below. Initially, enhancements for a NSACF discovery procedure initiated by the AMF 205 will be described with regard to the signaling diagram 300 of Fig. 3 . After, an exemplary AMF discovery procedure initiated by the NSACF 225 will be described with regard to the signaling diagram 400 of Fig. 4 . Subsequently, an exemplary EAC update procedure between the AMF 205 and the NSACF 225 will be described with regard to the signaling diagram 600 of Fig. 6 . The exemplary AMF discovery procedure may provide the basis for the enhancements introduced for the exemplary EAC update procedure.
  • Fig. 3 shows a signaling diagram 300 for a NSACF discovery procedure according to various exemplary embodiments.
  • the signaling diagram 300 will be described with regard to the network architecture 200 and include the AMF 205 and the NRF 220.
  • the NSACF discovery procedure may be initiated by the AMF 205.
  • the AMF 205 may transmit a network function registration request to the NRF 220.
  • the network function registration request may be transmitted by the AMF 205 to the NRF 220 over the Namf and/or Nnrf interfaces shown in Fig. 2 .
  • This request may be referred to as a "Nnrf_NFManagement_NFRegister_Request" and may include one or more globally unique AMF IDs (GUAMIs) and a list of S-NSSAI(s) supported by the AMF 205.
  • GUIAMIs globally unique AMF IDs
  • the AMF 205 may include the list of S-NSSAI(s) the AMF 205 supports in the Nnrf_NFManagement_NFRegister operation.
  • the list of S-NSSAI(s) supported by the AMF 205 is not provided to the NRF 220.
  • this exemplary enhancement allows the NRF 220 to know the S-NSSAI supported by this particular AMF 205.
  • the NRF 220 is able to provide a list of S-NSSAI supported the AMF 205 to the NSACF 225 in an AMF discovery procedure.
  • the NRF 220 may transmit a response to the network function registration request to the AMF 205.
  • This response may indicate whether or not the registration request was successful.
  • this response may be transmitted by the NRF 220 to the AMF 205 over the Nnrf and/or Namf interfaces shown in Fig. 2 .
  • This request may be referred to as a "Nnrf_NFManagement_NFRegister_Response" and comprise a result (e.g., successful, failure, etc.). In this example, it is assumed that the registration attempt is successful.
  • the AMF 205 may transmit a discovery request to the NRF 220.
  • the discovery request may be transmitted by the AMF 205 to the NRF 220 over the Nnrf and/or Namf interfaces shown in Fig. 2 .
  • This request may be referred to as a "Nnrf_NFDiscovery_Request" and may include S-NSSAI(s) and an indication that the discovery request is for a NSACF.
  • the target network function of the Nnrf_NFDiscovery service is an NSACF
  • the discovery request may include S-NSSAI(s).
  • the NRF 220 may transmit a discovery response to the AMF 205.
  • the discovery response may be transmitted by the NRF 220 to the AMF 205 over the Nnrf and/or Namf interfaces shown in Fig. 2 .
  • This response may be referred to as a "Nnrf_NFDiscovery_Response" and may include an address for the NSACF 225.
  • this response may include the other S-NSSAI(s) supported by the NSACF 225.
  • the discovery response may include the list of S-NSSAI(s) for which the NSACF 225 manages admission control.
  • the other S-NSSAI(s) supported by the NSACF 225 are not provided to the AMF 205 during the discovery procedure.
  • the AMF 205 may only be aware of a NSACF corresponding to a particular S-NSSAI when that particular S-NSSAI is provided to the NRF 220 in the discovery request and the corresponding NSACF address is provided in the response.
  • the exemplary embodiments incorporate the other S-NSSAI(s) supported by the NSACF 225 in the discovery response in an attempt to reduce the number of subsequent discovery requests that may transmitted by the AMF 205.
  • the AMF 205 may use the information of the other S-NSSAI(s) supported by the NSACF 225 received in 320 to determine that requested NSSAI in a registration request from the UE 110 contains an S-NSSAI subject to access control for which the AMF 205 has not previously performed a NSACF discovery procedure.
  • the AMF 205 since the AMF 205 knows the other S-NSSAI(s) supported by the NSACF 225, the AMF 205 may use the information received in 320 instead of transmitting a subsequent discovery request to the NRF 220.
  • request NSACF 225 to check whether quota is available for another UE/session, transmit a context request to the SMF 210 or any other appropriate operation
  • Fig. 4 shows a signaling diagram 400 for an AMF discovery procedure according to various exemplary embodiments.
  • the signaling diagram 400 will be described with regard to the network architecture 200 and include the NSACF 225 and the NRF 220.
  • the AMF discovery procedure may be initiated by the NSACF 225.
  • the NSACF 225 may transmit a network function registration request to the NRF 220.
  • the network function registration request may be transmitted by the NSACF 225 to the NRF 220 over the Nnsacf and/or Nnrf interfaces shown in Fig. 2 .
  • This request may be referred to as a "Nnrf_NFManagement_NFRegister_Request" and may include a list of S-NSSAI(s) supported by the NSACF 225.
  • the NSACF 225 may include the list of S-NSSAI(s) for which the NSACF 225 manages access control in the Nnrf_NFManagement_NFRegister operation.
  • the list of S-NSSAI(s) supported by the NSACF 225 is not provided to the NRF 220.
  • This exemplary enhancement allows the NRF 220 to know the S-NSSAI supported by this particular NSACF 225.
  • the NRF 220 is able to provide a list of S-NSSAI supported the NSACF 225 to the AMF 205 in the NSACF discovery procedure.
  • the exemplary enhancement referenced above with regard to 320 of the signaling diagram 300 may be enabled by this message in 405.
  • the NRF 220 may transmit a response to the network function registration request to the NSACF 225.
  • This response may indicate whether or not the registration request was successful.
  • this response may be transmitted by the NRF 220 to the NSACF 225 over the Nnrf and/or Nnsacf interfaces shown in Fig. 2 .
  • This request may be referred to as a "Nnrf_NFManagement_NFRegister_Response" and comprise a result (e.g., successful, failure, etc.). In this example, it is assumed that the registration attempt is successful.
  • the NSACF 225 may transmit a discovery request to the NRF 220.
  • the discovery request may be transmitted by the NSACF 225 to the NRF 220 over the Nnrf and/or Nnsacf interfaces shown in Fig. 2 .
  • This request may be referred to as a "Nnrf_NFDiscovery_Request" and may include S-NSSAI(s) and an indication that the discovery request is for a AMF 205.
  • the NRF 220 may transmit a discovery response to the NSACF 225.
  • the discovery response may be transmitted by the NRF 220 to the NSACF 225 over the Nnrf and/or Nnsacf interfaces shown in Fig. 2 .
  • This response may be referred to as a "Nnrf_NFDiscovery_Response" and may include a list of one or more AMFs, their corresponding GUAMI(s) and the S-NSSAI(s) supported by each AMF.
  • the discovery response may include a list of GUAMI(s), a list of GUAMI(s) for which is can server as backup and the S-NSSAI(s) the AMF 205 supports.
  • the methods 300, 400 of Figs 3 and 4 may be related to each other and that the various operations of these methods may be performed in any order.
  • the NSACF registration operations 405 and 410 of method 400 may be performed.
  • the method 300 may be performed by the AMF.
  • the NSACF registration operations are precursors to the AMF operations of Fig. 3 .
  • other orders of the operations of methods 300 and 400 may be used.
  • Fig. 5 shows a table 500 that illustrates an example of the exemplary information that may be included in by a NRF in a discovery response transmitted to the NSACF during an AMF discovery procedure.
  • the table includes column 505 for AMF details, column 510 for the corresponding GUAMI and column 515 for the list of S-NSSAI(s) supported by the corresponding GUAMI. This column may be used as a look up table by the NSACF 225 to find the appropriate AMF for the EAC update procedure.
  • this exemplary enhancement may be enabled by the exemplary enhancement introduced in 305 of the signaling diagram 300 where the AMF 205 provides include GUAMI(s) and a list of S-NSSAI(s) supported by the AMF 205 during the NSACF discovery procedure.
  • the signaling diagram 400 introduces the NSACF as a consumer for some NRF services and operations.
  • the NSACF 225 was shown as being a consumer for Nnrf_NFmanagement services, e.g., the NFRegister request and response operations.
  • the NSACF 225 was shown as being a consumer for Nnrf_NFDiscovery services, e.g., the NFDiscovery request and response operations.
  • the NSACF 225 may also be a consumer of the Nnrf_NFmanagement services "NFupdate" request/response operations and a consumer of the "NFDeregister" request/response operations.
  • the exemplary enhancement shown in 420 may provide the basis for exemplary enhancements introduced for the EAC update procedure.
  • the EAC update procedure indicates to the AMF 204 the activation or deactivation of the EAC mode for the S-NSSAI subject to NSAC.
  • the EAC mode of the S-NSSAI may control whether the AMF 205 is required to perform a network slice availability check and update procedure before the S-NSSAI is considered an allowed S-NSSAI of the UE 110.
  • Fig. 6 shows a signaling diagram 600 for an exemplary EAC update procedure according to various exemplary embodiments.
  • the signaling diagram 600 will be described with regard to the network architecture 200 and include the NSACF 225 and the AMF 205.
  • the NSACF 225 determines that a number of UEs (or sessions) registered with a network slice subject to NSAC crosses a threshold value. This threshold value indicates whether EAC mode for the S-NSSAI is to be activated or deactivated.
  • the NSACF 225 transmits an EAC mode activation or deactivation command to the AMF 205.
  • the determination in 605 may trigger the NSACF 225 to transmit a message that include one or more S-NSSAI and an EAC flag for each S-NSSAI.
  • the EAC flag for an S-NSSAI may be set to activated if the number of UEs registered with the network slice is above the threshold value.
  • the EAC flag for the S-NSSAI may be set to deactivated if the number of UEs registered with the network slice is below the threshold value.
  • This message may be referred to as a "Nnsacf_NumberOfUEsPerSliceEACnotify" message.
  • the NSACF 225 may be unable to determine which of the AMFs deployed by the network is to be notified when the threshold value is reached.
  • the exemplary enhancements described above with regard to the signaling diagrams 300-400 may provide a solution to this issue.
  • one of exemplary enhancements introduced in the signaling diagram 300 was the AMF 205 providing GUAMI(s) and a list of S-NSSAI(s) supported by the AMF 205 to the NRF 220 in the registration request 405.
  • the information obtained by the NRF 220 may be provided to the NSACF 225 in the AMF discovery response. Since the NSACF 225 has this information, the NSACF may trigger the Nnsacf_NumberOfUEsPerSliceEACnotify operations to notify only the one or more AMFS that support the corresponding S-NSSAI.
  • the AMF 205 uses the EAC flag to decide when to trigger the number of UEs per network slice availability check and update procedure. This may reduce delays to the registration procedure and avoid negatively impacting already allowed network slices.
  • the AMF 205 may trigger the number of UEs per network slice availability check and update procedure before the registration accept step of the registration procedure or before the UE configuration update message. In other words, if it is likely that the quota for the network slice has been reached, the AMF 205 may perform the availability check before these messages are to be provided to the UE 110.
  • the AMF 205 triggers the number of UEs per network slice availability check and update procedure after the registration accept step of the registration procedure or after the UE configuration update message.
  • the exemplary embodiments relate to the behavior of a NSACF within the context of a roaming scenario.
  • a roaming scenario Prior to discussing the exemplary embodiments an example of two different roaming scenarios are described below.
  • Fig. 7 shows an example of a local-breakout (LBO) roaming scenario 700.
  • This example 700 includes the UE 110, a VPLMN 710, a HPLMN 750, a data network 715, a NSACF deployed by the VPLMN (vNSACF) 712, a NSACF deployed by the HPLM (hNSACF) 852, a security edge protection proxy (SEPP) 714 on the VPLMN side and a SEPP 754 on the HPLMN side.
  • SEPPs 714, 754 may act as a service relay between the VPLMN 710 and the HPLMN 750 for providing secured connection as well as hiding network topology.
  • IP internet-protocol
  • Fig. 8 shows an example of a home-routed roaming scenario 800.
  • This example 800 includes the UE 110, a VPLMN 810, a HPLMN 850, a data network 855, a NSACF deployed by the VPLMN (vNSACF) 812, a NSACF deployed by the HPLMN (hNSACF) 852.
  • a SEPP 814 on the VPLMN side and a SEPP 854 on the HPLMN side may act as a service relay between the VPLMN 810 and the HPLMN 850 for providing secured connection as well as hiding network topology.
  • the VPLMN 810 data traffic is routed to the data network 855 via the HPLMN 850.
  • This scenario provides an operator with more control with regard to offering roaming services, policy and charging to subscribers.
  • the IP address for the data network 855 may be obtained from the HPLMN 850.
  • NSAC for roaming UEs may be performed by both the VPLMN and the HPLMN.
  • a NSACF in the VPLMN may be configured by both the HPLMN and the VPLMN with a maximum number of roaming UEs per network slice what are allowed to be served by each network slice that is subject to NSAC.
  • the NSACF in the VPLMN may perform NSAC for both the S-NSSAI in the VPLMN and the corresponding mapped S-NSAAI in the HPLMN.
  • a NSACF e.g., vNSACF 712
  • a NSACF may be configured with the maximum number of PDU sessions per network slice in LBO mode which are allowed to be served by each network slice that is subject to NSAC.
  • the AMF may trigger a request to a NSACF in the serving PLMN (e.g., vNSACF 712) to perform network slice admission control.
  • a NSACF in the serving PLMN e.g., vNSACF 712
  • the NSACF in the HPLMN e.g., hNSACF 752
  • a NSACF e.g., hNSACF 852 in the HPLMN 850 may be configured with a maximum number of PDU sessions per network slice and a NSACF (e.g., vNSACF 812) in the VPLMN 810 may be configured with a maximum number of PDU sessions per network slice in home-routed mode which are allowed to be served by each network slice that is subject to NSAC.
  • Both NSACFs may perform NSAC, where the vNSACF 812 performs NSAC for the S-NSSAI in the VPLMN 810 and the hNSACF 852 in the HPLMN 850 performs NSAC for the corresponding mapped S-NSSAI in the HPLMN.
  • the SMF of the VPLMN may trigger a request to the vNSACF 812 in the VPLMN 810.
  • the SMF of the HPLMN 850 may trigger a request to the hNSACF 852 in the HPLMN 850 to perform a maximum number of PDU sessions admission control.
  • Fig. 9 shows a signaling diagram 900 for a number of UEs per network slice availability check and update procedure according to various exemplary embodiments.
  • the signaling diagram 900 includes the AMF 205 and the NSACF 225.
  • enhancements for network slice admission control support for roaming will be described with regard to the signaling diagram 900, the LBO roaming scenario 700 and the home-routed roaming scenario 800.
  • the number of UEs per network slice availability check and update procedure is to update (e.g., increase or decrease) the number of UEs registered with a S-NSSAI which is subject to NSAC.
  • the AMF 205 may be configured with the information indicating which network slice is subject to NSAC.
  • the AMF 205 triggers the number of UEs per network slice availability check and update procedure to update the number of UEs registered with a network slice when a network slice subject to NSAC is included or removed from the allowed NSSAI for a UE.
  • the AMF 205 transmits a number of UEs per network slice availability check and update request to the NSACF 225.
  • this message may be referred to as a "Nnsacf_NumberOfUEsPerSliceAvailailityCheckandUpdate_Request" and include information such as, but not limited to, the UE ID, the S-NSSAI(s) for which the number of UEs registered per network slice update is required and the update flag which indicates whether the number of UEs registered per network slice update is to be increased or decreased.
  • the NSACF 225 updates the current number of registered UEs for the S-NSSAI.
  • the NSCAF 225 may increase or decrease number of UEs registered per network slice based on the information provided by the AMF 205 in the update flag parameter.
  • the NSACF 225 transmits a response to the request to the AMF 205.
  • this message may be referred to as a "Nnsacf_NumberOfUEsPerSliceAvailabilityCheckandUpdate_Response" and include information such as, but not limited to, the S-NSSAI(s) for which the maximum number of UEs per network slice has already been reached along with a result parameter indicating the maximum number of UEs registered with the network slice has been reached. If all the S-NSSAI the NSACF 225 returned to the AMF 205 have been reached, the AMF 205 may reject the request from the UE 110. Otherwise, the AMF 205 returns registration accept message in which the AMF 205 includes the rejected S-NSSAI(s) in the rejected NSSAI list.
  • a maximum number of roaming UEs per network slice or a maximum number of PDU sessions per network slice in LBO mode or a maximum number of PDU sessions per network slice in home-routed mode is allocated to the VPLMN per SLA agreement and stored in one responsible vNSACF of the S-NSSAI.
  • the maximum number of UEs registered with a network slice monitoring and enforcement is done in the VPLMN by the vNSACF.
  • the AMF 205 may provide both the S-NSSAI in the VPLMN and the corresponding mapped S-NSSAI in HPLMN to the vNSACF.
  • the vNSACF performs NSAC for the S-NSAAI in the VPLMN based on the SLA with the UE's HPLMN.
  • the maximum number of PDU session per network slice monitoring and enforcement is done in both the VPLMN 810 by the vNSACF 812 and the HPLMN 850 by the hNSACF 852.
  • Fig. 10 shows an exemplary UE 110 according to various exemplary embodiments.
  • the UE 110 will be described with regard to the network arrangement 100 of Fig. 1 .
  • the UE 110 may include a processor 1005, a memory arrangement 1010, a display device 1015, an input/output (I/O) device 1020, a transceiver 1025 and other components 130.
  • the other components 1030 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, etc.
  • the processor 1005 may be configured to execute a plurality of engines of the UE 110.
  • the engines may include a session management engine 1035.
  • the session management engine 1035 may perform various operations related to establishing and maintaining a PDU session.
  • the above referenced engine 1035 being an application (e.g., a program) executed by the processor 205 is merely provided for illustrative purposes.
  • the functionality associated with the engine 235 may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e.g., an integrated circuit with or without firmware.
  • the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information.
  • the engines may also be embodied as one application or separate applications.
  • the functionality described for the processor 1005 is split among two or more processors such as a baseband processor and an applications processor.
  • the exemplary embodiments may be implemented in any of these or other configurations of a UE.
  • the memory arrangement 1010 may be a hardware component configured to store data related to operations performed by the UE 110.
  • the display device 1015 may be a hardware component configured to show data to a user while the I/O device 1020 may be a hardware component that enables the user to enter inputs.
  • the display device 1015 and the I/O device 1020 may be separate components or integrated together such as a touchscreen.
  • the transceiver 1025 may be a hardware component configured to establish a connection with the 5G NR-RAN 120 and/or any other appropriate type of network. Accordingly, the transceiver 1025 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies).
  • Fig. 11 shows an exemplary base station 1100 according to various exemplary embodiments.
  • the base station 1100 may represent any access node (e.g., gNB 120Ae, etc.) through which the UE 110 may establish a connection and manage network operations.
  • gNB 120Ae any access node
  • the base station 1100 may include a processor 1105, a memory arrangement 1110, an input/output (I/O) device 1115, a transceiver 1120, and other components 1125.
  • the other components 1125 may include, for example, a battery, a data acquisition device, ports to electrically connect the base station 1100 to other electronic devices, etc.
  • the processor 1105 may be configured to execute a plurality of engines of the base station 1100.
  • a processor 1105 is only exemplary.
  • the functionality associated with the engines may also be represented as a separate incorporated component of the base station 1100 or may be a modular component coupled to the base station 1100, e.g., an integrated circuit with or without firmware.
  • the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information.
  • the functionality described for the processor 305 is split among a plurality of processors (e.g., a baseband processor, an applications processor, etc.).
  • the exemplary embodiments may be implemented in any of these or other configurations of a base station.
  • the memory 1110 may be a hardware component configured to store data related to operations performed by the base station 1100.
  • the I/O device 1115 may be a hardware component or ports that enable a user to interact with the base station 1100.
  • the transceiver 1120 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100.
  • the transceiver 1120 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies). Therefore, the transceiver 1120 may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs.
  • a network slice admission control function (NSACF) of a 5G core network is configured to perform operations comprising maintaining a network slice quota for one or more network slices, wherein the network function is a network slice admission control function (NSACF) configured to enforce network slice admission control (NSAC) for both a visiting public land mobile network (VPLMN) and a home public land mobile network (HPLMN), receiving a number of registered user equipment (UEs) per network slice availability check and update request from an access and mobility management function (AMF) and transmitting a response to the AMF, the response indicating whether a maximum number of registered UEs or sessions for the S-NSSAI has been reached.
  • NSACF network slice admission control function
  • the NSACF of the first example wherein the operations further comprise receiving a maximum number of roaming UEs per network slice for a single network slice selection assistance information (S-NSSAI) in a visiting public land mobile network (VPLMN) and receiving a maximum number of roaming UEs per network slice for a corresponding mapped S-NSAAI in a home public land mobile network (HPLMN).
  • S-NSSAI single network slice selection assistance information
  • HPLMN home public land mobile network
  • the NSACF of the first example wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN) that is configured with a maximum number of packet data unit (PDU) sessions per network slice in local-breakout mode (LBO).
  • NSACF network slice admission control function
  • VPN public land mobile network
  • PDU packet data unit
  • the NSACF of the first example wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN) that is configured with a maximum number of packet data unit (PDU) sessions per network slice in home-routed mode.
  • NSACF network slice admission control function
  • VPN public land mobile network
  • the NSACF of the fourth example wherein the NSACF deployed by the VPLMN is configured to enforce network slice admission control (NSAC) for a single network slice selection assistance information (S-NSSAI) and a NSACF deployed by a home public land mobile network (HPLMN) is configured to enforce NSAC for a corresponding mapped S-NSSAI.
  • NSAC network slice admission control
  • S-NSSAI single network slice selection assistance information
  • HPLMN home public land mobile network
  • the NSACF of the first example wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN) and the request is received from a session management function (SMF) deployed by the VPLMN.
  • NSACF network slice admission control function
  • VPN visiting public land mobile network
  • SMF session management function
  • the NSACF of the first example wherein the quota comprises a maximum number of packet data unit (PDU) sessions per network slice in local-break out (LBO) mode.
  • PDU packet data unit
  • the NSACF of the first example wherein the quota comprises a maximum number of packet data unit (PDU) sessions per network slice in home-routed mode.
  • PDU packet data unit
  • the NSACF of the first example wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN).
  • NSACF network slice admission control function
  • VPN visiting public land mobile network
  • the NSACF of the ninth example wherein the request comprises a single network slice selection assistance information (S-NSSAI) in the VPLMN and a corresponding mapped S-NSSAI in a home public land mobile network (HPLMN).
  • S-NSSAI single network slice selection assistance information
  • HPLMN home public land mobile network
  • the NSACF of the tenth example wherein the NSACF is configured to perform network slice admission control (NSAC) for a single network slice selection assistance information (S-NSSAI) in the VPLMN based on an agreement between the VPLMN and a home public land mobile network (HPLMN).
  • NSAC network slice admission control
  • S-NSSAI single network slice selection assistance information
  • a method performed by a network slice admission control function (NSACF) of a 5G core network comprises maintaining a network slice quota for one or more network slices, wherein a network slice admission control function (NSACF) configured to enforce network slice admission control (NSAC) for both a visiting public land mobile network (VPLMN) and a home public land mobile network (HPLMN), receiving a number of registered user equipment (UEs) per network slice availability check and update request from an access and mobility management function (AMF) and transmitting a response to the AMF, the response indicating whether a maximum number of registered UEs or sessions for the S-NSSAI has been reached.
  • NSACF network slice admission control function
  • the method further comprise receiving a maximum number of roaming UEs per network slice for a single network slice selection assistance information (S-NSSAI) in a visiting public land mobile network (VPLMN) and receiving a maximum number of roaming UEs per network slice for a corresponding mapped S-NSAAI in a home public land mobile network (HPLMN).
  • S-NSSAI single network slice selection assistance information
  • HPLMN home public land mobile network
  • the method the twelfth example, wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN) that is configured with a maximum number of packet data unit (PDU) sessions per network slice in local-breakout mode (LBO).
  • NSACF network slice admission control function
  • VPN visiting public land mobile network
  • PDU packet data unit
  • the method the twelfth example, wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN) that is configured with a maximum number of packet data unit (PDU) sessions per network slice in home-routed mode.
  • NSACF network slice admission control function
  • VPN public land mobile network
  • the method the fifteenth example wherein the NSACF deployed by the VPLMN is configured to enforce network slice admission control (NSAC) for a single network slice selection assistance information (S-NSSAI) and a NSACF deployed by a home public land mobile network (HPLMN) is configured to enforce NSAC for a corresponding mapped S-NSSAI.
  • NSAC network slice admission control
  • S-NSSAI single network slice selection assistance information
  • HPLMN home public land mobile network
  • the method the twelfth example, wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN) and the request is received from a session management function (SMF) deployed by the VPLMN.
  • NSACF network slice admission control function
  • VPN visiting public land mobile network
  • SMF session management function
  • the method the twelfth example, wherein the quota comprises a maximum number of packet data unit (PDU) sessions per network slice in local-break out (LBO) mode.
  • PDU packet data unit
  • the method the twelfth example, wherein the quota comprises a maximum number of packet data unit (PDU) sessions per network slice in home-routed mode.
  • PDU packet data unit
  • the method the twelfth example, wherein the network function is a network slice admission control function (NSACF) deployed by a visiting public land mobile network (VPLMN).
  • NSACF network slice admission control function
  • VPN visiting public land mobile network
  • the method the twentieth example wherein the request comprises a single network slice selection assistance information (S-NSSAI) in the VPLMN and a corresponding mapped S-NSSAI in a home public land mobile network (HPLMN).
  • S-NSSAI single network slice selection assistance information
  • HPLMN home public land mobile network
  • the method the twenty first example, the NSACF of the tenth example, wherein the NSACF is configured to perform network slice admission control (NSAC) for a single network slice selection assistance information (S-NSSAI) in the VPLMN based on an agreement between the VPLMN and a home public land mobile network (HPLMN).
  • NSAC network slice admission control
  • S-NSSAI single network slice selection assistance information
  • a method is performed by a network slice admission control function (NSACF) of a 5G core network, the method comprising transmitting a network function registration request to a network resource function (NRF), wherein the network function registration request includes a list of single network slice selection assistance information (S-NSSAI) for which the NSACF manages admission control and receiving a response to the network function registration request from the NRF, wherein the NSACF is a consumer of Nnrf_NFManagement services.
  • S-NSSAI single network slice selection assistance information
  • the method of the twenty third example wherein the network function registration request further comprises a number of registered user equipments (UEs) supported by a first one of the S-NSSAI.
  • UEs registered user equipments
  • the method of the twenty third example wherein the network function registration request further comprises a number of protocol data unit (PDU) sessions supported by a first one of the S-NSSAI.
  • PDU protocol data unit
  • the method of the twenty third example wherein the network function registration request further comprises a service area for the NSACF.
  • the method of the twenty third example further comprising identifying that a number of registered user equipment (UEs) for a S-NSSAI crosses a threshold value, identifying one or more AMFs associated with the S-NSSAI based on the discovery response and transmitting an early admission control (EAC) flag to only the identified AMFs in response to the number of registered UEs for the S-NSSAI crossing the threshold value.
  • UEs registered user equipment
  • EAC early admission control
  • An exemplary hardware platform for implementing the exemplary embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc.
  • the exemplary embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP22171438.9A 2021-05-10 2022-05-03 Découverte de commande d'admission de tranche de réseau (nsac) et améliorations de l'itinérance Pending EP4090060A3 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163201705P 2021-05-10 2021-05-10
US17/660,234 US20220361093A1 (en) 2021-05-10 2022-04-22 Network Slice Admission Control (NSAC) Discovery and Roaming Enhancements

Publications (2)

Publication Number Publication Date
EP4090060A2 true EP4090060A2 (fr) 2022-11-16
EP4090060A3 EP4090060A3 (fr) 2022-11-23

Family

ID=81580341

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22171438.9A Pending EP4090060A3 (fr) 2021-05-10 2022-05-03 Découverte de commande d'admission de tranche de réseau (nsac) et améliorations de l'itinérance

Country Status (6)

Country Link
US (1) US20220361093A1 (fr)
EP (1) EP4090060A3 (fr)
JP (1) JP2022174023A (fr)
KR (1) KR20220152950A (fr)
CN (1) CN115334490A (fr)
BR (1) BR102022008929A2 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11979931B2 (en) * 2021-09-30 2024-05-07 Samsung Electronics Co., Ltd. Wireless network and methods to maintain MA PDU session at NSACF

Also Published As

Publication number Publication date
JP2022174023A (ja) 2022-11-22
EP4090060A3 (fr) 2022-11-23
KR20220152950A (ko) 2022-11-17
US20220361093A1 (en) 2022-11-10
BR102022008929A2 (pt) 2022-11-16
CN115334490A (zh) 2022-11-11

Similar Documents

Publication Publication Date Title
CN109314917B (zh) 网络切片选择策略更新方法、及装置
US20220394592A1 (en) Access Control at a Relay User Equipment
US20230080067A1 (en) Network Access Method, Apparatus, and System
US10716159B2 (en) Method and user equipment for connecting by means of plurality of accesses in next generation network
US11758000B2 (en) System and method for survival time delivery in 5GC
US11678253B2 (en) Traffic routing towards local area data network per application function request
EP4175336A2 (fr) Améliorations apportées à la gestion de tranches de réseau d'équipement utilisateur
US20220312517A1 (en) D2d communication method, apparatus, and system
US20230171598A1 (en) Secondary or Splice-Specific Access Control in a Wireless Communication Network
WO2022056728A1 (fr) Opérations de réseau pour recevoir un consentement d'utilisateur pour le traitement informatique en périphérie
EP4090060A2 (fr) Découverte de commande d'admission de tranche de réseau (nsac) et améliorations de l'itinérance
EP4156795A1 (fr) Rejet de tranche de réseau au niveau de tai et amf
US20240129730A1 (en) Authentication Indication for Edge Data Network Relocation
WO2022056733A1 (fr) Protection de sécurité sur consentement d'utilisateur pour le traitement informatique en périphérie
US20240137277A1 (en) Network Slice Quota Management Enhancements
US11812375B2 (en) Simultaneous network slice usage via dual connectivity
US20230239828A1 (en) Network registration method for traffic steering and device supporting the same
US20210136717A1 (en) Establishing a Multiple Access Connection
US20240107288A1 (en) Roaming for UE of a NPN
WO2023215347A1 (fr) Attribution dynamique de limites de tranche de réseau et de tranches de réseau à la demande
WO2023060182A1 (fr) Mécanisme de libération locale pour le découpage en tranches d'un réseau
JP2024505266A (ja) 第１のコアネットワーク装置の方法、第２のコアネットワーク装置の方法、および無線アクセスネットワークの方法

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

17P Request for examination filed

Effective date: 20220503

AK Designated contracting states

Kind code of ref document: A2

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

AK Designated contracting states

Kind code of ref document: A3

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/14 20090101ALN20221018BHEP

Ipc: H04W 48/18 20090101ALN20221018BHEP

Ipc: H04W 24/02 20090101ALI20221018BHEP

Ipc: H04W 8/00 20090101AFI20221018BHEP