Coordinate reference system handling in a communication network

Abstract

A communication node (12A) is disclosed. The communication node (12A) transmits signaling (16-1) to, and / or receives signaling (16-2) from, another communication node (12B) regarding which coordinate reference system, CRS (18), and / or which CRS transformation (18T) to use for location coordinates (14) communicated between the communication nodes (12A, 12B). The communication node (12A) also communicates location coordinates (14) between the communication nodes (12A, 12B) according to the transmitted signaling (16-1) and / or the received signaling (16-2).

Description

[0001] COORDINATE REFERENCE SYSTEM HANDLING IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present application relates generally to a communication network, and relates more particularly to coordinate reference system handling in such a network.

[0004] BACKGROUND

[0005] A coordinate reference system (CRS) is a system usable to represent location coordinates, e.g., geodetic, projected, and / or vertical coordinates. A CRS in this regard may consist of a datum, a coordinate system, and optionally a projection. The datum defines the shape and size of the Earth, serving as a reference for positioning. It determines the origin and orientation of coordinates. The coordinate system provides a framework for measuring locations within a datum, defining axes, units, and reference points. Common types include geodetic coordinates (latitude, longitude, and height), projected coordinates (X, Y in meters, such as in the Universal Transverse Mercator [UTM] system), and Cartesian coordinates (X, Y, Z in a 3D space, like Earth-Centered, Earth-Fixed [ECEF]). Finally, a projection is used to convert 3D geographic coordinates into a 2D map while minimizing distortions. Generally, then, the datum defines the Earth’s shape, the coordinate system establishes how positions are measured, and the projection determines how those positions are mapped onto a flat surface.

[0006] A communication network heretofore represents all location coordinates in a global CRS known as World Geodetic System (WSG) 1984, also referred to as WSG84. The most recent version of WSG84 is aligned to the International Terrestrial Reference Frame (ITRF) datum. Representing location coordinates in a predefined CRS such as WSG184 has suited sufficiently well for conventional positioning accuracy requirements and positioning capabilities. Challenges exist, however, with how to represent location coordinates in a communication network in a way that keeps pace with tighter positioning accuracy requirements and improved positioning capabilities.

[0007] SUMMARY

[0008] Some embodiments herein introduce signaling between communication nodes regarding which CRS to use for location coordinates communicated between the communication nodes. Rather than the CRS for location coordinates being statically predefined, then, some embodiments herein introduce signaling that enables the CRS used for communicated location coordinates to be adapted, coordinated, and / or otherwise aligned between communication nodes. The CRS used for location coordinates may for example be selected as whatever CRS is most accurate or appropriate forthose location coordinates, e.g., that most accurately represents a region in which the location coordinates exist. Thus,instead of statically using a global CRS such as WGS84 for all location coordinates, the signaling herein may enable use of whichever national or regional CRS is most appropriate or accurate for the location coordinates being communicated. These and other embodiments herein may therefore advantageously represent location coordinates in a communication network in a way that keeps pace with tighter positioning accuracy requirements and improved positioning capabilities.

[0009] More particularly, embodiments herein include a method performed by a communication node. The method comprises transmitting signaling to, and / or receiving signaling from, another communication node regarding which coordinate reference system (CRS), and / or which CRS transformation, to use for location coordinates communicated between the communication nodes. In some embodiments, the method further comprises communicating location coordinates between the communication nodes according to the transmitted signaling and / or the received signaling.

[0010] Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.

[0011] BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a block diagram of communication nodes according to some embodiments.

[0013] Figure 2 is a block diagram of an exemplary information request / response procedure for communicating location coordinates or for preparing for communication of the location coordinates according to some embodiments.

[0014] Figure 3 is a block diagram of an exemplary information request / response procedure for communicating location coordinates or for preparing for communication of the location coordinates according to other embodiments.

[0015] Figure 4 is a block diagram of different possible forms of the communication nodes according to some embodiments.

[0016] Figure 5 is a block diagram of the positioning architecture in a 3GPP-based communication network according to some embodiments.

[0017] Figure 6 is a block diagram of the different 4G / LTE / EPC and 5G / NR / 5GC entities in the more complete and common architecture according to some embodiments.

[0018] Figure 7 is a block diagram of procedures between two nested network functions, or network functions interacting in sequence.

[0019] Figure 8 illustrates a signaling chart according to some embodiments.

[0020] Figure 9 illustrates a flow diagram of a request and response procedure according to some embodiments.Figure 10 illustrates a flow diagram of the exemplary information request / response procedure of Figure 2.

[0021] Figure 11 illustrates a flow diagram of the exemplary information request / response procedure of Figure 2.

[0022] Figure 12 illustrates a flow diagram on a capability request and response procedure according to some embodiments.

[0023] Figure 13 illustrates a flow diagram of the exemplary information request / response procedure of Figure 3.

[0024] Figure 14 illustrates a flow diagram of the exemplary information request / response procedure of Figure 3.

[0025] Figure 15 is a logic flow diagram of a method performed by a communication node in accordance with particular embodiments.

[0026] Figure 16 is a block diagram of a communication node according to some embodiments.

[0027] Figure 17 is a block diagram of a communication system according to some embodiments.

[0028] Figure 18 is a block diagram of a communication system according to other embodiments.

[0029] Figure 19 is a block diagram of a wireless device according to other embodiments Figure 20 is a block diagram of a network node according to other embodiments. Figure 21 is a block diagram of a virtualization environment according to other embodiments.

[0030] DETAILED DESCRIPTION

[0031] Figure 1 shows communication nodes 12A and 12B according to some embodiments, generally referred to as communication nodes 12. Each of the communication nodes 12A, 12B may be configured for use in or with a communication network, e.g., a 3rdGeneration Partnership Project (3GPP) network. Communication node 12A may for example be a communication device (e.g., a user equipment, UE) or a network node such as a radio network node or a core network node. Likewise, communication device 12B may itself be a communication device or a network node such as a radio network node or a core network node.

[0032] According to embodiments herein, the communication nodes 12A, 12B are configured to communicate location coordinates 14 between them. The location coordinates 14 may be transmitted from communication node 12Ato communication node 12B and / or may be transmitted in the other direction from communication node 12B to communication node 12A. Either way, the location coordinates 14 may be part of location information that represents a location of a target device, which may be one of the communication nodes 12A,12B or may be a different node not shown. Alternatively, the location coordinates 14 may be part of assistance data for assistance with determination of such location information.

[0033] No matter the particular nature of and / or purpose for the location coordinates 14, embodiments herein introduce signaling 16 between the communication nodes 12A, 12B. The signaling 16 may include signaling 16-1 transmitted by communication node 12Aand received by communication node 12B. Alternatively or additionally, the signaling 16 may include signaling 16-2 transmitted by communication node 12B and received by communication node 12A.

[0034] The signaling 16 according to some embodiments regards which coordinate reference system (CRS) 18 to use for the location coordinates 14 communicated between the communication nodes 12A, 12B. In some embodiments, for example, different possible CRSs may be usable for location coordinates 14 communicated between the communication nodes 12A, 12B, e.g., including one or more global CRSs and / or one or more national or regional CRSs. The signaling 16 in this case may regard which one of the different possible CRSs to use for the location coordinates 14. In these and other embodiments, the signaling 16 may effectively enable the CRS 18 to be adapted or otherwise tailored to the location coordinates 14 being communicated, while preserving a common understanding or agreement between the communication nodes 12A, 12B about which CRS to use for the location coordinates 14. In fact, the signaling 16 in some embodiments may be part of a procedure between the communication nodes 12A, 12B to negotiate, coordinate, or otherwise align which CRS 18 to use for the location coordinates 14 communicated between the communication nodes 12A, 12B.

[0035] The signaling 16 in other embodiments regards which CRS transformation 18T to use for the location coordinates 14 communicated between the communication nodes 12A, 12B. A CRS transformation 18T here refers to a transformation from one CRS 28 (referred to as a source CRS) to another CRS 18 (referred to as a target CRS). Which CRS transformation 18T to use for the location coordinates 14 may thereby implicate which source CRS to use, which target CRS to use, and / or which parameters and / or values thereof to use for transforming the source CRS into the target CRS. In some embodiments, for example, different possible CRS transformations 18T may be usable for location coordinates 14 communicated between the communication nodes 12A, 12B. The signaling 16 in this case may regard which one of the different possible CRS transformations to use for the location coordinates 14. In these and other embodiments, the signaling 16 may effectively enable the CRS transformation 18T to be adapted or otherwise tailored to the location coordinates 14 being communicated, while preserving a common understanding or agreement between the communication nodes 12A, 12B about which CRS transformation 18T to use for the location coordinates 14. In fact, the signaling 16 in some embodimentsmay be part of a procedure between the communication nodes 12A, 12B to negotiate, coordinate, or otherwise align which CRS transformation 18T to use for the location coordinates 14 communicated between the communication nodes 12A, 12B.

[0036] In some embodiments, the signaling 16-1 and / or the signaling 16-2 may indicate which CRS 18 and / or which CRS transformation 18T to use for the location coordinates 14 communicated between the communication nodes 12A, 12B. The signaling 16-1 and / or signaling 16-2 may for example indicate which CRS 18 and / or which CRS transformation 18T is to be used, is requested to be used, or has been used for the location coordinates 14.

[0037] Figure 2 illustrates one example as part of an information request / response procedure for communicating the location coordinates 14 or for preparing for communication of the location coordinates 14. As shown, communication node 12A transmits an information request 26-1 to communication node 12B. The information request 26-1 requests information from communication node 12B. The requested information may for example be location information or assistance data. Either way, the requested information includes the location coordinates 14. As shown, then, the communication node 12B transmits an information response 26-2 in response to the information request 26-1. In some embodiments, such as where the information request 26-2 requests the location coordinates 14 in a response to the request 26-1, the information response 26-2 may include the location coordinates 14. In other embodiments, though, the information request 26-2 may only request that the information be communicated in the future (e.g., periodically reported), in which case the information response 26-2 may not itself include the location coordinates 14.

[0038] In some embodiments, the information request 16-1 is or includes the signaling 16-1 described in Figure 1. The signaling 16-1 in this case may indicate which CRS 18 is requested to be used for the location coordinates 14.

[0039] Similarly, in some embodiments, the information response 26-2 is or includes the signaling 16-2 described in Figure 2. The signaling 16-2 in this case may indicate which CRS 18 is used, has been used, or will be used for the location coordinates 14. In embodiments where the information request 26-1 includes signaling 16-1 that indicates which CRS 18 is requested to be used for the location coordinates 14, the signaling 16-2 in the information response 26-2 may simply be an acknowledgement that communication node 12B supports, has used, and / or will use the requested CRS 18.

[0040] Alternatively, such as in the case where the communication node 12B does not support the requested CRS 18, the signaling 16-2 in the information response 26-2 may be an error indication indicating that communication node 12B does not support the requested CRS 18. Or, in some embodiments, the signaling 16-2 in the information request 26-2 may be an indication of a different CRS that communication node 12B supports, has used, and / or will use for the location coordinates 14. The different CRS may for instance be a baselineCRS that the signaling 16-1 in the information request 26-1 indicated is to be used (as a fallback position) in case the requested CRS is not supported. Or, the different CRS may be some other CRS, e.g., different than the requested CRS and / or different than the baseline CRS.

[0041] Although illustrated in Figure 2 for the case where the location coordinates 14 are provided in response to a request, the location coordinates 14 may be provided in other embodiments unsolicited without any such request. In this case, the location coordinates 14 may still nonetheless be accompanied by or otherwise associated with signaling 16-2 that indicates which CRS 18 and / or which CRS transformation 18T has been used for the location coordinates 14.

[0042] In other embodiments herein, the signaling 16-1 and / or the signaling 16-2 may indicate which CRS 18 and / or which CRS transformation 18T one or both of the communication nodes 12A, 12B is capable of using for the location coordinates 14 communicated between the communication nodes 12A, 12B. The signaling 16-1 from communication node 12A may for example indicate which CRS 18 and / or which CRS transformation 18T communication node 12A is capable of using, whereas the signaling 16-2 from communication node 12B may indicate which CRS 18 and / or which CRS transformation 18T communication node 12B is capable of using. In these and other embodiments, the signaling 16-1 and / or 16-2 may be communicated as part of a procedure for the communication nodes 12A, 12B to negotiate, agree on, or otherwise align which CRS 18 and / or which CRS transformation 18T to use for the location coordinates 14.

[0043] Figure 3 shows one example. As shown, communication node 12A transmits a capability request 30-1 to communication node 12B. The capability request 30-1 requests capability information 32 from communication node 12B indicating one or more capabilities of the communication node 12B. Communication node 12B in turn transmits a capability response 30-2 in response to the capability request 30-1. The capability response 30-2 includes the requested capability information 32.

[0044] In some embodiments, the capability request 30-1 is or includes the signaling 16-1 described in Figure 1. The capability information 32 requested in this case includes CRS capability information indicating which CRS 18 and / or which CRS transformation 18T communication node 12B is capable of using for location coordinates 14. The signaling 16-1 thereby regards which CRS 18 and / or which CRS transformation 18T to use for the location coordinates 14, in the sense that the signaling 16-1 requests which CRS 18 and / or which CRS transformation 18T is able to be used for the location coordinates 14.

[0045] Alternatively or additionally, the capability response 30-2 is or includes the signaling 16-2 described in Figure 1. The capability response 30-2 in this case includes capability information 32 that in turn includes CRS capability information indicating which CRS 18and / or which CRS transformation 18T communication node 12B is capable of using for location coordinates 14.

[0046] Note that the embodiments in Figure 3 may be implemented separately from or in combination with the embodiments in Figure 2. In some embodiments, for instance, the location coordinates 14 are thereafter communicated between the communication nodes 12A, 12B based on the capability request 30-1 and response 30-2. The CRS 18 and / or CRS transformation 18T used for the location coordinates 14 may for example be based on the CRS capability information, e.g., be a CRS 18 and / or CRS transformation 18T that both communication nodes 12A, 12B support.

[0047] Note also that the signaling 16 described herein may be communicated between any type of communication nodes 12A, 12B. Figure 4 in this regard shows different possible forms of the communication nodes 12A, 12B in Figures 1-3. As shown, a communication network 10 provides communication service to one or more communication devices 12-1, e.g., in the form of one or more user equipment (UE). The communication network 10 in this regard includes one or more radio network nodes 12-2 that provide radio access to the communication network 10 as part of a radio access network. The communication network 10 also includes one or more core network nodes in a core network of the communication network 10. In this context, the signaling 16 herein may be communicated between any of the nodes shown in Figure 4. For example, the signaling 16 may be communicated between two communication devices 12-1, between a communication device 12-1 and a radio network node 12-2, and / or between a communication device 12-1 and a core network node 12-3. Alternatively or additionally, the signaling 16 may be communicated between two radio network nodes 12-2 and / or between a radio network node 12-2 and a core network node 12-3. Alternatively or additionally, the signaling 16 may be communicated between two core network nodes 12-3.

[0048] Alternatively or additionally, a communication node 12A, 12B may be (or implement) a Location Services (LCS) client and / or an Application Function (AF). In such a case, the signaling 16 may be communicated to or from a Location Services (LCS) client and / or to or from an Application Function (AF).

[0049] Consider now some embodiments herein as applicable in the following context where the communication network 10 is based on 3GPP.

[0050] Figure 5 shows the positioning architecture in a 3GPP-based communication network according to some embodiments. The communication nodes 12A, 12B in Figure 1 may be any of the nodes shown in Figure 5.

[0051] Positioning in 4G I Long Term Evolution (LTE) I Evolved Packet Core (EPC) and 5G I New Radio (NR) I 5G Core (5GC) is supported by the architecture in Figure 5, with direct interactions between a UE (100) and a location server (130) via the LTE PositioningProtocol, LPP (171). Moreover, there are also interactions between the location server (130) and the serving radio base station (110) via the network location protocol (172), to some extent supported by interactions between the radio base station (110) and the UE (100) via the Radio Resource Control (RRC) protocol (170). The radio base station (110) interacts with a mobility network entity (120) via a first interface protocol (173), and the mobility network entity (120) interacts with the location server (130) via a second interface protocol (174). The location server also interacts with a location gateway function (140) via a location management protocol (175), either directly as in Figure 5 or via the mobility network entity (120). In the latter case, the network mobility entity (120) will act as an intermediate node in between the location server (130) and the location gateway (140). The location gateway function (140) exposes location information via a first exposure protocol (176) either directly to an application function (160) or via a network exposure function (150). In the latter case, the second exposure protocol (177) is between the network exposure function (150) and the application function (160).

[0052] In 4G / LTE / EPC and 5G / NR / 5GC, the servers / nodes / functions / interfaces / protocols are named as follows:

[0053]

[0054] In both cases, the location server can also interact with the UE directly over userplane communication carrying LPP (171) with signaling defined by Open Mobile Alliance (OMA) Secure UserPlane Location (SUPL) or some other userplane signaling. In case of SUPL, the location server is denoted SUPL Location Platform (SLP) and the device is denoted SUPL Enabled Terminal (SET).

[0055] Figure 6 illustrates the different 4G / LTE / EPC and 5G / NR / 5GC entities in the more complete and common architecture according to some embodiments.

[0056] 5G positioning methods based on 5G signals are realized with downlink positioning reference signals, associated to a specific radio resource, which may be transmitted using a radio beam with directivity. Each positioning reference signal is associated with an identifier. One or more such signals are transmitted from a specific transmission point associated to a radio base station (110).

[0057] Furthermore, the positioning platform is interacting with other core network functions via AMF (Access and Mobility Function), such as Gateway Mobile Location Center (GMLC), Network Exposure Function (NEF), Application Function (AF), etc. Effectively, these network functions can be seen as enabling location information handling in a nested fashion as illustrated by Figure 7, where one network function NF1 (260) can request, subscribe, receive manage or other procedures related to location information via a second network function NF2 (270), which in turn can have the same interaction with a third network function NF3 (280) due to the triggered request, etc., from NF1 (260). The interface between NF1 and NF2 is labelled (265) and the interface between NF2 and NF3 is labelled (275). Figure 7 provides a generic illustration of these procedures between two nested network functions, or network functions interacting in sequence.

[0058] Some examples with 5G core network

[0059]

[0060] In some embodiments in this context, a geodetic CRS defines coordinates in relation to the earth - a datum. Geodetic coordinates in 3gpp are heretofore defined in WGS84 and the most recent versions of WGS84 are aligned to the ITRF datum. This means that they are well defined globally. However, nationally and regionally, coordinates are defined in differentdatums - reference surfaces that represent the specific region well - to ensure that coordinates match regional and national maps, considering tectonic plate movements horizontally and vertically.

[0061] For example, the North American Datum, NAD83 that is fixed to the North American plate, differs from ITRF by about 2 meters, and the European Terrestrial Reference Frame, ETRF89, differs from ITRF by about 1 meter. Such a difference was negligible when positioning accuracy requirements were rather loose, which was the case when 3GPP decided to represent coordinates only in WGS84 / ITRF. However, positioning accuracy requirements have since become much tighter and the positioning capabilities much better -plentiful of use cases rely on a few centimeters precision in relation to maps. Therefore, it is highly relevant that the coordinate representation in 3GPP becomes more flexible with alternatives of coordinates in regional coordinate reference systems to adapt to use case needs and regional maps. Indeed, it is also important to know which version (epoch) of WGS84 has been adopted in the 3GPP network implementation to enable translations through time at global and regional scales.

[0062] Some embodiments herein address challenges that arise from 3GPP introducing support for assistance of high accuracy Global Navigation Satellite Systems (GNSS) in Rel 15 based on RTCM SC 104 v.3.3, released in October 2016, to enable centimeter precision. Since then, 3GPP Rel 16 and 17 has introduced support for decimeter precision cellular 5G positioning, and Rel 17 and 18 has introduced support for integrity to define error sources and mechanisms to assess positioning reliability.

[0063] The network architecture heretofore supports nominal assistance data and location information assuming that all data is provided in WGS84. This has the following shortcomings:

[0064] • Coordinates only defined in WGS84 without an associated epoch time are not well-defined.

[0065] • Site surveys of TRP antenna locations are typically performed in regional CRS so the network (RAN CAM or E-SMLC / LMF) needs to translate these coordinates to WGS84.

[0066] • Regional GNSS corrections providers typically provide data in regional CRS, so either they need to instead provide data in WGS84 or network needs to transform the reference station coordinates from regional CRS to WGS84. • UEs needs to transform its estimated position in WGS84 to a regional CRS in order to align to maps.

[0067] • RTCM has the ability to align all served devices by data in a regional CRS or via a signaled CRS transformation in an eco-system, while 3GPP LPP will notbe able to align devices causing a reliability risk with potentially different understandings of the CRS and relations to maps.

[0068] Some embodiments herein introduce support for different CRS, while enabling different entities to have the same understanding of the used CRS. Some embodiments describe mechanisms to handshake between network nodes which location CRS and / or CRS transformation that will be used for location information and / or assistance data between the nodes. In some embodiments, the nodes both support a baseline CRS without CRS transformations, e.g., WGS84.

[0069] In some embodiments, a first node provides capabilities related to support for location CRS and CRS transformation, and a second node selects location CRS in consideration of the provided capabilities and provide data to the first node.

[0070] Figure 8 illustrates a signaling chart according to some embodiments, where step 300 comprises an alignment between a first and second node of a location CRS or CRS transformation configuration, which extends the baseline location CRS. This step 300 of alignment may for instance involve communication of signaling 16 described in Figure 1. Based on the aligned CRS configuration, the first node provides to the second node location information related to CRS (step 310). The first node may be communication node 12A or 12B in Figure 1 whereas the second node may be the other of the communication nodes 12A or 12B.

[0071] One example trigger for the second node to initiate the alignment between a first and second node of a CRS location information reporting extension configuration is that it has been engaged in an alignment of a CRS location information reporting extension configuration with a third node.

[0072] One example action of the first node when the alignment between a first and second node of a CRS location information reporting extension configuration has been initiated is to initiate an alignment between the first and fourth node of a periodic location information reporting extension configuration.

[0073] Examples of nodes in 5G systems comprises

[0074] - First node is a network exposure function and second node an application function, fourth node is a GMLC

[0075] - First node is a GMLC, second node is an LMF or SLP, third node is an application function, fourth node is a UE or a radio base station - First node is an LMF or SLP, second node is a UE, third node is a GMLC

[0076] Concrete examples:

[0077] UE request assistance data (AD), with an optional CRS label, LMF to respond with error / data in CRS if available / data in WGS84 and CRS transformationUE to provide capabilities upon request, followed by LMF providing data with CRS label or data with CRS transformation

[0078] LMF to request gNB TRP location with an optional CRS label, gNB to respond with error / data in CRS if available

[0079] NF1 to request NF2 about UE location with an optional CRS label, to respond wit error / data in CRS if available / CRS transformation

[0080] Overall, some embodiments include a method to align the understanding between two communicating nodes (UE, base station, LMF, NEF, AMF, GMLC, AF, generic NF) about which CRS and / or CRS transformation that is used for location coordinates shared between two nodes.

[0081] Other embodiments include a method performed by network (NW) node where it receives from the LCS client whether the location of the target UE is to be obtained in global coordinate system (WGS 84) or regional coordinate reference system.

[0082] Other embodiments include a method performed by base station to provide its location coordinate in regional coordinate reference system to LMF and indicate the CRS to confirm to LMF that a regional CRS has been used

[0083] Other embodiments include a method performed by LMF where LMF check device capabilities for CRS support and if supported provides the needed transformation parameters as part of LPP assistance data to the UE so that the UE can transform its WGS 84 coordinate system to regional coordinate reference system.

[0084] Other embodiments include a method performed by LMF to provide the location of target UE in the desired coordinate system to the LCS client.

[0085] Other embodiments include a method performed by the gNB-DU to provide its location coordinate in regional coordinate reference system to gNB-CU over F1 interface.

[0086] Other embodiments include a method performed in the UE, where a UE indicates a capability to support different CRS and / or transformations.

[0087] Certain embodiments may provide one or more of the following technical advantage(s). The regional coordinate reference systems provide better precision and is aligned with the land overtime compared to WGS84. Supporting coordinates in the regional coordinate references systems by indicating which CRS are linked to would be a step towards high quality and trustworthy networking and (positioning) services.

[0088] 3GPP coordinate representations can be aligned with regional maps and avoid the meter level difference between regional maps and WGS84 / ITRF. 3GPP LPP assistance data representation will be on par with RTCM - industry standard for representing GNSS assistance data in many verticals. 3GPP LPP assistance data representation will also be on par with the representation of the data in regional CRS available from GNSS correctionproviders in a region / country. 3GPP distributed regional CRS or CRS transformations will align coordinate representation and avoid different understandings and assumptions of what the coordinates represent and how they should be converted on the device application layer - a difference in understanding that otherwise would be a positioning error source impacting positioning reliability. 3GPP regional CRS coordinate representation will mean that the mobile network operator will be able to represent base station antenna coordinates in a CRS that will remain relevant and associated to maps over long time and would require the base station antenna coordinates to be re-determined regularly causing higher OPEX.

[0089] Some embodiments thus allow for the handshake between entities - what CRS the other end supports to ensure that the coordinates can be understood by each node involved in positioning and benefit from the precision.

[0090] Alignment details

[0091] The section describes different means to align on location CRS between a first a second node, where the alignment mechanisms can be:

[0092] - alignment via request and response

[0093] - alignment via capability exchange

[0094] Alignment via request and response

[0095] In one embodiment, the alignment between a first and second node of a CRS location information reporting extension configuration is based on a request and response procedure, illustrated by Figure 9. Here, the first and second nodes may correspond to communication nodes 12A, 12B in Figure 1. The alignment is initiated by the second node sending (step 400) a request for location information reporting comprising an CRS indication in addition to a baseline configuration. The specific baseline configuration example is WGS84 that corresponds to a fallback configuration in case the first node does not support the extension. In response, the first node sends (step 410) a location information response including a CRS indication if the first node supports the indicated CRS in the request (400). The response may

[0096] A. comprise an acknowledgement of the location information CRS configuration B. comprise an alternative supported location information CRS configuration C. comprise a baseline response where only the baseline configuration in the request is to be supported.

[0097] Based on the aligned configuration, the first node provides to the second node a first location information (step 410) where the location information is in accordance to the aligned CRS location information reporting configuration,

[0098] From the perspective of the second node as illustrated by Figure 10, the second node sends (500) a request for location information reporting comprising a CRSconfiguration in addition to a baseline configuration. The baseline configuration is a specific configuration that corresponds to a fallback configuration in case the first node does not support the extension. An example fallback CRS is WGS84.

[0099] The second node obtains (510) a location information response from the first node. The response may

[0100] A. comprise an acknowledgement of the location information CRS configuration B. comprise an alternative supported location information CRS configuration C. comprise a baseline response where only the baseline configuration in the request is to be supported.

[0101] Thereby, the first and second nodes have an alignment about the location information CRS configuration, and the second node concludes that periodic location information will be provided in accordance to either A, B or C. Based on the aligned configuration, the second node obtains from the first node a first location information (step 520) where the location information CRS is in accordance with the aligned location information reporting CRS configuration.

[0102] From the perspective of the first node as illustrated by Figure 11 , the first node obtains (600) a request for location information reporting comprising a CRS configuration in addition to a baseline configuration. The baseline configuration is a specific configuration that corresponds to a fallback configuration in case the first node does not support the extension.

[0103] The first node sends (610) a location information response to a second node. The response may

[0104] - As in A, comprise an acknowledgement of the location information CRS configuration - this implies that the first node complies with the suggested location information CRS configuration from the second node and will provide location information accordingly

[0105] - As in B, comprise an alternative supported location information CRS configuration - this implies that the first node does not support the suggested location information CRS configuration from the second node and will instead provide location information according to the alternative location information CRS configuration.

[0106] - As in C, comprise a baseline response where only the baseline configuration in the request is to be supported - this implies that the first node does not support the location information CRS configuration, for example its supported protocol version does not comprise the location information CRS configuration

[0107] Thereby, the first and second nodes have an alignment about the locationinformation CRS configuration, and the first node concludes that location information will be provided in accordance with either A, B or C. Based on the aligned configuration, the first node provides to the second node a first location information (step 620), where the location information is in accordance with the aligned location information CRS configuration.

[0108] In some embodiments, Figures 9-11 exemplify the embodiments shown in Figure 2. In this case, the request 400 in Figure 9 exemplifies the information request 26-1 in Figure 2 and the response 410 in Figure 9 (optionally also with the location information 20) exemplifies the information response 26-2 in Figure 2.

[0109] Alignment via capability exchange

[0110] In another embodiment, the alignment between a first and second node of a location information reporting CRS configuration is based on a capability request and response procedure, illustrated by Figure 12. The first and second nodes may exemplify the communication nodes 12A, 12B in Figure 1. The alignment is initiated by the second node sending (step 400) a request for capabilities. The capability request may comprise information about what specific capabilities that are requested.

[0111] The request may comprise a specific baseline configuration that corresponds to a fallback configuration in case the first node does not support the extension.

[0112] In response, the first node sends (step 710) a capability response comprising one or more of

[0113] - baseline location information CRS reporting support

[0114] - location information reporting CRS support

[0115] - assistance data location CRS support

[0116] - assistance data location CRS transformation support

[0117] The location information reporting CRS support may comprise additional information about the type of supported location information reporting CRS. Examples include support for CRS indications for assistance data, support for CRS transformations in assistance data, support for CRS for location reporting. The support can be generic or specific per positioning method, or even per positioning mode such as node assisted (node reports location measurements) or node based (node estimates locations)

[0118] Based on the capabilities, the second node sends (720) a location information request comprising a location information reporting CRS configuration, and optionally a baseline periodic location information reporting configuration. The baseline configuration may comprise a default periodic reporting interval, a reporting amount that may be set to infinite, etc.

[0119] The first node provides a first location information (step 730) location information is in accordance with the aligned location information reporting configuration,

[0120] From the perspective of the second node as illustrated by Figure 8, the second nodesends (800) a capability request. The request may comprise instructions about what capabilities that are requested. The first node responds with capabilities comprising support for a location information reporting CRS configuration in addition to a baseline configuration.

[0121] The second node obtains (810) a location information capability response from the first node. The response may comprise

[0122] - baseline periodic location information reporting support

[0123] - location information reporting CRS support

[0124] The location information reporting CRS support may comprise additional information about the type of supported location information reporting CRS.

[0125] Based on the capabilities, the second node sends (820) a location information request comprising a location information reporting CRS configuration, and optionally a baseline periodic location information reporting configuration. Thereby, the first and second nodes have aligned the report CRS configuration.

[0126] The second node obtains a first location information (step 810), where the location information is in accordance with the aligned location information reporting CRS configuration.

[0127] From the perspective of the first node as illustrated by Figure 9, the first node obtains (900) a capability request. The request may comprise instructions about what capabilities that are requested. The first node responds (910) with capabilities comprising support for a location information reporting CRS configuration in addition to a baseline configuration.

[0128] The response may comprise

[0129] - baseline periodic location information reporting support

[0130] - location information reporting CRS support

[0131] The location information reporting CRS support may comprise additional information about the type of supported location information reporting CRS.

[0132] The first node obtains (820) a location information request comprising a location information reporting CRS configuration, and optionally a baseline location information reporting configuration. Thereby, the first and second nodes have aligned the periodic report configuration.

[0133] The first node provides a first location information (step 830), where the location information is in accordance with the aligned location information reporting CRS configuration.

[0134] In some embodiments, Figures 12-14 exemplify the embodiments shown in Figure 3. In this case, the request 700 in Figure 12 exemplifies the capability request 30-1 in Figure 3 and the response 710 in Figure 12 exemplifies the capability response 30-2 in Figure 3. Figures 12-14 may also exemplify combination of the embodiments shown in Figure 2, where the request 720 in Figure 12 exemplifies the information request 26-1 in Figure 2 andthe response 730 in Figure 12 exemplifies the information response 26-2 in Figure 2.

[0135] In any of the described procedures, the first node may request assistance data from the second node to support location information determination. The second node may provide assistance data to the first node to support location information determination, when not requested (unsolicited). The assistance data may comprise CRS indications and / or CRS transformations.

[0136] In one embodiment, a first network node, which can be base station or gNB-DU, indicates to a second network node, which can be LMF or gNB-CU, respectively, a list of standardized types referring to the CRS used by the TRP.

[0137] In one embodiment, the TRP coordinates include an indication of the regional coordinate references systems (CRS) by indicating which CRS it is associated to.

[0138] Impact to 3GPP specification

[0139] Some embodiments herein are exemplified with impacts to 3gpp specification:

[0140] • Alignment via capabilities - 3GPP LPP A-GNSS positioning

[0141] • Alignment via request / response - 3GPP Nlmf

[0142] • Alignment via request / response - 3GPP NRPPa

[0143] Alignment via capabilities - 3GPP LPP A-GNSS positioning

[0144] In this example, the alignment is via capabilities, in this case a generic capabilitiy request, and a response indicating support.

[0145] Request for capabilities:

[0146] The IE A-GNSS-Request-Capabilities is used by the location server to request A-GNSS location capabilities (e.g., GNSSs and assistance data supported) from the target device.

[0147] - ASN1 START

[0148] A-GNSS-RequestCapabilities ::= SEQUENCE {

[0149] gnss-SupportListReq BOOLEAN, assistanceDataSupportListReq BOOLEAN, locationVelocityTypesReq BOOLEAN,

[0150] - ASN1ST0P

[0151]

[0152] Response:

[0153] The IE A-GNSS-Provide-Capabilities is used by the target device to indicate its capability to support A-GNSS and to provide its A-GNSS location capabilities (e.g., GNSSs and assistance data supported) to the location server.

[0154] - ASN1 START

[0155] A-GNSS-ProvideCapabilities ::= SEQUENCE {

[0156] [[

[0157] location-CRS-Supported-r19 ENUMERATED { true } OPTIONAL ]]

[0158] }

[0159] }

[0160] - ASN1STOP

[0161]

[0162] Optional follow up request from location information

[0163] The CommonlEsRequestLocationlnformation carries common lEs for a Request Location Information LPP message Type.- ASN1 START

[0164] CommonlEsRequestLocationlnformation ::= SEQUENCE {

[0165] [[

[0166] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL ]]

[0167] }

[0168] - ASN1STOP

[0169]

[0170] i ECID i The field is optionally present, need ON, if E-Cib or NR E-CID is

[0171]

[0172]

[0173] Optional response with location information in the requested CRS

[0174] The CommonlEsProvideLocationlnformation carries common lEs for a Provide Location Information LPP message Type.

[0175] - ASN1 START

[0176] CommonlEsProvideLocationlnformation ::= SEQUENCE {

[0177] [[

[0178] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL ]]

[0179] }- ASN1STOP

[0180]

[0181] locationCRS

[0182] i This field specifies the coordinate reference system (CRS) the location coordinates are related to. In case of Local 2D / 3D coordinates, the specifies CRS relates to the i reference point attribute. If not present, the location coordinates are related to a CRS as defined in TS 23.032

[0015] ,

[0183] NOTE: Void.

[0184] Alternatively an error if the requested CRS is not supported, error cause IppCrsNotSupported

[0185] The CommonlEsError carries common lEs for an Error LPP message Type. - ASN1 START

[0186] CommonlEsError ::= SEQUENCE {

[0187] errorCause ENUMERATED {

[0188] undefined,

[0189] IppMessageHeaderError,

[0190] IppMessageBodyError,

[0191] epduError,

[0192] incorrectDataValue,

[0193] lppSegmentationError-v1450,

[0194] IppCrsNotSupported-rl 9,

[0195] IppCrsT ransformationNotSupported-r19

[0196] }

[0197] }

[0198] - ASN1STOP

[0199]

[0200] i This IE defines the cause for an error. ' IppMessageHeaderError1, 'IppMessageBodyError1and 'epduError1is used if a receiver is able to detect a coding i error in the LPP header (i.e., in the common fields), LPP message body or in an EPDU, i respectively. 'incorrectDataValue' is used if a receiver receives an incorrect data value.

[0201]

[0202] Alignment via request / response - 3GPP LPP A-GNSS positioning

[0203] In this example, a target device will request for assistance data comprising CRS transformations between a source CRS and a target CRS, and will receive an error if CRS transformations are not supported, or will receive CRS transformations are supported Request:

[0204] The CommonlEsRequestAssistanceData carries common lEs fora Request Assistance Data LPP message Type.

[0205] - ASN1 START

[0206] CommonlEsRequestAssistanceData ::= SEQUENCE {

[0207] primaryCelllD ECGI OPTIONAL, - Cond EUTRA

[0208] [[

[0209] segmentationlnfo-r14 Segmentationlnfo-r14 OPTIONAL

[0210] -- Cond Segmentation ]].

[0211] [[

[0212] periodicAssistanceDataReq-r15 PeriodicAssistanceDataControlParameters-r15

[0213] OPTIONAL, - Cond PerADreq primaryCelllD-r15 NCGI-r15 OPTIONAL - Cond NR ]].

[0214] [[

[0215] coordT ransformationsReq-r19 CoordinateT ransformationsReq-r19 OPTIONAL ]]

[0216] }- ASN1STOP

[0217]

[0218] i Segmentation This field is optionaHy present, need OP, if Ipp-message- segmentation-req has been received from the location serve with bit 1 (targetToServer) set to value 1. The field shall be omitted if Ipp-message-segmentation-req has not been recei in this location session, or has been received with bit 1 (targetToServer) set to value 0.

[0219] The field is mandatory present if the target device requests periodic assistance data delivery. Otherwise it is not present.

[0220]

[0221] i NR i The field is mandatory present for NR access. The field shall

[0222]

[0223]

[0224] i This parameter identifies the current primary cell for the target device.

[0225] segmentationinfo

[0226] i This field indicates whether this RequestAssistanceData message is o segments, as specified in clause 4.3.5.

[0227] periodicAssistanceDataReq

[0228] i This field indicates a request for periodic assistance data delivery, as specified in clause i

[0229]

[0230] Response if OK

[0231] CommonlEsProvideAssistanceData

[0232] The CommonlEsProvideAssistanceData carries common lEs for a Provide Assistance Data LPP message Type.- ASN1 START

[0233] CommonlEsProvideAssistanceData ::= SEQUENCE {

[0234] [[

[0235] segmentationlnfo-r14 Segmentationlnfo-r14 OPTIONAL -- Need ON ]].

[0236] [[

[0237] periodicAssistanceData-r15 PeriodicAssistanceDataControlParameters-r15

[0238] OPTIONAL - Cond PerAD ]].

[0239] [[

[0240] coordT ransformations-r19 CoordinateT ransformations-r19

[0241] OPTIONAL - Need OP ]]

[0242] }

[0243] - ASN1STOP

[0244]

[0245]

[0246] i This field indicates a periodic assistance data delivery, as specified in clauses 5.2.1a and i

[0247]

[0248] Response if not OK, error cause IppCrsTransformationNotSupported

[0249] CommonlEsErrorThe CommonlEsError carries common lEs for an Error LPP message Type.

[0250] - ASN1 START

[0251] CommonlEsError ::= SEQUENCE {

[0252] errorCause ENUMERATED {

[0253] undefined,

[0254] IppMessageHeaderError,

[0255] IppMessageBodyError,

[0256] epduError,

[0257] incorrectDataValue,

[0258] lppSegmentationError-v1450,

[0259] IppCrsNotSupported-rl 9,

[0260] IppCrsT ransformationNotSupported-r19

[0261] }

[0262] }

[0263] - ASN1STOP

[0264]

[0265] Alignment via request / response - 3GPP Nlmf

[0266] In Nlmf 3GPP TS 29.572, the request can contain an indication about what CRS to report location data in:

[0267] 6.1.6.2.2 Type: InputDataTable 6.1.6.2.2-1: Definition of type InputData

[0268]

[0269] Response - if successful, the attribute usedCRS is present and coordinates are in this CRS, otherwise the coordinates are in the baseline CRS.

[0270] 6.1.6.2.3 Type: LocationData

[0271] Table 6.1.6.2.3-1: Definition of type LocationData

[0272]

[0273] Alignment via request / response - 3GPP NRPPa

[0274] Below, LMF requests which CRS the gNB is requested to provide its TRP location information. If the gNB is capable and provides the requested CRS, it will also indicate the CRS in the response to ensure that gNB and LMF are aligned.

[0275] 9.1.1.14 TRP INFORMATION REQUEST

[0276] This message is sent by an LMF to request information for TRPs hosted by an NG-RAN node.

[0277] Direction:

[0278]

[0279] node.

[0280] >

[0281] <

[0282]

[0283]

[0284] In one embodiment, the addition can be the Reference point IE in NRPPa and F1AP specs as highlighted below:

[0285] 9.2.51 Reference Point

[0286] This information element provides a reference point information.

[0287]

[0288] 9.2.51a Coordinate Reference System

[0289] This information element provides a reference point information.

[0290] >

[0291] >

[0292] >

[0293]

[0294] Consider now the scope of location CRS and CRS transformations according to some embodiments.

[0295] 2.1 Location CRS information

[0296] An optional location CRS IE, identifying the CRS of the provided location coordinates is the key part to allow association of a location coordinate to a different coordinate reference system than WGS84.This information is provided as database links to databases managed by ISO [3] and EPRG [4], The parameters provided in the IE CoordinateReferenceSystem are used as specified for message type 1300 and 1302 in [2],CoordinateReferenceSystem-r19 SEQUENCE {

[0297] coordinateEpoch-r19 INTEGER (0..65535), OPTIONAL, - Cond CE

[0298] plateNumber-r19 INTEGER (0..31), OPTIONAL, - Cond Plate

[0299] crs-Name-r19 VisibleString (SIZE (1..31)) OPTIONAL, crs-DatabaseLinks-r19 CRS-DatabaseLinks-r19 OPTIONAL,

[0300] }

[0301] CRS-DatabaseLinks-r19::= SEQUENCE (SIZE (1..maxDBLinks-r19)) OF CRS- DatabaseLinkElement-r19

[0302] CRS-DatabaseLinkElement-r19 ::= SEQUENCE {

[0303] crs-Database-r19 ENUMERATED {epsg, iso, ...},

[0304] crs-Category-r19 ENUMERATED {crs, datum, ...} OPTIONAL, crs-Code-r19 INTEGER (1..65536) OPTIONAL,

[0305] }

[0306] maxDBLinks-r19 INTEGER ::= 7

[0307] 2.2 Optional Association of location coordinates to a location CRS

[0308] The baseline will be WGS84, but in case location CRS is supported, an additional attribute identifying the location CRS can be provided in

[0309] IE CommonlEsProvideLocationlnformation to define location CRS of reported location coordinates.

[0310] IE NR- Position Calculation Assistance-rl 6 to define location CRS of the provided assistance data for UE-based positioning.

[0311] IE GNSS-RTK-ReferenceStationlnfo-r15 to define location CRS of reference station coordinates.

[0312] IE GNSS-SSR-CorrectionPoints-r16 to define location CRS of GNSS SSR correction points.

[0313] - IE GNSS-LOS-NLOS-GridPoints-r18 to define location CRS of GNSS NLOS / LOS grid points.

[0314] IE GNSS-SSR-OrbitCorrections-r15 to define location CRS of orbit corrections.lEs TBS-AssistanceDataList-r14, Sensor-AssistanceDataList-r14, LocationDataLCI- r14 (of IE WLAN-AP-Location-r14), BT-Beaconlnfo-r18 to define location CRS for RAT-independent positioning.

[0315] posSibType8-1 representing the IE CoordinateReferenceSystem-r19.

[0316] 2.3 Optional Coordinate Transformations

[0317] In addition to the location CRS, it is relevant to also add support for coordinate transformations. There are a separate addition from the location CRS.

[0318] The IE CoordinateTransformations specifies coordinate transformation between a source CRS and a target CRS as specified in messages 1021-1027 and 1301 in [2], The transformations are defined based on three components - coordinate transformation information, residuals and projections, and the components can be combined in sequence. The components the combine into a transformation from a source CRS to a target CRS are provided with the same system ID, and realized by the following IE.

[0319] CoordinateTransformations-r19::= SEQUENCE (SIZE (1 ,.maxCT-r19)) OF

[0320] CoordT ransElement-r19

[0321] CoordTransElement-r19 ::= SEQUENCE {

[0322] systemlD-r19 INTEGER (0..255) OPTIONAL, coordTranslnfo-r19 CoordTranslnfo-r19 OPTIONAL, coordTransResidual-19 CHOICE {

[0323] residualEllipsGridRepr-r19 CoordTransResidualEllipsoidalGridRepr-r19, residualPlaneGridRepr-r19 CoordTransResidualPlaneGridRepr-r19,

[0324] } OPTIONAL, coordTransProjection-r19 CHOICE {

[0325] projTypesBaseline-r19 CoordTransProjectionTypesBaseline-r19, projLambertConicConf-r19 CoordT ransProjectionLambertConicConformal-r19, projObliqueMercator-r19 CoordT ransProjectionObliqueMercator-r19,

[0326] } OPTIONAL,

[0327] }

[0328] CoordTranslnfo-r19::= SEQUENCE {sourceCRS-r19 CoordinateReferenceSystem-r19, targetCRS-r19 CoordinateReferenceSystem-r19,

[0329] utilized? ransResidual-r19 ENUMERATED { ellipsGridRepr, planeGridRepr, ... } OPTIONAL, utilizedTransProjection-r19 ENUMERATED { baseline, lambertConicConf, obliqueMercator, ...}

[0330] OPTIONAL, coordTrans-r19 CHOICE {

[0331] helmertAbrMolodenskiBadekas-r19 CoordT ransHelmertAbrMolodenskiBadekas-r19, timeDepLinExprHelmert-r19 CoordT ransTimeDepLinExprHelmert-r19,

[0332] }.

[0333] maxCT-r19 INTEGER ::= 255

[0334] Coordinate transformation components

[0335] 1. The coordinate transformation information is either

[0336] a. linear or strict Helmert, the abridged Molodenski (message 1021) or the Molodenski-Badekas (1022). These are supported via one and the same IE: CoordTransHelmertAbrMolodenskiBadekas -r19 ::= SEQUENCE { computationlndicator-r19 ENUMERATE { linearForm, strictForm, abridgedMolodenski, molodenskiBadekas, ... },

[0337] heightlndicator-r19 ENUMERATE { geometricHeight, physHeightT arget, physHeightSource,

[0338] ...},

[0339] areaVal id ityO rig in Latitude- r19 INTEGER (-324000..324000), areaValidityOriginl_ongitude-r19 INTEGER (-648000..648000), areaValidity-N-S-Extension-r19 INTEGER (0..32766),

[0340] areaValidity-E-W-Extension-r19 INTEGER (0..32766),

[0341] xTranslation-r19 INTEGER (-4194303..4194303), yTranslation-r19 INTEGER (-4194303..4194303), zTranslation-r19 INTEGER (-4194303..4194303), xRotation-r19 INTEGER (-2147483647.. 2147483647) yRotation-r19 INTEGER (-2147483647.. 2147483647) zRotation-r19 INTEGER (-2147483647.. 2147483647)scaleCorrection-r19 INTEGER (-16777215..16777215), x-M-B-RotationPoint-r19 INTEGER (-17179869183..17179869183)

[0342] OPTIONAL -Cond molBad, y-M-B-RotationPoint-r19 INTEGER (-17179869183..17179869183)

[0343] OPTIONAL -Cond molBad, z-M-B-RotationPoint-r19 INTEGER (-17179869183..17179869183)

[0344] OPTIONAL -Cond molBad, sourceSemiMajorAxis-r19 INTEGER (0..16777215), sourceSemiMinorAxis-r19 INTEGER (0..33554431), targetSemiMajorAxis-r19 INTEGER (0..16777215), targetSemiMinorAxis-r19 INTEGER (0..33554431), horizHelmertMolodenskiQuality-r19 INTEGER (0..7), vertHelmertMolodenskiQuality-r19 INTEGER (0..7),

[0345] }

[0346] b. time-dependent linear Helmert transformation (message 1301 in [2]), supported via the IE

[0347] CoordT ransTimeDepLinExprHelmert-r19 SEQUENCE {

[0348] referenceEpoch-r19 INTEGER (0..65535),

[0349] xTranslation-r19 INTEGER (-4194303..4194303), yTranslation-r19 INTEGER (-4194303..4194303), zTranslation-r19 INTEGER (-4194303..4194303), xRotation-r19 INTEGER (-2147483647.. 2147483647) yRotation-r19 INTEGER (-2147483647.. 2147483647) zRotation-r19 INTEGER (-2147483647.. 2147483647) scaleCorrection-r19 INTEGER (-16777215..16777215), dot-xTranslation-r19 INTEGER (-65535..65535),

[0350] dot-yTranslation-r19 INTEGER (-65535..65535),

[0351] dot-zTranslation-r19 INTEGER (-65535..65535),

[0352] dot-xRotation-r19 INTEGER (-65535..65535),

[0353] dot-yRotation-r19 INTEGER (-65535..65535),

[0354] dot-zRotation-r19 INTEGER (-65535..65535),

[0355] dot-scaleCorrection-r19 INTEGER (-8191..8191),

[0356] }2. The coordinate transformation residuals can for example be used to translate the CRS from one epoch to another to capture drift of tectonic plates. They can be defined in ellipsoidal grid representation (message 1023 in [2]) or plane grid representation (message 1024 in [2])

[0357] a. Ellipsoidal grid representation is supported by the IE CoordTransResidualEllipsoidalGridRepr-r19 ::= SEQUENCE {

[0358] horizontalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP verticalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP g ridOrigi n Latitude- r19 INTEGER (-648000..648000), gridOriginl_ongitude-r19 INTEGER (-1296000..1296000),

[0359] grid-N-S-Delta-r19 INTEGER (0..4095),

[0360] grid-E-W-Delta-r19 INTEGER (0..4095),

[0361] meanl_atOffset-r19 INTEGER (-127..127),

[0362] meanl_ongOffset-r19 INTEGER (-127..127),

[0363] meanHeightOffset-r19 INTEGER (-16383..16383),

[0364] ell ipsoidaIG rid Resid uals- r19 SEQUENCE (SIZE(16)) OF EllipsoidalGridResidualElements-r19, horizlnterpMethodlndicator-r19 INTEGER (0..3),

[0365] vertlnterpMethodlndicator-r19 INTEGER (0..3), horizResidualQualitylndicator-r19 INTEGER (0..7), vertResidualQualitylndicator-r19 INTEGER (0..7),

[0366] modifiedJulianDayNumber-r19 INTEGER (0..65535),

[0367] }

[0368] Ellips

[0369]

[0370] }

[0371] b. Plane grid representation is supported by the IE CoordTransResidualPlaneGridRepr-r19 ::= SEQUENCE {

[0372] horizontalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP verticalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP g ridOrigi n North ing- r19 INTEGER (-16777215..16777215),gridOriginEasting-r19 INTEGER (0..67108863),

[0373] grid-N-S-Delta-r19 INTEGER (0..4095),

[0374] grid-E-W-Delta-r19 INTEGER (0..4095), meanLocalNorthingOffset-r19 INTEGER (-511..511), meanl_ocalEastingOffset-r19 INTEGER (-511..511), meanLocalHeightOffset-r19 INTEGER (-16383..16383), planeGridResiduals-r19 SEQUENCE (SIZE(16)) OF PlaneGridResidualElements-r19, horizlnterpMethodlndicator-r19 INTEGER (0..3),

[0375] vertlnterpMethodlndicator-r19 INTEGER (0..3), horizResidualQualitylndicator-r19 INTEGER (0..7), vertResidualQualitylndicator-r19 INTEGER (0..7), modifiedJulianDayNumber-r19 INTEGER (0..65535),

[0376] PlaneGridResidualElements-r19 SEQUENCE {

[0377] residualLocalNorthing-r19 INTEGER (-255..255), residualLocalEasting-r19 INTEGER (-255..255), residualLocalHeight-r19 INTEGER (-255..255),

[0378] 3. The projections are grouped in different lEs, where the projections are represented as in [2] and defined in [5], The different lEs are representing a baseline set of projections (message 1025 in [2]), Lambert conic conformal projection (message 1026 in [2]) and Oblique Mercator projection (message 1027 in [2]).

[0379] a. The baseline set of projections is supported by the IE CoordTransProjectionTypesBaseline-r19 ::= SEQUENCE {

[0380] projectionType-r19 ENUMERATED { unknown, tm, tms, Icdsp, Iccw, cs, om, os, mc,ps, ds, ...}, latNaturalOrigin-r19 INTEGER (-8181818181.. 8181818181), longNaturalOrigin-r19 INTEGER (-16363636362.. 16363636362), scaleFactorNaturalOrigin-r19 INTEGER (0..1073741823),

[0381] falseNorthing-r19 INTEGER (0..68719476735),

[0382] falseEasting-r19 INTEGER (0..17179869183),b. The Lambert conic conformal projection is supported by the IE CoordTransProjectionLambertConicConformal-r19 ::= SEQUENCE {

[0383] projectionType-r19 ENUMERATED { Icc2sp, ...},

[0384]

[0385] c. The Oblique Mercator projection is supported by the IE CoordTransProjectionObliqueMercator-r19 ::= SEQUENCE {

[0386] projectionType-r19 ENUMERATED { om, ...},

[0387] rectificationFlag-r19 ENUMERATED { true }, OPTIONAL - Need OP

[0388]

[0389] }

[0390] 2.4 Optional distribution of CRS transformations

[0391] The CRS transformations can be distributed to target devices in two different ways

[0392] - via the optional attribute coordTransformations of IE

[0393] Comm on lEsProvideAssistanceData .

[0394] - Vis the posSibType8-2 representing the IE CoordinateTransformations-r19.

[0395] Some embodiments herein may be implemented in 3GPP as follows, with the embodiments exemplified as proposed changes to TS 38.305, TS 36.305, and / or TS 37.355 LPP.Text Proposal to TS 38.305

[0396] 4.x Coordinate Reference Systems and Transformations

[0397] 4.x.1 Coordinate Reference Systems

[0398] The baseline Coordinate Reference System (CRS) for 5GS, including NG-RAN, is WGS84 as defined in [4], Optionally, location coordinates in location information and assistance data can be provided in other CRS. Atypical example is a national or regional CRS that is adapted to the regional conditions and follow the tectonic plate movements, which means that the coordinates will remain aligned with maps over long time without calibration. In this case, the location coordinates are accompanied by an optional CRS information as defined in [xx]. This CRS information consists of database links to databases managed by ISO [yy] and EPRG [zz].

[0399] The CRS information can be accompanied via the assistance data from the location server as well as the location information from the device. The CRS information can also be provided as a posSIB.

[0400] 4.x.2 Coordinate Transformations

[0401] Coordinates in one source CRS can be transformed into coordinates in a target CRS via coordinate transformations as specified in [xx. The transformations are defined based on three components - coordinate transformation information, residuals and projections, and the components can be combined in sequence. The components that combine into a transformation from a source CRS to a target CRS are provided with the same system identifier, to allow them to be distributed separately.

[0402] The coordinate transformation components and their subtypes are:

[0403] 1. The coordinate transformation information is either

[0404] a. linear or strict Helmert, the abridged Molodenski (message 1021 in [xx]) or the Molodenski-Badekas (1022) transformation.

[0405] b. time-dependent linear Helmert transformation (message 1301 in [xx]) 2. The coordinate transformation residuals can for example be used to translate the CRS from one epoch to another to capture drift of tectonic plates. They can be defined in either

[0406] a. ellipsoidal grid representation (message 1023 in [xx])

[0407] b. plane grid representation (message 1024 in [xx]

[0408] 3. The projections are defined in three groups, where the projections are represented as in [xx] and defined in [aa], chapter 1.4:

[0409] a. a baseline set of projections (message 1025 in [xx]), including Transverse Mercator (TM), Transverse Mercator, South-Oriented (TMS), Lambert ConicConformal, 1SP (LCC1SP), Lambert Conic Conformal (LCCW), Casini- Soldner (CS), Oblique Stereographic (OS), Mercator (MC), Polar Stereographic (PS), Double Stereographic (DS).

[0410] b. Lambert conic conformal, 2SP, projection (message 1026 in [xx]) and c. Oblique Mercator projection (message 1027 in [xx]).

[0411] Text Proposal to TS 36.305

[0412] 4.x Coordinate Reference Systems and Transformations

[0413] 4.x.1 Coordinate Reference Systems

[0414] The baseline Coordinate Reference System (CRS) for EPS, including E-UTRAN, is WGS84 as defined in [4],

[0415] Proposed Changes to TS 37.355. These proposed changes introduce location Coordinate Reference Systems (CRS) information and CRS coordinate transformations. Currently, 3GPP only useBLE WGS84 / ITRF2014 current epoch, which means

[0416] - There is a drift between WGS84 / ITRF2014 and actual physical locations due to tectonic plate movements - several centimeters per year.

[0417] - Assistance data coordinates (GNSS OSR / SSR, NR DL-TDOA / AoD, TBS, Baro, BLE) for UE-based positioning cannot be represented in a CRS that directly relates to national / regional maps.

[0418] National / regional assistance data for e.g. high accuracy GNSS is often available in national / regional CRS, and such feeds cannot be readily used by MNO without regular and frequent coordinate transformation

[0419] - The MNO needs to regularly and frequently update the location information of its infrastructure components in WGS84 / ITRF2014 due to tectonic plate movement.

[0420] All these costs / negative impact can be handled by representing te coordinates in national / regional CRS which moves with the tectonic plate, and does not have the drift of WGS84 / ITRF2014.

[0421] Some applications relate to both global and regional CRS, e.g. a UAV using a regional CRS in urban areas during landing and takeoff and a global CRS when in the air at high altitiude. Therefore, it would be convenient for the UE to be able to get CRS transformations from the MNO network. This would also imply that there is an alignment across all UEs that the same CRS transformations are used in a region, which avoids a potential error source.Accordingly, the proposed changes: (1) Added definitions of location CRS and CRS transformations. (2) Added optional attributes for location CRS where geodetic coordinates are used; (3) Added optional attribute for CRS transformations as part of the common assistance data; (4) Added posSIB attributes for regional CRS and CRS transformations.

[0422]

[0423] 2 References

[0424]

[0054] 3GPP TS 38.101-5: "User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements".

[0425] [xx] RTCM-SC104, RTCM Recommended Standards for Differential GNSS Service (v.3.4 with Amendment 1), November 1, 2024.

[0426] [yy] European Petroleum Survey Group (EPSG) Geodetic Parameter Dataset EPSG CRS database , International Association of Oil & Gas Producers ( I O G P) , https: / / epsq.org.

[0427] [zz] ISO Geodetic Registry for ISO 19127, ISO / TC 211,

[0428] https: / / qeodetic.isotc211.orq.

[0429] [aa] IOGP Publication 373-7-2 - Geomatics Guidance Note number 7, part 2,

[0430] Coordinate Conversions and Transformations including Formulas, September 2019.

[0431]

[0432] 5.4.3 LPP Error Detection

[0433] Upon receiving any LPP message, the receiving entity shall attempt to decode the message and verify the presence of any errors and:

[0434] 1 > if decoding errors are encountered:

[0435] 2> if the receiver can not determine that the received message is an LPP Error or Abort message:

[0436] 3> return an LPP Error message to the sender and include the received LPP- TransactionlD, if this was decoded, and type of error;

[0437] 3> if the receiver can determine the session and the LPP-TransactionlD and the received message includes the IE Segmentationinfo and the receiver has previously stored message segments for this session and LPP-TransactionlD'.

[0438] 4> discard all stored LPP message segments for this session and LPP- TransactionlD;

[0439] 3> discard the received message and stop the error detection procedure;

[0440] 1 > if the message is a duplicate of a previously received message:

[0441] 2> discard the message and stop the error detection procedure;> if the LPP-TransactionlD matches the LPP-TransactionlD for a procedure that is still ongoing for the same session and the message type is invalid for the current state of the procedure:

[0442] 2> abort the ongoing procedure;

[0443] 2> return an LPP Error message to the sender and include the received transaction ID and type of error;

[0444] 2> if the message includes the IE Segmentationinfo and the receiver has previously stored message segments for this session and LPP-TransactionlD'.

[0445] 3> discard all stored LPP message segments for this session and LPP- TransactionlD;

[0446] 2> discard the message and stop the error detection procedure;

[0447] > if the message includes the IE Segmentationinfo'.

[0448] 2> if the receiver has previously stored LPP message segments for this session and LPP- Transaction ID '.

[0449] 3> if the received message type is different to the stored message type:

[0450] 4> return an LPP Error message to the sender and include the received transaction ID and type of error;

[0451] 4> discard the message and all stored LPP message segments for this session and LPP-TransactionlD and stop the error detection procedure;

[0452] 2> if the IE Segmentationinfo has the value moreMessagesOnTheWay.

[0453] 3> store the received message;

[0454] NOTE: As an implementation option, the receiver of an LPP Provide Assistance Data or LPP Provide Location Information message may process the received message segment instead of storing the message.

[0455] 2> if the IE Segmentationinfo has the value noMoreMessages'.

[0456] 3> continue error detection for the received message and any stored LPP message segments for this session and LPP-TransactionlD;

[0457] > if the message type is an LPP Requestcapabilities and some of the requested information is not supported:

[0458] 2> return any information that can be provided in a normal response.

[0459] > if the message type is an LPP RequestAssistanceData or RequestLocationlnformation and some or all of the requested information is not supported:

[0460] 2> return any information that can be provided in a normal response, which includes indications on other information that is not supported.

[0461] 2> if the message contains a request for location information in a specific CRS, and the specific CRS is not supported by the target3> return the error cause lppCrsNotSupported-r19 and provide location information in the baseline CRS.

[0462] 2> if the message contains a request for assistance data including a specific CRS transformation, and the specific CRS transformation is not supported by the server 3> return the error cause lppCrsTransformationNotSupported-r19.

[0463]

[0464] 6.4.1 Common Lower-Level IBs

[0465] [■ ■ ■]

[0466] CellGloballdGERAN

[0467] The IE CellGloballdGERAN specifies the global Cell Identifier for GERAN, the globally unique identity of a cell in GERAN.

[0468] - ASN1 START

[0469] CellGloballdGERAN ::= SEQUENCE {

[0470] plmn-ldentity SEQUENCE {

[0471] mcc SEQUENCE (SIZE (3)) OF INTEGER (0..9), mnc SEQUENCE (SIZE (2..3)) OF INTEGER (0..9) }.

[0472] locationAreaCode BIT STRING (SIZE (16)),

[0473] cellldentity BIT STRING (SIZE (16)),

[0474] }

[0475] - ASN1STOP

[0476]

[0477] CoordinateReferenceSystem

[0478] The IE CoordinateReferenceSystem specifies the name and / or further details of the considered coordinate reference system (CRS). The parameters provided in the IE CoordinateReferenceSystem are used as specified for message type 1300 and 1302 in [xx], - ASN1 START

[0479] CoordinateReferenceSystem-

[0480]

[0481] ::= SEQUENC

[0482] coordinateEpoch-r19 INTEGER (0. OPTIONAL, - Cond CE plateNumber-r19 INTEGER (0. OPTIONAL, - Cond Plate crs-Name-r19 VisibleString OPTIONAL,

[0483] crs-Databasel_inks-r19 CRS-Databa

[0484]

[0485] OPTIONAL,

[0486] }

[0487] CRS-DatabaseLinks-r19::= SEQUENCE (SIZE (1..maxDBLinks-r19)) OF CRS- DatabaseLinkElement-r19

[0488] CRS-DatabaseLinkElement-r19 ::= SEQUENCE {

[0489] crs-Database-r19 ENUMERATED {epsg, iso, ...},

[0490] crs-Category-r19 ENUMERATED {crs, datum, ...} OPTIONAL, crs-Code-r19 INTEGER (1..65536) OPTIONAL,

[0491] maxDBLinks-r19 INTEGER ::= 7

[0492] - ASN1STOP

[0493]

[0494] >

[0495]

[0496]

[0497] NOTE 1 : If a database link is provided via the triplet cre-Database, crs-Category and crs-Code, the string representation of the Database-Link attribute of message 1302 in [xx] is compiled as “[crs-Database].[crs-Category]:[crs-Coc / e]”, for example as “EPSG.DATUM:1165” for the ITRF2014 datum or “ISO.CRS:425” for the ITRF2014 geodetic CRS.

[0498] CoordinateTransformations

[0499] The IE CoordinateTransformations specifies coordinate transformation between one or several sets of a source CRS and a target CRS as specified in messages 1021-1027 and 1301 in [xx],

[0500] - ASN1 START

[0501] CoordinateTransformations-r19::= SEQUENCE (SIZE (1 ,.maxCT-r19)) OF

[0502] CoordT ransElement-r19

[0503] CoordTransElement-r19 ::= SEQUENCE {

[0504] systemlD-r19 INTEGER (0..255) OPTIONAL, coordTranslnfo-r19 CoordTranslnfo-r19 OPTIONAL, coordTransResidual-19 CHOICE {

[0505] residualEllipsGridRepr-r19 CoordTransResidualEllipsoidalGridRepr-r19, residualPlaneGridRepr-r19 CoordTransResidualPlaneGridRepr-r19,

[0506] } OPTIONAL, coordTransProjection-r19 CHOICE {

[0507] projTypesBaseline-r19 CoordT ransProjectionTypesBaseline-r19, projLambertConicConf-r19 CoordT ransProjectionLambertConicConformal-r19, projObliqueMercator-r19 CoordTransProjectionObliqueMercator-r19,

[0508] } OPTIONAL,

[0509] ...}CoordTranslnfo-r19::= SEQUENCE {

[0510] sourceCRS-r19 CoordinateReferenceSystem-r19,

[0511] targetCRS-r19 CoordinateReferenceSystem-r19,

[0512] utilizedT ransResidual-r19 ENUMERATED { ellipsGridRepr, planeGridRepr, ...}

[0513] OPTIONAL,

[0514] utilizedT ransProjection-r19 ENUMERATED { baseline, lambertConicConf, obliqueMercator, ...} OPTIONAL, coordTrans-r19 CHOICE {

[0515] helmertAbrMolodenskiBadekas-r19 CoordT ransHelmertAbrMolodenskiBadekas-r19, timeDepLinExprHelmert-r19 CoordT ransTimeDepLinExprHelmert-r19,

[0516] }.

[0517] }

[0518] maxCT-r19 INTEGER ::= 255

[0519] - ASN1STOP

[0520]

[0521] CoordinateTransformationsReq

[0522] The IE CoordinateTransformationsReq specifies request details for coordinate transformations between a set of a source CRS and a target CRS.

[0523] - ASN1 START

[0524] CoordinateTransformationsReq-r19::= SEQUENCE (SIZE (1 ,.maxCT-r19)) OF CoordT ransReqElement-r19

[0525] CoordTransReqElement-r19 ::= SEQUENCE {

[0526] sourceCRS-r19 CoordinateReferenceSystem-r19, targetCRS-r19 CoordinateReferenceSystem-r19,

[0527] }

[0528] OPTIONAL,

[0529] - ASN1STOP

[0530]

[0531] i This field specifies the source CRS of the coordinate transformation.

[0532] targetCRS

[0533] i This field specifies the target CRS of the coordinate transformation.

[0534] CoordTransHelmertAbrMolodenskiBadekas

[0535] The IE CoordTransHelmertAbrMolodenskiBadekas specifies four different sets of transformations - the linear form of the Helbert Transformation, the strict form of the Helbert Transformation, the abridged Molodenski Transformation, and the Molodenski-Badekas as specified in messages 1021 and 1022 in [xx],

[0536] - ASN1 START

[0537] CoordT ransHelmertAbrMolodenskiBadekas -r19 = SEQUENCE { computationlndicator-r19 ENUMERATE { linearForm, strictForm,

[0538] abridgedMolodenski, molodenskiBadekas

[0539]

[0540] heightlndicator-r19 ENUMERATE { geometricHeight,

[0541] physHeightTarget, physHeightSource, ...}, areaVal id ityO rig in Latitude- r19 INTEGER (-324000..324000), areaValidityOriginl_ongitude-r19 INTEGER (-648000..648000),

[0542] areaValidity-N-S-Extension-r19 INTEGER (0..32766),

[0543] areaValidity-E-W-Extension-r19 INTEGER (0..32766),

[0544] xTranslation-r19 INTEGER (-4194303..4194303), yTranslation-r19 INTEGER (-4194303..4194303),

[0545] zTranslation-r19 INTEGER (-4194303..4194303),

[0546] xRotation-r19 INTEGER (-2147483647.. 2147483647), yRotation-r19 INTEGER (-2147483647.. 2147483647), zRotation-r19 INTEGER (-2147483647.. 2147483647), scaleCorrection-r19 INTEGER (-16777215..16777215),

[0547] x-M-B-RotationPoint-r19 INTEGER (-17179869183..17179869183)

[0548] OPTIONAL -Cond molBad,

[0549] y-M-B-RotationPoint-r19 INTEGER (-17179869183..17179869183)

[0550] OPTIONAL -Cond molBad,

[0551] z-M-B-RotationPoint-r19 INTEGER (-17179869183..17179869183)

[0552] OPTIONAL -Cond molBad,sourceSemiMajorAxis-r19 INTEGER (0..16777215), sourceSemiMinorAxis-r19 INTEGER (0..33554431), targetSemiMajorAxis-r19 INTEGER (0..16777215), targetSemiMinorAxis-r19 INTEGER (0..33554431), horizHelmertMolodenskiQuality-r19 INTEGER (0..7), vertHelmertMolodenskiQuality-r19 INTEGER (0..7),

[0553] }

[0554] - ASN1STOP

[0555]

[0556]

[0557] Helmert / Molodenski transformation, see Figure 3.5-3 of [xx]. Scale factor 2 arc seconds, i

[0558]

[0559]

[0560] , These fields specify semi-minor axis of the source and target system ellipsoid, encoded i

[0561]

[0562] NOTE 1 : Maximum approximation error of the Helmert / Molodenski transformation in the table below:

[0563] Relationship between Helmert / Molodenski quality indicator and physical quantity

[0564] <

[0565] < <

[0566] < <

[0567] < <

[0568] < <

[0569] < <

[0570] <

[0571]

[0572] CoordTransTimeDepLinExprHelmert

[0573] The IE CoordTransTimeDepLinExprHelmert specifies the time-dependent linear expression of the Helbert Transformation as specified in message 1301 in [xx],

[0574] - ASN1 START

[0575] CoordT ransTimeDepLinExprHelmert-r19 :: = SEQUENCE {

[0576] referenceEpoch-r19 INTEGER (0..65535),

[0577] xTranslation-r19 INTEGER (-4194303..4194303), yTranslation-r19 INTEGER (-4194303..4194303), zTranslation-r19 INTEGER (-4194303..4194303), xRotation-r19 INTEGER (-2147483647.. 2147483647), yRotation-r19 INTEGER (-2147483647.. 2147483647), zRotation-r19 INTEGER (-2147483647.. 2147483647), scaleCorrection-r19 INTEGER (-16777215..16777215), dot-xTranslation-r19 INTEGER (-65535..65535),

[0578] dot-yTranslation-r19 INTEGER (-65535..65535),

[0579] dot-zTranslation-r19 INTEGER (-65535..65535),

[0580] dot-xRotation-r19 INTEGER (-65535..65535),

[0581] dot-yRotation-r19 INTEGER (-65535..65535),

[0582] dot-zRotation-r19 INTEGER (-65535..65535),

[0583] dot-scaleCorrection-r19 INTEGER (-8191..8191),

[0584] }

[0585] - ASN1STOP

[0586]

[0587] CoordTransResidualEllipsoidalGridRepr

[0588] The IE CoordTransResidualEllipsoidalGridRepr specifies residuals with an ellisoid grid representation as part of the coordinate transformation as specified in message 1023 in [xx], - ASN1 START

[0589] CoordTransResidualEllipsoidalGridRepr-r19 ::= SEQUENCE {

[0590] horizontalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP verticalShift-r19 ENUMERATED { true } OPTIONAL, -- Need OP g ridOrigi n Latitude- r19 INTEGER (-648000..648000),

[0591] gridOriginLongitude-r19 INTEGER (-1296000..1296000),

[0592] grid-N-S-Delta-r19 INTEGER (0..4095),

[0593] grid-E-W-Delta-r19 INTEGER (0..4095),

[0594] meanLatOffset-r19 INTEGER (-127..127),meanl_ongOffset-r19 INTEGER (-127..127), meanHeightOffset-r19 INTEGER (-16383..16383), ellipsoidalGridResiduals-r19 SEQUENCE (SIZE(16)) OF EllipsoidalGridResidualElements-r19, horizlnterpMethodlndicator-r19 INTEGER (0..3), vertlnterpMethodlndicator-r19 INTEGER (0..3), horizResidualQualitylndicator-r19 INTEGER (0..7), vertResidualQualitylndicator-r19 INTEGER (0..7), modifiedJulianDayNumber-r19 INTEGER (0..65535),

[0595] EllipsoidalGridResidualElements-r19 ::= SEQUENCE {

[0596] residualLat-r19 INTEGER (-255..255), residualLong-r19 INTEGER (-255..255), residualHeight-r19 INTEGER (-255..255),

[0597] }

[0598] - ASN1STOP

[0599]

[0600] Es CoordTransHelmertAbrMolodenskiBadekas or CoordTransTimeDepLinExprHelmert. i

[0601]

[0602] These fields specify the mean height offset over the grid. Scale factor 0.01 m. If the field i heightindicator of IE CoordTransHelmertAbrMolodenskiBadekas is equal to 2, the height offset is in the source CRS, otherwise it is in target CRS. eilipsoidalGridResiduais

[0603]

[0604] This field specifies the grid with residuals. The grid contains 16 grid points, with the first i

[0605]

[0606]

[0607] NOTE 1 : Maximum approximation error of the transformation and grid adjustments in the table below:

[0608] Relationship between quality indicator and physical quantity after grid adjustments

[0609] <

[0610] < <

[0611] < <

[0612] < <

[0613] < <

[0614] < <

[0615] <

[0616]

[0617] CoordTransResidualPlaneGridRepr

[0618] The IE CoordTransResidualPlaneGridRepr specifies residuals with a plane grid representation as part of the coordinate transformation as specified in message 1024 in [xx], - ASN1 START

[0619] CoordTransResidualPlaneGridRepr-r19 ::= SEQUENCE {horizontalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP verticalShift-r19 ENUMERATED { true } OPTIONAL, - Need OP g ridOrigi n North ing- r19 INTEGER (-16777215..16777215), gridOriginEasting-r19 INTEGER (0..67108863),

[0620] grid-N-S-Delta-r19 INTEGER (0..4095),

[0621] grid-E-W-Delta-r19 INTEGER (0..4095),

[0622] meanLocalNorthingOffset-r19 INTEGER (-511..511), meanLocalEastingOffset-r19 INTEGER (-511..511), meanLocalHeightOffset-r19 INTEGER (-16383..16383),

[0623] planeGridResiduals-r19 SEQUENCE (SIZE(16)) OF PlaneGridResidualElements-r19, horizlnterpMethodlndicator-r19 INTEGER (0..3),

[0624] vertlnterpMethodlndicator-r19 INTEGER (0..3), horizResidualQualitylndicator-r19 INTEGER (0..7),

[0625] vertResidualQualitylndicator-r19 INTEGER (0..7),

[0626] modifiedJulianDayNumber-r19 INTEGER (0..65535),

[0627] Plane

[0628]

[0629] - ASN1STOPCoordTransResidualPlaneGridRepr field descriptions horizontalShift, verticalshift These fields specify whether horizontal and vertical shifts, respectively, are considered. gridOriginNorthing, gridOriginLongitude This field specifies Northing and Easting, respectively, of the grid origin in meters, see Figure 3.5-4 of [xx]. Coordinates defined in local system after projection. Scale factor

[0630]

[0631] 10m.

[0632] grid-N-S Delta, grid-E-W Delta ] These fields specify grid delta between adjacent grid points in north-south and east-west i directions, respectively, in meters, see Figure 3.5-4 of [xx]. Scale factor 10m and value 0 i is undefined. Delta coordinates defined in local system after projection. meanLocalNorthingOffset, meanLocalEastingOffset

[0633]

[0634] These fields specify the mean offset of Northing and Easting, respectively, over the local i system grid. Scale factor 0. meanLocalHeightOffset These fields specify the me

[0635]

[0636] m. If the field heightindicator of IE CoordTransHelmertAbrMolodenskiBadekas is equal to i

[0637]

[0638] planeGridResiduals

[0639] This field secifies the local sstem rid with residuals The rid contains 16 rid oints

[0640]

[0641] This field specifies the residual height for the grid point / . Scale factor 0.001 m. If the field i

[0642]

[0643] 3: reserved i

[0644] i

[0645]

[0646] CoordTransProjection TypesBaseline

[0647] The IE CoordTransProjectionTypesBaseline specifies a baseline set of projection types as specified in message 1025 in [xx], and with definitions of projections in [aa],

[0648] - ASN1 START

[0649] CoordTransProjectionTypesBasehne-r19 ::= SEQUENCE {

[0650] projectionType-r19 ENUMERATED { unknown, tm, tms, Icdsp, Iccw, cs, om, os, me, ps, ds, ...}, latNaturalOrigin-r19 INTEGER (-8181818181.. 8181818181), longNaturalOrigin-r19 INTEGER (-16363636362.. 16363636362), scaleFactorNaturalOrigin-r19 INTEGER (0..1073741823),

[0651] falseNorthing-r19 INTEGER (0..68719476735),

[0652] falseEasting-r19 INTEGER (0..17179869183),

[0653] }

[0654] - ASN1STOP

[0655]

[0656] 9806. | os: Oblique Stereographic (OS), [aa] 1.4.7.1 EPSG dataset coordinate operation method code 9809.

[0657] me: Mercator (MC), [aa] 1.4.3 EPSG dataset coordinate operation method code 9804 i or 9805. i ps: Polar Stereographic (PS), [aa] 1.4.7.2 EPSG dataset coordinate operation method i

[0658]

[0659] latNaturalOrigin

[0660] This field secifies latitude of the natural oriin in derees for rojection methods TM

[0661]

[0662] CoordTransProjectionLambertConicConformal

[0663] The IE CoordTransProjectionLambertConicConformal specifies a Lambert conic conformal projection as specified in message 1026 in [xx], and with definitions of projections in [aa], specifically 1.4.1.1 EPSG dataset coordinate operation method code 9802.

[0664] - ASN1 START

[0665] CoordTransProjectionLambertConicConformal-r19 ::= SEQUENCE {

[0666] projectionType-r19 ENUMERATED { Icc2sp, ...},

[0667]

[0668] }

[0669] - ASN1ST0P

[0670]

[0671] CoordTransProjectionObliqueMercator

[0672] The IE CoordTransProjectionObliqueMercator specifies a oblique mercator projection as specified in message 1027 in [xx], and with definitions of projections in [aa], specifically 1.4.6 EPSG dataset coordinate operation method code 9815.

[0673] - ASN1 START

[0674] CoordTransProjectionObliqueMercator-r19 ::= SEQUENCE {

[0675] projectionType-r19 ENUMERATED { om, ...},

[0676] rectificationFlag-r19 ENUMERATED { true }, OPTIONAL - Need OP

[0677]

[0678] - ASN1STOP

[0679]

[0680] ,

[0681]

[0682]

[0683] 6.4.2 Common Positioning

[0684] [■ ■ ■]

[0685] CommonlEsProvideCapabilities

[0686] The CommonlEsProvideCapabilities carries common lEs for a Provide Capabilities LPP message Type.

[0687] - ASN1 STARTCommonlEsProvideCapabilities ::= SEQUENCE {

[0688] [[

[0689] segmentationlnfo-r14 Segmentationlnfo-r14 OPTIONAL, -- Cond Segmentation Ipp-message-segmentation-r14 BIT STRING { serverToTarget (0),

[0690] targetToServer(l) } OPTIONAL ]].

[0691] [[

[0692] remoteUE-lndication-r18 BOOLEAN OPTIONAL, - Cond NR locationEstimateAndMeasurementReporting-r18

[0693] ENUMERATED { supported } OPTIONAL ]].

[0694] [[

[0695] coordTransformations-r19 ENUMERATED { supported } OPTIONAL

[0696] - ASN1STOP

[0697]

[0698]

[0699] CommonlEsRequestAssistanceData

[0700] The CommonlEsRequestAssistanceData carries common lEs for a Request Assistance Data LPP message Type.

[0701] - ASN1 START

[0702] CommonlEsRequestAssistanceData ::= SEQUENCE {

[0703] [[

[0704] coordT ransformationsReq-r19 CoordinateT ransformationsReq-r19 OPTIONAL ]]

[0705] }- ASN1STOP

[0706]

[0707] CommonlEsProvideAssistanceData

[0708] The CommonlEsProvideAssistanceData carries common IBs for a Provide Assistance Data LPP message Type.

[0709] - ASN1 START

[0710] CommonlEsProvideAssistanceData ::= SEQUENCE {

[0711] [[

[0712] coordTransformations-r19 CoordinateTransformations-r19 OPTIONAL -- Need OP ]]

[0713] }

[0714] - ASN1STOP

[0715] coordTransformations i This field provides coordinate transformations information.

[0716]

[0717] [■ ■ ■]

[0718] CommonlEsProvideLocationlnformation

[0719] The CommonlEsProvideLocationlnformation carries common lEs for a Provide Location Information LPP message Type.

[0720] - ASN1 START

[0721] CommonlEsProvideLocationlnformation ::= SEQUENCE {

[0722] [[

[0723] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL ]]}

[0724]

[0725] NOTE: Void.

[0726] [■■■]

[0727] CommonlEsError

[0728] The CommonlEsError carries common lEs for an Error LPP message Type.

[0729] - ASN1 START

[0730] CommonlEsError ::= SEQUENCE {

[0731] errorCause ENUMERATED {

[0732] undefined,

[0733] IppMessageHeaderError,

[0734] IppMessageBodyError,

[0735] epduError,

[0736] incorrectDataValue,

[0737] lppSegmentationError-v1450,

[0738] IppCrsNotSupported-rl 9,

[0739] IppCrsT ransformationNotSupported-r19

[0740] }

[0741] }

[0742] - ASN1STOP

[0743]

[0744]

[0745] 6.4.3 Common NR Positioning Information Elements

[0746] [■ ■ ■]

[0747] NR-Position CalculationAssistance

[0748] The IE NR-PositionCalculationAssistance is used by the location server to provide assistance data including integrity information to enable UE-based downlink positioning. - ASN1 START

[0749] NR-PositionCalculationAssistance-r16 ::= SEQUENCE {

[0750] [[

[0751] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL -- Need ON ]]

[0752] }

[0753] - ASN1STOP

[0754]

[0755] i This field specifies the coordinate reference system (CRS) the location coordinates are i related to in this IE If not present, the coordinates are defined as specified in the

[0756]

[0757] NEXT CHANGE

[0758] 6.5.2.2 GNSS Assistance Data Elements

[0759] [■■■]

[0760] GNSS-RTK-ReferenceStationlnfo

[0761] The IE GNSS-RTK-ReferenceStationlnfo is used by the location server to provide the Earthcentered, Earth-fixed (ECEF) coordinates of the antenna reference point (ARP) of the stationary reference station for which the GNSS-RTK-Observations assistance data are provided together with reference station antenna description.

[0762] The parameters provided in IE GNSS-RTK-ReferenceStationlnfo are used as specified for message type 1006, 1033 and 1032 in

[0030] ,

[0763] - ASN1 START

[0764] GNSS-RTK-ReferenceStationlnfo-r15 ::= SEQUENCE {

[0765] [[

[0766] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL -- Need ON ]]

[0767] }

[0768] - ASN1STOP

[0769]

[0770] i This field specifies the coordinate reference system (CRS) the location coordinates of

[0771]

[0772] [■■■]

[0773] GNSS-SSR-CorrectionPoints

[0774] The IE GNSS-SSR-CorrectionPoints is used by the location server to provide a list of correction point coordinates or an array of correction points ("grid") for which the GNSS-SSR-GriddedCorrection are valid.

[0775] - ASN1 START

[0776] GNSS-SSR-CorrectionPoints-r16 ::= SEQUENCE {

[0777] correctionPointSetlD-r16 INTEGER (0..16383),

[0778] correctionPoints-r16 CHOICE {HstOfCorrectionPoints-r16 GNSS-SSR-ListOfCorrectionPoints-r16, arrayOfCorrectionPoints-r16 GNSS-SSR-ArrayOfCorrectionPoints-r16 }.

[0779] [[

[0780] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL - Need OP ]]

[0781] }

[0782] GNSS-SSR-ListOfCorrectionPoints-r16 ::= SEQUENCE {

[0783] referencePointLatitude-r16 INTEGER (-16384..16383), referencePointLongitude-r16 INTEGER (-32768..32767), relativeLocationsList-r16 SEQUENCE (SIZE (0..63)) OF RelativeLocationElement-r16,

[0784] }

[0785] RelativeLocationElement-r16 ::= SEQUENCE {

[0786] deltal_atitude-r16 INTEGER (-512..511),

[0787] deltal_ongitude-r16 INTEGER (-1024..1023),

[0788] }

[0789] GNSS-SSR-ArrayOfCorrectionPoints-r16 ::=SEQUENCE {

[0790] referencePointl_atitude-r16 INTEGER (-16384..16383), referencePointl_ongitude-r16 INTEGER (-32768..32767), numberOfStepsLatitude-r16 INTEGER (0..63),

[0791] numberOfStepsLongitude-r16 INTEGER (0..63),

[0792] stepOfl_atitude-r16 INTEGER (1..511),

[0793] stepOfl_ongitude-r16 INTEGER (1..1023),

[0794] bitmaskOfGrids-r16 BIT STRING (SIZE(64)) OPTIONAL, - Need OP

[0795] }

[0796] - ASN1STOP

[0797]

[0798] GNSS-LOS-NLOS-GridPoints

[0799] The IE GNSS-LOS-NLOS-GridPoints is used by the location server to provide a list of grid point coordinates or an array of correction points ("grid") for which specific assistance data can be provided.

[0800] - ASN1 START

[0801] GNSS-LOS-NLOS-GridPoints-r18 ::= SEQUENCE {

[0802] [[

[0803] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL -- Need OP ]]

[0804] }

[0805] - ASN1STOP

[0806]

[0807] GNSS-SSR-OrbitCorrections

[0808] The IE GNSS-SSR-OrbitCorrections is used by the location server to provide radial, along-track and cross-track orbit corrections together with integrity information. The target device may use the SSR-OrbitCorrectionList to compute a satellite position correction to be combined with the satellite position calculated from broadcast ephemeris.

[0809] The parameters provided in IE GNSS-SSR-OrbitCorrections - except for ORBIT-IntegrityParameters and SSR-lntegrityOrbitBounds - are used as specified for SSR Orbit Messages (e.g., message type 1057 and 1063) in

[0030] and apply to all GNSSs.

[0810] - ASN1 STARTGNSS-SSR-OrbitCorrections-r15 ::= SEQUENCE {

[0811] [[

[0812] locationCRS-r19 CoordinateReferenceSystem-r19 OPTIONAL - Need ON ]]

[0813] locationCRS ]

[0814]

[0815]

[0816] 6.5.2.9 GNSS Capability Information

[0817] A-GNSS-ProvideCapabilities

[0818] The IE A-GNSS-Provide-Capabilities is used by the target device to indicate its capability to support A-GNSS and to provide its A-GNSS location capabilities (e.g., GNSSs and assistance data supported) to the location server.

[0819] - ASN1 START

[0820] A-GNSS-ProvideCapabilities ::= SEQUENCE {

[0821] [[

[0822] location-CRS-Supported-r19 ENUMERATED { true } OPTIONAL ]]

[0823] }

[0824] - ASN1STOP

[0825]

[0826]

[0827] 6.5.10.6 NR DL-TDOA Capability Information

[0828] NR-DL- TD OA-Provide Capabilities

[0829] The IE NR-DL-TDOA-ProvideCapabilities is used by the target device to indicate its capability to support NR DL-TDOA and to provide its NR DL-TDOA positioning capabilities to the location server.

[0830] - ASN1 START

[0831] NR-DL-TDOA-ProvideCapabilities-r16 ::= SEQUENCE {

[0832] [[

[0833] locationCoordinateTypes-r18 LocationCoordinateTypes

[0834] ]]

[0835] }

[0836] - ASN1STOP

[0837]

[0838]

[0839] 7.2 Mapping of posSibType to assistance data element

[0840] The supported posSibType's are specified in Table 7.2-1. The GNSS Common and Generic Assistance Data lEs are defined in clause 6.5.2.2. The OTDOA Assistance Data lEs and NR DL-TDOA / DL-AoD Assistance Data lEs are defined in clause 7.4.2. The Barometric Assistance Data lEs are defined in clause 6.5.5.8. The TBS (based on MBS signals) Assistance Data lEs are defined in clause 6.5.4.8. The Coordinate Reference System and Transformations lEs are defined in clause 6.4.1.

[0841] Table 7.2-1: Mapping of posSibType to assistanceDataElement

[0842]

[0843]

[0844] In view of the modifications and variations herein, Figure 15 depicts a method performed by a communication node 12A, 12B in accordance with particular embodiments. The method includes transmitting signaling 16-1 to, and / or receiving signaling 16-2 from, another communication node 12B, 12A regarding which coordinate reference system, CRS, 18 and / or which CRS transformation 18T to use for location coordinates 14 communicated between the communication nodes 12A, 12B (Block 1500).

[0845] In some embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation to use for location coordinates communicated between the communication nodes as part of location information indicating a location of a target node. In other embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation to use for location coordinates communicated between the communication nodes alternatively or additionally as part of assistance data for assistance with determining the location information.

[0846] In some embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation is to be used, or has been used, for location coordinates communicated between the communication nodes.

[0847] In some embodiments, said transmitting and / or receiving comprises transmitting a request 26-1 for information to the other communication node. In some embodiments, the requested information includes location coordinates, and the request indicates which CRS is requested to be used for the location coordinates. In other embodiments, said transmitting and / or receiving comprises alternatively or additionally receiving a response 26-2 to the request from the other communication node. In some embodiments, the response comprises an acknowledgement that the other communication node supports and / or will use the requested CRS for the location coordinates. In other embodiments, the response comprises an indication of a different CRS that the other communication node supports and / or will use for the location coordinates. In yet other embodiments, the response comprises an error indication indicating that the other communication node does not support the requested CRS.In some embodiments, transmitting and / or receiving comprises receiving a request for information from the other communication node. In some embodiments, the requested information includes location coordinates, and the request indicates which CRS is requested to be used for the location coordinates. In other embodiments, transmitting and / or receiving comprises alternatively or additionally transmitting a response to the request to the other communication node. In some embodiments, the response comprises an acknowledgement that the communication node supports and / or will use the requested CRS for the location coordinates. In other embodiments, the response comprises an indication of a different CRS that the communication node supports and / or will use for the location coordinates. In yet other embodiments, the response comprises an error indication indicating that the communication node does not support the requested CRS. In some embodiments, the request also indicates a baseline CRS to be used for the location coordinates in case the requested CRS is not supported. In some embodiments, different CRS is the baseline CRS. In some embodiments, the different CRS is different than the requested CRS and is different than the baseline CRS. In some embodiments, the requested information is location information that comprises location coordinates of a target node. In some embodiments, the requested information is assistance data that assists with determining a location of a target node. In some embodiments, the method further comprises transmitting or receiving the requested information with location coordinates in the requested CRS or the different CRS In some embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation one or both of the communication nodes is capable of using for location coordinates communicated between the communication nodes.

[0848] In some embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, the other communication node indicating which CRS and / or which CRS transformation the communication nodes is capable of using for location coordinates communicated between the communication nodes. In other embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, the other communication node indicating alternatively or additionally which CRS and / or which CRS transformation the other communication nodes is capable of using for location coordinates communicated between the communication nodes.

[0849] In some embodiments, said transmitting and / or receiving comprises transmitting, to the other communication node, a request 30-1 for capability information. In some embodiments, the capability information includes CRS capability information indicating which CRS and / or which CRS transformation the other communication node is capable of using for location coordinates communicated between the communication nodes. In other embodiments, said transmitting and / or receiving comprises alternatively or additionallyreceiving, from the other communication node, a response 30-2 to the request comprising the requested capability information.

[0850] In some embodiments, said transmitting and / or receiving comprises receiving, from the other communication node, a request for capability information. In other embodiments, said transmitting and / or receiving comprises alternatively or additionally transmitting, to the other communication node, a response to the request comprising the requested capability information. In some embodiments, the capability information includes CRS capability information indicating which CRS and / or which CRS transformation the other communication node is capable of using for location coordinates communicated between the communication nodes. In some embodiments, the CRS capability information is specific to one or more methods for determining a location of a target node. In other embodiments, the CRS capability information is alternatively or additionally specific to a target-based mode in which the target node determines its own location or specific to a target-assisted mode in which the target node reports measurements based on which another node determines the location of the target node. In some embodiments, said transmitting and / or receiving further comprises transmitting to the other communication node, or receiving from the other communication node, a request for information. In some embodiments, the requested information comprises location coordinates. In some embodiments, the request indicates which CRS is requested to be used for the location coordinates. In some embodiments, the indicated CRS is based on the CRS capability information. In some embodiments, said transmitting and / or receiving further comprises transmitting to the other communication node, or receiving from the other communication node, information that comprises location coordinates in a CRS that, according to the CRS capability information, one or more of the communication nodes is capable of using for the location coordinates. In some embodiments, the information is location information that comprises location coordinates of a target node. In some embodiments, the information is assistance data that assists with determining a location of a target node. In some embodiments, the request for capability information comprises an A-GNSS-RequestCapabilities Information Element (IE) that requests A-GNSS location capabilities. In some embodiments, the response to the request comprises an A-GNSS-ProvideCapabilities IE that indicates A-GNSS location capabilities, wherein the A-GNSS-location capabilities convey CRS capability information. In some embodiments, the CRS capability information indicates whether or not the communication node providing the CRS capability information supports location coordinates provided in a CRS, indicated together with A-GNSS assistance data. In some embodiments, inclusion of a location-CRS-Supported IE in the A-GNSS-ProvideCapabilities IE indicates that the communication node providing the CRS capability information supports location coordinates provided in a CRS, indicated together with A-GNSS assistance data. In other embodiments, alternatively or additionally,exclusion of the location-CRS-Supported IE from the A-GNSS-ProvideCapabilities IE indicates that the communication node providing the CRS capability information does not support location coordinates provided in a CRS, indicated together with A-GNSS assistance data.

[0851] In some embodiments, the request for information is a Request Location Information LPP message. In some embodiments, the Request Location Information LPP message includes a CommonlEsRequestLocationlnformation IE that carries common lEs for the Request Location Information LPP message. In some embodiments, the CommonlEsRequestLocationlnformation IE includes a locationCRS IE that specifies a CRS location coordinates are requested to be provided in. In some embodiments, the Request Location Information LPP message includes a CommonlEsRequestLocationlnformation IE that carries common lEs for the Request Location Information LPP message. In some embodiments, exclusion of a locationCRS IE from the CommonlEsRequestLocationlnformation IE indicates that location coordinates are expected to be provided in a baseline CRS. In some embodiments, the response to the request comprises a Provide Location Information LPP message. In some embodiments, the Provide Location Information LPP message includes a CommonlEsProvideLocationlnformation IE that carries common lEs for the Provide Location Information LPP message. In some embodiments, the CommonlEsProvideLocationlnformation IE includes a locationCRS IE that specifies a CRS location coordinates are related to. In some embodiments, the Provide Location Information LPP message includes a CommonlEsProvideLocationlnformation IE that carries common lEs for the Provide Location Information LPP message. In some embodiments, exclusion of a locationCRS IE from the CommonlEsProvideLocationlnformation IE indicates that location coordinates are related to a baseline CRS.

[0852] In some embodiments, the request for information is a Request Assistance Data LPP message that requests assistance data comprising a CRS transformation between a source CRS and a target CRS. In some embodiments, the Request Assistance Data LPP message includes a CommonlEsRequestAssistanceData IE. In some embodiments, the CommonlEsRequestAssistanceData IE includes a coordTransformationsReq field that indicates a request for coordinate transformations between a set of source and target CRSs. In some embodiments, the response is a Provide Assistance Data LPP message. In some embodiments, the Provide Assistance Data LPP message includes a coordTransformations field that provides coordinate transformations information.

[0853] In some embodiments, the response comprises the error indication. In some embodiments, the request for information is a Request Location Information LPP message or a Request Assistance Data LPP message, and the response is an Error LPP message. Insome embodiments, the Error LPP message includes a CommonlEsError IE that indicates a cause of the Error LPP message as being that the requested CRS is not supported. In other embodiments, the Error LPP message includes a CommonlEsError IE that indicates a cause of the Error LPP message as being that the requested CRS transformation is not supported.

[0854] In some embodiments, the request is a Determine Location Request on an Nlmf Service Based Interface. In some embodiments, the Determine Location Request includes an InputData structured data type. In some embodiments, the InputData structured data type includes a requestedCRS IE that indicates a CRS in which location coordinates are requested.

[0855] In some embodiments, the response is a Determine Location Response on an Nlmf Service Based Interface. In some embodiments, the Determine Location Response includes an LocationData structured data type. In some embodiments, the LocationData structured data type includes a usedCRS IE that indicates a CRS in which location coordinates are provided.

[0856] In some embodiments, the request is a TRP Information Request requesting location information for transmission reception points (TRPs) hosted by the communication node that receives the request. In some embodiments, the TRP Information Request includes a requestedCRS IE that indicates the requested CRS.

[0857] In some embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node regarding whether to use a regional CRS or global CRS for location coordinates communicated between the communication nodes.

[0858] In some embodiments, said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node regarding a CRS transformation to be used for transforming location coordinates from a source CRS to a target CRS before communicating the location coordinates between the communication nodes.

[0859] In some embodiments, at least one of the communication nodes is a communication device.

[0860] In some embodiments, at least one of the communication nodes is a network node. In some embodiments, at least one of the communication nodes is a radio network node.

[0861] In some embodiments, at least one of the communication nodes is a location server. In some embodiments, the method further comprises communicating location coordinates between the communication nodes according to the transmitted signaling and / or the received signaling (Block 1510).Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a communication node 12A, 12B configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B.

[0862] Embodiments also include a communication node 12A, 12B comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B. The power supply circuitry is configured to supply power to the communication node 12A, 12B.

[0863] Embodiments further include a communication node 12A, 12B comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B. In some embodiments, the communication node 12A, 12B further comprises communication circuitry.

[0864] Embodiments further include a communication node 12A, 12B comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication node 12A, 12B is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B.

[0865] Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio frontend circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication node 12A, 12B. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UEthat has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

[0866] More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory,which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0867] Figure 16 for example illustrates a communication node 12A, 12B as implemented in accordance with one or more embodiments. As shown, the communication node 12A, 12B includes processing circuitry 1610 and communication circuitry 1620. The communication circuitry 1620 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication node 1600. The processing circuitry 1610 is configured to perform processing described above, e.g., in Figure 15, such as by executing instructions stored in memory 1630. The processing circuitry 1610 in this regard may implement certain functional means, units, or modules.

[0868] Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0869] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

[0870] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0871] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0872] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0873] Figure 17 shows an example of a communication system 1700 in accordance with some embodiments.In the example, the communication system 1700 includes a telecommunications network 1702 that includes an access network 1704, such as a radio access network (RAN), and a core network 1706, which includes one or more core network nodes 1708. The access network 1704 includes one or more access network nodes or base stations of various types, access network nodes 1710A and 1710B are depicted (which may be collectively referred to as network nodes 1710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1704 may include more than one access network technology. The network nodes 1710 of access network 1704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 1712A, 1712B, 1712C, and 1712D (one or more of which may be generally referred to as UEs 1712) to the core network 1706 over one or more wireless connections.

[0874] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1702, including one or more access network nodes 1710 and / or core network nodes 1708.

[0875] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.The network nodes 1710 facilitate direct or indirect connection of one or more UEs 1712 to the core network 1706 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1700 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0876] The UEs 1712 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1710 and other communication devices. Similarly, the network nodes 1708, 1710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1702) with the UEs 1712 and / or with other network nodes or equipment in the telecommunications network 1702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1702. More specifically, UEs 1712 may send messages, data, and / or other signals to network nodes 1708, 1710 or other elements of the telecommunications network 1702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1708, 1710 may send messages, data, and other signals to UEs 17122, other network nodes 1708, 1710, and other devices in telecommunications network 1702 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1712 by transmitting the message to an access network node 1710 that will then transmit the message to the intended UE 1712. Similarly, a core network node 108 may receive a particular message from a UE 1712 by receiving the message from an access network node 1710 that itself received the message from the UE 1712.

[0877] In the depicted example, the core network 1706 connects elements of the access network 1704 (e.g., one or more of the network nodes 1710) to one or more host computing systems, such as host 1716. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1706 includes one or more core network nodes (e.g., corenetwork node 1708) of various types, one or more of which may be generally referred to as network nodes 1708. Network nodes 1708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1708. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0878] The host 1716 may be under the ownership or control of a service provider other than an operator or provider of the access network 1704 and / or the telecommunications network 1702. The host 1716 may be operated by the service provider or on behalf of the service provider. The host 1716 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0879] As a whole, the communication system 1700 of Figure 17 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1700 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1700 supporting different standards, protocols, or rule sets.

[0880] As one example, in certain embodiments, access network 1704 may contain some access network nodes 1710 that support 3GPP radio access technologies (RAT), such asLTE or NR, while other access network nodes 1710 support (or the same access network nodes 1710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0881] Telecommunications network 1702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1702. For example, the telecommunications network 1702 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0882] In some examples, one or more of the UEs 1712 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1704. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0883] In the example, the hub 1714 communicates with the access network 1704 to facilitate indirect communication between one or more UEs (e.g., UE 1712C and / or 1712D) and network nodes (e.g., network node 1710B). In some examples, the hub 1714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1714 may be a broadband router enabling access to the core network 1706 for the UEs. As another example, the hub 1714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1710, or by executable code, script, process, or other instructions in the hub 1714.

[0884] As another example, the hub 1714 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1714 may retrieve VR assets, video, audio, or other media or data related to sensory information via anetwork node, which the hub 1714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0885] The hub 1714 may have a constant / persistent or intermittent connection to the network node 171 OB. The hub 1714 may also allow fora different communication scheme and / or schedule between the hub 1714 and UEs (e.g., UE 1712C and / or 1712D), and between the hub 1714 and the core network 1706. In other examples, the hub 1714 is connected to the core network 1706 and / or one or more UEs via a wired connection.

[0886] Moreover, the hub 1714 may be configured to connect to an M2M service provider over the access network 1704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1710 while still connected via the hub 1714 via a wired or wireless connection. In some embodiments, the hub 1714 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 171 OB. In other embodiments, the hub 1714 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 171 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0887] Figure 18 is another example of a communication system 1800 according to some embodiments. As used herein, the communication system 1800 includes multiple access points (APs) 1810 (with four exemplary APs 1810A, 1810B, 1810C, and 1810D being depicted) and multiple wireless devices, referred to in the context of communication system 1800 as stations (ST As) 1812 (referred to individually as STA 1812A, STA 1812B, STA 1812C, STA 1812D, and STA 1812E). STA 1812A is served byAP 1810A in a first basic service set (BSS) 1820A. STA 1810B and STA 1810C are served by AP 1810B in a second BSS, BSS 1820B. STA 1812D is served byAP 1810C in a third BSS, BSS 1820C. STA 1812E is served by AP 1810D in a fourth BSS, BSS 1820D. Stations 1812 may be non-AP ST As and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0888] Each of STAs 1812 may connect through a radio link to one of APs 1810. For example, depending on location or channel conditions experienced by a given STA 1812, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriersfrom a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0889] Each AP 1810 may provide data connectivity to ST As 1812 connected to a particular AP 1810. As illustrated, APs 1810 may be connected to a data network 1830. In this way, APs 1810 may also provide data connectivity between STAs 1812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1812 and its serving AP 1810 may be used for providing various kinds of services to STA 1812, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1812 and / or on a device linked to STA 1812. Byway of example, Figure 18 illustrates an application service platform 1832 provided in data network 1830. The application(s) executed on STA 1812 and / or on one or more other devices linked to STA 1812 may use the radio link for data communication with one or more other STA 1812 and / or the application service platform 1832, thereby enabling utilization of the corresponding service(s) at STA 1812.

[0890] Figure 19 shows a wireless device 1900, which may be configured to operate in communication system 1700 of Figure 17 or in communication system 1800 of Figure 180. The wireless device 1900 may be alternatively referred to as a UE 1900, like a UE 1712 within the context of communication system 1700, or as a station (STA) 1900 or as a non-access-point station (non-AP STA) 1900, like a STA 1812 within the context of the communication system 1800, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0891] A wireless device 1900 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle-to-everything (V2X). In other examples, wireless device 1900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1900 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 1900 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0892] In particular embodiments, wireless device 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input / output interface 1906, a power source 1908, a memory 1910, a communication interface 1912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1900 may include all or a subset of the components shown in Figure 19. The level of integration between the components may vary from one embodiment of wireless device 1900 to another. In general, in a particular embodiment of wireless device 1900, processing circuitry 1902, input / output interface 1906, power source 1908, memory 1910, and communication interface 1912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1900. Further, certain embodiments of wireless devices 1900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0893] The processing circuitry 1902 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1910. The processing circuitry 1902 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1902 may include multiple central processing units (CPUs).

[0894] In the example, the input / output interface 1906 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 1900. Examples of an input device include a touch-sensitive or presencesensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera,etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0895] In some embodiments, the power source 1908 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 1908 may further include power circuitry for delivering power from the power source 1908 itself, and / or an external power source, to the various parts of wireless device 1900 via input circuitry or an interface such as an electrical power cable. Power source 1908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1900 to which power is supplied.

[0896] The memory 1910 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1910 includes one or more programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916. The memory 1910 may store, for use by wireless device 1900, any of a variety of various operating systems or combinations of operating systems.

[0897] The memory 1910 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) ora removable UICC commonly known as ‘SIM card.’ The memory 1910 may allow wireless device 1900 to access instructions, programs and the like, stored on transitory or non-transitory memorymedia, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1910, which may be or comprise a device-readable storage medium.

[0898] The processing circuitry 1902 may be configured to communicate with an access network or other network via or using the communication interface 1912. The communication interface 1912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1922. The communication interface 1912 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 1918 and / or a receiver 1920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1918 and receiver 1920 may be coupled to one or more antennas (e.g., antenna 1922) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0899] In the illustrated embodiment, communication functions of the communication interface 1912 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0900] In particular embodiments, wireless device 1900 may provide an output of data captured via a sensor, through its communication interface 1912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1900 can be communicated through a wireless connection to a network node via another wireless device 1900. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).As another example, wireless device 1900 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 1900 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0901] Wireless device 1900, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 1900 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 1900 shown in Figure 19.

[0902] As yet another specific example, in an loT scenario, wireless device 1900 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 1900 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 1900 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 1900 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0903] In practice, any number of wireless devices 1900 may be used together with respect to a single use case. For example, a first wireless device 1900 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1900 that is a remote controller operating the drone. When a usermakes changes from the remote controller, the first wireless device 1900 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 1900 can also include more than one of the functionalities described above. For example, wireless device 1900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0904] Figure 20 shows a network node 2000 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 2000 may be configured to operate in communication system 1700 of Figure 17, like network nodes 1708 or 1710, or in communication system 1800 of Figure 18, like an AP 1810 or a station 1812. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0905] Network nodes 2000 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 2000 may be a relay node or a relay donor node controlling a relay. Network nodes 2000 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0906] Other examples of network nodes 2000 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0907] In particular embodiments, network node 2000 includes a processing circuitry 2002, a memory 2004, a communication interface 2006, and a power source 2008. In general, in a particular embodiment of network node 2000, processing circuitry 2002, memory 2004,communication interface 2006, and power source 2008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 2000.

[0908] The network node 2000 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 2000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 2000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 2004 or portions of memory 2004 for different RATs) and some components may be reused (e.g., a same antenna 2010 may be shared by different RATs). The network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 2000.

[0909] The processing circuitry 2002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 2004, to provide network node 2000 functionality.

[0910] In some embodiments, the processing circuitry 2002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of radio frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the RF transceiver circuitry 2012 and the baseband processing circuitry 2014 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 2012 and baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units.

[0911] The memory 2004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 2002. The memory 2004 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 2002 and utilized by the network node 2000. The memory 2004 may be used to store any calculations made by the processing circuitry 2002 and / or any data received via the communication interface 2006. In some embodiments, the processing circuitry 2002 and memory 2004 is integrated.

[0912] The communication interface 2006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 2006 comprises port(s) / terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1900 may be capable of wireless communication and communication interface 2006 may also include radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, an antenna 2010. Particular embodiments of radio front-end circuitry 2018 include filter(s) 2020 and amplifier(s) 2022. The radio front-end circuitry 2018 may be connected to an antenna 2010 and processing circuitry 2002. The radio front-end circuitry may be configured to condition signals communicated between antenna 2010 and processing circuitry 2002. The radio front-end circuitry 2018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 2018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 2020 and / or amplifiers 2022. The radio signal(s) may then be transmitted via the antenna 2010. Similarly, when receiving data, the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018. The digital data may be passed to the processing circuitry 2002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0913] In certain alternative embodiments, network node 2000 may be capable of wireless communication but does not include separate radio front-end circuitry 2018, instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes one or more ports or terminals 2016, the radio front-end circuitry 2018, and the RF transceiver circuitry 2012, as part of a radio unit (not shown), and thecommunication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown).

[0914] The antenna 2010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 2010 may be coupled to the radio front-end circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through one or more interfaces or ports.

[0915] The antenna 2010, communication interface 2006, and / or the processing circuitry 2002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 2000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 2010, the communication interface 2006, and / or the processing circuitry 2002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 2000. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0916] The power source 2008 provides power to the various components of network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein. For example, the network node 2000 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2008. As a further example, the power source 2008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0917] Embodiments of the network node 2000 may include additional components beyond those shown in Figure 20 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 2000 may include user interface equipment to allow input of information into the network node 2000 and to allow output of information from the network node 2000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2000.Figure 21 is a block diagram illustrating a virtualization environment 2100 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 2100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0918] Applications 2102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0919] Hardware 2104 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 2108A and VM 2108B (which may be collectively referred to as VMs 2108), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 2106 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 2108.

[0920] The VMs 2108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 2106. Different embodiments of the instance of a virtual appliance 2102 may be implemented on one or more of VMs 2108, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.In the context of NFV, each of the VMs 2108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 2108, and that part of hardware 2104 that executes thatVM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 2108 on top of the hardware 2104 and corresponds to an application 2102.

[0921] Hardware 2104 may be implemented in a standalone network node with generic or specific components. Hardware 2104 may implement some functions via virtualization. Alternatively, hardware 2104 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 2110, which, among others, oversees lifecycle management of applications 2102. In some embodiments, hardware 2104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 2112 which may alternatively be used for communication between hardware nodes and radio units.

[0922] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communicationinterface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0923] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0924] Generally, various embodiments herein may be enumerated as follows:

[0925] Group A Embodiments

[0926] A1. A method performed by a communication node, the method comprising:

[0927] transmitting signaling to, and / or receiving signaling from, another communication node regarding which coordinate reference system, CRS, and / or which CRS transformation to use for location coordinates communicated between the communication nodes.

[0928] A2. The method of embodiment A1 , wherein said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation to use for location coordinates communicated between the communication nodes:

[0929] as part of location information indicating a location of a target node; and / or as part of assistance data for assistance with determining the location information.

[0930] A3. The method of any of embodiments A1-A2, wherein said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation is to be used, is requested to be used, or has been used, for location coordinates communicated between the communication nodes.A4. The method of any of embodiments A1-A3, wherein said transmitting and / or receiving comprises:

[0931] transmitting a request for information to the other communication node, wherein the requested information includes location coordinates, and wherein the request is or comprises the transmitted signaling and indicates which CRS is requested to be used for the location coordinates; and / or

[0932] receiving a response to the request from the other communication node, wherein the response is or includes the received signaling and comprises: an acknowledgement that the other communication node supports, has used, and / or will use the requested CRS for the location coordinates; or an indication of a different CRS that the other communication node supports, has used, and / or will use for the location coordinates; or

[0933] an error indication indicating that the other communication node does not support the requested CRS.

[0934] A5. The method of any of embodiments A1-A3, wherein said transmitting and / or receiving comprises:

[0935] receiving a request for information from the other communication node, wherein the requested information includes location coordinates, and wherein the request is or includes the received signaling and indicates which CRS is requested to be used for the location coordinates; and / or

[0936] transmitting a response to the request to the other communication node, wherein the response is or includes the transmitted signaling and comprises: an acknowledgement that the communication node supports, has used, and / or will use the requested CRS for the location coordinates; or an indication of a different CRS that the communication node supports, has used, and / or will use for the location coordinates; or

[0937] an error indication indicating that the communication node does not support the requested CRS.

[0938] A6. The method of any of embodiments A4-A5, wherein the request also indicates a baseline CRS to be used for the location coordinates in case the requested CRS is not supported.

[0939] A7. The method of embodiment A6, wherein different CRS is the baseline CRS.

[0940] A8. The method of embodiment A6, wherein the different CRS is different than therequested CRS and is different than the baseline CRS.

[0941] A8. The method of any of embodiments A4-A8, wherein the requested information is location information that comprises location coordinates of a target node.

[0942] A9. The method of any of embodiments A4-A8, wherein the requested information is assistance data that assists with determining a location of a target node.

[0943] A11. The method of any of embodiments A4-A10, further comprising transmitting or receiving the requested information with location coordinates in the requested CRS or the different CRS.

[0944] A12. The method of any of embodiments A1-A2, wherein said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node indicating which CRS and / or which CRS transformation one or both of the communication nodes is capable of using for location coordinates communicated between the communication nodes.

[0945] A13. The method of any of embodiments A1-A12, wherein said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, the other communication node indicating:

[0946] which CRS and / or which CRS transformation the communication node is capable of using for location coordinates communicated between the communication nodes; and / or

[0947] which CRS and / or which CRS transformation the other communication node is capable of using for location coordinates communicated between the communication nodes.

[0948] A14. The method of any of embodiments A1-A13, wherein said transmitting and / or receiving comprises:

[0949] transmitting, to the other communication node, a request for capability information, wherein the request is or includes the transmitted siganling, wherein the capability information includes CRS capability information indicating which CRS and / or which CRS transformation the other communication node is capable of using for location coordinates communicated between the communication nodes; and / or

[0950] receiving, from the other communication node, a response to the request comprisingthe requested capability information, wherein the response is or includes the received signaling.

[0951] A15. The method of any of embodiments A1-A14, wherein said transmitting and / or receiving comprises:

[0952] receiving, from the other communication node, a request for capability information, wherein the request is or includes the received signaling; and / or transmitting, to the other communication node, a response to the request comprising the requested capability information, wherein the response is or includes the transmitted signaling, wherein the capability information includes CRS capability information indicating which CRS and / or which CRS transformation the other communication node is capable of using for location coordinates communicated between the communication nodes.

[0953] A16. The method of any of embodiments A14-A15, wherein the CRS capability information is:

[0954] specific to one or more methods for determining a location of a target node; and / or specific to a target-based mode in which the target node determines its own location or specific to a target-assisted mode in which the target node reports measurements based on which another node determines the location of the target node.

[0955] A17. The method of any of embodiments A14-A16, wherein said transmitting and / or receiving further comprises transmitting to the other communication node, or receiving from the other communication node, a request for information, wherein the requested information comprises location coordinates, wherein the request indicates which CRS is requested to be used for the location coordinates, wherein the indicated CRS is based on the CRS capability information.

[0956] A18. The method of any of embodiments A14-A17, wherein said transmitting and / or receiving further comprises transmitting to the other communication node, or receiving from the other communication node, information that comprises location coordinates in a CRS that, according to the CRS capability information, one or more of the communication nodes is capable of using for the location coordinates.

[0957] A19. The method of any of embodiments A17-A18, wherein the information is location information that comprises location coordinates of a target node.A20. The method of any of embodiments A17-A18, wherein the information is assistance data that assists with determining a location of a target node.

[0958] A21. The method of any of embodiments A14-A20, wherein the request for capability information comprises an A-GNSS-RequestCapabilities Information Element (IE) that requests A-GNSS location capabilities, wherein the response to the request comprises an A-GNSS-ProvideCapabilities IE that indicates A-GNSS location capabilities, wherein the A-GNSS-location capabilities convey CRS capability information.

[0959] A22. The method of embodiment A21 , wherein the CRS capability information indicates whether or not the communication node providing the CRS capability information supports location coordinates provided in a CRS, indicated together with A-GNSS assistance data.

[0960] A23. The method of embodiment A22, wherein:

[0961] inclusion of a location-CRS-Supported IE in the A-GNSS-ProvideCapabilities IE indicates that the communication node providing the CRS capability information supports location coordinates provided in a CRS, indicated together with A-GNSS assistance data; and / or

[0962] exclusion of the location-CRS-Supported IE from the A-GNSS-ProvideCapabilities IE indicates that the communication node providing the CRS capability information does not support location coordinates provided in a CRS, indicated together with A-GNSS assistance data.

[0963] A24. The method of any of embodiments A4-A11 and A17, wherein the request for information is a Request Location Information LPP message.

[0964] A25. The method of embodiment A24, wherein the Request Location Information LPP message includes a CommonlEsRequestLocationlnformation IE that carries common lEs for the Request Location Information LPP message, wherein the CommonlEsRequestLocationlnformation IE includes a locationCRS IE that specifies a CRS location coordinates are requested to be provided in.

[0965] A26. The method of embodiment A24, wherein the Request Location Information LPP message includes a CommonlEsRequestLocationlnformation IE that carries common lEs for the Request Location Information LPP message, wherein exclusion of a locationCRS IE from the CommonlEsRequestLocationlnformation IE indicates that location coordinates areexpected to be provided in a baseline CRS.

[0966] / 27. The method of any of embodiments A4-A11 , A17, and A24-A26, wherein the response to the request comprises a Provide Location Information LPP message.

[0967] A28. The method of embodiment A27, wherein the Provide Location Information LPP message includes a CommonlEsProvideLocationlnformation IE that carries common lEs for the Provide Location Information LPP message, wherein the CommonlEsProvideLocationlnformation IE includes a locationCRS IE that specifies a CRS location coordinates are related to.

[0968] A26. The method of embodiment A24, wherein the Provide Location Information LPP message includes a CommonlEsProvideLocationlnformation IE that carries common lEs for the Provide Location Information LPP message, wherein exclusion of a locationCRS IE from the CommonlEsProvideLocationlnformation IE indicates that location coordinates are related to a baseline CRS.

[0969] A27. The method of any of embodiments A4-A11 and A17, wherein the request for information is a Request Assistance Data LPP message that requests assistance data comprising a CRS transformation between a source CRS and a target CRS.

[0970] A28. The method of embodiment A27, wherein the Request Assistance Data LPP message includes a CommonlEsRequestAssistanceData IE, wherein the CommonlEsRequestAssistanceData IE includes a coordTransformationsReq field that indicates a request for coordinate transformations between a set of source and target CRSs.

[0971] A29. The method of any of embodiments A27-A28, wherein the response is a Provide Assistance Data LPP message.

[0972] A30. The method of embodiment A29, wherein the Provide Assistance Data LPP message includes a coordTransformations field that provides coordinate transformations information.

[0973] A31. The method of any of embodiments A4-A11 , wherein the response comprises the error indication.

[0974] A32. The method of embodiment A31 , wherein the request for information is a Request Location Information LPP message ora Request Assistance Data LPP message, andwherein the response is an Error LPP message.

[0975] A33. The method of embodiment A32, wherein the an Error LPP message includes a CommonlEsError IE that indicates a cause of the Error LPP message as being:

[0976] that the requested CRS is not supported; or

[0977] that the requested CRS transformation is not supported.

[0978] A34. The method of any of embodiments A4-A11 , wherein the request is a Determine Location Request on an Nlmf Service Based Interface, wherein the Determine Location Request includes an InputData structured data type, wherein the InputData structured data type includes a requestedCRS IE that indicates a CRS in which location coordinates are requested.

[0979] A35. The method of any of embodiments A4-A11 and A34, wherein the response is a Determine Location Response on an Nlmf Service Based Interface, wherein the Determine Location Response includes an LocationData structured data type, wherein the LocationData structured data type includes a usedCRS IE that indicates a CRS in which location coordinates are provided.

[0980] A36. The method of any of embodiments A4-A11 , wherein the request is a TRP Information Request requesting location information for transmission reception points (TRPs) hosted by the communication node that receives the request, wherein the TRP Information Request includes a requestedCRS IE that indicates the requested CRS.

[0981] A37. The method of any of embodiments A1-A36, wherein said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node regarding whether to use a regional CRS or global CRS for location coordinates communicated between the communication nodes.

[0982] A38. The method of any of embodiments A1-A36, wherein said transmitting and / or receiving comprises transmitting signaling to, and / or receiving signaling from, another communication node regarding a CRS transformation to be used for transforming location coordinates from a source CRS to a target CRS before communicating the location coordinates between the communication nodes.

[0983] A39. The method of any of embodiments A1-A38, wherein at least one of the communication nodes is a communication device.A40. The method of any of embodiments A1-A39, wherein at least one of the communication nodes is a network node.

[0984] A41. The method of any of embodiments A1-A40, wherein at least one of the communication nodes is a radio network node.

[0985] A42. The method of any of embodiments A1-A41, wherein at least one of the communication nodes is a location server.

[0986] A43. The method of any of embodiments A1-A42, further comprising communicating location coordinates between the communication nodes according to the transmitted signaling and / or the received signaling. separa

[0987] Group B Embodiments

[0988] Reserved

[0989] Group C Embodiments

[0990] C1. A communication node configured to perform any of the steps of any of the Group A embodiments.

[0991] C2. A communication node comprising processing circuitry configured to any of the steps of any of the Group A embodiments.

[0992] C3. A communication node comprising:

[0993] communication circuitry; and

[0994] processing circuitry configured to perform any of the steps of any of the Group A embodiments.

[0995] C4. A communication node comprising:

[0996] processing circuitry configured to perform any of the steps of any of the Group A embodiments; and

[0997] power supply circuitry configured to supply power to the communication node.

[0998] C5. A communication node comprising:

[0999] processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication node is configured toperform any of the steps of any of the Group A embodiments.

[1000] C6. The communication node of any of embodiments C1-C5, wherein the communication node is a communication device or a network node.

[1001] C7. A user equipment (UE) comprising:

[1002] an antenna configured to send and receive wireless signals;

[1003] radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

[1004] the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;

[1005] an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

[1006] a battery connected to the processing circuitry and configured to supply power to the UE.

[1007] C8. A computer program comprising instructions which, when executed by at least one processor of a communication node, causes the communication node to perform any of the steps of any of the Group A embodiments.

[1008] C9. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[1009] REFERENCES

[1010] 1. 3GPP TS 37.355 v.18.4.0, LTE Positioning Protocol (LPP) https: / / www.3gpp.org / ftp / Specs / archive / 37_series / 37.355 / 37355-i40.zip

[1011] 2. 3GPP TS 38.455 v18.4.0, NR Positioning Protocol A (NRPPa) https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.455 / 38455-i40.zip

[1012] 3. 3GPP TS 38.473 v18.4.0, F1 interface Protocol (F1AP) https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.473 / 38473-i40.zip

Claims

1. CLAIMS1. A method performed by a communication node (12A), the method comprising:transmitting (1500) signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) regarding which coordinate reference system, CRS (18), and / or which CRS transformation (18T) to use for location coordinates (14) communicated between the communication nodes (12A, 12B); andcommunicating (1510) location coordinates (14) between the communication nodes (12A, 12B) according to the transmitted signaling (16-1) and / or the received signaling (16-2).

2. The method of claim 1, wherein said transmitting and / or receiving comprises transmitting signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) indicating which CRS (18) and / or which CRS transformation (18T) to use for location coordinates (14) communicated between the communication nodes (12A, 12B):as part of location information indicating a location of a target node; and / or as part of assistance data for assistance with determining the location information.

3. The method of any of claims 1-2, wherein said transmitting and / or receiving comprises transmitting signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) indicating which CRS (18) and / or which CRS transformation (18T) is to be used, is requested to be used, or has been used, for location coordinates (14) communicated between the communication nodes (12A, 12B).

4. The method of any of claims 1-3, wherein said transmitting and / or receiving comprises:transmitting a request for information to the other communication node (12B), wherein the requested information includes location coordinates (14), and wherein the request is or comprises the transmitted signaling (16-1) and indicates which CRS (18) is requested to be used for the location coordinates (14); and / orreceiving a response to the request from the other communication node (12B), wherein the response is or includes the received signaling (16-2) and comprises:an acknowledgement that the other communication node (12B) supports, has used, and / or will use the requested CRS (18) for the locationcoordinates (14); oran indication of a different CRS (18) that the other communication node (12B) supports, has used, and / or will use for the location coordinates (14); or an error indication indicating that the other communication node (12B) does not support the requested CRS (18).

5. The method of any of claims 1-3, wherein said transmitting and / or receiving comprises:receiving a request for information from the other communication node (12B), wherein the requested information includes location coordinates (14), and wherein the request is or includes the received signaling (16-2) and indicates which CRS (18) is requested to be used for the location coordinates (14); and / ortransmitting a response to the request to the other communication node (12B), wherein the response is or includes the transmitted signaling (16-1) and comprises:an acknowledgement that the communication node (12A) supports, has used, and / or will use the requested CRS (18) for the location coordinates (14); oran indication of a different CRS (18) that the communication node (12A) supports, has used, and / or will use for the location coordinates (14); or an error indication indicating that the communication node (12A) does not support the requested CRS (18).

6. The method of any of claims 4-5, wherein the request also indicates a baseline CRS to be used for the location coordinates (14) in case the requested CRS (18) is not supported.

7. The method of any of claims 4-6, wherein the requested information is:location information that comprises location coordinates (14) of a target node; or assistance data that assists with determining a location of a target node.

8. The method of any of claims 4-7, further comprising transmitting or receiving the requested information with location coordinates (14) in the requested CRS (18) or the different CRS (18).

9. The method of any of claims 1-8, wherein said transmitting and / or receiving comprises transmitting signaling (16-1) to, and / or receiving signaling (16-2) from, the other communication node (12B) indicating:which CRS (18) and / or which CRS transformation (18T) the communication node (12A) is capable of using for location coordinates (14) communicated between the communication nodes (12A, 12B); and / orwhich CRS (18) and / or which CRS transformation (18T) the other communication node (12B) is capable of using for location coordinates (14) communicated between the communication nodes (12A, 12B).

10. The method of any of claims 1 -9, wherein said transmitting and / or receiving comprises:transmitting, to the other communication node (12B), a request for capability information (32), wherein the request is or includes the transmitted siganling, wherein the capability information (32) includes CRS capability information indicating which CRS (18) and / or which CRS transformation (18T) the other communication node (12B) is capable of using for location coordinates (14) communicated between the communication nodes (12A, 12B); and / or receiving, from the other communication node (12B), a response to the request comprising the requested capability information (32), wherein the response is or includes the received signaling (16-2).

11. The method of any of claims 1-10, wherein said transmitting and / or receiving comprises:receiving, from the other communication node (12B), a request for capability information (32), wherein the request is or includes the received signaling (16- 2); and / ortransmitting, to the other communication node (12B), a response to the request comprising the requested capability information (32), wherein the response is or includes the transmitted signaling (16-1), wherein the capability information (32) includes CRS capability information indicating which CRS (18) and / or which CRS transformation (18T) the other communication node (12B) is capable of using for location coordinates (14) communicated between the communication nodes (12A, 12B).

12. The method of any of claims 10-11, wherein the CRS capability information is:specific to one or more methods for determining a location of a target node; and / or specific to a target-based mode in which the target node determines its own location or specific to a target-assisted mode in which the target node reports measurements based on which another node determines the location of the target node.

13. The method of any of claims 10-12, wherein said transmitting and / or receiving further comprises:transmitting to the other communication node (12B), or receiving from the other communication node (12B), a request for information, wherein the requested information comprises location coordinates (14), wherein the request indicates which CRS (18) is requested to be used for the location coordinates (14), wherein the indicated CRS (18) is based on the CRS capability information; and / ortransmitting to the other communication node (12B), or receiving from the other communication node (12B), information that comprises location coordinates (14) in a CRS (18) that, according to the CRS capability information, one or more of the communication nodes (12A, 12B) is capable of using for the location coordinates (14).

14. The method of claim 13, wherein the information is location information that comprises location coordinates (14) of a target node or wherein the information is assistance data that assists with determining a location of a target node.

15. The method of any of claims 10-14, wherein the request for capability information (32) comprises an A-GNSS-RequestCapabilities Information Element (IE) that requests A-GNSS location capabilities, wherein the response to the request comprises an A-GNSS-ProvideCapabilities IE that indicates A-GNSS location capabilities, wherein the A-GNSS-location capabilities convey CRS capability information.

16. The method of claim 15, wherein the CRS capability information indicates whether or not the communication node (12A) providing the CRS capability information supports location coordinates (14) provided in a CRS (18), indicated together with A-GNSS assistance data.

17. The method of any of claims 4-8 and 13, wherein:the request for information is a Request Location Information LPP message and / or wherein the response to the request comprises a Provide Location Information LPP message; orwherein the request for information is a Request Assistance Data LPP message that requests assistance data comprising a CRS transformation (18T) between a source CRS (28) and a target CRS (18) and / or wherein the response is aProvide Assistance Data LPP message.

18. The method of any of claims 4-8, wherein the response comprises the error indication.

19. The method of claim 18, wherein the request for information is a Request Location Information LPP message or a Request Assistance Data LPP message, and wherein the response is an Error LPP message.

20. The method of any of claims 4-8, wherein:the request is a Determine Location Request on an Nlmf Service Based Interface, wherein the Determine Location Request includes an InputData structured data type, wherein the InputData structured data type includes a requestedCRS IE that indicates a CRS (18) in which location coordinates (14) are requested; and / orthe response is a Determine Location Response on an Nlmf Service Based Interface, wherein the Determine Location Response includes an LocationData structured data type, wherein the LocationData structured data type includes a usedCRS IE that indicates a CRS (18) in which location coordinates (14) are provided.

21. The method of any of claims 4-8, wherein the request is a TRP Information Request requesting location information for transmission reception points (TRPs) hosted by the communication node (12A) that receives the request, wherein the TRP Information Request includes a requestedCRS IE that indicates the requested CRS (18).

22. The method of any of claims 1-21 , wherein said transmitting and / or receiving comprises transmitting signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) regarding whether to use a regional CRS or global CRS for location coordinates (14) communicated between the communication nodes (12A, 12B).

23. The method of any of claims 1-22, wherein said transmitting and / or receiving comprises transmitting signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) regarding a CRS transformation (18T) to be used for transforming location coordinates (14) from a source CRS (28) to a target CRS (18) before communicating the location coordinates (14) between the communication nodes (12A, 12B).

24. The method of any of claims 1-23, wherein at least one of the communication nodes (12A, 12B) is a communication device (12-1), a network node (12-2), or a location server.

25. The method of any of claims 1-24, wherein at least one of the communication nodes (12A, 12B) implements an application function or a location services client.

26. A communication node (12A) configured to:transmit signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) regarding which coordinate reference system, CRS (18), and / or which CRS transformation (18T) to use for location coordinates (14) communicated between the communication nodes (12A, 12B); andcommunicate location coordinates (14) between the communication nodes (12A, 12B) according to the transmitted signaling (16-1) and / or the received signaling (16-2).

27. The communication node of claim 26, configured to perform the method of any of claims 2-25.

28. A computer program comprising instructions which, when executed by at least one processor of a communication node (12A), causes the communication node (12A) to:transmit signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) regarding which coordinate reference system, CRS (18), and / or which CRS transformation (18T) to use for location coordinates (14) communicated between the communication nodes (12A, 12B); andcommunicate location coordinates (14) between the communication nodes (12A, 12B) according to the transmitted signaling (16-1) and / or the received signaling (16-2).

29. A carrier containing the computer program of claim 28, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

30. A communication node (12A) comprising:communication circuitry (1620); andprocessing circuitry (1610) configured to:transmit signaling (16-1) to, and / or receiving signaling (16-2) from, another communication node (12B) regarding which coordinate reference system, CRS (18), and / or which CRS transformation (18T) to use for locationcoordinates (14) communicated between the communication nodes (12A, 12B); andcommunicate location coordinates (14) between the communication nodes (12A, 12B) according to the transmitted signaling (16-1) and / or the received signaling (16-2).

31. The communication node of claim 30, wherein the processing circuitry (1610) is configured to perform the method of any of claims 2-25.

Images