Network selection supporting user equipment simultaneous multi-access registration

Abstract

Network selection is provided to support simultaneous multi-access registration from user equipment. A method for network selection to support simultaneous multiple access registration may include receiving capability information of a user equipment from the user equipment via a network entity. The capability information may include an indication of dual access registration capability of the user equipment to multiple mobile networks. The method may also include determining at least one geographic location corresponding to each of the plurality of mobile networks and generating a routing policy for the at least one geographic location. The routing policy may include registered mobile network specific data for a network slice or application. The method may also include sending the generated routing policy with the routing descriptor information to the user equipment.

Description

Technical Field

[0001] Some example embodiments may generally relate to mobile or wireless telecommunications technologies and systems, such as Long Term Evolution (LTE) or 5G New Radio (NR) access technologies, or technologies beyond 5G, or other communication systems. For example, some example embodiments may relate to network selection that supports simultaneous multiple access registrations for user equipment. Background Technology

[0002] Examples of mobile or wireless telecommunications technologies and systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (E-UTRAN) for Long Term Evolution (LTE), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, 5G or New Radio (NR) access technologies, and / or 6G radio access technologies. 5G and 6G wireless systems refer to Next Generation (NG) radio systems and network architectures. 5G and 6G network technologies are primarily based on New Radio (NR) technology, but 5G (or NG) networks can also be built on E-UTRAN radio. NR is estimated to provide bit rates of 10-20 Gbit / s or higher and can support at least Enhanced Mobile Broadband (eMBB) and Ultra-Reliable Low Latency Communication (URLLC) as well as Massive Machine-Type Communication (mMTC). NR is expected to provide extreme broadband and ultra-robust, low-latency connectivity, as well as massive networking to support the Internet of Things (IoT). Summary of the Invention

[0003] Various example embodiments may provide an apparatus including at least one processor and at least one memory storing instructions. When executed by the at least one processor, the stored instructions cause the apparatus to receive capability information of a user equipment (UE) from a UE at least via a network entity. The capability information may include indications of the UE's dual access registration capabilities with a plurality of mobile networks. The apparatus may also be configured to determine at least one geographic location corresponding to each of the plurality of mobile networks and generate a routing policy for the at least one geographic location. The routing policy may include registered mobile network-specific data for network slicing or applications. The apparatus may also be configured to transmit the generated routing policy with routing descriptor (RSD) information to the UE.

[0004] Some example embodiments may provide an apparatus including at least one processor and at least one memory storing instructions. When executed by the at least one processor, the stored instructions cause the apparatus to transmit, at least to a first network entity, a registration request for a mobile network containing capability information of the apparatus (e.g., a user equipment, user device). The capability information may include indications of the apparatus's access registration capabilities to multiple mobile networks. The apparatus may also be configured to receive and store a routing policy with RSD information from a second network entity. The routing policy may include mobile network-specific data for network slicing or application registration. The apparatus may also be configured to detect application-specific data services and establish packet data unit sessions for the application-specific data services using the routing policy and the RSD information. Attached Figure Description

[0005] To correctly understand the example embodiments, please refer to the accompanying drawings, as follows: Figure 1 Examples of flowcharts for one or more processes are shown according to various exemplary embodiments; Figure 2 Examples of signal diagrams are shown according to some exemplary embodiments; Figure 3 A flowchart of the method is shown according to various example embodiments; Figure 4 An example flowchart of another method is shown according to certain example embodiments; and Figure 5 A set of apparatuses is shown according to various example embodiments. Detailed Implementation

[0006] Those skilled in the art will readily understand that components of certain example embodiments generally described and illustrated herein can be arranged and designed in a variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and non-transitory computer program products for supporting network selection for simultaneous multiple access registrations of user equipment (UE). Although the devices discussed and illustrated below refer to 6G / 5G or next-generation Node B (gNB) devices and UE devices, this disclosure is not limited to gNBs and UEs only.

[0007] It will be readily understood that the components of certain example embodiments generally described herein and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Different reference numerals from the various drawings may be used in the description without order to refer to the same elements to describe their features or functions. If desired, the different functions or processes discussed herein may be performed in different orders and / or concurrently with each other. Furthermore, one or more of the described functions or processes may be optional or may be combined, if desired. Therefore, the following description should be considered as an illustration of the principles and teachings of certain example embodiments, and not as a limitation thereof.

[0008] It should be understood that although the terms "first," "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the various example embodiments.

[0009] In 5G / NR technology, Access Service Bootstrapping, Handover, and Offloading (ATSSS) can be defined by the 3rd Generation Partnership Project (3GPP) specifications. ATSSS provides the ability to bootstrap, handover, offload, and replicate services between different network accesses. For this purpose, one or more bootstrapping modes (SMs) for a given service data flow are associated with a Packet Data Unit (PDU) session established between the UE and a network entity (e.g., User Plane Function (UPF)). The UE can manage ATSSS rules, which contain service bootstrapping information for access services (e.g., 5-tuple Internet Protocol (IP) flows), and can handle uplink service bootstrapping.

[0010] The upper-layer ATSSS of UE services can involve data sessions across two 3GPP access links, where a single subscription to one or more Public Land Mobile Networks (PLMNs) and / or Non-Terrestrial Networks (NTNs) can be assumed. In a PLMN plus PLMN / NPN scenario, these two networks can be managed by the same operator or by different operators operating under the same agreement. For a two-network scenario, simultaneous connectivity via dual 3GPP access can assume that the UE supports appropriate radio capabilities (e.g., dual radios).

[0011] One issue with certain 3GPP technologies is that simultaneous connections via more than one (dual) NR access may not be supported. Simultaneous connections via LTE and NR access may already be supported. Dual NR registration can occur in a single PLMN, two different PLMNs (which can be two different Visited PLMNs (VPLMNs)), and a combination of a PLMN and a Standalone Non-Public Network (SNPN). Once the UE has performed its first registration with the serving PLMN, the UE can then decide whether to perform a second registration and on which PLMN. The UE can select the same serving PLMN from which the first registration was performed for the second or subsequent registrations. The UE can decide which PLMN to select based on PLMN selection information provided by the Home PLMN (HPLMN).

[0012] The same network slice, service, and / or application can be made available through both the first and second NR registrations. The first and second registrations can be performed on the same PLMN or different PLMNs, or a combination of PLMN and NPN. The first and second registrations can be performed using the same RAT (e.g., NR Terrestrial Network (TN)) or different RATs (one using NR TN registration and the other using NR NTN registration). After registration, when the UE detects an application service, the UE can apply UE Routing Policy (URSP) rules to determine how to route the application service, such as whether to use an existing PDU session or establish a new PDU session.

[0013] One issue with certain 3GPP technologies is the lack of a defined mechanism for a UE registering to two NR access points (e.g., the same or different PLMNs) to determine which NR access point to use to establish a new PDU session for a detected application. As a real-world example, a UE can move to a country X and register to both VPLMN1 (NR) and VPLMN2 (NR). If a PDU session needs to be established, the UE may require a mobile broadband (MBB) slice (or application), and both VPLMNs may be able to provide MBB slices (or applications). However, VPLMN1 may be less expensive than the HPLMN in terms of data roaming, thus VPLMN1 may be preferred. As a similar real-world example, a UE can move to a country Y and register to both VPLMN3 (NR) and VPLMN4 (satellite). If a PDU session needs to be established, the UE may require a broadband slice (or application), and both VPLMNs may be able to provide broadband slices (or applications). However, VPLMN4 may be more expensive due to satellite connectivity and / or cause undesirable latency. Therefore, VPLMN3 may be preferred.

[0014] Another issue with certain 3GPP technologies may be that when a UE has performed multiple 3GPP (NR) access registrations to the same PLMN, the UE may register to different RAT types, such as registration via NR TN and another registration via NR NTN.

[0015] Various example implementations can provide technical advantages to implement one or more procedures to allow the UE to determine which access to use to establish a PDU session for routing application services. Some example implementations can provide a preference priority for the UE to be notified to perform multiple 3GPP (NR) access registrations.

[0016] Some example embodiments may refer to PLMN, HPLMN, and VPLMN. However, example embodiments are not limited to PLMN only, and are equally applicable to SNPN as well as PLMN, HPLMN, and VPLMN, etc.

[0017] Some example embodiments may implement one or more procedures to allow the UE to determine which NR access to use to establish a PDU session for routing application services, for multiple 3GPP (NR) access registrations. Multiple 3GPP (NR) access registrations can be provided by the UE receiving a UE Routing Policy (URSP), which can be enhanced by including additional information as part of the RSD. The additional information may include PLMN selection information, which may include, for each geographic location, such as a country, a list of combinations of PLMN and RAT types, in preference order. The PLMN selection information, including the list of combinations of PLMN and RAT types, may be provided for application services (or per application), matching the service descriptor of the data service indicated in the URSP rule to determine how to route data services for the application. Alternatively, RAT type preferences may be provided separately from the PLMN selection information.

[0018] Multiple 3GPP (NR) accesses can perform NR access registration to a PLMN. For NR access registration, the UE communicates a registration request to the Application Management Function (AMF) of the HPLMN with the UE's dual / multi-access registration capability to multiple PLMNs or support indications for multiple accesses to the same PLMN. The AMF can then provide the support indications to the Policy Control Function (PCF) of the HPLMN. The PCF (e.g., H-PCF) can be used for the HPLMN, and the V-PCF can be used for the Visited PLMN (VPLMN). The AMF can provide the UE's dual 3GPP access registration capability to the PCF during UE policy association establishment. The PCF in the HPLMN can then transmit one or more URSP rules to the UE. One or more URSP rules can include PLMN selection information for each geographic location (e.g., country), with individual PLMN and RAT types, or a list of combinations of PLMN and RAT types in preferred order. The AMF and / or PCF can provide the same URSP rules for all countries, or can provide URSP rules specific to each country.

[0019] Various example embodiments may provide an RSD that can include multiple pieces of information known in conventional techniques. The RSD may also, or alternatively, include PLMN selection information for each geographic location (e.g., country), including a list of combinations of PLMN and RAT types in preferred order. The RSD may include a list of RAT types in preferred order. When a UE registers with a PLMN, the HPLMN may transmit one or more URSP rules that include a preferred RAT type for a specific network slice or application. This can allow a preferred RAT type to be selected for a specific service or network slice for two PLMNs with different RAT types.

[0020] Some example implementations may provide the UE to the network with an indication that the UE supports enhanced PLMN policies (e.g., URSP). When a UE registered to multiple 3GPP (NR) access protocols, it can detect application services. The UE can match the application services with service descriptors in the URSP rules. The RSD corresponding to the matched URSP rule may include PLMN selection information and / or RAT type preferences. The UE can determine whether to establish a PDU session by registering based on the preferences provided in the PLMN selection information and / or RAT type preferences.

[0021] Figure 1Examples of flowcharts for methods of implementing multiple 3GPP (NR) access registrations according to various example embodiments are shown. At 110, the UE may send a registration request to the AMF, including an indication of the UE's support for dual / multiple access registration capabilities. At 120, the AMF may provide the PCF with the UE's indication of support for dual / multiple access registrations during UE policy association establishment. At 130, the PCF may determine whether the UE supports more than one 3GPP (NR) access registration based on the UE's support indication. When the PCF determines that the UE does not support more than one 3GPP (NR) access registration, the process continues to step 140. At 140, access registration can be performed according to conventional access registration techniques.

[0022] When the PCF determines that the UE supports more than one 3GPP (NR) access registration, the process continues to step 150. At step 150, the PCF can select one or more geographic regions, such as the country where the UE is registered. The PCF can also generate URSPs that include network slices or application-specific data for the registered PLMN. PLMN selection information can include priority information for PLMN and RAT types, which can be an ordered list of preferences. At step 160, the PCF can send URSP rules to the UE with RSDs containing PLMN selector information and / or RAT type preferences. At step 170, the UE can store the received PLMN selector information and / or RAT type preferences, along with one or more URSP rules. The UE can also apply the PLMN selector information and / or RAT type preferences, along with one or more URSP rules, to select the PLMN and / or RAT for the PDU session, for example, when associated application traffic is detected.

[0023] Figure 2An example signaling diagram is shown for a configuration of implementing multiple 3GPP (NR) access registrations according to various example embodiments. This configuration may include communication between UE 201, AMF 202 of VPLMN1, AMF 203, AMF 204, PCF 205 of VPLMN2, and HPLMN (HN) 206. At 210, UE 201 can perform a non-access stratum (NAS) registration by sending a registration request to AMF 204, including an indication of UE 201's support for dual / multiple access registrations. The registration request may include a registration ID. At 220, UE 201 can complete NAS registration with HPLMN (HN) 206. At 230, AMF 204 can determine whether UE 201 supports more than one 3GPP access registration simultaneously based on the support indication or the presence of the registration ID in the registration request. Upon receiving a registration acceptance message, AMF 204 can establish a UE policy association with PCF 205. AMF204 can then send a UE policy association establishment request to PCF 205. The UE policy association establishment request may include a support indication for dual / multiple access registration from UE 201. In an example where a connection to a VPLMN is desired, AMF202 / 203 of either VPLMN1 or VPLMN2 can forward the support indication to PCF 205 (e.g., forwarded to H-PCF via V-PCF).

[0024] At 240, PCF 205 can determine the service geographic area (e.g., country) and can generate one or more URSP rules for the service geographic area (e.g., country). At 250, PCF 205 can send one or more URSP rules, and at 260, UE 201 can store one or more URSP rules received from PCF 205.

[0025] At 270, UE 201 can perform another (second) 3GPP access registration based on one or more URSP rules received from PCF 205. When UE 201, registered to multiple 3GPP (NR) accesses, detects application traffic, UE 201 can then match the application traffic with the traffic descriptor in the URSP rule. If the RSD corresponding to the matching URSP rule contains PLMN selection information and / or RAT type preference, UE 201 can determine the access and RAT type to establish a PDU session based on the preferences provided in the PLMN selection information and / or RAT type preference.

[0026] Various example implementations can provide technical advantages for implementing one or more procedures to allow a UE to determine which access to use to establish a PDU session for routing application traffic. Some example implementations can provide priority preferences that inform the UE to perform multiple 3GPP (NR) access registrations.

[0027] Figure 3 An example flowchart of a method according to certain example embodiments is shown. In the example embodiments, Figure 3 The method can be performed by devices in a 3GPP system, such as LTE, 5G-NR, or 6G. For example, in an example embodiment, Figure 3 The method can be executed by network entities, such as PCF, similar to Figure 5 The device 510 shown in the figure.

[0028] According to various example embodiments, Figure 3 The method may include, at 310, receiving UE capability information from the UE via a network entity (e.g., AMF). The capability information may include indications of the UE's dual access registration capabilities with multiple mobile networks. At 320, the method may further include determining at least one geographic area corresponding to each of the multiple mobile networks and generating a routing policy for the at least one geographic area. The routing policy may include network slices or applied registered mobile network-specific data. At 330, the method may further include sending the generated routing policy with routing descriptor information to the UE.

[0029] Some example embodiments may provide routing descriptor information including selection information, which includes a list of combinations of public land mobile networks and radio access technology (RAT) types for application traffic (or applications) that match the data traffic descriptor in the routing policy. The list of combinations of public land mobile networks and radio access technology (RAT) types may be sorted according to preferences indicated by device 510. The routing descriptor information may include selection information and radio access technology (RAT) type information. The selection information may include a list of public land mobile networks for application traffic (or applications) that match the data traffic descriptor in the routing policy. The selection information and the radio access technology (RAT) type information may each be sorted according to preferences indicated by device 510.

[0030] Some example implementations may provide routing policies that can be applied to one or more specified geographic areas. Routing policies may include rules that specify the preferred Radio Access Technology (RAT) type for a network slice or application. Routing policy and routing descriptor information may be sent only after receiving an indication that the user equipment supports dual access registration to multiple mobile networks.

[0031] Figure 4 An example flowchart of a method according to certain example embodiments is shown. In the example embodiments, Figure 4 The method can be performed by a user equipment, mobile device, or similar device in a 3GPP system, such as LTE, 5G-NR, or 6G. For example, in an exemplary embodiment, Figure 4 The method can be executed by the UE, similar to Figure 5 The device 520 shown in the figure.

[0032] According to various example embodiments, Figure 4 The method may include, at 410, sending a mobile network registration request and user equipment capability information to a first network entity. The capability information may include an indication of the device 520's ability to register for access to multiple mobile networks. At 420, the method may further include receiving and storing a routing policy with routing descriptor information from a second network entity. The routing policy may include network slices or registered mobile network-specific data of an application. At 430, the method may further include detecting application-specific data traffic and establishing a packet data unit session for the application-specific data traffic using the routing policy and routing descriptor information.

[0033] Some example embodiments may provide routing descriptor information that includes selection information comprising a list of combinations of Public Land Mobile Networks (PLNs) and Radio Access Technology (RAT) types for application traffic (or applications) that match data traffic descriptors in a routing policy. The list of combinations of PLANTs and RAT types may be sorted according to preferences indicated by a first network entity or a second network entity. The routing descriptor information may include selection information and RAT type information. The selection information may include a list of PLANTs for application traffic (or applications) that match data traffic descriptors in a routing policy.

[0034] Some example embodiments may provide selection information and Radio Access Technology (RAT) type information, which may each be ordered according to preferences indicated by a first network entity or a second network entity. Routing policies may be applied to one or more specified geographic areas. Capability information may include rules for the routing policy. Rules may include preferred RAT types for specifying network slices or applications. Routing policy and routing descriptor information may be received only after the transmitting device 520 has indicated that it supports dual access registration to multiple mobile networks.

[0035] Figure 5A set of devices 510, 520, and 530 according to various example embodiments are illustrated. In various example embodiments, device 510 may be configured to operate as an element or network entity in a communication network, such as a PCF. For example, PCF 205 according to the various example embodiments discussed above may be an example of device 510. That is, device 510 may be configured to operate as PCF 205 and thus be configured to perform one or more functions of PCF 205. In some example embodiments, device 510 may be configured to implement a virtualized network instance of PCF 205, the functionality of which may be distributed (or otherwise shared) in a network of devices including device 510. It should be noted that those skilled in the art will understand that device 510 may include Figure 5 Components or features not shown in the diagram. Furthermore, device 520 can be implemented as an element or network entity in a communication network, such as a UE, RedCap UE, SL UE, mobile device (ME), mobile station, mobile device, fixed device, IoT device, or other device. For example, UE 201 according to the various example embodiments discussed above can be an example of device 520. It should be noted that those skilled in the art will understand that device 520 may include... Figure 5 Components or features not shown. Furthermore, device 530 can be configured to operate as an element or network entity in a communication network, such as an AMF deployed in an HPLMN. For example, AMF 202 / 203 / 204 according to the various example embodiments discussed above can be examples of device 530. That is, device 530 can be configured to operate as AMF 202 / 203 / 204, and therefore configured to perform one or more functions of AMF 202 / 203 / 204. In some example embodiments, device 530 can be configured to implement a virtualized network instance of AMF 202 / 203 / 204, the functionality of which can be distributed (or otherwise shared) in a network of devices including device 530. It should be noted that those skilled in the art will understand that device 530 may include... Figure 5 Components or features not shown in the diagram.

[0036] In some example embodiments, devices 510, 520, and / or 530 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, or the like), one or more wireless access components (e.g., modems, transceivers, or the like), and / or a user interface. In some example embodiments, devices 510, 520, and / or 530 may be configured to operate using one or more wireless access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other wireless access technology.

[0037] like Figure 5 As shown in the examples, devices 510, 520, and / or 530 may respectively include or be coupled to processors 512, 522, and 532 for processing information and executing instructions or operations. Processors 512, 522, and 532 can be any type of general-purpose or special-purpose processor. In fact, processors 512, 522, and 532 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture, as an example. Although Figure 5 A single processor 512 (and 522 / 532) is shown for each of devices 510, 520, and / or 530, but multiple processors may be used according to other example embodiments. For example, it should be understood that in some example embodiments, devices 510, 520, and / or 530 may include two or more processors that can form a multiprocessor system (e.g., in this case, processors 512, 522, and 532 may represent multiple processors) that can support multiprocessing. According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster.

[0038] Processors 512, 522, and 532 can respectively perform functions associated with the operation of devices 510, 520, and / or 530, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of devices 510, 520, and / or 530, including... Figure 1-4 The process is shown in the figure.

[0039] Devices 510, 520, and / or 530 may also include or be coupled to memories 514, 524, and / or 534 (internal or external), which may be coupled to processors 512, 522, and 532, respectively, for storing information and instructions executable by processors 512, 522, and 532. Memory 514 (and memories 524 and 534) may be one or more memories and may be of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 514 (and memories 524 and 534) may include random access memory (RAM), read-only memory (ROM), static storage (e.g., disk or optical disk), hard disk drive (HDD), or any other type of non-transitory machine or computer-readable medium, and any combination thereof. The instructions stored in memory 514, memory 524 and memory 534 may include program instructions or computer program code, which, when executed by processors 512, 522 and 532, enable devices 510, 520 and / or 530 to perform the tasks described herein.

[0040] In some example embodiments, devices 510, 520, and / or 530 may also include or be coupled to (internal or external) drives or ports configured to receive and read external computer-readable storage media, such as optical discs, USB drives, flash drives, or any other storage media. For example, the external computer-readable storage media may store computer programs or software for execution by processors 512, 522, and 532 and / or devices 510, 520, and / or 530. Figure 1-4 Any method shown in the document.

[0041] According to various example embodiments, device 510 may include at least one processor 512 and at least one memory 514, such as Figure 5 As shown. Memory 514 may store instructions that, when executed by processor 512, cause device 510 to receive capability information of the user equipment from a user equipment via a network entity. The capability information may include indications of the user equipment's dual access registration capability with multiple mobile networks. Device 510 may also be configured to determine at least one geographic area corresponding to each of the multiple mobile networks and generate a routing policy for the at least one geographic area. The routing policy may include network slices or applied registered mobile network-specific data. Device 510 may also be configured to send the generated routing policy, along with routing descriptor information, to the user equipment.

[0042] According to various example embodiments, device 520 may include at least one processor 522 and at least one memory 524, such as Figure 5 As shown. Memory 524 can store instructions that, when executed by processor 522, cause device 520 to send a mobile network registration request and user equipment capability information to a first network entity. The capability information may include indications of device 520's ability to register for access to multiple mobile networks. Device 520 can also be made to receive and store a routing policy with routing descriptor information from a second network entity. The routing policy may include network slices or application-specific mobile network data. Device 520 can also be made to detect application-specific data traffic and establish packet data unit sessions for the application-specific data traffic using the routing policy and routing descriptor information.

[0043] In some example embodiments, devices 510, 520, and / or 530 may further include or be coupled to one or more antennas 515, 525, and 535 for receiving downlink signals and transmitting from devices 510, 520, and / or 530 via an uplink, respectively. Devices 510, 520, and / or 530 may also include transceivers 516, 526, and 536, respectively, configured to transmit and receive information. Transceivers 516, 526, and 536 may also include a wireless interface that may correspond to a variety of wireless access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, or similar technologies. The wireless interface may include other components, such as filters, converters (e.g., digital-to-analog converters or the like), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, or the like, to process symbols carried by the downlink or uplink, such as OFDMA symbols.

[0044] For example, transceivers 516, 526, and 536 may be configured to modulate information onto a carrier waveform for transmission and demodulate received information for further processing by other elements of devices 510, 520, and / or 530. In other example embodiments, transceivers 516, 526, and 536 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some example embodiments, devices 510, 520, and / or 530 may include input and / or output devices (I / O devices). In some example embodiments, devices 510, 520, and / or 530 may also include a user interface, such as a graphical user interface or a touchscreen.

[0045] In some example embodiments, memories 514, 524, and 534 store software modules that provide functionality when executed by processors 512, 522, and 532, respectively. These modules may include, for example, an operating system that provides operating system functionality for devices 510, 520, and / or 530. The memories may also store one or more functional modules, such as applications or programs, to provide additional functionality for devices 510, 520, and / or 530. Components of devices 510, 520, and / or 530 may be implemented in hardware or as any suitable combination of hardware and software. According to some example embodiments, devices 510, 520, and / or 530 may be optionally configured to communicate with each other via wireless or wired communication links 540, 550, and 560 according to any wireless access technology, such as NR.

[0046] According to some example embodiments, processors 512, 522, and / or 532, and memories 514, 524, and / or 534 may be included in or formed part of processing or control circuitry. Furthermore, in some example embodiments, transceivers 516, 526, and 536 may be included in or formed part of transceiver circuitry.

[0047] In some example embodiments, the apparatus (e.g., apparatus 510, 520, and / or 530) may include components for performing methods, processes, or any variations discussed herein. Examples of components may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing operations to be performed.

[0048] Some example embodiments may involve apparatus 510, which includes components for receiving capability information of a user equipment (UE) from a UE via a network entity. The capability information may include indications of the UE's dual access registration capability with multiple mobile networks. Apparatus 510 may also include components for determining at least one geographic area corresponding to each of the multiple mobile networks and components for generating a routing policy for the at least one geographic area. The routing policy may include network slices or applied registered mobile network-specific data. Apparatus 510 may also include components for sending the generated routing policy, along with routing descriptor information, to the UE.

[0049] Some example embodiments may relate to apparatus 520, which includes components for sending a mobile network registration request and user equipment capability information to a first network entity. The capability information may include indications of the apparatus's ability to register for access to multiple mobile networks. Apparatus 520 may also include components for receiving data and components for storing a routing policy with routing descriptor information from a second network entity. The routing policy may include network slices or registered mobile network-specific data of an application. Apparatus 520 may also include components for detecting application-specific data traffic and components for establishing packet data unit sessions for the application-specific data traffic using the routing policy and routing descriptor information.

[0050] As used herein, the term "circuit" can refer to a hardware circuit implementation only (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry with software / firmware, any portion of a hardware processor that works with software to enable a device (e.g., device 510, 520, and / or 530) to perform various functions, and / or hardware circuitry and / or a processor or portion thereof that operates using software but may not be present when operation is not required. As a further example, as used herein, the term "circuit" can also encompass an implementation of hardware circuitry or a processor or multiple processors only, or a portion of hardware circuitry or a processor, along with accompanying software and / or firmware. The term "circuit" can also encompass, for example, a baseband integrated circuit in a server, cellular network node, or other computing or networking device.

[0051] A computer program product may include one or more computer-executable components that, when the program runs, are configured to perform some example embodiments. The one or more computer-executable components may be at least one piece of software code or a portion thereof. Modifications and configurations required to implement the functionality of certain example embodiments may be executed as routines, which may be implemented as added or updated software routines. These software routines may be downloaded to the device.

[0052] As an example, software or computer program code, or portions thereof, may be in the form of source code, object code, or some intermediate form, and may be stored in some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such a carrier may include recording media, computer memory, read-only memory, photoelectric and / or electrical carrier signals, telecommunication signals, and software distribution packages, for example. Depending on the required processing power, the computer program may be executed in a single electronic digital computer or may be distributed across multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0053] In other example embodiments, this function may be performed by hardware or circuitry included in the device (e.g., devices 510, 520, and / or 530), for example, by using an application-specific integrated circuit (ASIC), a programmable gate array (PGA), a field-programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, this function may be implemented as a signal, i.e., a non-tangible component that can be carried by an electromagnetic signal downloaded from the Internet or other networks.

[0054] According to certain example embodiments, an apparatus (e.g., a node, device, or corresponding component) may be configured as a circuit, a computer, or a microprocessor (e.g., a microcontroller element) or a chipset, which includes at least a memory for providing storage capacity for arithmetic operations and an arithmetic processor for performing arithmetic operations.

[0055] The features, structures, or characteristics of the exemplary embodiments described in this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, phrases such as "some embodiments," "one exemplary embodiment," "some embodiments," or other similar language used throughout this specification refer to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Therefore, phrases such as "some embodiments," "one exemplary embodiment," "some embodiments," "other embodiments," or other similar language appearing throughout this specification do not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments. Furthermore, the terms "cell," "node," "gNB," or other similar language used in this specification are used interchangeably.

[0056] As used herein, "at least one of the following: " and "at least one of " and similar wording, wherein the list of two or more elements is connected by "and" or "or", means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0057] It will be readily understood by those skilled in the art that the disclosures discussed above can be practiced with processes in a different order and / or with hardware elements in a configuration different from the disclosed configurations. Therefore, although this disclosure has been described based on these exemplary embodiments, certain modifications, variations, and alternative constructions will be apparent to those skilled in the art, while remaining within the spirit and scope of the exemplary embodiments. While the above embodiments relate to 6G, 5G NR, and LTE technologies, they can also be applied to any other existing or future 3GPP technologies, such as LTE-advanced and / or fourth-generation (4G) technologies.

[0058] Partial vocabulary list: 3GPP Third Generation Partnership Project 5G fifth generation AMF application management functions ATSSS access traffic redirection, switching, and separation DL downlink EMBB Enhanced Mobile Broadband gNB5G or next-generation NodeB ID identifier LTE Long Term Evolution NAS Non-Access Layer NR New Radio NTN non-terrestrial network PCF strategy control function PDU Packet Data Unit PLMN Public Land Mobile Network RAT wireless access technology RSD route selection descriptor UE User Equipment UL uplink URSP User Equipment Routing Policy

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory for storing instructions that, when executed by the at least one processor, cause the device to at least: The capability information of the user equipment is received from the user equipment via a network entity, wherein the capability information includes an indication of the user equipment's ability to register for dual access to multiple mobile networks; Determine at least one geographic location corresponding to each of the plurality of mobile networks, and generate a routing policy for the at least one geographic location, wherein the routing policy includes registered mobile network-specific data for network slicing or applications; as well as Send the generated routing policy with routing descriptor information to the user equipment.

2. The apparatus of claim 1, wherein the routing descriptor information includes selection information, the selection information including a list of combinations of public terrestrial mobile network and radio access technology (RAT) types for applications that are matched with the data service descriptor in the routing policy.

3. The apparatus of claim 2, wherein the list of combinations of public terrestrial mobile networks and radio access technology (RAT) types is ordered according to preferences indicated by the apparatus.

4. The apparatus of claim 1, wherein the routing descriptor information includes selection information and radio access technology (RAT) type information, wherein the selection information includes a list of public terrestrial mobile networks for applications that are matched with the data service descriptor in the routing policy.

5. The apparatus of claim 4, wherein the selection information and the Radio Access Technology (RAT) type information are each sorted according to preferences indicated by the apparatus.

6. The apparatus according to any one of claims 1-5, wherein the routing strategy is applied to a specified geographic location or multiple geographic locations.

7. The apparatus according to any one of claims 1-6, wherein the routing policy includes rules, the rules including a preferred radio access technology (RAT) type for a specified network slice or application.

8. The apparatus according to any one of claims 1-7, wherein the routing policy and the routing descriptor information are sent only after receiving an indication that the user equipment supports dual access registration to multiple mobile networks.

9. An apparatus comprising: At least one processor; as well as At least one memory for storing instructions that, when executed by the at least one processor, cause the device to at least: Send a registration request for a mobile network to a first network entity, the registration request carrying capability information of the device, wherein the capability information includes an indication of the device's ability to register for access to multiple mobile networks; Receive and store a routing policy with routing descriptor information from a second network entity, wherein the routing policy includes registered mobile network-specific data for network slicing or applications; as well as Detect application-specific data services and establish packet data unit sessions for the application-specific data services using the routing policy and the routing descriptor information.

10. The apparatus of claim 9, wherein the routing descriptor information includes selection information, the selection information including a list of combinations of public terrestrial mobile network and radio access technology (RAT) types for applications that are matched with the data service descriptor in the routing policy.

11. The apparatus of claim 10, wherein the list of combinations of public terrestrial mobile networks and radio access technology (RAT) types is sorted according to a preference indicated by the first network entity or the second network entity.

12. The apparatus of claim 9, wherein the routing descriptor information includes selection information and radio access technology (RAT) type information, wherein the selection information includes a list of public terrestrial mobile networks for applications that are matched with the data service descriptor in the routing policy.

13. The apparatus of claim 12, wherein the selection information and the radio access technology (RAT) type information are each sorted according to a preference indicated by the first network entity or the second network entity.

14. The apparatus according to any one of claims 9-13, wherein the routing strategy is applied to a specified geographic location or multiple geographic locations.

15. The apparatus according to any one of claims 9-14, wherein the capability information includes rules for the routing policy, wherein the rules include a preferred Radio Access Technology (RAT) type for a specified network slice or application.

16. The apparatus according to any one of claims 9-15, wherein the routing policy and the routing descriptor information are received only after an indication that the apparatus supports dual access registration to multiple mobile networks is sent.

Images