Methods, apparatuses, and computer program products for supporting multiple slices in an overlay underlay networking scenario

Abstract

A method, apparatus, and computer program product are provided for supporting identification and selection of multiple network slices for a remote user equipment. In the context of a method, the method includes receiving a first request from a remote user equipment, the request including a network identifier and requested slice information. The method also includes obtaining, based at least on the network identifier and the requested slice information, a set of slice identifiers including at least one slice identifier, and causing transmission of the set of slice identifiers to the remote user equipment for use in a session.

Description

Technical Field

[0001] The example implementation generally relates to supporting the identification and selection of multiple network slices for remote user equipment. Background Technology

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities (such as user equipment (UE), base stations / access points, network functions (NFs), and / or other nodes) by providing connectivity between various entities involved in the communication path. A communication system can be provided, for example, by means of a communication network and one or more compatible communication devices. Telecommunication networks, such as fifth-generation mobile networks (5G networks), are expected to be the next major phase of mobile telecommunications standards and will bring many improvements to the mobile network user experience. For example, 5G networks should provide new technological solutions to allow for greater throughput, lower latency, higher reliability, higher connectivity, and greater mobility range. In addition to these performance improvements, 5G networks are also expected to expand the flexibility of network use and provide users with a wider range of use cases and business models.

[0003] The 3rd Generation Partnership Project (3GPP) is the standards organization that develops mobile phone protocols and is known for developing and maintaining various standards, including second-generation (2G), third-generation (3G), fourth-generation (4G), Long Term Evolution (LTE), and fifth-generation (5G) standards. 5G networks have been designed as service-based architectures (SBA), where system functions are implemented by a set of network functions (NFs) providing services to other licensed NFs in order to access their services. 5G network systems allow for network slicing, which is an end-to-end logical network supporting a specific set of NFs. In other words, a network slice is a logical network that provides specific network capabilities and characteristics. On a 5G network that includes multiple network slices, a specific network slice can be configured to support specific features not common to all network slices (e.g., hardware specifications, NFs, domain access, etc.). User equipment (UEs) can be configured to access multiple network slices through the same access point.

[0004] Network slice identification is performed via Single Network Slice Selection Assistance Information (S-NSSAI), which is sent to the User Equipment (UE) via signaling messages between the UE and the connected network. The Network Slice Selection Assistance Information (NSSAI) is a collection of S-NSSAIs sent to the UE via signaling messages between the UE and the connected network. A single UE can be served by multiple network slices at a time. The S-NSSAI signaled by the UE to the network helps the network select a specific network slice instance. A network slice instance is a set of NF instances and their required resources (e.g., compute, processing, storage, networking, etc.), forming a deployed network slice. The S-NSSAI is associated with a Public Land Mobile Network (PLMN); for example, the S-NSSAI is configured to indicate the associated PLMN identifier or other ID information, which has a network-specific value or a standard global value. The S-NSSAI is used by the UE to select and access the PLMN associated with the S-NSSAI. Summary of the Invention

[0005] In one embodiment, an apparatus is provided. The apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to receive a first request from a remote user equipment, the request including a network identifier and requested slice information. The at least one memory and the computer program code are also configured, together with the at least one processor, to cause the apparatus to obtain a set of slice identifiers including at least one slice identifier, based at least on the network identifier and the requested slice information. The at least one memory and the computer program code are also configured, together with the at least one processor, to cause the apparatus to cause the slice identifier set to be transmitted to the remote user equipment for use during a relay session.

[0006] In some embodiments, at least one memory and computer program code configured to cause the apparatus to acquire a set of slice identifiers together with at least one processor is further configured to: induce the transmission of a second request to the Access and Mobility Management Function (AMF), the second request including a network identifier and requested slice information; and receive a set of slice identifiers from the AMF, wherein the set of slice identifiers is determined at least based on the network identifier and the requested slice information.

[0007] In some embodiments, the second request includes a Packet Data Unit (PDU) session establishment request, and receiving a set of slice identifiers from the AMF includes receiving a set of slice identifiers as part of a PDU session acceptance message.

[0008] In some embodiments, the second request includes a Packet Data Unit (PDU) session modification request, and receiving a set of slice identifiers from the AMF includes receiving a set of slice identifiers as part of a PDU session modification acceptance message.

[0009] In some embodiments, the second request includes a Private Non-Access Stratum (NAS) message that requests authorization for services provided by the relay remote user equipment.

[0010] In some embodiments, the at least one memory and computer program code are further configured, together with at least one processor, to cause the device to receive a set of slice identifiers and a slice identifier, which will be used to determine a Packet Data Unit (PDU) session for relaying services to a remote user equipment.

[0011] In some embodiments, determining a PDU session includes one of the following: use of an established PDU session for a slice identifier, a request to modify an established PDU session for a slice identifier, or a request to establish a PDU session.

[0012] In some embodiments, at least one memory and computer program code configured to, together with at least one processor, cause the apparatus to acquire a set of slice identifiers are further configured to determine the set of slice identifiers based at least on one or more parameters including one or more slice mapping rules.

[0013] In some embodiments, one or more parameters may further include at least one of the requested slice information and the associated access network capabilities. In some embodiments, the slice mapping rules are received from the Policy Control Function (PCF).

[0014] In some embodiments, the at least one memory and computer program code are further configured, together with at least one processor, to cause the device to trigger the establishment of a PDU session based on one or more parameters.

[0015] In some embodiments, the at least one memory and computer program code are further configured, together with at least one processor, to cause the device to trigger a modification of the PDU session based on one or more parameters.

[0016] In another embodiment, an apparatus is provided. The apparatus includes components for receiving a first request from a remote user equipment, the request including a network identifier and requested slice information. The apparatus further includes components for obtaining a set of slice identifiers, including at least one slice identifier, based at least on the network identifier and the requested slice information. The apparatus also includes components for inducing the transmission of the set of slice identifiers to the remote user equipment for use during a relay session.

[0017] In some embodiments, the components for obtaining the slice identifier set further include components for inducing the transmission of a second request to the Access and Mobility Management Function (AMF), the second request including a network identifier and requested slice information, and components for receiving the slice identifier set from the AMF, wherein the slice identifier set is determined at least based on the network identifier and the requested slice information.

[0018] In some embodiments, the second request includes a Packet Data Unit (PDU) session establishment request, and the component for receiving a set of slice identifiers from the AMF includes a component for receiving the set of slice identifiers as part of a PDU session acceptance message.

[0019] In some embodiments, the second request includes a Packet Data Unit (PDU) session modification request, and wherein the component for receiving a set of slice identifiers from the AMF includes a component for receiving the set of slice identifiers as part of a PDU session modification acceptance message.

[0020] In some embodiments, the second request includes a Private Non-Access Stratum (NAS) message, which requests authorization for relaying services to a remote user equipment.

[0021] In some embodiments, the apparatus further includes components for receiving a set of slice identifiers and slice identifiers that will be used to determine packet data unit (PDU) sessions for relaying services to remote user equipment.

[0022] In some embodiments, determining a PDU session includes one of the following: use of an established PDU session for a slice identifier, a request to modify an established PDU session for a slice identifier, or a request to establish a PDU session.

[0023] In some embodiments, the component for obtaining the set of slice identifiers further includes a component for determining the set of slice identifiers based at least on one or more parameters including one or more slice mapping rules.

[0024] In some embodiments, one or more parameters further include at least one of the following: requested slice information and associated access network capabilities. In some embodiments, the slice mapping rules are received from a policy control function (PCF). In some embodiments, the apparatus further includes components for triggering the establishment of a PDU session based on one or more parameters. In some embodiments, the apparatus further includes components for triggering the modification of a PDU session based on one or more parameters.

[0025] In another embodiment, a method is provided. The method includes receiving a first request from a remote user equipment, the request including a network identifier and requested slice information. The method further includes obtaining a set of slice identifiers, including at least one slice identifier, based at least on the network identifier and the requested slice information. The method also includes causing the set of slice identifiers to be transmitted to the remote user equipment for use during a relay session.

[0026] In some embodiments of the method, obtaining the slice identifier set further includes initiating a transmission of a second request to the Access and Mobility Management Function (AMF), the second request including a network identifier and requested slice information, and receiving the slice identifier set from the AMF, wherein the slice identifier set is determined at least based on the network identifier and the requested slice information. In some embodiments of the method, the second request includes a Packet Data Unit (PDU) session establishment request, and receiving the slice identifier set from the AMF includes receiving the slice identifier set as part of a PDU session acceptance message.

[0027] In some embodiments of the method, the second request includes a Packet Data Unit (PDU) session modification request, and receiving a set of slice identifiers from the AMF includes receiving a set of slice identifiers as part of a PDU session modification acceptance message.

[0028] In some embodiments of the method, the second request includes a Private Non-Access Stratum (NAS) message, which requests authorization for relaying services to a remote user equipment.

[0029] In some embodiments of the method, the method further includes receiving a set of slice identifiers and slice identifiers, which will be used to determine packet data unit (PDU) sessions for relaying services to remote user equipment.

[0030] In some embodiments of the method, determining a PDU session includes one of the following: use of an established PDU session for a slice identifier, a request to modify an established PDU session for a slice identifier, or a request to establish a PDU session.

[0031] In some embodiments of the method, obtaining the set of slice identifiers further includes determining the set of slice identifiers based on at least one or more parameters including one or more slice mapping rules.

[0032] In some embodiments of the method, one or more parameters further include at least one of the following: the requested slice information and the capabilities of the associated access network. In some embodiments of the method, the slice mapping rules are received from the Policy Control Function (PCF).

[0033] In some embodiments of the method, the method further includes triggering the establishment of a PDU session based on one or more parameters. In some embodiments of the method, the method further includes triggering the modification of a PDU session based on one or more parameters.

[0034] In another embodiment, a computer program product is provided. The computer program product includes a non-transitory computer-readable storage medium having a portion of program code stored thereon, the program code portion being configured to, upon execution, receive a first request from a remote user equipment, the request including a network identifier and requested slice information. The program code portion is also configured to, upon execution, obtain a set of slice identifiers including at least one slice identifier based at least on the network identifier and the requested slice information. The program code portion is further configured to, upon execution, cause the set of slice identifiers to be transmitted to the remote user equipment for use during a relay session.

[0035] In some embodiments, the program code portion configured to obtain a set of slice identifiers is further configured to cause a second request to be transmitted to the Access and Mobility Management Function (AMF), the second request including a network identifier and requested slice information, and to receive a set of slice identifiers from the AMF, wherein the set of slice identifiers is determined at least based on the network identifier and the requested slice information.

[0036] In some embodiments, the second request includes a Packet Data Unit (PDU) session establishment request, and receiving a set of slice identifiers from the AMF includes receiving a set of slice identifiers as part of a PDU session acceptance message.

[0037] In some embodiments, the second request includes a Packet Data Unit (PDU) session modification request, and receiving a set of slice identifiers from the AMF includes receiving a set of slice identifiers as part of a PDU session modification acceptance message.

[0038] In some embodiments, the second request includes a Private Non-Access Stratum (NAS) message, which requests authorization for relaying services to a remote user equipment.

[0039] In some embodiments, the program code portion is also configured to receive a set of slice identifiers and a slice identifier at execution time, the slice identifier being used to determine a Packet Data Unit (PDU) session for relaying services to a remote user equipment.

[0040] In some embodiments, determining a PDU session includes one of the following: use of an established PDU session for a slice identifier, a request to modify an established PDU session for a slice identifier, or a request to establish a PDU session.

[0041] In some embodiments, the program code portion configured to cause the device to obtain a set of slice identifiers is further configured to determine the set of slice identifiers based at least on one or more parameters including one or more slice mapping rules.

[0042] In some embodiments, one or more parameters may further include at least one of the following: the requested slice information and the associated access network capabilities. In some embodiments, the slice mapping rules are received from the Policy Control Function (PCF).

[0043] In some embodiments, the program code portion is also configured, when executed, to trigger the establishment of a PDU session based on one or more parameters.

[0044] In some embodiments, the program code portion is also configured, when executed, to trigger modifications to the PDU session based on one or more parameters.

[0045] In another embodiment, an apparatus is provided, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to generate a first request, including a network identifier and requested slice information, based on an internal determination of one or more desired services from an overlay network. The at least one memory and the computer program code are also configured, together with the at least one processor, to cause the apparatus to obtain a set of slice identifiers, including at least one slice identifier, based at least on the network identifier and the requested slice information.

[0046] In some embodiments, at least one memory and computer program code configured to, together with at least one processor, cause the apparatus to acquire a set of slice identifiers are further configured to determine the set of slice identifiers based at least on one or more parameters including one or more slice mapping rules.

[0047] In some embodiments, at least one memory and computer program code configured, together with at least one processor, to cause the apparatus to acquire a set of slice identifiers, is further configured to induce the transmission of a first request to the Access and Mobility Management Function (AMF) and to receive a set of slice identifiers from the AMF, wherein the set of slice identifiers is determined at least based on a network identifier and the requested slice information.

[0048] In another embodiment, an apparatus is provided, comprising components for generating a first request, including a network identifier and requested slice information, based on an internal determination of one or more desired services from an overlay network. The apparatus further comprises components for obtaining a set of slice identifiers, including at least one slice identifier, based at least on the network identifier and the requested slice information.

[0049] In some embodiments, the components for obtaining the slice identifier set further include components for determining the slice identifier set based at least on one or more parameters including one or more slice mapping rules. In some embodiments, the components for obtaining the slice identifier set further include components for initiating the transmission of a first request to the Access and Mobility Management Function (AMF), and components for receiving the slice identifier set from the AMF, wherein the slice identifier set is determined based at least on a network identifier and the requested slice information.

[0050] In another embodiment, a method is provided. The method includes generating a first request, including a network identifier and requested slice information, based on an internal determination of one or more desired services from an overlay network. The method also includes obtaining a set of slice identifiers, including at least one slice identifier, based at least on the network identifier and the requested slice information.

[0051] In some embodiments, obtaining the slice identifier set further includes determining the slice identifier set based on at least one or more parameters including one or more slice mapping rules.

[0052] In some embodiments, obtaining the slice identifier set further includes initiating a transmission of a first request to the Access and Mobility Management Function (AMF) and receiving the slice identifier set from the AMF, wherein the slice identifier set is determined based at least on a network identifier and the requested slice information.

[0053] In another embodiment, a computer program product is provided, comprising a non-transitory computer-readable storage medium having thereon stored a portion of program code configured to, upon execution, generate a first request including a network identifier and requested slice information based on an internal determination of one or more desired services from an overlay network. The program code portion is also configured to, upon execution, obtain a set of slice identifiers including at least one slice identifier based at least on the network identifier and the requested slice information.

[0054] In some embodiments, the program code portion configured to obtain the set of slice identifiers is further configured to determine the set of slice identifiers based at least on one or more parameters including one or more slice mapping rules.

[0055] In some embodiments, the program code portion configured to obtain a set of slice identifiers is further configured to cause a first request to be transmitted to the Access and Mobility Management Function (AMF) and to receive a set of slice identifiers from the AMF, wherein the set of slice identifiers is determined at least based on a network identifier and the requested slice information.

[0056] In another embodiment, an apparatus is provided, comprising at least one processor and at least one memory including computer program code configured, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to generate a request for transmission to another user equipment, the request including a network identifier and requested slice information, and to receive a set of slice identifiers from the user equipment. In some embodiments, the set of slice identifiers is used to generate a slice request for registration with a network via a connection supported by the other user equipment.

[0057] In another embodiment, an apparatus is provided including components for initiating a request to transmit a request to another user equipment, the request including a network identifier and requested slice information, and components for receiving a set of slice identifiers from the user equipment. In some embodiments, the set of slice identifiers is used to generate a slice request for registering with the network via a connection supported by the other user equipment.

[0058] In another embodiment, a method is provided that includes initiating the transmission of a request to another user equipment, the request including a network identifier and requested slice information, and receiving a set of slice identifiers from the user equipment. In some embodiments, the set of slice identifiers is used to generate a slice request to register with the network via a connection supported by the other user equipment.

[0059] In another embodiment, a computer program product is provided, including a non-transitory computer-readable storage medium having a portion of program code stored thereon, the program code portion being configured to, upon execution, cause a request to be transmitted to another user equipment, the request including a network identifier and requested slice information, and receiving a set of slice identifiers from the user equipment. In some embodiments, the set of slice identifiers is used to generate a slice request to register with a network via a connection supported by the other user equipment.

[0060] In another embodiment, an apparatus is provided, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to receive a request from a user equipment for requested slice information including a network identifier and a remote user equipment, and to cause the transmission of a set of slice identifiers to the user equipment, the set of slice identifiers being determined at least based on the network identifier and the requested slice information.

[0061] In some embodiments, the request includes a Packet Data Unit (PDU) session establishment request, and wherein the transmission of the slice identifier set includes the transmission of the slice identifier set as part of a PDU session accept message.

[0062] In some embodiments, the request includes a Packet Data Unit (PDU) session modification request, and the transmission of the slice identifier set includes the transmission of the slice identifier set as part of a PDU session modification acceptance message.

[0063] In some embodiments, the request includes a Private Non-Access Stratum (NAS) message, which requests authorization for relaying remote user equipment.

[0064] In some embodiments, causing the transmission of the slice identifier set to the user equipment includes causing the transmission of the slice identifier set together with the slice identifiers within a Private Non-Access Stratum (NAS) message response that grants authorization for relaying to the remote user equipment.

[0065] In another embodiment, an apparatus is provided. The apparatus includes components for receiving a request from a user equipment (UE) for requesting slice information including a network identifier and remote UE information, and components for inducing the transmission of a set of slice identifiers to the UE, the set of slice identifiers being determined at least based on the network identifier and the requested slice information.

[0066] In some embodiments, the request includes a Packet Data Unit (PDU) session establishment request, and the component for inducing the transmission of the slice identifier set includes a component for inducing the transmission of the slice identifier set as part of a PDU session acceptance message.

[0067] In some embodiments, the request includes a Packet Data Unit (PDU) session modification request, and the component for inducing the transmission of a set of slice identifiers includes a component for inducing the transmission of the set of slice identifiers as part of a PDU session modification accept message.

[0068] In some embodiments, the request includes a Private Non-Access Stratum (NAS) message, which requests authorization for relaying remote user equipment.

[0069] In some embodiments, the components for inducing the transmission of the slice identifier set to the user equipment include components for inducing the transmission of the slice identifier set together with the slice identifiers within a Private Non-Access Stratum (NAS) message response, which grants authorization for relaying to the remote user equipment.

[0070] In another embodiment, a method is provided that includes receiving a request from a user equipment including a network identifier and requested slice information of a remote user equipment, and causing a set of slice identifiers to be transmitted to the user equipment, the set of slice identifiers being determined at least based on the network identifier and the requested slice information.

[0071] In some embodiments, the request includes a Packet Data Unit (PDU) session establishment request, wherein the transmission of the slice identifier set includes the transmission of the slice identifier set as part of a PDU session accept message. In some embodiments, the request includes a Packet Data Unit (PDU) session modification request, and the transmission of the slice identifier set includes the transmission of the slice identifier set as part of a PDU session modification accept message. In some embodiments, the request includes a Private Non-Access Stratum (NAS) message requesting authorization for relaying to a remote user equipment.

[0072] In some embodiments, causing the transmission of the slice identifier set to the user equipment includes causing the transmission of the slice identifier set together with the slice identifiers within a Private Non-Access Stratum (NAS) message response that grants authorization for relaying to the remote user equipment.

[0073] In another embodiment, a computer program product is provided, including a non-transitory computer-readable storage medium having a portion of program code stored thereon, the program code portion being configured to, upon execution, receive a request from a user equipment including a network identifier and requested slice information of a remote user equipment, and to cause the transmission of a set of slice identifiers to the user equipment, the set of slice identifiers being determined at least based on the network identifier and the requested slice information.

[0074] In some embodiments, the request includes a Packet Data Unit (PDU) session establishment request, and wherein the transmission of the slice identifier set includes the transmission of the slice identifier set as part of a PDU session accept message.

[0075] In some embodiments, the request includes a Packet Data Unit (PDU) session modification request, and the transmission of the slice identifier set includes the transmission of the slice identifier set as part of a PDU session modification acceptance message.

[0076] In some embodiments, the request includes a Private Non-Access Stratum (NAS) message, which requests authorization for relaying remote user equipment.

[0077] In some embodiments, causing the transmission of the slice identifier set to the user equipment includes causing the transmission of the slice identifier set together with the slice identifiers within a Private Non-Access Stratum (NAS) message response that grants authorization for relaying to the remote user equipment.

[0078] In another embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to transmit one or more slice mapping rules to a user equipment. In some embodiments, the apparatus is a policy control function (PCF).

[0079] In another embodiment, an apparatus is provided that includes components for inducing the transmission of one or more slice mapping rules to a user equipment. In some embodiments, the apparatus is a policy control function (PCF).

[0080] In another embodiment, a method is provided that includes transmitting one or more slice mapping rules to a user equipment via a device. In some embodiments, the device is a policy control function (PCF).

[0081] In another embodiment, a computer program product is provided, including a non-transitory computer-readable storage medium having a portion of program code stored thereon, the program code portion being configured to cause the transmission of one or more slice mapping rules to a user device upon execution. In some embodiments, the means is a policy control function (PCF). Attached Figure Description

[0082] Embodiments of this disclosure have been described in general terms in this manner. Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0083] Figure 1 An example architecture for a communication network according to an example embodiment of the present disclosure is shown;

[0084] Figure 2 An example protocol stack according to an example embodiment of this disclosure is shown;

[0085] Figure 3A An example access to a Public Land Mobile Network (PLMN) service via a Standalone Non-Public Network (SNPN) is illustrated according to an example embodiment of the present disclosure;

[0086] Figure 3B An example access to SNPN services via PLMN is shown according to an example embodiment of this disclosure;

[0087] Figure 4 A block diagram of an apparatus specifically configured according to exemplary embodiments of the present disclosure is shown;

[0088] Figure 5 This is a flowchart illustrating the operations performed according to an example embodiment;

[0089] Figure 6A This is a flowchart illustrating the operations performed according to an example embodiment;

[0090] Figure 6B This further illustrates the example embodiment in Figure 6A Signal diagram of the operations performed in the process;

[0091] Figure 7A This is a flowchart illustrating the operations performed according to an example embodiment; and

[0092] Figure 7B This further illustrates the example embodiment in Figure 7A Signal diagram of the operations performed in the process. Detailed Implementation

[0093] Some embodiments of the invention will now be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, embodiments of the invention. In fact, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Unless otherwise stated, the term “or” has both alternative and conjunctional meanings herein. The terms “illustrative” and “exemplary” refer to examples without an indication of quality level. The same reference numerals refer to the same elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms are used interchangeably to refer to data that can be transmitted, received, and / or stored according to embodiments of the invention. Therefore, the use of any such terms should not be considered as limiting the spirit and scope of the embodiments of the invention.

[0094] Furthermore, as used herein, the term "circuit system" means (a) a hardware circuit implementation (e.g., an implementation in an analog circuit system and / or a digital circuit system); (b) a combination of circuitry and (multiple) computer program products comprising software and / or firmware instructions stored on one or more computer-readable storage media, which work together to cause a device to perform one or more functions described herein; and (c) a circuit, such as (multiple) microprocessors or a portion thereof, which requires software or firmware to operate even if the software or firmware is not physically present. This definition of "circuit system" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit system" also includes implementations of one or more processors and / or (multiple) portions thereof, along with accompanying software and / or firmware. As yet another example, the term "circuit system" as used herein also includes, for example, baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network devices, other network devices, and / or other computing devices.

[0095] Furthermore, as used herein, the terms "node," "entity," "mediator," "intermediary entity," "medium," and similar terms may be used interchangeably to refer to a computer or a program running on one or more networks connected via one or more networks capable of creating, modifying, deleting, transmitting, receiving, and / or storing data according to embodiments of the invention. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of the invention.

[0096] Furthermore, as used herein, the terms "user equipment," "user device," "device," "apparatus," "mobile device," "personal computer," "laptop," "laptop computer," "desktop computer," "mobile phone," "tablet computer," "smartphone," "smart device," "phone," "computing device," "communication device," "user communication device," "terminal," and similar terms may be used interchangeably to refer to apparatus according to certain embodiments of this disclosure, such as apparatus embodied in a computing device configured to access one or more networks, at least for the purpose of wired and / or wireless transmission of communication signals. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of this disclosure.

[0097] Furthermore, as used herein, the terms “network slice,” “specific slice,” “slice,” “network portion,” “disjoint slice,” “isolated slice,” and similar terms may be used interchangeably to refer to an end-to-end logical communication network or a portion thereof within a Public Land Mobile Network (PLMN), a Standalone Non-Public Network (SNPN), a Public Network Integration NPN (PNI-NPN), etc.

[0098] As used herein, “computer-readable storage medium” (which refers to a non-transitory physical storage medium, such as a volatile or non-volatile memory device) can be distinguished from “computer-readable transmission medium,” which refers to an electromagnetic signal. Such media can take many forms, including, but not limited to, non-transitory computer-readable storage media (e.g., non-volatile media, volatile media) and transmission media. Transmission media include, for example, coaxial cables, copper wires, fiber optic cables, and carrier waves that travel through space without wires or cables, such as sound waves and electromagnetic waves, including radio waves, light waves, and infrared radiation. Signals include artificial transient variations in amplitude, frequency, phase, polarization, or other physical characteristics transmitted through the transmission medium.

[0099] Examples of non-transitory computer-readable media include magnetic computer-readable media (e.g., floppy disks, hard disks, magnetic tapes, any other magnetic media), optical computer-readable media (e.g., optical disc read-only memory (CD-ROM), digital versatile disc (DVD), Blu-ray disc (BD), etc., or combinations thereof), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), FLASH-EPROM, or any other non-transitory media from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium other than a transmission medium. However, it should be understood that while embodiments are described as using computer-readable storage media, in alternative embodiments, other types of computer-readable media may be used in place of or as a supplement to computer-readable storage media.

[0100] In the following explanation, certain embodiments are described with reference to communication devices capable of communicating via wired and / or wireless networks and communication systems serving such communication devices. Before explaining these exemplary embodiments in detail, refer to... Figures 1-4 Briefly explain some general principles of wired and / or wireless communication systems, their access systems, and communication equipment to aid in understanding the underlying technologies of the described examples.

[0101] According to some embodiments, communication devices or terminals may be provided for wireless access via cells, base stations, access points, etc. (e.g., wireless transmitters and / or receiver nodes providing access points for radio access communication systems and / or other forms of wired and / or wireless networks) or combinations thereof. Such wired and / or wireless networks include, but are not limited to, networks configured to conform to 2G, 3G, 4G, LTE, 5G and / or any other similar or future communication network standards to be developed. This disclosure contemplates that any method, apparatus, computer program code, and any part or combination thereof may also be implemented using communication networks and associated standards that have not yet been developed, as will be developed in the future and as understood by those skilled in the art based on this disclosure.

[0102] Access points and the communications therethrough are typically controlled by at least one suitable control device to enable their operation and the management of mobile communication devices communicating with them. In some embodiments, the control device for a node may be integrated with, coupled to, and / or otherwise provided for controlling the access point. In some embodiments, the control device may be arranged to allow communication between a user device and a core network or a network entity of the core network. For this purpose, the control device may include at least one memory, at least one data processing unit (such as a processor), and input / output interfaces (e.g., GPS receiver / transmitter, keyboard, mouse, touchpad, display, Universal Serial Bus (USB), Bluetooth, Ethernet, wired / wireless connection, etc., or combinations thereof).

[0103] Furthermore, the control device can be coupled to other relevant components of the access point via an interface. The control device can be configured to execute appropriate software code to provide control functions. It should be understood that similar components can be housed in control devices located elsewhere in the network system, such as in core network entities. The control device can interconnect with other control entities. Control devices and functions can be distributed among several control units. In some embodiments, each base station may include a control device. In alternative embodiments, two or more base stations may share a control device.

[0104] Access points and associated controllers can communicate with each other via fixed lines and / or via radio interfaces. Logical connections between base station nodes can be provided, for example, via XN interfaces, N2 interfaces, similar interfaces, or combinations thereof. These interfaces can be used, for example, for coordinating station operations and performing reselection or handover operations. The logical communication connection between the initial and final communication nodes of the network can include multiple intermediate nodes. Furthermore, any node can be added to or removed from the logical communication connection as needed to establish and maintain network functional communications.

[0105] Communication equipment or user equipment may include any suitable device capable of receiving at least communication signals including data. Communication signals may be transmitted via a wired connection, a wireless connection, or a combination thereof. For example, the device may be a handheld data processing device equipped with a radio receiver, data processing, and a user interface. Non-limiting examples include mobile stations (MS) (such as mobile phones or so-called "smartphones"), portable computers (such as laptops or tablets) equipped with wireless interface cards or other wireless interface facilities, personal data assistants (PDAs) equipped with wireless communication capabilities, or any combination thereof. Further examples include wearable wireless devices (such as devices integrated with watches or smartwatches, glasses, helmets, hats, clothing, headphones with wireless connectivity, jewelry, etc.), universal serial bus (USB) sticks with wireless capabilities, modem data cards, machine-type devices, or any combination thereof.

[0106] In some embodiments, a communication device, such as one configured to communicate with a wireless network or core network entity, can be exemplified by a handheld or other mobile communication device or user equipment. The mobile communication device may be provided with wireless communication capabilities and suitable electronic control means for enabling its operation. Therefore, the communication device may be provided with at least one data processing entity (e.g., a central processing unit and / or core processor), at least one memory, and other possible components, such as additional processors and memory for software and hardware-assisted execution of the tasks it is designed to perform. Data processing, storage, and other related control means may be disposed on suitable circuit boards and / or chipsets.

[0107] The data processing and storage functions provided by the control device of the communication device are configured to induce control and signaling operations according to certain embodiments described later in this specification. Users can control the operation of the communication device by means of a suitable user interface, such as a touch-sensitive display or keyboard and / or keypad, one or more actuator buttons, voice commands, combinations thereof, etc. A speaker and microphone are typically also provided. Furthermore, the mobile communication device may include suitable connectors (wired or wireless) for connecting external accessories (e.g., hands-free devices) to other devices.

[0108] In some embodiments, the communication device can wirelessly communicate via one or more suitable means for receiving and transmitting signals (e.g., a GPS receiver / transmitter, a remote touchpad interface with a remote display, a Wi-Fi interface, etc.). In some embodiments, a radio unit can be connected to the control device of the device. The radio unit may include a radio section and an associated antenna arrangement. The antenna arrangement may be located inside or outside the communication device.

[0109] The embodiments described herein can relate to several types of deployments. One type of deployment can be a device-to-device (D2D) deployment, which can use a Layer 3 user equipment (UE) to a network relay (relay UE), allowing a remote user equipment (or UE) to access its service network (referred to herein as the "overlay network") through the relay UE and the relay UE's service network (referred to herein as the "underlying network").

[0110] Another example of a deployment type could be a Standalone Non-Public Network (SNPN) deployment, which allows a UE to reach its PLMN (overlay network in this example) via the SNPN (the underlying network in this example). Although these deployments have different use cases, the embodiments described herein regarding slice selection can be similar in both types of deployments.

[0111] Figure 1 An exemplary Layer 3 UE-to-network relay architecture as described above is illustrated. In some embodiments, the 5G core network (5GC) serving the relay UE and the 5GC serving the remote UE may correspond to the same 5GC network. In some embodiments, the 5GC serving the relay UE and the 5GC serving the remote UE may correspond to different networks. For example, in Figure 1 In this context, the (serving and home) 5GC of a remote UE can be on a different network than the (serving and home) 5GC of a relay UE. Furthermore, in... Figure 1 In this context, the User Plane Function (UPF) (for a relay UE) can represent the Packet Data Unit (PDU) Session Anchor Point (PSA) of the relay UE, and the UPF (for a remote UE) can represent the Packet Data Unit (PDU) Session Anchor Point (PSA) of the remote UE.

[0112] Figure 2 It shows the relationship with Figure 1 The example protocol stack corresponding to the architecture model. In this regard, Figure 2 An example protocol stack for a 5G UE to network L3 relay solution using non-3GPP interoperability function (N3IWF) is shown.

[0113] Figure 3A and Figure 3B Several example deployments using SNPN are shown. Figure 3A An example access to PLMN services via SNPN is shown, while Figure 3B An example access to the SNPN service via PLMN is shown.

[0114] In some examples, a remote UE (in both D2D and SNPN deployments) may want to access two slices (e.g., slice "A" and slice "B") at the overlay network (e.g., the network that actually provides services to the remote UE). However, the remote UE may need connectivity of the underlying network in order to reach the N3IWF that provides access to its overlay network.

[0115] In order to reach the N3IWF through the underlying network, a PDU session needs to be established at the underlying network. Regardless of the slice used or the number of PDU sessions, the PDU session is unique and associated with a slice from the underlying network that best meets the requirements of the slice (e.g., slices "A" and "B") that the remote UE wishes to access.

[0116] In this regard, the embodiments described herein describe a solution to the problem of which slice to request from a relay UE (or intermediate network in the case of SNPN deployment) to establish a PDU session to reach the N3IWF. In other words, if a remote UE wishes to register to the overlay network using the requested NSSAI (“A” and “B”), the embodiments herein can determine which slice should be requested from the underlying network.

[0117] For example, a remote UE cannot determine whether the required NSSAI(s) are supported in a relay network in a D2D scenario and / or in an underlying network in a non-public network (NPN) scenario. In this regard, the embodiments herein introduce a signaling mechanism that allows a remote UE to reduce its NSSAI(s) to a subset for use in its registration toward the overlay network (remote network in a D2D scenario), a subset of NSSAI(s) that is also acceptable in a relay network in a D2D scenario and / or in an underlying network in an NPN scenario.

[0118] It should be understood that some of the example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise incorporate a fifth-generation (5G) architecture. Although Figure 1 Figure 3 illustrates various configurations and / or components of an example architecture for a communication network, but within the scope of this disclosure, many other systems, system configurations, networks, network entities, and paths / protocols used for communication therein are conceivable.

[0119] Although the methods, devices / apparatus, and computer program products / code described herein are described in the context of fifth-generation core networks (5GC) and systems, such as Figures 1-3BAs shown and described above, the methods, apparatus, and computer program products described can still be applied in a broader context within any suitable telecommunications system, network, standard, and / or protocol. It will be appreciated that the described methods, apparatus, and computer program products can be further applied to future networks and systems that have not yet been developed, as will be clear to those skilled in the art.

[0120] Turn now Figure 4 According to exemplary embodiments of this disclosure, examples of apparatuses that may be embodied by user equipment or network entities (such as servers or other computing devices) are depicted. As described below in conjunction with the flowcharts and block diagrams presented herein, apparatus 400 of the exemplary embodiments can be configured to perform the functions described herein. In any case, apparatus 400 can generally be embodied by a computing device, such as a server, personal computer, computer workstation, or other type of computing device, including computing devices used as components of user equipment and / or wireless networks or wireless local area networks. Regardless of how apparatus 400 is embodied, the apparatuses of the exemplary embodiments can be as follows: Figure 4 The configuration shown includes a processor 402 and a memory device 404, and in some embodiments includes and / or includes a communication interface 406 associated with or otherwise communicating with it.

[0121] Although not shown, the apparatus of the example embodiments may optionally include a user interface, such as a touchscreen, display, keyboard, etc., or combinations thereof. Furthermore, the apparatus according to the example embodiments may be configured with a global positioning circuit, which includes a global positioning receiver and / or a global positioning transmitter configured to communicate with one or more global navigation satellite systems (e.g., GPS, GLONASS, Galileo, etc., or combinations thereof). The global positioning circuit may be configured for the direct / indirect transmission and / or reception of satellite and / or cell signals to determine geographic location data (e.g., latitude, longitude, elevation, altitude, geographic coordinates, etc., or combinations thereof) of the apparatus and / or another communication device associated with the apparatus or one or more global navigation satellite systems. In some embodiments, the geographic location data may include a time dimension, such as a timestamp that associates the geographic location data with a corresponding time (e.g., 01:00 Eastern Time, etc.), a corresponding date (e.g., September 26, 2020, etc.). The time dimension may be configured based on one or more of the times of receiving, generating, transmitting, etc., by the apparatus. In some embodiments, the geographic location data may be associated with one or more time dimensions.

[0122] Processor 402 (and / or coprocessor or auxiliary processor or any other circuitry otherwise associated with the processor) may communicate with memory device 404 via a bus to transfer information between components of device 400. The memory device may include, for example, one or more volatile and / or non-volatile memories, such as non-transitory memory devices. In other words, for example, the memory device may be an electronic storage device (e.g., a computer-readable storage medium) including gates configured to store data (e.g., bits) that can be retrieved by a machine (e.g., a computing device, such as a processor). The memory device may be configured to store information, data, content, applications, instructions, etc., or combinations thereof, enabling the device to perform various functions according to example embodiments. For example, the memory device may be configured to buffer input data for processor processing. Additionally or alternatively, the memory device may be configured to store instructions for processor execution.

[0123] In some embodiments, device 400 may be embodied in various computing devices as described above. However, in some embodiments, the device may be embodied as a chip or chipset. In other words, the device may include one or more physical packages (e.g., chips) that include materials, components, and / or wires on a structural component (e.g., a substrate). The structural component may provide physical strength, dimensional conservation, and / or electrical interaction constraints for the component circuitry systems included thereon. Thus, in some cases, the device may be configured to implement embodiments of the invention on a single chip or as a single “system-on-a-chip.” Thus, in some cases, a chip or chipset may constitute components for performing one or more operations to provide the functions described herein.

[0124] Processor 402 can be embodied in a variety of different ways. For example, a processor can be embodied as one or more of a variety of hardware processing units, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing element with or without an accompanying DSP, or various other circuit systems including integrated circuits, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc. Thus, in some embodiments, the processor may include one or more processing cores configured to execute independently. Multi-core processors can implement multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in series via a bus to implement independent execution of instructions, pipelines, and / or multiple threads.

[0125] In one example embodiment, processor 402 may be configured to execute instructions stored in memory device 404 or instructions otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to perform hard-coded functions. Thus, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in a circuit system) capable of performing operations according to embodiments of this disclosure simultaneously with the appropriate configuration. Therefore, for example, when the processor is embodied as an ASIC, FPGA, etc., or a combination thereof, the processor may be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a particular device (e.g., an encoder and / or decoder) configured to further configure the processor to employ embodiments of the invention through instructions for performing the algorithms and / or operations described herein. The processor may include clocks, arithmetic logic units (ALUs), and logic gates, etc., configured to support processor operation.

[0126] In embodiments including communication interface 406, the communication interface can be any component, such as a device or circuitry embodied in hardware or a combination of hardware and software, configured to receive data from and / or transmit data to a network and / or any other device or module communicating with device 400, such as network functions, network repository functions, base stations, access points, serving communication proxies, UEs, radio access networks (RANs), core network services, AS / AFs, databases or other storage devices, or combinations thereof. In this regard, the communication interface may include, for example, one or more antennas and supporting hardware and / or software for implementing communication with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with one or more antennas to induce the transmission of signals via one or more antennas or the processing of the reception of signals received via one or more antennas.

[0127] In some embodiments, one or more antennas may include one or more of the following: dipole antenna, monopole antenna, helical antenna, loop antenna, waveguide, horn antenna, parabolic reflector, corner reflector, dish antenna, microstrip patch array, convex plane, concave plane, convex-convex lens, concave-concave lens, etc., or combinations thereof. In some environments, the communication interface may alternatively or additionally support wired communication. Thus, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), USB, etc., or combinations thereof.

[0128] As shown, device 400 may include processor 402, which communicates with memory 404 and is configured to provide signals to and receive signals from communication interface 406. In some embodiments, communication interface 406 may include a transmitter and a receiver. In some embodiments, processor 402 may be configured to at least partially control the functions of device 400. In some embodiments, processor 402 may be configured to control the functions of a transmitter and receiver by implementing control signaling via electrical leads to the transmitter and receiver. Similarly, processor 402 may be configured to control other elements of device 400 by implementing control signaling via electrical wires connecting processor 402 to other elements such as a display or memory 404.

[0129] Device 400 is capable of operating using one or more air interface standards, communication protocols, modulation types, access types, etc. Signals transmitted and received by processor 402 may include signaling information according to the air interface standards of the applicable cellular system and / or any number of different wired or wireless network technologies, including but not limited to Wi-Fi, Wireless Local Access Network (WLAN) technologies (such as IEEE 802.11, 802.16, 802.3), Asymmetric Digital Subscriber Line (ADSL), Cable Data Service Interface Specification (DOCSIS), etc., or combinations thereof. Furthermore, these signals may include voice data, user-generated data, user-requested data, etc., or combinations thereof.

[0130] For example, the cellular modem in device 400 and / or therein may be able to operate according to various first-generation (1G) communication protocols, second-generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), or combinations thereof. For example, device 400 may be able to operate according to 2G wireless communication protocol provisional standard (IS) 136 (IS-136), Time Division Multiple Access (TDMA), GSM, IS-95, Code Division Multiple Access, Code Division Multiple Access (CDMA), or combinations thereof. Furthermore, for example, device 400 may be able to operate according to 2.5G wireless communication protocols such as GPRS, Enhanced Data GSM Environment (EDGE), or combinations thereof.

[0131] Furthermore, for example, device 400 may be able to operate according to 3G wireless communication protocols, such as UMTS, Code Division Multiple Access 4000 (CDMA4000), Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), or combinations thereof. NA400 may also be able to operate according to 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), or combinations thereof.

[0132] Furthermore, for example, device 400 may be able to operate according to 4G wireless communication protocols (such as Advanced LTE), 5G, and similar wireless communication protocols that may be developed subsequently. In some embodiments, device 400 may be able to operate according to or within any suitable CUPS architecture, such as for gateway GGSN-C, TWAG-C, Broadband Network Gateway (BNG), N4 interface, Sxa interface, Sxb interface, Sxc interface, EPC SGW-C, EPC PGW-C, EPC TDF-C, and combinations thereof. In fact, although operation in conjunction with 5G systems is described herein, the device and method can be configured to operate in conjunction with many other types of systems, including those developed and implemented below.

[0133] Some embodiments disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on memory 404, processor 402, or electronic components. In some example embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable medium" can be any non-transitory medium that can contain, store, transmit, propagate, or transfer instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as a computer or data processor circuit system), for example, [examples would be inserted here]. Figure 4 As shown. Computer-readable media can include non-transitory computer-readable storage media, which can be any medium that can contain or store instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as a computer).

[0134] In some embodiments, such as those with a Layer 3 UE-to-network relay deployment, a remote UE can send a request to a relay UE via PC5 to obtain connectivity. PC5 refers to a reference point through which the UE communicates directly with another UE via a direct channel. In this case, communication with the base station may not be necessary.

[0135] In some embodiments, a request sent by a remote UE may include a PLMN identifier (ID) indicating a specific PLMN, such as the home PLMN identifier of the remote UE. The request may also include a pre-defined requested NSSAI. The pre-defined requested NSSAI may include a list of all S-NSSAIs that the remote UE intends to present as the requested NSSAI within a NAS registration request message sent by the remote UE to the overlay network (e.g., 5GC, Access and Mobility Management Function (AMF)).

[0136] In one embodiment, one or more slice mapping rules configured at the relay UE can be used to convert the expected requested NSSAI received from the remote UE via PC5, along with the remote UE's home PLMN identifier, into a unique S-NSSAI (Data Network Name (DNN), S-NSSAI). This unique S-NSSAI is used by the relay UE to a PDU session for relay services of the remote UE via the relay 5GC. This may require the relay UE to establish a new PDU session or modify an existing PDU session.

[0137] In one embodiment, the relay UE may have already received these slice mapping rules from the policy control function (PCF) of the network serving the relay UE.

[0138] In another embodiment, the relay UE may send a request (e.g., via NAS) to its associated AMF to convert the expected requested NSSAI and the home PLMN identifier of the remote UE into a unique S-NSSAI. This unique S-NSSAI can be used by a PDU session, which will be used by the relay UE for the relay services of the remote UE. This may require the relay UE to establish a new PDU session or modify an existing one.

[0139] In any of the embodiments described above, the relay UE's subscription and / or its access to the overlay network may not allow support for all slices within the expected requested NSSAI received from the remote UE. The relay UE can respond to the remote UE using slices of the remote UE that can be supported by the relay UE and its serving network (e.g., NSSAIs allowed for relaying). Based on this, when issuing a registration request to the overlay network, the remote UE can cut slices from its list of expected requested NSSAIs. In other words, for slices not supported by the underlying network, the remote UE does not need to include the S-NSSAI in the registration request sent to the overlay network.

[0140] In some embodiments, a request from a relay UE to its AMF (e.g., via NAS) to convert a anticipated requested NSSAI received from a remote UE into a unique S-NSSAI for a PDU session may include a NAS PDU session establishment (or modification), whereby the relay UE provides its (home) PLMN ID and the anticipated requested NSSAI received from the remote UE, instead of the S-NSSAI. The AMF may consider the home PLMN ID and the anticipated requested NSSAI received from the relay UE and select an appropriate S-NSSAI for the PDU session. The selected S-NSSAI is provided to the Session Management Function (SMF) and included as part of a PDU session acceptance message sent to the relay UE. The PDU session acceptance message may also include an NSSAI permitted for relaying, which is propagated by the relay UE to the remote UE in a PC5 response.

[0141] In some embodiments, a request from a relay UE to its AMF (e.g., via NAS) for converting a requested NSSAI received from a remote UE into a unique S-NSSAI for a PDU session may include a dedicated NAS message requesting authorization for relaying the remote UE using the requested NSSAI received from the remote UE via PC5.

[0142] In some embodiments, such as in embodiments having the following deployment: such as Figure 3A and Figure 3B As shown in the SNPN access via PLMN and PLMN access via SNPN, the UE may need to have a PDU session on the underlying network in order to reach the requested NSSAI of the overlay network. In one such embodiment, a slice mapping rule configured in the UE can convert the requested NSSAI of the overlay network into a unique S-NSSAI of the PDU session that the UE wants to use on the underlying network.

[0143] In one embodiment, the UE may have already received these slice mapping rules from the underlying network's PCF.

[0144] In another embodiment, the UE may request (e.g., via NAS) its AMF in the underlying network to convert the anticipated requested NSSAI into a unique S-NSSAI for the PDU session the UE intends to use over the underlying network. In either case, the relay UE's subscription and / or its access capabilities to the overlay network may not allow support for all slices within the anticipated requested NSSAI. Based on slice mapping rules or AMF responses, the UE may need to remove slices from its list of anticipated requested S-NSSAIs when issuing a registration request to the overlay network. Slice mapping rules may need to take into account the UE's HPLMN in order to convert overlay network slices.

[0145] Furthermore, in the embodiments described above, rules can be used to emphasize support for the most requested slice of the expected NSSAI sent by a remote UE, or, in the case of SNPN, support for the most requested slice that the UE wishes to access through its overlay network. For example, one such rule could be that if a (remote) UE requests both an eMBB slice and a URLLC slice, then the PDU session of the relay UE (or the underlying network) for the relevant services of the (remote) UE must correspond to the URLLC slice. As another example rule, if a remote UE requests both an eMBB slice and a Cellular Internet of Things (CIoT) slice, then the PDU session of the relay UE (or the underlying network) for the relay services of the remote UE must correspond to the CIoT slice.

[0146] In some embodiments, if a rule indicates that relay slice R1 (S-NSSAI) can be used for slices X1 and X2 of a remote UE's HPLMN, and the relay UE has a subscription to relay slice R1, then the relay UE can provide access to slices X1 and X2 for the remote UE of that HPLMN. In some embodiments, such slice mapping rules can be configured by the relay UE's Policy Control Function (PCF) and run within the relay UE. In other embodiments, such rules can correspond to local AMF policies.

[0147] Go to Figure 5In operation 501, apparatus 400 includes components such as processor 402 and communication interface 406 configured to receive a first request from a remote user equipment, the request including a network identifier and requested slice information. For example, the network identifier could be a PLMN identifier (PLMN ID). The requested slice information could include a requested NSSAI. In this respect, apparatus 400 could be embodied by a relay UE. As described above, the requested NSSAI could include a list of all S-NSSAIs that will be presented as the requested NSSAI within a NAS registration request message, and the remote UE plans to send the NAS registration request message to the overlay network (the remote UE's 5GC / AMF).

[0148] In some embodiments, it can be assumed that the relay UE has already registered for itself. The relay UE may also have already acquired a service (PDU session) for itself. In this respect, relay UE registration can allow the UE to access a slice (S-NSSAI) of services that are eligible to support (multiple) remote UEs.

[0149] Similarly, in deployments involving SNPN, it can be assumed that the UE has already registered itself on the underlying network. The UE may also have already obtained services (PDU sessions) from the underlying network. UE registration with the underlying network allows the UE to access slices (S-NSSAI) that are eligible to support services directed toward the overlay network.

[0150] In some embodiments, the first request may be a request that includes an attempt to establish a PC5 connection to the relay UE. In this regard, during PC5 establishment, the remote UE may provide its PLMN ID and its expected requested NSSAI. It should be understood that the remote UE can discover the relay UE in any manner. Similarly, in deployments involving SNPN, the first request may correspond to internal detection within the UE, i.e., the UE requires services from the overlay network and the expected requested NSSAI associated with those services.

[0151] In operation 502, device 400 includes components such as processor 402, communication interface 406, memory 404, etc., configured to acquire a set of slice identifiers (e.g., NSSAI) including at least one slice identifier (e.g., S-NSSAI) based at least on a network identifier and requested slice information. For example, device 300 may acquire a first slice identifier (S-NSSAI) for a PDU session and a set of slice identifiers (NSSAI) permitted for relaying.

[0152] As described above, obtaining the slice identifier set (and the S-NSSAI of the PDU session) can be achieved in several ways, such as through... Figure 6A and Figure 7A Any of the methods shown.

[0153] Briefly turn Figure 6A In method 600, at operation 601, apparatus 400 includes components configured to initiate the transmission of a second request to the AMF, such as processor 402, communication interface 406, etc., the second request including a network identifier and expected requested slice information. In this regard, a relay UE can contact its AMF and send a second request providing the expected requested NSSAI and PLMN ID provided by a remote UE. In some embodiments, the second request may include PDU session establishment or modification. Such a request may also include a request for authorization to relay for a remote UE, wherein parameters include the PLMN ID and the expected requested NSSAI. Similarly, in deployments involving SNPN, a UE can contact its (underlying network's) AMF and send a second request providing the PLMN ID and the expected requested NSSAI. In some embodiments, the second request may include PDU session establishment or modification.

[0154] In the embodiments described herein, NAS may be exchanged only between the relay UE and its serving network. In this respect, once Figure 5 The method has been implemented, allowing the remote UE to exchange NAS only with its serving network.

[0155] Once the AMF receives the second request, and based at least on the local configuration and the relay UE subscription, the AMF can determine the S-NSSAI to be used by the relay UE to carry the services of the remote UE within the underlying network, and the corresponding NSSAI to be provided back to the remote UE for relaying within the overlay network. The AMF can then proceed with establishing (or modifying) a PDU session with the selected S-NSSAI. Similarly, for SNPN deployments, once the AMF of the underlying network receives the second request, and based at least on the local configuration and the UE subscription (for the underlying network), the AMF can determine the S-NSSAI to be used by the UE to carry services to the overlay network within the underlying network, and the corresponding NSSAI to be provided back to the UE for relaying within the overlay network. The AMF can then proceed with establishing (or modifying) a PDU session with the selected S-NSSAI within the underlying network.

[0156] In operation 602, device 400 includes components such as processor 402, communication interface 406, etc., configured to receive a set of slice identifiers from AMF, the set of slice identifiers being based at least on network identifiers and expected requested slice information.

[0157] In this regard, the AMF responds to requests sent by relay UEs to provide information about the PDU session established (or modified) for the remote UE in the underlying network, the S-NSSAI used to establish the PDU session for relaying services, and the corresponding NSSAI of the overlay network permitted for relaying to be provided back to the remote UE. The process can then continue to... Figure 5 Operation 503, wherein apparatus 400 includes components configured to cause the transmission of a slice identifier set to a remote user equipment for use in a session (e.g., a PDU session), such as processor 402, communication interface 406, etc. In this regard, the relay UE can provide an NSSAI that allows the overlay network used for relaying. Similarly, for SNPN deployment, the AMF can respond to a request sent by the UE to provide information about the PDU session established (or modified) for the UE in the underlying network, the S-NSSAI for the PDU session established for relaying services, and the corresponding NSSAI that allows the overlay network used for relaying. The process can then continue to... Figure 5 Operation 503, wherein the apparatus 400 includes components configured to cause the transmission of a set of slice identifiers within the UE for use by the UE when accessing the overlay network, such as processor 402, communication interface 406, etc.

[0158] In some embodiments, when a registration request is made to the overlay network (at a later time), the remote UE can then cut slices from the slice information of its original request. After this cutting, registration and authentication toward the overlay network (the remote network in the case of D2D) can proceed normally; however, there may be a reduced set of NSSAIs that have already been verified with the relay network (in the case of D2D) or the underlying network (in the case of NPN). Similarly, for SNPN deployments, in some embodiments, when a registration request is made to the overlay network (at a later time), the UE can then cut (e.g., remove) slices from the slice information of its original request. After this cutting, registration and authentication toward the overlay network can proceed normally; however, there may be a reduced set of NSSAIs that have already been verified with the underlying network.

[0159] Figure 6B This is a signal diagram of an example data stream represented by method 600. Method 600 is described as being performed using a relay UE that communicates with a remote UE, an AMF, and a session management function (SMF).

[0160] In another embodiment, the S-NSSAI set can be obtained through... Figure 7A The method shown in 700 is used to complete this.

[0161] In operation 701, apparatus 400 includes components such as processor 402, memory 404, etc., configured to determine a set of slice identifiers based on at least one or more parameters, including one or more slice mapping rules. In this regard, a relay UE can determine the S-NSSAI to be used for relaying services. For example, the relay UE can select S-NSSAI and DNN for a PDU session that will be used to relay services for a remote UE. In some embodiments, determining the set of slice identifiers can be based on local mapping rules (e.g., slice mapping rules) at the relay UE. Furthermore, determining the set of slice identifiers may also take into account anticipated requested slice information received from the remote UE, and / or the capabilities of the access network to which the relay UE is connected. Similarly, for SNPN deployments, the UE can determine the S-NSSAI to be used for services relayed through the underlying network. For example, the UE can select S-NSSAI and DNN for a PDU session that will be used to relay services through the underlying network. In some embodiments, determining the slice identifiers can be based on local mapping rules (e.g., slice mapping rules) at the UE. Furthermore, determining the slice identifier may also take into account the expected requested slice information intended for use on the overlay network, and / or the capabilities of the access network to which the UE is connected. In both the case of a relay UE and a UE in an SNPN deployment, the slice mapping rules may have already been received from the policy control function.

[0162] In operation 702, device 400 includes components such as processor 402, memory 404, etc., configured to trigger the establishment (or modification) of a PDU session based on one or more parameters. In this regard, a relay UE (in the case of D2D) or a UE (in the case of SNPN) can use the S-NSSAI determined in step 701 to trigger the establishment (or modification) of a PDU session.

[0163] Figure 7B This is a signal diagram of an example data stream represented by method 700. Method 700 is described as being performed using a relay UE that communicates with a remote UE, an AMF, and a session management function (SMF).

[0164] As described above, similar methods (e.g., methods 500, 600, and 700) can be applied to SNPN access via PLMN or PLMN access via SNPN (e.g., as...). Figure 3A and Figure 3B As shown in the figure, the unique UE acts as both a remote UE and a relay UE, and the internal interface within the unique UE replaces the PC5 interface of the example embodiment described above.

[0165] As described above, the reference flowchart of the method can be executed by an apparatus according to a related computer program product including computer program code. It should be understood that each block of the flowchart, and combinations of blocks in the flowchart, can be implemented by various means, such as hardware, firmware, processors, circuit systems, and / or other devices associated with the execution of software including one or more computer program instructions. For example, one or more of the processes described above can be embodied by computer program instructions. In this regard, the computer program instructions embodying the processes described above can be stored in a memory device (e.g., 404) of an apparatus employing embodiments of the present invention (e.g., 400) and executed by the processor (e.g., 402) of that apparatus. As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine that causes the resulting computer or other programmable device to perform the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable storage medium that can instruct a computer or other programmable device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of art, the execution of which performs the functions specified in the flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operations to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable device, provide operations for implementing the functions specified in the flowchart blocks.

[0166] Therefore, a computer program product is defined whereby the computer program instructions (such as the computer-readable program code portion) are stored in at least one non-transitory computer-readable storage medium, wherein the computer program instructions (such as the computer-readable program code portion) are configured to perform the aforementioned functions upon execution. In other embodiments, the computer program instructions (such as the computer-readable program code portion) do not need to be stored in a non-transitory computer-readable storage medium or otherwise embodied, but may be embodied in a transient medium, wherein the computer program instructions (such as the computer-readable program code portion) are still configured to perform the aforementioned functions upon execution.

[0167] Therefore, flowchart blocks support combinations of components used to perform specified functions and combinations of operations used to perform specific functions. It will also be understood that one or more blocks of a flowchart, and combinations of blocks in a flowchart, can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions to perform the specified functions.

[0168] In some embodiments, certain of the operations, methods, steps, processes, etc. described above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations, methods, steps, processes, etc., may be included. Modifications, additions, subtractions, inversions, correlations, proportional relationships, imbalance relationships, attenuations, and / or amplifications of the above operations can be performed in any order and in any combination. It will also be understood that where specific operations, methods, processes, etc., require specific hardware, such hardware can be considered part of the apparatus 400 for any such embodiment.

[0169] Benefiting from the teachings given in the foregoing description and associated drawings, those skilled in the art will be able to conceive of many modifications and other embodiments of the invention presented herein. Therefore, it should be understood that the invention is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary embodiments in the context of certain example combinations of elements and / or functions, it should be understood that alternative embodiments may provide different combinations of elements and / or functions without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those explicitly described above, as set forth in some of the appended claims, are also contemplated. Although specific terms are used herein, they are used only in a general and descriptive sense and not for limiting purposes.

Claims

1. A relay user equipment configured to connect to an overlay network, the relay user equipment comprising: At least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured together with the at least one processor to cause the relay user equipment to: A first request is received from a remote user equipment, the request including the PLMN identifier of the home public land mobile network (PLMN) of the remote user equipment and the requested slice information, the requested slice information including: a list of individual network slice selection assistance information (S-NSSAI) that the remote user equipment intends to be presented as requested network slice selection assistance information (N-SSAI) in a non-access stratum registration request message, the non-access stratum registration request message being sent to the overlay network; Based at least on the PLMN identifier and the requested slice information, and based at least on one or more parameters including one or more slice mapping rules, determine a set of slice identifiers including at least one slice identifier, the at least one slice identifier identifying at least one corresponding network slice supported by the relay user equipment; and This causes the slice identifier set to be transmitted to the remote user equipment for use during a relay session to the overlay network.

2. The relay user equipment of claim 1, wherein the at least one memory and the computer program code are configured, together with the at least one processor, such that the relay user equipment determines the set of slice identifiers by: This triggers the transmission of a second request to the Access and Mobility Management Function (AMF), the second request including the PLMN identifier and the requested slice information; and The slice identifier set is received from the AMF, the slice identifier set being determined at least based on the PLMN identifier and the requested slice information.

3. The relay user equipment of claim 2, wherein the second request includes a Packet Data Unit (PDU) session establishment request, and wherein receiving the slice identifier set from the AMF includes: Receive the set of slice identifiers as part of the PDU session accept message.

4. The relay user equipment of claim 2, wherein the second request includes a Packet Data Unit (PDU) session modification request, and wherein receiving the slice identifier set from the AMF includes: Receive the set of slice identifiers as part of the PDU session modification accept message.

5. The relay user equipment according to claim 2, wherein the second request includes a Dedicated Non-Access Stratum (NAS) message, the NAS message requesting authorization for relaying services of the remote user equipment.

6. The relay user equipment of claim 5, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, such that the relay user equipment: The set of slice identifiers and the slice identifiers are received. The slice identifiers will be used to determine the Packet Data Unit (PDU) session for relaying the services of the remote user equipment.

7. The relay user equipment of claim 6, wherein determining the PDU session includes one of the following: use of an established PDU session for the slice identifier, a request to modify the established PDU session for the slice identifier, or a request to establish the PDU session.

8. The relay user equipment of claim 1, wherein the one or more parameters further include at least one of the following: the requested slice information and the associated access network capabilities.

9. The relay user equipment of claim 1, wherein the one or more slice mapping rules are received from the policy control function (PCF).

10. The relay user equipment of claim 1, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, such that the relay user equipment: The establishment of a PDU session is triggered based on one or more of the parameters.

11. The relay user equipment of claim 1, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, such that the relay user equipment: Modification of the PDU session is triggered based on one or more of the parameters.

12. An apparatus for a relay user equipment configured to connect to an overlay network, the apparatus comprising: Components for receiving a first request from a remote user equipment, the request including the PLMN identifier of the home public land mobile network (PLMN) of the remote user equipment and requested slice information, the requested slice information including: a list of individual network slice selection assist information (S-NSSAI) that the remote user equipment intends to be presented as requested network slice selection assist information (N-SSAI) in a non-access stratum registration request message, the non-access stratum registration request message being sent to the overlay network; A component for determining a set of slice identifiers, including at least one slice identifier, based at least on the PLMN identifier and the requested slice information, and at least on one or more parameters including one or more slice mapping rules, wherein the at least one slice identifier identifies at least one corresponding network slice supported by the relay user equipment; and Components used to cause the transmission of the slice identifier set to the remote user equipment for use during a relay session to the overlay network.

13. The apparatus of claim 12, wherein the component for determining the set of slice identifiers comprises: Components for initiating the transmission of a second request to the Access and Mobility Management Function (AMF), the second request including the PLMN identifier and the requested slice information; as well as A component for receiving the set of slice identifiers from the AMF, the set of slice identifiers being determined at least based on the PLMN identifier and the requested slice information.

14. The apparatus of claim 13, wherein the second request includes a Packet Data Unit (PDU) session establishment request, and wherein the component for receiving the set of slice identifiers from the AMF includes: A component for receiving the set of slice identifiers as part of a PDU session accept message.

15. The apparatus of claim 13, wherein the second request includes a Packet Data Unit (PDU) session modification request, and wherein the component for receiving the set of slice identifiers from the AMF includes: A component for receiving the set of slice identifiers as part of a PDU session modification accept message.

16. The apparatus of claim 13, wherein the second request includes a Dedicated Non-Access Stratum (NAS) message requesting authorization for relaying services of the remote user equipment.

17. The apparatus of claim 16, further comprising: The component is used to receive the set of slice identifiers and the slice identifiers, which will be used to determine the Packet Data Unit (PDU) session for relaying the service of the remote user equipment.

18. The apparatus of claim 17, wherein determining the PDU session comprises one of: using an established PDU session for the slice identifier, requesting modification of the established PDU session for the slice identifier, or requesting the establishment of the PDU session.

19. The apparatus of claim 12, wherein the one or more parameters further include at least one of the following: the requested slice information and the associated access network capabilities.

20. The apparatus of claim 12, wherein the one or more slice mapping rules are received from the policy control function (PCF).

21. The apparatus of claim 12, further comprising: A component used to trigger the establishment of a PDU session based on one or more of the parameters.

22. The apparatus of claim 12, further comprising: A component used to trigger modifications to a PDU session based on one or more of the parameters.

23. A method for providing a set of slice identifiers, the method being performed by a relay user equipment connected to an overlay network, the method comprising: A first request is received from a remote user equipment, the request including the PLMN identifier of the home public land mobile network (PLMN) of the remote user equipment and the requested slice information, the requested slice information including: a list of individual network slice selection assistance information (S-NSSAI) that the remote user equipment intends to be presented as requested network slice selection assistance information (N-SSAI) in a non-access stratum registration request message, the non-access stratum registration request message being sent to the overlay network; Based at least on the PLMN identifier and the requested slice information, and based at least on one or more parameters including one or more slice mapping rules, determine a set of slice identifiers including at least one slice identifier, the at least one slice identifier identifying at least one corresponding network slice supported by the relay user equipment; and This causes the slice identifier set to be transmitted to the remote user equipment for use during a relay session to the overlay network.

24. The method of claim 23, wherein determining the set of slice identifiers comprises: This triggers the transmission of a second request to the Access and Mobility Management Function (AMF), the second request including the PLMN identifier and the requested slice information; as well as The slice identifier set is received from the AMF, the slice identifier set being determined at least based on the PLMN identifier and the requested slice information.

25. The method of claim 24, wherein the second request includes a Packet Data Unit (PDU) session establishment request, and wherein receiving the slice identifier set from the AMF includes: Receive the set of slice identifiers as part of the PDU session accept message.

26. The method of claim 24, wherein the second request includes a Packet Data Unit (PDU) session modification request, and wherein receiving the slice identifier set from the AMF includes: Receive the set of slice identifiers as part of the PDU session modification accept message.

27. The method of claim 24, wherein the second request includes a Private Non-Access Stratum (NAS) message requesting authorization for relaying services of the remote user equipment.

28. The method of claim 27, further comprising: The set of slice identifiers and the slice identifiers are received. The slice identifiers will be used to determine the Packet Data Unit (PDU) session for relaying the services of the remote user equipment.

29. The method of claim 28, wherein determining the PDU session comprises one of: using an established PDU session for the slice identifier, requesting modification of the established PDU session for the slice identifier, or requesting the establishment of the PDU session.

30. The method of claim 23, wherein the one or more parameters further include at least one of the following: the requested slice information and the associated access network capabilities.

31. The method of claim 23, wherein the one or more slice mapping rules are received from the policy control function (PCF).

32. The method of claim 23, further comprising: The establishment of a PDU session is triggered based on one or more of the parameters.

33. The method of claim 23, further comprising: Modification of the PDU session is triggered based on one or more of the parameters.

34. A non-transitory computer-readable storage medium having a program code portion stored thereon, the program code portion being configured to, when executed, perform the method according to any one of claims 23 to 33.

35. A remote user equipment, comprising: At least one processor; as well as At least one memory including computer program code, the at least one memory and the computer program code being configured together with the at least one processor, such that the remote user equipment: The request is transmitted to a relay user equipment connected to the overlay network. The request includes the PLMN identifier of the home public land mobile network (PLMN) of the remote user equipment and the requested slice information, which includes a list of individual network slice selection assistance information (S-NSSAI) that the remote user equipment intends to be presented as requested network slice selection assistance information (N-SSAI) in the non-access stratum registration request message, which will be sent to the overlay network. as well as A set of slice identifiers is received from the relay user equipment for use by the remote user equipment during a relay session to the overlay network, wherein the set of slice identifiers includes at least one slice identifier that identifies at least one corresponding network slice supported by the relay user equipment, and wherein the set of slice identifiers is determined by the relay user equipment based on the PLMN identifier, the requested slice information, and at least one or more parameters including one or more slice mapping rules.

36. The remote user equipment of claim 35, wherein the set of slice identifiers is used to generate a slice request for registration with the network via a connection supported by the relay user equipment.

37. An apparatus for a remote user equipment, comprising: Components for initiating a request to transmit to a relay user equipment connected to an overlay network, the request including the PLMN identifier of the remote user equipment's Home Public Land Mobile Network (PLMN) and requested slice information, the requested slice information including: a list of individual Network Slice Selection Assistance Information (S-NSSAI) that the remote user equipment intends to be presented as requested Network Slice Selection Assistance Information (N-SSAI) within a Non-Access Stratum Registration Request message, the Non-Access Stratum Registration Request message being sent to the overlay network; and Components for receiving a set of slice identifiers from the relay user equipment for use by the remote user equipment during a relay session to the overlay network, wherein the set of slice identifiers includes at least one slice identifier that identifies at least one corresponding network slice supported by the relay user equipment, and wherein the set of slice identifiers is determined by the relay user equipment based on the PLMN identifier, the requested slice information, and at least one or more parameters including one or more slice mapping rules.

38. The apparatus of claim 37, wherein the set of slice identifiers is used to generate a slice request for registration with the network via a connection supported by the relay user equipment.

39. A communication method performed by a remote user equipment, comprising: A request is initiated to transmit to a relay user equipment connected to the overlay network. The request includes the PLMN identifier of the remote user equipment's Home Public Land Mobile Network (PLMN) and requested slice information, which includes a list of individual Network Slice Selection Assistance Information (S-NSSAI) that the remote user equipment intends to be presented as requested Network Slice Selection Assistance Information (N-SSAI) within the Non-Access Stratum Registration Request message, which will be sent to the overlay network. A set of slice identifiers is received from the relay user equipment for use by the remote user equipment during a relay session to the overlay network, wherein the set of slice identifiers includes at least one slice identifier that identifies at least one corresponding network slice supported by the relay user equipment, and wherein the set of slice identifiers is determined by the relay user equipment based on the PLMN identifier, the requested slice information, and at least one or more parameters including one or more slice mapping rules.

40. The method of claim 39, wherein the set of slice identifiers is used to generate a slice request for registration with the network via a connection supported by the relay user equipment.

41. A non-transitory computer-readable storage medium having a program code portion thereon stored thereon, the program code portion being configured to, when executed, perform the method according to any one of claims 39 to 40.

Images