Methods, devices and medium for sidelink positioning

Abstract

Embodiments of the present disclosure relate to methods, devices and computer readable storage medium for sidelink positioning. In the method, a first network device receives a first request for positioning of a first terminal device with respect to a second terminal device, where the first request includes a first identifier of the second terminal device. The first network device obtains information of the second terminal device based on the first identifier of the second terminal device, where the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device. The first network device causes, based on the information of the second terminal device, the positioning of the first terminal device to be performed.

Description

METHODS, DEVICES AND MEDIUM FOR SIDELINK POSITIONINGFIELDS

[0001] Various embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices and computer readable storage medium for sidelink positioning.BACKGROUND

[0002] This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

[0003] In the third-generation partnership project (3GPP) Release 18 (Rel-18) Sidelink Positioning and Ranging has been studied and specified. The 3GPP standards provides solutions how distance between two user equipment (UEs) can be calculated. 3GPP TS 23.273, Version V0.0.0 and TS 23.586, V18.0.0 define the procedures for Sidelink Mobile Originating Location Request (SL-MO-LR) and Sidelink Mobile Terminating Location Request (SL-MT-LR). The SL-MO-LR procedure enables user equipment (UE) to obtain Sidelink positioning / ranging location results using one or more other UEs with the assistance of a location management function (LMF) in a serving Public Land Mobile Network (PLMN) for UE1. The Ranging / SL Positioning location results may include absolute locations, relative locations or distances and directions, depending on the service request. If the Target UE decides to initiate SL-MO-LR procedure, it includes one or multiple SL reference UE(s) I Located UE (s) in the service request. The generic procedure is defined in TS 23.586, V18.0.0.SUMMARY

[0004] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0005] In the SL-MO-LR or SL-MT-LR procedure, there may be cases only Application layer ID of UE1 to UEn is provided while Application layer ID is not supposed to be used for messages routing over different PLMNs. In other words, the NF receiving the positioning request with UEn's application layer ID cannot determine the PLMN that UEn belongs to trigger subsequent steps. In the SL-MT-LR procedure, there may be cases only generic public subscription identifier (GPSI) of UE1-UEn is provided, while the receiving network function (NF) (e.g., GMLC) may still need to get Application Layer ID of UE1 -UEn to enable SL positioning between UE1 -UEn over PC5.

[0006] To overcome or mitigate at least one of the above-mentioned problems or other problems or provide a useful solution, embodiments of the present disclosure propose methods, devices and storage medium for sidelink positioning.

[0007] In a first aspect of the present disclosure, there is provided a method implemented at a first network device. In the method, the first network device receives a first request for positioning of a first terminal device with respect to a second terminal device, where the first request includes a first identifier of the second terminal device. The first network device obtains information of the second terminal device based on the first identifier of the second terminal device, where the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device. The first network device causes, based on the information of the second terminal device, the positioning of the first terminal device to be performed.

[0008] In an example, the first identifier comprises one of an application layer identifier, a generic public subscription identifier and a public land mobile network information. The second identifier comprises a different one of the application layer identifier, the generic public subscription identifier and the public land mobile network information.

[0009] In an example, the first network device comprises at least one of: a network device in a first home network of the first terminal device, a network device in a visiting network of both the first and second terminal devices, or a location server associated with the positioning of the first terminal device.

[0010] In an example, the information comprises the second identifier of the second terminal device. The first network device determines the second identifier of the second terminal device from the first identifier of the second terminal device based on mapping between the first identifier of the second terminal device and the second identifier of the second terminal device.

[0011] In an example, the first network device transmits, to a second network device, a second request for the information of the second terminal device, where the second request includes the first identifier of the second terminal device; and receives, from the second network device, the information of the second terminal device.

[0012] In an example, the information comprises the second identifier of the second terminal device. The second request comprises a request for mapping of the first identifier of the second terminal device to the second identifier of the second terminal device.

[0013] In an example, the information comprises the result of the privacy check of the second terminal device. In an example, the second request comprises a request for the privacy check of the second terminal device.

[0014] In an example, the first network device determines the second network device based on the first identifier of the second terminal device.

[0015] In an example, the second network device comprises at least one of: a network device in a second home network of the second terminal device, an application server associated with the positioning of the first terminal device.

[0016] In an example, the first network device transmits, to a third network device, a third request for the positioning of the first terminal device.

[0017] In an example, the third network device comprises at least one of: a network device in a visiting network of both the first terminal device and the second terminal device, or a network device in a second home network of the second terminal device.

[0018] In an example, the first request is received from an application function associated with the positioning of the first terminal device.

[0019] In a second aspect of the present disclosure, there is provided a method implemented at a second network device. In the method, the second network device receives, from a first network device, a second request for information of a second terminal device. The second request includes the first identifier of the second terminal device. The second network device obtains the information of the second terminal device based on the first identifier of the second terminal device. The information of the second termin al device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device. The second network device transmits, to the first network device, the information of the second terminal device.

[0020] In an example, the first identifier comprises at least one identifier of an application layer identifier, a generic public subscription identifier and a public land mobile network information . In an example, the second identifier comprises at least one further identifier of the application layer identifier, the generic public subscription identifier and the public land mobile network information.

[0021] In an example, the information comprises the second identifier of the second terminal device . In an example, the second network device determines mapping between the first identifier of the second terminal device and the second identifier of the second terminal device. The second network device determines the second identifier of the second terminal device from the first identifier of the second terminal device based on the mapping between the first identifier of the second terminal device and the second identifier of the second terminal device.

[0022] In an example, the information comprises the result of the privacy check of the second terminal device. In an example, the second network device performs the privacy check of the second terminal device to obtain the result of the privacy check of the second terminal device.

[0023] In an example, the first network device comprises at least one of: a network device in a first home network of the first terminal device, a network device in a visiting network of both the first and second terminal devices, or a location server associated with the positioning of the first terminal device.

[0024] In an example, the second network device comprises at least one of: a network device in a second home network of the second terminal device, an application server associated with the positioning of the first terminal device.

[0025] In a third aspect of the present disclosure, there is provided a first network device. The first network device comprises a memory containing instructions. The first network device further comprises a processor that executes the instructions to perform the method according to the first aspect.

[0026] In a fourth aspect of the present disclosure, there is provided a second network device. The second network device comprises a memory containing instructions. The second network device further comprises a processor that executes the instructions to perform the method according to the second aspect.

[0027] In a fifth aspect of the present disclosure, there is provided an apparatus. The apparatus comprises means for performing the method according to the first or second aspect.

[0028] In sixth aspect of the disclosure, there is provided a computer-readable storage medium having instructions stored thereon, the instructions, which, when executed by a processing system, cause the processing system to perform the method according to the first or second aspect.

[0029] With the present disclosure, during positioning of a fist terminal device with respect to a second terminal device, based on a first identifier of the second terminal device, a network device determines other information of the second terminal device. This scheme may allow a translation of different information of the located or reference UE for positioning of a target UE, which may improve the efficiency of SL positioning.BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Through the more detailed description of some embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, where the same reference generally refers to the same components in the embodiments of the present disclosure.

[0031] FIG. 1 is a diagram showing an example communication environment in which embodiments of the present disclosure can be implemented.

[0032] FIG. 2 is a signaling diagram a process for SL positioning in accordance with some embodiments of the present disclosure.

[0033] FIG. 3A is a diagram showing a flowchart of an example SL-MT-LR process without application layer ID provided in accordance with some embodiments of the present disclosure.

[0034] FIG. 3B is a diagram showing a flowchart of an example SL-MT-LR process without GPSI provided in accordance with some embodiments of the present disclosure.

[0035] FIG. 30 is a diagram showing a flowchart of an example SL-MO-LR process without GPSI provided in accordance with some embodiments of the present disclosure.

[0036] FIG. 4 is a diagram showing a flowchart of an example method of SL positioning in accordance with some embodiments of the present disclosure.

[0037] FIG. 5 is a diagram showing a flowchart of another example method of SL positioning in accordance with some other embodiments of the present disclosure.

[0038] FIG. 6 is a block diagram showing functional structures of a first network device in accordance with some embodiments.

[0039] FIG. 7 is a block diagram showing functional structures of a second network device in accordance with some embodiments.

[0040] FIG. 8 is a block diagram showing a communication device in accordance with some embodiments.

[0041] FIG. 9 is a block diagram showing a computer readable storage medium in accordance with some embodiments of the present disclosure.

[0042] FIG. 10 is a block diagram showing an example of a communication system in accordance with some embodiments.

[0043] FIG. 11 is a block diagram showing a UE in accordance with some embodiments.

[0044] FIG. 12 is a block diagram showing a network node in accordance with some embodiments.

[0045] FIG. 13 is a block diagram of a host in accordance with some embodiments.

[0046] FIG. 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0047] FIG. 15 is a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION

[0048] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0049] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to beinterpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step . Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa . Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0050] Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure . Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

[0051] As used herein, the terms "first", "second" and so forth refer to different elements . The singular forms "a" and "an" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises", "comprising", "has", "having", "includes" and / or "including" as used herein, specify the presence of stated features, elements, and / or components and the like, but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. The term "based on" is to be read as "based at least in part on" . The term "one embodiment" and "an embodiment" are to be read as "at least one embodiment" . The term "another embodiment" is to be read as "at least one other embodiment" . Other definitions, explicit and implicit, may be included below.

[0052] As used herein, the term "terminal device” refers to a device which is intended for accessing services via an access network and configured to communicate over the access network . The terminal device may be able to communicate with a network node, such as a base station, or with another terminal device by transmitting and / or receiving wireless signals. For instance, the terminal device may include, but is not limited to: a mobile phone, a smart phone, a sensor device, a meter, a vehicle, a household appliance, a medical appliance, a media player, a camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, a tablet computer, a laptop, or a personal computer (PC). The terminal device may also include a portable, pocket-storable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data, via a wireless connection.In the following description, the terms "terminal device”, "user equipment” and "UE” may be used interchangeably.

[0053] As used herein, the term "network node” refers to a device in a communication network via which a terminal device receives services from the network. The terms "network node”, "network function” may be used interchangeably. A network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g., on a cloud infrastructure. The network node comprises an access network node via which a terminal device accesses an access network. Examples of access network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio b ase stations, Node Bs, evolved Node Bs (eNBs) and newNR NodeBs (gNBs)). In the following description, the terms "access network node”, "base station” and "BS” may be used interchangeably.

[0054] The network node may further comprise a core network node. Examples of core network nodes may include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), an evolved Packet Data Gateway (ePGW), a trusted wireless local area network (WLAN) access network (TWLAN) node, a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Network Slice Selection Function (NSSF), a Serving Gateway (SGW), a Packet Data Network (PDN) Gateway (PGW), an Authentication Server Function (AUSF), a Subscription Identifier De-concealing function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0055] As used herein, the term "communication device” refers to a device capable of communications. Examples of a communication device may comprise a terminal device and a network device.

[0056] As used herein, the term "Located UE” refers to a sidelink (SL) reference UE of which the location is known or is able to be known using Uu based positioning. A Located UE can be used to determine the location of a Target UE using Sidelink Positioning.

[0057] As used herein, the term "positioning” refers to a functionality, which detects a geographical location and optionally, velocity (of e.g. a mobile terminal). As used herein, the term "ranging” refers to the determination of the distance between two UEs or more UEs and / or the direction of one UE (i.e. Target UE) from another UE (i.e. Reference UE) via PC5 interface. As used herein, the term "Sidelink Positioning” refers to positioning UE using PC5 to obtain absolute position, relative position, or ranging information.

[0058] As used herein, the term "relative position” refers to an estimate of the UE position relative to other network elements or relative to other UEs. As used herein, the term "relative velocity” refers to an estimate of the UE velocity relative to another UE.

[0059] As used herein, the term "SL Reference UE” refers to a UE, supporting positioning of target UE, e.g. by transmitting and / or receiving reference signals for positioning, providing positioning-related information,etc. using Sidelink. It is to be noted that SL reference UE is understood as "Anchor UE" in the 3GPP standards or documents. As used herein "target UE” refers to a UE whose distance, direction and / or position is measured with the support from one or multiple SL Reference UEs using Sidelink in the Ranging based service and Sidelink positioning.

[0060] As used herein, the term "Application Layer ID” refers to an identifier identifying a Ranging / Sidelink Positioning-enabled UE within the context of a specific application. The format of this identifier is outside the scope of 3GPP standards.

[0061] The SL-MT-LR procedure is used to estimate the relative locations or distances and / or directions between the UEs. The SL-MT-LR procedure enables a location service (LCS) Client or application function (AF) to obtain Ranging / Sidelink Positioning location results for a group of n UEs (n>2), i.e. UE1 , UE2, .... UEn. In the procedure, a Gateway Mobile Location Center (GMLC) determines a UE among the n UEs to be designated UE1 (i.e. Target UE in TS 23.586

[0040] ) and one or more other UEs designated UE2, UE3, .... UEn (n>2) (i.e. Reference / Located UEs in TS 23.586, V18.0.0). The Ranging / Sidelink Positioning location results may include absolute locations, relative locations or ranges and directions related to the UEs, based on the service request. Procedure for periodic and triggered SL-MT-LR is defined in clause 6.20.4.

[0062] It is to be noted that in order to check whether an external requester (e.g. AF) is allowed to get a position of any UE of UE1 to UEn, the Home (H) GMLC checks the UE LCS privacy profile belong to any UE of UE1 to UEn. The (H)GMLC invokes a Nudm_SDM_Get service operation towards a Unified Data Management (UDM) of each of the n UEs to get the privacy settings of the UE identified by its GPSI or Subscription Permanent Identifier (SUPI).

[0063] It was decided for Sidelink and Ranging that roaming is supported in Rel -18 in a way the UEs involved in ranging need to be served by the same PLMN, but they can belong to different PLMN. However, in the SL-MO-LR or SL-MT-LR procedure, there may be cases only Application layer ID of UE1 to UEn is provided while Application layer ID is not supposed to be used for messages routing over different PLMNs. In other words, the NF receiving the positioning request with UEn's application layer ID cannot determine the PLMN that UEn belongs to trigger subsequent steps. In the SL-MT-LR procedure, there may be cases only GPSI of UE1 -UEn is provided, while the receiving network function (NF) (e.g., GMLC) may still need to get Application Layer ID of UE1 -UEn to enable SL positioning between UE1 -UEn over PC5.

[0064] There was no solution related to translation between the GPSI and the Application Layer ID and the privacy checking if the home PLMN of the UE1 -UEn involved in ranging are not the same PLMN and only application layer ID is provided.

[0065] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Some embodiments of the present disclosure propose a sidelink positioning scheme. With this scheme, during positioning of a fist terminal device with respect to a second terminal device , based on afirst identifier of the second terminal device, a network device determines other information of the second terminal device, for example, including at least one of a second identifier, a result of a privacy check or a location of the second terminal device. This scheme may allow a translation of different information of the located or reference UE for positioning of a target UE.

[0066] In an example, with the proposed scheme, a services / interfaces / function between GMLCs belong to different PLMN may be defined. So far in case of normal LCS service, (H)GMLC can send a positioning request to visiting (V) GMLC. However, due to the complexity of Sidelink and Ranging, GMLCs need to provide other services to each other. If the Home GMLC of UE1 is not the Home GMLC of UE2, then GMLC may request Home GMLC of U2 to execute Privacy check. If the Home GMLC of UE1 is not the Home GMLC of UE2, then GMLC may request Home GMLC of U2 to execute translation from GPIS to Application Layer ID. In this way, a feasible solution is provided when UEs belonging to different PLMNs are roaming in 3rd PLMN. The SL positioning of a terminal device may be more effective and efficient.

[0067] FIG. 1 illustrates an example communication environment 100 in which embodiments of the present disclosure can be implemented.

[0068] As shown in FIG. 1 , the communication environment 100, which may be a part of a communication network, comprises a first terminal device 105 belonging to a first network 110 and a second terminal device 115 belonging to a second network 120. The first and second terminal devices 105 and 115 are both roaming in a third network 125 and can communicate with each other directly or via a network device such as a base station. In an example, the networks 110, 120 and 125 may be PLMNs which may include home PLMNs (HPLMNs) and a visiting PLMN (VPLMN) of the two terminal devices 105 and 110.

[0069] One network device 130, 135 or 140 is shown in one network 110, 120 or 125 only for the purpose of illustration, without suggesting any limitation. Each of the first, second and third networks 1 10, 120 and 125 may comprise any number of network devices which may implement any network function such as positioning, ranging, accessing, and other services. The communications in the communication environment 100 may use any suitable communication technologies and follow any communication protocols. The scope of the present disclosure will not be limited in this regard.

[0070] In the communication environment 100, the network devices 130, 135 and 140 can assist in SL positioning of the first and second terminal devices 105 and 115 across different networks 1 10, 120 and 125. Some example implementations will be described below with reference to FIG. 2.

[0071] FIG. 2 is a signaling diagram showing a process 200 for SL positioning in accordance with some embodiments of the present disclosure. The process 200 can be implemented between a first network device 205 and a second network device 210. The two network devices 205 and 210 may be implemented by the network devices 130, 135 and 140 in FIG. 1 or other network devices not shown.

[0072] As shown in FIG. 2, in the process 200, the first network device 205 receives (215) a first requestfor positioning of the first terminal device 105 with respect to the second terminal device 1 10. The first request, which may be a position request, may be received by any device which are intended to obtain a relative distance, relative locations, or relative velocities of the first terminal device 105 and the second terminal device 110. In an example, the transmitter of the first request may comprise an application server or application function (AF), a location server or location management function (LMF).

[0073] The first network device 205 may comprise any network device that can support the SL positioning of the first terminal device 105. In an example, the first network device 205 may comprise a network device in a first home network of the first terminal device 105 (e.g., the first network 110 in FIG. 1) or a network device in a visiting network of both the first and second terminal devices 105 and 110. Alternatively, or in addition, the first network device 205 may comprise a location server (such as LMF) associated with the positioning of the first terminal device 105.

[0074] The first request includes a first identifier of the second terminal device 110. The first identifier may comprise any type or form of identifiers that can identify the second terminal device 1 10. In some embodiments, the first identifier may comprise an application layer identifier (ID), a generic public subscription identifier (GPSI) and / or a public land mobile network (PLMN) information.

[0075] After receiving (215) the first request, the first network device 205 obtains (220) information of the second terminal device 110 based on the first identifier of the second terminal device 110. The information may comprise at least one of a second identifier, a result of a privacy check or a location of the second terminal device 210. The information may comprise any other information that can be used for the SL positioning of the first terminal device 110.

[0076] The first network device 205 may obtain the information of the second terminal device 110 based on the first identifier of the second terminal device 110 in any suitable way. In some embodiments, the first network device 205 may determine the second identifier of the second terminal device 110 from the first identifier of the second terminal device 110 based on mapping between the first identifier of the second terminal device and the second identifier of the second terminal device. For example, the first network device 205 such as an NF may have a local configuration to map the first identifier to the second identifier of the second terminal device 1 10. In the embodiments where the first identifier comprises one of an application layer identifier (ID), a generic public subscription identifier (GPSI) and / or a public land mobile network (PLMN) information, the second identifier may comprise a different one of the application layer ID, the GPSI and the PLMN information. For example, the first network device 205 may map the Application layer ID of the second terminal device 110 to PLMN information or GPSI of the second terminal device 110.

[0077] In some embodiments, the first network device 205 may request other devices to provide the mapping of the first identifier of the second terminal device 110 to the information of the second terminal device 110. As shown in FIG. 2, the first network device 205 may transmit (225), to the second network device 210, a second request for the information of the second terminal device 110. The second requestincludes the first identifier of the second terminal device 110. After the second network device 210 receives (230), from the first network device 205, the second request for the information of the second terminal device 110, the second network 210 may obtain (235) the information of the second terminal device based on the first identifier of the second terminal device. Then, the second network device 210 may transmit (240), to the first network device (105), the information of the second terminal device 11 0. Correspondingly, the first network device 205 may receive (245), from the second network device 210, the information of the second terminal device 110.

[0078] The second network device 210 may be any suitable network device that can assist in the SL positioning of the first terminal device 110. The first network device 210 may determine the second network device based on the first identifier of the second terminal device 120. In an example, the second network device may comprise a network device in a second home network of the second terminal device 110, such as the second network 120 in FIG. 1. For example, GMLC (as an example of the first network device 205) may request Home GMLC (as an example of the second network device 210) of the second terminal device 110 to make the translation of the first identifier to the second identifier of the second terminal device 110. Alternatively, or in addition, the second network device 210 may comprise an application server associated with the positioning of the first terminal device 105.

[0079] In the embodiments where the information of the second terminal device 110 comprises a second identifier of the second terminal device 110, the first network device 205 may transmit, to the second network device 210, a request for mapping of the first identifier of the second terminal device 105 to the second identifier of the second terminal device 210. The request includes the first identifier of the second terminal device. Then, the first network device 110 may receive, from the second network device 210, the second identifier of the second terminal device.

[0080] The second network device 210 may determine mapping between the first identifier of the second terminal device and a second identifier of the second terminal device; and then determine the second identifier of the second terminal device from the first identifier of the second terminal device based on the mapping between the first identifier of the second terminal device and the second identifier of the second terminal device.

[0081] For example, the first network device 205 may query an AF (as an example implementation of the second network device 210) to get mapping of the Application layer ID of the second terminal device 110 to the PLMN information or GPSI of the second terminal device 110.

[0082] In the embodiments where the information of the second terminal device 110 comprises a result of the privacy check of the second terminal device 120, the first network device 205 may transmit, to the second network device 210, a request for the privacy check of the second terminal device 210. The third request includes at least one of the first and second identifiers of the second network device . Accordingly, after the second network device 210 receives this request, the second network device 210 may perform theprivacy check of the second terminal device 110 to obtain the result of the privacy check of the second terminal device 110. Then, the first network device 205 may receive, from the second network device 210, the result of the privacy check of the second terminal device.

[0083] Based on the information of the second terminal device 110, the first network device 205 causes (250) the positioning of the first terminal device to be performed. In some embodiments, the first network device 205 may transmit, to a third network device, a third request for the positioning of the first terminal device 105. The third network device may comprise at least one of: a network device in a visiting network of both the first terminal device 105 and the second terminal device 110, or a network device in a second home network of the second terminal device 110.

[0084] For example, the NF (e.g. GMLC or LMF), as an example implementation of the fist network device 205, determines the PLMN information of the second terminal device 110 or derive PLMN information of the second terminal device 110 if mapping to GPSI is received. The NF sends the request to the PLMN of the second terminal device 110 to get UE ID (GPSI or Application layer ID) of the second terminal device 110 or ask for check privacy profile of the UE and then proceed the positioning procedure.

[0085] Some example process will be described below with reference to FIGS. 3A, 3B and 3C. In these embodiments, the first and second terminal devices 105 and 110 operate as UE1 and UE2 respectively.

[0086] FIG. 3A shows a flowchart of an example SL-MT-LR process 305 without application layer ID provided in accordance with some embodiments of the present disclosure.

[0087] In this example, the preconditions are as follows: PLMN1 is the Home PLMN of UE1 , but UE1 is visiting PLMN3; PLMN2 is the Home PLMN of UE2, but UE2 is visiting PLMN3. Based on different scenarios, any of PLMN1 / PLMN2 / PLMN3 might be same or different PLMNs each other.

[0088] At Step 1 , AF wants to get the distance between UE1 and UE2. AF sends position request i.e. SL- MT-LR to GMLC of UETs HPLMN i.e. GMLC1 and provides GPSI of both UEs. However, Application Layer ID of UE2 is not provided which is required for SL discovery over PC5 executed by UE1.

[0089] At Step2, GMLC1 (as an example of the first network device 205) checks the privacy profile of UE1 from its Home UDM1 ; GMLC1 may also obtain application layer ID of UE1 (if not provided in stepl) from UDR via NEF in PLMN1.

[0090] At Step3, GMLC1 determines the home PLMN of UE2 based GPSI of UE2. GMLC1 sends a request to GMLC2 (GMLC2 preferred, but could be other NF e.g. NEF, as an example of the second network device 210) of PLMN2 to ask for mapping of Application layer ID of UE2 to GPSI based on GPSI of UE2; GMLC2 obtains mapping of Application layer ID of UE2 to GPSI from UDR via NEF in PLMN2 and provides application layer ID of UE2 back to GMLC1. Further, GMLC1 sends a request to GMLC2 to check privacy of UE2, based on GPSI of UE2. GMLC2 checks the privacy profile of UE2 from UDM2 in PLMN2.

[0091] At Step4, if application layer ID of UE2 is obtained and privacy check of UE2 is OK, GMLC1 proceeds SL-MT-LR procedure and sends the requests to vGMLC in the serving PLMN (PLMN3), with GPSI and Application layer ID of UE1 and UE2 to proceed the SL-MT-LR procedure. At Step5: vGMLC now can execute position request.

[0092] FIG. 3B shows a flowchart of an example SL-MT-LR process 310 without GPSI provided in accordance with some embodiments of the present disclosure.

[0093] In this example, the preconditions are as follows: PLMN1 is the Home PLMN of UE1 , but UE1 is visiting PLMN3; PLMN2 is the Home PLMN of UE2, but UE2 is visiting PLMN3. Based on different scenarios, any of PLMN1 / PLMN2 / PLMN3 might be same or different PLMNs each other. GMLC1 and GMLC2 are examples of the first network device 205 and the second network device 210, respectively.

[0094] At Step 1 , AF wants to get the distance between UE1 and UE2. AF sends position request i.e. SL- MT-LR to GMLC of UETs HPLMN i.e. GMLC1 and provides application Layer IDs of both UEs.

[0095] At Step2: GMLC1 obtains GPSI of UE1 (if not provided in stepl) from UDR via NEF in PLMN1. GMLC1 checks the privacy profile of UE1 from its Home UDM1 .

[0096] At Step3: GMLC1 determines the home PLMN of UE2 based application layer ID of UE2. GMLC1 may has local configuration to map the Application layer ID of the UE2 to PLMN info of the UE2 or GPSI of the UE2. GMLC1 may query the AF to get mapping of the Application layer ID of the UE2 to PLMN info of the UE2 or GPSI of the UE2. If GPSI of UE2 is not available from above steps but only PLMN info (i.e. PLMN2) of UE2 is available, GMLC1 sends a request to GMLC2 (GMLC2 preferred, but could be other NFs e.g. NEF) of PLMN2 to ask for mapping of Application layer ID of UE2 to GPSI; GMLC2 obtains mapping of Application layer ID of UE2 to GPSI from UDR via NEF in PLMN2 and provides GPSI of UE2 back to GMLC1. Further, GMLC1 sends a request to GMLC2 to check privacy of UE2, using the obtained UE2 ID (e.g. GPSI). GMLC2 checks the privacy profile of UE2 from UDM2 in PLMN2.

[0097] At Step4, if GPSI of UE2 is obtained and privacy check of UE2 is OK, GMLC1 proceeds SL-MT-LR procedure and sends the requests to vGMLC in the serving PLMN (PLMN3), with GPSI and Application layer ID of UE1 and UE2 to proceed the SL-MT-LR procedure.

[0098] At Step5, vGMLC now can execute position request.

[0099] FIG. 3C shows a flowchart of an example SL-MO-LR process 315 without GPSI provided in accordance with some embodiments of the present disclosure.

[0100] In this example, the preconditions are as follows: PLMN1 is the Home PLMN of UE1 , but UE1 is visiting PLMN3; PLMN2 is the Home PLMN of UE2, but UE2 is visiting PLMN3. Based on different scenarios, any of PLMN1 / PLMN2 / PLMN3 might be same or different PLMNs each other. UE1 -UEn are able to provide the application layer IDs of each other, (i.e. UE1 -UEn to provide GPSI of each other is not considered inthis Ivd)

[0101] Step 1 : UE1 wants to get the distance between UE1 and UE2. UE1 sends position request to AMF of UE1 's serving AMF and LMF to trigger SL-MO-LR procedure. UE1 provides application layer IDs of both UEs.

[0102] Step2: During SL-MO-LR, LMF can determine to retrieve the location of the UE2 locally or triggers 5GC-MT-LR procedure to the GMLC of UE2's PLMN to acquire the absolute location of the UE2. LMF may send the request to GMLC in the PLMN3 (i.e. GMLC within its own PLMN). If vGMLC is not deployed, the following procedure performed by vGMLC can be performed by LMF.

[0103] Step3: vGMLC (as an example implementation of the first network device 205) determines the home PLMN of UE2 based application layer ID of UE2. vGMLC may has local configuration to map the Application layer ID of the UE2 to PLMN info of the UEs or GPSI of the UE2. vGMLC may query the AF (as an example implementation of the second network device 205) to get mapping of the Application layer ID of the UE2 to PLMN info of the UE or GPSI of the UE2. GMLC1 sends a request to NF (GMLC2 preferred, but could be other NF e.g. NEF, as another example implementation of the second network device 205) of PLMN2 to ask for mapping of Application layer ID of UE2 to GPSI; GMLC2 obtains mapping of Application layer ID of UE2 to GPSI from UDR via NEF in PLMN2. Further, GMLC1 sends a request to GMLC2 to check privacy of UE2, using the obtained UE2 ID (e.g. GPSI). GMLC2 checks the privacy profile of2 from its Home UDM2

[0104] Step4: If GPSI of UE2 is not available from above steps but only PLMN info (i.e, PLMN2) of UE2 is available, vGMLC sends Position request to GMLC2 of PLMN2 with UE2 ID ie. application layer ID. If GPSI of UE2 is obtained, vGMLC sends Position request to GMLC2 of PLMN2 with UE2 ID ie. GPSI and / or application layer ID.

[0105] Step5: GMLC2 now can execute MT-LT procedure for UE2.

[0106] In the SL-MO-LR process 315, if mapping of Application Layer ID to GPSI is not available for any of these Located UE(s), the UE(s) is considered as roaming UE. The (V)GMLC either uses local configuration to get home PLMN ID of the roaming UE(s) or retrieve the information from AF. The (V)GMLC triggers 5GC- MT-LR procedure to the home GMLC of each of these roaming Located UE(s) to acquire the absolute location of the UE(s) which may be considered as an example implementation of the information of UE.

[0107] If vGMLC is not deployed, the following procedure performed by vGMLC can be performed by LMF. In this case, LMF may be considered as an example implementation of the first network device 205.

[0108] FIG. 4 shows a flowchart of an example method 400 of SL positioning in accordance with some embodiments of the present disclosure. The method 400 may be implemented by the first network device 205 as shown in FIG. 2. For the purpose of discussion, the method 400 will be described from the perspective of the first network device 205.

[0109] As shown in FIG. 4, at block 410, the first network device receives a first request for positioning of a first terminal device with respect to a second terminal device, where the first request includes a first identifier of the second terminal device. At block 420, the first network device obtains information of the second terminal device based on the first identifier of the second terminal device, where the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device. At block 430, the first network device causes, based on the information of the second terminal device, the positioning of the first terminal device to be performed.

[0110] In an example, the first identifier comprises one of an application layer identifier, a generic public subscription identifier and a public land mobile network information. The second identifier comprises a different one of the application layer identifier, the generic public subscription identifier and the public land mobile network information.

[0111] In an example, the first network device comprises at least one of: a network device in a first home network of the first terminal device, a network device in a visiting network of both the first and second terminal devices, or a location server associated with the positioning of the first terminal device.

[0112] In an example, the information comprises the second identifier of the second terminal device. The first network device determines the second identifier of the second terminal device from the first identifier of the second terminal device based on mapping between the first identifier of the second terminal device and the second identifier of the second terminal device.

[0113] In an example, the first network device transmits, to a second network device, a second request for the information of the second terminal device, where the second request includes the first identifier of the second terminal device; and receives, from the second network device, the information of the second terminal device.

[0114] In an example, the information comprises the second identifier of the second terminal device. The second request comprises a request for mapping of the first identifier of the second terminal device to the second identifier of the second terminal device.

[0115] In an example, the information comprises the result of the privacy check of the second terminal device. In an example, the second request comprises a request for the privacy check of the second terminal device.

[0116] In an example, the first network device determines the second network device based on the first identifier of the second terminal device.

[0117] In an example, the second network device comprises at least one of: a network device in a second home network of the second terminal device, an application server associated with the positioning of the first terminal device.

[0118] In an example, the first network device transmits, to a third network device, a third request for the positioning of the first terminal device.

[0119] In an example, the third network device comprises at least one of: a network device in a visiting network of both the first terminal device and the second terminal device, or a network device in a second home network of the second terminal device.

[0120] In an example, the first request is received from an application function associated with the positioning of the first terminal device.

[0121] FIG. 5 shows a flowchart of an example method 500 of SL positioning in accordance with some embodiments of the present disclosure. The method 500 may be implemented by the second network device 210 as shown in FIG. 2. For the purpose of discussion, the method 500 will be described from the perspective of the second network device 210.

[0122] As shown in FIG. 5, at block 510, the second network device receives, from a first network device, a second request for information of a second terminal device. The second request includes the first identifier of the second terminal device. At block 520, the second network device obtains the information of the second terminal device based on the first identifier of the second terminal device. The information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device. At block 530, the second network device transmits, to the first network device, the information of the second terminal device.

[0123] In an example, the first identifier comprises at least one identifier of an application layer identifier, a generic public subscription identifier and a public land mobile network information. In an example, the second identifier comprises at least one further identifier of the application layer identifier, the generic public subscription identifier and the public land mobile network information.

[0124] In an example, the information comprises the second identifier of the second terminal device. In an example, the second network device determines mapping between the first identifier of the second terminal device and the second identifier of the second terminal device. The second network device determines the second identifier of the second terminal device from the first identifier of the second terminal device based on the mapping between the first identifier of the second terminal device and the second identifier of the second terminal device.

[0125] In an example, the information comprises the result of the privacy check of the second terminal device. In an example, the second network device performs the privacy check of the second terminal device to obtain the result of the privacy check of the second terminal device.

[0126] In an example, the first network device comprises at least one of: a network device in a first home network of the first terminal device, a network device in a visiting network of both the first and second terminal devices, or a location server associated with the positioning of the first terminal device.

[0127] In an example, the second network device comprises at least one of: a network device in a second home network of the second terminal device, an application server associated with the positioning of the first terminal device.

[0128] All operations and features related to the first network device 205 and the second network device 210 as described above with reference to FIG. 2 are likewise applicable to the methods 400 and 500 and have similar effects. For the purpose of simplification, the details will be omitted.

[0129] FIG. 6 shows function units of a first network device 600 in accordance with some embodiments of the present disclosure.

[0130] As shown in FIG. 6, the first network device 600 comprises a receiving unit 610 configured to receive a first request for positioning of a first terminal device with respect to a second terminal device, wherein the first request includes a first identifier of the second terminal device . The first network device 600 comprises an obtaining unit 620 configured to obtain information of the second terminal device based on the first identifier of the second terminal device, wherein the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device. The first network device 700 further comprises a positioning unit 630 configured to cause, based on the information of the second terminal device, the positioning of the first terminal device to be performed.

[0131] In some embodiments, the first network device 600 may further comprise units for implementing actions or operations according to any of the above-mentioned embodiments described with reference to FIG. 2 and 3.

[0132] FIG. 7 shows function units of a second network device 700 in accordance with some embodiments of the present disclosure.

[0133] As shown in FIG. 7, the second network device 700 comprises a receiving unit 710 configured to receive, from a first network device, a second request for information of a second terminal device, wherein the second request includes the first identifier of the second terminal device; an obtaining unit 720 configured to obtain the information of the second terminal device based on the first identifier of the second terminal device, wherein the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device; and a transmitting unit 730 configured to transmit, to the first network device, the information of the second terminal device.

[0134] In some embodiments, the second network device 700 may further comprise units for implementing actions or operations according to any of the above-mentioned embodiments described with reference to FIG. 2 and 4.

[0135] FIG. 8 shows a communication device 800 in accordance with some embodiments of the present disclosure.

[0136] As shown in FIG. 8, the communication device 800 may comprise a memory 810 containing instructions 815. The communication device 800 may further comprise a processor 805 that executes the instructions 815 to implement actions or operations according to any of the above-mentioned embodiments described with reference to FIGS. 2 to 5.

[0137] In some embodiments, the communication 800 may operate as a first network node. In these embodiments, the communication device 800 may be operative to: receive a first request for positioning of a first terminal device with respect to a second terminal device, wherein the first request includes a first identifier of the second terminal device; obtain information of the second terminal device based on the f irst identifier of the second terminal device, wherein the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device; and cause, based on the information of the second terminal device, the positioning of the first terminal device to be performed.

[0138] In some embodiments, the communication 800 may operate as a second network node. In these embodiments, the communication device 800 may be operative to: receive, from a first network device, a second request for information of a second terminal device, wherein the second request includes the first identifier of the second terminal device; obtain the information of the second terminal device based on the first identifier of the second terminal device, wherein the information of the second terminal device comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device; and transmit, to the first network device, the information of the second terminal device.

[0139] Processor 805 may include one or more processors, which may be any kind of processing component, such as one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. If processor 805 includes multiple processors, one of these processors may execute all the steps described with reference to FIGS. 2 to 5, or some of these processors may execute part of the steps and other processors execute other step(s). Memory 810 may be any kind of storage component, such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.

[0140] FIG. 9 shows a computer readable storage medium in accordance with some embodiments.

[0141] As shown in FIG. 9, the computer readable storage medium 900 comprising instructions 815 which when executed by a processor system of a device, the processor system may comprise one or more processors to perform any above-mentioned embodiments described with reference to FIGS. 2 to 5 by any combination of the processors.

[0142] The computer readable storage medium 900 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppydisks, hard disks, removable cartridges, or flash drives.

[0143] In some embodiments, an apparatus capable of performing the method 400 or 500 may comprise means for performing the respective operations of the method 400 or 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.Example System

[0144] FIG. 10 shows an example of a communication system 1000 in accordance with some embodiments.

[0145] In the example, the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010a and 1010b (one or more of which may be generally referred to as network nodes 1010), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1002 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1002 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1002, including one or more network nodes 1010 and / or core network nodes 1008.

[0146] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O- DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O- CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective "open" designating support of an ORAN specification) . The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1010 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1012a, 1012b, 1012c, and 1012d (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.

[0147] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1000 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0148] The UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1010 and other communication devices. Similarly, the network nodes 1010 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1012 and / or with other network nodes or equipment in the telecommunication network 1002 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1002.

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

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

[0151] As a whole, the communication system 1000 of FIG. 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) Zig Bee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0152] In some examples, the telecommunication network 1002 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1002. For example, the telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

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

[0154] In the example, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and / or 1012d) and network nodes (e.g., network node 1010b). In some examples, the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs. As another example, the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1010, or by executable code, script, process, or other instructions in the hub 1014. As another example, the hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, whichthe hub 1014 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1014 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0155] The hub 1014 may have a constant / persistent or intermittent connection to the network node 1010b. The hub 1014 may also allow for a different communication scheme and / or schedule between the hub 1014 and UEs (e.g., UE 1012c and / or 1012d), and between the hub 1014 and the core network 1006. In other examples, the hub 1014 is connected to the core network 1006 and / or one or more UEs via a wired connection. Moreover, the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection. In some embodiments, the hub 1014 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1010b. In other embodiments, the hub 1014 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1010b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0156] FIG. 11 shows a UE 1100 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehiclemounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0158] The UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1 104 to an input / output interface 1106, a power source 1108, a memory 1110, a communication interface 1112, and / orany other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

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

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

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

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

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

[0166] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1112, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0167] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

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

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

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

[0171] FIG. 12 shows a network node 1200 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

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

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

[0174] The network node 1200 includes a processing circuitry 1202, a memory 1204, a communication interface 1206, and a power source 1208. The network node 1200 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1200 comprises multiple separate components (e.g., BTS and BSC components), one ormore of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1200 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1200.

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

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

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

[0178] The communication interface 1206 is used in wired or wireless communication of signaling and / ordata between a network node, access network, and / or UE. As illustrated, the communication interface 1206 comprises port(s) / terminal(s) 1216 to send and receive data, for example to and from a network over a wired connection. The communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222. The radio front-end circuitry 1218 may be connected to an antenna 1210 and processing circuitry 1202. The radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202. The radio front-end circuitry 1218 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and / or amplifiers 1222. The radio signal may then be transmitted via the antenna 1210. Similarly, when receiving data, the antenna 1210 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1218. The digital data may be passed to the processing circuitry 1202. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0179] In certain alternative embodiments, the network node 1200 does not include separate radio frontend circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206. In still other embodiments, the communication interface 1206 includes one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).

[0180] The antenna 1210 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1210 may be coupled to the radio front-end circuitry 1218 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1210 is separate from the network node 1200 and connectable to the network node 1200 through an interface or port.

[0181] The antenna 1210, communication interface 1206, and / or the processing circuitry 1202 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1210, the communication interface 1206, and / or the processing circuitry 1202 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

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

[0183] Embodiments of the network node 1200 may include additional components beyond those shown in FIG. 12 for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1200 may include user interface equipment to allow input of information into the network node 1200 and to allow output of information from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1200.

[0184] FIG. 13 is a block diagram of a host 1300, which may be an embodiment of the host 1016 of FIG. 10, in accordance with various aspects described herein. As used herein, the host 1300 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud- implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1300 may provide one or more services to one or more UEs.

[0185] The host 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input / output interface 1306, a network interface 1308, a power source 1310, and a memory 1312. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.

[0186] The memory 1312 may include one or more computer programs including one or more host application programs 1314 and data 1316, which may include user data, e.g., data generated by a UE for the host 1300 or data generated by the host 1300 for a UE. Embodiments of the host 1300 may utilize only a subset or all of the components shown. The host application programs 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, headsup display systems). The host application programs 1314 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, s uchas a device in or on the edge of a core network. Accordingly, the host 1300 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1314 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real- Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0187] FIG. 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

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

[0190] The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0191] In the context of NFV, a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one o r more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.

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

[0193] FIG. 15 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1012a of FIG. 10 and / or UE 1100 of FIG. 11), network node (such as network node 1010a of FIG. 10 and / or network node 1200 of FIG. 12), and host (such as host 1016 of FIG. 10 and / or host 1300 of FIG. 13) discussed in the preceding paragraphs will now be described with reference to FIG. 15.

[0194] Like host 1300, embodiments of host 1502 include hardware, such as a communication interface, processing circuitry, and memory. The host 1502 also includes software, which is stored in or accessible by the host 1502 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1506 connecting via an over-the- top (OTT) connection 1550 extending between the UE 1506 and host 1502. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1550.

[0195] The network node 1504 includes hardware enabling it to communicate with the host 1502 and UE 1506. The connection 1560 may be direct or pass through a core network (like core network 1006 of FIG. 10) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0196] The UE 1506 includes hardware and software, which is stored in or accessible by UE 1506 and executable by the UE's processing circuitry. The software includes a client application, such as a webbrowser or operator-specific "app" that may be operable to provide a service to a human or non -human user via UE 1506 with the support of the host 1502. In the host 1502, an executing host application may communicate with the executing client application via the OTT connection 1550 terminating at the UE 1506 and host 1502. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1550 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1550.

[0197] The OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide the connection between the host 1502 and the UE 1506. The connection 1560 and wireless connection 1570, over which the OTT connection 1550 may be provided, have been drawn abstractly to illustrate the communication between the host 1502 and the UE 1506 via the network node 1504, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0198] As an example of transmitting data via the OTT connection 1550, in step 1508, the host 1502 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1506. In other embodiments, the user data is associated with a UE 1506 that shares data with the host 1502 without explicit human interaction. In step 1510, the host 1502 initiates a transmission carrying the user data towards the UE 1506. The host 1502 may initiate the transmission responsive to a request transmitted by the UE 1506. The request may be caused by human interaction with the UE 1506 or by operation of the client appli cation executing on the UE 1506. The transmission may pass via the network node 1504, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1512, the network node 1504 transmits to the UE 1506 the user data that was carried in the transmission that the host 1502 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1514, the UE 1506 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1506 associated with the host application executed by the host 1502.

[0199] In some examples, the UE 1506 executes a client application which provides user data to the host 1502. The user data may be provided in reaction or response to the data received from the host 1502. Accordingly, in step 1516, the UE 1506 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1506. Regardless of the specific manner in which the user data was provided, the UE 1506 initiates, in step 1518, transmission of the user data towards the host 1502 via the network node 1504. In step 1520, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1504 receives user data from the UE 1506 and initiates transmission of the received user data towards the host 1502. In step 1522, the host 1502 receives the user data carried in the transmission initiated by the UE 1506.

[0200] One or more of the various embodiments improve the performance of OTT services provided to the UE 1506 using the OTT connection 1550, in which the wireless connection 1570 forms the last segment.

[0201] In an example scenario, factory status information may be collected and analyzed by the host 1502. As another example, the host 1502 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1502 may collect and analyze real -time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1502 may store surveillance video uploaded by a UE. As another example, the host 1502 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1502 may be used for energy pricing, remote control of non -time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0202] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1550 between the host 1502 and UE 1506, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1502 and / or UE 1506. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1504. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1502. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1550 while monitoring propagation times, errors, etc.

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

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

[0205] Hereinafter, the solution will be further described with reference to text of contribution to be submitted to 3GPP TS 23.586 as follows. It is noted that some changes are highlighted with underline.Reason for change

[0206] It was decided that roaming is supported in this release in a way the UEs involved in ranging must be served by the same PLMN but they can belong to different PLMNs. However it was not described how the GPSI and Application Layer ID translation works if UEs belong to different PLMN.

[0207] If GMLC receives the GPSI of UEs belong to different PLMN, the trasnlation is not possible by (H)GMLC, then (H)GMLC shall query Application Layer ID from the Home GMLC of UEs.

[0208] Additonally, if the UE's Home PLMN is different, then (H)GMLC needs to send a request to the Home GMLC of the UE to check the UE LCS privacy profile.Summary of change

[0209] Adding to GMLC functionality the interaction with Home GMLC for ID translation and for privacy check.Conseguences if not approved

[0210] Incomplete solution and specification address scenario when UEs are from different PLMN.4.2.5 Service-based interfacesNlmf: In addition to the relevant services defined in TS 23.273 [8], if the LMF support Ranging / SLPositioning service, it may be used to provide service to other NFs related to it.Ngmlc: In addition to the relevant services defined in TS 23.273 [8], if the GMLC support Ranging / SL Positioning service, it may be used to get the location of Located UE / Reference UE from GMLC using the Application Layer ID in case of Sidelink Positioning and Ranging oper- ation, and it may be used for UEs belong to different PLMN to get the mapping between Application Layer ID and GPSI and check Privacy Profile of those UEs.Nudm: In addition to the relevant services defined in TS 23.501 [2] for Nudm, in the case of Ranging / SL Positioning service, services provided by UDM are used to get the related subscription information to AMF during Initial registration procedure or UE Configuration Update (UCU) procedure to inform AMF subscription information has changed.Npcf: In addition to the relevant services defined in TS 23.501 [2] for Npcf, in the case of Ranging / SL Positioning service, services provided by H-PCF are used to provide SL Positioning and Ranging Service related parameters to V-PCF for UE and NG-RAN in the roaming case.Nudr: In addition to the relevant services defined in TS 23.501 [2] for Nudr, in the case of Ranging / SL Positioning service, services provided by UDR are used to notify the PCF and the UDM of the update of the SL Positioning and Ranging-based service related information.Namf: In addition to the relevant services defined in TS 23.501 [2] for Namf, in the case of Ranging / SL Positioning service, services provided by AMF are consumed by PCF to provide the Ranging / SL Positioning service related parameters for the UE and the NG-RAN to AMF, and to enable the AMF create or update UE context related to Ranging / SL Positioning service.Nnef: In addition to the relevant services defined in TS 23.501 [2] for Nnef, in the case of Ranging / SL Positioning service, services provided by NEF are used by the Application Server to update Ranging / SL Positioning service related information of 5GC.Nnrf: In addition to the relevant services defined in TS 23.501 [2] for Nnrf, in the case of Ranging / SL Positioning service, services provided by NRF are used to discover the PCF that supports Ranging / SL Positioning.4.3.9 GMLCIn addition to the functions defined in TS 23.273 [8], the GMLC supports the following:- enable trusted AFs and NFs to perform MT-LR by accessing GMLC directly with additional service parameters for Ranging / SL Positioning.- enable AFs and NFs to perform MT-LR by accessing GMLC through NEF with additional service parameters for Ranging / SL Positioning.- determine the serving AMF instances for the UEs involved in the Ranging / SL Positioning request and forward the request to respective serving AMF. receive response from AMF and event reports from and return Ranging / SL Positioning result to NFs and AFs.- perform Application Layer ID to GPSI or GPSI to Application Layer ID resolution by querying NEF.- contact Home GMLC of the UE(s) that belong to different PLMN(s) to retrieve the mapping between GPSI and Application Laver ID (if needed) and trigger privacy check for the UE(s).

[0211] Hereinafter, the solution will be further described with reference to text of contribution to be submitted to 3GPP TS 23.273 as follows. It is noted that some changes are highlighted with underline.Reason for change

[0212] It was decided that roaming is supported in this release in a way the UEs involved in ranging must be served by the same PLMN but they can belong to different PLMNs. However it was not described how the GPSI and Application Layer ID translation works if UEs belong to different PLMNs.

[0213] In case of SL-MT-LR, If GMLC receives the GPSI of UEs belong to a different PLMN and the trasnlation is not possible by (H)GMLC then (H)GMLC shall query Application Layer ID from the Home GMLC of UEs. Additonally, if the UE's Home PLMN is different then (H)GMLC needs to send a request to the Home GMLC of UE to check the UE LCS privacy profile.

[0214] In case of SL-MO-LR, when Application ID of UE is avalaible only then (V)GMLC either uses local configuration to get home PLMN ID of the roaming UE(s) or retrieve the information from AF.Summary of change

[0215] Adding logic if any UE belongs to another PLMN then (H)GMLC may send a request to Home GMLC of UE to make ID translation and to check LCS privacy data.Conseguences if not approved

[0216] Incomplete solution and specification address scenario when UEs are from different PLMN .6.20.3 Procedures of SL-MT-LR involving LMFThe SL-MT-LR procedure is used to estimate the relative locations or distances and / or directions between the UEs.Figure 6.20.3-1 illustrates a procedure to enable an LCS Client or AF to obtain Ranging / Sidelink Positioning location results for a group of n UEs (n>2), i.e. UE1, UE2, .... UEn. In the procedure, the GMLC determines a UE among the n UEs to be designated UE1 (i.e. Target UE in TS 23.586

[0040] ) and one or more other UEs designated UE2, UE3, .... UEn (n>2) (i.e. Reference / Located UEs in TS 23.586

[0040] ). The Ranging / Sidelink Positioning location results may include absolute locations, relative locations or ranges and directions related to the UEs, based on the service request.Procedure for periodic and triggered SL-MT-LR is defined in clause 6.20.4.Figure 6.20.3-1 : SL-MT-LR ProcedurePrecondition: At least one of the n UEs is in coverage and registered with a serving PLMN.1 . The LCS Client or the AF (via NEF) sends an LCS service request to the (H)GMLC for Ranging / Sidelink Positioning location results for the n UEs which may each be identified by an Application Layer ID, and / or a GPSI and / or a SUPI. The request may include the required QoS, the required location results (e.g. absolute locations, relative locations or distances and / or directions related to the UEs), the SL reference UE(s) in case of relative locations, distance, or direction. The (H)GMLC or NEF authorizes the LCS Client or the AF for the usage of the LCS service. If the authorization fails, the remaining steps are skipped and the (H)GMLC or NEF responds to the LCS Client or the AF with the failure of the service authorization.In addition, an Application Layer ID shall be used for each of the n UEs to enable discovery of the UEs at step 12. If only GPSI is provided to the (H)GMLC, it can query the NEF for the mapping Application Layer ID as specified in clause 4.3.9 of TS 23.586

[0040] . If any of the n UEs belongs to another PLMN, then (H)GMLC may send a request to the Home GMLC of each of those UEs to retrieve the mapping between Application Laver ID and GPSI (?). The Home GMLC of each of those UEs queries the NEF in its own PLMN for the mapping Application Laver ID as specified in clause 4.3.9 of TS 23.586

[0040] and send back the mapping Application Laver ID to (H)GMLC.Editor's note: Whether Application Layer ID will be included in LPP operation is FFS and needs the coordination with RAN WGs.2. The (H)GMLC invokes a Nudm_SDM_Get service operation towards the UDM of each of the n UEs to get the privacy settings of the UE identified by its GPSI or SUPI. The UDM returns the UE Privacy setting of the UE. The (H)GMLC checks the UE LCS privacy profile. If any of the n UEs belong to another PLMN, then (H)GMLC sends a request to the Home GMLC of each of those UEs to check the LCS privacy profile of those UE(s) identified by GPSI or SUPI. The Home GMLC of each of those UEs queries the UDM in its own PLMN via Nudm SDM Get service operation to get the privacy settings of the UE and sends back the privacy check result to (H)GMLC.3. The (H)GMLC invokes a Nudm_UECM_Get service operation towards the UDM of each of the n UEs (for which GPSI or SUPI is available), one at a time, using the GPSI or SUPI of each UE. The (H)GMLC selects the UE (e.g. which is treated as UE1 in following steps) that initiates the Ranging / SL Positioning and selects the corresponding serving AMF.NOTE: The UDM is aware of the serving AMF address at UE registration on an AMF as defined in clause 4.2.2.2.2 of TS 23.502

[0019] , The UDM is aware of a serving (V)GMLC address at UE registration on an AMF as defined in clause 4.2.2.2.2 of TS 23.502

[0019] ,4. For a non-roaming case, this step is skipped. In the case of roaming, the (H)GMLC may receive an address of a (V)GMLC (together with the network address of the current serving AMF) from the UDM in step 3, otherwise, the (H)GMLC may use the NRF service in the (H)PLMN to select an available (V)GMLC in the (V)PLMN, based on the (V)PLMN identification contained in the AMF address received in step 3. The (H)GMLC then sends the location request to the (V)GMLC by invoking the Ngmlc_Location_Provide- Location service operation towards the (V)GMLC. In the cases when the (H)GMLC did not receive the address of the (V)GMLC, or when the (V)GMLC address is the same as the (H)GMLC address, or when both PLMN operators agree, the (H)GMLC sends the location service request message to the serving AMF. In this case, step 4 is skipped. The (H)-GMLC also provides the LCS client type of AF, if received in step 1, or LCS client type of LCS client and other attributes to be sent to AMF in step 5.5. In the case of roaming, the (V)GMLC first authorizes that the location request is allowed from this (H)GMLC, PLMN or from this country. If not, an error response is returned. The (H)GMLC or (V)GMLC invokes the Namf_Location_ProvidePositioninglnfo service operation towards the AMF serving UE1 to request Sidelink positioning / ranging location results of the n UEs. The service operation includes the SUPI of UE1, Application layer IDs of the UEs, the client type and may include the required LCS QoS, the required location results (e.g. relative locations or ranges and directions related to the UEs) and other attributes as received or determined in step 1 .6. If UE1 is in CM-IDLE state, the AMF initiates a network triggered Service Request procedure to establish a signalling connection with UE1.If signalling connection establishment fails, steps 7-17 are skipped.7-8. If the indicator of privacy check indicates an action is needed, then same operation as that of step 7-8 of clause 6.1 .2 is carried out.9. The serving AMF selects an LMF serving UE1 (e.g. an LMF that supports Ranging / Sidelink Positioning) and sends an Nlmf_Location_DetermineLocation service operation towards the LMF with the information received at step 5 e.g. required location results (e.g. relative locations or ranges and directions between pairs of UEs), SL reference UE(s) in case of relative locations, Application layer IDs of the UEs if received in step 5. The service operation includes a LCS Correlation identifier.10. The LMF sends an SL-MT-LR request to the serving AMF as a supplementary services message, using the Namf_Communication_N1 N2MessageTransfer service operation, and the session ID parameter is set to the LCS Correlation identifier.The SL-MT-LR request may include the application layer IDs of the other UEs 2 to n, the types of requiredlocation results (e.g. relative locations or distances and / or directions) and SL reference UE(s) in case of relative locations.Editor's note: Whether supplementary services message or Ipp will be sent from LMF to UE is FFS and needs the coordination with RAN WGs.11. The serving AMF forwards the SL-MT-LR request and a Routing identifier equal to the LCS Correlation identifier to UE1 using a DL NAS TRANSPORT message.12. UE1 attempts to discover the other UE 2 to n using their Application Layer IDs if not already discovered using procedure defined in clause 6.4 of TS 23.586

[0040] ,13. UE1 obtains the sidelink positioning capabilities of the discovered UEs via the SLPP if not already obtained.14. UE1 returns a supplementary services SL-MT-LR response to the serving AMF in an UL NAS TRANSPORT message and includes the Routing identifier received in step 11 .The SL-MT-LR response indicates which of UEs 2 to n have been discovered and the sidelink positioning capabilities of the discovered UEs.15. The serving AMF forwards the SL-MT-LR response to the LMF indicated by the Routing identifier received at step 14 and includes a LCS Correlation identifier equal to the Routing identifier.16. Ranging / Sidelink Positioning of UE1 and the other discovered UEs occurs as for an SL-MO-LR as described for steps 10-19 of Figure 6.20.1-1 with the difference that Ranging / Sidelink Positioning location measurement data or results are always returned to the LMF and the LMF indicates to UE1 at step 13 or step 14 of Figure 6.20.1-1 whether the Ranging / Sidelink Positioning location results will be calculated by the LMF (at step 19) or by UE1 (at step 17). For some undiscovered UEs among the other UEs 2 to n, the LMF interacts with GMLC to initiate the 5GC-MT-LR procedure using Application Laver ID for UE2 to n to get their absolute locations, and calculates the relative locations or distances and / or directions related to the UEs.17-20. The LMF returns the Sidelink positioning / ranging location results to the LCS Client or AF as in steps 13-15 and step 24 of clause 6.1.2. The results also include failure information of the UE(s) that was not discovered.6.20.1 Procedures of SL-MO-LR involving LMFFigure 6.20.1-1 illustrates a procedure to enable a UE to obtain Sidelink positioning / ranging location results using one or more other UEs with the assistance of an LMF in a serving PLMN for UE1 .The Ranging / SL Positioning location results may include absolute locations, relative locations or distances and directions, depending on the service request.If the Target UE decides to initiate SL-MO-LR procedure, it includes one or multiple SL reference UE(s) I Located UE (s) in the service request. See TS 23.586

[0040] for more information on how this generic procedure can be used.Figure 6.20.1-1: SL-MO-LR ProcedurePrecondition: UE1 is in coverage and registered with a serving PLMN. UEs 2 to n may or may not be in coverage and, if in coverage, may or may not be registered with the same serving PLMN as UE1.1 . The procedures and signalling specified in clause 6.2 of TS 23.586

[0040] may be used to provision the Ranging / SL positioning service authorization and policy / parameter provisioning to UEs 1 to n, when in coverage.NOTE 1: If indication of UE-only operation is received, procedures of Ranging / Sidelink Positioning control as defined in clause 6.8 of TS 23.586

[0040] is performed.2. Based on a trigger of service request (e.g. received from the application layer), which includes UE1 / . ,, / UEn, UE discovery is performed for Ranging / SL positioning as specified in clause 6.4 of TS 23.586

[0040] :- If UE1 is the target UE, UE1 discovers UEs 2 to n- If UE1 is the Located UE, the target UE (i.e. one of the UEs 2 to n) discovers UE1 (and other Located UEs in the set of UEs 2 to n).3. Secure groupcast and / or unicast links are established between UEs 1 to n as defined in clause 5.3 of TS 23.586

[0040] to enable UE1 to exchange Ranging and Sidelink Positioning Protocol (RSPP) messages over PC5-U reference point with each of UEs 2 to n and possibly enabling UEs 2 to n to exchange RSPP over PC5-U between each other.Editor's note: Security aspects for RSPP signalling need to be defined or agreed by SA WG3.4. UE1 and UEs 2 to n may communicate over PC5 for authorization of Ranging / SL positioning and receiving QoS parameters if needed. Each of UEs verifies that Ranging / SL positioning is permitted, including whether Ranging / SL positioning results may be transferred to an LCS Client or AF if this is used, according to any service authorization and policy / parameter provisioning received at step 1 . QoS requirements for the Ranging / SL positioning may be also provided based on QoS requirements in the service request.5. UE1 may obtain the Sidelink positioning capabilities of UEs 2 to n using the groupcast and / or unicast links established in step 3.Step 4 and 5 may be performed to transfer the information of UEs which are not served by the LMF.NOTE 2: UE2 / ... / UEn is not assumed to be served by the same LMF serving UE1.Editor's note: It needs to be verified that RAN2 will provide support for steps 4 and 5.6. Based on the Sidelink positioning capabilities of UE1 / . ,, / UEn, the target UE determines SL-MO-LR is to be performed. If UE1 is the Located UE (i.e. when the target UE is one of UE2 / ... / UEn and does not have NAS connection), the target UE initiates SL-MO-LR service request to UE1.7. If UE1 is in CM-IDLE state, UE1 instigates a UE triggered Service Request in order to establish a signalling connection with the serving AMF of UE1.8. UE1 sends a supplementary services SL-MO-LR request to the serving AMF in an UL NAS TRANSPORT message. The SL-MO-LR request indicates the other UEs 2 to n (using application layer ID), indicates any assistance data needed, indicates whether location calculation assistance is needed, and indicates whether location results should be transferred to an LCS client or AF. The message shall include the identity of the LCS client or the AF and may include the address of the GMLC through which the LCS client or AF (via NEF) should be accessed. In addition, a Service Type indicates which MO-LR service of the LCS Client is requested by the UE may be included. For location calculation assistance from the LMF, the preferred type of Sidelink positioning / ranging location results (e.g. absolute locations, relative locations or distances and directions between pairs of UEs) and the required QoS are included. If UE1 is Located UE andone of UE2 / ... / UEn is the target UE that does not have NAS connection, the supplementary services SL- MO-LR request includes an indication that one of UE2 / ... / UEn is the target UE instead of UE1.Editor's note: It is FFS whether indication about the need of assistance data from UE, which will be aligned with RAN WGs.9. The serving AMF selects an LMF serving UE1 (e.g. an LMF that supports Sidelink positioning / ranging) and sends an Nlmf_Location_DetermineLocation service operation towards the LMF with the information from the SL-MO-LR Request. The service operation includes a LCS Correlation identifier.10. The LMF sends a request to UE1 for the capabilities of UEs 1 to n.NOTE 3: UE2 / ... / UEn is not assumed to be served by the same LMF serving UE1.Editor's note: It is FFS the update when the LMF also serves UE2 / ... / UEn with alignment with RAN.11. UE 1 returns its capabilities to the LMF. UE1 may additionally return the capabilities of the UEs obtained at step 5 if requested by the LMF at step 10.12. UE1 may send a request for specific assistance data to the LMF.13. LMF sends the requested assistance data to UE1, and UE1 forwards the assistance data received from LMF to UE2 / ... / UEn. The assistance data may assist UEs 1 to n to obtain Sidelink location measurements at step 15 and / or may assist UE1 to calculate Sidelink positioning / ranging location results at step 16.NOTE 4: Steps 10 and 11 can be omitted if UE1 includes a message containing the capabilities of UEs 1 to n in the SL-MO-LR request at step 8. Step 12 can be omitted if UE1 includes a message containing the request for specific assistance data in the SL-MO-LR request at step 8.Editor's note: Whether step 10-11 are needed will be aligned with RAN WGs.14. If the SL-MO-LR request at step 8 indicated location calculation assistance is needed and / or indicated transfer of Sidelink positioning / ranging location results to an LCS Client or AF, the LMF sends a request for location information to UE1 and may also send a request for location information to UE2 / ... / UEn if it is served by the LMF. If LMF determines to apply UE based SL Positioning, LMF includes in the request the indication of UE based SL Positioning. LMF may also provide the list of candidate Located UE(s), if absolute location is requested at step 8. If scheduled location time is received at step 14. LMF may include a scheduled location time.Editor's note: It needs to be aligned with RAN WG2 if the list of candidate Located UE(s) is provided in step 13 or step 14.15. UE1 instigates a Sidelink positioning / ranging procedure among UEs 1 to n in which UEs 1 to n obtain Sidelink location measurements and UEs 2 to n transfer their Sidelink location measurements to UE 1 and / or to the LMF (depending on the assistance requested). If scheduled location time is received at step 14, Sidelink positioning / ranging is performed at the scheduled location time.16. If Target UE's absolute location information is required at step 8 and if absolute location of Located UE(s) is not available, the Target UE sends a request to the Located UE(s) to trigger 5GC-MO-LR procedure to let the Located UE(s) acquire their own absolute location. The QoS requirement received at step 8 is included in the request, which is used to derive the QoS for Located UE(s) positioning.17. If LMF determines to use UE based calculation, at least one of UE1 / . ,, / UEn calculates Sidelink positioning / ranging location results based on the Sidelink location measurements obtained at step 15 and possibly using assistance data received at step 13. The Sidelink positioning / ranging location results can include absolute locations, relative locations or ranges and directions related to the UEs 1 to n.18. If UE1 received a request for location information at step 14, UE1 sends a response to the LMF and includes the Sidelink location measurements obtained at step 15, the Sidelink positioning / ranging locationresults obtained at step 17 if step 17 was performed, or Located UE's absolute location obtained at step 16.19. If Target UE's absolute location information is required at step 8 and if absolute location of Located UE(s) is not received at step 18, LMF can either retrieved the location of the Located UE(s) locally or triggers 5GC-MT-LR procedure to the (V)GMLC to acquire the absolute location of the Located UE(s) using Application Layer ID of the Located UE(s). LMF includes the QoS requirement received at step 8 in the request, which is used to derive the QoS for Located UE(s) positioning. If scheduled location time is used, LMF includes the scheduled location time in the request to GMLC. (V)GMLC retrieves the mapping of Application Laver ID to GPSI as specified in clause 4.3.9 of TS 23.586. If mapping of Application Laver ID to GPSI is not available for any of these Located UE(s), the UE(s) is considered as roaming UE. The (V)GMLC either uses local configuration to get home PLMN ID of the roaming UE(s) or retrieve the information from AF. The (V)GMLC triggers 5GC-MT-LR procedure to the home GMLC of each of these roaming Located UE(s) to acguire the absolute location of the UE(s).20. The LMF calculates Sidelink positioning / ranging location results for UEs 1 to n from the Sidelink location measurements received at step 18 and absolute location of Located UE(s) at step 19. The Sidelink positioning / ranging location results can include absolute locations, relative locations or ranges and directions related to the UEs 1 to n, depending on the location request received in step 8.21. The LMF returns an Nlmf_Location_DetermineLocation service operation response to the AMF and includes the Sidelink positioning / ranging location results received at step 18 or calculated at step 20.22. If Sidelink positioning / ranging location results were received at step 21, the AMF performs steps 7-12 of clause 6.2 to send the Sidelink positioning / ranging location results to the GMLC and to an AF or LCS Client if this was requested at step 8. The Sidelink positioning / ranging location results include the identities for the respective UEs 1 to n received at step 8.NOTE 5: Sending location results and global identities for UEs 1 to n to an AF or LCS Client may require privacy verification from UEs 1 to n and / or from the HPLMNs of UEs 1 to n.23. The LMF returns a supplementary services SL-MO-LR response to UE1 in a DL NAS TRANSPORT message and includes any Sidelink positioning / ranging location results calculated at step 20 if step 20 was performed. If UE1 is Located UE, and the target UE is one of the UEs 2 to n and does not have NAS connection, then UE1 may transfer the Sidelink positioning / ranging location results to the target UE.

Claims

WHAT IS CLAIMED IS:

1. A method (400) implemented at a first network device (205), the method (400) comprising: receiving (410) a first request for positioning of a first terminal device (105) with respect to a second terminal device (110), wherein the first request includes a first identifier of the second terminal device (110); obtaining (420) information of the second terminal device (110) based on the first identifier of the second terminal device (110), wherein the information of the second terminal device (110) comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device (110); and sending the information of the second terminal device (110) towards a third network device for the positioning of the first terminal device (105).

2. The method (400) of claim 1 , wherein the first identifier comprises one of an Application Layer identifier (ID), a generic public subscription identifier (GPSI) and a public land mobile network (PLMN) information, and the second identifier comprises a different one of the application layer identifier, the generic public subscription identifier and the public land mobile network information.

3. The method (400) of claim 1 or 2, wherein the first network device (205) comprises at least one of: a network device in a first home network of the first terminal device (105), a network device in a visiting network of both the first and second terminal device (110)s, or a location server associated with the positioning of the first terminal device (105).

4. The method (400) of any of claims 1 -3, wherein the information comprises the second identifier of the second terminal device (110), and obtaining the information of the second terminal device (110) based on the first identifier of the second terminal device (110) comprises: determining the second identifier of the second terminal device (110) from the first identifier of the second terminal device (1 10) based on mapping between the first identifier of the second terminal device(110) and the second identifier of the second terminal device (110).

5. The method (400) of any of claims 1 -3, wherein obtaining the information of the second terminal device (110) based on the first identifier of the second terminal device (110) comprises: transmitting, to a second network device (210), a second request for the information of the second terminal device (110), wherein the second request includes the first identifier of the second terminal device (110); and receiving, from the second network device (210), the information of the second terminal device (1 10).

6. The method (400) of claim 5, wherein the information comprises the second identifier of the second terminal device (110), and the second request comprises a request for mapping of the first identifier of the second terminal device (110) to the second identifier of the second terminal device (110).

7. The method (400) of claim 5, wherein the information comprises the result of the privacy check of the second terminal device (110), and the second request comprises a request for the privacy check of the second terminal device (110).

8. The method (400) of any of claims 5-7, further comprising: determining the second network device (210) based on the first identifier of the second terminal device (110).

9. The method (400) of any of claims 5-8, wherein the second network device (210) comprises at least one of: a network device in a second home network of the second terminal device (110), an application server associated with the positioning of the first terminal device (105).

10. The method (400) of any of claims 1 -9, wherein causing the positioning of the first terminal device(105) to be performed comprises: transmit, to a third network device, a third request for the positioning of the first terminal device (105).

11. The method (400) of claim 10, wherein the third network device comprises at least one of: a network device in a visiting network of both the first terminal device (105) and the second terminal device (110), or a network device in a second home network of the second terminal device (110).

12. The method (400) of any of claims 1 -11 , wherein the first request is received from an application function associated with the positioning of the first terminal device (105).

13. A method (500) implemented at a second network device (210), the method (500) comprising: receiving (510), from a first network device (205), a second request for information of a second terminal device (110), wherein the second request includes the first identifier of the second terminal device (110); obtaining (520) the information of the second terminal device (110) based on the first identifier of the second terminal device (110), wherein the information of the second terminal device (110) comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device (110); and transmitting (530), to the first network device (205), the information of the second terminal device (110).

14. The method (500) of claim 13, wherein the first identifier comprises at least one identifier of an application layer identifier, a generic public subscription identifier and a public land mobile network information, and the second identifier comprises at least one further identifier of the application layer identifier, the generic public subscription identifier and the public land mobile network information.

15. The method (500) of any of claims 13-14, wherein the information comprises the second identifier of the second terminal device (1 10), and obtaining the information of the second terminal device (110) based on the first identifier of the second terminal device (110) comprises:determining mapping between the first identifier of the second terminal device (110) and the second identifier of the second terminal device (110); and determining the second identifier of the second terminal device (110) from the first identifier of the second terminal device (110) based on the mapping between the first identifier of the second terminal device (110) and the second identifier of the second terminal device (110).

16. The method (500) of any of claims 13-15, wherein the information comprises the result of the privacy check of the second terminal device (110), and obtaining the information of the second terminal device (110) based on the first identifier of the second terminal device (110) comprises: perform the privacy check of the second terminal device (110) to obtain the result of the privacy check of the second terminal device (110).

17. The method (500) of any of claims 13-16, wherein the first network device (205) comprises at least one of: a network device in a first home network of the first terminal device (105), a network device in a visiting network of both the first and second terminal device (110)s, or a location server associated with the positioning of the first terminal device (105).

18. The method (500) of any of claims 13-17, wherein the second network device (210) comprises at least one of: a network device in a second home network of the second terminal device (110), an application server associated with the positioning of the first terminal device (105).

19. A first network device (205) comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the first network device (205) is operative to: receive (410) a first request for positioning of a first terminal device (105) with respect to a second terminal device (1 10), wherein the first request includes a first identifier of the second terminaldevice (110); obtain (420) information of the second terminal device (110) based on the first identifier of the second terminal device (110), wherein the information of the second terminal device (110) comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device (110); and sending the information of the second terminal device (110) toward to a third network device for the positioning of the first terminal device (105).

20. The first network device (205) of claim 18, wherein the first network device (205) is further operative to implement the method (400) according to any of claims 2-12.

21. A second network device (210) comprising: a processor; and a memory, the memory containing instructions executable by the processor, whereby the second network device (210) is operative to: receive (510), from a first network device (205), a second request for information of a second terminal device (110), wherein the second request includes the first identifier of the second terminal device (110); obtain (520) the information of the second terminal device (110) based on the first identifier of the second terminal device (110), wherein the information of the second terminal device (110) comprises at least one of a second identifier, a result of a privacy check or a location of the second terminal device (110); and transmit (530), to the first network device (205), the information of the second terminal device (110).

22. The second network device (210) of claim 20, wherein the second network device (210) is further operative to implement the method (500) according to any of claims 14-18.

23. A computer-readable storage medium having instructions stored thereon, the instructions, which,when executed by at least one processor of a device, causes the device to perform the method (400) according to any of claims 1 -12 or the method (500) according to any of claims 13-18.

Images