Method for selecting non-3GPP access network in wireless communication network

Abstract

There is provided a method comprising creating a first list of available public land mobile networks (PLMNs), the PLMNs being connectable via available non-3GPP access networks using a first connection type, selecting a first PLMN from the first list of available PLMNs, creating a second list of available non-3GPP access networks, and selecting a second PLMN from the second list of available non-3GPP access networks. The second list contains all available non-3GPP access networks supporting connections to the first PLMN using the first connection type and one or more network slices non-3GPP access groups (NSNAGs) supported by each of the available non-3GPP access networks, determining a network slice associated with the NSNAG in the second list, selecting a first non-3GPP access network from a second list of available non-3GPP access networks, where the first non-3GPP access network supports a first connection type to a requested network slice in the first PLMN, where the requested network slice is a network slice associated with one or more NSNAGs in the second list, and starting a registration procedure with the first PLMN, where the NSNNGs are associated with the requested network slice in the second list. The registration procedure requests support for the requested network slice in the first PLMN.

Description

Technical Field

[0001] The subject matter disclosed herein relates generally to wireless communication networks. Background Art

[0002] Non-3GPP access networks (e.g., wireless local area networks (WLANs)) may support interfaces with mobile networks (e.g., public land mobile networks (PLMNs)) to enable wireless devices (e.g., user equipment (UE)) to connect to these mobile networks and utilize their services. When a wireless device wishes to connect to a mobile network via a non-3GPP access network, the wireless device requires a method for selecting a non-3GPP access network to use. Summary of the invention

[0003] A problem with existing methods for selecting a non-3GPP access network is that network slicing information is not taken into account.

[0004] A process for selecting a non-3GPP access network is disclosed herein. The process may be implemented by a wireless device such as a UE.

[0005] In one aspect, a method is provided, comprising: creating a first list of available public land mobile networks PLMNs that are capable of connecting via available non-3GPP access networks using a first connection type; selecting a first PLMN from the first list of available PLMNs; creating a second list of available non-3GPP access networks, the second list comprising all available non-3GPP access networks that support connection to the first PLMN using the first connection type and one or more network slice non-3GPP access groups NSNAGs supported by each of the available non-3GPP access networks; determining a network slice associated with the NSNAG 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 connection type 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 starting a registration process with the first PLMN, the registration process requesting support for the requested network slice in the first PLMN.

[0006] Creation of the first list may include discovering all available non-3GPP access networks, for each available non-3GPP access network, identifying one or more PLMNs to which the first connection type is supported, and including in the first list all PLMNs to which the first connection type is supported.

[0007] The method may also include, for each available non-3GPP access network, identifying one or more NSNAGs in each PLMN.

[0008] The determination of the network slice associated with each NSNAG may be performed using NSNAG information received within the access network discovery and selection policy ANDSP of the first PLMN or within a registration accept message received from the first PLMN.

[0009] The ANDSP of the first PLMN may be provided with an N1 signaling procedure.

[0010] The ANDSP of the first PLMN may be provided using User Equipment UE policy management procedures.

[0011] The non-3GPP access network may include a wireless access network WLAN.

[0012] The first connection type may be a 5G connection.

[0013] The determination of the network slice may include the determination of the network slice selection auxiliary information S-NSSAI.

[0014] The NSNAG information may contain one or more NSNAG identifiers and an associated S-NSSAI list for each NSNAG identifier.

[0015] The method may be executed by a UE.

[0016] In another aspect, a device configured to perform the method of the above aspect is provided, and the device may be a UE.

[0017] In yet another aspect, a wireless communication device is provided, comprising a receiver arranged to receive an access network discovery and selection policy (ANDS) from a first PLMN, the ANDSP comprising network slice group information, the network slice group information comprising 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 to select a non-3GPP access network that supports a first connection type to a requested network slice in the first PLMN. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to certain devices and methods shown in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and is not to be considered as limiting the scope thereof. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0019] Methods and apparatus for selecting a non-3GPP access network will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0020] Figure 1A A wireless communication system is shown;

[0021] Figure 1B A UE, a non-3GPP access network and a mobile network of a wireless communication system are shown;

[0022] Figure 2 A user equipment device is shown;

[0023] Figure 3 Network nodes are shown;

[0024] Figure 4 illustrates the interaction between a UE, a non-3GPP access network and a mobile network of a wireless communication system; and

[0025] Figure 5 A flow chart of a method performed within a wireless communication system is shown. DETAILED DESCRIPTION

[0026] As will be appreciated by those skilled in the art, aspects of the present disclosure may be implemented as systems, devices, methods or program products. Therefore, the arrangements described herein may be implemented in full hardware form, full software form (including firmware, resident software, microcode, etc.) or a combination of hardware and software.

[0027] For example, the disclosed methods and apparatus may be implemented as a hardware circuit comprising a custom very large scale integrated ("VLSI") circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. The disclosed methods and apparatus may also be implemented in a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code, which may be organized, for example, as an object, procedure, or function.

[0028] In addition, the method and apparatus may take the form of a program product contained in one or more computer-readable storage devices storing machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transient and / or non-transmitting. The storage device may not contain signals. In some arrangements, the storage device uses only signals for accessing the code.

[0029] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing 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.

[0030] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more conductors, 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 disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0031] Throughout the specification, references to examples or similar language of a particular method or apparatus mean that the specific features, structures, or characteristics described in conjunction with the example are included in at least one implementation of the methods and apparatus described herein. Therefore, references to features of examples of a particular method or apparatus or similar language may, but do not necessarily, all refer to the same example, but unless otherwise expressly specified, refer to "one or more but not all examples". Unless otherwise expressly stated, the terms "include", "comprise", "have" and their variations mean "including but not limited to". Unless otherwise expressly provided, a list of enumerated items does not mean that any or all items are mutually exclusive. Unless otherwise expressly provided, the terms "one" and "the" also refer to "one or more".

[0032] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, 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. As used herein, a list using the term "one or more" includes any single item in the list or a combination of items in the list. For example, 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. As used herein, a list using the term "one of" includes one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and does not include a combination of A, B, and C. As used herein, "a member selected from the group including A, B, and C" includes one and only one of A, B, or C, and does not include a combination of A, B, and C. As used herein, “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.

[0033] In addition, the features, structures, or characteristics described herein may be combined in any appropriate manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the present disclosure. However, those skilled in the relevant art will recognize that the disclosed methods and apparatus may be implemented without one or more of the specific details, or may be implemented using other methods, components, materials, etc. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid confusing aspects of the present disclosure.

[0034] The following is a description of various aspects of the disclosed methods and devices with reference to schematic flow charts and / or schematic block diagrams of methods, devices, systems, and program products. It should be understood that each block of the schematic flow charts and / or schematic block diagrams, and the combination of blocks in the schematic flow charts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in the schematic flow charts and / or schematic block diagrams.

[0035] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce a product including instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0036] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0037] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible implementation architectures, functions, and operations of devices, systems, methods, and program products. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of a code, which includes one or more executable instructions of a code for implementing (multiple) specified logical functions.

[0038] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur in the order noted in the drawings. For example, two blocks shown in succession may actually be performed substantially simultaneously, or the blocks may sometimes be performed in reverse order, depending on the functions involved. Other steps and methods may be envisioned that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the drawings shown.

[0039] The description of the elements in each figure may refer to the elements of the previous figure. The same numbers refer to the same elements in all figures.

[0040] FIG1 illustrates an embodiment of a wireless communication system 100 for selecting a non-3GPP access network. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a specific number of remote units 102 and network units 104 are shown in FIG1 , those skilled 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.

[0041] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, a modem), an aerial vehicle, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical helmet display, etc. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, the remote unit 102 may communicate directly with other remote units 102 via side link communications.

[0042] The network elements 104 may be distributed over a geographical area. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, Node-Bs, eNBs, gNBs, home Node-Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, network entities, access and mobility management functions (“AMFs”), unified data management functions (“UDMs”), unified data repositories (“UDRs”), UDM / UDRs, policy control functions (“PCFs”), radio access networks (“RANs”), network slice selection functions (“NSSFs”), operations, management, and administration (“OAs”). M"), session management function ("SMF"), user plane function ("UPF"), application function, authentication server function ("AUSF"), security anchor function ("SEAF"), trusted non-3GPP gateway function ("TNGF"), application function, service enabling architecture layer ("SEAL") function, vertical application enabling server, edge enabling server, edge configuration server, mobile edge computing platform function, mobile edge computing application, application data analysis enabling server, SEAL data delivery server, middleware entity, network slice capability management server or any other term used in the art. The network unit 104 is typically part of a radio access network and includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which can be coupled to other networks, such as the Internet and the public switched telephone network, as well as other networks. These and other elements of the radio access and core networks are not shown, but are well known to those of ordinary skill in the art.

[0043] In one implementation, the wireless communication system 100 complies with the New Radio (NR) protocol standardized in 3GPP, wherein the network unit 104 transmits on the downlink (DL) using an orthogonal frequency division multiplexing ("OFDM") modulation scheme, and the remote unit 102 transmits on the uplink (UL) using a single carrier frequency division multiple access ("SC-FDMA") scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0044] The network unit 104 can serve multiple remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0045] A non-3GPP access network (e.g., WLAN) may support an interface with a mobile network (e.g., PLMN) to enable wireless devices (e.g., UE) to connect to these mobile networks and utilize their services. For example, a WLAN access network may support an N2 interface and an N3 interface (specified in TS23.501) with a PLMN for connecting a wireless device to a 5G core (5GC) network in the PLMN via WLAN access. In addition, a WLAN access network may support an STa / SWa interface and an S2a interface (specified in TS23.401) with a PLMN for connecting a wireless device to an evolved packet core (EPC) network in the PLMN via WLAN access.

[0046] Figure 1B An example of such a WLAN access network 110 is shown. More specifically, Figure 1B A "trusted" WLAN 110 is shown connected to the EPC and 5GC in several PLMNs 120. Note that the "trusted" WLAN is connected to the EPC (e.g., the 5GC) using the STa interface and the S2a interface. Figure 1B As shown), the “untrusted” WLAN is connected to the EPC using the SWa interface and the S2a interface.

[0047] Figure 1B All network functions shown have been specified in 3GPP TS23.501, TS23.402 and TR 23.716. Specifically:

[0048] - Trusted Non-3GPP Gateway Function (TNGF) is specified in TR 23.716. It is a functional element for interfacing the 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).

[0049] - The Trusted WLAN Access Gateway (TWAG) and AAA Proxy are specified in TS23.402. They are used to interface the Trusted WLAN Access Network 110 with one or more Evolved Packet Cores (EPCs) in the PLMN 120. The TWAG provides a user plane interface (S2a), and the AAA Proxy provides a control plane interface (STa / SWa) for authentication, authorization, and accounting.

[0050] - The functional elements within 5GC (such as AMF, SMF, UPF, etc.) are specified in TS23.501, and the functional elements within EPC (such as MME, PGW, etc.)

[0051] Specified in TS23.401 and TS23.402.

[0052] When the wireless device 102 wants to register with (also referred to as "connect to") a PLMN 120 via a non-3GPP access network 110, the wireless device 102 needs a method for selecting (a) a PLMN 120 for connection via the non-3GPP access 110, (b) a core network (EPC or 5GC) in the PLMN 120 for connection, and (c) a non-3GPP access network 110 that provides connection to the selected core network in the selected PLMN 120 for connection. This method is specified in TS 23.501 of Rel-16 and Rel-17 (see clause 6.3.12).

[0053] However, this method does not take into account network slice information for selecting a non-3GPP access network 110 for connection, because it is assumed in the 3GPP specification that a non-3GPP access network 110 supporting 5G connectivity to a PLMN 120 can be used to connect to any network slice in that PLMN 120.

[0054] However, this assumption is no longer valid because in 3GPP Rel-17, it is specified that the non-3GPP access network 110 may only be able to support connections to specific network slices in the PLMN 120 (i.e., not all network slices in the PLMN 120). Therefore, if the UE 102 selects a non-3GPP access network 110 based on the method in TS 23.501 of Rel-16 and Rel-17 (see clause 6.3.12), the UE 102 may select a non-3GPP access network 110 that does not support connections to the network slice requested by the UE 102. For this reason, an updated selection method is needed that also takes into account the network slices to which the non-3GPP access network 110 can support 5G connections.

[0055] The problem of how a UE 102 selects a non-3GPP access network 110 to connect to a specific network slice in a 5G PLMN 120 is considered in the 5WWC_ph2 study item in Rel-18. In this context, solution 12 in TR 23.700-17 specifies that a trusted non-3GPP access network 110 (identified by an SSID) may advertise: a) a list of (multiple) S-NSSAIs in the PLMN 120 that can be connected via the access network 110, or b) a list of network slice access stratum groups (NSASGs) in the PLMN 120 that can be connected via the access network 110.

[0056] The present disclosure describes a method wherein:

[0057] i) the non-3GPP access network 110 advertises a list of network slice groups (referred to as a Network Slice Non-3GPP Access Group (NSNAG)), which is a different type of group from the NSAG described in b) above; and

[0058] ii) A method is defined by which the UE 102 can determine the S-NSSAI associated with the NSNAG and apply the determined S-NSSAI to select a non-3GPP access network.

[0059] Based on the above two points i) and ii), described herein is an updated selection method that can be used by UE 102, which takes into account the network slices that the non-3GPP access network 110 that UE 102 can detect can support 5G connections to it.

[0060] Figure 2 A user equipment device 200 (which may also be referred to as a wireless communication device) that can be used to implement the methods described herein is shown. The user equipment device 200 is used to implement one or more solutions described herein. The user equipment device 200 is based on one or more user equipment devices described in the embodiments of the present invention. Specifically, the user equipment device 200 and Figure 1A and 1B The user equipment device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0061] The input device 215 and the output device 220 may be combined into a single device, such as a touch screen. In some implementations, 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.

[0062] As shown, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 can communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 can operate on an unlicensed spectrum. In addition, the transceiver 225 can include multiple UE panels supporting one or more beams. In addition, the transceiver 225 can support at least one network interface 240 and / or application interface 245. (Multiple) application interface 245 can support one or more APIs. (Multiple) network interface 240 can support 3GPP reference points, such as Uu, N1, PC5, etc. As understood by those of ordinary skill in the art, other network interfaces 240 may also be supported.

[0063] The processor 205 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, 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 a 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.

[0064] Processor 205 may control user equipment device 200 to implement the user equipment device behaviors described herein. Processor 205 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0065] Memory 210 may be a computer-readable storage medium. Memory 210 may include volatile computer storage media. For example, memory 210 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 210 may include non-volatile computer storage media. For example, memory 210 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. Memory 210 may include both volatile and non-volatile computer storage media.

[0066] The memory 210 may store data related to implementing the traffic class fields described herein. The memory 210 may also store program code and related data, such as an operating system or other controller algorithms running on the device 200.

[0067] Input device 215 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. Input device 215 may be integrated with output device 220, for example, as a touch screen or similar touch-sensitive display. Input device 215 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 215 may include two or more different devices, such as a keyboard and a touch pad.

[0068] Output device 220 may be designed to output visual, auditory, and / or tactile signals. Output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, 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 a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 220 may include a wearable display that is separate from the rest of user device apparatus 200 but communicatively coupled to the rest of user device apparatus 200, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 220 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0069] Output device 220 may include one or more speakers for producing sound. For example, output device 220 may produce an audible alarm or notification (e.g., a beep or chime). Output device 220 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 220 may be integrated with input device 215. For example, input device 215 and output device 220 may form a touch screen or similar touch-sensitive display. Output device 220 may be located near input device 215.

[0070] The transceiver 225 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to send and receive messages, data, and other signals. For example, the processor 205 can selectively activate the transceiver 225 (or part thereof) at a specific time to send and receive messages.

[0071] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. One or more transmitters 230 can be used to provide uplink communication signals to the base unit of the wireless communication network. Similarly, one or more receivers 235 can be used to receive downlink communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are shown, the user equipment device 200 can have any appropriate number of transmitters 230 and receivers 235. In addition, (multiple) transmitters 230 and (multiple) receivers 235 can be any appropriate type of transmitter and receiver. The transceiver 225 may include a first transmitter / receiver pair for communicating with a mobile communication network on a licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on an unlicensed radio spectrum.

[0072] The first transmitter / receiver pair can be used to communicate with a mobile communication network on a licensed radio spectrum, while the second transmitter / receiver pair used to communicate with a mobile communication network on an unlicensed radio spectrum can be combined into a single transceiver unit, such as a single chip that performs functions for use with licensed and unlicensed radio spectrums. The first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, some of the transceivers 225, transmitters 230, and receivers 235 can be implemented as physically separated components that access shared hardware resources and / or software resources (e.g., network interface 240).

[0073] 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 multi-transceiver 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 a network interface 240 or other hardware components / circuits may be integrated into a single chip with any number of transmitters 230 and / or receivers 235. Transmitters 230 and receivers 235 may be logically configured as transceivers 225 using one or more common control signals, or may be configured as modular transmitters 230 and receivers 235 implemented in the same hardware chip or multi-chip module.

[0074] Figure 3 300. The network node 300 may be an implementation of an entity in a wireless communication network, such as one or more wireless communication networks described herein, such as the wireless communication network 100. The network node 300 may be associated with Figure 1AThe network node 300 is the same as or identical to the network unit 104. The network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320 and a transceiver 325.

[0075] The input device 315 and the output device 320 may be combined into a single device, such as a touch screen. In some implementations, 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 a processor 305, a memory 310, and a transceiver 325, and may not include an input device 315 and / or an output device 320.

[0076] As shown, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more remote units 200. In addition, the transceiver 325 can support at least one network interface 340 and / or application interface 345. (Multiple) application interface 345 can support one or more APIs. (Multiple) network interface 340 can support 3GPP reference points, such as Uu, N1, N2, and N3. As understood by those of ordinary skill in the art, other network interfaces 340 can be supported.

[0077] The processor 305 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a 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.

[0078] Memory 310 may be a computer-readable storage medium. Memory 310 may include volatile computer storage media. For example, memory 310 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 310 may include non-volatile computer storage media. For example, memory 310 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. Memory 310 may include both volatile and non-volatile computer storage media.

[0079] The memory 310 may store data related to establishing a multipath unicast link and / or mobile operation. For example, the memory 310 may store parameters, configurations, resource allocations, policies, etc., as described herein. The memory 310 may also store program code and related data, such as an operating system or other controller algorithm running on the network node 300.

[0080] Input device 315 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. Input device 315 may be integrated with output device 320, such as a touch screen or similar touch-sensitive display. Input device 315 may include a touch screen, so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 315 may include two or more different devices, such as a keyboard and a touch pad.

[0081] Output device 320 may be designed to output visual, auditory and / or tactile signals. Output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 320 may include a wearable display that is separate from the rest of network node 300 but communicatively coupled to the rest of network node 300, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 320 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0082] Output device 320 may include one or more speakers for producing sound. For example, output device 320 may produce an audible alarm or notification (e.g., a beep or chime). Output device 320 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 320 may be integrated with input device 315. For example, input device 315 and output device 320 may form a touch screen or similar touch-sensitive display. Output device 320 may be located near input device 315.

[0083] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. As described herein, one or more transmitters 330 may be used to communicate with a UE. Similarly, one or more receivers 335 may be used to communicate with a network function in a PLMN and / or RAN, as described herein. Although only one transmitter 330 and one receiver 335 are shown, the network node 300 may have any suitable number of transmitters 330 and receivers 335. In addition, the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitter and receiver.

[0084] Figure 4 An embodiment of trusted non-3GPP access selection based on slice information is shown.

[0085] The methods specified below are used in Figure 4 The exemplary deployment scenario shown in the embodiment of FIG. Figure 4 In the embodiment of the present invention, the WLAN access network 410 is considered to be a typical embodiment of a "trusted" non-3GPP access network. When the non-3GPP access network 410 supports TNGF, the non-3GPP access network 410 is considered to be trusted from the perspective of the PLMN 420, and the TNGF is connected to the PLMN 420 using a conventional N2 / N3 interface. Such a non-3GPP access network 410 is considered to support "5G connection" to the PLMN 420.

[0086] In step 0 (step 0), the UE 402 decides to register to a specific network slice in the 5G PLMN 420 via non-3GPP access. This can be decided, for example, when the UE 402 is registered only via 3GPP access and attempts to send data traffic, where the data traffic should be sent using a specific network slice via non-3GPP access and via a PDU session according to the URSP rules in the UE 402. Before the UE 402 initiates the registration process, the UE 402 needs to select (i) a 5G PLMN 420 and (ii) a non-3GPP access network 410 that provides a 5G connection to a specific network slice in the PLMN 420. The following steps specify how the UE 402 performs this selection, with an emphasis on how the UE selects a non-3GPP access network 410 that provides a 5G connection to a specific network slice in the selected PLMN 420.

[0087] It is assumed that the UE 402 may map a specific network slice included in the URSP rule (which is an S-NSSAI valid in the HPLMN) to a corresponding S-NSSAI valid in the selected PLMN 420. In other words, when the UE 402 identifies according to the URSP rule that some data traffic should be sent over a non-3GPP access and using a network slice S-NSSAI-x (valid in the HPLMN) via a PDU session, the UE 402 maps the network slice to a corresponding S-NSSAI-y (valid in the selected PLMN), and then will attempt to select a non-3GPP access network 410 that provides a 5G connection to the S-NSSAI-y in the selected PLMN 420. The UE 402 may map the S-NSSAI valid in the HPLMN to a corresponding S-NSSAI valid in the selected PLMN 420, for example, because it is provided with a configured NSSAI (as defined in TS 23.501) for the selected PLMN 420. The configured NSSAI is an existing information element in the existing 3GPP specifications, but it is applied by the UE 402 in the present disclosure for a different reason, namely, to decide which WLAN 410 to select.

[0088] In a first step (“Step 1”), the UE 402 discovers available WLANs 410 and, for each WLAN 410 , identifies: a) the PLMNs 420 and b) the network slice non-3GPP access group (NSNAG) that supports 5G connectivity in each PLMN 420 .

[0089] UE 402 identifies PLMN 420 and network slice non-3GPP access groups (NSNAGs) in each PLMN 420 by sending an ANQP request message to WLAN 410 to request "3GPP cellular network" information and receiving an ANQP response message containing the "3GPP cellular network" information, where WLAN 410 supports 5G connections to these NSNAGs.

[0090] The "3GPP Cellular Network" information in the ANQP response contains one or more of the following PLMN lists, as defined in TS24.302 Annex H: PLMN list; PLMN list with S2a connections; PLMN list with trusted 5G connections; PLMN list with trusted NAS-free 5G connections.

[0091] Since UE 402 has decided to register to 5G PLMN 420 through trusted non-3GPP access (as assumed in step 0), UE 402 only considers PLMNs 420 included in the "PLMN list with trusted 5G connection".

[0092] The “PLMN list with trusted 5G connections” is enhanced to include not only a list of PLMNs 420 to which 5G connections are supported by WLAN 410 (as currently specified), but also one or more Network Slice Non-3GPP Access Groups (NSNAGs) in each PLMN 420.

[0093] For example, UE 402 discovers the following three WLANs 410. WLAN 410 with SSID-x supports 5G connectivity to NSNAG-A and NSNAG-B in PLMN-1 and to NSNAG-C in PLMN-2. At this point, UE 402 is unaware of the network slices (S-NSSAI) associated with each NSNAG unless it has received ANDSP information, as further explained below.

[0094] SSID-x PLMN-1: NSNAG-A, NSNAG-B

[0095] PLMN-2: NSNAG-C

[0096] SSID-y PLMN-1: NSNAG-D

[0097] SSID-z PLMN-3: NSNAG-E

[0098] For privacy reasons, i.e., to avoid leaking the network slices supported by each PLMN 420, which may be sensitive information, the WLAN 410 provides the supported NSNAG identities in each PLMN 420 instead of the supported network slices (S-NSSAI) in each PLMN 420. ANQP request / response messages are exchanged between the UE 402 and the WLAN 410 before association and are therefore sent without confidentiality protection.

[0099] In the second step ("step 2"), UE 402 creates a first list of available PLMNs 420, i.e., a first list of PLMNs 420 to which 5G connections are supported by available WLAN 410. In the above example, first list of available PLMNs 420 includes: first list of available PLMNs 420 = PLMN-1, PLMN-2, PLMN-3.

[0100] The first list of available PLMNs 420 indicates 5G PLMNs 420 to which the UE 402 can connect via the available WLAN access network 410.

[0101] In a third step ("step 3"), from the first list of available PLMNs 420, UE 402 selects a first PLMN 420, such as PLMN-1. This PLMN 420 selection is performed without regard to slice information (as defined in existing 3GPP specifications). UE 402 selects the first PLMN 420, for example, based on an operator-controlled PLMN selector list configured in a USIM module.

[0102] In a fourth step ("Step 4"), UE 402 creates a second list of WLANs 410 that includes WLANs 410 that support 5G connectivity to the selected (first) PLMN 420 and the NSNAGs supported by each WLAN 410. In the above example, the second list of WLANs 410 includes two WLANs 410 and three NSNAGs in the selected (first) PLMN 420:

[0103] SSID-x: NSNAG-A, NSNAG-B in PLMN-1

[0104] SSID-y: NSNAG-D in PLMN-1

[0105] In a fifth step ("step 5"), UE 402 applies the access network discovery and selection policy (ANDSP) received from the selected (first) PLMN 420 to determine the network slices (S-NSSAI) associated with the NSNAGs in the second list of WLAN 410. ANDSP includes network slice group information, which contains a list of network slice groups (e.g., NSNAGs) applicable to non-3GPP access and one or more S-NSSAIs associated with each network slice group. Continuing with the above example, UE 402 may determine that each WLAN 410 in the second list of WLANs 410 supports the following network slices:

[0106] S-NSSAI-u and S-NSSAI-v of SSID-x in PLMN-1 (ANDSP information maps NSNAG-A to S-NSSAI-u and NSNAG-B to S-NSSAI-v)

[0107] S-NSSAI-v, S-NSSAI-w for SSID-y in PLMN-1 (ANDSP information maps NSNAG-D to S-NSSAI-v and S-NSSAI-w).

[0108] According to existing 3GPP specifications, ANDSP may include two components: (a) non-3GPP access node configuration information, which helps UE 402 select a non-3GPP access node (i.e., ePDG or N3IWF) in PLMN 420 and discover contact information (e.g., IP address or FQDN) of the non-3GPP access node in HPLMN; and (b) WLAN selection policy (WLANSP) rules that provide preferences for UE 402 to select WLAN access network 410.

[0109] According to the present disclosure, ANDSP is enhanced to also contain non-3GPP network slice group (NSNAG) information for PLMN 420, which indicates the network slice (S-NSSAI) associated with each NSNAG in the PLMN 420. In the above example, the NSNAG information in ANDSP provided by PLMN-1 may include:

[0110] NSNAG-A S-NSSAI-u

[0111] NSNAG-B S-NSSAI-v

[0112] NSNAG-C S-NSSAI-m,S-NSSAI-n

[0113] NSNAG-D S-NSSAI-v,S-NSSAI-w

[0114] NSNAG-E S-NSSAI-k

[0115] UE 402 uses the NSNAG information and the received “3GPP Cellular Network” information to determine that WLAN 410 with SSID-x supports 5G connections to S-NSSAI-u and S-NSSAI-v in PLMN1, and that WLAN 410 with SSID-y supports 5G connections to S-NSSAI-v and S-NSSAI-w in PLMN1.

[0116] The NSNAG information may be specified as an additional component in ANDSP (independent of the existing two components) or may be embedded in the existing components.

[0117] Using the existing UE policy configuration procedure applying the N1 confidentiality protection mechanism, the NSNAG information is provided to the UE 402 via the PCF in PLMN-1. Therefore, it cannot be inspected by an unauthorized third party.

[0118] The S-NSSAI value included in the NSNAG information may be an S-NSSAI in PLMN-1 corresponding to the S-NSSAI to which UE 402 subscribes in the HPLMN. In other words, the NSNAG information provided to UE 402 by the PCF in PLMN-1 may be created by considering the S-NSSAI to which UE 402 subscribes. The PCF creates the NSNAG information by using one or more of a local configuration, information received from an OAM system, and information received from a unified data repository (UDR).

[0119] If 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:

[0120] - UE 402 may use other means to determine the S-NSSAI associated with the NSNAG. For example, UE 402 may have received and stored the NSNAG information of the selected PLMN 420 during a previous registration process with that PLMN 420. For example, if UE 402 registers to the selected PLMN via 3GPP access

[0121] 420, the UE 402 may have received the NSNAG information within the configured NSSAI or another information element included in the Registration Accept message or the UE Configuration Update Command.

[0122] The above paragraph specifies one example method for providing NSNAG information to UE 402. NSNAG information may be provided to UE 402 (i) as part of an ANDSP that is sent to UE 402 using a UE Policy Configuration procedure, or (ii) provided to UE 402 along with an information element included in a Registration Accept message, such as a configured NSSAI.

[0123] If the UE 402 cannot determine the S-NSSAI associated with the NSNAG, the UE 402 selects the first WLAN 410 from the second list of WLANs 410 without considering the slice information, as defined in the next step.

[0124] It should be understood that although the selection method specified in the present disclosure is applicable to "trusted" non-3GPP access, the concept of providing NSNAG information to UE 402 and using this information to identify the S-NSSAI associated with each NSNAG is also applicable to "untrusted" non-3GPP access. In other words, UE 402 can apply NSNAG information to determine which S-NSSAIs can be supported by N3IWF (i.e., the network function supporting untrusted non-3GPP access 5G core).

[0125] In a sixth step ("step 6"), the UE 402 selects a first WLAN 410 from the list of second WLANs 410 that supports a 5G connection 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 list of second WLANs 410. In the above example, if the requested S-NSSAI = S-NSSAI-u, the UE 402 selects SSID-x. If the requested S-NSSAI = S-NSSAI-w, the UE 402 selects SSID-y. If the requested S-NSSAI = S-NSSAI-v, the UE 402 may select SSID-x or SSID-y. The selection may be based on UE 402 implementation-specific criteria, or based on a WLAN selection policy (WLANSP) rule that may have been provided to the UE 402 by the selected (first) PLMN 420, which contains preferences for WLAN 410 selection.

[0126] As described in step 0, 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 that some data traffic should be sent through a non-3GPP access and using a network slice S-NSSAI-x (valid in the HPLMN) via a PDU session according to the URSP rules, the UE 402 maps the network slice to a corresponding S-NSSAI-y (valid in the selected PLMN). The corresponding S-NSSAI-y is the requested network slice, and the UE 402 will attempt to select a non-3GPP access network 410 that provides a 5G connection to the S-NSSAI-y in the selected PLMN 420.

[0127] If the UE 402 cannot determine the S-NSSAI associated with the NSNAG (see the end of step 5), the UE 402 selects the first WLAN 410 from the second WLAN 410 list without knowing which S-NSSAIs are supported by each WLAN 410 in the second WLAN 410. In the above example, where the second WLAN list 410 contains SSID-x and SSID-y, the UE 402 may first select SSID-x and attempt to register to the requested network slice in the first PLMN 420. If this fails, for example because SSID-x does not support connection to the requested network slice, the UE 402 may select SSID-y and attempt to register to the requested network slice in the first PLMN 420 again.

[0128] In the seventh step (“Step 7”), the UE 402 initiates the “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.

[0129] Table 1 below summarizes all the above steps.

[0130]

[0131]

[0132]

[0133] Figure 5 A flowchart showing steps performed in a method 500 described herein that may be performed by a UE is shown. The UE may be, for example, the remote unit 102 of FIG. 1 or Figure 4 UE 402.

[0134] At step 510, the UE creates a first list of available Public Land Mobile Networks PLMNs, which can be connected via available non-3GPP access networks using a first connection type.

[0135] At step 520, the UE selects a first PLMN from a first list of available PLMNs.

[0136] At step 530, the UE creates a second list of available non-3GPP access networks. The second list includes all available non-3GPP access networks that support connection to the first PLMN using the first connection type and one or more network slice non-3GPP access groups NSNAG supported by each of the available non-3GPP access networks.

[0137] In step 540, the UE determines the network slice associated with the NSNAG in the second list.

[0138] At 550, 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 a first connection type 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.

[0139] In step 560, the UE starts a registration procedure with the first PLMN, which requests support for the requested network slice in the first PLMN.

[0140] Creation of the first list may include discovering all available non-3GPP access networks, for each available non-3GPP access network, identifying one or more PLMNs to which the first connection type is supported, and including in the first list all PLMNs to which the first connection type is supported.

[0141] The method may also include, for each available non-3GPP access network, identifying one or more NSNAGs in each PLMN.

[0142] The determination of the network slice associated with each NSNAG may be performed using NSNAG information received within the access network discovery and selection policy ANDSP of the first PLMN or within a registration accept message received from the first PLMN.

[0143] The ANDSP of the first PLMN may be provided with an N1 signaling procedure.

[0144] The ANDSP of the first PLMN may be provided using User Equipment UE policy management procedures.

[0145] The non-3GPP access network may include a wireless access network WLAN.

[0146] The first connection type may be a 5G connection.

[0147] The determination of the network slice may include the determination of the network slice selection auxiliary information S-NSSAI.

[0148] The NSNAG information may contain one or more NSNAG identifiers and an associated S-NSSAI list for each NSNAG identifier.

[0149] It should be understood that the UE 102 , 200 may communicate and / or connect with the WLAN 410 and / or PLMN 420 via one or more of the network elements / nodes 104 , 300 .

[0150] It should be noted that the above methods and apparatus illustrate rather than limit the present invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps other than those listed in the claims, "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of several units recited in the claims. Any reference signs in the claims shall not be construed as limiting their scope.

[0151] Furthermore, although examples have been given in the context of specific communication standards, these examples are not limitations of the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples have been given in the context of 3GPP, the principles disclosed herein may also be applied to another wireless communication system, and indeed to any communication system that uses routing rules.

[0152] The method may also be embodied in an instruction set stored on a computer readable medium, which, when loaded into a computer processor, a digital signal processor (DSP) or the like, causes the processor to perform the above method.

[0153] The described methods and apparatus may be implemented in other specific forms. The described methods and apparatus are to be considered in all respects only as illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes within the meaning and equivalent range of the claims are to be included within their scope.

Claims

1. A method comprising: creating a first list of available public land mobile networks PLMNs that are connectable via available non-3GPP access networks using a first connection type; selecting a first PLMN from said first list of available PLMNs; creating a second list of available non-3GPP access networks, the second list comprising all available non-3GPP access networks supporting connection to the first PLMN using the first connection type and one or more network slice non-3GPP access groups NSNAG supported by each of the available non-3GPP access networks; determining a network slice associated with the NSNAG 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 connection type to the 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; as well as A registration process is started with the first PLMN, the registration process requesting support for the requested network slice in the first PLMN.

2. The method of claim 1, wherein the creating of the first list comprises: Discover all available non-3GPP access networks; for each available non-3GPP access network, identifying one or more PLMNs to which said first connectivity type is supported; as well as All PLMNs to which said first connection type is supported are included in said first list.

3. The method according to claim 2, further comprising: For each available non-3GPP access network, one or more NSNAGs in each PLMN are identified.

4. A method according to any preceding claim, wherein the determining of the network slice associated with each NSNAG is performed using NSNAG information, the NSNAG information being received by: within the access network discovery and selection policy ANDSP of the first PLMN; or within a REGISTRATION ACCEPT message received from said first PLMN.

5. The method of claim 4, wherein the ANDSP of the first PLMN is provided using User Equipment (UE) policy management procedures.

6. A method according to any preceding claim, wherein the non-3GPP access network comprises a wireless access network (WLAN).

7. A method according to any preceding claim, wherein the first connection type is a 5G connection.

8. A method according to any preceding claim, wherein the determination of the network slice comprises determination of network slice selection assistance information, S-NSSAI.

9. The method according to any one of claims 4 to 8, wherein the NSNAG information contains a list of one or more NSNAG identifiers and an associated S-NSSAI for each NSNAG identifier.

10. The method according to any preceding claim, wherein the method is performed by a UE.

11. An apparatus comprising: A processor configured to: creating a first list of available public land mobile networks PLMNs that are connectable via available non-3GPP access networks using a first connection type; selecting a first PLMN from said first list of available PLMNs; creating a second list of available non-3GPP access networks, the second list comprising all available non-3GPP access networks supporting connection to the first PLMN using the first connection type and one or more network slice non-3GPP access groups NSNAG supported by each of the available non-3GPP access networks; determining a network slice associated with the NSNAG in the second list; Select a first non-3GPP access network from the second list of available non-3GPP access networks a 3GPP access network, wherein the first non-3GPP access network supports the first connection type 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; as well as A registration process is started with the first PLMN, the registration process requesting support for the requested network slice in the first PLMN.

12. The apparatus of claim 11, wherein the creating of the first list comprises: Discover all available non-3GPP access networks; for each available non-3GPP access network, identifying one or more PLMNs to which said first connectivity type is supported; as well as All PLMNs to which said first connection type is supported are included in said first list.

13. The apparatus of claim 12, wherein the processor is further configured to: For each available non-3GPP access network, one or more NSNAGs in each PLMN are identified.

14. The apparatus of any one of claims 11 to 13, wherein the determining of the network slice associated with each NSNAG is performed using NSNAG information, the NSNAG information being received by: within the access network discovery and selection policy ANDSP of the first PLMN; or within a REGISTRATION ACCEPT message received from said first PLMN.

15. The apparatus of claim 14, wherein the ANDSP of the first PLMN is provided using User Equipment (UE) Policy Management procedures.

16. The apparatus according to any one of claims 11 to 15, wherein the non-3GPP access network comprises a wireless access network (WLAN).

17. The apparatus of any one of claims 11 to 16, wherein the first connection type is a 5G connection.

18. An apparatus according to any one of claims 11 to 17, wherein the determination of the network slice comprises determination of network slice selection assistance information S-NSSAI.

19. The apparatus of any one of claims 14 to 18, wherein the NSNAG information contains a list of one or more NSNAG identifiers and an associated S-NSSAI for each NSNAG identifier.

20. The apparatus according to any one of claims 11 to 19, wherein the apparatus is a user equipment (UE).

21. A wireless communication device, comprising: A receiver is arranged to receive an access network discovery and selection policy ANDSP from a first PLMN, the ANDSP comprising network slice group information, the network slice group information comprising 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 to select a non-3GPP access network, the non-3GPP access network supporting a first connection type to the requested network slice in the first PLMN.

Images