10.46243/jst.2023.v8.i04.pp40-45 registered
UBLS - USER-BASED LOCATION SELECTION SCHEME FOR PRESERVING LOCATION PRIVACY
Resolves to https://www.jst.org.in/index.php/pub/article/view/695
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2023.v8.i04.pp40-45
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 c36e9ce2396dc140…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
UBLS - USER-BASED LOCATION SELECTION SCHEME FOR PRESERVING LOCATION PRIVACY (PrincipalTitle)
Published 2023-10-04
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 8 · issue 4 · pages 40–45
Agents
- Dr.S.Suresh Dr.S.Suresh (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2023.v8.i04.pp40-45
Abstract
Due to the wide availability of location-based services (LBSs) that enable many applications to provide user tailored services, it becomes possible to trace the locations of an individual by an adversary, especially when the LBS server is distrusted, which violates the user’s privacy. Therefore, we propose, in this project, a user-based location selection scheme (UBLS) to hide the users’ locations using k-anonymity to preserve users’ privacy. The proposed scheme uses the concept of dummy locations to hide the real locations of the users, but on top of that, it selects the dummy locations based on the users that exist in these locations. Moreover, we propose an attacker location exclusion (ALE) algorithm that can be used to attack the existing location privacypreserving schemes. We also propose a new metric, namely location privacy level (LPL), to qualify the ability of the malicious LBS server to reduce the privacy level of the requester. Our envisioned UBLS scheme is evaluated with extensive computer-based simulations. Comparing to the existing schemes in the literature that preserve location privacy, our proposed UBLS demonstrates performance improvement in terms of entropy, cloaking region, and location privacy level metrics
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2023.v8.i04.pp40-45 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | UBLS - USER-BASED LOCATION SELECTION SCHEME FOR PRESERVING LOCATION PRIVACY (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr.S.Suresh Dr.S.Suresh publisher: Longman Publishers published: 2023-10-04 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 8 · no. 4 · pp. 40–45 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 90 fields set · sha256 5bf42f4e776f… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | agents.0.name.family: agents.0.name.given: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
