Mobile station relay verification

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a mobile station may receive data from a first network entity to be relayed to a second network entity. The mobile station may send the data to the second network entity. The mobile station may receive a digitally signed confirmation of receipt of the data from the second network entity. The mobile station may send the digital signature acknowledgement to the first network entity. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 17 / 823,917, filed on August 31, 2022, entitled “MOBILE STATION RELAYING VERIFICATION,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for mobile station relay authentication. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive data to be relayed to a second network entity from a first network entity based at least in part on information stored in the memory. The one or more processors may be configured to send the data to the second network entity based at least in part on information stored in the memory. The one or more processors may be configured to receive a digital signature confirmation of receipt of the data from the second network entity based at least in part on information stored in the memory. The one or more processors may be configured to send the digital signature confirmation to the first network entity based at least in part on information stored in the memory.

[0008] Some aspects described herein relate to a mobile station for wireless communication. The mobile station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive data from a relay mobile station originating from a network entity and relayed by the relay mobile station based at least in part on information stored in the memory. The one or more processors may be configured to send a digital signature confirmation of receipt of the data to the relay mobile station based at least in part on information stored in the memory.

[0009] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send data to a relay mobile station to be relayed to a remote mobile station based at least in part on information stored in the memory. The one or more processors may be configured to receive from the relay mobile station a digital signature confirmation that the remote mobile station received the data based at least in part on information stored in the memory.

[0010] Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include receiving, by the mobile station, data to be relayed to a second network entity from a first network entity. The method may include sending, by the mobile station, the data to the second network entity. The method may include receiving, by the mobile station, a digitally signed confirmation of receipt of the data from the second network entity. The method may include sending, by the mobile station, the digitally signed confirmation to the first network entity.

[0011] Some aspects described herein relate to a method of wireless communication performed by a mobile station. The method may include receiving, by the mobile station, data from a relay mobile station that originated from a network entity and was relayed by the relay mobile station. The method may include sending, by the mobile station, to the relay mobile station, a digitally signed confirmation of receipt of the data.

[0012] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending, by the network entity, data to be relayed to a remote mobile station to a relay mobile station. The method may include receiving, by the network entity, from the relay mobile station a digitally signed confirmation that the data was received by the remote mobile station.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a mobile station. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to receive data from a first network entity to be relayed to a second network entity. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to send data to the second network entity. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to receive a digitally signed confirmation of receipt of the data from the second network entity. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to send a digitally signed confirmation to the first network entity.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a mobile station. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to receive data from a relay mobile station that originated from a network entity and was relayed by the relay mobile station. The set of instructions, when executed by one or more processors of the mobile station, may cause the mobile station to send a digitally signed confirmation of receipt of the data to the relay mobile station.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send data to a relay mobile station to be relayed to a remote mobile station. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive a digital signature confirmation of the remote mobile station receiving the data from the relay mobile station.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving data to be relayed to a second network entity from a first network entity. The apparatus may include means for sending the data to the second network entity. The apparatus may include means for receiving a digitally signed confirmation of receipt of the data from the second network entity. The apparatus may include means for sending the digitally signed confirmation to the first network entity.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving data from a relay mobile station that originated from a network entity and was relayed by the relay mobile station. The apparatus may include components for sending a digitally signed confirmation of receipt of the data to the relay mobile station.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending data to a relay mobile station to be relayed to a remote mobile station. The apparatus may include means for receiving from the relay mobile station a digitally signed confirmation of data received by the remote mobile station.

[0019] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0020] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0021] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0023] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0024] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0026] Figure 4 is a diagram illustrating an example of a relay UE that relays communications between the UE and a network node according to the present disclosure.

[0027] Figure 5 is a diagram illustrating an example of incentive-based relaying according to the present disclosure.

[0028] FIG. 6A to FIG. 6B is a diagram illustrating an example associated with UE relay authentication according to the present disclosure.

[0029] Figure 7 is a diagram illustrating an example associated with Layer 2 (L2) relay enhancement for UE relay verification according to the present disclosure.

[0030] Figure 8 is a diagram illustrating an example process performed, for example, by a mobile station according to the present disclosure.

[0031] Fig. 9 is a diagram illustrating an example process performed, for example, by a mobile station according to the present disclosure.

[0032] Fig.10 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0033] Figures 11 to 13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0034] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0035] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0037] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0038] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0039] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0040] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a certain number of different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0041] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0042] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0043] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0044] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0045] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0046] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0047] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0048] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0050] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, a mobile station (e.g., UE 120) may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may receive data from a first network entity to be relayed to a second network entity; send the data to the second network entity; receive a digitally signed confirmation of receipt of the data from the second network entity; and send the digitally signed confirmation to the first network entity. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0052] In some aspects, as described in more detail elsewhere herein, the communication manager 140 may receive data from a relay mobile station that originated from a network entity and was relayed by the relay mobile station; and send a digitally signed confirmation of receipt of the data to the relay mobile station. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0053] In some aspects, a network entity (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send data to a relay mobile station to be relayed to a remote mobile station; and receive from the relay mobile station a digitally signed confirmation of the data received by the remote mobile station. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0054] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0055] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0056] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0057] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0058] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0059] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0060] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to FIG. 6A to FIG. 6B and Figures 7 to 13 ).

[0061] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 200 to FIG. 1 ). FIG. 6A to FIG. 6B and Figures 7 to 13 ).

[0062] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network node 110 may perform one or more techniques associated with mobile station relay authentication, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 In some aspects, the mobile station described herein is a UE 120, is included in a UE 120, or includes Figure 2 One or more components of UE 120 are shown.

[0063] In some aspects, a mobile station (e.g., UE 120) includes: means for receiving, by the mobile station, data from a first network entity to be relayed to a second network entity; means for sending, by the mobile station, data to the second network entity; means for receiving, by the mobile station, a digitally signed confirmation of receipt of the data from the second network entity; and / or means for sending, by the mobile station, a digitally signed confirmation to the first network entity. In some aspects, means for the mobile station to perform operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0064] In some aspects, a mobile station (e.g., UE 120) includes: a component for receiving, by the mobile station, data originating from a network entity and relayed by the relay mobile station; and / or a component for sending, by the mobile station, a digitally signed confirmation of receipt of the data to the relay mobile station. In some aspects, the components for the mobile station to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0065] In some aspects, the network entity (e.g., network node 110) includes: a component for sending data to be relayed to a remote mobile station by the network entity to a relay mobile station; and / or a component for receiving a digital signature confirmation of data received by the remote mobile station from the relay mobile station by the network entity. In some aspects, the components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0066] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0067] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0068] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0069] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0070] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0071] Figure 33 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0072] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0073] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU310 may be implemented to communicate with the DU 330 for network control and signaling.

[0074] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0075] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0076] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0077] The non-RT RIC 315 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0078] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0079] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0080] Figure 4 4 is a diagram illustrating an example 400 of a relay UE that relays communications between a UE and a network node according to the present disclosure. As shown, the example 400 includes a UE 405, a relay UE 410, and a network node 110. In the example 400, the UE 405 is an Rx UE, and the relay UE 410 is a Tx UE. In some aspects, the UE 405 is a UE 120, and the relay UE 410 is another UE 120. In some aspects, the UE 405 may be referred to as a remote UE.

[0081] like Figure 4As shown, UE 405 may receive communications (e.g., data and / or control information) directly from network node 110 as downlink communications 415. Additionally or alternatively, UE 405 may receive communications (e.g., data and / or control information) indirectly from network node 110 via relay UE 410. For example, network node 110 may send communications as downlink communications 420 to relay UE 410, and relay UE 410 may relay (e.g., forward or send) the communications to UE 405 as sidelink communications 425.

[0082] In some aspects, UE 405 may communicate directly with network node 110 via direct link 430. For example, downlink communications 415 may be sent via direct link 430. Communications sent via direct link 430 between UE 405 and network node 110 (e.g., in downlink communications 415) do not pass through and are not relayed by relay UE 410. In some aspects, UE 405 may communicate indirectly with network node 110 via indirect link 435. For example, downlink communications 420 and sidelink communications 425 may be sent via different segments of indirect link 435. Communications sent via indirect link 435 between UE 405 and network node 110 (e.g., in downlink communications 420 and sidelink communications 425) pass through and are relayed by UE 410. Figure 4 The communication scheme shown in FIG. 4 may improve network performance and increase reliability by providing link diversity to UE 405 for communicating with network node 110.

[0083] In some cases, UE 405 may receive communications (e.g., the same communications) from network node 110 via both direct link 430 and indirect link 435. In other cases, network node 110 may select one of the links (e.g., direct link 430 or indirect link 435) and may use only the selected link to send communications to UE 405. Alternatively, network node 110 may receive an indication of one of the links (e.g., direct link 430 or indirect link 435) and may use only the indicated link to send communications to UE 405. The indication may be sent by UE 405 and / or relay UE 410. In some aspects, such selection and / or indication may be based at least in part on channel conditions and / or link reliability.

[0084] In some cases, the relay UE may use layer 2 (L2) relaying to relay communications between the network node 110 and the UE 405. In the case of using L2 relaying, the relay relationship between the relay UE 410 and the UE 405 may be known to the network node 110, and the network node 110 may store the context of the UE 405. In some cases, the relay UE may use layer 3 (L3) relaying to relay communications between the network node and the UE 405. In the case of using L3 relaying, the network node is not aware of (e.g., does not store) the context of the remote UE (e.g., UE 405).

[0085] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0086] Figure 5 is a diagram illustrating an example 500 of incentive-based relaying according to the present disclosure.

[0087] In some cases, a relay UE (or a user of a relay UE) may receive an incentive or reward for relaying data between a network node and a remote UE. For example, a network charging function (CHF) in a core network (e.g., a 5G core network) may provide a monetary payment for relaying data from a network node to a remote UE by a relay UE. In some examples, the incentive for relaying depends on the correlation of multiple reports from different entities. For example, the CHF may support reports from a relay UE and a remote UE (e.g., via the relay UE or directly). In this case, the CHF may correlate reports from the relay UE and the remote UE (e.g., core network charging reports) to verify the amount of traffic relayed to the remote UE via a particular relay UE. However, in some cases, the relay proof may not be available to verify that the relay UE relays the traffic to the remote UE. For L2 relaying, the relationship between the relay UE and the remote UE is only known to the RAN node (e.g., gNB), and the CHF may not be able to determine which relay UE relays the traffic to the remote UE. For L2 relay, if there is no transport / application ACK, the CHF may not be able to verify whether the relay UE has attempted relaying, or whether the remote UE has underreported the amount of traffic relayed to the remote UE. In addition, RAN local traffic (e.g., traffic that does not pass through the core network) such as system information (SI) broadcast by RAN nodes and relayed by the relay UE to the remote UE cannot be confirmed by the core network charging report.

[0088] In some cases, there may be multiple possible relay UEs that can relay data between the network node and the remote UE. Figure 5As shown, possible relay UEs for relaying data between the network node and the remote UE may include a first relay UE (relay UE1), a second relay UE (relay UE2), and a third relay (relay UE3). L2 relay and / or L3 relay may be supported for relaying data between the network node and the remote UE. Figure 5 As shown, the network node may send data for the remote UE to relay UE1, relay UE2, and relay UE3. The data to be relayed to the remote UE may be unicast data (which is intended for the remote UE) and / or broadcast data. In some examples, the data to be relayed to the remote UE may include core network services and / or RAN local services, such as broadcast information link SI or broadcast services (e.g., from 5G multicast broadcast service (MBS)). In some examples, L3 relay may enable direct local routing of services to the remote UE.

[0089] like Figure 5 As shown, relay UE1, relay UE2, and relay UE3 may each attempt to relay data received from a network node to a remote UE. In example 500, relay UE1 may successfully relay data to a remote UE, and relay UE1 may receive an acknowledgement (ACK) or negative acknowledgement (NACK) feedback (ACK / NACK feedback) (e.g., hybrid automatic repeat request (HARQ) ACK / NACK feedback) from the remote UE. In this case, relay UE1 (e.g., a relay UE that successfully relays a service to a remote UE) may be able to request an incentive or reward from a network node or a core network by providing a relay certificate (e.g., in a core network charging report). However, another UE (e.g., relay UE2 or relay UE3) that did not successfully relay data to a remote UE may provide a false certificate of relaying data in an attempt to request an incentive, and the network (e.g., CHF) may not be able to determine which relay UE relays the service to the remote UE.

[0090] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0091] In some examples, where a relay UE relays data to a remote UE, a core network function (e.g., a CHF, a policy control function (PCF), or a direct discovery name management function (DDNMF)) correlates and verifies the relay operation based on reports from both the relay UE and the remote UE. However, in such examples, verification requires that both the relay UE and the remote UE report the same information. This results in higher network overhead (e.g., compared to only one of the relay UE or the remote UE reporting the information), and when there is a difference between the information reported by the relay UE and the information reported by the remote UE, the network may not know whether to trust the relay UE or the remote UE. In addition, such reporting may incur high overhead of radio resources for relaying uplink communications and high power consumption at the remote UE. Additionally, in some cases, the network may be able to verify the relay proof by correlating reports from the relay UE and the remote UE, as described above in conjunction with Figure 5 as described.

[0092] Some techniques and devices described herein enable a UE to perform relay verification based at least in part on a digital signature confirmation from a remote UE. A relay UE may receive data to be relayed to a remote UE from a network node, and the relay UE may send the data to the remote UE. The relay UE may receive a digital signature confirmation of the receipt of the data from the remote UE. The digital signature confirmation may include a message and a digital signature. The message may provide proof that the data is relayed to the remote UE by the relay UE, and the digital signature may cryptographically protect the relay proof included in the message. The relay UE may send a digital signature confirmation to the network node, and the network node (or core network device) may verify the relay based at least in part on the digital signature confirmation. Therefore, compared to verification based on reports received from the relay UE and the remote UE, the network overhead for verifying the relay may be reduced. In addition, because the relay proof is cryptographically protected by a digital signature generated by the remote UE, the verification prevents UEs other than the relay UE from claiming rewards or incentives for the relay. In addition, in the case of L2 relay, in the case of L3 relay, in the case of relaying core network services, and in the case of relaying RAN local services, the relay certificate included in the digital signature confirmation can be used to verify the relay.

[0093] FIG. 6A to FIG. 6B 6 is a diagram illustrating an example 600 associated with UE (or mobile station) relay authentication according to the present disclosure. Fig. 6AAs shown, example 600 includes communication between network node 110, relay UE 120-1, and remote UE 120-2. In some aspects, network node 110, relay UE 120-1, and remote UE 120-2 may be included in a wireless network (such as wireless network 100). The network node and UE 120 (e.g., relay UE 120-1 and / or remote UE 120-2) may communicate via a wireless access link, which may include an uplink and a downlink. Relay UE 120-1 and remote UE 120-2 may communicate via a wireless access link that may include a side link. In some aspects, relay UE 120-1 may be a mobile station (e.g., a relay mobile station), may include a mobile station, or may be included in a mobile station. In some aspects, remote UE 120-2 may be a mobile station (e.g., a remote mobile station), may include a mobile station, or may be included in a mobile station. In some aspects, the network node 110 may be a base station, a decomposed base station, or one or more units (eg, CU, DU, RU) of a decomposed base station, or a combination thereof.

[0094] In some aspects, relay UE 120-2 may perform as in conjunction with Fig. 6A and Figure 6B Operations described with respect to verifying that data is relayed from a first network entity to a second network entity by a relay UE 120-1. In some aspects, as shown in example 600, the first network entity may be a network node 110, and the second entity may be a remote UE 120-2. In this case, the verification may involve relaying downlink data from the network node 110 to the remote UE 120-2 by the relay UE 120-1. In other aspects, the first network entity may be a UE (e.g., a transmitting UE), and the second network entity may be a remote UE 120-2 (e.g., for verifying the relaying of sidelink data by the relay UE 120-1).

[0095] like Fig. 6A As shown, and by reference numeral 605, the network node 110 may send data, and the relay UE 120-1 may receive the data sent by the network node 110. The data may be data to be relayed to the remote UE 120-2. The relay UE 120-1 may receive the data (e.g., a data packet) and determine to relay the data to the remote UE 120-2.

[0096] In some aspects, relay UE 120-1 determines to relay data to remote UE 120-2 based at least in part on information included in the data identifying remote UE 120-2. For example, the information identifying remote UE 120-2 may be included in a control message accompanying the data, or the information identifying remote UE 120-2 may be included in a data packet including the data (e.g., in a PDCP header). In such examples, the information may identify remote UE 120-2 as a destination for data sent by network node 110. For example, the data may be unicast data with remote UE 120-2 as a destination.

[0097] In some aspects, the data may be broadcast data transmitted (e.g., broadcast) by the network node 110, and the relay UE 120-1 may determine that the data is relayed to the remote UE 120-2 based at least on a request for the broadcast data from the remote UE 120-2. In this case, the remote UE 120-2 may transmit (e.g., in a unicast transmission to the relay UE 120-1 or in a broadcast transmission) a request for the broadcast data transmitted by the network node 110. For example, the broadcast data may include SI broadcast by the network node 110. The relay UE 120-1 may receive the request for the broadcast data from the remote UE 120-2, and the relay UE 120-1 may determine to relay the broadcast data to the remote UE 120-2 in conjunction with receiving the request for the broadcast data.

[0098] As shown by reference numeral 610, relay UE 120-1 may send (e.g., relay) data to remote UE 120-2. Remote UE 120-2 may receive data that originated from network node 110 and was relayed by relay UE 120-1. Relay UE 120-1 may send data to remote UE 120-2 (and remote UE 120-2 may receive data from relay UE 120-1) based at least in part on relay UE 120-1 determining to relay the data.

[0099] As further shown by reference numeral 615, remote UE 120-2 may generate a digitally signed confirmation of receipt of data relayed from relay UE 120-1. Remote UE 120-2 may be configured to send feedback including ACK / NACK feedback (e.g., HARQ ACK / NACK feedback) to relay UE 120-1 based at least in part on receiving the data from relay UE 120-1. Remote UE 120-2 may determine whether the feedback is to include an ACK (e.g., in conjunction with successful decoding of the data) or a NACK (e.g., in conjunction with unsuccessful decoding of the data). In some aspects, remote UE 120-2 may generate a digitally signed confirmation of receipt of data relayed from relay UE 120-1 based at least in part on determining that feedback for the relayed data will include an ACK (e.g., based at least in part on successfully decoding the relayed data).

[0100] In some aspects, the digital signature confirmation may include a message and a digital signature. The message may include one or more parameters associated with sending data from the relay UE 120-1 to the remote UE 120-2 (e.g., one or more parameters associated with the relay UE 120-1 relaying the data to the remote UE 120-2). For example, the message may include one or more parameters, such as the size of the data, the priority associated with the data, the quality of service (QoS) parameter associated with the data, the QoS flow identifier (QFI) associated with the data, the number of radio resources used to send the data from the relay UE 120-1 to the remote UE 120-2, and / or the number of transmission attempts for sending the data from the relay UE 120-1 to the remote UE 120-2, etc. In some aspects, the message may include (e.g., to the network node 110) one or more parameters that provide proof of relaying by the relay UE 120-1. In some aspects, the message may include one or more parameters to be used (e.g., by the network node 110 or a core network device) to determine an incentive associated with relaying the data. In some aspects, the digital signature includes a message digest associated with the message, the message digest being encrypted based at least in part on a private security key associated with the remote UE 120-2. The message digest may be the result of applying a hash function to the message (e.g., message digest = hash (message)). The digital signature may provide security for the proof of the relay information included in the message. For example, the digital signature may be used by the network node 110 to verify that the proof of the relay information included in the message originated from the remote UE 120-2 and that the digital signature confirmation was not changed before being sent to the network node 110.

[0101] Figure 6B An example 650 of generating a digital signature confirmation by the remote UE 120-2 is shown. As shown at reference numeral 652, Figure 6BIn example 650, the message may include an indication of the size of the data to be relayed to the remote UE 120-2 (e.g., in Figure 6B ), a priority associated with the data, a QoS parameter or QFI associated with the data, and a number of transmission attempts for transmitting the data from the relay UE 120-1 to the remote UE 120-2. As shown by reference numeral 654, the remote UE 120-2 may calculate / determine a message digest corresponding to the message by applying a hash function to the message. For example, the remote UE 120-2 may determine the message digest using a secure hash algorithm 1 (SHA-1) hash function or another hash function. The message digest is generated by applying a hash function to the message. As shown by reference numeral 656, the remote UE 120-2 may then encrypt the message digest using a private key of the remote UE 120-2 to generate a digital signature. For example, the remote UE 120-2 may encrypt the message digest based at least in part on the private key of the remote UE 120-2 using a Rivest-Shamir-Adelman (RSA) encryption algorithm or another encryption algorithm. The digital signature may be an encrypted signature generated by encrypting the message digest. As indicated by reference numeral 658, the remote UE 120-2 may then append the digital signature to the message, thereby generating a digital signature confirmation.

[0102] Return to Fig. 6A , as shown by reference numeral 625, remote UE 120-2 may send a digitally signed confirmation of receipt of the data to relay UE 120-1. For example, in the event that remote UE 120-2 determines that feedback for the data relayed to remote UE 120-2 is ACK (e.g., in the event that remote UE 120-2 successfully decodes the relayed data), remote UE 120-2 may send a digitally signed confirmation to relay UE 120-1. Relay UE 120-1 may receive from remote UE 120-2 a digitally signed confirmation of receipt of the data by remote UE 120-2.

[0103] As shown by reference numeral 630, relay UE 120-1 may send a digitally signed confirmation that remote UE 120-2 received the data to network node 110. Network node 110 may receive a digitally signed confirmation that remote UE 120-2 received the data from remote UE 120-2. In some aspects, relay UE 120-1 may verify that the message is consistent with the data relayed to remote UE 120-2 before sending the digitally signed confirmation to network node 110. For example, relay UE 120-1 may verify that one or more parameters included in the message (e.g., one or more parameters associated with sending data from relay UE 120-1 to remote UE 120-2) are consistent with relaying data from relay UE 120-1 to remote UE 120-2. In this case, relay UE 120-1 may send the digitally signed confirmation to network node 110 based at least in part on verifying the one or more parameters included in the message. In this manner, relay UE 120 - 1 may verify the accuracy of one or more parameters providing relay proof before sending the digitally signed confirmation (including the message and the digital signature) to network node 110 .

[0104] In some aspects, relay UE 120-1 may report the digitally signed confirmation for the relayed data to network node 110 using real-time (or near real-time) reporting. For example, once relay UE 120-1 receives the digitally signed confirmation from remote UE 120-2, relay UE 120-1 may send the digitally signed confirmation to network node 110. In this case, if relay UE 120-1 relays multiple data packets to remote UE 120-2 and / or one or more other remote UEs, relay UE 120-1 may send a respective digitally signed confirmation for each relayed data packet separately to network node 110. In some aspects, relay UE 120-1 may report the digitally signed confirmation for the relayed data to network node 110 using non-real-time reporting. For example, relay UE 120-1 may aggregate all digital signature confirmations for relaying to one or more remote UEs (remote UE 120-2 and / or one or more other remote UEs) within a certain time period (e.g., within a day), and relay UE 120-1 may send the aggregated digital signature confirmations together in a communication (e.g., an uplink communication) to network node 110. In this case, relay UE 120-1 may send a digital signature confirmation for data received for relaying to remote UE 120-2 to network node 110 in a communication that includes the digital signature confirmation and one or more other digital signature confirmations associated with relaying the other data.

[0105] like Fig. 6AAs further shown, and by reference numeral 635, the network node 110 may verify that the data is relayed by the relay UE 120-1 to the remote UE 120-2. To verify the relaying of the data, the network node 110 may decrypt the message digest based at least in part on a public security key associated with the remote UE 120-2. In some aspects, the remote UE 120-2 may provide the public security key associated with the remote UE 120-2 to the network node 110. For example, when an initial registration or initial connection is formed between the remote UE 120-2 and the network node 110, the remote UE 120-2 may provide the public security key associated with the remote UE 120-2 to the network node 110. In some aspects, the remote UE 120-2 may directly send the public security key associated with the remote UE 120-2 to the network node 110. In some aspects, remote UE 120-2 may send a public security key to network node 110 via one or more relay UEs (e.g., relay UE 120-1 and / or one or more other relay UEs). Network node 110 may receive the public security key associated with remote UE 120-2. Network node 110 may perform decryption on the digital signature based at least in part on the public security key associated with remote UE 120-2 (e.g., using a decryption algorithm), thereby generating a message digest.

[0106] Then, to verify the relay of the data, the network node 110 may verify one or more parameters included in the message in the digital signature confirmation based at least in part on the decrypted message digest. For example, the network node 110 may apply a hash function (e.g., a SHA-1 hash function) to the message, and compare the result of applying the hash function to the message (e.g., another message digest generated by the network node 110) with the decrypted message digest to verify whether the message digest generated by the network node 110 by applying the hash function to the message is the same as the decrypted message digest. The one or more parameters provide proof that the data was relayed to the remote UE 120-2 by the relay UE 120-1. Because the message digest included in the digital signature confirmation is decrypted based at least in part on a private key associated with the remote UE 120-2, the relay UE 120-1 cannot change the message digest included in the digital signature confirmation. Thus, by verifying the message based at least in part on the decrypted message digest, network node 110 may verify that one or more parameters (eg, relay proof) included in the message sent by remote UE 120-2 were not altered before the digitally signed confirmation was sent to network node 110.

[0107] In some aspects, one or more network devices (e.g., network entities) other than (or in addition to) network node 110 may perform verification of relaying based at least in part on the digital signature confirmation. For example, in some aspects, network node 110 may send a digital signature confirmation to a core network device (such as a device associated with a CHF, PCF, DDNMF, or another core network) that remote UE 120-2 received the digital signature, and the core network device may perform verification based at least in part on the digital signature confirmation that data was relayed from relay UE 120-1 to remote UE 120-2.

[0108] like Fig. 6A And as further shown by reference numeral 640, the network node 110 may send an incentive (or an indication of an incentive) to the relay UE 120-1. The relay UE 120-1 may receive the incentive (or an indication of the incentive). In some aspects, the network node 110 may send the incentive (or an indication of the incentive) to the relay UE 120-1 based at least in part on verifying that the data is relayed to the remote UE 120-2 by the relay UE 120-1. For example, the network node 110 may send the incentive (or an indication of the incentive) to the relay UE 120-1 based at least in part on verifying one or more parameters in the message included in the message. In some aspects, the incentive for the relay UE 120-1 to relay the data to the remote UE 120-2 may include at least one of the following: a monetary incentive, a QoS incentive, or a digital token that can be exchanged for a currency or QoS reward, etc.

[0109] In some aspects, a device other than network node 110 may provide an incentive to relay UE 120-1 or a user of relay UE 120-1 based at least in part on the relaying of verification data. For example, a core network device associated with CHF may provide a monetary incentive to an account of a user of relay UE 120-1 for relaying data. In such examples, network node 110 may send an indication of the incentive to relay UE 120-1, and relay UE 120-1 may receive the indication of the incentive.

[0110] As indicated above, FIG. 6A to FIG. 6B are provided as examples. Other examples can be found in the FIG. 6A to FIG. 6B The content described is different.

[0111] Figure 7 is a diagram illustrating an example 700 associated with L2 relay enhancement for UE (or mobile station) relay verification according to the present disclosure. Figure 7As shown, example 700 includes communication between a core network 702, a network node 110, a relay UE 120-1, and a remote UE 120-2. In some aspects, the network node 110 may communicate with the relay UE 120-1 and / or the remote UE 120-2 via a wireless access link, which may include an uplink and a downlink. The relay UE 120-1 and the remote UE 120-2 may communicate via a side link. The core network (e.g., a 5G core network) may include an access and mobility function (AMF) and a CHF, as well as other core network functions. The AMF and CHF may be executed on one or more core network devices.

[0112] like Figure 7 As shown, and by reference numeral 705, the network node 110, the relay UE 120-1, and the remote UE 120-2 may establish an L2 relay relationship, wherein the relay UE 120-1 relays communications between the network node 110 and the remote UE 120-2. In some aspects, the network node 110 may be a RAN node associated with the relay UE 120-1 (e.g., a RAN node with which the relay UE 120-1 has established a connection), may include the RAN node, or may be included in the RAN node. In this case, the network node 110 may store a context of the remote UE 120-2 associated with the L2 relay relationship.

[0113] As shown by reference numeral 710, the network node 110 may send an indication of a remote UE ID associated with the remote UE 120-2 to the core network 702. For example, the network node 110 may send an indication of the remote UE ID for reporting the L2 relay relationship to the core network. In some aspects, the network node 110 may send an indication of the remote UE ID of the remote UE 120-2 to the AMF so that the remote UE ID of the remote UE 120-2 may be associated with the context of the remote UE 120-2. For example, the network node 110 may be triggered to report to the AMF the remote UE ID of the remote UE 120-2 to be associated with the context of the relay UE 120-1 in conjunction with the L2 relay relationship being established. In some aspects, the remote UE ID may be a universal public subscription ID (GPSI) because in some cases, the remote UE 120-2 and the relay UE 120-1 may not be served by the same public land mobile network (PLMN).

[0114] As shown by reference numeral 715, the AMF may send / report the remote UE ID of the remote UE 120-2 to the CHF. In some aspects, the AMF may associate the remote UE ID with the context of the relay UE 120-1 as the L2 remote UE ID. In some aspects, when the AMF receives the remote UE ID from the network node 110, the AMF may be triggered to report the L2 remote UE ID to the CHF for correlation creation.

[0115] As shown by reference numeral 720, the CHF may create a correlation between the relay UE 120-1 (e.g., the UE ID of the relay UE 120-1) and the remote UE ID (e.g., GPSI) of the remote UE 120-2 based at least in part on receiving the remote UE ID from the AMF. The CHF may store the correlation between the relay UE 120-1 and the remote UE ID of the remote UE 120-2. In some aspects, the CHF may correlate reports from the relay UE 120-1 and the remote UE 120-2 that the relay UE 120-1 relayed data to the remote UE 120-2 based at least in part on the correlation between the remote UE IDs of the relay UE 120-1 and the remote UE 120-2, and the CHF may determine and / or provide (e.g., to the relay UE 120-1) an incentive for relaying based at least in part on correlating the reports of relaying. In this manner, verification of relaying by relay UE 120-1 to remote UE 120-2 by the CHF may be based at least in part on reporting of the L2 relay relationship by network node 110 to the core network.

[0116] In some aspects, the above combined Figure 7 The L2 relay enhancements described above can be combined with Fig. 6A and Figure 6B The described operations may be combined with the above Fig. 6A and Figure 6B The operations described are performed independently.

[0117] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0118] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a mobile station in accordance with the present disclosure. Example process 800 is an example of a mobile station (eg, relay UE 120-1) performing operations associated with mobile station relay authentication.

[0119] like Figure 8As shown, in some aspects, process 800 may include receiving data from a first network entity to be relayed to a second network entity (block 810). For example, a mobile station (e.g., using Fig.11 The communication manager 1108 and / or receiving component 1102 depicted in FIG. 10A can receive data from a first network entity to be relayed to a second network entity, as described above.

[0120] like Figure 8 As further shown, in some aspects, process 800 may include sending data to a second network entity (block 820). Fig.11 The communication manager 1108 and / or the sending component 1104 depicted in can send the data to the second network entity, as described above.

[0121] like Figure 8 As further shown, in some aspects, process 800 may include receiving a digitally signed confirmation of receipt of the data from the second network entity (block 830). Fig.11 The communication manager 1108 and / or receiving component 1102 depicted in FIG. 10A may receive a digitally signed confirmation of receipt of the data from the second network entity, as described above.

[0122] like Figure 8 As further shown, in some aspects, process 800 may include sending a digitally signed confirmation to the first network entity (block 840). Fig.11 The communication manager 1108 and / or the sending component 1104 depicted in FIG. 1104 may send a digitally signed confirmation to the first network entity, as described above.

[0123] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0124] In a first aspect, the data includes information identifying the second network entity, and sending the data to the second network entity includes sending the data to the second network entity based at least in part on the information identifying the second network entity.

[0125] In a second aspect, either alone or in combination with the first aspect, the data comprises broadcast data sent by a first network entity, and process 800 comprises receiving a request for the broadcast data from a second network entity, wherein sending the data to the second network entity comprises sending the data to the second network entity based at least in part on receiving the request for the broadcast data.

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, a digitally signed confirmation comprises: a message comprising an indication of one or more parameters associated with sending data from a mobile station to a second network entity; and a digital signature associated with the second network entity.

[0127] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the one or more parameters include at least one of the following: the size of the data, the priority associated with the data, the QoS parameter associated with the data, the number of radio resources used to send the data from the mobile station to the second network entity, or the number of transmission attempts used to send the data from the mobile station to the second network entity.

[0128] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the digital signature comprises a message digest associated with the message, the message digest encrypted at least in part based on a private security key associated with the second network entity.

[0129] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the message digest is a result of applying a hash function to the message.

[0130] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, sending a digitally signed confirmation to the first network entity comprises sending a digitally signed confirmation to the first network entity based at least in part on verification of one or more parameters included in the message.

[0131] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 800 includes receiving an incentive based at least in part on sending a digitally signed confirmation to the first network entity.

[0132] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, sending a digitally signed confirmation to a first network entity comprises sending a communication to the first network entity comprising the digitally signed confirmation and one or more other digitally signed confirmations associated with relaying other data.

[0133] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first network entity is a network node.

[0134] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the second network entity is a remote mobile station.

[0135] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0136] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a mobile station in accordance with the present disclosure. Example process 900 is an example of a mobile station (eg, remote UE 120-2) performing operations associated with mobile station relay authentication.

[0137] like Fig. 9 As shown, in some aspects, process 900 may include receiving data from a relay mobile station that originated from a network entity and is relayed by the relay mobile station (block 910). For example, a mobile station (e.g., using Fig.12 The communication manager 1208 and / or receiving component 1202 depicted in FIG. 1204 may receive data from a relay mobile station that originated from a network entity and was relayed by the relay mobile station, as described above.

[0138] like Fig. 9 As further shown, in some aspects, process 900 may include sending a digitally signed confirmation of receipt of the data to the relay mobile station (block 920). Fig.12 The communication manager 1208 and / or the sending component 1204 depicted in FIG. 12 may send a digitally signed confirmation of receipt of the data to the relay mobile station, as described above.

[0139] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0140] In a first aspect, the data includes information identifying the mobile station.

[0141] In a second aspect, either alone or in combination with the first aspect, the data comprises broadcast data sent by a network entity, and process 900 comprises sending a request for the broadcast data to a relay mobile station, wherein receiving the data comprises receiving the data from the relay mobile station based at least in part on sending the request for the broadcast data.

[0142] In a third aspect, alone or in combination with one or more of the first and second aspects, a digitally signed confirmation comprises: a message comprising an indication of one or more parameters associated with sending data from a relay mobile station to a mobile station; and a digital signature associated with the mobile station.

[0143] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the one or more parameters include at least one of the following: the size of the data, the priority associated with the data, the QoS parameter associated with the data, the amount of radio resources used to send the data from the relay mobile station to the mobile station, or the number of transmission attempts used to send the data from the relay mobile station to the mobile station.

[0144] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the digital signature comprises a message digest associated with the message, the message digest encrypted based at least in part on a private security key associated with the mobile station.

[0145] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 900 comprises: applying a hash function to a message, thereby producing a message digest; encrypting the message digest based at least in part on a private security key associated with a mobile station, thereby producing a digital signature; and attaching the digital signature to the message, thereby producing a digital signature confirmation.

[0146] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 900 includes sending, by a mobile station to a network entity, a public security key associated with the mobile station.

[0147] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0148] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a network entity in accordance with the present disclosure. Example process 1000 is an example of a network entity (eg, network node 110) performing operations associated with mobile station relay authentication.

[0149] like Fig.10 As shown, in some aspects, process 1000 may include sending data to a relay mobile station to be relayed to a remote mobile station (block 1010). For example, a network entity (e.g., using Fig.13 The communication manager 1308 and / or the sending component 1304 depicted in FIG. 10A can send data to the relay mobile station to be relayed to the remote mobile station, as described above.

[0150] like Fig.10As further shown, in some aspects, process 1000 may include receiving from the relay mobile station a digitally signed confirmation of data received from the remote mobile station (block 1020). Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 10A can receive a digitally signed confirmation from the relay mobile station that the data was received by the remote mobile station, as described above.

[0151] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0152] In a first aspect, process 1000 includes sending, by a network entity, an incentive or an indication of an incentive to a relay mobile station based at least in part on receiving a digital signature confirmation.

[0153] In a second aspect, either alone or in combination with the first aspect, the data comprises information identifying the remote mobile station.

[0154] In a third aspect, alone or in combination with one or more of the first and second aspects, the data comprises broadcast data.

[0155] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the digital signature confirmation comprises: a message comprising an indication of one or more parameters associated with sending data from the relay mobile station to the remote mobile station; and a digital signature associated with the remote mobile station.

[0156] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the one or more parameters include at least one of the following: the size of the data, the priority associated with the data, the QoS parameter associated with the data, the amount of radio resources used to send data from the relay mobile station to the remote mobile station, or the number of transmission attempts used to send data from the relay mobile station to the remote mobile station.

[0157] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the digital signature comprises a message digest associated with the message, the message digest encrypted at least in part based on a private security key associated with the second network entity.

[0158] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the message digest is a result of applying a hash function to the message.

[0159] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 1000 includes decrypting a message digest based at least in part on a public security key associated with a relay mobile station, and verifying one or more parameters in the message based at least in part on the message digest.

[0160] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1000 includes sending, by a network entity, an incentive or an indication of an incentive to a relay mobile station based at least in part on one or more parameters in a verification message.

[0161] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0162] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a mobile station, or a mobile station may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 1108. Communication manager 1108 may perform operations similar to communication manager 140 described elsewhere herein. Communication manager 1108 may include determining component 1110, etc.

[0163] In some aspects, the apparatus 1100 may be configured to perform FIG. 6A to FIG. 6B and Figure 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more of the processes described herein such as Figure 8 In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0164] The receiving component 1102 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from the device 1106. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the mobile station.

[0165] The transmitting component 1104 may transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the mobile station. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0166] Receiving component 1102 may receive data from a first network entity to be relayed to a second network entity. Sending component 1104 may send the data to the second network entity. Receiving component 1102 may receive a digitally signed confirmation of receipt of the data from the second network entity. Sending component 1104 may send the digitally signed confirmation to the first network entity.

[0167] Determining component 1110 can determine that data received from a first network entity is to be relayed to a second network entity.

[0168] Receiving component 1102 can receive the incentive based at least in part on sending a digitally signed confirmation to the first network entity.

[0169] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set of component(s) may be described as being executable by Fig.11 Another collection of components shown performs one or more functions.

[0170] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a mobile station, or a mobile station may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may perform operations similar to communication manager 140 described elsewhere herein. Communication manager 1208 may include one or more of a hashing component 1210, an encryption component 1212, and / or an additional component 1214, among others.

[0171] In some aspects, the apparatus 1200 may be configured to perform FIG. 6A to FIG. 6B and Figure 7 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein such as Fig. 9 In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0172] The receiving component 1202 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the mobile station.

[0173] The transmitting component 1204 may transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the mobile station. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0174] Receiving component 1202 can receive data from a relay mobile station that originated from a network entity and is relayed by the relay mobile station. Sending component 1204 can send a digitally signed confirmation of receipt of the data to the relay mobile station.

[0175] The hash component 1210 can apply a hash function to the message, thereby producing a message digest.

[0176] Encryption component 1212 can encrypt the message digest based at least in part on a private security key associated with the mobile station, thereby generating a digital signature.

[0177] The append component 1214 can append a digital signature to the message, thereby generating a digital signature confirmation.

[0178] Transmitting component 1204 can transmit a public security key associated with the mobile station to a network entity.

[0179] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The illustrated set of component(s) may be described as being executable by Fig.12 Another collection of components shown performs one or more functions.

[0180] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network entity, or a network entity may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 1308. Communication manager 1308 may perform operations similar to communication manager 150 described elsewhere herein. Communication manager 1308 may include one or more of encryption component 1310 and / or verification component 1312, etc.

[0181] In some aspects, the apparatus 1300 may be configured to perform FIG. 6A to FIG. 6B and Figure 7 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more of the processes described herein such as Fig.10 In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0182] The receiving component 1302 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0183] The transmitting component 1304 may transmit communications (such as reference signals, control information, data communications, or combinations thereof) to the device 1306. In some aspects, one or more other components of the device 1300 may generate communications and may provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0184] The sending component 1304 can send data to the relay mobile station to be relayed to the remote mobile station. The receiving component 1302 can receive from the relay mobile station a digitally signed confirmation that the remote mobile station received the data.

[0185] Transmitting component 1304 can transmit the incentive or an indication of the incentive to the relay mobile station based at least in part on receiving the digitally signed confirmation.

[0186] Decryption component 1310 can decrypt the message digest based at least in part on a public security key associated with the relay mobile station.

[0187] Verification component 1312 can verify one or more parameters in the message based at least in part on the message digest.

[0188] Transmitting component 1304 can transmit the incentive or an indication of the incentive to the relay mobile station based at least in part on one or more parameters in the verification message.

[0189] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set of component(s) may be described as being executable by Fig.13 Another collection of components shown performs one or more functions.

[0190] The following provides an overview of some aspects of the disclosure:

[0191] Aspect 1: A method of wireless communication performed by a mobile station, the method comprising: receiving, by the mobile station, data to be relayed to a second network entity from a first network entity; sending, by the mobile station, the data to the second network entity; receiving, by the mobile station, a digital signature confirmation of receipt of the data from the second network entity; and sending, by the mobile station, the digital signature confirmation to the first network entity.

[0192] Aspect 2: A method according to aspect 1, wherein the data includes information identifying the second network entity, and wherein sending the data to the second network entity includes: sending the data to the second network entity based at least in part on the information identifying the second network entity.

[0193] Aspect 3: A method according to Aspect 1, wherein the data includes broadcast data sent by the first network entity, and the method further includes: receiving, by the mobile station, a request for the broadcast data from the second network entity, wherein sending the data to the second network entity includes sending the data to the second network entity based at least in part on receiving the request for the broadcast data.

[0194] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the digital signature confirmation includes: a message including an indication of one or more parameters associated with sending the data from the mobile station to the second network entity; and a digital signature associated with the second network entity.

[0195] Aspect 5: A method according to Aspect 4, wherein the one or more parameters include at least one of the following: the size of the data, the priority associated with the data, the quality of service (QoS) parameter associated with the data, the number of radio resources used to send the data from the mobile station to the second network entity, or the number of transmission attempts used to send the data from the mobile station to the second network entity.

[0196] Aspect 6: The method according to any one of aspects 4 to 5, wherein the digital signature comprises a message digest associated with the message, the message digest being encrypted based at least in part on a private security key associated with the second network entity.

[0197] Aspect 7: The method according to aspect 6, wherein the message digest is a result of applying a hash function to the message.

[0198] Aspect 8: A method according to any one of Aspects 4 to 7, wherein sending the digital signature confirmation to the first network entity includes: sending the digital signature confirmation to the first network entity based at least in part on verification of the one or more parameters included in the message.

[0199] Aspect 9: The method according to any one of aspects 1 to 8, the method further comprising: receiving an incentive by the mobile station based at least in part on sending the digital signature confirmation to the first network entity.

[0200] Aspect 10: A method according to any one of Aspects 1 to 9, wherein sending the digital signature confirmation to the first network entity includes: sending a communication including the digital signature confirmation and one or more other digital signature confirmations associated with relaying other data to the first network entity.

[0201] Aspect 11: The method according to any one of aspects 1 to 10, wherein the first network entity is a network node.

[0202] Aspect 12: The method according to any one of aspects 1 to 11, wherein the second network entity is a remote mobile station.

[0203] Aspect 13: A method of wireless communication performed by a mobile station, the method comprising: receiving, by the mobile station, data originating from a network entity and relayed by the relay mobile station; and sending, by the mobile station, a digitally signed confirmation of receipt of the data to the relay mobile station.

[0204] Aspect 14: The method according to aspect 13, wherein the data includes information identifying the mobile station.

[0205] Aspect 15: A method according to Aspect 13, wherein the data includes broadcast data sent by the network entity, and the method further includes: the mobile station sending a request for the broadcast data to the relay mobile station, wherein receiving the data includes receiving the data from the relay mobile station based at least in part on sending the request for the broadcast data.

[0206] Aspect 16: A method according to any one of Aspects 13 to 15, wherein the digital signature confirmation comprises: a message including an indication of one or more parameters associated with sending the data from the relay mobile station to the mobile station; and a digital signature associated with the mobile station.

[0207] Aspect 17: A method according to Aspect 16, wherein the one or more parameters include at least one of the following: the size of the data, the priority associated with the data, the quality of service (QoS) parameter associated with the data, the number of radio resources used to send the data from the relay mobile station to the mobile station, or the number of transmission attempts used to send the data from the relay mobile station to the mobile station.

[0208] Aspect 18: The method of any one of aspects 16 to 17, wherein the digital signature comprises a message digest associated with the message, the message digest encrypted based at least in part on a private security key associated with the mobile station.

[0209] Aspect 19: According to the method of Aspect 18, the method also includes: applying a hash function to the message to generate the message digest; encrypting the message digest based at least in part on a private security key associated with the mobile station to generate the digital signature; and attaching the digital signature to the message to generate the digital signature confirmation.

[0210] Aspect 20: The method according to any one of aspects 18 to 19, the method further comprising: sending, by the mobile station to the network entity, a public security key associated with the mobile station.

[0211] Aspect 21: A method of wireless communication performed by a network entity, the method comprising: sending, by the network entity, data to be relayed to a remote mobile station to a relay mobile station; and receiving, by the network entity, from the relay mobile station a digitally signed confirmation that the remote mobile station has received the data.

[0212] Aspect 22: The method according to aspect 21, the method further comprising: sending an incentive or an indication of an incentive to the relay mobile station by a network entity based at least in part on receiving the digital signature confirmation.

[0213] Aspect 23: A method according to any one of aspects 21 to 22, wherein the data includes information identifying the remote mobile station.

[0214] Aspect 24: A method according to any one of Aspects 21 to 22, wherein the data comprises broadcast data.

[0215] Aspect 25: A method according to any one of Aspects 21 to 24, wherein the digital signature confirmation includes: a message including an indication of one or more parameters associated with sending the data from the relay mobile station to the remote mobile station; and a digital signature associated with the remote mobile station.

[0216] Aspect 26: A method according to Aspect 25, wherein the one or more parameters include at least one of the following: the size of the data, the priority associated with the data, the quality of service (QoS) parameter associated with the data, the amount of radio resources used to send the data from the relay mobile station to the remote mobile station, or the number of transmission attempts used to send the data from the relay mobile station to the remote mobile station.

[0217] Aspect 27: The method according to any one of Aspects 25 to 26, wherein the digital signature comprises a message digest associated with the message, the message digest being encrypted based at least in part on a private security key associated with the second network entity.

[0218] Aspect 28: The method according to Aspect 27, wherein the message digest is the result of applying a hash function to the message.

[0219] Aspect 29: According to the method described in any one of Aspects 27 to 28, the method also includes: decrypting the message digest based at least in part on a public security key associated with the relay mobile station; and verifying the one or more parameters in the message based at least in part on the message digest.

[0220] Aspect 30: The method according to aspect 29, the method further comprising: sending an incentive or an indication of an incentive to the relay mobile station by the network entity based at least in part on verifying the one or more parameters in the message.

[0221] Aspect 31: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 12.

[0222] Aspect 32: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 12.

[0223] Aspect 33: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 1 to 12.

[0224] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 12.

[0225] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 12.

[0226] Aspect 36: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 13 to 20.

[0227] Aspect 37: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 13 to 20.

[0228] Aspect 38: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 13 to 20.

[0229] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 13 to 20.

[0230] Aspect 40: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 13 to 20.

[0231] Aspect 41: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 21 to 30.

[0232] Aspect 42: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 21 to 30.

[0233] Aspect 43: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 21 to 30.

[0234] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 21 to 30.

[0235] Aspect 45: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 21 to 30.

[0236] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0237] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0238] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0239] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0240] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A device for wireless communication, the device comprising: Memory, and one or more processors coupled to the memory, the one or more processors configured to, based at least in part on the information stored in the memory: receiving data from the first network entity to be relayed to the second network entity; sending the data to the second network entity; receiving, from the second network entity, a digitally signed confirmation of receipt of the data; as well as The digital signature confirmation is sent to the first network entity.

2. The apparatus of claim 1 , wherein the data comprises information identifying the second network entity, and wherein to send the data to the second network entity, the one or more processors are configured to: based at least in part on the information stored in the memory: The data is sent to the second network entity based at least in part on the information identifying the second network entity.

3. The apparatus of claim 1 , wherein the data comprises broadcast data sent by the first network entity, and the one or more processors are further configured to, based at least in part on the information stored in the memory: A request for the broadcast data is received from the second network entity, wherein to send the data to the second network entity, the one or more processors are configured to send the data to the second network entity based at least in part on receiving the request for the broadcast data.

4. The apparatus of claim 1, wherein the digital signature confirmation comprises: a message including an indication of one or more parameters associated with sending the data from the apparatus to the second network entity; as well as A digital signature associated with the second network entity.

5. The apparatus of claim 4 , wherein the one or more parameters comprise at least one of: a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used to send the data from the apparatus to the second network entity, or a number of transmission attempts used to send the data from the apparatus to the second network entity.

6. The apparatus of claim 4, wherein the digital signature comprises a message digest associated with the message, the message digest encrypted based at least in part on a private security key associated with the second network entity. The apparatus of claim 6 , wherein the message digest is a result of applying a hash function to the message.

8. The apparatus of claim 4, wherein to send the digitally signed confirmation to the first network entity, the one or more processors are configured to: based at least in part on information stored in the memory: The digitally signed confirmation is sent to the first network entity based at least in part on verification of the one or more parameters included in the message.

9. The apparatus of claim 1 , wherein the one or more processors are further configured to: An incentive is received based at least in part on sending the digitally signed confirmation to the first network entity.

10. The apparatus of claim 1, wherein to send the digitally signed confirmation to the first network entity, the one or more processors are configured to: based at least in part on information stored in the memory: A communication including the digitally signed confirmation and one or more other digitally signed confirmations associated with relaying other data is sent to the first network entity. The apparatus of claim 1 , wherein the first network entity is a network node.

12. The apparatus of claim 1, wherein the second network entity is a remote mobile station.

13. An apparatus for wireless communication, the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to, based at least in part on the information stored in the memory: receiving, from a relay mobile station, data originating from a network entity and relayed by the relay mobile station; as well as A digitally signed confirmation of receipt of the data is sent to the relay mobile station. The device of claim 13 , wherein the data comprises information identifying the device.

15. The apparatus of claim 13, wherein the data comprises broadcast data sent by the network entity, and the one or more processors are further configured to, based at least in part on the information stored in the memory: A request for the broadcast data is sent to the relay mobile station, wherein receiving the data includes receiving the data from the relay mobile station based at least in part on sending the request for the broadcast data.

16. The apparatus of claim 13, wherein the digital signature confirmation comprises: a message including an indication of one or more parameters associated with transmitting the data from the relay mobile station to the apparatus; as well as A digital signature associated with the device.

17. The apparatus of claim 16, wherein the one or more parameters include at least one of: a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used to send the data from the relay mobile station to the apparatus, or a number of transmission attempts used to send the data from the relay mobile station to the apparatus.

18. The apparatus of claim 16, wherein the digital signature comprises a message digest associated with the message, the message digest encrypted based at least in part on a private security key associated with the apparatus.

19. The apparatus of claim 18, wherein the one or more processors are further configured to: applying a hash function to the message to generate the message digest; encrypting the message digest based at least in part on a private security key associated with the device to thereby produce the digital signature; as well as The digital signature is appended to the message, thereby generating the digital signature confirmation.

20. The apparatus of claim 18, wherein the one or more processors are further configured to: A public security key associated with the device is sent to the network entity.

21. A method of wireless communication performed by a mobile station, the method comprising: receiving, by the mobile station, data from a first network entity to be relayed to a second network entity; Sending the data to the second network entity by the mobile station; receiving, by the mobile station from the second network entity, a digitally signed confirmation of receipt of the data; as well as The digitally signed confirmation is sent by the mobile station to the first network entity.

22. The method of claim 21, wherein the digital signature confirmation comprises: a message including an indication of one or more parameters associated with sending the data from the mobile station to the second network entity; as well as A digital signature associated with the second network entity.

23. The method of claim 22, wherein the one or more parameters include at least one of: a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used to send the data from the mobile station to the second network entity, or a number of transmission attempts used to send the data from the mobile station to the second network entity.

24. The method of claim 22, wherein the digital signature comprises a message digest associated with the message, the message digest being encrypted based at least in part on a private security key associated with the second network entity, and wherein the message digest is a result of applying a hash function to the message.

25. The method of claim 22, wherein sending the digitally signed confirmation to the first network entity comprises: The digitally signed confirmation is sent to the first network entity based at least in part on verification of the one or more parameters included in the message.

26. A method of wireless communication performed by a mobile station, the method comprising: receiving, by the mobile station from a relay mobile station, data originating from a network entity and relayed by the relay mobile station; as well as A digitally signed confirmation of receipt of the data is sent by the mobile station to the relay mobile station.

27. The method of claim 26, wherein the digital signature confirmation comprises: a message including an indication of one or more parameters associated with transmitting the data from the relay mobile station to the mobile station; as well as A digital signature is associated with the mobile station.

28. The method of claim 27, wherein the one or more parameters include at least one of the following: a size of the data, a priority associated with the data, a quality of service (QoS) parameter associated with the data, a number of radio resources used to send the data from the relay mobile station to the mobile station, or a number of transmission attempts used to send the data from the relay mobile station to the mobile station.

29. The method of claim 27, wherein the digital signature comprises a message digest associated with the message, the message digest encrypted based at least in part on a private security key associated with the mobile station.

30. The method according to claim 29, further comprising: applying a hash function to the message to generate the message digest; encrypting the message digest based at least in part on a private security key associated with the mobile station to thereby generate the digital signature; as well as The digital signature is appended to the message, thereby generating the digital signature confirmation.

Images