CN121100536A - Network node indicating absolute position information or storing absolute position information - Google Patents

Abstract

An apparatus is provided, comprising: at least one processor; and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: generate a sidelink SL discovery message indicating that absolute location information is available, the absolute location information indicating the absolute location of the apparatus; at least send the SL discovery message to a terminal device; and at least one of a network node indicating the absolute location information to the terminal device or storing the absolute location information.

Description

Network nodes that indicate or store absolute location information

Technical Field

Various example implementations generally relate to cellular communications. More specifically, various examples relate to network nodes that indicate or store absolute location information in side-link positioning.

Background Technology

Sidelink positioning (or lateral positioning) is a process for determining the location of one or more terminal devices, based at least on the transmission of one or more reference signals between different UEs. Relative positioning or localization can be performed without absolute location information, but absolute positioning or localization may require knowledge of the absolute locations of other UEs. Therefore, providing a solution in a sidelink communication system that enables the sharing of absolute location information can be beneficial.

Summary of the Invention

The subject matter of the independent claims is provided according to several aspects. Additional aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims are to be interpreted as examples that aid in understanding this disclosure.

Attached Figure Description

The invention will now be described in more detail with reference to embodiments and accompanying drawings, wherein...

Figure 1 illustrates a network applicable to one or more embodiments;

Figure 2 illustrates an example of sidelink positioning applicable to one or more embodiments;

Figures 3A, 3B, 4, 5A, 5B, 5C, 6A, 6B, 6C, and 7 illustrate some example embodiments; and

Figures 8 and 9 illustrate apparatus according to some embodiments.

Detailed Implementation

The following embodiments are exemplary. Although the specification may refer to "a," "an," or "some" embodiments in several places in the text, this does not necessarily mean that the same embodiment is referred to every time, or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. For the purposes of this disclosure, the phrases "at least one of A or B," "at least one of A and B," and "A and/or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A or B" and "A and/or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and/or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

It should be understood that although the terms "first" and "second," etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments.

The described embodiments can be implemented in radio systems, such as radio systems including at least one of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, and Enhanced LTE (eLTE). The term "eLTE" here refers to LTE evolution connected to the 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN). The term "resource" can refer to radio resources, such as Physical Resource Blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmit" and/or "receive" can refer to wirelessly transmitting and/or receiving on radio resources via a radio propagation channel.

However, the embodiments are not limited to the system/RAT given as an example, but those skilled in the art can apply the solution to other communication systems/networks with the necessary attributes. Some examples of suitable communication networks include 5G and/or 6G networks. The 3GPP solution for 5G is called New Radio (NR). 6G is envisioned as a further development of 5G. NR is envisioned to use multiple-input multiple-output (MIMO) multi-antenna transmission technology, deploy more base stations or nodes than current LTE networks (the so-called small cell concept), including macro sites that cooperate with smaller local access nodes, and may also employ various radio technologies to achieve better coverage and enhanced data rates. 5G will likely include more than one radio access technology/radio access network (RAT/RAN), each optimized for certain use cases and/or spectrum. 5G mobile communications can have a wider range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications, including vehicle safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces, namely, below 6 GHz, cmWave, and mmWave, and can be integrated with existing legacy radio access technologies such as LTE.

The current architecture in LTE networks is distributed across radios and centralized in the core network. Low-latency applications and services in 5G may require bringing content closer to the radio, leading to local outages and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not be discontinuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for hosting applications and services. It also has the ability to store and process content near cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networking and processing, and can also be categorized as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, micro-cloud, distributed data storage and retrieval, autonomous and self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and/or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). Edge cloud can be brought into the RAN by leveraging Network Functions Virtualization (NVF) and Software-Defined Networking (SDN). Using edge cloud may mean performing access node operations, at least partially, in servers, hosts, or nodes that are operatively coupled to remote radio heads or base stations, including radio components. Network slicing allows the creation of multiple virtual networks over a shared physical infrastructure. These virtual networks can then be customized to meet the specific needs of applications, services, devices, customers, or operators.

In radio communications, node operations can be performed, at least partially, in a central/centralized unit (CU) (e.g., a server, host, or node) operatively coupled to a distributed unit (DU) (e.g., a radio head/node). Node operations can also be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of operations between core network operations and base station operations can vary depending on the implementation. Therefore, 5G network architectures can be based on so-called CU-DU partitioning. One gNB-CU controls several gNB-DUs. The term "gNB" in 5G can correspond to the eNB in LTE. One or more gNBs can communicate with one or more UEs. A gNB-CU (central node) can control multiple spatially separated gNB-DUs, at least acting as a transmit/receive (Tx/Rx) node. However, in some embodiments, the gNB-DU (also known as DU) may include, for example, the Radio Link Control (RLC), Media Access Control (MAC) layer, and Physical (PHY) layer, while the gNB-CU (also known as CU) may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC), and Internet Protocol (IP) layer. Other functional partitioning is also possible. It is assumed that those skilled in the art are familiar with the OSI model and the functions within each layer.

In an embodiment, the server or CU can generate a virtual network through which the server communicates with radio nodes. Typically, virtual networking can involve the process of combining hardware and software network resources and network functions into a single, software-based management entity (virtual network). Such a virtual network can provide flexible operational distribution between the server and the radio head end/node. In practice, any digital signal processing task can be performed in the CU or DU, and the boundaries of responsibility transferred between the CU and DU can be selected depending on the implementation.

Some other potential technological advancements to utilize are Software-Defined Networking (SDN), big data, and all-IP, to name just a few non-limiting examples. For instance, network slicing can take the form of a virtual network architecture that uses the same principles behind Software-Defined Networking (SDN) and Network Functions Virtualization (NFV) within a fixed network. SDN and NFV can provide greater network flexibility by allowing traditional network architectures to be divided into virtual components that can be linked (again, via software). Network slicing allows the creation of multiple virtual networks on top of a shared physical infrastructure. These virtual networks can then be customized to meet the specific needs of applications, services, devices, customers, or operators.

Multiple gNBs (access points/nodes), each comprising a CU and one or more DUs, can connect to each other via an Xn interface on which they can negotiate. The gNBs can also connect to the 5G core network (5GC) via a next-generation (NG) interface, which can be a 5G equivalent of the LTE core network. This type of 5G CU-DU split architecture can be implemented using a cloud/server architecture, where the higher-level CU resides in the cloud, and the DU is closer to or includes the actual radio and antenna units. Similar ongoing initiatives exist for LTE/LTE-A/eLTE. When both eLTE and 5G will use a similar architecture in the same cloud hardware (HW), the next step could be to combine software (SW) to allow a common SW to control both radio access networks/technologies (RAN/RAT). This could allow new ways to control the radio resources of both RANs. Furthermore, it is possible to have configurations where the entire protocol stack is controlled by the same HW as the CU and processed by the same radio units as the CU.

It should also be understood that the workforce distribution between core network operations and base station operations may differ from, or even not exist at all, the workforce distribution in LTE. Some other technological advancements that may be used are big data and all-IP, which could change how networks are built and managed. 5G (or New Radio, NR) networks are designed to support multiple tiers, where MEC servers can be placed between the core and base stations or Node Bs (gNBs). It should be understood that MEC can also be applied to 4G networks.

5G can also leverage satellite communications to enhance or supplement 5G service coverage, for example, by providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on transportation, or ensuring the availability of critical communications and future rail/sea/air communications. Satellite communications can utilize geostationary Earth orbit (GEO) satellite systems, and also low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite in a mega-constellation can cover a network entity of several supporting satellites that create a ground cell. Ground cells can be created via ground relay nodes or by gNBs located on the ground or in satellites.

The implementation can also be applied to narrowband (NB) Internet of Things (IoT) systems, enabling the connection of various devices and services using cellular telecommunications bands. NB-IoT is a narrowband radio technology designed for the Internet of Things (IoT) and is one of the technologies standardized by the 3rd Generation Partnership Project (3GPP). Other 3GPP IoT technologies suitable for implementing the implementation include Machine Type Communication (MTC) and eMTC (enhanced Machine Type Communication). NB-IoT focuses particularly on low cost, long battery life, and enabling a large number of connected devices. NB-IoT technology is deployed "in-band" in the spectrum allocated to Long Term Evolution (LTE) – using resource blocks within normal LTE carriers, or "guarding" the band in unused resource blocks within LTE carriers, or "independent" from deployments in dedicated spectrum.

The embodiments can also be applied to device-to-device (D2D), machine-to-machine, and peer-to-peer (P2P) communications. The embodiments can also be applied to vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and infrastructure-to-vehicle (I2V), or generally to V2X or X2V communications.

Figure 1 illustrates an example of a communication system to which embodiments of the present invention can be applied. The system may include a control node 110 providing one or more cells (such as cell 100) and a control node 112 providing one or more other cells (such as cell 102). For example, each cell may be, for example, a macro cell, micro cell, femtocell, or picocell. In another view, a cell may define the coverage area or service area of a corresponding access node. Control nodes 110 and 112 may be, for example, an evolved Node B (eNB) in LTE and LTE-A, an ng-eNB in eLTE, a gNB in 5G, or any other means capable of controlling radio communications and managing radio resources within the cell. Control nodes 110 and 112 may be referred to as a base station, a network node, or an access node.

The system can be a cellular communication system consisting of a radio access network of access nodes, with each access node controlling one or more corresponding cells. Access node 110 can provide user equipment (UE) 120 (one or more UEs) with radio access to other networks, such as the Internet. Radio access can include downlink (DL) communication from the control node to UE 120 and uplink (UL) communication from UE 120 to the control node.

Additionally, although not shown, one or more local access nodes may be arranged such that the cells provided by the local access nodes at least partially overlap with the cells of access nodes 110 and/or 112. The local access nodes may provide radio access within sub-cells. Examples of sub-cells may include microcells, picocells, and/or femtocells. Typically, sub-cells provide hotspots within macrocells. The operation of the local access nodes may be controlled by access nodes, which provide sub-cells within their control areas. Typically, the control node for a small cell may be similarly referred to as a base station, network node, or access node.

The system may have one or more UEs 120 and 122. UEs 120 and 122 may be served by one or more control nodes 110 and 112. UEs 120 and 122 may communicate with each other, for example, using a D2D communication interface established between them. D2D communication may refer to, for example, sidelink (SL) communication, such as NR sidelink communication.

The term "terminal device" or "UE" refers to any terminal device capable of wireless communication, more specifically cellular wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and return devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in the context of industrial and/or automated processing chains), consumer electronic devices, devices operating on commercial and/or industrial wireless networks, etc. In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

In the case of multiple access nodes in a communication network, the access nodes can connect to each other through an interface. The LTE specification calls such an interface an X2 interface. Similar interfaces can be provided between access points for IEEE 802.11 networks (i.e., wireless LAN, WLAN, WiFi). The interface between an LTE access point and a 5G access point, or between two 5G access points, can be called an Xn interface. Other communication methods between access nodes are also possible. Access nodes 110 and 112 can also connect to the core network 116 of the cellular communication system via another interface. The LTE specification designates the core network as the Evolved Packet Core (EPC), and the core network can include a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices in a tracking area containing multiple cells and handle signaling connections between terminal devices and the core network. Gateway nodes can handle data routing in the core network and data routing to/from terminal devices. The 5G specification designates the core network as the 5G Core (5GC), and the core network can include, for example, Access and Mobility Management Functions (AMF) and User Plane Functions/Gateways (UPF), to name just a few. AMF can handle Non-Access Stratum (NAS) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, a UPF node can support packet routing and forwarding, packet inspection, and QoS processing.

6G networks are expected to employ flexible decentralized and/or distributed computing systems and architectures, along with ubiquitous computing, where local spectrum licensing, spectrum sharing, infrastructure sharing, and intelligent automated management are determined by mobile edge computing, artificial intelligence, short packet communication, and blockchain technologies. Key features of 6G will include intelligent connectivity management and control, programmability, integrated sensing and communication, reduced energy consumption, trusted infrastructure, scalability, and affordability. In addition, 6G addresses new use cases by integrating location and sensing capabilities into the system definition to unify the user experience across the physical and digital worlds.

One or more UEs 120, 122 in the cellular communication system of Figure 1 can support sidelink positioning. In sidelink positioning, positioning is a positioning technique used, for example, in 5G NR communication networks. In sidelink positioning, signals transmitted via a sidelink (i.e., between UEs) are used to calculate the location of a given UE. When a UE determines that sidelink positioning is needed, it can first determine which potential anchor UEs (i.e., UEs that can be used as reference points in the positioning calculation) are within its range, and then select one or more of these anchor UEs to perform triangulation or other actions required to determine the location. The location of the target UE can be determined at the target UE, at the location management function (LMF) (sometimes referred to as a location server or sensing server), and/or at one of other UEs supporting the target UE or acting as an LMF. Location determination can be based at least on measurements of one or more location reference signals (PRS) transmitted between the anchor UE and the target UE.

For example, to enable the anchor UE to indicate whether its location is known, a Sidelink Location Protocol (SLPP) metadata field can be included in the sidelink discovery message to indicate whether the location is known. This indication could be a flag or binary indicator: "Location Known" or "Location Unknown." Thus, a potential target UE can determine whether the anchor UE's location is known, and therefore whether it can be used to determine the target UE's location (also known as the target UE's positioning). The target UE's position relative to the anchor UE can be calculated based on measurements of one or more reference signals (PRS and/or SRS) transmitted between the anchor UE and the target UE. To calculate the target UE's absolute position, it may be necessary to know the anchor UE's absolute position (i.e., using multipoint positioning relative to the anchor UE). Therefore, an indication from the anchor UE can indicate whether the anchor UE's absolute position is known. For example, if the anchor UE's absolute position is known, the UE can be referred to as the "positioning UE."

Some simple examples of how to calculate/determine the location of target UE 120 are shown. Referring to Figure 2, according to the first example, target UE 120 can measure the PRS (i.e., SL PRS) transmitted by anchor UEs 122, 222 via sidelink communication links 202, 204. According to the second example, target UE 120 can transmit the PRS (i.e., SL PRS) to anchor UEs 122, 222 via sidelink communication links 202, 204. Combinations of the first and second examples can be used.

The transmitted PRS can be measured to obtain information such as direction (e.g., angle of arrival (AOA)) and strength (e.g., received signal strength indicator (RSSI)). Based on this information and information about the location on anchor UEs 122 and 222, the absolute location of target UE 120 can be determined. In one example, the absolute location of target UE 120 can be determined at target UE 120. In another example, the absolute location of target UE 120 can be determined at location management entity 250 (e.g., LMF or UE acting as LMF (e.g., referred to as server UE)). In this case, the measurement of PRS can be shared with location management entity 250. However, it has not been proposed how to provide an indication (where the location is known/unknown) between UEs and how to use this indication to determine the absolute location of the anchor UE at the entity that will determine the absolute location of the target UE. Therefore, a solution capable of providing absolute location information at anchor UEs has been proposed.

Figures 3A and 3B illustrate flowcharts according to some embodiments. Referring to Figure 3A, a method for an apparatus for a radio access network (RAN) such as a cellular communication network is proposed. This apparatus may be or be included in a UE, such as UE 120, 122, 222 of Figures 1 and/or 2. For simplicity, the apparatus performing the method of Figure 3A is referred to herein as UE 122. Therefore, this apparatus may be able to act as an anchor UE for sidelink positioning. In some examples, UE 122 may be referred to as a positioning UE (LUE). That is, UE 122 may be a LUE if the absolute location of UE 122 is known to, for example, UE 122 or LME 250.

According to an embodiment, the method of FIG3A includes: generating an SL discovery message indicating that absolute location information (indicating the absolute location of the device) is available (box 302); sending the SL discovery message to at least a terminal device (box 304); and indicating the absolute location information and/or a network node storing the absolute location information to the terminal device (box 306).

An SL discovery message can be sent to one or more terminal devices. For example, an SL discovery message can be broadcast by UE 122, and other UEs can receive the broadcast SL discovery message. In this example, the SL discovery message is sent to at least one UE (referred to above as a terminal device). The terminal device can be referred to below as UE 120, which can be the target UE (tUE) that needs to be located via SL positioning (session-based or session-free SL positioning).

The solution proposed in this paper suggests that an SL discovery message can be used to indicate that the location of UE 122 is known (i.e., location information is available and indicates that the absolute location of UE 122 is known). For example, this indication could be a flag or bit indicator indicating that location information is available. On the other hand, if location information is unavailable, UE 122 can send an SL discovery message indicating that location information is unavailable, or it can not send an SL discovery message at all. Sending an SL discovery message indicating that location information is unavailable may also be beneficial, as such a UE can still be enabled to perform relative positioning. However, the absolute location of UE 122 (and possibly some other UEs) may be needed to perform absolute positioning of the target UE 120 (to improve positioning accuracy). Furthermore, the solution proposes that UE 122 indicate its absolute location information or a network node storing such information to the target UE 120. Therefore, the target UE 120 can directly obtain the absolute location information or request it from the indicated network node storing the absolute location information. Therefore, the target UE 120 can obtain the absolute position information on UE 122, which can then be used for the absolute positioning of the target UE 120. As described with reference to FIG2, the absolute position of the anchor UE may be needed to determine the absolute position of the target UE.

Absolute location information and/or indications of the network node storing the absolute location information can be accomplished in various ways. For example, an SL discovery message sent in box 304 can be used to transmit such information. Other examples include sharing the information as encrypted information (using one or more encryption keys) and/or as auxiliary data via Radio Resource Control (RRC) signaling, via Side Link Positioning Protocol (SLPP) signaling, via LTE Positioning Protocol (LPP) signaling. The indicated absolute location information and/or indications of the network node may include validity indicators (e.g., timers and/or timestamps) to indicate the validity period of the indicated information. For example, absolute location information may be indicated as valid for a specific time period. In another example, absolute location information may be associated with a timestamp indicating the time when the absolute location of UE 122 was obtained. Thus, for example, UE 120 may determine how long the information is valid based on the timestamp and some (pre)configuration.

Absolute location information can indicate the absolute location of the UE associated with it. For example, absolute location information on UE 122 can indicate the absolute location of the UE at least at a certain point in time. The accuracy of the absolute location can depend on the method used to locate UE 122 and/or the time elapsed since the location was performed. Absolute location information can indicate absolute location, for example, as coordinates. For example, coordinates can be two-dimensional or three-dimensional. For example, coordinates can indicate latitude, longitude, and/or altitude.

Referring to Figure 4, a method for an apparatus for a radio access network (RAN) such as a cellular communication network is proposed. This apparatus may be or be included in a UE, such as UE 120, 122, 222 of Figures 1 and/or 2. For simplicity, the apparatus performing the method of Figure 4 is referred to herein as UE 120. Therefore, this apparatus may be able to act as a target UE for sidelink localization. That is, UE 120 may need to be localized (or located) at a certain point.

According to an embodiment, the method of FIG4 includes: receiving an SL discovery message from a terminal device (e.g., UE 122) indicating that absolute location information indicating the absolute location of the terminal device (e.g., UE 122) is available (box 312); obtaining the absolute location information or an indication from a network node storing the absolute location information from the terminal device (e.g., UE 122) (box 314); and determining the location of the device using the absolute location information and/or the indication from the network node storing the absolute location information (box 316).

Step 312 can correspond to step 304 of FIG. 3A; that is, the SL discovery message sent (e.g., broadcast) can be received by UE 120. Similarly, step 314 can correspond to step 306 of FIG. 3A. In block 316, UE 120 can use absolute location information to determine the location of UE 120 (e.g., as explained with reference to FIG. 2), or it can request absolute location information from the indicated network node if only the network node is indicated.

One example of utilizing absolute location information is that UE 120 determines the absolute location of UE 122, and further uses this information when determining the absolute location of UE 120 based on measurements of one or more reference signals. Another example could be providing absolute location information to another entity, such as LME 250 or another UE, to determine the absolute location of UE 120. For example, if UE 120 is a wrist device or similar device, it could provide absolute location information to a mobile phone to determine the location of UE 120.

Before going into further detail, it is now highlighted that there are at least two different ways to obtain absolute location information indicating the absolute location of UE 122. The first option is that UE 122 directly indicates the information to UE 120 (and possibly some other UEs). The actual indication can be performed in several different ways, as discussed below. The second option is that UE 122 indicates the network node storing the absolute location information. The indication of the network node can be performed in several different ways. The third option is that both the absolute location information (which may be abbreviated as ALI) and the network node storing the absolute location information are indicated to UE 120.

A network node can be indicated, for example, by an identifier (e.g., a globally unique identifier). For instance, the identifier can be sent from UE 122 to UE 120. In an embodiment, the network node is UE 122; and therefore UE 122 can indicate itself as the network node storing the ALI. In one embodiment, the network node is an external network node. That is, it can be a different network node from UE 122. For example, the network node could be an LME 250 (e.g., an LMF, a location server, a sensing server, or a server UE). In the case of server UE indication, in some embodiments, UE 122 itself is the server UE, and therefore can thus indicate itself as described above.

Instead of sending the identifier of the network node storing the ALI, this indication can be implicit. For example, it can indicate the default LMF (the LMF located in the core network or at the server UE). Alternatively, the indication can explicitly indicate the default LMF without having to use the default LMF's identifier. The default LMF can refer to, for example, the default or assumed LMF of UE 120. Therefore, if the default LMF is indicated, UE 120 can request the ALI from the LMF associated with UE 120 (e.g., UE 120's default LMF).

Let us now turn to Figure 4, which illustrates a signaling diagram according to at least one embodiment. In block 400, one or more encryption keys (CKs) are assigned to UE 122 and UE 120 to enable encrypted communication for sidelink positioning. Thus, UE 122 and UE 120 can obtain one or more CKs. Similarly, if an external LME 250 is used in SL positioning, the LME 250 can also obtain one or more CKs. For example, the distribution of CKs can function such that different entities involved in encrypted communication can share their respective CKs with other entities. By doing so, CKs can be used to share encrypted information, as the information can be decrypted using CKs obtained from the information-sharing entity. Thus, for example, before sending an indication of an ALI or network node, the indication of an ALI or network node can be encrypted by UE 122. UE 120 can use at least one CK of UE 122 to decrypt the received information and obtain the indication of the ALI or network node. However, other UEs or devices may not decrypt the information because they may not have the correct CK, and therefore the location of UE 122 may remain secret from said other UEs or devices. This enhances the security of location sharing. Similar logic can be applied to situations where a network node supplies an ALI to the UE 120. That is, the ALI can be encrypted and therefore can be decrypted by the UE 120 using at least one CK from the network node (e.g., LMF).

Before delving into the details of sharing ALI with UE 120, an example of how to obtain ALI on UE 122 can be illustrated in Figure 4. Specifically, in box 404, UE 122 can initiate a positioning session including LME 250. This positioning session can be Uu-based or SL-based, where the absolute location of UE 122 can be obtained. In another example, non-RAN-specific positioning, such as satellite positioning, can be used to obtain the location of UE 122.

In the example of Figure 4, LME 250 can obtain absolute location information about UE 122, for example, based on UE 122's Uu or SL positioning (box 406). For example, SL positioning can be based on a Mobile Termination Location Request (MT-LR).

In step 408, LME 250 may provide UE 122 with absolute location information (i.e., ALI). Additionally, LME 250 may request (i.e., explicitly request) UE 122 to begin advertising ALI availability. For example, this request may be sent along with the ALI. For example, the request may be a flag or bit indicator (e.g., indicating state LUE) requesting UE 122 to activate itself as a LUE (located UE). For example, if the value of indicating state LUE is equal to 1, it may mean that LME 250 is requesting UE 122 to begin advertising ALI availability.

In this embodiment, UE 122 is configured to obtain absolute location information on UE 122 and a request indicating the availability of absolute location information by broadcasting an SL discovery message from a network node (e.g., LME 250). Therefore, UE 122 can begin broadcasting an SL discovery message indicating the availability of location information.

In another example, the request to start advertising (i.e., broadcast a discovery message) is sent separately.

In another example, the request to start advertising is implicit. That is, the LME 250 can implicitly request UE 122 to start advertising by sending an ALI to UE 122.

In yet another example, UE 122 may determine to begin sending a discovery message based on a request from LME 250 or based on receiving an ALI. In other words, as a LUE, UE 122 may activate itself based on receiving an ALI (box 410).

Alternatively, UE 122 can obtain absolute location information from another UE in the collective positioning group.

In box 412, the location session can be terminated. However, UE 122 can then be prepared to provide the ALI or indicate the network node storing the ALI of other UEs.

Figure 5A illustrates a signaling diagram according to at least one embodiment. Referring to Figure 5A, in step 502, UE 122 may send an SL discovery message indicating the availability of the absolute location of UE 122. For example, this message may be received by UE 120 (e.g., target UE 120).

In an example embodiment, the SL discovery message includes a location status information element indicating the availability of the absolute location of UE 122. The location status information element can be, for example, a flag or bit indicator. For instance, the location status information element could be referred to as statusLUE, where a value of statusLUE equal to 1 indicates the availability of the absolute location of UE 122. For example, the signaling in step 502 can be sent based at least on the absolute location information being available to UE 122 or stored at a network node (e.g., at LME 250).

In this embodiment, UE 122 is configured to determine whether absolute location information is available to UE 122. Based on the determination that the absolute location information is available to UE 122, UE 122 can send the SL discovery message of step 502.

In this embodiment, UE 122 is configured to determine whether absolute location information is stored at a network node. Based on the determination that the network node stores the absolute location information, UE 122 can send the SL discovery message of step 502.

Typically, UE 122 can be configured to send an SL discovery message indicating the availability of absolute location information, based at least on whether the absolute location information is available to UE 122 or stored at a network node.

The determination by UE 122 that the absolute location information is available to UE 122 or stored at a network node (e.g., LME 250) may be based on at least one of the following: the absolute location information is stored at the device; the absolute location information is received from the network node; UE 122 obtains an indication from the network node that the absolute location information is stored at the network node; or UE 122 is performing or has performed positioning of UE 122 with the network node (e.g., as explained with respect to Figure 4).

Considering the first scenario, UE 122 can determine whether the absolute location information is available to UE 122 or stored at a network node, based on whether the ALI is stored at UE 122. Therefore, inevitably, the absolute location of UE 122 is available because the ALI indicates the absolute location of UE 122.

Considering the second scenario, UE 122 can determine whether the absolute location information is available to UE 122 or stored at a network node based on the ALI received from LME 250. For example, the ALI can be received from LME 250 in step 408 of Figure 4.

In the third scenario, UE 122 can determine whether the absolute location information is available to UE 122 or stored at the network node based on the indication received from LME 250 and stored at LME 250 by ALI.

The fourth scenario could be that UE 122 determines, based on its location, that its absolute location information is available (i.e., stored) or at least will be available to LME 250, where location involves LME 250. For example, based on a location session with LME 250 as shown in Figure 4, UE 122 can determine that LME 250 knows the absolute location of UE 122, even if the absolute location is not necessarily shared with UE 122 (as in step 408).

UE 122 can use a combination of different conditions to determine whether the absolute location of UE 122 is available (i.e., ALI stored at UE 122 or at the network node).

Referring to Figure 5A, the validity of an ALI can expire, as shown in Figure 504. For example, an ALI may be considered valid for a period of time, after which it may become invalid. Examples of such timers could be a TimeToLive counter or a maximum duration timer that can be reset after each UE 122 positioning event. Thus, for example, an ALI can be determined to be invalid after a certain amount of time has elapsed since it was obtained (e.g., a timer that was started when the ALI was obtained has expired). For example, such a timer can be started and/or reset (i.e., started from a configured value) based on receiving an ALI from the LME 250 (e.g., as in step 408).

In another example, the validity of an ALI may expire based on mobility events such as acceleration, timing advance changes, handover, and/or changes in the reference signal (such as the Received Reference Signal Power (RSRP)). That is, the ALI may become invalid, meaning it is no longer valid or was previously considered valid. For example, UE 122 could detect a mobility event and determine that the ALI is no longer valid based on it.

In another example, the validity of an ALI can expire based on receiving a message or command from a network node (e.g., LME 250). For instance, LME 250 can indicate that the ALI is no longer valid.

Furthermore, UE 122 can indicate to LME 250 whether the ALI has become invalid based on, for example, the expiration of a timer or the detection of a mobility event as described above. Such an indication can be made by UE 122 sending a message to LME indicating that the ALI is invalid. For example, this could enable LME 250 to start a new location session to locate UE 122, allowing it to continue operating as an anchor UE.

Based on the invalidity or invalidation of the absolute location information, UE 122 may generate and transmit a discovery message indicating that the location information is unavailable (step 506). In another embodiment, UE 122 may simply stop sending the message of step 502 without sending message 506.

As discussed herein, the discovery message (e.g., in step 502) could be an SL discovery message broadcast by UE 122. Therefore, this message could be received by one or more UEs, such as UE 120. Thus, UE 120 could determine whether the absolute location of UE 122 is available.

Figure 5B illustrates an embodiment where the SL discovery message includes absolute location information and/or an indication of the network node storing the absolute location information. Therefore, the SL discovery message sent in step 512 may include, for example, a location status information element indicating the availability of the absolute location of UE 122, along with additional ALI and/or network node indications. Thus, the SL discovery message itself can be used to transmit location information (i.e., ALI or an indication of the network node storing the ALI). This offers the benefit of potentially eliminating the need for additional signaling between UE 122 and UE 120. However, UE 120 may request an updated ALI from UE 122 or an update of the ALI at a later stage (e.g., after a certain period of time). Therefore, the validity of the ALI can be maintained.

In this embodiment, one or more CKs are used to encrypt location information.

For example, the location status information element could be an SLPP meta field indicating the localization status of UE 122 (e.g., in the form of an elevated binary flag). Furthermore, the SLPP field could carry UE 122 location information encrypted with a CK. In this way, other UEs possessing the CK (e.g., a self-localization target UE or a server UE) could use UE 122 as an anchor UE for absolute localization purposes. Once the validity of the LUE location expires (e.g., based on a fixed timer or under UE 122 mobility), the localization status can be set to reflect the non-LUE status, meaning availability only for relative localization (e.g., ranging). See, for example, step 506 in Figure 5A.

Furthermore, in some examples, providing UE 120 with an ALI and indication of the network node (via a discovery message or some other signaling/message) may be beneficial, as it allows UE 120 to quickly obtain the absolute location of UE 122, but also allows UE 120 to request an ALI from the indicated network node, for example, after the validity of the initially provided ALI has expired. That is, the ALI at the network node may have already been updated based on a further or continued location session of UE 122 that includes the indicated network node (e.g., LME 250).

In this embodiment, the SL discovery message includes absolute location information and/or an indication of the network node storing the absolute location information, but does not include a location status information element. Therefore, the ALI or the indication of the network node in the SL discovery message can implicitly indicate the location status of UE 122 (i.e., the location of the UE or the absolute location of UE 122 is available).

In an embodiment, an SL discovery message, such as the SL discovery message in step 512, is sent based on (e.g., in response to) an SL discovery message received from (i.e., sent by) UE 120. For example, an SL discovery message received from UE 120 may request an indication of the location status of UE 122 (or any other UE receiving the message). Therefore, UE 122 can respond by sending the discovery message of step 512. For clarity, the SL discovery message sent by UE 120 may be referred to herein as an SL discovery request. However, it may be an SL discovery message used to request the location status of UE 122.

In another embodiment, an SL discovery message, such as in step 512, is sent without a request from UE 120. For example, SL discovery messages can be sent periodically. Periodic transmission can be initiated based on meeting one or more criteria.

For example, UE 122 may begin sending an SL discovery message indicating the availability of absolute location information (with or without the location information shown in Figure 5B) based on at least one of the following: receiving a request from a network node (e.g., LME 520) indicating the availability of absolute location information (see, for example, step 408 in Figure 4); receiving an SL discovery request indicating whether absolute location information is available (see, for example, step 522 in Figure 5C); completing the positioning of UE 122 (see, for example, Figure 4 where UE 122 is located); starting as or determining to start acting as an anchor UE for absolute positioning; or determining that UE 122 is or will act as an anchor UE for absolute positioning. Any of the described criteria may be used alone or in combination with any other criteria in the criteria as a trigger for starting to broadcast an SL discovery message indicating the availability of absolute location. Thus, for example, UE 122 may be configured to begin sending an SL discovery message based on satisfying both of the following conditions: receiving a request from LME 250 and receiving a request from UE 120. On the other hand, UE 122 may be configured to begin sending an SL discovery message based on satisfying only one of the criteria. Additionally, as mentioned above, in order to indicate that the absolute location is available, the absolute location should be available directly from UE 122 or from the network node storing the ALI.

In this embodiment, UE 122 is configured to generate a location information message that includes absolute location information and/or an indication of a network node storing absolute location information; and to send the location information message to UE 120. The location information message may be separate from the SL discovery message. For example, the location information message may be encrypted using one or more CKs. For example, this might mean that the absolute location information and/or indication of the network node are encrypted.

In this embodiment, UE 120 is configured to receive location information messages. If the content is encrypted, UE 120 can decrypt the location information messages to obtain absolute location information and/or indication of network nodes.

In one embodiment, UE 122 is configured to transmit a location information message based on a location information request for absolute location information received from UE 120. In the example, the location information message is sent in response to receiving the request. Therefore, UE 120 can be configured to generate a location information request for absolute location information. For example, the location information request can be generated and/or sent based on an SL discovery message indicating the availability of absolute location information received from UE 122 (e.g., in step 502 of FIG. 5A). For example, the location information request can be encrypted (or encrypted) using one or more CKs shared between UE 120 and UE 122 (e.g., as shown in FIG. 4). However, the main benefit of encryption can be hiding the location information from harmful entities (e.g., ALI), and therefore even if the location information is encrypted, other message transmissions may not be encrypted at all. However, this can depend on the implementation.

Figure 5C illustrates a signaling diagram according to at least one embodiment, wherein location information is requested by UE 122 and provided to UE 120. Referring to Figure 5C, in step 522, UE 120 may use an SL discovery request to request UE 122 (and possibly other UEs) to indicate whether an absolute location is available. UE 120 may generate the request before sending the SL discovery request.

In this example, the absolute location of UE 122 is available, so UE 122 can respond by sending an SL discovery message indicating that the absolute location information is available (e.g., start sending) (step 524). In this example, the SL discovery message may not include an indication of the ALI or the network node storing the ALI.

UE 120 may receive the discovery message sent in step 524, and based on receiving the SL discovery message, request absolute location information on UE 122 by sending a location information request to UE 122 (step 528). For example, a location information request may be generated and/or sent based on receiving an SL discovery message from UE 122 indicating that absolute location information is available (e.g., as in step 502 of FIG. 5A or step 524 of FIG. 5C).

UE 122 can receive a location information request and, based on the location information request, send a location information message to UE 120 including an indication of the ALI and/or a network node (e.g., an identifier of the network node) (step 530). Therefore, UE 120 can obtain the ALI on UE 122, or at least determine the network node from which it can request the ALI.

In one embodiment, the location information request is a capability request message, such as a requestCapability message. Therefore, the location information message can be a capability indication message, such as provideCapability. Other delivery methods are possible, such as via an auxiliary data format and/or via RRC.

In an embodiment, the SL discovery message indicating that the absolute location of UE 122 is available (i.e., the absolute location information (ALI) is available) includes a validity indicator indicating the time period during which the absolute location is valid. For example, the SL discovery message may indicate that the absolute location information is valid at a certain time or within a certain time period. Alternatively, as described above, the SL discovery message may simply include a timestamp indicating the time when the absolute location was obtained. In this case, the timestamp can be understood as a validity indicator. Based on such information, UE 120 can determine whether to request location information from UE 122, for example, as in step 528. Even expired location information can still be used for retrospective positioning, for example, as part of a continuous positioning tracking process. However, such a decision can be left to the implementation, as it can depend on the circumstances of UE 120.

In the embodiments, Figures 5B and 5C can be understood as illustrating cases where the ALI is stored at UE 122 and can therefore be provided directly to UE 120 via SL discovery message 512 or via location information message 530. This may be advantageous, for example, when at least one of UEs 120 or 122 is not connected to a cellular network (e.g., in a tunnel or some network interference) or more specifically connected to LME 250 (e.g., LMF). Figures 6A and 6B illustrate example embodiments where the ALI is stored at a network node (i.e., LME 250) and therefore an indication of LME 250 can be provided to UE 120 by UE 122.

Referring first to Figure 6A, in step 602, UE 120 can send an SL discovery request for absolute location information to UE 122.

In step 604, UE 122 may respond by sending an SL discovery message indicating that the absolute location is available and also including an indication of LME 250. As mentioned above, one example of such an indication is an identifier of LME 250. Another example could be an indication of the default LME.

UE 120 can obtain an indication of the LME storing absolute location information based on receiving the SL discovery message (step 604).

In step 606, UE 120 can request absolute location information from LME 250. The location information request in step 606 can be generated and/or sent based on SL discovery message 604.

LME 250 can receive the request and send a location information message to UE 120 based on the request (step 608). UE 120 can receive the location information message. As previously mentioned, at least in some examples, the location information message can be encrypted. In the case where the location information message is sent by LME 250, it includes the ALI (instead of an indication from LME 250). Therefore, in step 608, LME 250 can send the ALI from UE 122 to UE 120.

Referring then to Figure 6B, the discovery request in step 612 can correspond to the discovery request in step 602 of Figure 6A. However, instead of indicating the LME in the discovery message (or discovery response) in step 614, the discovery message can only indicate that the absolute location is available. Therefore, UE 120 can transmit a location information request to UE 122 in step 616 to request the ALI on UE 122.

When the ALI is stored at LME 250 instead of UE 122, the UE can respond by sending a location information message indicating LME 250 (step 618). Therefore, UE 120 can determine the network node from which it can request the ALI (i.e., LME 250 in the example). Therefore, step 622 can correspond to step 606 of FIG. 6A, and step 624 can correspond to step 608 of FIG. 6A.

Figure 6C illustrates yet another signaling diagram according to at least one embodiment. Referring to Figure 6C, in step 632, LME 250 may instruct UE 122 to stop providing absolute location information. This may mean that UE 122 deactivates its state as an LUE (step 634). Thus, for example, UE 122 may stop sending SL discovery messages indicating that absolute location is available and/or begin sending SL discovery messages indicating that absolute location information is unavailable.

Typically, if the absolute location is unavailable or invalid, UE 122 can generate an SL discovery message indicating that the absolute location information is unavailable; and based on the unavailability or invalidity of the absolute location information, send the other SL discovery message. For example, UE 122 can determine that the absolute location information is no longer valid or available based on a timer expiration or a message received from LME 250 (e.g., step 632); and based on this determination, send an SL discovery message indicating that the absolute location information is unavailable. For example, this SL discovery message can be received by one or more UEs, such as UE 120.

In the example of Figure 6C, another UE 690 requests location information about UE 122 from LME 250 (step 636). However, since UE 122 has been deactivated and is no longer an LUE, LME 250 can provide information about other anchor UEs (candidates) of UE 690. Therefore, UE 690 can request absolute location information about other anchor UE candidates.

Therefore, for example, once LUE 122 is no longer needed as an anchor (e.g., all absolute positioning sessions in the area end), LME 250 can explicitly instruct the LUE to stop advertising the LUE state (step 632). If any other UE (e.g., UE 690) simultaneously requests information about the location of LUE 122, the request can be rejected or a "null" response can be provided to indicate the LUE state. In other embodiments, alternative anchor LUEs with known location states can be provided to the target UE 690 to assist in its positioning.

Figure 7 illustrates at least one embodiment. Referring to Figure 7, the actions of UE 122 can be summarized in terms of sending an SL discovery message indicating whether an absolute location is available.

In step 702, UE 122 may determine whether the absolute location of UE 122 is known and valid. If so, UE 122 may advertise itself as LUE (i.e., the located UE) by sending, for example, an SL discovery message indicating that the absolute location is available (box 704).

If not true, then UE 122 can determine (step 712) whether the absolute location of UE 122 is known by another network node and whether the absolute location is valid. If yes (i.e., a valid absolute location is known), then the process can continue to box 704.

If not true, UE 122 can stop advertising itself as a located UE, preventing itself from advertising itself as a located UE or as an unlocated UE. This means that UE 122 can be used for relative positioning, but not for absolute positioning of UE 120 or some other target UE (box 714).

For example, the process can continue to box 702 again, and therefore can be repeated.

For example, UE 120 (although not shown in Figure 7) can receive an SL discovery message indicating that absolute location information is unavailable, and thus require different UEs to support its location in the future.

The embodiment shown in FIG8 provides an apparatus 10 including a control circuit (CTRL) 12, such as at least one processor, and at least one memory 14 storing instructions (INSTRUCT.) that, when executed by the at least one processor, cause the apparatus to perform at least any of the aforementioned processes. In the example, the at least one memory and the instructions are configured, together with the at least one processor, to cause the apparatus to perform any of the aforementioned processes. The memory can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The memory may include a database for storing data.

In embodiments, device 10 includes a terminal device of a communication system, such as a user terminal (UT), computer (PC), laptop computer, tablet computer, cellular phone, mobile phone, communicator, smartphone, handheld computer, mobile transportation equipment (e.g., automobile), home appliance, or any other communication device, generally referred to as UE in the specification. Alternatively, the device may be included in such a terminal device. Furthermore, the device may be or include (to be attached to the UE) a module providing connectivity, such as a plug-in unit, a "USB dongle," or any other type of unit. This unit may be installed inside the UE or attached to the UE via a connector or even wirelessly.

In this embodiment, device 10 is or is included in UE 122. The device may be able to perform some functions of the above-described process, such as steps 302, 304, and 306 of FIG. 3A.

The device 10 may also include a wireless interface (TRX) 16, which includes hardware and/or software for establishing a communication connection according to one or more communication protocols. For example, the TRX can provide the device with the communication capability to access a wireless access network. For example, the TRX can enable SL communication.

The device may also include a user interface 18, which may include, for example, at least one keypad, microphone, touch display, display, speaker, etc. The user interface can be used to control the device by a user.

In an embodiment, the control circuit 12 includes a generation circuit 20 for performing at least step 302 of FIG. 3A; a transmission circuit 22 for performing at least step 304 of FIG. 3A; and an indication circuit 24 for performing at least step 306 of FIG. 3A.

The embodiment shown in FIG9 provides an apparatus 50 including control circuitry (CTRL) 52 (such as at least one processor) and at least one memory 54 storing instructions (INSTRUCT.) that, when executed by the at least one processor, cause the apparatus to perform at least any of the aforementioned processes. In the example, at least one memory and instructions are configured, together with at least one processor, to cause the apparatus to perform any of the aforementioned processes. The memory can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The memory may include a database for storing data.

In an embodiment, device 50 includes a terminal device of a communication system, such as a user terminal (UT), computer (PC), laptop computer, tablet computer, cellular phone, mobile phone, communicator, smartphone, handheld computer, mobile transportation equipment (e.g., automobile), home appliance, or any other communication device, generally referred to as UE in the specification. Alternatively, the device may be included in such a terminal device. Furthermore, the device may be or include (to be attached to the UE) a module providing connectivity, such as a plug-in unit, a "USB dongle," or any other type of unit. This unit may be installed inside the UE or attached to the UE via a connector or even wirelessly.

In this embodiment, device 50 is or is included in UE 120. The device may be able to perform some functions of the above-described process, such as steps 312, 314, and 316 of FIG. 3B.

The device 50 may also include a radio interface (TRX) 56, which includes hardware and/or software for establishing a communication connection according to one or more communication protocols. For example, the TRX can provide the device with the communication capability to access a wireless access network. For example, the TRX can enable SL communication.

Device 50 may also include a user interface 58, which may include, for example, at least one keypad, microphone, touch display, display, speaker, etc. The user interface can be used to control the device by a user.

In an embodiment, the control circuit 52 includes a receiving circuit 60 for performing at least step 312 of FIG. 3B; an acquiring circuit 62 for performing at least step 314 of FIG. 3B; and an exploitation circuit 64 for performing at least step 316 of FIG. 3B.

According to one aspect, an apparatus is provided, comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: obtain absolute location information indicating the absolute location of a first terminal device (e.g., UE 122); and request the first terminal device to send an SL discovery message indicating the availability of the absolute location information, based on a request or based on another request via a second terminal device (e.g., UE 120). For example, the apparatus may be an LME 250 or included in an LME 250, such as an LMF or a server UE.

Additionally, the device can be configured to provide absolute location information to the first terminal device as described above (e.g., in step 408).

Additionally, the device can be configured to provide absolute location information to a second terminal device based on (e.g., according to) a request from the second terminal device (e.g., as in steps 606/608 and/or 622/624).

In one embodiment, an apparatus for performing at least some embodiments of the embodiments includes at least one processor and at least one memory including instructions, which, when executed by the at least one processor, cause the apparatus to perform a function according to any one of the embodiments. According to one aspect, when the at least one processor executes the instructions, the instructions cause the apparatus to perform a function according to any one of the described embodiments. According to another embodiment, the apparatus for performing at least some embodiments includes at least one processor and at least one memory including instructions, wherein the at least one processor and the instructions perform at least some functions according to any one of the described embodiments. Thus, at least one processor, memory, and instructions form a processing apparatus for performing at least some embodiments of the described embodiments. According to yet another embodiment, the apparatus for performing at least some embodiments includes circuitry including at least one processor and at least one memory including instructions. When activated, the circuitry causes the apparatus to perform at least some functions according to any one of the described embodiments.

As used herein, the term "circuit" means all of the following: (a) a circuit implementation that is only hardware, such as an implementation in analog and/or digital circuits only; and (b) a combination of circuits and software (and/or firmware), such as (where applicable): (i) a combination of processors or (ii) a portion of processor/software, including a digital signal processor, software, and memory, which work together to enable a device to perform various functions; and (c) a circuit, such as a microprocessor or a portion of a microprocessor, which requires software or firmware to operate, even if the software or firmware is not physically present. This definition of "circuit" applies to all uses of the term in this application. As another example, as used herein, the term "circuit" will also cover only an implementation of a processor (or a plurality of processors) or a portion of a processor and its (or its) accompanying software and/or firmware. The term "circuit" will also cover, for example and if applicable, baseband integrated circuits or application processor integrated circuits for mobile phones or similar integrated circuits in servers, cellular network devices, or other network devices.

In one embodiment, at least some of the processes described may be performed by a device including corresponding means for performing at least some of the processes described. Some example means for performing the processes may include at least one of the following: a detector, a processor (including dual-core and multi-core processors), a digital signal processor, a controller, a receiver, a transmitter, an encoder, a decoder, a memory, RAM, ROM, software, firmware, a display, a user interface, a display circuit system, a user interface circuit system, user interface software, display software, a circuit, an antenna, an antenna circuit system, and a circuit system.

As used herein, the term nontransitory refers to the limitation of the medium itself (i.e., tangible rather than signaling), rather than the limitation of the persistence of data storage (e.g., RAM versus ROM).

As used herein, the term “apparatus” should be interpreted in the singular form, referring to a single element, or in the plural form, referring to a combination of single elements. Therefore, the term “apparatus for [performing A, B, C]” will be interpreted to encompass devices in which only one apparatus exists for performing A, B, and C, or in which separate apparatuses exist for performing A, B, and C, or apparatuses for performing A, B, and C partially or completely overlap.

The techniques and methods described herein can be implemented in various ways. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For hardware implementations, the devices of the embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or combinations thereof. For firmware or software, the implementation may be performed by a module of at least one chipset (e.g., processes, functions, etc.) that performs the functions described herein. Software code may be stored in memory cells and executed by a processor. Memory cells may be implemented within or outside the processor. In the latter case, it may be communicatively coupled to the processor via various means known in the art. Furthermore, the components of the systems described herein may be rearranged and/or supplemented by additional components to facilitate the implementation of various aspects of the description, etc., and they are not limited to the precise configurations illustrated in the given figures, as will be understood by those skilled in the art.

The described embodiments can also be performed as a computer process defined by a computer program or parts thereof. Embodiments of the described methods can be performed by executing at least a portion of a computer program including corresponding instructions. The computer program can be in source code form, object code form, or some intermediate form, and it can be stored in some kind of carrier, which can be any entity or device capable of carrying the program. For example, the computer program can be stored on a computer or processor-readable computer program distribution medium. The computer program medium can be, for example, but not limited to, recording media, computer memory, read-only memory, electrical carrier signals, telecommunication signals, and software distribution packages. The computer program medium can be a non-transitory medium. The coding of the software used to perform the illustrated and described embodiments is entirely within the scope of those skilled in the art.

Example:

Example 1: An apparatus comprising: at least one processor; and

At least one memory storing instructions, which, when executed by at least one processor, cause the device to at least: generate a sidelink SL discovery message, the SL discovery message indicating that absolute location information is available, the absolute location information indicating the absolute location of the device; send the SL discovery message to at least a terminal device; and indicate to the terminal device at least one of the following: absolute location information or a network node storing absolute location information.

Example 2: The apparatus of Example 1, wherein the SL discovery message includes at least one of the following: absolute location information or an indication of a network node storing absolute location information.

Example 3: The device of Example 1 or 2, wherein the SL discovery message includes a location status information element indicating the availability of the absolute location of the device.

Example 4: The apparatus according to any one of Examples 1 to 3 is made to perform: generating a location information message, the location information message including at least one of the following: absolute location information or an indication of a network node storing absolute location information; and sending the location information message to a terminal device.

Example 5: The apparatus of Example 4 is made to perform: receiving a location information request for absolute location information, wherein a location information message is generated based on receiving the location information request.

Example 6: The apparatus according to any one of Examples 1 to 5 is made to perform: receiving an SL discovery request indicating whether absolute location information is available, wherein sending an SL discovery message indicating that absolute location information is available is based on receiving the SL discovery request.

Example 7: An apparatus of any one of Examples 1 to 6, wherein, based at least on absolute location information available to the apparatus or stored at the network node, the apparatus is made to send the SL discovery message indicating that the absolute location information is available.

Example 8: According to the apparatus of Example 7, the following is performed: determining that absolute location information is available to the apparatus or is stored at a network node based on at least one of the following: the absolute location information is stored at the apparatus; the absolute location information is received from the network node; an indication is obtained from the network node that the absolute location information is stored at the network node; or the apparatus is performing or has performed positioning of the apparatus with the network node.

Example 9: An apparatus of any one of Examples 1 to 8, wherein the apparatus is configured to begin sending an SL discovery message indicating the availability of absolute location information based on at least one of the following: obtaining a request from a network node to indicate that the absolute location information is available; receiving an SL discovery request to indicate whether the absolute location information is available; the apparatus has completed positioning; begins to act as or determines to begin acting as an anchor UE for absolute positioning; or determines that the apparatus is acting as or will act as an anchor UE for absolute positioning.

Example 10: A device of any of Examples 1 to 9 is made to perform: obtain absolute location information on the device from a network node and request to indicate that the absolute location information is available by broadcasting an SL discovery message.

Example 11: A device of any of Examples 1 to 10, wherein the SL discovery message also indicates that the absolute location information is valid for a specific period of time.

Example 12: An apparatus of any one of Examples 1 to 11 is made to: generate another SL discovery message indicating that the absolute location information is unavailable; and, based on the fact that the absolute location information is unavailable or invalid, send the other SL discovery message to at least a terminal device.

Example 13: The apparatus of Example 12 is made to perform: determining, based on the expiration of a timer or a message received from a network node, that the absolute location information is no longer valid; and based on this determination, sending at least the other SL discovery message to the terminal device.

Example 14: An apparatus comprising: at least one processor; and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: receive a sidelink SL discovery message from an end device, the SL discovery message indicating that absolute location information is available, the absolute location information indicating the absolute location of the end device; obtain from the end device at least one of the following: absolute location information or an indication of a network node storing the absolute location information; and determine the location of the apparatus using at least one of the following: the absolute location information or the indication of a network node storing the absolute location information.

Example 15: The apparatus of Example 14, wherein the SL discovery message includes at least one of the following: absolute location information or an indication of a network node storing absolute location information.

Example 16: The apparatus of Example 14 or 15, wherein the SL discovery message includes a location status information element indicating that the absolute location of the terminal device is available.

Example 17: An apparatus of any one of Examples 14 to 16 is made to perform: receiving a location information message from a terminal device, the location information message including at least one of the following: absolute location information or an indication of a network node storing absolute location information.

Example 18: The apparatus of any one of Examples 14 to 17 is made to: generate a location information request for absolute location information based on receiving an SL discovery message indicating that absolute location information is available; and send the location information request to a terminal device.

Example 19: An apparatus of any one of Examples 14 to 18 is made to perform: generate an SL discovery request indicating whether absolute location information is available; and at least send the generated SL discovery request to a terminal device.

Example 20: An apparatus of any one of Examples 14 to 19 is made to perform: obtaining an instruction from a terminal device of a network node storing absolute location information; requesting absolute location information from the network node; and receiving absolute location information from the network node.

Example 21: An apparatus of any of Examples 14 to 20, wherein the received SL discovery message also indicates that the absolute location information is valid for a specific time.

Example 22: The apparatus of any of Examples 14 to 21 is made to perform: receive from the terminal device another SL discovery message indicating that absolute location information is unavailable.

Example 23: An apparatus comprising: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: obtain absolute location information indicating the absolute location of a first terminal device; and request the first terminal device to send an SL discovery message indicating the availability of the absolute location information based on a request or based on another request via a second terminal device.

Example 24: A method comprising: generating a sidelink SL discovery message by a device, the SL discovery message indicating that absolute location information is available, the absolute location information indicating the absolute location of the device; sending the SL discovery message to at least an end device; and indicating to the end device at least one of the following: absolute location information or a network node storing absolute location information.

Example 25: A method comprising: receiving a sidelink SL discovery message from a terminal device by a device, the SL discovery message indicating that absolute location information is available, the absolute location information indicating the absolute location of the terminal device; obtaining from the terminal device at least one of the following: absolute location information or an indication of a network node storing the absolute location information; and determining the location of the device using at least one of the following: the absolute location information or the indication of a network node storing the absolute location information.

Example 26: A method comprising: obtaining absolute location information indicating the absolute location of a first terminal device by means of a device; and requesting the first terminal device to send an SL discovery message indicating that the absolute location information is available, based on a request or based on another request via a second terminal device.

Example 27: A computer program product including program instructions that, when loaded into a device, perform the method of any one of Examples 24 to 26.

Although the invention has been described above with reference to examples in conjunction with the accompanying drawings, it is apparent that the invention is not limited thereto, but may be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the embodiments. It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways as technology advances. Furthermore, it will be clear to those skilled in the art that the described embodiments can, but are not required to, be combined with other embodiments in various ways.

Claims (27)

1. An apparatus, comprising:

At least one processor, and

At least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:

Generating a side link SL discovery message, said SL discovery message indicating that absolute location information is available, said absolute location information indicating an absolute location of a device;

Transmitting at least the SL discovery message to a terminal device, and

At least one of the absolute location information or a network node storing the absolute location information is indicated to the terminal device.

2. The apparatus of claim 1, wherein the SL discovery message includes at least one of the absolute location information or an indication of the network node storing the absolute location information.

3. The apparatus according to claim 1 or 2, wherein the SL discovery message comprises a location status information element indicating that the absolute location of the apparatus is available.

4. The apparatus of any of the preceding claims, caused to perform:

generating a location information message comprising at least one of the absolute location information or the indication of the network node storing the absolute location information, and

And sending the position information message to the terminal equipment.

5. The apparatus of claim 4, caused to perform:

Receiving a location information request for the absolute location information;

Wherein generating the location information message is based on receiving the location information request.

6. The apparatus of any of the preceding claims, caused to perform:

a SL discovery request for indicating whether the absolute location information is available is received,

Wherein sending the SL discovery message indicating that the absolute location information is available is based on receiving the SL discovery request.

7. An apparatus according to any of the preceding claims, wherein the apparatus is caused to send the SL discovery message indicating that the absolute location information is available based at least on the absolute location information being available to the apparatus or stored at the network node.

8. The apparatus of claim 7, caused to perform:

Determining that the absolute location information is available to the apparatus or stored at the network node based on at least one of:

the absolute position information is stored at the device;

The absolute location information is received from the network node;

obtaining an indication from the network node that the absolute location information is stored at the network node, or

The apparatus is performing or has performed a positioning of the apparatus with the network node.

9. An apparatus according to any one of the preceding claims, wherein the apparatus is caused to start sending the SL discovery message indicating that the absolute location information is available based on at least one of:

obtaining a request from the network node indicating that the absolute location information is available;

Receiving a SL discovery request for indicating whether the absolute location information is available;

positioning of the device is completed;

start to act as or determine to start to act as anchor UE for absolute positioning, or

It is determined that the device is or is about to act as an anchor UE for absolute positioning.

10. The apparatus of any of the preceding claims, caused to perform:

obtaining the absolute location information on the device from the network node, and indicating a request that the absolute location information is available by broadcasting the SL discovery message.

11. The apparatus according to any of the preceding claims, wherein the SL discovery message further indicates that the absolute location information is valid for a specific time.

12. The apparatus of any preceding claim, caused to perform:

generating another SL discovery message indicating that the absolute location information is unavailable, and

The further SL discovery message is sent at least to the terminal device based on whether the absolute location information is unavailable or invalid.

13. The apparatus of claim 12, caused to perform:

determining that the absolute location information is no longer valid based on expiration of a timer or a message received from the network node, and

Based on the determination, at least the further SL discovery message is sent to the terminal device.

14. An apparatus, comprising:

At least one processor, and

At least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:

Receiving a side link SL discovery message from a terminal device, said SL discovery message indicating that absolute location information is available, said absolute location information indicating an absolute location of said terminal device;

obtaining from the terminal device at least one of the absolute location information or an indication of a network node storing the absolute location information, and

The location of the device is determined using at least one of the absolute location information or the indication of the network node storing the absolute location information.

15. The apparatus of claim 14, wherein the SL discovery message includes at least one of the absolute location information or the indication of the network node storing the absolute location information.

16. The apparatus according to claim 14 or 15, wherein the SL discovery message comprises a location status information element indicating that the absolute location of the terminal device is available.

17. The apparatus of any of claims 14 to 16, caused to perform:

A location information message is received from the terminal device, the location information message comprising at least one of the absolute location information or the indication of the network node storing the absolute location information.

18. The apparatus of any of claims 14 to 17, caused to perform:

generating a location information request for the absolute location information based on receiving the SL discovery message indicating that the absolute location information is available, and

And sending the position information request to the terminal equipment.

19. The apparatus of any of claims 14 to 18, caused to perform:

Generating a SL discovery request for indicating whether absolute location information is available, and

And sending the generated SL discovery request to at least the terminal equipment.

20. The apparatus of any of claims 14 to 19, caused to perform:

Obtaining from the terminal device the indication of the network node storing the absolute location information;

Requesting the absolute location information from the network node, and

The absolute location information is received from the network node.

21. The apparatus according to any of claims 14 to 20, wherein the SL discovery message received further indicates that the absolute location information is valid for a particular time.

22. The apparatus of any of claims 14 to 21, caused to perform:

Another SL discovery message indicating that the absolute location information is not available is received from the terminal device.

23. An apparatus, comprising:

At least one processor, and

At least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:

Obtaining absolute position information indicating an absolute position of the first terminal device, and

Requesting the first terminal device to send a SL discovery message indicating that the absolute location information is available, based on the request or based on another request via the second terminal device.

24. A method, comprising:

generating, by an apparatus, a side link SL discovery message indicating that the absolute location information is available, the absolute location information indicating an absolute location of the apparatus;

Transmitting at least the SL discovery message to a terminal device, and

At least one of the absolute location information or a network node storing the absolute location information is indicated to the terminal device.

25. A method, comprising:

Receiving, by an apparatus, a side link SL discovery message from a terminal device, the SL discovery message indicating that absolute location information is available, the absolute location information indicating an absolute location of the terminal device;

obtaining from the terminal device at least one of the absolute location information or an indication of a network node storing the absolute location information, and

The location of the device is determined using at least one of the absolute location information or the indication of the network node storing the absolute location information.

26. A method, comprising:

Obtaining absolute position information indicating an absolute position of the first terminal device, and

Requesting the first terminal device to send a SL discovery message indicating that the absolute location information is available, based on the request or based on another request via the second terminal device.

27. A computer program product comprising program instructions which, when loaded into an apparatus, perform the method of any of claims 24 to 26.