PROPRIETARY EXTENSIONS IN USER PLANE LOCATION PROTOCOLS

• US 20110235655A1
• Filed: 12/04/2009
• Published: 09/29/2011
• Est. Priority Date: 12/04/2008
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Halivaara, Ismo, Wirola, Lauri, Syrjarinne, Jari
• Granted Patent: US 9,615,198 B2
• Time in Patent Office: Days
• US Class Current: 370/474
• CPC Class Codes: G01S 19/05 providing aiding data
• CPC Class Codes: G01S 19/07 providing data for correcting measured positioning data, e.g. DGPS [differential GPS] or ionosphere corrections
• CPC Class Codes: G01S 19/071 DGPS corrections
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/024 Guidance services
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Abstract

Systems and methods are provided allowing for a vendor-defined payload in a standardized user-plane location solution/protocol, where proprietary extension support is introduced into one or more standardized solutions. In accordance with a first embodiment, a location payload consists of structures for transferring requests, assistance data, measurements and positioning instructions. Therefore, a proprietary extension is included in each of these structures so that, for example, proprietary assistance data can be requested in an appropriate structure. In accordance with another embodiment, a proprietary extension is introduced at the highest abstraction level. For example and in an actual implementation, a vendor can define that in the beginning of the proprietary payload, the proprietary extension is defined, whether the proprietary payload contains a request, assistance, etc.

Claims

1-50. -50. (canceled)

51. A method, comprising:

creating a payload structure having at least one structure for at least one of requesting and transmitting at least one of assistance and location information in a user-plane location protocol; and

adding at least one proprietary extension to the payload structure.

52. The method of claim 51, wherein the at least one proprietary extension comprises an information element having a vendor-specific payload.

53. The method of claim 52, wherein the vendor-specific payload is identified by a vendor identifier.

54. The method of claim 52, wherein the proprietary extension comprises more than one vendor-specific payload, the vendor-specific payloads being distinguished by vendor identifiers.

55. The method of claim 51, wherein the at least one proprietary extension comprises an information element having a vendor identifier and at least one of a placeholder for a message type and an assistance data identifier.

56. The method of claim 55, wherein the proprietary extension comprises more than one vendor-specific payload, the vendor-specific payloads being distinguished by vendor identifiers and either the message type or the assistance data identifier.

57. The method of claim 55, wherein the message type refers to a type of the at least one of the assistance and location information to be transmitted via the user-plane location protocol.

58. The method of claim 55, wherein interpretation of the placeholder for the message type is specified by a vendor.

59. The method of claim 55, wherein the vendor identifier and either the assistance data identifier or the message type are indicative of a particular service provider and at least one of a navigation model, time assistance, reference location, an atmosphere model, a differential correction, sensor assistance, acquisition assistance, position information, high-accuracy position information, multi-frequency multi-Global Navigation Satellite System measurement data, global positioning system-related data, computationally-generated measurements, sensor measurements, route information, and waypoint information.

60. The method of claim 51, wherein the addition of the at least one proprietary extension occurs at each of the at least one structure for transmitting the at least one of the assistance and location information.

61. The method of claim 51, wherein the payload structure is defined as containing the at least one of the assistance and location information.

62. The method of claim 52, wherein the vendor-specific payload comprises decoding instructions in addition to a data.

63. A computer program product, embodied on a computer-readable storage medium, comprising computer code configured to perform the processes of creating a payload structure having at least one structure for at least one of requesting and transmitting at least one of assistance and location information in a user-plane location protocol;

and adding at least one proprietary extension to the payload structure.

64. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following;

create a payload structure having at least one structure for at least one of requesting and transmitting at least one of assistance and location information in a user-plane location protocol; and

add at least one proprietary extension to the payload structure.

65. The apparatus of claim 64, wherein the at least one proprietary extension comprises an information element having a vendor-specific payload.

66. The apparatus of claim 65, wherein the vendor-specific payload is identified by a vendor identifier.

67. The apparatus of claim 65, wherein the proprietary extension comprises more than one vendor-specific payload, the vendor-specific payloads being distinguished by vendor identifiers.

68. The apparatus of claim 64, wherein the at least one proprietary extension comprises an information element having a vendor identifier and at least one of a placeholder for a message type and an assistance data identifier.

69. The apparatus of claim 68, wherein the proprietary extension comprises more than one vendor-specific payload, the vendor-specific payloads being distinguished by vendor identifiers and either the message type or the assistance data identifier.

70. The apparatus of claim 64, wherein the payload structure is defined as containing the at least one of the assistance and location information.

71. The apparatus of claim 65, wherein the vendor-specific payload comprises decoding instructions in addition to a data.

72. The apparatus of claim 64, wherein the apparatus is a server or a mobile terminal.