Patent Description:
<CIT> discloses a user equipment (UE) that may determine a service type to be used by the UE for one or more device-to-device (D2D) communications on a sidelink interface; determine a slice identifier based at least in part on the service type, wherein the slice identifier corresponds to a resource allocation to be used for the one or more D2D communications; and transmit an indication of the slice identifier. Numerous other aspects are provided, in particular a first UE receives an indication of a slice identifier that identifies a slice type to be used by a second UE, wherein the slice identifier corresponds to a service type and a resource allocation to be used for one or more D2D communications of the second UE on a sidelink interface; determines the resource allocation based at least in part on the slice identifier; and prevents the first UE from using resources indicated by the resource allocation for transmission of communications not associated with the service type.

<CIT> discloses a mechanism to enable interworking between fifth generation system (5GS) network slicing and evolved packet core (EPC) connectivity. In an example, techniques are provided for existing packet data unit (PDU) sessions that provide connectivity to a network slice from a set of network slices. Connectivity to the network slice is in response to a user equipment (UE), that uses network slices, moving between a <NUM> network and a <NUM> network. The existing PDU sessions are connected to a dedicated EPC core network that supports the same services provided by the network slice.

The present disclosure is better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

Tethering enables devices that may not have hardware or software resources for establishing a connection with a given network to still access the network through another capable device. For example, a first user equipment (UE) device, such as a tablet or notebook computer, may not have the hardware/software to connect with a cellular network. However, the first UE device can establish a wired or wireless tethered connection (downstream link) with a second UE device, such as a smartphone, capable of establishing a connection (upstream link) with the cellular network. The tethered connection enables the first UE device to access the cellular network's services through the second UE device's network connection.

As data and bandwidth allotments have increased for end-users, tethering has become a more viable and useful option for accessing the Internet through cellular networks. However, tethering technology typically is not configured to realize recent advancements in cellular networks. One such advancement is network slicing, which defines different classes of services and provides end-to-end logical networks (network slices) for these services that span multiple portions of a cellular network. Network slicing allows for network services to be customized based on the requirements of different use cases. The services provided by a Third Generation Partnership Project (3GPP) Fifth Generation New Radio (<NUM> NR) cellular network can be implemented using a network slice, which is instantiated and managed by the network management system of the <NUM> NR cellular network. In at least some embodiments, a network slice defines a class of service in a cellular network and can be viewed as an end-to-end logical network that spans multiple portions of the cellular network. Each network slice provides service qualities tailored to the use case associated with the network slice, such as low latency, guaranteed bandwidth, support for long-battery-life Internet of Things (IoT) devices, and so on. Also, a network slice can have dedicated resources in the network of a single network operator or across the network of multiple network operators. An end-to-end network slice may be comprised of a Radio Access Network ( RAN) slice and/or a core slice.

When a tethered connection is made between UE devices, only one upstream link is typically established with the cellular network. Also, conventional tethering technologies are typically not configured to maintain network slice mappings for data traffic over tethered connections. The combination of a single upstream link and lack of network slice mapping results in a single common network slice being used for the tethered connection regardless of the number of client UE devices that are tethered to the host UE device or the services being accessed by the client devices. As such, conventional tethering technology typically cannot utilize the different network slices offered by a cellular network.

The present disclosure describes embodiments of systems and methods for implementing multiple concurrent network slices for tethered connections. In at least some embodiments, a host UE device establishes a connection with a cellular network. As part of the connection process, the cellular network sends network slice information to the host UE device. This network slice information identifies the available network slices provided by the cellular network. In other embodiments, the network slice information is obtained by the host UE device while in an idle mode during a radio/cell search or at some other point in time before connecting to the cellular network. The network slice information comprises information such as a unique identifier, device and service requirements, capabilities, and the like for each available network. In at least some embodiments, the host UE device selects a default network slice from the available network slices for accessing the cellular network. The host UE device may select the default network slice, for example, based on the host UE device's context and/or the capabilities/requirements of the available network slices. For example, the host UE can select a default network slice based on one or more of the device type, executing applications, requested services or, latency requirements of the host UE device. In other embodiments, the cellular network selects a default network slice for the host UE device based on, for example, the context of the host UE device.

One or more client UE devices establish a tethered connection with the host UE device. The tethered connection may be a wired connection or a wireless connection. In at least some embodiments, the tethered connection is established before or after the host UE device has selected the default network slice. Responsive to the tethered connection(s) having been established, the host UE device determines one or more network slices to be used for each of the one or more client UE devices. For example, in at least some embodiments, the host UE device maintains and utilizes network slice selection policies (or rules) to select a network slice (or slices) for each client UE device. In at least some embodiments, the selection policies indicate which network slice is to be selected for a client UE device based on, for example, a context of the client UE device or a network slice request received from the client UE device. For example, a first selection policy may indicate that if a client UE device is an Internet-of-Things (IoT) device, then a first network slice is selected. In another example, a second selection policy may indicate that when a Wireless Fidelity (Wi-Fi) tethered connection is established between the host UE device and a client UE device, a second network slice is selected. Different selection policies can have different levels of granularity for selection criteria.

In at least some embodiments, a client UE device is assigned different network slices at different times. In other embodiments, a client UE device is assigned multiple different network slices concurrently. Also, different devices can be assigned different network slices based on the network slice selection policies. Once a network slice has been selected for each client UE device, the host UE device establishes an upstream link for the selected network slice if not already established. An upstream link, in at least some embodiments, includes a physical link or a virtual/logic link. For example, a physical upstream link, such as packet data network (PDN) connection, can support multiple network slices through network routes/rules, protocol data unit (PDU) assignment, and so on. As such, a single physical upstream link can support multiple logical upstream links for different network slices. Therefore, in at least some embodiments, a physical upstream link can be established for a selected network slice or a logical upstream link can be established for a selected network slice. Any data associated with a client UE device is transmitted and received through the assigned network slice instead of the default network slice. As such, the techniques described herein provide for a host UE device to establish multiple upstream links (physical and/or logical) for implementing concurrent network slices for tethered client UE devices in a cellular network. Data or data associated with tethered client UE devices can benefit from the networking, computing, and storage resources allocated and configured for the network slices carrying the data.

For ease of illustration, the following techniques are described in an example context in which one or more UE devices and Radio Access Networks (RANs) implement one or more radio access technologies (RATs) including at least a Fifth Generation (<NUM>) New Radio (NR) standard (e.g., Third Generation Partnership Project (3GPP) Release <NUM>, 3GPP Release <NUM>, etc.) (hereinafter, "<NUM> NR" or "<NUM> NR standard"). However, it should be understood that the present disclosure is not limited to networks employing a <NUM> NR RAT configuration, but rather the techniques described herein can be applied to any combination of different RATs employed at the UE devices and the RANs. It should also be understood that the present disclosure is not limited to any specific network configurations or architectures described herein for implementing network slicing (or equivalent technology) with tethered connections, but instead, techniques described herein can be applied to any configuration of RANs where a host UE device can establish multiple concurrent upstream links to implement different network slices for tethered client UE devices. Also, the present disclosure is not limited to the examples and context described herein, but rather the techniques described herein can be applied to any network environment where a host UE device implements network slicing for tethered client UE devices.

<FIG> illustrates an example mobile cellular network <NUM> employing a set of tethered UE devices <NUM>, <NUM> implementing network slicing in accordance with some embodiments. It should be understood that the present disclosure is not limited to a cellular network <NUM>, and the techniques described herein apply to other types of wireless communication systems. As shown, the cellular network <NUM> includes multiple UE devices <NUM>, <NUM>, one or more RANs <NUM>, and a core network <NUM>. <FIG> further shows that one or more external networks <NUM>, such as the Internet or a public switched telephone network (PSTN), are coupled to the cellular network <NUM> via the core network <NUM>. It should be understood that the cellular network <NUM> may include additional components not shown in <FIG>.

The UE devices <NUM>, <NUM> can include any of a variety of electronic devices capable of wired and/or wireless communications, such as a smartphone, a tablet computer, a notebook computer, a desktop computer, a smartwatch or other wearable computing device, an automobile or other vehicle employing wireless communication services (e.g., for navigation, provision of entertainment services, in-vehicle mobile hotspots, etc.), a gaming device, a media device, an loT device (e.g., sensor node, controller/actuator node, or a combination thereof), and another device capable of wired and/or wireless communication. In at least one embodiment, the RAN(s) <NUM> is accessible using, for example, a <NUM> NR RAT and is connected to one or more other RANs (not shown) via at least the core network <NUM>. A RAN <NUM> implementing a <NUM> NR RAT may be referred to as a <NUM> NR RAN or an NR RAN. One example of a core network <NUM> in a <NUM> NR cellular network is Fifth-Generation Core (5GC) network.

Each RAN <NUM> includes one or more base stations <NUM> operable to wirelessly communicate with UE devices <NUM>, <NUM> within signal range, with each or a combination of base stations <NUM> defining a single "cell" of coverage for the RAN <NUM>. In at least some embodiments, a base station <NUM> is implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof. Consistent with the terminology employed by the <NUM> NR standard, a base station <NUM> implementing a <NUM> NR RAT is referred to herein as "<NUM> NodeB <NUM>" or "gNB <NUM>". As is well known in the art, the base stations <NUM> operate as an "air interface" to establish radio frequency (RF) wireless communication links with UE devices <NUM>, <NUM>, which can be implemented as any suitable type of wireless communication link. These wireless communication links then serve as data and voice paths between the UE devices <NUM>, <NUM> and the core network <NUM>, which is coupled to one or more of the external networks <NUM>, for providing various services to the UE devices <NUM>, <NUM>. Examples of these services include voice services via circuit-switched networks or packet-switched networks, messaging services such as simple messaging service (SMS) or multimedia messaging service (MMS), multimedia content delivery, presence services, and so on. In at least some embodiments, multiple wireless communication links are aggregated in a carrier aggregation to provide a higher data rate for the UE devices <NUM>, <NUM>. Multiple wireless communication links from multiple base stations <NUM> can be configured for Coordinated Multipoint (CoMP) communication with the UE devices <NUM>, <NUM>. Additionally, in at least some embodiments, multiple wireless communication links are configured for single-RAT) or multi-RAT dual connectivity (MR-DC).

<FIG> further illustrates an example configuration of the cellular network <NUM> that implements network slicing for tethered connections between UE devices <NUM>, <NUM>. In the present invention, one or more client UE devices <NUM> (illustrated as <NUM>-<NUM> to <NUM>-<NUM>) establish a tethered connection <NUM> (illustrated as <NUM>-<NUM> to <NUM>-<NUM>) with a host UE device <NUM>. The tethered connection <NUM> (also referred to as a downstream link <NUM>) can be established using wired or wireless technologies. For example, a wired connection between the host UE device <NUM> and a client UE device <NUM> can be made using a Universal Serial Bus (USB) connection, an Ethernet connection, and so on. A wireless connection can be made using, for example, Wi-Fi (that is, one or more of the IEEE <NUM> wireless standards), Bluetooth®, Zigbee®, Near-field Communication (NFC), and so on.

The tethered connections <NUM> enable client UE devices <NUM> to access the core network <NUM> and the external networks <NUM> through a communication link(s) <NUM> (also referred to as an upstream link(s) <NUM>) established between the host UE device <NUM> and the core network <NUM> through the RAN <NUM>. For example, the client UE devices <NUM> transmit network requests to the host UE device <NUM> over their respective tethered connection <NUM>. The host UE device <NUM> relays the network requests received from the client UE devices <NUM> to the appropriate destination through the RAN <NUM> and core network <NUM> using the upstream link <NUM> established by the host UE device <NUM>. The host UE device <NUM> also receives data associated with one or more of the client UE devices <NUM> through the upstream link <NUM> from, for example, an external network <NUM>. The host UE device <NUM> transmits the received data to the appropriate client UE device <NUM> through the tethered connection <NUM>. Data, in at least some embodiments, includes singular data packets, multiple data packets, data streams, data bursts, and so on.

In conventional tethered configurations, a host UE device is typically not configured to maintain network slice mappings for data traffic over tethered connections. As such, the host UE usually establishes a single common upstream link with the <NUM> NR core network <NUM> for all connected client UE devices. Therefore, only the default network slice currently used by the host UE device can be used for the client UE devices. However, as described in greater detail below, the host UE device <NUM> can, in some embodiments, establish multiple concurrent upstream links <NUM> (illustrated as <NUM>-<NUM> to <NUM>-<NUM>) and access multiple network slices <NUM> for tethered client UE devices <NUM> using the upstream links <NUM>. In at least some embodiments, one or more of the upstream links <NUM> are a physical upstream link. In other embodiments, one or more of the concurrent upstream links <NUM> are logical upstream links carried over a physical upstream link.

In at least some embodiments, the host UE device <NUM> obtains network slice information <NUM> associated with the network slices <NUM> of the core network <NUM>. <FIG> shows that the core network <NUM> includes multiple network slices <NUM> (illustrated as network slice <NUM>-<NUM> to <NUM>-<NUM>). Throughout this description, network slice <NUM>-<NUM> is referred to as the default network slice, and network slices <NUM>-<NUM> to <NUM>-<NUM> are referred to as the non-default network slices. Examples of network slices <NUM> include network slices configured for <NUM> NR enhanced Mobile Broadband (eMBB), <NUM> Ultra-Reliable Low Latency Communications (URLLC), <NUM> NR massive Machine Type Communications (mMTC), massive Internet-of-Things (MIoT), and so on. The cellular network <NUM> may include any number and combination of network slices <NUM>, including those not illustrated in <FIG>.

The network slice information <NUM>, in at least some embodiments, comprises a list or other data structure representing available network slices <NUM> and information such as an identifier, device requirements and application/service requirements, capabilities, service level agreements (SLAs), configured resources, and the like for each available network slice <NUM>. In at least some embodiments, the network slice information <NUM> is obtained by the host UE device <NUM> from a user, a network operator, a base station <NUM>, one or more core network components <NUM>, an external network <NUM>, and so on. In one example, the network slice information <NUM> is obtained by the host UE device <NUM> as part of the attachment process with the cellular network <NUM>. In another example, the network slice information <NUM> is obtained by the host UE device <NUM> while in an idle mode during a radio/cell search or at some other point in time before attaching to the cellular network <NUM>.

The host UE device <NUM>, in at least some embodiments, selects the default network slice <NUM>-<NUM> based on, for example, a context <NUM> (also referred to as context information <NUM>) of the host UE device <NUM> and/or one or more selection policies (SPs) <NUM> described below. In other embodiments, the RAN <NUM> or a component <NUM> of the core network <NUM> managing the network slices <NUM> selects a default network slice <NUM>-<NUM> for the host UE device <NUM>. For example, the host UE device <NUM> can transmit a network slice access request to one or more network components <NUM>, such as a network slice management component, along with a context <NUM> of the host UE device <NUM>. The network slice management component uses the context <NUM> of the host UE device <NUM> to select a default network slice <NUM>-<NUM> for the host UE device <NUM>.

In at least some embodiments, a context <NUM> of a UE device indicates various parameters/attributes of the UE device. Examples of context information include tethered connection parameters such as link type (e.g., wired or wireless, USB, Wi-Fi, Bluetooth®, etc.), link frequency, channel, and so on; client UE device type (e.g., smartphone, tablet computing device, laptop, vehicle, IoT device, gaming device, etc.); media access control (MAC) address of the UE device <NUM>, <NUM>; source Internet Protocol (IP) address of the data associated with the UE device <NUM>, <NUM>; the destination IP address of the data associated with the UE device <NUM>, <NUM>; the communication port associated with the data of the UE device <NUM>, <NUM>; the applications and/or services on the UE device <NUM>, <NUM> requesting data; latency requirements of the UE device <NUM>, <NUM>; the mobility status (e.g., in a vehicle, stationary, on a pedestrian, traveling above or below a speed threshold, etc.) of the UE device <NUM>, <NUM>; the type and/or size of data being transmitted and/or requested by the UE device <NUM>, <NUM>; and so on.

The host UE device <NUM>, in at least some embodiments, activates the selected default network slice <NUM>-<NUM> by sending an access request to the RAN <NUM> and/or one or more core network components <NUM> for accessing the selected default network slice <NUM>-<NUM>. After the host UE device <NUM> has been authenticated and granted access to the default network slice <NUM>-<NUM>, the host UE device <NUM> uses a default upstream link <NUM>-<NUM> to access the default network slice <NUM>-<NUM> and related services.

Data associated with the default network slice <NUM>-<NUM> are wirelessly communicated (e.g., transmitted and/or received) by the host UE device <NUM> over the default upstream link <NUM>-<NUM>. Wireless communication of data, in at least some embodiments, can include one or both of transmitting data or receiving data. The host UE device <NUM> may establish the upstream link <NUM>-<NUM> with the cellular network <NUM> before or after selecting the default network slice <NUM>-<NUM>. Various mechanisms and techniques may be implemented by the host UE device <NUM> for establishing an upstream link <NUM> and accessing a network slice <NUM>, such as those described in the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the <NUM> System; Stage <NUM> (Release <NUM>).

In addition to selecting and accessing the default network slice <NUM>-<NUM>, the host UE device <NUM> also selects and accesses one or more network slices <NUM> for the client UE devices <NUM>. In at least some embodiments, the host UE device <NUM> uses a set of one or more network slice selection policies <NUM> (such as the illustrated network slice selection policies <NUM>-<NUM> and <NUM>-<NUM>) for determining which of the network slices <NUM> to select and use for a given client UE device <NUM>. The host UE device <NUM>, in at least some embodiments, obtains the network slice selection policies <NUM> (hereinafter, "selection policies <NUM>" for purposes of brevity) from a user, a network operator, one or more of the client UE devices <NUM>, a base station <NUM>, a component <NUM> of the core network <NUM>, an external network <NUM>, and so one. In one example, a client UE device <NUM> transmits one or more selection policies <NUM> to the host UE device <NUM> using the tethered connection <NUM>. In at least some embodiments, the selection policies <NUM> include, for example, identifiers <NUM> of the network slices <NUM> and criteria <NUM> for each network slice <NUM> that govern the selection and utilization of the network slices <NUM> for the client UE devices <NUM>. The host UE device <NUM> may store and access the selection policies <NUM> locally and/or remotely.

In at least some embodiments, the selection policies <NUM> are global selection policies <NUM>-<NUM> applied to one or more client UE devices <NUM>. In other embodiments, one or more selection policies <NUM> are UE specific selection policies <NUM>-<NUM> defined or configured for a specific client UE device <NUM>. If a client UE device <NUM> is associated with a UE specific selection policy <NUM>-<NUM>, the host UE device <NUM> may use the UE specific selection policy <NUM>-<NUM> to select a network slice <NUM> for the client UE device <NUM> instead of a global selection policy <NUM>-<NUM>. In at least some embodiments, the selection criteria <NUM> of a selection policy <NUM> can be defined from the viewpoint of a UE device <NUM>, <NUM> and/or network slice <NUM>. For example, a global selection policy <NUM>-<NUM> may indicate that an associated network slice <NUM> may only be selected for a client UE device <NUM> if the context <NUM> of the client UE device <NUM> satisfies the selection criteria <NUM>. In another example, a UE specific selection policy <NUM>-<NUM> may include selection criteria <NUM> that indicates a specific slice context <NUM> (e.g., parameters, attributes, capabilities, etc.) for a network slice <NUM> to be selected for a given client UE device <NUM>. In at least some embodiments, the host UE device <NUM> may use a selection policy <NUM> to select a default network slice <NUM>-<NUM>. Also, in at least some embodiments, a user or application executing on either the host UE device <NUM> or client UE device <NUM> can update a selection policy <NUM> defined for the client UE device <NUM>.

In addition to selection criteria <NUM>, the selection policies <NUM>, in at least some embodiments, also include resource allocation information for the tethered connections <NUM>. For example, the selection policies <NUM> can indicate specific resources for allocation to any client UE <NUM> or one or more specific client UE devices <NUM> for a given tethering context. For example, a selection policy <NUM> can indicate that, for a tethering context in which one or more client UE devices <NUM> are connected to the host UE <NUM> using a Wi-Fi link, resources such as a specific channel, frequency, buffer size, and so on are to be allocated to the one or more client UE devices <NUM>. In at least some embodiments, the resource allocation information may be included in a separate and distinct policy from the selection policies <NUM>.

<FIG> shows a generalized example of network slice selection policies <NUM> (illustrated as <NUM>-<NUM> to <NUM>-<NUM>), which are embodiments of the selection policies <NUM> of <FIG>. In at least some embodiments, each network slice selection policy <NUM> (or simply "selection policy <NUM>" herein for brevity's sake) comprises an identifier <NUM> and selection criteria <NUM>. The identifier <NUM> uniquely identifies the network slice <NUM> associated with the selection policy <NUM>. The selection criteria <NUM> are used by the host UE device <NUM> to determine whether the associated network slice <NUM> is selected and used for a client UE device <NUM>. For example, a first selection policy <NUM>-<NUM> associated with a first network slice <NUM>-<NUM> includes the unique identifier "NS_1", and the selection criteria <NUM> comprises a value of "Default". In this example, a "Default" value indicates the first network slice <NUM>-<NUM> is designated as a default network slice <NUM> selected for a client UE device <NUM> when no other network slice <NUM> can be selected for the client UE device <NUM>. For example, if the current context <NUM> of the client UE device <NUM> does not satisfy the selection criteria <NUM> defined for non-default network slices <NUM>-<NUM> to <NUM>-<NUM>, the host UE device <NUM> selects the default network slice <NUM>-<NUM> for the client UE device <NUM>. Alternatively, the host UE device <NUM> may determine the context <NUM> of the client UE device <NUM> satisfies the selection criteria <NUM> of the default network slice <NUM>-<NUM> and selects the default network slice <NUM>-<NUM> based on this determination. In embodiments, where the selection criteria <NUM> are to be satisfied by the network slices <NUM>, as compared to the client UE devices <NUM>, the host UE device <NUM> selects the default network slice <NUM>-<NUM> when the remaining network slices <NUM>-<NUM> to <NUM>-<NUM> do not satisfy the selection criteria <NUM>.

A second selection policy <NUM>-<NUM> associated with a second network slice <NUM>-<NUM> includes the unique identifier "NS_2" and the selection criteria "A, B, and C". In this example, the host UE device <NUM>-<NUM> selects and utilizes the second network slice <NUM>-<NUM> when conditions A, B, and C are satisfied. Depending on how the second selection policy <NUM>-<NUM> is configured, the conditions are to be satisfied either by a client UE device <NUM> or the second network slice <NUM>-<NUM>.

A third selection policy <NUM>-<NUM> associated with a third network slice <NUM>-<NUM> includes the unique identifier "NS_3", a first set of selection criteria "A, B, C, D, and E", and a second set of selection criteria "If !A but X, Y, or Z, then B, D, F, and G". In this example, the third selection policy <NUM>-<NUM> of the third network slice <NUM>-<NUM> includes a more complex set of selection criteria <NUM> than the second selection policy <NUM>-<NUM> of the second network slice <NUM>-<NUM>. For example, the host UE device <NUM> selects the third network slice <NUM>-<NUM> for the client UE device <NUM> if conditions A, B, C, D, and E are satisfied by the client UE device <NUM>. The third selection policy <NUM>-<NUM> also provides an additional rule that states, if condition A is not satisfied but conditions X, Y, or Z are satisfied, then the third network slice <NUM>-<NUM> can be selected if conditions B, D, F, and G are also satisfied. For example, condition A may indicate that the device type of the client UE device <NUM> should be a tablet computing device. Conditions B, C, D, and E may be specific conditions based on the client UE device <NUM> being a tablet computing device. However, in this example, the third network slice <NUM>-<NUM> is not limited to tablet computing devices. Therefore, the second set of selection criteria includes conditions indicating that if the client UE device <NUM> is not a tablet computing device (condition A) but is either a gaming device, smartphone, or wearable computing device (conditions X, Y, or Z), the third network slice <NUM>-<NUM> can be selected for the client UE device <NUM> if the additional conditions B, D, G, and G are satisfied.

A fourth selection policy <NUM>-<NUM> associated with a fourth network slice <NUM>-<NUM> includes the unique identifier "NS_N" and the selection criteria "A, D, D1, and N". In this example, the host UE device <NUM>-<NUM> selects and utilizes the fourth network slice <NUM>-<NUM> when conditions A, A1, D, and N are satisfied. In this example, not only does condition D have to be satisfied but so does a sub-condition D1 of condition D. For example, condition D may indicate that a tethered connection type between the host UE device <NUM> and the client UE device <NUM>-<NUM> to <NUM>-<NUM> should be a Wi-Fi-based link and sub-condition D1 may indicate that the Wi-Fi-based link should be utilizing the <NUM> gigahertz (GHz) frequency. It should be noted that embodiments are not limited to selection criteria <NUM> having to be satisfied by client UE devices <NUM>. For example, the selection criteria <NUM> may indicate specific parameters or attributes (e.g., latency, bandwidth, services, SLAs, etc.) of a network slice <NUM> to be selected for a given client UE device <NUM>.

Selection criteria <NUM> can be similar to the UE device context parameters listed above. For example, selection criteria <NUM> can include tethered connection parameters such as link type (e.g., wired or wireless, USB, Wi-Fi, Bluetooth®, etc.), link frequency, channel, and so on; client UE device type; media access control (MAC) address; source Internet Protocol (IP) address of the data associated with the client UE device <NUM>; the destination IP address of the data associated with the client UE device <NUM>; the communication port associated with the data of the client UE device <NUM>; the applications and/or services on the client UE device <NUM> requesting data; the mobility status (e.g., in a vehicle, stationary, on a pedestrian, traveling above or below a speed threshold, etc.) of the client UE device <NUM>; a combination thereof; and so on.

Referring back to <FIG>, in at least some embodiments, a network slice selection policy <NUM> may include additional information regarding the management of the selection policy <NUM>. For example, a selection policy <NUM> can indicate that a client UE device <NUM> is or is not authorized to update the selection rules or criteria of the selection policy <NUM>; the client UE device <NUM> needs or does not need to be authorized to update the selection rules or criteria; the client UE device <NUM>-<NUM> is or is not allowed to request its current network slice <NUM> or request a new network slice <NUM>; the client UE device <NUM>-<NUM> needs or does not need to be authorized to request/release a network slice <NUM>; a user of the host UE device <NUM> or the client UE device <NUM>-<NUM> can or cannot be shown details of the selection policy <NUM> or just a summary overview; and so on. In other embodiments, the additional information may be maintained or accessed separately from the selection policies <NUM>.

In at least some embodiments, the host UE device <NUM> determines one or more network slices <NUM> for a client UE device <NUM> responsive to the client UE device <NUM> establishing a tethered connection (downstream link) <NUM> with the host UE device <NUM>, or upon receiving a request from the client UE device <NUM> to access the cellular network <NUM>. As part of, or before, the network slice <NUM> selection process, the host UE device <NUM> obtains a current context <NUM> of the client UE device <NUM> for which a network slice <NUM> is to be selected. For example, the host UE device <NUM> can analyze the selection policies <NUM> and identify the type of context information <NUM> for determining which of the network slices <NUM> can be selected for a client UE device <NUM>. For example, after analyzing a selection policy <NUM> for the third network slice <NUM>-<NUM>, the host UE device <NUM> determines that context information <NUM> such as device type, tethered connection type, tethered connection frequency, and data type are needed to determine if the third network slice <NUM>-<NUM> can be selected for the client UE device <NUM>. The host UE device <NUM> then communicates with the client UE device <NUM> to obtain this context information <NUM>. However, in at least some embodiments, this and other context information <NUM> is already provided to the host UE device <NUM> as part of establishing the tethered connection <NUM>. As such, the context <NUM> of the client UE device <NUM> can be automatically provided to host UE device <NUM> by the client UE device <NUM>, and/or the host UE device <NUM> can query the client UE device <NUM> for context information <NUM>.

The host UE device <NUM>, in at least some embodiments, compares the context <NUM> of a client UE device <NUM> to the selection criteria <NUM> of the selection policies <NUM> to determine if the context <NUM> satisfies the selection criteria <NUM> of one or more network slices <NUM>. If the context <NUM> of the client UE device <NUM> satisfies the selection criteria <NUM> of a network slice <NUM>, the host UE device <NUM> selects the network slice <NUM> and establishes an upstream link <NUM> with the cellular network <NUM> for the client UE device <NUM> to wirelessly communicate data through the selected the network slice <NUM>. In other embodiments, the upstream link <NUM> may be established before selecting the network slice <NUM>. In at least some embodiments, if the context <NUM> of the client UE device <NUM> satisfies the selection criteria <NUM> of two or more network slices <NUM>, the host UE device <NUM> selects the two or more network slices <NUM> for the client UE device <NUM>. The host UE device <NUM> establishes a separate upstream link <NUM> for each of the two or more network slices <NUM> to wirelessly communicate data through the selected network slices <NUM>. If the context <NUM> of the client UE device <NUM> does not satisfy the selection criteria <NUM> of the non-default network slices <NUM>-<NUM> to <NUM>-<NUM>, the host UE device <NUM>, in at least some embodiments, selects the default network slice <NUM>-<NUM> for the client UE device <NUM>. In this embodiment, data associated with the client UE device <NUM> are wirelessly communicated through the default network slice <NUM>-<NUM> using the default upstream link <NUM>-<NUM>.

In at least some embodiments, instead of (or in addition to) analyzing a context <NUM> of a client UE device <NUM> with respect to the selection policies <NUM>, the host UE device <NUM> analyzes a context <NUM> (also referred to as context information <NUM>) of the network slices <NUM> with respect to the selection policies <NUM>. For example, a selection policy <NUM> may include selection criteria <NUM> based on a context <NUM> of network slices <NUM>. For example, selection criteria <NUM> can indicate specific attributes and/or parameters, such as latency, bandwidth, offered services, SLAs, etc., for a network slice <NUM> to be selected for a given client UE device <NUM>.

Also, in at least some embodiments, a client UE device <NUM> requests one or more specific network slices <NUM> or types of network slices <NUM> by sending a request to the host UE device <NUM> using the tethered connection <NUM>. For example, the host UE device <NUM> can broadcast/send a list of available network slices <NUM> provided by the cellular network to one or more of the client UE devices <NUM> through the tethered connection <NUM>, a network or application layer protocol, and so on. A user, application, or service of the client UE device <NUM> can select one or more of the available network slices <NUM>. The client UE device <NUM> then sends a request to the host UE device <NUM> identifying the requested network slice(s) <NUM>. The host UE device <NUM> proceeds to select the requested network slice(s) <NUM> for the client UE device <NUM>. In at least some embodiments, the host UE device <NUM> implements one or more selection policies <NUM> to determine if the requested network slice(s) <NUM> can be used for the client UE device <NUM>.

The network slice <NUM> selection techniques described above are performed for each client UE device <NUM>, resulting in multiple concurrent upstream links <NUM> being established for one or more client UE devices <NUM>. The concurrent upstream links <NUM> enable multiple different network slices <NUM> to be used for the UE devices <NUM>. For example, <FIG> shows that the host UE device <NUM> has established multiple concurrent upstream links <NUM>-<NUM> to <NUM>-<NUM>. In this example, the first (default) upstream link <NUM>-<NUM> is a default upstream link for use with the first (default) network slice <NUM>-<NUM>. The host UE device <NUM> utilizes the default upstream link <NUM>-<NUM> and the default network slice <NUM>-<NUM> to wirelessly communicate its data. <FIG> also shows that the host UE device <NUM> selected the default network slice <NUM>-<NUM> for the first client UE device <NUM>-<NUM>. Therefore, data associated with the first client UE device <NUM>-<NUM> are also wirelessly communicated over the default network slice <NUM>-<NUM> using the default upstream link <NUM>-<NUM>. The host UE device <NUM> has selected the second network slice <NUM>-<NUM> and established a second upstream link <NUM>-<NUM> for the second client UE device <NUM>-<NUM>. Therefore, data associated with the second client UE device <NUM>-<NUM> are wirelessly communicated over the second network slice <NUM>-<NUM> using the second upstream link <NUM>-<NUM>.

The third network slice <NUM>-<NUM> and the fourth network slice <NUM>-<NUM> have been selected by the host UE device <NUM> for the third client UE device <NUM>-<NUM>. In this example, a separate upstream link <NUM>-<NUM> and <NUM>-<NUM> has been established for each of the third network slice <NUM>-<NUM> and the fourth network slice <NUM>-<NUM>. Therefore, some data associated with the third client UE device <NUM>-<NUM> are wirelessly communicated over the third network slice <NUM>-<NUM> using the third upstream link <NUM>-<NUM>, while other data associated with the third client UE device <NUM>-<NUM> are wirelessly communicated over the fourth network slice <NUM>-<NUM> using the fourth upstream link <NUM>-<NUM>. For example, different applications or services, such as live gaming and background downloading, on the third client UE device <NUM>-<NUM> may benefit from using different network slices <NUM>-<NUM>, <NUM>-<NUM> at the same time. Data associated with the gaming application/service can be wirelessly communicated over the third network slice <NUM>-<NUM> using the third upstream link <NUM>-<NUM>, while data associated with application/service downloading files in the background can be wirelessly communicated over the fourth network slice <NUM>-<NUM> using the fourth upstream link <NUM>-<NUM>.

The host UE device <NUM>, in at least some embodiments, establishes a separate upstream link <NUM> for each network slice <NUM> selected for the client UE devices <NUM>. In other embodiments, if the host UE device <NUM> selects the same network slice <NUM> for multiple client UE devices <NUM>, a common upstream link <NUM> is established for at least two of the multiple client UE devices <NUM> for wirelessly communicating data. In this embodiment, the common upstream link <NUM> is shared between the at least two client UE devices <NUM> for wireless communicating data over the common network slice <NUM>.

In at least some embodiments, the host UE device <NUM> may change the network slices <NUM> selected for a client UE device <NUM> based on a change in context <NUM> of the client UE device <NUM>. For example, a network slice <NUM> may be initially selected for client UE device <NUM>-<NUM> based on the context <NUM> indicating a game is currently being played on the client UE device <NUM>-<NUM>. However, after the user has finished playing the game, the host UE device <NUM> may request a high definition video stream. Therefore, the host UE device <NUM> releases the initial network slice <NUM> and initial upstream link <NUM>, which were servicing the gaming application, and selects a new network slice <NUM> and establishes a new upstream link <NUM> to service the high definition video stream. In at least some embodiments, if an upstream link <NUM> associated with newly selected network slice <NUM> has already been established for another client UE device <NUM>-<NUM>, the host UE device <NUM> may utilize this upstream link <NUM> for the client UE device <NUM>-<NUM>.

A client UE device <NUM>, in at least some embodiments, can request to release its current network slice(s) <NUM> and/or activate a new network slice(s) <NUM>. For example, the second client UE device <NUM>-<NUM> can send a request to the host UE device <NUM> using the tethered connection <NUM>-<NUM> to release the second network slice <NUM>-<NUM> activated for the second client UE device <NUM>-<NUM>. The host UE device <NUM> then proceeds to deactivate the second network slice <NUM>-<NUM> and, in at least some embodiments, the associated upstream link <NUM>-<NUM>. If the second client UE device <NUM>-<NUM> has requested a new network slice <NUM>, the host UE device <NUM> activates the new network slice <NUM> for the second client UE device <NUM>-<NUM> according to the network slice selection techniques described above and establishes a new upstream link <NUM> if needed.

<FIG> illustrates an example device diagram <NUM> of a UE device <NUM> (or <NUM>). In aspects, the device diagram <NUM> describes a UE device that can implement various aspects of network slicing for tethered client UE devices. The UE device <NUM> may include additional functions and interfaces that are omitted from <FIG> for the sake of clarity. The UE device <NUM>, in at least some embodiments, includes antennas <NUM>, a radio frequency (RF) front end <NUM>, and one or more RF transceivers <NUM> (e.g., a 3GPP Fourth Generation (<NUM>) Long Term Evolution (LTE) transceiver <NUM>-<NUM> and a <NUM> NR transceiver <NUM>-<NUM>) for communicating with a base station <NUM> in a RAN <NUM>, such as a <NUM> RAN and/or an E-UTRAN. The UE device <NUM>, in at least some embodiments, also includes one or more additional transceivers <NUM>-<NUM>, such as a local wireless network transceiver, for communicating over one or more local wireless networks (e.g., WLAN, Bluetooth, Near-Field Communication (NFC), a personal area network (PAN), Wireless Fidelity Direct (Wi-Fi-Direct), IEEE <NUM>. <NUM>, ZigBee, Thread, mmWave, and the like) with other UE devices <NUM>, such as those in a tethered configuration with the UE device <NUM>. The RF front end <NUM>, in at least some embodiments, couples or connects the LTE transceiver <NUM>-<NUM>, the <NUM> NR transceiver <NUM>-<NUM>, and the local wireless network transceiver <NUM>-<NUM> to the antennas <NUM> to facilitate various types of wireless communication.

In at least some embodiments, the antennas <NUM> of the UE device <NUM> include an array of multiple antennas configured similar to or different from each other. The antennas <NUM> and the RF front end <NUM>, in at least some embodiments, are tuned to, and/or can be tunable to, one or more frequency bands, such as those defined by the 3GPP LTE, 3GPP <NUM> NR, IEEE WLAN, IEEE WMAN, or other communication standards. In at least some embodiments, the antennas <NUM>, the RF front end <NUM>, the LTE transceiver <NUM>-<NUM>, the <NUM> NR transceiver <NUM>-<NUM>, and/or the local wireless network transceiver <NUM>-<NUM> are configured to support beamforming (e.g., analog, digital, or hybrid), or in-phase and quadrature (I/Q) operations (e.g., I/Q modulation or demodulation operations) for the transmission and reception of communications with the base station <NUM>. By way of example, the antennas <NUM> and the RF front end <NUM> operate in sub-gigahertz bands, sub-<NUM> bands, and/or above <NUM> bands defined by the 3GPP LTE, 3GPP <NUM> NR, or other communication standards.

In at least some embodiments, the antennas <NUM> include one or more receiving antennas positioned in a one-dimensional shape (e.g., a line) or a two-dimensional shape (e.g., a triangle, a rectangle, or an L-shape) for implementations that include three or more receiving antenna elements. While the one-dimensional shape enables the measurement of one angular dimension (e.g., an azimuth or an elevation), the two-dimensional shape enables two angular dimensions to be measured (e.g., both azimuth and elevation). Using at least a portion of the antennas <NUM>, the UE device <NUM> can form beams that are steered or un-steered, wide or narrow, or shaped (e.g., as a hemisphere, cube, fan, cone, or cylinder). The one or more transmitting antennas may have an un-steered omnidirectional radiation pattern or may be able to produce a wide steerable beam. Either of these techniques enables the UE device <NUM> to transmit a radar signal to illuminate a large volume of space. In some embodiments, the receiving antennas generate thousands of narrow steered beams (e.g., <NUM> beams, <NUM> beams, or <NUM> beams) with digital beamforming to achieve desired levels of angular accuracy and angular resolution.

The UE device <NUM>, in at least some embodiments, includes one or more sensors <NUM> implemented to detect various properties such as temperature, supplied power, power usage, battery state, or the like. The sensors <NUM> can include any one or a combination of temperature sensors, thermistors, battery sensors, and power usage sensors.

The UE device <NUM> also includes at least one processor <NUM> and a non-transitory computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM>, in at least some embodiments, is a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. The CRM <NUM>, in at least some embodiments, includes any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data <NUM> of the UE device <NUM>. The device data <NUM> includes, for example, user data, multimedia data, beamforming codebooks, applications, and/or an operating system of the UE device <NUM>, which are executable by the processor <NUM> to enable user-plane communication, control-plane signaling, and user interaction with the UE device <NUM>.

The CRM <NUM>, in at least some embodiments, also includes a communication manager <NUM>. Alternatively, or additionally, the communication manager <NUM>, in at least some embodiments, is implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE device <NUM>. In at least some embodiments, the communication manager <NUM> configures the RF front end <NUM>, the LTE transceiver <NUM>-<NUM>, the <NUM> NR transceiver <NUM>-<NUM>, and/or the local wireless network transceiver <NUM>-<NUM> to perform one or more wireless communication operations.

In at least some embodiments, the CRM <NUM> further includes a tethering manager <NUM>, a network slice (NS) selection manager <NUM>, device context information <NUM>, network slice context information <NUM>, selection policies <NUM>, and so on. Alternately, or additionally, one or more of these components, in at least some embodiments, are implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE device <NUM>. The tethering manager <NUM> and network slice selection manager <NUM>, in at least some embodiments, configures the RF front end <NUM>, the transceiver(s) <NUM>, processor <NUM>, and/or other components of the UE device <NUM> to implement the techniques described herein for utilizing network slicing with tethered client UE devices <NUM>.

<FIG> and <FIG> together illustrate an example ladder diagram depicting data and control transactions between devices engaged in tethered connection network slicing in accordance with at least some embodiments. It should be understood the present disclosure is not limited to the illustrated sequence of the transactions shown in <FIG> and <FIG>. One or more of the transactions may be performed in a different order than shown, and/or multiple transactions may be performed in parallel. The host UE device <NUM> attaches <NUM> to the cellular network <NUM> using techniques known in the art. The RAN <NUM>, in at least some embodiments, transmits <NUM> network slice (NS) information <NUM> information to the host UE device <NUM>. The network slice information <NUM> includes, for example, a list of available network slices <NUM> and a context <NUM> of each available network slice <NUM>, such as parameters, attributes, capabilities, requirements, and so on of the network slices <NUM>.

The host UE device <NUM>, in at least some embodiments, selects <NUM> a first (default) network slice <NUM>-<NUM> from the available network slices <NUM>. In other embodiments, the RAN <NUM> or a core network component <NUM> selects a default network slice <NUM>-<NUM> for the host UE device <NUM>. The host UE device <NUM> establishes <NUM> a default upstream link <NUM>-<NUM> and activates the default network slice <NUM>-<NUM>. In some embodiments, the default upstream link <NUM>-<NUM> may be established before selecting the default network slice <NUM>-<NUM>. A first client UE device <NUM>-<NUM> establishes <NUM> a first tethered connection <NUM>-<NUM> with the host UE device <NUM>. At least a second client UE device <NUM>-<NUM> also establishes <NUM> a second tethered connection <NUM>-<NUM> with the host UE device <NUM>. In at least some embodiments, one or more of the client UE devices <NUM> may establish a tethered connection <NUM> with the host UE device <NUM> before a default network slice <NUM>-<NUM> being selected or activated.

In at least some embodiments, the first client UE device <NUM>-<NUM>, requests <NUM> access to the cellular network <NUM>. The request can be, for example, an explicit request or an implicit request, such as the transmission of a data stream. Responsive to receiving the request, the host UE device <NUM> selects <NUM>, in this example, the default network slice <NUM>-<NUM> for the first client UE device <NUM>-<NUM> based on network slice selection policies and the context <NUM> of the first client UE device <NUM>-<NUM> and/or the context <NUM> of the network slices <NUM>. For example, the context <NUM> of the first client UE device <NUM>-<NUM> may not have satisfied any of the non-default network slices <NUM>, resulting in the default network slice <NUM>-<NUM> being selected. The first client UE device <NUM>-<NUM> transmits <NUM> a first data stream to the host UE device <NUM> using the first tethered connection <NUM>-<NUM>. The host UE device <NUM> receives the first data stream and transmits <NUM> the first data stream over the default network slice <NUM>-<NUM> using the default upstream link <NUM>-<NUM>. A second data stream is received <NUM> by the host UE device <NUM> over the default network slice <NUM>-<NUM>. The host UE device <NUM> determines the second data stream is for the first client UE device <NUM>-<NUM> and transmits <NUM> the second data stream to the first client UE device <NUM>-<NUM> using the first tethered connection <NUM>-<NUM>.

In at least some embodiments, the second client UE device <NUM>-<NUM> requests <NUM> access to the cellular network <NUM>. The request can be, for example, an explicit request or an implicit request, such as the transmission of a data stream. Responsive to receiving the request, the host UE device <NUM> selects <NUM> one or more network slices for the second client UE device <NUM>-<NUM>, in this example, a second network slice <NUM>-<NUM> and a third network slice <NUM>-<NUM> for the second client UE device <NUM>-<NUM>. For example, the context <NUM> of the second client UE device <NUM>-<NUM> may indicate that two applications (or services), such as music streaming and gaming, are executing on the second client UE device <NUM>-<NUM>. Therefore, the host UE device <NUM> selects the second network slice <NUM>-<NUM> to wirelessly communicate data associated with the first application and select the third network slice <NUM>-<NUM> for wirelessly communicating data associated with the second application. In some embodiments, a network slice <NUM> is selected for each application.

The host UE device <NUM> establishes <NUM> a second upstream link <NUM>-<NUM> and a third upstream link <NUM>-<NUM>, and activates the second network slice <NUM>-<NUM> and the third network slice <NUM>-<NUM>. The second upstream link <NUM>-<NUM> is associated with the second network slice <NUM>-<NUM>, and the third upstream link <NUM>-<NUM> is associated with the third network slice <NUM>-<NUM>. In this example, the first upstream link <NUM>-<NUM>, the second upstream link <NUM>-<NUM>, and the third upstream <NUM>-<NUM> are concurrently active or maintained. The second client UE device <NUM>-<NUM> transmits <NUM> a third data stream to the host UE device <NUM> using a second tethered connection <NUM>-<NUM>. The second client UE device <NUM>-<NUM> also transmits <NUM> a fourth data stream to the host UE device <NUM> using the second tethered connection <NUM>-<NUM>.

The host UE device <NUM> receives the third data stream and transmits <NUM> the third data stream over the second network slice <NUM>-<NUM> using the second upstream link <NUM>-<NUM>. The host UE device <NUM> receives the fourth data stream and transmits <NUM> the fourth data stream over the third network slice <NUM>-<NUM> using the third upstream link <NUM>-<NUM>. In at least some embodiments, the host UE device <NUM> determines which upstream link <NUM> and network slice <NUM> is associated with a data stream received from a client UE device <NUM> based on, for example, a context of the data stream. A context of a data stream includes, for example, the type of data being transmitted, the application/service associated with the data, source IP address, destination IP address, and so on. The host UE device <NUM> receives <NUM> a fifth data stream over the second network slice <NUM>-<NUM>. The host UE device <NUM> also receives <NUM> a sixth data stream over the third network slice <NUM>-<NUM>. The host UE device <NUM> determines the fifth data stream is for the second client UE device <NUM>-<NUM> and transmits <NUM> the fifth data stream to the second client UE device <NUM>-<NUM> using the second tethered connection <NUM>-<NUM>. The host UE device <NUM> also determines the sixth data stream is for the second client UE device <NUM>-<NUM> and transmits <NUM> the sixth data stream to the second client UE device <NUM>-<NUM> using the second tethered connection <NUM>-<NUM>.

<FIG> and <FIG> together illustrate, in flow chart form, one example method <NUM> of a host UE device <NUM> implementing network slicing for tethered client UE devices <NUM>. The techniques described in the example method <NUM> have been previously discussed in detail with respect to <FIG>. It should be understood the present disclosure is not limited to the illustrated sequence of the operations shown in <FIG> and <FIG>. One or more of the operations may be performed in a different order than shown, and multiple operations may be performed in parallel.

The method <NUM> is initiated in response to the host UE device <NUM> determining that a tethering mode should be enabled. In response to this determination, the host UE device <NUM> enables the tethering mode at block <NUM>. The host UE device <NUM>, at block <NUM>, attaches to the cellular network <NUM>. The host UE device <NUM>, at block <NUM>, determines if the cellular network <NUM> is a <NUM> NR Standalone (SA) network. If the result of this determination is negative (e.g., the cellular network <NUM> is an LTE network or a <NUM> NR Non-Standalone (NSA) network), the host UE device <NUM>, at block <NUM>, uses a default upstream link <NUM>-<NUM> and default network slice <NUM>-<NUM> for all tethered client UE devices <NUM>. The host UE device <NUM> continues with this configuration until a determination is made at block <NUM> that tethering is no longer enabled. When a determination is made that tethering is no longer enabled, the process then ends at block <NUM>.

If the host UE device <NUM> determines that the cellular network <NUM> is a <NUM> NR SA network, the host UE device <NUM> obtains network slicing information <NUM> at block <NUM>. The network slice information <NUM>, in at least some embodiments, comprises a list <NUM> of available network slices <NUM> and context information <NUM> for each available network slice <NUM>. The host UE device <NUM>, at block <NUM>, selects a default network slice <NUM>-<NUM> based on the network slicing information <NUM>. The host UE device <NUM>, at block <NUM>, establishes a default upstream link <NUM>-<NUM> and activates the default network slice <NUM>-<NUM>. The host UE device <NUM>, at block <NUM>, establishes a tethered (downstream) link <NUM> with one or more client UE devices <NUM>. Responsive to one or more tethered connections <NUM> having been established, the host UE device <NUM>, at block <NUM>, broadcasts the list <NUM> available network slices <NUM> and the context information <NUM> (e.g., capabilities) of each network slice <NUM>.

The host UE device <NUM>, at block <NUM>, determines if a network slice selection was received from the client UE device <NUM>. If a network slice selection was not received from the client UE device <NUM>, the flow continues to block <NUM> of <FIG>. However, if a network slice selection was received, the host UE device <NUM>, at block <NUM>, updates one or more network slice selection policies <NUM> to indicate that the host UE device <NUM> has requested one or more specific network slices <NUM> or types of network slices. The flow then continues to block <NUM> of <FIG>. The host UE device <NUM>, at block <NUM>, also determines if a network slice selection policy <NUM> was received from the client UE device <NUM>. If a network slice selection policy <NUM> was not received from the client UE device <NUM>, the flow continues to block <NUM> of <FIG>. However, if a network slice selection policy <NUM> was received, the host UE device <NUM>, at block <NUM>, updates/customizes one or more network slice selection policies <NUM> based on the network slice selection policy <NUM> received from the client UE device <NUM>. The flow then continues to block <NUM> of <FIG>.

The host UE device <NUM>, at block <NUM>, analyzes one or more network slice selection policies <NUM> to select a network slice <NUM> for one or more client UE devices <NUM>. The selection policies <NUM>-<NUM> can include global selection policies and/or UE specific selection policies <NUM>-<NUM>. If the client UE device <NUM> provided selection data <NUM>, such as a network slice selection and/or a custom selection policy, the host UE device <NUM> analyzes this selection data <NUM> when selecting a network slice <NUM>. In at least some embodiments, the host UE device <NUM> analyzes selection criteria <NUM> of the selection policies <NUM> in view of a context <NUM> of the client UE device <NUM> and/or a context <NUM> of the network slices <NUM>.

The host UE device <NUM>, at block <NUM>, determines if the selection criteria <NUM> of any selection policies associated with the non-default network slices <NUM>-<NUM> to <NUM>-<NUM> have been satisfied. If the result of this determination is negative, the host UE device <NUM>, at block <NUM>, selects the default network slice <NUM>-<NUM>. The host UE device <NUM>, at block <NUM>, proceeds to transmit and receive data for the client UE device <NUM> over the default network slice <NUM>-<NUM> using the default upstream link <NUM>-<NUM>. If the selection criteria <NUM> was satisfied for one or more selection policies <NUM>, the host UE device <NUM>, at block <NUM>, selects one or more non-default network slices <NUM>-<NUM> to <NUM>-<NUM> for the client UE device <NUM>. The host UE device <NUM>, at block <NUM>, establishes an upstream link <NUM>-<NUM> to <NUM>-<NUM> for each of the selected non-default network slices <NUM>-<NUM> to <NUM>-<NUM>. The host UE device <NUM>, at block <NUM>, proceeds to transmit and receive data for the client UE device <NUM> over the one or more selected non-default network slices <NUM>-<NUM> to <NUM>-<NUM> using the associated upstream link(s) <NUM>-<NUM> to <NUM>-<NUM>.

The host UE device <NUM>, at block <NUM>, determines if the client UE device <NUM> has requested to release a network slice <NUM>. If the client UE device <NUM> has requested to release a network slice <NUM>, the host UE device <NUM>, at block <NUM>, releases the network slice <NUM>, and the flow proceeds to block <NUM>. If the client UE device <NUM> has not requested to release a network slice <NUM>, the host UE device <NUM>, at block <NUM>, determines if the client UE device <NUM> has requested to activate a new network slice <NUM>. If the client UE device <NUM> has requested to activate a new network slice <NUM>, the flow returns to block <NUM>, and the host UE device <NUM> determines if the requested network slice <NUM> can be selected for the client UE device <NUM>. If the client UE device <NUM> has not requested a new network slice <NUM>, the host UE device <NUM>, at block <NUM>, determines if tethering is still enabled. If tethering is still enabled, the flow returns to block <NUM> or block <NUM>, and the host UE device <NUM> continues to transmit and receive data for the client UE device <NUM> over the selected network slice(s) <NUM> using the associated upstream link(s) <NUM>. If tethering is no longer enabled, the process ends at block <NUM>.

In some embodiments, certain aspects of the techniques described above are implemented by one or more processors of a processing system executing software. The software includes one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, for example, a magnetic or optical disk storage device, solid-state storage devices such as Flash memory, a cache, random access memory (RAM) or other non-volatile memory device or devices, and the like. The executable instructions stored on the non-transitory computer-readable storage medium can be in source code, assembly language code, object code, or another instruction format that is interpreted or otherwise executable by one or more processors.

A computer-readable storage medium includes any storage medium or combination of storage media accessible by a computer system during use to provide instructions and/or data to the computer system. Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-ray disc), magnetic media (e.g., floppy disc, magnetic tape, or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media. The computer-readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g., a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

Claim 1:
A method, performed by a host user equipment, UE, comprising:
establishing a first tethered connection between the host UE and at least one client UE;
identifying a plurality of network slices provided by a network, wherein the host UE wirelessly communicates with the network; and
selecting at least a first network slice from the plurality of network slices for use by the at least one client UE to communicate with the network via the host UE.