Method and system for accessing services in multi-radio access technology network environment

Abstract

A method for accessing one or more services by a user equipment (UE) in a multi-radio access technology (multi-RAT) network, the method comprising: receiving, from an application associated with the UE, a request to access at least one of a service or a slice within the multi-RAT network; at least one of the RAT and a User Persistent Identifier (SUPI) is determined based on the mapping information and the received request. The mapping information indicates a relationship between the slice and at least one of a RAT associated with a network within the multi-RAT network and a SUPI stored at the UE; and establishing a connection with at least one of the networks within the multi-RAT network based on the determined at least one of the RAT and the SUPI for the at least one of the service or slice for the access request.

Description

Technical Field

[0001] The disclosure generally relates to mobile communication networks, and more specifically, to methods and systems for accessing one or more services or slices in a multi-radio access technology (multi-RAT) network environment. Background Technology

[0002] 5G slicing (5GS) supports both terrestrial 3GPP Next Generation Radio Access Network (NG-RAN) and non-terrestrial NG-RAN access technologies. Non-terrestrial NG-RAN technology helps extend 5G service to areas lacking coverage or sufficient connectivity, thereby enhancing the performance of terrestrial networks. Non-terrestrial NG-RAN technology ensures continuous service for user equipment (UEs) and mobile platforms such as passenger vehicles, aircraft, ships, high-speed trains, and buses, thus enhancing service reliability.

[0003] Non-terrestrial NG-RAN technologies generally enhance service availability, particularly for critical communications and future rail, maritime, and air communications. Furthermore, network slices tailored to specific use cases can be deployed by mobile network operators or private vendors across different technologies, such as Standalone Non-Public Networks (SNPN), Reduced Capability (RedCap), terrestrial NG-RAN, and non-terrestrial NG-RAN environments. Network slicing is also applicable to 5G+ or 6G networks and Radio Access Technologies (RATs) (or sub-RATs) deployed beneath the network. Moreover, network environments supporting these different combinations of the aforementioned networks and RATs are often referred to as multi-RAT network environments.

[0004] However, when a requested slice or service from a UE is rejected by one of the RATs in a Public Land Mobile Network (PLMN) / SNPN, the UE considers a rejection of the entire PLMN / SNPN. Therefore, even if another RAT in the same PLMN / SNPN can provide the requested slice or service to the UE, the UE cannot access the rejected slice and / or service. Similarly, when a requested slice or service from a UE is rejected based on a User Permanent Identifier (SUPI), the UE considers a rejection of all SUPIs configured at the UE. Therefore, even if another SUPI of the UE can provide the rejected slice or service to the UE from another RAT, the UE cannot access the rejected / unsupported slice or service.

[0005] Similar challenges arise when a requested slice or service is denied for a cell (i.e., the Registration Area (RA) or Tracking Area Identifier (TAI) of a specific RAT in a PLMN / SNPN). Furthermore, since neither the UE nor the network maintains a list of denied services / slices, the same challenges occur when the UE attempts to access the requested service or slice from different locations.

[0006] Typically, when slicing is supported across all satellite RAT types, RAT priority selection is not correctly defined. Therefore, even if Low Earth Orbit (LEO) or Medium Earth Orbit (MEO) cells are available, the UE may camp on a Geostationary Orbit (GEO) cell. This will result in UE latency and delayed service.

[0007] Therefore, there is a need to find solutions to the aforementioned technical problems associated with network slicing and service management in 5G and beyond 5G (B5G) networks. Summary of the Invention Technical issues

[0008] The primary objective of the embodiments herein is to disclose a method for a user equipment (UE) to access one or more services in a multi-radio access technology (multi-RAT) network.

[0009] Another objective of the embodiments herein is to disclose a user equipment (UE) for accessing one or more services in a multiple radio access technology (multiple RAT) network. Solution to the problem

[0010] According to the disclosed aspect, a method for accessing one or more services via a user equipment (UE) in a multi-radio access technology (multi-RAT) network, the method comprising: receiving from one or more applications associated with the UE a request for access to at least one of one or more services and one or more slices within the multi-RAT network; determining at least one of one or more RATs and one or more user permanent identifiers (SUPIs) based on mapping information and the received request, wherein the mapping information indicates relationships between multiple slices and multiple RATs associated with one or more networks within the multi-RAT network and at least one of multiple SUPIs stored at the UE; and establishing a connection with at least one of the one or more networks within the multi-RAT network based on the determined one or more RATs and at least one of the one or more SUPIs for the access request.

[0011] According to the disclosed aspect, a user equipment (UE) for accessing one or more services in a multiple radio access technology (multiple RAT) network, the UE comprising: at least one processor configured to: receive from one or more applications associated with the UE a request for access to one or more services and at least one of one or more slices within the multi-RAT network; determine at least one of one or more RATs and one or more user permanent identifiers (SUPIs) based on mapping information and the received request, wherein the mapping information indicates relationships between multiple slices and multiple RATs associated with one or more networks within the multi-RAT network and at least one of multiple SUPIs stored at the UE; and establish a connection with at least one of the one or more networks within the multi-RAT network based on the determined one or more RATs and at least one of the one or more SUPIs for the access request.

[0012] According to the disclosed aspect, a method for enabling a user equipment (UE) to access one or more services via a network device in a multi-radio access technology (RAT) network, the method comprising: receiving from the UE a request for access to at least one of one or more services and one or more slices within the multi-RAT network; and sending a response message to the UE, the response message indicating either rejection or acceptance of the one or more services and one or more slices within the received request, and mapping information, wherein the mapping information includes at least one of the following: a user equipment routing policy (URSP), an access network discovery and selection policy (ANDSP) or a home network configuration or control policy for selecting a RAT based on a service or slice, configured network slice selection assistance information (NSSAI), permitted NSSAI, optional NSSAI, slice or service priority, information related to supported frequency bands, SUPI, and a location associated with each of the one or more RATs within the multi-RAT network of a public terrestrial mobile network (PLMN) / independent non-public network (SNPN).

[0013] According to one aspect of the disclosure, a network apparatus is used to enable a user equipment (UE) to access one or more services in a multi-radio access technology (RAT) network, the network apparatus comprising: at least one processor configured to: receive from the UE a request for access to one or more services and at least one of one or more slices from a network within the multi-RAT network; and send a response message indicating either rejection or acceptance of the one or more services and at least one of the one or more slices for which the request has been received, as well as mapping information, wherein the mapping information includes at least one of the following: a user equipment routing policy (URSP), an access network discovery and selection policy (ANDSP), a home network configuration or control policy for selecting a RAT based on a service or slice, configured network slice selection assistance information (NSSAI), permitted NSSAI, optional NSSAI, slice or service priority, information related to supported frequency bands, SUPI, and a location associated with each of the one or more RATs within the multi-RAT network of a public terrestrial mobile network (PLMN) / independent non-public network (SNPN). Attached Figure Description

[0014] To further illustrate the advantages and features of the disclosure, a more specific description of the disclosure will be presented with reference to specific embodiments shown in the accompanying drawings. These drawings depict only typical embodiments of the disclosure and should not be considered as limiting its scope. The disclosure will be described and explained in the accompanying drawings with additional features and details.

[0015] These and other features, aspects, and advantages will become better understood when the following detailed description is read with reference to the accompanying drawings, in which the same reference numerals denote the same parts throughout the drawings, wherein:

[0016] Figure 1A and Figure 1B Each of the above illustrates one or more issues related to accessing one or more services and / or slices in a multi-RAT network environment, based on existing technologies.

[0017] Figure 2A and Figure 2B The illustration shows one or more embodiments according to the disclosure. Figure 1A and Figure 1B One or more solutions to one or more problems shown in the figure.

[0018] Figure 3 This illustrates a first problem scenario associated with a multi-RAT network environment based on existing technology.

[0019] Figure 4 This illustrates a second problem scenario associated with multi-SIM and multi-RAT network environments based on existing technologies.

[0020] Figure 5A and Figure 5B This illustrates a third problem scenario associated with a multi-RAT network environment based on existing technology.

[0021] Figure 6 This illustrates a fourth problem scenario associated with a multi-RAT network environment based on existing technologies.

[0022] Figure 7 The illustration shows one or more embodiments of the disclosed method. Figure 3 The first problem scenario corresponds to the first solution scenario.

[0023] Figure 8A and Figure 8B The illustration shows one or more embodiments of the disclosed method. Figure 3 The second solution scenario corresponds to the first problem scenario.

[0024] Figure 9 The illustration shows one or more embodiments of the disclosed method. Figure 3 The third solution scenario corresponds to the first problem scenario.

[0025] Figure 10A and Figure 10B The illustration shows one or more embodiments of the disclosed method. Figure 3 The fourth solution scenario corresponds to the first problem scenario.

[0026] Figure 11A and Figure 11B The illustration shows one or more embodiments of the disclosed method. Figure 4 The second problem scenario corresponds to the first solution scenario.

[0027] Figure 12A and Figure 12B The illustration shows one or more embodiments of the disclosed method. Figure 4 The second problem scenario corresponds to the second solution scenario.

[0028] Figure 13A and Figure 13B The illustration shows one or more embodiments of the disclosed method. Figure 4 The third solution scenario corresponds to the second problem scenario.

[0029] Figure 14A and Figure 14B The illustration shows one or more embodiments of the disclosed method. Figures 5A to 5B The solution scenario corresponding to the third problem scenario.

[0030] Figure 15 The illustration shows one or more embodiments of the disclosed method. Figure 6The solution scenario corresponding to the fourth problem scenario.

[0031] Figure 16 The present invention illustrates a method for a UE to access one or more services in a multi-RAT network environment, according to one or more embodiments disclosed herein.

[0032] Figure 17 The present invention illustrates a method for enabling a UE to access one or more services by a network device in a multi-RAT network environment, according to one or more embodiments disclosed herein.

[0033] Figure 18 The configuration of a UE in a wireless communication system according to a disclosed embodiment is shown; and

[0034] Figure 19 An exemplary diagram of a network device according to a disclosed embodiment is shown.

[0035] Furthermore, those skilled in the art will understand that the elements in the accompanying drawings are shown for simplicity and may not necessarily be drawn to scale. For example, the flowcharts illustrate the method according to the most prominent operations involved to aid in understanding the disclosed aspects. Additionally, regarding the construction of the apparatus, one or more components of the apparatus may have been indicated in the figures using conventional symbols, and the drawings may show only specific details relevant to understanding the disclosed embodiments, so as not to obscure the drawings with details readily understood by those skilled in the art who benefit from the description herein. Detailed Implementation

[0036] For the purpose of facilitating an understanding of the principles disclosed, reference will now be made to various embodiments, and specific language will be used to describe these embodiments. However, it will be understood that this is not intended to limit the scope of the disclosure, and such changes and further modifications in the illustrated systems, as well as such further applications of the principles disclosed therein, are considered to be common knowledge in the art to which this disclosure pertains. Those skilled in the art will understand that the foregoing general description and the following detailed description are interpretations of the disclosure and not limitations thereof.

[0037] Throughout this specification, references to "aspect," "on the other hand," or similar language indicate that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one of the disclosed embodiments. Therefore, the appearance of phrases such as "in one embodiment," "in another embodiment," and similar language throughout this specification may, but not necessarily, indicate the same embodiment.

[0038] The terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process or method that includes a list of steps may include not only those steps but also other steps not expressly listed or inherent to such a process or method. Similarly, without further constraints, a list of one or more devices, subsystems, elements, structures, or components beginning with “comprising…” does not exclude the presence of other devices or subsystems or elements or structures or components, or additional devices or subsystems or elements or structures or components. The terms “user” and “participant” are used interchangeably throughout the specification.

[0039] The term “combination” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “send,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The term “or” is an inclusive term meaning “and / or.” The phrase “associated with” and its derivatives mean including, being included in, interconnected with, containing, being contained within, connected to or connected with, combined to or combined with, able to communicate with, cooperate with, interleaved, juxtaposed, proximate, bound to or bound with, having, possessing the properties of, having a relationship to or with, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Whether local or remote, the functionality associated with any particular controller can be centralized or distributed. When used with a list of items, the phrase “at least one of” indicates that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C, and any variations thereof. As an additional example, the expression "at least one of a, b, or c" may indicate only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof. Similarly, the term "set" means one or more. Therefore, a set of items can be a single item or a collection of two or more items.

[0040] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" mean one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer (such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage). "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that permanently store data and media that store data and can be rewritten later (such as rewritable optical discs or erasable memory devices).

[0041] Figure 1A and Figure 1B This document illustrates one or more issues related to accessing one or more services and / or slices within multi-RAT network environments 100a and 100b (collectively referred to as multi-RAT network environment 100), based on existing technologies. Multi-RAT network environments 100a and 100b may include a 5G core network (5GCN) 104 (hereinafter referred to as network 104) comprising a terrestrial network (TN) 104a and a non-terrestrial network (NTN) 104b. In one embodiment, NTN 104b may represent a network operating via an airborne / space vehicle for communication. Specifically, NTN 104b may include networks such as, but not limited to, satellite-based cellular networks, high-altitude platform-based cellular networks, underwater networks, or air-to-ground networks. In some embodiments, NTN may also include unmanned aerial vehicle (UAV)-based cellular networks. TN 104a may correspond to a communication network operating primarily on the Earth's surface or within its atmosphere. TN 104a can be based on various technologies (such as, but not limited to, wired infrastructure (e.g., fiber optic cables), wireless communication towers (e.g., cellular towers), and other terrestrial systems). Examples of TN 104a include, but are not limited to, cellular networks, Internet backbones, terrestrial telephone networks, Wi-Fi networks, etc. Multi-RAT network environment 100 can correspond to a network that supports multiple RATs to achieve efficient and seamless communication. Multi-RAT network environment 100 can include, but is not limited to, terrestrial or non-terrestrial networks, 5G Reduced Capability (REDCAP) networks, Public Terrestrial Mobile Networks (PLMNs), or Standalone Non-Public Mobile Networks (SNPNs) with beyond 5G or 6G capabilities.

[0042] Multi-RAT network environments 100a and 100b may include UE 102. In multi-RAT network environment 100a, UE 102 may be a single User Identity Module (SIM) device, while in multi-RAT network environment 100b, UE 102 may correspond to a multi-SIM (MUSIM) device. In one exemplary embodiment, UE 102 may be a dual-SIM device.

[0043] exist Figure 1A In this context, UE 102 is a single-SIM device configured with a single network profile. UE 102 may include multiple applications running on UE 102 to perform one or more operations. Each of the multiple applications may be configured to provide one or more network services to UE 102 via one or more slices of network 104. The one or more slices may be provided by one or more networks 104a, 104b of the multi-RAT network environment 100. Examples of the multiple applications may include, but are not limited to, call applications, gaming applications, video conferencing applications, etc. Furthermore, examples of UE 102 may include, but are not limited to, computers, tablets, mobile devices, or any other device capable of sending information to and receiving information from the network.

[0044] In one example embodiment, UE 102 may include two applications (i.e., APP1 and APP2), which respectively require access to at least one of slice 1 or service 1 and slice 2 or service 2 from network 104. Furthermore, TN 104a may only support service 1 or slice 1. The NTN may support both slice 1 or service 1 and slice 2 or service 2. However, UE 102 may attempt to access both slices (i.e., slice 1 and slice 2) and / or services (i.e., service 1 and service 2) from TN 104a. Therefore, UE 102 sends a registration request from TN 104a to the desired slices 1 and 2 or services 1 and 2. In response, TN 104a may send a registration acceptance message indicating that slice 1 or service 1 is allowed and slice 2 or service 2 is rejected. Therefore, APP1 at UE 102 may obtain service, while APP2 at UE 102 may not obtain any service. Specifically, even if different RATs (i.e., NTN 104b) are able to provide the two requested slices and / or services to UE 102, UE 102 may still consider rejecting the entire PLMN / SNPN and / or multi-RAT network environment 100. Therefore, UE 102 may not be able to access the rejected slice / service from the same PLMN / SNPN / RedCap / B5G / 6G via another RAT.

[0045] exist Figure 1BIn this configuration, UE 102 is a multi-SIM device comprising SIM1 configured with network profile 1 and SIM2 configured with network profile 2. Furthermore, TN 104a can be configured to support slice 1 and / or service 1, and NTN 104b can be configured to support slice 2 and / or service 2. However, when UE 102 attempts to access a service / slice for APP1 and App2, as discussed above, UE 102 may only request TN 104a. Therefore, in response, TN 104a may send a registration acceptance message indicating that slice 1 or service 1 is allowed and slice 2 or service 2 is rejected. Thus, APP1 at UE 102 may obtain service, while APP2 at UE 102 may not obtain any service. Therefore, since UE 102 can include any information about which slice / service is supported by which RAT-based network of the multi-RAT network environment 100, UE 102 can consider rejecting the requested slice or service for the entire PLMN / SNPN, even if SIM2 of UE 102 may be able to connect to NTN 104b to access the rejected slice or service.

[0046] In some embodiments, if a request from UE 102 is rejected at a specific cell, UE 102 may consider the rejection for all cells within the same PLMN / SNPN. Furthermore, UE 102 may not maintain any list of rejected slices / services and their corresponding RATs; therefore, when UE 102 moves to another location or switches to a different RAT, the list of rejected slices / services can be deleted, and UE 102 may attempt to access the desired slice / service via an incorrect combination of RAT or SIM.

[0047] Furthermore, if slicing or services are supported across all RATs, RAT priorities may not be defined at UE 102 or network 104. Therefore, even if high-coverage cells are available, UE 102 may camp / register on low-coverage cells. This results in UE 102 having no service or experiencing delayed service.

[0048] Figure 2A and Figure 2B Show Figure 1A and Figure 1B One or more solutions to one or more problems shown in the figure. Figure 2A The diagram shows UE 102 corresponding to a multi-RAT network environment 100a with a single SIM device. In the disclosed solution, UE 102 may be pre-configured with mapping information indicating the relationship between multiple slices / services and at least one or more RATs associated with one or more networks within the multi-RAT network environment 100a, and multiple user general personal identifiers (SUPIs) stored at UE 102.

[0049] Each of the multiple SUPIs can be associated with a corresponding SIM implemented at UE 102. Specifically, the mapping information can indicate which particular RAT and / or SUPI needs to be selected in order to access a service / slice of network 104. For example, the mapping information can include that NTN 104a of network 104 can support only slice 1 or service 1, while NTN 104b of network 104 can support two slices (i.e., slice 1 and slice 2) and / or services (i.e., service 1 and service 2).

[0050] Based on this information, to access slice 1 / service 1 or slice 2 / service 2, UE 102 can directly connect to NTN 104b of the same network 104 (i.e., the same PLMN or SNPN) instead of sending a registration request to TN 104a. UE 102 can then send a registration request to access the desired slice / service, and since NTN 104b can support two slices / services, UE 102 can access each requested slice / service. Therefore, both APP1 and APP2 at UE 102 can access the desired service / slice. This saves time and improves the overall user experience in the multi-RAT network environment 100a. In one embodiment, the mapping information discussed above can be pre-configured at UE 102 in the USIM or corresponding memory element. In such an embodiment, the mapping information can be pre-configured at UE 102 by the HPLMN or network operator.

[0051] In an alternative embodiment, network 104 may include mapping information. For example, TN 104a and NTN 104b may include required mapping information for supported slices / services and unsupported slices / services. TN 104a and NTN 104b may also include mapping information corresponding to each other. For example, TN 104a may include mapping information corresponding to NTN 104b, indicating the slices / services supported by NTN 104b, and vice versa. Therefore, in such... Figure 1A In the problem illustrated, when UE 102 sends a request to access slice 1 / service 1 and slice 2 / service 2 from TN 104a, TN 104a may allow slice 1 / service 2 and deny slice 2 / service 2. However, TN 104a may also send mapping information to UE 102, enabling UE 102 to access the denied slice / service from another RAT-based network (i.e., NTN 104b). Therefore, UE 102 can obtain access to both services required for APP1 and APP2.

[0052] Figure 2BThe diagram illustrates a multi-SIM device in a multi-RAT network environment 100b. Similar to the solution disclosed above, UE 102 may also include mapping information indicating relationships between multiple slices / services and at least one or more RATs associated with one or more networks within the multi-RAT network environment 100b, and multiple SUPIs stored at UE 102. For example, the multiple SUPIs may correspond to SIM1 and SIM2 of UE 102. In an example embodiment, the mapping information may indicate that TN 104a supports slice 1 / service 1, and NTN 104b supports slice 2 / service 2. Therefore, based on this information, to access slice 1 / service 1 and slice 2 / service 2, instead of sending only a registration request to TN 104a, UE 102 can use two SIMs (i.e., SIM1 and SIM2) to establish connections with both TN 104a and NTN 104b, thereby simultaneously gaining access to both services / slices. This allows for appropriate utilization of resources at UE 102 and / or network 104, and improves the overall user experience.

[0053] In an alternative embodiment, network 104 may include mapping information. For example, TN 104a and NTN 104b may include the required mapping information for supported slices / services and unsupported slices / services. TN 104a and NTN 104b may also include mapping information corresponding to each other. For example, TN 104a may include mapping information corresponding to NTN 104b, indicating the slices / services supported by NTN 104b, and vice versa. Therefore, in such... Figure 1B In the problem illustrated, when UE 102 sends a request to access slice 1 / service 1 and slice 2 / service 2 from TN 104a, TN 104a may allow slice 1 / service 2 and deny slice 2 / service 2. However, TN 104a may also send mapping information to UE 102, enabling UE 102 to access the denied slice / service from a different RAT-based network (i.e., NTN 104b) via a different SIM2. Therefore, UE 102 can obtain access to both services required for APP1 and APP2.

[0054] In one embodiment, TN 104a and / or NTN 104b may share mapping information with UE 102 via any suitable communication protocol / information element (IE) (such as, but not limited to, UE policy container (i.e., UE routing policy (URSP)), roaming steering (Steering) / RAT steering (SoR) container, downlink network non-access stratum (DL-NAS) message, etc.).

[0055] In some embodiments, network 104 may also share the optional slice ID of a service / slice that has been rejected in the current RAT. For example, however, when TN 104a cannot support slice 2, the corresponding service 2 may be supported by slice 3, which TN 104a can support, and network 104 may indicate slice 3 to UE 102. This allows UE 102 to access the desired service via handover on the RAT.

[0056] Figure 3 The first problem scenario associated with a multi-RAT network environment 100 according to the prior art is illustrated. The first problem scenario involves one or more of the following prerequisites. First, slice-1 is exclusively provided and served by TN 104a (i.e., supported only within the Tracking Area Identifier (TAI) of TN104a). Slice-1 cannot be supported in the TAI of the non-terrestrial network (NTN) 104b. Second, UE 102 lacks the necessary Registration Area (RA) information.

[0057] In the first problem scenario, during operation 302, the NG-RAN (corresponding to TN 104a) and the NG-RAN satellite (corresponding to NTN 104b) are associated with the same Public Terrestrial Mobile Network (PLMN) (i.e., PLMN 1) provided by 5G network 104. TN 104a supports one or more services associated with slice-1, while NTN 104b supports one or more services associated with slice-2, which has coverage including TAI2, TAI3, and TAI4.

[0058] During operations 304 to 306, UE 102 attempts to camp on the NG-RAN satellite of PLMN-1 (i.e., NTN 104b) by sending a Radio Resource Control (RRC) Connection Establishment Complete Message (Registration Request-Initial) to Access Single Network Slice Selection Assistance Information (S-NSSAI)-1.

[0059] In operation 308, the NG-RAN satellite (i.e., NTN 104b) forwards the received RRC connection establishment completion message to the 5G network (NW) 104 and / or associated network entities (e.g., Access and Mobility Management Function (AMF)).

[0060] During operation 310, upon receiving the RRC connection establishment completion message, the 5G network 104 detected that the NG-RAN satellite (i.e., NTN 104b) does not support S-NSSAI-1.

[0061] In operation 312, upon detection, the 5G network 104 sends a registration rejection message to the UE 102. The registration rejection message may include an indication to the UE 102 "#62: S-NSSAI-1 for the current RA being rejected".

[0062] In operations 314 and 316, UE 102 may not have a RA list and may add the current TAI to the blocked TAI (FTAI) list. As a result, UE 102 may only block the current TAI and may only reside for limited services or emergency services.

[0063] In operation 316, UE 102 can then search for other TAIs (e.g., find TAI3) in the same RAT-based network (i.e., NTN 104b) and receive another rejection for the same reason. TAI3 will then be added to the UE's FTAI list. UE 102 may face a similar rejection when attempting to register on TAI4, and this TAI will also be added to the FTAI list. Because UE 102 cannot successfully register on any NTN TAI due to the lack of RA information, these operations can continue until UE 102 tries all available frequency bands in NTN 104b. In other words, because UE 102 attempts to register on different TAIs within NTN 104b and cannot successfully complete the registration process, the lack of the RA list during the initial registration rejection causes UE 102 to sequentially add TAIs to its FTAI list. This can lead to a waste of resources on both the UE 102 and NTN 104b sides. Furthermore, this adds latency to the services requested by UE 102.

[0064] Figure 4 This illustrates a second problem scenario associated with a multi-RAT network environment 100 according to existing technology. The sequence flowchart may include several operations as outlined below. The second problem scenario involves one or more of the following prerequisites.

[0065] First, UE 102 has two User Identification Modules (SIMs) or User Permanent Identifiers (SUPIs) associated with a single or the same user.

[0066] Second, UE 102 is configured with two different network slices (e.g., slice-1 and slice-2).

[0067] Third, slice-1 is dedicated to TN 104a, while slice-2 is dedicated to NTN 104b.

[0068] Fourth, application-1 is mapped and associated with slice-1, while application-2 is mapped and associated with slice-2.

[0069] In the second problem scenario, during operations 402 to 404, UE 102 camps on NG-RAN (i.e., TN 104a) by utilizing the function of SIM-1, and UE 102 camps on NG-RAN-satellite (i.e., NTN104b) by utilizing the function of SIM-2.

[0070] In operation 406, UE 102 sends an RRC connection establishment complete message (registration request-initial) to access S-NSSAI-1 and S-NSSAI-2 via SIM1 and NG-RAN (i.e., TN 104a).

[0071] In operation 408, the NG-RAN (i.e., TN 104a) forwards the received RRC connection establishment completion message to the 5G network 104 and / or the associated AMF.

[0072] In operation 410, upon receiving the RRC connection establishment complete message, the 5G network 104 detects that the NG-RAN (TN104a) supports S-NSSAI-1 and that the NG-RAN (TN 104a) does not support S-NSSAI-2.

[0073] In operation 412, upon detection, the 5G network 104 sends a registration acceptance message to the UE 102 (SIM-1), wherein the registration acceptance message indicates that S-NSSAI-1 is allowed for TAI for TN 104a, and S-NSSAI-2 is rejected.

[0074] In operation 414, UE 102 (SIM-1) sends a slice information SIM-1 message to the application, wherein the slice information SIM-1 message indicates that S-NSSAI-1 is allowed and S-NSSAI-2 is rejected for TAI for TN 104a.

[0075] In operation 416, UE 102 sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (i.e., NTN 104b) to access S-NSSAI-1 and S-NSSAI-2 via SIM2.

[0076] During operation 418, the NG-RAN satellite (NTN 104b) forwards the received RRC connection establishment completion message to the 5G network 104 and / or AMF.

[0077] During operation 420, upon receiving an RRC connection establishment completion message from the NG-RAN satellite (NTN 104b), the 5G network 104 detects that the NG-RAN satellite (NTN 104b) supports S-NSSAI-2 and does not support S-NSSAI-1.

[0078] In operation 422, upon detection, the 5G network 104 sends a registration acceptance message to the UE (SIM-2), wherein the registration acceptance message indicates that S-NSSAI-1 is allowed and S-NSSAI-2 is rejected for TAI for NTN 104b.

[0079] In operation 424, UE 102 (SIM-2) sends a slice information SIM-2 message to the application, wherein the slice information SIM-2 message indicates that S-NSSAI-2 is allowed and S-NSSAI-1 is denied for TAI for NTN 104b.

[0080] In operation 426, UE 102 with SIM-1 registers for both slice-1 and slice-2. UE 102 is accepted for slice-1 but rejected for slice-2. Therefore, application-1 (App1) is able to obtain the relevant service, while application-2 (App2) cannot initiate the requested service. Thus, even though UE 102 has SIM2 / SUPI2 residing on NTN 104b, UE 102 lacks the information to establish a Packet Data Unit (PDU) session on NTN 104b to make service 2 available and / or initialize App-2, and UE 102 cannot obtain the required service. This results in a poor user experience and delayed service for UE 102.

[0081] Figure 5A and Figure 5B This illustrates a third problem scenario associated with a multi-RAT network environment 100 according to existing technology. The sequence flowchart may include several operations outlined below. The third problem scenario involves one or more of the following prerequisites. First, slice-1 and slice-2 are configured for UE 102. Second, slice-1 is within the coverage area of ​​NG-RAN (TN 104a) TAI. Slice-2 is within the coverage area of ​​NG-RAN satellite (NTN 104b TAI). TN TAI is TAI1. NTN TAIs are TAI2 and TAI3.

[0082] In the third problem scenario, under Operation 502, NG-RAN (TN 104a) and NG-RAN satellites (NTN 104b) are associated with the same PLMN. TN 104a supports one or more services associated with slice-1 (TAI1), while NTN 104b supports one or more services associated with slice-2, covering TAI2 and TAI4.

[0083] During operations 504 to 506, UE 102 attempts to camp on the NG-RAN satellite (NTN 104b) by sending an RRC connection establishment complete message (registration request-initial) to access S-NSSAI-1 and S-NSSAI-2.

[0084] In operation 508, the NG-RAN satellite (NTN 104b) forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF-1). In operation 510, upon receiving the RRC connection establishment complete message, the 5G network 104 detects that the NG-RAN satellite (NTN 104b) does not support S-NSSAI-1. In operations 512 to 514, the 5G network 104 sends a partially rejected NSSAI list to assist UE 102, or sends a registration acceptance message to UE 102, wherein the registration acceptance message indicates "Allowed S-NSSAI-2, Partially Rejected S-NSSAI-1: TAI2, TAI3".

[0085] During operations 516 to 518, upon receiving a registration acceptance message, UE 102 stores S-NSSAI-1 for TAI2 and TAI3 that were rejected, and continues to use services from S-NSSAI-2.

[0086] In operation 520, UE 102 reselected to RA2 of the NG-RAN satellite (NTN 104b).

[0087] In operation 522, UE 102 sends an RRC connection establishment complete message (registration request-mobility) to access S-NSSAI-2.

[0088] During operation 524, the NG-RAN satellite (NTN 104b) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-1).

[0089] In operation 526, upon receiving the RRC connection establishment complete message, the 5G network 104 sends a registration acceptance message, which indicates "Allowed S-NSSAI-2".

[0090] In operation 528, UE 102 then removes the list of rejected NSSAIs / partially rejected NSSAIs. Afterward, RA (e.g., RA2) is modified and registration is attempted.

[0091] In operation 530, UE 102 can try slice-1 again.

[0092] In operation 532, UE 102 sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (NTN 104b) (PLMN-1, RA2) to access S-NSSAI-1 and S-NSSAI-2.

[0093] During operation 534, the NG-RAN satellite (NTN 104b) (PLMN-1, RA2) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-2).

[0094] During operation 536, upon receiving the RRC connection establishment complete message, 5G network 104 detected that the NG-RAN satellite (NTN104b) does not support S-NSSAI-1.

[0095] In operations 538 to 540, the 5G network 104 sends a partially rejected S-NSSAI list to assist UE 102, or sends a registration acceptance message to UE 102, indicating "Allowed S-NSSAI-2, Partially Rejected S-NSSAI-1: TAI4, TAI5". Therefore, when UE 102 moves to a new registration area (RA2) covered only by NTN TAIs, UE 102 requests mobility registration for slice 2. This request is accepted, and the previously rejected S-NSSAI list is removed. UE 102 then triggers another mobility registration, this time adding slice 1. However, because the NG-RAN satellite network's TAI cannot serve slice 1, slice 1 is rejected again. Therefore, the rejected S-NSSAI list is removed each time a new RA changes. Because the partially allowed and partially denied S-NSSAI lists are mapped to the RA (Registration Authority), these lists are either deleted each time the RA changes, or no specific processing is mentioned for managing the partially allowed and partially denied S-NSSAI lists. This behavior could cause potential problems for UE 102, as it may lose information about previously denied S-NSSAIs, which could be significant for subsequent registration attempts or service access.

[0096] Figure 6 The fourth problem scenario is illustrated in relation to a multi-RAT network environment 100 according to existing technology. The sequence flowchart may include several operations as outlined below. The fourth problem scenario involves one or more of the following prerequisites. First, slice-1 is configured in the UE for PLMN-1. Second, slice-1 is supported in the TAI of both TN and NTN, which include low Earth orbit (LEO), geostationary orbit (GEO), and medium Earth orbit (MEO) satellite networks.

[0097] In the fourth problem scenario, under Operation 602, NG-RAN and NG-RAN satellites are associated with the same PLMN. All NG-RAN and NG-RAN satellites (TAI) support slice 1.

[0098] During operations 604 to 608, UE 102 attempts to camp on the NG-RAN satellite of PLMN1 (i.e., GEO) by sending an RRC connection establishment complete message (registration request-initial) to access S-NSSAI-1.

[0099] During operation 610, the NG-RAN satellite (GEO) forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF).

[0100] In operation 612, upon receiving the RRC connection establishment complete message, the 5G network 104 sends a registration acceptance message to the UE 102.

[0101] In operation 614, compared to LEO NG-RAN satellites, UE 102 may experience delayed service due to increased latency when camped on GEO NG-RAN satellites. UE 102 is within the coverage area of ​​NG-RAN satellites, which include both LEO and GEO satellite networks. When UE 102 detects the availability of a GEO NG-RAN satellite, UE 102 selects and camps on a GEO NG-RAN satellite in PLMN-1. UE 102 then requests slice 1 and is accepted. The problem is that there is no defined RAT selection logic for NG-RAN satellites specified in 3GPP specifications 23.122 and 31.102. These specifications do not provide a priority order for different NG-RAN satellite technologies (LEO, GEO, MEO, and other satellite RATs). As a result, UE 102 camps on the first available GEO cell and registers with network 104 for slice-1. Because UE 102 resides on GEO NG-RAN satellites (which typically have higher latency), this can result in reduced service latency or Quality of Service (QoS) compared to LEO NG-RAN satellites. The lack of a defined RAT selection logic for NG-RAN satellite technology in the 3GPP specifications may lead to suboptimal network selection and service experience for UE 102.

[0102] Figure 7 This illustrates a relationship based on one or more embodiments. Figure 3 The first problem scenario corresponds to the first solution scenario in the sequence flowchart. The sequence flowchart may include several operations as outlined below. The first solution scenario involves one or more of the following prerequisites, as shown in the table below.

[0103]

[0104] In addition, when UE 102 is a multi-SIM UE, the solution may involve one or more of the following prerequisites:

[0105]

[0106] In operation 702, UE 102 is configured with a Network Slice Selection Assistance Information (NSSAI) list, which includes a slice / service type (SST) 1 for enhanced mobile broadband service (eMBB), a slice distinguisher (SD) 1 with a single Network Slice Selection Assistance Information (S-NSSAI) 1 supported on a next-generation radio access network (NG-RAN) with frequency band 1, and an SD2 with S-NSSAI 2 supported on an NG-RAN satellite network (low Earth orbit, LEO) with frequency band 2. Specifically, UE 102 may include mapping information indicating the relationship between multiple slices and at least one of multiple RATs associated with one or more networks within the multi-RAT network environment 100.

[0107] In operations 704 to 708, when UE 102 is camped on NG-RAN satellite network 104b and wants to use eMBB service for application 1, because S-NSSAI 2 is within the coverage area of ​​the camped NG-RAN satellite network 104b, the UE requests S-NSSAI 2 instead of S-NSSAI 1.

[0108] In operation 710, specifically, since the slice service is mapped based on RAT and configured in UE 102, UE 102 can send an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (LEO) to access S-NSSAI2.

[0109] During operation 712, the NG-RAN satellite (LEO) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-1).

[0110] In operation 714, upon receiving the RRC connection establishment complete message, the 5G network 104 can send a registration accept message to the UE, indicating that S-NSSAI 2 is allowed on the NG-RAN satellite (LEO) network.

[0111] Using this solution, UE 102, being configured in the UE's NSSAI list, has the ability to select the appropriate S-NSSAI and / or network slice based on its current location and available network capabilities. The UE's ability to request the correct S-NSSAI and the network's response upon accepting the request ensure successful establishment of the desired service on NG-RAN satellites.

[0112] exist Figure 7 In the first solution, slices are pre-configured with specific RAT information and provided to UE 102 in a list of partially allowed and partially denied S-NSSAIs. UE 102 can avoid requesting slices that are not allowed in a specific RAT and can request services or slices only in supported SUPIs and RATs.

[0113] In one or more embodiments, when network 104 sends a registration acceptance message and provides RAT information for slices that are only allowed to operate in specific RATs and TAIs using a partially permitted S-NSSAI list, UE 102 can use this information during PDU session establishment and mobility registration to register only those slices in permitted SUPI and RAT combinations and permitted TAIs.

[0114] In one or more embodiments, when a slice is not permitted in any TAI of a particular RAT, network 104 may use a partially rejected S-NSSAI list to indicate that the slice is not permitted for use with a PLMN or Independent Non-Public Network (SNPN) in a particular RAT. UE 102 may use this information to avoid requesting slices in any Registered Area (RA) or TAI of the same PLMN / SNPN / RedCap / B5G / 6G that is not supported by the RAT.

[0115] In one or more embodiments, when UE 102 moves from NG-RAN to an NG-RAN satellite network, the partially allowed and partially denied S-NSSAI lists of RATs can be removed, and vice versa. The network can also share additional information (such as SUPI, RAT, frequency band, and location) with UE 102 to assist UE 102 in determining which slices to trigger registration and selection for. This enables efficient and effective resource utilization and prevents delays in requested services.

[0116] In one or more embodiments, User Equipment Routing Policy (URSP) rules may include band and RAT information, as well as a SUPI for a service or slice, and may be shared with UE 102 via NAS or downlink signaling messages. UE 102 may use this information for PLMN / SNPN selection on the corresponding SUPI and RAT to select service or slice requirements, and for PDU session activation based on slices that support the SUPI and RAT. URSP rules may be defined using S-NSSAI values ​​that will be tried in different RATs, and the RAT type is added to the routing descriptor (RSD) for the same service descriptor (e.g., application) to indicate which RAT the PDU session should first try using the S-NSSAI value. If the corresponding application only supports a specific RAT, UE 102 may use this information during PLMN / SNPN selection and PDU session establishment based on SUPI and RAT support.

[0117] In one or more embodiments, RAT-specific mapping information that guides UE 102 to select a specific RAT / SUPI may be included in a DL NAS message or a SOR container.

[0118] exist Figure 7 The aforementioned solutions, including the use of partially permitted and partially denied S-NSSAI lists, URSP rules, and RAT-specific information, are applicable to future RATs in 5G and 6G networks.

[0119] Figure 8A and Figure 8B The second solution scenario is shown. Figure 8A and Figure 8B In this context, the solution can correspond to the reference. Figure 3 The solution to the first problem scenario is explained. The sequence flowchart may include several operations as outlined below, and involves one or more of the following prerequisites, as shown in the table below.

[0120]

[0121] Specifically, UE 102 can be configured with URSP rules containing RAT information, which is located locally in a memory element corresponding to UE 102 or in a USIM installed within UE 102. In another embodiment, UE 102 can be configured with URSP rules as shown in the table via signal-notified URSP.

[0122] In operation 802, UE 102 can be configured with URSP as discussed above.

[0123] Operations 804 to 814 are similar to those described in the reference. Figure 7Operations 704 to 714 are explained, therefore detailed descriptions of them are omitted.

[0124] During operations 802 to 814, UE 102 camps within the coverage area of ​​NG RAN satellite GEO-PLMN 1 (also known as HPLMN or Home Network). Furthermore, the user of UE 102 opens App1, a service requiring slice type eMBB. Because the slice service is mapped based on RAT and configured as URSP in UE 102, UE 102 correctly sends S-NSSAI2 instead of S-NSSAI-1 in the requested S-NSSAI.

[0125] Therefore, in Operation 816, a PDU connection is established with S-NSSAI2 based on URSP assessment to route services while residing on the NG-RAN satellite LEO.

[0126] However, during operation 818, the user closed App-1.

[0127] Therefore, in operation 820, the PDU associated with App-1 is now released.

[0128] In operation 822, the user opens App-2, which is related to the NG-RAN satellite GEO.

[0129] During operation 824, UE 102 is camped on the GEO cell.

[0130] In operation 826, UE 102 sends an RRC connection establishment completion message (registration request-mobility) with requested slice S-NSSAI 3 to NG-RAN satellite-PLMN1-GEO.

[0131] During operation 828, the NG-RAN satellite (GEO) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-1).

[0132] In operation 830, upon receiving the RRC connection establishment complete message, the 5G network 104 can send a registration accept message to the UE 102, instructing that S-NSSAI 3 be allowed on the NG-RAN satellite (GEO) network. Therefore, the UE 102 can effectively and efficiently utilize the resources associated with the UE 102 and the network 104 by leveraging the configured URSP rules for PLMN / SNPN selection.

[0133] exist Figures 8A to 8B The aforementioned solutions, including those using URSP for PLMN / SNPN selection, are applicable to future RATs in 5G and 6G networks.

[0134] Figure 9A third solution scenario is shown based on one or more of the disclosed embodiments. Figure 9 The solution shown in the figure corresponds to the reference. Figure 3 The solution to the first problem scenario is explained.

[0135] In operation 902, NG-RAN (TN 104a) and NG-RAN satellite (NTN 104b) can correspond to the same PLMN as network 104. UE 102 can be configured with slice 1, and TN 104a can be configured to support slice 1 (TAI1).

[0136] In operation 904, UE 102 resides on the NG-RAN satellite (NTN 104b).

[0137] In operation 906, the user of UE 102 opens App1, which requires a slice type eMBB service.

[0138] In operation 908, UE 102 can send an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (NTN 104b) associated with PLMN1-RA1 to access S-NSSAI 1.

[0139] During operation 910, the NG-RAN satellite (NTN 104b) forwards the received RRC connection establishment complete message to network 104 (e.g., AMF-1).

[0140] In operation 912, upon receiving the RRC connection establishment complete message, network 104 can determine that the PLMN (NTN 104b) in the NG-RAN satellite access does not support slice S-NSSAI 1.

[0141] In operation 914, network 104 sends a registration rejection message to UE 102. In one embodiment, network 104 may send a registration rejection message with a rejection clause 62 indicating "NSSAI rejected for the current RA". The registration rejection message may also include a new information element (IE) indicating the RAT and the corresponding mapped service. For example, the new ID may include "RAT: NG-RAN satellite (LEO / GEO / MEO / other) / new IE - mapped service configured NSSAI-S-NSSAI2". In an alternative embodiment, network 104 may accept the registration message and provide in the registration acceptance message the slice of the new configuration to be used on the NG-RAN satellite and S-NSSAI-1 from the list of rejected NSSAIs.

[0142] In Operation 916, UE 102 without RA can add TAI to the FTAI list of RAT S-NSSAI-1 mapped to the rejected NSSAI list.

[0143] In operation 918, based on the information included in the new IE, UE 102 may request eMBB services provided by network 104.

[0144] Specifically, UE 102 may perform operations 920 to 922, similar to operations 908 to 910, to establish a connection with the NG-RAN satellite (NTN 104b) to access S-NSSAI-2.

[0145] In operation 923, upon receiving the RRC connection establishment complete message, network 104 can determine that the PLMN supports slice S-NSSAI 2 in NG-RAN satellite access (NTN 104b).

[0146] In operation 924, network 104 can accept registration requests to allow S-NSSAI-2 access to UE 102. Therefore, UE 102 can effectively access the requested service in a multi-RAT environment.

[0147] like Figure 9 As shown, the above-mentioned solutions, including the use of the newly configured S-NSSAI for service access, are applicable to future RATs in 5G, 6G, and next-generation networks.

[0148] Figure 10A and Figure 10B A fourth solution scenario is illustrated according to one or more of the disclosed embodiments. The fourth solution scenario is based on a UE booted according to a RAT. Figure 9 The solution shown in the figure corresponds to the reference. Figure 3 The solution to the first problem scenario is explained. The sequence flowchart may include several operations as outlined below.

[0149] In Operation 1002, in this solution scenario, the NG-RAN satellite (NTN 104b) is associated with the MEO PLMN (Home PLMN), and the NG-RAN (TN 104a) is associated with PLMN2 (Visiting PLMN).

[0150] In operations 1004 to 1006, UE 102 resides on an NG-RAN satellite (NTN 104b) and wants to use eMBB services for application 1.

[0151] In operation 1008, UE 102 sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (GEO) (NTN 104b) to access S-NSSAI-1.

[0152] In operation 1010, the NG-RAN satellite (GEO) (NTN 104b) forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF-1).

[0153] In operation 1012, UE 102 and 5G network 104 complete the non-access stratum (NAS) security procedures.

[0154] In operation 1014, after a successful NAS security process, the 5G network 104 sends a registration acceptance message to UE 102, indicating that S-NSSAI-1 is an S-NSSAI that is permitted for UE 102.

[0155] In operation 1016, the Home Public Terrestrial Mobile Network (HPLMN) detected that UE 102 could be better served for eMBB services by roaming to PLMN2 under the LEO coverage area.

[0156] In operation 1018, the 5G network 104 sends a downlink NAS (DL-NAS) message (specifically, an SOR message) to UE 102, indicating that the mapped S-NSSAI2 is available on the PLMN2 NG-RAN-LEO network.

[0157] In operation 1020, UE 102 performs a local release of NAS signaling.

[0158] As a result of operation 1022, UE 102 resides on the PLMN2-LEO network.

[0159] In operation 1024, UE 102 sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (LEO) (NTN 104b) to access the S-NSSAI-2 network slice.

[0160] In operation 1026, the NG-RAN satellite (LEO) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-2).

[0161] In operation 1028, 5G network 104 (e.g., AMF-1) detected that the PLMN in the NG-RAN satellite (NTN 104b) supports S-NSSAI-2 network slicing.

[0162] At operation 1030, the 5G network 104 (e.g., AMF-1) sends a registration acceptance message to the UE, indicating that S-NSSAI-2 is an allowed network slice selection auxiliary information for the UE 102.

[0163] In operation 1032, as a result, UE 102 receives better service from PLMN2 under the LEO coverage area.

[0164] In operation 1034, the 5G network (e.g., AMF-1) 104 sends an additional registration acceptance message to the UE 102 to further confirm that S-NSSAI-2 is an allowed network slice selection auxiliary information.

[0165] In this solution, when the HPLMN detects that UE 102 can be better served by a VPLMN within the same LEO coverage area, network 104 utilizes the SOR function / SOR information. Specifically, the 5G network 104 sends a DL-NAS message containing SOR information to UE 102. This SOR information indicates that the mapped S-NSSAI-2 is available on the PLMN2 NG-RAN-LEO network. Upon receiving the SOR information, UE 102 locally releases its signaling connection and autonomously moves it to the PLMN2 network. UE 102 then registers with the S-NSSAI-2 network slice, enabling it to receive better service compared to the previous GEO coverage network. This disclosed solution allows network 104 to leverage the advantages of LEO coverage to guide UE 102 to the optimal PLMN and network slice without explicit UE involvement. The UE's local release of the signaling connection and autonomous registration with the appropriate S-NSSAI on the PLMN2 network improves the user experience by providing better quality of service.

[0166] Figure 11 illustrates a fifth solution scenario according to one or more embodiments disclosed. The fifth solution scenario is based on URSP rules. Figure 11 may correspond to references. Figure 4 The solution to the second problem scenario is explained. The sequence flowchart may include several operations as outlined below.

[0167] In one or more embodiments, if the required service or network slice is unavailable on the current SUPI or RAT of UE 102, UE 102 may trigger the necessary service on an additional SUPI or RAT within UE 102.

[0168] In one or more embodiments, when network 104 sends a registration acceptance message, network 104 may provide RAT-specific information for network slices that are only allowed to operate on specific RATs and TAIs. The RAT-specific information is transmitted via a partially permitted NSSAI list of the registered SUPI / RAT. UE 102 and / or applications may utilize the RAT-specific information during the PDU session establishment process. If the desired service or slice is not available for the received SUPI / RAT, UE 102 may trigger service or slice registration in another SUPI or RAT.

[0169] In one or more embodiments, network 104 may use an SOR container or DL-NAS message to carry a new information element (IE) providing RAT-specific or SUPI-specific information to guide UE 102 in selecting an appropriate RAT or SUPI. UE 102 may then use this information for PLMN or Independent Non-Public Network (SNPN) selection to access services not supported by the current RAT or SUPI in a different RAT or SUPI.

[0170] In one or more embodiments, network 104 may update UE routing policy (URSP) rules to provide RAT-specific information. The URSP may include information such as the frequency band of a specific service or slice, RAT, SUPI, or home operator details. This information can be shared with UE 102 via NAS or downlink signaling messages. UE 102 can use this information to perform PLMN or SNPN selection on the corresponding SUPI or RAT so that if the current RAT or SUPI does not support or has no traffic rules configured for the application, the desired service or slice can be selected on another SUPI or RAT and a PDU session activation can be initiated. The above solution is applicable to future RATs in 5G and 6G networks.

[0171] In one or more embodiments, another solution is URSP-based slicing and RAT selection, along with one or more prerequisites, as described below.

[0172] UE 102 can be configured with one or more URSP rules, which include information about network slices, RAT, SUPI, and HPLMN. This information can be stored locally on UE 102, provided in the USIM, or notified to UE 102 via network signaling.

[0173] The structure of the URSP rules is shown in the two tables below, providing the necessary details for the UE to make informed decisions regarding slice and RAT selection.

[0174]

[0175]

[0176] The proposed solution (URSP-based solution) shown in Figure 11 involves the following prerequisites. First, the UE has two active SUPI or SIM cards, each with a separate user. Second, the UE is configured with two network slices. Slice-1 is served only by the TN. Slice-2 is served only by the NTN. Third, applications running on the UE are mapped to their respective network slices as follows: Application 1 (App1) is mapped to Slice-1. Application 2 (App2) is mapped to Slice-2.

[0177] The sequence flowchart shown in Figure 11 may include several operations as outlined below.

[0178] In the URSP-based solution, during operations 1102 to 1106, UE 102 accesses S-NSSAI-1 and S-NSSAI-2 by sending an RRC connection setup completion message (registration request-initial). UE 102 camps on NG-RAN (TN 104a) using the functionality of SIM-1, and UE 102 camps on NG-RAN satellite (NTN 104b) using the functionality of SIM-2.

[0179] In operation 1108, the NG-RAN (TN 104a) forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF).

[0180] In operation 1110, upon receiving the RRC connection establishment complete message, the 5G network 104 detects that NG-RAN supports S-NSSAI-1 and NG-RAN does not support S-NSSAI-2.

[0181] In operation 1112, upon detection, the 5G network 104 sends a registration acceptance message to the UE (SIM-1), wherein the registration acceptance message indicates that for the TN TAI, the NG-RAN allows / supports S-NSSAI-1 and rejects S-NSSAI-2.

[0182] In operation 1114, UE 102 (SIM-1) sends a slice information SIM-1 message to the application, wherein the slice information SIM-1 message indicates that for TN TAI, NG-RAN allows / supports S-NSSAI-1 and rejects S-NSSAI-2.

[0183] In operation 1116, the 5G network 104 sends a DL-NAS message to SIM-1. This DL-NAS message contains URSP information, which indicates the following: First, for application 1 (APP-1), the allowed S-NSSAI is S-NSSAI-1, and the allowed RAT is RAT-TN. Second, for application 2 (APP-2), the allowed S-NSSAI is S-NSSAI-2, and the allowed RAT is RAT-NTN.

[0184] In operation 1118, SIM-1 forwards the received URSP information as URSP data to the application running on UE 102. The URSP information allows the application to make informed decisions about appropriate network slicing and RAT selection based on its respective service requirements. UE 102 can then use this policy information to initiate PDU session establishment based on the application's needs and available network capabilities (see operation 1134).

[0185] In operation 1120, the UE sends an RRC connection establishment complete message (registration request - initial) to the NG-RAN satellite to access S-NSSAI-1 and S-NSSAI-2. In operation 1122, the NG-RAN satellite forwards the received RRC connection establishment complete message to the 5G-NW (e.g., AMF). In operation 1124, upon receiving the RRC connection establishment complete message, the 5G network 104 detects that the NG-RAN satellite supports S-NSSAI-2 and does not support S-NSSAI-1.

[0186] In operation 1126, upon detection, the 5G network 104 sends a registration acceptance message to UE 102 (SIM-1), wherein the registration acceptance message indicates that for the TN's TAI, the NG-RAN allows / supports S-NSSAI-1 and rejects S-NSSAI-2. In operation 1128, UE 102 (SIM-1) sends a slice information SIM-2 message to the application, wherein the slice information SIM-2 message indicates that for the NTN's TAI, the NG-RAN allows / supports S-NSSAI-2 and rejects S-NSSAI-1.

[0187] In operation 1130, the 5G network 104 sends a DL-NAS message to SIM-1. This DL-NAS message contains URSP information, which indicates the following: First, for application 1 (APP-1), the allowed S-NSSAI is S-NSSAI-1, and the allowed RAT is RAT-TN. Second, for application 2 (APP-2), the allowed S-NSSAI is S-NSSAI-2, and the allowed RAT is RAT-NTN.

[0188] In operation 1132, SIM-1 forwards the received URSP information as URSP data to the application running on UE 102. The URSP information allows the application to make informed decisions about appropriate network slicing and RAT selection based on its respective service requirements. UE 102 can then use this policy information to initiate PDU session establishment based on the application's needs and available network capabilities (see operation 1134).

[0189] In operation 1134, application-2 initiates a PDU session in SIM-2 / SUPI-2 residing on NTN.

[0190] In operation 1136, the application (e.g., application-2) sends a PDU session establishment request for S-NSSAI-2 to SIM-2.

[0191] In operation 1138, SIM-2 sends a PDU session establishment request to 5G-NW.

[0192] In operations 1140 to 1142, upon receiving a PDU session establishment request, the 5G-NW sends a PDU acceptance message to the application via SIM-2, triggering the establishment of a Data Radio Bearer (DRB) for application-2 across the NTN coverage area. This sequence of operations allows application-2, mapped to the S-NSSAI-2 slice, to successfully establish a PDU session and associated DRB within the NTN coverage area. The use of SIM-2 / SUPI-2 and the 5G-NW response enables the application to access the necessary network resources and services via the appropriate NTN.

[0193] Figures 12A to 12B A second solution scenario (a bootstrapping-based solution) is shown according to one or more embodiments. Figures 12A to 12B Can correspond to reference Figure 4 The solution to the second problem scenario is explained. The sequence flowchart may include several operations as outlined below.

[0194] In the guided solution, in Operation 1202, the NG-RAN satellite is associated with MEO PLMN (HPLMN), and the NG-RAN is associated with PLMN2 (VPLMN).

[0195] In operations 1204 to 1206, UE 102 (SIM-1) is camped on an NG-RAN satellite (GEO) and wants to use eMBB service for application 1 and low-latency service for application 2.

[0196] In operation 1208, UE 102 (SIM-1) sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (GEO) to access S-NSSAI-1 and S-NSSAI-2.

[0197] At operation 1210, the NG-RAN satellite (GEO) forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF-1).

[0198] In operation 1212, UE 102 and 5G network 104 complete the non-access stratum (NAS) security protocol.

[0199] In operation 1214, after a successful NAS security process, the 5G network 104 sends a registration acceptance message to the UE 102, indicating that S-NSSAI-1 and S-NSSAI-2 are S-NSSAIs that are permitted for the UE 102.

[0200] In operation 1216, UE 102 (SIM-1) sends a PDU request for accessing S-NSSAI-1 to 5G network 104.

[0201] In operation 1218, in response to the PDU request, UE 102 (SIM-1) receives a PDU acceptance message from 5G network 104.

[0202] In operation 1220, UE 102 (SIM-1) sends a PDU request for accessing S-NSSAI-2 to 5G network 104.

[0203] In operation 1222, in response to the PDU request, UE 102 (SIM-1) receives a PDU acceptance message from 5G network 104.

[0204] In operation 1224, UE 102 (SIM-2) resides on an NG-RAN satellite (LEO).

[0205] In operation 1226, UE 102 (SIM-2) sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (LEO) to access S-NSSAI-1.

[0206] During operation 1228, the NG-RAN satellite (LEO) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-1).

[0207] In operation 1230, the 5G network 104 sends a registration acceptance message to UE 102 (SIM-2), indicating that UE 102 can access S-NSSAI-1.

[0208] In operation 1232, HPLMN detected that UE 102 can be better served with SUPI-2 users and LEO network for eMBB services.

[0209] In operation 1234, UE 102 is camped on an NG-RAN satellite operating in the GEO network.

[0210] In operation 1236, UE 102 receives a DL-NAS message from 5G network 104, which contains information about the S-NSSAI-1 network slice, SUPI-2 users, and LEO network.

[0211] In operation 1238, UE 102 uses the SIM-2 / SUPI-2 user and LEO network to establish a PDU session for S-NSSAI-1.

[0212] In operation 1240, UE 102 (using SIM-2 / SUPI-2) sends a PDU session establishment request for S-NSSAI-1 network slice to the 5G network.

[0213] In operation 1242, UE 102 (using SIM-2 / SUPI-2) receives a PDU session establishment acceptance from 5G network 104, which indicates that the UE is allowed to access the S-NSSAI-1 network slice.

[0214] The aforementioned sequence of operations demonstrates that the UE can utilize HPLMN to detect the improved eMBB service availability for SUPI-2 users and LEO networks. The UE's reception of DL-NAS messages, establishment of PDU sessions, and subsequent signaling with the 5G network enable the UE to access the S-NSSAI-1 network slice through the optimal SUPI-2 and LEO network combination recommended by HPLMN.

[0215] Figure 13A and Figure 13B A third solution scenario (based on NAS signaling) is illustrated according to one or more embodiments. Figures 13A to 13B Can correspond to reference Figure 4 The solution to the second problem scenario is explained. The sequence flowchart may include several operations as outlined below.

[0216] In the case of NAS signaling, during operations 1302 to 1306, by sending an RRC connection setup completion message (registration request-initial) to access S-NSSAI-1 and S-NSSAI-2, UE 102 camps on NG-RAN (TN 104b) using the function of SIM-1, and UE camps on NG-RAN satellite (NTN 104b) using the function of SIM-2.

[0217] In operation 1308, the NG-RAN forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF).

[0218] In operation 1310, upon receiving the RRC connection establishment complete message, the 5G network 104 detects that NG-RAN supports S-NSSAI-1 and NG-RAN does not support S-NSSAI-2.

[0219] In operation 1312, upon detection, the 5G network sends a registration acceptance message to UE 102 (SIM-1), where the registration acceptance message indicates that for TN TAI, NG-RAN allows / supports S-NSSAI-1 and rejects S-NSSAI-2.

[0220] In operation 1314, UE 102 (SIM-1) sends a slice information SIM-1 message to the application, wherein the slice information SIM-1 message indicates that for TN TAI, NG-RAN allows / supports S-NSSAI-1 and rejects S-NSSAI-2.

[0221] In operation 1316, UE 102 (SIM-2) sends an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite to access S-NSSAI-1 and S-NSSAI-2.

[0222] In operation 1318, the NG-RAN satellite forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF).

[0223] In operation 1320, upon receiving the RRC connection establishment complete message, the 5G network 104 detects that the NG-RAN satellite supports S-NSSAI-2 and the NG-RAN satellite does not support S-NSSAI-1.

[0224] In operation 1322, upon detection, the 5G network 104 sends a registration acceptance message to the UE (SIM-2), wherein the registration acceptance message indicates that for the TN TAI, the NG-RAN allows / supports S-NSSAI-1 and rejects S-NSSAI-2.

[0225] In operation 1324, UE 102 (SIM-1) sends a slice information SIM-2 message to the application, wherein the slice information SIM-2 message indicates that for the TAI of NTN, NG-RAN allows / supports S-NSSAI-2 and rejects S-NSSAI-1.

[0226] In operation 1326, application-2 initiates a PDU session in SIM-2 / SUPI-2 residing on NTN.

[0227] In operation 1328, the application (e.g., application-2) sends a PDU session establishment request for S-NSSAI-2 to SIM-2.

[0228] In operation 1330, SIM-2 sends a PDU session establishment request to 5G-NW.

[0229] In operations 1332 to 1334, upon receiving a PDU session establishment request, the 5G network 104 sends a PDU acceptance message to the application via SIM-2, triggering the establishment of a Data Radio Bearer (DRB) for application-2 across the NTN coverage area. This sequence of operations allows application-2, mapped to the S-NSSAI-2 slice, to successfully establish a PDU session and associated DRB within the NTN coverage area. The use of SIM-2 / SUPI-2 and the response of the 5G-NW enable the application to access the necessary network resources and services via the appropriate NTN.

[0230] Figure 14A and Figure 14B A solution scenario corresponding to the third problem scenario in Figure 5 is shown, according to one or more disclosed embodiments. The sequence flowchart may include several operations as outlined below. Figure 14A and Figure 14B The proposed solution shown may involve the following two prerequisites. First, configure slice-1 and slice-2 for the UE. Second, support slice-1 in TN TAI and slice-2 in NTN TAI (i.e., TN-TAI1 / NTN-TAI2, TAI3).

[0231] The aforementioned prerequisites are highlighted as Operation 1402.

[0232] In operation 1404, UE 102 resides on the NG-RAN satellite (NTN 104b).

[0233] In operation 1406, UE 102 can send an RRC connection establishment complete message (registration request-initial) to NG-RAN satellite network 104b to access S-NSSAI 1 and S-NSSAI-2.

[0234] At operation 1408, the NG-RAN satellite forwards the received RRC connection establishment complete message to the 5G network 104 (e.g., AMF-1).

[0235] In operation 1410, upon receiving the RRC connection establishment complete message, the 5G network 104 can determine that the PLMN does not support slicing S-NSSAI-1 in NG-RAN satellite access.

[0236] Therefore, in operation 1412, the 5G network 104 can send a partially rejected NSSAI list to assist UE 102.

[0237] In operation 1414, network 104 sends a registration acceptance message to UE 102, indicating that S-NSSAI-2 is allowed and S-NSSAI-1 is rejected. Furthermore, the registration acceptance message includes an indication of the new IEs supported by S-NSSAI-1.

[0238] In operation 1416, UE 102 may store the rejected S_NSSAI-1 received from network 104 for "TAI2 and TAI3 not allowed for NG-RAN satellite types".

[0239] During operation 1418, UE 102 can continue to receive services from S-NSSAI-2.

[0240] In operation 1420, UE 102 reselected to RA2 of the NG-RAN satellite.

[0241] During operations 1422 to 1426, UE 102 can perform RRC connection establishment.

[0242] In operation 1426, UE 102 may receive a registration acceptance message indicating that the requested S-NSSAI-2 registration is permitted.

[0243] In operation 1428, the list of rejected NSSAIs is not deleted, and the list of rejected NSSAIs is maintained on a per RAT basis.

[0244] In operation 1430, UE 102 wants to access slice-1.

[0245] However, in operation 1432, signaling attempts are not based on the stored list of rejected NSSAIs.

[0246] Figure 15 The illustration shows a corresponding embodiment based on one or more of the disclosed embodiments. Figure 6 The solution scenario for the fourth problem scenario. The solution scenario is based on the priority of the RAT defined at UE 102. The sequence flowchart may include several operations as outlined below.

[0247] In operation 1502, NG-RAN (TN 104a) and NG-RAN satellites (NTN 104b) can correspond to the same PLMN associated with network 104. Furthermore, slice 1 is supported by all NG-RAN (TN 104a) and NG-RAN satellite TAI (NTN 104b).

[0248] In operation 1504, the NG-RAN satellite TAI is configured in the SIM associated with UE 102 with a corresponding priority for each NG-RAN satellite type. For example, priorities can be defined for NG-RAN satellite LEO, NG-RAN satellite MEO, and NG-RAN satellite GEO, where NG-RAN satellite LEO can be given the highest priority and NG-RAN satellite GEO can be given the lowest priority.

[0249] Operation 1506 may indicate that the above priority can be defined at the SIM associated with UE 102.

[0250] In Operation 1508, UE 102 can reside on the NG-RAT satellite (NTN 104b) for the required services / slicing.

[0251] In operation 1510, UE 102 may reside on the NG-RAN satellite LEO instead of the NG-satellite GEO based on the priority stored at UE 102.

[0252] In operation 1512, UE 102 can send an RRC connection establishment complete message (registration request-initial) to the NG-RAN satellite (LEO) to access S-NSSAI 1.

[0253] In operation 1514, the NG-RAN satellite (LEO) forwards the received RRC connection establishment completion message to the 5G network 104 (e.g., AMF-1).

[0254] In operation 1516, upon receiving the RRC connection establishment complete message, the 5G network 104 may send a registration acceptance message to the UE, indicating that S-NSSAI 1 is allowed on the NG-RAN satellite (LEO) network.

[0255] Therefore, in Operation 1518, UE 102 can obtain better service than GEO coverage.

[0256] The SIM has RAT priorities defined in the order that NG-RAN satellite GEO is given the highest priority and NG-RAN satellite MEO is given the lowest priority. UE 102 can reside on NG-RAN satellite GEO to avoid service. The priority of different types of RATs can be defined based on factors such as, but not limited to, the UE's location, PLMN, HPLMN, and the user of UE 102. Furthermore, if each RAT type is given the same priority, UE 102 can prioritize NG-RAN satellite LEO over NG-RAN satellite GEO or NG-RAN satellite MEO.

[0257] In one embodiment, UE 102 may store priority information in a USIM file, such as an Elementary File user-controlled PLMN with Access Technology (EFPLMNWACT), an Elementary File operator-controlled PLMN with Access Technology (EFOPLMNWACT), or an Elementary File home PLMN selector with Access Technology (EFHPLMNWACT). Such a USIM file can specify detailed support for the RAT types supported by NG-RAN satellites and their corresponding priorities. Therefore, when the PLMN supports all NG-RAN satellite RAT types, priority settings should be considered to ensure reduced latency. However, in the absence of defined priorities for different RAT types, UE 102 may select the PLMN in the RAT in the following order: NG-RAN > NG-RAN satellite LEO > NG-RAN satellite MEO > NG-RAN satellite GEO.

[0258] Figure 16 A method is shown for UE 102 to access one or more services in a multi-RAT network environment 100.

[0259] In operation 1602, method 1600 may include receiving a request from one or more applications associated with UE 102 for access to at least one of one or more services and one or more slices within the multi-RAT network environment 100.

[0260] In operation 1604, method 1600 may include determining at least one of one or more RATs and one or more User Permanent Identifiers (SUPIs) based on mapping information and a received request. The mapping information indicates the relationship between multiple slices and at least one or more RATs associated with one or more networks within a multi-RAT network, and multiple SUPIs stored at UE 102. In one embodiment, the mapping information may include, but is not limited to, a User Equipment Routing Policy (URSP), an Access Network Discovery and Selection Policy (ANDSP), or a home network configuration or control policy for selecting RATs based on service or slice, configured Network Slice Selection Assistance Information (NSSAI), permitted NSSAIs, optional NSSAIs, slice or service priorities, information related to supported frequency bands, SUPIs, and the location associated with each of the one or more RATs within a multi-RAT environment of a Public Terrestrial Mobile Network (PLMN) / Independent Non-Public Network (SNPN).

[0261] In one embodiment, to determine at least one of one or more RATs and one or more SUPIs, method 1600 may include establishing a connection with at least one of one or more networks within a multi-RAT network environment 100. Subsequently, method 1600 may include sending a request to at least one of the one or more networks to access at least one of one or more services and one or more slices. Furthermore, method 1600 may include receiving a response message including an indication of either rejection or acceptance of at least one of the one or more services and one or more slices, as well as mapping information.

[0262] Specifically, in one embodiment, mapping information may be pre-configured at UE 102. For example, the mapping information may be stored in a memory element of UE 102 or in the USIM of UE 102. The mapping information may be stored at UE 102 by the network operator. In an alternative embodiment, the mapping information may be provided to UE 102 by network 104 via any suitable signaling message (such as, but not limited to, DLNAS signaling, SOR container, registration request message, etc.).

[0263] In some embodiments, method 1600 may further include: maintaining a list of networks and associated Tracking Area Identifiers (TAIs) and access environments, including SNPN, REDCAP networks, TN, NTN, B5G, and 6G, based on a received response message having an indication of rejection for at least one of one or more services and one or more slices. Method 1600 may also include avoiding access to any network based on information included in the network list.

[0264] In operation 1606, method 1600 may include: establishing a connection with at least one of one or more networks within a multi-RAT network environment based on at least one of one or more determined RATs and one or more SUPIs for the access request. Furthermore, in one embodiment, method 1600 may include identifying at least one or more services or slices not supported in the current RAT or SUPI based on response messages or mapping information. Subsequently, method 1600 may include establishing a second connection via one or more determined RATs or one or more SUPIs to access one or more identified services or slices.

[0265] In one or more embodiments, one or more RATs may include, but are not limited to, 5G NTN or 5G TN, wherein the priority of one or more RATs may be pre-configured in at least one of the user-controlled PLMN access technology basic file (EFPLMNWACT), the operator-controlled PLMN access technology basic file (EFOPLMNWACT), the home PLMN selector access technology basic file (EFHPLMNWACT), and the memory element of the UE, and the priority of one or more RATs is mapped to one or more services or one or more slices in the mapping information.

[0266] In one or more embodiments, the UE may also take additional actions (e.g., change from one access mode to another) before attempting to connect to the network. For example, when operating in PLMN access mode, access to the SNPN network is not permitted. Similarly, when operating in SNPN access mode, access to the PLMN is not permitted. Therefore, if a particular slice or service is only possible on a specific access configured in the UE or indicated to the UE by the network, the UE can change to the corresponding access mode to utilize those services.

[0267] The embodiments are exemplary in nature, and as Figure 16 The operation of method 1600 shown can occur in a varying order according to various embodiments.

[0268] Figure 17 A method is shown for enabling UE 102 to access one or more services by network device 104 in a multi-RAT network environment 100.

[0269] In operation 1702, method 1700 may include receiving from UE 102 a request for access to at least one of one or more services and one or more slices within the multi-RAT network environment 100.

[0270] In operation 1704, method 1700 may include sending a response message to UE 102, the response message including an indication of rejection and acceptance of at least one of one or more services and one or more slices within the received request, as well as mapping information. The mapping information may include data such as, but not limited to, User Equipment Routing Policy (URSP), Access Network Discovery and Selection Policy (ANDSP), policy for selecting RATs based on service or slice, configured Network Slice Selection Assistance Information (NSSAI), allowed NSSAIs, optional NSSAIs, slice or service priority, information related to supported frequency bands, SUPI, and the location associated with each of one or more RATs in a multi-RAT environment within a PLMN / SNPN.

[0271] In one embodiment, method 1700 may further include identifying the location of UE 102. Thereafter, method 1700 may include determining at least one of one or more RATs associated with network 104 and / or one or more SUPIs associated with UE 102, based at least on received requests, mapping information, the user, and the location of UE 102. Next, method 1700 may include guiding UE 102 to establish a connection based on at least one of the determined network-based RATs and one or more SUPIs of UE 102.

[0272] The embodiments are exemplary in nature, and as Figure 17 The operation of method 1700 shown can occur in a varying order according to various embodiments.

[0273] Figure 18 The configuration of UE 1800 in a wireless communication system according to a disclosed embodiment is shown. Figure 18 The configuration can be understood as part of the configuration of UE 1800. Furthermore, the method 1600 disclosed above can be implemented in UE 1800 according to another embodiment. In one embodiment, UE 1800 corresponds to UE 102.

[0274] Reference Figure 18 The UE 1800 may include at least one processor 1802, communication circuitry 1804 (e.g., a communicator or communication interface), and memory 1806. As an example, the UE 1800 may be a cellular phone or other device that communicates via multiple cellular networks, such as 3G, 4G, 5G or near-5G, 6G networks, or any future wireless communication network. The communication circuitry 1904 may perform functions for transmitting and receiving signals via a wireless channel.

[0275] As an example, processor 1802 may be a single processing unit or multiple units, all of which may include multiple computing units. Processor 1802 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any means of manipulating signals based on operating instructions. Among other capabilities, processor 1802 is configured to acquire and execute computer-readable instructions and data stored in memory 1806. Processor 1802 may include one or more processors. In this case, one or more processors 1802 may be a general-purpose processor (such as a central processing unit (CPU), application processor (AP), etc.), a graphics-only processor (such as a graphics processing unit (GPU), a vision processor (VPU)), and / or an AI-specific processor (such as a neural processor (NPU)). One or more processors 1802 may control the processing of input data according to predefined operating rules or artificial intelligence (AI) models stored in non-volatile memory and volatile memory (i.e., memory 1806). Predefined operating rules or AI models are provided through training or learning.

[0276] The memory 1806 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (such as static random access memory (SRAM) and dynamic random access memory (DRAM)) and / or non-volatile memory (such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk and magnetic tape).

[0277] The embodiments are exemplary in nature, and the UE 1800 may include additional components required to achieve the desired functionality of the UE 1800 in accordance with the requirements of the disclosure.

[0278] Figure 19 An exemplary diagram of a network device 1900 (also referred to as network 1900) according to a disclosed embodiment is shown. Network 1900 may correspond to any suitable network type (such as, but not limited to, 5G network, 6G network, etc.). Network 1900 may include TN and NTN. Network 1900 may be configured to perform method 1700 as described above. Network 1900 may correspond to the network elements / components discussed throughout the specification. Network 1900 may include at least one processor 1902, communication circuitry 1904, and memory 1906. Furthermore, network 1900 may also include a cloud RAN (C-RAN), central unit (CU), core network (NW), distributed unit (DU), or any other possible network (NW) entity. In one embodiment, network 1900 may correspond to network 104 and / or associated devices.

[0279] The communication circuit 1904 can perform one or more functions for transmitting and receiving signals via a wireless channel. The memory 1906 can be configured to store information / data required by the processor 1902 to perform one or more desired functions according to the disclosed network 1900.

[0280] The processor 1902, communication circuit 1904, and memory 1906 may each have a structure similar to that disclosed in reference UE 1800 for the processor 1802, communication circuit 1804, and memory 1806. Therefore, for the sake of brevity, detailed descriptions of these components are omitted.

[0281] While the embodiments explained above are defined with reference to the term RAT, the embodiments are extensible and applicable to any future technologies and / or communications introduced or used in place of RAT.

[0282] In addition, refer to Figure 1 to Figure 19 The illustrated embodiments are also applicable to maritime communication services on 3GPP systems.

[0283] Although specific language has been used to describe the disclosure, it is not intended to create any limitation. As will be apparent to those skilled in the art, various working modifications can be made to the method to achieve the inventive concept as taught herein.

[0284] The accompanying drawings and the foregoing description provide examples of embodiments. Those skilled in the art will understand that one or more of the described elements can be well combined into a single functional element. Optionally, a particular element may be divided into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and is not limited to the manner described herein.

Claims

1. A method for accessing one or more services via a user equipment (UE) in a multiple radio access technology (multiple RAT) network, the method comprising: Receive requests from one or more applications associated with the UE for access to one or more services and one or more slices within the multi-RAT network; Based on the mapping information and the received request, at least one of one or more RATs and one or more user permanent identifiers (SUPIs) is determined, wherein the mapping information indicates the relationship between multiple slices and multiple RATs associated with one or more networks within a multi-RAT network and at least one of multiple SUPIs stored at the UE. as well as Based on the one or more services used for the access request and at least one of the one or more slices, a connection is established with at least one of the one or more networks within the multi-RAT network.

2. The method according to claim 1, further comprising: Establish a connection with at least one of the one or more networks within a multi-RAT network; The request is sent to at least one of the one or more networks to access the one or more services and at least one of the one or more slices; as well as Receive a response message indicating either a rejection or acceptance of at least one of the one or more services and one or more slices, along with mapping information.

3. The method according to claim 2, further comprising: Based on the received response message indicating a rejection of at least one of the one or more services and one or more slices, a list of networks and associated Tracking Area Identifier (TAI) RAT and access environment are maintained, the access environment including at least one of Standalone Non-Public Network (SNPN), Reduced Capability REDCAP Network, Terrestrial Network (TN), Non-TN (NTN), Beyond 5G (B5G), and 6G.

4. The method according to claim 3, wherein, The steps of establishing a connection with at least one of the one or more networks within a multi-RAT network include: Identify the location of the UE; and Based on the received request, mapping information, the maintained list of networks, and the location of the UE, at least one of the one or more RATs and the one or more SUPIs is determined.

5. The method according to claim 4, further comprising: Based on response messages or mapping information, identify at least one or more services or slices that are not supported in the current RAT or SUPI; as well as Access to the identified one or more services or slices is achieved by establishing a second connection via the identified one or more RATs and one or more SUPIs.

6. The method according to claim 1, wherein, The mapping information includes at least one of the following: User Equipment Routing Policy (URSP), Access Network Discovery and Selection Policy (ANDSP) or Home Network Configuration or Control Policy for Service- or Slice-Based RAT Selection, Configured Network Slice Selection Assistance Information (NSSAI), Allowed NSSAI, Optional NSSAI, Slice or Service Priority, Information Related to Supported Frequency Bands, SUPI, and the location associated with each of the one or more RATs within a multi-RAT network of a Public Terrestrial Mobile Network (PLMN) / Standalone Non-Public Network (SNPN).

7. The method according to claim 1, wherein, The one or more RATs include a 5G non-terrestrial network NTN or a 5G terrestrial network TN. The priority of the one or more RATs can be pre-configured in at least one of the following: the user-controlled PLMN access technology basic file EFPLMNWACT file, the operator-controlled PLMN access technology basic file EFOPLMNWACT file, the home PLMN selector access technology basic file EFHPLMNWACT file, and the UE's memory element. The priority of the one or more RATs is mapped to one or more services or one or more slices in the mapping information.

8. The method according to claim 1, wherein, The mapping information is pre-configured at the UE.

9. A user equipment (UE) for accessing one or more services in a multiple radio access technology (multiple RAT) network, the UE comprising: At least one processor is configured as follows: Receives requests from one or more applications associated with the UE for access to at least one of one or more services and one or more slices within the multi-RAT network; Based on the mapping information and the received request, at least one of one or more RATs and one or more user permanent identifiers (SUPIs) is determined, wherein the mapping information indicates the relationship between multiple slices and multiple RATs associated with one or more networks within a multi-RAT network and at least one of multiple SUPIs stored at the UE. and Based on the one or more services used for the access request and at least one of the one or more slices, a connection is established with at least one of the one or more networks within the multi-RAT network, and at least one of the one or more RATs and one or more SUPIs.

10. The UE according to claim 9, wherein, The at least one processor is further configured to: Establish a connection with at least one of the one or more networks within a multi-RAT network; The request is sent to at least one of the one or more networks to access the one or more services and at least one of the one or more slices; and Receive a response message indicating either a rejection or acceptance of at least one of the one or more services and one or more slices, along with mapping information.

11. The UE according to claim 9, wherein, The at least one processor is further configured to: Based on the received response message having an indication of rejection of at least one of the one or more services and one or more slices, maintain a list of networks and associated Tracking Area Identifiers (TAI) RATs and access environments, including Standalone Non-Public Networks (SNPN), Reduced Capability REDCAP Networks, Terrestrial Networks (TN), Non-TN (NTN), Beyond 5G (B5G), and 6G.

12. The UE according to claim 11, wherein, The at least one processor is further configured to: Identify the location of the UE; and Based on the received request, mapping information, maintained network list, and UE location, at least one of the one or more RATs and the one or more SUPIs is determined.

13. The UE according to claim 12, wherein, The at least one processor is further configured to: Based on response messages or mapping information, identify at least one or more services or slices that are not currently supported in the RAT or SUPI; and A connection is established via the identified one or more RATs or one or more services to access the identified one or more services or slices.

14. The UE according to claim 9, wherein, The mapping information includes at least one of the following: User Equipment Routing Policy (URSP), Access Network Discovery and Selection Policy (ANDSP) or Home Network Configuration or Control Policy for Service- or Slice-Based RAT Selection, Configured Network Slice Selection Auxiliary Information (NSSAI), Allowed NSSAI, Optional NSSAI, Slice or Service Priority, Information Related to Supported Frequency Bands, SUPI, and the location associated with each of the one or more RATs within a multi-RAT network of a Public Terrestrial Mobile Network (PLMN) / Standalone Non-Public Network (SNPN).

15. The UE according to claim 9, wherein, The one or more RATs include a 5G non-terrestrial network NTN or a 5G terrestrial network TN. The priority of the one or more RATs can be pre-configured in at least one of the following: the user-controlled PLMN access technology basic file EFPLMNWACT file, the operator-controlled PLMN access technology basic file EFOPLMNWACT file, the home PLMN selector access technology basic file EFHPLMNWACT file, and the UE's memory element.

16. The UE according to claim 9, wherein, The priorities of the one or more RATs are mapped to one or more services or one or more slices in the mapping information.

17. The UE according to claim 9, wherein, The mapping information is pre-configured at the UE.

18. A network apparatus for enabling a user equipment (UE) to access one or more services in a multi-radio access technology (RAT) network, the network apparatus comprising: At least one processor is configured as follows: The UE receives a request for access to one or more services and at least one or more slices from a network within a multi-RAT network; and Send a response message indicating either a rejection or acceptance of the received request for at least one of the one or more services and one or more slices, along with mapping information. The mapping information includes at least one of the following: User Equipment Routing Policy (URSP), Access Network Discovery and Selection Policy (ANDSP), policy for home network configuration or control for service- or slice-based RAT selection, configured Network Slice Selection Assistance Information (NSSAI), permitted NSSAI, optional NSSAI, slice or service priority, information related to supported frequency bands, SUPI, and the location associated with each of the one or more RATs in a multi-RAT network within a Public Terrestrial Mobile Network (PLMN) / Standalone Non-Public Network (SNPN).

19. The network device according to claim 18, wherein, The at least one processor is further configured to: Identify the location of the UE; and Based at least on the received request, mapping information, and the location of the user and UE, determine at least one of one or more RATs associated with the network; And guide the UE to establish a connection to at least one of one or more network-based RATs and one or more SUPIs of the UE.

20. The network device according to claim 18, wherein, The mapping information is pre-configured at the UE.

Images