US2026039723A1PendingUtilityA1

Systems and methods for indicating spatial map employment for localization services

Assignee: SAMSUNG ELECTRONICS CO LTDPriority: Aug 5, 2024Filed: Aug 1, 2025Published: Feb 5, 2026
Est. expiryAug 5, 2044(~18 yrs left)· nominal 20-yr term from priority
H04W 12/08H04L 67/52
66
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Embodiments herein disclose methods for indicating a spatial map employment for a localization service. The method includes sending, by a first entity ( 102 ), a subscribe request to subscribe for a spatial map employed event to a second entity ( 112 ). The subscribe request may include a map identity, an identity associated with a requestor, and at least one security parameter. The method further includes receiving, by the first entity ( 102 ), a success response from the second entity ( 112 ) based on the subscribe request. The success response may include a subscription identity.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method performed by a first entity in a communication system, the method comprising:
 transmitting, to a second entity, a first request message to create a spatial map associated with an area of interest; and   in case that the spatial map produced based on a processed sensor data is not ready to provide service, receiving, from the second entity, a first response message including information indicating in-progress.   
     
     
         2 . The method of  claim 1 , further comprising:
 in case that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service, receiving, from the second entity, a first notification message for indicating that the spatial map is ready to provide service.   
     
     
         3 . The method of  claim 1 , further comprising:
 transmitting, to the second entity, a second request message to subscribe spatial map event;   in case that the first entity is authorized, receiving, from the second entity, a second response message including an identity of a subscribe request; and   in case that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service, receiving, from the second entity, a second notification message for indicating that the spatial map is ready to provide service.   
     
     
         4 . The method of  claim 3 , wherein the second request message includes at least one of an identifier of the first entity, security information, or an identifier of the spatial map. 
     
     
         5 . The method of  claim 1 ,
 wherein the spatial map is ready to provide service corresponds to being employed for a localization service,   wherein the first entity comprises at least one of an enabler client, a vertical application layer (VAL) server, a service enabler architecture layer (SEAL) client, a SEAL spatial map (SM) client, and   wherein the second entity comprises at least one of an enabler server, a SEAL server, or a SEAL SM server.   
     
     
         6 . A method performed by a second entity in a communication system, the method comprising:
 receiving, from a first entity, a first request message to create a spatial map associated with an area of interest;   producing the spatial map based on a processed sensor data; and   in case that the spatial map is not ready to provide service, transmitting, to the first entity, a first response message including information indicating in-progress.   
     
     
         7 . The method of  claim 6 , further comprising:
 determining that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service; and   transmitting, to the first entity, a first notification message for indicating that the spatial map is ready to provide service.   
     
     
         8 . The method of  claim 6 , further comprising:
 receiving, from the first entity, a second request message to subscribe spatial map event;   performing an authorization of the first entity;   in case that the first entity is authorized, transmitting, to the first entity, a second response message including an identity of a subscribe request;   determining that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service; and   transmitting, to the first entity, a second notification message for indicating that the spatial map is ready to provide service.   
     
     
         9 . The method of  claim 8 , wherein the second request message includes at least one of an identifier of the first entity, security information, or an identifier of the spatial map. 
     
     
         10 . The method of  claim 6 ,
 wherein the spatial map is ready to provide service corresponds to being employed for a localization service,   wherein the first entity comprises at least one of an enabler client, a vertical application layer (VAL) server, a service enabler architecture layer (SEAL) client, a SEAL spatial map (SM) client, and   wherein the second entity comprises at least one of an enabler server, a SEAL server, or a SEAL SM server.   
     
     
         11 . A first entity in a communication system, the first entity comprising:
 a transceiver; and   a controller configured to:
 transmit, to a second entity via the transceiver, a first request message to create a spatial map associated with an area of interest, and 
 in case that the spatial map produced based on a processed sensor data is not ready to provide service, receive, from the second entity via the transceiver, a first response message including information indicating in-progress. 
   
     
     
         12 . The first entity of  claim 11 , wherein the controller is further configured to:
 in case that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service, receive, from the second entity via the transceiver, a first notification message for indicating that the spatial map is ready to provide service.   
     
     
         13 . The first entity of  claim 11 , wherein the controller is further configured to:
 transmit, to the second entity via the transceiver, a second request message to subscribe spatial map event,   in case that the first entity is authorized, receive, from the second entity via the transceiver, a second response message including an identity of a subscribe request, and   in case that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service, receive, from the second entity via the transceiver, a second notification message for indicating that the spatial map is ready to provide service.   
     
     
         14 . The first entity of  claim 13 , wherein the second request message includes at least one of an identifier of the first entity, security information, or an identifier of the spatial map. 
     
     
         15 . The first entity of  claim 11 ,
 wherein the spatial map is ready to provide service corresponds to being employed for a localization service,   wherein the first entity comprises at least one of an enabler client, a vertical application layer (VAL) server, a service enabler architecture layer (SEAL) client, a SEAL spatial map (SM) client, and   wherein the second entity comprises at least one of an enabler server, a SEAL server, or a SEAL SM server.   
     
     
         16 . A second entity in a communication system, the second entity comprising:
 a transceiver; and   a controller configured to:
 receive, from a first entity via the transceiver, a first request message to create a spatial map associated with an area of interest, 
 produce the spatial map based on a processed sensor data, and 
 in case that the spatial map is not ready to provide service, transmit, to the first entity via the transceiver, a first response message including information indicating in-progress. 
   
     
     
         17 . The second entity of  claim 16 , wherein the controller is further configured to:
 determine that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service, and   transmit, to the first entity via the transceiver, a first notification message for indicating that the spatial map is ready to provide service.   
     
     
         18 . The second entity of  claim 16 , wherein the controller is further configured to:
 receive, from the first entity via the transceiver, a second request message to subscribe spatial map event,   perform an authorization of the first entity,   in case that the first entity is authorized, transmit, to the first entity via the transceiver, a second response message including an identity of a subscribe request,   determine that the second entity has sufficient information to map all objects related to the area of interest and the spatial map is ready to provide service, and   transmit, to the first entity via the transceiver, a second notification message for indicating that the spatial map is ready to provide service.   
     
     
         19 . The second entity of  claim 18 , wherein the second request message includes at least one of an identifier of the first entity, security information, or an identifier of the spatial map. 
     
     
         20 . The second entity of  claim 16 ,
 wherein the spatial map is ready to provide service corresponds to being employed for a localization service,   wherein the first entity comprises at least one of an enabler client, a vertical application layer (VAL) server, a service enabler architecture layer (SEAL) client, a SEAL spatial map (SM) client, and   wherein the second entity comprises at least one of an enabler server, a SEAL server, or a SEAL SM server.

Join the waitlist — get patent alerts

Track US2026039723A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.