WO2024027944A1 - Procédé de sélection d'un réseau d'accès non-3gpp dans un réseau de communication sans fil - Google Patents

Procédé de sélection d'un réseau d'accès non-3gpp dans un réseau de communication sans fil Download PDF

Info

Publication number
WO2024027944A1
WO2024027944A1 PCT/EP2022/076592 EP2022076592W WO2024027944A1 WO 2024027944 A1 WO2024027944 A1 WO 2024027944A1 EP 2022076592 W EP2022076592 W EP 2022076592W WO 2024027944 A1 WO2024027944 A1 WO 2024027944A1
Authority
WO
WIPO (PCT)
Prior art keywords
plmn
3gpp access
list
network
connectivity
Prior art date
Application number
PCT/EP2022/076592
Other languages
English (en)
Inventor
Apostolis Salkintzis
Genadi Velev
Dimitrios Karampatsis
Original Assignee
Lenovo (Singapore) Pte. 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 Lenovo (Singapore) Pte. Ltd filed Critical Lenovo (Singapore) Pte. Ltd
Publication of WO2024027944A1 publication Critical patent/WO2024027944A1/fr

Links

Classifications

    • 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

Definitions

  • the subject matter disclosed herein relates generally to wireless communication networks.
  • a non-3GPP access network may support interfaces with mobile networks (e.g., public land mobile networks, PLMNs) in order to enable wireless devices (e.g., user equipment, UE) to connect to these mobile networks and utilize their services.
  • PLMNs public land mobile networks
  • UE user equipment
  • a problem with existing methods for selecting a non-3GPP access network is that network slicing information is not considered.
  • a method comprising creating a first list of available public land mobile networks, PLMNs, connectable via available non-3GPP access networks using a first connectivity type, selecting from the first list of available PLMNs a first PLMN, creating a second list of available non-3GPP access networks, the second list containing all available non-3GPP access networks that support connectivity using the first connectivity type to the first PLMN and one or more Network Slice Non- 3GPP Access Groups, NSNAGs, supported by each of the available non-3GPP access networks, determining network slices associated with the NSNAGs in the second list, selecting a first non-3GPP access network from the second list of available non-3GPP access networks, wherein the first non-3GPP access network supports the first type of connectivity to a requested network slice in the first PLMN, wherein the requested network slice is a network slice associated with one or more NSNAGs in the second list, and beginning a registration procedure with the first PLMN, the registration procedure requesting support of
  • the creation of the first list may comprise discovering all available non-3GPP access networks, for each available non-3GPP access network identifying one or more PLMNs to which the first connectivity type is supported, and including all the PLMNs to which the first connectivity type is supported in the first list.
  • the method may further comprise for each available non-3GPP access network, identifying one or more NSNAGs in each PLMN.
  • the determination of the network slices associated with each NSNAG may be performed using NSNAG information received either: within an Access Network Discovery and Selection Policy, ANDSP, of the first PLMN or within a Registration Accept message received from the first PLMN.
  • NSNAG information received either: within an Access Network Discovery and Selection Policy, ANDSP, of the first PLMN or within a Registration Accept message received from the first PLMN.
  • the ANDSP of the first PLMN may be provided with an N1 signaling procedure.
  • the ANDSP of the first PLMN may be provided using a user equipment, UE, policy management procedure.
  • the non-3GPP access networks may comprise Wireless Access Networks, WLANs.
  • the first connectivity type may be 5G connectivity.
  • the determination of the network slices may comprise determination of Network Slice Selection Assistance Information, S-NSSAI.
  • the NSNAG information may contain one or more NSNAG identifiers and a list of associated S-NSSAIs for each NSNAG identifier.
  • the method may be performed by a UE.
  • an apparatus configured to perform the method of the aspect described above.
  • the apparatus may be a UE.
  • a wireless communication device comprising a receiver arranged to receive an Access Network Discovery and Selection Policy, ANDSP, from a first PLMN, the ANDSP comprising network slice group information that contains a list of network slice groups applicable to non-3GPP access and one or more S-NSSAIs associated with each network slice group, wherein the wireless communication device is configured to apply the network slice group information for selecting a non-3GPP access network that supports a first type of connectivity to a requested network slice in the first PLMN.
  • ANDSP Access Network Discovery and Selection Policy
  • Figure 1A illustrates a wireless communication system
  • Figure IB illustrates a UE, non-3GPP access networks and mobile networks of the wireless communication system
  • Figure 2 illustrates a user equipment apparatus
  • Figure 3 illustrates a network node
  • Figure 4 illustrates interactions between a UE, non-3GPP access networks and mobile networks of the wireless communication system
  • Figure 5 illustrates a flowchart of a method performed within the wireless communication system.
  • aspects of this disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, arrangements described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, micro-code, etc.) or a form combining software and hardware aspects.
  • the disclosed methods and apparatus may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • the disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • the disclosed methods and apparatus may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
  • the methods and apparatus may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/ or program code, referred hereafter as code.
  • the storage devices may be tangible, non-transitory, and/ or non-transmission.
  • the storage devices may not embody signals. In certain arrangements, the storage devices only employ signals for accessing code.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing the code.
  • the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.
  • references throughout this specification to an example of a particular method or apparatus, or similar language means that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the method and apparatus described herein.
  • reference to features of an example of a particular method or apparatus, or similar language may, but do not necessarily, all refer to the same example, but mean “one or more but not all examples” unless expressly specified otherwise.
  • a list with a conjunction of “and/ or” includes any single item in the list or a combination of items in the list.
  • a list of A, B and/ or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list.
  • one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one of’ includes one, and only one, of any single item in the list.
  • “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C.
  • a member selected from the group consisting of A, B, and C includes one and only one of A, B, or C, and excludes combinations of A, B, and C.”
  • a member selected from the group consisting of A, B, and C and combinations thereof includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/ act specified in the schematic flowchart diagrams and/or schematic block diagrams.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions /acts specified in the schematic flowchart diagrams and/ or schematic block diagram.
  • each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
  • Figure 1 depicts an embodiment of a wireless communication system 100 for selecting a non-3GPP access network.
  • the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.
  • the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle onboard computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like.
  • the remote units 102 include wearable devices, such as smartwatches, fitness bands, optical head-mounted displays, or the like.
  • the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art.
  • the remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.
  • the network units 104 may be distributed over a geographic region.
  • a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an Access and Mobility Management Function (“AMF”), a Unified Data Management Function (“UDM”), a Unified Data Repository (“UDR”), a UDM/UDR, a Policy Control Function (“PCF”), a Radio Access Network (“RAN”), an Network Slice Selection Function (“NSSF”), an operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), an
  • AMF Access and
  • the network units 104 are generally part of a radio access network that includes one or more controllers communicab ly coupled to one or more corresponding network units 104.
  • the radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.
  • the wireless communication system 100 is compliant with New Radio (NR) protocols standardized in 3GPP, wherein the network unit 104 transmits using an Orthogonal Frequency Division Multiplexing (“OFDM”) modulation scheme on the downlink (DL) and the remote units 102 transmit on the uplink (UL) using a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) scheme or an OFDM scheme.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols.
  • WiMAX WiMAX
  • IEEE 802.11 variants GSM
  • GPRS Global System for Mobile communications
  • UMTS Long Term Evolution
  • LTE Long Term Evolution
  • CDMA2000 Code Division Multiple Access 2000
  • Bluetooth® Zi
  • the network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • the network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/ or spatial domain.
  • a non-3GPP access network may support interfaces with mobile networks (e.g., PLMNs) in order to enable wireless devices (e.g., UEs) to connect to these mobile networks and utilize their services.
  • a WLAN access network may support the N2 interface and the N3 interface (specified in TS 23.501) with a PLMN for connecting wireless devices to the 5G core (5GC) network in this PLMN via WLAN access.
  • a WLAN access network may support the STa/SWa interfaces and the S2a interface (specified in TS 23.401) with a PLMN for connecting wireless devices to the Evolved Packet Core (EPC) network in this PLMN via WLAN access.
  • EPC Evolved Packet Core
  • Figure IB illustrates an example with such WLAN access networks 110. More specifically, Figure IB illustrates “Trusted” WLANs 110 connected to EPCs and 5GCs in several PLMNs 120. Note that “Trusted” WLANs are connected to EPC using the STa interface and the S2a interface (as shown in Figure IB), while “Untrusted” WLANs are connected to EPC using the SWa interface and the S2a interface.
  • the Trusted Non-3GPP Gateway Function is specified in TR 23.716. It is the functional element used to interface a trusted non-3GPP access network 110 with the 5G core (5GC) network in one or more PLMNs 120.
  • the TNGF provides both the control-plane interface (N2) and the user-plane interface (N3).
  • the Trusted WLAN Access Gateway (TWAG) and the AAA Proxy are specified in TS 23.402. They are used to interface a trusted WLAN access network 110 with the Evolved Packet Core (EPC) in one or more PLMNs 120.
  • the TWAG provides the user-plane interface (S2a) and the AAA Proxy provides the controlplane interface (STa/SWa) for authentication, authorization and accounting.
  • the functional elements inside the 5GC e.g. AMF, SMF, UPF, etc.
  • the functional elements inside the EPC e.g. MME, PGW, etc.
  • a wireless device 102 When a wireless device 102 wants to register to (also referred to as “connect to”) a PLMN 120 via a non-3GPP access network 110, the wireless device 102 requires a method for selecting (a) the PLMN 120 to connect to via non-3GPP access 110, (b) the core network (EPC or 5GC) in this PLMN 120 to connect to and (c) the non-3GPP access network 110 to connect to that provides connectivity to the selected core network in the selected PLMN 120.
  • a method is specified in TS 23.501 for Rel-16 and Rel- 17 (see clause 6.3.12).
  • This method does not consider network slicing information for selecting the non-3GPP access network 110 to connect to because it was assumed in 3GPP specifications that a non-3GPP access network 110 that supports 5G connectivity to a PLMN 120 could be used to connect to any network slice in this PLMN 120.
  • a trusted non-3GPP access network 110 may advertise, either: a) a list of S-NSSAI(s) in a PLMN 120, which are connectable via this access network 110, or b) a list of Network Slice Access Stratum Groups (NSASGs) in a PLMN 120, which are connectable via this access network 110.
  • NSASGs Network Slice Access Stratum Groups
  • the present disclosure describes a method in which: i) the non-3GPP access network 110 advertises a list of network slice groups (called Network Slice Non-3GPP Access Groups, NSNAGs), which are different types of groups from the NSASGs described in b) above; and ii) a method is defined with which the UE 102 can determine the S-NSSAIs associated with a NSNAG and applies the determined S-NSSAIs to select a non- 3GPP access network.
  • NSNAGs Network Slice Non-3GPP Access Groups
  • Figure 2 depicts a user equipment apparatus 200 (which may also be referred to as a wireless communication device) that may be used for implementing the methods described herein.
  • the user equipment apparatus 200 is used to implement one or more of the solutions described herein.
  • the user equipment apparatus 200 is in accordance with one or more of the user equipment apparatuses described in embodiments herein.
  • the user equipment apparatus 200 is in accordance with and/ or the same as the remote unit/UE 102 of Figures 1A and IB.
  • the user equipment apparatus 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.
  • the input device 215 and the output device 220 may be combined into a single device, such as a touchscreen.
  • the user equipment apparatus 200 does not include any input device 215 and/ or output device 220.
  • the user equipment apparatus 200 may include one or more of: the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and/ or the output device 220.
  • the transceiver 225 includes at least one transmitter 230 and at least one receiver 235.
  • the transceiver 225 may communicate with one or more cells (or wireless coverage areas) supported by one or more base units.
  • the transceiver 225 may be operable on unlicensed spectrum.
  • the transceiver 225 may include multiple UE panels supporting one or more beams.
  • the transceiver 225 may support at least one network interface 240 and/ or application interface 245.
  • the application interface(s) 245 may support one or more APIs.
  • the network interface(s) 240 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 240 may be supported, as understood by one of ordinary skill in the art.
  • the processor 205 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations.
  • the processor 205 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller.
  • the processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein.
  • the processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225.
  • the processor 205 may control the user equipment apparatus 200 to implement the user equipment apparatus behaviors described herein.
  • the processor 205 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
  • OS application-domain and operating system
  • baseband radio processor also known as “
  • the memory 210 may be a computer readable storage medium.
  • the memory 210 may include volatile computer storage media.
  • the memory 210 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”).
  • the memory 210 may include non-volatile computer storage media.
  • the memory 210 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 210 may include both volatile and non-volatile computer storage media.
  • the memory 210 may store data related to implement a traffic category field as described herein.
  • the memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on the apparatus 200.
  • the input device 215 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 215 may be integrated with the output device 220, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 215 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen.
  • the input device 215 may include two or more different devices, such as a keyboard and a touch panel.
  • the output device 220 may be designed to output visual, audible, and/ or haptic signals.
  • the output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 220 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light- Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • LCD Liquid Crystal Display
  • LED Light- Emitting Diode
  • OLED Organic LED
  • the output device 220 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 200, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 220 may include one or more speakers for producing sound.
  • the output device 220 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 220 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 220 may be integrated with the input device 215.
  • the input device 215 and output device 220 may form a touchscreen or similar touch-sensitive display.
  • the output device 220 may be located near the input device 215.
  • the transceiver 225 communicates with one or more network functions of a mobile communication network via one or more access networks.
  • the transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals and also to receive messages, data, and other signals.
  • the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times in order to send and receive messages.
  • the transceiver 225 includes at least one transmitter 230 and at least one receiver 235.
  • the one or more transmitters 230 may be used to provide uplink communication signals to a base unit of a wireless communications network.
  • the one or more receivers 235 may be used to receive downlink communication signals from the base unit.
  • the user equipment apparatus 200 may have any suitable number of transmitters 230 and receivers 235.
  • the trans mi tter(s) 230 and the receiver(s) 235 may be any suitable type of transmitters and receivers.
  • the transceiver 225 may include a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/ receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
  • the first transmitter/ receiver pair may be used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/ receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum.
  • the first transmitter /receiver pair and the second transmitter/receiver pair may share one or more hardware components.
  • certain transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access a shared hardware resource and/ or software resource, such as for example, the network interface 240.
  • One or more transmitters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a single hardware component, such as a multitransceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component.
  • One or more transmitters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a multi-chip module.
  • Other components such as the network interface 240 or other hardware components/ circuits may be integrated with any number of transmitters 230 and/ or receivers 235 into a single chip.
  • the transmitters 230 and receivers 235 may be logically configured as a transceiver 225 that uses one more common control signals or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or in a multi-chip module.
  • Figure 3 depicts further details of the network node 300 that may be used for implementing the methods described herein.
  • the network node 300 may be one implementation of an entity in the wireless communications network, e.g. in one or more of the wireless communications networks described herein, e.g. the wireless communication network 100.
  • the network node 300 may be the same as or in accordance with the network unit 104 of Figure 1A.
  • the network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.
  • the input device 315 and the output device 320 may be combined into a single device, such as a touchscreen.
  • the network node 300 does not include any input device 315 and/ or output device 320.
  • the network node 300 may include one or more of: the processor 305, the memory 310, and the transceiver 325, and may not include the input device 315 and/ or the output device 320.
  • the transceiver 325 includes at least one transmitter 330 and at least one receiver 335.
  • the transceiver 325 communicates with one or more remote units 200.
  • the transceiver 325 may support at least one network interface 340 and/ or application interface 345.
  • the application interface(s) 345 may support one or more APIs.
  • the network interface(s) 340 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 340 may be supported, as understood by one of ordinary skill in the art.
  • the processor 305 may include any known controller capable of executing computer-readable instructions and/ or capable of performing logical operations.
  • the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller.
  • the processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein.
  • the processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.
  • the memory 310 may be a computer readable storage medium.
  • the memory 310 may include volatile computer storage media.
  • the memory 310 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”).
  • the memory 310 may include non-volatile computer storage media.
  • the memory 310 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 310 may include both volatile and non-volatile computer storage media.
  • the memory 310 may store data related to establishing a multipath unicast link and/ or mobile operation.
  • the memory 310 may store parameters, configurations, resource assignments, policies, and the like, as described herein.
  • the memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network node 300.
  • the input device 315 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 315 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen.
  • the input device 315 may include two or more different devices, such as a keyboard and a touch panel.
  • the output device 320 may be designed to output visual, audible, and/ or haptic signals.
  • the output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the output device 320 may include a wearable display separate from, but communicatively coupled to, the rest of the network node 300, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 320 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 320 may include one or more speakers for producing sound.
  • the output device 320 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 320 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 320 may be integrated with the input device 315.
  • the input device 315 and output device 320 may form a touchscreen or similar touch-sensitive display.
  • the output device 320 may be located near the input device 315.
  • the transceiver 325 includes at least one transmitter 330 and at least one receiver 335.
  • the one or more transmitters 330 may be used to communicate with a UE, as described herein.
  • the one or more receivers 335 may be used to communicate with network functions in the PLMN and/ or RAN, as described herein.
  • the network node 300 may have any suitable number of transmitters 330 and receivers 335.
  • the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitters and receivers.
  • Figure 4 illustrates an embodiment for Trusted Non-3GPP Access Selection based on Slicing Information.
  • WLAN access networks 410 are considered as a typical embodiment of “trusted” non-3GPP access networks.
  • a non-3GPP access network 410 is considered “trusted” from a PLMN 420 point of view, when this access network supports a TNGF, which connects to the PLMN 420 using the regular N2/N3 interfaces.
  • Such a non-3GPP access network 410 is said to support “5G connectivity” to the PLMN 420.
  • a zeroth step (“step 0”), the UE 402 decides to register to a particular network slice in a 5G PLMN 420 over non-3GPP access. This may be decided e.g., when the UE 402 is registered only over 3GPP access and attempts to send data traffic which, according to the URSP rules in the UE 402, should be sent over non-3GPP access and via a PDU Session using the particular network slice.
  • the UE 402 needs to select a 5G PLMN 420 and 0) a non- 3GPP access network 410 that provides 5G connectivity to the particular network slice in this PLMN 420.
  • the following steps specify how the UE 402 carries out this selection with emphasis on how the UE selects a non-3GPP access network 410 that provides 5G connectivity to a particular network slice in the selected PLMN 420.
  • the UE 402 can map the particular network slice included in the URSP rules, which is an S-NSSAI valid in the HPLMN, to a corresponding S-NSSAI, which is valid in the selected PLMN 420.
  • the UE 402 when the UE 402 identifies, according to the URSP rules, that some data traffic should be sent over non-3GPP access and via a PDU Session using the network slice S-NSSAI-x (valid in HPLMN), the UE 402 would map this network slice to a corresponding S-NSSAI -y (valid in the selected PLMN) and then would attempt to select a non-3GPP access network 410 that provides 5G connectivity to S-NSSAI-y in the selected PLMN 420.
  • the UE 402 can map S-NSSAIs valid in the HPLMN to corresponding S-NSSAIs valid in the selected PLMN 420 e.g., because it is provisioned with a Configured NSSAI for the selected PLMN 420 (as defined in TS 23.501).
  • the Configured NSSAI is an existing information element in existing 3GPP specifications, but it is applied in this disclosure by a UE 402 for a different reason, i.e., for deciding which WLAN 410 to select.
  • a first step (“step 1”) the UE 402 discovers the available WLANs 410 and, for each WLAN 410, it identifies: a) the PLMNs 420 and b) the Network Slice Non-3GPP Access Groups (NSNAGs) in each PLMN 420, to which 5G connectivity is supported.
  • the UE 402 identifies the PLMNs 420 and the network slice non-3GPP access groups (NSNAGs) in each PLMN 420, to which 5G connectivity is supported by a WLAN 410, by sending an ANQP request message to the WLAN 410 requesting “3GPP Cellular Network” information and receiving an ANQP response message containing “3GPP Cellular Network” information.
  • the “3GPP Cellular Network” information in the ANQP response contains one or more of the following PLMN lists, as defined in TS 24.302, Annex H: PLMN List;
  • PLMN List with S2a connectivity PLMN List with trusted 5G connectivity
  • PLMN List with trusted 5G connectivity-without-NAS PLMN List with trusted 5G connectivity-without-NAS.
  • the UE 402 considers only the PLMNs 420 included in the “PLMN List with trusted 5G connectivity” because the UE 402 has decided to register to a 5G PLMN 420 over trusted non-3GPP access (as assumed in step 0).
  • the “PLMN List with trusted 5G connectivity” is enhanced to contain, not only a list of PLMNs 420 to which 5G connectivity is supported by a WLAN 410 (as presented specified), but also one or more network slice non-3GPP access groups (NSNAGs) in each PLMN 420.
  • NNAGs network slice non-3GPP access groups
  • the UE 402 discovers the following three WLANs 410.
  • the WLAN 410 with SSID-x supports 5G connectivity to the NSNAG-A and NSNAG-B in PLMN- 1 and to NSNAG-C in PLMN-2.
  • the UE 402 does not know the network slices (S-NSSAIs) associated with each NSNAG, unless it has received ANDSP information, as further explained below.
  • PLMN-2 NSNAG-C
  • the WLANs 410 provide the supported NSNAG identities in each PLMN 420, instead of the supported network slices (S-NSSAIs) in each PLMN 420, for privacy reasons, i.e., to avoid disclosing the network slices supported by each PLMN 420, which can be sensitive information.
  • the ANQP request/ response messages are exchanged between the UE 402 and the WLAN 410 prior to association and, therefore, are transmitted without confidentiality protection.
  • Step 2 the UE 402 creates a first list of available PLMNs 420, i.e., of PLMNs 420 to which 5G connectivity is supported by the available WLANs 410.
  • the first list of available PLMNs 420 indicates the 5G PLMNs 420 to which the UE 402 can connect via the available WLAN access networks 410.
  • Step 3 from the first list of available PLMNs 420, the UE 402 selects a first PLMN 420, e.g., PLMN-1.
  • This PLMN 420 selection is performed without considering slicing information (as defined in existing 3GPP specifications).
  • the UE 402 selects the first PLMN 420 e.g., based on the Operator Controlled PLMN Selector list configured in the USIM module.
  • a fourth step (“Step 4”), the UE 402 creates a second list of WLANs 410 that contains the WLANs 410 which support 5G connectivity to the selected (first) PLMN 420 and the NSNAGs supported by each WLAN 410.
  • the second list of WLANs 410 includes two WLANs 410 and three NSNAGs in the selected (first) PLMN 420:
  • Step 5 the UE 402 applies the Access Network Discovery & Selection Policy (ANDSP) received from the selected (first) PLMN 420 to determine the network slices (S-NSSAIs) associated with the NSNAGs in the second list of WLANs 410.
  • the ANDSP comprises network slice group information that contains a list of network slice groups applicable to non-3GPP access (e.g. NSNAGs) and one or more S- NSSAIs associated with each network slice group.
  • the UE 402 may determine that each WLAN 410 in the second list of WLANs 410 supports the following network slices:
  • the ANDSP may contain two components: (a) Non-3GPP access node configuration information, that assists the UE 402 in selecting a non-3GPP access node (i.e., ePDG or N3IWF) in a PLMN 420 and discovering contact information (e.g., IP addresses or FQDNs) for non-3GPP access nodes in the HPLMN, and (b) WLAN Selection Policy (WLANSP) rules that provide preferences for the UE 402 to select a WLAN access network 410.
  • a non-3GPP access node configuration information that assists the UE 402 in selecting a non-3GPP access node (i.e., ePDG or N3IWF) in a PLMN 420 and discovering contact information (e.g., IP addresses or FQDNs) for non-3GPP access nodes in the HPLMN
  • WLANSP WLAN Selection Policy
  • the ANDSP is enhanced to contain also Non-3GPP Network Slice Group (NSNAG) information for a PLMN 420, which indicates the network slices (S-NSSAIs) associated with each NSNAG in this PLMN 420.
  • NSNAG information in the ANDSP provided by PLMN-1 may contain:
  • the UE 402 determines that the WLAN 410 with SSID-x supports 5G connectivity to S-NSSAI-u and S-NSSAI-v in PLMN1, and the WLAN 410 with SSID-y supports 5G connectivity to S-NSSAI-v and S-NSSAI-w in PLMNL [0090]
  • the NSNAG information may be specified as an addition component in the ANDSP (independent from the existing two components) or may be embedded in an existing component.
  • the NSNAG information is provided to the UE 402 via a PCF in PLMN-1 using the existing UE policy configuration procedure, which applies the N1 confidentiality protection mechanisms. Thus, it cannot be inspected by unauthorized third parties.
  • the S-NSSAI values included in the NSNAG information may be S-NSSAIs in PLMN-1, which correspond to the UE's 402 subscribed S-NSSAIs in HPLMN.
  • the NSNAG information provided to UE 402 by a PCF in PLMN-1 may be created by considering the UE's 402 subscribed S-NSSAIs.
  • the PCF creates the NSNAG information by using one or more of: local configuration, information received from the OAM system, information received from the Unified Data Repository (UDR).
  • UDR Unified Data Repository
  • the UE 402 has not received NSNAG information from the selected (first) PLMN 420, i.e., the UE 402 has not received ANDSP from the selected (first) PLMN 420 or the UE 402 has received ANDSP from the selected (first) PLMN 420, but it does not contain NSNAG information, then:
  • the UE 402 may be able to determine the S-NSSAIs associated with a NSNAG using other means. For example, the UE 402 may have received and stored the NSNAG information for the selected PLMN 420 during a prior registration procedure with this PLMN 420. If, for instance, the UE 402 is registered to the selected PLMN 420 via 3GPP access, the UE 402 may have received the NSNAG information within the Configured NSSAI or another information element included in the Registration Accept message or UE Configuration Update Command.
  • the immediately above paragraph specifies one example method for providing the NSNAG information to the UE 402.
  • the NSNAG information may be provided to UE 402 either (i) as part of ANDSP, which is sent to UE 402 using the UE policy configuration procedure, or (ii) with an information element included in the Registration Accept message, such as the Configured NSSAI.
  • the UE 402 If the UE 402 is unable to determine the S-NSSAIs associated with a NSNAG, then the UE 402 selects a first WLAN 410 from the second list of WLANs 410 without considering slicing information, as defined in the next step.
  • the selection method specified in this disclosure is applicable to “trusted” non-3GPP accesses
  • the concept of providing the UE 402 with NSNAG information and using this information to identify the S-NSSAIs associated with each NSNAG is also applicable to “untrusted” non-3GPP accesses.
  • the UE 402 can apply the NSNAG information to determine which S- NSSAIs can be supported by an N3IWF (i.e., the network function that supports untrusted non-3GPP access to 5G core).
  • a sixth step (“Step 6”), the UE 402 selects a first WLAN 410 from the second list of WLANs 410 that supports 5G connectivity to a requested network slice in the first PLMN 420, wherein the requested network slice is an S-NSSAI associated with one or more NSNAGs in the second list of WLANs 410.
  • the UE 402 can select either SSID-x or SSID-y. This selection can be based on UE 402 implementationspecific criteria, or on the WLAN Selection Policy (WLANSP) rules that may have been provided to UE 402 by the selected (first) PLMN 420, which contain preferences for WLAN 410 selection.
  • WLANSP WLAN Selection Policy
  • the requested network slice may be determined by the UE 402 using the URSP rules in the UE 402. For example, when the UE 402 identifies, according to the URSP rules, that some data traffic should be sent over non-3GPP access and via a PDU Session using the network slice S-NSSAI-x (valid in HPLMN), the UE 402 would map this network slice to a corresponding S-NSSAI -y (valid in the selected PLMN). This corresponding S-NSSAI -y is the requested network slice, and the UE 402 would attempt to selects a non-3GPP access network 410 that provides 5G connectivity to S-NSSAI-y in the selected PLMN 420.
  • the UE 402 selects a first WLAN 410 from the second list of WLANs 410 without knowing which S-NSSAIs are supported by each WLAN 410 in the second list of WLANs 410.
  • the UE 402 may first select the SSID-x and attempt to register to the requested network slice in the first PLMN 420. If this fails, e.g., because the SSID-x does not support connectivity to the requested network slice, the UE 402 may select SSID-y and attempt again to register to the requested network slice in the first PLMN 420.
  • Step 7 the UE 402 initiates a “5G registration via trusted non-3GPP access” procedure (currently defined in TS 23.502) to register to the requested network slice in the selected (first) PLMN 420 via the selected (first) WLAN 410.
  • a “5G registration via trusted non-3GPP access” procedure (currently defined in TS 23.502) to register to the requested network slice in the selected (first) PLMN 420 via the selected (first) WLAN 410.
  • Figure 5 illustrates a flowchart showing steps performed in a method 500 performable by a UE as described herein.
  • the UE may be, for example, the remote unit 102 of Figure 1 or the UE 402 of Figure 4.
  • the UE creates a first list of available public land mobile networks, PLMNs, connectable via available non-3GPP access networks using a first connectivity type.
  • the UE selects from the first list of available PLMNs a first PLMN.
  • the UE creates a second list of available non-3GPP access networks.
  • the second list contains all available non-3GPP access networks that support connectivity using the first connectivity type to the first PLMN and one or more Network Slice Non-3GPP Access Groups, NSNAGs, supported by each of the available non-3GPP access networks.
  • the UE determines network slices associated with the NSNAGs in the second list.
  • the UE selects a first non-3GPP access network from the second list of available non-3GPP access networks.
  • the first non-3GPP access network supports the first type of connectivity to a requested network slice in the first PLMN.
  • the requested network slice is a network slice associated with one or more NSNAGs in the second list.
  • the UE begins a registration procedure with the first PLMN, the registration procedure requesting support of the requested network slice in the first PLMN.
  • the creation of the first list may comprise discovering all available non-3GPP access networks, for each available non-3GPP access network identifying one or more PLMNs to which the first connectivity type is supported, and including all the PLMNs to which the first connectivity type is supported in the first list.
  • the method may further comprise for each available non-3GPP access network, identifying one or more NSNAGs in each PLMN.
  • the determination of the network slices associated with each NSNAG may be performed using NSNAG information received either: within an Access Network Discovery and Selection Policy, ANDSP, of the first PLMN or within a Registration Accept message received from the first PLMN.
  • NSNAG information received either: within an Access Network Discovery and Selection Policy, ANDSP, of the first PLMN or within a Registration Accept message received from the first PLMN.
  • the ANDSP of the first PLMN may be provided with an N1 signaling procedure.
  • the ANDSP of the first PLMN may be provided using a user equipment, UE, policy management procedure.
  • the non-3GPP access networks may comprise Wireless Access Networks, WEANs.
  • the first connectivity type may be 5G connectivity.
  • the determination of the network slices may comprise determination of Network Slice Selection Assistance Information, S-NSSAI.
  • the NSNAG information may contain one or more NSNAG identifiers and a list of associated S-NSSAIs for each NSNAG identifier.
  • the UEs 102, 200 described above may communicate with and/ or connect to the above-described WEANs 410 and/ or PLMNs 420 via one or more of the above-described network units/nodes 104, 300.
  • the method may also be embodied in a set of instructions, stored on a computer readable medium, which when loaded into a computer processor, Digital Signal Processor (DSP) or similar, causes the processor to carry out the hereinbefore described methods.
  • DSP Digital Signal Processor

Landscapes

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

Abstract

L'invention concerne un procédé consistant à : créer une première liste de réseaux mobiles terrestres publics (PLMN) disponibles, pouvant être connectés par le biais de réseaux d'accès non-3GPP disponibles à l'aide d'un premier type de connectivité ; sélectionner un premier PLMN dans la première liste de PLMN disponibles ; créer une seconde liste de réseaux d'accès non-3GPP disponibles, la seconde liste contenant tous les réseaux d'accès non-3GPP disponibles qui prennent en charge la connectivité à l'aide du premier type de connectivité au premier PLMN, ainsi qu'un ou plusieurs groupes d'accès non-3GPP de tranches de réseau (NSNAG), pris en charge par chacun des réseaux non-3GPP ; déterminer des tranches de réseau associées aux NSNAG dans la seconde liste ; sélectionner un premier réseau d'accès non-3GPP dans la seconde liste de réseaux d'accès non-3GPP disponibles, le premier réseau d'accès non-3GPP prenant en charge le premier type de connectivité à une tranche de réseau demandée dans le premier PLMN, la tranche de réseau demandée étant une tranche de réseau associée à un ou plusieurs NSNAG dans la seconde liste ; et commencer une procédure d'enregistrement avec le premier PLMN, la procédure d'enregistrement demandant la prise en charge de la tranche de réseau demandée dans le premier PLMN.
PCT/EP2022/076592 2022-08-05 2022-09-23 Procédé de sélection d'un réseau d'accès non-3gpp dans un réseau de communication sans fil WO2024027944A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20220100653 2022-08-05
GR20220100653 2022-08-05

Publications (1)

Publication Number Publication Date
WO2024027944A1 true WO2024027944A1 (fr) 2024-02-08

Family

ID=83689695

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/076592 WO2024027944A1 (fr) 2022-08-05 2022-09-23 Procédé de sélection d'un réseau d'accès non-3gpp dans un réseau de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024027944A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020098954A1 (fr) * 2018-11-16 2020-05-22 Lenovo (Singapore) Pte. Ltd. Sélection de réseau d'accès pour un ue ne prenant pas en charge un nas sur un accès non-3gpp

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020098954A1 (fr) * 2018-11-16 2020-05-22 Lenovo (Singapore) Pte. Ltd. Sélection de réseau d'accès pour un ue ne prenant pas en charge un nas sur un accès non-3gpp

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on the support for 5WWC, Phase 2 (Release 18)", no. V0.2.0, 16 April 2022 (2022-04-16), pages 1 - 71, XP052145982, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/23_series/23.700-17/23700-17-020.zip 23700-17-020_rm2.docx> [retrieved on 20220416] *
3GPP TS 23.501
APOSTOLIS SALKINTZIS ET AL: "Update of Solution 12", vol. 3GPP SA 2, no. Online; 20220817 - 20220826, 10 August 2022 (2022-08-10), XP052185136, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_152E_Electronic_2022-08/Docs/S2-2206741.zip S2-2206741_R18_5WWC_Solution 12_v3.docx> [retrieved on 20220810] *
MOTOROLA MOBILITY ET AL: "Access Network Selection for UEs not supporting NAS over non-3GPP access", vol. SA WG2, no. West Palm Beach, USA; 20181126 - 20181130, 20 November 2018 (2018-11-20), XP051563375, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/SA2/Docs/S2%2D1811836%2Ezip> [retrieved on 20181120] *

Similar Documents

Publication Publication Date Title
US20240015644A1 (en) Methods and apparatuses for reconfiguring a data connection
US20210329541A1 (en) Determining a type of network connection from an os-specific connection capability
US12010089B2 (en) EPDG selection
US11589238B2 (en) Selecting a non-3GPP access network
US20230156584A1 (en) Target network slice information for target network slices
WO2024027944A1 (fr) Procédé de sélection d&#39;un réseau d&#39;accès non-3gpp dans un réseau de communication sans fil
WO2024032915A1 (fr) Connexion à un réseau d&#39;accès wlan à l&#39;aide d&#39;une authentification basée sur 3gpp
WO2024088598A1 (fr) Mappage réseau de sections de règles dans un réseau de communication sans fil
US20230300729A1 (en) User equipment radio capabilities
WO2024088568A1 (fr) Gestion de politiques d&#39;équipement utilisateur pour réseaux non publics autonomes
US20240187863A1 (en) Policies related to non-public networks
WO2024068024A1 (fr) Identification de nœud à l&#39;aide d&#39;une liaison latérale dans un réseau de communication sans fil
WO2024088554A1 (fr) Remplacement de tranches de réseau dans un réseau de communication sans fil
WO2024088595A1 (fr) Mobilité entre des réseaux de communication sans fil
WO2024088586A1 (fr) Demandes de sections de politiques dans un réseau de communication sans fil
WO2024037727A1 (fr) Procédés et appareils permettant de fournir des informations de consentement d&#39;utilisateur pour des services de collecte de données dans un réseau de communication sans fil
WO2023237220A1 (fr) Gestion de politique dans un réseau de communication sans fil
WO2024088592A1 (fr) Établissement d&#39;une connexion de données à accès multiples dans un système de communication sans fil
WO2023165721A1 (fr) Règles de politique de sélection d&#39;itinéraire pour réseaux visités
WO2023165720A1 (fr) Limitation de règles de politique de sélection d&#39;itinéraire à certains réseaux
WO2024088597A1 (fr) Fourniture de sections de politique pour de multiples réseaux de communication sans fil
WO2024088596A1 (fr) Mobilité dans un réseau de communication sans fil
WO2024088552A1 (fr) Amélioration des performances de fonction de plan utilisateur dans un réseau de communication sans fil
WO2024022596A1 (fr) Procédés et appareils de fourniture de services de périphérie lors de déploiements fédérés de réseaux de communication sans fil
WO2024032913A1 (fr) Gestion de politique d&#39;équipement utilisateur au moment de l&#39;enregistrement dans un réseau de communication sans fil

Legal Events

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

Ref document number: 22786947

Country of ref document: EP

Kind code of ref document: A1