Handover of service from WTRU to PIN and handover from PIN to WTRU

Abstract

A wireless transmit / receive unit (WTRU) may receive a service handover message from a network node that requests handover of a session from the WTRU to a personal Internet of Things (IoT) network (PIN) element (PINE). The PINE may be associated with the PIN. The WTRU may determine a second WTRU that supports the session handover. The WTRU may transmit an acknowledgement message to the network node, the acknowledgement message indicating a session identifier and / or an indication indicating that the second WTRU supports the session handover. The WTRU may transmit a configuration message to the second WTRU, the configuration message indicating the PINE identifier, the session identifier, and / or a request to support the session handover. The WTRU may receive an acknowledgement message from the second WTRU, the acknowledgement message indicating that the second WTRU has been configured to support the session handover. The WTRU may transmit a service handover response message to the network node.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 339,817, filed on May 9, 2022, the contents of which are incorporated herein by reference. Background Art

[0003] Mobile communications using wireless communications continue to evolve. The fifth generation may be referred to as 5G. Previous (legacy) mobile communications may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the invention

[0004] Described herein are systems, methods, and means for switching services, such as existing services and / or streaming services, from a wireless transmit / receive unit (WTRU) to a personal Internet of Things (IoT) network (PIN) and / or from a PIN to a WTRU.

[0005] The WTRU may receive a service handover request message. For example, the WTRU may receive a service handover request message from a network node. The service handover request message may request the WTRU to handover a session from the WTRU to a PIN element (PINE). The PINE may be associated with the PIN. In an example, the WTRU may be a PINE with management capabilities (PEMC). In an example, the network node may be a PIN server (PCS).

[0006] The service handover request message may be and / or may include an application session identification (ID), information associated with a destination PINE, an indication of whether the application session may be split between two or more PINEs, a description associated with the session, and / or a token indicating that the WTRU (e.g., the PINE at which the session may be terminated) may be an endpoint of the session. For example, the information associated with the destination PINE may be and / or may include an Internet Protocol (IP) address associated with the destination PINE, a port number associated with the destination PINE, or a Uniform Resource Locator (URL) associated with the destination PINE, and wherein the description associated with the session includes an Internet Protocol (IP) 4-tuple.

[0007] The WTRU (e.g., the first WTRU and / or the PEMC) may determine a second WTRU. For example, the second WTRU may be a PINE with gateway capabilities (PEGC). The second WTRU may support session switching. For example, the second WTRU may support session switching to a PINE within the PIN by accepting the application session and forwarding it to the selected PINE. In an example, the WTRU (such as the first WTRU) may determine one or more WTRUs (e.g., PEGCs) associated with the PIN. The WTRU (e.g., the first WTRU) may determine session capability criteria for supporting the session. For example, the session capability criteria for supporting the session may be and / or may include capabilities for supporting the session, reachability information associated with the PINE, and / or a PIN policy. The capability to support the session may be and / or may include a computing capability associated with the WTRU (e.g., PEGC) that may support the session, a memory capability associated with the WTRU (e.g., PEGC) that may support the session, a bandwidth capability associated with the WTRU (e.g., PEGC) that may support the session, and / or a filtering capability associated with the WTRU (e.g., PEGC) that may support the session, etc. As described herein, the capability may be associated with a threshold level. For example, based on the threshold level, such as above the threshold level, the WTRU may determine that the WTRUs (e.g., PEGCs) may meet the session capability criteria and may be candidates for session handover.

[0008] The WTRU (e.g., the first WTRU and / or the PEMC) may determine whether the capabilities of the second WTRU (e.g., the PEGC associated with the PIN) satisfy the session capability criteria. Based on determining that the capabilities of the second WTRU (e.g., the PEGC associated with the PIN) satisfy the session capability criteria, the WTRU (e.g., the first WTRU and / or the PEMC) may determine the second WTRU from the one or more WTRUs (e.g., the one or more PEGCs associated with the PIN). The WTRU (e.g., the first WTRU and / or the PEMC) may determine a PINE identifier associated with the second WTRU.

[0009] The WTRU (e.g., the first WTRU) may transmit a confirmation message to the network node. The confirmation message may indicate a session identifier and / or an indication that the second WTRU (e.g., the PEGC) supports the session handover. The session identifier may be and / or may include a termination identifier associated with the second WTRU (e.g., the PEGC), reachability information associated with the second WTRU (e.g., the PEGC), and / or reachability information associated with the PINE. The reachability information associated with the second WTRU (e.g., the PEGC) may be and / or may include an IP address associated with the second WTRU (e.g., the PEGC), a port number associated with the second WTRU (e.g., the PEGC), and / or a URL associated with the second WTRU (e.g., the PEGC). The reachability information associated with the PINE may be and / or may include an IP address associated with the PINE, a port number associated with the PINE, and / or a URL associated with the PINE.

[0010] The WTRU (e.g., the first WTRU) may transmit a configuration message to the second WTRU (e.g., the PEGC). The configuration message may indicate a PINE identifier, a session identifier, and / or a request to support handover of the session. For example, the configuration message may be and / or may include a list of PINE IDs (PEIDs), an IP address associated with the PINE, a port number associated with the PINE, and / or a URL associated with the PINE. The configuration may be and / or may include an indication of whether the session may be split (e.g., may need to be split) to two or more PINEs.

[0011] The WTRU (e.g., the first WTRU) may receive a confirmation message from the second WTRU (e.g., the PEGC). The confirmation message may indicate that the second WTRU (e.g., the PEGC) has been configured to support the session handover by forwarding data associated with the session to the PINE. For example, the configuration may involve establishing endpoint identifiers of a network node and / or a PINE, for example to allow receiving and / or forwarding application data, so as to establish a forwarding table to forward the application data from the network node to the PINE. The WTRU (e.g., the first WTRU) may transmit a service handover response message to the network node. The service handover response message may indicate that the second WTRU (e.g., the PEGC) has been configured to forward the data associated with the session to the PINE. For example, the configuration may involve establishing endpoint identifiers of a network node and / or a PINE, for example to allow receiving and / or forwarding application data, so as to establish a forwarding table to forward the application data from the network node to the PINE.

[0012] In an example, the WTRU may discover a suitable PIN that may support and / or enhance the application experience. An ongoing application session may be switched to the suitable PIN. The WTRU may request a service switch through a PIN application server (AS), which may perform a service switch process. For example, the service switch process described herein may be and / or may include a service to be switched from the WTRU to the PIN. In an example, the WTRU may request a service switch through a PIN element (PINE) such as a PEMC. For example, the PEMC may perform a service switch process (e.g., switching a service from the WTRU to the PIN). In an example, the WTRU may request a service switch through a PIN AS. For example, the PIN AS may perform the service switch process (e.g., switching a service from the PIN to the WTRU). BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

[0014] Figure 1B is an example of a method that can be used according to an embodiment of the present invention. Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within an illustrated communication system.

[0015] Figure 1C is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of an example Radio Access Network (RAN) and an example Core Network (CN) for use within the illustrated communication system.

[0016] Figure 1D is an example of a method that can be used according to an embodiment of the present invention. Figure 1A System diagram of an additional example RAN and an additional example CN for use within the illustrated communication system.

[0017] Figure 2 An example of a home automation Personal Internet of Things Network (PIN) is illustrated.

[0018] Figure 3 An example of a wearable PIN is illustrated.

[0019] Figure 4 An example of a PIN architecture is illustrated.

[0020] Figure 5 An example session flow for switching a service (eg, a session provided by an application server (AS)) from a WTRU to a PIN is illustrated.

[0021] Figure 6 One or more examples of PIN discovery and PIN selection by a WTRU are illustrated.

[0022] Figure 7 An example of service handover from a WTRU to a PIN performed by a PIN server is illustrated.

[0023] Figure 8 An example of service handover from WTRU to PIN performed by PEMC is illustrated.

[0024] Fig. 9 An example of service handover from a PIN to a WTRU performed by a PIN server is illustrated. DETAILED DESCRIPTION

[0025] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0026] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0027] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0028] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

[0029] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0030] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0033] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example using the dual connectivity (DC) principle. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0034] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0035] Figure 1AThe base station 114b in may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc., using any suitable RAT. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.11) to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a microcell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0036] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the text and video sections of the RAN 104 / 113, the CN 106 / 115 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0037] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0038] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0039] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0040] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0041] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station by air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In one embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, IR, UV or visible light signals. In another embodiment, the send / receive element 122 may be configured to send and / or receive both RF signals and optical signals. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0042] Although the transmit / receive element 122 Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0043] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0044] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0045] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0046] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0047] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0048] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0049] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0050] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0051] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0052] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0053] The MME 162 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0054] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0055] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0056] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0057] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communication interface with a communication network.

[0058] In a representative embodiment, the other network 112 may be a WLAN.

[0059] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0060] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. In the case where the primary channel is listened / detected and / or determined to be busy by a specific STA, the specific STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0061] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0062] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitting STA. At the receiver of the receiving STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0063] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0064] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

[0065] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0066] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 in accordance with an embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0067] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 108b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0068] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmit time intervals (TTIs) of varying or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths over time).

[0069] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0070] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0071] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0072] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0073] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure the traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy implementation and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0074] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184a, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0075] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0076] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a-d, base station 114a-b, evolved Node B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein. The simulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0077] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.

[0078] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0079] Figure 2 An example of a home automation personal Internet of Things (IoT) network (PIN) is illustrated. One or more PINs may be configured to switch services from a WTRU and / or switch services to a WTRU. One or more devices that communicate using a cellular network (such as a traditional cellular network) may utilize Internet of Things (IoT) features. The one or more IoT-enabled devices may provide a better user experience. In an example, the one or more IoT-enabled devices may provide power consumption performance and / or network efficiency. For example, the one or more IoT-enabled devices may have better power consumption performance and / or improved network efficiency for one or more batch operations.

[0080] One or more WTRUs with IoT capabilities may be organized in a PIN. For example, if one or more IoT devices are deployed in an environment such as a private environment, the one or more WTRUs with IoT capabilities may be organized in a PIN. In an example, in a home environment, security sensors, smart lights, smart plugs, printers, and / or mobile phones, etc. may be managed by WTRUs such as gateways (e.g., residential gateways) and / or may communicate with each other. The one or more devices in the home environment may be examples of PINs. A device (e.g., each device) may be a PIN element (PINE). One or more different PIN elements (PINEs) may have one or more different capabilities (e.g., corresponding different capabilities). A PIN gateway (PIN GW) may provide one or more connections between PIN elements and / or a connection between a network (e.g., a 5G network) and one or more PIN elements. A PINE may have management capabilities. For example, a PINE with management capabilities (PIN Mgmt or PEMC) may be and / or may include a PIN element having (e.g., enabling and / or providing components for) an authorized administrator to configure and / or manage a PIN. In an example, a WTRU and / or a PINE (such as a PINE acting as a PIN GW) may support PIN management functions and / or may be a PIN Mgmt or a PEMC.

[0081] Figure 3 An example of a wearable PIN is illustrated. One or more wearable devices may be of PIN type. For example, one or more wearable devices may be PIN elements. A WTRU (e.g., a smartphone) may act as a PIN element (PINE) with gateway capabilities (PIN GW) and / or a PIN element with management capabilities (PIN Mgmt or PEMC). If a WTRU (such as a smartphone) acts as a PIN GW and / or PIN Mgmt, other wearable items (such as smart watches, virtual reality (VR) augmented reality (AR) glasses, and / or audio devices, etc.) may communicate with each other in the PIN and / or via a PIN such as Figure 3 The illustrated network (e.g., a 5G network) communicates with other WTRUs.

[0082] The PIN may be described by an architecture. The PIN may include a PIN element (PE or PINE), a PIN management (PIN Mgmt or PEMC), and / or a PIN gateway (PIN GW). The PIN element may be a WTRU and / or one or more other devices (e.g., non-3GPP devices) that may communicate within the PIN. The PIN management device may be a PIN element that has the capability to manage the PIN. The PIN GW may be a PIN element that is configured (e.g., has the capability) to provide connectivity to and / or from a network (such as a 5G network) to other PIN elements.

[0083] Figure 4 An example of a PIN architecture is shown. In the example, Figure 4 As illustrated, PIN elements can communicate with each other via a PIN GW. Figure 4 As illustrated, the PIN elements may communicate directly with each other. The PIN elements may communicate with a system (e.g., a 5G system) to obtain services (e.g., 5G services) and / or communicate with a data network (e.g., via a 5G core network).

[0084] One or more PIN elements with management capabilities and / or one or more PIN elements with gateway capabilities may be WTRUs. One or more communications within the PIN may be performed via non-3gpp communications such as WiFi, Bluetooth, etc.

[0085] The PIN application framework (PINAPP) may provide application layer support to the PIN, such as a PIN application layer functional model. The PINAPP may provide one or more of: information and / or support from a network supporting PIN deployment (e.g., a 3GPP network); service and / or application discovery within the PIN; and / or service and / or application discovery by the WTRU outside the PIN via a network (e.g., a 3GPP network).

[0086] The PIN network may be managed by a mobile network operator (MNO). For example, the PIN network may be managed by the MNO to support one or more application services (e.g., gaming services and / or telehealth services, etc.) provided by one or more managed service providers. One or more users (e.g., at home, in a business, and / or elsewhere) may establish a PIN to operate the application service.

[0087] One or more application service providers may supply one or more PIN elements. For example, a user may purchase one or more PIN elements (e.g., off-the-shelf). One or more PIN elements (PINEs) may be mobile network devices (e.g., 3GPP devices) or non-mobile network devices (e.g., non-3GPP devices).

[0088] One or more users may run one or more applications in the WTRU and / or other devices (such as personal devices). For example, for a better experience, the user may want to switch services from the personal device to a device that is part of the PIN. For example, a user watching streaming video on a smartphone may want to switch to a PIN with a larger display and / or audio speakers (e.g., a PINE in the PIN).

[0089] Figure 5 An example session flow for switching a service from a WTRU to a PIN is illustrated. Figure 5 As illustrated, a session (e.g., an original session or an ongoing session) (e.g., flow 1) provided by an application server (AS) to a WTRU may be switched to a PIN. If the flow is switched to a PIN, a gateway-capable PIN (PEGC) may be the termination point (e.g., from the perspective of a network such as a gateway-capable core network or 5GC). The switch to a PIN / PEGC may be initiated by the network (e.g., a gateway-capable core network or 5GC) via Figure 5 The illustrated service flows (eg, flow 2, flow 3, and / or flow 4) are implemented in one or more exemplary ways.

[0090] like Figure 5 As illustrated, the WTRU may have a connection to the AS (e.g., the direct connection illustrated in Flow 1). For example, if the WTRU is outside the PIN, the WTRU may have a direct connection to the AS (e.g., Flow 1). The WTRU may stream video from a server.

[0091] In an example, the WTRU may move into the coverage of a PIN. In an example, the WTRU may be outside the coverage of a PIN, and the PIN may have one or more capabilities, such as a large display (TV), high-fidelity (HiFi) audio (e.g., speakers), to terminate application traffic from an AS (such as a video server).

[0092] Switching may occur in the opposite direction. For example, flows associated with applications running on a PIN element (PINE) (such as a large display and / or audio speakers) may be moved to the WTRU (e.g., when the user moves away from the home environment).

[0093] like Figure 5 As illustrated, a system (e.g., a 5G system (5GS)) may implement handover in one or more directions (e.g., in any direction). The system (e.g., 5GS) may be aware of (e.g., know) one or more endpoints that the handover may terminate (e.g., may need to terminate). One or more application-level processes may be used to provide information about one or more flow endpoints to the system (e.g., 5GS).

[0094] like Figure 5 As illustrated, a system (e.g., 5GS) may terminate a stream that is switched to a PEGC. The stream may be split into two or more substreams and may be terminated in two or more PINEs. The PEGC may split (e.g., be configured to split) the stream into one or more substreams and may be terminated in one or more PINEs. Information indicating how to split and / or which PINE or PINEs to terminate may be provided to the PEGC by a server (e.g., a PIN server). The PEGC may manage one or more synchronizations between the substreams. For example, the PEGC may manage one or more synchronizations between the substreams by obtaining information from a server such as a PIN server.

[0095] One or more of the following may be considered to enable service switching: the WTRU may be aware of the availability of PINs that can support service switching; the system (e.g., 5GS) may use one or more application-level mechanisms to establish service switching; and / or PEGC may be enabled to split a stream into two or more sub-streams and may terminate towards two or more PINes.

[0096] The WTRU may discover the PIN. In an example, the WTRU may contact an AS (such as a PIN AS) to discover the PIN. The PIN may support service switching. In an example, if the WTRU is in the vicinity of a PIN that is capable of performing a service switching procedure, the WTRU may subscribe to an AS (such as a PIN AS) to be notified. The PIN AS may provide information about one or more devices in the PIN that may provide one or more types of services (e.g., video and / or audio streaming).

[0097] In addition and / or as an alternative to contacting the PIN AS described herein, the WTRU may contact the PEMC. In an example, the WTRU may discover and / or join the PIN locally by contacting the PEMC. In an example, if service switching is allowed, the WTRU may subscribe to the PEMC to be notified. If the WTRU receives the notification, the WTRU may contact the PEMC to trigger the service switching process.

[0098] In an example, the service switching may be triggered by an application mechanism. The WTRU may trigger the service switching process. For example, the WTRU may trigger the service switching by transmitting a request to an AS (such as a PIN AS). The PIN AS may initiate the service switching process as described herein. For example, the PIN AS may initiate the service switching after receiving the request. The PIN AS may provide information to one or more PINAPP functions (e.g., PINAS, PEMC and / or PEGC, etc.) to perform the service switching (e.g., at the network level).

[0099] In an example, the WTRU may trigger a service switch by contacting the PEMC. The PEMC may initiate the service switch. For example, after receiving the request from the WTRU, the PEMC may initiate the service switch process.

[0100] The WTRU may participate in PIN discovery and / or selection. Figure 6 One or more examples of PIN discovery and selection by a WTRU are illustrated.

[0101] In the example, Figure 6 As illustrated in Example 1 of , the WTRU may be outside the home environment, away from the PIN, or within the coverage of the PIN. The WTRU may want to switch the service from the WTRU to the PIN device. The WTRU may initiate PIN discovery using a PIN server (PCS). The WTRU may transmit a message, such as a discovery PIN message. The discovery PIN message may be and / or may include an indication that the WTRU wants to discover a PIN that can support an application in a certain location. The message may be and / or may include location information and / or application capabilities (e.g., application requirements). The location information may be and / or may include the current location of the WTRU and / or a location specified by the user. The application capabilities (e.g., application requirements) may be and / or may include one or more PINAPP capabilities (e.g., one or more required PINAPP capabilities), such as display characteristics and / or audio characteristics, etc.

[0102] Based on the one or more location information details, the PIN server may search the PIN database and may determine one or more available PINs in the specified location. Among the one or more available PINs, the PIN server may check the subscription and / or PIN policy associated with one or more WTRUs. The PIN server may determine whether the WTRU is allowed to use the PIN service. If the WTRU is allowed to use the PIN service, the PIN server may select a PIN. The PIN server may transmit a PIN ID (e.g., a PIN identifier) ​​and / or one or more available PINs in the PIN to the WTRU.

[0103] Based on the location information and / or application service capabilities (e.g., application service requirements), the PIN server may transmit one or more of the following information to the WTRU: the discovered PIN ID; and / or one or more details of the PINAPP capabilities and / or one or more corresponding PEIDs. For example, the one or more corresponding PEIDs may be and / or may include one or more device IDs, one or more IP addresses, and / or one or more port numbers, etc.

[0104] In the example, Figure 6As illustrated in Example 2 of , discovery and / or switching may be triggered by a PIN server based on the location of the WTRU. The WTRU may subscribe to a PIN server in a location specified by a user. For example, if service switching is available based on the availability of one or more PIN devices that support the service in the location specified by the user, the PIN server may notify the WTRU.

[0105] The PIN server may obtain the location information of the WTRU using one or more location services supported by a system such as 5GS. If the WTRU is at a specified location, the PIN server may be notified that the WTRU has moved to the specified location. The PIN server may check a PIN database and may determine one or more available PINs in the location at this time. Based on the WTRU subscription and / or PIN policy, the PIN server may notify the WTRU if the WTRU is allowed to use a PIN.

[0106] If the WTRU is at a certain location and / or a PIN that can support the service is available, the PIN server may transmit a notification to the WTRU, such as a service switching availability notification. The notification may be and / or may include information about one or more devices that can support the service, such as a PIN ID, a PEID (such as a device ID) and / or an IP address and port number, etc. The WTRU may transmit a message, such as a confirmation message, to the PIN server to indicate that the WTRU is undergoing a service switching.

[0107] In the example, Figure 6 As illustrated in Example 3, if the WTRU comes near a PIN, the WTRU may discover the PIN and / or register with the PIN. The WTRU may use PCM / PEMC to subscribe to service switching availability. The WTRU may provide one or more service details, such as one or more service types and / or one or more required PINAPPs (e.g., a display and / or audio speakers, etc.). The PCM may notify the WTRU whether the PINAPP / PINE is available to support service switching. The PCM may transmit one or more of the following: one or more PINAPP details, such as one or more display characteristics and / or one or more speaker characteristics; and / or one or more corresponding PEIDs, such as one or more device IDs and / or one or more IP addresses and port numbers, etc.

[0108] The WTRU may initiate a service switch and the PIN server may perform the service switch. Figure 7 As illustrated, the PIN server may switch the service from the WTRU to the PIN. Figure 7 An example of service switching performed by the PIN server is illustrated. May or may not be performed (e.g., skipped) Figure 7 One or more processes are illustrated.

[0109] The WTRU may select a PIN. Figure 7 As illustrated, after PIN selection, the WTRU may transmit a request, such as a service switching request, to the PCS / PIN server. The service switching request may be and / or may include information about the service to be switched. The information about the service to be switched may be and / or may include an application session ID, a destination PIN ID, and / or a description of the session. In an example, the description of the session may be and / or may include (e.g., an IP 4-tuple describing the session. In an example, the description of the session (e.g., an IP 4-tuple) may be and / or may include the IP address of the WTRU, the IP address of the server providing the service, a WTRU port number that may be associated with the service, and / or one or more port numbers on the server that may be associated with the service.

[0110] If the WTRU is allowed to request a service switch to the destination PIN, the PIN server may verify the subscription and / or PIN policy associated with the WTRU. The PIN server may verify whether the PIN can support the requested service switch. If the WTRU is allowed to request a service switch and one or more PINs are available to support the service switch, the PIN server may transmit a response, such as an OK response, to the WTRU.

[0111] The PIN server may start the service handover process by looking up the destination PIN ID transmitted by the WTRU in the PIN database. The PIN server may select the PINE whose application session is to be terminated, for example, based on the application session ID and / or the capabilities of the PINE. The PIN server may use the application session ID to find out one or more details of the application session, such as video quality and / or audio quality, etc. The PIN server may match the PINE capabilities to select the terminating PINE.

[0112] Based on the application level communication, the PIN server and / or the application server may determine whether the application session may be split and / or whether one or more PINEs are available in the PIN. Based on the application level information, if one or more PINEs (e.g., one or more appropriate PINEs) are available, the PIN server may split the session. The PIN server may set a flag based on the decision. For example, the flag may be an indication that the session may be split, such as from a PEGC to a terminating PINE.

[0113] Based on the PIN ID, the PIN server may select a PCM / PEMC. The PCM / PEMC may perform a service switching process as described herein. The PIN server (PCS) may transmit a request, such as a switch application session request, to the selected PCM / PEMC.

[0114] like Figure 7 As illustrated, the PCS may transmit a request, such as a handover application session request, to the PCM / PEMC. The handover application session request may be and / or may include one or more of the following: an application session ID; a destination PINE (e.g., one or more PEIDs (1...N), an IP address, a port number, a uniform resource locator (URL), etc.); an indication of whether the application session can be split between two or more PINEs; a description of the session (e.g., an IP 4-tuple); and / or a token that the PEGC can use to prove to the AS that the PEGC can be an endpoint of a streaming session.

[0115] For example, the PCS may transmit a request with an indication to the PCM / PEMC, such as a request to switch an application session. The indication may indicate whether the application session may be split between one or more PINEs. The PCS may set a flag to indicate whether the application session may be split between one or more PINEs. For example, the PCS may set a flag SPLIT to FALSE or TRUE. For example, by setting the flag SPLIT to TRUE, the flag may indicate that the request includes two or more PINEs.

[0116] like Figure 7 As illustrated and / or as described herein, the PCM / PEMC may receive a request, such as a service handover request, from a PCS. In an example, the PCM / PEMC described herein may be a WTRU, such as a first WTRU. In an example, the PCS described herein may be a network node. For example, a first WTRU (e.g., a PCM / PEMC) may receive a service handover request message from a network node (e.g., a PCS). The service handover request message may request that a session be handed over from the first WTRU (e.g., a PCM / PEMC) to a PINE. As described herein, a PINE may be associated with a PIN.

[0117] As described herein, the service switching request message may be and / or may include one or more of the following: an application session ID; information associated with the destination PINE; an indication of whether the application session may be split between two or more PINEs; a description associated with the session; or a token indicating that the first WTRU may be an endpoint of the session.

[0118] The information associated with the destination PINE may be and / or may include one or more of: an IP address associated with the destination PINE, a port number associated with the destination PINE, or a URL associated with the destination PINE.

[0119] The description associated with the session may be and / or may include an IP 4-tuple.

[0120] like Figure 7 As illustrated and / or described herein, the PCM / PEMC may traverse one or more available PEGCs in a PIN. The PCM / PEMC may select a PEGC that may support service switching. For example, the PCM / PEMC may select a PEGC that may support service switching based on its ability to support application sessions, reachability toward the selected PINE, and / or the user's PIN policy.

[0121] For example, a first WTRU (e.g., PCM / PEMC) may determine a PEGC in a PIN. A PEGC as described herein may be a WTRU, such as a second WTRU. For example, a first WTRU may determine a second WTRU in a PIN. A first WTRU may determine one or more WTRUs (e.g., PEGCs) associated with a PIN. A first WTRU may determine session capability criteria for supporting a session.

[0122] For example, the session capability criteria may be and / or may include capabilities to support the session, reachability information associated with the PINE, or a PIN policy. Capabilities to support the session may be and / or may include computing capabilities, memory capabilities, bandwidth capabilities, and / or filtering capabilities, etc. In an example, the session capability criteria may be associated with a threshold level. For example, the session capability criteria may be a threshold level associated with computing capabilities of the PEGC that may support the session, a threshold level associated with memory capabilities of the PEGC that may support the session, a threshold level associated with bandwidth capabilities of the PEGC that may support the session, and / or a threshold level associated with filtering capabilities of the PEGC that may support the session, etc.

[0123] A first WTRU (e.g., PCM / PEMC) may determine whether a capability of a second WTRU (e.g., PEGC) satisfies session capability criteria. For example, the first WTRU may determine whether a capability of a second WTRU described herein is above a threshold level or below a threshold level. If a threshold level associated with one or more capabilities described herein is above a preconfigured threshold level, the first WTRU may determine that the second WTRU satisfies session capability criteria. If a threshold level associated with one or more capabilities described herein is below a preconfigured threshold level, the first WTRU may determine that the second WTRU does not satisfy the session capability criteria and / or the first WTRU may determine (e.g., evaluate) one or more PEGCs.

[0124] Based on determining that the capabilities of the second WTRU meet the session capability criteria, the first WTRU may determine and / or select the second WTRU from the one or more WTRUs. The first WTRU may determine a PINE identifier associated with the second WTRU. The selected PEGC (e.g., the second WTRU) may be used to establish a handed-off application session with the AS. For example, the selected PEGC (e.g., the second WTRU) may be used to support the handed-off application session with the AS, such as receiving an application session from the AS and forwarding it to the PINE.

[0125] PCM / PEMC may respond to PCS (e.g., in response to a handover application session request) using one or more of the following: terminating party PEGC ID; terminating party PEGC reachability information (e.g., IP address, port number, URL, etc.); and / or terminating party destination PINE reachability information (e.g., IP address, port number, URL, etc.).

[0126] like Figure 7 As illustrated and / or described herein, the PCM / PEMC (e.g., a first WTRU) may transmit a message, such as a confirmation message, to the PCS (e.g., a network node). The confirmation message may indicate a session identifier and / or an indication that the PEGC (e.g., a second WTRU) supports session switching. As described herein, support for session switching may be, for example, switching the session to a PINE within a PIN by accepting an application session and forwarding it to a selected PINE. The session identifier may be and / or may include one or more of: a termination identifier associated with the second WTRU; reachability information associated with the second WTRU; or reachability information associated with the PINE. The reachability information associated with the PEGC (e.g., a second WTRU) may be and / or may include one or more of an IP address associated with the PEGC (e.g., a second WTRU), a port number associated with the PEGC (e.g., a second WTRU), or a URL associated with the PEGC (e.g., a second WTRU). The reachability information associated with the PINE may be and / or may include one or more of an IP address associated with the PINE, a port number associated with the PINE, or a URL associated with the PINE.

[0127] The PCS may store information about the terminating party PEGC ID, the terminating party PEGC IP address, and / or the terminating party PINE reachability information for the service switching context of the user.

[0128] The PCS may provide the AS with the terminating party PEGC information. The PEGC and / or the AS may establish the switched application session.

[0129] like Figure 7As illustrated, the PCS may notify the AS (e.g., a streaming server) to switch the application session to a destination IP address (e.g., a new destination IP address). The PCS may transmit one or more of the following: an application session ID (e.g., to identify the application session to be switched to an endpoint such as a new endpoint); and / or a termination IP (TermIP) address (e.g., an IP address of the PEGC where the application session may be terminated).

[0130] like Figure 7 As illustrated, the PCM may start configuring the PEGC by transmitting a message such as a configuration service switching message. The configuration service switching message may be and / or may include one or more of the following: a session ID; a destination PINE information; a value of a flag SPLIT; a packet data unit (PDU) session modification request; and / or a PIN configuration service switching configuration request.

[0131] The destination PINE information may be and / or may include a list of PINE IDs (PEIDs), IP addresses and / or port numbers or URLs where one or more substreams are to be terminated. For example, the destination PINE information may be represented as DestinationPineList[(PEID1, IP address 1, port number 1) ... (PEIDn, IP address N, port number N)].

[0132] The flag SPLIT may be set to TRUE or FALSE based on whether the session may be split (eg, may need to be split) into two or more PINEs and / or whether more than one PINE information is included in the TerminatingPineList.

[0133] The PEGC may transmit a request, such as a PDU session modification request, to a network (e.g., 5GC). For example, if the PEGC receives a configure service switching message from the PCM, the PEGC may transmit a PDU session modification request to the network (e.g., 5GC). The PDU session modification request may be and / or may include an IP address, a port number, and / or a PEID received from the PCM. The PDU session modification request may be used to request one or more quality of service (QoS) rules (e.g., one or more new QoS rules) for a flow (e.g., for a new flow). The one or more QoS rules for the flow may be received by the PEGC in a PDU session modification command message. The one or more QoS rules may be used by the PEGC to determine what QoS marking to apply to the service when communicating with the PINE identified by the PEID.

[0134] The PIN configuration service handover configuration request may be and / or may include one or more of: an identifier associated with the requestor; security credentials; an application client identifier; an application server identifier; a target PIN client; an application session identifier; and / or a description of a session, such as an IP 4-tuple, that describes the services of the application session.

[0135] like Figure 7 As illustrated and / or described herein, a PCM / PEMC (e.g., a first WTRU) may transmit a message, such as a configuration message, to a PEGC (e.g., a second WTRU). For example, the configuration message may indicate a PINE identifier, a session identifier, and / or a request to support session switching. For example, the configuration message may indicate a PINE, including one or more of: a list of PEIDs, an IP address associated with the PINE, a port number associated with the PINE, and / or a URL associated with the PINE. For example, the configuration message may be and / or may include an indication of whether a session may be split (e.g., may need to be split) to two or more PINEs.

[0136] The PEGC may use the token to prove to the AS that the PEGC may be an endpoint of the streaming session.

[0137] Based on the application session ID, the PEGC can configure the port number and / or URL to receive the application session from the AS. The terminating party PINE information can be used to establish a forwarding table. The application session from the AS can be forwarded to the terminating party PINE.

[0138] If the SPLIT flag is set to TRUE, the PEGC may receive more than one terminating party PINE information from the PEMC. The PEGC may configure a forwarding table towards the PINE, for example, based on the sub-flows of the application session.

[0139] The PEGC may respond with a confirmation to indicate whether the PEGC is successfully configured. For example, an indication such as OK may indicate a successful configuration.

[0140] like Figure 7 As illustrated, the PCM / PEMC may configure the PINE to prepare for termination of the application session, eg, as indicated by a configuration service switch from the PCM to the PINE.

[0141] PINE may use the PEGC reachability information to establish a connection with the PEGC.PINE may configure a port number to receive application sessions from the AS through the PEGC.

[0142] like Figure 7As illustrated, PEGC and / or PINE may be successfully configured. After successfully configuring PEGC and / or PINE, PCM / PEMC may transmit an indication to PCS, such as a service switching configuration success indication. PEGC may contact AS. PIN GW client may provide a token proving that PEGC may be (e.g., may now be) an endpoint of the session.

[0143] like Figure 7 As illustrated and / or described herein, a first WTRU (e.g., PCM / PEMC) may receive a message, such as an acknowledgement message (e.g., a second acknowledgement message), from a second WTRU (e.g., PEGC). The second acknowledgement message may indicate that the second WTRU (e.g., PEGC) has been configured to support session switching, for example, by forwarding data associated with the session to a PINE. The first WTRU (e.g., PCM / PEMC) may transmit a message, such as a service switching response message, to a network node (e.g., PCS). The service switching response message may indicate that the second WTRU (e.g., PEGC) has been configured to forward data associated with the session to the PINE. For example, the configuration may involve establishing an endpoint identifier of a network node and / or PINE, for example to allow reception and / or forwarding of application data, so as to establish a forwarding table to forward the application data from the network node to the PINE.

[0144] like Figure 7 As illustrated, PCS, 5GS and / or PEGC may continue to perform session modification and / or session update to terminate the session in one or more PINEs. PEGC may split a session (e.g., a main session) into two or more substreams. The two or more split substreams may be terminated in two or more corresponding PINEs. PEGC may interact with PCS to maintain synchronization between substreams.

[0145] The WTRU may initiate a service switch and the PEMC may perform the service switch. Figure 8 As illustrated, the PEMC may switch the service from the WTRU to the PIN. Figure 8 Illustrate an example of service switching performed by PEMC. May or may not be performed (e.g., skipped) Figure 8 One or more processes are illustrated.

[0146] The WTRU may select a PIN. Figure 8 As illustrated, after PIN selection, the WTRU may transmit a request, such as a service switching request, to the PEMC. The service switching request may be and / or may include information regarding the application session ID, application name, and / or one or more selected PEIDs.

[0147] The PEMC may receive (e.g., obtain) a request from the WTRU. Based on one or more available PIN policies (e.g., obtained from a PIN server), the PEMC may determine whether the WTRU is allowed to request a service switch. The PEMC may determine what quality of service treatment may be provided to the WTRU based on the PIN policies (e.g., one or more available PIN policies). Based on the quality of service level and / or the PIN policies, the PEMC may select a PEGC that can support the service switch. The PEMC may transmit information to the PIN server. For example, the PEMC may transmit information to the PIN server to obtain authorization and / or update one or more selections for the service switching process described herein.

[0148] like Figure 8 As illustrated, the PEMC may transmit a notification, such as a handover notification, to the PCS and / or PIN server. The handover notification may be and / or may include one or more of: WTRU ID; application session ID; PIN ID; PEGCID; PEID; and / or a description of the service.

[0149] The WTRU ID may be and / or may include a user identity, an application-level WTRU ID of the WTRU requesting service switching. The application session ID may be and / or may include a session identifier to which the WTRU is requesting switching. The PIN ID may be and / or may include a PIN ID to which the service may be switched. The PEGC ID may be and / or may include a PEGC and / or PEGC IP address in the PIN that may terminate the application session from the 5GS, and / or an available port number, etc. The PEID may be and / or may include a PINE and / or PINAPP where the session may be forwarded and / or terminated by the PEGC. The description of the service may be and / or may include an IP 4-tuple that may describe the service. For example, the description of the service may be and / or may include one or more of the following: one or more WTRU IP address port numbers that may be associated with the service; and / or a server IP address and port number that may be associated with the service.

[0150] The PCS may authorize the request. The PCS may identify the AS. For example, the PCS may identify the AS based on the application session ID and / or IP address. An AS such as a PIN AS may query an application service provider. For example, a PIN AS may query an application service provider to identify the application session and / or obtain AS information (e.g., IP address, port number, URL, etc.).

[0151] The PIN server may check one or more of the following to authorize the request: a PIN database; a subscription of the WTRU; and / or a PIN policy. The PIN server may query the AS using the application session ID and / or the service handover request. The PIN server may query the AS (e.g., using the application session ID and / or the service handover request) to determine reachability information associated with the AS. The reachability information associated with the AS may be and / or may include an IP address, a port number, and / or a URL, among others.

[0152] The PIN server may inform the PEMC that the service switch may be authorized. For example, the PIN server may inform the PEMC that the service switch may be authorized along with one or more AS details (such as IP address, port number and / or URL, etc.).

[0153] like Figure 8 As illustrated, the PCS may transmit a message (e.g., a first message) to the PCM / PEMC. The message (e.g., the first message) may be and / or may include an identifier, such as an AS identifier and / or an indication of how to reach the AS, such as an IP address, a port number and / or a URL, etc. The PCS may notify the AS (e.g., and / or a streaming server). For example, the PCS may notify the AS to switch the application session to a destination IP address, such as a new destination IP address. For example, the destination IP address may be a PINE. The PCS may transmit a message (e.g., a second message) to the PCM / PEMC. The message (e.g., the second message) may be and / or may include an application session ID and / or a termination IP address (TermIP) to the PCM / PEMC. For example, the application session ID may identify an application session to be switched to an endpoint (e.g., a new endpoint). For example, the termination IP address (TermIP) may be and / or may include the IP address of the PINE where the application session may be terminated.

[0154] The PEMC may receive authorization information and / or AS information. The PEMC may obtain information about the session. For example, the information about the session may be whether the session can (e.g., may need to) be split into more than one PINE by interacting with the AS and / or PIN server. The PEMC may use application-level interactions to obtain media-related information.

[0155] The PEMC may continue to perform the service switching process. The PEMC may begin configuring the selected PEGC as described herein.

[0156] like Figure 8As illustrated, PCM / PEMC may transmit PEGC configuration information for session establishment. The configuration information may be and / or may include one or more of the following: session ID; AS information (e.g., AppserverInfo); destination PINE information; indication of whether to perform segmentation; and / or PDU session modification request.

[0157] The session ID may be and / or may include an identifier of the session. The AS information (e.g., AppserverInfo) may be and / or may include an IP address and / or a URL. The destination PINE information may be and / or may include a list of one or more of the following: PEIDs, IP addresses, port numbers, and / or URLs where the substreams may be terminated. For example, the destination PINE information may be provided as follows: DestinationPineList[(PEID1, IP address 1, port number 1)...(PEIDn, IP address N, port number N)]. An indication of whether to split may be and / or may include a SPLIT flag. For example, if the session is to be split into two or more PINEs and / or if more than one PINE information is included in the TerminatingPineList, the flag SPLIT may be set to TRUE or FALSE.

[0158] The PEGC may transmit a request, such as a PDU session modification request, to a network (e.g., 5GC). For example, if the PEGC receives a configuration service switching message from the PCM, the PEGC may transmit a PDU session modification request to the network (e.g., 5GC). The PDU session modification request may be and / or may include an IP address, a port number, and / or a PEID received from the PCM. The PDU session modification request may be used to request one or more QoS rules for a flow (e.g., one or more new QoS rules for a new flow). The one or more QoS rules for the flow may be received by the PEGC. For example, the one or more QoS rules for the flow may be received by the PEGC in a PDU session modification command message. The one or more QoS rules may be used by the PEGC. For example, the one or more QoS rules may be used by the PEGC to determine what QoS marking to apply to a service when communicating with a PINE identified by a PEID. The PCM / PEMC may configure the PINE to terminate the session.

[0159] Based on the application session ID, the PEGC can configure the port number and / or URL to receive the application session from the AS. The terminating party PINE information can be used to establish a forwarding table. The application session from the AS can be forwarded to the terminating party PINE.

[0160] If the SPLIT flag is set to TRUE, the PEGC may receive more than one terminating party PINE information from the PEMC. The PEGC may configure a forwarding table towards the PINE based on one or more sub-flows of the application session.

[0161] like Figure 8 As illustrated, 5GC and PEGC may establish one or more new / modified application sessions / PDU sessions. PEGC may split a session (e.g., a main session) into two or more sub-streams. The sub-streams may be terminated in two or more PINEs. PEGC may interact with PCS to maintain synchronization between sub-streams.

[0162] The WTRU may initiate a service switch and the PIN server may perform the service switch. Fig. 9 As illustrated, the PIN server may switch the service from the PIN to the WTRU. The service switching procedure performed by the PIN server may allow (eg, enable) the WTRU to trigger a service switch from the PIN to the WTRU (eg, the triggering WTRU) and / or one or more WTRUs. Fig. 9 An example of a service handover from a PIN to a WTRU performed by a PIN server is illustrated. May or may not be performed (e.g., skipped) Fig. 9 One or more processes are illustrated.

[0163] like Fig. 9 As illustrated, the WTRU may transmit a request, such as a service hand-off request, to the PCS / PIN server. The service hand-off request may indicate a request for a service handover from the PIN to the WTRU. The request may be and / or may include one or more of the following information: an application session ID; a source PIN ID; and / or a destination WTRU ID.

[0164] like Fig. 9 As illustrated, the PCS may identify the PCM / PEMC based on the PIN ID. The PCS may transmit a service handoff request to the PCM / PEMC. The service handoff request may be and / or may include an application session ID.

[0165] The PCM may respond to the PCS with the PEGC ID and / or PEGC reachability information (e.g., IP address). The response by the PCM may be and / or include the terminating party PEGC ID and / or a description of the session (e.g., an IP 4-tuple describing the session). The description of the session (e.g., IP 4-tuple) may be and / or include the IP address of the PEGC, the IP address of the server providing the service, a port number in the PEGC that may be associated with the service, and / or a port number on a server that may be associated with the service.

[0166] like Fig. 9As illustrated, the PCS may notify the AS (e.g., and / or the streaming server) to switch the application session to a destination IP address (e.g., a new destination IP address). The service switching message from the PCS may be and / or may include an application session ID (e.g., to identify the application session to be switched to an endpoint such as a new endpoint) and / or a termination IP (TermIP) address (e.g., an IP address of the WTRU where the application session may be terminated).

[0167] like Fig. 9 As illustrated, the PCM may start configuring the PEGC. For example, the PCM may start configuring the PEGC by transmitting a Configure Service Cut Out message. The Configure Service Cut Out message may be and / or may include a session ID and / or destination PINE information. The destination PINE information may be and / or may include a PEID list, an IP address, a port number, and / or a URL indicating that a substream may be terminated. For example, the destination PINE information may be provided as follows: DestinationPineList[(PEID1, IP address 1, port number 1) ... (PEIDn, IP address N, port number N)].

[0168] The PEGC may respond with a confirmation indicating whether the PEGC is successfully configured. For example, if the PEGC is successfully configured, the PEGC may respond with an OK confirmation message.

[0169] If the PEGC receives a configuration service switching message from the PCM, the PEGC may transmit a request, such as a PDU session modification request, to the network (such as a 5GC). The PDU session modification request may be and / or may include an IP address, a port number, and / or a PEID received from the PCM. The PDU session modification request may be used to request one or more QoS rules for a flow (e.g., one or more new QoS rules for a new flow). The one or more QoS rules for the flow may be received by the PEGC. For example, the one or more QoS rules for the flow may be received by the PEGC in a message (such as a PDU session modification command message). The one or more QoS rules may be used by the PEGC. For example, the one or more QoS rules may be used by the PEGC to determine what QoS marking to apply to the service when communicating with a PINE identified by a PEID.

[0170] like Fig. 9 As illustrated, the PCM may configure the PINE to prepare to stop receiving traffic and / or may configure the PINE to switch the application session to the WTRU.

[0171] like Fig. 9As illustrated, PCM / PEMC may transmit an indication of successful service switching configuration to PCS. For example, PCM / PEMC may transmit an indication of successful service switching configuration to PCS after successfully configuring PEGC and / or PINE. PCS, 5GS and / or PEGC may continue to perform session modification and / or session update to complete the service hand-off process.

[0172] Although the above features and elements are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without the other features and elements.

[0173] Although the implementations described herein may consider 3GPP specific protocols, it should be understood that the implementations described herein are not limited to such scenarios and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to such scenarios and may be applicable to other wireless systems.

[0174] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (sent via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, built-in hard disks and removable disks), magneto-optical media, and / or optical media (such as compact disk (CD)-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, a terminal, a base station, an RNC, and / or any host computer.

Claims

1. A first wireless transmit / receive unit (WTRU), the first WTRU comprising: A processor, the processor being configured to: receiving a service handover request message from a network node, wherein the service handover request message requests handover of a session from the first WTRU to a personal internet of things network (PIN) element (PINE), wherein the PINE is associated with the PIN; determining a second WTRU, wherein the second WTRU supports session handover; transmitting a first confirmation message to the network node, wherein the first confirmation message indicates a session identifier and indicates that the second WTRU supports the session handover; transmitting a configuration message to the second WTRU, wherein the configuration message indicates a PINE identifier, the session identifier, and a request to support handover of the session; receiving a second confirmation message from the second WTRU, wherein the second confirmation message indicates that the second WTRU has been configured to support the session handover by forwarding data associated with the session to the PINE; as well as A service switching response message is transmitted to the network node, wherein the service switching response message indicates that the second WTRU has been configured to forward the data associated with the session to the PINE.

2. The first WTRU of claim 1, wherein the first WTRU is a PINE with management capabilities (PEMC), the network node is a PIN server (PCS), and the second WTRU is a PINE with gateway capabilities (PEGC).

3. A first WTRU according to claim 1, wherein the service switching request message includes one or more of an application session identification (ID), information associated with a destination PINE, an indication indicating whether an application session can be split between multiple PINEs, a description associated with the session, or a token indicating that the first WTRU will be an endpoint of the session.

4. The first WTRU of claim 3, wherein the information associated with the destination PINE comprises one or more of an Internet Protocol (IP) address associated with the destination PINE, a port number associated with the destination PINE, or a Uniform Resource Locator (URL) associated with the destination PINE, and wherein the description associated with the session comprises an IP 4-tuple.

5. The first WTRU of claim 1 , wherein determining the second WTRU comprises the processor being configured to: determining one or more WTRUs associated with the PIN; determining session capability criteria for supporting the session; determining whether capabilities of the second WTRU satisfy the session capability criteria; as well as Based on determining that the capabilities of the second WTRU satisfy the session capability criteria, the second WTRU is determined from the one or more WTRUs based on the PINE identifier associated with the second WTRU.

6. The first WTRU of claim 5, wherein the session capability criteria for supporting the session comprises one or more of a capability to support the session, reachability information associated with the PINE, or a PIN policy.

7. According to the first WTRU of claim 1, the session identifier includes one or more of a termination identifier associated with the second WTRU, reachability information associated with the second WTRU, or reachability information associated with the PINE.

8. The first WTRU of claim 7, wherein the reachability information associated with the second WTRU comprises one or more of an IP address associated with the second WTRU, a port number associated with the second WTRU, or a URL associated with the second WTRU, and the reachability information associated with the PINE comprises one or more of an IP address associated with the PINE, a port number associated with the PINE, or a URL associated with the PINE.

9. The first WTRU of claim 1 , wherein the configuration message indicating the PINE includes a PINEID (PEID) list, an IP address associated with the PINE, a port number associated with the PINE, or a URL associated with the PINE, and the configuration message further includes an indication of whether the session is to be split into two or more PINEs.

10. A method for a first wireless transmit / receive unit (WTRU), the method comprising: receiving a service handover request message from a network node, wherein the service handover request message requests handover of a session from the first WTRU to a personal internet of things network (PIN) element (PINE), and wherein the PINE is associated with the PIN; determining a second WTRU, wherein the second WTRU supports session handover; transmitting a first confirmation message to the network node, wherein the first confirmation message indicates a session identifier and indicates that the second WTRU supports the session handover; transmitting a configuration message to the second WTRU, wherein the configuration message indicates a PINE identifier, the session identifier, and a request to support handover of the session; receiving a second confirmation message from the second WTRU, wherein the second confirmation message indicates that the second WTRU has been configured to support the session handover by forwarding data associated with the session to the PINE; as well as A service switching response message is transmitted to the network node, wherein the service switching response message indicates that the second WTRU has been configured to forward the data associated with the session to the PINE.

11. The method of claim 10, wherein the first WTRU is a PINE with management capabilities (PEMC), the network node is a PIN server (PCS), and the second WTRU is a PINE with gateway capabilities (PEGC).

12. The method of claim 10, wherein the service switching request message comprises one or more of an application session identification (ID), information associated with a destination PINE, an indication of whether an application session can be split between multiple PINEs, a description associated with the session, or a token indicating that the first WTRU will be an endpoint of the session, wherein the information associated with the destination PINE comprises one or more of an Internet Protocol (IP) address associated with the destination PINE, a port number associated with the destination PINE, or a URL associated with the destination PINE, and wherein the description associated with the session comprises an IP 4-tuple, and wherein the configuration message indicating the PINE comprises a list of PINEIDs (PEIDs), an IP address associated with the PINE, a port number associated with the PINE, or a URL associated with the PINE, and the configuration message also comprises an indication of whether the session is to be split between two or more PINEs.

13. The method of claim 10, wherein determining the second WTRU comprises: determining one or more WTRUs associated with the PIN; determining session capability criteria for supporting the session; determining whether capabilities of the second WTRU satisfy the session capability criteria; as well as Based on determining that the capabilities of the second WTRU satisfy the session capability criteria, the second WTRU is determined from the one or more WTRUs based on the PINE identifier associated with the second WTRU.

14. The method of claim 13, wherein the session capability criteria for supporting the session comprises one or more of a capability to support the session, reachability information associated with the PINE, or a PIN policy.

15. The method of claim 10, wherein the session identifier comprises one or more of a termination identifier associated with the second WTRU, reachability information associated with the second WTRU, or reachability information associated with the PINE, wherein the reachability information associated with the second WTRU comprises one or more of an IP address associated with the second WTRU, a port number associated with the second WTRU, or a URL associated with the second WTRU, and wherein the reachability information associated with the PINE comprises one or more of an IP address associated with the PINE, a port number associated with the PINE, or a URL associated with the PINE.

Images