WO2025155531A1 - Method and apparatus for location privacy with randomized and changing mac address - Google Patents

Abstract

In an embodiment, a method, implemented in a wireless transmit/receive unit, WTRU, capable of changing its Medium Access Control, MAC, addresses and/or using multiple MAC, addresses, comprising transmitting to a network controlling entity via a network element of a mobile network, a first message comprising a first information indicating an intention of the WTRU to switch from using one or more current MAC addresses to one or more new MAC addresses; receiving, from the mobile network, a second message comprising a second information indicating instruction for switching from the one or more current MAC addresses to the one or more new MAC addresses; and switching from the one or more current MAC addresses to the one or more new MAC addresses for communicating with the mobile network based on the second message.

Description

METHOD AND APPARATUS FOR LOCATION PRIVACY WITH RANDOMIZED AND CHANGING MAC ADDRESS

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of US Provisional Patent Application No. 63/621,276 filed January 16^th, 2024, which is incorporated herein by reference.

FIELD OF THE INVENTION

[0002] The present disclosure is generally directed to methods, architecture apparatuses and systems to enable location privacy with randomized and changing MAC address (RCM). More particularly, the present disclosure relates to methods to enable location privacy with RCM for 3GPP time sensitive communication-time sensitive networking (TSC-TSN) networks.

BACKGROUND

[0003] Internet privacy, and in particular, user tracking, may affect all layers of the protocol stack, from the lower layers involved in the actual access to the network (e.g., the Layer-2 and Layer-3 addresses can be used to obtain the location of a user) to higher layer protocol identifiers and user applications. In particular, IEEE 802 Medium Access Control (MAC) addresses may have historically been an easy target for tracking users. Attackers who are equipped with surveillance equipment can "monitor" Wi-Fi packets and track the activity of Wi-Fi devices. Once the association between a device and its user is made, identifying the device and its activity may be sufficient to deduce information about what the user is doing, without the user consent.

[0004] IEEE 802.11 (Wi-Fi) interfaces, as any other kind of IEEE 802-based network interface, like Ethernet (i.e., IEEE 802.3) have a Layer-2 address also referred to as MAC address, which can be seen by anybody who can receive the signal transmitted by the network interface.

[0005] MAC addresses can be easily observed by a third party, such as a passive device listening to communications in the same network. In an 802.11 network, a station may expose its MAC address in two different situations: (i) while unassociated and actively scanning for available networks, the MAC address is used in the Probe Request frames sent by the device (aka IEEE 802.11 STA); (ii) once associated to a given Access Point (AP), the MAC address is used in frame transmission and reception, as one of the addresses used in the address fields of an IEEE 802.11 frame.

[0006] MAC addresses can either be universally administered or locally administered. A MAC address may be identified as being locally administered when the second-last significant bit of the most significant octet of the address (the U/L bit) is set. The MAC address may be identified as globally unique when the U/L bit is unset.

[0007] A universally administered address may be uniquely assigned to a device by its manufacturer (and is called the bumed-in address). Most physical devices are provided with a universally administered address, which may be composed of two parts: (i) the Company Identifier (CID), which are the first three octets in transmission order and identify the organization that issued the identifier, and (ii) Network Interface Controller (NIC) Specific, which are the following three octets, assigned by the organization that manufactured the NIC, in such a way that the resulting MAC address is globally unique. Since universally administered MAC addresses are by definition globally-unique, when a device uses this MAC address to transmit data, especially over the air, it may be relatively easy to track this device by simple medium observation. This possibility poses a privacy concern when the device is directly associated to a single user (e.g., smartphones etc.).

[0008] Locally administered addresses may override the bumed-in address, and they may either be set-up by the network administrator, or by the Operating System (OS) of the device to which the address pertains. This may allow generating local addresses without the need for any global coordination mechanism to ensure that the generated address is still unique within the local network. This feature can be used to generate random addresses, which decouple the globally- unique identifier from the device and therefore make it more difficult to track a user device from its MAC/L2 address. There are initiatives at the IEEE 802 and other organizations to specify ways in which these locally administered addresses should be assigned, depending on the use case.

[0009] To reduce the risks of correlation between a device activity and its owner, multiple vendors have started to implement Randomized and Changing MAC addresses (RCM). With this scheme, an end-device may implement a different RCM over time when exchanging traffic over a wireless network. By randomizing the MAC address, the persistent association between a given traffic flow and a single device may be made more difficult, assuming no other visible unique identifiers are in use.

[0010] In 3GPP release 15, integration of 5G with Time-Sensitive Network (TSN) networks is supported. The 3 GPP Release 17 has introduced enhancements to generalize support for Time- Sensitive Communications (TSC) beyond TSN. But the existing 3GPP system is not fast enough to cope with MAC address(es) changes, especially in TSC/TSN scenarios.

[0011] There is a need to improve methods to change MAC addresses particularly for time sensitive/deterministic communications. SUMMARY

[0012] In an embodiment, a method, implemented in a wireless transmit/receive unit (WTRU) capable of changing its Medium Access Control (MAC) addresses and/or using multiple MAC addresses, may comprise a step of transmitting to (e.g., a network controlling entity via a network element of) a mobile network, a first message comprising a first information indicating an intention of the WTRU to switch from using one or more current MAC addresses to one or more new MAC addresses. The external controlling entity may be any of a time-sensitive communications (TSC), controlling entity, a time-sensitive networking (TSN), controlling entity, and a deterministic networking (DetNet), controlling entity. The network element may be a TSN application function (AF), and/or a Time Sensitive Communication and Time Synchronization Function (TSCTSF) of the mobile network. The method may further comprise a step of receiving, from the mobile network, a second message comprising a second information indicating instruction for switching from the one or more current MAC addresses to the one or more new MAC addresses; and a step of switching from the one or more current MAC addresses to the one or more new MAC addresses for communicating with the mobile network based on the second message.

[0013] The method may comprise a step of using sequentially and/or simultaneously the new MAC addresses. The one or more new MAC addresses may comprise at least one or more current MAC addresses.

[0014] The method may further comprise a step of receiving a third message comprising a third information indicating mobile network reconfiguration based on the one or more new MAC addresses.

[0015] The first message may be a protocol data unit, PDU, session modification or a PDU establishment request message. The first information may comprise a list of the one or more current MAC addresses and the one or more new MAC addresses, wherein each of the one or more current MAC addresses of the list may be associated with at least the one or more new MAC addresses. The first information may comprise an index value indicating the one or more new MAC addresses, wherein the index value may be received by the WTRU from an application function/application server.

[0016] The step of transmitting the first message may be on condition of a trigger event of switching MAC address, wherein the trigger event may be from subscription policies or is an external trigger from an AF.

[0017] In an embodiment, a wireless transmit/receive unit, WTRU, capable of changing its Medium Access Control, MAC, addresses and/or using multiple MAC addresses, comprising any of a memory and a processor, may be configured to transmit, to (e.g., a network controlling entity via a network element of) a mobile network, a first message comprising a first information indicating an intention of the WTRU to switch from using one or more current MAC addresses to one or more new MAC addresses. The WTRU may be further configured to receive, from the mobile network, a second message comprising a second information indicating instruction for switching from the one or more current MAC addresses to the one or more new MAC addresses; and to switch from the one or more current MAC addresses to the one or more new MAC addresses for communicating with the mobile network based on the second message.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein: [0019] FIG. 1 A is a system diagram illustrating an example communications system;

[0020] FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0021] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;

[0022] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0023] FIG. 2 is a block diagram illustrating an example 5G system acting as logical timesensitive networking bridge according to an embodiment;

[0024] FIG. 3 is a block diagram illustrating an example 5G system acting as logical deterministic networking node and time-sensitive networking-enabled transport netwrok according to an embodiment;

[0025] FIG. 4 is a block diagram illustrating a scenario example of WTRUs and/or devices bridged to the WTRU (TSN/TSC station) using multiple MAC addresses according to an embodiment;

[0026] FIG. 5 is a block diagram illustrating an example of a proactive WTRU RCM exposure signaling according to an embodiment;

[0027] FIG. 6A and FIG. 6B is a sequence diagram illustrating an example of a proactive WTRU RCM exposure signaling to an embodiment; [0028] FIG. 7 is a block diagram illustrating an example of proactive TSC/TSN end station bridged by a WTRU RCM exposure signaling according to an embodiment;

[0029] FIG. 8A and FIG. 8B is a sequence diagram illustrating an example of a proactive TSC/TSN end station bridged by a WTRU RCM exposure signaling according to an embodiment. [0030] FIG. 9 is a block diagram illustrating an example of RCM exposure from TSC/TSN station bridged by a WTRU supporting simultaneous use of old and new MAC addresses during a time window; and

[0031] FIG. 10 is a flow chart diagram illustrating an example of a method, implemented in a WTRU, for changing MAC addresses of the WTRU and/or for using multiple MAC addresses of the WTRU.

DETAILED DESCRIPTION

[0032] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and/or any portion thereof.

[0033] Hereinafter, ‘a’ and ‘an’ and similar phrases are to be interpreted as ‘one or more’ and ‘at least one’ . Similarly, any term which ends with the suffix ‘(s)’ is to be interpreted as ‘one or more’ and ‘at least one’. The term ‘may’ is to be interpreted as ‘may, for example’.

[0034] A sign, symbol, or mark of forward slash 7’ is to be interpreted as ‘and/or’ unless particularly mentioned otherwise, where for example, ‘A/B’ may imply ‘A and/or B’.

[0035] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein. [0036] FIG. 1A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 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), singlecarrier FDMA (SC-FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0037] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104/113, a core network (CN) 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated 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 a "STA", may be configured to transmit and/or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0038] The communications systems 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 configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), 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.

[0039] 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), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one 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 or any sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

[0040] 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).

[0041] More specifically, as noted above, the communications 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, and the like. 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 establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

[0042] 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), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE- Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).

[0043] 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).

[0044] 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 instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).

[0045] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, 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), and the like.

[0046] The base station 114b in FIG. 1 A may be a wireless router, Home Node-B, Home eNode- B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In an 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 an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106/115.

[0047] 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 varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, 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 be utilizing an NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0048] 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 circuit-switched telephone networks that provide 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), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired and/or wireless communications 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/114 or a different RAT.

[0049] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications 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 over different wireless links). For example, the WTRU 102c shown in FIG. 1A 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.

[0050] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include 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 elements/peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0051] 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 in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, 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. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

[0052] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In an embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0053] Although the transmit/receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit/receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an 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.

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

[0055] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or 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 the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), 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, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0056] The processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the 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, and the like.

[0057] 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 over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0058] The processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity. For example, the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (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, and the like. The elements/peripherals 138 may include one or more sensors, the sensors may be one or more of 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.

[0059] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (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 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

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

[0061] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-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 an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0062] Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0063] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator.

[0064] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI 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, and the like. 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.

[0065] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI 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 user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0066] 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.

[0067] 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 communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves 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 the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.

[0068] Although the WTRU is described in FIGs. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network. [0069] In representative embodiments, the other network 112 may be a WLAN.

[0070] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a distribution system (DS) or another type of wired/wireless network that carries traffic into and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad-hoc" mode of communication. [0071] When using the 802.1 lac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0072] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0073] Very high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast Fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0074] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in 802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.1 lah may support meter type control/machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life). [0075] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.1 In, 802.1 lac, 802.11af, and 802.1 lah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest 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, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.1 lah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes. Carrier sensing and/or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0076] In the United States, the available frequency bands, which may be used by 802.1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.1 lah is 6 MHz to 26 MHz depending on the country code.

[0077] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an 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.

[0078] 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 an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit 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, the gNB 180a may transmit multiple component carriers to the 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, the 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).

[0079] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. 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 gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

[0080] 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 the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non- standalone configuration WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non- standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.

[0081] 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 the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0082] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0083] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g., to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 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 MTC access, and/or the like. 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.

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

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

[0086] 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 serves 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 the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0087] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, one or more, or all, of the functions described herein with regard to any of WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0088] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, 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. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device (e.g., a network node) may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

[0089] The one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a network node (e.g., wired and/or wireless communication network). For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.

[0090] Starting with the Release 16 of 3GPP, integration of 5G with TSN networks may be supported. Referring to FIG. 2, the 5G System (5GS) may appear from the rest of the network as one (or more) logical TSN bridge(s). The 5GS may include TSN Translator (TT) functionality for the adaptation of the 5GS to the TSN bridged network and for hiding the 5GS internal procedures. The 5GS may provide the following components: interface to TSN controller, as per IEEE802.1Qcc for the fully centralized configuration model, time synchronization via reception and transmission of gPTP PDUs (IEEE802.1AS), low latency, hence, can be integrated with Scheduled Traffic (IEEE802.1Qbv), and reliability, hence, can be integrated with FRER (IEEE802.1CB).

[0091] The 3 GPP release 17 has introduced enhancements to generalize support for Time- Sensitive Communications (TSC) beyond TSN: the 5GS may act as a “TSC node” in a more generic sense (which includes TSN bridge and IP node); and a new entity may be defined, called Time Sensitive Communication and Time Synchronization Function (TSCTSF), to support non- TSN time sensitive communications.

[0092] Referring to FIG. 3, the 3GPP release 18 has introduced support for the 5GS to work as a logical deterministic networking (DetNet) node, and TSN-enabled transport network.

[0093] Referring to FIG. 4, WTRUs or connected TSC/TSN stations bridged by a WTRU can establish an Ethernet-type PDU session with deterministic/time sensitive requirements and engage into communication with other devices (WTRUs attached to the same 3GPP network, e.g., as part of a 5G LAN, or other TSC/TSN stations attached to an external data network with TSC/TSN/DetNet capabilities). Either a WTRU or a TSC/TSN station bridged by another WTRU (or both) can then make use of RCM and/or multiple MAC addresses when communicating with other devices. WTRUs and/or devices attached to the WTRU (TSN/TSC stations) might use multiple MAC addresses sequentially and/or simultaneously.

[0094] Current 3 GPP system may be not fast enough to cope with MAC address(es) changes, especially in TSC/TSN scenarios. More particularly, under deterministic networking requirements, the network may be not capable of reacting fast enough to changes on the MAC address of the WTRU and/or connected TSC/TSN end stations. For example, a MAC address change on the WTRU involves a device-side TSN translator (DS-TT) port change, which requires to be exposed to external entities (e.g., central network controller (CNC) or DetNet controller).

[0095] The following various embodiments relate to solutions to enable a WTRU (or a TSC/TSN station bridged by the WTRU) that is RCM capable (meaning that it can change and use multiple MAC address(es)) to cooperate with the mobile/cellular network to minimize the impact of an address change on time sensitive/deterministic communications. The following various embodiments addresses the following questions: (i) what does a WTRU and/or a TSC/TSN station may need to signal to the network to be able to cooperate with the network to minimize the impact of address(es) changes; (ii) how does the network may use the information provided by the WTRU/TSC/TSN station to facilitate preparation in advance of a MAC address(es) change? [0096] The following various embodiments may define new extensions for a WTRU and/or a station bridged by a WTRU to coordinate with the external TSN/TSC/DetNet network entities about the changes of MAC address(es) of the WTRU and/or stations bridged by the WTRU. The benefits may include TSN/TSC/DetNet entities (including the WTRU and or the stations bridged by the WTRU) consistently handle traffic, regardless of the potential change(s) of address(es). As a non-limited example, this may enable a TSN controller to recompute the traffic scheduling according to new MAC addresses to provide a consistent treatment to the traffic, despite the change of the MAC addresses used by the device. Support for simultaneous use of old and new address(es) may be also specified to minimize the effects of RCM on the traffic.

[0097] In order to enable WTRU RCM exposure for time sensitive communications, in various embodiments, methods of operation and signaling for a WTRU to inform the network about its decision to update the MAC address(es) it is using is described below. The WTRU may be capable of doing RCM, and therefore of using multiple addresses and changing them. The WTRU may be engaged in a time sensitive communication. FIG. 5 shows a high level scenario where a WTRU may be currently using MAC1 address and may decide to start using MAC2 and MAC3 addresses. Before the WTRU switches from using MAC1 address to using MAC2 and MAC3 addresses, the WTRU may transmit to the network, namely to the SMF through forwarding of the AMF, the information of switching from using MAC1 address to using MAC2 and MAC3 addresses. The SMF can then propagate that information to other (core) network entities, such as the UPF(s) anchoring an Ethernet-type PDU session, the NEF and the PCF. Through the PCF, a TSCTSF or a TSN AF can proceed to perform the required updates of MAC addresses in the network and to update external entities that are in control of TSC/TSN/DetNet capable networks connected to the mobile network.

[0098] In an embodiment, the WTRU may be capable of changing and randomized MAC (RCM) address(es). The WTRU may notify the network about impending changes of addresses, so it can be coordinated through a TSN AF or TSCTSF with an external controlling entity, in order to guarantee that traffic keeps receiving the intended deterministic treatment, regardless of the MAC address changes.

[0099] Accordingly, a method enabling WTRU RCM exposure for time sensitive communications, may comprise a step wherein the WTRU may be attached to a network, and the WTRU may be capable of changing its MAC address or using multiple MAC addresses simultaneously. In another step, the WTRU may decide to change its MAC address(es). This behavior might be triggered by an application on the WTRU or by configuration policies. In case of TSN integration is enabled, this may imply a DS-TT port change. In another step, the WTRU may transmit notification to the network (e.g., SMF) comprising information indicating the tentative new MAC address(es) before they are changed. The notification may indicate what tentative new MAC address(es) are associated with a currently in use MAC address. In another step, the network (e.g., SMF) may notify the TSN AF or TSCTSF about the impending change. In another step, the TSN AF/TSCTSF may communicate the information to an external controlling entity, so required MAC address(es) updates (e.g., hold-and-forward mechanism) can be precomputed. In another step, (e.g., once ready) the external controlling entity may acknowledge to the TSN AF/TSCTSF such that the TSN AF/TSCTSF may instruct the WTRU to perform the actual MAC address change. In another step, the WTRU/terminal may start using the new MAC address(es), with both the WTRU and the network applying consistent traffic treatment to guarantee deterministic behavior.

[0100] More particularly, in details, according to an embodiment, an extended WTRU requested PDU session modification procedure enabling exposure in advance of the MAC address(es) to be used by the WTRU, is described. The exposure can be used by the TSC/TSN/DetNet controlling entities to recompute as needed the mechanisms in the network to keep providing the required treatment to the traffic of the device. Signaling extensions may be shown. Existing 3GPP procedures may not be elaborated in detail but summarized for context. Extensions and new behavior are highlighted. Note that variations are possible (e.g., for roaming scenarios) over this exemplary signaling diagram. It is assumed that the WTRU may have already registered on the AMF.

[0101] Referring to FIG. 6A and FIG. 6B, a message sequence chart of a WTRU requested PDU session modification procedure is shown. More particularly, the WTRU may be capable of performing RCM such that the WTRU may decide to switch from using a MAC1 address to use MAC2 and MAC3 addresses.

[0102] Accordingly, at step 1, the WTRU is transmitting, to the AMF, a PDU session modification request message that may include a list of current and tentative MAC addresses. The current MAC address(es) may be the ones currently being used by the WTRU, whereas the tentative MAC address(es) may be the ones selected to be used. In this example, it contains MAC1 address (currently in use) and MAC2, MAC3 addresses (selected as new to be used).

[0103] Alternatively, the PDU session establishment/modification message may contain an index value to indicate the MAC address(es) selected for future next, from a previously agreed upon list of MAC addresses (e.g., provided through the initial PDU session establishment or provided by an application function/application server (AF/AS)). The list of current and tentative MAC addresses may be formatted such that the link between a current MAC address and tentative MAC address(es) is indicated. The WTRU may format the list in this manner so that the network knows what packet filters to associate the tentative MAC address(es) with. The WTRU may format the list in this manner so that the network can detect that the tentative MAC address is in use and that the current MAC address is no longer in use.

[0104] At step 2, the AMF may transmit, to the SMF, a Nsmf PDUSession UpdateSMContext request message, including the list of current and tentative MAC addresses.

[0105] At step 3, the SMF may report the event of the WTRU-triggered change of MAC addresses (e.g., RCM event) to the PCF by performing an SMF initiated SM policy association modification procedure, including the list of current and tentative MAC addresses.

[0106] At step 4a, the PCF may transmit an update message to the TSCTSF/TSN AF to inform about the decision of the WTRU to update its MAC address(es) and, if required, the updated mapping between the DS-TT port and the DS-TT port MAC address.

[0107] At step 5a, the TSCTSF/TSN AF may transmit to an external controller (e.g., CNC or DetNet controller) a message comprising information about the updated MAC address(es), such that the external controller can recompute and reconfigure the network.

[0108] The external controller may recompute and may reconfigure the network to prepare for the change of MAC address(es) of the WTRU. At this point the network may be configured for the WTRU to use the new MAC address(es). Accordingly, at step 5b, the external controller may transmit to the TSCTSF/TSN AF an update of MAC address acknowledgment message and, at step 4b, the TSCTSF/TSN AF may transmit to the PCF another message to inform about the update of MAC address through another update of MAC address acknowledgment message.

[0109] At step 7a, the SMF may update the UPF with N4 rules. The SMF may transmit to the UPF a N4 session modification request message comprising information including the list of current and tentative MAC addresses in the message.

[0110] At step 7b, the UPF may respond to the SMF. The UPF may transmit to the SMF a N4 session modification response message comprising information including the list of current and tentative MAC addresses acknowledged by the UPF. This may allow the UPF to notify potential issues, such as a potential address conflict (e.g., if already in use) or unsupported MAC address(es) back to the WTRU.

[0111] At step 8, the SMF transmit to the AMF, a Nsmf PDUSession UpdateSMContext response message including information (e.g., N2 SM information) that the AMF shall provide to the (R)AN. It may include information regarding QoS flows of the updated (tentative) MAC address(es). [0112] At step 9, the AMF may transmit N2 message to the (R)AN that may include the information regarding QoS flows of the updated (tentative) MAC address(es).

[0113] At step 10a, the (R)AN may issue AN specific signaling exchange with the WTRU that may be related with the information received from SMF. For example, modifying the necessary (R)AN resources related to the new tentative MAC address(es) of the PDU Session. This message may be used as a confirmation for the WTRU about the use of the new tentative MAC address(es) such that, at step 10b the WTRU may use the new MAC address(es).

[0114] At step 11, the (R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU session ack message to the AMF.

[0115] At step 12a, the AMF may transmit to the SMF, the N2 SM message received from the AN via Nsmf_PDUSession_UpdateSMContext request message.

[0116] At step 12b, the SMF may transmit to the AMF, a Nsmf PDUSession UpdateSMContext response message.

[0117] At step 13a, The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by transmitting a N4 Session Modification Request message to the UPF.

[0118] At step 13b, the UPF may transmit to the SMF an N4 session modification response message.

[0119] At step 14, the WTRU may acknowledge the PDU Session Modification Command by transmitting a NAS message PDU Session Modification Command Ack to the (R)AN.

[0120] At step 15, the (R)AN may transmit the NAS message to the AMF, by sending a N2 NAS uplink transfer message to the AMF.

[0121] At step 16a, the AMF may transmit, to the SMF, the N1 SM container (PDU Session Modification Command Ack) received from the AN to the SMF via a Nsmf_PDUSession_UpdateSMContext request message.

[0122] At step 16b, the SMF may transmit to the AMF a Nsmf PDUSession UpdateSMContext Response message.

[0123] At step 17a, the SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by transmitting a N4 Session Modification Request message to the UPF. This might involve updating Ethernet Packet Filter Set(s) and forwarding rule(s) to adapt to the new MAC address(es). The message from the SMF may indicate current and tentative MAC address(es) that are associated with each Ethernet Packet Filter Set.

[0124] At step 17b, the UPF may transmit, to the SMF, a N4 Session Modification response message. [0125] At step 18, the SMF may notify the PCF whether the Policy and charging control (PCC) decision could be enforced or not by performing an SMF initiated SM Policy Association Modification procedure.

[0126] When the UPF detects an ethernet frame that includes a tentative MAC Address, the UPF may determine that the tentative MAC Address is now a current MAC address and the UPF may determine that the MAC Address that the SMF indicated is current, is no longer in use and should be blocked. Blocked may mean that ethernet frames that include the no longer in use MAC address should be discarded. Also, when the UPF detects an ethernet frame that includes a tentative MAC Address, the UPF may send an N4 message to the SMF that indicates that the tentative MAC Address is now a current MAC address. The SMF may use this notification to update PCC Rules so that they no longer include the no longer in use MAC address.

[0127] In various embodiments, the network may enable RCM, and request the WTRU (e.g., through a network initiated PDU Session Modification request) to send start using a different MAC address(es) (e.g., by sending a PDU Session Modification Request). The network could use different events to trigger this, including subscription policies or external triggers from an AF (e.g., AF requests RCM through the NEF).

[0128] In order to enable connected terminal RCM exposure for time sensitive communications, in various embodiments, an extended TSC/TSN station Requested PDU Session Modification procedure enabling exposure in advance of the MAC address(es) to be used by a TSC/TSN station bridged by a WTRU is described below. The connected terminal RCM exposure can be used by the TSC/TSN/DetNet controlling entities to recompute as needed the mechanisms in the network to keep providing the required treatment to the traffic of the device. Signaling extensions may be shown. In the description below, existing 3GPP procedures may be not elaborated in detail but summarized for context. Extensions and new behavior are highlighted. FIG. 7 shows (e.g., proactive) TSC/TSN station bridged by a WTRU RCM exposure signaling. FIG. 7 shows a high level scenario where a connected terminal (e.g., TSN/TSC end stations) may be currently using MAC1 address and may decide to start using MAC2 and MAC3 addresses. Note that variations may be possible (e.g., for roaming scenarios) over FIG. 7. We assume that the WTRU has already registered on the AMF.

[0129] The TSC/TSN station connected to a WTRU may be capable of changing and randomized MAC address(es). The WTRU (or the TSC/TSCN station) may inform the network about its intention to change its MAC address(es), so it can be coordinated through the TSN AF or TSCTSF with external controlling entities, in order to guarantee that traffic keeps receiving the intended deterministic treatment, regardless of the MAC address(es) changes. [0130] Two options /alternatives may be considered: (i) the TSC/TSN station may directly inform the TSCTSF/TSN AF about MAC address(es) change decision; (ii) the TSC/TSN station may directly inform the WTRU about MAC address(es) change decision.

[0131] In an embodiment, a method Enabling connected terminal RCM exposure for Time Sensitive Communications may comprise a step wherein the WTRU is attached to the network. A connected (brigded) terminal (e.g., TSC/TSN end station) may be capable of changing its MAC address or using multiple addresses simultaneously. In another step, the connected terminal may decide to change its MAC address(es). In case of TSN integration is enabled, this may imply a Link Layer Discovery Protocol (LLDP) neighbor changes to report. In another step, the TSN/TSC terminal may notify the TSN AF/TSCTSF or the WTRU about the change. In the latter case, the WTRU may notify the network (e.g., SMF) the new address(es) before they are changed, and the SMF may notify the TSN AF/TSCTSF about the impending change. In another step, the TSN AF/TSCTSF may communicates this to an external controlling entity (e.g., LLDP discovery), so required updates (e.g., hold-and-forward mechanism) can be pre-computed. In another step, (e.g., once ready) the external controlling entity may acknowledge to the TSN AF/TSCTSF that can then instruct the TSN end station (directly or via the WTRU) to perform the actual MAC address(es) change. In another step, the TSN/TSC end station may start using the new MAC address(es), with the WTRU, terminal and the network applying consistent traffic treatment to guarantee deterministic behavior.

[0132] Referring to FIG. 8A and FIG. 8B, a message sequence chart of a WTRU requested PDU session modification procedure is shown. More particularly, the TSN/TSC station may be capable of performing RCM such that the TSN/TSC may decide to switch from using a MAC1 address to use MAC2 and MAC3 addresses.

[0133] Referring to FIG. 8A, step 1 to step 5 corresponds to option A, wherein the TSC/TSN station may directly inform the TSCTSF/TSN AF about MAC address(es) change decisions.

[0134] At step 1, the TSC/TSN station may inform the TSCTSF/TSN AF about current and intended (tentative) MAC address(es). The current MAC address(es) may be the ones currently being used by the TSC/TSN station, whereas the tentative MAC address(es) may be the ones selected to be used. In this example, it contains MAC1 (currently in use) and MAC2, MAC3 (selected as new to be used). At step 2, the TSCTSF/TSN AF may transmit to an external controller (e.g., CNC or DetNet controller) information about the updated MAC address(es), so the external controller can recompute and reconfigure the network. At step 3, the external controller may recompute and reconfigure (e.g., as needed) the network to prepare for the change of address(es) of the WTRU. At step 4, the TSCTSF/TSN AF may transmit to the PCF information about the request to update the MAC address(es) used by the TSC/TSN station bridged by the WTRU. At step 5, the PCF performs a PCF initiated SM Policy Association Modification procedure to notify SMF about the modification of policies, including the list of current and tentative MAC addresses. [0135] Referring to FIG. 8A, step 6 to step 12 corresponds to option B, wherein the TSC/TSN station may directly inform the UE about MAC address(es) change decisions.

[0136] At step 6, the TSC/TSN station may inform the WTRU about current and intended (tentative) MAC address(es). The current MAC address(es) may be the ones currently being used by the TSC/TSN station, whereas the tentative MAC address(es) may be the ones selected to be used. In this example, it contains MAC1 (currently in use) and MAC2, MAC3 (selected as new to be used). At step 7, the WTRU may transmit to the AMF a PDU Session Modification Request message including a list of current and tentative MAC addresses. The current MAC address(es) may be the ones currently being used by the WTRU, whereas the tentative MAC address(es) may be the ones selected to be used. In this example, it contains MAC1 (currently in use) and MAC2, MAC3 (selected as new to be used). Alternatively, the PDU Session Establishment/Modification message may contain an index value to indicate the MAC address(es) selected for future next, from a previously agreed upon list of MAC addresses (e.g., provided through the initial PDU Session Establishment or provided by an Application Function/ Application Server). At step 8, the AMF may transmit to the SMF a Nsmf PDUSession UpdateSMContext Request message, that may include the list of current and tentative MAC addresses. At step 9, the SMF may report the event of the WTRU-triggered change of MAC addresses (we can refer to it as RCM event) to the PCF by performing an SMF initiated SM Policy Association Modification procedure, including the list of current and tentative MAC addresses. At step 10a, the PCF may transmit, to the TSCTSF/TSN AF, an update message comprising information about the decision of the WTRU to update its MAC address(es) and, (e.g., if required), the updated mapping between the DS-TT port and the DS-TT port MAC address. At step I la, the TSCTSF/TSN AF may transmit to the external controller (e.g., CNC or DetNet controller) information about the updated MAC address(es), so the external controller can recompute and reconfigure the network. At step 12, The external controller recomputes, reconfigures and schedules (e.g., as needed) the network to prepare for the change of address(es) of the WTRU. At step 1 lb, the external controller (e.g., CNC or DetNet controller) may transmit to the TSCTSF/TSN AF an updated MAC address acknowledgement message. At step 10b, the TSCTSF/TSN AF may transmit to the PCF another updated MAC address acknowledgement message.

[0137] Referring to FIG. 8B, step 13a to step 25, expected step 17, corresponds to option A and B, and step 17 corresponds only to option A. At step 13a, The SMF may update the UPF with N4 rules. The SMF may transmit, to the UPF, a N4 session modification request message comprising information including the list of current and tentative MAC addresses in the message. At step 13b, the UPF responds to the SMF. The UPF may transmit, to the SMF, a N4 session modification response message comprising information including the list of current and tentative MAC addresses acknowledged by the UPF. This may allow the UPF to notify potential issues, such as a potential address conflict (e.g., if already in use) or unsupported MAC address(es) back to the WTRU. At step 14, the SMF may transmit to the AMF a Nsmf_PDUSession_UpdateSMContext Response message. This message may include (N2 SM information) information that the AMF shall provide to the (R)AN. It may include information regarding QoS flows of the updated (tentative) MAC address(es). At step 15, the AMF may transmit N2 message to the (R)AN. The N2 message may include the N2 SM information and may also include the information regarding QoS flows of the updated (tentative) MAC address(es). At step 16, The (R)AN may issue AN specific signaling exchange with the WTRU that is related with the information received from SMF. For example, modifying the necessary (R)AN resources related to the new tentative MAC address(es) of the PDU Session. This message serves as confirmation for the WTRU about the use of the new tentative MAC address(es). In case of option A, at step 17, the WTRU may acknowledge the request of the TSC/TSN station to perform the MAC address(es) change. At step 18, the (R)AN may acknowledge N2 PDU Session Request by transmitting a N2 PDU Session Ack Message to the AMF. At step 19a, the AMF may forward, to the SMF, the N2 SM received from the AN by transmitting a Nsmf_PDUSession_UpdateSMContext request message. At step 19b, the SMF may transmit to the AMF a Nsmf PDUSession UpdateSMContext Response message. At step 20a, the SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by transmitting N4 Session Modification Request message to the UPF. At step 20b, the UPF may transmit to the SMF a N4 session modification response message. At step 21, the WTRU may acknowledge the PDU Session Modification Command by transmitting a NAS message PDU Session Modification Command Ack. At step 22, the (R)AN may transmit the NAS message to the AMF. At step 23a, the AMF forwards the N1 SM container (PDU Session Modification Command Ack) received from the AN to the SMF by transmitting a Nsmf_PDUSession_UpdateSMContext request message to the SMF. At step 23b, the SMF transmit to the AMF a Nsmf_PDUSession_UpdateSMContext Response message. At step 24a, The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by transmitting a N4 Session Modification Request message to the UPF. This might involve updating Ethernet Packet Filter Set(s) and forwarding rule(s) to adapt to the new MAC address(es). At step 24b, the UPF may transmit, to the SMF, a N4 Session Modification Response message. At step 25, the SMF may notify the PCF whether the PCC decision could be enforced or not by performing an SMF initiated SM Policy Association Modification procedure.

[0138] In various embodiments, the network may enable RCM, and request the WTRU (e.g., through a network initiated PDU Session Modification request) to instruct a bridged TSC/TSN station to start using a different MAC address(es). The network could use different events to trigger this, including subscription policies or external triggers from an AF (e.g., AF requests RCM through the NEF).

[0139] In case of the TSN/TSC end station does not support MAC address(es) change signaling prior to the actual change, the change may be detected by the WTRU and notified to the network and TSN AF/TSCTSF.

[0140] Figure 9 shows a high level diagram of an embodiment wherein a TSC/TSN end station may be allowed to use the old and new MAC address(es) for some time (a time window T) to facilitate the transition. In addition to the embodiment illustrated by FIG. 7, FIG. 8a and FIG. 8b, the signaling used to convey both current and new (tentative) MAC address(es) to use may be extended to include a new parameter: a time window T, during which both old and new addresses should be operational. Note that this signaling may include the messages sent by the TSC/TSN end station and WTRU, but also the ones exchanged between network entities (e.g., SMF, AMF, PCF, etc).

[0141] The external TSC/TSN/DetNet controlling entities may use the new parameter T to compute and configure the network to support traffic using either old or new MAC address(es) during the time window. This might require adding new logical DS-TT ports and considering additional flows.

[0142] Referring to FIG. 10, in an embodiment, a method 1000, implemented in a wireless transmit/receive unit, WTRU, may comprise a step of transmitting 1010 to a mobile network, a first message comprising a first information indicating an intention of the WTRU to switch from using one or more current MAC addresses to one or more new MAC addresses. The WTRU may be capable of changing its Medium Access Control, MAC, addresses and/or using multiple MAC, addresses. Transmitting the first message to the mobile network may be a transmission of the first message to a network controlling entity via a network element of the mobile network. Transmitting the first message may be on condition that a RCM trigger event of switching MAC address occur. The trigger event may be a part of subscription policies, or the trigger may be an external trigger from an AF (e.g., AF may request RCM through a Network Exposure Function (NEF)). The external controlling entity may be any of a time-sensitive communications, TSC, controlling entity, a time-sensitive networking, TSN, controlling entity, and a deterministic networking, DetNet, controlling entity. The network element may be any of a TSN AF and a TSCTSF of the mobile network. The first message may comprise a list of the one or more current MAC addresses and the one or more new MAC addresses, wherein each of the one or more current MAC addresses of the list may be associated with at least the one or more new MAC addresses. The first information may indicate an index value indicating the one or more new MAC addresses, wherein the index value may have been received by the WTRU from an application function/application server. The first message may be a protocol data unit, PDU, session modification or a PDU establishment request message.

[0143] The method 1000, may further comprise a step of receiving 1020, from the mobile network, a second message comprising a second information indicating instruction for switching from the one or more current MAC addresses to the one or more new MAC addresses; and a step of switching 1030 from the one or more current MAC addresses to the one or more new MAC addresses for communicating with the mobile network based on the second message.

[0144] The one or more new MAC addresses may comprise at least one or more current MAC addresses. The WTRU may use sequentially and/or simultaneously the new MAC addresses.

[0145] The method 1000, may further comprise a step of receiving a third message comprising a third information indicating mobile network reconfiguration based on the one or more new MAC addresses.

[0146] Conclusion

[0147] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems. [0148] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e., infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves. [0149] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and/or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0150] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0151] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0152] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0153] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0154] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0155] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.

[0156] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be effected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

[0157] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0158] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

[0159] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0160] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0161] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of' followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0162] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0163] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0164] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

1. A method, implemented in a wireless transmit/receive unit, WTRU, the method comprising: transmitting, to a mobile network, a first message comprising a first information indicating an intention of the WTRU to switch from using one or more current Medium Access Control, MAC, addresses to one or more new MAC addresses; receiving, from the mobile network, a second message comprising a second information indicating instruction for switching from the one or more current MAC addresses to the one or more new MAC addresses; and switching from the one or more current MAC addresses to the one or more new MAC addresses for communicating with the mobile network based on the second message.

2. The method of claim 1, wherein the WTRU is capable of changing its MAC address and/or using multiple MAC address.

3. The method of any of claim 1 and claim 2, comprising, prior to transmitting the first message: receiving, from an external entity, a notification message comprising information indicating a request to change the one or more current MAC addresses to the one or more new MAC addresses.

4. The method of claim 3, wherein the external entity is a time-sensitive communications station bridged by the WTRU.

5. The method of any of claim 1 to claim 4, wherein transmitting the first message comprises transmitting to a network controlling entity via a network element of the mobile network.

6. The method of claim 5, wherein the network controlling entity is any of a time-sensitive communications, TSC, controlling entity, a time-sensitive networking, TSN, controlling entity, and a deterministic networking, DetNet, controlling entity.

7. The method of any of claim 5 and claim 6, wherein the network element is a TSN application function, AF, and/or a Time Sensitive Communication and Time Synchronization Function, TSCTSF, of the mobile network.

8. The method of any of claim 1 to claim 7, comprising using sequentially and/or simultaneously the one or more new MAC addresses.

9. The method of any of claim 1 to claim 8, wherein the one or more new MAC addresses comprise at least one or more current MAC addresses.

10. The method of any of claim 1 to claim 9, wherein the first message is a protocol data unit, PDU, session modification or a PDU establishment request message.

11. The method of any of claim 1 to claim 10, comprising receiving a third message comprising a third information indicating a mobile network reconfiguration based on the one or more new MAC addresses.

12. The method of any of claim 1 to claim 11, wherein the first message comprises a list of the one or more current MAC addresses and the one or more new MAC addresses.

13. The method of claim 12, wherein each of the one or more current MAC addresses of the list is associated with at least the one or more new MAC addresses.

14. The method of any of claim 1 to claim 13, wherein the first information indicates an index value indicating the one or more new MAC addresses.

15. The method of claim 14, comprising receiving, from an application function/application server, the index value.

16. The method of any of claim 1 to claim 15, comprising transmitting the first message on condition of a trigger event of switching MAC address.

17. The method of claim 16, wherein the trigger event is from subscription policies or is an external trigger from an AF.

18. A wireless transmit/receive unit, WTRU, comprising any of a memory and a processor, configured to: transmit, to a mobile network, a first message comprising a first information indicating an intention of the WTRU to switch from using one or more current MAC addresses to one or more new MAC addresses; receive, from the mobile network, a second message comprising a second information indicating instruction for switching from the one or more current Medium Access Control, MAC, addresses to the one or more new MAC addresses; and switch from the one or more current MAC addresses to the one or more new MAC addresses for communicating with the mobile network based on the second message.

19. The WTRU of claim 18, wherein the WTRU is capable of changing its MAC address and/or using multiple MAC address.

20. The WTRU of any of claim 18 and claim 19, configured to: receive, from an external entity, a notification message comprising information indicating a request to change the one or more current MAC addresses to the one or more new MAC addresses, prior to transmit the first message.

21. The WTRU of claim 20, wherein the external entity is a time-sensitive communications station bridged by the WTRU.

22. The WTRU of any of claim 18 to claim 21, configured to: transmit the first message to a network controlling entity via a network element of the mobile network.

23. The WTRU of claim 22, wherein the network controlling entity is any of a time-sensitive communications, TSC, controlling entity, a time-sensitive networking, TSN, controlling entity, and a deterministic networking, DetNet, controlling entity.

24. The WTRU of any of claim 22 and claim 23, wherein the network element is a TSN AF and/or a Time Sensitive Communication and Time Synchronization Function, TSCTSF, of the mobile network.

25. The WTRU of any of claim 18 to claim 24, configured to use sequentially and/or simultaneously the one or more new MAC addresses.

26. The WTRU of any of claim 18 to claim 25, wherein the one or more new MAC addresses comprise at least one or more current MAC addresses.

27. The WTRU of any of claim 18 to claim 26, wherein the first message is a protocol data unit, PDU, session modification or a PDU establishment request message.

28. The WTRU of any of claim 18 to claim 27, configured to receive a third message comprising a third information indicating mobile network reconfiguration based on the one or more new MAC addresses.

29. The WTRU of any of claim 18 to claim 28, wherein the first message comprises a list of the one or more current MAC addresses and of the one or more new MAC addresses.

30. The WTRU of claim 29, wherein each of the one or more current MAC addresses of the list is associated with at least the one or more new MAC addresses.

31. The WTRU of any of claim 18 to claim 30, wherein the first information indicates an index value indicating the one or more new MAC addresses.

32. The WTRU of claim 31, configured to receive, from an application function/application server, the index value.

33. The WTRU of any of claim 18 to claim 32, configured to transmit the first message on condition of a trigger event of switching MAC address.

34. The WTRU of claim 33, wherein the trigger event is from subscription policies or is an external trigger from an AF.