Enhancement of positioning quality of service

Abstract

Teachings herein improve selection of the positioning method(s) used to obtain positioning information responsive to a positioning request, by approaching positioning QoS holistically. Approached holistically, a joint QoS metric as taught herein takes into account the joint effect of individual QoS parameters of a positioning method, or the joint effect of multiple methods in a sequence. Processing in one or more embodiments thus includes determining a joint QoS metric for each of a plurality of candidate positioning methods or sequences, and selecting a positioning method or sequence based on those joint QoS metrics. By selecting a positioning method or sequence in this way, holistically based on joint QoS metrics rather than a piecemeal approach based on a one-by-one check of individual QoS parameters, selection proceeds flexibly according to actual QoS requirements of position-based services and/or systematically according to the joint effect of multiple positioning methods.

Claims

1. A method implemented by an electronic processing apparatus for responding to a request for a mobile terminal's geographic position, the method comprising: determining a joint quality of service, QoS, metric for each of a plurality of candidate sequences of positioning methods, a joint QoS metric jointly depending on two or more positioning methods in a candidate sequence, wherein determining a joint QoS metric for a candidate sequence that jointly depends on two or more joint QoS metrics comprises preventing a first one of the two or more joint QoS metrics that has better quality from making up for a second one of the two or more joint QoS metrics that has lesser quality; and selecting from said plurality a sequence of positioning methods, for determining the mobile terminal's position responsive to the request, based on said joint QoS metrics.

2. The method of claim 1, wherein determining a joint QoS metric for a candidate sequence comprises determining a joint QoS metric that jointly depends on two or more joint QoS metrics, each of the two or more joint QoS metrics comprising the accumulation of a different individual positioning QoS parameter across the positioning methods in the sequence.

3. The method according to claim 1: further comprising determining a joint QoS metric for the request, the joint QoS metric jointly depending on two or more individual QoS parameters associated with the request; and wherein said selecting comprises selecting based on evaluating the joint QoS metric determined for the request in relation to the joint QoS metric determined for each of said plurality of candidate sequences of positioning methods.

4. The method according to claim 1: further comprising receiving one or more parameters indicative of one or more weighting values; and wherein determining a joint QoS metric for a candidate positioning sequence comprises determining a joint QoS metric that is based on a weighted combination of two or more joint QoS metrics associated with that positioning sequence, the weighting being applied in accordance with the one or more weighting values, each of the two or more joint QoS metrics comprising the accumulation of a different individual positioning QoS parameter across the positioning methods in the sequence.

5. The method according to claim 1, wherein determining a joint QoS metric for a candidate positioning sequence comprises determining the joint QoS metric as an accumulation of normalized values for an individual positioning parameter across the positioning methods in the sequence.

6. The method according to claim 1, wherein candidate sequence has a response time associated with its performance, and wherein said selecting comprises selecting the candidate sequence that has the maximum joint QoS metric or, if that includes multiple sequences having the same joint QoS metric, selecting from among those multiple sequences the one that has the minimum response time.

7. The method according to claim 1, wherein each candidate sequence has a cost associated with its performance, and wherein said selecting comprises selecting, from among those candidate sequences that have a joint QoS metric at least as great as a joint QoS metric determined for the request, the sequence that has the minimum cost.

8. The method according to claim 1, further comprising either: performing the selected sequence of positioning methods and returning the results of that selected sequence; or sending an indication of the selected sequence of positioning methods to another apparatus for that apparatus' performance thereof.

9. The method according to claim 8, further comprising dynamically updating the joint QoS metric for the performed positioning sequence based on the results of that sequence.

10. The method according to claim 1, wherein determining a joint QoS metric J.sup.(m,n, . . . ) for a candidate sequence of positioning methods (m,n, . . . ) that jointly depends on two or more joint QoS metrics J.sub.p1.sup.(m,n, . . . ) and J.sub.p2.sup.(m,n, . . . ) comprises calculating at least a portion of that joint QoS metric J.sup.(m,n, . . . ) as α.sub.p1 .Math.min(J.sub.p1.sup.(m,n, . . . ),1)+α.sub.p2.Math.min(J.sub.p2.sup.(m,n, . . . ),1), where J.sub.p1.sup.(m,n, . . . )is the accumulation of an individual QoS parameter p1 across the positioning methods (m,n, . . . ) in the sequence, J.sub.p2.sup.(m,n, . . . ) is the accumulation of an individual QoS parameter p2 across the positioning methods (m,n, . . . ) in the sequence, α.sub.p1 is a weighting value associated with p1, and α.sub.p2 is a weighting value associated with p2.

11. The method according to claim 1: wherein determining a joint QoS metric for a candidate sequence comprises determining the joint QoS metric as an accumulation of an individual positioning QoS parameter across the positioning methods in the sequence; and wherein said selecting comprises selecting based on evaluating the value of a corresponding individual positioning QoS parameter associated with the request in relation to the joint QoS metric determined for each candidate sequence.

12. An electronic processing apparatus configured to respond to a request for a mobile terminal's geographic position, the apparatus comprising one or more processing circuits configured to: determine one or more joint quality of service, QoS, metrics for each of a plurality of candidate positioning methods, or candidate sequences of positioning methods, a joint QoS metric jointly depending on either two or more individual QoS parameters associated with a candidate positioning method, or the positioning methods in a candidate sequence, wherein the one or more processing circuits are configured to either: determine a joint QoS metric for a candidate positioning method that jointly depends on two or more individual QoS parameters by preventing a first one of the two or more individual QoS parameters that has better quality from making up for a second one of the two or more individual QoS parameters that has lesser quality; or determine a joint QoS metric for a candidate sequence that jointly depends on two or more joint QoS metrics by preventing a first one of the two or more joint QoS metrics that has better quality from making up for a second one of the two or more joint QoS metrics that has lesser quality, each of the two or more joint QoS metrics comprising the accumulation of a different individual positioning QoS parameter across the positioning methods in the sequence; comparing the determined joint QoS metrics to a joint QoS metric determined for the request, the joint QoS metric determined for the request jointly depending on two or more individual QoS parameters associated with the request; and select from said plurality a positioning method, or a sequence of positioning methods, for determining the mobile terminal's position responsive to the request, based on said comparing.

13. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are further configured to determine the joint QoS metric for the request.

14. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are configured to determine a joint QoS metric for a candidate positioning method by determining a joint QoS metric that is based on a weighted combination of two or more individual QoS parameters associated with that positioning method, the weighting applied depending on a service type of the request.

15. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are configured to: receive one or more parameters indicative of one or more weighting values; and determine a joint QoS metric for a candidate positioning method by determining a joint QoS metric that is based on a weighted combination of two or more individual QoS parameters associated with that positioning method, the weighting being applied in accordance with the one or more weighting values.

16. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are configured to determine a joint QoS metric for a candidate positioning method by determining the joint QoS metric as a weighted combination of normalized values for two or more individual positioning QoS parameters associated with that positioning method.

17. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are configured to determine a joint QoS metric for a candidate sequence by determining a joint QoS metric that jointly depends on two or more joint QoS metrics, each of the two or more joint QoS metrics comprising the accumulation of a different individual positioning QoS parameter across the positioning methods in the sequence.

18. The electronic processing apparatus according to claim 12, wherein each candidate positioning method, or candidate sequence, has a cost associated with its performance, and wherein the one or more processing circuits are configured to select, from among those candidate positioning methods, or candidate sequences, that have a joint QoS metric at least as great as the joint QoS metric determined for the request, the method or sequence that has the minimum cost.

19. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are further configured to: perform the selected positioning method, or sequence of positioning methods, and returning the results of that selected positioning method or sequence; or send an indication of the selected positioning method, or sequence of positioning methods, to another apparatus for that apparatus' performance thereof.

20. The electronic processing apparatus according to claim 19, wherein the one or more processing circuits are further configured to dynamically update the joint QoS metric for the performed positioning method, or sequence, based on the results of that performed positioning method or sequence.

21. The electronic processing apparatus according to claim 12, wherein the one or more processing circuits are configured to either: determine a joint QoS metric J.sup.m for a candidate positioning method m that jointly depends on two or more normalized individual QoS parameters {circumflex over (p)}.sub.1.sup.m and {circumflex over (p)}.sub.2.sup.m by calculating at least a portion of that joint QoS metric J.sup.m as α.sub.p1.Math.min({circumflex over (p)}.sub.1.sup.m,1)+α.sub.p2.Math.min({circumflex over (p)}.sub.2.sup.m,1), where α.sub.p1 is a weighting value associated with {circumflex over (p)}.sub.1.sup.m and α.sub.p2 is a weighting value associated with {circumflex over (p)}.sub.2.sup.m ; or determine a joint QoS metric J.sup.(m,n, . . . ) for a candidate sequence of positioning methods (m,n, . . . ) that jointly depends on two or more joint QoS metrics J.sub.p1.sup.(m,n, . . . ) and J.sub.p2.sup.(m,n, . . . ) by calculating at least a portion of that joint QoS metric J.sup.(m,n, . . . ) as α.sub.p1.Math.min(J.sub.p1.sup.(m,n, . . . ),1)+α.sub.p2.Math.min(J.sub.p2.sup.(m,n, . . . ),1) where J.sub.p1.sup.(m,n, . . . ) is the accumulation of an individual QoS parameter p1 across the positioning methods (m,n, . . . ) in the sequence, J.sub.p2.sup.(m,n, . . . ) is the accumulation of an individual QoS parameter p2 across the positioning methods (m,n, . . . ) in the sequence, α.sub.p1 is a weighting value associated with p1, and α.sub.p2 is a weighting value associated with p2.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a block diagram of a mobile communication network according to various embodiments of the present invention.

(2) FIG. 2 is a logic flow diagram of a method implemented by an electronic processing apparatus for responding to a request for a mobile terminal's geographic position, according to some embodiments of the present invention.

(3) FIG. 3 is a logic flow diagram of a method for responding to a positioning request according to other embodiments of the present invention.

(4) FIG. 4 is a block diagram of a positioning node configured to perform the method shown in FIG. 3.

(5) FIG. 5 is a logic flow diagram of a method for responding to a positioning request according to still other embodiments of the present invention.

(6) FIG. 6 is a logic flow diagram of a mobile terminal configured to perform the method shown in FIG. 5.

(7) FIG. 7 is a logic flow diagram of an access node configured to perform the method shown in FIG. 5.

(8) FIG. 8 is a logic flow diagram of a method for responding to a positioning request according to yet other embodiments of the present invention.

(9) FIG. 9 is a block diagram of a positioning node configured to perform the method shown in FIG. 8.

DETAILED DESCRIPTION

(10) FIG. 1 illustrates a mobile communication network 10, which, by way of non-limiting example, may comprise a Long Term Evolution (LTE) network. As depicted, the network 10 includes a Radio Access Network (RAN) 12 and a Core Network (CN) 14. The RAN 12 and the CN 14 communicatively couple mobile terminals 16 in the geographic coverage area of the network 10 to one or more external networks 18, such as the Internet or the Public Switched Telephone Network (PSTN).

(11) To that end, the RAN 12 includes a number of access nodes (ANs) 20—e.g., eNodeBs in an LTE embodiment—distributed across the geographic coverage area of the network 10. The ANs 20 each provide radio communication coverage for one or more portions of that area, referred to as cells 22. Mobile terminals 16 may change their geographic position, moving within or between cells 22, while maintaining communication with the ANs 20.

(12) Capable of estimating the current geographic position of any given mobile terminal 16, the mobile communication network 10 supports a variety of location services (LCS), e.g., emergency services, navigational assistance, and the like. Any authorized electronic processing apparatus, whether internal or external to the network 10, may subscribe to these location services in order to request positioning information for a mobile terminal 16. The requesting apparatus may be, for example, an emergency services network-based entity that requests positioning information when the user of the mobile terminal 16 makes an emergency services call. As another example, the requesting apparatus may be the mobile terminal 16 itself.

(13) Regardless of the particular apparatus originating the request, the request includes or is otherwise associated with two or more individual quality of service (QoS) parameters p.sup.r. In some embodiments, one such QoS parameter p.sub.time.sup.r relates to how quickly positioning information should be provided in response to the request, i.e., the requested response time expressed in seconds. Other QoS parameters in these embodiments relate to how accurate the positioning information should be. For instance, one QoS parameter p.sub.error.sup.r relates to the requested horizontal accuracy of the positioning information, and is expressed as a radius, in meters, of an uncertainty or error circle. A separate QoS parameter p.sub.v.sub._.sub.error.sup.r may relate to the requested vertical accuracy of the positioning information.

(14) The positioning request may likewise be accepted by any one of various apparatuses within the network 10 that are configured to estimate the position of the mobile terminal 16 responsive to the request. In some embodiments, for instance, the mobile terminal 16 estimates its own position. In other embodiments, the AN 14 serving the mobile terminal 16 estimates the terminal's position. In still other embodiments, the CN 20 includes or couples the mobile terminal 16 to a special positioning node (PN) 24—e.g., an Evolved Serving Mobile Location Center (E-SMLC) in an LTE embodiment—that is specifically dedicated to estimating the geographic position of the mobile terminal 16.

(15) Whichever apparatus estimates the position of the mobile terminal 16 responsive to the positioning request, be it the mobile terminal 16, the serving AN 20, or the PN 24, that apparatus has available to it a plurality of positioning methods, M, denoted as candidate positioning methods. The apparatus, in some embodiments, estimates the position of the mobile terminal 16 by performing a single one of the candidate positioning methods, e.g., mεM. In other embodiments, the apparatus estimates the position by performing some combination of multiple positioning methods, e.g., (m,n, . . . )εM, either serially in a defined order or in parallel. With a plurality of combinations possible, each such combination is referred to herein as a candidate sequence of positioning methods.

(16) Notably, the selection of which candidate positioning method, or candidate sequence of positioning methods, to perform for best satisfying the QoS parameters p.sup.r of the positioning request proceeds in a more intelligent manner than known selection approaches. In this regard, positioning QoS is viewed holistically for candidate positioning methods, or candidate sequences, according to the processing illustrated in FIG. 2.

(17) In FIG. 2, processing “begins” by determining a joint QoS metric J for each of a plurality of candidate positioning methods, or candidate sequences of positioning methods (Block 100). A joint QoS metric J.sup.m for a candidate positioning method m jointly depends on two or more individual QoS parameters p.sup.m associated with that method. Thus instead of a candidate positioning method m being described by several individual QoS parameters, e.g., p.sub.time.sup.m and p.sub.error.sup.m, the method is described by a single, joint QoS metric J.sup.m that in a sense represents an overall QoS for that method.

(18) In many embodiments, a joint QoS metric J.sup.(m,n, . . . ) for a candidate sequence of positioning methods (m,n, . . . ) is a direct extension of this concept across multiple methods, i.e., a single, joint QoS metric J.sup.(m,n, . . . ) that represents an overall QoS for that sequence. In other embodiments, though, a joint QoS metric J.sup.(m,n, . . . ) for a candidate sequence just represents the accumulation of an individual positioning QoS parameter p across the positioning methods in the sequence; that is, the joint effect of the positioning methods on that parameter p. In such embodiments, a candidate sequence may be described by several joint QoS metrics J.sup.(m,n, . . . ), with different joint QoS metrics J.sup.(m,n, . . . ) representing the accumulation of different individual positioning QoS parameters p across the positioning methods in the sequence. The description herein will distinguish between these embodiments, primarily for convenience, by denoting a joint QoS metric that represents an overall QoS for the sequence simply as J.sup.(m,n, . . . ) and denoting a joint QoS metric that represents the accumulation of an individual positioning) QoS parameter p across the positioning methods in the sequence as J.sub.p.sup.(m,n, . . . ). Nonetheless in all of these embodiments a joint QoS metric for a candidate sequence, whether denoted as J.sup.(m,n, . . . ) or J.sub.p.sup.(m,n, . . . ), jointly depends on two or more positioning methods in that sequence.

(19) Having determined a joint QoS metric J for each candidate positioning method, or candidate sequence of positioning methods, processing “continues” with selecting a positioning method or sequence for determining the mobile terminal's position responsive to the request, based on those joint QoS metrics J (Block 110). For example, in some embodiments, described more fully below, this selection entails selecting the positioning method or sequence that has the maximum joint QoS metric J. Regardless, by selecting a positioning method or sequence in this way, holistically based on joint QoS metrics J, selection proceeds flexibly according to actual QoS requirements of position-based services and/or systematically according to the joint effect of multiple positioning methods.

(20) The above processing may be carried out in any one of various electronic processing apparatuses within the network 10, not just the apparatus that ultimately performs the selected positioning method or sequence. That is, the above processing may be carried out in some embodiments in a network node, such as an AN 20 or Mobility Management Entity (MME) in an LTE embodiment, while actual performance of the selected positioning method or sequence is carried out in another node, such as the PN 24. In these embodiments, the processing may “end” with sending an indication of the selected positioning method or sequence to another apparatus, e.g., the PN 24, for that apparatus' performance thereof (Block 120). Of course, the processing may alternatively be carried out in the apparatus that actually performs the selected positioning method or sequence, e.g., the PN 24, such that processing “ends” with performing the selected positioning method or sequence, and then returning the positioning results (Block 130).

(21) FIG. 3 illustrates additional details of certain embodiments mentioned above, namely those directed to joint QoS metrics that represent overall QoS's of candidate positioning methods or sequences, e.g., where a joint QoS metric is denoted as J.sup.m for a candidate positioning method m or as J.sup.(m,n, . . . ) for a candidate positioning sequence (m,n, . . . ). As shown in FIG. 3, selection processing in these embodiments may further include determining a joint QoS metric J.sup.r for a positioning request (Block 200). This joint QoS metric J.sup.r jointly depends on two or more individual QoS parameters p.sup.r associated with the request. Thus, instead of the positioning request being described by several individual QoS parameters, e.g., p.sub.time.sup.r and p.sub.error.sup.r, the request is described by a single, joint QoS metric J.sup.r that in a sense represents an overall QoS for the request.

(22) Accordingly, having determined a joint QoS metric for each candidate positioning method or sequence as described above (Block 210), processing “continues” in the apparatus with selecting a positioning method or sequence based on evaluating the joint QoS metric J.sup.r for the request in relation to the joint QoS metric determined for each candidate positioning method (i.e., J.sup.m), or each candidate sequence (i.e., J.sup.(m,n, . . . ) (Block 220). This may entail, for instance, comparing the joint QoS metric J.sup.r for the request to the joint QoS metrics for the candidate positioning methods (i.e., J.sup.m), or candidate sequences (i.e., J.sup.(m,n, . . . )), and selecting the method or sequence that best satisfies the joint QoS metric J.sup.r for the request according to some selection criteria.

(23) In some embodiments, for example, the apparatus selects the method or sequence that has the maximum joint QoS metric in relation to the joint QoS metric J.sup.r for the request. Ties between multiple methods that have the same joint QoS metric J.sup.m may be broken by comparison of an individual QoS parameter p.sup.m associated with the methods, e.g., response time p.sub.time.sup.m. Similarly, ties between multiple sequences that have the same joint QoS metric J.sup.(m,n, . . . ) may be broken by comparison of an individual QoS parameter p as accumulated across the methods in each sequence. Indeed, in at least one embodiment, if multiple methods or sequences each have the maximum joint QoS metric, the apparatus selects from among those multiple methods or sequences the one that has the minimum response time.

(24) In other embodiments, the apparatus considers the cost of performing the candidate positioning methods or sequences in terms of processing resources used, rather than simply selecting the method or sequence that yields the maximum joint QoS. In these embodiments, each candidate positioning method or sequence has a cost c associated with its performance. Having compared the joint QoS metric J.sup.r for the request to the joint QoS metrics for the candidate positioning methods (i.e., J.sup.m), or candidate sequences (i.e., J.sup.(m,n, . . . )), the apparatus selects from among those candidate positioning methods or sequences that have a joint QoS metric at least as great as the joint QoS metric J.sup.r for the request, the method or sequence that has the minimum cost c.

(25) Processing in the apparatus may then proceed as already discussed; that is, by either sending an indication of the selected positioning method or sequence to another apparatus for that apparatus' performance thereof (Block 230), or by performing the selected positioning method or sequence itself, and returning the positioning results (Block 240).

(26) As used herein to describe the apparatus' processing in FIG. 3, determining a joint QoS metric J.sup.r for a positioning request (i.e., Block 200) may comprise either actually computing that joint QoS metric J.sup.r or simply receiving the joint QoS metric J.sup.r from another apparatus. In embodiments where processing includes computing the joint QoS metric J.sup.r for the request, processing may further include determining or otherwise obtaining values for the individual QoS parameters p.sup.r associated with the request, so that the joint QoS metric J.sup.r can be computed in joint dependence on those parameters p.sup.r. These values can be directly or indirectly signaled to the apparatus in any number of ways. As examples of direct signaling, the parameters p.sup.r can be included in the positioning request or received separately. As an example of indirect signaling, information related to the type of position-based services that the request is for can be received as part of the request, or separately. In this case, processing may include mapping that type information to individual QoS parameters p.sup.r, which are then used to compute the joint QoS metric J.sup.r for the request.

(27) In view of the above modifications and variations to the processing in FIG. 3, FIG. 4 illustrates an example of an electronic processing apparatus configured to carry out such processing. Specifically, FIG. 4 depicts an example of the PN 24, which according to one or more embodiments is configured to carry out the processing in FIG. 3. The PN 24 as shown includes a communication interface 28 that communicatively couples the PN 24 to one or more ANs 20, or other nodes. The PN 24 also includes one or more processing circuits 30, such as microprocessors or other computer/digital processing circuits, that are configured to carry out the processing in FIG. 3, responsive to receiving a positioning request for a mobile terminal 16 via the communication interface 28.

(28) The processing circuit(s) 30 as depicted are at least logically divided into various circuits, including a joint QoS determination circuit 32 configured to determine a joint QoS metric J.sup.r for the positioning request as discussed above. The joint QoS determination circuit 32 may simply receive the joint QoS metric J.sup.r as part of or in conjunction with the positioning request. Alternatively, the joint QoS determination circuit 32 may determine individual QoS parameters p for the request and use those parameters to compute the joint QoS metric J.sup.r.

(29) The processing circuit(s) 30 further include a joint QoS determination circuit 34 configured to determine a joint QoS metric for each candidate positioning method or sequence. A selection circuit 36 receives as input the joint QoS metric J.sup.r determined for the positioning request and the joint QoS metric determined for each candidate positioning method or sequence. Then, after selecting a positioning method or sequence for determining the mobile terminal's position, the selection circuit 36 provides the selected method or sequence to a performance circuit 38. The performance circuit 38 performs the selected method or sequence to obtain positioning information for the mobile terminal 16. The PN 24 returns this positioning information in response to the request, either to the apparatus that originated the request or to still another apparatus.

(30) In one or more embodiments, the joint QoS metric determination circuit 34 dynamically computes joint QoS metrics for the candidate positioning methods or sequences on the fly, or alternatively, maintains pre-computed values for those metrics. For example, the joint QoS metric determination circuit 34 may maintain a data table or other such data structure in non-volatile memory or other storage, which contains joint QoS metrics for each positioning method or sequence supported by the PN 24.

(31) Because the achieved quality for various QoS parameters that are obtained by a given sequence of positioning methods depends in some cases on the particular performance order of those methods (or whether they are performed in parallel), the joint QoS metric determination circuit 34 may store different joint QoS metrics for each sequence of methods defined by the PN 24. Further, even where the joint QoS metric determination circuit 34 stores pre-computed values for the joint QoS metrics of its defined methods or sequences, the circuit 34 may be configured to dynamically updated those metrics as part of its ongoing operations, based on the actual positioning results achieved by the performance circuit 38.

(32) Whether the joint QoS metrics for the candidate positioning methods or sequences are computed or retrieved from storage, they are, as noted above, “joint” in the sense that they depend on two or more individual QoS parameters, or two or more positioning methods. Consider first, for instance, a joint QoS metric J.sup.m for a candidate positioning method m. In some embodiments, the joint QoS metric J.sup.m is based on a weighted combination of the individual QoS parameters p.sup.m associated with that method, e.g.:
J.sup.m=α.Math.p.sub.time.sup.m+(1−α).Math.p.sub.error.sup.m,  (1)

(33) where any relative weighting combination is possible, based on αε[0,1].

(34) With α=1, the joint QoS metric J.sup.m fully prioritizes the response time p.sub.time.sup.m of the candidate positioning method, meaning that the method will not be selected unless it fully satisfies the requested response time p.sub.time.sup.r, as is the case for time-critical services. Conversely, with α=0, the joint QoS metric J.sup.m fully prioritizes the accuracy p.sub.error.sup.m of the candidate positioning method, meaning that the method will not be selected unless it fully satisfies the requested accuracy p.sub.error.sup.r, as is the case for accuracy-critical services. By setting α to any other value, an intermediate, fractional weight may be applied to the response time p.sub.time.sup.m and accuracy p.sub.error.sup.m of the candidate positioning method, to express a bias or preference toward response time or accuracy. With any relative weighting or bias possible, joint QoS metrics enable intelligent positioning method selection that is based more realistically on actual QoS requirements of position-based services, which may be neither accuracy-critical nor time-critical.

(35) In fact, in one or more embodiments, the relative weighting α applied to the individual QoS parameters p.sup.m associated with a given candidate positioning method m depends on the type of position-based services for which the request was made. Example service types may include emergency services, traffic information, asset management, friend finding, weather, etc., as specified in 3GPP Technical Specification 22.071. The service type may be included in or otherwise accompany the positioning request, and may map to a specific weighting α to apply for joint QoS metric computation.

(36) In other embodiments, the relative weighting α is signaled as part of a positioning request (e.g., from a Mobility Management Entity (MME) to the PN 24). The relative weighting α may alternatively be signaled as part of a positioning provide information message (e.g., from a mobile terminal 16 to the PN 24). In yet other embodiments, the relative weighting α is signaled as a requested parameter in a positioning provide information request (e.g., as a binary indicator which is TRUE if the parameter is requested).

(37) Accordingly, in embodiments where the PN 24 in FIG. 4 computes the joint QoS metrics, the PN 24 includes weighting values 40, which may be expressed as different sets of weighting values to be applied. The joint QoS metric determination circuit 34 may compute a joint QoS metric J.sup.m for a candidate positioning method m by determining a service type of the positioning request and determining a set of weighting values 40 based on that service type. Alternatively, the joint QoS metric determination circuit 34 may receive one or more parameters indicative of those weighting values 40 (e.g., via the signaling just described). In either case, the joint QoS metric determination circuit 34 may then compute the joint QoS metric J.sup.m as a weighted combination of the individual QoS parameters p.sup.m associated with that method according to equation (1), with the determined set of weighting values 40 as α, (1−α), etc.

(38) Of course, equation (1) represents just one example of a joint QoS metric J.sup.m for a candidate positioning method m, where the method is only associated with two individual QoS parameters p.sub.time.sup.m and p.sub.error.sup.m. In other embodiments, the method may be associated with more than two individual QoS parameters, e.g., p.sub.time.sup.m, p.sub.error.sup.m, and p.sub.v.sub._.sub.error.sup.m. In this case, equation (1) may be extended as:
J.sup.m=α.Math.p.sub.time.sup.m+(1−α−α.sub.v.sub._.sub.error).Math.p.sub.error.sup.m+α.sub.v.sub._.sub.error.Math.p.sub.v.sub._.sub.error.sup.m   (2)

(39) where α+α.sub.v.sub._.sub.error≦1. For ease of illustration, however, this description will simply use examples with two individual QoS parameters.

(40) Especially as the number of individual QoS parameters p.sup.m increases, though, those parameters p.sup.m may be expressed in different units (e.g., seconds for response time, meters for accuracy/error). In one or more embodiments, therefore, a joint QoS metric J.sup.m for a candidate positioning method m is determined as a weighted combination of normalized values {circumflex over (p)}.sup.m for those parameters:
J.sup.m=α.Math.{circumflex over (p)}.sub.time.sup.m+(1−α).Math.{circumflex over (p)}.sub.error.sup.m  (3)

(41) These normalized values {circumflex over (p)}.sup.m are dimensionless and may be weightedly combined without regard to the units of their associated QoS parameters p.sup.m.

(42) In some embodiments, for example, normalized values {circumflex over (p)}.sup.m are obtained by normalizing individual QoS parameters p.sup.m with respect to pre-determined reference values p.sup.ref that have units corresponding to those of the QoS parameters p.sup.m, e.g.:

(43) $\begin{array}{cc}{\hat{p}}_{\mathrm{time}}^m=\frac{p_{\mathrm{time}}^{\mathrm{ref}}}{p_{\mathrm{time}}^m}{\hat{p}}_{\mathrm{error}}^m=\frac{p_{\mathrm{error}}^{\mathrm{ref}}}{p_{\mathrm{error}}^m}& \left(4\right)\end{array}$

(44) The normalized values {circumflex over (p)}.sup.m in these embodiments express the individual QoS parameters p.sup.m as dimensionless ratios. Such dimensionless ratios describe the extent to which the individual QoS parameters p.sup.m satisfy or otherwise meet the corresponding pre-determined reference values p.sup.ref.

(45) With the individual QoS parameters p.sup.m normalized in this way, and with the joint QoS metric J.sup.m calculated as in equation (3), a candidate positioning method m that has, e.g., a quicker response time p.sub.time.sup.m than the pre-determined reference response time p.sub.time.sup.ref (i.e., {circumflex over (p)}.sub.time.sup.m>1), but a greater error p.sub.error.sup.m than the pre-determined reference error p.sub.error.sup.ref error (i.e., {circumflex over (p)}.sub.error.sup.m>1), could have the same resulting joint QoS metric as another method n that has the same response time p.sub.time.sup.n as the pre-determined reference response time p.sub.time.sup.ref (i.e., {circumflex over (p)}.sub.time.sup.n=1) and the same error p.sub.error .sup.n as the pre-determined reference error p.sub.error.sup.ref (i.e., {circumflex over (p)}.sub.error.sup.n=1). That is, better quality with respect to one QoS parameter can in a sense “make up” for lesser quality with respect to a different QoS parameter.

(46) In some cases this may be undesirable. Thus according to other embodiments, a joint QoS metric J.sup.m is determined according to:
J.sup.m=α.Math.min({circumflex over (p)}.sub.time.sup.m,1)+(1−α).Math.min({circumflex over (p)}.sub.error.sup.m,1),   (5)

(47) where the min function prevents one QoS parameter that has better quality from making up for another QoS parameter that has lesser quality.

(48) Consider now a joint QoS metric J.sup.(m,n, . . . ) for a candidate sequence of positioning methods (m,n, . . . ), which by extension of the above concepts is a single, joint QoS metric that represents an overall QoS for that sequence. In some embodiments, the joint QoS metric J.sup.(m,n, . . . ) jointly depends on two or more joint QoS metrics J.sub.p.sup.(m,n, . . . ) which each comprise the accumulation of a different individual positioning QoS parameter p across the positioning methods in the sequence. A joint QoS metric J.sub.time.sup.(m,n, . . . ), for example, comprises the accumulation of the QoS parameter p.sub.time across the positioning methods in the sequence:
J.sub.time.sup.(m,n, . . . )=p.sub.time.sup.m+p.sub.time.sup.n+ . . . , for serial performance of the methods m,n, . . .
J.sub.time.sup.(m,n, . . . )=max(p.sub.time.sup.m,p.sub.time.sup.n, . . . ), for parallel performance of the methods m,n, . . .   (6)

(49) Likewise, a joint QoS metric J.sub.error.sup.(m,n, . . . ) comprises the accumulation of the QoS parameter p.sub.error across the positioning methods in the sequence:
J.sub.error.sup.(m,n, . . . )=min(p.sub.error.sup.m,p.sub.error.sup.n, . . . ), for independent performance of the methods m,n, . . .
J.sub.error.sup.(m,n, . . . )≦min(p.sub.error.sup.m,p.sub.error.sup.n, . . . ), for hybrid performance of the methods m,n, . . . ,   (7)

(50) where hybrid performance of the methods entails using the partial results of one method to aid or otherwise assist the performance of another method in the sequence. Similar to the embodiments described above, the joint QoS metrics J.sub.p.sup.(m,n, . . . ) may be based on normalized values of the QoS parameters p.sub.time and p.sub.error, e.g., {circumflex over (p)}.sub.time.sup.m, {circumflex over (p)}.sub.time.sup.n, . . . and {circumflex over (p)}.sub.error.sup.m, {circumflex over (p)}.sub.error.sup.n, . . . .

(51) The joint QoS metric J.sup.(m,n, . . . ) for the candidate sequence (m,n, . . . ) may then be based on a weighted combination of these two or more joint QoS metrics J.sub.p.sup.(m,n, . . . ):
J.sup.(m,n, . . . )=α.Math.min(J.sub.time.sup.(m,n, . . . ),1)+(1−α).Math.min(J.sub.error.sup.(m,n, . . . ),1),   (8)

(52) where, again, any relative weighting combination is possible, based on αε[0,1]. The weighting values α, α−1, . . . may in much the same way as previously described permit a bias or preference toward the overall response time or accuracy provided by the candidate sequence, and may depend on the service type of the positioning request.

(53) With the overall QoS of candidate positioning methods or sequences described according to joint QoS metrics (J.sup.m for methods and J.sup.(m,n, . . . ) for sequences), selection can proceed holistically, based on evaluating the joint QoS metric J.sup.r for the request in relation to the joint QoS metrics for the candidate methods or sequences. In this regard, the joint QoS metric J.sup.r for the request can be computed in much the same way as a joint QoS metric J.sup.m for a given candidate positioning method. That is, the joint QoS metric J.sup.r for the request in one or more embodiments is computed based on a weighted combination of two or more individual positioning QoS parameters p.sup.r associated with the request:
J.sup.r=α.Math.min({circumflex over (p)}.sub.time.sup.r,1) +(1−α).Math.min({circumflex over (p)}.sub.error.sup.r,1),   (9)

(54) where the QoS parameters have been normalized and weighted in the same manner as those of the candidate positioning methods or sequences.

(55) Referring briefly again to FIG. 4, and with the above details in mind, the PN 30 may compute any of these joint QoS metrics J.sup.r, J.sup.m, J.sup.(m,n, . . . ), or may alternatively receive them from another apparatus. In particular embodiments, for example, the PN 30 receives the joint QoS metric J.sup.r for the request from another apparatus, e.g., a mobile terminal 16 or an AN 20, with that apparatus being the entity that computes the metric.

(56) FIG. 5 illustrates processing carried out in such an apparatus according to one or more embodiments. As depicted in FIG. 5, processing may optionally begin with determining individual QoS parameters p.sup.r associated with a positioning request (Block 300). Processing “continues” with computing a joint QoS metric J.sup.r for the request that jointly depends on the two or more individual QoS parameters p.sup.r (Block 310). Finally, processing “ends” with sending the request and the joint QoS metric J.sup.r to another apparatus for selection of a positioning method, or a sequence of positioning methods, based on the joint QoS metric J.sup.r (Block 320).

(57) FIG. 6 illustrates an example of an electronic processing apparatus configured to carry out such processing. Specifically, FIG. 6 depicts an example of a mobile terminal 16, which according to one or more embodiments is configured to carry out the processing in FIG. 5, in conjunction with sending a positioning request to its supporting network. The mobile terminal 16 as shown includes one or more processing circuits 42 that are at least logically divided into various circuits, including an application processor 44 that may trigger the sending of the positioning request. A software application running on the application processor 44 may, for instance, be or use a position-based service, and thereby trigger the sending of the positioning request, for use by that service.

(58) The one or more processing circuits 42 also include a joint QoS metric computation circuit 46 configured to compute a joint QoS metric J.sup.r for the request, e.g., in accordance with weighting values 48. For example, in some embodiments, the joint QoS metric computation circuit 42 determines a service type of the request and determines weighting values 48 based on that service type, such as by mapping the service type to a particular set of weighting values. The determination circuit 42 then computes the joint QoS metric J.sup.r as a weighted combination of the two or more individual positioning QoS parameters p.sup.r, according to those weighting values 48.

(59) The one or more processing circuits 42 further include an access control processor 50 that implements the air interface protocols, including any encryption and authentication processing, needed to send uplink signals to an AN 20 via transceiver circuits 52 and one or more associated antennas. By way of these circuits, the processing circuit(s) 42 send the positioning request and the joint QoS metric J.sup.r computed for the request to another apparatus, e.g., an AN 20 or the PN 24, for selection of a positioning method, or sequence of positioning methods, based on that joint QoS metric. Thus, the mobile terminal 16 configured as described above may originate a positioning request that includes or is accompanied by a joint QoS metric J.sup.r, for greatly improved selection of the positioning method or sequence used to respond to the request.

(60) FIG. 7 depicts an example of an AN 20, which according to one or more other embodiments is configured to carry out the processing in FIG. 5. The AN 20 includes one or more antennas and transceiver circuits 54 configured to receive uplink signals from a mobile terminal 16, which may include a positioning request. In some embodiments, the positioning request includes or otherwise accompanies a joint QoS metric J.sup.r for the request; in these cases, the AN 20 simply passes the request along to, e.g., the PN 24. In other embodiments, the positioning request does not accompany a joint QoS metric J.sup.r, but instead only accompanies individual QoS parameters or a service type. In these embodiments, the AN 20 is configured to itself compute the joint QoS metric J.sup.r.

(61) To that end, the AN 20 includes one or more processing circuits 56 that are at least logically divided into various circuits, including a joint QoS metric computation circuit 58 configured to compute a joint QoS metric J.sup.r for the request, e.g., in accordance with weighting values 60. For example, in some embodiments, the joint QoS metric computation circuit 58 determines a service type of the request and determines weighting values 60 based on that service type, such as by mapping the service type to a particular set of weighting values. The determination circuit 58 then computes the joint QoS metric J.sup.r as a weighted combination of the two or more individual positioning QoS parameters p.sup.r, according to those weighting values 60.

(62) The AN 20 further include a communication interface 62 that is configured to send the positioning request and the joint QoS metric J.sup.r computed for the request to another apparatus, e.g., the PN 24, for selection of a positioning method, or sequence of positioning methods, based on that joint QoS metric.

(63) With the above variations in mind, it should be understood that the joint QoS metric J.sup.r for any given positioning request is computed by the mobile terminal 16 in some embodiments, is computed in the RAN 12 in other embodiments, e.g., at an AN 20 or Mobility Management Entity (MME), and is computed in the CN 24 in still other embodiments, e.g., at the PN 24. Further, it may be that the apparatus that computes the joint QoS metric J.sup.r for a given positioning request changes, based on the type of position-based service or other circumstances associated with the request.

(64) Discussion now shifts to embodiments directed to joint QoS metrics J.sub.p.sup.(m,n, . . . ) for a candidate sequence that just represent the accumulation of an individual positioning QoS parameter p across the positioning methods in the sequence, rather than representing an overall QoS for the sequence. In such embodiments, a candidate sequence may be described by several joint QoS metrics J.sub.p.sup.(m,n, . . . ), with different joint QoS metrics J.sub.p.sup.(m,n, . . . ) representing the accumulation of different individual positioning QoS parameters p across the positioning methods in the sequence. Furthermore, in these embodiments, a joint QoS metric J.sup.r is not computed for a positioning request. Rather, the individual positioning QoS parameters p.sup.r associated with the request are themselves evaluated in relation to corresponding joint QoS metrics J.sub.p.sup.(m,n, . . . ) for the sequence. FIG. 8 illustrates selection processing according to these embodiments.

(65) As shown in FIG. 8, processing “begins” with determining a joint QoS metric J.sub.p.sup.(m,n, . . . ) for each candidate sequence as an accumulation of an individual positioning QoS parameter p across the positioning methods in that sequence (Block 400). This individual QoS parameter may be, for example, p.sub.time. In that case, processing entails determining a joint QoS metric J.sub.time.sup.(m,n, . . . ) for each candidate sequence. The joint QoS metric J.sub.time.sup.(m,n, . . . ) for a given one of those sequences comprises the accumulation of the QoS parameter p.sub.time across the positioning methods in the sequence:
J.sub.time.sup.(m,n, . . . )=p.sub.time.sup.m+p.sub.time.sup.n+ . . . , for serial performance of the methods m,n, . . .
J.sub.time.sup.(m,n, . . . )=max(p.sub.time.sup.m,p.sub.time.sup.n, . . . ), for parallel performance of the methods m,n, . . .

(66) Regardless, the joint QoS metrics J.sub.time.sup.(m,n, . . . ) may be based on normalized values of the QoS parameter p.sub.time, e.g., {circumflex over (p)}.sub.time.sup.m, {circumflex over (p)}.sub.time.sup.n.

(67) Processing then “continues” with selecting a sequence of positioning methods for determining the mobile terminal's position responsive to the request, based on evaluating the value of a corresponding individual positioning QoS parameter associated with the request, e.g., p.sub.time.sup.r, in relation to the joint QoS metrics determined for each candidate sequence, e.g., J.sub.time.sup.(m,n, . . . ) (Block 410). This selection may entail, for example, selecting the candidate sequence that, according to the joint QoS metrics J.sub.time.sup.(m,n, . . . ), has fastest total response time in relation to the requested response time p.sub.time.sup.r. Of course, as a candidate sequence may be described by multiple joint QoS metrics J.sub.p.sup.(m,n, . . . ) in these embodiments, e.g., both J.sub.time.sup.(m,n, . . . ) and J.sub.error.sup.(m,n, . . . ), selection may also be based on evaluating the value of other individual positioning QoS parameters associated with the request, e.g., p.sub.error.sup.r in relation to those other joint QoS metrics.

(68) Processing in the apparatus may nonetheless proceed as already discussed; that is, by either sending an indication of the selected positioning sequence to another apparatus for that apparatus' performance thereof (Block 420), or by performing the selected positioning sequence itself, and returning the positioning results (Block 430).

(69) FIG. 9 briefly illustrates an example of an apparatus configured to carry out the processing in FIG. 8. Specifically, FIG. 9 illustrates the apparatus as the PN 24, the PN 24 being similar to the PN 24 illustrated in FIG. 4, with a few exceptions. The PN 24 in FIG. 9 includes an individual QoS parameter determination circuit 64 configured to determine the individual QoS parameters associated with the request. The circuit 64 provides one or more of those parameters to the selection circuit 36, which performs the selection based on the parameters as discussed above. Note that the PN 24 in FIG. 9 does not include weighting values 40, as in FIG. 4, since no weighting is applied to different individual QoS parameters in these embodiments; that is, instead of weighting across individual QoS parameters, these embodiments just accumulate those parameters across positioning methods in a sequence.

(70) Of course, those skilled in the art will readily appreciate that the above examples and figures are non-limiting, and thereby simply illustrate some embodiments of the present invention. For example, in one or more embodiments, the joint QoS metrics are associated with a set of characteristics of the mobile terminal 16. The set of characteristics comprises at least one or any combination of the following: the terminal type which is being positioned, its capabilities (e.g., a laptop may have a better receiver than a cellular telephone and a small radio node, e.g., a relay, may have a better receiver than a laptop), and its measurement configuration (e.g., measurement bandwidth). This information may be received in a positioning request, signaled in relation to the request, or extracted for the requesting entity from some other database (e.g., maintained in MME or eNodeB in LTE). The association can be accounted for in the positioning method or sequence selection logic to better adapt the positioning service to the characteristics of the mobile terminal being positioned.

(71) Furthermore, although FIGS. 4 and 9 only illustrate the PN 24 as the apparatus performing the processing of FIGS. 2, 3, and/or 7, any one of various apparatuses may, as noted above, perform that processing. Furthermore, several embodiments have been described for convenience and ease of illustration using generalizations, but certain specific cases are also contemplated as being within the scope of the present invention and indeed may be equivalent.

(72) For example, normalization of the individual QoS parameters has been generally described above with respect to pre-determined reference values p.sup.ref. In one or more specific embodiments, though, these reference values p.sup.ref comprise the individual QoS parameters p.sup.r associated with the positioning request:

(73) $\begin{array}{cc}{\hat{p}}_{\mathrm{time}}^m=\frac{p_{\mathrm{time}}^r}{p_{\mathrm{time}}^m}{\hat{p}}_{\mathrm{error}}^m=\frac{p_{\mathrm{error}}^r}{p_{\mathrm{error}}^m}& \left(10\right)\end{array}$

(74) That is, the obtained normalized values {circumflex over (p)}.sup.m describe the extent to which the individual QoS parameters p.sup.m satisfy the individual QoS parameters p.sup.r associated with the positioning request. So normalized, a joint QoS metric J.sup.m for a candidate positioning method inherently encompasses a comparison to the joint QoS metric J.sup.r for the request, such that selection may be simplified in some sense to selecting the candidate positioning method with the maximum joint QoS metric J.sup.m:

(75) $\begin{array}{cc}m=\arg \underset{m\in M}{\max }{J}^m& \left(11\right)\end{array}$

(76) This same concept may be extended to candidate sequences of positioning methods.

(77) Those skilled in the art will appreciate, however, that these specific embodiments are actually equivalent to the more general embodiments described above, where the joint QoS metrics for the request, and the candidate positioning methods or sequences, are normalized the same. Indeed, in these cases, the joint QoS metric J.sup.r for the request simplifies to unity:

(78) $\begin{array}{cc}{J}^r=\alpha .Math.\min \left(\frac{p_{\mathrm{time}}^r}{p_{\mathrm{time}}^r},1\right)+\left(1-\alpha \right).Math.\min \left(\frac{p_{\mathrm{error}}^r}{p_{\mathrm{error}}^r},1\right)=1& \left(12\right)\end{array}$

(79) Those skilled in the art will further appreciate that a mobile terminal 16 may comprise a mobile telephone, a Portable Digital Assistant, a laptop computer, or the like. Also, no particular communication interface standard is necessary for practicing the present invention. The mobile communication network 10, therefore, may be any one of a number of standardized network implementations, including Long Term Evolution (LTE), LTE-Advanced, or the any other implementation supporting, e.g., quantification of individual QoS parameters for a positioning request and/or candidate positioning methods or sequences.

(80) Those skilled in the art will also appreciate that the various “circuits” described may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware (e.g., stored in memory) that, when executed by the one or more processors, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

(81) Thus, those skilled in the art will recognize that the present invention may be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the invention. The present embodiments are thus to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.