Method for enabling a first wireless device to determine relative positions between a plurality of second wireless devices, associated wireless devices, and associated network nodes

Abstract

A method is disclosed for enabling a first wireless device to determine a relative position between a plurality of second wireless devices based on a positioning capability of a core network, the method being implemented by a service API control node. The method includes receiving, from the first wireless device, via an established data connection, an authorization request message for using a service API. The method includes authorizing the first wireless device to use a service API for positioning of the wireless device. The method includes receiving, from the first wireless device, a message including information identifying a plurality of second wireless devices using the service API for positioning of the wireless device. The method includes authorizing the first wireless device to determine a relative position of the plurality of second wireless devices. The method includes performing a positioning procedure for determining a relative position of the plurality of second wireless devices based on the positioning capability and the message identifying the plurality of second wireless devices.

Description

[Technical Field]

[0001] The present disclosure relates to the field of wireless communications. The present disclosure relates to a method for enabling a first wireless device to determine relative positions between a plurality of second wireless devices, associated wireless devices, and associated network nodes, such as core network nodes. [Background technology]

[0002] 3rd Generation Partnership Project (3GPP®): rd The Universal Mobile Communications Generation Partnership Project (UMP) is working on positioning services, such as location-based services for wireless devices. Positioning of a wireless device can be used to provide various services to a first wireless device when the first wireless device is in a particular location, such as in the vicinity of a second wireless device.

[0003] Typically, location-based services for wireless devices are based on interactions between the wireless device and a Location Management Function (LMF) using a positioning protocol such as the LTE Positioning Protocol (LPP) via control plane signaling. A first wireless device and a second wireless device may also use sidelink positioning to determine whether they are in proximity to each other. Sidelink positioning can also be used to determine the relative distance between the first wireless device and the second wireless device.

[0004] Some services may require a third wireless device, which may be out of range of sidelink communication with the first wireless device and the second wireless device, to know the relative position between the first wireless device and the second wireless device. Summary of the Invention [Problem to be solved by the invention]

[0005] Therefore, what is needed is a device and method for enabling a wireless device to access a core network's service Application Programming Interface (API), which may mitigate, alleviate, or address existing shortcomings, providing a wireless device with access to the location, such as the relative location, of one or more other wireless devices, while reducing traffic in the control plane. [Means for solving the problem]

[0006] A method is disclosed for enabling a first wireless device to determine relative positions among multiple second wireless devices based on a positioning function of a core network, the method being implemented by a service application programming interface (API) control node. The method includes receiving, from the first wireless device via an established data connection, an authorization request message to use a service API. The authorization request message includes access information that authorizes the first wireless device to use the service API for positioning of the wireless device. The method includes authorizing the first wireless device to use the service API for positioning of the wireless device using a data management function and based on the access information. The method includes receiving, from the first wireless device, a message including information identifying multiple second wireless devices using the service API for positioning of the wireless device, the message requesting determination of relative positions of the multiple second wireless devices. The method includes authorizing the first wireless device to determine the relative positions of the multiple second wireless devices using the data management function and the message including information identifying the multiple second wireless devices. The method includes, when the first wireless device is authorized to determine the relative positions of the plurality of second wireless devices, performing a positioning procedure to determine the relative positions of the plurality of second wireless devices based on a positioning capability and a message identifying the plurality of second wireless devices, and transmitting the relative positions of the plurality of second wireless devices to the first wireless device using a service API for positioning of the wireless device.

[0007] Further provided is a service API control node comprising a memory circuit, a processor circuit, and an interface, the service API control node configured to perform any of the methods according to the present disclosure.

[0008] An advantage of the present disclosure is that a service API control node can authenticate and establish secure communication with a wireless device via a second interface, such as via an established data connection. This allows the wireless device to securely access a service API via the service API control node and obtain positioning information of one or more second wireless devices via the service API over the data connection instead of via the control plane. This reduces traffic and avoids control channel congestion. Furthermore, providing the wireless device with the access information necessary to access the service API enables the wireless device to use the service API to remotely access the locations of one or more second wireless devices, such as when the wireless device is not within sidelink range of the one or more second wireless devices. The use of the service API further enables the wireless device to remotely access the locations of one or more second wireless devices when the wireless device is located in a different PLMN, such as a different country, from the one or more second wireless devices. A further advantage is that a network control method can be provided that allows a wireless device to reuse service APIs designed for use with application functions, instead of relying on signaling messaging via the control plane.

[0009] A method is disclosed for enabling a first wireless device to determine a relative position between a plurality of second wireless devices, the method being implemented by a network node implementing a data management function. The method includes receiving a verification request message from a service API control node to verify whether the first wireless device is authorized to use a service API for wireless device positioning. The verification request message includes access information for accessing the service API for wireless device positioning. The method includes verifying whether the wireless device is authorized to use the service API for wireless device positioning based on the access information and one or more rules and / or subscription data. The method includes sending an authorization verification acceptance message to the service API control node if the first wireless device is authorized to use the service API for wireless device positioning. The authorization verification acceptance message includes dedicated information necessary to use the service API for wireless device positioning.

[0010] Further provided is a network node implementing a data management function, comprising a memory circuit, a processor circuit, and an interface, the network node implementing a data management function configured to perform any of the methods according to the present disclosure.

[0011] An advantage of the present disclosure is that a network node implementing a data management function can verify that a wireless device attempting to access a service API is the wireless device it claims to be and is authorized to use the service API. This may prevent unauthorized wireless devices from using the service API, thereby reducing traffic over the service API. A further advantage is that a network control method can be provided that allows wireless devices to reuse service APIs designed for use with application functions instead of relying on signaling messaging over the control plane.

[0012] A method is disclosed for determining relative positions between multiple second wireless devices based on a positioning function of a core network, the method being implemented by a first wireless device. The method includes transmitting an authorization request message to a service API control node of the core network via an established data connection to use a service API for wireless device positioning. The authorization request message includes access information for authenticating the first wireless device to use the service API for wireless device positioning. Upon receiving an authorization acceptance message to use the service API for wireless device positioning, the method includes transmitting a message identifying the multiple second wireless devices to the service API control node that uses the service API for wireless device positioning. The message triggers determination of relative positions of the multiple second wireless devices. The method includes receiving the relative positions of the multiple second wireless devices using the service API for wireless device positioning when the service API control node authorizes the first wireless device to access the relative positions of the multiple second wireless devices.

[0013] Further provided is a wireless device comprising a memory circuit, a processor circuit, and a wireless interface, the wireless device configured to perform any of the methods according to the present disclosure with respect to the first wireless device.

[0014] An advantage of the present disclosure is that a first wireless device can obtain access information necessary to access a service API over a data connection using control plane signaling. By providing control information over the control plane, the first wireless device may be authorized by the core network to use the service API and may receive the access information necessary to access the service API. This allows the wireless device to use the service API over a data connection to access services, such as positioning services, instead of over the control plane. This can reduce traffic and avoid control channel congestion. Furthermore, the use of the service API allows the wireless device to remotely access the location of one or more second wireless devices, such as when the wireless device is not within sidelink range of the one or more second wireless devices. The use of the service API further allows the wireless device to remotely access the location of one or more second wireless devices when the wireless device is located in a different Public Land Mobile Network (PLMN), for example, in a different country than the one or more second wireless devices. Additionally, it would be advantageous to provide a network control method that allows wireless devices to reuse service APIs designed for use with application functionality instead of consolidating signaling messaging over the control plane.

[0015] A method is disclosed that is implemented by a network node that implements a core network positioning function and that enables a first wireless device to determine a relative position between multiple second wireless devices. The method includes receiving a request to determine the relative positions of the multiple second wireless devices from a service API control node. The request includes information identifying the multiple second wireless devices. The method includes performing a positioning procedure to determine the relative positions between the multiple second wireless devices. The method includes transmitting a positioning result message to the service API control node that includes the relative positions of the multiple second wireless devices.

[0016] Further provided is a network node implementing a core network positioning function, comprising a memory circuit, a processor circuit, and an interface, the network node implementing a positioning function configured to perform any of the methods according to the present disclosure.

[0017] An advantage of the present disclosure is that a network node implementing a positioning function can be instructed to provide, and can provide, measurement results to a first wireless device via a service API control node and a service API. This allows the wireless device to access the positioning service over a data connection instead of over the control plane, thereby reducing traffic and avoiding control channel congestion. A further advantage is that a network control method can be provided that allows the wireless device to reuse service APIs designed for use by application functions instead of relying on signaling messaging over the control plane.

[0018] These and other features and advantages of the present disclosure will become readily apparent to those skilled in the art from the following detailed description of examples thereof, taken in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0019] [Figure 1]FIG. 1 illustrates an example wireless communication system including example network nodes and example wireless devices according to the present disclosure. [Figure 2] FIG. 2 is a signaling diagram illustrating an example message exchange according to the present disclosure for a first wireless device to register and obtain authorization to use a service API for positioning of multiple second wireless devices. [Figure 3] FIG. 3 is a flowchart illustrating an example method implemented in a first wireless device for accessing a service API and / or for determining relative positions between multiple second wireless devices based on positioning capabilities of a core network, in accordance with the present disclosure. [Figure 4] FIG. 4 is a flowchart illustrating an example method implemented in a first core network node of a wireless communication system for enabling a wireless device to access a core network service API, in accordance with the present disclosure. [Figure 5] FIG. 5 is a flowchart illustrating an example method implemented in a second core network node of a wireless communication system for enabling a wireless device to access a service API of a core network, in accordance with the present disclosure. [Figure 6A] FIG. 6A is a flowchart illustrating an example method implemented in a third core network node of a wireless communication system for enabling a wireless device to access a core network service API, in accordance with the present disclosure. [Figure 6B] FIG. 6B is a flowchart illustrating an example method implemented in a third core network node of a wireless communication system for enabling a wireless device to access a core network service API, in accordance with the present disclosure. [Figure 7] FIG. 7 is a flowchart illustrating an example method implemented in a fourth core network node of a wireless communication system for enabling a wireless device to access a core network service API in accordance with the present disclosure. [Figure 8]FIG. 8 is a block diagram illustrating an example wireless device according to the present disclosure. [Figure 9] FIG. 9 is a block diagram illustrating an example first core network node according to the present disclosure. [Figure 10] FIG. 10 is a block diagram illustrating an example second core network node according to the present disclosure. [Figure 11] FIG. 11 is a block diagram illustrating an example third core network node according to the present disclosure. [Figure 12] FIG. 12 is a block diagram illustrating an example fourth core network node according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0020] Various examples and details are described below with reference to the drawings, where relevant. It should be noted that the drawings may or may not be drawn to scale, and that elements of similar structure or function are represented by similar reference numerals throughout the drawings. It should also be noted that the drawings are intended only to facilitate the description of the examples. They are not intended as an exhaustive description of the present disclosure or as limitations on the scope of the present disclosure. Moreover, the illustrated example need not have all the illustrated aspects or advantages. An aspect or advantage described in connection with a particular example is not necessarily limited to that example and can be practiced in any other example, even if not so shown or explicitly described.

[0021] The drawings are schematic and simplified for clarity, and merely show details that aid in understanding the present disclosure, while other details are omitted. The same reference numerals are used throughout to refer to the same or corresponding parts.

[0022] FIG. 1 illustrates an exemplary wireless communication system 1 including exemplary core network nodes 600, 600A, 600B, 600C, and 600D, an exemplary radio network node 400, an exemplary first wireless device 300, and exemplary second wireless devices 300A and 300B according to the present disclosure.

[0023] As described in detail herein, the present disclosure relates to a wireless communication system 1, which may comprise a cellular system such as a 3GPP wireless communication system. The wireless communication system 1 comprises a wireless device 300 and / or a radio network node 400.

[0024] A radio network node as disclosed herein refers to a radio access network node operating in a radio access network, such as a base station in NR, an evolved Node B, an eNB, a gNB, etc. In one or more examples, a RAN node is a functional unit that may be distributed across several physical units.

[0025] A core network (CN) node disclosed herein refers to a network node operating in a core network, such as an Evolved Packet Core Network (EPC) and / or a 5G Core Network (5GC). An example of a CN node in an EPC includes a Mobility Management Entity (MME). A core network node may be configured to implement one or more functions, such as core network functions. The functions may be one or more of an access and mobility management function 600A, a data management function 600B, a network exposure function (NEF) 600C, and a positioning function 600D. A function is a functional unit that may be implemented in one or more physical units, such as one or more physical core network nodes.

[0026] In one or more examples, a RAN node is a functional unit that may be distributed across several physical units.

[0027] The wireless communication system 1 described in this specification may include one or more wireless devices, such as a first wireless device 300 and one or more second wireless devices 300A / 300B, and / or one or more network nodes 400, such as one or more base stations, eNBs, gNBs, and / or access points.

[0028] A wireless device herein may refer to a mobile device and / or user equipment (UE).

[0029] The first wireless device 300 may be configured to communicate with the network node 400 via a first wireless link (or wireless access link) 10. The second wireless device 300A may be configured to communicate with the network node 400 via a second wireless link (or wireless access link) 10A.

[0030] The wireless network node 400 may be configured to communicate with the CN node 600 via a wired or wireless link 12 .

[0031] The wireless devices 300, 300A may be configured to communicate with each other directly via the sidelink 20, for example without communicating via the radio network node 400. The sidelink 20 may be a wireless link.

[0032] Typically, location-based services for wireless devices are based on interactions between the wireless device and a positioning function, such as an LMF, in the core network that uses a positioning protocol, such as LPP, over the control plane. A wireless device that needs a positioning estimate of another wireless device or the relative distance between two other wireless devices may use this protocol to request the positioning estimate of another wireless device or the relative distance between two other wireless devices. The procedure for estimating the relative distance between two wireless devices is sometimes referred to herein as ranging. However, using LPP over the control plane increases traffic over the control plane and can cause congestion on the control plane.

[0033] Instead of using LPP via the control plane, this disclosure provides a solution whereby a wireless device requesting relative positioning of two other wireless devices can access functionality such as positioning functions in the core network using a service API such as a northbound API via the NEF. The northbound interface is an interface that allows network functions to communicate with higher-level components such as application functions. The NEF allows service providers to process data coming from application functions (AFs) in a secure manner with correct allocation and utilization of resources. The NEF API is traditionally used only by third-party AFs or network functions (NFs).

[0034] 2 is a signaling diagram illustrating an example message exchange 1000 between a first wireless device 300, a first core network node 600A, a second core network node 600B, a third core network node 600C, a fourth core network node 600D, a primary second wireless device 300A, and a secondary second wireless device 300B to enable the first wireless device 300 to determine a relative position among a plurality of second wireless devices based on a positioning capability of the core network, in accordance with one or more example methods disclosed herein. In one or more example methods herein, the first core network node 600A is a core network node that implements an access and mobility management function (AMF). In one or more example methods herein, the second core network node 600B is a core network node implementing one or more of an Authentication Server Function (AUSF), a Policy Control Function (PCF), a 5G Direct Discovery Name Management Function (DDNMF), and a Unified Data Management (UDM) function. In one or more example methods herein, the third core network node 600C is a core network node that controls service APIs, such as a core network node implementing one or more of a Network Exposure Function (NEF) and a Common API Framework (CAPIF) function. In one or more example methods herein, the fourth core network node 600D is a core network node that implements a positioning function, such as a Location Management Function (LMF).

[0035] In one or more example methods disclosed herein, a first wireless device 300 acquires access information, such as a certificate (CERT), to use a service API. The wireless device 300 transmits control information 1001 to a first core network node via a first interface, such as via a control plane. The control information includes one or more of an identifier that identifies the wireless device and information identifying a service API that the wireless device is attempting to access. The first wireless device may, in one or more example methods, transmit a registration request message including the control information and may include an indication of a desire and / or intent to access a service API / exposure API for positioning, such as ranging and sidelink positioning. In one or more example methods, the indication of a desire and / or intent to access a service API may be signaled as a capability exchange, such as a UE capability exchange indicating that the first wireless device can use the service API and / or ranging or positioning services, or may be a more explicit indication that the first wireless device desires to use the service API.

[0036] The first core network node 600A verifies, based on the control information, that the first wireless device 300 is authorized to use the service API. The verification may be performed by the first wireless device 600A sending authentication information 1002, such as an identifier that identifies the wireless device, to the second core network node. The second core network node may verify, for example, based on the subscription information, that the first wireless device is authorized to use the service API, such as that the first wireless device is authorized to use an exposure API to access the service API. Once the second core network node verifies that the first wireless device is authorized to use the service API, the second core network node provides, to the first core network node, access information 1003, such as onboarding enrollment information and / or certificates, necessary to access the service API, such as by accessing a service API control node, via a second interface, such as via the established data connection.

[0037] The first core network node 600A provides access information 1004, such as onboarding enrollment information and / or credentials, to the first wireless device 300, such as in a registration accept message. The first wireless device 300 can use this access information to obtain authorization to use the service API.

[0038] In one or more example methods, the first wireless device 300 performs a service API onboarding procedure with a third core network node, such as a service API control node, based on the onboarding information and / or the CERT received from the first core network node 300A to set up a secure connection with the third core network node 600C via the second interface. In one or more example methods, the first wireless device 300 transmits an onboarding request message 1005 including the onboarding enrollment information and / or the CERT to the third core network node 600C.

[0039] Based on the onboarding enrollment information and / or the CERT, the third core network node 600C performs an onboarding procedure for the first wireless device by verifying 1006 the onboarding enrollment information and / or the CERT. Verifying the onboarding enrollment information may include verifying enrollment credentials, such as an access token, of the first wireless device. Performing the onboarding procedure 1006 may further include generating a profile for use by the first wireless device to access service APIs, for example, an API caller profile as specified in 3GPP TS23.222 v.17.5.0.

[0040] The third core network node 600C provides an onboarding response message 1007 to the first wireless device that includes information from the generated profile of the wireless device.

[0041] In one or more exemplary methods, the first wireless device 300 is registered to obtain authorization to use a service API, such as a service API for positioning and / or ranging services, based on the enrollment information. The first wireless device 300 may send an authorization request message 1008 to the third core network node 600C. The authorization request message 1008 may include authentication information for authenticating the first wireless device 300, such as a Mobile Station International Subscriber Directory Number (MSISDN) and / or a provided CERT, and / or information from a profile, such as an API caller profile, provided in the onboarding response message. In one or more exemplary methods, authorization may be performed in two steps, such as in accordance with 3GPP TS23.222 v.17.5.0, sections 8.10 and 8.11. The MSISDN may be used to identify a subscription in a Global System for Mobile communications or Universal Mobile Telecommunications System mobile network.

[0042] In one or more example methods, the third core network node 600C verifies the authorization request by the second core network node 600B by sending authentication information to the second core network node 600B (1009). This verification may be based on the authentication information and one or more of subscription information of the first wireless device 300 and groups to which the first wireless device 300 belongs.

[0043] If the second core network node 600B verifies the authorization request, the second core network node 600B may send an authorization validation acceptance message 1010, such as an authorization confirmation message, to the third core network node. In one or more example methods, the authorization validation acceptance message 1010 may include proprietary information necessary to use the service API. The proprietary information may include keys and / or secrets generated by the second core network node.

[0044] In one or more example methods, the third core network node 600C uses a service API for wireless device positioning to transmit an authorization acceptance message 1011 indicating that the first wireless device is authorized to use the service API for wireless device positioning. The authorization acceptance message may include dedicated information required to use the service API.

[0045] Upon being authorized to use a service API, such as a service API for wireless device positioning, the first wireless device 300 may transmit a message 1012 via the service API requesting positioning of multiple second devices, such as a positioning request, such as a relative positioning and / or ranging request. The message 1012 may include identifiers for identifying the multiple second wireless devices. The message 1012 may trigger further authorization verification to confirm that the first wireless device is authorized to retrieve the requested positioning information. The message 1012 may trigger ranging and / or relative positioning between two second wireless devices (e.g., between wireless device 300A and wireless device 300B).

[0046] The third core network node may trigger the fourth core network node 600D, such as an LMF, to transmit positioning requests 1014A, 1014B, such as relative positioning requests for one or both of the second wireless devices (e.g., between wireless device 300A and wireless device 300B), by transmitting a request 1013, such as a positioning request to determine relative positions of a plurality of second wireless devices, to the fourth core network node 600D. The positioning requests 1014A, 1014B may be transmitted over the first interface, such as using LPP over the control plane.

[0047] The fourth core network node 600D may receive positioning results 1015A, 1015B, such as ranging results, from the second wireless device 300A and / or the second wireless device 300B using the first interface, such as using LPP over the control plane. The positioning results 1015A, 1015B may indicate a relative position between the two second wireless devices 300A and 300B. The positioning result 1015A from the second wireless device 300A may include a relative distance and direction to the second wireless device 300B. The positioning result 1015B from the second wireless device 300B may include a relative distance and direction to the second wireless device 300A.

[0048] The fourth core network node 600D may send a positioning result message including the relative positions of the plurality of second wireless devices to the third core network node 600C.

[0049] The third core network node 600C transmits the relative positions of the plurality of second wireless devices 1017 to the first wireless device 300 via a service API, for example in a positioning result message.

[0050] In other words, according to the present disclosure, the first wireless device may use the same service API as the AF, such as a location API (e.g., a northbound API), for positioning the wireless device. Using the service API provides an excellent solution for checking that the first wireless device is authorized to use the service API. To check whether the AF is authorized to use the API, a first core network node, such as an NEF, checks a second core network node, such as a UDM, for records. The first core network node can do the same for the wireless device. The first core network node can either check the subscription record of the first wireless device in the second core network node or check whether the wireless device belongs to the same group, e.g., the same application group ID, as multiple second wireless devices. The application group configuration may be provisioned by the AF as described in 3GPP TS23.304 v.17.1.0.

[0051] Exemplary advantages of using the service API to determine locations, such as relative locations, of multiple second wireless devices are: To obtain the locations of the multiple wireless devices, the first wireless device does not need to be in the vicinity of the multiple second wireless devices. The first wireless device can even obtain locations from different PLMNs, such as from another country. The exposure function for -AF can be adapted to wireless devices. The first core network node, such as the NEF, has built-in functionality for authorizing application functions to use the service, which can be adapted to also support wireless devices registered in the network.

[0052] FIG. 3 shows a flow diagram of an example method 100 for accessing a service API performed by a first wireless device. A service API is an interface that provides a device or program with a description of how to interact with a system to retrieve and / or exchange data within the system. An API service is a means by which a piece of software (e.g., a mobile app) interacts with functionality stored in a software backend, such as stored on a server or made available by a third party. The first wireless device may be a first wireless device disclosed herein, such as the first wireless device 300 of FIGS. 1, 2, and 8. A first wireless device that intends to access and / or use a service API may also be referred to herein as a service API caller or API caller. In one or more example methods, the method 100 is performed by a first wireless device to determine relative positions between multiple second wireless devices based on a core network's positioning capabilities, such as based on LMF.

[0053] The method 100 includes transmitting control information to a core network via a first interface, the control information including an indication that the first wireless device intends to access a service API, such as a service API control node. The first wireless device's indication may, in one or more exemplary ways, be a request to access the service API or a request for information necessary to access the service API. In one or more exemplary ways, the control information includes one or more of an identifier identifying the first wireless device and information identifying a service API, such as a service API control node, that the first wireless device intends to access. The control information may be transmitted to a network node implementing an Access and Mobility Management Function (AMF) of the core network. In one or more exemplary ways, the first interface is a control channel. The first interface may be an N1 interface between the wireless device and the AMF. In one or more exemplary ways, the control information is included in a registration request message, such as an initial registration request message and / or a registration request message resulting from movement of the first wireless device. In one or more exemplary ways, the first wireless device performs the registration request by transmitting a registration request message including an indication indicating that the first wireless device desires to access the service API. The indication that the first wireless device desires to access the service API may be signaled as a wireless device capability exchange indicating that the first wireless device can use the service API and / or an explicit indication that the first wireless device desires to use the service API. This step S102 corresponds to 1001 described in connection with FIG. 2.

[0054] The method 100 includes receiving S104, via a first interface, access information required to access a service API, such as a service API control node. The access information is received from a core network, such as from a network node implementing an AMF of the core network. In one or more exemplary methods, the access information includes one or more of authorization information, authentication information, an address to the service API control node, and a fully qualified domain name (FQDN) of the service API control node. The authorization information may indicate which functions the first wireless device is authorized to use. The service the first wireless device is authorized to use may be, for example, a positioning service provided by an LMF or the like. The authorization information may include onboarding enrollment information required to access the service API. The authentication information may include subscriber information and / or a CERT for identifying the first wireless device, such as a root certificate authority (CA) certificate. The onboarding enrollment information may be used to authenticate and establish secure Transport Layer Security (TLS) communications with a CAPIF core function, such as a Network Exposure Function (NEF), with the service API control node, for example, via a second interface, during the onboarding process. The onboarding enrollment information may include details of the CAPIF core function, such as an address and / or a root CA certificate. The onboarding enrollment information may further include onboarding credentials, such as an Open Authorization (OAuth) 2.0 access token. This step S104 corresponds to 1004 described in connection with FIG. 2.

[0055] Control and / or access information is transmitted, in one or more exemplary methods, using Non-Access Stratum (NAS) signaling.

[0056] In one or more exemplary methods, the method 100 includes establishing S101, S106 a data connection to a core network via NAS signaling over a first interface, such as by performing a Protocol Data Unit (PDU) session establishment procedure. In one or more exemplary methods, the data connection is established S101 before transmitting control information over the first interface S102. In one or more exemplary methods, the data connection is established S106 after receiving access information necessary to access a service API over the first interface S104. In one or more exemplary methods, an already established data connection can be reused to access the service API control node.

[0057] Upon determining to use the service API, the method 100 includes performing S108 a service API onboarding procedure based on the access information via a second interface. In one or more exemplary methods, the second interface is an established data connection with the core network node, such as a data connection for transmitting user data, such as user data using Hypertext Transfer Protocol (HTTP). The second interface may also be referred to as a PDU session. In one or more exemplary methods, the onboarding procedure may be performed using data via the established data connection, such as the service API. In one or more exemplary methods, the onboarding procedure may be performed using a data protocol, such as Hypertext Transfer Protocol (HTTP). In one or more exemplary methods, the onboarding procedure may be performed using a core network node that implements functionality for onboarding the wireless device, such as using a service API control node.

[0058] In one or more exemplary methods, performing the onboarding procedure S108 includes establishing secure communication with the core network S108A. The first wireless device and a service API control node, such as an NEF, may establish secure communication based on TLS (Server side certificate authentication). The first wireless device may establish secure communication based on onboarding enrollment information.

[0059] In one or more exemplary methods, performing the onboarding procedure S108 includes sending an onboarding request message S108B to the core network for service API control, etc. The onboarding request message may include onboarding enrollment information, such as onboarding credentials (OAuth 2.0 access token) and / or a CERT. If a CERT for the first wireless device, such as a client certificate, is issued by a third party, the onboarding request message may further include the CERT. The first wireless device may generate a key pair {private key, public key} and provide the public key to the onboarding request message. This step S108B corresponds to 1005 described in connection with FIG. 2.

[0060] In one or more exemplary methods, performing the onboarding procedure S108 includes receiving an onboarding response message S108C from a core network, such as an API control node. The onboarding response message may include an API caller profile of the first wireless device. The API caller profile may include one or more APIs, such as a list of one or more APIs, that the first wireless device can use. The onboarding response message may include one or more of an identifier (ID) assigned to the first wireless device by the service API control node that identifies the first wireless device, such as an API caller ID, authentication and authorization information generated by the API control node, a certificate for the first wireless device, and a secret generated by the API control node, such as an onboard secret for the first wireless device. This step S108C corresponds to 1007 described in connection with FIG. 2.

[0061] In one or more exemplary methods, the service API is a service API of a core network node, such as a service API for positioning of a wireless device, such as an exposure API for ranging and sidelink positioning.

[0062] In one or more exemplary methods, communication over the first interface uses a lower protocol layer, such as a lower protocol layer in a protocol stack, such as a 5G control plane protocol stack, than communication over the second interface.

[0063] In one or more example methods, the method 100 includes performing an authorization procedure S109 to authorize the first wireless device to use the service API via the second interface, which step S109 is similar to step 1008 described in connection with FIG.

[0064] In one or more exemplary methods, performing the authorization procedure S109 includes sending an authorization request message for using the service API to the core network S109A. The authorization request message may be a request to be authorized by the network to use the service API. In one or more exemplary methods, the authorization request message for using the service API is sent over the established data connection.

[0065] In one or more exemplary methods, the service API is a service API for positioning of a wireless device. In one or more exemplary methods, performing an authorization procedure S109, such as when the method is performed to determine relative positions of multiple wireless devices, includes sending an authorization request message S109A′ to a core network, such as a service API control node, to use a service API for positioning of a wireless device, e.g., to use an exposure API for ranging and sidelink positioning. The authorization request message may request a network, such as a service API control node, to perform an authorization verification to confirm that the first wireless device is authorized to use a service API, such as a service API for positioning of a wireless device. Thus, the authorization request message may request the network to verify, with another network node and / or by checking based on stored information, that the first wireless device is authorized to access a particular service API of the core network.

[0066] In one or more exemplary methods, the authorization request message includes access information for authenticating the first wireless device to use a service API for positioning of the wireless device. In one or more exemplary methods, the access information includes one or more of authorization information, authentication information, an address to a service API control node, and a fully qualified domain name (FQDN) of the service API control node. In one or more exemplary methods, the authorization request message includes authentication information for authenticating the first wireless device, such as for authenticating the first wireless device to use a service API for positioning of the wireless device. The authentication information may include one or more of an identifier identifying the first wireless device, such as an API caller ID and / or a Mobile Station International Subscriber Directory Number (MSISDN), and a CERT of the first wireless device.

[0067] In one or more exemplary methods, sending S109A, S109A' includes sending the authorization request S109AA to a service API control node, for example, a service API control node of a core network, for example, a node implementing a CAPIF core function such as an NEF.

[0068] In one or more exemplary methods, performing the authorization procedure S109 includes receiving an authorization acceptance message from the core network S109B when the wireless device is authorized to use the service API. In one or more exemplary methods, the core network is a service API control node. In one or more exemplary methods, receiving S109B, S109B' includes receiving an authorization acceptance message from the service API control node S109BA. In one or more exemplary methods, the authorization acceptance message is an authorization acceptance message for using a service API for positioning of a wireless device. In other words, in one or more exemplary methods, the authorization acceptance message may indicate that the first wireless device is authorized to use a service API for positioning of a wireless device. The authorization acceptance message may indicate that the first wireless device is authorized to access and / or use the requested service API. In one or more exemplary methods, the authorization acceptance message includes dedicated information necessary to use the service API for positioning of a wireless device. In one or more example methods, the authorization acceptance message and / or the proprietary information may include a key and / or a secret generated by a second core network node, such as a core network node implementing a data management function. This step S109B corresponds to 1011 described in connection with FIG. 2.

[0069] In one or more exemplary methods, method 100 includes, upon successfully completing the authorization procedure, e.g., upon receiving an authorization accept message (S109BA), sending a message to the core network using a service API S110, S110′. In one or more exemplary methods, the core network is a service API control node, such as a network exposure function (NEF). In one or more exemplary methods, the message is a positioning request for a plurality of second wireless devices. In one or more exemplary methods, for example, if the message is a positioning request for a plurality of second wireless devices, the message identifies a plurality of second wireless devices, such as a plurality of second wireless devices, whose relative positions are to be determined. In one or more exemplary methods, the message requests determination of the relative positions of the plurality of second wireless devices. This step S110, S110′ is similar to step 1012 described in connection with FIG. 2.

[0070] In one or more example methods, the method 100 includes receiving S112 the relative positions of the plurality of second wireless devices using a service API for positioning of the wireless device when the first wireless device is authorized by the service API control node to access the relative positions of the plurality of second wireless devices.

[0071] 4 shows a flow diagram of an example method 200 for enabling a wireless device to access a service API of a core network, performed by a first core network node. The first core network node may be a core network node disclosed herein, such as the first core network node 600A of FIGS. 1, 2, and 9. The first core network node may be a core network node that implements AMF.

[0072] In one or more exemplary methods, method 200 includes receiving S202, from a wireless device, control information including an indication that the wireless device intends to access a service API, such as a service API control node. In one or more exemplary methods, the control information includes one or more of an identifier identifying the first wireless device and information identifying the service API that the first wireless device intends to access. The control information may be transmitted to a network node implementing an Access and Mobility Management Function (AMF) of a core network. In one or more exemplary methods, the first interface is a control channel, such as a control channel for 3GPP control signaling, such as NAS signaling. The first interface may be an N1 interface between the wireless device and the AMF. In one or more exemplary methods, the control information is included in a registration request message, such as an initial registration request message and / or a registration request message resulting from movement of the first wireless device. In one or more exemplary methods, the first wireless device performs a registration request including an indication indicating that the first wireless device desires to access the service API. The indication that the first wireless device desires to access the service API may be signaled as a wireless device capability exchange indicating that the first wireless device can use the service API and / or an explicit indication that the first wireless device desires to use the service API. This step S202 corresponds to 1001 described in connection with FIG. 2.

[0073] In one or more exemplary methods, the method 200 includes performing S204 a first authorization verification by a second core network node based on the control information to authorize the wireless device to access a service API. The second core network node may be a network node implementing a data management function, such as a network node implementing a unified data management (UDM) function, or a network node implementing any other network function capable of verifying and providing necessary information to the wireless device. In one or more exemplary methods, performing S204 the authorization procedure includes transmitting S204A a first authorization verification request message for the wireless device to access a service API, such as a service API control node, based on the control information to the second core network node. In one or more exemplary methods, performing S204 the authorization verification includes checking whether the first wireless device is authorized to access a service API, such as to access any service API, by the second network node, such as a network node implementing a data management function. The verification may be performed by the second core network node by comparing the control information with subscription information of the first wireless device. This may also be done by other network functions that have the functionality to verify and provide the necessary information to the UE. This step S204A corresponds to 1002 described in relation to FIG.

[0074] In one or more exemplary methods, performing the authorization procedure S204 includes receiving access information necessary to access a service API, such as a service API control node, from a second core network node S204B once the wireless device is authorized to use the service API. In one or more exemplary methods, the access information includes one or more of authorization information, authentication information, an address to the service API control node, and a fully qualified domain name (FQDN) of the service API control node. The authorization information may indicate which functions the first wireless device is authorized to use. The authorization information may include onboarding enrollment information necessary to access the service API. The authentication information may include one or more of an identifier for identifying the first wireless device, subscriber information, and / or a CERT for identifying the first wireless device. The onboarding enrollment information may include details of the CAPIF core function, such as an address and / or a root CA certificate of the CAPIF core function. The onboarding enrollment information may further include onboarding credentials such as an OAuth 2.0 access token. This step S204B corresponds to 1003 described in relation to FIG.

[0075] In one or more example methods, the method 200 includes transmitting access information necessary to access the service API to the first wireless device S208 once the wireless device is authorized to access the service API, such as the service API control node. This step S208 corresponds to 1004 described in connection with FIG. 2 .

[0076] In one or more exemplary methods, the method 100 includes establishing a data connection between the wireless device and the core network S200, S206. In one or more exemplary methods, the data connection is established S200 before receiving control information from the wireless device S202. In one or more exemplary methods, the data connection is established S206 after performing an authorization procedure S204.

[0077] 5 illustrates a flow diagram of an example method 300 implemented by a second core network node for enabling a wireless device to access a service API of a core network. In one or more example methods, the method 300 implemented by the second core network node is for enabling a first wireless device to determine a relative position among multiple second wireless devices based on a positioning function of the core network. The second core network node is a second core network node disclosed herein, such as the second core network node 600B of FIGS. 1, 2, and 10. In one or more example methods, the second core network node is a network node that implements a data management function, such as a network node that maintains subscriber information of wireless devices. In one or more example methods, the data management function is a UDM and / or a PCF and / or an AUSF and / or a 5G Direct Discovery Name Management Function (DDNMF).

[0078] In one or more exemplary methods, the method 300 includes receiving S302 a first authorization verification request message from a first core network node to authorize the first wireless device to access a service API, e.g., to access a service API control node. In one or more exemplary methods, the first authorization verification request includes control information. In one or more exemplary methods, the control information includes one or more of an identifier that identifies the wireless device and information that identifies the service API that the wireless device is attempting to access and / or use. This step S302 corresponds to 1002 described in connection with FIG. 2.

[0079] In one or more example methods, the method 300 includes verifying S304 whether the wireless device is authorized to access a service API, such as a service API control node, based on the control information. In one or more example methods, verifying S304 includes comparing the received control information to stored information, such as subscription information, regarding whether the first wireless device is authorized to access a service API, such as a service API control node.

[0080] In one or more example methods, the method 300 includes, once the wireless device is authorized to access a service API, such as a service API control node, transmitting access information necessary to access the service API to a first core network node, such as a service API control node, S306. In one or more example methods, the access information includes one or more of authorization information, authentication information, an address to the service API control node, and an FQDN of the service API control node. This step S306 is similar to 1003 described in connection with FIG. 2.

[0081] In one or more example methods, the method 300 includes receiving S308 a second authorization verification request message from a third core network node, such as from a service API control node, for authorizing the wireless device to use a service API, e.g., a specific service API controlled by the service API control node. In one or more example methods, the second authorization verification request includes access information. This step S308 corresponds to 1009 described in connection with FIG. 2.

[0082] In one or more exemplary methods, the method 300 includes receiving S308′ from a service API control node a verification request message for verifying whether the first wireless device is authorized to use a service API for positioning of a wireless device. In one or more exemplary methods, the verification request message includes access information for accessing the service API for positioning of a wireless device. The access information may include authentication information for identifying the first wireless device. The authentication information may include one or more of an identifier for identifying the first wireless device, such as an API caller ID and / or a Mobile Station International Subscriber Directory Number (MSISDN), and a CERT of the first wireless device. In other words, the second authorization verification request message may be a verification request message for verifying whether the first wireless device is authorized to use a service API for positioning of a wireless device.

[0083] In one or more example methods, the method 300 includes verifying S310 whether the wireless device is authorized to use the service API based on the access information. In one or more example methods, the verifying S310 includes verifying S310′ whether the wireless device is authorized to use the service API based on the access information and one or more rules and / or subscription data.

[0084] In one or more exemplary methods, the method 300 includes transmitting an authorization validation acceptance message to a third core network node, such as a service API control node, once the wireless device is authorized to use the service API. In one or more exemplary methods, the authorization validation acceptance message may indicate that the wireless device is authorized to use the service API for wireless device positioning. In one or more exemplary methods, the authorization validation acceptance message includes dedicated information necessary to use the service API, such as the service API for wireless device positioning. In one or more exemplary methods, the dedicated information includes one or more of an identifier identifying the first wireless device, such as an API caller ID and / or a CERT of the first wireless device. In one or more exemplary methods, the dedicated information may include a key and / or a secret generated by the second core network node. This step S312, S312′ corresponds to 1010 described in connection with FIG. 2.

[0085] In one or more example methods, the method 300 includes receiving S314 a request message from a third core network node, such as a service API control node, to verify that the first wireless device is authorized to access the relative locations of the plurality of second wireless devices. In one or more example methods, the verification message includes information identifying the plurality of second devices. The information identifying the plurality of second devices may be identification information, such as the MSISDN of each of the plurality of second wireless devices, such as the primary second wireless device WD A and the secondary second wireless device WD B, or a respective application user ID or a respective inter-device ID.

[0086] In one or more exemplary methods, the method 300 includes verifying S316 whether one or more rules for accessing the relative positions of the multiple second wireless devices are satisfied based on the dedicated information required to use the service API and the information identifying the multiple second wireless devices.

[0087] In one or more exemplary methods, the one or more rules include: The relative positions of the plurality of second wireless devices are not restricted; The first wireless device belongs to the same group as a plurality of second wireless devices; and - the first wireless device is specifically authorized to access the relative positions of multiple second wireless devices; Contains one or more of the following:

[0088] In one or more examples, the groups may be defined by a third party, for example, by a Third Party Application Function (AF) as described in 3GPP TS23.304 v.17.1.0. Wireless devices may be grouped based on, for example, the MSISDNs of the wireless devices. A rule may indicate, for example, that these MSISDNs are in the same group.

[0089] In one or more examples, some subscribers may be grouped together, for example, all subscribers belonging to, for example, the police or fire department may be grouped together in the same group.

[0090] In one or more example methods, wireless devices may be grouped by a third-party AF, such as a game register. A group may indicate, for example, that wireless devices in the group are players in the same group, such as being on the same team or playing the same game during an active game period.

[0091] In one or more example methods, the method 300 includes sending S318 a positioning accept message to the service API control node when the first wireless device is authorized to access the relative positions of the plurality of second wireless devices. In one or more example methods, the positioning accept message indicates that the first wireless device is authorized to access the relative positions of the plurality of second wireless devices. In one or more example methods, the service API control node is a third core network node.

[0092] 6 shows a flow diagram of an example method 400 for enabling a wireless device to access a service API of a core network, performed by a third core network node. In one or more example methods, the method is for enabling a first wireless device to determine a relative position among multiple second wireless devices based on a positioning function of the core network, such as an LMF. In one or more example methods, the third core network node is a third core network node disclosed herein, such as the third core network node 600C of FIGS. 1, 2, and 11. In one or more example methods, the third core network node is a service API control node, such as a network node implementing a CAPIF core function, such as an NEF.

[0093] In one or more exemplary methods, method 400 includes receiving S402 an API onboarding request message from a wireless device, such as a first wireless device, via the established data connection. In one or more exemplary methods, the API onboarding request message includes access information for accessing a service API, for example, accessing a service API control node. The onboarding request message may include onboarding enrollment information, such as onboarding credentials (OAuth 2.0 access token) and / or a CERT. If the CERT for the first wireless device, such as a client certificate, is issued by a third party, the first wireless device may further include the CERT. In one or more exemplary methods, the onboarding request message may include a public key generated by the wireless device. The data connection may be established via a second interface. This step S402 corresponds to 1005 described in connection with FIG. 2.

[0094] In one or more exemplary methods, the method 400 includes performing an onboarding procedure S404 to authorize the wireless device to use the service API based on the access information. Performing the onboarding procedure S404 may include verifying onboarding enrollment information, such as enrollment credentials (e.g., an OAuth 2.0 access token) and / or a CERT. In one or more exemplary methods, upon successful verification of the onboarding enrollment information, such as the enrollment credentials, the third core network node generates a profile, such as an API caller profile as specified in 3GPP TS23.222 v 17.5.0, for the first wireless device. The profile may include selected methods for authentication and authorization between the first wireless device and the service API control node. The third core network node may generate a certificate for the first wireless device, also referred to as an API caller, attempting to access the service API for the assigned first wireless device identity and public key. The certificate may be used by the first wireless device for subsequent authentication procedures with the service API control node and may be used to establish a secure connection and authentication with the service API control node's API Exposing Function (AEF). In one or more exemplary methods, the third network node may generate a secret, such as Onboard_Secret, when the service API uses Method 3 for CAPIF-2e security (specified in Section 6.5.2.3 of 3GPP TS33.122 rel-16). The value of Onboard_Secret may remain the same for the lifetime of onboarding and may be bound to a specific wireless device ID, such as a specific API caller ID, generated by the third core network node. In one or more exemplary methods, when the third core network node, such as a CAPIF core function, trusts the issuer of the wireless device's client certificate, the third core network node includes the provided certificate in a profile, such as an API caller profile.In one or more exemplary methods, accepting a client certificate issued by a third party depends on CAPIF domain policy. This step S404 corresponds to 1006 described in connection with FIG.

[0095] In one or more exemplary methods, performing an onboarding procedure to authorize the wireless device to use the service API S404 includes transmitting an authorization verification request message to the second core network node S404A for the wireless device to use the service API, e.g., to access a service API control node, based on the access information. In one or more exemplary methods, the API onboarding procedure request message includes access information that authenticates the first wireless device to use the service API for positioning of the wireless device. In one or more exemplary methods, the access information includes one or more of authorization information, authentication information, an address to the service API control node, and an FQDN of the service API control node.

[0096] In one or more exemplary methods, once the wireless device is authorized to use the service API, performing an onboarding procedure for authorizing the wireless device to use the service API S404 includes receiving an API onboarding response message from the second core network node S404B.

[0097] In one or more example methods, the method 400 includes transmitting an API onboarding response message to the wireless device via the established data connection S406 once the wireless device is authorized to access a service API, such as a service API control node. The onboarding response message may include information from an API caller profile of the first wireless device. The API caller profile may include one or more APIs, such as a list of one or more APIs, that the first wireless device can use. The onboarding response message may include one or more of an identifier (ID) assigned to the first wireless device by the service API control node that identifies the first wireless device, such as an API caller ID, authentication and authorization information generated by the API control node, a certificate of the first wireless device, and a secret generated by the API control node, such as an onboard secret of the first wireless device.

[0098] In one or more exemplary methods, for example, when the method is for enabling a first wireless device to determine relative positions among multiple second wireless devices based on a positioning function of a core network, the method includes receiving, from the first wireless device via the established data connection, an authorization request message for using a service API. The authorization request message may include access information for authenticating the first wireless device. The authorization request message may request the third core network node to verify, based on the access information, that the first wireless device is authorized, e.g., permitted, to use the service API, e.g., access the service API. The access information for authenticating the first wireless device may include one or more of an identifier identifying the first wireless device, such as an API caller ID and / or an MSISDN, that verifies the identity of the first wireless device, and a CERT of the first wireless device. The API caller ID may be a temporary ID assigned to the first wireless device. The MSISDN may be a static address of the first wireless device, such as a telephone number. Based on the access information authenticating the first wireless device, the third core network node may, for example, authorize the first wireless device against a list of wireless devices that are allowed to use the service API, for example, by checking the identity of the first wireless device.

[0099] In one or more exemplary methods, the method 400 includes using a data management function and authorizing the first wireless device to access a service API for positioning of the wireless device S410 based on the access information.

[0100] In one or more exemplary methods, authorizing the first wireless device to access the service API for wireless device positioning S410 includes sending an authorization verification request message to a network node implementing a data management function S410A. In one or more exemplary methods, the authorization verification request message includes authentication information for verifying whether the first wireless device is authorized to access the service API for wireless device positioning. This step S410 corresponds to 1008 described in connection with FIG. 2.

[0101] In one or more exemplary methods, authorizing the first wireless device to use a service API for positioning of the wireless device S410 includes receiving an authorization verification acceptance message from a network node implementing a data management function S410B when the first wireless device is authorized to access the service API for positioning of the wireless device.

[0102] In one or more exemplary methods, such as when the first wireless device is authorized to access the wireless device positioning service API, the method 400 includes sending an authorization acceptance message to the first wireless device using the wireless device positioning service API S412. In one or more exemplary methods, the authorization acceptance message indicates that the first wireless device is authorized to use the wireless device positioning service API. In one or more exemplary methods, the authorization acceptance message includes dedicated information necessary to use the wireless device positioning service API. In one or more exemplary methods, the authorization acceptance message and / or the dedicated information may include a security method, key, and / or secret to be used. In one or more exemplary methods, the secret may be generated by a second core network node, such as a core network node implementing a data management function, and / or a third core network node, such as a service API control node. This step S412 corresponds to 1011 described in connection with FIG. 2.

[0103] In one or more exemplary methods, method 400 includes receiving S414 from the first wireless device, using a service API for wireless device positioning, a message including information identifying multiple second wireless devices. In one or more exemplary methods, the message requests determination of relative positions of the multiple second wireless devices. The information identifying the multiple second devices may be respective identification information, such as the MSISDN, application user ID, or inter-device ID, of the multiple second wireless devices, such as the primary second wireless device WD A and the secondary second wireless device WD B. This step S414 is similar to step 1012 described in connection with FIG. 2.

[0104] In one or more exemplary methods, the method 400 includes authorizing S416 the first wireless device to determine relative positions of the plurality of second wireless devices using a data management function and a message including information identifying the plurality of second wireless devices. In one or more exemplary methods, the data management function is a UDM and / or a PCF and / or a DDNMF.

[0105] In one or more exemplary methods, authorizing S416 includes verifying S416A using a data management function, for example by a second core network node implementing the data management function, and based on a message including identifiers identifying the multiple second wireless devices, whether one or more rules for accessing the relative positions of the multiple second wireless devices are satisfied.

[0106] In one or more exemplary methods, the one or more rules include: The relative positions of the plurality of second wireless devices are not restricted; The first wireless device belongs to the same group as a plurality of second wireless devices; and - the first wireless device is specifically authorized to access the relative positions of multiple second wireless devices; Contains one or more of the following:

[0107] In one or more examples, the groups may be defined by a third party, for example, by a third-party AF as described in 3GPP TS23.304 v.17.1.0. Wireless devices may be grouped based on, for example, the MSISDNs of the wireless devices. A rule may indicate, for example, that these MSISDNs are in the same group.

[0108] In one or more examples, some subscribers may be grouped together, for example, all subscribers belonging to, for example, the police or fire department may be grouped together in the same group.

[0109] In one or more example methods, wireless devices may be grouped by a third-party AF, such as a game register. A group may indicate, for example, that wireless devices in the group are players in the same group, such as being on the same team or playing the same game during an active game period.

[0110] In one or more example methods, the method 400 includes, if the first wireless device is authorized to determine the relative positions of the plurality of second wireless devices, performing a positioning procedure S418 to determine the relative positions of the plurality of second wireless devices based on the positioning capabilities and the messages identifying the plurality of second wireless devices. This step S418 is similar to steps 1013 and 1016 described in connection with FIG. 2 .

[0111] In one or more exemplary methods, performing the positioning procedure S418 includes transmitting a request to a network node implementing a positioning function, e.g., a core network node implementing an LMF, S418A to determine relative positions of the plurality of second wireless devices, such as between a primary second network node and a secondary second network node, based on the message identifying the plurality of second wireless devices. In one or more exemplary methods, the request to determine relative positions of the plurality of second wireless devices may be, for example, a ranging request. This step S418A corresponds to 1013 described in connection with FIG. 2.

[0112] In one or more exemplary methods, performing the positioning procedure S418 includes receiving a positioning result message S418B from a network node implementing a core network positioning function when the first wireless device is authorized to access the relative positions of the multiple second wireless devices. In one or more exemplary methods, the positioning result message includes the relative positions of the multiple second wireless devices, such as between a primary second wireless device and a secondary second wireless device. In one or more exemplary methods, the positioning result message is a ranging result message. The relative positions may include the relative distances and / or directions between the multiple second wireless devices, such as between a primary second network node and a secondary second network node, in one or more exemplary methods. This step S418B corresponds to 1016 described in connection with FIG. 2.

[0113] In one or more exemplary methods, the method 400 includes transmitting S420 relative positions of the plurality of second wireless devices to the first wireless device using a service API for wireless device positioning. The relative positions may, in one or more exemplary methods, include relative distances and / or directions between the plurality of second wireless devices, such as between a primary second network node and a secondary second network node. This step S420 corresponds to 1017 described in connection with FIG. 2.

[0114] 7 shows a flow diagram of an example method 500 for enabling a first wireless device to determine a relative position among a plurality of second wireless devices, performed by a fourth core network node. In one or more example methods, the fourth core network node is a fourth core network node disclosed herein, such as the fourth core network node 600D of FIGS. 1, 2, and 12. In one or more example methods, the fourth core network node is a network node that implements a positioning function, such as an LMF.

[0115] A method 500 for enabling a first wireless device to determine a relative position between a plurality of second wireless devices, performed by a network node implementing a positioning function of a core network, includes the following.

[0116] In one or more example methods, method 500 includes receiving S502 a request from a service API control node to determine relative positions of a plurality of second wireless devices. In one or more examples, the request includes information identifying the plurality of second wireless devices, such as a primary second wireless device and a secondary second wireless device. In one or more example methods, the request to determine relative positions of the plurality of second wireless devices may be, for example, a ranging request. This step S502 corresponds to 1013 described in connection with FIG. 2.

[0117] In one or more example methods, the method 500 includes performing a positioning procedure S506 to determine relative positions among the plurality of second wireless devices. Performing the positioning procedure may include transmitting a ranging request to each second wireless device and / or receiving a ranging result from each second wireless device. This step S506 is similar to 1014A, 1014B, 1015A, and / or 1015B described in connection with FIG. 2 .

[0118] In one or more example methods, the method 500 includes sending a positioning result message to the service API control node S508. In one or more example methods, the positioning result message includes relative positions of the plurality of second wireless devices. This step S508 corresponds to 1016 described in connection with FIG. 2.

[0119] 8 shows a block diagram of an example wireless device 300 according to the present disclosure, such as a first wireless device disclosed herein. The wireless device 300 includes a memory circuit 301, a processor circuit 302, and a wireless interface 303. The wireless device 300 may be configured to perform any of the methods disclosed in FIG. 3. In other words, the wireless device 300 may be configured to access a service API, such as a service API for positioning of wireless devices. In one or more example methods, the wireless device 300 may be configured to determine relative positions between multiple second wireless devices based on positioning capabilities of a core network.

[0120] The wireless device 300 is configured to communicate with network nodes, such as the wireless devices disclosed herein, using a wireless communication system.

[0121] The wireless device 300 is configured to send an authorization request message (e.g., via the wireless interface 303) to the service API control node via the second interface over the established data connection to use the service API for positioning of the wireless device, the authorization request message including access information for authenticating the first wireless device to use the service API for positioning of the wireless device.

[0122] Upon receiving the authorization acceptance message to use the service API for positioning of the wireless device, the wireless device 300 is configured to send (e.g., via the wireless interface 303) a message identifying multiple second wireless devices to a service API control node that uses the service API for positioning of the wireless device, the message requesting determination of relative positions of the multiple second wireless devices.

[0123] The wireless device 300 is configured to receive (e.g., via the wireless interface 303) the relative positions of the plurality of second wireless devices using a service API for wireless device positioning when the first wireless device is authorized by the service API control node to access the relative positions of the plurality of second wireless devices.

[0124] The air interface 303 is configured for wireless communication via a wireless communication system, e.g., a 3GPP system, e.g., a 3GPP system supporting one or more of the following: LTE, E-UTRA, New Radio (NR), Narrowband IoT, NB-IoT, and Long Term Evolution - enhanced Machine Type Communication (LTE-M), millimeter wave communication, e.g., licensed spectrum millimeter wave communication, e.g., licensed spectrum device-to-device millimeter wave communication.

[0125] 3 (e.g., any one or more of S101, S102, S104, S106, S108, S108A, S108B, S108C, S109, S109A, S109A′, S109AA, S109B, S109B′, S109BA, S110, S110′, S112). The operations of the wireless device 300 may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) stored in a non-transitory computer-readable medium (e.g., memory circuitry 301) and executed by processor circuitry 302.

[0126] Furthermore, the operations of the wireless device 300 may be considered as methods that the wireless device 300 is configured to perform. Also, while the functions and operations described may be implemented in software, such functions may also be performed via dedicated hardware or firmware, or some combination of hardware, firmware, and / or software.

[0127] The memory circuit 301 may be one or more of a buffer, flash memory, a hard drive, removable media, volatile memory, nonvolatile memory, random access memory (RAM), or other suitable device. In a typical configuration, the memory circuit 301 may include nonvolatile memory for long-term data storage and volatile memory that serves as system memory for the processor circuit 302. The memory circuit 301 may exchange data with the processor circuit 302 via a data bus. Control lines and an address bus between the memory circuit 301 and the processor circuit 302 may also be present (not shown in FIG. 8 ). The memory circuit 301 is considered a non-transitory computer-readable medium.

[0128] The memory circuitry 301 may be configured to store information (e.g., access information, onboarding information, etc.) in a portion of the memory.

[0129] 9 shows a block diagram of an exemplary first core network node 600A, such as a core network node implementing AMF, in accordance with the present disclosure. The first core network node 600A comprises a memory circuit 601A, a processor circuit 602A, and an interface 603A. The first core network node 600A may be configured to perform any of the methods disclosed in FIG. 4. In other words, the first core network node 600A may be configured to enable wireless devices to access a service API of the core network.

[0130] The first core network node 600A is configured to communicate with wireless devices, such as the first wireless device disclosed herein, using a wireless communication system.

[0131] The interface 603A may be a wired interface and / or a wireless interface configured for wireless communication via a wireless communication system, e.g., a 3GPP system, e.g., a 3GPP system supporting one or more of the following: LTE, E-UTRA, New Radio (NR), Narrowband IoT, NB-IoT, and Long Term Evolution - Enhanced Machine Type Communications (LTE-M), millimeter wave communication, e.g., licensed spectrum millimeter wave communication, e.g., licensed spectrum device-to-device millimeter wave communication.

[0132] In one or more examples, the first core network node 600A is configured to receive control information from a wireless device, for example via the air interface 603A, including an indication that the wireless device is attempting to access a service API.

[0133] In one or more examples, the first core network node 600A is configured to perform a first authorization verification with the second core network node based on the control information, for example using the processor circuitry 602A, to authorize the wireless device to access the service API.

[0134] In one or more examples, the first core network node 600A is configured to transmit access information required to access the service API to the wireless device, for example via the wireless interface 603A, once the wireless device is authorized to access the service API.

[0135] The processor circuitry 602A is optionally configured to perform any of the operations disclosed in Figure 4 (e.g., any one or more of S200, S202, S204, S204A, S204B, S206, S208). The operations of the first core network node 600A may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) stored in a non-transitory computer-readable medium (e.g., memory circuitry 601A) and executed by the processor circuitry 602A.

[0136] Furthermore, the operations of the first core network node 600A may be considered as methods that the first core network node 600A is configured to perform. Also, while the described functions and operations may be implemented in software, such functions may also be performed via dedicated hardware or firmware, or some combination of hardware, firmware and / or software.

[0137] The memory circuit 601A may be one or more of a buffer, flash memory, hard drive, removable media, volatile memory, nonvolatile memory, random access memory (RAM), or other suitable device. In a typical configuration, the memory circuit 601A may include nonvolatile memory for long-term data storage and volatile memory that serves as system memory for the processor circuit 602A. The memory circuit 601A may exchange data with the processor circuit 602A via a data bus. Control lines and address buses between the memory circuit 601A and the processor circuit 602A may also be present (not shown in FIG. 9). The memory circuit 601A is considered a non-transitory computer-readable medium.

[0138] The memory circuit 601A may be configured to store information (eg, access information, onboarding information, etc.) in a portion of the memory.

[0139] 10 shows a block diagram of an exemplary second core network node 600B, such as a core network node implementing data management functionality, in accordance with the present disclosure. The second core network node 600B comprises a memory circuit 601A, a processor circuit 602B, and an interface 603B. The second core network node 600B may be configured to perform any of the methods disclosed in FIG. 4. In other words, the second core network node 600B may be configured to enable wireless devices to access a core network service API and / or to enable a first wireless device to determine relative positions between multiple second wireless devices.

[0140] The second core network node 600B is configured to communicate with wireless devices, such as the first wireless device disclosed herein, using a wireless communication system.

[0141] The interface 603B may be a wired interface and / or a wireless interface configured for wireless communication via a wireless communication system, e.g., a 3GPP system, e.g., a 3GPP system supporting one or more of the following: LTE, E-UTRA, New Radio (NR), Narrowband IoT, NB-IoT, and Long Term Evolution - Enhanced Machine Type Communications (LTE-M), millimeter wave communication, e.g., licensed spectrum millimeter wave communication, e.g., licensed spectrum device-to-device millimeter wave communication.

[0142] The second core network node 600B is configured to receive, for example via interface 603B, from the service API control node a verification request message for verifying whether the first wireless device is authorized to use the service API for positioning of the wireless device, wherein the verification request message includes access information for accessing the service API for positioning of the wireless device.

[0143] The second core network node 600B is configured, for example, using the processor circuitry 602B and / or the interface 603B, to verify whether the wireless device is authorized to use the service API for positioning of the wireless device based on the access information and one or more rules and / or subscription data.

[0144] The second core network node 600B is configured to send an authorization verification acceptance message to the service API control node, for example via interface 603B, when the wireless device is authorized to use the service API for positioning of the wireless device, where the authorization verification acceptance message includes dedicated information required to use the service API for positioning of the wireless device.

[0145] The processor circuitry 602B is optionally configured to perform any of the operations disclosed in Figure 5 (e.g., any one or more of S302, S304, S306, S308, S308', S310, S310', S312, S312', S314, S316, S318). The operations of the second core network node 600B may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) stored in a non-transitory computer-readable medium (e.g., memory circuitry 601B) and executed by the processor circuitry 602B.

[0146] Furthermore, the operations of the second core network node 600B may be considered as methods that the second core network node 600B is configured to perform. Also, while the described functions and operations may be implemented in software, such functions may also be performed via dedicated hardware or firmware, or some combination of hardware, firmware and / or software.

[0147] The memory circuit 601B may be one or more of a buffer, flash memory, a hard drive, removable media, volatile memory, nonvolatile memory, random access memory (RAM), or other suitable device. In a typical configuration, the memory circuit 601B may include nonvolatile memory for long-term data storage and volatile memory that serves as system memory for the processor circuit 602B. The memory circuit 601B may exchange data with the processor circuit 602B via a data bus. Control lines and an address bus between the memory circuit 601B and the processor circuit 602B may also be present (not shown in FIG. 10). The memory circuit 601B is considered a non-transitory computer-readable medium.

[0148] The memory circuit 601B may be configured to store information (eg, access information, onboarding information, etc.) in a portion of the memory.

[0149] 11 shows a block diagram of an exemplary third core network node 600C, such as a service API control node, in accordance with the present disclosure. The third core network node 600C includes a memory circuit 601C, a processor circuit 602C, and an interface 603C. The third core network node 600C may be configured to implement any of the methods disclosed in FIG. 4. In other words, the third core network node 600C may be configured to enable a wireless device to access a service API of the core network and / or to enable a first wireless device to determine a relative position between multiple second wireless devices based on a positioning capability of the core network.

[0150] The third core network node 600C is configured to communicate with wireless devices, such as the first wireless device disclosed herein, using a wireless communication system.

[0151] The interface 603C may be a wired interface and / or a wireless interface configured for wireless communication via a wireless communication system, e.g., a 3GPP system, e.g., a 3GPP system supporting one or more of the following: LTE, E-UTRA, New Radio (NR), Narrowband IoT, NB-IoT, and Long Term Evolution - Enhanced Machine Type Communications (LTE-M), millimeter wave communication, e.g., licensed spectrum millimeter wave communication, e.g., licensed spectrum device-to-device millimeter wave communication.

[0152] The third core network node 600C is configured to receive, for example via interface 603C, from the first wireless device via the established data connection, an authorization request message for using the service API, wherein the authorization request message includes access information that authorizes the first wireless device to use the service API for positioning of the wireless device.

[0153] The third core network node 600C is configured, for example, using the processor circuit 602C and / or the interface 603C, using a data management function, and based on the access information, to authorize the first wireless device to use a service API for positioning of the wireless device.

[0154] The third core network node 600C includes receiving, for example via interface 603C, from the first wireless device using a service API for wireless device positioning, a message including information identifying a plurality of second wireless devices, the message requesting determination of relative positions of the plurality of second wireless devices.

[0155] The third core network node 600C is configured, for example using the processor circuit 602C and / or the interface 603C, to authorize the first wireless device to determine the relative positions of the plurality of second wireless devices using data management functions and messages including information identifying the plurality of second wireless devices.

[0156] The third core network node 600C is configured, when the first wireless device is authorized to determine the relative positions of the plurality of second wireless devices, to perform, for example, using the processor circuitry 602C, a positioning procedure to determine the relative positions of the plurality of second wireless devices based on the positioning capabilities and messages identifying the plurality of second wireless devices.

[0157] The third core network node 600C is configured to transmit relative positions of a plurality of second wireless devices to the first wireless device using a service API for positioning of the wireless device, for example via interface 603C, when the wireless device is authorized to access the service API.

[0158] The processor circuitry 602C is optionally configured to perform any of the operations disclosed in Figures 6A-6B (e.g., any one or more of S402, S404, S404A, S404B, S406). The operations of the second core network node 600B may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) stored in a non-transitory computer-readable medium (e.g., memory circuitry 601C) and executed by the processor circuitry 602C.

[0159] Furthermore, the operations of the second core network node 600C may be considered as methods that the second core network node 600C is configured to perform. Also, while the described functions and operations may be implemented in software, such functions may also be performed via dedicated hardware or firmware, or some combination of hardware, firmware and / or software.

[0160] The memory circuit 601C may be one or more of a buffer, flash memory, hard drive, removable media, volatile memory, nonvolatile memory, random access memory (RAM), or other suitable device. In a typical configuration, the memory circuit 601C may include nonvolatile memory for long-term data storage and volatile memory that serves as system memory for the processor circuit 602C. The memory circuit 601C may exchange data with the processor circuit 602C via a data bus. Control lines and address buses between the memory circuit 601C and the processor circuit 602C may also be present (not shown in FIG. 11 ). The memory circuit 601C is considered a non-transitory computer-readable medium.

[0161] The memory circuit 601C may be configured to store information (eg, access information, onboarding information, etc.) in a portion of the memory.

[0162] 12 shows a block diagram of an exemplary fourth core network node 600D, such as a core network node implementing a positioning function such as LMF, in accordance with the present disclosure. The fourth core network node 600D comprises a memory circuit 601D, a processor circuit 602D, and an interface 603D. The fourth core network node 600D may be configured to implement any of the methods disclosed in FIG. 4. In other words, the fourth core network node 600D may be configured to enable a first wireless device to determine a relative position between multiple second wireless devices.

[0163] The interface 603D may be a wired interface for communicating with one or more core network nodes.

[0164] The fourth core network node 600D is configured to receive, for example via interface 603D, from a service API control node a request to determine the relative positions of a plurality of second wireless devices, the request including information identifying the plurality of second wireless devices.

[0165] The fourth core network node 600D is configured to perform a positioning procedure for determining relative positions between a plurality of second wireless devices, for example using the processor circuitry 602D and / or the interface 603D.

[0166] The fourth core network node 600D is configured to send, for example via interface 603D, a positioning result message including the relative positions of the plurality of second wireless devices to the service API control node.

[0167] The processor circuitry 602D is optionally configured to perform any of the operations (e.g., any one or more of S502, S506, S508) disclosed in Figure 7. The operations of the fourth core network node 600D may be embodied in the form of executable logic routines (e.g., lines of code, software programs, etc.) stored in a non-transitory computer-readable medium (e.g., memory circuitry 601D) and executed by the processor circuitry 602D.

[0168] Furthermore, the operations of the fourth core network node 600D may be considered as methods that the fourth core network node 600D is configured to perform. Also, while the described functions and operations may be implemented in software, such functions may also be performed via dedicated hardware or firmware, or some combination of hardware, firmware and / or software.

[0169] The memory circuit 601D may be one or more of a buffer, flash memory, a hard drive, removable media, volatile memory, nonvolatile memory, random access memory (RAM), or other suitable device. In a typical configuration, the memory circuit 601D may include nonvolatile memory for long-term data storage and volatile memory that serves as system memory for the processor circuit 602D. The memory circuit 601D may exchange data with the processor circuit 602D via a data bus. Control lines and an address bus between the memory circuit 601D and the processor circuit 602D may also be present (not shown in FIG. 12). The memory circuit 601D is considered a non-transitory computer-readable medium.

[0170] The memory circuit 601D may be configured to store information (eg, information identifying the plurality of second wireless devices, relative locations of the plurality of second wireless devices, etc.) in a portion of the memory.

[0171] Examples of methods and products (network nodes and wireless devices) according to the present disclosure are described in the following sections: Item 1. A method for enabling a first wireless device to determine a relative position among a plurality of second wireless devices based on a positioning capability of a core network, the method being implemented by a service application programming interface (API) control node, the method comprising: receiving an authorization request message for using the service API from the first wireless device via the established data connection (S408), the authorization request message including access information for authenticating the first wireless device; - using a data management function and authorizing the first wireless device to use a service API for wireless device positioning based on the access information (S410); - receiving a message from a first wireless device using a service API for positioning of wireless devices, the message including information identifying a plurality of second wireless devices (S414), the message requesting determination of relative positions of the plurality of second wireless devices; - authorizing the first wireless device to determine relative positions of the plurality of second wireless devices using a data management function and a message including information identifying the plurality of second wireless devices (S416); - if the first wireless device is authorized to determine the relative positions of the plurality of second wireless devices, performing a positioning procedure to determine the relative positions of the plurality of second wireless devices based on the positioning capability and the messages identifying the plurality of second wireless devices (S418); - transmitting relative positions of a plurality of second wireless devices to the first wireless device using a service API for positioning of the wireless device (S420). Item 2. Authorizing the first wireless device to access a service API for positioning of the wireless device (S404′) - sending an authorization verification request message to a network node implementing a data management function, the authorization verification request message including authentication information for verifying whether the first wireless device is authorized to access a service API for positioning of the wireless device (S410A); - The method described in item 1, comprising: - receiving an authorization verification acceptance message from a network node implementing a data management function when the first wireless device is authorized to access a service API for positioning of the wireless device (S410B). Item 3. - A method as described in Item 1 or 2, including using a service API for positioning of a wireless device to send an authorization acceptance message to the first wireless device indicating that the first wireless device has been approved to use the service API for positioning of a wireless device (S412). Item 4. The method described in Item 3, wherein the authorization acceptance message includes dedicated access information required to use a service API for positioning of the wireless device. Item 5. The method according to any one of Items 1 to 4, wherein authorizing (S416) includes verifying (S416A) whether one or more rules for accessing relative positions of the plurality of second wireless devices are satisfied using a data management function and based on a message including identifiers that identify the plurality of second wireless devices. Item 6. One or more rules: The relative positions of the plurality of second wireless devices are not restricted; The first wireless device belongs to the same group as a plurality of second wireless devices; - the first wireless device is specifically authorized to access the relative positions of multiple second wireless devices; Item 6. The method according to item 5, comprising one or more of the following: Item 7. The method of any one of the preceding items, wherein the access information includes one or more of authorization information, authentication information, an address to the service API control node, and a fully qualified domain name (FQDN) of the service API control node. Item 8. Carrying out the positioning procedure (S418) - sending a request to a network node implementing a positioning function to determine relative positions of the plurality of second wireless devices based on the message identifying the plurality of second wireless devices (S418A); - if the first wireless device is authorized to access the relative positions of the plurality of second wireless devices, receiving a positioning result message including the relative positions of the plurality of second wireless devices from a network node implementing a positioning function of the core network (S418B); 10. The method of any one of the preceding items, including: Item 9. A method for enabling a first wireless device to determine a relative position between a plurality of second wireless devices, the method being performed by a network node implementing a data management function, the method comprising: - receiving a verification request message from a service application programming interface (API) control node to verify whether the first wireless device is authorized to use a service API for positioning of the wireless device (S308'), the verification request message including access information for accessing the service API for positioning of the wireless device; - verifying whether the wireless device is authorized to use a service API for positioning of the wireless device based on the access information and one or more rules and / or subscription data (S310'); -When the first wireless device is authorized to use a service API for positioning of the wireless device, sending an authorization verification acceptance message to a service API control node (S312'), wherein the authorization verification acceptance message includes dedicated information required to use the service API for positioning of the wireless device. Item 10. - Receiving a request message for verifying that the first wireless device is authorized to access the relative positions of the plurality of second wireless devices (S314), the request message including information identifying the plurality of second devices; - verifying whether one or more rules for accessing the relative positions of the second wireless devices are satisfied based on the dedicated access information and the information identifying the second wireless devices (S316); -When the first wireless device is authorized to access the relative positions of the plurality of second wireless devices, the method described in item 9 includes sending a positioning acceptance message to the service API control node indicating that the first wireless device is authorized to access the relative positions of the plurality of second wireless devices (S318). Item 11. One or more rules: The relative positions of the plurality of second wireless devices are not restricted; The first wireless device belongs to the same group as a plurality of second wireless devices; - the first wireless device is specifically authorized to access the relative positions of multiple second wireless devices; Item 11. The method according to item 10, comprising one or more of: Item 12. The method according to any one of Items 9 to 11, wherein the access information includes one or more of authorization information, authentication information, an address to the service API control node, and a fully qualified domain name (FQDN) of the service API control node. Item 13. A method implemented by a first wireless device for determining relative positions among a plurality of second wireless devices based on a positioning function of a core network, comprising: - sending an authorization request message for using a service API for positioning of the wireless device to a service application programming interface (API) control node of the core network via the established data connection (S109A'), the authorization request message including access information for authenticating the first wireless device; - upon receiving an authorization acceptance message to use a service API for positioning of a wireless device, sending a message identifying a plurality of second wireless devices to a service API control node that uses the service API for positioning of a wireless device (S110'), the message requesting determination of relative positions of the plurality of second wireless devices; - when the first wireless device is authorized by the service API control node to access the relative positions of the plurality of second wireless devices, receiving the relative positions of the plurality of second wireless devices using a service API for positioning of the wireless device (S112). Item 14.—The method of item 13, including receiving an authorization acceptance message from the service API control node when the wireless device is authorized to use the service API (S109B′). Item 15. The method described in Item 13 or 14, wherein the access information includes one or more of authorization information, authentication information, an address to the service API control node, and a fully qualified domain name (FQDN) of the service API control node. Item 16. The method according to any one of Items 13 to 15, wherein the authorization acceptance message includes dedicated information required to use a service API for positioning of the wireless device. Item 17. A method for enabling a first wireless device to determine a relative position between a plurality of second wireless devices, the method being performed by a network node implementing a core network positioning function, the method comprising: receiving a request from a service application programming interface (API) control node to determine relative positions of a plurality of second wireless devices (S502), the request including information identifying the plurality of second wireless devices; - performing a positioning procedure to determine relative positions between a plurality of second wireless devices (S506); - transmitting a positioning result message including relative positions of the plurality of second wireless devices to a service API control node (S508). Item 18. A service application programming interface (API) control node comprising a memory circuit, a processor circuit, and an interface, and configured to implement any of the methods described in any of items 1 to 8. Item 19. A network node implementing a data management function, comprising a memory circuit, a processor circuit, and an interface, and configured to perform any of the methods described in any of items 9 to 12. Item 20. A wireless device comprising a memory circuit, a processor circuit, and a wireless interface, and configured to implement any of the methods described in any of Items 13 to 16. Item 21. A network node implementing a core network positioning function, comprising a memory circuit, a processor circuit, and an interface, and configured to perform any of the methods described in Item 17.

[0172] The use of terms such as "first," "second," "third," and "fourth," "primary," "secondary," "secondary," "tertiary," etc., does not imply a particular order, but is included to identify individual elements. Furthermore, the use of terms such as "first," "second," "third," and "fourth," "primary," "secondary," "secondary," "tertiary," etc., does not indicate order or importance; rather, terms such as "first," "second," "third," and "fourth," "primary," "secondary," "tertiary," etc., are used to distinguish one element from another. Note that terms such as "first," "second," "third," and "fourth," "primary," "secondary," "tertiary," etc., are used herein and elsewhere for labeling purposes only and are not intended to indicate a particular spatial or temporal order. Furthermore, the labeling of a first element does not imply the presence of a second element, or vice versa.

[0173] It will be understood that FIGS. 1-12 include some circuits, components, features, or operations shown with solid lines and some circuits or operations shown with dashed lines. Circuits, components, features, or operations included with solid lines are circuits or operations included in the broadest examples. Circuits, components, features, or operations configured with dashed lines are examples that may be included in, or may be part of, circuits, components, features, or operations that may occur in addition to the circuits, components, features, or operations of the solid line examples, or are additional circuits, components, features, or operations. It will be understood that these operations need not be performed in the order presented. Furthermore, it will be understood that not all operations need be performed. Example operations may be performed in any order and in any combination. It will be understood that these operations need not be performed in the order presented. Circuits, components, features, or operations configured with dashed lines may be considered optional.

[0174] Other operations not described herein may be incorporated into the example operations, for example, one or more additional operations may be performed before, after, simultaneously with, or between any of the described operations.

[0175] Certain features described above as separate implementations may also be implemented in combination in a single implementation. Conversely, features described as a single implementation may also be implemented separately in multiple implementations or in any suitable subcombination. Furthermore, while features may be described above as acting in a particular combination, one or more features from a claimed combination may, in some cases, be deleted from the combination, and the combination may be claimed as any subcombination or variation of any subcombination.

[0176] It should be noted that the word "comprising" does not necessarily exclude the presence of other elements or steps than those listed.

[0177] It should be noted that the word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements.

[0178] Furthermore, it should be noted that any reference signs do not limit the scope of the claims, and that examples may be implemented at least in part by both hardware and software, and that several "means," "units," or "devices" may be represented by the same item of hardware.

[0179] Various example methods, devices, nodes, and systems described herein are described in the general context of method steps or processes that may be implemented in one aspect by a computer program product embodied in a computer-readable medium containing computer-executable instructions, such as program code, executed by computers in a network environment. Computer-readable media may include removable and non-removable storage devices, including, but not limited to, read-only memory (ROM), random-access memory (RAM), compact discs (CDs), digital versatile discs (DVDs), and the like. Generally, program circuitry may include routines, programs, objects, components, data structures, and the like that perform specified tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program circuitry represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

[0180] While features have been illustrated and described, they are not intended to limit the claimed disclosure, and it will be apparent to those skilled in the art that various changes and modifications can be made without departing from the scope of the claimed disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The claimed disclosure is intended to cover all alternatives, modifications, and equivalents.

Claims

1. 1. A method implemented by a service application programming interface (API) control node for enabling a first wireless device to determine a relative position among a plurality of second wireless devices based on a positioning capability of a core network, the method comprising: receiving an authorization request message for using a service API from the first wireless device via the established data connection (S408), the authorization request message including access information for authenticating the first wireless device; Using a data management function and based on the access information, authorizing the first wireless device to use the service API for wireless device positioning (S410); receiving, from the first wireless device, a message including information identifying the plurality of second wireless devices using the service API for wireless device positioning (S414); the message requesting determination of the relative positions of the plurality of second wireless devices; authorizing the first wireless device to determine the relative positions of the plurality of second wireless devices using a data management function and the message including information identifying the plurality of second wireless devices (S416); If the first wireless device is authorized to determine the relative positions of the plurality of second wireless devices, performing a positioning procedure to determine the relative positions of the plurality of second wireless devices based on the positioning capability and the message identifying the plurality of second wireless devices (S418); and transmitting (S420) to the first wireless device the relative positions of the plurality of second wireless devices using the service API for positioning of wireless devices.

2. Authorizing the first wireless device to access the service API for positioning of wireless devices (S404′), Sending an authorization verification request message to a network node implementing a data management function, the authorization verification request message including authentication information for verifying whether the first wireless device is authorized to access the service API for wireless device positioning (S410A); 2. The method of claim 1, further comprising: receiving an authorization validation acceptance message from the network node implementing a data management function if the first wireless device is authorized to access the service API for wireless device positioning (S410B).

3. The method of claim 1, comprising sending to the first wireless device (S412) an authorization acceptance message using the service API for positioning of the wireless device, indicating that the first wireless device has accepted use of the service API for positioning of the wireless device.

4. The method of claim 3 , wherein the authorization acceptance message includes dedicated access information necessary to use the service API for positioning of a wireless device.

5. 2. The method of claim 1, wherein authorizing (S416) includes verifying, using the data management function and based on the message including identifiers that identify the plurality of second wireless devices, whether one or more rules for accessing the relative positions of the plurality of second wireless devices are satisfied (S416A).

6. The one or more rules: the relative positions of the plurality of second wireless devices are not restricted; the first wireless device belongs to the same group as the plurality of second wireless devices; the first wireless device is specifically authorized to access the relative positions of the plurality of second wireless devices; The method of claim 5 , comprising one or more of:

7. The method of claim 1 , wherein the access information includes one or more of authorization information, authentication information, an address to a service API control node, and a fully qualified domain name (FQDN) of the service API control node.

8. Implementing the positioning procedure (S418), sending, to a network node implementing the positioning functionality, a request to determine relative positions of the plurality of second wireless devices based on the message identifying the plurality of second wireless devices (S418A); and receiving (S418B) a positioning result message including the relative positions of the plurality of second wireless devices from the network node implementing the positioning function of the core network when the first wireless device is authorized to access the relative positions of the plurality of second wireless devices.

9. 1. A method for enabling a first wireless device to determine a relative position between a plurality of second wireless devices, the method being performed by a network node implementing a data management function, the method comprising: receiving a verification request message from a service application programming interface (API) control node to verify whether the first wireless device is authorized to use a service API for positioning of a wireless device (S308'); the verification request message includes access information for accessing the service API for positioning of a wireless device; Verifying whether the wireless device is authorized to use the service API for wireless device positioning based on the access information and one or more rules and / or subscription data (S310'); When the first wireless device is authorized to use the service API for positioning of a wireless device, sending an authorization verification acceptance message to the service API control node (S312'), wherein the authorization verification acceptance message includes dedicated information required to use the service API for positioning of a wireless device. receiving a request message for verifying that the first wireless device is authorized to access the relative positions of the plurality of second wireless devices (S314), the request message including information identifying the plurality of second devices; Verifying whether one or more rules for accessing the relative positions of the plurality of second wireless devices are satisfied based on dedicated access information and the information identifying the plurality of second wireless devices (S316); 10. The method of claim 9, further comprising: when the first wireless device is authorized to access the relative positions of the plurality of second wireless devices, transmitting to the service API control node (S318) a positioning accept message indicating that the first wireless device is authorized to access the relative positions of the plurality of second wireless devices.

11. The one or more rules: the relative positions of the plurality of second wireless devices are not restricted; the first wireless device belongs to the same group as the plurality of second wireless devices; the first wireless device is specifically authorized to access the relative positions of the plurality of second wireless devices; The method of claim 10, comprising one or more of:

12. The method of claim 9 , wherein the access information includes one or more of authorization information, authentication information, an address to a service API control node, and a fully qualified domain name (FQDN) of the service API control node.

13. 1. A method implemented by a first wireless device for determining relative positions among a plurality of second wireless devices based on a positioning capability of a core network, comprising: sending an authorization request message to a service application programming interface (API) control node of a core network via the established data connection to use a service API for positioning of the wireless device (S109A'); the authorization request message includes access information for authenticating the first wireless device; Upon receiving an authorization acceptance message to use the service API for positioning of a wireless device, sending a message identifying the plurality of second wireless devices to the service API control node that uses the service API for positioning of a wireless device (S110'), the message requesting determination of the relative positions of the plurality of second wireless devices; and when the first wireless device is authorized by the service API control node to access the relative positions of the plurality of second wireless devices, receiving the relative positions of the plurality of second wireless devices using the service API for wireless device positioning (S112).

14. The method of claim 13, further comprising receiving an authorization acceptance message from the service API control node when the wireless device is authorized to use the service API (S109B').

15. The method of claim 13 , wherein the access information includes one or more of authorization information, authentication information, an address to a service API control node, and a fully qualified domain name (FQDN) of the service API control node.

Images