Entity and method for wireless communication

Abstract

The present invention relates to an entity for wireless communication for broadcasting data by: including the data in the form of one or more of a plurality of pilot modes into a signal comprising second data; the signal comprising the data in the form of the one or more pilot modes and the second data is transmitted. An entity for wireless communication is configured to: receive a signal; detecting one or more pilot modes of a plurality of pilot modes in the signal; data is extracted from the one or more pilot patterns. An entity for wireless communication is configured to: receive a signal; one or more pilot modes of a plurality of pilot modes available to include data in the signal are detected in the signal. Other entities for wireless communication and methods for wireless communication are provided. The signal includes first data in the form of one or more pilot modes.

Description

Technical Field

[0001] This application relates to entities and methods for wireless communication. Furthermore, the present invention relates to a signal comprising first data in the form of one or more pilot modes from a plurality of pilot modes and second data for transmission. Background Technology

[0002] Next-generation wireless broadband will be a core element in realizing smarter environments. A smart environment refers to a place where a large number of devices, networks, and services are increasingly utilizing digital and wireless internal communications to benefit users, communities, or businesses.

[0003] However, the realization of intelligent networks faces unprecedented challenges due to the ever-increasing number of connected devices and the need to consider various factors such as energy efficiency, scalability, mobility, predictability, monitoring, and control.

[0004] It is understood that 6G will support up to 10 million devices per square kilometer, which is 10 times greater than the theoretical maximum capacity of current 5G systems. Furthermore, the network should support an increasing number of heterogeneous devices, from vehicles and autonomous vehicles to wearable electronic devices and reduced-capacity devices. Summary of the Invention

[0005] In typical machine-to-machine communication use cases, such as vehicle-to-vehicle communication, devices can exchange information with other devices without direct human supervision, thus enabling an automated chain of acquisition, decision-making, and driving. For situations involving energy-saving devices, it is best to send data sporadically at low rates to conserve battery power. However, most intelligent network innovations are currently dominated by vertical industries, such as automotive and home entertainment, where devices are also considered to have substantial computing resources and near-unlimited battery capacity. Sharing data (e.g., sensor data) among multiple devices can lead to complex implementations that are not secure due to negative side effects such as side-connection establishment latency, link budget allocation, and interference from contributions.

[0006] The third-generation partnership project (3GPP) incorporated device-to-device (D2D) communication standards into LTE cellular systems. The primary incentive use case behind LTE D2D was initially dedicated to public safety authorities. In subsequent versions of the standard, D2D communication was extended to address V2X communication use cases (i.e., vehicle-to-everything communication), with a focus on public road safety scenarios. Starting with 5G NR, D2D technology (also known as sidelink (SL) communication) has been enhanced to meet a wider range of automotive applications. 3GPP defines the following use case groups: vehicle platooning, advanced driver assistance, extended sensors, and remote driving. In particular, the "extended sensors" group focuses on sharing sensor data from one device to another, with the goal of increasing a vehicle's awareness of its environment beyond the capacity of its own local sensors.

[0007] Sidelink (SL) radio resources can be allocated from licensed carriers dedicated to SL communications or from licensed carriers shared between sidelink (SL) and uplink (UL) communications. Critical scenarios or large market volumes will justify the significant cost of acquiring licensed carriers dedicated to sidelink communications, thus sidelink communications typically share the same resources as uplink communications.

[0008] There is a risk of conflict between SL (Single-Low) and UL (Ultra-Low) communications. Furthermore, there is a risk of conflict between devices using SL communication. The 5G NR SL standard defines two time-frequency resource allocation modes, referred to as Mode 1 and Mode 2. Mode 1 is limited by the condition that the user equipment (UE) must be within network coverage. In this case, the gNB (i.e., base station) allocates and manages SL radio resources. However, the UE needs to notify nearby UEs operating in Mode 2 of the resources available for its SL communication to minimize mutual interference. In Mode 2, the UE can autonomously select its SL resources from a resource pool, which can be predetermined or obtained through resource scanning. Devices in Mode 2 can use a random resource allocation method for selection. The SL device then needs to scan a set of resources within a time window that can be up to 1100 ms to avoid message collisions, thereby increasing latency.

[0009] In both modes, the UE undertakes some scheduling tasks through the relay gNB strategy or when it autonomously selects resources; this may significantly increase the implementation complexity of the UE.

[0010] Overall, the main challenges of SL communication remain scheduling and interference management. Assuming a half-duplex device, some strategies (such as the Listen-Before-Talk scheme) may reduce the probability of collisions, but may also affect uplink multiple access capabilities.

[0011] The 5G NR V2X specification is currently primarily designed for the automotive industry. 5G NR sidelinks (SL) have recently been integrated into IoT scenarios and will likely be merged with the RedCap specification (5G NR Light). From this perspective, IoT scenarios are generally less demanding than automotive scenarios; some use cases place greater emphasis on energy efficiency, complexity, latency, throughput, and device density. Therefore, network systems serving heterogeneous devices may be needed to support different types of networks (LTE-M, 5G NR Light, Narrowband IoT, 5G NR V2X) to achieve target-level interoperability. Switching between different network types can significantly increase system complexity.

[0012] In view of the foregoing, the present invention aims to provide an entity for wireless communication that supports device-to-device (D2D) communication, offering at least one of the advantages of reduced collision risk, reduced latency, elimination of scheduling and interference management, and reduced communication complexity. In cellular networks, D2D communication can be understood as direct communication of signals (e.g., one or more messages) between two or more mobile user equipment (UEs) without using another communication device, such as a base station (BS), for transmitting signals (e.g., one or more messages). That is, the communication does not traverse or pass through another device, such as a BS.

[0013] These and other objectives are achieved by the solutions of the invention described in the independent claims. Advantageous implementations are further defined in the dependent claims.

[0014] A first aspect of the present invention provides an entity for wireless communication. The entity is configured to broadcast data by: including the data in the form of one or more pilot patterns from a plurality of pilot patterns into a signal comprising second data; and transmitting the signal comprising the data in the form of the one or more pilot patterns and the second data.

[0015] In other words, the first aspect proposes an entity that supports broadcasting data by: including the data in the form of one or more pilot patterns from a plurality of pilot patterns into a signal comprising second data; and transmitting the signal comprising the data in the form of the one or more pilot patterns and the second data. That is, the signal comprises the one or more pilot patterns and the second data, wherein the one or more pilot patterns include the data (e.g., the data is encoded). It can be said that the data is stored in one or more pilot patterns of the signal.

[0016] Because the data is broadcast, other entities can receive the broadcast data, thus supporting D2D communication. For example, the entity and other entities can each be user equipment (UE). For data broadcasting, separate SL communication does not use sidelink (SL) resources. This reduces the risk of collisions, latency, and communication complexity. Furthermore, scheduling and interference management are unnecessary. That is, for entities in the first aspect, a transmitter is provided for broadcasting side information (i.e., data in the form of one or more pilot patterns) to any number of devices without establishing additional point-to-point or point-to-multipoint communication links. Since no point-to-point or point-to-multipoint communication links need to be established, there is no limit to the number of entities (i.e., devices) that can decode broadcast data encoded in one or more pilot patterns. By including data in the form of one or more pilot patterns in existing transmissions, i.e., in the signal that includes the second data, no air interference is generated for broadcast data.

[0017] An entity can be used to send second data to another entity used for wireless communication by sending a signal to that entity. The data included in the signal, which is in the form of one or more pilot patterns, can be side information destined for one or more other entities used for wireless communication. An entity can be used to transmit data as side information to one or more other entities by sending a signal to that entity. The other entity (the entity to which the second data is addressed) can be the entity described in the fifth aspect of the invention, as described below. One or more other entities (the entities to which the data is addressed) can be the entities described in the third aspect of the invention, as described below.

[0018] The pilot pattern mapping used can be notified to one or more other entities. For example, an entity can be configured for this purpose. One or more other entities can decode the side information by, for example, detecting one or more pilot patterns (the correct pilot pattern sequence) in a radio subframe. Therefore, in order to transmit data (i.e., side information), the entity according to the first aspect does not perform additional or superimposed signal transmissions. That is, the data (i.e., side information) is encoded in the form of one or more pilot patterns, which are comprised of signals that can be transmitted by one entity to another entity.

[0019] For example, one entity could be user equipment (UE), and the other entity could be a base station (BS). In this case, due to the use of multiple pilot patterns, in the uplink transmission from the entity that is a UE to the other entity that is a BS, the data included in the signal in the form of one or more pilot patterns can be transmitted as side information to one or more other UEs.

[0020] The terms “side link information” or “information for D2D communication” can be used as synonyms for the term “side information”. The term “side information” can be understood as the information to be sent via side link communication (i.e., D2D communication).

[0021] An entity can be user equipment (UE), a base station (BS), or any other entity used for wireless communication. It can be referred to as a transmitter, such as a transmitter UE or a transmitter BS. An entity can be a device used for wireless communication, such as radio frequency (RF) communication. An entity can be used to communicate according to one or more communication standards, such as transmitting signals. Optionally, such one or more communication standards can include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, an entity can be used to support one or more types of networks. One or more types of networks can include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc.

[0022] The term "information" can be used as a synonym for the term "data." Data can be referred to as opportunity data or application data. Data can be referred to as primary data. Data can be referred to as "side information." The data rate of the data can be lower than the data rate of the secondary data. Data can include or may be sensor data, i.e., data acquired from one or more sensors. For example, sensor data can include the position and / or orientation data of a device (e.g., an entity), accelerometer sensor data of a device (e.g., an entity), temperature sensor data at the location of a device (e.g., an entity), etc. This supports the realization of intelligent environmental scenarios that can utilize sensor data.

[0023] The second data is the signal payload. The second data may be referred to as "payload data." For example, the second data can be application data and / or feedback data (e.g., for channel estimation). One or more pilot patterns of the signal do not include the second data.

[0024] The signal can be an uplink signal, a downlink signal, or a sidelink signal. In the above cases, the second data can be referred to as uplink data, downlink data, or sidelink data, respectively.

[0025] The term "pilot sequence" can be used as a synonym for the term "pilot pattern." A pilot pattern can be a sequence of complex values. Multiple pilot patterns can be multiple radio frame communication pilot patterns. Multiple pilot patterns can be referred to as a "set of pilot patterns." Multiple pilot patterns are distinct from each other; that is, they are different from one another. In other words, multiple pilot patterns may exhibit structural differences. The multiple pilot patterns are distinct from each other such that (e.g., considering linear fading channel propagation between entities used for wireless communication) multiple pilot patterns support authentication (i.e., robust authentication) at the receiver side (i.e., at the entity to which data encoded in one or more pilot patterns is sent). Entities can be configured as part of a communication network. Multiple pilot patterns can be determined or selected such that one or more pilot patterns already assigned to other connected devices in the network are considered (not used for multiple pilot patterns) and used in the same communication resources (i.e., time and frequency). This supports avoiding or minimizing pilot pollution effects caused by reusing one or more assigned pilot patterns. Multiple pilot patterns can be selected or determined by entities within the network, such as those described in the sixth aspect of the invention or the seventh aspect of the invention, as follows. The multiple pilot patterns can be orthogonal or non-orthogonal. The multiple pilot patterns may not belong to a communication codebook (e.g., a predefined communication codebook).

[0026] In other words, the entity described in the first aspect can be used to encode data in one or more pilot patterns. The data can be a sequence of multiple bits (i.e., data bits), wherein the entity can be used to broadcast the sequence of multiple bits by including it in a signal in the form of one or more pilot patterns. The term "bit stream" can be used as a synonym for the term "bit sequence." The terms "in the form of" and "as" can be used as synonyms. The entity can be used to generate and transmit a signal comprising data and second data in the form of one or more pilot patterns. For example, to include n bits in the form of pilot patterns in a signal, i.e., to encode n bits in pilot patterns, the number of pilot patterns is equal to 2. n In other words, 2 n Each pilot mode can include 2 n The form of a pilot pattern is n bits in the form of one of the pilot patterns. The terms "include" and "insert" can be used as synonyms.

[0027] In one implementation of the first aspect, the entity is configured to select one or more pilot modes from the plurality of pilot modes according to an encoding scheme that maps different data to each pilot mode among the plurality of pilot modes.

[0028] In other words, an entity can be used to encode data in one or more pilot modes according to an encoding scheme. Data can be a sequence of multiple bits (i.e., data bits). Different sequences of one or more bits can be mapped to each pilot mode in the multiple pilot modes. In other words, each sequence of one or more bits can be mapped to a corresponding pilot mode in the multiple pilot modes. That is, multiple pilot modes support the encoding of multiple data, where the encoding scheme maps different data (i.e., different data among multiple data) to each pilot mode in the multiple pilot modes. For example, the encoding scheme can map each sequence of one or more bits to a corresponding pilot mode (i.e., different pilot modes) in the multiple pilot modes. In other words, the encoding scheme can map different sequences of one or more bits to different pilot modes in the multiple pilot modes. The term "associated with" can be used as a synonym for the term "mapped to".

[0029] Compared to communication pilot patterns, pilot pattern selection has more relaxed orthogonality constraints. Therefore, entities in the first aspect do not cause pilot pollution. Multiple pilot patterns, i.e., a wide range of pilot patterns, support more possibilities for mapping data (e.g., bitstreams).

[0030] In one implementation of the first aspect, the entity is configured to send a service request to a second entity for wireless communication and receive the encoding scheme from the second entity.

[0031] The second entity can be the entity described in the sixth aspect of the invention, as follows. The term "second entity" is used only to distinguish between an entity from which it may receive an encoding scheme and the entity described in the first aspect. Therefore, the terms "other entity" and "another entity" can be used instead of the term "second entity".

[0032] A service request can specify the nature of the data to be included in the signal in the form of one or more pilot patterns. The service request may include at least one of the following: the nature of the data (e.g., sensor type if the data is sensor data), the data format (e.g., information structure, bit resolution, etc.), the supported data rate, information about the application purpose (e.g., extended reality (XR) application or augmented reality (AR) application), and the application context. This information can enable a second entity to determine an appropriate encoding strategy, i.e., to determine an appropriate encoding scheme.

[0033] Optionally, the service request may include a suggestion of an encoding strategy. That is, the entity can be used to propose the encoding strategy in the service request to the second entity. The entity can receive information about multiple pilot modes from the second entity.

[0034] In one implementation of the first aspect, the entity is configured to: when transmitting the signal, transmit at least one of the one or more pilot patterns two or more times; and / or transmit a pilot pattern or a sequence of two or more pilot patterns specifying a context notification; and / or transmit the signal including a default pilot pattern and the second data, the default pilot pattern indicating that data was not transmitted in the form of one or more pilot patterns; and / or retransmit the signal including the default pilot pattern and the second data, the retransmitted default pilot pattern indicating that data transmission in the form of one or more pilot patterns has resumed; and / or transmit the signal including a second default pattern and the second data, the second default pilot pattern indicating that data transmission in the form of one or more pilot patterns has resumed. The phrase "transmit a pilot pattern or a sequence of two or more pilot patterns specifying a context notification" means "transmit a pilot pattern specifying a context notification, or a sequence of two or more pilot patterns specifying a context notification."

[0035] In other words, the entity can be used to perform at least one of the following operations: when sending the signal, sending at least one of the one or more pilot patterns two or more times; sending a sequence of one or two or more pilot patterns specifying context notification; sending the signal including a default pilot pattern and the second data, the default pilot pattern indicating that data was not sent in the form of one or more pilot patterns; retransmitting the signal including the default pilot pattern and the second data, the retransmitted default pilot pattern indicating that data transmission in the form of one or more pilot patterns has resumed; sending the signal including a second default pattern and the second data, the second default pilot pattern indicating that data transmission in the form of one or more pilot patterns has resumed. For example, the context notification can be a data synchronization event.

[0036] Instructing the resumption of data transmission in the form of one or more pilot modes (among multiple pilot modes) can mean that the signal, which includes the retransmission of the default pilot mode or the second default pilot mode, already includes data in the form of one or more pilot modes (among multiple pilot modes).

[0037] In other words, optionally, sending a default pilot mode can be used to turn on / off data transmission in one or more pilot modes among a plurality of pilot modes. For example, sending a signal including the default pilot mode and second data can indicate that no data is being transmitted in one or more pilot modes (i.e., turning off (stopping) data transmission in one or more pilot modes among a plurality of pilot modes). Retransmission (i.e., retransmission) a signal including the default pilot mode and second data can indicate resumption (i.e., turning on or starting) data transmission in one or more pilot modes.

[0038] Optionally, sending a default mode can be used to disable data transmission in one or more pilot modes from a plurality of pilot modes, and sending a second default mode can be used to enable data transmission in one or more pilot modes from a plurality of pilot modes. For example, sending a signal including a default pilot mode and second data can indicate that data transmission in one or more pilot modes is not in a plurality of pilot modes (i.e., disabling (stopping) data transmission in one or more pilot modes from a plurality of pilot modes). Sending a signal including a second default pilot mode and second data can indicate resumption (i.e., enabling or starting) of data transmission in one or more pilot modes.

[0039] In one implementation of the first aspect, the entity is configured to receive at least one of the following: information regarding the number of times at least one of the one or more pilot modes of the signal will be transmitted during the transmission of the signal; information regarding a pilot mode or a sequence of two or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0040] The entity can be used to receive one or more of the aforementioned optional information while receiving the encoding scheme from the second entity.

[0041] In order to realize the entity described in the first aspect of the present invention, some or all of the implementations and optional features of the first aspect may be combined with each other.

[0042] A second aspect of the invention provides an entity for wireless communication. The entity is configured to send a service request to a second entity for wireless communication and receive from the second entity an encoding scheme that maps different data to each of a plurality of pilot patterns.

[0043] An entity can be user equipment (UE), a base station (BS), or any other entity used for wireless communication. It can be referred to as a transmitter, such as a transmitter UE or a transmitter BS. An entity can be a device used for wireless communication, such as radio frequency (RF) communication. The entity can be used to communicate according to one or more communication standards, such as sending the service request. Optionally, such one or more communication standards can include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, the entity can be used to support one or more types of networks. One or more types of networks can include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc.

[0044] The second entity can be the entity described in the sixth aspect of the invention, as follows. The term "second entity" is used only to distinguish between the entity to which the service request can be sent and the entity described in the second aspect. Therefore, the terms "other entity" and "another entity" can be used instead of the term "second entity".

[0045] In one implementation of the second aspect, the entity is configured to receive at least one of the following: information regarding the number of times two or more of at least one pilot pattern among one or more pilot patterns for transmitting the signal during the transmission of the signal; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in the signal and retransmitted to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0046] The entity can be used to receive one or more of the aforementioned optional information while receiving the encoding scheme from the second entity.

[0047] The description of the entity described above according to the first aspect is correspondingly valid for the entity described according to the second aspect.

[0048] The entities, their implementations, and optional features of the second aspect achieve the same advantages as the entities, their corresponding implementations, and their corresponding optional features described in the first aspect.

[0049] To realize the entity described in the second aspect of the invention, some or all of the implementations and optional features of the second aspect described above may be combined with each other.

[0050] A third aspect of the invention provides an entity for wireless communication. The entity is configured to: receive a signal; detect one or more pilot patterns from a plurality of pilot patterns in the signal; and extract data from the one or more pilot patterns.

[0051] An entity can be user equipment (UE), a base station (BS), or any other entity used for wireless communication. It can be referred to as a listener, such as a listener UE or a listener BS. An entity can be a device used for wireless communication, such as radio frequency (RF) communication. An entity can be used to communicate according to one or more communication standards, such as receiving signals. Optionally, such one or more communication standards can include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, an entity can be used to support one or more types of networks. One or more types of networks can include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc.

[0052] The terms "identify" and "determine" can be used as synonyms for the term "detect". The entity can be used to receive the signal from another entity used for wireless communication. The other entity can be the entity described in the first aspect of the invention. The signal can be the signal described in the eighth aspect, as follows.

[0053] In one implementation of the third aspect, the entity is configured to extract the data from one or more pilot patterns according to a decoding scheme that maps each of the plurality of pilot patterns to different data.

[0054] Data can be a sequence of multiple bits (i.e., data bits). Each pilot pattern in the multiple pilot patterns can be mapped to a different sequence in one or more different sequences of bits. In other words, each pilot pattern in the multiple pilot patterns can be mapped to a corresponding sequence in one or more different sequences of bits. That is, the multiple pilot patterns support encoding multiple data, wherein the decoding scheme maps each pilot pattern in the multiple pilot patterns to different data in the multiple data, i.e., maps to different data in the multiple data. For example, the decoding scheme can map each pilot pattern in the multiple pilot patterns to a corresponding sequence (i.e., a different sequence) in one or more different sequences of bits. That is, the decoding scheme can map different pilot patterns in the multiple pilot patterns to different sequences of one or more bits.

[0055] In one implementation of the third aspect, the entity is used to receive the decoding scheme from a second entity used for wireless communication.

[0056] The second entity may be the entity described in the sixth aspect of the invention, or the entity described in the seventh aspect, as described below. The term "second entity" is used only to distinguish between an entity from which a decoding scheme can be received and an entity described in the third aspect. Therefore, the terms "other entity" and "another entity" may be used instead of the term "second entity".

[0057] In one implementation of the third aspect, the entity is configured to receive at least one of the following: information regarding the number of times two or more of at least one of the one or more pilot modes for transmitting the signal during the transmission of the signal; information regarding a pilot mode or a sequence of two or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0058] The entity can be used to receive one or more of the aforementioned optional information while receiving the decoding scheme from the second entity. The entity can also be used to receive one or more of the aforementioned optional information from the second entity.

[0059] The description of the entity described above according to the first aspect is correspondingly valid for the entity described according to the third aspect.

[0060] The entities, their implementations, and optional features of the third aspect have the same advantages as the entities, their corresponding implementations, and their corresponding optional features described in the first aspect.

[0061] To realize the entity described in the third aspect of the invention, some or all of the implementations and optional features of the third aspect described above may be combined with each other.

[0062] A fourth aspect of the invention provides an entity for wireless communication. The entity is used to receive a decoding scheme that maps each of a plurality of pilot modes to different data.

[0063] An entity can be user equipment (UE), a base station (BS), or any other entity used for wireless communication. It can be referred to as a listener, such as a listener UE or a listener BS. An entity can be a device used for wireless communication, such as radio frequency (RF) communication. An entity can be used to communicate according to one or more communication standards, such as a receive decoding scheme. Optionally, such one or more communication standards can include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, an entity can be used to support one or more types of networks. One or more types of networks can include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc.

[0064] Data can be a sequence of multiple bits (i.e., data bits). Each pilot pattern in the multiple pilot patterns can be mapped to a different sequence in one or more different sequences of bits. In other words, each pilot pattern in the multiple pilot patterns can be mapped to a corresponding sequence in one or more different sequences of bits. That is, the multiple pilot patterns support encoding multiple data, wherein the decoding scheme maps each pilot pattern in the multiple pilot patterns to different data in the multiple data, i.e., maps to different data in the multiple data. For example, the decoding scheme can map each pilot pattern in the multiple pilot patterns to a corresponding sequence (i.e., a different sequence) in one or more different sequences of bits. That is, the decoding scheme can map different pilot patterns in the multiple pilot patterns to different sequences of one or more bits.

[0065] The entity can be used to receive the decoding scheme from the second entity. The second entity can be the entity described in the sixth aspect of the invention, or the entity described in the seventh aspect of the invention, as described below. The term "second entity" is used only to distinguish between an entity from which a decoding scheme can be received and the entity described in the fourth aspect. Therefore, the terms "other entity" and "another entity" can be used instead of the term "second entity".

[0066] In one implementation of the fourth aspect, the entity is configured to receive at least one of the following: information regarding the number of times two or more of at least one pilot mode among one or more pilot modes for transmitting the signal during the transmission of the signal; information regarding a pilot mode or a sequence of two or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in the signal and retransmitted to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0067] The entity can be used to receive one or more of the aforementioned optional information while receiving the decoding scheme (e.g., from the second entity). The entity can be used to receive one or more of the aforementioned optional information from the second entity.

[0068] The descriptions of the entities described above according to the first aspect and the third aspect are respectively valid for the entities described according to the fourth aspect.

[0069] The entities, their implementations, and optional features of the fourth aspect have the same advantages as the entities, their corresponding implementations, and their corresponding optional features described in the first aspect.

[0070] To realize the entity described in the fourth aspect of the invention, some or all of the implementations and optional features of the fourth aspect may be combined with each other.

[0071] A fifth aspect of the invention provides an entity for wireless communication, wherein the entity is configured to receive a signal and detect one or more pilot modes among a plurality of pilot modes that can be used to include data in the signal.

[0072] An entity can be user equipment (UE), a base station (BS), or any other entity used for wireless communication. It can be referred to as a receiver, such as a receiver UE or a receiver BS. An entity can be a device used for wireless communication, such as radio frequency (RF) communication. An entity can be used to communicate according to one or more communication standards, such as receiving signals. Optionally, such one or more communication standards can include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, an entity can be used to support one or more types of networks. One or more types of networks can include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc. The signal can be the signal described in aspect eight, as follows.

[0073] In one implementation of the fifth aspect, the entity is used to extract data from the one or more pilot patterns.

[0074] In one implementation of the fifth aspect, the entity is used to extract second data from the signal.

[0075] One or more pilot modes of the signal do not include the second data. The second data is the signal payload. The second data can be referred to as "payload data".

[0076] In one implementation of the fifth aspect, the entity is configured to: verify the extracted second data; and if the verification of the extracted second data fails, determine an error in the detection of the one or more pilot patterns.

[0077] In one implementation of the fifth aspect, the entity is configured to: if the error is determined, re-execute the detection of the one or more pilot patterns in the signal, and extract the data from the re-detected one or more pilot patterns.

[0078] Therefore, the extraction of second data from the signal can be recovered from erroneous pilot pattern detection. Pilot pattern detection may include or may include pilot pattern prediction. Thus, the extraction of second data (e.g., payload data extraction) may not be affected by the broadcasting of data included in the signal in the form of one or more pilot patterns from a plurality of pilot sequences.

[0079] In one implementation of the fifth aspect, the entity is configured to extract the data from one or more pilot patterns according to a decoding scheme that maps each of the plurality of pilot patterns to different data.

[0080] Data can be a sequence of multiple bits (i.e., data bits). Each pilot pattern in a plurality of pilot patterns can be mapped to a different sequence in one or more bit sequences. In other words, each pilot pattern in a plurality of pilot patterns can be mapped to a corresponding sequence in one or more different bit sequences. That is, the plurality of pilot patterns support encoding multiple data, wherein the decoding scheme maps each pilot pattern in a plurality of pilot patterns to different data in the plurality of data, i.e., maps to different data in the plurality of data. For example, the decoding scheme can map each pilot pattern in a plurality of pilot patterns to a corresponding sequence (i.e., a different sequence) in one or more different bit sequences. That is, the decoding scheme can map different pilot patterns in a plurality of pilot patterns to different sequences of one or more bits.

[0081] In one implementation of the fifth aspect, the entity is used to receive the decoding scheme from a second entity used for wireless communication.

[0082] The second entity may be the entity described in the sixth aspect of the invention, or the entity described in the seventh aspect of the invention, as described below. The term "second entity" is used only to distinguish between an entity from which a decoding scheme can be received and the entity described in the fifth aspect. Therefore, the terms "other entity" and "another entity" may be used instead of the term "second entity".

[0083] In one implementation of the fifth aspect, the entity is configured to receive at least one of the following: information regarding the number of times two or more of at least one of the one or more pilot modes for transmitting the signal during the transmission of the signal; information regarding a pilot mode or a sequence of two or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0084] The entity can be used to receive one or more of the aforementioned optional information while receiving the decoding scheme from the second entity. The entity can also be used to receive one or more of the aforementioned optional information from the second entity.

[0085] The description of the entity described above according to the first aspect is correspondingly valid for the entity described according to the fifth aspect.

[0086] The entities, their implementations, and optional features of the fifth aspect have the same advantages as the entities, their corresponding implementations, and their corresponding optional features described in the first aspect.

[0087] In order to realize the entity according to the fourth aspect of the present invention, some or all of the implementations and optional features of the fifth aspect described above may be combined with each other.

[0088] A sixth aspect of the invention provides an entity for wireless communication. The entity is configured to: receive a service request from a second entity for wireless communication; and, in response to receiving the service request, send to the second entity an encoding scheme that maps different data to each of a plurality of pilot patterns.

[0089] The entity may be a controller unit for wireless communication. The controller unit may be associated with a BS or a UE. For example, it may be coupled to either the BS or the UE, or it may be part of either the BS or the UE. The entity may be a device for wireless communication, such as radio frequency (RF) communication. The entity may be used to communicate according to one or more communication standards, for example, receiving the service request and sending the encoding scheme. Optionally, such one or more communication standards may include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, the entity may be used to support one or more types of networks. One or more types of networks may include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc.

[0090] Data can be a sequence of multiple bits (i.e., data bits). Different sequences of one or more bits can be mapped to each of multiple pilot patterns. In other words, each sequence of one or more bits can be mapped to a corresponding pilot pattern in multiple pilot patterns. That is, multiple pilot patterns support encoding multiple data sets, where the encoding scheme maps different data sets (i.e., different data sets within the same set) to each pilot pattern in multiple pilot patterns. For example, the encoding scheme can map each sequence of one or more bits to a corresponding pilot pattern (i.e., a different pilot pattern) in multiple pilot patterns. In other words, the encoding scheme can map different sequences of one or more bits to different pilot patterns in multiple pilot patterns.

[0091] The entity can be used to determine or select the plurality of pilot patterns. The entity can be configured as part of a communication network. The entity can be used to determine or select the plurality of pilot patterns such that one or more pilot patterns already assigned to other connected devices in the network are considered (not for multiple pilot patterns), and these pilot patterns are used in the same communication resources (i.e., time and frequency). This helps to avoid or minimize pilot pollution effects caused by reusing one or more assigned pilot patterns. For example, the entity can be used to consider currently assigned pilot patterns within a network cell or near a second entity. The entity can determine or select multiple pilot patterns by considering currently assigned pilot patterns within a network cell or near a second entity.

[0092] A service request can specify the nature of the data to be included in the signal in the form of one or more pilot modes from a plurality of pilot modes. The service request may include at least one of the following: the nature of the data (e.g., sensor type if the data is sensor data), the data format (e.g., information structure, bit resolution, etc.), the supported data rate, information about the application purpose (e.g., extended reality (XR) application or augmented reality (AR) application), and the application context. The entity can use the above information to determine an encoding scheme. That is, this supports the entity in determining an appropriate encoding strategy, i.e., determining an appropriate encoding scheme.

[0093] Optionally, the service request may include suggestions for encoding strategies. Entities can be used to determine an encoding scheme based on the suggestions for encoding strategies.

[0094] The second entity may be the entity described in the first aspect of the invention or the entity described in the second aspect of the invention. The term "second entity" is used only to distinguish between an entity from which service requests may be received and the entity described in the sixth aspect. Therefore, the terms "other entity" and "another entity" may be used instead of the term "second entity".

[0095] In one implementation of the sixth aspect, the entity is configured to send to the second entity at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the second entity's transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0096] The entity can be used to send one or more of the above-mentioned optional information while sending the encoding scheme to the second entity.

[0097] In one implementation of the sixth aspect, the entity is configured to send a decoding scheme consistent with the encoding scheme to one or more entities associated with the second entity for wireless communication.

[0098] One or more entities may be entities as described in the third aspect of the invention or entities as described in the fourth aspect of the invention.

[0099] Optionally, the entity is used to send a decoding scheme consistent with the encoding scheme to another entity used for wireless communication. The other entity may be the entity described in the fifth aspect of the invention.

[0100] In one implementation of the sixth aspect, the one or more entities are associated with the second entity because at least one of the following is true: the one or more entities and the second entity are in a public cell; the one or more entities are in a specific area; the distance between the one or more entities and the second entity is less than a threshold; the one or more entities and the second entity are part of a public communication subnet. The phrase "the distance between the one or more entities and the second entity is less than a threshold" can mean that the one or more entities are located near the second entity.

[0101] In one implementation of the sixth aspect, the entity is configured to send to the one or more entities at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0102] The entity can be used to send one or more of the above-mentioned optional information while sending the decoding scheme to the one or more entities.

[0103] Optionally, the entity is configured to send to the other entity at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more pilot patterns.

[0104] The entity can be used to send one or more of the above-mentioned optional information while sending the decoding scheme to the other entity.

[0105] The description of the entity described above according to the first aspect is correspondingly valid for the entity described according to the sixth aspect.

[0106] The entities, implementations, and optional features of the sixth aspect have the same advantages as the entities, implementations, and optional features described in the first aspect.

[0107] In order to realize the entity according to the sixth aspect of the present invention, some or all of the implementations and optional features of the sixth aspect may be combined with each other.

[0108] A seventh aspect of the invention provides an entity for wireless communication. The entity is used to send a decoding scheme to one or more entities for wireless communication, mapping each of a plurality of pilot modes to different data.

[0109] The entity may be a controller unit for wireless communication. The controller unit may be associated with a BS or a UE. For example, it may be coupled to either the BS or the UE; or it may be part of either the BS or the UE. The entity may be a device for wireless communication, such as radio frequency (RF) communication. The entity may be used to communicate according to one or more communication standards, such as transmitting decoding schemes. Optionally, such one or more communication standards may include at least one of 4G LTE, LTE-M, 5G NR, 5G NR Light, narrowband IoT, 5G NR V2X, 6G, etc. In other words, the entity may be used to support one or more types of networks. One or more types of networks may include at least one of 4G LTE networks, LTE-M networks, 5G NR networks, 5G NR Light networks, narrowband IoT networks, 5G NR V2X networks, 6G networks, etc.

[0110] Data can be a sequence of multiple bits (i.e., data bits). Each pilot pattern in the multiple pilot patterns can be mapped to a different sequence in one or more different sequences of bits. In other words, each pilot pattern in the multiple pilot patterns can be mapped to a corresponding sequence in one or more different sequences of bits. That is, the multiple pilot patterns support encoding multiple data, wherein the decoding scheme maps each pilot pattern in the multiple pilot patterns to different data in the multiple data, i.e., maps to different data in the multiple data. For example, the decoding scheme can map each pilot pattern in the multiple pilot patterns to a corresponding sequence (i.e., a different sequence) in one or more different sequences of bits. That is, the decoding scheme can map different pilot patterns in the multiple pilot patterns to different sequences of one or more bits.

[0111] One or more entities may be entities as described in the third aspect of the invention or entities as described in the fourth aspect of the invention.

[0112] Optionally, the entity is configured to send the decoding scheme, which maps each of a plurality of pilot patterns to different data, to another entity for wireless communication. The other entity may be the entity described in the fifth aspect of the invention.

[0113] In one implementation of the seventh aspect, the entity is configured to send to the one or more entities at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0114] The entity can be used to send one or more of the above-mentioned optional information while sending the decoding scheme to the one or more entities.

[0115] Optionally, the entity is configured to send to the other entity at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more pilot patterns.

[0116] The entity can be used to send one or more of the above-mentioned optional information while sending the decoding scheme to the other entity.

[0117] The descriptions of the entities described above according to the first aspect and the sixth aspect are equally valid for the entities described according to the seventh aspect.

[0118] The entities, implementations, and optional features of the seventh aspect have the same advantages as the entities, implementations, and optional features described in the first aspect.

[0119] To realize the entity described in the seventh aspect of the present invention, some or all of the implementations and optional features of the seventh aspect may be combined with each other.

[0120] An eighth aspect of the invention provides a signal comprising first data in the form of one or more pilot modes of a plurality of pilot modes and second data for transmission.

[0121] The description of the entity described above according to the first aspect is valid for the signal described according to the eighth aspect.

[0122] The entities, implementations, and optional features of the eighth aspect have the same advantages as the entities, implementations, and optional features described in the first aspect.

[0123] A ninth aspect of the present invention provides a method for wireless communication. The method includes broadcasting data by: incorporating the data, in the form of one or more pilot patterns from a plurality of pilot patterns, into a signal comprising second data; and transmitting the signal comprising the data in the form of the one or more pilot patterns and the second data.

[0124] In one implementation of the ninth aspect, the method includes: selecting one or more pilot modes from the plurality of pilot modes according to an encoding scheme that maps different data to each pilot mode in the plurality of pilot modes.

[0125] In one implementation of the ninth aspect, the method includes: sending a service request to an entity for wireless communication; and receiving the encoding scheme from the entity.

[0126] In one implementation of the ninth aspect, the method includes: when transmitting the signal, transmitting at least one of the one or more pilot patterns two or more times; and / or transmitting a pilot pattern or a sequence of two or more pilot patterns specifying context notification; and / or transmitting the signal including a default pilot pattern and the second data, the default pilot pattern indicating that data was not transmitted in the form of one or more pilot patterns; and / or retransmitting the signal including the default pilot pattern and the second data, the retransmitted default pilot pattern indicating resumption of data transmission in the form of one or more pilot patterns; and / or transmitting the signal including a second default pilot pattern and the second data, the second default pilot pattern indicating resumption of data transmission in the form of one or more pilot patterns.

[0127] In one implementation of the ninth aspect, the method includes receiving at least one of the following: information regarding the number of times at least one of the one or more pilot modes of the signal will be transmitted during the transmission of the signal; information regarding a sequence of one or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0128] The description of the entity described above according to the first aspect is correspondingly valid for the method described according to the ninth aspect.

[0129] The method, implementation, and optional features of the ninth aspect have the same advantages as the entity, its corresponding implementation, and corresponding optional features described in the first aspect.

[0130] To implement the method according to the ninth aspect of the present invention, some or all of the implementations and optional features of the ninth aspect may be combined with each other.

[0131] A tenth aspect of the present invention provides a method for wireless communication, wherein the method includes: sending a service request to an entity for wireless communication; and receiving from the entity an encoding scheme that maps different data to each of a plurality of pilot patterns.

[0132] In one implementation of the tenth aspect, the method includes receiving at least one of the following: information regarding the number of times two or more of at least one pilot pattern among one or more pilot patterns for transmitting the signal during transmission of the signal; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0133] The description of the entity described above according to the second aspect is correspondingly valid for the method described according to the tenth aspect.

[0134] The method, implementation, and optional features of the tenth aspect have the same advantages as the entity, its corresponding implementation, and corresponding optional features described in the first aspect.

[0135] To implement the method according to the tenth aspect of the present invention, some or all of the above-described implementations and optional features of the tenth aspect may be combined with each other.

[0136] An eleventh aspect of the present invention provides a method for wireless communication. The method includes: receiving a signal; detecting one or more pilot patterns from a plurality of pilot patterns in the signal; and extracting data from the one or more pilot patterns.

[0137] In one implementation of the eleventh aspect, the method includes: extracting the data from one or more pilot patterns according to a decoding scheme that maps each of the plurality of pilot patterns to different data.

[0138] In one implementation of the eleventh aspect, the method includes: receiving the decoding scheme from an entity used for wireless communication.

[0139] In one implementation of the eleventh aspect, the method includes receiving at least one of the following: information regarding the number of times two or more of at least one of the one or more pilot modes of the signal will be transmitted during the transmission of the signal; information regarding a pilot mode or a sequence of two or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0140] The description of the entity described above according to the third aspect is correspondingly valid for the method described according to the eleventh aspect.

[0141] The method and its implementation and optional features of the eleventh aspect have the same advantages as the entity and its corresponding implementation and optional features described in the first aspect.

[0142] In order to implement the method according to the eleventh aspect of the present invention, some or all of the implementations and optional features of the eleventh aspect may be combined with each other.

[0143] A twelfth aspect of the present invention provides a method for wireless communication. The method includes receiving a decoding scheme that maps each of a plurality of pilot modes to different data.

[0144] In one implementation of the twelfth aspect, the method includes receiving at least one of the following: information regarding the number of times two or more of at least one pilot pattern among one or more pilot patterns for transmitting the signal during transmission of the signal; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0145] The description of the entity described above according to the fourth aspect is correspondingly valid for the method described according to the twelfth aspect.

[0146] The method and its implementation, along with optional features, of the twelfth aspect have the same advantages as the entity and its corresponding implementation and optional features described in the first aspect.

[0147] To implement the method according to the twelfth aspect of the present invention, some or all of the implementations and optional features of the twelfth aspect may be combined with each other.

[0148] A thirteenth aspect of the present invention provides a method for wireless communication. The method includes: receiving a signal; and detecting in the signal one or more pilot modes from a plurality of pilot modes that can be used to include data in the signal.

[0149] In one implementation of the thirteenth aspect, the method includes: extracting data from the one or more pilot patterns.

[0150] In one implementation of the thirteenth aspect, the method includes: extracting second data from the signal.

[0151] In one implementation of the thirteenth aspect, the method includes: verifying the extracted second data; if the verification of the extracted second data fails, determining an error in the detection of the one or more pilot patterns.

[0152] In one implementation of the thirteenth aspect, the method includes: if the error is determined, re-performing the detection of the one or more pilot patterns in the signal, and extracting the data from the re-detected one or more pilot patterns.

[0153] In one implementation of the thirteenth aspect, the method includes: extracting the data from one or more pilot patterns according to a decoding scheme that maps each of the plurality of pilot patterns to different data.

[0154] In one implementation of the thirteenth aspect, the method includes: receiving the decoding scheme from an entity used for wireless communication.

[0155] In one implementation of the thirteenth aspect, the method includes receiving at least one of the following: information regarding the number of times two or more of at least one of the one or more pilot modes for transmitting the signal during transmission of the signal; information regarding a sequence of one or two or more pilot modes specifying context notification; information regarding a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot modes; information regarding the default pilot mode included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes; and information regarding a second default pilot mode included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot modes.

[0156] The description of the entity described above according to the fifth aspect is correspondingly valid for the method described according to the thirteenth aspect.

[0157] The method, implementation, and optional features of the thirteenth aspect achieve the same advantages as the entity, its corresponding implementation, and its corresponding optional features described in the first aspect.

[0158] To implement the method according to the thirteenth aspect of the present invention, some or all of the implementations and optional features of the thirteenth aspect may be combined with each other.

[0159] A fourteenth aspect of the present invention provides a method for wireless communication. The method includes: receiving a service request from an entity for wireless communication; and, in response to receiving the service request, sending to the entity an encoding scheme that maps different data to each of a plurality of pilot patterns.

[0160] In one implementation of the fourteenth aspect, the method includes sending to the entity at least one of the following: information regarding the number of times two or more of at least one of one or more pilot patterns for transmitting a signal during the entity's transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0161] In one implementation of the fourteenth aspect, the method includes: sending a decoding scheme consistent with the encoding scheme to one or more entities associated with the entity for wireless communication.

[0162] In one implementation of the fourteenth aspect, the one or more entities are associated with the entity because at least one of the following is true: the one or more entities and the entity are in a public cell; the one or more entities are in a specific area; the distance between the one or more entities and the entity is less than a threshold; the one or more entities and the entity are part of a public communication subnet.

[0163] In one implementation of the fourteenth aspect, the method includes sending to the one or more entities at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0164] The description of the entity described above according to the sixth aspect is correspondingly valid for the method described according to the fourteenth aspect.

[0165] The method, implementation, and optional features of the fourteenth aspect achieve the same advantages as the entity, its corresponding implementation, and its corresponding optional features described in the first aspect.

[0166] To implement the method according to the fourteenth aspect of the present invention, some or all of the implementations and optional features of the fourteenth aspect may be combined with each other.

[0167] A fifteenth aspect of the present invention provides a method for wireless communication. The method includes: transmitting to one or more entities for wireless communication a decoding scheme that maps each of a plurality of pilot modes to different data.

[0168] In one implementation of the fifteenth aspect, the method includes sending to the one or more entities at least one of the following: information regarding the number of times at least one of one or more pilot patterns of a signal to be transmitted during the transmission of the signal, the signal including data in the form of the one or more pilot patterns; information regarding a pilot pattern or a sequence of two or more pilot patterns specifying context notification; information regarding a default pilot pattern included in the signal to indicate that the signal does not include data in the form of one or more of the plurality of pilot patterns; information regarding the default pilot pattern included in and retransmitted in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns; and information regarding a second default pilot pattern included in the signal to indicate resumption of data transmission in the form of one or more of the plurality of pilot patterns.

[0169] The description of the entity described above according to the seventh aspect is correspondingly valid for the method described according to the fifteenth aspect.

[0170] The method, implementation, and optional features of the fifteenth aspect achieve the same advantages as the entity, its corresponding implementation, and corresponding optional features described in the first aspect.

[0171] To implement the method according to the fifteenth aspect of the present invention, some or all of the implementations and optional features of the fifteenth aspect may be combined with each other.

[0172] The encoding blocks used to encode data in the form of one or more pilot patterns and the decoding blocks used to decode data from the pilot patterns can be low-complexity blocks; therefore, the entity described above can be a medium-performance device. This is advantageous in terms of implementation cost. According to the invention, by broadcasting data using one or more pilot patterns from a plurality of pilot patterns, network operators can provide new services to transmitters to broadcast data in the vicinity for the convenience of users, while the network operator also gains access to the broadcast data.

[0173] It should be noted that all devices, elements, units, and modules described in this application can be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in this application and the functions to be performed by the various entities are intended to indicate that each entity is suitable for or used to perform its respective steps and functions. Even if, in the description of the following specific embodiments, a particular function or step to be performed by an external entity is not reflected in the description of the specific detailed elements of the entity performing that particular step or function, those skilled in the art should understand that these methods and functions can be implemented in the corresponding software or hardware elements or any combination thereof. Attached Figure Description

[0174] The above aspects and implementation methods will be explained in the following detailed description of specific embodiments, in conjunction with the accompanying drawings.

[0175] Figure 1 Examples of entities for wireless communication provided by the present invention and examples of signals provided by the present invention are shown.

[0176] Figure 2 Examples of entities for wireless communication provided by the present invention and examples of encoding schemes provided by the present invention are shown.

[0177] Figure 3 Examples of entities for wireless communication provided by the present invention and examples of signals provided by the present invention are shown.

[0178] Figure 4 Examples of entities for wireless communication provided by the present invention and examples of decoding schemes provided by the present invention are shown.

[0179] Figure 5 Examples of entities for wireless communication provided by the present invention and examples of signals provided by the present invention are shown.

[0180] Figure 6 Examples of entities for wireless communication provided by the present invention and examples of encoding schemes provided by the present invention are shown.

[0181] Figure 7 Examples of entities for wireless communication provided by the present invention and examples of decoding schemes provided by the present invention are shown.

[0182] Figure 8 An example of the signal provided by the present invention is shown.

[0183] Figure 9 An example of an implementation of the entity for wireless communication provided by the present invention is shown.

[0184] Figure 10An example of the functionality of an entity for wireless communication provided by the present invention is shown.

[0185] Figure 11 An example of an implementation of the entity for wireless communication provided by the present invention is shown.

[0186] Figure 12 An example of an implementation of the entity for wireless communication provided by the present invention is shown.

[0187] Figure 13 An example of the interaction of entities for wireless communication provided by the present invention is shown.

[0188] Figure 14 An example of the interaction of entities for wireless communication provided by the present invention is shown.

[0189] Figures 15 to 21 Examples of the methods for wireless communication provided by the present invention are shown respectively. Detailed Implementation

[0190] Figure 1 Examples of entities for wireless communication provided by the present invention and examples of signals provided by the present invention are shown. Figure 1 Entity 1 is an example of an entity according to the first aspect of the invention. Correspondingly, according to the description of the entity according to the first aspect, [the following is a list of entities]. Figure 1 Entity 1 is valid.

[0191] Figure 1 Entity 1 is an entity used for wireless communication. Entity 1 is used to broadcast data D1 by: including data D1 in the form of one or more pilot patterns 101 of a plurality of pilot patterns into a signal 100 including second data D2; and transmitting the signal 100 including data D1 in the form of one or more pilot patterns 101 and second data D2. The second data D2 may be the payload 102 of the signal 100.

[0192] Entity 1 can send data to another entity used for wireless communication (e.g., Figure 5 Entity 2) sends signal 100 to another entity ( Figure 1 (Not shown in the image) provides second data D2. That is, second data D2 is sent to another entity. Regarding signal 100, Figure 1 Entity 1 can be referred to as a "transmitter". This enables one or more other entities positioned near Entity 1, another entity, and / or the transmission path of signal 100 to listen for (i.e., receive) signal 100 destined for another entity. These other one or more entities can be used to extract data D1 from one or more pilot patterns 101 of signal 100. Examples of these one or more entities could be... Figure 3Entity 3. The terms “in a vicinity of” and “at proximity of” can be used as synonyms.

[0193] about Figure 1 For further details of entity 1, refer to the description of the entity according to the first aspect, and Figure 9 , Figure 10 , Figure 13 and Figure 14 .

[0194] Figure 2 Examples of entities for wireless communication provided by the present invention and examples of encoding schemes provided by the present invention are shown. Figure 2 Entity 1 is an example of an entity according to the second aspect of the invention. Correspondingly, according to the description of the entity according to the second aspect, [the following is applied to...]. Figure 2 Entity 1 is valid.

[0195] Figure 2 Entity 1 is an entity used for wireless communication. Entity 1 is used to send a service request 200 to a second entity 4 used for wireless communication and to receive from the second entity 4 a coding scheme 300a that maps different data to each of a plurality of pilot patterns. For example, data (multiple data lines) d1, d2, d3, ..., d n–1 and d n Mapped to pilot modes p1, p2, p3, ... p respectively n–1 and p n . Figure 2 The data (i.e., multiple data points) and the number of pilot modes shown are merely examples and do not limit the invention.

[0196] For example, the second entity 4 could be Figure 6 The entity. Figure 2 The function of entity 1 can be Figure 1 Optional features of entity 1.

[0197] about Figure 2 For further details of entity 1, refer to the description of the entity as described in the second aspect.

[0198] Figure 3 Examples of entities for wireless communication provided by the present invention and examples of signals provided by the present invention are shown. Figure 3 Entity 3 is an example of an entity according to the third aspect of the invention. Correspondingly, according to the description of the entity according to the third aspect, [the following is a list of entities]. Figure 3 Entity 3 is valid.

[0199] Figure 3Entity 3 is an entity used for wireless communication. Entity 3 is used for: receiving signal 100; detecting one or more pilot patterns 101 among a plurality of pilot patterns in signal 100; and extracting data D1 from the one or more pilot patterns 101. Figure 3 As shown, signal 100 may include second data D2. The second data D2 may be the payload 102 of signal 100.

[0200] When another entity used for wireless communication (e.g.) Figure 1 When entity 1) sends signal 100 to another entity for wireless communication, entity 3 can receive signal 100 in order to provide the second data D2 of signal 100 to the other entity, i.e., because the second data D2 and therefore signal 100 are destined for the other entity. The other entity could be... Figure 5 Entity 2. Therefore, with respect to signal 100, entity 3 can be referred to as a “listener” or “listener device” because it is used to listen to (i.e., receive) signal 100 sent to another entity and extract data D1 included in signal 100 in the form of one or more pilot patterns 101.

[0201] about Figure 3 For further details of entity 3, refer to the description of the entity according to the third aspect, and Figures 12 to 14 .

[0202] Figure 4 Examples of entities for wireless communication provided by the present invention and examples of decoding schemes provided by the present invention are shown. Figure 4 Entity 3 is an example of an entity according to the fourth aspect of the invention. Correspondingly, according to the description of the entity according to the fourth aspect, [the following is applied to...]. Figure 4 Entity 3 is valid.

[0203] Figure 4 Entity 3 is an entity used for wireless communication. Entity 3 is used to receive a decoding scheme 300b that maps each of a plurality of pilot patterns to different data. For example, pilot patterns p1, p2, p3, ..., p n–1 and p n Mapped to data (multiple data entries) d1, d2, d3, ..., d n–1 and d n . Figure 4 The pilot patterns and the number of data (i.e., multiple data points) shown are merely examples and do not limit the invention.

[0204] like Figure 4 As shown, entity 3 can receive decoding scheme 300b from the second entity 4. For example, the second entity 4 could be... Figure 7 The entity. Figure 4 The function of entity 3 can be Figure 3 Optional features of entity 3.

[0205] about Figure 4 For further details of entity 3, refer to the description of the entity as described in the fourth aspect.

[0206] Figure 5 Examples of entities for wireless communication provided by the present invention and examples of signals provided by the present invention are shown. Figure 5 Entity 2 is an example of an entity according to the fifth aspect of the invention. Correspondingly, according to the description of the entity according to the fifth aspect, [the following is a list of entities]. Figure 5 Entity 2 is valid.

[0207] Figure 5 Entity 2 is an entity for wireless communication, wherein entity 2 is used to receive signal 100 and detect one or more pilot modes 101 in signal 100 that can be used to include data D1 in signal 100. Figure 5 As shown, signal 100 may include second data D2. The second data D2 may be the payload 102 of signal 100.

[0208] Entity 2 can be obtained from another entity used for wireless communication (e.g. Figure 1 Entity 1) receives signal 100, wherein signal 100 and therefore its second data D2 can be sent to entity 2. That is, another entity may have already sent signal 100 to entity 2 to provide the second data D2 of signal 100 to entity 2 while simultaneously broadcasting data D1 by including data D1 in the form of one or more pilot patterns 101 in signal 100. Regarding signal 100, Figure 5 Entity 2 can be called the "receiver".

[0209] about Figure 5 For further details of entity 2, refer to the description of the entity as described in the fifth aspect, and Figure 11 , Figure 13 and Figure 14 .

[0210] Figure 6 Examples of entities for wireless communication provided by the present invention and examples of encoding schemes provided by the present invention are shown. Figure 6 Entity 4 is an example of an entity according to the sixth aspect of the invention. Correspondingly, according to the description of the entity according to the sixth aspect, [the following is applied to...]. Figure 6 Entity 4 is valid.

[0211] Figure 6Entity 4 is an entity used for wireless communication. Entity 4 is used to: receive a service request 200 from a second entity 1 used for wireless communication; and in response to receiving the service request 200, send to the second entity 1 an encoding scheme 300a that maps different data to each of a plurality of pilot patterns. For example, data (multiple data items) d1, d2, d3, ..., d n–1 and d n Mapped to pilot modes p1, p2, p3, ... p respectively n–1 and p n . Figure 6 The data (i.e., multiple data points) and the number of pilot modes shown are merely examples and do not limit the invention.

[0212] For example, the second entity 1 could be Figure 1 or Figure 2 Entity 1.

[0213] about Figure 6 For further details of entity 4, refer to the description of the entity as described in the sixth aspect, and Figure 13 and Figure 14 .

[0214] Figure 7 Examples of entities for wireless communication provided by the present invention and examples of decoding schemes provided by the present invention are shown. Figure 7 Entity 4 is an example of an entity according to the seventh aspect of the invention. Correspondingly, according to the description of the entity according to the seventh aspect, [the following is a list of entities]. Figure 7 Entity 4 is valid.

[0215] Figure 7 Entity 4 is an entity used for wireless communication. Entity 4 is used to send a decoding scheme 300b to one or more entities 3 used for wireless communication, mapping each of a plurality of pilot patterns to different data. For example, pilot patterns p1, p2, p3, ..., p n–1 and p n Mapped to data (multiple data entries) d1, d2, d3, ..., d n–1 and d n . Figure 7 The pilot patterns and the number of data (i.e., multiple data points) shown are merely examples and do not limit the invention.

[0216] For example, one or more entities 3 could be Figure 3 or Figure 4 Entity 3. Figure 7 The function of entity 4 can be Figure 6 Optional features of entity 4.

[0217] about Figure 7For further details of entity 4, refer to the description of the entity as described in aspect seven, and Figure 13 and Figure 14 .

[0218] for Figures 1 to 7 Each entity in the entity (i.e., for) Figure 1 Entity 1 Figure 2 Entity 1 Figure 3 Entity 3 Figure 4 Entity 3 Figure 5 Entity 2 Figure 6 Entity 4 and Figure 7 Entity 4), the following may be correct: An entity may include a processor or processing circuitry (not shown) for performing, conducting, or initiating various operations of the entity described herein. The processing circuitry may include hardware and / or may be controlled by software. Hardware may include analog or digital circuitry, or both. Digital circuitry may include components such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), or multi-purpose processors. An entity may also include memory circuitry storing one or more instructions that can be executed by the processor or processing circuitry (specifically, under software control). For example, the memory circuitry may include a non-transitory storage medium storing executable software code that, when executed by the processor or processing circuitry, performs various operations of the entity. In one embodiment, the processing circuitry system includes one or more processors and non-transitory memory connected to one or more processors. The non-transitory memory may carry executable program code that, when executed by one or more processors, causes the entity to perform, implement, or initiate the operations or methods described herein.

[0219] Figure 8 An example of the signal provided by the present invention is shown. Figure 8 Signal 100 is an example of a signal according to the eighth aspect of the present invention. Correspondingly, according to the description of the entity described in the eighth aspect, [the following is provided]. Figure 8 The signal is 100% valid.

[0220] Figure 8 The signal 100 is a signal comprising first data D1 in the form of one or more pilot modes 101 among a plurality of pilot modes and second data D2 for transmission. The second data D2 may be the payload 102 of the signal 100.

[0221] Figure 8 Signal 100 can be Figure 1 , Figure 3 and Figure 5 The signal shown is 100. Regarding... Figure 8 For further details of signal 100, refer to the description of the signal according to aspect eight, and... Figures 9 to 14 .

[0222] Figure 9 An example of an implementation of the entity for wireless communication provided by the present invention is shown. Figure 9 Entity 1 is Figure 1 An example of how entity 1 is implemented. Figure 1 The description corresponds to Figure 9 Entity 1 is valid.

[0223] like Figure 9 As shown, entity 1 may include a source 11 for broadcasting data D1 to achieve D2D communication. Source 11 may acquire and / or generate data D1 from an external source. Optionally, source 11 may be at least one sensor. Source 11 may be referred to as a "side information source". Entity 1 may include a second source 13 for second data D2, which will be transmitted as the payload of a signal. Second source 13 may acquire and / or generate second data D2 from an external source. To transmit data D1 in the form of one or more pilot modes from a plurality of pilot modes, entity 1 may include a pilot mode selection unit 12. Pilot mode selection unit 12 is used to select one or more pilot modes from a plurality of pilot modes for data D1 provided by source 11 according to an encoding scheme that maps different data to each of the plurality of pilot modes. Entity 1 may also receive data from another entity used for wireless communication (e.g., Figure 6 Entity 4) receives the encoding scheme. Another entity for wireless communication may be a controller unit for wireless communication. The controller unit may be associated with a BS or a UE. Therefore, the pilot mode selection unit 12 can encode data D1 in one or more pilot modes according to the encoding scheme by selecting one or more pilot modes according to the encoding scheme.

[0224] Entity 1 may include a resource grid mapping unit 14 and a precoding unit 15 for generating a signal to be transmitted by one or more antennas 16 of entity 1, wherein the signal includes data D1 in the form of one or more pilot patterns and second data D2 as the payload of the signal provided by the second source 12. Figure 9The number of antennas 16 shown is merely illustrative and may vary. In the case of multiple antennas 16, these antennas may be part of an antenna array. The pilot mode selection unit 12, the resource grid mapping unit 14, and the precoding unit 15 may be part of, or form part of, the wireless communication transmission chain (e.g., a wireless transmission chain) of entity 1.

[0225] For example, assuming that data D1 is a bit stream and multiple pilot patterns are multiple pilot symbol sequences, the bit stream D1 provided by source 11 determines which pilot symbol sequence to use in the resource grid of each radio subframe to be transmitted. Figure 10 An example of the implementation and function of the pilot mode selection unit 12 and the resource grid mapping unit 14 is shown. The terms "pilot symbol" and "pilot mode symbol" can be used as synonyms.

[0226] Figure 10 An example of the functionality of an entity for wireless communication provided by the present invention is shown. Figure 10 The entity that demonstrates the exemplary functionality is Figure 9 An example of entity 1. Figure 9 The description corresponds to Figure 10 efficient.

[0227] like Figure 10 As shown, the pilot mode selection unit 12 and the resource grid mapping unit 14 can be implemented as a processor and a resource grid mapper, respectively. The processor 12 can receive data D1 in the form of a first data symbol. The processor 12 can provide data to the mapper 14 based on the received first data symbol, pilot symbol, pilot index, and data index, according to an encoding scheme, so as to provide data D1 in the form of one or more pilot modes. The mapper 14 can receive second data D2 in the form of a second data symbol and data D1 in the form of a pilot symbol, pilot index, and data index. The mapper 14 can use the received information to determine which resources in the resource grid to use to transmit a signal, the signal including data D1 in the form of one or more pilot modes and second data D2 as the payload of the signal. When a radio subframe resource block is formed, the resource slots for the pilot modes can be filled with mode symbols for encoding one or more pilot modes of data D1 provided from the processor output, while the resource slots for the second data D2 can be filled with the expected data payload. The resource slot indexes for one or more pilot modes can be provided by the processor output. Processor 12 can internally use a buffer that supports synchronizing the data rate of data D1 with the data rate of the second data D2. Processor 12 can perform or assist in resource grid mapping of the radio frames to be transmitted. Figure 10 On the right, an example of a resource grid divided by OFDM symbols and subcarriers is shown.

[0228] Figure 11 An example of an implementation of the entity for wireless communication provided by the present invention is shown. Figure 11 Entity 2 is Figure 5 An example of how entity 2 is implemented. Figure 5 The description corresponds to Figure 11 Entity 2 is valid.

[0229] Figure 11 The entity is an example of an entity used for wireless communication, which receives signals sent to it and extracts (i.e., decodes) the data of the signal, i.e., the data of the signal payload, wherein the signal may include other data in the form of one or more pilot patterns from a plurality of pilot patterns used for broadcasting other data. That is, Figure 11 Entity 2 can be used to receive and extract (i.e., decode) data D2 (which can be called second data), which is generated by another entity (e.g. Figure 1 or Figure 9 Entity 1) sends the payload of signal 100, and assumes that another entity intends to send signal 100, so it sends data D2 to entity 2.

[0230] For this purpose, entity 2 may include one or more antennas 21 for receiving signals. Figure 11 The number of antennas 21 shown is merely illustrative and may vary. In the case of multiple antennas 21, these antennas may be part of an antenna array. Entity 2 may include a pilot mode detection unit 22 for detecting signals (e.g., Figure 8 Entity 2 can detect one or more pilot patterns from a plurality of pilot patterns that can be used to include data D1 in the signal (signal 100). Entity 2 can include a decoding unit 23 for extracting data D1 (i.e., side information) of the signal from one or more pilot patterns according to a decoding scheme that maps each of the plurality of pilot patterns to different data. Entity 2 can be used to extract second data D2 from the signal. For this purpose, entity 2 can include a channel estimation and interpolation unit 24, a data detection unit 25, and a decoding unit 26. The channel estimation and interpolation unit 24 can perform channel estimation based on one or more pilot patterns detected by the pilot pattern detection unit 22. Then, the data detection unit 25 and the decoding unit 26 can extract the second data D2 of the signal, i.e., the payload.

[0231] Optionally, entity 2 may include a pilot pattern verification unit 27. The pilot pattern verification unit 27 can be used to verify the extracted second data D2, and if the verification of the extracted second data D2 fails, it is determined that the pilot pattern detection unit 22 has detected an error in one or more pilot patterns. The pilot pattern verification unit 27 can perform a cyclic redundancy check (CRC) verification of the second data D2. Entity 2 is used to: if an error is determined, re-perform the detection of one or more pilot patterns in the signal and extract data from the re-detected one or more pilot patterns. That is, if an error is determined, the pilot pattern detection unit 22 can again detect one or more pilot patterns in the signal received by one or more antennas 21, and the decoding unit 23 can extract data from the re-detected one or more pilot patterns. In other words, if the pilot pattern detection unit 22 detects at least one erroneous pilot pattern in the signal, the anomaly (i.e., error) can be detected in a later stage of signal processing (e.g., by the pilot pattern verification unit 27). This supports repeated signal processing of the signal with respect to data D1 included in the signal in the form of one or more pilot patterns. Therefore, when entity 2 (i.e., pilot pattern detection unit 22) detects one or more pilot patterns in the repeated signal due to an error determined by pilot pattern verification unit 27, it can exclude one or more previously selected pilot patterns. Thus, decoding of the signal used to extract data D2 as the payload can be recovered from erroneous pilot pattern detection. Pilot pattern detection can include or be pilot pattern prediction. This supports the possibility that payload data detection may not be affected by the broadcast of data D1 in the form of one or more pilot patterns from a plurality of pilot patterns.

[0232] For example, entity 2 can be a base station (BS), and the signal can be received from user equipment (UE) by one or more antennas 21. In this example, the signal can be an uplink signal. Pilot pattern detection unit 22, channel estimation and interpolation unit 24, data detection unit 25, and decoding unit 26 can be part of or form part of the wireless communication receiver chain of entity 2.

[0233] Figure 12 An example of an implementation of the entity for wireless communication provided by the present invention is shown. Figure 12 Entity 3 is Figure 3 An example of how entity 3 is implemented. Figure 3 The description corresponds to Figure 12 Entity 3 is valid.

[0234] Figure 12Entity 3 is an example of an entity used for wireless communication, which is used to listen for (i.e. receive) data included in a signal in the form of one or more pilot modes among a plurality of pilot modes, wherein the signal is not sent to entity 3 but to another entity used for wireless communication.

[0235] Entity 3 may include one or more antennas 31 for receiving signals. Figure 12 The number of antennas 31 shown is merely illustrative and may vary. In the case of multiple antennas 31, these antennas may be part of an antenna array. Entity 3 may include a channel estimation and interpolation unit 32 for performing channel estimation for one or more pilot patterns, which encode data D1 in the signal and optionally data as the payload of a signal sent to entity 3. Entity 3 may include a pilot pattern detection unit 35 for detecting one or more pilot patterns encoding data D1 in the signal. Entity 3 may include a decoding unit 36 ​​for extracting data D1 from one or more pilot patterns according to a decoding scheme that maps each of the multiple pilot patterns to different data.

[0236] like Figure 12 As shown in the dashed box, optionally, entity 3 can use the extracted data D1 for an application. For example, data D1 included in the signal in the form of one or more pilot patterns can be sensor data. The channel estimation and interpolation unit 32, the pilot pattern detection unit 35, and the decoding unit 36 ​​can form a wireless communication receiver chain (e.g., a wireless receiver chain) for entity 3 to receive data of a signal destined for another entity, wherein the data is not the payload of the signal and will be broadcast to the other entity via signal transmission. The aforementioned wireless communication receiver chain can be referred to as a "side information receiver chain". For example, entity 3 can be a UE. Signals not destined for entity 3 but destined for another entity can be downlink signals (e.g., from the BS to another UE) or uplink signals (e.g., from the UE to the BS).

[0237] Optionally, entity 3 may include a data detection unit 33 and a decoding unit 34 to support data extraction from the signal destined for entity 3, wherein the data is the payload of the signal. Therefore, the channel estimation and interpolation unit 32, the optional data detection unit 33, and the optional decoding unit 34 may be part of, or form part of, an optional second wireless communication receiver chain (e.g., a wireless receiver chain) for receiving data from the signal destined for entity 3. This optional second wireless communication receiver chain may be referred to as a "payload data receiver chain." For example, entity 3 may be a UE. The signal destined for entity 3 may be a downlink signal.

[0238] Figure 13An example of the interaction of entities for wireless communication provided by the present invention is shown. Figure 13 Entity 1, Entity 2, Entity 3, and Entity 4 can be respectively Figure 1 or Figure 9 Entity 1 Figure 5 or Figure 11 Entity 2 Figure 3 or Figure 12 Entity 3 and Figure 6 or Figure 7 Entity 4.

[0239] exist Figure 13 In the example, it is assumed that entity 1 can send data via wireless communication network 6 (e.g., a wireless communication network). Figure 8 The signal is sent to entity 2. That is, for the above signal, entity 1 is the transmitter device, and entity 2 is the receiver device. Figure 13 As shown, entity 1 may include a pilot mode selector 1b for encoding data D1 (which will be broadcast as side information without establishing a point-to-point link) in one or more pilot modes from a plurality of pilot modes. Figure 13 In the example, entity 3 can receive signals sent by entity 1 and destined for entity 2 via network 6. For example, entity 3 can be located near entities 1 and / or 2, allowing it to receive signals sent from entity 1 to entity 2. Since the signals are not destined for entity 3, entity 3 can be referred to as a listening device. Figure 13 As shown, entity 3 may include pilot pattern detector 3b for detecting and decoding one or more pilot patterns of the signal to extract data D1 from the signal.

[0240] exist Figure 13 In the example, assume entity 4 is associated with entity 2. Entity 4 can provide an encoding scheme to entity 1, where the encoding scheme maps different data to each of a plurality of pilot patterns. Therefore, entity 1 can encode data D1 in the form of one or more pilot patterns according to the encoding scheme. For example, entity 1 is used to send a service request to entity 4. Entity 4 can receive the service request from entity 1 and, in response to receiving the service request, send the encoding scheme to entity 1.

[0241] Entity 4 can send a decoding scheme consistent with the encoding scheme to Entity 3. Therefore, Entity 3 can receive from Entity 4 a decoding scheme that maps each of the multiple pilot patterns to different data. Entity 3 can be associated with Entity 1 because at least one of the following is true: Entity 3 and Entity 1 can be in a common cell; the entities can be in a specific area; the distance between Entity 3 and Entity 1 is less than a threshold; and Entity 3 and Entity 1 are part of a common communication subnet.

[0242] Because entity 4 is associated with entity 2, entity 2 can have knowledge about a decoding scheme from entity 4 that maps each of multiple pilot patterns to different data. For example... Figure 13 As shown, entity 4 can store the encoding scheme and the corresponding decoding scheme in memory 2a, which may be part of or associated with entity 4, allowing entity 4 to access memory 2a. Therefore, entity 1 may include memory 1a for storing the encoding scheme received from entity 4. Memory 1a may be part of or associated with entity 1, allowing entity 1 to access memory 1a. Entity 3 may include memory 3a for storing the decoding scheme received from entity 4. Memory 3a may be part of or associated with entity 3, allowing entity 3 to access memory 3a.

[0243] Optionally, entity 4 may be associated with another entity or not with entities such as entity 2. In this case, entity 4 may send a decoding scheme consistent with the encoding scheme to entity 2. Therefore, entity 2 can receive from entity 4 a decoding scheme that maps each of the multiple pilot patterns to different data. Entity 2 may include a memory for storing the decoding scheme received from entity 4. Figure 13 (Not shown in the image). The memory may be part of or associated with entity 2, allowing entity 2 to access the memory. Providing the encoding scheme to entity 1 and the decoding scheme to entity 3 are... Figure 13 The middle is indicated by a dashed arrow.

[0244] Entity 4 can be referred to as the controller unit. The encoding and decoding schemes support data D1 (i.e., side information) being broadcast by entity 1 to entities (which can be called listeners), such as entity 3, because entity 1 sends data to entity 2... Figure 8 The signal is consistent with the signal. Figure 13 In the diagram, reference numeral "5a" indicates a transmission from entity 1 to entity 2; reference numeral "5b" indicates a transmission from entity 2 to entity 1; and reference numeral "5c" indicates a broadcast. For example, if entity 1 is a UE and entity 2 is a BS, then transmission 5a is an uplink transmission and transmission 5b is a downlink transmission. Entity 3 can be a UE. Therefore, entity 1, as a UE, can transmit to entity 2... Figure 8 The signal is used to send data to entity 3, which is the UE, without transmitting data through entity 2, which is the BS. The data is included in the signal in the form of one or more pilot modes from a plurality of pilot modes. Therefore, entity 1 does not need to establish a point-to-point link with entity 3. Thus, D2D communication between entity 1 and entity 3 can be achieved without establishing a point-to-point link between them.

[0245] Entity 4 can support this communication (i.e., broadcasting) of data from entity 1 to entity 3 using one or more of the multiple pilot modes by providing entity 1 with an encoding scheme that maps different data to each of the multiple pilot modes and providing entity 3 with a decoding scheme consistent with the encoding scheme.

[0246] Figure 14 An example of the interaction of entities for wireless communication provided by the present invention is shown. Figure 14 Entity 1, Entity 2, Entity 3, and Entity 4 can be respectively Figure 1 or Figure 9 Entity 1 Figure 5 or Figure 11 Entity 2 Figure 3 or Figure 12 Entity 3 and Figure 6 or Figure 7 Entity 4. In particular, Figure 14 An example use case of the entities proposed in this invention is shown. For this exemplary use case, it is assumed that entity 1 is a device for wireless communication, as a UE having at least one sensor (e.g., a motion sensor). Furthermore, it is assumed that entity 2 is a base station (BS), there are multiple entities 3, each of which is a UE, and entity 4 is a controller unit (CU) associated with BS 2. The following description is true if one of entities 1, 2, 3, and 4 is a different communication device and / or CU 4 is associated with a different entity or not associated with another entity. Figure 14 The number of UE 3 shown is for illustrative purposes only. Assuming... Figure 14 Entities 1, 2, 3, and 4 are connected to the MIMO cellular network. If entities 1, 2, 3, and 4 are connected to different networks, the following description applies accordingly.

[0247] Device 1 can connect to a MIMO cellular network and provide communication services through BS 2. Orthogonal frequency division multiplexing (OFDM) modulation can be used for uplink and downlink communication transmission. The total bandwidth can be divided into a specific number of subcarriers, and each OFDM frame has a specific number of symbols. After a certain time or event, CU 4 associated with BS 2 (e.g., located at BS 2) can notify device 1 of the availability of the service according to the invention in the area of ​​device 1. This service can be referred to as a "proximity service". This service enables the device to broadcast information, such as sporadic information, to other nearby devices. In other UEs 3, it is assumed that UEs near device 1 are marked by reference numeral "3". Other devices located near device 1 (e.g., UE 3') that listen for the broadcast can sense the proximity of device 1 and / or use the broadcast information to trigger a specific action. For example, the broadcast information can be at least one of GPS coordinates, device orientation, and sensor data from sensors of device 1 (e.g., from an embedded accelerometer). Sharing this type of information improves awareness of spatial context between devices (i.e., device 1 and UE 3'), thereby facilitating rich device-to-device interactions without the need to establish dedicated point-to-point communication between device 1 and other UEs 3' near device 1.

[0248] The sensing application running on device 1 can initiate (i.e., send) a service request (which may be referred to as a "proximity service request") to CU 4. For example, the sensing application can broadcast accelerometer sensor data from device 1 so that the motion of the first device can be interpreted by other nearby devices (e.g., UE 3').

[0249] The request content of a service request can specify the nature of the data to be broadcast, thereby enabling CU4 to determine an appropriate encoding strategy. A service request may include at least one of the following: the nature of the data (e.g., sensor type if the data is sensor data), the data format (e.g., information structure, bit resolution, etc.), the supported data rate, information about the application purpose (e.g., extended reality (XR) application or augmented reality (AR) application), and the application context.

[0250] Optionally, device 1 may propose an encoding strategy to CU4 in the service request. CU4 can then determine an encoding scheme based on the proposed strategy. This could be the case, for example, when device 1 has recently used the service and can therefore reuse its previous configuration. In this case, CU4 may simply update the configuration parameters in its response. The aforementioned action of device 1 sending a service request to CU4... Figure 14The middle is indicated by arrow S1.

[0251] Upon receiving a service request, CU 4 can evaluate information about the service request, such as data flow requirements. Since encoding relies on pilot patterns (which can be called communication pilot patterns), CU 4 can consider currently allocated pilot patterns within the network cell or near device 1. Therefore, CU 4 can generate a pool of available pilot patterns (i.e., multiple pilot patterns) that can be selected for encoding. Pilot patterns can be sequences of complex values. The length of this sequence conforms to the current set of communication parameters used by device 1. In the case of OFDM, a resource index can be specified in the pilot pattern information. Multiple pilot patterns can be orthogonal to each other. Multiple pilot patterns do not necessarily need to be orthogonal. This allows CU 4 to acquire a wide range of randomly generated pilot patterns into the selection pool.

[0252] For example, the physical layer (e.g., the 5G NR physical layer) can utilize time-frequency resources for transmission. This invention is not limited to the 5G NR standard; therefore, the description is applicable to different communication standards. Resource elements form a resource grid to accommodate physical properties derived from the parameter set used for transmission, such as subcarrier spacing and the number of OFDM symbols within a radio frame. CU 4 can select the pilot mode based on the current parameter set and resource configuration used in the communication between entity 1 and entity 2 (i.e., the current example used in the uplink communication between device 1 and BS 2).

[0253] CU 4 can select multiple pilot patterns (for broadcast data, i.e., side information), allowing the information structure of the pilot patterns to be simplified for identification by other devices (e.g., UE 3) using a simple and low-complexity method. One possible way to select pilot patterns is to retain those that have significant structural differences from other pilot patterns in the set (i.e., among multiple pilot patterns). Below, examples of selection schemes that can be performed by CU 4 are provided, which include measuring the variance of the relative difference between each pair of pilot patterns in the set. CU 4 can use a (predefined) lower bound (i.e., lower limit) as the acceptance criterion for the variance value. An example of the above selection scheme can be represented as follows, where p1 and p2 are a pair of pilot patterns:

[0254]

[0255] Another example of the selection schemes that CU 4 can use may include a decision strategy based on the norm 2 distance between each pair of pilot modes p1 and p2, which can be represented as follows:

[0256]

[0257] CU 4 can determine (e.g., define) the coding scheme to be used after CU 4 has determined (e.g., formed) multiple pilot patterns for broadcasting. For example, CU 4 can map each of the multiple pilot patterns to one or more bits of the bitstream (i.e., data stream) for encoding. This supports meeting the target encoded data bit rate on a best-effort basis. CU 4 can determine Several pilot patterns (as multiple pilot patterns used for broadcasting) are used to indicate the data stream. A sequence of bits is used for encoding.

[0258] Optionally, CU 4 may additionally determine (e.g., define) other coding strategies to be subsequently applied to pilot pattern coding. For example, CU 4 may specify a redundancy number such that each pilot pattern used to encode data in the signal is repeatedly transmitted to simplify decoding prediction. CU 4 may specify a predetermined sequence of pilot patterns that may indicate contextual notifications, such as synchronization events of the data stream. CU 4 may specify a guard interval within the transmitted pilot patterns, wherein, for example, broadcast services are disabled and a default communication pilot pattern is used in uplink transmission. This may be desirable if the transmitting device (e.g., Device 1) or BS (e.g., BS 2) does not wish to use pilot pattern coding in every radio subframe.

[0259] In other words, CU 4 can determine at least one of the following: information about the number of times at least one of one or more pilot modes of a signal to be transmitted during the transmission of the signal, the signal including data in the form of one or more pilot modes; information about a pilot mode or a sequence of two or more pilot modes specifying a context notification (e.g., a synchronization event of data); information about a default pilot mode included in the signal to indicate that the signal does not include data in the form of one or more pilot modes; information about a default pilot mode included in and retransmitted in the signal to indicate the resumption of data transmission in the form of one or more pilot modes; and information about a second default pilot mode included in the signal to indicate the resumption of data transmission in the form of one or more pilot modes.

[0260] CU 4 can acknowledge the service request (received from device 1) and transmit the determined encoding scheme to device 1. Optionally, CU 4 can transmit at least one of the aforementioned determined optional information to device 1. CU 4 can send one or more of the aforementioned optional information simultaneously with sending the encoding scheme to device 1.

[0261] For example, CU 4 can send an encoding scheme to device 1 by sending multiple pilot patterns (which may be referred to as a set of pilot patterns) to be used for broadcast data and corresponding bit sequences, i.e., a mapping of different data (e.g., different bit sequences in the bit sequence) to each of the multiple pilot patterns. CU 4 can provide pilot symbol sequences (for the multiple pilot patterns). Optionally, CU 4 can provide one or more short identification codes associated with a predefined codebook of the multiple pilot patterns. After encoding the data to be broadcast in the form of one or more pilot patterns (i.e., after pilot encoding), CU 4 can send one or more additional encoding schemes (e.g., redundancy, guard intervals, and / or reference sequences) as exemplarily described above to device 1 for execution by device 1. Optionally, CU 4 can send an expiration time for using this service, after which device 1 needs to renew the service request, i.e., resend the service request. In response to the service request from the device, the above-described transmission from CU 4 to device 1 is completed. Figure 14 The middle is indicated by arrow S2a.

[0262] CU 4 can also send a decoding scheme consistent with the encoding scheme sent to device 1 to other devices near device 1 (e.g., UE 3' in UE 3). To this end, CU 4 can send to other devices (e.g., UE 3' in UE 3) multiple pilot patterns to be used for broadcast data and corresponding bit sequences, i.e., a mapping of each pilot pattern to different data (e.g., different bit sequences in the bit sequences). CU 4 can send to other devices (e.g., UE 3' in UE 3) one or more additional encoding schemes (e.g., redundancy, guard intervals, and / or reference sequences) as exemplarily described above. If the decoding algorithm is predetermined and known to CU 4 and other devices (e.g., UE 3' in UE 3), CU 4 can send to other devices near device 1 (e.g., UE 3' in UE 3) one or more references indicating which decoding algorithm to use.

[0263] CU 4 may also send at least one of the following information about the data to be broadcast and / or the transmitter of the data to other devices near device 1 (e.g., UE 3' in UE 3): the nature of the data (e.g., sensor type if the data is sensor data), the data format (e.g., information structure, bit resolution, etc.), the supported data rate, information about the application purpose (e.g., extended reality (XR) application or augmented reality (AR) application), and the application context. CU 4 may send synchronization information supporting radio frame detection (e.g., MCS index, timing advance, etc.), waveform information about the signal to be transmitted by device 1 (e.g., frequency carrier, bandwidth, etc.), and / or the broadcast expiration time (if any) to other devices (UE 3' in UE 3). CU 4 may send updated parameters of the above information to other devices near device 1 (e.g., UE 3' in UE 3) to notify of changes in transmission configuration (e.g., uplink transmission configuration changes) from the transmission from device 1. The aforementioned transmissions from CU 4 to other devices near device 1 (e.g., UE 3' in UE 3) Figure 14 The middle is indicated by arrow S2b.

[0264] After receiving a service confirmation message from CU 4 (indicated by arrow S2a), device 1 can trigger or create its local processor (e.g., Figure 10 The local processor 12 replaces or assists the resource grid mapper in the existing uplink communication chain of device 1 (e.g., processor 12). Figure 10 Mapper 14). Assuming the data to be broadcast by device 1 is a data stream from a sensor, the processor of device 1 can encode the data stream from the sensor using multiple pilot patterns transmitted by CU 4 and perform or assist resource grid mapping on the radio frame to be transmitted. That is, the processor can perform or assist in including the data from the sensor in the form of one or more pilot patterns in the signal to be transmitted from device 1 to BS 2. When forming radio subframe resource blocks, the resource slots for pilot patterns can be filled with mode symbols for encoding one or more pilot patterns provided from the processor output, while the resource slots for data (towards BS 2, i.e., uplink data) can be filled with the expected uplink data payload for uplink transmission as usual. The processor can internally use buffers that support synchronization of the sensor data rate with the uplink data rate.

[0265] Optionally, on UE 3' near device 1, the sensing application for receiving broadcast data in the form of one or more pilot patterns can be idle and can wait for notification from CU 4 regarding the active broadcast service. Upon receiving such notification from CU 4, the sensing application of UE 3' can trigger or create a local processor of UE 3' to perform pilot pattern detection and detection of data broadcast in the form of one or more pilot patterns.

[0266] An example of UE 3' implementing pilot pattern detection can be as follows. Since UE 3' is near device 1, it can receive signals destined for BS 2 and transmitted from device 1 to BS 2. For each of the multiple pilot patterns shared by CU 4, UE 3''s processor can sample the received symbol (of the received signal) at an index corresponding to the expected position of the pilot symbol. The processor can then measure the variance of the ratio between the received sample and the expected pilot symbol. The processor can make predictions by selecting the pilot pattern that yields the minimum variance.

[0267] For example, suppose a linear propagation system exists between the transmitter device (i.e., device 1) and the listener device (i.e., UE 3'). The following model can be considered:

[0268] Assume the coherence time is longer than the pilot mode. Time-frequency resource units are in integer form. For indexing. N is the number of (resource) elements in the resource block involved in the proposed scheme. The pilot pattern is composed of the index set. and size are ( A vector (the number of pilot modes) This indicates that, in order to decode the data held by selecting a pilot mode, the process can be as follows: First, select a possible pilot mode. Next, through the set The index of selection The received symbols are normalized, where the index is represented as... Then, the calculation and representation are as follows: The Indicators related to pilot signals.

[0269] For example, It can be one of the following:

[0270] ,in, .

[0271] Assuming the noise is modeled as a zero-mean random value, then for true positive pilot detection, the ratio of received symbol values ​​normalized by predetermined symbols in the pilot pattern can be expected to be equal to (approximately equal to) the same ratio of known pilot symbols.

[0272] In other cases, the sampled received symbols may correspond to data payload symbols instead of pilot symbols, and therefore the ratio of these sampled received symbols may exhibit a higher degree of randomness. This may be expected when the pilot pattern is also inconsistent with the resource index.

[0273]

[0274] The pilot mode selection data (i.e., encoded in the form of one or more pilot modes in the signal) can be minimized by the index. Let's decode it.

[0275] The processor of UE 3' can map the predicted pilot pattern (i.e., the detected pilot pattern) to a bit sequence specified by the decoding scheme received from CU 4. The bit sequence can be buffered so that the processor can further perform redundancy checks, as specified in the message received from CU 4. A reference sequence can also be detected at this stage and reported to the sensing application. The decoded (i.e., decrypted) data (broadcast in the form of one or more pilot patterns) can be transmitted to the sensing application.

[0276] After confirming the service request from Device 1, it is assumed that CU 4 associated with BS 2 (e.g., located on BS2) can trigger or create a local processor (to assist or replace the existing channel estimator and data detector, which can process signals received from Device 1 destined for BS 2 (i.e., uplink signals)). The processor of BS 2 can perform pilot pattern detection (e.g., Figure 11 As indicated by the pilot mode detection unit 22), channel estimation (such as... Figure 11 The channel estimation and interpolation unit 24 indicates), data detection estimation (such as... Figure 11 Data detection unit 25 indicates), decoding (such as) Figure 11 (as indicated by decoding unit 26) and optional pilot mode verification (such as...) Figure 11 (As indicated by pilot mode verification unit 27).

[0277] The pilot pattern detection process can be performed as described for pilot pattern detection by UE 3' near device 1, except that the processor of BS 2 can also store the prediction score for each pilot pattern entry. BS 2 can temporarily store the entire received signal symbol and the pilot prediction results. The processor of BS 2 can perform redundancy checks on the pilot prediction results and calculate aggregate predictions.

[0278] Using prior predictions of pilot patterns for identification, the processor can perform channel estimation, interpolation, and data detection and decoding, as in a communication signal processing chain used to process uplink signals to receive uplink data.

[0279] Optionally, the BS2 processor can perform verification tests on the detected data payload, such as CRC. If an anomaly is detected, the processor has the opportunity to reconsider the result of the previous aggregation prediction and select the next prediction result. Using this new estimate of the pilot pattern, the processor can restart pilot pattern detection until the pilot pattern verification step is passed (i.e., no error is detected). If all attempts fail, BS2 can report the frame error to the normal communication controller for processing.

[0280] Figure 15 An example of a method for wireless communication provided by the present invention is shown. Figure 15 The method is an example of the method according to the ninth aspect of the present invention. Correspondingly, according to the description of the method according to the ninth aspect, [the following is a description of the method]. Figure 15 The method is effective.

[0281] Figure 15 The method is a method for wireless communication. The method includes step S150: broadcasting data by including data in the form of one or more pilot patterns from a plurality of pilot patterns into a signal including second data in step S151, and transmitting the signal including data in the form of one or more pilot patterns and second data in step S152 after step S151.

[0282] Figure 1 Entity 1 can be used to execute Figure 15 The method.

[0283] about Figure 15 For further details of the method, refer to the description of the method described in accordance with aspect nine.

[0284] Figure 16 An example of a method for wireless communication provided by the present invention is shown. Figure 16 The method is an example of the method according to the tenth aspect of the present invention. Correspondingly to the description of the method according to the tenth aspect... Figure 16 The method is effective.

[0285] Figure 16 The method is for wireless communication. The method includes: in step S160, sending a service request to an entity for wireless communication. The method also includes: in step S161, following step S160, receiving from the entity a coding scheme that maps different data to each of a plurality of pilot patterns.

[0286] Figure 2 Entity 1 and optional Figure 1 Entity 1 can be used to execute Figure 16 The method.

[0287] about Figure 16 For further details of the method, refer to the description of the method according to aspect ten.

[0288] Figure 17 An example of a method for wireless communication provided by the present invention is shown. Figure 17 The method is an example of the method according to the eleventh aspect of the present invention. Correspondingly, according to the description of the method according to the eleventh aspect, [the following is a description of the method]. Figure 17 The method is effective.

[0289] Figure 17 The method is for wireless communication. The method includes: in step S170, receiving a signal. The method includes: in step S171 following step S170, detecting one or more pilot patterns from a plurality of pilot patterns in the signal. The method includes: in step S172 following step S171, extracting data from the one or more pilot patterns.

[0290] Figure 3 Entity 3 can be used to execute Figure 17 The method.

[0291] about Figure 17 For further details of the method, refer to the description of the method according to the eleventh aspect.

[0292] Figure 18 An example of a method for wireless communication provided by the present invention is shown. Figure 18 The method is an example of the method according to the twelfth aspect of the present invention. Correspondingly to the description of the method according to the twelfth aspect... Figure 18 The method is effective.

[0293] Figure 18 The method is for wireless communication. The method includes step S180: receiving a decoding scheme that maps each of a plurality of pilot modes to different data.

[0294] Figure 4 Entity 3 and optional Figure 3 Entity 3 can be used to execute Figure 18 The method.

[0295] about Figure 18 For further details of the method, refer to the description of the method according to aspect 12.

[0296] Figure 19 An example of a method for wireless communication provided by the present invention is shown. Figure 19 The method is an example of the method according to the thirteenth aspect of the present invention. Correspondingly to the description of the method according to the thirteenth aspect... Figure 19 The method is effective.

[0297] Figure 19 The method is for wireless communication. The method includes: in step S190, receiving a signal. The method includes: in step S191 after step S190, detecting one or more pilot modes from a plurality of pilot modes that can be used to include data in the signal. Optionally, the method may include: in step S192 after step S191, extracting data (such as...) from the one or more pilot modes. Figure 19 (Indicated by the dashed box in the middle).

[0298] Figure 5 Entity 2 can be used to execute Figure 19 The method.

[0299] about Figure 19 For further details of the method, refer to the description of the method described in accordance with aspect thirteen.

[0300] Figure 20 An example of a method for wireless communication provided by the present invention is shown. Figure 20 The method is an example of the method according to the fourteenth aspect of the present invention. Correspondingly to the description of the method according to the fourteenth aspect... Figure 20 The method is effective.

[0301] Figure 20 The method is a method for wireless communication. The method includes: in step S200, receiving a service request from an entity for wireless communication. The method also includes: in step S201, following step S200, in response to receiving the service request, sending to the entity an encoding scheme that maps different data to each of a plurality of pilot modes.

[0302] Figure 6 Entity 4 can be used to execute Figure 20 The method.

[0303] about Figure 20 For further details of the method, refer to the description of the method according to aspect fourteen.

[0304] Figure 21 An example of a method for wireless communication provided by the present invention is shown. Figure 21 The method is an example of the method according to the fifteenth aspect of the present invention. Correspondingly to the description of the method according to the fifteenth aspect... Figure 21 The method is effective.

[0305] Figure 21 The method is for wireless communication. The method includes step S210: sending a decoding scheme that maps each of a plurality of pilot modes to different data to one or more entities for wireless communication.

[0306] Figure 7 Entity 4 and optional Figure 6 Entity 4 can be used to execute Figure 21 The method.

[0307] about Figure 21 For further details of the method, refer to the description of the method according to aspect fifteen.

[0308] This invention has been described in conjunction with various embodiments as examples and implementations. However, based on a study of the drawings, the invention, and the independent claims, those skilled in the art will be able to understand and implement other variations when carrying out the claimed subject matter. In the claims and the specification, the word "comprising" does not exclude other elements or steps, and "a" or "an" does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items described in the claims. The enumeration of certain measures in dissimilar dependent claims does not imply that combinations of these measures cannot be used in advantageous implementations.

Claims

1. An entity (1) for wireless communication, characterized in that, The entity (1) is used to broadcast data (D1) in the following manner: The data (D1) is included in one or more pilot patterns (101) and added to the signal (100) including the second data (D2). The signal (100) is transmitted, comprising the data (D1) and the second data (D2) in the form of the one or more pilot patterns (101).

2. The entity (1) according to claim 1, characterized in that, The entity (1) is configured to select one or more pilot patterns (101) from the plurality of pilot patterns according to an encoding scheme (300a), the encoding scheme (300a) being used to map different data to each of the plurality of pilot patterns.

3. The entity (1) according to claim 2, characterized in that, The entity (1) is used for: Send a service request (200) to the second entity (4) for wireless communication, and, The encoding scheme (300a) is received from the second entity (4).

4. The entity (1) according to any one of the preceding claims, characterized in that, The entity is used for: When the signal is transmitted, at least one of the one or more pilot modes is transmitted two or more times; and / or Send one pilot pattern, a sequence of two pilot patterns, or a sequence of more than one pilot pattern to specify context notification; and / or Send the signal including a default pilot mode and the second data, wherein the default pilot mode indicates that data is not being sent in one or more pilot modes; and / or The retransmission includes the signal of the default pilot mode and the second data, wherein the default pilot mode of the retransmission indicates the resumption of data transmission in one or more pilot modes; and / or The signal is transmitted, which includes a second default pilot mode and the second data, wherein the second default pilot mode indicates the resumption of data transmission in one or more pilot modes.

5. The entity (1) according to claim 4, characterized in that, The entity is used to receive at least one of the following information: Information regarding the number of times at least one of the one or more pilot modes that transmit the signal during the transmission of the signal; Information about a pilot pattern or a sequence of two or more pilot patterns for a specified context notification; Information regarding the default pilot pattern included in the signal, indicating that the signal does not include data in the form of one or more of the plurality of pilot patterns; Information regarding the default pilot pattern included in and retransmitted in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot patterns; Information regarding the second default pilot mode included in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot modes.

6. An entity (1) for wireless communication, characterized in that, The entity (1) is used for: Send a service request (200) to the second entity (4) used for wireless communication. Receive from the second entity (4) a coding scheme (300a) that maps different data to each of the multiple pilot patterns.

7. An entity (3) for wireless communication, characterized in that, The entity (3) is used for: Receive signal (100). One or more pilot modes (101) are detected in the signal (100) among a plurality of pilot modes. Data (D1) is extracted from the one or more pilot patterns (101).

8. The entity (3) according to claim 7, characterized in that, The entity (3) is used to extract the data (D1) from the one or more pilot patterns (101) according to the decoding scheme (300b) that maps each of the plurality of pilot patterns to different data.

9. The entity (3) according to claim 8, characterized in that, The entity (3) is used to receive the decoding scheme (300b) from the second entity (4) of the wireless communication.

10. The entity (3) according to any one of claims 7 to 9, characterized in that, The entity (3) is used to receive at least one of the following information: Information regarding the number of times at least one of the one or more pilot modes that transmit the signal during the transmission of the signal is two or more times; Information about a pilot pattern or a sequence of two or more pilot patterns for a specified context notification; Information regarding the default pilot pattern included in the signal, indicating that the signal does not include data in the form of one or more of the plurality of pilot patterns; Information regarding the default pilot pattern included in and retransmitted in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot patterns; Information regarding the second default pilot mode included in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot modes.

11. An entity (3) for wireless communication, characterized in that, The entity (3) is used to receive a decoding scheme (300b) that maps each of the multiple pilot modes to different data.

12. An entity (2) for wireless communication, characterized in that, The entity is used for: Receive signal (100). One or more pilot modes (101) among a plurality of pilot modes that can be used to include data in the signal (100) are detected in the signal.

13. The entity (2) according to claim 12, characterized in that, The entity is used to extract data (D1) from the one or more pilot patterns (101).

14. The entity (2) according to claim 12 or 13, characterized in that, The entity (2) is used to extract second data (D2) from the signal (100).

15. The entity (2) according to claim 14, characterized in that, The entity (2) is used for: Verify the extracted second data (D2) described in (27). If the verification of the extracted second data (D2) fails, an error is determined in the detection of the one or more pilot patterns (101).

16. The entity (2) according to claim 15, characterized in that, The entity (2) is used to: if the error is determined, re-execute the detection of the one or more pilot patterns (101) in the signal (100) and extract the data (D1) from the re-detected one or more pilot patterns (101).

17. Entity (2) according to any one of claims 12 to 16, characterized in that, The entity (2) is used to extract the data (D1) from the one or more pilot patterns (101) according to the decoding scheme (300b) that maps each of the plurality of pilot patterns to different data.

18. The entity (3) according to claim 17, characterized in that, The entity (2) is used to receive the decoding scheme (300b) from the second entity (4) used for wireless communication.

19. The entity (3) according to any one of claims 12 to 18, characterized in that, The entity (3) is used to receive at least one of the following information: Information regarding the number of times at least one of the one or more pilot modes that transmit the signal during the transmission of the signal is two or more times; Information about a pilot pattern or a sequence of two or more pilot patterns for a specified context notification; Information regarding the default pilot pattern included in the signal, indicating that the signal does not include data in the form of one or more of the plurality of pilot patterns; Information regarding the default pilot pattern included in and retransmitted in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot patterns; Information regarding the second default pilot mode included in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot modes.

20. An entity (4) for wireless communication, characterized in that, The entity (4) is used for: Receive service request (200) from the second entity (1) used for wireless communication. In response to receiving the service request (200), the second entity (1) sends an encoding scheme (300a) that maps different data to each of the multiple pilot patterns.

21. The entity (4) according to claim 20, characterized in that, The entity (4) is used to send at least one of the following information to the second entity (1): Information regarding the number of times at least one of the one or more pilot modes of the transmitted signal is transmitted twice or more during the transmission of the signal by the second entity, the signal including data (D1) in the form of the one or more pilot modes (101). Information about a pilot pattern or a sequence of two or more pilot patterns for a specified context notification; Information regarding the default pilot pattern included in the signal, indicating that the signal does not include data in the form of one or more of the plurality of pilot patterns; Information regarding the default pilot pattern included in and retransmitted in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot patterns; Information regarding the second default pilot mode included in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot modes.

22. The entity (4) according to claim 20 or 21, characterized in that, The entity (4) is used to send a decoding scheme (300b) consistent with the encoding scheme (300a) to one or more entities (3) associated with the second entity (1) for wireless communication.

23. The entity (4) according to claim 22, characterized in that, The one or more entities (3) are related to the second entity (1) because at least one of the following is true: The one or more entities (3) and the second entity (1) are in a public community. The one or more entities (3) are in a specific area, The distance between the one or more entities (3) and the second entity (1) is less than a threshold; The one or more entities (3) and the second entity (1) are part of a public communications subnet.

24. The entity (4) according to claim 22 or 23, characterized in that, The entity (4) is used to send at least one of the following information to the one or more entities (3): Information regarding the number of times at least one of the one or more pilot modes of the transmitted signal is transmitted two or more times during the transmission of the signal, the signal including data (D1) in the form of the one or more pilot modes (101). Information about a pilot pattern or a sequence of two or more pilot patterns for a specified context notification; Information regarding the default pilot pattern included in the signal, indicating that the signal does not include data in the form of one or more of the plurality of pilot patterns; Information regarding the default pilot pattern included in and retransmitted in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot patterns; Information regarding the second default pilot mode included in the signal, to indicate the resumption of data transmission in the form of one or more of the plurality of pilot modes.

25. An entity (4) for wireless communication, characterized in that, The entity (4) is used to send a decoding scheme (300b) to one or more entities (3) for wireless communication, which maps each of the multiple pilot modes to different data.

26. A signal (100), characterized in that, include: First data (D1) in the form of one or more pilot modes (101) among a plurality of pilot modes. The second data (D2) used for transmission.

27. A method for wireless communication, characterized in that, The method includes broadcasting (S150) data in the following manner: The data, which is in the form of one or more pilot modes from a plurality of pilot modes, is included (S151) into a signal including the second data. The signal is transmitted (S152), the signal comprising the data and the second data in the form of the one or more pilot patterns.

28. A method for wireless communication, characterized in that, The method includes: Send a service request (S160) to the entity used for wireless communication. The entity receives (S161) an encoding scheme that maps different data to each of the multiple pilot patterns.

29. A method for wireless communication, characterized in that, The method includes: Receive (S170) signal, Detecting (S171) one or more pilot modes from a plurality of pilot modes in the signal, Data is extracted from the one or more pilot patterns (S172).

30. A method for wireless communication, characterized in that, The method includes: receiving (S180) a decoding scheme that maps each of a plurality of pilot modes to different data.

31. A method for wireless communication, characterized in that, The method includes: Receive (S190) signal, Detection in the signal (S191) can be used for one or more pilot modes among a plurality of pilot modes that include data in the signal.

32. A method for wireless communication, characterized in that, The method includes: Receive a service request from an entity used for wireless communication (S200). In response to receiving the service request, the entity is sent (S201) an encoding scheme that maps different data to each of the multiple pilot modes.

33. A method for wireless communication, characterized in that, The method includes: transmitting (S210) a decoding scheme that maps each of a plurality of pilot modes to different data to one or more entities for wireless communication.

Images