Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/02—Services making use of location information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/2866—Architectures; Arrangements
  • H04L67/30—Profiles
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management

Definitions

• Various example embodiments relate generally to positioning or locat ing of a device.
• the number of services which require location information is heavily increasing.
• other services may now require the use of location information: machine-to-machine (M2M) and Internet of Things (IoT) devices, commercial ser vices and also network optimization.
• M2M machine-to-machine
• IoT Internet of Things
• the related use cases may comprise e.g. reg ulatory requirements for emergency call positioning, public safety & security and lawful interception, positioning of IoT devices, indoor positioning for mobile ad vertising, and leveraging subscriber location to optimize network coverage and re cute costs.
• Figure 1 presents a wireless communication system, according to an embodiment
• Figure 2 shows a radio access network and a core network, according to an embodiment
• Figures 3 depicts a method, according to an embodiment
• FIGS. 4 and 5 illustrate signaling flow diagrams, according to some embodiments
• FIGS 6 and 7 depict methods, according to some embodiments.
• FIGS. 8, 9 and 10 illustrate apparatuses, according to some embodi ments. DESCRIPTION OF EMBODIMENTS
• phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
• phrase “at least one of the following: A, B, C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
• Embodiments described may be implemented in a radio system, such as one comprising at least one of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE).
• Term 'eLTE' here denotes the LTE evolution that connects to a 5G core.
• LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).
• a term “resource” may refer to radio resources, such as a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc.
• PRB physical resource block
• transmission and/or “reception” may refer to wirelessly transmit ting and/or receiving via a wireless propagation channel on radio resources
• the embodiments are not, however, restricted to the systems/RATs given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties.
• a suitable communications system is the 5G system.
• the 3GPP solution to 5G is re ferred to as New Radio (NR).
• 5G has been envisaged to use multiple-input-multiple- output (MIMO) multi-antenna transmission techniques, more base stations or nodes than the current network deployments of LTE (a so-called small cell con cept), including macro sites operating in co-operation with smaller local area ac cess nodes and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
• MIMO multiple-input-multiple- output
• 5G will likely be comprised of more than one radio access technology / radio access network (RAT/RAN), each optimized for certain use cases and/or spectrum.
• 5G mobile communications may have a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applica tions, including vehicular safety, different sensors and real-time control.
• 5G is ex pected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and being integrable with existing legacy radio access technologies, such as the LTE.
• the current architecture in LTE networks is distributed in the radio and centralized in the core network.
• the low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC).
• MEC multi-access edge computing
• 5G enables analytics and knowledge genera tion to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors.
• MEC provides a distributed computing environ ment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time.
• Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer- to-peer ad hoc networking and processing also classifiable as local cloud/fog com puting and grid/mesh computing, dew computing, mobile edge computing, cloud let, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical), critical communications (autono mous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).
• Edge cloud may be brought into RAN by utilizing network function virtualization (NVF) and software defined networking (SDN).
• NVF network function virtualization
• SDN software defined networking
• edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts.
• Network slicing allows multiple virtual networks to be created on top of a common shared physical infrastructure. The virtual networks are then custom ised to meet the specific needs of applications, services, devices, customers or op erators.
• the architecture may be based on a so-called CU-DU (central unit - distributed unit) split, where one gNB-CU controls several gNB-DUs.
• the term 'gNB' may correspond in 5G to the eNB in LTE.
• the gNBs (one or more) may communicate with one or more UEs.
• the gNB-CU (central node) may control a plurality of spatially separated gNB-DUs, acting at least as trans mit/receive (Tx/Rx) nodes.
• the gNB-DUs also called DU
• the gNB-DUs may comprise e.g.
• RLC radio link control
• MAC medium access control
• PHY physical
• gNB-CU also called a CU
• PDCP packet data convergence protocol
• RRC radio resource control
• IP internet protocol
• network slicing may be a form of virtual network architecture using the same principles behind software defined networking (SDN) and network functions virtualisation (NFV) in fixed networks.
• SDN and NFV may deliver greater network flexibility by allowing traditional network architectures to be partitioned into virtual elements that can be linked (also through software) .
• N et- work slicing allows multiple virtual networks to be created on top of a common shared physical infrastructure. The virtual networks are then customised to meet the specific needs of applications, services, devices, customers or operators.
• the plurality of gNBs (access points/nodes), each comprising the CU and one or more DUs, may be connected to each other via the Xn interface over which the gNBs may negotiate.
• the gNBs may also be connected over next genera tion (NG) interfaces to a 5G core network (5GC), which may be a 5G equivalent for the core network of LTE.
• 5G CU-DU split architecture may be implemented using cloud/server so that the CU having higher layers locates in the cloud and the DU is closer to or comprises actual radio and antenna unit.
• LTE/LTE-A/eLTE There are similar plans ongoing for LTE/LTE-A/eLTE as well.
• the next step may be to combine soft ware (SW) so that one common SW controls both radio access networks /technol ogies (RAN/RAT).
• SW soft ware
• RAN/RAT radio access networks /technol ogies
• 5G (or new radio, NR) networks are being designed to sup port multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well.
• NR may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling.
• Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future railway/maritime /aeronautical communications.
• Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in partic ular mega-constellations (systems in which hundreds of (nano) satellites are de ployed). Each satellite in the mega-constellation may cover several satellite-ena bled network entities that create on-ground cells.
• the on-ground cells may be cre ated through an on-ground relay node or by a gNB located on-ground or in a satel lite.
• the embodiments may be also applicable to narrow-band (NB) Inter- net-of-things (loT) systems which may enable a wide range of devices and services to be connected using cellular telecommunications bands.
• NB-loT is a narrowband radio technology designed for the Internet of Things (loT) and is one of technolo gies standardized by the 3rd Generation Partnership Project (3GPP).
• 3GPP loT technologies also suitable to implement the embodiments include machine type communication (MTC) and eMTC (enhanced Machine-Type Communication).
• MTC machine type communication
• eMTC enhanced Machine-Type Communication
• the NB-loT technology is deployed "in-band" in spectrum allocated to Long Term Evolution (LTE) - using resource blocks within a normal LTE carrier, or in the unused resource blocks within a LTE carrier’s guard-band - or "standalone" for deployments in dedicated spectrum.
• LTE Long Term Evolution
• FIG. 1 illustrates an example of a communication system to which em bodiments of the invention may be applied.
• the system may comprise a control node 110 providing a cell 100.
• Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. In another point of view, the cell may define a coverage area or a service area of the access node 110.
• the control node 110 may be an evolved Node B (eNB) as in the LTE and LTE-A, ng-eNB as in eLTE, gNB of 5G, or any other apparatus capable of controlling radio communication and managing radio resources within a cell.
• the control node 110 may be called a base station, network node, or an access node.
• the system may be a cellular communication system composed of a ra dio access network of access nodes, each controlling a respective cell or cells.
• the access node 110 may provide user equipment (UE) 120 (one or more UEs) with wireless access to other networks such as the Internet.
• the wireless access may comprise downlink (DL) communication from the control node 110 to the UE 120 and uplink (UL) communication from the UE 120 to the control node 110.
• DL downlink
• UL uplink
• one or more local area access nodes may be arranged such that a cell provided by the local area access node at least partially overlaps the cell 100 of the macro cell access node 110.
• the local area access node may provide wireless access within a sub-cell that may be comprised within a macro cell 100. Examples of the sub-cell may include a micro, pico and/or femto cell. Typically, the sub-cell provides a hot spot within a macro cell.
• the operation of the local area access node may be controlled by an access node under whose control area the sub cell is provided. In general, the control node may be likewise called a base station, network node, or an access node.
• terminal device refers to any end device that may be capable of wireless communication.
• a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT).
• UE user equipment
• SS Subscriber Station
• MS Mobile Station
• AT Access Terminal
• the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wire less local loop phones, a tablet, a wearable terminal device, a personal digital assis tant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback ap pliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an In ternet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a con sumer electronics device, a device operating on commercial and
• the access nodes may be connected to each other with an interface.
• LTE specifications call such an interface as X2 interface.
• IEEE 802.11 network i.e. wireless local area network, WLAN, WiFi
• Xw may be provided between ac cess points.
• An interface between an eLTE access point and a 5G access point may be called Xn.
• Other communication methods between the access nodes may also be possible.
• the access node 110 of the RAN may be further connected via another interface to a core network of the cellular communication system.
• the LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise a mobility management entity (MME) and a gateway node.
• the MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network.
• the gateway node may handle data routing in the core network and to/from the terminal devices.
• the 5G specifications specify the core network as a 5G core (5GC). This is shown in Figure 2.
• the core network may comprise an access and mobility man agement function (AMF), a session management function (SMF) and a user plane function (UPF), among others.
• AMF access and mobility man agement function
• SMF session management function
• UPF user plane function
• the AMF may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network.
• the SMF may handle selection and control of user plane connections for PDU sessions between the terminal de vices and the core network.
• the UPF may handle data routing in the core network and to/from the terminal devices.
• M2M/loT massive or industrial loT
• special low-cost single-purpose devices could be used for tracking of vehicles (like trolleys) for au tomated driving and logistics without human interaction.
• This can imply hundreds or thousands of devices in a spatially restricted area (indoor or outdoor) with sin gle or multiple base stations for coverage.
• it may be inefficient to perform location request procedures for each device on a per-need basis, since there may be a continuous and permanent need for positioning data.
• TTFF Time to First Fix
• the existing location procedure for a location request transaction is de scribed in TS 38.305 Stage 2 functional specification of User Equipment (UE) posi tioning in NG-RAN, sections 5.1-5.2.
• the 5GC may comprise a location management function (LMF), as shown in Figure 2 with dotted lines.
• the AMF may receive a request for a location service associated with a particular target UE (e.g. UE 120) from another entity (e.g., such as an external client of Figure 2 or a Gateway Mobile Location Center, GMLC) or the AMF itself decides to initiate some location service on behalf of a particular target UE (e.g., for an IMS emergency call from the UE).
• a particular target UE e.g. UE 120
• another entity e.g., such as an external client of Figure 2 or a Gateway Mobile Location Center, GMLC
• GMLC Gateway Mobile Location Center
• the AMF may then send a location services request to the LMF.
• the LMF processes the location services request which may include transferring assistance data to the target UE to assist with UE-based and/or UE-assisted positioning and/or may include positioning of the target UE.
• the LMF then returns the result of the location service back to the AMF (e.g., a position esti mate for the UE.
• the AMF returns the location service result to this entity.
• the LMF may have access to information from RAN (e.g. to support Observed Time Difference Of Arrival, OTDOA, positioning method using e.g. downlink measure ments obtained by a target UE of signals from eNBs/gNBs and/or positioning ref erence signals (PRS).
• RAN e.g. to support Observed Time Difference Of Arrival, OTDOA, positioning method using e.g. downlink measure ments obtained by a target UE of signals from eNBs/gNBs and/or
• the LMF manages the support of different location services for target UEs, including positioning of UEs and delivery of assistance data to UEs.
• the LMF may interact with the serving gNB or serving ng-eNB for a target UE in order to obtain position measurements for the UE, including uplink measurements made by an ng-eNB and downlink measurements made by the UE that were provided to an ng-eNB as part of other functions such as for support of handover.
• the LMF may interact with a target UE in order to deliver assistance data if requested for a particular location service, or to obtain a location estimate if that was requested.
• the LMF may decide on the position methods to be used, based on factors that may include the location ser vices (LCS) client type, the required quality of services (QoS), UE positioning capa bilities, gNB positioning capabilities and/or positioning capabilities of other access nodes (e.g. ng-eNB).
• the LMF may then invoke these positioning methods in the UE, serving gNB and/or other access nodes.
• the positioning methods may yield a location estimate for UE-based position methods and/or positioning measure ments for UE-assisted and network-based position methods.
• the LMF may com bine all the received results and determine a single location estimate for the target UE (hybrid positioning). Additional information like accuracy of the location esti mate and velocity may also be determined.
• the LCS request may provide a type of periodic or triggered location reporting being requested and associated parameters (attributes).
• the LCS Service Request may include the time interval between successive location reports, the total number of reports and may include location QoS.
• the LCS Service Request may include details of the target area, whether the event to be reported is the UE being inside, entering into or leaving the target area, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports, and whether only one location report is required or more than one.
• the LCS Service Request may include a threshold linear distance, the duration of event reporting, the minimum and maximum time intervals be tween successive event reports, the maximum event sampling interval, whether lo cation estimates shall be included in event reports (and associated location QoS), and whether only one location report is required or more than one.
• location request is deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events.
• a location request is sent for a target UE (or group of target UEs) and expects to receive a response containing the indication of event occurrence and location information if requested for the target UE (or group of target UEs) at some future time (or times), which may be associated with specific events associated with the target UE (or group of target UEs).
• These location request may cause the location of the UE to be determined periodically, per a predetermined trigger (e.g. certain movement and/or motion of the UE), and/or when the UE is available. Especially periodic location determinations may cause significant signaling overhead.
• the method may be performed by a radio access network (RAN) device, not part of the core network.
• RAN radio access network
• the RAN device also called RAN node
• location functionalities may be comprised in a Location Management Component (RAN LMC or simply LMC) shown in Figure 2, wherein the LMC functions as part of the RAN, in order to pro vide at least some functionalities similar to a Location Management Function (LMF) of the core network depicted in TS 38.305 and discussed above, such as how the positioning of the target device is made.
• LMF Location Management Function
• the LMC replaces the need for LMF of core, as the RAN LMC handles these functionalities (hence LMF is shows with doted lines in Figure 2).
• the LMF of the core is maintained as a central control unit for positioning purposes while the RAN LMC supports local positioning functions.
• the division of labour between the two may be configurable.
• the functionalities explained above in connection of LMF may be performed by the LMC as well.
• the proposed positioning method may reduce the time to obtain the lo cation estimation (i.e., to reduce the latency) and optimize the amount of signaling as well as of location assistance information that needs to be exchanged.
• the triggering of the location session may be performed by the RAN node itself, prior to receiving any LCS request e.g. from an external client in form of mobile terminating location request (MT-LR), from a target device (such as the terminal device to be located) in form of e.g. mobile originated location re quest (MO-LR), or from the core (e.g. from the AMF) in form of network induced location request (Nl-LR), e.g. emergency call.
• MT-LR mobile terminating location request
• MO-LR mobile originated location re quest
• Nl-LR network induced location request
• the LMC may support any of the lo cation request types that are defined for an LMF, i.e. Nl-LR, MT-LR, immediate lo cation requests, and deferred location requests.
• the LMC may be able to support location service requests from functions internal to the RAN node, for purposes such as Radio Resource Man agement (RRM), Minimization of Drive Tests (MDT), etc. This type of location request can be called RAN Induced Location Request (Rl-LR).
• RRM Radio Resource Man agement
• MDT Minimization of Drive Tests
• the LMC may effi ciently handle Rl-LR since the necessary operations are internal to the RAN and can therefore be handled locally, avoiding the additional latency and network interface signaling that would be incurred if Rl-LR was handled by the LMF.
• One possible use case is location determination of e.g. sensors.
• the RAN device may have ca pabilities for: receiving location service requests for a target UE from the serving AMF or from an internal function of the serving RAN node (e.g. RRM, MDT, etc.); decide on the position method (s) to be used; interact with other internal functions of the serving RAN node in order to e.g. obtain position measurements for the UE; interact with a target UE in order to e.g. deliver assistance data or to obtain a loca tion estimate; interact with neighboring RAN nodes in order to e.g. obtain position measurements for the UE or coordinate dynamic PRS configuration; calculate or verify the final location of the UE and provide it to the requesting entity or request ing internal function of the serving RAN node.
• an internal function of the serving RAN node e.g. RRM, MDT, etc.
• the RAN device may have ca pabilities for: receiving location service requests for a target UE from the serving AMF or from an internal function of the serving RAN node (e
• Figure 3 depicts an example method that is useable for such RCP.
• the RAN device performing the method of Figure 3 is a gNB, a ng-eNB or the location management component (LMC), which can be but need not be co located with the access node 110 - LMC may be a separate RAN entity having wired or wireless connection to the gNB as shown in Figure 2, for example.
• the LMC may be a function of the gNB-CU, possibly as part of gNB-CU-CP (gNB-central unit-control plane).
• the RAN device may in step 300 decide that a lo cation of the target device (such as a terminal device, e.g. sensor) is to be deter mined.
• the RAN device may determine location of the target device.
• the RAN device may receive a location request.
• the RAN device may respond to the location request by indicating the location of the target device. This may comprise indicating the location of the target device to the requester.
• the loca tion request may come many different sources (such as the target device or AMF, to mention only a few) and correspondingly the responding of step 306 may be to different directions, depending on the requester.
• positioning measurements and other related procedures in RAN may be conducted continuously and proactively by the LMC of the RAN. This may mean that positioning measurements and corresponding location information are already available when a location request from a client (external, UE, network) is received.
• the time-to-first-fix (TTFF) is significantly re prised compared to serial invocation of measurement procedures triggered by lo cation request.
• the deciding of step 300 is performed before receiv ing any location requests (also called location service, LCS, requests). This may pro vide for proactive and efficient location feedback, upon an LCS request has been received.
• LCS location service
• the deciding of step 300 is based on information as sociated with at least one of the following: target device registration, target device context setup, target device context modification.
• the RAN device may receive this registration and/or context setup associated information, such as RCP assistance information (RCPAI), from the core network.
• RCP assistance information RCP assistance information
• the in formation is received when initial UE context is established or modified for the tar get device, e.g. by use of NGAP messages such as INITIAL CONTEXT SETUP RE QUEST message or UE CONTEXT MODIFICATION REQUEST message.
• the "associ ated" may denote that the information is received in connection of target device registration, target device context setup and/or target device context modification.
• the deciding is based on information associated with at least one of the following: bearer context setup for the target device, bearer con text modification for the target device.
• the network device may re ceive this bearer associated information, such as RCP assistance information (RCPAI), from the core network.
• RCP assistance information RCP assistance information
• the information is received at the time a protocol data unit (PDU) session is established or modified, e.g. by use of NGAP messages such as PDU SESSION RESOURCE SETUP REQUEST message or PDU SESSION RESOURCE MODIFY REQUEST message.
• PDU protocol data unit
• the "associated" may de note that the information is received in connection of bearer context setup for the target device and/or bearer context modification for the target device.
• the information is received from the core network, such as from AMF therein. In some other embodiments, the information is at least partially received from the target device (e.g. the UE 120).
• the information may indicate at least one of the following: target device type, target device subscription information, application type applied by the target de vice, device capability information regarding positioning, location profile indicator.
• the location profile indicator (LPI), also called positioning profile indicator) may be e.g. an index to one of potentially multiple location profiles configured to the RAN node, wherein each location profile defines specific attributes for the location determination.
• the location profile indicator may be specific to a particular target device, or it may be specific to a particular area, or it may be specific to the RAN node such that the RAN node applies the same LP1 for each target device under its coverage.
• the deciding of step 300 may then be based on at least one of these in formation elements.
• the target device type may indicate that the de vice is a sensor, and there may be a rule to trigger the proactive location determi nation for each sensor in a predetermined area.
• the subscriber information of the target device may indicate that the device and/or the subscriber belongs to a group for which the proactive location determination is to be per formed.
• the application type used at the target device may be such that the device may benefit from proactive location determination.
• An exam ple application may be any application that may require continuous location deter mination such as automatic guided vehicles (AGVs), remote controlled UAVs, or ve hicle platoons.
• the location profile indicator may indicate that the proactive loca tion determination should be applied for a particular target device or area, for ex ample.
• the deciding is based on a flag in the information.
• a flag e.g. in subscription information for each device be longing to the group of certain type of devices.
• config uration of the proactive positioning via an Application Function is performed, for example by means of an inter-working function such as a Network Exposure Func tion (NEF) in the 5G core which configures activation of proactive positioning in the network based on input.
• NEF Network Exposure Func tion
• One specific example could be maintenance of AGVs and other equipment in a factory where continuous positioning is temporarily dis abled.
• the deciding in step 300 is based on a preconfigured rule stored in the RAN device.
• a local configuration may be stored in the RAN device defining that the location determination, such as RCP, may be per formed for all target devices in the area, e.g. in a private network.
• the location determination such as RCP
• the proactive location determination is performed for all certain type of target devices.
• determining the location of the target device in step 302 may be based on predefined attributes. These may be preconfigured and stored at the RAN device or may be configured locally in the RAN device.
• determining the location of the target device in step 302 is based on attributes indicated from core network as part of at least one of the following: target device registration, target device context setup, target device context modification, bearer context setup for the target de vice, bearer context modification for the target device.
• the at tributes may be received from the core as a location profile indicator included in the RCPA1.
• the attributes define at least one of the following: time interval between target device positioning fixes for periodic reporting, an event trigger for event based reporting (such as certain type of traffic detected or movement detected), quality of service for the location determination (such as QoS class, e.g. best effort class or assured class, accuracy, response time), trigger event for measurement report such as A3 "Neighbor becomes offset better than serving", or any of the parameters/attributes mentioned in connection of LMF for periodic reporting, area event reporting, and motion event reporting.
• an event trigger for event based reporting such as certain type of traffic detected or movement detected
• quality of service for the location determination such as QoS class, e.g. best effort class or assured class, accuracy, response time
• trigger event for measurement report such as A3 "Neighbor becomes offset better than serving"
• the RAN device may adapt attributes e.g. based on the target device type or the application being used at the target device. For exam ple, the rate at which position is being determined, measurements are being made, etc. may be modified dynamically.
• determining the location in step 302 is at least par tially based on target device positioning capabilities.
• RAN device positioning capabilities and/or positioning capabilities of other access nodes may affect how the determination is performed.
• These target device positioning capabilities may include e.g. information on does the target device support at least one of the following: PRS monitoring, Global Nav igation Satellite System (GNSS), Assisted GNSS (e.g. GNSSs supported (such as GPS, GLONASS, Galileo, Beidou, etc.) and assistance data supported, such as ionospheric model support], OTDOA (e.g.
• OTDOA mode supported bands, max supported PRS bandwidth, PRS frequency hopping, etc.
• enhanced cell ID E-C1D
• AoD Angle of Departure
• AoA Angle of Arrival
• the RAN device may need to proactively acquire the target device positioning capabilities.
• the target device positioning capabilities are received from the core network and/or from the target device.
• target device positioning capabilities are received from the core network, these may be in an embodiment be indicated by core net work to the RAN device, e.g. as part of RCPA1, possibly before the RAN device places any positioning related requests, such as requests for the positioning capabilities, to the core network. In another embodiment, the RAN device asks for this infor mation.
• the target device positioning capabilities may be known to the core assum ing that information on target device capabilities is stored as part of subscription information in the core (possibly in a unified data management (UDM) entity) and is obtained and sent to the RAN device e.g. during target device registration or con text setup/modification.
• the target device may send positioning capabilities in a non-access stratum (NAS) message to the AMF e.g.
• NAS non-access stratum
• the core network e.g. AMF, UDM, UDR (unified data repository)
• the core network may store it as part of the target device context, and then provide the same to the RAN device.
• AMF e.g. AMF, UDM, UDR (unified data repository)
• UDM unified data repository
• the target device positioning capabilities are received from the target device.
• the target device may send posi tioning capabilities as part of Access Network (AN) parameters in a registration request to the RAN, which stores it as part of UE context.
• the target device may provide its positioning capabilities in a radio resource control (RRC) message to RAN, possibly based on RRC request from the RAN (e.g. from the gNB).
• RRC radio resource control
• the RAN device may provide an indication of the ex istence of location information of the target device to the target device.
• the target device may be notified by the RAN node via RRC that the RCP session is activated.
• deactivation of the proactive location determination may be indi cated to the target device by the RAN device, upon the RAN device triggering deac tivation of the RCP.
• the target device may re quest its own position (e.g. via RRC) directly from the RAN device (e.g. from LMC), instead of the core. This may reduce signaling and latency since core’s AMF is not involved, as would be the case for MO-LR.
• the RAN device may provide location information of the target device to the target device.
• some benefits of the proposal may include reduced time-to-first-fix, possibly to a few milliseconds, and reduced latency for subsequent location requests due to elimination of core net work (AMF) in communication path.
• One benefit may also comprise that the RAN node is continuously aware of the location of the target device, which also helps in reducing latencies.
• the proactive deter mination of the target device’s location provides for reduced latencies and signal ing whenever a location request (also known as location service request) is re ceived by the RAN node or a need for providing target devices location is deter mined by the RAN node, as the location may be provided to the requesting entity substantially immediately, without negotiation with the core network.
• the benefits may realize even in case of a single location request, as well as for continuous po sitioning indication.
• some software applications run at the target device may benefit or even require constant or frequent and/or periodical location indication.
• Being able to provide such frequent location indication to the target device directly from the RAN instead of the core may reduce latencies and signaling overhead.
• Figure 4 show a signaling flow example for proactive location determi nation (e.g. RCP) activation based on e.g. RCPAI during initial access.
• the entities performing the signaling flow diagram may be the target device (such as the UE 120), the RAN (such as the gNB 110 or LMC of RAN) and the core network (such as AMF of the core network).
• an RRC connection setup is established. This may be done e.g. by means of random access (RA) procedure.
• Step 402 carries an UE message which may comprise a first uplink NAS message (e.g. Service Request) to trigger context setup to the AMF.
• Step 404 depicts an initial context setup re quest, enhanced with one or more of the following carried in the RCPAI embedded in the context setup request:
• AMF may obtain the "UE authorized for RCP" from UDM and store it in UE location context.
• the lo cation service QoS requirement are stored in UDM, after receiv ing from the target device.
• the UE sends the location service QoS requirement in a NAS message to AMF.
• the location service QoS requirement are stored in UDM, after receiving from the target device.
• the UE sends the location service QoS requirement in a NAS message to AMF.
• the UE sends the location service QoS requirement in a NAS message to AMF.
• the RAN node decides whether to use RCP or not.
• the RAN node may evaluate if any of the positioning methods (e.g. UE assistance and/or neighboring RAN node assistance) available is capable to provide the location estimation meeting the requirements received in the RCPA1, according to the current resource availability.
• the positioning methods e.g. UE assistance and/or neighboring RAN node assistance
• the RAN node may initiate positioning procedures for the target UE.
• the RAN node may additionally send a measurement configuration and/or an RCP usage indication, possibly to gether with location service QoS to the UE in an RRC Connection Reconfiguration message.
• the RAN node may, for downlink positioning, trigger loca tion procedures with the UE.
• Steps 410 depicts an RRC Reconfiguration Complete message from the UE to the RAN node.
• Step 412 shows that the RAN node indicates to the AMF in the Context Setup Response if RCP is used by RAN node.
• the location request may be responded substantially immediately reducing latencies.
• Step 500 of Figure 5 depicts RRC reconfiguration message without the RCP indication. This is because RCP has not yet been triggered by the RAN node. Also, the RAN node may in step 502 send a context setup response to the core network without RCP indication. Only after these, the RAN node may trigger RCP based on a local trigger (e.g. event based), for example, in step 406 of Figure 5. This is fol lowed by steps 408 and 410, as was the case for Figure 4. In step 504 of Figure 5, the RAN device sends location management information to the core network, wherein the information includes the RCP indication indicating that RCP has been triggered for this particular UE.
• a local trigger e.g. event based
• the proactive location determination may also be applied in connection of handovers, or in connection of Conditional Handover.
• This may include the RAN device acting as a source node of the handover and detecting that a handover is needed.
• the source node may send information to at least one candidate target node, the information indicating that location determination may be applied for the target device that is to be handed over to the target node.
• This information may comprise the RCPAI, or parts of it.
• the information may be sent in a handover request message, for example.
• the target node where the UE is handed over can then determine whether to start the proactive location determi nation for the UE. This may be based on local triggers, preconfigured rules, etc.
• the RAN device is comprised in the target node providing the target cell of the handover, and receive in connection of handover preparation information from a source node, the infor mation indicating that location determination may be applied for the target device that is to be handed over to the target node.
• the RAN device in the target node of the handover may then decide whether to start the proactive location determina tion for the UE. This may be based on local triggers, preconfigured rules, etc.
• Figure 6 shows a method from the point of view of the target device, such as the UE 120 or any other terminal device (sensor devices, etc.).
• the UE 120 may receive an indication from the RAN device (such as the gNB 110 or LMC) device that location information of the UE is available in the RAN device. This may take place before the UE 120 has any need for or has sent any location service requests.
• the UE may decide to request location information from the RAN device. Such decision may be due to an application in the UE requesting loca tion data, for example. This may be possible because the UE has knowledge that the RAN device has determined the location of the UE.
• the UE need not ask the location from the core network, as the UE has knowledge that the RAN device has this in formation. This may reduce latencies and signaling.
• the UE may receive the location information from the RAN device.
• the UE may determine location of the UE at least partially based on the received location information. This may be useful in e.g. indoor scenarios where the use of GPS may be impossible.
• Figure 7 shows a method from the point of view of the core network device, such as the AMF or LMF.
• the method may comprise, in step 700, receiving, from the target device (such as UE 120), information related to positioning of the target device. This information may be e.g. positioning capabilities of the target de vice, target device subscription information, application type applied by the target device, location profile indicator for the target device, for example.
• the method may comprise providing, before receiving a positioning related request (e.g. from the RAN device), at least part of the information to a radio access network device responsible of triggering a location determination of the target device.
• a positioning related request e.g. from the RAN device
• Such proactive provisioning of the RCPA1 may reduce latencies and enable the RAN de vice to decide on activation of RCP and to locate the target device more efficiently.
• An embodiment as shown in Figure 8, provides an apparatus 10 com prising a control circuitry (CTRL) 12, such as at least one processor, and at least one memory 14 including a computer program code (PROG), wherein the at least one memory and the computer program code (PROG), are configured, with the at least one processor, to cause the apparatus to carry out any one of the above-de scribed processes.
• CTRL control circuitry
• PROG computer program code
• the memory may be implemented using any suitable data stor age technology, such as semiconductor based memory devices, flash memory, mag netic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
• the apparatus 10 may be or be comprised in a net work node, such as in gNB/gNB-CU/gNB-DU of 5G.
• the appa ratus 10 is or is comprised in the network node 110.
• the appa ratus 10 is or is comprised in LMC.
• the apparatus 10 is or is comprised in ng-eNB.
• the apparatus 10 may be or be comprised in a WLAN access point. The apparatus may be caused to execute the functionalities of some of the above described processes, such as the steps of Figures 3, 4 and 5.
• NFV network func tions virtualization
• a virtualized net work function may comprise one or more virtual machines running com puter program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
• this may mean node operations to be carried out, at least partly, in a cen tral/centralized unit, CU, (e.g. server, host or node) operationally coupled to dis tributed unit, DU, (e.g. a radio head/node). It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may vary depending on implementation.
• the proactive location determination may also be ap plied in connection of RRC state transition between high activity states (e.g. RECONNECTED) and low activity states (RRCJNACTIVE, RRCJDLE).
• this may include the RAN device detecting low user plane activity and config uring the UE with the RRC state transition to RRCJNACTIVE.
• the proactive location determination can be done before the UE is configured with RRC_ INACTIVE state and connection is suspended, or before transitioning the connection CM-CON- NECTED to CM-IDLE (Connection Management) and releasing the RRC connection to RRCJDLE.
• the server may generate a virtual network through which the server communicates with the radio node.
• virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
• Such virtual network may provide flexible distribution of operations be tween the server and the radio head/node.
• any digital signal processing task may be performed in either the CU or the DU and the boundary where the re sponsibility is shifted between the CU and the DU may be selected according to im plementation.
• a CU-DU architecture is implemented.
• the apparatus 10 may be comprised in a central unit (e.g. a control unit, an edge cloud server, a server) operatively coupled (e.g. via a wireless or wired network) to a distributed unit (e.g. a remote radio head/node).
• the central unit e.g. an edge cloud server
• the radio node may be stand-alone apparatuses communicating with each other via a radio path or via a wired connection. Alter natively, they may be in a same entity communicating via a wired connection, etc.
• the edge cloud or edge cloud server may serve a plurality of radio nodes or a radio access networks.
• at least some of the described processes may be performed by the central unit.
• the apparatus 50 may be instead comprised in the distributed unit, and at least some of the described pro Waits may be performed by the distributed unit.
• the execution of at least some of the functionalities of the apparatus 10 may be shared between two physically separate devices (DU and CU) forming one operational entity. Therefore, the apparatus may be seen to depict the operational entity comprising one or more physically separate devices for executing at least some of the described processes.
• CU- DU architecture may provide flexible distribution of operations between the CU and the DU.
• any digital signal processing task may be performed in ei ther the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation.
• the apparatus 10 controls the execution of the processes, regardless of the location of the apparatus and regardless of where the processes/functions are car ried out.
• the apparatus may further comprise communication interface (TRX) 16 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
• TRX may provide the ap paratus with communication capabilities to access the core network, the UEs or some other devices of the radio access network, for example.
• the apparatus may also comprise a user interface 18 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc.
• the user interface may be used to control the apparatus by the user.
• the control circuitry 12 may comprise a positioning triggering circuitry 20 for deciding whether to trigger the proactive location determination, according to any of the embodiments.
• the control circuitry 12 may further comprise a loca tion determination circuitry 22 for determining the location of the target device, according to any of the embodiments.
• An embodiment as shown in Figure 9, provides an apparatus 50 com prising a control circuitry (CTRL) 52, such as at least one processor, and at least one memory 54 including a computer program code (PROG), wherein the at least one memory and the computer program code (PROG), are configured, with the at least one processor, to cause the apparatus to carry out any one of the above-de scribed processes.
• CTRL control circuitry
• PROG computer program code
• the memory may be implemented using any suitable data stor age technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
• the apparatus 50 may comprise the terminal device of a communication system, e.g. a user terminal (UT), a computer (PC), a laptop, a tabloid computer, a cellular phone, a mobile phone, a communicator, a smart phone, a palm computer, sensors, moving robots, a mobile transportation appa ratus (such as a car), a household appliance, or any other communication appa ratus, commonly called as UE or target device in the description.
• the apparatus is comprised in such a terminal device.
• the apparatus may be or comprise a module (to be attached to the UE) providing connectivity, such as a plug-in unit, an "USB dongle", or any other kind of unit.
• the unit may be installed either inside the UE or attached to the UE with a connector or even wirelessly.
• the apparatus 50 is or is comprised in the UE 120.
• the apparatus may be caused to execute the functionalities of some of the above described processes, such as the steps of Figure 4, 5 and 6.
• the apparatus may further comprise communication interface (TRX) 56 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
• TRX may provide the ap paratus with communication capabilities to access the radio access network, for example.
• the apparatus may also comprise a user interface 58 comprising, for ex ample, at least one keypad, a microphone, a touch display, a display, a speaker, etc.
• the user interface may be used to control the apparatus by the user.
• the control circuitry 52 may comprise a connection establishment cir cuitry 60 for establishing connection to the RAN, according to any of the embodi ments.
• the control circuitry 52 may further comprise a location determination cir cuitry 62 for determining the location of the target device (e.g. by asking from the RAN node), according to any of the embodiments.
• An embodiment as shown in Figure 10, provides an apparatus 80 com prising a control circuitry (CTRL) 82, such as at least one processor, and at least one memory 84 including a computer program code (PROG), wherein the at least one memory and the computer program code (PROG), are configured, with the at least one processor, to cause the apparatus to carry out any one of the above-de scribed processes.
• CTRL control circuitry
• PROG computer program code
• the memory may be implemented using any suitable data stor age technology, such as semiconductor-based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
• the apparatus 80 may comprise a core network de vice of a communication system, e.g. the AMF or LMF of the core.
• the apparatus 80 is or is comprised in the AMF.
• the apparatus may be caused to execute the functionalities of some of the above described processes, such as the steps of Figure 4, 5 and 7.
• the apparatus may further comprise communication interface (TRX) 86 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
• TRX may provide the ap paratus with communication capabilities to access the radio access network or other devices of the core network, for example.
• the apparatus may also comprise a user interface 88 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc. The user interface may be used to control the apparatus by the user.
• the control circuitry 82 may comprise a connection establishment cir cuitry 90 for establishing connection to the RAN and/or to the terminal device, ac cording to any of the embodiments.
• the control circuitry 82 may further comprise a positioning assistance circuitry 92 for assisting in a target device positioning, such as provisioning of the RCPAI to the RAN device, according to any of the em bodiments.
• the RCPAI may be stored in the memory 84, for example, or in some other core network entity with which the apparatus 80 has connection to.
• an apparatus carrying out at least some of the em bodiments described comprises at least one processor and at least one memory including a computer program code, wherein the at least one memory and the com puter program code are configured, with the at least one processor, to cause the apparatus to carry out the functionalities according to any one of the embodiments described.
• the computer program code when the at least one processor executes the computer program code, the computer program code causes the apparatus to carry out the functionalities according to any one of the embodiments described.
• the apparatus carrying out at least some of the embod iments comprises the at least one processor and at least one memory including a computer program code, wherein the at least one processor and the computer pro gram code perform at least some of the functionalities according to any one of the embodiments described.
• the at least one processor, the memory, and the computer program code form processing means for carrying out at least some of the embodiments described.
• the appa ratus carrying out at least some of the embodiments comprises a circuitry includ ing at least one processor and at least one memory including computer program code. When activated, the circuitry causes the apparatus to perform the at least some of the functionalities according to any one of the embodiments described.
• circuitry refers to all of the follow ing: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and software (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a micropro- cessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
• circuitry' applies to all uses of this term in this application.
• the term 'circuitry' would also cover an implementation of merely a processor (or mul tiple processors) or a portion of a processor and its (or their) accompanying soft ware and/or firmware.
• the term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
• At least some of the processes described may be car ried out by an apparatus comprising corresponding means for carrying out at least some of the described processes.
• Some example means for carrying out the pro Listes may include at least one of the following: detector, processor (including dual-core and multiple-core processors), digital signal processor, controller, re DCver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, dis play, user interface, display circuitry, user interface circuitry, user interface soft ware, display software, circuit, antenna, antenna circuitry, and circuitry.
• the appa ratus (es) of embodiments may be implemented within one or more application- specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programma ble gate arrays (FPGAs), processors, controllers, micro-controllers, microproces sors, other electronic units designed to perform the functions described herein, or a combination thereof.
• ASICs application- specific integrated circuits
• DSPs digital signal processors
• DSPDs digital signal processing devices
• PLDs programmable logic devices
• FPGAs field programma ble gate arrays
• processors controllers, micro-controllers, microproces sors, other electronic units designed to perform the functions described herein, or a combination thereof.
• firmware or software the implementation can be car ried out through modules of at least one chip set (e.g.
• the software codes may be stored in a memory unit and executed by processors.
• the memory unit may be imple mented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art.
• the components of the systems described herein may be rear ranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.
• Embodiments as described may also be carried out in the form of a computer process defined by a computer program or portions thereof. Embodi ments of the methods described may be carried out by executing at least one por tion of a computer program comprising corresponding instructions.
• the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
• the computer program may be stored on a computer program distribution medium readable by a computer or a processor.
• the computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
• the computer program medium may be a non-transitory medium. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.
• an apparatus comprising: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are config ured, with the at least one processor, to cause a radio access network device to perform operations comprising: decide that a location of a target device is to be determined; determine location of the target device; after having determined the location of the target device, receive a location request; respond to the location re quest with location information of the target device.
• deciding is based on information associated with at least one of the following: target device registration, target de vice context setup, target device context modification.
• deciding is based on information associated with at least one of the following: bearer context setup for the target de vice, bearer context modification for the target device.
• the information indicates at least one of the following: target device type, target device subscription information, appli cation type applied by the target device, location profile indica tor. • wherein the information indicates at least one of the following: target device type, target device subscription information, appli cation type applied by the target device, location profile indica tor.
• the information indicates at least one of the following: target device type, target device subscription information, appli cation type applied by the target device, location profile indica tor.
• determining the location is based on predefined attrib utes or based on attributes indicated from core network as part of at least one of the following: target device registration, target device context setup, target device context modification, bearer context setup for the target device, bearer context modification for the target device.
• determining the location is at least partially based on target device positioning capabilities, wherein the target device positioning capabilities are received from a core network or from the target device.
• radio access network device is a gNB, a ng-eNB or a location management component, LMC, within the radio access network.
• an apparatus comprising means for performing: deciding that a location of a target device is to be determined; determining location of the target device; after having determined the location of the target device, receiving a location request; responding to the loca tion request with location information of the target device.
• Various embodiments of the second example may comprise at least one feature from the bulleted list un der the first example.
• a method comprising: deciding that a location of a target device is to be determined; determining location of the target device; after having determined the location of the target device, re ceiving a location request; responding to the location request with location infor mation of the target device.
• Various embodiments of the third example may com prise at least one feature from the bulleted list under the first example.
• a computer program product embodied on a distribution medium readable by a computer and comprising program instructions which, when loaded into an apparatus, execute a method according the third example.
• Various embodiments of the third example may com prise at least one feature from the bulleted list under the first example.
• an apparatus comprising: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are config ured, with the at least one processor, to cause a terminal device to perform opera tions comprising: receive an indication from a radio access network device that lo cation information of the terminal device is available in the radio access network device; request the location information from the radio access network device; re ceive the location information from the radio access network device; determine lo cation of the terminal device at least partially based on the received location infor mation.
• an apparatus for a ter minal device comprising means for performing: receiving an indica tion from a radio access network device that location information of the terminal device is available in the radio access network device; requesting the location in formation from the radio access network device; receiving the location information from the radio access network device; determining location of the terminal device at least partially based on the received location information.
• a method performed by a terminal device comprising: receiving an indication from a radio access network device that location information of the terminal device is available in the radio access network device; requesting the location information from the radio access network device; receiving the location information from the radio ac cess network device; determining location of the terminal device at least partially based on the received location information.
• a computer program product embodied on a distribution medium readable by a computer and comprising program instructions which, when loaded into an apparatus, execute a method according to the seventh example.
• an apparatus comprising: at least one processor and at least one memory including a computer program code, wherein the at least one memory and the computer program code are config ured, with the at least one processor, to cause a core network device to perform operations comprising: receive, from a target device, information related to posi tioning of the target device; provide, before receiving a positioning related request, at least part of the information to a radio access network device responsible of trig gering a location determination of the target device.
• an apparatus for a core network device comprising means for performing: receiving, from a target device, information related to positioning of the target device; providing, be fore receiving a positioning related request, at least part of the information to a radio access network device responsible of triggering a location determination of the target device.
• a method per formed by a core network device comprising: receiving, from a target device, information related to positioning of the target device; providing, before receiving a positioning related request, at least part of the information to a radio access network device responsible of triggering a location determination of the tar get device.
• a computer program product embodied on a distribution medium readable by a computer and comprising program instructions which, when loaded into an apparatus, execute a method according the eleventh example.
• a computer system comprising: one or more processors; at least one data storage, and one or more computer program instructions to be executed by the one or more processors in association with the at least one data storage for carrying out a method according to any of third, seventh or eleventh example.

Applications Claiming Priority (2)

Publications (2)

Family

ID=74660042

Family Applications (1)

Country Status (2)

Families Citing this family (3)

Family Cites Families (2)

• 2020
  • 2020-06-25 WO PCT/FI2020/050454 patent/WO2021032907A1/en unknown
  • 2020-06-25 EP EP20855768.6A patent/EP4018690A4/de active Pending

Also Published As

Similar Documents

Legal Events