First network node, second network node, user equipment and methods performed therein

Abstract

Embodiments herein may relate to a method for handling location reports in a wireless communication network, for example performed by a first network node (13). The first network node aligns a reporting configuration with the second network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

Description

Technical Field

[0001] The embodiments herein relate to a first network node, a second network node, a user equipment (UE), and methods relating to wireless communication executed therein. Furthermore, computer program products and computer-readable storage media are also provided herein. In particular, the embodiments herein relate to handling communications in a wireless communication network, such as handling positioning or determining the location of the UE. Background Technology

[0002] In a typical wireless communication network, a UE, also referred to as a wireless communication device, mobile station, station (STA), and / or wireless device, communicates with one or more core networks (CNs) via a radio access network (RAN). The RAN covers a geographical area divided into service areas or cells, each of which is served by radio network nodes such as access nodes (e.g., Wi-Fi access points or radio base stations (RBS), which in some networks may also be referred to as NodeB, gNodeB, or eNodeB). A service area or cell is a geographical area in which radio network nodes provide radio coverage. Radio network nodes operate on radio frequencies to communicate with UEs within their range via an air interface. Radio network nodes communicate with UEs via downlink (DL), and UEs communicate with radio network nodes via uplink (UL).

[0003] Universal Mobile Telecommunications System (UMTS) is a third-generation (3G) telecommunications network evolved from the second-generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High-Speed ​​Packet Access (HSPA) for communication with user equipment. In a forum known as the 3rd Generation Partnership Project (3GPP), telecommunications providers proposed and agreed on standards for current and future generations of networks and studied enhancements such as data rates and radio capacity. In some RANs, such as in UMTS, several radio network nodes can be connected to a controller node, such as a Radio Network Controller (RNC) or Base Station Controller (BSC), via terrestrial lines or microwave, which monitors and coordinates the various activities of the multiple radio network nodes connected thereto. The RNC is typically connected to one or more core networks.

[0004] The Evolved Packet System (EPS) specification has been completed within 3GPP, and upcoming 3GPP releases, such as New Radio (NR), have been analyzed and studied. EPS includes the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology where radio network nodes are directly connected to the EPC core network. In this way, the EPS radio access network (RAN) has an architecture that includes radio network nodes directly connected to one or more core networks.

[0005] With the emergence of 5G technologies such as New Radio (NR), the use of numerous transmit and receive antenna elements is likely to generate significant interest because it enables the utilization of beamforming techniques, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signal in one or more selected directions while suppressing transmitted signals in other directions. Similarly, on the receive side, the receiver can amplify signals from one or more selected directions while suppressing unwanted signals from other directions.

[0006] Figure 1 The 5G reference architecture, as defined by 3GPP, is depicted below. Figure 1 The Network Functions (NF) shown in the figure.

[0007] Application Functions (AFs) or Application Servers (ASs) interact with the 3GPP core network and allow external parties to use open application programming interfaces (APIs) provided by the network operator. AFs provide session-related information to other nodes in the 5G core network (5GC).

[0008] Network Open Functions (NEF) supports different functionalities, and NEF supports different open APIs.

[0009] The Network Storage Function (NRF) functions as the registry center for Network Functions (NF).

[0010] The Unified Data Repository (UDR) stores data that is grouped into different sets of subscription-related information: subscription data; policy data; open structured data; and application data.

[0011] The Session Management Function (SMF) supports various functionalities. For example, the SMF receives policy and charging control (PCC) rules from the Policy Control Function (PCF) and configures the User Plane Function (UPF) accordingly.

[0012] UPF supports handling user plane traffic based on rules received from SMF, such as packet inspection and different enforcement actions (such as Quality of Service (QoS) handling).

[0013] PCF supports a unified policy framework for managing network behavior. Specifically, PCF provides PCC rules to the Policy and Charging Enforcement Function (PCEF), which is the SMF and / or UPF that enforces policy and charging decisions according to the prescribed PCC rules.

[0014] Access and Mobility Management (AMF) functions manage UE access (e.g., when the UE is connected through a different access network) and UE mobility aspects.

[0015] Billing of Billing Functions (CHF) management services and / or functions. CHF includes: Online Billing Function (OCF), which provides quota management functionality under credit control terms as specified in TS 32.296 v17.0.0; and Billing Data Function (CDF), which provides Billing Data Record (CDR) generation functionality for billing events as specified in Clause 4.3.1.232.240 v 18.0.0.

[0016] The Network Slice Selection Function (NSSF), not shown, selects a Network Slice Instance (NSI), determines the allowed Network Slice Selection Assistance Information (NSSAI), and sets the AMF to provide services to the UE.

[0017] Figure 2 The architecture supports positioning in 4G / LTE / EPC and 5G / NR / 5GC, where UE 100 and location server 130 interact directly via LTE Positioning Protocol (LPP) 171. Additionally, there is interaction between location server 130 and serving radio base station 110 via Network Positioning Protocol 172, which is to some extent supported by interaction between radio base station 110 and UE 100 via Radio Resource Control (RRC) Protocol 170. Radio base station 110 interacts with mobility network entity 120 via a first interface protocol 173, and mobility network entity 120 interacts with location server 130 via a second interface protocol 174. The location server also utilizes location management protocol 175 or other protocols. Figure 2 The location gateway function 140 interacts directly with the location server 130 or via the mobility network entity 120. In the latter case, the network mobility entity 120 acts as an intermediary node between the location server 130 and the location gateway 140. The location gateway function 140 discloses location information either via a first open protocol 176 or directly to the application function 160 or via the network open function 150. In the latter case, a second open protocol 177 lies between the network open function 150 and the application function 160.

[0018] In 4G / LTE / EPC and 5G / NR / 5GC, the server / node / function / interface / protocol is named as follows: Common name Names in 4G / LTE / EPC Names in 5G / NR / 5GC Location server (130) Evolved Services Mobile Location Center (E-SMLC) or SLP Location Management Function (LMF) or SLP Radio base station (110) eNodeB gNodeB Mobile network entities (120) Mobility Management Entity (MME) Access and Mobility Management Function (AMF) Network Location Protocol (172) LTE Location Protocol Annex (LPPa) Annex to the New Radio Positioning Protocol (NRPPa) First interface (173) S1-MME N2 Second interface (174) SL NL1 Second interface (174) SL NL1 Location Management Protocol (175) Nlmf First Open Protocol (176) NL5 (Ngmlc) Second Open Protocol (177) Nss (Nnef) In both cases, location server 130 can also interact directly with the UE via user plane communication carrying LPP 171, signaling defined by the Open Mobile Alliance (OMA) Secure User Plane Location (SUPL), or other user plane (UP) signaling. In the SUPL case, the location server is referred to as a SUPL Positioning Platform (SLP), and the device is referred to as a SUPL Enabled Terminal (SET).

[0019] Figure 3 This illustrates the different 4G / LTE / EPC and 5G / NR / 5GC entities in a more complete and general architecture.

[0020] A 5G positioning method based on 5G signals is implemented using downlink positioning reference signals associated with specific radio resources and transmitted using directional radio beams. Each positioning reference signal is associated with an identifier. One or more such signals are transmitted from a specific transmission point associated with radio base station 110.

[0021] Positioning methods rely on measurements, and several positioning methods rely on measurements from devices such as Global Navigation Satellite System (GNSS) signals, WiFi signals, Bluetooth signals, beacon signals, Radio Access Technology (RAT) related signals, etc.

[0022] Application functions or other network functions can request location information from different network functions / nodes or from the device, either as location measurement or as location estimation. Such requests can be on-demand (real-time) or periodic location information. Summary of the Invention

[0023] As part of the development of the embodiments described herein, one or more issues have been identified. Given the architecture described above that supports the transmission of nominal periodic location information over a network and through different interfaces, there are also industry-specific application requirements for more timely and granular reporting and an unlimited volume of reports to network applications. Such extensions are subtle and must be introduced in a manner that ensures backward compatibility.

[0024] The purpose of this paper is to provide a mechanism for efficiently handling location information in wireless communication networks.

[0025] According to one aspect, and according to embodiments herein, the objective is achieved by providing a method for processing location reports in a wireless communication network, performed by a first network node (such as an NF node, NEF, Gateway Mobility Location Center (GMLC), LMF, SLP, location node, or the like). The first network node aligns its reporting configuration with that of a second network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

[0026] According to another aspect, and according to embodiments herein, the objective is achieved by providing a method for processing location reports in a wireless communication network, performed by a second network node (such as an NF node, AF, LMF, SLP, UE, location node, or the like). The second network node aligns its reporting configuration with that of the first network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

[0027] According to another aspect, according to the embodiments herein, the purpose is achieved by providing a first network node and a second network node configured to respectively perform the methods herein.

[0028] Therefore, according to one aspect, and according to embodiments herein, the objective is achieved by providing a first network node (such as an NF node, location node, or the like) for handling location reports in a wireless communication network. The first network node is configured to align a reporting configuration with a second network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

[0029] According to another aspect, according to embodiments herein, the objective is achieved by providing a second network node (such as an NF node, location node) for handling location reports in a wireless communication network. The second network node is configured to align a reporting configuration with that of the first network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

[0030] According to another aspect, according to embodiments herein, the objective is achieved by providing a method for handling location reports in a wireless communication network, executed by a first network node. The first network node receives a request from a second network node, the request including a proposed periodic reporting extension in addition to a baseline periodic reporting configuration; and transmits to the second network node: confirmation of the periodic location information extension configuration; an alternative supported periodic location information extension configuration; or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the second network node.

[0031] According to another aspect, according to embodiments herein, the objective is achieved by providing a method for handling location reports in a wireless communication network, executed by a second network node. The second network node transmits a request to a first network node, the request including a proposed periodic reporting extension in addition to a baseline periodic reporting configuration; and receives from the first network node: confirmation of the periodic location information extension configuration, an alternative supported periodic location information extension configuration, or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the first network node.

[0032] According to another aspect, according to embodiments herein, the objective is achieved by providing a method executed by a UE for handling location reports in a wireless communication network. The UE transmits a request to a first network node, the request including a proposed periodic reporting extension in addition to a baseline periodic reporting configuration; and receives from the first network node: confirmation of the periodic location information extension configuration, an alternative supported periodic location information extension configuration, or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, and thereby aligning the reporting configuration with the first network node.

[0033] According to another aspect, according to embodiments herein, the objective is achieved by providing a first network node for processing location reports in a wireless communication network. The first network node is configured to receive a request from a second network node, the request including, in addition to a baseline periodic reporting configuration, a proposed periodic reporting extension; and to transmit to the second network node: confirmation of the periodic location information extension configuration; an alternative supported periodic location information extension configuration; or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the second network node.

[0034] According to another aspect, according to embodiments herein, the objective is achieved by providing a second network node for processing location reports in a wireless communication network. The second network node is configured to transmit a request to a first network node, the request including, in addition to a baseline periodic reporting configuration, a proposed periodic reporting extension; and to receive from the first network node: confirmation of the periodic location information extension configuration, an alternative supported periodic location information extension configuration, or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the first network node.

[0035] According to another aspect, according to embodiments herein, the objective is achieved by providing a UE for handling location reports in a wireless communication network. The UE is configured to transmit a request to a first network node, the request including a proposed periodic reporting extension in addition to a baseline periodic reporting configuration; and to receive from the first network node: confirmation of the periodic location information extension configuration, an alternative supported periodic location information extension configuration, or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the first network node.

[0036] Furthermore, a computer program product including instructions is provided herein, which, when executed on at least one processor, cause at least one processor to perform the methods described herein as executed by a first or second network node, respectively. Additionally, a computer-readable storage medium is provided herein storing a computer program product including instructions that, when executed on at least one processor, cause at least one processor to perform the methods described herein as executed by a first or second network node, respectively.

[0037] The embodiments described herein relate to an extension to periodic location information reporting, wherein first and second network nodes already support a baseline periodic location information reporting configuration, also referred to as a baseline periodic reporting configuration for location information. The advantage of the embodiments described herein is that they incorporate an extension to the baseline periodic reporting framework, which introduces support for periodic reporting more suited to industry needs while ensuring backward compatibility. Therefore, location information can be handled efficiently in wireless communication networks. Attached Figure Description

[0038] The embodiments will now be described in more detail with reference to the accompanying drawings, wherein: Figure 1 A schematic diagram of the network architecture is shown; Figure 2 A schematic diagram of the network architecture is shown; Figure 3 A schematic diagram of the network architecture is shown; Figure 4 A wireless communication network according to an embodiment of this document is shown; Figure 5 Signaling schemes and flowcharts combining embodiments according to the present document are shown; Figure 6 Signaling schemes and flowcharts combining embodiments according to the present document are shown; Figure 7 The method performed by a second network node (second node) according to the embodiments described herein is being described; Figure 8A method performed by a first network node (first node) according to embodiments herein is being described; Figure 9 Signaling schemes and flowcharts combining embodiments according to the present document are shown; Figure 10 A method performed by a second network node (second node) according to embodiments herein is being described; Figure 11 A method performed by a first network node (first node) according to embodiments herein is being described; Figure 12a Signaling schemes and flowcharts combining embodiments according to the present document are shown; Figure 12b A method performed by a first network node according to embodiments herein is being described; Figure 12c A method performed by a second network node according to embodiments herein is being described; Figure 12d A method performed by a first network node according to embodiments herein is being described; Figure 12e A method performed by a second network node according to embodiments herein is being described; Figure 12f This describes a method performed by a UE according to embodiments described herein; Figure 13 A block diagram depicting a first network node according to an embodiment herein is shown. Figure 14 A block diagram depicting a second network node according to an embodiment herein is shown; Figure 15 This schematically illustrates a telecommunications network connected to a host computer via an intermediate network; Figure 16 This is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection; and Figure 17 , 18 19 and 20 are flowcharts illustrating methods implemented in a communication system that includes a host computer, a base station, and user equipment. Detailed Implementation

[0039] The embodiments described herein typically relate to wireless communication networks. Figure 4This is a schematic overview depicting a wireless communication network 1. Wireless communication network 1 includes one or more RANs and one or more CNs. Wireless communication network 1 can use one or more different technologies. The embodiments in this document relate to recent technology trends of particular interest in the context of New Radio (NR); however, the embodiments are also applicable to existing wireless communication systems, such as, for example, LTE or Wideband Code Division Multiple Access (WCDMA) and their development.

[0040] In the wireless communication network 1, a user equipment (UE) 10 (illustrated herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), STA, and / or wireless terminal) communicates with one or more core networks (CN) via, for example, one or more access networks (AN) (e.g., a radio access network (RAN)). Those skilled in the art will understand that "UE" is a non-limiting term, referring to any terminal, wireless communication terminal, user equipment, narrowband Internet of Things (NB-IoT) device, machine-type communication (MTC) device, device-to-device (D2D) terminal, or node (e.g., a smartphone, laptop, mobile phone, sensor, relay, mobile tablet, or even a small base station capable of communicating wirelessly with radio network nodes within an area served by radio network nodes).

[0041] Wireless communication network 1 includes radio network nodes 12 providing radio coverage over a geographic area, a first service area 11, or a first cell using a first radio access technology (RAT) such as NR, LTE, or similar technologies. Radio network nodes 12 can be: transmission and reception points, such as access nodes, access controllers, base stations, such as radio base stations, such as gNodeB (gNB), evolved Node B (eNB, eNode B), NodeB, base transceiver station, radio remote unit, access point base station, base station router, wireless local area network (WLAN) access point or access point station (AP STA), radio base station, stand-alone access point, or any other network element or node transmission arrangement capable of communicating with wireless devices within the area served by the radio network node, depending on, for example, the first radio access technology and terminology used. A radio network node can be referred to as a serving radio network node, where the service area can be referred to as a serving cell, and the serving network node communicates with the UE in the form of DL transmissions to the UE and UL transmissions from the UE. It should be noted that a service area can be represented as a cell, beam, beam group, or the like to define the area of ​​radio coverage.

[0042] The wireless communication network further includes multiple core network nodes / network function nodes, such as a first network node 13 (e.g., a location node such as a Gateway Mobile Location Center (GMLC), LMF, or NF node), a second network node 14 (e.g., a location node such as a GMLC, LMF, UE 10, or Application Function (AF) node), a third network node 15 (e.g., a location node such as a GMLC, LMF, or AF node), and a fourth network node 16 (e.g., a location node such as a GMLC, LMF, UE 10, or radio network node 12). Network nodes are illustrated herein using NR terminology; however, it should be noted that embodiments described herein can be implemented in systems using other RATs such as LTE or similar technologies.

[0043] According to the embodiments herein, first network node 13 and second network node 14 align their reporting configurations, wherein the reporting configurations define an extension of the baseline periodic location information reporting configuration. Alignment can be triggered upon request and / or during capability exchange. The aligned reporting configuration may be referred to as a periodic location information reporting extension configuration, an extended location reporting configuration, an extended periodic location reporting configuration, or the like. Therefore, the first and second network nodes use the same or similar reporting configurations, coordinated reporting configurations, or reporting configurations with the same reporting intervals or reporting volume (number of reports).

[0044] The embodiments described herein relate to the alignment of reporting configurations, wherein the first network node 13 and the second network node 14 already support a baseline periodic location information reporting configuration. The baseline periodic location information reporting configuration may include... - A set of supported baseline reporting intervals (such as time ranges) - A set of supported baseline reporting volumes (such as the number of reports).

[0045] The baseline periodic location information reporting configuration may also be referred to as baseline configuration, baseline reporting configuration, or the like.

[0046] Figure 5An example of a signaling diagram is illustrated, showing that the mentioned actions can be taken in any suitable order. Action 300 includes alignment between a first network node 13 and a second network node 14 in a periodic location information reporting extended configuration, which extends the baseline periodic location information reporting configuration. Based on the aligned reporting configuration, the first network node 13 can provide the second network node 14 with first location information (see action 310) and second location information (see action 330), where the time difference between the first and second location information follows the aligned reporting configuration, and the amount of location information reported is aligned according to the reporting configuration. The second network node 14 manages (see action 320) the first location information and manages (see action 340) the second location information. For example, the second network node 14 can manage the second location information by forwarding it to a third network node 15, whose periodic location information reporting extended configuration may already be aligned. As another example, the second network node 14 can manage the second location information by using the acquired second location information in some process based on periodically reported location information.

[0047] The alignment between the first network node 13 and the second network node 14 initiating the extended configuration of the periodic location information report is triggered by its participation in the alignment of the extended configuration of the periodic location information report with the third network node 15.

[0048] When the alignment between the first network node 13 and the second network node 14, which has already initiated the extended configuration of periodic location information reporting, is initiated, the first network node 13 can initiate the alignment between the first network node 13 and the fourth network node 16, which has already initiated the extended configuration of periodic location information reporting.

[0049] Examples of nodes in a 5G system include (but are not limited to): - The first network node 13 is the network open function, the second network node is the application function, and the fourth network node is GMLC. - The first network node 13 is GMLC, the second network node is LMF or SLP, the third network node is application function, and the fourth network node is UE or radio base station. - The first network node 13 is either LMF or SLP, the second network node is UE, and the third network node is GMLC. Alignment of the reporting configuration, including the periodic location information reporting extension configuration, can be triggered upon request and / or during capability exchange.

[0050] The alignment between the first network node 13 and the second network node 14 in the extended configuration of periodic location information reporting can be based on a request and response process. Figure 6An example is illustrated below. Alignment of the reporting configuration can be initiated by the second network node 14 sending (Action 400) a request for periodic location information reporting, the request including extended configurations in addition to the baseline configuration. The request may also include a specific baseline configuration corresponding to the fallback configuration if the first network node 13 does not support extensions. In response, the first network node 13 can send (Action 405) a periodic location information response. The periodic location information response may include one or more of the following: A. Confirmation of the extended configuration of periodic location information; B. Alternative supported extended configurations for periodic location information; and / or C. Baseline response, which should only support the baseline configuration requested.

[0051] Based on the aligned periodic location information reporting extension configuration, the first network node 13 can provide the second network node 14 with first location information (action 410) and second location information (action 430), wherein the time difference between the first and second location information is in accordance with the aligned periodic location information reporting extension configuration, and the amount of location information reported is aligned in accordance with the aligned periodic location information reporting extension configuration. The second network node 14 can then manage (action 420) the first location information and manage (action 440) the second location information.

[0052] From the perspective of the second network node 14, Figure 7 The example illustrates that the second network node 14 sends (action 500) a request for an extended configuration for periodic location information reports, which includes the extended configuration in addition to the baseline configuration. The baseline configuration is a specific configuration corresponding to the fallback configuration in the event that the first network node 13 does not support the extended configuration.

[0053] The second network node 14 receives (action 505) a response from the first network node, such as a periodic location information response. The response may include one or more of the following: A. Confirmation of the extended configuration of periodic location information; B. Alternative supported extended configurations for periodic location information; and / or C. Baseline response, which should only support the baseline configuration requested.

[0054] Therefore, the first network node 13 and the second network node 14 are aligned with the periodic location information reporting extension configuration, and the second network node 14 infers that periodic location information will be provided according to either A, B, and / or C. Based on the aligned configuration, the second network node 14 can obtain first location information (action 510) and second location information (action 530) from the first network node 13, wherein the time difference between the first location information and the second location information is aligned according to the aligned periodic location information reporting extension configuration, and the amount of location information reported is aligned according to the periodic location information reporting extension configuration. The second network node 14 can manage (action 520) the first location information and can manage (action 540) the second location information.

[0055] From the perspective of the first network node 13, Figure 8 The example illustrates that a first network node 13 may receive (action 600) a request for periodic location information reporting, which includes an extended configuration in addition to the baseline configuration. The baseline configuration may be a specific configuration corresponding to the fallback configuration if the first network node 13 does not support the extended configuration.

[0056] The first network node 13 may send a response (Action 605) to the second network node 14. The response may include one or more of the following: - As in A, including confirmation of the extended configuration of periodic location information - means that the first network node 13 follows the periodic location information configuration suggested by the second network node 14 and will provide periodic location information accordingly; - As in B, including alternative supported periodic location information extended configurations - this means that the first network node 13 does not support the proposed periodic location information configuration from the second network node 14 and will instead provide periodic location information based on alternative periodic location information.

[0057] - As in C, including the baseline response, where only the baseline configuration in the request is supported - this means that the first network node 13 does not support the periodic location information extended configuration, for example, the protocol version it supports does not include the periodic location information extended configuration.

[0058] Therefore, the first network node 13 and the second network node 14 have an alignment regarding the periodic location information configuration, namely, an aligned periodic location information reporting extension configuration, and the first network node 13 can check or determine whether periodic location information can be provided according to A, B, or C. Based on the aligned configuration, the first network node 13 can provide the second network node 14 with first location information (action 610) and second location information (action 630), wherein the time difference between the first location information and the second location information is in accordance with the aligned periodic location information reporting extension configuration, and the amount of location information reported can be aligned according to the periodic location information reporting extension configuration.

[0059] Alternatively, or additionally, the alignment between the first network node 13 and the second network node 14 in the periodic location information reporting extended configuration is based on the capability request and response process. Figure 9 An example is illustrated below. Alignment is initiated by sending a capability request (Action 700) via the second network node 14. The capability request may include information about what specific capability is requested.

[0060] The request may also include a specific baseline configuration corresponding to the fallback configuration in the event that the first network node does not support the extension.

[0061] In response, the first network node 13 may send (action 705) a capability response including one or more of the following. - Baseline periodic location information reporting support; and / or - Extended support for periodic location information reporting Periodic location information reporting extension support may include additional information about the types of periodic location information reporting extensions supported. Examples include minimum reporting interval, the set of supported reporting intervals, maximum reporting volume, and / or an indicator that supports unlimited reporting volume.

[0062] Based on its capabilities, the second network node can send a location information request (Action 707) that includes a periodic location information reporting extended configuration and optionally a baseline periodic location information reporting configuration. The baseline configuration (i.e., the periodic location information reporting configuration) may include a default periodic reporting interval, a reporting volume that can be set to infinite, etc. The extended configuration (i.e., the periodic location information reporting extended configuration) may include a more granular periodic reporting interval, a more granular reporting volume, etc. The combination of the baseline reporting interval and the extended reporting interval can be used to ensure backward compatibility, so that the first network node 13, which does not support the extended configuration, will use the baseline configuration. Alternatively or additionally, a combination of the baseline reporting interval and the extended reporting interval can be used because a mandatory baseline reporting interval (indicated in the protocol specification to be ignored) is required. Alternatively or additionally, the first network node 13 may send a location information request that includes a periodic location information reporting extended configuration (instead of the baseline periodic location information reporting configuration), wherein the extended configuration may include one or more of the reporting interval and the reporting volume. Thus, the first network node 13 and the second network node 14 have aligned the periodic location information reporting configuration with the extended configuration.

[0063] The first network node 13 can provide first location information (action 710) and second location information (action 730), wherein the time difference between the first and second location information is configured according to an aligned periodic location information report extension, and the amount of location information reported is aligned according to the periodic location information report extension configuration. The second network node 14 can manage (action 720) the first location information and can manage (action 740) the second location information.

[0064] From the perspective of the second network node 14, Figure 10 The example illustrates that the second network node 14 can send a capability request (Action 800). The request can include instructions on what capabilities are requested. The first network node 13 can respond with capabilities including support for extended configurations such as periodic location information reporting, in addition to the baseline configuration.

[0065] The second network node 14 can therefore obtain (action 805) a periodic location information capability response from the first network node 13. The periodic location information capability response may include one or more of the following: - Baseline periodic location information reporting support; and / or - Extended support for periodic location information reporting Periodic location information reporting extension support may include additional information about the types of periodic location information reporting extensions supported. Examples include minimum reporting interval, the set of supported reporting intervals, maximum reporting volume, and / or an indicator that supports unlimited reporting volume.

[0066] Based on its capabilities, the second network node 14 can send a location information request (Action 807) that includes an extended periodic location information reporting configuration and optionally a baseline periodic location information reporting configuration. The baseline configuration may include a default periodic reporting interval, a reporting volume that can be set to unlimited, etc. The extended configuration may include a more granular periodic reporting interval, a more granular reporting volume, etc. A combination of the baseline and extended reporting intervals can be used to ensure backward compatibility, allowing the first network node that does not support the extended configuration to use the baseline configuration. A combination of the baseline and extended reporting intervals can be used to include a mandatory baseline reporting interval (indicated in the protocol specification to be ignored). The first network node 13 can send a location information request that includes an extended periodic location information reporting configuration (instead of the baseline periodic location information reporting configuration), where the extended configuration may include one or more of the reporting interval and the reporting volume. Therefore, the first network node 13 and the second network node 14 have aligned their periodic reporting configurations.

[0067] The second network node 14 can then obtain first location information (action 810) and second location information (action 830), wherein the time difference between the first and second location information is configured according to an aligned periodic location information report extension, and the amount of location information reported is aligned according to the periodic location information report extension configuration. The second network node 14 can manage (action 820) the first location information and can manage (action 840) the second location information.

[0068] From the perspective of the first network node 13, Figure 11 The example illustrates that the first network node 13 can receive (Action 900) a capability request. The capability request may include instructions regarding what capability is requested. The first network node 13 may respond with capabilities including support for extended configurations such as periodic location information reporting, in addition to the baseline configuration (Action 905).

[0069] A response may include one or more of the following: - Baseline periodic location information reporting support; and / or - Extended support for periodic location information reporting Periodic location information reporting extension support may include additional information about the types of periodic location information reporting extensions supported. Examples include minimum reporting interval, the set of supported reporting intervals, maximum reporting volume, and / or an indicator that supports unlimited reporting volume.

[0070] First network node 13 may receive (action 907) a location information request, which includes an extended periodic location information reporting configuration and optionally a baseline periodic location information reporting configuration. The baseline configuration may include a default periodic reporting interval, a reporting volume that can be set to unlimited, etc. The extended reporting configuration may include a more granular periodic reporting interval, a more granular reporting volume, etc. The combination of the baseline and extended reporting intervals can be used to ensure backward compatibility, so that first network nodes that do not support the extended configuration will use the baseline configuration. A combination of the baseline and extended reporting intervals can be used because a mandatory baseline reporting interval (which may be indicated in the protocol specification to be ignored) needs to be included. First network node 13 may send a location information request including the extended periodic location information reporting configuration (instead of the baseline periodic location information reporting configuration), wherein the extended configuration may include one or more of the reporting interval and the reporting volume. Therefore, first network node 13 and second network node 15 have aligned their periodic reporting configurations.

[0071] The first network node 13 can provide first location information (action 910) and second location information (action 930), wherein the time difference between the first location information and the second location information is configured according to an aligned periodic location information report, and the amount of location information reports can be aligned according to an extended configuration of the periodic location information reports.

[0072] exist Figure 9-11 At any point in the process described herein, the first network node 13 may request auxiliary data from the second network node 14 to support location information determination. The second network node 14 may provide auxiliary data to the first network node 13 to support location information determination when not requested (unrequested).

[0073] Extended configuration for periodic location information reporting.

[0074] In the case of request-response or capability exchange processes, the extension can be configured slightly differently.

[0075] By aligning requests and responses.

[0076] In the case of a request and response process, in addition to the baseline periodic reporting configuration, requests from the second network node 14 may also include proposed periodic reporting extensions. The first network node 13 may be instructed to include one or more of the following: A: Confirm the extended configuration of periodic location information. B: Provides alternative support for extended configurations of periodic location information. C: Use the baseline response, where only the baseline configuration in the request should be supported.

[0077] The response message from the first network node 13 can indicate which of the alternative schemes A, B, or C will be used to ensure alignment of the first and second network nodes.

[0078] The baseline configuration in the request may include: - Baseline reporting interval, such as baseline reporting interval in integer seconds. - Baseline reporting quantities in integer units, where infinity is not coded. The signaling example from Nlmf, see 3GPP TS 29.572 17.4.0, includes a baseline configuration that includes the reporting interval and reporting amount, along with an underlined extension, a millisecond reporting interval, and a Boolean value indicating an unlimited reporting amount. If the extension exists, the corresponding baseline configuration is ignored by the first supported network node 13, but is provided, for example, as a specific configuration for backward compatibility. - Minimum reporting interval of 1 - Maximum reporting volume 6.1.6.2.24 Type: PeriodicEventInfo (with underlined parts) Table 6.1.6.2.24-1: Definition of type PeriodicEventInfo Where reportIntervalMs can be defined as The first network node 13, which confirms the periodic report extension, can provide, for example, an acceptedPeriodicEventInfo acknowledgment of the same type as the baseline and extended configuration in the confirmation request, or a periodicEventInfo acknowledgment of the request that supports the extension and baseline configuration. If the response does not include a confirmation configuration, the second network node 14 can assume that the baseline configuration is aligned.

[0079] For Ngmlc (see 3GPP TS 29.515 17.4.0) and Namf (see 3GPP TS 29.518 17.4.0), as well as for similar interfaces between similar nodes, the corresponding signaling is also considered.

[0080] Alignment through the exchange of capabilities For capability requests and responses, a signaling example is for LPP, see 3GPP TS 37.355 17.4.0, where capabilities can be per-location method. An example of a location method could be... 1. Auxiliary Global Navigation Satellite System (A-GNSS) 2. LTE observation time difference 3. LTE Enhanced Cell ID 4. Land Beacon System 5. Sensor positioning 6. WLAN positioning 7. Bluetooth positioning 8. NR uplink positioning 9. NR Enhanced Cell ID 10. NR downlink arrival time difference 11. NR downlink departure angle 12. NR multiple round trip time It can also support periodic reporting base and extension under different positioning modes (such as standalone, no network assistance, UE-based, device-estimated location, and UE-assisted, device-provided measurement, network-estimated location).

[0081] An example of capability signaling comes from LPP and GNSS. In this example, the capability regarding millisecond periodic reporting intervals is the same for all positioning modes, but alternatives could be indicators of support for each positioning mode. Support indicators could simply indicate support for millisecond reporting intervals, or they could be more specific—for example, indicating a minimum reporting interval in milliseconds or a set of supported reporting intervals in milliseconds. The example below indicates the minimum reporting interval as a set of alternatives—1ms, 10ms, and 100ms. Variations are indicated by underscores.

[0082] 6.5.2.9 GNSS Capability Information - A-GNSS-ProvideCapabilities The target device uses IE A-GNSS-Provide-Capabilities This indicates its A-GNSS support capability and provides its A-GNSS location capabilities (e.g., supported GNSS and auxiliary data) to the location server.

[0083] The request for periodic location information is common to all positioning methods, and there may also be positioning method-specific information provided in the request.

[0084] A sample request includes an optional millisecond periodic reporting interval extension (instead of the baseline reporting interval) that will be considered. An alternative could be to provide the included alternative periodic reporting extensions (instead of the baseline configuration).

[0085] -CommonIEsRequestLocationInformation CommonIEsRequestLocationInformation Public IE browsers that carry LPP message type requests for location information.

[0086] The embodiments described herein affect LPP between UE and RAN for both 4G / LTE and 5G / NR [1], while inter-node signaling is affected for 5G core networks such as Nlmf [2], Ngmlc [3], and Namf [4]. Attached documentation is provided.

[0087] Figure 12a This is a flowchart and signaling scheme based on a combination of some embodiments described herein.

[0088] Action 1201: The first network node 13 and the second network node 14 align their reporting configurations with each other. The aligned reporting configurations define an extension of the baseline periodic location information reporting configuration. Alignment can be triggered upon request and / or during capability exchange.

[0089] Action 1202: The second network node 14 may provide the first and second location information to the first network node 13 in accordance with the aligned report configuration.

[0090] Action 1203: The first network node 13 can then manage the first and second location information. It should be noted that, as in... Figure 5-11 What is stated therein can be reversed and executed.

[0091] Now will refer to Figure 12b The flowchart depicted illustrates an example embodiment of a method for processing location reports in a wireless communication network, performed by a first network node 13. The actions do not necessarily have to be taken in the order stated below, but can be taken in any suitable order. Dashed boxes are optional features.

[0092] Action 1211: First network node 13 aligns its reporting configuration with second network node 14, where the reporting configuration defines an extension of the baseline periodic location information reporting configuration. This can be triggered upon request and / or during capability exchange. First network node 13 can align its reporting configuration with second network node 14 by requesting capabilities from second network node 14. First network node 13 can also align its reporting configuration with second network node 14 by receiving capability indications from second network node 14.

[0093] Action 1212: The first network node 13 can request location information from the second network node 14.

[0094] Action 1213: The first network node 13 may receive location information, including first and / or second location information, from the second network node 14 in accordance with the aligned report configuration.

[0095] Action 1214: The first network node 13 can manage location information.

[0096] The extension is defined by more granular periodic reporting intervals and / or more refined reporting volumes than the baseline periodic location information reporting configuration.

[0097] Action 1215: The first network node 13 may provide the second network node 14 with location information including first and / or second information in accordance with the aligned reporting configuration.

[0098] Now will refer to Figure 12cThe flowchart depicted below illustrates an example embodiment of a method for processing location reports in a wireless communication network, performed by a second network node 14. The actions do not necessarily have to be taken in the order stated below, but can be taken in any suitable order. Dashed boxes are optional features.

[0099] Action 1221: The second network node 14 aligns its reporting configuration with that of the first network node 13, where the reporting configuration defines an extension of the baseline periodic location information reporting configuration. This can be triggered upon request and / or during capability exchange. The second network node 14 can align its reporting configuration with the first network node 13 by receiving a capability request from the first network node 13. The second network node 14 can also align its reporting configuration with the first network node 13 by providing a capability indication to the first network node 13.

[0100] Action 1222: The second network node 14 can receive a request for location information from the first network node 13.

[0101] Action 1223: The second network node 14 may provide the first network node 13 with location information, including first and / or second location information, in accordance with the aligned reporting configuration.

[0102] Action 1224: The second network node 14 can receive instructions on the capabilities of the first network node 13 from the first network node 13.

[0103] Action 1225: The second network node 14 may receive location information, including first and / or second location information, from the first network node 13 in accordance with the aligned report configuration.

[0104] Action 1226: The second network node 14 can manage location information.

[0105] Extensions can be defined by configuring more granular periodic reporting intervals and / or more refined reporting volumes than baseline periodic location information reporting.

[0106] Now will refer to Figure 12d The flowchart depicted in the diagram illustrates an example embodiment of a method for handling location reports in a wireless communication network, performed by the first network node 13.

[0107] Action 1231: The first network node 13 receives a request from the second network node 14, the request including a proposed periodic reporting extension in addition to the baseline periodic reporting configuration.

[0108] Action 1232: The first network node 13 further transmits to the second network node 14: confirmation of the periodic location information extended configuration; alternative supported periodic location information extended configurations; or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the second network node 14. The extension can be defined as a finer-grained periodic reporting interval and / or a finer-grained reporting amount than the baseline periodic location information reporting configuration. The extension may include a millisecond reporting interval and a Boolean value indicating an unlimited reporting amount.

[0109] Now will refer to Figure 12e The flowchart depicted in the diagram illustrates an example embodiment of a method for handling location reports in a wireless communication network, performed by the second network node 14.

[0110] Action 1241: The second network node 14 sends a request to the first network node 13, the request including a proposed periodic reporting extension in addition to the baseline periodic reporting configuration.

[0111] Action 1242: The second network node 14 further receives from the first network node 13: confirmation of the periodic location information extended configuration, an alternative supported periodic location information extended configuration, or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the first network node 13. The extension can be defined as a finer-grained periodic reporting interval and / or a finer-grained reporting amount than the baseline periodic location information reporting configuration. The extension may include a millisecond reporting interval and a Boolean value indicating an unlimited reporting amount.

[0112] Now will refer to Figure 12f The flowcharts depicted in the diagram illustrate an example embodiment of a method performed by UE 10 for handling location reports in a wireless communication network.

[0113] Action 1251: UE 10 transmits a request to the first network node 13, which includes a proposed periodic reporting extension in addition to the baseline periodic reporting configuration.

[0114] Action 1252: UE 10 further receives from the first network node 13: confirmation of the periodic location information extended configuration, an alternative supported periodic location information extended configuration, or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the first network node 13. The extension can be defined as a finer-grained periodic reporting interval and / or a finer-grained reporting amount than the baseline periodic location information reporting configuration. The extension may include a millisecond reporting interval and a Boolean value indicating an unlimited reporting amount.

[0115] Figure 13This is a block diagram depicting an embodiment of a first network node 13 (such as a location node, network open function, or NF node) for processing location reports in a wireless communication network, according to embodiments herein.

[0116] The first network node 13 may include processing circuitry 1301, such as one or more processors, configured to perform the methods described herein.

[0117] The first network node 13 and / or processing circuitry 1301 are configured to align a reporting configuration with the second network node 14, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration. Alignment can be triggered upon request and / or during capability exchange.

[0118] The first network node 13 and / or processing circuit 1301 can be configured to request capabilities from the second network node 14.

[0119] The first network node 13 and / or processing circuit 1301 can be configured to request location information from the second network node 14.

[0120] The first network node 13 and / or processing circuit 1301 can be configured to receive a capability indication from the second network node 14.

[0121] The first network node 13 and / or processing circuit 1301 can be configured to receive location information, including first and / or second information, from the second network node 14 in accordance with an aligned report configuration.

[0122] The first network node 13 and / or processing circuit 1301 can be configured to manage location information.

[0123] The first network node 13 and / or processing circuit 1301 can be configured to provide a capability indication to the second network node 14.

[0124] The first network node 13 and / or processing circuit 1301 can be configured to provide location information, including first and / or second information, to the second network node 14 in accordance with an aligned reporting configuration.

[0125] According to some embodiments, a first network node 13 is configured to receive a request from a second network node 14, the request including, in addition to a baseline periodic reporting configuration, a proposed periodic reporting extension. The first network node 13 is further configured to transmit to the second network node 14: confirmation of the periodic location information extension configuration; an alternative supported periodic location information extension configuration; or a baseline response, wherein only the requested baseline periodic reporting configuration is supported, thereby aligning the reporting configuration with the second network node 14. The extension can be defined as a finer-grained periodic reporting interval and / or a finer-grained reporting amount than the baseline periodic location information reporting configuration. The extension may include a millisecond reporting interval and a Boolean value indicating an unlimited reporting amount.

[0126] The first network node 13 may include a memory 1306. The memory 1306 includes one or more units for storing data such as data packets, location information, baseline configuration, extended configuration, mappings, indications, status indications, instance IDs, UE IDs, mobility events, measurements, events, and applications that, when executed, perform the methods disclosed herein, and the like. Furthermore, the first network node 13 may include a communication interface 1307, which includes components such as a transmitter, receiver, transceiver, and / or one or more antennas.

[0127] The methods described herein for the first network node 13 are implemented, for example, by means of a computer program product 1308 or a computer program including instructions (i.e., software code portions), which, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by the first network node 13. The computer program product 1308 may be stored on a computer-readable storage medium 1309 (e.g., a disk, a Universal Serial Bus (USB) stick, or the like). The computer-readable storage medium 1309 on which the computer program product is stored may include instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by the first network node 13. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium. Therefore, the embodiments herein may disclose a first network node for disposing of tests in a wireless communication network, wherein the first network node includes processing circuitry and memory including instructions executable by the processing circuitry, thereby operating the first network node to perform any of the methods described herein.

[0128] Figure 14 This is a block diagram depicting an embodiment of a second network node 14 (such as a location node, UE, or AF node) for processing location reports in a wireless communication network 1, according to embodiments herein.

[0129] The second network node 14 may include processing circuitry 1401, such as one or more processors, configured to perform the methods described herein.

[0130] The second network node 14 and / or processing circuitry 1401 are configured to align a reporting configuration with the first network node 13, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration. Alignment can be triggered upon request and / or during capability exchange.

[0131] The second network node 14 and / or processing circuit 1401 can be configured to receive a request for capability from the first network node 13.

[0132] The second network node 14 and / or processing circuit 1401 can be configured to receive a request for location information from the second network node 14.

[0133] The second network node 14 and / or processing circuitry 1401 can be configured to provide capability indications to the first network node 13.

[0134] The second network node 14 and / or processing circuitry 1401 can be configured to provide location information, including first and / or second information, to the first network node 13 in accordance with an aligned reporting configuration.

[0135] The second network node 14 and / or processing circuit 1401 can be configured to receive location information, including first and / or second information, from the first network node 13 in accordance with an aligned report configuration.

[0136] The second network node 14 and / or processing circuit 1401 can be configured to manage location information.

[0137] The second network node can be configured to: transmit a request to the first network node 13, the request including a proposed periodic reporting extension in addition to the baseline periodic reporting configuration; and receive from the first network node 13: confirmation of the periodic location information extension configuration, an alternative supported periodic location information extension configuration, or a baseline response, wherein only the baseline periodic reporting configuration in the request is supported, thereby aligning the reporting configuration with the first network node 13.

[0138] In some embodiments, UE 10 is configured to process location reports in a wireless communication network, wherein UE is configured to transmit a request to a first network node 13, the request including a proposed periodic reporting extension in addition to a baseline periodic reporting configuration; and receive from the first network node 13: confirmation of the periodic location information extension configuration, an alternative supported periodic location information extension configuration, or a baseline response, wherein only the baseline periodic reporting configuration in the request is supported, thereby aligning the reporting configuration with the first network node 13.

[0139] The second network node 14 may include a memory 1406. The memory 1406 includes one or more units for storing data such as data packets, location information, capability indications, mappings, indications, status indications, instance IDs, UE IDs, mobility events, measurements, events, and applications that, when executed, perform the methods disclosed herein, and the like. Furthermore, the second network node 14 may include a communication interface 1407, which includes components such as a transmitter, receiver, transceiver, and / or one or more antennas.

[0140] The methods described herein for the second network node 14 are implemented, for example, by means of a computer program product 1408 or a computer program including instructions (i.e., software code portions), which, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by the second network node 14. The computer program product 1408 may be stored on a computer-readable storage medium 1409 (e.g., a disk, a Universal Serial Bus (USB) stick, or the like). The computer-readable storage medium 1409 on which the computer program product is stored may include instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by the second network node 14. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium. Therefore, the embodiments herein may disclose a second network node for disposing of tests in a wireless communication network, wherein the second network node includes processing circuitry and memory including instructions executable by the processing circuitry, thereby operating the second network node to perform any of the methods described herein.

[0141] It should be noted that “to…” and “receive from…” also cover embodiments in which messages are transmitted via an intermediate node, that is, “to” can be interpreted as “towards” and “from” can be interpreted as “transmitted by…” (not necessarily directly “to” or “from”).

[0142] In some embodiments, the more general term "network node" is used, and it can correspond to any type of radio network node or any network node that communicates with a wireless device and / or with another network node. Examples of network nodes are NodeB, MeNB, SeNB, network nodes belonging to a primary cell group (MCG) or secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio nodes such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node of control relay, base transceiver station (BTS), access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio headend (RRH), nodes in a distributed antenna system (DAS), etc.

[0143] In some embodiments, the term wireless device or user equipment (UE) is used without limitation, and it refers to any type of wireless device that communicates with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, UEs with proximity capabilities (also known as ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communication, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, etc.

[0144] The embodiments are applicable to any RAT or multi-RAT system in which a wireless device receives and / or transmits signals (e.g., data), such as New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rate GSM Evolution (GSM / EDGE), Global Microwave Access Interoperability (WiMax), or Ultra Mobile Broadband (UMB), with only a few possible implementations mentioned.

[0145] Those familiar with communication design will readily understand that functional components or circuits can be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions can be implemented together, such as in a single application-specific integrated circuit (ASIC) or in two or more separate devices with appropriate hardware and / or software interfaces between them. For example, some functions can be implemented on a processor shared with other functional components of a wireless device or network node.

[0146] Alternatively, some of the functional elements of the processing unit under discussion can be provided using dedicated hardware, while other functional elements are equipped with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not specifically refer to hardware capable of executing software and may implicitly include, but are not limited to, digital signal processor (DSP) hardware and / or program or application data. Other conventional and / or custom hardware may also be included. Designers of communication devices will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0147] Any suitable steps, methods, features, functions, or benefits disclosed herein can be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, including digital signal processors (DSPs), application-specific digital logic, and so on. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and so on. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0148] refer to Figure 15According to an embodiment, the communication system includes a telecommunications network 3210, such as a 3GPP-type cellular network, which includes an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 includes multiple base stations 3212a, 3212b, 3212c, such as NB, eNB, gNB, or other types of radio access points (examples of radio network node 12 herein), each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c can be connected to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE) 3291, located in coverage area 3213c and exemplified as UE 10, is configured to be wirelessly connected to or paged by the corresponding base station 3212c. A second UE 3292 in coverage area 3213a can be wirelessly connected to the corresponding base station 3212a. Although multiple UEs 3291 and 3292 are described in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or where only one UE is connected to the corresponding base station 3212.

[0149] Telecommunications network 3210 is itself connected to host computer 3230, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or may be embodied as processing resources in a server farm. Host computer 3230 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 3221, 3222 between telecommunications system 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230 or may pass through optional intermediate network 3220. Intermediate network 3220 may be one or more public, private, or hosted networks. Intermediate network 3220 (if any) may be a backbone network or the Internet; in particular, intermediate network 3220 may include two or more subnetworks (not shown).

[0150] Figure 15The communication system as a whole enables connectivity between one of the connected UEs 3291 and 3292 and the host computer 3230. This connectivity can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291 and 3292 are configured to transmit data and / or signaling via the OTT connection 3250 using the access network 3211, core network 3214, any intermediate network 3220, and possible additional infrastructure (not shown) as intermediaries. The OTT connection 3250 can be transparent in the sense that the participating communication devices traversing it are unaware of the routing of uplink and downlink communications. For example, the base station 3212 may not be notified or need not be notified of past routing of incoming downlink communications, where data originating from the host computer 3230 is to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, base station 3212 does not need to know the future routing of outbound uplink communication originating from UE 3291 toward host computer 3230.

[0151] In some embodiments, the telecommunications network 3210 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunications network 3210 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance or any similar organization) and can operate independently or together with other nodes to implement one or more functionalities of any node (including one or more network nodes and / or core network nodes) in the telecommunications network 3210.

[0152] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs) including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), RAN intelligent controllers (near real-time or non-real-time) with managed software or software plug-ins, such as near real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps), or any combination thereof (the adjective "open" indicates support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, Open Forward-Backward User Plane Interfaces, or Open Forward-Backward Management Plane Interfaces. Furthermore, ORAN access nodes can be logical nodes within physical nodes. Additionally, ORAN network nodes can be implemented in a virtualized environment (further described below) in which one or more network functions are virtualized. For example, the virtualized 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 similar technologies. Network nodes facilitate direct or indirect connections of user equipment (UE), such as connecting a UE (one or more of which may be collectively referred to as UE 3291, 3292) to the core network via one or more wireless connections.

[0153] Now refer to Figure 16 This section describes an example implementation of the UE, base station, and host computer discussed in the preceding paragraphs according to an embodiment. In the communication system 3300, the host computer 3310 includes hardware 3315, which includes a communication interface 3316 configured to establish and maintain wired or wireless connections to different communication devices of the communication system 3300. The host computer 3310 further includes processing circuitry 3318, which may have storage and / or processing capabilities. In particular, the processing circuitry 3318 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 3310 further includes software 3311, which is stored in the host computer 3310 or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. Host application 3312 is operable to provide services to remote users of UE 3330, such as those connected to UE 3330 via OTT connection 3350 terminated at UE 3330 and host computer 3310. When providing services to remote users, host application 3312 can provide user data transmitted using OTT connection 3350.

[0154] The communication system 3300 further includes a base station 3320 disposed in the telecommunications system and including hardware 3325, said hardware 3325 enabling the base station 3320 to communicate with a host computer 3310 and with a UE 3330. Hardware 3325 may include a communication interface 3326 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 3300, and for establishing and maintaining connections with at least the coverage area served by the base station 3320. Figure 16 The radio interface 3327 of the UE3330 (not shown in the diagram) is part of the wireless connection 3370. The communication interface 3326 can be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 can be direct, or it can be via the core network of the telecommunications system (…). Figure 16 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

[0155] The communication system 3300 further includes the already mentioned UE 3330. Its hardware 3335 may include a radio interface 3337 configured to establish and maintain wireless connections 3370 with base stations serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 3330 further includes software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. With the support of the host computer 3310, the client application 3332 may be operable to provide services to human or non-human users via the UE 3330. In host computer 3310, the executing host application 3312 can communicate with the executing client application 3332 via OTT connection 3350 terminated at UE 3330 and host computer 3310. When providing services to a user, client application 3332 can receive request data from host application 3312 and provide user data in response to the request data. OTT connection 3350 can transmit both request data and user data. Client application 3332 can interact with the user to generate the user data it provides.

[0156] Notice, Figure 16 The host computer 3310, base station 3320, and UE 3330 described herein can be respectively connected to Figure 15 The host computer 3230, one of the base stations 3212a, 3212b, and 3212c, and one of the UEs 3291 and 3292 are identical. That is to say, the internal operation of these entities can be as follows: Figure 16 As shown in the diagram, and independently, the surrounding network topology can be Figure 15 The surrounding network topology.

[0157] exist Figure 16 The OTT connection 3350 has been abstractly depicted to illustrate communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 3330, the service provider operating the host computer 3310, or both. When the OTT connection 3350 is active, the network infrastructure can further make decisions, through which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).

[0158] The wireless connection 3370 between UE 3330 and base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments utilize an OTT connection 3350 to improve the performance of the OTT services provided to UE 3330, wherein the wireless connection 3370 can form the final segment. More precisely, the teachings of some of these embodiments can improve performance because location information can be reported more flexibly and handled more effectively, and thus location information can provide benefits such as reduced user wait times and better responsiveness.

[0159] The measurement process can be provided for the purpose of monitoring data rates, latency, and other factors that improve one or more embodiments. In response to changes in the measurement results, optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 may further exist. The measurement process and / or network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310, the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that the software 3311, 3331 may calculate or estimate the monitored quantities from. Reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect the base station 3320, and may be unknown or imperceptible to the base station 3320. Such processes and functionalities are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates the measurement of throughput, propagation count, latency, etc., by the host computer 3310. Measurements can be performed because while the software 3311, 3331 monitors propagation count, errors, etc., the software 3311, 3331 uses the OTT connection 3350 to facilitate the transmission of messages, particularly empty or "false" messages.

[0160] Figure 17 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 15 and 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include references. Figure 17 The diagram shows the process. In the first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides user data by executing a host application. In the second step 3420, the host computer initiates a transmission carrying user data to the UE. In an optional third step 3430, in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0161] Figure 18 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 15 and16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include references. Figure 18 The diagram shows the process. In the first step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data via a host application. In the second step 3520, the host computer initiates a transmission carrying user data to the UE. Following the teachings of the embodiments described throughout this disclosure, the transmission can be carried out via a base station. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0162] Figure 19 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 15 and 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include references. Figure 19 The diagram illustrates this. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Alternatively, in an optional second step 3620, the UE provides user data. In an optional sub-step 3621 of the second step 3620, the UE provides user data by executing a client application. In an additional optional sub-step 3611 of the first step 3610, the UE executes a client application that provides user data as a response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of user data to the host computer in an optional third sub-step 3630. In a fourth step 3640 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the host computer receives the user data transmitted from the UE.

[0163] Figure 20 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 15 and 16 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include references. Figure 20 The diagram shows the method. In an optional first step 3710, the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In an optional second step 3720, the base station initiates a transmission of the received user data to a host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0164] It will be understood that the foregoing description and figures represent non-limiting examples of the methods and apparatus taught herein. In this way, the apparatus and techniques taught herein are not limited to the foregoing description and figures. Rather, the embodiments herein are limited only by the appended claims and their legal equivalents.

[0165] References: 1. 3GPP TS 37.355 v. 17.4.0 2. 3GPP TS 29.572 v. 17.4.0 3. 3GPP TS 29.515 v. 17.4.0 4. 3GPP TS 29.518 v. 17.4.0 appendix 3GPP TSG-CT WG4 Meeting #115-e C4-231abc E-Meeting, April 17-21, 2023 Regarding the use of this form help You can find it at http: / / www.3gpp.org / Change-Requests Full explanation.

[0166] 6.1.5.2.3 Type: LocationData Table 6.1.5.2.3-1: Definition of type LocationData 3GPP TSG-CT WG4 Meeting #115-e C4-231abc E-Meeting, April 17-21, 2023 Regarding the use of this form help You can find it at http: / / www.3gpp.org / Change-Requests Full explanation.

[0167] 6.4.6.2.3 Type: ProvidePosInfo Table 6.4.6.2.3-1: Definition of type ProvidePosInfo 3GPP TSG-CT WG4 Meeting #115-e C4-231abc E-Meeting, April 17-21, 2023 Regarding the use of this form help You can find it at http: / / www.3gpp.org / Change-Requests Full explanation.

[0168] 6.1.6.2.3 Type: LocationData Table 6.1.6.2.3-1: Definition of type LocationData 6.1.6.2.24 Type: PeriodicEventInfo Table 6.1.6.2.24-1: Definition of type PeriodicEventInfo 6.1.6.3.2 Simple Data Types The simple data types defined in Table 6.1.6.3.2-1 should be supported.

[0169] Table 6.1.6.3.2-1: Simple Data Types *************************Text skipped for clarity************************ *************************Text skipped for clarity************************ 3GPP TSG-RAN WG2 Meeting #121-e R2-231abc E-Meeting, April 17-26, 2023 Regarding the use of this form help You can find it at http: / / www.3gpp.org / Change-Requests Full explanation.

[0170] 6.4.1 Common Lower-Level IEs […] - PeriodicAssistanceDataControlParameters IE is used in the periodic auxiliary data delivery process as described in Sections 5.2.1a and 5.2.2a. PeriodicAssistanceDataControlParameters .

[0171] […] -PeriodicReportingIntervalMsSupport IE used by the target device PeriodicReportingIntervalMsSupport This indicates whether to support millisecond reporting intervals by providing a minimum millisecond reporting interval for periodic location information reporting.

[0172] […] -Polygon IE Polygon It is used to describe geographic shapes as defined in TS 23.032

[15] .

[0173] -Positioning Modes IE Positioning Modes It is used to indicate several positioning patterns using bitmaps.

[0174] -Scheduled Location Time Support IE used by the target device Scheduled Location Time Support To indicate the location of the scheduling request and the supported time base.

[0175] -Scheduled Location Time Support Per Mode IE used by the target device Scheduled Location Time Support Per Mode To indicate for by Positioning Modes The time base supported by the location request for each positioning mode is indicated.

[0176] […] 6.4.2 Common Positioning […] - Common IEs Request Location Information Common IEs Request Location InformationPublic IE browsers that carry LPP message type requests for location information.

[0177] […] 6.5.1.7 OTDOA Capability Information - OTDOA-Provide Capabilities IE used by the target device OTDOA-Provide Capabilities This indicates its ability to support OTDOA and provides its OTDOA positioning capabilities to the location server.

[0178] […] 6.5.2.9 GNSS Capability Information - A-GNSS-Provide Capabilities IE used by the target device A-GNSS-Provide-CapabilitiesThis indicates its A-GNSS support capability and provides its A-GNSS location capabilities (e.g., supported GNSS and auxiliary data) to the location server.

[0179] […] 6.5.3.4 E-CID Capability Information - ECID-Provide Capabilities IE used by the target device ECID-Provide Capabilities This indicates its support for ECID and provides its ECID location capabilities to the location server.

[0180] […] 6.5.4.4 TBS Capability Information - TBS-Provide Capabilities IE used by the target device TBS-Provide Capabilities This indicates its ability to support TBS and provides its TBS location capabilities to the location server.

[0181] […] 6.5.5.4 Sensor Capability Information -Sensor-Provide Capabilities IE used by the target device Sensor-Provide Capabilities Provides capabilities for sensor-based methods from location servers.

[0182] […] 6.5.6.4 WLAN Capability Information - WLAN-Provide Capabilities IE used by the target device WLAN-Provide Capabilites To provide the location server with its WLAN positioning capabilities.

[0183] […] 6.5.7.4 Bluetooth Capability Information - BT-Provide Capabilities IE used by the target device BT-Provide Capabilites It provides its Bluetooth positioning capabilities to the location server.

[0184] […] 6.5.9.4 NR E-CID Capability Information - NR-ECID-Provide Capabilities IE used by the target device NR-ECID-Provide Capabilities This indicates its support for NR E-CID and provides its NR E-CID positioning capabilities to the location server.

[0185] […] 6.5.10.6 NR DL-TDOA Capability Information - NR-DL-TDOA-Provide Capabilities IE used by the target device NR-DL-TDOA-Provide Capabilities This indicates its ability to support NR DL-TDOA and provides its NR DL-TDOA positioning capabilities to the location server.

[0186] […] 6.5.11.6 NR DL-AoD Capability Information - NR-DL-AoD-Provide Capabilities IE used by the target device NR-DL-AoD-Provide Capabilities This indicates its support for NR DL-AoD and provides its NR DL-AoD positioning capabilities to the location server.

[0187] […] 6.5.12.6 NR Multi-RTT Capability Information - NR-Multi-RTT-Provide Capabilities IE used by the target device NR-Multi-RTT-Provide Capabilities This indicates its support for NR multi-RTT capabilities and provides its NR multi-RTT positioning capabilities to the location server.

[0188] 3GPP TSG-RAN WG2 Meeting #121-e R2-231abc E-Meeting, April 17-26, 2023 Regarding the use of this table Help : Can be found at http: / / www.3gpp.org / Change-Requests for a full description.

[0189] 6.4.1 Common Lower-Level IEs […] - Periodic Assistance Data Control Parameters IE is used in the periodic auxiliary data delivery process as described in Sections 5.2.1a and 5.2.2a. Periodic Assistance Data Control Parameters .

[0190] […] - Periodic Reporting Interval Ms Support IE used by the target device Periodic Reporting Interval Ms Support This indicates whether to support millisecond reporting intervals by providing a minimum millisecond reporting interval for periodic location information reporting.

[0191] […] - Polygon IE Polygon It is used to describe geographic shapes as defined in TS 23.032

[15] .

[0192] - Positioning Modes IE Positioning Modes It is used to indicate several positioning patterns using bitmaps.

[0193] - Scheduled Location Time Support IE used by the target device Scheduled Location Time Support To indicate the location of the scheduling request and the supported time base.

[0194] - Scheduled Location Time Support Per Mode IE used by the target device Scheduled Location Time Support Per Mode To indicate for by Positioning Modes The time base supported by the location request for each positioning mode is indicated.

[0195] […] 6.4.2 Common Positioning […] - Common IEs Request Location Information Common IEs Request Location Information Public IE browsers that carry LPP message type requests for location information.

[0196] […] 6.5.1.7 OTDOA Capability Information - OTDOA-ProvideCapabilities IE used by the target device OTDOA - Provide Capabilities This indicates its ability to support OTDOA and provides its OTDOA positioning capabilities to the location server.

[0197] […] 6.5.2.9 GNSS Capability Information - A - GNSS - Provide Capabilities IE used by the target device A - GNSS - Provide - Capabilities This indicates its A-GNSS support capability and provides its A-GNSS location capabilities (e.g., supported GNSS and auxiliary data) to the location server.

[0198] […] 6.5.3.4 E-CID Capability Information - ECID - Provide Capabilities IE used by the target device ECID - Provide Capabilities This indicates its support for ECID and provides its ECID location capabilities to the location server.

[0199] […] 6.5.4.4 TBS Capability Information - TBS - Provide Capabilities IE used by the target device TBS - Provide Capabilities This indicates its ability to support TBS and provides its TBS location capabilities to the location server.

[0200] […] 6.5.5.4 Sensor Capability Information - Sensor - Provide Capabilities IE used by the target device Sensor - Provide Capabilities Provides capabilities for sensor-based methods from location servers.

[0201] […] 6.5.6.4 WLAN Capability Information - WLAN - Provide Capabilities IE used by the target device WLAN - Provide Capabilites To provide the location server with its WLAN positioning capabilities.

[0202] […] 6.5.7.4 Bluetooth Capability Information - BT - Provide Capabilities IE used by the target device BT - Provide Capabilites It provides its Bluetooth positioning capabilities to the location server.

[0203] […] 6.5.9.4 NR E - CID Capability Information - NR - ECID - Provide Capabilities IE used by the target device NR - ECID - Provide Capabilities This indicates its support for NR E-CID and provides its NR E-CID positioning capabilities to the location server.

[0204] […] 6.5.10.6 NR DL-TDOA Capability Information - NR - DL - TDOA - Provide Capabilities IE used by the target device NR - DL - TDOA - Provide Capabilities This indicates its ability to support NR DL-TDOA and provides its NR DL-TDOA positioning capabilities to the location server.

[0205] […] 6.5.11.6 NR DL-AoD Capability Information - NR - DL - AoD - Provide Capabilities IE used by the target device NR - DL - AoD - Provide Capabilities This indicates its support for NR DL-AoD and provides its NR DL-AoD positioning capabilities to the location server.

[0206] […] 6.5.12.6 NR Multi-RTT Capability Information - NR - Multi - RTT - Provide Capabilities IE used by the target device NR - Multi - RTT - Provide Capabilities This indicates its support for NR multi-RTT capabilities and provides its NR multi-RTT positioning capabilities to the location server.

Claims

1. A method for processing location reports in a wireless communication network, performed by a first network node (13), the method comprising: - Receive a request (1231) from the second network node (14), the request including, in addition to the baseline periodic reporting configuration, a proposed periodic reporting extension; and - Transmit (1232) to the second network node (14): confirmation of the periodic location information extension configuration; alternative supported periodic location information extension configuration; or baseline response, wherein only the baseline periodic reporting configuration in the request is supported, and thereby aligning the reporting configuration with the second network node (14).

2. The method of claim 1, wherein the extension is defined by the following: A more refined periodic reporting interval and / or a more refined reporting volume than the baseline periodic location information reporting configuration.

3. The method according to any one of claims 1-2, wherein the extension includes a millisecond reporting interval and a Boolean value indicating an unlimited amount of reporting.

4. A method for processing location reports in a wireless communication network, performed by a second network node (14), the method comprising: - A request (1241) is transmitted to the first network node (13), the request including, in addition to the baseline periodic reporting configuration, a proposed periodic reporting extension; and - Receive (1242) from the first network node (13): confirmation of the periodic location information extension configuration, alternative supported periodic location information extension configuration, or baseline response, wherein only the baseline periodic reporting configuration in the request is supported, and thereby aligning the reporting configuration with the first network node (13).

5. The method of claim 4, wherein the extension is defined by the following: A more refined periodic reporting interval and / or a more refined reporting volume than the baseline periodic location information reporting configuration.

6. The method according to any one of claims 4-5, wherein the extension includes a millisecond reporting interval and a Boolean value indicating an unlimited amount of reporting.

7. A method for processing location reports in a wireless communication network, performed by a user equipment (UE) (14), the method comprising: - A request (1251) is transmitted to the first network node (13), the request including, in addition to the baseline periodic reporting configuration, a proposed periodic reporting extension; and - Receive (1252) from the first network node (13): confirmation of the periodic location information extension configuration, alternative supported periodic location information extension configuration, or baseline response, wherein only the baseline periodic reporting configuration in the request is supported, and thereby aligning the reporting configuration with the first network node (13).

8. The method of claim 7, wherein the extension is defined by the following: A more refined periodic reporting interval and / or a more refined reporting volume than the baseline periodic location information reporting configuration.

9. The method according to any one of claims 7-8, wherein the extension includes a millisecond reporting interval and a Boolean value indicating an unlimited amount of reporting.

10. A method for processing location reports in a wireless communication network, performed by a first network node (13), the method comprising: - Align the reporting configuration with the second network node (14) (1211), wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

11. The method of claim 10, wherein the alignment (1211) of the report configuration with the second network node (14) is triggered upon request and / or during capability exchange.

12. The method according to any one of claims 10-11, wherein aligning the report configuration with the second network node (1211) includes requesting capability from the second network node (14).

13. The method according to claims 10-12, wherein aligning the report configuration with the second network node (1211) includes an indication of receiving capability from the second network node (14).

14. The method according to any one of claims 10-13, comprising: - Request (1212) location information from the second network node (14).

15. The method according to claims 10-14, comprising: - According to the aligned reporting configuration, receive (1213) location information including first and / or second location information from the second network node 14.

16. The method of claim 15, comprising: - Manage the location information described in (1214).

17. The method according to claims 10-16, wherein the extension is defined by the following: A more refined periodic reporting interval and / or a more refined reporting volume than the baseline periodic location information reporting configuration.

18. The method according to claims 10-17, comprising: - In accordance with the aligned reporting configuration, the second network node (14) is provided with (1215) location information including the first and / or second information.

19. A method for processing location reports in a wireless communication network, performed by a second network node (14), the method comprising: - Align the reporting configuration with the first network node (13) (1221), wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

20. The method of claim 19, wherein the alignment (1221) of the report configuration is triggered upon request and / or during capability exchange.

21. The method according to any one of claims 19-20, wherein aligning the report configuration with the first network node (1221) includes receiving a request for capability from the first network node (13).

22. The method of claims 19-21, wherein aligning the report configuration with the first network node (1221) includes an indication to provide capabilities to the first network node (13).

23. The method according to any one of claims 19-22, comprising: - Receive (1222) a request for location information from the first network node (13).

24. The method according to claims 19-23, comprising: - In accordance with the aligned reporting configuration, the first network node (13) is provided with (1223) location information including first and / or second location information.

25. The method according to claims 19-24, comprising: - Receive (1224) an indication of the capabilities of the first network node (15) from the first network node (14).

26. The method according to claims 19-25, comprising: - According to the aligned reporting configuration, receive (1225) location information, first and / or second information from the first network node 14.

27. The method of claim 26, comprising: - Manage the location information described in (1226).

28. The method according to claims 19-27, wherein the extension is defined by the following: A more refined periodic reporting interval and / or a more refined reporting volume than the baseline periodic location information reporting configuration.

29. A first network node (13) for processing location reports in a wireless communication network, wherein the first network node is configured to: Receive a request from the second network node (14), the request including, in addition to the baseline periodic reporting configuration, a proposed periodic reporting extension; and The following are transmitted to the second network node (14): confirmation of the periodic location information extension configuration; alternative supported periodic location information extension configuration; or baseline response, wherein only the baseline periodic reporting configuration in the request is supported, and thereby aligning the reporting configuration with the second network node (14).

30. A second network node (14) for processing location reports in a wireless communication network, wherein the second network node is configured to A request is transmitted to the first network node (13), the request including, in addition to the baseline periodic reporting configuration, a proposed periodic reporting extension; and Receive from the first network node (13): confirmation of the periodic location information extension configuration, alternative supported periodic location information extension configuration, or baseline response, wherein only the baseline periodic reporting configuration in the request is supported, and thereby align the reporting configuration with the first network node (13).

31. A user equipment (UE) (14) for processing location reports in a wireless communication network, wherein the UE is configured to A request is transmitted to the first network node (13), the request including, in addition to the baseline periodic reporting configuration, a proposed periodic reporting extension; and Receive from the first network node (13): confirmation of the periodic location information extension configuration, alternative supported periodic location information extension configuration, or baseline response, wherein only the baseline periodic reporting configuration in the request is supported, and thereby align the reporting configuration with the first network node (13).

32. A first network node (13) for processing location reports in a wireless communication network, wherein the first network node (13) is configured to Align the reporting configuration with the second network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

33. The first network node (13) of claim 32, wherein the first network node is configured to perform the method of any one of claims 11-18.

34. A second network node (14) for processing location reports in a wireless communication network, wherein the second network node (14) is configured to: Align the reporting configuration with the first network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

35. The second network node (14) of claim 34, wherein the second network node (14) is configured to perform the method of any one of claims 20-28.

36. A first network node for processing location reports in a wireless communication network, comprising a processor and a memory, the memory containing instructions executable by the processor, wherein the first network node operates for... Align the reporting configuration with the second network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

37. A second network node for processing location reports in a wireless communication network, comprising a processor and a memory, the memory containing instructions executable by the processor, wherein the second network node operates to... Align the reporting configuration with the first network node, wherein the reporting configuration defines an extension of the baseline periodic location information reporting configuration.

Images